This page is part of the US Core (v5.0.1: STU5) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
US Core Client CapabilityStatement |
This Section describes the expected capabilities of the US Core Client which is responsible for creating and initiating the queries for information about an individual patient. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined in the Conformance Requirements for Server. US Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements. |
US Core Server CapabilityStatement |
This Section describes the expected capabilities of the US Core Server actor which is responsible for providing responses to the queries submitted by the US Core Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined. Systems implementing this capability statement should meet the ONC 2015 Common Clinical Data Set (CCDS) access requirement for Patient Selection 170.315(g)(7) and Application Access - Data Category Request 170.315(g)(8) and the ONC U.S. Core Data for Interoperability (USCDI) Version 2 July 2021. US Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide
US Core Fetch DocumentReference |
This operation is used to return all the references to documents related to a patient. The operation requires a patient id and takes the optional input parameters:
and returns a Bundle of type “searchset” containing DocumentReference resources for the patient. The DocumentReference resources SHOULD conform to the US Core DocumentReference Profiles. If the server has or can create documents that are related to the patient, and that are available for the given user, the server returns the DocumentReference resources needed to support the records. The principle intended use for this operation is to provide a provider or patient with access to their available document information. This operation is different from a search by patient and type and date range because:
This operation is the same as a FHIR RESTful search by patient,type and date range because:
|
These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.
USCoreAllergyintoleranceClinicalStatus |
active | inactive | resolved
|
USCoreAllergyintolerancePatient |
Who the sensitivity is for
|
USCoreCareplanCategory |
Type of plan
|
USCoreCareplanDate |
Time period plan covers
|
USCoreCareplanPatient |
Who the care plan is for
|
USCoreCareplanStatus |
draft | active | on-hold | revoked | completed | entered-in-error | unknown
|
USCoreCareteamPatient |
Who care team is for
|
USCoreCareTeamRole |
Returns CareTeam resources with a participant role matching the specified code. |
USCoreCareteamStatus |
proposed | active | suspended | inactive | entered-in-error
|
USCoreConditionAbatementDate |
Date-related abatements (dateTime and period)
|
USCoreConditionAssertedDate |
Returns conditions with an assertedDate extension matching the specified date (dateTime). |
USCoreConditionCategory |
The category of the condition
|
USCoreConditionClinicalStatus |
The clinical status of the condition
|
USCoreConditionCode |
Code for the condition
|
USCoreConditionEncounter |
Encounter created as part of
|
USCoreConditionOnsetDate |
Date related onsets (dateTime and Period)
|
USCoreConditionPatient |
Who has the condition?
|
USCoreConditionRecordedDate |
Date record was first recorded
|
USCoreDevicePatient |
Patient information, if the resource is affixed to a person
|
USCoreDeviceType |
The type of the device
|
USCoreDiagnosticreportCategory |
Which diagnostic discipline/department created the report
|
USCoreDiagnosticreportCode |
The code for the report, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the result
|
USCoreDiagnosticreportDate |
The clinically relevant time of the report
|
USCoreDiagnosticreportPatient |
The subject of the report if a patient
|
USCoreDiagnosticreportStatus |
The status of the report
|
USCoreDocumentreferenceCategory |
Categorization of document
|
USCoreDocumentreferenceDate |
When this document reference was created
|
USCoreDocumentreferenceId |
Logical id of this artifact
|
USCoreDocumentreferencePatient |
Who/what is the subject of the document
|
USCoreDocumentreferencePeriod |
Time of service that is being documented
|
USCoreDocumentreferenceStatus |
current | superseded | entered-in-error
|
USCoreDocumentreferenceType |
Kind of document (LOINC if possible)
|
USCoreEncounterClass |
Classification of patient encounter
|
USCoreEncounterDate |
A date within the period the Encounter lasted
|
USCoreEncounterDischargeDisposition |
Returns encounters with an discharge-disposition matching the specified code. |
USCoreEncounterId |
Logical id of this artifact
|
USCoreEncounterIdentifier |
Identifier(s) by which this encounter is known
|
USCoreEncounterLocation |
Location the encounter takes place
|
USCoreEncounterPatient |
The patient or group present at the encounter
|
USCoreEncounterStatus |
planned | arrived | triaged | in-progress | onleave | finished | cancelled +
|
USCoreEncounterType |
Specific type of encounter
|
USCoreEthnicity |
Returns patients with an ethnicity extension matching the specified code. |
USCoreGoalDescription |
The code or text describing the goal NOTE: This US Core SearchParameter definition extends the usage context of the Conformance expectation extension
|
USCoreGoalLifecycleStatus |
proposed | planned | accepted | active | on-hold | completed | cancelled | entered-in-error | rejected
|
USCoreGoalPatient |
Who this goal is intended for
|
USCoreGoalTargetDate |
Reach goal on or before
|
USCoreImmunizationDate |
Vaccination (non)-Administration Date
|
USCoreImmunizationPatient |
The patient for the vaccination record
|
USCoreImmunizationStatus |
Immunization event status
|
USCoreLocationAddressCity |
A city specified in an address
|
USCoreLocationAddressPostalcode |
A postal code specified in an address
|
USCoreLocationAddressState |
A state specified in an address
|
USCoreLocationAddress |
A (part of the) address of the location
|
USCoreLocationName |
A portion of the location’s name or alias
|
USCoreMedicationrequestAuthoredon |
Return prescriptions written on this date
|
USCoreMedicationrequestEncounter |
Return prescriptions with this encounter identifier
|
USCoreMedicationrequestIntent |
Returns prescriptions with different intents
|
USCoreMedicationrequestPatient |
Returns prescriptions for a specific patient
|
USCoreMedicationrequestStatus |
Status of the prescription
|
USCoreObservationCategory |
The classification of the type of observation
|
USCoreObservationCode |
The code of the observation type
|
USCoreObservationDate |
Obtained date/time. If the obtained element is a period, a date that falls in the period
|
USCoreObservationPatient |
The subject that the observation is about (if patient)
|
USCoreObservationStatus |
The status of the observation
|
USCoreOrganizationAddress |
A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text
|
USCoreOrganizationName |
A portion of the organization’s name or alias
|
USCorePatientBirthdate |
The patient’s date of birth
|
USCorePatientFamily |
A portion of the family name of the patient
|
USCorePatientGenderIdentity |
Returns patients with an gender-identity extension matching the specified code. |
USCorePatientGender |
Gender of the patient
|
USCorePatientGiven |
A portion of the given name of the patient
|
USCorePatientId |
Logical id of this artifact
|
USCorePatientIdentifier |
A patient identifier
|
USCorePatientName |
A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text
|
USCorePractitionerId |
Logical id of this artifact
|
USCorePractitionerIdentifier |
A practitioner’s Identifier
|
USCorePractitionerName |
A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text
|
USCorePractitionerrolePractitioner |
Practitioner that is able to provide the defined services for the organization
|
USCorePractitionerroleSpecialty |
The practitioner has this specialty at an organization
|
USCoreProcedureCode |
A code to identify a procedure
|
USCoreProcedureDate |
When the procedure was performed
|
USCoreProcedurePatient |
Search by subject - a patient
|
USCoreProcedureStatus |
preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
|
USCoreQuestionnaireresponseAuthored |
When the questionnaire response was last changed
|
USCoreQuestionnaireresponseId |
Logical id of this artifact
|
USCoreQuestionnaireresponsePatient |
The patient that is the subject of the questionnaire response
|
USCoreQuestionnaireresponseQuestionnaire |
The questionnaire the answers are provided for
|
USCoreQuestionnaireresponseStatus |
The status of the questionnaire response
|
USCoreQuestionnaireresponseTag |
Tags applied to this resource
|
USCoreRace |
Returns patients with a race extension matching the specified code. |
USCoreRelatedpersonId |
Logical id of this artifact
|
USCoreRelatedpersonPatient |
The patient this related person is related to
|
USCoreServicerequestAuthored |
Date request signed
|
USCoreServicerequestCategory |
Classification of service
|
USCoreServicerequestCode |
What is being requested/ordered
|
USCoreServicerequestId |
Logical id of this artifact
|
USCoreServicerequestPatient |
Search by subject - a patient
|
USCoreServicerequestStatus |
draft | active | on-hold | revoked | completed | entered-in-error | unknown
|
These define constraints on FHIR resources for systems conforming to this implementation guide
US Core AllergyIntolerance Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the AllergyIntolerance resource to record, search, and fetch allergies/adverse reactions associated with a patient pm2. It identifies the mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the AllergyIntolerance resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Blood Pressure Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch diastolic and systolic blood pressure observations with standard LOINC codes and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core BMI Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch Body Mass Index (BMI) observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Body Height Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch body height observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Body Temperature Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch body temperature observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Body Weight Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch body weight observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core CarePlan Profile |
This profile sets minimum expectations for the CarePlan resource to record, search, and fetch assessment and plan of treatment data associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core CareTeam Profile |
This profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Condition Encounter Diagnosis Profile |
The US Core Condition Encounter Diagnosis Profile is based upon the core FHIR Condition Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Encounter Diagnosis’ requirements. In version 5.0.0, The US Core Condition Profile has been split into the US Core Condition Encounter Diagnosis Profile and US Core Condition Problems and Health Concerns Profile. To promote interoperability and adoption through common implementation, this profile defines constraints and extensions on the Condition resource for the minimal set of data to record, search, and fetch information about an encounter diagnosis. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Condition Problems and Health Concerns Profile |
The US Core Condition Problems and Health Concerns Profile is based upon the core FHIR Condition Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Problems’ and ‘Health Concerns’ requirements and SDOH ‘Problems/Health Concerns’ requirements. In version 5.0.0, The US Core Condition Profile has been split into the US Core Condition Encounter Diagnosis Profile and US Core Condition Problems and Health Concerns Profile. To promote interoperability and adoption through common implementation, this profile defines constraints and extensions on the Condition resource for the minimal set of data to record, search, and fetch information about a condition, diagnosis, or other event, situation, issue, or clinical concept that is documented and categorized as a problem or health concern including information about a Social Determinants of Health-related condition. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core DiagnosticReport Profile for Laboratory Results Reporting |
Laboratory results are grouped and summarized using the DiagnosticReport resource which typically reference Observation resource(s). Each Observation resource represents an individual laboratory test and result value or component result values, or a nested panel (such as a microbial susceptibility panel) which references other observations. They can also be presented in report form or as free text. This profile sets minimum expectations for the DiagnosticReport resource to record, search, and fetch laboratory results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core DiagnosticReport Profile for Report and Note Exchange |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. This profile identifies the mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the DiagnosticReport when using this profile. It provides the floor for standards development for specific uses cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DiagnosticReport Profile for Report and Note exchange and US Core DocumentReference Profile. |
US Core DocumentReference Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching patient documents including Clinical Notes using the DocumentReference resource. It identifies the mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the DocumentReference resource when using this profile. It provides the floor for standards development for specific uses cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DocumentReference Profile and US Core DiagnosticReport Profile for Report and Note exchange. |
US Core Encounter Profile |
This profile sets minimum expectations for the Encounter resource to record, search, and fetch basic encounter information for an individual patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Goal Profile |
This profile sets minimum expectations for the Goal resource to record, search, and fetch Goal information associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases |
US Core Head Circumference Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch head circumference observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Heart Rate Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch heart rate observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Immunization Profile |
This profile sets minimum expectations for the Immunization resource to record, search, and fetch immunization history associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Implantable Device Profile |
The US Core Implantable Device Profile is based upon the core FHIR Device Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Unique Device Identifier(s) for a Patient’s Implantable Device(s)’ requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Device resource to record, search, and fetch UDI information associated with a patient’s implantable device(s). It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Location Profile |
This profile sets minimum expectations for the Location resource for recording, searching for and fetching a Location associated with a patient, provider or organization to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Medication Profile |
When referencing a medication, the MedicationRequest resource can either use a code or refer to a Medication resource. This profile sets minimum expectations for the Medication resource to record, search, and fetch medications associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases |
US Core MedicationRequest Profile |
The US Core Medication Request Profile is based upon the core FHIR MedicationRequest Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Medications’ requirements. The MedicationRequest resource can be used to record a patient’s medication prescription or order. This profile sets minimum expectations for the MedicationRequest resource to record, search, and fetch a patient’s medication to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation Clinical Test Result Profile |
The US Core Observation Clinical Test Result Profile is based upon the core FHIR Observation Resource, and, along with the US Core DiagnosticReport Profile for Report and Note exchange, meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Clinical Tests’ requirements. Clinical tests includes non-imaging and non-laboratory tests performed on a patient that results in structured or unstructured (narrative) findings specific to the patient, such as electrocardiogram (ECG), visual acuity exam, macular exam, or graded exercise testing (GXT), to facilitate the diagnosis and management of conditions. The US Core Observation Clinical Test Result Profile profile sets minimum expectations for the Observation resource to record, search, and fetch clinical tests for a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation Imaging Result Profile |
The US Core Observation Imaging Result Profile is based upon the core FHIR Observation Resource, and, along with the US Core DiagnosticReport Profile for Report and Note exchange, meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Diagnostic Imaging’ requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch retrieve structured and unstructured (narrative) components of diagnostic imaging test results for a patient. These observations include reasons, findings, and impressions. It provides the floor for standards development for specific uses cases. |
US Core Laboratory Result Observation Profile |
The US Core Laboratory Result Observation Profile is based upon the core FHIR Observation Resource, and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Laboratory’ requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource which reference Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) which references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation SDOH Assessment Profile |
The US Core Observation SDOH Assessment Profile meets the U.S. Core Data for Interoperability (USCDI) v2 ‘SDOH Assessments’ requirements. This profile is based on the US Core Observation Survey Profile and sets minimum expectations for representing responses to assessment tools such as the Protocol for Responding to and Assessing Patients’ Assets, Risks, and Experiences (PRAPARE) Survey. It can be used to represent individual responses, panels of multi-question surveys, and multi-select responses to “check all that apply” questions. It identifies the additional core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation Sexual Orientation Profile |
The US Core Observation Sexual Orientation Profile meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Sexual Orientation’ requirements. this profile sets minimum expectations for the Observation resource to record, search, and fetch sexual orientation observations associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation Social History Profile |
The US Core Observation Social History Profile meets the U.S. Core Data for Interoperability (USCDI) v2 ‘SDOH Assessments’ requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch retrieve observations that represent simple observations made by an individual about a patient’s social history status such as education, food insecurity, etc. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Observation Survey Profile |
To promote interoperability and adoption through common implementation, the US Core Observation Survey Profile sets minimum expectations for the Observation Resource to record, search, and fetch retrieve observations that represent the questions and responses to form/survey and assessment tools. It can be used to represent individual responses, panels of multi-question surveys, and multi-select responses to “check all that apply” questions. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Organization Profile |
This profile sets minimum expectations for the Organization resource to searching for and fetching an Organization associated with a patient or provider to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Pediatric BMI for Age Observation Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric body mass index (BMI) percentile per age and sex for youth 2-20 observations in FHIR using a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Pediatric Weight for Height Observation Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric weight-for-length per age and gender observations in FHIR with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Practitioner Profile |
This profile sets minimum expectations for the Practitioner resource to record, search, and fetch basic demographics and other administrative information about an individual practitioner to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core PractitionerRole Profile |
This profile sets minimum expectations for the PractitionerRole Resource to record, search, and fetch the practitioner role for a practitioner to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. The requirements for the US Core Practitioner were drawn from the Argonaut Provider Directory, IHE Healthcare Provider Directory and the ONC Provider Directory Workshop. |
US Core Procedure Profile |
The US Core Procedure Profile is based upon the core FHIR Procedure Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Procedures’ requirements. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Provenance Profile |
This profile sets minimum expectations for the Provenance resource to record, search, and fetch Provenance information associated with a record to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. This FHIR Provenance profile here covers the minimal (basic) information to support lineage of information. It provides the floor for standards development for specific uses cases. Prior to reviewing this profile, implementers are encouraged to read the Basic Provenance guidance page which documents several key use cases, specifically, what organization was responsible for the most recent action on the resource. |
US Core Pulse Oximetry Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch pulse oximetry and inspired oxygen observations with a standard LOINC codes and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core QuestionnaireResponse Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the QuestionnaireResponse resource to record, search, and fetch retrieve captures the responses to form/survey and assessment tools such as the Protocol for Responding to and Assessing Patients’ Assets, Risks, and Experiences (PRAPARE) Survey. This profile is based on the Structured Data Capture (SDC) Questionnaire Response Profile and identifies the additional core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core RelatedPerson Profile |
This profile sets minimum expectations for the RelatedPerson resource to record, search, and fetch related persons associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Respiratory Rate Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch respiratory rate observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Smoking Status Observation Profile |
The US Core Smoking Status Observation Profile is based upon the core FHIR Observation Resource and implementers the U.S. Core Data for Interoperability (USCDI) v2 Smoking status’ requirements. This profile sets minimum expectations for the Observation resource to record, search, and fetch smoking status data associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Vital Signs Profile |
To promote interoperability and adoption through common implementation, this profile is based on the base FHIR Vital Signs Profile and defines additional constraints on the Observation resource to represent vital signs observations. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. This US Core profiles that are derived from this profile are listed below. |
US Core Pediatric Head Occipital-frontal Circumference Percentile Profile |
To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric head occipital frontal circumference (OFC) percentile observations associated with a patients from birth to 37 Months of age using a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets which SHALL be present in the Observation resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core Patient Profile |
The US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Patient Demographics’ requirements. This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
US Core ServiceRequest Profile |
This profile sets minimum expectations for recording, searching, and fetching using the ServiceRequest resource to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. |
These define constraints on FHIR data types for systems conforming to this implementation guide
US Core Birth Sex Extension |
A code classifying the person’s sex assigned at birth as specified by the Office of the National Coordinator for Health IT (ONC). This extension aligns with the C-CDA Birth Sex Observation (LOINC 76689-9). |
US Core Direct email Extension |
This email address is associated with a direct service. This extension can only be used on contact points where the system = ‘email’ |
US Core Ethnicity Extension |
Concepts classifying the person into a named category of humans sharing common history, traits, geographical origin or nationality. The ethnicity codes used to represent these concepts are based upon the CDC ethnicity and Ethnicity Code Set Version 1.0 which includes over 900 concepts for representing race and ethnicity of which 43 reference ethnicity. The ethnicity concepts are grouped by and pre-mapped to the 2 OMB ethnicity categories: - Hispanic or Latino - Not Hispanic or Latino. |
US Core Extension Questionnaire URI |
The location where a non-FHIR questionnaire/survey form can be found. This extension is used when the survey,form, or questionnaire which is being anwered is not a FHIR Questionnaire, otherwise the canonical url for the FHIR Questionnaire is used. |
US Core Gender Identity Extension |
This extension provides concepts to describe the gender a person identifies as. |
US Core Race Extension |
Concepts classifying the person into a named category of humans sharing common history, traits, geographical origin or nationality. The race codes used to represent these concepts are based upon the CDC Race and Ethnicity Code Set Version 1.0 which includes over 900 concepts for representing race and ethnicity of which 921 reference race. The race concepts are grouped by and pre-mapped to the 5 OMB race categories:
|
These define sets of codes used by systems conforming to this implementation guide
US Core Survey Codes |
This value set includes all LOINC values whose CLASSTYPE is SURVEY in the LOINC database (Refer to Appendix A of LOINC Users’ Guide) |
US Core Tags ValueSet |
Used to tag patient submitted resources for writing and searching from EHRs |
Detailed ethnicity |
The codes for the concepts ‘Unknown’, ‘Asked but no answer’, ‘other, and the 41 CDC ethnicity codes that are grouped under one of the 2 OMB ethnicity category codes. |
Detailed Race |
The codes for the concepts ‘Unknown’, ‘Asked but no answer’, ‘other, and the 900+ CDC Race codes that are grouped under one of the 5 OMB race category codes. |
US Core Discharge Disposition |
National Uniform Billing Committee, manual UB-04, UB form locator 17. |
OMB Ethnicity Categories |
The codes for the concepts ‘Unknown’, ‘Asked but no answer’, and the ethnicity categories - ‘Hispanic or Latino’ and ‘Not Hispanic or Latino’ - as defined by the OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997. |
OMB Race Categories |
The codes for the concepts ‘Unknown’, ‘Asked but Unknown’, ‘Other Race’* and the codes for the five race categories - ‘American Indian’ or ‘Alaska Native’, ‘Asian’, ‘Black or African American’, ‘Native Hawaiian or Other Pacific Islander’, and ‘White’ - as defined by the OMB Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity, Statistical Policy Directive No. 15, as revised, October 30, 1997 * The use of ‘Other Race’ is discouraged for statistical analysis. |
Language codes with language and optionally a region modifier |
This value set includes codes from BCP-47. This value set matches the ONC 2015 Edition LanguageCommunication data element value set within C-CDA to use a 2 character language code if one exists, and a 3 character code if a 2 character code does not exist. It points back to RFC 5646, however only the language codes are required, all other elements are optional. |
Birth Sex |
Codes for assigning sex at birth as specified by the Office of the National Coordinator for Health IT (ONC) |
US Core Clinical Note Type |
The US Core Clinical Note Type Value Set is a ‘starter set’ of types supported for fetching and storing clinical notes. |
US Core Clinical Test Codes |
Starter set of clinical test LOINC codes identified in Appendix B in U.S. Core Data for Interoperability (USCDI) Task Force 2021 HITAC Phase 3 Recommendations Report Letter |
US Core Common SDOH Assessments |
Common SDOH assessment concepts covering the following categories (Gravity Project SDOH Domains):
|
US Core Condition Codes |
This describes the problem. Diagnosis/Problem List is broadly defined as a series of brief statements that catalog a patient’s medical, nursing, dental, social, preventative and psychiatric events and issues that are relevant to that patient’s healthcare (e.g., signs, symptoms, and defined conditions). ICD-10 is appropriate for Diagnosis information, and ICD-9 for historical information. |
US Core Diagnostic Report Category Codes |
The US Core Diagnostic Report Category Value Set is a ‘starter set’ of categories supported for fetching and Diagnostic Reports and notes. |
US Core Diagnostic Report Laboratory Codes |
The Document Type value set includes all LOINC values whose CLASSTYPE is LABORATORY in the LOINC database |
US Core Non Laboratory Codes |
Non laboratory LOINC concepts such as codes for observations like vital signs, hemodynamics, intake/output, EKG, obstetric ultrasound, cardiac echo and other clinical observations. The codes selected should represent discrete and narrative diagnostic observations and reports |
US Core DocumentReference Category |
The US Core DocumentReferences Category Value Set is a ‘starter set’ of categories supported for fetching and storing clinical notes. |
US Core DocumentReference Type |
The US Core DocumentReference Type Value Set includes all LOINC values whose SCALE is DOC in the LOINC database and the HL7 v3 Code System NullFlavor concept ‘unknown’ |
US Core Encounter Type |
The type of encounter: a specific code indicating type of service provided. This value set includes codes from SNOMED CT decending from the concept 308335008 (Patient encounter procedure (procedure)) and codes from the Current Procedure and Terminology (CPT) found in the following CPT sections:
|
US Core Goal Codes |
Concepts from CPT and LOINC code systems that can be used to indicate the goal. |
US Core Narrative Status |
The US Core Narrative Status Value Set limits the text status for the resource narrative. |
US Core Observation Category |
HL7 FHIR concepts to classify an observation |
US Core Smoking Status Max-Binding |
Representing a patient’s smoking behavior using concepts from SNOMED CT. |
US Core Status for Smoking Status Observation |
Codes providing the status of an observation for smoking status. Constrained to |
US Core Observation Value Codes (SNOMED-CT) |
Snomed-CT concept codes for coded results |
US Core Problem or Health Concern |
Code set for category codes for US Core Condition Problems and Health Concerns Profile consisting of the concepts “problem” and “health-concern”. |
US Core Procedure Codes |
Concepts from CPT, SNOMED CT, HCPCS Level II Alphanumeric Codes, ICD-10-PCS,CDT and LOINC code systems that can be used to indicate the type of procedure performed. |
US Core Provenance Participant Type Codes |
The type of participation a provenance agent played for a given target. |
US Core Provider Role (NUCC) |
Provider roles codes which are composed of the NUCC Health Care Provider Taxonomy Code Set classification codes for providers. Only concepts with a classification and no specialization are included. |
US Core ServiceRequest Category Codes |
A set of SNOMED CT and LOINC concepts to classify a requested service |
US Core Sexual Orientation |
The US Core Sexual Orientation Value Set includes concepts to describe a person’s sexual orientation (who they are attracted to). |
US Core Smoking Status Observation Codes |
The US Core Smoking Status Observation Codes Value Set is a ‘starter set’ of concepts to capture smoking status. |
USPS Two Letter Alphabetic Codes |
This value set defines two letter USPS alphabetic codes. |
US Core Vital Signs ValueSet |
The vital sign codes from the base FHIR and US Core Vital Signs. |
These define new code systems used by systems conforming to this implementation guide
US Core Observation Category Extension Codes |
Set of codes for implementation of the US-Core profiles. These codes are extensions to the FHIR Observation Category Codes. |
US Core Tags CodeSystem |
Codes used in US Core |
US Core CarePlan Category Extension Codes |
Set of codes that are needed for implementation of the US-Core CarePlan Profile. These codes are used as extensions to the FHIR ValueSet. |
US Core Condition Category Extension Codes |
Set of codes that are needed for implementation of the US-Core Condition Profile. These codes are used as extensions to the FHIR and US Core value sets. |
US Core DocumentReferences Category Codes |
The US Core DocumentReferences Type Code System is a ‘starter set’ of categories supported for fetching and storing DocumentReference Resources. |
US Core Provenance Participant Type Extension Codes |
Set of codes that are needed for implementation of the US-Core Provenance Profile. These codes are used as extensions to the FHIR value sets. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like
Device Defib Example |
This is a Device defib example for the US Core Implantable Device Profile. |
Device Knee Example |
This is a Device knee example for the US Core Implantable Device Profile. |
DXA Bone density quantitative measurement panel Example |
This is a DXA Bone density quantitative measurement panel report example for the US Core DiagnosticReport Note Profile. |
DiagnosticReport Cardiology Report Example |
This is a DiagnosticReport cardiology report example for the US Core DiagnosticReport Note Profile. |
DiagnosticReport Chest Xray Report Example |
This is a DiagnosticReport chest xray report example for the US Core DiagnosticReport Note Profile. |
10 minute Apgar Color Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse. |
10 minute Apgar Heart Rate Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse. |
10 minute Apgar Muscle Tone Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse. |
10 minute Apgar Reflex Irritability Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse.. |
10 minute Apgar Respiratory effort Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse. |
10 Minute Apgar Score Panel Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture surveys assessments as a panel of observations. It is not derived from a FHIR QuestionnaireResponse. |
10 Minute Apgar Score Example |
This example of a US Core Survey Observation Profile illustrates its use to directly capture individual surveys assessment items as an observations. It is not derived from a FHIR QuestionnaireResponse. |
Ahc-Hrsn Item Example 44250-9 |
This is a Ahc-Hrsn Item Example 44250-9 (Little interest or pleasure in doing things?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 44255-8 |
This is a Ahc-Hrsn Item Example 44255-8 (Feeling down, depressed, or hopeless?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 68516-4 |
This is a Ahc-Hrsn Item Example 68516-4 (On average, how many minutes did you usually spend exercising at this level on one of those days?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 68517-2 |
This is a Ahc-Hrsn Item Example 68517-2 (How many times in the past 12 months have you had 5 or more drinks in a day (males) or 4 or more drinks in a day (females)?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 68524-8 |
This is a Ahc-Hrsn Item Example 68524-8 (How many times in the past year have you used illegal drugs?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 69858-9 |
This is a Ahc-Hrsn Item Example 69858-9 (Because of a physical, mental, or emotional condition, do you have serious difficulty concentrating, remembering, or making decisions?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 69861-3 |
This is a Ahc-Hrsn Item Example 69861-3 (Because of a physical, mental, or emotional condition, do you have difficulty doing errands alone such as visiting a physician’s office or shopping?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 76513-1 |
This is a Ahc-Hrsn Item Example 76513-1 (How hard is it for you to pay for the very basics like food, housing, medical care, and heating?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 89555-7 |
This is a Ahc-Hrsn Item Example 89555-7 (In the last 30 days, other than the activities you did for work, on average, how many days per week did you engage in moderate exercise (like walking fast, running, jogging, dancing, swimming, biking, or other similar activities)?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 93038-8 |
This is a Ahc-Hrsn Item Example 93038-8 (Stress means a situation in which a person feels tense, restless, nervous, or anxious, or is unable to sleep at night because his or her mind is troubled all the time. Do you feel this kind of stress these days?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 93159-2 |
This is a Ahc-Hrsn Item Example 93159-2 (How often do you feel lonely or isolated from those around you?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 95530-2 |
This is a Ahc-Hrsn Item Example 95530-2 (How many times in the past year have you used prescription drugs for non-medical reasons?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 96780-2 |
This is a Ahc-Hrsn Item Example 96780-2 (Do you want help finding or keeping work or a job?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 96781-0 |
This is a Ahc-Hrsn Item Example 96781-0 (If for any reason you need help with day-to-day activities such as bathing, preparing meals, shopping, managing finances, etc., do you get the help you need?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 96782-8 |
This is a Ahc-Hrsn Item Example 96782-8 (Do you want help with school or training? For example, starting or completing job training or getting a high school diploma, GED or equivalent.) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 96842-0 |
This is a Ahc-Hrsn Item Example 96842-0 (How often have you used any tobacco product in past 12 months?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Item Example 97027-7 |
This is a Ahc-Hrsn Item Example 97027-7 (Do you speak a language other than English at home?) for the US Core Screening Response Observation Profile |
Ahc-Hrsn Panel Example 96777-8 |
This is a Ahc-Hrsn Panel Example 96777-8 (Accountable health communities (AHC) health-related social needs screening (HRSN) tool) for the US Core Screening Response Observation Profile |
Hvs Item Example 88122-7 |
This is a Hvs Item Example 88122-7 ((I/We) worried whether (my/our) food would run out before (I/we) got money to buy more.) for the US Core Screening Response Observation Profile |
Hvs Item Example 88123-5 |
This is a Hvs Item Example 88123-5 (The food that (I/we) bought just didn’t last, and (I/we) didn’t have money to get more.) for the US Core Screening Response Observation Profile |
Hvs Item Example 88124-3 |
This is a Hvs Item Example 88124-3 (Food insecurity risk) for the US Core Screening Response Observation Profile |
Hvs Panel Example 88121-9 |
This is a Hvs Panel Example 88121-9 (Hunger Vital Sign [HVS]) for the US Core Screening Response Observation Profile |
Prapare Item Example 54899-0 |
This is a Prapare Item Example 54899-0 (Preferred language) for the US Core Screening Response Observation Profile |
Prapare Item Example 56051-6 |
This is a Prapare Item Example 56051-6 (Do you consider yourself Hispanic/Latino?) for the US Core Screening Response Observation Profile |
Prapare Item Example 56799-0 |
This is a Prapare Item Example 56799-0 (Address) for the US Core Screening Response Observation Profile |
Prapare Item Example 63512-8 |
This is a Prapare Item Example 63512-8 (How many people are living or staying at this address?) for the US Core Screening Response Observation Profile |
Prapare Item Example 63586-2 |
This is a Prapare Item Example 63586-2 (What was your best estimate of the total income of all family members from all sources, before taxes, in last year?) for the US Core Screening Response Observation Profile |
Prapare Item Example 67875-5 |
This is a Prapare Item Example 67875-5 (Employment status current) for the US Core Screening Response Observation Profile |
Prapare Item Example 71802-3 |
This is a Prapare Item Example 71802-3 (Housing status) for the US Core Screening Response Observation Profile |
Prapare Item Example 76437-3 |
This is a Prapare Item Example 76437-3 (Primary insurance) for the US Core Screening Response Observation Profile |
Prapare Item Example 76501-6 |
This is a Prapare Item Example 76501-6 (Within the last year, have you been afraid of your partner or ex-partner?) for the US Core Screening Response Observation Profile |
Prapare Item Example 82589-3 |
This is a Prapare Item Example 82589-3 (Highest level of educ) for the US Core Screening Response Observation Profile |
Prapare Item Example 93026-3 |
This is a Prapare Item Example 93026-3 (Do you feel physically and emotionally safe where you currently live?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93027-1 |
This is a Prapare Item Example 93027-1 (Are you a refugee?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93028-9 |
This is a Prapare Item Example 93028-9 (In the past year, have you spent more than 2 nights in a row in a jail, prison, detention center, or juvenile correctional facility?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93029-7 |
This is a Prapare Item Example 93029-7 (How often do you see or talk to people that you care about and feel close to (For example: talking to friends on the phone, visiting friends or family, going to church or club meetings)?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93030-5 |
This is a Prapare Item Example 93030-5 (Has lack of transportation kept you from medical appointments, meetings, work, or from getting things needed for daily living?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93033-9 |
This is a Prapare Item Example 93033-9 (Are you worried about losing your housing?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93034-7 |
This is a Prapare Item Example 93034-7 (Have you been discharged from the armed forces of the United States?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93035-4 |
This is a Prapare Item Example 93035-4 (At any point in the past 2 years, has season or migrant farm work been your or your family’s main source of income?) for the US Core Screening Response Observation Profile |
Prapare Item Example 93038-8 |
This is a Prapare Item Example 93038-8 (Stress is when someone feels tense, nervous, anxious or can’t sleep at night because their mind is troubled. How stressed are you?) for the US Core Screening Response Observation Profile |
Prapare Multiselect-Item Example 32624-9-Answer0 |
This is a Prapare Multiselect-Item Example 32624-9-Answer0 (Race) for the US Core Screening Response Observation Profile |
Prapare Multiselect-Item Example 32624-9-Answer1 |
This is a Prapare Multiselect-Item Example 32624-9-Answer1 (Race) for the US Core Screening Response Observation Profile |
Prapare Multiselect-Item Example 93031-3-Answer0 |
This is a Prapare Multiselect-Item Example 93031-3-Answer0 (In the past year, have you or any family members you live with been unable to get any of the following when it was really needed?) for the US Core Screening Response Observation Profile |
Prapare Multiselect-Item Example 93031-3-Answer1 |
This is a Prapare Multiselect-Item Example 93031-3-Answer1 (In the past year, have you or any family members you live with been unable to get any of the following when it was really needed?) for the US Core Screening Response Observation Profile |
Prapare Panel Example 93025-5 |
This is a Prapare Panel Example 93025-5 (Protocol for Responding to and Assessing Patients’ Assets, Risks, and Experiences [PRAPARE]) for the US Core Screening Response Observation Profile |
Prapare Panel Example 93039-6 |
This is a Prapare Panel Example 93039-6 (Optional additional questions) for the US Core Screening Response Observation Profile |
Prapare Panel Example 93040-4 |
This is a Prapare Panel Example 93040-4 (Social and emotional health) for the US Core Screening Response Observation Profile |
Prapare Panel Example 93041-2 |
This is a Prapare Panel Example 93041-2 (Money and resources) for the US Core Screening Response Observation Profile |
Prapare Panel Example 93042-0 |
This is a Prapare Panel Example 93042-0 (Family and home) for the US Core Screening Response Observation Profile |
PRAPARE Panel Example 93043-8 |
This is a Prapare Panel Example 93043-8 (Personal characteristics) for the US Core Screening Response Observation Profile |
PractitionerRole_Practitioner_Endpoint_Bundle_Example Example |
This is a PractitionerRole_Practitioner_Endpoint_Bundle_Example example for the Bundle Profile. |
Procedure R4 Defib Implant Example |
This is a Procedure R4 defib implant example for the US Core Procedure Profile. |
AHC HRSN Screening Example |
‘An example of an SDC QuestionnaireResponse that represents questions and selected answers from the Accountable health communities (AHC) health-related social needs screening (HRSN) tool in LOINC (code 96777-8). The example is generated using the LHC-Forms SDC Questionnaire App.’ |
PRAPARE Example |
‘An example of an US Core QuestionnaireResponse that represents questions and selected answers from the PRAPARE questionnaire represented in LOINC (code 93025-5). The example is generated using the LHC-Forms SDC Questionnaire App.’ |
Glascow Coma Score Example |
‘This example of a US Core QuestionnaireResponse illustrate using Questionnaire as a stand alone resource. It does not point to the definition of the questions in a FHIR Questionnaire, but represents the answers from a non FHIR survey instrument (in this case a pdf).’ |
Hunger Vital Sign [HVS] Example |
‘An example of an SDC QuestionnaireResponse that represents questions and selected answers from the Hunger Vital Sign Example questionnaire represented in LOINC (code 88122-7). The example is generated using the LHC-Forms SDC Questionnaire App.’ |
Acme Lab Example |
This is a acme lab example for the US Core Organization Profile. |
AllergyIntolerance Example |
This is a allergyintolerance example for the US Core AllergyIntolerance Profile. |
AllergyIntolerance Provenance Example |
This is a allergyintolerance provenance example for the Bundle Profile. |
Blood Pressure Example |
This is a blood pressure example for the Vitalsigns Profile. |
BMI Example |
This is a BMI example for the Vitalsigns Profile. |
BP Data Absent Example |
This is a bp data absent example for the Vitalsigns Profile showing how to reprsesent blood pressure with a missing diastolic measurement. |
Capillary refill Time Nail Bed Example |
This is a Capillary refill Time Nail Bed Example for the Clinical Test Result Observation Profile. |
CareTeam Example |
This is a careteam example for the US Core CareTeam Profile. |
Colonoscopy Example |
This is a colonoscopy example for the US Core CarePlan Profile. |
SDOH Problem/Health Concern Example |
This example of a US Core Condition Problems and Health Concerns Profile illustrates its use to capture information about a patient’s SDOH Problem/Health Concern. |
Encounter Diagnosis Example 1 |
This example of a US Core Condition Encounter Diagnosis Profile illustrates its use to capture information about a patient’s encounter diagnosis. |
Encounter Diagnosis Example 2 |
This example of a US Core Condition Encounter Diagnosis Profile illustrates its use to capture information about a patient’s encounter diagnosis. |
CBC Example |
This is a CBC example for the US Core DiagnosticReport Lab Profile. |
Metabolic Panel Example |
This is a metabolic panel example for the US Core DiagnosticReport Lab Profile. |
DXA Femur-L ArMass BMD Example |
This is a DXA Femur-L ArMass BMD Example for the Clinical Test Result Observation Profile. |
DXA Femur-L T-score BMD Example |
This is a DXA Femur-L T-score BMD Example for the Clinical Test Result Observation Profile. |
DXA Femur-L Z-score BMD Example |
This is a DXA Femur-L Z-score BMD Example for the Clinical Test Result Observation Profile. |
DXA Hip-L ArMass BMD Example |
This is a DXA Hip-L ArMass BMD Example for the Clinical Test Result Observation Profile. |
DXA Hip-L T-score BMD Example |
This is a DXA Hip-L T-score BMD Example for the Clinical Test Result Observation Profile. |
DXA Hip-L Z-score BMD Example |
This is a DXA Hip-L Z-score BMD Example for the Clinical Test Result Observation Profile. |
EKG impression Example |
This is a EKG impression Example for the Clinical Test Result Observation Profile. |
EKG lead Example |
This is a EKG lead Example for the Clinical Test Result Observation Profile. |
Encounter 1036 Example |
This is a encounter 1036 example for the Encounter Profile. |
Encounter Delivery Example |
This is a patient delivery encounter example for the Encounter Profile. |
Encounter 1 Example |
This is a encounter 1 example for the US Core Encounter Profile. |
Episode Summary Example |
This is a episode summary example for the US Core DocumentReference Profile. |
Organization 2 Example |
This is a organization 2 example for the US Core Organization Profile. |
ServiceRequest Example |
This is a service request example for the US Core ServiceRequest Profile Profile. |
Goal 1 Example |
This is a goal 1 example for the US Core Goal Profile. |
Goal 2 Example |
This is a goal 2 example for the US Core Goal Profile. |
Head Circumference Example |
This is a head circumference example for the US Core Head Circumference Profile. |
Health Concern Example |
This example of a US Core Condition Problems and Health Concerns Profile illustrates its use to capture information about a patient’s health concern. |
Heart rate rhythm Example |
This is a Heart rate rhythm Example for the Clinical Test Result Observation Profile. |
Heart Rate Example |
This is a heart rate example for the Vitalsigns Profile. |
Height Example |
This is a height example for the Vitalsigns Profile. |
HL7East Example |
This is a HL7East example for the US Core Location Profile. |
Imm 1 Example |
This is a imm 1 example for the US Core Immunization Profile. |
Jugular vein distension Example |
This is a Jugular vein distension Example for the Clinical Test Result Observation Profile. |
Length Example |
This is a length example for the Vitalsigns Profile which shows how body length (typically used for infants) is represented using 8306-3 -Body height - lying as an additional observation code. |
Hospital Location |
This is an example hospital location for the US Core Location Profile. |
Chest Xray Example |
This is an example Media xray image that is reference by the US Core DiagnosticReport Note Profile. |
EKG Strip Image |
This is an example Media image that is reference by the US Core DiagnosticReport Note Profile. |
Blood Glucose Example |
This is a blood glucose example for the US Core Observation Lab Profile. |
BUN Example |
This is a BUN example for the US Core Observation Lab Profile. |
Erythrocytes Example |
This is a erythrocytes example for the US Core Observation Lab Profile. |
Hemoglobin Example |
This is a hemoglobin example for the US Core Observation Lab Profile. |
MCHC Example |
This is a MCHC example for the US Core Observation Lab Profile. |
Neutrophils Example |
This is a neutrophils example for the US Core Observation Lab Profile. |
Observation SatO2 FiO2 Example |
This is a observation satO2 fiO2 example for the US Core Pulse Oximetry Profile representing a spO2 value with a for a patient on 6 l/min of O2 suppplemental oxygen. |
Serum Calcium Example |
This is a serum calcium example for the US Core Observation Lab Profile. |
Serum Chloride Example |
This is a serum chloride example for the US Core Observation Lab Profile. |
Serum CO2 Example |
This is a serum CO2 example for the US Core Observation Lab Profile. |
Serum Creatinine Example |
This is a serum creatinine example for the US Core Observation Lab Profile. |
Serum Potassium Example |
This is a serum potassium example for the US Core Observation Lab Profile. |
Serum Sodium Example |
This is a serum sodium example for the US Core Observation Lab Profile. |
Serum Total Bilirubin Example |
This is a serum total bilirubin example for the US Core Observation Lab Profile. |
Xray Chest Findings Example |
This example of a US Core Observation Imaging Result Profile illustrates its use to capture information about a patient’s radiology study findings. |
Xray Chest Impression Example |
This example of a US Core Observation Imaging Result Profile illustrates its use to capture information about a patient’s radiology study impression. |
OFC Percentile Example |
This is a OFC percentile example for the Head Occipital Frontal Circumference Percentile Profile. |
Oxygen Saturation Example |
This is a typical oxygen saturation example for the US Core Pulse Oximetry Profile on room air where no oxygen concentration is recorded. |
P-R interval {EKG lead} Example |
This is a P-R interval {EKG lead} Example for the Clinical Test Result Observation Profile. |
Patient Child Example |
This is a patient child example for the US Core Patient Profile. |
Patient Example |
This is a patient example for the US Core Patient Profile. |
Patient Infant Example |
This is a patient infant example for the US Core Patient Profile. |
Pediatric BMI Example |
This is a pediatric BMI example for the Pediatric BMI For Age Profile. |
Pediatric Wt Example |
This is a pediatric wt example for the Pediatric Weight For Height Profile. |
Practitioner 1 Example |
This is a practitioner 1 example for the US Core Practitioner Profile. |
Practitioner 2 Example |
This is a practitioner 2 example for the US Core Practitioner Profile. |
Pulse intensity Palpation Example |
This is a Pulse intensity Palpation Example for the Clinical Test Result Observation Profile. |
Q-T interval {EKG lead} Example |
This is a Q-T interval {EKG lead} Example for the Clinical Test Result Observation Profile. |
QRS dur {EKG lead} Example |
This is a QRS dur {EKG lead} Example for the Clinical Test Result Observation Profile. |
Rehab Example |
This is a rehab example for the US Core Procedure Profile. |
Patient Niece Example |
This is a patient niece example for the US Core RelatedPerson Profile Profile. |
Respiratory Rate Example |
This is a respiratory rate example for the Vitalsigns Profile. |
Saint Luke W Endpoint Example |
This is a saint luke w endpoint example for the US Core Organization Profile. |
Self Tylenol Example |
This is a self tylenol example for the MedicationRequest Profile. |
Sexual Orientation Observation Example |
This is an sexual orientation example for the US Core Observation Sexual Orientation Profile. |
Social History Assessment Example |
This is a Social History Assessment Example for the US Core Observation Social History Profile. |
Some Day Smoker Example |
This is a some day smoker example for the US Core Smokingstatus Profile. |
Temperature Example |
This is a temperature example for the Vitalsigns Profile. |
UDI 1 Example |
This is a UDI 1 example for the US Core Implantable Device Profile. |
Urobilinogen Example |
This is a urobilinogen example for the US Core Observation Lab Profile. |
Uscore Med1 Example |
This is a uscore med1 example for the US Core Medication Profile. |
Uscore Med2 Example |
This is a uscore med2 example for the US Core Medication Profile. |
Uscore MO1 Example |
This is a uscore mo1 example for the US Core MedicationRequest Profile. |
Uscore MO2 Example |
This is a uscore MO2 example for the US Core MedicationRequest Profile. |
Uscore MO3 Example |
This is a uscore mo3 example for the Bundle Profile. |
Weight Example |
This is a weight example for the Vitalsigns Profile. |