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.
An interoperability layer enables disparate health information systems to more easily communicate between each other in order to exchange information.
Call topics and agenda are managed at: https://trello.com/b/prE5M3fh
Process Overview
As a part for the RHEA project an HIE has been developed for maternal health in Rwanda. For more information about this implementation see: here. During this implementation the OpenHIM (http://openhim.org/) was developed. This is expected to work for the pilot implementation for the RHEA project that is planned to run in a single district of Rwanda, however, it is not know if this instance will scale to a national level and if the technology is appropriate for national scale.
As a part of the OpenHIE project this community is tasked with reviewing and evaluating what makes a good interoperability layer going into the future and seeks to determine what technologies would be suit an interoperability layer for our purposes.
Methodology
What is an interoperability layer
Document use cases
Document requirements
Review current OpenHIM architecture
Review current OpenHIM technologies
Performance test current OpenHIM
Generate estimated load figure for national deployment
Create performance testing framework
Gather data from tests
Compile performance data into a report
Investigate and evaluate alternate orchestration/mediation engines or options
Enumerate and explore alternatives
Detail each alternative, it's implications and pros/cons
Develop evaluation tool from requirements
Evaluate each tools against the evaluation tool
Compile results
Investigate use of standards in OpenHIM and each option
Write up results of evaluation
Detail each option, with input from the evaluation results
- Detail the suggested way forward
Interoperability Layer use cases and requirements
...
src | https://docs.google.com/document/d/1doz07xPGcta_1lu1f_9xgNuveN8d70dU0hgz7P6tJtk/edit# |
---|---|
width | 100% |
height | 800 |
...