Skip to main content
LIMS IQ Population health DOC PUBLIC-HEALTH
REV 2026-11

Public health LIMS software for state, county, and reference testing labs

Support community health with a secure Laboratory Information System built for public health testing labs. Centralize accessioning, automate reporting, and deliver results quickly to clinicians and agencies.

  • HL7 ELR reporting
  • Multi-site coordination
  • Outbreak surveillance
  • Role-based PHI access
Faster ELR routing Reportable conditions auto-route to state public health agencies on result release.
One tenant, many sites Central reference lab plus collection sites share one cloud LIS with site-scoped queues.
Surveillance-ready data Structured demographics and result data feed surveillance dashboards without spreadsheet exports.
Product view

An all-in-one cloud LIS that shortens turnaround time, reduces errors, and keeps patient care first.

Enhanced Data Management in Public Health

Manage high-volume public health data with confidence. LIMS IQ organizes patient records, test results, and surveillance data to improve accuracy, reduce errors, and simplify analytics and compliance reporting.

  • Workflow Efficiency
  • Reports
  • Enhanced Security
  • Sample Management
  • Enhanced Quality Control
  • Better Collaboration

Public health lab capabilities

9 capabilities

What a public health LIMS has to cover: high-volume intake, reportable disease routing, surveillance reporting, and the supply and portal logistics behind a multi-site testing program.

Workflow Efficiency

Streamline sample intake, accessioning, result review, and quality control so your team can handle high-volume testing with fewer bottlenecks.

Reports

Generate clinician, client, and public health reports in minutes with configurable templates for outbreaks, surveillance, and compliance.

Enhanced Security

Protect sensitive patient data with role-based access, audit trails, and secure storage that support HIPAA and local public health requirements.

Sample Management

Track specimens end-to-end with barcodes, chain of custody, and full visibility from collection to reportable results.

Enhanced Quality Control

Automate QC workflows and monitor performance trends to maintain consistent, reliable testing across programs.

Better Collaboration

Coordinate across departments and share data with hospitals and public health agencies to improve response times and reporting accuracy.

Submitter Portal

Give clinics, hospitals, and outreach sites paperless requisitions, bulk and repeat ordering, kiosk check-in, and 24/7 access to their own results.

Scheduled Surveillance Reporting

Run templated surveillance and program reports with guided filters, then schedule recurring delivery by email, SFTP, HL7, or portal with a full run history.

Kit and Supply Logistics

Track collection-kit stock per site with automatic consumption, reorder thresholds, low-stock alerts, and portal self-service ordering ahead of a surge.

A public health LIMS is a laboratory information management system built around the work a public health laboratory does for a population rather than for one ordering provider: high-volume intake from many submitters, testing across molecular, serology, microbiology, and chemistry programs, electronic laboratory reporting (ELR) of reportable conditions to health agencies, and the surveillance data that follows. State, county, and territorial public health laboratories use one, and so do the reference, hospital, and outreach laboratories that test specimens and report results to those agencies.

The sections below describe what the system has to cover: why agency reporting is a distinct problem, how the workflow fits together, how reportable-condition rules stay defensible, what happens after an ELR message leaves the lab, how surveillance and outbreak response change the operating tempo, and how a program runs surge testing across many sites. The HL7 v2.5.1 message itself is covered in the electronic laboratory reporting guide; this page covers the laboratory operation around it.

Why public health reporting is its own problem

Result reporting exists in every laboratory, but the public health version has characteristics a general clinical LIS often handles poorly:

  • Reporting is the product, not a side effect. In a commercial clinical lab, the result goes back to the ordering provider and the workflow ends. In a public health lab, the same result also flows outward to state surveillance, CDC programs, and outbreak responders. The outbound report is a primary deliverable with its own deadlines and its own compliance exposure.
  • The receiver is an agency, not an EMR. ELR rides on the same HL7 v2.5.1 ORU envelope as ordinary result messaging, but it conforms to the APHL ELR implementation guide, carries LOINC-coded results and SNOMED CT organism codes, and adds demographic and specimen fields an EMR never asks for. A message that satisfies an EMR interface can be rejected by a state gateway.
  • What is reportable changes by jurisdiction. Each state, territory, and tribal authority publishes its own reportable-conditions list, and they differ. A lab that serves patients across state lines has to evaluate each result against the right list and report to the right agency: the patient’s jurisdiction of residence, not the lab’s location, usually governs.
  • Deadlines are legal, not aspirational. Notifiable conditions carry statutory reporting windows: some immediate, some within a fixed number of days. Missing a window is a compliance failure, so the lab needs to prove not only that it sent a report but that it sent it on time and the agency received it.

A public health LIMS that treats agency reporting as a first-class workflow handles all four. A clinical LIS with a bolt-on “send to state” interface usually handles only the first.

How public health laboratory workflows fit together

Public health laboratories receive work from hospitals, clinics, collection sites, and surveillance programs. A connected LIMS keeps the specimen, result, reporting, and audit history together from intake through delivery:

  1. Receive and accession specimens. Capture electronic orders from submitting organizations or enter field-collection details, then assign barcodes and route work to the correct program and site.
  2. Run testing with quality controls. Coordinate molecular, serology, microbiology, chemistry, and other workflows with instrument interfaces, batch processing, reflex rules, and documented QC.
  3. Review and release results. Apply role-based review, preserve the audit trail, and release approved results through the lab’s configured workflow.
  4. Deliver results and required reports. Route results to submitters and configured public health recipients through supported interfaces, portals, and scheduled reports.
  5. Monitor operations across programs. Use structured result data, saved views, and scheduled reporting to track turnaround time, positivity trends, workloads, and site-level activity.

Each step leaves a record: who accessioned the specimen, which instrument produced the result, who released it, which reporting rule fired, and where the message went. That record is what the lab shows an inspector, a grant program, or an epidemiologist asking why a case appeared when it did.

Reportable-condition rules a lab can defend

The value of LIMS-driven reporting is that the lab owns the logic and can prove what it was. Every finalized result is evaluated against the rules for the patient’s jurisdiction: the test or organism, the result value or interpretation, and any threshold, such as a quantitative blood-lead level over the action limit. Evaluation runs on verified results, not preliminary ones, so a corrected or retracted result never generates a phantom report. Sound rule design covers:

  • Jurisdiction lists. Each rule states exactly what it matches and which jurisdiction it applies to. Jurisdictions publish and revise their own reportable-condition lists, so the LIMS should retain which rule set was in effect when a result was evaluated and let the lab answer “why was this result reportable in March but not January?” precisely. Ambiguous criteria are the most common reason a reportable result slips through unreported.
  • LOINC and SNOMED CT coding. ELR depends on accurate LOINC mapping for results and SNOMED CT codes for organisms. A wrong or generic code is a silent failure: the message sends but the agency cannot act on it. Codes belong in the test catalog alongside the test definition, governed once and reused everywhere.
  • Deadlines by condition. Conditions carry different reporting windows, immediate for some and a fixed number of days for others, and the window for the same condition can differ between jurisdictions. The rule that flags a result should also carry its deadline so the reporting queue can be worked by urgency rather than by arrival order.
  • Multi-jurisdiction routing by patient residence. Reference and outreach labs receive specimens from patients across many states, each with its own list, implementation guide, code requirements, and gateway. The LIMS holds per-jurisdiction rule sets and message configurations, evaluates each result against the rules for the patient’s residence, and routes to the matching agency endpoint; the condition determines whether a federal program such as NNDSS or the Laboratory Response Network also receives a report. Reporting logic maintained in spreadsheets outside the LIMS does not scale and fails inspection.
  • Specimen and demographic completeness. ELR requires collection details and demographic fields a routine order may not capture. The LIMS should enforce the data ELR needs at accessioning, backed by the same specimen tracking and chain-of-custody record the rest of the workflow uses.

In LIMS IQ, reportable test definitions, LOINC and SNOMED condition codes, and jurisdiction routing rules are configured in the application, reportable text is applied automatically through priority-based limit logic, and LOINC and CPT codes live on each test and panel in the compendium, so the lab does not maintain reporting logic outside the LIS.

What happens after the ELR message is sent

Most ELR explanations stop when the message leaves the lab. In practice, the work that determines whether a lab passes an inspection happens after transmission. An agency gateway does not silently accept everything: a message can be rejected because a LOINC code is missing or deprecated, a required demographic field is blank, an organism code does not map to a condition the agency recognizes, or the message fails the implementation guide’s conformance profile. Each rejection is a reportable result that has not been reported, and the clock is still running against its deadline.

A public health LIMS closes the loop by tracking each reportable result through sent, acknowledged, and rejected states, with the agency’s ACK or NAK recorded against the result that generated the message and the rejection reason captured so a coordinator can correct and resubmit. Two operational metrics fall out of that state tracking. Completeness asks whether every reportable result generated a successfully acknowledged report; the gap between “flagged reportable” and “acknowledged” is the lab’s outstanding risk. Timeliness asks whether each acknowledged report met its statutory window, which the LIMS can answer because it timestamped the finalized result, the transmission, and the acknowledgment. A result that was flagged but never acknowledged should surface for human attention well before its deadline, not in a retrospective audit.

The message layer behind this (HL7 v2.5.1 ORU structure, APHL implementation guides, transport options, and common gateway pitfalls) is covered in the electronic laboratory reporting guide.

Surveillance and outbreak response

Routine reporting is steady-state; outbreak response is a different operating tempo, and the same platform has to handle both. During an outbreak the lab faces a surge of specimens in a short window, needs case-level metadata that supports epidemiologic linkage, and has to get priority results to the surveillance team faster than the standard reporting cadence.

A public health LIMS supports this with structured demographic, geographic, and result data that can be queried for surveillance views: case counts by organism, positivity trends, and turnaround time by site. Saved views and configurable report templates let epidemiology and lab leadership monitor outbreak signals without exporting to spreadsheets for every question, and scheduled delivery keeps recurring program and grant reports flowing by email, SFTP, HL7, or portal while staff concentrate on the active response. The reporting machinery is the same; the templates, priority, and analytics are what flex.

Multi-agency collaboration matters as much as throughput. In LIMS IQ the same finalized result can route to the ordering clinician by HL7 ORU, to the patient portal, and to public health authorities by ELR from one approval action, so hospitals, health departments, and the lab work from the same result at the same time.

Surge testing across many sites

A public health testing program is rarely one building. A central reference lab, satellite labs, outreach clinics, and temporary collection sites all feed the same queue, and a surge multiplies specimens at every one of them. The logistics around the bench decide whether the lab keeps up:

  • Submitter portal. Clinics, hospitals, and collection sites work in a branded client portal with paperless digital requisitions that guide them to the right tests and block incompatible selections, bulk ordering and re-orders by spreadsheet upload, and kiosk-mode check-in on a tablet at outreach sites. The same portal gives them searchable results with cumulative trend views and 24/7 access, so the lab is not fielding faxes and phone calls for every order and every result. Submitters with an EHR send electronic orders (HL7 ORM) straight into the accessioning queue through the built-in HL7 engine.
  • Kit and supply logistics. Supply Monitor tracks collection-kit and consumable stock at every site in real time with a green, amber, or red health indicator and draws stock down automatically as specimens arrive from that site. Reorder thresholds trigger low-stock emails to custodians, sites can request supplies themselves from the portal, and Supply Orders carries each multi-line order from New through Completed with a packing list, shipment tracking, and a consolidated material ledger: the visibility a program needs before a surge, not after it runs out of swabs.
  • Batch release and reflex rules. Bidirectional analyzer interfacing loads serology and molecular results automatically, batch release lets technologists sign off large runs of normal results in a single action, and configurable reflex rules trigger confirmatory testing from screening flags without a manual re-order.
  • Multi-site queues in one tenant. Multiple collection sites, satellite labs, and the central lab share one LIMS IQ tenant with site-scoped queues, role-based access, and consolidated reporting. Specimens accessioned at one site can be transferred and tracked across locations, and surveillance data rolls up centrally for the program.

What to verify during a public health LIMS evaluation

Use a representative workflow in the demo and confirm how the system handles:

  • Multiple programs and sites: separate queues, permissions, test catalogs, and consolidated reporting without separate systems for every location.
  • Specimen traceability: barcode-driven intake, transfers between locations, chain of custody, and a complete history from receipt to release.
  • Configurable reporting: reportable-condition codes, receiver requirements, delivery schedules, interface monitoring, acknowledgment tracking, and correction or resend procedures.
  • Surge operations: peak daily volume, concurrent users, instrument queues, batch review, and backlog recovery using the lab’s own expected workloads.
  • Security and auditability: role-based access, protected data exchange, change history, and evidence that supports the lab’s validation and compliance process.
  • Implementation scope: interface testing, data migration, validation support, training, and ownership of future catalog or reporting changes.

Bring expected specimen volume, participating sites, instruments, submitting systems, reporting destinations, and required modules to the evaluation. Those inputs make product demonstrations and quotes easier to compare. See LIMS IQ pricing and configurations and the LIS buyer’s guide for the next step.

Sources

Frequently asked questions

12 answers on file
Q01

What is a public health LIMS?

A public health LIMS is a laboratory information management system built for laboratories that test for a population rather than for one ordering provider: state, county, and territorial public health labs, and the reference and hospital labs that report to them. It covers high-volume intake from many submitters, molecular, serology, microbiology, and chemistry workflows, electronic laboratory reporting (ELR) of reportable conditions to health agencies, surveillance reporting, and the multi-site logistics behind surge testing.
Q02

How does a public health LIMS detect which results are reportable?

The LIMS carries the reportable-conditions list for each jurisdiction it serves and evaluates every finalized result against that list. A rule matches on the test or organism, the result value or interpretation, and sometimes the patient's jurisdiction of residence: a positive culture for a notifiable organism, a quantitative value over a threshold (a childhood blood-lead level, for example), or a specific resistance marker. When a result matches, the LIMS flags it for electronic laboratory reporting automatically instead of relying on a technologist to recognize a reportable result and report it by hand.
Q03

How does a public health LIMS route ELR to the right agency when patients come from several jurisdictions?

Reportable results route by jurisdiction. The patient's residence determines which state or territorial health department receives the report, and the condition determines whether a federal program such as CDC NNDSS or the Laboratory Response Network also receives it. Reference and outreach labs receive specimens from patients across many states, each with its own reportable-conditions list, implementation guide, code requirements, and gateway, so the LIMS holds per-jurisdiction rule sets, endpoints, transport settings, and message templates, evaluates each result against the rules for the patient's jurisdiction, and sends to the matching gateway without manual sorting. Maintaining that logic in spreadsheets outside the LIMS does not scale and fails inspection.
Q04

What happens after an ELR message is sent, and how do labs monitor completeness and timeliness?

Transmission is not the end of the workflow. The receiving agency's gateway returns an HL7 acknowledgment: an application ACK confirming the message was accepted, or a NAK rejecting it for a coding, conformance, or content error. Rejected messages have to be corrected and resubmitted, and the lab is responsible for confirming delivery, not just sending. A defensible program tracks each reportable result through sent, acknowledged, and rejected states and monitors two things: completeness (every reportable result generated an acknowledged report) and timeliness (each report met its deadline). The LIMS supports this by flagging reportable results at verification, timestamping each transmission and acknowledgment, and surfacing any result that was flagged but not acknowledged so a coordinator can intervene before a deadline is missed.
Q05

Does LIMS IQ support state and federal reportable disease reporting?

Yes. LIMS IQ generates HL7 ELR (Electronic Laboratory Reporting) messages for reportable conditions and routes them to state and federal public health agencies. Reportable test definitions, condition codes (LOINC/SNOMED), and jurisdiction routing rules are configurable, reportable text is applied automatically through priority-based limit logic, and LOINC and CPT codes are maintained alongside each test and panel, so the lab does not keep reporting logic outside the LIS. The same finalized result can also go to the ordering clinician by HL7 ORU and to the patient portal from one approval action, with distribution rules defined per test.
Q06

How does LIMS IQ handle multi-site public health lab coordination?

Multiple collection sites, satellite labs, and a central reference lab can share one LIMS IQ tenant with site-scoped queues, role-based access, and consolidated reporting. Specimens accessioned at one site can be transferred and tracked across locations, with surveillance data rolled up centrally for the program.
Q07

How do public health labs run surveillance analytics and recurring program reporting in LIMS IQ?

LIMS IQ stores structured demographic, geographic, and result data that can be queried for surveillance views: case counts by organism, positivity trends, and turnaround time by site, with saved views so epidemiology and lab leadership can monitor outbreak signals without exporting to spreadsheets for every question. For recurring reporting, Report Runner supplies preconfigured templates with guided, typed filters; results export as CSV, Excel, tab-delimited text, or PDF; and administrators can schedule any template to deliver by email, SFTP, fax, HL7, or portal, with a do-not-send-when-empty option. Every run can be stamped with who ran it, their role, and the filter values, which is what makes a surveillance or grant report defensible after the fact.
Q08

How does LIMS IQ protect sensitive public health data?

LIMS IQ supports HIPAA-aligned controls including role-based access, full audit trails, encrypted transport, and least-privilege defaults for sensitive datasets. Access to reportable conditions, demographic identifiers, and surveillance exports can be scoped per user or per program.
Q09

Can submitting clinics, hospitals, and collection sites send orders into a LIMS IQ public health lab?

Yes, two ways. Submitters with an EHR send electronic orders (HL7 ORM) through the built-in HL7 engine, which connects with platforms like Epic, Cerner, Allscripts, and Practice Fusion, so orders and demographics land in the accessioning queue without re-keying; reference-lab connections to LabCorp and Quest are supported for send-outs. Submitters without an interface work in a branded client portal with paperless digital requisitions that guide them to the right tests and block incompatible selections, bulk ordering and re-orders by spreadsheet upload, and kiosk-mode check-in on a tablet at outreach and collection sites. The same portal gives them searchable, filterable results with cumulative trend views and 24/7 access.
Q10

Can LIMS IQ handle high-volume infectious disease and outbreak surge testing?

Yes. LIMS IQ is built for high-volume batch processing with bidirectional analyzer interfacing, so serology and molecular platforms load results automatically, and batch release lets techs sign off large runs of normal results in a single action. Configurable reflex rules trigger confirmatory testing from screening flags, and positivity rates and epidemiological trends surface through on-demand analytics: the throughput a public health lab needs during outbreak surges.
Q11

Can LIMS IQ track collection-kit inventory across public health collection sites?

Yes. Supply Monitor tracks kit and consumable stock at every site in real time with a green/amber/red health indicator, and draws stock down automatically as specimens arrive from that site. Reorder thresholds trigger low-stock emails to custodians, sites can request supplies themselves from the client portal, and Supply Orders carries each multi-line order from New through Completed with a packing list, shipment tracking, and a consolidated material ledger: the visibility a program needs before a surge, not after it runs out of swabs.
Q12

How quickly can a public health lab go live on LIMS IQ, and can legacy data come along?

Full-platform LIMS IQ onboarding is white-glove and phased from discovery through go-live; timing depends on the public health lab's sites, test menu, data migration, and integration scope. LIMS IQ supports legacy data migration, staff training, and 24/7 technical support. After launch, configurable catalogs, reportable condition codes, rules, and report layouts let teams add assays and reporting logic without waiting for vendor-developed code.
LIMS IQ See it in action NEXT STEP

Need a workflow built for your lab?

Public health LIMS software for state, county, and reference labs: ELR, reportable-condition rules, surveillance reporting, and multi-site surge testing.