One queue before many tools
Patient requests should land in a single operational queue before they scatter into calendars, records, reminders, and staff inboxes.
Reference architecture
A staff-reviewed operating model for patient access.
This is the architecture we are designing around: patient requests come in from every channel, policy checks run before automation acts, and staff stay in the approval loop for exceptions.
Design principles
Architecture is product behavior.
The important question is not which cloud logo sits behind the product. It is whether the system can explain what happened when a patient request turns into an appointment, task, reply, or escalation.
Human review is a control plane
The architecture keeps approval points visible. Automation prepares the work; clinic staff can intervene before a patient-facing action goes out.
Audit trail by default
Every automation decision should leave context behind: source message, detected intent, policy used, reviewer, timestamp, and final action.
Integrate without pretending
EHR and phone systems vary widely. The platform should expose clean integration points without claiming universal plug-and-play coverage.
Data boundaries
Keep every handoff visible.
We are not presenting this as a deployed compliance certification. This page describes the operating model and data boundaries the product is being shaped around.
Inbound message
Captured with source, timestamp, channel, and patient context when available.
Intent + policy result
Stored as reviewable metadata, not treated as a final clinical decision.
Staff action
Human edits, approvals, assignments, and overrides are preserved.
External sync
Calendar/EHR/API updates are tracked as outbound events with status and retry history.
Integration model
Connect through narrow, reviewable interfaces.
Calendar updates, patient record sync, phone events, and intake packets should move through explicit events with status, retries, and review history. That keeps integrations observable instead of magical.
Inbound adapters
Normalize messages and call summaries without hiding the original channel or source context.
Policy checks
Run routing, hours, provider, and escalation rules before a reply or task is proposed.
Staff actions
Capture approvals, edits, overrides, and assignments as first-class events.
Outbound sync
Push approved updates to connected systems with observable success, failure, and retry states.
Want the concrete view?