Intelligent lock box for infusion device

Abstract

The infusion pump is secured within a lock box configured to close and prevent access to the infusion pump and a medicament container of the infusion pump, the lock box including a lock box control interface configured to obtain access authorization to the lock box from a pump communication interface of the infusion pump and to be enclosed within the lock box. And the lock box control interface is electrically connected with the pump communication interface. The wireless credentials are transmitted to the pump communication interface either by being received at the lock box control interface or by the lock box at the pump interface. The lock box control interface receives access authorization based on the wireless credentials from the pump communication interface and performs an action according to the received access authorization. The actions include unlocking the lock box or extending an interface of the pump to a lock box control interface of an authorized user.

Description

Technical Field

[0001] The present application relates generally to safety enclosures for infusion pumps. Background Art

[0002] A substance is a “controlled substance” when it has been determined to be susceptible to abuse, demonstrates a pattern of abuse leading to dependence, and its abuse has been shown to pose a risk to public health and safety. In many cases, controlled substances have legitimate medical uses and therefore may be purchased, stored, distributed, and administered to patients during the treatment of an injury or illness. Healthcare facilities may need to maintain stocks of controlled substances for these uses, which may attract individuals who wish to use them for other purposes, leading to abuse. These individuals may be employees of the healthcare facility itself. Therefore, any organization that routinely uses controlled substances for valid therapeutic purposes may be a target for diversion.

[0003] Furthermore, drug seeking behavior is highly adaptive, and diverters will continually challenge any control system, looking for ways to defeat it and obtain the drugs they seek. While diverters may include patients or visitors of patients, diverters may also include healthcare professionals. In fact, diversion of controlled substances by healthcare professionals can occur in any profession that has routine and appropriate access to these substances. The healthcare professionals with the most frequent access include physicians, nurses, pharmacists, and pharmacy technicians. Generally speaking, when healthcare professionals divert drugs, it is for personal use and is a symptom of addiction. Furthermore, drug diverters attempt to disguise their diversion as apparently legitimate use of controlled substances.

[0004] Current automated control systems have increased security for controlled substances, but diversion still occurs. While control systems limit the opportunity for diversion, they cannot completely prevent it. Medical cabinets are typically secured with locks and monitored. Lockboxes have been built and used to prevent access to infusion pumps that deliver controlled substances. Lockboxes are designed to completely enclose and prevent access to infusion sets and medication containers connected to infusion pumps. Lockboxes provide a good deterrent to diversion activities; however, the lockbox must be manually removed (usually using a physical key) before any adjustments can be made to the infusion pump, which is a time-consuming process that creates a significant barrier to critical care needs. Summary of the invention

[0005] The subject technology provides a method for securing a pump, comprising: securing at least a portion of an infusion pump in a lockbox, the lockbox being configured to enclose and prevent access to at least a user interface of the infusion pump and a drug container of the infusion pump, the lockbox comprising a lockbox control interface, the lockbox control interface being configured to obtain access authorization to the lockbox from a pump communication interface of the infusion pump and being enclosed in the lockbox; electrically coupling the lockbox control interface to the pump communication interface; facilitating transmission of wireless credentials to the pump communication interface for authorization of the lockbox; receiving, by the lockbox control interface, access authorization based on the wireless credentials from the pump communication interface; and performing, by the lockbox control interface, an action in accordance with the received access authorization. Other aspects include corresponding apparatus and computer program products for implementing the corresponding methods and features thereof.

[0006] According to various aspects, a system for securing a pump includes: a lockbox configured to enclose and prevent access to at least a user interface of an infusion pump and a drug container of the infusion pump; and a lockbox control interface associated with the lockbox, the lockbox control interface configured to obtain access authorization to the lockbox from a pump communication interface of the infusion pump and enclosed in the lockbox, the lockbox control interface including a processor configured to: electrically couple the lockbox control interface to the pump communication interface; facilitate transmission of wireless credentials to the pump communication interface for authorization of the lockbox; receive access authorization based on the wireless credentials from the pump communication interface; and perform actions based on the received access authorization. Other aspects include corresponding apparatus, methods, and computer program products for implementing corresponding systems and features thereof.

[0007] It should be understood that from the following detailed description, those skilled in the art will readily understand other configurations of the subject technology, wherein the various configurations of the subject technology are shown and described by way of illustration. As will be appreciated, the subject technology can have other and different configurations and its several details can be modified in various other aspects, all without departing from the scope of the subject technology. Therefore, the accompanying drawings and detailed description are considered to be illustrative rather than restrictive in nature. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] For a better understanding of the various embodiments described, reference should be made to the following description in conjunction with the following drawings. Throughout the drawings and description, the same reference numerals represent corresponding parts.

[0009] Figure 1A A first example of a patient care unit including a syringe pump mounted to a control unit in accordance with various aspects of the subject technology is depicted.

[0010] Figure 1B A second example of a patient care unit having connected functional modules in accordance with various aspects of the subject technology is depicted.

[0011] Figure 2A A perspective view of an exemplary lock box enclosing a patient care unit is depicted.

[0012] Figure 2B Describes various aspects of the subject technology Figure 2A Perspective view of a lock box unlocked and opened.

[0013] Figure 2C Depicted is a front view of a lock box in a closed and secure state in accordance with various aspects of the subject technology.

[0014] Figure 2D Depicted is a front view of a lock box in an open and unsecured state in accordance with various aspects of the subject technology.

[0015] Figure 2E Depicted is a side view of a lock box in a closed and secure state in accordance with various aspects of the subject technology.

[0016] Figure 2F Depicted is a side view of a lock box in an open and unsecured state in accordance with various aspects of the subject technology.

[0017] Figure 2G An exploded view of a lockbox 200 is depicted in accordance with various aspects of the subject technology.

[0018] Figure 3 Depicted are systems for securing an infusion device by authenticating a user to the infusion device via a smart lock box in accordance with various aspects of the subject technology.

[0019] Figure 4 Depicted is an exemplary process for securing an infusion device using a smart lock box in accordance with various aspects of the subject technology.

[0020] Figure 5 is a conceptual diagram illustrating an exemplary electronic system for securing an infusion device using a smart lock box in accordance with various aspects of the subject technology. DETAILED DESCRIPTION

[0021] Reference will now be made to embodiments, examples of which are illustrated in the accompanying drawings. In the following description, many specific details are set forth in order to provide an understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other examples, known methods, steps, component circuits, and networks are not described in detail to avoid confusing aspects of the embodiments.

[0022] The subject technology provides an intelligent system for securing an infusion device. As will be further described, the infusion device is secured within a lockbox, which is configured to enclose and prevent access to at least a user interface of an infusion pump and a drug container of the infusion pump. The lockbox includes a communication interface configured to receive a credential and transmit the credential to the infusion device within the lockbox to obtain authorization from the infusion device to access the lockbox.

[0023] According to various embodiments, the lock box includes retractable multiple folding doors, each folding door is configured to enclose a corresponding portion of an infusion pump. The opening of the lock box is controlled by a motor, and the lock box includes a top configured to open automatically, and opposite sides of the housing, the opposite sides of the housing are configured to slide automatically in a rearward direction to provide further access to the infusion pump. The top, sides, and folding doors are integrated with each other when closed to seal the lock box and prevent access to the infusion pump within the lock box.

[0024] The lockbox of the subject technology can be communicatively connected (e.g., using Bluetooth) to an infusion pump and / or a mobile device for receiving a signal to open the lockbox. No hard key is required, and a clinician can scan a badge to open the lockbox. Upon authentication, the mechanical components of the lockbox (e.g., door, top, sides) can open, with the door folding and the sides sliding back to reveal the pump.

[0025] Figure 1A A first exemplary patient care unit 10 according to various aspects of the subject technology is depicted, which includes an injection pump 30 mounted to a control unit 14. According to various embodiments, the control unit 14 can provide control and monitoring functions for the injection pump 30. In this regard, the control unit can include a display 4 and control keys 6, the display being used to visually convey various information, such as operating parameters and alarm indications and alarm messages of the connected pump, and the control keys being used to select and / or set control parameters and / or options for controlling connected modules (such as injection pumps 30). The control unit 14 can also include a speaker to provide an audible alarm. In some embodiments, the display 4 can be implemented as a touch screen display. In such embodiments, the control keys 6 can be omitted or reduced in number by providing corresponding interactive elements via a graphical user interface (presented via the display 4). In some embodiments, each control key 6 can select a corresponding option displayed in the display 4.

[0026] The syringe pump 30 may include a control panel 36 that provides a plurality of buttons 32 for controlling the pump 26 and a display 34 (see also FIG. 2 ) for presenting pump-specific information to the operator. The buttons 32 may allow the operator to program the pump 26 for flow rate, volume to be infused, and other pump parameters. The display 34 may present the programmed flow rate, the amount of fluid remaining to be infused, as well as alarms and other information.

[0027] The control unit 14 may include a communication system (not shown) by which the control unit 14 can communicate with external devices, such as a healthcare facility server or other computer, and with a portable processor, such as a handheld communicator or a notebook computer, or a clinician may have to transfer information and download a drug library to a control unit, such as a pump 30 or, for example, Figure 1B The communication module can be used to communicate with other information devices such as the control unit (such as the pump 30 or a barcode scanner) for clinicians to access and interact with the control unit or a device connected thereto. The communication system may include one or more radio frequency (RF) systems, optical systems such as infrared, BLUETOOTH TM system or other wired or wireless system. The barcode scanner and communication system can alternatively be integrated with the infusion pump 30, such as in the absence of a control unit, or in addition to the control unit 14. Thus, the information input device does not need to be hardwired to the medical device, and the information can also be transmitted via a wireless connection. In addition, other types of modules can be connected to the pump module or control unit, such as a syringe pump module, a patient-controlled analgesia module, an end-tidal CO2 monitoring module, an oximeter monitoring module, etc.

[0028] In some embodiments, pressure measurements from an upstream pressure sensor and / or a downstream pressure sensor are transmitted to a server or other coordination device, and the methods disclosed herein are implemented on the server or other coordination device. For example, a pressure sensor can be used to determine the pressure or force within an infusion line downstream of a pump (e.g., between a patient and a pump). More complex and computationally intensive methods, such as machine learning, can be implemented on a server (or on a control unit with greater memory and / or CPU resources). In some embodiments, machine learning is used to identify an emptying state based on a pressure signal received from a pump.

[0029] Figure 1B A second example of a patient care unit 10 with connected functional modules in accordance with various aspects of the subject technology is depicted. A patient care unit (or "PCU") may include various ancillary medical devices, such as an infusion pump, a vital signs monitor, a medication dispensing device (e.g., a medicine cabinet, a tote bag), a medication preparation device, an automated dispensing device, a module coupled to one of the above devices (e.g., a syringe pump module configured to attach to an infusion pump), or other similar devices.

[0030] In the depicted example, the patient care unit 12 includes a control module 14, also referred to as a main frame infusion controller 14, which is connected to one or more functional modules 16, 18, 20, 22. The main frame infusion controller 14 includes a central processing unit (CPU) 50 connected to a memory (e.g., a random access memory (RAM) 58), and one or more interface devices, such as a user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices. Although not required, the main frame infusion controller 14 also includes a main non-volatile storage unit 56, such as a hard drive or non-volatile flash memory, for storing software and data and one or more internal buses 64 for interconnecting the above elements. The patient care unit 12 may include or incorporate pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeters and other patient monitors), therapeutic devices, and other drug delivery devices that can be used in accordance with the teachings set forth herein.

[0031] In various embodiments, the user interface device 54 is a touch screen for displaying information to a user and allowing the user to input information by touching a defined area of ​​the screen. Additionally or alternatively, the user interface device 54 may include any device for displaying and inputting information, such as a monitor, a printer, a keyboard, soft keys, a mouse, a trackball, and / or a light pen. The data input device 60 may be a bar code reader capable of scanning and interpreting data printed in a bar code format. Additionally or alternatively, the data input device 60 may be any device for inputting encoded data into a computer, such as a device for reading a magnetic stripe, a wireless communication (e.g., radio frequency or Bluetooth), a radio frequency identification (RFID) device, so that the digital data encoded in the RFID tag or smart tag (defined below) is captured by the reader 60 via radio waves, a PCMCIA smart card, a radio frequency card, a memory stick, a CD, a DVD, or any other analog or digital storage medium. Other examples of the data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending on the type of interface device used, the user interface device 54 and the data input device 60 may be the same device. Although the data input device 60 is shown as being disposed within the main frame infusion controller 14, it should be appreciated that the data input device 60 may be integrated within the pharmacy system, or located externally and communicate with the pharmacy system via an RS-232 serial interface or any other appropriate communication means. The auxiliary interface 62 may be an RS-232 communication interface, however, any other device for communicating with a peripheral device (such as a printer, patient monitor, infusion pump, or other medical device) may be used without departing from the subject technology. In addition, the data input device 60 may be a separate functional module, such as modules 16, 18, 20, and 22 and configured to communicate with the main frame infusion (controller) device 14 or any other system on the network using appropriate programming and communication protocols.

[0032] The network connection 52 may be a wired or wireless connection, such as via Ethernet, WiFi, BLUETOOTH, an integrated services digital network (ISDN) connection, a digital subscriber line (DSL) modem, or a cable modem. Any direct or indirect network connection may be used, including but not limited to a telephone modem, a MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link, or a WLANS connection or other wireless connection.

[0033] Functional modules 16, 18, 20, 22 are any devices for providing care to a patient or for monitoring a patient's condition. At least one of functional modules 16, 18, 20, 22 may be an infusion pump module, such as an intravenous infusion pump for delivering medication or other fluids to a patient. For purposes of discussion, functional module 16 is an infusion pump module. Each of functional modules 16, 18, 20, 22 may be any patient treatment or monitoring device, including but not limited to an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG monitor, an EEG monitor, a heart rate monitor, an intracranial pressure monitor, and the like. Functional modules 16, 18, 20, and / or 22 may be a printer, a scanner, a barcode reader, a near field communication reader, an RFID reader, a radio frequency (RF) transmission, Bluetooth, or any other peripheral input, output, or input / output device.

[0034] Data to and from various data sources can be converted to data compatible with the network by existing techniques, and information movement between medical devices and the network can be achieved in various ways. For example, patient care units 12 and network 10 can communicate via automatic interaction, manual interaction, or a combination of automatic and manual interaction. Automatic interaction can be continuous or intermittent, and can be achieved through direct network connection 52 (such as Figure 1A The patient care unit 10 and the network may be manually connected to the network using, for example, a user interface device 54, a coded data input device 60, a bar code, a computer disk, a portable data assistant, a memory card, or any other medium for storing data to physically transfer data between the systems, either intermittently or periodically.

[0035] Figures 2A to 2G An exemplary smart lock box 200 for securing a patient care unit 10 is depicted in accordance with various aspects of the subject technology. Figure 2A A perspective view of an exemplary lockbox 200 enclosing a patient care unit is depicted. According to various embodiments, the lockbox 200 includes a housing that completely surrounds the patient care unit 10, including any attached modules 16, 18, 20, 22 and associated medications, and protects the unit and the modules from physical manipulation by individuals who do not have access to the lockbox. In the example shown, one module enclosed and secured by the lockbox 200 includes a syringe pump 30. In this example, the medication within the syringe pump is secured by being enclosed within the lockbox. In some embodiments, the lockbox can be extended to accommodate and secure medication bags for different types of pumps, such as peristaltic pumps.

[0036] The rear side of the housing of the lock box 200 (see Figure 2B , Figure 2E , Figure 2F ) is located between the patient care unit 10 and the pole 2 or other structure to which the patient care unit is mounted. As will be further described, the rear side of the lock box is configured to be formed around and secured to the mounting structure. The lock box includes at least one access door 202. In the depicted example, the lock box 200 includes a left bi-folding access door 202a and a right bi-folding access door 202b, which, as will be further described, open to the side to reveal the front of the patient control unit 10.

[0037] Figure 2B Describes various aspects of the subject technology Figure 2A 200. According to various embodiments, the housing of the lock box 200 includes an electrically controlled lock and a series of sliding doors that can be actuated by a corresponding series of motors and mechanical gears (not shown) to move the doors when the lock box 200 is opened. In the depicted example, the doors include retractable multi-folding doors 202 on both sides of the housing that form the front face of the lock box housing when closed, and a top face 204 (or lid) that closes to form the top of the lock box housing. When closed, the top face 204 is integrally coupled to the front face of the housing consisting of the doors 202a, 202b.

[0038] As shown, when the lock box 200 receives an authorization signal to trigger the opening of the lock box, the motor and gear operate to retract the multi-folding door in opposite left directions 206a, right directions 206b to expose the corresponding portion of the front of the patient care unit 10 in the housing. Each door is physically and hingedly connected to the corresponding left side wall 208a or right side wall 208b of the lock box housing. While the multi-folding door is retracted, the walls 208a, 208b move backward in direction 210 to expose at least a portion of the side of the patient care unit 10 and provide access to it. While the door and side are retracted, the top surface 204 can be swung open according to an arc 212 directed upward to expose at least a portion of the top of the patient care unit 10 and provide access to it. In some embodiments, the lock box can be opened without a motor. In such embodiments, the gears can be interconnected so that when the door and / or top of the lock box are manually opened (e.g., after the user is granted access), the door, top and / or side move together to open the lock box.

[0039] According to various embodiments, the lock box 200 includes a lock box control interface device 214 that is integral to the housing (e.g., embedded within the housing or securely attached to the housing). In the depicted example, the control interface device 214 is embedded in the door. The control interface device 214 can be electronically or communicatively coupled to various motors and gears within the lock box housing and is configured to operate the motors to control the opening and closing of the various doors, sides, and lids of the housing.

[0040] In some embodiments, the control interface 214 is configured to receive user credentials and / or other user input. In some embodiments, the control interface 214 may include a touch screen for receiving input. Additionally or alternatively, the control interface 214 may include a conventional keyboard. In some embodiments, the lock box control interface 214 includes a wireless communication module (e.g., a radio frequency identification (RFID)) scanner to receive credentials from a (e.g., RFID or Bluetooth) transmitting device. As will be further described, the control interface 214 can be communicatively connected to the control unit 14 or other processing device of the patient control unit 10 to authenticate / verify credentials received via the interface 214, or to receive a signal from the patient care device 10 to open the lock box 200. Once authorized credentials are received, the control interface 214 can automatically retract the door 202, lid 204, and / or sides 208 to provide access to the patient care device to the user. In some embodiments, upon receiving authorized credentials, the control interface 214 can provide (e.g., via a touch screen display) an expansion of the various displays 4 and inputs 6 of the patient care device 10 (see Figure 1A ).

[0041] Figure 2C Depicted is a front view of a lock box in a closed and secure state in accordance with various aspects of the subject technology. Figure 2D Depicted is a front view of a lock box in an open and unsecured state in accordance with various aspects of the subject technology. Figure 2E Depicted is a side view of a lock box in a closed and secure state in accordance with various aspects of the subject technology. Figure 2F A side view of a lockbox in an open and unsecured state according to various aspects of the subject technology is depicted. In the depicted example, the patient care device 10 is mounted to the pole 2 via a horizontal mount 4. It should be understood that other known mounting hardware may be used to secure the patient care device 10 to the pole 2 or other structure.

[0042] Figure 2GAn exploded view of a lockbox 200 according to various aspects of the subject technology is depicted. The back side 216 of the lockbox housing includes an elongated horizontal channel or slot 218 that is open on one end when the side 220a of the housing is removed. In this regard, the slot 218 can be positioned at the same height within the face 216 relative to the mounting member 4 on the patient care device 10 so that the slot 218 can be guided on the mounting member 4 to secure the lockbox to the patient care device 10. Thus, the lockbox can be secured by locking the back side 216 in place around the mounting member 4 between the patient care device 10 and the pole 2 (or other mounting surface). As shown, the only way to remove the lockbox from the patient care device 10 is to access the lockbox and disconnect and remove the side 220a from the back side 216.

[0043] Figure 3 A system for securing an infusion set by authenticating a user to the infusion set via a smart lockbox is depicted in accordance with various aspects of the subject technology. In the illustrated example, as previously described, the lockbox 200 securely encloses the patient care unit 10. The lockbox 200 includes a control interface 302 configured to receive user credentials. According to various embodiments, the control interface 302 includes wireless circuitry and a processor configured to pair with the communication interface 52 of the PCU 10, for example, before the lockbox is secured around the PCU 10. In some embodiments, the communication between the lockbox control interface 302 and the communication interface 52 of the PCU 10 can be in the form of a wired connection (within the lockbox).

[0044] According to various embodiments, the lock box is self-powered and includes a power source 304 within the lock box (e.g., inaccessible to individuals outside the lock box when the lock box is secured). In some embodiments, power for the lock box door and / or control interface 302 can be provided or supplemented by an infusion device (e.g., PCU 10). In such embodiments, the lock box power interface 304 can include a wired connection that is configured to connect and / or plug into a power charger 306 (e.g., a socket) provided by the infusion device 10 (e.g., on the main frame control unit 14). In some embodiments, the lock box 200 can be powered by PoE (Power over Ethernet). In some embodiments, the lock box power interface 304 can include wireless charging capabilities and can be positioned adjacent to a wireless power charger 306 that is attached to or integrated into the infusion device so as to receive charging and / or power from the infusion device when the lock box is secured to the infusion device. Figure 3 , the power source 304 is positioned on the bottom inside of the lock box 200, adjacent to the power charger 306. In some embodiments, the power source 304 can be positioned directly below the charger 306 for efficient wireless charging.

[0045] In some embodiments, the lock box control interface 302 includes an input device, such as a touch screen device. In this regard, the touch screen device can display a lock box user interface that prompts and / or receives credentials. For example, the touch screen can prompt for a username and password and then provide a virtual keyboard to enter the credentials. In some embodiments, the interface 302 can include a biometric scanner, such as a fingerprint reader. In some embodiments, the lock box control interface 302 includes a wireless scanner (e.g., an RFID or Bluetooth receiver) that is configured to wirelessly receive user credentials from a transmission device 308 associated with the user. For example, a user can scan his or her badge 308 at the interface 302 to provide the interface 302 with credentials stored in an RFID device within the badge.

[0046] Thus, the lockbox interface 302 facilitates sending authentication / authorization credentials to the infusion device to authorize the lockbox, for example, by wirelessly receiving the credentials from the transmission device 308 and resending them (or a representation thereof) to the control processor 50 within the infusion device 10. The processor 50 can then authenticate the user associated with the credentials, and after authentication, the processor can authorize the user to use the lockbox. The processor 50 can send a signal to the lockbox interface to indicate that the user is authorized to perform an action with respect to the lockbox. As will be further described, the action can include causing the lockbox to open (as shown in FIG. 2) or activating the lockbox user interface 302 to serve as an extension of the control unit 14 interface (e.g., the display 4 and / or the control keys 6).

[0047] Figure 4 An exemplary process 400 for securing an infusion device using a smart lockbox according to various aspects of the subject technology is depicted. For purposes of explanation, reference is made herein to FIG. Figure 3 The various block diagrams of the exemplary process 400 are described with reference to the related components and / or processes described herein. One or more block diagrams of the process 400 may be implemented, for example, by one or more computing devices, including, for example, one or more of the infusion control module 14, the PCU 10, or the modules 16, 18, 20, 22, and 30. In some embodiments, one or more block diagrams may be implemented based on one or more machine learning algorithms. In some embodiments, one or more block diagrams may be separated from other block diagrams and implemented by one or more different processors or devices. In addition, for the purpose of explanation, insofar as the block diagrams of the exemplary process 400 are described as occurring serially or linearly, in some embodiments, multiple block diagrams of the exemplary process 400 may occur in parallel. In addition, the block diagrams of the exemplary process 400 need not be executed in the order shown, and / or one or more block diagrams of the exemplary process 400 need not be executed.

[0048] In the depicted process 400, an infusion device (e.g., a pump) is secured within a lockbox (402). According to various embodiments, the lockbox is configured to enclose and prevent access to at least a control interface of the infusion pump and a medication container (e.g., an infusion bag) of the infusion pump. Figure 3 As described, the lockbox includes a lockbox control interface 302 configured to obtain authorization for access to the lockbox from the pump communication interface 52 of the infusion pump. In some embodiments, the lockbox control interface includes a scanner configured to wirelessly receive user credentials from a transmission device (e.g., an RFID or Bluetooth transmitter) associated with the user.

[0049] In some embodiments, securing the infusion set may include locking the lockbox door 202 and / or activating the control interface 302 to require authorized credentials to unlock the door.

[0050] The lockbox control interface 302 is electrically coupled to the pump communication interface 52 (404). In some embodiments, electrically coupling the lockbox control interface to the pump communication interface includes wirelessly pairing the lockbox control interface to the pump communication interface, for example using a Bluetooth connection. In some embodiments, the coupling includes a wired connection within the lockbox 200 (to prevent external tampering).

[0051] The lockbox 200 facilitates transmission of credentials to the infusion pump communication interface to obtain authorization for the lockbox. Thus, in some embodiments, the credentials are received by the lockbox control interface 302 and transmitted to the infusion pump communication interface 52 for user authorization of the lockbox (406). In some embodiments, the credentials can be entered via a lockbox user interface displayed or provided at the control interface 302. In some embodiments, at the control interface 302, the credentials are received from a badge scanned by an RFID scanner. In some embodiments, facilitating transmission through the lockbox includes scanning the RFID credentials by the pump communication interface 52 through the housing of the lockbox.

[0052] Process 400 continues with lockbox control interface 302 receiving user access authorization to access the lockbox from pump communication interface 52 ( 408 ). Thus, in response to transmitting the user credentials (and pump authorization credentials) to pump communication interface 52 , lockbox control interface 302 may receive access authorization from pump communication interface 52 .

[0053] The lockbox control interface 302 performs an action (410) based on the received access authorization. According to some embodiments, performing the action includes automatically (without further user intervention) unlocking the lockbox to allow the user to access the user interface of the drug container and the infusion pump. In some embodiments, performing the action includes activating the pump user interface to receive user input while the lockbox remains locked. For example, while the lockbox is opened, the display of the pump can be switched from an off state (e.g., powered off and / or unable to receive input) to an activated state (e.g., power and lights are on and ready to receive input). At this point, the lockbox user interface can extend (e.g., virtually) the user interface of the pump, such as the display 4 or the control keys 6. The authorized user can then provide input for controlling the pump via the lockbox user interface 302 while the lockbox remains locked. The lockbox control interface 302 receives the user input via the activated lockbox user interface and transmits the user input to the pump communication interface 52 (and the processor 50) to operate the infusion pump according to the access authorization (e.g., as if the input had been directly received by the pump user interface).

[0054] According to various aspects of the subject technology, Figure 4 The optional sub-process of actions performed in accordance with the authorized access is continued. According to various embodiments, as previously described, the lockbox includes a retractable multi-folding door and a series of motors and gears (not shown) to move and / or retract and / or lock or unlock the door.

[0055] According to the described example, in response to unlocking the lockbox, the lockbox control interface causes the lockbox to automatically open at least one access door to expose a user interface or a drug container (412). As previously described, the lockbox includes a housing that encloses the patient care unit and / or the infusion pump 10. When the lockbox is closed, the retractable multi-fold door is configured to form a front face of the housing. The multi-fold door may include a left bi-fold door 202a and a right bi-fold door 202b that open like folding closet doors, with each half of the bi-fold door folding over the other half when the doors are open. In this regard, the process continues with the lockbox automatically retracting the retractable multi-fold door (via a motor and / or gears) in response to unlocking the lockbox to expose a corresponding portion of the front face of the housing and a corresponding portion of an opposite side of the housing, thereby providing the user with close access to the infusion pump (414).

[0056] According to some embodiments, once the doors 202a, 202b are fully opened, when the lockbox is unlocked, the respective left and right sides of the lockbox 200 are configured to move in a direction 210 away from the front face of the housing. In this regard, the process of unlocking the lockbox further includes automatically moving the respective left and right sides in response to unlocking the lockbox to provide the user with access to at least a portion of the left and right sides of the infusion pump (416).

[0057] like Figure 2B and Figure 2D As shown, the lockbox 200 may further include a retractable top that is integral with the front face when closed. In this regard, the process of unlocking the lockbox also includes automatically opening the retractable top in response to unlocking the lockbox, thereby providing access to the infusion pump to the user (418). In some embodiments, the lockbox 200 communicates the opening and closing actions to the infusion pump and can receive information from the pump regarding the interaction with the pump by the user. In some embodiments, the lockbox 200 can automatically close after a predetermined period of time (e.g., after being opened for two minutes without interaction with the pump).

[0058] Many of the above-described exemplary processes 400 and related features and applications may also be implemented as software processes, which are specified as a set of instructions recorded on a computer-readable storage medium (also referred to as a computer-readable medium) and can be automatically executed (e.g., without user intervention). When these instructions are executed by one or more processing units (e.g., one or more processors, cores of processors, or other processing units), they cause the (multiple) processing units 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. Computer-readable media do not include carrier waves and electronic signals transmitted over wireless or wired connections.

[0059] The term "software" is meant to include, where appropriate, firmware residing in a read-only memory or an application stored in a magnetic storage device that can be read into the memory for processing by a processor. In addition, in some embodiments, multiple software aspects of the present disclosure may be implemented as sub-parts of a larger program while maintaining different software aspects of the present disclosure. In some embodiments, multiple software aspects may also be implemented as independent programs. Finally, any combination of independent programs that jointly implement the software aspects described herein are within the scope of the present disclosure. In some embodiments, when the software program is installed to operate on one or more electronic systems, the software program defines one or more specific machine implementations that implement and execute the operations of the software program.

[0060] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and may be deployed in any form, 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 may 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, or in multiple coordinated files (e.g., files that store one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network.

[0061] Figure 5 1-1 is a conceptual diagram illustrating an exemplary electronic system 500 for securing an infusion device using a smart lockbox according to various aspects of the subject technology. The electronic system 500 may be software or a computer program for executing one or more portions or steps associated with the process 400. Figure 4 The computing device of the provided components and methods includes but is not limited to computing hardware within the PCU 10, the main frame infusion controller 14, the control module 14, the functional modules 16, 18, 20, 22, 30 and / or any computing device or associated module or terminal disclosed herein. The electronic system 500 can be a personal computer or a mobile device (such as a smart phone, a tablet computer, a laptop computer, a PDA, an augmented reality device), a wearable device (such as a watch or a watchband or glasses or a combination thereof), or other touch screens or televisions in which one or more processors are embedded or connected, or any other type of computer-related electronic device with network connectivity.

[0062] The electronic system 500 may include various types of computer-readable media and various other types of interfaces for computer-readable media. In the depicted example, the electronic system 500 includes a bus 508, a processing unit 512, a system memory 504, a read-only memory (ROM) 510, a permanent storage device 502, an input device interface 514, an output device interface 506, and one or more network interfaces 516. In some embodiments, the electronic system 500 may include other computing devices or circuits integrated therewith for running the aforementioned various components and methods.

[0063] Bus 508 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of electronic system 500. For example, bus 508 communicatively connects processing unit 512 with ROM 510, system memory 504, and permanent storage 502.

[0064] Processing unit 512 retrieves instructions to be executed and data to be processed from these various memory units in order to perform the processes of the subject disclosure. In various implementations, the processing unit may be a single processor or a multi-core processor.

[0065] ROM 510 stores static data and instructions required by processing unit 512 and other modules of the electronic system. On the other hand, permanent storage device 502 is a read-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 500 is turned off. Some embodiments of the present disclosure use a large-capacity storage device (such as a magnetic disk or optical disk and its corresponding magnetic disk drive) as permanent storage device 502.

[0066] Other embodiments use removable storage devices (such as floppy disks, flash drives and their corresponding disk drives) as permanent storage devices 502. Similar to permanent storage devices 502, system memory 504 is a read-write memory device. However, unlike storage devices 502, system memory 504 is a volatile read-write memory, such as random access memory. System memory 504 stores some instructions and data required by the processor at runtime. In some embodiments, the processes disclosed in the subject matter are stored in system memory 504, permanent storage devices 502, and / or ROM 510. Processing unit 512 retrieves instructions to be executed and data to be processed from these different memory units in order to perform the processes of some embodiments.

[0067] The bus 508 is also connected to an input device interface 514 and an output device interface 506. The input device interface 514 enables a user to transmit information and select instructions to the electronic system. Input devices used with the input device interface 514 include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). For example, the output device interface 506 can display images generated by the electronic system 500. Output devices used with the output device interface 506 include (for example, printers and display devices) such as cathode ray tubes (CRTs) or liquid crystal displays (LCDs). Some embodiments include devices that are used as both input devices and output devices, such as touch screens.

[0068] In addition, if Figure 5As shown, bus 508 also couples electronic system 500 to a network (not shown) via network interface 516. Network interface 516 may include, for example, a wireless access point (e.g., Bluetooth or WiFi) or a radio communication circuit for connecting to a wireless access point. Network interface 516 may also include hardware (e.g., Ethernet hardware) for connecting a computer to a portion of a network of computers, such as a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN or intranet, or a network of networks, such as the Internet. Any or all of the components of electronic system 500 may be used in conjunction with the present disclosure.

[0069] The above functions can be implemented in computer software, firmware or hardware. These technologies can be implemented using one or more computer program products. Programmable processors and computers can be included in mobile devices or packaged as mobile devices. Processes and logic flows can be performed by one or more programmable processors and one or more programmable logic circuits. General and special computing devices and storage devices can be interconnected through a communication network.

[0070] Some embodiments include electronic components, such as microprocessors, storage devices, and memories that store computer program instructions in machine-readable media or computer-readable media (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, compact disk-read only (CD-ROM), compact disk-recordable (CD-R), compact disk-rewritable (CD-RW), read-only digital versatile disks (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card, mini SD card, micro SD card, etc.), magnetic and / or solid-state hard drives, read-only and recordable A computer readable medium is capable of storing a computer program that can be executed by at least one processing unit and includes a set of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as produced by a compiler, and files including high-level code that are executed by a computer, electronic component, or microprocessor using an interpreter.

[0071] Although the above discussion mainly involves microprocessors or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions stored in the circuit itself.

[0072] As used in this specification and any claims of this application, the terms "computer," "server," "processor," and "memory" refer to electronic or other technical devices. These terms do not include people or groups of people. For the purposes of this specification, the terms display or display refer to 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 limited to tangible physical objects that store information in a computer-readable form. These terms do not include any wireless signals, wired download signals, and any other transient signals.

[0073] To provide interaction with a user, embodiments of the subject matter described in this specification may 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 pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by responding to a request received from a web browser to send a web page to a web browser on a user's client device.

[0074] The embodiments of the subject matter described in this specification may be implemented in a computing system that includes a back-end component (e.g., as a data server), or includes a middleware component (e.g., an application server), or includes a front-end component (e.g., a client computer with a graphical user interface or a web browser through which a user can interact with the embodiments of the subject matter described in this specification), or any combination of one or more such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), intranets (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).

[0075] A computing system may include a client and a server. The client and the server are usually remote from each other and may interact via a communication network. The relationship between the client and the server is generated by computer programs running on the respective computers, and they have a client-server relationship with each other. In some embodiments, the server transmits data (e.g., an HTML page) to a client device (e.g., for the purpose of displaying data to a user interacting with the client device and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., the result of the user interaction) may be received from the client device at the server.

[0076] Those skilled in the art will appreciate that the various illustrative block diagrams, modules, elements, parts, methods and algorithms described herein can be implemented as electronic hardware, computer software or a combination of the two. In order to illustrate this interchangeability of hardware and software, various illustrative block diagrams, modules, elements, parts, methods and algorithms are generally described above with respect to their functionality. Whether such functions are implemented as hardware or software depends on the specific application and design restrictions of the entire system. For each specific application, the functions can be implemented in different ways. Various parts and block diagrams can be arranged differently (e.g., arranged in different orders, or divided in different ways), all of which do not depart from the scope of the subject technology.

[0077] It should be understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of steps in these processes can be rearranged based on design preferences. Some steps can be performed simultaneously. The attached method claims present the elements of the various steps in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0078] Description of this subject technology:

[0079] For convenience, multiple examples of various aspects of the present disclosure are described according to numbered clauses (1, 2, 3, etc.). These are provided only as examples and do not limit the subject technology. The reference numerals and the identification of the drawings are shown below only as examples and for the purpose of illustration, and the clauses are not limited by these identifications.

[0080] Item 1 A system for securing a pump, comprising: a lock box configured to enclose and prevent access to at least a user interface of an infusion pump and a drug container of the infusion pump; and a lock box control interface associated with the lock box, the lock box control interface configured to obtain access authorization to the lock box from a pump communication interface of the infusion pump and encapsulated within the lock box, the lock box control interface comprising a processor configured to: electrically connect the lock box control interface to the pump communication interface; facilitate transmission of wireless credentials to the pump communication interface for authorization of the lock box; receive access authorization based on the wireless credentials from the pump communication interface; and perform actions based on the received access authorization.

[0081] Item 2: A system according to Item 1, wherein the processor is further configured to: receive user credentials via the lock box control interface; and transmit the received user credentials to the pump communication interface via the lock box control interface, wherein, in response to transmitting the user credentials to the pump communication interface, the access authorization is received by the lock box control interface from the pump communication interface.

[0082] Clause 3. A system according to clause 2, wherein the lock box control interface includes a scanner, the scanner is configured to wirelessly receive the user credentials from a transmission device associated with the user, and the processor is further configured to: receive the user credentials from a badge scanned by the scanner.

[0083] Clause 4. The system of any of Clauses 1-3, wherein electrically coupling the lock box control interface with the pump communication interface comprises wirelessly pairing the lock box control interface with the pump communication interface.

[0084] Clause 5. The system of any of Clauses 1-4, wherein performing the action comprises unlocking the lockbox to allow a user to access the user interface and medication container.

[0085] Item 6 The system of Item 5, wherein the lock box includes at least one access door, and the action further includes: in response to unlocking the lock box, automatically opening the at least one access door to expose the user interface or drug container; and in response to opening the at least one access door, automatically switching the user interface of the infusion pump from a closed state to an activated state.

[0086] Item 7: A system according to Item 6, wherein the lock box includes a shell that encloses the infusion pump and includes retractable multi-fold doors located on both sides of the front side of the shell, and the multi-fold doors form the front side of the shell when closed, and the action also includes: in response to unlocking the lock box, automatically retracting the retractable multi-fold doors to expose at least a portion of the front side of the infusion pump.

[0087] Item 8 The system of Item 7, wherein the lock box further comprises a retractable top integrally connected to the front face when closed, and wherein the action further comprises: automatically opening the retractable top in response to unlocking the lock box, thereby providing the user with access to at least a portion of the top surface of the infusion pump.

[0088] Item 9: The system of Item 7, wherein the lock box further comprises corresponding left and right sides, the left and right sides being configured to move in a direction away from the front face of the housing when the lock box is unlocked, the action further comprising: in response to unlocking the lock box, automatically moving the corresponding left and right sides to provide the user with access to at least a portion of the left and right sides of the infusion pump.

[0089] Item 10: The system of any one of items 1-9, wherein the lock box control interface is configured to receive user input, wherein performing the action includes activating the lock box control interface to receive the user input, and wherein the processor is further configured to: receive the user input via the activated lock box control interface; and after access authorization, transmit the user input to the pump communication interface for operating the infusion pump in accordance with the access authorization.

[0090] Clause 11. A system according to any of clauses 1-10, wherein the pump communication interface includes a scanner and is configured to wirelessly receive the user credentials from a transmission device associated with the user via the scanner and transmit an access authorization based on the wireless credentials to the lock box control interface.

[0091] Item 12 A method for securing a pump, comprising: securing at least a portion of an infusion pump in a lock box, the lock box being configured to enclose and prevent access to at least a user interface of the infusion pump and a drug container of the infusion pump, the lock box comprising a lock box control interface, the lock box control interface being configured to obtain access authorization to the lock box from a pump communication interface of the infusion pump and being enclosed in the lock box; electrically coupling the lock box control interface to the pump communication interface; facilitating transmission of wireless credentials to the pump communication interface for authorization of the lock box; receiving, by the lock box control interface, access authorization based on the wireless credentials from the pump communication interface; and performing an action by the lock box control interface based on the received access authorization.

[0092] Item 13 The method described in Item 12 also includes: receiving user credentials via the lock box control interface; and transmitting the received user credentials by the lock box control interface to the pump communication interface, wherein in response to transmitting the user credentials to the pump communication interface, the access authorization is received by the lock box control interface from the pump communication interface.

[0093] Item 14 The method of item 12, wherein the pump communication interface includes a scanner configured to wirelessly receive the user credentials through the lock box from a transmission device associated with a user outside the lock box, wherein, in response to the user credentials being scanned at the pump communication interface, the access authorization is received from the pump communication interface by the lock box control interface.

[0094] Clause 15. The method of any of Clauses 12-14, wherein electrically coupling the lock box control interface with the pump communication interface comprises wirelessly pairing the lock box control interface with the pump communication interface.

[0095] Clause 16. The method of any of Clauses 12-15, wherein performing the action comprises unlocking the lockbox to allow a user to access the user interface and the medication container.

[0096] Item 17: The method of Item 16, wherein the lock box includes at least one access door, and the action further includes: in response to unlocking the lock box, automatically opening the at least one access door to expose the user interface or drug container; and in response to opening the at least one access door, automatically switching the user interface of the infusion pump from a closed state to an activated state.

[0097] Item 18 is a method according to Item 17, wherein the lock box includes a shell that encloses the infusion pump and includes retractable multi-fold doors located on both sides of the front side of the shell, and the multi-fold doors form the front side of the shell when closed, and the action also includes: in response to unlocking the lock box, automatically retracting the retractable multi-fold doors to expose at least a portion of the front side of the infusion pump.

[0098] Item 19 The method of Item 18, wherein the lock box further comprises a retractable top integrally connected to the front face when closed, and wherein the action further comprises: in response to unlocking the lock box, automatically opening the retractable top to provide the user with access to at least a portion of the top surface of the infusion pump.

[0099] Item 20 is a method according to Item 18, wherein the lock box also includes corresponding left and right sides, and the left and right sides are configured to move in a direction away from the front of the shell when the lock box is unlocked, and the action also includes: in response to unlocking the lock box, automatically moving the corresponding left and right sides to provide the user with access to at least a portion of the left and right sides of the infusion pump.

[0100] Item 21: The method of any one of items 12-20, wherein the lock box control interface is configured to receive user input, wherein performing the action includes activating the lock box control interface to receive the user input, and wherein the method further includes: receiving the user input via the activated lock box control interface; and after access authorization, transmitting the user input to the pump communication interface for operating the infusion pump according to the access authorization.

[0101] Further considerations:

[0102] It should be understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of steps in these processes can be rearranged based on design preferences. Some steps can be performed simultaneously. The attached method claims present the elements of the various steps in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0103] The previous description is provided to enable those skilled in the art to practice the various aspects described herein. The above description provides various examples of the subject technology, and the subject technology is not limited to these examples. Multiple modifications to these aspects are very clear to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein unless otherwise specified, references to singular elements are not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Positive pronouns (e.g., his) include negative and neutral genders (e.g., her and its), and vice versa. The use of titles and subtitles (if any) is for convenience only and does not limit the invention described herein.

[0104] The predicates "configured to," "operable to," and "programmed to" do not imply any specific tangible or intangible modification of the subject matter, but are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or component may also mean a processor programmed to monitor and control an operation or a processor operable to monitor and control an operation. Likewise, a processor configured to execute code may be interpreted as a processor programmed to execute code or operable to execute code.

[0105] The term "automatically" as used herein may include the performance of a computer or machine without user intervention; for example, by responding to action-based instructions of the computer or machine or other activation mechanism. The word "exemplary" as used herein means "serving as an example or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0106] Phrases such as "aspects" do not mean that such aspects are essential to the subject technology, or that such aspects apply to all configurations of the subject technology. The disclosure related to an aspect can be applied to all configurations or one or more configurations. An aspect can provide one or more examples. Phrases such as "an aspect" can refer to one or more aspects, and vice versa. Phrases such as "embodiments" do not mean that such embodiments are essential to the subject technology, or that such embodiments apply to all configurations of the subject technology. The disclosure related to an embodiment can be applied to all embodiments or one or more embodiments. An embodiment can provide one or more examples. Phrases such as "embodiments" can refer to one or more embodiments, and vice versa. Phrases such as "constructions" do not mean that such constructions are essential to the subject technology, or that such constructions apply to all configurations of the subject technology. The disclosure related to a construction can be applied to all configurations or one or more constructions. A construction can provide one or more examples. Phrases such as "constructions" can refer to one or more constructions, and vice versa.

[0107] 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 web-based interface that includes data fields and / or other control elements for receiving input signals or providing electronic information and / or for providing information to a user in response to any received input signals. Control elements may include dials, buttons, icons, selectable areas, or other perceptible indicia presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiate the exchange of data by the device presenting the UI. The UI may be presented in whole or in part using, for example, Hypertext Markup Language (HTML), FLASH, or the like. TM , JAVA TM , NET TM , C, C++, web services or rich site summary (RSS) and other technologies. In some embodiments, the UI can be included in a stand-alone client (e.g., thin client, thick client) configured to communicate (e.g., send or receive data) according to one or more aspects described. The communication can be to or from a medical device or server communicating with it.

[0108] As used herein, the term "determine" or "measure" encompasses a wide variety of actions. For example, "measure" may include calculating, computing, processing, deriving, generating, obtaining, searching (e.g., searching in a table, database, or another data structure), ascertaining, etc., via a hardware element without user intervention. In addition, "measure" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc., via a hardware element without user intervention. "Measure" may include parsing, selecting, choosing, establishing, etc., via a hardware element without user intervention.

[0109] As used herein, the term "providing" or "supplying" encompasses a wide variety of actions. For example, "supplying" may include storing a value in a location on a storage device for subsequent retrieval, sending a value directly to a recipient via at least one wired or wireless communication medium, sending or storing a reference to a value, etc. "Supplying" may also include encoding, decoding, encrypting, decrypting, validating, verifying, etc. via a hardware element.

[0110] As used herein, the term "message" includes a variety of formats for conveying (e.g., sending or receiving) information. A message may include a collection of machine-readable information, such as an XML document, a fixed field message, a comma-delimited message, JSON, a custom protocol, etc. In some embodiments, a message may include a signal for transmitting one or more representations of information. Although described in the singular, it should be understood that a message may be composed of multiple parts, transmitted, stored, received, etc.

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

[0112] As used herein, the term "corresponds" or "corresponding" encompasses a structural, functional, quantitative and / or qualitative association or relationship between two or more objects, data sets, information, etc., preferably, wherein the correspondence or relationship can be used to explain one or more of the two or more objects, data sets, information, etc., so as to appear the same or equal. The correspondence can be assessed using one or more of a threshold, a value range, fuzzy logic, pattern matching, a machine learning assessment model, or a combination thereof.

[0113] In any embodiment, the data generated or detected can be forwarded to a "remote" device or location, where "remote" refers to a location or device other than the location or device where the program is executed. For example, the remote location can be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Therefore, when an item is indicated as being "remote" from another item, it means that the two items can be in the same space but independent, or at least in different spaces or different buildings, and can be at least one mile, ten miles, or at least one hundred miles apart. "Communicating" information refers to transmitting data representing the information as an electrical signal through an appropriate communication channel (e.g., a dedicated or public network). "Forwarding" an item refers to any means of moving the item from one location to the next, whether by physically transmitting the item or otherwise (where possible), and at least in the case of data, including physically communicating the medium that carries the data or transmitting the data. Examples of communication media include radio or infrared transmission channels and network connections to another computer or networked device, as well as the Internet or information including email transmission and recorded on a website, etc.

Claims

1. A system for fixing a pump, comprising: a lockbox configured to enclose and prevent access to at least a user interface of the infusion pump and a medication container of the infusion pump; as well as a lockbox control interface associated with the lockbox, the lockbox control interface configured to obtain access authorization to the lockbox from a pump communication interface of the infusion pump and enclosed within the lockbox, the lockbox control interface comprising a processor configured to: electrically connecting the lock box control interface to the pump communication interface; facilitating transmission of wireless credentials to the pump communication interface for use in authorizing the lock box; receiving, from the pump communication interface, an access authorization based on the wireless credentials; as well as An action is performed based on the received access authorization.

2. The system according to claim 1, wherein: The processor is further configured to: receiving user credentials via the lock box control interface; and The received user credentials are transmitted to the pump communication interface via the lock-box control interface, wherein the access authorization is received by the lock-box control interface from the pump communication interface in response to transmitting the user credentials to the pump communication interface.

3. The system according to claim 2, wherein: The lock box control interface includes a scanner configured to wirelessly receive the user credentials from a transmission device associated with the user, and the processor is further configured to: The user credentials are received from a badge scanned by the scanner.

4. The system according to claim 1 or 2, wherein: Electrically coupling the lock box control interface to the pump communication interface comprises: Wirelessly pairing the lock-box control interface with the pump communication interface.

5. The system according to claim 1 or 2, wherein: Executing the actions includes: The lock box is unlocked to allow a user access to the user interface and medication container.

6. The system according to claim 5, wherein: The lockbox includes at least one entry door, the actions further comprising: in response to unlocking the lockbox, automatically opening the at least one access door to expose the user interface or medication container; and In response to opening the at least one access door, the user interface of the infusion pump is automatically switched from a closed state to an active state.

7. The system according to claim 6, wherein: The lockbox comprises a housing enclosing the infusion pump and comprising retractable multi-folding doors on both sides of a front face of the housing, the multi-folding doors forming the front face of the housing when closed, the actions further comprising: In response to unlocking of the lock box, the retractable multi-fold door is automatically retracted to expose at least a portion of the front face of the infusion pump.

8. The system according to claim 7, wherein: The lock box further includes a retractable top portion integrally coupled to the front face when closed, the actions further comprising: In response to unlocking of the lock box, the retractable top is automatically opened, thereby providing a user with access to at least a portion of a top surface of the infusion pump.

9. The system according to claim 7, wherein: The lock box further includes respective left and right sides configured to move in a direction away from the front face of the housing when the lock box is unlocked, the actions further comprising: In response to unlocking of the lockbox, the respective left and right sides are automatically moved to provide a user with access to at least a portion of the left and right sides of the infusion pump.

10. The system according to claim 1 or 2, wherein: The lock box control interface is configured to receive user input, wherein performing the action comprises activating the lock box control interface to receive the user input, and wherein the processor is further configured to: receiving the user input via an activated lock box control interface; and After access authorization, the user input is transmitted to the pump communication interface for use in operating the infusion pump in accordance with the access authorization.

11. The system according to claim 1 or 2, wherein: The pump communication interface includes a scanner and is configured to wirelessly receive the user credentials from a transmission device associated with a user via the scanner and transmit an access authorization based on the wireless credentials to the lock box control interface.

12. A method for fixing a pump, comprising: securing at least a portion of an infusion pump within a lockbox, the lockbox configured to enclose and prevent access to at least a user interface of the infusion pump and a medication container of the infusion pump, the lockbox comprising a lockbox control interface configured to obtain access authorization to the lockbox from a pump communication interface of the infusion pump and to be enclosed within the lockbox; electrically connecting the lock box control interface to the pump communication interface; facilitating transmission of wireless credentials to the pump communication interface for use in authorizing the lock box; receiving, by the lockbox control interface from the pump communication interface, an access authorization based on the wireless credentials; and An action is performed by the lock box control interface according to the received access authorization.

13. The method according to claim 12, further comprising: receiving user credentials via the lock box control interface; as well as The received user credentials are transmitted by the lock-box control interface to the pump communication interface, wherein the access authorization is received by the lock-box control interface from the pump communication interface in response to transmitting the user credentials to the pump communication interface.

14. The method according to claim 12, wherein: The pump communication interface includes a scanner configured to wirelessly receive the user credentials through the lock box from a transmission device associated with a user external to the lock box, wherein the access authorization is received from the pump communication interface by the lock box control interface in response to the user credentials being scanned at the pump communication interface.

15. The method according to claim 12 or 13, wherein: Electrically coupling the lock box control interface to the pump communication interface comprises: Wirelessly pairing the lock-box control interface with the pump communication interface.

16. The method according to claim 12 or 13, wherein: Executing the actions includes: The lock box is unlocked to allow a user access to the user interface and medication container.

17. The method according to claim 16, wherein: The lockbox includes at least one entry door, the actions further comprising: in response to unlocking the lockbox, automatically opening the at least one access door to expose the user interface or medication container; and In response to opening the at least one access door, the user interface of the infusion pump is automatically switched from a closed state to an active state.

18. The method according to claim 17, wherein: The lockbox comprises a housing enclosing the infusion pump and comprising retractable multi-folding doors on both sides of a front face of the housing, the retractable multi-folding doors forming the front face of the housing when closed, the actions further comprising: In response to unlocking of the lock box, the retractable multi-fold door is automatically retracted to expose at least a portion of the front face of the infusion pump.

19. The method according to claim 18, wherein: The lock box further includes a retractable top portion integrally coupled to the front face when closed, the actions further comprising: In response to unlocking of the lock box, the retractable top is automatically opened, thereby providing a user with access to at least a portion of a top surface of the infusion pump.

20. The method according to claim 18, wherein: The lock box further includes respective left and right sides configured to move in a direction away from the front face of the housing when the lock box is unlocked, the actions further comprising: In response to unlocking of the lockbox, the respective left and right sides are automatically moved to provide a user with access to at least a portion of the left and right sides of the infusion pump.

21. The method according to claim 12 or 13, wherein: The lock box control interface is configured to receive user input, Wherein performing the action comprises activating the lock box control interface to receive user input, and wherein the method further comprises: receiving the user input via an activated lock box control interface; and After access authorization, the user input is transmitted to the pump communication interface for use in operating the infusion pump in accordance with the access authorization.

Images