0%
Hallucinations across the full scenario set
Strict prompts and yes/no TAQ format. Unsupported content has nowhere to go.
Approach
Agentic AI in hospital triage procedures
Triage guidelines are decision trees, not prose. A fluent model that invents a disposition is a patient-safety event. This article is how Vstorm treats that problem — proved out on Schmitt-Thompson Clinical Content, not on a stock hospital photo.
The production proof
The numbers on this page are STCC's. They stay STCC's.
We built this architecture for Schmitt-Thompson Clinical Content: HIPAA-aware agentic RAG, guidelines as the exclusive source of truth, no invented disposition. The test suite is 329 nurse-validated scenarios across 16 adult after-hours telehealth guidelines.
Zero hallucination events. 13 of 16 guidelines within five points of their expert benchmark. Scenarios below a 95% expert CRD gate were discarded — 95% is that panel gate, not the chatbot's score. Full engineering write-up: the STCC case study. This is not Medicare Advantage pre-appointment time and not Synera node-wiring.
329+
Nurse-validated scenarios
Sixteen adult after-hours telehealth guidelines. Below-gate scenarios never entered the score.
13 / 16
Guidelines within five points of benchmark
Two beat the expert bar. Three missed on deterministic matching, not hallucination.
About this article
This is a Vstorm approach piece, not a second STCC case study. It sits on the case-study route as an unlisted editorial. The production system it describes is Schmitt-Thompson Clinical Content — one of the most widely deployed clinical decision-support publishers in North America. Read the full build: zero-hallucination agentic RAG for clinical triage guidelines.
Our approach
What we build into a clinical AI system
- Guideline content stays the single source of truth — the model does not reason beyond it
- Every recommendation traces to a specific guideline and disposition, not a general inference
- The system reports when it cannot find a confident match, rather than a plausible-sounding answer
- HIPAA-aware data handling is in the architecture from the first Proof of Value
- Narrow agents and structured handoffs — not one model doing the whole tree at once
The problem
Why triage is a hard problem for AI
Clinical triage guidelines are rarely prose. They are decision trees: yes/no questions, ranked by urgency, each pointing to a disposition such as go to the emergency department now or safe to manage at home. A nurse or intake clinician works that logic under time pressure, often with incomplete information from the patient in front of them.
General-purpose language models are trained to interpret natural language, not branching conditionals and urgency tiers. Pointed at this content they can misread the logic and still answer with confidence. In most domains that is an annoyance. In triage, a confidently wrong disposition is a patient-safety incident, not a UX bug. The bar is not mostly right. It is traceable, and honest about its limits. A system that occasionally guesses is worse than one that says it does not know.
How we deliver it
Extract, retrieve the tree, refuse to invent
Proof of Value is a scored scenario set — not a fluent demo on a made-up patient.
Treat the guideline as the only source of truth
Map the tree: questions, urgency, dispositions. The model does not get to add medical knowledge from pretraining. Incomplete patient context is extracted first, not guessed later.
- Decision-tree inventory
- Urgency and disposition map
- HIPAA-aware data path
Proof of Value on nurse-validated scenarios
Retrieve against a structured, pre-indexed guideline, not raw PDF prose. Evaluate relevant branches in parallel. Report no-match instead of generating a disposition. Score against scenarios that already cleared the expert CRD gate.
- Structured retrieval
- Parallel branch eval
- Honest no-match
Harden the misses that are not hallucination
On STCC, remaining gaps were deterministic retrieval and matching — in active development — not invented content. Production follows TriStorm: a working Proof of Value, then hardening.
- Zero-hallucination bar
- Matching-gap backlog
- Production hardening
How it works
Narrow agents, structured handoffs, a tree that stays a tree
Patient context first. Retrieval against the indexed guideline. Branch evaluation. A disposition only when the tree supports it. The same isolation idea shows up in Vstorm's hybrid agent-graph work — specialists and typed handoffs — but those manufacturing SQL numbers stay on that page. Clinical proof stays on STCC.
Extract patient context What is known. What is not guessed.
↓
Retrieve the guideline tree Structured index — not raw prose
↓
Evaluate relevant branches In parallel, against the tree
↓
Disposition or no-match Never a fluent invention
Clinical triage agent — guidelines as exclusive source of truth
Results
Read the STCC breakdown for the engineering
Zero hallucination events on the published scenario set. Thirteen of sixteen guidelines within five points of the expert benchmark. Two exceeded it. Three fell short on matching, not on invented content. Full STCC engineering case study.
Work with us
Ready to see how agentic AI supports triage and clinical workflows?
Meet directly with our founders and PhD AI engineers. We will walk through real implementations from 30+ agentic projects and the practical steps to integrate them into your workflows.