| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
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
Design Specification
- OpenHIE Interoperability Layer design document
- Design of the Interoperability Layer core using Node.js
- Services that an HIM should provide
- Authentication and Authorization within OpenHIE
- Restricting access to domain service endpoints
Supported Workflows and Standards
General OHIE workflows
HIM-Specific workflows
Transaction and Message specifications
Additional documentation
- Presentations
The OpenHIM Tool
The OpenHIM is the open-source tool still under active development middle-ware tool developed to meet the requirements of an IOL according to as defined by this community.
More information about this evolving tool still under active development can be found on the the OpenHIM website and and the code repository is available on on Github.
View the 2014 Technical Development
RoadmapTraining Material
OpenHIM training documentationRoadmap to see what additional features and functionality are planned.
OpenHIM training material is available here.