Drug Infusion Device Auto-Programming Setup Time Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current drug infusion devices face challenges in quickly and accurately programming, leading to potential delays and errors in drug delivery, particularly in acute situations where rapid setup is crucial, and there is a need for enhanced safety and reduced human error.

Innovation Solution

A medication administering system that includes a drug infusion device connected to a medication management server, allowing for auto-programming and redundant safety checks, enabling rapid configuration and minimizing user intervention, with features like vial scanning for drug identification and automatic error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If manual programming is used for drug infusion devices, then programming accuracy can be maintained, but setup time increases and user error risk increases

Engineering Contradiction:
Improvesetup timeVSAvoidprogramming accuracy
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary actions by automatically retrieving and pre-configuring all necessary programming parameters from the electronic health record before the user needs to start the infusion. The programming parameters are pre-fetched and validated in advance, eliminating the need for manual entry and reducing setup time while maintaining accuracy through automated verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the programming parameters are automatically validated against the retrieved electronic health record data. The system provides real-time feedback to ensure accuracy by comparing programmed values with patient-specific parameters from the EHR, preventing errors before they occur and ensuring both speed and reliability.

Inventive Principle:
Principle #23Feedback

2Productivity

If automated programming is implemented, then setup time is reduced, but system complexity increases

Engineering Contradiction:
Improveprogramming speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer in the form of an automated programming module that acts as a mediator between the user and the complex programming requirements. This intermediary automatically handles the retrieval, validation, and configuration of programming parameters from the electronic health record, shielding the user from system complexity while enabling rapid programming.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The programming system is designed with multi-functionality, where a single automated programming module handles multiple tasks including data retrieval, parameter validation, error checking, and configuration. This universal approach consolidates complex functions into one integrated system, improving productivity without proportionally increasing user-facing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If redundant safety checks are added, then patient safety improves, but programming time increases

Engineering Contradiction:
Improvepatient safetyVSAvoidprogramming time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs safety checks in advance during the automated programming process rather than during manual configuration. By pre-validating programming parameters against the electronic health record before the infusion starts, the system incorporates redundant safety checks without adding time to the actual programming operation, as the verification occurs concurrently with or before parameter entry.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements real-time feedback loops that continuously validate programming parameters against patient data from the electronic health record. This feedback mechanism provides immediate verification of safety critical parameters, ensuring patient safety through redundant checks while maintaining fast programming speeds through automated, parallel validation processes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3440578B1Control of a drug infusion device
Publication Date: 2024.03.20 ICU MEDICAL INC
  • EP3440578B1 patent drawingFigure 1
  • EP3440578B1 patent drawingFigure 2
  • EP3440578B1 patent drawingFigure 3

AI summary

A drug infusion device determines whether an infusion program is stored within a memory. If so, a user is prompted to confirm usage of the program and a drug identifier, and to review the configuration of the device. If the program is not in the memory, the drug infusion device is enabled to receive an auto program with which it can configure itself. When auto program receipt is enabled, the drug infusion device waits for the auto program or for a selection for manual entry of the infusion program. A menu screen is displayed to indicate that the drug infusion device is waiting for the auto program, but the menu screen is not displayed if the auto program is already received. Therefore, a waiting for auto program menu screen may be avoided in many cases, reducing device setup time. In some embodiments, removal of a drug vial resets the device to a point after a power-on self-test and thus provides an easy method for resetting the device to a point that avoids unnecessary steps and expands a window of opportunity for receiving an auto program compared to prior work flows.