dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #04388
[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 96: Merged what I wrote about data quality with the existing text
------------------------------------------------------------
revno: 96
committer: Lars Helge Oeverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Thu 2010-02-18 18:19:53 +0100
message:
Merged what I wrote about data quality with the existing text
removed:
src/docbkx/en/dhis2_user_man_mod4.xml
modified:
src/docbkx/en/dhis2_user_man_data_quality.xml
src/docbkx/en/dhis2_user_manual_en.xml
--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs
Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription.
=== modified file 'src/docbkx/en/dhis2_user_man_data_quality.xml'
--- src/docbkx/en/dhis2_user_man_data_quality.xml 2010-02-17 19:38:33 +0000
+++ src/docbkx/en/dhis2_user_man_data_quality.xml 2010-02-18 17:19:53 +0000
@@ -3,6 +3,80 @@
<chapter>
<title>Data Quality</title>
<para>The data quality module provides means to improve the quality of the data in the system. This can be done through validation rules and various statistical checks.</para>
+ <section>
+ <title>Learning Objectives</title>
+ <para>After reading this module you will be able to understand:</para>
+ <highlights>
+ <orderedlist>
+ <listitem>
+ <para>What is data quality and its importance for HMIS.</para>
+ </listitem>
+ <listitem>
+ <para>How to do data quality check at point of data entry.</para>
+ </listitem>
+ <listitem>
+ <para>How to create data validation rules.</para>
+ </listitem>
+ <listitem>
+ <para>How to carry out data triangulation.</para>
+ </listitem>
+ <listitem>
+ <para>How to analyze data status.</para>
+ </listitem>
+ </orderedlist>
+ </highlights>
+ </section>
+ <section>
+ <title>Overview of data quality check</title>
+ <para>Ensuring data quality is a key concern in building an effective HMIS. Data quality has different dimensions including:</para>
+ <highlights>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Correctness:</emphasis> Data should be within the normal range for data collected at that facility. There should be no gross discrepancies when compared with data from related data elements.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Completeness:</emphasis> Data for all data elements for all health facilities/blocks/Taluka/districts should have been submitted.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Consistency:</emphasis> Data should be consistent with data entered during earlier months and years while allowing for changes with reorganization, increased work load, etc. and consistent with other similar facilities.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Timeliness:</emphasis> All data from all health facilities/blocks/Taluka/districts should be submitted at the appointed time.</para>
+ </listitem>
+ </itemizedlist>
+ </highlights>
+ </section>
+ <section>
+ <title>Data quality checks</title>
+ <para>Data quality checking can be done through various means, including:</para>
+ <orderedlist>
+ <listitem>
+ <para>At point of data entry, the software can check the data entered to see if it falls within the min-max ranges of that data element over the last six months or as defined by the user.</para>
+ </listitem>
+ <listitem>
+ <para>Defining various validation rules, which can be run once the user has finished data entry. The user can also check the entered data for a particular period and Organization Unit(s) against the validation rules, and display the violations for these validation rules. </para>
+ </listitem>
+ <listitem>
+ <para>Analysis of data sets, ie. examining gaps in data.</para>
+ </listitem>
+ <listitem>
+ <para>Data triangulation which is comparing the same data or indicator from different sources.</para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section>
+ <title>Data quality check at the point of data entry </title>
+ <para>Data quality can be checked at the point of data entry through setting the minimum and maximum value range for each element manually or generating the min-max values using the DHIS 2 if there is historical data available for that data element.
+ </para>
+ <section>
+ <title>Setting the minimum and maximum value range manually </title>
+ <para>If you are using the default entry screen click on the element for which you want to set the min-max value. A pop-up window will appear in which you can enter the vaules. On subsequent data entry if the value entered does not fall within the set min-max range the text box will change colour to red. The user will also get a pop-up as shown below. This change in colour is a prompt to check the data entered and make necessary correction. On the data entry screen the users also have the option to add a comment on how the discrepant figure might be explained (if required). This you can do by using the drop down menu of the ‘comment’ box. In case you are using the custom data entry screen which is displayed when you deselect the ‘default data entry form’ option on the top right corner of the screen. In this case the minimum and maximum values can be added by double-clicking on the data entry box instead of the data element.</para>
+ </section>
+ <section>
+ <title>Generated min-max values </title>
+ <para>It is possible to generate the min-max value, element-wise, using the DHIS2. In such case you merely need to click on the ‘Generate min-max’ button near the upper right corner. In case of default data entry screen the min and max values, when generated, will appear on the left and right side of the data entry box. In case you deselect the default data entry form the generated values will appear on the top right end of the screen.</para>
+ </section>
+ </section>
<section id="validationRule">
<title>Validation Rule</title>
<para>This module provides management of validation rules. A validation rule is based on an expression which defines a relationship between a number of data elements. The expression has a left side and a right side and an operator which defines whether the former must be less than, equal to or greater than the latter. The expression forms a condition which should assert that certain logical criterias are met. For instance, a validation rule could assert that the total number of vaccines given to infants is less than or equal to the total number of infants.</para>
@@ -32,10 +106,10 @@
<title>Min-Max Outlier Analysis</title>
<para>The min-max value based outlier analysis provides a mechanism for revealing values that are outside the defined minimum and maximum values. Minimum and maximum values can be custom defined or automatically defined by the system in the data entry module. See section about Std dev outlier analysis for further details on usage.</para>
</section>
- <section>
- <title>Gap Analysis</title>
- <para>The gap analysis provides a mechanism for revealing gaps in the data. A gap exists in the context of a data element and organisation unit. A gap is defined as a period with preceding and succeeding periods which have registered data values, but without registered data values itself. Such a gap might indicate a data capture error or omission and could be further investigated. See section about Std dev outlier analysis for further details on usage.</para>
- </section>
+ <section>
+ <title>Gap Analysis</title>
+ <para>The gap analysis provides a mechanism for revealing gaps in the data. A gap exists in the context of a data element and organisation unit. A gap is defined as a period with preceding and succeeding periods which have registered data values, but without registered data values itself. Such a gap might indicate a data capture error or omission and could be further investigated. See section about Std dev outlier analysis for further details on usage.</para>
+ </section>
<section>
<title>Follow-Up Analysis</title>
<para>The follow-up analysis function will list all data values which are marked for follup-up. A data value can be marked for follow-up in the data entry module and in the other validation analysis variants in this module. See section about Std dev outlier analysis for further details on usage.</para>
=== removed file 'src/docbkx/en/dhis2_user_man_mod4.xml'
--- src/docbkx/en/dhis2_user_man_mod4.xml 2010-01-18 15:58:42 +0000
+++ src/docbkx/en/dhis2_user_man_mod4.xml 1970-01-01 00:00:00 +0000
@@ -1,213 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. --><!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; []>
-<article>
- <articleinfo>
- <date>2009-11-15</date>
- <title>Data Quality and Validation</title>
- <author>
- <surname>Unknown</surname>
- <affiliation>
- <orgname/>
- </affiliation>
- </author>
- <revhistory>
- <revision>
- <revnumber>1</revnumber>
- <date>2009-11-15</date>
- <authorinitials>KNS</authorinitials>
- <revdescription>
- <para>Initial conversion from MS Word format to DocBook</para>
- </revdescription>
- </revision>
- </revhistory>
- </articleinfo>
- <sect1>
- <title>Learning objectives:</title>
- <para>After reading this module you will be able to understand:</para>
- <highlights>
- <orderedlist>
- <listitem>
- <para>What is data quality and its importance for HMIS.</para>
- </listitem>
- <listitem>
- <para>How to do data quality check at point of data entry.</para>
- </listitem>
- <listitem>
- <para>How to create data validation rules.</para>
- </listitem>
- <listitem>
- <para>How to carry out data triangulation.</para>
- </listitem>
- <listitem>
- <para>How to analyze data status.</para>
- </listitem>
- </orderedlist>
- </highlights>
- <sect2>
- <title>Overview of data quality check</title>
- <highlights>
- <para>Ensuring data quality is a key concern in building an effective HMIS. Data quality has different dimensions including:</para>
- <itemizedlist>
- <listitem>
- <para><emphasis>Correctness:</emphasis> Data should be within the normal range for data collected at that facility. There should be no gross discrepancies when compared with data from related data elements.</para>
- </listitem>
- <listitem>
- <para><emphasis>Completeness:</emphasis> Data for all data elements for all health facilities/blocks/Taluka/districts should have been submitted.</para>
- </listitem>
- <listitem>
- <para><emphasis>Consistency:</emphasis> Data should be consistent with data entered during earlier months and years while allowing for changes with reorganization, increased work load, etc. and consistent with other similar facilities.</para>
- </listitem>
- <listitem>
- <para><emphasis>Timeliness:</emphasis> All data from all health facilities/blocks/Taluka/districts should be submitted at the appointed time.</para>
- </listitem>
- </itemizedlist>
- </highlights>
- <para>If we have poor quality data, we will have “garbage in and garbage out†situations. Use of poor quality data leads to ill informed decisions. So, the HMIS software should be built in with different tools to do data quality checks and validation.</para>
- <sect3>
- <title>Data quality checks</title>
- <para>Data quality checking can be done through various means, including:</para>
- <orderedlist>
- <listitem>
- <para>At point of data entry, the software can check the data entered to see if it falls within the min-max ranges of that data element over the last six months or as defined by the user.</para>
- </listitem>
- <listitem>
- <para>Defining various validation rules, which can be run once the user has finished data entry. The user can also check the entered data for a particular period and Organization Unit(s) against the validation rules, and display the violations for these validation rules. </para>
- </listitem>
- <listitem>
- <para>Analysis of data sets, IE, examining gaps in data.</para>
- </listitem>
- <listitem>
- <para>Data triangulation which is comparing the same data or indicator from different sources.</para>
- </listitem>
- </orderedlist>
- </sect3>
- </sect2>
- <sect2>
- <title>Data quality check at the point of data entry </title>
- <para>
- Data quality can be checked at the point of data entry through setting the minimum and maximum value range for each element manually or generating the min-max values using the DHIS 2 if there is historical data available for that data element.
- </para>
- <sect3>
- <title>Setting the minimum and maximum value range manually </title>
- <para>If you are using the default entry screen click on the element for which you want to set the min-max value, as shown below. </para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>A pop up window will appear as shown below. Here you can enter the min-max values.</para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>On subsequent data entry if the value entered does not fall within the set min-max range the text box will change colour to red. The user will also get a pop-up as shown below. This change in colour is a prompt to check the data entered and make necessary correction.</para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>On the data entry screen the users also have the option to add a comment on how the discrepant figure might be explained (if required). This you can do by using the drop down menu of the ‘comment’ box. </para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>In case you are using the custom data entry screen which is displayed when you deselect the ‘default data entry form’ option on the top right corner of the screen. In this case the minimum and maximum values can be added by double-clicking on the data entry box instead of the data element.</para>
- </sect3>
- <sect3>
- <title>Generated min-max values </title>
- <para>It is possible to generate the min-max value, element-wise, using the DHIS2. In such case you merely need to click on the ‘Generate min-max’ tab as shown below.</para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>In case of default data entry screen the min and max values, when generated, will appear on the left and right side of the data entry box. In case you deselect the default data entry form the generated values will appear on the top right end of the screen as shown in the following picture
-</para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </sect3>
- </sect2>
- <sect2>
- <title>Defining Validation Rules </title>
- <para>Validation rules are data quality check mechanism based on verification of the logic of relation between related data elements. Validation rules are relational expressions comprising of related data elements and an operator that states the expected / logical relation between the elements. For example number of infant deaths cannot be greater than the number of deliveries. As can be seen from the example a validation rule comprises of a left and a right side. On the left side of the expression, there must be a data element or a combination of data elements, and the same on the right side. The left and right hand sides of the expression are separated with a validation operator which states the relation between the elements. As validation rules have a relational property there must be at least two data elements for which the validation rules may be applied. </para>
- <figure>
- <title>The health information cycle </title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="/resources/images/dhis2UserManual/dhis2_information_cycle.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>DHIS 2 supports the different facets of the information cycle
- including:<itemizedlist>
- <listitem>
- <para>Collecting data.</para>
- </listitem>
- <listitem>
- <para>Running quality checks.</para>
- </listitem>
- <listitem>
- <para>Data access at multiple levels.</para>
- </listitem>
- <listitem>
- <para>Reporting.</para>
- </listitem>
- <listitem>
- <para>Making graphs and maps and other forms of analysis.</para>
- </listitem>
- <listitem>
- <para>Enabling comparison across time (for example, previous
- months) and space (for example, across facilities and
- districts).</para>
- </listitem>
- <listitem>
- <para>See trends (displaying data in time series to see their min
- and max levels).</para>
- </listitem>
- </itemizedlist></para>
- <para>As a first step, DHIS 2 serves as a data collection, recording and
- compilation tool, and all data (be it in numbers or text form) can be
- entered into it. Data entry can be done in lists of data elements or in
- customized user defined forms based on the paper forms. </para>
- <para>As a next step, DHIS 2 can be used to increase data quality.
- Firstly, at the point of data entry, a check can be made to see if data
- falls within acceptable range levels of minimum and maximum values for
- any particular data element. Such checking, for example, can help to
- identify typing errors at the time of data entry. Further, user can
- define various validation rules, and DHIS 2 can run the data through the
- validation rules to identify violations.</para>
- <para>When data has been entered and verified, DHIS 2 can help to make
- different kinds of reports. The first kind are the routine reports that
- can be predefined, so that all those reports that need to be routine
- generated can be done on a click of a button. Further, DHIS 2 can help
- in the generation of analytical reports through comparisons of for
- example indicators across facilities or over time. Graphs, maps, reports
- and health profiles are amongst the outputs that DHIS 2 can produce, and
- these should routinely be produced, analyzed, and acted upon by health
- managers.</para>
- </sect2>
- </sect1>
-</article>
=== modified file 'src/docbkx/en/dhis2_user_manual_en.xml'
--- src/docbkx/en/dhis2_user_manual_en.xml 2010-02-18 16:42:46 +0000
+++ src/docbkx/en/dhis2_user_manual_en.xml 2010-02-18 17:19:53 +0000
@@ -23,7 +23,6 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_data_administration.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_data_elements_and_indicators.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_data_quality.xml" encoding="UTF-8"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_mod4.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_import_export.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_reporting.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_user_man_gis.xml" encoding="UTF-8"/>
