Some current urine monitoring systems use weight based methodologies to determine urine volume and urine flow rate over time. A fluid collection container may be suspended from a weighing device and as urine is captured by the fluid collection container, the weight of the fluid collection container increases. The weighing device may be configured to detect the increase in the weight of the fluid collection container. However, most urine monitoring systems do not travel with a patient as the patient is moved through a hospital setting, requiring clinicians to suspend urine monitoring until a patient is stationed in one location. If a patient has to move frequently within the hospital (e.g., multiple surgeries), critical patient data may not be captured. It would be beneficial to the patient and the clinician to be able to monitor urine output during the patient's entire stay. Disclosed herein is an automated urinary output monitoring system and method of use that address the foregoing.
Disclosed herein is an automated urinary output monitoring system including an automated urinary output monitoring device. The device includes a device body having a mounting system coupled thereto. The mounting system includes a mounting surface rotatably coupled with the device body, where the mounting surface is configured to secure the automated urinary output monitoring device to an external stabilizing surface. The mounting system further includes a buffering region disposed between the mounting surface and the device body, where the buffering region is configured to isolate the device body from vibrations of the external stabilizing surface. The device further includes a load cell assembly operatively coupled with the device body having a fluid collection bag attachment coupled therewith, where the fluid collection bag attachment is configured to suspend a fluid collection bag therefrom.
The system further includes a console communicatively coupled with the load cell assembly, where the console including one or more processors, and non-transitory computer readable medium having logic stored thereon that, when executed by the one or more processors, performs operations of the system. The operations include (i) receiving a load value applied to the fluid collection bag attachment by the fluid collection bag, (ii) calculating a volume of urine collected within the fluid collection bag based on the load value, and (iii) depicting the volume of urine on a display of the system.
In some embodiments, the mounting system extends laterally away from a back panel of the device body. In some embodiments, the mounting surface includes a number of suction cups, clamps, magnets, or an adhesive configured for securing the mounting surface to the stabilizing surface. In some embodiments, the automated urinary output monitoring device is configured to rotate with respect to the mounting surface due to gravity to maintain a vertical orientation of the device body during use.
In some embodiments, the buffering region is configured to transition between a non-compressed configuration and a compressed configuration in response to a lateral movement of the stabilizing surface. In some embodiments, the mounting surface rotates about an axis of rotation extending through the buffering region.
In some embodiments, the automated urinary output monitoring device includes a front panel including the display and an input interface, where each are in communication with the console. In some embodiments, the input interface includes a plurality of buttons.
In some embodiments, the automated urinary output monitoring device includes one or more module inputs configured to define communication between one or more modules and the console.
In some embodiments, the system receives electrical power from an external power source.
In some embodiments, the operations further include correlating the volume of urine with a time of day and depicting the time of day along with the volume of urine on the display of the system.
In some embodiments, the automated urinary output monitoring device includes a tube holder coupled with the device body, where the tube holder is configured to secure a portion of a drainage tube of the fluid collection bag to the device body.
In some embodiments, the one or more modules includes a temperature sensor coupled with the tube holder, where the temperature sensor is configured to determine a temperature of urine disposed with in the drainage tube, and the operations further include obtaining a temperature measurement of the urine disposed with in the drainage tube and depicting the temperature measurement on the display.
In some embodiments, the automated urinary output monitoring device includes the securing attachment extending upward away from a top side of the device body, where the securing attachment is configured to suspend the automated urinary output monitoring device from a bed rail.
In some embodiments, the console is configured to wirelessly communicate with an external computing device, where the external computing device includes one or more of a tablet, a cell phone, or an electronic medical record (EMR) system, and the operations further include at least one of (i) receiving patient information from the external computing device or (ii) transmitting urine output monitoring data to the external computing device.
In some embodiments, the operations further include receiving a plurality of patient profiles from the EMR system and storing the plurality of the patient profiles on the non-transitory computer readable medium.
In some embodiments, the operations further include depicting patient profile information on the display.
Also disclosed herein is a method of monitoring urine output from a patient performed by a urine output monitoring system. According to some embodiments, the method includes (i) rotating a device body of the urine output monitoring system about an axis of rotation with respect to a mounting surface of the urine output monitoring system so that the device body is vertically oriented; (ii) obtaining a load value from a load cell assembly of the urine output monitoring system, where the load value is defined by a urine collection bag coupled with load cell assembly and the urine collection bag includes a volume of urine collected therein; (iii) calculating the volume of urine based on the load value; (iv) correlating the volume of urine with a time of day; (v) receiving patient identification for the patient from an EMR system; and (vi) depicting the volume of urine, the time of day, and the patient identification on a display of the urine output monitoring system.
In some embodiments, the method further includes transmitting the volume of urine, the time of day, and the patient identification to the EMR system.
In some embodiments, the method further includes obtaining a temperature measurement of the urine disposed within a drainage tube of the urine output monitoring system and depicting the temperature measurement on the display.
These and other features of the concepts provided herein will become more apparent to those of skill in the art in view of the accompanying drawings and following description, which describe particular embodiments of such concepts in greater detail.
A more particular description of the present disclosure will be rendered by reference to specific embodiments thereof that are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. Example embodiments of the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Before some particular embodiments are disclosed in greater detail, it should be understood that the particular embodiments disclosed herein do not limit the scope of the concepts provided herein. It should also be understood that a particular embodiment disclosed herein can have features that can be readily separated from the particular embodiment and optionally combined with or substituted for features of any of a number of other embodiments disclosed herein.
Regarding terms used herein, it should also be understood the terms are for the purpose of describing some particular embodiments, and the terms do not limit the scope of the concepts provided herein. Ordinal numbers (e.g., first, second, third, etc.) are generally used to distinguish or identify different features or steps in a group of features or steps, and do not supply a serial or numerical limitation. For example, “first,” “second,” and “third” features or steps need not necessarily appear in that order, and the particular embodiments including such features or steps need not necessarily be limited to the three features or steps. Labels such as “left,” “right,” “top,” “bottom,” “front,” “back,” and the like are used for convenience and are not intended to imply, for example, any particular fixed location, orientation, or direction. Instead, such labels are used to reflect, for example, relative location, orientation, or directions. Singular forms of “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
The term “logic” may be representative of hardware, firmware or software that is configured to perform one or more functions. As hardware, the term logic may refer to or include circuitry having data processing and/or storage functionality. Examples of such circuitry may include, but are not limited or restricted to a hardware processor (e.g., microprocessor, one or more processor cores, a digital signal processor, a programmable gate array, a microcontroller, an application specific integrated circuit “ASIC”, etc.), a semiconductor memory, or combinatorial elements.
Additionally, or in the alternative, the term logic may refer to or include software such as one or more processes, one or more instances, Application Programming Interface(s) (API), subroutine(s), function(s), applet(s), servlet(s), routine(s), source code, object code, shared library/dynamic link library (dll), or even one or more instructions. This software may be stored in any type of a suitable non-transitory storage medium, or transitory storage medium (e.g., electrical, optical, acoustical or other form of propagated signals such as carrier waves, infrared signals, or digital signals). Examples of a non-transitory storage medium may include, but are not limited or restricted to a programmable circuit; non-persistent storage such as volatile memory (e.g., any type of random access memory “RAM”); or persistent storage such as non-volatile memory (e.g., read-only memory “ROM”, power-backed RAM, flash memory, phase-change memory, etc.), a solid-state drive, hard disk drive, an optical disc drive, or a portable memory device. As firmware, the logic may be stored in persistent storage.
The term “computing device” should be construed as electronics with the data processing capability and/or a capability of connecting to any type of network, such as a public network (e.g., Internet), a private network (e.g., a wireless data telecommunication network, a local area network “LAN”, etc.), or a combination of networks. Examples of a computing device may include, but are not limited or restricted to, the following: a server, an endpoint device (e.g., a laptop, a smartphone, a tablet, a “wearable” device such as a smart watch, augmented or virtual reality viewer, or the like, a desktop computer, a netbook, a medical device, or any general-purpose or special-purpose, user-controlled electronic device), a mainframe, internet server, a router; or the like.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the art.
The load cell assembly 140 may be integrated into the bottom side 116 of the device 110 or may be located within the device body 112. The load cell assembly 140 is communicatively coupled with a console 150 of the system 100 wherein the load cell assembly 140 is configured to communicate load cell values (measurements) to the console 150. The load cell assembly 140 may be wired to the console 150 or may be wirelessly coupled with the console 150. The console 150 may reside within the device body 112. In some embodiments, the console 150 may be in wireless communication with an external computing device (e.g., a stand-a-alone computer, a tablet, or cell phone) or electronic medical record (EMR) system so that the console 150 may transmit load cell values to the computing device or the EMR system. Exemplary wireless communication modalities can include WiFi, Bluetooth, Near Field Communications (NFC), cellular Global System for Mobile Communication (“GSM”), electromagnetic (EM), radio frequency (RF), combinations thereof, or the like.
The front panel 118 of the device 110 may include a display 170 integrated into or coupled to the device body 112. The display 170 may be in communication with the console 150 and may be configured to display determined load cell values or other information pertaining the monitoring of urine output. In some embodiments, the front panel 118 of the device 110 may include an input interface 126 in communication with the console 150. In some embodiments, the input interface 126 may include a plurality of buttons 126A configured to allow a user to input information into the system 100 and/or select information to be projected on the display 170. In some embodiments, the plurality of buttons 126A may be organized into a keypad array, positioned around the display 170, or a combination thereof.
The device 110 includes a securing attachment 124 configured to detachably couple the device 110 to a stabilizing surface 190. In some embodiments, the stabilizing surface 190 may include a rail of a hospital bed, an IV pole or the like. In some embodiments, the securing attachment 124 may include a hook, a clamp, or the like. The securing attachment 124 may be configured to allow the device 110 to be suspended from (i.e., hung from) the stabilizing surface 190 so that the device 110 is disposed in a vertical orientation, where the vertical orientation enables the load cell assembly 140 to precisely determine load values applied to the fluid collection bag attachment 122.
The device 110 may include a tube holder 130 configured for securing a portion of drainage tube 133 to the body 112. The tube holder 130 may be configured to optimally position and hold a drainage tube 133 so that movement of the patient does not affect the load applied to the fluid collection bag attachment 122. If the drainage tube is not adequately positioned and secured, the shape or strain of the drainage tube 1330 may alter the load obtained by the load cell assembly 140, confounding the determination of load cell values.
In some embodiments, the one or more modules may include a temperature sensor 127 coupled with the tube holder 130. The temperature sensor 127 may be configured to determine the temperature of the volume of fluid as the volume of fluid moves through the drainage tube 133 to the fluid collection bag 132.
In some embodiments, the fluid collection bag attachment 122 being fixed to the bottom side 116 of the device body 112 or the fluid collection bag attachment 122 be integrated into or formed into the device body 112. In some embodiments, the fluid collection bag attachment 122 is fixed directly underneath the device body 112, equidistant between the front panel 118 and the back panel 120. The fluid collection bag attachment 122 and the device body 112 may be formed as a single piece. In some embodiments, the device body 112 and the fluid collection bag attachment 122 may be formed of a thermoplastic material (e.g., polyvinyl chloride, polyethylene, polypropylene, polystyrene, polyurethane, nylon, or any other suitable thermoplastic material) formed by 3D printing, injection molding or the like. Advantageously, the device body 112 and the fluid collection bag attachment 122 being formed as a singular piece removes attachment/reattachment of the fluid collection bag attachment 122 and rotation of the fluid collection bag 132 around the fluid collection bag attachment 122, leading to longevity of the device 110 and consistency of the load cell assembly 140 detecting the load of the fluid collection bag attachment 122. In an embodiment, the load cell assembly 140 may be integrated into the fluid collection bag attachment 122. Advantageously, fixing the fluid collection bag attachment 122 to the device body 112 ensures both consistent placement of the fluid collection bag 132 on the fluid collection bag attachment 122 and that the load cell assembly 140 is protected and consistently able to transmit load values to the console 150 during multiple deployments of the system 100 or multiple changes of the fluid collection bag 132.
The mounting system 380 couples the device 310 to the stabilizing surface 190 along the axis 381. In some embodiments, the mounting system 380 extends laterally from a back panel 320 of the device 310. During use, the device 310 may be coupled to the stabilizing surface 190 via the securing attachment 324, the mounting system 380, or a combination thereof. In some embodiments, the stabilizing surface 190 be flat or may include portions of a hospital bed, a wall, an IV stand, a bed pole mount, or the like. In some embodiments, the mounting surface 382 may include a mounting mechanism 383 that may include a number (e.g., 1, 2, 3, 4 or more) of suction cups, clamps or magnets. In some embodiments, portions of the mounting surface 382 may include an adhesive configured to secure the mounting system 380 to the stabilizing surface 190. The mounting system 380 may be configured to prevent any sag or rotation of the device 310 except about the axis 381.
The mounting system 380 may also be configured to isolate the load cell system 340 from vibrations of the stabilizing surface 190. The mounting system 380 may include a buffering region 384 disposed between the back panel 320 and the mounting surface 382. The mounting surface 382 may be configured to couple the device 310 to a surface, including the stabilizing surface 190. Advantageously, the mounting surface 382 positions the device 310 to maintain the device in the vertical orientation so the fluid collection bag attachment 322 is suspended in line with the load cell assembly 340 and so that the stability of the device 310 in enhanced, e.g., isolated from vibrational movement of the stabilizing surface 190.
In some embodiments, the buffering region 384 buffers lateral movement of the device 310. In some embodiments, the buffering region 384 may include a spring. In some embodiments, the buffering region 384 may include a damping material such as a rubber or foam material. In some embodiments, the buffering region 384 may also be configured to allows the device 310 to move or rotate axially around the axis 381, allowing the device 310 to be maintained in a vertical orientation regardless of the orientation of the stabilizing surface 190. In some embodiments, the buffering region 384 may be configured (e.g., include stops) to limit rotation of the device 310 around the axis 381. In some embodiments, the user or the weight of the fluid collection bag 132 (see
In some embodiments, the device 310 may include an accelerometer (not shown) located within the device 310 that may be configured to determine the orientation of the device 310. The accelerometer may be in communication with the console 350 so as to receive accelerometer values from the accelerometer, where the console 350 may use the accelerometer values adjust load values obtained by the load cell assembly 340 to enhance the measurement accuracy of the load applied to the load cell assembly 340 and calculate the volume of fluid within the fluid collection bag 132 taking into account the orientation of the device 310. In some embodiments, the device 310 may include a gyroscope (not shown) that may be configured to stabilize the load cell assembly 340, such as maintain the device 310 in the vertical orientation and/or inhibit vibrations of the device 310 from affecting the ability of the load cell assembly 340 to detect load cell values. In some embodiments, the
For illustrative purposes, logic of the console 150 may be divided into a number of logic modules that may include load cell receiving logic 458, load cell correlation logic 460, module receiving logic 462, input interface receiving logic 464, display logic 466, and a data store 468.
The load cell receiving logic 458 may generally be configured to receive electrical signals (i.e., load cell values) from the load cell assembly 140. In some embodiments, the load cell receiving logic 458 may be configured to constantly (e.g., at a high sampling rate) receive the load cell values. In some embodiments, the sampling rate may be defined by the user, such as a sampling rate of every 5 minutes for example. In some embodiments, the load cell receiving logic 458 may be configured to receive the load cell values upon a defined change or difference from a previous load cell values.
The load cell correlation logic 460 may be configured to correlate the received load cell value with a volume of urine collected within the fluid collection bag 132. In some embodiments, the load cell correlation logic 460 may be configured correlate the volume of urine with a time of day value. In other words, the load cell correlation logic 460 may attach time stamp to each the volume of urine. By way of summary, a volume of urine may be calculated for each load cell value, and each volume of urine may include an attached time stamp.
The module receiving logic 462 may be configured to receive data from any of the one or more modules coupled with module inputs 128. The module receiving logic 462 may also be configured to receive data wirelessly from an external source, such as the external computing device or the EMR system. For example, the module receiving logic 462 may receive patient identification information from the EMR system and the volume of urine values to a specific patient. In some embodiments, the module receiving logic 462 may receive patient identification information for a plurality of patients and the patient information may be stored in the data store 468. The module receiving logic 462 may also be configured to receive/obtain temperature data from the temperature sensor 127 and correlate the temperature data with the volume of urine values.
In some embodiments, the input interface receiving logic 464 may be configured to receive input from the user via the input interface 126 including the plurality of buttons 126A. The input interface receiving logic 464 may, in response to the input, change a mode of operation, such as change the load cell sampling rate, for example. The user may also input various settings, such as a volume capacity for the fluid collection bag 132. The user may also define a number of alert limits for the system, such as a leak alert associated in a decrease in load cell values, or a low urine output rate, for example.
In some embodiments, the display logic 466 may be configured to project urine output information on the display 170, such as the determined load cell values, the correlated volume values, the time of day values, the patient identification information, the urine temperature data, and/or module data from the one or more modules. The display logic 466 may also be configured to transmit the urine output information to the external computing device or the EMR system.
In some embodiments, the data store 468 may be configured to store the detected load cell values, the correlated volume values, the time of day values, and the module data values. The data store 468 may be configured to store multiple patient profiles as may be input by the user or received from the EMR system. In some embodiments, the data store 468 may be configured to record and store all data received, generated, obtained, or otherwise utilized by the system 100.
While some particular embodiments have been disclosed herein, and while the particular embodiments have been disclosed in some detail, it is not the intention for the particular embodiments to limit the scope of the concepts provided herein. Additional adaptations and/or modifications can appear to those of ordinary skill in the art, and, in broader aspects, these adaptations and/or modifications are encompassed as well. Accordingly, departures may be made from the particular embodiments disclosed herein without departing from the scope of the concepts provided herein.
This application claims the benefit of priority to U.S. Provisional Application No. 63/237,085, filed Aug. 25, 2021, which is incorporated by reference in its entirety into this application.
Number | Date | Country | |
---|---|---|---|
63237085 | Aug 2021 | US |