Interoperability Layer Community Documentation

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

1. 1. Deadline(s):
      1. 14th May 2013 - Complete community discussions
      2. 14th June 2013 - Complete community document review, release version 1

2. erformance test the current OpenHIM used in RHEA

   1. Status: COMPLETED
   2. Working Document(s):
      1. Interoperability Layer Performance Analysis
      2. Estimated load figure for a Rwandan national deployment
   3. Deadline(s): none

3. Create a tool to evaluate Interoperability Layer software that is closely linked to the requirements

   1. Status: COMPLETED
   2. Working Document(s): Interoperability Layer Evaluation Tool
   3. Deadline(s): 14th June 2013 - Complete community review, release version 1

4. Compile a list of software that could be used as an interoperability layer

   1. Status: COMPLETED
   2. Working Document(s): Interoperability Layer - Tools for review
   3. Deadline(s): 31st May 2013 - Finalise list

5. Evaluate list software options using the evaluation tool
   

   1. Status: COMPLETED
   2. Working Document(s): Interoperability Layer Evaluation Tool
   3. Deadline(s): 21th June 2013

6. 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)

   1. Status: COMPLETED
   2. Working Document(s): Interoperability Layer options and recommendation
   3. Deadline(s): 

7. (if we need to build or modify) Create design specifications

   1. Status: COMPLETED
   2. Working Document(s):
      1. OpenHIE Interoperability Layer design document
         
      2. Additional Notes:
         1. Design Session HIM
            
         2. Open HIM Scalability Discussion
            
         3. No ESB Diagram
   3. Deadline(s):