QI-Core Implementation Guide
4.1.1 - STU 4.1.1 US

This page is part of the Quality Improvement Core Framework (v4.1.1: STU 4) 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

QI-Core Profiles

The following table lists the QI-Core profiles that are part of the IG, which USCore profile they are derived from, if any, and the underlying FHIR resources:

QI-Core Profile USCore Profile Base Resource
QICoreAdverseEvent   AdverseEvent
QICoreAllergyIntolerance USCoreAllergyIntolerance AllergyIntolerance
QICoreBodyStructure   BodyStructure
QICoreCarePlan USCoreCarePlan CarePlan
QICoreCareTeam USCoreCareTeam CareTeam
QICoreClaim   Claim
QICoreCommunication   Communication
QICoreCommunicationNotDone   Communication
QICoreCommunicationRequest   CommunicationRequest
QICoreCondition USCoreCondition Condition
QICoreCoverage   Coverage
QICoreDevice   Device
QICoreDeviceNotRequested   DeviceRequest
QICoreDeviceRequest   DeviceRequest
QICoreDeviceUseStatement   DeviceUseStatement
QICoreDiagnosticReportLab USCoreDiagnosticReportLab DiagnosticReport
QICoreDiagnosticReportNote USCoreDiagnosticReportNote DiagnosticReport
QICoreEncounter USCoreEncounter Encounter
QICoreFamilyMemberHistory   FamilyMemberHistory
QICoreFlag   Flag
QICoreGoal USCoreGoal Goal
QICoreImagingStudy   ImagingStudy
QICoreImmunization USCoreImmunization Immunization
QICoreImmunizationEvaluation   ImmunizationEvaluation
QICoreImmunizationNotDone USCoreImmunization Immunization
QICoreImmunizationRecommendation   ImmunizationRecommendation
  USCoreImplantableDeviceProfile Device
QICoreLocation USCoreLocation Location
QICoreMedication USCoreMedication Medication
QICoreMedicationAdministration   MedicationAdministration
QICoreMedicationAdministrationNotDone   MedicationAdministration
QICoreMedicationDispense   MedicationDispense
QICoreMedicationDispenseNotDone   MedicationDispense
QICoreMedicationNotRequested USCoreMedicationRequest MedicationRequest
QICoreMedicationRequest USCoreMedicationRequest MedicationRequest
QICoreMedicationStatement   MedicationStatement
QICoreNutritionOrder   NutritionOrder
QICoreObservation   Observation
QICoreObservationNotDone   Observation
  FHIR Vital Signs Observation
  USCore Smoking Status Observation
  USCore Laboratory Result Observation
  USCore Pediatric BMI for Age Observation
  USCore Pediatric Weight for Height Observation
  USCore Pulse Oximetry Observation
QICoreOrganization USCoreOrganization Organization
QICorePatient USCorePatient Patient
QICorePractitioner USCorePractitioner Practitioner
QICorePractitionerRole USCorePractitionerRole PractitionerRole
QICoreProcedure USCoreProcedure Procedure
QICoreProcedureNotDone USCoreProcedure Procedure
QICoreRelatedPerson   RelatedPerson
QICoreServiceNotRequested   ServiceRequest
QICoreServiceRequest   ServiceRequest
QICoreSpecimen   Specimen
QICoreSubstance   Substance
QICoreTask   Task
QICoreTaskNotDone   Task

Referencing QI-Core Profiles

There are a number of QI-Core profiles inherit directly from US Core profiles, if any, or other FHIR resources (i.e. USCoreImplantableDeviceProfile, FHIR VitalSigns, USCore Smoking Status etc.) and the underlying Reference elements can address the US Core or FHIR profiles for the items referenced. For any other references to base FHIR resources or not formally defined in a QI-Core Profile, the referenced resource SHOULD be a QI-Core Profile if a QI-Core Profile exists for the resource type. For example, USCore Smoking Status references US Core Patient profile, the reference to Patient SHOULD be a valid QI-Core Patient.


STU Note: Mappings from the QI Core Profiles to Quality Data Model have been removed from this version of the QI Core IG. The CQI Work Group is seeking implementer feedback on the value of these mappings and whether they would be useful to include in a future version of the specification. Mappings from QDM-to-QI-Core are still available on the QDM-to-QI-Core page, and the FHIR-to-QDM mappings are still available in the mappings section for each profile in the STU3.2 version of this implementation guide.