Data entry with DHIS2

+ Data entry +

Learning Objectives - After reading this chapter you will be able to understand: - - - How to do data entry - - - How to do data validation - - - How to use standard and customised data entry screens - - + After reading this chapter you will be able to understand: + + + How to do data entry + + + How to do data validation + + + How to use standard and customised data entry screens + +

- Opening the “Data Entry” screen - Entering data in DHIS 2 is a very simple task, and involves the +

+ Data entry with DHIS 2 + The data entry module is where data is manually registered in the DHIS 2 database. +

+ Opening the “Data Entry” screen + Entering data in DHIS 2 is a very simple task, and involves the following steps. Click on the services tab displayed on the main menu. A drop down menu will appear listing the services provided by DHIS2. Click on the Data Entry option. - - Open DHIS2 data entry screen - - - - - - - You will now enter the data entry module. This module is where the + + Open DHIS2 data entry screen + + + + + + + You will now enter the data entry module. This module is where the services/ data values are captured / registered into the system. The screen display will be like the screen-shot shown below. - - Main data entry screen - - - - - - -

- Navigate organisation tree and select organisation unit - In order to enter data you will first have to select the particular + + Main data entry screen + + + + + + +

+ Navigate organisation tree and select organisation unit + In order to enter data you will first have to select the particular organisation unit (e.g. Sub Centre/PHC/districts etc) for which you are going to enter data. Simply clicking on the concerned organisation unit from the organisation units hierarchy displayed on the left side of the data entry screen. - - Select Organisational unit - - - - - - -

- Entering data - When you select an organisational unit (or orgunit) from the + + Select Organisational unit + + + + + + +

+ Entering data + When you select an organisational unit (or orgunit) from the organisation unit tree, datasets available for this orgunit will then appear as a drop-down list in the data set box as depicted below. - - Select dataset - - - - - - - If the dataset field is disabled it means that there are no datasets + + Select dataset + + + + + + + If the dataset field is disabled it means that there are no datasets assigned for the selected organisation unit or that your user role is not authorised to enter data. For now we shall limit our concern to data entry. You will learn to create and assign datasets to specific organisation unit in a later module. +

=== modified file 'src/docbkx/en/dhis2_user_man_import_export.xml' --- src/docbkx/en/dhis2_user_man_import_export.xml 2010-02-18 18:52:03 +0000 +++ src/docbkx/en/dhis2_user_man_import_export.xml 2010-02-27 21:19:09 +0000 @@ -1,7 +1,7 @@ - + - Import and export of data with DHIS2 + Import and export Learning objectives: @@ -25,7 +25,7 @@ In a primary health system, the HMIS typically involves a distributed application, where the same application is running in different geographical locations (PHCs,CHCs, hospitals, districts, and state). Most of these physical locations do not have Internet connectivity, and hence they work offline. At some point (normally at the district level), the data needs to be synchronised in order to have a consolidated database for the a particular geographical region. For this, it is important to be able to export data from one location (which is working offline, say at the health facility level) to another one say at the district level where the data would need to be imported. This feature of exporting and importing is thus a crucial function of a HMIS. This feature also helps us overcome the dependency on Internet to some degree, as data updates can be transferred via USB key where there is no connectivity, or through email where there is limited Internet connectivity. DHIS 2 provides robust export-import functionality to fulfil these needs.

Exporting data In the case on on-line data entry, all data is saved into one database only. In an offline deployment, each deployment will have a separate database in their local system. So the data will be stored in their local database. In an offline deployment, after the data entry is finished, it will need to be manually sent to the next level of where the application is running. In an on-line application, however, that is not required, as all data is stored at a central location using the Internet. @@ -44,6 +44,7 @@ The exported data values are stored in an ‘xml file’. The file name is defined by the name of the source organisation unit and the period to allow the receiving organisation unit to identify the source and the period of the export file. The XML is placed in your home directory (On Windows this is normally C:\Documents and Settings\ under the sub-directories /dhis / import-export. +

Exporting data to other DHIS2 systems Once the data export screen is displayed, select the Organisation unit, period and dataset for which data export should be selected.Finally click on the export option that will be available on the lower left side of displayed screen. @@ -94,7 +95,7 @@

IXF data export - DHIS2 support export to the Indicator Exchange Format 2 developed by UNAIDS. The IXF data exchange standard has been implemented ,with various levels of compatibility, between several information management systems including CRIS version 2, DevInfo version 5, KIDS developed by FAO, DHIS 1.4, DHIS2, and HealthMapper version 4 developed by WHO. A more detailed discussion on the use of the IXF data exchange format is discussed in depth here. + DHIS2 support export to the Indicator Exchange Format 2 developed by UNAIDS. The IXF data exchange standard has been implemented ,with various levels of compatibility, between several information management systems including CRIS version 2, DevInfo version 5, KIDS developed by FAO, DHIS 1.4, DHIS2, and HealthMapper version 4 developed by WHO. A more detailed discussion on the use of the IXF data exchange format. The IXF data export is essentially the same as a standard DHIS 2 DXF export, but results in a file format that is compatible with IXF 2.

@@ -114,6 +115,20 @@ Auctor natoque ve vulputate quam. Quam duis posuere risus felis mus class tempor eu sociosqu. Risus duis penatibus turpis, tristique dictum enim est. Quisque mi pulvinar ultrices, fusce diam porttitor mi hendrerit viverra, augue leo vestibulum rutrum. Ridiculus dictumst luctus. Eros.

+ Importing data +

+ DXF Import + The Data Exchange Format (DXF) is the default XML schema that is used to transport data between two disconnected DHIS2 systems. Importing data from another DHIS2 system is simple. Just select "Services->Import-Export-Import". Click the "Browse" button, and select the name of the file that you wish to import as shown below. + + Default import screen + + + + + + +

Importing data The import option allows different instance of DHIS2 to receive standardised set of data in the absence of a networked system. Typically, a data set is exported from one DHIS instance (e.g. a district level system) to another system (e.g. a provincial level system). DHIS2 is capable of importing data from other systems that either support the DXF of IXF formats. DHIS2 is capable of importing data directly from a DHIS 1.4 Access database. Each of these options will be discussed in the following sections. @@ -123,44 +138,18 @@ Data can be imported into different instances of DHIS2 through the use of the DXF data exchange format. There are two screens that are used to import data, with default and advanced options. The default data import menu can be accessed by clicking the "Import" from the main Import-Export screen. By clicking the "Browse" button, you can select a file from you local file system. This file may have been received by email, copied from another users system, or received on a CD for example. Simply select the file that you wish to import. There are three separate options for importing data. - - - <tgroup cols="2"> - <colspec colnum="1" colname="c0" colwidth="30"/> - <colspec colnum="2" colname="c1" colwidth="70"/> - <tbody> - <row> - <entry>Import</entry> - <entry>Odio sem. Nunc, aliquet quisque tempor enim pellentesque at sodales elit. </entry> - </row> - <row> - <entry>Preview</entry> - <entry>Faucibus aenean. Ligula porta congue mattis quis in bibendum quisque. </entry> - </row> - <row> - <entry>Analysis</entry> - <entry>Donec. Arcu felis taciti tempus aliquam ve, lectus.</entry> - </row> - </tbody> - </tgroup> - </table> + <itemizedlist> + <listitem> + <para>Import: This option will import the contents of the import file directly into the database.</para> + </listitem> + <listitem> + <para>Preview: This option will enable a preview of the contents of the import file. In the preview one can get an overwiev of the data to be imported, discard unwanted elements and match import elements to existing ones.</para> + </listitem> + <listitem> + <para>Analysis: This option will enable an analysis of the contents of the import file. The analysis will search for and examine anomalies in the data, like violations of unique names constraints and invalid indicator formulas. This is useful when importing from external applications where data constraints might be less rigid than in DHIS 2.</para> + </listitem> + </itemizedlist> </section> </section> </section> - <section> - <title>Importing data -

- DXF Import - The Data Exchange Format (DXF) is the default XML schema that is used to transport data between two disconnected DHIS2 systems. Importing data from another DHIS2 system is simple. Just select "Services->Import-Export-Import". Click the "Browse" button, and select the name of the file that you wish to import as shown below. - - Default import screen - - - - - - - -

- === modified file 'src/docbkx/en/dhis2_user_man_reporting.xml' --- src/docbkx/en/dhis2_user_man_reporting.xml 2010-02-18 18:52:03 +0000 +++ src/docbkx/en/dhis2_user_man_reporting.xml 2010-02-27 21:19:09 +0000 @@ -1,4 +1,4 @@ - + Reporting @@ -96,7 +96,8 @@

Reports -

+ The reporting module in DHIS 2 provides a range of reporting alternatives, including canned reports using either JasperReports or BIRT, data set reports, charts, pivot tables and report tables. +

Report tables Report tables are meant to be database tables fulfilling the specific data needs of a report, chart, pivot table or other output format. It can be understood as a mini datamart that contains only the data needed for its purpose (the report). The rationale behind this concept is to automatically provide the data sources for reports without bothering the users every time, like a normal datamart, and to speed up the data processing and aggregation (small targeted datamarts are obviously faster than big ones). @@ -124,7 +125,7 @@ BIRT reports

Create a report table in DHIS 2 - - create a report table in DHIS 2 is to create so-called report tables in DHIS, found under Reports module, which will serve as the data table for your report. Normally one table per report, but multiple tables for one report is also possible. A report table can be a cross tabulated table on any of the dimensions period/indicator/data element / orgunit, and also in combination, like “BCG < 1 coverage + last 3 months” and “BCG coverage < 1 year+ last month”. This cross-tabulation makes it a lot easier to control the design of the report which is then done with dragging and dropping column headings onto the report. The report table can also have report parameters like reporting month, organisation unit and organisation unit parent (if you are e.g. listing all sub-districts in a given district). + To create a report table in DHIS 2 is to create so-called report tables in DHIS, found under Reports module, which will serve as the data table for your report. Normally one table per report, but multiple tables for one report is also possible. A report table can be a cross tabulated table on any of the dimensions period/indicator/data element / orgunit, and also in combination, like “BCG < 1 coverage + last 3 months” and “BCG coverage < 1 year+ last month”. This cross-tabulation makes it a lot easier to control the design of the report which is then done with dragging and dropping column headings onto the report. The report table can also have report parameters like reporting month, organisation unit and organisation unit parent (if you are e.g. listing all sub-districts in a given district).

Design the report in BIRT