eCQM Reporting for Hospitals: IQR vs PI Rules

An electronic clinical quality measure is not a chart-abstracted measure that happens to be stored electronically. It is a computable measure specification that a certified EHR executes against structured data, producing a numerator and denominator with no human judgement in the loop. That single architectural difference changes what a bad score means. On a chart-abstracted measure, a fallout usually means an abstractor could not find proof in the record. On an eCQM, a fallout very often means the clinical action happened, was documented, and was documented in a place the measure logic does not look — a narrative note instead of a coded order, a local code that is not in the measure’s value set, a flowsheet row the EHR’s measure engine never queries.

This page is written for the quality analyst, the clinical informaticist and the quality director who owns the annual eCQM submission. It covers what an eCQM actually is, how a QRDA Category I submission works, and — the part most secondary coverage gets wrong — which CMS programme is asking for what. The Hospital Inpatient Quality Reporting (IQR) Program and the Medicare Promoting Interoperability Program both require eCQMs, on a deliberately aligned schedule, but they sit in different regulations, carry different penalties, and the requirement is not located where most explainers say it is.

Everything year-specific below is marked with the reporting year it was verified for, and the rule that set it. Measure sets and counts change by annual rulemaking; a page that states a count without a year is stating something that expires.

What makes an eCQM different from a chart-abstracted measure

A chart-abstracted measure — SEP-1 is now the only one left in the Hospital IQR Program — is a set of abstraction instructions a trained human applies to a record. An eCQM is a set of instructions a machine applies to a database. The specification is published as a package containing:

Measure logic expressed in CQL (Clinical Quality Language) — the boolean and temporal expressions that define the initial patient population, denominator, denominator exclusions, numerator, numerator exclusions and denominator exceptions.
A data model — the Quality Data Model (QDM) for the hospital eCQMs in current use, which defines what a “Medication, Administered” or an “Encounter, Performed” is, independent of any one vendor’s schema.
Value sets — the enumerated code lists (SNOMED CT, LOINC, RxNorm, ICD-10-CM and others) that decide whether a given coded item counts. These are published through the NLM Value Set Authority Center (VSAC), and access requires a UMLS Metathesaurus licence.
A human-readable and machine-readable package — historically HQMF, distributed through the eCQI Resource Center as the CMS Annual Update.

The practical consequence is that an eCQM result is only as good as the structured capture underneath it. Three failure modes recur, and they are diagnosed differently:

Value-set misses. The action was coded, but with a local or legacy code that is not a member of the measure’s value set. This is a terminology-mapping fix, not a clinical one.
Wrong-location capture. The action was documented as free text, in a scanned document, or in a flowsheet field the measure engine does not map to the required QDM data element. This is a build fix.
Genuine performance gaps. The care did not happen inside the specified window. This is the only one that belongs in a performance improvement project.

Distinguishing (1) and (2) from (3) before launching an improvement project is the single highest-value thing a quality department does with eCQM data. Chasing a clinical root cause for what is a terminology-mapping defect wastes a year.

CMS itself acknowledges vendor variation in how this is implemented: in testing the Hospital Harm — Postoperative VTE eCQM, CMS reported using test sites collectively running four EHR systems, naming Epic, Allscripts, Cerner and Meditech (FY 2027 IPPS/LTCH PPS final rule, 91 FR 49976). The measure is one specification; the extraction is not one implementation. See also Epic vs Oracle Health for the underlying platform decision.

Be precise about which programme is asking

This is where secondary coverage most often goes wrong. Three things get conflated: the Hospital IQR Program, the Medicare Promoting Interoperability Program, and the Promoting Interoperability objectives. They are related but distinct, and the eCQM requirement is not where people expect it.

Hospital Inpatient Quality Reporting Program

Statutory basis: section 1886(b)(3)(B)(viii) of the Social Security Act. The consequence of not submitting is that the applicable percentage increase for the fiscal year is reduced by one-quarter of that increase. The programme’s procedural rules are codified at 42 CFR 412.140:

412.140(a) — a hospital must register on QualityNet before it begins reporting, identify and register a QualityNet security official, and submit a Notice of Participation form (by 31 December of the calendar year preceding the first quarter of data submission, for a first-time participant or one rejoining; within 180 days of the QIES open date for a hospital with a new CCN).
412.140(c)(1) — data are submitted “in a form and manner, and at a time, specified by CMS”. The CFR deliberately does not name the measures, the file format or the deadline. Those live in the annual IPPS rule and on QualityNet.
412.140(c)(2) — the Extraordinary Circumstance Exception, requested within 60 calendar days of the event.

Medicare Promoting Interoperability Program — and where the eCQM duty actually sits

Here is the correction worth the page. The eCQM requirement is not one of the Promoting Interoperability objectives. For eligible hospitals and CAHs attesting to CMS, the governing paragraph for 2023 and subsequent years is 42 CFR 495.24(f) (paragraph (e) governed 2019 through 2022, and the paragraph (c) Stage 3 list is a different attestation path — getting this wrong is easy, and it is why a CFR citation in someone else’s explainer is worth checking). Paragraph (f)(1)(i) requires a hospital to meet all objectives and associated measures selected by CMS under section 1886(n)(3) of the Act for the EHR reporting period, and to earn a minimum total score: 60 points in 2023 and 2024, 70 in 2025, and 80 points in 2026 and subsequent years. It does not enumerate the measures, and it says nothing about eCQMs.

The eCQM duty is instead a component of the definition of “meaningful EHR user” at 42 CFR 495.4, paragraph (1)(iv): a provider must, among other things, “successfully report the clinical quality measures selected by CMS to CMS or the States, as applicable, in the form and manner specified by CMS or the States, as applicable.” A hospital can score every objective measure and still fail to be a meaningful EHR user if the eCQM submission does not land.

The same definition also carries the certification requirement on the EHR. For 2019 and subsequent years, certified electronic health record technology must meet the 2015 Edition Base EHR definition and be certified to, among other criteria, the clinical quality measure certification criteria at 45 CFR 170.315(c)(2) and (c)(3)(i) and (ii) — the criteria supporting CQM calculation and reporting in a form that “can be electronically accepted by CMS”. If your vendor is certified to (c)(1) and (c)(2) but not the (c)(3) reporting criteria, you cannot produce a conformant submission file, regardless of how good the calculation is.

So the two duties are scored separately and can fail independently: a hospital can earn the full 80-point objectives score and still not be a meaningful EHR user because the eCQM submission did not land. For the public health objective itself — the one covering immunization registry, syndromic surveillance, electronic case reporting, ELR and registry reporting, and where in the regulation its measures actually live — see syndromic surveillance reporting for hospitals. That is a different requirement with a different clock, and it is not satisfied by an eCQM submission.

What eCQMs are not

Both programmes above are pay-for-reporting: the question is whether you submitted, not how you scored. That is a different question from the Hospital Value-Based Purchasing Total Performance Score, which scores a separate measure set on achievement and improvement, and from the Hospital Readmissions Reduction Program, which is claims-based. Do not describe an eCQM fallout as costing a payment penalty on performance; the IQR and PI consequences attach to submission, and the numbers are then published.

How many eCQMs, and does the hospital choose them?

Both. The structure since the CY 2026 reporting period is a growing set of mandatory measures plus exactly three self-selected measures, and CMS has stated explicitly that the Medicare Promoting Interoperability Program requirement is aligned with the Hospital IQR requirement (91 FR 50081).

The schedule finalized in the FY 2025 IPPS/LTCH PPS final rule (89 FR 68986, 28 August 2024):

Reporting period	Payment determination	Total eCQMs	Composition
CY 2026	FY 2028	8	5 mandatory + 3 self-selected
CY 2027	FY 2029	9	6 mandatory + 3 self-selected
CY 2028	FY 2030	11 as then finalized	8 mandatory + 3 self-selected

The five mandatory measures for the CY 2026 reporting period, named verbatim in that rule, are Safe Use of Opioids — Concurrent Prescribing; Severe Obstetric Complications; Cesarean Birth; Hospital Harm — Severe Hypoglycemia; and Hospital Harm — Severe Hyperglycemia. CY 2027 adds Hospital Harm — Opioid-Related Adverse Events. CY 2028 as originally finalized added Hospital Harm — Pressure Injury and Hospital Harm — Acute Kidney Injury.

The FY 2027 IPPS/LTCH PPS final rule (91 FR 49570, 4 August 2026) then changed CY 2028 and later. It finalized a standing rule that Hospital Harm eCQMs become mandatory after two years of self-selected reporting, and made three further measures mandatory beginning with the CY 2028 reporting period: Hospital Harm — Falls with Injury, Hospital Harm — Postoperative Respiratory Failure, and the Malnutrition Care Score. CMS’s own burden estimate states the resulting requirement is a total of 14 eCQMs for the CY 2028 and CY 2029 reporting periods, and 15 eCQMs beginning with the CY 2030 reporting period (91 FR 50331–50332), the last increment being Hospital Harm — Postoperative VTE, adopted for self-selection from CY 2028 and mandatory from CY 2030 (FY 2032 payment determination). The Advance Care Planning eCQM was also adopted as a self-selection option beginning CY 2028.

A caution for anyone reading the rule text directly. The per-year summary tables in the FY 2027 rule (Tables IX.C.8 and IX.C.10) are published as images and carry no extractable text, so a text search of the rule will not return them. The preamble also contains at least one stray phrase describing “three self-selected eCQMs to be reported in addition to three mandatory eCQMs” (91 FR 49975) that is inconsistent with the same rule’s tables and burden estimates. Where the prose and the burden section disagree, the burden section (OMB control number 0938-1022) states the counts explicitly and is the safer read — but confirm against the tables and QualityNet before you plan staffing around a number.

How CMS reads your self-selection

Worth knowing before you choose: CMS states that “on average, less than 10 percent of hospitals self-select to report on a given eCQM in the first year it is available, and we assume a hospital tends to self-select a given eCQM because it will perform better on that eCQM compared to other eCQMs available to self-select” (91 FR 50001). That assumption is the stated rationale for converting Hospital Harm measures to mandatory reporting. Two operational implications: a measure you self-select today is a plausible mandatory measure in two years, so treat self-selection as a build-readiness rehearsal rather than a score-optimisation exercise; and CMS finalized that Hospital Harm eCQMs are not publicly reported during the two-year self-selection window, appear on the research-oriented Provider Data Catalog in the first year of mandatory reporting, and move to Care Compare including Star Ratings from the second year of mandatory reporting.

The CY 2026 hospital inpatient eCQM measure set

Seventeen Hospital — Inpatient eCQMs are specified for the 2026 reporting period, per the eCQI Resource Center (page last updated 23 July 2026). Measure identifiers only are reproduced here; the specifications themselves are downloadable from eCQI and are not restated on this page. “CBE ID” is the consensus-based entity identifier, the successor label to the NQF number; eCQI’s own note is to verify active endorsement on the CBE’s PQM site rather than treating the listed ID as proof of current endorsement.

Measure	Short name	CMS eCQM ID (2026 version)	CBE ID
Safe Use of Opioids — Concurrent Prescribing	—	CMS506v8	3316e
Severe Obstetric Complications	PC-07	CMS1028v4	Not applicable
Cesarean Birth	PC-02	CMS334v7	0471e
Hospital Harm — Severe Hyperglycemia	HH-Hyper	CMS871v5	3533e
Hospital Harm — Severe Hypoglycemia	HH-Hypo	CMS816v5	3503e
Hospital Harm — Opioid-Related Adverse Events	HH-ORAE	CMS819v4	3501e
Hospital Harm — Pressure Injury	HH-PI	CMS826v3	3498e
Hospital Harm — Acute Kidney Injury	HH-AKI	CMS832v3	3713e
Hospital Harm — Falls with Injury	HH-FI	CMS1017v2	4120e
Hospital Harm — Postoperative Respiratory Failure	HH-RF	CMS1218v2	4130e
Malnutrition Care Score	MCS	CMS986v5	3592e
Anticoagulation Therapy for Atrial Fibrillation/Flutter	STK-3	CMS71v15	Not applicable
Antithrombotic Therapy by End of Hospital Day 2	STK-5	CMS72v14	Not applicable
Discharged on Antithrombotic Therapy	STK-2	CMS104v14	Not applicable
Venous Thromboembolism Prophylaxis	VTE-1	CMS108v14	Not applicable
Intensive Care Unit Venous Thromboembolism Prophylaxis	VTE-2	CMS190v14	Not applicable
Excessive Radiation Dose or Inadequate Image Quality for Diagnostic CT in Adults (Facility Inpatient)	IP-ExRad	CMS1074v3	3663e

Several of these are risk-adjusted (Acute Kidney Injury, Falls with Injury, Postoperative Respiratory Failure, Severe Obstetric Complications), each with its own published methodology report, and eCQI carries open known-issue tickets against some versions — check the eCQM Issue Tracker before assuming a discrepancy in your output is a local build defect. Hybrid measures, which combine claims data with EHR-derived core clinical data elements, are a separate category with their own submission rules and are not counted in the eCQM totals above.

Submission mechanics: QRDA Category I

Hospitals submit QRDA Category I files — patient-level, one file per patient episode, containing the data elements the measures consumed. QRDA Category III, the aggregate format, is the eligible-clinician path and is not what a hospital submits for inpatient eCQMs.

Verified from the eCQI Resource Center (QRDA page, last updated 15 July 2026):

The 2026 CMS QRDA I Implementation Guide for Hospital Quality Reporting (published May 2025) is based on HL7 CDA Release 2: QRDA Category I, Release 1, Standard for Trial Use Release 5.3 with errata (published December 2022).
The 2027 CMS QRDA I Implementation Guide (published May 2026) is based on the same STU Release 5.3 including subsequent errata updates.
CMS publishes a Schematron and sample files alongside each IG. Validating against the Schematron before the submission window opens is the cheapest defect-detection step available, because conformance errors reject files silently at the point they matter least.

Two timing facts, both from the FY 2027 IPPS final rule:

The eCQM submission deadline is 1 March following the calendar-year reporting period (91 FR 49980).
The specification version is set a year ahead. “The updated measure specifications applicable to a reporting period are contained in the Annual Update issued in the year prior to the reporting period” — for the CY 2026 reporting period / FY 2028 payment determination, hospitals collect and submit using the May 2025 Annual Update and any applicable addenda (91 FR 49999). A build that was validated against the wrong Annual Update produces conformant-looking files with wrong denominators.

Three different things count as a successful submission

This is the mechanic most often missed, and it is stated plainly in the rule (91 FR 50002, citing 82 FR 38387):

A QRDA Category I file with patients meeting the initial patient population of the applicable measures, a zero denominator declaration, or a case threshold exemption all count toward a successful submission for eCQMs for the Hospital Inpatient Quality Reporting Program.

So a hospital with no qualifying patients for a required measure does not fail it — it files a zero denominator declaration, and that satisfies the requirement for that measure. A hospital below the applicable case threshold files a case threshold exemption. Neither is an exception request and neither requires CMS approval in the way an Extraordinary Circumstance Exception does. A quality department that treats “we have no cases” as a compliance problem is manufacturing one.

For planning purposes, CMS’s approved information collection burden per reported eCQM is 10 minutes per hospital per quarter, or 40 minutes per hospital annually, at an assumed labour rate of $55.06 per hour across approximately 3,050 IPPS hospitals (91 FR 50331). That figure is a regulatory burden estimate for paperwork accounting, not a realistic estimate of what building and maintaining an eCQM costs a hospital — it excludes the build, the terminology mapping and the reconciliation work that consumes the actual effort. Cite it as what it is.

eCQM validation — and the change arriving with FY 2028

CMS validates a sample of submitted data by requesting patient charts. The regulation distinguishes the two measure types, and the eCQM standard is about to get materially harder. Per 42 CFR 412.140(d)(2):

Chart-abstracted measures: a hospital meets the validation requirement by achieving a 75-percent score.
eCQMs, before the FY 2028 payment determination: a hospital meets the requirement if it submits 100 percent of sampled eCQM measure medical records in a timely and complete manner. Note what this does and does not test — it tests whether you produced the records, not whether the data matched.
eCQMs, for the FY 2028 payment determination and later: a hospital meets the requirement if it achieves a 75-percent score, the same standard as chart-abstracted measures.

That is a change in kind, not degree. Under the current rule a hospital passes eCQM validation by being responsive to a records request. Under the FY 2028 rule the submitted data has to agree with the record at a scored threshold, which makes the terminology-mapping and capture-location problems described at the top of this page into a validation exposure rather than a reporting-accuracy annoyance. Requests must be answered within 30 days of the date identified on the written request (412.140(d)(1)).

If a hospital fails, 412.140(e) provides reconsideration within 30 days of the Annual Payment Update Notification Letter, with an enumerated list of required contents, and an appeal to the Provider Reimbursement Review Board under 42 CFR part 405 subpart R.

Why measures disappear: the removal factors are in the CFR

Unusually for this programme, the criteria for dropping a measure are codified rather than left to rulemaking narrative. 42 CFR 412.140(g)(3)(i) lists eight removal factors, including that performance is “so high and unvarying that meaningful distinctions and improvements in performance can no longer be made” (topped out), that a measure does not align with current clinical guidelines, that performance on it does not result in better patient outcomes, that it is not feasible to implement the specifications, and that costs outweigh benefit.

412.140(g)(3)(ii) then defines “topped out” numerically, and both conditions must hold:

Statistically indistinguishable performance at the 75th and 90th percentiles — defined as the difference between them being within two times the standard error of the full data set; and
A truncated coefficient of variation less than or equal to 0.10.

412.140(g)(2) also permits immediate removal without rulemaking where continued use of a measure raises specific patient safety concerns, with notice via the IQR ListServ and QualityNet. That is the mechanism to watch if a measure vanishes mid-year.

A readiness checklist

Confirm your CEHRT is certified to 45 CFR 170.315(c)(2) and (c)(3)(i) and (ii), not merely to (c)(1) and (c)(2).
Confirm which Annual Update governs the reporting period you are collecting for — the one issued the year before, not the current one.
Confirm the QRDA I Implementation Guide version for that reporting year and validate a sample file against the matching CMS Schematron early, not in February.
For each required measure, decide before the year starts whether you expect a real denominator, a zero denominator declaration or a case threshold exemption.
Choose your three self-selected measures on build readiness, not on expected score — Hospital Harm measures become mandatory two years after they become available.
Run a value-set reconciliation on local and legacy codes for each mandatory measure before the reporting year, and again after any terminology content update.
For any fallout, classify it as value-set miss, capture-location defect or genuine performance gap before opening a PIP.
Verify registration and Notice of Participation status under 412.140(a) — the deadline is 31 December of the preceding calendar year for a new or rejoining participant.
Rehearse the 30-day chart-production process now, ahead of the FY 2028 shift from a 100-percent-submission test to a 75-percent score.

What this page does not assert

Three deliberate gaps, stated rather than filled:

The per-year measure-count summary tables in the FY 2027 IPPS final rule (Tables IX.C.8 and IX.C.10) are published as images and could not be read. The counts above are taken from the explicit prose in the FY 2025 rule and from the FY 2027 rule’s information-collection burden section. Confirm against QualityNet before planning to them.
No CQL expression, value-set membership or measure specification text is reproduced here. Measure identifiers and regulatory section identifiers only. The specifications are published on the eCQI Resource Center and should be read there.
Hybrid measure submission requirements are out of scope. CMS explicitly did not change them in the FY 2027 rule and did not restate them; they are on QualityNet.

This page sits in CASRAI’s patient safety cluster alongside NDNQI nursing-sensitive indicators, the OMOP common data model for the analytics side of the same structured-data problem, and CPHQ certification for the people who do this work.

Frequently asked questions

How many eCQMs must a hospital report?

For the CY 2026 reporting period (FY 2028 payment determination), eight in total: five mandatory measures plus three the hospital self-selects. Nine for CY 2027. The FY 2027 IPPS final rule raised CY 2028 and CY 2029 to fourteen, and CY 2030 onward to fifteen. The same schedule applies to the Medicare Promoting Interoperability Program, which CMS has deliberately aligned with Hospital IQR.

Does the hospital choose which eCQMs to report?

Partly. Three are self-selected from the published measure set in every year from CY 2026 onward; the rest are mandatory and named in the annual IPPS rule. The self-selected slots do not shrink as the mandatory set grows.

What is the eCQM submission deadline?

1 March following the calendar-year reporting period, per the FY 2027 IPPS final rule at 91 FR 49980.

What if we have no patients who meet a required measure?

File a zero denominator declaration. CMS states that a QRDA Category I file with qualifying patients, a zero denominator declaration, or a case threshold exemption all count toward a successful submission.

Is QRDA Category I or Category III the right format?

Category I, the patient-level format, for hospital inpatient eCQMs. Category III is the aggregate format used by eligible clinicians.

Are eCQMs part of Promoting Interoperability?

They are required by the Medicare Promoting Interoperability Program, but they are not among the objectives and measures scored under 42 CFR 495.24(f), which is what governs a hospital attesting to CMS for 2023 and subsequent years. The eCQM duty is in the definition of “meaningful EHR user” at 42 CFR 495.4, paragraph (1)(iv), and it is scored separately from the 80-point objectives threshold that applies from 2026. This distinction matters when you are reading the regulation to answer a survey or audit question.

Why did we fail an eCQM when the care was delivered?

Most commonly because the action was captured somewhere the measure logic does not read — free text rather than a coded order, or a local code that is not a member of the measure’s value set. Rule out terminology mapping and capture location before treating it as a clinical performance problem.

What changes about eCQM validation in FY 2028?

The standard changes from submitting 100 percent of sampled eCQM medical records in a timely and complete manner to achieving a 75-percent score — the same standard already applied to chart-abstracted measures. See 42 CFR 412.140(d)(2)(ii).

Which specification version applies to our reporting year?

The Annual Update issued in the year before the reporting period. The CY 2026 reporting period uses the May 2025 Annual Update and any applicable addenda.