Skip to end of metadata
Go to start of metadata

OHIE Workflow Collection Maturity Level Definitions

The OpenHIE workflow collections are the building blocks used to support standards-based health information exchange interactions.  The same building blocks can be used to support multiple clinical and health information use cases.  

Collection Maturity Level

(Levels are cumulative and cannot be skipped)

Description
OHIE LEVEL 1 - Emerging Collection
  • Real-World Need Identified
  • Workflow in discussion
OHIE LEVEL 2 - Defined Collection
  • Workflows are defined, documented and designed to meet the need of the identified use case.
  • Implementers are aware of the design and have provided input.
  • Workflows have ARB approval
OHIE LEVEL 3 - Reference Solutions
  • Reference Software solutions exist, are available and have been tested
OHIE LEVEL 4 - Single Implementation of this workflow collection
  • Single instance of this workflow collection is implemented "in a real-world setting"
OHIE LEVEL 5 - Multiple Implementations of this workflow collection
  • One or more OpenHIE implementations of this workflow collection in one or more countries

Quick Links - OHIE Workflow Collections

Workflow CollectionMaturityDescription

Aggregate Data Reporting

OHIE LEVEL 2 - Defined Collections

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.

 Click for Aggregate Reporting Maturity Details

OpenHIE Workflows

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

Workflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of standards

Reference Software Assessment Maturity Criteria

  • Software exists
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Export Aggregate Data

  • Reference Software is being developed
  • IHE Integration Statement
  • Reference software is being integration tested on the DATIM project

Validate and Save Aggregate Data

 

  • Reference Software is being developed
  • IHE Integration Statement
  • Reference software is being integration tested on the DATIM project

Reference Software

Architecture Component

DHIS2Health Management Information System
OpenInfomanInterlinked Registry
OpenHim

Interoperability Layer

OHIE Matching ServiceOHIE Services Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

Workflow CollectionMaturityDescription

Alerting / Sending Reminders or Information

OHIE LEVEL 3 - Reference Solutions

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.

 Click for Alerting / Sending Reminders or Information Maturity Details

OpenHIE Workflows

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

Workflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Send client alert workflow

  • Software solutions support this workflow
  • Reference software has been IHE conformance tested
Send health worker alert workflow
  • Software solutions support this workflow
  • Reference software has been IHE conformance tested

Reference Software

Architecture Component

OpenInfomanInterlinked Registry
OpenHimInteroperability Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

 

 

Workflow CollectionMaturityDescription

Care Provider and Facility Query

OHIE LEVEL 3 - Reference Solutions

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.

 Click for Care Provider and Facility Query Maturity Details

OpenHIE Workflows

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

Workflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Query health worker and/or facility records workflow

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Reference SoftwareArchitecture Component
OpenInfoman 
OpenHimInteroperability Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

 

 

Workflow CollectionMaturityDescription

Case Based Reporting

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

OHIE LEVEL 1 - Emerging Collection

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.

 Click for Case Reporting Details

OpenHIE Workflows

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

Workflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Send Case Report to SHR

  • Workflow is defined and not yet ARB (link) approved
  • Workflow is supported by mature standards (links)
  • Reference software solutions exist (Links)

Reference Software

Architecture Component

OpenEMPI (Software Link)Client Registry
Medic CRClientRegistry
OpenHimInteroperability Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

 

 

Workflow CollectionMaturityDescription

Patient Identity Management

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

OHIE LEVEL 4 - Single Implementation of this workflow collection

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.

 Click for Patient Identity Management Maturity Details

OpenHIE Workflows

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

Workflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Create patient demographic record workflow

  • Workflow is defined and ARB (link) approved
  • Workflow is supported by mature standards (links)
  • Mobile standards are emerging (links)
  • Two reference software solutions exist (Links)
  • IHE Conformance statements (links)
  • OHIE Integration testing (Links)

Update patient demographic record workflow

 

  • Workflow is defined and ARB approved
  • Workflow is supported by mature standards (links)
  • Mobile standards are emerging (links)
  • Two reference software solutions exist (Links)
  • IHE Conformance statements (links)
  • OHIE Integration testing (Links)

Query patient demographic records by identifier workflow

  • Workflow is defined and ARB approved
  • Workflow is supported by mature standards (links)
  • Mobile standards are emerging (links)
  • Two reference software solutions exist (Links)
  • IHE Conformance statements (links)
  • OHIE Integration testing (Links)

Query patient demographic records by demographics workflow

  • Workflow is defined and ARB approved
  • Workflow is supported by mature standards (links)
  • Mobile standards are emerging (links)
  • Two reference software solutions exist (Links)
  • IHE Conformance statements (links)
  • OHIE Integration testing (Links)

Reference Software

Architecture Component

OpenEMPI (Software Link)Client Registry
Medic CRClientRegistry
OpenHimInteroperability Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

 

 

Workflow CollectionMaturityDescription

Shared Health Record

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

OHIE LEVEL 4 - Single Implementation of this workflow collection

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.

 Click for Shared Health Record Maturity Details

OpenHIE WorkflowsWorkflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Save patient-level clinical data workflow

Added support for on-demand documents and the option to use the MHD transport (FHIR-based) as an option. is not yet formally tested or approved.

  • Workflow is defined and ARB Approved
  • Workflow is supported by standards
  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Query patient-level clinical data workflow

Added support for on-demand documents and the option to use the MHD transport (FHIR-based) as an option. is not yet formally tested or approved.

  • Workflow is defined and ARB Approved
  • Workflow is supported by standards
  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested

Reference SoftwareArchitecture Component
 SHR
OpenHimInteroperability Layer

 

SCALE

The following are intended to be a visual scale that can be used to represent the qualitative judgement of how OpenHie support for the workflow is maturing.

Non-

existant

Mature

 

 

 

Workflow CollectionMaturityDescription

Terminology Service Collection

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

OHIE LEVEL 1

- Emerging 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 HIE.

  1. A system can query for Code Systems and Value Sets are present in the HIE's Terminology Service.
  2. A system can provide a code or sets of codes and the Terminology System will Validate that the code or set of codes exists.
  3. Mapping / Transformation from one code set to another.
  4. A system can query for the members of a value set
  5. A system can query for the version of a coding system.

 Terminology Service Collection

OpenHIE WorkflowsWorkflow Maturity Assessment Criteria
  • Workflow is defined and ARB approved
  • Workflow is supported by standards
  • Maturity of underlying standards

Reference Product Assessment Maturity Criteria

  • Software solutions support this workflow
  • Reference software has been conformance tested
  • Reference software has been OHIE integration tested
Expand Value Set  
Retrieve Code Mapping  
Verify Code Existence  
Reference SoftwareArchitecture Component
 Terminology Service