Infusion Pump Alerting With ML-Based Programming Error Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Infusion pumps face challenges in accurately detecting and alerting infusion programming errors due to broadly set limits, infrequent updates, lack of customization for patient type or condition, and computational limitations, leading to potential underdosing or overdosing.

Innovation Solution

A remote monitoring system with higher computing capabilities, integrated with EMR servers and analysis engines, uses machine learning to detect errors and provide alerts, allowing for flexible updates and personalized monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a drug library with broadly set limits is used for error detection, then the pump can accommodate unusual use cases, but it produces excessive warnings that result in users ignoring alerts

Engineering Contradiction:
Improveaccommodation of unusual use casesVSAvoidaccuracy of error detection
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system dynamically adjusts alert thresholds and parameters based on real-time analysis of infusion patterns, patient characteristics, and clinical context. The analysis engine continuously learns from actual usage data to refine what constitutes a genuine error versus an acceptable variation, making the error detection system adaptive rather than static.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback loops where the analysis engine monitors user responses to alerts and infusion outcomes to continuously improve detection accuracy. By analyzing which alerts are overridden and which lead to actual errors, the system refines its warning criteria to reduce false positives while maintaining sensitivity to real problems.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If hard limits are manually updated in the infusion pump drug library, then error detection can be customized, but the pump has computational limitations that restrict sophisticated monitoring features

Engineering Contradiction:
Improvecustomization for patient type and conditionVSAvoidcomputational capabilities of the pump
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A remote analysis engine serves as an intermediary between the infusion pump and the decision-making process. This external computational system handles complex analysis, pattern recognition, and sophisticated error detection, while the pump itself remains a simpler device that only performs basic parameter monitoring and communication with the analysis engine via the communication server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system moves error detection and analysis from the device dimension (pump) to the cloud dimension (remote server). By leveraging remote computing resources, the system achieves sophisticated monitoring capabilities without increasing the computational complexity of the pump hardware itself, effectively adding a new dimension to where processing occurs.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of manufacture

If the drug library is updated infrequently, then the pump structure remains simple, but the monitoring system cannot keep pace with changing clinical guidelines and practices

Engineering Contradiction:
Improvesimplicity of update processVSAvoidtimeliness of error detection
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The analysis engine continuously pre-processes and analyzes new clinical data, guidelines, and usage patterns in advance, building updated detection models before they are needed. This allows the system to respond rapidly to changing clinical practices without requiring frequent manual updates to pump software or hardware.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous learning and adaptation through ongoing analysis of infusion data, automatically updating its error detection algorithms in real-time. This continuous operation ensures the system stays current with clinical best practices without interrupting pump operation or requiring periodic manual interventions.

Inventive Principle:
Principle #20Continuity of useful action

4Speed

If the pump performs all error detection locally, then response time is fast, but the pump lacks the computational power for sophisticated monitoring features

Engineering Contradiction:
Improvemonitoring response timeVSAvoidcomputing capabilities of the pump
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The error detection function is segmented into two parts: local execution (fast, basic parameter checking at the pump) and remote execution (sophisticated pattern analysis and complex calculations at the cloud server). This segmentation allows the pump to maintain fast local response for immediate alerts while offloading computationally intensive tasks to remote systems with greater processing power.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20260077120A1Infusion pump error detection and alert communication systems and methods
Publication Date: 2026.03.19 BAXTER INT INC
  • US20260077120A1 patent drawing
  • US20260077120A1 patent drawing
  • US20260077120A1 patent drawing

AI summary

A system includes at least one infusion pump, an EMR server, an analysis engine, and a communication server. The analysis engine is configured to receive programming parameters and patient information from at least one of the infusion pump(s) and the EMR server. The analysis engine further configured to use at least one machine learning model configured to detect errors and abnormalities of programming parameters to generate an alert based, at least in part, on the programming parameters and the patient information. The communication server is communicatively coupled to a database and configured to both send and receive information from the infusion pump(s) and the analysis engine. The information received from the analysis engine includes the alert, which is saved in the database and transmitted to the infusion pump(s).