OK, I need some help as usual.
I have entered my geographic hierarchy.
I have entered the data elements for a simple form (18 count-type indicators disaggregated by sex), I have put them in a group. (BTW, it would be good to have [Unassigned] as a group filter for those who intend to add all their elements and then their group.) I have assigned the group's elements to a dataset and the dataset to certain facilities.
1. How do I specify the disaggregation? Do I have to make a combination of categories that contains only sex? It seems to work for the naked dataset (i.e. no sections, no form) but not when entering by sections.
2. How do I control the order of appearance of data elements in the naked dataset?
3. How do I make sections display the categories? Was the idea that each section would contain a single category?
4. How do I make zeros display and suppress the "don't enter zeroes" message?
5. The green "tool tip" box gets in the way. How about displaying it on a right click instead of always?
I have another form on which I would like to enter detail but transmit only summary counts. It is attached. Everything is just a check mark except for the page headings, day, file number (which is not unique per patient and probably won't be entered) and invalids. There is one field that has to be added for data entry, it's number counselled, follows counseling type (1 for individual, 2 for couples, n for family). There are two fields that have to be modified: day becomes visit date, composed of month and year from the top plus day; instead of checking A, B, or C for counselor, enter the counselor's ID from above. The 3 boxes starting with partner org and counselor will be used for grouping, service is the hierarchy level below facility. There are some complications about the indicators:
HIV positive and negative will be reported by sex (male/female) and age
combinations.
Kits used= 2 if positive or indeterminate or 1 if negative + invalid
Sessions= sum of reciprocal of number counselled
For the columns beginning TB, % referred = 100 * referred / counselled
Reporting frequency is ad hoc except each sheet will contain data for only a single month, which is the basic tabulation unit. I am at a loss as to how to do this. If somebody wants to walk me through this rather than write, I can call you.
DHIS2 identifies sequentially the different levels but you are
free to give them the name you want. However it is better if you want
to
use numbers to identify your levels to do it incrementally. Because if
you name level 5 as level 8, you will introduce some confusion for
other administrators especially when it comes to execute some sql
queries using orgunitstructure table with levels. I mean level 8 -as
child of level 4 in your case - will mean level 5 in dhis2 logic
instead. The possibility given to users to rename the levels is meant
to provide more meaningful level names like national, region, district,
facility, etc.
Thanks, Edem. I guess I should have given the use case.
Country X frequently divides its districts for political and managerial reasons. Indicator target values, population figures used as denominators and maps with the new districts may not be available immediately (if ever), so it will frequently be desirable to display results using a previous version of district definitions in order to show a longer time period. I was hoping to represent this by having multiple levels of district corresponding to each successive version of the definitions. So I wanted to leave some unused level numbers between the current districting and the (presumptively) unchanging sub-districts, so the sub-district level number would always be the same despite the number of versions of districting incorporated.
Perhaps there is some way of maintaining alternative hierarchies that I haven’t thought of.
DHIS2 identifies sequentially the different levels but you are free to give them the name you want. However it is better if you want to use numbers to identify your levels to do it incrementally. Because if you name level 5 as level 8, you will introduce some confusion for other administrators especially when it comes to execute some sql queries using orgunitstructure table with levels. I mean level 8 -as child of level 4 in your case - will mean level 5 in dhis2 logic instead. The possibility given to users to rename the levels is meant to provide more meaningful level names like national, region, district, facility, etc.
Thanks
Edem
On 01/04/2010 20:36, Friedman, Roger (CDC/OID/NCHHSTP) (CTR) wrote:
Lists –
Do org unit levels need to be numbered sequentially? That is, can I have a level 8 org unit as a child of a level 4 org unit?
Ok I see. In this case, what we often do is to represent a coherent
hierarchy that reflects the current situation and use orgUnit groups
and groupsets to address specific cases like like your old districts.
It is not always very smart but still it is the best way available
For instance you can create groups 2005district1 and 2005district2.
2005district1 will comprise 1009 District1 and 2009 District3. 2005
District2 will contain 2009 District2. Then you create an exclusive
groupset named for instance 2005 Hierarchy with 2005 District1 and 2005
District2 as groupset members. You can do the same for other period
having different hierarchy.
Thanks
Edem
···
dhis2-users-bounces+rdf4=cdc.gov@lists.launchpad.netmailto:dhis2-users-bounces+rdf4=cdc.gov@lists.launchpad.netOn
Behalf Of Sent:
**To:**dhis2-users@lists.launchpad.net Subject:
-- Dr Edem K. Kossi
Phone: +228 9923003
+47 99252519
Email: Skype: mylacas
Ok I see. In this case, what we often do is to represent a coherent hierarchy that reflects the current situation and use orgUnit groups and groupsets to address specific cases like like your old districts. It is not always very smart but still it is the best way available
For instance you can create groups 2005district1 and 2005district2. 2005district1 will comprise 1009 District1 and 2009 District3. 2005 District2 will contain 2009 District2. Then you create an exclusive groupset named for instance 2005 Hierarchy with 2005 District1 and 2005 District2 as groupset members. You can do the same for other period having different hierarchy.
Thanks
Edem
On 02/04/2010 14:58, Friedman, Roger (CDC/OID/NCHHSTP) (CTR) wrote:
Thanks, Edem. I guess I should have given the use case.
Country X frequently divides its districts for political and managerial reasons. Indicator target values, population figures used as denominators and maps with the new districts may not be available immediately (if ever), so it will frequently be desirable to display results using a previous version of district definitions in order to show a longer time period. I was hoping to represent this by having multiple levels of district corresponding to each successive version of the definitions. So I wanted to leave some unused level numbers between the current districting and the (presumptively) unchanging sub-districts, so the sub-district level number would always be the same despite the number of versions of districting incorporated.
Perhaps there is some way of maintaining alternative hierarchies that I haven’t thought of.
DHIS2 identifies sequentially the different levels but you are free to give them the name you want. However it is better if you want to use numbers to identify your levels to do it incrementally. Because if you name level 5 as level 8, you will introduce some confusion for other administrators especially when it comes to execute some sql queries using orgunitstructure table with levels. I mean level 8 -as child of level 4 in your case - will mean level 5 in dhis2 logic instead. The possibility given to users to rename the levels is meant to provide more meaningful level names like national, region, district, facility, etc.
Thanks
Edem
On 01/04/2010 20:36, Friedman, Roger (CDC/OID/NCHHSTP) (CTR) wrote:
Lists –
Do org unit levels need to be numbered sequentially? That is, can I have a level 8 org unit as a child of a level 4 org unit?
