eCQM Reporting for Medicare ACOs: Beyond the CMS Web Interface

With the CMS Web Interface retired, every Medicare Shared Savings Program ACO now reports through the APP Plus quality measure set, choosing between eCQMs, MIPS CQMs, and Medicare CQMs. A practical guide to the data, technical, and strategic choices ACOs face in 2026.

Editor’s note (updated June 2026): This guide was originally published in April 2024 by Dynamic Health IT, Inc. (DHIT) when the CMS Web Interface sunset was still upcoming. The Web Interface was retired at the end of the 2024 performance year, and every MSSP ACO has since transitioned to APP/APP Plus reporting. We’ve updated this page to reflect the current PY 2026 framework — including the expanded measure set and the time-sensitive note that PY 2026 is the last year ACOs can use MIPS CQMs as an APP Plus reporting option. The PDF download retains its original April 2024 content as a historical reference; the page below reflects current state.

The post-Web-Interface reality

For close to a decade, MSSP ACOs had a reasonably forgiving path to quality reporting: pick a sample of 248 Medicare-assigned patients from a CMS-curated list, fill in the data, submit through the Web Interface.

The Centers for Medicare & Medicaid Services (CMS) retired the Web Interface at the end of the 2024 performance year, and every ACO in the Medicare Shared Savings Program is now reporting through the APM Performance Pathway or its expanded successor, APP Plus.

The Web Interface let ACOs report on 248 sampled patients. APP Plus asks them to report on everyone.

ACOs went from sample-based reporting on a few hundred patients to all-payer reporting across their full assigned population, with a 70% data completeness threshold and quality measures calculated from actual clinical data rather than chart-abstracted samples. For ACOs that had built quality reporting workflows around the old model, the transition has been a multi-year scramble.

What this guide covers

  • The differences between eCQM, MIPS CQM, and Medicare CQM reporting paths
  • Why multi-EHR data aggregation is the real challenge for ACOs (and what makes Medicare CQMs different)
  • The PY 2026 APP Plus measure set and why this is the last year for MIPS CQMs
  • How FHIR Bulk fits as the long-term technical foundation
  • Where UDS reporting overlaps for FQHC-led ACOs

The three reporting paths

Under APP Plus, ACOs choose one of three collection types for the quality measures. The choice has significant operational consequences:

eCQMs

All-payer · Certified EHR data

  • Calculated from certified EHR data in QRDA or FHIR format
  • Requires CEHRT and integration capability
  • Eligible for the eCQM/MIPS CQM reporting incentive bonus
  • Best fit for ACOs with mature, connected data infrastructure

MIPS CQMs

All-payer · Registry-reported

  • Calculated and submitted through a CMS Qualified Registry
  • Broader source data — not limited to certified EHRs
  • Eligible for the eCQM/MIPS CQM reporting incentive bonus
  • PY 2026 is the last year MIPS CQMs are an APP Plus option

Medicare CQMs

Medicare FFS only · ACO-specific

  • Introduced specifically to ease ACO reporting burden
  • Reports only on Medicare fee-for-service beneficiaries
  • Dramatically reduces data aggregation complexity
  • Not eligible for the eCQM/MIPS CQM incentive

eCQMs and MIPS CQMs cover all payers. Good for benchmarking, but it means aggregating data on every patient across every participating practice. Medicare CQMs narrow the population to Medicare FFS beneficiaries only, which are exactly the patients CMS is measuring the ACO on, at the cost of forfeiting the eCQM/MIPS CQM reporting incentive.

Why multi-EHR data aggregation is the real challenge

This is the part the original 2024 paper got most right, and it’s only become more relevant since: the technical difficulty of ACO reporting is not measure calculation. It’s data aggregation.

A typical MSSP ACO includes multiple Tax Identification Numbers (TINs) — independent practices, often hospital-affiliated, sometimes Federally Qualified Health Centers, occasionally a Rural Health Clinic or two. Each runs its own EHR. Each has its own definition of what “patient” means, its own coding habits, its own data quality. To report APP Plus quality measures, the ACO has to:

  • Collect structured clinical data from every participating TIN, ideally as QRDA Category I or FHIR resources
  • Deduplicate patients who appear across multiple practices (which is half the assigned population in some ACOs)
  • Normalize coding inconsistencies across EHR vendors — value sets, units, problem list conventions
  • Calculate measures across the aggregated dataset, not per-practice
  • Validate that the result meets the 70% data completeness threshold across the full assigned population

None of this is theoretical. CMS introduced a “Complex Organization Adjustment” beginning with CY 2025 specifically because Virtual Groups and ACOs faced material disadvantages in eCQM reporting compared to single-EHR practices. The adjustment helps with scoring. It doesn’t eliminate the underlying technical problem.

The APP Plus measure set is growing

APP Plus isn’t static. CMS has laid out a multi-year expansion that increases the reporting burden every year through PY 2028:

YearMeasuresTotal
PY 20254 eCQMs/MIPS CQMs/Medicare CQMs + 1 admin claims + CAHPS for MIPS6
PY 2026 (current)5 quality measures + 2 admin claims + CAHPS · Colorectal cancer screening added. Last year for MIPS CQMs.8
PY 2027Substance use disorder measures phase in9
PY 2028Social determinants, immunizations, and additional measures11

The implication for ACOs is straightforward: any infrastructure investment made today needs to support not the PY 2026 measure set but the PY 2028 one. Shortcuts that get you through this year’s submission will compound into next year’s emergencies. For more on the specific measures being phased in, see our blog post on the APP Plus quality measure set.

Bulk FHIR: the long-term foundation

The 2024 paper called FHIR “a pivotal component of long-term solutions”. CMS, ASTP/ONC, and the major standards bodies have converged on FHIR R4 with USCDI v3 as the foundation for the next generation of quality and interoperability reporting.

For ACOs, the relevant pieces are:

  • FHIR Bulk Data Access — the standardized mechanism for pulling patient populations from participating EHRs, replacing per-patient API calls that don’t scale to ACO-sized populations
  • USCDI v3 data elements — the standardized clinical data set that quality measure calculations are increasingly written against
  • FHIR-based eCQMs — the gradual transition from QRDA-based calculation to FHIR-native logic, with HL7’s Da Vinci and CodeX accelerators leading the standards work

ACOs that invest in FHIR-capable data infrastructure now won’t have to re-platform when FHIR-native quality reporting becomes the default path. Those that wait will be re-platforming under deadline pressure.

A note on UDS overlap for FQHC-led ACOs

ACOs that include Federally Qualified Health Centers face an additional reporting layer: HRSA’s Uniform Data System (UDS), which has its own quality measure requirements and is moving toward FHIR-based patient-level submission through the emerging UDS+ framework. The good news is that HRSA has aligned UDS quality measures with eCQM logic. The data infrastructure built for APP Plus can do double duty for UDS, assuming the visit logic and patient identifiers reconcile cleanly. We cover this in detail in our UDS Reporting Guide for FQHCs.

Download the original white paper

DHIT’s April 2024 analysis of the Web Interface sunset, the introduction of Medicare CQMs, and the FHIR-based future. Free download.

About the DHIT ACO solution

Dynamic Health IT, Inc. (DHIT) has provided quality measure calculation and reporting software since 1999. Our CQMsolution platform is ONC-certified for eCQM calculation, and our Dynamic FHIR API handles the data ingestion side — FHIR Bulk, QRDA Category I, and FHIR resources from different EHRs — feeding into a DataStore designed to aggregate, deduplicate, and calculate measures across multi-TIN ACO populations.

ACOs need exactly this kind of multi-EHR infrastructure, and that’s why Dynamic Health IT built an end-to-end ACO reporting solution combining our CQMsolution quality measure engine, the Dynamic FHIR API, and an ACO performance dashboard.

For a walkthrough of the platform, or a working session on your ACO’s specific data aggregation challenges, get in touch.

ACO Quality Reporting: Frequently Asked Questions

What replaced the CMS Web Interface for ACO quality reporting?

The CMS Web Interface was retired at the end of the 2024 performance year. Beginning in PY 2025, all Medicare Shared Savings Program ACOs report through the APM Performance Pathway (APP) — specifically the expanded APP Plus quality measure set. ACOs can choose to report quality measures as eCQMs, MIPS CQMs, or Medicare CQMs.

What is the difference between eCQMs, MIPS CQMs, and Medicare CQMs?

eCQMs are electronic clinical quality measures calculated from certified EHR data using standardized FHIR or QRDA formats. MIPS CQMs are calculated and submitted through a CMS Qualified Registry, allowing broader source data beyond certified EHRs. Medicare CQMs are a collection type introduced specifically for ACOs — they focus only on Medicare fee-for-service beneficiaries, dramatically reducing the data aggregation burden compared to all-payer reporting.

What is the APM Performance Pathway, and what is APP Plus?

The APM Performance Pathway (APP) is the MIPS reporting framework that all MSSP ACOs are required to use. APP Plus is the expanded quality measure set that began in PY 2025, with the number of required measures growing each year: 6 total in PY 2025, 8 in PY 2026, 9 in PY 2027, and 11 in PY 2028. PY 2026 is also the final year MIPS CQMs are eligible as a collection type under APP Plus.

How many quality measures do ACOs report in PY 2026?

In Performance Year 2026, MSSP ACOs report 8 measures total: 5 eCQMs/MIPS CQMs/Medicare CQMs in the APP Plus quality measure set, 2 administrative claims-based measures, and the CAHPS for MIPS Survey. PY 2026 is also the last year ACOs can use MIPS CQMs as part of APP Plus.

Why is data aggregation harder for ACOs than for individual practices?

ACOs typically include multiple Tax Identification Numbers (TINs), each running its own EHR. Reporting requires aggregating clinical data across all participating practices, deduplicating patients who appear in multiple EHRs, and meeting a 70% data completeness threshold across the full assigned population. This multi-EHR aggregation challenge — not measure calculation — is the primary technical difficulty of post-Web-Interface ACO reporting.

More on ACO quality reporting

Blog

MSSP ACOs: 2025 Final Rule Impact

DHIT’s analysis of the APP Plus quality measure set and the eCQM reporting incentive for ACOs beginning PY 2025.

White Paper

UDS Reporting Guide for FQHCs

For FQHC-led ACOs: how HRSA’s UDS+ framework and eCQM-aligned quality measures overlap with ACO reporting requirements.

Product

CQMsolution

The ONC-certified quality measure engine behind DHIT’s ACO, UDS, and MIPS reporting solutions. Built for multi-EHR environments.

Quality Measure & Interoperability Solutions

Tired of stitching ACO data together by hand?

Talk with the DHIT team about how CQMsolution and the Dynamic FHIR API can handle the multi-EHR aggregation, deduplication, and APP Plus measure calculation your ACO is doing in spreadsheets today.