Active Engagement Is Not a Feeling: How to Prove Public Health Reporting for PI
Public health reporting can look complete when the technology is working. The EHR is live. The interface appears connected. The vendor says the registry connection is fine. Someone on the team remembers an email from the state public health agency.
That may sound reassuring, but it is not enough for Promoting Interoperability.
For 2026 MIPS Promoting Interoperability, CMS requires eligible clinicians to collect required measure data in certified EHR technology for at least 180 continuous days during the calendar year, provide a CMS EHR Certification ID from the CHPL, and submit the level of active engagement for required public health measures.
Here is the main point: active engagement is not a feeling. It is a status your practice must be able to prove.
1. Why Public Health Reporting Deserves an End-of-Month Check
I recommend treating public health reporting as an evidence issue, not just an interface issue.
The Public Health and Clinical Data Exchange objective includes two required measures for 2026 Promoting Interoperability: Immunization Registry Reporting and Electronic Case Reporting. CMS states that practices can receive full points for this objective by submitting “Yes” for both required measures, or by submitting one “Yes” and one applicable exclusion. CMS also allows up to 5 bonus points for one or more optional public health measures, including Public Health Reporting Using TEFCA.
That means your practice needs to know more than whether the system is connected.
You need to know:
Which public health measures you plan to report
Which measures are required
Which optional measures may apply
Which exclusions you plan to claim
What evidence supports each decision
Who owns the documentation
This is where practices often get into trouble. They confuse system capability with reporting proof.
A working connection is helpful. A complete proof file is safer.
2. What Active Engagement Means in Plain English
Active engagement means your practice is actively working with a public health agency or registry to submit electronic public health data in a meaningful way using certified EHR technology. In practice, this usually falls into two categories: Pre-Production and Validation or Validated Data Production.
For Immunization Registry Reporting, CMS states that clinicians must submit their level of active engagement when reporting the measure. The level may be Pre-Production and Validation or Validated Data Production. CMS defines Validated Data Production as completing testing and validation and electronically submitting production data to the public health agency or clinical data registry.
Let’s make that simpler.
Pre-Production and Validation means your practice is still moving through setup, testing, or validation.
Validated Data Production means the testing phase is done, and your practice is sending production data.
Both require documentation.
Your practice should be able to answer one question quickly:
Which active engagement level applies to each public health measure, and where is the proof?
If the answer is “the vendor knows,” keep digging.
3. Required Measure One: Immunization Registry Reporting
Immunization reporting can create confusion, especially for specialty practices that do not routinely give vaccines.
The measure is not something to skip mentally just because your practice is not a primary care clinic. CMS expects the clinician to be actively engaged with a public health agency to submit immunization data and receive immunization forecasts and histories from an immunization registry or immunization information system.
Your proof file should show:
Registry registration
Save the registration confirmation, portal record, or email from the immunization registry.Active engagement status
Identify whether the practice is in Pre-Production and Validation or Validated Data Production.Interface status
Document whether the interface is pending, testing, validating, or live.Registry communication
Save emails, tickets, portal messages, and notices from the registry or public health agency.Submission or query evidence
Store screenshots, reports, acknowledgments, or vendor documentation that shows the practice’s activity.Exclusion support
If you claim an exclusion, document why it applies. Do not rely on memory or “we thought we qualified.”
This measure can look easy until the evidence lives in five different places.
That is why I would not wait until submission season to find the immunization proof.
4. Required Measure Two: Electronic Case Reporting
Electronic case reporting, or eCR, is the electronic submission of reportable conditions to a public health agency.
This measure can be tricky because vendors may support eCR, but vendor capability does not automatically prove practice-level active engagement. CMS’s eCR specifications discuss active engagement and validated data production for electronic case reporting and note certified health IT developer implementation details tied to eCR.
For eCR, your practice should confirm:
Whether your public health jurisdiction can receive eCR data
Whether your EHR supports the required eCR workflow
Whether your practice registered with the public health agency
Whether testing or validation has started
Whether production data is being sent
Whether public health agency communications are saved
Whether any exclusion applies
Here is the risk: a practice may assume “the EHR has eCR” means “we are covered.”
That assumption can fail.
Your evidence needs to connect the vendor’s capability to your practice’s actual reporting status. The proof file should show what your practice did, when it happened, which public health agency was involved, and which active engagement level applies.
5. Optional Public Health Measures and the TEFCA Bonus Opportunity
Optional public health measures can support a stronger PI strategy, but optional does not mean casual.
CMS allows up to 5 bonus points for submitting a “Yes” response for one or more optional Public Health and Clinical Data Exchange measures. These optional measures include Public Health Registry Reporting, Clinical Data Registry Reporting, Syndromic Surveillance Reporting, and Public Health Reporting Using TEFCA.
The TEFCA opportunity deserves special attention.
TEFCA means the Trusted Exchange Framework and Common Agreement. It supports trusted health information exchange across networks. For PI, the optional TEFCA public health reporting bonus is not a “we like TEFCA” checkbox.
CMS states that the TEFCA public health reporting measure requires the clinician to participate as a signatory to a Framework Agreement, not be suspended from TEFCA exchange, submit health information using TEFCA to a public health agency, be in active engagement Option 2, and use CEHRT functions to exchange with the public health agency.
That means TEFCA bonus readiness should answer these questions:
Are we actually using TEFCA for public health reporting?
Are we connected through a QHIN, HIE, HIN, health system, or EHR vendor pathway?
Can we prove active engagement Option 2?
Can we show public health agency reporting through TEFCA?
Can we show the CEHRT functions used for the exchange?
Can we prove we are not suspended from TEFCA exchange?
TEFCA may be a real bonus opportunity for some practices.
For others, it may be a future-state strategy.
Either way, treat it as an evidence review, not a buzzword.
6. Build a Public Health Reporting Proof File
A proof file does not need to be fancy. It needs to be complete, clear, and easy to review.
I recommend creating one shared folder or tracker for public health reporting evidence. For each measure, include:
Measure name
Label the measure clearly: Immunization Registry Reporting, Electronic Case Reporting, or an optional measure.Reporting decision
Mark the measure as “Yes,” excluded, optional, or under review.Active engagement level
Document Pre-Production and Validation or Validated Data Production.Public health agency or registry name
Identify the agency, registry, or clinical data registry involved.Registration proof
Save confirmation emails, portal screenshots, onboarding records, or registry documentation.Interface status
Note whether the interface is pending, testing, validating, or in production.Communication log
Store emails, help desk tickets, vendor notes, and public health agency messages.Production or testing proof
Save acknowledgments, screenshots, interface reports, or validation results.Exclusion support
Save the reason, rule basis, and evidence for any exclusion.Owner and review date
Name the staff member responsible and record the last review date.
This kind of file helps practice managers, physicians, compliance teams, and reporting vendors stay aligned.
It also avoids the classic PI problem: everyone thought someone else had the proof.
7. Common Gaps That Create PI Risk
During an end-of-month active-engagement and interface evidence check, I would look for these gaps first.
Gap 1: The practice cannot name the active engagement level
If your team cannot say whether the practice is in Pre-Production and Validation or Validated Data Production, the evidence file is not ready.
Gap 2: The interface works, but the proof is missing
An interface can transmit data while documentation still fails. The technology may be working, but your practice still needs registry communications, validation records, screenshots, or production evidence.
Gap 3: Vendor documentation is not tied to the practice
A vendor may support immunization reporting or eCR across many clients. Your file should show your practice’s specific status.
Gap 4: Exclusions are assumed
Exclusions need support. “We do not do that here” is not a complete compliance record.
Gap 5: Evidence does not match the reporting period
Your evidence should support the actual reporting period. Old screenshots and outdated registration emails may help provide history, but they may not prove current-year readiness.
Gap 6: TEFCA gets treated like decoration
TEFCA can create a bonus opportunity, but only when the practice can support the required conditions. A TEFCA logo on a vendor slide is not the same as PI evidence.
8. A 30-Minute End-of-Month Check
Before the month closes, hold a short public health reporting huddle.
Use this agenda:
List every public health measure you plan to report.
Confirm required measures: Immunization Registry Reporting and Electronic Case Reporting.
Identify any optional measures.
Confirm active engagement level for each measure.
Locate registry and public health agency communications.
Confirm interface status.
Review exclusion support.
Check whether TEFCA bonus eligibility is real.
Assign owners for missing documentation.
Save everything in one proof file.
This meeting should include the person responsible for MIPS reporting, the EHR or IT contact, the compliance owner, and the practice manager.
For ACOs and APP participants, I would also include whoever owns participant-level or entity-level PI coordination. QPP notes that APP Promoting Interoperability reporting also requires collecting required measure data in CEHRT for at least 180 continuous days, along with a CMS EHR Certification ID from CHPL.
Do not let PI evidence live inside assumptions.
That is where reporting risk gets comfortable.
Public health reporting is not just about having a working interface. It is about proving the full reporting story.
For 2026 Promoting Interoperability, practices need clear evidence for Immunization Registry Reporting and Electronic Case Reporting, documented active engagement levels, saved registry communications, interface status, exclusion support, and a thoughtful review of optional measures, including TEFCA reporting.
The safest move is simple: check the evidence while the reporting period is still active.
Chirpy Bird can help your practice review active engagement, registry proof, eCR evidence, immunization reporting documentation, exclusions, and TEFCA bonus readiness.
Request a Second Opinion on public health reporting evidence
