Complete feature set

Everything a public-health laboratory needs, in one free platform

From specimen intake to the state ELR feed, from QC to court-admissible chain-of-custody, from one bench to a whole state's lab network. The software is free; you pay only for hosting and support. Salus runs on JIL Cloud with your data in Snowflake. Below is the complete feature set, with why each one matters, the benefit it delivers, how it differs, and how it compares to other LIMS.

Try the live demo Talk to us
Free software, you pay for hosting and support · Built on Snowflake · Agentic AI · Sealed evidence · HIPAA · HITRUST · SOC 2 · NIST · Operated by JIL Sovereign Technologies, Inc.
How Salus Agentic compares
Salus Agentic Legacy / homegrown state LIMS Commercial LIMS
Multi-tenant master-lab oversight ✓ ✗ ✗
Native PHL workflows (ELR, surveillance, NBS) ✓ Partial Partial
Self-service test builder (no vendor ticket) ✓ ✗ Partial
LOINC / SNOMED native ✓ Partial ✓
HL7 2.5.1 + FHIR R4 ✓ ✗ Partial
Sealed court-admissible chain-of-custody ✓ ✗ ✗
Post-quantum signatures ✓ ✗ ✗
Community content registry ✓ ✗ ✗
Federated inter-PHL sharing ✓ ✗ ✗
Agentic AI assistant ✓ ✗ Partial
Snowflake compliance inheritance (HIPAA/HITRUST/SOC2) ✓ ✗ Partial
Modern browser UI ✓ ✗ ✓
No software license fee ✓ Partial ✗
Certified-partner onboarding ✓ Partial ✓

From specimen to verified result

The lab bench workflow, modernized.

🧫 Accessioning & high-volume intake

Register specimens one-by-one or in massive batches, with submitter, source, priority, and order capture.
  • WhyIntake is the front door; a slow or error-prone front door bottlenecks the whole lab and corrupts every downstream record.
  • BenefitFast batch intake sized for 2-3M specimens a year, server-side filtered and paginated so lists stay instant at scale.
  • DifferentiatorBuilt for public-health volume out of the box, not a clinical LIMS retrofit; tests can be global or lab-specific from day one.
  • vs other LIMSLegacy and homegrown state systems bog down on bulk intake and rely on manual keying. Established commercial LIMS are tuned for clinical or commercial throughput, not the high-volume, submitter-heavy public-health intake Salus is sized for.

🧪 Lab-defined test builder

A lab creates a new test with its own result sets and reference ranges, each coded to LOINC (tests/observations) and SNOMED CT (coded results/organisms), with no vendor ticket.
  • WhyPublic-health labs constantly stand up new assays (a novel pathogen, a new panel). Waiting on a vendor to code a test costs weeks during an outbreak.
  • BenefitSelf-service test authoring with standards coding baked in, so results are interoperable from day one.
  • DifferentiatorMetadata-driven and standards-native; tests can be global or lab-specific, and shareable through the community registry.
  • vs other LIMSWith established commercial LIMS, standing up a new test usually means a configuration project or a vendor change order with a ticket and a lead time. Legacy and homegrown systems often require a developer to alter code. Salus lets the lab author and code the test itself, in the browser, with no ticket.

✅ Results entry & verification

Enter, review, and verify results through a controlled workflow, with preliminary, final, and corrected states.
  • WhyA result that leaves the lab wrong is a clinical and legal liability; verification is the lab's last line of defense.
  • BenefitTwo-step entry and verification, competency-aware, with a complete audit of who entered and who released.
  • DifferentiatorEvery result release is captured in the sealed chain-of-custody, so the record is tamper-evident and provable, not just logged.
  • vs other LIMSMost LIMS, commercial and legacy alike, record a verification audit trail in a database table that the operator's own administrators can edit. Salus binds each release into a cryptographically sealed chain, so the verification record is independently provable, not just internally logged.

🔬 Microbiology & molecular

Organism identification, susceptibility, and molecular workflows with SNOMED-coded organisms and results.
  • WhyPublic-health labs are micro-heavy (TB, enterics, STIs, respiratory panels); generic LIMS handle micro poorly.
  • BenefitMicro-aware result capture and coding that maps cleanly to the ELR feed and surveillance.
  • DifferentiatorMicro is a first-class module, not an afterthought bolted onto a chemistry LIMS.
  • vs other LIMSMany chemistry-first commercial LIMS treat microbiology as an add-on with limited organism and susceptibility modeling. Salus models organism identification, susceptibility, and molecular results natively and SNOMED-codes them so they flow straight to ELR and surveillance.

🧰 Instruments, QC & reagents

Instrument interfacing, quality-control runs, and reagent/lot tracking tied to results.
  • WhyA result is only as trustworthy as the instrument, the QC behind it, and the reagent lot used.
  • BenefitQC and reagent lots are linked to the results they govern, so a QC failure or a recalled lot is traceable to every affected specimen.
  • DifferentiatorLot-to-result traceability that makes a recall a query, not a fire drill.
  • vs other LIMSEstablished commercial LIMS support QC and lot tracking, but often as separately licensed modules that must be integrated. In legacy and homegrown systems, reagent lots frequently live in a spreadsheet disconnected from results. Salus ties lots and QC to the results they govern by default.

📋 Proficiency testing, worksheets & rules

PT sample handling, specimen rejection logic, bench worksheets, and a configurable rules engine.
  • WhyCLIA proficiency testing and defensible rejection rules are mandatory; doing them by hand is error-prone.
  • BenefitPT, rejection criteria, and worksheets are built in and configurable per lab.
  • DifferentiatorA rules engine the lab configures itself, instead of hard-coded logic only a vendor can change.
  • vs other LIMSIn legacy state systems, rejection and PT logic is usually hard-coded and only the original vendor or developer can change it. Commercial LIMS expose rules, but typically through a vendor-led configuration engagement. Salus puts a self-service rules engine in the lab's own hands.

📦 Specimen storage & location

Track where every specimen physically lives, through aliquoting, freezing, retrieval, and disposal.
  • WhyRetrieving the right vial months later (for confirmation, an audit, or a legal request) depends on knowing exactly where it is.
  • BenefitFull physical-location tracking, with every move recorded in the sealed custody chain.
  • DifferentiatorStorage moves are part of the same tamper-evident custody record as testing, not a separate spreadsheet.
  • vs other LIMSWhere commercial LIMS offer storage tracking, the move history is an ordinary editable log. Legacy systems often track freezer location in a side spreadsheet entirely. Salus records every storage move into the same sealed custody chain as testing, so retrieval and disposal are provable.

Reporting, ELR & public-health surveillance

Where a public-health lab earns its name.

📡 ELR / HL7 v2.5.1 + FHIR R4

Electronic Lab Reporting to the state, with HL7 ORU^R01 (LOINC to OBX-3, SNOMED to OBX-5, CLIA as the universal id) and a parallel FHIR R4 representation.
  • WhyELR is the legal reason a public-health lab exists: reportable results must reach the state, correctly coded and on time.
  • BenefitStandards-correct ELR generation, parameterized per jurisdiction, ready for the state feed without custom glue.
  • DifferentiatorModern HL7 2.5.1 plus FHIR R4 in parallel, both first-class, not an export bolted on later.
  • vs other LIMSMany legacy state systems are frozen at HL7 2.3 with custom Z-segments no one wants to maintain, and few emit FHIR R4 at all. Commercial LIMS support modern HL7, but FHIR R4 is frequently an extra-cost interface engine. Salus generates standards-correct HL7 2.5.1 and FHIR R4 in parallel, parameterized per jurisdiction.

📑 Report generation

Final, corrected, preliminary, and reprint reports; case reports; QC and turnaround-time reports; configurable templates and letterhead.
  • WhyReports are the lab's product; corrections and reprints must be handled cleanly and auditably.
  • BenefitEvery report kind is built in, with org branding and templates the lab controls.
  • DifferentiatorReport templates are shareable community content, so a good template spreads across labs.
  • vs other LIMSCommercial LIMS report designers are powerful but lock templates inside one customer's instance, and legacy systems often need a vendor to change a report layout. Salus lets the lab control its own templates and publish good ones to the community registry for other labs to adopt.

🛰️ Surveillance & NEDSS

Flag reportable conditions, open and track surveillance cases by jurisdiction, and feed public-health surveillance (NEDSS/NMI).
  • WhyDetecting and reporting notifiable conditions fast is the core of outbreak response.
  • BenefitReportable-condition logic and case tracking are built in and jurisdiction-aware.
  • DifferentiatorSealed, verifiable surveillance records can be shared across jurisdictions without a bilateral-trust bottleneck.
  • vs other LIMSMost LIMS, commercial and legacy, stop at the lab boundary and leave surveillance to a separate downstream system. Salus treats reportable-condition logic and jurisdiction-aware case tracking as built-in, and its sealed records can cross jurisdictions without a bilateral-trust bottleneck.

👶 Newborn screening (NBS)

Newborn screening panels, disorders, and screen results as a first-class module.
  • WhyNBS is time-critical and high-stakes; a missed or delayed result has lifelong consequences.
  • BenefitPurpose-built NBS handling rather than a generic test shoehorned into a chemistry workflow.
  • DifferentiatorFew LIMS treat NBS natively; Salus does.
  • vs other LIMSNewborn screening is so specialized that many states run a separate dedicated NBS application alongside their LIMS, and most commercial LIMS do not cover it. Salus includes NBS panels, disorders, and screen results as a first-class module inside the same platform.

✍️ E-signatures (21 CFR Part 11-style)

Cryptographically bound, attributable electronic signatures on the records that require them.
  • WhyRegulated records need attributable, non-repudiable sign-off.
  • BenefitPart 11-style e-signatures integrated into the workflow.
  • DifferentiatorSignatures fold into the same sealed evidence layer as the rest of the record.
  • vs other LIMSCommercial LIMS offer Part 11 e-signatures, but typically backed by an internal database flag rather than an independently verifiable signature. Salus binds signatures with hybrid Ed25519 plus post-quantum signatures into the same sealed evidence layer as the rest of the record.

💵 Billing & claims

Capture billable activity and produce claims alongside the lab workflow.
  • WhyEven public-health labs bill (Medicaid, insurers, interagency); disconnected billing leaks revenue.
  • BenefitBilling tied to the work performed, in one system.
  • DifferentiatorNo separate billing silo to reconcile against the LIMS.
  • vs other LIMSPublic-health labs running legacy systems usually bolt on a separate billing package and reconcile it by hand. Commercial LIMS often sell billing as a distinct module or integration. Salus captures billable activity beside the work performed, in one system.

Run a lab, or oversee an entire state's labs

Multi-tenant by design.

🏛️ Multi-tenant & master-lab oversight

Every record is tenant-scoped. A state public-health lab can run as a master tenant overseeing county and community labs, with roll-up KPIs, certifications, QC, and surveillance across all of them.
  • WhyA state health department oversees many labs; today that means many disconnected systems and no single view.
  • BenefitOne platform for the whole state system: tight hierarchical oversight, or autonomous labs that still federate.
  • DifferentiatorPHLs are the underserved step-children of health IT; almost no incumbent offers multi-tenant lab oversight at all. Salus is multi-tenant from the first table.
  • vs other LIMSLegacy state systems are single-tenant, so a state overseeing county labs ends up with many disconnected installs and no roll-up view. Commercial LIMS are typically licensed per instance and not built for a master lab to oversee subordinate labs. Salus is multi-tenant from the first table, with roll-up across the whole hierarchy.

🔀 Labs, departments & split-to-labs routing

Model labs and departments, and route or split a specimen to the lab that performs the test.
  • WhyA specimen often needs testing the receiving lab does not perform; it has to go somewhere that does.
  • BenefitBuilt-in routing so a community lab can accession and send to a central PHL for testing or confirmation.
  • DifferentiatorReferral is native, and (with sealed custody) portable across organizations, not a fax and a prayer.
  • vs other LIMSIn legacy systems, sending a specimen to another lab usually means a fax, a re-keyed order, and a manifest by hand. Commercial LIMS can route within one instance, but cross-organization referral is a custom integration. Salus makes referral native and, with sealed custody, portable across organizations.

👩‍🔬 Staff, certifications, competency & schedules

Tester roster and KPIs, a certifications repository with an expiry watchlist and test-competency requirements, and weekly work schedules.
  • WhyCLIA requires demonstrated competency; an expired certification on a released result is a finding.
  • BenefitCompetency and certification tracked against the tests each person may run, with expiry alerts.
  • DifferentiatorCompetency can gate result entry, turning a compliance burden into an automatic control.
  • vs other LIMSMost labs track certifications and competency in a spreadsheet or an HR system disconnected from the LIMS, and few commercial LIMS gate result entry on competency. Salus tracks certification expiry against the tests each person may run and can gate result entry automatically.

🔐 RBAC, real auth & KPIs

Password login to signed JWTs, lab-scoped roles and permissions enforced on every mutating endpoint, and per-lab KPI dashboards and analytics.
  • WhyLab data is sensitive and regulated; access must be real, scoped, and auditable.
  • BenefitEnforcing RBAC on the server (not just hidden in the UI) plus a self-service admin for roles and permissions.
  • DifferentiatorSecurity is enforced at the API, lab-scoped, with analytics that roll up across the network.
  • vs other LIMSOlder systems often enforce access only by hiding menu items in the UI, which a determined user can route around. Salus enforces lab-scoped roles and permissions on every mutating endpoint at the API, with analytics that roll up across the network.

🧩 Workflow engine, saved views, branding & support

Configurable workflows, saved/filtered views, per-org branding and letterhead, and in-app support ticketing.
  • WhyEvery lab works a little differently; rigid software forces bad process or shadow spreadsheets.
  • BenefitThe lab configures its own workflows and views, brands its output, and gets help in-app.
  • DifferentiatorConfigurability the lab owns, instead of a change order to a vendor.
  • vs other LIMSCommercial LIMS are highly configurable, but that configuration is usually delivered through a vendor services engagement and a change order. Legacy systems are rigid, pushing labs into shadow spreadsheets. Salus puts workflow, saved views, branding, and in-app support in the lab's own hands.

What makes Salus best-of-breed

The capabilities no legacy or commercial PHL LIMS has.

📚 Community content registry

Labs publish shareable, versioned, LOINC/SNOMED-coded artifacts (test definitions, accessioning workflows, report templates) that the rest of the community can adopt. A package registry for public-health lab content, with community governance.
  • WhyEvery state re-builds the same tests in isolation; the field has no shared content supply chain.
  • BenefitAdopt a vetted test definition or report template in minutes instead of authoring it from scratch.
  • DifferentiatorA network effect no single-tenant legacy system can offer: the more labs join, the better the shared content gets.
  • vs other LIMSNo legacy state system or commercial LIMS offers a cross-customer content registry; each customer rebuilds the same tests in isolation, since vendors have no incentive to let configuration flow between accounts. Salus runs an open, versioned, community-governed registry of test definitions, workflows, and report templates.

⛓️ Sealed, court-admissible chain-of-custody

Every custody event is hash-chained and then sealed with a hybrid Ed25519 plus post-quantum ML-DSA-65 signature, so a specimen's history is tamper-evident, independently verifiable, and durable past the post-quantum transition.
  • WhyForensic, legal, and outbreak specimens are evidence; logging it in a database is not the same as proving anyone can confirm it was not altered.
  • BenefitA custody chain a court, an auditor, or another agency can verify against the records it was given.
  • DifferentiatorNo other PHL LIMS produces cryptographically sealed, post-quantum, independently-verifiable custody.
  • vs other LIMSEvery other LIMS records chain-of-custody as an audit-log table inside the operator's own database, which the operator's administrators can in principle alter. Salus seals each event with a hash chain and hybrid Ed25519 plus post-quantum ML-DSA-65 signature, so the history is tamper-evident and independently verifiable by a court or another agency.

🌐 Federated inter-PHL network

Refer specimens, return results, and share surveillance across organizations, with portable sealed custody as the handoff envelope. A receiving lab verifies what it was sent without trusting, or touching, the sender's database.
  • WhyOutbreaks cross county and state lines, but labs do not share, because of trust and liability, not just technology.
  • BenefitCounty-to-state confirmation, state-to-reference escalation, and cross-jurisdiction surveillance that just works.
  • DifferentiatorNeutral, sealed evidence is the trust substrate: sharing becomes a verification problem, not a data-custody problem. This is the moat.
  • vs other LIMSNo legacy or commercial LIMS offers neutral, cross-organization sharing; today inter-lab exchange is point-to-point integration plus a legal data-sharing agreement. Salus uses portable sealed custody as the handoff envelope, so a receiving lab verifies what it was sent without touching the sender's database.

✨ Agentic AI assistant

An autonomous assistant watches recent lab activity for outbreak signals, QC and turnaround-time risk, and drafts routine work, with a defensible, sealed audit trail of everything it did or proposed. A human approves anything that leaves the lab.
  • WhyPublic-health labs are understaffed; the signal in the data is often missed for lack of hands.
  • BenefitThe agent surfaces what matters and drafts the busywork, while a human stays in control.
  • DifferentiatorAgentic plus sealed: every agent action is attested and tamper-evident, so AI is trustworthy in a regulated setting.
  • vs other LIMSLegacy state systems have no AI at all, and commercial LIMS are only beginning to add assistants, typically without a sealed record of what the AI did. Salus pairs an autonomous assistant with a sealed, attested audit trail of every action it took or proposed, so AI is defensible in a regulated setting.

❄️ Snowflake-native, dialect-agnostic

Runs on Postgres or, at deploy time, on the customer's own Snowflake (Unistore hybrid tables), processing data where it already lives.
  • WhyPublic-health data is sensitive and residency-constrained; moving it into a vendor cloud is a deal-breaker.
  • BenefitDeploy in the customer's tenant and inherit its HIPAA, HITRUST, SOC 2, and NIST posture.
  • DifferentiatorCompliance and residency by inheritance, not by promise.
  • vs other LIMSCommercial cloud LIMS host your PHI in the vendor's own tenant and ask you to trust their certifications. Legacy systems run on aging on-premise servers the lab must secure itself. Salus deploys into the customer's own Snowflake and inherits its HIPAA, HITRUST, SOC 2, and NIST posture, so compliance and residency are by inheritance, not by promise.

🕊️ Free to use

The software is free to use. You pay only for setup, migration, hosting, and support, delivered by verified, trained integration partners. Operated by JIL Sovereign Technologies, Inc. SalusAgentic is a trade name of that company. JIL Sovereign Holdings, LLC (WY) owns the SalusAgentic software. Global Hands, Inc. (TX) gave a grant to JIL Sovereign Holdings, LLC (WY) to build salusagentic.com under its public good initiative. The cost to build SalusAgentic was greater than what Global Hands paid. Global Hands may benefit from the software because it gave Holdings that money. JIL Sovereign Technologies, Inc. (DE) operates and supports salusagentic.com. JIL Sovereign Technologies, Inc. (DE) operates most, if not all, of the software JIL Sovereign Holdings, LLC (WY) owns. Global Hands, Inc. does not operate this site.
  • WhyThere is little commercial margin in a few hundred government labs, so no vendor serves them well. That is exactly why they are underserved.
  • BenefitBest-of-breed software with no license fee, and a certified partner network to onboard, migrate, and support.
  • DifferentiatorA public-good network: free software plus a sealed trust layer plus a partner ecosystem is a thing no closed commercial vendor will build.
  • vs other LIMSEstablished commercial LIMS all carry substantial software license and annual maintenance fees, and legacy and homegrown systems carry costly custom-maintenance contracts. Salus charges no software license fee; you pay only for hosting and support, delivered through a certified partner network.

See it on real public-health workflows

The fastest way to judge it is to use it.

Try the live demo Talk to us