Skip to main content

​
Alerts

Alert management center for monitoring, reviewing, and responding to patient alerts and system notifications.

​
Overview

The Alerts page serves as a centralized hub for managing all types of alerts in the healthcare system. It provides filtering, prioritization, and action capabilities for clinical alerts, system notifications, and patient-triggered events. Alerts are categorized by type and severity to help providers quickly identify and respond to critical situations.

​
Features

​
Alert List

  • Chronological display of all alerts
  • Severity indicators (Critical, High, Medium, Low)
  • Alert type icons and labels
  • Timestamp and age display
  • Patient context for clinical alerts

​
Filtering System

  • By Type: Clinical, System, Patient, Administrative
  • By Severity: Critical, High, Medium, Low
  • By Status: New, Acknowledged, Resolved, Dismissed
  • By Date Range: Today, This Week, Custom Range
  • By Patient: Filter alerts for specific patient

​
Alert Types

  1. Clinical Alerts
    • Abnormal lab results
    • Vital sign anomalies
    • Medication interactions
    • Risk score changes
  2. Patient Alerts
    • Form submissions
    • Message notifications
    • Appointment requests
    • Symptom reports
  3. System Alerts
    • Integration failures
    • Scheduled maintenance
    • Security notifications
  4. Administrative Alerts
    • Pending approvals
    • Expiring authorizations
    • Compliance reminders

​
Alert Actions

  • Acknowledge alert
  • Dismiss alert
  • View related patient
  • Take action (context-specific)
  • Add notes
  • Escalate to team member

​
Alert Statistics

  • Total alert count by severity
  • Alerts by type breakdown
  • Response time metrics
  • Trend indicators

​
Use Cases

​
UC-ALT-001: Review Critical Alerts

Actor: Healthcare Provider
Description: Provider reviews and responds to critical patient alerts. Flow:
  1. Provider sees critical alert indicator
  2. Navigates to Alerts page
  3. Filters by “Critical” severity
  4. Reviews alert details
  5. Clicks “View Patient” for context
  6. Takes appropriate clinical action
  7. Acknowledges or resolves alert

​
UC-ALT-002: Acknowledge Batch Alerts

Actor: Healthcare Provider
Description: Provider acknowledges multiple non-critical alerts. Flow:
  1. Provider filters alerts by type
  2. Selects multiple alerts
  3. Clicks “Acknowledge Selected”
  4. Alerts status updates to acknowledged
  5. Alerts move to acknowledged section

​
UC-ALT-003: Investigate Alert Trend

Actor: Healthcare Administrator
Description: Administrator investigates increase in specific alert type. Flow:
  1. Administrator views alert statistics
  2. Notices spike in specific alert type
  3. Filters to that alert type
  4. Reviews individual alerts
  5. Identifies pattern or root cause
  6. Takes corrective action

​
UC-ALT-004: Escalate Alert

Actor: Healthcare Provider
Description: Provider escalates alert to specialist or supervisor. Flow:
  1. Provider reviews complex alert
  2. Determines escalation needed
  3. Clicks “Escalate” action
  4. Selects team member
  5. Adds escalation notes
  6. Alert assigned to specialist
  7. Specialist receives notification

​
User Stories

​
US-ALT-001

As a healthcare provider
I want to see critical alerts prominently
So that I can respond to urgent situations quickly Acceptance Criteria:
  • Critical alerts are visually distinct
  • Critical count shows in navigation
  • Sound/visual notification for new critical alerts
  • Critical alerts appear at top of list

​
US-ALT-002

As a healthcare provider
I want to filter alerts by type and severity
So that I can focus on relevant alerts Acceptance Criteria:
  • Multiple filter options available
  • Filters can be combined
  • Filter state persists during session
  • Clear all filters option available

​
US-ALT-003

As a healthcare provider
I want to acknowledge alerts
So that my team knows I’ve seen them Acceptance Criteria:
  • Acknowledge action is one-click
  • Acknowledged alerts show who/when
  • Bulk acknowledge is supported
  • Acknowledged alerts remain visible

​
US-ALT-004

As a healthcare provider
I want to navigate from alert to patient
So that I can take action in context Acceptance Criteria:
  • Patient link is visible on alert
  • Click navigates to patient detail
  • Alert context is preserved
  • Return to alerts is easy

​
US-ALT-005

As a healthcare administrator
I want to see alert statistics
So that I can monitor system health Acceptance Criteria:
  • Alert counts by severity shown
  • Alert counts by type shown
  • Trend indicators visible
  • Time-based filtering available

​
Component Dependencies

AlertsComponent
├── AlertFilterBarComponent
├── AlertListComponent
│   └── AlertItemComponent
├── AlertStatsComponent
└── AlertDetailModalComponent

​
Data Flow

┌─────────────────┐     ┌──────────────────┐
│  AlertService   │────▶│                  │
└─────────────────┘     │                  │
         │              │     Alerts       │
         │              │    Component     │
         ▼              │                  │
┌─────────────────┐     │                  │
│  WebSocket      │────▶│                  │
│  (Real-time)    │     └────────┬─────────┘
└─────────────────┘              │
                        ┌────────┴────────┐
                        │                 │
                        ▼                 ▼
                 ┌──────────┐      ┌──────────┐
                 │FilterBar │      │AlertList │
                 └──────────┘      └──────────┘

​
Technical Notes

  • Real-time alert updates via WebSocket
  • Alerts are persisted with full audit trail
  • Critical alerts trigger browser notifications
  • Alert rules are configurable per organization
  • Supports integration with external monitoring systems
  • Mobile-responsive for on-call access