Infusion Pump EMR Back-Association for Complete Treatment Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current electronic medical record (EMR) systems require manual association between medical devices and patient records, leading to inefficient data storage and potential loss of medical device data if the association is not made prior to treatment, necessitating time-consuming manual data transfer post-treatment.

Innovation Solution

A system and method for back-associating medical device data with a patient's EMR by scanning device and patient identifiers, enabling automatic storage of medical device data to the EMR after treatment has begun or completed, using barcodes, QR codes, or NFC/RFID microchips for identification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual association between medical device and patient record is required before treatment, then data storage accuracy is improved, but treatment efficiency and ease of operation deteriorate due to time-consuming manual processes

Engineering Contradiction:
Improvedata storage accuracyVSAvoidtreatment efficiency
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system performs preliminary actions by pre-generating unique identifiers for medical devices and preparing the EMR system to receive and process these identifiers. The EMR server is pre-configured with the capability to automatically match identifiers and associate devices with patient records, so that when treatment begins, the association process is already optimized and ready to execute automatically without manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical manual process of associating devices with patient records with an automated electronic identification and matching system. Barcode scanners, RFID readers, or other automated identifier capture devices replace manual data entry, and automated algorithms replace manual matching logic, thereby improving both accuracy and efficiency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Speed

If association is made after treatment has begun, then treatment speed is improved, but data completeness and reliability deteriorate due to potential data loss

Engineering Contradiction:
Improvetreatment speedVSAvoiddata completeness
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the EMR server continuously monitors for identifier messages during and after treatment. The server receives feedback in the form of identifier messages from various sources (scanners, device transmissions) and automatically processes these to create associations. This continuous feedback loop ensures that even if association is delayed, the system remains alert and ready to capture and process the identifier information as soon as it becomes available.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of temporary storage or buffer zones for identifier messages. When a medical device transmits its identifier or when a scanner captures it, the information is held in an intermediary state until the EMR server can process and match it with the appropriate patient record. This intermediary buffer prevents data loss even if the association process is delayed.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual data copying from temporary storage to EMR is required, then data security is improved, but productivity and time efficiency deteriorate

Engineering Contradiction:
Improvedata securityVSAvoiddocumentation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements self-service by enabling the EMR server to automatically perform the entire association process without requiring manual data copying. The server autonomously receives identifier messages, matches identifiers to patient records, creates associations, and stores device data directly in the appropriate EMRs. This automation eliminates the manual labor of copying data while maintaining security through controlled automated processes.

Inventive Principle:
Principle #25Self-service

4Productivity

If automatic data storage from medical device to EMR is enabled, then productivity is improved, but device complexity increases due to association management requirements

Engineering Contradiction:
Improvedata storage efficiencyVSAvoidassociation management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the complex association management logic from the medical device itself and places it in the EMR server. The medical device only needs to transmit its unique identifier, which is a simple operation. The complex tasks of receiving the identifier, matching it with patient records, creating associations, and managing data storage are extracted and handled by the EMR server's automated systems, thereby reducing device complexity while maintaining high productivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260080990A1Medical device data back-association, system, apparatuses, and methods
Publication Date: 2026.03.19 BAXTER INT INC
  • US20260080990A1 patent drawing
  • US20260080990A1 patent drawing
  • US20260080990A1 patent drawing

AI summary

A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives, while an infusion pump is administering a medication to a patient, an identifier message including at least two of a device identifier of the infusion pump, a patient identifier of the patient, and a medication order identifier of a medication being administered by the infusion pump. The server prompts a clinician device for creating an association between an electronic medical record (“EMR”) of the patient and the infusion pump. When an association to be created, the server uses contents of the identifier message to create the association. For subsequently received infusion pump data, the server stores this infusion pump data to the EMR of the patient based on the created association between the EMR of the patient and the infusion pump.