Systems, methods, and articles of manufacture for determining lumens

Abstract

To provide an improved system, device, product, apparatus, and / or method for identifying a lumen.SOLUTION: A visual indicator of a smart device and a visual indicator of a medication source device may be controlled to produce a same type of visual output based on a communication established between the medication source device and the smart device. The medication source device may be connected to a lumen, the smart device may be configured to be connected to the lumen, and the same type of visual output may be associated with the lumen.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to systems, methods, and articles of manufacture for identifying a lumen. [Background technology]

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 62 / 800,609, entitled "System, Method, and Product for Identifying a Lumen," filed February 4, 2019, the disclosure of which is incorporated herein by reference in its entirety.

[0003] A patient may be connected to multiple lumens or fluid lines (e.g., IV lines, etc.). For example, a patient may be connected to multiple channels of an infusion pump system that includes multiple infusion pumps. As an example, a patient in an emergency room may be connected to ten or more fluid lines at the same time. Multiple fluid lines may cause confusion as to which patient's fluid line connects to which infusion pump or fluid source. For example, if maintenance on a line is indicated, a nurse may have to trace the fluid line from the infusion pump or fluid source fluid line connection to the patient's fluid line connection, and vice versa. However, when multiple fluid lines cross, overlap, and / or intertwine, it may be difficult to identify the correct line for maintenance, infusion, removal, etc. Summary of the Invention

[0004] Thus, improved systems, devices, products, apparatus, and / or methods for identifying a lumen are provided.

[0005] According to certain non-limiting embodiments or aspects, a drug source system including a plurality of smart devices configured to be connected to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component configured to receive user input from a user, and a plurality of drug source devices connected to the plurality of lumens, each drug source device including a visual indicator, a communication circuit, and a user input component configured to receive user input from a user, and the communication circuit of the drug source device is configured to establish communication with the communication circuit of the smart device based on the user input to the user input component of the drug source device and the user input to the user input component of the smart device, and communication established between the drug source system and the communication circuit of the drug source device and the communication circuit of the smart device. and one or more processors programmed and / or configured to: control the visual indicator of the smart device and the visual indicator of the medication source device based on the signal to generate a same type of visual output; associate the same type of visual output with a same lumen of the plurality of lumens; the medication source device is connected to the same lumen; obtain medication data associated with a first type of medication delivered or scheduled to be delivered to the patient through the same lumen and a second type of medication delivered or scheduled to be delivered to the patient through the same lumen, where the first type of medication is different from the second type of medication; determine based on the medication data a suitability of the second type of medication for delivery through the same lumen as the first type of medication; and provide an indication of whether the second type of medication is compatible for delivery through the same lumen associated with the same type of visual output.

[0006] In some non-limiting embodiments or aspects, the visual indicator of the smart device includes a light emitting diode, and the visual output of the same type is the same color light.

[0007] In certain non-limiting embodiments or aspects, the light emitting diode is configured to emit light of a plurality of different colors, and the one or more processors are further programmed and / or configured to determine and generate a color of light of the same color for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of a user input to a user input component of the drug source device and a user input to a user input component of the smart device.

[0008] In some non-limiting embodiments or aspects, the light emitting diode is configured to emit light of a plurality of different colors, and the one or more processors are further programmed and / or configured to determine a same color of light for the visual indicator of the smart device and the visual indicator of the drug source device, and generate a color of light that is different from each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each visual indicator of each other drug source device of the plurality of drug source devices.

[0009] In some non-limiting embodiments or aspects, the drug source system includes an infusion pump system and the multiple drug source devices include multiple infusion pumps.

[0010] In some non-limiting embodiments or aspects, a first type of drug is delivered to the patient via the same lumen and a second type of drug is scheduled for delivery to the patient via the same lumen, and the one or more processors are programmed and / or configured to provide an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output by controlling the drug source device to inhibit or prevent delivery of the second drug via the same lumen associated with the same type of visual output.

[0011] In some non-limiting embodiments or aspects, a first type of medication is delivered to the patient through the same lumen and a second type of medication is scheduled for delivery to the patient through the same lumen, and the indication of whether the second type of medication is compatible for delivery through the same lumen associated with the same type of visual output includes a prompt to the user to use another lumen associated with a different type of visual output than the same type of visual output to deliver the second type of medication to the patient.

[0012] In some non-limiting embodiments or aspects, the first type of agent and the second type of agent are delivered to the patient through the same lumen associated with the same type of visual output, and the indication of whether the second type of agent is compatible for delivery through the same lumen associated with the same type of visual output includes a prompt to the user to treat the same lumen associated with the same type of visual output for one of a thrombotic occlusion or a chemical occlusion.

[0013] In some non-limiting embodiments or aspects, the visual indicator of the smart device is configured to generate the same type of visual output as the visual indicator of the drug source device in response to being connected to the lumen at the same time that communication is established between the communication circuitry of the drug source device and the communication circuitry of the smart device, and the visual indicator of the smart device is configured to automatically stop generating the same type of visual output as the visual indicator of the drug source device in response to being disconnected from the lumen.

[0014] In some non-limiting embodiments or aspects, the communication circuitry of the another drug source device is configured to establish communication with the communication circuitry of the another smart device based on a user input to the user input component of the another drug source device and a user input to the user input component of the another smart device, and the one or more processors are further programmed and / or configured to: control the visual indicator of the another smart device and the visual indicator of the another drug source device to generate a different same type visual output based on the communication established between the communication circuitry of the another drug source device and the communication circuitry of the another smart device, the different same type visual output being different from the same type visual output, and associating the different same type visual output with the different same lumen of the plurality of lumens, the another drug source device being connected to the different same lumen, obtain drug data related to a third type of drug delivered or scheduled to be delivered to the patient via the different same lumen, and based on the drug data, determine suitability of the second type of drug for delivery via the different same lumen with the third type of drug, and the indication further indicates whether the second type of drug is compatible for delivery via the different same lumen associated with the different same type visual output.

[0015] According to certain non-limiting embodiments or aspects, the present invention includes a method for providing a drug source system comprising the steps of: connecting a plurality of smart devices to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component; connecting a plurality of drug source devices of a drug source system to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component; receiving a user input via a user input component of the smart device; receiving a user input via a user input component of the drug source device; establishing communication between the smart device and the drug source device using the communication circuit of the smart device and the communication circuit of the drug source device based on the user input received by the user input component of the drug source device and the user input received by the user input component of the smart device; and using at least one processor, detecting a drug source device in a state where the smart device is in a drug-source state based on the communication established between the drug source device and the smart device. In one embodiment, the method includes controlling a visual indicator of the drug source device and a visual indicator of the drug source device to generate a same type of visual output; associating, with the at least one processor, the same type of visual output with a same lumen of the plurality of lumens, where the drug source device is connected to the same lumen; acquiring, with the at least one processor, drug data associated with a first type of drug delivered or scheduled to be delivered to the patient through the same lumen and a second type of drug delivered or scheduled to be delivered to the patient through the same lumen, where the first type of drug is different from the second type of drug; determining, with the at least one processor, suitability of the second type of drug for delivery through the same lumen as the first type of drug based on the drug data; and providing, with the at least one processor, an indication of whether the second type of drug is compatible for delivery through the same lumen associated with the same type of visual output.

[0016] In some non-limiting embodiments or aspects, the visual indicator of the smart device includes a light emitting diode, and the visual output of the same type is the same color light.

[0017] In certain non-limiting embodiments or aspects, the light emitting diode is configured to emit light of a plurality of different colors, and the method further includes determining, with the at least one processor, and generating a color of light of the same color for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of a user input received by a user input component of the drug source device and a user input received by a user input component of the smart device.

[0018] In some non-limiting embodiments or aspects, the light emitting diode is configured to emit light of a plurality of different colors, and the method further includes determining, with at least one processor, a same color of light for the visual indicator of the smart device and the visual indicator of the drug source device, and generating light of a different color than each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each visual indicator of each other drug source device of the plurality of drug source devices.

[0019] In some non-limiting embodiments or aspects, the drug source system includes an infusion pump system and the multiple drug source devices include multiple infusion pumps.

[0020] In some non-limiting embodiments or aspects, the step of delivering a first type of drug to the patient using the same lumen associated with the same type of visual output, where a second type of drug is scheduled for delivery to the patient via the same lumen, and the step of providing an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output further includes controlling the drug source device to inhibit or prevent delivery of the second drug via the same lumen associated with the same type of visual output.

[0021] In some non-limiting embodiments or aspects, the method further includes delivering a first type of medication to the patient using the same lumen associated with the same type of visual output, where a second type of medication is scheduled to be delivered to the patient via the same lumen, and the indication of whether the second type of medication is compatible for delivery via the same lumen associated with the same type of visual output includes a prompt to the user to use another lumen associated with a different type of visual output than the same type of visual output to deliver the second type of medication to the patient.

[0022] In some non-limiting embodiments or aspects, the method further includes delivering a first type of agent and a second type of agent to the patient using the same lumen associated with the same type of visual output, and the indication of whether the second type of agent is compatible for delivery via the same lumen associated with the same type of visual output includes a prompt to the user to treat the same lumen associated with the same type of visual output for one of a thrombotic occlusion or a chemical occlusion.

[0023] In some non-limiting embodiments or aspects, the method further includes using a visual indicator on the smart device to generate the same type of visual output as the visual indicator on the drug source device in response to being connected to the lumen at the same time that communication is established between the drug source device and the smart device, and using the visual indicator on the smart device to automatically stop generating the same type of visual output as the visual indicator on the drug source device in response to being disconnected from the lumen.

[0024] In some non-limiting embodiments or aspects, the method includes receiving a user input via a user input component of the other smart device; receiving a user input via a user input component of the other drug source device; establishing communication between the other drug source device and the other smart device using a communication circuit of the other drug source device and a communication circuit of the other smart device based on the user input received by the user input component of the other drug source device and the user input received by the user input component of the other smart device; and controlling, using the at least one processor, a visual indicator of the other smart device and a visual indicator of the other drug source device to generate another same type of visual output based on the communication established between the other drug source device and the other smart device. the other same type visual output being different from the other same type visual output; associating, with the at least one processor, the other same type visual output with the other same lumen of the plurality of lumens, the other drug source device being connected to the other same lumen; obtaining, with the at least one processor, drug data related to a third type drug delivered or scheduled to be delivered to the patient via the other same lumen; and determining, with the at least one processor, based on the drug data, compatibility of the second type drug with the third type drug for delivery via the other same lumen, the indication further indicating whether the second type drug is compatible for delivery via the other same lumen associated with the other same type visual output.

[0025] According to certain non-limiting embodiments or aspects, a system is provided comprising one or more processors programmed and / or configured to: control a visual indicator of the smart device and a visual indicator of the drug source device to generate a same type of visual output based on communication established between a communication circuit of the drug source device and a communication circuit of the smart device; the drug source device is connected to the lumen, the smart device is configured to be connected to the lumen, associate the same type of visual output with the lumen; obtain drug data related to a first type of drug delivered or scheduled to be delivered via the lumen to a patient and a second type of drug delivered or scheduled to be delivered via the lumen to a patient, the first type of drug being different from the second type of drug; determine based on the drug data a suitability of the second type of drug for delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output.

[0026] According to certain non-limiting embodiments or aspects, a computer-implemented method is provided that includes controlling, with at least one processor, a visual indicator of the smart device and a visual indicator of the drug source device to generate a same type of visual output based on communication established between a communication circuit of the drug source device and a communication circuit of the smart device, where the drug source device is connected to the lumen and the smart device is configured to be connected to the lumen; associating, with the at least one processor, the same type of visual output with the lumen; acquiring, with the at least one processor, drug data related to a first type of drug delivered or scheduled to be delivered to the patient via the lumen and a second type of drug delivered or scheduled to be delivered to the patient via the lumen, where the first type of drug is different from the second type of drug; determining, with the at least one processor, suitability of the second type of drug for delivery via the same lumen as the first type of drug based on the drug data; and providing, with the at least one processor, an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output.

[0027] According to certain non-limiting embodiments or aspects, a computer program product is provided 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: control a visual indicator of the smart device and a visual indicator of the drug source device to generate a same type of visual output based on communication established between a communication circuit of the drug source device and a communication circuit of the smart device; the drug source device is connected to the lumen, the smart device is configured to be connected to the lumen, associate the same type of visual output with the lumen; obtain drug data related to a first type of drug delivered or scheduled to be delivered via the lumen to the patient and a second type of drug delivered or scheduled to be delivered via the lumen to the patient, the first type of drug being different from the second type of drug; determine based on the drug data a suitability of the second type of drug for delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output.

[0028] Further non-limiting embodiments or aspects are described in the following numbered sections.

[0029] Section 1. A drug source system including a plurality of smart devices configured to be connected to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component configured to receive a user input from a user, and a plurality of drug source devices connected to the plurality of lumens, each drug source device including a visual indicator, a communication circuit, and a user input component configured to receive a user input from a user, the communication circuit of the drug source device configured to establish communication with the communication circuit of the smart device based on the user input to the user input component of the drug source device and the user input to the user input component of the smart device, and based on the communication established between the drug source system and the communication circuit of the drug source device and the communication circuit of the smart device. and one or more processors programmed and / or configured to control the visual indicators of the drug source device and the visual indicators of the drug source device to generate a same type of visual output and to associate the same type of visual output with a same lumen of the plurality of lumens, the drug source device being connected to the same lumen, obtain drug data associated with a first type of drug delivered or scheduled to be delivered to the patient through the same lumen and a second type of drug delivered or scheduled to be delivered to the patient through the same lumen, the first type of drug being different from the second type of drug, determine based on the drug data a suitability of the second type of drug for delivery through the same lumen as the first type of drug, and provide an indication of whether the second type of drug is compatible for delivery through the same lumen associated with the same type of visual output.

[0030] Clause 2. The system of clause 1, wherein the visual indicator of the smart device includes a light emitting diode, and the visual output of the same type is a same color light.

[0031] Clause 3. The system of either clause 1 or clause 2, wherein the light emitting diode is configured to emit light of a plurality of different colors, and the one or more processors are further programmed and / or configured to: determine and generate a color of light of the same color for the visual indicator of the smart device and the visual indicator of the medication source device based on at least one of a user input to a user input component of the medication source device and a user input to a user input component of the smart device.

[0032] Clause 4. The system of any of clauses 1-3, wherein the light emitting diode is configured to emit a plurality of different colors of light, and the one or more processors are further programmed and / or configured to: determine a same color of light for the visual indicator of the smart device and the visual indicator of the medication source device, and generate a color of light that is different from each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each other visual indicator of each other medication source device of the plurality of medication source devices.

[0033] Clause 5. The system of any of clauses 1 to 4, wherein the drug source system includes an infusion pump system, and the multiple drug source devices include multiple infusion pumps.

[0034] Clause 6. The system of any of clauses 1-5, wherein a first type of drug is delivered to the patient through the same lumen and a second type of drug is scheduled for delivery to the patient through the same lumen, and the one or more processors are programmed and / or configured to provide an indication of whether the second type of drug is compatible for delivery through the same lumen associated with the same type of visual output by controlling the drug source device to inhibit or prevent delivery of the second drug through the same lumen associated with the same type of visual output.

[0035] Clause 7. The system of any of clauses 1-6, wherein a first type of medication is delivered to the patient through the same lumen and a second type of medication is scheduled for delivery to the patient through the same lumen, and the indication of whether the second type of medication is compatible for delivery through the same lumen associated with the same type of visual output includes a prompt to the user to use another lumen associated with a different type of visual output than the same type of visual output to deliver the second type of medication to the patient.

[0036] Clause 8. The system of any of clauses 1-7, wherein the first type of agent and the second type of agent are delivered to the patient through a same lumen associated with the same type of visual output, and the indication of whether the second type of agent is compatible for delivery through the same lumen associated with the same type of visual output includes a prompt to the user to treat the same lumen associated with the same type of visual output for one of a thrombotic occlusion or a chemical occlusion.

[0037] Clause 9. The system of any of clauses 1 to 8, wherein the visual indicator of the smart device is configured to generate the same type of visual output as the visual indicator of the drug source device in response to being connected to the lumen at the same time that communication is established between the communication circuitry of the drug source device and the communication circuitry of the smart device, and the visual indicator of the smart device is configured to automatically stop generating the same type of visual output as the visual indicator of the drug source device in response to being disconnected from the lumen.

[0038] Clause 10. The system of any of clauses 1-9, wherein the communication circuitry of the another drug source device is configured to establish communication with the communication circuitry of the another smart device based on a user input to the user input component of the another drug source device and a user input to the user input component of the another smart device, and the one or more processors are further programmed and / or configured to: control the visual indicator of the another smart device and the visual indicator of the another drug source device to generate a different same type visual output based on the communication established between the communication circuitry of the another drug source device and the communication circuitry of the another smart device, the different same type visual output being different from the same type visual output, the different same type visual output being associated with the different same lumen of the plurality of lumens, the another drug source device being connected to the different same lumen, obtain drug data related to a third type drug delivered or scheduled to be delivered to the patient via the different same lumen, and determine based on the drug data a suitability of the second type drug for delivery via the different same lumen with the third type drug, and the indication further indicates whether the second type drug is compatible for delivery via the different same lumen associated with the different same type visual output.

[0039] Section 11. Connecting a plurality of smart devices to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component; Connecting a plurality of drug source devices of a drug source system to a plurality of lumens, each drug source device including a visual indicator, a communication circuit, and a user input component; Receiving user input via a user input component of the smart devices; Receiving user input via a user input component of the drug source devices; Establishing communication between the smart devices and the drug source devices using the communication circuit of the smart devices and the communication circuit of the drug source devices based on the user input received by the user input component of the drug source devices and the user input received by the user input component of the smart devices; and Using at least one processor, detecting the visual indicator of the smart devices based on the communication established between the drug source devices and the smart devices. and controlling a visual indicator of the drug source device to generate a same type of visual output; associating, with at least one processor, the same type of visual output with a same lumen of a plurality of lumens, where the drug source device is connected to the same lumen; acquiring, with the at least one processor, drug data associated with a first type of drug delivered or scheduled to be delivered to the patient through the same lumen and a second type of drug delivered or scheduled to be delivered to the patient through the same lumen, where the first type of drug is different from the second type of drug; determining, with the at least one processor, suitability of the second type of drug for delivery through the same lumen as the first type of drug based on the drug data; and providing, with the at least one processor, an indication of whether the second type of drug is compatible for delivery through the same lumen associated with the same type of visual output.

[0040] Clause 12. The method of clause 11, wherein the visual indicator of the smart device includes a light emitting diode, and the visual output of the same type is light of the same color.

[0041] Clause 13. The method of either clause 11 or clause 12, wherein the light emitting diode is configured to emit light of a plurality of different colors, and the method further includes determining, with the at least one processor, and generating a color of light of the same color for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of a user input received by a user input component of the drug source device and a user input received by a user input component of the smart device.

[0042] Clause 14. The method of any of clauses 11 to 13, wherein the light emitting diode is configured to emit light of a plurality of different colors, the method further comprising: determining, with the at least one processor, a same color of light for the visual indicator of the smart device and the visual indicator of the medication source device, and generating light of a color that is different from each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each visual indicator of each other medication source device of the plurality of medication source devices.

[0043] Clause 15. The method of any of clauses 11 to 14, wherein the drug source system includes an infusion pump system and the multiple drug source devices include multiple infusion pumps.

[0044] Clause 16. The method of any of clauses 11 to 15, further comprising the step of delivering a first type of drug to the patient using the same lumen associated with the same type of visual output, where a second type of drug is scheduled for delivery to the patient via the same lumen, and the step of providing an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output further comprises the step of controlling the drug source device to inhibit or prevent delivery of the second drug via the same lumen associated with the same type of visual output.

[0045] Clause 17. The method of any of clauses 11 to 17, further comprising the step of delivering a first type of medication to the patient using the same lumen associated with the same type of visual output, where a second type of medication is scheduled for delivery to the patient via the same lumen, and the indication of whether the second type of medication is compatible for delivery via the same lumen associated with the same type of visual output includes a prompt to the user to use another lumen associated with a different type of visual output than the same type of visual output to deliver the second type of medication to the patient.

[0046] Clause 18. The method of any of clauses 11 to 17, further comprising delivering a first type of agent and a second type of agent to the patient using a same lumen associated with the same type of visual output, wherein the indication of whether the second type of agent is compatible for delivery via the same lumen associated with the same type of visual output includes a prompt to the user to treat the same lumen associated with the same type of visual output for one of a thrombotic occlusion or a chemical occlusion.

[0047] Clause 19. The method of any of clauses 11 to 18, further comprising: generating, with the visual indicator of the smart device, a visual output of the same type as the visual indicator of the drug source device in response to being connected to the lumen at the same time that communication is established between the drug source device and the smart device; and automatically ceasing, with the visual indicator of the smart device, generating a visual output of the same type as the visual indicator of the drug source device in response to being disconnected from the lumen.

[0048] Section 20. Receiving user input by a user input component of the other smart device; receiving user input by a user input component of the other drug source device; establishing communication between the other drug source device and the other smart device using a communication circuit of the other drug source device and a communication circuit of the other smart device based on the user input received by the user input component of the other drug source device and the user input received by the user input component of the other smart device; and controlling, using at least one processor, a visual indicator of the other smart device and a visual indicator of the other drug source device to generate another same type of visual output based on the communication established between the other drug source device and the other smart device, wherein the another same type of visual output is generated based on the same type of visual output. 21. The method of any of clauses 11 to 20, further comprising: controlling a visual output of a different type from the visual output of the different type; associating, with the at least one processor, another same lumen of the plurality of lumens, where another drug source device is connected to the another same lumen; obtaining, with the at least one processor, drug data related to a third type drug delivered or scheduled to be delivered to the patient through the another same lumen; and determining, with the at least one processor, suitability of the second type drug for delivery through the another same lumen with the third type drug based on the drug data, where the indication further indicates whether the second type drug is compatible for delivery through the another same lumen associated with the another same type visual output.

[0049] Section 21. A system comprising: one or more processors programmed and / or configured to: control a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output based on communication established between communication circuitry of the drug source device and communication circuitry of the smart device; the drug source device is connected to a lumen, the smart device is configured to be connected to the lumen, and associate the same type of visual output with the lumen; obtain drug data associated with a first type of drug delivered or scheduled to be delivered through the lumen to a patient and a second type of drug delivered or scheduled to be delivered through the lumen to a patient, the first type of drug being different from the second type of drug; determine, based on the drug data, suitability of the second type of drug for delivery through the same lumen as the first type of drug; and provide an indication of whether the second type of drug is suitable for delivery through the same lumen associated with the same type of visual output.

[0050] Section 22. A computer-implemented method comprising: controlling, with at least one processor, a visual indicator of the smart device and a visual indicator of the drug source device to generate a same type of visual output based on communication established between a communication circuit of the drug source device and a communication circuit of the smart device, where the drug source device is connected to the lumen and the smart device is configured to be connected to the lumen; associating, with the at least one processor, the same type of visual output with the lumen; obtaining, with the at least one processor, drug data associated with a first type of drug delivered or scheduled to be delivered to the patient via the lumen and a second type of drug delivered or scheduled to be delivered to the patient via the lumen, where the first type of drug is different from the second type of drug; determining, with the at least one processor, suitability of the second type of drug for delivery via the same lumen as the first type of drug based on the drug data; and providing, with the at least one processor, an indication of whether the second type of drug is suitable for delivery via the same lumen associated with the same type of visual output.

[0051] Section 23. A 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: control a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output based on communication established between a communication circuit of the drug source device and a communication circuit of the smart device, the drug source device being connected to the lumen, the smart device being configured to be connected to the lumen, associate the same type of visual output with the lumen, obtain drug data associated with a first type of drug delivered or scheduled to be delivered through the lumen to a patient and a second type of drug delivered or scheduled to be delivered through the lumen to a patient, the first type of drug being different from the second type of drug, determine based on the drug data suitability of the second type of drug for delivery through the same lumen as the first type of drug, and provide an indication of whether the second type of drug is suitable for delivery through the same lumen associated with the same type of visual output. [Brief description of the drawings]

[0052] [Figure 1] FIG. 1 illustrates a non-limiting embodiment or aspect of an environment in which the systems, devices, products, apparatus, and / or methods described herein may be implemented. [Figure 2A] FIG. 2 illustrates a non-limiting embodiment or aspect of an implementation of one or more systems and / or one or more devices of FIG. 1. [Figure 2B] FIG. 2 illustrates a non-limiting embodiment or aspect of an implementation of one or more systems and / or one or more devices of FIG. 1. [Figure 2C] FIG. 2 illustrates a non-limiting embodiment or aspect of an implementation of one or more systems and / or one or more devices of FIG. 1. [Diagram 3]FIG. 2 is a diagram of non-limiting embodiments or aspects of components of one or more devices and / or one or more systems of FIGS. 1 and 2A-2C. [Figure 4A] FIG. 13 is a side view of a non-limiting embodiment or aspect of an implementation of a needleless connector. [Figure 4B] FIG. 13 is a side view of a non-limiting embodiment or aspect of an implementation of a smart device and a needleless connector. [Figure 4C] FIG. 13 is a side view of a non-limiting embodiment or aspect of an implementation of a smart device and a needleless connector. [Figure 5A] FIG. 1 is a perspective view of a non-limiting embodiment or aspect of an implementation of a smart device and a needleless connector. [Figure 5B] FIG. 13 is a top view of a non-limiting embodiment or aspect of an implementation of a smart device and a needleless connector. [Figure 5C] 1 is a graph of a non-limiting embodiment or aspect of a force signal over time. [Figure 6A] 2 illustrates a non-limiting embodiment or aspect of an output of one or more systems and / or one or more devices of FIG. 1. [Figure 6B] 2 illustrates a non-limiting embodiment or aspect of an output of one or more systems and / or one or more devices of FIG. 1. [Figure 7] FIG. 1 illustrates a non-limiting embodiment or aspect of an implementation of a smart device for detecting drug extravasation and / or infiltration in a catheter. [Figure 8] 1 is a flowchart of a non-limiting embodiment or aspect of a process for identifying a lumen. [Figure 9] 1 is a flowchart of a non-limiting embodiment or aspect of a process for identifying a lumen. [Figure 10] 13 is a flow chart of a non-limiting embodiment or aspect of a process for identifying a needle tip location. [Figure 11] 1 is a flow chart of a non-limiting embodiment or aspect of a process for event monitoring. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0053] It is to be understood that the present disclosure may assume various alternative variations and step sequences unless 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 merely exemplary and non-limiting embodiments or aspects. Thus, specific dimensions and other physical characteristics relating to the embodiments or aspects disclosed herein are not to be considered as limiting.

[0054] For purposes of the following description, the terms "end", "top", "bottom", "right", "left", "vertical", "horizontal", "upper", "lower", "lateral", "vertical" and their derivatives are intended to refer to an embodiment or aspect as they are oriented in the drawings. However, it should be understood that an embodiment or aspect may assume various alternative variations and step sequences unless expressly specified to the contrary. It should also be understood that the specific devices and processes illustrated in the accompanying drawings and described in the following specification are merely non-limiting, exemplary embodiments or aspects. Thus, specific dimensions and other physical characteristics relating to an embodiment or aspect disclosed herein should not be considered as limiting unless otherwise specified.

[0055] As used herein, aspects, components, elements, structures, acts, steps, functions, instructions, and the like, should not be construed as critical or essential unless expressly described as such. Additionally, 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." Additionally, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one." When only one item is intended, the term "one" or similar language is used. Additionally, as used herein, the terms "has," "have," "having," and the like are intended to be open-ended terminology. Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified.

[0056] As used herein, the terms "communication" and "communicating" may refer to receiving, accepting, sending, forwarding, providing, etc., information (e.g., data, signals, messages, instructions, commands, etc.). One unit (e.g., a device, a system, a component of a device or system, combinations thereof, etc.) in communication with another unit means that one unit is capable of directly or indirectly sending and / or receiving information to and from the other unit. This may refer to a direct or indirect connection that is wired and / or wireless in nature. Furthermore, two units may be in communication with each other, although the information transmitted may be modified, processed, relayed, and / or routed between the first and second units. For example, a first unit may be in communication with a second unit, although 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 intermediate 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 or aspects, a message may refer to a network packet (e.g., a data packet, etc.) that includes data. It will be appreciated that many other configurations are possible.

[0057] The term "computing device" as used herein may refer to one or more electronic devices configured to communicate directly or indirectly with or through one or more networks. A computing device may be a mobile or portable computing device, a desktop computer, a server, etc. Furthermore, the term "computer" may refer to any computing device that includes the necessary components to receive, process, and output data, typically including a display, a processor, memory, input devices, and a network interface. A "computing system" may include one or more computing devices or computers. An "application" or "application program interface" (API) refers to computer code or other data grouped 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 for receiving data from a client and / or a server-side back-end. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUIs), with which a user may interact, directly or indirectly (e.g., through a keyboard, mouse, touch screen, etc.). Furthermore, multiple computers, e.g., servers or other computing devices, communicating directly or indirectly in a network environment may constitute a "system" or a "computing system."

[0058] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual special control hardware or software code used to implement these systems and / or methods does not limit the implementation. Thus, it should be understood that the operation and behavior of the systems and / or methods are described herein without regard to specific software code, and that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0059] Non-limiting embodiments or aspects are described herein in terms of a threshold value. As used herein, meeting a threshold may refer to a value being greater than the threshold, more than the threshold, higher than the threshold, equal to or greater than the threshold, less than the threshold, less than the threshold, lower than the threshold, less than or equal to the threshold.

[0060] Improved systems, devices, products, apparatus, and / or methods for identifying lumens are provided. Existing systems for identifying lumens may use tape, labels, handwritten nodes, and / or LED lights to identify lumens. However, existing systems for identifying lumens may not automatically associate an identified lumen with a fluid pump or fluid source connected to the identified lumen, and / or with medication data related to one or more medications that are delivered and / or scheduled to be delivered through the identified lumen. In this manner, existing systems for identifying lumens do not have a mechanism for automatically determining compatibility of medications that are delivered and / or scheduled to be delivered through the same lumen, and / or inhibiting or preventing delivery of incompatible medications through the same lumen. Thus, existing systems for identifying lumens may not sufficiently reduce or eliminate IV line complexity and / or medication delivery errors, and / or sufficiently improve compliance with lumen maintenance procedures (e.g., line flushing, etc.).

[0061] Non-limiting embodiments or aspects of the present disclosure are directed to systems, devices, products, apparatus, and / or methods that automatically associate an identified lumen with a fluid pump or fluid source connected to the identified lumen and / or with medication data related to one or more medications delivered and / or scheduled to be delivered via the identified lumen. For example, the method may include controlling a visual indicator of the smart device and a visual indicator of the drug source device to generate a same type of visual output based on communication established between a communication circuitry of the drug source device and a communication circuitry of the smart device, where the drug source device is connected to the lumen and the smart device is configured to be connected to the lumen; associating the same type of visual output with the lumen; obtaining drug data related to a first type of drug delivered or scheduled to be delivered to the patient via the lumen and a second type of drug delivered or scheduled to be delivered to the patient via the lumen, where the first type of drug is different from the second type of drug; determining, based on the drug data, suitability of the second type of drug for delivery via the same lumen as the first type of drug; and providing an indication of whether the second type of drug is compatible for delivery via the same lumen associated with the same type of visual output.

[0062] In this manner, non-limiting embodiments or aspects of the present disclosure provide for automatically determining compatibility of medications delivered and / or scheduled to be delivered through the same lumen, and / or inhibiting or preventing delivery of incompatible medications through the same lumen, which may allow for improvement or elimination of IV line complications and / or medication delivery errors, and / or improved compliance with lumen maintenance procedures (e.g., line cleaning, etc.).

[0063]

[0023] Referring now to Figure 1, Figure 1 is a diagram of an example environment 100 in which the devices, systems, methods, and / or products described herein may be implemented. As shown in Figure 1, the environment 100 includes a drug source system 102, a smart device 104, a communication network 106, a central computing system 108, and a terminal / mobile computing system 110. The systems and / or devices of the environment 100 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0064] In some non-limiting embodiments or aspects, the drug source system 102 includes one or more devices capable of delivering one or more fluids to one or more lumens (e.g., fluid lines, IV lines, etc.). For example, the drug source system 102 may include one or more manual fluid delivery systems (e.g., one or more IV bags, one or more syringes, etc.) and / or an infusion pump system including one or more infusion pumps. In some non-limiting embodiments, the smart device 104 may include multiple smart devices 104 (e.g., one or more other and / or different types of smart devices 104, etc.).

[0065] In some non-limiting embodiments or aspects, the drug source system 102 includes one or more devices capable of receiving information and / or data from and / or communicating information and / or data to the smart devices 104, the communication network 106, the central computing system 108, and / or the terminal / mobile computing system 110. For example, the drug source system 102 may include one or more computing systems (e.g., one or more computing devices, one or more mobile computing devices, etc.) including one or more processors.

[0066] Further details regarding non-limiting embodiments or aspects of the drug source system 102 are provided below with respect to FIGS. 2A, 2C, and 3.

[0067] In some non-limiting embodiments or aspects, the smart device 104 includes one or more devices capable of receiving information and / or data from and / or communicating information and / or data to the drug source system 102, one or more other smart devices 104, the communication network 106, the central computing system 108, and / or the terminal / mobile computing system 110. For example, the smart device 104 may include one or more computing systems (e.g., one or more computing devices, one or more mobile computing devices, etc.) including one or more processors. In some non-limiting embodiments or aspects, the smart device 104 may be capable of receiving information (e.g., from the drug source system 102 (e.g., from the drug source controller 204 and / or from the drug source device 206), from the terminal / mobile computing system 110, from one or more other smart devices 104, etc.) via a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, etc.) and / or communicating information (e.g., to the drug source system 102 (e.g., to the drug source controller 204 and / or to the drug source device 206), to the terminal / mobile computing system 110, to one or more other smart devices 104, etc.) via a short-range wireless communication connection (e.g., to the drug source system 102 (e.g., to the drug source controller 204 and / or to the drug source device 206), to the terminal / mobile computing system 110, to one or more other smart devices 104, etc.).

[0068] 6B, the smart device 104 may provide direct patient feedback (e.g., via LED lighting to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a predetermined period of time and / or prior to a scheduled use, (ii) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a sufficient period of time prior to accessing the catheter line, (iii) detecting that flushing of the needleless connector 214 and / or lumen 212 is scheduled, (iv) detecting that a disinfecting cap was not installed after a previous access of the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include a needleless connector 214 that may be configured to detect at least one of a cleaning event, a flushing event, a connecting or capping event, or any combination thereof. As an example, the needleless connector 214 may be configured to provide information and / or data related to a detected cleaning event, a detected flushing event, and / or a detected connecting or capping event (e.g., using the processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to store the events and report compliance performance for monitoring compliance events.

[0069] Further details regarding non-limiting embodiments or aspects of smart device 104 are provided below with respect to Figures 2A-2C, 3, 4A-4C, 5A-5C, 6A, 6B, and 7.

[0070] In some non-limiting embodiments or aspects, the communications network 106 includes one or more wired and / or wireless networks. For example, the communications network 106 includes a cellular network (e.g., a Long Term Evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad-hoc network, an intranet, the Internet, an optical fiber-based network, a cloud computing network, etc., and / or any combination of these or other types of networks.

[0071] In some non-limiting embodiments or aspects, the central computing system 108 includes one or more devices capable of receiving information and / or data from and / or communicating information and / or data to the drug source system 102, the smart device 104, the communication network 106, and / or the terminal / mobile computing system 110. For example, the drug source system 102 may include one or more computing systems (e.g., one or more computing devices, one or more mobile computing devices, etc.) including one or more processors. In some non-limiting embodiments or aspects, the central computing system 108 includes a secure hospital server and / or one or more secure hospital databases that store personally identifiable information (PII) and / or Health Insurance Portability and Accountability Act (HIPAA) protected information.

[0072] In some non-limiting embodiments or aspects, the terminal / mobile computing system 110 includes one or more devices capable of receiving information and / or data from and / or communicating information and / or data to the drug source system 102, the smart device 104, the communication network 106, and / or the central computing system 108. For example, the terminal / mobile computing system 110 may include one or more computing systems (e.g., one or more computing devices, one or more mobile computing devices, etc.) including one or more processors. In some non-limiting embodiments or aspects, the terminal / mobile computing system 110 includes a nurse's station throughout the hospital. For example, as shown in implementation 600A of FIG. 6A , the terminal / mobile computing system 110 may provide bedside nurse support (e.g., recording each access to the needleless connector 214 and / or lumen 212 in real time and feedback to the nurse when cleaning or flushing is scheduled or determined to be required according to the recorded access), nursing station manager support (e.g., optimizing flushing procedures to reduce workflow and improve timing targets for flushing the needleless connector 214 and / or lumen 212), retrospective reporting for nursing management (e.g., cleaning duration, flushing technique, time between flushes of the needleless connector 214 and / or lumen 212, etc.), and the like.

[0073] 2A-2C, which are diagrams of non-limiting embodiments or aspects of an implementation 200 of one or more systems and / or one or more devices of FIG. 1. As shown in FIGS. 2A and 2C, the drug source system 102 may include a drug source controller 204 and / or one or more drug source devices 206 (e.g., multiple drug source devices 206a, 206b, ... 206n, etc.). As an example, the drug source controller 204 may include an infusion pump controller and / or the drug source device 206 may include an infusion pump. In such an example, the drug source system 102 may include a BD Alaris™ system. For example, the drug source system 102 may include a BD Alaris™ PC unit and one or more BD Alaris™ pump modules. As another example, the drug source controller 204 may include a bedside console or computing device that may be separate from the infusion pump system, and / or the drug source device 206, which may be separate from the infusion pump, may be associated with and / or connected to a drug source (e.g., an IV bag, a syringe, the end of an IV line proximate to an IV bag or syringe, etc.).

[0074] As shown in FIG. 2A, the multiple drug source devices 206a, 206b, ... 206n may be connected to multiple lumens (e.g., fluid lines, etc.) 202a, 202b, ... 202n (e.g., for receiving fluids and / or drugs at the drug source system 102) and / or multiple lumens (e.g., fluid lines, etc.) 212a, 212b, ... 212n (e.g., for delivering fluids and / or drugs from the drug source system 102, etc.). As shown in FIG. 2C, the drug source device 206 may include a pairing input 208 (e.g., a button, an input component 310, etc.) and / or a visual indicator 210 (e.g., a multi-colored LED, an output component 312, etc.). As shown in FIG. 2A and FIG. 2B, the multiple lumens 212a, 212b, ... 212n may be connected to multiple smart devices 104a, 104b, ... 104n.

[0075] However, non-limiting embodiments or aspects are not so limited, and a patient may be connected to only a single lumen, and the lumen may (or may not) be connected to any medication source device 206 and / or fluid source. For example, if a patient is connected to a single lumen, the smart device 104 may be connected to a single lumen, and the smart device 104 may be associated with a particular color associated with that lumen. A physician and / or pharmacy may issue instructions to deliver a certain type of medication to a patient, and the instructions for a certain type of medication may link the color of the lumen to instructions to reduce or avoid medication delivery errors. As an example, a first patient may have an order from a physician and / or pharmacy that includes a "pink" LED light illuminated on the smart device 104, and instructions to a user (e.g., a nurse, etc.) to deliver a new type of medication or treatment delivered and only a "pink" line to implement an error checking process. When a user (e.g., a nurse, etc.) initiates delivery of a medication to a patient, the user can ensure that the smart device 104 emits a pink light for an additional safety check to ensure that the user has the right patient for the right type of medication. If the smart device 104 emits a color light other than a "pink" light (e.g., a "green" light or a "blue" light) and the medication instructions indicate that the medication should only be delivered through the "pink" lumen, the user (e.g., a nurse, etc.) may initiate delivery to the patient because the user can determine that the instructions and colors do not match (e.g., do not deliver medication to the patient), which may indicate an issue and / or incompatibility with the medication for the patient and / or lumen. For example, if the patient is connected to a single lumen, the instructions may indicate to deliver saline on the "pink" line, deliver antibiotics on the same "pink" line, etc.However, if the prescribed medication is incompatible, the instructions may alert the user that additional flushing is indicated on the "pink" line to ensure that the pink line is properly flushed before a subsequent medication is delivered that may not be compatible with the medication or fluid previously delivered through the "pink" line. As an example, if there are two lumens connected to a single patient (e.g., a single "pink" line and a single "blue" line), the instructions may indicate to deliver saline through the "pink" lumen or line, deliver antibiotics through the "blue" lumen or line, etc. Thus, in some non-limiting embodiments or aspects, the smart device 104 may simply be used for identification of the appropriate patient lumen and / or to instruct the user to use the optimal lumen for delivering fluid to the patient, which ensures that the appropriate therapy is delivered to the optimal or appropriate lumen, thereby reducing scenarios associated with wrong dose, wrong patient, wrong lumen, etc., using the smart device 104.

[0076] In some non-limiting embodiments or aspects, the smart device 104 is configured to be removably connected to a portion of the lumen 212 proximate the needleless connector 214, such as an IV lumen (e.g., a peripherally inserted central catheter (PICC), a peripheral intravenous catheter (PIVC), a central venous catheter (CVC), etc.). For example, the smart device 104 may include a clamp, adhesive, or other attachment means configured to removably connect the smart device 104 to the needleless connector 214 and / or the lumen 212 proximate the needleless connector 214. As an example, as shown in FIG. 2A and FIG. 2B, the smart device 104a may be connected to a catheter lumen connecting a catheter to the needleless connector 214 and / or lumen 212b, and / or the smart device 104n may be connected to a catheter lumen connecting a catheter to the needleless connector 214 and / or lumen 212a. In some non-limiting embodiments or aspects, the smart device 104 includes the needleless connector 214. For example, the smart device 104 may be integrated with the needleless connector 214 (e.g., within the needleless connector 214 and / or within the catheter hub of the needleless connector of the fluidly invasive device, etc.). As an example, as shown in Figures 2A and 2B, the smart device 104b may include a catheter hub that connects a catheter lumen to a lumen 212n via the needleless connector 214 and / or a Y-site connector. In such an example, the smart device 104 may include a needleless connector 214 including a housing 402 of the needleless connector 214 within the housing 250 (e.g., integrated with the housing 250, contained within the housing 250, etc.).

[0077] 4A, which is a side view of a non-limiting embodiment or aspect of an implementation 400A of a needleless connector 214. As shown in FIG. 4A, the needleless connector 214 may include a fluid flow path in a housing 402 between an inlet 404 and an outlet 406 opposite the inlet 404. The inlet 404 may be fluidically sealed by a displaceable septum 408 configured to be displaced to open or connect the inlet 404 to the fluid flow path in response to connection of the needleless connector 214 to a medical device (e.g., an infusion pump, an IV bag, a syringe, an IV line, etc.). For example, the needleless connector 214 may include a BD MaxPlus® connector, a BD MaxZero® needleless connector, etc. However, non-limiting embodiments or aspects are not so limited and the needleless connector 214 may include any needleless connector 214 for use in fluid administration. In some non-limiting embodiments or aspects, one or more components of the smart device 104 may be included within the housing 402 of the needleless connector 214. For example, the housing 402 of the needleless connector 214 may include the housing 250 of the smart device 104 (e.g., the housing 250 may be integrated with the housing 402, contained within the housing 402, etc.).

[0078] 2C, the smart device 104 may include a visual indicator 252 (e.g., one or more visual indicators, multiple visual indicators, multi-color LED, multiple LEDs, output component 312, etc.), a sensor 254 (e.g., one or more sensors, multiple sensors, a sensor suite, etc.), a pairing input 256 (e.g., one or more buttons, one or more force sensors, one or more accelerometers, input component 310, etc.), a battery 258, and / or an energy harvester 260 (e.g., a thermoelectric energy harvester, a photovoltaic energy harvester, a piezoelectric energy harvester, etc.). All or a portion of the visual indicator 252, the sensor 254, the pairing input 256, the battery 258, the energy harvester 260, and the needleless connector 214 may be included within a housing 250 of the smart device 104. The visual indicator 252 may be visible through and / or extend from a sidewall of the housing 250. The battery 258 and / or energy harvester 260 may provide power to operate components of the smart device 104, such as the visual indicator 252, the sensor 254, the pairing input 256, the rechargeable battery of the battery 258, and one or more components of the device 300 included in the smart device 104.

[0079] In some non-limiting embodiments or aspects, the smart device 104 may include labels (e.g., human readable labels, etc.) that characterize the visual indicators 252 of the smart device 104. For example, as shown in implementation 400C of FIG. 4C, the smart device 104 may include labels (e.g., on a sidewall of the housing 250, etc.) associated with the visual indicators 252 that characterize each visual indicator 252 to be configured to provide an indication related to a particular event, such as one of a cleaning event where the needleless connector 214 is cleaned with a disinfectant (e.g., labeled "clean"), a flushing event where the needleless connector 214 is flushed with a solution (e.g., labeled "flush"), a connecting or capping event where the needleless connector 214 is connected to a medical device (e.g., labeled "cap"), etc. In some non-limiting embodiments or aspects, the smart device 104 may include a single visual indicator 252 (e.g., as shown in implementation 400B of FIG. 4B). For example, the smart device 104 may control the single visual indicator 252 to illuminate in a particular color and / or in a particular pattern to indicate or prompt the user to do things like illuminate a continuous green color in response to the needleless connector 214 being cleaned for a predetermined period of time (e.g., 15 seconds, etc.), illuminate a blinking green color in response to an appropriate pulsating flush being performed, illuminate a blinking red color in response to determining that the needleless connector 214 has not been pulsating flushed for a predetermined period of time (e.g., 88 hours, etc.), illuminate a continuous red color in response to determining that the needleless connector 214 has not been capped with a disinfectant cap for a predetermined period of time (e.g., one minute or more, etc.), etc.

[0080] In some non-limiting embodiments or aspects, the communication circuitry (e.g., communication interface 314, etc.) of the drug source device 206 is configured to establish communication with the communication circuitry (e.g., communication interface 314, etc.) of the smart device 104 based on a user input to the pairing input 208 of the drug source device 206 and a user input to the pairing input 256 of the smart device 104. For example, the drug source device 206 may establish a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, etc.) with the smart device 104. As an example, the visual indicator 210 may be configured to emit a predetermined light pattern (e.g., blink quickly to indicate that the drug source device 206 is in pairing mode) in response to a predetermined user input to the pairing input 208 of the drug source device 206 (e.g., in response to a user pressing and holding a button on the pairing input 208, etc.). In such an example, the smart device 104 may be configured to establish communication with the drug source device 206 (e.g., pair the drug source device 206 with the smart device 104 and / or activate a pairing sequence for pairing therewith, etc.) in response to a predetermined user input to the pairing input 256 of the smart device 104 (e.g., in response to a user pressing and holding a button on the pairing input 256, etc.) at the same time that the drug source device 206 is in pairing mode.

[0081] In some non-limiting embodiments or aspects, when the drug source device 206 is paired with the smart device 104, the visual indicator 210 of the drug source device 206 and the visual indicator 252 of the smart device 104 are configured to provide the same type of visual output (e.g., the same color light from a multi-colored LED, the same pattern of light, etc.). For example, referring again to FIG. 2A, the drug source device 206a may be paired with the smart device 104n, where each of the drug source device 206a and the smart device 104n may output light of a first color (e.g., red light), the drug source device 206b may be paired with the smart device 104a, where each of the drug source device 206b and the smart device 104a may output light of a second color (e.g., green light), the drug source device 206n may be paired with the smart device 104b, where each of the drug source device 206n and the smart device 104b may output light of a third color (e.g., blue light), etc.

[0082] In some non-limiting embodiments or aspects, the sensor 254 includes at least one of one or more force sensors (e.g., one or more piezoelectric elements or transducers, one or more force sensing resistive (FSR) sensors, one or more strain gauges, etc.), one or more pressure sensors, one or more acoustic sensors, one or more optical sensors (e.g., an optical sensor configured to detect at least one of a color signature and a reflection of a medical device connected to the smart device 104, etc.), one or more identification sensors (e.g., a magnetometer configured to detect a magnetic material, a barcode scanner configured to read a barcode, etc., an identification sensor configured to detect an identification tag on a medical device connected to or attached to the needleless connector 214, etc.), one or more position sensors (e.g., a position sensor configured to detect movement of the smart device 104, etc.), one or more RBG color sensors, or any combination thereof.

[0083] The number and configuration of systems, devices, and networks shown in Figures 1 and 2A-2C are provided as an example. There may be additional, fewer, different, or differently configured systems, devices, and / or networks in the systems, devices, and / or networks shown in Figures 1 and 2A-2C. Furthermore, two or more systems or devices shown in Figures 1 and 2A-2C may be implemented within a single system or device, or a single system or device shown in Figures 1 and 2A-2C may be implemented as multiple, distributed systems or devices. Additionally or alternatively, a set of systems or devices (e.g., one or more systems, one or more devices, etc.) of environment 100 and / or implementation 200 may perform one or more functions described as being performed by another set of systems or another set of devices of environment 100 and / or implementation 200.

[0084] Referring now to FIG. 3, FIG. 3 is a diagram of example components of a device 300. The device 300 may correspond to one or more devices of the drug source system 102, the smart device 104, and / or one or more devices of the communication network 106, one or more devices of the central computing system 108, one or more devices of the terminal / mobile computing system 110, one or more devices of the drug source controller 204, and / or one or more devices of the drug source device 206. In some non-limiting embodiments or aspects, one or more devices of the drug source system 102, the smart device 104, and / or one or more devices of the communication network 106, one or more devices of the central computing system 108, one or more devices of the terminal / mobile computing system 110, one or more devices of the drug source controller 204, and / or one or more devices of the drug source device 206 may include at least one device 300 and / or at least one component of the device 300. As shown in FIG. 3, device 300 may include a bus 302, a processor 304, a memory 306, a storage component 308, an input component 310, an output component 312, and a communication interface 314.

[0085] The bus 302 may include components that enable communication between the components of the device 300. In some non-limiting embodiments or aspects, the processor 304 may be implemented in hardware, firmware, or a combination of hardware and software. For example, the processor 304 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), a microcontroller (MCU), etc.) that can be programmed to perform functions. The memory 306 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 the processor 304.

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

[0087] The input components 310 may include components that enable the device 300 to receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, a microphone, a camera, an electroencephalogram (EEG) monitor, etc.). Additionally or alternatively, the input components 310 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). The output components 312 may include components that provide output information from the device 300 (e.g., a display, a speaker, one or more light emitting diodes (LEDs), etc.).

[0088] The communication interface 314 may include transceiver-like components (e.g., a transceiver, a separate receiver and transmitter, etc.) that enable the device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 314 may enable the device 300 to receive information from another device and / or to provide information to another device. For example, the communication interface 314 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, etc.

[0089] The device 300 may perform one or more processes described herein. The device 300 may perform these processes based on the processor 304 executing software instructions stored by a computer-readable medium, such as the memory 306 and / or the storage component 308. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A non-transitory memory device includes a memory space located within a single physical storage device or a memory space spread across multiple physical storage devices.

[0090] Software instructions may be read into memory 306 and / or storage component 308 from another computer-readable medium or from another device via communication interface 314. When executed, the software instructions stored in memory 306 and / or storage component 308 may cause processor 304 to perform one or more operations described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more operations described herein. Thus, the embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software.

[0091] The memory 306 and / or the storage component 308 may include a data storage or one or more data structures (e.g., a database, etc.). The device 300 may be capable of receiving information from, storing information in, communicating information to, or searching for information stored in the data storage or one or more data structures in the memory 306 and / or the storage component 308. For example, the information may be input data, output data, medical data, or any combination thereof.

[0092] The number and configuration of components shown in Figure 3 are provided as an example. In some non-limiting embodiments or aspects, device 300 may include additional, fewer, different, or differently configured components than those shown in Figure 3. Additionally or alternatively, a set of components (e.g., one or more components) of device 300 may perform one or more functions described as being performed by another set of components of device 300.

[0093] FIG. 5A is a perspective view and FIG. 5B is a top view of a non-limiting embodiment or aspect of an implementation 500 of a smart device 104 including a needleless connector 214. Still referring to FIG. 4A, the needleless connector 214 may include a fluid flow path in a housing 402 between an inlet 404 and an outlet 406 opposite the inlet 404. The inlet 404 may be fluidically sealed by a displaceable septum 408 configured to be displaced to open or connect the inlet 404 to the fluid flow path in response to connection of the needleless connector 214 to a medical device (e.g., an infusion pump, an IV bag, a syringe, an IV line, etc.). Referring again to FIG. 5A and FIG. 5B, in some non-limiting embodiments, the smart device 104 may include a sensor 254. For example, the sensor 254 may include a force sensor 502 connected to the needleless connector 214. As an example, the force sensor 502 may be configured to sense, detect, and / or determine a force signal. In such an example, at least one of a cleaning event where the needleless connector is cleaned with a disinfectant, a flushing event where the needleless connector is flushed with a solution, a connection event where the needleless connector is connected to a medical device, or any combination thereof may be determined based on the force signal (e.g., by the smart device 104, etc.). In such an example, a pattern of events including at least one of a cleaning event where the needleless connector is cleaned with a disinfectant, a flushing event where the needleless connector is flushed with a solution, a connection event where the needleless connector is connected to a medical device, a time between one or more detected events, or any combination thereof may be determined based on the force signal, and a drug administration event where a drug is administered to a patient via the needleless connector 214 may be determined based on the pattern of events. As an example, standard of care may assume a clean-flush-clean-drug-administer-clean-flush-clean pattern or sequence of events, and thus detection of three accesses of a luer connector may be interpreted to the smart device 104 as a drug administration event. For example, FIG. 5C is a graph 550 of a non-limiting embodiment or aspect of a force measurement or signal over time.5C, pulsating flushing may be determined or detected by force measurements, for example, when flushing is accomplished by intermittent pulsations applied to the plunger of a flushing syringe, and the smart device 104 may detect the occurrence of pulsating flushing by identifying a periodic force signal between x-y Hz in the force signal perpendicular to the face of the septum 408 of the needleless connector 214. For example, the smart device 104 may determine a flushing event based on a force signal indicative of a periodic force in a second direction that is perpendicular to the face of the septum facing the first direction, and the flushing event includes a pulsating flushing event.

[0094] In some non-limiting embodiments or aspects, the smart device 104 may further include a communication circuit configured to transmit the force signal to a remote computing system. For example, the drug source system 102, the central computing system 108, and / or the terminal / mobile computing system 110 may obtain the force signal from the smart device 104 and / or the needleless connector 214 and process the force signal to determine at least one of a cleaning event in which the needleless connector is cleaned with a disinfectant, a flushing event in which the needleless connector is flushed with a solution, a connection event in which the needleless connector is connected to a medical device, or any combination thereof.

[0095] In some non-limiting embodiments or aspects, the force sensor 502 includes at least one of a piezoelectric element, a force sensitive resistive film (FSR) sensor, a strain gauge, or any combination thereof. In some non-limiting embodiments or aspects, the force sensor 502 is located between an outer surface of an inner wall 510 (e.g., an inner harder plastic wall) of the needleless connector 214 that defines the fluid flow path of the needleless connector 214 and an inner surface of an outer wall 512 (e.g., a softer, more flexible, more pliable, rubber, etc. wall) of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214. In some non-limiting embodiments or aspects, the area between the outer surface of the inner wall 510 (e.g., an inner harder plastic wall) of the needleless connector 214 that defines the fluid flow path of the needleless connector 214, which may be held by a user during cleaning and / or connection to another medical device, and the inner surface of the outer wall 512 (e.g., a softer, more pliable, more compliant, rubber, etc. wall) of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214, may be filled with rubber or other pliable type material 514 that includes a force sensor 502 as a force sensing film in the material 514 between the inner wall 510 and the outer wall 512. In some non-limiting embodiments or aspects, the force sensor 502 may be located between the inner wall 510 and the outer wall 512 below the threads on and / or near the inlet 404 of the needleless connector 214.

[0096] In some non-limiting embodiments or aspects, the force sensor 502 includes a plurality of force sensors 502 positioned about the fluid flow path of the needleless connector 214 between an outer surface of an inner wall 510 of the needleless connector 214 that defines the fluid flow path of the needleless connector 214 and an inner surface of an outer wall 512 of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214. For example, the inlet 404 of the needleless connector 214 may include a septum 408 that includes a face that faces in a first direction, and the force sensor 502 may be configured to detect a force in a second direction that is perpendicular to the face of the septum that faces in the first direction. As an example, a flush event, which may include a pulsating flush event, may be determined based on a force signal indicative of a periodic force in a second direction that is perpendicular to the face of the septum that faces in the first direction.

[0097] In some non-limiting embodiments or aspects, the sensor 254 includes a pressure sensor that is one of: in direct contact with the fluid in the fluid flow path of the needleless connector; located within an inner wall of the needleless connector that defines the fluid flow path of the needleless connector; and located within a wall of a lumen connected to the needleless connector. For example, the smart device 104 may determine or detect pulsatile flushing, flushing, and / or drug administration by a pressure sensor in contact with the fluid path in the needleless connector 214 and / or its lumen.

[0098] In some non-limiting embodiments or aspects, the sensor 254 includes an optical sensor configured to detect at least one of a color signature and a reflectance of a medical device connected to and / or coupled to the needleless connector 214, and the smart device 104 may determine a type of medical device based on at least one of the color signature and the reflectance of the medical device. For example, the color signature and / or reflectance of the medical device may be indicative of a syringe, an IV bag, an infusion pump, and / or a particular type thereof.

[0099] In some non-limiting embodiments or aspects, the sensor 254 includes an identification sensor configured to detect an identification tag on a medical device connected to or coupled to the needleless connector. For example, the identification sensor may include a magnetometer and the identification tag may include a magnetic material on and / or integrated with the needleless connector 214.

[0100] In some non-limiting embodiments or aspects, the sensor 254 includes a position sensor configured to detect movement of the needleless connector. For example, a patient movement, a patient fall event, a patient bed movement can be determined (e.g., by the smart device 104, etc.) based on the detected movement of the needleless connector.

[0101] In some non-limiting embodiments or aspects, the sensor 254 includes an RGB color sensor configured to detect a color of a fluid in the fluid flow path of the needleless connector. For example, at least one of blood collection in the needleless connector and retention of blood in the needleless connector may be determined based on a color of a fluid detected in the fluid flow path of the needleless connector (e.g., by the smart device 104, etc.).

[0102] In some non-limiting embodiments or aspects, the smart device 104 including the needleless connector 214 may include a visual indicator 252 that may be configured to provide a visual indication related to at least one of a cleaning event in which the needleless connector is cleaned with a disinfectant, a flushing event in which the needleless connector is rinsed with a solution, a connection event in which the needleless connector is connected to a medical device, or any combination thereof. For example, as shown in implementation 600B of FIG. 6B, the smart device 104 may provide direct patient-side feedback (e.g., via LED lighting to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a predetermined period of time and / or prior to a scheduled use, (ii) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a sufficient period of time prior to accessing the catheter line, (iii) detecting that flushing of the needleless connector 214 and / or lumen 212 is scheduled, (iv) detecting that a disinfecting cap was not installed after a previous access to the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include a needleless connector 214 that may be configured to detect at least one of a cleaning event, a flushing event, a connecting or capping event, or any combination thereof. As an example, the needleless connector 214 may be configured to provide information and / or data related to a detected cleaning event, a detected flushing event, and / or a detected connecting or capping event (e.g., using the processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to store the events and report compliance performance for monitoring compliance events.

[0103] 7 is a diagram of a non-limiting embodiment or aspect of a smart device implementation 700 for detecting drug extravasation or infiltration in a catheter. As shown in FIG. 7, the smart device 104 can be connected or integrated with a needleless connector 214 at the catheter hub of a catheter 702 that includes a catheter lumen or line 704 and a needle tip 706 for delivering fluid to a patient at the opposite end of the catheter line 704 from the smart device 104. The catheter 702 can be inserted into a patient's blood vessel (e.g., vein, artery, etc.) or urinary tract. For example, the location of the needle tip 706 can be within the patient's blood vessel or urinary tract, within the wall of the patient's blood vessel or urinary tract, or outside the wall of the patient's blood vessel or urinary tract and the wall of the blood vessel or urinary tract. In some non-limiting embodiments or aspects, the smart device 104 including the catheter 702 may include a wired and / or wireless transmitter configured to transmit (e.g., via a wire, wirelessly, etc.) at least one signal (and / or a variation in at least one signal over a period of time, the location of the needle tip relative to the patient's blood vessel or urinary tract, etc.) to a remote computer system or processing device.

[0104] In some non-limiting embodiments or aspects, the smart device 104 may include a sensor 254 (e.g., as shown in FIG. 2 ) located outside the patient's body (e.g., at a needleless connector 214 of a hub of the catheter 702 located outside the patient's body, the sensor 254 may be connected to the hub of the catheter 702 outside the patient's body, etc.). For example, the sensor 254 may include at least one of a pressure sensor and an acoustic sensor (e.g., a piezoelectric transducer, etc.). As an example, the sensor 254 including a pressure sensor and / or an acoustic sensor may be connected to the catheter 702 at the needleless connector 214 of the hub of the catheter 792. For example, the hub of the catheter 702 may include the needleless connector 214 and / or the smart device 104, and the sensor 254 may be included in the needleless connector 214. In such an example, the sensor 254 may be configured to sense, detect, and / or measure pressure signals, acoustic signals, and / or time variations of the pressure signals and / or acoustic signals with a catheter needle in the patient's body. For example, the pressure signal and / or acoustic signal sensed by sensor 254 may be transmitted through the fluid in the catheter and / or through the material of the catheter (e.g., via the needle tip 706, the catheter lumen 704, the needleless connector 214, etc.) for sensing by sensor 254. As an example, if the needle tip 706 punctures the wall of a patient's blood vessel or urinary tract, the pressure signal and / or acoustic signal sensed by sensor 254 may decrease or drop. In such an example, the decrease and / or absence of the pressure signal (e.g., decreased amplitude of the heartbeat and / or a drop in blood pressure, etc.) may indicate an absence of a pressure signal associated with an absence of a blood pressure signal, thereby indicating an infiltration event.

[0105] In some non-limiting embodiments or aspects, the smart device 104 may be programmed and / or configured to compare a relatively slower change or variation in the pressure signal over time (e.g., a relatively slower decrease in the amplitude of the heartbeat and / or a drop in blood pressure, etc.) to a threshold level to determine an occlusion event rather than an infiltration or extravasation event. For example, an occlusion in the lumen may occur at a relatively slow rate over time (e.g., compared to an infiltration event, extravasation event, disconnection event, etc.), which changes slowly in the pressure signal sensed by the sensor 254. As an example, the smart device 104 may determine an occlusion event, provide an alert, and / or automatically flush the lumen associated with the occlusion in response to detecting an occlusion event. In some non-limiting embodiments, the smart device 104 may detect a disconnection event in response to detecting a pressure signal substantially equal to atmospheric pressure by the sensor 254, which indicates a connection of the catheter 702, e.g., the needleless connector 214 is disconnected therefrom, and provide an alert to the user to address the connection.

[0106] In some non-limiting embodiments or aspects, the smart device 104 can provide the location of the needle tip relative to the patient's blood vessel or urinary tract in real time according to the pressure signal and / or the acoustic signal, thereby providing real-time feedback to the user when the catheter is placed in the patient's blood vessel or urinary tract to indicate whether the catheter is properly positioned within the blood vessel or urinary tract or whether there is one of potential or existing infiltration of fluid and potential or existing extravasation of fluid.

[0107] 8, which is a flow chart of a non-limiting embodiment or aspect of a process 800 for identifying a lumen. In some non-limiting embodiments or aspects, one or more of the steps of the process 800 are performed (e.g., fully, partially, etc.) by the drug source system 102 (e.g., one or more devices of the drug source system 102, etc.). In some non-limiting embodiments or aspects, one or more of the steps of the process 800 are performed (e.g., fully, partially, etc.) by another device or group of devices separate from or including the drug source system 102, such as the smart device 104 (e.g., one or more devices of the system of the smart device 104, etc.), the central computing system 108 (e.g., one or more devices of the central computing system 108, etc.), and / or the terminal / mobile computing system 110 (e.g., one or more devices of the terminal / mobile computing system 110, etc.).

[0108] 8, at step 802, the process 800 includes obtaining a user input associated with a drug source device. For example, the drug source system 102 may obtain a user input associated with the drug source device 206. As an example, the drug source system 102 may obtain (e.g., receive, retrieve, determine, etc.) the user input received via a user input component of the drug source device 206 (e.g., via the pairing input 208, etc.). In such an example, the drug source system 102 may receive data associated with the user input from the drug source device 206.

[0109] 2A , in some non-limiting embodiments or aspects, the multiple drug source devices 206a, 206b, ... 206n of the drug source system 102 are connected to the multiple lumens 212a, 212b, ... 212n, and each drug source device 206 may include a visual indicator 210, a communication circuit (e.g., communication interface 314, etc.), and a pairing input 208. In some non-limiting embodiments or aspects, the drug source device 206 receives a user input via the pairing input 208 of the drug source device 206. For example, the visual indicator 210 may emit a predetermined light pattern (e.g., blink rapidly and / or emit a predetermined color to indicate that the drug source device 206 is in pairing mode) in response to a predetermined user input to the pairing input 208 of the drug source device 206 (e.g., in response to a user pressing and holding a button on the pairing input 208, etc.).

[0110] 8, at step 804, the process 800 includes obtaining a user input associated with the smart device. For example, the drug source system 102 may obtain a user input associated with the smart device 104. As an example, the drug source system 102 may obtain (e.g., receive, retrieve, determine, etc.) a user input received via a user input component (e.g., pairing input 256, etc.) of the smart device 104. In such an example, the drug source system 102 may receive data associated with the user input from the smart device 104 that is received at the same time that the drug source device 206 is in pairing mode.

[0111] 2A and 2B, in some non-limiting embodiments or aspects, multiple smart devices 104a, 104b, ... 104n may be connected (e.g., removably connected, etc.) or configured to be connected to multiple lumens 212a, 212b, ... 212n, and each smart device 104 may include a visual indicator 252, a communication circuit (e.g., a communication interface 314, etc.), and a pairing input 256. In some non-limiting embodiments or aspects, the smart device 104 receives user input via the pairing input 256 of the smart device 104. For example, the smart device 104 may establish communication with the drug source device 206 (e.g., activate / initiate a pairing sequence for pairing the drug source device 206 with the smart device 104, etc.) in response to a predetermined user input to the pairing input 256 of the smart device 104 (e.g., in response to a user pressing and holding a button on the pairing input 256, etc.) at the same time that the drug source device 206 is in pairing mode.

[0112] As shown in FIG. 8 , in step 806, the process 800 includes establishing communication between the drug source device and the smart device. For example, the drug source system 102 may establish communication between the drug source device 206 and the smart device 104. As an example, the drug source system 102 may establish communication between the drug source device 206 and the smart device 104 (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, etc.). In such an example, the communication circuitry of the smart device 104 and the communication circuitry of the drug source device 206 may establish communication (e.g., pair, etc.) between the smart device 104 and the drug source device 206 based on a user input received by a pairing input 208 of the drug source device 206 and a user input received by a pairing input 256 of the smart device 104. For example, the drug source device 206 may establish a short-range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, etc.) with the smart device 104. As an example, the visual indicator 210 may be configured to emit a predetermined light pattern (e.g., blink quickly to indicate that the drug source device 206 is in pairing mode, etc.) in response to a predetermined user input to the pairing input 208 of the drug source device 206 (e.g., in response to a user pressing and holding a button on the pairing input 208, etc.). In such an example, the smart device 104 may be configured to establish communication with the drug source device 206 (e.g., pair the drug source device 206 with the smart device 104 and / or activate a pairing sequence for pairing therewith, etc.) in response to a predetermined user input to the pairing input 256 of the smart device 104 (e.g., in response to a user pressing and holding a button on the pairing input 256, etc.) at the same time that the drug source device 206 is in pairing mode.

[0113] 8, in step 808, the process 800 includes controlling the visual indicators of the drug source device and the smart device to generate the same type of visual output. For example, the drug source system 102 may control the visual indicator 210 of the drug source device 206 and the visual indicator 252 of the smart device 104 to generate the same type of visual output. As an example, the drug source system 102 may control the visual indicator 210 (e.g., a multi-colored LED, etc.) of the drug source device 206 and the visual indicator 252 (e.g., a multi-colored LED, etc.) of the smart device 104 to generate the same type of visual output (e.g., the same color light, etc.) based on the communication established between the drug source device and the smart device.

[0114] In some non-limiting embodiments or aspects, when the smart device 104 is paired with the drug source device 206, the drug source device 206 may illuminate the visual indicator 210 in a color not previously used in the drug source system 102 (e.g., a color not associated with another drug source device 206 and another smart device 104 paired in the drug source system 102, a color different from each other color of light generated by each other smart device 104 of the multiple smart devices 104a, 104b, ... 104n and each other drug source device 206 of the multiple drug source devices 206a, 206b, ... 206n in the drug source system 102, etc.), and the smart device 104 may illuminate the visual indicator 252 in the same color as the visual indicator 210 (e.g., the drug source system 102, the drug source device 206, the smart device 104, etc. may control the visual indicator 252 to illuminate in the same color as the visual indicator 210). In some non-limiting embodiments or aspects, the smart device 104 may illuminate the visual indicator 252 the same color as the visual indicator 210 in response to the smart device 104 being connected to the lumen and / or during the period of time that the smart device 104 is connected to the lumen. For example, the smart device 104 may automatically stop illuminating the visual indicator 252 the same color as the visual indicator 210 (e.g., turn off the LED, set the LED to a default color indicative of an unpaired smart device 104, etc.) in response to the smart device 104 being disconnected from the lumen. As an example, the smart device 104 may include a switch connected to the visual indicator 252 configured to be activated / deactivated in response to a clamp or other connection means being connected / disconnected from the lumen and / or its needleless connector 214.

[0115] In some non-limiting embodiments or aspects, the drug source system 102 determines the same color of light for the visual indicator 252 of the smart device 104 and the visual indicator 210 of the drug source device 206 to generate based on at least one of a user input received by the pairing input 208 of the drug source device 206 and a user input received by the pairing input 256 of the smart device 104. For example, after the smart device 104 is paired with the drug source device 206, a user may actuate the pairing input 208 and / or the pairing input 256 to cycle through the colors of lights available for pairing to select a desired (and / or available or previously unused) color of light for pairing.

[0116] As shown in FIG. 8, in step 810, the process 800 includes associating the same type of visual output with the same lumen. For example, the drug source system 102 may associate (e.g., automatically associate, etc.) the same type of visual output with the same lumen. As an example, the drug source system 102 may associate (e.g., store with, pair, link, illuminate with, etc.) the same type of visual output (e.g., the same color light, etc.) with the same lumen (e.g., the same lumen of the multiple lumens 212a, 212b, ... 212n, etc.). In such an example, the drug source device 206 and the smart device 104 may be connected to the same lumen. Thus, the user may more easily identify the lumen or line, the location of the lumen or line, the drug that was or is being delivered through the lumen or line, which infusion pump or line the lumen or line is connected to, etc.

[0117] In some non-limiting embodiments or aspects, the drug source system 102 may obtain a user input received by a user input component of the another drug source device, obtain a user input received by a user input component of the another smart device, establish communication between the another drug source device and the another smart device based on the user input received by the user input component of the another drug source device and the user input received by the user input component of the another smart device, and control a visual indicator of the another smart device and a visual indicator of the another drug source device to generate another same type of visual output based on the communication established between the another drug source device and the another smart device, where the another same type of visual output is different from the same type of visual output and / or associates the another same type of visual output with another same lumen of the multiple lumens, where the another drug source device is connected to the another same lumen. For example, referring again to FIG. 2A, the drug source device 206a may be paired with the smart device 104n, where each of the drug source device 206a and the smart device 104n may output light of a first color associated with the lumen 212a (e.g., red light), the drug source device 206b may be paired with the smart device 104a, where each of the drug source device 206b and the smart device 104a may output light of a second color associated with the lumen 212b (e.g., green light), the drug source device 206n may be paired with the smart device 104b, where each of the drug source device 206n and the smart device 104b may output light of a third color associated with the lumen 212n (e.g., blue light), etc.

[0118] 8, in step 812, the process 800 includes identifying the lumens. For example, the drug source system 102 may identify the lumens. As an example, the drug source system 102 may identify the same lumens associated with the same type of visual output.

[0119] In some non-limiting embodiments or aspects, the drug source system 102 identifies the lumen by automatically associating and / or providing the medical data with a visual output of the same type associated with the lumen and / or lumen identifier. For example, the medical data may include patient data (e.g., an identifier for a particular patient, information and / or data related to the patient, etc.), drug source data (e.g., an identifier for a particular drug source device 206, etc.), drug data (e.g., an identifier for a type of drug, a scheduled delivery of a particular drug, a previous delivery of a particular drug, a lumen associated with a drug, etc.), lumen data (e.g., an identifier for a particular lumen, such as an identifier for the same lumen associated with the same type of visual output, etc.), sensor data (e.g., an identifier for a particular sensor 254, information, data, and / or signals sensed, measured, and / or detected by one or more sensors 254 in one or more smart devices 104, etc.), compliance data (e.g., information or data related to a cleaning event in which the needleless connector 214 and / or lumen are cleaned with a disinfectant ... 214 and / or the lumen is flushed with a solution, information or data related to a flushing event in which the needleless connector 214 or lumen is connected to a medical device, information or data related to a connection or capping event in which the needleless connector 214 or lumen is connected to a medical device, etc.), location data (e.g., location of the patient, location of a previous or scheduled fluid delivery procedure, location of the lumen, location of the drug source device, etc.), time data (e.g., time related to a previous or scheduled fluid delivery procedure, time of connection of the lumen to the drug source device 206, time of connection of the smart device 104 to the lumen, time of pairing of the drug source device 206 with the smart device 104, etc.), location of the catheter needle tip of the lumen relative to the patient's blood vessel or urinary tract, or any combination thereof.As an example, the drug source system 102 may obtain medical data from the smart device 104, the central computing system 108, the terminal / mobile computing system 110, one or more databases connected thereto, and / or one or more sensors connected thereto (e.g., a barcode sensor for scanning an identifier of a patient identification, a fluid flow sensor for sensing a fluid flow, a drug type sensor for sensing a type of drug, etc.). In such an example, the drug source system 102 may identify a lumen having information and / or data associated therewith and provide a visual indication of which lumen of the plurality of lumens 212a, 212b, ... 212n is connected to which drug source device of the plurality of drug source devices 206a, 206b, ... 206n, which may allow a user to more easily trace a lumen from the patient to the particular drug source device to which it is connected and to more easily reattach the correct drug source device channel to the correct (e.g., the same as before) lumen. With the same type of visual indicator used for the source device pair, it can be possible for the connection between the lumen and the drug source device to be removed when the patient is moved (e.g., to a new room, new floor, operating room, bathroom, etc.), for example, to track compliance with best protocols by determining whether the hub has been cleaned and whether the hub has been cleaned effectively (e.g., enough pressure, cleaned for enough time, etc.) and / or whether the device has been flushed, maintained, etc., to provide reminders and prescriptive help for protocol compliance, etc.

[0120] In some non-limiting embodiments or aspects, the drug source system 102 identifies the lumen by determining and providing one or more alerts or reminders associated with the lumen and / or the same type of visual output associated with the lumen based on the medical data, such as a reminder to flush the lumen and / or its needleless connector 214, a reminder to remove or replace the lumen, med-mined infection prevention guidance, an alert to use a different lumen for delivery of a particular drug to reduce the possibility of formation of a chemical blockage, an alert indicating whether the lumen should be treated for a thrombotic or chemical blockage, an alert that an obstruction has been detected in the lumen, an alert in which the location of the tip of a needle connected to the lumen is associated with one of potential or existing infiltration of fluid and potential or existing extravasation of fluid, etc.

[0121] In some non-limiting embodiments or aspects, the drug source system 102 identifies a lumen by controlling the drug source device 206 or another medical device (e.g., an electronic valve, etc.) based on the medical data to inhibit or prevent delivery of a fluid (e.g., a particular drug, a type of drug, etc.) through the lumen.

[0122] Further details regarding non-limiting embodiments or aspects of process 800 are provided below with respect to FIG.

[0123] 9, which is a flow chart of a non-limiting embodiment or aspect of a process 900 for identifying a lumen. In some non-limiting embodiments or aspects, one or more of the steps of the process 900 are performed (e.g., fully, partially, etc.) by the drug source system 102 (e.g., one or more devices of the drug source system 102, etc.). In some non-limiting embodiments or aspects, one or more of the steps of the process 900 are performed (e.g., fully, partially, etc.) by another device or group of devices separate from or including the drug source system 102, such as the smart device 104 (e.g., one or more devices of the system of the smart device 104, etc.), the central computing system 108 (e.g., one or more devices of the central computing system 108, etc.), and / or the terminal / mobile computing system 110 (e.g., one or more devices of the terminal / mobile computing system 110, etc.).

[0124] 9, at step 902, the process 900 includes acquiring drug data. For example, the drug source system 102 may acquire the drug data. As an example, the drug source system 102 may acquire drug data related to a first type of drug delivered or scheduled to be delivered to a patient through the same lumen and a second type of drug delivered or scheduled to be delivered to a patient through the same lumen. In such an example, the first type of drug may be different from the second type of drug.

[0125] In certain non-limiting embodiments or aspects, the drug data is associated with at least one of an identifier for a type of drug, a scheduled delivery of the drug through a particular drug source device and / or lumen, a previous delivery of the drug through a particular drug source device and / or lumen, an amount of the drug, an identifier for a patient for whom the drug is scheduled to be delivered (or to whom it has been delivered), one or more identifiers of one or more different types of drugs that are not compatible for delivery through the same lumen as the drug, and / or the like.

[0126] 9, at step 904, the process 900 includes determining suitability of the medication. For example, the medication source system 102 may determine the suitability of the medication. As an example, the medication source system 102 may determine the suitability of a second type of medication for delivery via the same lumen as a first type of medication based on the medication data.

[0127] In some non-limiting embodiments or aspects, the drug source system 102 may use the first type drug identifier and / or the second type drug identifier to access a lookup table that indicates whether the first type drug and the second type drug are compatible or incompatible (e.g., compatible or incompatible for delivery via the same lumen, etc.). In some non-limiting embodiments or aspects, the lookup table may be stored in and / or associated with the first type drug identifier and / or the second type drug identifier.

[0128] In some non-limiting embodiments or aspects, the drug source system 102 may obtain drug data related to a third type of drug delivered or scheduled to be delivered to the patient through another same lumen (e.g., different from the same lumen) and determine, based on the drug data, suitability of the second type of drug for delivery through the same other lumen as the third type of drug, where the display further indicates whether the second type of drug is compatible for delivery through another same lumen associated with another same type of visual output. For example, referring again to Figures 2A and 2B, if the drug source system 102 determines that the second type of drug is not compatible for delivery through the first lumen 212a, the drug source system 102 may determine the suitability of the second type of drug for delivery through an alternative lumen, such as the second lumen 212b, based on a third type of drug that has been delivered or is scheduled to be delivered through the second lumen 212b, and if the second type of drug is compatible for delivery through the same lumen as the third type of drug, provide an indication that the second type of drug is compatible for delivery through the second lumen 212b.

[0129] 9, at step 906, the process 900 includes providing an indication of compatibility. For example, the drug source system 102 may provide an indication of compatibility. As one example, the drug source system 102 may provide an indication of whether a second type of drug is compatible for delivery through the same lumen associated with the same type of visual output. As another example, the drug source system 102 may provide an indication of whether a third type of drug is compatible for delivery through another same lumen associated with another same type of visual output.

[0130] In some non-limiting embodiments or aspects, the drug source system 102 may provide an indication of compatibility by controlling the drug source device 206 to inhibit or prevent delivery of a second drug through the same lumen associated with the same type of visual output. For example, a first type of drug may be delivered to a patient with the same lumen associated with the same type of visual output, and a second type of drug may be scheduled to be delivered to the patient through the same lumen. By way of example, and referring again to FIGS. 2A and 2B, the drug source system 102 may determine, based on the medical data including the drug data, that a first type of drug is delivered to the patient through lumen 212a, and a second type of drug scheduled or attempting to be delivered through the same lumen 212a is incompatible with the first type of drug (e.g., may cause a blockage, may cause an adverse drug reaction in the patient, etc.). In such an example, the drug source system 102 may control the drug source device 206a to inhibit or prevent (e.g., by stopping the pump, closing a valve, etc.) delivery of the second drug through the same lumen 212a and / or prompting the user to use another lumen (e.g., 212b, ... 212n, etc.) associated with a different type of visual output from the same type of visual output to deliver a second type of drug to the patient.

[0131] In some non-limiting embodiments or aspects, a first type of drug and a second type of drug may be delivered to the patient through the same lumen associated with the same type of visual output, and the drug source system 102 may prompt the user to treat the same lumen associated with the same type of visual output for one of a thrombotic occlusion and a chemical occlusion. For example, when an occlusion occurs that may be detected by the drug source system 102 as described herein, a user (e.g., a nurse, etc.) may need to determine whether the occlusion is thrombotic or chemical due to a drug interaction, and the drug source system 102 may determine which drug was delivered through which lumen to inform the user about the history of the lumen and / or provide an indication of the potential cause of the occlusion, thereby enabling a correct decision as to whether the lumen should be treated for a thrombotic occlusion or a chemical occlusion. In some non-limiting embodiments or aspects, the drug source system 102 may control the drug source device 206 to automatically perform a flushing operation to deliver flushing fluid to a lumen connected to the drug source device 206 in response to determining that the blockage in the lumen is a chemical blockage.

[0132] 10, which is a flow chart of a non-limiting embodiment or aspect of a process 1000 for identifying a needle tip location. In some non-limiting embodiments or aspects, one or more of the steps of the process 1000 are performed (e.g., fully, partially, etc.) by the smart device 104 (e.g., one or more devices of the system of the smart device 104, etc.). In some non-limiting embodiments or aspects, one or more of the steps of the process 1000 are performed (e.g., fully, partially, etc.) by another device or group of devices separate from or including the smart device 104, such as the drug source system 102 (e.g., one or more devices of the system of the drug source system 102), the central computing system 108 (e.g., one or more devices of the central computing system 108, etc.), and / or the terminal / mobile computing system 110 (e.g., one or more devices of the terminal / mobile computing system 110, etc.).

[0133] As shown in FIG. 10, in step 1002, the process 1000 includes obtaining a signal including at least one of a pressure signal and an acoustic signal. For example, the smart device 104 may obtain a signal including at least one of a pressure signal and an acoustic signal from at least one sensor connected to the catheter. As an example, the smart device 104 may obtain at least one signal including at least one of a pressure signal and an acoustic signal from a sensor 254 connected to the catheter 702 (e.g., from a pressure sensor, from an acoustic sensor, etc.). In some non-limiting embodiments or aspects, and referring to FIG. 7, the catheter 702 includes a needle having a tip 706 for delivering fluid to the patient.

[0134] In some non-limiting embodiments or aspects, the sensor 254 measures at least one signal including at least one of a pressure signal and an acoustic signal. For example, the sensor 254 may measure at least one signal including at least one of a pressure signal and an acoustic signal, and the smart device 104 (and / or the drug source system 102, the central computing system, 108, and / or the terminal / mobile computing system 110) may obtain the at least one signal including at least one of the pressure signal and the acoustic signal from the sensor 254. For example, the smart device 104 may include a communication circuit (e.g., communication interface 314, etc.) that wirelessly transmits at least one signal to a remote computing system. As an example, the smart device 104 may process the pressure and / or acoustic signals on a microprocessor within the housing of the smart device 104 that contains the sensor 254 and the microprocessor, and / or the smart device 104 may wirelessly transmit (and / or transmit via a wired connection) the pressure and / or acoustic signals to a remote computer that performs digital signal processing on the pressure and / or acoustic signals to identify and classify events of interest (e.g., infiltration, extravasation, catheter obstruction, etc.).

[0135] 10, in step 1004, the process 1000 includes determining a location of a needle tip of the catheter relative to a blood vessel or urinary tract of the patient. For example, the smart device 104 may determine a location of the needle tip relative to a blood vessel or urinary tract of the patient. As an example, the smart device 104 may determine a location of the needle tip 706 relative to a blood vessel or urinary tract of the patient based on a variability of at least one signal over a period of time.

[0136] In some non-limiting embodiments or aspects, the location of the needle tip 706 is determined as one of within a blood vessel or urinary tract, within a wall of a blood vessel or urinary tract, and outside the blood vessel or urinary tract and the wall of the blood vessel or urinary tract. In some non-limiting embodiments or aspects, the smart device 104 and / or one or more components thereof may be connected to or included within (e.g., integrated with) a needleless connector 214 at a catheter hub of the catheter 702 located outside the patient's body. For example, the sensor 254 (e.g., a pressure sensor, an acoustic sensor, etc.) of the smart device 104 may measure at least one signal including at least one of a pressure signal and an acoustic signal, where the catheter includes a needle having a tip for delivering fluid to the patient.

[0137] In some non-limiting embodiments or aspects, the smart device 104 determines that the location of the needle tip 706 is associated with one of potential or existing infiltration of fluid and potential or existing extravasation of fluid. For example, the sensor 254 (e.g., one or more pressure sensors, one or more acoustic sensors, etc.) may detect time variations in pressure and / or acoustic signals resulting from the needle tip 706 of the catheter 702 being properly inserted into a blood vessel or urinary tract, being located in the wall of the blood vessel or urinary tract, being located outside the blood vessel or urinary tract, etc. As an example, the smart device 104 may compare the variation of at least one signal over a period of time with a threshold variation associated with the patient's heartbeat. For example, the variation of the pressure and / or acoustic signal may be associated with pressure and / or acoustic variations in the blood vessel or urinary tract as a result of the patient's heartbeat. As an example, the smart device 104 may compare the detected pressure signal and / or detected acoustic signal fluctuations with pressure and / or acoustic signal fluctuations associated with the patient's heartbeat to determine whether the needle tip 706 of the catheter 702 is properly positioned within the patient's blood vessel (e.g., artery, vein, etc.). In such an example, if the needle tip 706 of the catheter 702 overshoots the tube or urinary tract (e.g., punctures the wall of the blood vessel or urinary tract, is not properly within the blood vessel or urinary tract, etc.), the pressure and / or acoustic signature of at least one signal measured by the sensor 254 changes. In some non-limiting embodiments or aspects, infiltration or extravasation of the agent into tissue surrounding the blood vessel or urinary tract (but not within the blood vessel or urinary tract) may result in characteristic pressure or acoustic signals being detected by the sensor 254 depending on the effect of the infiltration or extravasation on the surrounding tissue (e.g., if the extravasating agent is a strong vesicant, such effect may be severe, etc.).

[0138] In some non-limiting embodiments or aspects, the smart device 104 determines at least one of an occlusion of the catheter and a disconnection of the catheter from the needleless connector based on a variation of the at least one signal over a period of time. For example, the smart device 104 may compare the variation of the at least one signal over a period of time to a threshold period of time associated with the formation of an occlusion in the catheter. As an example, the smart device 104 may compare a relatively slower change or variation of the pressure signal over time (e.g., a relatively slower decrease in the amplitude of the heartbeat and / or a drop in blood pressure compared to an occlusion or extravasation) to a threshold level to determine an occlusion event rather than an occlusion event or an extravasation event. For example, an occlusion in the lumen may occur at a relatively slow rate over time (e.g., compared to an occlusion event, an extravasation event, a disconnection event, etc.), which may change slowly in the pressure signal sensed by the sensor 254. As an example, the smart device 104 may determine an occlusion event, provide an alarm, and / or automatically flush the lumen associated with the occlusion in response to detecting the occlusion event. In some non-limiting embodiments, the smart device 104 may detect a disconnection event in response to detecting a pressure signal substantially equal to atmospheric pressure by the sensor 254, indicating connection of the catheter 702, e.g., the needleless connector 214, therefrom and providing an alert to the user to address the connection.

[0139] 10, in step 1006, the process 1000 includes providing a location of the tip of the needle. For example, the smart device 104 may provide the location of the tip of the needle. As an example, the smart device 104 may provide the location of the tip of the needle 706 relative to a blood vessel or urinary tract of the patient.

[0140] In some non-limiting embodiments or aspects, the smart device 104 controls the warning device to issue a warning associated with one of a potential or existing infiltration of fluid and a potential or existing extravasation of fluid. For example, the smart device 104 controls the visual indicator 252 of the smart device 104 to output a color and / or pattern of light associated with one of a potential or existing infiltration of fluid and a potential or existing extravasation of fluid. As an example, in response to determining an event as an infiltration, extravasation, or catheter blockage, the smart device 104 may flash a warning light to a user (e.g., a clinician, a caregiver, a family member, another patient at home or in an assisted living environment, etc.) and / or send a signal to a remote computing system (e.g., the drug source system 102, the central computing system 108, the terminal / mobile computing system 110, etc.) to control (e.g., trigger) the output of an audio and / or visual alarm at the remote computing system to alert appropriate individuals about the determined event.

[0141] In some non-limiting embodiments or aspects, the smart device 104 controls the drug source device 206 or a valve (e.g., a valve controlling fluid delivery to or from the catheter 702, etc.) to stop (e.g., inhibit, prevent, etc.) fluid delivery to and / or from the catheter. As an example, in response to determining an event as infiltration, extravasation, catheter obstruction, or catheter disconnection, the smart device 104 may signal an infusion device to immediately stop drug infusion or signal a valve or mechanical clamp to block further drug from being infused into the catheter and / or the patient.

[0142] In some non-limiting embodiments or aspects, the smart device 104 and / or the needle-free catheter 214 may include a communication circuit (e.g., communication interface 314, etc.) that wirelessly transmits at least one signal to a remote computing system. As an example, the smart device 104 and / or the needle-free catheter 214 may process the pressure and / or acoustic signals on a microprocessor in the housing 250 of the smart device 104 and / or in the housing 250 of the needle-free catheter 214 that includes the sensor 254 and the microprocessor, and / or the smart device 104 and / or the needle-free catheter 214 may wirelessly transmit (and / or transmit via a wired connection) the pressure and / or acoustic signals to a remote computer that performs digital signal processing on the pressure and / or acoustic signals to identify and classify events of interest (e.g., infiltration, extravasation, catheter obstruction, catheter disconnection, etc.).

[0143] In some non-limiting embodiments or aspects, the smart device 104 may provide real-time feedback during insertion of the catheter (e.g., via the visual indicator 252, the output component 312, the drug source system 102, etc.) so that a clinician or other person may be alerted as to whether the catheter 702 is properly inserted and / or whether the needle tip 706 of the catheter 702 has penetrated or is in the process of penetrating a blood vessel or urinary tract and / or has been accidentally cut or occluded.

[0144] 11, which is a flow chart of a non-limiting embodiment or aspect of a process 1100 for monitoring for matching events. In some non-limiting embodiments or aspects, one or more of the steps of the process 1100 are performed (e.g., fully, partially, etc.) by the smart device 104 (e.g., one or more devices of the system of the smart device 104, etc.). In some non-limiting embodiments or aspects, one or more of the steps of the process 1100 are performed (e.g., fully, partially, etc.) by another device or group of devices separate from or including the smart device, such as the drug source system 102 (e.g., one or more devices of the system of the drug source system 102), the central computing system 108 (e.g., one or more devices of the central computing system 108, etc.), and / or the terminal / mobile computing system 110 (e.g., one or more devices of the terminal / mobile computing system 110, etc.).

[0145] 11, in step 1102, the process 1100 includes acquiring a force signal. For example, the smart device 104 may acquire the force signal. As an example, the smart device 104 may acquire a force signal measured by a sensor 252 (e.g., a force sensor, etc.) connected to a needleless connector 214 including a fluid flow path. In such an example, the sensor 252 may measure the force signal using a force sensor connected to a needleless connector including a fluid flow path, and the smart device 104 (and / or the drug source system 101, the central computing system 108, the terminal / mobile computing system 110, etc.) may acquire the force signal from the sensor 252.

[0146] 11, in step 1104, the process 1100 includes determining an event associated with the needleless connector based on the force signal. For example, the smart device 104 may determine an event associated with the needleless connector 214 based on the force signal. As an example, the smart device 104 may determine at least one of a cleaning event in which the needleless connector is cleaned with a disinfectant, a flushing event in which the needleless connector is flushed with a solution, a connection event in which the needleless connector is connected to a medical device, or any combination thereof based on the force signal.

[0147] In some non-limiting embodiments or aspects, the force sensor 502 includes at least one of a piezoelectric element, a force sensitive resistive film (FSR) sensor, a strain gauge, or any combination thereof. In some non-limiting embodiments or aspects, the force sensor 502 is located between an outer surface of an inner wall 510 (e.g., an inner harder plastic wall) of the needleless connector 214 that defines the fluid flow path of the needleless connector 214 and an inner surface of an outer wall 512 (e.g., a softer, more flexible, more pliable, rubber, etc. wall) of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214. In some non-limiting embodiments or aspects, the area between the outer surface of the inner wall 510 (e.g., an inner harder plastic wall) of the needleless connector 214 that defines the fluid flow path of the needleless connector 214, which may be held by a user during cleaning and / or connection to another medical device, and the inner surface of the outer wall 512 (e.g., a softer, more pliable, more compliant, rubber, etc. wall) of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214, may be filled with rubber or other pliable type material 514 that includes a force sensor 502 as a force sensing film in the material 514 between the inner wall 510 and the outer wall 512. In some non-limiting embodiments or aspects, the force sensor 502 may be located between the inner wall 510 and the outer wall 512 below the threads on and / or near the inlet 404 of the needleless connector 214.

[0148] In some non-limiting embodiments or aspects, the force sensor 502 includes a plurality of force sensors 502 positioned about the fluid flow path of the needleless connector 214 between an outer surface of an inner wall 510 of the needleless connector 214 that defines the fluid flow path of the needleless connector 214 and an inner surface of an outer wall 512 of the needleless connector 214 that surrounds the inner wall 510 of the needleless connector 214. For example, the inlet 404 of the needleless connector 214 may include a septum 408 that includes a face that faces in a first direction, and the force sensor 502 may be configured to detect a force in a second direction that is perpendicular to the face of the septum that faces in the first direction. As an example, a flush event, which may include a pulsating flush event, may be determined based on a force signal indicative of a periodic force in a second direction that is perpendicular to the face of the septum that faces in the first direction.

[0149] In some non-limiting embodiments or aspects, the sensor 254 includes a pressure sensor that is one of: in direct contact with the fluid in the fluid flow path of the needleless connector; located within an inner wall of the needleless connector that defines the fluid flow path of the needleless connector; and located within a wall of a lumen connected to the needleless connector. For example, the smart device 104 may determine or detect pulsatile flushing, flushing, and / or drug administration by a pressure sensor in contact with the fluid path in the needleless connector 214 and / or its lumen.

[0150] In some non-limiting embodiments or aspects, the sensor 254 includes an optical sensor configured to detect at least one of a color signature and a reflectance of a medical device connected to and / or coupled to the needleless connector 214, and the smart device 104 may determine a type of medical device based on at least one of the color signature and the reflectance of the medical device. For example, the color signature and / or reflectance of the medical device may be indicative of a syringe, an IV bag, an infusion pump, and / or a particular type thereof.

[0151] In some non-limiting embodiments or aspects, the sensor 254 includes an identification sensor configured to detect an identification tag on a medical device connected to or coupled to the needleless connector. For example, the identification sensor may include a magnetometer and the identification tag may include a magnetic material on and / or integrated with the needleless connector 214.

[0152] In some non-limiting embodiments or aspects, the sensor 254 includes a position sensor configured to detect movement of the needleless connector. For example, a patient movement, a patient fall event, a patient bed movement can be determined (e.g., by the smart device 104, etc.) based on the detected movement of the needleless connector.

[0153] In some non-limiting embodiments or aspects, the sensor 254 includes an RGB color sensor configured to detect a color of a fluid in the fluid flow path of the needleless connector. For example, at least one of blood collection in the needleless connector and retention of blood in the needleless connector may be determined based on a color of a fluid detected in the fluid flow path of the needleless connector (e.g., by the smart device 104, etc.).

[0154] 11, in step 1106, the process 1100 includes providing an indication of the event. For example, the smart device 104 may provide an indication of the event. For example, the smart device 104 may provide an indication of the determined event.

[0155] In some non-limiting embodiments or aspects, the smart device 104 including the needleless connector 214 may include a visual indicator 252 that may be configured to provide a visual indication related to at least one of a cleaning event in which the needleless connector is cleaned with a disinfectant, a flushing event in which the needleless connector is rinsed with a solution, a connection event in which the needleless connector is connected to a medical device, or any combination thereof. For example, as shown in implementation 600B of FIG. 6B, the smart device 104 may provide direct patient-side feedback (e.g., via LED lighting to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a predetermined period of time and / or prior to a scheduled use, (ii) detecting that the needleless connector 214 and / or its lumen 212 have not been cleaned for a sufficient period of time prior to accessing the catheter line, (iii) detecting that flushing of the needleless connector 214 and / or lumen 212 is scheduled, (iv) detecting that a disinfecting cap was not installed after a previous access to the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include a needleless connector 214 that may be configured to detect at least one of a cleaning event, a flushing event, a connecting or capping event, or any combination thereof. As an example, the needleless connector 214 may be configured to provide information and / or data related to a detected cleaning event, a detected flushing event, and / or a detected connecting or capping event (e.g., using the processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to store the events and report compliance performance for monitoring compliance events.

[0156] In some non-limiting embodiments or aspects, the smart device 104 may include communication circuitry (e.g., communication interface 314, etc.) that wirelessly transmits the force signal and / or events determined therefrom to a remote computing system. As an example, the smart device 104 may process the force signal on a microprocessor within a housing of the smart device 104 that includes the sensor 254 and the microprocessor, and / or the smart device 104 may wirelessly transmit the force signal (and / or transmit via a wired connection) to a remote computer that performs digital signal processing on the force signal to identify and classify events of interest (e.g., cleaning events, flushing events, connection events, etc.).

[0157] In some non-limiting embodiments or aspects, a pattern of events including at least one of a cleaning event in which the needleless connector 214 is cleaned with a disinfectant, a flushing event in which the needleless connector 214 is rinsed with a solution, a connecting or capping event in which the needleless connector 214 is connected to a medical device, or any combination thereof can be determined based on the force signal, and based on the pattern of events, a drug administration event in which a drug is administered to a patient via the needleless connector 214 can be determined.

[0158] In some non-limiting embodiments or aspects, the smart device 104 may detect an identification tag on a medical device connected or attached to the needleless connector, movement of the needleless connector, color of fluid in the fluid flow path of the needleless connector, or any combination thereof, and use the visual indicator 252 to provide a visual indication related to any information or data sensed and / or measured by the sensor 254, such as a type of medical device, a drug administration event in which a drug is administered to a patient through the needleless connector, an identification of the medical device, a patient movement, a patient fall event, a patient bed movement, color of fluid in the fluid flow path of the needleless connector 412, blood collection in the needleless connector, retention of blood in the needleless connector, a cleaning event in which the needleless connector is cleaned with a disinfectant, a flushing event in which the needleless connector is flushed with a solution, a connecting or capping event in which the needleless connector is connected to a medical device, or any combination thereof.

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

Claims

1. a plurality of smart devices configured to be connected to the plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component configured to receive user input from a user; a drug source system including a plurality of drug source devices connected to the plurality of lumens, each drug source device including a visual indicator, a communication circuit, and a user input component configured to receive a user input from the user, the communication circuit of the drug source device configured to establish communication with the communication circuit of a smart device based on the user input to the user input component of the drug source device and the user input to the user input component of the smart device; Based on the communication established between the communication circuitry of the drug source device and the communication circuitry of the smart device, control the visual indicator of the smart device and the visual indicator of the drug source device to generate the same type of visual output; associating said same type of visual output with a same lumen of said plurality of lumens; one or more processors programmed and / or configured to Equipped with The drug source device is connected to the same lumen.

2. 10. The system of claim 1, wherein the visual indicators of the smart devices include light emitting diodes, and the visual outputs of the same type are lights of the same color.

3. The light emitting diode is configured to emit light of a plurality of different colors, and the one or more processors: determining and generating the same color of light for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of the user input to the user input component of the drug source device and the user input to the user input component of the smart device; The system of claim 2 further programmed and / or configured to:

4. The light emitting diode is configured to emit light of a plurality of different colors, and the one or more processors: The system of claim 2, further programmed and / or configured to determine the same color of light for the visual indicator of the smart device and the visual indicator of the drug source device, and to generate a light of a different color than each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each visual indicator of each other drug source device of the plurality of drug source devices.

5. The system of claim 1 , wherein the drug source system comprises an infusion pump system, and the plurality of drug source devices comprises a plurality of infusion pumps.

6. 2. The system of claim 1, wherein the visual indicator of the smart device is configured to generate the same type of visual output as the visual indicator of the drug source device in response to being connected to a lumen at the same time that the communication is established between the communication circuitry of the drug source device and the communication circuitry of the smart device, and the visual indicator of the smart device is configured to automatically stop generating the same type of visual output as the visual indicator of the drug source device in response to being disconnected from the lumen.

7. The communication circuitry of the other drug source device is configured to establish communication with the communication circuitry of the other smart device based on the user input to the user input component of the other drug source device and the user input to the user input component of the other smart device, and the one or more processors are configured to: Based on the communication established between the communication circuitry of the other drug source device and the communication circuitry of the other smart device, control the visual indicator of the other smart device and the visual indicator of the other drug source device to generate another same type of visual output, wherein the other same type of visual output is different from the same type of visual output; associating said different same type visual outputs with different same lumens of said plurality of lumens; and / or further configured to: The system of claim 1 , wherein the other drug source device is connected to the same other lumen.

8. connecting a plurality of smart devices to a plurality of lumens, each smart device including a visual indicator, a communication circuit, and a user input component; connecting a plurality of drug source devices of a drug source system to the plurality of lumens, each drug source device including a visual indicator, a communication circuit, and a user input component; receiving user input via the user input component of a smart device; receiving a user input via the user input component of a drug source device; establishing communication between the smart device and the drug source device using the communication circuitry of the smart device and the communication circuitry of the drug source device based on the user input received by the user input component of the drug source device and the user input received by the user input component of the smart device; controlling, with at least one processor, the visual indicator of the smart device and the visual indicator of the drug source device to generate the same type of visual output based on the communication established between the drug source device and the smart device; using at least one processor to associate the same type of visual output with a same lumen of the plurality of lumens, the drug source device being connected to the same lumen; A method comprising:

9. 10. The method of claim 8, wherein the visual indicators of the smart devices include light emitting diodes, and the visual outputs of the same type are lights of the same color.

10. The light emitting diode is configured to emit light of a plurality of different colors, and the method further comprises:

10. The method of claim 9, further comprising: determining and generating, with at least one processor, a color of light of the same color for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of the user input received by the user input component of the drug source device and the user input received by the user input component of the smart device.

11. 10. The method of claim 9, wherein the light emitting diode is configured to emit light of a plurality of different colors, the method further comprising: determining, with at least one processor, the same color of light for the visual indicator of the smart device and the visual indicator of the drug source device, and generating light of a color that is different from each other color of light generated by each visual indicator of each other smart device of the plurality of smart devices and each visual indicator of each other drug source device of the plurality of drug source devices.

12. 10. The method of claim 8, wherein the drug source system comprises an infusion pump system, and the multiple drug source devices comprise multiple infusion pumps.

13. generating, with the visual indicator of the smart device, the visual output of the same type as the visual indicator of the drug source device in response to being connected to a lumen at the same time that the communication is established between the drug source device and the smart device; using the visual indicator of the smart device to automatically cease generating the visual output of the same type as the visual indicator of the drug source device in response to being disconnected from the lumen; The method of claim 8 , further comprising:

14. receiving user input by the user input component of another smart device; receiving a user input by the user input component of a separate drug source device; establishing communication between the other drug source device and the other smart device using the communication circuitry of the other drug source device and the communication circuitry of the other smart device based on the user input received by the user input component of the other drug source device and the user input received by the user input component of the other smart device; controlling, with at least one processor, the visual indicator of the other smart device and the visual indicator of the other drug source device to generate another same type visual output based on the communication established between the other drug source device and the other smart device, where the other same type visual output is different from the same type visual output; associating, with at least one processor, the different same type of visual output with a different same lumen of the plurality of lumens, the different drug source device being connected to the different same lumen; The method of claim 8 further comprising:

15. In response to a user input to a drug source device and a smart device establishing communication between a communication circuit of the drug source device and a communication circuit of the smart device, a visual indicator of the smart device and a visual indicator of the drug source device are controlled to generate the same type of visual output, the drug source device is connected to a lumen, and the smart device is configured to be connected to the lumen; associating said same type of visual output with said lumen; 20. A system comprising one or more processors programmed and / or configured to:

16. In response to communication being established between a communication circuit of the drug source device and a communication circuit of the smart device by user input to the drug source device and smart device, a step of controlling, using at least one processor, a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output, wherein the drug source device is connected to a lumen and the smart device is configured to be connected to the lumen; using at least one processor to associate the same type of visual output with the lumen; A computer-implemented method comprising:

17. When executed by at least one processor, the at least one processor is caused to: In response to a user input to a drug source device and a smart device establishing communication between the communication circuitry of the drug source device and the communication circuitry of the smart device, control a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output, the drug source device is connected to a lumen, and the smart device is configured to be connected to the lumen; associating said same type of visual output with said lumen; At least one non-transitory computer readable medium containing program instructions to cause

18. In response to a user input to a drug source device and a smart device establishing communication between a communication circuit of the drug source device and a communication circuit of the smart device, a visual indicator of the smart device and a visual indicator of the drug source device are controlled to generate the same type of visual output, the drug source device is connected to a lumen, and the smart device is configured to be connected to the lumen; associating said same type of visual output with said lumen; providing the same type of visual output to a user and identifying the lumen to the user.

2. A system comprising one or more processors programmed and / or configured to:

19. In response to communication being established between a communication circuit of the drug source device and a communication circuit of the smart device by user input to the drug source device and the smart device, a step of controlling, using at least one processor, a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output, wherein the drug source device is connected to a lumen and the smart device is configured to be connected to the lumen; using at least one processor to associate the same type of visual output with the lumen; providing, with at least one processor, the same type of visual output to a user and identifying the lumen to the user; A computer-implemented method comprising:

20. When executed by at least one processor, the at least one processor is caused to: In response to a user input to a drug source device and a smart device establishing communication between the communication circuitry of the drug source device and the communication circuitry of the smart device, control a visual indicator of the smart device and a visual indicator of the drug source device to generate the same type of visual output, the drug source device is connected to a lumen, and the smart device is configured to be connected to the lumen; associating said same type of visual output with said lumen; providing the same type of visual output to a user, identifying the lumen to the user; At least one non-transitory computer readable medium containing program instructions.

Images