Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


A core principle of the OpenHIE architecture is to allow the various infrastructure services (such as the SHR) to be interchangeable. Thus, the SHR must support some standard interfaces such that different implementation that are developed can be swapped in as needed. Various standards have been evaluated and the SHR community has decided that the core standards that an OpenHIE SHR must support are as follows:  

The context in which an SHR should use the above standard profiles is described in the OpenHIE workflows that an SHR is required to support. Each of these workflows describes a particular interaction that an SHR must support. To be OHIE SHR component, the SHR application must be able to support the OHIE workflows listed below.  Implementations may support only the workflows needed to support their use case:


In addition to the above an SHR should closely match the requirements defined by OpenHIE as can be found here.

Support of OpenHIE Non-functional Requirements 

An OpenHIE component should consider the following OpenHIE Non-Functional Requirements - Draft

Additional levels of support