SYSTEM FOR PROVIDING MULTIPLE INFUSIONS TO A PATIENT

Abstract

A system for providing multiple infusions to a patient (P), the system comprises a multiplicity of infusion devices (10) for administering a multiplicity of medical fluids through an infusion line (102) of an infusion set (103) to the patient (P), and a control device (2) for controlling the multiplicity of infusion devices (10). Herein, the control device (2) comprises a multiplex module (22) configured to multiplex the multiplicity of medical fluids for a multiplexed administration of the medical fluids through said infusion line (102) of the infusion set (103), the multiplex module (22) comprising a scheduling module (222) configured to define at least two packets, each packet comprising at least one medical fluid out of the multiplicity of medical fluids, and to arrange the at least two packets in a sequence for administration of the medical fluids of the at least two packets. In this way a system for providing multiple infusions to a patient is provided which allows for an efficient, yet reliable administration of multiple infusions while at the same time reducing the risks for errors. An advantage of multiplexing is reduction of the number of lumens with associated reduction of infection risks and discomfort.

Claims

1. A system for providing multiple infusions to a patient, the system comprising: a multiplicity of infusion devices for administering a multiplicity of medical fluids through an infusion line of an infusion set to the patient, and a control device for controlling the multiplicity of infusion devices, wherein the control device comprises a multiplex module configured to multiplex the multiplicity of medical fluids for a multiplexed administration of the medical fluids through said infusion line of the infusion set, the multiplex module comprising a scheduling module configured to define at least two packets, each packet comprising at least one medical fluid out of the multiplicity of medical fluids, and to arrange the at least two packets in a sequence for administration of the medical fluids of the at least two packets.

2. The system according to claim 1, wherein at least one packet of the at least two packets comprises at least two medical fluids to be administered to the patient in parallel.

3. The system according to claim 1, wherein the multiplex module comprises an analyzing module configured to determine, using information obtained from a database, whether medical fluids of the multiplicity of medical fluids are compatible for administration to the patient in parallel, wherein the scheduling module is configured to group at least two compatible medical fluids together to define a packet.

4. The system according to claim 1, wherein the scheduling module is further configured to obtain, from a database, information relating to permissible interruption times of the medical fluids of the at least two packets.

5. The system according to claim 4, wherein the scheduling module is further configured to define, for each packet, a packet interruption time.

6. The system according to claim 5, wherein the packet interruption time is determined as a lowest of the permissible interruption times of the medical fluids of the packet.

7. The system according to claim 5, wherein the scheduling module is further configured to determine a duration of each packet based on an administration time assigned to at least one medical fluid of the packet and/or a permissible interruption time assigned to at least one medical fluid of another packet.

8. The system according to claim 7, wherein the scheduling module is further configured to determine a utility value for the sequence based on the durations of the packets and the interruption times of the packets.

9. The system according to claim 8, wherein the utility value is determined according to the following formula: $U=\underset{1=1}{\overset{n}{.Math.}}.Math.\frac{D_i}{P_i}$ wherein U is the utility value, D.sub.i is the duration of the i-th packet out of n packets, and P.sub.i is the time period of the i-th packet in which the i-th packet will be scheduled at least once, derived from the duration of the i-th packet and the interruption time of the i-th packet.

10. The system according to claim 8, wherein the scheduling module is further configured to suggest to remove at least one medical fluid from at least one packet if the utility value exceeds a threshold.

11. The system according to claim 7, wherein the scheduling module is further configured to assign a flow rate to each of the medical fluids assigned to the at least two packets based on the duration of the packet to which the medical fluid is assigned.

12. The system according to claim 1, wherein the scheduling module is further configured to assign a priority to each packet based on an administration deadline of a medical fluid of the packet, and placing the packets in the sequence according to their priority.

13. The system according to claim 1, wherein the scheduling module is further configured to place a separator fluid in between two neighbouring packets for separating the administration of the medical fluids of the two neighbouring packets from each other.

14. The system according to claim 1, wherein the control device is configured to control the multiplicity of infusion devices for administering the sequence of packets of medical fluids to the patient.

15. A method for providing multiple infusions to a patient, the method comprising: controlling, using a control device, a multiplicity of infusion devices for administering a multiplicity of medical fluids through an infusion line of an infusion set to the patient, and multiplexing, in a set-up phase, using a multiplex module of the control device, the multiplicity of medical fluids for a multiplexed administration of the medical fluids through said infusion line of the infusion set in that the multiplex module defines at least two packets, each packet comprising at least one medical fluid out of the multiplicity of medical fluids, and arranges the at least two packets in a sequence for administration of the medical fluids of the at least two packets.

Description

[0044] The idea underlying the invention shall subsequently be described in more detail according to the embodiments shown in the figures. Herein:

[0045] FIG. 1 shows a schematic drawing of a scenario as it can be found at the bedside of a patient in a hospital environment, for example in an intensive care unit;

[0046] FIG. 2 shows a schematic view of an arrangement of multiple infusion devices for administering multiple medical solutions to a patient;

[0047] FIG. 3 shows a schematic functional drawing of a control device for controlling multiple infusion devices;

[0048] FIG. 4 shows a flow chart during a setup of multiple infusion devices for administering multiple medical solutions;

[0049] FIG. 5 shows a flow chart of a subsequent step during the setup of the multiple infusion devices;

[0050] FIG. 6 shows a flow chart of a subsequent step during the setup of the infusion devices; and

[0051] FIG. 7 shows an example of a sequence of packets of multiple medical solutions for administration to a patient.

[0052] Referring to the schematic view of FIG. 1, in a hospital environment multiple infusion devices 10 may be arranged at the bedside of a patient P for administering multiple medical solutions to the patient P. A scenario of this kind may for example be found in a critical care unit of a hospital, for example an intensive care unit, wherein the orchestrated, coordinated administration of multiple medical solutions to the patient P may be critical to sustain the patient's constitution.

[0053] The infusion devices 10, for example in the form of volumetric (peristaltic) or syringe infusion pumps, may for example be arranged on a rack 11, which is constituted to mechanically hold the infusion devices 10 in an organized fashion and to provide a communication backbone in between the infusion devices 10, also connecting the infusion devices 10 to an external communication network, for example a hospital network.

[0054] The rack 11 is arranged on a stand 12 and in this way is physically placed at the bedside of the patient P.

[0055] In the instant scenario, the infusion devices 10 are controlled by a control device 2 being linked for example to the rack 11 and via the rack 11 to the infusion devices 10 by means of a communication link 20, for example a wired link or a wireless link. The control device 2 may be implemented for example on a computing device, such as a personal computer, a tablet computer, a laptop computer, a mobile device such as a smart phone, or the like. The control device 2 may be a dedicated physical entity, or alternatively may be implemented by software on a multipurpose computing device.

[0056] Within the instant context, the control device 2 controls the infusion devices 10 for an orchestrated infusion of multiple medical solutions. Herein, as illustrated in FIG. 2, the infusion devices 10A, 10B, 100, 10D, 10E, 10N may be connected to a connection device 101 via the delivery lines 100A, 100B, 100C, 100D, 100B, 100N, the connection device 101 for example comprising switchable valves for switching between infusions of the different infusion devices 10A, 10B, 100, 10D, 10E, 10N for delivery via a single infusion line 102 connected to the patient P. Hence, multiple infusions of the multiple infusion devices 10A, 10B, 100, 10D, 10E, 10N may be applied to the patient P via a single infusion line 102 having a single lumen and providing single access to the patient P.

[0057] Referring now to FIG. 3, the control device 2, in one embodiment, comprises a communication module 21 for communicating to the infusion devices 10 and for communicating for example to a patient data management system (PDMS) 23 of the hospital. The communication module 21 may be configured for a wired communication via a wired network connection, or for a wireless communication for example according to the WiFi or the Bluetooth standard. Via the communication module 21 information may be received from the infusion devices 10 or the patient data management system 23, and commands may be issued for example to the infusion devices 10 for controlling their operation.

[0058] The control device 2 furthermore comprises a multiplex module 22 which serves to multiplex the administration of multiple medical solutions to the patient P. The multiplex module 22, which may be a separate physical entity or which may be implemented by software including all its components within a computing device implementing the control device 2, comprises a (graphical) user interface 220 via which a user N, for example a nurse, may interact with the control device 2 and may input control commands, such as information relating to medical solutions to be infused to a patient P.

[0059] The multiplex module 22 furthermore comprises a scheduling module 222 which serves to define packets of medical solutions to be administered in parallel to the patient P and to arrange the packets in a sequence for the administration to the patient P, as shall be in more detail described below.

[0060] An analyzing module 221 serves to analyze compatibilities/incompatibilities between the different medical solutions and provides its input in particular to the scheduling module 222 for defining packets of medical solutions.

[0061] A layout module 223 contains information relating to the layout of a tubing set 103 comprising delivery lines 100A, 100B, 100C, 100D, 100E, 100N, the connection device 101 and the infusion line 102 as illustrated in FIG. 2, the layout module 223 for example allowing a user N to define, input and/or modify the layout of the lines of the infusion set 103 such that the layout may be taken into account for controlling the infusion operation.

[0062] The control device 2 interacts with a database 24, which may be internal to the control device 2 and for this may be implemented for example on a computing device also implementing the control device 2. The database 24 alternatively may be external to the control device 2 and may for example be stored on a server within a hospital network, the control device 2 being in communication connection with the database 24 for example via a hospital information network.

[0063] As it is illustrated in FIGS. 4 to 6, the control device 2 serves to define a sequence of packets of medical solutions for a multiplexed administration of the medical solutions to the patient P, in a setup (programming) phase prior to the actual administration of the medical solutions to the patient P.

[0064] The process illustrated in FIGS. 4 to 6 serves to configure multiple infusion devices 10 for a multiplexed infusion of multiple medical solutions. At the start of the process, illustrated in FIG. 4, medical solutions are entered, for example by a user N, into the multiplex module 22 via for example the user interface 220 as input A, defining in the instant example five drugs, denoted as a drug A, drug B, drug C, drug D, and drug E.

[0065] When entering the different drugs into the control device 2, the user and may also indicate an initial programmed rate ID.sub.A, ID.sub.B, ID.sub.C, ID.sub.D, ID.sub.E for the administration of the different medical solutions.

[0066] Further to the definition of the different medical solutions, the multiplex module 22 takes as input from the external database 24 information with regard to the compatibilities/incompatibilities of the different medical solutions. The compatibilities/incompatibilities are for example defined in an association table stored in the database 24, the table defining whether a certain drug is compatible or incompatible with another drug, as illustrated in the bottom of FIG. 4.

[0067] In the example of FIG. 4, drug A is compatible with drug B, but is incompatible with drug C, drug D and drug E. This means, that drug A may be administered together with drug B, but may not be administered together with drug C, drug D and/or drug E, such that a sufficient separation of administration between drug A and drugs C, D and E must be provided. Likewise, drug B is compatible with drug A, but is incompatible with drug C, drug D and drug E. Drug C is incompatible with drugs A and B, but is compatible with drugs D and E. Drug D is incompatible with drug A and drug B, but is compatible with drug C and drug E. And drug E is incompatible with drug A and drug B, but is compatible with drug C and drug D.

[0068] Taking the input A and the compatibility/incompatibility information from the database 24, the multiplex module 22 defines packets of drugs which may be administered in parallel (i.e., synchronously) via a single infusion line. In the noted example, drugs A and B, which are compatible with each other, are grouped together in packet 1, whereas drugs C, D and E, which also are compatible with each other (but are incompatible with drugs A and B), are grouped together in packet 2 (output B).

[0069] In addition, during administration a separator fluid may have to be inserted in between the two packets in order to sufficiently separate the packets and their medical solutions from each other. The separator fluid may be a neutral fluid not containing a drug, such as a saline solution or a glucose solution, which may be administered, during the actual administration, using a dedicated infusion device 10N, as illustrated in FIG. 2. The separator fluid may also serve to flush the infusion line 102 in between the two packets during the actual administration.

[0070] Upon having defined the packets, which generally group drugs together for administration to the patient P, a sequence of the packets and their duration is determined, as this is illustrated in FIG. 5. Taking the general definition of the packets output in the step illustrated in FIG. 4 (output B) as input and obtaining as further input from the database 24 maximum permissible interruption times I.sub.A, I.sub.B, I.sub.C, I.sub.D, I.sub.E associated with the different drugs, durations for the different packets are determined.

[0071] Herein, for each packet a packet interruption time is determined as the smallest interruption time of the medical solutions grouped together in the packet. From the packet interruption time of the first packet the duration of the other, second packet is derived, the duration of the second packet (including the required duration for the separator fluid) being determined to correspond to the packet interruption time of the first packet, and vice versa.

[0072] The permissible interruption time of a medical fluid generally indicates for what maximum time period the administration of a medical solution may be interrupted without having a significant (disadvantageous) therapeutic effect. Hence, the packet interruption time indicates a permissible pause between two instances of a packet, which may be used for administering another packet of medical solutions.

[0073] The duration of administration of the separator fluid may be predefined, assuming for example a maximum flow rate and a minimum volume of separator fluid to provide for a sufficient separation. The actual duration available for administering the medical fluids of a packet, in the instant example comprising two packets, then will equal the packet interruption time of the other packet minus the duration of the administration of the separator fluid.

[0074] Having determined the durations of the packets, the general set up of a sequence of packets is obtained as output C, as illustrated in FIG. 5.

[0075] In a next step, a utility value is calculated for the sequence responding to output C, the utility value generally being calculated according to the following formula:

[00002]$U=\underset{i=1}{\overset{n}{.Math.}}.Math.\frac{D_i}{P_i},$

wherein U is the utility value, D.sub.i is the duration of the i-th packet out of n packets, and P.sub.i is the time period of the i-th packet in which the i-th packet will be scheduled at least once. P.sub.i is derived from the duration of the i-th packet and the interruption time of the i-th packet.

[0076] The utility value indicates the fraction of use of the single lumen infusion line 102 for administering the sequence of packets comprising the different medical solutions. A utility value smaller than or equal to 1 indicates that the sequence of packets may sequentially be administered using the single infusion line 102. A utility value larger than 1 indicates that more than one infusion line 102, i.e., more than one lumen, is required for administering the medical solutions to the patient.

[0077] The above formula as such does not take the separator fluid into account. If a separator fluid has to be inserted in between packets, the calculation of the utility value may take place using the following formula:

[00003]$U=\underset{i=1}{\overset{n}{.Math.}}.Math.\frac{D_i+D_{s.Math.e.Math.p}}{P_i-D_{s.Math.e.Math.p}},$

in which D.sub.sep indicates the duration of administration of the separator fluid in between the packets.

[0078] If, for the sequence determined as output C in the flow chart of FIG. 5, a utility value larger than 1 arises, the packets need to be redefined. For this, the medical solution having the smallest interruption time is removed from the associated packet and is indicated to the user N to be infused via a separate infusion line 102 (or another lumen of the same infusion line 102). After removal of the noted medical solution, the utility value is recalculated, potentially repeating the procedure until a utility value smaller than or equal to 1 is obtained, indicating that the now obtained sequence of packets may be administered to the patient using a single infusion line 102.

[0079] As illustrated in the flow chart of FIG. 6, the definition of the sequence of packets obtained as output C in FIG. 5 (after the optimization using the utility value) is taken as input in another step during which the flow rates of the medical solutions of the packets for the administration using the infusion devices 10 are determined. Herein, from the initial programmed rate and the known time of administration, the volume of administration for each medical solution is known (input D in the flow chart of FIG. 6). From the known volume of each medical solution and from the combined duration of the packets within a repetitive administration of the sequence of packets it hence can be derived with which flow rate each medical solution is to be administered during the duration of the associated packet, as this is schematically illustrated in FIG. 6 (output E).

[0080] The initial programmed rates for the medical solutions hence are adapted, the infusion devices 10 being controlled according to the newly calculated flow rates during the later administration of the medical fluids within the sequence of packets.

[0081] As further illustrated in FIG. 6, as further input to the determination of the flow rates it is taken into account what maximal flow rates are acceptable for the different medical solutions, which is taken from the database 24. It generally is checked whether the determined flow rate exceeds the maximum permissible flow rate. If this is not the case, the determined flow rate is acceptable. If this is the case, the definition of the sequence of packets needs to be adapted, such that it must be reverted to the step illustrated in FIG. 5 for redefining the packets and their durations.

[0082] As illustrated also in FIG. 6, during the actual administration the sequence of packets shall be repeated, in the instant example, twice for an overall duration of 60 minutes. After completion of the repeated administration of the sequence of packets hence all medical solutions are in their desired volume administered to the patient P.

[0083] Prior to or after determining the flow rate, the order of the packets in the sequence is determined. This is done according to priority scheme taking an administration deadline of the medical fluids in the packets into account. Herein, a medical solution having an early deadline generally has a high priority, the packet associated with the medical solution having the highest priority (the shortest administration deadline) being placed first in the sequence. The deadline indicates how soon the administration of the medical solution should start: A short deadline indicates that the administration should start early, whereas a long deadline indicates that it can potentially be waited with administering the medical solution.

[0084] In the noted example, if for example drug A has the highest priority of all drugs contained in the sequence of packets of medical solutions, packet 1 is placed first in the sequence, followed by separator fluid and then packet 2.

[0085] As a result, as illustrated in FIG. 7, a repetitive sequence of packets for administration to the patient P is defined. The administration of the sequence herein takes place periodically, for a predefined number of repetitions of the sequence, such that each packet is administered multiple times to the patient P.

[0086] During the actual administration, the control device 2 controls the infusion devices 10A, 10B, 100, 10D, 10E in the setup of FIG. 2 to administer drug A, drug B, drug C, drug D and drug E according to the defined sequence of packets and the calculated flow rates, wherein in between two packets of incompatible medical solutions a separator fluid via the infusion device 10N may be administered.

[0087] The invention is not limited to the embodiments described above, but may be implemented in an entirely different fashion.

[0088] Using the described approach, medical solutions may be grouped together in packets for a multiplexed, parallel administration, wherein different packets of (incompatible) medical solutions may be defined for a sequential administration. Because medical solutions are administered in parallel, one packet of medical solutions being followed by the other, an efficient administration of multiple medical solutions in a multiplexed fashion becomes possible, hence potentially shortening an overall administration time of medical solutions to a patient.

[0089] Because the determination of a sequence of packets of medical solutions takes place automatically according to constraints defined in the system, the risk for human errors is reduced, enabling a reliable, efficient, secure administration of a multiplicity of medical solutions to a patient.

[0090] Another advantage of the proposed multiplexing scheme is that infection risks may be lowered by reducing the number of infusion lumens.

LIST OF REFERENCE NUMERALS

[0091] 1 System [0092] 10, 10A-10E, 10N Infusion device [0093] 100, 100A-100E, 100N Delivery line [0094] 101 Connection member [0095] 102 Infusion line [0096] 103 Infusion set [0097] 11 Organization device (rack) [0098] 12 Stand [0099] 2 Control device [0100] 20 Communication connection [0101] 21 Communication module [0102] 22 Multiplex module [0103] 220 User interface [0104] 221 Analyzing module [0105] 222 Scheduling module [0106] 223 Layout module [0107] 23 Patient data management system [0108] 24 Database [0109] A-E Input/output [0110] F Flow [0111] N User (nurse) [0112] P Patient