The Salus community: publish once, adopt everywhere

Across a state, and across the country, public health labs run many of the same assays, report to the same standards, and answer the same inspections. Yet each one typically rebuilds its test definitions, result sets, coding, and report templates from scratch, and maintains them alone. That is enormous duplicated effort, and it is where inconsistency and coding errors creep in.

Salus treats lab content as shareable, versioned artifacts. A test definition, with its acceptable result set, reference ranges, and LOINC and SNOMED CT coding, an accessioning workflow, or a report template can be published as a bundle that another lab can install.

The model borrows from software package registries. A group, a reference laboratory, or an organization like APHL, can author a test once, code it correctly, and publish it. The rest of the community can then browse, install, and adopt that bundle, rather than reinventing it. Bundles are versioned, so an adopting lab knows exactly what it installed and can take an update deliberately.

Because the same mechanism carries test definitions, accessioning workflows, and report templates, a well-run lab's entire way of working, not just a single test, can become a starting point for the next lab, and a configuration proven in one site accelerates the second and third.

Public health lab software touches CLIA, CAP, and state certification, so content that is used clinically cannot be pulled in blindly. The community model is designed for a vetting and approval step before published content goes into clinical use, so a lab adopts on its own terms and its own timeline, with a human deciding what becomes part of its live configuration.

The result is the best of both worlds: the reach of shared, standardized content, and the control every regulated laboratory needs over what it actually runs.