Portable anesthesia monitoring device for non-operating room anesthesia
The portable anesthesia monitoring device addresses the mobility and data limitations of existing equipment by integrating syringe pumps and sensors into a compact unit for real-time patient monitoring and controlled fluid delivery in non-operating room settings.
Patent Information
- Application Number
- PCT/US2025/025751
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-04-23
- Filing Date
- 2025-04-22
- Publication Date
- 2025-10-30
Smart Images

Figure US2025025751_30102025_PF_FP_ABST
Abstract
Description
PORTABLE ANESTHESIA MONITORING DEVICE FOR NON-OPERATING ROOM ANESTHESIACROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 637,471, filed April 23, 2024, the entire contents of which are incorporated herein by reference.BACKGROUND
[0002] About one-third of all general anesthesia cases occur outside of the operating room. Nonoperating room anesthesia (NORA) is increasing in prevalence as advances are made in modern medicine. Due to these innovations, many minimally invasive procedures are being performed as ambulatory surgeries, which require the use of anesthetic equipment in outpatient settings. However, existing anesthesia equipment is specifically designed to be used in inpatient operating room settings and does not fit the needs of ambulatory care centers. Current anesthetic administration devices used in outpatient care are bulky, lack mobility, and do not provide a comprehensive data set necessary to monitor patients.
[0003] Therefore, considering these limitations and their impacts on patient outcomes, there is a need for improved anesthetic devices.SUMMARY
[0004] Disclosed herein are improved methods, systems, and devices for anesthesia administration and monitoring in non-operating rooms. The disclosed methods, systems, and devices may include a syringe pump to control the flow of anesthesia (or other fluid therapeutics). The disclosed methods, systems, and devices may remotely monitor patient vitals. Thus, an improved method, system, and device is disclosed that allows for easy transport and setup in a non-operating room setting.
[0005] According to one implementation, a portable anesthesia monitoring device is disclosed. The device includes a housing defining a front side and a back side. The device further includes a screen on the front side of the housing configured to display information. The device further includes a first syringe channel defined on the back side of the housing, the first syringe channel configured to retain a first syringe therein. The device further includes a flange retainer coupled to and extending at least partially into the first syringe channel. The flange retainer is configured to limit motion of a flange of the first syringe relative to the first syringe channel. The devicefurther includes a plunger retainer on a first side of the housing adjacent to the first syringe channel. The plunger retainer is moveable relative to the flange retainer and configured to engage a plunger of the first syringe. The device further includes a linear actuator coupled between the flange retainer and the plunger retainer and configured to move the plunger retainer relative to the flange retainer. Movement of the plunger retainer is configured to move the plunger of the first syringe to change an internal volume of the first syringe. At least one sensor is coupled to the housing via at least one port defined therein. The at least one sensor is configured to communicate patient data to the device. The device further includes a controller in electrical communication with each of the screen, the linear actuator, and the at least one sensor. The controller is configured to (i) continuously display patient data from the at least one sensor on the screen and (ii) initiate movement of the plunger retainer to expel a fluid from the first syringe at a controlled flow rate.
[0006] In some implementations, the portable anesthesia monitoring device further includes a control knob extending from a portion of the housing. The control knob is operatively connected to the linear actuator. The controller is configured to receive an input from the control knob and adjust a speed of the linear actuator to adjust the flow rate of the fluid expelled from the first syringe.
[0007] In some implementations, the screen is further configured to display the flow rate of the fluid expelled from the first syringe based on a speed of the linear actuator.
[0008] In some implementations, the portable anesthesia monitoring device further includes a syringe retention tab extending from a portion of the first syringe channel and configured to abut an outer diameter of the first syringe. The syringe retention tab includes a potentiometer to facilitate measurement of the outer diameter of the first syringe. The controller is configured to receive the measured outer diameter of the first syringe from the syringe retention tab and calculate the flow rate of the fluid expelled from the first syringe based on the measured outer diameter and a speed of the linear actuator.
[0009] In some implementations, the portable anesthesia monitoring device further includes a second syringe channel defined on the back side of the housing adjacent to the first syringe channel. The second syringe channel is configured to retain a second syringe therein. A second flange retainer is coupled to and extends at least partially into the second syringe channel, the second flange retainer configured to limit motion of a flange of the second syringe relative to the second syringe channel. A second plunger retainer is on a first side of the housing adjacent to thesecond syringe channel. The second plunger retainer is moveable relative to the second flange retainer and configured to engage a plunger of the second syringe. A second linear actuator is coupled between the second flange retainer and the second plunger retainer and configured to move the second plunger retainer relative to the second flange retainer. Movement of the second plunger retainer moves the plunger of the second syringe to change an internal volume of the second syringe and expel a fluid from the second syringe at a controlled flow rate.
[0010] In some implementations, the fluid is a therapeutic fluid configured to sedate a patient via an intravenous connection.
[0011] In some implementations, the portable anesthesia monitoring device further includes a mounting device extending from a portion of a housing to removably couple the device to a rigid object.
[0012] In some implementations, the at least one sensor includes a pulse oximetry sensor, a heart rate sensor, a blood pressure sensor, or a respiration sensor, and wherein more than one patient data set is delivered to and displayed on the screen in real time.
[0013] In some implementations, the controller is in communication with a remote device, the controller configured to communicate patient data from the at least one sensor and flow rate information related to the first syringe to the remote device for display thereon.
[0014] In some implementations, the portable anesthesia monitoring device further includes a pressure sensor configured to be in fluid communication with the first syringe, wherein the controller receives pressure data from the pressure sensor and initiates an alert if a pressure measurement exceeds a threshold value.
[0015] According to another implementation, a portable anesthesia device is disclosed. The device includes a syringe retainer, a control knob, at least one patient sensor, a screen, and a controller. The syringe retainer has a linear actuator coupled to a first portion and a second portion of the syringe retainer. The syringe retainer is configured to retain a first syringe having a first therapeutic fluid therein. Movement of the first portion relative to the second portion is configured to expel the first therapeutic fluid from the first syringe. The control knob extends from a portion of the device, the control knob being operatively connected to the linear actuator. Movement of the control knob in a first direction adjusts a speed of the linear actuator which is configured to adjust a flow rate of the first therapeutic fluid expelled from the first syringe. The at least onepatient sensor is coupled to and extends from at least one port of the device. The screen is configured to display at least (i) patient monitoring data from the at least one patient sensor, and (ii) the flow rate of the first therapeutic fluid expelled from the first syringe based on movement information from the linear actuator. The controller is in electrical communication with the linear actuator, the control knob, the at least one patient sensor, and the screen. The controller is configured to facilitate the display of patient monitoring data and flow rate information on the screen.
[0016] In some implementations, the controller includes a processor and a memory storing instructions thereon that, when executed by the processor, cause the processor to receive and interpret patient monitoring data from the at least one patient sensor and continuously update a display of patient monitoring data on the screen.
[0017] In some implementations, the controller includes a processor and a memory storing instructions thereon that, when executed by the processor, cause the processor to calculate the flow rate of the first therapeutic fluid expelled from the first syringe based on displacement data from the linear actuator of the syringe retainer.
[0018] In some implementations, the portable anesthesia monitoring device further includes a syringe size gauge coupled to a portion of the syringe retainer and configured to measure a diameter of the first syringe therein. The processor receives a measured diameter of the first syringe from the syringe size gauge and updates the calculated flow rate of the first therapeutic fluid based in part on the measured diameter of the first syringe.
[0019] In some implementations, the portable anesthesia monitoring device further includes a scanning module adjacent to the syringe retainer, the scanning module configure to retrieve information from a first syringe deposited into the syringe retainer. The information received by the scanning module includes a size of the first syringe or a composition of the first therapeutic fluid therein.
[0020] In some implementations, the memory includes a library of therapeutic compositions and syringe sizes that inform the flow rate information displayed on the screen.
[0021] In some implementations, the first therapeutic fluid is an intravenous anesthetic.
[0022] In some implementations, the at least one patient sensor includes a pulse oximetry sensor, a heart rate sensor, a blood pressure sensor, or a respiration sensor, and wherein more than one set of patient monitoring data is delivered to and displayed on the screen in real time.
[0023] In some implementations, the controller is in communication with a remote device, the controller configured to communicate patient monitoring data from the at least one sensor and flow rate information related to the first syringe to the remote device for display thereon.
[0024] In some implementations, the screen is a touch screen defining a user interface, wherein the user interface includes one or more controls configured to change the patient monitoring data displayed on the screen.
[0025] This summary is illustrative only and is not intended to be in any way limiting. Other aspects, features, and advantages of the devices or processes described herein will become apparent in the detailed description set forth herein, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements.BRIEF DESCRIPTION OF DRAWINGS
[0026] The systems, methods, and devices are explained in even greater detail in the following drawings. The drawings are merely exemplary and certain features may be used singularly or in combination with other features. The drawings are not necessarily drawn to scale.
[0027] FIG. 1 is an isometric view of a portable therapeutic delivery and patient monitoring device, according to one implementation.
[0028] FIG. 2 is another isometric view of the device of FIG. 1.
[0029] FIG. 3 is a top view of the device of FIG. 1.
[0030] FIG. 4 is a back view of the device of FIG. 1.
[0031] FIG. 5 is a side view of the device of FIG. 1.
[0032] FIG. 6 is a front view of the device of FIG. 1.
[0033] FIG. 7 is another side view of the device of FIG. 1.
[0034] FIG. 8 is a bottom view of the device of FIG. 1.
[0035] FIG. 9 is a cross-sectional view of the device taken along line 9-9 in FIG. 5.
[0036] FIG. 10 is a cross-sectional view of the device taken along line 10-10 in FIG. 5.
[0037] FIG. 11 is a system diagram showing the device of FIG. 1 along with the associated control system, according to one implementation.
[0038] FIG. 12 shows another portable therapeutic delivery and patient monitoring device with an active screen showing patient data and other information, according to one implementation.DETAILED DESCRIPTION
[0039] Following below are more detailed descriptions of concepts related to, and implementations of, methods, apparatuses, and systems for compact and transportable anesthesia administration with remote patient monitoring. The figures illustrate exemplary implementations in detail and the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. The terminology used herein is for the purpose of description only and should not be regarded as limiting.
[0040] General anesthesia administration is a medical procedure used to sedate patients undergoing a wide range of clinical treatments. Traditionally, anesthesia is used in operating rooms for complex surgeries. However, anesthesia is often used for less invasive procedures conducted outside traditional operating room settings, giving rise to the concept of non-operating room anesthesia (NORA).
[0041] Current anesthesia equipment primarily caters to operating room needs and is relatively bulky, posing spatial challenges when deployed in NORA settings. In some settings, placing current operating room anesthesia equipment in a non-operating room would occupy 20% of the available space. This layout is impractical because it must accommodate other medical equipment, healthcare personnel, patients, their families, and the procedure.
[0042] Therefore, this disclosure presents a NORA device tailored to the spatial constraints of nonoperating rooms while facilitating anesthesiologists during the procedures. The device also displays essential information on a portable device, granting anesthesiologists the flexibility to move around the room while monitoring the patient. This approach not only enhances patient care but also gives other medical staff greater access to the patient.
[0043] In some existing systems, to enable anesthesia administration beyond the operating room, anesthesiologists rely on smaller devices for sensor readings. However, this approach has limitations. First, these devices remain heavy and cumbersome, hindering mobility during procedures. Second, they lack integration into a singular output system, making simultaneous monitoring challenging. In addition, the sole available monitor in non-operating room settings, positioned above the patient's bed, presents visibility issues because anesthesiologists often work at the patient's head. Another problem arises with syringe pumps used for medication delivery, as they lack feedback data to confirm accurate medicine flow rates.
[0044] Therefore, this disclosure presents a comprehensive device that integrates blood pressure, ECG, pulse oximetry (or other sensors), and syringe pump flow feedback sensors, with output displayed on a single portable screen. This device may be used by anesthesiologists in a hospital setting serving patients undergoing anesthesia outside the operating room.Example System and Device
[0045] FIGS. 1-10 show various views of a portable anesthesia monitoring device 100, according to one implementation. FIG. 11 shows the portable anesthesia monitoring device 100 and an associated controller 200, wherein the device 100 is coupled to a patient 90. In general, the device 100 provides for controlled application of a therapeutic fluid (e.g., a sedative, such as Propofol) to the patient 90 with simultaneous monitoring of patient data on the same device 100. The device 100 is generally a compact and portable device that can be easily transported from one room to another (e.g., in an anesthesiologist’s bag) and easily set up for different patients. The device 100 may include a power source (e.g., a battery pack).
[0046] As shown in FIG. 1, the anesthesia monitoring device 100 includes a housing 102. The housing 102 includes a front side 104 and a back side 106 opposite from the front side 104. The housing further includes a first side 108 and a second side 110 opposite from the first side 108. The first and second sides 108, 110 extend between the front and back sides 104, 106. The housing 102 may have an ergonomic and portable shape (e.g., without sharp comers). The housing 102 may include drop- and shock-proof features (e.g., rubberized edges).
[0047] The device 100 further includes a screen 112 on the front side 104 of the housing 102. The screen 112 is configured to display information. For example, the screen 112 may be an LCD screen or an LED screen capable of displaying visual information to a user. As elsewhere described herein, the screen 112 may include a user interface (UI) configured to both communicateinformation to a user and receive user input. For example, the screen 112 may have touchscreen capabilities, such as a resistive or capacitive touchscreen features, which may include multi-touch features and / or haptic feedback. The screen 112 and the user interface thereof may be reconfigurable by a user (e.g., to display different data sets or information). The device 100 may further include a speaker (not shown) to provide audio feedback to a user in conjunction with the visual feedback on the screen 112.
[0048] As best shown in FIGS. 3 and 4, the device 100 further includes a mounting arm 114. The mounting arm 114 extends from the first side 108 of the housing 102. The mounting arm 114 includes an adjustable fastener 116 extending into a mounting channel 118. The mounting arm 114 is configured to attach the device 100 to a rigid object or surface. For example, an IV pole may fit within the mounting channel 118. The adjustable fastener 116 is moveable to engage the IV pole, securely attaching the mounting arm 114 and the device 100 to the IV pole (or other rigid object adjacent to the patient 90 or patient support surface).
[0049] As best shown in FIGS. 2 and 4, the device 100 further includes two syringe channels, including a first syringe channel 120a and a second syringe channel 120b. As shown, a first syringe 10a is disposed within the first syringe channel 120a, and a second syringe 10b is disposed within the second syringe channel 120b. The first syringe channel 120a is substantially similar in structure and in function to the second syringe channel 120b. The first syringe 10a is substantially similar in structure and in function to the second syringe 10b. Therefore, this description will primarily reference and describe the first syringe channel 120a and the first syringe 10a, the description of which is equally applicable to the second syringe channel 120b and the second syringe 10b therein.
[0050] The syringe first syringe 10a includes a barrel 12 defining a cavity 14 within which a therapeutic fluid (e.g., Propofol or other fluid therapeutic) is contained. The first syringe 10a includes a nozzle 16 in fluid communication with the cavity 14 on one end of the barrel 12. The nozzle 16 is couplable to a flexible intravenous line (e.g., coupled to the patient 90). The first syringe 10a further includes a flange 18 on an opposite end of the barrel 12. The first syringe 10a further includes a plunger 20 extending into the cavity 14 of the barrel 12. The plunger 20 includes a seal 22 on one end that is movable within the cavity 14. The cavity 14 of the barrel 12 and the seal 22 of the plunger 20 together define a volume of the first syringe 10a and the fluid therein (e.g., an active volume extending from the seal 22 to the nozzle 16 within which a fluid is disposed).
[0051] The first syringe 10a shown is a 30 cc syringe having a length of 118.36mm, an outer diameter of 25.27mm, and an inner diameter of 22.63mm. However, the first syringe channel 120a can accommodate a wide variety of syringe lengths and diameters not shown explicitly herein.
[0052] The first syringe channel 120a is configured to house, retain, and engage with the first syringe 10a therein. The first syringe channel 120a is defined by a syringe retainer surface 122 on the back side 106 of the housing 102. The syringe retainer surface 122 is curved to match the shape of the first syringe 10a (e.g., a semi-circular shape matching the circular cross-sectional shape of the barrel 12 of the first syringe 10a). The first syringe channel 120a extends along a first longitudinal axis 124 from the first side 108 of the housing 102 toward the second side 110 of the housing 102.
[0053] A syringe retention tab 126 extends from a portion of the back side 106 of the housing 102 adjacent to the first syringe channel 120a. The syringe retention tab 126 includes a spring- loaded shaft 128 and a curved arm 130 extending from the spring-loaded shaft 128. The curved arm 130 is configured to abut the barrel 12 of the first syringe 10a within the first syringe channel 120a. The spring-loaded shaft 128 is configured to pull the curved arm 130 inwardly (e.g., towards the barrel 12 of the first syringe 10a) to facilitate retention of the first syringe 10a in the first syringe channel 120a. The curved arm 130 may be rotatable relative to the spring-loaded shaft 128 to facilitate removal and replacement of the syringe in the first syringe channel 120a.
[0054] Furthermore, the syringe retention tab 126 functions as a size gauge for the first syringe 10a. For example, the spring-loaded shaft 128 includes a potentiometer (or similar measurement sensor) configured to measure the outward extension of the curved arm 130 relative to the first syringe channel 120a. Thus, the syringe retention tab 126 can measure an outer diameter of the barrel 12 of the first syringe 10a.
[0055] Aflange retainer 132 is positioned adjacent to the first syringe channel 120a. For example, the flange retainer 132 is positioned adjacent to the second side 110 of the housing 102, which includes the end of the first syringe 10a including the flange 18 and the plunger 20. Thus, the flange retainer 132 is opposite from the first side 108 of the housing 102, which is adjacent to the nozzle 16 end of the first syringe 10a.
[0056] As best shown in FIG. 4 or the cross-sectional view of FIG. 10, the flange retainer 132 is circumferential opening (e.g., semi-circular shaped) defined in part by the syringe retainer surface 122. For example, the flange retainer 132 an opening extending radially into the syringe retainersurface 122. Thus, when the first syringe 10a is inserted into the first syringe channel 120a, the flange 18 is seated within the flange retainer 132. Thus, the flange retainer 132 mechanically retains the barrel 12 of the first syringe 10a within the first syringe channel 120a. In some implementations, the flange retainer may be a separate structure at least partially coupled to the syringe retainer surface.
[0057] As shown in FIGS. 2 or 4, the device 100 further includes a plunger retainer 134. The plunger retainer 134 disposed on the second side 110 of the housing 102 adjacent to the first syringe channel 120a. Specifically, the plunger retainer 134 is defined by a moveable portion 136 of the housing 102 on the second side 110 of the housing 102. The moveable portion 136 is axially aligned with the first syringe channel 120a and the first syringe 10a therein. The moveable portion 136 is moveable between the closed configuration wherein the moveable portion 136 is aligned with the second side 110 of the housing 102 (as shown) and an open configuration wherein the moveable portion 136 is extended out and spaced apart from the second side 110 of the housing 102.
[0058] The plunger retainer 134 is a circumferential opening (e.g., semi-circular shaped) defined by the moveable portion 136. The plunger retainer 134 is configured to retain the plunger 20 of the first syringe 10a (e.g., a plunger flange thereof). Thus, when the first syringe 10a is inserted into the first syringe channel 120a, a portion of the plunger 20 is seated within the plunger retainer 134. Thus, the flange retainer 132 mechanically retains the plunger 20 of the first syringe 10a relative to the moveable portion 136 of the housing 102.
[0059] The first syringe 10a is moveable between a closed configuration wherein the seal 22 is adjacent to the nozzle 16 (as shown) and an open configuration wherein the plunger 20 and the seal 22 are extended axially away from the nozzle 16 of the first syringe 10a. The open configuration of the moveable portion 136 and the first syringe 10a correspond to a maximum volume configuration of the first syringe 10a. The close configuration of the moveable portion 136 and the first syringe 10a correspond to a minimal volume configuration of the first syringe 10a. The seal 22 (and thus the volume of the first syringe 10a) is moveable to any position between the open and closed configurations.
[0060] As best shown in FIG. 9, the device 100 further includes a linear actuator 140 disposed within a portion of the housing 102 (e.g., an inner cavity defined by the housing 102). The linear actuator 140 is coupled to the housing 102 adjacent to the first syringe channel 120a (e.g., inwardlyfrom the syringe retainer surface 122). The linear actuator 140 is generally coupled to a power source and the controller 200, as further described herein.
[0061] The linear actuator 140 includes a stationary member 142 and a moveable rod 144. The stationary member 142 extends along a portion of the device 100 adjacent to the first syringe channel 120a and the syringe retainer surface 122. A portion of the linear actuator 140 and / or the stationary member 142 is coupled to the syringe retainer structure or a portion adjacent to the first syringe channel 120a. Thus, the linear actuator 140 and its stationary member 142 are mechanically coupled (e.g., stationary) relative to the first syringe channel 120a.
[0062] The moveable rod 144 is disposed within a channel defined by the stationary member 142. The moveable rod 144 is controllably extendable out of the channel of the stationary member 142 (e.g., in a direction parallel to the longitudinal direction of the first syringe channel 120a). A free end of the moveable rod 144 is coupled to the moveable portion 136 of the device 100. Thus, when the moveable rod 144 is extended relative to the stationary member 142, the moveable portion 136 is extended outwardly from the second side 110 of the housing 102. Furthermore, when the moveable rod 144 is extended relative to the stationary member 142, the plunger 20 is extended relative to the barrel 12 of the first syringe 10a (e.g., increasing the volume of the first syringe 10a). Correspondingly, when the moveable rod 144 is retracted inwardly, the moveable portion 136 is moved towards the first syringe channel 120a, and the plunger 20 is moved towards the nozzle 16 (e.g., decreasing the volume of the first syringe 10a).
[0063] As shown in FIG. 9, two guide rods 146a, 146b are disposed on either side of the stationary member 142 adjacent to the first syringe channel 120a. The guide rods 146a, 146b are coupled to either the moveable portion 136 or an internal structure adjacent to the first syringe channel 120a. The guide rods 146a, 146b extend within corresponding guide channels. Linear slide bearings 148a, 148b are positioned around the guide rods 146a, 146b to facilitate their longitudinal movement. The guide rods 146a, 146b are configured to maintain alignment between the moveable portion 136 and the remainder of the device (e.g., the first syringe channel 120a), which ensures proper alignment of the plunger 20 with the barrel 12 of the first syringe 10a.
[0064] The linear actuator 140 is configured to move the moveable portion 136 relative to the first syringe channel 120a, which moves the plunger 20 relative to the barrel 12 of the first syringe 10a. In other words, the linear actuator 140 initiates and controls movement of the moveable portion 136 and the first syringe 10a between the open and closed configurations and any positionin between. The linear actuator 140 is controllable such that the speed of the linear actuator 140 - and the corresponding speed of the plunger 20 - may be monitored and adjusted when needed.
[0065] A control knob 150 is disposed on the second side 110 of the housing 102. The control knob 150 is operatively coupled to the control knob 150 (e.g., mechanically or electrically coupled). For example, the control knob 150 may be in communication with controller 200 that is in further communication with the linear actuator 140, as elsewhere described herein. The control knob 150 is rotatable in one or two directions (e.g., clockwise and counter-clockwise) to increase and / or decrease the speed of the linear actuator 140. The control knob 150 further includes a ridged outer surface 152 to facilitate a user’s grip and use of the control knob 150 (e.g., a user wearing a glove). The control knob 150 may also be moveable axially inward toward the housing 102. For example, the control knob 150 may include a button press feature such that the control knob 150 is “clickable” (e.g., to make a selection or otherwise interact with the device 100).
[0066] The housing 102 defines one or more ports configured to couple to a sensor or device. For example, the device 100 includes one or more sensors coupled to the device 100 via a port on the housing 102. For example, as shown in FIG. 7, the housing 102 includes a first port 154, a second port 156, and a third port 158. As shown, the first port 154 is a USB-C connector, the second port 156 is a 9-pin connector (e.g., D9 connector), and the third port 158 is a rectangular 10-pin connector. However, in other implementations, the device may include a variety of connector types (e.g., USB-C, USB-A, Micro-USB, Mini-USB, HDMI, DisplayPort, Ethernet port, 3.5mm Audio Jack, any other common data and / or power connection). Although three ports are shown, the device may include a different number of ports (e.g., 1, 2, 4, 5, or more ports). In other implementations, a sensor or device may couple to and communicate with the device in a wireless manner. Although not explicitly shown in FIGS. 1-10, the device 100b of FIG. 12 includes three cables connected to the corresponding three ports, as one exemplary implementation. The cables coupled to the ports may extend to a power source, an external device, or directly to the patient.
[0067] The device 100 includes at least one sensor coupled to the one or more ports (e.g., the first port 154). The at least one sensor of the present disclosure is generally configured to receive and / or sense information about the patient 90. For example, the at least one sensor may be coupled to the patient 90 to receive one or more patient data values. The at least one sensor then communicates patient data to the controller 200 of the device 100 via the one or more ports.
[0068] In some implementations, the at least one sensor is a pulse oximetry device configured to measure at least a blood oxygen saturation level of the patient. In some implementations, the at least one sensor is a respiration monitor configured to measure at least a rate of respiration of the patient. In some implementations, the at least one sensor is a heart rate monitor configured to measure at least the patient’s heart rate. In some implementations, the at least one sensor is an electrocardiogram (ECG) configured to measure at least the electrical activity of the patient’s heart. In some implementations, the at least one sensor is a blood pressure sensor configured to measure at least a patient’s blood pressure. Other similar patient monitoring sensors are contemplated by this disclosure.
[0069] The device 100 further includes a controller 200, as shown in FIG. 11. Although the system diagram of FIG. 11 shows the controller 200 as external to the device 100, the controller 200 is integrated into the device 100 (e.g., one or more printed circuit boards disposed within the housing 102). In other implementations, a portion of the controller may be remote from the housing of the device.
[0070] The controller 200 is in electrical communication with each of the screen 112, the linear actuator 140, and the at least one sensor via the ports (e.g., the first port 154). The controller 200 includes a processor 202 and a memory 204. The memory 204 includes instructions stored thereon that, when executed by the processor 202, initiate one or more actions of the device 100. For example, a processing circuit of the controller 200 may include the processor 202 and the memory 204 and one or more modules thereof.
[0071] The controller 200 is configured to continuously display patient data from the at least one sensor on the screen 112. As one example, the device 100b in FIG. 12 includes an ECG graph, among other patient information displays. The patient monitoring data is delivered from the at least one sensor to the controller 200. Once received, the processor 202 may interpret the patient monitoring data (e.g., perform a data correction based on individualized patient information or perform a check for errors or key indicators). The processor 202 may issue an alert if one of the patient data values exceeds a predetermined value or range or values. The processor 202 then continuously updates the display of the patient monitoring data on the screen 112.
[0072] The controller 200 is configured to initiate the flow of fluid from the first syringe 10a (e.g., to a patient via flexible tubing coupled to the nozzle 16 of the first syringe 10a). The fluid in the syringe may be a therapeutic fluid configured to sedate the patient 90 via an intravenousconnection. Therefore, the device 100 provides precise control and monitoring of the flow rate of fluid leaving the first syringe 10a. The controller 200 is in communication with the linear actuator 140 to initiate and maintain movement of the moveable portion 136 (and plunger 20). For example, the processor 202 may initiate and maintain a predetermined speed of the linear actuator 140 based on a desired or calculated flow rate. Such a flow rate may be selected via a user interface on the screen 112 and / or the control knob 150. The controller 200 may further initiate flow of fluid from the second syringe 10b in the second syringe channel 120b based on initiation of a second linear actuator (e.g., based on an empty or error signal from the first syringe channel 120a).
[0073] The controller 200 is further configured display a flow rate of the therapeutic fluid expelled from the first syringe 10a on the screen 112 (e.g., as shown in FIG. 12). For example, the controller 200 is in communication with the linear actuator 140 and the potentiometer (or other sensor) thereof to monitor displacement and / or speed data from the linear actuator 140. The controller 200 is further in communication with the syringe retention tab 126 and a potentiometer (or other sensor) to receive size data about the first syringe 10a (e.g., the diameter of the barrel 12, which may inform the volume of the nozzle 16).
[0074] A module of the controller 200 is configured to calculate the flow rate of fluid leaving the nozzle 16 of the first syringe 10a. The calculated flow rate is based on one or more of the size of the first syringe 10a and the speed of the linear actuator 140, which corresponds to the speed of the plunger 20. In some implementations, the memory 204 includes information about the first syringe 10a, including a standard set of geometries (e.g., inner diameters, lengths, volumes) for a given syringe. In some implementations, a syringe type is input into the device 100 (e.g., via the user interface on the screen 112) to inform the calculated flow rate. In some implementations, the device includes a scanning module (e.g., adjacent to the first syringe channel). The scanning module receives information about the syringe (e.g., size, type, and / or composition of the fluid therein). The scanning module may include a barcode reader, NFC tag reader, RFID reader, or any similar device configured to retrieve and communicate data about the syringe to the controller.
[0075] A module of the controller 200 is configured to adjust the flow rate of fluid expelled from the first syringe 10a. The control knob 150 is in communication with the controller 200 and may be rotated to adjust the speed of the linear actuator 140, which adjusts the flow rate of fluid expelled from the first syringe 10a. In some implementations, the controller 200 receives a signal from the control knob 150 and initiates a corresponding change in the speed of the linear actuator140. In other implementations, the processor 202 may verify the desired flow rate (e.g., based on patient data) and issue an alert if an error is detected.
[0076] In some implementations, a flow rate sensor is coupled to a portion of the IV line coupled to the first syringe 10a. For example, a fluid flow rate sensor may monitor the volume of fluid flowing in the IV line. The flow rate sensor may be in communication with the controller 200, wherein the controller 200 can verify the expected flow rate, adjust if needed, and stop operation in case of an error.
[0077] In some implementations, a pressure sensor (not shown) is coupled to a portion of the syringe and / or the intravenous line coupled to the patient. The pressure sensor is configured to deliver pressure data to the controller, where the processor may issue an alert if pressure values exceed a threshold value (e.g., indicating an error in the placement of the intravenous line in the patient).
[0078] The controller 200 of the device 100 is in further communication with one or more external devices or systems. As shown in FIG. 11, the controller 200 is communication with an external system 210 and an external device 220 via a communications interface 206. The external device 220 may be a remote device (e.g., a tablet, computer, phone, or other device local to the non-operating room setting within which the device 100 is used). The external system 210 may be a plurality of remote devices and / or a network (e.g., a cloud-based network) retrievable from a plurality of remote devices.
[0079] The external system 210 and / or the external device 220 may retrieve information from the device 100 and / or the controller 200. For example, the external device 220 may display the same information as the screen 112 so that a user can monitor the patient 90 from a distance away from the patient 90. The external device 220 may include a user interface that can be changed by the user to view different patient monitoring data or information. In some implementations, the external device 220 may cause the processor to initiate an action on the device 100 (e.g., an emergency stop).
[0080] In other implementations, such as shown in the device 100b of FIG. 12, the arrangement of elements of the device may be slightly changed without affecting the primary functions of the device. For example, the device 100b includes the syringe retainer closer to a bottom side of the housing. Additionally, the linear actuator and the syringe retaining mechanism of the device 100b may be slightly different than that shown and described in the device 100. However, the operationof the device 100b is substantially similar to that elsewhere described. In other implementations, the linear actuators may be replaced with another fluid pump (e.g., a peristaltic pump) coupled to a bulk fluid source. Throughout this disclosure structural and operational features in one example may be modified, replaced, or incorporated into that of another example.Example Method of Use
[0081] In use, the device 100 is brought to a non-operating room setting (e.g., an outpatient settings). The device 100 may be provided in a system or kit having a plurality of sensors and wires. A user (e.g., an anesthesiologist or other healthcare professional) places the device 100 adjacent to the patient 90 (e.g., on a table nearby or an IV pole via the mounting arm 114).
[0082] A user connects one or more patient sensors between the patient 90 and the device 100. A user may also connect the device or the sensors to a power source. The patient monitoring data is delivered from the one or more sensors to the controller 200. The controller 200 (e.g., the processor 202 thereof) updates the screen 112 to display patient monitoring data (e.g., blood pressure, ECG, oxygen saturation, etc.). The user verifies that all data sources from the sensors are properly displaying on the screen 112.
[0083] The device 100 is initialized with any relevant patient data or information about the procedure. For example, a desired flow rate of the therapeutic may be input into the device 100 (e.g., via the UI of the screen 112). The moveable portion 136 is moved to the open position, either manually or via initiation of the linear actuator 140 via the controller 200.
[0084] A syringe (e.g., the first syringe 10a) containing a desired therapeutic is inserted into the first syringe channel 120a of the device 100 in the open (or full-volume) configuration. The flange 18 of the first syringe 10a is disposed within the flange retainer 132. The plunger 20 of the first syringe 10a is disposed within the plunger retainer 134. An intravenous line (or other IV connection) is coupled to the patient 90. The IV line is then coupled to the nozzle 16 of the first syringe 10a.
[0085] Once all the relevant safety checks and standard procedures are performed by the healthcare professional(s), the device 100 can begin administering the therapeutic. The processor 202 initiates the linear actuator 140 to move at a predetermined speed, which moves the moveable portion 136 towards the housing 102. Thus, the volume of the first syringe 10a decreases at a controlled rate to deliver the therapeutic fluid along the IV line to the patient.
[0086] The processor 202 calculates the flow rate of fluid being delivered to the patient 90 and displays the flow rate on the screen 112 alongside the patient monitoring data. A user may interact with the device (e.g., the UI of the screen 112) to alter the information and / or arrangement of information displayed on the screen 112.
[0087] A user may adjust the flow rate of fluid expelled from the first syringe 10a by turning the control knob 150. The control knob 150 is operatively coupled to the linear actuator 140 (e.g., via the controller) so that input at the control knob 150 is output as a speed change of the linear actuator 140.
[0088] The device 100 may further communicate with an external system 210 or an external device 220. The external system 210 or the external device 220 may display the same patient information and / or fluid flow rate as the screen 112.Controller Architecture
[0089] In one configuration, the circuits of the controller 200 are in the form of machine or computer-readable media that is executable by a processor, such as processor 202. As described herein, the machine-readable media facilitates performance of certain operations to enable reception and transmission of data. For example, the machine-readable media may provide an instruction (e.g., command, etc.) to acquire data. In this regard, the machine-readable media may include programmable logic that defines the frequency of acquisition of the data (or, transmission of the data). The computer readable media may include code written in any programming language. The computer readable program code may be executed on one processor, multiple co located processors, multiple remote processors, or any combination of local and remote processors. Remote processors may be connected to each other through any type of network (e.g., CAN bus, etc.).
[0090] In another configuration, the circuits of the controller 200 are implemented as hardware units, such as electronic control units. As such, the circuits of the controller 200 may be implemented as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc. In some implementations, the circuits of the controller 200 may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, microcontrollers, etc.), telecommunication circuits, hybrid circuits, and any other type of “circuit.” In this regard, the circuits of the controller 200 may include any type of component foraccomplishing or facilitating achievement of the operations described herein. For example, a circuit as described herein may include one or more transistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors, multiplexers, registers, capacitors, inductors, diodes, wiring, and so on). The circuits of the controller 200 may also include programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. The circuits of the controller 200 may include one or more memory devices (e.g., memory 204) for storing instructions that are executable by the processor(s) of the circuits of the controller 200. The one or more memory devices and processor(s) may have the same definition as provided below with respect to the memory device 204 and processor 202. In some hardware unit configurations, the circuits of the controller 200 may be geographically dispersed throughout separate locations. Alternatively and as shown, the circuits of the controller 200 may be implemented in or within a single unit / housing, which is shown as the controller 200.
[0091] In the example shown, the controller 200 includes the processor 202 and the memory device 204. The processor 202 may be structured or configured to execute or implement the instructions, commands, and / or control processes described herein with respect to the circuits of the controller 200. The depicted configuration represents the circuits of the controller 200 as machine or computer-readable media. However, as mentioned above, this illustration is not meant to be limiting as the present disclosure contemplates other implementations where the circuits of the controller 200, or at least one circuit of the circuits of the controller 200, is configured as a hardware unit. All such combinations and variations are intended to fall within the scope of the present disclosure.
[0092] The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the implementations disclosed herein (e.g., the processor 202) may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration. In some implementations, the one or more processors may be shared by multiple circuits (e.g., the circuits of the controller 200 may comprise or otherwise share the same processor which, in some example implementations, may execute instructions stored, or otherwise accessed, via different areas of memory). Alternatively or additionally, the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors. In other example implementations, two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution. All such variations are intended to fall within the scope of the present disclosure.
[0093] The memory device 204 (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and / or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory device 204 may be communicably connected to the processor 202 to provide computer code or instructions to the processor 202 for executing at least some of the processes described herein. Moreover, the memory device 204 may be or include tangible, non-transient volatile memory or non-volatile memory. Accordingly, the memory device 204 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein.
[0094] While various circuits with particular functionality are shown in FIG. 11, it should be understood that the controller 200 may include any number of circuits for completing the functions described herein. For example, the activities and functionalities of the circuits of the controller 200 may be combined in multiple circuits or as a single circuit. Additional circuits with additional functionality may also be included. Further, the controller 200 may further control other activity beyond the scope of the present disclosure. In some implementations, the circuits described herein may include one or more processing circuits comprising one or more memory devices coupled to one or more processors, the one or more memory devices configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to perform the operations performed herein and described with reference to circuits.
[0095] As mentioned above and in one configuration, the “circuits” may be implemented in machine-readable medium for execution by various types of processors, such as the processor 202 of FIG. 11. An identified circuit of executable code may, for instance, comprise one or morephysical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified circuit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the circuit and achieve the stated purpose for the circuit. Indeed, a circuit of computer readable program code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within circuits, and may be implemented in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
[0096] While the term “processor” is briefly defined above, the term “processor” and “processing circuit” are meant to be broadly interpreted. In this regard and as mentioned above, the “processor” may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory. The one or more processors may take the form of a single core processor, multi -core processor (e.g., a dual core processor, triple core processor, quad core processor, etc.), microprocessor, etc. In some implementations, the one or more processors may be external to the apparatus, for example the one or more processors may be a remote processor (e.g., a cloud based processor). Alternatively or additionally, the one or more processors may be internal and / or local to the apparatus. In this regard, a given circuit or components thereof may be disposed locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud based server). To that end, a “circuit” as described herein may include components that are distributed across one or more locations.
[0097] Implementations within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form ofmachine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.Conclusion
[0098] For purposes of this description, certain advantages and novel features of the aspects and configurations of this disclosure are described herein. The described methods, systems, and apparatus should not be construed as limiting in any way. Instead, the present disclosure is directed toward all novel and nonobvious features and aspects of the various disclosed aspects, alone and in various combinations and sub-combinations with one another. The disclosed methods, systems, and apparatus are not limited to any specific aspect, feature, or combination thereof, nor do the disclosed methods, systems, and apparatus require that any one or more specific advantages be present or problems be solved.
[0099] Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.
[0100] Features disclosed in this specification (including any accompanying claims, abstract, and drawings), and / or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive. The claimed features extend to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract, and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed.
[0101] As used in the specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. Ranges may beexpressed herein as from “about” one particular value, and / or to “about” another particular value. When such a range is expressed, another aspect includes from the one particular value and / or to the other particular value. Similarly, when values are expressed as approximations, by use of the antecedent “about”, it will be understood that the particular value forms another aspect. It will be further understood that the endpoints of each of the ranges are significant both in relation to the other endpoint, and independently of the other endpoint. The terms “about” and “approximately” are defined as being “close to” as understood by one of ordinary skill in the art.
[0102] The terms “coupled”, “connected”, and the like as used herein mean the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members or the two members and any additional intermediate members being integrally formed as a single unitary body with one another or with the two members or the two members and any additional intermediate members being attached to one another. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.
[0103] Certain terminology is used in the following description for convenience only and is not limiting. The words “right”, “left”, “lower”, and “upper” designate direction in the drawings to which reference is made. The words “inner” and “outer” refer to directions toward and away from, respectively, the geometric center of the described feature or device. The words “distal” and “proximal” refer to directions taken in context of the item described and, with regard to the instruments herein described, are typically based on the perspective of the practitioner using such instrument, with “proximal” indicating a position closer to the practitioner and “distal” indicating a position further from the practitioner. The terminology includes the above-listed words, derivatives thereof, and words of similar import.
[0104] Throughout the description and claims of this specification, the word “comprise” and variations of the word, such as “comprising” and “comprises”, means “including but not limited to”, and is not intended to exclude, for example, other additives, components, integers or steps. “Exemplary” means “an example of’ and is not intended to convey an indication of a preferred or ideal aspect. “Such as” is not used in a restrictive sense, but for explanatory purposes.
[0105] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description but is not intended to be exhaustive or limited to the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present disclosure.
Claims
What is claimed is:
1. A portable anesthesia monitoring device comprising: a housing defining a front side and a back side; a screen on the front side of the housing configured to display information; a first syringe channel defined on the back side of the housing, the first syringe channel configured to retain a first syringe therein; a flange retainer coupled to and extending at least partially into the first syringe channel, the flange retainer configured to limit motion of a flange of the first syringe relative to the first syringe channel; a plunger retainer on a first side of the housing adjacent to the first syringe channel, the plunger retainer being moveable relative to the flange retainer and configured to engage a plunger of the first syringe; a linear actuator coupled between the flange retainer and the plunger retainer and configured to move the plunger retainer relative to the flange retainer, wherein movement of the plunger retainer is configured to move the plunger of the first syringe to change an internal volume of the first syringe; at least one sensor coupled to the housing via at least one port defined therein, the at least one sensor configured to communicate patient data to the device; and a controller in electrical communication with each of the screen, the linear actuator, and the at least one sensor, the controller configured to (i) continuously display patient data from the at least one sensor on the screen and (ii) initiate movement of the plunger retainer to expel a fluid from the first syringe at a controlled flow rate.
2. The portable anesthesia monitoring device of claim 1, further comprising a control knob extending from a portion of the housing, the control knob operatively connected to the linear actuator, wherein the controller is configured to receive an input from the control knob and adjust a speed of the linear actuator to adjust the flow rate of the fluid expelled from the first syringe.
3. The portable anesthesia monitoring device of any of claims 1-2, wherein the screen is further configured to display the flow rate of the fluid expelled from the first syringe based on a speed of the linear actuator.
4. The portable anesthesia monitoring device of any of claims 1-3, further comprising a syringe retention tab extending from a portion of the first syringe channel and configured to abut an outer diameter of the first syringe, wherein the syringe retention tab comprises a potentiometer to facilitate measurement of the outer diameter of the first syringe, wherein the controller is configured to receive the measured outer diameter of the first syringe from the syringe retention tab and calculate the flow rate of the fluid expelled from the first syringe based on the measured outer diameter and a speed of the linear actuator.
5. The portable anesthesia monitoring device of any of claims 1-4, further comprising: a second syringe channel defined on the back side of the housing adjacent to the first syringe channel, wherein the second syringe channel is configured to retain a second syringe therein; a second flange retainer coupled to and extending at least partially into the second syringe channel, the second flange retainer configured to limit motion of a flange of the second syringe relative to the second syringe channel; a second plunger retainer on a first side of the housing adjacent to the second syringe channel, the second plunger retainer being moveable relative to the second flange retainer and configured to engage a plunger of the second syringe; a second linear actuator coupled between the second flange retainer and the second plunger retainer and configured to move the second plunger retainer relative to the second flange retainer, wherein movement of the second plunger retainer moves the plunger of the second syringe to change an internal volume of the second syringe and expel a fluid from the second syringe at a controlled flow rate.
6. The portable anesthesia monitoring device of any of claims 1-5, wherein the fluid is a therapeutic fluid configured to sedate a patient via an intravenous connection.
7. The portable anesthesia monitoring device of any of claims 1-6, further comprising a mounting device extending from a portion of a housing to removably couple the device to a rigid object.
8. The portable anesthesia monitoring device of any of claims 1-7, wherein the at least one sensor comprises a pulse oximetry sensor, a heart rate sensor, a blood pressure sensor, or a respiration sensor, and wherein more than one patient data set is delivered to and displayed on the screen in real time.
9. The portable anesthesia monitoring device of any of claims 1-8, wherein the controller is in communication with a remote device, the controller configured to communicate patient data from the at least one sensor and flow rate information related to the first syringe to the remote device for display thereon.
10. The portable anesthesia monitoring device of any of claims 1-9, further comprising a pressure sensor configured to be in fluid communication with the first syringe, wherein the controller receives pressure data from the pressure sensor and initiates an alert if a pressure measurement exceeds a threshold value.
11. A portable anesthesia monitoring device comprising: a syringe retainer having a linear actuator coupled to a first portion and a second portion of the syringe retainer, wherein the syringe retainer is configured to retain a first syringe having a first therapeutic fluid therein, wherein movement of the first portion relative to the second portion is configured to expel the first therapeutic fluid from the first syringe; a control knob extending from a portion of the device, the control knob being operatively connected to the linear actuator, wherein movement of the control knob in a first direction adjusts a speed of the linear actuator which is configured to adjust a flow rate of the first therapeutic fluid expelled from the first syringe; at least one patient sensor coupled to and extending from at least one port of the device; a screen configured to display at least (i) patient monitoring data from the at least one patient sensor, and (ii) the flow rate of the first therapeutic fluid expelled from the first syringe based on movement information from the linear actuator; and a controller in electrical communication with the linear actuator, the control knob, the at least one patient sensor, and the screen, wherein the controller is configured to facilitate the display of patient monitoring data and flow rate information on the screen.
12. The portable anesthesia monitoring device of claim 11, wherein the controller comprises a processor and a memory storing instructions thereon that, when executed by the processor, cause the processor to receive and interpret patient monitoring data from the at least one patient sensor and continuously update a display of patient monitoring data on the screen.
13. The portable anesthesia monitoring device of any of claims 11-12, wherein the controller comprises a processor and a memory storing instructions thereon that, when executed by the processor, cause the processor to calculate the flow rate of the first therapeutic fluid expelled from the first syringe based on displacement data from the linear actuator of the syringe retainer.
14. The portable anesthesia monitoring device of any of claims 11-13, further comprising a syringe size gauge coupled to a portion of the syringe retainer and configured to measure a diameter of the first syringe therein, wherein the processor receives a measured diameter of the first syringe from the syringe size gauge and updates the calculated flow rate of the first therapeutic fluid based in part on the measured diameter of the first syringe.
15. The portable anesthesia monitoring device of any of claims 11-14, further comprising a scanning module adjacent to the syringe retainer, the scanning module configure to retrieve information from a first syringe deposited into the syringe retainer, wherein the information received by the scanning module comprises a size of the first syringe or a composition of the first therapeutic fluid therein.
16. The portable anesthesia monitoring device of any of claims 11-15, wherein the memory comprises a library of therapeutic compositions and syringe sizes that inform the flow rate information displayed on the screen.
17. The portable anesthesia monitoring device of any of claims 11-16, wherein the first therapeutic fluid is an intravenous anesthetic.
18. The portable anesthesia monitoring device of any of claims 11-17, wherein the at least one patient sensor comprises a pulse oximetry sensor, a heart rate sensor, a blood pressure sensor, or a respiration sensor, and wherein more than one set of patient monitoring data is delivered to and displayed on the screen in real time.
19. The portable anesthesia monitoring device of any of claims 11-18, wherein the controller is in communication with a remote device, the controller configured to communicate patient monitoring data from the at least one sensor and flow rate information related to the first syringe to the remote device for display thereon.
20. The portable anesthesia monitoring device of any of claims 11-19, wherein the screen is a touch screen defining a user interface, wherein the user interface includes one or more controls configured to change the patient monitoring data displayed on the screen.
Citation Information
Patent Citations
CO2 monitored drug infusion system
US20030106553A1
Patient-controlled analgesia with patient monitoring system and method
US20050177096A1
Multi-pump closed-loop management system
WO2024039748A1