Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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 a Shared Health Record (SHR) based off of OpenMRS ( 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 known 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 SHR going into the future and seeks to determine what technologies would be suit a SHR for the purposes of OpenHIE.

SHR Evaluation Methodology

This section shows the methodology for going through the process of evaluating options for a shared health record. 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.

  • What is an SHR (for us)?

    • Document use cases

    • Document requirements for SHR use in OpenHIE

  • Evaluate existing SHR (OpenMRS)

    • Performance evaluation of OpenMRS

      • Stress testing (where does it break? How close does it get us to what we need?)

    • Identify functional shortcomings based on requirements

    • How its working in Rwanda

  • Design

    • Research various standards for clinical data (HL7v2; CDA - Antepartum Summary, - EDR)

    • Compilation of design options

  • Review of existing tools

    • Develop evaluation tool from requirements

    • Evaluate each tools against the evaluation tool

    • Compile results

  • Evaluation of feasibility

    • Further documentation of design options based on review of existing tools

    • Design of option for a new build (if determined to be necessary):

      • Document technology restrictions

      • Develop architecture of tool

  • Selected Strategy for way forward
  • No labels