Flow sensor system

Abstract

The invention relates to a flow sensor system. A system may include a disposable flow sensor and a base for the disposable flow sensor. In one embodiment, a method may include scanning a flow sensor tag attached to a disposable flow sensor using an optical scanner of a base for the disposable flow sensor to decode a flow sensor identifier associated with the flow sensor, a patient tag attached to a patient is scanned using an optical scanner of a base for the disposable flow sensor to decode a patient identifier associated with the patient, and the disposable flow sensor is connected to the base.

Description

[0001] This application is a divisional application of the invention patent application entitled “Flow Sensor System”, which has Chinese application number 202180015051.X and filing date January 27, 2021, PCT application PCT / US2021 / 015187.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Application Serial No. 62 / 966,291, filed on January 27, 2020, entitled “Flow Sensor System,” the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0004] The present disclosure relates generally to flow sensor systems and, in some non-limiting embodiments or aspects, to flow sensor systems for sensing flow of a fluid medicament. Background Art

[0005] There is a need to reduce medication errors at the bedside during bolus delivery. It would be advantageous to provide a record and electronic measurement of bolus delivery, allowing monitoring of bolus delivery and automatic recording of bolus delivery as part of a patient's health record. In addition, it would be advantageous to provide a reminder when a bolus delivery that is inconsistent with a patient's medical record is about to occur. Summary of the invention

[0006] Non-limiting embodiments or aspects are set forth in the following numbered clauses:

[0007] Item 1. A system comprising: a flow sensor comprising: a flow tube including a fluid inlet at a first end of the flow tube, a fluid outlet at a second end of the flow tube opposite to the first end of the flow tube, a fluid injection port between the first end and the second end of the flow tube, and a valve configured to control the flow of fluid in the flow tube; at least one sensor configured to characterize at least one property of the fluid in the flow tube; and a flow sensor electrical contact electrically connected to the at least one sensor; and a base configured to be connected to the flow sensor, wherein the base comprises: one or more processors; a base electrical contact electrically connected to the one or more processors; a short-range wireless communication device; and a display, wherein when the flow sensor is connected to the base, the flow sensor electrical contact is electrically connected to the base electrical contact.

[0008] Item 2. A system as described in Item 1, wherein the valve is configured to switch between multiple different states to control at least one of: the flow of fluid between a fluid inlet and a fluid outlet, the flow of fluid between a fluid inlet and a fluid injection port, the flow of fluid between a fluid injection port and a fluid outlet, or any combination thereof.

[0009] Clause 3. The system of any of Clauses 1 and 2, wherein the one or more processors are programmed and / or configured to automatically detect the state of the valve when a flow sensor is connected to the base.

[0010] Clause 4. The system of any of clauses 1-3, wherein the one or more processors are programmed and / or configured to determine whether to record information associated with the at least one property of the fluid in the flow tube based on the detected valve state.

[0011] Clause 5. The system of any of Clauses 1-4, wherein the one or more processors are programmed and / or configured to automatically detect connection of the flow sensor to the base.

[0012] Clause 6. The system of any of Clauses 1-5, wherein the one or more processors are programmed and / or configured to automatically detect connection of a syringe to a fluid injection port of a flow sensor.

[0013] Clause 7. The system of any of Clauses 1-6, wherein the display comprises a touch screen display configured to receive user input from a user.

[0014] Clause 8. The system of any of Clauses 1-7, wherein the flow sensor is inserted in-line with an IV line between the fluid source and the patient.

[0015] Clause 9. A system as described in any of clauses 1-8, wherein the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe via a short-range wireless communication connection when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

[0016] Clause 10. The system of any of clauses 1-9, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver.

[0017] Clause 11. The system of any of clauses 1-10, wherein the base further comprises a wireless communication device configured to transmit information associated with the at least one property of the fluid in the flow tube to a remote computing device.

[0018] Clause 12. The system of any of Clauses 1-11, wherein the base further comprises an optical scanner configured to read a bar code label.

[0019] Clause 13. The system of any of Clauses 1-12, wherein the base further comprises an opening configured to receive the flow sensor, and wherein the flow sensor is configured to slidably engage the opening of the base.

[0020] Item 14. A flow sensor comprising: a flow tube including a fluid inlet at a first end of the flow tube, a fluid outlet at a second end of the flow tube opposite to the first end of the flow tube, a fluid injection port between the first end and the second end of the flow tube, and a valve configured to control the flow of fluid in the flow tube; at least one sensor configured to characterize at least one property of the fluid in the flow tube; and a flow sensor electrical contact electrically connected to the at least one sensor.

[0021] Item 15. A flow sensor as described in Item 14, wherein the valve is configured to switch between multiple different states to control at least one of the following: the flow of fluid between a fluid inlet and a fluid outlet, the flow of fluid between a fluid inlet and a fluid injection port, the flow of fluid between a fluid injection port and a fluid outlet, or any combination thereof.

[0022] Clause 16. The flow sensor of any of Clauses 14 and 15, wherein the flow sensor is inserted in-line with an IV line between a fluid source and a patient.

[0023] Item 17. A base for a flow sensor, comprising: one or more processors; base electrical contacts electrically connected to the one or more processors; a short-range wireless communication device; and a display, wherein when the flow sensor is connected to the base, the base sensor electrical contacts are electrically connected to at least one sensor of the flow sensor.

[0024] Clause 18. The base of Clause 17, wherein the one or more processors are programmed and / or configured to automatically detect a status of a valve of the flow sensor when the flow sensor is connected to the base.

[0025] Clause 19. The base of any of clauses 17 and 18, wherein the one or more processors are programmed and / or configured to determine whether to record information associated with at least one property of the fluid sensed by the flow sensor based on the detected valve state.

[0026] Clause 20. The base of any of Clauses 17-19, wherein the one or more processors are programmed and / or configured to automatically detect connection of the flow sensor to the base.

[0027] Clause 21. The base of any of Clauses 17-20, wherein the one or more processors are programmed and / or configured to automatically detect connection of a syringe to the flow sensor.

[0028] Clause 22. The base of any of Clauses 17-21, wherein the display comprises a touch screen display configured to receive user input from a user.

[0029] Clause 23. A base as described in any of clauses 17-22, wherein the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe via a short-range wireless communication connection when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

[0030] Clause 24. The base of any of clauses 17-23, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver.

[0031] Clause 25. The base of any of clauses 17-24, wherein the base further comprises a wireless communication device configured to transmit information associated with the at least one property of the fluid in the flow tube to a remote computing device.

[0032] Clause 26. The base of any of Clauses 17-25, wherein the base further comprises an optical scanner configured to read a bar code label.

[0033] Clause 27. The base of any of Clauses 17-26, wherein the base further comprises an opening configured to receive the flow sensor, and wherein the flow sensor is configured to slidably engage the opening of the base.

[0034] Item 28. A system comprising: a flow sensor, comprising: a flow tube, including a fluid inlet at a first end of the flow tube, a fluid outlet at a second end of the flow tube opposite to the first end of the flow tube, a fluid injection port between the first end and the second end of the flow tube, wherein the fluid injection port extends from the flow tube in a first direction parallel to the longitudinal axis of the fluid injection port; and a base configured to be connected to the flow sensor, wherein the base comprises: a short-range wireless communication device, which includes a bent coil antenna, wherein the bent coil antenna is radially bent relative to the longitudinal axis of the fluid injection port when the flow sensor is connected to the base.

[0035] Clause 29. The system of Clause 28, wherein the curved coil antenna extends in a first direction parallel to a longitudinal axis of the fluid injection port.

[0036] Clause 30. The system of any of Clauses 28-30, wherein the base further comprises a display, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the display.

[0037] Clause 31. The system of any of Clauses 28-30, wherein the base further comprises a display, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the display.

[0038] Clause 32. The system of any of clauses 28-31, wherein the fluid injection port is configured to connect to a syringe, and wherein the curved coil antenna bends radially around the syringe when the syringe is connected to the fluid injection port of the flow sensor and the flow sensor is connected to the base.

[0039] Clause 33. The system of any of Clauses 28-32, wherein the attached short-range wireless communication tag is attached to the body of the injector.

[0040] Clause 34. A system as described in any of Clauses 28-33, wherein the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe via a short-range wireless communication connection when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

[0041] Clause 35. The system of any of Clauses 28-34, wherein the short-range wireless communication device receives information associated with a drug included in a syringe from the short-range wireless communication tag when the short-range wireless communication tag is brought into communication range of the short-range wireless communication device.

[0042] Clause 36. The system of any of clauses 28-35, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver.

[0043] Clause 37. A system comprising: a flow sensor comprising: a flow tube comprising a fluid inlet at a first end of the flow tube, a fluid outlet at a second end of the flow tube opposite to the first end of the flow tube, a fluid injection port between the first end and the second end of the flow tube, wherein the fluid injection port is configured to be connected to a syringe; and a base configured to be connected to the flow sensor, wherein the base comprises: a short-range wireless communication device comprising a bent coil antenna, wherein when the syringe is connected to the fluid injection port of the flow sensor and the flow sensor is connected to the base, the bent coil antenna is radially bent around the syringe.

[0044] Clause 38. The system of Clause 37, wherein when a syringe is connected to the fluid injection port of the flow sensor and the flow sensor is connected to the base, the curved coil antenna extends in a first direction parallel to a longitudinal axis of the syringe.

[0045] Clause 39. The system of any of Clauses 37 and 38, wherein the base further comprises a display, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the display.

[0046] Clause 40. The system of any of Clauses 37-39, wherein the base further comprises a display, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the display.

[0047] Clause 41. The system of any of Clauses 27-40, wherein the attached short-range wireless communication tag is attached to the body of the injector.

[0048] Clause 42. A system as described in any of Clauses 27-41, wherein the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe via a short-range wireless communication connection when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

[0049] Clause 43. The system of any of Clauses 27-42, wherein the short-range wireless communication device receives information associated with a drug included in a syringe from the short-range wireless communication tag when the short-range wireless communication tag is brought into communication range of the short-range wireless communication device.

[0050] Clause 44. The system of any of clauses 27-43, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver.

[0051] Clause 45. A base for a flow sensor, comprising: a housing including: an opening configured to receive the flow sensor; one or more processors; a display; and a short-range wireless communication device including a curved coil antenna.

[0052] Clause 46. The base of Clause 45, wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the display.

[0053] Clause 47. The base of any of Clauses 45 and 46, wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the display.

[0054] Clause 48. The system of any of Clauses 45-47, wherein the curved coil antenna bends radially around the syringe when the syringe is connected to the flow sensor and the flow sensor is connected to the base.

[0055] Clause 49. A system as described in any of Clauses 45-48, wherein the attached short-range wireless communication tag is attached to the body of the syringe.

[0056] Clause 50. A system as described in any of Clauses 45-49, wherein the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe via a short-range wireless communication connection when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

[0057] Clause 51. The system of any of Clauses 45-50, wherein the short-range wireless communication device receives information associated with a drug included in a syringe from the short-range wireless communication tag when the short-range wireless communication tag is brought into communication range of the short-range wireless communication device.

[0058] Clause 52. The system of any of clauses 45-51, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver.

[0059] Clause 53. A method comprising: scanning a flow sensor tag attached to a disposable flow sensor using an optical scanner of a base for a disposable flow sensor to decode a flow sensor identifier associated with the flow sensor; scanning a patient tag attached to a patient using an optical scanner of a base for a disposable flow sensor to decode a patient identifier associated with the patient; and connecting the disposable flow sensor to the base.

[0060] Clause 54. The method of Clause 53, further comprising: integrating a disposable flow sensor into the IV line.

[0061] Clause 55. The method of any of clauses 53 and 54, wherein the disposable flow sensor is integrated into the IV line prior to scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor to the base.

[0062] Clause 56. The method of any of clauses 53-55, wherein the disposable flow sensor is integrated into the IV line after scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor to the base.

[0063] Clause 57. The method of any of Clauses 53-56, further comprising: transmitting the flow sensor identifier and the patient identifier to a remote computing device using the base; associating the flow sensor identifier with the patient identifier using the remote computing device in a database.

[0064] Clause 58. The method as described in any of clauses 53-57 further includes: using the base to transmit a request for the status of the flow sensor associated with the flow sensor identifier to the remote computing device; using the base to receive an indication of the status of the flow sensor associated with the flow sensor identifier from the remote computing device, wherein the indication of the status of the flow sensor includes an indication of whether the flow sensor identifier of the flow sensor is associated with a patient identifier of the patient.

[0065] Clause 59. The method described in any of Clauses 53-58 further includes: using the base to transmit a base identifier associated with the base to a remote computing device in a request for a status of a flow sensor associated with the flow sensor identifier; and associating the base identifier with the flow sensor identifier and the patient identifier using the remote computing device in a database.

[0066] Clause 60. The method as described in any of Clauses 53-59 further includes: using the base to transmit a request for information associated with a patient associated with a patient identifier to a remote computing device; using the base to receive information associated with the patient from the remote computing device; and using a display of the base to display the information associated with the patient.

[0067] Clause 61. The method of any of Clauses 53-60, wherein the information associated with the patient comprises at least one of a list of drug allergies associated with the patient and a list of drug dosages to be administered for the patient.

[0068] Clause 62. The method as described in any of clauses 53-61 further includes: using a short-range wireless communication device of a base to scan a short-range wireless communication tag attached to the syringe to decode a drug identifier associated with the drug in the syringe; using the base to compare the drug identifier with at least one of a list of drug allergies associated with the patient and a list of drug doses to be administered for the patient; and using a display of the base to display a reminder associated with the drug administered to the patient.

[0069] Clause 63. The method of any of clauses 53-62, wherein the short-range wireless communication device comprises a near field communication (NFC) receiver, and wherein the short-range wireless communication tag comprises an NFC tag.

[0070] These and other features and characteristics of the present disclosure, as well as the methods of operation and function of the related elements of the structure and the economy of incorporation and manufacture of the parts, will become more apparent by considering the following description and appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals indicate corresponding parts in the various figures. It should be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as definitions of limitations. As used in the specification and claims, the singular forms of "a", "an" and "the" include plural referents unless the context clearly dictates otherwise. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Further advantages and details of embodiments or aspects of the present disclosure are explained in more detail below with reference to exemplary embodiments shown in the accompanying drawings, in which:

[0072] Figure 1 are diagrams of non-limiting embodiments or aspects of environments in which the systems, devices, products, apparatuses, and / or methods described herein may be implemented;

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

[0074] Figure 3A is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0075] Figure 3B is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0076] Figure 3C is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0077] Figure 3D is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0078] Figure 3E is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0079] Figure 3F is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0080] Figure 3G is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0081] Figure 3His a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0082] Figure 4A is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0083] Figure 4B is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0084] Figure 4C is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0085] Figure 4D is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0086] Figure 5A is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0087] Figure 5B is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0088] Figure 5C is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0089] Fig. 6A is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0090] Figure 6B is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0091] Figure 6C is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0092] Fig. 7A is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0093] Figure 7B is a perspective view of an implementation of a non-limiting example or aspect of a flow sensor system;

[0094] Figure 8 is a diagram of an example magnetic H-field around an antenna of a flow sensor system according to a non-limiting embodiment or aspect;

[0095] Fig. 9A is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0096] Fig. 9B is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0097] Fig. 9C is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0098] Fig.9D is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system;

[0099] Fig.9E1 is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system; and

[0100] Fig.9E2 is a flow chart of a non-limiting embodiment or aspect of a process for using a flow sensor system. DETAILED DESCRIPTION

[0101] It should be understood that the present disclosure may employ various alternative variations and step sequences, unless expressly indicated to the contrary. It should also be understood that the specific devices and processes illustrated in the accompanying drawings and described in the following specification are merely exemplary and non-limiting embodiments or aspects. Therefore, specific dimensions and other physical characteristics associated with the embodiments or aspects disclosed herein should not be considered limiting.

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

[0103] As used herein, the proximal end shall refer to the portion or direction that is farthest from or away from the patient (upstream), while the distal end shall refer to the portion or direction that is toward or located closest to the patient (downstream). In addition, pharmaceutical substances are used herein in an illustrative, non-limiting manner to refer to any substance that can be injected into a patient for any purpose. References to patients may refer to any organism, human or animal. References to clinicians may refer to anyone or anything that administers treatment, such as a nurse, doctor, machine intelligence, caregiver, or even self-treatment.

[0104] Unless explicitly described as such, any aspect, component, element, structure, action, step, function, instruction, etc. used in this document should not be construed as critical or essential. Moreover, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more" and "at least one." In addition, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and can be used interchangeably with "one or more" or "at least one." In the case of only meaning Figure 1 In the case of a term such as "one", "one" or similar language is used. Moreover, as used herein, the terms "having" and "having" are intended to be open-ended terms. In addition, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise.

[0105] As used herein, the terms "communication" and "transmission" refer to receiving or transmitting one or more signals, messages, commands or other types of data. For a unit (for example, any device, system or its parts) to communicate with another unit means that the unit can directly or indirectly receive data from another unit and / or transmit data to another unit. This can refer to a direct or indirect connection that is essentially wired and / or wireless. In addition, even if the data transmitted can be modified, processed, relayed and / or routed between the first and second units, the two units can also communicate with each other. For example, even if the first unit passively receives data and does not actively transmit data to the second unit, the first unit can also communicate with the second unit. As another example, if the intermediate unit processes the data from a unit and transmits the processed data to the second unit, the first unit can communicate with the second unit. It should be appreciated that many other arrangements are possible.

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

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

[0108] As used herein, the term "computing device" or "computer device" may refer to one or more electronic devices configured to communicate directly or indirectly with one or more networks or to communicate through one or more networks. A computing device may be a mobile device, a desktop computer, etc. In addition, the term "computer" may refer to any computing device that includes the necessary components for receiving, processing, and outputting data, and typically includes a display, a processor, a memory, an input device, and a network interface. An "application" or "application programming interface" (API) refers to computer code or other data stored on a computer-readable medium that can be executed by a processor to facilitate interaction between software components (such as a client-side front end and / or a server-side back end for receiving data from a client). An "interface" refers to a generated display, such as one or more graphical user interfaces (GUIs) with which a user can interact, either directly or indirectly (e.g., via a keyboard, mouse, touch screen, etc.).

[0109] As used herein, the term "server" may refer to or include one or more processors or computers, storage devices, or similar computer arrangements that are operated by or facilitate communication and processing by multiple parties in a network environment (such as the Internet), but it should be recognized that communications may be facilitated through one or more public or private network environments, and various other arrangements are possible. In addition, multiple computers, such as servers or other computerized devices, that communicate directly or indirectly in a network environment may constitute a "system." As used herein, the term "data center" may include one or more servers, or other computing devices, and / or databases.

[0110] As used herein, the term "mobile device" may refer to one or more portable electronic devices configured to communicate with one or more networks. As an example, a mobile device may include a cellular phone (e.g., a smart phone or a standard cellular phone), a portable computer (e.g., a tablet computer, a laptop computer, etc.), a wearable device (e.g., a watch, glasses, lenses, clothing, etc.), a personal digital assistant (PDA), and / or other similar devices. As used herein, the terms "client device" and "user device" refer to any electronic device configured to communicate with one or more servers or remote devices and / or systems. Client devices or user devices may include mobile devices, network-enabled appliances (e.g., network-enabled televisions, refrigerators, thermostats, etc.), computers, and / or any other device or system capable of communicating with a network.

[0111] As used herein, the term "application" or "application programming interface" (API) refers to a computer code, set of rules, or other data stored on a computer-readable medium that can be executed by a processor to facilitate interaction between software components (such as a client-side front end and / or a server-side back end for receiving data from a client). 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, etc.).

[0112] refer to Figure 1 , illustrates a non-limiting embodiment or aspect of an environment 100 in which systems, devices, products, apparatuses, and / or methods as described herein may be implemented. Figure 1 As shown in , environment 100 may include a flow sensor system 150 including a flow sensor 160 and a base 180, a medical device 102 (e.g., a syringe, etc.) including a short-range wireless communication tag 104, an IV line 106, a communication network 108 and / or a remote computing device 110.

[0113] The medical device 102 can be configured to be physically connected to the flow sensor 160, as described in more detail herein. The short-range wireless communication tag 104 can be attached to or integrated with the medical device 102, as described in more detail herein. In some non-limiting embodiments or aspects, the short-range wireless communication tag 104 includes one or more computing devices, chips, contactless transmitters, contactless transceivers, NFC transmitters / receivers, RFID transmitters / receivers, contact-based transmitters / receivers, etc. In some non-limiting embodiments or aspects, the short-range wireless communication tag 104 may include a device capable of communicating with the flow sensor 160 via a short-range wireless communication connection (e.g., a communication connection using an NFC protocol, a communication connection using a radio frequency identification (RFID), a communication connection using a RFID protocol, ... One or more devices that transmit and / or receive information to and / or from the base 180 (eg, a communication connection using a wireless technology standard, etc.). More details on non-limiting embodiments or aspects of the medical device 102 and the short-range wireless communication tag 104 are provided below. Figures 3A-3H , 4A-4D and 5A-5C are provided.

[0114] The flow sensor 160 can be configured to be removably, physically and / or electrically connected to the base 180, as described in more detail herein. In some non-limiting embodiments or aspects, the flow sensor 160 can be connected in-line with the IV line 106 between the fluid source and the patient. More details on non-limiting embodiments or aspects of the flow sensor 160 are provided below with reference to Figures 3A-3H , 4A-4D and 5A-5C are provided.

[0115] The base 180 may be configured to be removably, physically, and / or electrically connected to the flow sensor 160, as described in more detail herein. The base 180 may include one or more devices capable of receiving information and / or data from a remote computing device 110 (e.g., via a communication network 108, etc.) and / or transmitting information and / or data to a remote computing device 110 (e.g., via a communication network 108, etc.). For example, the base 180 may include a computing device, a mobile device, etc. In some non-limiting embodiments or aspects, the base 180 includes one or more computing devices, chips, contactless transmitters, contactless transceivers, NFC transmitters / receivers, RFID transmitters / receivers, contact-based transmitters / receivers, etc. In some non-limiting embodiments or aspects, the base 180 may include a communication device capable of connecting to the flow sensor 160 via a short-range wireless communication connection (e.g., a communication connection using an NFC protocol, a communication connection using radio frequency identification (RFID), a communication connection using One or more devices that transmit and / or receive information to and / or from the short-range wireless communication tag 104 (communication connection using wireless technology standards, etc.). In some non-limiting embodiments or aspects, the base 180 includes an integrated power source (not shown), such as a battery, etc. More details about non-limiting embodiments or aspects of the base 180 are provided below with reference to Figures 3A-3H , 4A-4D and 5A-5C are provided.

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

[0117] Remote computing device 110 may include one or more devices capable of receiving information and / or data from base 180 (e.g., via communication network 108, etc.) and / or transmitting information and / or data to base 180 (e.g., via communication network 108, etc.). For example, remote computing device 110 may include a computing device, a server, a group of servers, a mobile device, a group of mobile devices, etc.

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

[0119] Reference now Figure 2 , Figure 2 2 is a diagram of example components of device 200. Device 200 may correspond to base 180 and / or remote computing device 110. In some non-limiting embodiments or aspects, base 180 and / or remote computing device 110 may include at least one device 200 and / or at least one component of device 200. Figure 2 As shown in , device 200 may include a bus 202 , a processor 204 , a memory 206 , a storage component 208 , an input component 210 , an output component 212 , and / or a communication interface 214 .

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

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

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

[0123] The communication interface 214 may include components similar to a transceiver (e.g., a transceiver, a separate receiver and transmission source, etc.) that enable the device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of a wired and wireless connection. The communication interface 214 may allow the device 200 to receive information from another device and / or provide information to another device. For example, the communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

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

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

[0126] The memory 206 and / or storage component 208 may include a data store or one or more data structures (e.g., a database, etc.). The device 200 may be capable of receiving information from, storing information in, transmitting information to, or searching for information stored in the data store or one or more data structures in the memory 206 and / or storage component 208.

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

[0128] Figures 3A-3H , 4A-4D, and 5A-5C illustrate non-limiting embodiments or aspects of the flow sensor system 150. Figures 3A-3H , 4A-4D and 5A-5C, the flow sensor system 150 can include two main components that are assembled together before use: a flow sensor 160 and a base 180. In some non-limiting embodiments or aspects, the flow sensor 160 can be a single-use flow sensor that can be engaged with a reusable base 180.

[0129] The flow sensor system 150 can reduce medication errors at the bedside during bolus delivery. The flow sensor system 150 can provide a record and electronic measurement of bolus delivery, which allows monitoring of bolus delivery and automatic recording of bolus delivery as part of the patient's health record. The flow sensor system 150 can provide an alert when a bolus delivery that is inconsistent with the patient's medical record is about to occur.

[0130] The flow sensor system 150 can be a handheld instrument injection site with an interactive interface for syringe injection IV drug delivery and direct electronic medical record documentation. The base 180 can include a durable reusable reader base with a touch screen display and a separate disposable consumable flow sensor 160.

[0131] In some non-limiting embodiments or aspects, the flow sensor 160 may include a flow tube 162, at least one sensor 170 configured to characterize at least one property of a fluid in the flow tube 162, and / or a flow sensor electrical contact 172 in electrical communication with the at least one sensor 170. The flow tube 162 may include a fluid inlet 163 at a first end of the flow tube 162, a fluid outlet 164 at a second end of the flow tube 162 opposite the first end of the flow tube 162, a fluid injection port 165 between the first end and the second end of the flow tube 162, and a valve 166 (e.g., a manual valve, etc.) configured to control the flow of fluid in the flow tube 162.

[0132] In some non-limiting embodiments or aspects, the base 180 may include one or more processors 204, a base electrical contact 192 in electrical communication with the one or more processors 204, a short-range wireless communication device (e.g., a communication interface 214, a near field communication (NFC) receiver, etc.), and / or a display 194 (e.g., an input component 210, an output component 212, a touch screen display configured to receive user input from a user, etc.). When the flow sensor is connected (e.g., connected, attached, mounted, etc.) to the base 180, the flow sensor electrical contact 172 may be in electrical communication with the base electrical contact 192.

[0133] In some non-limiting embodiments or aspects, the base 180 includes an opening 196 configured to receive the flow sensor 160 , and the flow sensor 160 is configured to slidably engage the opening 196 of the base 180 .

[0134] In some non-limiting embodiments or aspects, at least one sensor 170 may include a first ultrasonic transducer or piezoelectric element 170 disposed at an upstream position of the flow tube 162, and a second ultrasonic transducer or piezoelectric element 170 disposed at a downstream position of the flow tube 162. The first and second piezoelectric elements 170 may be configured to transmit a flow signal indicating the flow of a fluid (e.g., a fluid medication, etc.) in the flow tube 162. In some non-limiting embodiments or aspects, the first ultrasonic transducer or piezoelectric element and the second ultrasonic transducer or piezoelectric element 170 are annular in shape and surround the flow tube 162 at respective mounting points. In some non-limiting embodiments or aspects, the first ultrasonic transducer or piezoelectric element and the second ultrasonic transducer or piezoelectric element 170 are mounted to be separated from each other by a preselected distance. When the flow sensor 160 is connected to the base 180, the first and second ultrasonic transducers or piezoelectric elements 170 may be in electrical communication with one or more processors 204 (e.g., via electrical contacts 172, 192, etc.). For example, the base 180 may interact with the first and second ultrasonic transducers or the piezoelectric element 170 in the flow sensor 160 to measure the displacement of the fluid passing through the flow sensor 160 .

[0135] In some non-limiting embodiments or aspects, the valve 166 can be configured to switch between a plurality of different states to control at least one of the following: the flow of fluid between the fluid inlet 163 and the fluid outlet 164, the flow of fluid between the fluid inlet 163 and the fluid injection port 165, the flow of fluid between the fluid injection port 165 and the fluid outlet 164, or any combination thereof. For example, the valve 166 can include a three-way stopcock valve, etc.

[0136] In some non-limiting embodiments or aspects, the one or more processors 204 may be programmed and / or configured to automatically detect the connection of the flow sensor 160 to the base 180. For example, when a user attaches the flow sensor 160 to the reader base 180, the reader base 180 automatically detects the installation of the flow sensor 160. As an example, a mechanical button or switch on the base 180 in electrical communication with the one or more processors may be actuated by the connection / disconnection of the flow sensor 160 to the base 180 to send a signal to the one or more processors 204 indicating the connection / disconnection status of the flow sensor 160 to the base 180.

[0137] In some non-limiting embodiments or aspects, one or more processors 204 are programmed and / or configured to automatically detect the connection of the syringe 102 to the fluid injection port 165 of the flow sensor 160. For example, when a user inserts a syringe 102 with a needleless Luer connector into the fluid injection port 165, the reader base 180 can automatically detect the presence of the syringe connection to the fluid injection port 165 syringe and initiate decoding of the tag 104 (e.g., via a short-range wireless communication device, etc.) to record the information content of the tag 104 (e.g., drug information, etc.). As an example, the flow sensor system 150 may include an electronic and mechanical interface that interacts with the syringe 102, and when the syringe 102 is inserted into the fluid injection port 165, detects the presence of the syringe 102 when the user inserts the syringe 102. In such an example, a mechanical button or switch on the flow sensor 160 that is electrically connected to one or more processors (e.g., via electrical contacts 172 and 192, etc.) can be actuated by the connection / disconnection of the syringe 102 to the fluid injection port 165 to send a signal to the one or more processors 204 indicating the connection / disconnection status of the syringe 102 to the fluid injection port 165. In some non-limiting embodiments or aspects, a tag or label 104 that can include an NFC tag embedded in the tag or label 104 can be manually placed on the body of the syringe 102 using a standard label printer. For example, a label printer can be used to encode the NFC tag when printing. Additionally or alternatively, a separate NFC tag encoding unit can be used to perform NFC encoding.

[0138] In some non-limiting embodiments or aspects, the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag 104 on the syringe 102 via a short-range wireless communication connection when the short-range wireless communication tag 104 is brought into the communication range of the short-range wireless communication device. In some non-limiting embodiments or aspects, the short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag 104 on the syringe 102 via a short-range wireless communication connection in response to the base 180 detecting the connection of the syringe 102 to the fluid injection port 165. For example, when the tag 104 is placed radially near the antenna of the short-range wireless communication device in the base 180, the tag 104 can be detected by using NFC. As an example, the base 180 can include an integrated NFC antenna that is radially positioned to record the syringe tag tag 104 and read and decode the encoded information therefrom. In such an example, the NFC antenna and tag indicia are optimized to eliminate false detection of adjacently positioned syringes having NFC tag indicia (e.g., an NFC antenna radially mounted in base 180 and tag indicia 104 on the syringe barrel of syringe 102 can be used to transmit encoded tag information from the syringe tag indicia 104 to the reader base 180, etc.).

[0139] In some non-limiting embodiments or aspects, the one or more processors 204 can be programmed and / or configured to automatically detect the state of the valve 166 when the flow sensor 160 is connected to the base 180. For example, when the user manually switches the state or position of the valve 166, the base 180 can automatically determine the state or position of the valve 166. As an example, an electronic and / or mechanical interface can interact with the valve 166 to monitor the valve position or state. In such an example, a mechanical button or switch on the flow sensor 160 (e.g., via electrical contacts 172 and 192, etc.) that is electrically connected to the one or more processors can be actuated by changing the position or state of the valve 166 to send a signal to the one or more processors 204 indicating the state or position of the valve 166 (e.g., indicating that fluid flow is allowed between the fluid inlet 163 and the fluid outlet 164, between the fluid inlet 163 and the fluid injection port 165, between the fluid injection port 165 and the fluid outlet 164, or any combination thereof, etc.).

[0140] In some non-limiting embodiments or aspects, the one or more processors 204 are programmed and / or configured to determine whether to record information associated with at least one property of the fluid in the flow tube 162 based on the detected state of the valve 166. For example, a user can switch the state or position of the valve 166 to enable recording of flow measurements and / or allow IV fluid flow. As an example, when IV fluid is drawn into the syringe 102 and then subsequently injected through the flow sensor 160, the one or more processors 204 of the base 180 can determine when to bookmark the flow measurement and ignore the IV fluid flow and redundant volume measurements.

[0141] In some non-limiting embodiments or aspects, the flow sensor 160 is inserted in line with the IV line 106 between the fluid source and the patient. For example, the disposable flow sensor 160 can be inserted in line with the IV line 106 so that the IV fluid can pass directly through the patient extension line catheter. In some non-limiting embodiments or aspects, the valve 166 is configured to enable the syringe 102 to extract IV fluid from the IV line 106 and pass the extracted IV fluid through the flow sensor 160 to push the fluid to flush the extension line and flow sensor 160 of the previously delivered volume of the drug. In some non-limiting embodiments or aspects, the flow sensor 160 can be integrated into the IV 106 (e.g., integrated into the IV extension set tubing, etc.) without the need for a separate removable connector. In some non-limiting embodiments or aspects, the fluid flow stopcock valve can be positioned in line before and / or after the flow sensor 160, and / or additional functionality can be developed within the interactive display 194 of the base 180 for incorporating workflow operations. For example, by positioning flow sensor 160 in-line with IV line 106, dead band issues due to lack of flushing associated with a parallel connection may be addressed.

[0142] In some non-limiting embodiments or aspects, base 180 includes an optical scanner configured to read a bar code label (eg, a patient wristband bar code label, a bar code label on flow sensor 160 , etc.).

[0143] In some non-limiting embodiments or aspects, display 194 includes a touch screen display configured to receive user input from a user. For example, display 194 may include an interactive graphical user interface configured to display the current state of the internal functions of reader base 180, the current state of the injection site, and / or prompts for user interaction, and reader base 180 may interact with the user via a touch screen display, audio, voice commands, tactile feedback, etc. (e.g., to prompt the user of the current state and request user input, etc.). Therefore, by incorporating display 194 into base 180, the user does not need to move their attention away from base 180 to interact with display 194.

[0144] In some non-limiting embodiments or aspects, the base 180 includes a wireless communication device configured to communicate information associated with at least one property of the fluid in the flow tube 162 to the remote computing device 110. For example, the base 180 can communicate information and / or data with the remote computing device 110 to record a drug delivery event in a patient medical record (e.g., a patient medical record associated with a patient wristband barcode label scanned by an optical scanner of the base 180, etc.).

[0145] Reference now Figure 4A ,5A , 6A-6C, 7A, 7B and 8, in some non-limiting embodiments or aspects, the short-range wireless communication device of the base 180 may include a curved coil antenna 600.

[0146] The size of the syringe 102 can vary (e.g., the syringe size can range from 1 mL to 60 mL, etc.). The location of the short-range wireless communication tag 104 on the syringe 102 can vary. For example, the user can attach the short-range wireless communication tag 104 to various locations on the body of the syringe 102. The variability between the location of the tag 104 and the size of the syringe 102 combined with the curvature of the main body syringe 102 can make it more difficult to read the encoded data from the tag 104 and / or place a considerable burden on the user. For example, HF RFID / NFC works in the following manner, that is, generating inductively coupled magnetic waves in the 13.56 MHz range to power the HF RFID / NFC tag, thereby transmitting the encoded information back to the transmitting coil antenna. As an example, the transmitting coil antenna should transmit enough energy to power the tag 104, and the tag coil antenna in the tag 104 should receive enough energy to power up and transmit the encoded information stored in the tag 104 back to the transmitting coil antenna. The transmitting coil antenna can be flat and the tag 104 can be placed parallel to the transmitting coil antenna to power the tag 104 when the tag 104 receives sufficient energy. The received energy can be based on the distance of the tag 104 to the transmitting coil antenna and / or the orientation of the transmitting coil antenna relative to the tag 104 (e.g., the offset and / or angle of the tag 104 facing the transmitting coil antenna, etc.). For example, as the angle between the coil antenna of the tag 104 and the transmitting coil antenna becomes closer to 90 or 270 degrees, the antenna energy received by the tag 104 can decrease to zero. As an example, the formula for calculating the amount of energy received by the tag 104 from the transmitting coil antenna can be defined according to cosine (angle). Therefore, if the angle between the transmitting coil antenna and the coil antenna of the tag 104 reaches 90 degrees or 270 degrees, the energy received by the tag 104 is zero, and the tag 104 cannot be powered. In this way, if the tag 104 is on the syringe 102 and the tag 104 can be placed anywhere on the syringe 102 by the user, then the angle may be close enough or at the zero energy point that the data encoded in the tag 104 cannot be read by the short-range wireless communication device.

[0147] Non-limiting embodiments or aspects of the flow sensor system 150 including the curved coil antenna 600 can reduce and / or eliminate the 90 degree and / or 270 degree angles between the transmitting coil antenna of the short-range wireless communication device of the base 180 and the markings 104 on the syringe 102 by surrounding and / or encircling the syringe 102 with the curved coil antenna 600. For example, and with reference to Figure 8, the curved coil antenna 600 can enable magnetic waves to be transmitted from the short-range wireless communication device of the base 180 in a radial manner relative to the syringe 102 when the syringe 102 is connected to the flow sensor 160 and the flow sensor 160 is connected to the base 180, thereby covering a larger area of ​​the syringe 102 (e.g., depending on the circumferential area of ​​the curved coil antenna 600, the acceptance criteria for a successful read, etc.). As an example, the curved coil antenna 600 can enable magnetic waves to be transmitted radially from the short-range wireless communication device of the base 180 to surround an NFC HF RFID tag on a circular syringe. In contrast, a flat NFC coil antenna may cause the magnetic waves to be transmitted orthogonally to the coil antenna, which may cause the NFC HF RFID tag to be misaligned with the transmitted magnetic waves (e.g., especially if the tag is 90 degrees to the wave, etc.), thereby not being powered and not transmitting the information encoded on the tag back to the transmitting NFC coil antenna. Thus, the curved NFC coil antenna may enable magnetic waves to be transmitted in more directions relative to an NFC HF RFID tag (e.g., for NFC communication based on NFC standards of ISO 14443 and / or ISO 15693 describing physical layer technology and protocol layer technology, etc.), thereby reducing and / or preventing 90 and / or 270 degree angles between the transmitting coil antenna and the tag.

[0148] In some non-limiting embodiments or aspects, the fluid injection port 165 of the flow sensor 160 may extend from the flow tube 162 in a first direction parallel to the longitudinal axis of the fluid injection port 165, and the curved coil antenna 600 in the short-range wireless communication device of the base 180 may be radially bent relative to the longitudinal axis of the fluid injection port 165 when the flow sensor 160 is connected to the base 180. For example, the fluid injection port 165 may be configured to be connected to the syringe 102, and when the syringe 102 is connected to the fluid injection port 165 of the flow sensor 160 and the flow sensor 160 is connected to the base 180, the curved coil antenna 600 may be radially bent around the syringe 102 and / or extend in a first direction parallel to the longitudinal axis of the fluid injection port 165.

[0149] In some non-limiting embodiments or aspects, for example Figure 4A and 6A -6C, the curved coil antenna 600 extends in a direction parallel to the plane defined by the face of the display 194 of the base 180 (e.g., when the syringe 102 is connected to the flow sensor 160 and the flow sensor 160 is connected to the base 180, in a direction parallel to the longitudinal axis of the syringe 102, etc.). In some non-limiting embodiments or aspects, for example, Figure 5A, the curved coil antenna 600 extends in a direction that is not parallel to (e.g., perpendicular to) a plane defined by a face of the display 194 of the base 180 (e.g., when the syringe 102 is connected to the flow sensor 160 and the flow sensor 160 is connected to the base 180, in a direction perpendicular to the longitudinal axis of the syringe 102, etc.). In such an example, when the syringe 102 is connected to the flow sensor 160 and the flow sensor 160 is connected to the base 180, the curved coil antenna 600 can at least partially surround the syringe 102. In some non-limiting embodiments or aspects, the curvature of the curved coil antenna can correspond to the circumferential area of ​​a 60 mL syringe, etc.

[0150] Reference now Figures 3A-3H and 9A-9E, Figures 3A-3H 9A-9E are flow charts of non-limiting embodiments or aspects of a process for using a flow sensor system. In some non-limiting embodiments or aspects, one or more steps of the process are performed (e.g., completely, partially, etc.) by the flow sensor system 150 (e.g., one or more devices of the flow sensor system 150, etc.). In some non-limiting embodiments or aspects, one or more steps of the process are performed (e.g., completely, partially, etc.) by another device or group of devices that is separate from or includes the flow sensor system 150, such as the remote computing device 110 (e.g., one or more devices of a system of the remote computing device 110, etc.) (e.g., completely, partially, etc.).

[0151] like Fig. 9A As shown in FIG. 5 , at step WS5.2, the process of using the flow sensor system includes scanning a flow sensor tag attached to a disposable flow sensor to decode a flow sensor identifier associated with the flow sensor. For example, for a disposable flow sensor 160 (e.g., Fig. 9A -9E) of the optical scanner of the base 180 (e.g., Fig. 9A -9E) can scan a flow sensor tag (e.g., a flow sensor barcode, etc.) attached to the disposable flow sensor to decode a flow sensor identifier associated with the flow sensor. As an example, a barcode scan of the disposable flow sensor 160 enables the base 180 (and / or the remote computing system 110) to determine whether the disposable flow sensor 160 has been used, and if so, by which patient.

[0152] like Fig. 9AAs shown in, at step WS4, the process of using the flow sensor system includes scanning a patient tag attached to the patient to decode a patient identifier associated with the patient. For example, an optical scanner of the base 180 for the disposable flow sensor 160 can scan a patient tag (e.g., a patient wristband, a patient barcode, etc.) attached to the patient to decode a patient identifier associated with the patient. As an example, a smart device (e.g., a base 180, etc.) can be used to electronically scan each of a smart IV consumable (e.g., a disposable flow sensor 160, etc.) and a patient wristband provided by an EMR vendor, for example, by a barcode scanner. The smart device can transmit patient identifier information (e.g., a patient MRN) and a unique identification number of the smart IV consumable to a virtual server (e.g., a remote computing device 110, etc.) on a hospital network. The virtual server can use the patient identifier information to generate a two-way link to an application on a hospital information system associated with the patient associated with the functions of the smart device and the smart consumable. Once a two-way link is established, the virtual server can associate the link with the unique identification number of the smart IV consumable, and if the smart device is disassociated, the smart device or a new different device can be reassociated by scanning the smart consumable. In contrast, if the patient is associated only electronically, such as by associating the patient to a barcode reader, then if the device is no longer usable (e.g., battery drained, etc.), then re-association may need to be performed by scanning the patient's wristband, and if the wristband is inaccessible (e.g., during surgery, etc.), then manual entry of the patient identifier may need to be performed, which may be error-prone. For example, the device may need to associate the device with the patient record by having the EMR assign the case to the device, manually selecting the patient through a user interface on the device, or associating the smart device directly with the patient through an electronic scan, or otherwise. In addition, if not properly disassociated, the device may also be at risk of having incorrect patient record information used for the wrong patient record.

[0153] like Fig. 9A As shown in FIG. 5 , at step WS5.3, the process of using the flow sensor system includes connecting the disposable flow sensor to the base. For example, the disposable flow sensor 160 can be connected to the base 180.

[0154] like Fig. 9A As shown in , at step WS5.1, the process of using the flow sensor system includes integrating a disposable flow sensor into an IV line. For example, the disposable flow sensor 160 can be integrated into the IV line 106.

[0155] In some non-limiting embodiments or aspects, and now with reference to Fig. 9B, the disposable flow sensor 160 is integrated into the IV line 106 prior to scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor 160 to the base 180. For example, integrating the disposable flow sensor 160 into the IV line 106 prior to scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor 160 to the base 180 may enable a clinician to associate a patient when performing other positive patient identifications and / or scan and attach the disposable flow sensor 160 in one or more consecutive steps, which, for example, adds value when setting up a patient for a procedure in an operating room. As an example, scanning the patient ID prior to connection may ensure that the IV line 106 does not prevent a user from scanning the patient ID, which may be desirable for an outpatient patient who is constructing a new IV line with the disposable flow sensor 160 in place for a procedure.

[0156] In some non-limiting embodiments or aspects, and referring now to Fig. 9C , integrating the disposable flow sensor 160 into the IV line 106 after scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor 160 to the base 180. For example, integrating the disposable flow sensor 160 into the IV line 106 after scanning the flow sensor tag, scanning the patient tag, and connecting the disposable flow sensor 160 to the base 180 may enable the clinician to prepare the base 180 and disposable flow sensor 160 prior to interacting with the patient and / or a pre-existing IV, which may add value when the clinician has time prior to the arrival of an inpatient without requiring a pre-existing IV preservation step to be performed while the patient is present.

[0157] like Fig. 9A As shown in , at steps WS4, WS5.2, and / or WS5.4, the process of using the flow sensor system includes transmitting the flow sensor identifier and the patient identifier to the remote computing device and associating the flow sensor identifier with the patient identifier. For example, the base 180 can transmit the flow sensor identifier and the patient identifier to the remote computing device 110, and the remote computing device 110 can associate the flow sensor identifier with the patient identifier in the database.

[0158] In some non-limiting embodiments or aspects, and now with reference to Fig.9D, the base 180 may transmit a request for the status of the disposable flow sensor 160 associated with the flow sensor identifier to the remote computing device 110, and receive an indication of the status of the disposable flow sensor 160 associated with the flow sensor identifier from the remote computing device 110. For example, the indication of the status of the disposable flow sensor 160 may include an indication of whether the flow sensor identifier of the disposable flow sensor 160 is associated with the patient identifier of the patient.

[0159] In some non-limiting embodiments or aspects, and still with reference to Fig.9D , the base 180 can transmit the base identifier associated with the base 180 to the remote computing device 110 in a request for the status of the disposable flow sensor 160 associated with the flow sensor identifier, and the remote computing device 110 can associate the base identifier with the flow sensor identifier and the patient identifier.

[0160] like Fig. 9A As shown in , at steps WS4 and / or WS6, the process of using the flow sensor system includes transmitting a request for information associated with a patient associated with a patient identifier, receiving information associated with the patient, and displaying information associated with the patient. For example and also referring to FIG. 9E, the base 180 can transmit a request for information associated with a patient associated with a patient identifier to the remote computing device 110, receive information associated with the patient from the remote computing device 110, and display information associated with the patient through a display.

[0161] In some non-limiting embodiments or aspects, the information associated with the patient includes at least one of a list of drug allergies associated with the patient and a list of drug dosages to be administered for the patient.

[0162] In some non-limiting embodiments or aspects, and still referring to FIG. 9E , the short-range wireless communication device of the base 180 can scan the short-range wireless communication tag 104 attached to the syringe 102 to decode the drug identifier associated with the drug in the syringe 102, and the base 180 can compare the drug identifier with at least one of a list of drug allergies associated with the patient and a list of drug doses to be administered for the patient. For example, the display 194 of the base 180 can display a reminder associated with administering the drug to the patient based on the comparison. In some non-limiting embodiments or aspects, the short-range wireless communication device includes a near field communication (NFC) receiver, and wherein the short-range wireless communication tag includes an NFC tag.

[0163] Thus, non-limiting embodiments or aspects of a process using a flow sensor system may enable more steps to be performed at the patient's point of care, given the advantages provided over methods that require interaction with an EMR screen. Additionally, non-limiting embodiments or aspects of a process using a flow sensor system may enable a patient to be associated with a smart consumable that is attached to the patient's IV line rather than a separate electronic device (e.g., base 180, etc.), which provides a higher level of confidence that the device data is associated with the correct patient because the smart IV consumable is directly attached to the patient (via an IV), and this may enable the smart device to be exchanged with another device that may be associated with the patient by scanning the smart consumable rather than requiring a rescan of the patient's wristband.

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

Claims

1. A system comprising: Flow sensor, including: a flow tube including a fluid inlet at a first end of the flow tube, a fluid outlet at a second end of the flow tube opposite the first end of the flow tube, a fluid injection port between the first end and the second end of the flow tube, and a valve configured to control the flow of fluid in the flow tube; at least one sensor configured to characterize at least one property of the fluid in the flow tube; and a flow sensor electrical contact in electrical communication with the at least one sensor; and a base configured to be connected to the flow sensor, wherein the base comprises: one or more processors; a base electrical contact in electrical communication with the one or more processors; Short-range wireless communications equipment; and A display wherein the flow sensor electrical contacts are in electrical communication with the base electrical contacts when the flow sensor is connected to the base.

2. The system of claim 1, wherein: The valve is configured to switch between multiple different states to control at least one of the following: flow of fluid between a fluid inlet and a fluid outlet, flow of fluid between a fluid inlet and a fluid injection port, flow of fluid between a fluid injection port and a fluid outlet, or any combination thereof.

3. The system of claim 1, wherein: The one or more processors are programmed to automatically detect the state of the valve when the flow sensor is connected to the base.

4. The system of claim 1, wherein: The one or more processors are programmed to determine whether to record information associated with the at least one property of the fluid in the flow tube based on the detected valve state.

5. The system of claim 1, wherein: The one or more processors are programmed to automatically detect connection of the flow sensor to the base.

6. The system of claim 1, wherein: The one or more processors are programmed to automatically detect connection of a syringe to the fluid injection port of the flow sensor.

7. The system of claim 1, wherein: The short-range wireless communication device is configured to automatically communicate with the short-range wireless communication tag on the syringe when the short-range wireless communication tag on the syringe is brought within the communication range of the short-range wireless communication device.

8. The system of claim 1, wherein: The fluid injection port is configured to connect to a syringe, and wherein the short-range wireless communication device includes a bent coil antenna, and wherein the bent coil antenna radially bends around a portion of the syringe when the syringe is connected to the fluid injection port of the flow sensor and the flow sensor is connected to the base.

9. The system of claim 8, wherein: When a syringe is connected to the fluid injection port of the flow sensor and the flow sensor is connected to the base, the curved coil antenna extends in a first direction parallel to a longitudinal axis of the syringe.

10. The system of claim 1, wherein: The short-range wireless communication device includes a Near Field Communication (NFC) receiver.

11. The system of claim 1, wherein: The base also includes a wireless communication device configured to transmit information associated with the at least one property of the fluid in the flow tube to a remote computing device.

12. The system of claim 1, wherein: The base also includes an optical scanner configured to read the bar code label.

13. The system of claim 1, wherein: The base also includes an opening configured to receive the flow sensor, and wherein the flow sensor is configured to slideably engage the opening of the base.

14. A system comprising: a flow sensor, including a flow sensor identifier that specifically identifies the flow sensor; A base configured to be connected to the flow sensor, wherein the base comprises: a scanner operable to scan a flow sensor identifier; wireless communications equipment; and One or more processors programmed to: transmitting the flow sensor identifier to a remote computing device; receiving a status of the flow sensor from a remote computing device, wherein the status includes an indication of whether the flow sensor has been previously used; and A reminder is generated based at least in part on the received status.

15. The system of claim 14, wherein: The base includes a base identifier that identifies the base.

16. The system of claim 15, wherein: The one or more processors are programmed to transmit the flow sensor identifier and the base identifier to the remote computing device.

17. The system of claim 16, further comprising the remote computing device, wherein: The remote computing device is programmed to associate the base identifier with the flow sensor identifier in a database.

18. The system of claim 17, wherein: The one or more processors are programmed to transmit the patient identifier to the remote computing device, and wherein the remote computing device is programmed to associate the base identifier with the flow sensor identifier and the patient identifier in a database.

Images