MANAGEMENT OF DIALYSIS AND INFUSION DATA METHODS AND APPARATUS

• US 20160095976A1
• Filed: 10/02/2015
• Published: 04/07/2016
• Est. Priority Date: 01/29/2002
• Status: Abandoned Application

• Current Assignee: Baxter International Inc.
• Original Assignee: Baxter International Inc.
• Inventors: Simpson, Thomas L.C., Letellier, Laura M., Martucci, James P., Wilkes, Gordon J.
• Application Number:
  US14/873,960
• Publication Number:
  US 20160095976A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: A61M 1/14 Dialysis systems; Artificial kidneys; Blood oxygenators semi-permeable membranes characterised by the material, manufacturing processes therefor B01D71/00 ; Reciprocating systems for treatment of body fluids, e.g. single needle systems for hemofiltration or pheresis
• CPC Class Codes: A61M 1/1613 Profiling or modelling of patient or predicted treatment evolution or outcome
• CPC Class Codes: A61M 1/34 Filtering material out of the blood by passing it through a membrane, i.e. hemofiltration or diafiltration
• CPC Class Codes: A61M 2005/14208 with a programmable infusion control system, characterised by the infusion program
• CPC Class Codes: A61M 2205/18 with alarm
• CPC Class Codes: A61M 2205/33 Controlling, regulating or measuring
• CPC Class Codes: A61M 2205/3334 Measuring or controlling the flow rate
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/3584 using modem, internet or bluetooth
• CPC Class Codes: A61M 2205/50 with microprocessors or computers
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 2230/005 Parameter used as control input for the apparatus
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/172 electrical or electronic A61M5/16804, A61M5/16831 take precedence
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 20/40 relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
• CPC Class Codes: G16H 40/63 : for local operation
• CPC Class Codes: G16H 40/67 : for remote operation

Abstract

A networked patient care system includes an infusion pump communicatively coupled to a hospital network and configured to perform an infusion treatment on a patient, a dialysis machine communicatively coupled to the hospital network and configured to perform a dialysis treatment on the same patient, and a server communicatively coupled to the infusion pump and the dialysis machine via the hospital network. The server is configured to receive the infusion pump data, receive the dialysis machine, determine that the infusion pump data is related to the dialysis machine data, and determine a display device that is to receive the infusion pump data and the dialysis machine data. The server is further configured to transmit the infusion pump data and the dialysis machine data to the determined display device and cause the display device to display the infusion pump data and the dialysis machine data.

Claims

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, integrate a patient identifier associated with the patient within the infusion pump data, and transmit the infusion pump data and the patient identifier to the hospital network;

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, integrate the patient identifier within the dialysis machine data, and transmit the dialysis machine data and the patient identifier to the hospital network; and

a server communicatively coupled to the infusion pump and the dialysis machine via the hospital network and configured to;

receive the infusion pump data from the hospital network,

receive the dialysis machine data from the hospital network,

determine that the infusion pump data is related to the dialysis machine data based on the patient identifier,

determine a display device that is to receive the infusion pump data and the dialysis machine data, and

transmit the infusion pump data and the dialysis machine data to the determined display device and cause the display device to display the infusion pump data and the dialysis machine data.

2. The system of claim 1, wherein the infusion pump data and the dialysis machine data are each displayed by the display device in a time graph.

3. The system of claim 1, wherein the infusion pump data includes an infusion rate and the dialysis machine data includes an ultrafiltration 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 dialysis machine data includes at least one of (i) a dialysis fluid flow rate, (ii) a total amount of fluid removed from the patient, (iii) an amount of time remaining for the dialysis treatment, or (iv) an event associated with the dialysis treatment.

6. The system of claim 1, wherein the server is configured to:

determine an alarm based on at least one of the infusion pump data or the dialysis machine data exceeding a threshold; and

transmit the alarm to at least one of the infusion pump, the dialysis machine, or the display device.

7. The system of claim 1, wherein the server is configured to:

determine a patient condition based on the infusion pump data in conjunction with the dialysis machine data; and

transmit a message including a notification indicative of the determined patient condition to at least one of the infusion pump, the dialysis machine, or the display device.

8. The system of claim 1, wherein

the infusion treatment includes a heparin infusion;

the dialysis machine data provides patient blood glucose data; and

the 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) transmit a message including the alert to at least one of the infusion pump, the dialysis machine, or the display device, and

(c) 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 1, wherein the 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 1, wherein the 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 1, 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. A centralized hospital server apparatus comprising:

a first interface configured to receive infusion pump data from an infusion pump, the infusion pump data related to an infusion treatment performed on a patient and including a patient identifier;

a second interface configured to receive dialysis machine data from a dialysis machine, the dialysis machine data related to a dialysis treatment performed on the same patient and including the patient identifier;

a third interface configured to receive a request message from a display device, the request message associated with the patient and including the patient identifier; 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

determine the infusion pump data is related to the dialysis machine data based on the matching patient identifier, and

transmit the infusion pump data and the dialysis machine data to the requesting display device and cause the display device to display the infusion pump data and the dialysis machine data.

13. The apparatus of claim 12, wherein the memory includes instructions that when executed cause the hardware processor to validate (i) operating parameters for the infusion pump that specify the infusion treatment and (ii) operating parameters for the dialysis machine that specify the dialysis treatment.

14. The apparatus of claim 13, wherein the memory includes instructions that when executed cause the hardware processor to confirm that the operating parameters related to the infusion treatment in combination with the operating parameters related to the dialysis treatment will not create an adverse reaction in the patient.

15. The apparatus of claim 13, wherein the memory includes instructions that when executed cause the hardware processor to access an electronic medical record of the patient to compare patient physiological data in combination with (i) the operating parameters related to the infusion treatment and (ii) the operating parameters related to the dialysis treatment to one or more limit to determine whether the patient will experience an adverse reaction.

16. The apparatus of claim 13, wherein the memory includes instructions that when executed cause the hardware processor to perform drug-to-drug incompatibility by comparing a first substance specified in the operating parameters related to the infusion treatment to a second substance specified in the operating parameters related to the dialysis treatment.

17. 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, integrate a patient identifier associated with the patient within the infusion pump data, and transmit the infusion pump data and the patient identifier to the hospital network;

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, integrate the patient identifier within the dialysis machine data, and transmit the dialysis machine data and the patient identifier to the hospital network;

a sensor communicatively coupled to the hospital network via at least one of the infusion pump or the dialysis machine, the sensor configured to perform a measurement on the patient undergoing the infusion treatment and the dialysis treatment, and transmit data associated with the measurement to the hospital network; and

a server communicatively coupled to the infusion pump, the dialysis machine, and the sensor via the hospital network and configured to;

receive the infusion pump data from the hospital network,

receive the dialysis machine data from the hospital network,

receive the measurement data from the hospital network,

determine that the infusion pump data is related to the dialysis machine data and the measurement data,

determine a display device that is to receive the infusion pump data, the dialysis machine data, and the measurement data, and

transmit the infusion pump data, the dialysis machine data, and the measurement data to the determined display device and cause the display device to display the infusion pump data, the dialysis machine data, and the measurement data.

18. The system of claim 17, wherein

the sensor is configured to measure at least one hemodynamic monitoring parameter of the patient, and

the 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.

19. The system of claim 17, wherein the sensor is configured to measure at least one vital sign of the patient.

20. The system of claim 19, wherein the server is further configured to:

determine a change in the at least one vital sign;

determine at least one infusion pump data or dialysis machine 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, the determined infusion pump data, or the determined dialysis machine data; and

transmit a message including the notification to the display device.

21. The system of claim 20, wherein the server is configured to transmit the message to at least one of the infusion pump, the dialysis machine, and a vital sign monitor.

22. The system of claim 17, 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, the dialysis machine data, and the measurement data concurrently.