OHIE > Metadata > DATIM

DATIM Data Import and Exchange Resources

Purpose

This online guide provides resources and describes procedures necessary for importing and submitting data into DATIM.

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 of 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 (Results and Targets/COP), SIMS 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).
* These code lists are open to the public i.e. you do not need a DATIM log in to access them
  • Data Exchange Guidance: This section provides instructions and useful resources necessary for performing MER and SIMS data exchange with DATIM.
  • Other 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 gender. 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.

Back to the top.

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 “10.1 Post-Violence Care Score”. 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 DHIS2 internal date format for designating reporting periods. All periods in DATIM data exchange files must provide a valid DHIS2 period identifier. In particular, DATIM uses Financial Year October for COP targets, PEPFAR Quarters for MER Results, and Days for SIMS reporting.
  • Days: use yyyyMMdd e.g. 20160101 for January 01, 2016
  • PEPFAR Quarters: use yyyyQn e.g. 2016Q1 for PEPFAR FY16Q2 i.e.  January – March 2016
  • Financial Year October: use yyyyOct e.g.2016Oct for October 2016 – September 2017
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”.
Comment Data comment This is a comment associated with the data value. An example comment is “Needs follow-up”.

Back to the top.

Current Code List

Data Elements *

* These code lists are open to the public i.e. you do not need a DATIM log in to access them
Year/
Version
Type Data Set HTML JSON CSV XML
COP16
(FY17Q4)
Results Facility Based Code List HTML JSON CSV XML
Community Based Code List HTML JSON CSV XML
Facility Based – DoD ONLY Code List HTML JSON CSV XML
Community Based – DoD ONLY Code List HTML JSON CSV XML
Medical Store HTML JSON CSV XML
Narratives (IM) HTML JSON CSV XML
Operating Unit Level (IM) HTML JSON CSV XML
Host Country Results: Narratives (USG) HTML JSON CSV XML
Host Country Results: Operating Unit Level (USG) HTML JSON CSV XML
Host Country Results: COP Prioritization SNU (USG) HTML JSON CSV XML
COP16
(FY17Q2)
Results Facility Based Code List HTML JSON CSV XML
Community Based Code List HTML JSON CSV XML
Facility Based – DoD ONLY Code List HTML JSON CSV XML
Community Based – DoD ONLY Code List HTML JSON CSV XML
Medical Store HTML JSON CSV XML
Narratives (IM) HTML JSON CSV XML
Operating Unit Level (IM) HTML JSON CSV XML
Host Country Results: Narratives (USG) HTML JSON CSV XML
COP16
(FY17Q1)
Results Facility Based Code List HTML JSON CSV XML
Community Based Code List HTML JSON CSV XML
Facility Based – DoD ONLY Code List HTML JSON CSV XML
Community Based – DoD ONLY Code List HTML JSON CSV XML
Medical Store HTML JSON CSV XML
Narratives (IM) HTML JSON CSV XML
Operating Unit Level (IM) HTML JSON CSV XML
Host Country Results: Narratives (USG) HTML JSON CSV XML
Host Country Results: Operating Unit Level (USG) HTML JSON CSV XML
Host Country Results: COP Prioritization SNU (USG) HTML JSON CSV XML
COP17
(FY18)
Target Facility Based Code List HTML JSON CSV XML
Community Based Code List HTML JSON CSV XML
Facility Based – DoD ONLY Code List HTML JSON CSV XML
Community Based – DoD ONLY Code List HTML JSON CSV XML
Narratives (IM) Code List HTML JSON CSV XML
Operating Unit Level (IM) Code List HTML JSON CSV XML
Host Country Operating Unit Level (USG) Code HTML JSON CSV XML
Planning Attributes: COP Prioritization National HTML JSON CSV XML
Planning Attributes: COP Prioritization SNU HTML JSON CSV XML
Medical Store HTML JSON CSV XML
Host Country COP Prioritization SNU (USG) HTML JSON CSV XML
SIMS 3.0* SIMS Facility Based Code List HTML  JSON CSV XML  
Community Based Code List HTML JSON   CSV XML  
Above Site Based Code List HTML  JSON  CSV XML 
SIMS v2 Option Sets HTML JSON CSV XML
  Tiered Site Support Tiered Site Support Data Elements HTML JSON CSV XML
Tiered Site Support Option Set List HTML JSON CSV XML

Back to the top.

Mechanism *

* These code lists are open to the public i.e. you do not need a DATIM log in to access them
Concepts HTML JSON CSV XML
Mechanism Attribute Combo Option UIDs HTML JSON CSV XML

Back to the top.

Need help with DATIM Metadata? Contact support@ohie.org