Electronic Case Reporting for MIPS: What the 2026 Suppression Actually Means

eCR is suppressed for 2026

If you only read the headline, “CMS suppressed the eCR measure” sounds like one less thing to worry about. Suppression doesn’t remove the measure from your reporting obligations. It removes the performance scoring while the public health infrastructure catches up.

Here’s the mechanism. The Promoting Interoperability category is 25% of your MIPS final score. Within it, the Public Health and Clinical Data Exchange objective requires eligible clinicians to report two measures: Immunization Registry Reporting and Electronic Case Reporting. While eCR is suppressed, you still attest to it, “Yes,” “No,” or a claimed exclusion, and you receive maximum points no matter what you attest. But omit it entirely and CMS scores it at zero.

What electronic case reporting actually is

Electronic case reporting is the automated exchange of case reports from an EHR to the appropriate public health agency (PHA) when a patient is diagnosed with, or suspected of having, a reportable condition. It replaces the fax-and-phone workflows that the COVID-19 pandemic exposed as too slow and too incomplete to support real public health response.

The loop has four moving parts:

• Trigger. A reportable diagnosis is entered in the EHR, which matches against the trigger code set distributed through eRSD (Electronic Reporting and Surveillance Distribution).
• eICR. The EHR generates an electronic initial case report — an HL7 CDA document (or its FHIR equivalent) capturing the clinical and demographic detail the PHA needs.
• Transmission. The eICR routes through the APHL Informatics Messaging Services (AIMS) platform to the correct PHA.
• Reportability Response. The PHA returns an RR telling the provider whether the case is reportable and what, if anything, happens next.

None of that happens without two things: an EHR (or relied-upon module) that can build and send a conformant eICR, and a PHA that has declared readiness to receive it.

Why “suppressed” is a window, not a reprieve

The temptation is to read suppression as permission to defer eCR until CMS makes it count again. That’s the wrong read, for three reasons.

First, onboarding is slow and queue-based. Getting from “registered with the PHA” to “validated data production” runs through the CDC, APHL, and your state health department. When suppression lifts, everyone who waited will be in the same queue at the same time.

Second, suppression is explicitly temporary. CMS framed it as a response to the CDC’s onboarding pause, and in the same rule adopted a general measure-suppression policy to handle situations like this going forward. The mechanism is now standing infrastructure, but the eCR suppression itself is tied to a backlog that’s meant to clear.

Third, the standards keep moving whether you’re reporting or not. eICR and eRSD versions are advancing on their own schedule. An organization that “waits for eCR to matter again” will find that when it does, the conformance bar has moved, and they’re implementing under deadline pressure instead of during a grace period.

Active engagement: the Option 1 to Option 2 trap

To meet eCR (when scored), you demonstrate “active engagement” with a PHA in one of two ways:

• Option 1 — Pre-Production and Validation. You’ve registered with the PHA and are testing or awaiting an invitation to test. Registration must be completed within 60 days of the start of the performance period.
• Option 2 — Validated Data Production. You’re fully integrated and sending production eICRs to the PHA.

The trap is in the fine print: a clinician can only remain in Option 1 for a single performance period. If you were in Option 1 in 2025, you’re expected to be in Option 2 in 2026.

The standards are a moving target

eCR conformance isn’t a fixed spec you implement once. The eICR document standard, the trigger distribution mechanism, and the certification criteria all advance on their own cadence and many public health agencies are setting their own sunset dates for older versions:

Component	What’s changing	Timing
eICR (HL7 CDA)	Migration from older eICR 1.1 to the 3.x line; full condition triggering required	Many PHAs setting 2026–2027 cutoffs
eRSD	Version 3+ required for full triggering across all reportable conditions	Required by many PHAs now
eICR (FHIR)	FHIR-based reporting via the eCR Now FHIR App; the long-term direction	Growing alongside CDA
Certification	ONC criterion 45 CFR 170.315(f)(5) for transmission to public health	CEHRT must be certified by Dec 31, 2026

The practical takeaway: whatever you stand up needs a maintenance path, not just an install date. Older eICR 1.1 senders in particular should be planning their move to the 3.x line now, and confirming their relied-upon software keeps pace with eRSD as the trigger set expands.

TEFCA: the emerging bonus path

Alongside the suppression, CMS added a bonus under the same Public Health and Clinical Data Exchange objective: up to five bonus points for organizations that exchange public health data through a Trusted Exchange Framework and Common Agreement (TEFCA) participant. It’s capped at five points and it’s optional, but it signals where CMS expects public health data exchange to head. For organizations already weighing a QHIN connection for other reasons, the eCR-adjacent bonus is one more line in the business case.

About the Dynamic eCR Gateway

Dynamic Health IT, Inc. (DHIT) addresses electronic case reporting through its Dynamic eCR Gateway — a workflow built around the FHIR-based eCR Now app that automates eICR generation and transmission from the EHR to public health agencies via AIMS. It’s designed to take the trigger-to-Reportability-Response loop off your staff’s plate.

On the HL7 side, our TIE — The Interface Engine handles the CDA and HL7 v2.x messaging that eICR transmission depends on, and our Dynamic FHIR API and ConnectEHR are ONC-certified for the key interoperability criteria. More than 75 EHR systems already use DHIT applications as relied-upon software, which means we’ve handled the public-health-reporting plumbing for organizations that didn’t want to build it themselves.

If you’re using the suppression window to get onboarded, or you’re an older eICR 1.1 sender who needs to move to the 3.x line, get in touch for a working session on your eCR setup.