Public health laboratory modernization, explained.
Practical guides on migration, AI governance, cloud architecture, security, and interoperability, written for laboratory leaders, not vendors.
Start here.
A first set of articles. More are published as the platform grows.
CDC DMI, AIMS, and TEFCA for a public health laboratory
What data modernization actually requires of a PHL LIMS, and what Salus will and will not claim about TEFCA.
WHO IHR, genomics, and what a state PHL actually owes
H5, VHF, and other IHR-relevant detections have to be visible on the same record as the state ELR, or they get lost between systems.
The LDT landscape after ACLA v. FDA
What the 2025 vacatur actually changed for public health laboratories, and why validation discipline is now the whole advantage.
The 2026 CLIA RFI: AI, NGS, cyber, and emergency preparedness
CMS and CDC asked the field how CLIA should treat AI, sequencing, cybersecurity, and surge. Here is how a PHL should answer in practice.
LEIE and SAM screening for a public health laboratory
42 CFR 1001.1901 is not only a hospital rule. If federal program funds touch the work, exclusion screening is part of the quality system.
Migrating from a legacy LIMS: what actually changes
A realistic look at what moving off a legacy LIMS involves, what Salus maps for you, and what stays in your control.
How Salus's AI personas actually work
Conrad is the live Salus voice, with a scoped role and an autonomy level, and why a human always holds the kill switch.
Why Salus is built on Snowflake
Elastic scale, separation of compute and storage, and a multi-tenant foundation that runs a whole state network on one deployment.
Inside the Salus architecture: stateless app, Snowflake data plane, zero-trust
How Salus separates a stateless application layer from the Snowflake data plane and the AI layer, so protected health information stays governed and your security team can review the design end to end.
HIPAA, NIST, SOC 2, and HITRUST for laboratory systems
How Salus's security model aligns with the frameworks public health programs are actually held to, and what it inherits from Snowflake.
ELR, HL7, and FHIR: a practical implementation guide
What actually has to be configured to get a state feed live, and why onboarding a new jurisdiction doesn't mean a new build.
Turnaround time, outbreak signals, and the director's morning read
How real-time Snowflake-powered analytics turn a day's work into operational intelligence a director can act on before it becomes a backlog.
Zero lock-in: exporting and re-importing your lab's data
Your data is yours. How Salus lets a lab export everything, including the schema, and re-import clean records, so leaving is always an option you never have to use.
The Salus community: publish once, adopt everywhere
A package registry for public health lab content. How a reference lab can build a test once, code it to LOINC and SNOMED, and let every other lab adopt it.
Continuous compliance monitoring: how Salus watches for PHI risk
Compliance is not a binder you update once a year. How a security persona watches access in real time, contains a threat, and turns HIPAA safeguards into evidence you can show.
Billing, insurance, and reference labs for public health
How Salus handles submitter invoices, purchase orders, insurance payers, and 837 claims for PHL and public-health reference laboratories - without becoming a commercial RCM product.
Accessioning that names the lab, the specimen, and the pick
How Salus registers specimens at PHL volume: lab-qualified IDs, 4-digit picks, Excel/CSV/JSON import, human/animal/environmental domains, referral verification, and holding times that start at collection.
The Salus feature map for PHL buyers and bench leads
How to read the full Salus feature matrix: what matters to technologists, what matters to directors and procurement, and how free PHL access changes the RFQ conversation.
ETOR, ELR, and eCR: the PHL exchange triad
Why electronic orders, laboratory reporting, and case reporting must live together in a public health LIMS, and how Salus implements each with human gates.
Newborn screening at a public health laboratory
Why a state's newborn screening program needs its own workflow inside the LIMS, not a bolt-on spreadsheet, and what that looks like in practice.
Environmental and water testing at a public health laboratory
Wastewater surveillance, veterinary isolates, and clinical specimens arrive at the same dock. Here's how Salus keeps them from becoming one undifferentiated worklist.
Statistical outbreak detection: EWMA and CUSUM for laboratory data
The authoritative outbreak signal comes from verified lab data and transparent statistical models, reviewed by a human epidemiologist - not from a model declaring an outbreak on its own.
Multi-tenant data isolation: schema-per-tenant vs. database-per-tenant
How Salus keeps one laboratory's data out of another's reach on shared infrastructure, and why the isolation boundary differs by database engine.
Federation: signed data exchange between public health laboratories
When a surveillance signal crosses laboratory boundaries, the receiving lab needs to trust it without trusting the sending lab's database. Here's the cryptography that makes that possible.
What is a LIMS for public health? A buyer's glossary
Accessioning, ELR, chain of custody, LOINC/SNOMED coding: the terms a state or local health department hears during procurement, defined plainly.
Looking for pricing or the FAQ?
Resources covers program pricing, common questions, and what's coming next in the knowledge center.