I get different monthly consultation numbers when I create same pivot table using weekly and monthly reporting period for same period (let’s say Jan-2018). Therefore, I was wondering if anyone ever encounter same issue with DHIS2 implementation and how I can resolve this problem because I can’t rely on monthly, quarterly, annual reporting period numbers as they are not accurate as weekly.
I get different monthly consultation numbers when I create same pivot table using weekly and monthly reporting period for same period (let’s say Jan-2018). Therefore, I was wondering if anyone ever encounter same issue with DHIS2 implementation and how I can resolve this problem because I can’t rely on monthly, quarterly, annual reporting period numbers as they are not accurate as weekly.
Thanks for your kind reply. Entering data on daily basis for our context is not feasible therefore we have to enter/import data into DHIS2 on weekly basis.
Since weekly, monthly, quarterly, etc. as period have been provided by DHIS2 database, don’t you think they all should be align with each other while extracting the data? In addition, I was wondering if DHIS2 developers are aware of this issue?
I get different monthly consultation numbers when I create same pivot table using weekly and monthly reporting period for same period (let’s say Jan-2018). Therefore, I was wondering if anyone ever encounter same issue with DHIS2 implementation and how I can resolve this problem because I can’t rely on monthly, quarterly, annual reporting period numbers as they are not accurate as weekly.
Unfortunately , working over the overlap issues may not be an easy one. The big question is which month do you consider the data for if the week starts within the previous month or the one that ends in another month,
Probably the month with many days takes up the data BUT remember like Prosper said, it will be an approximation and not an exact match of data.
A More realistic data would be accurate as you go higher in the period hierarchy e…g. quarterly, …
Thanks for your kind reply. Entering data on daily basis for our context is not feasible therefore we have to enter/import data into DHIS2 on weekly basis.
Since weekly, monthly, quarterly, etc. as period have been provided by DHIS2 database, don’t you think they all should be align with each other while extracting the data? In addition, I was wondering if DHIS2 developers are aware of this issue?
I get different monthly consultation numbers when I create same pivot table using weekly and monthly reporting period for same period (let’s say Jan-2018). Therefore, I was wondering if anyone ever encounter same issue with DHIS2 implementation and how I can resolve this problem because I can’t rely on monthly, quarterly, annual reporting period numbers as they are not accurate as weekly.