US2020023127A1PendingUtilityA1

Management of infusion data methods and apparatus

Assignee: BAXTER INTPriority: Jan 29, 2002Filed: Sep 30, 2019Published: Jan 23, 2020
Est. expiryJan 29, 2022(expired)· nominal 20-yr term from priority
A61M 1/14G16H 10/60A61M 2205/33A61M 2205/502A61M 2005/14208A61M 2205/50A61M 2205/3584A61M 5/142A61M 2205/18A61M 2205/3334A61M 2205/52A61M 2205/3561A61M 1/1613G16H 20/17G16H 20/10G16H 40/63A61M 5/172A61M 2230/005G16H 20/40A61M 5/1723G16H 40/67A61M 1/34
62
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A networked patient care system includes an infusion pump communicatively coupled to a hospital network, a first server communicatively coupled to the infusion pump via the hospital network, and a second server communicatively coupled to the first server via a separate secure connection. The first server is configured to receive infusion pump data from the infusion pump and cause the second server to store the infusion pump data in an HL 7 format to an electronic patient medical record. The first server is also configured to receive a request from a display device to access the electronic patient medical record and cause the second server to convert the infusion pump data in the electronic patient medical record from the HL 7 format to a web-based format. The first server is further configured to transmit the infusion pump data in the web-based format to the display device.

Claims

exact text as granted — not AI-modified
The invention is claimed as follows: 
     
         1 . A networked patient care system comprising:
 an infusion pump communicatively coupled to a hospital network and configured to perform an infusion treatment on a patient, determine infusion pump data related to the infusion treatment, and transmit the infusion pump data in an HL 7 format to the hospital network;   a first server communicatively coupled to the infusion pump via the hospital network; and   a second server communicatively coupled to the first server via a separate secure connection, the first server including at least one relay interface to enable display devices to access electronic patient medical records that are stored via the second server,   wherein the first server is configured to
 receive the infusion pump data from the hospital network, and cause the second server to store the infusion pump data in the HL 7 format to an electronic patient medical record, 
 receive a request via the at least one relay interface from a display device to access the electronic patient medical record, 
 use the at least one relay interface to request the electronic patient medical record from the second server causing the second server to convert the infusion pump data from the HL 7 format to a web-based format, 
 transmit the infusion pump data in the web-based format to the display device causing the display device to display the infusion pump data. 
   
     
     
         2 . The system of  claim 1 , wherein the infusion pump data is displayed by the display device in a time graph. 
     
     
         3 . The system of  claim 1 , wherein the infusion pump data includes an infusion rate. 
     
     
         4 . The system of  claim 1 , wherein the infusion pump data includes at least one of (i) a drug name of the fluid infused into the patient, (ii) a total amount of fluid infused into the patient, (iii) an amount of time remaining for the infusion treatment, (iv) an event associated with the infusion treatment, or (v) a drug limit for the infusion treatment. 
     
     
         5 . The system of  claim 1 , wherein the second server is configured to:
 determine an alarm based on the infusion pump data exceeding a threshold; and   transmit the alarm, via the first server, to at least one of the infusion pump or the display device.   
     
     
         6 . The system of  claim 1 , wherein the server is configured to:
 receive, in the first server for storage via the second server, a patient condition for relating to the infusion pump data; and   transmit, via the first server, a message including a notification indicative of the patient condition to at least one of the infusion pump or the display device.   
     
     
         7 . The system of  claim 1 , further comprising a dialysis machine communicatively coupled to the hospital network and configured to perform a dialysis treatment on the same patient, determine dialysis machine data related to the dialysis treatment, and transmit the dialysis machine data and the patient identifier in the HL 7 format to the hospital network,
 wherein the first server is configured to:   receive the dialysis machine data from the hospital network, and cause the second server to store the dialysis machine data is associated with the patient identifier in the HL 7 format to the electronic patient medical record,   cause the second server to convert the dialysis machine data from the HL 7 format to a web-based format in response to the request from the display device to access the electronic patient medical record, and   transmit the dialysis machine data in the web-based format to the display device causing the display device to display the dialysis machine data.   
     
     
         8 . The system of  claim 7 , wherein
 the infusion treatment includes a heparin infusion;   the dialysis machine data provides patient blood glucose data; and   the second server is configured to
 (i) use at least one heparin infusion protocol to determine whether an alert is to be generated as a result of new blood glucose data, 
 (ii) responsive to determining that an alert is to be generated in (i):
 (a) determine a titration volume to be delivered by the infusion pump for the infusion treatment, 
 (b) cause the first server to transmit a message including the alert to at least one of the infusion pump, the dialysis machine, or the display device, and 
 (c) cause the first server to transmit the determined titration volume to at least one of the infusion pump, the dialysis machine, or the display device. 
 
   
     
     
         9 . The system of  claim 7 , wherein the first server includes a first data listener interface configured to receive the infusion pump data and a second data listener interface configured to receive the dialysis machine data. 
     
     
         10 . The system of  claim 7 , wherein the first server is configured to communicate with at least one of the infusion pump, the dialysis machine, or the display device via a web service. 
     
     
         11 . The system of  claim 7 , wherein at least one of (i) the dialysis machine and the infusion pump are configured to perform their respective treatments concurrently, or (ii) the display device is caused to display the infusion pump data and the dialysis machine data concurrently. 
     
     
         12 . The system of  claim 1 , wherein the first server is configured as a gateway device. 
     
     
         13 . A networked patient care system comprising:
 an infusion pump communicatively coupled to a hospital network and configured to perform an infusion treatment on a patient, determine infusion pump data related to the infusion treatment, and transmit the infusion pump data in an HL 7 format to the hospital network;   a sensor communicatively coupled to the hospital network, the sensor configured to perform a measurement on the patient undergoing the infusion treatment and transmit data associated with the measurement to the hospital network;   a first server communicatively coupled to the infusion pump and the sensor via the hospital network; and   a second server communicatively coupled to the first server via a separate secure connection, the first server including at least one relay interface to enable display devices to access electronic patient medical records that are stored via the second server,   wherein the first server is configured to
 receive the infusion pump data from the hospital network, and cause the second server to store the infusion pump data in the HL 7 format to an electronic patient medical record, 
 receive the measurement data from the hospital network, and cause the second server to store the measurement data in the HL 7 format to the electronic patient medical record, 
 receive a request via the at least one relay interface from a display device to access the electronic patient medical record, 
 use the at least one relay interface to request the electronic patient medical record from the second server causing the second server to convert the infusion pump data and the measurement data from the HL 7 format to a web-based format, 
 transmit the infusion pump data and the measurement data in the web-based format to the display device and cause the display device to display the infusion pump data and the measurement data. 
   
     
     
         14 . The system of  claim 13 , wherein
 the sensor is configured to measure at least one hemodynamic monitoring parameter of the patient, and   the second server is configured to link the at least one hemodynamic monitoring parameter to the infusion pump data and generate at least one message including the infusion pump data in combination with the at least one hemodynamic monitoring parameter.   
     
     
         15 . The system of  claim 13 , wherein the sensor is configured to measure at least one vital sign of the patient. 
     
     
         16 . The system of  claim 15 , wherein the second server is further configured to:
 determine a change in the at least one vital sign;   determine infusion pump data that corresponds to the change in the at least one vital sign;   generate a notification using a script that includes an indication of the at least one change in the vital sign or the determined infusion pump data; and   transmit a message, via the first server, including the notification to the display device.   
     
     
         17 . The system of  claim 16 , wherein the first server is configured to transmit the message to at least one of the infusion pump or a vital sign monitor. 
     
     
         18 . The system of  claim 13 , wherein the web-based format includes at least one of an eXtensible Markup Language (“XML”), Javascript, or a HyperText Transfer Protocol (“HTTP”). 
     
     
         19 . A centralized hospital server apparatus comprising:
 a first interface configured to receive infusion pump data in an HL 7 format from an infusion pump, the infusion pump data related to an infusion treatment performed on a patient;   a second interface configured to receive dialysis machine data in the HL 7 format from a dialysis machine, the dialysis machine data related to a dialysis treatment performed on the same patient;   a third interface configured to receive a request message from a display device;   a fourth interface configured to communicatively couple to a second server via a separate secure connection, the second server configured to provide access to stored electronic patient medical records; and   a hardware processor communicatively coupled to the first interface, the second interface, and the third interface the hardware processor in communication with a memory storing instructions, which when executed, cause the hardware processor to
 cause the second server to store the infusion pump data and the dialysis machine data in the HL 7 format to an electronic patient medical record, 
 receive a request via the third interface from the display device to access the electronic patient medical record, 
 use the fourth interface to request the electronic patient medical record from the second server causing the second server to convert the infusion pump data and the dialysis machine data from the HL 7 format to a web-based format, and 
 transmit the infusion pump data and the dialysis machine data in the web-based format to the requesting display device and cause the display device to display the infusion pump data and the dialysis machine data. 
   
     
     
         20 . The apparatus of  claim 18 , wherein the memory includes instructions that when executed cause the hardware processor to validate operating parameters for the infusion pump that specify the infusion treatment.

Join the waitlist — get patent alerts

Track US2020023127A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.