Patent Description:
In certain applications, it is important to determine when two devices are connected with each other. This is a relatively straightforward problem if devices to be connected are able to directly interact with each other. For example, in a case of an electrical connection between two devices, establishment of a current flow can indicate a presence of a connection between the two devices, e.g., one of the mating connectors may complete a circuit in its complement.

Hospitals have conventionally used Bar Code Medication Administration (BCMA) systems to reduce medication error. BCMA systems include a handheld barcode reader, which includes an integrated processor and a wireless connection. A computer server with software is integrated with other hospital IT systems, (e.g., an electronic medication administration record), to verify that an identified patient is the intended recipient of a medicine in a container. In use, prior to administering a medication to a patient, a nurse scans a wristband barcode on the patient, and scans a barcode on the container to verify that the medication in the container is the correct medication for the patient. In some implementations, the nurse may also scan his or her own badge barcode. BCMA systems require the use of a handheld electronic device that is inconvenient, requires manual management, and is a contamination risk.

Further, although BCMA systems can help confirm the five "rights" of medication administration: right patient, right drug, right dose, right route, and right time, and reduce medication administration errors, many workarounds to BCMA systems exist, such as affixing patient identification barcodes to computer carts, scanners, doorjambs, or nurses' belt rings, carrying several patients' pre-scanned medications on carts, and the like. Nurses or other medical professionals may override and/or ignore BCMA alerts and/or procedures for various reasons. For example, some causes of these workarounds include unreadable medication barcodes (e.g., barcodes that are crinkled, smudged, torn, missing, and/or covered by another label), malfunctioning scanners, unreadable or missing patient identification wristbands (e.g., wristbands that are chewed, soaked, and/or missing), non-barcoded medications, failing batteries, uncertain wireless connectivity, emergencies, and the like. Possible consequences of workarounds include incorrect administration of medications, incorrect doses, incorrect medication administration times, and incorrect medication formulations, and the like. Shortcomings in BCMA system design, implementation, and workflow integration may encourage these workarounds. Moreover, integrating BCMA systems within real-world clinical workflows requires attention to in situ use to ensure correct use of safety features of BCMA systems.

<CIT> discloses a system for identifying a connection of two or more components in which one or more RFID transponders are associated with the two or more components. However, <CIT> requires using an electrical connection between devices to determine connection of a particular plug and a particular socket on a pairwise basis. Moreover, <CIT> does not disclose detection of a connection event, only determination that a connection between devices exists.

<CIT> is directed to a medication safety system that includes a panel mounted to an IV pole above a multi-channel infusion pump also mounted to the IV pole. However, the panel requires an RFID reader for each channel of the multi-channel infusion pump for reading the RFID tags placed on each of the medication containers mounted to the panel, not RFID transmitters on each of the channels and the medication containers. <CIT> discloses a RFID based system relying on physical proximity to determine connections among devices.

Therefore, there is a need in the art for connection identification systems and methods that enable use of independent connection sensors that are sealed from the environment, create a simplified workflow for caregivers, reduce a need and possibility for workarounds, eliminate hand-held scanners as vectors of infection, provide increased detail regarding route of administration, monitor of all points of entry that can result in fluid being delivered to a patient, and/or achieve higher reliability and specificity of radio detection.

Accordingly, it is an object of the present disclosure to provide a method, system, and computer program product for identifying device connections that overcomes some or all of the deficiencies of the prior art.

According to a non-limiting embodiment or aspect, provided is a system for identifying device connections in a connection area, comprising at least one computer including at least one processor, the at least computer programmed and/or configured to: receive a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, wherein the plurality of physical parameters indicates physical states of the plurality of devices; and determine at least one physical connection state between the plurality of devices based on the plurality of physical parameters of the plurality of devices.

According to a non-limiting embodiment or aspect, provided is a system for identifying device connections in a connection area comprising: at least one first device; at least one second device, wherein the at least one first device is configured to be physically connected to the at least one second device; at least one first sensor on the at least one first device, wherein the at least one first sensor is configured to sense at least one physical state of the at least one first device to determine at least one first physical parameter of the at least one first device; at least one first transmission source on the at least one first device, wherein the at least one first transmission source is configured to transmit the at least one first physical parameter of the at least one first device; at least one second sensor on the at least one second device, wherein the at least one second sensor is configured to sense at least one physical state of the at least one second device to determine at least one second physical parameter of the at least one second device; at least one second transmission source on the at least one second device, wherein the at least one second transmission source is configured to transmit the at least one second physical parameter of the at least one second device; at least one receiver configured to detect the at least one first transmission source in a connection area, detect the at least one second transmission source in the connection area, receive the at least one first physical parameter from the at least one first transmission source, and receive the at least one second physical parameter from the at least one second transmission source.

According to a non-limiting embodiment or aspect, provided is a computer-implemented method for identifying device connections in a connection area, the method comprising: receiving, with at least one processor, a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, wherein the plurality of physical parameters indicates physical states of the plurality of devices; and determining, with at least one processor, at least one physical connection state between the plurality of devices based on the plurality of physical parameters of the plurality of devices.

According to a non-limiting embodiment or aspect, provided is a method for identifying device connections in a connection area comprising: sensing, with at least one first sensor on at least one first device, at least one physical state of the at least one first device to determine at least one first physical parameter of the at least one first device; transmitting, with at least one first transmission source on the at least one first device, the at least one first physical parameter of the at least one first device; sensing, with at least one second sensor on at least one second device, at least one physical state of the at least one second device to determine at least one second physical parameter of the at least one second device; transmitting, with at least one second transmission source on the at least one second device, the at least one second physical parameter of the at least one second device; with at least one signal receiver, detecting the at least one first transmission source in a connection area, detecting the at least one second transmission source in the connection area, receiving the at least one the at least one first physical parameter from the at least one first transmission source, and receiving the at least one second physical parameter from the at least one second transmission source.

It is noted herein that a multitude of receivers may be included in the system. Each receiver may have a reception area that depends on many factors, including objects blocking and/or reflecting radio signals. Accordingly, which specific receiver picks up signals from each device can be variable. Signals from devices undergoing connections may be detected by different receivers. In one configuration, an individual transmitter can be received by multiple receivers. In another configuration, each transmitter of a pair of devices can be detected by different receivers. In yet another configuration, pairs of device transmitters can be detected by multiple receivers. Combinatorial logic can determine from complex and potentially redundant data received from multiple receivers which transmitters have been connected together.

According to a non-limiting embodiment or aspect, provided is a computer program product for dynamic application selection for electronic medical records, the computer program product comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor cause the at least one processor to: receive a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, wherein the plurality of physical parameters indicates physical states of the plurality of devices; and determine at least one physical connection state between the plurality of devices based on the plurality of physical parameters of the plurality of devices.

It is appreciated herein that the transmitter may send information about the activation state or connection state of a device being used. Along with these states, a device identity may be conveyed, which can either be unique (for example, at the SKU level), or general device-type. Individual unique device identity can be used to identify the SKU, which can be used to identify the type of device.

It is further appreciated herein that the system can include a database of devices that contain a digital description of the physical characteristics of a device being used at a facility. This database may contain, for example, the fluid path structure of each device, allowed interactions between devices, inlets and outlets, connection points, and fluid path lengths and volumes between them. For example, an IV set could be detected. A digital representation could contain the position of connectors and the structure of the branching fluid path between all inlets and outlets.

It is further appreciated herein that the system can include a database which can be accessed by the computer application to create a digital representation of the fluid path, interactions of the devices within the fluid path, and other devices in the receiver area.

It is still further contemplated that the system can include a computer application which uses information in the database to resolve conflicts. For example, if two sets of connections are detected simultaneously, information in the database can help resolve which pairs of connections have the highest likelihood of being correct.

These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the present disclosure. As used in the specification and the claims, the singular form of "a," "an," and "the" include plural referents unless the context clearly dictates otherwise.

Additional advantages and details of embodiments or aspects of the present disclosure are explained in greater detail below with reference to the exemplary embodiments that are illustrated in the accompanying schematic figures, in which:.

For purposes of the description hereinafter, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "lateral," "longitudinal," and derivatives thereof shall relate to the present disclosure as it is oriented in the drawing figures. However, it is to be understood that the present disclosure may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments or aspects of the present disclosure. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments disclosed herein are not to be considered as limiting unless otherwise indicated.

No aspect, component, element, structure, act, step, function, instruction, and/or the like used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more" and "at least one. " Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one. " Where only one item is intended, the term "one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or the like are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "based at least in partially on" unless explicitly stated otherwise.

As used herein, the terms "communication" and "communicate" may refer to the reception, receipt, transmission, transfer, provision, and/or the like, of information (e.g., data, signals, messages, instructions, commands, and/or the like). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, and/or the like) to be in communication with another unit means that the one unit is able to directly or indirectly receive information from and/or transmit information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, and/or the like) that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may be in communication with a second unit if at least one intermediary unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and communicates the processed information to the second unit. In some non-limiting embodiments, a message may refer to a network packet (e.g., a data packet, and/or the like) that includes data. It will be appreciated that numerous other arrangements are possible.

As used herein, the term "computing device" may refer to one or more electronic devices that are configured to directly or indirectly communicate with or over one or more networks. The computing device may be a mobile device. As used herein, the term "mobile device" may refer to one or more portable electronic devices configured to communicate with one or more networks. As an example, a mobile device may include a cellular phone (e.g., a smartphone or standard cellular phone), a portable computer (e.g., a tablet computer, a laptop computer, etc.), a wearable device (e.g., a watch, pair of glasses, lens, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. The computing device may not be a mobile device, such as a desktop computer. Furthermore, the term "computer" may refer to any computing device that includes the necessary components to receive, process, and output data, and normally includes a display, a processor, a memory, an input device, and a network interface.

As used herein, a "data transmission apparatus" or a "transmission source" may refer to one or more devices, which may be used to transmit data or signals to a receiver in a connection area. For example, a data transmission apparatus or a transmission source may include one or more computers, peripheral devices, near-field communication (NFC) transmission sources, radio frequency identification (RFID) transmission sources, and/or other contactless transmission sources or transceivers, contact-based transmission sources, computers, servers, output devices, and/or the like.

As used herein, the term "receiver" may refer to one or more electronic devices or systems (e.g., located in a connection area and separate, remote from, and/or spaced apart from a data transmission apparatus or transmission source) used to receive data or signals from a data transmission apparatus or transmission source and configured to communicate with one or more networks. For example, a receiver may include one or more computers, portable computers, tablet computers, cellular phones, wearable devices (e.g., watches, glasses, lenses, clothing, and/or the like), PDAs, and/or the like. In some non-limiting embodiments or aspects, a receiver may include one or more computers, peripheral devices, near-field communication (NFC) reception sources, radio frequency identification (RFID) reception sources, and/or other contactless reception sources or transceivers, contact-based reception sources, computers, servers, input devices, and/or the like.

As used herein, the term "connection area" may refer to an area or location in which one or more receivers associated with that area or location are configured to receive data transmissions or signal transmissions from one or more data transmission apparatuses or transmission sources that are located within the connection area, have entered the connection, and/or are entering the connection area. For example, a connection area may be defined by a range of a wireless communication network between one or more receivers and one or more data transmission apparatuses or transmission sources.

As used herein, the term "server" may refer to one or more computing devices (e.g., processors, storage devices, similar computer components, and/or the like) that communicate with receivers, data transmission apparatuses or transmission sources, and/or other computing devices over a network (e.g., a public network, the Internet, a private network, and/or the like) and, in some examples, facilitate communication among other servers and/or receivers. It will be appreciated that various other arrangements are possible. As used herein, the term "system" may refer to one or more computing devices or combinations of computing devices (e.g., processors, servers, client devices, software applications, components of such, and/or the like). Reference to "a device," "a server," "a processor," and/or the like, as used herein, may refer to a previously-recited device, server, or processor that is recited as performing a previous step or function, a different server or processor, and/or a combination of servers and/or processors. For example, as used in the specification and the claims, a first server or a first processor that is recited as performing a first step or a first function may refer to the same or different server or the same or different processor recited as performing a second step or a second function.

As used herein, the term "application" or "application program interface" (API) refers to computer code, a set of rules, or other data sorted on a computer-readable medium that may be executed by a processor to facilitate interaction between software components, such as a client-side front-end and/or server-side back-end for receiving data from the client. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUIs) with which a user may interact, either directly or indirectly (e.g., through a keyboard, mouse, etc.).

Non-limiting embodiments or aspects of the present disclosure are directed to systems, methods, and computer program products for identifying device connections in a connection area. Non-limiting embodiments or aspects of the present disclosure allow for identification of devices that are currently being or have previously been connected in an environment where there are multiple devices that can be simultaneously interconnected, without connecting devices directly communicating or interacting with each other. For example, non-limiting embodiments or aspects of the present disclosure provide a remote computing device and/or receiver that receives a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, and determines a physical connection state(s) between the plurality of devices based on the plurality of physical parameters of the plurality of devices. These features enable use of independent connection sensors that are sealed from the environment, creating a simplified workflow for caregivers, reducing a need and possibility for workarounds, eliminating RFID scanners as vectors of infection, providing increased detail regarding route of administration, monitoring of all points of entry that can result in fluid being delivered to a patient, and/or achieving higher reliability and specificity of radio detection. For example, these features enable determining which devices are interconnected without relying on physical connector type or restrictions on connections based on connector type or shape and/or without relying on electrical communication or interaction between connection sensors. These features further enable determining which devices are interconnected when multiple sets of connections may already be established.

Referring to <FIG>, a non-limiting embodiment or aspect of an environment <NUM> in which systems, devices, products, apparatus, and/or methods, as described herein, may be implemented is shown. As shown in <FIG>, environment <NUM> may include one or more connection areas <NUM>, one or more receivers <NUM>, a plurality of transmission sources <NUM>, network <NUM>, one or more remote computing devices <NUM>, and/or a plurality of devices <NUM>. For example, environment <NUM> as shown in <FIG> includes connection area 102a including receiver 104a and transmission sources 106a and 106b, and connection area 102b including receiver 104b, receiver 104c, and transmission sources 106c, 106d, and 106e. Transmission sources 106a through 106e may be respectively connected to or integrated with medical devices 112a through 112e. In some non-limiting embodiments or aspects, environment <NUM> may include additional components, fewer components, different components, or differently arranged components than those shown in <FIG>. Additionally, or alternatively, a set of components (e.g., one or more components) may perform one or more functions described as being performed by another set of components of environment <NUM>.

In some non-limiting embodiments or aspects, a connection area <NUM> includes an area or location in which one or more receivers <NUM> are located and/or configured to communicate with transmission sources <NUM> via one or more wired and/or wireless networks. As an example, connection area 102a includes receiver 104a, and connection area 102b includes receivers 104b and 104c spaced apart from one another in the connection area. In some non-limiting embodiments or aspects, a connection area <NUM> includes an area or location defined or covered by a range of one or more short range wireless communication connections (e.g., an NFC communication connection, a Radio-frequency identification (RFID) communication connection, a Bluetooth® communication connection, and/or the like) via which one or more receivers <NUM> are capable of receiving information from transmission sources <NUM>. For example, as shown in <FIG>, multiple permanent and/or semi-permanent receivers <NUM> can be spaced apart from one another around a patient area, for example, connected to or integrated with objects such as a patient bed and an IV pump, to define a connection area <NUM> covering and/or surrounding the patient area, which can improve reliability and specificity of radio detection of transmission sources <NUM> within the patient area. Dotted lines between receivers <NUM> in <FIG> represent example communication connections between receivers <NUM>.

In some non-limiting embodiments or aspects, a receiver <NUM> includes one or more devices capable of receiving information, data, and/or signals from and/or transmitting information, data, and/or signals to other receivers <NUM>, transmission sources <NUM>, and/or remote computing device <NUM> via one or more wired and/or wireless networks. As an example, a receiver <NUM> includes one or more computing devices, servers, desktop computers, mobile devices, chip readers, contactless transceivers, contactless receivers, NFC receivers, RFID receivers, contact based receivers, and/or the like. In some non-limiting embodiments or aspects, a mobile device includes one or more portable electronic devices configured to communicate with one or more other electronic devices via a network (e.g., network <NUM>). For example, a mobile device can include a cellular phone (e.g., a smartphone or standard cellular phone), a portable computer (e.g., a tablet computer, a laptop computer, etc.), a wearable device (e.g., a watch, pair of glasses, augmented or virtual reality display, heads up display, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. In some non-limiting embodiments or aspects, a receiver <NUM> includes one or more devices capable of receiving information from transmission sources <NUM> via a short range wireless communication connection (e.g., a communication connection that uses NFC protocol, a communication connection that uses Radio-frequency identification (RFID), a communication connection that uses a Bluetooth® wireless technology standard, and/or the like).

In some non-limiting embodiments or aspects, a receiver <NUM> is configured as a bedside unit that is capable of being located in a vicinity of a patient. For example, the bedside unit can be connected to a wall of a room of the patient, an IV pole, and/or a carrier held in place by a bed of the patient (e.g., between mattresses) near a side of the patient or the bed.

The bedside device can display warnings, as in the illustrations below, which can also have audible warnings. The bedside unit can also contain necessary networking interfaces and the RFID reader.

In some non-limiting embodiments or aspects, a transmission source <NUM> includes one or more devices capable of transmitting information, data, and/or signals to receivers <NUM> via one or more wired and/or wireless networks. For example, as shown in <FIG>, transmission sources 106a and 106b communicate with receiver 104a, transmission sources 106c and 106d communicate with receiver 104b, and transmission sources 106d and 106e communicate with receiver 104c. As an example, a transmission source <NUM> includes one or more computing devices, chips, contactless transmitters, contactless transceivers, NFC transmitters, RFID transmitters, contact based transmitters, and/or the like. In some non-limiting embodiments or aspects, a transmission source <NUM> can include one or more devices capable of transmitting information to receivers <NUM> via a short range wireless communication connection (e.g., a communication connection that uses NFC protocol, a communication connection that uses Radio-frequency identification (RFID), a communication connection that uses a Bluetooth® wireless technology standard, and/or the like). In some non-limiting embodiments or aspects, transmission sources <NUM> may not be configured to communicate with one another. For example, transmission sources <NUM> may be configured to communicate only with receivers <NUM>.

In some non-limiting embodiments or aspects, remote computing device <NUM> may include one or more devices capable of receiving information, data and/or signals from and/or transmitting information, data, and/or signals to one or more receivers <NUM>, transmission sources <NUM>, and/or other remote computing devices <NUM> via one or more wired and/or wireless networks. For example, remote computing device <NUM> may include a computing device, a server, a group of servers, a mobile device, a group of mobile devices and/or the like. In some non-limiting embodiments or aspects, remote computing device <NUM> includes one or more receivers <NUM>. For example, remote computing device <NUM> includes a receiver <NUM> that enables remote computing device <NUM> to receive information directly from and/or communicate information directly to transmission sources <NUM> via a short range wireless communication connection (e.g., a communication connection that uses NFC protocol, a communication connection that uses Radio-frequency identification (RFID), a communication connection that uses a Bluetooth® wireless technology standard, and/or the like). In some non-limiting embodiments or aspects, remote computing device <NUM> may be separate from receivers <NUM> and/or remote from a connection area(s) <NUM>.

In some non-limiting embodiments or aspects, remote computing device <NUM> is configured to receive information, data, and/or signals from and/or transmit information, data, and/or signals to receivers <NUM> in a plurality of different connection areas <NUM>. For example, as shown in <FIG>, receiver 104a may communicate with transmission sources 106a and 106b in connection area 102a via a short range wireless communication connection, and communicate with remote computing device <NUM> via network <NUM>. Receivers 104b and 104c may communicate with each other in a connection area 102b. Receiver 104b may communicate with transmission sources 106c and 106d, and receiver 104c may communicate with transmission source 106e, which may be outside a connection range of receiver 104b, but still within connection area 102b due to being within a connection range of receiver 104c. Receiver 104c may communicate information and/or data received from transmission source 106e to receiver 104b for forwarding to remote computing device <NUM>, or communicate the information and/or data directly to remote computing device <NUM> via network <NUM>. Receivers <NUM> in a same connection area <NUM> may be associated with that connection area at remote computing device <NUM> and communicate with one another via network <NUM> or via one or more direct communication connections within that connection area <NUM>, such as the short range communication connections as defined herein.

In some non-limiting embodiments or aspects, remote computing device <NUM> is configured to receive manually input information and/or data. As an example, if longer-term connections (e.g., if there are more than a single pair of devices) are out of sync, remote computing device <NUM> may receive a manual data entry that updates connections of devices. For example, manual data entry can occur if new IVs are started away from a bedside unit including receiver <NUM>, e.g., outside a connection area <NUM>. Remote computing system provides a user interface that enables a caregiver to manually update connections of devices if connections cannot be automatically determined. As an example, remote computing device <NUM> comprises buttons with a graphical user interface. One button is configured to control the remote computer <NUM> to cycle through connected devices, with the display graphically and/or alphanumerically indicating types of devices (or drug, ID number, etc.). Another button is configured to select a displayed device in the graphical user interface, via which a user can input device pairs into the remote computer <NUM>.

In some non-limiting embodiments or aspects, network <NUM> includes one or more wired and/or wireless networks. For example, network <NUM> may include a cellular network (e.g., a long-term evolution (LTE) network, a third generation (<NUM>) network, a fourth generation (<NUM>) 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., the public switched telephone network (PSTN)), a private network (e.g., a private network associated with a transaction service provider), an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or the like, and/or a combination of these or other types of networks.

Referring now to <FIG> is a diagram of example components of a device <NUM>. Device <NUM> may correspond to receiver <NUM>, transmission source <NUM>, and/or remote computing device <NUM>. In some non-limiting embodiments or aspects, receiver <NUM>, transmission source <NUM>, and/or remote computing device <NUM> may include at least one device <NUM> and/or at least one component of device <NUM>. As shown in <FIG>, device <NUM> may include bus <NUM>, processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, and/or communication interface <NUM>.

Bus <NUM> may include a component that permits communication among the components of device <NUM>. In some non-limiting embodiments or aspects, processor <NUM> may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor <NUM> 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 (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), and/or the like, which can be programmed to perform a function. Memory <NUM> may include a random-access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by processor <NUM>.

Input component <NUM> may include a component that permits device <NUM> to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively, input component <NUM> may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component <NUM> may include a component that provides output information from device <NUM> (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

Communication interface <NUM> may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmission source, etc.) that enables device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface <NUM> may permit device <NUM> to receive information from another device and/or provide information to another device. For example, communication interface <NUM> 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, a Wi-Fi interface, a cellular network interface, and/or the like.

Device <NUM> may perform one or more processes described herein. Device <NUM> may perform these processes based on processor <NUM> executing software instructions stored by a computer-readable medium, such as memory <NUM> and/or storage component <NUM>. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices.

Thus, embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software.

Referring now to <FIG> is a diagram of example components of a tracking device <NUM>. Tracking device <NUM> may be implemented as a transmission source <NUM> and/or a transmission source <NUM> may be included as part of tracking device <NUM>. For example, tracking device <NUM> comprises controller <NUM>, e.g., an RFID chip, antenna <NUM>, e.g., an RFID antenna, and/or sensor <NUM>, which can be attached to or integrated with a tag or carrier <NUM> configured to carry or hold the components of the tracking device <NUM>. Device <NUM> may be connected to and/or integrated with another device, such as a medical device <NUM>. For example, tracking device <NUM> may be connected to and/or integrated with at least one of the following: a syringe, an IV spike, an IV access site, an IV bag, an IV set, a catheter, a medical device connector, or any combination thereof. In some non-limiting embodiments or aspects, tracking device <NUM> is located within a fluid flow path formed by one or more medical devices.

In some non-limiting embodiments or aspects, tracking device <NUM> receives power via a wirelessly transmitted power source, such as via an RF transmission from a receiver <NUM>. In some non-limiting embodiments or aspects, tracking device <NUM> includes an integrated power source, such as a battery.

In some non-limiting embodiments or aspects, sensor <NUM> is configured to sense an electrical, optical, and/or physical state or characteristic. As an example, sensor <NUM> is configured to sense electrically, optically, and/or physically at least one physical parameter of a medical device <NUM> with which tracking device <NUM> is connected and/or integrated. In some non-limiting embodiments or aspects, sensor <NUM> comprises a pressure sensor. For example, sensor <NUM> is configured to sense a pressure applied to a connection of a medical device <NUM> when the medical device <NUM> is connected to another medical device <NUM>. In some non-limiting embodiments or aspects, sensor <NUM> is integrated with and/or included as part of controller <NUM>.

In some non-limiting embodiments or aspects, tracking device <NUM> and/or sensor <NUM> are located or positioned at or near a fluid entry point or a fluid exit point of a medical device <NUM>. As an example, tracking device <NUM> and/or sensor <NUM> are connected to and/or integrated with a connector of a medical device <NUM> configured to connect to another connector of another medical device such that when the connector of the medical device is connected to or disconnected from the another connector of the another medical device, the another connector of the another medical device activates or actuates sensor <NUM>, e.g., by applying or removing a pressure on a pressure and/or increasing or decreasing a transmissivity of a light path to an optical sensor.

In some non-limiting embodiments or aspects, controller <NUM> is configured to control antenna <NUM> to transmit information, data, and/or signals. As an example, controller <NUM> is configured to transmit information based on the at least one physical parameter sensed by the sensor <NUM>. Controller <NUM> may include a storage component storing an identifier that identifies a type of medical device and/or uniquely identifies a medical device with which tracking device <NUM> is connected and/or integrated, and/or other information and/or data related to the medical device and/or a procedure for which the medical device is intended to be used. For example, controller <NUM> transmits the identifier and/or other information and/or data with the information and/or data including the sensed at least one physical parameter.

In some non-limiting embodiments, controller <NUM> is configured to control antenna <NUM> to transmit information including the sensed at least one physical parameter in response to at least one of the following: entering a connection area, (e.g., in response to receiving a polling signal from a receiver <NUM>), receiving a polling signal from a receiver <NUM> while within a connection area, actuation of sensor <NUM>, determining a change in a physical parameter sensed by sensor <NUM>, or any combination thereof. In some non-limiting embodiments or aspects, after an initial transmission in response to polling by a receiver <NUM> upon entering a connection area, controller <NUM> is configured to control antenna <NUM> to transmit information including the sensed at least one physical parameter only in response to actuation of sensor <NUM> and/or a change in a physical parameter sensed by sensor <NUM>. In some non-limiting embodiments or aspects, controller <NUM> is configured to control antenna <NUM> to transmit information including the sensed at least one physical parameter continuously while tracking device <NUM> is within a connection area <NUM> or at periodic intervals while tracking device <NUM> is within a connection area <NUM>.

In some non-limiting embodiments or aspects, controller <NUM>, antenna <NUM>, and/or sensor <NUM> are sealed from the environment and/or self-contained. For example, controller <NUM>, antenna <NUM>, and sensor <NUM> are sealed within and/or integrally formed within tag or carrier <NUM>. In some non-limiting embodiments or aspects, controller <NUM>, antenna <NUM>, sensor <NUM>, and/or tag or carrier <NUM> are sealed within and/or integrally formed within another device. For example, tracking device <NUM> is sealed within and/or integrally formed with a medical device.

In some non-limiting embodiments or aspects, tracking device <NUM> may include additional components, fewer components, different components, or differently arranged components than those shown in <FIG>. Additionally, or alternatively, a set of components (e.g., one or more components) of tracking device <NUM> may perform one or more functions described as being performed by another set of components of device <NUM>.

<FIG> is a perspective view of a non-limiting embodiment or aspect of an implementation <NUM> relating to tracking device <NUM> shown in <FIG>. As shown in <FIG>, tracking device <NUM> may include controller <NUM>, antenna <NUM>, and sensor <NUM> provided on tag or carrier <NUM>. In some non-limiting embodiments or aspects, controller <NUM> may be the same as or similar to controller <NUM> as described herein, antenna <NUM> may the same as or similar to antenna <NUM> as described herein, sensor <NUM> may be the same as or similar to sensor <NUM> described herein, and tag or carrier <NUM> may be the same as or similar to tag or carrier <NUM> described herein.

In some non-limiting embodiments or aspects, tracking device <NUM> is configured to be connected or adhered to a medical device, such as a medical connector <NUM> as shown in <FIG>. For example, tag or carrier <NUM> of tracking device <NUM> can comprise an adhesive and/or mechanical connector, such as a push-fit connection, a snap-fit connection, and the like, configured to connect tracking device <NUM> to medical connector <NUM>.

In some non-limiting embodiments or aspects, medical connector <NUM> forms or is configured to form at least a portion of a fluid flow path, and tracking device <NUM> is attached to medical connector <NUM> at a fluid outlet or a fluid inlet of medical connector <NUM>. In some non-limiting embodiments or aspects, antenna <NUM> may be located adjacent to other components on the tag or carrier <NUM>, such as controller <NUM> and sensor <NUM>, to simplify manufacturing and assembly. However, other geometries and adhesive technologies may be used. For example, as shown in <FIG>, tag or carrier <NUM> including antenna <NUM> may comprise a ring shape configured to be applied over a base of medical connector <NUM>, which can enable use of a larger antenna without significantly increasing a size of tracking device <NUM>. Sensor <NUM> may comprise a layer in the ring-shaped tag or carrier <NUM>, for example, a layer on top of a layer comprising antenna <NUM>. In some non-limiting embodiments or aspects, tracking device <NUM> can be implemented as an RFID chip including an RFID antenna and a pressure sensor.

<FIG> is a perspective view of a non-limiting embodiment or aspect of an implementation <NUM> relating to tracking device <NUM> shown in <FIG>. In some non-limiting embodiments or aspects, tracking device <NUM> may be the same as or similar to tracking device <NUM> as described herein. In some non-limiting embodiments or aspects, tracking device <NUM> is sealed within and/or integrally formed within another device. For example, as shown in <FIG>, first tracking device 500a is sealed within syringe <NUM> and second tracking device 500b is sealed within Luer connector <NUM>.

<FIG> are perspective views of non-limiting embodiments or aspects of an implementation <NUM> relating to tracking device <NUM> shown in <FIG>. As shown in <FIG>, tracking device <NUM> may include controller <NUM>, antenna <NUM>, and sensor <NUM> provided on tag or carrier <NUM>. In some non-limiting embodiments or aspects, controller <NUM> may be the same as or similar to controller <NUM> as described herein, antenna <NUM> may the same as or similar to antenna <NUM> as described herein, sensor <NUM> may be the same as or similar to sensor <NUM> described herein, and tag or carrier <NUM> may be the same as or similar to tag or carrier <NUM> described herein.

In some non-limiting embodiments or aspects, as shown in <FIG>, tracking device <NUM> comprises tag or carrier <NUM> including wings 610a and 610b. As an example, tag or carrier <NUM> is flexible so that tag or carrier <NUM> can be wrapped or bent around a medical device, such as IV bag connector <NUM>, syringe <NUM>, Luer connection of IV set <NUM>, IV bag access spike <NUM>, closed system transfer device <NUM>, and the like. For example, wings 610a and 610b comprise removable adhesive backing <NUM> such that when adhesive backing <NUM> is removed and wings 610a and 610b are connected to one another with tag or carrier <NUM> wrapped around a medical device, such as around IV bag connector <NUM> as shown in <FIG>, tracking device <NUM> is secured to the medical device. <FIG> shows tracking device <NUM> attached to IV bag connector <NUM>. <FIG> shows first tracking device 600a attached to a Luer connection of syringe <NUM> and second tracking device 600b attached to a Luer connection of IV set <NUM> to be connected to the Luer connection of syringe <NUM>. As an example, Luer connection of syringe <NUM> activates or actuates a sensor of tracking device 600b when connected to or disconnected from Luer connection of IV set <NUM>, and Luer connection of IV set <NUM> activates or actuates a sensor of tracking device 600a when connected to or disconnected from Luer connection of syringe <NUM>. For example, tracking devices 600a and 600b are positioned or located proximate openings or ends of the Luer connectors such that a pressure on or an amount of light received by sensors of the tracking devices 600a or 600b changes with IV set <NUM> and syringe <NUM> are connected and disconnected from one another. <FIG> shows tracking device <NUM> attached to IV bag access spike <NUM>. <FIG> shows tracking device <NUM> wrapped around a closed system transfer device connector <NUM>.

In some non-limiting embodiments or aspects, as shown in <FIG>, tracking device <NUM> comprises a sleeve having a cylindrical shape. For example, as shown in <FIG>, tag or carrier <NUM> is configured to be applied around syringe <NUM> and/or around a Luer connector of syringe <NUM>. Sensor <NUM> may be located at a distal end of the cylindrically shaped sleeve such that sensor <NUM> is located proximate a distal end of the Luer connector of syringe <NUM> when tracking device <NUM> is connected to the syringe <NUM> so that sensor <NUM> is configured to be physically actuated in response to connection of the Luer connector of syringe <NUM> to another medical device.

Referring now to <FIG>, a process <NUM> is shown for identifying device connections in a connection area. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by one or more receivers <NUM>. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by another system, another device, another group of systems, or another group of devices, separate from or including one or more receivers <NUM>, such as remote computing device <NUM> and/or transmission sources <NUM>. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by receiver <NUM>, which may be a computing device, such as a tablet computer, that executes cloud-based software that provides a user interface and delivers cloud-based APIs to the receiver <NUM>.

As shown in <FIG>, process <NUM> includes a step <NUM> of receiving, with at least one processor, a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, wherein the plurality of physical parameters indicates physical states of the plurality of devices. At a step <NUM>, at least one processor determines at least one physical connection state between the plurality of devices based on the plurality of physical parameters of the plurality of devices. At a step <NUM>, at least one processor monitors and/or controls the plurality of devices based on the at least one physical connection state between the plurality of devices.

In some non-limiting embodiments or aspects, a physical parameter of a device may change according to a physical state of the device. As described herein, a device may comprise a medical device, such as one or more of the following: a syringe, an IV spike, an IV access site, an IV bag, an IV set, a catheter, a medical device connector, or any combination thereof. In some non-limiting embodiments or aspects, a physical parameter can indicate a finite set of states of a physical state of a device. For example, a physical parameter may indicate a connected state or a disconnected state of a device, such as a catheter connected or disconnected state with a patient and/or an IV set, a syringe connected or disconnected state with an IV set, and the like. In some non-limiting embodiments or aspects, a physical parameter can indicate a magnitude of change in a physical state of a device. For example, a physical parameter may indicate a level or a strength of a connection of a device, for example, from a fully disconnected level to a fully connected level. A level of a connection that is less than a fully connected level may indicate an incorrect or improper connection of a device to another device. For example, a pressure sensor may sense a pressure at a Luer connection of a syringe as a physical parameter, and a sensed pressure less than a threshold pressure may indicate that the syringe is not fully connected or is improperly connected to another device, such as an IV set.

In some non-limiting embodiments or aspects, the plurality of physical parameters is associated with a plurality of event times, wherein the plurality of event times indicates times of changes in the physical states of the plurality of devices. As an example, at least one first event time may be associated with at least one first device physical parameter, (e.g., activation of a first device and/or a sensor associated with the first device), and at least one second event time may be associated with at least one second device physical parameter, (e.g., activation of a second device and/or a sensor associated with the first device). For example, a transmission source <NUM> automatically updates and/or transmits a physical parameter in response to a change in the physical parameter, for example, in response to activation of a device <NUM> and/or a sensor <NUM> of a tracking device <NUM> associated with a device <NUM>, and/or transmits an updated physical parameter in response to polling from a receiver <NUM>. In some non-limiting embodiments, a transmission sources <NUM> transmits an event time associated with the updated physical parameter. In some non-limiting embodiments, a receiver <NUM> determines an event associated with the updated physical parameter based on a time at which a signal including the updated physical parameter is received.

In some non-limiting embodiments or aspects, the plurality of physical parameters indicate a plurality of different physical states of the plurality of devices. For example, a first physical parameter may indicate an optically sensed physical state of a device, such as a covered Luer connection of a syringe, and a second physical parameter may indicate a physically sensed physical state of a device, such as a pressure on a Luer connection of a syringe. In some non-limiting embodiments or aspects, a physical parameter may include information that indicates at least one predetermined connection state between two or more connectors of a plurality of connectors of at least one device. For example, a physical parameter may indicate a valve open state or a valve closed state of a valve between connection ports of an IV set. In some non-limiting embodiment or aspects, a physical parameter may be associated with a device identifier that uniquely identifies a device, a connector of a device, a type of device, or any combination thereof. For example, a device identifier may uniquely identify one or more of the following: a type of IV set, the IV set from all other IV sets of that type, individual connectors or connections of the IV set, or any combination thereof. As an example, if it is not physically possible to form a connection, but it is determined that a connection has been made based on the physical parameters and/or event times, device identifiers can be used to further characterize the connection. For example, by comparing device identifiers associated with devices determined as connected, it can be determined that a detection or system error condition has occurred, devices are being misused, and/or simultaneous connections are being made between two or more pairs of devices and correct pairings can be determined.

In some non-limiting embodiments or aspects, at least one physical parameter of the plurality of physical parameters includes a plurality of connection parameters that indicates physical states of a plurality of connectors of at least one device of the plurality of devices. For example, at least one device of the plurality of devices may comprise a plurality of connectors configured to be physically connected to at least one of the following: a patient, the at least one second device, at least one third device, one or more connectors of the at least one second device, one or more connectors of the at least one third device, or any combination thereof, and the at least one physical parameter physical parameter may include a plurality of connection parameters that indicates physical states of the plurality of connectors of the at least one device. For example, an IV set may include a first connector at a first end of a flow path and a second connector at a second end of the flow path, wherein a physical state of the first connector is indicated by a first physical parameter sensed by a first sensor and a physical state of the second connector is indicated by a second physical parameter sensed by a second sensor.

Referring now to <FIG>, a process <NUM> is shown for identifying device connections in a connection area. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by one or more transmission sources <NUM> and/or tracking devices <NUM>. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by another system, another device, another group of systems, or another group of devices, separate from or including one or more transmission sources <NUM> and/or tracking devices <NUM>, such as remote computing device <NUM> and/or one or more receivers <NUM>.

As shown in <FIG>, process <NUM> includes a step <NUM> of sensing, with a plurality of sensors on the plurality of devices, the physical states of the plurality of devices to determine the plurality of physical parameters. For example, at least one first sensor on at least one first device may sense at least one physical state of the at least one first device to determine at least one first physical parameter of the at least one first device, and at least one second sensor on at least one second device may sense at least one physical state of the at least one second device to determine at least one second physical parameter of the at least one second device. In a step <NUM>, a plurality of transmission sources on the plurality of devices transmit the plurality of physical parameters. For example, at least one first transmission source on the at least one first device may transmit the at least one first physical parameter of the at least one first device, and at least one second transmission source on the at least one second device may transmit the at least one second physical parameter of the at least one second device.

In some non-limiting embodiments or aspects, a transmission source <NUM> transmits physical parameters in response to entering a connection area, in response to receiving a polling signal, and/or in response to a change in a physical state of a device associated with the transmission source <NUM>. As an example, the at least one first transmission source may transmit the at least one first physical parameter in response entering the connection area, and the at least one second transmission source may transmit the at least one second physical parameter in response to entering the connection area. As an example, an RFID transmission source may automatically transmit a physical parameter upon entering a connection area, e.g., in response to being polled by an RFID reader. The RFID transmission source may continuously transmit the physical parameter while in the connection area, transmit the physical parameter at periodic intervals while in the connection area, and/or transmit the physical parameter only in response to actuation of a sensor of the RFID transmission source after an initial transmission in response to polling by an RFID reader upon entering in the connection area. In some non-limiting embodiments or aspects, the at least one first transmission source may transmit the at least one first physical parameter in response to the at least one first sensor sensing a change in the at least one physical state of the at least one first device, and the at least one second transmission source may transmit the at least one second physical parameter in response to the at least one second sensor sensing a change in the at least one physical state of the at least second first device. For example, a transmission source <NUM> transmits a physical parameter in response to a sensor <NUM> of a tracking device <NUM> that implements the transmission source <NUM> sensing a change in a physical state of a device associated with the transmission source <NUM>.

Referring now to <FIG>, a process <NUM> is shown for identifying device connections in a connection area. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by one or more receivers <NUM>. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by another system, another device, another group of systems, or another group of devices, separate from or including one or more receivers <NUM>, such as remote computing device <NUM> and/or transmission sources <NUM>. In some non-limiting embodiments or aspects, one or more of the steps of process <NUM> may be performed (e.g., completely, partially, etc.) by a receiver <NUM>, which may be a computing device, such as a tablet computer, that executes cloud-based software that provides a user interface and delivers cloud-based APIs to the receiver <NUM>.

As shown in <FIG>, process <NUM> includes a step of <NUM> of determining, with at least one processor, a device event associated with a connection area. At a step <NUM>, at least one processor determines an effect of the device event. At a step <NUM>, at least one processor updates a device register based on the determined effect of the device event.

In some non-limiting embodiments or aspects, a device register includes a list of devices, also referred to herein as nodes, in a connection area. Devices in the list are identified by device identifiers, and device identifiers are stored in association with physical parameters associated with the devices, event times associated with the physical parameters, and/or indications of connections and/or disconnections between devices. The information in a device register can be used to build or generate a computer-based logical branch structure of physical devices in a connection area. As an example, a logical branch structure maps to a physical branch structure in the connection area and includes nodes corresponding to points of entry into the physical device structure. For example, a logical branch structure of a physical branch structure for a physical IV branch structure including a fluid flow path includes nodes at points of entry to the fluid flow path, e.g., at fluid inputs and fluid outputs. A logical branch structure may include predetermined device associations or connections, e.g., between nodes/ends of a catheter, and/or detected device associations or connections, e.g., between a syringe and a node/end of the catheter connected in the connection area.

In some non-limiting embodiments or aspects, step <NUM> includes receiving a device identifier and/or at least one physical parameter associated with at least one device of the plurality of devices. For example, a receiver <NUM> determines a device event in response to receiving a signal including the at least one physical parameter and the device identifier associated with the at least one device. Step <NUM> may include determining that the at least one device of the plurality of devices is within the connection area. As an example, a receiver <NUM> compares the device identifier of the device with a current device register including a list of devices in the connection area to determine if the device associated with the device identifier is already registered or is a new device that has entered the connection area. Step <NUM> may include updating the device register including the list of devices in the connection area with the device identifier in association with the at least one physical parameter of the at least one device and/or reporting the updated device register to at least one remote computing system. A device identifier can be stored in the device register in association with any other information or data associated with the at least one device and/or received in a signal associated with the device identifier, e.g., information or data received from or associated with a transmission source, a connection area, a patient identifier of a patient, a medication identifier of a medication, or any combination thereof.

In some non-limiting embodiments or aspects, step <NUM> includes polling the connection area and determining responses to the polling. As an example, a receiver <NUM> polls a connection area <NUM> and determines a device event in response the polling. For example, a receiver receives responses from transmission sources <NUM> associated with devices currently in the connection area, but the receiver <NUM> does not receive responses from transmission sources <NUM> outside the connection area during the polling. Step <NUM> may include determining based on the responses to the polling an updated list of devices currently in the connection area. For example, if the at least one device is listed in the device register, but does not respond to the polling within a predetermined polling time period, a receiver <NUM> determines that the at least one device is no longer in the connection area. Step <NUM> may include updating the device register to remove the device identifier of the at least one device from the device register, updating connections of any devices identified as connected to the at least one device in the device register as described herein in more detail below, and/or reporting the updated device register to at least one remote computing system.

In some non-limiting embodiments or aspects, step <NUM> includes receiving the plurality of physical parameters in association with a plurality of event times (e.g., a time stamp associated with a change in a physical parameter sensed by a corresponding sensor and/or a time stamp associated with transmission of a physical parameter by a corresponding transmission source) and/or associating the plurality of physical parameters with event times as the plurality of physical parameters are received (e.g., a time stamp associated with a reception of a physical parameter by a receiver). As an example, the plurality of physical parameters is associated with a plurality of event times, and the plurality of event times indicates times of changes in the physical states of the plurality of devices. For example, a tracking device <NUM> as described herein and connected to a syringe activates when the syringe is connected to an IV connector (e.g., a female Luer), which causes the syringe tracking device <NUM> to transmit a signal to a receiver <NUM>. Similarly, a tracking device <NUM> as described herein and connected to the IV connector activates when the IV connector is connected to the syringe (e.g., a male Luer), which causes the IV connector tracking device <NUM> to transmit a signal to a receiver <NUM>. A receiver <NUM> may determine a device event in response to receiving a signal including a physical parameter in association with an event time.

In some non-limiting embodiments, at step <NUM>, at least one physical connection state between the plurality of devices is determined based at least partially on the plurality of event times. As an example, at least one processor determines whether the plurality of event times are within a sliding time window. For example, when two or more device events happen within a predetermined time interval with compatible devices (e.g., compatibility as indicated by device identifiers), a connection of the two or more devices can be determined. A receiver <NUM> and/or remote computing device <NUM> can determine if the two or more events happen within a sliding time window. As an example, at least one first event time associated with the at least one first device physical parameter and at least one second event time associated with the at least one second device physical parameter are received, and the at least one connection state is determined based on the at least one first even time and the at least one second event time. For example, if the at least one first event time and the at least one second event time each occur within a predetermined time of each other, e.g., <NUM> seconds, the receiver <NUM> and/or remote computing device <NUM> determines that the two or more devices associated with the at least one first even time and the at least one second event time are associated with one another.

In some non-limiting embodiments or aspects, the at least one connection state between the plurality of devices is determined based at least partially on at least one predefined compatibility of the plurality of devices. As an example, when device identifiers for two or more devices are received within a sliding time window, a receiver <NUM> and/or remote computing device <NUM> determines based on the device identifiers whether the two or more devices are compatible with one another. For example, the receiver <NUM> and/or remote computing device <NUM> can consult a look-up of acceptable states and connections for devices associated with the device identifiers. If the two or more devices are determined to be incompatible, the receiver <NUM> and/or remote computing device <NUM> can issue an alert that the two or more devices, which are associated with one another, are being misused. If the two or more devices are determined to be compatible, the receiver <NUM> and/or remote computing device <NUM> can determine a connection between the two devices and update the device register to include an indication of the connection in association with the device identifiers of the devices, a time of the connection, and/or physical parameters of the devices.

In some non-limiting embodiments or aspects, the plurality of physical parameters include information or data indicating a connection state of the plurality of physical devices. For example, a physical parameter can indicate a connected state, a disconnected state, and/or a level of connection of a device and/or a node or connector of a device. If the physical parameters associated with the at least one first event time and the at least one second event time indicate connected states, a receiver <NUM> and/or remote computing device <NUM> determines that the devices are now connected and updates the device register. If the physical parameters associated with the at least one first event time and the at least one second event time indicate disconnected states, the receiver <NUM> and/or remote computing device <NUM> determines that the devices are now disconnected.

It is noted herein that in addition to the detection of various states of connection/disconnection, the system can also be utilized to monitor preparation and/or maintenance of the fluid path. For example, other events that can be captured include disinfection of a component of the system, capping/decapping of a component of the system, and monitoring placement of component into or out of the system (such as monitoring placement of a catheter securement device). It is also contemplated herein that the system can detect additional disinfection processes, such as the preparation of an IV site with an antimicrobial agent.

If the physical parameters associated with the at least one first event time and the at least one second event time indicate non-matching states (e.g., a disconnected state and a connected state) and/or a level of connection below a threshold connection level, the receiver <NUM> and/or remote computing device <NUM> determines an error condition and provides an alert based on the error condition. As an example, a receiver <NUM> and/or remote computing device <NUM> compares the device identifiers of the two or more devices having device events within the sliding time window to the device register to determine if the devices are currently associated or connected. If the devices are currently connected, the receiver <NUM> and/or remote computing device <NUM> determines that the devices are now disconnected based on the at least one first event time and the at least one second event time occurring within the predetermined time of each other. If the devices are not currently connected in the device register, the receiver <NUM> and/or remote computing device <NUM> determines that the devices are now associated and/or connected to one another. In some non-limiting embodiments or aspects, a receiver determines whether a disconnection of two or more devices is a permissible disconnection, (e.g., by consulting a look-up table of acceptable states and connections associated with the device identifiers). For example, if physical parameters for the two or more devices, which are stored as connected in the device register, are received that indicate different states, e.g., a connected state and a disconnected state, a receiver <NUM> determines an error condition and outputs an alert indicating that a detection or system error condition has occurred and/or that the two medical devices are being misused. Furthermore, the system can send data from other sensors that detect problems with a system component, such as a catheter, an IV set, and/or a patient. The system can provide healthcare workers with alerts for errors or other clinical issues, system analytics, and workflow based on data from the system.

In some non-limiting embodiments or aspects, a receiver <NUM> and/or remote computing device <NUM> associated with a connection area can filter or reject signals from transmission sources associated with devices of neighboring patients (e.g., devices in other connection areas). Due to complexities in RF signal propagation, device events that occur in other connection areas may sometimes be improperly detected. As an example, a receiver <NUM> and/or remote computing device <NUM> can compare a device identifier of a signal received from a transmission source to a device register for another connection area(s) to determine whether the transmission source and/or a medical device associated with the transmission source are registered in the other connection area and/or associated or connected to another device within the other connection area. If the device is already registered and/or connected in the other connection area, the receiver <NUM> and/or remote computing device <NUM> can reject registration of the device in the connection area associated with the receiver <NUM>. In some non-limiting embodiments or aspects, a connection area is associated with a predefined list of acceptable devices, and the receiver <NUM> and/or remote computing device <NUM> compares the device identifier of a signal received from a transmission source to the list of acceptable devices to determine whether the transmission source and/or a medical device associated with the transmission source can be registered in that connection area and/or connected to another device within that connection area.

Referring again to <FIG>, in some non-limiting embodiments or aspects, step <NUM> includes controlling a flow of a fluid in a fluid flow path including at least one device of the plurality of devices based at least partially on the at least one physical connection state between the plurality of devices. For example, by using a device register including physical structures of medical devices and connections between medical devices, including where transmission sources are located relative to the physical fluid flow path, a tree structure of the fluid flow path, (e.g., IV system) is established, e.g., a logical branch structure. A receiver <NUM> and/or remote computing device <NUM> monitor each point of entry to the fluid flow path that enables fluid to be delivered to the patient. For example, sensors at each point of entry, which may be sensors <NUM> of tracking devices <NUM> or separate sensors configured to communicate sensed data associated with the fluid flow path to the receiver <NUM> and/or remote computing device <NUM>, and the receiver <NUM> and/or remote computing device <NUM> can issue an alert and/or control one or more devices in the fluid flow path to stop the fluid flow and/or adjust the fluid flow, e.g., using one or more electronically controlled valves, based on the sensed data, e.g., in response sensed data indicating that devices in the fluid flow path have been disconnected.

In some non-limiting embodiments or aspects, step <NUM> includes receiving a patient identifier associated with a patient, receiving a medication identifier of a medication to be delivered to the patient via the fluid flow path, associating the patient identifier and the medication identifier with the at least one device of the fluid flow path and controlling the flow of the fluid in the fluid flow path based at least partially on the patient identifier and the medication identifier. As an example, sensors at each point of entry to the fluid flow path, which may be sensors <NUM> of tracking devices <NUM> or separate sensors configured to communicate sensed data associated with the fluid flow path to the receiver <NUM> and/or remote computing device <NUM>, are configured to determine at least one of the following: a connection state at a point of entry, a volume of fluid in the fluid flow path and/or at a point of entry, a type of fluid or medication in the fluid flow path and/or at the point of entry, a flow rate of fluid in the fluid flow path and/or at a point of entry, or any combination thereof. For example, a receiver <NUM> and/or remote computing device <NUM> compare medication, medication dosage, medication delivery route, and/or medication delivery time determined based on the sensed data to an approved patient, approved medication, approved medication dosage, approved medication delivery route, and/or approved medication delivery time associated with the patient identifier and/or the medication identifier to reduce medication administration errors. The receiver <NUM> and/or remote computing device <NUM> can issue an alert and/or control one or more devices in the flow path to stop fluid flow and/or adjust fluid flow based on the sensed data, the patient identifier, and/or the medication identifier. For example, if a medication sensed at a point of entry in the fluid flow path is determined to be an improper medication for the patient, an improper dosage for the patient and/or medication, an improper medication delivery route for the patient and/or medication (e.g., improper point of entry to the fluid flow path), and/or an improper medication delivery time for the patient and/or medication, the receiver <NUM> and/or remote computing device <NUM> can issue an alert and/or control one or more devices in the flow path to stop the fluid flow.

In some non-limiting embodiments or aspects, step <NUM> includes generating, with at least one processor, a digital representation of a fluid flow path including at least one device of the plurality of devices based at least partially on the at least one physical connection state between the plurality of devices; and monitoring, with at least one processor, a flow of a fluid in the fluid flow path based at least partially on the representation of the fluid flow path. As an example, the at least one processor can control an audio and/or visual output device to output an audible and/or visible indication in the connection area, wherein the audible and/or visible indication indicates a status of the fluid flow path. For example, the receiver <NUM> and/or remote computing device <NUM> can generate a logical IV branch structure that maps to a physical IV branch structure in the connection area and includes a unique node identifier for each medical device of the physical IV branch structure, each connector or entry/exit point to a fluid flow path formed by the medical devices, and/or each element of a medical device associated with an action that can affect the fluid flow path, (e.g., a valve in a medical device), in a connection area. The logical IV branch structure includes connections between nodes, which can be nodes connected in the connection area and/or predetermined node connections, such as nodes associated with a same medical device and/or nodes connected outside the connection area that enter the connection area already connection to one another. An example physical IV branch structure mapped to a logical IV branch structure is described in more detail herein below with respect to <FIG>.

<FIG> is a diagram of an overview of a non-limiting embodiment or aspect of an implementation <NUM> relating to processes <NUM>, <NUM>, and <NUM> shown in <FIG>. As shown in <FIG>, implementation <NUM> may include connection area <NUM>, receiver <NUM>, transmission sources <NUM> associated with medical devices <NUM>, network <NUM>, and/or remote computing device <NUM>. In some non-limiting embodiments or aspects, connection area <NUM> may be the same as or similar to connection area <NUM> as described herein above, receiver <NUM> may the same as or similar to receiver <NUM> as described herein above, transmission sources <NUM> may be the same as or similar to transmission sources <NUM> and/or tracking devices <NUM> described herein above, network <NUM> may be the same as or similar to network <NUM> as described herein above, and remote computing device <NUM> may be the same as or similar to remote computing device <NUM> as described herein above.

It is noted that implementation <NUM> is described primarily with respect to receiver <NUM> performing one or more functions referenced by reference numbers in <FIG>; however, additionally, or alternatively, a remote system or server, such as remote computing device <NUM>, or one or more other receivers in communication with receiver <NUM>, such as a receiver configuration of implementation <NUM> as shown in <FIG>, or a cloud-based server of a cloud-based receiver in which receiver <NUM> comprises a user device, such as a tablet computer, that communicates with the cloud-based server, may perform one or more functions referenced by the reference numbers in <FIG>.

<FIG> is a diagram of devices of implementation <NUM>. As shown in <FIG>, implementation <NUM> includes medical devices <NUM> comprising IV catheter <NUM>, IV set <NUM>, first drug syringe <NUM>, second drug syringe <NUM>, and flush syringe <NUM>. Each medical device <NUM> has a transmission device <NUM>, e.g., a tracking device <NUM> as shown in <FIG>, at each node where a fluid connection can be made, e.g., at each fluid inlet and each fluid outlet, and each tracking device or node is associated with a unique device or node identifier. The tracking devices at each node are referred to herein with the same numerical label as associated with the corresponding node identifiers of the tracking devices in <FIG>. For example, IV catheter <NUM> comprises tracking devices associated with node identifiers <NUM> and <NUM>, IV set <NUM> comprises tracking devices associated with node identifiers <NUM> and <NUM>, first drug syringe <NUM> comprises a tracking device associated with node identifier <NUM>, second drug syringe <NUM> comprises a tracking device associated with node identifier <NUM>, and flush syringe <NUM> comprises a tracking device associated with node identifier <NUM>. The tracking devices or nodes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are located at fluid entry points and fluid exit points of the medical devices <NUM>.

<FIG> is a table of example data of implementation <NUM>. <FIG> shows an example device register database, which is populated as time progresses, with data received from and processed by receiver <NUM> and/or remote computing device <NUM> associated with connection area <NUM>. Time index, which can be any number of seconds per interval, is mapped to a time range on a real-time clock. Device Register is a listing of devices within connection area <NUM> in association with the physical parameters of the devices. Coincidence Logic indicates when device nodes are associated with one another, (e.g., x + y indicates association of device nodes x and y, x - y indicates disassociation of device nodes x and y).

Referring now to <FIG>, as shown by reference number <NUM> in <FIG>, a medical device <NUM> enters connection area <NUM>. For example, at time index <NUM> in <FIG>, there are no medical devices in the connection area <NUM>, e.g., there are no medical devices <NUM> listed in the device register. At time index <NUM>, catheter <NUM> enters the connection area. Receiver <NUM> receives a signal from the tracking devices associated with node identifiers <NUM> and <NUM>, e.g., in response to polling from receiver <NUM>, including the node identifiers <NUM> and <NUM> and a physical parameter associated with each node identifier, and updates the device register with the node identifiers <NUM> and <NUM> in association with inactive states. For example, in implementation <NUM> a physical parameter indicates that a node identifier associated with the physical parameter is in one of an active state, e.g., a data bit <NUM>, and an inactive state, e.g., a data bit <NUM>. Node identifiers <NUM> and <NUM> are associated with inactive state <NUM> by receiver <NUM> in the device registered based on the received physical parameters.

At time index <NUM>, catheter <NUM> is placed or deployed. For example, a cannula of catheter <NUM> associated with node identifier <NUM> is inserted into a patient. A sensor of the tracking device associated with node identifier <NUM> is activated in response to deployment of the catheter, which causes the tracking device associated with node identifier <NUM> to transmit a signal including node identifier <NUM> associated with a physical parameter indicating an active state of the node <NUM>. Receiver <NUM> receives the signal, determines that no other node identifiers with active state physical parameters were received within a sliding time window, e.g., within <NUM> seconds of receipt of the signal associated with node identifier <NUM>, determines that an active state physical parameter associated with node identifier <NUM> without node identifier <NUM> being associated with another node identifier is permissible for node identifier <NUM>, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with active state <NUM> and node identifier <NUM> associated with inactive state <NUM>.

At time index <NUM>, IV set <NUM> including tracking devices associated with node identifiers <NUM> and <NUM> enters the connection area <NUM>, and node identifers143 and <NUM> are added to the device register in associated with inactive state <NUM>, for example, in a manner similar to that as described herein above with respect to reference number <NUM>.

As shown by reference number <NUM> in <FIG>, a medical device <NUM> is connected with another medical device <NUM> in connection area <NUM>. For example, at time index <NUM>, IV set <NUM> is connected to catheter <NUM>. For example, a connector of catheter <NUM> associated with node identifier <NUM> is connected to a connector of IV set <NUM> associated with node identifier <NUM>. Sensors of the tracking devices associated with node identifiers <NUM> and <NUM> are activated in response to the connection, e.g., a pressure is applied to pressure sensors of the tracking devices by connectors of the connecting devices, which causes the tracking devices associated with node identifiers <NUM> and <NUM> to respectively transmit a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM> and a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM>. Receiver <NUM> receives the signals, determines that the signals were generated, transmitted and/or received within the sliding time window, e.g., within <NUM> seconds of each other, determines that a connection of node identifier <NUM> and <NUM> is a permissible connection, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with active state <NUM> and node identifier <NUM> associated with active state <NUM>, and to include an indication that node <NUM> and node <NUM> are connected to one another, e.g., coincidence logic <NUM> + <NUM>.

At time index <NUM>, first drug syringe <NUM> including a tracking device associated with node identifier <NUM> enters the connection area <NUM>, and node identifier <NUM> is added to the device register in association with inactive state <NUM>, for example, in a manner similar to that as described herein above with respect to reference number <NUM>.

At time index <NUM>, IV set <NUM> is connected to first drug syringe <NUM>. For example, the connector of IV set <NUM> associated with node identifier <NUM> is connected to a connector of first drug syringe <NUM> associated with node identifier <NUM>. Sensors of the tracking devices associated with node identifiers <NUM> and <NUM> are activated in response to the connection, which causes the tracking devices associated with node identifiers <NUM> and <NUM> to respectively transmit a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM> and a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM>. Receiver <NUM> receives the signals, determines that the signals were received within the sliding time window, e.g., within <NUM> seconds of each other, determines that a connection of node identifiers <NUM> and <NUM> is a permissible connection, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with active state <NUM> and node identifier <NUM> associated with active state <NUM>, and to include an indication that node <NUM> and node <NUM> are connected to one another, e.g., coincidence logic <NUM> + <NUM>.

As shown by reference number <NUM> in <FIG>, a medical device <NUM> is disconnected from another medical device <NUM> in connection area <NUM>. As an example, at time index <NUM>, IV set <NUM> is disconnected from first drug syringe <NUM>. For example, the connector of IV set <NUM> associated with node identifier <NUM> is disconnected from the connector of first drug syringe <NUM> associated with node identifier <NUM>. Sensors of the tracking devices associated with node identifiers <NUM> and <NUM> are activated in response to the disconnection, e.g., a pressure on pressure sensors of the tracking devices is removed because the devices are no longer connected, which causes the tracking devices associated with node identifiers <NUM> and <NUM> to respectively transmit a signal including node identifier <NUM> associated with a physical parameter indicating an inactive state <NUM> of the node <NUM> and a signal including node identifier <NUM> associated with a physical parameter indicating an inactive state <NUM> of the node <NUM>. Receiver <NUM> receives the signals, determines that the signals were received within the sliding time window, e.g., within <NUM> seconds of each other, determines that a disconnection of node identifiers <NUM> and <NUM> is a permissible disconnection, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with inactive state <NUM> and node identifier <NUM> associated with inactive state <NUM>, and to include an indication that node <NUM> and node <NUM> are now disconnected from one another, e.g., coincidence logic <NUM> - <NUM>. In some non-limiting embodiments or aspects, if signals for node identifiers <NUM> and <NUM>, which are stored as connected in the device register, are received that indicate different states, e.g., an activate state <NUM> for node identifier <NUM> and an inactive state <NUM> for node identifier <NUM>, receiver <NUM> determines an error condition and outputs an alert indicating that a detection or system error condition has occurred and/or that medical devices <NUM> and/or <NUM> are being misused.

As shown by reference number <NUM> in <FIG>, a medical device <NUM> leaves connection area <NUM>. For example, at time index <NUM> in <FIG>, first drug syringe <NUM> including node identifier <NUM> is in the connection area <NUM>, e.g., node identifier <NUM> is listed in the device register. At time index <NUM>, first drug syringe <NUM> leaves connection area <NUM>. Receiver <NUM> determines that node identifier <NUM> which is listed in the device register at time index <NUM>, is now outside connection area <NUM> based on a lack of a response within a polling period from the tracking device associated with node identifier <NUM> to polling of connection area <NUM>. For example, receiver <NUM> does not receive a signal including node identifier <NUM> in the polling period. Based on the lack of response, node identifier <NUM> is removed from the device register by the receiver <NUM>.

At time index <NUM>, second drug syringe <NUM> including a tracking device associated with node identifier <NUM> enters the connection area <NUM>, and node identifier <NUM> is added to the device register in associated with inactive state <NUM>, for example, in a manner similar to that as described herein above with respect to reference number <NUM>.

At time index <NUM>, flush syringe <NUM> including a tracking device associated with node identifier <NUM> enters the connection area <NUM>, and node identifier <NUM> is added to the device register in associated with inactive state <NUM>, for example, in a manner similar to that as described herein above with respect to reference number <NUM>.

At time index <NUM>, the connector of IV set <NUM> associated with node identifier <NUM> is connected to the connector of flush syringe <NUM> associated with node identifier <NUM>. Sensors of the tracking devices associated with node identifiers <NUM> and <NUM> are activated in response to the connection, which causes the tracking devices associated with node identifiers <NUM> and <NUM> to respectively transmit a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM> and a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node <NUM>. Receiver <NUM> receives the signals, determines that the signals were received within the sliding time window, e.g., within <NUM> seconds of each other, determines that a connection of node identifiers <NUM> and <NUM> is a permissible connection, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with active state <NUM> and node identifier <NUM> associated with active state <NUM>, and to include an indication that node <NUM> and node <NUM> are connected to one another, e.g., coincidence logic <NUM> + <NUM>.

At time index <NUM>, IV set <NUM> is disconnected from flush syringe <NUM>. For example, the connector of IV set <NUM> associated with node identifier <NUM> is disconnected from the connector of flush syringe <NUM> associated with node identifier <NUM>. Sensors of the tracking devices associated with node identifiers <NUM> and <NUM> are activated in response to the disconnection, which causes the tracking devices associated with node identifiers <NUM> and <NUM> to respectively transmit a signal including node identifier <NUM> associated with a physical parameter indicating an inactive state <NUM> of the node and a signal including node identifier <NUM> associated with a physical parameter indicating an active state <NUM> of the node. Receiver <NUM> receives the signals, determines that the signals were received within the sliding time window, e.g., within <NUM> seconds of each other, determines that a disconnection of node identifiers <NUM> and <NUM> is a permissible disconnection, (e.g., by consulting a look-up table of acceptable states and connections for node identifiers/devices), and updates the device register to include node identifier <NUM> associated with inactive state <NUM> and node identifier <NUM> associated with inactive state <NUM>, and to include an indication that node <NUM> and node <NUM> are now disconnected from one another, e.g., coincidence logic <NUM> - <NUM>. In some non-limiting embodiments or aspects, if signals for node identifiers <NUM> and <NUM>, which are stored as connected in the device register <NUM> + <NUM>, are received that indicate different states, e.g., an activate state <NUM> for node identifier <NUM> and an inactive state <NUM> for node identifier <NUM>, receiver <NUM> determines an error condition and outputs an alert indicating that a detection or system error condition has occurred and/or that medical devices <NUM> and/or <NUM> are being misused.

At time index <NUM>, the device register includes information indicating a logical branch structure including predetermined device associations or connections, (e.g., between nodes/connectors <NUM> and <NUM> of catheter <NUM> and between nodes/connectors <NUM> and <NUM> of IV set <NUM> catheter, and/or detected device associations or connections, (e.g., between a node/connector <NUM> of catheter <NUM> node/connector <NUM> of IV set <NUM>). Based on the logical branch structure, receiver <NUM> can determine that catheter <NUM> has a node <NUM> with a male Luer connector that is in fluid communication with a node <NUM> of IV set <NUM>, a male Luer connector, and that fluid entering node <NUM> of IV set <NUM> flows through the connection of nodes <NUM> and <NUM> and exits node <NUM> of catheter <NUM>. It is noted that with more complex IV sets with a greater number of connections/nodes, a branch structure is built using multiple nodes as multiple connection points as described in more detail herein below with respect to <FIG>.

Claim 1:
A system for identifying device connections in a connection area defined by a range of a wireless communication network between one or more receivers and one or more transmission sources, comprising at least one computer including at least one processor, the at least one computer programmed and/or configured to:
receive a plurality of physical parameters of a plurality of devices from a plurality of transmission sources in a connection area, wherein the plurality of physical parameters indicates identity and/or physical states of the plurality of devices; and
determine at least one identity and/or physical connection state between the plurality of devices based on the plurality of physical parameters of the plurality of devices,
wherein the plurality of physical parameters is associated with a plurality of event times, wherein the plurality of event times indicates times of changes in the physical states of the plurality of devices, and wherein the at least one computer is programmed and/or configured to determine the at least one physical connection state based on the plurality of physical parameters of the plurality of devices and the plurality of event times associated with the plurality of physical parameters such that when two or more event times happen within a predetermined time interval with two or more compatible devices, the at least one physical connection state between the two or more compatible devices is determined as changed from a current physical connection state between the two or more compatible devices.