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.
Who Salus Agentic is for
Decision support for qualified public health laboratories. JIL Sovereign Technologies, Inc. operates this host. SalusAgentic is its trade name.
Living regulatory intelligence for public health laboratories
CMS, OIG, CDC, APHL, state reportable rules, and court outcomes, written as operational notes. Salus records what changed. It does not certify the laboratory.
LOINC and SNOMED CT on the public health test card
The site already puts LOINC on the observation and SNOMED CT on coded results and organisms. This is how that coding is meant to travel, and what it does not prove.
Guardrailed agents for laboratory work
Conrad drafts, flags, and validates under a human gate. He does not release a result, transmit a message, submit a claim, or declare an outbreak.
Survey-ready attestation for a public health laboratory
Attestation here is an exportable, reviewable evidence package. It is not a certificate, not a clean-survey guarantee, and not a medical-device claim.
What Salus Agentic does not do
Decision support for qualified public health laboratories. Not a diagnosis, not a laboratory director, and not a JIL chain.
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.
How a public health LIMS interfaces with bioinformatics pipelines
Why running sequence assembly inside a LIMS fails, and how clean JSON metric ingestion preserves CLIA lineage and CDC reporting.
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 runs on Snowflake SPCS
Salus runs in Snowflake Snowpark Container Services. AI calls AWS through Amazon Bedrock. Snowflake and AWS each provide a Business Associate Agreement.
Salus architecture: Snowflake SPCS and AWS
Salus runs in Snowflake Snowpark Container Services. AI calls AWS through Amazon Bedrock. Snowflake and AWS each provide a Business Associate Agreement.
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 does and does not claim.
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 and outbreak signals
How the day's results become turnaround, backlog, and outbreak signals a director can read before a time-critical test hides in the queue.
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
A security persona watches access, contains a threat, and turns HIPAA safeguards into evidence a laboratory can show.
Billing, insurance, and reference labs for public health
Submitter invoices, purchase orders, insurance payers, and 837 claims for public health laboratories, without becoming a commercial billing product.
Accessioning that names the lab, the specimen, and the pick
How Salus registers specimens at public health volume: lab-qualified IDs, picks, imports, and holding times that start at collection.
The Salus feature map for PHL buyers and bench leads
How to read the Salus feature matrix: what matters to the bench, to directors, and to procurement.
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, veterinary isolates, and clinical specimens arrive at the same dock. Salus keeps them from becoming one worklist.
Outbreak detection with EWMA and CUSUM
Outbreak signals come from verified lab data and transparent EWMA and CUSUM models, reviewed by a human. An AI does not declare an outbreak.
Multi-tenant isolation: schema or database
How Salus keeps one laboratory's data out of another's reach on shared infrastructure, and why the isolation boundary differs by database engine.
Signed data exchange between public health labs
A receiving laboratory can trust a signed surveillance signal without trusting the sending laboratory's database.
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.