Indicator Mapping and Submission

Shayna Padovano -

Indicator Mapping Instructions

The process of indicator mapping is crucial for the harmonization of data between MoH and PEPFAR for the Data Alignment activity.  It will be used to identify the indicator and data element from one system that precisely matches the definition of an indicator and data element in another.  This document defines the procedures for conducting the indicator mapping exercise using the provided template, 'IndicatorMapping.csv'

To begin, you must have the following:

  1. The ‘IndicatorMapping.csv’ template
  2. The Data Alignment indicator list and definitions
  3. A list of the relevant/equivalent MoH indicators and disaggregations


Indicator Mapping

In order to map data elements from two disparate systems, they must agree on the indicator and disaggregation definition.  In an ideal scenario, the mapping will consist of a one-to-one link, where the MoH and PEPFAR data elements are an exact match:

I.e. MoH’s [CurrentOnTreatment <15] = PEPFAR’s [TX_CURR <15]

Note that the level at which the data is aggregated must also match.  For this activity we only focus on facility level results.  Data elements that collect aggregated data at higher geographic levels (anything above the facility level) cannot be mapped.


Using the Indicator Mapping Template

The template is a comma-separated values (CSV) file consisting of five fields or columns.  It is recommended to open and edit the file using MS Excel, as this will provide a simple table layout for entry.



Upon opening the template, you will see that the first two Column A ‘DATIM_IndicatorCode’ and Column B ‘DATIM_Disag’, contain the list of Data Alignment indicators and disaggregations as they have been defined in DATIM.  These should not be altered. 

MoH Fields

Column C ‘MOH_IndicatorCode’ and Column D ‘MOH_Disag’ are where the MoH equivalent data elements will be entered (see Table 1Yellow cells).  Coding and naming conventions will vary depending on the how this has been established in country or the information system in use.  If the MoH uses DHIS2 as their central repository, then they will likely also use an Indicator and Disag identification structure to uniquely identify their data elements.  Some countries may have a single code to uniquely identify each indicator and disaggregation, rather than the combination of the two.  In this case you will simply put this unique code in column C (MOH_IndicatorCode), and leave column D (MOH_Disag) blank. 

Table 1

Note: The values provided under Columns C & D must be the precise codes as used by the MoH.  These values will be used in DATIM to align the final MoH ‘Results File’ once completed.  Any deviation among the codes will cause errors and inability to align indicators.

Calculation Field

Column E ‘Calculation’ field is used if needing to perform a calculation on the MoH disaggregations in order to equate to one of the DATIM disaggregations.  For example, if the MoH collects different age bands that could be summed to align with <15 or 15+, then this column would be used to define that formula. 

I.e. [Age 0-5] + [Age 6-15] = [Age <15]

Taking this example further, one can see how this would be presented in the mapping template in ‘table 2’ below.  There are three components to note:

  1. Even though the MoH does not have an equivalent code for ‘less than 15’, one must be created and provided in the table (see Table 2Yellow cell).
  2. Defining a formula (see Table 2Orange cell)
    1. Square brackets “[ ]” are used to delimit indicator and disaggregation codes
    2. Indicator and Disaggregation are separated with a colon “:”
  3. The data elements that make up the formula must be independently defined as MoH indicators in the mapping (see Table 2Green cells).  You will notice that the DATIM Indicator and Disag columns must be blank when these are defined. 
Table 2


Note: The final MoH ‘Results File’ will not be expected to contain any of these calculated indicators, only the contributing data elements that are used to make up the formulas (i.e. the green cells from table 2).   The calculation will be conducted by the Transformation Team before being imported into DATIM.

Mapping Considerations

Care must be taken to ensure proper alignment of the definition between the indicators and their disaggregations.  Some Ministries of Health may not collect any or be able to align to the provided disaggregations, in which case only the total can be reported (numerator).  The HTS and PMTCT indicators each include a ‘totals’ field.  The TX indicators, with their Age and Sex cross-disaggregation also allows one to map to a total by using the combined ‘AgeUnknown | SexUnknown’ disaggregation.

The disaggregations are summed to equate to the total of the indicator.  If the Ministry of Health collects age and sex, but independent of each other, then it is recommended to report the one that is generally considered to be more accurate, as reporting both would result in double counting.

Submitting the Indicator Mapping Template

After the mapping has been completed, save the file and name it prefixed with your country (i.e. [Country]_IndicatorMapping.csv).Then, import into your country’s designated folder within PEPFAR SharePoint (https://www.pepfar.net) under the MoH-PEPFAR Data Alignment Team Site. More information about how to use this site will be available soon. Note that individuals who must submit these files will require PEPFAR SharePoint accounts, which can be requested from the PEPFAR SharePoint welcome page. This site is also best accessed using Internet Explorer.

See the "SharePoint_Submission_Guide.pdf" below for more details.


The indicator mapping template described above is provided as an Excel file below so you can download it for your team's use.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk