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.

Salus, high-volume accessioning

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, human and animal and environmental programs on one worklist, panels that change as new conditions emerge, and tests a lab needs to define itself rather than wait for a vendor to ship.

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.

Excel, CSV, and JSON import

Upload a submitter spreadsheet or file, map columns, preview validation, then commit through the same accession writer as a walk-in. Legacy .xls is rejected; save as .xlsx.

High-volume / massive intake

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

Lab-qualified accession IDs

Every printed number names the origin lab, then a 10-digit specimen (year plus sequence), then a 4-digit pick: FLAG.2026000001-0001. Federation lineage is on the label.

4-digit pick numbering

Each ordered test is a pick on the parent accession. Pick 0001 through 9999 is never reused after cancel, so reprints and barcodes stay honest.

Human, animal, and environmental domains

Accession clinical, veterinary, and environmental specimens on the same platform, with matrix codes and animal fields when they apply.

Referral verification gate

Inbound referrals land pending a 10-check physical review. A scan does not receive the specimen; a tech passes, rejects, or accepts with a written exception.

Holding times from collection

Rules by domain, matrix, and test clock max hours from collection and flag picks as ok, at-risk, or expired before the run starts.

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 picks and 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 as an Excel manifest. The file is mapped and previewed, a tech confirms, and all 96 are accessioned in minutes instead of hours, each with a lab-qualified ID and pick 0001.

A referred confirmation

A county lab sends an isolate to the state PHL. The specimen lands pending verification. The receiving tech walks identity, label, integrity, volume, and transport checks, then receives it. A QR scan never skips that gate.

Environmental and veterinary work on the same dock

A wastewater grab and a veterinary isolate arrive with the morning clinical swabs. Each is accessioned in its domain, with matrix and holding-time rules applied from collection, not from receipt.

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 picks, 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)
  • Set each lab's unique ID and accession-number parameters (year width, sequence padding, lab separator)
  • Configure pick labels, label templates, and rejection reasons
  • Define holding-time rules by specimen domain, matrix, and test
  • 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.