Generated Narrative: CapabilityStatement us-quality-core-server US Quality Core Server CapabilityStatement Implementation Guide Version: 0.1.0 FHIR Version: 4.0.1 Supported Formats: json Published on: 2026-03-31 Published by: ASTP 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/astp/us-quality-core FHIR RESTful Capabilities Mode: server The US Quality Core Server SHALL: Conform to requirements provided in the US Core Server CapabilityStatement and the base FHIR specification Support all US Quality Core profiles that contain at least one USCDI+ Quality data element, as described in the USCDI+ Quality page Support all interactions, search parameters, and combined search parameters that have SHALL conformance expectations as described in this CapabilityStatement Support all USCDI+ Quality flagged data elements, and those flagged as MustSupport from underlying US Core profiles Ensure resources in 'Any' references conform to US Quality Core profiles if the base resource has a US Quality Core profile Implement the RESTful behavior according to the FHIR specification for all US Quality Core interactions Support JSON source formats for all US Quality Core interactions NOTE: US Quality 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. Servers and Clients SHOULD 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 Type Profile R S U C Searches _include _revinclude Operations AdverseEvent Supported Profiles US Quality Core AdverseEvent Y Y subject, event, recordedDate, subject+event, subject+recordedDate AllergyIntolerance Supported Profiles US Quality Core AllergyIntolerance Y Y patient CarePlan Supported Profiles US Quality Core CarePlan Y Y patient, category, patient+category CareTeam Supported Profiles US Quality Core CareTeam Y Y patient, status, patient+status Claim Supported Profiles US Quality Core Claim Y Y patient Condition Supported Profiles US Quality Core Condition Encounter Diagnosis US Quality Core Condition Problems Health Concerns Y Y patient, category, code, onset-date, abatement-date, patient+abatement-date, patient+category, patient+code, patient+onset-date Coverage Supported Profiles US Quality Core Coverage Y Y patient DeviceRequest Supported Profiles US Quality Core DeviceRequest US Quality Core Device Not Requested Y Y patient, code, patient+code 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 Encounter Supported Profiles US Quality Core Encounter Y Y _id, patient, type, date, patient+type, patient+date FamilyMemberHistory Supported Profiles US Quality Core FamilyMemberHistory Y Y patient Goal Supported Profiles US Quality Core Goal Y Y patient Immunization Supported Profiles US Quality Core Immunization US Quality Core Immunization Not Done Y Y patient, status, date, patient+date, patient+status Location Supported Profiles US Quality Core Location Y Y _id 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 MedicationDispense Supported Profiles US Quality Core MedicationDispense US Quality Core MedicationDispense Declined Y Y patient, status, patient+status MedicationRequest Supported Profiles US Quality Core MedicationRequest US Quality Core Medication Not Requested Y Y patient, intent, patient+intent 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 Quality Core Laboratory Result Observation Y Y patient, category, code, date, patient+category, patient+category+date, patient+code Organization Supported Profiles US Quality Core Organization Y y? Patient Supported Profiles US Quality Core Patient Y Y _id Practitioner Supported Profiles US Quality Core Practitioner Y Y _id PractitionerRole Supported Profiles US Quality Core PractitionerRole Y Y _id Procedure Supported Profiles US Quality Core Procedure US Quality Core Procedure Not Done Y Y patient, status, date, patient+status, patient+date RelatedPerson Supported Profiles US Quality Core RelatedPerson Y Y _id, patient ServiceRequest Supported Profiles US Quality Core ServiceRequest US Quality Core Service Not Requested Y Y _id, patient, category, code, authored, patient+category, patient+category+authored, patient+code Task Supported Profiles US Quality Core Task US Quality Core Task Rejected Y Y patient, status, code, patient+status, patient+code Resource Conformance: SHALL AdverseEvent Core FHIR Resource AdverseEvent Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core AdverseEvent 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 recordedDate date The client MAY provide a date value. Combined Search Parameters Conformance Parameters Types SHALL subject+event reference+token SHALL subject+recordedDate reference+date Resource Conformance: SHALL AllergyIntolerance Core FHIR Resource AllergyIntolerance Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core AllergyIntolerance Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide an id value for the reference. Resource Conformance: SHALL CarePlan Core FHIR Resource CarePlan Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core CarePlan 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: SHALL CareTeam Core FHIR Resource CareTeam Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core CareTeam 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: SHALL Claim Core FHIR Resource Claim Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Claim Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide an id value for the reference. Resource Conformance: SHALL Condition 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 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 onset-date date The client MAY provide a date value. MAY abatement-date date The client MAY provide a date value. Combined Search Parameters Conformance Parameters Types SHALL patient+category reference+token SHOULD patient+abatement-date reference+date SHOULD patient+code reference+token SHOULD patient+onset-date reference+date Resource Conformance: SHALL Coverage Core FHIR Resource Coverage Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Coverage Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide an id value for the reference. Resource Conformance: SHALL DeviceRequest 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 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. Combined Search Parameters Conformance Parameters Types SHALL patient+code reference+token Resource Conformance: SHALL DiagnosticReport 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 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: SHALL Encounter Core FHIR Resource Encounter Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Encounter 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: SHALL FamilyMemberHistory Core FHIR Resource FamilyMemberHistory Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core FamilyMemberHistory Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide an id value for the reference. Resource Conformance: SHALL Goal Core FHIR Resource Goal Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Goal Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide an id value for the reference. Resource Conformance: SHALL Immunization 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 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 SHOULD patient+date reference+date Resource Conformance: SHALL Location Core FHIR Resource Location Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Location Search Parameters Conformance Parameter Type Documentation SHALL _id token The client SHALL provide an id value. Resource Conformance: SHALL Medication Core FHIR Resource Medication Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Medication Search Parameters Conformance Parameter Type Documentation SHALL code token The client SHALL provide a code value. Resource Conformance: SHALL MedicationAdministration 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 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: SHALL MedicationDispense 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 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: SHALL MedicationRequest 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 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. Combined Search Parameters Conformance Parameters Types SHALL patient+intent reference+token Resource Conformance: SHALL Observation 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 Quality Core Laboratory Result Observation 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 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: SHALL Organization Core FHIR Resource Organization Reference Policy resolves Interaction summary SHALL support read. MAY support search-type. Supported Profiles US Quality Core Organization Resource Conformance: SHALL Patient Core FHIR Resource Patient Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Patient Search Parameters Conformance Parameter Type Documentation SHALL _id token The client SHALL provide an id value. Resource Conformance: SHALL Practitioner Core FHIR Resource Practitioner Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core Practitioner Search Parameters Conformance Parameter Type Documentation SHALL _id token The client SHALL provide an id value. Resource Conformance: SHALL PractitionerRole Core FHIR Resource PractitionerRole Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core PractitionerRole Search Parameters Conformance Parameter Type Documentation SHALL _id token The client SHALL provide an id value. Resource Conformance: SHALL Procedure 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 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: SHALL RelatedPerson Core FHIR Resource RelatedPerson Reference Policy resolves Interaction summary SHALL support read, search-type. Supported Profiles US Quality Core RelatedPerson 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: SHALL ServiceRequest 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 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. Combined Search Parameters Conformance Parameters Types SHALL patient+category reference+token SHALL patient+category+authored reference+token+date SHALL patient+code reference+token Resource Conformance: SHALL Task 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 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
US Quality Core Server CapabilityStatement
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](uscdiquality.html) section of this implementation guide. US Quality Core Servers **SHALL** support the capabilities described in the [US Core Server CapabilityStatement STU6.1](https://hl7.org/fhir/us/core/STU6.1/CapabilityStatement-us-core-server.html). 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 v1 is derived from the QI-Core Implementation Guide STU6. It adopts all profiles within the [QI-Core Implementation Guide STU6](https://hl7.org/fhir/us/qicore/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.
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 profiles that contain at least one USCDI+ Quality data element, as described in the [USCDI+ Quality page](/uscdiquality.html) 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 US Quality Core interactions 7. Support JSON source formats for all US Quality Core interactions NOTE: US Quality 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. Servers and Clients SHOULD use the standard FHIR SearchParameters.
The client **SHALL** provide an id value for the reference.
The client **MAY** provide a code value.
The client **MAY** provide a date value.
The client **SHALL** provide an id value.
The client **SHALL** provide a code value.
The client **MAY** provide a token value.