Abstract: An infusion pump including an interface unit for receiving first data for a first infusion regimen for a medication, the first regimen including a first unit of measure in which the first regimen is executed and after receipt of the first data, second data for a second infusion regimen for the medication, the second regimen including a second unit of measure in which the second regimen is executed. The pump also includes a processor for comparing the first and second units of measure. In one embodiment, the pump includes a graphical user interface, and the processor identifies a difference between the first and second units of measure; generates, using the processor, a warning message; and displays the message on the graphical user interface. In another embodiment, the processor holds in abeyance initiation of the second infusion regimen in response to identifying the difference between the units of measure.

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.

Abstract: A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives first medical device data from a medical device including a device identifier and stores the first medical device data to an unassociated record in a database after determining that there is no association between the device identifier and any patient identifier or medication order identifier. While the medical device is administering the medication to a patient, the server receives an identifier message including at least two of the device identifier, the patient identifier, and the medication order identifier. The server creates an identifier association between a medical record of the patient and the medical device using the identifier message. The server uses the identifier association to store subsequent medical device data from the medical device to the medical record of the patient.

Abstract: A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives first medical device data from a medical device including a device identifier and stores the first medical device data to an unassociated record in a database after determining that there is no association between the device identifier and any patient identifier or medication order identifier. While the medical device is administering the medication to a patient, the server receives an identifier message including at least two of the device identifier, the patient identifier, and the medication order identifier. The server creates an identifier association between a medical record of the patient and the medical device using the identifier message. The server uses the identifier association to store subsequent medical device data from the medical device to the medical record of the patient.

Abstract: A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives first medical device data from a medical device including a device identifier and stores the first medical device data to an unassociated record in a database after determining that there is no association between the device identifier and any patient identifier or medication order identifier. While the medical device is administering the medication to a patient, the server receives an identifier message including at least two of the device identifier, the patient identifier, and the medication order identifier. The server creates an identifier association between a medical record of the patient and the medical device using the identifier message. The server uses the identifier association to store subsequent medical device data from the medical device to the medical record of the patient.

Abstract: An infusion pump including an interface unit for receiving first data for a first infusion regimen for a medication, the first regimen including a first unit of measure in which the first regimen is executed and after receipt of the first data, second data for a second infusion regimen for the medication, the second regimen including a second unit of measure in which the second regimen is executed. The pump also includes a processor for comparing the first and second units of measure. In one embodiment, the pump includes a graphical user interface, and the processor identifies a difference between the first and second units of measure; generates, using the processor, a warning message; and displays the message on the graphical user interface. In another embodiment, the processor holds in abeyance initiation of the second infusion regimen in response to identifying the difference between the units of measure.

Abstract: A medical device data back-association system, apparatuses, and methods are disclosed. In an example embodiment, a server receives first medical device data from a medical device including a device identifier and stores the first medical device data to an unassociated record in a database after determining that there is no association between the device identifier and any patient identifier or medication order identifier. While the medical device is administering the medication to a patient, the server receives an identifier message including at least two of the device identifier, the patient identifier, and the medication order identifier. The server creates an identifier association between a medical record of the patient and the medical device using the identifier message. The server uses the identifier association to store subsequent medical device data from the medical device to the medical record of the patient.

Abstract: An infusion pump including an interface unit for receiving first data for a first infusion regimen for a medication, the first regimen including a first unit of measure in which the first regimen is executed and after receipt of the first data, second data for a second infusion regimen for the medication, the second regimen including a second unit of measure in which the second regimen is executed. The pump also includes a processor for comparing the first and second units of measure. In one embodiment, the pump includes a graphical user interface, and the processor identifies a difference between the first and second units of measure; generates, using the processor, a warning message; and displays the message on the graphical user interface. In another embodiment, the processor holds in abeyance initiation of the second infusion regimen in response to identifying the difference between the units of measure.

Abstract: An infusion pump including an interface unit for receiving first data for a first infusion regimen for a medication, the first regimen including a first unit of measure in which the first regimen is executed and after receipt of the first data, second data for a second infusion regimen for the medication, the second regimen including a second unit of measure in which the second regimen is executed. The pump also includes a processor for comparing the first and second units of measure. In one embodiment, the pump includes a graphical user interface, and the processor identifies a difference between the first and second units of measure; generates, using the processor, a warning message; and displays the message on the graphical user interface. In another embodiment, the processor holds in abeyance initiation of the second infusion regimen in response to identifying the difference between the units of measure.