Workflow Collection Maturity

This collection of workflows is designed to support aggregate data exchange of health indicators. To fully support this capability, metadata describing the indicators also needs to be translated or exchanged.  

The workflows in this collection are designed to support the following types of data exchanges:

1. Sending an aggregate data message from an HIE.
2. An HIE receiving an aggregate data message.
3. Subscribing to metadata that can be used to support translation of synchronization processes.
4. Responding to a request for updated metadata.

This collection is targeted for initial pilot implemented by PEPFAR in late 2016 / early 2017.

These workflows are designed to facilitate one-way communication to a client or provider listed in the HIE. The workflows are designed to support use cases such as care reminders or crisis communications.

The workflows in this collection are designed to support the following types of data exchanges:

1. Sending alerts to patients or those for whom care or services are being provided.
2. Sending alerts to providers or those who are providing care.

This collection is designed to allow external systems such as point-of-care systems to query for provider and/or facility information.

The workflows in this collection are designed to support the following types of data exchanges:

1. Query for provider information.  
2. Query for facility information.  
3. Query for provider and facility information that is linked together.

Case Based Reporting

(Click on the links for a full description of the workflow)

The workflows designed to transmit sentinel events and case reports for the purposes of monitoring care at a public health level and incident reporting.

The workflows are designed to support the following types of data exchanges:

1. A Point-of-Service (PoS) systems such as EMR to a shared health record.

Insurance Collection

(Click on the links for a full description of the workflow)

The Client Registry is designed to assist in uniquely identifying individuals who receive healthcare services in the geographic region and/or use cases supported HIE.

The workflows are designed to support the following types of data exchanges:

1. A Point-of-Service (PoS) systems such as EMRs or other patient identity sources can add or update a patient's demographics information in the Client Registry.
2. A Point-of-Service (PoS) or other system that is authorized to access the the HIE can query the Client Registry for the patient's unique id or demographic information.

For more information on exemplary implementations, please contact the Client Registry Community.

This collection of workflows allows an external system with access to the HIE to save and retrieve information from the HIE.

The workflows are designed to support the following types of data exchanges with systems that have authority to access the HIE:

1. A point-of-care or external system can query for previous encounter for a specific patient.
2. This transaction allows a PoC or an external system can provide data to the HIE's SHR.
3. A point-of-care or external system can request and receive an on-demand document from the HIE's SHR.

Supply Chain Collection

(Click on the links for a full description of the workflow)

Terminology Service Collection

(Click on the links for a full description of the workflow)

OHIE LEVEL 4 - Single Implementation of this workflow collection

This collection of workflows is being designed to support terminology service interactions within or external to the HIE.

The workflows are designed to support the following types of data exchanges with systems that have access to the HI

1. Query for Code Systems, Value Sets and Concept Maps that are present in the HIE's Terminology Service.
2. Validate that a code exists in a Code System or Value Set.
3. Lookup a code in Code System and retrieve its details.
4. Expand (retrieve) the members of a Value Set.
5. Retrieve a code mapping from a Concept Map.