SymptomRouter
Route patients to the right next step — safely
A triage service that asks clinically-approved symptom questions, applies rule-based escalation, and routes patients to the right specialist, queue, or emergency pathway — never pretending to be a doctor.
- 0 Diagnoses made — by design
- Rule -based escalation, deterministic
- Audit Trail on every decision
SymptomRouter runs a short, clinician-approved triage flow. It asks the questions a nurse would, applies deterministic escalation rules, and routes the patient to the right place — telehealth, in-person slot, or emergency referral.
Crucially, it never diagnoses. The flow, the rules, and the outputs are owned by the clinical team; the service just runs them consistently, documents every decision, and hands patients off with full context.
Everything SymptomRouter handles for you
-
Clinician-authored
Flows and rules are written and versioned by the clinical team — not improvised by an LLM.
-
Deterministic routes
Escalation is rule-based and audit-traced: same inputs, same outputs, every time.
-
Emergency pathway
Clear escalation to emergency services when triggers are hit — no ambiguity, no delay.
-
Documented decisions
Every routing outcome and its reasoning is captured in the audit trail.
How SymptomRouter plugs into the clinic stack
SymptomRouter is a deterministic layer sitting between intake and the clinician queue. It does not override clinical judgement — it prepares the ground.
- PatientPortal hosts the triage UI as part of the intake flow.
- ClinicianQueue receives the routed case with full triage context attached.
- PHIVault stores the decision trail with appropriate access controls.
- ConsentLedger captures and reads the consent required to run the triage.
Wire SymptomRouter into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.