Systems, methods, and products for identifying a lumen

Abstract

The visual indicators of the smart device and the drug delivery device can be controlled to produce the same type of visual output based on communication established between the drug delivery device and the smart device. The drug delivery device can be connected to a lumen, the smart device can be configured to connect to a lumen, and the same type of visual output can be associated with the lumen. The compatibility of a first type of drug delivered or planned to be delivered to the patient via the lumen and a second type of drug delivered or planned to be delivered to the patient via the lumen can be determined to indicate whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 62 / 800,609, filed February 4, 2019, entitled “System, Method and Products for Identification Alumes,” the entire disclosure of which is incorporated herein by reference. Background Technology

[0003] Patients 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 the emergency room may be connected to ten or more fluid lines simultaneously. Multiple fluid lines can lead to confusion about which fluid line at the patient's location is connected to which infusion pump or fluid source. For example, when ordering line maintenance, a nurse may have to trace the fluid lines from the infusion pump or fluid source to the fluid line at the patient's location, and vice versa. However, when multiple fluid lines cross, overlap, and / or become tangled, it can be difficult to identify the correct line for maintenance, infusion, removal, etc. Summary of the Invention

[0004] Therefore, improved systems, devices, products, equipment and / or methods for identifying lumens are provided.

[0005] According to some non-limiting embodiments or aspects, a system is provided, comprising: a plurality of smart devices configured to be connected to a plurality of lumens, wherein each smart device includes a visual indicator, communication circuitry, and a user input component configured to receive user input from a user; a drug source system comprising a plurality of drug source devices connected to the plurality of lumens, wherein each drug source device includes a visual indicator, communication circuitry, and a user input component configured to receive user input from a user, wherein the communication circuitry of the drug source devices is configured to establish communication with the communication circuitry of the smart devices based on user input to the user input component of the drug source devices and user input to the user input component of the smart devices; and one or more processors programmed and / or configured to: based on drug... Communication is established between the communication circuitry of the source device and the communication circuitry of the smart device to control the visual indicator of the smart device and the visual indicator of the drug source device to produce the same type of visual output; the same type of visual output is associated with the same lumen in a plurality of lumens, wherein the drug source device is connected to the same lumen; drug data associated with a first type of drug delivered or planned to be delivered to a patient via the same lumen and a second type of drug delivered or planned to be delivered to a patient via the same lumen, wherein the first type of drug is different from the second type of drug; based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug is determined; and an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output is provided.

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

[0007] In some non-limiting embodiments or aspects, the light-emitting diode is configured to emit light of multiple different colors, and said one or more processors are further programmed and / or configured to: determine the color of light of the same color to be generated for the visual indicator of the smart device and the visual indicator of the drug source device based on at least one of user input to the user input component of the drug source device and user input to the 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 variety of different colors, and wherein the one or more processors are further programmed and / or configured to: determine light of the same color for the visual indicator of the smart device and the visual indicator of the drug source device to produce light of a different color from each other color produced by each visual indicator of each of the other smart devices and each visual indicator of each of the other drug source devices.

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

[0010] In some non-limiting embodiments or aspects, a first type of drug is delivered to a patient via the same lumen, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein the one or more processors are programmed and / or configured to provide an indication of whether the second type of drug is compatible with 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 drug is delivered to a patient via the same lumen, wherein a second type of drug is planned to be delivered to a patient via the same lumen, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to use a different lumen associated with a different type of visual output than the same type of visual output to deliver the second type of drug to the patient.

[0012] In some non-limiting embodiments or aspects, the first type of drug and the second type of drug are delivered to the patient via the same lumen associated with the same type of visual output, and wherein the indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to treat the same lumen associated with the same type of visual output for one of thromboembolism and 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 connection to the lumen, while establishing communication between the communication circuit of the drug source device and the communication circuit of the smart device, and wherein 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 disconnection from the lumen.

[0014] In some non-limiting embodiments or aspects, the communication circuitry of another drug source device is configured to establish communication with the communication circuitry of another smart device based on user input to a user input component of the other drug source device and user input to a user input component of the other smart device, and one or more processors are further programmed and / or configured to: control the visual indicator of the other smart device and the visual indicator of the other drug source device to produce another visual output of the same type, wherein the other visual output of the same type is different from the visual output of the same type; associate the other visual output of the same type with another lumen among a plurality of lumens, wherein the other drug source device is connected to the other lumen; obtain drug data associated with a third type of drug delivered or planned to be delivered to a patient via the other lumen; and determine, based on the drug data, the compatibility of a second type of drug with delivery via the same other lumen as the third type of drug, wherein the indicator also indicates whether the second type of drug is compatible with delivery via the other other lumen associated with the other visual output of the same type.

[0015] According to some non-limiting embodiments or aspects, a method is provided, comprising: connecting a plurality of smart devices to a plurality of lumens, wherein each smart device includes 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, wherein each drug source device includes a visual indicator, a communication circuit, and a user input component; receiving user input via the user input component of the smart devices; receiving user input via the user input component of the drug source devices; establishing communication between the smart devices and 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, using the communication circuits of the smart devices and the communication circuits of the drug source devices; and controlling the visual indicator of the smart devices and the visual indicator of the drug source devices using at least one processor. The device generates the same type of visual output based on communication established between a drug source device and a smart device; associates the same type of visual output with the same lumen among a plurality of lumens using at least one processor, wherein the drug source device is connected to the same lumen; obtains drug data associated with a first type of drug delivered or planned to be delivered to a patient via the same lumen and a second type of drug delivered or planned to be delivered to a patient via the same lumen using at least one processor, wherein the first type of drug is different from the second type of drug; determines, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug using at least one processor; and provides an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output using at least one processor.

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

[0017] In some non-limiting embodiments or aspects, the light-emitting diode is configured to emit a variety of different colors of light, and the method further includes: using at least one processor to determine the color of light to be produced by the visual indicator of the smart device and the visual indicator of the drug source device of the same color, based on at least one of user input received by the user input component of the drug source device and user input received by the user input component of the smart device.

[0018] In some non-limiting embodiments or aspects, the light-emitting diode is configured to emit a variety of different colors of light, and the method further includes: using at least one processor to determine light of the same color for a visual indicator of a smart device and a visual indicator of a drug source device to produce light of a different color from light of each other color produced by each visual indicator of each of the other smart devices and each visual indicator of each of the other drug source devices.

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

[0020] In some non-limiting embodiments or aspects, the method further includes: delivering a first type of drug to a patient via the same lumen associated with the same type of visual output, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein providing an indication of whether delivery of the second type of drug via the same lumen associated with the same type of visual output is compatible further includes: controlling a 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 drug to a patient using the same lumen associated with the same type of visual output, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to use a different lumen associated with a different type of visual output rather than the same type of visual output to deliver the second type of drug to the patient.

[0022] In some non-limiting embodiments or aspects, the method further includes: delivering a first type of drug and a second type of drug to a patient via the same lumen associated with the same type of visual output, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to treat the same lumen associated with the same type of visual output for either thromboembolism or chemical occlusion.

[0023] In some non-limiting embodiments or aspects, the method further includes: in response to being connected to the lumen, generating visual output of the same type as that of the visual indicator of the drug source device using a visual indicator of the smart device, while establishing communication between the drug source device and the smart device; and in response to being disconnected from the lumen, automatically stopping the generation of visual output of the same type as that of the visual indicator of the drug source device using a visual indicator of the smart device.

[0024] In some non-limiting embodiments or aspects, the method further includes: receiving user input by a user input component of another smart device; receiving user input by a user input component of another drug source device; establishing communication between the other drug source device and 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 component of the other smart device, using the communication circuitry of the other drug source device and the communication circuitry of the other smart device; and controlling the visual indicator of the other smart device and the visual indicator of the other drug source device to generate another visual indicator of the same type, using at least one processor, based on the communication established between the other drug source device and the other smart device. Visual output, wherein another visual output of the same type is different from the visual output of the same type; using at least one processor to associate another visual output of the same type with another lumen of the same type among a plurality of lumens, wherein another drug source device is connected to the other lumen of the same type; using at least one processor to obtain drug data associated with a third type of drug delivered or planned to be delivered to a patient via the other lumen of the same type; and using at least one processor, based on the drug data, to determine the compatibility of a second type of drug with delivery via the other lumen of the same type as the third type of drug, wherein the indication also indicates whether the second type of drug is compatible with delivery via the other lumen of the same type associated with the visual output of the same type.

[0025] According to some 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 produce the same type of visual output based on communication established between communication circuitry of a drug source device and communication circuitry of a smart device, wherein the drug source device is connected to a lumen, and wherein the smart device is 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 planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen, wherein the first type of drug is different from the second type of drug; determine, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0026] According to some non-limiting embodiments or aspects, a computer-implemented method is provided, comprising: controlling a visual indicator of a smart device and a visual indicator of a drug source device using at least one processor 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, wherein the drug source device is connected to a lumen, and wherein the smart device is configured to be connected to the lumen; associating the same type of visual output with the lumen using at least one processor; obtaining drug data associated with a first type of drug delivered or planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen using at least one processor, wherein the first type of drug is different from the second type of drug; determining, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug using at least one processor; and providing an indication, using at least one processor, whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0027] According to some non-limiting embodiments or aspects, a computer program product is provided, comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium including program instructions, which, when executed by at least one processor, cause at least one processor to: control a visual indicator of the smart device and a visual indicator of the drug source device to produce the same type of visual output based on communication established between a communication circuit of a drug source device and a communication circuit of a smart device, wherein the drug source device is connected to a lumen, and wherein the smart device is 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 planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen, wherein the first type of drug is different from the second type of drug; determine, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0028] Further non-limiting embodiments or aspects are set forth in the following numbered clauses:

[0029] Clause 1. A system comprising: a plurality of intelligent devices configured to be connected to a plurality of lumens, wherein each intelligent device includes a visual indicator, communication circuitry, 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, wherein each drug source device includes a visual indicator, communication circuitry, and a user input component configured to receive user input from a user, wherein the communication circuitry of the drug source devices is configured to establish communication with the communication circuitry of the intelligent devices based on user input to the user input component of the drug source devices and user input to the user input component of the intelligent devices; and one or more processors programmed and / or configured to: based on the drug source devices Communication is established between the communication circuit and the communication circuit of the smart device to control the visual indicator of the smart device and the visual indicator of the drug source device to produce the same type of visual output; the same type of visual output is associated with the same lumen among the plurality of lumens, wherein the drug source device is connected to the same lumen; drug data associated with a first type of drug delivered or planned to be delivered to the patient via the same lumen and a second type of drug delivered or planned to be delivered to the patient via the same lumen, wherein the first type of drug is different from the second type of drug; the compatibility of the second type of drug with delivery via the same lumen as the first type of drug is determined based on the drug data; and an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output is provided.

[0030] Clause 2. The system according to Clause 1, wherein the visual indicator of the smart device includes a light-emitting diode, and wherein visual outputs of the same type are light of the same color.

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

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

[0033] Clause 5. The system according to any one of Clauses 1-4, wherein the drug source system includes an infusion pump system, and wherein the plurality of drug source devices include a plurality of infusion pumps.

[0034] Clause 6. A system according to any one of Clauses 1-5, wherein a first type of drug is delivered to a patient via the same lumen, wherein a second type of drug is planned to be delivered to a patient via the same lumen, and wherein said one or more processors are programmed and / or configured to provide an indication of whether the second type of drug is compatible with 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.

[0035] Clause 7. The system of any one of Clauses 1-6, wherein a first type of drug is delivered to the patient via the same lumen, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to use a different lumen associated with a different type of visual output than the same type of visual output to deliver the second type of drug to the patient.

[0036] Clause 8. The system according to any one of Clauses 1-7, wherein the first type of drug and the second type of drug are delivered to the patient via the same lumen associated with the same type of visual output, and wherein the indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to treat the same lumen associated with the same type of visual output for one of thromboembolism and chemical occlusion.

[0037] Clause 9. The system according to any one of Clauses 1-8, wherein the visual indicator of the smart device is configured to generate visual output of the same type as that of the visual indicator of the drug source device in response to connection to the lumen, while establishing communication between the communication circuit of the drug source device and the communication circuit of the smart device, and wherein the visual indicator of the smart device is configured to automatically stop generating visual output of the same type as that of the visual indicator of the drug source device in response to disconnection from the lumen.

[0038] Clause 10. The system according to any one of Clauses 1-9, wherein the communication circuitry of another drug source device is configured to establish communication with the communication circuitry of another intelligent device based on user input to a user input component of the other drug source device and user input to a user input component of the other intelligent device, and wherein one or more processors are further programmed and / or configured to: control the visual indicator of the other intelligent device and the visual indicator of the other drug source device to produce another visual output of the same type, wherein the other visual output of the same type is different from the visual output of the same type; associate the other visual output of the same type with another lumen among a plurality of lumens, wherein the other drug source device is connected to the other lumen; obtain drug data associated with a third type of drug delivered or planned to be delivered to a patient via the other lumen; and determine, based on the drug data, the compatibility of a second type of drug with delivery via the same other lumen as the third type of drug, wherein the indicator also indicates whether the second type of drug is compatible with delivery via the other other lumen associated with the other visual output of the same type.

[0039] Clause 11. A method comprising: connecting a plurality of intelligent devices to a plurality of lumens, wherein each intelligent device includes a visual indicator, communication circuitry, and a user input component; connecting a plurality of drug source devices of a drug source system to the plurality of lumens, wherein each drug source device includes a visual indicator, communication circuitry, and a user input component; receiving user input via the user input component of the intelligent device; receiving user input via the user input component of the drug source device; establishing communication between the intelligent devices and the drug source devices 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 intelligent device, using the communication circuitry of the intelligent devices and the communication circuitry of the drug source devices; controlling the visual indicator of the intelligent devices and the visual indicator of the drug source devices using at least one processor, to based on Communication established between a drug delivery device and a smart device produces the same type of visual output; the same type of visual output is associated with the same lumen among a plurality of lumens using at least one processor, wherein the drug delivery device is connected to the same lumen; drug data associated with a first type of drug delivered or planned to be delivered to a patient via the same lumen and a second type of drug delivered or planned to be delivered to a patient via the same lumen using at least one processor, wherein the first type of drug is different from the second type of drug; the compatibility of the second type of drug with delivery via the same lumen as the first type of drug is determined based on the drug data using at least one processor; and an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output is provided using at least one processor.

[0040] Clause 12. The method according to Clause 11, wherein the visual indicator of the smart device includes a light-emitting diode, and wherein visual outputs of the same type are light of the same color.

[0041] Clause 13. The method according to Clause 11 or 12, wherein the light-emitting diode is configured to emit light of multiple different colors, and wherein the method further comprises: using at least one processor to determine, based on at least one of user input received by a user input component of a drug source device and user input received by a user input component of a smart device, the color of light to be produced by the visual indicator of the smart device and the visual indicator of the drug source device of the same color.

[0042] Clause 14. The method according to any one of Clauses 11-13, wherein the light-emitting diode is configured to emit a plurality of different colors of light, and wherein the method further comprises: using at least one processor to determine light of the same color for a visual indicator of a smart device and a visual indicator of a drug source device to produce light of a different color from light of each other color produced by each visual indicator of each of the plurality of other smart devices and each visual indicator of each of the plurality of other drug source devices.

[0043] Clause 15. The method according to any one of Clauses 11-14, wherein the drug source system includes an infusion pump system, and wherein the plurality of drug source devices include a plurality of infusion pumps.

[0044] Clause 16. The method according to any one of Clauses 11-15 further comprises: delivering a first type of drug to a patient via the same lumen associated with the same type of visual output, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein providing an indication of whether delivery of the second type of drug via the same lumen associated with the same type of visual output further comprises: 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 according to any one of Clauses 11-17 further comprises: delivering a first type of drug to a patient using the same lumen associated with the same type of visual output, wherein a second type of drug is planned to be delivered to the patient via the same lumen, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to use a different lumen associated with a different type of visual output rather than the same type of visual output to deliver the second type of drug to the patient.

[0046] Clause 18. The method according to any one of Clauses 11-17 further comprises: delivering a first type of drug and a second type of drug to a patient via the same lumen associated with the same type of visual output, and wherein an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output includes prompting the user to treat the same lumen associated with the same type of visual output for either thromboembolism or chemical occlusion.

[0047] Clause 19. The method according to any one of Clauses 11-18 further comprises: in response to being connected to the lumen, generating visual output of the same type as that of the visual indicator of the drug source device using a visual indicator of the smart device, while establishing communication between the drug source device and the smart device; and in response to being disconnected from the lumen, automatically stopping the generation of visual output of the same type as that of the visual indicator of the drug source device using a visual indicator of the smart device.

[0048] Clause 20. The method according to any one of Clauses 11-20 further includes: receiving user input by a user input component of another smart device; receiving user input by a user input component of another drug source device; establishing communication between the other drug source device and 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, using the communication circuit of the other drug source device and the communication circuit of the other smart device; and controlling the visual indicator of the other smart device and the visual indicator of the other drug source device to generate another of the same type of [something] based on the communication established between the other drug source device and the other smart device, using at least one processor. The visual output of the same type, wherein another visual output of the same type is different from the visual output of the same type; using at least one processor to associate another visual output of the same type with another lumen of the same type among a plurality of lumens, wherein another drug source device is connected to the other lumen of the same type; using at least one processor to obtain drug data associated with a third type of drug delivered or planned to be delivered to a patient via the other lumen of the same type; and using at least one processor, based on the drug data, to determine the compatibility of a second type of drug with delivery via the other lumen of the same type as the third type of drug, wherein the indication also indicates whether the second type of drug is compatible with delivery via the other lumen of the same type associated with the visual output of the same type.

[0049] Clause 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 produce the same type of visual output based on communication established between communication circuitry of a drug source device and communication circuitry of a smart device, wherein the drug source device is connected to a lumen, and wherein the smart device is 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 planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen, wherein the first type of drug is different from the second type of drug; determine, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0050] Clause 22. A computer-implemented method comprising: controlling, using at least one processor, a visual indicator of a smart device and a visual indicator of a 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, wherein the drug source device is connected to a lumen, and wherein the smart device is configured to be connected to the lumen; associating the same type of visual output with the lumen using at least one processor; obtaining, using at least one processor, drug data associated with a first type of drug delivered or planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen, wherein the first type of drug is different from the second type of drug; determining, using at least one processor, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug based on the drug data; and providing, using at least one processor, an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0051] Clause 23. A computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising program instructions, which, when executed by at least one processor, cause at least one processor to: control a visual indicator of the intelligent device and a visual indicator of the drug source device to produce the same type of visual output based on communication established between a communication circuit of a drug source device and a communication circuit of an intelligent device, wherein the drug source device is connected to a lumen, and wherein the intelligent device is 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 planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to a patient via the lumen, wherein the first type of drug is different from the second type of drug; determine, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and provide an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output. Attached Figure Description

[0052] Figure 1 The figures are non-limiting embodiments or aspects of the environment in which the systems, devices, products, apparatuses and / or methods described herein can be implemented;

[0053] Figure 2A-2C yes Figure 1 A diagram of a non-limiting embodiment or aspect of an implementation of one or more systems and / or one or more devices;

[0054] Figure 3 yes Figure 1 and 2A-Illustrations of non-limiting embodiments or aspects of components of one or more devices and / or one or more systems of -2C;

[0055] Figure 4A This is a side view of a non-limiting embodiment or aspect of a pinless connector implementation;

[0056] Figure 4B It is a side view of a non-limiting embodiment or aspect of the implementation of smart devices and pinless connectors;

[0057] Figure 4C It is a side view of a non-limiting embodiment or aspect of the implementation of smart devices and pinless connectors;

[0058] Figure 5A This is a perspective view of a non-limiting embodiment or aspect of the implementation of smart devices and pinless connectors;

[0059] Figure 5B This is a top view of a non-limiting embodiment or aspect of the implementation of smart devices and pinless connectors;

[0060] Figure 5C It is a graph of a non-limiting embodiment or aspect of the force signal changing over time;

[0061] Figure 6A and 6B It shows Figure 1 Non-limiting embodiments or aspects of the output of one or more systems and / or one or more devices;

[0062] Figure 7 The illustration is a non-limiting embodiment or aspect of an intelligent device for detecting extravasation and / or infiltration of drugs in a catheter;

[0063] Figure 8 A flowchart of a non-limiting embodiment or aspect of a process for identifying a lumen;

[0064] Figure 9 A flowchart of a non-limiting embodiment or aspect of a process for identifying a lumen;

[0065] Figure 10 A flowchart of a non-limiting embodiment or aspect of the process for positioning the needle tip; and

[0066] Figure 11 It is a flowchart of a non-limiting embodiment or aspect of a process for event monitoring. Detailed Implementation

[0067] It should be understood that various alternative variations and sequences of steps may be taken in this disclosure unless expressly specified to the contrary. It should also be understood that the specific apparatus and methods shown in the accompanying drawings and described in the following specification are merely exemplary and not limiting embodiments or aspects. Therefore, specific dimensions and other physical characteristics relating to the embodiments or aspects disclosed herein should not be considered limiting.

[0068] For the purposes described below, the terms “end,” “upper,” “lower,” “right,” “left,” “vertical,” “horizontal,” “top,” “bottom,” “lateral,” “longitudinal,” and their derivatives shall refer to the embodiments or aspects oriented as shown in the accompanying drawings. However, it should be understood that various alternative variations and sequences of steps may be taken in the embodiments or aspects unless expressly specified to the contrary. It should also be understood that the specific apparatus and processes shown in the accompanying drawings and described in the following specification are merely non-limiting exemplary embodiments or aspects. Therefore, unless otherwise indicated, the specific dimensions and other physical characteristics associated with the embodiments or aspects disclosed herein should not be considered limiting.

[0069] Unless explicitly stated otherwise, aspects, components, elements, structures, actions, steps, functions, instructions, etc., as used herein should not be construed as critical or necessary. Furthermore, as used herein, the article “a” is intended to include one or more items and is interchangeable with “one or more” and “at least one.” Additionally, as used herein, the term “group” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and is interchangeable with “one or more” or “at least one.” The term “a” or similar language is used where only one item is referred to. Furthermore, as used herein, the terms “having” and the like are intended to be open-ended terms. Additionally, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.”

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

[0071] As used herein, the term "computing device" can refer to one or more electronic devices configured to communicate directly or indirectly with or through one or more networks. A computing device can be a mobile or portable computing device, a desktop computer, a server, etc. Furthermore, the term "computer" can refer to any computing device that includes the necessary components for receiving, processing, and outputting data, and typically includes a display, processor, memory, input devices, and network interfaces. A "computing system" can include one or more computing devices or computers. An "application" or "application programming interface" (API) refers to computer code or other data categorized on a computer-readable medium that can be executed by a processor to facilitate interaction between software components, such as client-side front-ends and / or server-side back-ends for receiving data from clients. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUIs) with which a user can interact directly or indirectly (e.g., via a keyboard, mouse, touchscreen, etc.). Furthermore, multiple computers, such as servers or other computerized devices, communicating directly or indirectly in a networked environment can constitute a "system" or "computing system."

[0072] Clearly, the systems and / or methods described herein can be implemented in various forms, including hardware, software, or a combination of both. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these implementations. Therefore, the operation and behavior of the systems and / or methods described herein do not refer to any specific software code, and it should be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0073] This document describes some non-limiting embodiments or aspects in conjunction with thresholds. As used herein, satisfying a threshold can mean a value greater than a threshold, more than a threshold, higher than a threshold, greater than or equal to a threshold, less than a threshold, lower than a threshold, less than or equal to a threshold, equal to a threshold, etc.

[0074] Improved systems, apparatuses, products, devices, and / or methods for identifying lumens are provided. Existing systems for lumen identification may use tape, labels, handwritten nodes, and / or LED lights to identify lumens. However, existing systems for lumen identification may not automatically associate the identified lumen with a fluid pump or fluid source connected to the identified lumen and / or with drug data associated with one or more drugs delivered and / or planned to be delivered via the identified lumen. Thus, existing systems for lumen identification lack mechanisms for automatically determining the compatibility of drugs delivered and / or planned to be delivered via the same lumen and / or for inhibiting or preventing the delivery of incompatible drugs via the same lumen. Therefore, existing systems for lumen identification may be insufficient to reduce or eliminate IV line complexity and / or drug delivery errors and / or insufficient to improve compliance with lumen maintenance procedures (e.g., line flushing, etc.).

[0075] Non-limiting embodiments or aspects of this disclosure relate to systems, devices, products, apparatuses, and / or methods for automatically associating an identified lumen with a fluid pump or fluid source connected to the identified lumen and / or with drug data associated with one or more drugs delivered and / or planned to be delivered via the identified lumen. For example, the method may include controlling a visual indicator of a smart device and a visual indicator of a 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 being connected to the lumen, and the smart device being configured to be connected to the lumen; associating the same type of visual output with the lumen; obtaining drug data associated with a first type of drug delivered or planned to be delivered to a patient via the lumen and a second type of drug delivered or planned to be delivered to the patient via the lumen, the first type of drug being different from the second type of drug; determining, based on the drug data, the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and providing an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

[0076] Thus, non-limiting embodiments or aspects of this disclosure provide for the automatic determination of the compatibility of drugs delivered and / or planned to be delivered via the same lumen and / or the inhibition or prevention of delivery of incompatible drugs via the same lumen, which can achieve reduced or eliminated IV line complexity and / or drug delivery errors and / or improved compliance of lumen maintenance procedures (e.g., line flushing, etc.).

[0077] Now for reference Figure 1 , Figure 1 This is a diagram of an example environment 100 in which the devices, systems, methods, and / or products described herein can be implemented. For example... Figure 1 As shown, 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 environment 100 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0078] In some non-limiting embodiments or aspects, the drug delivery system 102 includes one or more means capable of delivering one or more fluids to one or more lumens (e.g., fluid lines, IV lines, etc.). For example, the drug delivery 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.).

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

[0080] The following reference Figure 2A , 2C Further details regarding non-limiting embodiments or aspects of the drug source system 102 are provided in sections 3 and 4.

[0081] In some non-limiting embodiments or aspects, the smart device 104 includes one or more devices capable of receiving information and / or data from 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, and / or transmitting 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 including one or more processors (e.g., one or more computing devices, one or more mobile computing devices, etc.). In some non-limiting embodiments or aspects, the smart device 104 is 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, etc.), from the terminal / mobile computing system 110, from one or more other smart devices 104, etc.) via short-range wireless communication connections (e.g., NFC communication connections, RFID communication connections, Bluetooth communication connections, etc.), and / or transmitting information via short-range wireless communication connections (e.g., to the drug source system 102 (e.g., to the drug source controller 204 and / or to the drug source device 206, etc.), to the terminal / mobile computing system 110, to one or more other smart devices 104, etc.).

[0082] In some non-limiting embodiments or aspects, such as Figure 6B As shown, the smart device 104 can provide direct patient-side feedback (e.g., via an LED light to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 has not been washed within a predetermined time period and / or before predetermined use, (ii) detecting that the needleless connector 214 and / or its lumen 212 has not been washed for a sufficient period of time before entering the catheter line, (iii) detecting that the flushing of the needleless connector 214 and / or lumen 212 has expired, (iv) detecting that the sterilization cap has not been attached after the previous entry of the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include the needleless connector 214, and the needleless connector 214 may be configured to detect at least one of a washing event, a flushing event, a connection or capping event, or any combination thereof. As an example, the pinless connector 214 can be configured (e.g., utilizing processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to provide information and / or data associated with detected washing events, detected rinsing events, and / or detected connection or capping events, to store events and report compliance performance for compliance event monitoring.

[0083] The following reference Figure 2A-2CDocuments 3, 4A-4C, 5A-5C, 6A, 6B, and 7 provide further details regarding non-limiting embodiments or aspects of the smart device 104.

[0084] In some non-limiting embodiments or aspects, communication network 106 includes one or more wired and / or wireless networks. For example, communication network 106 includes cellular networks (e.g., Long Term Evolution (LTE) networks, third-generation (3G) networks, fourth-generation (4G) networks, Code Division Multiple Access (CDMA) networks, etc.), Public Land Mobile Networks (PLMN), Local Area Networks (LAN), Wide Area Networks (WAN), Metropolitan Area Networks (MAN), telephone networks (e.g., Public Switched Telephone Network (PSTN)), private networks, ad hoc networks, intranets, the Internet, fiber-optic networks, cloud computing networks, etc., and / or any combination of these or other types of networks.

[0085] 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 the drug source system 102, the smart device 104, the communication network 106, and / or the terminal / mobile computing system 110, and / or transmitting 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, which include one or more processors (e.g., one or more computing devices, one or more mobile computing devices, etc.). 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 storing personally identifiable information (PII) and / or information protected by the Health Insurance Portability and Accountability Act (HIPAA).

[0086] 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 the drug source system 102, the smart device 104, the communication network 106, and / or the central computing system 108, and / or transmitting 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, which include one or more processors (e.g., one or more computing devices, one or more mobile computing devices, etc.). In some non-limiting embodiments or aspects, the terminal / mobile computing system 110 includes a nurse station in a hospital. For example, as... Figure 6AAs shown in implementation 600A, the terminal / mobile computing system 110 can provide bedside nurse support (e.g., real-time recording of each access to the needleless connector 214 and / or lumen 212, and feedback to the nurse if it is determined that it is due or requires washing or rinsing based on the recorded accesses, etc.), nursing station manager support (e.g., optimizing rinsing procedures to reduce the workflow of rinsing the needleless connector 214 and / or lumen 212 and improve timing targets, etc.), retrospective reporting of nursing management (e.g., washing duration, rinsing technique, time between rinsings, etc. for the needleless connector 214 and / or lumen 212), etc.

[0087] Now for reference Figure 2A-2C , Figure 2A-2C yes Figure 1 A diagram illustrating a non-limiting embodiment or aspect of one or more systems and / or one or more devices. (See diagram for reference.) Figure 2A and 2C As shown, 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 BD Alaris. TM System. For example, drug source system 102 may include BD Alaris TM PC unit and one or more BD Alaris TM Pump module. As another example, drug source controller 204 may include a bedside console or computing device that may be detached from the infusion pump system, and / or drug source device 206 that may be detached from the infusion pump and may be associated with and / or connected to a drug source (e.g., an IV bag, syringe, one end of an IV line connected to and near the IV bag or syringe, etc.).

[0088] like Figure 2A As shown, multiple drug source devices 206a, 206b, ... 206n can be connected to multiple lumens (e.g., fluid lines, etc.) 202a, 202b, ... 202n (e.g., for receiving fluid and / or drugs at drug source system 102) and / or multiple lumens (e.g., fluid lines, etc.) 212a, 212b, ... 212n (e.g., for delivering fluid and / or drugs from drug source system 102). Figure 2C As shown, the drug source device 206 may include a paired input 208 (e.g., a button, input component 310, etc.) and / or a visual indicator 210 (e.g., one or more multi-color LEDs, output component 312, etc.). Figure 2A and 2BAs shown, multiple cavities 212a, 212b, ... 212n can be connected to multiple smart devices 104a, 104b, ... 104n.

[0089] However, non-limiting embodiments or aspects are not limited thereto, and the patient may be connected to only a single lumen, and the lumen may (or may not) be connected to any drug source device 206 and / or fluid source. For example, if the patient is connected to a single lumen, the smart device 104 may be connected to that single lumen, and the smart device 104 may be associated with a specific color associated with that lumen. The doctor and / or pharmacy may issue an order for the type of medication to be delivered to the patient, and the order for the type of medication may associate the color of the lumen with the order to reduce or avoid medication delivery errors. As an example, a first patient may have a “pink” LED light lit on the smart device 104, and an order from the doctor and / or pharmacy that includes a new type of medication or treatment to be delivered and instructions for the user (e.g., a nurse, etc.) to deliver the new type of medication on a single “pink” line to implement an error-checking process. When the user (e.g., a nurse, etc.) begins delivering medication to the patient, the user can ensure that the smart device 104 emits pink for an additional security check to ensure that the user has the correct patient with the correct type of medication. If the smart device 104 emits a color different from the "pink" light (e.g., "green" or "blue"), and the medication order instructs that the medication should be delivered only through the "pink" colored lumen, the user (e.g., a nurse, etc.) can begin delivery to the patient (e.g., not delivering the medication, etc.) because the user can determine that the order and color mismatch indicate a potential problem and / or incompatibility with the medication for the patient and / or the lumen. For example, if the patient is connected to a single lumen, the order might instruct the delivery of a given saline solution on the "pink" line as well as antibiotics, etc., on the same "pink" line. However, if a medication incompatibility order exists, the order could change the user's instructions to perform additional flushing of the "pink" line to ensure that the pink line is properly flushed before delivery of subsequent medications that may be incompatible with medications or fluids previously delivered via the "pink" line. As an example, if two lumens are connected to a single patient (e.g., a single "pink" line and a single "blue" line), an order may instruct the delivery of saline via the "pink" lumen or line, and the delivery of antibiotics via the "blue" lumen or line, and so on. Therefore, in some non-limiting embodiments or aspects, the smart device 104 can simply be used for correct patient lumen identification and / or guiding the user to use the optimal lumen to deliver fluid to the patient. This ensures that the correct treatment is delivered to the optimal or correct lumen, thereby reducing situations associated with incorrect dosing, incorrect patients, incorrect lumens, etc., related to the smart device 104.

[0090] In some non-limiting embodiments or aspects, the smart device 104 is configured to be removably connected to a portion of the needleless connector 214 and / or lumen 212 near 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.) and / or the like. 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 lumen 212 near the needleless connector 214. As an example, such as Figure 2A and 2B As shown, smart device 104a can be connected to needleless connector 214 and / or a catheter lumen connecting a catheter to lumen 212b, and / or smart device 104n can be connected to needleless connector 214 and / or a catheter lumen connecting a catheter to lumen 212a. In some non-limiting embodiments or aspects, smart device 104 includes needleless connector 214. For example, smart device 104 can be integrated with needleless connector 214 (e.g., within needleless connector 214 of a fluid intrusion device and / or within a catheter hub of a needleless connector, etc.). As an example, such as Figure 2A and 2B As shown, the smart device 104b may include a needleless connector 214 and / or a catheter hub that connects the catheter lumen to the lumen 212n via a Y-part connector. In such an example, the smart device 104 may include the needleless connector 214, which includes a housing 402 of the needleless connector 214 within a housing 250 (e.g., integrated with the housing 250, contained within the housing 250, etc.).

[0091] Also refer to Figure 4A , Figure 4A This is a side view of a non-limiting embodiment or aspect of a pinless connector 214 implementation 400A. (See attached image.) Figure 4A As shown, the needleless connector 214 may include a fluid flow path within the housing 402 between an inlet 404 and an outlet 406 opposite to the inlet 404. The inlet 404 may be fluid-sealed by a movable diaphragm 408 configured to displace in response to connection of the needleless connector 214 to a medical device (e.g., an infusion pump, IV bag, syringe, IV line, etc.) to open the inlet 404 or connect the inlet to the fluid flow path. For example, the needleless connector 214 may include a BD MaxPlus... TM Connector, BDMaxZero TMPinless connectors, etc. However, non-limiting embodiments or aspects are not limited thereto, and the pinless connector 214 may include any pinless connector 214 for use in fluid application. 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 pinless connector 214. For example, the housing 402 of the pinless 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.).

[0092] like Figure 2C As shown, the smart device 104 may include a visual indicator 252 (e.g., one or more visual indicators, multiple visual indicators, one or more multi-color LEDs, multiple LEDs, output component 312, etc.), a sensor 254 (e.g., one or more sensors, multiple sensors, 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 part of the visual indicator 252, sensor 254, pairing input 256, battery 258, energy harvester 260, and pinless connector 214 may be included within the housing 250 of the smart device 104. The visual indicator 252 may be visible through and / or extend from the sidewall of the housing 250. Battery 258 and / or energy harvester 260 can provide power for the components of smart device 104, such as visual indicator 252, sensor 254, pairing input 256, rechargeable battery of battery 258, one or more components of device 300 included in smart device 104, etc.

[0093] In some non-limiting embodiments or aspects, the smart device 104 may include a label (e.g., a human-readable label, etc.) representing a visual indicator 252 of the smart device 104. For example, as Figure 4C As shown in implementation 400C, the smart device 104 may include labels associated with visual indicators 252 (e.g., on the sidewall of housing 250, etc.) that characterize each visual indicator 252 as being configured to provide indications associated with a specific event, such as one of the following: a washing event in which the needleless connector 214 is washed with a disinfectant (e.g., label “SCRUB”, etc.); a rinsing event in which the needleless connector 214 is rinsed with a solution (e.g., label “FLUSH”, etc.); a connection or capping event in which the needleless connector 214 is connected to a medical device (e.g., label “CAP”, etc.); and / or similar. In some non-limiting embodiments or aspects, the smart device 104 may include a single visual indicator 252 (e.g., as shown in the image). Figure 4B(As shown in implementation 400B). For example, the smart device 104 can control a single visual indicator 252 to emit light in a specific color and / or a specific pattern to provide indication or prompt to the user, such as emitting continuous green in response to sensing that washing of the pinless connector 214 has occurred for a predetermined period of time (e.g., 15 seconds, etc.), emitting pulsating green in response to sensing that an appropriate pulsating rinse has occurred, emitting pulsating red in response to determining that a pulsating rinse of the pinless connector 214 has not occurred for a predetermined period of time (e.g., 88 hours, etc.), and emitting continuous red in response to determining that the pinless connector 214 has not been sealed by the sterilization cap for a predetermined period of time (e.g., more than a few minutes, etc.).

[0094] 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 user input to the pairing input 208 of the drug source device 206 and user input to the pairing input 256 of the smart device 104. For example, the drug source device 206 can establish a short-range wireless communication connection (e.g., NFC communication connection, RFID communication connection, etc.) with the smart device 104. (Communication connection, etc.). As an example, the visual indicator 210 may be configured to emit a predetermined light pattern (e.g., rapidly flashing 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., pairing and / or activating a pairing sequence for pairing the smart device 104 with the drug source device 206, 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.) while the drug source device 206 is in pairing mode.

[0095] 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., light of the same color from a multicolor LED, light of the same pattern, etc.). For example, refer again... Figure 2ADrug source device 206a can be paired with smart device 104n, and each of drug source device 206a and smart device 104n can output light of a first color (e.g., red light). Drug source device 206b can be paired with smart device 104a, and each of drug source device 206b and smart device 104a can output light of a second color (e.g., green light). Drug source device 206n can be paired with smart device 104b, and each of drug source device 206n and smart device 104b can output light of a third color (e.g., blue light), and so on.

[0096] In some non-limiting embodiments or aspects, sensor 254 includes at least one of the following: one or more force sensors (e.g., one or more piezoelectric elements or transducers, one or more force-sensitive resistor (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., optical sensors configured to detect at least one of color signature and reflectivity of a medical device connected to smart device 104, etc.); one or more identification sensors (e.g., identification sensors configured to detect identification tags connected to or being connected to a medical device connected to or being connected to the pinless connector 214, such as magnetometers configured to detect magnetic materials, barcode scanners configured to read barcodes, etc.); one or more position sensors (e.g., position sensors configured to detect movement of smart device 104, etc.); one or more RGB color sensors; or any combination thereof.

[0097] Figure 1 and 2A The number and arrangement of systems, devices, and networks shown in -2C are provided as examples. More may exist than... Figure 1 and 2A -2C represents systems, devices, and / or networks with more systems, devices, and / or networks, fewer systems, devices, and / or networks, different systems, devices, and / or networks, or systems, devices, and / or networks with different arrangements. Furthermore, Figure 1 and 2A The two or more systems or devices shown in -C can be implemented in a single system or a single device, or Figure 1 and 2A The single system or single device shown in -2C can be implemented as multiple distributed systems or devices. Alternatively, a group of systems or a group of devices (e.g., one or more systems, one or more devices, etc.) of environment 100 and / or implementation 200 can perform one or more functions described as being performed by another group of systems or another group of devices of environment 100 and / or implementation 200.

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

[0099] Bus 302 may include components that allow communication between components of device 300. In some non-limiting embodiments or aspects, processor 304 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 304 may include a processor (e.g., a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), etc.), microprocessor, digital signal processor (DSP), and / or any processing component capable of being programmed to perform functions (e.g., a field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), microcontroller (MCU), etc.). Memory 306 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, optical storage, etc.) that stores information and / or instructions for use by processor 304.

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

[0101] Input component 310 may include components that allow device 300 to receive information, such as via user input (e.g., touchscreen display, keyboard, keypad, mouse, button, switch, microphone, camera, EEG monitor, etc.). Alternatively, input component 310 may include sensors for sensing information (e.g., GPS component, accelerometer, gyroscope, actuator, etc.). Output component 312 may include components that provide output information from device 300 (e.g., display, speaker, one or more light-emitting diodes (LEDs) and / or the like).

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

[0103] Device 300 can perform one or more of the processes described herein. Device 300 can execute these processes based on software instructions stored in a computer-readable medium, such as memory 306 and / or storage component 308, executed by processor 304. Computer-readable media (e.g., non-transitory computer-readable media) are defined herein as non-transitory memory devices. Non-transitory memory devices include memory space located within a single physical storage device or memory space distributed across multiple physical storage devices.

[0104] Software instructions may be read into memory 306 and / or storage component 308 via communication interface 314 from another computer-readable medium or from another device. When executed, the software instructions stored in memory 306 and / or storage component 308 may cause processor 304 to perform one or more processes described herein. Alternatively or additionally, hard-wired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Therefore, the embodiments or aspects described herein are not limited to any particular combination of hardware circuitry and software.

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

[0106] Figure 3 The number and arrangement of components shown are provided as examples. In some non-limiting embodiments or aspects, device 300 may include components with... Figure 3 The components shown are additional, fewer, different, or arranged differently compared to other components. 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.

[0107] Figure 5A This is a perspective view of a non-limiting embodiment or aspect of an implementation 500 of a smart device 104 including a pinless connector 214, and Figure 5B This is its top view. Also refer to... Figure 4A The needleless connector 214 may include a fluid flow path within the housing 402 between an inlet 404 and an outlet 406 opposite to the inlet 404. The inlet 404 may be fluid-sealed by a movable diaphragm 408 configured to displace in response to connection of the needleless connector 214 to a medical device (e.g., an infusion pump, IV bag, syringe, IV line, etc.) to open the inlet 404 or connect the inlet to the fluid flow path. (See again) Figure 5A and 5BIn 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 the following may be determined based on the force signal (e.g., by the smart device 104, etc.): a washing event of washing the needleless connector with a disinfectant, a rinsing event of washing the needleless connector with a solution, a connection event of connecting the needleless connector to a medical device, or any combination thereof. In such an example, a pattern of events including at least one of the following may be determined based on the force signal: a washing event of washing the needleless connector with a disinfectant, a rinsing event of rinsing the needleless connector with a solution, a connection event of connecting the needleless connector to a medical device, the time between one or more detected events, or any combination thereof, and a drug administration event of administering medication to a patient via the needleless connector 214 may be determined based on the pattern of the events. As an example, standard medical practice may assume a wash-rinse-wash-drug administration-wash-rinse-wash pattern or event sequence, and therefore, the detection of the three accesses of the Luer connector can be interpreted by the smart device 104 as a drug administration event. For example, Figure 5C This is a graph 550 showing a non-limiting embodiment or aspect of force measurement or signal variation over time. (e.g.) Figure 5C As shown, pulsating flushing can be determined or detected by force measurement. For example, when flushing is achieved by intermittent pressure pulses applied to the plunger of the flushing syringe, the smart device 104 can detect the occurrence of pulsating flushing by recognizing a periodic force signal between x and y Hz in the force signal perpendicular to the surface of the diaphragm 408 of the needleless connector 214. For example, the smart device 104 can determine a flushing event based on a force signal indicating a periodic force in a second direction perpendicular to the surface of the diaphragm facing the first direction, and the flushing event includes a pulsating flushing event.

[0108] In some non-limiting embodiments or aspects, the smart device 104 may include communication circuitry configured to transmit force signals 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 force signals from the smart device 104 and / or the needleless connector 214, and process the force signals to determine at least one of the following: a washing event of washing the needleless connector with a disinfectant, a rinsing event of rinsing the needleless connector with a solution, a connection event of the needleless connector being connected to a medical device, or any combination thereof.

[0109] In some non-limiting embodiments or aspects, the force sensor 502 includes at least one of the following: a piezoelectric element, a force-sensitive resistor (FSR) sensor, a strain gauge, or any combination thereof. In some non-limiting embodiments or aspects, the force sensor 502 is positioned between the outer surface of the inner wall 510 of the pinless connector 214 (e.g., a harder plastic inner wall) defining a fluid flow path for the pinless connector 214 and the inner surface of the outer wall 512 of the pinless connector 214 surrounding the inner wall 510 (e.g., a softer, more flexible, more resilient, rubber, or other wall). In some non-limiting embodiments or aspects, the region between the outer surface of the inner wall 510 of the needleless connector 214 (e.g., a harder inner plastic wall) defining the fluid flow path of the needleless connector 214 and the inner surface of the outer wall 512 of the needleless connector 214 surrounding the inner wall 510 (e.g., a softer, more flexible, more numerous, more resilient, rubber, etc. wall) (which may be retained by the user during cleaning and / or connection to other medical devices) may be filled with a rubber or other flexible type of material 514, including a force sensor 502 as a force-sensing membrane within 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 and / or near the threads of the inlet 404 of the needleless connector 214.

[0110] In some non-limiting embodiments or aspects, force sensor 502 includes a plurality of force sensors 502 positioned around the fluid flow path of the pinless connector 214 between an outer surface of an inner wall 510 defining a fluid flow path of the pinless connector 214 and an inner surface of an outer wall 512 surrounding the inner wall 510 of the pinless connector 214. For example, the inlet 404 of the pinless connector 214 may include a diaphragm 408 having a surface facing a first direction, and force sensor 502 may be configured to detect a force in a second direction perpendicular to the surface of the diaphragm facing the first direction. As an example, a flushing event, which may include a pulsating flushing event, may be determined based on a force signal indicating a periodic force in a second direction perpendicular to the surface of the diaphragm facing the first direction.

[0111] In some non-limiting embodiments or aspects, sensor 254 includes a pressure sensor, and the pressure sensor is one of the following: in direct contact with fluid in the fluid flow path of the needleless connector; located within the inner wall defining the fluid flow path of the needleless connector; and located within the lumen wall connected to the needleless connector. For example, smart device 104 can determine or detect pulsating flushing, rinsing, and / or drug administration by means of a pressure sensor in contact with the fluid path and / or lumen in needleless connector 214.

[0112] In some non-limiting embodiments or aspects, sensor 254 includes an optical sensor configured to detect at least one of a color signature and reflectivity of a medical device connected to and / or being connected to the needleless connector 214, and smart device 104 can determine the type of medical device based on at least one of the color signature and reflectivity of the medical device. For example, the color signature and / or reflectivity of the medical device can indicate a syringe, IV bag, infusion pump, and / or a specific type thereof.

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

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

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

[0116] In some non-limiting embodiments or aspects, the smart device 104 including the needleless connector 214 may include a visual indicator 252, and the visual indicator 252 may be configured to provide a visual indication associated with at least one of the following: a washing event of washing the needleless connector with a disinfectant, a rinsing event of rinsing the needleless connector with a solution, a connection event of the needleless connector being connected to a medical device, or any combination thereof. For example, as Figure 6BAs shown in implementation 600B, the smart device 104 can provide direct patient-side feedback (e.g., via an LED light to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 has not been washed within a predetermined time period and / or before predetermined use, (ii) detecting that the needleless connector 214 and / or its lumen 212 has not been washed for a sufficient period of time before entering the catheter line, (iii) detecting that the flushing of the needleless connector 214 and / or lumen 212 has expired, (iv) detecting that the sterilization cap has not been attached after the previous entry of the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include the needleless connector 214, and the needleless connector 214 may be configured to detect at least one of a washing event, a flushing event, a connection or capping event, or any combination thereof. As an example, the pinless connector 214 can be configured to provide information and / or data associated with detected washing events, detected rinsing events, and / or detected connection or capping events (e.g., using processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to store events and report compliance performance for compliance event monitoring.

[0117] Figure 7 This is an illustration of a non-limiting embodiment or aspect of a smart device for detecting extravasation or infiltration of drugs in a catheter. (See illustration for example.) Figure 7 As shown, the smart device 104 can be connected to or integrated with the needleless connector 214 at the catheter hub of the catheter 702, the catheter hub including a catheter lumen or line 704 and a needle tip 706 for delivering fluid from the smart device 104 to the patient at opposite ends of the catheter line 704. The catheter 702 can be inserted into a patient's blood vessel (e.g., vein, artery, etc.) or urethra. For example, the location of the needle tip 706 can be within the patient's blood vessel or urethra, within the wall of the patient's blood vessel or urethra, or outside the patient's blood vessel or urethra and the wall of the blood vessel or urethra. In some non-limiting embodiments or aspects, the smart device 104 including the catheter 702 may include a wired and / or wireless transmitter configured (e.g., via wires, wirelessly, etc.) to transmit at least one signal (and / or a change in at least one signal over a period of time, the position of the needle tip relative to the patient's blood vessel or urethra, etc.) to a remote computer system or processing device.

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

[0119] In some non-limiting embodiments or aspects, the smart device 104 may be programmed and / or configured to compare a relatively slow change or variation in the pressure signal over time (e.g., a relatively slow decrease in heart rate amplitude and / or a drop in blood pressure, etc.) with a threshold level to determine an occlusion event rather than an infiltration or extravasation event. For example, an occlusion in the lumen may change the pressure signal sensed by the sensor 254 slowly over time (e.g., compared to an infiltration event, extravasation event, disconnection event, etc.). As an example, the smart device 104 may determine an occlusion event and, in response to detecting an occlusion event, provide alterations and / or automatic flushing of the lumen associated with the occlusion. In some non-limiting embodiments, the smart device 104 may detect a disconnection event in response to the sensor 254 detecting a pressure signal substantially equal to atmospheric pressure, indicating that the connection of the catheter 702, such as the needleless connector 214, is disconnected therefrom, and provide the user with alterations to resolve the connection.

[0120] In some non-limiting embodiments or aspects, the smart device 104 may provide the position of the needle tip relative to the patient's blood vessel or urethra in real time based on pressure signals and / or acoustic signals, thereby providing real-time feedback to the user as the catheter is being inserted into the patient's blood vessel or urethra to indicate whether the catheter is properly placed in the blood vessel or urethra or whether there is a potential or existing infiltration of fluid and a potential or existing extravasation of fluid.

[0121] Now for reference Figure 8 , Figure 8 This is a flowchart 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 steps of process 800 are performed (e.g., fully, partially, etc.) by a drug source system 102 (e.g., one or more devices of drug source system 102, etc.). In some non-limiting embodiments or aspects, one or more steps of process 800 are performed (e.g., fully, partially, etc.) by a device or group of devices including a drug source system, such as a smart device 104 (e.g., one or more devices of a system of smart devices 104, etc.), a central computing system 108 (e.g., one or more devices of central computing system 108, etc.), and / or a terminal / mobile computing system 110 (e.g., one or more devices of terminal / mobile computing system 110, etc.) or separate from it.

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

[0123] Also refer to Figure 2A In some non-limiting embodiments or aspects, a plurality of drug source devices 206a, 206b, ... 206, 206n of the drug source system 102 are connected to a plurality of lumens 212a, 212b, ... 212n, and each drug source device 206 may include a visual indicator 210, communication circuitry (e.g., a communication interface 314, etc.), and a pairing input 208. In some non-limiting embodiments or aspects, the drug source device 206 receives 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., rapidly flashing and / or emitting a predetermined color 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.).

[0124] like Figure 8As shown, in step 804, process 800 includes obtaining user input associated with a smart device. For example, drug source system 102 can obtain user input associated with smart device 104. As an example, drug source system 102 can obtain (e.g., receive, retrieve, determine, etc.) user input received via a user input component of smart device 104 (e.g., pairing input 256, etc.). In such an example, drug source system 102 can receive data associated with user input from smart device 104, which is received while drug source device 206 is in pairing mode.

[0125] Also refer to Figure 2A and 2B In some non-limiting embodiments or aspects, multiple smart devices 104a, 104b, ... 104, 104n may be connected (e.g., removably connected, etc.) or configured to connect to multiple lumens 212a, 212b, ... 212n, and each smart device 104 may include a visual indicator 252, communication circuitry (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., pairing and / or activating / initiating a pairing sequence for pairing the smart device 104 with the drug source device 206, etc.) in response to a predetermined user input to the pairing input 256 of the smart device 104 while the drug source device 206 is in pairing mode.

[0126] like Figure 8 As shown, in step 806, process 800 includes establishing communication between the drug source device and the smart device. For example, drug source system 102 can establish communication between drug source device 206 and smart device 104. As an example, drug source system 102 can establish communication (e.g., NFC communication connection, RFID communication connection, etc.). Communication connections, etc.). Between the drug source device 206 and the smart device 104. In such an example, the communication circuitry of the smart device 104 and the communication circuitry of the drug source device 206 can establish communication (e.g., pairing, etc.) between the smart device 104 and the drug source device 206 based on user input received by the pairing input 208 of the drug source device 206 and user input received by the pairing input 256 of the smart device 104. For example, the drug source device 206 can establish a short-range wireless communication connection with the smart device 104 (e.g., NFC communication connection, RFID communication connection, etc.). (Communication connection, etc.). As an example, the visual indicator 210 may be configured to emit a predetermined light pattern (e.g., rapidly flashing 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., pairing and / or activating a pairing sequence for pairing the smart device 104 with the drug source device 206, 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.) while the drug source device 206 is in pairing mode.

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

[0128] 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., not associated with another drug source device 206 and another smart device 104 paired in the drug source system 102, different from each other color of light produced by each of the other smart devices 104 among the plurality of smart devices 104a, 104b, ... 104n and each of the other 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 in 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 when the smart device 104 is connected to the lumen. For example, the smart device 104 may automatically stop illuminating the visual indicator 252 in the same color as the visual indicator 210 in response to the smart device 104 being disconnected from the lumen (e.g., turning off the LED, setting the LED to the default color indicating an unpaired smart device 104, etc.). As an example, the smart device 104 may include a switch connected to the visual indicator 252, and the switch is configured to be activated / deactivated in response to a clamp or other connection device being connected / disconnected to the lumen and / or its pinless connector 214.

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

[0130] like Figure 8As shown, in step 810, process 800 includes associating visual outputs of the same type with the same lumen. For example, drug delivery system 102 may associate visual outputs of the same type with the same lumen (e.g., automatically associating, etc.). As an example, drug delivery system 102 may associate visual outputs of the same type (e.g., light of the same color, etc.) with the same lumen (e.g., the same lumen among multiple lumens 212a, 212b, ... 212n, etc.) (e.g., storing, pairing, linking, illuminating, etc. in association with them). In such an example, drug delivery device 206 and smart device 104 may be connected to the same lumen. Therefore, users can more easily identify lumens or lines, the location of lumens or lines, drugs that have been or are being delivered via lumens or lines, and which infusion pump or drug source and / or the like are connected to the lumen or line.

[0131] In some non-limiting embodiments or aspects, the drug source system 102 may obtain user input received by a user input component of another drug source device, obtain user input received by a user input component of another smart device, establish communication between the other drug source device and 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, control the visual indicator of the other smart device and the visual indicator of the other drug source device to produce another visual output of the same type based on the communication established between the other drug source device and the other smart device, wherein the other visual output of the same type is different from the same type of visual output, and / or associate the other visual output of the same type with another same lumen among a plurality of lumens, wherein the other drug source device is connected to the other same lumen. For example, refer again Figure 2A Drug source device 206a can be paired with smart device 104n, and each of drug source device 206a and smart device 104n can output light of a first color (e.g., red light) associated with lumen 212a. Drug source device 206b can be paired with smart device 104a, and each of drug source device 206b and smart device 104a can output light of a second color (e.g., green light) associated with lumen 21b. Drug source device 206n can be paired with smart device 104b, and each of drug source device 206n and smart device 104b can output light of a third color (e.g., blue light) associated with lumen 212n, etc.

[0132] like Figure 8 As shown, in step 812, process 800 includes identifying a lumen. For example, drug delivery system 102 can identify a lumen. As an example, drug delivery system 102 can identify the same lumen associated with the same type of visual output.

[0133] In some non-limiting embodiments or aspects, the drug delivery system 102 identifies lumens by automatically associating medical data with visual outputs of the same type and / or lumen identifiers associated with lumens and / or providing medical data. For example, medical data may include at least one of the following: patient data (e.g., identifiers of a specific patient, patient-associated information and / or data, etc.); drug delivery data (e.g., identifiers of a specific drug delivery device 206, etc.); drug data (e.g., identifiers of drug types, planned delivery of a specific drug, previous delivery of a specific drug, lumen associated with the drug, etc.); lumen data (e.g., identifiers of a specific lumen, such as identifiers of the same lumen associated with the same type of visual output, etc.); sensor data (e.g., identifiers of a specific sensor 254, information, data, and / or signals sensed, measured, and / or detected by one or more sensors 254 of one or more smart devices 104, etc.); compliance data (e.g., compliance with washing with disinfectant). Information or data associated with washing events of the needle connector 214 and / or the lumen, information or data associated with flushing events of the needleless connector 214 and / or the lumen with a solution, information or data associated with connection or capping events of the needleless connector 214 or the lumen to a medical device, etc.; location data (e.g., patient location, location of a previous or planned fluid delivery process, location of the lumen, location of the drug source device, etc.); time data (e.g., time associated with a previous or planned fluid delivery process, connection time of the lumen to the drug source device 206, connection time of the smart device 104 to the lumen, pairing time of the drug source device 206 and the smart device 104, etc.); the position of the tip of the needle of the catheter of the lumen relative to the patient's blood vessel or urethra; or any combination thereof. As an example, the drug source system 102 may obtain medical data from a smart device 104, a central computing system 108, a terminal / mobile computing system 110, one or more databases connected to it, and / or one or more sensors connected to it (e.g., a barcode sensor for scanning patient identifiers, a fluid flow sensor for sensing fluid flow, a drug type sensor for sensing the type of drug, etc.).In such an example, the drug delivery system 102 can identify lumens using associated information and / or data, and provide visual indications of which lumens among multiple lumens 212a, 212b, ... 212n are connected to which drug delivery devices among multiple drug delivery devices 206a, 206b, ... 206n. This allows users to more easily track the lumen from the patient to the specific drug delivery device to which the lumen is connected; if the patient is moved (e.g., to a new room, a new floor, to surgery, to a bathroom, etc.), the connection between the lumen and the drug delivery device is removed, and the lumen / drug delivery device pair has the same type of visual indicator for easier reattachment of the correct drug delivery device channel to the correct (e.g., the same as before) lumen; for example, tracking compliance with best practice protocols by determining whether hub washing has occurred and whether hub washing has occurred effectively (e.g., sufficient pressure, sufficient time washing, etc.) and / or whether the device has been flushed, maintained, etc.; providing reminders and guidance on protocol compliance, etc.

[0134] In some non-limiting embodiments or aspects, the drug delivery system 102 identifies a lumen by determining and providing one or more alarms or alerts associated with the lumen based on medical data and / or the same type of visual output associated with the lumen, such as alerts to flush the lumen and / or its needleless connector 214, alerts to remove or replace the lumen, medically excavated infection prevention instructions, alerts to use different lumens to deliver specific drugs to reduce the chance of chemical occlusion, alerts indicating whether the lumen is being treated for thromboocclusion or chemical occlusion, alerts to the detection of occlusion within the lumen, alerts to the location of the needle tip connected to the lumen being associated with one of the potential or existing infiltration of fluid and the potential or existing extravasation of fluid, etc.

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

[0136] The following text is about Figure 9 Further details are provided regarding non-limiting embodiments or aspects of step 812 of process 800.

[0137] Now for reference Figure 9 , Figure 9This is a flowchart 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 steps of process 900 are performed (e.g., fully, partially, etc.) by a drug source system 102 (e.g., one or more devices of drug source system 102, etc.). In some non-limiting embodiments or aspects, one or more steps of process 900 are performed (e.g., fully, partially, etc.) by a device or group of devices including drug source system 102, such as smart device 104 (e.g., one or more devices of smart device 104), central computing system 108 (e.g., one or more devices of central computing system 108, etc.) and / or terminal / mobile computing system 110 (e.g., one or more devices of terminal / mobile computing system 110, etc.) or separate from it.

[0138] like Figure 9 As shown, in step 902, process 900 includes obtaining drug data. For example, drug source system 102 may obtain drug data. As an example, drug source system 102 may obtain drug data associated with a first type of drug delivered to or planned to be delivered to a patient via the same lumen and a second type of drug delivered to or planned to be delivered to a patient via the same lumen. In such an example, the first type of drug may be different from the second type of drug.

[0139] In some non-limiting embodiments or aspects, the drug data is associated with at least one of the following: an identifier of the drug type, a planned delivery of the drug via a specific drug source device and / or lumen, a previous delivery of the drug via a specific drug source device and / or lumen, the amount of the drug, an identifier of the patient to whom the drug is planned to be delivered (or delivered), one or more identifiers of one or more different types of drugs that are incompatible with delivery via the same lumen as the drug, etc.

[0140] like Figure 9 As shown, in step 904, process 900 includes determining drug compatibility. For example, drug source system 102 can determine drug compatibility. As an example, drug source system 102 can determine the compatibility of a second type of drug with delivery via the same lumen as a first type of drug based on drug data.

[0141] In some non-limiting embodiments or aspects, the drug source system 102 may use identifiers of a first type of drug and / or identifiers of a second type of drug to access a lookup table indicating whether the first type of drug and the second type of 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 identifiers of the first type of drug and / or identifiers of the second type of drug.

[0142] In some non-limiting embodiments or aspects, the drug source device 102 may acquire drug data associated with a third type of drug delivered or planned to be delivered to a patient via another lumen (e.g., a different lumen, etc.), and determine, based on the drug data, the compatibility of a second type of drug with delivery via another lumen identical to that of the third type of drug, wherein the indication further indicates whether the second type of drug is compatible with delivery via another identical lumen associated with another type of visual output. For example, refer again... Figure 2A and 2B If the drug source device 102 determines that the second type of drug is incompatible with delivery via the first lumen 212a, the drug source device 102 may determine the compatibility of the second type of drug with delivery via an alternative lumen, such as the second lumen 212b, based on delivery or planned delivery of the third type of drug via the second lumen 212b, and if the second type of drug is compatible with delivery via the same lumen as the third type of drug, provide an indication that the second type of drug is compatible with delivery via the second lumen 212b.

[0143] like Figure 9 As shown, in step 906, process 900 includes providing a compatibility indication. For example, drug source system 102 can provide a compatibility indication. As an example, drug source system 102 can provide an indication of whether a second type of drug is compatible with delivery via the same lumen associated with the same type of visual output. As another example, drug source system 102 can provide an indication of whether a third type of drug is compatible with delivery via another lumen associated with another visual output at the same time.

[0144] In some non-limiting embodiments or aspects, the drug delivery system 102 can provide an indication of compatibility by controlling the drug delivery device 206 to inhibit or prevent the delivery of a second drug through the same lumen associated with the same type of visual output. For example, a first type of drug can be delivered to a patient using the same lumen associated with the same type of visual output, and a second type of drug can be planned to be delivered to the patient via the same lumen. As an example, and again with reference to... Figure 2A and2B The drug delivery system 102 can determine, based on medical data including drug data, that a first type of drug is delivered to the patient via lumen 212a, and that a second type of drug planned to be delivered or attempted to be delivered via the same lumen 212a is incompatible with the first type of drug (e.g., may cause occlusion, may cause adverse reactions in the patient, etc.). In such an example, the drug delivery system 102 can control the drug delivery device 206a to inhibit or prevent the delivery of the second drug via the same lumen 212a (e.g., by stopping the pump, closing the valve, etc.) and / or provide the user with a prompt to deliver the second type of drug to the patient using another lumen (e.g., 212b, ... 212n, etc.) associated with a different type of visual output than the same type of visual output.

[0145] In some non-limiting embodiments or aspects, first-type and second-type drugs can be delivered to the patient via the same lumen associated with the same type of visual output, and the drug delivery system 102 can provide prompts to the user to treat the same lumen associated with the same type of visual output for either thrombotic occlusion or chemical occlusion. For example, when an occlusion occurs, it can be detected by the drug delivery system 102 as described herein, and the 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 delivery system 102 can determine which drugs are delivered via which lumens to inform the user of the lumen history and / or provide indication of the potential cause of the occlusion, enabling a proper decision on whether the lumen should be treated for thrombotic or chemical occlusion. In some non-limiting embodiments or aspects, the drug delivery system 102 can control the drug delivery device 206 to automatically perform a flushing operation to deliver flushing fluid to the lumen connected to the drug delivery device 206 in response to determining that the lumen occlusion is a chemical occlusion.

[0146] Now for reference Figure 10 , Figure 10 This is a flowchart of a non-limiting embodiment or aspect of process 1000 for positioning the needle tip. In some non-limiting embodiments or aspects, one or more steps of process 1000 are performed (e.g., entirely, partially, etc.) by a smart device 104 (e.g., one or more devices of a system of smart device 104). In some non-limiting embodiments or aspects, one or more steps of process 1000 are performed (e.g., entirely, partially, etc.) by a device or group of devices including smart device 104, such as drug source system 102 (e.g., one or more devices of a system of drug source system 102), central computing system 108 (e.g., one or more devices of central computing system 108), and / or terminal / mobile computing system 110 (e.g., one or more devices of terminal / mobile computing system 110), or separate from it.

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

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

[0149] like Figure 10 As shown, in step 1004, process 1000 includes determining the position of the needle tip of the catheter relative to a patient's blood vessel or urethra. For example, smart device 104 can determine the position of the needle tip relative to a patient's blood vessel or urethra. As an example, smart device 104 can determine the position of the needle tip 706 relative to a patient's blood vessel or urethra based on changes in at least one signal over a period of time.

[0150] In some non-limiting embodiments or aspects, the location of the needle tip 706 is defined as one of the following: within a blood vessel or urethra; within the wall of a blood vessel or urethra; and outside a blood vessel or urethra and its wall. In some non-limiting embodiments or aspects, the smart device 104 and / or one or more components thereof may be connected to or included (e.g., integrated therewith, etc.) at a catheter hub of the catheter 702 located outside the patient's body. For example, sensors 254 of the smart device 104 (e.g., pressure sensors, acoustic sensors, etc.) may measure at least one signal including at least one of pressure and acoustic signals, wherein the catheter includes a needle with a tip for delivering fluid to the patient.

[0151] In some non-limiting embodiments or aspects, the smart device 104 determines the position of the needle tip 706 in relation to one of potential or existing fluid infiltration and potential or existing fluid extravasation. For example, sensor 254 (e.g., one or more pressure sensors, one or more acoustic sensors, etc.) can detect temporal changes in pressure and / or acoustic signals caused by the proper insertion of the needle tip 706 of catheter 702 into a blood vessel or urethra, its location within the wall of a blood vessel or urethra, or its location outside a blood vessel or urethra. As an example, the smart device 104 can compare changes in at least one signal within this time period with threshold changes associated with the patient's heartbeat. For example, changes in pressure and / or acoustic signals can be associated with pressure and / or acoustic changes in a blood vessel or urethra due to the patient's heartbeat. As an example, the smart device 104 can compare detected changes in pressure and / or acoustic signals with changes in pressure and / or acoustic signals associated with the patient's heartbeat to determine whether the needle tip 706 of catheter 702 is properly located within the patient's blood vessel (e.g., artery, vein, etc.). In such an example, if the tip 706 of the needle of catheter 702 overflows a blood vessel or urethra (e.g., punctures the wall of a blood vessel or urethra, is not properly positioned within a blood vessel or urethra, etc.), the pressure and / or acoustic characteristics of at least one signal measured by sensor 254 will change. In some non-limiting embodiments or aspects, drug infiltration or extravasation into the tissue surrounding a blood vessel or urethra (rather than permeation or extravasation into the blood vessel or urethra) may result in sensor 254 detecting a unique pressure or acoustic signal, depending on the effect of infiltration or extravasation on the surrounding tissue (e.g., if the extravasated drug is a strong foaming agent, this effect may be severe, etc.).

[0152] In some non-limiting embodiments or aspects, the smart device 104 determines at least one of catheter blockage and catheter disconnection from the needleless connector based on changes in at least one signal over a period of time. For example, the smart device 104 may compare changes in at least one signal over that time period with a threshold time period associated with the formation of an occlusion in the catheter. As an example, the smart device 104 may compare relatively slow changes or variations in pressure signals over time (e.g., a relatively slow decrease in heart rate amplitude and / or a decrease in blood pressure, etc., compared to infiltration or extravasation) with a threshold level to determine an occlusion event rather than an infiltration or extravasation event. For example, an occlusion in the lumen may develop at a relatively slow rate over time (e.g., compared to a permeation event, extravasation event, disconnection event, etc.), which slowly changes the pressure signal sensed by sensor 254. As an example, the smart device 104 may determine an occlusion event and, in response to detecting an occlusion event, provide a warning and / or automatically flush the lumen associated with the occlusion. In some non-limiting embodiments, the smart device 104 may detect a disconnection event in response to a pressure signal detected by the sensor 254 that is substantially equal to atmospheric pressure. This indicates that the connection of the conduit 702, such as the pinless connector 214, is disconnected from it, and provides the user with a change to resolve the connection.

[0153] like Figure 10 As shown, in step 1006, process 1000 includes providing the position of the needle tip. For example, smart device 104 can provide the position of the needle tip. As an example, smart device 104 can provide the position of the tip 706 of the needle relative to a patient's blood vessel or urethra.

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

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

[0156] In some non-limiting embodiments or aspects, the smart device 104 and / or the needleless catheter may include communication circuitry (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 needleless connector 214 may process pressure signals and / or acoustic signals on a microprocessor within the housing 250 of the smart device 104 and / or on a microprocessor within the housing 402 of the needleless connector 214, which includes a sensor 254 and a microprocessor. Furthermore, the smart device 104 and / or the needleless connector 214 may wirelessly transmit (and / or via a wired connection) the pressure signals and / or acoustic signals to a remote computer that performs digital signal processing on the pressure signals and / or acoustic signals to identify and classify events of interest (e.g., infiltration, extravasation, catheter blockage, catheter disconnection, etc.).

[0157] In some non-limiting embodiments or aspects, the smart device 104 may provide real-time feedback during catheter insertion (e.g., via visual indicator 252, output component 312, drug delivery system 102, etc.) so that a clinician or other person may be alerted whether the catheter 702 is correctly inserted and / or whether the tip 706 of the needle of the catheter 702 has been punctured or is in the process of puncturing a blood vessel or urethra and / or has been accidentally disconnected or blocked.

[0158] Now for reference Figure 11 , Figure 11 This is a flowchart of a non-limiting embodiment or aspect of a process 1100 for compliance event monitoring. In some non-limiting embodiments or aspects, one or more steps of process 1100 are performed (e.g., entirely, partially, etc.) by a smart device 104 (e.g., one or more devices of a system of smart device 104). In some non-limiting embodiments or aspects, one or more steps of process 1100 are performed by a device or group of devices separate from or related to a smart device, such as a drug source system 102 (e.g., one or more devices of drug source system 102), a central computing system 108 (e.g., one or more devices of central computing system 108), and / or a terminal / mobile computing system 110 (e.g., one or more devices of terminal / mobile computing system 110), or a smart device.

[0159] like Figure 11 As shown, in step 1102, process 1100 includes acquiring a force signal. For example, smart device 104 can acquire a force signal. As an example, smart device 104 can acquire a force signal measured by a sensor 252 (e.g., a force sensor, etc.) connected to a needleless connector 214 that includes a fluid flow path. In such an example, sensor 252 can utilize a force sensor connected to a needleless connector that includes a fluid flow path to measure the force signal, and smart device 104 (and / or drug delivery system 101, central computing system 108, terminal / mobile computing system 100, etc.) can acquire the force signal from sensor 252.

[0160] like Figure 11 As shown, in step 1104, process 1100 includes determining an event associated with the needleless connector based on a force signal. For example, smart device 104 may determine an event associated with the needleless connector 214 based on a force signal. As an example, smart device 104 may determine at least one of the following based on the force signal: a washing event of washing the needleless connector with a disinfectant, a rinsing event of rinsing the needleless connector with a solution, a connection event of the needleless connector being connected to a medical device, or any combination thereof.

[0161] In some non-limiting embodiments or aspects, the force sensor 502 includes at least one of the following: a piezoelectric element, a force-sensitive resistor (FSR) sensor, a strain gauge, or any combination thereof. In some non-limiting embodiments or aspects, the force sensor 502 is positioned between the outer surface of the inner wall 510 of the pinless connector 214 (e.g., a harder plastic inner wall) defining a fluid flow path for the pinless connector 214 and the inner surface of the outer wall 512 of the pinless connector 214 surrounding the inner wall 510 (e.g., a softer, more flexible, more resilient, rubber, or other wall). In some non-limiting embodiments or aspects, the region between the outer surface of the inner wall 510 of the needleless connector 214 (e.g., a harder inner plastic wall) defining the fluid flow path of the needleless connector 214 and the inner surface of the outer wall 512 of the needleless connector 214 surrounding the inner wall 510 (e.g., a softer, more flexible, more numerous, more resilient, rubber, etc. wall) (which may be retained by the user during cleaning and / or connection to other medical devices) may be filled with a rubber or other flexible type of material 514, including a force sensor 502 as a force-sensing membrane within 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 and / or near the threads of the inlet 404 of the needleless connector 214.

[0162] In some non-limiting embodiments or aspects, force sensor 502 includes a plurality of force sensors 502 positioned around the fluid flow path of the pinless connector 214 between an outer surface of the inner wall 510 of the pinless connector 214 defining the fluid flow path of the pinless connector 214 and an inner surface of the outer wall 512 of the pinless connector 214 surrounding the inner wall 510 of the pinless connector 214. For example, the inlet 404 of the pinless connector 214 may include a diaphragm 408 including a surface facing a first direction, and force sensor 502 may be configured to detect a force in a second direction perpendicular to the surface of the diaphragm facing the first direction. As an example, a flushing event, which may include a pulsating flushing event, may be determined based on a force signal indicating a periodic force in a second direction perpendicular to the surface of the diaphragm facing the first direction.

[0163] In some non-limiting embodiments or aspects, sensor 254 includes a pressure sensor, and the pressure sensor is one of the following: in direct contact with fluid in the fluid flow path of the needleless connector; located within the inner wall defining the fluid flow path of the needleless connector; and located within the lumen wall connected to the needleless connector. For example, smart device 104 can determine or detect pulsating flushing, irrigation, and / or medical application by means of a pressure sensor in contact with the fluid path and / or lumen in needleless connector 214.

[0164] In some non-limiting embodiments or aspects, sensor 254 includes an optical sensor configured to detect at least one of a color signature and reflectivity of a medical device connected to and / or being connected to the needleless connector 214, and smart device 104 can determine the type of medical device based on at least one of the color signature and reflectivity of the medical device. For example, the color signature and / or reflectivity of the medical device can indicate a syringe, IV bag, infusion pump, and / or a specific type thereof.

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

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

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

[0168] like Figure 11 As shown, in step 1106, process 1100 includes providing an indication of an event. For example, smart device 104 can provide an indication of an event. As an example, smart device 104 can provide an indication of a determined event.

[0169] In some non-limiting embodiments or aspects, the smart device 104 including the needleless connector 214 may include a visual indicator 252, and the visual indicator 252 may be configured to provide a visual indication associated with at least one of the following: a washing event of washing the needleless connector with a disinfectant, a rinsing event of rinsing the needleless connector with a solution, a connection event of the needleless connector being connected to a medical device, or any combination thereof. For example, as Figure 6B As shown in implementation 600B, the smart device 104 can provide direct patient-side feedback (e.g., via an LED light to a nurse, etc.) in response to (i) detecting that the needleless connector 214 and / or its lumen 212 has not been washed within a predetermined time period and / or prior to planned use, (ii) detecting that the needleless connector 214 and / or its lumen 212 has not been washed for a sufficient period of time before entering the catheter line, (iii) detecting that the flushing of the needleless connector 214 and / or lumen 212 has expired, (iv) detecting that the sterilization cap has not been attached after the previous entry of the needleless connector 214 and / or lumen 212, etc. For example, the smart device 104 may include the needleless connector 214, and the needleless connector 214 may be configured to detect at least one of a washing event, a flushing event, a connection or capping event, or any combination thereof. As an example, the pinless connector 214 can be configured to provide information and / or data associated with detected washing events, detected rinsing events, and / or detected connection or capping events (e.g., using processor 304, memory 306, storage component 308, input component 310, output component 312, etc.) to store events and report compliance performance for compliance event monitoring.

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

[0171] In some non-limiting embodiments or aspects, a pattern of events including at least one of the following can be determined based on force signals: a washing event of washing the needleless connector 214 with a disinfectant, a rinsing event of washing the needleless connector 214 with a solution, a connection or capping event of the needleless connector 214 to a medical device, or any combination thereof, and a drug delivery event of administering medication to a patient via the needleless connector 214 can be determined based on the pattern of the events.

[0172] In some non-limiting embodiments or aspects, the smart device 104 may use sensor 254 to detect identification tags on a medical device connected to or being connected 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 utilize visual indicator 252 to provide visual indications associated with any information or data sensed and / or measured by sensor 254, such as the type of medical device, drug administration events via the needleless connector to a patient, identification of the medical device, movement of the patient, patient fall events, movement of the patient's bed, color of fluid in the fluid flow path of the needleless connector 412, blood draw in the needleless connector, blood retention in the needleless connector, washing events using disinfectant to clean the needleless connector, rinsing events using solution to rinse the needleless connector, connection or capping events of the needleless connector to a medical device, or any combination thereof.

[0173] Although embodiments or aspects have been described in detail for illustrative and descriptive purposes, it should be understood that such detail is for that purpose only, and the embodiments or aspects are not limited to the disclosed embodiments or aspects, but rather are intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that this 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 stated in the claims and / or disclosed in the specification. While each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes combinations of each dependent claim with each other claim in the claim set.

Claims

1. A system comprising: Multiple smart devices are configured to be connected to multiple first terminals of multiple IV lines, wherein each smart device includes a visual indicator, communication circuitry, and a user input component, the user input component being configured to receive user input from a user, and wherein the visual indicator of the smart device includes a light-emitting diode, and wherein the light-emitting diode is configured to emit multiple different colors of light; A drug source system comprising multiple drug source devices connected to multiple second terminals of the plurality of IV lines, wherein each drug source device includes a visual indicator, communication circuitry, and a user input component configured to receive user input from a user, wherein the communication circuitry of the drug source device is configured to establish communication with the communication circuitry of the smart device based on user input to the user input component of the drug source device and user input to the user input component of the smart device; and One or more processors are programmed and / or configured to: In response to the communication circuit of the drug source device, communication with the communication circuit of the smart device is established based on user input to the user input component of the drug source device and user input to the user input component of the smart device. By cyclically passing through available colors of light to select previously unused colors of light, the same color of light generated by the visual indicator of the smart device and the visual indicator of the drug source device is determined as light of a different color from each other color of light generated by each visual indicator of each of the other smart devices and each visual indicator of each of the other drug source devices. Based on the communication established between the communication circuit of the drug source device and the communication circuit of the smart device, the visual indicator of the smart device and the visual indicator of the drug source device are controlled to produce the same type of visual output, wherein the same type of visual output includes light of the same color. Associate the same type of visual output with the same IV line among the plurality of IV lines, wherein the drug source device is connected to the same IV line; By using a first identifier associated with a first type of drug and a second identifier associated with a second type of drug to access a lookup table indicating whether the first type of drug and the second type of drug are compatible or incompatible, drug data associated with a first type of drug delivered or planned to be delivered to a patient via the same IV line and a second type of drug delivered or planned to be delivered to a patient via the same IV line are obtained, wherein the first type of drug is different from the second type of drug. Based on drug data, determine the compatibility of the second type of drug with delivery via the same IV pathway as the first type of drug; and Provides an indication of whether the second type of drug is compatible with delivery via the same IV line associated with the same type of visual output.

2. The system of claim 1, wherein the drug source system includes an infusion pump system, and wherein the plurality of drug source devices include a plurality of infusion pumps.

3. The system of claim 1, wherein a first type of drug is delivered to the patient via the same IV line, wherein a second type of drug is planned to be delivered to the patient via the same IV line, and wherein the one or more processors are programmed and / or configured to provide an indication of whether the second type of drug is compatible with delivery via the same IV line associated with the same type of visual output through the following steps: Control the drug delivery device to inhibit or prevent the delivery of a second drug via the same IV line associated with the same type of visual output.

4. The system of claim 1, wherein the first type of drug is delivered to the patient via the same IV line, wherein the second type of drug is planned to be delivered to the patient via the same IV line, and wherein the indication of whether the second type of drug is compatible with delivery via the same IV line associated with the same type of visual output includes prompting the user to use another IV line associated with a different type of visual output than the same type of visual output to deliver the second type of drug to the patient.

5. The system of claim 1, wherein the first type of drug and the second type of drug are delivered to the patient via the same IV line associated with the same type of visual output, and wherein an indication of whether the second type of drug is compatible with delivery via the same IV line associated with the same type of visual output includes prompting the user to treat the same IV line associated with the same type of visual output for either thromboembolism or chemoembolism.

6. The system of claim 1, wherein the visual indicator of the smart device is configured to generate visual output of the same type as that of the visual indicator of the drug source device in response to connection to the IV line, while establishing communication between the communication circuit of the drug source device and the communication circuit of the smart device, and wherein the visual indicator of the smart device is configured to automatically stop generating visual output of the same type as that of the visual indicator of the drug source device in response to disconnection from the IV line.

7. The system of claim 1, wherein the communication circuitry of the other drug source device is configured to establish communication with the communication circuitry of the other intelligent device based on user input to a user input component of the other drug source device and user input to a user input component of the other intelligent device, and wherein one or more processors are further programmed and / or configured to: Based on the communication established between the communication circuit of another drug source device and the communication circuit of another smart device, the visual indicator of the other smart device and the visual indicator of the other drug source device are controlled to produce another visual output of the same type, wherein the other visual output of the same type is different from the same type of visual output. Associate another visual output of the same type with another identical IV line among multiple IV lines, wherein another drug source device is connected to another identical IV line; Obtain drug data associated with a third type of drug delivered or planned to be delivered to a patient via another identical IV line; as well as The compatibility of a second-type drug with delivery via another identical IV line, the same as that of a third-type drug, is determined based on drug data, wherein the indication also indicates whether the second-type drug is compatible with delivery via another identical IV line associated with another identical type of visual output.

8. A method comprising: Multiple smart devices are connected to multiple IV lines, wherein each smart device includes a visual indicator, communication circuitry, and user input components, wherein the visual indicator of the smart device includes a light-emitting diode (LED), and wherein the LED is configured to emit multiple different colors of light. Multiple drug source devices of the drug source system are connected to multiple IV lines, wherein each drug source device includes a visual indicator, communication circuitry, and user input components; User input is received via the user input component of the smart device; User input is received via the user input component of the drug source device; Using the communication circuits of the smart device and the drug source device, communication between the smart device and the drug source device is established based on user input received by the user input component of the drug source device and user input received by the user input component of the smart device. In response to the communication circuit of the drug source device, communication with the communication circuit of the smart device is established based on user input to the user input component of the drug source device and user input to the user input component of the smart device. The communication circuit utilizes at least one processor to select a previously unused color of light by cyclically passing through available colors of light. The communication circuit determines that the same color of light is generated by the visual indicator of the smart device and the visual indicator of the drug source device, as a color of light different from each other color of light generated by each visual indicator of each of the other smart devices and each visual indicator of each of the other drug source devices. The visual indicator of the smart device and the visual indicator of the drug source device are controlled by at least one processor to produce the same type of visual output based on the communication established between the drug source device and the smart device, wherein the same type of visual output includes light of the same color. Using at least one processor, the same type of visual output is associated with the same IV line among multiple IV lines, wherein the drug source device is connected to the same IV line. By using a first identifier associated with a first type of drug and a second identifier associated with a second type of drug to access a lookup table indicating whether the first type of drug and the second type of drug are compatible or incompatible, drug data associated with a first type of drug delivered or planned to be delivered to a patient via the same IV line and a second type of drug delivered or planned to be delivered to a patient via the same IV line are obtained using at least one processor, wherein the first type of drug is different from the second type of drug. Using at least one processor, determine the compatibility of a second type of drug with delivery via the same IV pathway as a first type of drug based on drug data; and The processor provides an indication of whether the delivery of a second type of drug is compatible with delivery via the same IV line associated with the same type of visual output.

9. The method of claim 8, wherein the drug source system includes an infusion pump system, and wherein the plurality of drug source devices include a plurality of infusion pumps.

10. The method of claim 8, further comprising: Delivering a type 1 drug to a patient via the same IV line associated with the same type of visual output, wherein a type 2 drug is planned to be delivered to the patient via the same IV line, and wherein providing an indication of whether delivery of the type 2 drug via the same IV line associated with the same type of visual output further includes: Control the drug delivery device to inhibit or prevent the delivery of a second drug via the same IV line associated with the same type of visual output.

11. The method of claim 8, further comprising: The delivery of a first type of drug to a patient via the same IV line associated with the same type of visual output, wherein a second type of drug is planned to be delivered to the patient via the same IV line, and wherein an indication of whether the delivery of the second type of drug via the same IV line associated with the same type of visual output is compatible includes prompting the user to use a different IV line associated with a different type of visual output rather than the same type of visual output to deliver the second type of drug to the patient.

12. The method according to claim 8, further comprising: The first type of drug and the second type of drug are delivered to the patient via the same IV line associated with the same type of visual output, and the indication of whether the second type of drug is compatible with delivery via the same IV line associated with the same type of visual output includes prompting the user to treat the same IV line associated with the same type of visual output for either thromboembolism or chemoembolism.

13. The method of claim 8, further comprising: In response to being connected to the IV line, the same type of visual output as the visual indicator of the drug source device is generated using the visual indicator of the smart device, while establishing communication between the drug source device and the smart device. as well as In response to disconnection from the IV line, the smart device automatically stops producing the same type of visual output as the visual indicator of the drug source device.

14. The method of claim 8, further comprising: User input is received by the user input component of another smart device; User input is received by the user input component of another drug source device; Using the communication circuits of another drug source device and another smart device, communication is established between the other drug source device and the other smart device based on user input received by the user input component of the other drug source device and user input received by the user input component of the other smart device. Using at least one processor, based on communication established between another drug source device and another smart device, the visual indicator of the other smart device and the visual indicator of the other drug source device are controlled to produce another visual output of the same type, wherein the other visual output of the same type is different from the same type of visual output. Using at least one processor, another visual output of the same type is associated with another identical IV line among a plurality of IV lines, wherein another drug source device is connected to another identical IV line. By using a third identifier associated with the third type of drug to access a lookup table indicating whether the second and third type of drugs are compatible or incompatible, drug data associated with a third type of drug delivered or planned to be delivered to a patient via another identical IV line is obtained using at least one processor; and Using at least one processor, based on drug data, the compatibility of a second type of drug with delivery via another identical IV line as that of a third type of drug is determined, wherein the indication also indicates whether the second type of drug is compatible with delivery via another identical IV line associated with another identical type of visual output.

15. A system comprising: One or more processors, which are programmed and / or configured to: Based on communication established between the communication circuit of the drug source device and the communication circuit of the smart device, the visual indicators of the smart device and the visual indicators of the drug source device are controlled to produce the same type of visual output, wherein the drug source device is connected to a lumen, and wherein the smart device is configured to be connected to the lumen, wherein each visual indicator includes a light-emitting diode, wherein each light-emitting diode is configured to emit multiple different colors of light, and wherein, in response to establishing communication between the communication circuit of the drug source device and the communication circuit of the smart device, the one or more processors are configured to determine the same color of light produced by the visual indicators of the smart device and the visual indicators of the drug source device by cyclically passing through available colors of light to select previously unused colors of light, as a color of light different from each other color of light produced by each visual indicator of each of the multiple other smart devices and each visual indicator of each of the multiple other drug source devices, wherein the same type of visual output includes the same color of light; Associate visual outputs of the same type with the lumen; Obtain drug data associated with a type 1 drug delivered or planned to a patient via a lumen and a type 2 drug delivered or planned to a patient via a lumen, wherein the type 1 drug is different from the type 2 drug; Based on drug data, determine the compatibility of the second type of drug with delivery via the same lumen as the first type of drug; and Provides an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

16. A computer-implemented method, comprising: The system utilizes at least one processor to control the visual indicators of a smart device and a drug source device to produce the same type of visual output based on communication established between the communication circuits of the drug source device and the smart device, wherein the drug source device is connected to a lumen, and wherein the smart device is configured to be connected to the lumen, wherein each visual indicator includes a light-emitting diode, wherein each light-emitting diode is configured to emit multiple different colors of light, and wherein, in response to establishing communication between the communication circuits of the drug source device and the smart device, the at least one processor determines the same color of light produced by the visual indicators of the smart device and the visual indicators of the drug source device by cyclically passing through available colors of light to select previously unused colors of light, as a color of light different from each other color of light produced by each visual indicator of each of the multiple other smart devices and each visual indicator of each of the multiple other drug source devices, wherein the same type of visual output includes the same color of light; Associate the same type of visual output with the lumen using at least one processor; Using at least one processor, drug data associated with a first type of drug delivered or planned to be delivered to a patient via a lumen and a second type of drug delivered or planned to be delivered to a patient via a lumen are obtained, wherein the first type of drug is different from the second type of drug; Using at least one processor, the compatibility of a second type of drug with delivery via the same lumen as a first type of drug is determined based on drug data; and The processor provides an indication of whether the delivery of a second type of drug via the same lumen associated with the same type of visual output is compatible.

17. A computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising program instructions, the program instructions causing the at least one processor, when executed by at least one processor, to: The visual indicators of the smart device and the drug source device are controlled based on communication established between the communication circuits of the drug source device and the communication circuits of the smart device to produce 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. Each visual indicator includes a light-emitting diode (LED), and each LED is configured to emit multiple different colors of light. In response to establishing communication between the communication circuit of the drug source device and the communication circuit of the smart device, the program instructions, when executed by the at least one processor, cause the at least one processor to determine, by cyclically passing through available colors of light to select a previously unused color of light, the same color of light produced by the visual indicator of the smart device and the visual indicator of the drug source device, as light of a different color from other colors of light produced by each visual indicator of each of the plurality of other smart devices and each visual indicator of each of the plurality of other drug source devices, wherein the same type of visual output includes light of the same color; Associate visual outputs of the same type with the lumen; Obtain drug data associated with a type 1 drug delivered or planned to a patient via a lumen and a type 2 drug delivered or planned to a patient via a lumen, wherein the type 1 drug is different from the type 2 drug; The compatibility of the second type of drug with delivery via the same lumen as the first type of drug was determined based on drug data; as well as Provides an indication of whether the second type of drug is compatible with delivery via the same lumen associated with the same type of visual output.

Images