When report tables are generated, the tables are populated with a zero, which makes it difficult to determine if the user had entered a zero into the database or left the data element blank. Is there a report that can be generated within DHIS that could be used to analyze data completeness by data element, instead of by report?
In side are both SQL as well as BIRT reports that may give you, after
modification, what you want.
Best regards,
Jason
···
On Tue, Jan 26, 2010 at 12:35 AM, Paul Amendola <Paul.Amendola@theirc.org> wrote:
When report tables are generated, the tables are populated with a zero,
which makes it difficult to determine if the user had entered a zero into
the database or left the data element blank. Is there a report that can be
generated within DHIS that could be used to analyze data completeness by
data element, instead of by report?
Thank you for the response and for the reports. Do you know if this has been looked at in terms of exporting the report tables to Excel? When exported to excel, all of the data elements are zero (both true zeros and incomplete data).
Thanks again
Paul
···
-----Original Message-----
From: Jason Pickering [mailto:jason.p.pickering@gmail.com]
Sent: Monday, January 25, 2010 11:25 PM
To: Paul Amendola
Cc: dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Question about Data Completeness
Indeed, a topic dear to my heart and one that we have spent some time
working on.
In side are both SQL as well as BIRT reports that may give you, after
modification, what you want.
Best regards,
Jason
On Tue, Jan 26, 2010 at 12:35 AM, Paul Amendola <Paul.Amendola@theirc.org> wrote:
When report tables are generated, the tables are populated with a zero,
which makes it difficult to determine if the user had entered a zero into
the database or left the data element blank. Is there a report that can be
generated within DHIS that could be used to analyze data completeness by
data element, instead of by report?
Hi Paul,
You can export these reports to Excel no problem as they are BIRT reports.
These reports (and associated SQL) analyze the ratio of blank data
values to a numeric value, including zeroes. It would be simple enough
to alter the SQL to analyze NULLS, zeros and actual data values, but
it would require modification to the SQL that produces the
materialized view.
The issue of NULLS and zeroes, has a number of long and winding
threads on this mailing list. It might be good to search the archives
and see if any of the discussion helps to clarify things.
Regards,
Jason
···
On Tue, Jan 26, 2010 at 5:23 PM, Paul Amendola <Paul.Amendola@theirc.org> wrote:
Hi Jason
Thank you for the response and for the reports. Do you know if this has been looked at in terms of exporting the report tables to Excel? When exported to excel, all of the data elements are zero (both true zeros and incomplete data).
Thanks again
Paul
-----Original Message-----
From: Jason Pickering [mailto:jason.p.pickering@gmail.com]
Sent: Monday, January 25, 2010 11:25 PM
To: Paul Amendola
Cc: dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] Question about Data Completeness
Indeed, a topic dear to my heart and one that we have spent some time
working on.
In side are both SQL as well as BIRT reports that may give you, after
modification, what you want.
Best regards,
Jason
On Tue, Jan 26, 2010 at 12:35 AM, Paul Amendola > <Paul.Amendola@theirc.org> wrote:
When report tables are generated, the tables are populated with a zero,
which makes it difficult to determine if the user had entered a zero into
the database or left the data element blank. Is there a report that can be
generated within DHIS that could be used to analyze data completeness by
data element, instead of by report?
Also note that there is built in functionality in DHIS to create completeness reports based on the subjective option to set every data entry to complete or not (there is a “Set as complete” button on the bottom of each form). Under Reports there is a section on Completeness where you can get reports based on this. I am not familiar with how this works in detail though. Maybe Edem, Romain or Johan who have used this functionality in Sierra Leone could explain? Or Lars Helge of course…
We’ve also had discussions and suggestions on more objective completeness functionality, e.g. per data element, per data element group or per “set of mandatory data elements”.
Not sure what the status is on that right now. Maybe Lars could fill in.
Ola Hodne Titlestad |Technical Officer|
Health Metrics Network (HMN) | World Health Organization
Avenue Appia 20 |1211 Geneva 27, Switzerland | Email: titlestado@who.int|Tel: +41 788216897
Thank you for the response and for the reports. Do you know if this has been looked at in terms of exporting the report tables to Excel? When exported to excel, all of the data elements are zero (both true zeros and incomplete data).
Also note that there is built in functionality in DHIS to create completeness reports based on the subjective option to set every data entry to complete or not (there is a “Set as complete” button on the bottom of each form). Under Reports there is a section on Completeness where you can get reports based on this. I am not familiar with how this works in detail though. Maybe Edem, Romain or Johan who have used this functionality in Sierra Leone could explain? Or Lars Helge of course…
One can browse completeness (based on which datasets are marked as complete as Ola says) by dataset or organisation unit under “Data Completeness” in the reporting module.
We also have a report table variant for the mentioned completeness data, go to “Report table” and select “New DataSet table”.
We’ve also had discussions and suggestions on more objective completeness functionality, e.g. per data element, per data element group or per “set of mandatory data elements”.
Not sure what the status is on that right now. Maybe Lars could fill in.
This is on the roadmap for the next release - 2.0.4.
Lars
···
On Tue, Jan 26, 2010 at 5:30 PM, Ola Hodne Titlestad olatitle@gmail.com wrote: