Medical device with radio frequency identification component

Abstract

A system may include a medical device; a radio frequency identification (RFID) tear tag attached to the medical device wherein the RFID tear tag comprises an RFID circuit and an electronic component electrically connected to the RFID circuit wherein the electronic component comprises a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable wherein the first portion and the second portion are configured to be separable, the first portion and the second portion of the electronic component are electrically coupled when the electronic component is in a first state, and the RFID circuit is configured to provide a first signal, and wherein the first portion and the second portion of the electronic component are not electrically coupled when the electronic component is in a second state, and the RFID circuit is configured to provide a second signal.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 409,946, filed on September 26, 2022, entitled “Medical Device with Radio Frequency Identification Component,” the entire disclosure of which is incorporated herein by reference in its entirety. Background Art

[0003] Radio frequency identification (RFID) may refer to a technology that uses electromagnetic fields to automatically identify and track devices (e.g., RFID tags) that can be attached to objects. An RFID tag may consist of a radio transponder, a radio receiver, and a transmitter. When an RFID tag is triggered by an electromagnetic interrogation pulse from a nearby RFID reader device, the RFID tag may send a signal including data (which is typically an inventory identification number) back to the RFID reader device. In some cases, the inventory identification number may be used to track the goods.

[0004] RFID tags can include passive RFID tags and active RFID tags. Passive RFID tags can be powered by electromagnetic energy from electromagnetic waves emitted by an RFID reader device to interrogate the RFID tag. Active RFID tags can be powered by a power source included in the active RFID tag, so the active RFID tag can be read by an RFID reader device at a larger range (e.g., up to hundreds of meters).

[0005] In some cases, RFID tags have been associated with medical devices to identify the medical device and / or a drug included in the medical device. For example, an RFID tag may be included in the packaging of the medical device, and when the RFID tag is interrogated by an RFID reader device, the RFID tag may provide a signal including an identifier of the medical device and / or a drug included in the medical device.

[0006] However, RFID tags may not provide accurate information about the use of medical devices. For example, a user (e.g., a doctor) may read an RFID tag on the packaging of a medical device when the packaging is removed from the medical device. In this case, the doctor may not administer medication from the medical device when the packaging is removed, and therefore, the information read from the RFID tag on the packaging about when the medical device was used may be inaccurate. In addition, after the packaging is removed, the medical device may no longer be used. Summary of the invention

[0007] Accordingly, improved systems, devices, products, apparatus and / or methods are provided for determining characteristics of a medical device using radio frequency identification (RFID).

[0008] In one embodiment, a system includes: a medical device; a radio frequency identification (RFID) tear tag, the RFID tear tag attached to the medical device, wherein the RFID tear tag includes an RFID circuit and an electronic component, the electronic component is electrically connected to the RFID circuit, wherein the electronic component includes a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable. When the electronic component is in a first state, the first portion and the second portion of the electronic component are electrically coupled, and the RFID circuit is configured to provide a first signal. When the electronic component is in a second state, the first portion and the second portion of the electronic component are not electrically coupled, and the RFID circuit is configured to provide a second signal.

[0009] According to an embodiment of the present invention, when the first portion and the second portion of the electronic component are electrically coupled, the first portion and the second portion of the electronic component are conductively coupled.

[0010] According to an embodiment of the invention, the electronic component comprises an electrical conductor.

[0011] According to an embodiment of the invention, the electrical conductor comprises an electrically conductive trace.

[0012] According to an embodiment of the present invention, the system further comprises a base component, wherein the RFID circuit and the electronic component are positioned on the base component.

[0013] According to an embodiment of the invention, the base component comprises a perforation, and wherein the first part and the second part are configured to be separable based on the perforation of the base component.

[0014] According to an embodiment of the present invention, the first part and the second part are coupled together when the electronic component is in the first state, and wherein the first part and the second part cannot be recoupled when the electronic component is in the second state.

[0015] According to an embodiment of the invention, the first part and the second part are configured to be separable independently of additional mechanical components.

[0016] According to an embodiment of the present invention, the electronic component is a first electronic component, and the system further comprises a second electronic component, the second electronic component being electrically connected to the RFID circuit, wherein the second electronic component comprises an additional first portion and an additional second portion, and wherein the additional first portion of the second electronic component and the additional second portion of the second electronic component are configured to be separable, wherein the additional first portion is separated from the additional second portion, and the RFID circuit is configured to provide a third signal, wherein the third signal is different from the first signal and the second signal.

[0017] According to an embodiment of the present invention, when the electronic component is in the first state, the RFID circuit is configured to provide the first signal during interrogation by an RFID reader device.

[0018] According to an embodiment of the present invention, when the electronic component is in the second state, the RFID circuit is configured to provide the second signal during interrogation by an RFID reader device, wherein the second signal is different from the first signal.

[0019] According to an embodiment of the present invention, the medical device comprises a disposable medical device.

[0020] According to an embodiment of the present invention, a medical device assembly includes: a container having a closure; a radio frequency identification (RFID) circuit; and an electronic component electrically connected to the RFID circuit. The electronic component includes a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable. The RFID circuit and the electronic component are positioned on the container, and when the electronic component is in a first state, the first portion and the second portion of the electronic component are electrically coupled, and the RFID circuit is configured to provide a first signal during interrogation by an RFID reader device. When the electronic component is in a second state, the first portion and the second portion of the electronic component are not electrically coupled, and the RFID circuit is configured to provide a second signal during interrogation by an RFID reader device, wherein the second signal is different from the first signal.

[0021] According to an embodiment of the present invention, when the first portion and the second portion of the electronic component are electrically coupled, the first portion and the second portion of the electronic component are conductively coupled.

[0022] According to an embodiment of the invention, the electronic component comprises an electrical conductor.

[0023] According to an embodiment of the invention, the electrical conductor comprises an electrically conductive trace.

[0024] According to an embodiment of the present invention, the medical device further comprises a base component, wherein the RFID circuit and the electronic component are positioned on the base component, and wherein the base component is positioned on the closure of the container.

[0025] According to an embodiment of the invention, the base component comprises a perforation, and wherein the first part and the second part are configured to be separable based on the perforation of the base component.

[0026] According to an embodiment of the invention, the first part and the second part of the electronic component are configured to be destructively disconnected when the electronic component is in the second state.

[0027] According to an embodiment of the invention, the first part and the second part are configured to be separable independently of additional mechanical components.

[0028] According to an embodiment of the present invention, the electronic component is a first electronic component, and the medical device assembly further comprises a second electronic component electrically connected to the RFID circuit. The second electronic component comprises an additional first portion and an additional second portion, and wherein the additional first portion of the second electronic component and the additional second portion of the second electronic component are configured to be separable. The additional first portion is separated from the additional second portion, and the RFID circuit is configured to provide a third signal, wherein the third signal is different from the first signal and the second signal.

[0029] According to an embodiment of the invention, the container is a disposable container. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Additional advantages and details are explained in more detail below with reference to an exemplary embodiment shown in the attached schematic drawings, in which:

[0031] Figure 1 is a schematic diagram of a non-limiting aspect or embodiment of a system for determining a characteristic of a medical device using a radio frequency identification (RFID) tag;

[0032] Figure 2 yes Figure 1 Schematic diagrams of non-limiting aspects or embodiments of one or more devices and / or components of one or more systems;

[0033] Figure 3 is a flow chart of a non-limiting aspect or embodiment of a process for determining a characteristic of a medical device using an RFID tag;

[0034] Figure 4A and Figure 4B is a schematic diagram of a non-limiting embodiment of an RFID tear tag;

[0035] Figure 5 is a schematic diagram of a non-limiting embodiment of an RFID tear tag;

[0036] Figure 6 is a schematic diagram of a non-limiting embodiment of a medical device assembly including an RFID tear tag attached to a container;

[0037] Figure 7 is a schematic diagram of a non-limiting embodiment of a medical device assembly including an RFID tear tag attached to a syringe;

[0038] Figure 8 is a schematic diagram of a non-limiting embodiment of a medical device assembly including an RFID tear tag attached to an intravenous (IV) assembly;

[0039] Fig. 9 is a schematic diagram of a non-limiting embodiment of a medical device assembly including an RFID tear tag attached to a medication package; and

[0040] Fig.10 is a schematic diagram of a non-limiting embodiment of the location of an RFID reader device. DETAILED DESCRIPTION

[0041] It should be understood that, unless expressly stated otherwise, the present disclosure may make various alternative variations and various step sequences. It should also be understood that the specific devices and processes shown in the accompanying drawings and described in the following specification are merely exemplary, non-limiting embodiments. Therefore, the specific dimensions and other physical characteristics associated with the embodiments disclosed herein should not be considered limiting.

[0042] For the purpose of description hereinafter, the terms "end", "upper", "lower", "right", "left", "vertical", "horizontal", "top", "bottom", "lateral", "longitudinal" and their derivatives shall relate to embodiments or aspects as oriented in the accompanying drawings. However, it will be understood that various alternative variations and various step orders may be made to the embodiments or aspects unless expressly stated to the contrary. It should also be understood that the specific devices and processes shown in the drawings and described in the following specification are merely non-limiting exemplary embodiments or aspects. Therefore, unless otherwise indicated, specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments or aspects disclosed herein should not be considered limiting.

[0043] Unless explicitly described, the aspects, parts, elements, structures, actions, steps, functions and / or instructions used herein, etc., should not be interpreted as critical or necessary. In addition, as used herein, the article "a, an" is intended to include one or more items, and can be used interchangeably with "one or more" and "at least one". For example, unless the context clearly indicates otherwise, as used in the specification and claims, the singular "one" and "the" include plural indicators. Additionally, in addition, as used herein, the terms "set" and "group" are intended to include one or more items (for example, related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more" or "at least one". In the case of only one item, the term "one (one)" or similar language is used. In addition, as used herein, the terms "have", "have" or "with" etc. are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part". In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part". Additionally, the phrase "based on" may mean "in response to," and indicate a condition for automatically triggering a specified operation of an electronic device (eg, controller, processor, computing device, etc.) as appropriately referred to herein.

[0044] As used herein, the terms "communication" and "transmission" may refer to the reception, collection, transmission, transmission and / or provision of information (e.g., data, signals, messages, instructions and / or commands, etc.). A unit (e.g., a device, a system, or a component of a device or system and / or a combination thereof, etc.) communicating with another unit means that the unit is able to directly or indirectly receive information from the other unit and / or send information to the other unit. This may refer to a direct or indirect connection that is essentially wired and / or wireless. In addition, even if the information transmitted between the first unit and the second unit can be modified, processed, relayed and / or routed, the two units can also communicate with each other. For example, even if the first unit passively receives information and does not actively send information to the second unit, the first unit can communicate with the second unit. As another example, if at least one intermediate unit (e.g., a third unit located between the first unit and the second unit) processes the information received from the first unit and transmits the processed information to the second unit, the first unit can communicate with the second unit. In some non-limiting embodiments, a message may refer to a network packet (e.g., a data packet, etc.) including data. It will be appreciated that many other arrangements are possible.

[0045] It will be apparent that the systems and / or methods described herein can be implemented in different forms such as hardware, software, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to these implementation forms. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it should be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0046] Some non-limiting embodiments are described herein in conjunction with threshold values. As used herein, satisfying a threshold value may refer to a value being greater than a threshold value, more than a threshold value, above a threshold value, greater than or equal to a threshold value, less than a threshold value, less than a threshold value, below a threshold value, less than or equal to a threshold value, equal to a threshold value, etc.

[0047] Improved devices, systems, methods, and products for accurately identifying characteristics of medical devices (e.g., disposable medical devices) are provided. Embodiments of the present disclosure may include a device comprising a medical device and a radio frequency identification (RFID) tear tag attached to the medical device, wherein the RFID tear tag comprises an RFID circuit and an electronic component electrically connected to the RFID circuit, wherein the electronic component comprises a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable. In some non-limiting embodiments, when the electronic component is in a first state, the first portion and the second portion of the electronic component are electrically coupled, and the RFID circuit is configured to provide a first signal during interrogation by an RFID reader device, and when the electronic component is in a second state, the first portion and the second portion of the electronic component are not electrically coupled, and the RFID circuit is configured to provide a second signal during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal is different from the first signal.

[0048] In some non-limiting embodiments, when the first and second parts of the electronic component are electrically coupled, the first and second parts of the electronic component are conductively coupled. In some non-limiting embodiments, the electronic component includes an electrical conductor, which may include a conductive trace. In some non-limiting embodiments, the device also includes a base component, and the RFID circuit and the electronic component are positioned on the base component. In some non-limiting embodiments, the base component includes a perforation, wherein the first and second parts are configured to be separable based on the perforation of the base component. In some non-limiting embodiments, the first and second parts of the electronic component are configured to be destructively disconnected when the electronic component is in the second state. In some non-limiting embodiments, the first and second parts are configured to be separable independently of the additional mechanical parts. In some non-limiting embodiments, the above-mentioned electronic component is a first electronic component, and the device also includes a second electronic component electrically connected to the RFID circuit, wherein the second electronic component includes a first part and a second part, and wherein the first part of the second electronic component and the second part of the second electronic component are configured to be separable.

[0049] In this way, embodiments of the present disclosure provide an RFID tag that can provide accurate information about the use of a medical device. For example, when removing a package from a medical device, a user can receive information from an RFID tag on the package of the medical device. In addition, a user can read an RFID tag positioned on the medical device that will provide information about when the medical device was used. In this way, reading an RFID tag from the package can provide accurate information about when the medical device was removed from the package and / or when the medical device was used.

[0050] Reference now Figure 1 , Figure 1 1 is a schematic diagram of an example environment 100 in which the devices, systems, methods, and / or products described herein may be implemented. Figure 1 As shown, environment 100 includes a medical device management system 102, a radio frequency identification (RFID) reader device 104, and RFID tags 106-1 to RFID tags 106-n (these tags may be collectively referred to as RFID tags 106 and individually referred to as RFID tags 106 where appropriate). Medical device management system 102 and RFID reader device 104 may be interconnected (e.g., establish a connection for communication, etc.) via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection.

[0051] The medical device management system 102 may include one or more devices configured to communicate with the RFID reader device 104 via the communication network 108. For example, the medical device management system 102 may include a server (e.g., a cloud server), a group of servers, a computing device, such as a mobile device (e.g., a smartphone), a tablet computer, a laptop computer, and / or a desktop computer, etc. In some non-limiting embodiments, the medical device management system 102 may be configured to communicate with the RFID reader device 104 via a direct communication connection (e.g., a communication connection independent of a communication network such as the communication network 108), such as a short-range wireless communication connection (e.g., a near-field communication (NFC) communication connection, an RFID communication connection, The medical device management system 102 may be configured to determine the characteristics of the medical device based on the data received from the RFID reader device 104. In some non-limiting embodiments, the medical device management system 102 may be a component of the RFID reader device 104.

[0052] The RFID reader device 104 may include one or more devices configured to communicate with the RFID tag 106. For example, the RFID reader device 104 may include one or more RFID readers (e.g., devices including a radio frequency (RF) transmitter and an RF receiver that are capable of reading RFID tags and / or writing information to RFID tags). In some non-limiting embodiments, the RFID reader device 104 may include one or more devices configured to communicate with the medical device management system 102 via the communication network 108. For example, the RFID reader device 104 may include a computing device, such as a mobile device (e.g., a smartphone, a wearable device such as a bracelet, etc.), a tablet computer, a laptop computer, and / or a desktop computer, etc. In some non-limiting embodiments, the RFID reader device 104 may be configured to communicate with the medical device management system 102 via a direct communication connection (e.g., a communication connection independent of a communication network such as the communication network 108), such as a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, communication connection, infrared communication connection, etc.) or a wired communication connection (for example, a connection using a cable and a universal serial bus (USB) communication protocol).

[0053] The RFID tag 106 may include one or more RFID tags configured to provide a signal in response to an interrogation signal from an RFID reader (e.g., the RFID reader device 104). In some non-limiting embodiments, the RFID tag 106 may include a passive RFID tag or an active RFID tag. In some non-limiting embodiments, the RFID tag 106 may include an RFID tear tag as described herein.

[0054] The communication network 108 may include one or more wired networks and / or wireless networks. For example, the communication network 108 may include a cellular network (e.g., a long-term evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a fifth generation (5G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, an internet, a fiber-based network, and / or a cloud computing network, etc., and / or any combination of some or all of these or other types of networks.

[0055] Figure 1 The number and arrangement of systems and / or devices shown in are provided as examples. Figure 1 There may be additional systems and / or devices, fewer systems and / or devices, different systems and / or devices, or differently configured systems and / or devices compared to those systems and / or devices shown in . Figure 1 Two or more systems and / or devices shown in the drawings may be implemented in a single system or a single device, or Figure 1 A single system or a single device shown in the environment 100 may be implemented as multiple distributed systems or devices. Additionally or alternatively, a group of systems or a group of devices (e.g., one or more systems, one or more devices) of the environment 100 may perform one or more functions described as being performed by another group of systems or another group of devices of the environment 100.

[0056] Reference now Figure 2 , Figure 2 2 is a schematic diagram of example components of device 200. Device 200 may correspond to medical device management system 102 (one or more devices of medical device management system 102) and / or RFID reader device 104. In some non-limiting embodiments, medical device management system 102 and / or RFID reader device 104 may include at least one device 200 or at least one component of device 200. Figure 2 As shown, device 200 may include a bus 202 , a processor 204 , a memory 206 , a storage component 208 , an input component 210 , an output component 212 , and a communication interface 214 .

[0057] The bus 202 may include components that allow communication between the components of the device 200. In some non-limiting embodiments, the processor 204 may be implemented in hardware, software, or a combination of hardware and software. For example, the processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.). The memory 206 may include a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the processor 204.

[0058] The storage component 208 may store information and / or software related to the operation and use of the device 200. For example, the storage component 208 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, a solid-state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of computer-readable medium and a corresponding drive.

[0059] Input components 210 may include components that allow device 200 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, a microphone, a camera, etc.). Additionally or alternatively, input components 210 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output components 212 may include components that provide output information from device 200 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

[0060] The communication interface 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables the device 200 to communicate with other devices, for example, via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection. The communication interface 214 may allow the device 200 to receive information from another device and / or provide information to another device. For example, the communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, interface and / or cellular network interface, etc.

[0061] The device 200 can perform one or more processes described herein. The device 200 can perform these processes based on the processor 204 executing software instructions, which are stored by a computer-readable medium (e.g., memory 206 and / or storage component 208). Computer-readable media (e.g., non-transitory computer-readable media) are defined herein as non-transitory storage devices. Non-transitory storage devices include storage space located inside a single physical storage device or storage space distributed across multiple physical storage devices.

[0062] The software instructions may be read into the memory 206 and / or storage component 208 from another computer-readable medium or from another device via the communication interface 214. The software instructions stored in the memory 206 and / or storage component 208, when executed, may cause the processor 204 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.

[0063] The memory 206 and / or storage component 208 may include a data storage device or one or more data structures (e.g., a database, etc.). The device 200 can receive information from, store information in, transmit information to, or search for information stored in the data storage device or data structure in the memory 206 and / or storage component 208. For example, the information may include data associated with a real-time mobile device application profile, data associated with a historical mobile device application profile, input data, output data, transaction data, account data, or any combination thereof.

[0064] Figure 2 The number and arrangement of components shown in are provided as examples. In some non-limiting embodiments, Figure 2 Device 200 may include additional components, fewer components, different components, or differently arranged components than those shown in . Additionally or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.

[0065] Reference now Figure 3 , Figure 3 300. In some non-limiting embodiments, one or more functions described with respect to process 300 may be performed (e.g., completely, partially, etc.) by medical device management system 102. In some non-limiting embodiments, one or more steps of process 300 may be performed (e.g., completely and / or partially, etc.) by another device or another group of devices separate from medical device management system 102, such as RFID reader device 104.

[0066] like Figure 3 As shown, at step 302, process 300 may include: receiving first data associated with a first radio frequency identification (RFID) tag attached to a medical device. For example, the medical device management system 102 may receive (e.g., receive in real time) first data associated with an RFID tag 106-1 attached (e.g., applied, adhered, stuck, etc.) to a surface of a medical device (e.g., a container, a syringe, a catheter, etc.).

[0067] In some non-limiting embodiments, the data associated with the RFID tag 106 (e.g., first data associated with the RFID tag 106-1, second data associated with the RFID tag 106-2, additional data associated with the RFID tag 106-n, etc.) may include data associated with the identification of the individual on whom the medical device is to be used, data associated with the substance (e.g., a drug, medicament, medicine, etc.) used to fill the medical device (e.g., the type of substance), data associated with the amount of the substance used to fill the medical device, data associated with the time when the medical device was filled with the substance, data associated with the time when the medical device was placed (e.g., initially placed, replaced, etc.) in a package (e.g., a sterile package), data associated with the time when the medical device was removed from the package, and data associated with the time when the medical device was removed from the package. data associated with the medical device being placed in an activated state (e.g., a ready-to-use state, an open state, a state in which a substance in the medical device is to be administered, etc.), data associated with the medical device being placed in an inactivated state (e.g., a not ready-to-use state, a closed state, a state in which a substance in the medical device is not to be administered, etc.), data associated with the time when the medical device begins to be used in an activated state (e.g., a state in which a substance in the medical device begins to be administered), data associated with the time when the medical device ends being used in an activated state (e.g., a state in which a substance in the medical device ends being administered), and / or data related to the time when one or more components of the medical device (e.g., one or more safety components) are placed in a specific position (e.g., adjacent to each other, in a coupled connection, in a fixed connection, etc.), etc.

[0068] In some non-limiting embodiments, the RFID tag 106 may provide (e.g., transmit) data associated with the RFID tag 106 (e.g., a signal including the data) based on receiving an interrogation signal from the RFID reader device 104. In some non-limiting embodiments, the RFID tag 106 may provide (e.g., automatically provide) data associated with the RFID tag 106 continuously, periodically, or at predetermined time intervals.

[0069] In some non-limiting embodiments, the RFID tag 106 may include an RFID circuit and an electronic component electrically connected to the RFID circuit. In some non-limiting embodiments, when the electronic component is in a first state, the RFID circuit is configured to provide data associated with the RFID tag 106. In some non-limiting embodiments, when the electronic component is in a second state, the RFID circuit is configured to provide additional data associated with the RFID tag 106. In some non-limiting embodiments, when the electronic component is in the first state, the RFID circuit is configured to provide data associated with the RFID tag 106 that is different from the data associated with the RFID tag 106 that the RFID circuit is configured to provide when the electronic component is in the second state.

[0070] In some non-limiting embodiments, the medical device management system 102 may receive the first data associated with the RFID tag 106-1 from the RFID reader device 104. For example, the RFID reader device 104 may read the RFID tag 106-1 and obtain the first data associated with the RFID tag 106-1 based on reading the RFID tag 106-1. The RFID reader device 104 may send the first data associated with the RFID tag 106-1 to the medical device management system 102, and the medical device management system 102 may receive the first data associated with the RFID tag 106-1 from the RFID reader device 104 based on the RFID reader device 104 reading the RFID tag 106-1.

[0071] In some non-limiting embodiments, the medical device may include a disposable medical device. A disposable medical device may include a medical device designed and configured to be used once and then disposed of (e.g., discarded). Additionally or alternatively, a disposable medical device may include a medical device designed and configured to be used once on a single patient. In some non-limiting embodiments, a medical device such as a disposable medical device may include an indication (e.g., a mark, such as a logo, sticker, mark, etc.) that the disposable medical device will be used once and then disposed of. In some non-limiting embodiments, the medical device may include a container, such as a disposable container.

[0072] like Figure 3 As shown, at step 304, process 300 may include receiving second data associated with a second RFID tag attached to the medical device. For example, medical device management system 102 may receive second data associated with RFID tag 106-2 attached to the medical device. In some non-limiting embodiments, the first data associated with RFID tag 106-1 may be different from the data associated with RFID tag 106-2.

[0073] In some non-limiting embodiments, the medical device management system 102 may receive the second data associated with the RFID tag 106-2 from the RFID reader device 104. For example, the RFID reader device 104 may read the RFID tag 106-2 and obtain the second data associated with the RFID tag 106-2 based on reading the RFID tag 106-2. The RFID reader device 104 may send the second data associated with the RFID tag 106-2 to the medical device management system 102, and the medical device management system 102 may receive the second data associated with the RFID tag 106-2 from the RFID reader device 104 based on the RFID reader device 104 reading the RFID tag 106-2.

[0074] like Figure 3 As shown, at step 306, process 300 may include determining a characteristic of the medical device. For example, the medical device management system 102 may determine the characteristic of the medical device based on first data associated with the RFID tag 106-1 attached to the medical device and / or second data associated with the RFID tag 106-2 attached to the medical device. In some non-limiting embodiments, the medical device management system 102 may determine the characteristic of the medical device by comparing the first data and the second data. In some non-limiting embodiments, the medical device management system 102 may determine the characteristic of the medical device by comparing data associated with the RFID tag 106 provided by the RFID circuit of the RFID tag 106 when the electronic component of the RFID tag 106 is in the first state with data associated with the RFID tag 106 provided by the RFID circuit of the RFID tag 106 when the electronic component of the RFID tag 106 is in the second state.

[0075] In some non-limiting embodiments, the medical device management system 102 can determine the identification of the individual on whom the medical device is to be used, the time when the medical device is filled with a substance, the time when the medical device is placed in a package, the time when the medical device is taken out of a package, the time when the medical device is placed in an activated state, the time when the medical device is placed in an inactivated state, the time when the medical device begins to be used in an activated state, the time when the medical device ends being used in an activated state, and / or the time when one or more components of the medical device are set in a specific position, etc.

[0076] Additionally or alternatively, the medical device management system 102 can determine the type of substance administered using the medical device, the amount of substance administered using the medical device, the administration time of the substance administered using the medical device, the number of times the medical device is used (e.g., reused), the number of times the medical device is placed in an activated state, the number of times the medical device is placed in an inactivated state, the number of times the medical device is successfully used on an individual (e.g., a patient) (e.g., the number of times the medical device is successfully applied to an individual, the number of times the device is successfully inserted into an individual's body, the number of times the device is successfully delivered to an individual, etc.), the number of times the medical device is unsuccessfully used on an individual, the number of attempts to use the medical device on an individual, and / or the number of times the medical device is attempted on an individual but ultimately not used, etc.

[0077] In some non-limiting embodiments, the medical device management system 102 can assign a medical device to an individual (e.g., a patient) based on data associated with an RFID tag 106 attached to the medical device. For example, the medical device management system 102 can assign a medical device to an individual based on data associated with an identification of the individual. In such an example, the medical device management system 102 can determine whether the medical device is used (e.g., properly used) on the individual based on additional data associated with the RFID tag 106 attached to the medical device. In some non-limiting embodiments, after assigning the medical device to an individual, the medical device management system 102 can receive additional data from the RFID reader device 104, and the medical device management system 102 can determine whether the medical device has been used on the individual.

[0078] In some non-limiting embodiments, the medical device management system 102 can perform actions based on data associated with the RFID tag 106 attached to the medical device. For example, the medical device management system 102 can send data to a database. In some non-limiting embodiments, the medical device management system 102 can send data to an electronic medical record (EMR) system for automatic recording and / or secure confirmation that the medication to be administered matches the individual's medication order.

[0079] refer to Figure 4A and Figure 4B , Figure 4A and Figure 4B 4 is a schematic diagram of an RFID tag 400 and its components. In some non-limiting embodiments, the RFID tag 400 can be the same as or similar to the RFID tag 106. In some non-limiting embodiments, the RFID tag 400 can be attached to a medical device. For example, the RFID tag 400 can be attached to a syringe, an IV set, a catheter, a container, and / or a drug package, etc.

[0080] In some non-limiting embodiments, the RFID tag 400 can be attached to a syringe (e.g., an unfilled syringe, a prefilled syringe, and / or a needle-free syringe, etc.). For example, the RFID tag 400 can be attached to the syringe cap of the syringe. In such an example, the RFID tag 400 can bridge the gap between the syringe cap of the syringe and the syringe body. As another example, the RFID tag 400 can be attached to the safety device of the syringe. As another example, the RFID tag 400 can be attached to the barrel and plunger of the syringe. In such an example, the RFID tag 400 can bridge the gap between the barrel and plunger of the syringe. As another example, the RFID tag 400 can be attached to the sleeve (e.g., a foldable sleeve or a retractable sleeve) and / or a connector (e.g., a Luer connector, etc.) of a needle-free syringe. In such an example, the RFID tag 400 can be attached to the sleeve and / or connector of the needle-free syringe at one end, and attached to a matching device (e.g., a needle, a tube, and / or a Luer connector, etc.) at the opposite end.

[0081] In some non-limiting embodiments, the RFID tag 400 can be attached to an IV assembly. For example, the RFID tag 400 can be positioned between two components of an IV assembly. For example, the RFID tag 400 can be positioned between a syringe (e.g., a needle-free syringe) and a connector (e.g., an IV connector). In some non-limiting embodiments, the RFID tag 400 can be attached to two components of an IV assembly. For example, the RFID tag 400 can be attached to a syringe (e.g., a needle-free syringe) and / or a connector (e.g., an IV connector).

[0082] In some non-limiting embodiments, the RFID tag 400 can be attached to a catheter. For example, the RFID tag 400 can be attached to a safety device of a catheter. As another example, the RFID tag 400 can be attached to a cap (e.g., a disinfection cap) of a catheter. As another example, the RFID tag 400 can be attached to a connector (e.g., a Luer connector, etc.) of a catheter. In such an example, the RFID tag 400 can be attached to a connector of a catheter at one end and to a mating device (e.g., a needleless connector, a manifold, a catheter line, and / or a syringe, etc.) at the opposite end.

[0083] In some non-limiting embodiments, the RFID tag 400 can be attached to a container. For example, the RFID tag 400 can be attached to a medication container (e.g., a medicine bottle, a medicine box (e.g., a pill box), and / or an IV bag, etc.). In such an example, the RFID tag 400 can be attached to a cap of a container (e.g., a medication container). For example, the RFID tag 400 can bridge a gap between the cap of the container and the body of the container. In some non-limiting embodiments, the RFID tag 400 can be attached to a food container and / or a beverage container. In such an example, the RFID tag 400 can be attached to a cap of a food container and / or a beverage container.

[0084] In some non-limiting embodiments, the RFID tag 400 can be attached to the packaging of the medical device. In such an example, the RFID tag 400 can be attached to the cover and / or cap of the packaging of the medical device. For example, the RFID tag 400 can bridge the gap between the cover and / or cap of the packaging of the medical device and the body of the packaging of the medical device. In some non-limiting embodiments, the RFID tag 400 can be attached to a drug package (e.g., a drug blister package). In such an example, the RFID tag 400 can be set on a label of the drug package.

[0085] In some non-limiting embodiments, the RFID tag 400 may have a size that allows the RFID tag 400 to be attached to a particular medical device. In such an example, the size of the RFID tag 400 may be proportional to the size of the medical device or component of the medical device to which the RFID tag 400 is attached. As another example, the RFID tag 400 may have a size sufficient to include individual components of the plurality of components of the RFID tag 400 to be positioned on the RFID tag 400.

[0086] In some non-limiting embodiments, the RFID tag 400 may have a shape that allows the RFID tag 400 to be attached to a particular medical device. In such an example, the RFID tag 400 may have a shape that corresponds to an area of ​​the medical device to which the RFID tag 400 is attached. As another example, the RFID tag 400 may have a shape sufficient to include individual components of the plurality of components of the RFID tag 400 to be positioned on the RFID tag 400.

[0087] In some non-limiting embodiments, the RFID tag 400 can send a signal to an RFID reader device (e.g., the RFID reader device 104). In some non-limiting embodiments, the RFID tag 400 can be a passive RFID tag. In such an example, the RFID tag 400 (e.g., the RFID circuit 402 of the RFID tag 400) can be powered by electromagnetic energy of electromagnetic waves emitted from the RFID reader device for interrogating the RFID tag 400. In some non-limiting embodiments, the RFID tag 400 can be an active RFID tag. In such an example, the RFID tag 400 can be powered by a power supply included in the RFID tag 400, so that the RFID tag 400 can be read by the RFID reader device in a larger range than the passive RFID tag. In some non-limiting embodiments, the RFID tag 400 can be read by the RFID reader device at a distance of at least 100 meters. In some non-limiting embodiments, the RFID tag 400 can include an NFC tag. In some non-limiting embodiments, the RFID tag 400 can be an RFID tear tag 400. As used herein, the RFID tear tag 400 refers to an RFID tag including an electronic component wherein an output of the RFID tag 400 depends on whether the electronic component is in a closed state or in an open state.

[0088] In some non-limiting embodiments, Figure 4A and Figure 4B As shown, RFID tag 400 may include RFID circuit 402, electronic component 404, and base component 410. In some non-limiting embodiments, RFID circuit 402 may be positioned on base component 410. In such examples, RFID circuit 402 may be attached to base component 410 (e.g., by adhesive, welding, and / or soldering, etc.). In some non-limiting embodiments, electronic component 404 may be positioned on base component 410. For example, electronic component 404 may be attached to base component 410 (e.g., by adhesive, welding, and / or soldering, etc.). As another example, electronic component 404 may be embedded in base component 410. In some non-limiting embodiments, electronic component 404 may be coupled to RFID circuit 402. For example, electronic component 404 may be electrically connected to RFID circuit 402.

[0089] In some non-limiting embodiments, the base component 410 may include an attachment point 416 configured to allow the base component 410 to be separated into a first section and a second section.

[0090] In some non-limiting embodiments, the RFID tag 400 may include an RFID circuit 402. In some non-limiting embodiments, the RFID circuit 402 may have a suitable size based on the application for which the RFID tag 400 is designed. For example, the RFID circuit 402 may have a size that allows the RFID circuit 402 to be positioned on the base component 410. In some non-limiting embodiments, the RFID circuit 402 may include various components that are typically provided in an RFID circuit. In some non-limiting embodiments, the RFID circuit 402 may include a radio transponder, a radio receiver, and / or a radio transmitter, etc. In some non-limiting embodiments, the RFID circuit 402 may include a power source (e.g., a battery, etc.). In some non-limiting embodiments, the RFID circuit 402 may be powered by electromagnetic energy. As used herein, electromagnetic energy refers to the energy of electromagnetic waves characterized by an electromagnetic spectrum. In such an example, the RFID circuit 402 may be powered by electromagnetic energy from an RFID reader device.

[0091] In some non-limiting embodiments, the RFID circuit 402 can provide a signal to an RFID reader device. In such an example, the RFID circuit 402 can provide a signal during interrogation by the RFID reader device. In some non-limiting embodiments, the RFID circuit 402 can provide more than one signal.

[0092] In some non-limiting embodiments, the RFID circuit 402 can provide a signal based on the state of one or more components of the RFID tag 400. For example, the RFID circuit 402 can provide a first signal when one or more components of the RFID tag 400 are in a first state, and can provide a second signal when one or more components of the RFID tag 400 are in a second state.

[0093] In some non-limiting embodiments, the electronic component 404 may include a conductive element, such as a wire, an electrical trace (e.g., a conductive trace), an electrical conductor, a metal strip, a conductive ink, a conductive coating, and / or a conductive tab, etc. In some non-limiting embodiments, the electronic component 404 may have an appropriate size based on the application for which the RFID tag 400 is designed. For example, the electronic component 404 may have a size such that the electronic component 404 can be positioned on the base component 410. In some non-limiting embodiments, the electronic component 404 may include a conductive material.

[0094] In some non-limiting embodiments, the electronic component 404 may include a first portion 406 and a second portion 408. In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may be positioned on the base component 410. For example, the first portion 406 and the second portion 408 of the electronic component 404 may be attached to the base component 410 (e.g., by adhesive, welding and / or soldering, etc.). As another example, the first portion 406 and the second portion 408 of the electronic component 404 may be embedded in the base component 410.

[0095] In some non-limiting embodiments, the first part 406 and the second part 408 of the electronic component 404 are separable. For example, the first part 406 and the second part 408 may be destructively separable. In such an example, destructively separable means that once the first part 406 and the second part 408 of the electronic component 404 are decoupled, the first part 406 and the second part 408 cannot be recoupled. In another example, the first part 406 and the second part 408 of the electronic component 404 may be non-destructively separable. In such an example, non-destructively separable means that once the first part 406 and the second part 408 of the electronic component 404 are decoupled, the first part 406 and the second part 408 of the electronic component 404 can also be recoupled. In some non-limiting embodiments, the first part 406 and the second part 408 of the electronic component 404 may be configured to be separable independently of additional mechanical components.

[0096] In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may form a continuous, integrated electronic component 404. In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may be coupled. For example, the first portion 406 and the second portion 408 of the electronic component 404 may be electrically coupled (e.g., conductively coupled). In some non-limiting embodiments, the first portion 406 of the electronic component 404 may be connected (e.g., electrically connected) to the RFID circuit 402.

[0097] In some non-limiting embodiments, the base component 410 can be constructed of a suitable material based on the application for which the RFID tag 400 is designed. In some non-limiting embodiments, the base component 410 can have a suitable shape based on the application for which the RFID tag 400 is designed. In such examples, the shape of the base component 410 is not particularly limited, as long as the shape of the base component 410 can be suitable for the required components positioned thereon. Non-limiting examples of the shape of the base component 410 include, but are not limited to, a rectangle, a circle, an oval, a square, a parallelogram, a trapezoid, and / or a triangle, etc. In some non-limiting embodiments, the base component 410 can include a suitable material based on the application for which the RFID tag 400 is designed. In some non-limiting embodiments, the base component 410 can include paper and / or plastic, etc.

[0098] In some non-limiting embodiments, the base component 410 may include a first portion 412 and a second portion 414. In some non-limiting embodiments, the RFID circuit 402 may be positioned on the first portion 412 of the base component 410. For example, the RFID circuit 402 may be attached to the first portion 412 of the base component 410 (e.g., by adhesive, welding, and / or soldering, etc.). In some non-limiting embodiments, the first portion 406 of the electronic component 404 may be positioned on the first portion 412 of the base component 410. For example, the first portion 406 of the electronic component 404 may be attached to the first portion 412 of the base component 410 (e.g., by adhesive, welding, and / or soldering, etc.). As another example, the first portion 406 of the electronic component 404 may be embedded in the first portion 412 of the base component 410. In some non-limiting embodiments, the second portion 408 of the electronic component 404 may be positioned on the second portion 414 of the base component 410. For example, second portion 408 of electronic component 404 may be attached to second portion 414 of base component 410 (eg, by adhesive, welding and / or soldering, etc.). In another example, second portion 408 of electronic component 404 may be embedded in second portion 414 of base component 410.

[0099] In some non-limiting embodiments, the base component 410 may include an attachment point 416 that separates the first portion 412 of the base component 410 from the second portion 414 of the base component 410. In some non-limiting embodiments, the attachment point 416 may include a perforation. In such an example, the perforation may include a plurality of holes spanning the length of the attachment point 416. In some non-limiting embodiments, the attachment point 416 includes a perforation disposed on one side of the base component 410. In some non-limiting embodiments, the attachment point 416 may include a perforation disposed on only one side of the base component 410. For example, the perforation of the attachment point 416 may be disposed on one side of the base component 410 where the RFID circuit 402 and the electronic component 404 are located. In another example, the perforation of the attachment point 416 may be disposed on the opposite side of the base component 410 where the RFID circuit 402 and the electronic component 404 are located. In another non-limiting embodiment, the perforation of the attachment point 416 may be disposed on both sides of the base component 410.

[0100] In some non-limiting embodiments, the attachment point 416 may include a creased area. In such an example, the creased area of ​​the attachment point 416 may include a thinner area, or an area with poorer mechanical properties, compared to the rest of the base component 410. In some non-limiting embodiments, the attachment point 416 may include an adhesive. In such an example, the adhesive of the attachment point 416 may be configured to couple the first portion 412 of the base component 410 to the second portion 414 of the base component 410. In some non-limiting embodiments, the attachment point 416 may include a plurality of magnets. In such an example, the first portion 412 of the base component 410 may include at least one magnet at the attachment point 416, and the second portion 414 of the base component 410 may include at least one magnet at the attachment point 416, such that the magnets may couple the first portion 412 of the base component 410 to the second portion 414 of the base component 410.

[0101] In some non-limiting embodiments, the first portion 412 and the second portion 414 of the foundation component 410 may form a continuous, integral foundation component 410 at the attachment point 416. In such an example, the first portion 412 of the foundation component 410 is substantially connected to the second portion 414 of the foundation component 410 at the attachment point 416. In some non-limiting embodiments, the first portion 412 of the foundation component 410 may be separated from the second portion 414 of the foundation component 410 at the attachment point 416, such that the first portion 412 and the second portion 414 of the foundation component 410 are not substantially connected, but are coupled at the attachment point 416.

[0102] In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may be separable at the attachment point 416 of the base component 410. In such an example, the first portion 406 of the electronic component 404 may be coupled to the second portion 408 of the electronic component 404 at the attachment point 416 of the base component 410.

[0103] refer to Figure 4A In some non-limiting embodiments, when the electronic component 404 is in the first state, the first portion 406 and the second portion 408 of the electronic component 404 may be coupled together. For example, when the electronic component 404 is in the first state, the first portion 406 and the second portion 408 of the electronic component 404 may be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the electronic component 404 is in the first state, the first portion 412 and the second portion 414 of the base component 410 may be coupled together, such that the first portion 406 and the second portion 408 of the electronic component 404 are coupled together.

[0104] In some non-limiting embodiments, when the electronic component 404 is in the first state, the first portion 406 and the second portion 408 of the electronic component 404 may be recoupled after being previously decoupled. For example, when the electronic component 404 is in the first state, the first portion 406 and the second portion 408 of the electronic component 404 may be recoupled electrically (e.g., recoupled conductively) after being previously electrically decoupled (e.g., decoupled conductively). In some non-limiting embodiments, when the electronic component 404 is in the first state, the first portion 412 and the second portion 414 of the base component 410 may be recoupled after being previously decoupled, so that the first portion 406 and the second portion 408 of the electronic component 404 are recoupled after being previously decoupled. In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may be decoupled and then recoupled to change the state of the electronic component 404 from the first state to the second state and then back to the first state, and change the signal provided by the RFID circuit 402 from the first signal to the second signal and then back to the first signal any number of times.

[0105] In some non-limiting embodiments, when the electronic component 404 is in the first state, the RFID circuit 402 can be configured to provide a first signal, for example, during an interrogation by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit 402 can include data associated with an indication of the first state of the medical device. In some non-limiting embodiments, the data associated with the first state of the medical device can indicate a closed configuration. For example, the data associated with the first state of the medical device can indicate a closed configuration of the medical device. In such an example, the data associated with the first state of the medical device can indicate that a cap and / or cover of the medical device (e.g., a container, etc.) is fixed to the body of the medical device to seal the contents (e.g., a drug) within the medical device.

[0106] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate an unused configuration. For example, the data associated with the first state of the medical device may indicate an unused configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet delivered a drug. In another example, the data associated with the first state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has not yet been activated. In another example, the data associated with the first state of the medical device may indicate that the sleeve of the medical device (e.g., a foldable sleeve and / or a retractable sleeve, etc.) has not yet been displaced to connect the medical device to a mating device.

[0107] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate a coupling configuration. For example, the data associated with the first state of the medical device may indicate a coupling configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that a first component of the medical device is coupled to a second component of the medical device. In such an example, the data associated with the first state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0108] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate an uncontaminated configuration. For example, the data associated with the first state of the medical device may indicate an uncontaminated configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that a floating cannula of the medical device has not been touched or contacted prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the first state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has not been deformed.

[0109] In some non-limiting embodiments, the first signal provided by the RFID circuit 402 may include data associated with an indication of a first state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the first state of the packaging of the medical device may indicate a sealing configuration. For example, the data associated with the first state of the packaging of the medical device may indicate a sealing configuration of the packaging of the medical device. In such an example, the data associated with the first state of the packaging of the medical device may indicate that packaging has not been opened to remove the medical device from packaging. In another example, the data associated with the first state of the packaging of the medical device may indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) is not destroyed.

[0110] refer to Figure 4B In some non-limiting embodiments, when the electronic component 404 is in the second state, the first portion 406 and the second portion 408 of the electronic component 404 may be decoupled. For example, when the electronic component 404 is in the second state, the first portion 406 and the second portion 408 of the electronic component 404 may not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the electronic component 404 is in the second state, the first portion 412 of the base component 410 may be decoupled from the second portion 414 of the base component 410 at the attachment point 416, so that the first portion 406 and the second portion 408 of the electronic component 404 are decoupled. For example, the first portion 412 of the base component 410 may be decoupled from the second portion 414 of the base component 410 at the attachment point 416, so that there is a gap 418 between the first portion 412 and the second portion 414 of the base component 410. There is no particular limitation on the width W of the gap 418, as long as the width W is wide enough so that the first portion 406 and the second portion 408 of the electronic component 404 are not electrically coupled. In some non-limiting embodiments, the first portion 412 of the base component 410 can be decoupled from the second portion 414 of the base component 410 by pulling and / or rotating the first portion 412 of the base component 410 away from the second portion 414 of the base component 410 at the attachment point 416, such as to form a gap 418 of width W between the first portion 412 and the second portion 414 of the base component 410. For example, the base component 410 can be disconnected at the attachment point 416, and then the first portion 412 of the base component 410 can be pulled and / or rotated away from the second portion 414 of the base component 410. In some non-limiting embodiments, when the electronic component 404 is in the second state, the RFID circuit 402 can be configured to provide a second signal, such as during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit 402 can be different from the first signal provided by the RFID circuit 402.

[0111] In some non-limiting embodiments, the second signal provided by the RFID circuit 402 may include data associated with an indication of the second state of the medical device. In some non-limiting embodiments, the data associated with the second state of the medical device may indicate an open configuration. For example, the data associated with the second state of the medical device may indicate an open configuration of the medical device. In such an example, the data associated with the second state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) has been removed from the body of the medical device, so that the contents (e.g., a drug) within the medical device are no longer sealed within the medical device.

[0112] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate an unfilled configuration. For example, the data associated with the second state of the medical device may indicate an unfilled configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet received a drug.

[0113] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a usage configuration. For example, the data associated with the second state of the medical device may indicate a usage configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has delivered a drug. In another example, the data associated with the second state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has been activated. In another example, the data associated with the second state of the medical device may indicate that a sleeve (e.g., a foldable sleeve and / or a retractable sleeve, etc.) of the medical device has been displaced to connect the medical device to a mating device.

[0114] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a decoupled configuration. For example, the data associated with the second state of the medical device may indicate a decoupled configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that a first component of the medical device is not coupled to a second component of the medical device. In such an example, the data associated with the second state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is not connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0115] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a contaminated configuration. For example, the data associated with the second state of the medical device may indicate a contaminated configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that a floating cannula of the medical device has been bumped or touched prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the second state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has been deformed.

[0116] In some non-limiting embodiments, the second signal provided by the RFID circuit 402 can include data associated with the indication of the second state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the second state of the packaging of the medical device can indicate an unsealed configuration. For example, the data associated with the second state of the packaging of the medical device can indicate an unsealed configuration of the packaging of the medical device. In such an example, the data associated with the second state of the packaging of the medical device can indicate that packaging has been opened to remove the medical device from packaging. In another example, the data associated with the second state of the packaging of the medical device can indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) has been destroyed.

[0117] In some non-limiting embodiments, when the electronic component 404 is in the third state, the first portion 406 and the second portion 408 of the electronic component 404 may be recoupled after being previously decoupled. For example, when the electronic component 404 is in the third state, the first portion 406 and the second portion 408 of the electronic component 404 may be recoupled electrically (e.g., recoupled conductively) after being previously electrically decoupled (e.g., decoupled conductively). In some non-limiting embodiments, when the electronic component 404 is in the third state, the first portion 412 and the second portion 414 of the base component 410 may be recoupled after being previously decoupled, so that the first portion 406 and the second portion 408 of the electronic component 404 are recoupled after being previously decoupled. In some non-limiting embodiments, the first portion 406 and the second portion 408 of the electronic component 404 may be decoupled and then recoupled to change the state of the electronic component 404 from the first state to the second state to the third state, and to change the signal provided by the RFID circuit 402 from the first signal to the second signal to the third signal any number of times to provide any number of signals.

[0118] In some non-limiting embodiments, when the electronic component 404 is in the third state, the RFID circuit 402 can be configured to provide a third signal, for example, during an inquiry by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit 402 can be different from the first signal provided by the RFID circuit 402 and the second signal provided by the RFID circuit 402. In some non-limiting embodiments, the third signal provided by the RFID circuit 402 can include data associated with an indication of the third state of the medical device. In some non-limiting embodiments, the data associated with the third state of the medical device can indicate a re-closing configuration. For example, the data associated with the third state of the medical device can indicate a re-closing configuration of the medical device. In such an example, the data associated with the third state of the medical device can indicate that after the cap and / or cover of the medical device (e.g., container, etc.) has been previously removed to unseal the contents (e.g., medicine) in the medical device, the cap and / or cover has been reattached to the body of the medical device.

[0119] In some non-limiting embodiments, the data associated with the third state of the medical device may indicate a reuse configuration. For example, the data associated with the third state of the medical device may indicate a reuse configuration of the medical device. For example, the data associated with the third state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has been refilled with a drug after previously delivering the drug. In another example, the data associated with the third state of the medical device may indicate that the safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has been disabled after being previously activated. In another example, the data associated with the third state of the medical device may indicate that the sleeve of the medical device (e.g., a foldable sleeve and / or a retractable sleeve, etc.) has been returned to the original position of the sleeve after being previously displaced to connect the medical device to a mating device.

[0120] In some non-limiting embodiments, the data associated with the third state of the medical device may indicate a recoupling configuration. For example, the data associated with the third state of the medical device may indicate a recoupling configuration of the medical device. For example, the data associated with the third state of the medical device may indicate that a first component of the medical device is recoupled to a second component of the medical device after the first component of the medical device has previously been decoupled from the second component. In such an example, the data associated with the third state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is reconnected and / or resecured to a second connector (e.g., a Luer connector, etc.) after the first connector has previously been disconnected from the second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0121] In some non-limiting embodiments, the third signal provided by the RFID circuit 402 can include data associated with the indication of the third state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the third state of the packaging of the medical device can indicate a resealing configuration. For example, the data associated with the third state of the packaging of the medical device can indicate the resealing configuration of the packaging of the medical device. In such an example, the data associated with the third state of the packaging of the medical device can indicate that the packaging has been resealed after previously being opened to take the medical device out of the packaging. In another example, the data related to the third state of the packaging of the medical device can indicate that the seal of the medicine kept in the packaging (e.g., medicine blister pack, etc.) has been resealed after being previously destroyed.

[0122] refer to Figure 5 , Figure 5 is a schematic diagram of an RFID tag 500 and its components. In some non-limiting embodiments, the RFID tag 500 can be the same as or similar to the RFID tag 400 and / or the RFID tag 106. In some non-limiting embodiments, the RFID tag 500 can include a plurality of electronic components 504a, 504b, 504c, and the base component 510 can include a plurality of separable portions 514a, 514b, 514c corresponding to each of the plurality of electronic components 504a, 504b, 504c.

[0123] In some non-limiting embodiments, the RFID tag 500 can be attached to a medical device. For example, the RFID tag 500 can be attached to a syringe, an IV set, a catheter, a container, and / or a drug package, etc.

[0124] In some non-limiting embodiments, the RFID tag 500 can be attached to a syringe (e.g., an unfilled syringe, a prefilled syringe, and / or a needle-free syringe, etc.). For example, the RFID tag 500 can be attached to the syringe cap of the syringe. In such an example, the RFID tag 500 can bridge the gap between the syringe cap of the syringe and the syringe body. As another example, the RFID tag 500 can be attached to the safety device of the syringe. As another example, the RFID tag 500 can be attached to the barrel and plunger of the syringe. In such an example, the RFID tag 500 can bridge the gap between the barrel and plunger of the syringe. As another example, the RFID tag 500 can be attached to the sleeve (e.g., a foldable sleeve or a retractable sleeve) and / or a connector (e.g., a Luer connector, etc.) of a needle-free syringe. In such an example, the RFID tag 500 can be attached to the sleeve and / or connector of the needle-free syringe at one end, and attached to a matching device (e.g., a needle, a tube, and / or a Luer connector, etc.) at the opposite end.

[0125] In some non-limiting embodiments, the RFID tag 500 can be attached to an IV assembly. For example, the RFID tag 500 can be located between two components of an IV assembly. For example, the RFID tag 500 can be located between a syringe (e.g., a needle-free syringe) and a connector (e.g., an IV connector). In some non-limiting embodiments, the RFID tag 500 can be attached to two components of an IV assembly. For example, the RFID tag 500 can be attached to a syringe (e.g., a needle-free syringe) and / or a connector (e.g., an IV connector).

[0126] In some non-limiting embodiments, the RFID tag 500 can be attached to a catheter. For example, the RFID tag 500 can be attached to a safety device of a catheter. As another example, the RFID tag 500 can be attached to a cap (e.g., a disinfection cap) of a catheter. As another example, the RFID tag 500 can be attached to a connector (e.g., a Luer connector, etc.) of a catheter. In such an example, the RFID tag 500 can be attached to a connector of a catheter at one end and to a mating device (e.g., a needleless connector, a manifold, and / or a catheter line, etc.) at the opposite end.

[0127] In some non-limiting embodiments, the RFID tag 500 can be attached to a container. For example, the RFID tag 500 can be attached to a medication container (e.g., a medicine bottle, a medicine box (e.g., a pill box), and / or an IV bag, etc.). In such an example, the RFID tag 500 can be attached to a cap of a container (e.g., a medication container). For example, the RFID tag 500 can bridge a gap between the cap of the container and the body of the container. In some non-limiting embodiments, the RFID tag 500 can be attached to a food container and / or a beverage container. In such an example, the RFID tag 500 can be attached to a cap of a food container and / or a beverage container.

[0128] In some non-limiting embodiments, the RFID tag 500 can be attached to the packaging of the medical device. In such an example, the RFID tag 500 can be attached to the cover and / or cap of the packaging of the medical device. For example, the RFID tag 500 can bridge the gap between the cover and / or cap of the packaging of the medical device and the body of the packaging of the medical device. In some non-limiting embodiments, the RFID tag 500 can be attached to a drug package (e.g., a drug blister package). In such an example, the RFID tag 500 can be set on a label of the drug package.

[0129] In some non-limiting embodiments, the RFID tag 500 may have a size that allows the RFID tag 500 to be attached to a particular medical device. In such an example, the size of the RFID tag 500 may be proportional to the size of the medical device or component of the medical device to which the RFID tag 500 is attached. As another example, the RFID tag 500 may have a size sufficient to include individual components of the plurality of components of the RFID tag 500 to be positioned on the RFID tag 500.

[0130] In some non-limiting embodiments, the RFID tag 500 may have a shape that allows the RFID tag 500 to be attached to a particular medical device. In such an example, the RFID tag 500 may have a shape that corresponds to an area of ​​the medical device to which the RFID tag 500 is attached. As another example, the RFID tag 500 may have a shape sufficient to include individual components of the plurality of components of the RFID tag 500 to be positioned on the RFID tag 500.

[0131] In some non-limiting embodiments, the RFID tag 500 can send a signal to an RFID reader device (e.g., the RFID reader device 104). In some non-limiting embodiments, the RFID tag 500 can be a passive RFID tag. In such an example, the RFID tag 500 (e.g., the RFID circuit 502 of the RFID tag 500) can be powered by electromagnetic energy from electromagnetic waves emitted by the RFID reader device to interrogate the RFID tag 500. In some non-limiting embodiments, the RFID tag 500 can be an active RFID tag. In such an example, the RFID tag 500 can be powered by a power source included in the RFID tag 500, so that the RFID tag 500 can be read by the RFID reader device in a larger range than the passive RFID tag. In some non-limiting embodiments, the RFID tag 500 can be read by the RFID reader device at a distance of at least 100 meters. In some non-limiting embodiments, the RFID tag 500 can be a near field communication (NFC) tag 500. In some non-limiting embodiments, the RFID tag 500 can be an RFID tear tag 500. As used herein, the RFID tear tag 500 refers to an RFID tag including an electronic component wherein an output of the RFID tag 500 depends on whether the electronic component is in a closed state or an open state.

[0132] In some non-limiting embodiments, the RFID tag 500 may include an RFID circuit 502, a plurality of electronic components 504a, 504b, 504c, and a base component 510. In some non-limiting embodiments, the RFID circuit 502 may be positioned on the base component 510. In such examples, the RFID circuit 502 may be attached to the base component 510 (e.g., by adhesive, welding and / or soldering, etc.). In some non-limiting embodiments, the plurality of electronic components 504a, 504b, 504c may be positioned on the base component 510. For example, the plurality of electronic components 504a, 504b, 504c may be attached to the base component 510 (e.g., by adhesive, welding and / or soldering, etc.). As another example, the plurality of electronic components 504a, 504b, 504c may be embedded in the base component 510. In some non-limiting embodiments, each of the plurality of electronic components 504a, 504b, 504c may be coupled to the RFID circuit 502. For example, each of the plurality of electronic components 504 a , 504 b , 504 c may be electrically connected to the RFID circuit 502 .

[0133] In some non-limiting embodiments, the base component 510 may include an attachment point 516 configured to allow the base component 510 to be separated into a first section and a plurality of separable sections.

[0134] In some non-limiting embodiments, RFID tag 500 may include RFID circuit 502. In some non-limiting embodiments, RFID circuit 502 may be the same as RFID circuit 402. In some non-limiting embodiments, RFID circuit 502 may provide a signal based on the state of one or more components of RFID tag 500. For example, RFID circuit 502 may provide a particular signal when one or more components of RFID tag 500 are in a first state, and may provide a different signal when one or more components of RFID tag 500 are in a second state.

[0135] In some non-limiting embodiments, the plurality of electronic components 504a, 504b, 504c may include a first electronic component 504a. In some non-limiting embodiments, the first electronic component 504a may be the same as the electronic component 404. In some non-limiting embodiments, the first electronic component 504a may include a first portion 506a and a second portion 508a. In some non-limiting embodiments, the first portion 506a and the second portion 508a of the first electronic component 504a may be the same as the first portion 406 and the second portion 408 of the electronic component 404.

[0136] In some non-limiting embodiments, the plurality of electronic components 504a, 504b, 504c may include a second electronic component 504b. In some non-limiting embodiments, the second electronic component 504b may be the same as the electronic component 404. In some non-limiting embodiments, the second electronic component 504b may include a first portion 506b and a second portion 508b. In some non-limiting embodiments, the first portion 506b and the second portion 508b of the second electronic component 504b may be the same as the first portion 406 and the second portion 408 of the electronic component 404.

[0137] In some non-limiting embodiments, the plurality of electronic components 504a, 504b, 504c may include a third electronic component 504c. In some non-limiting embodiments, the third electronic component 504c may be the same as the electronic component 404. In some non-limiting embodiments, the third electronic component 504c may include a first portion 506c and a second portion 508c.

[0138] In some non-limiting embodiments, the first portion 506 c and the second portion 508 c of the third electronic component 504 c may be identical to the first portion 406 and the second portion 408 of the electronic component 404 .

[0139] It can be easily envisioned that the RFID tag 500 may include additional electronic components having the same characteristics as the characteristics of the plurality of electronic components 504a, 504b, 504c, such as a fourth electronic component and / or a fifth electronic component, etc. For example, the RFID tag 500 may include at least two, or at least three, or at least four, or at least five electronic components 504, wherein each electronic component 504 may include an accompanying detachable portion of the base component 510 (e.g., one of the plurality of detachable portions 514a, 514b, or 514c).

[0140] In some non-limiting embodiments, the base component 510 can be the same as the base component 410. In some non-limiting embodiments, the base component 510 can include a first portion 512 and a plurality of separable portions 514a, 514b, 514c. In some non-limiting embodiments, the first portion 512 of the base component 510 can be the same as the first portion 412 of the base component 410.

[0141] In some non-limiting embodiments, the plurality of separable portions 514a, 514b, 514c may include a first separable portion 514a. In some non-limiting embodiments, the second portion 508a of the first electronic component 504a may be positioned on the first separable portion 514a of the base component 510. For example, the second portion 508a of the first electronic component 504a may be attached to the first separable portion 514a of the base component 510 (e.g., by adhesive, welding and / or soldering, etc.). As another example, the second portion 508a of the first electronic component 504a may be embedded in the first separable portion 514a of the base component 510.

[0142] In some non-limiting embodiments, the plurality of separable portions 514a, 514b, 514c may include a second separable portion 514b. In some non-limiting embodiments, the second portion 508b of the second electronic component 504b may be positioned on the second separable portion 514b of the base component 510. For example, the second portion 508b of the second electronic component 504b may be attached to the second separable portion 514b of the base component 510 (e.g., by adhesive, welding and / or soldering, etc.). As another example, the second portion 508b of the second electronic component 504b may be embedded in the second separable portion 514b of the base component 510.

[0143] In some non-limiting embodiments, the plurality of separable portions 514a, 514b, 514c may include a third separable portion 514c. In some non-limiting embodiments, the second portion 508c of the third electronic component 504c may be positioned on the third separable portion 514c of the base component 510. For example, the second portion 508c of the third electronic component 504c may be attached to the third separable portion 514c of the base component 510 (e.g., by adhesive, welding and / or soldering, etc.). As another example, the second portion 508c of the third electronic component 504c may be embedded in the third separable portion 514c of the base component 510.

[0144] In some non-limiting embodiments, the base component 510 can include an attachment point 516 that separates the first portion 512 of the base component 510 from the plurality of separable portions 514a, 514b, 514c of the base component 510. In some non-limiting embodiments, the attachment point 516 can be the same as the attachment point 416.

[0145] In some non-limiting embodiments, the first portion 512 of the foundation component 510 and the plurality of separable portions 514a, 514b, 514c can form a continuous, integral foundation component 510 at an attachment point 516. In such an example, the first portion 512 of the foundation component 510 is substantially connected to each of the plurality of separable portions 514a, 514b, 514c of the foundation component 510 at the attachment point 516. In some non-limiting embodiments, the first portion 512 of the foundation component 510 can be separated from each of the plurality of separable portions 514a, 514b, 514c of the foundation component 510 at the attachment point 516, such that the first portion 512 of the foundation component 510 and the plurality of separable portions 514a, 514b, 514c are not substantially connected but are coupled at the attachment point 516.

[0146] In some non-limiting embodiments, when the first electronic component 504a is in the first state, the first portion 506a and the second portion 508a of the first electronic component 504a can be coupled together. For example, when the first electronic component 504a is in the first state, the first portion 506a and the second portion 508a of the first electronic component 504a can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the first electronic component 504a is in the first state, the first portion 512 and the first detachable portion 514a of the base component 510 can be coupled together such that the first portion 506a and the second portion 508a of the first electronic component 504a are coupled together.

[0147] In some non-limiting embodiments, when the second electronic component 504b is in the first state, the first portion 506b and the second portion 508b of the second electronic component 504b can be coupled together. For example, when the second electronic component 504b is in the first state, the first portion 506b and the second portion 508b of the second electronic component 504b can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the second electronic component 504b is in the first state, the first portion 512 and the second detachable portion 514b of the base component 510 can be coupled together, so that the first portion 506b and the second portion 508b of the second electronic component 504b are coupled together.

[0148] In some non-limiting embodiments, when the third electronic component 504c is in the first state, the first portion 506c and the second portion 508c of the third electronic component 504c can be coupled together. For example, when the third electronic component 504c is in the first state, the first portion 506c and the second portion 508c of the third electronic component 504c can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the third electronic component 504c is in the first state, the first portion 512 and the third detachable portion 514c of the base component 510 can be coupled together, so that the first portion 506c and the second portion 508c of the third electronic component 504c are coupled together.

[0149] In some non-limiting embodiments, when the first electronic component 504a, the second electronic component 504b and / or the third electronic component 504c are in the first state, the RFID circuit 502 can be configured to provide a first signal, for example, during an inquiry by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit 502 can include data associated with an indication of the first state of the medical device. In some non-limiting embodiments, the data associated with the first state of the medical device can indicate a closed configuration. For example, the data associated with the first state of the medical device can indicate a closed configuration of the medical device. In such an example, the data associated with the first state of the medical device can indicate that a cap and / or a cover of the medical device (e.g., a container, etc.) is fixed to the body of the medical device to seal the contents (e.g., a drug) within the medical device.

[0150] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate an unused configuration. For example, the data associated with the first state of the medical device may indicate an unused configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet delivered a drug. In another example, the data associated with the first state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has not yet been activated. In another example, the data associated with the first state of the medical device may indicate that the sleeve of the medical device (e.g., a foldable sleeve and / or a retractable sleeve, etc.) has not yet been displaced to connect the medical device to a mating device.

[0151] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate a coupling configuration. For example, the data associated with the first state of the medical device may indicate a coupling configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that a first component of the medical device is coupled to a second component of the medical device. In such an example, the data associated with the first state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0152] In some non-limiting embodiments, the data associated with the first state of the medical device may indicate an uncontaminated configuration. For example, the data associated with the first state of the medical device may indicate an uncontaminated configuration of the medical device. For example, the data associated with the first state of the medical device may indicate that a floating cannula of the medical device has not been touched or contacted prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the first state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has not been deformed.

[0153] In some non-limiting embodiments, the first signal provided by the RFID circuit 502 may include data associated with an indication of a first state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the first state of the packaging of the medical device may indicate a sealing configuration. For example, the data associated with the first state of the packaging of the medical device may indicate a sealing configuration of the packaging of the medical device. In such an example, the data associated with the first state of the packaging of the medical device may indicate that packaging has not been opened to remove the medical device from packaging. In another example, the data associated with the first state of the packaging of the medical device may indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) is not destroyed.

[0154] In some non-limiting embodiments, when the first electronic component 504a is in the second state, the first portion 506a and the second portion 508a of the first electronic component 504a can be decoupled. For example, when the first electronic component 504a is in the second state, the first portion 506a and the second portion 508a of the first electronic component 504a can not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the first electronic component 504a is in the second state, the first portion 512 of the base component 510 can be decoupled from the first detachable portion 514a of the base component 510 at the attachment point 516, such that the first portion 506a and the second portion 508a of the first electronic component 504a are decoupled. For example, the first portion 512 of the base component 510 can be decoupled from the first detachable portion 514a of the base component 510 at the attachment point 516, such that a gap exists between the first portion 512 of the base component 510 and the first detachable portion 514a, wherein the gap is wide enough so that the first portion 506a and the second portion 508a of the first electronic component 504a are not electrically coupled. In some non-limiting embodiments, the first portion 512 of the base component 510 can be decoupled from the first detachable portion 514a of the base component 510 by pulling and / or rotating the first portion 512 of the base component 510 away from the first detachable portion 514a of the base component 510 at the attachment point 516, thereby forming a gap having a width between the first portion 512 of the base component 510 and the first detachable portion 514a of the base component 510. For example, the base component 510 may be disconnected at the attachment point 516 , and then the first portion 512 of the base component 510 may be pulled and / or rotated away from the first detachable portion 514a of the base component 510 .

[0155] In some non-limiting embodiments, when the second electronic component 504b is in the second state, the first portion 506b and the second portion 508b of the second electronic component 504b can be decoupled. For example, when the second electronic component 504b is in the second state, the first portion 506b and the second portion 508b of the second electronic component 504b can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the second electronic component 504b is in the second state, the first portion 512 of the base component 510 can be decoupled from the second detachable portion 514b of the base component 510 at the attachment point 516, thereby decoupling the first portion 506b and the second portion 508b of the second electronic component 504b. For example, the first portion 512 of the base component 510 can be decoupled from the second detachable portion 514b of the base component 510 at the attachment point 516, so that there is a gap between the first portion 512 of the base component 510 and the second detachable portion 514b, wherein the gap is wide enough so that the first portion 506b and the second portion 508b of the second electronic component 504b are not electrically coupled. In some non-limiting embodiments, the first portion 512 of the base component 510 can be decoupled from the second detachable portion 514b of the base component 510 by pulling and / or rotating the first portion 512 of the base component 510 away from the second detachable portion 514b of the base component 510 at the attachment point 516, thereby forming a gap having a width between the first portion 512 of the base component 510 and the second detachable portion 514b of the base component 510. For example, the base component 510 can be disconnected at the attachment point 516, and then the first portion 512 of the base component 510 can be pulled and / or rotated away from the second detachable portion 514b of the base component 510.

[0156] In some non-limiting embodiments, when the third electronic component 504c is in the second state, the first portion 506c and the second portion 508c of the third electronic component 504c can be decoupled. For example, when the third electronic component 504c is in the second state, the first portion 506c and the second portion 508c of the third electronic component 504c can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the third electronic component 504c is in the second state, the first portion 512 of the base component 510 can be decoupled from the third detachable portion 514c of the base component 510 at the attachment point 516, thereby decoupling the first portion 506c and the second portion 508c of the third electronic component 504c. For example, the first portion 512 of the base component 510 can be decoupled from the third detachable portion 514c of the base component 510 at the attachment point 516, so that there is a gap between the first portion 512 of the base component 510 and the third detachable portion 514c, wherein the gap is wide enough so that the first portion 506c and the second portion 508c of the third electronic component 504c are not electrically coupled. In some non-limiting embodiments, the first portion 512 of the base component 510 can be decoupled from the third detachable portion 514c of the base component 510 by pulling and / or rotating the first portion 512 of the base component 510 away from the third detachable portion 514c of the base component 510 at the attachment point 516, thereby forming a gap having a width between the first portion 512 of the base component 510 and the third detachable portion 514c. For example, the base component 510 may be disconnected at the attachment point 516 and then the first portion 512 of the base component 510 may be pulled and / or rotated away from the third detachable portion 514 c of the base component 510 .

[0157] In some non-limiting embodiments, when the first electronic component 504a, the second electronic component 504b, and / or the third electronic component 504c are in the second state, the RFID circuit 502 can be configured to provide a second signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit 502 can be different from the first signal provided by the RFID circuit 502.

[0158] In some non-limiting embodiments, the second signal provided by the RFID circuit 502 may include data associated with an indication of the second state of the medical device. In some non-limiting embodiments, the data associated with the second state of the medical device may indicate an open configuration. For example, the data associated with the second state of the medical device may indicate an open configuration of the medical device. In such an example, the data associated with the second state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) has been removed from the body of the medical device, such that the contents (e.g., a drug) within the medical device are no longer sealed within the medical device.

[0159] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate an unfilled configuration. For example, the data associated with the second state of the medical device may indicate an unfilled configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet received a drug.

[0160] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a usage configuration. For example, the data associated with the second state of the medical device may indicate a usage configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has delivered a drug. In another example, the data associated with the second state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has been activated. In another example, the data associated with the second state of the medical device may indicate that a sleeve (e.g., a foldable sleeve and / or a retractable sleeve, etc.) of the medical device has been displaced to connect the medical device to a mating device.

[0161] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a decoupled configuration. For example, the data associated with the second state of the medical device may indicate a decoupled configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that a first component of the medical device is not coupled to a second component of the medical device. In such an example, the data associated with the second state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is not connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0162] In some non-limiting embodiments, the data associated with the second state of the medical device may indicate a contaminated configuration. For example, the data associated with the second state of the medical device may indicate a contaminated configuration of the medical device. For example, the data associated with the second state of the medical device may indicate that a floating cannula of the medical device has been bumped or touched prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the second state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has been deformed.

[0163] In some non-limiting embodiments, the second signal provided by the RFID circuit 502 may include data associated with the indication of the second state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the second state of the packaging of the medical device may indicate an unsealed configuration. For example, the data associated with the second state of the packaging of the medical device may indicate an unsealed configuration of the packaging of the medical device. In such an example, the data associated with the second state of the packaging of the medical device may indicate that packaging has been opened to remove the medical device from packaging. In another example, the data associated with the second state of the packaging of the medical device may indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) has been destroyed.

[0164] In some non-limiting embodiments, when the second electronic component 504b is in the third state, the first portion 506b and the second portion 508b of the second electronic component 504b can be coupled together. For example, when the second electronic component 504b is in the third state, the first portion 506b and the second portion 508b of the second electronic component 504b can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the second electronic component 504b is in the third state, the first portion 512 and the second detachable portion 514b of the base component 510 can be coupled together, so that the first portion 506b and the second portion 508b of the second electronic component 504b are coupled together.

[0165] In some non-limiting embodiments, when the second electronic component 504b is in the third state, the RFID circuit 502 can be configured to provide a third signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit 502 can be different from the first signal and the second signal provided by the RFID circuit 502.

[0166] In some non-limiting embodiments, the third signal provided by the RFID circuit 502 may include data associated with an indication of the third state of the medical device. In some non-limiting embodiments, the data associated with the third state of the medical device may indicate a closed configuration. For example, the data associated with the third state of the medical device may indicate a closed configuration of the medical device. In such an example, the data associated with the third state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) is secured to the body of the medical device to seal the contents (e.g., a drug) within the medical device.

[0167] In some non-limiting embodiments, the data associated with the third state of the medical device may indicate an unused configuration. For example, the data associated with the third state of the medical device may indicate an unused configuration of the medical device. For example, the data associated with the third state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet delivered a drug. In another example, the data associated with the third state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has not yet been activated. In another example, the data associated with the third state of the medical device may indicate that the sleeve of the medical device (e.g., a foldable sleeve and / or a retractable sleeve, etc.) has not yet been displaced to connect the medical device to a mating device.

[0168] In some non-limiting embodiments, the data associated with the third state of the medical device may indicate a coupling configuration. For example, the data associated with the third state of the medical device may indicate a coupling configuration of the medical device. For example, the data associated with the third state of the medical device may indicate that a first component of the medical device is coupled to a second component of the medical device. In such an example, the data associated with the third state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0169] In some non-limiting embodiments, the data associated with the third state of the medical device may indicate an uncontaminated configuration. For example, the data associated with the third state of the medical device may indicate an uncontaminated configuration of the medical device. For example, the data associated with the third state of the medical device may indicate that a floating cannula of the medical device has not been touched or contacted prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the third state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has not been deformed.

[0170] In some non-limiting embodiments, the third signal provided by the RFID circuit 502 can include data associated with the indication of the third state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the third state of the packaging of the medical device can indicate a sealing configuration. For example, the data associated with the third state of the packaging of the medical device can indicate the sealing configuration of the packaging of the medical device. In such an example, the data associated with the third state of the packaging of the medical device can indicate that the packaging has not been opened and the medical device cannot be taken out from the packaging. In another example, the data associated with the third state of the packaging of the medical device can indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) is not destroyed.

[0171] In some non-limiting embodiments, when the second electronic component 504b is in the fourth state, the first portion 506b and the second portion 508b of the second electronic component 504b can be decoupled. For example, when the second electronic component 504b is in the fourth state, the first portion 506b and the second portion 508b of the second electronic component 504b can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the second electronic component 504b is in the fourth state, the first portion 512 of the base component 510 can be decoupled from the second detachable portion 514b of the base component 510 at the attachment point 516, such that the first portion 506b and the second portion 508b of the second electronic component 504b are decoupled. For example, the first portion 512 of the base component 510 can be decoupled from the second detachable portion 514b of the base component 510 at the attachment point 516 so that a gap exists between the first portion 512 and the second detachable portion 514b of the base component 510, wherein the gap is wide enough such that the first portion 506b and the second portion 508b of the second electronic component 504b are not electrically coupled.

[0172] In some non-limiting embodiments, when the second electronic component 504b is in the fourth state, the RFID circuit 502 can be configured to provide a fourth signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the fourth signal provided by the RFID circuit 502 can be different from the first signal, the second signal, and the third signal provided by the RFID circuit 502.

[0173] In some non-limiting embodiments, the fourth signal provided by the RFID circuit 502 may include data associated with an indication of a fourth state of the medical device. In some non-limiting embodiments, the data associated with the fourth state of the medical device may indicate an open configuration. For example, the data associated with the fourth state of the medical device may indicate an open configuration of the medical device. In such an example, the data associated with the fourth state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) has been removed from the body of the medical device, such that the contents (e.g., a drug) within the medical device are no longer sealed within the medical device.

[0174] In some non-limiting embodiments, the data associated with the fourth state of the medical device may indicate an unfilled configuration. For example, the data associated with the fourth state of the medical device may indicate an unfilled configuration of the medical device. For example, the data associated with the fourth state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet received a drug.

[0175] In some non-limiting embodiments, the data associated with the fourth state of the medical device may indicate a usage configuration. For example, the data associated with the fourth state of the medical device may indicate a usage configuration of the medical device. For example, the data associated with the fourth state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has delivered a drug. In another example, the data associated with the fourth state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has been activated. In another example, the data associated with the fourth state of the medical device may indicate that a sleeve (e.g., a foldable sleeve and / or a telescopic sleeve, etc.) of the medical device has been displaced to connect the medical device to a mating device.

[0176] In some non-limiting embodiments, the data associated with the fourth state of the medical device may indicate a decoupled configuration. For example, the data associated with the fourth state of the medical device may indicate a decoupled configuration of the medical device. For example, the data associated with the fourth state of the medical device may indicate that a first component of the medical device is not coupled to a second component of the medical device. In such an example, the data associated with the fourth state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is not connected to a second connector (e.g., a Luer connector, etc.), such as a connection between a needle-free syringe and an IV connector.

[0177] In some non-limiting embodiments, the data associated with the fourth state of the medical device may indicate a contaminated configuration. For example, the data associated with the fourth state of the medical device may indicate a contaminated configuration of the medical device. For example, the data associated with the fourth state of the medical device may indicate that a floating cannula of the medical device has been bumped or touched prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the fourth state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has been deformed.

[0178] In some non-limiting embodiments, the fourth signal provided by the RFID circuit 502 may include data associated with an indication of a fourth state of the medical device package. In some non-limiting embodiments, the data associated with the fourth state of the medical device package may indicate an unsealed configuration. For example, the data associated with the fourth state of the medical device package may indicate an unsealed configuration of the medical device package. In such an example, the data associated with the fourth state of the medical device package may indicate that the package has been opened to remove the medical device from the package. In another example, the data associated with the fourth state of the medical device package may indicate that the seal of the medicine in the package (e.g., a medicine blister package, etc.) has been broken.

[0179] In some non-limiting embodiments, when the third electronic component 504c is in the fifth state, the first portion 506c and the second portion 508c of the third electronic component 504c can be coupled together. For example, when the third electronic component 504c is in the fifth state, the first portion 506c and the second portion 508c of the third electronic component 504c can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the third electronic component 504c is in the fifth state, the first portion 512 and the third detachable portion 514c of the base component 510 can be coupled together, so that the first portion 506c and the second portion 508c of the third electronic component 504c are coupled together.

[0180] In some non-limiting embodiments, when the third electronic component 504c is in the fifth state, the RFID circuit 502 can be configured to provide a fifth signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the fifth signal provided by the RFID circuit 502 can be different from the first signal, the second signal, the third signal, and the fourth signal provided by the RFID circuit 502.

[0181] In some non-limiting embodiments, the fifth signal provided by the RFID circuit 502 may include data associated with an indication of a fifth state of the medical device. In some non-limiting embodiments, the data associated with the fifth state of the medical device may indicate a closed configuration. For example, the data associated with the fifth state of the medical device may indicate a closed configuration of the medical device. In such an example, the data associated with the fifth state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) is secured to the body of the medical device to seal the contents (e.g., a drug) within the medical device.

[0182] In some non-limiting embodiments, the data associated with the fifth state of the medical device may indicate an unused configuration. For example, the data associated with the fifth state of the medical device may indicate an unused configuration of the medical device. For example, the data associated with the fifth state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet delivered a drug. In another example, the data associated with the fifth state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has not yet been activated. In another example, the data associated with the fifth state of the medical device may indicate that the sleeve of the medical device (e.g., a foldable sleeve and / or a telescopic sleeve, etc.) has not yet been displaced to connect the medical device to a mating device.

[0183] In some non-limiting embodiments, the data associated with the fifth state of the medical device may indicate a coupling configuration. For example, the data associated with the fifth state of the medical device may indicate a coupling configuration of the medical device. For example, the data associated with the fifth state of the medical device may indicate that a first component of the medical device is coupled to a second component of the medical device. In such an example, the data associated with the fifth state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is connected to a second connector, such as a connection between a needle-free syringe and an IV connector.

[0184] In some non-limiting embodiments, the data associated with the fifth state of the medical device may indicate an uncontaminated configuration. For example, the data associated with the fifth state of the medical device may indicate an uncontaminated configuration of the medical device. For example, the data associated with the fifth state of the medical device may indicate that a floating cannula of the medical device has not been bumped or touched prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the fifth state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has not been deformed.

[0185] In some non-limiting embodiments, the fifth signal provided by the RFID circuit 502 can include data associated with the indication of the fifth state of the packaging of medical equipment. In some non-limiting embodiments, the data associated with the fifth state of the packaging of medical equipment can indicate a sealing configuration. For example, the data associated with the fifth state of the packaging of medical equipment can indicate the sealing configuration of the packaging of medical equipment. In such an example, the data associated with the fifth state of the packaging of medical equipment can indicate that packaging has not been opened to remove medical equipment from packaging. In another example, the data associated with the fifth state of the packaging of medical equipment can indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) is not destroyed.

[0186] In some non-limiting embodiments, when the third electronic component 504c is in the sixth state, the first portion 506c and the second portion 508c of the third electronic component 504c may be decoupled. For example, when the third electronic component 504c is in the sixth state, the first portion 506c and the second portion 508c of the third electronic component 504c may not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the third electronic component 504c is in the sixth state, the first portion 512 of the base component 510 may be separated from the third detachable portion 514c of the base component 510 at the attachment point 516, thereby decoupling the first portion 506c and the second portion 508c of the third electronic component 504c. For example, the first portion 512 of the base component 510 can be decoupled from the third detachable portion 514c of the base component 510 at the attachment point 516 so that a gap exists between the first portion 512 of the base component 510 and the third detachable portion 514c, wherein the gap is wide enough such that the first portion 506c and the second portion 508c of the third electronic component 504c are not electrically coupled.

[0187] In some non-limiting embodiments, when the third electronic component 504c is in the sixth state, the RFID circuit 502 can be configured to provide a sixth signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the sixth signal provided by the RFID circuit 502 can be different from the first signal, the second signal, the third signal, the fourth signal, and the fifth signal provided by the RFID circuit 502.

[0188] In some non-limiting embodiments, the sixth signal provided by the RFID circuit 502 may include data associated with an indication of the sixth state of the medical device. In some non-limiting embodiments, the data associated with the sixth state of the medical device may indicate an open configuration. For example, the data associated with the sixth state of the medical device may indicate an open configuration of the medical device. In such an example, the data associated with the sixth state of the medical device may indicate that a cap and / or cover of the medical device (e.g., a container, etc.) has been removed from the body of the medical device so that the contents (e.g., a drug) within the medical device are no longer sealed within the medical device.

[0189] In some non-limiting embodiments, the data associated with the sixth state of the medical device may indicate an unfilled configuration. For example, the data associated with the sixth state of the medical device may indicate an unfilled configuration of the medical device. For example, the data associated with the sixth state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has not yet received a drug.

[0190] In some non-limiting embodiments, the data associated with the sixth state of the medical device may indicate a use configuration. For example, the data associated with the sixth state of the medical device may indicate a use configuration of the medical device. For example, the data associated with the sixth state of the medical device may indicate that the medical device (e.g., a syringe, etc.) has delivered a drug. In another example, the data associated with the sixth state of the medical device may indicate that a safety device of the medical device (e.g., a syringe and / or a catheter, etc.) has been activated. In another example, the data associated with the sixth state of the medical device may indicate that a sleeve (e.g., a foldable sleeve and / or a telescopic sleeve, etc.) of the medical device has been displaced so as to connect the medical device to a mating device.

[0191] In some non-limiting embodiments, the data associated with the sixth state of the medical device may indicate a decoupled configuration. For example, the data associated with the sixth state of the medical device may indicate a decoupled configuration of the medical device. For example, the data associated with the sixth state of the medical device may indicate that a first component of the medical device is not coupled to a second component of the medical device. In such an example, the data associated with the sixth state of the medical device may indicate that a first connector (e.g., a Luer connector, etc.) is not connected (e.g., secured) to a second connector, such as a connection between a needle-free syringe and an IV connector.

[0192] In some non-limiting embodiments, the data associated with the sixth state of the medical device may indicate a contaminated configuration. For example, the data associated with the sixth state of the medical device may indicate a contaminated configuration of the medical device. For example, the data associated with the sixth state of the medical device may indicate that a floating cannula of the medical device has been bumped or touched prior to connection (e.g., Luer attachment, etc.). In another example, the data associated with the sixth state of the medical device may indicate that a deformable element in a cannula of a medical device (e.g., a syringe, etc.) has been deformed.

[0193] In some non-limiting embodiments, the sixth signal provided by the RFID circuit 502 can include data associated with the indication of the sixth state of the packaging of the medical device. In some non-limiting embodiments, the data associated with the sixth state of the packaging of the medical device can indicate an unsealed configuration. For example, the data associated with the sixth state of the packaging of the medical device can indicate the unsealed configuration of the packaging of the medical device. In such an example, the data associated with the sixth state of the packaging of the medical device can indicate that packaging has been opened to remove the medical device from packaging. In another example, the data associated with the sixth state of the packaging of the medical device can indicate that the seal of the medicine in the packaging (e.g., medicine blister pack, etc.) has been destroyed.

[0194] refer to Figure 6 , Figure 6 is a schematic diagram of a medical device assembly 600. Figure 6 As shown, medical device assembly 600 includes an RFID tag 602 located on a container 650. In some non-limiting embodiments, RFID tag 602 can be attached to container 650 (e.g., by an adhesive, etc.). In some non-limiting embodiments, RFID tag 602 can be the same as RFID tag 400 and / or RFID tag 500.

[0195] In some non-limiting embodiments, the container 650 may have a suitable size based on the contents to be contained in the container 650 and the location where the container 650 is to be placed. In some non-limiting embodiments, the container 650 may have a suitable shape based on the contents to be contained in the container 650 and the location where the container 650 is to be placed. For example, the cross-section of the container 650 may be rectangular, square, circular and / or oval, etc. In some non-limiting embodiments, the container 650 may include a suitable material based on the contents to be contained in the container 650. For example, the material of the container 650 may include plastic and / or glass, etc. In some non-limiting embodiments, the container 650 may be configured to contain contents in the container 650. For example, the container 650 may be configured to contain solids and / or liquids in the container 650. In such an example, the container 650 may be configured to contain medicines in the container 650.

[0196] In some non-limiting embodiments, the container 650 may include a container body 652. In some non-limiting embodiments, the container body 652 may have a suitable size based on the contents to be contained in the container body 652 and the location where the container 650 is to be placed. In some non-limiting embodiments, the container body 652 may have a suitable shape based on the contents to be contained in the container body 652 and the location where the container 650 is to be placed. For example, the cross-section of the container body 652 may be rectangular, square, circular and / or oval, etc. In some non-limiting embodiments, the container body 652 includes a suitable material based on the contents to be contained in the container body 652. For example, the material of the container body 652 may include plastic and / or glass, etc.

[0197] In some non-limiting embodiments, the container 650 may include a closure 660. In some non-limiting embodiments, the closure 660 may include a cap, a top, and / or a seal, etc. In some non-limiting embodiments, the closure 660 may have a size suitable for coupling (e.g., fixing) to the container body 652. For example, the closure 660 may have a size proportional to the size of the container body 652. In some non-limiting embodiments, the closure 660 may have a shape suitable for fixing to the container body 652. For example, the shape of the cross-section of the closure 660 may be rectangular, square, circular, and / or oval, etc. In some non-limiting embodiments, the closure 660 may include a suitable material based on the application for which the container 650 is designed. For example, the material of the closure 660 may include plastic and / or glass, etc.

[0198] In some non-limiting embodiments, the closure 660 can be positioned over the opening of the container body 652. For example, the closure 660 can be coupled to (eg, attached to, sealed to, and / or otherwise coupled to, etc.) the opening of the container body 652.

[0199] In some non-limiting embodiments, the RFID tag 602 can be attached to the container 650. In some non-limiting embodiments, the RFID tag 602 can have a size that allows the RFID tag 602 to be attached to the container 650. In such examples, the size of the RFID tag 602 can be proportional to the size of the container 650. As another example, the RFID tag 602 can have a size sufficient to include individual components of the plurality of components of the RFID tag 602 to be positioned on the RFID tag 602.

[0200] In some non-limiting embodiments, the RFID tag 602 can have a shape that allows the RFID tag 602 to be attached to the container 650. In such examples, the RFID tag 602 can have a shape that corresponds to the container body 652 and / or the closure 660.

[0201] In some non-limiting embodiments, the RFID tag 602 may include an RFID circuit, an electronic component, and a base component 610. In some non-limiting embodiments, the base component 610 may include an attachment point 616 configured to allow the base component 610 to be separated into a first section and a second section.

[0202] In some non-limiting embodiments, the RFID tag 602 may include an RFID circuit. In some non-limiting embodiments, the RFID circuit may be the same as the RFID circuit 402. In some non-limiting embodiments, the RFID circuit may provide a signal based on the state of one or more components of the RFID tag 602. For example, the RFID circuit may provide a first signal when one or more components of the RFID tag 602 are in a first state, and may provide a second signal when one or more components of the RFID tag 602 are in a second state.

[0203] In some non-limiting embodiments, RFID tag 602 may include an electronic component. In some non-limiting embodiments, the electronic component may be the same as electronic component 404. In some non-limiting embodiments, the electronic component may include a first portion and a second portion. In some non-limiting embodiments, the first portion and the second portion of the electronic component may be the same as first portion 406 and second portion 408 of electronic component 404.

[0204] In some non-limiting embodiments, the base component 610 can be the same as the base component 410. In some non-limiting embodiments, the base component 610 can be positioned on the container 650. In some non-limiting embodiments, the base component 610 can be attached (e.g., by an adhesive, etc.) to the container 650. For example, the base component 610 can be attached to the container body 652 and / or the closure 660 of the container 650.

[0205] In some non-limiting embodiments, the base component 610 can include a first portion 612 and a second portion 614. In some non-limiting embodiments, the first portion 612 and the second portion 614 of the base component 610 can be the same as the first portion 412 and the second portion 414 of the base component 410. In some non-limiting embodiments, the first portion 612 of the base component 610 can be positioned on the container body 652. For example, the first portion 612 of the base component 610 can be attached to the container body 652 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the first portion 612 of the base component 610 can be positioned on the closure 660. For example, the first portion 612 of the base component 610 can be attached to the closure 660 (e.g., by an adhesive, etc.).

[0206] In some non-limiting embodiments, the second portion 614 of the base component 610 can be located on the container body 652. For example, the second portion 614 of the base component 610 can be attached to the container body 652 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the second portion 614 of the base component 610 can be located on the closure 660. For example, the second portion 614 of the base component 610 can be attached to the closure 660 (e.g., by an adhesive, etc.).

[0207] In some non-limiting embodiments, the base component 610 can include an attachment point 616 that separates the first portion 612 of the base component 610 from the second portion 614 of the base component 610. In some non-limiting embodiments, the attachment point 616 can be the same as the attachment point 416. In some non-limiting embodiments, the attachment point 616 can be located at a gap between the closure 660 and the container body 652. For example, the attachment point 616 can bridge the gap between the closure 660 and the container body 652.

[0208] In some non-limiting embodiments, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be coupled together. For example, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the electronic component is in the first state, the first portion 612 and the second portion 614 of the base component 610 can be coupled together, such that the first portion and the second portion of the electronic component are coupled together. For example, when the electronic component is in the first state, the closure 660 can be coupled to (e.g., attached to and / or otherwise coupled to) the container body 652, such that the first portion 612 and the second portion 614 of the base component 610 can be coupled together, and the first portion and the second portion of the electronic component are coupled together.

[0209] In some non-limiting embodiments, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be recoupled after being previously decoupled. For example, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be recoupled electrically (e.g., re-conductively coupled) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component is in the first state, the first portion 612 and the second portion 614 of the base component 610 can be recoupled after being previously decoupled, such that the first portion and the second portion of the electronic component are recoupled after being previously decoupled. For example, when the electronic component is in the first state, the closure 660 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the container body 652 after being previously removed from the container body 652, such that the first portion 612 and the second portion 614 of the base component 610 can be recoupled together, and the first portion and the second portion of the electronic component are recoupled together. In some non-limiting embodiments, the first portion and the second portion of the electronic component can be decoupled and then recoupled to change the state of the electronic component from a first state to a second state and back to the first state, and to change the signal provided by the RFID circuit from a first signal to a second signal and back to the first signal any number of times.

[0210] In some non-limiting embodiments, when the electronic component is in the first state, the RFID circuit can be configured to provide a first signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit can include data associated with an indication of the first state of the container 650. In some non-limiting embodiments, the data associated with the first state of the container 650 can indicate a closed configuration. For example, the data associated with the first state of the container 650 can indicate a closed configuration of the container 650. In such an example, the data associated with the first state of the container 650 can indicate that the closure 660 is coupled to (e.g., attached to and / or otherwise coupled to) the container body 652.

[0211] In some non-limiting embodiments, when the electronic component is in the second state, the first portion and the second portion of the electronic component can be decoupled. For example, when the electronic component is in the second state, the first portion and the second portion of the electronic component can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the electronic component is in the second state, the first portion 612 of the base component 610 can be decoupled from the second portion 614 of the base component 610 at the attachment point 616, such that the first portion and the second portion of the electronic component are decoupled. For example, the first portion 612 of the base component 610 can be decoupled from the second portion 614 of the base component 610 at the attachment point 616, such that a gap exists between the first portion 612 and the second portion 614 of the base component 610, wherein the gap is wide enough such that the first portion and the second portion of the electronic component are not electrically coupled. For example, the closure 660 can be decoupled from the container body 652 (e.g., detached from the container body 652, etc.), so that the first portion 612 and the second portion 614 of the base component 610 can be decoupled, and when the electronic component is in the second state, the first portion and the second portion of the electronic component can be decoupled. In some non-limiting embodiments, when the electronic component is in the second state, the RFID circuit can be configured to provide a second signal, such as during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit.

[0212] In some non-limiting embodiments, the second signal provided by the RFID circuit may include data associated with an indication of a second state of the container 650. In some non-limiting embodiments, the data associated with the second state of the container 650 may indicate an open configuration. For example, the data associated with the second state of the container 650 may indicate an open configuration of the container 650. In such an example, the data associated with the second state of the container 650 may indicate that the closure 660 has been decoupled from the container body 652 (detached from the container body 652, etc.).

[0213] In some non-limiting embodiments, when the electronic component is in the third state, the first portion and the second portion of the electronic component can be recoupled after being previously decoupled. For example, when the electronic component is in the third state, the first portion and the second portion of the electronic component can be recoupled electrically (e.g., re-conductively coupled) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component is in the third state, the first portion 612 and the second portion 614 of the base component 610 can be recoupled after being previously decoupled, so that the first portion and the second portion of the electronic component are recoupled after being previously decoupled. For example, when the electronic component is in the third state, the closure 660 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the container body 652 after being previously detached from the container body 652, so that the first portion 612 and the second portion 614 of the base component 610 can be recoupled together, and the first portion and the second portion of the electronic component are recoupled together. In some non-limiting embodiments, the first portion and the second portion of the electronic component can be decoupled and then recoupled to change the state of the electronic component from a first state to a second state to a third state, and to change the signal provided by the RFID circuit from a first signal to a second signal to a third signal any number of times to provide any number of signals.

[0214] In some non-limiting embodiments, when the electronic component is in the third state, the RFID circuit can be configured to provide a third signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit and the second signal provided by the RFID circuit. In some non-limiting embodiments, the third signal provided by the RFID circuit can include data associated with an indication of the third state of the container 650. In some non-limiting embodiments, the data associated with the third state of the container 650 can indicate a re-closing configuration. For example, the data associated with the third state of the container 650 can indicate a re-closing configuration of the container 650. In such an example, the data associated with the third state of the container 650 can indicate that the closure 660 has been re-coupled to (e.g., reattached to and / or otherwise coupled to) the container body 652 after the closure 660 has previously been decoupled from the container body 652 (e.g., detached from the container body 652, etc.).

[0215] refer to Figure 7 , Figure 7 is a schematic diagram of a medical device assembly 700. Figure 7As shown, medical device assembly 700 includes an RFID tag 702 positioned on a syringe 750. In some non-limiting embodiments, RFID tag 702 can be attached to syringe 750 (e.g., by an adhesive, etc.). In some non-limiting embodiments, RFID tag 702 can be the same as RFID tag 400 or RFID tag 500.

[0216] In some non-limiting embodiments, the syringe 750 can have an appropriate size based on the application for which the syringe 750 is designed. In some non-limiting embodiments, the syringe 750 can have an appropriate shape based on the application for which the syringe 750 is designed. In some non-limiting embodiments, the syringe 750 can include an appropriate material based on the application for which the syringe 750 is designed and the desired contents to be contained within the syringe 750.

[0217] In some non-limiting embodiments, syringe 750 can include a syringe body 752. In some non-limiting embodiments, syringe body 752 can be sized appropriately based on the contents to be contained within syringe body 752 and the application for which syringe 750 is designed.

[0218] In some non-limiting embodiments, the syringe 750 may include a plunger 762. In some non-limiting embodiments, the plunger 762 may have a suitable size based on the application for which the syringe 750 is designed. For example, the plunger 762 may have a size corresponding to the size of the internal volume of the syringe body 752. In some non-limiting embodiments, the plunger 762 may have a suitable shape based on the application for which the syringe 750 is designed. For example, the plunger 762 may have a shape corresponding to the shape of the internal volume of the syringe body 752. In some non-limiting embodiments, the plunger 762 may include a suitable material based on the application for which the syringe 750 is designed. In some non-limiting embodiments, the plunger 762 may be configured to be inserted into the internal volume of the syringe body 752 through the opening.

[0219] In some non-limiting embodiments, the syringe 750 may include a closure 770. In some non-limiting embodiments, the closure 770 may be a cap, a top and / or a seal, etc. In some non-limiting embodiments, the closure 770 may have a suitable size based on the application for which the syringe 750 is designed. For example, the closure 770 may have a size proportional to the size of the syringe body 752. In some non-limiting embodiments, the closure 770 may have a suitable shape based on the application for which the syringe 750 is designed. For example, the closure 770 may have a shape corresponding to the shape of the syringe body 752. In some non-limiting embodiments, the closure 770 may be positioned at one end of the syringe body 752. For example, the closure 770 may be configured to be attached to the syringe body 752 (e.g., by threaded connection and / or Luer attachment, etc.).

[0220] In some non-limiting embodiments, the RFID tag 702 can be attached to the syringe 750. In some non-limiting embodiments, the RFID tag 702 can have a size that allows the RFID tag 702 to be attached to the syringe 750. In such examples, the size of the RFID tag 702 can be proportional to the size of the syringe 750. In some non-limiting embodiments, the RFID tag 702 can have a shape that allows the RFID tag 702 to be attached to the syringe 750. In such examples, the RFID tag 702 can have a shape that corresponds to the syringe body 752 and / or the closure 770. As another example, the RFID tag 702 can have a shape sufficient to include individual components of the plurality of components of the RFID tag 702 to be positioned on the RFID tag 702.

[0221] In some non-limiting embodiments, RFID tag 702 may include RFID circuitry, electronic components, and base component 710. In some non-limiting embodiments, base component 710 may include attachment points 716 configured to allow base component 710 to be separated into a first section and a second section.

[0222] In some non-limiting embodiments, the RFID tag 702 may include an RFID circuit. In some non-limiting embodiments, the RFID circuit may be the same as the RFID circuit 402. In some non-limiting embodiments, the RFID circuit may provide a signal based on the state of one or more components of the RFID tag 702. For example, the RFID circuit may provide a first signal when one or more components of the RFID tag 702 are in a first state, and may provide a second signal when one or more components of the RFID tag 702 are in a second state.

[0223] In some non-limiting embodiments, the electronic component can be the same as electronic component 404. In some non-limiting embodiments, the electronic component can include a first portion and a second portion. In some non-limiting embodiments, the first portion and the second portion of the electronic component can be the same as first portion 406 and second portion 408 of electronic component 404.

[0224] In some non-limiting embodiments, the base component 710 can be the same as the base component 410. In some non-limiting embodiments, the base component 710 can be positioned on the syringe 750. In some non-limiting embodiments, the base component 710 can be attached to the syringe 750 (e.g., by an adhesive, etc.). For example, the base component 710 can be attached to the syringe body 752 and / or the closure 770. As another example, the base component 710 can be attached to the syringe body 752 and / or the plunger 762.

[0225] In some non-limiting embodiments, base component 710 can include first portion 712 and second portion 714. In some non-limiting embodiments, first portion 712 and second portion 714 of base component 710 can be the same as first portion 412 and second portion 414 of base component 410.

[0226] In some non-limiting embodiments, the first portion 712 of the base component 710 can be positioned on the syringe body 752. For example, the first portion 712 of the base component 710 can be attached to the syringe body 752 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the first portion 712 of the base component 710 can be positioned on the closure 770. For example, the first portion 712 of the base component 710 can be attached to the closure 770 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the first portion 712 of the base component 710 can be positioned on the plunger 762. For example, the first portion 712 of the base component 710 can be attached to the plunger 762 (e.g., by an adhesive, etc.).

[0227] In some non-limiting embodiments, the second portion 714 of the base component 710 can be positioned on the syringe body 752. For example, the second portion 714 of the base component 710 can be attached to the syringe body 752 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the second portion 714 of the base component 710 can be positioned on the closure 770. For example, the second portion 714 of the base component 710 can be attached to the closure 770 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the second portion 714 of the base component 710 can be positioned on the plunger 762. For example, the second portion 714 of the base component 710 can be attached to the plunger 762 (e.g., by an adhesive, etc.).

[0228] In some non-limiting embodiments, the base component 710 can include an attachment point 716 that separates the first portion 712 of the base component 710 from the second portion 714 of the base component 710. In some non-limiting embodiments, the attachment point 716 can be the same as the attachment point 416. In some non-limiting embodiments, the attachment point 716 can be positioned at a gap between the closure 770 and the syringe body 752. For example, the attachment point 716 can bridge the gap between the closure 770 and the syringe body 752. In some non-limiting embodiments, the attachment point 716 can be positioned at a gap between the plunger 762 and the syringe body 752. For example, the attachment point 716 can bridge the gap between the plunger 762 and the syringe body 752.

[0229] In some non-limiting embodiments, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be coupled together. For example, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the electronic component is in the first state, the first portion 712 and the second portion 714 of the base component 710 can be coupled together, so that the first portion and the second portion of the electronic component are coupled together. For example, when the electronic component is in the first state, the closure 770 can be coupled to (e.g., attached to and / or otherwise coupled to) the syringe body 752, so that the first portion 712 and the second portion 714 of the base component 710 can be coupled together, and the first portion and the second portion of the electronic component are coupled together. As another example, the plunger 762 can be in an unused position relative to the syringe body 752, so that when the electronic component is in the first state, the first portion 712 and the second portion 714 of the base component 710 can be coupled together, and the first portion and the second portion of the electronic component are coupled together.

[0230] In some non-limiting embodiments, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be recoupled after being previously decoupled. For example, when the electronic component is in the first state, the first portion and the second portion of the electronic component can be recoupled electrically (e.g., re-conductively coupled) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component is in the first state, the first portion 712 and the second portion 714 of the base component 710 can be recoupled after being previously decoupled, such that the first portion and the second portion of the electronic component are recoupled after being previously decoupled. For example, when the electronic component is in the first state, the closure 770 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the syringe body 752 after being previously removed from the syringe body 752, such that the first portion 712 and the second portion 714 of the base component 710 can be recoupled together, and the first portion and the second portion of the electronic component are recoupled together. As another example, when the electronic component is in the first state, the plunger 762 can be in a reuse position relative to the syringe body 752 after being previously in the use position, so that the first portion 712 and the second portion 714 of the base component 710 can be recoupled together and the first portion and the second portion of the electronic component can be recoupled together. In some non-limiting embodiments, the first portion and the second portion of the electronic component can be decoupled and then recoupled to change the state of the electronic component from the first state to the second state and back to the first state, and change the signal provided by the RFID circuit from the first signal to the second signal and back to the first signal any number of times.

[0231] In some non-limiting embodiments, when the electronic component is in the first state, the RFID circuit can be configured to provide a first signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit can include data associated with an indication of the first state of the syringe 750. In some non-limiting embodiments, the data associated with the first state of the syringe 750 can indicate a closed configuration. For example, the data associated with the first state of the syringe 750 can indicate a closed configuration of the syringe 750. In such an example, the data associated with the first state of the syringe 750 can indicate that the closure 770 is coupled to (e.g., attached to and / or otherwise coupled to) the syringe body 752.

[0232] In some non-limiting embodiments, the data associated with the first state of the syringe 750 may indicate an unused configuration. For example, the data associated with the first state of the syringe 750 may indicate an unused configuration of the syringe 750. In such an example, the data associated with the first state of the syringe 750 may indicate that the plunger 762 is in an unused position relative to the syringe body 752 (e.g., the plunger 762 has not yet been pushed into the interior volume of the syringe body 752).

[0233] In some non-limiting embodiments, when the electronic component is in the second state, the first portion and the second portion of the electronic component can be decoupled. For example, when the electronic component is in the second state, the first portion and the second portion of the electronic component can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the electronic component is in the second state, the first portion 712 of the base component 710 can be decoupled from the second portion 714 of the base component 710 at the attachment point 716, such that the first portion and the second portion of the electronic component are decoupled. For example, the first portion 712 of the base component 710 can be decoupled from the second portion 714 of the base component 710 at the attachment point 716, such that a gap exists between the first portion 712 and the second portion 714 of the base component 710, wherein the gap is wide enough such that the first portion and the second portion of the electronic component are not electrically coupled. For example, when the electronic component is in the second state, the closure 770 can be decoupled from the syringe body 752 (e.g., detached from the syringe body 752, etc.), such that the first portion 712 and the second portion 714 of the base component 710 can be decoupled, and the first portion and the second portion of the electronic component can be decoupled. As another example, when the electronic component is in the second state, the plunger 762 can be in a use position relative to the syringe body 752, such that the first portion 712 and the second portion 714 of the base component 710 can be decoupled, and the first portion and the second portion of the electronic component can be decoupled. In some non-limiting embodiments, when the electronic component is in the second state, the RFID circuit can be configured to provide a second signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit.

[0234] In some non-limiting embodiments, the second signal provided by the RFID circuit may include data associated with an indication of a second state of the syringe 750. In some non-limiting embodiments, the data associated with the second state of the syringe 750 may indicate an open configuration. For example, the data associated with the second state of the syringe 750 may indicate an open configuration of the syringe 750. In such an example, the data associated with the second state of the syringe 750 may indicate that the closure 770 has been decoupled from the syringe body 752 (e.g., detached from the syringe body 752, etc.).

[0235] In some non-limiting embodiments, the data associated with the second state of the syringe 750 may indicate a use configuration. For example, the data associated with the second state of the syringe 750 may indicate a use configuration of the syringe 750. In such an example, the data associated with the second state of the syringe 750 may indicate that the plunger 762 is in a use position relative to the syringe body 752 (e.g., the plunger 762 has been pushed into the interior volume of the syringe body 752).

[0236] In some non-limiting embodiments, when the electronic component is in the third state, the first portion and the second portion of the electronic component can be recoupled after being previously decoupled. For example, when the electronic component is in the third state, the first portion and the second portion of the electronic component can be recoupled electrically (e.g., re-conductively coupled) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component is in the third state, the first portion 712 and the second portion 714 of the base component 710 can be recoupled after being previously decoupled, such that the first portion and the second portion of the electronic component are recoupled after being previously decoupled. For example, when the electronic component is in the third state, the closure 770 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the syringe body 752 after being previously removed from the syringe body 752, such that the first portion 712 and the second portion 714 of the base component 710 can be recoupled together, and the first portion and the second portion of the electronic component are recoupled together. In some non-limiting embodiments, the first portion and the second portion of the electronic component can be decoupled and then recoupled to change the state of the electronic component from a first state to a second state to a third state, and to change the signal provided by the RFID circuit from a first signal to a second signal to a third signal any number of times to provide any number of signals.

[0237] In some non-limiting embodiments, when the electronic component is in the third state, the RFID circuit can be configured to provide a third signal, for example, during an interrogation by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit and the second signal provided by the RFID circuit. In some non-limiting embodiments, the third signal provided by the RFID circuit can include data associated with an indication of the third state of the syringe 750. In some non-limiting embodiments, the data associated with the third state of the syringe 750 can indicate a re-closing configuration. For example, the data associated with the third state of the syringe 750 can indicate a re-closing configuration of the syringe 750. In such an example, the data associated with the third state of the syringe 750 can indicate that the closure 770 has been recoupled to (e.g., reattached to and / or otherwise coupled to) the syringe body 752 after the closure 770 has previously been removed from the syringe body 752.

[0238] In some non-limiting embodiments, the data associated with the third state of the syringe 750 may indicate a reuse configuration. For example, the data associated with the third state of the syringe 750 may indicate a reuse configuration of the syringe 750. In such an example, the data associated with the third state of the syringe 750 may indicate that the plunger 762 is in a reuse position relative to the syringe body 752 (e.g., the plunger 762 has been pulled out of the interior volume of the syringe body 752 after previously being pushed into the interior volume of the syringe body 752).

[0239] refer to Figure 8 , Figure 8 is a schematic diagram of a medical device assembly 800. Figure 8 As shown, medical device assembly 800 includes an RFID tag 802 positioned on and / or between syringe 850 and IV connector 870. For example, RFID tag 802 can be attached to syringe 850 and / or IV connector 870. In some non-limiting embodiments, RFID tag 802 can be the same as RFID tag 400 or RFID tag 500.

[0240] In some non-limiting embodiments, the syringe 850 can have an appropriate size based on the application for which the syringe 850 is designed. In some non-limiting embodiments, the syringe 850 can have an appropriate shape based on the application for which the syringe 850 is designed. In some non-limiting embodiments, the syringe 850 can include an appropriate material based on the application for which the syringe 850 is designed and the desired contents to be contained within the syringe 850.

[0241] In some non-limiting embodiments, the syringe 850 may include a syringe body 852. In some non-limiting embodiments, the syringe body 852 may have an appropriate size based on the contents to be contained in the syringe body 852 and the application for which the syringe 850 is designed. In some non-limiting embodiments, the syringe body 852 may have an appropriate shape based on the contents to be contained in the syringe body 852 and the application for which the syringe 850 is designed. For example, the cross-section of the syringe body 852 may be circular, oval, rectangular, and / or square, etc. In some non-limiting embodiments, the syringe body 852 may include an appropriate material based on the contents to be contained in the syringe body 852.

[0242] In some non-limiting embodiments, the syringe body 852 can include a connection tip 854 at one end. In some non-limiting embodiments, the connection tip 854 of the syringe body 852 can be threaded. In some non-limiting embodiments, the connection tip 854 of the syringe body 852 can include a Luer connector. In some non-limiting embodiments, the connection tip 854 of the syringe body 852 can be configured to attach to a connector (e.g., an IV connector 870).

[0243] In some non-limiting embodiments, the IV assembly can include an IV connector 870. In some non-limiting embodiments, the IV connector 870 can have an appropriate size based on the application for which the IV connector 870 is designed. In some non-limiting embodiments, the IV connector 870 can have an appropriate shape based on the application for which the IV connector 870 is designed. In some non-limiting embodiments, the IV connector 870 can include an appropriate material based on the application for which the IV connector 870 is designed.

[0244] In some non-limiting embodiments, the IV connector 870 can include a connector body 872. In some non-limiting embodiments, the connector body 872 can have an appropriate size based on the contents to be contained within the connector body 872 and the application for which the IV connector 870 is designed. In some non-limiting embodiments, the connector body 872 can have an appropriate shape based on the application for which the IV connector 870 is designed. For example, the cross-section of the connector body 872 can be circular, oval, rectangular, and / or square, etc. In some non-limiting embodiments, the connector body 872 can include an appropriate material based on the contents to be contained within the connector body 872.

[0245] In some non-limiting embodiments, the connector body 872 can include a connection end 880 at an end of the connector body 872. In some non-limiting embodiments, the connection end 880 of the connector body 872 can be threaded. In some non-limiting embodiments, the connection end 880 of the connector body 872 can include a Luer connector. In some non-limiting embodiments, the connection end 880 of the connector body 872 can be configured to couple to the connection end 854 of the syringe body 852. For example, the connection end 880 of the connector body 872 can be configured to connect to the connection end 854 of the syringe body 852 (e.g., by threaded attachment and / or Luer attachment, etc.).

[0246] In some non-limiting embodiments, the RFID tag 802 can be attached to the syringe 850 and / or the IV connector 870. In some non-limiting embodiments, the RFID tag 802 can have a size that allows the RFID tag 802 to be attached to the syringe 850 and / or the IV connector 870. In such examples, the size of the RFID tag 802 can be proportional to the size of the syringe 850 and / or the IV connector 870.

[0247] In some non-limiting embodiments, the RFID tag 802 can have a shape that allows the RFID tag 802 to be positioned between (e.g., attached to) the syringe 850 and the IV connector 870, etc. In such an example, the RFID tag 802 can have a shape corresponding to the IV connector 870 and / or the syringe 850.

[0248] In some non-limiting embodiments, RFID tag 802 may include an RFID circuit, an electronic component 804 , and a base component 810 .

[0249] In some non-limiting embodiments, the RFID tag 802 may include an RFID circuit. In some non-limiting embodiments, the RFID circuit may be the same as the RFID circuit 402. In some non-limiting embodiments, the RFID circuit may provide a signal based on the state of one or more components of the RFID tag 802. For example, the RFID circuit may provide a first signal when one or more components of the RFID tag 802 are in a first state, and may provide a second signal when one or more components of the RFID tag 802 are in a second state.

[0250] In some non-limiting embodiments, the electronic component 804 can be the same as the electronic component 404. In some non-limiting embodiments, the electronic component 804 can include a first portion 806 and a second portion 808. In some non-limiting embodiments, the first portion 806 of the electronic component 804 can be a first conductive tab 806, and the second portion 808 of the electronic component 804 can be a second conductive tab 808. In some non-limiting embodiments, the first conductive tab 806 and the second conductive tab 808 of the electronic component 804 can be separated by a gap 818. In some non-limiting embodiments, the first conductive tab 806 and the second conductive tab 808 of the electronic component 804 can be separated by a gap 818 having a sufficient width such that the first conductive tab 806 and the second conductive tab 808 of the electronic component 804 are decoupled. For example, the first conductive tab 806 and the second conductive tab 808 of the electronic component 804 can be separated by a gap 818 having a sufficient width such that the first conductive tab 806 and the second conductive tab 808 of the electronic component 804 are not electrically connected. In some non-limiting embodiments, the first portion 806 and the second portion 808 of the electronic component 804 (e.g., the first conductive tab 806 and the second conductive tab 808) can be the same as the first portion 406 and the second portion 408 of the electronic component 404. In some non-limiting embodiments, the first portion 806 and the second portion 808 of the electronic component 804 can be separable based on one or more mechanical components. For example, the first portion 806 and the second portion 808 of the electronic component 804 can be separable based on the disconnection of the syringe 850 and the IV connector 870. In some non-limiting embodiments, the first portion 806 of the electronic component 804 can be connected (e.g., electrically connected) to the RFID circuit.

[0251] In some non-limiting embodiments, base component 810 can be the same as base component 410. In some non-limiting embodiments, base component 810 can be located on and / or between syringe 850 and IV connector 870. In some non-limiting embodiments, base component 810 can be attached to syringe 850 and / or IV connector 870 (e.g., by an adhesive, etc.).

[0252] In some non-limiting embodiments, base component 810 can include first portion 812 and second portion 814. In some non-limiting embodiments, first portion 812 and second portion 814 of base component 810 can be the same as first portion 412 and second portion 414 of base component 410.

[0253] In some non-limiting embodiments, the first portion 812 of the base component 810 can be positioned on the IV connector 870. For example, the first portion 812 of the base component 810 can be attached (e.g., by an adhesive, etc.) to the IV connector 870. In some non-limiting embodiments, the first portion 812 of the base component 810 can be positioned on the syringe 850. For example, the first portion 812 of the base component 810 can be attached (e.g., by an adhesive, etc.) to the syringe 850.

[0254] In some non-limiting embodiments, the second portion 814 of the base component 810 can be positioned on the IV connector 870. For example, the second portion 814 of the base component 810 can be attached (e.g., by an adhesive, etc.) to the IV connector 870. In some non-limiting embodiments, the second portion 814 of the base component 810 can be positioned on the syringe 850. For example, the second portion 814 of the base component 810 can be attached (e.g., by an adhesive, etc.) to the syringe 850.

[0255] In some non-limiting embodiments, a portion of the first portion 812 and the second portion 814 of the base component 810 may be substantially connected, while another portion of the first portion 812 and the second portion 814 of the base component 810 may be separated by a gap 818 .

[0256] In some non-limiting embodiments, when the electronic component 804 is in the first state, the first portion 806 and the second portion 808 of the electronic component 804 can be coupled together. For example, when the electronic component 804 is in the first state, the first portion 806 and the second portion 808 of the electronic component 804 can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the electronic component 804 is in the first state, the first portion 812 and the second portion 814 of the base component 810 can be coupled together, such that the first portion 806 and the second portion 808 of the electronic component 804 are coupled together. For example, when the electronic component 804 is in the first state, the syringe 850 can be coupled to (e.g., attached to and / or otherwise coupled to) the IV connector 870, such that the first portion 812 and the second portion 814 of the base component 810 can be coupled together, and the first portion 806 and the second portion 808 of the electronic component 804 are coupled together.

[0257] In some non-limiting embodiments, when the electronic component 804 is in the first state, the first portion 806 and the second portion 808 of the electronic component 804 may be recoupled after being previously decoupled. For example, when the electronic component 804 is in the first state, the first portion 806 and the second portion 808 of the electronic component 804 may be recoupled electrically (e.g., recoupled conductively) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component 804 is in the first state, the first portion 812 and the second portion 814 of the base component 810 may be recoupled after being previously decoupled, so that the first portion 806 and the second portion 808 of the electronic component 804 are recoupled after being previously decoupled. For example, when the electronic component 804 is in the first state, the syringe 850 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the IV connector 870 after previously being decoupled from (e.g., detached from the IV connector 870, etc.), so that the first portion 812 and the second portion 814 of the base component 810 can be recoupled together, and the first portion 806 and the second portion 808 of the electronic component 804 can be recoupled together. In some non-limiting embodiments, the first portion 806 and the second portion 808 of the electronic component 804 can be decoupled and then recoupled to change the state of the electronic component 804 from the first state to the second state and back to the first state, and change the signal provided by the RFID circuit from the first signal to the second signal and back to the first signal any number of times.

[0258] In some non-limiting embodiments, when the electronic component 804 is in the first state, the RFID circuit can be configured to provide a first signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit can include data associated with an indication of a first state of the syringe 850 and / or the IV connector 870. For example, the data associated with the first state of the syringe 850 and / or the IV connector 870 can indicate a coupling configuration. For example, the data associated with the first state of the syringe 850 and / or the IV connector 870 can indicate a coupling configuration of the syringe 850 and / or the IV connector 870. For example, the data associated with the first state of the syringe 850 and / or the IV connector 870 can indicate that the syringe 850 is coupled to the IV connector 870. In such an example, the data associated with the first state of the syringe 850 and / or the IV connector 870 can indicate that the connection end 854 of the syringe body 852 (e.g., by a threaded coupling and / or a Luer connector, etc.) is connected to the connection end 880 of the connector body 872 (e.g., by a threaded coupling and / or a Luer connector, etc.).

[0259] In some non-limiting embodiments, when the electronic component 804 is in the second state, the first portion 806 and the second portion 808 of the electronic component 804 can be decoupled. For example, when the electronic component 804 is in the second state, the first portion 806 and the second portion 808 of the electronic component 804 can be not electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the electronic component 804 is in the second state, the first portion 812 of the base component 810 can be decoupled from the second portion 814 of the base component 810, such that the first portion 806 and the second portion 808 of the electronic component 804 are decoupled. For example, the first portion 812 of the base component 810 can be decoupled from the second portion 814 of the base component 810, such that a gap 818 exists between the first portion 812 and the second portion 814 of the base component 810, wherein the gap 818 is wide enough such that the first portion 806 and the second portion 808 of the electronic component 804 are not electrically coupled. For example, when the electronic component 804 is in the second state, the syringe 850 can be decoupled from the IV connector 870 (e.g., detached from the IV connector 870, etc.), so that the first portion 812 and the second portion 814 of the base component 810 can be decoupled, and the first portion 806 and the second portion 808 of the electronic component 804 can be decoupled. In some non-limiting embodiments, when the electronic component 804 is in the second state, the RFID circuit can be configured to provide a second signal, such as during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit.

[0260] In some non-limiting embodiments, the second signal provided by the RFID circuit may include data associated with an indication of a second state of the syringe 850 and / or the IV connector 870. In some non-limiting embodiments, the data associated with the second state of the syringe 850 and / or the IV connector 870 may indicate a decoupled configuration. For example, the data associated with the second state of the syringe 850 and / or the IV connector 870 may indicate a decoupled configuration of the syringe 850 and the IV connector 870. For example, the data associated with the second state of the syringe 850 and / or the IV connector 870 may indicate that the syringe 850 is decoupled from the IV connector 870 (e.g., the syringe 850 is disengaged from the IV connector 870, etc.). In such an example, the data associated with the second state of the syringe 850 and / or the IV connector 870 may indicate that the connection end 854 of the syringe body 852 (e.g., by disconnecting a threaded coupling and / or a luer connector, etc.) is not connected to the connection end 880 of the connector body 872 (e.g., by disconnecting a threaded coupling and / or a luer connector, etc.).

[0261] In some non-limiting embodiments, when the electronic component 804 is in the third state, the first portion 806 and the second portion 808 of the electronic component 804 may be recoupled after being previously decoupled. For example, when the electronic component 804 is in the third state, the first portion 806 and the second portion 808 of the electronic component 804 may be recoupled electrically (e.g., recoupled conductively) after being previously electrically decoupled (e.g., conductively decoupled). In some non-limiting embodiments, when the electronic component 804 is in the third state, the first portion 812 and the second portion 814 of the base component 810 may be recoupled after being previously decoupled, so that the first portion 806 and the second portion 808 of the electronic component 804 are recoupled after being previously decoupled. For example, when the electronic component 804 is in the third state, the syringe 850 can be recoupled to (e.g., reattached to and / or otherwise coupled to) the IV connector 870 after being previously decoupled from (e.g., detached from the IV connector 870, etc.), so that the first portion 812 and the second portion 814 of the base component 810 can be recoupled together, and the first portion 806 and the second portion 808 of the electronic component 804 can be recoupled together. In some non-limiting embodiments, the first portion 806 and the second portion 808 of the electronic component 804 can be decoupled and then recoupled to change the state of the electronic component 804 from the first state to the second state and then to the third state, and change the signal provided by the RFID circuit from the first signal to the second signal and then to the third signal any number of times to provide any number of signals.

[0262] In some non-limiting embodiments, when the electronic component 804 is in the third state, the RFID circuit can be configured to provide a third signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit can be different from the first signal provided by the RFID circuit and the second signal provided by the RFID circuit. In some non-limiting embodiments, the third signal provided by the RFID circuit can include data associated with an indication of the third state of the syringe 850 and / or the IV connector 870. In some non-limiting embodiments, the data associated with the third state of the syringe 850 and / or the IV connector 870 can indicate a re-coupling configuration. For example, the data associated with the third state of the syringe 850 and / or the IV connector 870 can indicate a re-coupling configuration of the syringe 850 and the IV connector 870. In such an example, data associated with the third state of the syringe 850 and / or IV connector 870 may indicate that the connection end 854 of the syringe body 852 (e.g., via a threaded connection and / or a luer connector, etc.) has been recoupled (e.g., reattached and / or otherwise coupled to) the connection end 880 of the connector body 872 (e.g., via a threaded connection and / or a luer connector, etc.) after being previously decoupled (e.g., detached, etc.).

[0263] refer to Fig. 9 , Fig. 9 is a schematic diagram of medical device assembly 950. Fig. 9 As shown, medical device assembly 950 includes RFID tag 900 positioned on medication package 952. In some non-limiting embodiments, RFID tag 900 can be attached to medication package 952 (e.g., by an adhesive, etc.). In some non-limiting embodiments, RFID tag 900 can be the same as RFID tag 400 or RFID tag 500.

[0264] In some non-limiting embodiments, the drug package 952 can have a suitable size based on the application for which the drug package 952 is designed. For example, the drug package 952 can have a size sufficient to contain the drug 956 therein. In some non-limiting embodiments, the drug package 952 can have a suitable shape based on the application for which the drug package 952 is designed. In some non-limiting embodiments, the drug package 952 can include a suitable material based on the application for which the drug package 952 is designed. For example, the material of the drug package 952 can include plastic and / or metal, etc. In some non-limiting embodiments, the drug package 952 can be a drug blister package 952.

[0265] In some non-limiting embodiments, the drug package 952 may include a drug mesh 954a. In some non-limiting embodiments, the drug mesh 954a may be positioned on the drug package 952. For example, the drug mesh 954a may be substantially attached to the drug package 952. In some non-limiting embodiments, the drug mesh 954a may be sealed by the drug package 952. In some non-limiting embodiments, the drug mesh 954a may have a suitable size based on the application for which the drug package 952 is designed. For example, the drug mesh 954a may have a size such that the drug 956 may be positioned in the drug mesh 954a. In some non-limiting embodiments, the drug mesh 954a may have a suitable shape based on the application for which the drug package 952 is designed. For example, the drug mesh 954a may have a shape such that the drug 956 may be positioned in the drug mesh 956. In some non-limiting embodiments, the drug mesh 954a can include suitable materials based on the application for which the drug package 952 is designed. For example, the drug mesh 954a can include materials based on the drug 956 contained within the drug mesh 954a. For example, the drug mesh 954a can include plastic.

[0266] In some non-limiting embodiments, the drug package 952 can include a drug 956. For example, the drug 956 can be contained within the drug web 954a (e.g., sealed within the drug web 954a by the drug package 952). In some non-limiting embodiments, the drug package 952 can include a plurality of drug webs 954a, 954b, wherein the drug 956 is positioned within each of the plurality of drug webs 954a, 954b.

[0267] In some non-limiting embodiments, the RFID tag 900 can be attached to the medication package 952 (e.g., by an adhesive, etc.). In some non-limiting embodiments, the RFID tag 900 can have a size that allows the RFID tag 900 to be attached to the medication package 952. In such examples, the RFID tag 900 can have a size that is proportional to the size of the medication package 952. In some non-limiting embodiments, the RFID tag 900 can have a shape that allows the RFID tag 900 to be attached to the medication package 952.

[0268] In some non-limiting embodiments, the RFID tag 900 may include an RFID circuit 902, a plurality of electronic components 904a, 904b, and a base component 910. In some non-limiting embodiments, the base component 910 may include a plurality of attachment points 916a, 916b, each of the plurality of attachment points being positioned on a drug mesh 954a, 954b, and each of the attachment points 916a, 916b being configured to allow the base component 910 to be pierced, e.g., to open the drug mesh 954a, 954b to allow the drug 956 to be removed from the drug mesh 954a, 954b.

[0269] In some non-limiting embodiments, the RFID tag 900 may include an RFID circuit 902. In some non-limiting embodiments, the RFID circuit 902 may be the same as the RFID circuit 402. In some non-limiting embodiments, the RFID circuit 902 may provide a signal based on the state of one or more components of the RFID tag 900. For example, the RFID circuit 902 may provide a first signal when one or more components of the RFID tag 900 are in a first state, and the RFID circuit 402 may provide a second signal when one or more components of the RFID tag 900 are in a second state.

[0270] In some non-limiting embodiments, the plurality of electronic components 904a, 904b may include a first electronic component 904a. In some non-limiting embodiments, the first electronic component 904a may be the same as the electronic component 404. In some non-limiting embodiments, the first electronic component 904a may have a size corresponding to the size of the drug mesh 954a. In some non-limiting embodiments, the first electronic component 904a may be positioned on the drug mesh 954a. For example, the first electronic component 904a may be positioned on a portion of the base component 910 that seals the drug mesh 954a.

[0271] In some non-limiting embodiments, the first electronic component 904a may include a first portion 906a and a second portion 908a. In some non-limiting embodiments, the first portion 906a and the second portion 908a of the first electronic component 904a may be the same as the first portion 406 and the second portion 408 of the electronic component 404. In some non-limiting embodiments, the first portion 906a and the second portion 908a of the first electronic component 904a may be positioned on the drug mesh 954a. For example, the first portion 906a and the second portion 908a of the first electronic component 904a may be positioned on the portion of the base component 910 that seals the drug mesh 954a. In some non-limiting embodiments, a plurality of electronic components 904a, 904b may include a second electronic component 904b. In some non-limiting embodiments, the second electronic component 904b may be the same as the electronic component 404. In some non-limiting embodiments, the second electronic component 904b may have a suitable size based on the application for which the RFID tag 900 is designed. For example, the second electronic component 904b may have a size such that the second electronic component 904b may be positioned on the base component 910. In such an example, the second electronic component 904b may have a size corresponding to the size of the drug mesh 954b.

[0272] In some non-limiting embodiments, the second electronic component 904b can be positioned on the drug mesh 954b. For example, the second electronic component 904b can be positioned on a portion of the base component 910 that seals the drug mesh 954b.

[0273] In some non-limiting embodiments, the second electronic component 904b may include a first portion 906b and a second portion 908b. In some non-limiting embodiments, the first portion 906b and the second portion 908b of the second electronic component 904b may be the same as the first portion 406 and the second portion 408 of the electronic component 404. In some non-limiting embodiments, the first portion 906b and the second portion 908b of the second electronic component 904b may be positioned on the drug mesh 954b. For example, the first portion 906b and the second portion 908b of the second electronic component 904b may be positioned on a portion of the base component 910 that seals the drug mesh 954b.

[0274] It can be easily envisioned that additional electronic components having the same characteristics as the plurality of electronic components 904a, 904b can be included in the RFID tag 900, such as a third electronic component, a fourth electronic component, and / or a fifth electronic component, etc. For example, the RFID tag 900 can include at least two, or at least three, or at least four, or at least five electronic components 904, wherein each electronic component 904 is positioned on a drug mesh among the plurality of drug meshes 954a, 954b, such as positioned on a portion of the base component 910 that seals a drug mesh among the plurality of drug meshes 954a, 954b.

[0275] In some non-limiting embodiments, the base component 910 can be the same as the base component 410. In some non-limiting embodiments, the plurality of attachment points 916a, 916b can include a first attachment point 916a. In some non-limiting embodiments, the first attachment point 916a can be the same as the attachment point 416. In some non-limiting embodiments, the first attachment point 916a can be positioned on the drug mesh 954a. For example, the first attachment point 916a can be positioned on a portion of the base component 910 that seals the drug mesh 954a. In some non-limiting embodiments, the first attachment point 916a can be configured to allow the base component 910 to be pierced at the portion of the sealed drug mesh 954a.

[0276] In some non-limiting embodiments, the plurality of attachment points 916a, 916b may include a second attachment point 916b. In some non-limiting embodiments, the second attachment point 916b may be the same as the attachment point 416. In some non-limiting embodiments, the second attachment point 916b may be positioned on the drug mesh 954b. For example, the second attachment point 916b may be positioned on a portion of the base component 910 that seals the drug mesh 954b. In some non-limiting embodiments, the second attachment point 916b may be configured to allow the base component 910 to be pierced at the portion of the sealed drug mesh 954b.

[0277] In some non-limiting embodiments, when the first electronic component 904a is in the first state, the first portion 906a and the second portion 908a of the first electronic component 904a can be coupled together. For example, when the first electronic component 904a is in the first state, the first portion 906a and the second portion 908a of the first electronic component 904a can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the first electronic component 904a is in the first state, the base component 910 is not pierced, so that the drug mesh 954a is sealed, so that the first portion 906a and the second portion 908a of the first electronic component 904a are coupled together.

[0278] In some non-limiting embodiments, when the second electronic component 904b is in the first state, the first portion 906b and the second portion 908b of the second electronic component 904b can be coupled together. For example, when the second electronic component 904b is in the first state, the first portion 906b and the second portion 908b of the second electronic component 904b can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the second electronic component 904b is in the first state, the base component 910 is not pierced, so that the drug mesh 954b is sealed, so that the first portion 906b and the second portion 908b of the second electronic component 904b are coupled together.

[0279] In some non-limiting embodiments, when the first electronic component 904a and / or the second electronic component 904b are in the first state, the RFID circuit 902 can be configured to provide a first signal, for example, during an inquiry by an RFID reader device. In some non-limiting embodiments, the first signal provided by the RFID circuit 902 can include data associated with the indication of the first state of the drug package 952. In some non-limiting embodiments, the data associated with the first state of the drug package 952 can indicate a sealing configuration. For example, the data associated with the first state of the drug package 952 can indicate the sealing configuration of the drug package 952. In such an example, the data associated with the first state of the drug package 952 can indicate that the base component 910 is not pierced at any one of the attachment points of a plurality of attachment points 916a, 916b to open any one of the drug meshes 954a, 954b. In another example, the data associated with the first state of the drug package 952 can indicate that the base component 910 is not pierced at the first attachment point 916a to open the drug mesh 954a.

[0280] In some non-limiting embodiments, when the first electronic component 904a is in the second state, the first portion 906a and the second portion 908a of the first electronic component 904a can be decoupled. For example, when the first electronic component 904a is in the second state, the first portion 906a and the second portion 908a of the first electronic component 904a can not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the first electronic component 904a is in the second state, the base component 910 can be pierced at the first attachment point 916a, so that the drug mesh 954a is opened, so that the first portion 906a and the second portion 908a of the first electronic component 904a are decoupled.

[0281] In some non-limiting embodiments, when the second electronic component 904b is in the second state, the first portion 906b and the second portion 908b of the second electronic component 904b can be decoupled. For example, when the second electronic component 904b is in the second state, the first portion 906b and the second portion 908b of the second electronic component 904b can not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the second electronic component 904b is in the second state, the base component 910 can be pierced at the second attachment point 916b, so that the drug mesh 954b is opened, so that the first portion 906b and the second portion 908b of the second electronic component 904b are decoupled.

[0282] In some non-limiting embodiments, when the first electronic component 904a and / or the second electronic component 904b is in the second state, the RFID circuit 902 can be configured to provide a second signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the second signal provided by the RFID circuit 902 can be different from the first signal provided by the RFID circuit 902.

[0283] In some non-limiting embodiments, the second signal provided by the RFID circuit 902 may include data associated with an indication of a second state of the drug package 952. In some non-limiting embodiments, the data associated with the second state of the drug package 952 may indicate an unsealed configuration. For example, the data associated with the second state of the drug package 952 may indicate an unsealed configuration of the drug package 952. In such an example, the data associated with the second state of the drug package 952 may indicate that the base component 910 has been pierced at any one of the attachment points 916a, 916b to open any one of the drug meshes 954a, 954b. In another example, the data associated with the second state of the drug package 952 may indicate that the base component 910 has been pierced at the first attachment point 916a to open the drug mesh 954a.

[0284] In some non-limiting embodiments, when the second electronic component 904b is in the third state, the first portion 906b and the second portion 908b of the second electronic component 904b can be coupled together. For example, when the second electronic component 904b is in the third state, the first portion 906b and the second portion 908b of the second electronic component 904b can be electrically coupled (e.g., conductively coupled) together. In some non-limiting embodiments, when the second electronic component 904b is in the third state, the base component 910 is not pierced, so that the drug mesh 954b is sealed, so that the first portion 906b and the second portion 908b of the second electronic component 904b are coupled together.

[0285] In some non-limiting embodiments, when the second electronic component 904b is in the third state, the RFID circuit 902 can be configured to provide a third signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the third signal provided by the RFID circuit 902 can be different from the first signal and the second signal provided by the RFID circuit 902.

[0286] In some non-limiting embodiments, the third signal provided by the RFID circuit 902 may include data associated with an indication of a third state of the drug package 952. In some non-limiting embodiments, the data associated with the third state of the drug package 952 may indicate a sealed configuration. For example, the data associated with the third state of the drug package 952 may indicate a sealed configuration of the drug package 952. For example, the data associated with the third state of the drug package 952 may indicate that the base component 910 has not been pierced at the second attachment point 916b to open the drug web 954b.

[0287] In some non-limiting embodiments, when the second electronic component 904b is in the fourth state, the first portion 906b and the second portion 908b of the second electronic component 904b may be decoupled. For example, when the second electronic component 904b is in the fourth state, the first portion 906b and the second portion 908b of the second electronic component 904b may not be electrically coupled (e.g., not conductively coupled). In some non-limiting embodiments, when the second electronic component 904b is in the fourth state, the base component 910 may be pierced at the second attachment point 916b, so that the drug mesh 954b is opened, so that the first portion 906b and the second portion 908b of the second electronic component 904b are decoupled.

[0288] In some non-limiting embodiments, when the second electronic component 904b is in the fourth state, the RFID circuit 902 can be configured to provide a fourth signal, for example, during interrogation by an RFID reader device. In some non-limiting embodiments, the fourth signal provided by the RFID circuit 902 can be different from the first signal, the second signal, and the third signal provided by the RFID circuit 902.

[0289] In some non-limiting embodiments, the fourth signal provided by the RFID circuit 902 may include data associated with an indication of a fourth state of the drug package 952. In some non-limiting embodiments, the data associated with the fourth state of the drug package 952 may indicate an unsealed configuration. For example, the data associated with the fourth state of the drug package 952 may indicate an unsealed configuration of the drug package 952. For example, the data associated with the fourth state of the drug package 952 may indicate that the base component 910 is pierced at the second attachment point 916b to open the drug web 954b.

[0290] refer to Fig.10 , Fig.10 1006. RFID reader device 1002 may be located on bed ...

[0291] In some non-limiting embodiments, the RFID reader device 1002 can be positioned on the side table 1008. For example, the RFID reader device 1002 can be attached to the side table 1008 (e.g., by adhesive and / or fasteners, etc.). In another example, the RFID reader device 1002 can form a part of the side table 1008, such that the RFID reader device 1002 and the side table 1008 are substantially connected.

[0292] It can be easily envisioned that the RFID reader device 1002 can be located at other locations in the area 1000. For example, the RFID reader device 1002 can be located on the patient, such as on a bracelet and / or attached to an outer garment, etc. In another example, the RFID reader device 1002 can be located on a wall, ceiling, and / or floor of the area 1000 and / or on a medical instrument present in the area 1000.

[0293] In some non-limiting embodiments, the RFID reader device 1002 can receive data from an RFID tag (e.g., RFID tag 400 and / or RFID tag 500) and send a notification 1004 based on the received data. For example, the RFID reader device 1002 can be cloud connected. In some non-limiting embodiments, the RFID reader device 1002 can receive data from an RFID tag (e.g., RFID tag 400 and / or RFID tag 500) and send a notification 1004 based on the received data via email and / or instant messaging, etc. For example, the RFID reader device can send a notification 1004 to a clinician, clinic, patient, spouse, and / or insurance provider, etc. based on the received data.

[0294] Although various non-limiting embodiments have been described in detail for purposes of illustration and description, it will be understood that such detail is for that purpose only, and that the embodiments are not limited to the disclosed embodiments, but, on the contrary, are intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it will be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment or aspect may be combined with one or more features of any other embodiment or aspect. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may be directly dependent on only one claim, the disclosure of possible implementations includes the combination of each dependent claim with each other claim in the claim group.

Claims

1. A system comprising: Medical devices; as well as a radio frequency identification (RFID) tear tag attached to the medical device, wherein the RFID tear tag comprises: RFID circuitry; and an electronic component electrically connected to the RFID circuit, wherein the electronic component includes a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable, wherein, when the electronic component is in a first state, the first portion and the second portion of the electronic component are electrically coupled, and the RFID circuit is configured to provide a first signal, and Wherein, when the electronic component is in a second state, the first part and the second part of the electronic component are not electrically coupled, and the RFID circuit is configured to provide a second signal.

2. The system according to claim 1, wherein: When the first portion and the second portion of the electronic component are electrically coupled, the first portion and the second portion of the electronic component are conductively coupled.

3. The system according to claim 1, wherein: The electronic component comprises an electrical conductor.

4. The system according to claim 3, wherein: The electrical conductors include conductive traces.

5. The system according to claim 1, further comprising: Basic components, Wherein, the RFID circuit and the electronic component are positioned on the base component.

6. The system according to claim 5, wherein: The base component comprises a perforation, and wherein the first portion and the second portion are configured to be separable based on the perforation of the base component.

7. The system according to claim 1, wherein: The first portion and the second portion are coupled together when the electronic component is in the first state, and wherein the first portion and the second portion cannot be recoupled when the electronic component is in the second state.

8. The system according to claim 1, wherein: The first portion and the second portion are configured to be separable independent of additional mechanical components.

9. The system according to claim 1, wherein: The electronic component is a first electronic component, and the system further comprises: a second electronic component electrically connected to the RFID circuit, wherein the second electronic component includes an additional first portion and an additional second portion, and wherein the additional first portion of the second electronic component and the additional second portion of the second electronic component are configured to be separable; and The additional first portion is separate from the additional second portion, and the RFID circuit is configured to provide a third signal, wherein the third signal is different from the first signal and the second signal.

10. The system according to claim 1, wherein: When the electronic component is in the first state, the RFID circuit is configured to provide the first signal during interrogation by an RFID reader device.

11. The system according to claim 1, wherein: When the electronic component is in the second state, the RFID circuit is configured to provide the second signal during interrogation by an RFID reader device, wherein the second signal is different from the first signal.

12. The system of claim 1, wherein: The medical device comprises a disposable medical device.

13. A medical device assembly comprising: a container having a closure; Radio frequency identification (RFID) circuits; as well as an electronic component electrically connected to the RFID circuit, wherein the electronic component comprises a first portion and a second portion, and wherein the first portion and the second portion are configured to be separable, and wherein the RFID circuit and the electronic component are positioned on the container, wherein the first portion and the second portion of the electronic component are electrically coupled when the electronic component is in a first state, and the RFID circuit is configured to provide a first signal during interrogation by an RFID reader device, and Wherein, when the electronic component is in a second state, the first portion and the second portion of the electronic component are not electrically coupled, and the RFID circuit is configured to provide a second signal during interrogation by an RFID reader device, wherein the second signal is different from the first signal.

14. The medical device assembly of claim 12, wherein: When the first portion and the second portion of the electronic component are electrically coupled, the first portion and the second portion of the electronic component are conductively coupled.

15. The medical device assembly of claim 12, wherein: The electronic component comprises an electrical conductor.

16. The medical device assembly of claim 14, wherein: The electrical conductors include conductive traces.

17. The medical device assembly of claim 12, further comprising: Basic components, wherein the RFID circuit and the electronic component are positioned on the base component, and Therein, the base component is positioned on the closure of the container.

18. The medical device assembly of claim 16, wherein: The base component comprises a perforation, and wherein the first portion and the second portion are configured to be separable based on the perforation of the base component.

19. The medical device assembly of claim 12, wherein: The first portion and the second portion of the electronic component are configured to be destructively disconnected when the electronic component is in the second state.

20. The medical device assembly of claim 12, wherein: The first portion and the second portion are configured to be separable independent of additional mechanical components.

21. The medical device assembly of claim 12, wherein: The electronic component is a first electronic component, and the medical device assembly further comprises: a second electronic component electrically connected to the RFID circuit, wherein the second electronic component includes an additional first portion and an additional second portion, and wherein the additional first portion of the second electronic component and the additional second portion of the second electronic component are configured to be separable; and The additional first portion is separate from the additional second portion, and the RFID circuit is configured to provide a third signal, wherein the third signal is different from the first signal and the second signal.

22. The medical device assembly of claim 12, wherein: The container comprises a disposable container.

Images