See a doctor,
without the waiting room.
Video and chat consults connected to the same patient record as your clinic or hospital, with a triage agent that routes routine questions calmly and escalates genuine emergencies immediately — never waiting on an approval step that shouldn't exist in that moment.
Triage agent
Quick answer
How does telemedicine triage decide when to escalate immediately?
Most actions a triage agent might take require a documented human approval threshold before they execute, under rule INT-01 — this is deliberate, since an agent should not make consequential decisions unsupervised. Genuine emergencies are the one scoped exception: a small, published set of emergency-pattern symptoms triggers immediate escalation to a human clinician within a defined time limit, rather than waiting for approval that could cost real time in a genuine crisis. That exception, rule INT-01-EMERGENCY, is written down and bounded rather than left as an implicit "healthcare is different" carve-out, and every escalation is logged with the same immutability as any other agent action, emergency or not.
Most telemedicine tools
treat every case the same.
A queue with no triage, and a consult with no history, both cost the same thing: a delay that shouldn't exist.
Failure 01
The queue that isn't triaged
Patients wait in the same line whether the issue is urgent or routine, because nothing sorts them before a human looks.
Failure 02
The consult that starts from nothing
The clinician has no access to the patient's existing record from their last clinic or hospital visit, so the first minutes are spent re-establishing history that already existed.
Failure 03
The agent that waits too long
A rigid approval-only system delays escalation for a genuine emergency by exactly the amount of time it shouldn't.
Four components, one record.
Consults connect into the same patient record used across the rest of the HealthTech Suite, not a separate silo.
01
Video & chat consults
Connected to the same patient record used in Hospital and Clinic Management, so a clinician starts with real history, not a blank screen.
02
Triage agent with a stated exception
Most actions require approval; a defined, published set of emergency symptoms escalates to a human within a stated time limit instead.
03
Prescriptions & follow-up
Prescriptions route directly into the Pharmacy module where deployed, and follow-up tasks are logged against the patient record.
04
Full audit log
Every triage decision, escalation and consult recorded immutably, including which ones used the emergency exception and why.
Five steps, in this
order, every time.
The escalation path is tested deliberately before launch, not discovered during a real emergency.
- 1
Assess
Which consult types you need, and what should trigger immediate escalation for your clinic.
- 2
Configure
Clinician availability, consult types and the approval threshold, set to match your practice.
- 3
Integrate
Connect to your existing patient record from Hospital or Clinic Management, if deployed.
- 4
Test escalation
Trigger the emergency path deliberately and confirm it reaches a clinician within the stated limit.
- 5
Launch
Go live with monitoring on escalation timing from day one, not added after an incident.
Second target for an emergency escalation to reach a human clinician.
Classified Critical: human approval, manual override, no public training on your data.
Documented exception to the approval rule — stated, not hidden.
Why one emergency exception is stated, not hidden.
Requiring human approval before every agent action is the correct default, and healthcare is not an excuse to quietly weaken it everywhere. But a rigid interpretation would delay exactly the cases where seconds matter. The resolution is a narrow, published carve-out: pre-approved emergency actions may fire without waiting for approval only when they route to a human within a defined time limit, and they are logged with the same immutability as every other action. This is written into the Standard as an explicit exception class, not an implicit "healthcare is special" rule that quietly erodes INT-01 everywhere else it applies.
Source: The Qawex Standard v1.0, rule INT-01-EMERGENCY · /standard/intelligence/Answers, not brochures.
Is a video consult a replacement for an in-person visit?
Not always, and the system is built to know the difference. Triage routes cases that genuinely need a physical examination toward an in-person appointment rather than forcing every case through video regardless of fit.
What happens in a genuine emergency during a chat or video consult?
The stated emergency exception applies: recognised emergency symptoms trigger immediate escalation to a human clinician within a defined time limit, without waiting on the standard approval step, and the escalation is logged immediately.
Can prescriptions be issued through telemedicine?
Yes, and they route directly into the Pharmacy module where it's deployed, rather than being issued as a disconnected note the patient has to relay themselves.
Does the clinician see the patient's full history?
Where Telemedicine is connected to Hospital or Clinic Management, yes — the same record, not a separate copy. Where it runs standalone, history is limited to what's captured within Telemedicine itself.
Is this integrated with Clinic or Hospital Management, or standalone?
Both are supported. It runs best connected to an existing deployment so consults share the same patient record, but it can also run standalone for a clinic that only needs remote consults.
See how escalation actually works.
A demo walks through a real triage case, including how the emergency exception is bounded and logged.