The Salus feature map for PHL buyers and bench leads

Public health laboratory software is bought by leadership and lived in by technologists. The Salus features page is built for both. Every row states what the capability does, why a bench operator cares, why a buyer or director cares, and which audiences it serves - from APHL and CDC to clinic submitters and CLIA surveyors.

That dual voice matters because RFQs often mix workforce relief, interoperability, and free-or-low-cost licensing. A feature list that only markets to CIOs loses the tech; a list that only describes screens loses the funder. The matrix holds both columns side by side.

For technologists: scan-first accessioning, Excel/CSV/JSON import with preview, 4-digit picks, holding times from collection, exception-oriented results, QC that is not a side spreadsheet, instrument health that answers is the analyzer talking, and AI that drafts into human queues instead of releasing alone.

For directors and buyers: ETOR and ELR excellence, eCR with dual control, command center and priority inbox, CLIA/CAP inspection binder, multi-tenant network posture, sealed federation, and a license model with no per-user or per-module tax.

The matrix marks shipped capabilities you can exercise in the live demo, and a short honest roadmap set (deeper statewide roll-up, PHL capability directory, AMR/wastewater/genomic program modules). Modernization conversations go better when the product does not overclaim.

Open /features, filter by audience, and jump from any row into product detail or Learn articles. Then prove the same path in app.salusagentic.com/Demo with demo / demo.