Messaging, Memo Desk and alert requirements · C0996
Does alert delivery survive failures, and which channels does it fall back to?
In the pilot (v0.2.0, synthetic data)
Short answer
The pilot covers part of this. The rest is designed, not built. In the pilot: Store-and-forward with late flag, dedup; ordering/at-least-once under failure not load-tested. For reference, REQ-4207 (a top-priority requirement, the medium and large tiers) says Alert delivery must be at-least-once with de-duplication, ordered per alert, with delivery receipts, and must fall back across channels (terminal, tablet, pager/radio/phone gateway where installed). Check: kill one channel; alert arrives via next.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-4207
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- What happens if a critical result is not acknowledged? Pilot
- Do pager and SMS alerts contain patient information? Designed
- Is every alert action audited? Pilot
- Do code alerts work when the internet or cloud is down? Designed
See it in context: Code and clinical alert notifications · Search the help center · Ask a question