Infusion Management System

Abstract

The infusion pump system may include a portable infusion pump configured to be worn by a user and a detachable display. The portable infusion pump may include a fluid container configured to store a fluid to be delivered to the user, a pumping mechanism configured to effect delivery of the fluid from the fluid container to the user via a fluid delivery tube, and a communication circuit. The detachable display may transmit a fluid delivery protocol to the communication circuit of the portable infusion pump when the detachable display is coupled to the portable infusion pump. The detachable display may be detached from the portable infusion pump after transmission of the fluid delivery protocol to the portable infusion pump.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Provisional Application No. 63 / 159,929, entitled "Infusion Management System," filed March 11, 2021, which is incorporated by reference in its entirety.

[0002] FIELD OF THE DISCLOSURE The subject matter described herein relates generally to medication distribution, and more particularly, to infusion management systems for delivering medication to a patient. [Background technology]

[0003] Fluid pumps, such as infusion pumps, administer treatment to patients by delivering medication or other fluids to the patient. In some cases, certain types of therapies, such as chemotherapy, require a long period of time to deliver the medication to the patient. Fluid pumps may be large, which may make them difficult to store and / or use, as available space in a medical facility or patient care room may be limited and may require a caregiver to control the pump during the period of delivery of the treatment. Additionally or alternatively, certain types of treatments, such as insulin or chemotherapy delivery, may be delivered to patients at locations other than a medical facility, such as the patient's home, or while the patient is mobile. Also, certain clinical treatments may require the patient to go to a medical facility to administer the treatment for multiple days over an extended period of time. However, administering treatment to patients at locations other than a medical facility may be difficult due to the pump's lack of portability and inability to remotely control and / or program the pump. Providing relevant information about the pump or the administered treatment to the patient or caregiver may also be difficult. Summary of the Invention

[0004] Systems, methods, and articles of manufacture, including computer program products, are provided for an infusion management system for dispensing medication to a patient. For example, the system can provide an infusion pump system including a portable infusion pump that can be easily carried and / or worn by a user. The infusion pump system can include a portable infusion pump and a display separable from the portable infusion pump. The separable display can configure the portable infusion pump with a fluid delivery protocol. The portable infusion pump can additionally or alternatively be disposable.

[0005] According to some aspects, an infusion pump system includes a portable infusion pump and / or a detachable display. The portable infusion pump may be worn by a user. The portable infusion pump may include a fluid container configured to store a fluid to be delivered to the user, a pumping mechanism configured to effect delivery of the fluid from the fluid container to the user via a fluid delivery tube, and a communication circuit including an antenna. The detachable display may transmit a fluid delivery protocol to the communication circuit of the portable infusion pump when the detachable display is coupled to the portable infusion pump. The detachable display may be detached from the portable infusion pump after transmitting the fluid delivery protocol to the portable infusion pump. The fluid delivery protocol may define one or more parameters for delivering fluid to the user.

[0006] In some aspects, the portable infusion pump is disposable.

[0007] In some aspects, the communications circuitry includes at least one of a low energy communications circuitry, a near field communications circuitry, and a Bluetooth® low energy communications circuitry.

[0008] In some aspects, the detachable display includes an attachment sensor. The detachable display can transmit a fluid delivery protocol when a signal from the attachment sensor indicates that the detachable display is physically coupled to the portable infusion pump.

[0009] In some aspects, the physical coupling includes a magnetic coupling.

[0010] In some aspects, the detachable display includes a proximity sensor. The detachable display can transmit a fluid delivery protocol when a signal from the proximity sensor indicates that the detachable display is positioned within a predetermined distance from the portable infusion pump.

[0011] In some aspects, the infusion pump system includes a fluid delivery tube.

[0012] In some aspects, the portable infusion pump includes a waterproof housing, wherein at least the fluid container, the pumping mechanism, and the communication circuitry may be disposed within the waterproof housing.

[0013] In some aspects, the portable infusion pump includes an alarm system for generating an alarm upon detection of an error during delivery of fluid to a user. The alarm can include one or more of an audio, visual, and tactile alarm.

[0014] In some embodiments, the fluid container is configured to hold no more than 100 milliliters of fluid.

[0015] According to some aspects, the method includes receiving, by the portable infusion pump, at least one fluid delivery protocol from a display. The display may be temporarily coupled to the portable infusion pump. The method may also include delivering, by the portable infusion pump, fluid to a user based on the at least one fluid delivery protocol. The method may also include measuring, by the portable infusion pump, one or more fluid delivery parameters associated with the delivery of the fluid. The method may also include establishing, by the portable infusion pump, a wireless connection with the display. The method may also include transmitting, by the portable infusion pump, the one or more fluid delivery parameters to a display that is in wireless communication with the portable infusion pump.

[0016] In some aspects, the method also includes detecting an error in the delivery of fluid to the user and stopping the delivery of fluid to the user.

[0017] In some aspects, the method also includes transmitting the error to the display while the display is in wireless communication with the portable infusion pump, and displaying information related to the error via the display.

[0018] In some aspects, the portable infusion pump includes a fluid container configured to store a fluid to be delivered to a user, a pumping mechanism configured to effect delivery of the fluid from the fluid container to the user via a fluid delivery tube, and communication circuitry including an antenna.

[0019] In some aspects, the method also includes establishing, by the portable infusion pump, a wireless connection with the display when an attachment sensor of the display indicates that the portable infusion pump is physically coupled to the display. The method may also include disconnecting, by the portable infusion pump, a wireless connection with the display when the portable infusion pump is not physically coupled to the display.

[0020] In some aspects, the portable infusion pump is disposable.

[0021] In some aspects, the communications circuitry includes at least one of a low energy communications circuitry, a near field communications circuitry, and a Bluetooth low energy communications circuitry.

[0022] In some embodiments, the portable infusion pump further includes a fill port through which the fluid container is configured to be filled.

[0023] In some aspects, the fluid container is configured to hold multiple fluid bags.

[0024] In some aspects, the portable infusion pump includes a waterproof housing, with at least the fluid container, the pumping mechanism, and the communication circuitry disposed within the waterproof housing.

[0025] In some aspects, the method also includes the portable infusion pump further including an alarm system for generating an alarm upon detection of an error during delivery of fluid to a user. The alarm can include one or more of an audio, visual, and tactile alarm.

[0026] In some embodiments, the fluid container is configured to hold no more than 100 milliliters of fluid.

[0027] Implementations of the subject matter can include methods consistent with the descriptions provided herein, as well as articles comprising tangibly embodied machine-readable media operable to cause one or more machines (e.g., computers, etc.) to perform operations that implement one or more of the described features. Similarly, computer systems are described that can include one or more processors and one or more memories coupled to the one or more processors. The memory, which can include a non-transitory computer-readable medium or a machine-readable storage medium, can include, encode, store, etc., one or more programs that cause the one or more processors to perform one or more of the operations described herein.

[0028] A computer-implemented method consistent with one or more implementations of the present subject matter may be implemented by one or more data processors present in a single computing system or in multiple computing systems. Such multiple computing systems may be connected and may exchange data and / or commands or other instructions, etc., via one or more connections, including, for example, connections across a network (e.g., the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), such as via a direct connection between one or more of the multiple computing systems.

[0029] Details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will become apparent from the description and drawings, and from the claims. It should be readily understood that while certain features of the presently disclosed subject matter have been described in connection with an infusion management system for illustrative purposes, such features are not intended to be limiting. The claims following this disclosure are intended to define the scope of the protected subject matter. [Brief description of the drawings]

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate certain aspects of the subject matter disclosed herein and, together with the description, serve to explain some of the principles associated with the disclosed implementations.

[0031] [Figure 1] FIG. 1 shows a system diagram illustrating an infusion management system according to some exemplary embodiments. [Diagram 2] 1 illustrates a schematic diagram of an infusion pump system according to some exemplary embodiments. [Figure 3A] 1 illustrates an example of an infusion pump system including a portable infusion pump and a display according to some exemplary embodiments. [Figure 3B]1 illustrates an example of an infusion pump system including a portable infusion pump and a display according to some exemplary embodiments. [Figure 3C] 1 illustrates an example of a user device and an infusion pump system including a portable infusion pump and a display according to some exemplary embodiments. [Figure 4A] 1 illustrates an example of a portable infusion pump according to some illustrative embodiments. [Figure 4B] 1 illustrates an example of an infusion pump system including a portable infusion pump and a display according to some exemplary embodiments. [Figure 4C] 1 illustrates an example of an infusion pump system including a portable infusion pump and a user device according to some exemplary embodiments. [Figure 4D] 1 illustrates a schematic diagram of an example of a portable infusion pump according to some exemplary embodiments. [Diagram 5] 1 shows a flowchart illustrating a process for configuring a portable infusion pump according to some exemplary embodiments. [Figure 6] FIG. 1 shows a block diagram illustrating a computing system according to some exemplary embodiments. [Figure 7A] FIG. 1 illustrates a front view of a patient care system according to some exemplary embodiments. [Figure 7B] 1 illustrates an expanded view of a portion of a patient care system according to some exemplary embodiments. [Figure 7C] 1 illustrates a perspective view of a pump according to some illustrative embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0032] Wherever practical, like reference numerals refer to like structures, features or elements.

[0033] Fluid pumps, such as infusion pumps, administer therapy to patients by delivering medications or other fluids to the patient. The delivery of certain therapies, such as chemotherapy, may require a long period of time, requiring the patient to travel to a medical facility every day, and / or requiring a caregiver to be with the patient throughout the duration of the delivery of the therapy to the patient. Fluid pumps may be very large, occupy a large amount of space in a hospital and / or a patient room, and may be very cumbersome to use. For example, during cancer treatment, the administration of chemotherapy may be combined with one or more other therapies, such as hydration therapy. The infusion management systems described herein include one or more portable infusion pumps, which may be smaller than pumps (e.g., multi-channel pumps) typically used to deliver certain therapies, such as chemotherapy or other therapies that may combine multiple types of infusion therapy. For example, the infusion pump systems described herein may include a modular system that includes a separable portable infusion pump and a display. In some embodiments, the portable infusion pump may be disposable. By reducing the size of portable infusion pumps, more pumps can be stored within a medical facility and / or patient care room, making it easier to deliver therapies that involve the delivery of multiple types of fluids and improving the flexibility of these types of therapies.

[0034] By reducing the size of the pump, such as by providing a portable infusion pump as described herein, the pump can be placed adjacent and / or close to the infusion site of the patient's body. This reduces the risk of incorrect and / or displaced connections in the fluid delivery tubing connecting the portable infusion pump to the patient's body because the pump is placed closer to the infusion site. This may also reduce the impact of the fluid delivery line on the administration of fluid therapy to the patient. As a result, the portable infusion pump as described herein can improve the accuracy of measurements made based on the delivered therapy.

[0035] Additionally or alternatively, certain types of treatments, such as insulin or chemotherapy delivery, may be delivered to a patient at a location other than a medical facility, such as at the patient's home, or while the patient is mobile, or for an extended period of time at a medical facility, such as with the assistance of a caregiver. As previously mentioned, fluid pumps are generally very large, which may make the pump difficult to store and / or use. Thus, administering treatment to a patient at a location other than a medical facility may be difficult due to the pump's lack of portability and the inability to remotely control and / or program the pump. Providing the patient with relevant information regarding the pump or the administered treatment may be difficult. An infusion management system including a portable infusion pump as described herein may enable a patient to receive infusion therapy at home instead of at a medical facility, thereby resulting in a more comfortable life and improved experience of receiving infusion therapy. The portable infusion pumps as described herein may also be worn on the patient's body and / or easily carried by the patient, thereby enabling the patient to receive the administered treatment at various locations. The portable infusion pumps may also enable a patient to engage in normal activities, such as traveling, sleeping, and / or showering, without interrupting the delivery of treatment. In this manner, the portable infusion pumps described herein can provide the same functionality as pumps located in medical facilities, but allow the patient to live a normal lifestyle with minimal or no burden or ease of awareness of the portable infusion pump.

[0036] In some embodiments, the portable infusion pumps described herein may also be remotely controlled and / or programmed by an application on a mobile device or a standalone display, and / or may transmit useful data regarding the administered therapy to a display for display to the patient and / or transmission to a medical facility. Such a configuration may make it easier for a patient (or their caregiver) to administer fluid therapy using a portable infusion pump, may help reduce the size of the portable infusion pump by eliminating the need for a display on the pump carried by the patient, and may help improve the portability of the portable infusion pump. The portable infusion pumps described herein may also enable a caregiver to monitor the delivery of therapy to the patient. For example, if the portable infusion pump detects a problem that affects the delivery of therapy, such as an IV line blockage, the portable infusion pump may send an alert to the caregiver and / or the patient to correct the problem. This configuration may be useful in situations such as when access to a caregiver is limited.

[0037] Consistent with implementations of the present subject matter, a portable infusion pump may additionally or alternatively reduce costs because the pump may include a reduced set of components (e.g., a separable display and / or a disposable pump). Such a configuration may provide an integrated interface that is more patient-friendly. The integrated interface (e.g., via a separate display or user device) may be easier for the patient to use and / or read. The integrated interface may be used to enforce rules to prevent administration of incompatible fluids to the patient. Additionally or alternatively, the portable infusion pump may allow the patient to program or otherwise set up the portable infusion pump without or with minimal caregiver supervision.

[0038] 1 shows a system diagram illustrating an infusion management system 100 according to some example implementations. With reference to FIG. 1, the infusion management system 100 can include an infusion pump system 110, which includes a portable infusion pump 150 (also referred to herein as an “infusion device”) and a display 154, a user device 130, and a data system 125.

[0039] The user device 130 may be a mobile device, such as, for example, a smartphone, a tablet computer, a wearable device, and / or the like. However, it should be understood that the user device 130 may be any processor-based device, including, for example, a desktop computer, a laptop computer, a workstation, a network-connected television, and / or the like. For example, via the user device 130, the user 160 may view certain parameters of the pump 150, such as information about the user, the fluid therapy being infused, and / or alerts generated based on the pump 150. Information about the fluid therapy being delivered may include the time or time interval of fluid therapy delivery, the amount of fluid being delivered, the type of fluid being delivered, and / or the like. The user device 130 may additionally or alternatively be used by the clinician 165 (also referred to herein as a "caregiver") and / or the user 160 to configure certain parameters of the pump 150, such as the time or time interval of fluid therapy delivery, the amount of fluid being delivered, the type of fluid being delivered, and / or the like. Additionally, in some examples, via the user device 130, the clinician 165 can configure various fluid delivery protocols with default settings and safety parameters (e.g., setting limits on the volume of fluid delivered).

[0040] In some implementations, the user device 130 can directly program the pump 150 with a fluid delivery protocol, send data to the pump 150, and / or receive data from the pump 150. For example, the pump 150 can read and / or write from the display 154 and / or the data tag of the user device 130 when the pump 150 is positioned within a predetermined distance and / or away from the data tag for a predetermined time. The predetermined distance may be about 3 cm. In some embodiments, the predetermined distance is about 1-2 cm, 2-3 cm, 3-4 cm, and / or other ranges therebetween. In other embodiments, the pump 150 may be held in contact with the data tag, the display 154, and / or the user device 130. The predetermined time may be about 0.5 seconds to 1 second. In some embodiments, the predetermined time is about 0.5 seconds to 1.5 seconds, 1.0 seconds to 2.0 seconds, 2.0 seconds to 3.0 seconds, 3.0 seconds to 4.0 seconds, and / or the like. Restricting the display 154 and / or user device 130 from reading from and / or writing to the data tag when the pump 150 is located within a predetermined distance and / or for a predetermined period of time away from the data tag helps to improve security by reducing or eliminating the possibility of a security breach.

[0041] The data system 125 may include one or more databases that provide physical data storage in a dedicated facility and / or are stored locally on the pump 150 and / or display 154. The data system 125 may include inventory systems, patient care systems, management systems, electronic medical record systems, and / or the like that store a plurality of electronic medical records, each electronic medical record including a patient's medical history, one or more fluid delivery protocols, and / or the like. Additionally or alternatively, the data system 125 may include a cloud-based system that provides remote storage of data, for example, in a multi-tenant computing environment and / or the like. The data system 125 may also include non-transitory computer readable media.

[0042] In some embodiments, the data system 125 may include and / or be coupled to a server 126, which may be a network-coupled server, a cloud server, and / or the like. The user device 130 may wirelessly communicate with the server 126. The server 126 may communicate directly with the pump 150 or may communicate via the user device 130 and / or the display 154. The server 126, which may include a cloud-based server, may provide data and / or instructions from the data system 125 to the pump 150 and / or to the user device 130 or the display 154 for transmission to the pump 150 to implement one or more features of a fluid therapy protocol consistent with implementation of the present subject matter. Additionally or alternatively, the server 126 may receive data from the user device 130 and / or the display 154 (e.g., one or more parameters of a fluid therapy) transmitted from the pump 150 to the user device 130 and / or the display 154.

[0043] Application software ("app") executing on at least one of the user device 130 and / or display 154 may be configured to control operational aspects of the pump 150 and receive information regarding the operation of the pump 150. For example, the app may provide the user 160 with a limited set of functionality, such as viewing the status of the pump 150, one or more parameters of the fluid therapy being delivered by the pump 150, any errors in the administration of the fluid therapy, and / or the like. The app may display, via the user interface 148 (see FIGS. 2 and 3A), one or more parameters of the fluid therapy, such as the fluid delivery rate, the volume to be infused (VTBI) and / or the like, a battery status indicating the status of the power source 142 of the pump 150, the amount of fluid remaining in the fluid reservoir 144 of the pump 150 and / or the like. In some embodiments, the app may additionally or alternatively provide the clinician 165 with the ability to retrieve, via the app, one or more fluid delivery protocols from the server 126, establish a secure connection between the app, the display 154, and / or the pump 150, and transmit the fluid delivery protocols to the pump 150. The app may also provide the clinician 165 with the ability to select, for example, via the user interface 148, one or more sets of characteristics or parameters of a fluid delivery protocol to be sent to the pump 150. In other words, the user interface 148 may detect a user interaction that includes a selection of one or more sets of characteristics or parameters of a fluid delivery protocol to be sent to the pump 150. In some embodiments, the app may record various parameters of the fluid therapy delivered by the pump 150 and transmit the recorded parameters to the server 126, as described in more detail below.

[0044] Additionally or alternatively, an app on the user device 130 and / or display 154 can be operated by the clinician 165 to retrieve one or more fluid delivery protocols from the server 126. For example, the app and / or display 154 can detect a user interaction, such as a request to retrieve one or more fluid delivery protocols from the server 126 and / or a selection of one or more fluid delivery protocols. In some implementations, the app can include one or more authentication features to allow the clinician 165 access to the server 126 and prevent the user 160 from accessing certain features of the app (e.g., retrieving and / or modifying a fluid delivery protocol). For example, the app can prompt the clinician 165, via a user interface on the user device 130 and / or a user interface 148 on the display 154, to enter a username and password, scan a badge, perform a fingerprint scan or a retina scan, and / or use facial recognition to identify the clinician 165 and provide access via the app to retrieve and / or modify one or more aspects of a fluid delivery protocol.

[0045] The infusion pump system 110, including the display 154 and / or the pump 150, the user device 130, and / or the data system 125 may be communicatively coupled to each other via a network 105. The network 105 can be a wired and / or wireless network, including, for example, a public land mobile network (PLMN), a local area network (LAN), a virtual local area network (VLAN), a wide area network (WAN), the Internet, short-range wireless connections, such as Bluetooth, a peer-to-peer mesh network, and / or the like.

[0046] FIG. 2 illustrates a schematic of an infusion pump system 110 consistent with embodiments of the present subject matter. The infusion pump system 110 can include a portable infusion pump 150 and a display 154. The display 154 may be separable from the pump 150. For example, the display 154 can be communicatively and / or physically coupled to the pump 150 to program the pump 150 and / or send data to and / or receive data from the pump 150. In some implementations, the display 154 physically couples to the pump 150 via a magnetic connection, a snap-fit ​​arrangement, a friction-fit arrangement, mechanical fasteners, and / or the like. The display 154 and the pump 150 can have the same or similar size and / or shape. For example, the display 154 can have the same or similar circumference and / or shape as the circumference and / or shape of the pump 150. This allows the pump and display 154 to be easily held and / or coupled to one another during programming of the pump 150 and / or transmission of data to and / or from the pump 150 .

[0047] In some implementations, as described herein, the display 154 can program the pump 150 when the display 154 is communicatively and / or physically coupled to the pump 150. For example, the display can transmit information, such as a fluid delivery protocol, to the pump 150 when the display is communicatively and / or physically coupled to the pump 150. The display 154 may be separated and / or otherwise removed from the pump, such as after transmitting data to and / or from the pump 150. This reduces the weight of the pump system 110 and allows the pump 150 to be easily carried and / or worn by the patient, such as during delivery of therapy to the patient.

[0048] In some implementations, the display 154 includes sensors, such as attachment sensors, proximity sensors, and / or the like. The sensors can detect when the display 154 is within a predetermined distance from the pump 150. For example, in some implementations, the display 154 can transmit data to or from the pump 150 when a signal from an attachment sensor indicates that the display 154 is coupled (e.g., physically coupled) to the pump 150. Additionally or alternatively, the display 154 can transmit data to or from the pump 150 when a signal from a proximity sensor indicates that the display 154 is coupled (e.g., communicatively coupled) to the pump 150 and / or positioned within a predetermined distance from the pump 150.

[0049] The pump 150 may be a TCI pump, a syringe pump, an anesthesia delivery pump, a patient controlled analgesia (PCA) pump, a large volume pump (LVP), a small volume pump (SVP), and / or the like configured to deliver medication to a patient. However, it should be understood that the pump 150 may be any infusion device configured to deliver a substance (e.g., fluids, nutrients, medications, and / or the like) to a patient's circulatory system or epidural space via, for example, intravenous infusion, subcutaneous infusion, arterial infusion, epidural infusion, and / or the like. Alternatively, the pump 150 may be an infusion device configured to deliver a substance (e.g., fluids, nutrients, medications, and / or the like) to a patient's digestive system via a nasogastric tube (NG), a percutaneous endoscopic gastrostomy tube (PEG), a nasojejunal tube (NJ), and / or the like. Additionally, the pump 150 may be part of a patient care system that includes one or more additional pumps.

[0050] The pump 150 may have limited functionality and / or features available for use by a user 160. As previously mentioned, the display 154 may be separate from the pump 150 to allow the pump to be carried and / or worn by a patient during use. The pump 150 may include a user interface 137, a data storage device 131, a pumping mechanism 140, a fluid container 144, communication circuitry 134, an antenna 138, a controller 136 for controlling one or more operations of the pump 150, a power source 142, a safety system 146, and one or more indicators 135.

[0051] Because the display 154 is separable from the pump 150 and may not be coupled to the pump 150 when the pump 150 is carried and / or worn by a user, the pump 150 may include a limited user interface 137. The user interface 137 of the pump 150 may include one or more power buttons, one or more indicators, such as the indicator 135, and / or a pairing button (or other pairing feature) for pairing the pump 150 to the user device 130 and / or the display 154. The pump 150 may additionally or alternatively include audio indicators for providing alarms and / or warnings, a wireless system-on-chip (SOC) for motor and / or feedback control within the body of the pump 150, and a memory device for storing fluid delivery protocols. The pump 150 may thus be low-profile, thereby allowing the pump 150 to be carried and / or worn by a user and limiting the amount of space occupied by the pump 150, such as when the pump 150 is carried and / or worn by a user. Such a configuration may additionally or alternatively allow pump 150 to be placed closer to the infusion site on the patient's body to provide more accurate measurements, reduce the likelihood that the pump will become detached from the patient, improve the portability of the pump allowing patients to more comfortably use the pump away from medical facilities, and reduce manufacturing costs of pump 150.

[0052] For ease of wear, pump 150 may include a clip, clamp, strap, or other attachment fastener for coupling pump 150 to clothing or accessories worn by the patient (e.g., a purse, belt, bag, hat, bicycle, etc.) In some embodiments, pump 150 may include an adhesive element for semi-permanently attaching pump 150 to the patient or an item associated with the patient (e.g., a purse, bag, clothing, etc.).

[0053] In some embodiments, the pump 150 includes a data store 131 including one or more databases, data tables, and / or the like for storing (e.g., temporarily storing) a fluid delivery protocol, one or more fluid parameters, one or more patient parameters, and / or one or more clinician parameters. In some implementations, the controller 136 of the pump 150 can verify the fluid delivery protocol, one or more fluid parameters, one or more patient parameters, and / or one or more clinician parameters, such as a type of fluid to be delivered, a dosage of the fluid to be delivered, a delivery rate of the fluid to be delivered, a delivery rate of the fluid to be delivered, and / or the like. For example, the controller 136 can compare one or more stored fluid parameters to one or more of the patient parameters to determine whether the stored fluid parameters are the same as the stored patient parameters.

[0054] The pump 150 may include wireless communication circuitry 134 connected to and / or controlled by the controller 136. The wireless communication circuitry 134 may include one or more antennas 138 (which may include a near field communication (NFC) antenna, a Bluetooth antenna, a Bluetooth low energy antenna, a Wi-Fi antenna, and / or other antennas), a barcode reader, and / or a radio frequency identification (RFID) tag reader. The antenna 138 may be configured to read from and / or write to a data tag positioned on or otherwise coupled to the display 154 and / or the user device 130. The data tag may be a type of wireless transceiver and may include a microcontroller unit (MCU), memory, and an antenna (e.g., an NFC antenna) to perform various functions described herein. The data tag may be, for example, a 1 Kbit or 2 Kbit NFC tag. NFC tags of other specifications may also be used.

[0055] Additionally and / or alternatively, pump 150 may include communications circuitry 134 including one or more cellular communications capabilities, such as over network 105. The one or more cellular communications capabilities may include General Packet Radio Service (GPRS), Long Term Evolution (LTE) networks, 5G cellular technologies, etc. Such cellular communications capabilities may increase system mobility and deployment options.

[0056] The wireless communication circuitry 134 may include additional components / circuitry for other communication modes, such as, for example, NFC circuitry, Bluetooth circuitry, Bluetooth low energy circuitry, and / or Wi-Fi circuitry and associated circuitry (e.g., control circuitry) for communicating with other devices. For example, the pump 150 may be configured to wirelessly communicate with remote processors (e.g., display 154, user device 130, smartphone, tablet, wearable electronics, cloud servers, and / or the like) via the wireless communication circuitry 134 and may receive and / or transmit one or more fluid parameters, one or more patient parameters, one or more clinician parameters, one or more fluid delivery protocols, etc. from and / or to one or more of the remote processors.

[0057] Fluid reservoir 144 may store a fluid to be delivered to a user by pump 150. Fluid reservoir 144 may be filled, for example, by a pharmacist, clinician, etc., via fill port 176 (see FIGS. 3A-3C and 4A-4C). As described herein, fluid reservoir 144 may be refillable (e.g., via fill port 176) and / or may not be refillable such that fluid reservoir 144 along with other components of pump 150 are disposable for a single use or after a limited number of uses. In some embodiments, fluid reservoir 144 may store a relatively large amount of fluid, since pump 150 may be used to deliver fluid to a patient over an extended period of time, and pump 150 may be carried and / or worn by the patient throughout the duration of delivery of therapy to the patient. For example, the fluid container can have a maximum capacity of about 150 mL, 250 mL, 100-150 mL, 150-200 mL, 200-250 mL, 250-300 mL, 300-350 mL, or more. In some embodiments, the fluid container can store one or more fluid bags having a maximum capacity of about 150 mL, 250 mL, 100-150 mL, 150-200 mL, 200-250 mL, 250-300 mL, 300-350 mL, or more.

[0058] The pumping mechanism 140 can push fluid from the fluid container 144 for delivery to the patient through the fluid delivery tube. The pumping mechanism 140 can include a pump, a motor, and / or the like. In some implementations, the pumping mechanism 140 includes a peristaltic pump mechanism (e.g., linear or rotary), a piston type pump mechanism, and / or the like. The pumping mechanism 140 can enable efficient pumping of viscous medications and can improve the accuracy of fluid delivered to the patient under various temperature and pressure conditions. In some implementations, the pumping mechanism delivers therapy to the patient over an extended period of time. Thus, in some cases, the pumping mechanism 140 does not need to be highly accurate and / or may be inexpensive.

[0059] In some implementations, after pump 150 receives the desired fluid delivery protocol, pump 150 can be used to deliver fluid to a user based on the fluid delivery protocol. As described herein, pump 150 can be used to deliver fluid to a user at a location remote from a medical facility, such as at a medical facility and / or at the user's home and / or while the user is traveling.

[0060] The pump 150 can measure and / or record one or more parameters based on the fluid delivery protocol and / or delivery of fluid to the user. For example, the pump 150 can measure and / or record (e.g., store) one or more parameters, such as time of fluid delivery, information about the user, number of fluid deliveries, amount of fluid delivered, type of fluid being delivered, amount of fluid remaining to be delivered, location data, etc. The pump 150 can wirelessly transmit the measured and / or recorded parameters to the user device 130 and / or to the display 154 (e.g., an app). In some implementations, at least one of the measured and / or recorded parameters may be displayed to the user via the display 154 and / or the user device 130. In some implementations, at least one of the measured and / or recorded parameters may be transmitted from the user device 130 to a client device of the medical facility and / or directly to the server 126 and stored in one or more of the data systems 125 described herein. Such a configuration would allow the pump 150 to be used in a location remote from the medical facility and still update records associated with the delivery of fluid therapy to clinicians and / or users at the medical facility.

[0061] In some implementations, the pump 150 may include a safety system 146 including one or more safety mechanisms. The safety features may include one or more sensors 147, indicators 135, and an alarm system 133. For example, the one or more sensors 147 may include one or more pressure sensors, flow sensors, and / or optical sensors that measure one or more aspects of the delivery of fluid to the patient, such as the amount of fluid being delivered, the type of fluid being delivered, the amount of fluid remaining to be delivered, the air level in the fluid delivery tube, and / or the like. The one or more sensors may additionally or alternatively include a battery sensor that detects the charge level or remaining power capacity of the power source 142. In some implementations, the pump 150 detects an error, for example, via the one or more safety mechanisms and / or as a result of one or more parameters measured by the one or more safety mechanisms. The error may be related to the operation of the pump 150 and / or the delivery of fluid to the user.

[0062] For example, the pump 150 can detect a low battery, an obstruction in the fluid delivery line, a disconnection of the fluid delivery line from the user, a small amount of fluid remaining to be delivered, a malfunctioning component of the pump 150, a difference between stored fluid parameters and patient parameters, etc. In response to detecting an error, the pump 150 can activate the alarm system 133 and / or the indicators 135. The alarm system 133 can include visual, audio, and / or tactile indicators 135. For example, via the indicators 135, the alarm system 133 can display visual (e.g., light, colored light, red, orange, yellow, green, etc., patterned light, etc.), audio (e.g., sound, patterned sound, etc.), and / or tactile (e.g., vibration, patterned vibration, etc.) feedback via one or more of the indicators 135 on the pump 150. Additionally or alternatively, the pump 150 can transmit the error and / or details regarding the error to the display 154 and / or the user device 130. The display 154 and / or user device 130 can present details related to the error to the user. The details related to the error can include the type of error that occurred, instructions for correcting the error, and / or instructions for contacting a clinician. In some implementations, the display 154 and / or user device 130 can contact a clinician in response to receiving the error and / or details related to the error from the pump 150. For example, if the display 154 and / or user device 130 is implemented as a smartphone or smart display, the details related to the error can cause the smartphone or smart display to initiate a communication session (e.g., a chat, a call, a voice over IP call, a video call, etc.) with a device associated with the clinician.

[0063] In some implementations, in response to detecting an error, the pump 150 can stop delivering fluid to the user, for example, until the error is resolved (e.g., when the pump receives a command to continue delivering fluid). Additionally or alternatively, the display 154 and / or the user device 130 can cause the pump 150 to stop delivering fluid to the user in response to receiving an error and / or details related to the error from the pump 150. In some implementations, the display 154 and / or the user device 130 can cause the pump 150 to stop delivering fluid to the user based on the type of error received from the pump 150. For example, if the display 154 and / or the user device 130 determines that the fluid delivery line is disconnected from the user and / or that the fluid delivery line is blocked, the display 154 and / or the user device 130 can cause the pump 150 to deliver fluid to the user. This allows the pump 150 to be used away from a medical facility, improving the portability and usefulness of the pump 150 away from a medical facility.

[0064] 2, the display 154 may form part of the pump 150 and / or may be separately coupled to the pump 150. The display 154 may also include a user interface 148. The user interface 148 may form part of a display screen of the display 154 that presents information to a user 160 (e.g., a patient or their caregiver, e.g., a family member or home health aide), and / or the user interface may be separate from the display screen. For example, the user interface 148 may include one or more buttons or portions of a display screen configured to receive input from the user 160. In some implementations, the display 154 (and / or the user interface of the pump 150) described herein displays information such as the name of the fluid (e.g., medication) to be delivered and / or the amount of fluid to be delivered, among other parameters of a fluid delivery protocol.

[0065] In some implementations, the display 154 includes a communication circuit 149. The communication circuit 149 of the display 154 can communicate with the communication circuit 134 of the pump 150, the user device 130, the server 126, and / or another device in the medical facility. The communication circuit 149 can include an antenna, such as a Near Field Communication (NFC) antenna, a barcode reader, and / or a radio frequency identification (RFID) tag reader. The communication circuit 149 can additionally or alternatively include a data tag. The data tag can be a type of wireless transceiver and can include a microcontroller unit (MCU), memory, and an antenna (e.g., an NFC antenna) to perform various functions described herein. The data tag can be, for example, a 1 Kbit or 2 Kbit NFC tag. Other specifications of NFC tags can also be used. The data tag can provide information, such as a fluid delivery protocol, to the pump 150.

[0066] Additionally and / or alternatively, the communications circuitry 149 may include one or more cellular communications capabilities, such as via the network 105. The one or more cellular communications capabilities may include General Packet Radio Service (GPRS), Long Term Evolution (LTE) networks, 5G cellular technologies, etc. Such cellular communications capabilities may increase system mobility and deployment options. The communications circuitry 149 may include additional components / circuitry for other communication modes, such as Bluetooth, Bluetooth low energy, and / or Wi-Fi chips and associated circuitry (e.g., control circuitry) for communicating with other devices, such as the pump 150, the user device 130, the server 126, and / or other devices in the medical facility.

[0067] 3A-3C illustrate an example of an infusion pump system 110 consistent with implementations of the present subject matter. As shown in FIGS. 3A-3C and as described herein, the pump system 110 may be modular, including a portable infusion pump 150 and a display 154 that is separable from the pump 150. For example, FIG. 3A illustrates an example of an infusion pump system 110 in which the display 154 is coupled to the pump 150 via a magnetic connection, a snap-fit ​​arrangement, a friction-fit arrangement, a mechanical fastener, or the like. When the display 154 is coupled to the pump 150 and / or held within a predetermined distance of the pump 150, the display 154 can transmit and / or receive data including a fluid delivery protocol and / or one or more parameters related to the patient, delivery of therapy, or the like.

[0068] As shown in FIG. 3A, the pump 150 can be coupled to a fluid delivery tube 170 that can be coupled to a drug delivery device, such as a needle, via a connector 172 (e.g., a luer lock). The pump 150 can include one or more components, including a fluid container 144. For example, the fluid container 144 can hold a fluid to be delivered to a patient. In some embodiments, the fluid container holds one or more (e.g., 1, 2, 3, 4, or more) fluid bags (e.g., IV bags) that can have a volume of 250 mL or more, 100 mL or less, 100 to 200 mL, 200 to 300 mL, 300 to 400 mL, 400 to 500 mL or more. The fluid bags can be coupled to one end of the fluid delivery tube 170. In such a configuration, a clinician (e.g., a caregiver, a pharmacist, and / or the like) can connect a fluid bag to an end of the fluid delivery tube. Alternatively, the fluid container 144 can be configured to hold a fluid to be delivered to a user. In such a configuration, fluid can flow directly between the interior of the fluid container 144 and the fluid delivery tube 170 .

[0069] In some implementations, pump 150 includes a power source, such as power source 142. Power source 142 can have a capacity of up to or greater than 7 days, including 1-2 days, 2-3 days, 3-4 days, 4-5 days, 5-6 days, 6-7 days, 1-2 weeks, or more, before charging. Thus, pump 150 can be used for an extended period of time and / or multiple short periods of time as needed to deliver fluid to a patient, depending on the fluid delivery protocol. To allow for long run times before recharging power source 142, pump 150 can include low power consumption components, such as a low power consumption processor, a limited user interface, such as user interface 137 and / or an electronically linked display, and communication circuitry 134, including Bluetooth communication.

[0070] In some embodiments, the pump 150 includes a housing 174. The housing 174 can house internal components of the pump 150. For example, the housing 174 can house internal components such as the fluid container 144, the pumping mechanism 140, the communication circuitry 134, etc. In some embodiments, the housing 174 is waterproof, allowing for fluid protection up to IP66 or greater. This can allow a user to use the pump 150 in the shower, in the rain, or while traveling in wet and / or dusty conditions with no or minimal disruption.

[0071] In some implementations, the pump 150 includes an inductive coil and / or antenna, such as antenna 138. The inductive coil may enable NFC communication, for example, with the display 154, although other communication methods are contemplated, such as those described herein. The NFC functionality may enable pairing of the pump 150 and the display 154 and wirelessly transfer settings, such as one or more parameters and / or fluid delivery protocols, when the pump 150 and the display 154 are in contact with each other and / or the display 154 is placed within a distance of the pump 150. NFC also provides the ability to identify and communicate with a smartphone or tablet, such as the user device 130, to provide additional functionality that allows advanced programming and long-distance monitoring by a clinician. For example, FIG. 3C illustrates an example of an infusion pump system 110 in which the user device 130 is communicatively coupled to the display 154 and / or the pump 150. The coil may additionally or alternatively enable wireless charging of the power source 142 of the pump 150 (e.g., using Qi charging technology). Such a configuration can reduce or eliminate exterior facing connection points on the pump 150 that would otherwise be susceptible to fluid ingress.

[0072] As described herein, the pump 150 can include a pumping mechanism 140. The pumping mechanism 140 can propel fluid stored in the fluid reservoir 144 and / or in the fluid bag from within the fluid reservoir 144 to be delivered to a user. The pumping mechanism 140 can include a cassette-type interface with the pump 150, thus reducing the possibility of misloading. The cassette-type interface can include a peristaltic pump mechanism (e.g., a linear or rotary motor) for pumping the fluid to be delivered through the fluid delivery tube 170. Additionally or alternatively, the pumping mechanism 140 can include a piston-type mechanism that allows for efficient pumping of viscous fluids and improves the accuracy of the pumping mechanism 140 under various temperature and pressure conditions.

[0073] In some implementations, the power source 142 may be isolated from the pump 150 for maintenance, recharging, and / or replacement. This allows the pump to maintain a sufficient amount of power and manage battery life in an ambulatory setting. In some implementations, one or more sensors 147 may detect when the power remaining in the power source 142 is below a threshold amount (e.g., 5%, 10%, 15%, 20% capacity, etc.). Upon determining limited remaining power, the controller 136 may cause the safety system 146 to issue an alert, such as via the indicator 135, the display 154, and / or the user device 130. In some implementations, the alert includes instructions to recharge or replace the power source 142. Additionally or alternatively, upon detecting low remaining power, the controller 136 may operate the pump in a low power or battery saving mode such that the pump 150 has sufficient power to fully deliver therapy to the patient. Additionally or alternatively, prior to initiating delivery of fluid to the patient, the controller 136 may determine, based on the fluid delivery protocol transmitted from the display 154, that the power source 142 has an insufficient amount of power to begin delivery of fluid to the patient and / or has an insufficient amount of power to last for the duration of a treatment. In such an instance, the controller 136 may cause the safety system 146 to issue an alert. In some embodiments, the power source 142 is coupled to a replaceable cassette-type pumping mechanism 140, which helps ensure that the power source 142 is fully charged with each refill of fluid in the fluid container 144.

[0074] Thus, pump 150 can minimize performance feasible by delivering fluid to a user without coupling display 154 to pump 150. When display 154 is not physically coupled to pump 150, pump 150 can be reduced in size, allowing a user to carry it comfortably (e.g., by a strap or belt clip), and providing greater flexibility in performing normal daily activities. As an example, FIG. 3B illustrates pump 150 separated from display 154, consistent with implementation of the present subject matter.

[0075] 4A-4D show another example of an infusion pump system 110. The exemplary infusion pump system 110 shown in FIGS. 4A-4D can include the same or similar properties and / or features as the infusion pump system 110 shown in FIGS. 3A-3C. As described herein, the pump 150 may be separable from the display 154 (see FIG. 4B), and the display 154 and / or the user device 130 may communicate wirelessly with the pump 150 (see FIG. 4C). In the exemplary infusion pump system 110 shown in FIGS. 4A-4D, the pump 150 may be disposable and / or form a disposable unit. The disposable pump 150 may help reduce or eliminate misloading of the fluid delivery tube into the pumping mechanism 140 of the pump 150. For example, the fluid delivery tube 170 may be permanently coupled to the pump 150 or the pumping mechanism 140 such that the fluid delivery tube 170 is not separately coupled to the pump 150 during setup. This configuration helps reduce problems due to misloading of the fluid delivery tube, which may be more pronounced in an ambulatory environment.

[0076] Additionally or alternatively, a disposable pump 150 may reduce or eliminate maintenance, cleaning, calibration, testing, functional verification, etc. that may otherwise be time-consuming for a user of the pump 150. Such a configuration may also reduce or eliminate the incidence of transmission of septic infection between multiple users when a non-disposable pump is reused.

[0077] Additionally or alternatively, the disposable pump 150 can include low-cost materials. Although the low-cost materials may not be durable, the disposable pump 150 can be used for a limited time (single or limited number of doses). Thus, the pump 150 can be discarded before the materials of the pump 150 and its components begin to wear out. For example, the pump 150 can include one or more injection molded plastic components, including a low-cost motor with plastic gearing, to reduce manufacturing costs. It should be understood that other materials, such as recycled plastic materials, can be used to form one or more components of the pump 150.

[0078] In some implementations, the pumping mechanism 140 is attached directly to the drive motor, eliminating the need for an IV set interface. As shown in FIG. 4D, the electrical components of the pump 150 can use hard-wired connections, thereby eliminating the cost of connectors and their associated reliability. Because the pump 150 may be disposable and therefore requires no maintenance, the entire electrical system of the pump 150 can be encapsulated in a plastic material to ensure protection of the internal components from fluids and from impact damage due to handling of the pump 150. Additionally or alternatively, the pump user interface 137 can use a low energy material such as ePaper.

[0079] Additionally or alternatively, the disposable pump 150 may have its internal components enclosed and / or completely sealed, allowing the pump 150 to be used in non-sterile home or other ambulatory environments. As previously mentioned, this also helps to prevent or limit the ingress of unwanted fluids from entering the interior of the pump 150.

[0080] Additionally or alternatively, the disposable pump 150 may provide updated software to the user. For example, the pump 150 may include new and / or updated software and / or firmware on the pump 150 when the pump 150 is discarded and replaced. Such an arrangement saves time for the consumer and helps ensure that the pump 150 has the most up-to-date software and / or firmware.

[0081] In some embodiments, a disposable pump 150, such as the pump 150 shown in FIGS. 4A-4D, may be usable for a limited amount of time. For example, the pump 150 may be usable for approximately 30 days, 1-5 days, 5-10 days, 10-15 days, 15-20 days, 20-25 days, 25-30 days, 30-35 days, 35-40 days, or more. In some embodiments, the pump 150 may be usable for a length of time that does not cause the contained fluid to expire. After the usable period has elapsed, the pump 150 may be disposed of. In some embodiments, the pump 150 may be disposed of after a single use, after a single treatment, after a predetermined number of uses (e.g., 1, 2, 3, 4, or more uses), and / or after a predetermined number of treatments (e.g., 1, 2, 3, 4, or more treatments). Such a configuration reduces maintenance or cleaning time, as discussed above.

[0082] In some implementations, the fluid container 144 may be integrated into the pump 150. For example, the fluid container 144 may directly store the fluid to be delivered to the user. This allows the fluid container 144 to be directly coupled to the fluid delivery tube 170. Such a configuration also eliminates unnecessary equipment and reduces the possibility of infection, leakage, and / or leakage of fluid, such as dangerous drugs. In some implementations, the pump 150 includes a fill port 176 that allows the fluid container 144 to be filled, such as at a pharmacy. In some implementations where the pump 150 may only be refilled a limited number of times, the fluid container 144 may be refilled via the fill port 176. The fill port 176 may include a sealed joint and a check valve or other valve to prevent or reduce leakage from the interior of the fluid container 144. In some embodiments, the fluid container 144 can have a maximum capacity of about 150 mL, 250 mL, 100-150 mL, 150-200 mL, 200-250 mL, 250-300 mL, 300-350 mL, less, or more. Thus, the disposable pump 150 can reduce costs and improve the user experience while using the pump due to reduced time spent on maintenance, servicing, and cleaning of the pump 150.

[0083] 5 illustrates an example process 500 for configuring a portable infusion pump, such as pump 150, via a detachable display, such as display 154, consistent with implementations of the present subject matter. Consistent with implementations of the present subject matter, an infusion pump system including pump 150 and / or display 154 can reduce the amount of space pumps take up within a medical facility, allow the pump to be placed closer to the infusion site on the patient's body to provide more accurate measurements, reduce the likelihood that the pump will become detached from the patient, improve the portability of the pump to allow patients to more comfortably use the pump away from the medical facility, reduce manufacturing costs of the pump, etc.

[0084] In some implementations, as described herein, the display may be physically coupled (e.g., in contact) with the portable infusion pump and / or the display may be held within a predetermined distance from the portable infusion pump to establish a wireless connection with the pump. At 502, the portable infusion pump may receive at least one fluid delivery protocol from the display. For example, the portable infusion pump may receive the at least one fluid delivery protocol via NFC, Bluetooth, etc. The at least one fluid delivery protocol may include one or more parameters for delivering fluid to a user. For example, the one or more parameters may include a volume of fluid to be delivered to a user, a type of fluid to be delivered to a user, a time interval between fluid delivery, a frequency of fluid delivery, a delivery rate at which the fluid is to be delivered to a user, etc.

[0085] As discussed above with respect to at least FIGS. 1-4D, the display may be temporarily coupled to the portable infusion pump and may be detached from the portable infusion pump after transmission of a fluid delivery protocol from the display to the portable infusion pump. After the display is detached from the portable infusion pump, the portable infusion pump may include limited functionality. For example, the portable infusion pump may include indicators to provide visual, tactile, and / or audio feedback to the user based on one or more operations of the portable infusion pump. The indicators may display a light, change a color of a light, change a pattern of a light, flash a light, play a sound, play a sound pattern, play a vibration pattern, etc., when an error occurs in the delivery of fluid to the user. The error may indicate an occlusion in the fluid delivery line, the presence of air in the fluid delivery tube, an interruption in the connection between the fluid delivery line and the user, a low battery in the portable infusion pump, a small volume of fluid to be delivered to the user, and / or the like. Such a configuration may help the portable infusion pump maintain a low profile for improved portability and may allow the portable infusion pump to be carried and / or worn by a user.

[0086] At 504, fluid can be delivered to a user by the portable infusion pump based on at least one fluid delivery protocol. For example, the portable infusion pump can deliver fluid to a user based on a fluid delivery rate, a time interval, etc. stored as part of the fluid delivery protocol.

[0087] At 506, the portable infusion pump may measure and / or record one or more fluid delivery parameters associated with the delivery of fluid by the portable infusion pump. For example, the portable infusion pump may measure and / or record the time of fluid delivery, user information, number of fluid deliveries, amount of fluid delivered, type of fluid delivered, amount of fluid remaining to be delivered, location data, etc.

[0088] At 508, the portable infusion pump can establish and / or re-establish a wireless connection with the display. For example, the pump may be in contact with the display and / or within a predetermined distance of the display, as described herein.

[0089] At 510, the portable infusion pump can transmit the measured and / or recorded fluid delivery parameters associated with the delivery of fluid to a display for display to a user. In some embodiments, the display (e.g., via an app) displays at least one of the measured and / or recorded fluid delivery parameters to the user and / or transmits the measured and / or recorded fluid delivery parameters to a clinician. In some embodiments, the portable infusion pump can detect an error. In response to detecting an error, the portable infusion pump can provide visual, tactile, and / or audio feedback to the user via indicators on the portable infusion pump and / or display and / or transmit the error to the display. The display can then transmit the error and / or information related to the error to the clinician. In some embodiments, the portable infusion pump stops delivering fluid to the user in response to detecting an error.

[0090] 6 illustrates a block diagram of a computing system 600 consistent with implementations of the present subject matter. With reference to FIGS. 1 and 6, the computing system 600 may be used to implement the infusion pump system 110, including the portable infusion pump 150 and the display 154, the data system 125, the server 126, the user device 130, and / or any components therein.

[0091] As shown in FIG. 6, the computing system 600 may include a processor 610, a memory 620, a storage device 630, and an input / output device 640. The processor 610, the memory 620, the storage device 630, and the input / output device 640 may be interconnected via a system bus 650. The processor 610 may process instructions for execution within the computing system 600. Such executed instructions may implement, for example, the display 154 and / or one or more components of the portable infusion pump 150. In some exemplary embodiments, the processor 610 may be a single-threaded processor. Alternatively, the processor 610 may be a multi-threaded processor. The processor 610 may process instructions stored in the memory 620 and / or the storage device 630 to present graphical information for a user interface provided via the input / output device 640.

[0092] Memory 620 is a computer-readable medium, such as volatile or non-volatile, that stores information within computing system 600. Memory 620 may store, for example, data structures representing a configuration object database. Storage device 630 may provide persistent storage for computing system 600. Storage device 630 may be a floppy disk device, a hard disk device, an optical disk device, or a tape device, or other suitable persistent storage means. Input / output device 640 provides input / output operations to computing system 600. In some exemplary embodiments, input / output device 640 includes a keyboard and / or a pointing device. In various implementations, input / output device 640 includes a display unit for displaying a graphical user interface.

[0093] According to some demonstrative embodiments, I / O device(s) 640 may provide I / O operations to network devices. For example, I / O device(s) 640 may include Ethernet ports or other networking ports for communicating with one or more wired and / or wireless networks (e.g., a local area network (LAN), a wide area network (WAN), the Internet).

[0094] In some exemplary embodiments, computing system 600 can be used to execute various interactive computer software applications that can be used to organize, analyze, and / or store data in various formats. Alternatively, computing system 600 can be used to execute software applications. These applications can be used to perform various functions, such as planning functions (e.g., creating, managing, editing spreadsheet documents, word processing documents, and / or any other objects), computing functions, communication functions, and the like. Applications can include various add-in functions or can be stand-alone computing products and / or functions. When launched within an application, the functions can be used to generate a user interface that is provided via input / output devices 640. The user interface can be generated by computing system 600 and presented to a user (e.g., on a computer screen monitor, etc.).

[0095] In some exemplary embodiments, pump 22 (e.g., portable infusion pump 150) may be part of a patient care system 20. Although FIGS. 7A-7C show an exemplary embodiment of patient care system 20, other types of patient care systems may be implemented. With reference to FIG. 7A, patient care system 20 may include pump 22 as well as additional pumps 24, 26, and 28. Although a large volume pump (LVP) is shown, other types of pumps may be implemented, such as small volume pumps (SVP), TCI pumps, syringe pumps, anesthesia delivery pumps, and / or patient controlled analgesia (PCA) pumps configured to deliver medication to a patient according to one or more fluid delivery protocols. In some implementations, portable infusion pump 150 as described herein may be communicatively coupled to and / or form part of some of pumps 22, 24, 26, 28. Pump 22 may be any infusion device configured to deliver a substance (e.g., fluids, nutrients, medications, etc.) to a patient's circulatory system or epidural space via, for example, intravenous infusion, subcutaneous infusion, arterial infusion, epidural infusion, etc., or pump 22 may be an infusion device configured to deliver a substance (e.g., fluids, nutrients, medications, etc.) to a patient's digestive system via a nasogastric tube (NG), a percutaneous endoscopic gastrostomy tube (PEG), a nasojejunal tube (NJ), etc.

[0096] 7A, each of pumps 22, 24, 26, and 28 may be fluidly connected to upstream fluid lines 30, 32, 34, and 36, respectively. Additionally, each of the four pumps 22, 24, 26, and 28 may also be fluidly connected to downstream fluid lines 31, 33, 35, and 37, respectively. The fluid lines may be any type of fluid conduit, such as tubing, through which a fluid may flow. At least a portion of one or more of the fluid lines may be configured in a multi-layer configuration as described herein.

[0097] The fluid supplies 38, 40, 42, and 44 can take a variety of forms, but in this case are shown as bottles, inverted and suspended above the pumps. The fluid supplies can also take the form of bags, syringes, or other types of containers. Both the patient care system 20 and the fluid supplies 38, 40, 42, and 44 may be mounted on a roller stand or intravenous (IV) pole 46.

[0098] Separate pumps 22, 24, 26, and 28 may be used to infuse each fluid in the fluid supplies into the patient. Pumps 22, 24, 26, and 28 may be flow control devices that act on the respective fluid lines to move fluid from the fluid sources through the fluid lines to the patient 48. Because individual pumps are used, the pumping or operating parameters required to infuse a particular medical fluid from each fluid source into the patient at a particular rate prescribed by a physician for that fluid can be individually set. Such medical fluids may include drugs or nutrients or other fluids.

[0099] Typically, a medical administration set will have many more parts than are shown in FIG. 7A. Many will have check valves, drip chambers, valved ports, connectors, and other devices known to those skilled in the art. These other devices are not included in the drawing to maintain clarity of illustration. Additionally, it should be noted that the drawing in FIG. 7A is not to scale and distances have been compressed for clarity. In an actual setup, the distances between the bottles 38, 40, 42, and 44 and the pump modules 22, 24, 26, and 28 may be much greater.

[0100] 7B, an enlarged view of the front of the patient care system 20 is shown. The pump 22 can include a front door 50 and a handle 52 that are operable to lock the door in a closed position for operation, to unlock and open the door to access the internal pumping and sensing mechanisms, and to load an administration set for the pump. When the door is open, tubing can be connected to the pump, as shown in FIG. 7C. When the door is closed, the tubing is in operative engagement with the pumping mechanism, the upstream and downstream pressure sensors, and other equipment of the pump. A display 54, such as an LED display, is disposed in plan view on the door in this embodiment and can be used to visually communicate various information related to the pump, such as alarm indications (e.g., alarm messages), such as via the safety system 146. The display 54 may otherwise be part of or coupled to the pump 22. There are control keys 56 for programming and controlling the operation of the pump as desired. The pump 22 also includes an audio alarm device in the form of a speaker (not shown).

[0101] In the illustrated embodiment, the programming module 60 is mounted to the left side of the pump 22. In some embodiments, the programming module 60 forms part of the pump 22. Other devices or modules, including another pump, may be mounted to the right side of the pump 22, as shown in FIG. 7A. In such a system, each attached pump represents a pump channel in the overall patient care system 20. In one embodiment, the programming module is used to provide an interface between the pump 22 and external devices as well as provide the majority of the operator interface for the pump 22.

[0102] The programming module 60 includes a display 62 for visually communicating various information, such as operating parameters of the pump 22 and alarm indications and messages. In some implementations, the display 62 forms part of or is in communication with the portable infusion pump 150, the display 154, and / or the user device 130. The programming module 60 can additionally or alternatively display one or more patient parameters and corresponding values ​​for each of the one or more patient parameters described herein on the display 54 and / or the display 64. The programming module 60 can also include a speaker for providing audible alarms. The programming module or any other module also has various input devices, including, in this embodiment, control keys 64 and a bar code or other scanner or reader for scanning information from electronic data tags relating to the infusion, the patient, the caregiver, and the like. The programming module also has a communications system (not shown) that can communicate with external devices such as a medical facility server or other computers, as well as with a portable processor such as a handheld personal digital assistant (PDA) or laptop computer, or other information device to which a caregiver may need to transfer information and download drug libraries to the programming module or pump. In some embodiments, the pump 22 can communicate with a server (e.g., server 126) and / or one or more portable infusion pumps 150 to transmit one or more fluid delivery protocols to the one or more portable infusion pumps 150.

[0103] In some implementations, the programming module 60 may be configured as a display for the portable infusion pump 150. The programming module 60 may be paired with the portable infusion pump 150 using a proprietary or standards-based device pairing protocol, such as Bluetooth or WiFi connection protocols. Once paired, information received by the programming module 60 may be transmitted to the portable infusion pump 150. Conversely, an alert or warning generated by the portable infusion pump 150 may be transmitted to the programming module 60, which may present a human-perceptible manifestation of the alert or warning using one or more output devices included in the programming module. Output devices for presenting the manifestation may include, for example, audio output devices, lighting devices (e.g., LEDs), displays (e.g., graphical user interfaces), and the like.

[0104] The communication system can take the form of a radio frequency ("RF") system, an optical system such as infrared, a Bluetooth system, or other wired or wireless system. Alternatively, the barcode scanner and communication system may be included integrally with the pump 22, such as when a programming module is not used, or in conjunction with a programming module. Also, the information input device need not be wired to the medical equipment, as information may be communicated via a wireless connection.

[0105] FIGURE 7B includes a second pump 26 connected to the programming module 60. More pump modules may be connected as shown in FIGURE 7A. Additionally, other types of modules may be connected to the pump modules or programming module. In such an embodiment, the programming module may maintain the determined, adjusted, and / or displayed values ​​(e.g., default values) of one or more patient parameters for each pump (e.g., pump 22 and pump 26).

[0106] 7C, the pump 22 is shown in a perspective view with the front door 50 open, showing the upstream and downstream fluid lines 30 and 31 in operative engagement with the pump 22. The pump 22 acts directly on tubing 66 (also referred to as a pump segment) that connects the upstream and downstream fluid lines 30 and 31 to form a continuous fluid conduit extending from the respective fluid supplies 38 (FIG. 7A) to the patient 48, through which fluid is acted upon by the pump to move the fluid downstream of the patient. Specifically, the pumping mechanism 70 functions as a pump flow control device for moving fluid through the conduit. The upstream and downstream fluid lines and / or tubing 66 may be coupled to a pump cassette or cartridge configured to be coupled to the pump 22, such as the type described in co-pending U.S. patent application Ser. No. 13 / 827,775, which is incorporated herein by reference.

[0107] The types of pumping mechanisms, such as pumping mechanism 140, may vary, for example, be multi-finger pumping mechanisms. For example, the pumping mechanism may be of the "four finger" type, including an upstream occlusion finger 72, a primary pumping finger 74, a downstream occlusion finger 76, and a secondary pumping finger 78. "Four finger" pumping mechanisms, and mechanisms used in other linear peristaltic pumps, operate by sequentially pressing segments of a fluid conduit with cam-following pumping and valve fingers 72, 74, 76, and 78. Pressure is applied to successive locations of the conduit, beginning at the upstream end of the pumping mechanism and working toward the downstream end. At least one finger is always pressing hard enough to occlude the conduit. As a practical matter, one finger will not back away from occluding the tube until the next finger in turn has already occluded the tube, and therefore there is no direct fluid path from the fluid supply to the patient. The operation of peristaltic pumps, including four finger pumps, is well known to those skilled in the art, and further operational details will not be provided here.

[0108] In this particular embodiment, Figure 7C further illustrates a downstream pressure sensor 82 included with pump 22 in a downstream position relative to the pumping mechanism. The downstream pressure sensor 82 is attached to and positioned adjacent to the flow control device 70 and downstream relative to the flow control device. The downstream pressure sensor is positioned downstream of the flow control device, i.e., between the patient 48 (Figure 7A) and the flow control device, so that connection of the correct fluid source to the correct pump can be confirmed before any fluid is pumped to the patient.

[0109] 7C, an upstream pressure sensor 80 may also be included in the pump 22. The upstream pressure sensor is assigned to the flow control device or pumping mechanism 70, which in this embodiment is further provided as an integral part of the pump 22. The upstream pressure sensor is attached to the flow control device 70 and is located adjacent to and upstream relative to the flow control device. The upstream pressure sensor is located upstream of the flow control device, i.e., in a position between the fluid supply 38 (FIG. 7A) and the flow control device, so that connection of the correct fluid supply to the correct pump can be confirmed before any fluid is pumped to the patient. In an embodiment where the source is a syringe, the flow control device 70 may be configured to push the plunger of the syringe to provide an infusion according to programmed parameters.

[0110] One or more aspects or features of the subject matter described herein may be implemented in digital electronic circuitry, integrated circuits, specially designed ASICs, field programmable gate array (FPGA) computer hardware, firmware, software, and / or combinations thereof. These various aspects or features may include implementation in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. The programmable system or computing system may include clients and servers. The clients and servers are remote from each other and typically interact through a communication network. The relationship of clients and servers arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0111] These computer programs, which may also be referred to as programs, software, software applications, applications, components, or codes, include machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented programming language, and / or assembly / machine language. As used herein, the term "machine-readable medium" refers to any computer program product, apparatus, and / or device used to provide machine instructions and / or data to a programmable processor, such as, for example, magnetic disks, optical disks, memories, and programmable logic devices (PLDs), including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor. A machine-readable medium may store such machine instructions non-transiently, such as, for example, a non-transient solid-state memory or a magnetic hard drive or any equivalent storage medium. A machine-readable medium may alternatively or additionally store such machine instructions temporarily, such as, for example, a processor cache or other random access memory associated with one or more physical processor cores.

[0112] To provide for user interaction, one or more aspects or features of the subject matter described herein can be implemented on a computer having a display device, such as, for example, a cathode ray tube (CRT) or liquid crystal display (LCD) or light emitting diode (LED) monitor, for displaying information to a user, and a keyboard and pointing device, such as, for example, a mouse or trackball, by which the user can provide input to the computer. Other types of devices can also be used to provide for user interaction. For example, feedback provided to the user can be any form of sensory feedback, such as, for example, visual feedback, auditory feedback, or haptic feedback, and input from the user can be received in any form, including acoustic, voice, or tactile input. Other possible input devices include touch screens or other touch-sensitive devices, such as single-point or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software.

[0113] It should be understood that the disclosure, including the figures, described herein may describe and / or illustrate different variants separately, but may combine all or part of them, or components thereof.

[0114] Although various exemplary embodiments have been described above, any of a number of modifications may be made to the various embodiments. For example, the order in which the various described method steps are performed may often be changed in alternative embodiments, and in other alternative embodiments, one or more method steps may be skipped entirely. Any feature of the various device and system embodiments may be included in some embodiments and not in other embodiments. Thus, the foregoing description has been provided primarily for illustrative purposes and should not be construed as limiting the scope of the claims.

[0115] When a feature or element is referred to herein as being "on" another feature or element, it can be directly on the other feature or element, or there may be intervening features and / or elements. In contrast, when a feature or element is referred to as being "directly on" another feature or element, there are no intervening features or elements. When a feature or element is referred to as being "connected," "attached," or "coupled" to another feature or element, it can also be understood that it can be directly connected, attached, or coupled to the other feature or element, or there may be intervening features or elements. In contrast, when a feature or element is referred to as being "directly connected," "directly attached," or "directly coupled" to another feature or element, there are no intervening features or elements. Although described or illustrated with respect to one embodiment, the features and elements so described or illustrated may be applicable to other embodiments. Reference to a structure or feature located "adjacent" to another feature can have portions that overlap or underlie the adjacent feature.

[0116] The terms used herein are for the purpose of describing particular embodiments only and are not intended to be limiting. For example, as used herein, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly indicates otherwise. It can be further understood that the terms "comprises" and / or "comprising", as used herein, specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items and can be abbreviated as " / ".

[0117] For example, spatially relative terms such as "under," "below," "lower," "over," "upper," and the like may be used herein for ease of description to describe the relationship of one element or feature to another element or feature as shown in the figures. It may be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is inverted, elements described as being "below" or "directly below" the other element or feature would be oriented "above" the other element or feature. Thus, the exemplary term "under" can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or to other orientations) and the spatially relative descriptors used herein would be interpreted accordingly. Similarly, terms such as "upwardly," "downwardly," "vertical," "horizontal," etc. are used herein for descriptive purposes only, unless otherwise specified.

[0118] Although the terms "first" and "second" may be used herein to describe various features / elements (including steps), these features / elements should not be limited by these terms unless the context indicates otherwise. These terms may be used to distinguish one feature / element from another. Thus, a first feature / element described below can be referred to as a second feature / element, and similarly, a second feature / element described below can be referred to as a first feature / element without departing from the teachings provided herein.

[0119] Throughout this specification and the appended claims, unless the context requires otherwise, the word "comprise" and variations such as "comprises" and "comprising" mean that various components may be used jointly in methods and articles (e.g., compositions and apparatuses that include devices and methods). For example, the term "comprising" is understood to imply the inclusion of any described elements or steps but not the exclusion of any other elements or steps.

[0120] As used in this specification and claims, including as used in the examples, unless expressly specified otherwise, all numbers can be read as if they were preceded by the word "about" or "approximately", even if the term does not appear explicitly. The phrase "about" or "approximately" can be used when describing a size and / or location to indicate that the stated value and / or location is within a reasonable expected range of values ​​and / or locations. For example, a numerical value can have a value of + / -0.1% of the stated value (or range of values), + / -1% of the stated value (or range of values), + / -2% of the stated value (or range of values), + / -5% of the stated value (or range of values), + / -10% of the stated value (or range of values), etc. Any numerical value provided herein should also be understood to include approximately that value unless the context indicates otherwise.

[0121] The examples and illustrations contained herein show, by way of illustration and not limitation, specific embodiments in which the subject matter may be practiced. As previously mentioned, other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Although specific embodiments have been illustrated and described herein, any configuration calculated to achieve the same purpose may be substituted for the specific embodiment shown. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments and other embodiments not specifically described herein are possible.

[0122] In the above description and in the claims, phrases such as, for example, "at least one of" or "one or more of" may appear followed by a combined list of elements or features. The term "and / or" may also appear in a list of two or more elements or features. Such phrases are intended to mean any of the listed elements or features individually or any of the listed elements or features in combination with any of the other listed elements or features, unless otherwise implicitly or explicitly contradicted by the context in which it is used. For example, the phrases "at least one of A and B," "one or more of A and B," and "A and / or B" are intended to mean "A alone, B alone, or A and B together," respectively. A similar interpretation is intended for lists containing more than two items. For example, the phrases "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, and / or C" are intended to mean "A alone, B alone, C alone, A and B, A and C, B and C, or A, B and C," respectively. Use of the term "based on" above and in the claims is intended to mean "based at least in part on," allowing for unrecited features or elements.

[0123] A "user interface" as used herein (also referred to as an interactive user interface, graphical user interface, or UI) may refer to a network-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. The control elements may include dials, buttons, icons, selectable areas, or other perceivable indications presented via the UI that, when interacted with (e.g., click, touch, select, etc.), initiate an exchange of data for the device presenting the UI. The UI may be implemented in whole or in part using technologies such as Hypertext Markup Language (HTML), FLASH®, JAVA®, NET™, web services, or rich site summary (RSS). In some embodiments, the UI may be included in a standalone client (e.g., thick client, fat client) configured to communicate (e.g., send or receive data) according to one or more of the described aspects. The communication may be between a medical device or a server communicating with the medical device.

[0124] As used herein, the terms "determine" or "determining" encompass a wide variety of operations. For example, "determining" can include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up a table, database, or another data structure), ascertaining, etc., via hardware elements without user intervention. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc., via hardware elements without user intervention. "Determining" can include resolving, selecting, choosing, establishing, etc., via hardware elements without user intervention.

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

[0126] As used herein, the term "message" encompasses a wide variety of formats for communicating (e.g., sending or receiving) information. A message may include a machine-readable aggregation of information, such as an XML document, a fixed-field message, a comma-separated message, etc. A message may, in some implementations, include a signal utilized to transmit one or more representations of information. Although described in the singular, it may be understood that a message may be composed, transmitted, stored, received, etc., of multiple parts.

[0127] The term "selectively" or "selective" as used herein 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 to make the decision. In some implementations, an n-input switch may be included to provide the selection function, where n is the number of inputs used to make the selection.

[0128] The term "correspond" or "corresponding" as used herein encompasses a structural, functional, quantitative and / or qualitative correlation or relationship between two or more objects, data sets, information and / or the like, and preferably, the correspondence or relationship can be used to interpret one or more of the two or more objects, data sets, information and / or the like as being the same or equivalent. The correspondence can be evaluated using one or more of thresholds, ranges, fuzzy logic, pattern matching, machine learning evaluation models, or combinations thereof.

[0129] In any embodiment, the generated or detected data may be transferred to a "remote" device or location, where "remote" means a location or device other than the location or device where the program is executed. For example, a remote location may be another location in the same city (e.g., an office, a lab, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Thus, when an item is implied to be "remote" from another item, it means that the two items may be in the same room but separated, or at least in different rooms or different buildings, and may be at least 1 mile, 10 miles, or at least 100 miles apart. "Communicating" information refers to transmitting data representing that information as an electrical signal over an appropriate communication channel (e.g., a private or public network). "Transferring" an item refers to any means of getting the item from one location to the next, whether by physically transporting the item or by other means (if possible), and includes, at least in the case of data, physically transporting a medium carrying the data or communicating the data. Examples of communication media include wireless or infrared transmission channels, as well as a network connection to another computer or network device, and the Internet, or email transmissions and information stored on a website, and the like.

[0130] The examples and illustrations contained herein show, by way of illustration and not limitation, specific embodiments in which the subject matter may be practiced. As previously mentioned, other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Such embodiments of the subject matter of the present invention may be individually or collectively referred to herein by the term "invention" when more than one is actually disclosed, merely for convenience, and without any intention of spontaneously limiting the scope of the present application to any single invention or inventive concept. Thus, although specific embodiments have been illustrated and described herein, any configuration calculated to achieve the same purpose may be substituted for the specific embodiment illustrated. The present disclosure is intended to cover any and all adaptations or variations of the various embodiments. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art upon reviewing the above description.

Claims

1. 1. A portable infusion pump configured to be worn by a user, comprising: a fluid container configured to store a fluid to be delivered to a user; a pumping mechanism configured to effect delivery of fluid from the fluid container to a user via a fluid delivery tube; a communication circuit having an antenna; A portable infusion pump comprising: a detachable display configured to transmit a fluid delivery protocol to the communication circuitry of the portable infusion pump when the detachable display is coupled to the portable infusion pump and further configured to be detached from the portable infusion pump after transmitting the fluid delivery protocol to the portable infusion pump, the fluid delivery protocol defining one or more parameters for delivering fluid to a user; An infusion pump system comprising:

2. The system of claim 1 , wherein the portable infusion pump is disposable.

3. 3. The system of claim 1 or 2, wherein the communication circuitry comprises at least one of a low energy communication circuitry, a near field communication circuitry, and a Bluetooth low energy communication circuitry.

4. 3. The system of claim 1 or 2, wherein the detachable display includes an attachment sensor, and the detachable display is configured to transmit the fluid delivery protocol when a signal from the attachment sensor indicates that the detachable display is physically coupled to the portable infusion pump.

5. The system of claim 4 , wherein the physical coupling comprises a magnetic coupling.

6. 3. The system of claim 1 or 2, wherein the detachable display includes a proximity sensor, the detachable display configured to transmit the fluid delivery protocol when a signal from the proximity sensor indicates that the detachable display is positioned within a predetermined distance from the portable infusion pump.

7. The system of claim 1 or 2, further comprising the fluid delivery tube.

8. The system of claim 1 or 2, wherein the portable infusion pump includes a waterproof housing, and at least the fluid container, the pumping mechanism, and the communication circuitry are disposed within the waterproof housing.

9. 3. The system of claim 1 or 2, wherein the portable infusion pump comprises an alarm system for generating an alarm upon detection of an error during delivery of fluid to a user, the alarm including one or more of an audio, visual, and tactile alarm.

10. The system of claim 1 or 2, wherein the fluid container is configured to hold 100 milliliters or less of fluid.

11. 1. A portable infusion pump configured to be worn by a user, comprising: a fluid container configured to store a fluid to be delivered to a user; a pumping mechanism configured to effect delivery of fluid from the fluid container to a user via a fluid delivery tube; a communication circuit having an antenna; Equipped with the portable infusion pump is configured to be temporarily coupled to a detachable display; the communications circuitry is configured to receive a fluid delivery protocol from the separable display when the portable infusion pump is coupled to the separable display, the fluid delivery protocol defining one or more parameters for delivering fluid to a user; the portable infusion pump is configured to be decoupled from the display after receiving the fluid delivery protocol from the display. Portable infusion pump.

12. The pump of claim 11 , wherein the portable infusion pump is disposable.

13. 13. The pump of claim 11 or 12, wherein the communications circuitry comprises at least one of a low energy communications circuitry, a short range communications circuitry, and a Bluetooth low energy communications circuitry.

14. The pump of claim 11 or 12, wherein the detachable display includes an attachment sensor, the detachable display configured to transmit the fluid delivery protocol when a signal from the attachment sensor indicates that the detachable display is physically coupled to the portable infusion pump.

15. The pump of claim 14 , wherein the physical coupling comprises a magnetic coupling.

16. The pump of claim 11 or 12, wherein the detachable display includes a proximity sensor, the detachable display configured to transmit the fluid delivery protocol when a signal from the proximity sensor indicates that the detachable display is positioned within a predetermined distance from the portable infusion pump.

17. 13. The pump of claim 11 or 12, further comprising a fill port through which the fluid container is configured to be filled.

18. 13. The pump of claim 11 or 12, wherein the fluid container is configured to hold a plurality of fluid bags.

19. 13. The pump of claim 11 or 12, wherein the portable infusion pump includes a waterproof housing, and at least the fluid container, the pumping mechanism, and the communication circuitry are disposed within the waterproof housing.

20. 13. The pump of claim 11 or 12, further comprising an alarm system for generating an alarm upon detection of an error during delivery of fluid to a user, the alarm comprising one or more of an audio, visual and tactile alarm.

21. 13. The pump of claim 11 or 12, wherein the fluid reservoir is configured to hold no more than 100 milliliters of fluid.

22. at least one data processor; at least one memory storing instructions that, when executed by the at least one data processor, receiving at least one fluid delivery protocol by a portable infusion pump from a display, the display being temporarily coupled to the portable infusion pump; delivering fluid to a user according to the at least one fluid delivery protocol by the portable infusion pump; measuring, by the portable infusion pump, one or more fluid delivery parameters associated with the delivery of a fluid; establishing, by the portable infusion pump, a wireless connection with the display; transmitting, by the portable infusion pump, the one or more fluid delivery parameters to the display in wireless communication with the portable infusion pump; At least one memory that provides operations including: An infusion management system comprising:

23. The operation includes: detecting an error in the delivery of fluid to a user; stopping delivery of fluid to the user; 23. The system of claim 22, further comprising:

24. The operation includes: transmitting the error to the display while the display is in wireless communication with the portable infusion pump; displaying information regarding the error via the display; 24. The system of claim 23, further comprising:

25. The portable infusion pump comprises: a fluid container configured to store a fluid to be delivered to a user; a pumping mechanism configured to effect delivery of fluid from the fluid container to a user via a fluid delivery tube; a communication circuit having an antenna; 25. The system of claim 22, comprising:

26. The operation includes: establishing, by the portable infusion pump, a wireless connection with the display when an attachment sensor of the display indicates that the portable infusion pump is physically coupled to the display; disconnecting, by the portable infusion pump, a wireless connection with the display when the portable infusion pump is not physically coupled to the display; 25. The system of claim 22, further comprising:

27. 25. The system of any one of claims 22 to 24, wherein the portable infusion pump is disposable.

28. 26. The system of claim 25, wherein the communications circuitry comprises at least one of a low energy communications circuitry, a near field communications circuitry, and a Bluetooth low energy communications circuitry.

29. 26. The system of claim 25, wherein the portable infusion pump further comprises a fill port through which the fluid container is configured to be filled.

30. The system of claim 25 , wherein the fluid container is configured to hold a plurality of fluid bags.

31. 25. The system of any one of claims 22 to 24, wherein the portable infusion pump includes a waterproof housing, and at least the fluid container, the pumping mechanism, and the communication circuitry are disposed within the waterproof housing.

32. 26. The system of claim 25, wherein the portable infusion pump further comprises an alarm system for generating an alarm upon detection of an error during delivery of fluid to a user, the alarm including one or more of an audio, visual, and tactile alarm.

33. 26. The system of claim 25, wherein the fluid container is configured to hold 100 milliliters or less of fluid.

Images