Patent Description:
The present disclosure relates generally to a flow sensor system and, in some non-limiting embodiments or aspects, to a flow sensor system for sensing a flow of a fluidic medicament.

There is a need to reduce medication error at bedside during bolus delivery. It is advantageous to provide a record of, and electronically measure, bolus delivery which allows monitoring bolus delivery and automatic documentation of bolus delivery as part of a patient's health record. Additionally, it is advantageous to provide alerts when bolus delivery inconsistent with a patient's medical record is about to occur.

Preferable embodiments are further defined in the dependent claims.

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

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

It is to be understood that the present disclosure may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary and non-limiting embodiments or aspects. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein are not to be considered as limiting.

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

As used herein, proximal shall refer to a part or direction located away or furthest from a patient (upstream), while distal shall refer to a part or direction towards or located nearest to a patient (downstream). Also, a drug substance is used herein in an illustrative, non-limiting manner to refer to any substance injectable into the body of a patient for any purpose. Reference to a patient may be to any being, human or animal. Reference to a clinician may be to any person or thing giving treatment, e.g., a nurse, doctor, machine intelligence, caregiver, or even self-treatment.

As used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more" and "at least one. " Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with "one or more" or "at least one. " Where only one item is intended, the term "one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or the like are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "based at least in partially on" unless explicitly stated otherwise.

As used herein, the terms "communication" and "communicate" refer to the receipt or transfer of one or more signals, messages, commands, or other type of data. For one unit (e.g., any device, system, or component thereof) to be in communication with another unit means that the one unit is able to directly or indirectly receive data from and/or transmit data to the other unit. This may refer to a direct or indirect connection that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the data transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives data and does not actively transmit data to the second unit. As another example, a first unit may be in communication with a second unit if an intermediary unit processes data from one unit and transmits processed data to the second unit. It will be appreciated that numerous other arrangements are possible.

It will be apparent that systems and/or methods, described herein, can be implemented in different forms of hardware, software, or a combination of hardware and software. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, it being understood that software and hardware can be designed to implement the systems and/or methods based on the description herein.

Some non-limiting embodiments or aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, more than the threshold, higher than the threshold, greater than or equal to the threshold, less than the threshold, fewer 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 directly or indirectly communicate with or over 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 necessary components to receive, process, and output data, and normally includes a display, a processor, a memory, an input device, and a network interface. An "application" or "application program interface" (API) refers to computer code or other data sorted on a computer-readable medium that may be executed by a processor to facilitate the interaction between software components, such as a client-side front-end and/or server-side back-end for receiving data from the client. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUls) with which a user may interact, either directly or indirectly (e.g., through 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 computer arrangements that are operated by 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 over one or more public or private network environments and that various other arrangements are possible. Further, multiple computers, e.g., servers, or other computerized devices, directly or indirectly communicating 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 cellular phone (e.g., a smartphone or standard cellular phone), a portable computer (e.g., a tablet computer, a laptop computer, etc.), a wearable device (e.g., a watch, pair of glasses, lens, clothing, and/or the like), a personal digital assistant (PDA), and/or other like devices. The 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 appliance (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 sorted on a computer-readable medium that may be executed by a processor to facilitate interaction between software components, such as a client-side front-end and/or server-side back-end for receiving data from the client. An "interface" refers to a generated display, such as one or more graphical user interfaces (GUls) with which a user may interact, either directly or indirectly (e.g., through a keyboard, mouse, etc.).

Referring to <FIG>, non-limiting embodiments or aspects of an environment <NUM> in which systems, devices, products, apparatus, and/or methods, as described herein, may be implemented is shown. As shown in <FIG>, environment <NUM> may include flow sensor system <NUM> including flow sensor <NUM> and base <NUM>, medical device <NUM> (e.g., a syringe, etc.) including short range wireless communication tag <NUM>, IV line <NUM>, communications network <NUM>, and/or remote computing device <NUM>.

Medical device <NUM> may be configured to physically connect to flow sensor <NUM> as described in more detail herein. Short range wireless communication tag <NUM> may be attached to or integrated with medical device <NUM> as described in more detail herein. In some non-limiting embodiments or aspects, short range wireless communication tag <NUM> 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, short range wireless communication tag <NUM> can include one or more devices capable of transmitting and/or receiving information to and/or from base <NUM> via a short range wireless communication connection (e.g., a communication connection that uses NFC protocol, a communication connection that uses Radio-frequency identification (RFID), a communication connection that uses a Bluetooth® wireless technology standard, and/or the like). Further details regarding non-limiting embodiments or aspects of medical device <NUM> and short range wireless communication tag <NUM> are provided below with regard to <FIG>, <FIG>, and <FIG>.

Flow sensor <NUM> may be configured to be removably, physically, and/or electrically connected to base <NUM> as described in more detail herein. In some non-limiting embodiments or aspects, flow sensor <NUM> may be connected in-line with IV line <NUM> between a fluid source and a patient. Further details regarding non-limiting embodiments or aspects of flow sensor <NUM> are provided below with regard to <FIG>, <FIG>, and <FIG>.

Base <NUM> may be configured to be removably, physically, and/or electrically connected to flow sensor <NUM> as described in more detail herein. Base <NUM> may include may include one or more devices capable of receiving information and/or data from remote computing device <NUM> (e.g., via communication network <NUM>, etc.) and/or communicating information and/or data to remote computing device <NUM> (e.g., via communication network <NUM>, etc.). For example, base <NUM> may include a computing device, a mobile device, and/or the like. In some non-limiting embodiments or aspects, base <NUM> 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, base <NUM> can include one or more devices capable of transmitting and/or receiving information to and/or from short range wireless communication tag <NUM> via a short range wireless communication connection (e.g., a communication connection that uses NFC protocol, a communication connection that uses Radio-frequency identification (RFID), a communication connection that uses a Bluetooth® wireless technology standard, and/or the like). In some non-limiting embodiments or aspects, base <NUM> includes an integrated power source (not shown), such as a battery, and/or the like. Further details regarding non-limiting embodiments or aspects of base <NUM> are provided below with regard to <FIG>, <FIG>, and <FIG>.

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

Remote computing device <NUM> may include one or more devices capable of receiving information and/or data from base <NUM> (e.g., via communication network <NUM>, etc.) and/or communicating information and/or data to base <NUM> (e.g., via communication network <NUM>, etc.). For example, remote computing device <NUM> may include a computing device, a server, a group of servers, a mobile device, a group of mobile devices, and/or the like.

The number and arrangement of devices and systems shown in <FIG> is provided as an example. There 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>. Furthermore, two or more devices and/or systems shown in <FIG> may be implemented within a single device and/or system, or a single device and/or system shown in <FIG> may be implemented as multiple, distributed devices and/or systems. Additionally, or alternatively, a set of devices and/or systems (e.g., one or more devices or systems) of environment <NUM> may perform one or more functions described as being performed by another set of devices and/or systems of environment <NUM>.

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

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

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

Communication interface <NUM> may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmission source, etc.) that enables device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface <NUM> may permit device <NUM> to receive information from another device and/or provide information to another device. For example, communication interface <NUM> may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, and/or the like.

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

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

Memory <NUM> and/or storage component <NUM> may include data storage or one or more data structures (e.g., a database, etc.). Device <NUM> may be capable of receiving information from, storing information in, communicating information to, or searching information stored in the data storage or one or more data structures in memory <NUM> and/or storage component <NUM>.

<FIG>, <FIG>, and <FIG> illustrate non-limiting embodiments or aspects of flow sensor system <NUM>. Referring to <FIG>, <FIG>, and <FIG>, flow sensor system <NUM> may include two main assemblies which fit together prior to use: flow sensor <NUM> and base <NUM>. In some non-limiting embodiments or aspects, flow sensor <NUM> may be a single-use flow sensor which is engageable with reusable base <NUM>.

Flow sensor system <NUM> may reduce medication error at bedside during bolus delivery. Flow sensor system <NUM> may provide a record of and electronically measure bolus delivery, which allows monitoring bolus delivery and automatic documentation of bolus delivery as part of a patient's health record. Flow sensor system <NUM> may provide alerts when bolus delivery inconsistent with a patient's medical record is about to occur.

Flow sensor system <NUM> may be a handheld instrument Injection Site with interactive interface for syringe injection IV drug delivery and direct electronic medical record documentation. Base <NUM> may include a durable reusable reader base with a touchscreen display and a separate disposable consumable flow sensor <NUM>.

In some non-limiting embodiments or aspects, flow sensor <NUM> may include a flow tube <NUM>, at least one sensor <NUM> configured to characterize at least one attribute of the fluid in the flow tube <NUM>, and/or a flow senor electrical contact <NUM> in electrical communication with the at least one sensor <NUM>. The flow tube <NUM> may include a fluid inlet <NUM> at a first end of the flow tube <NUM>, a fluid outlet <NUM> at a second end of the flow tube <NUM> opposite the first end of the flow tube <NUM>, a fluid injection port <NUM> between the first end and the second end of the flow tube <NUM>, and a valve <NUM> (e.g., a manual valve, etc.) configured to control a flow of a fluid in the flow tube <NUM>.

In some non-limiting embodiments or aspects, base <NUM> may include one or more processors <NUM>, a base electrical contact <NUM> in electrical communication with the one or more processors <NUM>, a short range wireless communication device (e.g., communication interface <NUM>, a near-field communication (NFC) receiver, etc.), and/or a display <NUM> (e.g., input component <NUM>, output component <NUM>, a touchscreen display configured to receive user input from a user, etc.). The flow sensor electrical contact <NUM> may be in electrical communication with the base electrical contact <NUM> when the flow sensor is connected (e.g., connected, attached, mounted, etc.) to the base <NUM>.

In some non-limiting embodiments or aspects, base <NUM> includes an opening <NUM> configured to receive the flow sensor <NUM>, and the flow sensor <NUM> is configured for sliding engagement with the opening <NUM> of the base <NUM>.

In some non-limiting embodiments or aspects, the at least one sensor <NUM> may include a first ultrasonic transducer or piezo element <NUM> arranged at an upstream position of the flow tube <NUM> and a second ultrasonic transducer or piezo element <NUM> is arranged at a downstream position of the flow tube <NUM>. The first and second piezo elements <NUM> may be configured to transmit a flow signal indicative of a flow of a fluid (e.g., a fluidic medicament, etc.) in the flow tube <NUM>. In some non-limiting embodiments or aspects, the first ultrasonic transducer or piezo element and the second ultrasonic transducer or piezo element <NUM> are annular in shape and encircle the flow tube <NUM> at respective mounting points. In some non-limiting embodiments or aspects, the first ultrasonic transducer or piezo element and the second ultrasonic transducer or piezo element <NUM> are mounted apart a pre-selected distance from each other. The first and second ultrasonic transducers or piezeo elements <NUM> may be in electrical communication with the one or more processors <NUM> (e.g., via the electrical contacts <NUM>, <NUM>, etc.) when the flow sensor <NUM> is connected to the base <NUM>. For example, base <NUM> may interact with the first and second ultrasonic transducers or piezeo elements <NUM> in flow sensor <NUM> to measure displacement of fluid through the flow sensor <NUM>.

In some non-limiting embodiments or aspects, valve <NUM> may be configured transition between a plurality of different states to control at least one of: the flow of the fluid between the fluid inlet <NUM> and the fluid outlet <NUM>, the flow of the fluid between the fluid inlet <NUM> and the fluid injection port <NUM>, the flow of the fluid between the fluid injection port <NUM> and the fluid outlet <NUM>, or any combination thereof. For example, valve <NUM> may include a <NUM>-way stopcock valve, and/or the like.

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

In some non-limiting embodiments or aspects, the one or more processors <NUM> are programmed and/or configured to automatically detect a connection of a syringe <NUM> to the fluid injection port <NUM> of the flow sensor <NUM>. For example, when a user inserts a syringe <NUM> with needle free Luer connector into fluid injection port <NUM>, reader base <NUM> may automatically detect the connection of the syringe to the fluid injection port <NUM> syringe presence and initiates decoding of tag <NUM> (e.g., via the short range wireless communication device, etc.) to record information contents of tag <NUM> (e.g., medication information, etc.). As an example, flow sensor system <NUM> may include an electronic and mechanical interface that interacts with the syringe <NUM> when inserted into fluid injection port <NUM> to detect the presence of the syringe <NUM> upon insertion by the user. In such an example, a mechanical button or switch on flow sensor <NUM> in electrical communication with the one or more processors (e.g., via the electrical contacts <NUM> and <NUM>, etc.) may be actuated by connection/disconnection syringe <NUM> to fluid injection port <NUM> to send a signal to the one or more processors <NUM> indicating the connection/disconnection state of syringe <NUM> to fluid injection port <NUM>. In some non-limiting embodiments or aspects, tag or label <NUM>, which may include an NFC tag embedded in the tag or label <NUM>, may be manually placed on a body of syringe <NUM> using a standard label printer. For example, a label printer can be used to encode the NFC tag at the time of printing. Additionally or alternatively, NFC encoding can 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 <NUM> on syringe <NUM> via a short range wireless communication connection when the short range wireless communication tag <NUM> is brought within a 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 <NUM> on the syringe <NUM> via a short range wireless communication connection in response to the base <NUM> detecting a connection of the syringe <NUM> to the fluid injection port <NUM>. For example, the tag <NUM> may be detected by using NFC when placed radially adjacent to an antenna of the short range wireless communication device in base <NUM>. As an example, base <NUM> may include an integrated NFC antenna positioned radially to record syringe label tag <NUM> and read and decode encoded information therefrom. In such an example, the NFC antenna and label tags are optimized to eliminate false detection of adjacently positioned syringes with NFC tag labels (e.g., an NFC antenna mounted radially in the base <NUM> and label tag <NUM> on the syringe barrel of syringe <NUM> can be used to transmit encoded label information from the syringe label tag <NUM> to the reader base <NUM>, etc.).

In some non-limiting embodiments or aspects, the one or more processors <NUM> may be programmed and/or configured to automatically detect a state of the valve <NUM> when the flow sensor <NUM> is connected to the base <NUM>. For example, base <NUM> may automatically determine a state or position of valve <NUM> when a user manually switches the state or position of the valve <NUM>. As an example, an electronic and/or mechanical interface may interact with the valve <NUM> to monitor valve position or state. In such an example, a mechanical button or switch on flow sensor <NUM> in electrical communication with the one or more processors (e.g., via the electrical contacts <NUM> and <NUM>, etc.) may be actuated by changing the position or state of the valve <NUM> to send a signal to the one or more processors <NUM> indicating the state or position of the valve <NUM> (e.g., indicating that fluid flow is allowed between the fluid inlet <NUM> and the fluid outlet <NUM>, between the fluid inlet <NUM> and the fluid injection port <NUM>, between the fluid injection port <NUM> and the fluid outlet <NUM>, or any combination thereof, etc.).

In some non-limiting embodiments or aspects, the one or more processors <NUM> 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 <NUM> based on the detected state of the valve <NUM>. For example, a user may switch the state or position of the valve <NUM> to enable recording of flow measurement and/or permit IV fluid flow. As an example, the one or more processors <NUM> of base <NUM> may determine when to bookmark flow measurements and ignore IV fluid flow and redundant volume measurements when IV fluid is drawn into the syringe <NUM> then subsequently injected through the flow sensor <NUM>.

In some non-limiting embodiments or aspects, flow sensor <NUM> is inserted in-line with IV line <NUM> between a fluid source and a patient. For example, disposable flow sensor <NUM> can be inserted in-line with IV line <NUM> enabling IV fluid to pass directly to a patient extension line catheter. In some non-limiting embodiments or aspects, valve <NUM> is configured to enable syringe <NUM> to draw IV fluid from IV line <NUM> and deliver the drawn IV fluid through the flow sensor <NUM> to push the fluid to flush the flow sensor <NUM> and extension line of a previously delivered drug volume. In some non-limiting embodiments or aspects, flow sensor <NUM> may be integrated into IV <NUM> (e.g., into an IV extension set line, etc.) without separate detachable connectors. In some non-limiting embodiments or aspects, fluid flow stopcock valves can be positioned in-line before and/or after flow sensor <NUM> and/or additional functionality to incorporate workflow operations can be developed within the interactive display <NUM> of base <NUM>. For example, by positioning flow sensor <NUM> in-line with IV line <NUM>, a dead space issue to due lack of flushing associated with parallel connections can be resolved.

In some non-limiting embodiments or aspects, base <NUM> includes an optical scanner configured to read a bar code label (e.g., a patient wristband bar code label, a bar code label on flow sensor <NUM>, etc.).

In some non-limiting embodiments or aspects, display <NUM> includes a touchscreen display configured to receive user input from a user. For example display <NUM> may include an interactive graphical user interface configured to display a current status of internal functions of reader base <NUM>, a current status of an injection site, and/or a prompt for user interaction, and reader base <NUM> may interact with the user via touchscreen display, audio, voice command, haptic feedback, and/or the like (e.g., to prompt the user on current status and request user input, etc.). Accordingly, by incorporating display <NUM> into base <NUM>, a user need not remove their attention from the base <NUM> to interact with the display <NUM>.

In some non-limiting embodiments or aspects, base <NUM> includes a wireless communication device configured to communicate information associated with the at least one attribute of the fluid in the flow tube <NUM> to remote computing device <NUM>. For example, base <NUM> may communicate information and/or data with remote computing device <NUM> to document drug delivery occurrences into patient medical records (e.g., patient medical records associated with a patient wristband bar code label scanned by the optical scanner of base <NUM>, etc.).

Referring now to <FIG>, <FIG>,<FIG>, <FIG>, <FIG>, and <FIG>, in some non-limiting embodiments or aspects, short range wireless communication device of base <NUM> may include a curved coil antenna <NUM>.

A size of syringe <NUM> may vary (e.g., a syringe size may be in a range from1mL to <NUM>, etc.). A location of short range wireless communication tag <NUM> on syringe <NUM> may vary. For example, a user may attach short range wireless communication tag <NUM> at various different locations on a body of syringe <NUM>. The variability between location of the tag <NUM> and the size of the syringe <NUM> in combination with a curvature of the body syringe <NUM> may make reading encoded data off of tag <NUM> more difficult and/or put considerable burden on a user. For example, HF RFID/NFC works by creating an inductive coupling of magnetic waves in the <NUM> range to power up a HF RFID/NFC tag, which transmits the encoded information back to a transmitting coil antenna. As an example, the transmitting coil antenna should transmit enough energy to power up the tag <NUM>, and a tag coil antenna in tag <NUM> should receive enough energy to power up and transmit the encoded information stored in tag <NUM> back to the transmitting coil antenna. A transmitting coil antenna may be flat and the tag <NUM> may lie parallel to the transmitting coil antenna to power the tag <NUM> up if the tag <NUM> receives enough energy. The energy received may be based a distance of the tag <NUM> to the transmitting coil antenna and/oe an orientation of the transmitting coil antenna with respect to the tag <NUM> (e.g., an offset and/or an angle at which the tag <NUM> faces the transmitting coil antenna, etc.). For example, as the angle between the coil antenna of the tag <NUM> and the transmitting coil antenna becomes closer to <NUM> or <NUM> degrees, antenna energy received by tag <NUM> may be reduced to zero. As an example, a formula for calculating an amount of energy received by tag <NUM> from a transmitting coil antenna may be defined according a cosine (angle). Accordingly, if the angle between the transmitting coil antenna and the coil antenna of the tag <NUM> reaches <NUM> or <NUM> degrees, the energy received by the tag <NUM> is zero and the tag <NUM> cannot power up. In this way, if tag <NUM> is on a syringe <NUM> and the tag <NUM> can be placed anywhere on the syringe <NUM> by a user, there is a possibility that the angle may be close enough to or at the <NUM> energy point where data encoded in the tag <NUM> cannot be read by a short range wireless communication device.

Non-limiting embodiments or aspects of flow sensor system <NUM> including curved coil antenna <NUM> may reduce and/or eliminate a <NUM> and/or <NUM> degree angle between a transmitting coil antenna of the short range wireless communication device of base <NUM> and tag <NUM> on syringe <NUM> by encompassing and/or surrounding syringe <NUM> with the curved coil antenna <NUM>. For example, and referring to <FIG>, curved coil antenna <NUM> may enable magnetic waves to be transmitted out from the short range wireless communication device of base <NUM> in a radial fashion with respect to syringe <NUM> when syringe <NUM> is connected to flow sensor <NUM> and flow sensor <NUM> is connected to base <NUM>, thereby covering a larger area of syringe <NUM> (e.g., depending on a circumferential area of the curved coil antenna <NUM>, an acceptance criteria for successful reads, etc.). As an example, curved coil antenna <NUM> may enable the magnetic waves to be transmitted radially from the short range wireless communication device of base <NUM> to encompass an NFC HF RFID tag on a circular syringe. In contrast, a flat NFC coil antenna may result in the magnetic waves being transmitted orthogonal to the coil antenna, which may result in an NFC HF RFID tag that does not line up with the transmitted magnetic waves (e.g., particularly if the tag is <NUM> degrees to the waves, etc.) not powering up and not transmitting back information encoded on the tag to the transmitting NFC coil antenna. Accordingly, a curved NFC coil antenna may enable magnetic waves to be transmitted in more directions with respect to an NFC HF RFID tag (e.g., for NFC communications based on the NFC standards of ISO14443 and/or ISO15693 which describe physical layer technology and protocol layer technology, etc.), thereby reducing and/or preventing a <NUM> and/or <NUM> degree angle between the transmitting coil antenna and the tag.

In some non-limiting embodiments or aspects, fluid injection port <NUM> of flow sensor <NUM> may extend from flow tube <NUM> in a first direction parallel to a longitudinal axis of the fluid injection port <NUM>, and curved coil antenna <NUM> in the short range wireless communication device of base <NUM> may be radially curved with respect to the longitudinal axis of the fluid injection port <NUM> when the flow sensor <NUM> is connected to the base <NUM>. For example, fluid injection port <NUM> may be configured to connect to syringe <NUM> and, when the syringe <NUM> is connected to the fluid injection port <NUM> of the flow sensor <NUM> and the flow sensor <NUM> is connected to the base <NUM>, curved coil antenna <NUM> may be radially curved around the syringe <NUM> and/or extend in the first direction parallel to the longitudinal axis of the fluid injection port <NUM>.

In some non-limiting embodiments or aspects, as shown for example in <FIG> and <FIG>, curved coil antenna <NUM> extends in a direction parallel to a plane defined by a face of display <NUM> of base <NUM> (e.g., in a direction parallel to a longitudinal axis of syringe <NUM> when syringe <NUM> is connected to flow sensor <NUM> and flow sensor <NUM> is connected to base <NUM>, etc.). In some non-limiting embodiments or aspects, as shown for example in <FIG>, curved coil antenna <NUM> extends in a direction not parallel (e.g., in a direction perpendicular to) a plane defined by a face of display <NUM> of base <NUM> (e.g., in a direction perpendicular to a longitudinal axis of syringe <NUM> when syringe <NUM> is connected to flow sensor <NUM> and flow sensor <NUM> is connected to base <NUM>, etc.). In such example, curved coil antenna <NUM> may at least partially surround syringe <NUM> when syringe <NUM> is connected to flow sensor <NUM> and flow sensor <NUM> is connected to base <NUM>. In some non-limiting embodiments or aspects, a curvature of curved coil antenna may correspond to a circumferential area of a <NUM> syringe, and/or the like.

Referring now to <FIG> and <FIG>, <FIG> and <FIG>are flowcharts 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 steps of the processes are performed (e.g., completely, partially, etc.) by flow sensor system <NUM> (e.g., one or more devices of flow sensor system <NUM>, etc.). In some non-limiting embodiments or aspects, one or more of the steps of the processes are performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including flow sensor system <NUM>, such as remote computing device <NUM> (e.g., one or more devices of a system of remote computing device <NUM>, etc.).

As shown in <FIG>, at step WS5. <NUM>, 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, an optical scanner of base <NUM> (e.g., "Reader" in <FIG>) for disposable flow sensor <NUM> (e.g., "Sensor" in <FIG>) 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, barcode scanning of the disposable flow sensor <NUM> enables base <NUM> (and/or remote computing system <NUM>) to determine whether the disposable flow sensor <NUM> has been used yet or not and, if so, by which patient.

As shown in <FIG>, at step WS4, a process for using a flow sensor system includes scanning a patient label attached to a patient to decode a patient identifier associated with the patient. For example, the optical scanner of base <NUM> for disposable flow sensor <NUM> may scan a patient label attached to a patient (e.g., a patient wristband, a patient barcode, etc.) to decode a patient identifier associated with the patient. As an example, a smart device (e.g., base <NUM>, etc.) may be utilized to electronically scan, with, for example, a barcode scanner, each of a smart IV consumable (e.g., disposable flow sensor <NUM>, etc.) and the patient wristband provided by an EMR vendor. The smart device may communicate patient identifier information (e.g., Patient MRN) and smart IV consumable unique identification number up to a virtual server (e.g., remote computing device <NUM>, etc.) on a hospital network. The virtual server may utilize patient identifier information to generate a bi-directional link to applications on the Hospital Information System associated to that patient relevant to the function of the smart device and smart consumable. Once the bi-directional link is established, the virtual server may associate the link to the smart IV consumable unique identification number and, if the smart device is disassociated, the smart device, or a new different device, can be re-associated by a scan of the smart consumable. In contrast, if the patient is associated by the electronics alone, such as a patient association to a barcode reader, if that device can no longer be used (e.g., runs out of batteries, etc.) re-association by scanning the patient wristband is required and, if the wristband is not accessible (e.g., during surgery, etc.), manual entry of the patient identifier may need to be performed, which may be subject to error. For example, a device may need to be associated with a patient record by having the case assigned to the device by the EMR, manually selecting the patient through the user interface on the device or associating the smart device directly to the patient through electronic scan or otherwise. Further, if not properly disassociated, a device may also be at risk of utilization on the incorrect patient recording information to the wrong patient record.

As shown in <FIG>, at step WS5. <NUM>, a process for using a flow sensor system includes connecting the disposable flow sensor to the base. For example, disposable flow sensor <NUM> may be connected to base <NUM>.

As shown in <FIG>, at step WS5. <NUM>, a process for using a flow sensor system includes integrating the disposable flow sensor into an IV line. For example, disposable flow sensor <NUM> may be integrated into IV line <NUM>.

In some non-limiting embodiments or aspects, and referring now to <FIG>, disposable flow sensor <NUM> is integrated into IV line <NUM> before scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor <NUM> to the base <NUM>. For example, integrating disposable flow sensor <NUM> into IV line <NUM> before scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor <NUM> to the base <NUM> may enable a clinician to associate the patient when performing other positive patient identification and/or to scan and attach the disposable flow sensor <NUM> in one more contiguous step which adds value, for example, when setting up a patient for a procedure in an operating room. As an example, scanning the patient ID prior to connecting may ensure that the IV line <NUM> does not hinder a user in scanning the patient ID, which may be ideal for outpatients where a new IV line is built with the disposable flow sensor <NUM> in place for the procedure.

In some non-limiting embodiments or aspects, and referring now to <FIG>, disposable flow sensor <NUM> is integrated into IV line <NUM> after scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor <NUM> to the base <NUM>. For example, integrating disposable flow sensor <NUM> into IV line <NUM> after scanning the flow sensor label, scanning the patient label, and connecting the disposable flow sensor <NUM> to the base <NUM> may enable a clinician to prepare the base <NUM> and disposable flow sensor <NUM> 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 an inpatient with a pre-existing IV saving steps that need not be performed in the presence of the patient.

As shown in <FIG>, at steps WS4, WS5. <NUM>, and/or WS5. <NUM>, 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 <NUM> may communicate the flow sensor identifier and the patient identifier to remote computing device <NUM>, and remote computing device <NUM> may associate the flow sensor identifier with the patient identifier in a database.

In some non-limiting embodiments or aspects, and referring now to <FIG>, base <NUM> may communicate, to remote computing device <NUM>, a request for a status of the disposable flow sensor <NUM> associated with the flow sensor identifier and receive, from remote computing device <NUM>, an indication of the status of the disposable flow sensor <NUM> associated with the flow sensor identifier. For example, the indication of the status of the disposable flow sensor <NUM> may include an indication of whether the flow sensor identifier of the disposable flow sensor <NUM> is associated with the patient identifier of the patient.

In some non-limiting embodiments or aspects, and still referring to <FIG>, base <NUM> may communicate, to remote computing device <NUM>, a base identifier associated with the base <NUM> in the request for the status of the disposable flow sensor <NUM> associated with the flow sensor identifier, and remote computing device <NUM> may associate the base identifier with the flow sensor identifier and the patient identifier.

As shown in <FIG>, at steps WS4 and/or WS6, a process for using a flow sensor system includes communicating a request for information associated with the patient associated with the patient identifier, receiving the information associated with the patient, and displaying the information associated with the patient. For example, and referring also to <FIG>, base <NUM> may communicate, to remote computing device <NUM>, a request for information associated with the patient associated with the patient identifier, receive, from remote computing device <NUM>, the information associated with the patient, and display, with a display, the information associated with the patient.

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 medication doses pending for the patient.

In some non-limiting embodiments or aspects, and still referring to <FIG>, a short range wireless communication device of base <NUM> may scan a short range wireless communication tag <NUM> attached to a syringe <NUM> to decode a medication identifier associated with a medication in the syringe <NUM>, and the base <NUM> may compare the medication identifier to the at least one of the list of medication allergies associated with the patient and the list of medication doses pending for the patient. For example, a display <NUM> of the base <NUM> may display an alert associated with 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 a NFC tag.

Claim 1:
A system comprising:
a flow sensor (<NUM>) including:
a flow tube (<NUM>) including a fluid inlet (<NUM>) at a first end of the flow tube, a fluid outlet (<NUM>) at a second end of the flow tube opposite the first end of the flow tube, a fluid injection port (<NUM>) between the first end and the second end of the flow tube, and a valve (<NUM>) configured to control a flow of a fluid in the flow tube;
at least one sensor (<NUM>) configured to characterize at least one attribute of the fluid in the flow tube; and
a flow sensor electrical contact (<NUM>) in electrical communication with the at least one sensor; and
a base (<NUM>) configured to connect to the flow sensor, wherein the base includes:
one or more processors;
a base electrical contact (<NUM>) in electrical communication with the one or more processors;
a short range wireless communication device; and
a display (<NUM>),
wherein the flow sensor electrical contact is in electrical communication with the base electrical contact when the flow sensor is connected to the base,
wherein the 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,
characterized in that
the 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.