We are currently using the 2.22 version. In that version, we are using aggregation queries that aggregate event data into data sets that have a weekly time period.
We want to upgrade DHIS2 to 2.23 soon. As aggregation queries are not supported anymore in the 2.23 version, we will replace them with program indicators. We started to create several program indicators, but we are facing a problem.
When we create monthly reports the monthly totals don’t match with the sum of the aggregated weekly totals belonging to that month. For example:
Aggregate data for 2016W39 will be aggregated into 2016 September when displayed per month.
Events with the date 2016-10-01 will be aggregated into 2016W39 when displayed by week but aggregated into 2016 October when displayed by month.
This makes it confusing for end users because for aggregate data September 2016 is the sum of the weeks 2016W36-2016W39 (28 days), whereas for event data September 2016 is the sum of events between 2016-09-01 and 2016-09-30 (30 days).
Has anybody else experienced this problem, and is there a way to have these program indicators aggregated by month using ISO weeks?
we experience the same problem in MSF Spain, and the team from MSF Belgium has brought this conversation to the table more than once. It was actually discussed during the experts academy in Oslo, however I cannot see anything referring to this in the roadmap.
In fact, even if we don’t have individual data and work only with aggregates, the aggregation of weeks into months, according to where Monday falls, is not ideal and we have to extract information weekly and aggregate it externally, for example,to report to the MoH which allocates the week into the month in which it has four days. Simplifying, the week goes where its Thursday is.
For the combination of individual and agg. data; the problem gets worse as you described and only a proportional distribution of values depending on the number of days belonging to each month will be more approximate to reality (assuming the aggregated value is equally distributed along the days of the week).
We understand that the solution might not be trivial, but would love the conversation to be considered for next releases.
We are currently using the 2.22 version. In that version, we are using aggregation queries that aggregate event data into data sets that have a weekly time period.
We want to upgrade DHIS2 to 2.23 soon. As aggregation queries are not supported anymore in the 2.23 version, we will replace them with program indicators. We started to create several program indicators, but we are facing a problem.
When we create monthly reports the monthly totals don’t match with the sum of the aggregated weekly totals belonging to that month. For example:
Aggregate data for 2016W39 will be aggregated into 2016 September when displayed per month.
Events with the date 2016-10-01 will be aggregated into 2016W39 when displayed by week but aggregated into 2016 October when displayed by month.
This makes it confusing for end users because for aggregate data September 2016 is the sum of the weeks 2016W36-2016W39 (28 days), whereas for event data September 2016 is the sum of events between 2016-09-01 and 2016-09-30 (30 days).
Has anybody else experienced this problem, and is there a way to have these program indicators aggregated by month using ISO weeks?