Stop Losing Days to State Feed Rejections
Standards-compliant HL7 and FHIR messaging, with LOINC and SNOMED coding validated before transmission, so reports reach the state feed clean the first time.
A public health lab is only as useful as its ability to report. Salus generates standards-compliant electronic lab reporting to the state and exchanges data cleanly with the systems your programs already depend on.
The identifiers and facility details that every jurisdiction wants slightly differently are configuration, not code, so onboarding a new feed does not mean a new build.
Salus works with the commercial LIMS a laboratory already runs. Orders and results move through the HL7 interfaces that system already uses, including StarLIMS, LabWare, and Horizon. A product name is not a certified connector. The laboratory's interface engine posts the message, Salus maps the test codes, and the electronic laboratory report goes out in the form the state already accepts.
What it does.
The full capability set, not a highlight reel.
HL7 v2 ELR
Generate ORU^R01 electronic lab reporting for the state feed, with a custom ZLR segment and CLIA as the universal identifier.
FHIR
Exchange data over HL7 FHIR alongside v2, for partners and programs that have moved to it.
LOINC and SNOMED coding
LOINC mapped to the observation (OBX-3) and SNOMED CT to the coded result (OBX-5), validated before transmission.
Configurable identifiers
MSH, FHS, and BHS facility identifiers, CLIA, and OBX-15 live in configuration and are edited on a Settings screen, not in code.
ELR destinations and export queue
Manage multiple destinations and watch the export queue, so you can see exactly what is staged, sent, and acknowledged.
Instrument interfaces
Connect analyzers through standardized instrument interfaces so results flow into the same verification workflow.
Commercial LIMS interfaces
StarLIMS, LabWare, and Horizon can send orders through the HL7 interfaces they already use. A product name is not a certified connector. The interface engine posts the message and Salus maps the test codes.
In practice.
What it looks like on a real lab day.
A new jurisdiction needs its own MSH and facility identifiers. They are set on the Settings screen and the feed is live, no rebuild.
Conrad validates coding before transmission, so problems are caught in the lab, not in the state's reject report.
An instrument posts results over a standardized interface; they land in the results workflow for verification like any other.
The existing system keeps sending HL7. Salus maps the codes and sends the electronic laboratory report in the form the state already accepts. There is no separate certified connector to buy.
Configuration.
What your lab controls, without a vendor in the loop.
- Set ELR identifiers (MSH-3/4/5/6/11/12, FHS/BHS facility, CLIA, OBX-15) and letterhead in app configuration
- Manage ELR destinations and the export queue
- Configure instrument interfaces
See it in your laboratory's context.
Explore the live demo, no login and no request form.