Patient intake and triage
The patient types or talks; intake and urgency scoring take seconds, and a nurse always makes the final call.
Patient intake and triage
- Voice message received in the app, patient identity verified via OTP
- Transcribed (Turkish, 42 s): "chest tightness for two days, worse on the stairs"
- History pulled: 58 y, hypertension, no prior cardiac events
- 3 follow-up questions asked: no radiating pain, no shortness of breath at rest
- Manchester Triage discriminators for chest pain retrieved
- Urgency score 71/100 → "urgent" (same-day cardiology), red flags: 1 of 6
- Guardrail: no diagnosis given to the patient, emergency wording checked
- Triage nurse confirmed the urgency level on the dashboard (mandatory for every case)
- Cardiology slot booked today 15:40, Dr Kaya, room C-204
- Patient sent the slot, directions and a "call 112 if worse" instruction on WhatsApp
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Voice or text symptom report in the app or on WhatsApp
Urgency confirmed by a nurse, appointment booked in the right clinic, patient guided
Agents
Triage Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Voice Agent
Transcribes the voice message and detects language
transcribe_audiodetect_languageSymptom Agent
Asks follow-up questions and structures the complaints
ask_followupextract_symptomsget_patient_historyUrgency Agent
Scores urgency against protocol; never makes the final decision
search_triage_protocolscore_urgencycheck_red_flagsRouting Agent
Finds the right clinic and slot, books the appointment
find_clinic_slotbook_appointmentsend_whatsappSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Triage Supervisor | Voice message received in the app, patient identity verified via OTP | — | 220 | — |
| 02 | reason | Voice Agent | Transcribed (Turkish, 42 s): "chest tightness for two days, worse on the stairs" | — | 900 | 380 |
| 03 | tool | Symptom Agent | History pulled: 58 y, hypertension, no prior cardiac events | EHR (HL7/FHIR) | 430 | — |
| 04 | reason | Symptom Agent | 3 follow-up questions asked: no radiating pain, no shortness of breath at rest | — | 1,100 | 720 |
| 05 | retrieve | Urgency Agent | Manchester Triage discriminators for chest pain retrieved | Triage Protocol Vector Store | 380 | 520 |
| 06 | reason | Urgency Agent | Urgency score 71/100 → "urgent" (same-day cardiology), red flags: 1 of 6 | — | 760 | 940 |
| 07 | verify | Urgency Agent | Guardrail: no diagnosis given to the patient, emergency wording checked | — | 340 | 260 |
| 08 | approval | Triage Supervisor | Triage nurse confirmed the urgency level on the dashboard (mandatory for every case) | — | 2,800 | — |
| 09 | write | Routing Agent | Cardiology slot booked today 15:40, Dr Kaya, room C-204 | HIS Scheduling | 480 | — |
| 10 | notify | Routing Agent | Patient sent the slot, directions and a "call 112 if worse" instruction on WhatsApp | WhatsApp Business API | 260 | — |
Prior authorization
Payer rules searched, clinical evidence gathered and the packet ready to submit within minutes of the order.
Appointment scheduling and no-show reduction
High no-show-risk patients are reached on WhatsApp in advance; freed slots are refilled from the waiting list.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis