Microservice - Notifications

[Broondoon]

Master thread for general discussion of the Notifications microservice.

[er-ber-ter]

Concepts: Users : They have contact info (phone, email, browser extension, etc.)

• For each contact method the user can say if they would like to be contacted there or not (boolean attached per method)
• We push notifications automatically as users get near the top of the queue to the notifications set to "true" (one MUST be on)
• A user has a list of ED's that they are nearby, we assume that they can go the closest one, but they can add others.

Queue:

• Assume 3 queues per ED, each of the 3 is based on severity (tier 1 is most urgent, tier 3 is least urgent), and users are treated in order of: tier 1's, if tier 1 is empty, tier 2, if tier 2 is empty, tier 3, etc.
• Users can be inserted into each of the 3 queues by our system based on virtual triage
• Users that are tier 1's: if their current "preferred" or "closest" ED is at full capacity, they will be recommended others that aren't at full capacity to hopefully (get treated faster/spread patient load)

[Broondoon]

Should be noted that the case where "preferred" is full and we recommend another, may be delegated to another milestone, as it is a case which may require integration with the Maps team.