Infusion Pump Data Back-Association for Automatic EMR Documentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current medical documentation systems require manual and time-consuming processes to associate medical device data with a patient's electronic medical record (EMR), leading to inefficiencies and potential data loss or incorrect data entry.
Innovation Solution
A system and method for automatically associating medical device data with a patient's EMR by using a medical device identifier, patient identifier, and medication order identifier, enabling automatic storage of device data to the EMR after treatment has begun or completed, utilizing barcode scanning and server processing to create associations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual association process is used to link medical device data with patient EMR, then data accuracy can be ensured through clinician verification, but time consumption and operational complexity increase significantly
Solution Approach 1:
The system performs preliminary actions by pre-processing medical device data and preparing association records before clinician review. The server automatically matches device identifiers with patient identifiers and medication order identifiers in advance, so that when the clinician reviews the data, the association is already established and ready for verification, reducing the time required at the point of care
Solution Approach 2:
The patent introduces an intermediary server that acts as a mediator between the medical device and the EMR system. This server automatically processes device data, performs identifier matching, and manages association records, thereby reducing the manual burden on clinicians while maintaining data accuracy through automated verification processes
2Reliability
If automatic data storage is implemented without pre-established associations, then data loss is prevented by storing all received data, but operational complexity increases due to temporary storage management and post-treatment association creation
Solution Approach 1:
The system segments the data storage and association process into distinct components: an unassociated records table for temporary storage of device data without patient links, and an associated records table for permanently linked data. This segmentation allows the system to maintain all received data while managing complexity through structured organization and automated association workflows
3Reliability
If clinician manually copies data from temporary storage to patient EMR after treatment, then data can be preserved, but productivity decreases due to repetitive manual tasks
Solution Approach 1:
The system implements self-service by enabling automatic data transfer and association creation through automated identifier matching. When a clinician scans or enters identifiers, the server automatically retrieves the corresponding device data from unassociated records, creates the association, and populates the EMR without requiring manual copying, thereby preserving data while significantly improving clinician productivity
4Extent of automation
If association is required before treatment begins, then data integration is seamless, but ease of operation is reduced due to mandatory pre-configuration steps
Solution Approach 1:
The system introduces dynamics by allowing the association process to be flexible rather than rigid. Associations can be established before treatment (pre-configuration mode) or after treatment begins (post-configuration mode). The server dynamically adapts to the timing of association creation, automatically managing unassociated records and enabling seamless integration regardless of when the association is made, thereby maintaining data integration while improving ease of operation
Data Source
AI summary
A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, an electronic medical record memory 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 administer by the infusion pump. The memory creates an association between an electronic medical record (“EMR”) of the patient and the infusion pump using the identifier message. The memory next receives, after the association between the EMR of the patient and the infusion pump, infusion pump data from the infusion pump. The infusion pump data includes the device identifier. The memory then stores the infusion pump data to the EMR of the patient based on the created association between the EMR of the patient and the infusion pump.