Ambient triage
AI-assisted operator guidance, governed by clinical safety.
Ambient triage listens for clinically relevant cues while the conversation happens, keeps only reviewed structured signals, and surfaces the next safe question or action for an operator. It is decision support, not diagnosis.
Safety first
Deterministic red-flag rules run before AI output and cannot be downgraded by the model.
Governed and auditable
Every turn, tool call, nudge, and disposition state is designed to be logged for review.
Private by design
The integration summary is PHI-minimised and exposes structured cues, not raw conversation text.
Demo video
Simulated operator console and MCP activity
Pretend host environment
CRM/EHR host surfaceSynthetic partner workspace showing how the assistant can sit over contact-centre and EHR surfaces.
Composite CRM/EHR host surface with an overlay widget.
Genesys-style call workspace
Genesys CRM shell
Epic-style ED track board
Epic triage board context
high-risk chest pain intake
shortness of breath concern term
central chest pain complaint summary
Assistant behaviours in the host surface
Active operator question
Next safe action
Clinician pickup context
Synthetic 000-style call
Browser speech synthesis. No real patient audio.
Triple Zero, ambulance. Tell me exactly what has happened.
It's my dad. He's fifty-eight. His chest feels tight in the middle and he's getting short of breath.
Ambient cue stream
Live clinical cues, simulated
Next best question
Operator-facing, not patient-released
Start with immediate risk and breathing questions.
Ambient triage listens for clinically relevant cues and turns them into reviewed, structured signals for the operator.
Deterministic safety floor
Red-flag checks, escalation policy, and disposition floor remain active.
Integration activity
ambient-copilot-turn ready
SNOMED CT-AU mapping checked
Review-safe event prepared
Demo reel cue sheet
Recording-safe chapter data for partners who need to embed or recreate the walkthrough.
Comms intake agent
Initial interaction agent for demographics, DOB, address, contact details, and the first complaint. It creates a clinician pickup file and applies deterministic concern-word routing before triage continues.
Safety routing
Concern terms prioritise the queue before clinician handoff.
Priority clinician pickup: high-risk concern terms detected during intake.
- Keep the caller connected while triage continues.
- Surface the chest pain structured assessment for the receiving clinician.
- Send the PHI-minimised patient file to the operator console.
If emergency terms such as not breathing or unconscious are detected, the route changes to 000 escalation. This does not release patient advice or replace clinician triage.
Community triage service profiles
The same governed signal can be rendered into community telephone triage workflows as structured decision support, with local clinical rules and patient advice release kept outside the ambient listening layer.
Healthdirect Australia
National nurse-led telephone triage queue with escalation back to 000 when emergency concern terms are detected.
- Community disposition projection
- Missing red-flag fields
- Clinician pickup handoff
NHS 111-style service
Non-emergency telephone triage workflow analogue for queue routing, structured assessment prompts, and clinician review.
- Directory-of-services handoff readiness
- Structured question set alignment
- Safety-net review gate
Canada 811-style service
Provincial health advice line workflow analogue for nurse callback queues and urgent-care routing.
- Nurse callback priority
- Urgent-care routing candidate
- Emergency escalation guard
Governed evolution loop
Operator feedback and workflow gaps become a clinical governance queue. They do not change triage rules, dispositions, or patient-facing advice until the evidence pack, safety sign-off, and vignette coverage are complete.
Operator rewording pattern
evo-operator-reworded-breathing-question
Operator reworded a breathing-risk prompt for caller comprehension; only the action category and fact keys are retained.
Community red-flag gap
evo-community-red-flag-gap
Community queue users need the missing red-flag field list to remain visible across nurse callback handoff.
Directory routing signal
evo-service-profile-directory-routing
Service-profile analogue highlights a directory-of-services routing difference for local deployment review.
Dummy run integration contract
The same governed turn can be rendered by an authorised external system through REST or MCP.
MCP integration event
Structured event summary
Operator nudge response
Preferred integration summary
Operator action acknowledgement
Closed-loop action summary
How ambient triage works
Listen in the room
Ambient audio or consultation context is reduced to structured clinical cues.
Understand context
Relevant symptoms, negatives, uncertainty, and missing critical fields are tracked.
Apply safety floor
Australian triage guardrails and red flags constrain every suggested next step.
Call MCP
The authorised system calls ambient-copilot-turn for the current tenant-owned session.
Nudge operator
A safe, concise next question or action is surfaced for clinical judgement.
Ready to show the implementation surface?
The public walkthrough explains the concept. The dummy run shows how an authorised system can render the same governed operator nudge from the integration contract.