title Node Requests Mechanism Update From Global DATIM

participant Global-IL
participant Node-IL
participant Node-ILR
Participant Node-HMIS

loop periodic refresh
Node-ILR->Node-IL: [1] Update Request
Node-IL->Global-IL: [2] Update Request
Global-IL->Node-IL: [3] Update Response
Node-IL->Node-ILR: [4] Update Response
Node-ILR->Node-HMIS: [5] Update Response

 

Questions to be answered:

1)  Where are associations between mechanisms, indicators and org units to be maintained? 
       There is no association being maintained at the DATIM Global level.  The association is modeled in CSD and will be accessible there, however it is unclear where the user interface to manage the association should exist.

The business process that needs to be supported:  

There is an agreement between the funders and Implementing Partner (IP) concerning the reporting requirements.  That agreement specifies the indicators for that mechanism.  

There can be communication from Donor to IP sometimes at the end of the period that specifies the indicators that should be collected under a specific mechanisms.  

OpenInfoMan should have that data at the country or the MOH instance so that it can be easily queried.

 NEW Functionality needed:  An interface is needed to support the association between mechanisms, indicators and org units.  The interface options:   

    1.  DHIS2 
    2.  OpenInfoMan

Notes:  

 

      • UI needs to be build in either DHIS 2 or in OpenInfoMan
      • OpenInfoman would perhaps be easier because it is a heavier lift in DHIS2 as it has no existing "mechanism-indicator-org unit" association.  
      • However, DHIS2 is maintaining the org unit and the indicator association so it makes sense from a user perspective to store it there
      • Note: even if the association is maintained/managed  in DHIS2, it will be exported and made query-able in OpenInfoMan

2)  How does the IP/MOH choose mechanisms are loaded into the DHIS 2 system?  

Business Process to be supported:  There may be many mechanisms, but you only want to load the funded mechanisms.  The ITI-73 query will return more mechanisms than then node is funded for because there is no association in the Global DATIM instance.  

 New functionality needed:  Need to have some way to choose which mechanisms to load from the returned ITI-73 query.  

3)  How will the mechanisms be imported into DHIS2?  

New Functionality needed:  A way to import mechanisms into DHIS2  Options:  

notes:

4)  How will the request to update mechanisms be specified and initiated?

StepTransaction DescriptionMessage SpecificationOpenHIE Support Notes
1

On a regularly scheduled basis, CSD ITI-73 Care Services Discovery message requesting an update on the mechanisms from the Global DATIM instance. ??? How is this query initiated? from an interface? In which application? Does it happen on a scheduled basis or is there human intervention? Will the ITI-73 be different for every implementor. How will the query be configured?

ITI-73

Need to make sure that the IL can handle this out-going message type.

ITI-73 was tested in V1.0, but not going from the ILR to the IL.

2Message passed from the Country IL to the Global DATIM instance's IL.ITI-73 
3The DATIM Global instance responds with the ITI-73 with a CSD document OR a DXF document.The DXF document can be directly sent to DHIS2, but the CSD document would go into OpenInfoMan first.ITI-73 response (CSD Document)

Need to make sure that the IL can handle this in-coming message type.

CSD responses were tested in V1.0, but going from the IL to the ILR.

4The CSD document is updated in InfoMan.ITI-73 response (CSD Document)

 

5Import DXF document document into HMIS - Is this done manuallly? DXFThis was done manually in OpenHIE 1.0
title Node Requests Mechanism Update From Global DATIM

participant Global-IL
participant Node-IL
participant Node-ILR
Participant Node-HMIS

loop periodic refresh
Node-ILR->Node-IL: [1] Update Request
Node-IL->Global-IL: [2] Update Request
Global-IL->Node-IL: [3] Update Response
Node-IL->Node-ILR: [4] Update Response
Node-ILR->Node-HMIS: [5] Update Response

INDICATORS:  

Like the mechanism questions.  Don't want to load in the ones you don't need.  Need a UI to select the indicators we are loading.  DHIS2 is probably the best place to have the mechanisms.  Having the UI for this is much more natural in DHIS2 than as is the case with the mechanisms.  Need an app to create the ITI-73 to search  for services, returns result.  Result in CSD to InfoMan or DXF nativly (Carl votes for DXF).  

 

ORG UNITS - Like the indicators, select the ones you want before you import. 

How are stie names from teh country and PEPFAR mapped?  In infoman?  In DHIS2?

 

DHIS2 App or OpenInfoMan app to determine what needs to be imported 

Ideal soslution - Orgunit case - OpenInfoMan produce the elements 

ITI-73.  TO give DHIS2 the list and then dsiplay.  

 

 

 

title Node Requests Disaggregator Update From Global DATIM

participant Global-IL
participant Node-IL
participant Node-ILR
Participant Node-HMIS

loop periodic refresh
Node-ILR->+Node-IL: [1] Update Request
Node-IL->Global-IL: [2] Update Request
Global-IL->Node-IL: [3] Update Response
Node-IL->Node-ILR: [4] Update Response
Node-ILR->Node-HMIS: [5] Update Response





 

 

StepTransaction DescriptionMessage SpecificationOpenHIE Support Notes
1

On a regularly scheduled basis, Chron jobs are used to generate a ITI-48 Retrieve Value Set message requesting an update of the disaggregator values.

Is there a need to coordinate this update with the indicator update?

ITI-48

This message was not tested in OpenHIE V1.0, what components need to support this transaction? The IL?

2Message passed from the Country IL to the Global DATIM instance IL.ITI-48 
3The DATIM Global instance responds with the ITI-48 with an SVSITI-48 Response (SVS)

This message was not tested in OpenHIE V1.0, what components need to support this? The IL, the InfoMan?

4??The Disaggregators are stored in OpenInfoMan???? transform into XSD?ITI-48 Response (SVS)

 

5Import into DHIS2 via an interface? XDFNot tested in OpenHIE 1.0