← Back to team overview

dhis2-users team mailing list archive

Re: Constructing indicators from boolean data elements


Hi Jennifer

In order to do this you should create two program indicators.

1. Count events with the yes responses
2. Count the total events

You can then make a combined indicator in the maintenance indicator app
using these two program indicators.

To do this choose 'programs' followed by program indicators when you select
the numerator/denominator


On Jan 1, 2018 6:16 PM, "Spratt, Jennifer" <spratt@xxxxxxx> wrote:

Hello all, I am trying to create an indicator that is the proportion of
entities that replied “yes” on a Boolean data element in a dataset. (Number
replying yes divided by total number responding).

I have searched high and low in the DHIS2 user’s guide, but find nothing to
help me construct what should be a pretty basic indicator.

I have specified the Indicator type as “percentage”, the numerator as
#{UID}==1 and the denominator as #{UID}>=0,  (replacing “UID” with the
actual UID of course)  and I KNOW there are both 1s and 0s in the data
element in question, but the result is always “0”.

Also, I thought one could use an indicator as the basis for another
indicator, but am unable to see “indicator” among the choice of items when
creating numerators and denominators…

PS, I have also tried +(#{UID}==1)  and #{UID}==”TRUE”  as the numerator,
but the result is the same… Evidently filters do not work in aggregate
indicator construction? Or do they?

Could you enlighten me as to what I may be doing wrong, and ideally, point
me to the elegant obvious solution?

Much obliged,

*Jennifer E. Spratt, Ph.D.*

Senior Education Research Analyst

International Development Group at RTI International

Email: spratt@xxxxxxx   Skype: j_spratt

Mobile: 443-562-2129 <(443)%20562-2129>  Messages: 410-235-0019

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

Follow ups