Skip to end of metadata
Go to start of metadata


The official version of the OHIE workflows can be found in the OpenHIE Architecture Specification.


Description: This workflow enables requested metadata to be sent from an interlinked registry to another system.  In DATIM, it will be used to send data from the interlinked registry with the source metadata (indicators, mechanisms, sites) to another interlinked registry.  

Referenced Standards and APIs

Assumptions and Prerequisites

  • Metadata being requested has already been populated in the ILR (interlinked registry).   


External System Actor (Actor outside this HIE)

  • The system requesting the updated metadata (sites, mechanisms and/or indicators).  

OpenHIE System Actors (Actors within the HIE receiving the request for updated metadata.)

  • IL -The Interoperability Layer (IL) is the component that enables easier interoperability between disparate information systems by connecting the infrastructure services and client applications together. An interoperability layer receives transactions from the external system and coordinates interaction between components of the HIE and provides common core functions to simplify the interoperability between systems.
  • ILR - The interlinked Registry containing the metadata (sites, indicators and / or mechanisms) requested by the external system.  

Technical Details

Step NumberInteractionDesign NotesDataTransaction Standard

Receive incoming ITI-74 requesting updated interlinked data.

Note: for more specificity, an implementer can also use an ITI-73.

Request for all updated data since a specific time stamp.


Authenticate sender and log message header


Request for updated interlinked data is sent to the ILR.

Request for all updated data since a specific time stamp.

4The ILR generates the response document and sends it to the IL.

5Log the responseThe IL logs the response


Return Matching data to the requesting system

Test Cases 

The following are the high-level test cases that this workflow must support:  

Test CaseDescription

Message Examples

  • No labels