-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Highest
-
US Da Vinci Alerts (FHIR)
-
0.2.0 [deprecated]
-
Infrastructure & Messaging
-
Home (index)
-
1.1.2
-
-
Ulrike Merrick/Nick Radov: 3-0-1
-
Clarification
-
Compatible, substantive
Unsolicted notifications should be limited to defined use cases and triggers, with named message types. We don't want to create a scenario where people can start sending alerts based on self defined triggers; that could create a system where someone has to manually review the alert and decide what to do with it. Far more efficient would be a set of specific alert use cases/triggers that developers could program to route certain message types to specific work queues. Perhaps the best way to deal with this would be for actors to only use unsolicited notifications for approved/defined use cases. What we want to avoid are free text messages that would require manual review.
Existing Wording:
Out of Scope: What constitutes a trigger (nature of the event as defined in your organization)
- is duplicated by
-
FHIR-26115 Triggers should not be out of scope
-
- Duplicate
-
- is voted on by
-
BALLOT-11670 Negative - Celine Lefebvre : 2020-Feb-ALERTS R1 STU
- Balloted