Medical device data back-association, system, apparatuses, and methods

Inventors

Heavelyn, Troy David • ALLEN, Curt Matthew • Fisk, Phillip Edwin

Assignees

Baxter Healthcare SA • Baxter International Inc

Abstract

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.

Core Innovation

The invention relates to a medical system for associating device data with the correct electronic medical record (EMR) during treatment. An EMR memory stores machine-readable code or instructions that, when executed by a processor, receive an identifier message while an infusion pump or medical device is administering a medication to a patient.

The identifier message is generated by scanning at least one of alpha-numeric characters, barcodes, or quick-response ("QR") codes corresponding to at least two of a device identifier, a patient identifier, and a medication order identifier. Using the identifier message, the processor creates an association between an EMR of the patient and the infusion pump or medical device, and after the association is created, receives device data that includes the device identifier and stores the device data to the patient’s EMR based on the created association.

The disclosed workflow also addresses scenarios where device data is received before an association can be determined. In such cases, the processor determines there is no association between the device identifier and any patient identifiers or medication order identifiers and stores the device data to an unassociated record, with variants where the unassociated record is indexed by the device identifier and where association creation is refined by matching patient and/or medication order identifiers between the identifier message and medication order records.

Claims Coverage

The provided material includes three independent claims. Across these independent claims, the coverage centers on receiving scanned identifier messages containing device, patient, and medication order identifiers, creating an EMR-to-device association, and storing subsequently received device data into the patient’s EMR based on that association. Additional coverage includes pre-association handling with storage to an unassociated record and indexing by device identifier.

Collectively, the independent claim coverage establishes a process in which scanned codes provide device identifier together with patient and medication order identifiers, an EMR-to-device association is created, and device data received after association is stored into the patient’s EMR based on that association. The coverage further includes handling device data when no association can be determined by storing it to an unassociated record and, in variants, indexing unassociated records by the device identifier.

Stated Advantages

Documented Applications