Put Extra Hands on Your Team, Not New Risks
Allyson reviews entered results, drafts the verification, and waits. Conrad watches QC. Neither releases a result alone.
Salus is AI-native, and a person stays in charge. Allyson is the agent on the bench. She challenges entered results and drafts a verification. She does not sign it.
Conrad remains the QC colleague. The floating bar on every screen is Allyson, so a director or a technologist can ask her from the queue they are in.
What it does.
The full capability set, not a highlight reel.
Drafts the routine work
Accessioning from manifests, operational reports, and verifications are drafted for a person to approve in one click, never auto-committed.
Flags what needs a human
Out-of-range results, presumptive positives, QC drift, and turnaround-time risk are surfaced first, so attention goes where it matters.
Assists ELR and coding
Validates HL7 and FHIR messages and LOINC/SNOMED coding before anything reaches the state feed.
Watches for signals
Monitors test patterns for anomalies and possible outbreak signals, and drafts alerts for epidemiologist review.
The assistant bar
The bar on every screen is Allyson. Ask her to review the unverified queue. She proposes the run, and a person confirms it.
Meet the personas.
Named workers across the lab and finance desk, each with an autonomy level, and a human in control.
Challenges entered results. Flags reference, delta, and critical anomalies. Drafts the verification. A person signs the release. She does not declare an outbreak.
Evaluates Westgard and out-of-spec QC and drafts CAP/CLIA notes. A person still owns the quality record.
The full architecture.
For your technical reviewers: the complete AI agent ecosystem, the human-in-the-loop pipeline, and the governance model behind it.
What it demonstrates
Why this reassures a cautious reviewer.
- Allyson challenges results and drafts the verification. A person signs the release
- A human-in-the-loop pipeline: every AI action is drafted for a person to approve
- A governance layer with bias, performance, and audit monitoring built in
- Explainability by design, so every recommendation carries its rationale
Who is in control.
- Each persona has an autonomy level: Suggest, Acts with approval, or Autonomous in scope.
- A human admin can pause or disable Allyson or Conrad from the AI Personas screen.
- Disabling a persona is a human-only action. The kill switch always stays in a person's hands.
- Every status, autonomy, and scope change is written to an append-only control log: who changed what, and when.
- Personas hold scoped permissions that mirror staff roles, so a persona can never do something its human counterpart could not.
Configuration.
What your lab controls, without a vendor in the loop.
- Set each persona Active, Paused, or Disabled from the AI Personas screen
- Choose an autonomy level per persona (Suggest / Acts with approval / Autonomous in scope)
- Grant or revoke a persona's permission scope, lab by lab
- Review the full control history for any persona
See it in your laboratory's context.
Explore the live demo, no login and no request form.