- Created by Jamie Thomas, last modified by Shelby Guthrie on Aug 24, 2023
The OpenHIE Interoperability Layer Community (OHIE-IOL) aims to enable easier interoperability between Health Information Systems by providing a forum for discussion and knowledge sharing and by designing and developing an interoperability layer that connects the components within the OHIE.
We envision a world in which the timely exchange of health information improves health outcomes and saves lives.
Our mission is to build and sustain an open community to discuss the challenges of interoperability between health information systems, as well as to design an architecture and develop a reference software application to enable easier interoperability between disparate health systems and components. We promote the use of appropriate standards to support best practices for health data exchange.
Our values
- We hold the needs of our target community of users as our primary concern
- We are an open and collaborative community, valuing the inputs and respecting the contributions of every member
- We strive for elegantly simple solutions to complex problems
- We use the “adopt, adapt, develop” approach to inform our decision-making process for standards and technology
- We aim for ease of use to reduce barriers to adoption, especially in low-resource settings
- We are implementation-driven in our designs and requirements, valuing practical solutions to real problems and real needs
What is an Interoperability Layer?
An interoperability layer is a system that enables easier interoperability between disparate information systems by connecting all of the infrastructure services and client applications together. In the OpenHIE context, these systems are Health Information Systems (HISs) such as a client registry, provider registry, facility registry, shared health record and terminology service. An interoperability layer receives transactions from client systems, coordinates interaction between components of the HIE and provides common core functions to simplify the interoperability between systems.
- Documentation
- Use cases and Requirements
- Architecture & Design discussions
- Supported Workflows & Standards
- Transaction and Message specifications
- Interoperabiltiy Layer Functional Specifications Document
- Reference Technologies (Reference software)
The interoperability layer developed by this community is the OpenHIM (Open Health Information Mediator),an open-source middleware system based on an ESB architecture and currently implemented in Rwanda as part of the RHIE. Plans for current development activities can be seen on the roadmap.
More details about this tool are available at
and the code is available on the
There are however a number of other technology options which may be utilised for this component.
RHIE Rwanda Health Information Exchange
Zimbabwe
For more detailed information about these and other implementations, click here.
Upcoming Events
Error(s) occurred.
Warning(s) occurred.
Calendars with restrictions are embedded here.
- EDIT THE CALENDAR
Customise the different types of events you'd like to manage in this calendar.
#legIndex/#totalLegs - RESTRICT THE CALENDAR
Optionally, restrict who can view or add events to the team calendar.
#legIndex/#totalLegs - SHARE WITH YOUR TEAM
Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.
#legIndex/#totalLegs - ADD AN EVENT
The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.
#legIndex/#totalLegs - SUBSCRIBE
Subscribe to calendars using your favourite calendar client.
#legIndex/#totalLegs
- No labels