An interoperability layer enables disparate health information systems to more easily communicate between each other in order to exchange information.
This documentation has been produced by the Interoperability Layer Community group under the OpenHIE project.
Use cases and Requirements
Interoperability Layer - Use Cases and Requirements
...
- Deadline(s):
14th May 2013 - Complete community discussions14th June 2013 - Complete community document review, release version 1
...
erformance test the current OpenHIM used in RHEA
- Status:
Status colour Green title Completed - Working Document(s):
- Deadline(s): none
...
Create a tool to evaluate Interoperability Layer software that is closely linked to the requirements
- Status:
Status colour Green title Completed - Working Document(s): Interoperability Layer Evaluation Tool
- Deadline(s):
14th June 2013 - Complete community review, release version 1
...
Compile a list of software that could be used as an interoperability layer
- Status:
Status colour Green title Completed - Working Document(s): Interoperability Layer - Tools for review
- Deadline(s):
31st May 2013 - Finalise list
...
Evaluate list software options using the evaluation tool
- Status:
Status colour Green title Completed - Working Document(s): Interoperability Layer Evaluation Tool
- Deadline(s):
21th June 2013
...
Write up results of the evaluation and come to consensus on a recommended way forward (ie. Use/modify an existing tool or build from scratch)
- Status:
Status colour Green title Completed - Working Document(s): Interoperability Layer options and recommendation
- Deadline(s):
(if we need to build or modify) Create design specifications
...
| Status | ||||
|---|---|---|---|---|
|
...
- OpenHIE Interoperability Layer design document
- Additional Notes:
...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Value Proposition
Please contribute to the value propostion document here
Use cases and Requirements
Architecture and Design Discussions
- Architecture discussion: ESB vs No ESB
- Architecture for using CSD in the OpenHIM
- Authentication and Authorization within OpenHIE
- Division of Labor Between the Registries and the Interoperability Layer
- Interactions through the Interoperability Layer
- Mark Tucker Blog on Interoperability Layer
- Consent Management - IL community thoughts
Design Specification
Supported Workflows and Standards
General OHIE workflows
HIM-Specific workflows
Transaction and Message specifications
- OpenHIE Transactions
Additional documentation
- Presentations
The OpenHIM Tool
The OpenHIM is the open-source middle-ware tool developed to meet the requirements of an IOL as defined by this community.
More information about this evolving tool still under active development can be found on the OpenHIM website and the code repository is available on Github.
View the 2014 Technical Development Roadmap to see what additional features and functionality are planned.
OpenHIM training material is available here.