Quick answer: Electronic laboratory reporting (ELR) is the structured electronic submission of reportable lab results from a clinical lab to a public-health agency — typically over HL7 v2.5.1 ORU messages per the CDC ELR implementation guide and state-specific APHL extensions. Every U.S. state requires ELR for nationally notifiable conditions; the lab’s LIS is responsible for identifying reportable results, mapping codes to LOINC and SNOMED CT, and delivering the message to the agency’s gateway.
Lab directors, LIS analysts, and public-health coordinators run into ELR on day one of any specialty (toxicology, infectious disease, molecular) or public-health lab evaluation. This guide explains what ELR is, what triggers it, how the messaging works, and what an LIS needs to do to make ELR routine instead of a per-result manual process.
What ELR is
ELR is the lab side of public-health surveillance. When a clinical lab reports a positive result for a condition the state considers reportable — measles, gonorrhea, Salmonella, lead levels above a threshold, certain antimicrobial-resistance markers — the lab is legally required to submit that result to the state or territorial public-health agency. ELR is the automated, structured-message version of that submission, replacing fax forms and phone calls that older surveillance workflows depended on.
Three forces drove ELR adoption:
- Meaningful Use (now Promoting Interoperability) — CMS recognized ELR as a measure starting in 2011, pushing every certified EMR and most LIS systems to support it.
- State surveillance mandates — every U.S. state has reportable-conditions law, and most states moved to mandatory ELR through the 2010s.
- Pandemic response — SARS-CoV-2 and COVID-19 reporting accelerated ELR adoption further, with CDC and state agencies tightening message-quality expectations.
The result: ELR is now table stakes for any lab running clinical or specialty work. An LIS that cannot do ELR cleanly is a non-starter for public-health labs and a friction point for clinical labs that have any infectious-disease, molecular, or toxicology work in their menu. Serology and infectious-disease immunoassay testing is a common source of reportable results — see the immunology LIS guide for how serology runs on the same high-volume immunoassay backbone that feeds automated ELR straight from the LIS.
What triggers an ELR submission
Each state publishes a list of reportable conditions, plus the LOINC-coded tests and SNOMED-coded organisms or analytes that trigger a report. The lists differ by state but share a common backbone derived from the CDC Nationally Notifiable Diseases list.
Common reportable categories:
- Communicable diseases — HIV, hepatitis A/B/C, syphilis, gonorrhea, chlamydia, tuberculosis, measles, mumps, pertussis, COVID-19, influenza in some states.
- Foodborne illness — Salmonella, Shigella, E. coli O157:H7, Listeria, Campylobacter, Vibrio.
- Vector-borne disease — Lyme, West Nile, Zika, Eastern equine encephalitis.
- Antimicrobial-resistance markers — CRE (carbapenem-resistant Enterobacteriaceae), C. difficile in some states, MRSA blood culture in some.
- Respiratory viruses — RSV, SARS-CoV-2, novel-influenza in some.
- Environmental and exposure — childhood lead levels (often ≥3.5 µg/dL), elevated mercury, certain pesticide exposures.
- Cancer registry — tumor markers, pathology specimens for reportable cancer types (typically separate workflow with its own implementation guide).
The lab’s LIS is responsible for evaluating each finalized result against the state’s reportable list. When a match occurs, the system generates the ELR message and routes it to the state gateway. Many of these reportable results originate at the microbiology bench — a culture-identified organism, or an antimicrobial-susceptibility result flagging a resistance marker such as CRE or MRSA. See the microbiology LIS guide for how culture workup and AST interpretation produce the SNOMED-coded organism result that triggers the ELR.
How the messaging works
ELR rides on HL7 v2.5.1 ORU messages — the same message type clinical labs use to deliver results to EMRs — with additional structure required by public-health implementation guides.
Standards and code sets
- HL7 v2.5.1 is the canonical message version for ELR. Most state implementation guides are version-locked to v2.5.1.
- APHL ELR 2.5.1 Implementation Guide defines the segments, fields, and constraints. Maintained by the Association of Public Health Laboratories in collaboration with CDC.
- LOINC identifies the test or observation (e.g. LOINC 94500-6 for SARS-CoV-2 RNA).
- SNOMED CT identifies the organism, finding, or interpretation (e.g. SNOMED 840533007 for “Severe acute respiratory syndrome coronavirus 2”).
- HL7 standard code sets (race, ethnicity, gender) per the implementation guide.
Message segments
A typical ELR ORU message includes:
- MSH — message header, sending facility, receiving agency, message type.
- PID — patient demographics, including race, ethnicity, address required for surveillance.
- NK1 — next-of-kin if applicable.
- OBR — order details, ordering provider, specimen collection date and source.
- OBX — observation values; one OBX per reported result.
- SPM — specimen detail (type, source, collection method).
- NTE — notes; some agencies require interpretive narrative.
Field-level requirements vary by state. California, Texas, New York, and Massachusetts each have local extensions to the APHL guide; an LIS configured for ELR needs to support per-state field mapping.
Transport
- MLLP over secure VPN — common for state-hosted ELR gateways.
- HTTPS REST/SOAP — used by some modern state systems and the CDC.
- SFTP batch — used as fallback or backup channel.
The state publishes the endpoint, transport, and connectivity requirements. The lab’s LIS or interface engine establishes and maintains the connection.
ELR workflow inside the lab
A clean ELR workflow looks like this:
- Test ordered and resulted in the LIS — normal clinical flow.
- Reportability evaluation — the LIS checks the finalized result against the state’s reportable-conditions rule set. Match = ELR candidate.
- Code mapping — the LIS maps the result to LOINC, the organism or analyte to SNOMED, and the demographics to the state’s required code sets.
- Message construction — the LIS generates the HL7 v2.5.1 ORU message per the APHL guide and state extension.
- Routing — the message goes to the state’s ELR gateway over the configured transport. Acknowledgments (HL7 ACK or HTTPS response) are captured.
- Retry and exception handling — failed deliveries enter an exception queue; the lab’s ELR coordinator works the queue.
- Audit trail — every ELR message and acknowledgment is logged with timestamps and message IDs for inspection.
Done well, the lab sends thousands of ELR messages per month with no manual touch. Done poorly, the lab’s ELR coordinator hand-builds messages in a spreadsheet and faxes overflow. For the operational lifecycle in depth — reportable-condition detection, jurisdiction routing, and reconciling the agency’s acknowledgment after a message is sent — see how a public health LIMS automates ELR.
Common ELR pitfalls
- Per-state code set drift. A LOINC code that satisfies California may not satisfy Texas; the LIS must support per-state code maps.
- Race and ethnicity coding. OMB-aligned codes are required by many states; legacy free-text demographics break ELR.
- Specimen collection time precision. Some states require minute-level precision; the LIS must capture it at accessioning.
- Result amendment handling. Corrected results require ELR retransmission with proper status codes; missing this creates duplicate-case headaches at the agency.
- Test menu drift. As the lab adds new tests, the reportability rule set must update with them.
- State endpoint changes. State agencies move endpoints; an LIS without monitored connectivity loses messages silently.
How LIMS IQ supports ELR
LIMS IQ supports the HL7 v2.5.1 ORU messaging, LOINC and SNOMED CT code mapping, and per-state field requirements that ELR depends on. The platform’s HL7 / FHIR integration layer handles the message construction; the public health LIMS solution wraps the broader workflow (multi-site coordination, surveillance dashboards, agency reporting); the audit trail captures every sent message and acknowledgment for inspection.
For labs in a state with mature ELR requirements (most of the country at this point), configuration includes:
- Reportable-conditions rule set — per state, mapped to your test catalog.
- Code maps — LOINC for tests, SNOMED for organisms and findings, OMB race/ethnicity codes.
- State endpoint configuration — transport, authentication, retry policy.
- Exception workflow — queue for rejected or delivery-failed messages.
See the public health LIMS solution for the broader public-health surveillance context and the LIS glossary for related ELR-adjacent terms (APHL, LRN, CDC NNDSS).
Related reading
- Public health LIMS solution — the broader public-health workflow including ELR
- HL7 LIS integration — protocols and message types behind ELR
- Clinical LIS guide — clinical-lab context that ELR sits inside
- LIS glossary — definitions for APHL, LRN, LOINC, SNOMED CT, MLLP
- Integrations hub — full LIMS IQ integration coverage including ELR
Request a demo to see how LIMS IQ runs ELR against your state’s reportable list, or contact the team with state-specific implementation questions.