US 8,302,602 B2Grant
Breathing assistance system with multiple pressure sensors
Issue Date:2012-11-06
•26 Claims
•14 Drawing Sheets
Abstract
A method for managing pressure in a breathing assistance system configured to provide breathing assistance to a patient via a patient connection system is provided. The method may include receiving one or more first pressure sensor signals from a first pressure sensor, and analyzing the one or more first pressure sensor signals. Based at least on the analysis of the one or more first pressure sensor signals, either the first pressure sensor or the second pressure sensor may be selected for use in controlling the breathing assistance provided to the patient, and the breathing assistance provided to the patient may be controlled based at least on signals from the selected pressure sensor.
Metadata
Assignee
- Nellcor Puritan Bennett LLC
Inventors
- Claude Andrieux
- Cedric Jourdain
Application Information
Application Number:US 12/241,243
Filing Date:2008-09-30
Priority Date:2008-09-30
Art Unit:3771
Classifications
IPC:
A61M11/00
Patent Drawings (14 sheets)
Description
Technical Field
[0001] The present disclosure is related to breathing assistance systems, and more particularly to a breathing assistance system with multiple pressure sensors.
Background
[0002] Breathing assistance systems are used to provide various types of breathing assistance to patients. For example, a ventilator provides mechanical ventilation to a patient by delivering pressurized gas (e.g., air and/or supplemental oxygen) to the patient through a breathing circuit connected to the patient by a connection device, e.g., an endotracheal tube or a nose or face mask. A ventilator may provide ventilation according to any of a variety of well-known ventilation modes, e.g., assist/control (A/C) ventilation, volume controlled ventilation, pressure controlled ventilation, and synchronous intermittent mandatory ventilation (SIMV) ventilation. Each of such modes may provide or allow for one or more types of breaths, including mandatory breaths, assisted breaths, and/or spontaneous breaths.
[0003] Another example breathing assistance system is a continuous positive airway pressure (CPAP) system. CPAP therapy has become a common prescription for individuals suffering from sleep apnea and/or other breathing ailments. Such therapy may involve placement of a nose or face mask on the subject during sleeping, while positive pressure air is continuously delivered from a CPAP box to the patient through a breathing circuit connected to the patient by a connection device, e.g., a nose or face mask. In this manner, positive pressure air may be delivered to the patient's upper airway in order to prevent the upper airway tissues from collapsing during sleep, thus reducing the occurrence and/or severity of sleep apnea.
Summary
[0004] According to one embodiment of the present disclosure, a method for managing pressure in a breathing assistance system configured to provide breathing assistance to a patient via a patient connection system is provided. The method may include receiving one or more first pressure sensor signals from a first pressure sensor, and analyzing the one or more first pressure sensor signals. Based at least on the analysis of the one or more first pressure sensor signals, either the first pressure sensor or the second pressure sensor may be selected for use in controlling the breathing assistance provided to the patient, and the breathing assistance provided to the patient may be controlled based at least on signals from the selected pressure sensor.
[0005] According to another embodiment of the present disclosure, a breathing assistance system configured to provide breathing assistance to a patient via a patient connection system is provided. The breathing assistance system includes a first pressure sensor, a second pressure sensor, and a control system. The control system may be configured to receive first pressure sensor signals from the first pressure sensor and second pressure sensor signals from the second pressure sensor; analyze one or more first pressure sensor signals; based at least on the analysis of the one or more first pressure sensor signals, select either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient; and control the breathing assistance provided to the patient based at least on signals from the selected pressure sensor.
[0006] According to another embodiment of the present disclosure, a method is provided for managing pressure in a breathing assistance system including a gas delivery system for delivering gas toward a patient via a patient connection system between the gas delivery system and the patient. The method may include receiving first pressure sensor signals from a first pressure sensor configured to measure gas pressure at a first location relative to the patient connection system; receiving second pressure sensor signals from a second pressure sensor configured to measure gas pressure at a different, second location relative to the patient connection system; controlling the gas de system based on at least one of the first pressure sensor signals and the second pressure sensor signals; automatically detecting an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals; and in response to detecting the over-pressure condition in the patient connection system, automatically controlling the gas delivery system to reduce the pressure in the patient connection system.
[0007] According to another embodiment of the present disclosure, a breathing assistance system for providing breathing assistance to a patient is provided. The breathing assistance system may include a gas delivery system for delivering gas toward a patient via a patient connection system between the gas delivery system and the patient; a first pressure sensor configured to measure gas pressure at a first location relative to the patient connection system; a second pressure sensor configured to measure gas pressure at a different, second location relative to the patient connection system; and a control system. The control system may be configured to: receive first pressure sensor signals from the first pressure sensor; receive second pressure sensor signals from the second pressure sensor; control the gas delivery system based on at least one of the first pressure sensor signals and the second pressure sensor signals; automatically detect an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals; and in response to detecting the over-pressure condition in the patient connection system, automatically control the gas delivery system to reduce the pressure in the patient connection system.
Brief Description of the Drawings
[0008] Some embodiments of the disclosure may be understood by referring, in part, to the following description and the accompanying drawings, in which like reference numbers refer to the same or like parts and wherein:
[0009] FIG. 1 illustrates an example breathing assistance system for providing breathing assistance to a patient, according to one embodiment of the disclosure;
[0010] FIG. 2 illustrates an example ventilation system including an over-pressure security system, exhalation valve detection system, proximal pressure detection system, and an O2 safety system, according to certain embodiments of the present disclosure;
[0011] FIG. 3 illustrates details of an example power system for a ventilation system, according to certain embodiments of the present disclosure;
[0012] FIGS. 4A and 4B illustrate example O2 safety systems for use with a ventilation system, according to certain embodiments of the present disclosure;
[0013] FIG. 5 illustrates a flow path diagram showing various components and gas flow paths in an example embodiment of a ventilation system, according to one embodiment of the present disclosure;
[0014] FIG. 6 illustrates an example arrangement of various components of an example ventilation system, according to one embodiment of the present disclosure;
[0015] FIG. 7 illustrates an example wireless notification system configured to communicate wireless notifications (e.g., alarms) from a ventilation system to one or more receiving devices, according to certain embodiments of the present disclosure;
[0016] FIG. 8 illustrates an example method of using multiple pressure sensors for managing control of a ventilation system, according to certain embodiments of the present disclosure;
[0017] FIG. 9 illustrates an example method for detecting and managing an over-pressure condition in a breathing assistance system, according to certain embodiments of the present disclosure;
[0018] FIG. 10 illustrates an example method for determining whether an exhalation valve is connected to a ventilation system, and controlling the ventilation system accordingly, according to certain embodiments of the present disclosure;
[0019] FIG. 11 illustrates an example method for managing a supplemental gas supply (e.g., supplemental oxygen supply) in a breathing assistance system, according to certain embodiments of the present disclosure;
[0020] FIG. 12 illustrates an example method for determining an overheat condition in a breathing assistance system and managing a supplemental gas flow (e.g., supplemental oxygen flow) using an O2 safety system as shown in FIG. 4A , according to certain embodiments of the present disclosure; and
[0021] FIGS. 13A and 13B illustrate example methods for determining an overheat condition in a breathing assistance system and managing a supplemental gas flow (e.g., supplemental oxygen flow) using an O2 safety system as shown in FIG. 4B , according to certain embodiments of the present disclosure.
Detailed Description
[0022] Selected embodiments of the disclosure may be understood by reference, in part, to FIGS. 1-13B , wherein like numbers refer to same and like parts.
[0023] FIG. 1 illustrates an example breathing assistance system 10 for providing breathing assistance to a patient, according to one embodiment of the disclosure. Breathing assistance system 10 may be generally configured to provide one or more types of ventilation to the patient. As used herein, “ventilation” means communicating gas to and/or from a patient 11 to provide any type of breathing assistance to the patient 11, including, e.g., mechanically ventilating the patient and/or treating an apnea or other breathing condition of the patient. “Ventilation” includes breathing assistance typically provided by a ventilator, as well as breathing assistance typically provided by CPAP device. Thus, as discussed below, breathing assistance system 10 may provide any or all of the following:
-
- [0024] Positive Pressure ventilation;
- [0025] Assist/Control, SIMV, and/or CPAP modes of ventilation;
- [0026] Breath types including Volume, Pressure Control, and Pressure Support;
- [0027] Other types or modes of ventilation and/or other breath types.
[0028] In example embodiments, breathing assistance system 10 may provide some or all of the following user-selectable ventilation modes:
-
- [0029] Assisted Controlled Volume (VOLUME A/C);
- [0030] Assisted Controlled Pressure (PRESSURE A/C);
- [0031] Synchronous Intermittent Mandatory Ventilation Volume (V SIMV);
- [0032] Synchronous Intermittent Mandatory Ventilation Pressure (P SIMV);
- [0033] Continuous Positive Airway Pressure (CPAP); and
- [0034] Pressure Support Ventilation (PSV).
[0035] Breathing assistance system 10 may be configured for use by both adult and pediatric patients 11. In addition, in certain embodiments, breathing assistance system 10 may be configured for use in institutional, home, and/or portable settings.
[0036] As shown in FIG. 1 , breathing assistance system 10 may include a ventilation system 12 and a connection system 14 for connecting ventilation system 12 to patient 11.
[0037] Ventilation system 12 may comprise any device, apparatus, or system for providing ventilation to a patient 11 via connection system 14. Connection system 14 may be generally configured to deliver gas from ventilation system 12 to patient 11 and/or to communicate exhaust gas away from patient 11. For example, connection system 14 may comprise any suitable type of breathing circuit 16 (e.g., a single-limb or dual-limb breathing circuit) and/or a patient connection apparatus 18. For instance, connection system 14 may include a 6-foot (single-limb or dual-limb) breathing circuit 16. In embodiments using a dual-limb breathing circuit 16, both limbs (the inspiratory limb and the expiratory limb) may be connected to ventilation system 12, as discussed below with reference to FIG. 2 .
[0038] A patient connection apparatus 18 may include any device or devices configured to connect breathing circuit 16 to one or more breathing passageways of patient 11. For example, patient connection apparatus 18 may include a patient connection tube directly connected to the patient's trachea, an artificial airway (e.g., an endotracheal tube or other device) inserted in the patient's trachea, and/or a mask, cushion or nasal pillows positioned over the patient's nose and/or mouth.
[0039] Ventilation system 12 may include a gas delivery system 20, a control system 22, sensors 24, user interfaces 26, a display system 28, and a wireless notification module 44.
[0040] Gas delivery system 20 may include any device or devices configured to generate, supply, and/or deliver gas (e.g., pressurized air) toward patient 11 via connection system 14. For example, gas delivery system 20 may comprise a device capable of generating pressurized air (e.g., a motorized turbine-based blower or piston-based device), a wall outlet through which pressurized air may be supplied (e.g., in a hospital or clinic), valves configured to control the supply of gas to the patient (e.g., a PSOL or other solenoid valve), one or more tanks of compressed gas, a compressor, or any other suitable source of pressurized or non-pressurized gas. In some embodiments, gas delivery system 20, in cooperation with other components of ventilation system 12 (e.g., an exhalation valve) may generate both positive and negative gas flows toward patient 11. For example, a positive gas flow may be generated as gas is delivered to patient 11 during inhalation, while a negative gas flow may be generated as exhaust gas is communicated from patient 11 during exhalation.
[0041] In some embodiments, gas delivery system 20 may be configured to deliver a gas mixture toward patient 11, e.g., a mixture of air and supplemental oxygen or other supplemental gas. Depending on the particular embodiment, the point of mixture for the multiple gasses may be upstream or downstream of gas delivery system 20. For example, a supplemental oxygen stream may be connected to mix with a primary air stream at a point upstream or downstream of gas delivery system 20.
[0042] As used herein, the term “gas” may refer to any one or more gases and/or vaporized substances suitable to be delivered to and/or from a patient via one or more breathing orifices (e.g., the nose and/or mouth), such as air; nitrogen, oxygen, any other component of air, CO2, vaporized water, vaporized medicines, and/or any combination of two or more of the above, for example.
[0043] As used herein, the term “patient” may refer to any person or animal that may receive breathing assistance from system 10, regardless of the medical status, official patient status, physical location, or any other characteristic of the person. Thus, for example, patients may include persons under official medical care (e.g., hospital patients), persons not under official medical care, persons receiving care at a medical care facility, persons receiving home care, etc.
[0044] Control system 22 may include any sub-systems for controlling any aspect of the operation of ventilation system 12, including, e.g., a power system 30, a gas delivery control system 31, an over-pressure security system 32, an exhalation valve detection system 34, a proximal pressure detection system 36, and an oxygen safety system 38.
[0045] Each sub-system 30, 31, 32, 34, 36, and 38 of control system 22, may include, or have access to, any suitable controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for performing any of the function associated with such systems. In particular, each system 30, 31, 32, 34, 36, and 38 may include or have access to any instructions (e.g., software, firmware, algorithms, or other logic or instructions) stored in any suitable tangible storage media and executable by a processor for performing any of the functions associated with that system.
[0046] Any one or more sensors 24 may be provided for sensing, detecting, and/or monitoring one or more parameters related to the ventilation of patient 11, e.g., parameters regarding the ventilation provided by ventilation system 12 and/or physiological parameters regarding patient 11. For example, sensors 24 may include one or more devices for measuring various parameters of gas flowing to or from patient 11 or ventilation system 12, e.g., the pressure, flow rate, flow volume, temperature, gas content, and/or humidity of such gas flow.
[0047] In certain embodiments, sensors 24 may include one or more pressure sensors and one or more flow sensors for measuring the pressure and flow, respectively, of gas through various components of system 10. Such pressure and flow sensors 24 may be located at any suitable location in system 10. For example, each sensor 24 may be integrated with or coupled to ventilation system 12, integrated with or coupled to connection system 14, coupled to patient 11, or otherwise associated with system 10.
[0048] In some embodiments (e.g., as shown in FIGS. 5 and 6 ), system 10 may include any or all of the following:
[0049] (a) a main pressure sensor for measuring the pressure of gas flow exiting ventilation system 12 or gas delivery system 20, or the pressure of gas flow entering connection system 14;
[0050] (b) a proximal pressure sensor for measuring pressure at or near the patient end of connection system 14, referred to as the “proximal pressure”;
[0051] (c) an exhalation valve pressure sensor for measuring pressure in a conduit used for controlling an exhalation valve of system 10;
[0052] (d) an inhalation flow sensor for measuring the flow rate of gas flowing toward patient 11 (e.g., via an inhalation limb of breathing circuit 16);
[0053] (e) an exhalation flow sensor for measuring the flow rate of gas exhaled by patient 11 (e.g., via an exhalation limb of breathing circuit 16); and/or
[0054] (f) any other pressure and/or flow sensors.
[0055] The main pressure sensor, proximal pressure sensor, and/or exhalation valve pressure sensor may be used to provide various functions of ventilation system 12. For example, as discussed below regarding FIG. 2 , signals from the main pressure sensor and the proximal pressure sensor may be used in a first technique for detecting and managing over-pressure of gas in connection system 14 (e.g., in breathing circuit 16). As another example, as discussed below regarding FIG. 2 , signals from the exhalation valve pressure sensor may be used in a second technique for detecting and managing over-pressure of gas in connection system 14 (e.g., in breathing circuit 16). As another example, as discussed below regarding FIG. 2 , signals from the exhalation valve pressure sensor may be used to detect whether an exhalation valve is present in the current configuration of system 10 (e.g., whether the currently connected breathing circuit 16 includes an exhalation valve). As yet another example, as discussed below regarding FIG. 2 , signals from the main pressure sensor and/or the proximal pressure sensor may be used to determine whether proximal pressure may be measured and used by ventilation system 12 (e.g., if a proximal pressure line is properly connected and the proximal pressure sensor is working properly).
[0056] User interfaces 26 may include any suitable device or devices allowing a user to interface with breathing assistance system 10, e.g., to control ventilation system 12, to navigate through various display screens, to make selections, and/or to set, modify, or otherwise control various parameters regarding system 10. For example, user interfaces 26 may allow a user to input desired performance parameters (e.g., pressure or flow rate) that may be communicated to control system 22 to control the operation of gas delivery system 20 and/or other components of system 10.
[0057] User interfaces 26 may include a graphic user interface (GUI) 40, one or more manual input devices 42 separate from the GUI, and/or any other input devices. In some embodiments, GUI 40 may include a touch screen configured to display various information and provide an interface for accepting input from user (e.g., to navigate through various screens, to make selections, to set or modify various parameters, to change or configure the display, etc.). In embodiments in which GUI 40 does not include a touch screen, manual input devices 42 may be used to make selections and navigate through various screens or menus displayed on GUI 40. Manual input devices 42 may include any physical buttons, knobs, dials, switches, levers, or any other devices that may be manipulated by a user.
[0058] Display system 28 may comprise a screen or any other device suitable for visually displaying medical data. For example, display system 28 may include a monitor, an LCD screen, LEDs, or any other visual device. In some embodiments, display system 28 and user interfaces 26 may be at least partially integrated, e.g., where ventilation system 12 includes a touch screen or other GUI 40.
[0059] Power system 30 may include or facilitate the connection of one or more sources of power for ventilation system 12, e.g., an external AC power source, an external DC power source, and/or one or more rechargeable batteries, for example. In embodiments including a battery 50, power system 30 may include a battery security system 52 for ensuring that only approved batteries may be used in ventilation system 12 and/or a battery age management system 70 for recording and displaying age data regarding a battery 50, e.g., the number of charge and discharge cycles the battery 50 has experienced. Battery security system 52 and battery age management system 70 are illustrated and discussed in greater detail below with reference to FIG. 3 .
[0060] Gas delivery control system 31 is generally operable to control the delivery of gas to and/or from patient 11 based on various input, e.g., input received from a user (e.g., via a touch screen and/or other user interfaces provided by ventilation system 12), data received from one or more sensors 24, and/or data received from other components of ventilation system 12 (e.g., power system 30, over-pressure security system 32, exhalation valve detection system 34, and proximal pressure detection system 36). As discussed below, in some embodiments, gas delivery control system 31 may control gas delivery to patient 11 based on input from one of two sensors 24: (a) a proximal pressure sensor generally configured to measure pressure in the breathing circuit 16 near patient 11, and (b) an outlet pressure sensor generally configured to measure pressure exiting ventilation system 12 and entering breathing circuit 16.
[0061] Over-pressure security system 32 is generally operable to detect and facilitate the management of over-pressure of gas in connection system 14 (e.g., in breathing circuit 16) based on pressure signals received from one or more pressure sensors 24.
[0062] Exhalation valve detection system 34 is generally operable to determine whether an exhalation valve is present in the current configuration of system 10 (e.g., whether the currently connected breathing circuit 16 includes an exhalation valve) based on pressure signals received from one or more pressure sensors 24.
[0063] Proximal pressure detection system 36 is generally operable to determine whether proximal pressure may be measured and used by ventilation system 12 (e.g., if a proximal pressure line is properly connected and the proximal pressure sensor is working properly) based on pressure signals received from one or more pressure sensors 24.
[0064] Over-pressure security system 32, exhalation valve detection system 34, and proximal pressure detection system 36, are discussed in greater detail below with reference to FIG. 2 .
[0065] Oxygen safety system 38 is generally operable to slow or stop the flow of a supplemental oxygen supply in particular circumstances, e.g., when gas delivery system 20 is not running and/or overheating. Oxygen safety system 38 is discussed in greater detail below with reference to FIGS. 4A and 4B .
[0066] Wireless notification module 44 is generally configured to communicate wireless notifications (e.g., alarms generated by control system 22) from ventilation system 12 to any suitable receiving device, e.g., a remote monitor or a mobile alarm unit carried by a user (e.g., a caretaker). In some embodiments, wireless notification module 44 may communicate to such receiving device(s) via one or more wireless repeaters, which may increase the physical range of wireless communications from ventilation system 12.
Sensor Systems
[0067] FIG. 2 illustrates an example ventilation system 12 including an over-pressure security system 32, exhalation valve detection system 34, proximal pressure detection system 36, and an O2 safety system 38, according to certain embodiments of the present disclosure. FIG. 2 illustrates systems 31, 32, 34, 36, and 38, various sensors 24 for providing input to systems 31, 32, 34, 36, and 38, and/or control system 22, and an example connection system 14 connected to ventilation system 12. The example connection system 14 includes a dual-limb breathing circuit 16 including an inspiratory limb 90, exhalation limb 92, exhalation valve 96, exhalation valve control line 98, and a proximal pressure line 100 running along a length of inspiratory limb 90 or exhalation limb 92.
[0068] Breathing assistance system 10 may include one or more pressure sensors 80 for providing input to systems 31, 32, 34, and 36. For example, system 10 may include any or all of the following pressure sensors:
[0069] (a) An outlet pressure sensor 80a located at or near a main gas outlet of ventilation system 12 (e.g., at or near an outlet of gas delivery system 20) to measure the pressure of gas flow exiting ventilation system 12 or gas delivery system 20, or the pressure of gas flow entering connection system 14. For example, outlet pressure sensor 80a may be located inside or just outside a housing or enclosure of ventilation system 12.
[0070] (b) A proximal pressure sensor 80b configured to measure pressure at or near the patient end of connection system 14 (indicated in FIG. 2 generally at 86), referred to as the “proximal pressure.” Proximal pressure sensor 80b may be located at any suitable location. For example, proximal pressure sensor 80b may be located in ventilation system 12 and connected to a proximal pressure line 100 (e.g., a tube or other conduit) that extends along a limb 90 or 92 of breathing circuit 16 and opens near the patient end 86 of connection system 14. Thus, proximal pressure sensor 80b may measure the gas pressure at the open end (i.e., the patient end) of proximal pressure line 100. As another example, proximal pressure sensor 80b may be located at or near the open, patient end of the proximal pressure line 100 and may be configured to communicate pressure measurement signals back to ventilation system 12 (e.g., via an embedded wire in connection system 14).
[0071] Typically, the pressure measured by proximal pressure sensor 80b is lower than the pressure measured by outlet pressure sensor 80a in positive flow situations (flow toward patient 11), and greater than the pressure measured by outlet pressure sensor 80a in negative flow situations (flow away patient 11). The difference between the measurements of sensors 80a and 80b is largely or completely due to pressure drop inherent in the breathing circuit 16. Proximal pressure sensor 80b typically provides a more accurate measure of the pressure experienced by the patient, referred to as the “patient pressure.”
[0072] (c) An exhalation valve pressure sensor 80c configured to measure pressure in a conduit used for controlling an exhalation valve of system 10. In some embodiments, breathing circuit 16 may include an exhalation valve 96 and an exhalation valve control line 98. Gas may be delivered from gas delivery system 20 through exhalation valve control line 98 to control exhalation valve 96. Measurements taken by exhalation valve pressure sensor 80c may be used (e.g., by control system 22) for controlling exhalation valve 96.
[0073] For example, in some embodiments, a pilot valve 102 (e.g., controlled by control system 22) may control the pressure in exhalation valve control line 98, thus controlling the operation of exhalation valve 96. Exhalation valve pressure sensor 80c may be configured to measure the pressure in exhalation valve control line 98 between the pilot valve 102 and exhalation valve 96, which measured pressure may then be used (e.g., by control system 22) for controlling the pilot valve 102 in order to control exhalation valve 96. Exhalation valve pressure sensor 80c may be located at any suitable location, e.g., within or attached to ventilation system 12 (e.g., near the pilot valve 102) or breathing circuit 16 (e.g., near exhalation valve 96).
[0074] Pilot valve 102 may comprise any type of valve operable to control gas flow through exhalation valve control line 98 in order to control exhalation valve 96. For example, pilot valve 102 may comprise a solenoid valve, a pneumatic valve, or a piezoelectric valve. In an example embodiment, pilot valve 102 is an electro valve and exhalation valve pressure sensor 80c is connected to a command port of the electro valve. In other embodiments, ventilation system 12 may not include a pilot valve.
[0075] In operation, any or all of main pressure sensor 80a, proximal pressure sensor 80b, and exhalation valve pressure sensor 80c may take and communicate pressure measurements for use by sub-systems 31, 32, 34, and/or 36 of control system 22. For example, pressure measurements taken by any or all of sensors 80a, 80b, and 80c may be communicated to control system 22 and used by the various sub-systems 31, 32, 34, and/or 36 for controlling various aspects of the operation of system 12, e.g., the delivery of gas by gas delivery system 20. Sensors 80a, 80b, and/or 80c may take and/or communicate pressure measurements according to any time schedule, e.g., periodically or substantially continuously, for example.
[0076] In addition to pressure sensors 80, breathing assistance system 10 may also include one or more flow sensors 82 for measuring gas flows and providing input to control system 22. For example, system 10 may include at least (a) an inhalation flow sensor 82a configured to measure the flow rate of gas flow delivered toward patient 11 via connection system 14, and (b) an exhalation flow sensor 82b configured to measure the flow rate of gas flow exhaled by or otherwise communicated away from patient 11 via connection system 14.
[0077] Like pressure sensors 80, each flow sensor 82 may be located at any suitable location. For example, inhalation flow sensor 82a may be located at or near a gas outlet of ventilation system 12 connected to inhalation limb 90 of breathing circuit 16, and exhalation flow sensor 82b may be located at or near a gas inlet of ventilation system 12 connected to exhalation limb 90 of breathing circuit 16.
[0078] It should be understood that ventilation system 12 includes various other components (e.g., a power system, user interfaces, a display, etc.) not shown in FIG. 2 for the sake of simplicity.
Gas Delivery Control System 31
[0079] As discussed above, gas delivery control system 31 may control the delivery of gas to and/or from patient 11 based on various input, e.g., input received from a user (e.g., via a touch screen and/or other user interfaces provided by ventilation system 12), data received from one or more sensors 24, and/or data received from other components or sub-systems of ventilation system 12. Gas delivery control system 31 may control the communication of gas to and/or from patient 11 by controlling, for example, the operation of gas delivery system 20 and/or the operation of one or more valves in order to control the pressure and/or flow rate of gas delivered to and/or communicated from patient 11.
[0080] For example, gas delivery control system 31 may regulate the pressure and/or flow rate of gas communicated to and/or from patient 11 based on pressure and/or flow data received from pressure and/or flow sensors 24. As another example, gas delivery control system 31 may shut down or reduce the pressure and/or flow rate of gas delivered to patient 11 based on signals received from over-pressure security system 32 indicating an over-pressure situation. As another example, gas delivery control system 31 may control the pressure and/or flow rate of gas communicated to and/or from patient 11 based on signals received from exhalation valve detection system 34 indicating whether or not an exhalation valve is being used in the current system configuration. As another example, gas delivery control system 31 may control the pressure and/or flow rate of gas communicated to and/or from patient 11 based on signals received from proximal pressure detection system 36 indicating whether or not a proximal pressure sensor is currently connected and operational. Example implementations of each of these techniques for controlling system 10 are discussed below.
[0081] Gas delivery control system 31 may include or have access to any instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for automatically controlling the operation of ventilation system 12 (e.g., controlling the pressure and/or flow rate output by gas delivery system 20 and/or controlling one or more valves) based on any of the various input data discussed herein.
[0082] Gas delivery control system 31 may control gas delivery system 20 directly, or by controlling another system or device configured to control gas delivery system 20. For example, in embodiments including a turbine-based blower 20, gas delivery control system 31 may control a turbine control device 200 (e.g., see FIG. 6 ), which in turn controls the turbine.
[0083] In some embodiments, gas delivery control system 31 may control gas delivery to patient 11 based on input from (a) outlet pressure sensor 80a (for measuring the pressure of gas exiting ventilation system 12 or entering connection system 14) and/or (b) proximal pressure sensor 80b (for measuring the pressure of gas in connection system 14 near patient 11). For example, as discussed below in the “Dual-Sensor System and Proximal Pressure Detection” section, system 12 may default to using proximal pressure sensor 80b for controlling ventilation, but switch to outlet pressure sensor 80a as a backup when proximal pressure line 100 is not connected to system 12 or the proximal pressure cannot effectively be used for some other reason.
[0084] As another example, gas delivery control system 31 may use readings from both outlet pressure sensor 80a and proximal pressure sensor 80b for controlling ventilation. For example, control system 31 may calculate an average, or weighted average, of readings from sensor 80a and sensor 80b to determine effective pressure values for use in controlling ventilation. As another example, control system 31 may calculate effective pressure values using any other algorithms) incorporating readings from both sensors 80a and 80b. One example algorithm provides:
PE=A*(Pproximal)+B*(Poutlet) (1)
PE=A*(Pproximal)+B*(Poutlet) (1)
[0085] where:
-
- [0086] PE=the effective pressure that may be used for controlling ventilation;
- [0087] Pproximal=pressure measured by proximal pressure sensor 80b;
- [0088] Poutlet=pressure measured by outlet pressure sensor 80a; and
- [0089] A and B are coefficients (e.g., positive values having a sum of 1.0).
Another example algorithm provides:
PE=A*(Pproximal)+B*(Poutlet+Pdrop) (2)
[0090] where Pdrop=a pressure drop compensation value. Pdrop may be an estimate of the pressure drop inherent in connection system 14 between outlet pressure sensor 80a and patient 11, which pressure drop may be a function of the flow rate through connection system 14. Pdrop may be determined in any known or suitable manner, e.g., using techniques described in co-pending EP Patent Application EP 08006240.9, filed on Mar. 31, 2008, and entitled “Systems and Methods for Compensating for Pressure Drop in a Breathing Assistance System.”
Dual-Sensor System and Proximal Pressure Detection
[0091] As discussed above, proximal pressure detection system 36 may be generally operable to determine whether proximal pressure may be effectively used by ventilation system 12 (e.g., if a proximal pressure line 100 is properly connected and the proximal pressure sensor 80b is providing useful readings) based on pressure signals received from one or more pressure sensors 24.
[0092] Gas delivery control system 31 may control the pressure and/or flow of gas delivered toward patient 11 based on one or both of (a) outlet pressure measured by outlet pressure sensor 80a and (b) proximal pressure measured by proximal pressure sensor 80b. As discussed above, proximal pressure measured by proximal pressure sensor 80b typically provides a more accurate measure of the patient pressure than outlet pressure measured by outlet pressure sensor 80a. Thus, it may be desirable to use proximal pressure for controlling the pressure and/or flow of delivered gas, assuming that proximal pressure may be effectively used for controlling ventilation (e.g., if a proximal pressure line 100 is properly connected and the proximal pressure sensor 80b is working properly). If proximal pressure cannot be effectively used for controlling ventilation (e.g., if a proximal pressure line 100 is not connected or is blocked, or if proximal pressure sensor 80b is not working properly), gas delivery control system 31 may use outlet pressure sensor 80a as a backup for measuring pressure for controlling ventilation; however, as such pressure measurements may be less accurate, the ventilation control may be less than optimal in certain ventilation modes or applications.
[0093] Therefore, proximal pressure detection system 36 may determine whether proximal pressure may be effectively used, e.g., by gas delivery control system 31 for controlling ventilation pressure and/or flow. Proximal pressure detection system 36 may compare measurements from outlet pressure sensor 80a with measurements from proximal pressure sensor 80b, and determine whether or not proximal pressure can be effectively used based on the results of such comparison. For example, proximal pressure detection system 36 may determine that proximal pressure can be effectively used if the outlet pressure (measured by sensor 80a) is greater than the proximal pressure (measured by sensor 80b), but not if the outlet pressure is less than or equal to the proximal pressure (during positive direction flow, i.e., toward patient 11). As another example, proximal pressure detection system 36 may determine that proximal pressure can be effectively used if the outlet pressure is greater than the proximal pressure, but not by more than a predetermined threshold value. The preceding examples assume positive direction flow (i.e., toward patient 11); for negative direction flow (i.e., away from patient 11), the analysis would be reversed.
[0094] As another example, proximal pressure detection system 36 may compare a proximal pressure measurement taken at a particular flow rate to a predetermined expected pressure value for the particular flow rate, and determine that proximal pressure can be effectively used if the measured proximal pressure does not differ from the expected pressure value by more than a predetermined threshold value.
[0095] In other embodiments, proximal pressure detection system 36 may separately determine (a) whether a proximal pressure line 100 is not connected to system 12 and (b) whether readings from proximal pressure sensor 80b are effective, or usable, and use both determinations for controlling various aspects of the operation of ventilation system 12.
[0096] Based on the results of any of such analyses discussed above, proximal pressure detection system 36 may communicate a notification to gas delivery control system 31 indicating whether proximal pressure cannot be effectively used. If proximal pressure cannot be effectively used, gas delivery control system 31 may subsequently use outlet pressures (measured by sensor 80a) for controlling ventilation, and/or may trigger an alarm or notification to the user that the proximal pressure system is not connected or not working property. The alarm may comprise any notification that may be sensed by a user, e.g., an audible alarm or a visible alarm displayed to the user, e.g., via display 28 or separate device (e.g., an LED). If proximal pressure can be effectively used, no alarm is triggered (although gas delivery control system 31 may notify the user that proximal pressure is being used) and ventilation may begin, or continue, using proximal pressure to control ventilation pressure and/or flow.
[0097] Proximal pressure detection system 36 may determine whether or not proximal pressure can be effectively used at any suitable time. For example, system 36 may perform such analysis prior to, or during, the initiation of ventilation in order to establish the most accurate control system. In addition, system 36 may perform such analysis periodically or substantially continuously during ventilation of patient 11, e.g., such that system 36 may adjust to a disconnection (or connection) of proximal pressure line 100 during ventilation. If gas delivery control system 31 is using proximal pressure to control ventilation, and system 36 determines that proximal pressure can no longer be effectively used (e.g., upon disconnection of proximal pressure line 100 from system 12), system 36 may notify gas delivery control system 31 such that gas delivery control system 31 can switch to using outlet pressure (measured by sensor 80a) and trigger an alarm that the proximal pressure system has been disconnected or is not working properly. Similarly, if gas delivery control system 31 is using outlet pressure to control ventilation, and system 36 determines that proximal pressure can now be effectively used (e.g., upon connection of proximal pressure line 100 to system 12), system 36 may notify gas delivery control system 31 such that gas delivery control system 31 can switch to using proximal pressure (measured by sensor 80b) to control ventilation. Thus, gas delivery control system 31 can automatically switch between using outlet pressure sensor 80a and proximal pressure sensor 80b, depending on whether proximal pressure can currently be used (e.g., depending on whether a pressure line 100 is currently connected).
[0098] In addition, in some embodiments, control system 22 may allow or disallow certain ventilation modes or settings based on whether gas delivery control system 31 is currently using outlet pressure or proximal pressure to control ventilation (e.g., based on whether or not a pressure line 100 is currently connected). For example, certain ventilation modes or settings may require accurate patient pressure readings that may be provided by proximal pressure sensor 80b but not by outlet pressure sensor 80a. Thus, control system 22 may disallow user selection of, and/or automatic switching to, such ventilation modes or settings while outlet pressure is being used to control ventilation (e.g., when pressure line 100 is not connected to system 12). An alarm or notification indicating that such ventilation modes or settings are not available due to pressure line 100 not being connected may be displayed to the user, e.g., via display 28. If a pressure line 100 is then connected/re-connected to system 12, control system 22 may allow user selection or switching to such disallowed ventilation modes or settings.
[0099] In some embodiments, if proximal pressure line 100 becomes disconnected while operating according to a ventilation mode or settings that requires proximal pressure readings (from sensor 80b), proximal pressure detection system 36 may detect the disconnection and gas delivery control system 31 may automatically adjust the ventilation (e.g., by switching to a different ventilation mode or adjusting one or more settings) to be compliant with operation based on outlet pressure readings (from sensor 80a). Gas delivery control system 31 may also generate an alarm or notification to the user that the proximal pressure line is disconnected and/or that the ventilation mode or settings have been automatically changed. If proximal pressure line 100 is then re-connected while operating according to the changed ventilation mode or settings based on outlet pressure readings, proximal pressure detection system 36 may detect the re-connection and gas delivery control system 31 may automatically switch back to the previous ventilation mode or settings, or may automatically display to the user a selectable option to return to such previous ventilation mode or settings.
[0100] Proximal pressure detection system 36 may include or have access to one or more controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for providing any of the various functionality discussed herein. Such memory device(s) may store instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for providing such functionality. Proximal pressure detection system 36 may be partially or fully integrated with, or may be distinct from, gas delivery control system 31.
Over-Pressure Security
[0101] As discussed above, over-pressure security system 32 is generally operable to detect and facilitate the management of over-pressure of gas in connection system 14 (e.g., in breathing circuit 16) based on pressure signals received from one or more pressure sensors 24. For example, over-pressure security system 32 may provide either or both of the levels of over-pressure security discussed below.
[0102] A first level of over-pressure security is based on redundancy of pressure measurements from outlet pressure sensor 80a and proximal pressure sensor 80b. As discussed above, outlet pressure sensor 80a may measure pressure at or near a main gas outlet of ventilation system 12 (i.e., the pressure of gas flow entering connection system 14), and proximal pressure sensor 80b may measure “proximal pressure” at or near the open end (i.e., the patient end) of a proximal pressure line 100 extending along a limb of breathing circuit 16. The two sensors 80a and 80b may produce different results due to pressure drop inherent in breathing circuit 16.
[0103] The first level of over-pressure security involves monitoring both outlet pressure sensor 80a and proximal pressure sensor 80b to detect an over-pressure condition in connection system 14. For example, over-pressure security system 32 may compare pressure measurements received from sensors 80a and 80b to one or more threshold pressure values to automatically detect an over-pressure condition. Pressure measurements from both sensors 80a and 80b may be compared to a single pressure threshold value, or each sensor's measurements may be compared to a separate corresponding pressure threshold value. Such pressure threshold value(s) may be determined in any suitable manner, and may vary over time.
[0104] If some embodiments, the determination of pressure threshold values depends on the selected ventilation mode and/or breath type. For example, in one embodiment:
-
- [0105] For Volume modes, the pressure threshold value is set by a user via GUT 40 as a “high pressure” alarm threshold.
- [0106] For Pressure modes, the pressure threshold value is automatically calculated on the basis of the ventilation pressure set by the user via GUT 40, e.g., according to the equation.
Pressure threshold=Pcontrol(or Psupport)+X%
[0107] where:
-
- [0108] Pcontrol represents the pressure setting in a Control mode;
- [0109] Psupport represents the pressure setting in a Support mode; and
- [0110] X is a preset coefficient, e.g., 10% or 20%.
[0111] If over-pressure security system 32 detects an over-pressure condition, system 32 may generate an over-pressure signal to gas delivery control system 31 (and/or to an alarm system) indicating details of the over-pressure condition (e.g., relevant pressure measurement(s) and threshold value(s)). In response, gas delivery control system 31 may control gas delivery system 20 in order to end the over-pressure condition, for example by reducing the pressure or flow rate produced by gas delivery system 20 (e.g., to a pressure at or just below a threshold pressure value, or to a lower pressure) or by shutting down gas delivery system 20. For example, in embodiments in which gas delivery system 20 includes a blower (e.g., a turbine-based blower), gas delivery control system 31 may reduce the speed of the blower.
[0112] Monitoring signals from both sensors 80a and 80b may provide redundancy to account for situations in which 80a or 80b is not providing useful data, e.g., where one of sensors 80a and 80b is damaged or not working properly, or where a proximal pressure line 100 is not used or is blocked.
[0113] A second level of over-pressure security is based on pressure measurements from exhalation valve pressure sensor 80c used for detecting the presence of an exhalation valve 96 and controlling the operation of such exhalation valve 96 (e.g., by generating pressure signals used to control a pilot valve 102 that controls exhalation valve 96, as discussed above). For certain exhalation valves 96, the effective surface area upon which gas pressure acts from the command side of the valve (i.e., the side facing exhalation valve control line 98) is larger than the effective surface area upon which gas pressure acts from the breathing circuit side of the valve (i.e., the side facing exhalation valve control line 98). Such configuration may provide the desired sealing of exhalation valve 96.
[0114] In normal operation, exhalation valve pressure sensor 80c may be automatically controlled to maintain an internal pressure inside exhalation valve 96 substantially equal to the pressure inside breathing circuit 16 near valve 96, based on pressure measurements from pressure sensors 80a, 80b, and/or 80c. However, in an over-pressure situation, the internal pressure inside exhalation valve 96 may be automatically maintained at a maximum setting level (e.g., an IPAP setting if operating in a barometric mode or a “high pressure” setting if operating in a volumetric mode) based at least on pressure measurements from exhalation valve pressure sensor 80c. In such situation, the pressure inside breathing circuit 16 may exceed the internal pressure inside exhalation valve 96, and exhalation valve 96 may leak, thus reducing and/or limiting the pressure in breathing circuit 16.
[0115] Thus, in embodiments or situations in which the first level of over-pressure security is not provided or not effective (e.g., where both sensors 80a and 80b fail, or where gas delivery control system 31 fails to correct an over-pressure situation), the internal pressure inside exhalation valve 96 may be limited based on measurements from exhalation valve pressure sensor 80c, providing leakage through exhalation valve 96, thus reducing and/or limiting the pressure in breathing circuit 16. In this manner, exhalation valve pressure sensor 80c may facilitate the second level of over-pressure security.
[0116] Over-pressure security system 32 may include or have access to one or more controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for providing any of the various functionality discussed herein. Such memory device(s) may store instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for providing such functionality. Over-pressure security system 32 may be partially or fully integrated with, or may be distinct from, gas delivery control system 31.
Exhalation Valve Detection
[0117] As discussed above, exhalation valve detection system 34 is generally operable to determine whether an exhalation valve 96 is present in the current configuration of system 10 (e.g., whether the currently connected breathing circuit 16 includes an exhalation valve 96) based on pressure signals received from one or more pressure sensors 24.
[0118] In some embodiments, exhalation valve pressure sensor 80c may be used to detect whether an exhalation valve 96 is present. For example, gas may be delivered through an outlet configured for connection to an exhalation valve control line 98. If an exhalation valve control line 98 leading to an exhalation valve 96 is present, pressure in exhalation valve control line 98 increases, which increased pressure may be detected by exhalation valve pressure sensor 80c. However, if an exhalation valve control line 98 leading to an exhalation valve 96 is not present, pressure in exhalation valve control line 98 remains low, which low pressure may be detected by exhalation valve pressure sensor 80c. The pressure measured by exhalation valve pressure sensor 80c may thus be compared against an appropriate threshold value to determine whether an exhalation valve 96 is present. Such threshold value may be determined in any suitable manner, and may depend upon various factors, e.g., the current ventilation mode, a flow rate setting, or a pressure setting.
[0119] In one embodiment, exhalation valve pressure sensor 80c is connected to a command port of a pilot valve 102 (e.g., an electro valve) that controls exhalation valve 96 on breathing circuit 16 via exhalation valve control line 98. At the beginning of ventilation, pilot valve 102 opens in order to fill exhalation valve 96 via an exhalation valve control line 98 that may be connected to ventilation system 12. If an exhalation valve control line 98 with exhalation valve 96 is connected to ventilation system 12, pressure in exhalation valve control line 98 increases, which is detected by sensor 80c. However, if an exhalation valve control line 98 with exhalation valve 96 is not connected to ventilation system 12, pressure in exhalation valve control line 98 remains low, which is detected by sensor 80c.
[0120] Exhalation valve detection system 34 may communicate a notification to gas delivery control system 31 indicating whether system 10 includes an exhalation valve 96. Gas delivery control system 31 may automatically select between different ventilation styles or modes or otherwise control one or more ventilation parameters (e.g., flow and/or pressure) based on such notification, e.g., by controlling gas delivery system 20.
[0121] For example, in some embodiments, ventilation system 12 can provide either leakage ventilation or exhalation valve ventilation. Gas delivery control system 31 may automatically control ventilation parameters (e.g., ventilation flow and pressure) to provide either leakage ventilation or exhalation valve ventilation, based on whether or not system 10 includes an exhalation valve 96. If system 10 includes an exhalation valve 96 (e.g., a dual-limb breathing circuit 16 is connected to system 12), gas delivery control system 31 may automatically adapt to provide exhalation valve ventilation; alternatively, if system 10 does not include an exhalation valve 96 (e.g., a single-limb breathing circuit 16 is connected to system 12), gas delivery control system 31 may automatically adapt to provide leakage ventilation. However, if selected ventilator settings or ventilation mode are incompatible with the relevant ventilation type (leakage ventilation or exhalation valve ventilation), gas delivery control system 31 may trigger an alarm and wait for the user to adjust the selected settings to become compatible before beginning ventilation of patient 11. The alarm may comprise any notification that may be sensed by a user, e.g., an audible alarm or a visible alarm displayed to the user, e.g., via display 28 or separate device (e.g., an LED).
[0122] Exhalation valve detection system 34 may include or have access to one or more controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for providing any of the various functionality discussed herein. Such memory device(s) may store instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for providing such functionality. Exhalation valve detection system 34 may be partially or fully integrated with, or may be distinct from, gas delivery control system 31.
Power System/Battery
[0123] FIG. 3 illustrates details of an example power system 30 for ventilation system 12, according to certain embodiments of the present disclosure. Power system 30 may include or facilitate the connection of one or more sources of power for ventilation system 12, such as an external AC power source, an external DC power source, and/or one or more rechargeable batteries 50, for example. In some embodiments, power system 30 may include one or more converters 124 (e.g., a DC/DC converter and/or an AC/DC converter). One or more power sources may be removable from ventilation system 12. For example, an AC or DC power source or may be plugged into and/or unplugged from ventilation system 12 via one or more power source connections 120. As another example, one or more rechargeable batteries 50 may be inserted into and/or removed from ventilation system 12. In some embodiments, ventilation system 12 may be configured for one or more “swappable” or “hot swappable” batteries 50. In the example embodiment discussed below with reference to FIG. 6 , power system 30 may include a lithium battery 50, a connection 120a for an external 110/220V AC power source, a connection 120b for an external 24V DC power source, a battery charger 124, and a power supply switchover 126 for switching between the battery 50 and an external AC or DC power source.
[0124] In some embodiments including a battery 50, power system 30 may include a battery security system 52 for ensuring that only compliant or authorized batteries may be used in ventilation system 12 and/or a battery age management system 70 for recording and displaying age data regarding a battery 50, e.g., the number of charge and discharge cycles the battery 50 has experienced.
[0125] Battery security system 52 may include a data read device 55, a battery identification module 56, and approval data 60 stored in memory 62 or otherwise accessible by battery identification module 56. Battery security system 52 is generally operable to read battery identification data 54 from battery 50 and determine, based on such data 54, whether battery 50 is approved for use in ventilation system 12. For example, battery security system 52 may compare battery identification data 54 read from a battery 50 with approval data 60 to determine whether the battery 50 is approved.
[0126] Battery identification data 54 may be stored in battery 50 (e.g., stored in memory), marked on battery 50 (e.g., a scanable bar code), or otherwise associated with battery 50. In some embodiments, battery identification data 54 may be stored in memory 58 in battery 50. Memory 58 may comprise any type of tangible memory device configured to store electronic data (e.g., RAM, DRAM, ROM, EPROM, Flash memory, or any other memory or storage device). In an example embodiment, memory 58 may comprise a single pin memory configuration such that read and write operations occur through the same pin.
[0127] Battery identification data 54 may include any data that may be used for determining whether battery 50 is compliant or authorized, e.g., a product ID number, data identifying the battery manufacturer, data identifying production data (e.g., a date code), data identifying the battery type, data identifying the storage capacity, etc. Battery identification data 54 may or may not be encrypted. In particular embodiments, battery identification data 54 is not encrypted such that neither battery 50 nor system 12 includes encoders and/or decoders for such data.
[0128] Approval data 60 may include, for example, approved product ID numbers, approved battery manufacturer(s), approved production data (e.g., approved date codes), approved battery type(s), and/or approved storage capacity(ies). Approval data may be stored in memory 62, which may comprise any type of tangible memory device configured to store electronic data (e.g., RAM, DRAM, ROM, EPROM, Flash memory, or any other memory or storage device).
[0129] Data read device 55 may comprise any device configured to read data from battery 50. In particular, data read device 55 may read battery identification data 54 from memory 58 in battery 50.
[0130] Battery identification module 56 is generally operable to determine, based on battery identification data 54 read by data read device 55, whether battery 50 is compliant or authorized for use in ventilation system 12. For example, battery identification module 56 may compare battery identification data 54 read from battery 50 with approval data 60 to determine whether the battery 50 is approved.
[0131] If battery identification module 56 determines, based on battery identification data 54 read from a battery 50 and/or approval data 60, that a battery 50 inserted in ventilation system 12 is compliant or authorized, module 56 will allow the battery 50 to provide power to system 12 and not trigger an alarm. However, if battery identification module 56 determines that a battery 50 inserted in ventilation system 12 is not compliant or not authorized, module 56 may prevent battery 50 from providing power to system 12 and/or may generate a signal to trigger an alarm 64 to notify the user to remove the non-compliant/unauthorized battery. Alarm 64 may comprise any notification that may be sensed by a user, e.g., audible alarm or a visible alarm displayed to the user. A visible alarm may be displayed in any suitable manner, e.g., an image or text displayed on display 28 or an LED or other light or visible device separate from display 28.
[0132] Battery security system 52 may perform such battery authorization process discussed above at any suitable time(s), e.g., upon a triggering event, such as the insertion of battery 50 into system 12 or system 12 being turned on, or in response to a manual user request to check the battery. In some embodiments, battery security system 52 may also automatically perform the battery authorization process periodically, e.g., every hour.
[0133] As discussed above, power system 30 may include a battery age management system 70 for recording and displaying age data regarding a battery 50. Battery age management system 70 may include a data read/write device 76 configured to write data to and/or read data from memory 58, including battery age data 72. Battery age data 72 may be stored in memory 58. In alternative embodiments, battery age data 72 and battery identification data 54 may be stored in separate memory devices in battery 50.
[0134] Battery age data 72 may include any data regarding the age or usage of a battery 50, e.g., the usage time (e.g., total hours of use), the total number of charge/discharge cycles the battery 50 has experienced, the usage time since the last charge, the effective usage time for the previous charge before needing recharge, etc.
[0135] Battery age data 72 may be stored and/or updated in memory 58 in battery 50 in any suitable manner. For example, data read/write device 76 may write battery age data 72 to memory 58 and/or update battery age data 72 stored in memory 58. Updating battery age data 72 may include storing updated data over existing stored data, or storing updated data in addition to existing stored data. Data read/write device 76 may write any type of battery age data 72 to memory 58. Data read/write device 76 may write such data at any suitable time, e.g., periodically or upon a triggering event, such as the beginning or completion of a charge or discharge of battery 50, ventilation system 12 being turned on or off, or ventilation system 12 being plugged into or unplugged from an external power source. Data read/write device 76 may include or have access to a clock or timer 77.
[0136] Data read/write device 76 may also read any type of battery age data 72 from memory 58 in battery 50. Data read/write device 76 may read such data at any suitable time, e.g., periodically or upon a triggering event, such as the beginning or completion of a charge or discharge of battery 50, ventilation system 12 being turned on or off, ventilation system 12 being plugged into or unplugged from an external power source, or in response to a user request.
[0137] Data read/write device 76 may be configured to display or generate signals for displaying any type of battery age data 72 from memory 58. For example, data read/write device 76 may be generate signals for displaying the total number of charge/discharge cycles the battery 50 has experienced on display 28. In an example embodiment, GUI 40 provides a user interface for accessing various types of battery age data 72 (e.g., using buttons, menus, or other interfaces for selecting the desired battery age data 72).
[0138] In other embodiments, battery 50 itself may include processing resources, software or firmware, and/or a clock or timer configured to store and/or update battery age data 72 in memory 50. For example, battery 50 may use such resources to generate and store/update any type of battery age data 72 in memory 50 periodically or upon a triggering event, e.g., the beginning or completion of a charge or discharge of battery 50, ventilation system 12 being turned on or off, or ventilation system 12 being plugged into or unplugged from an external power source. Such triggering events may be detected by battery 50 itself or via signals communicated from battery age management system 70.
[0139] Battery 50 may also include a temperature sensor 74 for monitoring the temperature of battery 50. In some embodiments, temperature sensor 74 is not electrically connected to memory 58.
[0140] As shown in FIG. 3 , battery 50 may have four contacts: (1) a positive terminal 66, (2) a negative terminal 67, (3) a memory contact 68, and (4) a temperature sensor contact 69. Positive and negative terminals 66, 67 are connected to circuitry within system 12 to provide power to system loads. Memory contact 68 may be connected to data read device 55 of battery security system 52 and/or data read/write device 76 of battery age management system 70, allowing read device 55 and/or data read/write device 76 to communicate data (e.g., battery ID data 54 and/or battery age data 72) to/from memory 58. Temperature sensor contact 69 may provide an interface for communicating battery temperature measurements to one or more components of system 12, e.g., a security system configured to determine whether battery 50 is overheating and respond accordingly.
O2 Safety System
[0141] O2 safety system 38 is generally configured to slow or stop supplemental oxygen flow when gas delivery system 20 (e.g., a blower) is overheating and/or not running property. O2 safety system 38 may receive signals from one or more of (a) a temperature sensor 83 configured to measure a temperature of gas delivery system 20 (e.g., a blower); (b) a speed sensor 84 configured to measure an operational speed of a component (e.g., a motor, blower, turbine) of gas delivery system 20; and/or (c) a power monitor 85 configured to measure the power drawn by a component (e.g., a motor, blower, turbine) of gas delivery system 20. If O2 safety system 38 determines an overheat or a danger condition, O2 safety system 38 may generate a command to close an O2 shut-off valve (e.g., O2 safety valve shown in FIGS. 4A , 4B, and 5) to slow or stop the flow of supplemental oxygen.
[0142] FIGS. 4A and 4B illustrate an example O2 safety system 38 for use with ventilation system 12, according to certain embodiments of the present disclosure. As discussed above, O2 safety system 38 is generally configured to slow or stop a supplemental oxygen flow when gas delivery system 20 (e.g., a blower) is overheating and/or not running properly. As used herein, supplemental oxygen refers to any oxygen-rich gas used to supplement the main gas flow (e.g., air) delivered to a patient 11. For example, supplemental oxygen may include pure oxygen or any other gas having an oxygen concentration greater than air. As used herein, reference to slowing or stopping a supplemental oxygen flow may refer to slowing or stopping the flow of supplemental oxygen from the supplemental oxygen supply (e.g., a tank, a concentrator, or a line from the wall) to the patient 11. For example, slowing or stopping a supplemental oxygen flow may refer to slowing or stopping a flow of supplemental oxygen into ventilation system 12 via a supplemental oxygen inlet (e.g., O2 inlet 154) or through a valve of ventilation system 12 (e.g., O2 safety valve 156). As another example, slowing or stopping a supplemental oxygen flow may refer to opening a release or vent valve to allow supplemental oxygen to flow out and/or away from ventilation system 12.
[0143] FIG. 4A illustrates an example O2 safety system 38 in which the supplemental oxygen flow may be controlled based on temperature measurements, e.g., to slow or stop the supplemental oxygen flow in the event of an detected overheat condition. As shown in FIG. 4A , O2 safety system 38 may include a temperature sensor 83, an overheat detection module 158, an O2 safety valve 156, and/or logic associated with gas delivery control system 31.
[0144] Temperature sensor 83 is configured to measure the temperature of one or more components of gas delivery system 20 (e.g., a component of a turbine-based blower). Temperature sensor 83 may take temperature measurements at any suitable time and/or frequency, e.g., substantially continuously, periodically (e.g., every 30 seconds), or in response to an event (e.g., a request received from a user).
[0145] Overheat detection module 158 is generally configured to determine whether gas delivery system 20 is overheating by monitoring readings from temperature sensor 83. For example, overheat detection module 158 may compare readings from temperature sensor 83 with threshold temperature(s) to determine whether gas delivery system 20 is overheating. Such threshold temperature(s) may be constant or may change over time. For example, a threshold temperature may be determined using an algorithm or look-up table relating the threshold value to one or more other parameters, e.g., the current pressure or flow rate of gas delivered by delivery system 20, or the current speed of a turbine (in embodiments in which gas delivery system 20 comprises a turbine-based blower). Thus, for example, an algorithm may be used to increase the threshold temperature in proportion to the flow rate or turbine speed, as higher temperatures are expected with higher flow rates or turbine speeds.
[0146] As another example, different threshold temperatures may be used for different ventilation modes or conditions. For example, different threshold temperatures may be used for SIMV ventilation, Assist/Control ventilation, and CPAP ventilation. As another example, different threshold temperatures may be used for adult vs. pediatric ventilation, as higher temperatures are expected with adult ventilation (e.g., due to higher flow rates or turbine speeds).
[0147] Threshold temperatures may be pre-programmed into overheat detection module 158 and/or gas delivery control system 31. Alternatively, threshold temperatures may be set or modified by a user, e.g., an authorized technician. Threshold temperatures may be determined based on empirical data, data regarding various system components (e.g., a maximum temperature that a blower motor can support), based on industry regulations, or determined in any other suitable manner.
[0148] In some embodiments, overheat detection module 158 may determine two different overheat levels based on different threshold temperatures—a first overheat level that triggers control of O2 safety valve and a second overheat level that triggers control of gas delivery system 20. The first overheat level may be lower than, higher than, or the same as the second overheat level. For example, overheat detection module 158 may determine a first overheat level (for triggering control of O2 safety valve) if the measured temperature exceeds a first threshold temperature T1, and a second overheat level (for triggering control of gas delivery system 20) if the measured temperature exceeds a second threshold temperature T2, where T2>T1. Thus, while operating between T1 and T2, gas delivery system 20 may continue to ventilate patient 11 after O2 safety valve has been closed to slow or stop the flow of supplemental oxygen.
[0149] In some embodiments, overheat detection module 158 may determine additional overheat levels for triggering control of different components of system 10 based on various threshold temperatures. Each threshold temperature T1, T2, etc. may be determined in any suitable manner, e.g., as discussed above.
[0150] Overheat detection module 158 may determine that gas delivery system 20 is overheating based on any number of readings from temperature sensor 83. For example, overheat detection module 158 may determine an overheat condition in response to a single sensor reading above the relevant threshold temperature. As another example, overheat detection module 158 may determine an overheat condition based on a predetermined number (e.g., 5) of consecutive sensor readings above the relevant threshold temperature, based on sensor readings remaining above the relevant threshold temperature for a predetermined duration (e.g., 10 seconds). As another example, overheat detection module 158 may determine an overheat condition based on an average of sensor readings for a predetermined number of readings or over a predetermined duration.
[0151] In response to determining an overheat condition in gas delivery system 20, overheat detection module 158 may send an overheat notification signal to gas delivery control system 31. Based on such signal, gas delivery control system 31 may control O2 safety valve and/or gas delivery system 20 accordingly. For example, gas delivery control system 31 may partially or fully close O2 safety valve to slow or stop the flow of supplemental oxygen. O2 safety valve may comprise any suitable type of valve. O2 safety valve may be separate from, or integrated with, O2 inlet 154.
[0152] In addition, in some embodiments, gas delivery control system 31 may control gas delivery system 20 in response to an overheat condition. For example, where gas delivery system 20 includes a blower, gas delivery control system 31 may slow or stop the blower in order to reduce the temperature of gas delivery system 20.
[0153] In some embodiments, gas delivery control system 31 may control both O2 safety valve and gas delivery system 20 based on a single overheat notification signal. In embodiments using a first overheat level for triggering control of O2 safety valve and a second overheat level for triggering control of gas delivery system 20, gas delivery control system 31 may control O2 safety valve and gas delivery system 20 separately according to the relevant overheat signals received from overheat detection module 158.
[0154] In some embodiments, gas delivery control system 31 may control (e.g., close) O2 safety valve based on either of the following input: (a) an overheat notification signal from overheat detection module 158 or (b) a notification of an event regarding gas delivery system 20, e.g., that gas delivery system 20 is not delivering gas (e.g., turned off or in standby mode) or is not operating properly. Thus, for example, the flow of supplemental oxygen may be slowed or stopped if gas delivery system 20 is overheating, turned off, in standby mode, or not operating properly.
[0155] Overheat detection module 158 and/or gas delivery control system 31 may generate any suitable alarm(s) 159 regarding overheat conditions and/or the closing of O2 safety valve to slow or stop the flow of supplemental oxygen. An alarm 159 may comprise any notification that may be sensed by a user, e.g., audible alarm or a visible alarm displayed to the user. A visible alarm may be displayed in any suitable manner, e.g., an image or text displayed on display 28 or an LED or other light or visible device separate from display 28.
[0156] Overheat detection module 158 may include or have access to one or more controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for providing any of the various functionality discussed herein. Such memory device(s) may store instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for providing such functionality. Overheat detection module 158 may be partially or fully integrated with, or may be distinct from, gas delivery control system 31.
[0157] FIG. 4B illustrates an example O2 safety system 38 in which the supplemental oxygen flow may be controlled based on any combination of temperature measurements, speed measurements related to gas delivery system 20 (e.g., the speed of a blower motor), and the power drawn by gas delivery system 20 (e.g., the power drawn by a blower motor). The O2 safety system 38 of FIG. 4B may be particularly suitable for embodiments of ventilation system 12 in which gas delivery system 20 includes a motor, e.g., for a blower or turbine.
[0158] As shown in FIG. 4B , O2 safety system 38 may include a temperature sensor 83, a speed sensor 84, a power monitor 85, a safety status module 161, an O2 safety valve 156, and/or logic associated with gas delivery control system 31.
[0159] Temperature sensor 83 is generally discussed above regarding FIG. 4A . Speed sensor 84 may comprise any system or device configured to measure an operational speed of a motor, blower, turbine, or other component of gas delivery system 20. Power monitor 85 may comprise any system or device configured to measure the power drawn by a motor, blower, turbine, or other component of gas delivery system 20.
[0160] Safety status module 161 is generally configured to analyze the operational safety status of gas delivery system 20, including determining conditions regarding gas delivery system 20 (e.g., overheating of a blower motor) that call for controlling O2 safety valve 156. Such conditions are referred to herein as “danger conditions.” Safety status module 161 may analyze the operational safety status of gas delivery system 20, including determining danger conditions, based on any combination of some or all of the following types of data, referred to herein as “O2 safety data”:
[0161] (a) temperature measurements at one or more locations of ventilation system 12;
[0162] (b) speed measurements related to gas delivery system 20 (e.g., the speed of a blower motor, fan, or turbine); and/or
[0163] (c) measurements of the power drawn by gas delivery system 20 or certain component(s) thereof (e.g., the power drawn by a blower motor).
[0164] In some embodiments, safety status module 161 may calculate a safety factor using one or more algorithms relating different types of measured O2 safety data, and compare the calculated safety factor to a danger condition threshold value to determine whether a danger condition is present.
[0165] In other embodiments, safety status module 161 may access look-up tables 163 relating different types of measured O2 safety data to determine whether a danger condition is present. For example, for an embodiment using temperature measurements and speed measurements as O2 safety data, look-up tables 163 may include a table indicating whether a danger condition is present for various combinations of temperature measurements and speed measurements.
[0166] As another example, for an embodiment using temperature measurements and power measurements as O2 safety data, look-up tables 163 may include a table indicating whether a danger condition is present for various combinations of temperature measurements and power measurements.
[0167] As another example, for an embodiment using speed measurements and power measurements as O2 safety data, look-up tables 163 may include tables indicating whether a danger condition is present for various combinations of speed measurements and power measurements.
[0168] As another example, for an embodiment using temperature measurements, speed measurements, and power measurements as O2 safety data, look-up tables 163 may include tables indicating whether a danger condition is present for various combinations of temperature measurements, speed measurements, and power measurements.
[0169] Look-up tables 163 may be stored in any suitable storage medium associated with ventilation system 12. Look-up tables 163 may be generated in any suitable manner; e.g., using mathematical algorithms or based on empirical testing.
[0170] In other embodiments, safety status module 161 may determine whether a danger condition is present by comparing individual types of O2 safety data to corresponding threshold values. In some embodiments, the danger condition determination may include a series of two or more threshold comparisons.
[0171] For example, for an embodiment using temperature measurements and speed measurements as O2 safety data, safety status module 161 may identify a danger condition where (a) a current temperature measurement surpasses (e.g., is higher than) a temperature threshold value and (b) a current speed measurement surpasses (e.g. is lower than) a speed threshold value.
[0172] As another example, for an embodiment using temperature measurements and power measurements as O2 safety data, safety status module 161 may identify a danger condition where (a) a current temperature measurement surpasses a temperature threshold value and (b) a current power measurement surpasses a power threshold value.
[0173] As another example, for an embodiment using speed measurements and power measurements as O2 safety data, safety status module 161 may identify a danger condition where (a) a current speed measurement surpasses (e.g., is lower than) a speed threshold value and (b) a current power measurement surpasses (e.g., is higher than) a power threshold value.
[0174] As another example, for an embodiment using temperature measurements, speed measurements, and power measurements as O2 safety data, safety status module 611 may identify a danger condition where (a) a current temperature measurement surpasses a temperature threshold value, (b) a current speed measurement surpasses a speed threshold value, and (c) a current power measurement surpasses a power threshold value.
[0175] As used herein, the term “surpassed” may refer to a measurement rising above a threshold value or to a measurement falling below a threshold value, depending on the particular embodiment and the particular setting for the threshold value. For example, in certain applications, a motor speed threshold value of 1,000 rpm may be surpassed when the motor speed increases above 1,000 rpm, while in other applications the motor speed threshold value may be surpassed when the motor speed falls below 1,000 rpm.
[0176] Each of the threshold values used by safety status module 161 (e.g., temperature threshold values, speed threshold values, and/or power threshold values) may be determined in any suitable manner and may be constant or may change over time. For example, a particular threshold value may be determined using an algorithm or look-up table relating the threshold value to one or more other parameters, e.g., the current pressure or flow rate of gas delivered by delivery system 20, or the current speed of a turbine (in embodiments in which gas delivery system 20 comprises a turbine-based blower).
[0177] As another example, different threshold values may be used for different ventilation modes or conditions. For example, different threshold values may be used for SIMV ventilation, Assist/Control ventilation, and CPAP ventilation. As another example, different threshold values may be used for adult vs. pediatric ventilation, as higher temperatures are expected with adult ventilation (e.g., due to higher flow rates or turbine speeds).
[0178] One or more threshold values may be pre-programmed into overheat detection module 158 and/or gas delivery control system 31. Alternatively, one or more threshold values may be set or modified by a user, e.g., an authorized technician. One or more threshold values may be determined based on empirical data, data regarding material properties of various system components, based on industry regulations, or determined in any other suitable manner.
[0179] In embodiments in which safety status module 161 compares temperature measurements to a temperature threshold value, safety status module 161 may cooperate with an overheat detection module 158, which may provide any of the functionality discussed above with respect to FIG. 4A , e.g., using different threshold temperatures for determining different overheat levels for triggering control of different components of system 10 based on various threshold temperatures.
[0180] Safety status module 161 may identify a danger condition based on any number of readings from temperature sensor 83, speed sensor 84, and/or power monitor 85. For example, in an embodiment using temperature sensor 83 and speed sensor 84, safety status module 161 may identify a danger condition based on a single reading from each of temperature sensor 83 and speed sensor 84. As another example, safety status module 161 may identify a danger condition based on a predetermined number (e.g., 5) of consecutive readings from sensors 83 and 84 indicate a danger condition, or where consecutive sensor readings indicate a danger condition for more than a predetermined duration (e.g., 10 seconds), or where an average of sensor readings for a predetermined number of readings or over a predetermined duration indicate a danger condition.
[0181] In response to determining a danger condition in gas delivery system 20, safety status module 161 may send a danger condition notification signal to gas delivery control system 31. Based on such signal, gas delivery control system 31 may control O2 safety valve and/or gas delivery system 20 accordingly. For example, gas delivery control system 31 may partially or fully close O2 safety valve to slow or stop the flow of supplemental oxygen. O2 safety valve may comprise any suitable type of valve. O2 safety valve may be separate from, or integrated with, O2 inlet 154.
[0182] In addition, in some embodiments, gas delivery control system 31 may control gas delivery system 20 in response to a danger condition. For example, where gas delivery system 20 includes a blower, gas delivery control system 31 may slow or stop the blower in order to reduce the temperature of gas delivery system 20.
[0183] In some embodiments, gas delivery control system 31 may control both O2 safety valve and gas delivery system 20 based on a single danger condition notification signal. In some embodiments, gas delivery control system 31 may control O2 safety valve and gas delivery system 20 separately according to different danger condition threshold levels.
[0184] In some embodiments, gas delivery control system 31 may control (e.g., close) O2 safety valve based on either of the following input: (a) a danger condition notification signal from safety status module 161 or (b) a notification of an event regarding gas delivery system 20, e.g., that gas delivery system 20 is not delivering gas (e.g., turned off or in standby mode) or is not operating properly. Thus, for example, the flow of supplemental oxygen may be slowed or stopped if gas delivery system 20 is overheating, turned off, in standby mode, or not operating properly.
[0185] Safety status module 161 and/or gas delivery control system 31 may generate any suitable alarm(s) 159 regarding danger conditions and/or the closing of O2 safety valve to slow or stop the flow of supplemental oxygen. An alarm 159 may comprise any notification that may be sensed by a user, e.g., audible alarm or a visible alarm displayed to the user. A visible alarm may be displayed in any suitable manner, e.g., an image or text displayed on display 28 or an LED or other light or visible device separate from display 28.
[0186] Safety status module 161 may include or have access to one or more controllers, processors, memory devices, and any other suitable hardware, software, and/or firmware for providing any of the various functionality discussed herein. Such memory device(s) may store instructions (e.g., any suitable software, algorithms, or other logic or instructions that may be executed by one or more processors) for providing such functionality. Safety status module 161 may be partially or fully integrated with, or may be distinct from, gas delivery control system 31.
[0187] Although the discussion herein focuses on safety systems for a supplemental supply of oxygen, the various techniques discussed herein may similarly be used for providing a safety system for a supply of any other type of gas or gas mixture (e.g., an oxygen-rich mixture).
Example Ventilation Systems
[0188] FIG. 5 illustrates a flow path diagram showing various components and gas flow paths in an example embodiment of ventilation system 12, indicated as ventilation system 12a, according to one embodiment of the present disclosure. The particular set of components, and arrangement of such components, shown in ventilation system 12a represent only an example embodiment ventilation system 12; in other embodiments ventilation system 12 may include different components and/or a different arrangement of components.
[0189] An example dual-limb breathing circuit 16 is shown connected to ventilation system 12a. However, a different type of dual-limb breathing circuit, or a single-limb breathing circuit, may be connected to ventilation system 12a.
[0190] Ventilation system 12a provides a first flow path for air flow and a second, optional flow path for supplemental oxygen. Air flow path may include an air inlet filter 140, an inlet silencer 150, a turbine-based blower 20, and an outlet silencer 152. Air inlet filter 140 may be any filter suitable for filtering or cleaning air before entering turbine 20. For example, air inlet filter 140 may comprise a double material filter, e.g., including a fine particulate portion and a rough foam portion. Turbine 20 may comprise a high-speed, low-inertia air compressor configured to control the air flow and/or pressure through the mainstream pathway toward inspiration flow outlet 130. Silencers 150 and 152 may comprise any noise devices for suppressing noise from the inlet or outlet interfaces of turbine 20. For example, silencers 150 and 152 may comprise any suitable materials that provide noise damping, absorbing, and/or insulating, e.g., foams and other materials such as those provided by PINTA ENAC S.A.S. (http://www.pinta-enac.com/index_eng.html). In addition, such foams or other noise controlling materials may be configured to form a labyrinth or other convoluted or tortuous path to provide additional noise control.
[0191] The supplemental oxygen flow path may include an O2 inlet 154 and an O2 safety valve, after which the path may combine with the air flow path at a union 128. Oxygen inlet 154 may comprise a low-pressure oxygen inlet interface for connecting to a supplemental oxygen source (e.g., a tank, compressor, or line-in from a wall). It may include a safety coupling valve for preventing leakage during disconnection of the oxygen source. O2 safety valve may close oxygen inlet 154 when ventilation system 12a is turned off or otherwise not providing ventilation, e.g., as discussed above regarding O2 safety system 38.
[0192] The combined paths may then continue toward an inspiration flow outlet 130, to which an inspiration limb 90 of breathing circuit 16 may be connected. An over-pressure pressure relief valve 160, an inspiration flow sensor 82a, and an outlet pressure sensor 80a may be connected between union 128 and inspiration flow outlet 130. Over-pressure pressure relief valve 160 may comprise any known pressure relief valve. Relief valve 160 may be configured to protect the patient from dangerous over-pressure situations. Other embodiments may not include relief valve 160, and may utilize an over-pressure safety system using pressure measurements from sensors 80a and/or 80b and gas delivery control system 31 to control turbine 20, e.g., as discussed above regarding over-pressure security system 32. Flow sensor 82a may monitor the flow delivered toward the patient, and outlet pressure sensor 80a may monitor the pressure at the outlet of ventilation system 12a, e.g., to provide safety back-up pressure measurement when proximal pressure line 100 is not connected.
[0193] An exhalation limb 90 of breathing circuit 16 may be connected to an exhalation flow inlet 132, which may be directed toward an exhalation flow outlet 134 leading out of ventilation system 12a. An exhalation flow sensor 82b may be located between exhalation flow inlet 132 and exhalation flow outlet 134 to measure the exhalation flow.
[0194] Ventilation system 12a may also include an exhalation valve control system for controlling exhalation valve 96. Such exhalation valve control system may include a pilot valve 102 and an exhalation valve pressure sensor 80c positioned along a flow line 138 from blower 20 (e.g., such line directly output from blower 20 or branching off of the main flow line directed toward inspiration flow outlet 130). The flow line 138 may lead to an exhalation valve interface 134 for connecting an exhalation valve control line 98 used for controlling exhalation valve 96.
[0195] Ventilation system 12a may also include a proximal pressure sensor 80b connected to a proximal pressure interface 136 configured for connecting a proximal pressure line 100, which may run along limb 90 or 92 of breathing circuit 16. Proximal pressure sensor 80b may monitor the gas pressure delivered toward the patient when proximal pressure line 100 is connected to ventilation system 12.
[0196] Any of the various sensors and/or valves of system 12a may communicate signals to gas delivery control system 31, which may process such signals and control the speed of turbine 20 accordingly. Gas delivery control system 31 may also communicate control signals to control the operation of any of the valves of system 12a.
[0197] FIG. 6 illustrates an example arrangement of various components of example ventilation system 12a, according to one embodiment of the present disclosure. Beginning at the air intake pathway, ventilation system 12a may include air inlet filter 140 leading to first silencer 150 of a turbine-based blower module. Intake air may then be compressed by turbine 20 and delivered through second silencer 152 and along the main flow line 190 toward the connection interface 130 for the inhalation limb of a breathing circuit 16.
[0198] A check valve 160 may be located along main flow line 190. Check valve 160 may comprise a mechanical (e.g., spring-based) or pneumatic relief valve configured to automatically open in the event of an overpressure situation. Some embodiment may not include check valve 160. Inhalation flow sensor 82a and inhalation pressure sensor 80a may also be located along main flow line 190, and configured to measure the flow rate and pressure in main flow line 190.
[0199] An O2 inlet 154 may be configured for connecting a supplemental oxygen source. An O2 safety valve 156 may be located along O2 flow line 192, and configured to slow or stop the flow of supplemental oxygen in certain situations, e.g., as discussed above regarding FIGS. 4A and 4B . O2 flow line 192 may lead to a mixing chamber or area such that the supplemental oxygen may mix with the output air from turbine 20 and continue toward patient 11 along main flow line 190 inhalation limb connection interface 130 as an air—O2 mixture.
[0200] An exhalation limb connection interface 132 provides an interface for connecting an exhalation limb of a breathing circuit 16, and leads to an exhalation flow line 194. An exhalation flow sensor 82b for measuring the exhalation flow rate is located along exhalation flow line 194 before the flow is directed out of and away from system 12.
[0201] An exhalation valve control line interface 134 provides an interface for connecting an exhalation valve control line for controlling an exhalation valve in a breathing circuit 16. Exhalation valve control line interface 134 is connected to the turbine-based blower module via a pressurized control line 196 such that pressurized gas can be applied to the exhalation valve in order to control the exhalation valve. A pilot valve 102 (e.g., a solenoid) may control the pressure within control line 196. Pilot valve 102 may be controlled by signals from CPU 22, which may be generated based on pressure measurements from a pressure sensor 80c located along control line 196.
[0202] A user interface module 40 may include a display (e.g., an LCD or other screen) and a keypad 42 including any number and/or type of keys, buttons, switches, or other manual interfaces. CPU 22 may include any one or more processor configured to communicated with and/or control any of the various components of system 12a. CPU 22 may include or may have access to any software, firmware, algorithms, or other logic or instructions for performing any of the various control functions discussed herein.
[0203] Various components may be physically located on a circuit board. In this example, CPU, sensors 80a, 80c, 80c, 82a, and 82b, and user interface module 40 are located on a circuit board 198.
[0204] CPU 22 may control a turbine control device 200 configured to control the operation of turbine 20. Turbine control device 200 may be configured to provide any suitable performance characteristics, as desired. For instance, in an example embodiment, turbine control device 200 is designed according to the following performance characteristics:
-
- [0205] The device drives from 0 to 45,000 rpm a 3-phase brushless motor with position or motor speed sensors;
- [0206] The device transfers signals from a motor position or motor speed sensor;
- [0207] The device transfers signals from a motor temperature sensor;
- [0208] The device allows the motor supply to be cut by an external control;
- [0209] The device allows breaking of the motor by an external source;
- [0210] The inrush current of the device is less than 3 A; and
- [0211] The power supply current is less than 3 A.
[0212] CPU 22 may control turbine control device 200 based on any suitable data, e.g., data from one or more sensors and/or data input by a user via user interface module 40.
[0213] One or more data ports 206 may provide a connection interface for communicating data to and/or from system 12 (e.g., CPU 22). Each data port 206 may comprise any suitable type of data port, e.g., a USB, Ethernet, FireWire, or RS-232 port.
[0214] A repeater interface 202 provides an interface for connecting a wireless notification module 44 for wirelessly communicating data (e.g., alarms and/or other data) to wireless receiving devices via one or more wireless repeaters. Such system is discussed below with reference to FIG. 7 .
[0215] An FiO2 socket 204 for connecting a FiO2 sensor (e.g., oxygen cell) for providing measurements of the oxygen concentration (or percent oxygen) of the gas delivered toward patient 11. Ventilation system 12 may use such measurements for monitoring the oxygen concentration in the patient air flow, e.g., for triggering Low and High FiO2 alarms based on Low and High FiO2 thresholds (which may be set by a user via GUI 40, automatically determined by system 12, or otherwise determined).
[0216] A power system 30 may include a battery 50, an AC/DC power supply and battery charger 124, and a power switchover 126, e.g., as discussed above with reference to FIG. 3 . An AC/DC source interface 210 and an on/off switch 212 may be connected to AC/DC power supply and battery charger 124.
Wireless Notification System
[0217] FIG. 7 illustrates an example wireless notification system 250 configured to communicate wireless notifications (e.g., alarms generated by control system 22) from ventilation system 12 to one or more receiving device, e.g., a remote monitor or a mobile alarm unit carried by a user (e.g., a caretaker). In some embodiments, wireless notification system 250 may include a wireless notification module 44 included in or coupled to ventilation system 12, one or more wireless repeaters 260, and one or more wireless receiving devices 256. In general, wireless notification module 44 may be configured to wirelessly transmit alarms or other data to wireless receiving devices 256, either directly or via one or more wireless repeaters 260.
[0218] Wireless notification module 44 may be included in or coupled to ventilation system 12. For example, module 44 may be integrated with ventilation system 12. Alternatively, module 44 may be a separate module that may be connected to an interface of ventilation system 12 via any suitable wireline or wireless interface, e.g., USB, Ethernet, or Bluetooth connection. In the example embodiment shown in FIG. 6 , module 44 may be configured to connection to ventilation system 12 via repeater interface 202. Wireless notification module 44 may include any hardware, software, firmware, etc. for communicating with components of ventilation system 12 (e.g., control system 22) and wirelessly communicating data 252 from such components of ventilation system 12 to one or more wireless receiving devices 256, either directly or via one or more wireless repeaters 260. In an example embodiment, wireless notification module 44 may include an RF modem configured to transmit and/or receive wireless signals.
[0219] Each wireless repeater 260 may comprise any type of known repeater for wirelessly relaying data 252 between two devices (e.g., between a computing device and a wireless access point). More particularly, each wireless repeaters 260 may relay data (a) between wireless notification module 44 and a receiving device 256, (b) between wireless notification module 44 and another wireless repeater 260, and (e) between two other wireless repeaters 260. In this manner, wireless repeaters 260 facilitate communication of data 252 between wireless notification module 44 and receiving devices 256.
[0220] Wireless notification system 250 may include any number of wireless repeater 260 positioned and at any suitable locations. For example, wireless repeaters 260 may be aligned in a row to provide wireless coverage for a distance in one direction, or may be arranged in an array to provide wireless coverage over a desired area. In some embodiments, wireless repeaters 260 may be located in multiple rooms throughout a building to provide wireless coverage throughout the building.
[0221] Wireless receiving devices 256 may include any one or more types of devices configured to (a) wirelessly receive data 252 from wireless notification module 44, either directly or via one or more wireless repeaters 260 and (b) communicate the received data 252 to a person (e.g., a caretaker) remote from ventilation system 12. A wireless receiving devices 256 may communicate data 252 to a person in any suitable manner, e.g., (a) visually displaying the data via a visible display device (e.g., a screen, monitor, LEDs, etc.), (b) generating various audible sounds or voice messages via a speaker or other suitable device, (c) vibrating, or (d) any combination of the above.
[0222] Wireless receiving devices 256 may include one or more monitor devices 270 and mobile alarm units 272. A monitor device 270 may comprise any device having a monitor or screen for visually displaying data 252. For example, monitor device 270 may comprise a monitor or screen of a computer, a television, or a stand-alone monitor device. Mobile alarm units 272 may include any mobile device that may be carried by a person, e.g., a hand-held device or a device that may be attached to the person's clothing. Mobile alarm units 272 may include devices having other functionality not related to wireless notification system 250 (e.g., a mobile phone, PDA, or portable computer) and/or devices specifically designed for wireless notification system 250. For certain device (e.g., mobile phone, PDA, or portable computers having other, unrelated functionality), software may be installed onto such devices in order to provide the relevant functionality (e.g., data communication, processing, and display functionality) of a wireless receiving devices 256 for use in wireless notification system 250.
[0223] Data 252 may include any type of data regarding the condition of patient 11 and/or the operation of breathing assistance system 10. In some embodiments, data 252 includes alarm data, e.g., notifications of alarms generated by any of the sub-systems of control system 22 (including, for example, any of the various alarms discussed herein). Some alarms may indicate any fault or malfunction regarding the operation of any one or more sub-system or component of breathing assistance system 10. Other alarms may indicate a dangerous or potentially dangerous physiological condition of patient 11.
[0224] In other embodiments, data 252 includes alarm data as well as other data regarding patient 11 and/or breathing assistance system 10, e.g., ventilator settings, sensor readings (e.g., pressure, flow, and temperature data), and/or physiological measurements regarding patient 11. In some embodiments, data 252 (e.g., ventilator settings, sensor readings, and/or physiological measurements) may be continuously or substantially continuously communicated to wireless receiving devices 256 such that the data may be continuously or substantially continuously displayed and updated by the wireless receiving devices 256.
[0225] Data 252 may also include data identifying the particular ventilation system 12 and/or the particular patient 11. In some configurations, data 252 may include “heartbeat” signals or other signals for indicating the presence and/or operational status of the communicating device.
[0226] As discussed above, in some embodiments or configurations, wireless notification module 44 may communicate data 252 to wireless receiving devices 256 continuously or substantially continuously. Such communications may include alarms and/or other data.
[0227] In other embodiments or configurations, wireless notification system 250 is essentially a remote alarm system, designed mainly for communicating alarms. In some such embodiments, wireless notification module 44 may maintain continuous (or frequent) communications with wireless receiving devices 256, e.g., my “heartbeat” signals or other signals indicating the presence and/or operational status (e.g., “powered on”) of each wireless receiving device 256. When an alarm condition occurs in system 10, wireless notification module 44 may interrupt the continuous (or frequent) communications with wireless receiving devices 256; in response to the interrupt in communications, each wireless receiving device 256 may generate an alarm. Each wireless receiving device 256 may also generate an alarm if it moves outside the range for receiving communications from wireless notification module 44 (e.g., if device 256 cannot communicate with wireless notification module 44 or any wireless repeater 260).
[0228] Alternatively, when an alarm condition occurs in breathing assistance system 10, wireless notification module 44 may transmit an alarm signal (as data 252) to wireless receiving devices 256 (again, either directly or via one or more repeaters 260), and in response, each wireless receiving device 256 may generate an alarm (e.g., an audible or visible alarm). In some embodiments, wireless receiving device 256 may generate a first type of alarm when it receives an alarm signal transmitted by wireless notification module 44, and a second first type of alarm when communications with wireless notification module 44 are interrupted (e.g., due to moving outside the range of communication with wireless notification module 44 or any wireless repeater 260, or due to a fault associated with any component of wireless notification module 44.
[0229] Components of wireless notification system 250 (e.g., wireless notification module 44, wireless repeaters 260, and wireless receiving devices 256) may be powered in any suitable manner, e.g., by battery or from an electrical power grid (e.g., via an A/C wall outlet). For example, in some embodiments, wireless notification module 44 may be powered by power system 30 of ventilation system 12, wireless repeaters 260 may plugged into a wall outlet or powered by battery, and wireless receiving devices 256 may be powered by rechargeable battery. In some embodiments, components of wireless notification system 250 operating on battery power may generate a low battery alarm when appropriate. Such alarm may notify the user to replace or recharge the battery.
[0230] In some embodiments, wireless notification system 250 may utilize power management techniques for reducing power used by various system components (e.g., wireless notification module 44, wireless repeaters 260, and wireless receiving devices 256). For example, various system components may enter a low power mode (e.g., a sleep, standby, or low power mode) when not communicating data, in order to conserve power. System components may be awakened or enter a full power or powered up mode as appropriate in order to transmit and/or receive data. For example, one system component (e.g., wireless notification module 44) may communicate a “wakeup” signal to wireless repeaters 260 and/or wireless receiving devices 256 in order to awaken such components for receiving and/or transmitting data. Such “wakeup” signals may be communicated periodically or at any other time for communicating data 252. Alternatively, various system components may be synchronized and awaken themselves in a synchronized manner in order to communicate data 252. In such embodiments, each system component may maintain a clock, and synchronization signals may be communicated among the system components periodically in order to keep the component clocks synchronized.
[0231] Any of the components of wireless notification system 250 (e.g., wireless notification module 44, wireless repeaters 260, and wireless receiving devices 256) may include any hardware, software, and/or firmware for transmitting and/or receiving wireless communications of data (e.g., data 252). For example, components of wireless notification system 250 may include any suitable wireless transmitters, wireless receivers, and/or wireless transceivers. In some embodiments, each of wireless notification module 44, wireless repeaters 260, and wireless receiving devices 256 include both transmitters and receivers (or transceivers) such that data may be communication in both directions between wireless notification module 44 and wireless receiving devices 256.
[0232] The wireless communications between the various components of wireless notification system 250 may use any known protocol or standard. Examples of wireless communication protocols that may be used include, but are not limited to, personal area networks (PAN) (e.g., BLUETOOTH), local area networks (LAN), wide area networks (WAN), narrowband personal communications services (PCS), broadband PCS, circuit switched cellular, cellular digital packet data (CDPD), radio frequencies, such as the 800 MHz, 900 MHz, 1.9 GHz and 2.4 GHz bands, infra-red and laser.
[0233] In some embodiments, wireless notification system 250 may fixed-frequency communications. In other embodiments, wireless notification system 250 may spread-spectrum communications, e.g., by means of frequency-hopping, direct sequence, or any other known techniques.
[0234] In some embodiments, wireless receiving devices 256 may communicate data to wireless notification module 44. For example, each wireless receiving device 256 may communicate identification data and/or location data to wireless notification module 44 at any suitable time, for example, substantially continuously, periodically, or in response to some triggering event (e.g., wireless receiving device 256 being turned on or preparing to communicate a control signal to wireless notification module 44, for example, to remotely change a ventilation setting).
[0235] In some embodiments, wireless notification system 250 may include an identification or security system to ensure that only authorized devices are communicating in system 250. Some or all system components may store identification data that may be communicated to other system components for authentication of system components. For example, in order to enter a communication session with wireless notification module 44, the wireless receiving device 256 may communicate identification data to module 44 at any suitable time, for example, periodically, upon powering up device 256, module 44, or ventilation system 12, or in response to a request by module 44. Thus, wireless notification module 44 may manage the authentication process. In other embodiments, wireless repeaters 260 may be configured to manage the authentication process.
Example Methods of Operation
[0236] FIG. 8 illustrates an example method 300 of using multiple pressure sensors for managing control of a ventilation system 12, according to certain embodiments of the present disclosure. The example method 300 uses two pressure sensors for managing control of ventilation system 12. In particular, in the discussion below, the two pressure sensors are outlet pressure sensor 80a and proximal pressure sensor 80b. However, method 300 may similarly apply to other pairs of pressure sensors provided in breathing assistance system 10, depending on the specific embodiment. Such pair of pressure sensors may be positioned at any location in breathing assistance system 10, and may be configured to measure pressure at any different locations within breathing assistance system 10, e.g., any locations along a conduit of ventilation system 12 and/or connection system 14. In addition, although example method 300 uses two pressure sensors for managing control of ventilation system 12, similar techniques may be used for managing control of ventilation system 12 using more than two (e.g., 3 or more) pressure sensors.
[0237] At step 302, a proximal pressure detection process is initiated. Such process may be initiated automatically upon a triggering event (e.g., turning on ventilation system 12, user or automatic selection of a particular ventilation mode or setting, or execution of a start-up test) or based on a user-initiated request. In general, as discussed below, the proximal pressure detection process determines whether a proximal pressure line 100 is connected to ventilation system 12 such that proximal pressure sensor 80b may effectively measure the proximal pressure (e.g., pressure in connection system 14 near patient 11) for use in controlling the operation of ventilation system 12 (e.g., whether proximal pressure sensor 80b may be used by gas delivery control system 31 may control the pressure and/or flow of gas delivered toward patient 11).
[0238] At step 304, proximal pressure sensor 80b may take and communicate one or more pressure measurements to proximal pressure detection system 36. Proximal pressure sensor 80b may communicate a single pressure measurement or multiple pressure measurements over any suitable time period.
[0239] At step 306, outlet pressure sensor 80a may take and communicate one or more pressure measurements to proximal pressure detection system 36. Outlet pressure sensor 80a may communicate a single pressure measurement or multiple pressure measurements over any suitable time period. Steps 304 and 306 may be performed in any order and/or substantially simultaneously.
[0240] At step 308, proximal pressure detection system 36 may determine whether a proximal pressure line 100 is connected to ventilation system 12 such that proximal pressure sensor 80b may effectively measure the proximal pressure (e.g., the pressure in connection system 14 near patient 11). Proximal pressure detection system 36 may determine whether a proximal pressure line 100 is connected based at least on (a) pressure measurements from proximal pressure sensor 80b at step 304, (b) pressure measurements from outlet pressure sensor 80a at step 306, or (c) both.
[0241] For example, proximal pressure detection system 36 may compare measurement(s) from proximal pressure sensor 80b with measurement(s) from outlet pressure sensor 80a, and determine that a proximal pressure line 100 is connected if the proximal pressure sensor 80b measurement(s) is/are greater than the outlet pressure sensor 80a measurement(s), and that a proximal pressure line 100 is not connected if the proximal pressure sensor 80b measurement(s) is/are less than or equal to than the outlet pressure sensor 80a measurement(s).
[0242] As another example, proximal pressure detection system 36 may determine that a proximal pressure line 100 is connected if the proximal pressure sensor 80b measurement(s) is/are greater than the outlet pressure sensor 80a measurement(s), but by an amount within a threshold pressure difference (e.g., determined based on empirical data). In such embodiments, such threshold pressure difference may be selected from a set or range of predetermined threshold pressure difference based on the particular flow rate at which the outlet pressure sensor 80a measurement(s) were taken. Such set or range of predetermined threshold pressure difference may be used to account for the fact that, in certain configurations, the expected difference in pressure measurements between outlet pressure sensor 80a and proximal pressure sensor 80b (e.g., due to pressure drop within connection system 14) depends on the flow rate through connection system 14. Thus, the higher the flow rate through connection system 14 during the pressure measurements at steps 304 and/or 306, the higher the expected difference between proximal pressure sensor 80b measurement(s) and outlet pressure sensor 80a measurement(s), and thus the higher the threshold pressure difference that should be used.
[0243] Note that these two examples assume positive direction flow (i.e., toward patient 11); for negative direction flow (i.e., away from patient 11), the analysis would be reversed.
[0244] As another example, proximal pressure detection system 36 may compare the proximal pressure sensor 80b measurement(s) to a threshold pressure value (e.g., determined based on empirical data), and determine that a proximal pressure line 100 is connected if the proximal pressure sensor 80b measurement(s) is/are greater than the threshold pressure value, and that a proximal pressure line 100 is not connected if the proximal pressure sensor 80b measurement(s) is/are less than or equal to the threshold pressure value.
[0245] As another example, proximal pressure detection system 36 may compare the proximal pressure sensor 80b measurement(s) to a predetermined expected pressure value (e.g., determined based on empirical data), and determine that a proximal pressure line 100 is connected if the proximal pressure sensor 80b measurement(s) do not differ from the predetermined expected pressure value by more than a predetermined threshold value.
[0246] In other embodiments, proximal pressure detection system 36 may analyze (a) proximal pressure sensor 80b measurement(s), (b) outlet pressure sensor 80a measurement(s), or (c) both, in any other manner to determine whether a proximal pressure line 100 is connected to ventilation system 12.
[0247] If proximal pressure detection system 36 determines at step 308 that a proximal pressure line 100 is connected to ventilation system 12, the method may advance to step 310. At step 310, system 36 may generate and/or display to the user a notification that a proximal pressure line 100 is connected and/or that proximal pressure sensor 80b measurement(s) will or may be used for controlling aspects of ventilation system 12.
[0248] At step 312, control system 31 may allow or disallow particular ventilation modes or settings based on the determination that a proximal pressure line 100 is connected to ventilation system 12 (and that proximal pressure sensor 80b measurement(s) may be used for controlling ventilation system 12). For example, control system 31 may allow user or automatic selection of, and/or automatic switching to, certain ventilation modes or settings that require accurate patient pressure readings that may be provided by proximal pressure sensor 80b but not by outlet pressure sensor 80a. As discussed below at step 322, one or more of such ventilation modes or settings may be disallowed if it is determined that a proximal pressure line 100 is not connected to ventilation system 12.
[0249] At step 314, ventilation system 12 may provide breathing assistance to patient 11 according to ventilation settings (e.g., a ventilation mode and/or parameter settings) selected manually by a user and/or automatically by control system 31. One or more of such ventilation settings may be determined by the determination at step 312.
[0250] At step 316, control system 22 may control operational aspects of ventilation system 12 based at least on proximal pressure measurements from proximal pressure sensor 80b. For example, gas delivery control system 31 may control the pressure and/or flow rate of gas delivered toward patient 11 based on proximal pressure measurements from sensor 80b. As another example, if an exhalation valve 96 is connected to system 12, control system 22 may control exhalation valve 96 (e.g., by controlling pilot valve 102) based on proximal pressure measurements from sensor 80b.
[0251] Alternatively, if proximal pressure detection system 36 determines at step 308 that a proximal pressure line 100 is not connected to ventilation system 12, the method may advance to step 318. At step 318, system 36 may generate and/or display to the user a notification or alarm that a proximal pressure line 100 is not connected and/or that proximal pressure sensor 80b measurement(s) will not be used (or that for outlet pressure sensor 80a measurement(s) will be used) for controlling aspects of ventilation system 12.
[0252] At step 320, proximal pressure detection system 36 may allow the user to respond to the alarm displayed at step 318 before beginning or continuing breathing assistance to patient 11. For example, system 36 may display a user-selectable option to connect a proximal pressure line 100 or to continue without a proximal pressure line 100. If the user connects a proximal pressure line 100, the method may advance to step 312. If the user selects to continue without a proximal pressure line 100, the method may advance to step 322. In some embodiments, step 320 may be excluded, wherein the method may automatically advance from step 318 to step 322.
[0253] At step 322, control system 31 may allow or disallow particular ventilation modes or settings based on the determination that a proximal pressure line 100 is not connected to ventilation system 12 (and that proximal pressure sensor 80b measurement(s) may not be used for controlling ventilation system 12). For example, control system 31 may disallow user or automatic selection oft and/or automatic switching to, certain ventilation modes or settings that require accurate patient pressure readings that may be provided by proximal pressure sensor 80b but not by outlet pressure sensor 80a.
[0254] At step 324, ventilation system 12 may provide breathing assistance to patient 11 according to ventilation settings (e.g., a ventilation mode and/or parameter settings) selected manually by a user and/or automatically by control system 31. One or more of such ventilation settings may be determined by the determination at step 322.
[0255] At step 326, control system 22 may control operational aspects of ventilation system 12 based at least on outlet pressure measurements from outlet pressure sensor 80a. For example, gas delivery control system 31 may control the pressure and/or flow rate of gas delivered toward patient 11 based on outlet pressure measurements from sensor 80a. As another example, if an exhalation valve 96 is connected to system 12, control system 22 may control exhalation valve 96 (e.g., by controlling pilot valve 102) based on outlet pressure measurements from sensor 80a. In some embodiments, outlet pressure measurements from sensor 80a may be “corrected” (e.g., to compensate for pressure drop within connection system 14) using any suitable technique, e.g., any of the techniques disclosed in pending EP Patent Application EP 08006240.9, filed on Mar. 31, 2008, and entitled “Systems and Methods for Compensating for Pressure Drop in a Breathing Assistance System.”
[0256] While providing breathing assistance to patient 11, proximal pressure detection system 36 may continue to determine whether a proximal pressure line 100 is connected to system 12 periodically, continuously, in response to a detected event or user request, or at any other time. In this manner, control system 22 may adjust to a connection or disconnection of a proximal pressure line 100 while system 12 is providing breathing assistance to patient 11. Such detection may include, for example, the techniques discussed above at steps 304-308.
[0257] As shown at step 328, if ventilation system 12 is providing breathing assistance using proximal pressure sensor 80b measurements for controlling various operational aspects, and system 36 detects disconnection of proximal pressure line 100, the method may advance to steps 318-326 to switch from proximal pressure sensor 80b measurement to outlet pressure sensor 80a measurements. Thus, for example, system 36 may generate a user alarm indicating disconnection of proximal pressure line 100 (at step 318), allow the user to re-connect proximal pressure line 100 or continue without proximal pressure line 100 (at step 320), allow or disallow particular ventilation modes or settings based on the determination that proximal pressure line 100 is not connected (at step 322), provide breathing assistance according to the now relevant ventilation settings (at step 324), and control operational aspects of ventilation system 12 based on outlet pressure sensor 80a measurements (at step 326).
[0258] Similarly, as shown at step 330, if ventilation system 12 is providing breathing assistance using outlet pressure sensor 80a measurements for controlling various operational aspects, and system 36 detects connection (or reconnection) of a proximal pressure line 100, the method may advance to steps 310-316 to switch from outlet pressure sensor 80a measurements to proximal pressure sensor 80b measurements. Thus, for example, system 36 may generate a user notification indicating connection of proximal pressure line 100 (at step 310), allow or disallow particular ventilation modes or settings based on the determination that proximal pressure line 100 is connected (at step 312), provide breathing assistance according to the now relevant ventilation settings (at step 314), and control operational aspects of ventilation system 12 based on proximal pressure sensor 80a measurements (at step 316).
[0259] FIG. 9 illustrates an example method 350 for detecting and managing an over-pressure condition in a breathing assistance system 10, according to certain embodiments of the present disclosure. For example, method 350 may be used for detecting an over-pressure condition in connection system 14 (e.g., in breathing circuit 16) based on pressure signals received from one or more pressure sensors 24 and managing a detected over-pressure condition.
[0260] The example method 350 uses two pressure sensors, either separately or in combination, for detecting an over-pressure condition in breathing assistance system 10. In particular, in the discussion below, the two pressure sensors are outlet pressure sensor 80a and proximal pressure sensor 80b. However, method 350 may similarly apply to other pairs of pressure sensors provided in breathing assistance system 10, depending on the specific embodiment. Such pair of pressure sensors may be positioned at any location in breathing assistance system 10, and may be configured to measure pressure at any different locations within breathing assistance system 10, e.g., any locations along a conduit of ventilation system 12 and/or connection system 14. In addition, although example method 350 uses two pressure sensors for detecting an over-pressure condition in breathing assistance system 10, similar techniques may be used for detecting an over-pressure condition using more than two (e.g., 3 or more) pressure sensors, either separately or in combination.
[0261] At step 352, ventilation system 12 may provide breathing assistance to patient 11, e.g., according to ventilation settings (e.g., a ventilation mode and/or parameter settings) selected manually by a user and/or automatically by control system 31.
[0262] At step 354, proximal pressure sensor 80b may take and communicate one or more pressure measurements to proximal pressure detection system 36. Proximal pressure sensor 80b may communicate a single pressure measurement or multiple pressure measurements over any suitable time period. In some embodiments or configurations, proximal pressure sensor 80b may be configured to measure a proximal pressure near patient 11 via a proximal pressure line 100 connected at one end to ventilation system 12 and extending along a limb of breathing circuit 16.
[0263] At step 356, outlet pressure sensor 80a may take and communicate one or more pressure measurements to proximal pressure detection system 36. Outlet pressure sensor 80a may communicate a single pressure measurement or multiple pressure measurements over any suitable time period. In some embodiments or configurations, outlet pressure sensor 80a may be located at or near a main gas outlet of ventilation system 12 (e.g., at or near an outlet of gas delivery system 20) to measure the pressure of gas flow exiting ventilation system 12 or gas delivery system 20, or the pressure of gas flow entering connection system 14. The two sensors 80a and 80b may detect different pressure levels, e.g., due to pressure drop inherent in breathing circuit 16.
[0264] Steps 354 and 356 may be performed in any order and/or substantially simultaneously.
[0265] At step 358, over-pressure security system 32 may determine whether an over-pressure condition is present in system 10 (e.g., in connection system 14). For example, over-pressure security system 32 may compare pressure measurements received from sensors 80a and 80b to one or more threshold pressure values to automatically detect an over-pressure condition. Pressure measurements from both sensors 80a and 80b may each be compared to a single pressure threshold value, or each sensor's measurements may be compared to a separate corresponding pressure threshold value. Such pressure threshold value(s) may be determined in any suitable manner, and may be manually or automatically adjusted over time.
[0266] In some embodiments, over-pressure security system 32 may compare pressure measurements received from sensors 80a and 80b to different pressure threshold values to account for differences between expected pressure measurements from sensors 80a and 80b, e.g., due to pressure drop in connection system 14. The pressure threshold values for comparing pressures from each of sensors 80a and 80b may be determined in any suitable manner (e.g., stored values based on empirical data).
[0267] In some embodiments, one or both of threshold pressure values may be selected (e.g., using an algorithm or look-up table) based on the particular flow rate at which such measurements by sensors 80a and/or 80b were taken. Thus, one or both of threshold pressure values may be selected from a range of values to account for the fact that, in certain configurations, the expected difference in pressure measurements from sensor 80a and sensor 80b (e.g., due to pressure drop within connection system 14) depends on the flow rate through connection system 14.
[0268] In some embodiments, over-pressure security system 32 may determine that an over-pressure condition is present if either (a) the pressure measured by proximal pressure sensor 80a exceeds its corresponding threshold value or (b) the pressure measured by proximal pressure sensor 80a exceeds its corresponding threshold value (which may be the same as, or different from, the corresponding threshold value for proximal pressure sensor 80a measurements, as discussed above). In such embodiments, using both sensors 80a and 80b may provide a level of redundancy for protecting against over-pressure situations.
[0269] In other embodiments, over-pressure security system 32 may determine that an over-pressure condition is present only if both (a) the pressure measured by proximal pressure sensor 80a exceeds its corresponding threshold value and (b) the pressure measured by proximal pressure sensor 80a exceeds its corresponding threshold value (which may be the same as, or different from, the corresponding threshold value for proximal pressure sensor 80a measurements, as discussed above).
[0270] If over-pressure security system 32 does not determine an over-pressure condition at step 358, the method may return to steps 352-358 to continue providing breathing assistance, take pressure measurements, and determine whether an over-pressure condition arises. Steps 354-358 may be repeated at any time interval, e.g., substantially continuously, periodically, or in response to some triggering event.
[0271] Alternatively, if over-pressure security system 32 determines an over-pressure condition at step 358, system 32 may manage the over-pressure condition at step 360. For example, over-pressure security system 32 may notify gas delivery control system 31 such that system 31 controls gas delivery system 20 to end the over-pressure condition, e.g., by (a) reducing the pressure or flow rate produced by gas delivery system 20 (e.g., to a pressure at or just below a threshold pressure value, or to a lower pressure) or (b) shutting down gas delivery system 20. For example, in embodiments in which gas delivery system 20 includes a blower (e.g., a turbine-based blower), gas delivery control system 31 may reduce the speed of the blower.
[0272] At step 362, over-pressure security system 32 may generate an over-pressure alarm. The alarm may comprise any notification that may be sensed by a user, e.g., an audible alarm or a visible alarm displayed to the user, e.g., via display 28 or separate device (e.g., an LED).
[0273] In some configurations, monitoring signals from both sensors 80a and 80b as discussed above may provide redundancy to account for situations in which 80a or 80b is not providing useful data, e.g., where one of sensors 80a and 80b is damaged or not working properly, or where a proximal pressure line 100 is not used or is blocked.
[0274] FIG. 10 illustrates an example method 400 for determining whether an exhalation valve 96 is connected to ventilation system 12, and controlling ventilation system 12 accordingly, according to certain embodiments of the present disclosure.
[0275] At step 402, an exhalation valve detection process is initiated. Such process may be initiated automatically upon a triggering event (e.g., turning on ventilation system 12, user or automatic selection of a particular ventilation mode or setting, or execution of a start-up test) or based on a user-initiated request. In general, as discussed below, the exhalation valve detection process determines whether an exhalation valve 96 is connected to ventilation system 12 (e.g., via an exhalation valve control line 98) such that ventilation system 12 may control exhalation valve 96 while providing breathing assistance to patient 11.
[0276] At step 404, exhalation valve sensor 80c may take and communicate one or more pressure measurements to exhalation valve detection system 34. Exhalation valve sensor 80c may communicate a single pressure measurement or multiple pressure measurements over any suitable time period.
[0277] At step 406, exhalation valve detection system 34 may determine whether an exhalation valve 96 is connected to ventilation system 12 (e.g., via an exhalation valve control line 98) based at least on pressure measurements from exhalation valve sensor 80c. For example, exhalation valve detection system 34 may compare measurement(s) from exhalation valve sensor 80c to a threshold pressure value to automatically determine whether an exhalation valve 96 is connected. Generally, if no exhalation valve 96 is connected, the connection port for exhalation valve control line 98 may remain open, and thus the pressure measured by exhalation valve sensor 80c may remain low (e.g., below the threshold pressure value). However, if an exhalation valve 96 is connected via an exhalation valve control line 98 connected to ventilation system 12, the pressure measured by exhalation valve sensor 80c may increase (e.g., above the threshold pressure value). The threshold pressure value may be determined in any suitable manner (e.g., stored value(s) based on empirical data), and may be manually or automatically adjusted over time.
[0278] If exhalation valve detection system 34 determines that an exhalation valve 96 is connected to ventilation system 12, the method may proceed to step 408. Otherwise, the method may proceed to step 418.
[0279] At step 408, exhalation valve detection system 34 may generate and display a user notification that an exhalation valve 96 is connected and/or being used for controlling breathing assistance.
[0280] At step 410, gas delivery control system 31 may automatically select between different ventilation modes or settings or otherwise control one or more ventilation parameters (e.g., flow and/or pressure) based on the determination that an exhalation valve 96 is connected to ventilation system 12. For example, in some embodiments in which ventilation system 12 can provide either leakage ventilation or exhalation valve ventilation, gas delivery control system 31 may automatically select or switch to exhalation valve ventilation based on the determination that an exhalation valve 96 is connected to ventilation system 12.
[0281] In addition, gas delivery control system 31 may allow or disallow particular ventilation modes or settings based on the determination that an exhalation valve 96 is connected to ventilation system 12. For example, control system 31 may allow user or automatic selection of, and/or automatic switching to, certain ventilation modes or settings that require control of an exhalation valve 96.
[0282] At step 412, in example configurations in which ventilation system 12 selects or switches to exhalation valve ventilation (at step 410), gas delivery control system 31 may determine whether any selected ventilation settings are incompatible with exhalation valve ventilation. If so, gas delivery control system 31 may trigger an alarm at step 414 and wait for the user to adjust the selected settings to become compatible before beginning ventilation of patient 11. The alarm may comprise any notification that may be sensed by a user, e.g., an audible alarm or a visible alarm displayed to the user, e.g., via display 28 or separate device (e.g., an LED). If not, the method may continue to step 416.
[0283] At step 416, ventilation system 12 may provide breathing assistance to patient 11 according to a ventilation mode and/or settings (e.g., exhalation valve ventilation) determined at steps 410-414.
[0284] Returning to the decision at step 406, if exhalation valve detection system 34 determines that an exhalation valve 96 is not connected to ventilation system 12, the method may proceed to step 418.
[0285] At step 418, exhalation valve detection system 34 may generate and display a user notification or alarm that an exhalation valve 96 is not connected and may not be used for controlling breathing assistance. System 34 may provide the user an opportunity to connect an exhalation valve 96, or to select to continue without an exhalation valve 96, or alternatively the method may automatically continue to step 420.
[0286] At step 420, gas delivery control system 31 may automatically select between different ventilation modes or settings or otherwise control one or more ventilation parameters (e.g., flow and/or pressure) based on the determination that an exhalation valve 96 is not connected to ventilation system 12. For example, in some embodiments in which ventilation system 12 can provide either leakage ventilation or exhalation valve ventilation, gas delivery control system 31 may automatically select or switch to leakage ventilation based on the determination that an exhalation valve 96 is not connected to ventilation system 12.
[0287] In addition, gas delivery control system 31 may allow or disallow particular ventilation modes or settings based on the determination that an exhalation valve 96 is not connected to ventilation system 12. For example, control system 31 may disallow user or automatic selection of, and/or automatic switching to, certain ventilation modes or settings that require control of an exhalation valve 96.
[0288] At step 422, in example configurations in which ventilation system 12 selects or switches to leakage ventilation (at step 410), gas delivery control system 31 may determine whether any selected ventilation settings are incompatible with leakage ventilation. If so, gas delivery control system 31 may trigger an alarm at step 424 and wait for the user to adjust the selected settings to become compatible before beginning ventilation of patient 11. The alarm may comprise any notification that may be sensed by a user, e.g., an audible alarm or a visible alarm displayed to the user, e.g., via display 28 or separate device (e.g., an LED). If not the method may continue to step 426.
[0289] At step 426, ventilation system 12 may provide breathing assistance to patient 11 according to a ventilation mode and/or settings (e.g., leakage ventilation) determined at steps 420-424.
[0290] While providing breathing assistance to patient 11, exhalation valve detection system 34 may continue to determine whether an exhalation valve 96 is connected to system 12 periodically, continuously, in response to a detected event or user request, or at any other time. In this manner, control system 22 may adjust to a connection or disconnection of an exhalation valve 96 while system 12 is providing breathing assistance to patient 11. Such detection may include, for example, the techniques discussed above at steps 402-406.
[0291] As shown at step 428, if exhalation valve detection system 34 detects a disconnection of exhalation valve 96 while ventilation system 12 is providing breathing assistance, the method may advance to steps 418-416 to account for the disconnection. This may include, e.g., generating a user alarm and automatically adjusting one or more ventilation settings (e.g., switching from exhalation valve ventilation to leakage ventilation).
[0292] Similarly, as shown at step 430, if exhalation valve detection system 34 detects a connection/re-connection of exhalation valve 96 while ventilation system 12 is providing breathing assistance, the method may advance to steps 408-416 to account for the connection/re-connection. This may include, e.g., generating a user notification and automatically adjusting one or more ventilation settings (e.g., switching from leakage ventilation to exhalation valve ventilation).
[0293] FIG. 11 illustrates an example method 500 for managing a supplemental gas supply (e.g., supplemental oxygen supply) in a breathing assistance system 10 configured to provide breathing assistance to a patient 11, according to certain embodiments of the present disclosure. In particular, method 500 may provide security for a supplemental gas supply when a gas delivery system 20 of breathing assistance system 10 is overheating or not operating properly (e.g., not running). For example, O2 safety system 38 may stop or slow the flow of the supplemental gas (e.g., by closing a safety valve) in such situations. Although the discussion focuses on a supplemental oxygen supply, the same techniques may be used for any other type of supplemental gas supply.
[0294] At step 502, O2 safety system 38 may determine whether gas delivery system 20 is operating properly (e.g., not running or running improperly). For example, O2 safety system 38 may communicate with gas delivery control system 31 to obtain data regarding the operation of gas delivery system 20. If O2 safety system 38 determines that gas delivery system 20 is not operating properly, the method may proceed to step 506. Otherwise, if O2 safety system 38 determines that gas delivery system 20 is operating properly, the method may proceed to step 504.
[0295] At step 504, O2 safety system 38 (e.g., an overheat detection module 158 of system 38) may determine whether gas delivery system 20 is overheating by monitoring readings from a temperature sensor 83 configured to measure the temperature of gas delivery system 20 or a component thereof. For example, overheat detection module 158 may compare readings from temperature sensor 83 with threshold temperature(s) to determine whether gas delivery system 20 is overheating. If O2 safety system 38 determines that gas delivery system 20 is overheating, the method may proceed to step 506. Otherwise, if O2 safety system 38 determines that gas delivery system 20 is not overheating, the method may return to step 502.
[0296] Steps 502 and 504 may be performed in any order and/or substantially simultaneously. Steps 502 and 504 may be performed at any time, e.g., substantially continuously, periodically, or in response to a triggering event.
[0297] At step 506, in response to determining that gas delivery system 20 is not operating properly (at step 502) or that gas delivery system 20 is overheating (at step 504), overheat detection module 158 may send an overheat notification signal to gas delivery control system 31. Based on such signal, gas delivery control system 31 may control O2 safety valve and/or gas delivery system 20 accordingly. For example, gas delivery control system 31 may partially or fully close O2 safety valve to slow or stop the flow of supplemental oxygen.
[0298] FIG. 12 illustrates an example method 550 for determining an overheat condition in a breathing assistance system 10 and managing a supplemental gas flow (e.g., supplemental oxygen flow) accordingly, according to certain embodiments of the present disclosure. In general, method 550 is an example embodiment of steps 504 and 506 of method 500 shown in FIG. 11 . More particularly, method 550 may monitor for an overheat condition in a gas delivery system 20, and in response to detecting an overheat condition, stop or slow the flow of the supplemental gas (e.g., by closing a safety valve). Again, although the discussion focuses on a supplemental oxygen supply, the same techniques may be used for any other type of supplemental gas supply.
[0299] At step 552, overheat detection module 158 may monitor temperature readings from temperature sensor 83 configured to measure the temperature of gas delivery system 20 or a component thereof Temperature sensor 83 may take and communicate measurement signals to overheat detection module 158 at any time, e.g., substantially continuously, periodically, or in response to a triggering event.
[0300] At step 552, overheat detection module 158 may compare temperature readings from temperature sensor 83 with a threshold temperature to determine whether gas delivery system 20 is overheating. Such threshold temperature may be constant or may change over time. For example, a threshold temperature may be determined using an algorithm or look-up table relating the threshold value to one or more other parameters, e.g., the current pressure or flow rate of gas delivered by delivery system 20, or the current speed of a turbine (in embodiments in which gas delivery system 20 comprises a turbine-based blower). Thus, for example, an algorithm may be used to increase the threshold temperature in proportion to the flow rate or turbine speed, as higher temperatures are expected with higher flow rates or turbine speeds.
[0301] As another example, the threshold temperature may be selected based on the current ventilation mode or settings. For example, different threshold temperatures may be used for SIMV ventilation, Assist/Control ventilation, and CPAP ventilation. As another example, different threshold temperatures may be used for adult vs. pediatric ventilation, as higher temperatures are expected with adult ventilation (e.g., due to higher flow rates or turbine speeds).
[0302] At step 556, overheat detection module 158 may determine whether gas delivery system 20 is overheating based on any number of temperature readings and comparisons performed at steps 552 and 554. For example) overheat detection module 158 may determine an overheat condition in response to a single sensor reading above the relevant threshold temperature. As another example, overheat detection module 158 may determine an overheat condition based on a predetermined number (e.g., 5) of consecutive sensor readings above the relevant threshold temperature, based on sensor readings remaining above the relevant threshold temperature for a predetermined duration (e.g., 10 seconds). As another example, overheat detection module 158 may determine an overheat condition based on an average of sensor readings for a predetermined number of readings or over a predetermined duration.
[0303] If overheat detection module 158 detects an overheat condition at step 556, the method may proceed to step 558. At step 558, control system 22 may control (e.g., reduce or stop) the supplemental gas flow and generate an alarm, in response to detecting an overheat condition at step 556. For example, overheat detection module 158 may send an overheat notification signal to gas delivery control system 31, which may in turn control O2 safety valve 156 and/or gas delivery system 20 accordingly. For example, gas delivery control system 31 may partially or fully close O2 safety valve 156 to slow or stop the flow of supplemental oxygen.
[0304] Overheat detection module 158 and/or gas delivery control system 31 may generate any suitable alarm(s) 159 regarding the overheat condition and/or the closing of O2 safety valve 156. An alarm 159 may comprise any notification that may be sensed by a user, e.g., audible alarm or a visible alarm displayed to the user.
[0305] If overheat detection module 158 does not detect an overheat condition at step 556, the method may proceed to step 560. At step 560, overheat detection module 158 may determine to adjust the temperature threshold used at step 554. For example, the threshold temperature may be adjusted (e.g., using an algorithm or look-up table) at step 562 according to one or more current ventilation parameters (e.g., the current pressure or flow rate of gas delivered by delivery system 20, or the current speed of a turbine). Thus, for example, overheat detection module 158 automatically increase the temperature threshold (according to an algorithm or look-up table) in response to an increase in the current flow rate or turbine speed, as higher temperatures are expected with higher flow rates or turbine speeds.
[0306] As another example, overheat detection module 158 may automatically adjust the temperature threshold based on a change in the current ventilation mode or settings. For example, module 158 may adjust the temperature threshold in response to a switch from Assist/Control ventilation to CPAP ventilation.
[0307] FIGS. 13A and 13B illustrate example methods 600 and 700 for determining a danger condition in a breathing assistance system and managing a supplemental gas flow (e.g., supplemental oxygen flow) using an O2 safety system as shown in FIG. 4B , according to certain embodiments of the present disclosure.
[0308] Referring to FIG. 13A , method 600 may be performed at any time during the operation of ventilation system 12. At step 602, a temperature of gas delivery system 20 (e.g., a blower motor) may be measured, e.g., using temperature sensor 83. At step 604, an operational speed of a component (e.g., a motor, blower, turbine) of gas delivery system 20 may be measured, e.g., using a speed sensor 84. At step 606, the power drawn by a component (e.g., a motor, blower, turbine) of gas delivery system 20 may be measured, e.g., using a power monitor 85. Steps 602-606 may be performed in any order, and each step may be performed at any suitable time and frequency. In addition, in some embodiments, at least one of steps 602-606 may be excluded, e.g., in embodiments in which O2 safety system is controlled using temperature and speed measurements, but not power measurements.
[0309] At step 608, a danger factor may be calculated based on the data obtained at steps 602-606. For example, safety status module 161 may calculate a safety factor using one or more algorithms relating the different types of measurements obtained at steps 602-606.
[0310] At step 610, safety status module 161 may compare the calculated safety factor to a danger condition threshold value to determine whether a danger condition is present. If it is determined that a danger condition is present (see step 612), control system 22 may slow or stop the supplemental oxygen flow (e.g., by controlling O2 safety valve 156) and generate an alarm at step 614.
[0311] Alternatively, if it is determined that a danger condition is not present (see step 616), the method may advance to step 618. At step 618, safety status module 161 may determine to adjust the danger factor threshold value used at step 610. For example, the threshold value may be adjusted (e.g., using an algorithm or look-up table) at step 620 according to the current ventilation mode or current ventilation parameters. The method may then return to steps 602-606 for continued measurements.
[0312] Referring to FIG. 13B , method 700 may be performed at any time during the operation of ventilation system 12. At step 702, a temperature of gas delivery system 20 (e.g., a blower motor) may be measured, e.g., using temperature sensor 83. At step 704, safety status module 161 may compare the measured temperature to a temperature threshold value. If the measured temperature does not surpass the temperature threshold value, there is no danger condition present, and the method may continue to step 718.
[0313] However, if the measured temperature does surpass the temperature threshold value, the method continues to step 706 for further analysis to determine whether a danger condition is present. At step 706, an operational speed of a component (e.g., a motor, blower, turbine) of gas delivery system 20 may be measured, e.g., using a speed sensor 84. At step 708, safety status module 161 may compare the measured speed to a speed threshold value. If the measured speed does not surpass the speed threshold value, there is no danger condition present, and the method may continue to step 718.
[0314] However, if the measured speed does surpass the speed threshold value, the method continues to step 710 for further analysis to determine whether a danger condition is present. At step 710, the power drawn by a component (e.g., a motor, blower, turbine) of gas delivery system 20 may be measured, e.g., using a power monitor 85. If the measured power does not surpass the power threshold value, there is no danger condition present, and the method may continue to step 718.
[0315] However, if the measured power does surpass the power threshold value (in combination with the temperature and speed surpassing their corresponding threshold values, as described above), a danger condition is identified at 714. In response to identifying the danger condition, control system 22 may slow or stop the supplemental oxygen flow (e.g., by controlling O2 safety valve 156) and generate an alarm at step 716.
[0316] As discussed above, if any of the measured temperature, speed, or power do not surpass their corresponding thresholds, there is no danger condition present, as indicated at step 718. At step 720, safety status module 161 may determine to adjust one or more threshold values used at steps 704, 708, and/or 712. For example, the speed threshold value may be adjusted (e.g., using an algorithm or look-up table) at step 722 according to the current ventilation mode or current ventilation parameters. The method may then return to step 702.
[0317] Certain steps may be eliminated from method 700 depending on which of temperature, speed, and power measurements are used for controlling O2 safety system, according to the particular embodiment. Thus, any of the method modules “A”, “B”, or “C” shown in FIG. 13B may be removed from method 700, depending on the particular embodiment. For example, in embodiments in which temperature and speed measurements, but not power measurements, are used for controlling O2 safety system, steps 710 and 712 indicated as method module “C” may be removed from method 700. As another example, in embodiments in which speed and power measurements, but not temperature measurements, are used for controlling O2 safety system, steps 702 and 704 indicated as method module “A” may be removed from method 700.
[0318] It should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the disclosure as illustrated by the following claims.
Claims
What is claimed is:
1. A method for managing pressure in a breathing assistance system configured to provide breathing assistance to a patient via a patient connection system, the method comprising:
receiving one or more first pressure sensor signals from a first pressure sensor;
analyzing the one or more first pressure sensor signals;
based at least on the analysis of the one or more first pressure sensor signals, selecting either the first pressure sensor or a separate second pressure sensor for use in controlling the breathing assistance provided to the patient; and
controlling the breathing assistance provided to the patient based at least on signals from the selected first or second pressure sensor.
2. A method according to claim 1, wherein:
the first pressure sensor is configured to measure gas pressure at a first location relative to the patient connection system; and
the second pressure sensor is configured to measure gas pressure at a different, second location relative to the patient connection system.
3. A method according to claim 2, wherein the first location is downstream toward the patient relative to the second location.
4. A method according to claim 1, wherein:
the first pressure sensor is configured to measure gas pressure at a location proximate a patient end of the patient connection system; and
the second pressure sensor is configured to measure gas pressure at a location proximate a delivery device end of the patient connection system generally opposite the patient end of the patient connection system.
5. A method according to claim 1, further comprising receiving one or more second pressure sensor signals from the second pressure sensor; and
wherein analyzing the one or more first pressure signals comprises comparing the one or more first pressure signals with the one or more second pressure signals.
6. A method according to claim 1 wherein selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the analysis of the one or more first pressure sensor signals comprises:
selecting the first pressure sensor if the one or more first pressure sensor signals indicate a pressure level above a threshold pressure level; and
selecting the second pressure sensor if the one or more first pressure sensor signals indicate a pressure level below the threshold pressure level.
7. A method according to claim 1, comprising:
receiving one or more second pressure sensor signals from the second pressure sensor; and
wherein analyzing the one or more first pressure sensor signals comprises:
making a first comparison of the one or more first pressure sensor signals with the one or more second pressure sensor signals; and making a first comparison of the one or more first pressure signals with a threshold pressure level; and
selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the first comparison and the second comparison.
8. A method according to claim 1, comprising:
receiving one or more second pressure sensor signals from the second pressure sensor; and
wherein analyzing the one or more first pressure sensor signals comprises comparing the one or more first pressure sensor signals with the one or more second pressure sensor signals; and
selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the analysis of the one or more first pressure sensor signals comprises:
selecting the first pressure sensor if the one or more first pressure sensor signals differ from the one or more second pressure sensor signals by less than a threshold amount; and
selecting the second pressure sensor if the one or more first pressure sensor signals differ from the one or more second pressure sensor signals by more than the threshold amount.
9. A method according to claim 1, wherein selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the analysis of the one or more first pressure sensor signals comprises:
determining whether a proximal pressure line is communicatively connected to the first pressure sensor based at least on the analysis of the one or more first pressure sensor signals;
selecting the first pressure sensor in response to determining that a proximal pressure line is communicatively connected to the first pressure sensor; and
selecting the second pressure sensor in response to determining that a proximal pressure line is not communicatively connected to the first pressure sensor.
10. A method according to claim 1, wherein controlling the breathing assistance provided to the patient comprises adjusting at least one of the pressure and flow rate of gas delivered toward the patient.
11. A method according to claim 1, wherein:
analyzing the one or more first pressure sensor signals comprises detecting a connection of a proximal pressure line configured for communication with the first pressure sensor; and
selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the analysis of the one or more first pressure sensor signals comprises automatically switching from the second pressure sensor to the first pressure sensor in response to detecting the connection of a proximal pressure line.
12. A method according to claim 1, wherein:
analyzing the one or more first pressure sensor signals comprises detecting a disconnection of a proximal pressure line configured for communication with the first pressure sensor; and
selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient based at least on the analysis of the one or more first pressure sensor signals comprises automatically switching from the first pressure sensor to the second pressure sensor in response to detecting the disconnection of a proximal pressure line.
13. A method according to claim 1, wherein selecting either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient comprises switching from the first pressure sensor to the second pressure sensor or from the second pressure sensor to the first pressure sensor while providing breathing assistance to the patient.
14. A method according to claim 1, further comprising disallowing initiation or continuation of at least one breathing assistance mode in response to the second pressure sensor being selected for use in controlling the breathing assistance provided to the patient.
15. A method according to claim 1, further comprising disallowing user selection of at least one breathing assistance mode in response to the second pressure sensor being selected for use in controlling the breathing assistance provided to the patient.
16. A method according to claim 1, further comprising automatically generating a user notification indicating whether the first or second pressure sensor is selected for use in controlling the breathing assistance provided to the patient.
17. A method according to claim 1, comprising:
automatically detecting an over-pressure condition in the patient connection system based on pressure sensor signals from the selected pressure sensor; and
in response to detecting the over-pressure condition in the patient connection system, automatically controlling the breathing assistance system to reduce the pressure in the patient connection system.
18. A method according to claim 1, comprising:
comparing pressure sensor signals from the selected pressure sensor to a pressure threshold; and
detecting an over-pressure condition in the patient connection system based at least on the comparison of the pressure sensor signals from the selected pressure sensor to the pressure threshold.
19. A method according to claim 1, comprising:
automatically detecting an over-pressure condition in the patient connection system based on pressure sensor signals from the non-selected pressure sensor; and
in response to detecting the over-pressure condition in the patient connection system, automatically controlling the breathing assistance system to reduce the pressure in the patient connection system.
20. A method according to claim 1, comprising:
comparing pressure sensor signals from the non-selected pressure sensor to a pressure threshold; and
detecting an over-pressure condition in the patient connection system based at least on the comparison of the pressure sensor signals from the non-selected pressure sensor to the pressure threshold.
21. A breathing assistance system configured to provide breathing assistance to a patient via a patient connection system, the breathing assistance system comprising:
a first pressure sensor;
a second pressure sensor; and
a control system configured to:
receive first pressure sensor signals from the first pressure sensor and second pressure sensor signals from the second pressure sensor;
analyze one or more first pressure sensor signals;
based at least on the analysis of the one or more first pressure sensor signals, select either the first pressure sensor or the second pressure sensor for use in controlling the breathing assistance provided to the patient; and
control the breathing assistance provided to the patient based at least on signals from the selected first or second pressure sensor.
22. A method for managing pressure in a breathing assistance system including a gas delivery system for delivering gas toward a patient via a patient connection system between the gas delivery system and the patient, the method comprising:
receiving first pressure sensor signals from a first pressure sensor configured to measure gas pressure at a first location relative to the patient connection system;
receiving second pressure sensor signals from a second pressure sensor configured to measure gas pressure at a different, second location relative to the patient connection system;
controlling the gas delivery system based on at least one of the first pressure sensor signals and the second pressure sensor signals;
automatically detecting an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals; and
in response to detecting the over-pressure condition in the patient connection system, automatically controlling the gas delivery system to reduce the pressure in the patient connection system.
23. A method according to claim 22, wherein automatically detecting an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals comprises automatically detecting an over-pressure condition in the patient connection system if either the one or more first pressure sensor signals or the one or more second pressure sensor signals indicate an over-pressure condition.
24. A method according to claim 22, wherein automatically detecting an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals comprises automatically detecting an over-pressure condition in the patient connection system if both the one or more first pressure sensor signals and the one or more second pressure sensor signals indicate an over-pressure condition.
25. A method according to claim 22, further comprising:
comparing the first pressure sensor signals to a first pressure threshold; comparing the second pressure sensor signals to a second pressure threshold; and
detecting an over-pressure condition in the patient connection system based on at least one of (a) the comparison of the first pressure sensor signals to the first pressure threshold and (b) the comparison of the second pressure sensor signals to the second pressure threshold.
26. A breathing assistance system for providing breathing assistance to a patient, comprising:
a gas delivery system for delivering gas toward a patient via a patient connection system between the gas delivery system and the patient;
a first pressure sensor configured to measure gas pressure at a first location relative to the patient connection system;
a second pressure sensor configured to measure gas pressure at a different, second location relative to the patient connection system; and
a control system configured to:
receive first pressure sensor signals from the first pressure sensor;
receive second pressure sensor signals from the second pressure sensor;
control the gas delivery system based on at least one of the first pressure sensor signals and the second pressure sensor signals; automatically detect an over-pressure condition in the patient connection system based on one or more first pressure sensor signals and one or more second pressure sensor signals; and
in response to detecting the over-pressure condition in the patient connection system, automatically control the gas delivery system to reduce the pressure in the patient connection system.
Patent Citations (267)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3120843(A) | 1964-02-01 | Hyman | Applicant |
| US3267935(A) | 1966-08-01 | Andreasen et al. | Applicant |
| US3333584(A) | 1967-08-01 | Andreasen et al. | Applicant |
| US3595228(A) | 1971-07-01 | Simon et al. | Applicant |
| US3675640(A) | 1972-07-01 | Gatts | Applicant |
| US3741208(A) | 1973-06-01 | Jonsson et al. | Applicant |
| US3811400(A) | 1974-05-01 | Smilg | Applicant |
| US3831595(A) | 1974-08-01 | Valenta et al. | Applicant |
| US3848591(A) | 1974-11-01 | Smythe et al. | Applicant |
| US3867934(A) | 1975-02-01 | Ollivier | Applicant |
| US3877467(A) | 1975-04-01 | Plicchi | Applicant |
| US3916888(A) | 1975-11-01 | Buck et al. | Applicant |
| US3985131(A) | 1976-10-01 | Buck et al. | Applicant |
| US3991304(A) | 1976-11-01 | Hillsman | Applicant |
| US4036221(A) | 1977-07-01 | Hillsman et al. | Applicant |
| US4050458(A) | 1977-09-01 | Friend | Applicant |
| US4077404(A) | 1978-03-01 | Elam | Applicant |
| US4096858(A) | 1978-06-01 | Eyrick et al. | Applicant |
| US4155357(A) | 1979-05-01 | Dahl | Applicant |
| US4176617(A) | 1979-12-01 | Pilipski | Applicant |
| US4239039(A) | 1980-12-01 | Thompson | Applicant |
| US4249528(A) | 1981-02-01 | Mathes | Applicant |
| US4281651(A) | 1981-08-01 | Cox | Applicant |
| US4286589(A) | 1981-09-01 | Thompson | Applicant |
| US4287886(A) | 1981-09-01 | Thompson | Applicant |
| US4302640(A) | 1981-11-01 | Vicenzi et al. | Applicant |
| US4318399(A) | 1982-03-01 | Berndtsson | Applicant |
| US4336590(A) | 1982-06-01 | Jacq et al. | Applicant |
| US4365636(A) | 1982-12-01 | Barker | Applicant |
| US4401115(A) | 1983-08-01 | Monnier | Applicant |
| US4421113(A) | 1983-12-01 | Gedeon et al. | Applicant |
| US4440177(A) | 1984-04-01 | Anderson et al. | Applicant |
| US4444201(A) | 1984-04-01 | Itoh | Applicant |
| US4448192(A) | 1984-05-01 | Stawitcke et al. | Applicant |
| US4466433(A) | 1984-08-01 | Robbins | Applicant |
| US4550726(A) | 1985-11-01 | McEwen | Applicant |
| US4602644(A) | 1986-07-01 | DiBenedetto et al. | Applicant |
| US4635631(A) | 1987-01-01 | Izumi | Applicant |
| US4637385(A) | 1987-01-01 | Rusz | Applicant |
| US4637386(A) | 1987-01-01 | Baum | Applicant |
| US4655213(A) | 1987-04-01 | Rapoport et al. | Applicant |
| US4674492(A) | 1987-06-01 | Niemeyer | Applicant |
| US4686974(A) | 1987-08-01 | Sato et al. | Applicant |
| US4686975(A) | 1987-08-01 | Naimon et al. | Applicant |
| USRE32553(E) | 1987-12-01 | Bennett et al. | Applicant |
| US4712580(A) | 1987-12-01 | Gilman et al. | Applicant |
| US4723543(A) | 1988-02-01 | Beran | Applicant |
| US4765326(A) | 1988-08-01 | Pieper | Applicant |
| US4766894(A) | 1988-08-01 | Legrand et al. | Applicant |
| US4782832(A) | 1988-11-01 | Trimble et al. | Applicant |
| US4803997(A) | 1989-02-01 | Bowman | Applicant |
| US4811755(A) | 1989-03-01 | Bourdon et al. | Applicant |
| US4825802(A) | 1989-05-01 | Le Bec | Applicant |
| US4838257(A) | 1989-06-01 | Hatch | Applicant |
| US4870393(A) | 1989-09-01 | Snuttjer et al. | Applicant |
| US4883051(A) | 1989-11-01 | Westenskow et al. | Applicant |
| US4899740(A) | 1990-02-01 | Napolitano | Applicant |
| US4941469(A) | 1990-07-01 | Adahan | Applicant |
| US4944310(A) | 1990-07-01 | Sullivan | Applicant |
| US4957107(A) | 1990-09-01 | Sipin | Applicant |
| US4967744(A) | 1990-11-01 | Chua | Applicant |
| US4971049(A) | 1990-11-01 | Rotariu et al. | Applicant |
| US4990894(A) | 1991-02-01 | Loescher et al. | Applicant |
| US5000173(A) | 1991-03-01 | Zalkin et al. | Applicant |
| US5035239(A) | 1991-07-01 | Edwards | Applicant |
| US5042470(A) | 1991-08-01 | Kanesaka | Applicant |
| US5057822(A) | 1991-10-01 | Hoffman | Applicant |
| US5065756(A) | 1991-11-01 | Rapoport | Applicant |
| US5072729(A) | 1991-12-01 | DeVries | Applicant |
| US5097826(A) | 1992-03-01 | Gray et al. | Applicant |
| US5107830(A) | 1992-04-01 | Younes | Applicant |
| US5107831(A) | 1992-04-01 | Halpern et al. | Applicant |
| US5117819(A) | 1992-06-01 | Servidio et al. | Applicant |
| US5129390(A) | 1992-07-01 | Chopin et al. | Applicant |
| US5134995(A) | 1992-08-01 | Gruenke et al. | Applicant |
| US5146918(A) | 1992-09-01 | Kallok et al. | Applicant |
| US5148802(A) | 1992-09-01 | Sanders et al. | Applicant |
| US5161541(A) | 1992-11-01 | Bowman et al. | Applicant |
| US5165397(A) | 1992-11-01 | Arp | Applicant |
| US5190048(A) | 1993-03-01 | Wilkinson | Applicant |
| US5199424(A) | 1993-04-01 | Sullivan et al. | Applicant |
| US5203343(A) | 1993-04-01 | Axe et al. | Applicant |
| US5231979(A) | 1993-08-01 | Rose et al. | Applicant |
| US5239995(A) | 1993-08-01 | Estes et al. | Applicant |
| US5246995(A) | 1993-09-01 | Murakami et al. | Applicant |
| US5259373(A) | 1993-11-01 | Gruenke et al. | Applicant |
| US5269296(A) | 1993-12-01 | Landis | Applicant |
| US5275159(A) | 1994-01-01 | Griebel | Applicant |
| US5303699(A) | 1994-04-01 | Bonassa et al. | Applicant |
| US5313937(A) | 1994-05-01 | Zdrojkowski | Applicant |
| US5320092(A) | 1994-06-01 | Ryder | Applicant |
| US5335654(A) | 1994-08-01 | Rapoport | Applicant |
| US5353788(A) | 1994-10-01 | Miles | Applicant |
| US5365922(A) | 1994-11-01 | Raemer | Applicant |
| US5373842(A) | 1994-12-01 | Olsson et al. | Applicant |
| US5383449(A) | 1995-01-01 | Forare et al. | Applicant |
| US5390666(A) | 1995-02-01 | Kimm et al. | Applicant |
| US5413111(A) | 1995-05-01 | Wilkinson | Applicant |
| US5433193(A) | 1995-07-01 | Sanders et al. | Applicant |
| US5438980(A) | 1995-08-01 | Phillips | Applicant |
| US5456264(A) | 1995-10-01 | Series et al. | Applicant |
| US5458137(A) | 1995-10-01 | Axe et al. | Applicant |
| US5490499(A) | 1996-02-01 | Heinonen et al. | Applicant |
| US5490502(A) | 1996-02-01 | Rapoport et al. | Applicant |
| US5503146(A) | 1996-04-01 | Froehlich et al. | Applicant |
| US5517983(A) | 1996-05-01 | Deighan et al. | Applicant |
| US5520172(A) | 1996-05-01 | Obermayer | Applicant |
| US5522382(A) | 1996-06-01 | Sullivan et al. | Applicant |
| US5535738(A) | 1996-07-01 | Estes et al. | Applicant |
| US5535739(A) | 1996-07-01 | Rapoport et al. | Applicant |
| US5537997(A) | 1996-07-01 | Mechlenburg et al. | Applicant |
| US5540220(A) | 1996-07-01 | Gropper et al. | Applicant |
| US5540733(A) | 1996-07-01 | Testerman et al. | Applicant |
| US5546933(A) | 1996-08-01 | Rapoport et al. | Applicant |
| US5549106(A) | 1996-08-01 | Gruenke et al. | Applicant |
| US5551419(A) | 1996-09-01 | Froehlich et al. | Applicant |
| USRE35339(E) | 1996-10-01 | Rapoport | Applicant |
| US5577496(A) | 1996-11-01 | Blackwood et al. | Applicant |
| US5603315(A) | 1997-02-01 | Sasso, Jr. | Applicant |
| US5626129(A) | 1997-05-01 | Klimm et al. | Applicant |
| US5630411(A) | 1997-05-01 | Holscher | Applicant |
| US5640149(A) | 1997-06-01 | Campbell | Applicant |
| US5645053(A) | 1997-07-01 | Remmers et al. | Applicant |
| US5645054(A) | 1997-07-01 | Cotner | Applicant |
| US5647351(A) | 1997-07-01 | Weismann et al. | Applicant |
| US5660171(A) | 1997-08-01 | Kimm et al. | Applicant |
| US5664562(A) | 1997-09-01 | Bourdon | Applicant |
| US5704345(A) | 1998-01-01 | Berthon-Jones | Applicant |
| US5715812(A) | 1998-02-01 | Deighan et al. | Applicant |
| US5720709(A) | 1998-02-01 | Schnall | Applicant |
| US5732696(A) | 1998-03-01 | Rapoport et al. | Applicant |
| US5735267(A) | 1998-04-01 | Tobia | Applicant |
| US5740796(A) | 1998-04-01 | Skog | Applicant |
| US5743253(A) | 1998-04-01 | Castor et al. | Applicant |
| US5746201(A) | 1998-05-01 | Kidd | Applicant |
| US5746697(A) | 1998-05-01 | Swedlow et al. | Applicant |
| US5794614(A) | 1998-08-01 | Gruenke et al. | Applicant |
| US5797393(A) | 1998-08-01 | Kohl | Examiner |
| US5803066(A) | 1998-09-01 | Rapoport et al. | Applicant |
| US5829441(A) | 1998-11-01 | Kidd et al. | Applicant |
| US5845636(A) | 1998-12-01 | Gruenke et al. | Applicant |
| US5873361(A) | 1999-02-01 | Hakala | Applicant |
| US5875783(A) | 1999-03-01 | Kullik | Applicant |
| US5878744(A) | 1999-03-01 | Pfeiffer | Applicant |
| US5881717(A) | 1999-03-01 | Isaza | Applicant |
| US5901704(A) | 1999-05-01 | Estes et al. | Applicant |
| US5921238(A) | 1999-07-01 | Bourdon | Applicant |
| US5924979(A) | 1999-07-01 | Swedlow et al. | Applicant |
| US5950621(A) | 1999-09-01 | Klockseth et al. | Applicant |
| US5970975(A) | 1999-10-01 | Estes et al. | Applicant |
| US6032065(A) | 2000-02-01 | Brown | Applicant |
| US6067022(A) | 2000-05-01 | Laswick et al. | Applicant |
| US6085747(A) | 2000-07-01 | Axe et al. | Applicant |
| US6095139(A) | 2000-08-01 | Psaros | Applicant |
| US6123074(A) | 2000-09-01 | Hete et al. | Applicant |
| US6131571(A) | 2000-10-01 | Lampotang et al. | Applicant |
| US6135106(A) | 2000-10-01 | Dirks et al. | Applicant |
| US6152132(A) | 2000-11-01 | Psaros | Applicant |
| US6209579(B1) | 2001-04-01 | Bowden et al. | Applicant |
| US6269811(B1) | 2001-08-01 | Duff et al. | Applicant |
| US6283119(B1) | 2001-09-01 | Bourdon | Applicant |
| US6299581(B1) | 2001-10-01 | Rapoport et al. | Applicant |
| US6308706(B1) | 2001-10-01 | Lammers et al. | Applicant |
| US6341606(B1) | 2002-01-01 | Bordewick et al. | Applicant |
| US6347631(B1) | 2002-02-01 | Hansen et al. | Applicant |
| US6360741(B2) | 2002-03-01 | Truschel | Applicant |
| US6386196(B1) | 2002-05-01 | Culton | Applicant |
| US6392555(B1) | 2002-05-01 | Most, Jr. | Applicant |
| US6418928(B1) | 2002-07-01 | Bordewick et al. | Applicant |
| US6431172(B1) | 2002-08-01 | Bordewick | Applicant |
| US6488634(B1) | 2002-12-01 | Rapoport et al. | Applicant |
| US6505623(B1) | 2003-01-01 | Hansen | Applicant |
| US6516802(B2) | 2003-02-01 | Hansen et al. | Applicant |
| US6530373(B1) | 2003-03-01 | Patron et al. | Applicant |
| US6543449(B1) | 2003-04-01 | Woodring et al. | Applicant |
| US6546930(B1) | 2003-04-01 | Emerson et al. | Applicant |
| US6571795(B2) | 2003-06-01 | Bourdon | Applicant |
| US6591834(B1) | 2003-07-01 | Colla et al. | Applicant |
| US6615828(B1) | 2003-09-01 | Petherbridge | Applicant |
| US6626175(B2) | 2003-09-01 | Jafari et al. | Applicant |
| US6629527(B1) | 2003-10-01 | Estes et al. | Applicant |
| US6644310(B1) | 2003-11-01 | Delache et al. | Applicant |
| US6644316(B2) | 2003-11-01 | Bowman et al. | Applicant |
| US6668824(B1) | 2003-12-01 | Isaza et al. | Applicant |
| US6668830(B1) | 2003-12-01 | Hansen et al. | Applicant |
| US6718974(B1) | 2004-04-01 | Moberg | Applicant |
| US6745768(B2) | 2004-06-01 | Colla et al. | Applicant |
| US6761167(B1) | 2004-07-01 | Nadjafizadeh et al. | Applicant |
| US6761168(B1) | 2004-07-01 | Nadjafizadeh et al. | Applicant |
| US6793629(B2) | 2004-09-01 | Rapoport et al. | Applicant |
| US6814074(B1) | 2004-11-01 | Nadjafizadeh et al. | Applicant |
| US6823866(B2) | 2004-11-01 | Jafari et al. | Applicant |
| US6840240(B1) | 2005-01-01 | Berthon-Jones et al. | Applicant |
| US6844691(B2) | 2005-01-01 | Chiang et al. | Applicant |
| US6866040(B1) | 2005-03-01 | Bourdon | Applicant |
| US6877511(B2) | 2005-04-01 | DeVries et al. | Applicant |
| US6960854(B2) | 2005-11-01 | Nadjafizadeh et al. | Applicant |
| US7000612(B2) | 2006-02-01 | Jafari et al. | Applicant |
| US7040317(B2) | 2006-05-01 | Colla et al. | Applicant |
| USRE39225(E) | 2006-08-01 | Isaza et al. | Applicant |
| US7089930(B2) | 2006-08-01 | Adams et al. | Applicant |
| US7100608(B2) | 2006-09-01 | Brewer et al. | Examiner |
| US7101341(B2) | 2006-09-01 | Tsukashima et al. | Applicant |
| US7297120(B2) | 2007-11-01 | Tsukashima et al. | Applicant |
| US7975691(B2) | 2011-07-01 | Cha et al. | Examiner |
| US2002/0005197(A1) | 2002-01-01 | DeVries et al. | Applicant |
| US2002/0014239(A1) | 2002-02-01 | Chalvignac | Applicant |
| US2002/0014240(A1) | 2002-02-01 | Truschel | Examiner |
| US2002/0053345(A1) | 2002-05-01 | Jafari et al. | Applicant |
| US2003/0062045(A1) | 2003-04-01 | Woodring et al. | Applicant |
| US2003/0066529(A1) | 2003-04-01 | Truschel et al. | Applicant |
| US2004/0015058(A1) | 2004-01-01 | Besson et al. | Applicant |
| US2004/0050387(A1) | 2004-03-01 | Younes | Applicant |
| US2004/0226561(A1) | 2004-11-01 | Colla et al. | Applicant |
| US2005/0061321(A1) | 2005-03-01 | Jones | Applicant |
| US2005/0087187(A1) | 2005-04-01 | Berthon-Jones et al. | Applicant |
| US2005/0087190(A1) | 2005-04-01 | Jafari et al. | Applicant |
| US2005/0263155(A1) | 2005-12-01 | Gossweiler | Applicant |
| US2006/0070624(A1) | 2006-04-01 | Kane et al. | Applicant |
| US2006/0107953(A1) | 2006-05-01 | Truschel et al. | Applicant |
| US2008/0021339(A1) | 2008-01-01 | Gabriel et al. | Applicant |
| US2008/0177404(A1) | 2008-07-01 | Bonnat | Applicant |
| US2008/0200776(A1) | 2008-08-01 | Schermeier et al. | Applicant |
| DE3306607(A1) | 1983-02-01 | Applicant | |
| DE3732475 | 1989-04-01 | Applicant | |
| DE4038871(A1) | 1992-06-01 | Applicant | |
| DE19714644(A) | 1998-10-01 | Applicant | |
| EP42321(A1) | 1981-06-01 | Applicant | |
| EP46570 | 1982-03-01 | Applicant | |
| EP283141(A2) | 1988-02-01 | Applicant | |
| EP402951(A2) | 1990-06-01 | Applicant | |
| EP459647 | 1991-12-01 | Applicant | |
| EP504725(A2) | 1992-09-01 | Applicant | |
| EP504945 | 1992-09-01 | Applicant | |
| EP99743 | 1994-02-01 | Applicant | |
| EP621056(A1) | 1994-10-01 | Applicant | |
| EP661071(B1) | 1995-07-01 | Applicant | |
| EP742027 | 1996-11-01 | Applicant | |
| EP774233(A1) | 1997-05-01 | Applicant | |
| EP862922(A) | 1998-09-01 | Applicant | |
| EP1243282(A) | 2002-09-01 | Applicant | |
| FR2663547(A1) | 1990-06-01 | Applicant | |
| FR2695830(A1) | 1992-09-01 | Applicant | |
| FR2822384(A1) | 2002-09-01 | Applicant | |
| GB2054387(A) | 1980-06-01 | Applicant | |
| GB2215216(B1) | 1989-09-01 | Applicant | |
| GB2294400 | 1996-05-01 | Applicant | |
| GB2324122(A) | 1998-10-01 | Applicant | |
| WO88/10108 | 1988-12-01 | Applicant | |
| WO89/10768 | 1989-11-01 | Applicant | |
| WO89/11823 | 1989-12-01 | Applicant | |
| WO90/14121 | 1990-11-01 | Applicant | |
| WO91/06832 | 1991-05-01 | Applicant | |
| WO91/19526 | 1991-12-01 | Applicant | |
| WO9211054 | 1992-07-01 | Applicant | |
| WO9215355(A1) | 1992-09-01 | Applicant | |
| WO9321982 | 1993-11-01 | Applicant | |
| WO9325260 | 1993-12-01 | Applicant | |
| WO95/28874 | 1995-11-01 | Applicant | |
| WO9603174(A1) | 1996-02-01 | Applicant | |
| WO96/08285 | 1996-03-01 | Applicant | |
| WO9933508(A1) | 1999-07-01 | Applicant | |
| WO/24447 | 2000-05-01 | Applicant | |
| WO27457(A1) | 2000-05-01 | Applicant | |
| WO2/26305 | 2002-04-01 | Applicant | |
| WO2004/024053 | 2004-03-01 | Applicant | |
| WO2007/035804 | 2007-03-01 | Applicant |
Non-Patent Literature (62)
- Clergue et al., Le Respirateur Servo Ventilator 900 C, Department d'anesthesie-reanimation (Pr P. Viars) Groupe Hospitalier Pitie, Salpetriere, Paris, pp. 417-421, 1984.Applicant
- Conference Proceedings, the New Generation of Mechanical Ventilators, Respiratory Care, vol. 32, No. 6, pp. 403-418, Jun. 1987.Applicant
- International PCT Search Report with Written Opinion, PCT/US2007/077195, 3 pages, Feb. 14, 2008.Applicant
- International PCT Search Report and Written Opinion, PCT/US2009/055280, 22 pages, Mar. 24, 2010.Applicant
- “GoodKnight© 425 GoodKnight© 425ST Clinician and Home Care Provider Manual”, Puritan Bennett, Revision G, p. 25, referring to breathing circuits having an “internal pressure sensor line”, Mar. 2010.Applicant
- “Puritan Bennett CPAP / BiLEVEL Tubing with Internal Pressure Sensor Line”, Printout of page from website www.cpapxchange.com, 2 pages, Printed Jun. 9, 2010.Applicant
- Ballard, Robert, et al., “Sleep Apnea—Diagnosis and Treatment”, Topics in Primary Care Medicine, The Western Journal of Medicine, 145:249-250, Aug. 1986.Applicant
- Guilleminault, C. et al., “Unattended CPAP Titration: Toward a Smart Machine”, 1992; pp. 342 [Sleep Research, vol. 21], 1992.Applicant
- Miles, L.E. et al.; “Development and Application of an Automatic Nasal CPAP Calibration Procedures for Use in the Unsupervised Home Environment”; pp. S118-S119 [Supplemental Issue: Sleep and Breathing, vol. 16.], Dec. 1993.Applicant
- Miles, L.E. et al.; “Different Roles for an Automatic Nasal CPAP Calibration Procedure and Smart Pap”, Sleep Research 21, p. 238, 1993.Applicant
- Remmers, et al.; “Mechanics of the Pharynx in Patients With Obstructive Sleep Apnea”; pp. 261-271 [Sleep and Respiration], 1990.Applicant
- Miles, L.E. et al.; “Development and Application of an Automatic Nasal CPAP Calibration Procedure for Use in the Unsupervised Home Environmnet”; p. 352 [Sleep Research, vol. 21], 1992.Applicant
- Dupuis, Yvon G., “Ventilators—Theory and Clinical Application”, The C.V. Mosby Co., pp. 107-117, 1986.Applicant
- Sullivan et al., Reversal of Obstructive Sleep Apnea by Continuous Positive Airway Pressure Applied Through the Nares, The Lancet, vol. 1, No. 8225, pp. 862-865, 1981.Applicant
- International Preliminary Examination Report for Relating International Application PCT/FR93/00902, Jun. 9, 1994.Applicant
- Rapapart et al., “Reversal of the Pickwickian Syndrome by Long-term use of Nocturnal Nasal-Airway Pressure”, New England Journal of Medicine, vol. 307, No. 15, pp. 931-933, 1982.Applicant
- Operating Manual for Siemens Servo ventilator 300, May 1993.Applicant
- Service Manual for Siemens Servo Ventilator 300, Feb. 1994.Applicant
- Schwartz et al., “Induction of Upper Airway Occlusion in Sleeping Individuals with Subatmospheric Nasal Pressure”, Journal of Applied Physiology, pp. 535-542, 1988.Applicant
- Southworth et al., “Digital Computation and Numerical Methods”, McGraw-Hill, Inc., pp. 6-10, 1965.Applicant
- Rapoport, “Techniques for Administering Nasal CPAP”, Respiratory Management, pp. 18-21, 1987.Applicant
- Garay, “Therapeutic Options for Obstructive Sleep Apnea”, Respiratory Management, pp. 11-15, 1987.Applicant
- Technical Brochure of the SV300, Mar. 1992.Applicant
- Siemans News Letter, Nov. 1992.Applicant
- Jager, “Microprocessor Based Disconnect Monitor in Surgery”, The UBC Engineer, pp. 28-31, 1982.Applicant
- MacIntyre, “Clinically Available New Strategies for Mechanical Ventilatory Support”, Chest/104/2 (Duke University Medical Center, Durham, NC), pp. 560-565, 1993.Applicant
- Pocket Guide for Siemens System Servo Ventilator, Nov. 1993.Applicant
- Search Report Corresponding International Appln. No. PCT/FR95/01158, Nov. 23, 1995.Applicant
- Preliminary Examination Report for Corresponding International Appln. No. PCT/Fr95/01158, Oct. 22, 1996.Applicant
- Notification of Opposition to Corresponding European Appln. Ser. No. 95/930565.70782462, Apr. 13, 2000.Applicant
- The Future Begins . . . with Puritan-Bennett's 7200 Microprocessor Ventilator, May 1983.Applicant
- Puritan-Bennett, 7200 Microprocessor Ventilator Service Manual, Figure 2-1 Electro-Pneumatic System, Jun. 1983.Applicant
- Puritan-Bennett, 7200 Microprocessor Ventilator Operator's Manual, Mar. 1986.Applicant
- Puritan-Bennett Brochure, Flow-By, Option 50, pp. 1-6, Oct. 1986.Applicant
- French Search Report for Relating French Application No. 9211131, Jun. 29, 1993.Applicant
- Search Report Corresponding to French (priority Appln. Ser. No. FR9410839, Jun. 2, 1995.Applicant
- A First Opposition Brief Against the Relating European Patent 0 662 009 B1, Feb. 15, 1999.Applicant
- Response to Opposition Relating to European Patent 0 662 009 B1, Oct. 8, 1999.Applicant
- A Second Opposition Brief Against the Relating European Patent 0 662 009 B1, Jan. 19, 2000.Applicant
- Response to Second Notice of Opposition Relating to European Patent 0 662 009 B1, Apr. 21, 2000.Applicant
- European Patent Office's Decision on the Opposition Corresponding to European Patent 0 662 009, Sep. 27, 2001.Applicant
- Non-Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 6 pages, Mailed Jun. 6, 2001.Applicant
- Response to Office Action dated Jun. 6, 2001, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 5 pages, filed Sep. 6, 2001.Applicant
- Non-Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 9 pages, Mailed Nov. 29, 2001.Applicant
- Response to Non-Final Office Action dated Nov. 29, 2001, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 4 pages, filed Feb. 28, 2002.Applicant
- Non-Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 10 pages, Mailed Jul. 2, 2002.Applicant
- Opposition Filed by SIEMENS Corresponding to European Appln. Ser. No. 95/930565.7, Feb. 22, 2000.Applicant
- Grounds of Decision of Revocation Corresponding to European Appln. No. Ser. No. 95/930565.7 (with English translation), Oct. 16, 2001.Applicant
- Response to Non-Final Office Action dated Jul. 2, 2002, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 10 pages, filed Oct. 2, 2002.Applicant
- Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 12 pages, Mailed Dec. 31, 2002.Applicant
- Response to Final Office Action dated Dec. 31, 2002, filed concurrently with Request for Continued Examination for U.S. Appl. No. 09/307,511, filed May 7, 1999, 11 pages, filed Apr. 30, 2000.Applicant
- Non-Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 11 pages, Mailed Jul. 3, 2003.Applicant
- Response to Non-Final Office Action dated Jul. 3, 2003, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 13 pages, filed Oct. 3, 2003.Applicant
- Final Office Action, U.S. Appl. No. 09/307,511, filed May 7, 1999, 12 pages, Mailed Dec. 23, 2003.Applicant
- Response to Final Office Action dated Dec. 23, 2003, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 10 pages, filed Feb. 23, 2004.Applicant
- Notice of Appeal to the Board of Patent Appeals and Interferences, U.S. Appl. No. 09/307,511, filed May 7, 1999, 2 pages, filed Mar. 23, 2004.Applicant
- Non-Final Office Action, U.S. Appl. No. 09/307,511, Filed May 7, 1999, 12 pages, Mailed Apr. 28, 2004.Applicant
- Response to Non-Final Office Action dated Apr. 28, 2004, in U.S. Appl. No. 09/307,511, filed May 7, 1999, 11 pages, Filed Jul. 28, 2004.Applicant
- U.S. Appl. No. 12/238,607 as filed with the U.S. Patent and Trademark Office, Filed Sep. 26, 2008.Applicant
- U.S. Appl. No. 11/469,677 as filed with the U.S. Patent and Trademark Office, filed Sep. 1, 2006.Applicant
- U.S. Appl. No. 12/140,095 as filed with the U.S. Patent and Trademark Office, filed Jun. 16, 2008.Applicant
- U.S. Appl. No. 11/781,013 as filed with the U.S. Patent and Trademark Office, filed Jul. 20, 2007.Applicant