Integrated Liquid Flow Closed-Loop Sensing and Control

Abstract

The integrated intravenous (IV) administration set includes a flow stop having a tubing fitment and a housing, the flow stop configured to prevent fluid flow through the tubing in a first position and to allow fluid flow through the tubing in a second position, the tubing fitment having a protrusion configured to receive the tubing. The IV administration set also includes an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure fluid flow through the tubing, and one or more conductive connections configured within the housing to provide power to the electronic flow sensor. The flow stop is configured to be mounted and engaged with a receptacle of an infusion device, and when mounted and engaged, the one or more conductive connections are configured to engage corresponding conductive connections provided by the infusion device to activate the flow sensor based on power flow from the infusion device.

Description

[Technical field]

[0001] This application is a non-provisional extension of U.S. Provisional Application No. 63 / 030,234, filed May 26, 2020, and entitled “INTEGRATED LIQUID FLOW CLOSED LOOP SENSING AND CONTROL,” which is hereby incorporated by reference in its entirety.

[0002] FIELD OF THE DISCLOSURE This application relates generally to sensing and controlling liquid flow in injection processes. [Background technology]

[0003] Infusion pumps commonly monitor the flow rate of the fluid being delivered. There is a desire to improve the efficiency, sensitivity, and accuracy of infusion pumps for sensing and controlling liquid flow having a wide range of dynamic flow rates during the infusion process. Summary of the Invention

[0004] Therapeutic fluid overinfusion occurs when there is a variance between the target flow rate set in the infusion device and the actual flow rate of therapeutic fluid infused through an intravenous (IV) administration set and into the patient.

[0005] Thus, there is a desire to improve the efficiency, sensitivity, and accuracy of over- or under-infusion detection. IV administration sets are typically disposable consumables that are used only once for the infusion process. Thus, IV administration sets generally do not include sensors or other electronics that monitor or control fluid flow. The IV sets described herein include liquid sensing capabilities and closed-loop flow control circuitry and are coupled to a mechanical flow stop to form an integrated platform for flow control and sensing. In some implementations, the flow stop may be referred to as a flow clamp, safety clamp, or slide clamp. The devices and methods described herein provide closed-loop flow control to an infusion pump that monitors the actual flow rate and adjusts the pump or alerts the user when there is any deviation from the set flow rate under normal operation or fault conditions.

[0006] The disclosed subject matter relates to an integrated intravenous (IV) administration set including a tubing fitment, the tubing fitment including a protrusion configured to receive tubing of an IV administration set. The set includes a housing coupled to the tubing fitment, an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure a flow of fluid through the tubing. The set includes one or more conductive connections configured to provide power and transmit data to the electronic flow sensor, and a flow stop configured to prevent fluid flow through the tubing in a first position and to allow fluid flow through the tubing in a second position. The tubing fitment is configured to mount to and engage an infusion device configured with a corresponding receptacle to maintain alignment of the housing to the infusion device.

[0007] The integrated IV administration set includes a control circuit for closed-loop flow control of a flow of a fluid, the closed-loop flow control being based on data measured by the electronic flow sensor. The control circuit is configured to send a control signal to the infusion device to modify a flow rate produced by a pump mechanism of the infusion device.

[0008] In another aspect, the sensor system includes a first plurality of conductive connections, a data port for receiving data recorded by an electronic flow sensor of an integrated intravenous (IV) administration set, the integrated IV administration set including a second plurality of conductive connections configured to interface with the first plurality of conductive connections when the integrated IV administration set is engaged with the sensor system, and the sensor system configured to provide a control signal to an infusion device based on the data recorded by the electronic flow sensor to maintain fluid flow through the integrated IV administration set at a desired flow rate.

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

[0010] For a better understanding of the various described implementations, reference should be made to the following description of implementations in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings and description, and in which: [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram depicting an example of a facility patient care system of a healthcare organization, in accordance with an aspect of the subject technology. [Diagram 2]1 depicts an example of an integrated administration set and infusion pump in accordance with an aspect of the subject technology. [Diagram 3] 1 is a close-up view of an integrated administration set and infusion pump in accordance with an aspect of the subject technology. [Figure 4A] 1 is a first perspective view of an integrated flow stop system according to an embodiment of the subject technology; [Figure 4B] FIG. 13 is a second perspective view of an integrated flow stop system according to an embodiment of the subject technology. [Figure 4C] FIG. 13 is a third perspective view of an integrated flow stop system according to an embodiment of the subject technology. [Figure 5A] A diagram depicting an example sensor system attached to an infusion device, in accordance with an aspect of the subject technology. [Figure 5B] A diagram depicting an example sensor system including a device having a port for accepting a flow sensor, in accordance with an aspect of the subject technology. [Figure 5C] A diagram depicting an example sensor system configured to couple two or more sensors and two or more pump modules in accordance with an aspect of the subject technology. [Figure 5D] FIG. 1 depicts an example sensor system in accordance with an aspect of the subject technology. [Figure 5E] A diagram depicting an example sensor system configured to couple two or more pump modules in accordance with an aspect of the subject technology. [Figure 6] 1 is a conceptual diagram illustrating an example system for sensing and controlling liquid flow in an injection process, in accordance with aspects of the subject technology. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0013] There is a need to more accurately monitor fluid flow during the infusion process. Unregulated flow, such as over- and under-infusion of therapeutic fluid, occurs when there is variation between the target flow rate set in the infusion device and the actual flow rate of therapeutic fluid through the IV administration set and into the patient.

[0014] The devices and methods described herein provide an integrated IV administration set that incorporates electronic sensing and control of fluid flow.

[0015] FIG. 1 depicts an example of an institutional patient care system 100 of a healthcare organization according to aspects of the subject technology. In FIG. 1, patient care devices (or generally "medical devices") 12 are connected to a hospital network 10. The term patient care device (or "PCD") may be used interchangeably with the term patient care unit (or "PCU"), both of which may include various ancillary medical devices, such as infusion pumps, vital signs monitors, medication delivery devices (e.g., cabinets, totes), medication preparation devices, automated delivery devices, modules coupled with one of the foregoing (e.g., a syringe pump module configured to attach to an infusion pump), or other similar devices. Each element 12 is connected to the internal healthcare network 10 by a transmission channel 31. The transmission channel 31 may be any wired or wireless transmission channel, such as, for example, an 802.11 wireless local area network (LAN). In some implementations, the network 10 also includes computer systems located in various departments throughout the hospital. 1 optionally includes computer systems associated with an admissions department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, and / or a medical decision support system. As described further below, network 10 may include separate sub-networks. In the depicted example, network 10 includes a device network 41 with which patient care devices 12 (and other devices) communicate according to normal operation.

[0016] Additionally, the facility patient care system 100 may incorporate a separate information system server 130, the functionality of which is described in more detail below. Moreover, while the information system server 130 is shown as a separate server, the functionality and programming of the information system server 130 may be incorporated into another computer, if desired by an engineer designing the facility's information system. The facility patient care system 100 may further include one or more device terminals 132 for connecting to and communicating with the information system server 130. The device terminals 132 may include personal computers, personal data assistants, mobile devices such as laptops, tablet computers, augmented reality devices, or smartphones, and are configured with software for communication with the information system server 130 over the network 10.

[0017] The patient care device 12 includes a system for providing patient care, such as that described in Eggers et al., which is incorporated herein by reference for that purpose. The patient care device 12 can include or incorporate pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeters, and other patient monitors), therapeutic devices, and other drug delivery devices that may be utilized in accordance with the teachings presented herein. In the depicted example, the patient care device 12 includes a control module 14, also referred to as an interface unit 14, connected to one or more functional modules 116, 118, 120, 122. The interface unit 14 includes a central processing unit (CPU) 50 connected to a memory, such as a random access memory (RAM) 58, and one or more interface devices, such as a user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices. The interface unit 14 also includes, but is not necessarily limited to, a main non-volatile storage unit 56, such as a hard disk drive or non-volatile flash memory, for storing software and data, as well as one or more internal buses 64 for interconnecting the aforementioned elements.

[0018] In various implementations, the user interface device 54 is a touch screen for displaying information to a user and for allowing the user to input information by touching defined areas of the screen. Additionally or alternatively, the user interface device 54 can include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, soft keys, a mouse, a track ball, and / or a light pen. The data input device 60 can be a bar code reader capable of scanning and interpreting data printed in a bar coded format. Additionally or alternatively, the data input device 60 can be any device for entering coded data into a computer, such as a device for reading magnetic stripes, a radio-frequency identification (RFID) device in which digital data encoded in an RFID tag or smart label (defined below) is captured by the reader 60 via radio waves, a PCMCIA smart card, a radio frequency card, a memory stick, a CD, a DVD, or any other analog or digital storage medium. Other examples of the data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending on the type of interface device used, the user interface device 54 and the data input device 60 may be the same device. Although the data input device 60 is shown in FIG. 1 as being located within the interface unit 14, it is recognized that the data input device 60 may be internal to the pharmacy system or may be external to the pharmacy system and communicate with the pharmacy system through an RS-232 serial interface or any other suitable communication means. The auxiliary interface 62 may be an RS-232 communication interface, although any other means for communicating with peripheral devices such as printers, patient monitors, infusion pumps, or other medical devices may be used without departing from the subject technology.Additionally, data input device 60 may be separate functional modules, such as modules 116, 118, 120, and 122, and may be configured to communicate with controller 14, or any other system on the network, using appropriate programming and communication protocols.

[0019] The network connection 52 may be a wired or wireless connection, such as via Ethernet, WiFi, BLUETOOTH, an Integrated Services Digital Network (ISDN) connection, a Digital Subscriber Line (DSL) modem or a cable modem, etc. Any direct or indirect network connection may be used, including, but not limited to, a telephone modem, a MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link or a WLANs connection, or other wireless connection.

[0020] Functional modules 116, 118, 120, 122 are any device for providing care to a patient or for monitoring a patient's condition. As shown in FIG. 1, at least one of functional modules 116, 118, 120, 122 may be an infusion pump module, such as an intravenous infusion pump for delivering medication or other fluids to a patient. For purposes of this discussion, functional module 116 is an infusion pump module. Each of functional modules 118, 120, 122 may be any patient treatment or monitoring device, including, but not limited to, an infusion pump, a syringe pump, a PCA pump, an epidural pump, an enteral pump, a blood pressure monitor, a pulse oximeter, an EKG monitor, an EEG monitor, a heart rate monitor, or an intracranial pressure monitor, or the like. Functional modules 118, 120, and / or 122 may be a printer, a scanner, a bar code reader, or any other peripheral input, output, or input / output device.

[0021] Each functional module 116, 118, 120, 122 communicates directly or indirectly with the interface unit 14, which provides overall monitoring and control of the device 12. The functional modules 116, 118, 120, 122 may be physically and electronically connected serially to one or both ends of the interface unit 14, as shown in FIG. 1 or as detailed in Eggers et al. Nevertheless, it is recognized that there are other means for connecting the functional modules with the interface units that may be utilized without departing from the subject technology. It will also be recognized that devices such as pumps or patient monitoring devices that provide sufficient programmability and connectivity may be capable of operating as standalone devices and may communicate directly with the network without being connected through a separate interface unit or control unit 14. As discussed above, additional medical or peripheral devices may be connected to the patient care device 12 through one or more auxiliary interfaces 62.

[0022] Each functional module 116, 118, 120, 122 may include module-specific components 76, a microprocessor 70, a volatile memory 72 for storing information, and a non-volatile memory 74. Note that although four functional modules are shown in FIG. 1C, any number of devices may be directly or indirectly connected to the central controller 14. The number and types of functional modules described herein are intended to be illustrative and in no way limit the scope of the subject technology. Module-specific components 76 include any components necessary for the operation of a particular module, such as a pump mechanism for the infusion pump module 116.

[0023] Although each functional module may be capable of at least some level of independent operation, interface unit 14 monitors and controls the overall operation of device 12. For example, as described in more detail below, interface unit 14 provides programming instructions to functional modules 116, 118, 120, 122 and monitors the status of each module.

[0024] The patient care device 12 is capable of operating in several different modes, or personalities, each of which is defined by a configuration database. The configuration database may be a database 56 internal to the patient care device, or an external database 37. A particular configuration database is selected based at least in part on patient-specific information, such as the patient's location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics, or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or the location of the patient care device 10 in the hospital or hospital computer network. Patient care information may be entered through interface devices 52, 54, 60, or 62 and may originate anywhere within the network 10, such as, for example, from a pharmacy server, an admissions server, a laboratory server, and the like.

[0025] Medical devices incorporating aspects of the subject technology may be equipped with a Network Interface Module (NIM) that enables the medical device to participate as a node in a network. For clarity, the subject technology is described as operating in an Ethernet network environment using the Internet Protocol (IP), however, it is understood that the concepts of the subject technology are equally applicable in other network environments and such environments are intended to be within the scope of the subject technology.

[0026] Data passing through various data sources can be converted to network-compatible data using existing technology, and the movement of information between medical devices and the network can be accomplished by various means. For example, the patient care devices 12 and the network 10 can communicate through automatic interaction, manual interaction, or a combination of both automatic and manual interaction. Automatic interaction can be continuous or intermittent and can occur through a direct network connection 52 (as shown in FIG. 1) or through an RS232 link, MIB system, RF link, such as BLUETOOTH, IR link, WLANs, digital cable system, telephone modem, or other wired or wireless communication means. Manual interaction between the patient care devices 12 and the network 10 involves intermittent or periodic physical transfer of data between the systems, for example, using a user interface device 54, a coded data entry device 60, a bar code, a computer disk, a portable data assistant, a memory card, or any other medium for storing data. The communication means in various embodiments is bidirectional with access to data from as many points as possible of distributed data sources. Decisions can occur at various locations within the network 10. For example, and not by way of limitation, decisions can be made at the HIS server 30, decision support 48, remote data server 49, hospital department or unit station 46, or within the patient care device 12 itself.

[0027] All direct communication with medical devices operating on a network according to the subject technology may be conducted through an information system server 30 known as a remote data server (RDS). According to an aspect of the subject technology, a network interface module built into a medical device, such as an infusion pump or a vital signs measurement device, ignores all network traffic that does not originate from an authenticated RDS. The primary responsibility of the RDS of the subject technology is to track the location and status of all networked medical devices that have a NIM and maintain open communication.

[0028] FIG. 2 depicts an example of an integrated administration set and infusion pump according to aspects of the subject technology. In some implementations, the administration set 200 includes an integrated flow stop system 202. The integrated flow stop system 202 provides closed-loop control and flow sensing in addition to functioning as a mechanical flow stop device. FIGS. 4A-4C provide different views of the integrated flow stop system 202. IV administration sets are typically disposable consumables that are used only once. As such, they generally do not include sensors or other electronics that monitor or control fluid flow. In contrast, the integrated IV set 200 includes liquid sensing capabilities and closed-loop flow control circuitry that directly enhance the accuracy and efficiency of flow sensing in the administration set and improve overall control of flow rate based at least in part on the sensed value.

[0029] A closed loop control system (or feedback control system) can automatically regulate a process variable to a desired set point with limited or even no human interaction. The control circuitry of the integrated flow stop system 202 detects the flow rate of the infusion process by generating a control message to adjust one or more elements of the patient care device. The control message can be generated based on a set (e.g., desired) flow rate provided at the infusion pump compared to the detected flow rate of the infusion pump. A closed loop control system includes one or more feedback loops between its output value and its input value. A closed loop control system can generate an error signal reflecting the difference between its output value (e.g., flow rate measured by a flow sensor) and its reference input value (e.g., set flow rate provided at the infusion pump), and the control message generated by the closed loop control system depends on the output value. For example, a control signal sent by the control circuitry changes an operating parameter of the infusion pump to bring the measured flow rate as close as possible to the set (e.g., desired) flow rate.

[0030] 2 depicts an administration set 200 coupled to a large volume pump (LVP) 250. In some implementations, the administration set 200 is used with a syringe pump or other infusion pump system. The LVP 250 includes a door 252, an upper tube fitment receptacle 254, and a pump mechanism 256. The LVP 250 also includes a molded feature 260 having a shape complementary to a corresponding portion of the integrated flow stop system 202. In this manner, the molded feature 260 ensures a snug fit of the integrated flow stop system 202 when the IV administration set 200 is loaded onto and engaged with the pump 250.

[0031] A first plurality of conductive connections 258 (FIG. 2 depicts four different conductive connections) to the pump 250 allows electricity and data to flow between the pump 250 and the integrated flow stop system 202 when the integrated IV administration set 200 is loaded onto and engaged with the pump 250. Each of the conductive connections 258 may be formed from the same material or different materials depending on the conductive path formed. For example, the conductive connections for power may be formed from metal or other materials to conduct electricity, while the data connections may be formed from metal or fiber optic conductive materials to form a data pathway. The pump 250 also includes a retainer 264 for securing the tubing 214. The pump 250 includes an inter-unit interface (IUI) connector 266. The IUI connector 266 establishes power and communication between the pump 250 and the various attached modules.

[0032] The receiving portion 262 of the pump 250 defines a slot into which the tube fitment 222 of the integrated flow stop system 202 is mounted. The flow stop 210 is coupled to and positioned below the tube fitment 222. As will be described in more detail with reference to Figures 4A-4C, the flow stop 210 is configured to slide between two positions.

[0033] In the first position (open), the flow stop 210 is aligned with the tube fitment 222 (as shown in FIG. 4B) and does not obstruct fluid flow through the tube 214. In the second position (closed), the flow stop 210 slides toward the tube 214 protruding from under the tube fitment 222, mechanically clamping the tube 214 to obstruct fluid flow.

[0034] In some implementations, the flow stop 210 is in the open position when the administration set 200 is loaded onto the pump 250. During the infusion process, the door 252 is closed and the flow stop 210 remains in the open position to allow fluid flow. When the door 252 is opened (e.g., accidentally) during the infusion process, the flow stop 210 automatically changes to the closed position and mechanically pinches the tubing 214 to prevent the unexpected spillage of fluid.

[0035] The integrated flow stop system 202 adds electronic control functionality to the flow stop. In some implementations, when the integrated administration set 200 is loaded onto the pump 250, the flow stop 210 is engaged (e.g., left in an open position) and the plurality of conductive connections 258 interface with corresponding conductive connections on the integrated flow stop system 202. The conductive connections provide power to and activate an electronic flow sensor 406 (shown in FIG. 4C ) disposed within a housing 450 of the integrated flow stop system 202. In addition to conducting electricity, the plurality of conductive connections 258 also allow sensor data and / or control signals from the flow sensor 406 or closed-loop control circuitry to be relayed to the pump 250.

[0036] For example, in some implementations, a control signal from the closed loop control circuit changes an operating parameter of the pump mechanism 256 to change the measured flow rate at the electronic flow sensor 406 so that the value approaches the desired set flow rate programmed in the pump 250.

[0037] In some implementations, the integrated flow stop system 202 also includes a non-volatile memory component configured to store identification information of the administration set 200. For example, when the integrated flow stop system 202 is properly mounted and engaged with the pump 250, the data stored in the non-volatile memory component is read by the pump 250. In some implementations, the memory component stores information about how long the administration set 200 has been in use. For example, a circuit component (e.g., an electronic time counter) disposed within the integrated flow stop system 202 records the length of time that the integrated flow stop system 202 has received electricity from the plurality of conductive connections 258. In some implementations, the memory component also stores flow rate data measured by the electronic flow sensor 406.

[0038] In some implementations, the integrated flow stop system 202 includes a wireless communication module. The flow rate data measured by the electronic flow sensor 406 is uploaded directly to a server system (e.g., of a hospital system) that monitors the operation of the pump 250. In some implementations, the pump 250 stores flow rate values ​​for different infusion fluid types and modifies its operating parameters based on the flow rates measured by the electronic flow sensor 406. The pump 250 receives the measured flow rates relayed directly by the integrated flow stop system 202 or transmitted from a server system.

[0039] In some implementations, the identification information stored in the non-volatile memory includes a manufacturing date of the administration set, which allows the pump 250 to determine the shelf life of the administration set loaded on the pump 250. Once a conductive connection is established between the integrated flow stop system 202 and the pump 250 (e.g., through the plurality of conductive connections 258), the pump 250 can obtain shelf life information from the administration set 200. The shelf life information can identify an expiration date of the set after which the set should not be used. To ensure patient safety, the pump 250 can block the infusion process for administration sets that have exceeded the identified shelf life. The identification information can include additional or alternative information regarding the use of the administration set 200. For example, the identification information can include a maximum usage time of the administration set 200. In such cases, the pump 250 can terminate the infusion process and / or sound an alarm when the administration set 200 has been in use for longer than the maximum usage time. This can help minimize infection risks associated with excessive use of the administration set. Other usage information may include drug types that may or may not be infused with the administration set, pumps or pump modules that are compatible with the administration set, or calibration values ​​that may be used to improve the accuracy of pressure sensing and flow delivery performance. In some implementations, additional information may be provided via the flow stop system 202, such as whether the IV bag is empty and there is no flow, whether there is an occlusion condition due to pressure buildup and its effect on the flow pattern. If the latch on the flow stop does not engage or engages in a manner that is not within specifications, unregulated flow may result. The flow stop systems described herein may be capable of detecting such conditions since the pump module may communicate with the flow stop.

[0040] Incorporating electronic functionality into the integrated flow stop system 202 allows for easy association of a flow sensor (in a particular administration set) to a pump. For pumps with multi-channel infusion capabilities, automatically establishing a data channel between the pump and each administration set's flow sensor (e.g., through multiple conductive connections 258) minimizes errors (e.g., associating the wrong flow rate with the wrong infusion channel) and reduces the need for manual checking of the administration set during on-boarding or the infusion process from health care professionals. In some implementations, the IV bag and set are prepared together by the pharmacy. An identification ("ID") number can be associated with both the IV bag and administration set. The ID number can be read by the pump and correlated to the drug, flow rate, and volume that will be administered to the patient. The pump can be programmed based on these parameters, without the need for the clinician to enter these values. In some implementations, such information can be provided by the integrated flow stop system 202.

[0041] In some implementations, the plurality of conductive connections 258 include spring-loaded pogo pin type connectors. In some implementations, the conductive connections 258 are made from a resilient plastic conductor material. In some implementations, there is a contactless transfer of power and / or data between the integrated flow stop system 202 and the pump 250. The contactless transfer of power includes an inductive coupling element. For example, the pump 250 includes a transmitting device driven by power from a power source to generate a time-varying electromagnetic field. The electromagnetic field transmits the power across space to a receiving device of the integrated flow stop system 202. The receiving device extracts power from the electromagnetic field and provides the power to an electrical load (e.g., the electronic flow sensor 406 and / or control circuitry).

[0042] Molded features 260 in the housing of the pump 250 receive, center, and position the housing 450 of the integrated flow stop system 202 (and components such as the electronic flow sensor 406) and ensure fit of the flow stop 210 and electrical contact between the integrated flow stop system 202 and the pump 250.

[0043] At low flow rates, pumps can produce large relative changes in flow even with small deviations (i.e., a small change in flow equates to a large percentage change when the flow rate is small). In other words, a small (absolute) change in flow produces a large percentage (i.e., relative) change. The large relative change limits the dynamic range of flow that a flow sensor can reliably detect.

[0044] Additionally, areas close to the pump mechanism 256 are often subject to high noise factors (e.g., from the motor generating bursts of flow in the system). In some implementations, the system 202 is provided in the upper fitting area of ​​the pump above the pump mechanism 256 (e.g., the upper tube fitting receptacle 254), and the flow stop would not be part of the flow sensor. In such an implementation, the administration set would have two separate fittings, one containing the (standalone) flow sensor and associated control circuitry, and the other (lower) fitting having the flow stop clamp. Locating the flow sensor and control circuitry near the upper tube fitting receptacle 254 allows the flow rate to be measured in an area of ​​the pump that has a lower noise factor and results in a more accurate measurement. The lower noise factor also allows the dynamic range of the flow rate measurement to be improved. In some implementations, the flow sensor 406 measures a dynamic range of flow rates from 0.1 ml / hr to 999 ml / hr.

[0045] Although Figures 2 and 3 show insertion of the integrated flow stop system 202 in a lower region of the pump 250, an administration set according to aspects of the subject technology can be inserted in other regions of the pump 250.

[0046] In some implementations, instead of the entire integrated flow stop system 202 being positioned (e.g., inserted) in the upper tube fitment receptacle 254, only the electronics (e.g., electronic flow sensor 406, control circuitry, wireless communication module, inductive coupling elements) contained in the housing 450 are inserted in the upper section (e.g., while still encased in the housing). In such implementations, the tube fitment 222 and the flow stop 210 are still inserted below the pump mechanism 256, similar to the configuration shown in FIG. 2. In such a configuration, the components contained in the upper tube fitment may be conductively coupled to the flow stop 210. In this manner, resources such as power and data may be conducted through the flow stop 210 to the components contained in the upper tube fitment. The conductive path may be formed on or in the wall of the administration set, or the conductive path may be wireless. In other words, the flow sensor may be part of the upper fitment and the power or communication may be part of the flow stop in the lower fitment.

[0047] FIG. 3 depicts a close-up view of an integrated administration set and infusion pump in accordance with aspects of the subject technology. In some implementations, a portion of the pump 250 receives the integrated administration set 200. The molded feature 260 has a shape complementary to the housing 450 of the integrated flow stop system 202. A plurality of vertically arranged conductive connections 258 are embedded in the pump housing and interface with conductive connections in the integrated flow stop system 202 (as shown more clearly in FIGS. 4A-4C ). FIG. 3 more clearly depicts how the receiving portion 262 will engage with the pump-side fitting region 220 of the tube fitting 222.

[0048] 4A depicts a first perspective view of an integrated flow stop system in accordance with an embodiment of the subject technology. As shown in the close-up view of the integrated flow stop system 202, the integrated flow stop system 202 includes a tube fitment 222, a housing 450, and a flow stop 210. The tube fitment 222 includes a protrusion 228 configured to receive the tube 212. The integrated flow stop system 202 includes a flow stop 210. The flow stop 210 includes a slider portion 216. The flow stop 210 is movably mounted to and positioned below the tube fitment 222. The slider portion 216 of the flow stop 210 can slide along a channel defined within the tube fitment 222.

[0049] The flow stop 210 is a clamping device or safety clamp that prevents inadvertent free flow of fluid in the tubing 212 when the administration set 200 is removed from the infusion device. The slider portion 216 slides along a direction 410 annotated with a double-headed arrow. When the slider portion 216 slides closer to the pump-side fitting area 220 of the fitting 222, the flow stop 210 is in an open position, which allows fluid to flow through the tubing 212 from the upper portion of the integrated flow stop system 202 to the tubing 214 connected to the lower portion of the integrated flow stop system 202. As the slider portion 216 slides toward the tube-side region 230 of the fitting 222, the rounded region 224 of the teardrop-shaped opening 218 moves away from the tube 214 such that the narrower region 226 of the flow step 210 attracts the tube 214 and mechanically constricts (e.g., pinches or clamps) the tube 214, occluding the flow of fluid through the tube 214. In this closed position, the edge portion 230 of the flow stop 210 extends (e.g., protrudes) beyond the tube-side region 230 of the fitting 222 along the direction 410.

[0050] When the administration set 200 is properly loaded (e.g., engaged with) and accepted by the pump 250, the flow stop 210 of the administration set 200 is maintained in an open state that allows fluid to flow through the tube 214. When the infusion process is interrupted (e.g., by opening the door 252 of the pump 250), the flow stop 210 moves to a closed position to prevent the unexpected flow of fluid during the interruption of the infusion process. For example, the door 252 can include a latching element that secures the door in place relative to the pump 250. When a handle attached to the front of the door 252 is lifted, this lifting action can release the latching element. In doing so, the change in position of the latching element can change the position of the flow stop 210 to the closed position. In some implementations, opening the door exerts the force necessary to move the flow stop 210 to the closed position. For example, a flange 236 can engage under the flow stop 210. When the door 252 is opened, the flange is pulled away from the pump 250 and the flow stop 210. Once the flange is off the pump 250, the pump 250 can slide the flow stop 210 into a closed position.

[0051] Conventional dosing sets typically rely on flow sensors that are external to or integrated into the pump. Having a flow sensor integrated into the flow stop allows for greater sensitivity in measuring different flow rates. The flow stop 210 can include a door-facing housing 234. The door-facing housing 234 can additionally or alternatively include a conductive connector for interfacing with a connector attached to the door 252. The door-facing housing 234 can include electronic components for implementing one or more of the described features, such as sensors, microprocessors, memory, power, antennas, valves or valve controllers (e.g., piezoelectric or electromagnetic controllers), and / or optical fibers.

[0052] In some implementations, the flow stop is in the downstream section of the pump so that the flow towards the patient is more precisely controlled for flow continuity. Upstream flow monitoring measures the flow rate of the intake. In some implementations, the intake fills very quickly to allow flow continuity downstream. Therefore, it may be desirable to monitor the flow at the downstream section of the pump. Assuming there are no leaks or restrictions down from the pump to the needle (e.g., the location of fluid entry to the patient), the location of the flow monitor should not be critical. Placing the flow sensor near or in the pump reduces the length of the conductive (e.g., electrical) leads.

[0053] 4B depicts a second perspective view of an integrated flow stop system in accordance with an embodiment of the subject technology. As shown, flow stop 210 is in an open position. In the open position, rounded region 224 of teardrop-shaped opening 218 does not mechanically obstruct the flow of fluid within tube 214. In the open position, edge 232 of flow stop 210 does not protrude beyond tube-side region 230 of tube fitment 222.

[0054] FIG. 4C depicts a third perspective view of an integrated flow stop system according to an embodiment of the subject technology. The view of the integrated flow stop system 202 from the pump side shows several conductive connections 402-a to 402-e in a recess 404 in an upper housing 450 of the integrated flow stop system 202. The fitting 222 forms the lower portion of the system 202. The recess 404 can facilitate the fitting of the conductive connections to corresponding receiving portions of the conductive connections on the pump 250. As shown in FIG. 4C, the flow stop system 202 includes five conductive connections, while the pump interface includes four (see FIG. 3, element 258). The conductive connections may be different between the flow stop system 202 and the pump shown in FIG. 4C. This allows the flow stop system 202 to interface with a variety of different pumps, thereby improving the functionality provided when resources are available. In some cases, the flow stop system 202 may become inoperable if there is not sufficient connectivity with the pump. In such cases, the flow stop system 202 may include a valve that remains closed to prevent fluid from being infused through the administration set. In such cases, the pump may receive a message from the flow stop system 202 that prevents infusion through the pump until the administration set is replaced.

[0055] The housing 450 of the integrated flow stop system 202 includes one or more flow sensors. In some implementations, at least a portion of the flow sensor may be in contact with the fluid. In such implementations, the flow sensor may include a metering element in the fluid path that may be moved based on the velocity of the fluid moving along the fluid path. In some implementations, the pressure (or differential pressure) in series of the fluid along the fluid path or a constricted fluid path may be measured to determine the flow rate.

[0056] In some implementations, the fluid may not be in contact with the flow sensor. In some implementations, the flow sensor may include two components, one in the housing 450 and one in the housing 234 facing the door. An emission from one component may be read by the second component. A comparison between the emitted signal and the received signal may provide an indication of the flow rate. In some implementations, the flow sensor may include an acoustic sensor. The acoustic sensor may detect noise in the fluid line as the fluid flows past the sensor. The detected noise may be used to identify the flow rate. In some implementations, the acoustic sensor includes an ultrasonic method of flow detection.

[0057] In some implementations, the flow sensor operates based on the calorimetric principle. For example, a static heating element and two temperature sensors are placed in the fluid path and the flow rate is measured based on the change in the temperature profile of the fluid. Such flow sensors may be CMOS-based. In some implementations, the flow sensor operates based on the time-of-flight principle. Unlike static heaters, a time-of-flight based heater is modulated and receivers both upstream and downstream of the heater receive the modulated signal. Based on the arrival time of the modulated signal, the flow rate is determined. In some implementations, such flow sensors may be packaged as MEMS.

[0058] In some implementations, electrical energy for powering the flow sensor is transmitted from the pump to the flow sensor through the conductive connection 402-a. The flow sensor sends data back to the pump 250 through one of the conductive connections. In some implementations, the conductive connections 402-a and 402-e include pogo pin type connectors. In some implementations, the conductive connections 402-a and 402-e include a resilient plastic conductive material. In some implementations, the conductive connections 402-a and 402-e form a conductive connection with an inductive power source housed within the pump. The inductive power source includes an inductive coupling component configured to wirelessly transfer power from the pump to the electronic flow sensor. In such a case, the conductive connection does not need to be formed on an exposed surface of the housing 450 at the top of the integrated flow stop system 202.

[0059] In some implementations, the integrated flow stop system 202 includes wireless communication circuitry that enables the administration set 200 to form a wireless coupling with a pump and / or a server system. In some implementations, the wireless coupling is formed automatically without specific user input. Such a wireless connection allows the server system to track the location of a particular administration set and also allows the server system to receive information about the flow rates of therapeutic treatments provided by different administration sets.

[0060] The housing 450 at the top of the system 202 also contains various circuit components that allow the pump to identify a particular administration set. A non-volatile memory in the circuit can store information regarding the date of manufacture of the administration set 200, allowing the pump to ascertain whether the administration set 200 has exceeded a particular shelf life. In some implementations, to ensure patient safety, the pump will not proceed with the infusion process when it reads from the non-volatile memory of the integrated flow stop system 202 that the administration set 200 has exceeded its shelf life. In some implementations, the pump can obtain life information from the non-volatile memory of the administration set 200 as the administration set becomes less accurate toward its end of life. Thus, the integrated flow stop system 202 provides the pump 250 with a smart sensor. The pump can also record the time of use measured with a particular administration set. In some implementations, when a patient is transferred between different zones within the hospital (e.g., from the intensive care unit to a general ward), the same administration set is used / associated with a different pump and the circuit components on the integrated flow stop system 202 provide information to the hospital system regarding the total duration of the therapy treatment.

[0061] The circuitry contained within the housing 450 at the top of the integrated flow stop system 202 also includes a closed loop flow control circuit. In some implementations, the closed loop flow control circuit directly receives real time data recorded by the flow sensor (or other sensors included in the flow stop, such as temperature sensors, light sensors, cameras, gyro sensors or accelerometers to identify if the set was inserted correctly by the user, Near Field Communication (NFC) sensors for powering, communicating and / or authenticating authorized administration sets, Bluetooth Low Energy (BLE) beacons for asset management and to identify active infusion and administration sets) and provides control signals to the pump 250 to vary the pump flow rate to achieve a desired therapeutic fluid flow rate profile of the infusion. In some implementations, the flow sensor includes a capacitive sensor that measures flow based on dielectric changes caused by fluid flow. In some implementations, it may be desirable to provide measurements to the pump so that the pump can evaluate and apply adjustments to achieve a target pump state.

[0062] Having a flow sensor provides real-time measured data to a closed-loop flow control circuit contained within the housing 450 of the integrated flow stop system 202, minimizing or potentially eliminating the need to transfer raw flow data to the pump, reducing the latency between detecting the flow rate and the pump receiving, calculating, and regulating the flow rate. In some implementations, the housing 450 of the integrated flow stop system 202 can include novel control circuitry and / or firmware that can provide enhanced flow control or other fluid property sensing based on the administration set's control circuitry, even for older style pumps, without the need to install or modify the pump or add and match additional sensors. In some implementations, the additional circuitry provides the ability to update the flow stop firmware over the air, so that algorithms can be enhanced to improve flow sensitivity without the need to reconfigure pumps already deployed in the field. In some implementations, older pumps with mating connections can be connected to flow stops with corresponding conductive connections (e.g., electrical conductive connections and data conductive elements).

[0063] In some implementations, the measured flow rate or other fluid property data is stored on the administration set. In some implementations, the measured flow rate or other fluid property data is stored on the system (e.g., on the pump or on a server system (e.g., in a hospital system)).

[0064] The pump contains flow values ​​for different fluid types. By measuring and controlling the flow in a closed loop directly above the administration set, greater accuracy is achieved. Greater accuracy allows for better prediction of the volume of therapeutic fluid that will be infused into the patient. The system 250 detects the risk of unregulated flow (e.g., over-infusion, under-infusion) and proactively corrects any infusion volume errors.

[0065] FIG. 5A depicts an example sensor system attached to an infusion device, according to aspects of the subject technology. Instead of an integrated flow stop system 202 that establishes an electrical or data connection to a control module 14 (e.g., pump 250), a sensor wedge 500 has one or more sensor plug-ins 502 for coupling one or more separate administration sets (e.g., 508, 510) that infuse one or more fluids into a patient via an integrated flow stop system (similar to the flow stop system 202 described in FIGS. 2-4D). In some implementations, various flow features can be integrated into one or more sensor plug-ins 502. In some implementations, a sensor feature is plugged into the wedge (as shown in FIGS. 5B and 5C) or included (e.g., attached) to the wedge (as shown in FIGS. 5D and 5E). When a sensor feature is included in the sensor 500, an administration set (e.g., 508, 510) can be mounted to the sensor plug-in 502 for non-contact sensing (e.g., through tubing, without direct contact with the fluid).

[0066] In some implementations, modules 504 and 506 can include different pumps, such as a large volume pump (LVP), a syringe pump, or an end-tidal CO2 monitor (EtCO2). In some implementations, the sensor plug-in can be clamped outside of the administration set without being coupled to or integrated into the administration set. In this way, the sensor plug-in can be reused for multiple infusions. In some implementations, the sensor plug-in is integrated into the administration set and includes one or more conductive coupling elements for connecting with the sensor wedge.

[0067] The control module 14 can include a user interface device 54. The sensor wedge 500 can be attached to the pump to provide sensing capabilities via the IUI connector 266 (shown in FIG. 2). Data and power can be transferred via the IUI connector 266. The sensor wedge can include circuit components similar to a flow stop, such as a microprocessor, memory, power storage, antenna, and sensors. The sensor plug-in can provide measurements to the sensor wedge 500. As discussed, the sensor wedge can process the measurements and provide control messages to regulate the pump. In some implementations, the sensor wedge can transfer sensor readings to the pump to allow the pump to evaluate normal control. In some implementations, the sensor wedge allows for the flow sensor and control circuitry to be placed on the top tube fitting rather than the bottom fitting.

[0068] FIG. 5B depicts an example sensor system including a device having a port for receiving a flow sensor, according to aspects of the subject technology. FIG. 5B shows a view of one side of a wedge sensor 520. The wedge sensor 520 has a housing 522. In some implementations, the housing 522 has a first major surface 524 and a second major surface (not shown in FIG. 5B) parallel to the first major surface 524. The processor of the wedge sensor 520 is internal to the housing 522. The storage memory is also internal to the housing 522.

[0069] The wedge sensor 520 includes a connection element 528 mounted to a first surface 524 of the housing 522. In some implementations, the connection element 528 is an inter-unit interface connector configured to mate with an IUI connector of a pump module or a patient care unit (PCU). The connection element 528 includes a data conductive element for transferring data from the wedge sensor 520 to the pump module or the PCU. The connection element 528 also includes an electrical conductive element for transferring power. In some implementations, the connection element 528 receives power from the infusion device and data is transferred between the sensor system and the infusion device. In some implementations, the connection element 528 includes a mounting element for mounting to a corresponding interface connector of the infusion device. In some implementations, the infusion device has a predetermined length and the first surface 524 of the housing 522 has a length that exceeds the predetermined length such that the first electronic flow sensor can extend from the first surface 524 below or above the infusion device.

[0070] In some implementations, the inter-unit interface connector 528 includes a mounting element for mounting to a corresponding interface connector of a first infusion device, and the second inter-unit interface connector 534 includes a second mounting element for mounting to a corresponding interface connector of a second infusion device. In some implementations, power is received from the first infusion device, and data is transferred between the sensor system and the first infusion device. In some implementations, the power received by the second inter-unit interface connector 534 includes at least a portion of the power received by the inter-unit interface connector 528 and is transmitted to the second infusion device. The data received by the second inter-unit interface connector 534 includes at least a portion of the data transferred between the sensor system and the first infusion device, and is transferred between the sensor system and the second infusion device.

[0071] The wedge sensor 520 includes an electronic flow sensor port 526 on a first major surface 524 for receiving a flow sensor. In some implementations, the port 522 includes three pins, as shown in FIG. 5B. In some implementations, there may be more or fewer pins depending on the power and data capabilities of the flow sensor. The port 526 is configured to receive flow information from a first electronic flow sensor of a first fluid line coupled to the port 526 (e.g., from an administration set). The data conducting element, the electrical conducting element, and the electronic flow sensor port are coupled to a processor.

[0072] A second connection element 534 (shown in FIG. 5C ) is mounted to the second surface 522 of the housing. In some implementations, the second connection element is similar to the connection element mounted to the first major surface 524 and is configured to mate with an IUI connector of a pump module or PCU, includes a second data conduction element for transferring second data from the wedge sensor 520 to the pump module or PCU, and includes a second electrical conduction element for transferring power.

[0073] A second electronic flow sensor port 536 (shown in FIG. 5C) is also mounted to the second major surface. In some implementations, the second electronic flow sensor port is similar to the electronic flow sensor port 526 mounted to the first major surface 524 and is configured to receive flow information from a second electronic flow sensor of a second fluid line coupled to the second electronic flow sensor port (e.g., from an administration set). The second data conducting element, the second electrical conducting element, and the second electronic flow sensor port are also coupled to the processor.

[0074] In some implementations, a first portion 530 of the housing 522 has a height x that corresponds to the height of the pump module. A second portion 532 of the housing 522 includes the port 526 and has a height n. In some implementations, the sum of the height of the first portion 530 and the height of the second portion 532 exceeds the height of the pump module, providing clearance for the sensor.

[0075] FIG. 5C depicts an example sensor system configured to couple two or more sensors and two or more pump modules, according to aspects of the subject technology. FIG. 5C illustrates coupling between the microprocessor of the wedge sensor 520 and various connectors and ports. In some implementations, a first IUI connector 528 and a first electronic flow sensor port 526 are both mounted on a first major surface 524 of the housing 522 and coupled to the microprocessor. The microprocessor of the wedge sensor 520 is also coupled to a second IUI connector 534 and a second electronic flow sensor port 536, both mounted on a second major surface of the housing 522. A storage memory or other memory is also coupled to the microprocessor. In other words, the wedge sensor 520 includes two sensor ports (one on each side of the wedge sensor 520) and is configured to couple to two PCUs (one on each side of the wedge).

[0076] FIG. 5D depicts an example sensor system in accordance with aspects of the subject technology. FIG. 5D shows a view of one side of a wedge sensor 540. The wedge sensor 540 has a housing 542. In some implementations, the housing 542 has a first major surface 544 and a second major surface (not shown in FIG. 5D) parallel to the first major surface 544. The processor of the wedge sensor 540 is internal to the housing 542. The storage memory is also internal to the housing 542.

[0077] The wedge sensor 540 includes a connection element 548 mounted to a first surface 544 of the housing 542. In some implementations, the connection element 548 is an IUI connector configured to mate with an IUI connector of an infusion device (e.g., a pump module or a PCU). The connection element 548 includes a data conductive element for transferring data from the wedge sensor 540 to the pump module or PCU. The connection element 548 also includes an electrical conductive element for transferring power. In some implementations, the connection element 548 receives power from the infusion device and data is transferred between the sensor system and the infusion device. In some implementations, the connection element 548 includes a mounting element for mounting to a corresponding interface connector of the infusion device. In some implementations, the infusion device has a predetermined length and the first surface 544 of the housing 542 has a length that exceeds the predetermined length such that the first electronic flow sensor can extend from the first surface 544 below or above the infusion device.

[0078] In some implementations, the inter-unit interface connector 548 includes a mounting element for mounting to a corresponding interface connector of a first infusion device, and the second inter-unit interface connector 554 includes a second mounting element for mounting to a corresponding interface connector of a second infusion device. In some implementations, power is received from the first infusion device and data is transferred between the sensor system and the first infusion device. In some implementations, the power received by the second inter-unit interface connector 554 includes at least a portion of the power received by the inter-unit interface connector 548 and is transmitted to the second infusion device. The data received by the second inter-unit interface connector 554 includes at least a portion of the data transferred between the sensor system and the first infusion device and is transferred between the sensor system and the second infusion device.

[0079] An electronic flow sensor 546 attached to the first major surface 544 is configured to measure flow information of a first fluid line coupled thereto. The data conducting element, the electrical conducting element, and the first electronic flow sensor are coupled to the processor.

[0080] A second connection element 554 (shown in FIG. 5E ) is mounted to a second surface of the housing 552. In some implementations, the second connection element is similar to the connection element mounted to the first major surface 554 and is configured to mate with an IUI connector of a pump module or PCU, includes a second data conduction element for transferring second data from the wedge sensor 550 to the pump module or PCU, and includes a second electrical conduction element for transferring power.

[0081] A second electronic flow sensor 556 (shown in FIG. 5E) attached to the second surface is configured to measure flow information of a second fluid line coupled thereto. The second data conducting element, the second electrical conducting element, and the second electronic flow sensor port are also coupled to the processor.

[0082] FIG. 5E depicts an example sensor system configured to couple two or more pump modules, according to aspects of the subject technology. FIG. 5E illustrates coupling between the microprocessor of the wedge sensor 540 and various connectors and ports. In some implementations, the first IUI connector 548 and the first electronic flow sensor 546 are both mounted on the first major surface 544 of the housing 542 and coupled to the microprocessor. The microprocessor of the wedge sensor 540 is also coupled to the second IUI connector 554 (mounted on the second major surface of the housing 542) and the second electronic flow sensor 556. Storage memory or other memory is also coupled to the microprocessor. In other words, the wedge sensor 540 includes two sensors (one on each side of the wedge sensor 540) and is configured to couple to two PCUs (one on each side of the wedge).

[0083] In one aspect, an integrated intravenous (IV) administration set includes a flow stop having a tube fitting and a housing configured to prevent fluid flow through the tube in a first position and to allow fluid flow through the tube in a second position, the tube fitting having a protrusion configured to receive the tube. The IV administration set also includes an electronic flow sensor disposed within the housing configured to measure fluid flow through the tube and one or more conductive connections configured within the housing and configured to provide power to the electronic flow sensor. The flow stop is configured to be mounted and engaged with a receptacle of an infusion device, and when mounted and engaged, the one or more conductive connections are configured to engage corresponding conductive connections provided by the infusion device to activate the electronic flow sensor based on power flow from the infusion device.

[0084] In some implementations, the integrated intravenous (IV) administration set further includes a control circuit configured to send a control signal to the infusion device to modify the flow rate generated by the pump mechanism of the infusion device. In some implementations, the electronic flow sensor further includes a data communication component. One or more conductive connections are disposed on the exterior of the housing, and the infusion device is configured with a corresponding one or more conductive connections, such that during use of the integrated IV administration set, the one or more conductive connections are in electrical contact with the corresponding one or more conductive connections, and the electronic flow sensor is in electrical communication to transmit data to the infusion device using the data communication component.

[0085] In some implementations, the housing includes a recess and the one or more conductive connections are vertically aligned within the recess. In some implementations, the one or more conductive connections include a spring-loaded pogo pin connector. In some implementations, the one or more conductive connections include a resilient plastic conductor material. In some implementations, the tube fitment has a shape complementary to a feature molded into the housing of the infusion device such that when the integrated IV administration set is mounted and engaged to the infusion device, the tube fitment is configured to align the flow stop with respect to the infusion device.

[0086] In some implementations, the integrated IV administration set further includes a wireless communications module, hi some implementations, the integrated IV administration set is configured to wirelessly upload data measured by the electronic flow sensor to a server system that monitors operation of the infusion device.

[0087] In some implementations, the integrated IV administration set is configured to wirelessly transfer data measured by the electronic flow sensor to the infusion device.

[0088] In some implementations, the one or more conductive connections include an inductive coupling component configured for wireless power transfer from the infusion device to the electronic flow sensor.

[0089] In some implementations, the integrated IV administration set further includes a non-volatile memory component that stores an identification of the integrated IV administration set. In some implementations, the non-volatile memory component stores information about a manufacturing date of the integrated IV administration set, and the infusion device is configured to check the identification and manufacturing date of the integrated IV administration set before beginning the infusion process.

[0090] In some implementations, the non-volatile memory component stores information that is transmitted to the infusion device, the information indicating how long the integrated IV administration set has been in use.

[0091] In some implementations, the flow stop includes a slider component mounted to and positioned at an orthogonal angle to the tube fitting, the slider component configured to slide relative to the tube fitting and engage tubing connected to the tube fitting to prevent fluid flow in the tubing when the IV administration set is removed from the infusion device and to allow fluid flow in the tubing when the IV administration set is mounted to and engaged with the infusion device.

[0092] In some implementations, the tube fitting and housing are configured to be received in an upper portion of the infusion device, the upper portion of the infusion device being above a pump mechanism of the infusion device, and the flow stop is configured to be received in a lower portion of the infusion device, the lower portion of the infusion device being below the pump mechanism of the infusion device.

[0093] In some implementations, the flow sensor is configured to send a control signal to the infusion device after the integrated IV administration set has been in use for a predetermined period of time.

[0094] In some implementations, the IV administration set further includes a processor configured to determine a period of time the integrated IV administration set has been in use based on the length of time the integrated IV administration set receives power from the infusion device through the one or more conductive connections.

[0095] In another aspect, the sensor system includes a first plurality of conductive connections, a data port for receiving data recorded by an electronic flow sensor of an integrated intravenous (IV) administration set, the integrated IV administration set including a second plurality of conductive connections configured to interface with the first plurality of conductive connections when the integrated IV administration set is engaged with the sensor system, and the sensor system configured to provide a control signal to an infusion device based on the data recorded by the electronic flow sensor to maintain fluid flow through the integrated IV administration set at a desired flow rate.

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

[0097] The term "software" is intended to include, where appropriate, firmware resident in read-only memory or applications stored in magnetic storage that can be loaded into memory for processing by a processor. Also, in some implementations, the software aspects of the subject disclosure can be implemented as sub-portions of a larger program while remaining separate software aspects of the subject disclosure. In some implementations, the software aspects can also be implemented as separate programs. Finally, any combination of separate programs that together embody the software aspects described herein is within the scope of the subject disclosure. In some implementations, the software programs, when installed for operation on one or more electronic systems, define one or more unique machine implementations that execute and perform the operations of the software programs.

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

[0099] FIG. 6 is a conceptual diagram illustrating an example electronic system 600 for sensing and controlling liquid flow in an injection process, according to aspects of the subject technology. The electronic system 600 may be a computing device for execution of one or more portions or steps of the process 600, or software associated with the components and processes provided by FIGS. 1-6, including, but not limited to, the information system server 30, or computing hardware in the patient care device 12. The electronic system 600 may be depicted in combination with the disclosure with respect to FIGS. 1-6. In this regard, the electronic system 600 may be a personal computer or mobile device, such as a smartphone, a tablet computer, a laptop, a PDA, an augmented reality device, a wearable such as a watch or band or glasses, or a combination thereof, or other touch screen or television with one or more processors embedded or coupled thereto, or any other type of computer-related electronic device with a network connection.

[0100] The electronic system 600 may include various types of computer readable media and interfaces for various other types of computer readable media. In the depicted example, the electronic system 600 includes a bus 608, a processing unit 612, a system memory 604, a read only memory (ROM) 610, a permanent storage device 602, an input device interface 614, an output device interface 606, and one or more network interfaces 616. In some implementations, the electronic system 600 may include or be integrated with other computing devices or circuitry for operation of the various components and processes described above.

[0101] The bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect numerous internal devices of the electronic system 600. For example, the bus 608 communicatively connects the processing unit 612 with the ROM 610, the system memory 604, and the permanent storage device 602.

[0102] From these various memory units, the processing unit 612 retrieves instructions to execute and data to process in order to perform the processes of the subject disclosure. The processing unit can be a single processor or a multi-core processor in different implementations.

[0103] The ROM 610 stores static data and instructions required by the processing unit 612 and other modules of the electronic system. The permanent storage device 602, on the other hand, is a read-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 600 is stopped. Some implementations of the subject disclosure use a mass storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 602.

[0104] Other implementations use a removable storage device (such as a floppy disk, flash drive, and its corresponding disk drive) as the permanent storage device 602. Like the permanent storage device 602, the system memory 604 is a read-write memory device. Yet, unlike the storage device 602, the system memory 604 is a volatile read-write memory, such as a random access memory. The system memory 604 stores some of the instructions and data that the processor needs at run time. In some implementations, the processes of the subject disclosure are stored in the system memory 604, the permanent storage device 602, and / or the ROM 610. From these various memory units, the processing unit 612 retrieves instructions to execute and data to process in order to execute the processes of some implementations.

[0105] The bus 608 also connects to input and output device interfaces 614 and 606. The input device interface 614 allows a user to communicate information and select commands to the electronic system. Input devices used with the input device interface 614 include, for example, alphanumeric keyboards and pointing devices (also called "cursor control devices"). The output device interface 606 allows, for example, the display of images generated by the electronic system 600. Output devices used with the output device interface 606 include, for example, printers and display devices such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some implementations include devices such as touch screens that function as both input and output devices.

[0106] 6, the bus 608 also couples the electronic system 600 to a network (not shown) through a network interface 616. The network interface 616 can include, for example, a wireless access point (e.g., Bluetooth or WiFi) or radio circuitry for connecting to a wireless access point. The network interface 616 can also include hardware (e.g., Ethernet hardware) for connecting the computer to a portion of a network of computers, such as a local area network ("LAN"), a wide area network ("WAN"), a wireless LAN, or an intranet, or a network of networks, such as the Internet. Any or all of the components of the electronic system 600 can be used in conjunction with the subject disclosure.

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

[0108] Some implementations include electronic components, such as a microprocessor, storage, and memory, that store computer program instructions on a machine-readable or computer-readable medium (also referred to as a computer-readable storage medium, machine-readable media, or machine-readable storage medium). Some examples of such computer-readable media include RAM, ROM, read-only compact disks (CD-ROMs), recordable compact disks (CD-Rs), rewritable compact disks (CD-RWs), read-only digital versatile disks (e.g., DVD-ROMs, dual-layer DVD-ROMs), various recordable / rewritable DVDs (e.g., DVD-RAMs, DVD-RWs, DVD+RWs, etc.), flash memory (e.g., SD cards, mini SD cards, micro SD cards, etc.), magnetic and / or solid state hard drives, read-only and recordable Blu-ray® disks, extra-high density optical disks, any other optical or magnetic medium, and floppy disks. The computer-readable medium may store a computer program executable by at least one processing unit and including a set of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as produced by a compiler, and files containing higher level code that is executed by a computer, electronic component, or microprocessor using an interpreter.

[0109] Although the above discussion has primarily referred to microprocessors or multi-core processors executing software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions stored on the circuitry itself.

[0110] As used herein and in any claims of this application, the terms "computer", "server", "processor", and "memory" all refer to electronic or other technological devices. These terms exclude people or groups of people. For purposes of this specification, the terms display or displaying mean displaying on an electronic device. As used herein and in any claims of this application, the terms "computer readable medium" and "computer readable media" are strictly restricted to tangible physical objects that store information in a computer readable format. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.

[0111] To provide for user interaction, implementations of the subject matter described herein can be implemented on a computer having a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to a user, and a keyboard and pointing device, such as a mouse or track ball, for allowing a user to provide input to the computer. Other types of devices can be used to provide for user interaction as well, e.g., feedback provided to the user can be in the form of any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback, and input from the user can be received in any form, including acoustic, speech, or tactile input. Additionally, a computer can interact with a user by sending documents to and receiving documents from a device used by the user, e.g., by sending a web page to a web browser on the user's client device in response to a request received from the web browser.

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

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

[0114] As used herein, a "user interface" (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 to receive input signals or provide electronic information and / or to provide information to a user in response to any received input signals. The control elements may include dials, buttons, icons, selectable areas, or other perceptible indicia presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiates data exchange 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™, C, C++, Web Services, or Rich Site Summary (RSS). In some implementations, the UI may be included in a stand-alone 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 to and from the communicating medical device or a server.

[0115] As used herein, the term "determining" or "determining" encompasses a wide variety of actions. 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, and the like, through a hardware element without user intervention. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like, through a hardware element without user intervention. "Determining" can include resolving, selecting, choosing, establishing, and the like, through a hardware element without user intervention.

[0116] As used herein, the terms "providing" or "providing" encompass a wide variety of actions. For example, "providing" can include storing a value in a 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, and the like. "Providing" can also include encoding, decoding, encrypting, decrypting, validating, verifying, and the like via a hardware element.

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

[0118] In any implementation, the generated or detected data can 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, the remote location can be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Thus, when one item is indicated as being "remote" from another item, what is meant is that the two items can be in the same room but separated, or at least in different rooms or different buildings, and can be at least 1.6 kilometers (1 mile), 16 kilometers (10 miles), or at least 160 kilometers (100 miles) apart. "Communicating" information refers to transmitting data representing this information as electrical signals over an appropriate communication channel (e.g., a private or public network). "Transmitting" an item refers to any means of bringing the item, or any other, from one location to the next by physically transporting the item (if possible), including, at least in the case of data, physically transporting the medium that carries or communicates the data. Examples of communication media include radio or infrared transmission channels, as well as network connections to other computers or networked devices, and the Internet, or email transmissions, and information stored on websites, and the like.

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

[0120] It is understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of a sample approach. It is understood that the specific order or hierarchy of steps in the processes may be rearranged based on design preferences. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sampling order, and are not intended to be limited to the specific order or hierarchy presented.

[0121] Demonstration of the subject's technique as a section

[0122] Various examples of aspects of the present disclosure are described for convenience as numbered sections (1, 2, 3, etc.). These are provided as examples and do not limit the subject technology. Figure and reference number identification is provided below merely as examples and for illustration, and the sections are not limited by these identifications.

[0123] Clause 1. An integrated intravenous (IV) administration set, comprising: a flow stop having a tube fitting and a housing, the flow stop configured to prevent fluid flow through the tube in a first position and to allow fluid flow through the tube in a second position, the tube fitting having a protrusion configured to receive the tube; an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure a flow of fluid through the tube; and one or more conductive connections configured within the housing and configured to provide power to the electronic flow sensor, the flow stop being configured to be mounted and engaged with a receptacle of an infusion device, the one or more conductive connections being configured to engage corresponding conductive connections provided by the infusion device when mounted and engaged to activate the electronic flow sensor based on a flow of power from the infusion device.

[0124] Clause 2. The integrated IV administration set of clause 1, further comprising a control circuit configured to send a control signal to the infusion device to modify the flow rate produced by the pump mechanism of the infusion device.

[0125] Clause 3. An integrated IV administration set as described in any of clauses 1 to 2, wherein the electronic flow sensor further has a data communication component, wherein the one or more conductive connections are disposed external to the housing, and wherein the infusion device is configured with corresponding one or more conductive connections, such that during use of the integrated IV administration set, the one or more conductive connections are in electrical contact with the corresponding one or more conductive connections, and the electronic flow sensor is in electrical communication to transmit data to the infusion device using the data communication component.

[0126] Clause 4. The integrated IV administration set of clause 3, wherein the one or more conductive connections have a spring-loaded pogo pin connector.

[0127] Clause 5. The integrated IV administration set of clause 3, wherein the one or more conductive connections have a resilient plastic conductor material.

[0128] Clause 6. The integrated IV administration set of clause 3, wherein the tube fitting has a shape complementary to a feature molded into the housing of the infusion device such that when the integrated IV administration set is mounted to and engaged with the infusion device, the tube fitting is configured to align the flow stop with respect to the infusion device.

[0129] Clause 7. The integrated IV administration set of any of clauses 1 to 6, further comprising a wireless communications module, wherein the integrated IV administration set is configured to wirelessly upload data measured by the electronic flow sensor to a server system that monitors operation of the infusion device.

[0130] Clause 8. The integrated IV administration set of any of clauses 1 to 7, further comprising a wireless communications module, wherein the integrated IV administration set is configured to wirelessly transfer data measured by the electronic flow sensor to an infusion device.

[0131] Clause 9. The integrated IV administration set of any of clauses 1 to 8, wherein the one or more conductive connections have an inductive coupling component configured for wireless power transfer from the infusion device to the electronic flow sensor.

[0132] Clause 10. The integrated IV administration set of any of clauses 1 to 9, further comprising a non-volatile memory component that stores an identification of the integrated IV administration set.

[0133] Clause 11. The integrated IV administration set of clause 10, wherein the non-volatile memory component stores information that is transmitted to the infusion device, the information indicating how long the integrated IV administration set has been in use.

[0134] Clause 12. The integrated IV administration set of any of clauses 1 to 11, wherein the flow stop has a slider component mounted to and positioned at a right angle to the tube fitting, the slider component configured to slide relative to the tube fitting and engage tubing connected to the tube fitting to prevent fluid flow in the tubing when the IV administration set is removed from the infusion device and to allow fluid flow in the tubing when the IV administration set is mounted to and engaged with the infusion device.

[0135] Clause 13. An integrated IV administration set as described in any of clauses 1 to 12, wherein the tube fitting and housing are configured to be received in an upper portion of the infusion device, the upper portion of the infusion device being above a pump mechanism of the infusion device, and the flow stop is configured to be received in a lower portion of the infusion device, the lower portion of the infusion device being below the pump mechanism of the infusion device.

[0136] Clause 14. The integrated IV administration set of any of clauses 1 to 13, wherein the electronic flow sensor is configured to send a control signal to the infusion device after the integrated IV administration set has been used for a predetermined period of time.

[0137] Clause 15. A device comprising: a housing having a first surface and a second surface; a processor disposed within the housing, the first surface comprising a first inter-unit interface connector mounted on the first surface of the housing, the first inter-unit interface connector including a first data conducting element for transferring first data and a first electrical conducting element for transferring first power; and a first electronic flow sensor configured to measure flow information of a coupled first fluid line, the first data conducting element, the first electrical conducting element, and the first electronic flow sensor being coupled to the processor. a second inter-unit interface connector mounted on a second surface of the housing, the second inter-unit interface connector including a second data conducting element for transferring second data and a second electrically conducting element for transferring second power, and a second electronic flow sensor configured to measure flow information of an associated second fluid line, the second data conducting element, the second electrically conducting element, and the second electronic flow sensor being coupled to a processor.

[0138] Clause 16. The sensor system of clause 15, wherein the first inter-unit interface connector includes a mounting element for mounting to a corresponding interface connector of the infusion device, the infusion device having a predetermined length, and the first surface of the housing has a length that exceeds the predetermined length such that the first electronic flow sensor can extend from the first surface below or above the infusion device.

[0139] Clause 17. A sensor system as described in any of clauses 15 and 16, wherein the first inter-unit interface connector includes a mounting element for mounting to a corresponding interface connector of the infusion device, and wherein first power is received from the infusion device and first data is transferred between the sensor system and the infusion device.

[0140] Clause 18. A sensor system as described in any of clauses 15 and 16, wherein the first inter-unit interface connector includes a mounting element for mounting to a corresponding interface connector of a first infusion device and the second inter-unit interface connector includes a second mounting element for mounting to a corresponding interface connector of a second infusion device.

[0141] Clause 19. The sensor system of clause 18, wherein a first power is received from the first infusion device, and first data is transferred between the sensor system and the first infusion device, a second power includes at least a portion of the first power, the second power is transmitted to the second infusion device, and the second data includes at least a portion of the first data, and the second data is transferred between the sensor system and the second infusion device.

[0142] Clause 20. A device comprising: a housing having a first surface and a second surface; and a processor disposed within the housing, the first surface comprising: a first inter-unit interface connector mounted to the first surface of the housing, the first inter-unit interface connector including a first data conducting element for transferring first data and a first electrical conducting element for transferring first power; and a first electronic flow sensor port configured to receive flow information of a first fluid line from a coupled first electronic flow sensor, the first data conducting element, the first electrical conducting element, and the first electronic flow sensor port being coupled to the processor; A sensor system including a first electronic flow sensor port, a second inter-unit interface connector mounted to a second surface of the housing, the second inter-unit interface connector including a second data conducting element for transferring second data and a second electrical conducting element for transferring second power, and a second electronic flow sensor port configured to receive flow information of the second fluid line from a coupled second electronic flow sensor, the second data conducting element, the second electrical conducting element, and the second electronic flow sensor port being coupled to a processor.

[0143] Further considerations

[0144] It is understood that the specific order or hierarchy of steps in the disclosed processes is an illustration of a sample approach. It is understood that the specific order or hierarchy of steps in the processes may be rearranged based on design preferences. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sampling order, and are not intended to be limited to the specific order or hierarchy presented.

[0145] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The preceding description provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects set forth herein, but are intended to give full scope consistent with the claims in their language, and references to elements in the singular are not intended to mean "one and only one" unless specifically so stated, but rather "one or more." The term "some" refers to one or more, unless specifically stated otherwise. Masculine pronouns (e.g., his) include feminine and neuter genders (e.g., her and its), and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

[0146] The term website as used herein can include any aspect of a website, including one or more web pages, one or more servers used to host or store web-related content, and the like. Thus, the term website can be used interchangeably with the terms web page and server. The predicates "configured to," "operable to," and "programmed to" do not imply any particular tangible or intangible modification of the subject matter, but rather are intended to be used interchangeably. For example, a processor configured to monitor and control operations or components can also mean a processor programmed to monitor and control operations, or a processor operable to monitor and control operations. In the same manner, a processor configured to execute code can be interpreted as a processor programmed to execute code or operable to execute code.

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

[0148] A phrase such as "aspects" does not imply that such aspects are essential to the subject technology, nor that such aspects apply to all configurations of the subject technology. Disclosure regarding an aspect may apply to all configurations, or to one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects, and vice versa. A phrase such as "implementation" does not imply that such implementation is essential to the subject technology, nor that such implementation applies to all configurations of the subject technology. Disclosure regarding an implementation may apply to all implementations, or to one or more implementations. An implementation may provide one or more examples. A phrase such as an "implementation" may refer to one or more implementations, and vice versa. A phrase such as "configuration" does not imply that such configuration is essential to the subject technology, nor that such configuration applies to all configurations of the subject technology. Disclosure regarding a configuration may apply to all configurations, or to one or more configurations. A configuration may provide one or more examples. A phrase such as "a configuration" can refer to one or more configurations, and vice versa.

Claims

1. 1. An integrated intravenous (IV) administration set, comprising: a flow stop having a tube fitment and a housing, the flow stop configured to prevent flow of a fluid through a tube in a first position and to allow the flow of the fluid through the tube in a second position, the tube fitment having a protrusion configured to receive the tube; an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure the flow of the fluid within the tube; a closed loop circuit for controlling the flow rate of the fluid; one or more conductive connections configured within the housing and configured to provide power to the electronic flow sensor; having the flow stop is configured to be mounted and engaged with a receptacle of an infusion device, and when mounted and engaged, the one or more conductive connections are configured to engage corresponding conductive connections provided by the infusion device, thereby powering the electronic flow sensor based on power flow from the infusion device; and an integrated intravenous (IV) administration set, the flow stop having a slider component mounted to the tube fitting and positioned perpendicular to the tube fitting, the slider component configured to slide relative to the tube fitting to engage a portion of the tubing connected to the tube fitting to prevent the flow of fluid in the tubing when the integrated IV administration set is removed from the infusion device and to allow the flow of fluid in the tubing when the integrated IV administration set is mounted to and engaged with the infusion device.

2. 10. The integrated IV administration set of claim 1, further comprising a control circuit configured to send a control signal to the infusion device to modify the flow rate of the fluid produced by a pump mechanism of the infusion device.

3. The electronic flow sensor further comprises a data communication component, the one or more conductive connections being disposed external to the housing, and the infusion device being configured with a corresponding one or more conductive connections, whereby during use of the integrated IV administration set: the one or more conductive connections are in electrical contact with the corresponding one or more conductive connections; and the electronic flow sensor is in electrical communication with the infusion device to transmit data using the data communication component; 10. The integrated IV administration set of claim 1.

4. The integrated IV administration set of claim 3 , wherein the one or more conductive connections include a spring-loaded pogo pin connector.

5. The integrated IV administration set of claim 3 , wherein the one or more conductive connections comprise a resilient plastic conductor material.

6. 4. The integrated IV administration set of claim 3, wherein the tube fitting has a shape complementary to a feature molded into the housing of the infusion device, whereby the tube fitting is configured to align the flow stop with respect to the infusion device when the integrated IV administration set is mounted and engaged to the infusion device.

7. 10. The integrated IV administration set of claim 1, further comprising a wireless communication module, wherein the integrated IV administration set is configured to wirelessly upload data measured by the electronic flow sensor to a server system that monitors operation of the infusion device.

8. 10. The integrated IV administration set of claim 1, further comprising a wireless communication module, wherein the integrated IV administration set is configured to wirelessly transfer data measured by the electronic flow sensor to the infusion device.

9. 10. The integrated IV administration set of claim 1, wherein the one or more conductive connections include an inductive coupling component configured for wireless power transfer from the infusion device to the electronic flow sensor.

10. 10. The integrated IV administration set of claim 1, further comprising a non-volatile memory component that stores an identification of the integrated IV administration set.

11. 11. The integrated IV administration set of claim 10, wherein the non-volatile memory component stores information that is transmitted to the infusion device, the information indicating how long the integrated IV administration set has been in use.

12. 2. The integrated IV administration set of claim 1, wherein the tube is configured to be received in an upper portion of the infusion device when the flow stop is mounted and engaged in the receptacle of the infusion device, the upper portion of the infusion device being above a pump mechanism of the infusion device, and the flow stop is configured to be received in a lower portion of the infusion device, the lower portion of the infusion device being below the pump mechanism of the infusion device.

13. The integrated IV administration set of claim 1 , wherein the electronic flow sensor is configured to send a control signal to the infusion device after the integrated IV administration set has been in use for a predetermined period of time.

Images