TriageDesk
A digital front door for clinics — intake, triage, queue, consent.
Patients intake themselves, a protocol-driven router decides what they need, and clinicians see a prioritised queue — with PHI staying inside the vault.
WHY IT WORKS
TriageDesk takes the paperwork and the waiting room online. A patient lands on the clinic's page, answers a guided form, snaps a photo of their insurance card, uploads symptom photos and signs the clinic's consents in one flow. Behind that, a triage agent — tuned to the clinic's protocols, never to general medical advice — routes the case: video visit, in-person slot, self-care with follow-up, or urgent escalation.
Clinicians don't get a firehose of messages: they get a prioritised queue with context. Every signal — symptoms, history, consents, attachments — is stored in a separate PHI vault behind a strict consent ledger, and only summarised content leaves that vault. The rest of the stack is the same AIMicroservices backbone any AI product uses.
The result is a front door that replaces the call centre for routine needs, reduces no-show walk-ins and gives the clinician a one-minute pre-read before every patient walks in.
ARCHITECTURE · LAYERED BLUEPRINT
How the microservices wire up.
Read top to bottom. Channels are where people arrive, orchestration is how the AI thinks, domain is the startup-specific logic, data & identity keeps the source of truth, and platform is the invisible glue.
Scroll horizontally to see the full architecture.
INVENTORY
Every block in TriageDesk.
Each block is a microservice with a clear role — grouped by layer so you can see what belongs to channels, orchestration, domain, data and platform at a glance.
HOW TO SHIP IT
Quick-start checklist.
- 01 Codify the clinic's triage protocol inside KnowledgeBase + SymptomRouter.
- 02 Spin up PHIVault in the clinic's region; wire ConsentLedger to every intake form.
- 03 Connect Calendar to provider calendars; publish PatientPortal.
- 04 ClinicianQueue goes live; the phone desk becomes an escalation path.
WHAT'S NEXT
Compose TriageDesk in a visual workspace.
Log into AIM Engine 2.0, drop the blueprint on a canvas, fork the domain microservices you need, and deploy to your own domain. Everything shown here is already a real component.