Messaging, Memo Desk and alert requirements · C0991
Can a facility define what its own codes mean?
In the pilot (v0.2.0, synthetic data)
Short answer
Code alerts must be configurable per facility: name, color, meaning, script, audience, sound, lockdown and integration actions. No code meaning must be hard-coded as universal. That is REQ-4202, a top-priority requirement for all three tiers. The pilot covers part of this. The rest is designed, not built. Where the code stands: Editable templates with propose/approve; no per-facility scripts/integration actions. Test in the specification: two facilities can define Code Silver differently and both work.
This exists in the synthetic-data pilot only.
- Specification item
- REQ-4202
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, 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
- Does AuroraMed support alert classes CODE, CLINICAL-CRITICAL (lab, imaging, blood), PING-EMERGENCY, PING-URGENT and PING-STANDARD with defined priority levels, ack rules and escalation? Pilot
- Does AuroraMed ship a default code library (Code Blue, Red, Pink, Purple, Silver, Active Shooter/Imminent Threat, Gray, Black, Orange, Yellow, Green, White, Triage, Amber, Rapid Response, Stroke, STEMI, Trauma, Sepsis, Massive Transfusion) as editable templates with no asserted universal meaning? Pilot
- How does a two-person cancel of an imminent-threat alert work in the spec? Pilot
See it in context: Code and clinical alert notifications · Search the help center · Ask a question