Purpose
This article provides guidance on DATIM concepts, outlining requirements for importing data into DATIM, ensuring compatibility and alignment with system and program needs.
DATIM Concepts
Data intended for import into DATIM must satisfy strict requirements with respect to the format of the data as well the relationship of the data to the current metadata within the system.
- Current Code List: The code lists provides the identifier to be used in the data exchange files i.e. the Codes and UIDs code for MER data elements, Disaggregates/Category Option Combos, Mechanisms and Organization Unit. In addition they contain common names and codes for data elements (Indicators & Disaggregates) and data sets (forms).
- Note: Code lists are Not open to the public i.e. you will need a DATIM account to access them
- Data Exchange Guidance: This section provides instructions and useful resources necessary for performing MER data exchange with DATIM.
Additional Resources: Other useful DATIM and DHIS2 links and resources are provided in this section.
Metadata dimensions
Data must be valid with respect to the destination sites, periods, indicators, disaggregation and mechanisms, therefore all data values must be associated with four metadata dimensions which describe different aspects of the data namely:
-
-
Where - Organization Unit: This dimension describes the location of the data i.e. where the data is captured.
- Example: Clinical Facility, Community Site, or OU Level
- What - Data element (Indicator) + Disaggregation: This dimension describes the phenomena which the data value is attached to, such as the Number of HTC tests for Females 1-4. In this case the data element has a disaggregation of Female 1-4. Data elements in DATIM typically have many different disaggregations with respect to age and sex. In addition to that, different classes of data elements such as Targets and Results and DSD and TA exist.
-
When - Period: This dimension describes the time period of the data being reported.
- Example: January through March 2016 or April through June 2016
- Who - Funding mechanism: Also known as the “attribute option combination” this is an extra custom dimension in DATIM, which describes which implementing mechanism the data is being reported for and refers to the FACTS Info funding mechanism ID.
-
Where - Organization Unit: This dimension describes the location of the data i.e. where the data is captured.
Format
Data intended for import into DATIM must also satisfy strict requirements with respect to the format i.e. valid types of data (integers, options, etc.)
The data formats are generic DHIS2 formats which have been mapped to PEPFAR specific concepts in DATIM. The elements in the formats are described in the following.
|
DHIS2 concept |
PEPFAR concept |
Description | Format |
|---|---|---|---|
| Data element | Indicator | Data item being captured. In PEPFAR terms referred to as indicator. Example is "Number of adults and children currently receiving antiretroviral therapy (ART)." | Data elements can be reported either using Codes or UIDs (refer to Current Code List contained in this online guide for specific Codes and UIDs). |
| Period | Period | The time period for which the data is captured. DATIM uses the ISO standard format for designating reporting periods. All periods in DATIM data exchange files must provide a valid period identifier. Specifically, DATIM uses PEPFAR Quarters for MER Results and Financial Year October for COP targets. |
For further information, you can view the DHIS2 documentation here. |
| Org unit | Facility / Site / Community / OU | Organizational unit for the data. Examples are site, district and country. Not to be confused with PEPFAR OU. Would typically be the site where the data is captured. | Facility, Site, Community and OU codes and UIDs are available in the Current Code List contained in this online guide. |
| Category option combo | Disaggregation | The disaggregation of an indicator/data element. Example is "Female, Under 5." | For the Disaggregation/ Category option combo Codes or UIDs refer to the Current Code List contained in this online guide for specific Codes and UIDs). |
| Attribute option combo | Funding mechanism | Funding mechanism for which the data applies. Example is "25147". Refers to the FACTS info mechanism ID. | The appropriate funding mechanism Code or UID should be reported (refer to Current Code List contained in this online guide for specific Codes and UIDs) |
| Value | Data value | This is the data value being reported. | An example data value is "45." |
Back to the top.
Current Code Lists
Data Elements
| Fiscal Year (Version) | Type | Data Set | HTML | JSON | CSV |
|---|---|---|---|---|---|
| FY26 (MER 2.8.2) | Results | MER Results: Community Based | HTML | JSON | CSV |
| MER Results: Facility Based | HTML | JSON | CSV | ||
| Host Country Results: DREAMS (USG) | HTML | JSON | CSV | ||
| Host Country Results: Operating Unit Level (USG) | HTML | JSON | CSV | ||
| Host Country Results: COP Prioritization SNU (USG) | HTML | JSON | CSV |
Mechanism
Org Units
Click this link to view and download your Org Unit code list
Data Exchange Guidance
| April 22, 2024 | MER | This guide will provide guidance to Data for Accountability, Transparency and Impact Monitoring (DATIM) data importers and explain key concepts in more detail including how to construct an appropriately formatted file for import as well as a graphical representation of the steps necessary to perform a successful MER data import into DATIM. |
Back to top
Additional Resources
- Validation App (https://apps.datim.org/validation) - This is the validation App, which is used to ensure data in the import file conform to all the necessary standards, the applicable dataset as well as data validation checks across indicators.
- Dev-de (dev-de.datim.org) - This is a dedicated server and a copy of the actual DATIM production system that can be used for final testing of your import file. It is strictly a testing environment that can be used to test data import files prior to submission for import into the actual production system, without affecting the data stored in production.
- DATIM (datim.org) - This is the live production server of DATIM. Once data have been submitted and sucessfully imported, you can verify the import here.
Support
For questions or issues related to data exchange please submit a help desk ticket at the help desk.
Back to top.
Comments