Guiding physical interactions with a syringe pump

Abstract

An infusion system includes a syringe pump, a display device, sensors, and a processor. The sensors can be configured to generate data associated with a physical interaction with the syringe pump. The

Description

GUIDING PHYSICAL INTERACTIONS WITH A SYRINGE PUMPTECHNICAL FIELD

[0001] The present disclosure relates generally to syringe pumps for use in infusion therapies, and more specifically to automatically providing loading and unloading guidance relating thereto.BACKGROUND

[0002] Setting up and operating a syringe pump can be complex. In order to ensure patient safety, the clinician must follow particular steps and procedures in loading, programming, and unloading the syringe pump. Unfortunately, current syringe pump technologies do little to assist clinicians in following said steps and procedures and identifying when a syringe is misloaded. In the event of a misstep, troubleshooting is often left up to the clinician or a technician.SUMMARY

[0003] The subject technology includes a “smart” syringe pump device that provides automatic loading, programming, and unloading guidance based on physical user interactions with the syringe pump. The syringe pump, or a device connected thereto, predicts whether, for example, the user is attempting to load or unload the syringe pump and provides relevant guidance accordingly. In this manner, syringe pump accessibility is improved and the risk of misusing or reusing a syringe or administrative set is decreased.

[0004] According to various aspects of the subject technology, an infusion system includes a syringe pump with a receptacle for receiving a syringe having a barrel and a plunger. The infusion system also includes a display device, a plurality of sensors, and a processor. The plurality of sensors are configured to generate sensor data associated with a physical interaction with the syringe pump. The processor is configured to continuously monitor the sensor data generated by the plurality of sensors. The processor is also configured to detect, based on the monitored sensor data, the physical interaction with the syringe pump by an external user. Additionally, the processor is configured to perform operations responsive to detecting the physical interaction. The operations include determining a loading condition of the syringe based on the monitored sensor data. The operations also include displaying guidance for loading the syringe on the display device when the loading condition indicates the syringe isnot loaded in the receptacle. Further, the operations include, when the loading condition indicates the syringe is loaded in the receptacle, (1) determining an infusion state of the syringe and (2) displaying guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

[0005] According to various aspects of the subject technology, a computer-implemented method for guiding physical interactions with a syringe pump includes continuously monitoring sensor data generated by a plurality of sensors configured to generate sensor data associated with a physical interaction with a syringe pump. The computer-implemented method also includes detecting, based on the monitored sensor data, the physical interaction with the syringe pump by an external user. Additionally, the computer-implemented method includes performing operations responsive to detecting the physical interaction. The operations include determining a loading condition of a syringe based on the monitored sensor data. The operations also include displaying guidance for loading the syringe on a display device when the loading condition indicates the syringe is not loaded in a receptacle of the syringe pump. Further, the operations include, when the loading condition indicates the syringe is loaded in the receptacle, (1) determining an infusion state of the syringe and (2) displaying guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

[0006] According to various aspects of the subject technology, a non-transitory, machine- readable storage medium embodying instructions that, when executed by a machine, facilitate the machine to perform the method described above.

[0007] 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

[0008] 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.

[0009] FIG. 1 depicts an example infusion device including a control module, a peristaltic infusion pump 131, and a syringe pump 132, according to various aspects of the subject technology.

[0010] FIG. 2 depicts an example syringe pump module, according to various aspects of the subject technology.

[0011] FIG. 3 depicts an example standalone syringe pump infusion device, according to various aspects of the subject technology.

[0012] FIG. 4 depicts an example process for guiding physical interactions with a syringe pump, according to various aspects of the subject technology.

[0013] FIGS. 5A, 5B, and 5C depict example first and second processes for providing automatic guidance with respect to a syringe pump, according to various aspects of the subject technology.

[0014] FIGS. 6 A and 6B depict a table including example states of a syringe pump and guidance corresponding thereto, according to various aspects of the subject technology.

[0015] FIG. 7 is a conceptual diagram illustrating an example electronic system for guiding physical interactions with a syringe pump, according to various aspects of the subject technology.

[0016] FIG. 8 is a diagram illustrating a guidance prediction system that implements various aspects of the subject technology.DETAILED DESCRIPTION

[0017] 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.

[0018] The subject technology provides a syringe pump that provides automatic guidance for loading, programming, and / or unloading a syringe. The guidance is provided based on a user’s physical interactions with the syringe pump. For example, the interactions may suggestthat the user is attempting to load, program, or unload the syringe pump. Accordingly, the syringe pump or a device connected thereto can display guidance to assist the user with the intended action. In this manner, the syringe pump and / or the connected device may increase the accessibility of the syringe pump while also decreasing the risks of syringe misload and misuse.

[0019] As an example, when the user manipulates (e.g., opens, moves, shifts) the drive head or the barrel clamp of the syringe pump, the infusion device may collect data via various sensors - such as a cradle sensor, a drive head sensor, or a barrel clamp sensor - and take specific operational actions in accordance with the collected data. For example, in line with sensor data and the nature of the user interaction, the infusion device may automatically provide programming, unloading, or loading guidance to the user. Additionally, the infusion device may generate an alarm. The infusion device may also set one or more timers (e.g., a siphon timer, an idle timer) that correspond to one or more actions or alarms (e.g., a siphon alarm, an idle revert action). Accordingly, the infusion device may improve accessibility and decrease the risks of associated with improper use of the infusion device.

[0020] FIG. 1 depicts an example infusion device 100 including a control module 104, a peristaltic infusion pump 131, and a syringe pump 132, according to various aspects of the subject technology. As depicted, the peristaltic infusion pump 131 and the syringe pump 132 (collectively, infusion pumps 131 and 132) are mounted at either side of a control module 104 configured for programming the infusion pumps 131 and 132.

[0021] According to various implementations, the control module 104 is used to provide a user interface for the infusion pumps 131 and 132. The control module 104 may also act as an interface between the infusion pumps 131 and 132 and external devices (e.g., a device terminal, a smartphone or tablet computer). As depicted in FIG. 1, the control module 104 includes a display 114 for visually presenting various information to a clinician, such as operating parameters of the infusion pumps 131 and 132 or alerts (e.g., alert indications, alert messages) relating to the infusion pumps 131 and 132. The control module 104 may also include a speaker to provide audible alerts. In some implementations, the display 114 may be implemented as a touchscreen display. In this manner, the control keys 116A-C may be omitted or reduced in number by providing corresponding interactive elements via a graphical user interface presented via the display 114.

[0022] Additionally, the control module 104 may include a communications system by which the control module 104 may communicate with external equipment. For example, the control module 104 may communicate with a medical facility server, a computer (e.g., a handheld communication device or a laptop-type of computer), or an information device. In communicating with these devices, the control module 104 may transfer information to the devices, or the control module 104 may download information (e.g., drug libraries) from them.

[0023] The communications system may be used to transfer access and interaction information for users encountering the control module 104 or a device coupled therewith (e.g., infusion pumps 131 and 132, or a bar code scanner). Additionally, the communications system may include one or more of a radio frequency (RF) system, an optical system such as infrared, a BLUETOOTH™ system, or other wired or wireless system. A communications system (and / or the aforenoted barcode scanner) may additionally be included integrally with the infusion pumps 131 and 132, such as in implementations where the infusion device 100 does not include a control module. Information input devices need not be hard-wired to medical instruments; information may be transferred through a wireless connection, as well.

[0024] In addition to the infusion pumps 131 and 132, the control module 104 may also be connected to other functional modules, such as physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, or pulse oximeter monitors), therapy devices, or other drug delivery devices (e.g., additional infusion pumps), according to the teachings set forth herein. Moreover, the control module 104 may a central processing unit (CPU) connected to a memory, such as random access memory (RAM). In some implementations, the control module 104 includes a main, non-volatile storage unit, such as a hard-disk drive or a non-volatile flash memory. For example, the control module 104 may for store software data on the non-volatile storage unit. Additionally, the control module may include one or more internal buses for connecting the aforementioned elements (see FIG. 7).

[0025] In various implementations, the display 114 is a touch screen for displaying information to a user and allowing a user to input information by touching defined areas of the screen. Additionally, or in the alternative, the display 114 could 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.

[0026] The control module 104 may include a data input device, such as a bar code reader capable of scanning and interpreting data printed in bar-coded format. Additionally, or in thealternative, the data input device can be a device for entering coded data into a computer, such as a device(s) for reading magnetic strips, radio-frequency identification (RFID) devices whereby digital data encoded in RFID tags or smart labels are captured by the data input device via radio waves, PCMCIA smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of the data input device include a voice activation or recognition device or a portable personal data assistant (PDA).

[0027] FIG. 2 depicts an example syringe pump module 202 (e.g., syringe pump 132 of FIG. 1), according to various aspects of the subject technology. Syringe pumps can be used for the infusion of medical fluids (e.g., parenteral fluids) into the human body. In many cases, loading, programming, and unloading a syringe pump requires closely following particular steps.

[0028] Aspects of the implementations disclosed herein seek to improve syringe pump accessibility by offering automatic guidance via the syringe pump or a device connected thereto. As discussed in more detail below, the syringe pump may include one or more sensors for detecting user interactions with the syringe pump. Based on these interactions, the syringe pump may then automatically provide the user with guidance for loading, programming, or unloading the syringe pump.

[0029] In the depicted implementation, an example infusion system 200 includes the syringe pump module 202, which may include a drivetrain subsystem. A syringe 204 is shown next to the pump rather than mounted in the pump, for clarity of illustration. The syringe pump module 202 includes a cradle 206 in which a barrel 208 of the syringe 204 can rest when mounted in the syringe pump module 202. The cradle 206 can include a clamp 210 to securely hold the barrel 208 in a fixed position in the cradle 206 so that axial and lateral movement is resisted.

[0030] The clamp 210 can be pivoted so that it may be moved into an open position to permit loading or removal of the syringe 204 and a closed position in which it extends over the cradle 206 to hold a mounted barrel 208. A barrel flange 212 of the syringe 204 can be located in a barrel flange groove 214 in the syringe pump module 202 to immobilize the barrel 208 from axial movement during movement of the plunger 216 within the barrel 208.

[0031] In the example infusion system 200, the syringe 204 includes the barrel 208 and the plunger 216. The plunger 216 includes a push-button 218 having an inner side 220 and being interconnected with a stopper 222 of the plunger 216 by a piston 240. The plunger 216 caninclude the stopper 222 to engage an inner wall of the barrel 208 to prevent fluid from leaking past the stopper 222 (e.g., by creating a seal between the stopper 222 and the inner wall of the barrel 208).

[0032] The drive head 224 of the syringe pump module 202 may be connected to a screwdrive mechanism that includes a motor, for connecting the linear motion of the screw-drive mechanism to the plunger 216 in order to empty the contents of the syringe 204 through an administration set 244 and into a patient. The flow rate of the syringe pump module 202 can be controlled by the syringe pump module 202 based on programmed parameters (e.g., a requested flow rate, a type of the syringe).

[0033] When mounted in the syringe pump module 202, the push-button 218 can be held by the drive head 224 with a plunger retainer comprising a pair of pivotally mounted claws, first retainer claw 226 and second retainer claw 228, shown in the closed position in FIG. 2. The retainer claws 226 and 228 can curve inwardly toward each other to grasp the pushbutton 218 while the syringe 204 is mounted in the syringe pump module 202.

[0034] A rotation knob 230 can be used to control the positions of the first and second retainer claws 226 and 228 to allow removal and insertion of the push-button 218 and to release the split-nut from the driveshaft to permit axial positioning of the drive head 224. Also, the syringe 204 can be provided for use with the syringe pump module 202 with different quantities of fluid, such that the plunger 216 of the syringe 204 may be located at different positions in relation to the barrel 208.

[0035] The drive head 224 may be manually adjustable to accommodate syringes with different beginning plunger positions. A syringe inserted in the cradle 206 can align with the drive head 224 within a particular axial range. The points where the axial center lines of the syringes intersect the driver can change according to the size of the syringe but only in one direction along the drive head 224. A guide device 232 can extend from the drive head 224 to a point within a body of the syringe pump module 202.

[0036] The syringe pump module 202 can include a control panel 234 providing multiple buttons 236 for control of the syringe pump module 202 as well as a display 238 used to present pump-specific information to the operator. The buttons 236 can allow the operator to program the syringe pump module 202 for the flow rate, the volume to be infused, and / or other parameters. The display 238 can present the programmed flow rate, the amount of fluid remaining to be infused, as well as alarms and other information.

[0037] The syringe pump module 202 can also include one or more sensors. In some implementations, the syringe pump module 202 includes a cradle sensor 246 positioned in or near the cradle 206. For example, the cradle sensor 246 may be configured to detect whether a syringe is loaded in the cradle 206. As another example, the cradle sensor 246 may be configured to detect whether a syringe loaded in the cradle 206 is empty.

[0038] In some implementations, the syringe pump module 202 includes a barrel clamp sensor 248 positioned on or near the clamp 210. For example, the barrel clamp sensor 248 may be configured to detect movement of the clamp 210. As another example, the barrel clamp sensor 248 may be configured to detect whether or how tightly the clamp 210 grips the barrel 208 of the syringe 204 (e.g., corresponding to a size of the syringe 204). As yet another example, the barrel clamp sensor 248 may be configured to detect a degree of displacement of the clamp 210. A completely displaced clamp 210 may indicate that the clamp 210 is open (e.g., for loading or unloading of a syringe). By contrast, a clamp 210 displaced only slightly from a completely closed position may indicate that the clamp 210 is gripping a syringe (e.g., with the degree of displacement corresponding to a diameter of the syringe).

[0039] In some implementations, the syringe pump module 202 includes a drive head sensor 250 positioned on or near the drive head 224. For example, the drive head sensor 250 may be configured to detect movement of the drive head 224. As another example, the drive head sensor 250 may be configured to detect a position of the drive head 224. In some implementations, the syringe pump module 202 includes a plunger retainer sensor 252 positioned on or near the retainer claw 228. For example, the plunger retainer sensor 252 may be configured to detect opening and / or closing of the retainer claw 228. As another example, the plunger retainer sensor 252 may be configured to detect whether or how tightly the retainer claw 228 grips the push-button 218 and / or the piston 240 of the plunger 216. In some implementations, the syringe pump module 202 includes a barrel flange sensor 254 positioned near or within the barrel flange groove 214. For example, the barrel flange sensor 254 may be configured to detect whether the barrel flange 212 is inserted into and / or secured within the barrel flange groove 214.

[0040] When loading the syringe 204, a clinician releases and raises up the drive head 224. Such physical interaction may be detected by the drive head sensor 250. The clinician may then pull and / or twist the clamp 210 out of the way, activating the barrel clamp sensor 248. The clinician loads the syringe 204 and the cradle sensor 246 detects the barrel 208 of the syringe 204 when it is loaded into the cradle 206. The barrel flange sensor 254 detects thebarrel flange 212 when the barrel flange 212 is secured by the barrel flange groove 214. The clinician presses and / or twists the clamp 210 back in place to secure the syringe 204 within the cradle 206 and barrel clamp sensor 248 may detect the clamp 210 has secured the syringe 204. The clinician opens the retainer claws 226 and 228 and lowers the drive head 224 onto the push-button 218 of the plunger 216, releasing the retainer claws 226 and 228 to secure the plunger 216 as the claws close around the push-button 218. Such physical interaction may be detected by the drive head sensor 250 and the plunger retainer sensor 252, respectively.

[0041] FIG. 3 depicts an example standalone syringe pump 300 infusion device, according to various aspects of the subject technology. While the example syringe pump 300 is shown as a standalone device, the syringe pump 300 may be configured as a functional module of a modular infusion system, such as a syringe module (e.g., syringe pump 132 of FIG. 1, syringe pump module 202 of FIG. 2) in a patient care device (e.g., infusion device 100 of FIG. 1).

[0042] Similar to the implementations of FIG. 2, when a syringe 302 is loaded into the syringe pump 300, a plunger flange 304 at the end of a syringe plunger 306 is held in or against a drive head 308 by a flange clamp 310. The syringe barrel 312 is secured by a barrel clamp 314. The drive head 308 includes a pushing surface on which the plunger flange 304 will rest as the drive head 308 moves toward the syringe barrel 312, thus pushing the syringe plunger 306 into the secured syringe barrel 312 to expel the contents of the syringe 302 through an administrative set 316 to the patient.

[0043] As with the drive head 224 of FIG. 2, the drive head 308 may be connected to a screw-drive mechanism that includes a motor, for connecting the linear motion of the screwdrive mechanism to the syringe plunger 306 in order to empty the syringe 302. The flow rate of the syringe pump 300 can be controlled by the syringe pump 300 based on programmed parameters (e.g., a requested flow rate, a type of the syringe).

[0044] Typically, syringe pumps do not experience upstream pressure conditions because the fluid to be infused is housed in the syringe barrel 312 and pushed into the administrative set 316 by way of the syringe plunger 306. Accordingly, in some implementations, the syringe pump 300 does not include an upstream pressure sensor. Downstream pressure conditions, on the other hand, are more commonly experienced by syringe pumps. Accordingly, in some implementations, the syringe pump 300 includes a force sensor for detecting said downstream pressure. In some implementations, the force sensor measures the force exerted by the drive head 308 of the syringe pump on the syringe plunger 306.

[0045] In some implementations, the syringe pump 300 includes a high-resolution pressure sensor that interfaces with a pressure disc on the administrative set 316. The pressure disc provides a relatively large area in contact with the pressure sensor. This allows the pressure sensor to measure the pressure inside the administrative set 316 more directly (e.g., rather than through the head of the syringe plunger 306) and with higher resolution and higher accuracy as compared to a force sensor located at the drive head 308. The measurements from the high- resolution pressure sensor and those from the drive head force sensor can be used independently or in conjunction with each other to detect an empty condition in the syringe pump 300.

[0046] In addition to various buttons or switches, which the operator may use to activate and program the syringe pump 300, there is also a display screen 318. The display screen 318 may be a liquid-crystal display (LCD) having a small number of segments, for example seven segments in a figure-of-eight configuration per character, adapted to display a small number of alphanumeric characters.

[0047] Additionally, the display 318 may be monochromatic. For example, it might only display red, green, or black characters. Alternatively, the display 318 can be a more complicated LCD capable of displaying more characters and / or more complicated characters. The LCD may be backlit, for example, using light emitting diodes (LEDs). In some implementations, the infusion pump may include a thin-film transistor (TFT) LCD. In some implementations, the display 318 is a touchscreen, such as a capacitive touchscreen.

[0048] When programming the syringe pump 300, a user may input the type of the syringe 302 being used. The syringe pump 300 may store in an internal memory a database of known syringe types containing information such as syringe diameter and / or stroke. In this manner, the infusion pump firmware can calculate the position of the syringe plunger 306 based on movement of the drive head 308 and the type and size of the syringe 302. This may allow the machine to display the volume infused, time elapsed, volume remaining, and / or time remaining. As the infusion continues and the drive head moves, these calculations can be updated, and the information displayed at display 318 can be changed.

[0049] The syringe pump 300 may include an input interface with controls operable to enter, increase, and / or decrease pumping parameters (e.g., flow rate, or volume to be infused). As depicted, in some implementations, input keys 320A-C are physically present on the device.However, in some implementations, input keys are graphically displayed on the display 318 (e.g., a touchscreen display).

[0050] In some implementations, the syringe pump 300 may be configured to identify (e.g., using a sensor) a disposable container loaded by the device. For example, the syringe pump 300 may perform electro-mechanical measurements on the loaded syringe to identify certain characteristics about the loaded container. Additionally, in some implementations, the syringe pump 300 is configured to detect the size (e.g., diameter) of the syringe 302 inserted into the syringe pump 300. For example, the syringe pump 300 may include a sensor that measures the size of the syringe 302 (e.g., whether it is a 6 ml, a 10 ml, or a 50 ml syringe) based on how tightly the syringe is being hugged or based on the position of the barrel clamp 314. For example, based on measurements made by the sensor, the syringe pump may determine a list of possible candidate syringes. The device may then request confirmation via the display whether the container is within that list. During the infusion, volume infused and / or flow rate may be calculated based on the type of the syringe 302 (e.g., based on the size of the syringe barrel 312).

[0051] Like the syringe pump module 202, in some implementations, the syringe pump 300 includes a barrel clamp sensor (not pictured) positioned on or near the barrel clamp 314. For example, the barrel clamp sensor may be configured to detect movement of the barrel clamp 314. As another example, the barrel clamp sensor may be configured to detect whether or how tightly the barrel clamp 314 grips the syringe barrel 312 (e.g., corresponding to a size of the syringe 302). As yet another example, the barrel clamp sensor may be configured to detect a degree of displacement of the barrel clamp 314. A completely displaced barrel clamp 314 may indicate that the barrel clamp 314 is open (e.g., for loading or unloading of a syringe). By contrast, the barrel clamp 314 being displaced only slightly from a completely closed position may indicate that the barrel clamp 314 is gripping the syringe 302 (e.g., with the degree of displacement corresponding to a diameter of the syringe 302).

[0052] In some implementations, the syringe pump 300 includes a drive head sensor (not pictured) positioned on or near the drive head 308. For example, the drive head sensor may be configured to detect movement of the drive head 308. As another example, the drive head sensor may be configured to detect a position of the drive head 308. In some implementations, the syringe pump 300 includes a plunger retainer sensor (not pictured) positioned on or near the flange clamp 310. For example, the plunger retainer sensor may be configured to detect opening and / or closing of the flange clamp 310. As another example, the plunger retainersensor may be configured to detect whether or how tightly the flange clamp 310 grips the syringe plunger 306 (e.g., a push-button of the syringe plunger 306). In some implementations, the syringe pump 300 includes a barrel flange sensor (not pictured) positioned near or within a barrel flange groove in the syringe pump 300. For example, the barrel flange sensor may be configured to detect whether a flange of the syringe barrel 312 is inserted into and / or secured within the barrel flange groove.

[0053] When loading the syringe 302, a clinician releases and raises up the drive head 308. Such physical interaction may be detected by the drive head sensor. The clinician may then pull and / or twist the barrel clamp 314 out of the way, activating the barrel clamp sensor. The clinician loads the syringe 302 and the cradle sensor detects the syringe barrel 312 when it is loaded into a receptacle of the syringe pump 300. The barrel flange sensor detects the barrel flange when the barrel flange is secured by the barrel flange groove. The clinician presses and / or twists the barrel clamp 314 back in place to secure the syringe 302 within the receptacle and barrel clamp sensor may detect the barrel clamp 314 has secured the syringe 302. The clinician opens the flange clamp 310 and lowers the drive head 308 onto the push-button of the syringe plunger 306, releasing the flange clamp 310 to secure the syringe plunger 306 as the flange clamp 310 closes around the push-button. Such physical interaction may be detected by the drive head sensor and the plunger retainer sensor, respectively.

[0054] In some implementations, the syringe pump 300 is configured to determine that the syringe 302 is loaded based on the sensor data. After determining the syringe is loaded in the receptacle, the syringe pump 300 may prompt the user (e.g., via the display screen 318) to select a type of the syringe 302 (e.g., a syringe size, a syringe brand). The user may respond to the prompt by selecting the syringe type, for example, from a list displayed via the display screen 318.

[0055] The list may include one or more syringe types obtained from an active drug library loaded on the device, and / or obtained from a remote server based on selection of certain parameters at the user interface of the pump (e.g., patient identifier, drug type, etc.). The list of syringes may also include, for example, favorite syringe types previously identified in a drug library editor. Alternatively, if no syringe favorites were chosen in the drug library editor, then the infusion device may display a list of all compatible syringes (e.g., corresponding to a measured barrel size range).

[0056] On receiving a selection of the syringe type, the syringe pump 300 may display a confirmation of the syringe selection. For example, the confirmation may include a size, a brand, or a model of the selected syringe - as well as a prompt for the user to indicate whether the displayed information is correct. Alternatively, or additionally, the user may be able to view information regarding the selected syringe, such as brand or size information, via an auxiliary options menu. In addition to the confirmation, the infusion device may also display a warning regarding risks associated with selecting an incorrect syringe (e.g., impacting device performance).

[0057] If the user needs to change the syringe selection or other settings relating to the infusion therapy (e.g., infusion parameters, such as fluid type, flow rate, or volume to be infused), the user can correct the selection or the other settings. If the user navigates backwards and changes the selected syringe (e.g., brand or size), the syringe pump 300 may discard forward programming (e.g., selections made after the syringe selection). However, once the user confirms that the selected syringe and other settings are correct, in some implementations, the syringe pump 300 proceeds with programming and initiates the infusion therapy.

[0058] In some implementations, after receiving the user-selected syringe type, the syringe pump 300 determines (e.g., based on sensor data), a candidate syringe type. For example, the candidate syringe type may be based on a detected diameter of the syringe barrel 312. After determining the candidate syringe type, the syringe pump 300 may further determine whether the user-selected syringe type corresponds to the candidate syringe type. For example, the syringe pump 300 may determine whether the size (e.g., diameter) of the user-selected syringe type matches the size of the candidate syringe type.

[0059] When the user-selected syringe deviates from the candidate selected syringe type, in some implementations, the syringe pump 300 displays guidance for unloading the syringe 302 and loading a new syringe. Additionally, or in the alternative, the syringe pump 300 may display a notice indicating the user-selected syringe deviates from a detected attribute of the syringe 302. However, if the user-selected syringe corresponds to the candidate syringe type, the syringe pump 300 may determine an infusion state of the syringe and / or proceed with programming.

[0060] FIG. 4 depicts an example process 400 for guiding physical interactions with a syringe pump, according to various aspects of the subject technology. For explanatory purposes, the various blocks of example process 400 are described herein with reference toFIGS. 1, 2, and 3, and the components and / or processes described therein. The one or more of the blocks of process 400 may be implemented, for example, by a control unit (e.g., control module 104 of FIG. 1, or a processor) of a syringe pump.

[0061] In some implementations, one or more of the blocks 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 example process 400 are described as occurring in serial, or linearly. However, multiple blocks of example process 400 may occur in parallel. In addition, the blocks of example process 400 need not be performed in the order shown and / or one or more of the blocks of example process 400 need not be performed.

[0062] In the depicted example, the process 400 includes continuously monitoring sensor data associated with a physical interaction with a syringe pump (e.g., syringe pump module 202 of FIG. 2, or syringe pump 300 of FIG. 3) (402). The sensor data may be generated by a plurality of sensors, such as the sensors described above with respect to the syringe pump module 202 of FIG. 2 (e.g., cradle sensor 246, barrel clamp sensor 248, drive head sensor 250, plunger retainer sensor 252, and / or barrel flange sensor 254) and the syringe pump 300 of FIG. 3. Additionally, or in the alternative, the plurality of sensors may be configured to generate sensor data associated with positioning of a syringe (e.g., syringe 204 of FIG. 2, or syringe 302 of FIG. 3) in a receptacle (e.g., cradle 206 of FIG. 2) of the syringe pump.

[0063] For example, the plurality of sensors may include a drive head sensor (e.g., drive head sensor 250 of FIG. 2) configured to sense when a drive head (e.g., drive head 224 of FIG. 2, or drive head 308 of FIG. 3) of the syringe pump is secured to a plunger (e.g., plunger 216 of FIG. 2, or syringe plunger 306 of FIG. 3) of the syringe. As another example, the plurality of sensors may include a barrel clamp sensor (e.g., barrel clamp sensor 248 of FIG. 2) configured to sense placement of the syringe within a barrel clamp (e.g., clamp 210 of FIG. 2, or barrel clamp 314 of FIG. 3) of the syringe pump. Additionally, or in the alternative, the barrel clamp sensor may be configured to sense a displacement of the barrel clamp (e.g., indicating a diameter of the syringe barrel). In some implementations, the drive head sensor and the barrel clamp sensor are used to determine that the syringe is loaded in the receptacle when, based on the monitored sensor data, the drive head is secured to the plunger and the syringe is placed in the barrel clamp. Continuously monitoring may refer to, for example, recording a measurement according to a continuous schedule (e.g., every second, every minute, and the like).

[0064] The process 400 detects a physical interaction with the syringe pump by an external user based on the monitored sensor data (404). For example, the physical interaction may include any of the physical interactions discussed with respect to FIG. 2, such as pulling or twisting the barrel clamp away from the receptacle, loading the syringe, inserting the barrel flange of the syringe into the barrel flange groove of the syringe pump, pressing or twisting the barrel clamp to secure the syringe in the receptacle, and / or opening or closing the retainer claws. As another example, the physical interaction may include sliding the drive head towards or away from the receptacle. In short, the physical interaction can include any physical movement or manipulation of the syringe pump by the user.

[0065] As discussed previously, the aforenoted plurality of sensors may include a barrel flange sensor (e.g., barrel flange sensor 254 of FIG. 2) configured to detect a flange (e.g., barrel flange 212 of FIG. 2) of the syringe barrel. The plurality of sensors may also include a drive head motion sensor (e.g., drive head sensor 250 of FIG. 2) configured to detect physical movement of the drive head. Accordingly, in some implementations, detecting the physical interaction may include detecting a signal from two or more of the drive head sensor, the barrel clamp sensor, the barrel flange sensor, and / or the drive head motion sensor. In some implementations, detecting the physical interaction may include detecting placement or movement of the syringe by at least one of the plurality of sensors.

[0066] The process 400 determines a loading condition of the syringe based on the monitored sensor data and responsive to detecting the physical interaction (406). In some implementations, determining the loading condition includes determining whether a syringe is loaded in the receptacle of the syringe pump. For example, as discussed above, in some implementations, the drive head sensor and the barrel clamp sensor may be used to determine the syringe is loaded in the receptacle.

[0067] In some implementations, determining the loading condition of the syringe includes using the drive head sensor, the barrel clamp sensor, and / or other sensors of the plurality of sensors are used to determine whether the syringe is loaded properly in the syringe pump. For example, the loading condition may indicate misloading of the syringe if one or more of the plurality of sensors indicate the syringe is loaded in the receptacle and one or more of the plurality of the sensors indicate that the syringe is not loaded in the receptacle. In this regard, responsive to the loading condition indicating misloading of the syringe, the process 400 may include displaying an alert on the display device indicating the syringe is misloaded or generating a misload alarm.

[0068] In some implementations, misloading of the syringe may create a risk of the fluid in the syringe siphoning through the administration set (e.g., administration set 244 of FIG. 2, or administration set 316 of FIG. 3) and to the patient prior to the start of infusion and unbeknownst to the clinician. This is referred to herein as a siphon risk or a siphon condition. In some implementations, the process 400 includes determining that the syringe is associated with a siphon condition when, based on the monitored sensor data, the syringe is placed in the barrel clamp but the drive head is not secured to the plunger. Responsive to determining the syringe is associated with the siphon condition, the process 400 may include initiating a siphon timer (e.g., a thirty-second timer, a sixty-second timer). Upon expiration of the siphon timer, the process 400 may include generating an alarm or an alert (e.g., indicating the siphon risk).

[0069] Moreover, the process 400 includes determining whether the syringe is loaded in a receptacle of the syringe pump (408). For example, the determination of whether the syringe is loaded may be based on monitored sensor data, for example, from a receptacle sensor (e.g., cradle sensor 246 of FIG. 2), a retainer sensor (e.g., plunger retainer sensor 252), and / or the aforenoted barrel flange sensor of the plurality of sensors.

[0070] If it is determined the syringe is not loaded in the receptacle, the process includes displaying loading guidance via a display device (410). In some implementations, determining the syringe is not loaded in the receptacle includes determining the syringe is not properly loaded in the receptacle. Responsive to such a determination, displaying the loading guidance may include displaying an indication regarding why the loading of the syringe was deemed improper. For example, the indication may notify the user that the plunger is not secured in the retainer claws, the barrel clamp is not secured tightly around the barrel of the syringe, and so on.

[0071] However, if it is determined the syringe is loaded in the receptacle, the process 400 includes determining an infusion state of the syringe (412). For example, determining the infusion state of the syringe may be based on the monitored sensor data and whether the syringe is empty (e.g., as detected by the receptacle sensor) or whether the drive head is in a fully- extended, starting position (e.g., as detected by the drive head sensor). As another example, determining the infusion state of the syringe may be based on the monitored sensor data, the infusion history of the syringe pump, and whether an infusion has been initiated since the syringe was placed in the receptacle.

[0072] After determining the infusion state of the syringe (412), the process 400 includes determining whether the syringe was used in an infusion (414). This determination may be based on the infusion state of the syringe and the aforenoted determinations with respect thereto. For example, if an infusion has been initiated since the syringe was placed in the syringe pump, then the syringe can be considered to have been used in an infusion.

[0073] If it is determined that the syringe was used in an infusion, the process 400 includes displaying unloading guidance via the display device (418). In this manner, the process 400 decreases the likelihood of the syringe mistakenly being used in another infusion (e.g., for another patient) by reminding the user to unload the syringe. Likewise, the process 400 decreases the likelihood of siphon risk by suggesting removal of the syringe from the syringe pump once the syringe is no longer needed for the infusion.

[0074] On the other hand, if it is determined the syringe was not used in an infusion, the process 400 includes displaying guidance based on the monitored sensor data (416). For example, when the loading condition indicates the syringe is loaded in the receptacle and the infusion state indicates the syringe was not used in an infusion, the process 400 may include determining whether a syringe type has been selected by the external user. The process 400 may further include displaying guidance for unloading the syringe on the display device responsive to determining that the user has selected the syringe type. Moreover, the process 400 may include displaying guidance for unloading the syringe on the display device responsive to determining that the user has not selected the syringe type and responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the barrel clamp. Additionally, the process 400 may include displaying guidance for loading the syringe on the display device responsive to determining that the user has not selected the syringe type and responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of a drive head of the syringe pump.

[0075] Moreover, the process 400 may include, when the loading condition indicates the syringe is loaded in the receptacle performing one or more operations. For example, the one or more operations may include determining that the syringe pump is in a standby, delay, or pause state. Further, the one or more operations may include, responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the barrel clamp while the syringe pump is in the standby, delay, or pause state, generating a misload alarm when the syringe pump receives a request to resume infusion. As another example, the one or more operations may include, responsive to determining, based on the monitored sensor data,that the physical interaction comprises movement of the drive head while the syringe pump is in the standby, delay, or pause state, cancelling the infusion, discarding a user-selected syringe type, and displaying a home screen on the display device. As yet another example, the one or more operations may include, responsive to determining, based on the monitored sensor data, that the physical interaction comprises removal of the syringe from the receptacle while the syringe pump is in the standby, delay, or pause state, generating a high-priority alarm, cancelling the infusion, discarding the user-selected syringe type, and displaying a home screen on the display device.

[0076] Furthermore, in some implementations, the process 400 may include, when the loading condition indicates the syringe is loaded in the receptacle, determining that the syringe pump is in an infusion-complete state. The process 400 may also include displaying guidance for unloading the syringe on the display device when the loading condition indicates the syringe is loaded in the receptacle, the infusion state indicates the syringe was used in an infusion, the syringe pump is in an infusion-complete state, and responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the barrel clamp or the drive head.

[0077] Many of the above-described blocks of example process 400, and related features and applications, may also be implemented as software processes that are specified as a set of specific instructions recorded on a computer readable storage medium (also referred to as computer readable medium), and may be executed automatically (e.g., without user intervention). When these specific instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.

[0078] The term “software” is meant to include, where appropriate, firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some implementations, multiple software aspects of the subject disclosure can be implemented as sub-parts of a larger program while remaining distinct software aspects of the subject disclosure. In some implementations, multiple software aspects can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software aspect described here is within the scope of the subjectdisclosure. In some implementations, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.

[0079] A computer program (also known as a program, software, software application, script, or code) can be written in a programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in one or more forms, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

[0080] FIGS. 5A, 5B, and 5C depict example first (FIG. 5A) and second (FIGS. 5B and 5C) processes 500 and 550 for providing automatic guidance with respect to a syringe pump, according to various aspects of the subject technology. One or more of the blocks of the first and second processes 500 and 550 may be implemented based on one or more machine learning algorithms. Moreover, 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 are described as occurring in serial, or linearly. However, multiple blocks may occur in parallel. Additionally, the blocks of the first and second processes 500 and 550 need not be performed in the order shown and one or more of the blocks of the process 500 and 550 need not be performed.

[0081] For illustrative purposes, the first process 500 is described as occurring at an infusion device, such as the infusion device 100 of FIG. 1. However, one or more blocks of the first process 500 may be implemented by other computing devices, such as the syringe pump module 202 of FIG. 2 or the syringe pump 300 of FIG. 3, or an electronic device connected thereto.

[0082] In FIG. 5A, the first process 500 includes detecting (502) selection of a syringe pump module (e.g., syringe pump module 202 of FIG. 2). For example, a user can select thesyringe pump module via the control module (e.g., control module 104 of FIG. 1) of an infusion device (e.g., infusion device 100 of FIG. 1).

[0083] After the selection is detected, the process 500 includes determining whether a syringe is loaded at the selected syringe pump module (504). For example, the infusion device may determine whether the syringe is loaded using one or more sensors (e.g., via cradle sensor 246 of FIG. 2) at the selected syringe pump module.

[0084] Responsive to determining that a syringe is not loaded, the process includes performing one or more operations (504-N). In some implementations, the operations (504-N) include prompting the user to load a syringe. For example, the infusion device may display instructions regarding how to properly load the syringe.

[0085] The operations (504-N) may also include determining whether the syringe was properly loaded into the selected syringe pump module. After determining that the syringe was properly loaded, the operations (504-N) may further include prompting the user to select a syringe type. For example, prompting the user may include displaying a syringe selection screen that includes a list of syringe types (e.g., including syringe brands or syringe sizes).

[0086] If the user does not select a syringe type within a predetermined amount of time, the infusion device can also revert to displaying a home screen. Additionally, if the user closes the syringe selection screen, the infusion device can revert to displaying the home screen. However, if the infusion device receives a selection of a syringe type (e.g., prior to expiration of a revert timer), the infusion device may then prompt the user for selection of a fluid. For example, prompting the user may include displaying a fluid selection screen that includes a list of fluids.

[0087] If the user removes the syringe from the infusion device, the infusion device may discard the syringe selection and / or revert to displaying the home screen. Additionally, as with the syringe selection screen, if the user closes the fluid selection screen, the infusion device may revert to displaying the home screen. Alternatively, the infusion device can instead return to displaying the syringe selection screen (e.g., retaining the selected syringe) if the user closes the fluid selection screen.

[0088] If the infusion device determines that the user did not load a syringe (e.g., within a predetermined amount of time), the infusion device may stop prompting the user to load a syringe and / or revert to displaying the home screen.

[0089] Returning to FIG. 5A, the process 500 further includes determining whether the syringe is misloaded (506) responsive to determining that the syringe was loaded at the selected syringe pump module (504). If it is determined that the syringe is misloaded, the process 500 includes performing one or more operations (506- Y).

[0090] In some implementations, the operations (506-Y) include determining whether the syringe is misloaded in the infusion device. For example, determining whether the syringe is misloaded may include determining whether the syringe is misloaded in a barrel clamp (e.g., clamp 210 of FIG. 2, or barrel clamp 314 of FIG. 3) or misloaded in a drive head (e.g., drive head 224 of FIG. 2, or drive head 308 of FIG. 3). The infusion pump may include one or more sensors for these determinations.

[0091] Responsive to determining that the syringe is misloaded, the infusion device may prompt the user to load the syringe properly (e.g., based on readings from the aforenoted sensors). If the user properly loads the syringe, the infusion device may prompt the user to select a syringe type. For example, prompting the user may include displaying a syringe selection screen that includes a list of syringe types (e.g., including syringe brands or syringe sizes).

[0092] If the user does not select a syringe type within a predetermined amount of time, the infusion device can also revert to displaying a home screen. Additionally, if the user closes the syringe selection screen, the infusion device can revert to displaying the home screen. However, if the device receives a selection of a syringe type (e.g., prior to expiration of a revert timer), the infusion device may then prompt the user for selection of a fluid. For example, prompting the user may include displaying a fluid selection screen that includes a list of fluids.

[0093] If the user removes the syringe from the infusion device, the infusion device may discard the syringe selection and / or revert to displaying the home screen. Additionally, as with the syringe selection screen, if the user closes the fluid selection screen, the infusion device may revert to displaying the home screen. Alternatively, the infusion device can instead return to displaying the syringe selection screen (e.g., retaining the selected syringe) if the user closes the fluid selection screen.

[0094] If the infusion device determines that the user did not properly load the syringe (e.g., within a predetermined amount of time), the infusion device may stop prompting the user to properly load the syringe and / or revert to displaying the home screen.

[0095] In some implementations, the operations (506-Y) include determining specifically whether the syringe is misloaded in the drive head and the barrel of the syringe is retained in the barrel clamp. If it is determined that the barrel clamp retains the barrel of the syringe but the syringe is misloaded in the drive head (e.g., the plunger of the syringe is not connected to the drive head), the infusion device may set a siphon timer (e.g., a thirty- or sixty-second timer).

[0096] The siphon timer may function to prevent fluid from being unintentionally siphoned out of the syringe and into a patient via an administration set (e.g., administration set 244 of FIG. 2, or administration set 316 of FIG. 3) connected to the syringe. The risk of this occurring arises when the plunger of the syringe is not secured to the drive head. Accordingly, expiration of the siphon timer may trigger a siphon alarm indicating to the user that the syringe is misloaded and that there is therefore a siphon risk.

[0097] Referring again to FIG. 5A, the process 500 further includes determining whether a type of the syringe was selected (508) responsive to determining that the syringe was not misloaded (506). In some implementations, determining whether the type of the syringe was selected (508) is preceded by prompting the user to select a type of the syringe and / or displaying a list of syringe types (e.g., including syringe brands or syringe sizes). The list of syringe types may be generated based on a detected size of the barrel of the currently-loaded syringe. For example, the infusion device may determine the diameter of the barrel based on a sensor at the barrel clamp (e.g., detecting an angle of the barrel clamp). The infusion device may then display a list of syringe types that correspond to the detected diameter of the syringe barrel.

[0098] Additionally, in some implementations, determining whether the type of the syringe was selected (508) includes confirming that a selected type of the syringe is valid. For example, if the selected type of the syringe does not correspond to a detected size of the syringe, the infusion device may prompt the user to confirm that the selected type of the syringe is correct.

[0099] If it is determined that the type of the syringe was not selected, the process 500 includes performing one or more operations (508-N). In some implementations, the operations (508-N) include prompting the user to select the type of the syringe. As with the operations (504-N) and (506-Y) discussed above, if the user does not select the type of the syringe, the infusion device may return to displaying the home screen (e.g., upon expiration of a revert timer). Likewise, if the user closes the syringe selection screen, the infusion device may return to displaying the home screen.

[0100] Further, if the infusion pump receives a selection of the type of the syringe, in some implementations, the operations (508-N) include determining whether the syringe is empty (e.g., via cradle sensor 246 of FIG. 2). Responsive to determining that the syringe is empty, the infusion device may inform the user that the syringe is empty. The infusion device may also discard the syringe selection and / or return to displaying the home screen.

[0101] Responsive to determining that the syringe is not empty, the infusion device may then prompt the user for selection of a fluid. For example, prompting the user may include displaying a fluid selection screen that includes a list of fluids, as with the syringe selection screen, if the user closes the fluid selection screen, the infusion device may revert to displaying the home screen. Alternatively, the infusion device can instead return to displaying the syringe selection screen (e.g., retaining the selected syringe) if the user closes the fluid selection screen.

[0102] Referring to FIG. 5A, the process 500 further includes determining whether the syringe is empty (510) responsive to determining that a type of the syringe was selected (508). For example, as noted above, the infusion device may include one or more sensors (e.g., cradle sensor 246 of FIG. 2) for determining whether a loaded syringe is empty. If it is determined that the syringe is empty, the process 500 includes performing one or more operations (506- Y). For example, the operations (506- Y) may include prompting the user to properly load a new syringe (e.g., a non-empty syringe).

[0103] If it is instead determined that the syringe is not empty, the process 500 includes performing one or more other operations (506-N). In some implementations, the operations (506-N) include prompting the user for selection of a fluid. For example, prompting the user may include displaying a fluid selection screen that includes a list of fluids. If the user closes the fluid selection screen, the infusion device may return to displaying the home screen. Additionally, the infusion device may also discard the selected type of the syringe if the user closes the fluid selection screen. Similarly, if the user removes the syringe from the infusion device (e.g., an infusion module of the infusion device) or disconnects the infusion module from the infusion device, the infusion device may likewise discard the selection of the type of the syringe.

[0104] In some implementations, the infusion device is configured to detect removal of the syringe or manipulation of the barrel clamp and / or the drive head. For example, the infusion device may include sensors positioned at or near the syringe receptacle (e.g., cradle 206 ofFIG. 2), the barrel clamp, and / or the drive head for detecting removal of the syringe and / or the aforesaid manipulation.

[0105] In some implementations, if the infusion device detects removal of the syringe, the infusion device discards the selection of the type of the syringe and does not proceed with programming. Additionally, in some implementations, if the infusion device detects manipulation of the barrel clamp, the infusion device display an indication of syringe misload. Relatedly, in some implementations, if the infusion device detects manipulation of the drive head, the infusion device likewise displays the syringe misload indication and also sets the aforementioned siphon timer. Upon expiration of the siphon timer, the infusion device may trigger the siphon alarm.

[0106] However, if the infusion device does not detect removal of the syringe or manipulation of the barrel clamp or drive head, the infusion device may proceed with responsive to receiving a selection of the fluid. For example, the infusion device may display an indication that the infusion therapy is ready to initiate. Upon receiving a confirmation from the user (e.g., a button press), the infusion device may begin the infusion therapy. In some implementations, the infusion device displays the selected type of the syringe and the selected fluid prior to initiating the infusion therapy and prompts the user to confirm the same.

[0107] Turning now to FIGS. 5B and 5C, the second process 550 includes various operations and determinations - many of which result in prompting a user with guidance for loading or unloading a syringe pump. As discussed in more detail below, the loading or unloading guidance is offered to the user without explicit input from the user requesting the guidance. Rather, input received at the syringe pump, or a device connected thereto, is used to determine whether the user intends to load or unload the syringe pump. In this manner, the guidance is provided to the user in a manner that increases accessibility and improves the overall user experience.

[0108] For illustrative purposes, the second process 550 is described as occurring at a syringe pump, such as the syringe pump module 202 of FIG. 2 or the syringe pump 300 of FIG. 3. However, one or more blocks of the second process 550 may be implemented by other computing devices, such as the infusion device 100 of FIG. 1, or an electronic device connected to any of the aforementioned devices.

[0109] Starting with FIG. 5B, the second process 550 includes detecting an interaction with a syringe pump (552), such as the syringe pump module 202 of FIG. 2 or the syringe pump 300of FIG. 3. For example, the interaction may include insertion or removal of a syringe (e.g., syringe 204 of FIG. 2, or syringe 302 of FIG. 3), selection of an input (e.g., buttons 236 of FIG. 2, or input keys 320A-C of FIG. 3), or manipulation of the barrel clamp (e.g., clamp 210 of FIG. 2, or the barrel clamp 314 of FIG. 3) or the drive head (e.g., drive head 224 of FIG. 2, or drive head 308 of FIG. 3).

[0110] After detecting the interaction with the syringe pump (552), the process 550 includes determining whether a syringe is inserted in the syringe pump (554). Responsive to determining that a syringe not inserted (554), the process 550 includes performing one or more operations (554-N).

[0111] In some implementations, the operations (554-N) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp (e.g., via barrel clamp sensor 248 of FIG. 2), the syringe pump may prompt the user with loading guidance. As another example, if the syringe pump detects manipulation of the drive head (e.g., via drive head sensor 250 of FIG. 2), the infusion pump may prompt the user with loading guidance.

[0112] In some implementations, the operations (554-N) include responding to proper insertion of a syringe. For example, if the syringe pump detects proper insertion of a syringe (e.g., cradle sensor 246, barrel clamp sensor 248, drive head sensor 250, plunger retainer sensor 252, and / or barrel flange sensor 254 of FIG. 2), the syringe pump may prompt the user to select a type of the inserted syringe. Prompting the user to select a syringe type may include displaying a syringe selection screen including a list of syringe types (e.g., syringe brands, or syringe sizes).

[0113] If the user does not select a type of the syringe within a predetermined amount of time, the syringe pump may revert to displaying a home screen. Similarly, if the user closes the syringe selection screen, the syringe pump may revert to displaying the home screen. However, if the user selects a syringe, the syringe pump may prompt the user to select a fluid for infusion via the syringe pump. Prompting the user to select the fluid may include displaying a fluid selection screen including a list of fluids. If the user closes the fluid selection screen, the syringe pump may return to displaying the home screen. In some implementations, the syringe pump retains the selection of the type of the syringe when returning to displaying the home screen. However, if the syringe pump detects removal of the syringe (e.g., via cradle sensor 246 of FIG. 2), the syringe pump may discard the selected type of the syringe.

[0114] In some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (554-N) include discarding a syringe type selection if the control module detects that the syringe pump module was disconnected from the control module.

[0115] Returning to FIG. 5B, the process 550 further includes determining whether the syringe is misloaded (556) responsive to determining that the syringe is inserted in the syringe pump (554). If it is determined that the syringe is misloaded, the process 550 includes performing one or more operations (556-Y).

[0116] In some implementations, the operations (556-Y) include setting a siphon timer to prevent fluid from siphoning out of the syringe and into a patient. For example, if it is determined that the barrel of the syringe is retained in the barrel clamp but the syringe is not connected to the drive head, the syringe pump may set a siphon timer (e.g., a thirty- or sixty- second timer). Upon expiration of the timer, the syringe pump may trigger an alarm alerting the user of a siphon risk.

[0117] Additionally, in some implementations, the operations (556-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp (e.g., via barrel clamp sensor 248 of FIG. 2), the syringe pump may prompt the user with loading guidance. As another example, if the syringe pump detects manipulation of the drive head (e.g., via drive head sensor 250 of FIG. 2), the infusion pump may prompt the user with loading guidance.

[0118] Moreover, in some implementations, the operations (556-Y) include responding to proper loading of a syringe. For example, if the syringe pump detects proper loading of a syringe (e.g., cradle sensor 246, barrel clamp sensor 248, drive head sensor 250, plunger retainer sensor 252, and / or barrel flange sensor 254 of FIG. 2), the syringe pump may prompt the user to select a type of the loaded syringe. Prompting the user to select a syringe type may include displaying a syringe selection screen including a list of syringe types (e.g., syringe brands, or syringe sizes).

[0119] If the user does not select a type of the syringe within a predetermined amount of time, the syringe pump may revert to displaying a home screen. Similarly, if the user closes the syringe selection screen, the syringe pump may revert to displaying the home screen. However, if the user selects a syringe, the syringe pump may prompt the user to select a fluid for infusion via the syringe pump. Prompting the user to select the fluid may include displaying a fluidselection screen including a list of fluids. If the user closes the fluid selection screen, the syringe pump may return to displaying the home screen. In some implementations, the syringe pump retains the selection of the type of the syringe when returning to displaying the home screen. However, if the syringe pump detects removal of the syringe (e.g., via cradle sensor 246 of FIG. 2), the syringe pump may discard the selected type of the syringe.

[0120] In some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (556- Y) include discarding a syringe type selection if the control module detects that the syringe pump module was disconnected from the control module.

[0121] Referring back to FIG. 5B, the process 550 also includes determining whether a type of the syringe is selected (558) responsive to determining that the syringe was not misloaded (556). If it is determined that a type of the syringe is not selected (558), the process 550 includes performing one or more operations (558-N).

[0122] In some implementations, the operations (558-N) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp, the syringe pump may prompt the user with unloading guidance. As another example, if the syringe pump detects manipulation of the drive head, the infusion pump may prompt the user with loading guidance. Additionally, the syringe pump may also initiate the siphon timer if it detects manipulation of the drive head. Upon expiration of the siphon timer, the syringe pump may trigger an alert indicating a siphon risk.

[0123] The process 550 further includes determining whether the syringe is empty (560) responsive to determining that the type of the syringe is selected (558). For example, determining whether the syringe is empty may utilize one or more sensors (e.g., cradle sensor 246 of FIG. 2) positioned at or near the syringe receptacle of the syringe pump. If it is determined that the syringe is empty (560), the process 550 includes performing one or more operations (560-Y).

[0124] In some implementations, the operations (560-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp or the drive head, the syringe pump may prompt the user with unloading guidance. Additionally, if the user dismisses the unloading guidance, the syringe pump may return to displaying the home screen. Further, if the syringe pump detects that thesyringe was removed, the syringe pump may dismiss any loading or unloading guidance and / or return to displaying the home screen.

[0125] On the other hand, if it is determined that the syringe is not empty (560), the process includes performing one or more other operations (560-N). In some implementations, the operations (560-N) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp or the drive head, the syringe pump may prompt the user with unloading guidance. Additionally, the syringe pump may also initiate the siphon timer if it detects manipulation of the drive head. Upon expiration of the siphon timer, the syringe pump may trigger an alert indicating a siphon risk. Further, if the syringe pump detects that the syringe was removed, the syringe pump may dismiss any loading or unloading guidance, discard the selection of the syringe type, and / or return to displaying the home screen.

[0126] In some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (560-N) include discarding the syringe type selection if the control module detects that the syringe pump module was disconnected from the control module.

[0127] The process 550 continues in FIG. 5C. After performing the operations (560-N), the process 550 includes determining whether the syringe pump is priming the syringe (562). If it is determined that the syringe pump is priming the syringe 562), the process 550 includes performing one or more operations (562-Y).

[0128] In some implementations, the operations (562-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp or the drive head, the syringe pump may trigger an alarm indicating a syringe misload. Additionally, the syringe pump may also initiate the siphon timer if it detects manipulation of the drive head. Upon expiration of the siphon timer, the syringe pump may trigger an alarm indicating a siphon risk. Further, if the syringe pump detects that the syringe was removed, the syringe pump may dismiss any loading or unloading guidance, discard the selection of the syringe type, and / or return to displaying the home screen.

[0129] In some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (562-Y) include discarding the syringe type selection if the control module detects that the syringe pump module was disconnected from the control module.

[0130] Further, the process 550 includes determining whether the syringe pump is in an active infusion mode, an active titration mode, or triggering an alarm (564) responsive to determining that the syringe pump is not priming the syringe (562). If it is determined that the syringe pump is in the active infusion mode or the active titration mode, or triggering an alarm (564), the process 550 includes performing one or more operations (564-Y).

[0131] In some implementations, the operations (564-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp, the syringe pump may stop the infusion and / or trigger a high- priority alert or alarm. As another example, if the syringe pump detects manipulation of the drive head, the syringe pump may cancel the active infusion and / or discard the selection of the syringe type.

[0132] Additionally, if the syringe pump detects manipulation of the drive head, the syringe pump may increase the priority of the alarm and / or trigger a high-priority alarm. Further, the syringe pump may initiate the siphon timer if it detects manipulation of the drive head. Upon expiration of the siphon timer, the syringe pump may trigger a siphon alarm indicating a siphon risk. If the syringe pump receives a request to dismiss the siphon alarm, the syringe pump may return to displaying the home screen. Further, if the syringe pump detects that the syringe was removed, the syringe pump may trigger a high-priority alarm, cancel the active infusion, discard the selected syringe type, and / or return to displaying the home screen.

[0133] Moreover, in some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (564-Y) include discarding the syringe type selection, canceling the infusion, and / or triggering a disconnected-channel alarm if the control module detects that the syringe pump module was disconnected from the control module.

[0134] Returning to FIG. 5C, the process 550 also includes determining whether the syringe pump is in a pause, standby, or delay mode (566) responsive to determining that the syringe pump is not in an active infusion mode, an active titration mode, or triggering an alarm (564). If it is determined that the syringe pump is in a pause, standby, or delay mode (566), the process 550 includes performing one or more operations (566-Y).

[0135] In some implementations, the operations (566-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp, the syringe pump may remain in the pause, standby, or delaymode. However, if the syringe pump receives a resume request, the syringe pump may trigger a misload alarm. Additionally, if the syringe pump does not receive an input (e.g., a resume request) within a predetermined amount of time, the syringe pump may declare a callback (e.g., reminding the user that the syringe pump is in the pause, standby, or delay mode).

[0136] As another example, if the syringe pump detects manipulation of the drive head, the syringe pump may cancel the active infusion, discard the selection of the syringe type, return to displaying the home screen, and / or initiate the siphon timer. Upon expiration of the siphon timer, the syringe pump may trigger a siphon alarm indicating a siphon risk.

[0137] In some implementations, the operations (566-Y) include responding to removal of the syringe from the syringe pump. For example, if the syringe pump determines that the syringe was removed from the syringe pump, the syringe pump may trigger a high-priority alarm, cancel the infusion, discard the selection of the syringe type, and / or return to displaying the home screen.

[0138] Moreover, in some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (566-Y) include discarding the syringe type selection, canceling the infusion, and / or triggering a disconnected-channel alarm if the control module detects that the syringe pump module was disconnected from the control module.

[0139] Furthermore, the process 550 include determining whether the syringe pump is in an infusion complete mode, a stop mode for intermittent infusions, or an empty mode (568) responsive to determining that the syringe pump is not in a pause, standby, or delay mode (566). If it is determined that the syringe pump is in the infusion complete mode, the stop mode, or the empty mode (568), the process 550 includes performing one or more operations (568-Y).

[0140] In some implementations, the operations (568-Y) include responding to manipulation of the barrel clamp or the drive head. For example, if the syringe pump detects manipulation of the barrel clamp or the drive head, the syringe pump may prompt the user with unloading guidance. Additionally, if the user dismisses the unloading guidance, the syringe pump may return to displaying the home screen, discard the selection of the type of the syringe, and / or cancel the infusion. As another example, if the syringe pump detects manipulation of the drive head, the syringe pump may also initiate the siphon timer. Upon expiration of the siphon timer, the syringe pump may trigger a siphon alarm indicating a siphon risk.

[0141] In some implementations, the operations (568-Y) include responding to removal of the syringe from the syringe pump. For example, if the syringe pump determines that the syringe was removed from the syringe pump, the syringe pump may discard the selection of the syringe type, and / or return to displaying the home screen.

[0142] Moreover, in some implementations, the syringe pump is a syringe pump module connected to a control module (e.g., control module 104 of FIG. 1). Accordingly, in some implementations, the operations (568-Y) include clearing all alarms (e.g., an end-of-infusion alarm) associated with the syringe pump module if the control module detects that the syringe pump module was disconnected from the control module. In some implementations, the control module does not trigger the disconnected-channel alarm if the control module detects that the syringe pump module was disconnected from the control module while the following a determination that the syringe pump was in an infusion complete mode, a stop mode for intermittent infusions, or an empty mode (568).

[0143] If it is instead determined that the syringe pump is not in the infusion complete mode, the stop mode for intermittent infusions, or the empty mode (568), the syringe pump may perform operations including trigger an alarm and / or return to displaying the home screen.

[0144] FIGS. 6 A and 6B depict a table 600 including example states of a syringe pump and guidance corresponding thereto, according to various aspects of the subject technology. Many of the circumstances and responses thereto outlined in the table 600 are described in more detail above with respect to the processes 500 and 550 in FIGS. 5A through 5C.

[0145] The example states, as outlined in the first column of the table 600, correspond to various states of a syringe pump (e.g., syringe pump 132 of FIG. 1, syringe pump module 202 of FIG. 2, or syringe pump 300 of FIG. 3) or a device connected thereto (e.g., control module 104 of FIG. 1).

[0146] The second column of the table 600 enumerates various sensors (e.g., cradle sensor 246, barrel clamp sensor 248, drive head sensor 250, plunger retainer sensor 252, and / or barrel flange sensor 254 of FIG. 2) that may capture user input indicating the user is attempting to load or unload a syringe. Accordingly, the third column of the table 600 lists corresponding guidance that may be displayed based on the module state and / or sensor readings.

[0147] For example, if the barrel clamp sensor detects something (e.g., movement of the barrel clamp) while the channel is idle, the syringe pump or device connected thereto may display loading guidance as an informative alert (see first row in FIG. 6A). As another example,if the drive head sensor detects something (e.g., movement of the drive head) while the channel is active (e.g., infusing, programming, alarming, or “keep vein open” (KVO)), the syringe pump or device detected thereto may display an indication of misload and trigger a high- priority alarm or alert.

[0148] FIG. 7 is a conceptual diagram illustrating an example electronic system 700 for guiding physical interactions with a syringe pump, according to various aspects of the subject technology. Electronic system 700 may be implemented by a computing device for execution of software associated with portions or steps of processes 500 and 550, or components and methods provided by FIGS. 1-4. In this regard, electronic system 700 may include the infusion device 100 of FIG 1, the syringe pump module 202 of FIG. 2, and / or the syringe pump 300 of FIG. 3.

[0149] The electronic system 700 may also include a specifically-configured personal computer or a mobile device for infusion such as a smartphone, tablet computer, laptop, PDA, an augmented reality device, a wearable such as a watch or band or glasses, or 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.

[0150] 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, 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, electronic system 700 may include or be integrated with other computing devices or circuitry for operation of the various components and methods previously described.

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

[0152] From these various memory units, processing unit(s) 712 retrieves instructions to execute and data to process in order to execute the processes of the subject disclosure.Processing unit(s) 712 can be a single processor or a multi-core processor in different implementations.

[0153] ROM 710 stores static data and instructions that are needed by processing unit(s) 712 and other modules of the electronic system. 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 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 permanent storage device 702. Other implementations use a removable storage device (such as a floppy disk, flash drive, and its corresponding disk drive) as permanent storage device 702.

[0154] Like permanent storage device 702, system memory 704 is a read-and-write memory device. However, unlike storage device 702, system memory 704 is a volatile read- and-write memory, such as random-access memory (RAM). 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 system memory 704, permanent storage device 702, and / or ROM 710. From these various memory units, processing unit(s) 712 retrieves instructions to execute and data to process, in order to execute the processes of some implementations.

[0155] Bus 708 also connects to input device interface(s) 714 and output device interface(s) 706. Input device interface(s) 714 enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface(s) 714 include, for example, alphanumeric keyboards and pointing devices (also called “cursor control devices”). Output device interface(s) 706 enables, for example, the display of images generated by electronic system 700. Output devices used with 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.

[0156] Furthermore, bus 708 also couples electronic system 700 to a network (not shown) through network interface(s) 716. 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. 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 electronic system 700 can be used in conjunction with the subject disclosure when specifically configured with one of more of the features described.

[0157] FIG. 8 is a diagram illustrating a guidance prediction system 800 that implements various aspects of the subject technology. The guidance prediction system 800 may be implemented as a standalone device or be integrated into one or more of the devices described herein. The guidance prediction system 800 may include a guidance engine 810. The guidance engine 810 may be configured to receive inputs and provide predicted guidance based thereupon.

[0158] The guidance may include guidance on how to insert a syringe into the syringe pump, how to select a syringe after inserting a syringe, how to check a syringe that may be misloaded or inserted incorrectly, how to unload a syringe that is empty or no longer needed for an infusion, or the like. Moreover, the guidance may be provided directly or indirectly. Direct guidance may include specific configuration details to adjust the syringe pump to manifest human perceivable clinical assistance information. Indirect guidance may include encoded indicators that can be used by the syringe pump to acquire the configuration needed to provide the predicted assistance information.

[0159] The guidance engine 810 may be configured using information from a guidance configuration data store 820. The guidance configuration data store 820 may include one or more look up tables to correlate inputs to a predicted guidance. The guidance configuration data store 820 may include a trained machine learning model or other artificial intelligence model that accepts a set of inputs and generates a guidance prediction. The guidance engine 810 may use different configurations for guidance based on additional inputs such as the clinician identifier, clinician role, drug type to be infused, care area for the infusion pump, or other information provided to the guidance prediction system 800.

[0160] FIGS. 6 A and 6B provide an example of how the guidance engine 810 may be configured to process the inputs to generate a guidance prediction. Additionally, FIG. 4 and FIGS. 5A-5C provide example processes that may be implemented (in whole or in part) by the guidance engine 810 to generate guidance.

[0161] The inputs to the guidance engine 810 shown in the example of FIG. 8 may be received via respective data receivers including a receiver for syringe volume 802, a receiver for infusion state 804, a receiver for workflow state 806, and a receiver for sensor data 808.Depending on the clinical workflow, the prediction for a given point in time may not include values from all inputs. For example, if the syringe has not yet been loaded, the infusion state may be unknown or null since the pump has not yet been configured (e.g., programmed) for an infusion. Examples of infusion state shown in FIG. 8 include prime, flush, active, complete / keep vein open (KVO), or pause. Examples of workflow state include standby (e.g., idle), programming (e.g., in the process of programming the pump for infusing from an inserted container), infusing (e.g., driving the syringe to expel a fluid), or alarm (e.g., sounding an alarm). Examples of sensor data include data from one or more of the sensors described or associated with the syringe pump, such as the barrel clamp sensor, drive head sensor, syringe seating sensor, line pressure sensor, or the like.

[0162] The 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.

[0163] 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.

[0164] While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or moreintegrated 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.

[0165] 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.

[0166] 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).

[0167] 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 ofcommunication 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).

[0168] 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.

[0169] 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.

[0170] 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.

[0171] Illustration of Subject Technology as Clauses:

[0172] 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.

[0173] Clause 1. An infusion system, comprising: a syringe pump comprising a receptacle for receiving a syringe, the syringe comprising a barrel and a plunger; a display device; a plurality of sensors configured to generate sensor data associated with a physical interaction with the syringe pump; and a processor configured to: continuously monitor the sensor data generated by the plurality of sensors; detect, based on the monitored sensor data, the physical interaction with the syringe pump by an external user; and responsive to detecting the physical interaction: determine, based on the monitored sensor data, a loading condition of the syringe; when the loading condition indicates the syringe is not loaded in the receptacle, display guidance for loading the syringe on the display device; and when the loading condition indicates the syringe is loaded in the receptacle, (1) determine an infusion state of the syringe and (2) display guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

[0174] Clause 2. The infusion system of Clause 1, further comprising: a drive head; and a barrel clamp; wherein the plurality of sensors comprises a drive head sensor configured to sense when the drive head is secured to the plunger and a barrel clamp sensor configured to sense placement of the syringe within the barrel clamp; wherein the processor is further configured to: determine that the syringe is loaded in the receptacle when, based on the monitored sensor data, the drive head is secured to the plunger and the syringe is placed in the barrel clamp

[0175] Clause 3. The infusion system of Clause 2, wherein the processor is further configured to, when the loading condition indicates that the syringe is loaded in the receptacle: prompt, on the display device, selection of a user-selected syringe type; receive the user- selected syringe type in response to the prompt; determine, using at least one sensor of the plurality of sensors, a candidate syringe type; determine whether the user-selected syringe type corresponds to the candidate syringe type; and display guidance for unloading the syringe and loading a new syringe when the user-selected syringe type deviates from the candidate syringe type, and determine an infusion state of the syringe when the user-selected syringe type corresponds to the syringe type.

[0176] Clause 4. The infusion system of Clause 2 or 3, wherein the plurality of sensors further comprises a barrel flange sensor configured to detect a flange of the barrel and a drive head motion sensor configured to detect physical movement of the drive head, and detecting the physical interaction with the syringe pump comprises detecting a signal from two or more of the drive head sensor, barrel clamp sensor, barrel flange sensor, and drive head motion sensor.

[0177] Clause 5. The infusion system of Clause 4, further comprising: determining that the loading condition indicates a misloading of the syringe in the receptacle when one or more of the plurality of sensors indicate the syringe is loaded in the receptacle and one or more of the plurality of sensors indicate that the syringe is not loaded in the receptacle; and displaying, responsive to the loading condition indicating misloading of the syringe, an alert on the display device indicating that the syringe is misloaded.

[0178] Clause 6. The infusion system of any one of Clauses 2 through 5, wherein the processor is further configured to: determine that the syringe is associated with a siphon condition when, based on the monitored sensor data, the syringe is placed in the barrel clamp but the drive head is not secured to the plunger; initiate a siphon timer responsive to determining the syringe is associated with the siphon condition; and generate an alarm when the timer expires.

[0179] Clause 7. The infusion system of any one of Clauses 1 through 6, wherein detecting the physical interaction comprises detecting placement or movement of the syringe by at least one of the plurality of sensors.

[0180] Clause 8. The infusion system of any one of Clauses 1 through 7, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle and the infusion state indicates the syringe was not used in an infusion: determine whether a syringe type has been selected by the external user; responsive to determining that the external user has selected the syringe type, display guidance for unloading the syringe on the display device; and responsive to determining that the external user has not selected the syringe type: responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of a barrel clamp of the syringe pump, display guidance for unloading the syringe on the display device; and responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of a drive head of the syringe pump, display guidance for loading the syringe on the display device.

[0181] Clause 9. The infusion system of Clause 8, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle: determine that the syringe pump is in a standby, delay, or pause state; responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the barrel clamp while the syringe pump is in the standby, delay, or pause state, generate a misload alarm when the syringe pump receives a request to resume infusion;responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the drive head while the syringe pump is in the standby, delay, or pause state, cancel the infusion, discard a user-selected syringe type, and display a home screen on the display device; and responsive to determining, based on the monitored sensor data, that the physical interaction comprises removal of the syringe from the receptacle while the syringe pump is in the standby, delay, or pause state, generate a high-priority alarm, cancel the infusion, discard the user-selected syringe type, and display a home screen on the display device.

[0182] Clause 10. The infusion system of Clause 8 or 9, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle: determine that the syringe pump is in an infusion-complete state; responsive to determining, based on the monitored sensor data, that the physical interaction comprises removal of the syringe from the receptacle while the syringe pump is in the infusion-complete state, cancel the infusion, discard a user-selected syringe type, and display a home screen on the display device.

[0183] Clause 11. A computer-implemented method for guiding physical interactions with a syringe pump, comprising: continuously monitoring sensor data generated by a plurality of sensors configured to generate sensor data associated with a physical interaction with a syringe pump; detecting, based on the monitored sensor data, the physical interaction with the syringe pump by an external user; and responsive to detecting the physical interaction: determining, based on the monitored sensor data, a loading condition of a syringe; when the loading condition indicates the syringe is not loaded in a receptacle of the syringe pump, displaying guidance for loading the syringe on a display device; and when the loading condition indicates the syringe is loaded in the receptacle, (1) determining an infusion state of the syringe and (2) displaying guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

[0184] Clause 12. The computer-implemented method of Clause 11, wherein the syringe comprises a barrel and a plunger, the syringe pump comprises a drive head and a barrel clamp, the plurality of sensors comprises a drive head sensor configured to sense when the drive head is secured to the plunger and a barrel clamp sensor configured to sense placement of the syringe within the barrel clamp, and the method further comprises: determining that the syringe is loaded in the receptacle when, based on the monitored sensor data, the drive head is secured to the plunger and the syringe is placed in the barrel clamp.

[0185] Clause 13. The computer-implemented method of Clause 12, further comprising, when the loading condition indicates that the syringe is loaded in the receptacle: prompting, on the display device, selection of a user-selected syringe type; receiving the user-selected syringe type in response to the prompt; determining, using at least one sensor of the plurality of sensors, a candidate syringe type; determining whether the user-selected syringe type corresponds to the candidate syringe type; and displaying guidance for unloading the syringe and loading a new syringe when the user-selected syringe type deviates from the candidate syringe type, and determine an infusion state of the syringe when the user-selected syringe type corresponds to the candidate syringe type.

[0186] Clause 14. The computer-implemented method of Clause 12 or 13, further comprising: determining that the syringe is associated with a siphon condition when, based on the monitored sensor data, the syringe is placed in the barrel clamp but the drive head is not secured to the plunger; initiating a siphon timer responsive to determining the syringe is associated with the siphon condition; and generating an alarm when the siphon timer expires.

[0187] Clause 15. A non-transitory, machine-readable storage medium embodying instructions that, when executed by a machine, facilitate the machine to perform the method of any one of Clauses 11-14.

[0188] Further Consideration:

[0189] 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.

[0190] 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.

[0191] 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 sostated, 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.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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 theinformation. While recited in the singular, it will be understood that a message may be composed, transmitted, stored, received, etc. in multiple parts.

[0199] 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.

[0200] 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.

[0201] 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 syringe pump comprising a receptacle for receiving a syringe, the syringe comprising a barrel and a plunger; a display device; a plurality of sensors configured to generate sensor data associated with a physical interaction with the syringe pump; and a processor configured to: continuously monitor the sensor data generated by the plurality of sensors; detect, based on the monitored sensor data, the physical interaction with the syringe pump by an external user; and responsive to detecting the physical interaction: determine, based on the monitored sensor data, a loading condition of the syringe; when the loading condition indicates the syringe is not loaded in the receptacle, display guidance for loading the syringe on the display device; and when the loading condition indicates the syringe is loaded in the receptacle, (1) determine an infusion state of the syringe and (2) display guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

2. The infusion system of Claim 1, further comprising: a drive head; and a barrel clamp; wherein the plurality of sensors comprises a drive head sensor configured to sense when the drive head is secured to the plunger and a barrel clamp sensor configured to sense placement of the syringe within the barrel clamp; wherein the processor is further configured to: determine that the syringe is loaded in the receptacle when, based on the monitored sensor data, the drive head is secured to the plunger and the syringe is placed in the barrel clamp.

3. The infusion system of Claim 2, wherein the processor is further configured to, when the loading condition indicates that the syringe is loaded in the receptacle: prompt, on the display device, selection of a user-selected syringe type; receive the user-selected syringe type in response to the prompting; determine, using at least one sensor of the plurality of sensors, a candidate syringe type; determine whether the user-selected syringe type corresponds to the candidate syringe type; and display guidance for unloading the syringe and loading a new syringe when the user- selected syringe type deviates from the candidate syringe type, and determine an infusion state of the syringe when the user-selected syringe type corresponds to the candidate syringe type.

4. The infusion system of Claim 2, wherein the plurality of sensors further comprises a barrel flange sensor configured to detect a flange of the barrel and a drive head motion sensor configured to detect physical movement of the drive head, and detecting the physical interaction with the syringe pump comprises detecting a signal from two or more of the drive head sensor, the barrel clamp sensor, the barrel flange sensor, and the drive head motion sensor.

5. The infusion system of Claim 4, further comprising: determining that the loading condition indicates a misloading of the syringe in the receptacle when one or more of the plurality of sensors indicate the syringe is loaded in the receptacle and one or more of the plurality of sensors indicate that the syringe is not loaded in the receptacle; and displaying, responsive to the loading condition indicating misloading of the syringe, an alert on the display device indicating that the syringe is misloaded.

6. The infusion system of Claim 2, wherein the processor is further configured to: determine that the syringe is associated with a siphon condition when, based on the monitored sensor data, the syringe is placed in the barrel clamp but the drive head is not secured to the plunger; initiate a siphon timer responsive to determining the syringe is associated with the siphon condition; and generate an alarm when the siphon timer expires.

7. The infusion system of Claim 1, wherein detecting the physical interaction comprises detecting placement or movement of the syringe by at least one of the plurality of sensors.

8. The infusion system of Claim 1, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle and the infusion state indicates the syringe was not used in an infusion: determine whether a syringe type has been selected by the external user; responsive to determining that the external user has selected the syringe type, display guidance for unloading the syringe on the display device; and responsive to determining that the external user has not selected the syringe type: responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of a barrel clamp of the syringe pump, display guidance for unloading the syringe on the display device; and responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of a drive head of the syringe pump, display guidance for loading the syringe on the display device.

9. The infusion system of Claim 8, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle: determine that the syringe pump is in a standby, delay, or pause state; responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the barrel clamp while the syringe pump is in the standby, delay, or pause state, generate a misload alarm when the syringe pump receives a request to resume infusion; responsive to determining, based on the monitored sensor data, that the physical interaction comprises movement of the drive head while the syringe pump is in the standby, delay, or pause state, cancel the infusion, discard a user-selected syringe type, and display a home screen on the display device; and responsive to determining, based on the monitored sensor data, that the physical interaction comprises removal of the syringe from the receptacle while the syringe pump is in the standby, delay, or pause state, generate a high-priority alarm, cancel the infusion, discard the user-selected syringe type, and display a home screen on the display device.

10. The infusion system of Claim 8, wherein the processor is further configured to, when the loading condition indicates the syringe is loaded in the receptacle: determine that the syringe pump is in an infusion-complete state; responsive to determining, based on the monitored sensor data, that the physical interaction comprises removal of the syringe from the receptacle while the syringe pump is in the infusion-complete state, cancel the infusion, discard a user-selected syringe type, and display a home screen on the display device.

11. A computer-implemented method for guiding physical interactions with a syringe pump, comprising: continuously monitoring sensor data generated by a plurality of sensors configured to generate sensor data associated with a physical interaction with a syringe pump; detecting, based on the monitored sensor data, the physical interaction with the syringe pump by an external user; and responsive to detecting the physical interaction: determining, based on the monitored sensor data, a loading condition of a syringe; when the loading condition indicates the syringe is not loaded in a receptacle of the syringe pump, displaying guidance for loading the syringe on a display device; and when the loading condition indicates the syringe is loaded in the receptacle, (1) determining an infusion state of the syringe and (2) displaying guidance for unloading the syringe on the display device when the infusion state indicates the syringe was used in an infusion.

12. The computer-implemented method of Claim 11, wherein the syringe comprises a barrel and a plunger, the syringe pump comprises a drive head and a barrel clamp, the plurality of sensors comprises a drive head sensor configured to sense when the drive head is secured to the plunger and a barrel clamp sensor configured to sense placement of the syringe within the barrel clamp, and the method further comprises: determining that the syringe is loaded in the receptacle when, based on the monitored sensor data, the drive head is secured to the plunger and the syringe is placed in the barrel clamp.

13. The computer-implemented method of Claim 12, further comprising, when the loading condition indicates that the syringe is loaded in the receptacle: prompting, on the display device, selection of a user-selected syringe type; receiving the user-selected syringe type in response to the prompt; determining, using at least one sensor of the plurality of sensors, a candidate syringe type; determining whether the user-selected syringe type corresponds to the candidate syringe type; and displaying guidance for unloading the syringe and loading a new syringe when the user- selected syringe type deviates from the candidate syringe type, and determine an infusion state of the syringe when the user-selected syringe type corresponds to the candidate syringe type.

14. The computer-implemented method of Claim 12, further comprising: determining that the syringe is associated with a siphon condition when, based on the monitored sensor data, the syringe is placed in the barrel clamp but the drive head is not secured to the plunger; initiating a siphon timer responsive to determining the syringe is associated with the siphon condition; and generating an alarm when the siphon timer expires.

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

Images