Skip to main content
The Crisis Queue screen is a real-time triage queue for active crisis alerts detected in the CE core. It is accessible at /ce/intake/crisis.

​
Overview

The Crisis Queue shows all active crisis alerts. A tab strip filters the queue to All active, Tier 1, or Tier 2. The page header states that Tier-1 alerts also page on-call clinicians. Each tab renders a CrisisQueueList for the corresponding tier. On mobile viewports, selecting an alert for escalation opens a CrisisAlertMobileSheet bottom sheet. The page uses a destructive (red) icon in its header to indicate urgency.

​
Who it’s for

Required permission: CE_PERMISSIONS.CRISIS_VIEW (route-level gate, resolved from @/platform/permissions/constants).

​
Before you start

  • You need the CE_PERMISSIONS.CRISIS_VIEW permission.
  • Crisis alerts must have been generated by the platform detection system.

​
Steps

1

Open the Crisis Queue

Navigate to /ce/intake/crisis from the Community Engagement navigation or a crisis widget link.
2

Filter by tier

Click the Tier 1 or Tier 2 tab to focus on a specific severity level, or stay on All active to see everything.
3

Triage an alert

Use the actions available within the CrisisQueueList (SME: confirm exact actions — acknowledge, confirm, dismiss, escalate).
4

Escalate on mobile

On a mobile device, tap an alert and use the bottom sheet to take action or escalate.

​
Key concepts

  • Tier 1 — highest severity; on-call clinicians are paged automatically.
  • Tier 2 — lower severity; requires manual review and action.
  • Crisis alert — generated by platform detection; displayed as DbCrisisAlert type records.

Community Engagement

Community Engagement core overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/ce.tsx
  • src/cores/ce/pages/CrisisQueuePage.tsx