This document relates generally to medical device systems and particularly to a system providing for management of hospitalization of heart failure patients having implantable devices.
The heart is the center of a person's circulatory system. It includes an electro-mechanical system performing two major pumping functions. The left side of the heart, including the left atrium and left ventricle, draws oxygenated blood from the lungs and pumps it to various organs of the body to provide the organs with oxygen for their metabolic needs. This pumped blood flow is called the cardiac output. The right side of the heart, including the right atrium and right ventricle, draws deoxygenated blood from the organs and pumps it into the lungs where the blood gets oxygenated. The pumping functions are accomplished by contractions of the myocardium (heart muscles). In a normal heart, the sinoatrial node, the heart's natural pacemaker, generates electrical impulses, known as action potentials, that propagate through an electrical conduction system to various regions of the heart to excite myocardial tissues in these regions. Coordinated delays in the propagations of the action potentials in a normal electrical conduction system cause the various regions of the heart to contract in synchrony such that the pumping functions are performed efficiently.
A blocked or otherwise damaged electrical conduction system causes irregular contractions of the myocardium, a condition generally known as arrhythmia. Arrhythmia reduces the heart's pumping efficiency and hence, diminishes the cardiac output. The diminished cardiac output may also be caused by heart failure where the myocardial muscle is weakened and its contractility is reduced. A heart failure patient usually suffers from both a damaged electrical conduction system and a deteriorated myocardium. In response to the reduced cardiac output, the body attempts to adapt in a number of ways that lead to various symptoms as the heart failure condition progresses. The body retains salt and water as a result of reduced urinal output. The salt and water are then accumulated in the lung and/or in peripheral tissues. The water retention may also lead to acute pulmonary edema in which fluid leaks into the air sacs of the lung, causing the patient to gasp for breath. This condition can be fatal if not treated immediately. Another symptom of a patient with heart failure is fatigue on exertion. Once diagnosed with chronic heart failure, the patients is typically managed by interventions such as diet restriction and pharmacologic and/or device therapies. Such interventions keep the patient in a clinically stable state unless punctuated by episodes of acute heart failure decompensation. Acute heart failure decompensation is characterized by fluid overload and shortness of breath, and requires immediate treatment in a hospital or an outpatient clinical setting.
Heart failure has been recognized as a significant public health concern with a huge economic impact. Patients hospitalized with decompensated heart failure reportedly have a high rate of rehospitalization within six months (more than 50% according to some studies), with a significant percentage of them rehospitalized within a month. Hospital readmission is a principal factor responsible for the cost associated with managing heart failure. Premature hospital discharge and insufficient resolution of heart failure worsening are among the factors contributing to the high rate of rehospitalization. Therefore, there is a need to improve management of heart failure hospitalization for reducing the rate of rehospitalization.
A hospitalization management system including a heart failure analyzer that receives diagnostic data including at least sensor data representative of one or more physiological signals sensed from a hospitalized patient using one or more sensors and assesses risk of rehospitalization for the patient using the diagnostic data. The outcome of the risk assessment is used during and following the patient's hospitalization for reducing the risk of rehospitalization.
In one embodiment, a hospitalization management system includes one or more sensors, a sensor processing circuit, and a heart failure analyzer. The one or more sensors sense one or more physiological signals. The sensor processing circuit produces sensor data representative of the sensed one or more physiological signals. The heart failure analyzer includes a data input, a diagnostic data processor, a mode switch, and a risk analyzer. The data input receives diagnostic data indicative of one or more conditions associated with heart failure. The data input includes a sensor data input to receive the sensor data. The diagnostic data processor produces one or more parameters using the diagnostic data. The mode switch switches an operational mode of the heart failure analyzer to a hospitalization mode in response to a mode-change command. The risk analyzer produces a risk class parameter during the hospitalization mode. The risk class parameter classifies a level of risk for rehospitalization within a specified period using the one or more parameters.
In one embodiment, a method for operating a heart failure analyzer for managing hospitalization of a heart failure patient is provided. One or more physiological signals are sensed. Sensor data representative of the sensed one or more physiological signals are produced. Diagnostic data indicative of one or more conditions associated with heart failure, including the sensor data, are received. One or more parameters are produced using the diagnostic data. An operational mode of the heart failure analyzer is switched to a hospitalization mode in response to a mode-change command. A risk class parameter is produced using the one or more parameters during the hospitalization mode. The risk class parameter classifies a level of risk for rehospitalization.
This Summary is an overview of some of the teachings of the present application and not intended to be an exclusive or exhaustive therapy of the present subject matter. Further details about the present subject matter are found in the detailed description and appended claims. Other aspects of the invention will be apparent to persons skilled in the art upon reading and understanding the following detailed description and viewing the drawings that form a part thereof. The scope of the present invention is defined by the appended claims and their legal equivalents.
The drawings illustrate generally, by way of example, various embodiments discussed in the present document. The drawings are for illustrative purposes only and may not be to scale.
In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that the embodiments may be combined, or that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the scope of the present invention. The following detailed description provides examples, and the scope of the present invention is defined by the appended claims and their legal equivalents.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive or, unless otherwise indicated. Furthermore, all publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this documents and those documents so incorporated by reference, the usage in the incorporated reference(s) should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
It should be noted that references to “an”, “one”, or “various” embodiments in this document are not necessarily to the same embodiment, and such references contemplate more than one embodiment.
This document discusses a hospitalization management system that provides for management of heart failure patient including risk stratification using data acquired by a medical device implanted in the patient. Efforts have been to reduce the rate of hospitalization by, for example, assessing the risk of rehospitalization for a hospitalized patient by analyzing the patient's medical history and measurements made during hospitalization. Hospital discharge is planned based on the outcome of the risk assessment. Following the discharge, the patient is monitored for need of medical attention when certain symptoms occur. The present system automates such practice to allow them to be performed in a timely and consistent manner while the heart failure patient is in the hospital and following the patient's discharge from the hospital, thereby reducing the risk of rehospitalization and improving the patient's quality of life. In various embodiments, the present system analyzes physiological data acquired using one or more sensors implanted in the patient for therapy monitoring, risk stratification, and discharge planning during the hospitalization and for monitoring and intervention after the hospitalization. In one embodiment, the one or more sensors are part of an implantable CRM system implanted in the patient. The implantable CRM system communicates with an external patient management system that allows a physician or other caregiver to monitor, treat, and give instruction to the patient from a remote location.
In this document, “hospitalization” includes in-patient hospitalization and out-patient and clinical care. “Heart failure hospitalization” includes any hospital or clinical setting providing professional care for a heart failure patient, particularly when acute heart failure decompensation occurs.
Hospitalization management system 100 includes a heart failure analyzer 160 providing for hospitalization management of a heart failure patient using at least diagnostic data acquired by implantable system 105. Heart failure analyzer 160 analyzes the diagnostic data for therapy monitoring, risk stratification, and discharge planning during hospitalization of a heart failure patient and for monitoring and intervention after the hospitalization of the patient. In the illustrated embodiment, heart failure analyzer 160 is substantially included in implantable medical device 110. In another embodiment, heart failure analyzer 160 is substantially included in external system 125. In various embodiments, heart failure analyzer 160 is distributed in both implantable system 105 and external system 125. Heart failure analyzer 160 may be implemented using a combination of hardware and software. In various embodiments, each element of heart failure analyzer 160, including its specific embodiments, may be implemented using an application-specific circuit constructed to perform one or more particular functions or a general-purpose circuit programmed to perform such function(s). Such a general-purpose circuit includes, but is not limited to, a microprocessor or a portion thereof, a microcontroller or portions thereof, and a programmable logic circuit or a portion thereof. For example, a “timer” includes, among other things, an electronic circuit timer constructed to perform the only function of tracking time or a portion of a general-purpose circuit driven by a code instructing that portion of the general-purpose circuit to track time.
External system 225 represents an embodiment of external system 125 and includes a user interface 242, an external control circuit 244, an external telemetry circuit 246, and one or more external memory circuits 248. These components are each included in one or both of external device 120 and remote device 124. User interface 242 allows a user such as a physician or other caregiver to control hospitalization management system 100 and include a user input device 250 and a presentation device 252. User input device 250 receives commands and parameters from the user. Presentation device 252 includes a printer and/or a display screen to present to the user various information including information indicative of operation of hospitalization management system 100 and information acquired and/or stored in various portions of hospitalization management system 100. External control circuit 244 controls the operation of external system 225. External telemetry circuit 246 receives data from, and transmits data to, implantable medical device 210 via telemetry link 115. External memory circuit(s) 248 store data including external data representative of patient information. In one embodiment, the external data include data used in management of heart failure patients and data transmitted from one or more implantable or external medical devices (other than implantable medical device 210) as well as data received by user input device 250. Examples of such external data include therapy parameters such as drug dosage and pacing parameters, diagnostic test results such as laboratory test results and medical examination results, medical history information such as patient demographics and history of cardiac conditions including heart failure symptoms and recovery information.
In one embodiment, implant control circuit 236 includes heart failure analyzer 160. In another embodiment, external control circuit 244 includes heart failure analyzer 160. In another embodiment, implant control circuit 236 and external control circuit 244 each include portions of heart failure analyzer 160. Heart failure analyzer 160 receives a mode-change command and controls the operation of implantable medical device 210 and/or external system 225 according to an operational mode selected according to the mode-change command. In one embodiment, the operational mode is selected from a hospitalization mode, a post-hospitalization mode, and a non-hospitalization mode. These operational modes each correspond to a heart failure management algorithm applied to a patient depending on the hospitalization status of that patient.
Data input 362 receives diagnostic data indicative of one or more conditions associated with heart failure. In the illustrated embodiment, data input 362 includes a sensor data input 372 and an external data input 374. In other embodiments, data input 362 includes one or more of sensor data input 372 and external data input 374, depending on the need of the heart failure management algorithms executed by heart failure analyzer 360. Sensor data input 372 receives sensor data representative of one or more physiological signals sensed by sensor(s) 230 of implantable medical device 210. External data input 374 receives the external data representative of patient information from external system 225.
Diagnostic data processor 366 produces one or more parameters indicative of one or more conditions associated with heart failure using the diagnostic data received by data input 362. Examples of such one or more parameters include amplitude of third heart sounds (S3) produced using the heart sound signal, thoracic fluid volume produced using the thoracic impedance signal, respiration rate produced using the thoracic impedance signal, heart rate and heart rate variability produced using the one or more electrograms, and parameters indicative of various physiological responses to patient's physical activities. In one embodiment, diagnostic data processor 366 produces a parameter as a function of a plurality of sensed physiological signals and patient information represented by selected sensor data and external data received by data input 362. In one embodiment, diagnostic data processor 366 produces a trend using at least one of the one or more parameters. The trend is indicative of progression of heart failure, including an acute worsening of heart failure. An example of such a trend is illustrated in
Mode switch 364 switches the operational mode of heart failure analyzer 360 to one of a hospitalization mode, a post-hospitalization mode, and a non-hospitalization mode in response to a mode-change command. In the illustrated embodiment, mode switch 364 includes a mode selector 376 and a command receiver 378. In other embodiments, mode switch 364 includes any one or more of mode selector 376 and command receiver 378, depending on how heart failure analyzer 160 determines the hospitalization status of the patient. Mode selector 376 produces the mode-change command automatically using the one or more parameters produced by diagnostic data processor 366. Command receiver 378 receives the mode-change command from external system 225. In one embodiment, the mode-change command is entered by the user through user input device 250.
Heart failure management module 368 executes a heart failure management algorithm selected from one or more stored heart failure management algorithms according to the operational mode. Memory circuit 370 stores the one or more heart failure management algorithms, including at least a hospitalization algorithm that is to be executed while the patient is hospitalized. In one embodiment, memory circuit 370 stores a post-hospitalization algorithm in addition to the hospitalization algorithm. The post-hospitalization algorithm is to be executed during a post-hospitalization period after the discharge of the patient from the hospital. In another embodiment, memory circuit 370 stores a baseline algorithm in addition to the hospitalization algorithm and the post-hospitalization algorithm. The baseline algorithm is to be executed after the post-hospitalization period and before the patient is hospitalized.
During the non-hospitalization mode, parameter 400 indicates a degree of severity of heart failure that does not require hospitalization. When parameter 400 indicates that the patient is clinically stable (without symptoms indicating a substantially degree of decompensation for 30 days, for example), heart failure management module 368 establishes a baseline value 406 for parameter 400, using the one or more parameters produced using data acquired during the clinically stable period, by executing the baseline algorithm during the non-hospitalization mode. In one embodiment, data input 362 receives data selected according to the requirement of the baseline algorithm, and diagnostic data processor 366 produces parameter 400 using the selected data. In one embodiment, selected one or more physiological signals represented by the received data are smoothed with filters such as finite impulse response, infinite impulse response, and/or nonlinear filters. In another embodiment, regression analysis or curve fitting are used to estimate baseline value 406.
At 402, mode switch 364 switches the operational mode of heart failure analyzer 360 to the hospitalization mode from the non-hospitalization mode when parameter 400 exceeds a hospitalization threshold value, or when a user command is received following the patient's admission into a hospital. During the hospitalization mode, heart failure management module 368 analyzes therapy efficacy, produces therapy adjustment signals when necessary, and assesses risk of rehospitalization using parameter 400 by executing the hospitalization algorithm. In one embodiment, the therapy efficacy is analyzed by comparing parameter 400 to its expected value 410 that is determined according to one or more therapies applied to the patient. In various embodiments, the therapy adjustment signals are presented to the physician or other caregiver and/or result in automatic adjustment of therapy delivery. In one embodiment, data input 362 receives data selected according to the requirement of the hospitalization algorithm, and diagnostic data processor 366 produces parameter 400 using the selected data.
At 404, mode switch 364 switches the operational mode of heart failure analyzer 360 to the post-hospitalization mode from the hospitalization mode when parameter 400 decreases below a discharge threshold value, or when a user command is received after a decision to discharge the patient from the hospital is made. Readiness to discharge is determined by comparing one or more features extracted from parameter 400 during the hospitalization mode to corresponding one or more criteria statistically established using a patient population. Examples of such features include change of value of parameter 400 from baseline value 406, change of value of parameter 400 from its peak value prior to the hospitalization, a derivative of parameter 400, a frequency-domain feature of parameter 400, and a measure of variance of parameter 400. In one embodiment, as illustrated in
Baseline analyzer 580 is activated during the non-hospitalization mode and produces one or more baseline values of the one or more parameters produced by diagnostic data processor 366 when the patient is clinically stable. Heart failure is generally characterized by clinically stable periods punctuated by episodes of decompensation and hospitalization. The one or more baseline values of the one or more parameters are produced using the sensor data acquired when decompensation has not been detected for a specified period of time, such as 30 days.
Hospitalization alarm generator 582 produces a hospitalization alarm signal when the one or more parameters indicate a need for hospitalization during the non-hospitalization mode. In various embodiments, the hospitalization alarm signal is produced as a tone audible to the patient and/or transmitted to external system 225 for notifying the patient and/or the physician or other caregiver using presentation device 252. In one embodiment, hospitalization alarm generator 582 produces the hospitalization alarm signal by comparing at least one of the one or more parameters to a corresponding hospitalization threshold value. In another embodiment, hospitalization alarm generator 582 produces the hospitalization alarm signal by comparing a time derivative (slope) of at least one of the one or more parameters to a corresponding hospitalization threshold derivative value. In one embodiment, mode switch 364 switches the operational mode of heart failure analyzer 360 from the non-hospitalization mode to the hospitalization mode in response to the hospitalization alarm signal.
Therapy monitor 584 is activated during the hospitalization mode and analyzes efficacy of therapy using one or more parameters produced by diagnostic data processor 366 and one or more corresponding expected values of the one or more parameters associated with the one or more therapies applied. The one or more therapies are adjusted if the one or more parameters substantially deviate from the one or more expected values.
Risk analyzer 586 is activated during the hospitalization mode and produces a risk class parameter. The risk class parameter classifies a level of risk for rehospitalization. In one embodiment, the level of risk for rehospitalization is a probability of rehospitalization within a specified period of time, and risk analyzer 586 calculates this probability using an empirically established mathematical formula using the one or more parameters produced by diagnostic data processor 366. In one embodiment, risk analyzer 586 produces the risk class parameter by comparing at least a risk parameter selected from the one or more parameters produced by diagnostic data processor 366 to one or more risk threshold values associated with the risk parameter. In one embodiment, the risk threshold value is a function of the baseline value of the risk parameter. In another embodiment, risk analyzer 586 produces the risk class parameter by comparing a time derivative (slope) of at least one of the one or more parameters to one or more risk threshold derivative values associated with the risk parameter.
Discharge planning analyzer 588 produces a discharge recommendation signal using the risk class parameter during the hospitalization mode. In one embodiment, discharge planning analyzer 588 produces the discharge recommendation signal when the risk class parameter falls below a predetermined or programmed threshold. In one embodiment, mode switch 364 switches the operational mode of heart failure analyzer 360 from the hospitalization mode to the post hospitalization mode in response to the discharge recommendation signal.
Post-hospitalization monitor 590 is activated during the post-hospitalization mode. Post-hospitalization monitor 590 monitors the one or more parameters produced by diagnostic data processor 366 and produces signals indicative of need for medical intervention using the one or more parameters and predetermined and/or programmed criteria associated with the one or more parameters. The intervention may include adjustments of one or more factors affecting conditions associated with heart failure, such as therapy, diet, and daily activities. The adjustments of therapy include, for example, starting a therapy, stopping a therapy, and adjustment of therapy parameters such as drug dosage and pacing parameters. In one embodiment, the patient is monitored more closely in the post-hospitalization mode than in the non-hospitalization mode because the known elevated risk of hospitalization during the period of time (such as 180 days) following the hospitalization. This requires, for example, monitoring of more parameters representing physiological signals sensed by more sensors and analysis of more features extracted from the one or more parameters.
Rehospitalization alarm generator 592 produces a rehospitalization alarm signal when the one or more parameters produced by diagnostic data processor 366 indicate a need for rehospitalization during the post-hospitalization mode. In one embodiment, rehospitalization alarm generator 592 produces the rehospitalization alarm signal by comparing at least one of the one or more parameters to a corresponding rehospitalization threshold value. In another embodiment, rehospitalization alarm generator 592 produces the rehospitalization alarm signal by comparing a time derivative of at least one of the one or more parameters to a corresponding rehospitalization threshold derivative value. In one embodiment, mode switch 364 switches the operational mode of heart failure analyzer 360 from the post-hospitalization mode to the hospitalization mode in response to the rehospitalization alarm signal.
Post-hospitalization timer 594 times a post-hospitalization period that starts with the post-hospitalization mode. In one embodiment, the post-hospitalization period is a predetermined period. In another embodiment, the post-hospitalization period is programmable, such as using user input device 250. In one embodiment, mode switch 364 switches the operational mode of heart failure analyzer 360 from the post-hospitalization mode to the non-hospitalization mode in response to the expiration of the post-hospitalization period.
At 610, the hospitalization management system enters the non-hospitalization mode. In one embodiment, the hospitalization management system enters each of its operational modes in response to a mode-change command received from a user. In another embodiment, the hospitalization management system enters each of its operational modes in response to a mode-change command produced automatically using patient information including at least a physiological signal sensed from the patient. The hospitalization management system selects a heart failure management algorithm upon entering each of its operational modes and executes that algorithm during the operational mode. During the non-hospitalization mode, the hospitalization management system executes a baseline algorithm.
At 612, diagnostic data indicative of one or more conditions associated with heart failure are received. The diagnostic data include sensor data representative of one or more physiological signals sensed by one or more implantable sensors being part of or communicatively coupled to an implantable medical device of the hospitalization management system. In one embodiment, diagnostic data further include external data representative of patient information stored an external system communicatively coupled to the implantable medical device. In one embodiment, the diagnostic data received during each operational mode include input data required to execute the heart failure management algorithm selected for that operational mode.
At 614, one or more parameters are produced using the diagnostic data. In one embodiment, the selected heart failure management algorithm determines which one or more parameters are produced during each operational mode.
At 616, one or more baseline values for the one or more parameters are established. In one embodiment, a baseline value for each of the one or more parameters is produced using baseline data including sensor data representative of the one or more sensor signals sensed by the one or more implantable sensors within a clinically stable period (when decompensation is not detected) during the non-hospitalization mode.
At 618, whether the patient needs hospitalization is determined. In one embodiment, whether the patient needs hospitalization is determined by comparing at least one of the one or more parameters to a corresponding hospitalization threshold value. In another embodiment, whether the patient needs hospitalization is determined by comparing a time derivative (slope) of at least one of the one or more parameters to a corresponding hospitalization threshold derivative value. In one embodiment, in response to each determination that the patient needs hospitalization, a hospitalization alarm signal is produced.
At 630, the hospitalization management system enters to hospitalization mode after the determination that the patient needs hospitalization is made at 618. If the patient does not need hospitalization as determined at 618, the hospitalization management system remains in the non-hospitalization mode. In one embodiment, the operational mode is switched from the non-hospitalization mode to the hospitalization mode in response to the determination that the patient needs hospitalization (such as in response to the hospitalization alarm signal). In another embodiment, the operational mode is switched from the non-hospitalization mode to the hospitalization mode in response to the mode-change command entered by a physician or other caregiver upon the patient's admission into a hospital. During the hospitalization mode, the hospitalization management system executes a hospitalization algorithm.
At 632, the diagnostic data are received according to the requirement for executing the hospitalization algorithm. At 634, the one or more parameters are produced using the diagnostic data according to the hospitalization algorithm. In various embodiments, the diagnostic data received and the one or more parameters produced during different operational modes may be substantially identical or substantially different, depending on the need for patient monitoring and availability of types of data. In one embodiment, a trend indicative of progression of heart failure is produced using at least one of the one or more parameters. The trend indicates acute worsening of heart failure. In one embodiment, the trend is presented to the physician or other caregiver using a display screen and/or a printer. In one embodiment, the trend is the trend of a parameter being a function of the sensor data and the external data.
At 636, therapy efficacy is monitored, and therapy is adjusted when needed in response to the outcome of the monitoring. The efficacy of therapy administrated during the hospitalization mode is analyzed by comparing the one or more parameters to the corresponding expected values of the one or more parameters. The expected values represent the predicted response of the patient to the therapy. In one embodiment, the therapy delivered includes one or more of an anti-bradycardia pacing therapy, an anti-tachycardia pacing therapy, a defibrillation therapy, a cardiac resynchronization therapy, and a neurostimulation therapy.
At 638, a risk class parameter is produced. The risk class parameter classifies a level of risk for rehospitalization. In one embodiment, the risk class parameter represents the probability of rehospitalization within a specified period. In one embodiment, the risk class parameter is produced by comparing at least one of the one or more parameters to one or more risk threshold values associated with the risk parameter. In another embodiment, the risk class parameter is produced by comparing a time derivative (slope) of at least a risk parameter of the one or more parameters with one or more risk threshold derivative values associated with the risk parameter.
At 640, whether the patient is ready to be discharged from the hospital is determined using the risk class parameter. In one embodiment, in response to a determination that the patient is ready to be discharged, a discharge recommendation signal is produced and presented to the physician or other caregiver.
At 650, the hospitalization management system enters a post-hospitalization mode after the determination that the patient is ready to be discharged at 640. If the patient is not ready to be discharged as determined at 640, the hospitalization management system remains in the hospitalization mode. In one embodiment, the operational mode is switched from the hospitalization mode to the post hospitalization mode in response to the determination that the patient is ready to be discharged (such as in response to the discharge recommendation signal). In another embodiment, the operational mode is switched from the non-hospitalization mode to the hospitalization mode in response to the mode-change command entered by the physician or other caregiver before the patient leaves the hospital. During the post-hospitalization mode, the hospitalization management system executes a post-hospitalization algorithm.
At 652, the diagnostic data are received according to the requirement for executing the post-hospitalization algorithm. At 654, the one or more parameters are produced using the diagnostic data according to the post-hospitalization algorithm.
At 656, the one or more parameters are monitored, and a need for intervention is signaled, when needed, in response to the outcome of the monitoring. Signals indicative of need for intervention are produced during the post-hospitalization mode when the one or more parameters indicate such need according to predetermined and/or programmed criteria. Examples of such intervention include adjustments of one or more factors affecting conditions associated with heart failure, such as therapy parameters, diet, and daily activities.
At 658, whether the patient needs rehospitalization is determined. In one embodiment, whether the patient needs rehospitalization is determined by comparing at least one of the one or more parameters to a corresponding rehospitalization threshold value. In another embodiment, whether the patient needs rehospitalization is determined by comparing a time derivative of at least one of the one or more parameters to a corresponding rehospitalization threshold derivative value. In one embodiment, a rehospitalization alarm signal is produced when the one or more parameters indicate a need for rehospitalization.
In response to a determination that the patients needs rehospitalization at 658, the patient is to be rehospitalized, and the operational mode of the hospitalization management system reenters the hospitalization mode at 630. In one embodiment, the operational mode is switched from the post-hospitalization mode to the hospitalization mode in response to the rehospitalization alarm signal. In another embodiment, the operational mode is switched from the non-hospitalization mode to the hospitalization mode in response to the mode-change command entered by the physician or other caregiver upon the patient's readmission into the hospital.
A post-hospitalization period is started when the hospitalization management system enters the post-hospitalization mode and is timed during the post-hospitalization mode. At 660, if the post-hospitalization period has expired, the operational mode is switched from the post-hospitalization mode to the non-hospitalization mode.
It is to be understood that the above detailed description is intended to be illustrative, and not restrictive. Other embodiments will be apparent to those of skill in the art upon reading and understanding the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
This application is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 14/814,135, filed on Jul. 30, 2015, which is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 14/166,417, filed on Jan. 28, 2014, now issued as U.S. Pat. No. 9,138,151, which is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 13/668,659, filed on Nov. 5, 2012, now issued as U.S. Pat. No. 8,708,924, which is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 13/279,517, filed on Oct. 24, 2011, now issued as U.S. Pat. No. 8,303,513, which is a continuation of and claims the benefit of priority under 35 U.S.C. § 120 to U.S. patent application Ser. No. 11/685,949, filed on Mar. 14, 2007, now issued as U.S. Pat. No. 8,052,611, which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4562841 | Brockway et al. | Jan 1986 | A |
4697591 | Lekholm et al. | Oct 1987 | A |
4928688 | Mower | May 1990 | A |
5036849 | Hauck et al. | Aug 1991 | A |
5063927 | Webb et al. | Nov 1991 | A |
5133353 | Hauser | Jul 1992 | A |
5179945 | Van Hofwegen et al. | Jan 1993 | A |
5203348 | Dahl et al. | Apr 1993 | A |
5230337 | Dahl et al. | Jul 1993 | A |
5271395 | Wahlstrand et al. | Dec 1993 | A |
5284136 | Hauck et al. | Feb 1994 | A |
5301677 | Hsung | Apr 1994 | A |
5313953 | Yomtov et al. | May 1994 | A |
5314459 | Swanson et al. | May 1994 | A |
5318597 | Hauck et al. | Jun 1994 | A |
5334222 | Salo et al. | Aug 1994 | A |
5360442 | Dahl et al. | Nov 1994 | A |
5366496 | Dahl et al. | Nov 1994 | A |
5372606 | Lang et al. | Dec 1994 | A |
5376106 | Stahmann et al. | Dec 1994 | A |
5388578 | Yomtov et al. | Feb 1995 | A |
5391200 | KenKnight et al. | Feb 1995 | A |
5397342 | Heil, Jr. et al. | Mar 1995 | A |
5411031 | Yomtov | May 1995 | A |
5411525 | Swanson et al. | May 1995 | A |
5468254 | Hahn et al. | Nov 1995 | A |
5540727 | Tockman et al. | Jul 1996 | A |
5545202 | Dahl et al. | Aug 1996 | A |
5593431 | Sheldon | Jan 1997 | A |
5603732 | Dahl et al. | Feb 1997 | A |
5620466 | Haefner et al. | Apr 1997 | A |
5634938 | Swanson et al. | Jun 1997 | A |
5662688 | Haefner et al. | Sep 1997 | A |
5697953 | Kroll et al. | Dec 1997 | A |
5738102 | Lemelson | Apr 1998 | A |
5836987 | Baumann et al. | Nov 1998 | A |
5876353 | Riff | Mar 1999 | A |
5916243 | KenKnight et al. | Jun 1999 | A |
5957861 | Combs et al. | Sep 1999 | A |
5974340 | Kadhiresan | Oct 1999 | A |
5974349 | Levine | Oct 1999 | A |
6026320 | Carlson et al. | Feb 2000 | A |
6044297 | Sheldon et al. | Mar 2000 | A |
6044298 | Salo et al. | Mar 2000 | A |
6055454 | Heemels | Apr 2000 | A |
6073046 | Patel et al. | Jun 2000 | A |
6076015 | Hartley et al. | Jun 2000 | A |
6162183 | Hoover | Dec 2000 | A |
6203495 | Bardy | Mar 2001 | B1 |
6221011 | Bardy | Apr 2001 | B1 |
6261230 | Bardy | Jul 2001 | B1 |
6270457 | Bardy | Aug 2001 | B1 |
6275727 | Hopper et al. | Aug 2001 | B1 |
6277072 | Bardy | Aug 2001 | B1 |
6280380 | Bardy | Aug 2001 | B1 |
6285907 | Kramer et al. | Sep 2001 | B1 |
6312378 | Bardy | Nov 2001 | B1 |
6336903 | Bardy | Jan 2002 | B1 |
6358203 | Bardy | Mar 2002 | B2 |
6360127 | Ding et al. | Mar 2002 | B1 |
6368284 | Bardy | Apr 2002 | B1 |
6371922 | Baumann et al. | Apr 2002 | B1 |
6398728 | Bardy | Jun 2002 | B1 |
6409675 | Turcott | Jun 2002 | B1 |
6411848 | Kramer et al. | Jun 2002 | B2 |
6424865 | Ding | Jul 2002 | B1 |
6438407 | Ousdigian et al. | Aug 2002 | B1 |
6438408 | Mulligan et al. | Aug 2002 | B1 |
6438410 | Hsu et al. | Aug 2002 | B2 |
6440066 | Bardy | Aug 2002 | B1 |
6449509 | Park | Sep 2002 | B1 |
6454719 | Greenhut | Sep 2002 | B1 |
6459929 | Hopper et al. | Oct 2002 | B1 |
6473640 | Erlebacher | Oct 2002 | B1 |
6480733 | Turcott | Nov 2002 | B1 |
6513532 | Mault et al. | Feb 2003 | B2 |
6527729 | Turcott | Mar 2003 | B1 |
6542775 | Ding et al. | Apr 2003 | B2 |
6564106 | Guck et al. | May 2003 | B2 |
6572557 | Tchou et al. | Jun 2003 | B2 |
6579242 | Bui et al. | Jun 2003 | B2 |
6589188 | Street et al. | Jul 2003 | B1 |
6597951 | Kramer et al. | Jul 2003 | B2 |
6600949 | Turcott | Jul 2003 | B1 |
6607485 | Bardy | Aug 2003 | B2 |
6641542 | Cho et al. | Nov 2003 | B2 |
6645153 | Kroll et al. | Nov 2003 | B2 |
6650939 | Taepke, II et al. | Nov 2003 | B2 |
6658292 | Kroll et al. | Dec 2003 | B2 |
6666826 | Salo et al. | Dec 2003 | B2 |
6705990 | Gallant et al. | Mar 2004 | B1 |
6708058 | Kim et al. | Mar 2004 | B2 |
6738667 | Deno et al. | May 2004 | B2 |
6741885 | Park et al. | May 2004 | B1 |
6752765 | Jensen et al. | Jun 2004 | B1 |
6773404 | Poezevera | Aug 2004 | B2 |
6811537 | Bardy | Nov 2004 | B2 |
6827690 | Bardy | Dec 2004 | B2 |
6829503 | Alt | Dec 2004 | B2 |
6830548 | Bonnet et al. | Dec 2004 | B2 |
6832113 | Belalcazar | Dec 2004 | B2 |
6852080 | Bardy | Feb 2005 | B2 |
6856829 | Ohsaki et al. | Feb 2005 | B2 |
6860897 | Bardy | Mar 2005 | B2 |
6866629 | Bardy | Mar 2005 | B2 |
6869404 | Schulhauser et al. | Mar 2005 | B2 |
6887201 | Bardy | May 2005 | B2 |
6893397 | Bardy | May 2005 | B2 |
6905463 | Bardy | Jun 2005 | B2 |
6908431 | Bardy | Jun 2005 | B2 |
6908437 | Bardy | Jun 2005 | B2 |
6913577 | Bardy | Jul 2005 | B2 |
6922587 | Weinberg | Jul 2005 | B2 |
6945934 | Bardy | Sep 2005 | B2 |
6960167 | Bardy | Nov 2005 | B2 |
6961615 | Kroll et al. | Nov 2005 | B2 |
6974413 | Bardy | Dec 2005 | B2 |
6993389 | Ding et al. | Jan 2006 | B2 |
7013176 | Ding et al. | Mar 2006 | B2 |
7020521 | Brewer et al. | Mar 2006 | B1 |
7035684 | Lee | Apr 2006 | B2 |
7041061 | Kramer et al. | May 2006 | B2 |
7070562 | Bardy | Jul 2006 | B2 |
7096064 | Deno et al. | Aug 2006 | B2 |
7104955 | Bardy | Sep 2006 | B2 |
7113823 | Yonce et al. | Sep 2006 | B2 |
7115096 | Siejko et al. | Oct 2006 | B2 |
7127290 | Girouard et al. | Oct 2006 | B2 |
7158830 | Yu et al. | Jan 2007 | B2 |
7181285 | Lindh et al. | Feb 2007 | B2 |
7206634 | Ding et al. | Apr 2007 | B2 |
7228174 | Burnes et al. | Jun 2007 | B2 |
7306564 | Nakatani et al. | Dec 2007 | B2 |
7310554 | Kramer et al. | Dec 2007 | B2 |
7343199 | Hatlestad et al. | Mar 2008 | B2 |
7376457 | Ross | May 2008 | B2 |
7389141 | Hall et al. | Jun 2008 | B2 |
7409244 | Salo et al. | Aug 2008 | B2 |
7435221 | Bharmi et al. | Oct 2008 | B1 |
7468032 | Stahmann et al. | Dec 2008 | B2 |
7480528 | Brockway et al. | Jan 2009 | B2 |
7483743 | Mann et al. | Jan 2009 | B2 |
7499750 | Haefner et al. | Mar 2009 | B2 |
7572225 | Stahmann | Aug 2009 | B2 |
7606617 | Wariar | Oct 2009 | B2 |
7662105 | Hatlestad et al. | Feb 2010 | B2 |
7680534 | Hopper et al. | Mar 2010 | B2 |
7803118 | Reisfeld et al. | Sep 2010 | B2 |
8052611 | Wariar et al. | Nov 2011 | B2 |
8303513 | Wariar et al. | Nov 2012 | B2 |
8708924 | Wariar et al. | Apr 2014 | B2 |
20040006278 | Webb et al. | Jan 2004 | A1 |
20040116819 | Alt | Jun 2004 | A1 |
20040122294 | Hatlestad et al. | Jun 2004 | A1 |
20040127792 | Siejko et al. | Jul 2004 | A1 |
20040133079 | Mazar et al. | Jul 2004 | A1 |
20040230230 | Lindstrom et al. | Nov 2004 | A1 |
20050085738 | Stahmann et al. | Apr 2005 | A1 |
20050137629 | Dyjach et al. | Jun 2005 | A1 |
20050216067 | Min et al. | Sep 2005 | A1 |
20050234355 | Rowlandson | Oct 2005 | A1 |
20050256545 | Koh et al. | Nov 2005 | A1 |
20060020295 | Brockway et al. | Jan 2006 | A1 |
20060167516 | Kjellstrom et al. | Jul 2006 | A1 |
20070055115 | Kwok et al. | Mar 2007 | A1 |
20070073168 | Zhang et al. | Mar 2007 | A1 |
20070083241 | Bardy | Apr 2007 | A1 |
20070118183 | Gelfand et al. | May 2007 | A1 |
20070135725 | Hatlestad | Jun 2007 | A1 |
20070149862 | Pipke | Jun 2007 | A1 |
20070191697 | Lynn et al. | Aug 2007 | A1 |
20070208266 | Hadley | Sep 2007 | A1 |
20070213621 | Reisfeld et al. | Sep 2007 | A1 |
20080114219 | Zhang et al. | May 2008 | A1 |
20080162182 | Cazares et al. | Jul 2008 | A1 |
20080228090 | Wariar et al. | Sep 2008 | A1 |
20080262360 | Dalal et al. | Oct 2008 | A1 |
20080312541 | Lewicke et al. | Dec 2008 | A1 |
20090198139 | Lewicke et al. | Aug 2009 | A1 |
20090234240 | Kuenzler et al. | Sep 2009 | A1 |
20090324034 | Watson et al. | Dec 2009 | A1 |
20100073170 | Siejko et al. | Mar 2010 | A1 |
20100191076 | Lewicke et al. | Jul 2010 | A1 |
20100198097 | Sowelam | Aug 2010 | A1 |
20110009760 | Zhang et al. | Jan 2011 | A1 |
20120041325 | Wariar et al. | Feb 2012 | A1 |
20130060151 | Wariar et al. | Mar 2013 | A1 |
20140142440 | Wariar et al. | May 2014 | A1 |
20150335255 | Wariar et al. | Nov 2015 | A1 |
Number | Date | Country |
---|---|---|
1151719 | Nov 2001 | EP |
1177764 | Feb 2002 | EP |
119705 | Jan 1999 | JP |
2000005145 | Jan 2000 | JP |
2001185238 | Jul 2001 | JP |
2003220039 | Aug 2003 | JP |
2005515043 | May 2005 | JP |
2007502670 | Feb 2007 | JP |
2007503286 | Feb 2007 | JP |
2007537777 | Dec 2007 | JP |
WO-9602185 | Feb 1996 | WO |
WO-9833553 | Aug 1998 | WO |
WO-0240096 | May 2002 | WO |
WO-03075744 | Sep 2003 | WO |
WO-2004062485 | Jul 2004 | WO |
WO-05028029 | Mar 2005 | WO |
WO-2008085309 | Jul 2008 | WO |
Entry |
---|
“U.S. Appl. No. 11/300,675, Final Office Action dated Aug. 5, 2009”, 9 pgs. |
“U.S. Appl. No. 11/300,675, Non Final Office Action dated Jan. 24, 2008”, 12 pgs. |
“U.S. Appl. No. 11/300,675, Notice of Allowance dated Oct. 6, 2009”, 6 pgs. |
“U.S. Appl. No. 11/300,675, Response filed Feb. 2, 2009 to Restriction Requirement dated Dec. 31, 2008”, 7 pgs. |
“U.S. Appl. No. 11/300,675, Response filed Apr. 23, 2008 to Non Final Office Action dated Jan. 24, 2008”, 10 pgs. |
“U.S. Appl. No. 11/300,675, Response filed Sep. 16, 2008 to Restriction Requirement dated Aug. 25, 2008”, 7 pgs. |
“U.S. Appl. No. 11/300,675, Response filed Sep. 7, 2009 to Final Office Action dated Aug. 5, 2009”, 7 pgs. |
“U.S. Appl. No. 11/300,675, Response filed Dec. 19, 2007 to Restriction Requirement dated Oct. 30, 2007”, 5 pgs. |
“U.S. Appl. No. 11/300,675, Restriction Requirement dated Aug. 25, 2008”, 5 pgs. |
“U.S. Appl. No. 11/300,675, Restriction Requirement dated Oct. 30, 2017”, 6 pgs. |
“U.S. Appl. No. 11/300,675, Restriction Requirement dated Dec. 31, 2008”, 8 pgs. |
“U.S. Appl. No. 11/685,949, Response to Restriction Requirement filed Apr. 8, 2010”, 10 pgs. |
“U.S. Appl. No. 11/685,949, Non Final Office Action dated Jan. 25, 2011”, 9 pgs. |
“U.S. Appl. No. 11/685,949, Notice of Allowance dated Jul. 8, 2011”, 5 pgs. |
“U.S. Appl. No. 11/685,949, Response filed May 18, 2011 to Non Final Office Action dated Jan. 25, 2011 ”, 13 pgs. |
“U.S. Appl. No. 11/685,949, Restriction Requirement dated Mar. 9, 2010”, 5 pgs. |
“U.S. Appl. No. 12/787,789, Advisory Action dated Mar. 27, 2015”, 3 pgs. |
“U.S. Appl. No. 12/787,789, Advisory Action dated Dec. 30, 2013”, 3 pgs. |
“U.S. Appl. No. 12/787,789, Final Office Action dated Jul. 5, 2013”, 15 pgs. |
“U.S. Appl. No. 12/787,789, Final Office Action dated Dec. 4, 2014”, 18 pgs. |
“U.S. Appl. No. 12/787,789, Non Final Office Action dated May 8, 2014”, 16 pgs. |
“U.S. Appl. No. 12/787,789, Non Final Office Action dated Dec. 20, 2012”, 15 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Mar. 4, 2015 to Final Office Action dated Dec. 4, 2015”, 12 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Apr. 6, 2015 to Final Office Action dated Dec. 4, 2015”, 14 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Apr. 18, 2013 to Non Final Office Action dated Dec. 20, 2012”, 12 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Aug. 8, 2014 to Non Final Office Action dated May 8, 2015”, 12 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Oct. 22, 2012 to Restriction Requirement dated Oct. 12, 2012”, 7 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Nov. 26, 2013 to Final Office Action dated Jul. 5, 2013”, 12 pgs. |
“U.S. Appl. No. 12/787,789, Restriction Requirement dated Oct. 12, 2012”, 7 pgs. |
“U.S. Appl. No. 13/279,517 , Response filed Jun. 19, 2012 to Non Final Office Action dated Apr. 3, 2012”, 9 pgs. |
“U.S. Appl. No. 13/279,517, Non Final Office Action dated Apr. 3, 2012”, 4 pgs. |
“U.S. Appl. No. 13/279,517, Notice of Allowance dated Jul. 9, 2012”, 7 pgs. |
“U.S. Appl. No. 13/668,659 , Response filed Nov. 21, 2013 to Non Final Office Action dated Aug. 23, 2013”, 8 pgs. |
“U.S. Appl. No. 13/668,659, Non Final Office Action dated Aug. 23, 2013”, 6 pgs. |
“U.S. Appl. No. 13/668,659, Notice of Allowance dated Dec. 10, 2013”, 8 pgs. |
“U.S. Appl. No. 13/668,659, Response fied Feb. 6, 2013 to Restriction Requirement dated Jan. 18, 2013”, 7 pgs. |
“U.S. Appl. No. 13/668,659, Restriction Requirement dated Jan. 18, 2013”, 5 pgs. |
“U.S. Appl. No. 14/166,417, Non Final Office Action dated Mar. 21, 2014”, 5 pgs. |
“U.S. Appl. No. 14/166,417, Notice of Allowance dated Jan. 21, 2015”, 6 pgs. |
“U.S. Appl. No. 14/166,417, Notice of Allowance dated May 29, 2015”, 7 pgs. |
“U.S. Appl. No. 14/166,417, Response filed Jun. 23, 2014 to Non Final Office Action dated Mar. 21, 2014”, 9 pgs. |
“U.S. Appl. No. 14/814,135, Notice of Allowance dated Apr. 12, 2017”, 5 pgs. |
“U.S. Appl. No. 14/814,135, Preliminary Amendment filed Jul. 31, 2015”, 7 pgs. |
“Australian Application Serial No. 2009206541, First Examiner Report dated May 5, 2011”, 3 pgs. |
“Definition of window”, [online]. (c) 2009 Dictionary.com, LLC. [retrieved on Apr. 12, 2009]. Retrieved From the Internet: <URL: http://dictionary.refernce.com/browse/window>, (2009), 8 pgs. |
“File History for European Application No. 09704414.3”, Retrieved from the European Patent Office Electronic File System on May 27, 2011, 147 pgs. |
“File History for European Application No. 10721084.1”, Retrieved from the European Patent Office Electronic File System on Aug. 15, 2012, 43 pgs. |
“File History for U.S. Appl. No. 12/356,289”, Retrieved from the U.S. Patent and Trademark Office. |
“International Application Serial No. PCT/US2010/036386, International Search Report dated Nov. 3, 2010”, 6 pgs. |
“International Application Serial No. PCT/US2010/036386, Written Opinion dated Nov. 3, 2010”, 7 pgs. |
“Japanese Application Serial No. 2010-543304, Office Action dated May 8, 2012”, 5 pgs. |
“Japanese Application Serial No. 2010-543304, Office Action dated Sep. 25, 2012”, 4 pgs. |
Altshule, M. D., et al., “The Effect of Position on Periodic Breathing in Chronic Cardiac Decomposition”, New Eng. Journal of Med., 259(22), (1958), 1064-1066. |
Butler, J., et al., “Beta-Blocker Use and Outcomes Among Hospitalized Heart Failure Patients”, Journal of the American College of Cardiology, 47(12), (2006), 2462-2469. |
Dark, D. S., et al., “Breathing Pattern Abnormalities and Arterial Oxygen Desaturation During Sleep in the Congestive Heart Failure Syndrome”, Chest, 91(6), (1987), 833-836. |
Dimopolou, I., et al., “Pattern of Breathing during Progressive Exercise in Chronic Heart Failure”, (Abstract), Int. J. Cardiol., 81(2-3), 117-121, (2001), 3 pgs. |
Duguet, A., et al., “Expiratory Flow Limitation as a Determinant of Orthopnea in Acute Left Heart Failure”, Journal of the American College of Cardiology, 35(3), (2000), 690-700. |
Felker, G. M., et al., “Risk stratification after hospitalization for decompensated heart failure”, J Card Fail., 10(6), (Dec. 2004), 460-6. |
Felker, G. M., et al., “The problem of decompensated heart failure: nomenclature, classification, and risk stratification”, Am Heart J., 145(2 Suppl), (Feb. 2003), S18-25. |
Heidenreich, P. A., et al., “Health status identifies heart failure outpatients at risk for hospitalization or death”, J Am Coll Cardiol., 47(4), (Feb. 21, 2006), 752-6. |
Hoffman, R., et al., “Cheyne-Stokes Respiration in Patients Recovering from Acute Cardiogenic Pulmonary Edema”, Chest, 97, (1990), 410-412. |
Jaarsma, T., et al., “Readmission of older heart failure patients”, Prog Cardiovasc Nurs., 11(1), (Winter, 1996), 15-20. |
Lee, D. S., et al., “Predicting Mortality Among Patients Hospitalized for Heart Failure: Derivation and Validation of a Clinical Model”, JAMA, 290(19), (2003), 2581-2587. |
Mai, Junyu, et al., “Posture Detection Algorithm Using Multi Axis DC-Accelerometer”, Pace, vol. 22, Part II, (Apr. 1999), 851. |
Rame, J. E, et al., “Outcomes after emergency department discharge with a primary diagnosis of heart failure”, American Heart Journal, 142(4), (Oct. 2001), 714-719. |
Rees, P. J., et al., “Paroxysmal Nocturnal Dyspnoea and Periodic Respiration”, (Abstract), The Lancet, 314(8156), 1315-1317, (1979), 1315-1317. |
Solin, P., et al., “Effects of Cardiac Dysfunction on Non-Hypercapnic Central Sleep Apnea”, Chest, 113, (1998), 104-110. |
Tkacova, R., et al., “Left Ventricular Volume in Patients with Heart Failure and Cheyne-Strokes Respiration during Sleep”, Am Journal, Respir. Crit. Care Med., 156, (1997), 1549-1555. |
“U.S. Appl. No. 12/787,789, Advisory Action dated Jul. 21, 2016”, 4 pgs. |
“U.S. Appl. No. 12/787,789, Advisory Action dated Aug. 1, 2017”, 3 pgs. |
“U.S. Appl. No. 12/787,789, Examiner Interview Summary dated May 20, 2015”, 3 pgs. |
“U.S. Appl. No. 12/787,789, Examiner Interview Summary dated Aug. 11, 2017”, 3 pgs. |
“U.S. Appl. No. 12/787,789, Final Office Action dated Mar. 22, 2016”, 20 pgs. |
“U.S. Appl. No. 12/787,789, Final Office Action dated May 19, 2017”, 26 pgs. |
“U.S. Appl. No. 12/787,789, Non Final Office Action dated Sep. 22, 2015”, 18 pgs. |
“U.S. Appl. No. 12/787,789, Non Final Office Action dated Oct. 5, 2016”, 25 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Jan. 5, 2017 to Non Final Office Action dated Oct. 5, 2016”, 22 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Jun. 21, 2016 to Final Office Action dated Mar. 22, 2016”, 15 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Jul. 18, 2017 to Final Office Action dated May 19, 2017”, 18 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Aug. 22, 2016 to Final Office Action dated Mar. 22, 2016”, 18 pgs. |
“U.S. Appl. No. 12/787,789, Response filed Dec. 15, 2015 to Sep. 22, 2015”, 17 pgs. |
Number | Date | Country | |
---|---|---|---|
20170303797 A1 | Oct 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14814135 | Jul 2015 | US |
Child | 15646846 | US | |
Parent | 14166417 | Jan 2014 | US |
Child | 14814135 | US | |
Parent | 13668659 | Nov 2012 | US |
Child | 14166417 | US | |
Parent | 13279517 | Oct 2011 | US |
Child | 13668659 | US | |
Parent | 11685949 | Mar 2007 | US |
Child | 13279517 | US |