Skip to main content

Notifications

What it does​

Notifications let administrators manage templates, events, deliveries, and subscriptions for channels such as email or SMS. Templates define content; events record what was triggered; subscriptions control who receives which kinds of messages. An emergency review queue may be available for sensitive notification paths.

Where to find it​

  • Notifications — /notifications
  • Templates — /notifications/templates
  • Events — /notifications/events
  • Subscriptions — /notifications/subscriptions
  • Emergency review — /notifications/emergency-review
  • Critical-result acknowledgement — /notifications/critical-results

📸 Screenshot: notifications admin (notifications-admin).

Notifications admin

Common tasks​

Manage a template​

  1. Open Notifications → Templates.
  2. Create or open a template: code, channel, body/variables your site uses.
  3. Save. Voided templates cannot be used for new deliveries.

Review events and deliveries​

  1. Open Events.
  2. Open an event to see delivery attempts. Failed provider attempts remain in history so nothing is silently lost.

Configure subscriptions​

  1. Open Subscriptions.
  2. Create a subscription for a user/person, channel, and template or event-type scope.
  3. Deactivate subscriptions that should stop receiving traffic.

Emergency review​

Open Emergency review when your deployment uses moderated / break-glass notification paths, and process items according to local policy.

Acknowledge a critical result​

  1. Open Critical-result acknowledgement.
  2. Optionally filter by the generic source-module key, such as imaging or lab.
  3. Review the severity, current escalation level, and notification history. An unacknowledged item remains visible and continues to escalate.
  4. Select Acknowledge. The queue records the signed-in clinician and time.
  5. After acknowledgement, select Close result when the local closed-loop procedure is complete.

Tips & limitations​

  • Real email/SMS providers are configured by operations (SMTP / SMS gateway). Local and CI environments often use a simulated provider — messages appear as deliveries without leaving the platform.
  • Subscription admin against a live API depends on notification-subscription endpoints (M10-009 / FE-104). If save fails while other notification screens work, that slice may still be mock-backed.
  • Never put secrets or full PHI into template codes or unrestricted variables.
  • Critical-result delivery is not controlled by ordinary notification subscription opt-outs. Do not treat a muted reminder channel as a reason to defer acknowledgement.
  • Imaging-specific criteria and the imaging-filtered queue live under Imaging → Critical criteria / Critical results (FE-224). This notification screen remains the generic shared queue.

When something looks wrong​

What you seeWhat it usually is
A notification was not deliveredThe channel is not configured for this deployment, or the provider is unavailable
A critical result is still outstandingAcknowledgement is a queue action, not a side effect of viewing the result
A template renders oddlyIts placeholders do not match the event that triggered it

For the causes common to every screen — a missing menu item, an empty list, a refusal — see Why a screen will not work.