EP4721093A1

EP4721093A1 - Device, system, and method for determining and increasing clinician engagement with infusion devices

Info

Publication number: EP4721093A1
Application number: EP23732762.2A
Authority: EP
Inventors: Daniel M. Abal
Original assignee: CareFusion 303 Inc
Current assignee: CareFusion 303 Inc
Priority date: 2023-05-24
Filing date: 2023-05-24
Publication date: 2026-04-08
Also published as: WO2024242677A1; CN121285860A; AU2023449664A1

Abstract

An infusion system includes a display device, an eye-tracking sensor, and a processor. The display device is configured to display an infusion metric of an infusion therapy. The eye-tracking sensor is configured to detect gaze points that correspond to locations on the display device at which a user is looking. The processor is configured to display the infusion metric via the display device and determine, based on a status of the infusion therapy, that the infusion metric is a high-priority infusion metric. The processor is also configured to detect the gaze points via the eye-tracking sensor and determine, based on the gaze points, that the user is unaware of the high-priority infusion metric. Additionally, the processor is configured to, responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to emphasize the high-priority infusion metric.

Description

DEVICE, SYSTEM, AND METHOD FOR DETERMINING

AND INCREASING CLINICIAN ENGAGEMENT WITH INFUSION DEVICES

TECHNICAL FIELD

[0001] The present disclosure relates generally to infusion devices configured for autonomous and semi-autonomous operation. In particular, the present disclosure describes methods for improving clinician interactions with said infusion devices, as well as systems and devices incorporating the same.

BACKGROUND

[0002] As medical devices become increasingly autonomous, there is a risk that clinicians will become over-reliant on these devices and, as a result, less engaged in the therapies they perform. This is particularly true for “closed-loop” patient care devices that can operate without any input from the clinician.

SUMMARY

[0003] There is a growing need for technologies that can encourage or ensure clinician engagement. According to various aspects of the subject technology, an infusion system includes a display device, an eye-tracking sensor, and a processor. The display device is configured to display an infusion metric of an infusion therapy. The eye-tracking sensor is configured to detect gaze points that correspond to locations on the display device at which a user is looking. The processor is configured to display the infusion metric via the display device and determine, based on a status of the infusion therapy, that the infusion metric is a high- priority infusion metric. The processor is also configured to detect the gaze points via the eyetracking sensor and determine, based on the gaze points, that the user is unaware of the high- priority infusion metric. Additionally, the processor is configured to, responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to emphasize the high-priority infusion metric.

[0004] According to various aspects of the subject technology, a computer-implemented method for increasing clinician engagement with an infusion device includes displaying, via a display device, an infusion metric of an infusion therapy. The method also includes determining, based on a status of the infusion therapy, that the infusion metric is a high-priority infusion metric. Additionally, the method includes detecting, via an eye-tracking sensor, gaze points that correspond to locations on the display device at which a user is looking. Further, the method includes determining, based on the gaze points, that the user is unaware of the high- priority infusion metric. Moreover, the method includes, responsive to determining that the user is unaware of the high-priority infusion metric, adjusting the display device to emphasize the high-priority infusion metric.

[0005] It is understood that other configurations of the subject technology will become readily apparent to those skilled in the art from the following detailed description, wherein various configurations of the subject technology are shown and described by way of illustration. As will be realized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] For a better understanding of the various described implementations, reference should be made to the Detailed Description below, in conjunction with the Figures. Like reference numerals refer to corresponding parts throughout the Figures and Description.

[0007] FIGS. 1 A and IB depict an example institutional patient care system of a healthcare organization, according to various aspects of the subject technology.

[0008] FIGS. 2 A and 2B are conceptual diagrams that illustrate example interactions between a clinician, a patient, and a patient care device involved in an infusion therapy, according to various aspects of the subject technology.

[0009] FIG. 3 depicts a display device that includes an eye-tracking sensor for detecting a gaze point of a clinician, according to various aspects of the subject technology.

[0010] FIGS. 4A-4G depict an example display device, a user interface displayed thereon, and example adjustments made thereto for emphasizing information displayed via the user interface, according to various aspects of the subject technology.

[0011] FIG. 5 depicts an example process for increasing clinician engagement with an infusion device, according to various aspects of the subject technology. [0012] FIG. 6 depicts an example process for tailoring prompts regarding an infusion therapy, according to various aspects of the subject technology.

[0013] FIG. 7 is a conceptual diagram illustrating an example electronic system for increasing clinician engagement with an infusion device, according to various aspects of the subject technology.

DETAILED DESCRIPTION

[0014] Reference will now be made to implementations, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide an understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In some instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

[0015] The present disclosure provides an infusion system for increasing clinician engagement with an infusion device. The infusion system of the subject technologies provides a solution to the aforenoted problems with user engagement in infusion therapies, in part, by determining whether a user of the infusion device is engaged with infusion therapy being performed by the infusion device and directing or redirecting the user’s attention, as needed, so that the user stays engaged. For example, the therapy may require monitoring of a high- priority infusion metric indicative of a safety hazard or an upcoming alarm. The infusion system of the subject technology includes an eye-tracking sensor to determine where the user is looking, as well as a processor configured to detect, based on data from the eye-tracking sensor, whether the user is unaware of the infusion metric. Responsive to this determination, the processor may then adjust a display device at which the infusion metric is displayed to emphasize the infusion metric. In this manner, the infusion system can respond to the engagement level of the user and ensure the user is aware of certain infusion metrics (e.g., high- priority infusion metrics).

[0016] The present disclosure also provides a system for tailoring prompts regarding an ongoing infusion therapy. Accordingly, the system may adjust the amount of infusion-therapy- related prompts displayed at a display device based on user preferences, skill level, and/or user engagement levels. In this regard, a processor is configured to retrieve a series of prompts for an infusion therapy, where each prompt is associated with a “trigger event” that may cause the prompt to be displayed, as well as an indicator of the prompt’s priority. For example, certain prompts may be of a higher priority than other prompts. The processor is also configured to receive an indication of a prompt-frequency level. For example, a user (e.g., a user with little clinical experience) may indicate that they want to receive every prompt relevant to the ongoing infusion therapy. Or a user (e.g., an experienced user) may indicate that they only want to receive high-priority prompts regarding the infusion therapy. The processor may, on consideration of the user’s skill level, display a prompt only after determining that a trigger event has occurred and that the prompt should be displayed based on a determination regarding the prompt-frequency level and the priority indicator of the prompt (e.g., determining that the prompt-frequency level exceeds the priority indicator of the prompt). In this manner, the other infusion system allows the user to tailor the amount of prompts they receive (e.g., based on their clinical experience) - thus avoiding issuing too many or too few prompts for a given infusion therapy.

[0017] FIGS. 1A and IB depict an example institutional patient care system 100 of a healthcare organization, according to various aspects of the subject technology. As illustrated in FIG. 1A, a patient care device 102 is connected to a healthcare network 104 via a transmission channel 106. (Note, “medical device” and “infusion device” may also be used herein to refer to the patient care device 102). The transmission channel 106 can be any wired or wireless transmission channel (e.g., a 502.11 wireless local area network (WLAN)).

[0018] The patient care device 102 may include various ancillary medical devices, each of which may also be connected to the healthcare network 104 via the transmission channel 106. Example medical devices include an infusion pump, a vital signs monitor, a medication dispensing device, a medication preparation device, an automated dispensing device, or a module coupled with one of the aforementioned devices.

[0019] In some implementations, the healthcare network 104 includes computer systems located in various departments throughout the healthcare organization. For example, the healthcare network 104 may include computer systems associated with an admissions department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, or a medical decision support system. The healthcare network 104 may also include discrete subnetworks. For example, in the depicted example, the healthcare network 104 includes a device network 108, by which the patient care device 102 and other devices may communicate in accordance with normal operations. [0020] Additionally, the patient care system 100 may incorporate an information system server 110. Although the information system server 110 is shown as being a separate server in the depicted example, the functions and programming of the information system server 110 can be incorporated into another computer, if such is desired by engineers designing the institution's information system.

[0021] The patient care system 100 may further include one or more device terminals 112 for connecting and communicating with the information system server 110. Device terminals 112 may include personal computers, personal data assistants, and mobile devices (e.g., laptops, tablet computers, augmented reality devices, or smartphones) configured with software for communicating with the information system server 110 via the healthcare network 104.

[0022] The patient care device 102 of the patient care system 100 comprises itself a system for providing patient care. The patient care device 102 may include or incorporate pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy devices, and other drug-delivery devices that may be utilized according to the teachings set forth herein. In the depicted example, the patient care device 102 includes a control unit 114 that is connected to two functional modules 116 and 118.

[0023] The control unit 114 may include a central processing unit (CPU) connected to a memory (e.g., random-access memory), and one or more interface devices, such as a display 120, a coded data input device, a network connection, and an auxiliary interface for communicating with additional modules or devices. The control unit 114 may also include a main non-volatile storage unit, such as a hard disk drive or non-volatile flash memory, for storing software and data. Further, the control unit 114 may include one or more internal buses for interconnecting the aforementioned elements. The display 120 may comprise a touch screen for both displaying information to a user and allowing the user to input information by touching defined areas of the display 120.

[0024] Additionally, or alternatively, the control unit 114 may include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, softkeys, a mouse, a track ball and/or a light pen. The control unit 114 may further include a bar code reader capable of scanning and interpreting data printed in a bar-code format. Additionally the control unit 114 may include any device for entering coded data into a computer, such as a device(s) for reading a magnetic strips, radio-frequency identification (RFID) devices whereby digital data encoded in RFID tags or smart labels are captured by a reader via radio waves, PCMCIA (Personal Computer Memory Card International Association) smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of data input devices that may be incorporated into the control unit 114 include a voice activation or recognition device or a portable personal data assistant (PDA).

[0025] The functional modules 116 and 118 of the patient care device 102 may be any devices for providing care to a patient or for monitoring a condition of the patient. For example, at least one of the functional modules 116 and 118 may be an infusion pump module, such as an intravenous (IV) infusion pump for delivering medication or other fluid to a patient. For purposes of discussion, the first functional module 116 will be referred to as an infusion pump module.

[0026] Notwithstanding, each of the functional modules 116 and 118 may be any patient treatment or monitoring device, such as an infusion pump, a syringe pump, a patient-controlled analgesic (PCA) pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an etCO2 monitor, an EKG monitor, an EEG monitor, a heart rate monitor, an intracranial pressure monitor, or the like. Additionally, the functional modules 116 and 118 may also be other devices, such as a printer, a scanner, a bar code reader, a near-field communication reader, an RFID reader, or any other peripheral input, output, or input-output device.

[0027] Each of the functional modules 116 and 118 may communicate, whether directly or indirectly, with the control unit 114. In some implementations, the control unit 114 provides overall monitoring and control of the patient care device 102. Further, the functional modules 116 and 118 may be connected physically or electronically in serial fashion to one or both ends of the control unit 114, as shown in the depicted embodiment. However, it is recognized that there are other means for connecting the functional modules 116 and 118 to the control unit 114 that may be utilized without departing from the subject technology.

[0028] It is also be appreciated that devices, such as pumps or patient monitoring devices that provide sufficient programmability and connectivity, may be capable of operating as standalone devices and may communicate directly with the healthcare network 104 without being connected to the healthcare network 104 through the control unit 114. As described above, additional medical devices or peripheral devices may be connected to the patient care device 102 through one or more auxiliary interfaces. [0029] Furthermore, each of the functional modules 116 and 118 may include modulespecific components, such as a microprocessor, as well as volatile and nonvolatile memory for storing information. It is noted that while only the two functional modules 116 and 118 are shown in the depicted embodiment, any number of functional modules or other devices may be connected to the control unit 114. The number and type of functional modules described herein are illustrative, and they do not limit the scope of the subject technology. Modulespecific components include any components necessary for operation of a particular module, such as a pumping mechanism for the first functional module 116.

[0030] While each functional module may be capable of a least some level of independent operation, the control unit 114 monitors and controls overall operation of the patient care device 102. For example, the control unit 114 may provide programming instructions to the functional modules 116 and 118 and monitor the status of each of the functional modules 116 and 118.

[0031] A medical device incorporating aspects of the subject technology may be equipped with a network interface module (NIM), thus allowing the medical device to participate as a node in a network. While, for purposes of clarity, the subject technology is described as operating in an Ethemet-network environment using Internet Protocol (IP), it is understood that concepts of the subject technology are equally applicable in other network environments, and such environments are intended to be within the scope of the subject technology.

[0032] Moreover, it is noted that data to and from various data sources can be converted into network-compatible data with existing technology, and movement of the information between the medical device and network can be accomplished by a variety of means. For example, the patient care device 102 and the healthcare network 104 may communicate via automated interaction, manual interaction, or a combination of both automated and manual interaction.

[0033] Automated interaction may be continuous or intermittent and may occur through direct network connection, or through RS232 links, MIB systems, RF links (e.g., Bluetooth, WLAN, digital cable), or other wired- or wireless-communication means. Manual interaction between the patient care device 102 and the healthcare network 104 may involve physically transferring, whether intermittently or periodically, data between systems. For example, data transfer may utilize user interface devices, coded data input devices, bar codes, computer disks, portable data assistants, memory cards, or any other media for storing data. The communication means in various aspects is bidirectional with access to data from as many points of the distributed data sources as possible. Decision-making can occur at a variety of places within the healthcare network 104.

[0034] With further reference to the example patient care system 100, the patient care device 102 may be capable of operating in different modes (or “personalities”) with each mode defined by a configuration database. The configuration database may be a database internal to the patient care device 102, or it may be an external database 122. A particular configuration database is selected based, at least in part, on patient-specific information such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics, or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) and a location of the patient care device 102 in the healthcare network 104. Patient care information may be entered through various interface devices, and it may originate from anywhere in the healthcare network 104. For example, the patient care information may originate from a pharmacy server, an admissions server, a laboratory server, or another server connected to the healthcare network 104.

[0035] FIG. IB depicts an example embodiment of the patient care device 102, according to various aspects of the subject technology. In the depicted embodiment, both of the functional modules 116 and 118 are infusion pumps that include a door, a handle, a display, and control keys. For example, as depicted, infusion pump 118 includes door 128 and handle 130. The handle 130 operates to lock the door 128 in a closed position during operation. The handle 130 also operates to unlock and open the door 128 for loading the administration set 126 and for accessing the internal pumping and sensing mechanisms of the infusion pump 118. While the door 128 is open, the administration set 126 can be connected with the infusion pump 118. Moreover, while the door 128 is closed, the administration set 126 is brought into operative engagement with the pumping mechanism of the infusion pump 118, as well as any upstream or downstream pressure sensors or other equipment of the infusion pump 118.

[0036] The display 132 of the infusion pump 118 (e.g., an LED display) is located on the door 128 in the depicted embodiment. The display 132 may be used to visually communicate information regarding the infusion pump 118, including alerts (e.g., regarding upcoming or currently active alarms). Additionally, the control keys 134A-D of the infusion pump 118 may be used for programming or controlling operations of the infusion pump. In some implementations, the control keys are presented as interactive elements on the display 132 (e.g., a touchscreen display). The patient care device 102 and/or the infusion pumps 116 and 118 may also include audio-alert equipment in the form of a speaker.

[0037] Each of the infusion pumps 116 and 118 is in operative engagement with a respective administration set 124 or 126 (e.g., silicon tubing). The administration sets 124 and 126 connect the infusion pumps 116 and 118 to respective first and second fluid supplies (e.g., bottles, bags, or other containers), which may be inverted and suspended above the infusion pumps 116 and 118. The administration sets 124 and 126 also connect the infusion pumps 116 and 118 to a patient.

[0038] In the depicted example, the infusion pumps 116 and 118 are used to infuse respective fluids of the fluid supplies into the patient. The infusion pumps 116 and 118 may be flow control devices that act on the administration sets 124 and 126 to move fluid from the fluid supplies, through the administration sets 124 and 126, and into the patient. Because individual infusion pumps 116 and 118 are used, each of the infusion pumps 116 and 118 may be individually set to the pumping or operating parameters required for infusing the respective fluid in the respective fluid supply into the patient at a particular rate prescribed by the clinician.

[0039] Typically, medical administration sets have more parts than are shown in the depicted embodiment. For example, many administration sets include check valves, drip chambers, valved ports, connectors, and other devices well known to those skilled in the art. These other devices are not included in the depicted embodiment to preserve clarity of illustration.

[0040] The illustrated patient care device 102 also includes a control unit 114, which includes a display 120, control keys 136A-C, and an eye-tracking sensor 138. The display 120 may be configured to visually communicate information regarding the patient care device 102, such as the operating parameters of the infusion pumps 116 and 118, alert indications, or messages. In some implementations, the control keys 136A-C are configured for selecting or setting control parameters or options for controlling the patient care device 102 and modules connected thereto (e.g., infusion pumps 116 and 118).

[0041] In some implementations, the eye-tracking sensor 138 is configured to detect a direction at which a user of the patient care device 102 is looking. For example, the patient care device 102 may use the eye-tracking sensor 138 to determine whether the user is looking at the display 120 of the control unit 114 or a display of a device connected thereto (e.g., display 132 of infusion pump 118). As another example, the patient care device 102 may use the eyetracking sensor 138 to determine whether the user is looking at a particular location on a display (e.g., the display 120). In this manner, the patient care device 102 may determine whether the user is aware of information (e.g., a high-priority infusion metric) displayed via the display.

[0042] The control unit 114 may also include a speaker for providing audible alerts. Moreover, in various implementations, the display 120 may be implemented as a touchscreen display. Further, in some such implementations, the control keys 136A-C may be omitted or reduced in number by providing corresponding interactive elements via a graphical user interface presented via the display 120. In some implementations, each of the control keys 136A-C may select a corresponding option displayed via the display 120.

[0043] The control unit 114 may also include a communications system, which the control unit 114 may use to communicate with external equipment. For example, the control unit 114 may use the communications system to communicate with a medical facility server (e.g., information system server 110 of FIG. 1A) or other computer, such as a handheld communication device or a laptop-type of computer. As another example, the control unit 114 may use the communications system to communicate with other information devices that a clinician may have to transfer information or to download drug libraries to the functional modules 116 and 118.

[0044] The communication module may be used to transfer access and interaction information for clinicians encountering the control unit 114 or a device coupled therewith (e.g., infusion pumps 116 and 118, or a bar code scanner). The communications system may include one or more of a radio frequency (RF) system, an optical system (e.g., infrared), a BLUETOOTH™ system, or other wired or wireless systems. The bar code scanner and communications system may alternatively be included integrally with either of the infusion pumps 116 and 118, such as in cases where a control unit is not used or in addition to the communications module of the control unit 114.

[0045] Moreover, information input devices need not be hard-wired to medical instruments, as information may be transferred through a wireless connection as well. Additionally, other types of modules may be connected to the infusion pumps 116 and 118 or to the control unit 114, such as a syringe pump module, a PCA module, an end-tidal CO2 monitoring module, an oximeter monitoring module, or the like. [0046] In some implementations, the control unit 114 includes control software that provides processing for control algorithms. The control unit 114 may also include connectivity circuitry or software to enable closed- and semi-closed-loop control capabilities. As used herein, “closed-loop” control (also closed loop operation) refers generally to a system that does not rely on external manual inputs to deliver a therapy (e.g., an infusion therapy). Similarly, “semi-closed-loop” control (or semi-closed-loop operation) refers to a system that requires only a minimal amount of external manual inputs for delivering a therapy. For example, when operating in a closed-loop control mode, the control unit 114 may monitor and instruct changes to operation parameters in real time to maintain the patient in a designated state (e.g., by way of keeping a physiological sensor measurement within a target zone). Whereas, in a semi- closed-loop control mode, the control unit 114 may request confirmation of parameter changes from the user (e.g., via display 120). In some implementations, the control unit 114 merely monitors and provides reporting to the user of monitored conditions, alarms, and measurements.

[0047] In some implementations, the control unit 114 provides an external interface, for example, for interaction between the infusion pumps 116 and 118 and physiological or biometric sensors, the external interface may also function to allow for input of parameters that may be used to control the titration of IV infusions of medications to a patient. In some implementations, control unit 114 may control operation of interface elements for the purpose of interaction between the infusion pumps 116 and 118 and the sensors, and for providing input parameters.

[0048] In some implementations, the control unit 114 provides control for an infusion therapy performed via one of the infusion pumps 116 or 118. The infusion therapy may incorporate feedback provided by the aforenoted physiological or biometric sensors used to monitor the therapy being performed. In situations where an IV fluid is not being delivered as a result of abnormal conditions (e.g., occlusion of an administration set 124 or 126, leaking, or disconnect from a patient), the sensors may indicate that the patient is not responding to or receiving the therapy. The control unit 114 may detect such activity and provide feedback (e.g., a notification or an alarm) to the clinician to alert the clinician of a possible fault condition that should be addressed.

[0049] The control unit 114 can incorporate control software (including, e.g., one or more algorithms in the unit) that can be tailored to specific or general medical treatments. Moreover, the control unit 114 may receive infusion status information from the infusion pumps 116 and 118. The infusion status information may include, for example, an identification of the IV fluid (e.g., a type of medication), a flow rate of the IV fluid, a programmed volume-to-be-infused (VTBI), a delivery duration, an upstream or downstream pressure metric, and the like.

[0050] Once configured, the closed-loop system can autonomously provide a therapy, receive feedback from one or more sensors and, based on the feedback, automatically adjust the therapy as needed. For example, the control unit 114 may determine, during an administration of a medication, an expected trend in a physiological property during a predetermined time period based on sensor data for a prior period of time, a dose of the medication provided to the patient, and the one or more physical parameters of the patient. The control unit 114 may then cause the infusion device to adjust the dose of the medication to cause the physiological property to follow an expected trend within a predetermined time period.

[0051] In some implementations, the software that allows for closed- or semi-closed-loop control reside in a component different than the control unit 114. This may allow for more frequent updates to the software, and it may also free up computational resources at the patient care device 102. Moreover, machine learning and artificial intelligence may account for patient variations related to physiological properties such as age, genetics, health history, and other characteristic and environmental factors. Systems incorporating such capabilities may involve large databases and complex programs requiring powerful microprocessors and data storage capabilities to perform the timely and accurate computation needed. Depending on the complexity of the software, these systems may not be fit for running on the control unit 114. Accordingly, they may instead reside and run a server (e.g., information system server 110 of FIG. 1 A) or a device (e.g., device terminal 112 of FIG. 1 A) connected to the patient care device (e.g., via healthcare network 104 of FIG. 1A).

[0052] FIGS. 2A and 2B are conceptual diagrams 200 and 250 that illustrate example interactions between a clinician 202, a patient 204, and a patient care device 102 involved in an infusion therapy, according to various aspects of the subject technology. The patient care device 102 includes an infusion pump 116, a user interface 208 (e.g., displayed via display 120 of FIGS. 1A and IB), a control unit 114, and a sensor 206 (e.g., eye-tracking sensor 138 of FIG. IB).

[0053] The first conceptual diagram 200, illustrated in FIG. 2A, relates to an infusion therapy performed by the patient care device 102 (e.g., patient care device 102 of FIGS. 1A and IB) while operating in a non-closed-loop mode, such as a semi-closed loop or manual mode. As discussed above, semi-closed-loop operation requires occasional input from the clinician (e.g., confirmation of a prompt). Similarly, manual operation denotes a non- autonomous mode where the patient care device does not act unless instructed to do so by the clinician 202. As illustrated in the first conceptual diagram, the clinician 202 is an integral part of non-closed loop operation. Without the clinician 202, the patient care device 102 may not be able to initiate or complete an infusion therapy.

[0054] It is noted that there can be varying degrees of semi-closed-loop operation. For example, the present disclosure contemplates at least three levels of operation that each qualify as semi-closed-loop operation: In level one operation, the patient care device 102 (e.g., via user interface 208) provides biometric or biophysical temporal data (e.g., detected via sensor 206) and alerts to the clinician 202. In level two operation, the patient care device 102 provides advisory therapeutic actions to the clinician. And, in level three operation, the patient care device 102 provides recommended therapeutic actions to the clinician and then proceeds with the recommended actions (e.g., by adjusting the infusion pump 116 or another infusion pump of the patient care device 102) after receiving confirmation from the clinician 202 (e.g., via user interface 208).

[0055] By contrast, the second conceptual diagram 250, illustrated in FIG. 2B, relates to an infusion therapy performed by the patient care device 102 while operating in a closed-loop mode. As discussed above, closed-loop operation does not require manual inputs from the clinician 202 for delivering the infusion therapy. The patient care device 102 may still present information to the clinician 202, for example, via the user interface 208. However, the infusion therapy can continue to completion without input from the clinician 202. Accordingly, the clinician 202 in the second conceptual diagram 250 is depicted as being tangential to the operation of the patient care device 102. This “closed-loop” operation may also be referred to as level four operation.

[0056] In some implementations, in both level three and level four operation, the patient care device 102 has the capability to pause or interrupt an ongoing infusion therapy based on a physiological parameter of the patient 204. For example, in the case of a PCA therapy, the patient care device 102 may include a PCA pump and an SPO2 or etCO2 sensor. In this case, the patient care device 102 can stop or prevent additional administration of the analgesic by the patient 204 or the clinician 202 if the physiological parameter indicates that the patient 204 is entering a critical physiological stage. [0057] In some implementations, the patient care device 102 is configured to indicate (e.g., via the user interface 208) the current operating mode (e.g., manual, level one, level two, closed-loop, etc.). In this manner, the patient care device 102 informs the clinician 202 the amount of engagement required of the clinician for administering the infusion therapy.

[0058] Furthermore, the patient care device 102 can change from operating level or mode to another. For example, if the patient care device 102 is operating at level four (or in a closed- loop mode) and the clinician 202 determines that the patient needs an additional bolus of insulin when the patient has already received a significant amount of insulin, the patient care device 102 may prompt the clinician 202 whether want to revert to manual operation or a lower level of autonomous operation (e.g., level one, two, or three). As will be described further, the system may monitor actions (e.g., gaze) of the clinician 202 to determine whether the clinician becomes aware of the prompt and adjust the screen accordingly to ensure awareness. The patient care device 102 may identify the implication of the mode change. The patient care device 102 may also provide information about how the mode change will affect the functioning of the patient care device 102 (e.g., requiring clinician confirmation, etc.), how the mode change may impact the patient 204, and what the clinician’s 202 responsibilities include in the new operating mode.

[0059] In some implementations, the patient care device 102 is configured to transition to level one operation after detecting failure of the sensor 206, a communication interruption (e.g., with information system server 110 of FIG. 1A), or another disruption in the patient care device 102. After detecting such an event, in some implementations, the patient care device 102 will inform the clinician 202, identify changes required in the clinician’s 202 tasks (e.g., including a necessary time to adjust to the new tasks), and the clinician’s 202 responsibilities to ensure proper administration of the infusion therapy.

[0060] The patient care device 102 may also identify all pertinent pharmacokinetic (PK) information, such as patient 204 PK parameters, a current amount of a drug in the patient 204, a time and a value of a next infusion required to maintain a concentration of the drug, and any other necessary information needed by the clinician 202 to effectively take control of the infusion therapy. Further, the patient care device 102 may also record the conditions leading to the automatic mode change. The patient care device 102 will provide easy access to information about the conditions leading to the automatic mode-change. This may assist the clinician 202 in understanding the reason for the mode change. [0061] The patient care device 102 may also use the above information with a machinelearning algorithm to identify the causes of the mode change and predict future occurrences of upcoming mode changes. In this manner, the patient care device 102 can learn to adapt and evolve, thus improving the efficiency thereof. Similarly, the patient care device 102 may use an algorithm to predict and schedule actions to reduce interference.

[0062] The patient care device 102 will also use an algorithm to predict and schedule actions required of the clinician 202 to reduce interference (Figure 4). For example, the algorithm may cause the patient care device 102 to schedule actions that can be controlled (e.g., initiation of checklists or confirmations) during periods that are less prone to disruption, thus preventing interference with actions that cannot be controlled. As an example, the patient care device 102 may schedule the replacement of near-empty syringes or IV containers to periods before a bolus, infusion rate increase, or a procedure requiring the clinician’s 202 attention.

[0063] The patient care device may also employ a machine-learning algorithm to deal with frequent alarms and errors by identifying the source of the error and prescribing steps or recommendations to avoid the error. This is important since error frequency and severity can negatively affect the usability of the system.

[0064] In some implementations, when the patient care device 102 is operating in level three, which requires clinician 202 confirmations, frequent confirmations can lead to errors and can be disruptive and annoying to the clinician 202. Accordingly, the patient care device 102 may use a hierarchy of confirmations. For example, the patient care device 102 may be configured to present only confirmations corresponding to a certain threshold priority in the hierarchy (e.g., high-priority confirmations) to the clinician 202. These confirmations may include confirmations to prevent an error or to prevent an action that could cause harm to the patient. Accordingly, the patient care device 102 may allow the clinician 202 to configure the frequency and type of confirmation required.

[0065] In some implementations, the patient care device 102 is configured to avoid yes-no confirmations (e.g., confirmations requiring the clinician select only a “yes” input or a “no” input), as these confirmations can lead to errors. Instead of yes-no confirmations, the patient care device 102 may provide response options that summarize what will happen for each possible response.

[0066] For example, the patient care device 102 may prompts the clinician 202 for a decrease in an analgesic based on the patient’s SPO2 or etCO2 level, either of which may indicate that the patient is sufficiently anesthetized. Instead of a yes-no confirmation, the patient care device 102 can provide additional information using a progressive disclosure to allow the clinician 202 to find out more about the consequences of their response to the confirmation, as well as their responsibilities before they respond to the confirmation. In so doing, the patient care device 102 will still keep the text in the confirmation dialog brief enough to be easily scannable by the clinician 202.

[0067] The patient care device 102 may also use artificial intelligence or machine learning to learn as a procedure goes along to provide a situation or procedure-driven response. The patient care device may identify patterns by combining historical information from past patient procedures, clinician 202 preferences, and patient parameters and conditions. By learning through multiple sources of data, including past clinical history and results, clinician 202 actions and responses, and combining data from multiple physiological sensors, the patient care device 102 can then provide recommendations, make predictions, and initiate actions for complex medical situations.

[0068] In some implementations, during operation in any mode, but particularly in levels one through three, the patient care device 102 checks for errors in the clinician’s 202 inputs (e.g., a misplaced decimal point, or an improper medication input). After identifying a potential error, the patient care device 102 may then alert the clinician 202 to potential errors of commission (e.g., taking an incorrect action) or omission (e.g., failing to take a needed action). Also, the patient care device 102 may inform the clinician 202 if their actions appear incompatible with the state of the patient or the control process. As will be described further with regard to FIG. 3, the system may determine that the clinician 202 is not aware of the error then the system may adjust the screen accordingly to ensure awareness.

[0069] This error-correction capability can also extend to the actions of the clinician 202 in setting-up and configuring closed-loop automation control. It is noted that this capability of the patient care device 102 can be updated using machine learning from previous conditions. Another key feature of this capability is anomaly detection by combining multivariate physiological data signals and considering the correlations among them, as well as their consequences. By analyzing the interrelationships among signals, the machine-learning model can build a univariate model that can maximize the accuracy of identifying anomalies.

[0070] When the patient care device 102 detects a notable event, it may also generate a log containing relevant information that could otherwise be missed by the clinician 202. The process can run continuously, and the event log can be initiated not only by the physiological sensors but by introduction of other external events, such as, for example, medication orders or a laboratory result. The patient care device 102 can then alert the clinician to potential issues, such as the patient’s 204 known conditions contraindicate the medication treatment being ordered, lab results indicating that the patient 204 is experiencing a worsening condition, or that the treatment is producing other noteworthy adverse effects. The log will record the patient event that triggered it, as well as a summary of other items in the patient record that are particularly relevant. The logs may then be used by the aforenoted artificial intelligence and machine-learning algorithms to improve the patient care device 102 response and performance for different clinical situations or procedures.

[0071] FIG. 3 depicts a display device 300 that includes an eye-tracking sensor 138 (e.g., a front-facing camera) for detecting a gaze point 302 of a clinician 202, according to various aspects of the subject technology. The display device 300 includes a display 304 configured to display information relevant to an ongoing infusion therapy. The display 304 may be adjusted to emphasize or deemphasize particular information to ensure the clinician 202 remains engaged in the ongoing therapy.

[0072] In the depicted embodiment, the display device 300 is presented as a standalone display device, such as a computer monitor. This is for clarity of illustration and does not limit the disclosure with respect to the display device 300. The display device 300 can be the display of a patient care device or an infusion pump, such as the displays 120 and 132 discussed above with respect to FIG. IB. Similarly, the display device 300 can be the display of a mobile device (e.g., a smartphone) connected to a patient care device (e.g., via healthcare network 104 of FIG. 1A).

[0073] In some implementations, the display device 300 uses the eye-tracking sensor and eye-tracking software to detect a gaze point associated with a location on the display 304 at which the clinician 202 is looking. This allows the display device 300 to monitor the clinician’s 202 focus of attention and determine whether the clinician 202 is aware of particular information (e.g., an infusion metric) presented via the display 304.

[0074] In some implementations, machine-learning is used to adjust the user interface based on a particular use case. For example, the display device 300 may direct the attention of the clinician 202 to serious issues by enhancing elements on the display 304 (e.g., zooming in on critical information). In this manner, the display device 300 can verify that the clinician 202 is attentive and focused on the most important metrics regarding the ongoing therapy. This in turn improves patient care and clinician 202 efficiency.

[0075] The display device 300 may project key patient physiological data focused onto a portion of the display 304 which is positioned in the center of the clinician’s 202 line of sight as they scan the display 304. The information can be associated with trend information indicators for parameters, such as depth of anesthesia, cardio-pulmonary information, or glycemic trends. Appropriate interpretation of the trend information may allow the clinician 202 to make efficient and timely adjustments of the applicable medications to achieve the desired physiological effects.

[0076] During high workload periods of surgery, fixation on one aspect of the surgery and the screen information may occur. This can lead to an overall loss of situational awareness of the patient. To overcome this, in some implementations, the display device 300 monitors the focus of the clinician 202 and directs the clinician 202 to certain external visual scans of the patient in order to be aligned with the patient’s condition.

[0077] Additionally, the display device 300 may declutter the display 304 if it determines (e.g., by a machine-learning algorithm) that the display 304 includes too much information. For example, where appropriate, the information can be eliminated from the display 304, or some of the information can be turned off to reduce the amount of information presented on the display 304. However, in some implementations, the display device 300 may automatically bring up information or alerts when certain infusion metrics (e.g., physiological information) exceeds predetermined levels.

[0078] By focusing on the information that matters, the display device 300 dynamically changes its display 304 to highlight information of interest and/or most-important information. The display device thereby ensures that the clinician 202 is aware of high-priority information (e.g., high-priority infusion metrics). In contrast to a statically oriented display, with flashing lights and audible alarms, where the clinician must determine the cause of the alarm and why it is happening, the display device 300 of the present disclosure can operate to highlight the most relevant information, thus distraction and alarm fatigue.

[0079] These features, for example, can be used effectively during the inductance and termination phases of anesthesia, during the initiation of glycemic control to bring glucose levels within the desired range, during a fluid challenge period for vasopressor management to increase cardiac output, and in transition periods from semi- to fully-automatic closed-loop control. The features described above allow the clinician to more fully concentrate on the critical parameters of a given therapy. The display device 300 can therefore facilitate a reduced workload during complex situations and during operationally demanding phases of a therapy (e.g., a surgery).

[0080] FIGS. 4A-4G depict an example display device 300, a user interface 402 (or user interface 414, see FIG. 4G) displayed thereon, and example adjustments made thereto for emphasizing information displayed via the user interface 402, according to various aspects of the subject technology. As illustrated in FIG. 4 A, the user interface 402 includes various infusion metrics and waveforms relating to an infusion therapy (or another medical procedure) and a patient receiving the infusion therapy.

[0081] For example, as illustrated in FIG. 4A, the waveforms may correspond to a heartrate of the patient or a respiratory rate of the patient and the infusion metrics may correspond to a cardiac frequency (“FC”), a blood-oxygen level (“SPO2”), a non-invasive blood pressure or pressure non-invasive (“PNI”), or a T-wave of the cardiac signal (“TOFC”) of the patient. As another example, as illustrated in FIG. 4G, the waveforms may correspond to sensor data (e.g., from bi-spectral (BIS) sensor or an electromyographic (EMG) sensor) or amounts of fluids (e.g., propofol or remifentanil) provided to the patient. Additionally, the infusion metrics may include additional information regarding the fluids provided to the patient, such as a rate at which the fluids are being infused. The user interface 402 (or 414) may also include other information regarding the therapy or the patient.

[0082] In addition to the aforenoted infusion metrics and waveforms, FIG. 4B depicts an example heatmap that includes gaze points 404-407. The gaze points 404-407 are detected by an eye-tracking sensor 138 of the display device 300, and the gaze points 404-407 correspond to locations on the user interface 402 at which a user of the display device 300 has looked or is looking - as discussed in more detail above with respect to the gaze point 302 of FIG. 3. Overlapping gaze points are used to indicate that a user has spent more time looking at a particular region (with overlapping gaze points) than at another region (without overlapping gaze points). For example, the user has looked at the locations on the screen corresponding to gaze points 406 and 407, which overlap with gaze point 405, for more time than the user has looked at the location on the screen corresponding only to gaze point 405.

[0083] The heat map suggests that the user has not looked at a particular location 408 at which an infusion metric is displayed for some amount of time (e.g., for 5 mins, 10 mins). If the infusion metric displayed at the particular location 408 is a high-priority infusion metric suggesting a safety hazard or an upcoming alarm, the user may not be aware of the safety hazard or the upcoming alarm. Accordingly, the display device 300 and/or the user interface 402 may be adjusted to emphasize the infusion metric in the particular location 408, thereby alerting the user of the high-priority infusion metric.

[0084] An example adjustment is illustrated in FIG. 4C, which shows a notification 410 displayed overlaid the rest of the user interface 402. Another example adjustment is illustrated in FIG. 4D, which shows the portion of the user interface 402 other than the particular location 408 at which the high-priority infusion metric is displayed as being deemphasized. Deemphasizing the portion of the user interface 402 other than the particular location 408 may include, for example, darkening, blurring, or lowering the contrast of the portion of the user interface 402.

[0085] Yet another example adjustment is illustrated in FIG. 4E, which shows the particular location 408 in which the high-priority infusion metric is displayed as being expanded to fill more of the user interface 402. The particular location 408 is expanded and the rest of the infusion metrics are hidden, thus emphasizing the high-priority infusion metric. Additionally, the size of the font used to render the high-priority infusion metric is increased. A further example adjustment is illustrated in FIG. 4F, which shows a bold font used to display the high-priority infusion metric. In some implementations, the font color may also be adjusted to emphasize the high-priority infusion metric.

[0086] The adjustments described above with respect to FIGS. 4C through 4F can similarly be made to other user interfaces, such as the user interface 414 of FIG. 4G. The user interface 414 of FIG. 4G includes waveforms, metrics, and other information relating to a patient receiving anesthesia (e.g., via the patient care device 102 of FIGS. 1 A-1B). As with the information displayed via the user interface 402, the waveforms, metrics, and information of the user interface 414 can be emphasized or deemphasized using the teachings discussed herein, for example, by changing the color, font, size, or other aspects of said waveforms, metrics, or information.

[0087] FIG. 5 depicts an example process 500 for increasing clinician engagement with an infusion device, according to various aspects of the subject technology. One or more blocks of the process 500 may be implemented, for example, by one or more computing devices, such as the patient care device 102 or the control unit 114 of FIGS. 1A and IB, the device terminal 240 of FIG. 1 A, or a mobile device. For explanatory purposes and without limiting the present disclosure, the example process 500 is described in relation to the patient care device 102 of FIG. IB and the components thereof, including the control unit 114, the infusion pump 116, and the eye-tracking sensor 138.

[0088] In some implementations, one or more of the blocks of the example process 500 may be implemented based on one or more machine-learning algorithms. In some implementations, one or more of the blocks may be implemented apart from other blocks, and by one or more different processors or devices. Further, for explanatory purposes, the blocks of the process 500 are described as occurring in serial, or linearly. However, multiple blocks of the process 500 may occur in parallel. Additionally, the blocks of the process 500 need not be performed in the order shown, and one or more of the blocks of the process 500 need not be performed.

[0089] In the depicted example, a processor (e.g., a processor of control unit 114) displays, via a display device (e.g., display 120 or 132 of FIG. IB), an infusion metric of an infusion therapy (502). The infusion metric may relate to an operating condition of an infusion pump 116. For example, the infusion metric may indicate a flow rate of the infusion pump 116, whether an administration set 124 connected to the infusion pump 116 is occluded, or whether air is detected in the administration set 124. Alternatively, the infusion metric may relate to a physiological or biometric characteristic of a patient receiving the infusion therapy. For example, the infusion metric may indicate the patient’s heartrate, blood pressure, blood oxygen level, or anything else that may be relevant to how the patient is responding to the infusion therapy.

[0090] The processor also determines, based on a status of the infusion therapy, whether the infusion metric is a high-priority infusion metric (504). “High-priority infusion metric” denotes an infusion metric that suggests a potential safety hazard (e.g., a blood sugar of 245 mg/dL or 70 mg/dL), an upcoming alarm (e.g., an end-of-infusion alarm), or some event of which a user of the patient care device 102 ought to be aware. The priority determination may include comparing the infusion metric to a safety threshold. If the processor determines that the infusion metric is not a high-priority infusion metric (504-N), then the processor may wait until the infusion metric becomes a high-priority infusion metric.

[0091] However, if the processor does determine that the infusion metric is a high-priority infusion metric (504- Y), then the processor detects, via the eye-tracking sensor 138, gaze points (e.g., gaze point 302 of FIG. 3) that correspond to locations on the aforenoted display device at which the user has looked (506). Based on the gaze points, the processor then determines whether the user is unaware of the high-priority infusion metric (508).

[0092] For example, for a high-priority infusion metric displayed at a particular location on the display device, determining that the user is unaware of the high-priority infusion metric may include determining that the user has not looked at the particular location for a particular amount of time (e.g., 30 seconds) after the processor determined that the infusion metric was a high-priority infusion metric. In some implementations, the processor may ignore gaze points that suggest the user looked at the particular location for less than another particular amount of time (e.g., 500 milliseconds), as a brief glance over the high-priority infusion metric may suggest that the user is either not aware of the high-priority infusion metric or at least does not appreciate its importance.

[0093] In some implementations, the processor may be configured to receive a clinical experience level of the user and adjust the particular amount of time or the other particular amount of time based on the user’s clinical experience level. Similarly, in some implementations, the processor may be configured to receive an indication of how frequently the user would like the patient care device 102 to provide prompts regarding the infusion therapy. The processor may also adjust the particular amount of time or the other particular amount of time to account for this indication (e.g., increasing the particular amount of time if the user indicated that they would prefer less-frequent prompts).

[0094] If the processor determines that the user is aware of the high-priority infusion metric (508-N), then the processor may wait until the priority of the infusion metric increases. For example, the processor may wait until the infusion metric becomes a non-high-priority infusion metric and again becomes a high-priority infusion metric. Or the processor may wait until the infusion metric reaches an even greater level of priority (e.g., becoming an extra-high- priority infusion metric).

[0095] On the other hand, if the processor determines that the user is unaware of the high- priority infusion metric (508-Y), then the processor adjusts the display device to emphasize the high-priority infusion metric (510). In many implementations, this adjustment lasts only until the user is aware of the high-priority infusion metric. For example, after adjusting the display, the processor may continue to detect gaze points via the eye-tracking sensor 138 until the gaze points suggest that the user is looking at the high-priority infusion metric. Accordingly, the processor may then adjust the display device to stop emphasizing the high-priority infusion metric. Similarly, the processor may adjust the display device to stop emphasizing the infusion metric if it determines that the infusion metric is no longer a high-priority infusion metric.

[0096] In some implementations, adjusting the display device includes adjusting a size, color, or emphasis of the font used to display the high-priority infusion metric. For example, the processor may increase the size of the font to draw attention to the infusion metric. As another example, the processor may change the color of the font to a color (e.g., red, pink) that contrasts against the rest of the information displayed via the display device. As yet another example, the processor may bold, italicize, or underline the font.

[0097] In some implementations, adjusting the display device includes displaying a notification (e.g., notification 410 of FIG. 4C) via the display device, where the notification includes information regarding the high-priority infusion metric. For example, in addition to the high-priority infusion metric, the notification may also include information suggesting why the high-priority infusion metric is of a high-priority.

[0098] In some implementations, adjusting the display device includes adjusting the display device to deemphasize other infusion metrics displayed via the display device, thus drawing attention to the high-priority infusion metric. For example, the display device may decrease a font size of the other infusion metrics, blur the other infusion metrics, or display an overlay (e.g., overlay 412 of FIG. 4D) over the other infusion metrics.

[0099] The processor may also use data from sensors other than the eye-tracking sensor to determine whether the user is aware of high-priority infusion metrics or otherwise engaged in the infusion therapy. For example, the patient care device 102 may include a proximity sensor configured to detect a distance between the display device and the user. If the distance between the display device and the user is greater than a particular distance (e.g., 1 m), this may suggest that the user is not engaged in the infusion therapy. Accordingly, in some implementations, the processor may determine that the user is unaware of the high-priority infusion metric when the distance satisfies (e.g., exceeds) a distance threshold. In this manner, the proximity sensor data may supplement or, in some instances, replace the eye-tracking sensor data.

[0100] Moreover, the processor may be configured to change an operation mode on determining that the user is unaware of the high-priority infusion metric. For example, the processor may be configured operate in a closed-loop mode that does not require user input for administration of the infusion therapy, or operate in a non-closed-loop mode (e.g., a manual mode, a semi-closed-loop mode) that requires user input for administration of the infusion therapy. Accordingly, the processor may transition from operating to the closed-loop mode to operating in the non-closed loop mode responsive to or after determining that the user is not aware of the high-priority infusion metric. This may require the user to be more actively engaged in the infusion therapy.

[0101] By contrast, in some implementations, the processor may be configured to transition from operating in the non-closed-loop mode to operating in the closed-loop mode after determining that the user is not aware of the high-priority infusion metric. This may allow the user to be less engaged in the infusion therapy in instances where the user’s attention is required elsewhere (e.g., with the patient, or with another patient).

[0102] In either instance, the processor may also be configured to transition from one mode (e.g., closed-loop or non-closed-loop) to another (e.g., non-closed-loop or closed-loop) based on other determinations, such as whether the user is engaged in the infusion therapy (e.g., based on gaze point data, proximity data, or user input at the patient care device 102) or whether the user is needed elsewhere in a healthcare environment (e.g., with another patient).

[0103] In some implementations, the processor is configured to create an activity log detailing the user’s engagement with the patient care device 102 and the infusion therapy performed thereby. For example, the activity log may include the aforenoted gaze point data. The activity log may also include data regarding an amount of time between adjusting the display device to emphasize the high-priority infusion metric and determining that the user is aware of the high-priority infusion metric. Moreover, the activity log may include data regarding alarms, detected safety hazards, and the like, as well as how the user responded to the same. Additionally, the activity log may include data regarding how the user responded to prompts from the patient care device 102 (e.g., whether the user read the prompts, based on gaze point data; or whether the user accepted or rej ected the prompts), such as prompts to adjust the infusion therapy (e.g., adjust a flow rate of the infusion pump 116, stop the infusion therapy, or replace the IV fluid with another IV fluid) based on sensor data from sensors connected to the patient care device 102.

[0104] FIG. 6 depicts an example process 600 for tailoring prompts regarding an infusion therapy, according to various aspects of the subject technology. One or more blocks of the process 600 may be implemented, for example, by one or more computing devices, such as the patient care device 102 or the control unit 114 of FIGS. 1 A and IB, the device terminal 240 of FIG. 1A, or a mobile device. For explanatory purposes and without limiting the present disclosure, the example process 600 is described in relation to the patient care device 102 of FIG. IB and components thereof, including the control unit 114, the infusion pump 116, and the eye-tracking sensor 138.

[0105] In some implementations, one or more of the blocks of the example process 600 may be implemented based on one or more machine-learning algorithms. In some implementations, one or more of the blocks may be implemented apart from other blocks, and by one or more different processors or devices. Further, for explanatory purposes, the blocks of the process 600 are described as occurring in serial, or linearly. However, multiple blocks of the process 600 may occur in parallel. Additionally, the blocks of the process 600 need not be performed in the order shown and one or more of the blocks of the process 600 need not be performed.

[0106] In the depicted example, a processor (e.g., a processor of control unit 114) receives (e.g., from a user, from information system server 110 of FIG. 1 A) an indication of a promptfrequency level (602). The indication of the prompt-frequency level may include an indication of a user preference regarding a frequency at which prompts for an infusion therapy should be displayed. Alternatively, or additionally, the indication of the prompt-frequency level may include an indication of a clinical experience level of the user. For example, an indication that the clinical experience level of the user is high (e.g., two years, five years) may suggest that the processor should present the user with less-frequent prompts regarding the infusion therapy. In this regard, on authorization of the user, the frequency of the prompts (e.g., time between prompts) may be determined based on the user’s experience level associated with the user’s authorization account.

[0107] The processor also retrieves a series of prompts associated with the infusion therapy (604), where each of the prompts is associated with a respective trigger event and a respective priority level. The series of prompts for a given infusion therapy may include, for example, prompts for ensuring that an administration set (e.g., administration set 124) is properly loaded in a receptacle of an infusion pump (e.g., infusion pump 116). The series of prompts may further include prompts for ensuring that the user properly primed the administration set and secured the administration set to a catheter inserted into a patient. As another, more specific, example, the series of prompts may include, for an infusion therapy involving the administration of insulin to a diabetic patient, prompts for checking the blood- sugar level of the patient at a particular interval (e.g., every 10 mins). [0108] A “trigger event” is an event that may trigger the display of a respective prompt. For example, detecting that the current fluid supply contains less than a particular amount of fluid (e.g., 50 mL, 100 mL) may be the trigger event for a prompt regarding changing a fluid supply for an infusion pump. As another example, detecting that the infusion therapy has been administered for a predetermined amount of time (e.g., 30 minutes, 1 hour) may be the trigger event for a prompt regarding checking the patient’s blood pressure. A “priority indicator” is an indicator of the priority of the prompt. For example, the priority indicator can be a numeric value on a scale from low- (e.g., small numbers) to high-priority (e.g., large numbers).

[0109] After retrieving the series of prompts, the processor determines (e.g., based on an infusion metric of the infusion therapy) that a trigger event of a prompt of the series of prompts has occurred (606). As discussed above, the trigger event for a given prompt is an event that might cause the processor to display the prompt. Prior to displaying the prompt, however, the processor first determines whether a priority indicator of the prompt satisfies the promptfrequency level (608). If the priority indicator does not satisfy the prompt-frequency level (608-N), then the processor waits until a trigger event (e.g., another trigger event) of a prompt (e.g., another prompt) of the series of prompts is satisfied.

[0110] However, if the priority indicator does satisfy the prompt-frequency level (608-Y), then the processor displays the prompt (610) via a display device (e.g., display 120 or 132). The determination regarding the priority indicator and the prompt-frequency level allows for user-specific customization of the prompts displayed for a given infusion therapy.

[OHl] For example, if the clinical experience level of the user is high (e.g., the promptfrequency level is low), then the processor may only display high-priority prompts (e.g., prompts with a high priority indicator). As another example, if the user is demonstrating how to perform an infusion therapy, for example, in an educational setting, then the processor may display all of the prompts (e.g., the prompt-frequency level is maximized).

[0112] In some implementations, the processor is configured to adjust the promptfrequency level based on sensor data. For example, the processor may receive data from an eye-tracking sensor (e.g., eye-tracking sensor 138) or a proximity sensor, either of which may provide data indicative of whether the user is actively engaged in the infusion therapy. If the sensor data suggests that the user is staring at a portion of the display device for a particular amount of time (e.g., 5 minutes), then the processor may increase the prompt-frequency level, thus resulting in more frequent prompts. Similarly, if the sensor data suggests that a distance between the user and the display device is greater than a particular distance (e.g., 1 meter), then the processor may increase the prompt-frequency level.

[0113] FIG. 7 is a conceptual diagram illustrating an example electronic system 700 for increasing clinician engagement with an infusion device, according to various aspects of the subject technology. The electronic system 700 may be implemented by a computing device for execution of software associated with portions or steps of the processes 600 and 700, or components and methods provided by FIGS. 1-5F. In this regard, the electronic system 700 may include the patient care device 102 of FIGS. 1 and 2, the device terminal 240 of FIG. 2, or the display device 500 of FIGS. 5A-5F.

[0114] The electronic system 700 may also include a specifically-configured personal computer or a mobile device for infusion (e.g., a smartphone, a tablet computer, a laptop computer, or a personal digital assistant), an augmented reality device, a wearable (e.g., a watch, a band, glasses, or a combination thereof), or other touch screen or television with one or more processors embedded therein or coupled thereto, or any other sort of computer-related electronic device having network connectivity.

[0115] Additionally, the electronic system 700 may include various types of computer- readable media and interfaces for various other types of computer readable media. In the depicted example, the electronic system 700 includes a bus 708, a processing unit(s) 712, a system memory 704, a read-only memory (ROM) 710, a permanent storage device 702, an input device interface(s) 714, an output device interface(s) 706, and a network interface(s) 716. In some implementations, the electronic system 700 may include or be integrated with other computing devices or circuitry for operation of the various components and methods previously described.

[0116] The bus 708 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 700. For instance, the bus 708 communicatively connects the processing unit(s) 712 with the ROM 710, the system memory 704, and the permanent storage device 702.

[0117] From these various memory units, the processing unit(s) 712 retrieves instructions to execute and data to process in order to execute the processes of the subject disclosure. The processing unit(s) 712 can be a single processor or a multi-core processor in different implementations. [0118] The ROM 710 stores static data and instructions that are needed by the processing unit(s) 712 and other modules of the electronic system. The permanent storage device 702, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 700 is powered off. Some implementations of the subject disclosure use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 702. Other implementations use a removable storage device (such as a floppy disk, or a flash drive and its corresponding disk drive) as the permanent storage device 702.

[0119] Like the permanent storage device 702, the system memory 704 is a read-and-write memory device. However, unlike the storage device 702, the system memory 704 is a volatile read-and-write memory, such as random-access memory (RAM). The system memory 704 stores some of the instructions and data that the processor needs at runtime. In some implementations, the processes of the subject disclosure are stored in the system memory 704, the permanent storage device 702, and/or the ROM 710. From these various memory units, the processing unit(s) 712 retrieves instructions to execute and data to process, in order to execute the processes of some implementations.

[0120] The bus 708 also connects to the input device interface(s) 714 and the output device interface(s) 706. The input device interface(s) 714 enables the user to communicate information and select commands to the electronic system. Input devices used with the input device interface(s) 714 include, for example, alphanumeric keyboards and pointing devices (also called “cursor control devices”). The output device interface(s) 706 enables, for example, the display of images generated by the electronic system 700. Output devices used with the output device interface(s) 706 include, for example, printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some implementations include devices (e.g., touchscreens) that function as both input and output devices.

[0121] Furthermore, the bus 708 also couples the electronic system 700 to a network (not shown) through the network interface(s) 716. The network interface(s) 716 may include, for example, a wireless access point (e.g., Bluetooth or Wi-Fi) or radio circuitry for connecting to a wireless access point. The network interface(s) 716 may also include hardware (e.g., ethernet hardware) for connecting the computer to a part of a network of computers such as a local area network (LAN), a wide area network (WAN), wireless LAN, an intranet, or a network of networks, such as the Internet. Any or all components of the electronic system 700 can be used in conjunction with the subject disclosure when specifically configured with one of more of the features described.

[0122] These functions described above can be implemented in computer software, firmware, or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. The processes and logic flows can be performed by one or more programmable processors and by programmable logic circuitry. General and special purpose computing devices and storage devices can be interconnected through communication networks.

[0123] Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (also referred to as computer-readable storage media, machine- readable media, or machine-readable storage media). Some examples of such computer- readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD- ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, other optical or magnetic media, and floppy disks. The computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.

[0124] While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field- programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions that are stored on the circuit itself.

[0125] As used in this specification and any claims of this application, the terms “computer,” “server,” “processor,” and “memory” all refer to electronic or other technological devices specifically configured with one or more of the features described above. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification and any claims of this application, the terms “computer readable medium” and “computer readable media” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.

[0126] To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, tactile feedback), and input from the user can be received in forms such as acoustic, speech, gesture, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user (e.g., by sending web pages to a web browser on a user’s client device in response to requests received from the web browser).

[0127] Implementations of the subject matter described in this specification can be implemented in a specifically configured computing system that includes a back end component (e.g., a data server), or that includes a specifically configured middleware component (e.g., an application server), or that includes a specifically configured front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification), or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by one or more forms or mediums of digital data communication, such as a communication network. Examples of communication networks include a LAN and a WAN, an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0128] The computing system can include specifically configured clients and servers. A client and server are generally remote from each other and may interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some implementations, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.

[0129] Those of skill in the art will appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or a combination thereof. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality may be implemented in varying ways for each particular application. Various components and blocks may be arranged differently (e.g., arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology.

[0130] It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0131] Illustration of Subject Technology as Clauses:

[0132] Various examples of aspects of the disclosure are described as numbered clauses (1, 2, 3, etc.) for convenience. These are provided as examples, and do not limit the subject technology. Identifications of the figures and reference numbers are provided below merely as examples and for illustrative purposes, and the clauses are not limited by those identifications.

[0133] Clause 1. An infusion system, comprising: a display device configured to display an infusion metric of an infusion therapy; an eye-tracking sensor configured to detect gaze points that correspond to locations on the display device at which a user is looking; and a processor configured to: display the infusion metric via the display device; determine, based on a status of the infusion therapy, that the infusion metric is a high-priority infusion metric; detect the gaze points via the eye-tracking sensor; determine, based on the gaze points, that the user is unaware of the high-priority infusion metric; and responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to emphasize the high- priority infusion metric. [0134] Clause 2. The infusion system of Clause 1, wherein: the high-priority infusion metric is displayed at a particular location on the display device; and determining that the user is unaware of the high-priority infusion metric comprises determining, based on the gaze points, that the user has not looked at the particular location for a particular amount of time after the processor determined that the infusion metric was a high-priority infusion metric.

[0135] Clause 3. The infusion system of Clause 2, wherein the processor is further configured to receive a clinical experience level of the user and adjust the particular amount of time based on the clinical experience level.

[0136] Clause 4. The infusion system of Clause 2 or 3, wherein the processor is further configured to: determine, based on the gaze points, that the user is aware of the high-priority infusion metric; and responsive to determining that the user is aware of the high-priority infusion metric, adjust the display device to stop emphasizing the high-priority infusion metric.

[0137] Clause 5. The infusion system of any one of Clauses 1 through 4, wherein adjusting the display device to emphasize the high-priority infusion metric comprises changing a size, a color, or an emphasis of a font used to display the high-priority infusion metric.

[0138] Clause 6. The infusion system of any one of Clauses 1 through 5, wherein adjusting the display device to emphasize the high-priority infusion metric comprises displaying a notification via the display device regarding the high-priority infusion metric.

[0139] Clause 7. The infusion system of any one of Clauses 1 through 6, wherein the processor is further configured to: display other infusion metrics of the infusion therapy via the display device; and responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to deemphasize the other infusion metrics.

[0140] Clause 8. The infusion system of any one of Clauses 1 through 7, further comprising a proximity sensor configured to detect a distance between the display device and the user, and wherein the processor is further configured to determine that the user is unaware of the high- priority infusion metric when the distance satisfies a distance threshold.

[0141] Clause 9. The infusion system of any one of Clauses 1 through 8, wherein the processor is configured to: operate in a closed-loop mode wherein adjustments to the infusion therapy are made without user interaction and, while operating in the closed-loop mode and responsive to determining that the user is unaware of the high-priority infusion metric, transition from operating in the closed-loop mode to operating in a non-closed-loop mode wherein a user input is required to continue the infusion therapy. [0142] Clause 10. The infusion system of any one of Clauses 1 through 9, wherein the processor is further configured to create an activity log including data regarding (i) the gaze points and (ii) an amount of time between adjusting the display device to emphasize the high- priority infusion metric and determining that the user is aware of the high-priority infusion metric.

[0143] Clause 11. A computer-implemented method for increasing clinician engagement with an infusion device, the method comprising: displaying, via a display device, an infusion metric of an infusion therapy; determining, based on a status of the infusion therapy, that the infusion metric is a high-priority infusion metric; detecting, via an eye-tracking sensor, gaze points that correspond to locations on the display device at which a user is looking; determining, based on the gaze points, that the user is unaware of the high-priority infusion metric; and responsive to determining that the user is unaware of the high-priority infusion metric, adjusting the display device to emphasize the high-priority infusion metric.

[0144] Clause 12. The computer-implemented method of Clause 11, wherein: the high- priority infusion metric is displayed at a particular location on the display device; and determining that the user is unaware of the high-priority infusion metric comprises determining, based on the gaze points, that the user has not looked at the particular location for a particular amount of time after the processor determined that the infusion metric was the high-priority infusion metric.

[0145] Clause 13. The computer-implemented method of Clauses 11 or 12, further comprising: determining, based on the gaze points, that the user is aware of the high-priority infusion metric; and responsive to determining that the user is aware of the high-priority infusion metric, adjusting the display device to stop emphasizing the high-priority infusion metric.

[0146] Clause 14. The computer-implemented method of any one of Clauses 11 through 13, further comprising: while operating in a closed-loop mode, wherein adjustments to the infusion therapy are made without user interaction, and responsive to determining that the user is unaware of the high-priority infusion metric, transition from operating in the closed-loop mode to operating in a non-closed-loop mode wherein a user input is required to continue the infusion therapy. [0147] Clause 15. A non-transitory, machine-readable storage medium embodying instructions that, when executed by a machine, facilitate the machine to perform the computer- implemented method of any one of Clauses 11 through 14.

[0148] Further Consideration:

[0149] It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0150] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The previous description provides various examples of the subj ect technology, and the subj ect technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects.

[0151] Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims. For example, 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.” Moreover, unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

[0152] The predicate words “configured to,” “operable to,” and “programmed to” do not imply any particular tangible or intangible modification of a subject, but, rather, are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or a component, may also mean the processor being programmed to monitor and control the operation or the processor being operable to monitor and control the operation. Likewise, a processor configured to execute code can be construed as a processor programmed to execute code or operable to execute code.

[0153] The term “automatic,” as used herein, may include performance by a computer or machine without user intervention, for example, by instructions responsive to a predicate action by the computer or machine or other initiation mechanism. The word “example” is used herein to mean “serving as an example or illustration.” Any aspect or design described herein as “example” is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0154] A phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects and vice versa. A phrase such as an “implementation” does not imply that such implementation is essential to the subject technology or that such implementation applies to all configurations of the subject technology. A disclosure relating to an implementation may apply to all implementations, or one or more implementations. An implementation may provide one or more examples. A phrase such as an “implementation” may refer to one or more implementations and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. A phrase such as a “configuration” may refer to one or more configurations and vice versa.

[0155] As used herein a “user interface” (also referred to as an interactive user interface, a graphical user interface, or a UI) may refer to a network-based interface including data fields or other control elements for receiving input signals or providing electronic information or for providing information to the user in response to any received input signals. Control elements may include dials, buttons, icons, selectable areas, or other perceivable indicia presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiates an exchange of data for the device presenting the UI. A UI may be implemented in whole or in part using technologies such as hyper-text mark-up language (HTML), FLASH™, JAVA™, .NET™, C, C++, web services, or rich site summary (RSS). In some implementations, a UI may be included in a stand-alone client (for example, thick client, fat client) configured to communicate (e.g., send or receive data) in accordance with one or more of the aspects described. The communication may be to or from a medical device or server in communication therewith.

[0156] As used herein, the terms “determine” or “determining” encompass a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining and the like via a hardware element without user intervention. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like via a hardware element without user intervention. “Determining” may include resolving, selecting, choosing, establishing, and the like via a hardware element without user intervention.

[0157] As used herein, the terms “provide” or “providing” encompass a wide variety of actions. For example, “providing” may include storing a value in a location of a storage device for subsequent retrieval, transmitting a value directly to the recipient via at least one wired or wireless communication medium, transmitting or storing a reference to a value, and the like. “Providing” may also include encoding, decoding, encrypting, decrypting, validating, verifying, and the like via a hardware element.

[0158] As used herein, the term “message” encompasses a wide variety of formats for communicating (e.g., transmitting or receiving) information. A message may include a machine-readable aggregation of information such as an XML document, fixed field message, comma separated message, JSON, a custom mode, or the like. A message may, in some implementations, include a signal utilized to transmit one or more representations of the information. While recited in the singular, it will be understood that a message may be composed, transmitted, stored, received, etc. in multiple parts.

[0159] As used herein, the term “selectively” or “selective” may encompass a wide variety of actions. For example, a “selective” process may include determining one option from multiple options. A “selective” process may include one or more of: dynamically determined inputs, preconfigured inputs, or user-initiated inputs for making the determination. In some implementations, an n-input switch may be included to provide selective functionality where n is the number of inputs used to make the selection.

[0160] As used herein, the terms “correspond” or “corresponding” encompasses a structural, functional, quantitative and/or qualitative correlation or relationship between two or more objects, data sets, information and/or the like, preferably where the correspondence or relationship may be used to translate one or more of the two or more objects, data sets, information and/or the like so to appear to be the same or equal. Correspondence may be assessed using one or more of a threshold, a value range, fu5y logic, pattern matching, a machine-learning assessment model, or combinations thereof. [0161] In some implementations, data generated or detected can be forwarded to a “remote” device or location, where “remote,” means a location or device other than the location or device at which the program is executed. For example, a remote location could be another location (e.g., office, lab, etc.) in the same city, another location in a different city, another location in a different state, another location in a different country, etc. As such, when one item is indicated as being “remote” from another, what is meant is that the two items can be in the same room but separated, or at least in different rooms or different buildings, and can be at least one mile, ten miles, or at least one hundred miles apart. “Communicating” information references transmitting the data representing that information as electrical signals over a suitable communication channel (e.g., a private or public network). “Forwarding” an item refers to any means of getting that item from one location to the next, whether by physically transporting that item or otherwise (where that is possible) and includes, at least in the case of data, physically transporting a medium carrying the data or communicating the data. Examples of communicating media include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the internet or including email transmissions and information recorded on websites and the like.

Claims

WHAT IS CLAIMED IS:

1. An infusion system, comprising: a display device configured to display an infusion metric of an infusion therapy; an eye-tracking sensor configured to detect gaze points that correspond to locations on the display device at which a user is looking; and a processor configured to: display the infusion metric via the display device; determine, based on a status of the infusion therapy, that the infusion metric is a high-priority infusion metric; detect the gaze points via the eye-tracking sensor; determine, based on the gaze points, that the user is unaware of the high-priority infusion metric; and responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to emphasize the high-priority infusion metric.

2. The infusion system of Claim 1, wherein: the high-priority infusion metric is displayed at a particular location on the display device; and determining that the user is unaware of the high-priority infusion metric comprises determining, based on the gaze points, that the user has not looked at the particular location for a particular amount of time after the processor determined that the infusion metric was a high- priority infusion metric.

3. The infusion system of Claim 2, wherein the processor is further configured to receive a clinical experience level of the user and adjust the particular amount of time based on the clinical experience level.

4. The infusion system of Claim 1, wherein the processor is further configured to: determine, based on the gaze points, that the user has focused on the high-priority infusion metric; and responsive to determining that the user focused on the high-priority infusion metric, adjust the display device to stop emphasizing the high-priority infusion metric.

5. The infusion system of Claim 1, wherein adjusting the display device to emphasize the high-priority infusion metric comprises changing a size, a color, or an emphasis of a font used to display the high-priority infusion metric.

6. The infusion system of Claim 1, wherein adjusting the display device to emphasize the high-priority infusion metric comprises displaying a notification via the display device regarding the high-priority infusion metric.

7. The infusion system of Claim 1, wherein the processor is further configured to: display other infusion metrics of the infusion therapy via the display device; and responsive to determining that the user is unaware of the high-priority infusion metric, adjust the display device to deemphasize the other infusion metrics.

8. The infusion system of Claim 1, further comprising a proximity sensor configured to detect a distance between the display device and the user, and wherein the processor is further configured to determine that the user is unaware of the high-priority infusion metric when the distance satisfies a distance threshold.

9. The infusion system of Claim 1, wherein the processor is configured to: operate in a closed-loop mode wherein adjustments to the infusion therapy are made without user interaction; and while operating in the closed-loop mode and responsive to determining that the user is unaware of the high-priority infusion metric, transition from operating in the closed-loop mode to operating in a non-closed-loop mode wherein a user input is required to continue the infusion therapy.

10. The infusion system of Claim 1, wherein the processor is further configured to create an activity log including data regarding (i) the gaze points and (ii) an amount of time between adjusting the display device to emphasize the high-priority infusion metric and determining that the user is aware of the high-priority infusion metric.

11. A computer-implemented method for increasing clinician engagement with an infusion device, the method comprising: displaying, via a display device, an infusion metric of an infusion therapy; determining, based on a status of the infusion therapy, that the infusion metric is a high- priority infusion metric; detecting, via an eye-tracking sensor, gaze points that correspond to locations on the display device at which a user is looking; determining, based on the gaze points, that the user is unaware of the high-priority infusion metric; and responsive to determining that the user is unaware of the high-priority infusion metric, adjusting the display device to emphasize the high-priority infusion metric.

12. The computer-implemented method of Claim 11, wherein: the high-priority infusion metric is displayed at a particular location on the display device; and determining that the user is unaware of the high-priority infusion metric comprises determining, based on the gaze points, that the user has not looked at the particular location for a particular amount of time after the processor determined that the infusion metric was the high-priority infusion metric.

13. The computer-implemented method of Claim 11, further comprising: determining, based on the gaze points, that the user is aware of the high-priority infusion metric; and responsive to determining that the user is aware of the high-priority infusion metric, adjusting the display device to stop emphasizing the high-priority infusion metric.

14. The computer-implemented method of Claim 11, further comprising: while operating in a closed-loop mode, wherein adjustments to the infusion therapy are made without user interaction, and responsive to determining that the user is unaware of the high-priority infusion metric, transition from operating in the closed-loop mode to operating in a non-closed-loop mode wherein a user input is required to continue the infusion therapy.

15. A non-transitory, machine-readable storage medium embodying instructions that, when executed by a machine, facilitate the machine to perform the computer-implemented method of any one of Claims 11-14.