This invention relates to ventilators and to drug dispensing systems.
Mechanical ventilation is a method of mechanically assisting or replacing spontaneous breathing when patients cannot do so. One type of ventilation system employs the use of an endotracheal or tracheostomy tube secured into a patient's upper respiratory tract. Gas is mechanically delivered to the patient via the tube. In many cases, mechanical ventilation is used in acute settings such as an intensive care unit for a short period of time during a serious illness. Currently, the main form of mechanical ventilation is positive pressure ventilation, which works by increasing the pressure in the patient's airway and thus forcing additional air into the lungs. To aid in the treatment of ventilated patients, aerosol medicines are aspirated in situ through an access point in the ventilator system. Conventionally, this process is manual, requiring the medical professional to deliver the aerosols on a regular basis.
Automatically administering medication to mechanically ventilated patients may reduce healthcare costs and improve patient safety.
Embodiments of the present invention relate generally to systems for respiratory therapy, particularly to ventilator systems that include heat and moisture exchanger (HME) media or heat and moisture exchanger (HME) media in the respiratory path and also provides the additional capability of automated dispensing of aerosol medication to a patient effectively without interrupting the respiratory path.
It is noted that aspects of the invention described with respect to one embodiment may be incorporated in a different embodiment although not specifically described relative thereto. That is, all embodiments and/or features of any embodiment can be combined in any way and/or combination. Applicant reserves the right to change any originally filed claim or file any new claim accordingly, including the right to be able to amend any originally filed claim to depend from and/or incorporate any feature of any other claim although not originally claimed in that manner. These and other objects and/or aspects of the present invention are explained in detail in the specification set forth below.
The present invention will now be described more fully hereinafter, in which embodiments of the invention are shown. This invention may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the drawings, like numbers refer to like elements throughout.
Thicknesses and dimensions of some components may be exaggerated for clarity. Broken lines illustrate elements or features not visible from the presented view (e.g., on the opposite side) or as an optional element unless otherwise indicated. It will be understood that when an element is referred to as being “attached,” “connected,” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly attached,” “directly connected,” or “directly coupled” to another element, there are no intervening elements present. Also, although a feature is described with respect to one embodiment, this feature may be used with another embodiment.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. As used herein, phrases such as “between X and Y” and “between about X and Y” should be interpreted to include X and Y. As used herein, phrases such as “between about X and Y” mean “between about X and about Y.” As used herein, phrases such as “from about X to Y” mean “from about X to about Y.”
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the specification and relevant art and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Well-known functions or constructions may not be described in detail for brevity and/or clarity.
The term “about” when used with a numerical values means that the numerical value can vary by +/−20%.
Turning now to the figures, a ventilator system 100 with an automated drug dispensing control and delivery system 10 is illustrated in
In some embodiments, the dispensing system 10 can include a housing 10h that can hold the actuator 11. The housing 10h can be a compact, light-weight device that can reside directly on tubing in the ventilator tubing system, typically in fluid communication with the inhalation tubing upstream of the heat and moisture exchanger (HME) 30.
The HME 30 is typically passive without requiring active heating or humidification as is known to those of skill in the art. However, active HMEs may also be used. A commercially available HME, which uses a bypass flow path, is the CIRCUVENT® sold by Smiths Medical.
As illustrated in
As shown in
The inhalation connector leg or fork 34i of the Y connector 34 can be connected to one end of a (typically flexible) bypass tube 40 having its other end of the bypass tube 40 connected to tubing 33 downstream of the HME 30, closer to the endotracheal tube inside the patient P. The inhalation connector leg or fork 34i can include at least one internal electromechanical flow valve 25 that is configured with a valve member 25m that is normally closed to close the intake region 40i of the bypass tubing from the inhalation flow path.
As shown in
The at least one flow valve 25 can be located at various locations along the inhalation flow path, including upstream, instead of downstream, of the actuator 12. The bypass flow valve 25 can reside upstream of the Y connector 34 (where used).
In some embodiments, the ventilator circuit 60c can include three or more inhalation flow path tubes (
Various types of medical grade valves can be used for the at least one valve 25. As shown in
As also shown in
Other types of medical grade valves can be used for the at least one valve 25. For example, a ball valve can be used, which may provide for rapid shut-off, since a 90° turn offers complete a shut-off angle.
In some embodiments, first and second valves upstream of the HME 30 may be used, one to shut the normal flow path through the HME 30 and the other to open the bypass path 40. The first and second valves may comprise butterfly valves or other valve configurations. The first and second valves can be operated with a defined sequence, e.g., open bypass concurrently with the closing of the normal flow path through the HME or open the bypass path, then rapidly close the normal bypass flow path within 0.1 seconds to 2 seconds, for example.
In some embodiments, the at least one valve 25 may be configured as a disc valve, a diaphragm valve, a gate valve, a knife valve, and/or a plug valve, by way of example.
In some embodiments a check valve (e.g., a one way valve) may be positioned at the egress end of the inhalation bypass tube 40e to inhibit exhalation flow in the bypass tube 40 thereby reducing “dead volume.”
The at least one valve 25 includes an electrical connection 26 (wired or wireless) to at least one controller 50 for automated operation in synchronization with inhalation air flow based on input from an air flow sensor 35 and/or the ventilator 60. The actuator 11 can also include an electrical (wired or wireless) connection to the at least one controller 50. The sensor 35 can include at least one electrical (wired or wireless) connection 36 to the at least one controller 50.
While the at least one valve 25 is shown using a “Y” connector upstream of the HME 30, other flow circuit 60c configurations may be used.
The at least one controller 50 can be a single controller or may be a plurality of controllers which may be in a common location or distributed. The at least one controller 50 can monitor inhalation air flow direction using data from an air flow sensor 25 and/or ventilator 60, direct the actuation of the actuator 11 to only actuate when air flow is in the inhalation direction and open the normally closed valve 25 to open the bypass valve when the actuator is actively dispensing or within a defined time before and/or after a dispensing. The dispensing system 10 may be configured to provide different numbers of actuations per inhalation for custom dosing.
The at least one valve can be a single valve 25 or may comprise a plurality of valves. For example, the at least one valve 25 can include a first valve 251 at the intake to the bypass tubing 40i and a second valve 252 at the egress of the bypass tubing 40e as shown in
With respect to
The at least one valve 25 can be configured to automatically return to the closed state a defined time after it is open without being directed to close by the at least one controller 50. For example, the at least one valve 25 can be biased to return to the closed configuration after it is open or may have a timer that directs the closure independent of the controller 50. However, typically the at least one controller 50 can direct the at least one valve 25 to return to a defined home state.
As shown in
The direction of air flow (exhale/inhale) may optionally be determined by a sensor 35, which can be placed at a number of locations along the ventilation flow circuit 60c and/or by the operation of the ventilator 60, 60′ itself.
As shown in
The embodiments shown in
The dispensing system 10 can be configured to be dynamic, responsive to the patients physiologic parameters. That is, the dispensing system 10 (whether a separate system or incorporated into the ventilator 60) can be a “smart” device that will actuate automatically in accordance to a preset algorithm based-off the patient's current (bedside) physiologic status including but not limited to, one or more of the following parameters which can be electronically periodically or continuously monitored by the system 10 and/or 60′ or by devices in communication therewith: heart rate, respiratory rate, airway resistance, blood pressure, minute ventilation, end tidal carbon dioxide measurements, temperature, EEG monitoring, cardiac telemetry rhythm/ECG monitoring, oxygen saturation/oximetry monitoring peripheral or central, nitric oxide exhaled. The term “minute ventilation” is well known and refers to a measured parameter of the ventilator, e.g., Resp rate×tidal volume.
As illustrated in
The display 120 can configured to display certain information and operational parameters. For example, the doses remaining (i.e., the number of doses input by the operator or the number of doses associated with the MDI 11 less the number of doses already administered) may be displayed. The number of doses need not necessarily match the number of actuations as a patient may need more than one “puff per dose.” In some embodiments, the system 10 can be configured to track and/or display the number of actuations or “puffs.” MDIs are sometimes prepackaged and pre-measured with a defined number of actuations or puffs (e.g., 60 to 400 actuations or puffs). Because the number of puffs per dose may vary based on a patient and/or a physician's orders, the unit can track the actuations or puffs to provide information and audible, visual or other warning as to when the MDI canister 11 will be empty or should be replaced. It is noted that although the system 10 can track or measure actuations (puffs), the dispensing system 10 can also be programmed such that this information is converted to doses for a particular patient.
The interval between doses may also be displayed on the display 120d. Other information such as the “status” of the MDI 11 can also be displayed. For example, the status may read “on” when the MDI is operating under an automated mode with defined programmed parameters or “off” if the MDI is not in an automated mode. The status may also inform the operator whether the MDI has been installed correctly and/or whether the MDI is operational in general. The controller 50 (
In some embodiments, all operational information can be displayed on the display 120d together. Alternatively, the information may scroll along the display 120d and/or the display 120d may toggle between different screens containing different information. The display UI control may allow the operator to manually perform these scrolling and toggling operations. The display UI control may also power the display “on” and “off” in some embodiments. The display 120d may power “on” and “off” at various intervals for a power-saving mode. An “on” display mode may be triggered by a proximity sensor or by a clinician's manual input or at selected or pre-set time intervals. The display 120d may automatically operate prior to actuation and just after then go into power-saving mode.
Power may be provided to the system 10 via a medical grade AC or DC power supply 150. The dispensing system 10 may include a battery to allow the unit 10 to function if the AC or DC power supply is interrupted. Alternatively, the power may be provided by an on-board housing battery and the system 10 can include one or more backup batteries. It is contemplated that various components could be powered by different power sources. For example, the actuator 11, display 120d, controller 50 and valve 25 may be powered by different power sources.
In operation, the controller 50 can direct an agitator to agitate the canister 12 just prior to actuation and delivery of the medication based on the selected delivery frequency. The controller 50 can direct the actuator 11 to actuate the canister 12 to dispense medication into the inhalation flow path TI of the ventilator flow circuit 60c. The controller 50 times the actuation such that the medication is dispensed while the flow of gas through the tubular (spacer) connector 16 is toward the patient (i.e., while the patient inhales) and the at least one bypass valve 25 is open to force the medication to travel through the bypass valve to the patient to avoid the HME. This flow direction is indicated by the arrows to the right in
It is noted that two or more successive actuations could equal one dose where the dose is two or more “puffs” and the dose counter can indicate the number of doses remaining (shown by schematic example in
The gas flow sensor 35 can be disposed in the connector 16 (or elsewhere in the ventilator circuit 60c) to detect incoming air from the ventilator V and exhaled breath from the patient P. In other words, the gas flow sensor 35 can measure or sense the direction of the flow of gas through the tubing TI, and/or connector 16 (or the ventilator circuit 60c) and communicate the same to the controller. As described above, the release of medication from the canister 12 can be timed so that the medication flows with the gas toward the patient. The gas flow sensor 35 or a different sensor may further verify that the medication properly reaches the patient and may communicate the same to the controller 50.
The gas flow sensor 35, or an additional sensor, may be used to measure pressure and/or the rate of change of pressure in the ventilator flow circuit, and may measure other gas flow characteristics such as volumetric gas flow rate and temperature, that indicate the patient's ability to receive the medication. The gas flow sensor 35 can measure ventilator flow circuit conditions and patient airway resistance, which may be used to determine the need for additional medication dosing and timing or modulation of the current specified dosing and timing of the medication. Higher pressure and/or a relatively short cycle time on reversal of gas flow may indicate that the ability of the patient to consume the medication through the lungs is impaired. In such case, the controller 50 may increase the dosage frequency or dosage amount to the patient or both. The adjustment may occur manually or automatically by an algorithm utilized by the controller 50. Similarly, to wean the patient, the frequency and/or dose amount can be reduced when patient airway resistance improves.
The sensor(s) described herein and other sensors may perform other functions as described in U.S. Pat. Nos. 8,857,429 and 8,869,793, the disclosures of which are incorporated by reference as if disclosed herein in its entirety.
The dispensing system 10 can include a manual override UI control 32. The operator may use this control to deliver an unscheduled release of medication, such as if the respiratory condition of the patient appears poor or upon an order from the doctor. The counter on the display (e.g., “doses or puffs remaining”) will generally be decremented following use of the manual override.
The dispensing system 10 may include other features. For example, the dispensing system 10 may have a shutoff control to immediately cease the automated functions (for example, in an emergency situation). The shutoff control may be part of the operator interface panel 120 or may be a separate switch on the housing 10h.
The dispensing system 10 may also provide alarms for various events, such as when the unit 10 is malfunctioning (e.g., one or more components have stopped operating) or when the MDI canister 12 is depleted of medication or approaching this state. The alarms may be visible alarms on the display 120d and/or audible alarms. The alarms may be sent to one or more of a PDA, cell phone, notepad, or other device carried by a clinician such as a nurse and/or a monitoring station.
The dispensing system 10 may include certain features to enhance security and patient safety. For example, the operator may need to enter a password prior to operating the dispensing system 10. The password may be entered via UI controls on the operator interface panel 120, for example. The dispensing system 10 may also include or communicate with one or more identification devices and can include one or more optical or electronic devices. For example, the operator may be required to enter (e.g., swipe) or scan a badge or authorized key fob or other identification prior to operating the unit. The housing or other part of the dispensing system 10 can include an on-board reader that recognizes authorized users via biometrics, magnetic data strips, digital information memories and the like.
The dispensing system 10 can be configured for pre-defined product data for a particular patient. Thus, the MDI canister 12 may be electronically identified (e.g., via a bar code label) by the dispensing system 10 before or during installation in the housing 10 or before operation of the system 10 to help ensure the proper medication is being administered. For example, the system 10 can include an optical reader that electronically reads a label on the MDI canister (the MDI canister may need to be rotated to have the correct orientation before allowing automated dispensing). Other identification devices, such as RFID tags, may be implemented instead of bar codes. The system 10 may also store information about each MDI drug and about the patient so it can alert the operator to drug incompatibilities or to prevent programming an overdose and generally reduce drug administration errors.
Furthermore, the patient may be identified in a variety of ways prior to administering medication. For example, the system 10 can be programmatically locked, and the operator must identify the proper patient identification to unlock the unit housing 10h (e.g., after loading the canister 12). That is, the dispensing system 10 may be configured to have a patient-specific code that an operator must use to operate or change the MDIs in the housing 10h.
Other methods of automating and controlling the system 10 are contemplated. For example, the system 10 may include and/or communicate with a wireless handheld device (such as a PDA, cell phone, notepad or smartphone). The handheld device may be used along with, form the interface panel or be used with another user interface panel to input parameters such as the number and frequency of doses.
The dispensing system 10 can be provided using cloud computing which includes the provision of computational resources on demand via a computer network. The resources can be embodied as various infrastructure services (e.g., compute, storage, etc.) as well as applications, databases, file services, email, etc. In the traditional model of computing, both data and software are typically fully contained on the user's computer; in cloud computing, the user's computer may contain little software or data (perhaps an operating system and/or web browser), and may serve as little more than a display terminal for processes occurring on a network of external computers. A cloud computing service (or an aggregation of multiple cloud resources) may be generally referred to as the “Cloud”. Cloud storage may include a model of networked computer data storage where data is stored on multiple virtual servers, rather than being hosted on one or more dedicated servers.
The dispensing systems 10 may include a web portal that controls participant access. The web portal may be configured to be user-specific based on defined privacy or privilege levels of the user. That is, each web client can display a different web portal configuration and/or different web pages associated with a specific user type (showing different permissible actions, commands and data options). Where used, a server can provide a centralized administration and management application. The server can include or communicate with a plurality of databases including participant/user profiles, a security directory, routing security rules, and patient records.
As shown in
Another embodiment of an automated control and dispensing system 10′ is illustrated in
The dispensing systems 10, 10′ may include a memory, such as the memory 412 (
In the embodiments described above, medication from an MDI such as the MDI canister 12 is typically injected into the ventilator flow circuit 60c via the interior of the connector 16. In some other embodiments, the connector may take a different form.
In some embodiments, the dispensing system 10 may be designed with the option to allow the patient the ability to self-administer an unscheduled “puff” or dose of medication with a manual override control that may be attached to or integrated into a hospital bed or may be a device placed within reach of the patient P, such as a control with a depressible button or the like. The control may allow the patient P to self-administer an unscheduled “puff” or dose of medication whenever the patient P senses the need and without having to call a caregiver. This may be useful because mechanical ventilator patients generally cannot easily communicate their needs. For example, this feature may be useful for critical but non-sedated patients.
The system 10, 10′ may include safety control of patient-initiated drug dispensation within safe parameters as determined by a physician and/or programmed by the unit operator.
The dispensing system 10, 10′ may provide a diagnostic platform and may be used with patients in vivo. The systems 10, 10′ can provide for the administration of inhaled particles, whether they be small chemical agents, small peptide/proteins, whole organisms such as a virus vector, or a radioactive labeled particles (e.g., nucleotide/carbohydrate/gas) that can be thought of as a “drug or pharmaceutical agent.” This agent may be used for a clinical effect to measure, diagnose, and/or treat any physiologic process or condition by measuring the exhaled gas to make a physiological reading or measurement to determine a specific state or condition. The device 10, 10′ may then use the measured specific state based on the pre-determined/programmed protocol to automatically initiate specified care/treatment (e.g., inhaled antibiotics/inhaled steroids/radioactive gold particles or initiate ventilator weaning) in an automated fashion based on the disease state/condition and/or the physiologic parameter that is chosen to be measured. In various embodiments, the device 10, 10′ may be used for only administration purposes, for only detection purposes, and for both administration and detection purposes. In some embodiments, the detected condition or state may be displayed for a clinician or physician; for example, the detected condition or state may be displayed on a display 120d.
Techniques used to diagnose/measure in the device include but are not limited to gas chromatography/capillary GC, liquid chromatography (HPLC/UHPLC), multidimensional chromatography, DNA/RNA sequencing, biophotonic sensors/photometry, biospectroscopy, single cell/multicell flow cytometry, optical microscopy, optical analysis with remote and automated/televised monitoring, mass spectroscopy, IR spectroscopy, antibody labeled ELIZA, gas volitile and non-volitile analysis, small molecule/protein, peptide, carbohydrate hydrocarbon analysis, chemical vapor deposition, calimetry, bioluminensence/luminensence, ion exchange, or any other analytical bio/radio/histochemistry technique that could be used to measure exhaled breath condensate.
The dispensing systems 10, 10′ can include an optional exhaled gas sensor 135 (
A physiological reading or measurement (or exhaled gas measurement EGM) can be communicated from the sensor 135 to the controller 50. The controller or outside device can determine a specific state or condition of the patient based on the EGM. The controller may then adjust a medication dosing or timing based on the specific state or condition of the patient. The device 10 may include a display 120d which may display parameters related to the determined specific state or condition of the patient and/or the current medication dosing or frequency and/or any adjustment thereto.
The foregoing is illustrative of the present invention, and is not to be construed as limiting thereof. Although exemplary embodiments of this invention have been described, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this invention. As such, all such modifications are intended to be included within the scope of this invention. The scope of the invention is to be defined by the following claims.
This application is a divisional application of U.S. patent application Ser. No. 14/925,553, filed Oct. 28, 2015, which claims the benefit of and priority to U.S. Provisional Application Ser. No. 62/081,927 filed Nov. 19, 2014, the contents of which are hereby incorporated by reference as if recited in full herein.
Number | Name | Date | Kind |
---|---|---|---|
4558710 | Eichler | Dec 1985 | A |
4604093 | Brown et al. | Aug 1986 | A |
4819629 | Jonson | Apr 1989 | A |
4934358 | Nilsson et al. | Jun 1990 | A |
4984158 | Hillsman | Jan 1991 | A |
5002048 | Makiej, Jr. | Mar 1991 | A |
5020527 | Dessertine | Jun 1991 | A |
5103814 | Maher | Apr 1992 | A |
5178138 | Walstrom et al. | Jan 1993 | A |
5277175 | Riggs et al. | Jan 1994 | A |
5284133 | Burns et al. | Feb 1994 | A |
5297543 | Larson et al. | Mar 1994 | A |
5363842 | Mishelevich et al. | Nov 1994 | A |
5392768 | Johansson et al. | Feb 1995 | A |
5394866 | Ritson et al. | Mar 1995 | A |
5404871 | Goodman et al. | Apr 1995 | A |
5431154 | Seigel et al. | Jul 1995 | A |
5437267 | Weinstein et al. | Aug 1995 | A |
5438982 | MacIntyre | Aug 1995 | A |
5474058 | Lix | Dec 1995 | A |
5497764 | Ritson et al. | Mar 1996 | A |
5507277 | Rubsamen et al. | Apr 1996 | A |
5520166 | Ritson et al. | May 1996 | A |
5522378 | Ritson et al. | Jun 1996 | A |
5522385 | Lloyd et al. | Jun 1996 | A |
5542410 | Goodman et al. | Aug 1996 | A |
5544647 | Jewett et al. | Aug 1996 | A |
5560353 | Willemot et al. | Oct 1996 | A |
5564414 | Walker et al. | Oct 1996 | A |
5608647 | Rubsamen et al. | Mar 1997 | A |
5617844 | King | Apr 1997 | A |
5622162 | Johansson et al. | Apr 1997 | A |
5622163 | Jewett et al. | Apr 1997 | A |
5655516 | Goodman et al. | Aug 1997 | A |
5676129 | Rocci, Jr. et al. | Oct 1997 | A |
5694919 | Rubsamen et al. | Dec 1997 | A |
5724957 | Rubsamen et al. | Mar 1998 | A |
5738087 | King | Apr 1998 | A |
5743252 | Rubsamen et al. | Apr 1998 | A |
5755218 | Johansson et al. | May 1998 | A |
5770585 | Kaufman et al. | Jun 1998 | A |
5794612 | Wachter et al. | Aug 1998 | A |
5809997 | Wolf | Sep 1998 | A |
5826570 | Goodman et al. | Oct 1998 | A |
5881716 | Wirch et al. | Mar 1999 | A |
5967141 | Heinonen | Oct 1999 | A |
6012450 | Rubsamen | Jan 2000 | A |
6014972 | Sladek | Jan 2000 | A |
6079413 | Baran | Jun 2000 | A |
6116234 | Genova et al. | Sep 2000 | A |
6119684 | Nöhl et al. | Sep 2000 | A |
6123068 | Lloyd et al. | Sep 2000 | A |
6138669 | Rocci, Jr. et al. | Oct 2000 | A |
6148815 | Wolf | Nov 2000 | A |
6202642 | McKinnon et al. | Mar 2001 | B1 |
6223744 | Garon | May 2001 | B1 |
6237597 | Kovac | May 2001 | B1 |
6260549 | Sosiak | Jul 2001 | B1 |
6318361 | Sosiak | Nov 2001 | B1 |
6325062 | Sosiak | Dec 2001 | B1 |
6349724 | Burton et al. | Feb 2002 | B1 |
6358058 | Strupat et al. | Mar 2002 | B1 |
6390088 | Nöhl et al. | May 2002 | B1 |
6435175 | Stenzler | Aug 2002 | B1 |
6523536 | Fugelsang et al. | Feb 2003 | B2 |
6529446 | de la Huerga | Mar 2003 | B1 |
6550476 | Ryder | Apr 2003 | B1 |
6557552 | Cox et al. | May 2003 | B1 |
6588421 | Diehl et al. | Jul 2003 | B1 |
6595389 | Fuchs | Jul 2003 | B2 |
6598602 | Sjoholm | Jul 2003 | B1 |
6615825 | Stenzler | Sep 2003 | B2 |
6631716 | Robinson et al. | Oct 2003 | B1 |
6651844 | Tomaka et al. | Nov 2003 | B2 |
6681767 | Patton et al. | Jan 2004 | B1 |
6684880 | Trueba | Feb 2004 | B2 |
6705316 | Blythe et al. | Mar 2004 | B2 |
6725859 | Rothenberg et al. | Apr 2004 | B1 |
6830046 | Blakley et al. | Dec 2004 | B2 |
6871645 | Wartman et al. | Mar 2005 | B2 |
6951216 | Heinonen | Oct 2005 | B2 |
6962152 | Sladek | Nov 2005 | B1 |
7185648 | Rand | Mar 2007 | B1 |
7191777 | Band et al. | Mar 2007 | B2 |
7198044 | Trueba | Apr 2007 | B2 |
7201166 | Blaise et al. | Apr 2007 | B2 |
7201167 | Fink et al. | Apr 2007 | B2 |
7347200 | Jones et al. | Mar 2008 | B2 |
7347203 | Marler et al. | Mar 2008 | B2 |
7495546 | Lintell | Feb 2009 | B2 |
7549421 | Levi et al. | Jun 2009 | B2 |
7600511 | Power et al. | Oct 2009 | B2 |
7634995 | Grychowski et al. | Dec 2009 | B2 |
7748382 | Denyer et al. | Jul 2010 | B2 |
7905230 | Schuler et al. | Mar 2011 | B2 |
7921846 | Marler et al. | Apr 2011 | B1 |
8151794 | Meyer et al. | Apr 2012 | B2 |
8857429 | Spandorfer | Oct 2014 | B2 |
8869793 | Spandorfer et al. | Oct 2014 | B1 |
9737679 | Ritter, III et al. | Aug 2017 | B2 |
20020069869 | Farmer | Jun 2002 | A1 |
20020069870 | Farmer | Jun 2002 | A1 |
20030200964 | Blakley et al. | Oct 2003 | A1 |
20040069301 | Bacon | Apr 2004 | A1 |
20040084050 | Baran | May 2004 | A1 |
20040107961 | Trueba | Jun 2004 | A1 |
20040138577 | Kline | Jul 2004 | A1 |
20040231667 | Horton et al. | Nov 2004 | A1 |
20040255936 | Urbanus | Dec 2004 | A1 |
20050016528 | Aslin et al. | Jan 2005 | A1 |
20050039746 | Grychowski et al. | Feb 2005 | A1 |
20050139211 | Alson et al. | Jun 2005 | A1 |
20050183725 | Gumaste et al. | Aug 2005 | A1 |
20050235987 | Smaldone et al. | Oct 2005 | A1 |
20050268908 | Bonney et al. | Dec 2005 | A1 |
20050274378 | Bonney et al. | Dec 2005 | A1 |
20060021614 | Wermeling et al. | Feb 2006 | A1 |
20060254581 | Genova et al. | Nov 2006 | A1 |
20070151560 | Price et al. | Jul 2007 | A1 |
20070173731 | Meka et al. | Jul 2007 | A1 |
20080009761 | Acker et al. | Jan 2008 | A1 |
20080308101 | Spandorfer | Dec 2008 | A1 |
20090120431 | Borgschulte et al. | May 2009 | A1 |
20090137920 | Colman et al. | May 2009 | A1 |
20120055472 | Brunnberg et al. | Mar 2012 | A1 |
20120234321 | Power et al. | Sep 2012 | A1 |
20130008436 | Von Hollen et al. | Jan 2013 | A1 |
20140251330 | Collins et al. | Sep 2014 | A1 |
Number | Date | Country |
---|---|---|
2055046 | Feb 1981 | GB |
WO 9831413 | Jul 1998 | WO |
Entry |
---|
Ari et al., A Guide to Aerosol Delivery Devices for Respiratory Therapists, 2nd Edition, American Association for Respiratory Care, © 2009, Exemplary pp. 22, 24 and 34. |
Carrillo et al., The Development of an Automatic Metered Dose Inhaler, Vanderbilt University Department of BioMedical Engineering, 32 pages, Apr. 27, 2004. |
Carrillo et al., Automated Metered Dose Inhaler Presentation #5, Vanderbilt University Department of Engineering, 11 pages, dated Apr. 7, 2004. |
CircuVent® Ventilator Support Products, www.smiths-medical.com, printed from the internet Nov. 18, 2014, 9 pages. |
European Office Action Corresponding to European Patent Application No. 08770987.9; dated Feb. 28, 2014; 10 Pages. |
European Patent Office communication of a Decision to Grant a European Patent pursuant to Article 97(1) EPC corresponding to European Patent Application No. 08770987.9, 2 pp. (dated Nov. 17, 2016). |
International Search Report and Written Opinion for corresponding PCT Application No. PCT/US2008/066883, dated Oct. 1, 2008. |
OHMEDA Project: Automated Metered-Dose Inhaler Deliver Device, Biomedical Engineering Design Projects, College of Engineering University of Wisconsin-Madison, printed from http://homepages.cae.wisc.edu/, printed Jul. 3, 2008, 4 pages, final poster presentation and demo stated to be date May 10, 2002. |
Product Specification and Directions, Metered Dose Inhaler (MDI) Adapter, Instrumentation Industries, Inc., 2 pages, (Date of first publication unknown but for exam purposes only, is to be considered before the priority date of the instant application.) |
Number | Date | Country | |
---|---|---|---|
20200147332 A1 | May 2020 | US |
Number | Date | Country | |
---|---|---|---|
62081927 | Nov 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14925553 | Oct 2015 | US |
Child | 16734953 | US |