Randy,
Just NOTE that when you set up a data set with a catcombo (which gets stored as attributeoptioncomboids), the assumption is usually that you have several SEPARATE set of values, with each set linked to as specific catcombo (e.g. as source of funding).
Example: you have a facility with three equal sources of funding for HIV counselling and Testing (HCT). Let us say they counsel 6,000 patients, test 5,700, and 900 test HIV positive. If you capture that data as 2,000 counselled, 1,900 tested, and 300 tested positive three times, each time selecting a different source of funding for the data set catcombo, then that’s technically OK and totals are correct (might be conceptually/politically messy, of course, with each funding source claiming “their share” of all HCT clients). The three reports add up to the total. This is typically the situation where each donor demand separate reporting for “their share” of the funding. It also typically results in significant double-counting, because facilities report the same patient cases multiple times.
On the other hand, you might have one data reporting stream (i.e. less chance of double-counting), but where the funding is coming from different sources. Using the data set catcombo option, you would then capture the same data three times but with different catcombos (funding sources). Technically that could become messy, and it might be difficult to avoid erroneous totals. In such cases it might be better to capture funding “shares” as comments, or - if you need to report separately - as separate annual or quarterly data element values. You can then use such “shares” (i.e. fractions) via indicators to generate reports for each source of funding.
The above is mostly technical consideration around data break-downs etc. Strategically/ideologically, analysis by source of funding tend to inflate the importance of donor funding and reduce the importance of government funding (because it’s generic under “salaries” and “drugs” and “utilities” and “construction costs” etc) and eliminate the importance of work done by families and communities (because those are often not even monetised). Just mentioning it to keep things in perspective 
Regards from Norway - snowing for a second day!
Calle
···
On 4 January 2017 at 10:39, Elmarie Claasen elmarie@hisp.org wrote:
Hi Randy,
If you create the attribute options and then add them as categories and category combinations and then assign them to the dataset under category combination ref ART monthly dataset in SL demo then the data entry screen allows the data entry clerk to choose the attribute combos for which to capture data and those are then stored in the data value table based on the selection made.
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
From: Dhis2-users [mailto:dhis2-users-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Wilson, Randy
Sent: Wednesday, January 4, 2017 9:56 AM
To: DHIS 2 developers dhis2-devs@lists.launchpad.net; dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] AttributeOptioncombo field in datavalue table
Is there any documentation available on how to populate the attributeoptioncomboid in the data values table through the data entry screens? We would like to use it to store source of funding as the categoryoptioncombo is already being used for another purpose.
We’re using version 2.24.
–
Randy Wilson
Team Leader: Knowledge Management, Data Use and Research
Rwanda Health System Strengthening Activity
Management Sciences for Health
Rwanda-Kigali
Direct: +250 788308835
E-mail: rwilson@msh.org
Skype: wilsonrandy_us
Stronger health systems. Greater health impact.
www.msh.org
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
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
–
Calle Hedberg
46D Alma Road, 7700 Rosebank, SOUTH AFRICA
Tel/fax (home): +27-21-685-6472
Cell: +27-82-853-5352
Iridium SatPhone: +8816-315-19119
Email: calle.hedberg@gmail.com
Skype: calle_hedberg
