Electronic tag for associating and identifying intravenous administration lines

Abstract

An electronic tag includes a housing; a processor within the housing; a transceiver configured within the housing and coupled to the processor; a display coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to an intravenous (IV) tube; and a sensor configured within the housing and configured to measure a property of a fluid in the IV tube at a location of the clamping mechanism.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 066,113, entitled “ELECTRONIC TAGS FOR ASSOCIATING AND IDENTIFYING INTRAVENOUS ADMINISTRATION LINES”, filed August 14, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application typically involves associating and identifying intravenous (IV) administration lines. Background Technology

[0004] Patients receiving care in the intensive care unit and / or operating room may be connected to multiple IV dosing lines. Ensuring that each dosing line is correctly connected to the correct infusion fluid and delivered to the patient at the correct infusion rate can require significant time and manpower to track the path of each IV dosing line between the patient and the corresponding infusion pump or fluid container. The presence of more than one IV dosing line can lead to risks associated with incorrect connections or IV dosing lines not being programmed to be at the correct infusion rate when entering the infusion pump. Tape or labels may be attached to the lines with information about the medication container to which each line is attached. However, tape can detach, is difficult to read or understand, and the information may be incorrectly recorded. For safety reasons, IV dosing lines are also monitored to ensure that their use does not exceed their intended lifespan. Summary of the Invention

[0005] Information related to infusions, such as the contents of the fluid container attached to each IV line, the initiator of the IV line, and the date and time the IV line began, can be written on tape or a label and attached to the line. However, the tape may come off, be difficult to read or understand, or the information may be incorrectly recorded.

[0006] The labeling and conditioning of IV lines (a process also known as “line tracking”) can be performed by the clinician at least once per shift. Line tracking ensures that a specific medical fluid is connected to the intended channel for infusion to the intended patient. During line tracking, the clinician can check that (i) the IV delivery device has not been used beyond its intended lifespan (or expired), (ii) the fluid in the fluid container has not expired, (iii) the IV delivery line of the IV device is correctly labeled with a sticker, (iv) the infusion pump is correctly labeled, and (v) the patient’s IV site is clearly visible. The clinician can record this information as an electronic document in the patient’s electronic medical record (EMR).

[0007] Therefore, there is a need for equipment and methods to help reduce manpower and improve efficiency associated with labeling and tubing coordination. Such equipment and methods could also help improve the accuracy of expiry information provided to clinicians regarding IV devices and / or infusion medications to be administered. More accurate tubing coordination can also prevent accidental tubing swaps that result in the use of incorrect medical fluids during infusions. Accidental tubing swaps can also lead to the correct medical fluid being infused to the patient at the wrong infusion rate via the wrong infusion pump.

[0008] The disclosed subject matter relates to an electronic tag and a method for correctly associating an IV container with an IV device using the electronic tag. The electronic tag can be programmed to display information related to the infusion process, such as the name of the medical fluid to be infused, the patient's name, the name of the clinician initiating the infusion, the start time of the infusion, the expiration date of the IV device, and infusion-related barcode information. This information can be used to track and record the various steps of the infusion process, track the patient and / or medication, or for other purposes.

[0009] The disclosed device and method, in addition to tracking and identifying IV lines, include a sensor that provides real-time feedback on whether a specific IV fluid container has been correctly associated with the IV delivery device. The sensor can also monitor whether the IV fluid container is empty and issue timely notifications or warnings to clinicians.

[0010] The disclosed subject matter also relates to a system for associating a fluid container with an infusion pump. The system includes one or more processors and a memory including instructions that, when executed by the one or more processors, cause the one or more processors to perform the steps of the method described herein.

[0011] This subject matter provides an electronic tag including a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display screen coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to a vein (IV) tube; and a sensor disposed within the housing and configured to measure the properties of fluid in the IV tube at the location of the clamping mechanism. Other aspects include corresponding methods, apparatus, and computer program products for implementing the corresponding system and its features.

[0012] It will be understood that other configurations of the present subject matter will become apparent to those skilled in the art from the following detailed description, wherein various configurations of the present subject matter are illustrated and described by way of illustration. As will be appreciated, the present subject matter is capable of other and different configurations, and several details thereof can be modified in various other ways, all without departing from the scope of the present subject matter. Therefore, the accompanying drawings and detailed description should be regarded as illustrative in nature and not as limiting. Attached Figure Description

[0013] To better understand the various described embodiments, reference should be made to the following description of the embodiments in conjunction with the accompanying drawings. Throughout the drawings and description, similar reference numerals refer to corresponding parts.

[0014] Figure 1 This is a front view of a medical drug delivery system with four fluid infusion pumps according to aspects of the subject matter, each fluid infusion pump being connected to a corresponding fluid container to pump the contents of the fluid container to the patient, wherein the fluid containers are mounted on a common roller rack.

[0015] Figure 2 It is based on the technical aspects of this topic. Figure 1 An enlarged view of a portion of a medical delivery system shows two fluid infusion pumps mounted on either side of a programming module, along with a display screen and control keys for each, where the programming module is capable of programming both infusion pumps.

[0016] Figure 3 An example of an institutional patient care system for a healthcare organization based on aspects of the technology in this subject is depicted.

[0017] Figure 4A-4G Various views of electronic tags based on aspects of the technology in this subject are depicted.

[0018] Figure 5A This illustrates aspects of the technology according to this subject matter. Figure 4A-4G A conceptual diagram illustrating the use of electronic tags as described in the text.

[0019] Figure 5B This is a conceptual diagram illustrating the use of multiple electronic tags.

[0020] Figure 6 This is a conceptual diagram illustrating an example electronic system 600 for associating a fluid container with an infusion pump, according to aspects of the subject matter. Detailed Implementation

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

[0022] Figure 1 A medical drug delivery system 20 is shown, comprising four medical drug delivery devices 22, 24, 26, and 28, which in this embodiment are infusion pumps, each operatively engaged with a corresponding fluid delivery device 30, 32, 34, and 36. The medical fluid supply units or containers 38, 40, 42, and 44 can take various forms, but in this case are shown as inverted bottles suspended above the pumps. The fluid supply can also take the form of bags or other types of containers. The infusion pumps 22, 24, 26, and 28, as well as the fluid containers 38, 40, 42, and 44, are all mounted on roller frames or IV rods 46.

[0023] Each delivery device 30, 32, 34, and 36 is connected between the corresponding fluid containers 38, 40, 42, and 44 and the same patient 48, such that the patient is connected to multiple fluid delivery devices and receives fluid from multiple fluid containers (e.g., four in this example). Individual infusion pumps 22, 24, 26, and 28 are used to infuse each fluid from the fluid containers into the patient. The infusion pumps are flow-controlled devices that act on the corresponding tubing or fluid conduit of the fluid delivery device to deliver fluid from the fluid container through the conduit into the patient. Because individual pumps are used, each pump can be individually set to the pumping or operating parameters required to infuse a specific medical fluid from the corresponding fluid container into the patient at a specific rate prescribed by the physician for that fluid. As previously mentioned, such medical fluids may include drugs, pharmaceuticals, nutrients, or other therapeutic fluids.

[0024] Typically, medical fluid delivery devices have a higher... Figure 1The components shown are numerous. Many have check valves, drip chambers, valved ports, connectors, and other devices well known to those skilled in the art. Sometimes, during an infusion therapy regimen, a second medication is prescribed for infusion while the first is being administered to the patient. Attention turns to U.S. Patent No. 9,307,907 to Condurso et al., entitled “System and method for dynamically adjusting patient therapy,” which is incorporated herein by reference, providing further details on how to use a “Y-Site” connector that provides access to the primary infusion line to accomplish secondary infusions. These other devices are not included in the figures to maintain clarity of illustration. However, those skilled in the art will understand that the inclusion of such other devices can occur frequently.

[0025] Based on the background discussed above, it is desirable to verify that each fluid container 38, 40, 42, and 44 is associated with the correct patient 48, that the pumping parameters for a given medical fluid have been correctly programmed into the infusion pumps 22, 24, 26, or 28, and that each fluid container is correctly connected to the appropriately programmed pump. As will be discussed in more detail below, the present invention allows for easier and more accurate association of infusion fluid lines with the infusion device controlling their fluid flow and / or the fluid container from which the fluid originates. Data devices associated with the medical fluid containers, such as acoustic transducers 49, 50, 51, and 52, shown mounted on the bottle associated with the patient 48, can transmit relevant dosing data to the pump to verify that the medical drug delivery system 20 has been correctly connected. Relevant dosing data may include various data related to the administration of medical fluid to a particular patient. For example, relevant dosing data may include drug identification, patient identification, and other information deemed relevant.

[0026] It should be noted that Figure 1 The drawings are not to scale and have been compressed and exaggerated for clarity. In actual setups, the distances between containers 38, 40, 42, and 44 and infusion pumps 22, 24, 26, and 28 can be much greater. When all four tubes are suspended from the containers, the tubes of the administration devices 30, 32, 34, and 36 have a greater chance of becoming entangled, which can lead to confusion about which tube should be in which infusion pump. The chance of confusion increases with the number of tubes. However, it should also be understood that the invention is useful in cases involving a single pump and a single medical fluid container, as the system can also be used to confirm that the correct medication for the patient has arrived and that the infusion parameters have been correctly programmed into the pump.

[0027] like Figure 1The terms “upstream” and “downstream” as shown and used in different places herein are intended to provide indications of relative positioning and the location of certain specific devices. For example, the patient is located “downstream” of the pump and “downstream” of the container. The pump is located “upstream” of the patient, as is the container. On the other hand, there are “upstream data reader devices” and “downstream data reader devices” indicating their relative positions on the pump.

[0028] Now for reference Figure 2 The image shows an enlarged view of the front of the infusion pump 24. The pump includes a front door 53 and a handle 54, which is operated to lock the door in a closed position for operation, and to unlock and open the door to access the internal pump and sensing mechanisms, and to load the drug delivery device onto the pump. When the door is open, tubing can be connected to the pump. When the door is closed, the tubing is operatively engaged with the pump's pumping mechanism and other devices. In this embodiment, a display screen 55 (such as an LED display) is located in a plan view on the door and can be used to visually convey various pump-related information, such as alarm indications (e.g., alarm messages). Control keys 56 are present for programming and controlling the operation of the infusion pump as needed. In some embodiments, the infusion pump 24 also includes an audio alarm device in the form of a speaker 58.

[0029] In some implementations, such as Figure 2 As shown, the infusion pump 24 is attached to the right side of the programming module 60. Figure 1 As shown, other devices or modules, including another infusion pump, can be attached to the right side of infusion pump 24. In such a system, each attached pump represents a pump channel for the entire medical drug delivery system 20. In one embodiment, a programming module is used to provide an interface between infusion pump 24 and external devices, as well as to provide most of the operator interface for infusion pump 24. Attention turns to U.S. Patent No. 5,713,856, Eggers et al., entitled “Modular Patient Care System,” which is incorporated herein by reference, in which the programming module is described as a high-level interface unit. In other cases, the programming module is referred to as a “point of care unit.”

[0030] Programming module 60 includes a display screen 62 for visually conveying various information, such as operating parameters of pump 24, as well as alarm indications and alarm messages. Programming module 60 may also include a speaker (not shown) to provide audible alarms. In this embodiment, the programming module also has various input devices, including control keys 64. The programming module also has a communication system (not shown) through which it can communicate with external devices (such as a medical facility server or other computer) and portable processors (such as a handheld portable digital assistant (“PDA”) or a laptop-type computer), or other information devices that caregivers may need to communicate with and download medications or drug catalogs to the programming module or pump. The communication system may take the form of an RF system, an optical system (such as infrared), a Bluetooth system, or other wired or wireless systems. The communication system may alternatively be integrated integrally with the infusion pump, such as in the case where it is a stand-alone pump. Furthermore, information input devices do not need to be hardwired to the medical device; information can also be transmitted wirelessly.

[0031] Figure 2 This includes a second pump module 26 connected to the programming module 60. (e.g.) Figure 1 As shown, more pump modules can be connected. Additionally, other types of modules can be connected to the pump module or the programming module.

[0032] Figure 3 An example of an institutional patient care system 300 for a healthcare organization, based on aspects of the subject matter technology, is depicted. Figure 3 In this system, patient care equipment (or generally "medical equipment") 312 is connected to hospital network 10. The term "patient care equipment" (or "PCD") may be used interchangeably with the term "patient care unit" (or "PCU"), either of which may include various assistive medical devices such as infusion pumps, vital sign monitors, medication dispensing devices (e.g., cabinets, cases), medication preparation devices, automated dispensing devices, modules coupled to one of the foregoing (e.g., syringe pump modules configured to be attached to infusion pumps), or other similar devices. Each element 312 is connected to the internal healthcare network 310 via transmission channel 331. Transmission channel 331 is any wired or wireless transmission channel, such as an 802.11 wireless local area network (LAN). In some embodiments, network 310 also includes computer systems located in various departments throughout the hospital. For example, Figure 3Network 310 may optionally include computer systems associated with admissions, billing, biomedical engineering, clinical laboratories, central supply, one or more unit station computers, and / or medical decision support systems. As further described below, network 310 may include discrete subnetworks. In the depicted example, healthcare network 310 includes device network 340 through which patient care devices 312 (and other devices) communicate in accordance with normal operation.

[0033] Additionally, the institutional patient care system 100 may include a separate information system server 330, the functions of which will be described in more detail below. Furthermore, although the information system server 330 is shown as a separate server, its functionality and programming can be integrated into another computer if desired by the engineers designing the institutional information system. The institutional patient care system 300 may also include one or more device terminals 332 for connecting to and communicating with the information system server 330. Device terminals 332 may include personal computers, personal data assistants, or mobile devices (such as laptops, tablets, augmented reality devices, or smartphones) configured with software for communicating with the information system server 330 via network 310.

[0034] Patient care device 312 includes systems for providing patient care, such as those described in Eggers et al., which are incorporated herein by reference for this purpose. Patient care device 312 may include or contain pumps, physiological monitors (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), treatment devices, and other drug delivery devices that may be used in accordance with the teachings set forth herein. In the depicted example, patient care device 312 includes a control module 314, also referred to as interface unit 314, connected to one or more functional modules 316, 318, 320, 322. Interface unit 314 includes a central processing unit (CPU) 350 connected to a memory (e.g., random access memory (RAM) 358), and one or more interface devices, such as a user interface device 354, an coded data input device 360, a network connection 352, and an auxiliary interface 362 for communicating with additional modules or devices. Interface unit 314 also (though not necessarily) includes a main non-volatile storage unit 356 (such as a hard disk drive or non-volatile flash memory) for storing software and data, and one or more internal buses 364 for interconnecting the aforementioned components.

[0035] In various implementations, the user interface device 354 is a touchscreen for displaying information to a user and allowing the user to input information by touching a defined area of ​​the screen. Additionally or alternatively, the user interface device 354 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 360 ​​may be a barcode reader capable of scanning and interpreting data printed in barcode format. Additionally or alternatively, the data input device 360 ​​may be any device for inputting encoded data into a computer, such as one or more devices for reading magnetic stripes, radio frequency identification (RFID) devices, whereby digital data encoded in an RFID tag or smart tag (defined below) is captured by the reader 360 via radio waves, a PCMCIA smart card, an RFID card, a memory stick, a CD, DVD, or any other analog or digital storage medium. Other examples of the data input device 360 ​​include voice-activated or recognition devices or portable personal data assistants (PDAs). Depending on the type of interface device used, the user interface device 354 and the data input device 360 ​​may be the same device. Although the data input device 360 ​​is... Figure 3 The data input device 360 ​​is shown as being housed within interface unit 314; however, it is understood that the data input device 360 ​​may be integrated within the pharmacy system or located externally and communicate with the pharmacy system via an RS-232 serial interface or any other suitable communication device. The auxiliary interface 362 may be an RS-232 communication interface; however, any other means for communicating with peripheral devices (such as printers, patient monitors, infusion pumps, or other medical devices) may be used without departing from the subject matter. Alternatively, the data input device 360 ​​may be a separate functional module, such as modules 316, 318, 320, and 322, and configured to communicate with controller 314 or any other system on the network using suitable programming and communication protocols.

[0036] Network connection 352 can be a wired or wireless connection, such as via Ethernet, WiFi, BLUETOOTH, Integrated Services Digital Network (ISDN) connection, Digital Subscriber Line (DSL) modem, or cable modem. Any direct or indirect network connection can be used, including but not limited to telephone modems, MIB systems, RS232 interfaces, auxiliary interfaces, optical links, infrared links, radio frequency links, microwave links, or WLAN connections or other wireless connections.

[0037] Functional modules 316, 318, 320, and 322 are any devices used to provide care to patients or to monitor patient conditions. For example... Figure 3As shown, at least one of functional modules 316, 318, 320, and 322 can be an infusion pump module, such as an intravenous infusion pump, for delivering medication or other fluids to a patient. For the purposes of this discussion, functional module 316 is an infusion pump module. Each of functional modules 318, 320, and 322 can be any patient treatment or monitoring device, including but not limited to infusion pumps, syringe pumps, PCA pumps, epidural pumps, enteral pumps, blood pressure monitors, pulse oximeters, EKG monitors, EEG monitors, heart rate monitors, or intracranial pressure monitors. Functional modules 318, 320, and / or 322 can be printers, scanners, barcode readers, or any other peripheral input, output, or input / output device.

[0038] Each functional module 316, 318, 320, and 322 communicates directly or indirectly with interface unit 314, which provides overall monitoring and control of device 312. For example... Figure 3 As shown, or as detailed by Eggers et al., functional modules 316, 318, 320, and 322 can be physically and electronically connected serially to one or both ends of interface unit 314. However, it is recognized that other means exist for connecting functional modules to the interface unit, which can be used without departing from the subject matter. It will also be appreciated that devices providing sufficient programmability and connectivity (such as pumps or patient monitoring devices) can operate as standalone devices and communicate directly with the network without connection via a separate interface unit or control unit 314. As described above, additional medical devices or peripheral devices can be connected to patient care device 312 via one or more auxiliary interfaces 362.

[0039] Each functional module 316, 318, 320, 322 may include a module-specific component 376, a microprocessor 370, volatile memory 372, and non-volatile memory 374 for storing information. It should be noted that, although... Figure 3 Four functional modules are shown, but any number of devices can be connected directly or indirectly to the central controller 314. The number and type of functional modules described herein are intended to be illustrative and in no way limit the scope of the subject matter. Module-specific components 376 include any components necessary for operating a particular module, such as the pumping mechanism for the infusion pump module 316.

[0040] Although each functional module may be able to operate independently to some extent, the interface unit 314 monitors and controls the overall operation of the device 312. For example, as will be described in more detail below, the interface unit 314 provides programming instructions to functional modules 316, 318, 320, and 322 and monitors the status of each module.

[0041] The patient care device 312 can operate in several different modes or personalities, each defined by a configuration database. The configuration database can be an internal database 356 of the patient care device or an external database 337. A specific configuration database is selected based at least in part on patient-specific information, such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescriptions, medical history, medical records, patient care provider identity, physical characteristics, or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identity) or the location of the patient care device 312 within the hospital or hospital computer network. Patient care information can be input via interface device 354, data input device 360, or auxiliary interface 362, and can originate from anywhere within network 310, such as, for example, from a pharmacy server, admission server, laboratory server, etc.

[0042] Medical devices incorporating aspects of this subject matter can be equipped with a Network Interface Module (NIM) to allow the medical device to participate as a node in a network. Although for clarity, this subject matter will be described as operating in an Ethernet network environment using the Internet Protocol (IP), it is understood that the concepts of this subject matter are equally applicable to other network environments, and such environments are intended to be within the scope of this subject matter.

[0043] Data from and to various data sources can be converted into network-compatible data using existing technologies, and information movement between medical devices and the network can be achieved through various means. For example, patient care device 312 and network 310 can communicate via automatic interaction, manual interaction, or a combination of both. Automatic interaction can be continuous or intermittent and can be achieved through a direct network connection 352 (e.g., ...). Figure 3 (As shown), or via RS232 links, MIB systems, RF links (such as BLUETOOTH), IR links, WLANs, digital cable systems, telephone modems, or other wired or wireless communication means. Manual interaction between patient care device 312 and network 310 involves the physical, intermittent, or periodic transfer of data between systems using, for example, user interface device 354, coded data input device 360, barcodes, computer disks, portable data assistants, memory cards, or any other medium used for storing data. Communication in all aspects is bidirectional, with data accessed from as many points as possible from distributed data sources. Decision-making can occur in various locations within network 310. For example, rather than in a restricted manner, decisions can be made at a remote data server, in a hospital department or unit station, or within the patient care device 312 itself.

[0044] All direct communication with medical devices operating on a network according to the present invention can be performed through an information system server 330 (referred to as a Remote Data Server (RDS)). According to aspects of the present invention, the network interface module incorporated into the medical device (such as an infusion pump or vital sign measuring device) ignores all network traffic not originating from the certified RDS. The primary responsibility of the RDS in this invention is to track the location and status of all networked medical devices with NIM and to maintain open communication.

[0045] Figure 4A An electronic tag 400 according to aspects of the present subject matter is shown, which is configured with a display screen to show relevant information related to the infusion process. The electronic tag 400 is configured to visually associate an IV delivery device (or fluid line) with a specific infusion container and / or a specific infusion device. The infusion container may be, for example... Figure 1 The IV bag 38 is shown. The IV bag 38 includes fluid that is infused to the patient using an IV device 408 connected to the IV bag 38 and the infusion pump 22. In some embodiments, the drug delivery device can deliver gas to the patient from a source (such as a canister) via a device configured to regulate gas flow (such as a ventilator). An electronic tag 400 can provide a similar association feature to that described for fluids for a gas-including line.

[0046] The electronic tag 400 includes a front portion having a housing 402. In some embodiments, the housing 402 encapsulates one or more of a processor, memory, power storage, antenna, sensor, and data communication components. In some embodiments, the data communication component is a transceiver coupled to the processor. In some embodiments, the transceiver is a Bluetooth transceiver. In some embodiments, the transceiver is an RFID transceiver. In some embodiments, a display screen 406 is coupled to the processor and configured to display information received via the transceiver. In some embodiments, the display screen 406 is an electronic ink display screen. An electronic ink display screen can display different colors, and these colors can be used to identify different IV lines.

[0047] Alternatively or additionally, the electronic tag 400 may include additional colored LED components to indicate whether a malfunction in the infusion process has been detected. For example, the electronic tag 400 may include colored or color-adjustable LEDs that allow general indications of the infusion process's status to be visible even from a distance. The LEDs may be mounted inside, on, or outside the housing of the electronic tag 400. If a green LED is lit, the clinician can see it from a distance and be informed that the infusion process is proceeding normally. In some embodiments, the electronic tag 400 may include red or yellow LEDs. Similarly, when red or yellow LEDs are lit, the clinician can see them from a distance and be informed that the infusion process may require some malfunction handling. In some embodiments, the color of the LEDs may be encoded to provide the clinician with additional information about the status of the infusion process. Additionally or alternatively, these colored LED components may be represented by corresponding colored graphic indicators (e.g., groups of pixels in the form of LEDs) presented by the display screen 406.

[0048] The electronic tag 400 also includes communication components and / or an antenna, which allows the electronic tag 400 to be programmed via wireless technologies (e.g., Bluetooth, Wi-Fi, Near Field Communication (NFC)) in some embodiments. In some embodiments, the electronic tag 400 can communicate with the infusion pump (e.g., using data communication components and / or an antenna) to coordinate with an alarm system at the pump or care station. For example, before the infusion line becomes empty and air is drawn into the system, the electronic tag 400 can receive information from the pump that the infusion container is empty and generate an infusion container empty alarm. For example, a sensor may be included in the electronic tag to provide information about the fluid pressure in the IV line. In some embodiments, the infusion pump includes software for converting signals transmitted by the electronic tag 400 into actionable messages for the clinician (e.g., changing the infusion container).

[0049] In some implementations, the electronic tag 400 can also communicate with medication safety and continuous quality improvement (CQI) software at the point of care. The point of care may include a programming module 60 and / or an infusion pump. When the software is deployed at the programming module 60 and / or the infusion pump, it can help reduce IV medication errors, improve the overall quality of patient care, track and measure system performance, and help improve compliance with national safety standards. In some implementations, the software allows for customization of care areas or profiles. In each of these profiles, a library of medications and IV fluids can be created. The names of medications and IV fluids can be customized using generic or brand-name medications and help distinguish similar names. The software can also create clinical consultations for specific medications, providing additional clinical information prior to the infusion. The software can also allow for the treatment of specific medications to be customized to patient-specific infusion delivery limits. For example, once the electronic tag 400 is associated with a specific IV container containing a specific medical fluid, the electronic tag 400 can communicate the identity of the medical fluid to the pump, which then determines the range of infusion rates for that medical fluid from a library containing information about various medical fluids. The clinician can then select an infusion rate from a range of infusion rates on the programming module 60 and / or the infusion pump, and the electronic tag 400 can subsequently display the selected infusion rate. The electronic tag 400 is configured to receive, via a transceiver, infusion information about the contents of the IV infusion container obtained via software from the infusion pump, as well as infusion parameters of the infusion process associated with the IV infusion container.

[0050] In some embodiments, the electronic tag 400 does not include communication components, and the electronic tag is configured for use alone in the absence of an infusion pump, for example, during gravity infusion. In some embodiments, the electronic tag configured for gravity infusion may include Bluetooth functionality to provide communication and location signals to the hospital system's network. The system can then detect and determine the location in the hospital where gravity infusion is occurring.

[0051] The rear portion of the electronic tag 400 includes a clamping mechanism 404. The clamping mechanism 404 is configured to secure the electronic tag 400 to the IV tube of the IV device 408. The clamping mechanism 404 includes a first elongated bracket 414 formed on the rear portion 413 of the housing 402 to receive the IV tube of the IV device 408. Together with a second elongated bracket 412, the brackets 412 and 414 are shaped to snugly constrain a portion of the tube of the IV device 408 without obstructing fluid flow in the tube. The brackets 412 and 414 together surround this portion of the tube of the IV device 408. In some embodiments, such as Figure 4B and Figure 4C As shown, brackets 412 and 414 are V-shaped grooves that together surround the tube length between clamping arm 416 and first elongated bracket 414.

[0052] Figure 4B A rear view of the electronic tag 400 is shown. The electronic tag 400 includes a clamping mechanism 404 with clamping arms 416. Typically, the electronic tag 400 can be securely attached using any mechanism that does not obstruct fluid flow in the tube. In some embodiments, such as Figure 4B As shown, the clamping mechanism 404 includes a rotary joint and a spring 418 (e.g., pivotally coupling the housing 402 and the arm 416) which applies a mechanical force (e.g., tension to the clamping arm 416) on the second bracket 412 when no external force is applied to the lever 417 of the clamping mechanism 404.

[0053] Before releasing the force on lever 417, the electronic tag 400 can be easily attached to the tubing of the IV device by applying force to lever 417 to move clamping arm 416 away from housing 402 and open brackets 412 and 414 to receive the tubing. In some embodiments, the electronic tag 400 may incorporate additional components to ensure that the electronic tag 400 is locked in place during infusion and can only be removed by one or more authorized personnel. For example, the electronic tag 400 may be locked by electromechanical devices. For example, the electromechanical devices receive a wireless control signal from the infusion pump to unlock the electronic tag 400 when the infusion pump detects an authorized person at the electronic tag 400 at the end of the infusion process, or when the IV container and / or IV device is replaced. In some embodiments, the electronic tag 400 can also be “locked” to the tubing by means of a proximity sensor. For example, clamping mechanism 404 may have a magnet therein, and the electronic tag 400 may have a Hall effect sensor that records that clamping mechanism 404 is in a “closed” state. Once the electronic tag 400 is associated with an infusion pump (e.g., infusion pump 22), the electronic tag 400 can sense whether a "clamp closure" signal has been interrupted and issue an error message when the "clamp closure" signal has been interrupted. Similarly, the electronic tag 400 may include other communication functions, such as providing the pump with the tag's location information and / or transmitting other information to the pump.

[0054] Figure 4C A rear view of the clamping mechanism 404 is shown when an external force is applied to the lever 417, according to an aspect of the subject matter. For example, when a clinician presses down on the lever 417 such that the lever 417 is substantially parallel to the plane of the housing 402, the first bracket 414 separates from the second bracket 412. Figure 4CAs shown, sensor 420 is positioned within bracket 414. In some embodiments, sensor 420 is a pressure sensor configured to measure the fluid pressure in the tubing of IV device 408 at the location of sensor 420. In some embodiments, the pressure sensor is an electronic flow sensor that transmits measurement data to the infusion pump using a data communication component disposed within housing 402.

[0055] In some implementations, when the IV container is squeezed, sensor 420 detects the increase in pressure and helps identify whether electronic tag 400 is attached to the correct tube. Sensor 420 can also be used to detect when the IV container is empty.

[0056] In some embodiments, sensor 420 includes an acoustic sensor. As the infusion fluid flows through the sensor, the acoustic sensor can detect sound waves, noise, or other disturbances within the fluid line. The detected noise can be used to identify the flow rate. In some embodiments, the acoustic sensor includes an ultrasonic method for flow sensing.

[0057] In some embodiments, the electronic tag 400 operates in conjunction with an acoustic transducer that generates sound waves detected by a sensor 420 within the electronic tag 400. In this case, instead of a clinician physically squeezing the IV container to mate a specific IV device with the IV container, the acoustic transducer can be attached to the specific IV container. The acoustic sensor in the electronic tag 400 (attached to the IV device) determines whether it detects an acoustic signal generated by the acoustic transducer attached to the IV container to check whether the electronic tag 400 is correctly associated with that specific IV container. In some embodiments, the electronic tag 400 may also include a transmitter (e.g., an acoustic transducer or pressure actuator) that generates an acoustic or pressure signal to allow association between the IV delivery line and the infusion pump (and / or a second electronic tag).

[0058] In some implementations, the acoustic signal can be generated by an infusion pump. For example, the infusion pump can move one or more of its motors back and forth to generate a signature acoustic pattern transmitted to the electronic tag 400 via the IV device.

[0059] The transmission and detection of signals (e.g., acoustic signals, pressure signals) performed by acoustic transducers or pressure actuators and sensors in electronic tags can be coordinated as follows:

[0060] The process can begin when the electronic tag 400 receives an indication that it is time to check the IV administration line (e.g., “line tracking”). This indication can be provided by an element paired with the electronic tag 400. For example, the element paired with the electronic tag 400 could be a second electronic tag, infusion pump 22, or programming module 60.

[0061] Clinicians can first determine where the electronic tag 400 is attached to the IV dosing line (e.g., the clamping mechanism 404 based on the electronic tag 400 attaches the electronic tag to the location of the IV dosing line).

[0062] The electronic tag 400 can transmit a "ready to launch" activation signal, and the pairing element can optionally provide confirmation of received signal. The activation signal can trigger adjustments to a detection device, such as in other electronic tags, the infusion pump 22, or the programming module 60. This adjustment may include activating the detection device or adjusting the detection threshold for a period of time.

[0063] An acoustic transducer or pressure actuator in the electronic tag 400 causes one or more emission of sound or pressure waves. The electronic tag 400 and / or pairing element receive confirmation of successful line tracking. In some embodiments, this confirmation can be received directly through interaction with the electronic tag. In some embodiments, the confirmation is received via signals from the infusion pump 22, the programming module 60, or through interaction with other components in the infusion process.

[0064] In some embodiments, an acoustic transducer in the electronic tag can transmit an acoustic signal to the infusion pump, enabling the pump to verify that the correct electronic tag 400 is associated with it. The infusion pump can detect whether a signature acoustic pattern is transmitted from a specific electronic tag along the IV device. In this way, various associations can be made: (1) from the IV container to the electronic tag, and (2) from the electronic tag to the infusion pump. In some embodiments, an additional electronic tag can be used to correctly associate the IV device from the pump to the patient, as described in more detail below.

[0065] In some implementations, the patient may be provided with a device that receives communication signals from the infusion pump and / or an electronic tag. For example, the device may be a wristband that allows the pump to transmit information from the electronic tag 400 to the patient, or the electronic tag 400 to transmit information directly to the patient.

[0066] Figure 4DA close-up view of the display screen 406 of the electronic tag 400 is shown. In some embodiments, the electronic tag 400 is a standalone device that allows the display screen 406 to present clear information to clinicians and / or patients without any additional accessories. For example, the electronic tag 400 may be self-powered and does not require a power cord to power the electronic tag during use. In some embodiments, the electronic tag 400 includes a rechargeable battery with sufficient electrical (e.g., charge) storage capacity to power the electronic tag 400 for the duration of the infusion and / or until the expiration of the IV delivery device's lifespan (e.g., up to 96 hours). In some embodiments, the electronic tag 400 is reusable, and data containing relevant information about each infusion procedure is transmitted to the electronic tag 400 before the start of each infusion procedure.

[0067] The electronic tag 400 provides sufficient power so that the display screen 406 can present information about the infusion process throughout the expected lifespan of the IV device. In some embodiments, the IV device can be used for up to 96 hours. In some embodiments, the IV device can be used for up to 72 hours. For safety reasons, the IV device is replaced once it has been used within its expected lifespan to ensure that the IV device maintains its specified performance characteristics.

[0068] The electronic tag 400 is a low-cost component that can improve the safety and accuracy of the infusion process. The display screen 406 can be used to display information related to the infusion process, thereby allowing the electronic tag 400 to provide clinicians and / or patients with up-to-date and accurate information.

[0069] The electronic tag 400 also allows for the establishment and execution of infusion procedures with less manpower, while improving the accuracy and safety of the infusion process. Clinicians can rely on the smart tag to help them accurately associate IV containers with specific IV devices and specific infusion pumps. For example, the display screen 406 displays: (i) channel information 422 about the infusion pump to which the IV device 408 is connected; (ii) information 424 about the medical fluid contained in the IV container being infused; (iii) information 426 about the infusion rate of the medical fluid; (iv) information 428 about the start time of the infusion; (iv) information 430 on the display screen 406 indicating that the IV device will exceed its expected lifespan; (v) information 432 about the clinician who initiated the infusion procedure; and (vi) information 434 about the patient receiving the infusion.

[0070] In some embodiments, information 436 is provided on display 406 in a larger font size to inform clinicians and / or patients about the expected lifespan of the IV device. In some embodiments, display 406 further displays a countdown timer indicating when the IV device 408 needs to be replaced. In this way, the electronic tag 400 provides more functionality than a simple tag or display screen. The electronic tag 400 can also provide timely warnings or error messages, enabling clinicians to promptly correct any malfunctions associated with the infusion process.

[0071] In some implementations, machine-readable code (e.g., linear barcode, 2D barcode, quick-read code) 438 may be used to track and record steps of the infusion process, such as tracking medications prescribed to a particular patient and / or for other purposes.

[0072] Figure 4E-4G This illustrates how an electronic tag 400, according to aspects of the subject matter, can be associated with a specific IV device for delivering infusion fluid from an IV container to a patient. In some embodiments, when the electronic tag 400 is first activated for use, an introductory message 440 is displayed on a display screen 406. For example, when the lever 417 of the clamping mechanism 404 is depressed such that the lever 417 is substantially parallel to the plane of the housing 402 (e.g., as...). Figure 4C As shown, the electronic tag 400 can be activated for first-time use. In some embodiments, the introductory message 440 may provide clinicians with step-by-step instructions to properly associate the IV device with the IV container. For example, in some embodiments, the introductory message 440 provides clinicians with initial instructions to attach the electronic tag 400 to the IV tube.

[0073] Figure 4F The subsequent steps in the process of correctly associating an IV device with an IV container according to aspects of the subject matter are illustrated. In some embodiments, once the sensor 420 on the electronic tag 400 senses that the electronic tag 400 has been attached to the tube of the IV device 408, the display screen 406 provides an update message 442 containing subsequent instructions for associating the electronic tag 400 with a specific IV container.

[0074] For example, message 442 instructs a clinician to squeeze an IV container (e.g., an IV bag) containing medical fluid that the clinician wishes to administer to a patient using an IV device to which electronic tag 400 is attached. When the clinician squeezes the IV container, a change in fluid pressure (caused by the squeezing) is detected at a sensor 420 located within a first elongated bracket 414 on the rear of housing 402. A processor located in housing 402 of the electronic tag is able to analyze the signal received from sensor 420 to confirm that the IV bag squeezed by the clinician is correctly associated with IV device 408.

[0075] Conversely, if sensor 420 anticipates an increase in fluid pressure but this pressure change is not detected, electronic tag 400 can display a warning message indicating that it has not been properly associated with the IV container. Electronic tag 400 can also transmit warning messages via Bluetooth to the pump and / or care station to notify clinicians that the IV device has not been properly associated with the IV container.

[0076] In some implementations, message 442 may further guide the clinician to provide a series of squeezes so that the pattern of pressure change is detected at sensor 420 to provide a more accurate association between the squeezed IV container and the IV device 408 to which the electronic tag 400 is attached (e.g., by eliminating spurious noise that could lead to a “false positive” association between the IV container and the IV device 408).

[0077] In some embodiments, an acoustic transducer is placed near or above the IV container and activated to deliver a series of sound waves detected by sensor 420 to the medical fluid. In some embodiments, a data communication component disposed within the housing 402 of the electronic tag can communicate directly with the acoustic transducer placed at or near the IV container and send requests to the acoustic transducer to generate a series of acoustic pulses. In some embodiments, this series of acoustic pulses is modulated.

[0078] In some embodiments, the series of modulated acoustic pulses is detected by sensor 420, and the detected signal is analyzed by a processor located within housing 402 to ensure that the modulated acoustic pulses match a series of acoustic pulses emitted by an acoustic transducer. In some embodiments, the signal detected by sensor 420 is wirelessly transmitted to the infusion pump, and the infusion pump then sends a control signal to electronic tag 400 to display a completion message 444 when the pump determines that the modulated acoustic signal detected by sensor 420 matches a signal generated by an acoustic transducer placed at or near the IV container. When the detected modulated acoustic pulse deviates from the expected modulated acoustic pulse by an amount greater than a threshold, electronic tag 400 may also transmit a warning message, for example via Bluetooth, to the infusion pump and / or care station to notify the clinician that the IV device has not been properly associated with the IV container.

[0079] When sensor 420 successfully detects a change in fluid pressure or a modulated acoustic signal, electronic tag 400 can then display a completion message 444 on display screen 406 to notify the clinician that the IV device has been detected and confirmed to be correctly associated with the IV container. The identity of the medical fluid in the IV container is also displayed on display screen 406 as an additional check that the IV container has been correctly associated. The name of the infusion pump (e.g., “Channel 1”) can also be displayed on display screen 406 to ensure that IV device 408 is correctly connected to the intended infusion pump.

[0080] In some implementations, the electronic tag 400 is associated with the IV container and / or infusion pump via a near-field communication (NFC) component within the electronic tag 400. The NFC component allows for a one-to-one association between the IV container and / or infusion pump when the electronic tag 400 establishes wireless communication. In some implementations, the electronic tag 400 is associated with a code scanned by a clinician (e.g., ...). Figure 4D After the machine-readable code 438 in the code, the programming module 60 selects an infusion pump as the active infusion pump, and the IV device can be loaded to connect to that specific infusion pump.

[0081] In some implementations, two or more electronic tags may be combined for a specific IV device. For example, a first electronic tag in a pair may be attached to the IV container, and a second electronic tag may be attached to the IV device, upstream of the pump. When both tags are placed in the fluid path between the IV container and the pump, information may be sent to the electronic tags in different ways.

[0082] In some implementations, the pump already possesses information about the IV container via methods other than displaying information provided by the electronic tag (e.g., by scanning a barcode or other means of associating the IV container with the pump). The pump then transmits this information to the electronic tag via RFID or Bluetooth. In some implementations, acoustic signal exchange between the electronic tags is initiated to verify that the correct device is receiving the wireless information.

[0083] In some implementations, the IV container includes an RFID or Bluetooth transmitter tag attached thereto, which allows the IV electronic tag to receive information directly from the IV container. The information encoded in the RFID or Bluetooth transmitter tag located within the IV container may have been pre-loaded in the pharmacy. In some implementations, acoustic signal exchange between the electronic tags is initiated to verify that the correct device is receiving the wireless information.

[0084] Alternatively, the first electronic tag in the pair may be attached to a first location on the IV device, upstream of the pump. The second electronic tag may be attached to a second location on the IV device, downstream of the pump (e.g., between the pump and the patient). In some embodiments, the electronic tags communicate via acoustic signaling.

[0085] In some implementations, three electronic tags can be used in combination and associated with a single pump. For example, a first tag may be associated with the primary infusion IV container, a second electronic tag may be associated with the secondary infusion IV container, and a third electronic tag may be located on the IV device to complete the downstream connection from the pump to the patient.

[0086] Each electronic tag is capable of generating its own acoustic signal and detecting acoustic signals generated by another electronic tag. In some embodiments, the acoustic signals are propagated and detected via medical fluid within the IV device. For example, when an acoustic signal generated by a first electronic tag at a first location on the IV device is detected by a sensor of a second electronic tag at a second location on the IV device, the pair of electronic tags can determine that they are correctly attached to the same infusion IV device. Similarly, when the pair of electronic tags can detect the acoustic signals generated by each other, a first electronic tag attached to an IV container can be correctly associated with a second electronic tag located on the IV device. In some embodiments, the acoustic signal is detected by the pump upstream of the pump, and then the pump generates a retransmitted acoustic signal downstream to associate the upstream and downstream tags with each other.

[0087] Figure 5A It shows that electronic tag 400 is included. Figure 1 The illustrated medical drug delivery system 20 includes system 500. Four fluid containers 38, 40, 42, and 44 are connected to infusion pumps 22, 24, 28, and 26, respectively, and infusion pumps 22, 24, 26, and 28 are all attached to programming module 60. Electronic tag 400 is attached to IV device 36. Additional electronic tags are attached to... Figure 5A The corresponding IV device is not shown. In some embodiments, the electronic tag 400 is capable of communication between its upstream 504 and downstream 502. For example, the electronic tag 400 is capable of receiving an acoustic signal generated upstream of the clip and transmitting an acoustic signal downstream of the electronic tag 400 to the infusion pump 28. The acoustic signal can be modulated, thereby allowing an acoustic sensor receiving the acoustic signal to determine its source.

[0088] Figure 5BA system 500 is shown in which electronic tags 506, 508, 510, and 512 are attached to IV devices 36, 34, 32, and 30, respectively. IV device 30 has been partially swapped with IV device 32, causing IV device 30 to associate fluid container 38 with infusion 24. In some embodiments, electronic tag 512 can generate a warning on its display or cause infusion pump 22 to generate an alarm when a clinician is unaware that IV device 30 has been incorrectly swapped with IV device 32. For example, infusion pump 24 may have been pre-programmed to receive medical fluid from fluid container 40 and infuse the medical fluid to patient 518 at a specific infusion rate. Instead, infusion pump 24 receives fluid from fluid container 38 and may then infuse fluid from fluid container 38 to patient at an incorrectly set infusion rate. To reduce the likelihood of such tubing swapping, an acoustic transducer housed within electronic tag 510 can generate an acoustic signal intended for use with a sensor associated with infusion pump 24, which may be located near the infusion line. When the sensor associated with infusion pump 24 fails to receive a signal generated by the acoustic transducer from electronic tag 510, the pump may display or issue an alarm, or may wirelessly deliver a warning message to electronic tag 510 for presentation on the display screen of electronic tag 510. Lines 514 and 516 are schematic diagrams showing the outputs of various infusion pumps 22, 24, 26, and 28 being delivered to patient 518. In some embodiments, line 514 includes a central line. The central line includes a catheter placed in a large vein. In some embodiments, line 516 includes an antecubital line. The antecubital line may be inserted into a vein in the patient's arm. Patient 518 may be equipped with a smart wristband that transmits information from the electronic tag to the patient. For example, information presented on display screen 406 may be additionally provided to the display screen on the smart wristband. The display screen on the smart wristband may be an electronic paper display technology, such as those available from E Ink Corporation. Then, the patient can receive information about the identity of the medical fluid being infused, and also about when the IV device must be replaced.

[0089] Many of the aforementioned devices, systems, and methods can also be implemented as software processes, specified as a set of instructions recorded on a computer-readable storage medium (also known as a computer-readable medium), and 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, processor cores, or other processing units), they cause the one or more processing units to perform the actions indicated in the instructions. Examples of computer-readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard disk drives, EPROMs, etc. Computer-readable media do not include carrier waves and electronic signals transmitted wirelessly or via wired connections.

[0090] The term "software" is intended to include, where appropriate, firmware residing in read-only memory or an application stored in magnetic storage, which can be read into memory for processor processing. Furthermore, in some embodiments, the multiple software aspects disclosed herein may be implemented as sub-parts of a larger program while maintaining the distinct software aspects disclosed herein. In some embodiments, the multiple software aspects may also be implemented as separate programs. Finally, any combination of separate programs that collectively implement the software aspects described herein is within the scope of this disclosure. In some embodiments, a software program, when installed for operation on one or more electronic systems, defines one or more specific machine implementations of the operations performed and executed by the software program.

[0091] Computer programs (also referred to as programs, software, software applications, scripts, or code) can be written in any programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, objects, or other units suitable for use in a computing environment. A computer program may, but does not necessarily, correspond to a file in a file system. A program may be stored as a portion of a file containing other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinating files (e.g., a file storing one or more modules, subroutines, or code sections). A computer program can be deployed to execute on a single computer or on multiple computers located at a site or distributed across multiple sites and interconnected by a communication network.

[0092] In some embodiments, the electronic tag includes a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to a vein (IV) tube; and a sensor disposed within the housing and configured to measure the properties of the fluid in the IV tube at the location of the clamping mechanism.

[0093] In some embodiments, the processor is configured to send a first signal to the infusion device via a transceiver and receive a second signal from the infusion device via the transceiver. In some embodiments, the first signal sent to the infusion device is configured to trigger an alarm at a location remote from the electronic tag when a fault condition exists. In some embodiments, the transceiver includes a wireless communication device and is configured to communicate with the infusion device via a wireless connection. In some embodiments, the processor is configured to cause the electronic tag to receive infusion information about the contents of the IV infusion container and infusion parameters of the infusion process associated with the IV infusion container from the infusion device via the transceiver; and the display screen is configured to display the infusion information and infusion parameters.

[0094] In some embodiments, the housing includes a first elongated bracket configured to receive a portion of the IV tube, and a clamping mechanism includes a clamping arm and a spring configured to apply tension to the clamping arm to restrain the portion of the IV tube within the first elongated bracket. In some embodiments, a display screen is disposed on a first side of the housing opposite to the first elongated bracket and the clamping arm. The clamping arm includes a second elongated bracket, and the first elongated bracket and the second elongated receiver are configured to together surround the portion of the IV tube to restrain at least that portion of the IV tube between the clamping arm and the first elongated bracket.

[0095] In some embodiments, when the clamping arm is moved to constrain the IV tube, the first elongated bracket and the second elongated bracket form a substantially cylindrical shape, and a sensor is disposed within the first elongated bracket and configured to contact the constrained IV tube. In some embodiments, the sensor includes an acoustic sensor configured to measure acoustics within at least a portion of the IV tube. In some embodiments, the sensor includes a pressure sensor configured to detect the fluid pressure within the IV tube at its location. In some embodiments, the electronic tag also includes a lock to secure the electronic tag to the IV tube.

[0096] In some embodiments, the electronic tag also includes at least one color light-emitting diode (LED). The at least one color LED is configured to emit a first color when a fault condition is present and a second color different from the first color during normal operation. In some embodiments, the electronic tag also includes a signal transmitter configured to emit a signal for associating the electronic tag with an infusion device or a second electronic tag. In some embodiments, the signal transmitter includes an acoustic transducer or a pressure actuator.

[0097] In some embodiments, a method of associating an intravenous (IV) infusion container with an infusion pump of an infusion device includes receiving an IV tube coupled to the IV infusion container at the infusion pump. An electronic tag is affixed to the IV tube, and the electronic tag includes a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to the IV tube; and a sensor disposed within the housing and configured to measure the properties of fluid in the IV tube at the location of the clamping mechanism. The method includes transmitting a signal from at least one of the IV infusion container and the infusion pump of the infusion device. The method includes receiving from the electronic tag an acknowledgment message indicating that a sensor of the electronic tag has received an associated signal. The method includes determining that the associated signal corresponds to a signal transmitted by at least one of the IV infusion container and the infusion pump. The method includes causing the electronic tag to display a message indicating association with the IV infusion container or the infusion pump of the infusion device on the display screen of the electronic tag.

[0098] In some embodiments, transmitting a signal from the IV infusion container includes applying pressure to the IV infusion container. The electronic tag's sensor includes a pressure sensor, and an acknowledgment message indicates that the electronic tag has detected an increase in fluid pressure in the IV tubing caused by the pressure applied to the IV infusion container. In some embodiments, the method further includes causing the electronic tag's display to show an instruction to apply pressure to the IV infusion container. Displaying this message is based at least in part on determining that the acknowledgment message was received within a first time period measured from the time the instruction was displayed. In some embodiments, transmitting a signal at the infusion pump of the infusion device includes transmitting an acoustic signal within the IV tubing at the infusion pump of the infusion device; and the electronic tag's sensor includes an acoustic sensor. An acknowledgment message indicates that the electronic tag measures a detected acoustic signal in the IV tubing caused by an acoustic signal generated at the infusion pump of the infusion device.

[0099] In some embodiments, the acoustic signal generated at the infusion pump of the infusion device includes a modulated acoustic signal caused by changes in the pump's movement within the infusion device. An acknowledgment message indicates that the detected modulation of the acoustic signal in the IV tubing corresponds to the modulation of the modulated acoustic signal generated at the infusion pump of the infusion device.

[0100] In some implementations, the electronic tag displays a message based at least in part on the determination that the acknowledgment message was received within a threshold time period measured from the time the signal was transmitted.

[0101] In some embodiments, the method further includes transmitting information from the infusion device about the contents of the IV infusion container and parameters of the infusion process associated with the IV infusion container; and displaying the information and parameters on an electronic tag display screen.

[0102] In some embodiments, a method for associating an intravenous (IV) infusion container with an infusion pump of an infusion device includes determining that an electronic tag is affixed to an IV tube coupled to the IV infusion container at an electronic tag. The electronic tag includes a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to the IV tube; and a sensor disposed within the housing and configured to measure the properties of fluid in the IV tube at the location of the clamping mechanism. The method includes receiving a signal transmitted from at least one of the IV infusion container and the infusion pump of the infusion device. The method includes generating, based on the signal, an acknowledgment message by the electronic tag indicating that the sensor of the electronic tag has received an association signal. The method includes transmitting the acknowledgment message to at least one of the IV infusion container and the infusion pump of the infusion device. The method includes receiving, from the IV infusion container or the infusion pump of the infusion device, a message indicating association with the IV infusion container or the infusion pump of the infusion device. The method includes displaying a message on the electronic tag's display screen indicating an association with an IV infusion container or infusion device's infusion pump.

[0103] In some embodiments, a method is provided for associating an intravenous (IV) infusion container with an infusion pump of an infusion device. The method includes attaching a first electronic tag at a first location along a fluid path between the IV infusion container and the infusion device. The first electronic tag includes a first housing; a first processor within the first housing; a first transceiver disposed within the first housing and coupled to the first processor; a first display coupled to the first housing and the first processor and configured to display information received via the first transceiver; a first clamping mechanism coupled to the first housing and configured to secure the first electronic tag to the IV tube; and a first sensor disposed within the first housing and configured to measure properties of the fluid in the IV tube at the location of the first clamping mechanism. The method includes attaching a second electronic tag to a second location along a fluid path. The second electronic tag includes a second housing; a second processor within the second housing; a second transceiver disposed within the second housing and coupled to the second processor; a second display screen coupled to the second housing and the second processor and configured to display information received via the second transceiver; a second clamping mechanism coupled to the second housing and configured to secure the second electronic tag to a venous (IV) tube; and a second sensor disposed within the second housing and configured to measure the properties of the fluid in the IV tube at the location of the second clamping mechanism. The method includes generating a first signal at a first signal generator of a first electronic tag. Based on the determination that the second sensor of the second electronic tag receives the first signal generated at the first signal generator of the first electronic tag: a message indicating that the IV fluid infusion container is associated with the IV tube is displayed on a first display screen of the first electronic tag and on a second display screen of the second electronic tag.

[0104] Figure 6 This is a conceptual diagram illustrating an example electronic system 600 for communicating with electronic tags according to aspects of the subject matter. Electronic system 600 can be used to perform... Figure 1-5B The provided computing device includes, but is not limited to, computing hardware within server 330 or patient care device 312, one or more components and processes associated with the software. Electronic system 600 may be representative, in conjunction with... Figures 1-5B The publicly disclosed content. In this regard, electronic system 600 may be a personal computer or mobile device, such as a smartphone, tablet, laptop, PDA, augmented reality device, wearable device (such as a watch or strap or glasses), or a combination thereof, or other touchscreen or television having one or more processors embedded therein or coupled thereto, or any other category of computer-related electronic equipment with network connectivity.

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

[0106] Bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of electronic system 600. For example, bus 608 communicatively connects one or more processing units 612 to ROM 610, system memory 604, and permanent storage device 602.

[0107] From these various memory units, one or more processing units 612 retrieve instructions to be executed and data to be processed in order to perform the processes disclosed in this subject matter. In different embodiments, the one or more processing units may be a single-processor or a multi-core processor.

[0108] ROM 610 stores static data and instructions required by one or more processing units 612 and other modules of the electronic system. On the other hand, permanent storage device 602 is a read-write memory device. Such a device is a non-volatile memory cell that stores instructions and data even when the electronic system 600 is off. Some embodiments disclosed in this subject matter use mass storage devices (such as magnetic disks or optical disks and their corresponding disk drives) as permanent storage device 602.

[0109] Other embodiments use removable storage devices (such as floppy disks, flash drives, and their corresponding disk drives) as permanent storage device 602. Like permanent storage device 602, system memory 604 is a read-write memory device. However, unlike storage device 602, system memory 604 is volatile read-write memory, such as random access memory. System memory 604 stores some instructions and data required by the processor during operation. In some embodiments, the processes disclosed in this subject matter are stored in system memory 604, permanent storage device 602, and / or ROM 610. From these various memory units, one or more processing units 612 retrieve instructions to be executed and data to be processed in order to perform the processes of some embodiments.

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

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

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

[0113] Some implementations include electronic components, such as microprocessors, storage, and memory, that store computer program instructions in a machine-readable or computer-readable medium (also referred to as a computer-readable storage medium, machine-readable medium, or machine-readable storage medium). Examples of such computer-readable media include RAM, ROM, read-only optical disc (CD-ROM), recordable optical disc (CD-R), rewritable optical disc (CD-RW), read-only digital versatile optical disc (e.g., DVD-ROM, dual-layer DVD-ROM), various recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD card, mini SD card, micro SD card, etc.), magnetic and / or solid-state hard disk drives, read-only and recordable... Disks, high-density optical discs, any other optical or magnetic media, and floppy disks. Computer-readable media may store computer programs executable by at least one processing unit and include 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 higher-level code executed by a computer, electronic component, or microprocessor using an interpreter.

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

[0115] As used in the specification and any claims of this application, the terms "computer," "server," "processor," and "memory" refer to electronic or other technical devices. These terms do not include people or groups of people. For the purposes of this specification, the terms "displayed" or "being displayed" mean displayed on an electronic device. As used in the specification and any claims of this application, the terms "computer-readable medium" and "computer-readable media" are entirely limited to tangible physical objects that store information in a computer-readable form. These terms do not include any wireless signals, wired download signals, or any other transient signals.

[0116] To provide interaction with the user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) and a keyboard and pointing device (e.g., a mouse or trackball) for displaying information to the user, through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and input from the user can be received in any form, including sound, speech, or tactile input. Additionally, the computer can interact with the user by sending and receiving documents from the device used by the user; for example, by sending a webpage to a web browser on the user's client device in response to a request received from a web browser.

[0117] Implementations of the subject matter described in this specification can be implemented in a computing system that includes back-end components (e.g., as a data server), or middleware components (e.g., an application server), or front-end components (e.g., a client computer with a graphical user interface or web browser through which a user can interact with the implementations of the subject matter described in this specification), or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected via digital data communication (e.g., a communication network) of any form or medium. 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).

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

[0119] Those skilled in the art will understand 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 between hardware and software, the various illustrative blocks, modules, elements, components, methods, and algorithms have been described above in general terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. For each specific application, the described functionality can be implemented in different ways. Various components and blocks can be arranged differently (e.g., in different orders or partitioned in different ways), all without departing from the scope of the subject matter.

[0120] It is understood that the specific order or hierarchy of steps in the disclosed process is illustrative of the method. Based on design preferences, it is understood that the specific order or hierarchy of steps in the process can be rearranged. Some steps may be performed simultaneously. The claims accompanying the method present the elements of various steps in a sample order, but this does not imply limitation to the specific order or hierarchy presented.

[0121] Description of the subject matter technology in the form of clauses:

[0122] Clause 1. An electronic tag comprising a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to a vein (IV) tube; and a sensor disposed within the housing and configured to measure the properties of fluid in the IV tube at the location of the clamping mechanism.

[0123] Clause 2. The electronic tag according to Clause 1, wherein the processor is configured to send a first signal to the infusion device via a transceiver and receive a second signal from the infusion device via a transceiver.

[0124] Clause 3, the electronic tag as described in Clause 2, wherein the first signal sent to the infusion device is configured to trigger an alarm at a location remote from the electronic tag in the event of a fault condition.

[0125] Clause 4. The electronic tag as described in Clause 2, wherein the transceiver includes a wireless communication device and is configured to communicate with the infusion device via a wireless connection.

[0126] Clause 5. The electronic tag as described in Clause 1, wherein: the processor is configured to: cause the electronic tag to receive, via a transceiver, infusion information about the contents of the IV infusion container and infusion parameters of the infusion process associated with the IV infusion container from the infusion device; and the display screen is configured to display the infusion information and infusion parameters.

[0127] Clause 6. The electronic tag according to Clause 1, wherein the housing includes a first elongated bracket configured to receive a portion of the IV tube, and the clamping mechanism includes a clamping arm and a spring configured to apply tension to the clamping arm to restrain the portion of the IV tube within the first elongated bracket.

[0128] Clause 7. The electronic tag pursuant to Clause 6, wherein: the display screen is disposed on a first side of the housing opposite to the first elongated bracket and the clamping arm; and wherein the clamping arm includes a second elongated bracket, the first elongated bracket and the second elongated bracket being configured to together surround a portion of the IV tube to constrain at least a portion of the IV tube between the clamping arm and the first elongated bracket.

[0129] Clause 8. The electronic tag according to Clause 7, wherein when the clamping arm is moved to constrain the IV tube, the first elongated bracket and the second elongated bracket form a substantially cylindrical shape, and wherein the sensor is disposed within the first elongated bracket and configured to contact the constrained IV tube.

[0130] Clause 9. The electronic tag as described in Clause 8, wherein the sensor includes an acoustic sensor configured to measure acoustics within at least a portion of the IV tube.

[0131] Clause 10. The electronic tag as described in Clause 8, wherein the sensor includes a pressure sensor configured to detect the fluid pressure within the IV tube at the location of the IV tube.

[0132] Clause 11. The electronic tag as described in Clause 1 also includes a lock for securing the electronic tag to the IV tube.

[0133] Clause 12. The electronic tag pursuant to Clause 1 further includes at least one color light-emitting diode (LED), wherein the at least one color LED is configured to emit a first color when a fault condition is present, and to emit a second color different from the first color during normal operation.

[0134] Clause 13. The electronic tag as described in Clause 1 further includes a signal transmitter configured to emit a signal for associating the electronic tag with an infusion device or a second electronic tag.

[0135] Clause 14. The electronic tag as described in Clause 13, wherein the signal transmitter includes an acoustic transducer or a pressure actuator.

[0136] Clause 15. A method of associating an intravenous (IV) infusion container with an infusion pump of an infusion device, the method comprising: receiving an IV tube coupled to the IV infusion container at the infusion pump, wherein an electronic tag is affixed to the IV tube, wherein the electronic tag includes: a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display screen coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to the intravenous (IV) tube; and a sensor disposed within the housing and configured to measure the properties of a fluid in the IV tube at a location of the clamping mechanism; causing a signal to be transmitted from at least one of the IV infusion container and the infusion pump of the infusion device; receiving from the electronic tag an acknowledgment message indicating that the sensor of the electronic tag has received an association signal; determining that the association signal corresponds to a signal transmitted by at least one of the IV infusion container and the infusion pump; causing the electronic tag to display a message indicating association with the IV infusion container or the infusion pump of the infusion device on the display screen of the electronic tag.

[0137] Clause 16. The method according to Clause 15, wherein: causing a signal to be transmitted from the IV infusion container comprises: applying pressure to the IV infusion container; and wherein the sensor of the electronic tag includes a pressure sensor; and wherein an acknowledgment message indicates that the electronic tag has detected an increase in fluid pressure in the IV tubing caused by the pressure applied to the IV infusion container.

[0138] Clause 17. The method according to Clause 16 further includes: causing the display screen of the electronic tag to display an instruction for applying pressure to the IV infusion container; and wherein the display of the message is based at least in part on determining that the confirmation message was received within a first time period measured from the time the instruction is displayed.

[0139] Clause 18. The method according to Clause 15, wherein: transmitting a signal at the infusion pump of the infusion device includes: transmitting an acoustic signal within the IV tube at the infusion pump of the infusion device; and wherein the sensor of the electronic tag includes an acoustic sensor; and wherein an acknowledgment message indicates that the electronic tag measures the acoustic signal detected in the IV tube caused by the acoustic signal generated at the infusion pump of the infusion device.

[0140] Clause 19. The method according to Clause 18, wherein: the acoustic signal generated at the infusion pump of the infusion device includes a modulated acoustic signal caused by a change in the movement of the pump in the infusion device; and wherein an acknowledgment message indicates the detected modulation of the acoustic signal detected in the IV tubing, and the method further includes determining that the detected modulation of the acoustic signal detected in the IV tubing corresponds to the modulation of the modulated acoustic signal generated at the infusion pump of the infusion device.

[0141] Clause 20, the method according to Clause 18, wherein causing the electronic tag to display a message is based at least in part on determining that the acknowledgment message was received within a threshold time period measured from the time of transmission of the signal.

[0142] Clause 21. The method described in Clause 18 further includes: transmitting from the infusion device information about the contents of the IV infusion container and parameters of the infusion process associated with the IV infusion container; and causing the electronic tag to display the information and parameters on the display screen of the electronic tag.

[0143] Clause 22. A method for associating an intravenous (IV) infusion container with an infusion pump of an infusion device, the method comprising: determining at an electronic tag affixed to an IV tube coupled to the IV infusion container, wherein the electronic tag includes: a housing; a processor within the housing; a transceiver disposed within the housing and coupled to the processor; a display screen coupled to the housing and the processor and configured to display information received via the transceiver; a clamping mechanism coupled to the housing and configured to secure the electronic tag to the intravenous (IV) tube; and a sensor disposed within the housing and configured to, during clamping... The device measures the properties of the fluid in the IV tubing at its location; receives a signal transmitted from at least one of the IV infusion container and the infusion pump of the infusion device; generates an acknowledgment message by an electronic tag based on the signal, indicating that the sensor of the electronic tag has received the associated signal; transmits the acknowledgment message to at least one of the IV infusion container and the infusion pump of the infusion device; receives a message indicating the association with the IV infusion container or the infusion pump of the infusion device from the IV infusion container or the infusion pump of the infusion device; and causes the electronic tag to display the message indicating the association with the IV infusion container or the infusion pump of the infusion device on the display screen of the electronic tag.

[0144] Clause 23. A method of associating an intravenous (IV) infusion container with an infusion pump of an infusion device, the method comprising: attaching a first electronic tag at a first location along a fluid path between the IV infusion container and the infusion device, the first electronic tag comprising: a first housing; a first processor located within the first housing; a first transceiver disposed within the first housing and coupled to the first processor; a first display coupled to the first housing and the first processor and configured to display information received via the first transceiver; a first clamping mechanism coupled to the first housing and configured to secure the first electronic tag to the IV tube; and a first sensor disposed within the first housing and configured to measure properties of the fluid in the IV tube at the location of the first clamping mechanism; attaching a second electronic tag at a second location along the fluid path, the second electronic tag... The device includes: a second housing; a second processor within the housing; a second transceiver disposed within the second housing and coupled to the second processor; a second display screen coupled to the second housing and the second processor and configured to display information received via the second transceiver; a second clamping mechanism coupled to the second housing and configured to secure a second electronic tag to a venous (IV) tube; and a second sensor disposed within the second housing and configured to measure the properties of the fluid in the IV tube at the location of the second clamping mechanism; generating a first signal at a signal generator of the first electronic tag; and, based on the determination that the second sensor of the second electronic tag receives the first signal generated at the signal generator of the first electronic tag: displaying a message on the first display screen of the first electronic tag and on the second display screen of the second electronic tag that the IV fluid infusion container is associated with the IV tube.

[0145] For convenience, various examples of aspects of this disclosure are described as numbered clauses (1, 2, 3, etc.). These are provided as examples and do not limit the technical scope of the subject matter. The identification of the figures and reference numbers is provided below for illustrative purposes only, and the clauses are not limited by these identifications.

[0146] Further consideration:

[0147] It is understood that the specific order or hierarchy of steps in the disclosed process is illustrative of the method. Based on design preferences, it is understood that the specific order or hierarchy of steps in the process can be rearranged. Some steps may be performed simultaneously. The claims accompanying the method present the elements of various steps in a sample order, but this does not imply limitation to the specific order or hierarchy presented.

[0148] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The foregoing description provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to an element in the singular is not intended to mean "one and only one," but rather "one or more." Unless otherwise specifically stated, the term "some" means one or more. Male pronouns (e.g., his) include female and neutral pronouns (e.g., her and its), and vice versa. Titles and subtitles, if any, are used for convenience only and do not limit the invention described herein.

[0149] As used herein, the term "website" can include any aspect of a website, including one or more web pages, one or more servers used to host or store web-related content, etc. Therefore, the term "website" can be used interchangeably with the terms "web page" and "server." The predicates "configured as," "operable as," and "programmed as" do not imply any specific tangible or intangible modification of the subject, but are intended to be used interchangeably. For example, "processor configured as a monitoring and control operation or component" can also mean "processor programmed as a monitoring and control operation" or "processor operable as a monitoring and control operation." Similarly, "processor configured to execute code" can be interpreted as "processor programmed to execute code" or "operable as executing code."

[0150] As used herein, the term "automatic" can include actions performed by a computer or machine without user intervention; for example, by instructions issued by a computer, machine, or other initiation mechanism in response to a predicate action. The word "example" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as an "example" is not necessarily to be construed as preferential or superior to other aspects or designs.

[0151] Phrases such as "aspect" do not imply that such an aspect is essential to the present subject matter, or that such an aspect applies to all configurations of the present subject matter. Disclosures relating to 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 imply that such an embodiment is essential to the present subject matter, or that such an embodiment applies to all configurations of the present subject matter. Disclosures relating to an embodiment may apply to all implementations, or one or more implementations. 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 imply that such a configuration is essential to the present subject matter, or that such a configuration applies to all configurations of the present subject matter. Disclosures relating to 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.

Claims

1. An electronic tag, the electronic tag comprising: case; The processor inside the housing; A transceiver, disposed within the housing and coupled to the processor, wherein the processor is configured to transmit a first signal to the infusion device via the transceiver and to receive a second signal from the infusion device via the transceiver; A display screen, coupled to the housing and the processor, is configured to display information received via the transceiver; A clamping mechanism coupled to the housing and configured to secure the electronic tag to the IV tube; as well as A sensor, disposed within the housing and configured to measure the properties of a fluid in an IV tube at the location of the clamping mechanism, includes either an acoustic sensor for measuring acoustic properties within at least a portion of the IV tube, or a pressure sensor for detecting the fluid pressure within the IV tube at the location of the IV tube. The fluid properties measured by the sensor are transmitted to the infusion device via a transceiver, and information displayed on the display screen is displayed in response to a control signal received from the infusion device via the transceiver. The processor is configured to determine that the electronic tag is correctly associated with a specific IV infusion container based on the acoustic signal generated by the acoustic transducer or infusion pump attached to the IV tube detected by the acoustic sensor, or the pressure change generated by the squeezing of the IV infusion container detected by the pressure sensor.

2. The electronic tag according to claim 1, wherein, The first signal sent to the infusion device is configured to trigger an alarm at a location remote from the electronic tag in the event of a malfunction.

3. The electronic tag according to claim 1, wherein, The transceiver includes a wireless communication device and is configured to communicate with the infusion device via a wireless connection.

4. The electronic tag according to claim 1, wherein: The processor is configured to cause the electronic tag to receive, via the transceiver, infusion information about the contents of the IV infusion container and infusion parameters of the infusion process associated with the IV infusion container from the infusion device; and The display screen is configured to display the infusion information and the infusion parameters.

5. The electronic tag according to claim 1, wherein, The housing includes a first elongated bracket configured to receive a portion of the IV tube, and the clamping mechanism includes a clamping arm and a spring configured to apply tension to the clamping arm to constrain the portion of the IV tube within the first elongated bracket.

6. The electronic tag according to claim 5, wherein: The display screen is disposed on a first side of the housing opposite to the first elongated bracket and the clamping arm; as well as The clamping arm includes a second elongated bracket, and the first elongated bracket and the second elongated bracket are configured to jointly surround the portion of the IV tube to constrain at least the portion of the IV tube between the clamping arm and the first elongated bracket.

7. The electronic tag according to claim 6, wherein, When the clamping arm is moved to constrain the IV tube, the first elongated bracket and the second elongated bracket form a substantially cylindrical shape, and the sensor is disposed within the first elongated bracket and configured to contact the constrained IV tube.

8. The electronic tag according to claim 1, further comprising a lock for securing the electronic tag to the IV tube.

9. The electronic tag of claim 1 further comprises at least one color light-emitting diode (LED), wherein the at least one color LED is configured to emit a first color when a fault condition is present, and to emit a second color different from the first color during normal operation.

10. The electronic tag of claim 1, further comprising a signal transmitter configured to emit a signal for associating the electronic tag with an infusion device or a second electronic tag.

11. The electronic tag according to claim 10, wherein, The signal transmitter includes an acoustic transducer or a pressure actuator.

12. A method for associating an intravenous IV infusion container with an infusion pump of an infusion device, the method comprising: An IV tube coupled to an IV infusion container is received at the infusion pump, wherein an electronic tag is attached to the IV tube, the electronic tag comprising: case; The processor inside the housing; A transceiver, which is disposed within the housing and coupled to the processor; A display screen, coupled to the housing and the processor, is configured to display information received via the transceiver; A clamping mechanism, coupled to the housing and configured to secure the electronic tag to the IV tube; and A sensor is disposed within the housing and configured to measure the properties of the fluid in the IV tube at the location of the clamping mechanism; Cause a signal to be transmitted from at least one of the IV infusion container and the infusion pump of the infusion device, wherein causing the signal to be transmitted from the IV infusion container includes: applying pressure to the IV infusion container; The electronic tag receives an acknowledgment message indicating that the sensor of the electronic tag has received an associated signal, and The electronic tag's sensor includes an acoustic sensor configured to measure acoustic pressure within at least a portion of the IV tube, or the sensor includes a pressure sensor configured to detect fluid pressure within the IV tube at a location within the IV tube; and The confirmation message indicates that the electronic tag has detected an increase in fluid pressure in the IV tubing caused by pressure applied to the IV infusion container; Determine that the associated signal corresponds to a signal transmitted by at least one of the IV infusion container and the infusion pump; Information about the contents of the IV infusion container and parameters of the infusion process associated with the IV infusion container are transmitted from the infusion device; and This causes the electronic tag to display a message on its display screen indicating association with the IV infusion container or the infusion pump of the infusion device, wherein the fluid properties measured by the sensor are transmitted to the infusion device via the transceiver, and wherein the message on the display screen is displayed in response to a control signal received from the infusion device via the transceiver. The processor determines that the electronic tag is correctly associated with a specific IV infusion container based on the acoustic signal generated by the acoustic transducer or infusion pump attached to the IV tube detected by the acoustic sensor, or the pressure change generated by the squeezing of the IV infusion container detected by the pressure sensor.

13. The method of claim 12, further comprising: This causes the display screen of the electronic tag to show instructions for applying pressure to the IV infusion container; as well as The message is displayed based at least in part on the determination that the confirmation message was received within a first time period measured from the time the instruction was displayed.

14. The method according to claim 12, wherein: Transmitting signals at the infusion pump of the infusion device includes: transmitting acoustic signals within the IV tubing at the infusion pump of the infusion device; and The electronic tag's sensor includes an acoustic sensor; and The confirmation message indicates that the electronic tag measures the acoustic signal detected in the IV tube caused by the acoustic signal generated at the infusion pump of the infusion device.

15. The method of claim 14, wherein: The acoustic signal generated at the infusion pump of the infusion device includes a modulated acoustic signal, which is caused by changes in the movement of the pump in the infusion device; and The confirmation message indicates the detected modulation of the acoustic signal in the IV tube, and the method further includes: The detected modulation of the acoustic signal detected in the IV tube is determined to correspond to the modulation of the modulated acoustic signal generated at the infusion pump of the infusion device.

16. The method according to claim 13, in, The electronic tag displays the message at least in part based on the determination that the confirmation message was received within a threshold time period measured from the time the signal was transmitted.

17. A method for associating an intravenous IV infusion container with an infusion pump of an infusion device, the method comprising: The electronic tag is located at the point where it is attached to the IV tubing coupled to the IV infusion container, wherein the electronic tag comprises: case; The processor inside the housing; A transceiver, which is disposed within the housing and coupled to the processor; A display screen, coupled to the housing and the processor, is configured to display information received via the transceiver; A clamping mechanism, coupled to the housing and configured to secure the electronic tag to the IV tube; and A sensor, disposed within the housing and configured to measure the properties of a fluid in an IV tube at the location of the clamping mechanism, wherein the sensor includes an acoustic sensor configured to measure acoustic properties within at least a portion of the IV tube, or the sensor includes a pressure sensor configured to detect the fluid pressure of the fluid within the IV tube at the location of the IV tube. Receive a signal transmitted from at least one of the IV infusion container and the infusion pump of the infusion device; The electronic tag generates a confirmation message based on the signal, indicating that the sensor of the electronic tag has received the associated signal; The confirmation message is transmitted to at least one of the IV infusion container and the infusion pump of the infusion device; Receive a message indicating association with the IV infusion container or the infusion pump of the infusion device from the IV infusion container or the infusion pump of the infusion device; This causes the electronic tag to display a message on its display screen indicating its association with the IV infusion container or the infusion pump of the infusion device. The processor determines that the electronic tag is correctly associated with a specific IV infusion container based on the acoustic signal generated by the acoustic transducer or infusion pump attached to the IV tube detected by the acoustic sensor, or the pressure change generated by the squeezing of the IV infusion container detected by the pressure sensor.

18. A method for associating an intravenous IV infusion container with an infusion pump of an infusion device, the method comprising: A first electronic tag is attached at a first location along the fluid path between the IV infusion container and the infusion device, the first electronic tag comprising: First shell; The first processor within the first housing; A first transceiver is configured within the first housing and coupled to the first processor; A first display screen is coupled to the first housing and the first processor and is configured to display information received via the first transceiver; A first clamping mechanism, coupled to the first housing and configured to secure the first electronic tag to the IV tube; and A first sensor is disposed within the first housing and configured to measure the properties of the fluid in the IV tube at the location of the first clamping mechanism, wherein the first sensor includes an acoustic sensor configured to measure acoustics within at least a portion of the IV tube, or the first sensor includes a pressure sensor configured to detect the fluid pressure of the fluid in the IV tube at the location of the IV tube. A second electronic tag is attached to a second location along the fluid path, the second electronic tag comprising: Second shell; The second processor is located within the second housing; A second transceiver is configured within the second housing and coupled to the second processor; A second display screen is coupled to the second housing and the second processor, and is configured to display information received via the second transceiver; A second clamping mechanism, coupled to the second housing and configured to secure the second electronic tag to the IV tube; and A second sensor is disposed within the second housing and configured to measure the properties of the fluid in the IV tube at the location of the second clamping mechanism; A first signal is generated at the signal generator of the first electronic tag; The determination is based on the second sensor of the second electronic tag receiving the first signal generated at the signal generator of the first electronic tag: The message that the IV infusion container is associated with the IV tube is displayed on the first display screen of the first electronic tag and on the second display screen of the second electronic tag.

Images