Public health agencies depend on data that originates in clinical systems: which vaccines were given, which reportable diseases were diagnosed, what symptoms are showing up in emergency departments, and what laboratories are finding. For decades that data moved by fax and phone, late and incomplete. Federal incentive programs and EHR certification rules have spent more than a decade pushing it into automated electronic interfaces. This guide explains the reporting types your EHR is expected to support, what certification does and does not guarantee, how the reporting measures work in the incentive programs, and what it takes to get an interface into production.
Why EHRs report to public health
Two forces drive it. The first is state law: every state requires providers and laboratories to report certain diseases and conditions, and most require or strongly encourage reporting of immunizations to a state registry. Those obligations exist whether or not you have an EHR. The second is the federal incentive structure. The Medicare Promoting Interoperability program for hospitals and the Promoting Interoperability category of the Merit-based Incentive Payment System for clinicians both include a public health and clinical data exchange objective, and the certification criteria that EHR vendors must meet include public health reporting capabilities. The result is that the software can do it and the payment programs reward doing it.
The main reporting types
- Immunization registry reporting. The EHR sends each administered vaccine to the state or jurisdictional immunization information system, and can query the registry for a patient's history and forecast. Applies to nearly every practice that vaccinates.
- Syndromic surveillance. Emergency departments and urgent care settings send de-identified or limited visit data (chief complaint, diagnosis, disposition) in near real time so agencies can detect outbreaks. Ambulatory practices may report where the jurisdiction accepts it.
- Electronic case reporting (eCR). The EHR automatically detects when a diagnosis, lab result, or medication matches a reportable condition trigger and sends an initial case report to public health through a national intermediary, which routes it to the right jurisdiction. This is replacing manual disease reporting.
- Electronic laboratory reporting. Laboratories, including hospital labs, send reportable results directly to public health. Practices with in-house labs may fall under this.
- Public health registry and clinical data registry reporting. Cancer registries, specialty registries, and other registries designated by the jurisdiction or a specialty society.
- Antimicrobial use and resistance surveillance. A hospital-specific measure reporting to the national healthcare safety network.
Which of these apply to you depends on your setting and your state. An ambulatory primary care practice typically needs immunization reporting and electronic case reporting; a hospital needs most of the list.
What certification guarantees
The federal health IT certification program includes specific public health criteria: transmission to immunization registries, transmission to public health agencies for syndromic surveillance, electronic case reporting, and transmission of reportable laboratory tests, among others. A certified EHR has demonstrated it can produce the required message formats and, in more recent editions, support the specified standards such as HL7 Version 2 messaging for immunizations and lab results and the FHIR-based or CDA-based electronic initial case report.
Certification is a capability, not a connection. The vendor proved the software can generate a conforming message. Getting that message to your state registry requires onboarding with the agency, credentials, testing, and often vendor implementation work that may be priced separately.
When comparing or renewing an EHR, ask which public health criteria the product is certified for, which jurisdictions it has live connections in, and what the implementation fee and timeline are for each interface in your state.
How incentive programs score it
In the clinician program, the public health and clinical data exchange objective generally requires active engagement with two registries: immunization registry reporting and electronic case reporting are the required pair in recent performance years, with exclusions available if a jurisdiction cannot accept the data or the clinician does not perform the relevant activity. Additional registries earn bonus consideration in some years. Hospitals have a longer required list.
Active engagement is defined in stages: registered to submit, testing and validation, or in production. Being in the registration or testing stage is acceptable for a limited period, after which the program expects production. The details change from year to year in the annual payment rule, so confirm the current requirements before the performance period rather than relying on last year's checklist. Documentation matters: keep the registration confirmation, testing correspondence, and production go-live acknowledgement from each agency, because these are what an audit will ask for.
Getting connected: registration, testing, production
- Identify the receiving agency for each reporting type in your state and find its onboarding page. Immunization registries and syndromic surveillance are usually state health department programs; electronic case reporting goes through a national platform that jurisdictions have joined.
- Register intent to submit with the agency, which starts the clock for incentive purposes and puts you in the onboarding queue. Queues can be long; start early in the year.
- Engage the EHR vendor to build or enable the interface. Confirm cost, timeline, and who configures the trigger codes for case reporting.
- Complete message validation with the agency, which typically involves submitting test messages and correcting format or content errors until they pass.
- Move to production and obtain written confirmation from the agency. For bidirectional immunization interfaces, verify that history queries return results.
- Monitor ongoing for rejected messages, interface outages, and changes in the agency's specifications, which occur periodically.
Common problems and how to avoid them
The most frequent failure is data quality: messages rejected because a patient's address is incomplete, a vaccine lot number is missing, or a race and ethnicity field is blank. Front-desk and clinical intake workflows need to capture the fields the registry requires, and someone should review the rejection queue weekly. The second is silent interface failure: a connection that stopped sending months ago without anyone noticing. Set up monitoring or a periodic reconciliation between vaccines administered and messages acknowledged.
For electronic case reporting, the trigger logic is maintained centrally and updated as reportable conditions change; make sure your EHR is consuming the updates. And for all reporting, treat the agency's acknowledgements as records: they demonstrate compliance with state law and with the incentive program at the same time.
Common questions
Is public health reporting required or optional?
Disease and immunization reporting is required by state law regardless of technology. Doing it electronically through the EHR is what the federal incentive programs measure and what certified EHRs are built to support.
What is electronic case reporting?
An automated process in which the EHR detects a reportable condition from diagnoses, lab results, or medications and sends an electronic initial case report to public health through a national intermediary, replacing manual fax or phone reporting.
Our state registry cannot accept our data yet. Does that hurt our incentive score?
The programs include exclusions for situations where a jurisdiction cannot accept electronic data or where the clinician does not perform the relevant activity. Document the basis for the exclusion in case of audit, and confirm the current year's rules.
Does the EHR vendor handle the registry onboarding?
Usually the vendor builds and configures the interface, but the practice registers with the agency, provides the credentials, and owns the testing and go-live relationship. Ask the vendor exactly what is included and what is billed separately.