Sensor for detecting disconnection of a fluid connector

Abstract

A fluid flow interruption sensor and an alarm system each include first and second sensor units configured to be removably coupled to first and second portions of a fluid connector assembly. The first sensor unit includes a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, a transmitter configured to transmit an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the first and second sensor units. A computing device that receives the indication can determine when the first and second portions of the fluid connector assembly are coupled to each other and when the assembly is disconnected, and can generate an alarm when the first and second portions are disconnected.

Description

Technical Field

[0001] The present disclosure generally relates to a control device configured to facilitate the operation of an accessory associated with an infusion device.

Background Art

[0002] During infusion therapy, fluid is administered via an administration set connected to a catheter, which can be installed in the center of a large vein. The catheter can be connected to the administration set by a luer. Whether intentional or accidental, if the administration set is pulled with sufficient force, the catheter can become dislodged from the patient. A dislodged catheter requires replacement with a new catheter and an additional needle stick. The clinician will notice that the disconnection has occurred when the patient is next checked, which can take up to one hour depending on hospital practices. Upon noticing that the fluid flow has been interrupted, the clinician can clean and then rejoin the connection to resume fluid administration. Some administration sets include a fuse that can prevent fluid from flowing during a cut. During the time the fluid path is cut, the patient does not receive their medication.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Means for Solving the Problems

[0004] According to various aspects, the present technology provides a system and method for operating an infusion accessory device intelligently. In this regard, an intelligent accessory system for use with an infusion pump and related devices is disclosed. The system increases safety by reducing human error and accessory damage. The system includes a microcontroller and firmware and is designed to operate with a smart accessory that can automatically set up parameters related to the pump, thereby reducing the setup complexity for the user.

[0005] According to various aspects, the present technology includes a first sensor unit configured to be removably coupled to a first portion of a fluid connector assembly, and a second sensor unit configured to be removably coupled to a second portion of the fluid connector assembly and configured to be detected by the first sensor unit. Here, the first sensor unit includes a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, a transmitter configured to transmit an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the first and second sensor units. Here, the first and second sensor units are configured such that the threshold distance is satisfied when the first and second portions of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second portions are not coupled to each other, providing a fluid flow interruption alarm system. Other aspects include corresponding methods, apparatus, and computer program products for implementing corresponding systems and their features.

[0006] According to some embodiments, the disconnect sensor comprises a first sensor unit configured to be removably coupled to a first portion of a fluid connector assembly, and a second sensor unit configured to be removably coupled to a second portion of the fluid connector assembly and configured to be detected by the first sensor unit, wherein the first sensor unit comprises a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, comprises a transmitter configured to transmit an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the disconnect sensor, wherein the first and second sensor units are configured such that the threshold distance is satisfied when the first and second portions of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second portions are not coupled to each other. Other aspects include corresponding systems, methods, and computer program products for embodiments of the above features.

[0007] It will be understood that other configurations of the present technology will be readily apparent to those skilled in the art from the following detailed description, which illustrates and describes various configurations of the present technology by way of example. As will be appreciated, the present technology is capable of other different configurations and some details thereof may be modified in various other respects without departing from the scope of the present technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.

[0008] To enhance understanding of the various embodiments described, reference should be made to the following description of the embodiments in conjunction with the following drawings. Throughout the drawings and the description, like reference numerals refer to corresponding parts.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2A

Figure 2B

Figure 3A

Figure 3B

Figure 4A

Figure 4B

Figure 5

Figure 6A

Figure 6B

Figure 7A

Figure 7B

Figure 8A

Figure 8B

Figure 9

Figure 10

[0010] 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 implementations described. It will be apparent, however, to one of ordinary skill in the art that the various implementations described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

[0011] The present technology includes accessories or additional products that can be used with a fluid connector assembly for an IV set cutting event, or fuse connectors. In particular, the present technology provides a cutting alarm that alerts a clinician when a cut occurs in an IV line, especially when a fuse type connector assembly is used. The alert is provided wirelessly to the clinician (e.g., via a text message or email, or a notification to a designated clinician station) and / or can be provided via a server in a hospital network. Upon receiving the alert, the clinician can immediately attend to the patient and rejoin the two halves of the connector. The disclosed cutting sensor is intended to minimize the time during which a patient's medication is stopped by alerting the clinician more quickly than can be detected by an intermittent patient status check that fluid administration has been interrupted.

[0012] Figure 1 shows an example of a patient care system 100 within a healthcare organization's facility according to an aspect of the present technology. In Figure 1, a patient care device (or generally "medical device") 12 is connected to a hospital network 10. The term "patient care device" (or "PCD: patient care device") may be used interchangeably with the term "patient care unit" (or "PCU: patient care unit"), and in either case, various ancillary medical devices may be included, such as infusion pumps, vital sign monitors, drug dispensing devices (e.g., cabinets, totes), drug preparation devices, automated dispensing devices, modules coupled to one of the foregoing (e.g., a syringe pump module configured to attach to an infusion pump), or other similar devices. Each element 12 is connected to the internal healthcare network 10 by a transmission channel 31. The transmission channel 31 is any wired or wireless transmission channel, such as an 802.11 wireless local area network (LAN). In some implementations, the network 10 also includes computer systems located in various departments throughout the hospital. For example, the network 10 in Figure 1 optionally includes an inpatient department, a billing department, a biomedical engineering department, a clinical laboratory, a central supply department, one or more unit station computers, and / or a computer system associated with a medical decision support system. As further described below, the network 10 may include individual sub-networks. In the illustrated example, the network 10 includes a device network 40, and the patient care devices 12 (and other devices) communicate according to normal operation via that device network 41.

[0013] Additionally, the in-facility patient care system 100 can incorporate a separate information system server 30, the functions of which will be described in more detail below. Further, although the information system server 30 is shown as a separate server, if desired by the engineer designing the facility's information system, the functions and programming of the information system server 30 may be incorporated into another computer. The in-facility patient care system 100 may further include one or more device terminals 32 for connecting to and communicating with the information system server 30. The device terminals 32 may include personal computers, personal data assistants, mobile devices such as laptops, tablet computers, augmented reality devices, or smartphones configured to have software for communicating with the information system server 30 via the network 10.

[0014] The patient care device 12 comprises a system for providing patient care, such as that described in U.S. Patent No. 5,713,856 to Eggers et al., which is incorporated herein by reference for its purpose. The patient care device 12 may include or incorporate a pump, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), treatment devices, and other drug delivery devices may be utilized in accordance with the teachings described herein. In the illustrated example, the patient care device 12 comprises an interface device 14, also referred to as an interface unit 14, connected to one or more functional modules 16, 18, 20, 22. 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 includes, although not necessarily, a non-volatile main memory unit 56, such as a hard disk drive or non-volatile flash memory for storing software and data, and one or more internal buses 64 for interconnecting the aforementioned elements.

[0015] In various implementations, the user interface device 54 is a touch screen for displaying information to the user and enabling the user to input information by touching defined areas of the screen. Additionally or alternatively, the user interface device 54 may 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 may be a barcode reader capable of scanning and interpreting data printed in a barcode format. Additionally or alternatively, the data input device 60 may be any device for inputting coded data into a computer, such as a device for reading magnetic strips, a radio-frequency identification (RFID) device where digital data encoded in an RFID tag or smart label (defined below) is captured by the reader 60 via radio waves, PCMCIA smart cards, radio-frequency cards, memory sticks, CDs, DVDs, or other analog or digital storage media. Other examples of the data input device 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 may be the same device. Although FIG. 1 shows the data input device 60 disposed within the interface unit 14, it is recognized that the data input device 60 may be incorporated within the pharmacy system 34 or located externally and communicate with the pharmacy system 34 via an RS-232 serial interface or any other suitable communication means. The auxiliary interface 62 may be an RS-232 communication interface, but any other means for communicating with peripheral devices such as printers, patient monitors, infusion pumps, or other medical devices may be used without departing from the present technology.Additionally, data input device 60 can be separate functional modules such as modules 16, 18, 20, and 22, and may be configured to communicate with controller 14 or any other system on the network using suitable programming and communication protocols.

[0016] Network connection 52 can be a wired or wireless connection, such as by Ethernet®, WiFi, BLUETOOTH®, integrated services digital network (ISDN) connection, digital subscriber line (DSL) modem, or cable modem. Without limitation, any direct or indirect network connection can be used, including, but not limited to, telephone modems, MIB systems, RS232 interfaces, auxiliary interfaces, optical links, infrared links, radio frequency links, microwave links, personal area network connections, local area network connections, cellular links, or WLAN connections or other wireless connections.

[0017] Functional modules 16, 18, 20, 22 are any devices for providing care to a patient or monitoring a patient's condition. As shown in FIG. 1, at least one of functional modules 16, 18, 20, 22 can be an infusion pump module, such as an intravenous infusion pump for delivering a drug or other infusion to a patient. For the purposes of this description, functional module 16 is an infusion pump module. Each of functional modules 18, 20, 22 can be any device for patient treatment or monitoring, including, but not limited to, an infusion pump, syringe pump, patient-controlled analgesia (PCA) pump, epidural pump, enteral pump, blood pressure monitor, pulse oximeter, EKG monitor, EEG monitor, heart rate monitor, or intracranial pressure monitor. Functional modules 18, 20, and / or 22 can be a printer, scanner, barcode reader, or any other peripheral input, output, or input / output device.

[0018] Each of the functional modules 16, 18, 20, 22 communicates directly or indirectly with the interface unit 14, and the interface unit 14 provides overall monitoring and control of the device 12. The functional modules 16, 18, 20, 22 may be physically and electronically connected in a serial manner to one or both ends of the interface unit 14, as shown in FIG. 1 or as detailed in Eggers et al. However, it is recognized that other means may be utilized to connect the functional modules to the interface unit without departing from the present technology. It will also be understood that a device such as a pump or patient monitoring device that provides sufficient programmability and connectivity can operate as a stand-alone device and communicate directly with a network without being connected via a separate interface unit or control unit 14. As described above, additional medical devices or peripheral devices may be connected to the patient care device 12 via one or more auxiliary interfaces 62.

[0019] Each of the functional modules 16, 18, 20, 22 may include module-specific components 76, a microprocessor 70, a volatile memory 72, and a non-volatile memory 74 for storing information. Although four functional modules are shown in FIG. 1, it should be noted that any number of devices may be directly or indirectly connected to the central controller 14. The number and types of functional modules described herein are for illustrative purposes only and do not limit the scope of the present technology in any way. The module-specific components 76 include any components necessary for the operation of a particular module, such as a pumping mechanism for the infusion pump module 16.

[0020] Each functional module may be capable of at least a level of independent operation, while the interface unit 14 monitors and controls the overall operation of the device 12. For example, as will be described in more detail below, the interface unit 14 provides programming instructions to the functional modules 16, 18, 20, 22 and monitors the status of each module.

[0021] The patient care device 12 is capable of operating in several different modes or personalities, each personality being defined by a configuration database. The configuration database may be an internal database 56 of 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 the patient's location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, the patient's diagnosis, treatment prescription, medical history, medical records, identification information of the patient care provider, physiological characteristics or psychological characteristics. Patient-specific information as used herein also includes care provider information (e.g., identification information of a physician), or the location of the patient care device 10 in a hospital or a hospital computer network. Patient care information may be input via interface devices 52, 54, 60, or 62, and may originate from any location within the network 10, such as a pharmacy server, an admission server, a laboratory server, etc.

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

[0023] Data exchanged between various data sources can be converted into network-compatible data using existing technologies, and information transfer between medical devices and a network can be achieved by various means. For example, patient care device <12> and network <10> may communicate via automated dialogue, manual dialogue, or a combination of both automated and manual dialogue. The automated dialogue may be continuous or intermittent and may be via a direct network connection <54> (as shown in FIG. 1), or via an RS232 link, an RF link such as a MIB system, BLUETOOTH (registered trademark), an IR link, a PAN, a LAN, a WLAN, a digital cable system, a telephone modem, or any other wired or wireless communication means. Manual dialogue between patient care device <12> and network <10> includes physically transferring data intermittently or periodically between systems using, for example, user interface device <54>, a coded data input device <60>, a barcode, a computer disk, a portable data assistant, a memory card, or any other medium for storing data. The communication means in various embodiments is two-way communication by accessing data from as many possible locations of the distributed data source as possible. Decision-making may be performed at various locations within network <10>. For example, but not limited to, in HIS server <30>, decision support <48>, remote data server <49>, a hospital department or unit station <46>, or within patient care device <12> itself, a decision can be made.

[0024] All direct communication with medical devices operating on the network according to this technology may be carried out via an information system server 30 known as a remote data server (RDS). According to aspects of this technology, a network interface module incorporated in a medical device, such as an infusion pump or a vital sign measurement device, for example, ignores all network traffic not originating from an authenticated RDS. The main role of the RDS of this technology is to track the location and status of all networked medical devices having NIMs and maintain open communication.

[0025] In some implementations, the drug delivery modules 16, 18, 20, 22 include a plug-in port for expansion. Thus, a new drug delivery module can be attached to the PCU 12 by coupling a connector through the plug-in port, which may include electrical terminals such that the added drug delivery modules 16, 18, 20, 22 can send and receive information to and from the control module 14. In some implementations, the added drug delivery modules 16, 18, 20, 22 may also receive power from the control module 14 through the plug-in port. The control module 14 may include a main display, memory, and a processor (see FIG. 5) and may be configured to display operating parameters, drug delivery status, and further information associated with each of the drug delivery modules 16, 18, 20, 22. According to various implementations, the module display may also display physiological data (e.g., vital signs) associated with the patient.

[0026] The main display (e.g., I / O 54) may be configured to display one or more user interfaces for the display of operating parameters or other data associated with modules 16, 18, 20, 22 and / or physiological parameters associated with a patient. The main display may include a plurality of user interfaces, and each individual user interface graphically displays information for each of the drug modules, including information that is also displayed on the corresponding module display. In some implementations, control module 14 includes a controller and / or a communication module configured to communicate wirelessly with a network (e.g., including an antenna).

[0027] Referring to FIG. 1, when drug delivery modules 16, 18, 20, 22 initiate the infusion of a drug to a patient, control module 14 is configured to create and manage an infusion session in the memory of the control module (or related module). For the purposes of the present disclosure, an infusion session includes state information of the PCU 12, its control module 14, and / or its related modules that is recorded and stored in memory during a particular time period. The state information includes, but is not limited to, the recording of parameter values utilized by the PCU, its control module, and / or its related modules during the time period and / or the recording of physiological data collected during the time period. During the infusion, physiological data associated with the patient is recorded within the session, i.e., within the operating parameter values, and modifications to the operating parameters of the PCU, its control module, and / or the modules are also recorded during the session.

[0028] If not yet logged in to the PCU12, the clinician may scan his or her badge in proximity to sensors (e.g., 54, 60) on the PCU12, and the PCU may attempt to authenticate the clinician by transmitting the scanned identification information of the clinician to the server 30. The clinician's badge may incorporate a radio frequency identification device (RFID) that is read by a scanner integrated with the PCU or a portable scanner associated with the PCU. The clinician may scan his or her badge in the control module 14 to identify and authorize the clinician to initiate the administration of medication. When the clinician is associated with the PCU and / or module, the clinician's identification information is associated with the session. The same applies to the patient. The clinician may scan the patient's wristband using a portable scanner or using a sensor on the PCU12 (or its control module) to associate the patient with the PCU and / or module (and session).

[0029] The control unit 14 of the PCU12 is configured to generate a graphical representation of the infusion session and display (e.g., on a display) a graphical representation that includes all the parameters of the infusion during the session, along with the physiological data acquired during the session and a graphical visualization of the modifications to the parameters. The graphical representation may include a pseudo-identifier for unknown data until such data is replaced with known identifiers.

[0030] Figures 2A and 2B are conceptual diagrams illustrating an exemplary modular fluid connector assembly 101 according to aspects of the present technology. The fluid connector assembly 101 can be directed to any modular fluid delivery system having two or more parts 102, 104 that can be connected to each other to form a fluid channel. For example, the fluid connector assembly can include a first component configured to connect to intravenous (IV) tubing and a second component including a luer for connection to a catheter or other subcutaneous insertion device. The system shown includes first and second portions 102, 104 of a fuse type connector. The first portion 102 of the fluid connector assembly 101 includes a first portion of a valve (not shown) and a first fluid passage therein. The second portion of the fluid connector assembly 101 includes a second portion of the valve and a second fluid passage therein. According to some implementations, the second assembly is configured to couple to the first assembly to form a continuous fluid path with the valve and functions as a fuse to stop fluid flow when it is severed. When the two components are connected, the fluid flow is open from end to end, for example, fluid can flow from the IV tubing to the patient. When a force is applied to the device and / or line, the device components can separate and stop the fluid flow through the device. An exemplary assembly for an implementation of the present technology is described in U.S. Application No. 63 / 217,165, filed June 30, 2021, which is hereby incorporated by reference in its entirety.

[0031] Figures 3A and 3B are conceptual diagrams illustrating an exemplary fluid flow interruption sensor system according to aspects of the present technology. According to various implementations, the fluid flow interruption sensor system includes a first sensor unit 112 configured to be removably coupled to a first portion 102 of a fluid connector assembly, and a second sensor unit 114 configured to be removably coupled to a second portion 104 of the fluid connector assembly 101. According to various implementations, the second sensor unit 114 is configured to be detected by the first sensor unit 112. In some implementations, the first sensor unit may be configured to be detected by the second sensor unit.

[0032] As further described, the first sensor unit 112 includes a sensor configured to detect when the second sensor unit 114 is within a threshold distance of the first sensor unit 112. The sensor may be housed within the body of the sensor unit 112. For purposes of the present disclosure, "threshold distance" is used to convey or describe the arrangement of the two sensor units and may not describe a specific distance. For example, the threshold distance may include a distance inferred from the arrangement and / or it may be a result or consequence of that implementation using the fluid connector assembly 101. The first sensor unit 112 (or the second sensor unit 114) includes a transmitter configured to transmit, in response to the detection, an indication as to whether the first and second portions 102, 104 of the fluid connector assembly 101 are coupled to each other to a device remote from the unit.

[0033] Each of the sensor units 112, 114 can be rectangular or square, and a pair of parallel locking appendages 115 extend from its sides as shown by FIGS. 3A and 3B. As also shown, each part 102, 104 of the fluid connector assembly 101 can be configured with one or more interfacing tabs 116 configured to receive the locking appendages. The interfacing tabs 116 can be formed as part of the body of the component part or can be removably connected to the body of the component, for example, by snap - fitting around the body. Each tab 116 can include an aperture (or keyway) 118. The locking appendage can include interfacing teeth 119 (for example, each having a one - directional ridge) that are received into the aperture 118 and can lock the sensing unit in a predetermined position. In this regard, the first sensor unit 112 can be configured to be removably coupled to the first part 102 of the fluid connector assembly 101 via one or more first tabs 116a fixed outside the first part 102 of the fluid connector assembly, and the second sensor unit 114 can be configured to be removably coupled to the second part 104 of the fluid connector assembly 101 via one or more second tabs 116b fixed outside the second part 104 of the fluid connector assembly.

[0034] According to various implementations, when each sensor unit 112, 114 is coupled to its respective part 102, 104 of the fluid connector assembly 101, the appendages straddle the connector assembly at opposite sides of the connector assembly such that each sensor unit 112, 114 is held against the side of the fluid connector assembly as shown in FIG. 3A and locks into each keyway 118 within the tabs 116 of assemblies 102, 104 at the opposite sides.

[0035] As shown, the body (or housing) 120 of each sensing unit 112, 114 can form a partial rectangle that is bored out such that one side forms around a connector assembly. The upper majority portion 120 of each sensor unit can have at least 1 / 2 of the mass of the entire sensor unit. The lateral sides (e.g., perpendicular to the fluid path) of the majority portion can extend to the appendage such that the lateral sides of the partial rectangle's sides and appendage, and the upper portion of the majority portion form another side. What becomes the fourth side is bored out to form around the connector assembly as shown. When installed, the sensor unit is held by a locking appendage at a position perpendicular to the side of the connector assembly between tabs, as shown in FIG. 3A. The longitudinal sides (e.g., in the direction of the fluid path) are substantially flat. In some implementations, each sensor unit 112, 114 has at least one flat side that faces the flat side of another sensor unit when the sensor unit is held in place by a locking appendage.

[0036] Figures 4A and 4B show an exemplary fluid flow interruption sensor system used with an exemplary modular fluid connector system according to aspects of the present technology. FIG. 4A shows an exploded illustration. As shown, the fluid connector assembly 101 can include a first fuse portion 102 tube end configured to prime with fluid from IV tubing 106 (from infusion pump 12), and a second fuse portion 104 configured as a luer end for connection to a catheter 122. The sensor units 112, 114 are shown above the fluid connector assembly 101 and are ready for insertion / docking into respective tabs 116 of the fluid connector system 101. FIG. 4B shows the completed assembled system 130.

[0037] Figure 5 shows an exemplary clinician station 132 that includes a computing device for use with the disclosed cutting sensor according to aspects of the present technology. According to various aspects of the present technology, the transmitter of the sensor unit 112 can be configured to wirelessly connect to a remote computing device 32. The transmitter can include a short-range wireless communication circuit for pairing with a corresponding receiver and communicating data with the corresponding receiver. For example, the sensor unit 112 can communicate using Bluetooth®. In such a case, the sensor unit 112 can be paired with a Bluetooth®-compatible device such as a laptop, desktop, or mobile device. In some implementations, the sensor unit can communicate using radio-frequency (RF) transmission. In some implementations, a dongle 134 can be utilized in the computing device to provide receiving and transmitting capabilities to the computing device 32. In some implementations, wired technology can be utilized, particularly in situations where wireless communication can interfere with other systems. For example, a wire / tether can extend between the dongle 134 and the sensor unit 112 to provide communication between the sensor unit and the computing device.

[0038] According to various implementations, a non-transitory computer-readable medium can be provided that includes software for the computing device 32 to execute to enable communication with the cutting sensor and interoperability with other medical systems such as the infusion pump 12 and the med station. The software can be loaded onto a USB stick that is associated with or incorporated into the cutting sensor (e.g., in the first sensor unit 112). The software can be compatible with the operating system of the terminal computer 32.

[0039] Referring briefly to FIGS. 3A and 10, the cut sensor system may include a microprocessor and / or a memory device. In this regard, the memory device may be used to store information such as patient identifiers. A scanning device (not shown) may be integrated with or connected to the computing device. Software may be initiated in the computing device by scanning or entering the identifier of the cut sensor in relation to the setup of the infusion pump 12 for administering a drug to the patient. The clinician may begin the pump setup workflow (e.g., via input devices 54, 60, or 62 on the PCU 12 and / or via the terminal 32), scan the identifier on the sensor unit (e.g., the barcode, QR code (registered trademark), or RFID tag in the second sensor unit 114), scan the identifier on the fluid connector assembly 101, enter the patient identifier, connect the IV set (e.g., an IV tubing catheter, etc.), and initiate the infusion. In some implementations, a barcode scanner may be integrated with or connected to the PCU 14 (e.g., input devices 54, 60, or 62 on the PCU 12).

[0040] According to some implementations, software operating on a computing device associates a patient identifier with first and second sensor units 112, 114 and stores the patient identifier in a memory device (e.g., in a local memory or database 37 associated with server 30). During operation, an indication that a disconnection sensor has detected a disconnection, e.g., whether a second sensor unit is within a threshold distance of a first sensor unit, is transmitted from sensor unit 112 to the computing device (e.g., via a wireless connection). The patient identifier locally stored by disconnection sensor 101 is transmitted in connection with a change in the disconnection status (e.g., being connected or disconnected). In this regard, the computing device may monitor (e.g., via dongle 134) whether the patient identifier has changed by connecting different parts of the fluid connector device to different patients. Upon a change in the connection status, the computing device verifies that the received patient identifier is associated with first and second sensor units 112, 114. If the computing device detects a change, an alert may be provided audibly or visually on a display screen. When a change is detected or periodically, the computing device may provide the coupling status of the first and second portions of the fluid connector assembly and whether the acquired patient identifier is associated with the first and second sensor units. In some implementations, the sensor may not need to transmit a disconnection alert signal to dongle 134 until a disconnection is detected.

[0041] Figures 6A and 6B show first and second exemplary implementations of a sensor activation mechanism for a disclosed cutting sensor system, according to various aspects of the present technology. In some implementations, a body (or majority) portion 120 of one of the sensor units has an overhang portion 140 that extends away from each sensor for alignment with and coupling to an interface 142 on a body portion 120 of the other sensor unit when the first and second sensor units 112, 114 are held by a locking appendage 115 and the first and second portions 102, 104 of the fluid connector assembly 101 are coupled together. In some implementations, as shown in FIGS. 6A and 6B, the interface portion 142 can be in the form of a notch into which the overhang portion 140 of the other unit can slide. In this way, the sensor units are forced into alignment when joined together. In the example shown, the second sensor unit 114 includes the overhang, although in some implementations, the first sensor unit 112 may include the overhang.

[0042] Figures 7A and 7B show an example in which sensor activation occurs during the coupling of the first and second portions 102, 104 of the fluid connector assembly. Referring to FIGS. 6 and 7, according to various implementations, the interface or overhang portion includes a trigger contact 144 where the overhang portion 140 is aligned with the interface 142 and is activated in response to being coupled to the interface 142. In the example of FIG. 6A, the trigger contact is a contact for completing an electrical circuit. In this regard, the trigger contact 144a includes two conductive pads that provide current within the device detected by the sensor when shorted, and the device reads that short as the two portions being coupled. In this way, the break sensor can determine that portions 112, 114 are not coupled when the pads are not shorted. The overhang portion includes conductive pads below the overhang that overlap and contact the electrical pads 144a when the two portions are joined, causing a short.

[0043] In the example of FIG. 6B, the trigger contact 144b includes a push button. In the illustrated implementation, the push button is activated by the overhang when the overhang 140 slides into the interface 142 in which the push button is disposed. The overhang 142 slides into the interface 140, and by anchoring the sensor unit to the respective portions of the fluid connector assembly 101, the overhang causes the button 144b to be depressed, causing the break sensor to detect that the portions are coupled. The break sensor can determine that the portions are not coupled when the button is not depressed.

[0044] Figures 8A and 8B show a third exemplary implementation of a sensor-activation mechanism for a disclosed cutting sensor according to various aspects of the present technology. In the illustrated implementation, the trigger contact 144c includes one of the sensor units that incorporates an electronic tag (e.g., an RFID chip), and the other sensor unit that incorporates a sensor configured to detect the electronic tag while the first and second portions of the fluid connector assembly are joined together to form the fluid connector assembly 101 such that the first and second sensor units are brought together. In the illustrated example, the second sensor unit 114 includes the electronic tag, and the first sensor unit 112 includes a sensor for detecting the tag within the sensor 114.

[0045] In some implementations (e.g., in FIG. 8B), the sensor is configured to detect the presence of the tag when the tag is sufficiently close to the sensor such that the first and second portions 102, 104 of the fluid connector assembly 101 are connected (and the sensor units are in contact with each other or sufficiently close to each other). Similarly, the sensor is configured to no longer detect the presence of the electronic tag when the first and second portions of the fluid connector assembly are decoupled such that the first and second sensor units are moved away from each other. As previously explained, the sensor unit responsible for detecting the tag may be configured to send a coupling status indication when the presence of the electronic tag has been detected or is no longer detected. The overhang portion 140 is used in the illustrated implementation, but it should be noted that the overhang portion 140 and the corresponding interface 142 may be included in each sensor unit 112, 114 for proper alignment of the units if desired.

[0046] Figure 9 shows an exemplary process for operating a cutting sensor and an alarm system according to an aspect of the present technology. For the sake of explanation, the various blocks of the exemplary process 900 are described herein with reference to FIGS. 1-8, as well as the components and / or processes described herein. For the sake of explanation, the blocks of the exemplary process 900 are described as being performed serially or linearly. However, multiple blocks of the exemplary process 900 may be performed in parallel. In addition, the blocks of the exemplary process 900 need not be performed in the order shown, and / or one or more of the blocks of the exemplary process 900 need not be performed.

[0047] In the example shown, a first sensor unit configured to be removably coupled to a first portion of a fluid connector assembly is provided (402). A second sensor unit configured to be removably coupled to a second portion of the fluid connector assembly and configured to be detected by the first sensor unit is also provided (404). As previously explained, the first sensor unit may include a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, may include a transmitter configured to transmit an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the first and second sensor units. The first and second sensor units may be configured such that the threshold distance is satisfied when the first and second portions of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second portions are not coupled to each other.

[0048] According to some implementations, at least the second sensor unit includes a memory device for storing a patient identifier. A computer-readable medium is further provided to the device (406). The computer-readable medium stores instructions that, when executed by a computing device, cause the computing device to perform operations for operating the disconnect sensor. The operations may include steps that may be included in process 400 or may be the subject of a separate process.

[0049] According to various implementations, the operations performed by the instructions include associating a patient identifier with the first and second sensor units in a computing device (408), storing the patient identifier in the memory device (410), receiving an indication as to whether the second sensor unit is within a threshold distance of the first sensor unit (412), and obtaining the patient identifier from at least the first sensor unit in relation to receiving an indication that the first and second portions of the fluid connector assembly are coupled to each other in response to detection (414). The process may further include verifying whether the obtained patient identifier is associated with the first and second sensor units (416), and providing the coupling status of the first and second portions of the fluid connector assembly and whether the obtained patient identifier is associated with the first and second sensor units for display based on the obtaining and verifying (418).

[0050] According to various implementations, the clinician's workflow begins by verifying that the dongle 134 and the software are installed on the clinician workstation 32. The clinician installs a break sensor (sensor and tag portions 112, 114) on the fluid connector assembly 101. The clinician may then register a patient identifier (e.g., patient identification number or room number) within the software and link the identifier to the break sensor. When the fluid connector assembly 101 is broken, the sensor portion 112 of the break sensor detects that the tag portion 114 is not in contact and transmits an alert signal to the dongle 134. The clinician may then reconnect the connector assembly and restore contact between the first and second portions 112, 114 of the break sensor, and drug administration may continue.

[0051] In some implementations, the first and / or second sensor units 112, 114 may include a piezoelectric circuit configured to generate an audible alarm. When the fluid connector assembly 101 is broken, the piezoelectric circuit may be commanded to generate an alarm. The command may be a signal generated within the sensor unit or transmitted from the dongle 134. In this way, the audible alarm comes from the separate connector itself, in addition to or instead of the remote system alarm described above.

[0052] Example 400 described above, as well as many of the related features and applications, may also be implemented as a software process embodied as a set of instructions recorded on a computer-readable storage medium (also referred to as a computer-readable medium), which can be executed automatically (e.g., without user intervention). When these instructions are executed by one or more processing units (e.g., one or more processors, cores of a processor, or other processing units), they cause the processing unit to perform the actions specified in the instructions. Examples of computer-readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. A computer-readable medium does not include carrier waves and electronic signals passing wirelessly or via a wired connection.

[0053] The term "software" is intended to include, where appropriate, firmware that resides in read-only memory, which can be loaded into memory for processing by a processor, or an application stored on magnetic storage. Also, in some implementations, multiple software aspects of the present disclosure may be implemented as sub-parts of a larger program while remaining separate software aspects of the present disclosure. In some implementations, multiple software aspects may also be implemented as separate programs. Finally, any combination of separate programs that implement the software aspects described herein together is within the scope of the present disclosure. In some implementations, when a software program is installed to operate on one or more electronic systems, it defines one or more specific machine implementations that execute and implement the operation of the software program.

[0054] (Also known as a program, software, software application, script, or code) A computer program can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and 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. The computer program may, but is not required to, correspond to a file in a file system. The program can be stored in a part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). The computer program can be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0055] FIG. 10 is a conceptual diagram illustrating an exemplary electronic system 500 for a cutting sensor and an alarm system according to an aspect of the present technology. The electronic system 500 can be software associated with one or more parts or steps of process 500, including but not limited to an information system / server 30, a database 37, computing hardware within a patient care device 12, or a remote device 32 (e.g., a mobile device), or a computing device for executing the components and processes provided by FIGS. 1-9. The electronic system 500 may be representative in combination with the present disclosure regarding FIGS. 1-9. In some implementations, the electronic system 500 can be representative of circuitry within one of the sensor units 112, 114. For example, a first sensor unit 112 with an input device interface 514 can be representative of a sensor (e.g., a trigger contact 144 or an RFID reader) capable of detecting a second sensor unit 112. In this regard, the electronic system 500 can be a personal computer, or a mobile device such as a smartphone, a tablet computer, a laptop, a PDA, an augmented reality device, a wearable such as a watch or a band or glasses, or a combination thereof, or another touch screen or television with one or more processors embedded therein or coupled thereto, or any other type of computer-related electronic device having network connectivity.

[0056] The electronic system 500 may include various types of computer-readable media and interfaces for various other types of computer-readable media. In the illustrated example, the electronic system 500 includes a bus 508, a processing unit 512, a system memory 504, a read-only memory (ROM) 510, a persistent storage device 502, an input device interface 514, an output device interface 506, and one or more network interfaces 516. In some implementations, the electronic system 500 may include or be integrated with other computing devices or circuits for the operation of the various components and processes described above.

[0057] The bus 508 collectively represents all system buses, peripheral buses, and chipset buses that communicatively connect a number of internal devices of the electronic system 500. For example, the bus 508 communicatively connects the processing unit 512 to the ROM 510, the system memory 504, and the persistent storage device 502.

[0058] From these various memory units, the processing unit 512 retrieves the instructions to be executed and the data to be processed in order to execute the processes of the present disclosure. In different implementations, the processing unit can be a single processor or a multi-core processor.

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

[0060] Other implementations use a removable storage device (such as a floppy disk, flash drive, and corresponding disk drive) as the persistent storage device 502. Similar to the persistent storage device 502, the system memory 504 is a read-write memory device. However, unlike the storage device 502, the system memory 504 is a volatile read-write memory such as random access memory. The system memory 504 stores some of the instructions and data required by the processor during execution. In some implementations, the processes of the present disclosure are stored in the system memory 504, the persistent storage device 502, and / or the ROM 510. From these various memory units, the processing unit 512 retrieves the instructions to be executed and the data to be processed in order to execute the processes of some implementations.

[0061] The bus 508 is also connected to an input device interface 514 and an output device interface 506. The input device interface 514 enables a user to communicate information and selected commands to the electronic system. Input devices used with the input device interface 514 include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). The output device interface 506 enables, for example, the display of images generated by the electronic system 500. Output devices used with the output device interface 506 include, for example, a printer and a display device such as a cathode ray tube (CRT) or a liquid crystal display (LCD). Some implementations include devices such as a touch screen that function as both an input device and an output device.

[0062] Also, as shown in FIG. 10, bus 508 also couples electronic system 500 to a network (e.g., network 40 of FIG. 1) via network interface 516. Network interface 516 may include, for example, a wireless access point (e.g., Bluetooth® or WiFi) or a wireless circuit for connecting to a wireless access point. Network interface 516 may also include hardware (e.g., Ethernet® hardware) for connecting a computer to a network of computers such as a local area network (“LAN”), wide area network (“WAN”), wireless LAN, or intranet, or to a network of networks such as the Internet. Any or all of the components of electronic system 500 can be used in conjunction with the present disclosure.

[0063] These above functions may be implemented in computer software, firmware, or hardware. One or more computer program products can be used to implement the techniques. Programmable processors and computers can be included in or packaged as a mobile device. Processes and logic flows can be performed by one or more programmable processors and also by one or more programmable logic circuits. General purpose and special purpose computing devices and storage devices can be interconnected via a communication network.

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

[0065] The above description has mainly referred to a microprocessor or a multi-core processor that executes software, but some implementations are executed by one or more integrated circuits such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). In some implementations, such integrated circuits execute instructions stored in the circuit itself.

[0066] All of the terms "computer", "server", "processor", and "memory" used in the specification and any claims of this application refer to electronic devices or other technical devices. These terms exclude a person or a group of persons. For the purposes of this specification, the term "display" or "displaying" means displaying on an electronic device. The terms "computer-readable medium" and "computer-readable medium" used in the specification and any claims of this application are completely limited to tangible physical objects that store information in a form readable by a computer. These terms exclude wireless signals, wired download signals, and any other transient signals.

[0067] To provide interaction with a user, implementations of the subject matter described herein can be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, and a keyboard and a pointing device, such as a mouse or trackball, by which the user can provide input to the computer. To provide interaction with a user, other types of devices can equally be used. For example, the feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback, etc., and the input from the user can be received in any form including acoustic input, voice input, or tactile input. Further, the computer can interact with the user by sending and receiving documents to and from the devices used by the user, such as by sending a web page to a web browser on the user's client device in response to a request received from the web browser.

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

[0069] A computing system can include clients and servers. Clients and servers are generally separated from each other and may interact via a communication network. The client - server relationship is created by computer programs that are executed on respective computers and have a client - server relationship with each other. In some implementations, a server sends data (e.g., an HTML page) to a client device (e.g., to display to a user interacting with the client device and to receive user input from that user). Data generated at the client device (e.g., as a result of user interaction) can be received at the server from the client device.

[0070] One of ordinary skill 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 a combination of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality may be implemented in various ways for each particular application. Without departing from the scope of the present technology, various components and blocks may be differently configured (e.g., they may be configured in a different order or divided in a different way).

[0071] It should be understood that the specific order or hierarchy of steps in the disclosed process is for illustrative purposes. It is understood that, based on design preferences, the specific order or hierarchy of steps in the process may be reconfigured. Some of the steps may be performed simultaneously. The appended method claims present the elements of the various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0072] Exemplification as a clause of this technology: For the various examples of aspects of this disclosure, for convenience, they will be described as numbered clauses (1, 2, 3, etc.). These are provided as examples and do not limit the technology. The identification of figures and reference numbers is provided below merely as examples for the purpose of explanation, and the clauses are not limited by those identifications.

[0073] Clause 1. A first sensor unit configured to be removably coupled to a first portion of a fluid connector assembly, and a second sensor unit configured to be removably coupled to a second portion of the fluid connector assembly and configured to be detected by the first sensor unit, wherein the first sensor unit includes a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, includes a transmitter configured to transmit an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the first and second sensor units, wherein the first and second sensor units are configured such that when the first and second portions of the fluid connector assembly are coupled to each other to form the fluid connector assembly, the threshold distance is satisfied, and when the first and second portions are not coupled to each other, the threshold distance is not satisfied, a fluid flow cutoff system.

[0074] Clause 2. The fluid flow cutoff system according to Clause 1, wherein the first sensor unit is configured to be detachably coupled to the first part of the fluid connector assembly via one or more first tabs fixed outside the first part of the fluid connector assembly, and the second sensor unit is configured to be detachably coupled to the second part of the fluid connector assembly via one or more second tabs fixed outside the second part of the fluid connector assembly.

[0075] Clause 3. The fluid flow cutoff system according to Clause 2, wherein the first and second sensor units each include a pair of parallel locking appendages that straddle the respective part of the fluid connector assembly at opposite sides of the respective part of the fluid connector assembly and lock into respective key openings within the tabs of the respective part of the fluid connector assembly such that when each sensor unit is coupled to the respective part of the fluid connector assembly, the sensor unit is held against the side of the respective part of the fluid connector assembly between the tabs.

[0076] Clause 4. The fluid flow cutoff system according to Clause 3, wherein when each sensor unit is coupled to the respective part of the fluid connector assembly, a majority portion of the sensor unit having at least 1 / 2 of the mass of the sensor unit is held by the locking appendage at a position perpendicular to the side of the respective part of the fluid connector assembly between the tabs, wherein the majority portion of the first sensor unit comprises at least one flat side that faces the flat side of the majority portion of the second sensor unit when the sensor unit is held by the locking appendage.

[0077] Clause 5. The majority portion of each sensor unit comprises an overhang portion that extends away from each sensor unit to align with and couple to an interface in the majority portion of the other sensor unit when the first and second sensor units are held by the locking appendages and the first and second portions of the fluid connector assembly are coupled to each other, for the fluid flow cutoff system described in Clause 4.

[0078] Clause 6. The interface or overhang portion comprises a trigger contact that is activated in response to the overhang portion aligning with and coupling to the interface, and the first sensor unit is configured to detect the second sensor unit when the trigger contact is activated and to detect that the first and second sensor units are disconnected when the trigger contact is deactivated, for the fluid flow cutoff system described in Clause 5.

[0079] Clause 7. The trigger contact comprises a push button or contact for completing an electrical circuit, for the fluid flow cutoff system described in Clause 6.

[0080] Clause 8. The fluid flow cutoff system according to any one of Clauses 1 to 7, wherein a transmitter is configured to wirelessly transmit an instruction to a remote device.

[0081] Clause 9. The fluid flow cutoff system according to any one of Clauses 1 to 8, further comprising a first portion of the fluid connector assembly and a second portion of the fluid connector assembly, wherein the first portion of the fluid connector assembly comprises a first portion of a valve and a first fluid passage therein, and the second portion of the fluid connector assembly comprises a second portion of the valve and a second fluid passage therein, and the second portion of the fluid connector assembly is configured to be coupled to the first portion of the fluid connector assembly to form a continuous fluid path from the first and second fluid passages.

[0082] Clause 10. The second sensor unit comprises an electronic tag, and the sensor of the first sensor unit is configured to wirelessly detect the presence of the electronic tag of the second sensor unit when the first and second sensor units are brought together by the first and second portions of the fluid connector assembly being coupled to form the fluid connector assembly, and not to detect the presence of the electronic tag when the first and second portions of the fluid connector assembly are decoupled and the first and second sensor units are moved away from each other, and the first sensor unit is configured to send an indication when the presence of the electronic tag is no longer detected, of the fluid flow interruption system according to any one of Clauses 1 to 5, 8, and 9.

[0083] Clause 11. At least the second sensor unit comprises a memory device for storing a patient identifier, and the system, when executed by a computing device, causes the computing device to associate the patient identifier with the first and second sensor units in the computing device, store the patient identifier in the memory device, receive an indication as to whether the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, obtain the patient identifier from at least the first sensor unit in relation to receiving an indication as to whether the first and second portions of the fluid connector assembly are coupled to each other, confirm whether the obtained patient identifier is associated with the first and second sensor units, and provide, for display based on the obtaining and confirmation, the coupling status of the first and second portions of the fluid connector assembly and whether the obtained patient identifier is associated with the first and second sensor units, and further comprises a non-transitory computer-readable medium storing instructions that cause the above-described operations to be performed, of the fluid flow interruption system according to any one of Clauses 1 to 10.

[0084] Clause 12. The first sensor unit includes a piezoelectric circuit configured to generate an audible alarm when activated, and when the first and second portions are no longer coupled to each other such that the threshold distance is no longer satisfied, the first sensor unit is the fluid flow interruption system according to any one of Clauses 1 to 11, wherein the piezoelectric circuit is configured to cause the generation of an audible alarm.

[0085] Clause 13. A disconnect sensor comprising a first sensor unit configured to be removably coupled to a first portion of a fluid connector assembly, and a second sensor unit configured to be removably coupled to a second portion of the fluid connector assembly and configured to be detected by the first sensor unit, wherein the first sensor unit includes a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and in response to the detection, includes a transmitter configured to transmit an indication as to whether the first and second portions of the fluid connector assembly are coupled to each other to a device remote from the disconnect sensor, wherein the first and second sensor units are configured such that the threshold distance is satisfied when the first and second portions of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second portions are not coupled to each other.

[0086] Clause 14. The disconnect sensor according to Clause 13, wherein the first sensor unit is configured to be removably coupled to the first portion of the fluid connector assembly via one or more first tabs fixed outside the first portion of the fluid connector assembly, and the second sensor unit is configured to be removably coupled to the second portion of the fluid connector assembly via one or more second tabs fixed outside the second portion of the fluid connector assembly.

[0087] Clause 15. The first and second sensor units each include a pair of parallel locking appendages that straddle respective portions of the fluid connector assembly at opposing sides thereof and lock into respective key openings within tabs of respective portions of the fluid connector assembly such that when each sensor unit is coupled to a respective portion of the fluid connector assembly, the sensor unit is held against a side of the respective portion of the fluid connector assembly between the tabs, for the disconnect sensor according to Clause 14.

[0088] Clause 16. The disconnect sensor according to Clause 13 or Clause 14, wherein at least the second sensor unit is further configured to wirelessly receive a patient identifier from a computing device remote from the first and second sensor units, store the patient identifier in a memory device, and wirelessly transmit to the computing device the patient identifier and an indication as to whether the first and second portions of the fluid connector assembly are coupled to each other in response to a detection.

[0089] Clause 17. A method comprising providing a first sensor unit and a second sensor unit, wherein the first sensor unit is configured to be removably coupled to a first portion of a fluid connector assembly and the second sensor unit is configured to be removably coupled to a second portion of the fluid connector assembly, the first sensor unit being configured to be detected by the first sensor unit; receiving an indication as to whether the second sensor unit is within a threshold distance of the first sensor unit; and providing a coupling status of the first and second portions of the fluid connector assembly for display based on receiving the indication.

[0090] The method of clause 17 further comprising wirelessly receiving, at a mobile computing device remote from the first and second sensor units, an indication from the first sensor unit that the second sensor unit is no longer within a threshold distance of the first sensor unit, and providing, at the mobile computing device, an alert indicating that a first portion of the fluid connector assembly has been decoupled from a second portion of the fluid connector assembly in response to the indication that the second sensor unit is no longer within a threshold distance of the first sensor unit.

[0091] The method of clause 17 or clause 18 further comprising associating a patient identifier with the first and second sensor units, obtaining the patient identifier from at least the first sensor unit in relation to receiving an indication regarding whether the first and second portions of the fluid connector assembly are coupled to each other in response to detection, verifying whether the obtained patient identifier is associated with the first and second sensor units before providing the coupling status, and providing an indication as to whether the obtained patient identifier is associated with the first and second sensor units.

[0092] A non-transitory computer-readable memory storing instructions that, when executed, perform operations enabling the method of any one of clauses 17 to 19.

[0093] Further considerations: It should be understood that the specific order or hierarchy of steps in the disclosed process is an illustration of exemplary approaches. It is understood that, based on design preferences, the specific order or hierarchy of steps in a process may be reconfigured. Some of the steps may be performed simultaneously. The appended method claims present elements of various steps in a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0094] The foregoing description has been provided to enable a person skilled in the art to practice the various aspects described herein. The foregoing description provides illustrative examples of the technology, and the technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein, but rather should be accorded the full scope consistent with the language of the claims, and singular reference to an element is not intended to mean "sole" unless expressly so stated, but rather is intended to mean "one or more." Unless expressly stated otherwise, the term "some" refers to one or more. Masculine pronouns (e.g., "his") include feminine and neuter forms (e.g., "her" and "its"), and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.

[0095] The phrases "configured to," "operable to," and "programmed to" do not imply a particular tangible or intangible modification of a subject, but rather are intended to be used interchangeably. For example, a processor configured to monitor and control operations may also mean that the processor is programmed to monitor and control operations or is operable to monitor and control operations. Similarly, a processor configured to execute code may be construed as a processor programmed to execute code or operable to execute code.

[0096] As used herein, the term "automatically" may include performance by a computer or machine without user intervention, e.g., by instructions responsive to a predicate action by a computer or machine or other initiating mechanism. The word "example" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as an "example" should not necessarily be construed as being more preferred or advantageous than other aspects or designs.

[0097] Phrases such as "aspect" do not mean that such an aspect is essential to the technology or that such an aspect applies to all configurations of the technology. The disclosure regarding an aspect may apply to all configurations or one or more configurations. An aspect may provide one or more examples. Phrases such as "aspect" may refer to one or more aspects, and vice versa. Phrases such as "embodiment" do not mean that such an embodiment is essential to the technology or that such an embodiment applies to all configurations of the technology. The disclosure regarding an embodiment may apply to all embodiments or one or more embodiments. An embodiment may provide one or more examples. Phrases such as "embodiment" may refer to one or more embodiments, and vice versa. Phrases such as "configuration" do not mean that such a configuration is essential to the technology or that such a configuration applies to all configurations of the technology. The disclosure regarding a configuration may apply to all configurations or one or more configurations. A configuration may provide one or more examples. Phrases such as "configuration" may refer to one or more configurations, and vice versa.

[0098] As used herein, a "user interface" (also referred to as an "interactive user interface", "graphical user interface", or "UI") can refer to a network-based interface that includes data fields and / or other control elements for receiving input signals or providing electronic information and / or for providing information to a user in response to any received input signal. Control elements can include dials, buttons, icons, selectable areas, or other perceivable indicators presented via the UI that initiate data exchanges for a device presenting the UI when interacted with (e.g., clicked, touched, selected, etc.). The UI can be implemented in whole or in part using technologies such as hyper-text mark-up language (HTML), FLASH®, JAVA®, .NET®, C, C++, web services, or rich site summary (RSS). In some embodiments, the UI can be included in a stand-alone client (e.g., a thin client, a fat client) configured to communicate (e.g., send or receive data) according to one or more of the described manners. The communication can be between a medical device and a server that communicates with it.

[0099] As used herein, the term "determine" or "determining" encompasses a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, generating, obtaining, retrieving (e.g., retrieving within a table, database, or another data structure), validating, etc. via a hardware element without user intervention. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. via a hardware element without user intervention. "Determining" can include solving, selecting, choosing, establishing, etc. via a hardware element without user intervention.

[0100] As used herein, the term "provide" or "providing" encompasses a wide variety of actions. For example, "providing" can include storing a value at a location in a storage device for later retrieval, directly transmitting a value to a receiving side via at least one wired or wireless communication medium, transmitting or storing a reference to a value, etc. "Providing" can also include encoding, decoding, encrypting, decrypting, authenticating, verifying, etc. via a hardware element.

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

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

[0103] As used herein, the term "corresponding" or "correspondingly" when used to describe a relationship between two or more elements, encompasses a structural, functional, quantitative, and / or qualitative correlation or relationship between two or more objects, data sets, information, etc., and preferably here, the correspondence or relationship can be used to transform one or more of the two or more objects, data sets, information, etc. to appear the same or equivalent. The correspondence may be evaluated using one or more of a threshold, a range of values, fuzzy logic, pattern matching, a machine learning evaluation model, or a combination thereof.

[0104] In any of the embodiments, the generated or detected data can be transferred to a "remote" device or location, where "remote" means a location or device other than the location or device where the program is executed. For example, a remote location can be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, or another location in a different country. Thus, if an item is shown to be "remote" from another item, this means that the two items may be in the same room but separated or at least in different rooms or different buildings, and that the two items may be at least 1.61 km (1 mile), 16.1 km (10 miles), or 161 km (100 miles) apart. "Communicating" information refers to transmitting data representing that information as an electrical signal via a suitable communication channel (e.g., a private or public network). "Transferring" an item refers to any means of moving that item from one location to the next, whether by physically transporting the item or (if possible) by other means, and in the case of at least data, includes physically transporting the medium carrying the data or communicating that data. Examples of communication media include wireless or infrared transmission channels, as well as network connections to another computer or networked device, and including the Internet, or electronic mail transmission and information recorded on a website, etc.

Claims

1. A first sensor unit configured to be detachably coupled to a first portion of a fluid connector assembly, A second sensor unit is configured to be detachably coupled to a second portion of the fluid connector assembly and to be detected by the first sensor unit. Equipped with, Herein, the first sensor unit comprises a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and a transmitter configured to transmit, in response to the detection, an instruction from the first and second sensor units to a remote device regarding whether the first and second parts of the fluid connector assembly are coupled to each other. Herein, the first and second sensor units are configured such that the threshold distance is satisfied when the first and second parts of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second parts are not coupled to each other. Fluid flow cutting system.

2. The fluid flow cutting system according to claim 1, wherein the first sensor unit is configured to be detachably coupled to the first portion of the fluid connector assembly via one or more first tabs fixed to the outside of the first portion of the fluid connector assembly, and the second sensor unit is configured to be detachably coupled to the second portion of the fluid connector assembly via one or more second tabs fixed to the outside of the second portion of the fluid connector assembly.

3. The fluid flow cutting system according to claim 2, wherein the first and second sensor units each include a pair of parallel locking appendages that straddle the respective parts of the fluid connector assembly at opposing sides of the respective parts of the fluid connector assembly and lock into the respective key openings in the tabs of the respective parts of the fluid connector assembly at the opposing sides, so that when the respective sensor unit is coupled to the respective part of the fluid connector assembly, the sensor unit is held against the sides of the respective parts of the fluid connector assembly between the tabs.

4. A fluid flow cutting system according to claim 3, wherein when each sensor unit is coupled to the respective part of the fluid connector assembly, the majority portion of the sensor unit having at least half of the mass of the sensor unit is held by the locking appendage between the tabs in a position perpendicular to the sides of the respective parts of the fluid connector assembly, wherein the majority portion of the first sensor unit has at least one flat side facing the flat side of the majority portion of the second sensor unit when the sensor unit is held by the locking appendage.

5. The fluid flow cutting system according to claim 4, wherein the majority portion of each sensor unit has an overhang portion that aligns with the interface on the majority portion of the other sensor unit and extends away from the respective sensor unit in order to connect to the interface when the first and second sensor units are held by the locking appendage and the first and second portions of the fluid connector assembly are coupled to each other.

6. The fluid flow cutting system according to claim 5, wherein the interface or the overhang portion comprises a trigger contact which is activated in response to the overhang portion being aligned with and coupled to the interface, and the first sensor unit is configured to detect the second sensor unit when the trigger contact is activated, and to detect that the first and second sensor units are disconnected when the trigger contact is deactivated.

7. The fluid flow cutting system according to claim 6, wherein the trigger contact comprises a push button or contact for completing an electrical circuit.

8. The fluid flow cutting system according to any one of claims 1 to 7, wherein the transmitter is configured to wirelessly transmit the instructions to the remote device.

9. The fluid connector assembly further comprises the first part and the second part, wherein the first part of the fluid connector assembly comprises a first part of a valve and a first fluid passage therein. Herein, the second portion of the fluid connector assembly comprises the second portion of the valve and a second fluid passage therein, and the second portion of the fluid connector assembly is configured to be coupled to the first portion of the fluid connector assembly to form a continuous fluid path from the first and second fluid passages. A fluid flow cutting system according to any one of claims 1 to 7.

10. A fluid flow cutting system according to any one of claims 1 to 5, wherein the second sensor unit comprises an electronic tag, the sensor of the first sensor unit is configured to wirelessly detect the presence of the electronic tag of the second sensor unit while the first and second sensor units are together by the coupling of the first and second parts of the fluid connector assembly to form the fluid connector assembly, and is configured to no longer detect the presence of the electronic tag when the first and second sensor units are moved away from each other by the uncoupling of the first and second parts of the fluid connector assembly, and the first sensor unit is configured to transmit the instruction when the presence of the electronic tag is no longer detected.

11. At least the second sensor unit includes a memory device for storing a patient identifier, and the system, When executed by a computing device, the computing device In the computing device, the patient identifier is associated with the first and second sensor units, The patient identifier is stored in the memory device, The second sensor unit receives the instruction regarding whether it is within the threshold distance of the first sensor unit, In response to the detection, and in connection with receiving the instruction regarding whether the first and second parts of the fluid connector assembly are coupled to each other, the patient identifier is obtained from at least the first sensor unit, To confirm whether the acquired patient identifier is associated with the first and second sensor units, For display based on the acquisition and verification, the coupling status of the first and second parts of the fluid connector assembly and whether the acquired patient identifier is associated with the first and second sensor units are provided. A non-temporary computer-readable medium that stores instructions that cause an action to be performed. A fluid flow cutting system according to any one of claims 1 to 7, further comprising the above.

12. A fluid flow interruption system according to any one of claims 1 to 7, wherein the first sensor unit comprises a piezoelectric circuit configured to generate an audible alarm when activated, and the first sensor unit is configured to cause the piezoelectric circuit to generate the audible alarm when the threshold distance is no longer met because the first and second parts are no longer coupled to each other.

13. It is a cutting sensor, A first sensor unit configured to be detachably coupled to a first portion of a fluid connector assembly, A second sensor unit is configured to be detachably coupled to a second portion of the fluid connector assembly and to be detected by the first sensor unit. Equipped with, Herein, the first sensor unit comprises a sensor configured to detect when the second sensor unit is within a threshold distance of the first sensor unit, and a transmitter configured to transmit, in response to the detection, an instruction from the disconnection sensor to a remote device regarding whether the first and second parts of the fluid connector assembly are coupled to each other. Herein, the first and second sensor units are configured such that the threshold distance is satisfied when the first and second parts of the fluid connector assembly are coupled to each other to form the fluid connector assembly, and the threshold distance is not satisfied when the first and second parts are not coupled to each other. Cutting sensor.

14. The cutting sensor according to claim 13, wherein the first sensor unit is configured to be detachably coupled to the first portion of the fluid connector assembly via one or more first tabs fixed to the outside of the first portion of the fluid connector assembly, and the second sensor unit is configured to be detachably coupled to the second portion of the fluid connector assembly via one or more second tabs fixed to the outside of the second portion of the fluid connector assembly.

15. The cutting sensor according to claim 14, wherein the first and second sensor units each include a pair of parallel locking appendages that straddle the respective parts of the fluid connector assembly at opposing sides of the respective parts of the fluid connector assembly and lock into the respective key openings in the tabs of the respective parts of the fluid connector assembly at the opposing sides, so that when the respective sensor unit is coupled to the respective part of the fluid connector assembly, the sensor unit is held against the sides of the respective parts of the fluid connector assembly between the tabs.

16. At least the second sensor unit includes a memory device for storing a patient identifier, The patient identifier is wirelessly received from a computing device located remotely from the first and second sensor units, The patient identifier is stored in the memory device, In response to the detection, the patient identifier and the instruction regarding whether the first and second parts of the fluid connector assembly are coupled to each other are transmitted wirelessly to the computing device. A cutting sensor according to claim 13 or claim 14, further configured to perform the following:

17. To provide a first sensor unit and a second sensor unit, wherein the first sensor unit is configured to be detachably coupled to a first portion of a fluid connector assembly, and the second sensor unit is configured to be detachably coupled to a second portion of the fluid connector assembly and to be detected by the first sensor unit. The second sensor unit receives an instruction regarding whether it is within the threshold distance of the first sensor unit, To indicate that the aforementioned instructions have been received, the coupling status of the first and second parts of the fluid connector assembly is provided. A method that includes [a certain feature].

18. The instruction that the second sensor unit is no longer within the threshold distance of the first sensor unit is received wirelessly from the first sensor unit on a mobile computing device located remotely from the first and second sensor units, In response to an instruction that the second sensor unit is no longer within the threshold distance of the first sensor unit, the mobile computing device provides an alarm indicating that the first portion of the fluid connector assembly has been discoupled from the second portion of the fluid connector assembly. The method according to claim 17, further comprising:

19. Associating the patient identifier with the first sensor unit and the second sensor unit, In connection with receiving an instruction regarding whether the first and second parts of the fluid connector assembly are coupled to each other in response to detection, the patient identifier is obtained from at least the first sensor unit, Before providing the aforementioned coupling status, it is confirmed whether the acquired patient identifier is associated with the first and second sensor units, To provide an indication of whether the acquired patient identifier is associated with the first and second sensor units. The method according to claim 17 or claim 18, further comprising:

20. A non-temporary computer-readable memory storing instructions that, when executed, perform an operation enabling the method according to claim 17 or 18.

Images