Clinical Alert Routing System with Dynamic Context Rules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Clinical decision support applications often deliver generic alerts that fail to target specific clinicians, leading to alerts reaching disinterested clinicians or not reaching the appropriate clinician in time, and messaging systems lack dynamic business logic and complex escalation rules, resulting in inefficient alert handling and potential alarm fatigue.

Innovation Solution

A messaging system with an event handler that receives and modifies inbound messages using rules based on hospital policies, on-call status, worklists, and workflows, allowing for intelligent routing of alerts to specific clinicians and prioritization of alerts based on severity, with a standardized protocol for representing and communicating messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If generic alerts are delivered to all clinicians, then alert coverage is maximized, but alert relevance and clinician engagement deteriorate

Engineering Contradiction:
Improvealert coverageVSAvoidclinician engagement
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The system applies local quality by customizing alert distribution according to each clinician's specific context, including their patient list, clinical role, current workload, and availability status. Instead of uniform alert delivery, the system dynamically adjusts which alerts each clinician receives based on their individual needs and capacity, thereby maintaining high alert coverage while ensuring relevance and engagement.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements dynamics by continuously monitoring clinician status (on-duty/off-duty, available/unavailable, current workload) and adjusting alert routing in real-time. This dynamic approach allows the system to adapt alert distribution as clinician circumstances change, ensuring alerts reach the right person at the right time while preventing overload on already-busy clinicians.

Inventive Principle:
Principle #15Dynamics

2Speed

If alerts are sent immediately upon generation, then response time is minimized, but alarm fatigue and distraction increase

Engineering Contradiction:
Improvealert response timeVSAvoidalarm fatigue
Core Design Contradiction:
SpeedVSObject-generated harmful factors

Solution Approach 1:

The system performs preliminary actions by proactively assessing clinician availability and workload before sending alerts. It checks the clinician's current status, ongoing tasks, and capacity to handle additional alerts, and only routes alerts to clinicians who are currently able to respond. This preliminary filtering prevents sending alerts to overwhelmed or unavailable clinicians, reducing alarm fatigue while maintaining rapid response times for appropriate recipients.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If complex business logic is implemented for each alert and user, then alert routing precision is improved, but system configuration complexity increases

Engineering Contradiction:
Improvealert routing precisionVSAvoidsystem configuration
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system applies self-service by automatically gathering necessary routing information from existing hospital systems (electronic health records, scheduling systems, workload management systems) without requiring manual configuration for each alert-user pair. The system autonomously determines clinician availability, patient assignments, and appropriate routing based on pre-integrated data sources, achieving high routing precision while minimizing configuration burden through automated data collection and processing.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2661849B1System and method for distributing meaningful clinical alerts
Publication Date: 2019.05.29 KONINKLIJKE PHILIPS NV
  • EP2661849B1 patent drawingFigure 1
  • EP2661849B1 patent drawingFigure 2
  • EP2661849B1 patent drawingFigure 3

AI summary

A messaging system (100) for routing clinical messages includes an event handler and a standardized protocol (105). The event handler (106) receives one or more inbound messages from one or more event sources (102). The event sources (102) include one or more worklist items. The event handler (106) further stores the worklist items in an event database (198) and generates and communicates outbound messages for one or more worklist items in the event database (198) that need to be acted upon, as determined by one or more rules. The standardized protocol (105)is used to represent the inbound messages and the outbound messages.