01.2 — Relay
The inbox that closes
small decisions before
they become incidents.
Relay handles the steady stream of small clinical-operations decisions a primary-care team makes every day — pathology results, safety netting, medication changes, referrals, recalls, escalations — with explicit SLA matrices and escalation chains for items that breach.
A — What Relay handles
Seven queues. One inbox.
Each queue is a domain that has its own clinical and regulatory expectations. Relay carries those expectations as SLAs and escalation chains so an item that breaches doesn't quietly slip past the duty clinician.
- 01
Pathology results
Filed, reviewed, actioned. Abnormal results escalate per the SLA matrix.
- 02
Safety netting
Closed loops on contingent advice. Items with no follow-up surface before they fail.
- 03
Medication changes
Initiations, titrations, monitoring requirements, deprescribing — tracked through to confirmation.
- 04
Referrals
Outbound referrals tracked through acceptance, attendance, outcome, and integration with the patient record.
- 05
Recalls
Cohort-based recalls (chronic disease reviews, vaccination programmes) with completion and exception handling.
- 06
Tasks
The general-purpose queue for items that don't fit a specific clinical category.
- 07
Escalations
The breaching-item queue. When an item breaches its SLA, it lands here for the duty clinician.
B — Workflow preview
What partners see during a Relay walkthrough.
Relay's dashboard, queue views, and escalation surfaces are demonstrated to alpha partners alongside Cadence so they can see where the Operations Library is heading. Snapshots from active development:
C — What 'preview' means here
Buildable. Demonstrable. Not yet deployed.
Relay's database, schemas, queue model, and an eleven-stage onboarding wizard are scoped and partly implemented. The dashboard surface is in active build. We demonstrate Relay in alpha conversations to give partners a clear view of where the Operations Library is heading; we do not yet deploy it for partner use.
Cadence is the alpha product right now. Relay's deployment follows once Cadence has been calibrated against real partner use, because the lessons from Cadence's first deployment will materially shape Relay's design — what workflows actually need explicit SLA enforcement, what escalation patterns hold up, what reporting partners actually use.