Integrated liquid flow closed loop sensing and control

Abstract

Integrated liquid flow closed loop sensing and control are disclosed. An integrated intravenous (IV) applicator includes a flow stop having a conduit adapter including a protrusion configured to receive a conduit and a housing, the flow stop configured to, in a first position, prevent fluid flow through the conduit and, in a second position, allow fluid flow through the conduit. The IV applicator also includes an electron flow sensor disposed within the housing, the electron flow sensor configured to measure a flow of the fluid in the conduit, and one or more electrically conductive connections configured within the housing and configured to provide electrical power to the electron flow sensor. The flow stop is shaped to be loaded and engaged to a container of an infusion device and to engage one or more electrically conductive connections with corresponding electrically conductive connections provided by the infusion device when loaded and engaged to activate the flow sensor based on a power flow from the infusion device.

Description

[0001] This application is a continuation-in-part of patent application number “202180041786X” filed May 26, 2021, entitled “Integrated Liquid Flow Closed Loop Sensing and Control.”

[0002] Cross Reference to Related Applications

[0003] This application is a non-provisional of U.S. Provisional Application Serial No. 63 / 030,234, filed May 26, 2020, entitled “INTEGRATED LIQUID FLOW CLOSED LOOP SENSING AND CONTROL,” the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0004] This application relates generally to sensing and controlling liquid flow during an infusion process. BACKGROUND

[0005] Infusion pumps typically monitor the flow rate of fluids being dispensed. There is a desire to improve the efficiency, sensitivity, and accuracy of infusion pumps to sense and control liquid flow with a wide range of dynamic flow rates during an infusion process. SUMMARY

[0006] Excessive infusion of therapeutic fluid occurs when there is a discrepancy between a target flow rate setting at an infusion device and the actual flow rate of therapeutic fluid being administered through an intravenous (IV) administration set and infused to a patient.

[0007] Accordingly, there is a desire to improve the efficiency, sensitivity, and accuracy of detection of over-infusion or under-infusion. IV administration sets are typically single-use disposable consumables for an infusion process. As such, they typically do not contain sensors or other electronics to monitor or control fluid flow. The IV devices 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 embodiments, the flow stop can be referred to as a flow clamp, safety clamp, or slide clamp. The devices and methods described herein provide closed loop flow control for an infusion pump that monitors the actual flow rate and adjusts the pump or alerts the user of any deviation from the set flow rate under normal operation or fault conditions.

[0008] The disclosed subject matter relates to an integrated intravenous (IV) administration set that includes a tubing adapter comprising a protrusion configured to receive tubing of an IV administration set. The device includes a housing coupled to the tubing adapter; an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure fluid flow in the tubing. The device includes one or more conductive connections configured to provide electrical power to the electronic flow sensor and transmit data; and a flow stop configured to, in a first position, prevent fluid flow through the tubing, and in a second position, allow fluid flow through the tubing. The tubing adapter is shaped to be loaded and engaged to an infusion device configured with a corresponding receptacle for holding the housing in alignment with respect to the infusion device.

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

[0010] In another aspect, a sensor system includes a first plurality of conductive connections; a data port to receive data recorded by an electronic flow sensor of an integrated intravenous (IV) administration set, wherein the integrated IV administration set includes 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 is configured to provide control signals to an infusion device based on the data recorded by the electronic flow sensor to maintain the flow of fluid through the integrated IV administration set at a desired flow rate.

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

[0012] For a better understanding of the various described implementations, reference should be made to the Description of the Embodiments below in conjunction with the following drawings. In the drawings and description below, like numerals are used to refer to like parts throughout several figures.

[0013] Figure 1 An example of a healthcare organization's institutional patient care system is depicted in accordance with aspects of the subject technology.

[0014] Figure 2An example of an integrated administration set and infusion pump according to aspects of the subject technology is depicted.

[0015] Figure 3 An enlarged view of an integrated administration set and infusion pump according to aspects of the subject technology is depicted.

[0016] Figure 4A A first perspective view of an integrated flow stop system according to aspects of the subject technology is depicted.

[0017] Figure 4B A second perspective view of an integrated flow stop system according to aspects of the subject technology is depicted.

[0018] Figure 4C A third perspective view of an integrated flow stop system according to aspects of the subject technology is depicted.

[0019] Figure 5A An example sensor system adapted to an infusion device according to aspects of the subject technology is depicted.

[0020] Figure 5B An example sensor system including a device having a port for receiving a flow sensor according to aspects of the subject technology is depicted.

[0021] Figure 5C An example sensor system configured to couple more than one sensor and more than one pump module according to aspects of the subject technology is depicted.

[0022] Figure 5D An example sensor system according to aspects of the subject technology is depicted.

[0023] Figure 5E An example sensor system configured to couple more than one pump module according to aspects of the subject technology is depicted.

[0024] Figure 6 is a conceptual diagram showing an example system for sensing and controlling liquid flow during an infusion process according to aspects of the subject technology. DETAILED DESCRIPTION

[0025] Reference will now be made to implementations, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide an understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations can 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.

[0026] It is desirable to more accurately monitor fluid flow during an infusion procedure. Unregulated flow of therapeutic fluid, such as over-infusion and under-infusion, occurs when there is a difference between a target flow rate set at an infusion device and an actual flow rate of therapeutic fluid administered through an IV administration set and infused to a patient.

[0027] The devices and methods described herein provide integrated IV administration sets that include electronic sensing and control of fluid flow.

[0028] Figure 1 An example of a healthcare organization's institutional patient care system 100 is depicted in accordance with aspects of the subject technology. In Figure 1 In the depicted example, patient care devices (or generally "medical devices") 12 are connected to a hospital network 10. The term patient care device (or "PCD") can be used interchangeably with the term patient care unit (or "PCU"), either of which can include various ancillary medical devices such as infusion pumps, vital signs monitors, medication dispensing devices (e.g., cabinets, carts), medication preparation devices, automated dispensing 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 through a transmission channel 31. Transmission channel 31 is any wired or wireless transmission channel, for example, an 802.11 wireless local area network (LAN). In some embodiments, network 10 also includes computer systems located in various departments throughout the hospital. For example, Figure 1 Network 10 can optionally include computer systems associated with an admissions department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, and / or a medical decision support system. As described further below, network 10 can include discrete sub-networks. In the depicted example, healthcare network 10 includes a device network 41 through which patient care devices 12 (and other devices) communicate in accordance with normal operations.

[0029] Additionally, institutional patient care system 100 can include a separate information system server 130, the functions of which will be described in greater detail below. Furthermore, although information system server 130 is shown as a separate server, the functions and programming of information system server 130 can be incorporated into another computer if the engineers designing the institutional information system so desire. Institutional patient care system 100 can also include one or more device terminals 132 for connecting and communicating with information system server 130. Device terminals 132 can include personal computers, personal data assistants, mobile devices (such as laptops, tablets, augmented reality devices, or smartphones) configured with software for communicating with information system server 130 via network 10.

[0030] 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 this purpose. The patient care device 12 can include or incorporate pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy devices, and other drug delivery devices that can be used in accordance with the teachings set forth herein. In the depicted example, the patient care device 12 includes a control module 14, also referred to as an interface unit 14, that is 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 (e.g., 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 (although not necessarily) includes a primary nonvolatile storage unit 56 (such as a hard disk drive or nonvolatile flash memory) for storing software and data, and one or more internal buses 64 for interconnecting the aforementioned elements.

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

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

[0033] The functional modules 116, 118, 120, 122 are any devices used to provide care to a patient or to monitor a patient's condition. As shown, at least one of the functional modules 116, 118, 120, 122 can be an infusion pump module for delivering medication or other fluids to a patient, such as an intravenous infusion pump. For purposes of this discussion, the functional module 116 is an infusion pump module. Each of the functional modules 118, 120, 122 can 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, among others. The functional modules 118, 120 and / or 122 can be a printer, a scanner, a bar code reader or any other peripheral input, output or input / output device. Figure 1

[0034] Each of the functional modules 116, 118, 120, 122 communicates directly or indirectly with the interface unit 14, with the interface unit 14 providing overall monitoring and control of the device 12. As shown, the functional modules 116, 118, 120, 122 are connected to the interface unit 14 through a network connection 52, which can be a wired or wireless connection, such as through an Ethernet, WiFi, BLUETOOTH, Integrated Services Digital Network (ISDN) connection, Digital Subscriber Line (DSL) modem or cable modem. Any direct or indirect network connection can be used, including but not limited to a telephone modem, MIB system, RS232 interface, auxiliary interface, optical link, infrared link, radio frequency link, microwave link or WLANS connection or other wireless connection. Figure 1 ​The functional modules 116, 118, 120, 122 can be physically and electronically connected in series to one or both ends of the interface unit 14, as shown, or as detailed by Eggers et al. However, it is recognized that other means for connecting functional modules with an interface unit exist, and these can be used without departing from the subject technology. It will also be appreciated that a device that provides sufficient programmability and connectivity, such as a pump or patient monitoring device, can be capable of operating as a standalone device and can communicate directly with the network without being connected through a separate interface unit or control unit 14. As noted above, additional medical devices or peripherals can be connected to the patient care device 12 through one or more auxiliary interfaces 62.

[0035] Each functional module 116, 118, 120, 122 can include module-specific components 76, a microprocessor 70, volatile memory 72, and non-volatile memory 74 for storing information. It should be noted that, while Figure 1 While four functional modules are shown in FIG. 1, any number of devices can be connected directly or indirectly to the central controller 14. The number and type of functional modules described herein are intended to be illustrative and in no way limit the scope of the subject technology. The module-specific components 76 include any components necessary to operate a particular module, such as a pumping mechanism for the infusion pump module 116.

[0036] While each functional module can be capable of at least some degree of independent operation, the interface unit 14 monitors and controls the overall operation of the device 12. For example, as will be described in greater detail below, the interface unit 14 provides programming instructions to the functional modules 116, 118, 120, 122 and monitors the status of each module.

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

[0038] Medical devices incorporating aspects of the subject technology can be equipped with a network interface module (NIM) to allow the medical device to participate as a node in the network. While the subject technology will be described for purposes of clarity in an Ethernet network environment using Internet Protocols (IP), it is understood that the concepts of the subject technology are equally applicable to other network environments and such environments are intended to be within the scope of the subject technology.

[0039] Data from various data sources can be converted into network compatible data using existing technology, and information movement between the medical devices and the network can be accomplished through various means. For example, patient care devices 12 and network 10 can communicate via 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), or through RS232 links, MIB systems, RF links such as BLUETOOTH, IR links, WLANS, digital cable systems, telephone modems, or other wired or wireless communication means. Manual interaction between patient care devices 12 and network 10 involves physically, intermittently, or periodically transferring data between the systems using, for example, user interface devices 54, coded data input devices 60, bar codes, computer disks, portable data assistants, memory cards, or any other medium for storing data. The means of communication in various aspects is bidirectional, where data is accessed from points of as many distributed data sources as possible. Decision making can occur at various places within network 10. For example, and not by way of limitation, decisions can be made at HIS server 30, decision support 48, remote data server 49, hospital department or unit stations 46, or within patient care devices 12 themselves. Figure 1

[0040] All direct communication with medical devices operating on the network in accordance with the subject technology can be performed through an information system server 30, referred to as a remote data server (RDS). In accordance with aspects of the subject technology, a network interface module incorporated into a medical device, such as, for example, an infusion pump or a vital signs measurement device, ignores all network traffic not originating from an authenticated RDS. The primary responsibility of the RDS of the subject technology is to keep track of the location and status of all networked medical devices with NIMs and to maintain open communication.

[0041] Figure 2 An example of an integrated administration set and infusion pump in accordance with aspects of the subject technology is depicted. In some implementations, the administration set 200 includes an integrated flow stop system 202. The integrated flow control system 202 provides closed loop control and flow sensing in addition to functioning as a mechanical flow stop device. Figures 4A-4C ​Different views of the integrated flow stop system 202 are provided. IV administration sets are typically single-use disposable consumables. As such, they typically do not contain sensors or other electronics to monitor or control fluid flow. In contrast, the integrated IV set 200 includes liquid sensing capabilities and closed loop flow control circuitry that improves the accuracy and efficiency of sensing flow directly at the administration set and improves overall control of flow based at least in part on the sensed values.

[0042] A closed loop control system (or feedback control system) can automatically adjust a process variable to a desired set point with limited or in some cases no human interaction. The control circuitry in the integrated flow stop system 202 detects the flow of an infusion process by generating control messages to adjust one or more elements of the patient care device. The control messages can be generated based on a comparison of the set (e.g., desired) flow provided at the infusion pump to the detected flow of the infusion pump. A closed loop control system includes one or more feedback loops between its output value and its input value. The closed loop control system can generate an error signal that reflects the difference between its output value (e.g., the flow measured by the flow sensor) and its reference input value (e.g., the set flow provided at the infusion pump), and the control messages generated by the closed loop control system are dependent on the output value. For example, the control signals sent by the control circuitry change the operating parameters of the infusion pump in order to bring the measured flow as close as possible to the set (e.g., desired) flow.

[0043] Figure 2 An administration set 200 coupled to a large volume pump (LVP) 250 is depicted. 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 tubing fitting container 254, and a pumping mechanism 256. The LVP 250 also includes a molded feature 260 having a shape that is complementary to a corresponding portion of the integrated flow stop system 202. In this way, the molded feature 260 ensures a snug fit of the integrated flow stop system 202 when the IV administration set 200 is loaded into and engaged with the pump 250.

[0044] A first plurality of electrically conductive connections 258 (e.g., wires) on the pump 250 Figure 2The four different electrically conductive connections) allow for the flow of electricity and data between the pump 250 and the integrated flow stop system 202 when the integrated IV administration set 200 is loaded into and engaged with the pump 250. Each electrically conductive connection 258 can be formed from the same material or different materials depending on the electrically conductive path formed. For example, the electrically conductive connection for power can be formed from a metal or other material for conducting electricity, while the data connection can be formed from a metal or fiber optic electrically conductive material to form a data pathway. The pump 250 also includes a holder 264 to secure 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 various attached modules.

[0045] The receiving portion 262 in the pump 250 defines a slot into which the tubing adapter 222 of the integrated flow stop system 202 is loaded. The flow stop 210 is coupled to and positioned below the tubing adapter 222. As referenced above, the flow stop 210 is configured to slide between two positions. Figures 4A-4C As explained in more detail, the flow stop 210 is configured to slide between two positions.

[0046] In the first position (open position), the flow stop 210 is aligned with the tubing adapter 222 (as shown in FIG. 2A) and the flow of fluid in the tubing 214 is not obstructed. In the second position (closed position), the flow stop 210 is slid toward the tubing 214 to protrude below the tubing adapter 222 and mechanically clamps the tubing 214 to block the flow of fluid. Figure 4B

[0047] In some embodiments, the flow stop 210 is in the open position when the administration set 200 is loaded into the pump 250. During an 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 to mechanically clamp the tubing 214 to prevent accidental fluid discharge.

[0048] The integrated flow stop system 202 adds electronic control functionality to the flow stop. In some embodiments, upon loading the integrated administration set 200 into the pump 250, the flow stop 210 is engaged (e.g., remains in the open position) and the plurality of electrically conductive connections 258 are mated with corresponding electrically conductive connections on the integrated flow stop system 202. The electrically conductive connections provide power to the electronic flow sensor 406 (and other components) disposed within the housing 450 of the integrated flow stop system 202 and provide a data pathway between the electronic flow sensor 406 and the pump 250. Figure 4C ​The plurality of conductive connections 258 provide electrical power to activate the electronic flow sensor 406, in addition to conducting electricity. 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 circuit to be relayed to the pump 250.

[0049] For example, in some embodiments, the control signals from the closed loop control circuit change an operating parameter of the pumping mechanism 256 to shift the measured flow at the electronic flow sensor 406 in value closer to the desired set flow programmed at the pump 250.

[0050] In some embodiments, 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, upon proper loading and engagement of the integrated flow stop system 202 into the pump 250, data stored in the non-volatile memory component is read by the pump 250. In some embodiments, the memory component stores information about how long the administration set 200 has been in use. For example, a circuit (e.g., an electronic time counter) disposed in the integrated flow stop system 202 records the length of time that the integrated flow stop system 202 receives power from the plurality of conductive connections 258. In some embodiments, the memory component also stores flow data measured by the electronic flow sensor 406.

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

[0052] In some embodiments, the identification information stored on the non-volatile memory includes a manufacture date of the administration set to allow the pump 250 to determine a shelf life of the administration set loaded into 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 prevent an infusion process on an administration set whose shelf life has been exceeded. The identification information can include additional or alternative information about the use of the administration set 200. For example, the identification information can include a maximum use time of the administration set 200. In this case, when the administration set 200 has been used for more than the maximum use time, the pump 250 can terminate the infusion process and / or issue an alert. This can help minimize the risk of infection associated with the over-extended use of an administration set. Other use information can include a type of medication that can or can not be infused with the administration set, a pump or pump module that is compatible with the administration set, or a calibration value that can be used to improve the accuracy of pressure sensing and flow delivery performance. In some embodiments, additional information can 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 affecting the flow pattern. If the lock on the flow stop is not engaged or is engaged in a way that is not within the specification, it can cause the flow to be unregulated. The flow stop system described herein can be able to detect this because the pump module is able to communicate with the flow stop.

[0053] The incorporation of electronic functionality into the integrated flow stop system 202 allows for easy association of the flow sensor (in the particular administration set) to the pump. For pumps with multi-channel infusion capability, the automatic establishment of a data channel between the pump and the flow sensor of each administration set (e.g., through the plurality of conductive connections 258) minimizes errors (e.g., errors that associate the wrong flow rate with the wrong infusion channel) and reduces the need for manual inspection of the administration set from a healthcare professional during loading or during an infusion process. In some embodiments, the IV bag and set are prepared together by a pharmacy. An identification (“ID”) number can be associated with the IV bag and administration set. The ID number can be read by the pump and correlated to the medication, flow rate, and volume to be administered to the patient. The pump can be programmed based on these parameters without the need for the clinician to input these values. In some embodiments, this information can be provided by the integrated flow stop system 202.

[0054] In some implementations, the plurality of electrically conductive connections 258 comprise spring-loaded pogo pin type connectors. In some implementations, the electrically conductive connections 258 are made of a resilient plastic conductor material. In some implementations, there is non-contact transfer of power and / or data between the integrated flow stop system 202 and the pump 250. The non-contact transfer of power includes an inductive coupling element. For example, the pump 250 includes a transmitter device driven by electrical power from a power source to generate a time-varying electromagnetic field. The electromagnetic field transfers power across space to a receiver device in the integrated flow stop system 202. The receiver device extracts power from the electromagnetic field and supplies it to electrical loads (e.g., the electronic flow sensor 406 and / or control circuitry).

[0055] The 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 alignment of the flow stop 210, as well as electrical contact between the integrated flow stop system 202 and the pump 250.

[0056] At slow flow rates, even a small deviation can create a large relative change in flow rate (e.g., a small change in flow rate constitutes a large percentage change when the flow rate is small). In other words, a small (absolute) change in flow rate results in a large percentage (e.g., relative) change. The large relative change limits the dynamic range of flow rates that the flow sensor can reliably detect.

[0057] Additionally, the area near the pumping mechanism 256 is often subject to high noise factors (e.g., from a motor that creates a burst flow in the system). In some implementations, the system 202 is disposed at the upper portion of the pump where the upper tubing fitting container 254 is located above the pumping mechanism 256, and the flow stop will not be part of the flow sensor. In such implementations, the applicator will have two separate fittings: one containing the (stand-alone) flow sensor and associated control circuitry, and the other (lower) fitting having the flow stop clamp. Placing the flow sensor and control circuitry near the upper tubing fitting container 254 allows for flow rate measurement at an area of the pump that has lower noise factors, resulting in more accurate measurements. The lower noise factors also allow for improved dynamic range of the flow rate measurements. In some implementations, the flow sensor 406 measures a dynamic range of flow rates between 0.1 ml / hour and 999 ml / hour.

[0058] Although Figure 2 and Figure 3 While the integrated flow stop system 202 is shown inserted at the lower region of the pump 250, applicators according to aspects of the subject technology can be inserted at other regions of the pump 250.

[0059] In some implementations, instead of positioning (e.g., inserting) the entire integrated flow stop system 202 at the upper tubing adapter container 254, only the electronics (e.g., electronic flow sensor 406, control circuitry, wireless communication module, inductive coupling element) contained in the housing 450 are inserted (e.g., when encased in the housing) at the top. In such implementations, similar to the configuration shown, the tubing adapter 222 and flow stop 210 are still inserted below the pumping mechanism 256. In this configuration, the components included in the upper tubing adapter can be conductively coupled to the flow stop 210. In this way, resources such as power and data can be conducted to the components included in the upper tubing adapter via the flow stop 210. The conductive path can be formed on or within the walls of the administration set, or the conductive path can be wireless. In other words, the flow sensor can be part of the upper adapter, and the electrical power or communication can be part of the flow stop in the lower adapter. Figure 2

[0060] Figure 3 An enlarged view of an integrated administration set and infusion pump, according to aspects of the subject technology, is depicted. In some implementations, a portion of the pump 250 receives the integrated administration set 200. The molded feature 260 has a shape that is 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 mate with the conductive connections in the integrated flow stop system 202 (shown more clearly in Figures 4A-4C ). Figure 3 The pump side alignment region 220 of the tubing adapter 222 is more clearly depicted as to how the receiving portion 262 engages.

[0061] Figure 4A A first perspective view of an integrated flow stop system, according to aspects of the subject technology, is depicted. As shown in the close-up view of the integrated flow stop system 202, the integrated flow stop system 202 includes a tubing adapter 222, a housing 450, and a flow stop 210. The tubing adapter 222 includes a protrusion 228 that is configured to receive a 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 the tubing adapter 222 and positioned below the tubing adapter 222. The slider portion 216 of the flow stop 210 is slidable along a channel defined in the tubing adapter 222.

[0062] ​Flow stop 210 is a clamp device or safety clamp that prevents fluid from accidentally flowing freely in tubing 212 when administration set 200 is removed from an infusion set. Slider portion 216 slides along direction 410, which is indicated by a double arrow. When slider portion 216 is slid closer to pump side alignment region 220 of adapter 222, flow stop 210 is in an open position, which allows fluid to flow from the top portion of integrated flow stop system 202 through tubing 212 to tubing 214, which is connected to the lower portion of integrated flow stop system 202. When slider portion 216 is slid toward tubing side region 230 of adapter 222, the circular region 224 of tear drop shaped opening 218 moves away from tubing 214, such that the narrower region 226 of flow stop 210 engages and mechanically constricts (e.g., clamps or clamps down on) tubing 214, thereby blocking fluid flow in tubing 214. In this closed position, the edge portion 230 of flow stop 210 extends beyond (e.g., protrudes out of) the tubing side region 230 of adapter 222 along direction 410.

[0063] When administration set 200 is properly loaded into (e.g., engaged with) pump 250 and received by pump 250, flow stop 210 in administration set 200 is held in an open state, in which fluid can flow through tubing 214. When the infusion process is interrupted (e.g., by opening door 252 of pump 250), flow stop 210 is displaced to a closed position to prevent accidental discharge of fluid when the infusion process is interrupted. For example, door 252 can include a locking element that fixes the door in position relative to pump 250. When a handle attached to the front of door 252 is lifted, the lifting action can release the locking element. In doing so, the change in position of the locking element can change the position of flow stop 210 to the closed position. In some embodiments, the opening of the door exerts the force necessary to displace flow stop 210 to the closed position. For example, flange 236 can engage under flow stop 210. When door 252 is opened, the flange will be pulled away from pump 250 and flow stop 210. As the flange moves away from pump 250, it can slide flow stop 210 to the closed position.

[0064] Conventional administration sets typically rely on external or built-in flow sensors within the pump. Incorporating a flow sensor into the flow stop allows for greater sensitivity in measuring different flow rates. Flow stop 210 can include a door-facing housing 234. Door-facing housing 234 can additionally or alternatively include a conductive connector to couple with a connector attached to door 252. Door-facing housing 234 can include electronic components that implement one or more of the features described, such as a sensor, a microprocessor, a memory, a power source, an antenna, a valve or valve controller (e.g., a piezoelectric or electromagnetic controller), and / or an optical fiber.

[0065] In some implementations, a flow stop is located on the downstream portion of the pump to more accurately control the flow to the patient for flow continuity. Monitoring the flow on the upstream side measures the inlet flow rate. In some implementations, the inlet is rapidly filled to allow for downstream flow continuity. Therefore, it may be necessary to monitor the flow on the downstream portion of the pump. Assuming there are no leaks or restrictions from the pump down to the needle (e.g., the site where fluid enters the patient), the location of flow monitoring should be irrelevant. Placing the flow sensor near or inside the pump reduces the length of conductive (e.g., electrical) leads.

[0066] Figure 4B A second perspective view of an integrated flow-stopping system according to aspects of the subject matter is depicted. As shown, the flow stop 210 is in the open position. In the open position, the circular region 224 of the teardrop-shaped opening 218 does not mechanically obstruct fluid flow in the pipe 214. In the open position, the edge 232 of the flow stop 210 does not protrude beyond the pipe-side region 230 of the pipe adapter 222.

[0067] Figure 4C A third perspective view of an integrated flow stopping system according to aspects of the subject matter is depicted. The view of the integrated flow stopping system 202 from the pump side shows multiple conductive connections 402-a to 402-e in a recessed portion 404 of the housing 450 of the upper portion of the integrated flow stopping system 202. An adapter 222 forms the lower portion of the system 202. The recessed portion 404 allows for easier alignment of the conductive connections with corresponding receiving portions of the conductive connections on the pump 250. Figure 4C As shown, the flow stopping system 202 includes five conductive connections, while the pump interface includes four (see...). Figure 3 (Component 258). Conductive connections can be made in... Figure 4C The flow stop system 202 shown differs from the pump. This allows the flow stop system 202 to interface with a variety of different pumps and increases the functionality provided when resources are available. In some instances, the flow stop system 202 may be inoperable without adequate connection to the pump. In such instances, the flow stop system 202 may include a valve that remains closed to prevent fluid from being delivered through the application device. In such instances, the pump can receive a message from the flow stop system 202 to prohibit delivery through the pump until the application device is changed.

[0068] The housing 450 of the integrated flow stop system 202 includes one or more flow sensors. In some embodiments, at least a portion of the flow sensors can be in contact with the fluid. In such embodiments, the flow sensors can include a metering element in the fluid path that can move based on the rate at which the fluid moves along the fluid path. In some embodiments, the inline pressure (or differential pressure) of the fluid along the fluid path or constricted fluid path can be measured to determine flow rate.

[0069] In some embodiments, the fluid can not be in contact with the flow sensors. In some embodiments, the flow sensors can include two components, one within the housing 450 and one within the door-facing housing 234. Emissions from one component can be read by the second component. A comparison between the emission signal and the received signal can provide an indication of flow rate. In some embodiments, the flow sensors can include acoustic sensors. The acoustic sensors can detect noise within the fluid line as the fluid is flowing through the sensor. The detected noise can be used to identify flow rate. In some embodiments, the acoustic sensors include flow sensing of the ultrasonic method.

[0070] In some embodiments, the flow sensors operate based on calorimetric principles. For example, a static heating element and two temperature sensors are placed in the fluid path, and flow rate is measured based on changes in the temperature profile of the fluid. Such flow sensors can be CMOS-based. In some embodiments, the flow sensors operate based on time-of-flight principles. Unlike static heaters, the heaters based on time-of-flight principles are modulated, and receivers located upstream and downstream of the heater receive the modulated signal. Based on the arrival time of the modulated signal, flow rate is determined. In some embodiments, such flow sensors can be packaged as MEMS.

[0071] In some embodiments, electrical energy for powering the flow sensors is transmitted from the pump to the flow sensors through the conductive connections 402-a. The flow sensors send data back to the pump 250 through one of the conductive connections. In some embodiments, the conductive connections 402-a and 402-e include pogo-pin type connectors. In some embodiments, the conductive connections 402-a and 402-e include a resilient plastic conductor material. In some embodiments, 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 sensors. In such cases, the conductive connections do not need to be formed on the exposed surface of the housing 450 in the upper portion of the integrated flow stop system 202.

[0072] In some embodiments, the integrated flow stop system 202 includes wireless communication circuitry to allow the administration device 200 to form a wireless association with the pump and / or a server system. In some embodiments, the wireless association is formed automatically without requiring specific user input. This wireless connection allows the server system to track the location of a particular administration device and also allows the server system to receive information about the flow of medical treatment provided by different administration devices.

[0073] The housing 450 in the upper portion of the system 202 can also contain various circuitry to allow the pump to identify a particular administration device. Non-volatile memory in the circuitry can store information about the manufacturing date of the administration device 200, allowing the pump to determine whether the administration device 200 has exceeded a particular shelf life. In some embodiments, to ensure patient safety, the pump will not proceed with an infusion process when the pump reads from the non-volatile memory of the integrated flow stop system 202 that the administration device 200 has exceeded its shelf life. In some embodiments, the administration device degrades in accuracy as it approaches the end of its life, and the pump will be able to obtain life time information from the non-volatile memory of the administration device 200. Thus, the integrated flow stop system 202 provides the pump 250 with a smart sensor. The pump is also able to record the usage time clocked on a particular administration device. In some embodiments, when a patient moves between different areas of a hospital (e.g., from an intensive care unit to a general ward), the same administration device is used / associated with different pumps, and the circuitry on the integrated flow stop system 202 provides information to the hospital system about the total duration of the medical treatment.

[0074] The circuitry contained within the housing 450 in the upper portion of the integrated flow stop system 202 also includes a closed loop flow control circuit. In some embodiments, the closed loop flow control circuit directly receives real-time data recorded by a flow sensor (or other sensors included in the flow stop, such as temperature sensors, light sensors, cameras, gyroscopic sensors or accelerometers to identify whether the device has been properly inserted by a user, near-field communication (NFC) sensors for powering, communicating, and / or authenticating authorized administration devices, Bluetooth Low Energy (BLE) beacons for asset tracking, and for identifying activated infusions and administration devices) and provides control signals to the pump 250 to change the flow of the pump to achieve a desired medical fluid flow profile for the infusion. In some embodiments, the flow sensor includes a capacitive sensor that measures flow based on dielectric changes caused by fluid flow. In some embodiments, it can be desirable to provide the measurements to the pump and allow the pump to evaluate and apply adjustments to achieve target pumping conditions.

[0075] The flow sensor provides real-time measurement data to a closed loop flow control circuit contained within the housing 450 of the integrated flow stop system 202, minimizing or in some cases eliminating the need to pass raw flow data to the pump, and reducing the delay between detecting flow and the pump receiving, calculating, and adjusting flow. In some embodiments, the housing 450 of the integrated flow stop system 202 can include newer control circuitry and / or firmware, allowing even older versions of pumps to provide enhanced flow control or other fluid property sensing based on the control circuitry in the administration set, without the need to retrofit or modify the pump or add and coordinate additional sensors. In some embodiments, 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 that have already been deployed in the field. In some embodiments, older pumps with mating connections can be connected with flow stops having corresponding conductive connections (e.g., electrically conductive connections and data conductive elements).

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

[0077] The pump includes flow values for different fluid types. By measuring flow and controlling flow in a closed loop, higher accuracy is achieved on the administration set. Higher accuracy allows for better prediction of the amount of medical fluid that will be infused to the patient. The system 250 detects the risk of unregulated flow (e.g., over-infusion, under-infusion) and corrects any infusion rate errors in advance.

[0078] Figure 5A An example sensor system adapted to an infusion device is depicted in accordance with aspects of the subject technology. Instead of the integrated flow stop system 202 establishing an electrical or data connection to the control module 14 (e.g., pump 250), the sensor wedge 500 has one or more sensor inserts 502 to couple one or more fluid infusions to one or more different administration sets (e.g., 508, 510) via an integrated flow stop system (similar to the flow stop system 202 described in Figures 2-4C In some embodiments, various flow features can be integrated into one or more sensor inserts 502. In some embodiments, sensor features are inserted into the wedge (as shown in Figure 5B and Figure 5C or included in (e.g., attached to) the wedge (as shown in Figure 5D and Figure 5EThe sensor features are included in the sensor 500, the administration device (e.g., 508, 510) can be loaded into the sensor insert 502 for non-contact sensing (e.g., through a conduit without direct contact with the fluid).

[0079] In some implementations, the modules 504 and 506 can include different pumps, such as a large volume pump (LVP), a syringe pump, or an end-tidal C02monitor (EtC02). In some implementations, the sensor insert can be clamped outside of the administration device, rather than being coupled with or integrated into the administration device. In this way, the sensor insert can be reused for multiple infusions. In some implementations, the sensor insert is integrated into the administration device and includes one or more electrically conductive coupling elements to connect with the sensor wedge.

[0080] The control module 14 can include a user interface device 54. The sensor wedge 500 can be retrofitted to a pump to provide sensing capabilities via the IUI connector 266 (as Figure 2 shown). Data and power can be transferred via the IUI connector 266. The sensor wedge can include similar circuitry to the flow stop, such as a microprocessor, memory, power storage, antenna, sensors, etc. The sensor insert can provide measurements to the sensor wedge 500. As discussed, the sensor wedge can process the measurements and provide control messages to adjust the pump. In some implementations, the sensor wedge can forward the sensor readings to the pump and allow the pump to evaluate the appropriate control. In some implementations, the sensor wedge allows the flow sensor and control circuitry to be located on the top conduit fitting, rather than on the lower fitting.

[0081] Figure 5B An example sensor system including a device having a port for receiving a flow sensor is depicted in accordance with aspects of the subject technology. Figure 5B A side view of the wedge sensor 520 is shown. 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 parallel to the first major surface 522 (not shown in FIG. 6). The wedge sensor has a processor located inside the housing 522. A storage memory is also located inside the housing 522. Figure 5B The wedge sensor has a processor located inside the housing 522. A storage memory is also located inside the housing 522.

[0082] The wedge sensor 520 includes a connection element 528 mounted on a first surface 524 of the housing 522. In some embodiments, the connection element 528 is an inter-unit interface connector configured to mate with an IUI connector on a pump module or patient care unit (PCU). The connection element 528 includes data conducting elements to pass data from the wedge sensor 520 to the pump module or PCU. The connection element 528 also includes electrical conducting elements to pass power. In some embodiments, the connection element 528 receives power from the infusion device, and data is passed between the sensor system and the infusion device. In some embodiments, the connection element 528 includes mounting elements to attach to a corresponding interface connector of the infusion device. In some embodiments, 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.

[0083] In some embodiments, the inter-unit interface connector 528 includes mounting elements to attach to a corresponding interface connector of a first infusion device, and the second inter-unit interface connector 534 includes second mounting elements to attach to a corresponding interface connector of a second infusion device. In some embodiments, power is received from the first infusion device, and data is passed between the sensor system and the first infusion device. In some embodiments, 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 passed between the sensor system and the first infusion device, and is passed between the sensor system and the second infusion device.

[0084] The wedge sensor 520 includes an electronic flow sensor port 526 on the first major surface 524 for receiving a flow sensor. In some embodiments, the port 522 includes three pins as shown in Figure 5B In some embodiments, there can 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 (e.g., from an administration set) of a first fluid line coupled thereto. The data conducting elements, the electrical conducting elements, and the electronic flow sensor port are coupled with the processor.

[0085] The second connection element 534 (as Figure 5CA second connection element (not shown) is also mounted on the second major surface. In some embodiments, the second connection element is similar to the connection element mounted on the first major surface 524: it is configured to mate with an IUI connector on a pump module or PCU; it includes a second data conducting element to pass second data from the wedge sensor 520 to the pump module or PCU; and it includes a second electrical conducting element to pass power.

[0086] A second electronic flow sensor port 536 (not shown) is also mounted on the second major surface. In some embodiments, the second electronic flow sensor port is similar to the electronic flow sensor port 526 mounted on the first major surface 524: it is configured to receive flow information from a second electronic flow sensor coupled to a second fluid line (e.g., from an administration set) thereto. The second data conducting element, the second electrical conducting element, and the second electronic flow sensor port are also coupled with the processor. Figure 5C

[0087] In some embodiments, the first portion 530 of the housing 522 has a height x that corresponds to the height of a pump module. The second portion 532 of the housing 522 includes the port 526 and has a height n. In some embodiments, 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.

[0088] Figure 5C An example sensor system configured to couple more than one sensor and more than one pump module is depicted in accordance with aspects of the subject technology. Figure 5C The coupling between the microprocessor in the wedge sensor 520 and the various connectors and ports is shown. In some embodiments, the first IUI connector 528 and the first electronic flow sensor port 526 (both mounted to the first major surface 524 of the housing 522) are coupled to the microprocessor. The microprocessor in the wedge sensor 520 is also coupled to the second IUI connector 534 and the second electronic flow sensor port 536, both mounted to the 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 be coupled to two PCUs (one on each side of the wedge).

[0089] Figure 5D An example sensor system is depicted in accordance with aspects of the subject technology. Figure 5D A side view of a wedge sensor 540 is shown. The wedge sensor 540 has a housing 542. In some embodiments, the housing 542 has a first major surface 544 and a second major surface parallel to the first major surface 544 (not shown). The first major surface 544 is configured to be coupled to a first PCU (not shown) and the second major surface is configured to be coupled to a second PCU (not shown). Figure 5D ​(Not shown in the image). The processor of the wedge sensor 540 is located inside the housing 542. The storage memory is also located inside the housing 542.

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

[0091] In some embodiments, the inter-unit interface connector 548 includes mounting elements for attachment to a corresponding interface connector of the first infusion device, and the second inter-unit interface connector 554 includes second mounting elements for attachment to a corresponding interface connector of the second infusion device. In some embodiments, power is received from the first infusion device, and data is transmitted between the sensor system and the first infusion device. In some embodiments, 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 transmitted between the sensor system and the first infusion device, and is transmitted between the sensor system and the second infusion device.

[0092] An electronic flow sensor 546, attached to a first main surface 544, is configured to measure flow information of a first fluid line coupled thereto. Data transmission elements, electrical transmission elements, and the first electronic flow sensor are coupled to a processor.

[0093] Second connecting element 554 ( Figure 5E (As shown) is mounted on the second surface of housing 552. In some embodiments, the second connection element is similar to the connection element mounted on the first main surface 554: it is configured to mate with an IUI connector on the pump module or PCU; it includes a second data conduction element to transmit second data from the wedge sensor 550 to the pump module or PCU; and it includes a second electrical conduction element to transmit power.

[0094] a second electronic flow sensor 556 (shown) configured to measure flow information of a second fluid line coupled thereto. The second data conducting element, the second electrically conducting element, and the second electronic flow sensor port are also coupled with the processor. Figure 5E

[0095] Figure 5E An example sensor system configured to couple more than one pump module is depicted in accordance with aspects of the subject technology. Figure 5E Couplings between the microprocessor in the wedge sensor 540 and various connectors and ports are shown. In some implementations, a first IUI connector 548 and a first electronic flow sensor 546 (both mounted to the first major surface 544 of the housing 542) are coupled to the microprocessor. The microprocessor in the wedge sensor 540 is also coupled to a second IUI connector 554 (mounted to the second major surface of the housing 542) and a second electronic flow sensor 556. A memory storage 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 be coupled to two PCUs (one on each side of the wedge).

[0096] In one aspect, an integrated intravenous (IV) administration set includes a flow stop having a tubing fitting and a housing, the flow stop configured to: in a first position, prevent fluid flow through the tubing; and in a second position, allow fluid flow through the tubing, the tubing fitting including 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 flow of the fluid in the tubing, and one or more electrically conductive connections configured within the housing and configured to provide electrical power to the electronic flow sensor. The flow stop is shaped to be loaded and engaged to a container of an infusion device, and shaped to, when loaded and engaged, cause the one or more electrically conductive connections to engage with corresponding electrically conductive connections provided by the infusion device to activate the electronic flow sensor based on power flow from the infusion device.

[0097] In some implementations, the integrated intravenous (IV) administration set also includes a control circuit configured to send control signals to the infusion device to modify a flow rate produced by a pumping mechanism of the infusion device. In some implementations, the electronic flow sensor also includes a data communication component. The one or more electrically conductive connections are disposed on an exterior of the housing, and the infusion device is configured with corresponding one or more electrically conductive connections, such that during use of the integrated IV administration set: the one or more electrically conductive connections are in electrical contact with the corresponding one or more electrically conductive connections, and the electronic flow sensor is in electrical communication to transmit data to the infusion device using the data communication component.​

[0098] In some embodiments, the housing includes a recessed portion, and the one or more electrically conductive connections are vertically aligned within the recessed portion. In some embodiments, the one or more electrically conductive connections include spring-loaded pogo pin connectors. In some embodiments, the one or more electrically conductive connections include a resilient plastic conductor material. In some embodiments, the tubing adapter has a shape that is complementary to a feature molded into the housing of the infusion device, such that the tubing adapter is configured to align the flow stop with respect to the infusion device when the integrated IV administration set is loaded and engaged to the infusion device.

[0099] In some embodiments, the integrated IV administration set further includes a wireless communication module. In some embodiments, 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.

[0100] In some embodiments, the integrated IV administration set is configured to wirelessly communicate data measured by the electronic flow sensor to the infusion device.

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

[0102] In some embodiments, the integrated IV administration set further includes a non-volatile memory component that stores identification information of the integrated IV administration set. In some embodiments, 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 information and manufacturing date of the integrated IV administration set prior to starting an infusion process.

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

[0104] In some embodiments, the flow stop includes a slider assembly mounted to and positioned orthogonally with respect to the tubing adapter. The slider assembly is configured to slide with respect to the tubing adapter and engage a tubing connected to the tubing adapter to prevent flow of fluid in the tubing when the IV administration set is removed from the infusion device, and to allow flow of fluid in the tubing when the IV administration set is loaded and engaged to the infusion device.

[0105] In some embodiments, the tubing adapter and the housing are configured to be received in a top portion of the infusion device that is above a pumping mechanism of the infusion device, and the flow stop is configured to be received in a bottom portion of the infusion device that is below the pumping mechanism of the infusion device.

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

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

[0108] In another aspect, a sensor system includes a first plurality of conductive connections; a data port to receive data recorded by an electronic flow sensor of an integrated intravenous (IV) administration set, wherein the integrated IV administration set includes 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 is configured to provide a control signal to an infusion device based on the data recorded by the electronic flow sensor to maintain a flow of fluid through the integrated IV administration set at a desired flow rate.

[0109] Many of the above-described features and applications can also be implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium), and that are executed by one or more processing units (for example, one or more processors, cores of processors, or other processing units). When executed by the one or more processing units, the instructions cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable medium include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. Computer readable medium does not include wireless or wired carrying away signals and electronic signals processed and conveyed by communication media.

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

[0111] 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 it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or code portions). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and

[0112] Figure 6 is a conceptual diagram illustrating an example electronic system 600 for sensing and controlling liquid flow during an infusion process, in accordance with aspects of the subject technology. Electronic system 600 can be a computing device for executing software associated with one or more portions or steps of process 600, or by Figures 1-6 The components and processes provided by the subject disclosure, including but not limited to computing hardware within information system server 30 or patient care device 12. Electronic system 600 can be representative, in conjunction with the disclosure regarding Figures 1-6 . In this regard, electronic system 600 can be a personal computer or a mobile device, such as a smartphone, tablet, notebook, PDA, augmented reality device, wearable device (such as a watch or band or glasses), or combination thereof, or other touchscreen or television having one or more processors embedded therein or coupled thereto, or any other category of computer-related electronic device having network connectivity.

[0113] Electronic system 600 can include various types of computer readable media and interfaces for various other types of computer readable media. In the depicted example, 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, electronic system 600 can include or be integrated with other computing devices or circuitry for operating the various components and processes described previously.

[0114] Bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect the various internals of electronic system 600. For instance, bus 608 communicatively connects processing unit 612 with ROM 610, system memory 604, and permanent storage device 602.

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

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

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

[0118] Bus 608 is also connected to input and output device interfaces 614 and 606. Input device interface 614 enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface 614 include, for example, alphanumeric keypads and pointing devices (also referred to as "cursor control devices"). Output device interface 606 enables, for example, the display of images generated by electronic system 600. Output devices used with output device interface 606 include, for example, printers and display devices such as cathode ray tube (CRT) or liquid crystal display (LCD). Some implementations include devices such as touchscreens, which function as both input and output devices.

[0119] In addition, such as Figure 6 As shown, bus 608 also couples electronic system 600 to a network (not shown) via network interface 616. Network interface 616 may include, for example, a wireless access point (e.g., Bluetooth or WiFi) or radio circuitry for connecting to a wireless access point. Network interface 616 may also include hardware (e.g., Ethernet hardware) for connecting the computer to a part of a computer network (such as a local area network (“LAN”), wide area network (“WAN”), wireless LAN, or intranet), or a network of networks (such as the Internet). Any or all components of electronic system 600 may be used in conjunction with the disclosure of this subject matter.

[0120] The functions described above can be implemented in computer software, firmware, or hardware. This technology can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. Processes and logic flows can be executed by one or more programmable processors and one or more programmable logic circuits. General-purpose and special-purpose computing devices and storage devices can be interconnected through communication networks.

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

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

[0123] As used in the specification and anywhere else in this application, the terms "computer", "server", "processor", and "memory" all refer to electronic or other technological devices. These terms do not encompass humans or groups of humans. For the purposes of the specification, the term display or being displayed means display on an electronic device. As used in the specification and anywhere else in this application, the terms "computer-readable medium" and "computer-readable media" are entirely restricted to tangible, physical objects that store information in a form readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.

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

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

[0126] The computing system can include clients and servers. A client and server are generally remote from each other and typically 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 embodiments, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.

[0127] A "user interface" (also referred to as an interactive user interface, graphical user interface, or UI) as used herein can refer to a web-based interface, including data fields and / or other control elements, for receiving input signals or providing electronic information and / or for providing information to a user in response to any received input signals. Control elements can include dials, buttons, icons, selectable areas, or other perceptible indicia presented via the UI that, when interacted with (e.g., clicked, touched, selected, etc.), initiate data exchange of the device presenting the UI. The UI can be implemented using technologies such as HyperText Markup Language (HTML), FLASH™, JAVA™,.NET™, C, C++, web services, or Rich Site Summary (RSS), in whole or in part. In some embodiments, the UI can be included in a standalone client (e.g., thick client, fat client) configured to communicate (e.g., send or receive data) in accordance with one or more aspects described. The communication can be to or from a medical device or server in communication therewith.

[0128] As used herein, the term "determining" or "determine" encompasses a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, generating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like in

[0129] As used herein, the term "providing" or "provide" encompasses a wide variety of actions. For example, "providing" can include storing values in locations of a storage for subsequent retrieval, transmitting the values directly to a recipient via at least one wired or wireless communication medium, transmitting or storing a reference to the values, and the like. "Providing" can also include encoding, decoding, encrypting, decrypting, authenticating, verifying, and the like via hardware elements.

[0130] As used herein, the term "message" encompasses a variety of formats for communicating (e.g., sending or receiving) information. A message can include a machine-readable aggregation of information, such as an XML document, a fixed field message, a comma separated message, JSON, a custom protocol, and the like. In some embodiments, a message can include a signal for transmitting one or more representations of information. While recited in the singular, it will be understood that a message can be composed, sent, stored, received, and the like in multiple parts.

[0131] In any of the embodiments, the data generated or detected can be forwarded to a "remote" device or location, where "remote" means a location or device other than the location or device where the program is executed. For example, the remote location can be another location (e.g., office, laboratory, etc.) in the same city, another location in a different city, another location in a different state, or another location in a different country, etc. Thus, when one item is indicated as being "remote" from another, this means 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 a mile, ten miles, or at least a hundred miles apart. "Communicating" information means transmitting the data representing the information as electrical, electromagnetic or optical signals over a suitable communication channel (wireless or wired, as applicable). "Forwarding" an item means any means of getting that item from one location to the next, whether by physically transporting the item or otherwise (as applicable), and at least in the case of data, includes physically transporting a medium carrying the data or communicating the data. Examples of communication media include radio or infra-red transmission channels as well as a network connection to another computer or networking device, and the Internet or Intranets including e-mail transmissions and information recorded on websites.

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

[0133] It can be appreciated that the particular sequence of steps in the process disclosed is illustrative. Based upon the design preferences, it can be appreciated that the particular sequence of steps in the process can be rearranged. Some steps can be performed concurrently. The accompanying method presents the elements of the various steps in example order, and is not meant to be limited to the particular order presented.

[0134] The subject technology is illustrated as clauses:

[0135] For convenience, the various examples of aspects of the disclosure have been described as numbered clauses (1, 2, 3, etc.). These are provided as examples and are not intended to be limiting of the subject technology. The clauses are not meant to be sequential or hierarchical in stages. The illustrations presented have been simplified for the sake of clarity to describe the principles of the subject technology. The numbering scheme is provided for consistency with the examples described above and is not meant to limit the scope of the subject technology.

[0136] Clause 1. An integrated intravenous (IV) administration set, comprising: a flow stopper comprising a tubing adapter and a housing, the flow stopper configured to, in a first position, prevent fluid flow through a tube, and in a second position, allow the fluid flow through the tube, the tubing adapter comprising a protrusion configured to receive a tube; an electronic flow sensor disposed within the housing, the electronic flow sensor configured to measure flow of the fluid in the tube; and one or more electrically conductive connections configured within the housing and configured to provide electrical power to the electronic flow sensor; wherein the flow stopper is shaped to be loaded and engaged to a container of an infusion device, and shaped to, when loaded and engaged, cause the one or more electrically conductive connections to engage with corresponding electrically conductive connections provided by the infusion device to activate the electronic flow sensor based on power flow from the infusion device.

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

[0138] Clause 3. The integrated IV administration set of any of the preceding clauses, wherein the electronic flow sensor further comprises a data communication component, and wherein the one or more electrically conductive connections are disposed on an exterior of the housing, and the infusion device is configured with a corresponding one or more electrically conductive connections, such that during use of the integrated IV administration set: the one or more electrically conductive connections are in electrical contact with the corresponding one or more electrically conductive connections, and the electronic flow sensor is in electrical communication to transmit data to the infusion device using the data communication component.

[0139] Clause 4. The integrated IV administration set of clause 3, wherein the one or more electrically conductive connections comprise spring-loaded pogo pin connectors.

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

[0141] Clause 6. The integrated IV administration set of clause 3, wherein the tubing adapter has a shape that is complementary to a feature molded into a housing of the infusion device, such that the tubing adapter is configured to align the flow stopper relative to the infusion device when the integrated IV administration set is loaded and engaged to the infusion device.

[0142] Clause 7. The integrated IV administration set of any of the preceding clauses, further comprising a wireless communication module, and wherein the integrated IV administration set is configured to wirelessly upload data measured by the electronic flow sensor to a server system monitoring operation of the infusion device.

[0143] Clause 8. The integrated IV administration set of any of the preceding clauses, further comprising a wireless communication module, and wherein the integrated IV administration set is configured to wirelessly communicate data measured by the electronic flow sensor to the infusion device.

[0144] Clause 9. The integrated IV administration set of any of the preceding clauses, wherein the one or more electrically conductive connections comprise an inductive coupling assembly configured for wireless power transfer from the infusion device to the electronic flow sensor.

[0145] Clause 10. The integrated IV administration set of any of the preceding clauses, further comprising a non-volatile memory assembly storing identification information of the integrated IV administration set.

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

[0147] Clause 12. The integrated IV administration set of any of the preceding clauses, wherein the flow stopper comprises a slider assembly mounted to the tubing adapter and positioned orthogonally thereto, wherein the slider assembly is configured to slide relative to the tubing adapter and engage a tube connected to the tubing adapter to prevent flow of fluid in the tube when the IV administration set is removed from the infusion device, and to allow flow of fluid in the tube when the IV administration set is loaded and engaged to the infusion device.

[0148] Clause 13. The integrated IV administration set of any of the preceding clauses, wherein the tubing adapter and the housing are configured to be received in a top portion of the infusion device above a pumping mechanism of the infusion device, and the flow stopper is configured to be received in a bottom portion of the infusion device below the pumping mechanism of the infusion device.

[0149] Clause 14. The integrated IV administration set of any of the preceding clauses, 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.

[0150] Clause 15. A sensor system 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 comprising a first data conducting element that conveys first data and a first electrically conducting element that conveys first power, and a first electronic flow sensor configured to measure flow information of a first fluid line coupled thereto, wherein the first data conducting element, the first electrically conducting element, and the first electronic flow sensor are coupled with the processor; the second surface comprising: a second inter-unit interface connector mounted on the second surface of the housing, the second inter-unit interface connector comprising a second data conducting element that conveys second data and a second electrically conducting element that conveys second power, and a second electronic flow sensor configured to measure flow information of a second fluid line coupled thereto, wherein the second data conducting element, the second electrically conducting element, and the second electronic flow sensor are coupled with the processor.

[0151] Clause 16. The sensor system of clause 15, wherein the first inter-unit interface connector comprises a mounting element to attach to a corresponding interface connector of an infusion device, and the infusion device has a predetermined length, and wherein 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.

[0152] Clause 17. The sensor system of any of clauses 15 and 16, wherein the first inter-unit interface connector comprises a mounting element to attach to a corresponding interface connector of an infusion device and receives the first power from the infusion device, and wherein the first data is conveyed between the sensor system and the infusion device.

[0153] Clause 18. The sensor system of any of clauses 15 and 16, wherein the first inter-unit interface connector comprises a mounting element to attach to a corresponding interface connector of a first infusion device, and wherein the second inter-unit interface connector comprises a second mounting element to attach to a corresponding interface connector of a second infusion device.

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

[0155] Clause 20. A sensor system, 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 comprising a first data conductive element that communicates first data and a first electrically conductive element that communicates first power, and a first electronic flow sensor port configured to receive flow information from a first electronic flow sensor for a first fluid line coupled thereto, wherein the first data conductive element, the first electrically conductive element, and the first electronic flow sensor port are coupled with the processor; the second surface comprising: a second inter-unit interface connector mounted on the second surface of the housing, the second inter-unit interface connector comprising a second data conductive element that communicates second data and a second electrically conductive element that communicates second power, and a second electronic flow sensor port configured to receive flow information from a second electronic flow sensor for a second fluid line coupled thereto, wherein the second data conductive element, the second electrically conductive element, and the second electronic flow sensor port are coupled with the processor.

[0156] Further contemplated:

[0157] It can be appreciated that the particular sequence or hierarchy of steps in the processes disclosed is an example. Based on design preferences, it can be appreciated that the specific sequence or hierarchy of steps in the processes can be re-arranged, or that some steps can be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0158] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The descriptions are provided as illustrative examples and are not intended to be limiting to the subject technology. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language claims, wherein reference to an aspect in the following description is not a limitation on the claims, which

[0159] The term website, as used herein, can include any aspect of a website, including one or more webpages, one or more servers used to host or store web-related content, etc. Thus, the term website can be used interchangeably with the terms webpage and server. The verbs “configured to,” “operable to,” and “programmed to” do not imply any particular tangible or intangible modification to the subject, but rather merely that the subject is enabled to perform an operation or activity. For example, a processor configured to monitor and control an operation or component can also mean that the processor is programmed to monitor and control the operation or processor is operable to monitor and control the operation. Likewise, a processor configured to execute code can be interpreted to mean that the processor is programmed to execute the code or is operable to execute the code.

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

[0161] Phrases such as "aspect" do not imply that a particular aspect is critical, essential, or mandatory to the subject technology. Rather, descriptions or implementations that include, for example, an aspect, can include additional aspects not expressly described. Phrases such as "aspect" can refer to one or more aspects and vice versa. Phrases such as "implementation" do not imply that a particular implementation is critical, essential, or mandatory to the subject technology. Rather, descriptions or implementations that include, for example, an implementation, can include additional implementations not expressly described. Phrases such as "implementation" can refer to one or more implementations and vice versa. Phrases such as "configuration" do not imply that a particular configuration is critical, essential, or mandatory to the subject technology. Rather, descriptions or implementations that include, for example, a configuration, can include additional configurations not expressly described. Phrases such as "configuration" can refer to one or more configurations and vice versa.

Claims

1. A sensor system, 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 comprising a mounting element to attach to a corresponding interface connector of an infusion device, a first data conducting element to communicate first data between the sensor system and the infusion device, and a first electrically conducting element to receive first power from the infusion device, and a first electronic flow sensor configured to measure flow information of a first fluid line coupled thereto, wherein the first data conducting element, the first electrically conducting element, and the first electronic flow sensor are coupled with the processor; the second surface comprising: a second inter-unit interface connector mounted on the second surface of the housing, the second inter-unit interface connector comprising a second data conducting element to communicate second data and a second electrically conducting element to communicate second power, and a second electronic flow sensor configured to measure flow information of a second fluid line coupled thereto, wherein the second data conducting element, the second electrically conducting element, and the second electronic flow sensor are coupled with the processor.

2. The sensor system of claim 1, wherein, the infusion device having a predetermined length, and wherein 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.

3. The sensor system of claim 1, wherein, the second inter-unit interface connector comprising a second mounting element to attach to a corresponding interface connector of a second infusion device.

4. The sensor system of claim 3, wherein, the second power comprises at least a portion of the first power, and wherein the second power is communicated to the second infusion device, and wherein the second data comprises at least a portion of the first data, and wherein the second data is communicated between the sensor system and the second infusion device.

5. The sensor system of claim 1, wherein, the housing comprising: a connection element comprising a data conducting element configured to communicate data from the sensor system to a first or second infusion pump module or to an infusion pump control unit.

6. The sensor system of claim 5, wherein, the housing further comprising: a non-volatile memory storing identification information of the sensor system.

7. The sensor system of claim 6, further comprising: a control circuit configured to communicate with the first or second infusion pump module or with the infusion pump control unit and to change an operating parameter of the first or second infusion pump module or of the infusion pump control unit in order to bring a flow rate measured by the first or second electronic flow sensor as close as possible to a set flow rate.

8. The sensor system of claim 7, further comprising a wireless communication module, and wherein the processor is configured to wirelessly communicate data measured by the first or second electronic flow sensor to the first or second infusion pump module or to the infusion pump control unit.

9. The sensor system of claim 8, wherein, the processor is configured to change the operating parameter after the sensor system has been in use for a predetermined period of time.

10. The sensor system of claim 1, wherein, the first surface and the second surface are parallel to each other.

11. A sensor system, 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 comprising a mounting element to attach to a corresponding interface connector of an infusion device, a first data conducting element to pass first data between the sensor system and the infusion device, and a first electrical conducting element to receive from the infusion device a first electrical power to pass, and a first electronic flow sensor port configured to receive flow information from a first electronic flow sensor for a first fluid line coupled thereto, wherein the first data conducting element, the first electrical conducting element, and the first electronic flow sensor port are coupled with the processor; the second surface comprising: a second inter-unit interface connector mounted on the second surface of the housing, the second inter-unit interface connector comprising a second data conducting element to pass second data and a second electrical conducting element to pass second electrical power, and a second electronic flow sensor port configured to receive flow information from a second electronic flow sensor for a second fluid line coupled thereto, wherein the second data conducting element, the second electrical conducting element, and the second electronic flow sensor port are coupled with the processor.

12. The sensor system of claim 11, wherein, the infusion device having a predetermined length, and wherein the first surface of the housing has a length that exceeds the predetermined length such that the first electronic flow sensor port can extend from the first surface below or above the infusion device.

13. The sensor system of claim 11, wherein, the second inter-unit interface connector comprising a second mounting element to attach to a corresponding interface connector of a second infusion device.

14. The sensor system of claim 13, wherein, the second power comprising at least a portion of the first power, and wherein the second power is passed to the second infusion device, and wherein the second data comprises at least a portion of the first data, and wherein the second data is passed between the sensor system and the second infusion device.

15. The sensor system of claim 11, wherein, the housing comprising: a connection element configured to pass data from the sensor system to a first or second infusion pump module or to an infusion pump control unit, and wherein the housing further comprises a non-volatile memory that stores identification information of the sensor system.

16. The sensor system of claim 15, further comprising: a control circuit configured to communicate with the first or second infusion pump module or with the infusion pump control unit and to change an operating parameter of the first or second infusion pump module or the infusion pump control unit so as to bring a flow rate measured by the first or second electronic flow sensor and received by the first or second electronic flow sensor port as close as possible to a set flow rate, and wherein the processor is configured to change the operating parameter after the sensor system has been in use for a predetermined period of time.

17. The sensor system of claim 16, further comprising a wireless communication module, and wherein the processor is configured to wirelessly communicate data measured by the first or second electronic flow sensor and received by the first or second electronic flow sensor port to the first or second infusion pump module or to the infusion pump control unit.

18. The sensor system of claim 17, wherein, the processor is configured to change an operational parameter after the sensor system has been used for a predetermined period of time.

19. The sensor system of claim 11, wherein, the first surface and the second surface are parallel to each other.

20. The sensor system of claim 11, wherein, the first electronic flow sensor port is configured to receive the first electronic flow sensor via insertion of the first electronic flow sensor into the first electronic flow sensor port and to receive flow information from the first electronic flow sensor via a plurality of pins, wherein the first electronic flow sensor is coupled to the first fluid line, and wherein the second electronic flow sensor port is configured to receive the second electronic flow sensor via insertion of the second electronic flow sensor into the second electronic flow sensor port and to receive flow information from the second electronic flow sensor via a plurality of pins, wherein the second electronic flow sensor is coupled to the second fluid line.

Images