Reporting Rate Summary: Calculating Completeness Rate over multiple periods based on Compulsory Data Elements

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

osbornkitsuimi@imaworldhealth.org |

osbornlegrand@yahoo.fr

Tél. : (+243)816695644

Skype: jkoduciel , G+

Facebook | Twitter | LinkedIn

Donate Today!

Hi Joseph,

first - I cannot see any attachments for the screenshots/explanations, could you check if you attached them?

regards,

Lars

···

On Mon, Nov 9, 2015 at 11:34 AM, Joseph K. Osborn osbornlegrand@hotmail.fr wrote:

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

osbornkitsuimi@imaworldhealth.org |

osbornlegrand@yahoo.fr

Tél. : (+243)816695644

Skype: jkoduciel , G+

Facebook | Twitter | LinkedIn

Donate Today!

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Sorry Lars and all , here is the attachements.

Please Lars,
Are there any response to this request?
Thank a lot.