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