Page History

...

This section shows the methodology for going through the process of evaluating options for an interoperability layer. As we work on each of these items, links will be added to the relevant documentation that shows the work that is currently being done on that item.

...

1. Document use cases and requirements for a Interoperability Layer

   1. Status: Initial version completed, needs community discussion
   2. Working Document(s): What is an interoperability layer

...

• Document use cases

• Document requirements

...

Performance test current OpenHIM [Ongoing - Jembi]

• Generate estimated load figure for national deployment [Ongoing - Jembi]

• 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 [Initial version complete, out for community comment and revision]

• Evaluate each tools against the evaluation tool

• Compile results 

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

2. Performance test the current OpenHIM used in RHEA

   1. Status: Completed, needs to be discussed with community
   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: On-going, updated as requirements change
   2. Working Document(s): Interoperability Layer Evaluation Tool
   3. Deadline(s): 28th May 2013 - Complete community review, release version 1

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

   1. Status: Not started but, some basic technologies are know
   2. Working Document(s):
   3. Deadline(s): 31st May 2013 - Finalise list

5. Evaluate list software options using the evaluation tool
   

   1. Status: Not started
   2. Working Document(s):
   3. Deadline(s): 11th 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: Not started
   2. Working Document(s):
   3. Deadline(s): 30th June 2013

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

   1. Status: Initial ideas have emerged
   2. Working Document(s):

...

Detail each option, with input from the evaluation results

...

1. 1. 1. Design Session HIM
         
      2. Open HIM Scalability Discussion
         

...

Write up results of evaluation 

1. 1. Deadline(s):