The OpenHIE architecture supports interoperability by creating a framework that maximally leverages health information standards, enables flexible implementation by country partners, and supports interchangeability of individual components (more information on the strategy can be found here). Each component supports well-described, core health data management functions and interoperates with other components to ensure that health information from various point of service applications is rationalized to support person-centric and population-based healthcare needs. Reference implementations of each of the components exist to validate and highlight the functionality enabled within the architecture, and also are designed to support real world needs. Different compositions of these components can be used within a given environment to support myriad workflows. Exemplar user cases are highlighted below.
The fundamental basis of interoperability is in harmonizing the context with which information is collected in so that it’s broadly reusable to a much larger set of stakeholders. The OpenHIE architecture supports interoperability by creating a framework that maximally leverages health information standards, enables flexible implementation by country partners, and supports interchangeability of individual components.
Reference implementations of each of the components exist to validate and highlight the functionality enabled within the architecture. Each component supports well-described, core health data management functions and interoperates with other components to ensure that health information from various external systems is rationalized to support person-centric and population-based healthcare needs. Different compositions of these components can also be used within a given environment to support workflows.
Who benefits from the health information exchange?
The external systems are a diverse group of actors that leverage the health information exchange to improve the quality of care by using higher quality and more timely data to support their activities. These systems include mobile messaging tools (SMS/IVR), electronic medical records, laboratory or stock management systems, and monitoring and evaluation tools.
Who facilitates complex interactions where multiple actors are involved?
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 external systems and coordinates interaction between components of the HIE and provides common core functions to simplify the interoperability between systems.
What vocabulary do we agree to use?
The Terminology Services (TS) component of the Open HIE Architecture provides a centralized source for the HIE’s standards and definitions, including terminologies, ontologies, dictionaries, code systems, and value sets. Other HIE components can use these standards and definitions to normalize clinical data and achieve consistent aggregation and reporting.
Who received health services?
The Client Registry (CR) supports the unique identification and management of patient identities. In order for the details of what specifically happens during a health service event to be understood universally, each client or patient needs to be represented in a standard way.
Shared Health Record
What is a person’s cumulative health history?
A Shared Health Record (SHR) enables the collection and storage of electronic health information about individual patients in a centralised repository which is capable of being shared across different healthcare settings.
Health Management Information System
What is the population’s cumulative health history?
The Health Management Information System (HMIS) component – stores and redistributes population level information normalized through the exchange.
What locations provide health services?
The Facility Registry (FR) serves as the authority for maintaining the unique identities of locations where health services are provided. This is the service that manages a master facility list dataset.
Health Worker Regisry
Who provides health services?
The Health Worker Registry (HWR) serves as the authority for maintaining the unique identities of health workers within a country.
We seek to leverage consensus-based, international interoperability specifications that support countries’ health information exchange needs. To the extent possible we will leverage the IHE process to identify, evaluate and implement pre-existing specifications and advocate for the development of future solutions.
Health information exchange functional requirements vary among countries and evolve over time. We recognize that existing standards and interoperability specifications don’t always align with a country’s needs. Consequently, we seek an architecture that supports, and does not constrain, the effective implementation of country-driven workflows. We seek to make architectural decisions based on implementations expressed needs and choose standards that best support the user.
OpenHIE seeks to support a robust and diverse component ecosystem, where implementation and support organizations can leverage different software products for the OpenHIE components. To enable effective and efficient use of components, we seek an architecture that clearly defines and reinforces standardized interfaces for each of these components.