Versions Compared


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


  1. The SHR should receive and store clinical documents for patients and respond to queries to retrieve a patients clinical documents.
  2. The SHR should be able to respond to queries for existing data about a patient that was received from the clinical documents.

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

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.


Additional levels of support

The above forms the base standards that an OpenHIE SHR must support. A number of those standards contain many different profiles that a SHR implementation may choose to support for a variety of use cases. OpenHIE SHRs may be built incrementally to support additional profiles. These different categories of support have been broken down into different phases. These phases are listed below: