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

Captioned product walkthroughSynthetic 000-style call audioSession active00:27 elapsed03:12

Pretend host environment

CRM/EHR host surface

Synthetic partner workspace showing how the assistant can sit over contact-centre and EHR surfaces.

No patient identifiers
Pretend CRM/EHR host environment

Composite CRM/EHR host surface with an overlay widget.

CRM: Genesys CRM shellEHR: Epic triage board context

Genesys-style call workspace

Genesys CRM shell

Live call
Queue
Ambulance intake
Call status
Synthetic 000 call connected
Redacted demographics
Captured
Initial complaint summary
Chest pain and shortness of breath
Rendered host fields
QueueCall statusRedacted demographicsInitial complaint summary

Epic-style ED track board

Epic triage board context

Patient file
demo-file-001
Priority
P1 review
Clinician pickup state
Structured assessments queued
Assessment queue
ABCDE safety screen
Open

high-risk chest pain intake

Respiratory effort screen
Ask now

shortness of breath concern term

Chest pain structured assessment
Prioritised

central chest pain complaint summary

Assistant behaviours in the host surface

Prompting

Active operator question

Suggesting

Next safe action

Assisting

Clinician pickup context

Synthetic 000-style call

Browser speech synthesis. No real patient audio.

Triple Zero

Triple Zero, ambulance. Tell me exactly what has happened.

Synthetic caller

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

00:07
Live conversation context
00:13
No patient identifier shown
00:19
Reviewed cue stream opened

Next best question

Operator-facing, not patient-released

AI governed

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

Safety floor active

Red-flag checks, escalation policy, and disposition floor remain active.

Red flag rulesChecked
Emergency keywordsChecked
High-risk conditionsChecked
Disposition floorChecked

Integration activity

Nudge surfaced
Completed

ambient-copilot-turn ready

Terminology checked
Completed

SNOMED CT-AU mapping checked

Evidence checkpoint ready
Completed

Review-safe event prepared

00:00

Demo reel cue sheet

Recording-safe chapter data for partners who need to embed or recreate the walkthrough.

Watch full demo reelOpen demo reel manifestOpen captions
Schema ambient-demo-reel-v1
Media captioned_product_walkthrough
Captions /ambient-triage/demo-reel/captions.vtt
Integration reference ambient-operator-nudge-v1
Integration chapter MCP handoff
Audio Synthetic 000-style call
No real patient audio Yes
Patient text Not retained

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.

Initial interaction agentClinician pickup file000 escalation

Captured intake file

Demographics captured
DOB captured
Address captured
Initial complaint captured
Raw complaint Not retained

Safety routing

Concern terms prioritise the queue before clinician handoff.

Priority clinician pickup
Matched issue
chest pain
Next tool
ambient-copilot-turn

Priority clinician pickup: high-risk concern terms detected during intake.

Next operator actions
  • 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.
Recommended structured assessments
ABCDE safety screenChest pain screenATS projection

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.

Community triage

Healthdirect Australia

National nurse-led telephone triage queue with escalation back to 000 when emergency concern terms are detected.

AU
Rendered considerations
  • Community disposition projection
  • Missing red-flag fields
  • Clinician pickup handoff
Handoff constraints
Decision support onlyNo patient text retainedNo patient advice released from ambient listeningGoverned triage must continue

NHS 111-style service

Non-emergency telephone triage workflow analogue for queue routing, structured assessment prompts, and clinician review.

UK analogue
Rendered considerations
  • Directory-of-services handoff readiness
  • Structured question set alignment
  • Safety-net review gate
Handoff constraints
Workflow analogue onlyLocal clinical rules not impliedNo patient text retainedGoverned triage must continue

Canada 811-style service

Provincial health advice line workflow analogue for nurse callback queues and urgent-care routing.

CA analogue
Rendered considerations
  • Nurse callback priority
  • Urgent-care routing candidate
  • Emergency escalation guard
Handoff constraints
Workflow analogue onlyProvincial clinical rules not impliedNo patient text retainedNo patient advice released from ambient listening

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.

1Operator feedback
2Governance queue
3Validated release
No automatic rule changesDeterministic safety floor unchangedRequires clinical governance approvalRequires vignette coverage

Operator rewording pattern

evo-operator-reworded-breathing-question

ambulance_call_taker

Operator reworded a breathing-risk prompt for caller comprehension; only the action category and fact keys are retained.

Review state
queued_for_clinical_governance
Required evidence
clinical_safety_reviewvignette_regression_coverageaudit_event_trace

Community red-flag gap

evo-community-red-flag-gap

community_triage

Community queue users need the missing red-flag field list to remain visible across nurse callback handoff.

Review state
needs_evidence_pack
Required evidence
workflow_surface_reviewclinical_safety_reviewvignette_regression_coverage

Directory routing signal

evo-service-profile-directory-routing

community_triage

Service-profile analogue highlights a directory-of-services routing difference for local deployment review.

Review state
queued_for_clinical_governance
Required evidence
local_service_directory_mappingclinical_safety_reviewtenant_configuration_approval

Dummy run integration contract

The same governed turn can be rendered by an authorised external system through REST or MCP.

Call-taker side panelED pre-arrival boardHealthdirect/811 queue
REST endpoint
POST /api/agentic-triage/ambient-sessions/ambient-demo-session-001/governed-turn
Open dummy run manifest

MCP integration event

Structured event summary

Tool ambient-copilot-turn
Session ambient-demo-session-001
Disposition mode ats
Jurisdiction AU
Structured events 1

Operator nudge response

Preferred integration summary

Schema ambient-operator-nudge-v1
Jurisdiction AU
Question Ask active breathing red-flag question
Source event consult-segment-004
Patient text Not retained
Decision support only Yes
Workflow surfaces ambulance_call_taker, emergency_department, community_triage

Operator action acknowledgement

Closed-loop action summary

Tool ambient-copilot-turn
Action asked
Recommendation event consult-segment-004
Recommendation provenance ambient-demo-history-taking:breathing-red-flag
Retention Question text not retained

How ambient triage works

01

Listen in the room

Ambient audio or consultation context is reduced to structured clinical cues.

02

Understand context

Relevant symptoms, negatives, uncertainty, and missing critical fields are tracked.

03

Apply safety floor

Australian triage guardrails and red flags constrain every suggested next step.

04

Call MCP

The authorised system calls ambient-copilot-turn for the current tenant-owned session.

05

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.