Eliminate Accessioning Bottlenecks and Accelerate Results | Salus Agentic
Product

Eliminate Accessioning Bottlenecks and Accelerate Results

Technologists spend less time on manual data entry and error recovery. Salus validates accessioning data at intake and keeps every specimen moving, from a single sample to a thousand-sample surge day.

Laboratory management is the spine of Salus. Every specimen is registered once and tracked from the loading dock through to a released, reportable result, with a complete event history behind it.

It is built for the realities of public health: surge days where thousands of specimens arrive at once, panels that change as new conditions emerge, and tests a lab needs to define itself rather than wait for a vendor to ship.

Salus, high-volume accessioning

What it does.

The full capability set, not a highlight reel.

Single and batch accessioning

Register one specimen at a guided form, or accession in batches with sensible defaults so a tech is not retyping shared fields.

High-volume / massive intake

Purpose-built for outbreak-scale days: import manifests, label sheets, and CSVs, and let the intake agent pre-fill the queue for one-click confirmation.

Specimen and result tracking

Every specimen carries its full lifecycle, received, aliquoted, in-testing, resulted, verified, reported, as an auditable event timeline.

Split-to-labs routing

Split a specimen into aliquots and route each to the department or partner lab that runs the test, without losing the parent record.

Lab-defined test builder

Create a new test with its acceptable result set, reference ranges, and interpretive logic, and assign LOINC to the observation and SNOMED CT to coded results and organisms.

Specimen rejection and recollection

Capture rejection reasons at the source and trigger recollection requests, so a bad specimen never quietly becomes a bad result.

Storage and location tracking

Track where every specimen and aliquot physically lives, with transfers logged, for retrieval, retention, and disposal.

In practice.

What it looks like on a real lab day.

An outbreak surge day

A respiratory panel batch of 96 arrives mid-morning. The intake agent extracts the manifest into the Suspense Queue; a tech reviews and confirms, and all 96 are accessioned in minutes instead of hours.

Standing up a new test

An emerging pathogen needs a new assay. A lab builds the test, its result set, and LOINC/SNOMED coding in the Test Builder, then runs it the same day, no vendor release required.

Cross-department routing

A specimen needs both serology and molecular work. Salus splits it into aliquots, routes each to the right bench, and keeps a single chain of custody for the parent.

Configuration.

What your lab controls, without a vendor in the loop.

  • Define tests, result sets, reference ranges, and interpretive rules in the Test Builder
  • Assign LOINC (tests/observations) and SNOMED CT (coded results/organisms)
  • Configure accession-number formats, label templates, and rejection reasons
  • Scope a test globally (available to every lab) or to a specific lab
Share it with the community

Build it once. Share it with every lab.

A test you build, its result set, reference ranges, and LOINC/SNOMED coding, is a shareable, versioned artifact. Publish it to a partner lab or to the Salus community so no one has to rebuild the same assay from scratch.

Test definitions with coded result setsReference ranges and interpretive rulesAccessioning workflows
How sharing and producer credits work

See it in your laboratory's context.

Explore the live demo, no login and no request form.