Master Data Management SOP

Sources of master data

  1. Master data for Tete for the group 4 campaign. Master data would be campaign-specific as village boundaries and user lists will change from campaign to campaign.

  2. Master data imported from DHIS2. This would be for the other two provinces and used for dashboard visualisation.

Types of Master Data

Type of master data in DIGIT

Frequency of change/update

Shared between

Equivalent in DHIS2

Typical time taken to upload in the system

Boundary hierarchy

Fixed for a campaign

CHAI programme- eGov impel


Boundary data specs (boundary names, total households, campaign dates for the boundary, etc.).

Note: No deletions after the campaign begins. Updation is allowed in worst-case scenario.

Changeable. The village list may change right upto the campaign (that is, the start of distribution).

CHAI programme- eGov impel


System users

Local monitors-Changeable


Warehouse managers- Changeable

Supervisors (District and provincial and National)- Fixed.

CHAI programme- eGov impel


Facility (Warehouses-Community , District, provincial and national)

Fixed for a campaign

(To be checked with CHAI).

CHAI programme- eGov impel


Product (Type , variant, SKUs, etc.)

Fixed for a campaign.

CHAI programme- eGov impel

Not available


Role-action mapping

Campaign setup

Delivery procedure-1 bed net for 2 individuals to a maximum of 3 bed nets per household

Fixed for a campaign.

Registration procedure-

Do we want to limit the numbers of households in a household?

Fixed for a campaign.

Master Data Collection template

Click here to view the details.

Master Data review process and Upload process

1. Finalise the data gathering template.

2. Sharing templates with CHAI and having a run-through.

3. Have an agreement with CHAI on the lead time for sharing the data.

4. CHAI to review the data internally before sharing it back with eGov. We are expecting the data to be in Portuguese.

5. Store all the data in appropriate shared folders.

6. Abhishek or Naved to review the data shared and approve if all required values are present.

7. If there are mistakes, duplicates, missing fields, etc., mark them and share it back with CHAI.

8. Once the approved data is ready, this has to be shared with the implementation engineers for loading to development.

9. Use the data load utility (if ready) or load manually.

10. Verify the application using the new data.

Master data upload process

Handling DHIS2 master data updation:

  1. How is master data updation handled in DHIS2 application?

  2. How does CHAI get to know that a certain master data has been changed/updated, and typically, how much time will be available to update it in the HCM application?

  3. Master data received from CHAI would be in Portuguese? It is understood that eGov will not be able to do any validation on accuracy of this.

  4. Will the help desk play any role in master data updation or communicating the changes to eGov?

  5. When the master data update/change happens, how do the devices get re-provisioned with the latest set of master data (in case of DHIS2)? Will eGov-CHAI need to draft a strategy around this?

  6. Can we arrive at default values for missing master data in agreement with CHAI?