2026 US Quality Core Implementation Guide
0.5.0 - release

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

## CapabilityStatement: US Quality Core Client CapabilityStatement

Official URL: http://fhir.org/guides/onc/us-quality-core/CapabilityStatement/us-quality-core-client | Version: 0.5.0 | Highlight text changes?
Active as of 2026-06-05 | Computable Name: USQualityCoreClientCapabilityStatement

This capability statement describes the expected capabilities of the US Quality Core Client which is responsible for initiating queries for USCDI+ Quality V1 data from US Quality Core Servers. The set of FHIR RESTful operations and search parameters required to be supported by US Quality Core Servers is provided in the US Quality Core Server Capability Statement. US Quality Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.

Raw OpenAPI-Swagger Definition file | Download

Language: en

## US Quality Core Client 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

- http://fhir.org/guides/onc/us-quality-core/ImplementationGuide/fhir.onc.us-quality-core

## FHIR RESTful Capabilities

### Mode: `client`

The US Quality Core Client SHALL:

1. Support fetching and querying US Quality Core and US Core profiles that contain at least one in-scope USCDI+ Quality data element, using the supported RESTful interactions and search parameters declared in the US Quality Core Server CapabilityStatement
2. Recognize and process all MustSupport and USCDI+ Quality flagged elements in US Quality Core, and all MustSupport elements in in-scope US Core profiles
3. Treat all modifying attributes as MustSupport, even if not explicitly declared
4. SHALL NOT process resource instances that include unknown modifying attributes
5. Be simultaneously conformant with US Quality Core profiles and US Core profiles. As such, the more restrictive bindings between US Core and US Quality Core SHALL be adhered to. For example, all value sets that are required in US Core SHALL be required by US Quality Core, regardless of the binding strength in US Quality Core.

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 `transaction`interaction.
- MAY support the `batch`interaction.
- MAY support the `search-system`interaction.
- MAY support the `history-system`interaction.

### 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 Type | Profile | R | S | U | C | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
AdverseEvent | Supported Profiles US Quality Core AdverseEvent | Y | Y |  |  | subject, event, recorded-date, subject+event, subject+recorded-date |  | `Provenance:target` |
AllergyIntolerance | Supported Profiles US Quality Core AllergyIntolerance | Y | Y |  |  | patient |  | `Provenance:target` |
CarePlan | Supported Profiles US Quality Core CarePlan | Y | Y |  |  | patient, category, patient+category |  | `Provenance:target` |
CareTeam | Supported Profiles US Quality Core CareTeam | Y | Y |  |  | patient, status, patient+status |  | `Provenance:target` |
Condition | Supported Profiles US Quality Core Condition Encounter Diagnosis US Quality Core Condition Problems Health Concerns | Y | Y |  |  | patient, category, code, patient+category, patient+code |  | `Provenance:target` |
Coverage | Supported Profiles US Quality Core Coverage | Y | Y |  |  | patient |  | `Provenance:target` |
DeviceRequest | Supported Profiles US Quality Core DeviceRequest US Quality Core Device Not Requested | Y | Y |  |  | patient, code, do-not-perform, patient+code, patient+do-not-perform |  | `Provenance:target` |
DiagnosticReport | Supported Profiles US Quality Core DiagnosticReport Profile for Report and Note Exchange US Quality Core DiagnosticReport Profile for Laboratory Results Reporting | Y | Y |  |  | patient, category, code, date, patient+category, patient+category+date, patient+code |  | `Provenance:target` |
DocumentReference | Supported Profiles US Core DocumentReference Profileversion: 6.1.0) | Y | Y |  |  | patient, _id, category, date, type, patient+type, patient+category, patient+category+date |  | `Provenance:target` |
Encounter | Supported Profiles US Quality Core Encounter | Y | Y |  |  | _id, patient, type, date, patient+type, patient+date |  | `Provenance:target` |
FamilyMemberHistory | Supported Profiles US Quality Core FamilyMemberHistory | Y | Y |  |  | patient |  | `Provenance:target` |
Goal | Supported Profiles US Quality Core Goal | Y | Y |  |  | patient |  | `Provenance:target` |
Immunization | Supported Profiles US Quality Core Immunization US Quality Core Immunization Not Done | Y | Y |  |  | patient, status, patient+status |  | `Provenance:target` |
Location | Supported Profiles US Quality Core Location | Y |  |  |  |  |  |  |
Medication | Supported Profiles US Quality Core Medication | Y | Y |  |  | code |  |  |
MedicationAdministration | Supported Profiles US Quality Core MedicationAdministration US Quality Core MedicationAdministration Not Done | Y | Y |  |  | patient, status, code, effective-time, patient+status, patient+code, patient+effective-time |  | `Provenance:target` |
MedicationDispense | Supported Profiles US Quality Core MedicationDispense US Quality Core MedicationDispense Declined | Y | Y |  |  | patient, status, patient+status |  | `Provenance:target` |
MedicationRequest | Supported Profiles US Quality Core MedicationRequest US Quality Core Medication Not Requested | Y | Y |  |  | patient, intent, do-not-perform, patient+intent+do-not-perform, patient+intent |  | `Provenance:target` |
Observation | Supported 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) | Y | Y |  |  | patient, category, status, code, date, patient+category+status, patient+category, patient+category+date, patient+code |  | `Provenance:target` |
Organization | Supported Profiles US Quality Core Organization | Y | y? |  |  |  |  |  |
Patient | Supported Profiles US Quality Core Patient | Y | Y |  |  | _id |  | `Provenance:target` |
Practitioner | Supported Profiles US Quality Core Practitioner | Y |  |  |  |  |  |  |
PractitionerRole | Supported Profiles US Quality Core PractitionerRole | Y |  |  |  |  |  |  |
Procedure | Supported Profiles US Quality Core Procedure US Quality Core Procedure Not Done | Y | Y |  |  | patient, status, date, patient+status, patient+date |  | `Provenance:target` |
Provenance | Supported Profiles US Core Provenance Profileversion: 6.1.0) | Y | y? |  |  |  |  |  |
RelatedPerson | Supported Profiles US Quality Core RelatedPerson | Y | Y |  |  | _id, patient |  | `Provenance:target` |
ServiceRequest | Supported Profiles US Quality Core ServiceRequest US Quality Core Service Not Requested | Y | Y |  |  | _id, patient, category, code, authored, do-not-perform, patient+category, patient+category+authored, patient+code, patient+do-not-perform |  | `Provenance:target` |
Specimen | Supported Profiles US Core Specimen Profileversion: 6.1.0) | Y | Y |  |  | patient, _id |  |  |
Task | Supported Profiles US Quality Core Task US Quality Core Task Rejected | Y | Y |  |  | patient, status, code, patient+status, patient+code |  | `Provenance:target` |

#### Resource Conformance: SHALLAdverseEvent

Core FHIR Resource
AdverseEvent
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core AdverseEvent

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | subject | `reference` | The client SHALL provide an id value for the reference.
MAY | event | `token` | The client MAY provide a code value.
MAY | recorded-date | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | subject+event | `reference`+`token`
SHALL | subject+recorded-date | `reference`+`date`

#### Resource Conformance: SHALLAllergyIntolerance

Core FHIR Resource
AllergyIntolerance
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core AllergyIntolerance

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLCarePlan

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
MAY | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | category | `token` | The client MAY provide a code value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+category | `reference`+`token`

#### Resource Conformance: SHALLCareTeam

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
MAY | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a code value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`

#### Resource Conformance: SHALLCondition

Core FHIR Resource
Condition
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core Condition Encounter Diagnosis
US Quality Core Condition Problems Health Concerns

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | category | `token` | The client MAY provide a category.
MAY | code | `token` | The client MAY provide a code value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+category | `reference`+`token`
SHALL | patient+code | `reference`+`token`

#### Resource Conformance: SHALLCoverage

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLDeviceRequest

Core FHIR Resource
DeviceRequest
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core DeviceRequest
US Quality Core Device Not Requested

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | code | `token` | The client MAY provide a code value.
MAY | do-not-perform | `token` | The client MAY provide a token value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+code | `reference`+`token`
SHALL | patient+do-not-perform | `reference`+`token`

#### Resource Conformance: SHALLDiagnosticReport

Core FHIR Resource
DiagnosticReport
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core DiagnosticReport Profile for Report and Note Exchange
US Quality Core DiagnosticReport Profile for Laboratory Results Reporting

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | category | `token` | The client MAY provide a category.
MAY | code | `token` | The client MAY provide a code value.
MAY | date | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+category | `reference`+`token`
SHALL | patient+category+date | `reference`+`token`+`date`
SHALL | patient+code | `reference`+`token`

#### Resource Conformance: SHALLDocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Core DocumentReference Profileversion: 6.1.0)

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
SHALL | _id | `token` | The client SHALL provide a token value.
MAY | category | `token` | The client MAY provide a token value.
MAY | date | `date` | The client MAY provide a date value.
MAY | type | `token` | The client MAY provide a token value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+type | `reference`+`token`
SHALL | patient+category | `reference`+`token`
SHALL | patient+category+date | `reference`+`token`+`date`

#### Resource Conformance: SHALLEncounter

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _id | `token` | The client SHALL provide an id value.
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | type | `token` | The client MAY provide a code value.
MAY | date | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+type | `reference`+`token`
SHALL | patient+date | `reference`+`date`

#### Resource Conformance: SHALLFamilyMemberHistory

Core FHIR Resource
FamilyMemberHistory
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core FamilyMemberHistory

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLGoal

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLImmunization

Core FHIR Resource
Immunization
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core Immunization
US Quality Core Immunization Not Done

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a status.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`

#### Resource Conformance: SHALLLocation

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.

#### Resource Conformance: SHALLMedication

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | code | `token` | The client SHALL provide a code value.

#### Resource Conformance: SHALLMedicationAdministration

Core FHIR Resource
MedicationAdministration
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core MedicationAdministration
US Quality Core MedicationAdministration Not Done

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a status.
MAY | code | `token` | The client MAY provide a code value.
MAY | effective-time | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`
SHALL | patient+code | `reference`+`token`
SHALL | patient+effective-time | `reference`+`date`

#### Resource Conformance: SHALLMedicationDispense

Core FHIR Resource
MedicationDispense
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core MedicationDispense
US Quality Core MedicationDispense Declined

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a status.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`

#### Resource Conformance: SHALLMedicationRequest

Core FHIR Resource
MedicationRequest
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core MedicationRequest
US Quality Core Medication Not Requested

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
MAY | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | intent | `token` | The client MAY provide a token value.
MAY | do-not-perform | `token` | The client MAY provide a token value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+intent+do-not-perform | `reference`+`token`+`token`
SHALL | patient+intent | `reference`+`token`

#### Resource Conformance: SHALLObservation

Core FHIR Resource
Observation
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported 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)

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
MAY | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | category | `token` | The client MAY provide a category.
MAY | status | `token` | The client MAY provide a status.
MAY | code | `token` | The client MAY provide a code value.
MAY | date | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+category+status | `reference`+`token`+`token`
SHALL | patient+category | `reference`+`token`
SHALL | patient+category+date | `reference`+`token`+`date`
SHALL | patient+code | `reference`+`token`

#### Resource Conformance: SHALLOrganization

Core FHIR Resource
Organization
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`.
- MAY support `search-type`.

Supported Profiles

US Quality Core Organization

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.

#### Resource Conformance: SHALLPatient

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _id | `token` | The client SHALL provide an id value.

#### Resource Conformance: SHALLPractitioner

Core FHIR Resource
Practitioner
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`.

Supported Profiles

US Quality Core Practitioner

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.

#### Resource Conformance: SHALLPractitionerRole

Core FHIR Resource
PractitionerRole
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`.

Supported Profiles

US Quality Core PractitionerRole

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.

#### Resource Conformance: SHALLProcedure

Core FHIR Resource
Procedure
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core Procedure
US Quality Core Procedure Not Done

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a status.
MAY | date | `date` | The client MAY provide a date value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`
SHALL | patient+date | `reference`+`date`

#### Resource Conformance: SHALLProvenance

Core FHIR Resource
Provenance
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`.
- MAY support `search-type`.

Supported Profiles

US Core Provenance Profileversion: 6.1.0)

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.

#### Resource Conformance: SHALLRelatedPerson

Core FHIR Resource
RelatedPerson
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core RelatedPerson

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _id | `token` | The client SHALL provide an id value.
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLServiceRequest

Core FHIR Resource
ServiceRequest
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core ServiceRequest
US Quality Core Service Not Requested

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _id | `token` | The client SHALL provide an id value.
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | category | `token` | The client MAY provide a category.
MAY | code | `token` | The client MAY provide a code value.
MAY | authored | `date` | The client MAY provide a date value.
MAY | do-not-perform | `token` | The client MAY provide a token value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+category | `reference`+`token`
SHALL | patient+category+authored | `reference`+`token`+`date`
SHALL | patient+code | `reference`+`token`
SHALL | patient+do-not-perform | `reference`+`token`

#### Resource Conformance: SHALLSpecimen

Core FHIR Resource
Specimen
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Core Specimen Profileversion: 6.1.0)

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | _id | `token` | The client SHALL provide a token value.
MAY | patient | `reference` | The client SHALL provide an id value for the reference.

#### Resource Conformance: SHALLTask

Core FHIR Resource
Task
Reference Policy
`resolves`
Interaction summary

- SHALL support `read`, `search-type`.

Supported Profiles

US Quality Core Task
US Quality Core Task Rejected

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

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | patient | `reference` | The client SHALL provide an id value for the reference.
MAY | status | `token` | The client MAY provide a status.
MAY | code | `token` | The client MAY provide a code value.

Combined Search Parameters

Conformance | Parameters | Types
--- | --- | ---
SHALL | patient+status | `reference`+`token`
SHALL | patient+code | `reference`+`token`