OpenHIE is actively developing workflows to support the movement of aggregate and individual records. The OpenHIE Workflows section includes technical details of workflows that are supported or under development. This wiki area aims to capture implementer workflows and use cases at a less technical level to better support human interaction between point of service systems and the HIE.

Integrating with a Master Patient Index (Currently Supported)

This workflow focuses on integrating a point of service application with a master patient index. A master patient index runs as a service in the HIE so a patient record can be identified across all HIE infrastructure components.

Workflow Steps

• A patient registration is required at a health facility or frontline worker (FLW) system
• Demographic information is collected on the patient to see if they are already registered in the point of service system
  • If the patient has already been registered, the point of service system should already have the HIE patient identifier so information.
  • If the patient has not been registered, the HIE needs to be queried by demographic information to see if the patient exists.
    • If results are returned, the user should be presented with the returned information and they should be able to choose the patient
    • If no results are returned, the registration process should be completed and the patient should be created in the HIE.

Aggregate Data exchange with the HMIS (Supported in v1.5)

The Health Management Information System (HMIS) contains aggregate indicator information. The system is setup to support configuration-based indicators, allowing for a wide range of aggregate data to be stored in the HMIS. Two way interaction with the HMIS is supported in OpenHIE v 1.5. Technical workflows can be found here for saving aggregate data and here for exporting aggregate data.

Sample Implementer Workflows

• Storing aggregate program data such as population statistics, number of patients served, number of vaccines distributed, etc. 
• Storing a count of cases under surveillance
• Storing supply chain commodity use and distribution information at the facility and health worker level.
• Storing aggregate insurance payment and claims information.
• Consuming aggregate information to support clinic activities and strengthen cases