FLOW SENSOR SYSTEM.

Abstract

A system may include a flow sensor and a base. The flow sensor may be configured to connect to the base. The flow sensor may include a flow tube with a fluid inlet at one end, a fluid outlet at the other end opposite the first, and a fluid injection port between the first and second ends. The base may include a short-range wireless communication device with a curved-coil antenna.

Description

FLOW SENSOR SYSTEM REFERENCE TO RELATED APPLICATION This application claims priority to U.S. Provisional Application Serial No. 62 / 966,281, entitled Flow Sensor System, filed January 27, 2020, the full disclosure of which is incorporated by reference in its entirety herein. BACKGROUND 1. Field The present disclosure generally relates to a flow sensor system and, in some non-limiting embodiments or aspects, to a flow sensor system for detecting a flow of a fluidic medicament. 2. Technical considerations There is a need to reduce medication errors at the bedside during bolus administration. It is advantageous to provide a record of, and electronically measure, bolus administration, allowing for monitoring and automatic documentation of bolus administration as part of the patient's medical record. Additionally, it is advantageous to provide alerts when a bolus administration inconsistent with a patient's medical record is about to occur. BRIEF DESCRIPTION The non-limiting aspects or realizations are set out in the following numbered clauses: Clause 1. A system including: a 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 a fluid in the flow tube; at least one sensor configured to characterize at least one attribute of the fluid in the flow tube; and an electrical contact of the flow sensor in electrical communication with the at least one sensor; and a base configured to be connected to the flow sensor, wherein the base includes: one or more processors; a base electrical contact in electrical communication with one or more processors; a short-range wireless communication device;and a display, wherein the electrical contact of the flow sensor is in electrical communication with the electrical contact of the base when the flow sensor is connected to the base.; LfrZAnn / zznz / E / YiAi Clause 2. The system of clause 1, wherein the valve is configured to transition between a plurality of different states to control at least one of: fluid flow between the fluid inlet and the fluid outlet, fluid flow between the fluid inlet and the fluid injection port, fluid flow between the fluid injection port and the fluid outlet, or any combination thereof. Clause 3. The system of any of clauses 1 and 2, wherein one or more processors are programmed and / or configured to automatically detect a state of the valve when the flow sensor is connected to the base. Clause 4. The system of any of clauses 1-3, wherein one or more processors are programmed and / or configured to determine whether to record information associated with the at least one attribute of the fluid in the flow tube based on the detected state of the valve. Clause 5. The system of any of clauses 1-4, wherein one or more processors are programmed and / or configured to automatically detect a connection of the flow sensor to the base. Clause 6. The system of any of clauses 1-5, wherein one or more processors are programmed and / or configured to automatically detect a connection of a syringe to the fluid injection port of the flow sensor. Clause 7. The system of any of clauses 1-6, wherein the display includes a touch screen configured to receive input from a user. Clause 8. The system of any of clauses 1-7, wherein the flow sensor is inserted in line with an IV line between a fluid source and a patient. Clause 9. The system of any of clauses 1-8, wherein the short-range wireless communication device is configured to automatically communicate with a short-range wireless communication tag on a syringe via a short-range wireless communication connection when the short-range wireless communication tag is brought within a communication range of the short-range wireless communication device. Clause 10. The system of any of clauses 1-9, wherein the short-range wireless communication device includes a near field communication (NFC) receiver. Clause 11. The system of any of clauses 1-10, wherein the base further includes a wireless communication device configured to communicate information associated with the at least one attribute of the fluid in the flow tube to a computing device. LfrZAnn / zznz / E / YiAi remote. Clause 12. The system of any of clauses 1-11, wherein the base further includes an optical scanner configured to read a barcode label. Clause 13. The system of any of clauses 1-12, wherein the base further includes an opening configured to receive the flow sensor, and wherein the flow sensor is configured to slideably engage the opening of the base. Clause 14. A 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 a fluid in the flow tube; at least one sensor configured to characterize at least one attribute of the fluid in the flow tube; an electrical contact of the flow sensor in electrical communication with the at least one sensor. Clause 15. The flow sensor of clause 14, wherein the valve is configured to transition between a plurality of different states to control at least one of: fluid flow between the fluid inlet and the fluid outlet, fluid flow between the fluid inlet and the fluid injection port, fluid flow between the fluid injection port and the fluid outlet, or any combination thereof. 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. Clause 17. A base for a flow sensor, including: one or more processors; a base electrical contact in electrical communication with one or more processors; a short-range wireless communication device; and a display, wherein the base sensor electrical contact is in electrical communication with at least one sensor of the flow sensor when the flow sensor is connected to the base. Clause 18. The basis of clause 17, wherein one or more processors are programmed and / or configured to automatically detect a state of a flow sensor valve when the flow sensor is connected to the base. Clause 19. The basis of any of clauses 17 and 18, wherein one or more processors are programmed and / or configured to determine whether to record information associated with at least one attribute of a fluid detected by the flow sensor based on the detected state of the valve. Clause 20. The basis of any of clauses 17-19, wherein one or more processors are programmed and / or configured to automatically detect a connection LfrZAnn / zznz / E / YiAi from flow sensor to base. Clause 21. The basis of any of clauses 17-20, wherein one or more processors are programmed and / or configured to automatically detect a connection of a syringe to the flow sensor. Clause 22. The basis of any of clauses 17-21, wherein the display includes a touch screen configured to receive input from a user. Clause 23. The basis of any of clauses 17-22, wherein the short-range wireless communication device is configured to automatically communicate with a short-range wireless communication tag on a syringe via a short-range wireless communication connection when the short-range wireless communication tag is brought within a communication range of the short-range wireless communication device. Clause 24. The basis of any of clauses 17-23, wherein the short-range wireless communication device includes a near field communication (NFC) receiver. Clause 25. The base of any of clauses 17-24, wherein the base further includes a wireless communication device configured to communicate information associated with the at least one attribute of the fluid in the flow tube to a remote computing device. Clause 26. The basis of any of clauses 17-25, wherein the basis further includes an optical scanner configured to read a barcode label. Clause 27. The base of any of clauses 17-26, wherein the base further includes an opening configured to receive the flow sensor, and wherein the flow sensor is configured to slideably engage the opening of the base. Clause 28. A system including: a 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, wherein the fluid injection port extends from the flow tube in a first direction parallel to a longitudinal axis of the fluid injection port; and a base configured to be connected to the flow sensor, wherein the base includes: a short-range wireless communication device including a curved coil antenna, wherein the curved coil antenna is radially curved with respect to the longitudinal axis of the fluid injection port when the flow sensor is connected to the base. LfrZAnn / zznz / E / YiAi Clause 29. The system of clause 28, wherein the curved coil antenna extends in the first direction parallel to the longitudinal axis of the fluid injection port. Clause 30. The system of any of clauses 28-30, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen. Clause 31. The system of any of clauses 28-30, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the screen. Clause 32. The system of any of clauses 28-31, wherein the fluid injection port is configured to be connected to a syringe, and 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 curved coil antenna is curved radially around the syringe. Clause 33. The system of any of clauses 28-32, wherein a short-range wireless communication tag is attached to a syringe body. Clause 34. The system of 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 is brought within a communication range of the short-range wireless communication device. Clause 35. The system of any of clauses 28-34, wherein the short-range wireless communication device receives information associated with a medication included in the syringe from the short-range wireless communication tag when the short-range wireless communication tag is placed within communication range of the short-range wireless communication device. Clause 36. The system of any of clauses 28-35, wherein the short-range wireless communication device includes a near field communication (NFC) receiver. Clause 37. A system including: a 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, wherein the fluid injection port is configured to connect to a syringe; and a base configured to connect to the flow sensor, wherein the base includes: a fluid inlet device LfrZAnn / zznz / E / YiAi short-range wireless communication including a curved 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 curved coil antenna radially curves around the syringe. Clause 38. The system of clause 37, wherein the curved coil antenna extends in a first direction parallel to a longitudinal axis 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. Clause 39. The system of any of clauses 37 and 38, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen. Clause 40. The system of any of clauses 37-39, wherein the base further includes a shield, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the shield. Clause 41. The system of any of clauses 27-40, wherein a short-range wireless communication tag is attached to a syringe body. Clause 42. The system of 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 is brought within a communication range of the short-range wireless communication device. Clause 43. The system of any of clauses 27-42, wherein the short-range wireless communication device receives information associated with a medication included in the syringe from the short-range wireless communication tag when the short-range wireless communication tag is placed within communication range of the short-range wireless communication device. Clause 44. The system of any of clauses 27-43, wherein the short-range wireless communication device includes a near field communication (NFC) receiver. Clause 45. A base for a flow sensor, including: 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. LfrZRnn / zznz / E / YiAi Clause 46. The basis of clause 45, wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen. Clause 47. The basis 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 screen. Clause 48. The system of any of clauses 45-47, wherein the curved coil antenna radially curves around a syringe when the syringe is connected to the flow sensor and the flow sensor is connected to the base. Clause 49. The system of any of clauses 45-48, wherein a short-range wireless communication tag is attached to a syringe body. Clause 50. The system of 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 is brought within a communication range of the short-range wireless communication device. Clause 51. The system of any of clauses 45-50, wherein the short-range wireless communication device receives information associated with a medication included in the syringe from the short-range wireless communication tag when the short-range wireless communication tag is placed within communication range of the short-range wireless communication device. Clause 52. The system of any of clauses 45-51, wherein the short-range wireless communication device includes a near field communication (NFC) receiver. Clause 53. A method including: scanning, with an optical scanner of a base for a disposable flow sensor, a flow sensor label attached to the disposable flow sensor to decode a flow sensor identifier associated with the flow sensor; scanning, with the optical scanner of the base for the disposable flow sensor, a patient label attached to a patient to decode a patient identifier associated with the patient; connecting the disposable flow sensor to the base. Clause 54. The method of clause 53, which further includes: integrating the disposable flow sensor into an IV line. Clause 55. The method of any of clauses 53 and 54, wherein the disposable flow sensor is integrated into the IV line before scanning the flow sensor label, scanning the patient label and connecting the disposable flow sensor to the class. LfrZAnn / zznz / E / YiAi 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 label, scanning the patient label, and connecting the disposable flow sensor to the class. Clause 57. The method of any of clauses 53-56, further including: communicating, with the class, the flow sensor identifier and the patient identifier to a remote computing device; associating, with the remote computing device in a data class, the flow sensor identifier with the patient identifier. Clause 58. The method of any of clauses 53-57, further including: communicating, with the class, to a remote computing device, a request for a state of the flow sensor associated with the flow sensor identifier; receiving, with the class, from the remote computing device, an indication of a state of the flow sensor associated with the flow sensor identifier, wherein the indication of the state 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. Clause 59. The method of any of clauses 53-58, further including: communicating, with the base, to the remote computing device, a base identifier associated with the base in the flow sensor status request associated with the flow sensor identifier; and associating, with the remote computing device in a database, the base identifier with the flow sensor identifier and the patient identifier. Clause 60. The method of any of clauses 53-59, further including: communicating, with the base, to the remote computing device, a request for information associated with the patient associated with the patient identifier; receiving, with the base, from the remote computing device, the information associated with the patient; and displaying, with a display of the base, the information associated with the patient. Clause 61. The method of any of clauses 53-60, wherein the information associated with the patient includes at least one of a list of drug allergies associated with the patient and a list of pending drug doses for the patient. Clause 62. The method of any of clauses 53-61, further including: scanning, with a short-range wireless communication device of the base, a short-range wireless communication tag attached to a syringe to decode a medication identifier associated with a medication on the syringe; comparing, with the base, the medication identifier for at least one of the list of medication allergies associated with the patient and the list of pending medication doses for the patient; and displaying, with the display of the base, an alert associated with the administration of the medication LfrZAnn / zznz / E / YiAi to the patient. Clause 63. The method of any of clauses 53-62, wherein 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. These and other features and characteristics of the present disclosure, as well as the methods of operation and functions of related elements of the structures and the combination of parts and the economy of manufacture, will become more apparent upon consideration of 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 is expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits. As used in the specification and claims, the singular forms a, an, and the include plural referents unless the context clearly dictates otherwise. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and further details of the embodiments or aspects of the present disclosure are explained in greater detail below with reference to the example embodiments illustrated in the attached schematic figures, in which: Figure 1 is a diagram of non-limiting embodiments or aspects of an environment in which the systems, devices, products, apparatus and / or methods described herein may be implemented; Figure 2 is a diagram of non-limiting embodiments or aspects of components of one or more devices and / or one or more systems of Figure 1; Figure 3A is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3B is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3C is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3D is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3E is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; LfrZAnn / zznz / E / YiAi Figure 3F is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3G is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 3H is a flow diagram of a non-limiting embodiment or aspect of a process for using a flow sensor system; Figure 4A is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 4B is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 4C is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 4D is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 5A is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 5B is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 5C is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 6A is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 6B is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 6C is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 7A is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 7B is a perspective view of an implementation of non-limiting embodiments or aspects of a flow sensor system; Figure 8 is a diagram of an exemplary magnetic H field around an antenna of a flow sensor system according to non-limiting embodiments or aspects; Figure 9A is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system; LfrZAnn / zznz / E / YiAi Figure 9B is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system; Figure 9C is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system; Figure 9D is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system; Figure 9E1 is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system; and Figure 9E2 is a flow diagram of non-limiting embodiments or aspects of a process for using a flow sensor system. DETAILED DESCRIPTION It should be understood that this disclosure may involve various variations and alternative sequence steps, except where expressly specified otherwise. It should also be understood that the specific devices and processes illustrated in the accompanying drawings, and described in the following specification, are merely examples and non-limiting embodiments or aspects. Accordingly, the specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein should not be considered limiting. For the purposes of the description that follows, the terms end, top, bottom, right, left, vertical, horizontal, up, down, side, length, and their derivatives will relate to the present disclosure as oriented in the Figures of the drawings. However, it should be understood that the present disclosure may involve various variations and alternative sequence steps, except where expressly specified otherwise. 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 embodiments or aspects of the present disclosure. Accordingly, the specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments disclosed herein should not be considered as limiting unless otherwise indicated. As used herein, proximal shall refer to a part or direction located away or further from a patient (upstream), while distal shall refer to a part or direction toward or located closer to a patient (downstream). Also, a drug substance is used herein for illustrative purposes and not as a limitation to refer to any substance injectable into a patient's body for any purpose. Reference to LfrZAnn / zznz / E / YiAi A patient can be any being, human or animal. A reference to a physician can be any person or thing that provides treatment, for example, a nurse, doctor, artificial intelligence, caregiver, or even self-treatment. No aspect, component, element, structure, action, step, function, instruction, and / or the like used herein should be considered critical or essential unless explicitly described as such. Also, as used herein, the terms "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more" and "at least one." Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one." Where only one item is intended, the term "one" or similar language is used. Also, as used herein, the terms "has," "having," "has," or the like are intended to be open-ended terms.Furthermore, the expression based on is intended to mean based at least partially on unless explicitly stated otherwise. As used herein, the terms "communication" and "communicate" refer to the reception or transfer of one or more signals, messages, commands, or other types of data. For a unit (e.g., any device, system, or component thereof) to be in communication with another unit means that one unit is capable of directly or indirectly receiving data from and / or transmitting data to the other unit. This may refer to a direct or indirect connection that may be wired and / or wireless. Additionally, two units may be in communication with each other, although the transmitted data may be modified, processed, forwarded, and / or routed between the first and second units. For example, a first unit may be in communication with a second unit even though the first unit passively receives data and does not actively transmit data to the second unit.As another example, a first unit may communicate with a second unit if an intermediary unit processes data from one unit and transmits the processed data to the second unit. It will be appreciated that many other arrangements are possible. It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Therefore, while the operation and behavior of the systems and / or methods are described herein without reference to specific software code, it is to be understood that the software and LfrZAnn / zznz / E / YiAi hardware may be designed to implement the systems and / or methods based on the description in this document. Some non-limiting embodiments or aspects are described herein in conjunction with thresholds. As used herein, satisfying a threshold may refer to a value that is greater than the threshold, more than the threshold, greater than the threshold, greater than or equal to the threshold, less than the threshold, less than the threshold, lower than the threshold, less than or equal to the threshold, equal to the threshold, etc. As used herein, the term "computing device" or "computer device" may refer to one or more electronic devices that are configured to communicate directly or indirectly with or across one or more networks. The computing device may be a mobile device, a desktop computer, or the like. Furthermore, the term "computer" may refer to any computing device that includes the components necessary to receive, process, and output data, and typically includes a display, a processor, memory, an input device, and a network interface.An application or application program interface (API) refers to computer code or other data presented on a machine-readable medium that can be executed by a processor to facilitate interaction between software components, such as a client-side front-end and a server-side back-end for receiving data from the client. An interface refers to a generated display, such as one or more graphical user interfaces (GUIs), with which a user can interact, either directly or indirectly (e.g., via a keyboard, mouse, touchscreen, etc.). As used herein, the term "server" may refer to or include one or more processors or computers, storage devices, or similar computing arrangements that are operated or facilitate communication and processing for multiple parties in a network environment, such as the Internet, although it will be appreciated that communication may be facilitated through one or more public or private network environments and that other arrangements are possible. Furthermore, multiple computers, e.g., servers or other computing devices, communicating directly or indirectly in the 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. 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 mobile phone (e.g., a smartphone or standard mobile phone), a portable computer (e.g., a tablet, a laptop, a notebook, a mobile device, or a mobile device). LfrZAnn / zznz / E / YiAi laptop, etc.), a wearable device (e.g., a watch, pair of glasses, eyeglasses, clothing, and / or the like), a personal digital assistant (PDA), and / or other similar devices. The terms “client device” and “user device,” as used herein, refer to any electronic device that is configured to communicate with one or more servers or remote devices and / or systems. A client device or user device may include a mobile device, a network-enabled device (e.g., a network-enabled television, refrigerator, thermostat, and / or the like), a computer, and / or any other device or system capable of communicating with a network. As used herein, the term application or application program interface (API) refers to computer code, a set of rules, or other data classified in a machine-readable medium that can be executed by a processor to facilitate interaction between software components, such as a client-side front-end and a server-side back-end for receiving data from the client. An interface refers to a generated display, such as one or more graphical user interfaces (GUIs), with which a user can interact, either directly or indirectly (e.g., via a keyboard, mouse, etc.). Referring to Figure 1, non-limiting embodiments or aspects of an environment 100 in which the systems, devices, products, apparatus, and / or methods, as described herein, may be implemented. As shown in Figure 1, the environment 100 may include a flow sensor system 150 including a flow sensor 160 and a base 180, medical device 102 (e.g., a syringe, etc.) including the short-range wireless communication tag 104, IV line 106, communications network 108, and / or remote computing device 110. The medical device 102 may be configured to be physically connected to the flow sensor 160 as described in more detail herein. The short-range wireless communication tag 104 may 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, and / or the like. In some non-limiting embodiments or aspects, the short-range wireless communication tag 104 may include one or more devices capable of transmitting and / or receiving information to and / or from the base 180 via a short-range wireless communication connection (e.g., a short-range wireless communication connection). LfrZAnn / zznz / E / YiAi communication using the NFC protocol, a communication connection using radio frequency identification (RFID), a communication connection using a Bluetooth® wireless technology standard, and / or the like). Further details about non-limiting embodiments or aspects of the medical device 102 and the short-range wireless communication tag 104 are provided below with respect to Figures 3A-3H, 4A-4D, and 5A-5C. The flow sensor 160 may be configured to be detachably 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 may be connected in-line with the IV line 106 between a fluid source and a patient. Additional details regarding non-limiting embodiments or aspects of the flow sensor 160 are provided below with respect to Figures 3A-3H, 4A-4D, and 5A-5C. 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 the remote computing device 110 (e.g., via the communication network 108, etc.) and / or communicating information and / or data to the remote computing device 110 (e.g., via the communication network 108, etc.). For example, the base 180 may include a computing device, a mobile device, and / or the like. 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, and / or the like.In some non-limiting embodiments or aspects, the base 180 may include one or more devices capable of transmitting and / or receiving information to and / or from the short-range wireless communication tag 104 via a short-range wireless communication connection (e.g., a communication connection utilizing the NFC protocol, a communication connection utilizing radio frequency identification (RFID), a communication connection utilizing a Bluetooth® wireless technology standard, and / or the like). In some non-limiting embodiments or aspects, the base 180 includes an integrated power source (not shown), such as a battery, and / or the like. Further details regarding non-limiting embodiments or aspects of the base 180 are provided below with respect to Figures 3A-3H, 4A-4D, and 5A-5C. 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), or a cellular network. LfrZAnn / zznz / E / YiAi (4G), a fifth generation network (5G), 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 pwork telephony network (e.g., a public switched telephone network (PSTN)), a private network, a specially manufactured network, an intranet, the Internet, a fiber optic network, a cloud computing network, and / or the like, and / or a combination of these or other types of networks. The remote computing device 110 may include one or more devices capable of receiving information and / or data from the base 180 (e.g., via the communication network 108, etc.) and / or communicating information and / or data to the base 180 (e.g., via the communication network 108, etc.). For example, the remote computing device 110 may include a computing device, a server, a group of servers, a mobile device, a group of mobile devices, and / or the like. The number and arrangement of devices and systems shown in Figure 1 is provided as an example. There may be additional devices and / or systems, fewer devices and / or systems, different devices and / or systems, or devices and / or systems arranged differently than those shown in Figure 1. Furthermore, two or more devices and / or systems shown in Figure 1 may be implemented within a single device and / or system, or a single device and / or system shown in Figure 1 may be implemented as multiple distributed devices and / or systems. Additionally or alternatively, one set of devices and / or systems (e.g., one or more devices or systems) of environment 100 may perform one or more functions described as being performed by another set of devices and / or systems of environment 100. Referring now to Figure 2, Figure 2 is an example component diagram of a device 200. The device 200 may correspond to the base 180 and / or the remote computing device 110. In some non-limiting embodiments or aspects, the base 180 and / or the remote computing device 110 may include at least one device 200 and / or at least one component of the device 200. As shown in Figure 2, the device 200 may include the bus 202, processor 204, memory 206, storage component 208, input component 210, output component 212, and / or communication interface 214. The bus 202 may include a component that enables 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), a graphics processing unit (GDPR), a graphics processing unit (GDPR), a graphics processing unit (GDPR), a graphics processing unit (GDPR) or a graphics processing unit (GDPR). LfrZAnn / zznz / E / YiAi accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), and / or the like, that can be programmed to perform a function. Memory 206 may include random access memory (RAM), read-only memory (ROM), and / or other type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use in processor 204. The storage component 208 may store information and / or software related to the operation and use of the device 200. For example, the storage component 208 may include a hard disk drive (e.g., a magnetic disk, an optical disk, an optomagnetic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or other type of computer-readable media, along with a corresponding drive. The input component 210 may include a component that enables the device 200 to receive information, such as through user input (e.g., a touch screen, a keypad, a wireless keyboard, a mouse, a button, a switch, a microphone, etc.). Additionally or alternatively, the input component 210 may include a sensor for detecting 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.). The output component 212 may include a component that provides output information from the device 200 (e.g., a display, a speaker, one or more light emitting diodes (LEDs), etc.). The communications interface 214 may include a transceiver-type component (e.g., a separate transceiver, receiver, and transmission source, etc.) that enables the device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communications interface 214 may enable the device 200 to receive information from another device and / or provide information to another device. For example, the communications interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal signal bus (USB) interface, a Wi-Fi interface, a cellular network interface, and / or the like. Device 200 may perform one or more of the processes described herein. Device 200 may perform these processes based on processor 204 executing LfrZRnn / zznz / E / YiAi computer instructions stored on a computer-readable medium, such as a memory 206 and / or a storage component 208. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device includes memory space located within a single physical storage device or memory space spread across multiple physical storage devices. The software instructions may be read into the memory 206 and / or the 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 the storage component 208 may cause the processor 204 to perform one or more processes described herein. Additionally or alternatively, hard-wired circuitry may be used in place of or in conjunction with computer program 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 / or computer programs. Memory 206 and / or storage component 208 may include data storage or one or more data structures (e.g., a database, etc.). Device 200 may be able to receive information from, store information in, communicate information to, or search for information stored in the data storage or one or more data structures in memory 206 and / or storage component 208. The number and arrangement of components shown in Figure 2 are provided as an example. In some non-limiting embodiments or aspects, the device 200 may include additional components, fewer components, different components, or components arranged differently than those shown in Figure 2. Additionally or alternatively, one set of components (e.g., one or more components) of the device 200 may perform one or more functions described as being performed by another set of components of the device 200. Figures 3A-3H, 4A-4D, and 5A-5C illustrate non-limiting embodiments or aspects of flow sensor system 150. Referring to Figures 3A-3H, 4A-4D, and 5A-5C, flow sensor system 150 may include two primary assemblies that snap together prior to use: flow sensor 160 and base 180. In some non-limiting embodiments or aspects, flow sensor 160 may be a single-use flow sensor that mates with reusable base 180. LfrZAnn / zznz / E / YiAi The flow sensor system 150 may reduce medication error at the bedside during bolus administration. The flow sensor system 150 may provide a record and electronically measure bolus administration, allowing monitoring of bolus administration and automatic documentation of bolus administration as part of the patient's medical record. The flow sensor system 150 may provide alerts when a bolus administration inconsistent with a patient's medical record is about to occur. The flow sensor system 150 may be a portable instrument injection site with an interactive interface for IV syringe drug administration and direct electronic medical record documentation. The base 180 may include a durable, reusable reader base with a touchscreen display and a separate disposable consumable flow sensor 160. 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 attribute of the fluid in the flow tube 162, and / or an electrical contact of the flow sensor 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 a flow of a fluid in the flow tube 162. 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 one or more processors 204, a short-range wireless communication device (e.g., communications interface 214, a near field communication (NFC) receiver, etc.), and / or a display 194 (e.g., input component 210, output component 212, a touchscreen configured to receive user input from a user, etc.). The flow sensor electrical contact 172 may be in electrical communication with the base electrical contact 192 when the flow sensor is connected (e.g., attached, affixed, mounted, etc.) to the base 180. 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 be slidably engaged with the opening 196 of the base 180. In some non-limiting embodiments or aspects, the at least one sensor 170 may include a first ultrasonic transducer or piezoelectric element 170 disposed at a position i to detect the presence of the syringe and initiate decoding of the label 104 (e.g., via the short-range wireless communication device, etc.) to record information contents of the label 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 when it is inserted into the fluid injection port 165 to detect the presence of the syringe 102 when inserted by a user. In such an example, a mechanical button or switch on the flow sensor 160 is in electrical communication with one or more processors (e.g., via electrical contacts 172 and 192, etc.) may be actuated by connecting / disconnecting the syringe 102 to the fluid injection port 165 to send a signal to 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, the tag or marking 104, which may include an NFC tag embedded in the tag or marking 104, may be manually placed on a syringe body 102 using a standard label printer. For example, a label printer may be used to encode the NFC tag at the time of printing. Additionally or alternatively, the NFC encoding may be performed using a separate NFC tag encoding unit. 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 within 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 a connection of the syringe 102 to the fluid injection port 165.For example, the tag 104 may be detected using NFC when positioned radially adjacent to an antenna of the short-range wireless communication device on the base 180. As an example, the base 180 may include an integrated radially positioned NFC antenna to register the bearing tag of the syringe 104 and read and decode encoded information thereon. In such an example, the NFC antenna and bearing tags are optimized to eliminate false detection of syringes positioned adjacent to NFC bearing tags (e.g., an NFC antenna mounted radially on the base 180). LfrZAnn / zznz / E / YiAi and the marking tag 104 on the syringe barrel 102 can be used to transmit encoded tag information from the syringe marking tag 104 to the reader base 180, etc.). In some non-limiting embodiments or aspects, the one or more processors 204 may be programmed and / or configured to automatically detect a state of the valve 166 when the flow sensor 160 is connected to the base 180. For example, the base 180 may automatically determine a state or position of the valve 166 when a user manually changes the state or position of the valve 166. As an example, an electronic and / or mechanical interface may interact with the valve 166 to control the position or state of the valve. In such an example, a mechanical button or switch on the flow sensor 160 is in electrical communication with the one or more processors (e.g., via electrical contacts 172 and 192, etc.) may be activated by changing the position or state of valve 166 to send a signal to one or more processors 204 indicating the state or position of valve 166 (e.g., indicating that fluid flow is permitted between fluid inlet 163 and fluid outlet 164, between fluid inlet 163 and fluid injection port 165, between fluid injection port 165 and fluid outlet 164, or any combination thereof, etc.). 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 the at least one attribute of the fluid in the flow tube 162 based on the detected state of the valve 166. For example, a user may change the state or position of the valve 166 to allow recording of the flow measurement and / or allow IV fluid flow. As an example, the one or more processors 204 of the base 180 may determine when to flag flow measurements and ignore redundant IV fluid flow and volume measurements when IV fluid is drawn into the syringe 102 and then injected through the flow sensor 160. In some non-limiting embodiments or aspects, the flow sensor 160 is inserted in-line with the IV line 106 between a fluid source and a patient. For example, the disposable flow sensor 160 may be inserted in-line with the IV line 106 allowing IV fluid to pass directly into a patient's extension line catheter. In some non-limiting embodiments or aspects, the valve 166 is configured to allow the syringe 102 to draw IV fluid from the IV line 106 and deliver the drawn IV fluid through the flow sensor 160 to push the fluid to flush the flow sensor 160 and the extension line of a previously administered volume of medication. In some non-limiting embodiments or aspects, the flow sensor 160 may be integrated into IV 106 (e.g., into an IV extension set line, etc.) without LfrZAnn / zznz / E / YiAi separate detachable connectors. In some non-limiting embodiments or aspects, fluid flow stopcock valves may be positioned in-line before and / or after flow sensor 160 and / or additional functionality may be developed to incorporate workflow operations within interactive display 194 of base 180. For example, by placing flow sensor 160 in-line with IV line 106, a dead space issue may be solved due to the lack of flushing associated with parallel connections. In some non-limiting embodiments or aspects, the base 180 includes an optical scanner configured to read a barcode label (e.g., a barcode label on the patient's cuff, a barcode label on the flow sensor 160, etc.). In some non-limiting embodiments or aspects, the display 194 includes a touch screen configured to receive input from a user. For example, the display 194 may include an interactive graphical user interface configured to display a current state of internal functions of the reader base 180, a current state of an injection site, and / or a prompt for user interaction, and the reader base 180 may interact with the user via the touch screen, audio, voice command, haptic feedback, and / or the like (e.g., to inform the user of the current state and request user input, etc.). Accordingly, by incorporating the display 194 into the base 180, a user need not remove their attention from the base 180 to interact with the display 194. In some non-limiting embodiments or aspects, the base 180 includes a wireless communication device configured to communicate information associated with at least one attribute of the fluid in the flow tube 162 to the remote computing device 110. For example, the base 180 may communicate information and / or data with the remote computing device 110 to document occurrences of medication administration in the patient's medical records (e.g., patient medical records associated with a barcode label on the patient's bracelet scanned by the optical scanner of the base 180, etc.). Referring now to Figures 4A, 5A, 6A-6C, 7A, 7B and 8, in some non-limiting embodiments or aspects, the base short-range wireless communication device 180 may include a curved coil antenna 600. The size of the syringe 102 may vary (e.g., the size of a syringe may be in a range of 1 ml to 60 ml, etc.). The location of the short-range wireless communication tag 104 on the syringe 102 may vary. For example, a user may attach a short-range wireless communication tag 104 in several different locations on a syringe body 102. The variability between the location of the tag 104 and the location of the short-range wireless communication tag 104 may vary. LfrZAnn / zznz / E / YiAi size of the syringe 102 in combination with a curvature of the syringe body 102 may make it difficult to read encoded data from the tag 104 and / or place a significant burden on the user. For example, HF / NFC RFID works by creating inductive coupling of magnetic waves in the 13.56 MHz range to power an HF / NFC RFID tag, which transmits the encoded information to a transmitter coil antenna. As an example, the transmitter coil antenna must transmit enough power to power the tag 104, and a tag coil antenna on the tag 104 must receive enough power to power and transmit the encoded information stored on the tag 104 back to the transmitter coil antenna. A transmitter coil antenna may be planar, and the tag 104 may be parallel to the transmitter coil antenna to power the tag 104 if the tag 104 receives enough power.The received power may be based on the distance of the tag 104 from the transmitting coil antenna and / or the orientation of the transmitting coil antenna relative to the tag 104 (e.g., an offset and / or an angle at which the tag 104 faces the transmitting coil antenna, etc.). For example, as the angle between the tag coil antenna 104 and the transmitting coil antenna approaches 90 or 270 degrees, the antenna power received by the tag 104 may decrease to zero. As an example, a formula may be defined to calculate the amount of power received by the tag 104 from a transmitting coil antenna according to a cosine (angle). Accordingly, if the angle between the transmitting coil antenna and the tag coil antenna 104 reaches 90 or 270 degrees, the power received by the tag 104 is zero and the tag 104 cannot be turned on.Thus, if the tag 104 is on a syringe 102 and the user can place the tag 104 anywhere on the syringe 102, there is a possibility that the angle may be close enough to or at the 0 energy point where the data encoded on the tag 104 cannot be read by a short range wireless communication device. Non-limiting embodiments or aspects of the flow sensor system 150 that include the curved coil antenna 600 may reduce and / or eliminate a 90 and / or 270 degree angle between a transmitting coil antenna of the base short range wireless communication device 180 and the tag 104 on the syringe 102 by encompassing and / or surrounding the syringe 102 with the curved coil antenna 600. For example, and referring to Figure 8, the curved coil antenna 600 may allow magnetic waves to be transmitted from the base short range wireless communication device 180 radially with respect 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., LfrZAnn / zznz / E / YiAi depending on a circumferential area of ​​the curved coil antenna 600, an acceptance criterion for successful reads, etc.). As an example, the curved coil antenna 600 may allow magnetic waves to be transmitted radially from the base short range wireless communication device 180 to encompass an HF NFC RFID tag on a circular syringe. On the other hand, a flat NFC coil antenna may cause magnetic waves to be transmitted orthogonal to the coil antenna, which may result in an HF NFC RFID tag that does not align with the transmitted magnetic waves (e.g., particularly if the tag is at 90 degrees to the waves, etc.), fails to power on, and fails to transmit the information encoded in the tag to the transmitting NFC coil antenna.Accordingly, a curved NFC coil antenna may allow magnetic waves to be transmitted in more directions relative to an HF NFC RFID tag (e.g., for NFC communications based on NFC standards of ISO14443 and / or ISO15693 which describe physical layer technology and protocol layer technology, etc.), thereby reducing and / or avoiding a 90 and / or 270 degree angle between the transmitting coil antenna and the tag. 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 on the short-range wireless communication device of the base 180 may be radially curved with respect 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 curved about the syringe 102 and / or extend in the first direction parallel to the longitudinal axis of the fluid injection port 165. In some non-limiting embodiments or aspects, as shown for example in Figures 4A and 6A-6C, the curved coil antenna 600 extends in a direction parallel to a plane defined by a face of the display 194 of the base 180 (e.g., in a direction parallel to the longitudinal axis of 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, etc.). In some non-limiting embodiments or aspects, as shown for example in Figure 5A, the curved coil antenna 600 extends in a non-parallel direction (e.g., in a direction perpendicular to) a plane defined by a face of the display 194 of the base 180 (e.g., in a direction perpendicular to a longitudinal axis of the syringe 102 when the syringe 102 is connected to the LfrZAnn / zznz / E / YiAi flow sensor 160 and the flow sensor 160 is connected to the base 180, etc.). In such an example, the curved coil antenna 600 may at least partially surround 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. In some non-limiting embodiments or aspects, a curved coil antenna curvature may correspond to a circumferential area of ​​a 60 ml syringe and / or the like. Referring now to Figures 3A-3H and 9A-9E, Figures 3A-3H and 9A-9E are flow diagrams of non-limiting embodiments or aspects of processes for using a flow sensor system. In some non-limiting embodiments or aspects, one or more of the process steps 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 of the process steps are performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including the flow sensor system 150, such as the remote computing device 110 (e.g., one or more devices of a remote computing device system 110, etc.). As shown in Figure 9A, in step WS5.2, a process for using a flow sensor system includes scanning a flow sensor label attached to the disposable flow sensor to decode a flow sensor identifier associated with the flow sensor. For example, a base optical scanner 180 (e.g., Reader in Figures 9A-9E) for the disposable flow sensor 160 (e.g., Sensor in Figures 9A-9E) may scan a flow sensor label (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, scanning the barcode of the disposable flow sensor 160 allows the base 180 (and / or the remote computing system 110) to determine whether or not the disposable flow sensor 160 has already been used, and if so, by which patient. As shown in Figure 9A, in step WS4, a process for using a flow sensor system includes scanning a patient tag attached to a patient to decode a patient identifier associated with the patient. For example, the optical scanner of the base 180 for the disposable flow sensor 160 may scan a patient tag adhered to a patient (e.g., a patient bracelet, a patient barcode, etc.) to decode a patient identifier associated with the patient. As an example, a smart device (e.g., the base 180, etc.) may be used to electronically scan, with, for example, a barcode scanner, each of the smart IV consumables (e.g., disposable flow sensor 160, etc.) and the patient bracelet provided by a LfrZAnn / zznz / E / YiAi EMR provider. The smart device may communicate patient identification information (e.g., patient MRN) and the smart IV supply's unique identification number to a virtual server (e.g., remote computing device 110, etc.) on a hospital network. The virtual server may use the patient identifier information to generate a two-way link to applications in the Hospital Information System associated with that patient relevant to the function of the smart device and the smart IV supply. Once the two-way link is established, the virtual server may associate the link with the smart IV supply's unique identification number, and if the smart device is disassociated, the smart device, or a new, different device, may be reassociated by scanning the smart supply.On the other hand, if the patient is associated only with electronics, such as a patient association with a barcode reader, if that device can no longer be used (e.g., if the batteries run out, etc.), a new association is required by scanning the patient's wristband. If the wristband is inaccessible (e.g., during surgery, etc.), manual entry of the patient ID may be required, which may be subject to error. For example, a device may need to be associated with a patient's record by having the EMR assign the case to the device, by manually selecting the patient through the user interface on the device, or by associating the smart device directly with the patient through an electronic scan or other means.Additionally, if not properly disassociated, a device may also be at risk of being used to record incorrect patient information in the wrong patient record. As shown in Figure 9A, in step WS5.3, a process for using a flow sensor system includes connecting the disposable flow sensor to the base. For example, the disposable flow sensor 160 may be connected to the base 180. As shown in Figure 9A, in step WS5.1, a process for using a flow sensor system includes integrating the disposable flow sensor into an IV line. For example, the disposable flow sensor 160 may be integrated into the IV line 106. In some non-limiting embodiments or aspects, and referring now to Figure 9B, the disposable flow sensor 160 is integrated into the IV line 106 before scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor 160 to the base 180. For example, integrating the disposable flow sensor 160 into the IV line 106 before scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor 160 to the base 180 may allow a physician to associate the patient by performing other positive patient identification and / or scanning and connecting the disposable flow sensor 160. LfrZAnn / zznz / E / YiAi at a more contiguous stage that adds value, for example, when preparing a patient for a procedure in an operating room. For example, scanning the patient's ID before connection can ensure that the IV line 106 does not obstruct the user when scanning the patient's ID, which can be ideal for outpatients where a new IV line is being constructed with the disposable flow sensor 160 in place for the procedure. In some non-limiting embodiments or aspects, and referring now to Figure 9C, the disposable flow sensor 160 is integrated into the IV line 106 after scanning the flow sensor label, scanning the patient label, 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 label, scanning the patient label, and connecting the disposable flow sensor 160 to the base 180 may allow a clinician to prepare the base 180 and the disposable flow sensor 160 prior to interaction with a patient and / or a pre-existing IV, which may add value when the clinician has time prior to the arrival of a hospitalized patient with a pre-existing IV, saving steps that do not need to be performed in the presence of the patient. As shown in Figure 9A, in steps WS4, WS5.2 and / or WS5.4, a process for using a flow sensor system includes communicating the flow sensor identifier and the patient identifier to a remote computing device and associating the flow sensor identifier with the patient identifier. For example, base 180 may communicate the flow sensor identifier and the patient identifier to remote computing device 110, and the remote computing device 110 may associate the flow sensor identifier with the patient identifier in a database. In some non-limiting embodiments or aspects, and referring now to Figure 9D, the base 180 may communicate, to the remote computing device 110, a request for the status of the disposable flow sensor 160 associated with the flow sensor identifier and receive, from the remote computing device 110, an indication of the status of the disposable flow sensor 160 associated with the flow sensor identifier. 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. In some non-limiting embodiments or aspects, and still referring to Figure 9D, the base 180 may communicate, to the remote computing device 110, a base identifier associated with the base 180 in the request for the status of the disposable flow sensor 160 associated with the flow sensor identifier, and the remote computing device 110 may associate the LfrZAnn / zznz / E / YiAi Base identifier with the flow sensor identifier and the patient identifier. As shown in Figure 9A, in steps WS4 and / or WS6, a process for using a flow sensor system includes communicating a request for patient-associated information associated with the patient identifier, receiving the patient-associated information, and displaying the patient-associated information. For example, and also referring to Figure 9E, base 180 may communicate, to remote computing device 110, a request for patient-associated information associated with the patient identifier, receive, from the remote computing device 110, the patient-associated information, and display, with a display, the patient-associated information. In some non-limiting embodiments or aspects, the information associated with the patient includes at least one of a list of medication allergies associated with the patient and a list of pending medication doses for the patient. In some non-limiting embodiments or aspects, and still referring to Figure 9E, a short-range wireless communication device of the base 180 may scan a short-range wireless communication tag 104 attached to a syringe 102 to decode a medication identifier associated with a medication on the syringe 102, and the base 180 may compare the medication identifier to at least one of the list of medication allergies associated with the patient and the list of pending medication doses for the patient. For example, a display 194 of the base 180 may display an alert associated with the administration of the medication 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.Accordingly, non-limiting embodiments or aspects of a process for using a flow sensor system may allow for more steps to be performed at a point of care with a patient in view, providing advantages over methods requiring interaction with EMR screens. Furthermore, non-limiting embodiments or aspects of a process for using a flow sensor system may allow a patient to be associated with the smart consumable that is connected to the patient's IV line instead of to electronics (e.g., the 180 base, etc.).) only, providing greater confidence that the device data is linked to the correct patient as the smart IV consumable is connected directly to the patient (via the IV), and which can allow the smart device to be exchanged with another that can be associated to the patient by scanning the smart consumable rather than having to rescan the patient's bracelet. LfrZAnn / zznz / E / YiAi Although embodiments or aspects have been described in detail for purposes of illustration and description, it is to be understood that such detail is for that purpose only and that the embodiments or aspects are not limited to the disclosed embodiments or aspects, but rather are intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more elements of any embodiment or aspect may be combined with one or more elements of any other embodiment or aspect. Indeed, 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 a single claim, the disclosure of possible implementations includes each dependent claim combined with each and every remaining claim in the claim set.

Claims

1. A system comprising: a 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 and second ends of the flow tube, wherein the fluid injection port extends from the flow tube in a first direction parallel to a longitudinal axis of the fluid injection port; and a base configured to connect to the flow sensor, wherein the base includes: a short-range wireless communication device including a curved coil antenna, wherein the curved coil antenna is radially curved with respect to the longitudinal axis of the fluid injection port when the flow sensor is connected to the base.

2. The system of claim 1, wherein the curved coil antenna extends in the first direction parallel to the longitudinal axis of the fluid injection port.

3. The system of claim 1, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen.

4. The system of claim 1, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the screen.

5. The system of claim 1, wherein the fluid injection port is configured to connect to a syringe, and 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 curved coil antenna is radially curved around the syringe.

6. The system of claim 5, wherein an attached short-range wireless communication tag is attached to a syringe body.

7. The system of claim 6, 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 is carried within the communication range of the short-range wireless communication device. LfrZAnn / zznz / E / YiAi 8. The system of claim 7, wherein the short-range wireless communication device receives information associated with a drug contained in the syringe from the short-range wireless communication tag when the short-range wireless communication tag is carried within the communication range of the short-range wireless communication device.

9. The system of claim 1, wherein the short-range wireless communication device includes a near-field communication (NFC) receiver.

10. A system comprising: a 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 and second ends of the flow tube, wherein the fluid injection port is configured to connect to a syringe; and a base configured to connect to the flow sensor, wherein the base includes: a short-range wireless communication device including a curved 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 curved coil antenna is radially curved around the syringe.

11. The system of claim 10, wherein the curved coil antenna extends in a first direction parallel to a longitudinal axis 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.

12. The system of claim 10, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen.

13. The system of claim 10, wherein the base further includes a screen, and wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the screen.

14. The system of claim 10, wherein an attached short-range wireless communication tag is attached to a syringe body.

15. The system of claim 14, 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 is carried within a communication range of the short-range wireless communication device.

16. The system of claim 15, wherein the short-range wireless communication device receives information associated with a drug contained in the syringe from the short-range wireless communication tag when the short-range wireless communication tag is carried within the communication range of the short-range wireless communication device.

17. The system of claim 10, wherein the short-range wireless communication device includes a near-field communication (NFC) receiver.

18. 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.

19. The basis of claim 18, wherein the curved coil antenna extends in a direction parallel to a plane defined by a face of the screen.

20. The basis of claim 18, wherein the curved coil antenna extends in a direction perpendicular to a plane defined by a face of the screen.

21. The base of claim 18, wherein the curved coil antenna is radially curved around a syringe when the syringe is connected to the flow sensor and the flow sensor is connected to the base.

22. The basis of claim 21, wherein an attached short-range wireless communication tag is attached to a syringe body.

23. The basis of claim 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 is carried within a communication range of the short-range wireless communication device.

24. The basis of claim 23, wherein the short-range wireless communication device receives information associated with a drug included in the LfrZAnn / zznz / E / YiAi syringe from the short-range wireless communication tag when the short-range wireless communication tag is carried within the communication range of the short-range wireless communication device.

25. The basis of claim 18, wherein the short-range wireless communication device 5 includes a near-field communication (NFC) receiver.

Images