ETOR, ELR, and eCR: the PHL exchange triad
Why electronic orders, laboratory reporting, and case reporting must live together in a public health LIMS, and how Salus implements each with human gates.
Three feeds, one lab day
ETOR brings hospital and clinic orders in. ELR sends laboratory results out to the state and partners. eCR carries case-oriented reporting for reportable conditions. Treating them as three different vendor projects is how PHLs end up with brittle middleware and rekeying.
Salus treats exchange as a first-class layer: ORM/OML order intake with a mapping workbench, HL7 v2.5.1 and FHIR ELR with multi-destination release, and eICR generation with reportability determination plus dual-control approve before submit.
What lab techs experience
Mapped ETOR orders become accessions without retyping. Unmapped codes surface in the workbench. ELR and eCR leave through governed queues with ACK tracking. AI personas may validate coding; they do not send alone.
What buyers and APHL hear
APHL data modernization surveys put instrument interfacing and ETOR at the top of the stack. CDC public health data strategy milestones keep pressure on eCR via AIMS and ELR completeness. Salus positions those as product, not slides - and labels mapping quality honestly as certified versus best-effort where appropriate.
See the full matrix on the Features page, filtered to IT, APHL, CDC, or director, then walk ELR and ETOR in the live demo.
See it in your laboratory's context.
Explore the live demo, no login and no request form.