Re: [Dhis2-devs] Why no Category Combinations for Patient Domain type data elements?
Thank you so much Jason. This sounds good to me. John John Ojo MD, FMCPH Accra, Ghana. Mobile: +233 234691626 Skype: Johnojo Email: jn...@yahoo.com From: Jason Pickering jason.p.picker...@gmail.com To: John Ojo jn...@yahoo.com Cc: DHIS developers dhis2-devs@lists.launchpad.net; dhis1-users dhis2-us...@lists.launchpad.net Sent: Saturday, July 27, 2013 12:53 PM Subject: Re: [Dhis2-devs] Why no Category Combinations for Patient Domain type data elements? Hi John, Not really sure the entire approach makes sense. For the tracker module, you would typically have a tracker data element like Received HIV prevention capacity building through step-down technical assistance which would be a boolean (True/False). This would represent an event. Did they receive capacity building or did they not? If you are registering people then you would need to register the person obviously, and provide their gender and something like Affiliation, which would need to be a Person attribute with Predefined values corresponding to the options NGO, CBO, . A slightly different but similar approach would be needed for anonymous events. In the aggregation query builder, you would then need to map each of the different combinations to the correct category option, such as If Received HIV prevention capacity building through step-down technical assistance = TRUE AND Gender = Male and Affiliation = NGO were all true, this would get mapped to the corresponding aggregate data element Number of individuals who Received HIV prevention capacity building through step-down technical assistance in the male/NGO category combo option. I This is how I understand it anyway, but there are others out there who understand this module better than me. :) Regards, Jason On Sat, Jul 27, 2013 at 12:49 PM, John Ojo jn...@yahoo.com wrote: Dear All, I have noticed that data elements defined with Patient Domain type cannot have category combinations. Please why is this so? I have a data element defined with Aggregate Domain type and the data element has category combinations (Sex + Organization type). Pls see the attached screenShot. The challenge is that values for each of the data fields in the screenShot must come from data aggregated from the Tracker side of my DHIS2 application. Following the instructions titled Sample of person aggregation on page 241 of DHIS2 2.12, I tried creating a corresponding data element on the tracker side to match my data element 22a (screenShot) but realized my tracker-side data element cannot have the category combinations like we have in the screenShot. I am thinking of creating several data elements (Patient domain type) that will map to each of the data fields in the screenShot as follows: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Female Please ignore the 't' in parenthesis; it's just to signify (to me) that the data element is the tracker side equivalent. The strategy is that data collected in the data element: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male in the tracker module, would be aggregated into the corresponding data field in the screenShot and so on. My next questions are: Will this approach work? Would you consider this approach as a good way to achieve my aim? If not, please could somebody kindly suggest a better, more efficient way of handling this situation? I would appreciate a very clear
[Dhis2-devs] Why no Category Combinations for Patient Domain type data elements?
Dear All, I have noticed that data elements defined with Patient Domain type cannot have category combinations. Please why is this so? I have a data element defined with Aggregate Domain type and the data element has category combinations (Sex + Organization type). Pls see the attached screenShot. The challenge is that values for each of the data fields in the screenShot must come from data aggregated from the Tracker side of my DHIS2 application. Following the instructions titled Sample of person aggregation on page 241 of DHIS2 2.12, I tried creating a corresponding data element on the tracker side to match my data element 22a (screenShot) but realized my tracker-side data element cannot have the category combinations like we have in the screenShot. I am thinking of creating several data elements (Patient domain type) that will map to each of the data fields in the screenShot as follows: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Female Please ignore the 't' in parenthesis; it's just to signify (to me) that the data element is the tracker side equivalent. The strategy is that data collected in the data element: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male in the tracker module, would be aggregated into the corresponding data field in the screenShot and so on. My next questions are: Will this approach work? Would you consider this approach as a good way to achieve my aim? If not, please could somebody kindly suggest a better, more efficient way of handling this situation? I would appreciate a very clear step-by-step directions to solving this problem. Thank you, John John Ojo MD, FMCPH Accra, Ghana. Mobile: +233 234691626 Skype: Johnojo Email: jn...@yahoo.com attachment: screenShot.png___ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
Re: [Dhis2-devs] Why no Category Combinations for Patient Domain type data elements?
Hi John, Not really sure the entire approach makes sense. For the tracker module, you would typically have a tracker data element like Received HIV prevention capacity building through step-down technical assistance which would be a boolean (True/False). This would represent an event. Did they receive capacity building or did they not? If you are registering people then you would need to register the person obviously, and provide their gender and something like Affiliation, which would need to be a Person attribute with Predefined values corresponding to the options NGO, CBO, . A slightly different but similar approach would be needed for anonymous events. In the aggregation query builder, you would then need to map each of the different combinations to the correct category option, such as If Received HIV prevention capacity building through step-down technical assistance = TRUE AND Gender = Male and Affiliation = NGO were all true, this would get mapped to the corresponding aggregate data element Number of individuals who Received HIV prevention capacity building through step-down technical assistance in the male/NGO category combo option. I This is how I understand it anyway, but there are others out there who understand this module better than me. :) Regards, Jason On Sat, Jul 27, 2013 at 12:49 PM, John Ojo jn...@yahoo.com wrote: Dear All, I have noticed that data elements defined with Patient Domain type cannot have category combinations. Please why is this so? I have a data element defined with Aggregate Domain type and the data element has category combinations (Sex + Organization type). Pls see the attached screenShot. The challenge is that values for each of the data fields in the screenShot must come from data aggregated from the Tracker side of my DHIS2 application. Following the instructions titled Sample of person aggregation on page 241 of DHIS2 2.12, I tried creating a corresponding data element on the tracker side to match my data element 22a (screenShot) but realized my tracker-side data element cannot have the category combinations like we have in the screenShot. I am thinking of creating several data elements (Patient domain type) that will map to each of the data fields in the screenShot as follows: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - CBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - FBO_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - intGvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - Gvmntal_Female 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Male 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - HFacility_Female Please ignore the 't' in parenthesis; it's just to signify (to me) that the data element is the tracker side equivalent. The strategy is that data collected in the data element: 22a(t) # of individuals who received HIV prevention capacity building through step-down technical assistance - NGO_Male in the tracker module, would be aggregated into the corresponding data field in the screenShot and so on. My next questions are: Will this approach work? Would you consider this approach as a good way to achieve my aim? If not, please could somebody kindly suggest a better, more efficient way of handling this situation? I would appreciate a very clear step-by-step directions to solving this problem. Thank you, John *John Ojo MD, FMCPH * Accra, Ghana. Mobile: +233 234691626 Skype: Johnojo Email: jn...@yahoo.com j...@corridor-sida.org http://www.corridor-sida.org/ ___ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
