...
The implementers page should have a basic OpenHIE overview to ensure that implementers actually understand what OHIE is and what it isn’t. The layman’s guide is a good start but would want a bit more
Architecture overview
Getting OpenHIE setup
...
- Organizational Principles: Identify generally applicable approaches for good self-governance;
- Trust Principles: Guide HIE governance entities on patient privacy, meaningful choice, and data management in HIE;
- Business Principles: Focus on responsible financial and operational policies for governance entities, with emphasis on transparency and HIE with the patients best interests in mind;
- Technical Principles: Express priorities for the use of standards in order to support the Trust and Business Principles as well as furthering the execution of interoperability.
It is thought that the Principles and 'actions' above could be adopted as a starting place for determining the appropriate governance model or models needed within the context of low-resource settings, or the needs of a particular country or Domain setting. Bearing in mind that varying degrees of design and implementation may need to be considered due to the potential needs of less or more complex scenarios. Not all countries are equal in their need to implement all the features of an HIE and connected systems strategy.
...
Figure: OpenHIE Architecture
In the diagram above is are depicted the building blocks of a Health Information Exchange based upon the the OpenHIE Architecture, namely: Client Registry, Facilities Registry, Health Management Information System, Health Worker Registry, Shared Health Record, and Terminology Services, and the Interoperability Services Layer that interconnects them all and provides Authentication, Interlinked Registries, and Entity Matching services.
...
OpenMRS
DHIS2
Country and Partner EHRs
PEPFAR DATIM
Laboratory Information Management Systems (LIMS)
Logistics Management Information Systems (LMIS)
Pharmacy Information Systems
etc.
...