Lab result follow-up
uhc_labs_followup.v2 · active · effective 4 Aug 2026 · channels: whatsapp, email
DEMO · SYNTHETIC DATAThis console is a public product tour served from synthetic fixtures. There is no login, no tenant credential in the page, and no connection to a Regent backend. A real tenant console requires a server-side session boundary before a browser may reach tenant-scoped APIs.
Pre-judgment controls · run before the judgment engine
- ContactabilityActive channel required
WhatsApp preferred, email fallback where the subject has a verified address.
- Crisis flagNon-overridable hard stop
Same hard stop as every other policy. It is not a per-policy setting.
- Global opt-outNon-overridable hard stop
A global opt-out ends the operation before judgment.
Post-judgment controls · run after the AI proposal, before any dispatch
- Proposal-specific consentClinical correspondence scope
Consent must cover clinical follow-up specifically.
- Frequency cap3 per rolling 7 days
Shared cap across channels for the same subject.
- Send window08:00–21:00 subject-local
Outside the window resolves DEFER_REPUSH_REQUIRED. No queue.
- Content policyNo diagnostic detail in the message body
Result values never leave the tenant system; the message points the subject at their own portal.
Escalation
Named targetDr. Nour Khalil · on-call clinical lead
Acknowledgment SLA15 minutes
FallbackLadder to a secondary target, then the named operator alarm
Decisions governed by this version
Disabled in the demo. This action belongs to a signed backend sprint. Policy mutation is a Sprint 4 capability with its own signed contract.