CMS Hospital Quality Reporting FHIR Implementation Guide
0.1.0 - ci-build
CMS Hospital Quality Reporting FHIR Implementation Guide
0.1.0 - ci-build
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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| HQR Receiver CapabilityStatement (DRAFT 0.1.0) |
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. |
| HQR Submitter CapabilityStatement (DRAFT 0.1.0) |
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. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| HQR Reporting Organization (DRAFT) |
DRAFT. Constrains QI-Core Organization to require the CMS Certification Number (CCN), identifying the facility reporting to HQR. |
| HQR Submission MeasureReport (DRAFT) |
DRAFT, measure-independent constraint of the DEQM Data Exchange MeasureReport profile for CMS Hospital Quality Reporting submissions (built against DEQM US Realm STU5 in version 0.1.0; this guide targets DEQM Universal Realm by version 1.0.0). Placeholder for Connectathon scaffolding only. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| HQR Program/Reporting Year Extension |
DRAFT. Carries the CMS quality program reporting year (e.g., 2026) associated with a submission. Placeholder pending confirmation of final data element placement (ROADMAP.md #9). |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example HQR Submission MeasureReport — CMS138 (EC/ambulatory gap-analysis candidate, DRAFT) |
DRAFT example targeting CMS138 (Tobacco Use: Screening and Cessation Intervention), an EC measure outside this guide's stated Hospital IQR program focus, used to test whether ambulatory measures structurally avoid this guide's recurring Hospital IQR gap categories. This demonstrates measure-independence – CMS138 is not excluded by the profile, only outside HQR's current reporting-program focus. |
| Example HQR Submission MeasureReport — CMS506 (one of three either/or Connectathon test measures, DRAFT) |
DRAFT example targeting CMS506 (Safe Use of Opioids - Concurrent Prescribing), one of three either/or Connectathon test measures (no primary/stretch tiering), demonstrating measure-independence of the profile. |
| Example HQR Submission MeasureReport — CMS71 (one of three either/or Connectathon test measures, DRAFT) |
DRAFT example targeting CMS71 (STK-3, Anticoagulation Therapy for AF/Flutter), one of three either/or Connectathon test measures (no primary/stretch tiering). |
| Example HQR Submission MeasureReport — EXMConnectathonSept2026Simple (DRAFT) |
DRAFT example targeting EXMConnectathonSept2026Simple (https://madie.cms.gov/Measure/EXMConnectathonSept2026Simple), one of three either/or Connectathon test measures alongside CMS71/CMS506 (no primary/stretch tiering). |
| Example HQR Submission MeasureReport — Vendor-Submitted (DRAFT) |
DRAFT example illustrating reporter and Submitter as distinct entities: the reporting facility (hqr-example-organization, identified by CCN) is not the one technically submitting the data – a health IT vendor (hqr-example-vendor-organization) is, via the reportingVendor extension. Reuses the CMS71 measure canonical arbitrarily; the profile is measure-independent, this example is about the reporter/vendor split, not the measure. |
| Example Patient |
Illustrative example patient used as the subject for the MeasureReport submission examples. QI-Core-conformant, per HQRSubmissionMeasureReport.subject. |
| Example Reporting Hospital |
Illustrative example reporting hospital used as the reporter for the MeasureReport submission examples. QI-Core-conformant, carrying CCN via identifier:ccn per HQRReportingOrganization. |
| Example Reporting Vendor |
Illustrative example health IT vendor, used as the reportingVendor for the vendor-submitted MeasureReport example. Deliberately InstanceOf plain QICoreOrganization, not HQRReportingOrganization – a vendor/intermediary is not a CMS-certified facility and has no CCN. |