2026 US Quality Core Implementation Guide
0.5.0 - release United States of America flag

2026 US Quality Core Implementation Guide - Downloaded Version 0.5.0 See the Directory of published versions

CapabilityStatement: US Quality Core Server CapabilityStatement

Official URL: http://fhir.org/guides/onc/us-quality-core/CapabilityStatement/us-quality-core-server Version: 0.5.0
Active as of 2026-06-05 Computable Name: USQualityCoreServerCapabilityStatement

This capability statement describes the expected capabilities of the US Quality Core Servers which is responsible for responding to USCDI+ Quality V1 queries submitted by US Quality Core Clients. It describes a minimum set of FHIR RESTful operations and search parameters necessary to enable access to the set of USCDI+ Quality V1 data that is in scope of this implementation guide. For more information about which USCDI+ Quality data elements are in scope, please review the USCDI+ Quality section of this implementation guide.

US Quality Core Servers SHALL support the capabilities described in the US Core Server CapabilityStatement STU6.1. Some RESTFUL operations and search parameters described in the US Quality Core Server CapabilityStatement are redundant to the US Core Server CapabilityStatement, but are listed here to highlight which capabilities are specifically relevant to USCDI+ Quality V1.

The US Quality Core Implementation Guide v0.5.0 is derived from the QI-Core Implementation Guide STU6. It adopts all profiles within the QI-Core Implementation Guide STU6 to enable a more seamless adoption of this implementation guide. However, only those profiles that contain USCDI+ Quality V1 data are required to be supported by US Quality Core Servers. The FHIR RESTful operations and search parameters in this capability statement reflects this scope.

Raw OpenAPI-Swagger Definition file | Download

Language: en

US Quality Core Server CapabilityStatement

  • Implementation Guide Version: 0.5.0
  • FHIR Version: 4.0.1
  • Supported Formats: json
  • Published on: 2026-06-05
  • Published by: Office of the National Coordinator for Health Information Technology (ONC)

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

The US Quality Core Server SHALL:

  1. Conform to requirements provided in the US Core Server CapabilityStatement and the base FHIR specification
  2. Support all US Quality Core and US Core profiles that contain at least one in-scope USCDI+ Quality data element, as described in the USCDI+ Quality page
  3. Support all interactions, search parameters, and combined search parameters that have SHALL conformance expectations as described in this CapabilityStatement
  4. Support all USCDI+ Quality flagged data elements, and those flagged as MustSupport from underlying US Core profiles
  5. Ensure resources in 'Any' references conform to US Quality Core profiles if the base resource has a US Quality Core profile
  6. Implement the RESTful behavior according to the FHIR specification for all interactions in this CapabilityStatement
  7. Support JSON source formats for all interactions in this CapabilityStatement

NOTE: US Quality Core and US Core SearchParameters referenced in this CapabilityStatement that are derived from standard FHIR SearchParameters are only defined to document Server and Client expectations, such as comparator expectations, and to support generation tooling. They SHALL NOT be interpreted as search parameters for searching. Actual searches use the standard FHIR SearchParameters.

Summary of System-wide Interactions
  • MAY support the transactioninteraction.
  • MAY support the batchinteraction.
  • MAY support the search-systeminteraction.
  • MAY support the history-systeminteraction.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
AdverseEventSupported Profiles
  US Quality Core AdverseEvent
YYsubject, event, recorded-date, subject+event, subject+recorded-dateProvenance:target
AllergyIntoleranceSupported Profiles
  US Quality Core AllergyIntolerance
YYpatientProvenance:target
CarePlanSupported Profiles
  US Quality Core CarePlan
YYpatient, category, patient+categoryProvenance:target
CareTeamSupported Profiles
  US Quality Core CareTeam
YYpatient, status, patient+statusProvenance:target
ConditionSupported Profiles
  US Quality Core Condition Encounter Diagnosis
  US Quality Core Condition Problems Health Concerns
YYpatient, category, code, patient+category, patient+codeProvenance:target
CoverageSupported Profiles
  US Quality Core Coverage
YYpatientProvenance:target
DeviceRequestSupported Profiles
  US Quality Core DeviceRequest
  US Quality Core Device Not Requested
YYpatient, code, do-not-perform, patient+code, patient+do-not-performProvenance:target
DiagnosticReportSupported Profiles
  US Quality Core DiagnosticReport Profile for Report and Note Exchange
  US Quality Core DiagnosticReport Profile for Laboratory Results Reporting
YYpatient, category, code, date, patient+category, patient+category+date, patient+codeProvenance:target
DocumentReferenceSupported Profiles
  US Core DocumentReference Profileversion: 6.1.0)
YYpatient, _id, category, date, type, patient+type, patient+category, patient+category+dateProvenance:target
EncounterSupported Profiles
  US Quality Core Encounter
YY_id, patient, type, date, patient+type, patient+dateProvenance:target
FamilyMemberHistorySupported Profiles
  US Quality Core FamilyMemberHistory
YYpatientProvenance:target
GoalSupported Profiles
  US Quality Core Goal
YYpatientProvenance:target
ImmunizationSupported Profiles
  US Quality Core Immunization
  US Quality Core Immunization Not Done
YYpatient, status, patient+statusProvenance:target
LocationSupported Profiles
  US Quality Core Location
Y
MedicationSupported Profiles
  US Quality Core Medication
YYcode
MedicationAdministrationSupported Profiles
  US Quality Core MedicationAdministration
  US Quality Core MedicationAdministration Not Done
YYpatient, status, code, effective-time, patient+status, patient+code, patient+effective-timeProvenance:target
MedicationDispenseSupported Profiles
  US Quality Core MedicationDispense
  US Quality Core MedicationDispense Declined
YYpatient, status, patient+statusProvenance:target
MedicationRequestSupported Profiles
  US Quality Core MedicationRequest
  US Quality Core Medication Not Requested
YYpatient, intent, do-not-perform, patient+intent+do-not-perform, patient+intentProvenance:target
ObservationSupported Profiles
  US Quality Core Observation Clinical Result
  US Quality Core Simple Observation
  US Quality Core Observation Screening Assessment
  US Quality Core Observation Cancelled
  US Core Observation Pregnancy Intent Profileversion: 6.1.0)
  US Core Observation Pregnancy Status Profileversion: 6.1.0)
  US Core Smoking Status Observation Profileversion: 6.1.0)
  US Quality Core Laboratory Result Observation
  US Core Observation Occupation Profileversion: 6.1.0)
  US Core Blood Pressure Profileversion: 6.1.0)
  US Core BMI Profileversion: 6.1.0)
  US Core Pediatric BMI for Age Observation Profileversion: 6.1.0)
  US Core Body Height Profileversion: 6.1.0)
  US Core Body Temperature Profileversion: 6.1.0)
  US Core Body Weight Profileversion: 6.1.0)
  US Core Pediatric Head Occipital Frontal Circumference Percentile Profileversion: 6.1.0)
  US Core Heart Rate Profileversion: 6.1.0)
  US Core Pulse Oximetry Profileversion: 6.1.0)
  US Core Respiratory Rate Profileversion: 6.1.0)
  US Core Pediatric Weight for Height Observation Profileversion: 6.1.0)
YYpatient, category, status, code, date, patient+category+status, patient+category, patient+category+date, patient+codeProvenance:target
OrganizationSupported Profiles
  US Quality Core Organization
Yy?
PatientSupported Profiles
  US Quality Core Patient
YY_idProvenance:target
PractitionerSupported Profiles
  US Quality Core Practitioner
Y
PractitionerRoleSupported Profiles
  US Quality Core PractitionerRole
Y
ProcedureSupported Profiles
  US Quality Core Procedure
  US Quality Core Procedure Not Done
YYpatient, status, date, patient+status, patient+dateProvenance:target
ProvenanceSupported Profiles
  US Core Provenance Profileversion: 6.1.0)
Yy?
RelatedPersonSupported Profiles
  US Quality Core RelatedPerson
YY_id, patientProvenance:target
ServiceRequestSupported Profiles
  US Quality Core ServiceRequest
  US Quality Core Service Not Requested
YY_id, patient, category, code, authored, do-not-perform, patient+category, patient+category+authored, patient+code, patient+do-not-performProvenance:target
SpecimenSupported Profiles
  US Core Specimen Profileversion: 6.1.0)
YYpatient, _id
TaskSupported Profiles
  US Quality Core Task
  US Quality Core Task Rejected
YYpatient, status, code, patient+status, patient+codeProvenance:target

Core FHIR Resource
AdverseEvent
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
subject Added in US Quality Core. Supports subject-scoped retrieval of AdverseEvent resources for quality reporting. This US Quality Core-specific search is needed because AdverseEvent is in scope for USCDI+ Quality but is not profiled by US Core 6.1.0.
subject + event Added in US Quality Core. Supports subject-scoped retrieval filtered by adverse event concept. This US Quality Core-specific combination makes the adverse event concept available as a primary retrieval path for quality logic.
subject + recorded-date Added in US Quality Core. Supports subject-scoped retrieval filtered by recorded date so quality workflows can constrain adverse events to relevant reporting periods.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLsubjectreference

The client SHALL provide an id value for the reference.

MAYeventtoken

The client MAY provide a code value.

MAYrecorded-datedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLsubject+eventreference+token
SHALLsubject+recorded-datereference+date
Core FHIR Resource
AllergyIntolerance
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of allergy and intolerance data needed for in-scope USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
CarePlan
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core CarePlan

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient + category Required by US Core. Supports patient-scoped retrieval of care plans filtered to the category relevant for USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
MAYpatientreference

The client SHALL provide an id value for the reference.

MAYcategorytoken

The client MAY provide a code value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+categoryreference+token
Core FHIR Resource
CareTeam
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core CareTeam

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient + status Required by US Core. Supports patient-scoped retrieval of care teams filtered by status for quality workflows.
Search Parameters
ConformanceParameterTypeDocumentation
MAYpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a code value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
Core FHIR Resource
Condition
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of conditions needed for in-scope USCDI+ Quality data access.
patient + category Required by US Core. Supports patient-scoped retrieval filtered by condition category, including problem, health concern, and encounter diagnosis use cases.
patient + code Added in US Quality Core. Supports patient-scoped retrieval filtered by condition code. US Quality Core makes this combination explicit as a primary retrieval path for quality logic that filters by diagnosis, problem, or health concern code.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYcategorytoken

The client MAY provide a category.

MAYcodetoken

The client MAY provide a code value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+categoryreference+token
SHALLpatient+codereference+token
Core FHIR Resource
Coverage
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core Coverage

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of coverage data needed for in-scope USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
DeviceRequest
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Added in US Quality Core. Supports patient-scoped retrieval of device requests for quality reporting. This US Quality Core-specific search is needed because DeviceRequest is in scope for USCDI+ Quality but is not profiled by US Core 6.1.0.
patient + code Added in US Quality Core. Supports patient-scoped retrieval filtered by requested device code. This US Quality Core-specific combination makes the device code available as a primary retrieval path for quality logic.
patient + do-not-perform Added in US Quality Core. Supports negation workflows by enabling retrieval of device requests that indicate the requested action should not be performed.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYcodetoken

The client MAY provide a code value.

MAYdo-not-performtoken

The client MAY provide a token value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+codereference+token
SHALLpatient+do-not-performreference+token
Core FHIR Resource
DiagnosticReport
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of diagnostic reports needed for in-scope USCDI+ Quality data access.
patient + category Required by US Core. Supports patient-scoped retrieval filtered by report category, including laboratory and clinical-note report categories.
patient + category + date Required by US Core. Supports patient-scoped retrieval filtered by report category and date so quality workflows can constrain reports to relevant reporting periods.
patient + code Required by US Core. Supports patient-scoped retrieval filtered by report code, including code-oriented retrieval paths used by quality logic.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYcategorytoken

The client MAY provide a category.

MAYcodetoken

The client MAY provide a code value.

MAYdatedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+categoryreference+token
SHALLpatient+category+datereference+token+date
SHALLpatient+codereference+token
Core FHIR Resource
DocumentReference
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports search retrieval of a known DocumentReference by resource id.
patient Required by US Core. Supports patient-scoped retrieval of document references needed for in-scope USCDI+ Quality data access.
patient + type Required by US Core. Supports patient-scoped retrieval filtered by document type, including clinical note type retrieval.
patient + category Required by US Core. Supports patient-scoped retrieval filtered by document category.
patient + category + date Required by US Core. Supports patient-scoped retrieval filtered by document category and date so quality workflows can constrain documents to relevant reporting periods.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

SHALL_idtoken

The client SHALL provide a token value.

MAYcategorytoken

The client MAY provide a token value.

MAYdatedate

The client MAY provide a date value.

MAYtypetoken

The client MAY provide a token value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+typereference+token
SHALLpatient+categoryreference+token
SHALLpatient+category+datereference+token+date
Core FHIR Resource
Encounter
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core Encounter

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports search retrieval of a known Encounter by resource id.
patient Required by US Core. Supports patient-scoped retrieval of encounters needed for in-scope USCDI+ Quality data access.
patient + type Added in US Quality Core. Supports patient-scoped retrieval filtered by encounter type. US Quality Core makes this combination explicit as a primary retrieval path for quality logic that filters by visit or service type.
patient + date Required by US Core. Supports patient-scoped retrieval filtered by encounter date so quality workflows can constrain encounters to relevant reporting periods.
Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

The client SHALL provide an id value.

SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYtypetoken

The client MAY provide a code value.

MAYdatedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+typereference+token
SHALLpatient+datereference+date
Core FHIR Resource
FamilyMemberHistory
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Added in US Quality Core. Supports patient-scoped retrieval of family member history for quality reporting. This US Quality Core-specific search is needed because FamilyMemberHistory is in scope for USCDI+ Quality but is not profiled by US Core 6.1.0.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
Goal
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core Goal

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of goals needed for in-scope USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
Immunization
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of immunizations needed for in-scope USCDI+ Quality data access.
patient + status Added in US Quality Core. Supports patient-scoped retrieval filtered by immunization status. US Quality Core makes this combination explicit for status-sensitive quality workflows, including not-done immunization cases.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a status.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
Core FHIR Resource
Location
Reference Policy
resolves
Interaction summary
  • SHALL support read.

Supported Profiles

US Quality Core Location

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. US Quality Core does not define additional required individual search parameters or required search parameter combinations for this resource. Implementations still support the required interactions in this CapabilityStatement and any applicable US Core requirements independently.

Core FHIR Resource
Medication
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core Medication

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
code Added in US Quality Core. Supports retrieval of Medication resources by clinical code. This search is included as a primary code path for quality logic when Medication is represented as a referenced resource.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLcodetoken

The client SHALL provide a code value.

 
Core FHIR Resource
MedicationAdministration
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Added in US Quality Core. Supports patient-scoped retrieval of medication administrations for quality reporting. This US Quality Core-specific search is needed because MedicationAdministration is in scope for USCDI+ Quality but is not profiled by US Core 6.1.0.
patient + status Added in US Quality Core. Supports patient-scoped retrieval filtered by administration status for status-sensitive quality workflows.
patient + code Added in US Quality Core. Supports patient-scoped retrieval filtered by medication code. This US Quality Core-specific combination makes the medication code available as a primary retrieval path for quality logic.
patient + effective-time Added in US Quality Core. Supports patient-scoped retrieval filtered by administration time so quality workflows can constrain administrations to relevant reporting periods.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a status.

MAYcodetoken

The client MAY provide a code value.

MAYeffective-timedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
SHALLpatient+codereference+token
SHALLpatient+effective-timereference+date
Core FHIR Resource
MedicationDispense
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of medication dispenses needed for in-scope USCDI+ Quality data access.
patient + status Added in US Quality Core. Supports patient-scoped retrieval filtered by dispense status. US Quality Core makes this combination explicit for status-sensitive quality workflows, including declined dispense cases.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a status.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
Core FHIR Resource
MedicationRequest
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient + intent + do-not-perform Added in US Quality Core. Supports negation workflows by enabling retrieval of medication requests that indicate the requested medication should not be performed, while preserving the patient and intent context.
patient + intent Required by US Core. Supports patient-scoped retrieval of medication requests filtered by intent, including medication orders relevant to quality reporting.
Search Parameters
ConformanceParameterTypeDocumentation
MAYpatientreference

The client SHALL provide an id value for the reference.

MAYintenttoken

The client MAY provide a token value.

MAYdo-not-performtoken

The client MAY provide a token value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+intent+do-not-performreference+token+token
SHALLpatient+intentreference+token
Core FHIR Resource
Observation
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient + category + status Added in US Quality Core. Supports patient-scoped retrieval filtered by observation category and status. US Quality Core makes this combination explicit for status-sensitive quality workflows, including cancelled or otherwise not-final observations.
patient + category Required by US Core. Supports patient-scoped retrieval filtered by observation category for in-scope USCDI+ Quality data access.
patient + category + date Required by US Core. Supports patient-scoped retrieval filtered by category and date so quality workflows can constrain observations to relevant reporting periods.
patient + code Required by US Core. Supports patient-scoped retrieval filtered by observation code, including primary code paths used by quality logic.
Search Parameters
ConformanceParameterTypeDocumentation
MAYpatientreference

The client SHALL provide an id value for the reference.

MAYcategorytoken

The client MAY provide a category.

MAYstatustoken

The client MAY provide a status.

MAYcodetoken

The client MAY provide a code value.

MAYdatedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+category+statusreference+token+token
SHALLpatient+categoryreference+token
SHALLpatient+category+datereference+token+date
SHALLpatient+codereference+token
Core FHIR Resource
Organization
Reference Policy
resolves
Interaction summary
  • SHALL support read.
  • MAY support search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. US Quality Core does not define additional required individual search parameters or required search parameter combinations for this resource. Implementations still support the required interactions in this CapabilityStatement and any applicable US Core requirements independently.

Core FHIR Resource
Patient
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Supported Profiles

US Quality Core Patient

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports retrieval of a known Patient by resource id, which is the normal starting point for patient-scoped USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

The client SHALL provide an id value.

 
Core FHIR Resource
Practitioner
Reference Policy
resolves
Interaction summary
  • SHALL support read.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. US Quality Core does not define additional required individual search parameters or required search parameter combinations for this resource. Implementations still support the required interactions in this CapabilityStatement and any applicable US Core requirements independently.

Core FHIR Resource
PractitionerRole
Reference Policy
resolves
Interaction summary
  • SHALL support read.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. US Quality Core does not define additional required individual search parameters or required search parameter combinations for this resource. Implementations still support the required interactions in this CapabilityStatement and any applicable US Core requirements independently.

Core FHIR Resource
Procedure
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Required by US Core. Supports patient-scoped retrieval of procedures needed for in-scope USCDI+ Quality data access.
patient + status Added in US Quality Core. Supports patient-scoped retrieval filtered by procedure status. US Quality Core makes this combination explicit for status-sensitive quality workflows, including not-done procedure cases.
patient + date Required by US Core. Supports patient-scoped retrieval filtered by procedure date so quality workflows can constrain procedures to relevant reporting periods.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a status.

MAYdatedate

The client MAY provide a date value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
SHALLpatient+datereference+date
Core FHIR Resource
Provenance
Reference Policy
resolves
Interaction summary
  • SHALL support read.
  • MAY support search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. US Quality Core does not define additional required individual search parameters or required search parameter combinations for this resource. Implementations still support the required interactions in this CapabilityStatement and any applicable US Core requirements independently.

Core FHIR Resource
RelatedPerson
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports search retrieval of a known RelatedPerson by resource id.
patient Added in US Quality Core. Supports retrieval of related persons associated with a patient for in-scope USCDI+ Quality data access.
Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

The client SHALL provide an id value.

SHALLpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
ServiceRequest
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports search retrieval of a known ServiceRequest by resource id.
patient Required by US Core. Supports patient-scoped retrieval of service requests needed for in-scope USCDI+ Quality data access.
patient + category Required by US Core. Supports patient-scoped retrieval filtered by service request category.
patient + category + authored Required by US Core. Supports patient-scoped retrieval filtered by category and authored date so quality workflows can constrain service requests to relevant reporting periods.
patient + code Required by US Core. Supports patient-scoped retrieval filtered by service request code, including primary code paths used by quality logic.
patient + do-not-perform Added in US Quality Core. Supports negation workflows by enabling retrieval of service requests that indicate the requested action should not be performed.
Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

The client SHALL provide an id value.

SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYcategorytoken

The client MAY provide a category.

MAYcodetoken

The client MAY provide a code value.

MAYauthoreddate

The client MAY provide a date value.

MAYdo-not-performtoken

The client MAY provide a token value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+categoryreference+token
SHALLpatient+category+authoredreference+token+date
SHALLpatient+codereference+token
SHALLpatient+do-not-performreference+token
Core FHIR Resource
Specimen
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
_id Required by US Core. Supports search retrieval of a known Specimen by resource id, including specimens referenced by quality-relevant observations and diagnostic reports.
Search Parameters
ConformanceParameterTypeDocumentation
SHALL_idtoken

The client SHALL provide a token value.

MAYpatientreference

The client SHALL provide an id value for the reference.

 
Core FHIR Resource
Task
Reference Policy
resolves
Interaction summary
  • SHALL support read, search-type.

Documentation

Search requirements are selected according to the rules described in Search Requirement Selection. The table below summarizes why each required individual search or required search parameter combination is included for this resource.

Required search US Core alignment Rationale
patient Added in US Quality Core. Supports patient-scoped retrieval of tasks for quality reporting. This US Quality Core-specific search is needed because Task is in scope for USCDI+ Quality but is not profiled by US Core 6.1.0.
patient + status Added in US Quality Core. Supports patient-scoped retrieval filtered by task status for status-sensitive quality workflows.
patient + code Added in US Quality Core. Supports patient-scoped retrieval filtered by task code. This US Quality Core-specific combination makes the task code available as a primary retrieval path for quality logic.
Search Parameters
ConformanceParameterTypeDocumentation
SHALLpatientreference

The client SHALL provide an id value for the reference.

MAYstatustoken

The client MAY provide a status.

MAYcodetoken

The client MAY provide a code value.

Combined Search Parameters
ConformanceParametersTypes
SHALLpatient+statusreference+token
SHALLpatient+codereference+token