Hi developers and all,
We have a use case where compulsory data elements have been defined for calculating completeness rates. This is for a monthly data set. When we run the report by month, this works perfectly. In our case, 4 data elements captured = 1 completed report. However when you run the same report over multiple periods, say, quarterly, the calculation is slightly confounding. For instance, completeness is calculated on the basis of Period 1 AND Period 2 AND Period 3 compulsory data elements captured. So in a scenario where I have completed the compulsory data elements for Period 1 and 2 but not 3, this is calculated as 0 reported rather than 2/3. Can someone suggest how we could accommodate the alternative logic which I have in the attached file with screenshots and explanations? This issue continues to be a problem for us. We rely on the obligatory data report to track if people are effectively sending their data to the server. (As a sidenote, we do believe that they are entering the data!) We need to be able to calculate this report on a quarterly and six-monthly basis; no matter what the individual reports say, the answer always comes back zero. Many thanks. Kind regards. __ _ __ _ __ _ __ _ __ _ __ _ __ _ __ _ __Vivre pour vous servir, c'est ma passion|Live to serve you, is my passion Joseph K. Osborn |DHIS IT [email protected] | [email protected]él. : (+243)816695644Skype: jkoduciel , G+Facebook | Twitter | LinkedIn Donate Today!
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
