SYSTEM AND METHOD FOR ADMINISTERING A MEDICAL FLUID TO A PATIENT

20230041841 · 2023-02-09

    Inventors

    Cpc classification

    International classification

    Abstract

    A system for administering a medical fluid to a patient (P), comprises an infusion station (1) comprising a rack (10) and a control device (11), the rack (10) defining a multiplicity of slots (100), wherein the control device (11) is configured to synchronize reference patient data between infusion devices (2) attached to said multiplicity of slots (100), said reference patient data relating to a patient (P) to be administered with a medical fluid using the infusion station (1), and a new infusion device (2A) to be attached to one of said multiplicity of slots (100) of the rack (10). The control device (11) herein is configured, on the occasion of attaching the new infusion device (2A) to one of the multiplicity of slots (100) of the rack (10), to receive, from the new infusion device (2A), device patient data defined on the new infusion device (2A), and to update said reference patient data based on the device patient data dependent on an infusion status of the new infusion device (2A) and on an infusion status of the infusion station (1).

    Claims

    1. A system for administering a medical fluid to a patient, comprising: an infusion station comprising a rack and a control device, the rack defining a multiplicity of slots, wherein the control device is configured to synchronize reference patient data between infusion devices attached to said multiplicity of slots, said reference patient data relating to a patient to be administered with a medical fluid using the infusion station, and a new infusion device to be attached to one of said multiplicity of slots of the rack, wherein the control device is configured, on an occasion of attaching the new infusion device to one of the multiplicity of slots of the rack, to receive, from the new infusion device, device patient data defined on the new infusion device, and to update said reference patient data based on the device patient data dependent on an infusion status of the new infusion device and on an infusion status of the infusion station.

    2. The system according to claim 1, wherein the control device is configured to identify a connection event on the occasion of attaching the new infusion device to one of the multiplicity of slots of the rack, and to update said reference patient data based on the device patient data subsequent to the connection event.

    3. The system according to claim 1, wherein the new infusion device is configured to transfer said device patient data to the control device on the occasion of attaching the new infusion device to one of the multiplicity of slots of the rack.

    4. The system according to claim 1, wherein the control device is configured to synchronize the updated reference patient data between the infusion devices attached to said multiplicity of slots.

    5. The system according to claim 1, wherein the infusion status of the new infusion device is indicative of whether the new infusion device is currently carrying out an infusion operation.

    6. The system according to claim 1, wherein the infusion status of the infusion station is indicative of whether at least one of the infusion devices attached to said multiplicity of slots is currently carrying out an infusion operation.

    7. The system according to claim 1, wherein the control device is configured to set the reference patient data to the device patient data dependent on the infusion status of the new infusion device and on the infusion status of the infusion station.

    8. The system according to claim 1, wherein the control device is configured to set the reference patient data to the device patient data if the infusion status of the new infusion device indicates that the new infusion device is currently carrying out an infusion operation, and if in addition the infusion status of the infusion station indicates that none of the infusion devices attached to said multiplicity of slots is currently carrying out an infusion operation.

    9. The system according to claim 1, wherein the control device is configured to not update said reference patient data if the infusion status of the new infusion device indicates that the new infusion device is currently not carrying out an infusion operation, or if the infusion status of the infusion station indicates that at least one of the infusion devices attached to said multiplicity of slots is currently carrying out an infusion operation.

    10. The system according to claim 1, wherein the control device is configured to transfer said reference patient data to the new infusion device if the infusion status of the new infusion device indicates that the new infusion device is currently not carrying out an infusion operation, or if the infusion status of the infusion station indicates that at least one of the infusion devices attached to said multiplicity of slots is currently carrying out an infusion operation.

    11. The system according to claim 1, wherein the new infusion device is configured, in case the new infusion device is currently carrying out an infusion operation, to initiate a conflict workflow for adjusting at least one parameter of the infusion operation according to the reference patient data.

    12. The system according to claim 11, wherein the new infusion device is configured, within the conflict workflow, to adjust at least one parameter of the infusion operation upon a user confirmation.

    13. A method for administering a medical fluid to a patient, comprising: providing an infusion station comprising a rack and a control device, the rack defining a multiplicity of slots, wherein the control device is configured to synchronize reference patient data between infusion devices attached to said multiplicity of slots, said reference patient data relating to a patient to be administered with a medical fluid using the infusion station, and attaching a new infusion device to one of said multiplicity of slots of the rack, wherein the control device, on an occasion of attaching the new infusion device to one of the multiplicity of slots of the rack , receives, from the new infusion device, device patient data defined on the new infusion device, and updates said reference patient data based on the device patient data dependent on an infusion status of the new infusion device and on an infusion status of the infusion station.

    Description

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

    [0031] FIG. 1 shows a schematic drawing of an infusion station at the bedside of a patient;

    [0032] FIG. 2 shows a view of an embodiment of an infusion station;

    [0033] FIG. 3 shows a schematic diagram of the interaction of a control device and an infusion device of an infusion station;

    [0034] FIG. 4 shows an interaction chart for the communication in between an infusion device and a control device of an infusion station during the programming of an infusion operation by a user, in a situation in which the infusion station is not infusing;

    [0035] FIG. 5 shows an interaction chart for the communication between an infusion device and a control device of an infusion station during the programming of an infusion operation by a user, in a situation in which the infusion station is already infusing; and

    [0036] FIG. 6 shows a flow diagram for the synchronization of patient data in between an infusion device and a control device of an infusion station when attaching the infusion device to the infusion station.

    [0037] FIG. 1 shows a schematic drawing of an infusion station 1 at the bedside of a patient P, for example in a healthcare environment, such as in an intensive care unit (ICU) of a hospital.

    [0038] As visible from FIG. 1 in view of FIG. 2, the infusion station 1 comprises a rack 10 defining a multiplicity of slots 100 to which a multiplicity of infusion devices 2 may be attached. The rack 10, at the slots 100, provides for a mechanical and electrical connection for the infusion devices 2, the rack 10 serving as a communication link as well as a power supply such that the infusion devices 2 connected to the rack 10 are interconnected with each other and further are connected to a power supply via the rack 10.

    [0039] The rack 10 comprises a control device 11 which, as schematically shown in FIG. 3, comprises a memory device 110 and a processing device 111 and hence comprises electronic circuitry for controlling operation of the infusion station 1. The control device 11 in particular provides for a connection to a hospital information system 4, such that via the control device 11 data may be transferred to and may be received from the hospital information system 4.

    [0040] In particular, the control device 11 may be configured to send infusion data resulting from infusion operations carried out by infusion devices 2 of the infusion station 1 to the hospital information system 4. Alternatively or in addition, the control device 11 may be configured to receive configuration data, such as drug library data, from the hospital information system 4.

    [0041] In addition, a nurse call system and a reading device such as a barcode reader or the like may be connected to the control device 11.

    [0042] Alternatively or in addition, the control device 11 may be configured to control operation of the infusion devices 2 connected to the rack 10, for example for carrying out infusion operations in a concerted fashion, such as within a medical protocol for a multichannel infusion.

    [0043] The rack 10 together with the control device 11 and the infusion devices 2 arranged thereon is connected to a stand 3 placed at the bedside of a patient P, as visible from FIG. 1. The rack 10 holds the infusion devices 2 connected thereto in an organized fashion, forming a vertical stack of infusion devices 2.

    [0044] The infusion station 1 in addition comprises an interface device 12, also denoted as therapy manager, which is functionally connected to the control device 11 - as indicated in FIG. 3 - and comprises an input device 120 and a display 121. The interface device 12 is configured to output information about infusion operations carried out by infusion devices 2 of the infusion station 1. In addition, a user may enter information into the input device 120 for example for programming infusion operations of the infusion station 1.

    [0045] As visible from FIG. 2, the infusion devices 2 may be configured as syringe infusion pumps or as volumetric (peristaltic) infusion pumps. In either case, the infusion devices 2 may comprise a housing 20, an input device 21 for example in the shape of a rotary knob and/or a keypad or the like for inputting data into the respective infusion device 2, for example for programming an infusion operation, and a display 22 for outputting information, for example relating to an ongoing infusion operation.

    [0046] Referring again to FIG. 3, each infusion device 2 may comprise a memory device 23 for storing information and a processing device 24 for controlling operation of the infusion device 2.

    [0047] The infusion devices 2 arranged on the rack 10 of the infusion station 1 may be configured to individually or together in a multichannel operation perform infusions on a patient P to which the infusion station 1 is assigned. Herein, each infusion station 1 generally is assigned to a single patient P, the infusion devices 2 hence being dedicated to the patient P for carrying out infusion operations on the patient P.

    [0048] When setting up an infusion operation on an infusion device 2, generally patient data, such as the patient’s age, weight, gender, body surface area, body mass index and the like, is taken into account for defining certain settings of the infusion operation. For example, within a drug library a variety of different drugs may be associated with a variety of different limits, for example relating to a flow rate, a dosage, a dose rate or the like, wherein the limits may depend on patient data, for example the patient’s age or the patient’s weight. In addition, whereas a flow rate generally is defined as a fluid volume per time administered to a patient (stated for example in ml/h), a dose rate (also denoted as infusion rate) takes into account pharmacokinetics and refers to a rate at which a drug should be administered to achieve a steady-state of a particular dose within e.g. a patient’s plasma compartment, the dose rate herein generally being computed by taking patient data, in particular the patient’s weight, into account.

    [0049] As the infusion station 1 with the infusion devices 2 connected to the rack 10 is assigned to a single patient, all infusion devices 2 of the infusion station 1 should use the same patient data. It hence is a task of the control device 11 to ensure that patient data, i.e. all data relating to the patient assigned to the infusion station 1, is synchronized in between the different infusion devices 2 attached to the rack 10 and the control device 11.

    [0050] Referring now to FIG. 4, in case a user U, such as a physician or a nurse, wishes to program an infusion operation on a particular infusion device 2A (step A1), the infusion device 2A sends a message to the control device 11 to inquire from the control device 11 whether a patient confirmation is required (step A2). The control device 11 responds to the request of the infusion device 2A by sending a response message indicating to the infusion device 2A whether a patient confirmation is required or not, which in the instant case is true (step A3). The infusion device 2A hence indicates to the user U to either confirm the patient data currently defined on the infusion station 1 or to define a new patient by entering new patient data (step A4).

    [0051] If the user U confirms the patient data as previously defined on the infusion station 1, the programming of the infusion operation takes place based on previously defined reference patient data as stored in the control device 11 (step A5).

    [0052] In the alternative, if the user U decides to create a new patient (step A6), the user U enters new patient data into the infusion device 2A, which is forwarded by the infusion device 2A to the control device 11 (step A7). In the control device 11, previously stored reference patient data is replaced by the patient data received from the infusion device 2A, upon which the control device 11 distributes the new reference patient data to all infusion devices 2, 2A connected to the rack 10 and hence being part of the infusion station 1 (steps A8, A9). Hence, the newly defined patient data, entered by the user U in step A6, is transferred to the control device 11, which distributes the patient data as new reference patient data to all infusion devices 2, 2A connected to the rack 10.

    [0053] An entering of new patient data on an infusion device 2A on which an infusion operation shall be programmed by a user U is possible, in one embodiment, if and only if the infusion station 1 is currently not infusing, i.e., none of the infusion devices 2 connected to the rack 10 other than the currently programmed infusion device 2A is currently infusing, that is if no infusion operation is currently carried out on the infusion station 1.

    [0054] If, in contrast, an infusion operation is carried out by one or multiple of the infusion devices 2 of the infusion station 1, no entering of a new patient and no replacement of the current reference patient data is admissible. Referring now to FIG. 5, if a user U in this case initiates a programming of an infusion device 2A (step B1), the infusion device 2A sends a message to the control device 11 to inquire whether a patient confirmation is required (step B2). In this case the control device 11 responds by a message indicating that no patient confirmation is required, the response message hence having the value FALSE (step B3). The user U hence is not allowed to enter a new patient, but may continue with programming an infusion operation on the infusion device 2A based on the previously defined reference patient data.

    [0055] Referring now to FIG. 6, upon attaching an infusion device 2A to a slot 100 of the rack 10 of the infusion station 1, a synchronization of patient data in between the infusion station 1 and the newly attached infusion device 2A must take place, as patient data defined on the infusion device 2A may differ from reference patient data defined in the control device 11 and previously attached infusion devices 2 of the infusion station 1. The synchronization herein takes place substantially immediately following the attachment of the infusion device 2A to the infusion station 1, and shall involve a minimum number of user interactions in order to obtain an easy, fast and comfortable synchronization procedure.

    [0056] FIG. 6 shows a flow chart for performing a synchronization procedure of patient data involving the newly attached infusion device 2A and the control device 11 of the infusion station 1.

    [0057] If an infusion device 2A is newly attached to a slot 100 of the rack 10 of the infusion station 1 (step C1 in FIG. 6), a connection event is identified at the control device 11 (step C2) such that the control device 11 becomes aware of the infusion device 2A having been connected to the rack 10. Following the connection event in step C2, the control device 11 checks whether the infusion station 1 is currently infusing (step C3). For this, the control device 11 examines whether one or multiple of the infusion devices 2 which previously had been connected to the rack 10 are currently carrying out an infusion operation.

    [0058] If the infusion status of the infusion station 1 indicates that the infusion station 1 is currently not infusing, the control device 11 in step C4 receives device patient data from the infusion device 2A. In step C5 it is checked whether the infusion device 2A is currently carrying out an infusion operation. If this is the case, it is assumed that the device patient data should have priority over the previously stored reference patient data as defined in the control device 11, such that the device patient data replaces the reference patient data as previously stored in the control device 11 and hence becomes the new reference patient data (step C6).

    [0059] If it in step C3 is found that the infusion station 1 is in an infusing state, i.e., one or multiple of the infusion devices 2 already previously connected to the rack 10 are carrying out an infusion operation, it is assumed that the reference patient data as previously stored in the control device 11 should have priority over device patient data which possibly is stored on the newly attached infusion device 2A, such that the reference patient data as previously stored in the control device 11 is maintained (step C7).

    [0060] In step C8, the now present reference patient data, which may correspond to the updated reference patient data of step C6 or the previous reference patient data of step C7, is synchronized to all infusion devices 2, 2A connected to the rack 10 of the infusion station 1, such that all infusion devices 2, 2A receive the now valid reference patient data (step C9). This includes also the newly attached infusion device 2A, such that it is made sure that in any case all infusion devices 2, 2A are synchronized with the same reference patient data.

    [0061] The process thereupon ends in step C10.

    [0062] In case of attaching a new infusion device 2A to the infusion station 1, hence a synchronization procedure takes place which synchronizes the patient data between all infusion devices 2, 2A connected to the infusion station 1. Herein, dependent on an infusion status of the new infusion device 2A and an infusion status of the infusion station 1 including all previously connected infusion devices 2 are taken into account to determine whether the device patient data as stored on the new infusion device 2A or the reference patient data as previously defined in the control device 11 should be given priority. In any case, at the end of the synchronization procedure all infusion devices 2, 2A are set to the same reference patient data and hence make use of the same reference patient data for example for defining an infusion operation.

    [0063] In the flow diagram of FIG. 6 the reference patient data as previously defined in the control device 11 is always given priority if the infusion station 1 is in an infusing state, i.e. one or multiple of the infusion devices 2 previously connected to the infusion station 1 are currently infusing. If the infusion station 1 is in an infusing state, the reference patient data as previously defined is maintained, independent on whether the new infusion device 2A is infusing or not.

    [0064] If, in this case, the new infusion device 2A is infusing, reference patient data as previously defined in the control device 11 is transferred to the new infusion device 2A, causing an updating of the patient data as defined in the infusion device 2A. This may give rise to a conflict with the ongoing infusion operation on the infusion device 2A, upon which a conflict workflow may be carried out on the infusion device 2A. During the conflict workflow, a user U may be asked for a confirmation for an adaption of parameters of the infusion operation, for example for a confirmation of an adapted flow rate or an adapted dose rate.

    [0065] The idea underlying the invention is not limited to the embodiments described above, but may be implemented in a different fashion.

    [0066] Reference patient data may relate to a specific patient currently treated by an infusion station. Reference patient data however may also refer to a generic, default patient, assuming some average, standard values for the patient, for example the patient’s weight.

    [0067] It is conceivable that multiple racks are present within an infusion station and are associated with a single control device for controlling the racks and the infusion devices arranged thereon. Synchronization of patient data herein may be effected by a single control device associated with the multiple racks for all infusion devices arranged on the racks.

    LIST OF REFERENCE NUMERALS

    [0068] 1 Infusion station [0069] 10 Rack [0070] 100 Slot [0071] 11 Control device [0072] 110 Memory device [0073] 111 Processing device [0074] 12 Interface device [0075] 120 Input device [0076] 121 Display [0077] 2, 2A Infusion device [0078] 20 Housing [0079] 21 Input device [0080] 22 Display [0081] 23 Memory device [0082] 24 Processing device [0083] 3 Stand [0084] 4 Hospital information system [0085] A1-A9 Steps [0086] B1-B3 Steps [0087] C1-C10 Steps [0088] P Patient [0089] U User