dhis2-users team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Roger,

I am not 100% sure why or if this would be necessary. When you mean
"in order to use it for selection", are you referring to selection in
a PivotTable view? A reference table
(_organisationunitgroupsetstructure) can be generated which will
provide the necessary data on the Group Set structure of
Organizational units. The other table (orgunitgroupmembers) and
(orgunitgroup) could be used in conjunction with this table to provide
different views and thus filters on the data. Both of these can be
used for different filtering/combination operations as needed in a
PivotTable view.

One of the key ideas behind groups sets, was the ability to combine
groups in different ways.  One could them lump different orgunit
groups into a common set and then aggregate the data further in a view
or PivotTable (using the (_organisationunitgroupsetstructure) table.
So, if you have orgunitgroups (Urban Health Center, Rural Health
Center, Health Post, Hosptial Affiliated Health Center) these might be
grouped into a group set (Primary Health Care). You might have (First
level hospital, Second level hospital, Tertiary hospital, specialist
hospital) and group these into a group set (Hospital). This is my
understanding of the functionality at least. Of course, you would have
your compulsory group sets as well (Type, Ownership).

In our case here in Zambia, we have "subfacilities", which function
essentially as wards within a facility. Examples are "Maternity",
"OPD", "Dental",etc. These each belong to an orgunitgroupset
(Subfacility Type). So, I would say in your case yes, you would need
two separate group sets for facility type and activity type. Each of
these would be "non-compulsory" as they do not apply to all orgunits.

That is my recommendation, but Ola might have some views on this as well?

Regards,
Jason


On Mon, Apr 19, 2010 at 8:52 PM, Friedman, Roger (CDC/OID/NCHHSTP)
(CTR) <rdf4@xxxxxxx> wrote:
>
>        Thanks, Jason.
>        I already have Type in OrgUnit and it breaks out as you suggest, it just occurred to me that I would have to replicate the information as a group set in order to use it for selection.  I already have an Owner group set that works as you say.  My level hierarchy is Country-Region-District-Subdistrict-Facility-Activity.  In the OrgUnit.Type field, there are the first 4 levels and then multiple values at the facility (eg. hospital, clinic) and activity (eg. ANC clinic, ART clinic, lab, community-based C&T) level.  So would you suggest a single Type groupset with all values or separate non-required groupsets for FacilityType and ActivityType?
> Saludos, Roger
>
> -----Original Message-----
> From: Jason Pickering [mailto:jason.p.pickering@xxxxxxxxx]
> Sent: Monday, April 19, 2010 1:30 PM
> To: Friedman, Roger (CDC/OID/NCHHSTP) (CTR)
> Cc: dhis2-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Dhis2-users] Type
>
> Hi Roger,
> Typically, one would setup at least three groups 1) Type and 2)
> Ownership and 3) Location. Often times type would be used to describe
> National, Province, District, and then a facility type (Hospital,
> Urban Health Center etc). Ownership would typically be Private,
> Government, NGO, etc. Location would be something like Urban,
> Peri-urban, Rural, Rural hard to reach, etc.
>
> There are no hard and fast rules, but these are the ones that have
> been used for sometime with both DHIS 1.4 and 2.
>
> Regards,
> Jason
>
>
> On Mon, Apr 19, 2010 at 7:21 PM, Friedman, Roger (CDC/OID/NCHHSTP)
> (CTR) <rdf4@xxxxxxx> wrote:
>> Lists --
>>        Is it good practice to set up a group that mirrors the values in
>> OrgUnit.Type?
>> Thanks, Roger
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> --
> Jason P. Pickering
> email: jason.p.pickering@xxxxxxxxx
> tel:+260968395190
>
>
>



-- 
--
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190