Multiple fluid pumps delivering multiple fluids

Abstract

The fluid delivery system includes a fluid delivery controller and a plurality of fluid pumps. The plurality of fluid pumps includes a first fluid pump and a second fluid pump. A caregiver receives fluid delivery instructions specifying a schedule for delivering a plurality of different fluids to a recipient. To deliver the plurality of different fluids to the recipient, the caregiver assigns each of the plurality of fluid pumps to deliver a different fluid as specified by the fluid delivery instructions. One or more fluid delivery controllers control the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner specified by the schedule.

Description

[Background technology]

[0001] Conventional infusion pumps allow a caregiver to deliver fluids intravenously to a patient. For example, a physician first creates a medication order that specifies one or more fluid-based medications for delivery to a particular patient in a hospital. Typically, a pharmacy in the hospital receives such medication orders provided by the physician. In accordance with the medication order, the pharmacy dispenses the corresponding physical order by providing the medications to the caregiver for delivery to the respective patient.

[0002] In some instances, a medication order includes multiple fluid-based medications that need to be administered intravenously to each patient. In such instances, assuming that each of the fluid-based medications must be delivered by a separate fluid delivery system (fluid pump), the caregiver looking after the patient must locate multiple fluid delivery systems (fluid pumps) within the hospital. This in itself can be a difficult task, since hospitals may not have good visibility into medical equipment that is not in use.

[0003] Following locating the multiple fluid delivery systems, the caregiver must transport the fluid delivery systems to where the patient is located. At the patient's bedside, in accordance with the medication order information, the caregiver manually operates one or more fluid delivery systems to deliver the corresponding prescribed fluid-based medication intravenously to the patient. Each fluid pump must be individually programmed by the caregiver to administer the corresponding fluid intravenously to the patient.

[0004] Infusion devices are essential components in the delivery of infusion drugs, fluid formulations, and fluid hydration to patients, especially in complex and dangerous treatments such as chemotherapy that involve multiple infusion drugs and fluids delivered from multiple infusion devices in a specific sequence over a period of time.

[0005] Although protocols for fluid delivery therapies are often carefully defined from the outset, delivery of such therapies sometimes involves multiple interactions with infusion devices to ensure that the intended fluid therapy (infusate, infusate) is administered to the patient from different pumps in a timely manner. Each of these manual interactions introduces opportunities for clinicians to make mistakes, such as inadvertently changing the sequence of infusions, delivering the wrong medication at the wrong rate, or forgetting to administer one of the fluids or medications in the protocol. Additionally, each of these transitions is time consuming and can result in medication errors, delayed therapy, or extend the time required to administer the entire therapy. Summary of the Invention

[0006] Conventional techniques for intravenously delivering fluids to a patient suffer from a variety of deficiencies, including, as discussed above, the operations of managing the delivery of one or more fluids to a patient can be tedious and subject to fluid delivery errors.

[0007] As a specific example, assume that a caregiver needs to administer infusions of two different types of prescribed fluids to a corresponding patient. As discussed above, the caregiver must first retrieve one of the two fluid pumps to deliver each of the prescribed fluid-based medications. Each of the fluid delivery systems then needs to be configured or programmed to deliver one of the multiple prescribed fluids.

[0008] In some instances, to gain more knowledge about the various medications prescribed to the patient, and in terms of the specific details of how to administer the medications, the caregiver must log on to and provide input to a remote computer that is separate from the fluid pump. The remote computer is typically at least several feet away from the actual fluid pump that is configured to deliver the prescribed fluid to the patient. When administering multiple fluids to a patient, this means that, when administering multiple fluids to a patient, the caregiver must program (e.g., provide input to) at least three different devices, including the remote computer, the first fluid pump, and the second fluid pump, to complete the delivery of each medication order. Thus, the caregiver must provide input to three different user interfaces, none of which may recognize each other. The caregiver must be trained on how to use each of the user interfaces - the fluid pump user interface and the remote computer user interface.

[0009] Failure to properly deliver prescribed fluid-based medications to corresponding patients can be dangerous and potentially life-threatening. In contrast to conventional techniques, embodiments herein include a unique method for managing fluid delivery systems and associated data to facilitate delivery of fluids to recipients.

[0010] The present embodiments include the implementation of a unique fluid delivery schedule for delivering multiple fluids to a recipient in a timely manner via multiple fluid pumps. In one embodiment, the automated fluid delivery system allows a clinician (caregiver or other appropriate entity) to ensure that fluid medications are delivered to the right patient at the right time and in the correct sequence. The present embodiments also provide the ability to monitor the status of a therapy from a remote location and to pause the delivery at any point in the process.

[0011] As a more specific example, a fluid delivery system described herein includes a fluid management system (e.g., one or more controllers) and a plurality of fluid pumps. The plurality of fluid pumps includes any number of fluid pumps, such as a first fluid pump and a second fluid pump. The fluid delivery management system, such as a controller, receives fluid delivery instructions that specify a schedule for delivering a plurality of different fluids to a recipient. In response to receiving such instructions, the fluid delivery management system (controller) assigns each of the plurality of fluid pumps to deliver a different fluid as specified by the fluid delivery instructions. The fluid delivery management system (controller) then controls the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner as specified by the schedule.

[0012] The plurality of distinct fluids may include any number of fluids. In one embodiment, the plurality of distinct fluids may include a first fluid and a second fluid. The plurality of fluid pumps may include any number of fluid pumps. In one embodiment, the plurality of fluid pumps assigned to execute the fluid delivery instructions may include a first fluid pump and a second fluid pump.

[0013] In a further exemplary embodiment, the fluid delivery instructions indicate the timing of delivery of a second fluid from a second fluid pump relative to (versus) delivery of a first fluid from a first fluid pump.

[0014] According to further example embodiments, the first fluid pump provides notification of a triggering event, such as completion of delivery of the first fluid, to the second fluid pump, in accordance with a schedule. In such examples, notification of completion from the first fluid pump, or other suitable entity, triggers the second fluid pump to deliver the second fluid to a recipient.

[0015] Each of the plurality of fluid pumps optionally includes a display screen. In one embodiment, the first fluid pump includes a display screen that displays a visual notification. The displayed visual notification indicates a schedule for pumping one or more of the plurality of different fluids by each of the plurality of fluid pumps.

[0016] Further embodiments herein include displaying a notification on a display screen of a first fluid pump of the plurality of fluid pumps, the notification indicating a trigger condition in which a second fluid pump is scheduled to deliver a second fluid relative to the first fluid to a recipient.

[0017] According to a further exemplary embodiment, controlling the delivery of a plurality of different fluids from a plurality of fluid pumps in a manner as specified by a schedule includes distributing the schedule to each of the plurality of fluid pumps and synchronizing operation of the plurality of fluid pumps to a common clock, the fluid pumps operating collectively to provide the plurality of fluids to a recipient.

[0018] Further embodiments herein include receiving a schedule from a communication device operated by a caregiver, the caregiver creating the schedule to indicate timing for each of a plurality of fluid pumps to pump respective fluids to a recipient.

[0019] In one non-limiting exemplary embodiment, the plurality of different fluids includes a first fluid and a second fluid, as described above. The schedule indicates that the delivery of the second fluid to the recipient is conditional on the delivery of the first fluid to the recipient. For example, in one embodiment, the schedule indicates that the first fluid and the second fluid are delivered to the recipient sequentially, e.g., in quick succession. Alternatively, the fluid delivery schedule indicates that the first fluid and the second fluid are delivered to the recipient concurrently, where both the first fluid and the second fluid must be delivered at the same time.

[0020] Further embodiments herein include delivering the second fluid to the recipient after a predetermined delay following completion of delivery of the first fluid to the recipient, as specified by the schedule.

[0021] As discussed above, the plurality of fluid pumps may include a first fluid pump and a second fluid pump, and allocating the plurality of fluid pumps to execute the fluid delivery instruction includes, via input from a caregiver providing the fluid delivery instruction, i) selecting the first fluid pump to deliver a first fluid of the plurality of different fluids, and ii) selecting the second fluid pump to deliver a second fluid of the plurality of different fluids.

[0022] These and other more specific embodiments are described in greater detail below.

[0023] It should be noted that any of the resources described herein may include one or more computerized devices, fluid delivery systems, servers, base stations, wireless communication equipment, communication management systems, workstations, handheld or laptop computers, etc., to perform and / or support any or all of the method operations disclosed herein. In other words, one or more computerized devices or processors may be programmed and / or configured to operate as described herein to perform different embodiments of the present invention.

[0024] Yet another embodiment of the present application includes a software program for performing the steps and operations outlined above and disclosed in detail below. One such embodiment includes a computer program product including a non-transitory computer-readable storage medium (i.e., any physical computer-readable hardware storage medium) encoding software instructions for subsequent execution. The instructions, when executed in a computerized device (e.g., computer processing hardware) having a processor, programs the processor to perform or causes the processor to perform the operations disclosed herein. Such configurations are typically provided as software, code, instructions, and / or other data (e.g., data structures) configured or encoded on a non-transitory computer-readable storage medium such as an optical medium (e.g., CD-ROM), a floppy disk, a hard disk, a memory stick, etc., or on other media such as firmware, in one or more ROMs, RAMs, PROMs, etc., or as an application specific integrated circuit (ASIC), etc. Software or firmware or other such configurations may be installed on a computerized device to cause the computerized device to perform the techniques described herein.

[0025] Accordingly, embodiments herein are directed to methods, systems, computer program products, etc. that support the operations described herein.

[0026] One embodiment herein includes a computer readable storage medium and / or a system having instructions stored thereon that, when executed by computer processor hardware, cause the computer processor hardware to receive fluid delivery instructions specifying a schedule for delivering a plurality of different fluids to a recipient, assign a collection of a plurality of fluid pumps to execute the fluid delivery instructions for delivering the plurality of different fluids to the recipient, and control delivery of the plurality of different fluids from the plurality of fluid pumps in a manner as specified by the schedule.

[0027] The order of operations above has been provided for ease of understanding. It should be noted that any of the process steps described herein may be performed in any suitable order.

[0028] Other embodiments of the present disclosure include software programs and / or respective hardware to perform any of the steps and operations of the method embodiments outlined above and disclosed in detail below.

[0029] It should also be understood that the systems, methods, apparatus, instructions on a computer-readable storage medium, etc. described herein may be embodied strictly as a software program, firmware, as a mixture of software, hardware and / or firmware, or as hardware alone, such as within a processor, an operating system, or a software application.

[0030] As described herein, the techniques herein are well suited for managing and facilitating the use of medical devices, although it should be noted that embodiments herein are not limited to use in such applications, and the techniques described herein are well suited for other applications as well.

[0031] Also, it should be noted that although each of the different features, techniques, configurations, etc. herein may be described in different parts of this disclosure, it is contemplated that each of the concepts may optionally be practiced independently of one another or in combination with one another, where appropriate. Thus, the invention(s) described herein may be embodied and understood in many different ways.

[0032] It should also be noted that this introductory description of the embodiments herein does not intentionally identify each embodiment and / or incrementally inventive aspect of the present disclosure or the claimed invention. Rather, this brief description only presents general embodiments and corresponding portions of inventive steps over conventional techniques. For additional details and / or possible perspectives (permutations) of the present invention, the reader is directed to the Detailed Description portion and corresponding figures of the present disclosure, as further described below. [Brief description of the drawings]

[0033] [Figure 1] FIG. 2 is an exemplary diagram illustrating the management of fluid therapy delivery of multiple different fluids to a recipient from multiple fluid pumps in accordance with embodiments herein.

[0034] [Diagram 2] 1 is an example diagram illustrating the generation of fluid instructions and fluid delivery schedule information according to embodiments herein.

[0035] [Diagram 3] 1 is an example diagram illustrating the display of delivery status information related to the delivery of fluid therapy from multiple fluid pumps, according to an embodiment of the present application.

[0036] [Figure 4] 1 is an example diagram illustrating communication between multiple fluid pumps during fluid delivery, according to an embodiment of the present application. FIG.

[0037] [Diagram 5]1 is an example diagram illustrating the display of delivery status information related to the delivery of fluid therapy from multiple fluid pumps, according to an embodiment of the present application.

[0038] [Figure 6] 1 is an example diagram illustrating communication of messages related to fluid delivery, according to embodiments herein.

[0039] [Figure 7] 1 is an example diagram illustrating the display of delivery status information related to the delivery of fluid therapy from multiple fluid pumps, according to an embodiment of the present application.

[0040] [Figure 8] FIG. 1 is an example diagram illustrating a computer architecture for implementing one or more embodiments described herein.

[0041] [Figure 9] FIG. 2 is an exemplary diagram illustrating a method according to an embodiment of the present application.

[0042] The foregoing and other objects, features, and advantages of the present invention will become apparent from the following more particular description of the presently preferred embodiments, as illustrated in the accompanying drawings, in which like reference characters refer to like parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating embodiments, principles, concepts, and the like. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0043] The fluid delivery system includes a fluid management system (e.g., a single controller or multiple controllers) and a plurality of fluid pumps. The plurality of fluid pumps includes any number of fluid pumps, such as a first fluid pump and a second fluid pump. The fluid management system receives fluid delivery instructions that specify a plurality of different fluids for delivery to a recipient. In response to receiving the instructions, and according to generated schedule information, the fluid management system assigns each of the plurality of fluid pumps to deliver a different fluid as specified by the fluid delivery instructions. The schedule information distributed to the plurality of fluid pumps controls the delivery of the plurality of different fluids from the plurality of fluid pumps.

[0044] Accordingly, embodiments herein include methods, systems, etc. for delivering therapy, including multiple injections in a coordinated and synchronized manner across multiple independent injection devices and via one or more fluid pathways available on those devices.

[0045] It is further noted that one embodiment of the present application provides means for defining individual infusions associated with infusion therapy, defining when each of these infusions should be started, and optionally when they should be terminated or modified in support of such therapy, and defining the device and, optionally, the fluid pathway through which the infusions are delivered, and the event that triggers the start of each infusion.

[0046] Once initiated, a fluid therapy may be delivered, in part or in whole, between multiple infusion devices without the need for human interaction, reducing the chance of human error and streamlining the administration of the therapy. To accomplish this, in one embodiment, infusion devices are collocated near a common therapy to independently deliver specific infusions within the therapy in a synchronized manner while concurrently verifying proper execution of the therapy delivery being performed by the peer infusion device.

[0047] More specifically now, FIG. 1 is an example diagram illustrating the management of multiple fluid pump delivery to a recipient via multiple different fluid pumps, in accordance with embodiments herein.

[0048] Embodiments herein include systems and methods for delivering infusion therapy protocols in a coordinated manner via multiple independent infusion devices (fluid pumps 121, 122, 123, etc.) operated according to a delivery schedule.

[0049] As a more specific example, fluid delivery system 100 includes a plurality of fluid pumps. The plurality of fluid pumps may include any number of fluid pumps, such as fluid pump 121, fluid pump 122, fluid pump 123, and so on.

[0050] The fluid management system 126 (also known as a therapy definition manager) of the communication device 120 receives fluid instructions 105 specifying multiple fluids A, B, C, etc., and schedule information indicating the timing and corresponding rates at which the multiple different fluids A, B, C, etc. are to be delivered to the recipient 108.

[0051] In one embodiment, a caregiver 106, such as a doctor, nurse, etc., prescribes a fluid therapy for each of one or more fluids. The fluid management system 126 receives a fluid prescription 105 from a prescription integration engine 115 or other suitable entity.

[0052] For example, in response to receiving the fluid instruction 105 (including fluid instruction information), the caregiver 107 operates a fluid delivery management system 126 (e.g., a controller or other suitable entity) associated with the communication device 120 to assign the task of delivering a different fluid to each of a plurality of fluid pumps as specified by the fluid delivery instruction.

[0053] In one embodiment, the communication device 120 is located independently of the fluid pumps and the instruction management entity 119. However, it should be noted that the communication device 126 may be integrated into one or more of the fluid pumps 121, 122, 123, etc.

[0054] In a further exemplary embodiment, the caregiver 107 operates the communication device 120 to scan one or more labels associated with each of the fluids during allocation (e.g., label L1 affixed to fluid pump 121, label L2 affixed to fluid pump 120, label L3 affixed to fluid pump 123, etc.). In this manner, the communication device 120 and corresponding fluid management system 126 receive notification of the group of available fluid pumps that are needed to deliver the fluid therapy as specified by the fluid instruction 105.

[0055] In one embodiment, the received fluid instructions 105 specify a need to deliver multiple fluids including fluid type A, fluid type B, fluid type C, etc. The caregiver 107 or other suitable entity assigns each of the fluid pumps in the group (as created by the caregiver 107 or other suitable entity) to deliver each selected fluid as specified by the fluid instructions 115.

[0056] Assume that, via a fluid management system 126 running on the communication device 120, the caregiver 107 assigns (selects) fluid pump 121 to deliver fluid A to the recipient 108, the caregiver 107 assigns (selects) fluid pump 122 to deliver fluid B to the recipient 108, and the caregiver 107 assigns (selects) fluid pump 123 to deliver fluid C to the recipient 108. In one embodiment, the caregiver makes an association between each fluid pump and fluid based on input from the caregiver 107.

[0057] The caregiver 107 or fluid management system 126 also creates a schedule 160-1 (fluid delivery control information derived from the instructions 105 or newly generated by the caregiver 107, or a combination of both) indicating the timing of delivery of each of the fluids A, B, C, etc. associated with the instructions 105.

[0058] For example, assume that fluid management system 126 generates schedule information 160-1 to indicate the delivery of fluid A between time T1 and time T2, fluid management system 126 generates schedule information 160-1 to indicate the delivery of fluid B between time T3 and time T4, and fluid management system 126 generates schedule information 160-1 to indicate the delivery of fluid C between time T5 and time T6.

[0059] It should be noted that fluids may be delivered simultaneously, partially overlapping, one after the other, etc., according to schedule information 160-1.

[0060] As described above, in one embodiment, the fluid instruction 105 indicates the timing for pumping the second fluid B from the second fluid pump 122 based on the pumping of the first fluid A from the first fluid pump 121, and the fluid pumping instruction 105 indicates the timing for pumping the third fluid C from the third fluid pump 123 based on the pumping of the second fluid B from the second fluid pump 122.

[0061] The fluid management system 126 of the communication device 120 communicates schedule information 160-1 (aka delivery control information) which subsequently controls the delivery of multiple different fluids A, B, C, etc. from multiple fluid pumps 121, 122, 123, etc. according to appropriate schedules.

[0062] According to further exemplary embodiments, schedule information 160-1 indicates the contingencies of the delivery of the fluids relative to one another. For example, in one embodiment, schedule information 160-1 indicates that the delivery of a second fluid B to recipient 108 is contingent upon the completion of the delivery of a first fluid A to the recipient, and schedule information 160-1 indicates that the delivery of a third fluid C to recipient 108 is contingent upon the delivery of either the first fluid A or the second fluid B to recipient 108.

[0063] According to another example embodiment, schedule information 160-1 may be configured to indicate concurrent delivery of a first fluid A and a second fluid B to recipient 108.

[0064] It should be noted that, alternatively, schedule information 160-1 may be configured to indicate that the first fluid A and the second fluid B are to be delivered to the recipient 108 sequentially, e.g., one at a time, in the manner described above.

[0065] Further embodiments herein include delivering a second fluid B to the recipient 108 after a predetermined delay following completion of delivery of a first fluid A to the recipient 108 as specified by schedule information 160-1.

[0066] According to a further example embodiment, controlling the delivery of multiple different fluids A, B, C, etc. from multiple fluid pumps in a manner specified by schedule 160-1 includes distributing schedule information 160-1 to each of the multiple fluid pumps 121, 122, 123, etc., and synchronizing operation of each of the multiple fluid pumps to a common master clock.

[0067] In one embodiment, the communication device 120, the command management entity 119, or other suitable entity communicates the schedule information 160-1 to each of the fluid pumps 121, 122, 123, etc., via communication 161 over the network 190. Additionally or alternatively, the schedule information 160-1 is communicated via communication 161 to a first fluid pump, which communicates the schedule information 160-1 to the other fluid pumps in the group.

[0068] According to a further exemplary embodiment, fluid pump 121 includes a controller 141 that implements the delivery of fluid A in accordance with distributed schedule information 160-1, fluid pump 122 includes a controller 142 that implements the delivery of fluid B in accordance with distributed schedule information 160, and fluid pump 123 includes a controller 143 that implements the delivery of fluid C in accordance with distributed schedule information 160-1.

[0069] In one embodiment, each of the different controllers in an assigned group of fluid pumps receives the same schedule information 160-1 that provides the details or rules for the delivery of each of the fluids.

[0070] It should be noted that according to further exemplary embodiments, each of the controllers of fluid pumps 121, 122, 123, etc., are operative to communicate with each other, and possibly with instruction management entity 119 and communication device 120, regarding the status of the delivery of the respective fluids in accordance with fluid instructions 105. For example, controller 141 communicates with controllers 142 and 143 over a respective network or wireless communication link, controller 142 communicates with controllers 141 and 143 over a respective network, and controller 143 communicates with controllers 141 and 142 over a respective network.

[0071] As previously discussed, delivery of fluid B to the recipient may be conditional on delivery of fluid A. In one embodiment, the first fluid pump 121 and controller 141 provide notification of completion of delivery of the first fluid A to the controller 142 of the second fluid pump 122. In such an example, the notification between the controllers triggers the second fluid pump 122 to begin delivering the second fluid B to the recipient 108 in accordance with the schedule information 160.

[0072] As further shown, each of the multiple fluid pumps 121, 122, 123, etc. includes a display screen. For example, fluid pump 121 includes display screen 131, fluid pump 122 includes display screen 132, and fluid pump 123 includes display screen 133. Each of the display screens displays any suitable information related to the delivery of fluid.

[0073] In one embodiment, the first fluid pump 121 includes a display screen 131 that displays one or more visual notifications related to pumping fluid as specified by the fluid instructions 115. In one embodiment, the displayed visual notifications show schedule information 160-1 for the pumping of a plurality of different fluids by each of the plurality of fluid pumps. Similarly, each of the display screens 132, 133, etc. may be configured to display the respective schedule information 160-1.

[0074] Further embodiments herein include displaying a notification on one or more respective display screens, such as via one or more of display screens 131, 132, 133, indicating a triggering event in which a respective fluid pump is scheduled to deliver a corresponding fluid (via infusion) to a recipient based on another fluid being delivered by another fluid pump.

[0075] In a further exemplary embodiment, the group of fluid pumps assigned to execute the fluid instructions 105 operate autonomously. For example, as described above, each of the fluid pumps 121, 122, 123, etc. in the group receives the schedule information 160-1 (fluid delivery control information) over a communication link. The connections, such as the network 190, between the group of fluid pumps, the instruction management entity 119, the communication device 120, etc., may be prone to failure. In one embodiment, even if the group of fluid pumps cannot communicate with the instruction management entity 119 (e.g., a management server), the communication device 120, etc. over the network 190, the fluid pumps in the group still communicate with each other to execute their respective fluid instructions 115. In other words, each of the fluid pumps communicate with each other over one or more communication links that are independent of the communication over the network 190. In such an example, after the schedule information 160-1 is distributed to the fluid pumps, the fluid pumps communicate with each other to fulfill the fluid delivery instructions to the recipient as indicated by the schedule information 160-1.

[0076] Additional details about Fluid Therapy Offerings As previously discussed, environment 100 includes multiple components. For example, environment 100 includes an order integration engine 115 (e.g., hardware, software, or a combination of hardware and software) that receives and stores physician orders 101 related to a fluid therapy to be administered to a recipient 108, such as a patient. Environment 100 further includes a therapy definition manager (e.g., fluid management system 126 implemented as hardware, software, or a combination of hardware and software) that acts to configure how the fluid therapy should be delivered via a number of fluid pumps. In one embodiment, environment 100 further includes a database that is stored, such as in repository 180, that stores persistent information about the fluid therapy. Such information may include, but is not limited to, basic orders, means for delivering the fluid therapy, and the current status of the therapy and each associated infusion.

[0077] Environment 100 further includes a therapy service 118 (implemented as hardware, software, or a combination of hardware and software) that acts to facilitate the transfer of information between a therapy definition manager, a therapy repository, and infusion devices (a.k.a. fluid pumps 121, 122, 123, etc.).

[0078] It should be noted that the environment 100 and corresponding prescription management entity 119 further includes a therapy dashboard 170 that serves to remotely monitor the fluid therapy once it has begun.

[0079] As previously mentioned, environment 100 further includes intelligent infusion devices (such as fluid pumps 121, 122, 123, etc.), each of which includes one or more fluid delivery inlets for receiving fluid for delivery. In one embodiment, the fluid pumps (aka infusion devices) act to retrieve specific details for the delivery of fluid therapies from therapy service 118. As will be further described herein, through retrieved information, such as schedule information 160-1 from therapy service 118, the fluid pumps determine their individual roles in the delivery of multiple infusion therapies. The group of fluid pumps act collectively to deliver the appropriate infusions at the appropriate time and in the appropriate sequence to the recipient 108 (patient).

[0080] Additionally, as previously mentioned, embodiments herein include the use of physician orders 101, which are obtained from a networked order entry system or other networked repository for these orders. The Order Integration Engine 115 may obtain a single order for the entire fluid therapy, including the individual injections that exist as part of the fluid therapy, or the Order Integration Engine 115 may receive a collection of individual orders that may be associated with a therapy through the use of a therapy definition manager (such as the fluid management system 126). Upon receiving the orders, the Order Integration Engine 115 stores these orders in the therapy repository 180.

[0081] In a further exemplary embodiment, as discussed above, the therapy definition manager (e.g., fluid management system 126) implements functionality for identifying the recipient patient, the infusion devices (fluid pumps) and infusates (i.e., infusion medications and fluid mixtures) associated with the fluid therapy, and the predetermined sequence in which the infusates should be delivered according to the schedule information. It should be noted that any suitable method may be used to identify each fluid pump, including manual entry of an identifier or via scanning a bar code or ID tag associated with each fluid pump.

[0082] Once a patient (e.g., recipient 108) is identified via instructions, the therapy definition manager (e.g., fluid management system 126) retrieves all outstanding instructions associated with the patient (a.k.a., recipient 108) from the therapy repository 180 and provides these instructions to the caregiver 107 (user) on the display screen 130 of the communication device 120.

[0083] It should be noted that instructions may exist for a particular therapy and may include sub-instructions that include one or more infusion instructions, and separate instructions may exist for the infusion itself.

[0084] The therapy definition manager (fluid management system 126), after retrieval of instructions 105 and corresponding information, implements functionality to select instructions (as specified by fluid instructions 105) related to the fluid therapy to be administered to the recipient 108, and incorporates these instructions into an injection sequence that reflects how the therapy should be delivered. In one embodiment, if desired, the therapy definition manager (fluid management system 126) implements functionality to hide any instructions that are not related to a therapy.

[0085] For each infusion (e.g., fluid type A, B, C, etc.) associated with the fluid order 105, the therapy definition manager (fluid management system 126) defines program settings for corresponding fluid pumps 121, 122, 123, etc., such as infusion devices, and the events that initiate infusions on those fluid pumps. The therapy definition manager (fluid management system 126) implements functionality for scanning bar codes and / or other identification tags for the infusates and using this information to verify that the scanned information matches the selected medication order.

[0086] Using the Instructions 105 details for each infusion (A, B, C, etc.), the Therapy Definition Manager (Fluid Management System 126) obtains a set of program settings and provides them to the caregiver 107. The caregiver 107 has the option to change these settings or accept them as is. These settings may include, but are not limited to, the composition or concentration of the drug in the fluid source, the dose, dose rate, rate, amount to be infused, and duration of the infusion.

[0087] In one embodiment, each infusion in a therapy must have a triggering event that starts each infusion. This may include clicking start on the infusion device, the expiration of a delay timer, the clock on the device reaching a particular time, the start or end of another infusion defined as part of the therapy, the occurrence of an alarm that occurs during the administration of another infusion defined as part of the therapy, or some other event message delivery from the Therapy Service 118 or another infusion device (fluid pump) that is scheduled in the delivery of the therapy. The Therapy Definition Manager (Fluid Management System 126) provides the means to define this triggering event and, optionally, a delay that is built in between the triggering event and the start of the infusion on the selected fluid pump.

[0088] To transmit the program settings to each infusion device, the infusion device is first identified. The Therapy Definition Manager (Fluid Management System 126) implements functionality to identify the fluid pump (infusion device) in a variety of ways. Such methods include, but are not limited to, entering the device's serial number, scanning a barcode on the device, or scanning some other ID tag located on or within the device. As previously mentioned, in one embodiment, the communication device includes a scanner 157 that scans the respective labels L1, L2, L3, etc.

[0089] As previously discussed, a caregiver 107 or other suitable entity assigns respective fluids to fluid pumps according to instructions 105. Assignment refers to the allocation of a fluid pump to deliver an identified fluid.

[0090] After the fluid pumps are identified and the schedule information 160-1 is generated, the Therapy Definition Manager communicates the programming (e.g., schedule information 160-1) to each of the infusion devices (fluid pumps). Programming refers to the allocation of fluids to each fluid pump. In this way, the receiving fluid pump can identify the particular fluid it is about to deliver to the recipient, and when or under what circumstances to deliver the particular fluid.

[0091] More specifically, each respective receiving fluid pump programs itself with program settings, infusate information, patient identifier, and triggering events (such as the circumstances under which the delivery of each fluid begins.) Once programmed, the infusion device (fluid pump) is set up to deliver the infusate (fluid type) in a particular sequence with respect to other infusates administered as part of the fluid therapy.

[0092] The process of defining the details of each infusion in the therapy may continue until the entire fluid therapy is defined. At any time, the infusion device may begin administering an infusion. Similarly, additional medications may be added, or any infusions already defined may be modified or removed from the therapy.

[0093] Check your therapy setup It should be noted that in one embodiment, a copy of the fluid pump identities and corresponding fluid pump settings are maintained in the therapy repository 180. As each infusion begins, the status of such infusion is also maintained in the repository via communication from each fluid pump delivering fluid to the order management entity 119 over the network 190. Through access to the information stored in the repository 180, the caregiver 107 may optionally review the status and details of the therapy definition process via a therapy definition manager (manager 126).

[0094] In one non-limiting exemplary embodiment, the Therapy Definition Manager (126) includes the functionality to command already programmed infusion devices (fluid pumps) to display their specific details, such as the order in which infusions should occur, the events that trigger the start of an infusion, and the infusion program settings themselves. In one embodiment, each fluid pump includes a display screen to show the corresponding details for review by the caregiver 107.

[0095] It should be noted that multiple infusions may be delivered, partially or entirely, from the same infusion device and fluid pathway. For example, an infusion device may have a large source container of fluid that is partially delivered between administrations of medications from multiple fluid pumps. More specifically, in one non-limiting exemplary embodiment, 33% of a particular type of fluid may be delivered after administration of each of three medications.

[0096] Synchronized injection delivery It is further noted that the fluid pumps may be configured to discover each other on a local wired or wireless network and to establish peer-to-peer group messaging directly with each other. For example, each of the fluid pumps may be configured to send a discovery request to learn about other fluid pumps in the vicinity. The other pumps respond to such discovery requests, indicating their presence and availability in the environment. Additionally or alternatively, each of the fluid pumps may be configured to send a beacon indicating its presence to the other pumps. In accordance with the schedule information 160-1, each of the fluid pumps represented by the schedule information 160-1 communicates with the other fluid pumps in the group to coordinate the delivery of fluid therapy as specified by the fluid instructions 105 and the schedule information 160-1.

[0097] Through the received schedule information 160-1, each fluid pump learns the identity of the other fluid pumps assigned to the group that is about to deliver a fluid instruction 105 to the recipient 108. Based on being part of the same ordered therapy and group as specified by the schedule information 160-1, the fluid pumps create a wired or wireless connection with each other. The fluid pumps then use that connection to provide notifications to each other. Examples of notifications include heartbeat signals indicating that the fluid pumps are connected and alive, trigger events such as indicating that each fluid pump has completed delivery of its assigned fluid, synchronization information to maintain temporal synchronization of the fluid pumps, etc.

[0098] In one embodiment, fluid pumps in a group can broadcast messages to other fluid pump members of the group and can send messages directly to other specific infusion devices, and if desired, communications can be secured (e.g., encrypted) to prevent malicious tampering.

[0099] Thus, in one embodiment, each fluid pump in the group of fluid pumps specified by schedule information 160-1 has the ability to communicate with other fluid pumps associated with fluid therapy delivery without the need for an intermediary agent, such as the order management entity 119, communication device 120, etc. As previously mentioned, in one embodiment, the group of fluid pumps has the ability to communicate with each other to collectively provide fluid therapy as specified by fluid order 105 without connection to network 190. In other words, the group of assigned fluid pumps 121, 122, 123, etc. are part of an independent network that delivers the respective fluid therapy to the recipient.

[0100] In one non-limiting exemplary embodiment, each of the fluid pumps 121, 122, 123, etc. are positioned independently relative to one another.

[0101] In a further exemplary embodiment, when the network 190 is available, each of the fluid pumps in the group further has the ability to communicate with the therapy service 118 of the instruction management entity 119. As part of the setup of each fluid pump, each fluid pump ensures that it can at least communicate with any infusion devices to which it is subordinate or which are subordinate to it (i.e., depending on its own triggering event definition). This may include a second device performing an infusion that must be completed before a third device can begin, or a third device performing an infusion with which the first device is configured to operate concurrently. As noted above, communication between the fluid pumps may be established over any network, either wired or wireless.

[0102] After communication is established between the fluid pumps in the group, the subordinate infusion device (a fluid pump waiting for another fluid pump to deliver a fluid) requests to be informed of all events. The upstream device (such as fluid pump 121, which is assigned to deliver a first fluid to the recipient prior to other fluids by fluid pumps 122, 123, etc.) communicates its own status and any noteworthy events that have already occurred. For example, if an upstream fluid pump has already started infusing its respective fluid, it communicates such information to the other fluid pumps in the group. In this way, each of the fluid pumps is aware of the status of all the other fluid pumps that collectively deliver the fluid therapy to the recipient 108.

[0103] As fluid therapy continues, the upstream fluid pumps (e.g., the initial delivering fluid pump) and concurrent infusion devices (fluid pumps that are simultaneously delivering fluid to the recipient 108 according to the schedule information) continue to communicate their respective status and any significant events (i.e., start, stop, stop, setting change, fault, alarm conditions, etc. associated with the fluid pumps) to the downstream fluid pumps (e.g., fluid pumps 122, 123, etc. that are scheduled to deliver their respective fluids after the upstream fluid pump) and other concurrent infusion devices. Using this information, the fluid pumps coordinate the start of their infusions.

[0104] Also, in the event that an upstream or concurrent fluid pump fails, loses communication, or an upstream or concurrent infusion is cancelled, the downstream infusion device (e.g., fluid pumps 122, 123) may indefinitely terminate, pause, or generate an alarm (e.g., on a display screen) (or an audible alarm) to notify the caregiver 107 of such event. For example, if a concurrent infusion of a respective fluid fails, the infusion device may terminate and generate an alarm. Also, if an upstream fluid pump (e.g., fluid pump 121) pauses or fails, the fluid pump may pause indefinitely.

[0105] In a further exemplary embodiment, when a connection to the instruction management entity 119 via the network 190 is available, each respective fluid pump communicates their status and significant trigger events to the therapy service 118, which stores such information in the therapy repository 180.

[0106] The therapy service 118 may also be queried by any fluid pump regarding the status of any other fluid pumps participating in the delivery of the fluid therapy as specified by the fluid instructions 105. This essentially acts as an alternate or secondary channel of communication, allowing each infusion device to verify the information it is receiving from a second source, providing a high degree of security. The repository 180 is also a source for additional information, providing each fluid pump information regarding its current status for the delivery of the fluid therapy.

[0107] Monitoring an ongoing injection In a further exemplary embodiment, the status of the fluid therapy may be monitored by the clinician through the use of the therapy dashboard 170 in FIG.

[0108] In one embodiment, dashboard 170 shows each infusion, the programmed infusion settings, an indication of the status of the infusion (e.g., completed, running, paused, pending), and any identified dependencies each infusion has with other infusions defined as part of the therapy.

[0109] FIG. 2 is an example diagram illustrating fluid instruction and generation of fluid delivery schedule information according to embodiments herein.

[0110] In this example embodiment, a caregiver 107 creates schedule information 160-1 (i.e., fluid delivery control information) for the delivery of multiple fluids to each recipient 108. Initially, communication device 120 receives information associated with each fluid to be delivered in a fluid order 105, such as type of fluid, amount of fluid to be delivered, rate at which to deliver the fluid to the recipient 108, dose / dose rate, order date, duration of delivery, etc.

[0111] In one embodiment, the instructional information 105 includes data indicative of a particular schedule to be used for delivering different fluids (including the order in which to deliver the fluids as specified by the fluid therapy, etc.).

[0112] In a further exemplary embodiment, to create schedule information 160-1, the caregiver 107 selects, via the fluid management system 126 (such as hardware, executed software, or a combination of hardware and executed software), a different fluid pump 121, 122, 123, etc., for delivering each respective fluid A, B, C, etc. as specified by the instructions 105.

[0113] More specifically, as shown in generated schedule information 160-1, caregiver 107 or other suitable entity assigns fluid A of the received fluid instruction 105 for delivery by fluid pump 121, caregiver 107 or other suitable entity assigns fluid B of the received fluid instruction 105 for delivery by fluid pump 122, caregiver 107 or other suitable entity assigns fluid C of the received fluid instruction 105 for delivery by fluid pump 123, and caregiver 107 or other suitable entity assigns fluid D of the received fluid instruction 105 for delivery by fluid pump 124.

[0114] In one embodiment, the fluid management system 126 of the communication device 120 initiates the display of the identity of each fluid pump and corresponding fluid associated with the fluid instruction 105 on the display screen 130. The caregiver 107 indicates which of the respective fluid pumps are to be assigned to deliver each different fluid as described above.

[0115] Referring again to FIG. 1, via communication 161, communication device 120 communicates generated schedule information 160-1 to each of fluid pumps 121, 122, 123, etc.

[0116] As previously discussed, fluid pumps 121 etc. operate collectively to provide for the delivery of different fluids A, B, C, D etc. according to schedule information 160-1.

[0117] In response to receiving schedule information 160-1 via communication 161, each of the fluid pumps initiates the display of information regarding any of a plurality of fluids associated with the fluid instruction 105 that are assigned for delivery to the recipient 108.

[0118] For example, the fluid pump 121 displays information on the display screen 131 of the fluid pump 121 such as the identity of the fluid A to be delivered to the recipient 108, the rate at which fluid A is to be delivered to the recipient 108, the dose / dose rate of fluid A, the indicated date, the duration of delivery associated with each fluid, etc.

[0119] The fluid pump 122 displays information, such as the identity of fluid B, and corresponding information, such as the amount of fluid B to be delivered to the recipient 108, the rate at which fluid B is delivered to the recipient 108, the dose / dose rate of fluid B, the indicated date, the duration of delivery associated with fluid B, etc., on a display screen 132 of the fluid pump 122.

[0120] The fluid pump 123 displays information on a display screen 133 of the fluid pump 123, such as the identity of the fluid C to be delivered to the recipient 108, the rate at which the fluid C is to be delivered to the recipient 108, the dose / dose rate of the fluid C, the indicated date, the duration of delivery associated with the fluid C, etc.

[0121] In this way, the caregiver 107 is informed which fluid source (such as type A, B, C, etc.) to connect to each fluid pump.

[0122] FIG. 3 is an example diagram illustrating the display of status information associated with multiple fluid pumps, according to embodiments herein.

[0123] Assume that at time T1, a caregiver 107 or other suitable entity initiates execution of fluid instructions 105 as specified by schedule information 160-1. In response to receiving input to begin an infusion (e.g., from the caregiver 107, via the fluid pump itself or communication device 120), the fluid pump 121 begins delivering fluid A to the recipient 108.

[0124] In this exemplary embodiment, each of the fluid pumps 121, 122, etc. displays the current status of the pump delivering the respective fluid to the recipient 108. For example, the display screen 131 of fluid pump 121 displays the status of delivery of fluid A to the recipient 108, and the display screen 132 of fluid pump 122 displays the status of delivery of fluid B to the recipient 108.

[0125] In a further exemplary embodiment, each of the fluid pumps communicate with each other (e.g., via their respective controllers) to indicate their status, and also communicate with the command management entity 119 and / or the communication device 120 to indicate the status of the delivery of the fluid. In one embodiment, between times T1 and T2 (a time period, such as one hour, for delivering fluid A), the fluid pump 121 communicates the status of the delivery to the communication device 120. In response to receiving the input, the communication device 120 displays a notification in the display area 325 of the display screen 130 indicating the status of the delivery of fluid A. Also, in one embodiment, the fluid pump 121 displays the information in the display area 325 on the display screen 131 of the fluid pump 121.

[0126] In this manner, the caregiver 107 can view the display screen 130 of the communication device 120 or the display screen 131 of the fluid pump 121 to determine the status of the respective fluid delivery.

[0127] FIG. 4 is an example diagram illustrating communications associated with multiple fluid pumps, according to embodiments herein.

[0128] At or about time T2, the delivery of fluid A is completed. In response to the completion of the delivery, fluid pump 121 communicates message 410 to fluid pump 122. In one embodiment, message 410 communicated to fluid pump 122 and other fluid pumps 123, etc., indicates the completion of the delivery of fluid A to recipient 108. It should be noted that message 410 may be generated and received from any suitable resource, such as fluid pump 121, instruction management entity 119, communication device 120, etc.

[0129] According to the schedule information 160-1 indicating to begin pumping of fluid B after the delivery of fluid A is completed, the message 410 acts as a triggering event for the fluid pump 122 to begin pumping of fluid B to the recipient 108.

[0130] In one embodiment, the fluid pump 122 initiates the display of a notification on the display screen 132 that the delivery of fluid B has begun. As further shown in FIG. 5, the communication device displays a notification that the fluid pump 121 has completed the delivery of fluid A.

[0131] FIG. 5 is an example diagram illustrating the display of status information associated with multiple fluid pumps, according to embodiments herein.

[0132] As described above, in accordance with schedule information 160-1 indicating that infusion of fluid B will begin when infusion of fluid A is completed at or near time T2, the fluid pump automatically begins delivering fluid B to recipient 108 (without requiring further input from other sources, etc.) in response to receiving notification from fluid pump 121 that delivery is complete.

[0133] In this exemplary embodiment, each of the fluid pumps 121, 122, etc., displays the current status of the pump delivering the respective fluid to the recipient 108. For example, the display screen 131 of fluid pump 121 displays a status (in display area 325) that delivery of fluid A is complete, while the display screen 132 of fluid pump 122 displays a status (in display area 525) that it is currently delivering fluid B to the recipient 108.

[0134] In a further exemplary embodiment, in the manner described above, each of the fluid pumps communicates with each other (such as via their respective controllers) to indicate their status, and also communicates with the command management entity 119 and / or the communication device 120 to indicate the status of the fluid delivery.

[0135] In one embodiment, between times T2 and T3 (a time period such as 15 minutes during which fluid B is being delivered), fluid pump 122 repeatedly communicates the status and current progress of the delivery to communication device 120. In response to receiving the input, communication device 120 displays a notification in display area 525 of display screen 130 indicating the status of the delivery of fluid B. Status information may include any information such as how much or what percentage of the total fluid has been delivered at a given time, the time remaining until completion of the delivery of fluid B, etc.

[0136] In one embodiment, the fluid pump 122 also displays a copy of the status information in the display area 525 on the display screen 132 of the fluid pump 122 .

[0137] In this manner, the caregiver 107 can view the display screen 130 of the communication device 120 or the respective display screens of each of the fluid pumps to determine the status of each fluid delivery.

[0138] FIG. 6 is an example diagram illustrating communication between multiple fluid pumps, according to embodiments herein.

[0139] At or about time T3, the delivery of fluid B is completed. In response to the completion, fluid pump 122 communicates message 610 to fluid pump 123 and other fluid pumps. In one embodiment, message 610 communicated to fluid pump 123 and other fluid pumps indicates the completion of delivery of fluid B to the recipient 108.

[0140] In accordance with schedule information 160-1, message 610 serves as a triggering event that causes fluid pump 123 to begin pumping fluid C to recipient 108. As shown in FIG 7 below, fluid pump 122 initiates the display of a notification on display screen 133 that pumping of fluid C has begun.

[0141] FIG. 7 is an example diagram illustrating the display of status information associated with multiple fluid pumps, according to embodiments herein.

[0142] As described above, at or about time T3, in accordance with schedule information 160-1, fluid pump 123 automatically begins delivering fluid C to recipient 108 in response to receiving notification from fluid pump 122 that it has completed delivering fluid B to recipient 108.

[0143] In this exemplary embodiment, each of the fluid pumps 121, 122, etc., displays the current status of the pump delivering the respective fluid to the recipient 108. For example, the display screen 131 of fluid pump 121 displays a status that delivery of fluid A is complete, the display screen 132 of fluid pump 122 displays a status that delivery of fluid B is complete, and the display screen 133 of fluid pump 123 displays a status that it is currently delivering fluid C to the recipient 108.

[0144] In a further exemplary embodiment, in the manner described above, each of the fluid pumps communicates with each other (such as via their respective controllers) to indicate their status, and also communicates with the command management entity 119 and / or the communication device 120 to indicate the status of the fluid delivery.

[0145] In one embodiment, during the time period of pumping fluid B between times T3 and T4 (e.g., 300 minutes), fluid pump 123 repeatedly communicates the status of the pumping (e.g., amount pumped over time) to communication device 120. In response to receiving the input, communication device 120 displays a notification in display area 725 of display screen 130 indicating the status of the pumping of fluid C. Also, in one embodiment, fluid pump 122 displays the information in display area 725 on display screen 133 of fluid pump 123.

[0146] In this manner, the caregiver 107 can view the display screen 130 of the communication device 120 or the display screens of each of the fluid pumps to determine the status of each fluid delivery.

[0147] FIG. 8 is an example block diagram of a computing device for implementing any of the operations described herein, according to embodiments herein.

[0148] In one embodiment, the fluid delivery environment 100 includes one or more instances of a computer system 850 to execute the fluid management system 126, the fluid pumps, the command management entity 119, the controllers 141, 142, and 143, and the like.

[0149] As shown, the computer system 850 of this example includes an interconnect 811, a processor 813 (such as one or more processor devices, computer processor hardware, etc.), a computer-readable storage medium 812 (such as hardware storage for storing data), an I / O interface 814, and a communication interface 817.

[0150] The interconnect 811 provides a connection between the processor 813 , the computer readable storage medium 812 , the I / O interface 814 , and the communication interface 817 .

[0151] The I / O interface 814 provides a connection to the repository 880 and, if present, to other devices such as a playback device, a display screen, input resources 892, a computer mouse, etc.

[0152] The computer readable storage medium 812 (e.g., a non-transitory hardware medium) may be any hardware storage resource or device such as memory, optical storage, a hard drive, a rotating disk, etc. In one embodiment, the computer readable storage medium 812 stores instructions that are executed by the processor 813.

[0153] Communications interface 817 allows computer system 850 and processor 813 to communicate over resources such as network 190 to retrieve information from remote sources and to communicate with other computers. I / O interface 814 allows processor 813 to retrieve stored information from repository 180.

[0154] As shown, computer readable storage medium 812 is encoded with a controller application 140-1 (e.g., software, firmware, etc.) executed by processor 813. Controller application 140-1 may be configured to include instructions to implement any of the operations described herein. For example, each of the resources, such as resource 119, communication device 120, fluid management system 126, fluid pump 121, fluid pump 122, fluid pump 123, etc., may be configured to include an instance of computer system 850 to perform the corresponding operations.

[0155] During operation of one embodiment, the processor 813 (e.g., computer processor hardware) accesses the computer-readable storage medium 812 through the use of the interconnect 811 to initiate, operate, execute, interpret, or otherwise perform instructions in the control application 140-1 (i.e., a management application) stored on the computer-readable storage medium 812.

[0156] Execution of management application 140-1 generates processing functions such as management process 140-2 in processor 813. In other words, management process 140-2 associated with processor 813 represents one or more aspects of the execution of management application 140-1 within or on processor 813 in computer system 850.

[0157] Those skilled in the art will appreciate that computer system 850 may include other processes and / or software and hardware components, such as an operating system that controls the allocation and use of hardware resources to execute management application 140-1.

[0158] It should be noted that, according to different embodiments, the computer system can be any of a variety of types of devices, including, but not limited to, wireless access points, mobile computers, personal computer systems, wireless devices, base stations, telephone devices, desktop computers, laptops, notebooks, netbook computers, mainframe computer systems, handheld computers, workstations, network computers, application servers, storage devices, consumer electronics devices, such as cameras, camcorders, set-top boxes, mobile devices, video game consoles, handheld video game devices, peripheral devices such as switches, modems, routers, or generally any type of computing or electronic device. In one non-limiting embodiment, the computer system 850 is within the fluid delivery system 100. However, it should be noted that the computer system 850 can be in any location or can be included in any suitable resource in the network environment 100 to implement the functionality described herein.

[0159] The functionality supported by the different resources will now be described via the flowchart in Figure 9. Please note that the steps in the flowchart below may be performed in any suitable order.

[0160] 9 is a flow chart 900 illustrating an example method according to an embodiment. Note that there is some overlap with the concepts discussed above.

[0161] In action 910, the fluid management system 126, and therefore the caregiver 107, receives fluid delivery instructions 105 that specify a fluid therapy for delivering a number of different fluids to a recipient .

[0162] In processing operation 920, via the fluid management system 126, the caregiver 107 assigns a group of multiple fluid pumps, including fluid pump 121, fluid pump 122, fluid pump 123, etc., to execute the fluid delivery instructions 105 for delivering multiple different fluids A, B, C, etc. to the recipient 108.

[0163] In processing operation 930, the fluid management system 126 configures / programs a group of multiple fluid pumps 121, 122, 123, etc. and corresponding controllers 141, 142, 143, etc. based on the fluid delivery instructions 105 and the schedule information 160-1 to implement controlled delivery of multiple different fluids A, B, C, etc. from the multiple fluid pumps 121, 122, 123, etc. in a manner specified by the schedule information 160-1.

[0164] It should again be noted that the techniques herein are well suited for use in managing fluid delivery systems, however, the embodiments herein are not limited to use in such applications, and the techniques described herein are well suited for other applications as well.

[0165] Based on the description set forth herein, numerous specific details have been set forth to provide a thorough understanding of the claimed subject matter. However, one of ordinary skill in the art will understand that the claimed subject matter may be practiced without these specific details. In other instances, methods, apparatus, systems, etc. known to those skilled in the art have not been described in detail so as not to obscure the claimed subject matter. Some portions of the detailed description are presented in terms of algorithms or symbolic representations of operations on data bits or binary digital signals stored within a computing system memory, such as a computer memory. These algorithmic descriptions or representations are examples of techniques used by those skilled in the data processing arts to convey the meaning of their work to others skilled in the art. An algorithm described herein is generally considered to be a self-consistent sequence of operations or similar processing that leads to a desired result. In this context, operations or processing include physical manipulations of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals that can be stored, transferred, combined, compared, or otherwise manipulated. It has sometimes been convenient, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals, or the like. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless otherwise indicated, and as will be apparent from the description below, use of the terms "processing," "computing," "calculating," "determining," and the like throughout the description of this specification will be understood to refer to actions or processes of a computing platform, such as a computer or similar electronic computing device, that manipulates or transforms data, which is represented as physical electronic or magnetic quantities, within memories, registers or other information storage devices, transmission devices, or display devices of the computing platform.

[0166] Although the present invention has been shown and described in detail with reference to preferred embodiments thereof, those skilled in the art will understand that various changes in form and details may be made therein without departing from the spirit and scope of the present application as defined by the appended claims. Such variations are intended to be covered by the scope of the present application. Thus, the foregoing description of the embodiments of the present application is not intended to be limiting. Rather, any limitations to the present invention are expressed in the following claims.

Claims

1. A method for operating a fluid management system for managing a fluid, comprising: receiving, by the fluid management system, fluid delivery instructions specifying a schedule for delivering a plurality of different fluids to a recipient; the plurality of different fluids includes a first fluid and a second fluid; the schedule indicates a triggering condition for delivering a second fluid from a second fluid pump relative to delivering a first fluid from a first fluid pump, the schedule indicating that delivery of the second fluid to a recipient is conditional on delivery of the first fluid to the recipient; the schedule further indicating the first fluid pump providing a trigger notification to the second fluid pump, the trigger notification triggering the second fluid pump to deliver the second fluid to the recipient; assigning a group of a plurality of fluid pumps to execute the fluid delivery instructions for delivering the plurality of different fluids to the recipient by the fluid management system, the group of a plurality of fluid pumps including the first fluid pump and the second fluid pump; displaying, by the fluid management system, a notification indicating the trigger condition for which the second fluid pump is scheduled to deliver the second fluid to the recipient; controlling, by the fluid management system, the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner specified by the schedule; A method comprising:

2. 2. The method of claim 1 , The method further includes displaying, by the fluid management system, a visual notification on a first fluid pump of the plurality of fluid pumps, the displayed visual notification indicating the schedule for pumping the plurality of different fluids from each of the plurality of fluid pumps.

3. 2. The method of claim 1, wherein controlling the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner specified by the schedule comprises: distributing the schedule to each of the plurality of fluid pumps; synchronizing operation of the plurality of fluid pumps with respect to a common clock; A method comprising:

4. 2. The method of claim 1 , The method further comprising receiving the schedule from a communication device operated by a caregiver, the caregiver creating the schedule, the schedule indicating when each of the plurality of fluid pumps will deliver a respective fluid to the recipient.

5. 10. The method of claim 1, wherein the schedule indicates concurrent delivery of the first fluid and the second fluid to the recipient.

6. 10. The method of claim 1, wherein the schedule indicates that the first fluid and the second fluid are to be delivered to the recipient sequentially.

7. 2. The method of claim 1, wherein the schedule indicates that the second fluid is to be delivered to the recipient after a predetermined delay following completion of delivery of the first fluid to the recipient.

8. 2. The method of claim 1, wherein allocating the group of multiple fluid pumps to execute the fluid delivery instructions includes, via input from a caregiver administering the fluid delivery instructions, i) selecting the first fluid pump to deliver a first fluid of the multiple different fluids, and ii) selecting the second fluid pump to deliver a second fluid of the multiple different fluids.

9. 1. A system comprising: a plurality of fluid pumps including a first fluid pump and a second fluid pump; A fluid management system; Including, The fluid management system comprises: operatively receiving fluid delivery instructions specifying a schedule for delivering a plurality of different fluids to a recipient; the plurality of different fluids includes a first fluid and a second fluid; the schedule indicating timing of delivery of a second fluid from a second fluid pump relative to delivery of a first fluid from a first fluid pump, the schedule indicating that delivery of the second fluid to a recipient is conditioned on delivery of the first fluid to the recipient; operatively allocating a group of a plurality of fluid pumps, including the first fluid pump and the second fluid pump, to execute the fluid delivery instructions for delivering the plurality of different fluids to the recipient; and operative to control the delivery of said plurality of different fluids from said plurality of fluid pumps in a manner as specified by said schedule; the fluid management system is further operative to display a notification indicative of a trigger condition under which the second fluid pump is scheduled to deliver the second fluid to the recipient; the first fluid pump providing a triggering signal to the second fluid pump, the triggering signal indicating triggering the second fluid pump to deliver the second fluid to the recipient. system.

10. 10. The system of claim 9, The method further includes a display screen operative to display a visual notification on a first fluid pump of the plurality of fluid pumps, the displayed visual notification indicating the schedule for pumping the plurality of different fluids by each of the plurality of fluid pumps.

11. 10. The system of claim 9, wherein the fluid management system is further operative to control the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner specified by the schedule, the control comprising: distribution of the schedule to each of the plurality of fluid pumps; synchronizing operation of the plurality of fluid pumps with respect to a common clock; Including, the system.

12. 10. The system of claim 9, wherein the fluid management system further comprises: The system is operative to receive the schedule from a communication device operated by a caregiver, the caregiver creating the schedule, the schedule indicating when each of the plurality of fluid pumps will deliver a respective fluid to the recipient.

13. 10. The system of claim 9, wherein the schedule indicates concurrent delivery of the first fluid and the second fluid to the recipient.

14. 10. The system of claim 9, wherein the schedule indicates that the first fluid and the second fluid are delivered to the recipient sequentially.

15. 10. The system of claim 9, wherein the schedule determines that the second fluid is delivered to the recipient after a predetermined delay following completion of delivery of the first fluid to the recipient.

16. 10. The system of claim 9, wherein the fluid management system further comprises: The system, via input from a caregiver administering the fluid delivery instructions, acts to: i) select the first fluid pump to deliver a first fluid of the plurality of different fluids, and ii) select the second fluid pump to deliver a second fluid of the plurality of different fluids.

17. 1. Computer readable storage hardware having instructions stored therein, the instructions, when executed by computer processor hardware, causing the computer processor hardware to: receiving fluid delivery instructions specifying a schedule for delivering a plurality of different fluids to a recipient; the plurality of different fluids includes a first fluid and a second fluid; the receiving, the schedule indicating timing of delivery of a second fluid from a second fluid pump relative to delivery of a first fluid from a first fluid pump, the schedule indicating that delivery of the second fluid to a recipient is contingent on delivery of the first fluid to the recipient; the schedule further indicating a trigger condition under which the first fluid pump provides a trigger notification to the second fluid pump, the trigger notification triggering the second fluid pump to deliver the second fluid to the recipient; assigning a group of a plurality of fluid pumps, including the first fluid pump and the second fluid pump, to execute the fluid delivery instructions for delivering the plurality of different fluids to the recipient; displaying a notification indicating the trigger condition under which the second fluid pump is scheduled to deliver the second fluid to the recipient; and controlling the delivery of the plurality of different fluids from the plurality of fluid pumps in a manner specified by the schedule; Computer readable storage hardware.

Images