dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

On 10 August 2011 10:10, Jason Pickering <jason.p.pickering@xxxxxxxxx>wrote:

> In fact, it is possible to assign an orgunit to two separate members
> of an orgunit group set. If you create a group set "Services" you can
> add the facility to multiple groups, but only through the Organisation
> unit group management function, and not through the UI for the
> organisation unit itself.
>

Then this is a bug (thanks for mentioning it Jason). The intended design is
to make all groupsets exclusive. I have been pushing for a better workflow
in the UI for creating group sets and groups, and I really don't see any
need to create groups that are not member of any group set. If the workflow
is group set -> groups -> assign orgunits it will be easier to
enforce exclusiveness.

Orgunit groups are intended for aggregation and are therefore strictly
organised in exclusive group sets (at least that is the idea). Right now
such aggregation by groups (within each group set) is possible in pivot
tables, and soon available also in report tables (see roadmap), and any
non-exlusive groupset will cause duplication and confusion. This is not
easily combined with a more free tagging functionality where multiple
attributed are just added freely to an orgunit (e.g. multiple services).

As Suzuki mentioned, the reporting coverage is calculated automatically by
DHIS in Completeness reports and this makes use of the assigned data sets
per orgunit, not the groups.

We should perhaps look into how we can better support the concept of having
multiple services linked to orguits, as there is not always a 1-1 link
between data set and services (at least not a natural one), and as
completeness is provided by data set this is sometimes a limitation. Still I
see this as quite different from having "aggregation groups" and group sets,
and I am not sure we can combine all this within the concept of orgunit
groups.

The approach suggested by Jason is a hack and a workaround, and is not
recommended practice (except maybe for a few experts like Jason who know
exactly what they are doing, and my experience is that most people don't...)
since the risk of data duplication is so high.

To view geographical distribution of orgunits by services provided (and any
other orgunit "categorisation"), e.g. to view all facilities that provide a
service you can use the symbol layer in GIS, and for distribution in numbers
and percentages you can use the orgunit distribution reports. These are both
based on orgunit group sets, and the limitations listed before (only one
group per orgunit per group set) are correct.

As Bob suggested you can create as many group sets as you like, e.g. create
a group set "Emergency Obstetric Care" with groups 'Basic' and
'Comprehensive' and assign facilities to these two groups. Group sets do not
have to be compulsory, so there is no need to assign e.g. facilities that
are not providing the service, in this case obstetric care (so no need to
have a group 'None'). In GIS you can then select the Emergency Obstetric
Care group set in the symbol layer and view locations of facilities with
basic care and facilities with comprehensive care (with custom symbols for
each group). It might seem tedious to create all these group sets, but the
actual assigning of orgunits to groups, which is the main work here, will be
the same.

Ola
-----






Ola
-----


> In this case, the "Services" groupset is not longer exclusive, meaning
> that you might have a facility which belongs to both "DOTS" and "CS",
> both of which belong to the "Services" group set.
>
> The problem comes about in how DHIS2 generates the resource tables.
> DHIS2 only takes one entry, and not both, so even though I may have
> assigned a given orgunit to both "DOTS" and "CS", in the resource
> tables, only "DOTS" appears under the "services" column.
>
> This query will return a list of all groups a given orgunit belongs to
>
> SELECT a.organisationunitid, a.name,c.* from organisationunit a
> INNER JOIN orgunitgroupmembers b on a.organisationunitid =
> b.organisationunitid
> INNER JOIN orgunitgroup c on b.orgunitgroupid = c.orgunitgroupid
>
> If you assign an orgunit to multiple groups, there will be multiple
> rows in this view, which would need to be carefully handled when
> performing analyses in PivotTables, asit will lead duplication unless
> the orgunit group column is separated into multiple columns or
> seperate views are created for each orgunit group prior to feeding the
> data to a PivotTable.
>
> Regards,
> Jason
>
>
> On Wed, Aug 10, 2011 at 9:35 AM, samuel cheburet
> <samuelcheburet@xxxxxxxxx> wrote:
> > Thanks everyone for health discussion
> > Dhis require upgrading to have service while registering new health
> facility
> > using conventional naming. Regards
> >
> > regards
> >
> > On Wednesday, August 10, 2011, Shinichi Suzuki <shin461@xxxxxxxxx>
> wrote:
> >> Hello Chet,
> >>
> >> I think Mr. Wanjala answered properly.
> >>
> >> Group capability in DHIS2 is not use for Service of Facility.
> >>
> >> I know one facility has several services.
> >>
> >> These services comes up as a dataset to be entered.
> >>
> >> So, we assign these datasets along with services of the facilities,
> >> properly.
> >>
> >> Then we could get completeness report by dataset by organisation unit.
> >>
> >> Regards,
> >>
> >>    Suzuki
> >>
> >>
> >>
> >> From: dhis2-devs-bounces+shin461=gmail.com@xxxxxxxxxxxxxxxxxxx
> >> [mailto:dhis2-devs-bounces+shin461 <dhis2-devs-bounces%2Bshin461>=
> gmail.com@xxxxxxxxxxxxxxxxxxx]
> >> On Behalf Of Chet Chaulagai
> >> Sent: Tuesday, August 09, 2011 11:56 PM
> >> To: Brajesh Murari
> >> Cc: dhis2-devs@xxxxxxxxxxxxxxxxxxx
> >> Subject: Re: [Dhis2-devs] OrgUit groups and group sets
> >>
> >>
> >>
> >> Hi Brajesh,
> >> Thank you very much for your clarification. As you said a health
> facility
> >> can be a member of only one group, this is the main limitation of this
> >> database. If I want to know the distribution of CS facilities or
> reporting
> >> coverage of CS facility, I would like to have all facilities offering CS
> >> services be grouped together. People interested in DOTS would like to do
> the
> >> same. The problem comes when one facility is providing the both
> services.
> >> You can place this facility either on DOTS or on CS category, not in
> both
> >> categories.   This is the issue we need to address.
> >> Regards,
> >> Chet
> >>
> >> On Tue, Aug 9, 2011 at 1:50 AM, Brajesh Murari <
> brajesh2murari@xxxxxxxxx>
> >> wrote:
> >>
> >> Hi Chet,
> >>
> >>
> >>
> >> In DHIS2, user have extensive space to make several kind of orgunit
> groups
> >> or more general we can say health facility groups by considering at
> least
> >> one common attribute belongs to all facilities in that group, and
> criteria
> >> for selection could be anything like type of services offered (Cesarean
> >> Section Delivery, ORT, DOTS etc ) or geographical location or
> administrative
> >> regions etc. More precisely we can say, a group set in DHIS2 is always
> >> exclusive, which means that an orgunit (health facility) cannot be
> member of
> >> more than one such group in a group set. If you try otherwise you will
> get
> >> notified by the application and the action not allowed. It is possible
> to
> >> define whether a group set is compulsory or not, which will affect the
> >> completeness of the data when analyzing data using group sets.
> Compulsory
> >> means that ALL orgunits (health facility) must be member of a group in
> that
> >> group set.
> >>
> >>
> >>
> >> Regards,
> >>
> >> Brajesh
> >>
> >>
> >>
> >> On Mon, Aug 8, 2011 at 7:31 PM, wanjala pepela <wanjala2p@xxxxxxxxx>
> >> wrote:
> >>
> >> I think that a facility can have all of them as service areas with
> >> different datasets which are well assigned in DHIS so long as the
> datasets
> >> are put in DHIS.  What the districts should do is to assign the
> different
> >> services to their facilities and a facility will have offering CS, ORT,
> DOTs
> >> and  linked to also CUs .
> >>
> >>
> >>
> >> regards
> >>
> >>
> >>
> >> PEPELA WANJALA
> >
> > --
> > Samuel Cheburet
> > Ministry Of Health
> > P.O. Box 20781
> > Nairobi, Kenya
> > Mobile- 0721624338
> > Don't Compromise The Quality! Don't Risk It! apply Available Standards to
> > Achieve Your/organizational Goal.
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dhis2-devs
> > Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dhis2-devs
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>