Who Salus Agentic is for

A public health laboratory is in a software conversation, and the deck in the room was written for a hospital or a commercial clinical laboratory. The questions that still matter are ordinary ones. Who accessions a surge morning. Who can show competency for the tests those people actually perform. Who transmits electronic laboratory reporting, and who is not allowed to send it for them.

The director is still the director. The quality manager still needs the packet out of a single inbox. The bench still needs the specimen registered before a result exists. In the same meeting, a vendor or an assistant is being asked to sit in one of those chairs. JIL Sovereign Technologies, Inc. operates this host and offers the software. It does not take the laboratory's certificate. 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 salusagentic.com. Holdings owns the rights, maintains the code, provides Level 1 support, and does not operate the code. Global Hands, Inc. does not operate this site.

Those are the signs.

Salus Agentic is a laboratory information system for public health. JIL Sovereign Technologies, Inc. operates salusagentic.com. salusagentic.com is part of JIL Sovereign Technologies, Inc., a Delaware corporation. 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 salusagentic.com. Holdings owns the rights, maintains the code, provides Level 1 support, and does not operate the code. Global Hands, Inc. does not operate this site. The laboratory that accessions the specimen, runs the method, and signs the report remains the laboratory. The operator does not sit in that chair.

Qualified, on this site, means a public health laboratory or a laboratory inside a public health network: a state public health laboratory, a regional or county laboratory, an environmental or water laboratory, a newborn screening laboratory, a specialized testing facility, or a satellite of that network. Reference laboratories appear when they are part of that public health work, not as a general commercial outreach list. The site does not publish a customer count, and this article will not invent one.

If your organization bills itself as a clinical laboratory for individual patient care and does not carry a public health reporting duty, this product is the wrong fit. The workflows assume reportable conditions, electronic laboratory reporting, proficiency and competency files, and a director who can explain the menu to a surveyor. Those are public health problems. They are not the same as a physician-office order entry system.

The about page names the roles on purpose. A laboratory director needs a menu that shows which assays are grant-aligned, which are laboratory-developed, and which must stay live for readiness even when a fee schedule is hostile. A quality manager needs validation packets, SOP versions, competency tied to the tests a person actually performs, and an exclusion-screening log that is not trapped in a private inbox. A bench lead needs accessioning that survives a surge morning, holding times counted from collection, and a referral that cannot be received by a barcode scan alone.

State leadership and compliance officers use the same record from the other direction. They need to see what left the building as ELR, what an agent was allowed to draft, and what a human accepted. Program staff who deliver technical assistance use the same platform. They are not a second laboratory. The platform page says this directly: capacity support, not a competing laboratory.

Conrad, the single in-product voice, is not a member of that staff list. He drafts and flags. The people above remain the users. A technologist confirms an accession. A supervisor reviews a quality-control flag. A director, or the director's designee, signs a validation summary. The software records those acts. It does not appoint itself to any of those jobs.

The laboratory management module is the spine. A specimen is registered once, as a human, animal, or environmental domain, and tracked from receipt through result, verification, and report. High-volume intake accepts a mapped spreadsheet or file, previews validation, and commits through the same writer as a walk-in. Legacy binary spreadsheets are rejected. A referred isolate stays pending until a person walks the physical checks. Holding-time rules clock from collection, not from whenever the box was opened.

Tests are laboratory-defined. The Test Builder holds the acceptable result set, reference ranges, and the codes the message will carry. A test can be available to every laboratory in the deployment or scoped to one laboratory. Community bundles exist so a second laboratory can install a versioned definition instead of retyping it. That is a sharing model for public health content. It is not a claim that any particular bundle has been adopted by a named state.

Reporting is part of the same record. HL7 v2 and FHIR electronic laboratory reporting, LOINC on the observation, and SNOMED CT on coded results and organisms are product behavior the interoperability pages describe. A human transmits. The system can validate a message before that person sends it. Validation is not the send.

The Public Health Access Program publishes a shape, not a roster. The software license is $0 for qualified public health laboratories. There is no setup fee and no per-user fee, and the site says there are no editions that strip features by contribution level. Hosting starts at $15,000 per year and is reassessed against actual volume and cloud cost. Maintenance and support is $12,500 per lab per year. The pricing page says most laboratories start at $27,500 per year. A laboratory may bring its own Snowflake account. Maintenance still applies, and Salus support does not replace that laboratory's Snowflake contract.

Those figures are the published program. They are not a quote for your procurement, and they are not evidence that a federal cooperative agreement will pay them. The grants page is explicit that its examples are illustrative. A director still takes the line items to the agency's own purchasing rules. Thresholds vary. This site does not know yours.

Nothing in the access program is a promise of a clean survey, a connected electronic health network, or a particular turnaround time. The product is the system of record and the evidence around it. The laboratory's certificate, people, and methods remain the laboratory's.

It is not for a patient looking up a personal result. It is not a diagnostic device a clinician orders in place of a laboratory. It is not a substitute for the association toolkits a public health laboratory already uses. It is not a blockchain or a token network. JIL Sovereign Holdings, LLC does not operate this site. 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 salusagentic.com. Holdings owns the rights, maintains the code, provides Level 1 support, and does not operate the code. Global Hands, Inc. does not operate this site. JIL Sovereign Technologies, Inc. operates this host and does not own the software. This page's product is the public-health laboratory.

It is also not for a team that wants an agent to release results overnight. The non-clinical boundary is part of the product definition. If a procurement requires unsupervised auto-verification, automatic claim submission, or a vendor stamp that says the laboratory is compliant, Salus will not say yes. Decision support only. Local CLIA certification, state law, and medical director judgment control testing and reporting.

If you are a qualified public health laboratory and the fit is still unclear, start with the platform page, the pathogen library, and the regulatory change log. Those three surfaces show the work the product will and will not take on. Then use the contact path. Eligibility is a conversation with the operator, not a box this article can check for you.