US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 8.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions
Page standards status: Informative |
US Core is intended to provide an implementable standard for FHIR based interfaces for provider and patient facing systems providing:
The context of US Core within the set of US Realm HL7 FHIR standards is shown in the figure below.
Other international and national standards were reviewed and considered during the development process to assess the degree of alignment and to facilitate adoption of this standard. These implementation guides include:
Implementation Guide | Relationship |
---|---|
International Patient Access (IPA) | This IG describes how an application acting on behalf of a patient can access information about the patient from a clinical records system using a FHIR based API. The REST API and profiles in this IG were reviewed and considered during development of US Core. US Core was is compatible with IPA, e.g. US Core conformant data can be accessed by an IPA conformant client. |
International Patient Summary (IPS) | This IG describes specify how to represent in HL7 FHIR the IPS. An IPS document is an electronic health record extract containing essential healthcare information about a subject of care. The formal review between this IG and US Core is not current. |
The table below summarizes profile only comparison between US Core and the International Patient Access Implementation Guides. This comparison evaluates US Core conformance requirements with the key implementation guides identifying where compliance with US Core satisfies the expectations established by the referenced implementation guide. Compliance in the reverse direction is not guaranteed, i.e. a resource that is compliant with an International Patient Access profile may not be compliant with US Core.
As part of profile comparison, the requirements, constraints, and standards specified in a particular FHIR profile are evaluated. These requirements can include mandatory elements, Must Support elements, cardinality constraints, data types, terminology bindings, usage rules, extensions, rules on missing or suppressed data. A detailed comparisons with the current version of IPA can be found here
Legend:
✔ Compliant: A US Core compliant resource meets all requirements of the compared profile.
➕ Additional requirements: A US Core compliant resource is compatible, but additional changes may be needed to meet all requirements of the compared profile. Where additional requirements are identified, more information is provided in the sections below.
✘ Incompatible: A US Core compliant resource is incompatible with the compared profile. A resource cannot be compliant to both. Where incompatible requirements are identified, more information is provided in the sections below.
⛔ No equivalent profile: No equivalent profile for comparison.
The following US Core resource are compatible to the IPA profiles, but the IPA profile(s) contain additional requirements which are listed below. Changes may be needed to meet all the IPA profile requirements. Implementers are advised to note that some code changes may be required to support these profiles.
US Core ADI DocumentReference Profile
Additional requirements for IPA DocumentReference:
DocumentReference.content.attachment.contentType
Element minimum cardinalities differ: '1' vs '0'DocumentReference.context
Elements differ in definition for mustSupport: 'true' vs 'false'DocumentReference.context.encounter
Elements differ in definition for mustSupport: 'true' vs 'false'DocumentReference.context.encounter
Element maximum cardinalities differ: '1' vs '*'DocumentReference.context.period
Elements differ in definition for mustSupport: 'true' vs 'false'US Core DocumentReference Profile
Additional requirements for IPA DocumentReference:
DocumentReference.content.attachment.contentType
Element minimum cardinalities differ: '1' vs '0'US Core Average Blood Pressure Profile
Additional requirements for IPA Observation
Observation.value[x]
Elements differ in definition for mustSupport: 'true' vs 'false'Observation.value[x]
Element maximum cardinalities differ: '1' vs '0'Observation.dataAbsentReason
Elements differ in definition for mustSupport: 'true' vs 'false'US Core Care Experience Preference Profile, US Core Simple Observation Profile, US Core Smoking Status Observation Profile, US Core Treatment Intervention Preference Profile
Additional requirements for IPA Observation:
Observation.dataAbsentReason
Elements differ in definition for mustSupport: 'true' vs 'false'US Core Observation ADI Documentation Profile, US Core Observation Occupation Profile
Additional requirements for IPA Observation:
Observation.value[x]
Elements differ in definition for mustSupport: 'true' vs 'false'Observation.dataAbsentReason
Elements differ in definition for mustSupport: 'true' vs 'false'Additional requirements for IPA Patient:
Patient.active
Element minimum cardinalities differ: '1' vs '0'Patient.active
Elements differ in definition for mustSupport: 'true' vs 'false'Patient.gender
Elements differ in definition for mustSupport: 'true' vs 'false'Patient.link
Element maximum cardinalities differ: '1' vs '*' (:thinking_face: a technical error in IPA profile)Patient.link
Elements differ in definition for mustSupport: 'true' vs 'false'US Core compliant resources are compliant with IPA requirements for Missing Data.
IPA does not include requirements for Suppressed Data.
This version of US Core has no equivalent profile for the following IPA profiles: