...
In addition to the above an SHR should closely match the requirements defined by OpenHIE as can be found here.
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:
SHR Level 1 - (at least one content profile + query for existing data)
A phase 1 OpenHIE SHR must implement the following:
- XDS.b's provide and register document, stored query and retrieve document transactions
At least one of the Patient Care Coordination CDA content profiles which profile the CDA Continuity of Care Document (CCD) specification.
- The Query for Existing Data (QED) profile
SHR Level 2 - (all PCC content profiles + query for existing data + referrals)
A phase 2 OpenHIE SHR must implement the following:
- XDS.b's provide and register document, stored query and retrieve document transactions
ALL of the Patient Care Coordination CDA content profiles which profile the CDA Continuity of Care Document (CCD) specification.
The Emergency Department Referral (EDR) PCC profile which supports referrals
- The Query for Existing Data (QED) profile
SHR Level 3 - (clinical documents + query for existing data + referrals + some form of data export - [perhaps lab and drug profiles])
A phase 3 OpenHIE SHR must implement the following:
...