Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


4U Nodes supported in OUs manage (Operating Units)  manage their own site list.  The 4U site list will contain all sites that the node needs to use in PEPFAR reporting.  In addition, the 4U instance site list may contain sites that are used for other business or reporting needs.  PEPFAR subscribes to the OU node's lists list and provides a unique PEPFAR ID that allows a 4U instance to map this metadata element to a site record.  That allows a 4U instance to communicate a PEPFAR ID back to PEPFAR at the time of reporting.  

When new Site data is entered into a 4U site list, the system will do a search to determine if that site already exists in the 4U site list.   If the site does not exist, the 4U user can decide to add the site.  

PEPFAR will subscribe to the site list of specific 4U nodes.  When PEPFAR receives an new site from a 4U instance, they will:  

  1.  Determine if the site is a PEPFAR reporting site
    1. No - Stop
    2. Yes - Determine if the site is already in the PEPFAR site list 
      1. No - Add site and PEPFAR site id 
      2. Yes - ???

What does PEPFAR do when there is an update to a site?  

Note:  For sites 4U instances that are not ready to physically support site management, the sites can continue to be managed by OU personnel in the PEPFAR repository.  



Step 7 - Import the PEPFAR IDs into 4U DHIS2 

We may or may not need to do this step.  It depends upon the strategy we use to import the desired mechanism data.  If we only need the site name to import mechanism data, then we do not need this step.  Jim will need to help us understand the options for keeping mechanism data aligned.  

We also need to be careful that importing the ids is not a change that will kick off the update cycle with global again. We want to make sure we don't get into an endless loop of transmitting the same records.  

Step 8 - Translate the ADX message 4U IDs to PEPFAR IDs

An OpenHim mediator has been designed to read any outgoing ADX message on the node and check to make sure that any 4U site IDs in the message are translated to PEPFAR site IDs.  

Workflow  - Export Aggregate Data - V1.5