CMS Hospital Quality Reporting FHIR Implementation Guide
0.1.0 - ci-build United States of America flag

CMS Hospital Quality Reporting FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: HQR Submitter CapabilityStatement (DRAFT 0.1.0)

Official URL: http://example.org/fhir/us/hqr/CapabilityStatement/HQRSubmitterCapabilityStatement Version: 0.1.0
Draft as of 2026-08-03 Computable Name:

DRAFT. Submitter pushes a MeasureReport via $submit-data / create, then retrieves status and results via read/search. Invited-pull entries below describe a second exchange pattern this guide is exploring, not yet a committed capability.

Raw OpenAPI-Swagger Definition file | Download

HQR Submitter CapabilityStatement (DRAFT 0.1.0)

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.1
  • Supported Formats: json
  • Published on: 2026-08-03
  • Published by: Centers for Medicare & Medicaid Services (CMS)

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.

FHIR RESTful Capabilities

REST Configuration: 1

Mode: client

Submitter invokes $submit-data / creates a MeasureReport on the Receiver, authenticated per the (still provisional) auth pattern, and receives an acceptance/status response.

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$submit-data

REST Configuration: 2

Mode: client

Results retrieval. Submitter reads/searches the Receiver for the submission's status and results after the fact, independent of the original synchronous response.

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
MeasureReport yy
Core FHIR Resource
MeasureReport
Reference Policy
Interaction summary
  • Supports read, search-type.

REST Configuration: 3

Mode: server

Invited-pull concept, not yet a committed capability. If pursued, Submitter would expose a Bulk Data $export endpoint for the Receiver to pull from once invited.

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$export

REST Configuration: 4

Mode: client

Invited-pull concept, not yet a committed capability. If pursued, Submitter would invoke $bulk-submit-data against the Receiver to indicate a dataset is ready and where to pull it from (the ping half of ping-and-pull).

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$bulk-submit-data