Volume monitoring system for intravenous infusion fluid containers

Abstract

A system, method, and apparatus for determining the volume of fluid in a drug container are disclosed. A drug infusion is initiated from the drug container. The drug container includes one or more radio frequency identification (RFID) tags affixed along one side of the container. Radio frequency (RF) signals are directed from a reader device to the RFID tags disposed on the drug container. The signal strength of one or more corresponding returned RF signals from the one or more RFID tags is detected; the returned RF signals include one or more identifiers for identifying the one or more RFID tags. A threshold signal level is determined for determining the fluid level within the drug container, and the volume of fluid is then determined by determining which of the returned corresponding RF signals has a signal strength that satisfies the threshold signal level.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 046,544 entitled “INTRAVENOUS FLUID CONTAINERVOLUME MONITORING SYSTEM”, filed June 30, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application typically relates to monitoring the volume of fluid in a drug container. Background Technology

[0004] Intravenous (IV) infusions are typically run unattended after a nurse has set the infusion volume to be administered for a specific duration. The infusion device (e.g., an infusion pump) can be configured with a VTBI (Total Volume Infused). For example, a clinician can input the infusion rate and duration, and the infusion device can generate the VTBI. Alternatively, the clinician can use the VTBI to initiate the infusion. Sometimes, the clinician can start from the VTBI. Typically, the infusion pump calculates an estimate of the infused volume and alerts the nurse when the prescribed VTBI is reached, notifying them to change the IV bag. The infusion process can be interrupted if timely notification is not provided. Summary of the Invention

[0005] Under normal operating conditions, some pumps may run faster, but still within the pump's performance specifications tolerances. Existing pumps cannot measure the actual infusion volume as the running speed increases. For example, some infusion pumps may only calculate the expected infusion volume (at the rated rate), excluding actual over-infusion volumes. In other words, over-infusion may occur when the pump exceeds its VTBI (VTBI), which may still be within tolerance limits. For example, for a pump running at 60 ml / h for 8 hours, if it runs 5% faster, the pump will empty a 500 mL bag approximately 20 minutes earlier than expected. This can cause air to be drawn into the pump. In this case, the pump will alarm after the air reaches the air bubble ingress (AIL) sensor. Caregivers may then have to disconnect the device, refill it to remove the air, and then restart the infusion. This interruption can lead to infection, increase caregiver time and workload, and increase the number of steps that could result in errors.

[0006] Therefore, there is a need for a method and system for monitoring the fluid volume in IV solution containers so as to provide timely notification that the container is empty or about to become empty.

[0007] The disclosed subject matter relates to a system, apparatus, and method for determining the volume of fluid in a drug container. According to some embodiments, drug infusion is initiated from a drug container (e.g., an IV solution bag or infusion container). The drug container includes one or more electronic tags affixed along one side of the drug container. For the purposes of this disclosure, the apparatus, system, and method disclosed herein are described as using radio frequency identification (RFID) tags. However, other tags configured to receive and transmit signals through a liquid medium may also be used.

[0008] A monitoring device for monitoring the volume of a drug container includes one or more radio frequency (RF) devices providing an RF transmitting source and an RF receiving source; one or more processors; and a non-transitory memory device having instructions thereon that, when executed by the one or more processors, cause the monitoring device to perform operations. According to various embodiments, the operations include transmitting RF signals via the RF transmitting source toward a plurality of RFID tags disposed on one side of a drug container associated with an infusion device from which a drug is administered, wherein said side of the drug container is opposite the side of the drug container closest to the RF transmitting source, such that the RF signals pass through the drug container before interacting with the RFID tags; detecting the signal strength of returned RF signals from the RFID tags via the RF receiving source, each of the returned RF signals including an identifier identifying the corresponding RFID tag; determining a threshold signal level associated with detecting fluid within the drug container based on at least one of the returned identifiers; determining the volume of fluid within the drug container based on comparing the signal strength of each returned RF signal to the determined threshold signal level; and providing an electronic indication of the volume. Other aspects include corresponding methods, systems, and computer program products for implementing the monitoring device and its features.

[0009] A disclosed method includes directing a radio frequency (RF) signal from an RF source to one or more RFID tags disposed on a drug container. The method further includes using an RF reader to detect the signal strength of one or more returned corresponding RF signals from the one or more RFID tags, the returned RF signals including one or more identifiers for identifying the one or more RFID tags. The method includes determining a threshold signal level based on the one or more identifiers for determining a fluid level within the drug container, and determining whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level. Based on the determination that the signal strength of the returned RF signals meets the threshold signal level, the method includes providing an indication that the fluid within the drug container is at a first volume; and based on the determination that the signal strength does not meet the threshold signal level, the method includes providing an indication that the fluid within the drug container is at a second volume.

[0010] The disclosed subject matter also relates to a machine-readable medium embodying instructions that, when executed by a machine, allow the machine to perform a method for determining the volume of fluid in a drug container.

[0011] The disclosed subject matter also relates to a system for determining the volume of fluid in a drug container. 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.

[0012] This subject matter provides a system for determining the volume of fluid in a drug container, including one or more processors and a memory. The memory includes instructions that, when executed by the one or more processors, cause the system to initiate drug infusion from the drug container. The drug container includes one or more radio frequency identification (RFID) tags adhered along one side of the drug container. The system directs radio frequency (RF) signals from an RF source to the one or more RFID tags disposed on the drug container. The system also uses an RF reader to detect the signal strength of one or more returned corresponding RF signals from the one or more RFID tags, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags. The system determines a threshold signal level based on the one or more identifiers for determining the level of fluid within the drug container, and determines whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level. Based on the determination that the signal strength of the returned RF signals meets the threshold signal level, the system provides an indication that the fluid within the drug container is in a first volume; and based on the determination that the signal strength does not meet the threshold signal level, the system provides an indication that the fluid within the drug container is in a second volume. Other aspects include corresponding methods, apparatus, and computer program products for implementing the corresponding system and its features.

[0013] 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

[0014] 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.

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

[0016] Figure 2A An example of a system for determining the volume of fluid within a drug container, based on aspects of the art in this subject matter, is depicted.

[0017] Figure 2B This illustrates aspects of the technology according to this subject matter. Figure 2A Another example implementation of the system utilizes multiple separate electronic tags to monitor the fluid volume in the container.

[0018] Figure 3 An example of a drug container with two RFID tags for determining the volume of fluid inside the drug container is depicted, according to aspects of the subject matter.

[0019] Figure 4 An example process for determining the fluid volume within a drug container, based on aspects of the art in this subject matter, is described.

[0020] Figure 5 This is a conceptual diagram illustrating an example electronic system 500 for determining the volume of fluid within a drug container, 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] Intravenous infusion (IV) containers, such as infusion bags, are bags made of plastic material that hold fluid with a volume between 250 and 1000 mL. Due to sterility requirements, these containers are typically disposable. Under normal operating conditions, some pumps run at higher speeds, but still within the pump's performance specifications. For example, a pump running at a rate of 60 mL / h is expected to empty a 500 mL IV bag in a little over 8 hours. If the running speed is increased by 5%, the pump will empty the 500 mL bag approximately 20 minutes earlier than expected. In some cases, increasing the pumping speed can cause air to be drawn into the pump. In this situation, the pump will alarm upon reaching the air-in-line (AIL) sensor. Caregivers may then have to disconnect the infusion set, refill it to remove the air, and then restart the infusion. This interruption can lead to infection, increase caregiver time and workload, and increase the number of steps that can result in errors. Therefore, there is a need for a method and system to monitor the fluid volume in IV containers to provide timely notification that the container is empty or about to be empty.

[0023] The methods and systems according to this subject matter utilize sensing elements attached to IV infusion fluid containers (e.g., bags, bottles, etc.), which are low in cost and complexity and do not excessively increase the cost of IV infusions. According to this subject matter, a single large radio frequency identification (RFID) tag or several RFID tags are used to monitor the fluid level in the IV container. One or more RFID tags are placed on the container, and the power level of the signal response from the RFID tags is detected. By monitoring changes in the RF power level of the detected RFID signal from the RFID tags, the fluid level in the IV container with the RFID tag attached is determined.

[0024] Figure 1 An example of an institutional patient care system 100 of a healthcare organization, based on aspects of the subject matter technology, is depicted. Figure 1 In this system, patient care equipment (or generally "medical equipment") 12 is connected to the 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 12 is connected to the internal healthcare network 10 via a transmission channel 31. The transmission channel 31 is any wired or wireless transmission channel, such as an 802.11 wireless local area network (LAN). In some embodiments, network 10 also includes computer systems located in various departments throughout the hospital. For example, Figure 1 Network 10 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 10 may include discrete subnetworks. In the depicted example, healthcare network 10 includes device network 41 through which patient care devices 12 (and other devices) communicate in accordance with normal operation.

[0025] Additionally, the institutional patient care system 100 may include a separate information system server 130, the functions of which will be described in more detail below. Furthermore, although the information system server 130 is shown as a separate server, its functionality and programming can be incorporated into another computer if desired by the engineers designing the institutional information system. The institutional patient care system 100 may also include one or more device terminals 132 for connecting to and communicating with the information system server 130. Device terminals 132 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 130 via network 10.

[0026] Patient care device 12 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 12 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 12 includes a control module 14, also referred to as interface unit 14, connected to one or more functional modules 116, 118, 120, 122. Interface unit 14 includes a central processing unit (CPU) 50 connected to memory (e.g., random access memory (RAM) 58), and one or more interface devices, such as user interface device 54, coded data input device 60, network connection 52, and auxiliary interface 62 for communicating with additional modules or devices. Interface unit 14 also (though not necessarily) includes a primary non-volatile storage unit 56 (such as a hard disk drive or non-volatile flash memory) for storing software and data, and one or more internal buses 64 for interconnecting the aforementioned components.

[0027] In various embodiments, the user interface device 54 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 54 may include any means for displaying and inputting information, such as a monitor, printer, keyboard, soft keys, mouse, trackball, and / or light pen. The data input device 60 may be a barcode reader capable of scanning and interpreting data printed in barcode format. Additionally or alternatively, the data input device 60 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 60 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 60 include voice-activated or recognition devices or portable personal data assistants (PDAs). Depending on the type of interface device used, the user interface device 54 and the data input device 60 may be the same device. Although the data input device 60 is... Figure 1 The data input device 60 is shown as being housed within interface unit 14; however, it is understood that the data input device 60 may be integrated within pharmacy system 34 or located externally and communicate with pharmacy system 34 via an RS-232 serial interface or any other suitable communication device. Auxiliary interface 62 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 60 may be a separate functional module, such as modules 116, 118, 120, and 122, and configured to communicate with controller 14 or any other system on the network using suitable programming and communication protocols.

[0028] Network connection 52 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.

[0029] Functional modules 116, 118, 120, and 122 are any devices used to provide care to patients or to monitor patient conditions. For example... Figure 1As shown, at least one of functional modules 116, 118, 120, and 122 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 116 is an infusion pump module. Each of functional modules 118, 120, and 122 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 118, 120, and / or 122 can be printers, scanners, barcode readers, or any other peripheral input, output, or input / output device.

[0030] Each functional module 116, 118, 120, and 122 communicates directly or indirectly with interface unit 14, which provides overall monitoring and control of device 12. For example... Figure 1 As shown, or as detailed by Eggers et al., functional modules 116, 118, 120, and 122 can be physically and electronically connected serially to one or both ends of interface unit 14. 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 14. As described above, additional medical devices or peripheral devices can be connected to patient care device 12 via one or more auxiliary interfaces 62.

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

[0032] Although each functional module may be able to operate independently to some extent, the interface unit 14 monitors and controls the overall operation of the device 12. For example, as will be described in more detail below, the interface unit 14 provides programming instructions to functional modules 116, 118, 120, and 122 and monitors the status of each module.

[0033] Patient care device 12 can operate in several different modes or personalities, each defined by a configuration database. The configuration database can be an internal database 56 of the patient care device or an external database 37. 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 patient care device 10 within a hospital or hospital computer network. Patient care information can be entered via interface devices 52, 54, 60, or 62 and can originate from anywhere within network 10, such as, for example, from a pharmacy server, admission server, laboratory server, etc.

[0034] 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.

[0035] Data from 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 12 and network 10 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 54 (e.g., ...). Figure 1 (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 12 and network 10 involves the physical, intermittent, or periodic transfer of data between systems using, for example, user interface device 54, coded data input device 60, 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 of distributed data sources as possible. Decision making can occur in various locations within network 10. For example, rather than in a restricted manner, decisions can be made at HIS server 30, decision support 48, remote data server 49, hospital department or unit station 46, or within patient care device 12 itself.

[0036] All direct communication with medical devices operating on a network according to the present invention can be performed through an information system server 30 (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.

[0037] Figure 2A An example system 200 according to an aspect of the present subject matter is shown, which monitors the volume of fluid in a medication container by means of a series of electronic tags attached to the container. For example, the medication container is an IV bag 202. The IV bag 202 is magnified relative to a pump 22 to illustrate an aspect of the present subject matter. The IV bag 202 includes fluid 204 infused to a patient using the pump 22. The height 216 of the fluid 204 varies depending on the volume of fluid 204 in the IV bag 202.

[0038] Figure 2A Ten radio frequency identification (RFID) tags 206-a, 206-b, 206-c, 206-d, 206-e, 206-f, 206-g, 206-h, 206-i, 206-k, 206-k, and 206-l are shown adhered to the exterior of IV bag 202. The RFID tags can be mass-produced at very low cost, sterilized using common sterilization methods, and easily applied (e.g., affixed) to the outer surface of the IV container. In Figure 2, most of the RFID tags (e.g., 206-c to 206-l) are adjacent to the fluid 204 in the z-direction (e.g., into the plane of Figure 2) (e.g., separated only by a single layer of IV bag 202). RFID tag 206-a is adjacent to air (e.g., the y-position of RFID tag 206-a is above height 216), while a portion of RFID tag 206-b is adjacent to air, and the remainder of RFID tag 206-b is adjacent to fluid 204 in IV bag 202.

[0039] According to various implementation methods, such as Figure 2AAs shown, multiple RFID tags can be placed adjacent to each other in series to form a continuous tag strip (e.g., on a base strip of material, which is then attached to the bag). In other embodiments, different numbers of RFID tags are used. For example, in some embodiments, a single RFID tag is used. In some embodiments, a single RFID tag spans a portion (e.g., a quarter, half, more than three-quarters) of the total length (along the height 216 dimension) of the IV bag 202. In some embodiments, some (e.g., two, three, four, five, six, seven... or more than twenty, etc.) RFID tags are adhered to spaced locations on the IV bag 202 (e.g., not consecutively, as shown in Figure 2). In the foregoing example, the tags can be attached to the underlying material strip (adjacent to each other or spaced apart on the material), and the material adheres to the bag 202.

[0040] In the depicted example, the infusion device control module 14 (hereinafter referred to as infusion device 14) includes an internal RFID reader 208. The internal RFID reader may include a sensor attached to or implemented within the housing of the infusion device, adjacent to a location configured to secure the IV bag. (See reference...) Figure 2B As further described, reader 208 may be an external device. Reader 208 includes a radio frequency (RF) source, such as a transmitter (“TX”), that emits RF radiation 210. In some embodiments, the RF radiation is low-frequency (LF) RF radiation, for example, between 30-300 kHz or 120-150 kHz.

[0041] The reader 208 may include one or more transceivers or separate transmitters and receivers for communicating with a corresponding electronic tag adhered to the drug container 202. For the purposes of this disclosure, the terms “transceiver” and / or “receiver” and / or “transmitter” and / or “receiver / transmitter” are used interchangeably and may refer to one or more transceivers or combinations of transmitters and receivers. In some embodiments, the receiver / transmitter (TX / RX) of the reader 208 is very close to the tag. In various embodiments, the electronic tag is an RFID tag and may operate at a frequency of approximately 150 kHz. For example, in some embodiments, the TX / RX unit may be placed at the lever clip near the IV bag to achieve this purpose. In some embodiments, when the TX / RX unit is located in a pump or control module, the pump or control unit (and the TX / RX unit) may be placed approximately 1 m away from the IV bag. In this configuration, the RFID tag may operate in a frequency range of approximately 13 to 900 MHz.

[0042] The control module 14 may also include one or more input devices, such as control keys 264 or a barcode scanner (not shown), for scanning information related to infusion, patients, clinicians, or other relevant information. In some embodiments, the display 54 may be implemented as a touchscreen display.

[0043] Functional module 116 includes a door 250 and a handle 252, 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 mechanism and to load management devices for the pump. In some embodiments, a display 254 (such as an LED display) may be positioned in a prominent location on the door and may be used to visually convey various information related to functional module 116, such as alarm indications (e.g., alarm messages). Control keys 256 are present for programming and controlling the operation of functional module 116 as needed. In some embodiments, control keys may be omitted and presented as interactive elements on display 254 (e.g., a touchscreen display). Functional module 116 also includes an audio alarm device in the form of a speaker (not shown).

[0044] In some embodiments, IV bag 202 is positioned no more than 3 feet from infusion device 14. In some embodiments, RFID tags 206-a to 206-l are passive RFID tags, each including an antenna for receiving and transmitting RF signals and a microchip (e.g., an integrated circuit for storing and processing information and modulating and demodulating RF signals). Tag information is stored in non-volatile memory on the microchip. Passive RFID tags do not include batteries; instead, the tags use radio power transmitted by an RF source (e.g., in an RF reader). In some embodiments, RFID tags are read-only, and each RFID tag includes a factory-assigned serial number that allows the RF reader to identify a specific RFID tag. Because RFID tags have unique serial numbers, RFID readers are able to distinguish several tags within the RFID reader's range and read them simultaneously.

[0045] When the internal antenna of an RFID tag draws energy from RF radiation 210 and uses that energy to power the tag's own microchip, passive RFID tags 206-a to 206-l respond to RF radiation 210 or signals from RFID reader 208. The microchip of the RFID tag generates an RF signal 212 that encodes information (e.g., RFID tag-specific), and signal 212 is detected by RFID reader 208. For example, RF signal 212 originates from RFID tag 206-c and encodes information about the identity of RFID tag 206-c. RFID reader 208 is then able to decrypt the source of RF signal 212 to originate from RFID tag 206-c.

[0046] The fluid 204 within the IV bag is typically a fluid-based medication primarily composed of water. When the RFID tag is adjacent to the fluid 204 (e.g., the RFID tag is separated from the fluid 204 by only one layer of the IV bag 202 along the z-direction), the background dielectric of the RFID tag is therefore essentially water. Water is a polar dielectric, which cancels out most of the incident electric field passing through it. This cancellation of the incident electric field is equivalent to the fluid absorbing the RF signal from the RFID reader 208. In some embodiments, the RFID tag is placed on one side of the bag opposite the RFID reader 208, such that any signal transmission between the RFID reader 208 and the RFID tag 206 can pass through the IV bag and the fluid therein. In other words, the signal from the RFID reader 208 is directed through the interior space of the IV bag 202, and one or more RFID tags 206 are positioned on the IV bag 202 opposite the interior space. In this configuration, the returned RF signal from the RFID tag (e.g., when the RFID tag is only half-covered by the fluid) will also pass through the fluid before the RFID reader 208 can detect it. The signal may also have to pass through the plastic, which can cause signal attenuation. This configuration can be used in situations where there is no fluid interaction with the label.

[0047] When RF signal 210 is transmitted by RFID reader 208 through the IV bag to the corresponding RFID tag, the internal antenna of the RFID can draw less (or no) energy from RF signal 210 when a high dielectric fluid is present near the RFID tag. The microchip of RFID tag 206 then has less (or no) energy to use to generate a response RF signal 212. Therefore, the signal strength of the response RF signal 212 can provide an indication of the fluid level in the IV bag.

[0048] In some implementations, one or more RFID tags are placed on the front side of the IV bag (e.g., in front of the fluid). The presence of a high-dielectric current behind the RFID tag causes the characteristic frequency (e.g., resonant frequency) of the RFID tag's internal antenna to become skewed, making the internal antenna less able (or unable) to draw energy from the RF signal 210 emitted by the RFID reader 208. As a result, when a high-dielectric current is present adjacent to the RFID tag, the microchip available for the RFID tag to generate the return RF signal 212 has less (or no) energy.

[0049] When the fluid level 216 has dropped below the location of a specific RFID tag (e.g., RFID tag 206-a) (e.g., along the y-direction), the internal antenna of that RFID tag (e.g., RFID 206-a) is able to extract most or all of the RF energy from signal 21, because air does not cancel out the electric field of RF signal 210 as water does. Therefore, when the RFID tag is no longer adjacent to water, the return signal 212 generated by RFID tag 206-a is stronger. As a result, system 200 is able to sense the presence of fluid 204 near RFID tag 206 based on the controlled degradation of the RFID tag's power characteristics (e.g., in the return RF signal 212).

[0050] In some implementations, the signal strength of the returned RF signal 212 is monitored by a Received Signal Strength Indication (RSSI) power level. RSSI is a measurement of the power present in the received radio signal. This signal is then correlated with the fluid level in the IV container. The amount of surface area of ​​the tag covered by the fluid can be proportional to the signal strength sensed by the tag. Therefore, when a tag in strip form is placed on one side of the IV bag in a linear direction corresponding to the height of the fluid inside the bag when the bag is suspended in place, the tag's signal strength can indicate the height of the fluid inside the bag.

[0051] In some implementations, the correlation between the surface area of ​​the tag (or strip of the tag) adjacent to the fluid, the signal strength, and the amount of fluid in the bag can be determined based on a calibration process. During calibration, the power characteristics of one or more RFID tags are measured as a function of the volume of that particular type of fluid in the IV bag prior to an infusion procedure for that particular type of fluid. In some implementations, when a single RFID tag is used on a portion of the IV bag 202, the calibration process includes generating a lookup table that correlates the received power in the returned RF signal 212 detected by the RF reader 210 with the height (and therefore the volume) of the fluid 204 present in the IV bag. For a single RFID tag, the fluid present in the medication container causes antenna misalignment, resulting in a reduced signal strength of the RF signal from the RFID tag. As the fluid level in the medication container decreases, the portion of the RFID tag adjacent to the fluid decreases, resulting in an increase in the signal strength of the RF signal.

[0052] In some embodiments, system 200 includes an RFID reader 208 that senses RSSI power to determine the fluid level in the medication container. The RFID reader 208 communicates with the infusion pump to provide fluid level information, which in some embodiments includes a signal strength value indicating the remaining fluid volume. The processor 50 of the infusion pump performs a lookup to determine the amount of fluid remaining in the IV bag. In some embodiments, the RFID reader 208 receives RF signals, and processing of the received signals is performed by some processor (in the pump, control unit, or reader). In some embodiments, this processing may be performed in the PCU pump control unit. In some embodiments, the location where processing of the received signals is performed may depend on the placement of the RFID TX / RX unit. This processing may be performed by the reader, and the indication of the fluid level is transmitted from the reader to the pump. In some embodiments, the reader may periodically read the tag, and the pump may query the reader for the current reading or instruct the reader to read the reading and return the result value. If necessary, the processor generates an alarm indicating that the medication container is empty before the infusion line is purged and air is drawn into the system. In some implementations, the infusion pump includes software for converting RFID tag signals into actionable messages for caregivers (e.g., changing medication containers).

[0053] According to aspects of the subject matter, an example manner of configuring the pump to administer medication to a patient (hereinafter referred to as the operating procedure) includes: initiating a procedure to initialize an IV bag volume monitoring system (“IV-BVMS”). In some embodiments, the IV-BVMS includes system 200.

[0054] The workflow includes inputting information about the infusion process. This input may include the medication to be administered, the IV bag's fill volume (e.g., the total volume of fluid in the IV bag at the start of the infusion process). Some medications may have stronger dielectric properties than others. In this respect, different signal intensities can be associated with different medications, so a lookup table can associate different signal intensities of different medications with the same fluid level. Some infusion pumps may have multiple channels, allowing the delivery of multiple medications to the same patient. For infusion pumps with multiple channels, information about pump associations, such as which channel of the pump is associated with which IV bag, can also be entered in this part of the workflow. The workflow may include reading the RFID tag on the IV bag to verify the information entered so far during the workflow. The final step of the workflow includes connecting the IV line (e.g., the delivery device) to the pump before starting the IV infusion process.

[0055] During infusion, the initially initialized IV-BVMS periodically detects signals from RFID tags attached to the IV bag. In some implementations, signals from the RFID tags are detected periodically every 1–5 minutes (e.g., reading the RFID tag at one-minute intervals, two-minute intervals, three-minute intervals, four-minute intervals, five-minute intervals, etc.). The length of the detection interval can depend on the infusion flow rate and the volume of fluid in the IV bag. More frequent detections can be performed for high flow rates. In some implementations, the detection interval changes as the infusion progresses (e.g., shortens). At the beginning of the infusion process, when a relatively large amount of fluid remains in the IV bag, the IV bag volume can be detected less frequently. As the volume of fluid in the IV bag decreases, the volume of remaining fluid in the bag can be detected more frequently to provide timely warning to clinicians when the IV bag is rapidly empty.

[0056] The RFID tag detection process includes: an internal RFID reader 208 that transmits an RF signal 210; and an RFID reader 208 that receives a return signal 212 from one or more RFID tags 206-a...206-l. In some embodiments, a single RF signal is transmitted to trigger a response from most (e.g., all) RFID tags on the IV bag 202, for example, responses from all RFID tags positioned along the entire height of the IV bag 202 during operation. In some embodiments, the RFID tags may include configuration information, and the RFID reader 208 may be used during infusion setup to scan the configuration information prior to administration. The configuration information may include the identification of the respective tag and its position relative to other tags on the bag. In some embodiments, a master configuration RFID tag (or barcode) may be placed on the IV bag, which includes configuration information (e.g., identifier and placement position) for all tags on the bag. The infusion pump processor 50 is configured to receive the configuration tags and determine an appropriate lookup table for determining the amount of fluid in the bag during infusion (e.g., based on drug type, number of tags, tag position, identifier, etc.).

[0057] In some implementations, the RFID reader 208 is configured to detect / read multiple signals (e.g., from each of 10 tags) and process these signals sequentially. In some implementations, the signals are processed into one of two binary states (e.g., on or off): an on RFID tag (e.g., when there is no fluid in the IV bag behind the RFID tag) can transmit an ID number. The ID number can be correlated with a position on the IV bag (e.g., in the y-direction) to indicate the level of fluid present in the bag. In some implementations, once a strong signal (e.g., an RF signal with a signal strength above a threshold) is obtained from the first tag (“tag-1”), it is assumed that one or more tags above it (e.g., tags positioned higher in the y-direction) also emit high signals, thereby allowing detection of tags limited to those below the first tag (e.g., positioned lower in the y-direction). In some implementations, the RFID reader 208 is configured to monitor signal trends and account for cases where a strong signal is detected only momentarily due to temporary deviations.

[0058] In some implementations, no RF signal is received from the RFID tag when fluid is present adjacent to it. In such implementations, the RF reader detects two binary states—either an RF signal is received, indicating no fluid at the height of the RFID tag; or no RF signal is received, indicating fluid is present at the height of the RFID tag.

[0059] In some implementations, RSSI power provides a quantitative measurement of the amount of returned RF power. In such implementations, the liquid level in the medication container is considered to be below a height corresponding to the location of the RFID tag and / or its surface area when the RF reader detects a returned RF signal equal to or greater than a predetermined threshold. In some implementations, the predetermined threshold is obtained via a calibration system when the medication container is emptied. In such implementations, at the start of the infusion process, when the fluid level is above the RFID tag's location, the RF reader does not register any RF signal, or only registers a low level of RF signal. As the infusion process progresses, the detected RF signal begins to increase as the fluid level moves closer to the RFID tag. For applications requiring early warning, the predetermined threshold can be set to a lower amplitude. Generally, the infusion process begins with the RFID reader detecting little (or no) RF signal, and as the infusion process progresses, the RFID reader detects the maximum value when the fluid level is below the tag.

[0060] In some implementations, the IV-BVMS calculates the volume of remaining fluid. This calculation can be performed at the pump's processor 50. Measurements detected at the RFID reader 208 are transmitted to a server, where a processor performs calculations related to the amount of remaining fluid in the IV container.

[0061] For a first RFID tag that does not receive an RF signal or receives an RF signal below a threshold, the IV bag will be considered to have a fluid level covering at least half of the vertical / height dimension (e.g., the y-direction) of that tag. In some implementations, when the RFID reader 208 determines that a second tag directly above the first tag (for which it has not received one or more signals below a threshold) is emitting a strong signal, the processor sets the fluid level of the IV bag to a position between the first and second tags.

[0062] The IV-BVMS displays the remaining volume calculated based on signals detected by RFID reader 208, serving as confirmation of normal operation of the infusion pump. In some implementations, the IV-BVMS transmits information to clinicians (e.g., nursing staff at a nursing station) via a wireless communication (e.g., WiFi) connection for monitoring.

[0063] The IV-BVMS also compares the calculated infusion volume (based on the volume of remaining fluid detected by the RFID reader 208) with the expected infusion volume (i.e., based on pump time and flow rate). If the infusion volume differs from the expected infusion volume by a set percentage (e.g., 5%, 7%, 10%, 15%, 20%), the IV-BVMS issues an alert to the clinician to check the infusion process.

[0064] When the remaining volume in the IV bag falls below a set limit (e.g., less than 10%, less than 5%, less than 2%, etc.), an alarm is displayed or issued, or an alarm is sent to a computing device 132 associated with the clinician (e.g., a mobile device or smartphone), to indicate that the bag is nearly empty. The set limits are determined based on the total infusion volume and flow rate to ensure sufficient time for bag replacement.

[0065] When the RFID tags indicate that all volume has been drained from the bag (e.g., when all RFID tags return signals with power above a threshold), the infusion pump will stop and an alarm will notify caregivers that the IV bag is completely empty.

[0066] Figure 2B This illustrates aspects of the technology according to this subject matter. Figure 2AAnother example implementation of the system utilizes multiple separate electronic tags 302 and 304 to monitor the fluid volume in a container. In the depicted example, the electronic tags are not adjacent to each other, but are placed at two separate locations on an IV bag 308. The fluid level 306 of the fluid 310 in the IV bag 308 is close to tag 304, and a lower RF signal is received from tag 304. Conversely, since tag 302 is adjacent to air in the z-direction, a larger RF signal is detected from tag 302. As a result, IV-BVMS determines / calculates that the volume of fluid 310 remaining in the IV bag 308 is less than the height associated with the position of tag 302.

[0067] As fluid 310 is discharged through a height dimension (e.g., from height 312 to height 306), the RF signal 312 returned from tag 306 increases. The varying intensity of the RF signal indicates the change in fluid level at the height covered by tag 304.

[0068] Figure 3 An example intravenous infusion (IV) pole 300, having an example drug container 202 and an example reader 208 suspended thereon, is shown according to aspects of the subject matter. In the depicted example, the disclosed reader 208 is suspended on an upper attachment of a vertical mast 301 of the pole 300, adjacent to an IV bag 202, which is also suspended on the pole 200. For example, the reader 308 may be suspended on an arm at or near the top of the vertical mast, or on an anchor of an attachment to which the fluid container is suspended. Tags 206-a to 206-l are affixed to one side of the bag 202, and the reader 208 and the bag 202 are positioned such that transfer from the reader 208 to the tags 206-a to 206-l occurs through the bag 202 and its contents. In the illustrated example, bag 202 is suspended on an external attachment of bar 300, while reader 202 is suspended on an internal attachment between bar and bag 202 with an electronic tag located on the side of bag opposite the reader.

[0069] As shown in the figure, the reader 208 can be attached to the vertical mast of the pole 300 via a pole mount. In some embodiments, the reader 208 can be integrated into the vertical mast 301. For example, the vertical mast 301 may be configured with the circuitry (including a processor) of the reader 208 embedded therein. In such an embodiment, the radio transmitter (e.g., circuitry) of the reader 208 can be positioned near the top of the vertical mast 301 at a location corresponding to the predicted height of the container 202, such that when the container 202 is attached to the pole 300, the radio transmitter is aligned or substantially aligned with the electronic tags 206-a to 206-l.

[0070] The reader 208 can communicate with the control module 14 or functional modules 116, 118, 120, 122 (e.g., the infusion pump) via a wired (e.g., USB) or wireless (e.g., WiFi, Bluetooth, etc.) connection. In some embodiments, the reader 208 can be connected to a (separate) monitoring device configured to consume and report (e.g., via a display screen) the information provided by the reader 208. The reader 208 can transmit and / or receive power from a source integrated into or with the pole. For example, power and data connection cables can be routed to the pump and / or power outlet via the vertical mast 301. Thus, the reader 208 may include a wired connection to the pump. In some embodiments, the reader may include mounting elements to suspend the reader at a definitive position relative to the drug container atop the infusion pole. In embodiments where the reader 208 is suspended at the top of the pole 300 via mounting elements, an accessory or anchor can provide the power or data connection cable (e.g., which can be fed via the vertical mast).

[0071] Reader 208 may include one or more RF devices, such as one or more transceivers or a combination of one or more transmitters and receivers. In this regard, each RF device may provide an RF transmitting source and an RF receiving source. According to various embodiments, reader 208 may transmit RF signals (via RF transmitting sources) to a plurality of RFID tags 206-a to 206-l disposed on one side of a drug container 202 associated with an infusion device from which medication is administered. The infusion device may be control unit 14 or functional modules 116, 118, 120, 122, such as the described infusion pump. The RFID tags are placed on one side of the drug container opposite the side of the drug container closest to the RF transmitting source, such that the RF signal passes through the drug container before interacting with the RFID tag. Reader 208 then (via RF receiving sources) detects the signal strength of the RF signal returned from the RFID tag.

[0072] According to various implementations, each returned RF signal includes an identifier that identifies the corresponding RFID tag. Reader 208 determines a threshold signal level associated with the fluid within the detected drug container based on at least one of the returned identifiers. For example, the RFID tag may be associated with a specific drug, and reader 208 may use the returned identifiers to look up transport characteristics of the drug fluid. The lookup may be performed using a reader-accessible lookup table (e.g., in the reader's memory), or by the reader querying a remote server or database using the identifiers and obtaining one or more features in response to a query from the server or database.

[0073] The reader 208 then determines the fluid volume within the drug container by comparing the signal strength of each returned RF signal to a determined threshold signal level. In this regard, tags can be placed on the drug container 202 in a predetermined order. For example, each tag can be placed on a material strip in a predetermined order, and this order is maintained in a database (or lookup table). This order can be determined by the reader (or other device that determines the volume based on readings) based on at least one of predetermined identifiers. This order can be used to determine the volume by identifying which of the RFID tags corresponds to a signal indicating the absence of fluid. If there are four tags, and positions one and two indicate the absence of fluid, and tags three and four indicate the presence of fluid, it can be assumed that the fluid is at the level corresponding to tag three (e.g., half-full if tag three is at a position associated with a half-full volume). Therefore, the reader 208 can determine that the first signal strength of the first returned RF signal meets the threshold signal level, while the second signal strength of the second returned RF signal does not meet the threshold signal level, and can then determine the volume of the fluid based on a predetermined placement order of multiple RFID tags and the location of RFID tags that provided returned RF signals with signal strengths that did not meet the threshold signal level within the predetermined order.

[0074] In some embodiments, the reader 208 includes a display screen and provides a representation of the fluid level on the display screen. In some embodiments, the reader 208 provides an electronic indication of the volume to the control unit 14 or a functional module of the device for display by the control unit or functional module.

[0075] Refer to Figure 2 and Figure 3 As a safety precaution, in some implementations, background signals can be received from the IV bag throughout the infusion process. For example, a reference RFID tag associated with the IV bag can be positioned on the IV bag at a sufficient distance from any fluid. As a result, the reference RFID tag on the IV bag always returns a signal (containing information about the identity of the IV bag) during the infusion process, regardless of the fluid level in the IV bag. In this way, the absence of a return signal from a particular RFID tag is not due to the RFID signal 210 failing to reach the RFID tag.

[0076] Various clinicians can use the IV-BVMS system. In some implementations, RFID tags are affixed to IV containers by pharmacists or prescribing physicians. To further improve the performance of the IV-BVMS system, specialized RFID tags can be used. In some implementations, the antenna of the RFID tag is designed to radiate the returned RF signal 212 in a specific direction (e.g., toward the RF reader 208). In this way, the RF reader 208 can detect the small RF signal emitted by the RFID tag.

[0077] The IV-BVMS system is not limited to monitoring the use of a single IV bag at any given time. In some implementations, the system is used to monitor more than one IV container. For example, monitoring the level of secondary fluid from additional intravenous infusion bags. Typically, the IV-BVMS system is capable of simultaneously measuring the fluid levels of multiple IV bags. In some implementations, each bag is associated with a unique reference ID tag number, allowing for the simultaneous measurement of fluid levels from multiple IV bags. For example, clinicians can identify the bags and reference the ID tags to specific pump channels. This subject matter also allows IV bags / medications to be associated with pump channels to reduce association errors.

[0078] In some implementations, processor 50 also calculates the fluid volume in the drug container based on the height of the fluid in the container. Based on the calculation, the IV-BVMS system can provide an indication that the fluid level in the drug container is below a minimum height (e.g., a minimum height associated with the drug container being emptied over a short period of time). For example, when the fluid level in the drug container is below the minimum height, the IV-BVMS can issue an alarm to notify the clinician.

[0079] Figure 4 An example method for determining the fluid volume in a drug container, based on aspects of the art in this subject matter, is described. For illustrative purposes, reference is made to... Figure 1-3 The various blocks of example process 400, as well as the components and / or processes described herein, are described. One or more blocks of process 400 may be implemented, for example, by one or more computing devices. In some embodiments, one or more blocks may be implemented separately from other blocks and may be implemented by one or more different processors or devices. Also for illustrative purposes, the blocks of example process 400 are described as occurring serially or linearly. However, multiple blocks of example process 400 may occur in parallel. Furthermore, the blocks of example process 400 do not need to be executed in the order shown and / or one or more blocks of example process 400 do not need to be executed.

[0080] In the depicted example, drug infusion is initiated from a drug container (402). The drug container includes one or more radio frequency identification (RFID) tags affixed along one side of the drug container. The IV-BVMS system causes an RF signal from an RF source to be directed to one or more RFID tags disposed on the drug container (404). The IV-BVMS system uses an RF reader to detect the signal strength of one or more returned corresponding RF signals from the one or more RFID tags, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags (406). The IV-BVMS system determines a threshold signal level for determining the level of fluid within the drug container based on the one or more identifiers (408). The IV-BVMS system determines whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level (410). Based on the determination that the signal strength of the returned RF signals meets the threshold signal level, the IV-BVMS system provides an indication that the fluid within the drug container is in a first volume (412). Based on the determination that the signal strength does not meet the threshold signal level, the IV-BVMS system provides an indication that the fluid within the drug container is in a second volume (414). In one aspect, a method for determining the volume of fluid in a drug container includes initiating a drug infusion from the drug container. The drug container includes one or more radio frequency identification (RFID) tags adhered along one side of the drug container. The method includes directing a radio frequency (RF) signal from an RF source to the one or more RFID tags disposed on the drug container. The method also includes detecting the signal strength of one or more returned corresponding RF signals from the one or more RFID tags using an RF reader, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags. The method includes determining a threshold signal level for determining the level of fluid within the drug container based on the one or more identifiers, and determining whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level. Based on the determination that the signal strength of the returned RF signals meets the threshold signal level, the method includes providing an indication that the fluid within the drug container is in a first volume; and based on the determination that the signal strength does not meet the threshold signal level, the method includes providing an indication that the fluid within the drug container is in a second volume.

[0081] In some embodiments, the method further includes calculating the fluid volume in the drug container based on signal strength and the number and location of one or more RFID tags on the drug container. In some embodiments, the method further includes generating an alarm when the fluid in the drug container falls below a predetermined minimum volume. In some embodiments, the processor of the server system performs the determination of whether the signal strength of one or more returned corresponding RF signals meets a determined threshold signal level.

[0082] In some embodiments, determining that a returned RF signal does not meet a threshold signal level includes not detecting any returned RF signals from the RFID tag. In some embodiments, the method includes determining the fluid volume in the drug container based on a lookup table storing a correspondence between RFID tag identifiers and corresponding fluid volumes within the drug container. In some embodiments, the method includes identifying the drug in the drug container based on information provided by a corresponding RFID tag adhered to the drug container.

[0083] In some embodiments, guiding the RF signal includes guiding the RF signal through the internal space of the drug container, and one or more RFID tags are disposed on the drug container opposite the internal space. In some embodiments, the drug container includes an IV bag. In some embodiments, the method includes checking the remaining fluid volume in the drug container against a expected infusion volume. In some embodiments, multiple RFID tags are adhered along one side of the drug container, and the method further includes guiding multiple RF signals to the multiple RFID tags and receiving responses from a portion of the multiple RFID tags; and determining the fluid volume within the drug container based on the number of responses received from the RFID tags.

[0084] In some embodiments, the drug container includes a first container and a second container, the first container including one or more first RFID tags and the second container including one or more second RFID tags, the method further including determining the volume of fluid in the first container based on RF signals received from the first RFID tags; and determining the volume of fluid in the second container based on RF signals received from the second RFID tags.

[0085] In some implementations, the RFID tag has dimensions that span more than half the height of the drug container, and the amplitude of the returned RF signal indicates the level of fluid in the drug container.

[0086] In some embodiments, the method includes using a lookup table to convert the amplitude of the returned RF signal into the volume of fluid in the drug container. In some embodiments, the lookup table is obtained by calibrating an RFID tag with a known amount of fluid in the drug container. In some embodiments, a first RFID tag is affixed to the drug container at a location associated with the lowest fluid level in the drug container, below which the drug container is empty. In some embodiments, the method further includes causing a pump connected to the drug container to stop infusion and notifying a clinician when the drug container is empty.

[0087] In some implementations, an RFID tag is affixed to a location on a drug container associated with the drug container becoming empty in less than a predetermined time at a specific drug container flow rate. The method also includes determining that the drug container will become empty in less than a predetermined time based on the strength of the RF signal returned from a first RFID tag and the current flow rate of the infused drug; and generating an alarm indicating that the drug container will become empty in less than a predetermined time.

[0088] In some implementations, the method also includes calculating the volume delivered from the drug container based on a change in the returned RF signal from one or more RFID tags from a signal level below a threshold level to a signal level above a threshold level.

[0089] In some embodiments, the method further includes comparing the delivered volume with the expected infusion volume and issuing an alarm when the difference between the delivered volume and the expected infusion volume is greater than a threshold. In some embodiments, the threshold is selected by the clinician. In some embodiments, the threshold is greater than 5% (e.g., 6%, 7%, 8%, 10%, 15%, etc.). In some embodiments, the threshold is less than 5% (e.g., 4%, 3%, 2%, 1%, 0.5%, etc.). In some embodiments, the threshold is approximately 5% (e.g., between 4.5% and 5.5%). In some embodiments, detecting the returned RF signal from the RFID tag includes periodically detecting the returned RF signal throughout the infusion.

[0090] Many of the methods 400 described above, along with their related features and applications, can also be implemented as a software process specified as a set of instructions recorded on a computer-readable storage medium (also known as a computer-readable medium) and capable of being 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.

[0091] 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.

[0092] 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.

[0093] Figure 5 This is a conceptual diagram illustrating an example electronic system 600 for automatically determining the fluid volume in a drug container, according to aspects of the subject matter technology. The electronic system 500 may be a computing device for executing software associated with one or more parts or steps of the process 500, or... Figures 1-3 The provided components and processes include, but are not limited to, server 130, computing hardware within patient care device 12, or terminal device 132. Electronic system 500 may be representative, in conjunction with... Figures 1-4 The publicly disclosed content. In this regard, electronic system 500 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 bracelet 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.

[0094] Electronic system 500 may include various types of computer-readable media and interfaces for various other types of computer-readable media. In the depicted example, electronic system 500 includes a bus 508, one or more processing units 512, system memory 504, read-only memory (ROM) 510, permanent storage device 502, input device interface 514, output device interface 506, and one or more network interfaces 516. In some embodiments, electronic system 500 may include or be integrated with other computing devices or circuitry for operating the various components and processes described above.

[0095] Bus 508 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of electronic system 500. For example, bus 508 communicatively connects one or more processing units 512 to ROM 510, system memory 504, and permanent storage device 502.

[0096] From these various memory units, one or more processing units 512 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.

[0097] ROM 510 stores static data and instructions required by one or more processing units 512 and other modules of the electronic system. On the other hand, permanent storage device 502 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 500 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 502.

[0098] Other embodiments use removable storage devices (such as floppy disks, flash drives, and their corresponding disk drives) as permanent storage device 502. Like permanent storage device 502, system memory 504 is a read-write memory device. However, unlike storage device 502, system memory 504 is volatile read-write memory, such as random access memory. System memory 504 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 504, permanent storage device 502, and / or ROM 510. From these various memory units, one or more processing units 512 retrieve instructions to be executed and data to be processed in order to perform the processes of some embodiments.

[0099] Bus 508 is also connected to input and output device interfaces 514 and 506. Input device interface 514 enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface 514 include, for example, alphanumeric keypads and pointing devices (also referred to as "cursor control devices"). Output device interface 506 enables, for example, the display of images generated by electronic system 500. Output devices used with output device interface 506 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.

[0100] In addition, such as Figure 5 As shown, bus 508 also couples electronic system 500 to a network (not shown) via network interface 516. Network interface 516 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 516 may also include hardware (e.g., Ethernet hardware) for connecting a 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 500 may be used in conjunction with the disclosure of this subject matter.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] Examples of the subjects described in this specification can be implemented in a computing system that includes back-end components, such as a data server, or middleware components, such as an application server, or front-end components, such as a client computer with a graphical user interface or a web browser through which a user can interact with embodiments of the subjects 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).

[0107] 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.

[0108] 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.

[0109] 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 appended method claims present the elements of each step in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0110] It should be understood that the specific order or hierarchy of steps in the disclosed process is illustrative of the example method. Based on design preferences, it is understood that the specific order or hierarchy of steps in the process can be rearranged. Some of these 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 presented specific order or hierarchy.

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

[0112] Clause 1. A monitoring device for monitoring the volume of a drug container, comprising: one or more radio frequency (RF) devices providing an RF transmitting source and an RF receiving source; one or more processors; and a non-transitory memory device having instructions thereon, which, when executed by the one or more processors, cause the monitoring device to perform operations including: transmitting an RF signal via the RF transmitting source toward a plurality of RF identification (RFID) tags disposed on one side of a drug container associated with an infusion device from which a drug is administered, wherein said side of the drug container is opposite to the side of the drug container closest to the RF transmitting source, such that the RF signal passes through the drug container before interacting with the RFID tags; detecting the signal strength of returned RF signals from the RFID tags via the RF receiving source, each of the returned RF signals including an identifier identifying the corresponding RFID tag; determining a threshold signal level associated with detecting fluid within the drug container based on at least one of the returned identifiers; determining the volume of fluid within the drug container based on comparing the signal strength of each returned RF signal with the determined threshold signal level; and providing an electronic indication of the volume.

[0113] Clause 2. The monitoring device according to Clause 1, wherein determining the volume of the fluid comprises: determining that a first signal strength of a first returned RF signal meets a threshold signal level, while a second returned RF signal does not meet the threshold signal level; determining a predetermined placement order of first and second RFID tags based on at least one of the returned identifiers; and determining the volume of the fluid based on a predetermined placement order of a plurality of RFID tags and the position of an RFID tag within the predetermined order that provides a returned RF signal with a signal strength that does not meet the threshold signal level.

[0114] Clause 3. The monitoring device according to Clause 1, wherein providing the electronic indication of the volume includes: providing an electronic indication to the infusion device for display at the infusion device.

[0115] Clause 4. The monitoring device according to Clause 1 further includes: a display screen, wherein operation further includes: displaying a representation of the electronic indication on the display screen.

[0116] Clause 5. A method for determining the volume of fluid in a drug container, comprising: initiating a drug infusion from the drug container, wherein the drug container includes one or more radio frequency identification (RFID) tags adhered along one side of the drug container; directing a radio frequency (RF) signal from an RF source to the one or more RFID tags disposed on the drug container; detecting the signal strength of one or more returned corresponding RF signals from the one or more RFID tags using an RF reader, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags; determining a threshold signal level for determining the level of fluid within the drug container based on the one or more identifiers; determining whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level; providing an indication that the fluid within the drug container is in a first volume based on the determination that the signal strength of the returned RF signals meets the threshold signal level; and providing an indication that the fluid within the drug container is in a second volume based on the determination that the signal strength does not meet the threshold signal level.

[0117] Clause 6. The method described in Clause 5 further includes: calculating the fluid volume in the drug container based on signal strength and the number and location of one or more RFID tags on the drug container.

[0118] Clause 7. The method described in Clause 5 further includes: generating an alarm when the fluid in the drug container falls below a predetermined minimum volume.

[0119] Clause 8. The method according to Clause 5, wherein determining whether the signal strength of one or more returned corresponding RF signals meets the determined threshold signal level is performed by the processor of the server system.

[0120] Clause 9. The method described in Clause 5, wherein determining that a returned RF signal does not meet a threshold signal level includes not detecting any returned RF signal from the RFID tag.

[0121] Clause 10. The method described in Clause 5 further includes determining the volume of fluid in the drug container based on a lookup table that stores a correspondence between RFID tag identifiers and corresponding volumes of fluid within the drug container.

[0122] Clause 11. The method described in Clause 5 further includes identifying the drug in the drug container based on information provided by a corresponding RFID tag affixed to the drug container.

[0123] Clause 12. The method according to Clause 5, wherein guiding the RF signal comprises: guiding the RF signal through the internal space of the drug container, and one or more RFID tags being disposed on the drug container opposite the internal space.

[0124] Clause 13. The method described in Clause 5, wherein the drug container includes an IV bag.

[0125] Clause 14. The method described in Clause 5 further includes: checking the remaining fluid volume in the drug container against the expected infusion volume.

[0126] Clause 15. The method according to Clause 5, wherein a plurality of RFID tags are affixed along one side of a drug container, the method further comprising: directing a plurality of RF signals to the plurality of RFID tags and receiving responses from a portion of the plurality of RFID tags; and determining the fluid volume within the drug container based on the number of responses received from the RFID tags.

[0127] Clause 16. The method according to Clause 5, wherein the drug container includes a first container and a second container, the first container including one or more first RFID tags, and the second container including one or more second RFID tags, the method further comprising: determining the fluid volume in the first container based on RF signals received from the first RFID tags; and determining the fluid volume in the second container based on RF signals received from the second RFID tags.

[0128] Clause 17, the method according to Clause 16, wherein the RFID tag has dimensions spanning more than half the height of the drug container, and the amplitude of the returned RF signal indicates the level of fluid in the drug container.

[0129] Clause 18. The method described in Clause 5 further includes using a lookup table to convert the amplitude of the returned RF signal into the fluid volume in the drug container.

[0130] Clause 19. The method according to Clause 18, wherein the lookup table is obtained by calibrating the RFID tag with a known amount of fluid in the drug container.

[0131] Clause 20. The method according to Clause 5, wherein a first RFID tag is affixed to the drug container at a location associated with the lowest fluid level in the drug container, below which the drug container is empty.

[0132] Clause 21. The method described in Clause 20 further includes, when the drug container is empty, causing the pump connected to the drug container to stop infusion and transmitting a notification to the clinician device.

[0133] Clause 22. The method according to Clause 5, wherein a first RFID tag is affixed to a location on the drug container associated with the drug container becoming empty in less than a predetermined time at a specific flow rate of the drug container, the method further comprising: determining, based on the strength of the RF signal returned from the first RFID tag and the current flow rate of the infused drug, that the drug container will become empty in less than a predetermined time; and generating an alarm indicating that the drug container will become empty in less than a predetermined time.

[0134] Clause 23. The method according to Clause 5 further includes calculating the volume delivered from the drug container based on a change in the returned RF signal from one or more RFID tags from a signal level below a threshold signal level to a signal level above a threshold signal level.

[0135] Clause 24. The method described in Clause 23 further includes comparing the delivered volume with the expected infusion volume and issuing an alarm when the difference between the delivered volume and the expected infusion volume is greater than a threshold.

[0136] Clause 25. The method according to Clause 5, wherein detecting the returned RF signal from the RFID tag includes periodically detecting the returned RF signal throughout the infusion.

[0137] Clause 26. A non-transitory machine-readable storage medium embodying instructions that, when executed by a machine, allow the machine to perform a method for determining the volume of fluid in a drug container according to any one of Clauses 5-26.

[0138] Clause 27. A system comprising: 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 one of the methods of Clauses 5-26.

[0139] Clause 28. A non-transitory machine-readable storage medium containing instructions that, when executed by a machine, allow the machine to perform a method for determining the volume of fluid in a drug container, the method comprising: initiating drug infusion from the drug container, wherein the drug container includes one or more radio frequency identification (RFID) tags adhered along one side of the drug container; directing a radio frequency (RF) signal from an RF source to the one or more RFID tags disposed on the drug container; detecting, using an RF reader, the signal strength of one or more returned corresponding RF signals from the one or more RFID tags, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags; determining, based on the one or more identifiers, a threshold signal level for determining the level of fluid within the drug container; determining whether the signal strength of the one or more returned corresponding RF signals satisfies the determined threshold signal level; providing an indication that the fluid within the drug container is in a first volume based on the determination that the signal strength of the returned RF signals satisfies the threshold signal level; and providing an indication that the fluid within the drug container is in a second volume based on the determination that the signal strength does not satisfy the threshold signal level.

[0140] Clause 29. A system comprising: 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: initiate drug infusion from a drug container, wherein the drug container includes one or more radio frequency identification (RFID) tags adhered along one side of the drug container; direct radio frequency (RF) signals from an RF source to the one or more RFID tags disposed on the drug container; detect the signal strength of one or more returned corresponding RF signals from the one or more RFID tags using an RF reader, the returned one or more RF signals including one or more identifiers for identifying the one or more RFID tags; determine a threshold signal level based on the one or more identifiers for determining the level of fluid within the drug container; determine whether the signal strength of the one or more returned corresponding RF signals meets the determined threshold signal level; provide an indication that the fluid within the drug container is in a first volume based on the determination that the signal strength of the returned RF signals meets the threshold signal level; and provide an indication that the fluid within the drug container is in a second volume based on the determination that the signal strength does not meet the threshold signal level.

[0141] Clause 30. The system described in Clause 29, wherein the RFID tag includes an antenna structure that radiates RF signals toward an RF reader in a specific direction.

[0142] 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.

[0143] Further consideration:

[0144] 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 appended method claims present the elements of each step in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0145] 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.

[0146] 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."

[0147] 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.

[0148] 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. A monitoring device for monitoring the volume of a drug container, comprising: One or more radio frequency (RF) devices that provide RF transmitting and RF receiving sources; One or more processors; as well as A non-transitory memory device having instructions thereon, which, when executed by the one or more processors, cause the monitoring device to perform operations including the following steps: An RF signal is transmitted via the RF transmitter toward a series of RF identification (RFID) tags aligned in a predetermined order and vertically attached to one side of the drug container associated with an infusion device from which the drug is administered, wherein the side of the drug container is opposite the side of the drug container closest to the RF transmitter, such that the RF signal passes through the drug container before interacting with the series of RFID tags. The signal strength of the returned RF signals from the series of RFID tags is detected via the RF receiving source, each of the returned RF signals including an identifier of the corresponding RFID tag that identifies the series of RFID tags; Based on at least one of the returned identifiers, a threshold signal level associated with detecting fluid within the drug container is determined; The volume of fluid in the drug container is determined based on a predetermined order of the series of RFID tags. A first returned RF signal associated with a first RFID tag in the series of RFID tags is determined to meet the threshold signal level, indicating that there is no fluid in the drug container at the height of the first RFID tag. When it is determined that a second RF signal associated with a second RFID tag in the series of RFID tags is not detected or does not meet the threshold signal level, it indicates that there is fluid in the drug container at the height of the second RFID tag. as well as Based on the first returned RF signal satisfying the threshold signal, and the second RF signal not being detected or not satisfying the threshold signal level, and based on the corresponding heights of the first RFID tag and the second RFID tag on the drug container, the volume of fluid inside the drug container is determined; Provides an electronic indication of the volume.

2. The monitoring device according to claim 1, wherein, Determining the volume of the fluid includes: The volume of the fluid is determined based on the first position of the first RFID tag in a predetermined placement sequence and the second position of the second RFID tag in the predetermined placement sequence.

3. The monitoring device according to claim 1, wherein, The electronic indication providing the volume includes: The electronic indicator is provided to the infusion device for display at the infusion device.

4. The monitoring device according to claim 1 further includes: Display screen The operation also includes: The electronic indication is displayed on the screen.

5. A method for determining the volume of fluid in a drug container, comprising: Infusion of a drug is initiated from the drug container, wherein the drug container includes a series of radio frequency identification (RFID) tags aligned with each other in a predetermined order and attached along one side of the drug container; Radio frequency (RF) signals are directed from an RF source to the series of RFID tags attached to the drug container; The signal strength of the corresponding RF signal returned from the series of RFID tags is detected using an RF reader, the returned RF signal including one or more identifiers for identifying the series of RFID tags; A threshold signal level for determining the fluid level within the drug container is determined based on the one or more identifiers; Determine whether the signal strength of a first returned RF signal associated with a first RFID tag in one or more of the first RFID tags meets a determined threshold signal level, indicating that there is no fluid in the drug container at the height of the first RFID tag; and when it is determined that a second RF signal associated with a second RFID tag in the series of RFID tags is not detected or does not meet the threshold signal level, indicate that there is fluid in the drug container at the height of the second RFID tag. as well as Based on the first returned RF signal satisfying the threshold signal, while the second RF signal is not detected or does not satisfy the threshold signal level, and based on the corresponding heights of the first RFID tag and the second RFID tag on the drug container, the fluid volume inside the drug container is determined.

6. The method according to claim 5, further comprising: The fluid volume in the drug container is calculated based on the signal strength and the number and location of the series of RFID tags on the drug container.

7. The method according to claim 5, further comprising: An alarm is generated when the fluid in the drug container falls below a predetermined minimum volume.

8. The method according to claim 5, wherein, The formation of the series of RFID tags into a continuous RFID tag strip, and the determination of whether the signal strength of each of the returned corresponding RF signals meets the determined threshold signal level, are performed by the processor of the server system.

9. The method according to claim 5, wherein, Determining that a second returned RF signal does not meet the threshold signal level includes not detecting any returned RF signals from the RFID tag.

10. The method of claim 5, further comprising determining the volume of fluid in the drug container based on a lookup table storing a correspondence between RFID tag identifiers of the series of RFID tags and corresponding volumes of fluid within the drug container.

11. The method of claim 5, further comprising identifying the drug in the drug container based on information provided by a corresponding RFID tag adhered to the drug container.

12. The method according to claim 5, wherein, Guiding the RF signal includes guiding the RF signal through the internal space of the drug container, and the series of RFID tags are disposed on the drug container opposite the internal space.

13. The method of claim 5, further comprising: Check the remaining fluid volume in the drug container against the expected infusion volume.

14. The method according to claim 5, wherein, The method further includes: Directing multiple RF signals to the series of RFID tags and receiving responses from a portion of the series of RFID tags; and The fluid volume within the drug container is determined based on the number of responses received from the RFID tag.

15. The method of claim 5, further comprising using a lookup table to convert the amplitude of the corresponding returned RF signal into the fluid volume in the drug container.

16. The method according to claim 5, wherein, The first RFID tag is affixed to the drug container at a location associated with the lowest fluid level in the drug container, below which the drug container is empty.

17. The method of claim 16, further comprising, when the drug container is empty, causing the pump connected to the drug container to stop infusion and transmitting a notification to the clinician device.

18. The method according to claim 5, wherein, The first RFID tag is affixed to a location on the drug container associated with the drug container becoming empty in less than a predetermined time at a specific flow rate of the drug container, and the method further includes: Based on the strength of the first RF signal returned from the first RFID tag and the current flow rate of the drug infusion, it is determined that the drug container will become empty in less than the predetermined time; and An alarm is generated indicating that the drug container will become empty in less than the predetermined time.

19. The method of claim 5, further comprising calculating the volume delivered from the drug container based on a change in the returned RF signal from at least one of the series of RFID tags from a signal below the threshold signal level to a signal above the threshold signal level.

20. The method of claim 19, further comprising comparing the delivered volume with the expected infusion volume and issuing an alarm when the difference between the delivered volume and the expected infusion volume is greater than a threshold.

Images