dhis2-users team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Hi Randy,

In the Pivot Tables your categories will appear as dimensions in the left
side menu, given that the category has the option "Use as data dimension"
enabled (and you run analytics again after enabling that option). This
gives you a lot of flexibility in terms of how you want to aggregate and
display your data.

You could e.g. put the "Partner" category in the filter position of your
table (in Layout). Then select one or more partners in the left side menu
for the "Partners" category (dimension), e.g."FHI".

You could put your second category with the target groups reached
(fishermen etc.) (not sure what you call that category) on the column
position and select all its options.
If you then select all the data elements you need and put the Data
dimension on rows, then the table should look like the one in your email.

Let me know if that works.

Ola
----------


----------------------------------
Ola Hodne Titlestad (Mr)
HISP
Department of Informatics
University of Oslo

Mobile: +47 48069736
Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps
link<https://maps.google.com/maps?q=Eftas%C3%A5sen+68,+0687+Oslo,+Norge&hl=en&ie=UTF8&sll=59.893855,10.785116&sspn=0.222842,0.585709&oq=eftas%C3%A5sen+68,+0687+Oslo,+&t=h&hnear=Eftas%C3%A5sen+68,+%C3%98stensj%C3%B8,+0687+Oslo,+Norway&z=16>


On 30 July 2013 09:50, Wilson,Randy <rwilson@xxxxxxx> wrote:

>  Hi Lars,****
>
> ** **
>
> We’ve completed this exercise of moving this system back to the aggregate
> data entry system thanks to your advice, but have come across an issue on
> the output side:****
>
> ** **
>
> Dataset: FHI****
>
> District: Bugasera****
>
> ** **
>
> *Type of MARPs*
>
> *FSW*
>
> *MSM*
>
> *TD*
>
> *Fishermen*
>
> *PwD*
>
> 1. People reached by peer educators****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> 2. Contacts with people where interpersonal communication was provided****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> 3. People who received condoms****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> Columns are actually category option combos: (FSW ,FHI), (MSM, FHI), (TD,
> FHI), (Fishermen,FHI),(PwD,FHI))****
>
> ** **
>
> In version 2.12 we now can select details to display category option
> combos (for example (FSW,FHI); (fishermen,FHI)) in the data visualizer, but
> it doesn’t work in the pivot table module yet L and there doesn’t appear
> to be a way to break out an individual category (eg. All Fishermen or all
> FSW, regardless of partner).  I’ve had to create a custom query that parses
> out the two halves of the category combination field that we can then use
> for Excel Pivot table analysis.****
>
> ** **
>
> SELECT ****
>
>   _categoryoptioncomboname.categoryoptioncomboname, ****
>
> àdon’t parse out default category options, but for others make string
> upto comma beneficiary****
>
> case when  _categoryoptioncomboname.categoryoptioncomboname <> '(default)'
> then****
>
>                 substring(_categoryoptioncomboname.categoryoptioncomboname
> from 2 for (position(',' in
> _categoryoptioncomboname.categoryoptioncomboname)-2)) ****
>
>                 else****
>
>                 _categoryoptioncomboname.categoryoptioncomboname ****
>
>                 end as beneficiary,****
>
> àdon’t parse out default category options, but for others make string
> after comma partner****
>
> case when  _categoryoptioncomboname.categoryoptioncomboname <> '(default)'
> then****
>
>
> substring(trim(_categoryoptioncomboname.categoryoptioncomboname) from
> position(',' in _categoryoptioncomboname.categoryoptioncomboname)+2 for **
> **
>
>                 position(')' in
> _categoryoptioncomboname.categoryoptioncomboname)-position(',' in
> _categoryoptioncomboname.categoryoptioncomboname)-2) ****
>
>                 else****
>
>                 _categoryoptioncomboname.categoryoptioncomboname ****
>
>                 end as partner,****
>
>   dataelement.name as dataelementname,****
>
>   aggregateddatavalue.organisationunitid, ****
>
>   organisationunit.name as orgunitname, ****
>
>   period.startdate, ****
>
>   aggregateddatavalue.level, ****
>
>   aggregateddatavalue.periodtypeid, ****
>
>   aggregateddatavalue.value****
>
> FROM ****
>
>   public.dataelement, ****
>
>   public.aggregateddatavalue, ****
>
>   public.period, ****
>
>   public.organisationunit, ****
>
>   public._categoryoptioncomboname****
>
> WHERE ****
>
>   aggregateddatavalue.dataelementid = dataelement.dataelementid AND****
>
>   aggregateddatavalue.categoryoptioncomboid =
> _categoryoptioncomboname.categoryoptioncomboid AND****
>
>   aggregateddatavalue.organisationunitid =
> organisationunit.organisationunitid AND****
>
>   aggregateddatavalue.periodid = period.periodid****
>
>   and   aggregateddatavalue.level = 3 ****
>
>   and aggregateddatavalue.periodtypeid= 4****
>
>   and aggregateddatavalue.dataelementid in****
>
>   (SELECT ****
>
>   dataelementid ****
>
> FROM ****
>
>   public._dataelementgroupsetstructure where thematic_area='MARPS');****
>
>   ALTER TABLE _view_healthfacilityhierarchy OWNER TO dhis;****
>
> ** **
>
> ** **
>
> Do you have any other suggestions?****
>
> ** **
>
> Randy****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Lars Helge Øverland [mailto:larshelge@xxxxxxxxx]
> *Sent:* Thursday, March 28, 2013 7:51 PM
> *To:* Wilson,Randy
> *Cc:* dhis2-users@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Dhis2-users] Any suggestions for partner reporting in
> DHIS-2?****
>
> ** **
>
> Hi Randy,****
>
> ** **
>
> on this issue there are lots of opinions - my recommendation would be to
> stick to the aggregate part of the system and leave out the individual
> records module. This is routine data captured at a fixed interval so
> capturing it as events might become messy over time.****
>
> ** **
>
> My suggestion on how to solve this would be to use categories - you could:
> ****
>
> ** **
>
> - set up a category and category combination called "Partners".****
>
> - category options for each partner like "FHI" and "ACCESS".****
>
> - create data elements for each service and assign them to the partner
> category combination. ****
>
> - create one data set per partner (e.g. "HIV counselling FHI").****
>
> - for each data set you create a custom form, and insert the data element
> + category option combinations for input fields accordingly.****
>
> - you create user roles for each partner.****
>
> - you assign the partner data sets to the corresponding partner user roles.
> ****
>
> - you assign users for each partner to the corresponding user roles.****
>
> - you assign data sets (for partners) to facilities according to where the
> partners operate.****
>
> ** **
>
> The partners can then select their data set when entering data, without
> having to worry about "who they are". There are no extra org units to
> maintain and the partners cannot mix up data sets when entering data.****
>
> ** **
>
> One drawback is that you have to create those extra custom forms, but
> since you have a "very simple list of services" this might be affordable.*
> ***
>
> ** **
>
> regards,****
>
> ** **
>
> Lars****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> On Tue, Mar 26, 2013 at 1:02 PM, Wilson,Randy <rwilson@xxxxxxx> wrote:****
>
> Hi all,****
>
>  ****
>
> Our HIV team works with civil society organizations and local partners to
> track a very simple list of services provided to persons living with
> HIV/Aids.****
>
>  ****
>
> The data elements themselves are all numeric so it would be easy to do in
> a regular data set, except that partners don’t fit well in the reporting
> hierarchy which goes from Province -> district -> sub-district -> sector ->
> health facility.****
>
>  ****
>
> Data entered are total numbers per district per partner.****
>
>  ****
>
> For example, a partner (FHI) might work in several districts, so there
> would be more than one FHI report for a given period.****
>
>  ****
>
> District****
>
> Partner****
>
> Period****
>
> Dataelement****
>
> Datavalue****
>
> Rwamagana****
>
> FHI****
>
> Feb-13****
>
> # of PLWHA mutuelle payments made****
>
> 12****
>
> Gicumbi****
>
> FHI****
>
> Feb-13****
>
> # of PLWHA mutuelle payments made****
>
> 30****
>
> Huye****
>
> ACCESS****
>
> Feb-13****
>
> # of PLWHA mutuelle payments made****
>
> 44****
>
> Gicumbi****
>
> ACCESS****
>
> Feb-13****
>
> # of PLWHA mutuelle payments made****
>
> 23****
>
>  ****
>
> I’ve thought of creating a separate partner’s table and entering a partner
> numeric code as one of the fields that could called up in a special report,
> but referential integrity rules won’t let me enter more than one data value
> record per period per district.****
>
>  ****
>
> We can create the report using the Single Event Without Registration
> feature in Individual Records, using an Option set to maintain the list of
> partners, but unfortunately we can’t seem to use any of this data in the
> dashboard, data visualizer, maps or standard reports.****
>
>  ****
>
> If Single Event Without Registration is the only way to enter the data,
> would it not be possible to expose the dataelements for use with the
> standard reporting tools?****
>
>  ****
>
> I remember Jason had to develop this sort of relationship for some work he
> did in Zambia but I’m not sure if it is documented somewhere.****
>
>  ****
>
> Thanks,****
>
>  ****
>
> Randy****
>
>  ****
>
>
> _______________________________________________
> 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****
>
> ** **
>
> _______________________________________________
> 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
>
>