- OpenHIE Workflow (Data Exchange) Maturity Level This maturity level takes into account the maturity of underlying IHE / FHIR specifications and the use of the workflow pattern in implementations.
- Laboratory Workflows Data exchanges revolving around laboratory information have been added to the specification.
- The Facility Registry Requirements The requirements for the key features of a facility registry were updated.
- Terminology Workflow Updates The terminology workflows were updated to include IHE specification.
We adopt best practices and influence international health information sharing standards to keep our recommendations up-to-date.
The OpenHIE Architecture provides patterns that can be used as foundations to support complex, interoperable systems for information exchange.
Our architecture recommendations are not one-size-fits-all. The components are modular to make the system work for your community’s needs.
A Health Information Exchange (HIE) makes sharing health data across information systems possible. It enables data to be shared between databases, facilities, and across regions or countries.
OpenHIE’s Architecture is made up of patterns that ensure that health information from various external systems is gathered into a single, uniﬁed HIE. To accomplish this, the exchange normalizes the context in which health information is used by focusing on the “for whom”, ”by whom”, “where”, and “what” of a patient’s health visit, bringing relevant information through a layer of interoperability and directly to the point of service. Additionally, OpenHIE also integrates medical supply data. This supports enhanced decision-making, improves the quality, safety, and continuity of care, and facilitates the appropriate use of information to improve health in a population.
Business Domain Services & Registry Services
The ﬁrst layer of the architecture consists of business domain services and registry services. Business domain components are designed to support speciﬁc health system business domains and would have the potential to combine data from multiple point-of-service and point-of-care systems. Registry services are designed to uniquely identify and track unique patients, facilities, healthcare products and terminology that are used throughout the health information exchange.
Interoperability Services Layer
The second layer of the architecture acts as a gateway between the business domain and registry services and the points of service, keeping data secure and consistent.
Point of Service Layer
Points of service , including those such as OpenMRS electronic medical records (EMR) system and the RapidSMS mHealth application, are used by clinicians and by community health workers to access and update a patient’s person-centric shared health information and to record healthcare transactions.
Updated September 2020
OHIE In Action
Take a look at how the OpenHIE Community is helping to solve health problems and improve outcomes for resource emerging communities across the globe.
A two-way communication system that was developed in 2014 to address Ebola in West Africa has been deployed in several countries to serve health workers in crises, including COVID-19, and other messaging needs like routine data collection and disease surveillance.
Global goods teamed up to achieve healthcare sustainability and address key issues in HIV care and treatment
Leveraging local universities: Capacity building for continual and sustainable health service improvement and digitization effort.