{ "resourceType" : "CapabilityStatement", "id" : "HQRReceiverCapabilityStatement", "text" : { "status" : "extensions", "div" : "

Generated Narrative: CapabilityStatement HQRReceiverCapabilityStatement

HQR Receiver CapabilityStatement (DRAFT 0.1.0)

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: server

Receiver accepts $submit-data / a created MeasureReport from an authenticated Submitter, validates conformance against HQR profiles, persists accepted data, and returns a clear acceptance/status response.

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

Capabilities by Resource/Profile

Summary

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

Resource TypeProfileRSUCSearches_include_revincludeOperations
MeasureReporthttp://example.org/fhir/us/hqr/StructureDefinition/hqr-submission-measurereporty
Resource Conformance: unspecified MeasureReport
Base System Profile
HQR Submission MeasureReport (DRAFT)
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create.

REST Configuration: 2

Mode: server

Results retrieval. Receiver supports read/search on the submitted MeasureReport so the Submitter can retrieve status/results after the fact, not just via the original synchronous response.

\n

Capabilities by Resource/Profile

Summary

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

Resource TypeProfileRSUCSearches_include_revincludeOperations
MeasureReport\u00a0yy
Resource Conformance: unspecified MeasureReport
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, Receiver would accept the $bulk-submit-data ping from an authenticated Submitter, then pull via Bulk $export (see client role below).

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

REST Configuration: 4

Mode: client

Invited-pull concept, not yet a committed capability. If pursued, Receiver would invoke Bulk $export against the Submitter's server named in the ping, retrieve the dataset, validate, and persist accepted data.

\n
Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$export
" }, "url" : "http://example.org/fhir/us/hqr/CapabilityStatement/HQRReceiverCapabilityStatement", "version" : "0.1.0", "title" : "HQR Receiver CapabilityStatement (DRAFT 0.1.0)", "status" : "draft", "date" : "2026-08-03", "publisher" : "Centers for Medicare & Medicaid Services (CMS)", "contact" : [{ "name" : "Centers for Medicare & Medicaid Services (CMS)", "telecom" : [{ "system" : "url", "value" : "https://www.cms.gov" }] }], "description" : "DRAFT. Receiver accepts a pushed MeasureReport and supports status/results retrieval. Invited-pull entries below describe a second exchange pattern this guide is exploring, not yet a committed capability.", "jurisdiction" : [{ "coding" : [{ "system" : "urn:iso:std:iso:3166", "code" : "US", "display" : "United States of America" }] }], "kind" : "requirements", "fhirVersion" : "4.0.1", "format" : ["json"], "rest" : [{ "mode" : "server", "documentation" : "Receiver accepts $submit-data / a created MeasureReport from an authenticated Submitter, validates conformance against HQR profiles, persists accepted data, and returns a clear acceptance/status response.", "resource" : [{ "type" : "MeasureReport", "profile" : "http://example.org/fhir/us/hqr/StructureDefinition/hqr-submission-measurereport", "interaction" : [{ "code" : "create" }] }], "operation" : [{ "name" : "submit-data", "definition" : "http://hl7.org/fhir/us/davinci-deqm/OperationDefinition/submit-data" }] }, { "mode" : "server", "documentation" : "Results retrieval. Receiver supports read/search on the submitted MeasureReport so the Submitter can retrieve status/results after the fact, not just via the original synchronous response.", "resource" : [{ "type" : "MeasureReport", "interaction" : [{ "code" : "read" }, { "code" : "search-type" }] }] }, { "mode" : "server", "documentation" : "Invited-pull concept, not yet a committed capability. If pursued, Receiver would accept the $bulk-submit-data ping from an authenticated Submitter, then pull via Bulk $export (see client role below).", "operation" : [{ "name" : "bulk-submit-data", "definition" : "http://hl7.org/fhir/us/davinci-deqm/OperationDefinition/bulk-submit-data" }] }, { "mode" : "client", "documentation" : "Invited-pull concept, not yet a committed capability. If pursued, Receiver would invoke Bulk $export against the Submitter's server named in the ping, retrieve the dataset, validate, and persist accepted data.", "operation" : [{ "name" : "export", "definition" : "http://hl7.org/fhir/uv/bulkdata/OperationDefinition/export|3.0.0" }] }] }