dhis2-users team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Hi Baakai,

This sounds like a caching issue to me. What I mean is that the  system or
bowser, in order to boost performance remembered the query
(indicator,period, orgunit) and gave you the same result from its
memory/cache without actually calculating the values again.

Can you try with another orgunit or period in the pivot table and see if
you still get non-annualised values for that same indicator?

If the numerator is monthly and the denominator is yearly the annualised
option will add a factor of 12 to the indicators value,  so should be easy
to see whether it works or not.

Ola
------
 On 26 Mar 2015 00:35, "Baakai Kamoriki" <btkamoriki@xxxxxxxxx> wrote:

> Thanks Lars and Ola,
>
> It works!  I have set the aggregation operator to "average(sum in org
> unit hierarchy)" on the population data elements.  I also noticed that
> even without setting "annualized" to yes, for the indicators it still
> yield the same result in pivot table as to that set to "annualized".
>
> In fact, after setting aggregation operator to "average(sum in org
> unit hierarchy) on the population data element, I went straight to the
> pivot table and run the analysis.  It gives me the result but then I
> realized that I have not set the indicator to "annualized".  I decided
> to download a copy of the result to excel before I annualized the
> indicator, just to see what would be the difference in the results.
>
> Now having set the indicator to "annualized - yes", I refresh the
> pivot table and run the same indicator again with same period and org
> unit and to my surprise the results were the same? Does that mean that
> we do not have to annualize the indicator if the denominator is set to
> "average(sum in org unit hierarchy).
>
> I did not try it out with data element aggregation operator set to
> "average" instead of "average (sum in org unit hierarchy)".
>
> Anyway, thanks once again for your help.
>
> Regards
>
>
>
> On Tue, Mar 24, 2015 at 6:16 PM, Lars Helge Øverland
> <larshelge@xxxxxxxxx> wrote:
> > Hi Baakai,
> >
> > make sure you set the "aggregation operator" to "average (sum in org unit
> > hierarchy)" on the population data elements. Then set "annualized" to yes
> > for your indicators.
> >
> > regards,
> >
> > Lars
> >
> >
> > On Tue, Mar 24, 2015 at 4:49 AM, Baakai Kamoriki <btkamoriki@xxxxxxxxx>
> > wrote:
> >>
> >> Dear all,
> >>
> >> Can anyone enlightens on how to generate monthly indicators which uses
> >> yearly population data?
> >>
> >> I had been trying to run pivot table on some health indicator for
> >> Solomon Islands such as watery diarrhoea, ARI to name a few by month
> >> but the pivot table always say no values.  In fact these data are
> >> collected on a monthly basis, however our population figures are
> >> yearly?
> >>
> >> Is there a way to do this kind of analysis in DHIS?
> >>
> >> We are currently using version 2.18.
> >>
> >> Many thanks.
> >>
> >> --
> >> Mrs Baakai Kamoriki
> >> Chief Medical Statistician
> >> HIS Unit/ MOH
> >> Honiara
> >> Solomon Islands
> >>
> >> _______________________________________________
> >> 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
> >
> >
>
>
>
> --
> Mrs Baakai Kamoriki
> Chief Medical Statistician
> HIS Unit/ MOH
> Honiara
> Solomon Islands
>
> _______________________________________________
> 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
>