Procedure-based programming for infusion pumps

Abstract

Methods and systems for configuring a plurality of infusion pumps according to a functional set. A method includes implementing a plurality of infusion pumps, each of the infusion pumps configured to administer medication to a patient, implementing a drug library, the drug library including at least one functional set defining a set of medications, receiving input data related to one of the at least one functional sets, obtaining a particular set of medications from the drug library corresponding to the input data, programming the plurality of infusion pumps according to the set of medications, and infusing the patient with the plurality of infusion pumps.

Claims

1. A system for configuring a plurality of medical devices in a hospital network of one or more hospitals, each medical device configured according to a particular treatment protocol selected from a plurality of treatment protocols, each medical device comprising an infusion pump configured to administer medication to a patient, the system comprising: a rack, configured to physically and removably couple the plurality of medical devices thereto; a router, configured to enable digital communications between the plurality of medical devices that are physically and removably coupled to the rack into a local area network; and a drug library including functional sets of infusates grouped according to a hierarchy of operational levels in the hospital network of one or more hospitals, each operational level comprising an amount of complexity of detail by which the system is viewed or programmed by a user, wherein the amount of complexity of detail is inversely proportional to the operational level at which a particular functional set appears in the hierarchy, each functional set implemented through one or more treatment protocols and comprising a plurality of sets of medications, defining medication amounts and infusion rates based on a received data set including hospital data, patient data, sensor data, and procedure data, the drug library configured to automatically select a set of medications from a chosen functional set based on the received data set, wherein, when the plurality of medical devices are physically coupled to the rack and electrically coupled to the local area network through the router, (i) a particular treatment protocol pursuant to the selected set of medications is transmitted to each of the plurality of medical devices and (ii) the plurality of medical devices are each able to responsively provide pre-selected therapies, corresponding to the particular treatment protocol, the plurality of infusion pumps being communicatively coupled with each other such that the pumps are mutually programmable according to the selected set of medications.

2. The system for configuring a plurality of medical devices according to a particular treatment protocol of claim 1, wherein the particular treatment protocol is selected from a group consisting of workflow management protocols and procedure management protocols.

3. The system of claim 1, wherein at least one functional set of the drug library comprises a hospital procedure.

4. The system of claim 1, wherein the functional sets of infusates of the drug library can be set at a hospital network level, a hospital level, a department level, or a procedure level.

5. The system of claim 1, further comprising: a user interface configured to receive input data; and a programming engine configured to receive a command from the input data and transmit a command from the programming engine to the plurality of medical devices.

6. A system for configuring a plurality of medical devices in a hospital network of one or more hospitals, each medical device configured according to a particular treatment protocol selected from a plurality of treatment protocols, each medical device comprising an infusion pump configured to administer medication to a patient, the system comprising: a rack, configured to physically and removably couple the plurality of medical devices thereto; and a router, configured to enable digital communications between the plurality of medical devices that are physically and removably coupled to the rack into a local area network: and a drug library including functional sets of infusates grouped according to a hierarchy of operational levels in the hospital network of one or more hospitals, each operational level comprising an amount of complexity of detail by which the system is viewed or programmed by a user, wherein the amount of complexity of detail is inversely proportional to the operational level at which a particular functional set appears in the hierarchy, each functional set implemented through one or more treatment protocols and comprising a plurality of sets of medications, defining medication amounts and infusion rates based on a received data set including hospital data, patient data, sensor data, and procedure data, the drug library configured to automatically select a set of medications from a chosen functional set based on the received data set, wherein, when the plurality of medical devices are physically coupled to the rack and electrically coupled to the local area network through the router, (i) a particular treatment protocol pursuant to the selected set of medications is transmitted to each of the plurality of medical devices such that each medical device receives a unique treatment protocol and (ii) the plurality of medical devices are each able to responsively provide pre-selected therapies, corresponding to the particular treatment protocol, the plurality of infusion pumps being communicatively coupled with each other such that the pumps are mutually programmable according to the selected set of medications.

7. The system of claim 6, wherein the particular treatment protocol is selected from a group consisting of workflow management protocols and procedure management protocols.

8. The system of claim 6, wherein at least one functional set of the drug library comprises a hospital procedure.

9. The system of claim 6, wherein the functional sets of infusates of the drug library can be set at a hospital network level, a hospital level, a department level, or a procedure level.

10. The system of claim 6, further comprising: a user interface configured to receive input data; and a programming engine configured to receive a command from the input data and transmit a command from the programming engine to the plurality of medical devices.

11. A system for configuring a plurality of medical devices in a hospital network of one or more hospitals, each medical device configured according to a particular treatment protocol selected from a plurality of treatment protocols, comprising: a rack, configured to physically and removably couple the plurality of medical devices thereto; a router, configured to enable digital communications between the plurality of medical devices that are physically and removably coupled to the rack into a local area network; and a drug library including functional sets of infusates grouped according to a hierarchy of operational levels in the hospital network of one or more hospitals, each operational level comprising an amount of complexity of detail by which the system is viewed or programmed by a user, wherein the amount of complexity of detail is inversely proportional to the operational level at which a particular functional set appears in the hierarchy, each functional set implemented through selected ones of said treatment protocols, wherein, when the plurality of medical devices are physically coupled to the rack and electrically coupled to the local area network through the router, (i) a particular treatment protocol pursuant to a selected functional set of infusates within the hierarchical levels of functional sets of infusates is transmitted to each of the plurality of medical devices and (ii) the plurality of medical devices are able to each responsively provide pre-selected therapies, respectively, corresponding to the particular treatment protocol.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) Subject matter hereof may be more completely understood in consideration of the following detailed description of various embodiments of the subject matter in connection with the accompanying drawings, in which:

(2) FIG. 1A is a perspective view of a syringe type infusion pump, according to an embodiment.

(3) FIG. 1B is a front view of a control module of an ambulatory type infusion pump, according to an embodiment.

(4) FIG. 2 is a block diagram of an infusion pump system, according to an embodiment.

(5) FIG. 3 is a block diagram of a portion of a generic drug library including functional sets, according to an embodiment.

(6) FIG. 4 is a block diagram of a procedure-based programming configuration of a cardiac surgery procedure, according to an embodiment.

(7) FIG. 5 is an annotated block diagram of a system for programming a set of infusion pumps for the procedure-based programming of the cardiac surgery procedure of FIG. 4, according to an embodiment.

(8) FIG. 6 is a block diagram of a system for procedure-based programming a set of infusion pumps for according to a functional set, according to an embodiment.

(9) FIG. 7A is a block diagram of an example hierarchy in a hospital network, according to an embodiment.

(10) FIG. 7B is a block diagram of an example hierarchy in a hospital network, according to an embodiment.

(11) FIG. 8 is a flowchart of a method for procedure-based programming of a plurality of infusion pumps in a functional set, according to an embodiment.

(12) While embodiments are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit subject matter hereof to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of subject matter hereof in accordance with the appended claims.

DETAILED DESCRIPTION OF THE DRAWINGS

(13) FIGS. 1A and 1B show examples of infusion pumps 100 and 150, respectively (also referred to more generally in this disclosure by numeral 100), which can be used to implement embodiments of the systems and methods discussed herein. In general, infusion pump 100 is a syringe-type pump that can be used to deliver a wide range of infusates, drug therapies and treatments. Infusion pump 100 includes a pharmaceutical container or syringe 110, which is supported on and secured to housing 120 by clamp 130, respectively. In embodiments, syringe 110 can be separately supplied from pump 100. In other embodiments, syringe 110 is an integrated component of pump 100. Syringe 110 includes a plunger 140 that forces fluid outwardly from syringe 110 via infusion line 160 that is connected to a patient. A motor and lead screw arrangement internal to housing 120 of pump 100 cooperatively actuates a pusher or plunger driver mechanism 170, to move plunger 140 of syringe 110. In embodiments, a sensor (not shown; which is typically internal to plunger driver mechanism 170) monitors force and/or plunger position in the syringe according to system specifications.

(14) Infusion pump 150 shown in FIG. 1B is an example of an ambulatory-type infusion pump that can be used to deliver a wide range of infusates, drug therapies, and treatments. Such ambulatory pumps can be comfortably worn by or otherwise removably coupled to a user for in-home ambulatory care by way of belts, straps, clips or other simple fastening means, and can also be alternatively provided in ambulatory pole-mounted arrangements within hospitals and other medical care facilities. Infusion pump 150 generally includes a peristaltic type infusion pump mechanism that controls the flow of medication from a reservoir (not shown in FIG. 1B) of fluid coupled to pump 150 through a conduit from the reservoir which can matingly pass along bottom surface 180 of pump 150. The reservoir can comprise a cassette that is attached to the bottom of pump 150 at surface 180, or an IV bag or other fluid source that is similarly connected to pump 150 via an adapter plate (not shown) at surface 180. Specifically, pump 150 uses valves and an expulsor located on bottom surface 180 to selectively squeeze a tube of fluid (not shown) connected to the reservoir to effect the movement of the fluid supplied by the reservoir through the tube and to a patient in peristaltic pumping fashion. Infusion pumps 100 and 150 are two examples of infusion pumps that can be suitable for use with embodiments discussed herein, though other pumps and devices can be used in other embodiments of infusion systems utilizing subject matter hereof.

(15) FIG. 2 is a schematic diagram of an infusion pump system 200. System 200 includes infusion pump 210 having pump control system 245 with processor 250 and memory 255 programmable with selected protocols, profiles, segments of profiles, and other settings for controlling operation of pumping mechanism 260 such as, for example, the aforementioned syringe and ambulatory or peristaltic type mechanisms. In an embodiment, memory 255 can comprise a drug library or portions thereof configured for programming according to the functional sets described herein.

(16) In an embodiment, processor 250 can be any programmable device that accepts digital data as input, is configured to process the input according to instructions or algorithms, and provides results as outputs. In an embodiment, processor 250 can be a central processing unit (CPU) configured to carry out the instructions of a computer program. In another embodiment, processor 250 can be an application specific integrated circuit (ASIC). In another embodiment, processor 250 can be a field-programmable gate array (FPGA). Processor 250 is therefore configured to perform arithmetical, logical, and input/output operations.

(17) Memory 255 can comprise volatile or non-volatile memory as required by the coupled processor 255 to not only provide space to execute the instructions or algorithms, but to provide the space to store the instructions themselves. In embodiments, volatile memory can include random access memory (RAM), dynamic random access memory (DRAM), or static random access memory (SRAM), for example. In embodiments, non-volatile memory can include read-only memory, flash memory, ferroelectric RAM, hard disk, floppy disk, magnetic tape, or optical disc storage, for example. The foregoing lists in no way limit the type of memory that can be used, as these embodiments are given only by way of example and are not intended to limit the scope of subject matter hereof.

(18) Infusion pump 200 can also include control module 220 (e.g., a user interface) for relaying commands to pump control system 245. Control module 220 includes at least one user interface 230 utilizing operator input technology including input mechanism(s) 235, which work with display 225. In some cases display 225 will be considered part of user interface(s) 230. User interface 230 generally allows a user to enter various parameters, including but not limited to names, drug information, limits, delivery shapes, information relating to hospital facilities, as well as various user-specific parameters (e.g., patient age and/or weight). Infusion pump 210 can include a USB port, Ethernet, Wi-Fi or other appropriate input/output (I/O) interface port 240 for connecting infusion pump 210 to network or computer 215 having software designed to interface with infusion pump 210. In an embodiment, network or computer 215 can transmit a drug library or portions thereof for programming according to the functional sets described herein. For example, network or computer 215 can comprise an embedded server system for controlling, in real-time, infusion pump 200. In embodiments, control module 220 can be automatically configured according to data from network or computer 215 (or the embedded server) for programming according to functional sets.

(19) Power to infusion pump 210 is accomplished via an AC or DC power cord or any suitable battery source. Embodiments can also include a wireless power source. User inputs 205 to the system can be provided by programming from a user, such as a patient, pharmacist, scientist, drug program designer, medical engineer, nurse, physician, or other medical practitioner or healthcare provider. User inputs 205 may utilize direct interfacing (i.e., a keyboard or other touch-based inputs) or user inputs 205 may utilize indirect or “touchless” interfacing (i.e., gestures; voice commands; facial movements or expressions; finger, hand, head, body and arm movements; or other inputs that do not require physical contact). User inputs 205 are generally interfaced, communicated, sensed, and/or received by operator input mechanisms 235 of user interface 230. Operator input mechanisms 235 may include, for example, keyboards, touch screens, cameras, or sensors of electric field, capacitance, or sound.

(20) As depicted in FIG. 2, infusion pump 210 is operably coupled to reservoir 265 via pumping mechanism 260. In embodiments, reservoir 265 can comprise any suitable infusate supply, such as an IV bag, syringe, continuous supply, or other infusate storage. In an embodiment, reservoir 265 is coupled to pumping mechanism 260 by cannula suitable for transferring infusate stored in reservoir 265 to pumping mechanism 260.

(21) Referring to FIG. 3, a block diagram of a portion of a generic drug library 300 including functional sets is depicted, according to an embodiment. Drug library 300 generally comprises Functional Set A 302 and Functional Set B 304. For example, Functional Set A 302 can comprise a department-level procedure for emergencies, in an emergency room department. In another example Functional Set B 304 can comprise a particular procedure for a particular department, such as cardiac surgery.

(22) Functional Set A 302 comprises a set of medications 306 to be infused. For example, set of medications 306 can be defined by Drug 1, Drug 2, and Drug 3, as depicted in FIG. 3. Each of the individual medications in set of medications 306 can be utilized to individually address a need of Functional Set A 302. In an embodiment, in combination, the individual medications within set of medications 306 are configured to complement each other to positively affect the patient being infused. In other embodiments, a medical practitioner can select among set of medications 306 for infusion. For example, only Drug 1 and Drug 3 might be utilized for a particular patient. Drug library 300 allows for easy selection of subgroups of set of medications 306. Likewise, Functional Set B 304 comprises a set of medications 308 to be infused. For example, set of medications 308 can be defined by Drug 4, Drug 5, Drug 6, and Drug 7, as depicted in FIG. 3.

(23) Set of medications 306, and particularly, Drug 1, Drug 2, and Drug 3 can be respectively configured for programming on a particular set of pumps 310. For example, set of pumps 310 can generally include Infusion Pump 1, Infusion Pump 2, and Infusion Pump 3. In an embodiment, Drug 1 can be configured for programming on Infusion Pump 1, Drug 2 can be configured for programming on Infusion Pump 2, and Drug 3 can be configured for programming on Infusion Pump 3. In other embodiments (not shown), set of infusions 306 can be defined such that pumps can be programmed ad-hoc. Likewise, set of infusions 308, and particularly, Drug 4, Drug 5, Drug 6, and Drug 7 can be respectively configured for programming on a particular set of pumps 312. For example, set of pumps 312 can generally include Infusion Pump 4, Infusion Pump 5, Infusion Pump 6, and Infusion Pump 7.

(24) Therefore, by selecting Functional Set A 302, a medical practitioner can program the infusions defined by set of medications 306 on set of pumps 310. Likewise, by selecting Functional Set B 304, a medical practitioner can program the infusions defined by set of medications 308 on set of pumps 312.

(25) Referring to FIG. 4, a block diagram of a procedure-based programming configuration 400 for a cardiac surgery procedure 402 is depicted, according to an embodiment. Configuration 400 generally comprises a quick setup procedure, such as cardiac surgery procedure 402.

(26) Cardiac surgery procedure 402 comprises a set of infusates 404-414. For example, cardiac surgery procedure 402 can comprise a programming configuration for an infusion pump for sodium bicarbonate 404, a programming configuration for an infusion pump for saline 406, a programming configuration for an infusion pump for fenoldopam 408, a programming configuration for an infusion pump for insoline 410, a programming configuration for an infusion pump for remifentanil 412, and a programming configuration for an infusion pump for saline 414.

(27) In an embodiment, a drug library can be utilized that defines a set of medications for the procedure 402 and the infusates 404-414, such as drug library 300. Optionally, and as described with respect to drug library 300, the drug library can define a set of pumps for administering the set of infusates. As a result, a drug library, such as drug library 300, can comprise a “Workflow Management” programming configuration or “Procedure Management” programming configuration option. Drug library 300 therefore supports more than one pump being programmed concurrently. In another embodiment, a “Workflow Management” programming configuration or “Procedure Management” programming configuration option can be selected on a pump, such as infusion pump 210 in FIG. 2.

(28) Referring to FIG. 5, an annotated block diagram of a system 500 for programming a set of infusion pumps for functional set programming is depicted, according to an embodiment. In particular, system 500 is configured for the programming of the cardiac surgery procedure of FIG. 4 System 500 generally comprises a server 502, a drug library 504, and a set of infusion pumps 506-516.

(29) In embodiments, set of infusion pumps 506-516 can be operably coupled to a networked rack. The rack can be configured to physically and removably couple the set of infusion pumps 506-516. In an embodiment, the rack further comprises a router configured to enable digital communications between the set of infusion pumps 506-516. For example, a router and set of infusion pumps 506-516 can comprise a local area network such the set of infusion pumps 506-516 are physically coupled to the rack and electrically coupled to the local area network through the router.

(30) In an embodiment, server 502 comprises a processor and a memory. In an embodiment, the processor can be any programmable device that accepts digital data as input, is configured to process the input according to instructions or algorithms, and provides results as outputs. In an embodiment, the processor can be a central processing unit (CPU) configured to carry out the instructions of a computer program. In another embodiment, the processor can be an application specific integrated circuit (ASIC). In another embodiment, the processor can be a field-programmable gate array (FPGA). The processor is therefore configured to perform basic arithmetical, logical, and input/output operations.

(31) The memory can comprise volatile or non-volatile memory as required by the coupled processor to not only provide space to execute the instructions or algorithms, but to provide the space to store the instructions themselves. In embodiments, volatile memory can include random access memory (RAM), dynamic random access memory (DRAM), or static random access memory (SRAM), for example. In embodiments, non-volatile memory can include read-only memory, flash memory, ferroelectric RAM, hard disk, floppy disk, magnetic tape, or optical disc storage, for example. In an embodiment, the memory can comprise a database. In an embodiment, the memory comprises memory for operation of the processor and a separate database for storing records related to the system. The foregoing lists in no way limit the type of memory that can be used, as these embodiments are given only by way of example and are not intended to limit the scope of the subject matter hereof.

(32) A plurality of engines can be implemented by or according to the processor and memory of server 502. For example, any number of engines can be configured to coordinate the programming of the set of pumps 506-516, as directed by drug library 504. As such, server 502 is communicatively coupled to at least one of infusion pumps 506-516. In an embodiment, referring to infusion pump system 200 in FIG. 2, server 502 comprises a network or computer similar to network or computer 215 having software designed to interface with infusion pumps 506-516. In an embodiment, server 502 can comprise a real-time embedded server, such as embodiments of the embedded server described in the aforementioned U.S. Patent Application No. 62/158,213. It is therefore to be appreciated and understood that, although depicted in FIG. 5 separately from pumps 506-516, server 502 could physically reside in the rack or even in one of pumps 506-516.

(33) Server 502 can be configured to transmit a set of programming instructions that comprise part of a functional set larger than programming for a single pump. For example, a set of programming instructions can comprise a unique programming configuration for each coupled pump. In an embodiment, the set of programming instructions comprises a batch programming command that contains the programming instructions for all coupled pumps 506-516. In such embodiments, each pump is only programmed according to the particular instructions intended for that particular pump but receives the batch or aggregated programming instructions for all pumps. In embodiments, pump identifiers or other unique data sets can be utilized to parse the batch programming command. In another embodiment, server 502 individually transmits the programming instructions for all coupled pumps 506-516 to each of the coupled pumps 506-516. In still another embodiment, one of pumps 506-516 further directs the programming command after receipt from server 502.

(34) Drug library 504 comprises a database of functional sets including a set of medications to be infused for each level such as, for example, the aforementioned department-level procedure for emergencies. In an embodiment, drug library 504 is substantially similar to the portion of drug library 300 depicted in FIG. 3. For example, drug library 504 can comprise cardiac surgery procedure 402 and set of medications 404-414 as depicted and described with respect to FIG. 4. Referring again to FIG. 5, as depicted, drug library 504 is operably coupled to server 502. In an embodiment, drug library 504 can be embodied on server 502. In another embodiment, drug library 504 can be embodied on a separate database accessible by server 502.

(35) Each of set of pumps 506-516 can be substantially similar to infusion pump 210 as depicted and described with respect to FIG. 2. In an embodiment, set of pumps 506-516 are communicatively coupled to each other. For example, pump 506 can be operably and communicatively coupled to each of pumps 508-516 such that pump 506 can command programming to each of pumps 508-516. In another example embodiment, each of pumps 506-516 is communicatively coupled to server 502. In embodiments, pumps 506-516 can be communicatively coupled such that data, commands, messages, or any other information specific to one of pumps 506-516 can be passed to any of the other pumps 506-516. For example, pumps 506-516 can be operably coupled to a networked rack.

(36) In operation, as depicted by the annotations in FIG. 5, server 502 communicates with drug library 504 to define the functional set programming for pumps 506-516. Server 502 communicates with pump 506 after a functional set programming is selected on pump 506. In another embodiment, functional set programming is initiated by server 502. In another embodiment, a clinician interfaces with one of associated pumps and selects the desired work flow for the upcoming procedure. This pump then sends programming information to the other of the associated plurality of pumps 506-516. The programming information can include infusion information such as drug, dose, concentration, and weight, as needed per the infusion type. In an embodiment, after the initial programming, the pumps do not automatically control each other.

(37) As depicted in FIG. 5, “Cardiac Surgery Quick Setup” is selected on pump 506. Pump 506 interfaces with server 502, and pump 506 is correspondingly programmed for a particular infusion defined by the functional set infusions for Cardiac Surgery. For example, referring again to FIG. 4, and cardiac surgery procedure 402, pump 506 can be programmed for an infusion of sodium bicarbonate 404. Subsequently or concurrently with the programming of pump 506, pumps 508-516 receive programming information from pump 506. In an embodiment, pump 506 can transmit a programming command to pumps 508-516. For example, in an embodiment, and referring again to FIG. 4, pump 508 is programmed for an infusion of saline 406. Pump 510 is programmed for an infusion of fenoldopam 408. Pump 512 is programmed for an infusion of insoline 410. Pump 514 is programmed for an infusion of remifentanil 412. Pump 516 is programmed for an infusion of saline 414. In another embodiment (not depicted), server 502 transmits a programming instruction separately to each of pumps 506-516 in either a batched command or individual commands unique to each pump. Irrespective of a particular programming architecture, pumps 506-516 to be used in the procedure are thus associated with each other. Pumps 506-516 could be associated by being plugged into the same rack or they could be associated manually through serial number, MAC (media access control) address, same subnet, barcode, or any other suitable association method.

(38) Referring to FIG. 6, a block diagram of a system 600 for programming a set of infusion pumps according to a functional set is depicted, according to an embodiment. System 600 generally comprises inputs of hospital data 602, patient data 604, sensor data 606, and procedure data 608 into programming engine 610 for programming of a plurality of infusion pumps 612-616.

(39) Hospital data 602 generally comprises hospital-level data or information related to infusions. For example, hospital data 602 can comprise hospital procedures, standards, configurations, and other hospital-centric information.

(40) Patient data 604 generally comprises patient-specific data or information. For example, patient data 604 can comprise patient height, patient weight, patient gender, patient ID, allergy information, and any other suitable patient-specific information.

(41) Sensor data 606 generally comprises readings, levels, or other statuses provided by any sensors configured for sensing information about the patient. For example, sensor data 606 can comprise temperature data, pulse rate, breathing rate, blood oxygen levels, and blood pressure, and any other suitable sensor data.

(42) Procedure data 608 generally comprises a functional set selection of a set of medications to be infused. In an embodiment, procedure data 608 can comprise a functional set selection as defined by FIG. 3 and, for example, Functional Set A 302 or Functional Set B 304. For example, procedure data 608 can comprise “Cardiac Surgery Quick Setup” as depicted in FIG. 4.

(43) In embodiments, hospital data 602, patient data 604, sensor data 606, and procedure data 608 can be received by communications engine 622 from a respective sending apparatus. For example, a Hospital Information System (HIS) can transmit hospital data 602 and/or patient data 604 to communications engine 622. Each of the respective sensors configured to sense characteristics about or related to the patient can transmit the respective sensor data 606 to communications engine 622. Procedure data 608 can be selected or input as described with respect to FIG. 5 and subsequently transmitted to communications engine 622. In embodiments, additional or fewer data inputs can be utilized by system 600.

(44) Programming engine 610 generally comprises a functional set drug library 618, a processor 620, and a communications engine 622. In an embodiment, programming engine 610 is embodied on a discrete server, such as server 502 as depicted in FIG. 5. However, in other embodiments, programming engine 610 is embodied on an individual medical device, such as one of the plurality of coupled infusion pumps 612-616. In other embodiments, portions of the engines described herein can be spread across multiple devices, such as a discrete server or an infusion pump.

(45) The engines described herein can be constructed, programmed, configured, or otherwise adapted, to autonomously carry out a function or set of functions. The term engine as used throughout this document is defined as a real-world device, component, or arrangement of components implemented using hardware, such as by an application specific integrated circuit (ASIC) or field-programmable gate array (FPGA), for example, or as a combination of hardware and software, such as by a microprocessor system and a set of program instructions that cause the engine to implement the particular functionality, which (while being executed) transform the microprocessor system into a special-purpose device. An engine can also be implemented as a combination of the two, with certain functions facilitated by hardware alone, and other functions facilitated by a combination of hardware and software. In certain implementations, at least a portion, and in some cases, all, of an engine can be executed on the processor(s) of one or more computing platforms that are made up of hardware (e.g., one or more processors, data storage devices such as memory or drive storage, input/output facilities such as network interface devices, video devices, keyboards, mouse or touchscreen devices, etc.) that execute an operating system, system programs, and application programs, while also implementing the engine using multitasking, multithreading, distributed (e.g., cluster, peer-peer, cloud, etc.) processing where appropriate, or other such techniques. Accordingly, each engine can be realized in a variety of physically embodied configurations, and should generally not be limited to any particular implementation exemplified herein, unless such limitations are expressly called out. In addition, an engine can itself be composed of more than one sub-engines, each of which can be regarded as an engine in its own right. Moreover, in the embodiments described herein, each of the various engines corresponds to a defined autonomous functionality; however, it should be understood that in other contemplated embodiments, each functionality can be distributed to more than one engine. Likewise, in other contemplated embodiments, multiple defined functionalities may be implemented by a single engine that performs those multiple functions, possibly in parallel or series with, and/or complementary to other functions, or distributed differently among a set of engines than specifically illustrated in the examples herein.

(46) Drug library 618 comprises a database of functional sets including a set of medications to be infused for each level. In an embodiment, drug library 618 is substantially similar to the portion of drug library 300 depicted in FIG. 3. In embodiments, drug library 618 can comprise a set of medications defining the respective medication amounts and infusion rates that are varied depending on a number of factors, including inputs related to hospital data 602, patient data 604, and sensor data 606. For example, the amounts and infusion rates of the set of medications for a selected functional set for a 200 lb male patient can be significantly different than for a 130 lb female patient. Drug library 618 is configured to store these differing sets of medications. As such, multiple sets of medications can be defined for each functional set.

(47) Processor 620 comprises processing logic and suitable hardware for implementing the processing logic to evaluate received hospital data 602, patient data 604, sensor data 606, and procedure data 608 and determine an appropriate set of infusions from drug library 618. Processor 620 is further configured to command programming of a set of infusions to infusion pumps 612-616. In embodiments, processor 620 can be operably coupled to memory (not shown in FIG. 6).

(48) In embodiments, processor 620 is further configured to suggest or automatically adjust the previously-determined set of infusions or infusion parameters. For example, additional hospital data 602, patient data 604, sensor data 606, and/or procedure data 608 can be received and evaluated to modify or adjust infusion parameters. In an embodiment, such additional hospital data 602, patient data 604, sensor data 606, and/or procedure data 608 can be received and evaluated after the initial set of infusions or infusion parameters have been commanded and are operational. In embodiments, evaluation of hospital data 602, patient data 604, sensor data 606, and/or procedure data 608 can be on regular intervals or continuous.

(49) Communications engine 622 comprises communication logic and suitable hardware for receiving hospital data 602, patient data 604, sensor data 606, and procedure data 608. Further, communications engine 622 comprises communication logic and suitable hardware for transmitting programming commands to infusion pumps 612-616.

(50) Each of infusion pumps 612-616 can be substantially similar to infusion pump 210 as depicted and described with respect to FIG. 2. In embodiments, additional or fewer infusion pumps can be programmed.

(51) In operation, system 600 is configured for the programming of infusion pumps 612-616 according to a functional set. Hospital data 602, patient data 604, sensor data 606, and procedure data 608 are input into programming engine 610. In an embodiment, hospital data 602, patient data 604, sensor data 606, and procedure data 608 are received by communications engine 622. In an embodiment, the data received by communications engine 622 is stored. For example, memory operably coupled to processor 620 can store the received data.

(52) Processor 620 evaluates received hospital data 602, patient data 604, sensor data 606, and procedure data 608 in view of drug library 618. For example, as selected by procedure data 608, a set of medications to be infused is chosen. Processor 620 can then utilize drug library 618 in view of received hospital data 602, patient data 604, and sensor data 606 to select a particular set of medications specific for the unique combination defined by the received data.

(53) Subsequently, processor 620 transmits a programming signal to any of infusion pump 612, infusion pump 614, infusion pump 616, or additional infusion pumps (not shown in FIG. 6). As a result, the pumps receiving the programming signal, such as infusion pump 612, infusion pump 614, infusion pump 616, or additional infusion pumps, are programmed for the respective infusion defined by drug library 618 for the selected procedure data 608 and the unique combination defined by the received hospital data 602, patient data 604, and sensor data 606.

(54) According to embodiments, grouping principles such as functional sets can be applied such that a hierarchy is adhered to so that higher levels are placed near the “top” with more specific concepts underneath. The higher the level, the less detail is presented to the user. The lower the level, the more detail is presented to the user. In embodiments, a drug library can be grouped according to various functional set hierarchies.

(55) For example, referring to FIG. 7A, a block diagram of an example functional set according to a hierarchy 700 in a hospital network is depicted, according to an embodiment. Hierarchy 700 generally comprises a hospital network level 702, a hospital level 704, a department level 706, a procedure level 708, and an infusion level 710.

(56) As depicted, hospital network 702 generally comprises one or more hospitals 704. A particular hospital 704 generally comprises one or departments 706. A particular department 706 generally comprises one or more procedures 708. Each procedure 708 generally comprises one or more infusions 710. In embodiments, any of the aforementioned levels can be omitted such that programming of infusions does not adhere to the hierarchical flow depicted in FIG. 7A. For example, depending on the procedures and guidelines for the particular hospital network 702 and/or hospital 704, additional or fewer functional sets can be utilized.

(57) In embodiments, referring again to FIG. 7A, programming hierarchies can be implemented at any of the aforementioned levels. As a result, programming hierarchies can be carried down through the lower functional sets. For example, at hospital network 702, generalized infusions 710 common to all hospitals 704 in hospital network 702 can be defined. In turn, all of the generalized infusions 710 common to all hospitals 704 in hospital network 702 are carried through the lower levels and thus available to all departments 706 and procedures 708. In this way, particular hospital networks 702 can define sets of infusions 710 unique to that hospital network 702.

(58) Likewise, at hospital 704, generalized infusions 710 common to all departments 706 in a particular hospital 704 can be defined. In turn, all of the generalized infusions 710 common to all departments 706 in hospital 704 are carried through the lower levels and thus available to all procedures 708. In this way, particular hospitals 704 can define sets of infusions 710 unique to that hospital 704.

(59) Similarly, each department 706 can define sets of infusions 710 unique to that particular department 706. For example, infusions 710 that are specific to the “surgery” department 706 can be implemented such that the higher level infusion definitions are available for use, as well as the surgery-specific infusions defined at the department 706 level.

(60) In another example, referring to FIG. 7B, a block diagram of an example hierarchy 750 in a hospital network is depicted, according to an embodiment. Hierarchy 750 generally comprises a hospital network level 752, a hospital level 754, a department level 756, a procedure level 758, and an infusion level 760. In the example depicted, infusions 760 can be defined at any level within hierarchy 750. In embodiments, infusions 760 are defined such that no generalized infusions are carried through the lower functional sets.

(61) Referring to FIG. 8, a flowchart of a method 800 for procedure-based programming of a plurality of infusion pumps in a functional set is depicted, according to an embodiment.

(62) At 810, a plurality of infusion pumps are implemented. For example, each of the plurality of infusion pumps can be substantially similar to any of the infusion pumps described herein, such as infusion pump 210 as depicted in FIG. 2. In an embodiment, the plurality of infusion pumps can be activated, turned on, or otherwise prepared for operation. In embodiments, the plurality of infusion pumps are operably coupled to a patient. In another embodiment, the plurality of infusion pumps are staged for coupling to a patient.

(63) At 820, a drug library including one or more functional sets is implemented. For example, the drug library can be substantially similar to any of the drug libraries described herein, such as the template of the portion of generic drug library 300 as depicted in FIG. 3. In an embodiment, implementing the drug library comprises receiving inputs that define the functional set and the corresponding set of medications to be infused. In embodiments, other inputs can define the number or type of infusion pumps needed or other criteria or fields related to the set of medications to be infused.

(64) At 830, input data is received. In an embodiment, input data comprises a functional set selection. For example, referring to FIG. 6, procedure data 608 is input into programming engine 610 as the selected functional set. In other embodiments, input data further comprises hospital data, patient data, and/or sensor data. For example, referring again to FIG. 6, inputs such as hospital data 602, patient data 604, and sensor data 606 are input into programming engine 610. Input data can be received by manual input into the programming engine, such as on a pump or embedded server as aforementioned. In other embodiments, input data can be automatically transmitted to the programming engine.

(65) Referring again to FIG. 8 at 840, a set of medications is obtained from the drug library implemented at 820. In an embodiment, the functional set selection corresponds to a set of medications in the drug library. In another embodiment, referring to FIG. 6, processor 620 evaluates received hospital data 602, patient data 604, sensor data 606, and procedure data 608 in view of drug library 618. As selected by procedure data 608, a set of medications to be infused is chosen. Processor 620 can then utilize drug library 618 in view of received hospital data 602, patient data 604, and sensor data 606 to select a particular set of medications specific for the unique combination defined by the received input data.

(66) Referring again to FIG. 8 at 850, the plurality of infusion pumps are programmed according to the set of medications obtained from the drug library at 840. For example, again referring to FIG. 6, processor 620 transmits a programming signal to any of the plurality of infusion pumps, such as infusion pump 612, infusion pump 614, and infusion pump 616. In an embodiment, each of the infusion pumps receives a set of instructions that are part of the larger set of instructions. Each pump can then parse the received message for its particular protocol and delivery characteristics. In another embodiment, each pump is individually sent programming instructions or commands for its particular protocol and delivery characteristics such that parsing of a larger message is not needed. The pumps are then respectively programmed for operation according to the set of medications defined by the drug library.

(67) Referring again to FIG. 8 at 860, the plurality of infusion pumps respectively infuse the patient according to the set of medications programmed at 850. In an embodiment, at 860, a clinician loads the drug container onto each of the plurality of pumps per its respective programmed setup configuration. The clinician can then verify the information is correct on each of the plurality of pumps. In an embodiment, the clinician can then start each pump to initiate their respective infusion processes.

(68) Various embodiments of systems, devices, and methods have been described herein. These embodiments are given only by way of example and are not intended to limit the scope of subject matter hereof. It should be appreciated, moreover, that the various features of the embodiments that have been described may be combined in various ways to produce numerous additional embodiments. Moreover, while various materials, dimensions, shapes, configurations and locations, etc. have been described for use with disclosed embodiments, others besides those disclosed may be utilized commensurate with the scope of subject matter hereof.

(69) Persons of ordinary skill in the relevant arts will recognize that subject matter hereof may comprise fewer features than illustrated in any individual embodiment described above. The embodiments described herein are not meant to be an exhaustive presentation of the ways in which the various features of subject matter hereof may be combined. Accordingly, the embodiments are not mutually exclusive combinations of features; rather, the subject matter hereof may comprise a combination of different individual features selected from different individual embodiments, as understood by persons of ordinary skill in the art.

(70) Any incorporation by reference of documents above is limited such that no subject matter is incorporated that is contrary to the explicit disclosure herein. Any incorporation by reference of documents above is further limited such that no claims included in the documents are incorporated by reference herein. Any incorporation by reference of documents above is yet further limited such that any definitions provided in the documents are not incorporated by reference herein unless expressly included herein.

(71) For purposes of interpreting the claims of subject matter hereof, it is expressly intended that the provisions of Section 112, sixth paragraph of 35 U.S.C. are not to be invoked unless the specific terms “means for” or “step for” are recited in a claim.