Intelligent infusion device with adjustable automation levels

Abstract

Certain aspects of the disclosure provide systems and methods for intelligent infusions, for example, with a plurality of automation states. In particular, an infusion system may be in one state of a plurality of automation states, whereby infusion parameters for adjusting the infusion system may be received in various manners, based on the state of the infusion system. In some automation states, a clinician may be alerted to changes in the infusion system. In some automation states, a clinician may confirm a recommended infusion parameter. In some automation states, an infusion system may implement an infusion parameter.

Description

INTELLIGENT INFUSION DEVICE WITH ADJUSTABLE AUTOMATION LEVELSCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This Application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 559,147, filed on February 28, 2024, the entire contents of which are hereby incorporated by reference.BACKGROUNDField

[0002] Aspects of the present disclosure relate to systems and methods for intelligent infusions systems operating in a plurality of automation states.Description of Related Art

[0003] Infusion systems are a common medical device for administration of therapeutic fluids to a subject, such as intravenously. Previously, fluid containers were elevated to utilize gravity to drop the fluid through a line to the subject. Now, a pump is used to control flow of the therapeutic fluid to the subject in an accurate and consistent manner. An infusion pump controller controls the pumping module to pump fluid from a fluid container through an infusion set to the patient.

[0004] Generally, an infusion system is programmed to pump fluid at a specific flow rate and up to a specific volume in order to administer a specific dose of a treatment. In particular, the infusion pump controller may be configured to receive one or more operational parameters used to control operation of the infusion pump. The one or more operational parameters may include one or more of flow rate, volume, velocity, infusion time, and / or the like. The infusion pump controller then controls operation of the infusion pump according to the one or more operational parameters.

[0005] Typically, a clinician, such as a nurse, enters the operational parameters at the infusion system, for example, through a user interface coupled to the infusion system to start an infusion. In some cases, the infusion system may be connected to a hospital system, such as an EMR and / or pharmacy system to receive operational parameters for an infusion order.A clinician may enter the infusion order through the EMR or pharmacy system. The nurse, then, sets up the infusion system for the patient and starts the infusion order.

[0006] As the infusion proceeds, clinicians monitor the patient to determine the progress of the infusion and changes in patient status or symptoms. The clinician may pause, resume, or change an operational parameter of the infusion based on monitoring the patient.

[0007] As medical devices increase in integration and interconnectivity, autonomous control of an infusion system may be possible. For example, one or more patient monitoring devices, such as a vital signs monitor, may interface with an infusion system to autonomously control the infusion.SUMMARY

[0008] Certain aspects provide a method, comprising: assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitoring device; receiving a set of data comprising a value for the patient parameter measured by the patient monitoring device and an initial operational parameter of the infusion system; determining a state of the infusion system; receiving an updated operational parameter of the infusion system based on the state of the infusion system; adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

[0009] Other aspects provide processing systems configured to perform the aforementioned methods as well as those described herein; non-transitory, computer- readable media comprising instructions that, when executed by one or more processors of a processing system, cause the processing system to perform the aforementioned methods as well as those described herein; a computer program product embodied on a computer readable storage medium comprising code for performing the aforementioned methods as well as those further described herein; and a processing system comprising means for performing the aforementioned methods as well as those further described herein.

[0010] The following description and the related drawings set forth in detail certain illustrative features of one or more aspects.DESCRIPTION OF THE DRAWINGS

[0011] The appended figures depict certain aspects and are therefore not to be considered limiting of the scope of this disclosure.

[0012] FIG. 1 depicts an example intelligent infusion system.

[0013] FIG. 2 depicts an example workflow for an intelligent infusion system operating in various automation states.

[0014] FIG. 3 depicts an example user interface of an intelligent infusion system.

[0015] FIGS. 4A-4B depict an example intelligent infusion system in a first automation state.

[0016] FIGS. 5A-5C depict an example intelligent infusion system in a second automation state.

[0017] FIGS. 6A-6C depict an example intelligent infusion system in a third automation state.

[0018] FIGS. 7A-7B depict an example intelligent infusion system in a fourth automation state.

[0019] FIG. 8 depicts an example infusion system.

[0020] FIG. 9 depicts an example syringe infusion system.

[0021] FIG. 10 depicts an example method for intelligent infusion in various automation states.

[0022] FIG. 11 depicts an example computing device with which aspects of the present disclosure can be performed.

[0023] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the drawings. It is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.DETAILED DESCRIPTION

[0024] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for intelligent infusions systems operating in a plurality of automation states.

[0025] Autonomous control of infusion systems may be implemented as part of open loop, closed loop, or semi-closed loop configurations. In an open loop configuration, a clinician may monitor a patient and infusion system to determine whether any changes to the infusion system should be made. The clinician may monitor the patient for changes in status or symptoms. The clinician may further use laboratory or imaging testing, patient history, and clinical experience to make changes to the infusion system. Additionally, patient monitoring devices, such as vital signs monitors, blood pressure monitors, sensors, or other monitoring devices may measure physiological characteristics of the patient for the clinician to use.

[0026] Recently, alarm and alert systems may been implemented for infusion systems and patient monitoring devices. An alarm system may have an audible alert, visual alert, or send notifications to alert clinicians to a change in patient status or infusion system status. For example, an audible alert may sound when a vital signs monitor detects the patient’s heart rate has dropped below a safe threshold. As another example, a visual error message may appear on a user interface of an infusion system when the infusion system detects an issue with the pump. The clinician may then respond to the alarm system by adjusting the infusion system, such as changing an operational parameter, pausing the infusion system, adding another therapy to the infusion fluid, or the like.

[0027] In a semi-closed loop system, a control algorithm or Al system may generate suggested operational parameter(s) for the infusion based on monitoring data. For example, a control algorithm may utilize a patient’s heart rate, as measured by a vital signs monitor, to generate suggested operational parameters for the infusion system. The suggested operational parameters are provided to the clinician for confirmation before implementation at the infusion system. In some cases, a clinician may override or input different operational parameters, rather than use the suggested operational parameters.

[0028] A semi-closed loop system may also utilize an alarm system, for example, an audible alert to the patient’s heart rate dropping below a safe threshold. Further, the semi-closed loop system may provide the suggested operational parameters with the alert for the clinician to review and confirm, or override.

[0029] In a closed loop system, the control algorithm or Al system generates the operational parameter(s) for the infusion based on the monitoring data, and implements the operational parameters without clinician confirmation. A closed loop system may also use an alarm system and provide information regarding the operational parameters implemented in response to the alert.

[0030] Generally, medical devices are configured as part of one of these systems and configured for operation only in that system. For example, an open loop system is conventionally not configured with a control algorithm and will not operate as a closed loop system. An infusion pump controller is generally configured to receive operational parameters from a source and control the infusion pump to implement those operational parameters. Further, infusion systems are not configured to change sources during an infusion event.

[0031] Aspects described herein overcome the technical limitations of conventional systems, e.g., open, closed, or semi-closed systems, through an infusion system configuration which may be dynamically adjusted to operate in a plurality of automation states, whereby the state of automation may be flexed based on the particular infusion order. The plurality of automation states described herein enable automated control of an infusion system. The plurality of automation states may include aspects of open, closed, and semiclosed loops systems, as well as additional automation limits and safety thresholds to provide safe and accurate autonomous control. For example, the plurality of automation states may include lower levels of automated control (e.g., more user input), and higher levels of automated control (e.g., less or no user input). The plurality of automation states allows for dynamic and adaptable automated control of infusion systems.

[0032] Further, in some aspects, the state of automation of the infusion system may be adjusted during an infusion event, for example, to account for changes in patient and / or infusion system status. The automation described herein may form part of an infusion system or patient monitoring device, such that adjustments to the state of automation does not require switch devices, or addition and removal of devices to the system.

[0033] In some aspects, an automation state of the infusion system may be based on the infusion order, for example, the type of therapy, one or more operational parameters, the type of infusion system, a care area of the infusion system, a patient type, a clinician or clinician type, or the like. The automated infusion system may then adapt to the desired automation state for each particular infusion order.

[0034] For example, a certain type of therapy may be associated with a lower automation state, such as where the adverse risk of the type of therapy is high, while another type of therapy may be associated with a higher automation state, such as where the other type of therapy is associated with a low adverse risk. Thus, beneficially, the automated infusion system may be dynamically adaptable to automate various types of therapies.

[0035] In some aspects, a clinician may set or assign the infusion system to an automation state. In some aspects, an infusion system may assign the state of automation based on the infusion order.

[0036] Further, the automated infusion system may be associated with automation limits, which may limit or adjust the automation state where the automation system is uncertain or exceeds safety levels. Such automation limits may increase safety by limiting automated control of the infusion system in certain cases.Example Intelligent Infusion System

[0037] FIG. 1 depicts an example intelligent infusion system 100 for a plurality of autonomous operation of a medical device, such as an infusion system 114. Infusion system 114 is an electromechanical device for infusing therapeutic fluids into a patient 110 in a controlled and precise manner. Exemplary infusion systems may include a syringe pump or a large volume pump, such as depicted in FIG. 8 or FIG. 9. Infusion system 114 comprises an infusion pump controller 118 configured to control operations of infusion system 114. In general operation, therapeutic fluid is loaded into an infusion pump 116, for example, in a syringe, bottle, bag, or other storage container, and the infusion system 114 is configured to pump, or infuse, the therapeutic fluid according to operational parameters of the infusion pump 116, including, for example, flow rate, volume, and / or time to administer a specific dose of treatment, the infusion pump controller 118 and / or the infusion pumps 116 may include one or more buttons, controls, displays, keys, or the like to control operations of theinfusion system 114. In some examples, a clinician may utilize the infusion pump controller 118 to enter operational parameters or otherwise control operation of the infusion pumps 116. Further, the infusion pump controller 118 may display drug entries from the drug library. Each of the associated sets of drug delivery parameters includes information selected from a group of parameters including drug concentration, drug delivery rate, drug dose, and bolus size. The electronically loaded drug library contains a list of available mode options specifying the units available for expressing drug delivery information, and the drug infusion pump offers the user the list of available mode options from which to make a selection when the electronically loaded drug library is in the pump. In the case of a syringe pump, the electronically loaded drug library may include a list of names of syringe manufacturers identifying syringes that can be used in the drug infusion pump, and the drug infusion pump offers the user the list of names of syringe manufacturers.

[0038] In some aspects, the infusion pump controller 118 may contain a memory comprising a drug library or libraries, an event log or logs, and pump configuration settings, such as, but not limited to, profiles to be used in particular care areas such as ICU, PED, etc. The memory may be electronically loadable memory such as non-volatile memory (e.g., EEPROM). Drug libraries stored on infusion systems (which illustratively contain such information as the drug names, ranges of delivery parameter values such as proper concentrations, dosage units, and dose limits) may be used to perform drug calculationbased infusions in a clinical setting. A drug library stored within the infusion system may include clinical order settings such as limits set by the clinical institution for each drug of the library (also referred to as “guardrails” herein). Such limits may take the form of maximum and minimum dosages for each drug which may be made dependent on patient factors or other factors associated with delivery of the drug. For example, the dosage limits may vary depending on the weight of the patient or body surface area (“BSA”), depending on the unit or ward (e.g., a care area) of the medical institution in which the drug is being used (for example neonatal care unit (NICU), the intensive care unit (ICU), etc.), and depending on other factors. An alarm may be provided if the clinician sets the pump to operate outside the range between the limits for a particular drug. In some cases, the alarm may be overridden and in other cases it may not. The medical facility may establish “soft” limits for each drug, which may be overridden by the nurse, and “hard” limits which may not. In either case where a limit is exceeded, a pump data log or other processor incommunication with the infusion pump may record each such limit event for later analysis where the attempted setting is higher than the maximum or lower than the minimum dosage. Although depicted in this example as an infusion system, in some examples, other patient care devices or medical devices may be utilized.

[0039] Infusion system 114 is further configured to transmit and receive data, such as data related to the infusion including infusion parameters, infusion data, operational data, or the like. Infusion system 114 may use network 102 to transmit and receive data. In some aspects, infusion system 114 is configured to transmit data to a hospital information system (HIS) 122 of a medical center of the infusion system 114.

[0040] For example, HIS 122 is configured with an electronic medical recordation (EMR) system 124, a pharmacy system 126, a laboratory system 128, a medication ordering system 130, or the like, for the medical center, to facilitate communications such as transmitting and receiving laboratory testing data, prescription data, documentation of a patient’s medical history, diagnosis, treatments, laboratory data, or the like. HIS 122 may include, or be configured to interface with other hospital systems such as an admissions system, a billing system, a biomedical engineering system, a central supply system, unit station systems, or a medical decision support system.

[0041] In some aspects, the pharmacy system 126 includes a formulary and / or pharmacy information system. Pharmacy information systems may enable a safer physician medication order process. A pharmacy website (e.g., provided by the server) may provide the physician with a list of available drugs from which the physician may select. The pharmacy website may contain a drug library having the list of available drugs but may also contain and present to the physician the drug names associated with recommended dosages and dose limits that have been established or adopted by the medical center. In such a case where the physician need only select items from the computer screen rather than having to manually type in drug names and drug administration numbers (such as infusion rates, times, etc.) associated with administration of the medication, a more accurate medication process may result.

[0042] If a clinical order is for administration of a particular medication regimen, the order will be transmitted to the medical center’s pharmacy information system 126. The pharmacy reviews the order, and once the order has been prepared, the order may betransmited to a nurse station for matching with the appropriate patient. Formulary is an approved list of drugs for use (e.g., available to order for a patient) within a medical facility. Within a formulary, there may be indication for use information and / or concentrations and drug ranges approved for the medical center. As will be described further, a formulary may be used to define one or more medical device drug libraries, which may then be provided to infusion pumps within HIS 122. Inside the library, there is medication information such as drug names, concentration, diluent volume, strength, minimum or maximum infusion parameters for a drug, and other parameters. The establishment of these parameters, along with parameters for off-formulary orders, via the network 102, is useful for maintaining consistency across the medical center environment and ensuring an order is intelligible and executed according to expectations by other devices within the HIS 122 (e.g., an infusion system 114).

[0043] The patient 110 is coupled with a patient monitoring device 112 configured to monitor one or more patient parameters. For example, patient monitoring device 112 may be a vital signs monitoring device, physiological monitoring device (e.g., hear rate, blood pressure, ECG, EEG, pulse oximeter, intracranial pressure monitor, etc.), end tidal CO2 monitoring device, an analyte sensor, or other patient monitoring devices. In some aspects, a patient monitoring device may monitor more than one patient parameters. In some aspects, multiple patient monitoring devices may be coupled to the patient 110.

[0044] Patient monitoring device 112 is further configured to transmit and receive data, such as patient parameter(s) through network 102. For example, patient monitoring device 112 may send data related to one or more patient parameters to the HIS 122 or an intelligent infusion module 120.

[0045] Although depicted here as separate devices, in some cases, intelligent infusion module 120 may be integral to or form part of infusion system 114, patient monitoring device 112, or HIS 122. In some cases, the intelligent infusion module 120 may form part of a clinician device, such as a mobile device, a nurse station monitoring device, a computing device, or the like.

[0046] The network 102 may be a wired or wireless connection, such as by Ethernet, Wi-Fi, Bluetooth, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem or a cable modem. Any direct or indirect network connectionmay be used, including, but not limited to a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a micro wave link or a WLANS connection or other wireless connection.Example Automation State Workflow

[0047] FIG. 2 depicts an example workflow 200 for an intelligent infusion system, such as system 100 in FIG. 1.

[0048] Initially, at block 202, workflow 200 begins with associating the infusion system, such as infusion system 114 and a patient monitoring device, such as patient monitoring device 112 with a patient, such as patient 110. In some aspects, associating the infusion system and / or the patient monitoring device with the patient may include a set up procedure for the infusion system and / or the patient monitoring device. The infusion system and / or the patient monitoring device may receive data associated with the patient, for example, a patient’s name, a hospital identification number, or other identifier of the patient. In some examples, a clinician may enter, such as through a user interface of the infusion system or the patient monitoring device, the patient’s identifier. In other examples, the patient identifier may be entered by scanning an identifier number, such as a barcode on a hospital bracelet, an electronic data tag, such as a radio frequency identification device (“RFID”) tag, or the like.

[0049] Optionally, the infusion system and / or the patient monitoring device may be associated with a clinician. The infusion system and / or the patient monitoring device may receive data associated with a clinician, for example, a clinician’s name, hospital identification number, etc. or another identifier of the clinician. In some examples, a clinician may enter, such as through a user interface of the infusion system and / or the patient monitoring device, the clinician’s identifier. In other examples, the clinician identifier may be entered by scanning an identification number, such as a barcode on an identification badge, an electronic data tag, such as an RFID tag, or the like. In some aspects, the infusion system is not associated with any clinician, for example, when a clinician identifier is not entered, a clinician identifier entered incorrectly, a clinician is not found, or the like, and the patient note mode is disabled until the infusion system is associated with a clinician.

[0050] In some aspects, optionally, workflow 200 may include assigning an automation state 203 of the infusion system. An automation state may be assigned based on one or more characteristics of the infusion system, the patient, and / or the patient monitoring device. An automation state may be selected from a set of available automation sets, for example, two automation states, three automation states, or four automation states. Although four automation states are described herein, additional, or fewer automation states may exist. Further, in some aspects, a set of available automation states may be a subset of automation stations, for example, two of four automation states. In some aspects, the automation states available to be assigned, e.g., the set of available automation states, may be determined by a clinical center, such as a hospital, an outpatient clinic, nursing center, or the like. In some aspects, the automation states available to be assigned may be determined based on a care area of the clinical center, such as a floor or unit, e.g., a neonatal intensive care unit (NICU), an intensive care unit (ICU), a post anesthesia care unit (PACU), or the like. In some aspects, the automation states available to be assigned may be set based on characteristics of the infusion system, the patient monitoring system, and / or the patient. For example, automation states available for a first type of infusion systems may be different from automation states available for a second type of infusion.

[0051] In some aspects, an automation state of the infusion system may be assigned based on a selection by the clinician, such as through a user interface of the infusion system, through a user interface of the patient monitoring device, or through a user interface associated with an intelligent infusion module, such as module 120. FIG. 3 depicts an example user interface 300 for selecting an automation state of the infusion system. User interface 300 depicts an element 302 for selecting a therapy for the infusion, in the depicted example, Therapy 1. Then, for therapy 1, an automation level is selected using various elements. A first element 304A may be used to select a first automation level, e.g., Fevel 2 - Alert. In the first automation level, an alert may be generated based on a condition, such as described in further detail at block 222. A second element 304B may be used to select a second automation level, e.g., Fevel 2 - Automatic Pause. In the second automation level, the infusion may be paused based on a condition, such as described in further detail at block 224. A third element 304C may be used to select a third automation level, e.g., Level 3 - Clinical Recommendation. In the third automation level, a recommendation may be provided to adjust the infusion to ensure one or more conditions are met, such as describedin further detail at block 234. A fourth element 304D may be used to select a fourth automation level, e.g., Level 4 - Fully Automated. In the fourth automation level, an adjustment to the infusion may be implemented to ensure one or more conditions are met, such as described in further detail at block 242.

[0052] In some aspects, an automation state of the infusion system may be assigned by the intelligent infusion module 120, based on the one or more characteristics of the infusion system, the patient, and / or the patient monitoring device. For example, characteristics of an infusion order, such as type of fluid or operational parameters, may be associated with a subset of automation states and only the subset is available to be assigned. In some aspects, the automation state may be assigned a default automation state, e.g., as determined by the medical center, the clinician, etc., and infusion systems may be assigned the default automation state unless otherwise specified by a clinician. In some aspects, there may be a preferred or priority default automation state that may be assigned, unless characteristics of the infusion system, the patient, and / or the patient monitoring device indicate another automation state. For example, characteristics of the infusion system, the patient, and / or the patient monitoring device may indicate a higher (or lower) automation state, e.g., increased automation or decreased automation, than the preferred or priority default automation state.

[0053] Characteristics of the infusion system may include, for example, firmware version, one or more module types, care area, power source (e.g., battery or plugged in power), power level (e.g., percentage of available battery charge such as 100% battery, 20% battery, etc.), wireless connection status (e.g., connected to a Wi-Fi network or not connected), signal strength of the wireless connection (e.g., higher signal strength associated with a higher automation state), or the like. For example, some automation states may incur additional battery usage (e.g., due to operation of the automation state) and an automation state may be assigned to reduce additional battery usage. Other characteristics of the infusion system may also incur additional battery usage, such as poor or weak wireless connection. In one example, where the infusion system is operating on battery, has a weak wireless connection (e.g., incurring additional battery usage), and has less than a threshold battery level (e.g., less than 50% battery), the automation state may be assigned to a lower state (e.g., a first or second automation state), which may be associated with decreased additional battery usage to conserve battery power.

[0054] Further, characteristics of the infusion system may also include alarm status of the infusion system. For example, a currently alarming infusion system may be assigned a lower automation state (such as a first or second automation state). An infusion system not currently alarming or with a period of time since a previous alarm may be assigned a higher automation state (e.g., a third or fourth automation state).

[0055] Characteristics of the patient monitoring device may include, for example, firmware version, one or more module types, care area, power source (e.g., battery or plugged in power), power level (e.g., percentage of available battery charge such as 100% battery, 20% battery, etc.), wireless connection status (e.g., connected to a Wi-Fi network or not connected), signal strength of the wireless connection (e.g., higher signal strength associated with a higher automation state), or the like. For example, some automation states may incur additional battery usage (e.g., due to operation of the automation state) and an automation state may be assigned to reduce additional battery usage. As another example, a weaker wireless connection may be associated with a higher chance of misread or lost data, e.g., due to the weak signal, and thus may be associated with a lower automation state (e.g., a first or second automation state).

[0056] Furthermore, characteristics of the patient monitoring device may also include a duration of use of the patient monitoring device. For example, a patient monitoring device may become less reliable the longer the device is used due to overuse. For a patient monitoring device used for a time period over an overuse threshold, one or more automation states may be unavailable.

[0057] Workflow 200 continues at block 204 with assigning a target zone for the patient. A target zone may be a value, or range of values, for a patient parameter. In some cases, a target zone may be associated with an upper or lower limit. A target zone may be set for each patient parameter of a set of patient parameters. For example, a target zone for a heart rate may be between 60 and 80 beats per minute (BPM) as measured by a heart rate monitor. In some aspects, a target zone for a patient parameter may be a preferred zone or normal zone for the patient parameter. For example, a target zone may be a preferred zone for the patient parameter, whereby the infusion may continue when the patient is in the target zone.

[0058] In some aspects, a patient parameter may also be associated with a safe zone, whereby a patient parameter value outside the safe zone may be associated with an urgentor emergent alert or alarm. For example, a safe zone for a heart rate may be 20-200 BPM, whereby below 20 BPM the patient may be in bradycardia and above 200 BPM the patient may be in tachycardia. In some aspects, the target zone for the patient may be based on the infusion order, for example, one or more initial operational parameters for the infusion system and the type of fluid to be infused.

[0059] In some aspects, the target zone may be assigned based on a selection by the clinician, such as through a user interface of the infusion system, through a user interface of the patient monitoring device, or through a user interface associated with an intelligent infusion module, such as module 120.

[0060] In some aspects, the target zone may be assigned by the intelligent infusion module 120, based on the one or more characteristics of the infusion system, the patient, and / or the patient monitoring device. For example, characteristics of an infusion order, such as type of fluid or operational parameters, may be associated with a target zone for a patient parameter. In some cases, the target zone may be based on a range specified in a drug library for the type of fluid. For example, for an antihypertensive, a target zone for blood pressure may be between 130-140 mmHg / 80-90 mHg, as specified in the drug library. In some cases, a target zone may be assigned by the intelligent infusion module 120, and confirmed by a clinician.

[0061] Workflow 200 then continues at block 206 with receiving infusion data, for example, pump data 115 from the infusion system 114 and one or more patient parameters 117 from the patient monitoring device 112. Pump data 115 may include one or more operational parameters of the infusion system, for example, a flow rate, volume, velocity, infusion time, or the like. In some cases, pump data 115 may further include other pump information, such as a type of pump, a care area of the pump, or the like. The one or more patient parameters 117 may include a value for each patient parameter.

[0062] In some cases, the pump data 115 and the patient parameters 117 are obtained over a period of time, for example, 1 hour, 2 hours, 6 hours, 24 hours, etc. In some cases, the time period may be from a start of the infusion.

[0063] Workflow 200 continues at block 208 with determining a state of the infusion system. The state of the infusion system may be determined based on the assigned state.

[0064] In some aspects, the state of the infusion system may be determined based on an updated state. For example, in some aspects, the state of the infusion system may be updated, for example, transition from an initial state to the updated state. In some aspects, the state may transition based on receiving an updated state from a clinician, for example, entered at a user interface of the infusion system, a user interface of the intelligent infusion module, or a clinician device.

[0065] In some aspects, the state may transition based on data associated with the infusion system, such as patient parameter 117 or pump data 115. For example, where the data exceeds an operational threshold, the state may transition to a lower state, e.g., from a fourth state to a third state.

[0066] An operational threshold may be associated with a limit on automatic or autonomous operation of the infusion system. An infusion pump may be configured with operational limits to prevent improper or dangerous operation of the infusion pump. Such operational limits may be based on, for example, the mechanical capabilities of the infusion pump or safety limits related to the drug therapy administered by the infusion pump. An operational threshold may be based on operational limits or large changes in operational parameters which may be associated with improper or dangerous operation of the infusion pump.

[0067] For example, based on additional data and additional operational parameters, an operational parameter may be determined to be exceeded. The state of the infusion may transition between automation states, for example, from a fourth automation state to a third automation state. Then, beneficially, clinician input may be required to implement the additional operational parameter, e.g., a confirmation or other entry, to ensure safe operation of the infusion pump. In some aspects, an alert of the transition between automation states may be displayed on the user interface of the infusion system, a user interface of the intelligent infusion module, or on a clinician device.

[0068] Workflow 200 may then continue based on the state of the infusion system determined at block 208. For example, where the infusion system is determined to be in a first automation state 210, workflow 200 continues to block 212 with receiving an updated operational parameter for the infusion system from a user. A user may be the clinician associated with the infusion system, or another clinician authorized to adjust an infusionsystem. In some aspects, the user may enter the updated operational parameter on a user interface of the infusion system. In some aspects, the user may enter the updated operational parameter on a user interface of the intelligent infusion module, and the intelligent infusion module may transmit the updated operational parameter to the infusion system, for example, to an infusion controller configured to control the infusion pump to operate based on the operational parameter. In some aspects, the user may enter the updated operational parameter via a clinician device. The clinician device transmits the updated operational parameter to the infusion system. Then, workflow 200 continues to block 216 with adjusting the operational parameter of the infusion system from the initial operational parameter to the updated operational parameter. Further, in some examples, the workflow 200 further includes sending, to an EMR, such as through HIS 122, the set of data, and the updated operational parameter.

[0069] FIGS. 4A and 4B depict an example of an intelligent infusion system 400 in a first automation state. A patient 410 is coupled to an infusion system 414 and a patient monitoring device 412. Initially, patient monitoring device sends one or more patient parameters 417A to an intelligent infusion module 420. In the depicted example, biographical data 417B is also provided to the intelligent infusion module 420. Biographical data 417B may include patient data, historical data, demographic data, or the like of the patient 410. In some cases, biographical data 417B may be received from an EMR for the patient 410. In some examples, biographical data 417B may also include laboratory data and / or imaging data. The infusion system 414 also sends infusion pump data 415 to the intelligent infusion module 420.

[0070] As depicted in FIG. 4A intelligent infusion module 420 is configured to display the data, for example, the one or more patient parameters 417A, and the infusion pump data 415 on a user interface 420A of the intelligent infusion module 420. In response, a clinician may enter one or more update operational parameters based on the data. Then, as depicted in FIG. 4B, the user interface 420B of the intelligent infusion module 420, displays the information sent to the patient’s EMR regarding the infusion data and the updated operational parameters. Specifically, user interface 420B depicts a patient parameter value and infusion parameter value at 5 times during an infusion period. Additionally, interface 420B also depicts two manual infusion flow rate changes entered by a clinician.

[0071] Returning to FIG. 2, where the infusion system is determined to be in a second automation state 220, workflow 200 continues to block 222 with determining a zone threshold associated with the target zone is exceeded based on the set of data. A zone threshold may be an upper limit of the target zone. For example, where the target zone for the patient’s heart rate is 60-80 BPM, and the patient’s heart rate is 90 BPM, the upper limit of the target zone is exceeded. A zone threshold may also be a lower limit of the target zone. For example, for the target zone for the patient’s heart rate is 60-80 BMP, a lower limit zone threshold may be 60, and when the patient’s heart rate is below 60 BMP, the lower limit zone threshold has been exceeded. In some cases, a target zone may be associated with only an upper or lower limit. For example, a zone threshold may be maximum or minimum value for the patient parameter.

[0072] In some aspects, optionally, workflow 200 continues to block 224, with stopping the infusion based on determining the zone threshold associated with the target zone is exceeded.

[0073] Workflow 200 may then continue to block 226, either directly from block 222 or from block 224, with generating a notification based on the zone threshold being exceeded. A notification may comprise information about the patient parameter out of target zone, or a zone threshold is exceeded. At block 228, workflow 200 continues with displaying, on a user interface associated with the infusion system, the notification. In some aspects, the notification may be transmitted to a clinician device for display on the clinician device.

[0074] Workflow 200 then continues to block 214 with receiving an updated operational parameter for the infusion system from a user. Block 214 may operate substantially similarly to block 212. Then, workflow 200 continues to block 216 with adjusting the operational parameter of the infusion system from the initial operational parameter to the updated operational parameter. Further, in some examples, the workflow 200 further includes sending, to an EMR, such as through HIS 122, the set of data, and the updated operational parameter.

[0075] FIGS. 5A-5C depict an example of an intelligent infusion system 500 in a second automation state. A patient 510 is coupled to an infusion system 514 and a patient monitoring device 512. Initially, patient monitoring device sends one or more patientparameters 517A to an intelligent infusion module 520. In the depicted example, biographical data 517B is also provided to the intelligent infusion module 520. Biographical data 517B may include patient data, historical data, demographic data, or the like of the patient 510. In some cases, biographical data 517B may be received from an EMR for the patient 510. In some examples, biographical data 517B may also include laboratory data and / or imaging data. The infusion system 514 also sends infusion pump data 515 to the intelligent infusion module 520.

[0076] As depicted in FIG. 5A, an intelligent infusion module 520 is configured to display the data, for example, the one or more patient parameters 517A, and the infusion pump data 515 on a user interface 520A of the intelligent infusion module 520. Further, the user interface 520A includes a notification 521 A indicating the patient parameter X is above the target range or zone.

[0077] FIG. 5B depicts an alternative user interface 520B, where the target zone is associated with an upper limit. The notification 52 IB indicates that the patient parameter X is above the upper limit associated with the target zone.

[0078] In response to the notification 521A or 521B, a clinician may enter one or more update operational parameters based on the data. Then, as depicted in FIG. 5C, the user interface 520C of the intelligent infusion module 520, displays the information sent to the patient’s EMR regarding the infusion data and the updated operational parameters. Specifically, user interface 520C depicts a patient parameter value and infusion parameter value at 5 times during an infusion period. Additionally, interface 520C also depicts two manual infusion flow rate changes entered by a clinician.

[0079] Returning to FIG. 2, where the infusion system is determined to be in a third automation state 230, workflow 200 continues to block 232 with determining an updated operational parameter based on the set of data. An updated operational parameter may be determined by a non-human, such as by a control algorithm or artificial intelligence (Al) system generating one or more operational parameters. For example, a control algorithm or Al system may process the set of data (e.g., patient parameter(s) 117 and / or pump data 115) received to determine updated operational parameter (s).

[0080] Workflow 200 then continues to block 234 with generating an infusion recommendation based on the updated operational parameter. An infusion recommendationmay comprise information for a notification or alert to a clinician of the updated operational parameter generated by the control algorithm or Al system.

[0081] Workflow 200 then continues to block 236 with displaying, on a user interface associated with the infusion system, the infusion recommendation. In some aspects, the notification may be transmitted to a clinician device for display on the clinician device. A user may be the clinician associated with the infusion system, or another clinician authorized to adjust an infusion system.

[0082] Workflow 200 then continues to block 238 with receiving, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is transmitted to the infusion system in response to receiving the confirmation from the user.

[0083] In some aspects, the user may enter the confirmation on a user interface of the infusion system. In some aspects, the user may enter the confirmation on a user interface of the intelligent infusion module, and the intelligent infusion module may transmit the updated operational parameter to the infusion system, for example, to an infusion controller configured to control the infusion pump to operate based on the operational parameter. In some aspects, the user may enter the confirmation via a clinician device. The clinician device transmits the confirmation to the intelligent infusion module.

[0084] Then, workflow 200 continues to block 216 with adjusting the operational parameter of the infusion system from the initial operational parameter to the updated operational parameter. Further, in some examples, the workflow 200 further includes sending, to an EMR, such as through HIS 122, the set of data, and the updated operational parameter.

[0085] FIGS. 6A-6C depict an example of an intelligent infusion system 600 in a third automation state. A patient 610 is coupled to an infusion system 614 and a patient monitoring device 612. Initially, patient monitoring device sends one or more patient parameters 617A to an intelligent infusion module 620. In the depicted example, biographical data 617B is also provided to the intelligent infusion module 620. Biographical data 617B may include patient data, historical data, demographic data, or the like of the patient 610. In some cases, biographical data 617B may be received from an EMR for the patient 610. In some examples, biographical data 617B may also include laboratory dataand / or imaging data. The infusion system 614 also sends infusion pump data 615 to the intelligent infusion module 620.

[0086] As depicted in FIG. 6A, an intelligent infusion module 520 is configured to display the data, for example, the one or more patient parameters 617A, and the infusion pump data 615 on a user interface 620A of the intelligent infusion module 620.

[0087] FIG. 6B depicts a user interface 620B, where the patient parameter x is out of the target zone. The recommendation 621 indicates that to maintain patient parameter X in the target zone, the pump A infusion flow rate should be increased to 2.2 mT / hr. The clinician may select either the accept element 623 or the reject element 625. If the clinician selects the accept element 623, then the updated operational parameter, e.g., flow rate of 2.2 mT / hr, may be sent to the infusion system 614 for implementation.

[0088] Then, as depicted in FIG. 6C, the user interface 620C of the intelligent infusion module 620, displays the information sent to the patient’s EMR regarding the infusion data and the updated operational parameters. Specifically, user interface 620C depicts a patient parameter value and infusion parameter value at 5 times during an infusion period. Additionally, interface 620C also depicts a recommended infusion flow rate change accepted by a clinician.

[0089] Returning to FIG. 2, where the infusion system is determined to be in a fourth automation state 240, workflow 200 continues to block 242 with determining the updated operational parameter based on the set of data. Block 242 may operate substantially similarly to block 232.

[0090] In some aspects, workflow 200 continues with transmitting to the infusion system, the updated operational parameter and at block 216 adjusts the operational parameter of the infusion system from the initial operational parameter to the updated operational parameter.

[0091] In some aspects, from block 242, workflow optionally continues to block 250 with determining an automation threshold is exceeded based on the updated operational parameter.

[0092] Workflow 200 then continues to block 252 with generating an automation recommendation for the updated operational parameter based on the automation threshold being exceeded.

[0093] Workflow 200 continues to block 254 with displaying, on a user interface associated with the infusion system, the automation recommendation. At block 256, workflow 200 continues with receiving, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is transmitted to the infusion pump in response to receiving the confirmation. Blocks 254-256 may operate substantially similarly to blocks 236-238.

[0094] Then, workflow 200 continues to block 216 with adjusting the operational parameter of the infusion system from the initial operational parameter to the updated operational parameter. Further, in some examples, the workflow 200 further includes sending, to an EMR, such as through HIS 122, the set of data, and the updated operational parameter.

[0095] FIGS. 7A-7B depict an example of an intelligent infusion system 700 in a fourth automation state. A patient 710 is coupled to an infusion system 714 and a patient monitoring device 712. Initially, patient monitoring device sends one or more patient parameters 717A to an intelligent infusion module 720. In the depicted example, biographical data 717B is also provided to the intelligent infusion module 720. Biographical data 717B may include patient data, historical data, demographic data, or the like of the patient 710. In some cases, biographical data 717B may be received from an EMR for the patient 710. In some examples, biographical data 717B may also include laboratory data and / or imaging data. The infusion system 714 also sends infusion pump data 715 to the intelligent infusion module 720.

[0096] As depicted in FIG. 7A intelligent infusion module 720 is configured to display the data, for example, the one or more patient parameters 717A, and the infusion pump data 715 on a user interface 720A of the intelligent infusion module 720.

[0097] Then, as depicted in FIG. 7B, the user interface 720B of the intelligent infusion module 720, displays the information sent to the patient’s EMR regarding the infusion data and the updated operational parameters. Specifically, user interface 720B depicts a patient parameter value and infusion parameter value at 5 times during an infusion period.Additionally, interface 720B also depicts two automatic infusion flow rate changes implemented by the intelligent infusion module 720.

[0098] Note that workflow 200 is just one example, and other flows including fewer, additional, or alternative steps, consistent with this disclosure, are possible.Example Infusion System

[0099] FIG. 8 depicts an example infusion system 800, which may implement methods described herein for intelligent infusion. The infusion system 800 may be coupled to a patient 850 to administer a substance to the patient 850 through infusion. The infusion system 800 may include one or more pumps, for example, pump 802, pump 804, pump 806, and pump 808. Although a large volume pump is illustrated, other types of pumps may be implemented, such as a peristaltic pump, a small volume pump, a syringe pump, an anesthesia delivery pump, or a patient-controlled analgesic. A pump may be an infusion device configured to deliver a substance, (e.g., fluid, nutrients, drug, etc.) to a patient’s circulatory system, or epidural space, for example, via an intravenous infusion, subcutaneous infusion, arterial infusion, epidural infusion, etc., or to a patient’s digestive system, for example, via a nasogastric tube (NG), a percutaneous endoscopic gastrostomy tube (PEG), nasojejunal tube (NJ), etc. Each of the pumps 802, 804, 806, or 808 may comprise a standard infusion pumping unit, patient-controlled analgesia (PCA) pump, syringe pump, pulse oximeter, invasive or non-invasive blood pressure monitor, electrocardiograph, bar code reader, printer, temperature monitor, RF telemetry link, fluid warmer / IV pump, or high rate IV pump (2000+ ml / hr).

[0100] Each of the pumps 802, 804, 806, or 808 may be fluidly connected with an upstream fluid line 812, fluid line 814, fluid line 816, and fluid line 818, respectively. Further, each of pump 802, pump 804, pump 806, and pump 808, may be fluidly connected with a downstream fluid line 822, fluid line 824, fluid line 826, and fluid line 828, respectively. The fluid lines may be any type of fluid conduit, such as tubing, through which fluid can flow.

[0101] Each of fluid supply 832, fluid supply 834, fluid supply 836, and fluid supply 838, may be a reservoir, for example, as bottles shown, inverted, and suspended above thepumps. Fluid supplies may also take the form of bags, syringes, or other types of containers. The infusion system 800 may be mounted on a roller stand or intravenous pole 840.

[0102] Infusion system 800 may further comprise check valves, drip chambers, valved ports, connectors, and other devices configured to administer a substance.

[0103] Each of the pumps 802, 804, 806, or 808 of infusion system 800 may be coupled to an infusion pump controller 860. The infusion pump controller 860 may be a patient care device (PCD) or patient care unit (PCU). The infusion pump controller 860 is configured to control operations of the pumps 802, 804, 806, or 808, for example, to control infusions to patient 150. The infusion pump controller 860 may be further configured to the control of fluid delivery to the patient and the monitoring of the fluid path for occlusion or air-in-line obstructions.

[0104] The infusion pump controller 860 may further include a graphical user interface (GUI), for example, an information display such as a liquid crystal display, and / or a touchscreen. The user interface of the infusion pump controller 860 may be used during set up and / or operating procedures to facilitate control of the infusion system 800. For example, entry, editing, and / or display of operational parameters of the pumps 802, 804, 806, or 808. The infusion pump controller 860 may further include one or more softkeys and / or hardkeys to facilitate data entry and commands. In some aspects, a user interface may display the operational parameters of the pumps 802, 804, 806, or 808, for example, the infusion rate at which the pump is operating. The user interface may additionally and / or alternatively, be used to display informational, advisory, alarm, or malfunction messages associated with the pumps 802, 804, 806, or 808.

[0105] The infusion pump controller 860 may further be configured to provide power to the infusion system 800 and interface between aspects of the infusion system 800 and external devices and / or networks, for example, patient monitoring networks, instructional systems (e.g., an electronic medical record system), pharmacy systems, and / or nurse call systems, or as an interface to external equipment such as barcode readers to provide a means of inputting drug and / or patient information from medication or patient records. In some aspects, the infusion pump controller 860 is configured to provide physical attachment of the infusion system 800 to structures, such as intravenous pole 840 and / or bedrails, and the like.Example Syringe Pump

[0106] FIG. 9 depicts an example syringe pump 902. Syringe pump 902 includes a graphical user interface (GUI) 924 for displaying operational information, including the selected syringe type and the configured infusion (e.g., in terms of rate of infusion, volume infused, length of time of infusion, etc.). A user may operate syringe pump 902 through one or more buttons 922 in this example. Note that other examples may include other arrangements, such as touch-screen interfaces, or interfaces operable by remote device, such as by an application on a computing device.

[0107] Syringe 901 is shown next to syringe pump 902, rather than loaded in the pump, for clarity of illustration. Syringe pump 902 includes cradle 904 in which a barrel 903 of syringe 901 rests when mounted in the syringe pump 902. Sensor 928 detects volume markings along a barrel of syringe 901. Cradle 904 has a clamp 906 to securely hold the barrel 903 in a fixed position in cradle 904 to resist axial and lateral movement. Clamp 906 may pivot between an open position to permit loading or removal of syringe 901 and a closed position over cradle 904. Barrel clamp 906 may measure an outside diameter of the barrel 903 of syringe 901. Barrel flange 905 of syringe 901 resides in a barrel flange groove 908 in syringe pump 902 to immobilize barrel 903 from axial movement during movement of plunger 907 within barrel 903 of syringe 901. Barrel flange groove may measure an outside diameter and a thickness of the barrel flange 905 of syringe 901.

[0108] Plunger 907 can include push-button 909 having an inner side 911 and being interconnected with stopper 913 of plunger 907 by piston 915. When mounted in syringe pump 902, push-button 909 can be held by drive head 910 with a plunger retainer comprising a pair of pivotally mounted claws, first retainer claw 912 and second retainer claw 914, shown in the closed position in FIG. 9. The retainer claws 912 and 914 can curve inwardly toward each other to grasp push-button 909 mounted in syringe pump 902.

[0109] A rotation knob 916 can be used to control the positions of the first and second retainer claws 912 and 914 to allow removal and insertion of the push-button 909 and to release the split-nut from the driveshaft to permit axial positioning of the drive head 910. Syringes can be provided for use with a syringe pump with different quantities of fluid, and the plunger can be located at different positions in relation to the barrel.

[0110] The drive head 910 can allow manual adjustment to accommodate syringes with different beginning plunger positions. A syringe inserted in the cradle 904 can align with the drive head 910 within a particular axial range. The points where the axial center lines of the syringe intersect the driver can change according to the size of the syringe but only in one direction along the drive head 910. A guide device 918 can extend from the drive head 910 to a point within a body of the syringe pump 902.

[0111] Syringe pump 902 can include a control panel 920 providing multiple buttons 922 for control of the syringe pump 902 as well as GUI 924 used to present pumpspecific information to the operator. The buttons 922 can allow the operator to program the syringe pump 902 for the flow rate, the volume to be infused, and other pump parameters. GUI 924 can present the programmed flow rate, the amount of fluid remaining to be infused, as well as alarms and other information.

[0112] The drive head 910 can include a contact plate 926 that has a pushing surface that contacts the outer side 917 of the push-button 909 as the drive head 910 moves forward toward the barrel 903, pushing the plunger 907 into the barrel 903 of the syringe to expel the syringe contents through a fluid administration set tubing 919 to a patient. A drive mechanism S54 is configured to drive the drive head 910 forward. The drive mechanism S54 may include, a drivetrain, for example, gears, axles, shafts, chains, hydraulics, and / or any other components for translating rotational motion of a motor into linear motion of the drive head 910. The drivetrain may include linear actuating components, such as a linear stepper motor, a brushed DC electric motor, a brushless DC electric motor, a servo motor, an AC motor, or any other type of motor.

[0113] When the contact plate 926 exerts force against the push-button 909, the force may be detected by force sensor 929 and transmitted to a processor for monitoring. In the case of friction between the stopper 913 and the barrel 903, the force exerted can increase and can be detected by force sensor 929.

[0114] Syringe pump 902 is configured with known syringe types containing information such as syringe inner diameter and stroke of the stopper 913. Syringe pump 902 determines the position of stopper 913 based on the movement of drive head 910 based on the syringe type and stored characteristics of the syringe type. Then, syringe pump 902 calculates the volume infused, time elapsed, volume remaining, and time remaining. As thedrive head 910 continues to move, a flow rate is determined based on the characteristics of the syringe and the velocity of the drive head 910.

[0115] One or more sensors, such as sensor 928, barrel clamp 906, groove 908, claws 912 and 914, and force sensor 929, may measure various characteristics of syringe 901, to obtain a measured value for the characteristic, such as barrel length, barrel outside diameter, flange shape, flange size, plunger shape, plunger size (e.g., diameter), plunger tab thickness, volume per plunger distance moved, driver head height, etc. These sensors may include one or more of an optical sensor, a light source, a pressure sensor, a position sensor (e.g., magnetic linear position sensor indicating the plunger head), force sensor, and the like.Example Method for Intelligent Infusion

[0116] FIG. 10 depicts an example method 1000 for intelligent infusion with an intelligent infusion system, such as intelligent infusion system 100 in FIG. 1.

[0117] Method 1000 begins at step 1002 with assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitoring device.

[0118] Method 1000 proceeds at step 1004 with receiving a set of data comprising a value for the patient parameter measured by the patient monitoring device and an initial operational parameter of the infusion system.

[0119] Method 1000 then proceeds at step 1006 determining a state of the infusion system.

[0120] Method 1000 proceeds at step 1008 with receiving an updated operational parameter of the infusion system based on the state of the infusion system.

[0121] Method 1000 proceeds at step 1010 with adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

[0122] In some aspects, the state of the infusion system is a first automation state, and the updated operational parameter is received from a user of the infusion system.

[0123] In some aspects, the state of the infusion system is a second automation state, and the method further comprises: determining a zone threshold associated with the target zone is exceeded based on the set of data; generating a notification based on the zonethreshold being exceeded; and displaying, on a user interface associated with the infusion system, the notification, wherein the updated operational parameter is received from a user of the infusion system in response to the notification.

[0124] In some aspects, the method further comprises transmitting, to a clinician device associated with the user of the infusion system, the notification, wherein the updated operational parameter is received from the clinician device.

[0125] In some aspects, the method further comprises stopping the infusion system based on the zone threshold being exceeded.

[0126] In some aspects, the state of the infusion system is a third automation state, and the method further comprises: determining the updated operational parameter based on the set of data; generating, an infusion recommendation based on the updated operational parameter; displaying, on a user interface associated with the infusion system, the infusion recommendation; and receiving, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is received in response to receiving the confirmation from the user.

[0127] In some aspects, the method further comprises transmitting, to a clinician device associated with the user of the infusion system, the infusion recommendation, wherein the confirmation is received from the clinician device.

[0128] In some aspects, the state of the infusion system is a fourth automation state, and the method further comprises: determining the updated operational parameter based on the set of data.

[0129] In some aspects, the method further comprises: determining an automation threshold is exceeded based on the updated operational parameter; generating an automation recommendation for the updated operational parameter based on the automation threshold being exceeded; displaying, on a user interface associated with the infusion system, the automation recommendation; and receiving, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is received in response to receiving the confirmation.

[0130] In some aspects, the method further comprising: receiving a second set of data comprising a second value for the patient parameter measured by the patient monitoring device and the updated operational parameter of the infusion system; determining an operational threshold is exceeded based on the second set of data; transitioning, the state of the infusion system from the fourth automation state to a third automation state; and displaying, on the user interface associated with the infusion system, an alert of the transition from the fourth automation state to the third automation state.

[0131] In some aspects, the target zone is assigned based on user input to the infusion system. In some aspects, the target zone is assigned based on the patient parameter and one or more characteristics of the infusion system. In some aspects, the target zone comprises an upper threshold for the patient parameter and a lower threshold for the patient parameter.

[0132] In some aspects, the method further comprises: generating, based on the state of the infusion system and the updated operational parameter, a clinical note; and sending, to an electronic medical record system, the clinical note. In some aspects, the clinical note comprises the set of data.

[0133] In some aspects, the method further comprises displaying, on a user interface associated with the infusion system, the value for the patient parameter measured by the patient monitoring device. In some aspects, further comprises displaying, on a user interface associated with the infusion system, the updated operational parameter. In some aspects, the set of data comprises a set of values of the patient parameter over a time period. In some aspects, the set of data further comprises biographical information associated with the patient.

[0134] In some aspects, the method further comprises assigning the state of the infusion system. In some aspects, assigning the state of the infusion system comprises receiving, from a user of the infusion system, the state. In some aspects, assigning the state of the infusion system comprises determining, based on a characteristic of the infusion system, the state of the infusion system. In some aspects, the characteristic of the infusion system comprises a type of fluid for infusion to the patient by the infusion system. In some aspects, the characteristic of the infusion system comprises a care area of the infusion system. In some aspects, the characteristic of the infusion system comprises a clinical site of the infusion system.

[0135] In some aspects, assigning the state of the infusion system comprises determining, based on a characteristic of the patient, the state of the infusion system. In some aspects, the characteristic of the infusion system comprises a type of the patient.

[0136] In some aspects, assigning the state of the infusion system comprises determining, based on a characteristic of a user of the infusion system, the state of the infusion system.

[0137] In one aspect, method 1000, or any aspect related to it, may be performed by an apparatus, such as computing device 1100 of FIG. 11, which includes various components operable, configured, or adapted to perform the method 1000. Computing device 1100 is described below in further detail.

[0138] Note that FIG. 10 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.Example Computing Device for Intelligent Infusion

[0139] FIG. 11 depicts an example computing device 1100, such as a medical device, which implements various features and processes described herein, such as infusion system 800 in FIG. 8 and / or syringe pump 902 in FIG. 9. For example, the computing device 1100 may perform one or more steps of any of FIG. 2 or method 1000. The computing device 1100 may include one or more processors 1104, one or more memories 1106, one or more input components 1110, one or more output components 1112, and one or more communication interfaces 1108. Each of these components may be coupled by a bus 1102.

[0140] Computing device 1100 may perform these processes based on one or more processors 1104 executing software instructions stored by a computer-readable medium, such as one or more memories 1106. In certain embodiments, one or more processors 1104 may be programmed / designed / configured to perform these processes. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non- transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices. Software instructions may be read into one or more memories from another computer-readable medium or from another device via communication interface 1108.When executed, software instructions stored in one or more memories may cause one or more processors 1104 to perform one or more processes described herein.

[0141] A memory 1106 may include data storage or one or more data structures (e.g., a database, etc.). Computing device 1100 may be capable of receiving information from, storing information in, communicating information to, or searching information stored in the data storage or one or more data structures in one or more memories 1106.

[0142] A memory 1106 may include random access memory (RAM), read only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory, etc.), that stores information and / or instructions for use by one or more processors 1104. For example, a memory 1106 may include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0143] In some aspects, one or more memories 1106 may include assignation component 1114 is configured for assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitor device.

[0144] In some aspects, one or more memories 1106 may include a communication component 1116 is configured for receiving a set of data comprising a value for the patient parameter measured by the patient monitor device and an initial operational parameter of the infusion system, such as infusion data 1120, or receive an updated operational parameter of the infusion system based on the state of the infusion system.

[0145] In some aspects, one or more memories 1106 may include an infusion component 1118 is configured for adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

[0146] One or more processors 1104 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), that may be programmed to perform a function, such as described herein.

[0147] One or more input components 1110 may include a component that permits computing device 1100 to receive information, such as via user input (e.g., a touch-screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Further, one or more input components 1110 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.).

[0148] One or more output components 1112 may include a component that provides output information from computing device 1100 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

[0149] Communication interface 1108 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables computing device 1100 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 1108 may permit computing device 1100 to receive information from another device and / or provide information to another device. For example, communication interface 1108 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, and / or the like.Example Clauses

[0150] Implementation examples are described in the following numbered clauses:

[0151] Clause 1 : A method, comprising: assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitoring device; receiving a set of data comprising a value for the patient parameter measured by the patient monitoring device and an initial operational parameter of the infusion system; determining a state of the infusion system; receiving an updated operational parameter of the infusion system based on the state of the infusion system; adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

[0152] Clause 2: The method of clause 1, wherein: the state of the infusion system is a first automation state, and the updated operational parameter is received from a user of the infusion system.

[0153] Clause 3: The method of clause 1, wherein: the state of the infusion system is a second automation state, and the method further comprises: determining a zone threshold associated with the target zone is exceeded based on the set of data; generating a notification based on the zone threshold being exceeded; displaying, on a user interface associated with the infusion system, the notification, wherein the updated operational parameter is received from a user of the infusion system in response to the notification.

[0154] Clause 4: The method of clause 3, further comprising transmitting, to a clinician device associated with the user of the infusion system, the notification, wherein the updated operational parameter is received from the clinician device.

[0155] Clause 5: The method of clause 3, further comprising stopping the infusion system based on the zone threshold being exceeded.

[0156] Clause 6: The method of clause 1, wherein: the state of the infusion system is a third automation state, and the method further comprises: determining the updated operational parameter based on the set of data; generating, an infusion recommendation based on the updated operational parameter; displaying, on a user interface associated with the infusion system, the infusion recommendation; and receiving, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is received in response to receiving the confirmation from the user.

[0157] Clause 7 : The method of clause 6, further comprising transmitting, to a clinician device associated with the user of the infusion system, the infusion recommendation, wherein the confirmation is received from the clinician device.

[0158] Clause 8: The method of clause 1, wherein: the state of the infusion system is a fourth automation state, and the method further comprises: determining the updated operational parameter based on the set of data.

[0159] Clause 9: The method of clause 8, further comprising: determining an automation threshold is exceeded based on the updated operational parameter; generatingan automation recommendation for the updated operational parameter based on the automation threshold being exceeded; displaying, on a user interface associated with the infusion system, the automation recommendation; and receiving, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is received in response to receiving the confirmation.

[0160] Clause 10: The method of clause 8, further comprising: receiving a second set of data comprising a second value for the patient parameter measured by the patient monitoring device and the updated operational parameter of the infusion system; determining an operational threshold is exceeded based on the second set of data; transitioning, the state of the infusion system from the fourth automation state to a third automation state; and displaying, on the user interface associated with the infusion system, an alert of the transition from the fourth automation state to the third automation state.

[0161] Clause 11 : The method of any one of clauses 1-10, wherein the target zone is assigned based on user input to the infusion system.

[0162] Clause 12: The method of any one of clauses 1-10, wherein the target zone is assigned based on the patient parameter and one or more characteristics of the infusion system.

[0163] Clause 13: The method of any one of clauses 1-12, further comprising: generating, based on the state of the infusion system and the updated operational parameter, a clinical note; and sending, to an electronic medical record system, the clinical note.

[0164] Clause 14: The method of clause 13, wherein the clinical note comprises the set of data.

[0165] Clause 15 : The method of any one of clauses 1-14, wherein the set of data further comprises biographical information associated with the patient.

[0166] Clause 16: The method of any one of clauses 1-15 wherein the target zone comprises an upper threshold for the patient parameter and a lower threshold for the patient parameter.

[0167] Clause 17: The method of any one of clauses 1-16, further comprising displaying, on a user interface associated with the infusion system, the value for the patient parameter measured by the patient monitoring device.

[0168] Clause 18: The method of any one of clauses 1-17, further comprising displaying, on a user interface associated with the infusion system, the updated operational parameter.

[0169] Clause 19: The method of any one of clauses 1-18, wherein the set of data comprises a set of values of the patient parameter over a time period.

[0170] Clause 20: The method of any one of clauses 1-19, further comprising assigning the state of the infusion system.

[0171] Clause 21 : The method of clause 20, wherein assigning the state of the infusion system comprises receiving, from a user of the infusion system, the state.

[0172] Clause 22: The method of clause 20, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the infusion system, the state of the infusion system.

[0173] Clause 23 : The method of clause 22, wherein the characteristic of the infusion system comprises a type of fluid for infusion to the patient by the infusion system.

[0174] Clause 24: The method of clause 22, wherein the characteristic of the infusion system comprises a care area of the infusion system.

[0175] Clause 25 : The method of clause 22, wherein the characteristic of the infusion system comprises a clinical site of the infusion system.

[0176] Clause 26: The method of clause 20, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the patient, the state of the infusion system.

[0177] Clause 27 : The method of clause 26, wherein the characteristic of the infusion system comprises a type of the patient.

[0178] Clause 28: The method of clause 26, wherein assigning the state of the infusion system comprises determining, based on a characteristic of a user of the infusion system, the state of the infusion system.

[0179] Clause 29: An infusion system, comprising: an infusion pump configured to deliver fluid to a patient; and an infusion pump controller configured to perform a method in accordance with any one of Clauses 1-28.

[0180] Clause 30: A processing system, comprising: memory comprising computerexecutable instructions; and one or more processors configured to execute the computerexecutable instructions and cause the processing system to perform a method in accordance with any one of Clauses 1-28.

[0181] Clause 31 : A processing system, comprising means for performing a method in accordance with any one of Clauses 1-28.

[0182] Clause 32: A non-transitory computer-readable medium storing program code for causing a processing system to perform the steps of any one of Clauses 1-28.

[0183] Clause 33: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of Clauses 1-28.Additional Considerations

[0184] The preceding description is provided to enable any person skilled in the art to practice the various embodiments described herein. The examples discussed herein are not limiting of the scope, applicability, or embodiments set forth in the claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0185] As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0186] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). Reference to an element in the singular is not intended to mean only one unless specifically so stated, but rather “one or more.” For example, reference to an element (e.g., “a processor,” “a memory,” etc.), unless otherwise specifically stated, should be understood to refer to one or more elements (e.g., “one or more processors,” “one or more memories,” etc.). The terms “set” and “group” are intended to include one or more elements, and may be used interchangeably with “one or more.” Where reference is made to one or more elements performing functions (e.g., steps of a method), one element may perform all functions, or more than one element may collectively perform the functions. When more than one element collectively performs the functions, each function need not be performed by each of those elements (e.g., different functions may be performed by different elements) and / or each function need not be performed in whole by only one element (e.g., different elements may perform different sub-functions of a function). Similarly, where reference is made to one or more elements configured to cause another element (e.g., an apparatus) to perform functions, one element may be configured to cause the other element to perform all functions, or more than one element may collectively be configured to cause the other element to perform the functions. Unless specifically stated otherwise, the term “some” refers to one or more.

[0187] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0188] The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and / or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.

[0189] The following claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

WHAT IS CLAIMED IS:

1. An infusion system, comprising: an infusion pump configured to deliver fluid to a patient; and an infusion pump controller configured to: assign a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitor device; receive a set of data comprising a value for the patient parameter measured by the patient monitor device and an initial operational parameter of the infusion system; determine a state of the infusion system; receive an updated operational parameter of the infusion system based on the state of the infusion system; and adjust the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

2. The infusion system of claim 1, wherein: the state of the infusion system is a first automation state, and the updated operational parameter is received from a user of the infusion system.

3. The infusion system of claim 1, wherein: the state of the infusion system is a second automation state, and the infusion pump controller is further configured to: determine a zone threshold associated with the target zone is exceeded based on the set of data; generate a notification based on the zone threshold be exceeded; and display, on a user interface associated with the infusion system, the notification, wherein the updated operational parameter is received from a user of the infusion system in response to the notification.

4. The infusion system of claim 3, wherein the infusion pump controller is further configured to transmit, to a clinician device associated with the user of the infusionsystem, the notification, wherein the updated operational parameter is received from the clinician device.

5. The infusion system of claim 3, wherein the infusion pump controller is further configured to stop the infusion system based on the zone threshold be exceeded.

6. The infusion system of claim 1, wherein: the state of the infusion system is a third automation state, and the infusion pump controller is further configured to: determine the updated operational parameter based on the set of data; generate, an infusion recommendation based on the updated operational parameter; display, on a user interface associated with the infusion system, the infusion recommendation; and receive, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is received in response to receive the confirmation from the user.

7. The infusion system of claim 6, wherein the infusion pump controller is further configured to transmit, to a clinician device associated with the user of the infusion system, the infusion recommendation, wherein the confirmation is received from the clinician device.

8. The infusion system of claim 1, wherein: the state of the infusion system is a fourth automation state, and the infusion pump controller is further configured to: determine the updated operational parameter based on the set of data.

9. The infusion system of claim 8, wherein the infusion pump controller is further configured to: determine an automation threshold is exceeded based on the updated operational parameter;generate an automation recommendation for the updated operational parameter based on the automation threshold be exceeded; display, on a user interface associated with the infusion system, the automation recommendation; and receive, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is received in response to receive the confirmation.

10. The infusion system of claim 8, wherein the infusion pump controller is further configured to: receive a second set of data comprising a second value for the patient parameter measured by the patient monitor device and the updated operational parameter of the infusion system; determine an operational threshold is exceeded based on the second set of data; transition, the state of the infusion system from the fourth automation state to a third automation state; and display, on a user interface associated with the infusion system, an alert of the transition from the fourth automation state to the third automation state.

11. The infusion system of any of claims 1-10, wherein the target zone is assigned based on user input to the infusion system.

12. The infusion system of any of claims 1-10, wherein the target zone is assigned based on the patient parameter and one or more characteristics of the infusion system.

13. The infusion system of any of claims 1-12, wherein the infusion pump controller is further configured to: generate, based on the state of the infusion system and the updated operational parameter, a clinical note; and send, to an electronic medical record system, the clinical note.

14. The infusion system of claim 13, wherein the clinical note comprises the set of data.

15. The infusion system of any of claims 1-14, wherein the set of data further comprises biographical information associated with the patient.

16. The infusion system of any of claims 1-15, wherein the target zone comprises an upper threshold for the patient parameter and a lower threshold for the patient parameter.

17. The infusion system of any of claims 1-16, wherein the infusion pump controller is further configured to display, on a user interface associated with the infusion system, the value for the patient parameter measured by the patient monitor device.

18. The infusion system of any of claims 1-17 wherein the infusion pump controller is further configured to display, on a user interface associated with the infusion system, the updated operational parameter.

19. The infusion system of any of claims 1-18, wherein the set of data comprises a set of values of the patient parameter over a time period.

20. The infusion system of any of claims 1-19, wherein the infusion pump controller is further configured to assign the state of the infusion system.

21. The infusion system of claim 20, wherein to assign the state of the infusion system the infusion pump controller is further configured to receive, from a user of the infusion system, the state.

22. The infusion system of claim 20, wherein to assign the state of the infusion system the infusion pump controller is further configured to determine, based on a characteristic of the infusion system, the state of the infusion system.

23. The infusion system of claim 22, wherein the characteristic of the infusion system comprises a type of fluid for infusion to the patient by the infusion system.

24. The infusion system of claim 22, wherein the characteristic of the infusion system comprises a care area of the infusion system.

25. The infusion system of claim 22, wherein the characteristic of the infusion system comprises a clinical site of the infusion system.

26. The infusion system of claim 20, wherein to assign the state of the infusion system the infusion pump controller is further configured to determine, based on a characteristic of the patient, the state of the infusion system.

27. The infusion system of claim 22, wherein the characteristic of the infusion system comprises a type of the patient.

28. The infusion system of claim 20, wherein to assign the state of the infusion system the infusion pump controller is further configured to determine, based on a characteristic of a user of the infusion system, the state of the infusion system.

29. A method, comprising: assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitoring device; receiving a set of data comprising a value for the patient parameter measured by the patient monitoring device and an initial operational parameter of the infusion system; determining a state of the infusion system; receiving an updated operational parameter of the infusion system based on the state of the infusion system; and adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

30. The method of claim 29, wherein: the state of the infusion system is a first automation state, and the updated operational parameter is received from a user of the infusion system.

31. The method of claim 29, wherein: the state of the infusion system is a second automation state, and the method further comprises:determining a zone threshold associated with the target zone is exceeded based on the set of data; generating a notification based on the zone threshold being exceeded; and displaying, on a user interface associated with the infusion system, the notification, wherein the updated operational parameter is received from a user of the infusion system in response to the notification.

32. The method of claim 31, further comprising transmitting, to a clinician device associated with the user of the infusion system, the notification, wherein the updated operational parameter is received from the clinician device.

33. The method of claim 31, further comprising stopping the infusion system based on the zone threshold being exceeded.

34. The method of claim 29, wherein: the state of the infusion system is a third automation state, and the method further comprises: determining the updated operational parameter based on the set of data; generating, an infusion recommendation based on the updated operational parameter; displaying, on a user interface associated with the infusion system, the infusion recommendation; and receiving, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is received in response to receiving the confirmation from the user.

35. The method of claim 34, further comprising transmitting, to a clinician device associated with the user of the infusion system, the infusion recommendation, wherein the confirmation is received from the clinician device.

36. The method of claim 29, wherein:the state of the infusion system is a fourth automation state, and the method further comprises: determining the updated operational parameter based on the set of data.

37. The method of claim 36, further comprising: determining an automation threshold is exceeded based on the updated operational parameter; generating an automation recommendation for the updated operational parameter based on the automation threshold being exceeded; displaying, on a user interface associated with the infusion system, the automation recommendation; and receiving, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is received in response to receiving the confirmation.

38. The method of claim 36, further comprising: receiving a second set of data comprising a second value for the patient parameter measured by the patient monitoring device and the updated operational parameter of the infusion system; determining an operational threshold is exceeded based on the second set of data; transitioning, the state of the infusion system from the fourth automation state to a third automation state; and displaying, on a user interface associated with the infusion system, an alert of the transition from the fourth automation state to the third automation state.

39. The method of any one of claims 29-38, wherein the target zone is assigned based on user input to the infusion system.

40. The method of any one of claims 29-38, wherein the target zone is assigned based on the patient parameter and one or more characteristics of the infusion system.

41. The method of any one of claims 29-40, further comprising:generating, based on the state of the infusion system and the updated operational parameter, a clinical note; and sending, to an electronic medical record system, the clinical note.

42. The method of claim 41, wherein the clinical note comprises the set of data.

43. The method of any one of claims 29-42, wherein the set of data further comprises biographical information associated with the patient.

44. The method of any one of claims 29-42, wherein the target zone comprises an upper threshold for the patient parameter and a lower threshold for the patient parameter.

45. The method of any one of claims 29-44, further comprising displaying, on a user interface associated with the infusion system, the value for the patient parameter measured by the patient monitoring device.

46. The method of any one of claims 29-45, further comprising displaying, on a user interface associated with the infusion system, the updated operational parameter.

47. The method of any one of claims 29-46, wherein the set of data comprises a set of values of the patient parameter over a time period.

48. The method of any one of claims 29-47, further comprising assigning the state of the infusion system.

49. The method of claim 48, wherein assigning the state of the infusion system comprises receiving, from a user of the infusion system, the state.

50. The method of claim 48, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the infusion system, the state of the infusion system.

51. The method of claim 50, wherein the characteristic of the infusion system comprises a type of fluid for infusion to the patient by the infusion system.

52. The method of claim 50, wherein the characteristic of the infusion system comprises a care area of the infusion system.

53. The method of claim 50, wherein the characteristic of the infusion system comprises a clinical site of the infusion system.

54. The method of claim 48, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the patient, the state of the infusion system.

55. The method of claim 54, wherein the characteristic of the infusion system comprises a type of the patient.

56. The method of claim 48, wherein assigning the state of the infusion system comprises determining, based on a characteristic of a user of the infusion system, the state of the infusion system.

57. A non-transitory computer-readable medium storing program code for causing a processing system to perform steps of: assigning a target zone for a patient parameter of a patient coupled to an infusion system and a patient monitoring device; receiving a set of data comprising a value for the patient parameter measured by the patient monitoring device and an initial operational parameter of the infusion system; determining a state of the infusion system; receiving an updated operational parameter of the infusion system based on the state of the infusion system; and adjusting the infusion system based on the set of data from the initial operational parameter of the infusion system to the updated operational parameter of the infusion system.

58. The non-transitory computer-readable medium of claim 57, wherein: the state of the infusion system is a first automation state, and the updated operational parameter is received from a user of the infusion system.

59. The non-transitory computer-readable medium of claim 57, wherein: the state of the infusion system is a second automation state, andthe steps further comprise: determining a zone threshold associated with the target zone is exceeded based on the set of data; generating a notification based on the zone threshold being exceeded; and displaying, on a user interface associated with the infusion system, the notification, wherein the updated operational parameter is received from a user of the infusion system in response to the notification.

60. The non-transitory computer-readable medium of claim 59, wherein the steps further comprise transmitting, to a clinician device associated with the user of the infusion system, the notification, wherein the updated operational parameter is received from the clinician device.

61. The non-transitory computer-readable medium of claim 59, wherein the steps further comprise stopping the infusion system based on the zone threshold being exceeded.

62. The non-transitory computer-readable medium of claim 57, wherein: the state of the infusion system is a third automation state, and the steps further comprise: determining the updated operational parameter based on the set of data; generating, an infusion recommendation based on the updated operational parameter; displaying, on a user interface associated with the infusion system, the infusion recommendation; and receiving, in response to the infusion recommendation, a confirmation to adjust the infusion system according to the infusion recommendation from a user, wherein the updated operational parameter is received in response to receiving the confirmation from the user.

63. The non-transitory computer-readable medium of claim 62, wherein the steps further comprise transmitting, to a clinician device associated with the user of theinfusion system, the infusion recommendation, wherein the confirmation is received from the clinician device.

64. The non-transitory computer-readable medium of claim 57, wherein: the state of the infusion system is a fourth automation state, and the steps further comprise: determining the updated operational parameter based on the set of data.

65. The non-transitory computer-readable medium of claim 64, wherein the steps further comprise: determining an automation threshold is exceeded based on the updated operational parameter; generating an automation recommendation for the updated operational parameter based on the automation threshold being exceeded; displaying, on a user interface associated with the infusion system, the automation recommendation; and receiving, in response to the automation recommendation, confirmation to adjust the infusion system, wherein the updated operational parameter is received in response to receiving the confirmation.

66. The non-transitory computer-readable medium of claim 65, wherein the steps further comprise: receiving a second set of data comprising a second value for the patient parameter measured by the patient monitoring device and the updated operational parameter of the infusion system; determining an operational threshold is exceeded based on the second set of data; transitioning, the state of the infusion system from the fourth automation state to a third automation state; and displaying, on the user interface associated with the infusion system, an alert of the transition from the fourth automation state to the third automation state.

67. The non-transitory computer-readable medium of any one of claims 57-66, wherein the target zone is assigned based on user input to the infusion system.

68. The non-transitory computer-readable medium of any one of claims 57-67, wherein the target zone is assigned based on the patient parameter and one or more characteristics of the infusion system.

69. The non-transitory computer-readable medium of any one of claims 57-68, wherein the steps further comprise: generating, based on the state of the infusion system and the updated operational parameter, a clinical note; and sending, to an electronic medical record system, the clinical note.

70. The non-transitory computer-readable medium of claim 69, wherein the clinical note comprises the set of data.

71. The non-transitory computer-readable medium of any one of claims 57-70, wherein the set of data further comprises biographical information associated with the patient.

72. The non-transitory computer-readable medium of any one of claims 57-71, wherein the target zone comprises an upper threshold for the patient parameter and a lower threshold for the patient parameter.

73. The non-transitory computer-readable medium of any one of claims 57-72, further comprising displaying, on a user interface associated with the infusion system, the value for the patient parameter measured by the patient monitoring device.

74. The non-transitory computer-readable medium of any one of claims 57-73, wherein the steps further comprise displaying, on a user interface associated with the infusion system, the updated operational parameter.

75. The non-transitory computer-readable medium of any one of claims 57-74, wherein the set of data comprises a set of values of the patient parameter over a time period.

76. The non-transitory computer-readable medium of any one of claims 57-75, wherein the steps further comprise assigning the state of the infusion system.

77. The non-transitory computer-readable medium of claim 76, wherein assigning the state of the infusion system comprises receiving, from a user of the infusion system, the state.

78. The non-transitory computer-readable medium of claim 76, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the infusion system, the state of the infusion system.

79. The non-transitory computer-readable medium of claim 78, wherein the characteristic of the infusion system comprises a type of fluid for infusion to the patient by the infusion system.

80. The non-transitory computer-readable medium of claim 78, wherein the characteristic of the infusion system comprises a care area of the infusion system.

81. The non-transitory computer-readable medium of claim 78, wherein the characteristic of the infusion system comprises a clinical site of the infusion system.

82. The non-transitory computer-readable medium of claim 78, wherein assigning the state of the infusion system comprises determining, based on a characteristic of the patient, the state of the infusion system.

83. The non-transitory computer-readable medium of claim 82, wherein the characteristic of the infusion system comprises a type of the patient.

84. The non-transitory computer-readable medium of claim 78, wherein assigning the state of the infusion system comprises determining, based on a characteristic of a user of the infusion system, the state of the infusion system.

Images