The present subject matter relates to implantable devices and more specifically, to a method and system for optimizing performance of an implanted medical device based on contextual information derived from the implanted medical device, external sensors, user provided data, or other sources.
A normal, healthy, heart beats at a regular rate. Irregular heart beats, known as cardiac arrhythmia, on the other hand, may characterize an unhealthy condition. Another unhealthy condition is known as congestive heart failure (ACHF@). CHF, also known as heart failure, is a condition where the heart has inadequate capacity to pump sufficient blood to meet metabolic demand. CHF may be caused by a variety of sources, including, coronary artery disease, myocardial infarction, high blood pressure, heart valve disease, cardiomyopathy, congenital heart disease, endocarditis, myocarditis, and others.
Unhealthy heart conditions may be treated using a cardiac rhythm management (CRM) system. Examples of CRM systems, or pulse generator systems, include defibrillators (including implantable cardioverter defibrillator), pacemakers and other cardiac resynchronization devices.
Typically, a pulse generator is surgically implanted under the skin, but outside the thorax of a patient and includes one or more conductive lead wires that deliver an electrical pulse to the heart according to a therapy schedule. The electrical pulses may be delivered on a predetermined schedule, on an as needed basis, or according to other predetermined criteria.
In some cases, the operation of the pulse generator may be adjusted using an external programmer. The programmer allows a physician to tailor the performance of the pulse generator without performing surgery on the patient. The programmer may communicate with the pulse generator by wireless technology such as radio frequency communication.
A typical programmer includes a wand coupled to a desktop unit by a flexible electrical cord. In use, the operator positions the wand near the implanted device and a signal from the programmer is wirelessly transmitted to the device. Data is extracted from the transmitted signal and stored in internal memory within the implanted device. The implanted device then delivers therapy according to the memory contents. The memory contents may include operating parameters or programming. For example, the implanted device may be wirelessly programmed to deliver electrical shocks at a greater amplitude or with greater frequency.
The ability to wirelessly program an implantable device has taxed the performance and capacity of device data storage and the device power supply and also compelled the addition of a transceiver suitable for communicating with the programmer. To address these needs, some manufacturers have adapted their devices to include additional circuitry as well as increased battery capacity. To the chagrin of the patient, such improvements have, in some instances, resulted in larger case sizes for the implantable device.
Consumer, and therefore, manufacturers, of implanted medical devices have demonstrated a clear desire for, among other things, reduced device size, increased functionality, and increased reliability and longevity. Efforts to provide increased functionality and increased reliability have tended to frustrate the objective of reduced device size. Thus, there is a need for an implanted device with reduced size and yet permits field programmability along with increased reliability.
At initial implantation, the medical device is programmed to provide therapy based on known parameters and conditions of the patient. Follow-up programming of the implanted device, which may take place at a doctor's office, may be based on stored data and patient input. However, for many patients, follow-up visits are infrequent and thus, patients are unable to provide their physician with accurate or complete information regarding the events surrounding a particular cardiac event. For example, few patients are able to provide reliable data concerning their dietary intake just prior to a period of increased heart rate that may have occurred three weeks ago. Thus, there is a need for collecting timely patient data with improved accuracy.
The present subject matter includes, among other things, a system and method for collecting timely data from a variety of sources and correlating the data with data provided by an implanted medical device. In one embodiment, patient responses are collected using a portable device. The portable device may present questions or data entry prompts or otherwise solicit a response from the patient. The prompts may concern subjective or objective data. In one embodiment, the questions include “Have you felt dizzy in the last two hours?,” “Are you breathless?,” “Do you feel palpitations?,” “Do you have any chest pain?” and “How many alcoholic drinks have you consumed in the previous 2 hours?” In one embodiment, data from a sensor coupled to the implanted medical device is communicated to the portable device. The data includes physiological information concerning the performance of the implanted medical device or measured parameters concerning a particular body organ or system. In one embodiment, data from a sensor not coupled to the implanted medical device is communicated to the portable device.
By way of example, in one embodiment, the patient is implanted with a medical device as part of a cardiac rhythm management (CRM) system. The CRM system includes a pacemaker defibrillator with an accelerometer and heart rhythm sensor. In addition, the patient is also fitted with an implanted respiration monitor with in the CRM system. In this example, the portable device, which is carried external from the body of the patient, prompts the patient with questions concerning such topics as their sleep patterns, dietary and drug intake, visible edema and other relevant signs and symptoms. The portable device also receives data from the defibrillator with the accelerometer, heart rhythm monitor and the respiration monitor.
At a clinical setting, or by a remote communication coupling, the patient's doctor can access the portable device and retrieve the stored data from the various inputs. The retrieved data can be analyzed for trends as part of a wellness monitoring system and therefore, enable improved medical care and reduce healthcare utilization.
In one embodiment, the portable device is coupled to, or incorporated within a personal digital assistant (PDA). Thus, the PDA communicates wirelessly with an implanted medical device as well as communicates with a programmer. In addition, the portable device is adapted to execute instructions that prompts the user for information and stores the responses. In one embodiment, the user entered data is received in response to a prompt or message. In one embodiment, the user is able to enter data in a free-text entry mode without regard to a particular schedule. In one embodiment, the portable device also receives data from non-invasive sensors or detectors. Examples of non-invasive sensors include an arterial blood pressure monitor, a respiration monitor, a blood sugar detector, a body mass scale as well as other devices. The portable device communicates with the non-invasive sensors or detectors in a wireless manner or via a wired coupling.
In one embodiment, the portable device may receive data from an implanted device other than that which is controllable by way of the programmer. For example, a patient may be equipped with an implanted cardiac pacing device as well as a separate implanted sensor for monitoring a body parameter or organ and the portable device receives data from both implanted devices and yet the programmer interfaces with and controls the operation of the cardiac pacing device and not the separate implanted sensor.
In various embodiments, the portable device is coupled to a PDA, (variously referred to as a personal digital, or data, assistant), a portable telephone (including a cellular telephone or a cordless telephone), a pager (one way or two way), a handheld, palm-top, laptop, portable or notebook computer, or other such battery operated portable communication device, all of which are herein referred to as portable communicators.
In one embodiment, the portable device operates independently and without coupling to a portable communicator. It will be appreciated that either the portable device or the portable communicator may provide the data storage capacity, processing, display, or user input means as described herein.
In one embodiment, the portable device includes circuitry or executable programming and communicates wirelessly with the implanted medical device. In one embodiment, the portable device is coupled by a wired link to a remote programmer or other network communication device. In one embodiment, the device includes a separate module that communicates wirelessly with the implantable medical device and the separate module is user-removable from the portable device.
The present subject matter also includes a method and apparatus to allow a portable communicator, such as a PDA or cellular telephone, to interface between an implantable medical device and a programmer. The programmer may be coupled to the portable device by a network communication connection. For example, in one embodiment, a remote programmer can access a cellular telephone coupled to a portable device via the Internet, a private area branch exchange (PABX, also known as a PBX), an intranet network, an ethernet connection or other remote communication means. In one embodiment, the portable device is coupled to a portable telephone with which the programmer communicates using a public switched telephone network (PSTN) and the portable telephone is in wireless communication with the implantable medical device.
The present system may allow increased data logging, thereby permitting analysis otherwise not possible using the limited data storage capacity and battery capacity of an implanted device.
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 spirit and scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents. In the drawings, like numerals describe substantially similar components throughout the several views. Like numerals having different letter suffixes represent different instances of substantially similar components. As used herein, the term data includes both data and programming.
In accordance with the present system,
In one embodiment, implantable medical device 25 provides data including heart rhythm, breathing, activity, and contractility, as illustrated at 450. Other types of data derived from implantable systems are also contemplated, as noted at 450. For example, in one embodiment, a respiration sensor is implanted into patient 455 and communicates with portable device 35. Data received from such implantable systems may be perceived as involuntary, or passive, data since the patient has no control over the process of collecting and transmitting the data from such sources.
In one embodiment, portable communicator 80 includes a touch-sensitive display screen for displaying information to a user or patient 455. Depending on the application executing on portable communicator 80, the display screen may provide prompts, messages, questions, or other data designed to elicit an input from patient 455. For example, in one embodiment, portable communicator 80 may display a screen shot as shown at 400. Screen shot 400, entitled “Non-invasive Data Entry Screen” provides links to questions or prompts as shown in the figure. Data received from such interactive prompts may be perceived as voluntary, or active, data since the cooperation and active input of the patient is part of the data collection process. The user voluntarily provides answers in response to prompts that appear on the screen. At each of 405 through 445, the patient may be linked to one or more questions concerning the general topic appearing in screen shot 400. For example, at 405, the link “Blood Pressure” may lead to one or more questions concerning the patient's blood pressure. At 410, the patient may be prompted for information concerning their body weight. At 415 the patient may be prompted to supply data concerning their sleep patterns (bedtime, sleep time, perceived arousals, perceived sleep quality) or recent life experiences. At 420, the patient may be prompted for data concerning their perceived quality of life (Q of L). At 425, the patient may be prompted to supply information concerning their perceived physical strength. At 430, the patient may be prompted to supply information regarding their mental acuity. In one embodiment, the patient may be presented with a series of short questions and based on the responses received, portable communicator 80 calculates a parameter corresponding to mental acuity. At 435, the patient is prompted for data concerning their dietary intake. At 440, the patient is prompted for data concerning their voiding patterns. At 445, the patient is prompted to supply information concerning drug therapy compliance.
Wellness monitoring system 460 is in communication with portable communicator 80, and thus, portable device 35. Wellness monitoring system 460 provides analysis of voluntary and involuntary data gathered by portable device 35. In one embodiment, wellness monitoring system 460 includes computer and programming that conducts data analysis and identifies trends that may improve patient health and medical care.
In one embodiment, lead 20 includes a catheter or other implanted lead having one or more electrodes for the delivery of electrical energy to selected portions of an organ, or tissue, of a patient or for receiving electrical signals indicative of the health of the patient or a selected organ. In one embodiment, lead 20 is coupled to a human or animal heart, however, other organs may also be monitored or treated. In one embodiment, the housing of IMD 25 is electrically conductive and serves as an electrical conductor and operates in conjunction with a signal on a conductor portion of lead 20.
In one embodiment, IMD 25 includes a pacing device (commonly referred to as a pacemaker) a defibrillator, heart failure therapy device, cardiac resynchronization device or other medical device. In one embodiment, IMD 25 also includes circuitry and programming adapted to monitor the condition and performance of the pulse generator or other implanted device. For example, in one embodiment, IMD 25 provides data concerning the remaining battery condition for a power supply coupled to IMD 25. Such data may include information regarding remaining battery capacity or life, battery internal resistance or other measurable parameter. In other embodiments the data includes information regarding the electrical therapy provided by IMD 25. For example, in one embodiment, such data includes the peak voltage level, the rate, or frequency, of therapy, the profile of the delivered shock or other parameters. In various embodiments, IMD 25 is controlled by digital or analog signals and in one embodiment, IMD 25 generates data in digital or analog form.
In one embodiment, IMD 25 includes a program executing on an internal processor that controls the operation of the device. The program instructions reside in a memory accessible to the internal processor. By changing the program, or memory contents, the present system allows the operating program of IMD 25 to be dynamically tailored to a particular patient or condition. In one embodiment, the operating system, or memory contents of IMD 25 can be changed using wireless communication.
In one embodiment, IMD 25 includes a wireless transceiver. The transceiver operates using radio frequency transmissions, electromagnetic transmissions, magnetic coupling, inductive coupling, optical coupling, or other means of communicating without need of a wire connection between IMD 25 and another transceiver. In one embodiment, IMD 25 is coupled to a wireless transceiver by a wired connection.
In one embodiment, IMD 25 performs a data acquisition function. For example, a detector coupled to IMD 25 is adapted to monitor a fluid pressure, such as blood or urine. In one embodiment, the detector is adapted to monitor respiration, stress level, or other measurable biometric parameter. In one embodiment, monitoring includes determining an absolute or relative value for a particular biometric parameter. Internal memory within IMD 25 may be adapted to store a comparison value which may then be compared with a measured value thereby determining the performance of IMD 25 or the health of the patient.
Link 30 is a wireless communication link between IMD 25 and portable device 35. Link 30 allows communication in one or two directions. For example, in one embodiment, data from IMD 25 is communicated to portable device 35 with no data transmitted from portable device 35 to IMD 25. In this manner, portable device 35 functions as a data storage facility for IMD 25. In one embodiment, data stored in portable device 35 can be accessed by a treating physician and used for diagnosis, therapy or other purposes. Programming and controlling the operation of IMD 25 is performed using a programmer adapted to transmit commands, data or code to IMD 25. In one embodiment, portable device 35, or portable communicator 80, executes programming to analyze and process the data received from IMD 25. In one embodiment, communication link 30 may preclude transfer of data from portable device 35 to IMD 25 or to preclude transfer of data from IMD 25 to portable device 35. For example, in one embodiment, portable device 35 executes programming which automatically adjusts the performance or operation of IMD 25 independent of programmer 45 and under certain predetermined conditions, it may be desirable to preclude such automatic adjustments.
In one embodiment, data is communicated from portable device 35 to IMD 25 with no data transmitted from IMD 25 to portable device 35. In this manner, portable device 35 functions as an interface to communicate commands, data or code to IMD 25.
In one embodiment, data is communicated bidirectionally between IMD 25 and portable device 35. In various embodiments, link 30 entails a single bidirectional communication channel or includes multiple unidirectional communication channels which, when viewed as a whole, provide bidirectional communication. In one embodiment, a unidirectional communication channel operates using a particular frequency or communication protocol. For example, link 30 include a wireless radio frequency link compatible with a transmitter and receiver that uses frequency hopping, spread spectrum technology.
In one embodiment, internal memory within IMD 25 provides storage for data related to the CRM therapy provided to heart 15. The data may relate to the electrical, chemical or mechanical operation of the heart. In addition, IMD 25 includes memory for programming, comparison and other functions. In one embodiment, the contents of the memory regulates the operation of IMD 25.
In one embodiment, portable device 35 is coupled to a battery operated portable communicator having a processor, memory, and an output interface to communicate with a user and an input interface to receive user entered data. One suitable example of a portable communicator is that of a PDA. Commercial suppliers of PDAs include Palm, Inc. (Santa Clara, Calif.), Microsoft Corporation (Redmond, Wash.) and Handspring Inc., (Mountain View, Calif.) and others. Such devices typically include a display screen for presenting visual information to a user and a writing surface for entry of data using a stylus. Data may also be entered using a keyboard coupled to the portable communicator or by means of a wired or wireless communication link. Some portable communicator models also include an audio transducer, or sound generator, adapted to produce sounds that are audible by a user. In one embodiment, data from IMD 25 or programmer 45 is displayed on a screen coupled to portable device 35.
In one embodiment, portable device 35 is coupled to a portable telephone (such as a cellular telephone or a cordless telephone), a pager (one way or two way), or a computer (such as a handheld, palm-top, laptop, or notebook computer) or other such battery operated, processor based, portable communication device.
In one embodiment, portable device 35, or portable communicator 80, includes data storage and includes programming and instructions to conduct data processing. In one embodiment, the data storage capacity of portable device 35 or portable communicator 80 augments the data storage capacity of IMD 25, thus enabling a clinician to access a greater amount of contextual information regarding the medical condition of a user. For example, but not by way of limitation, the contextual information may assist in discovering and understanding relationships among different events.
In one embodiment, a wireless receiver is coupled to portable device 35 for purposes of receiving data from IMD 25. The wireless receiver may be internal or external to the housing of portable device 35. In one embodiment, a wireless transmitter is coupled to portable device 35 for purposes of transmitting data to IMD 25. The wireless transmitter may be internal or external to the housing of portable communicator 80. In one embodiment, a wireless transceiver is coupled to portable device 35 for purposes of both transmitting data to, and receiving data from, IMD 25. The wireless transceiver may be internal or external to the housing of portable device 35. In one embodiment, portable device 35 includes a telemetry head that is positioned near IMD 25 to facilitate wireless communications.
In one embodiment, circuitry or programming allows portable device 35 to trigger an alarm under predetermined conditions. For example, portable device 35 may sound an audible alarm or transmit an alarm signal if a biometric parameter exceeds a particular value or is outside a specified range of values. The alarm signal can be received by programmer 45 or a designated physician.
Referring again to
In one embodiment, programmer 45 includes a processor based apparatus executing programming to communicate with IMD 25, portable device 35, or both. Typically, a clinician or physician will operate programmer 45 to communicate with IMD 25 using portable device 35 as a data interface. In particular, one embodiment provides that data from IMD 25 can be retrieved by accessing the memory of portable device 35. In one embodiment, programmer 45 transmits data to IMD 25 via portable device 35.
To the extent that IMD 25A, portable device 35A, programmer 45A, link 30A, and link 40A are described elsewhere in this document, the following discussion concerns the elements not earlier described.
IMD 25A is coupled to programmer 45A via wireless link 30B. In one embodiment, link 30B include a handheld wand that is placed in the vicinity of IMD 25A to allow communication of data. In the figure, link 30B is shown to include a bidirectional communication channel.
Portable device 35A is coupled to programmer 45A via network 50 by way of link 40B and link 40C. It will be appreciated that network 50 may include the Internet, a private intranet, a wide area network (WAN), a local area network (LAN), or other communication network. In one embodiment, programmer 45A accesses network 50 using an ethernet connection, a dial-up connection, a cable modem connection, a digital subscriber line (DSL) connection, or other wired or wireless network connection. In one embodiment, portable device 35A accesses network 50 using an ethernet connection, a dial-up connection, a cable modem connection, a digital subscriber line (DSL) connection, or other wired or wireless network connection.
Portable device 35A is coupled to a block modeled in the figure as involuntary data source 58. Involuntary data source 58, in one embodiment, includes IMD 25A and ex-IMD data source 55, either of which can provide data to enable system 10A to tailor therapy of IMD 25 in an efficient manner. As described above, IMD 25A may include sensors that provide information, ultimately, to programmer 45A. In addition, in one embodiment, ex-IMD data source 55 may include an externally worn sensor or an implanted device. In one embodiment, an implanted device includes a second implanted medical device adapted to monitor a body organ or function, such as a blood oxygen monitor. Also by way of example, one externally worn sensor includes a non-invasive data source such as a temperature monitor, blood pressure monitor or respiration monitor. In one embodiment, ex-IMD data source 55 is non-user worn. For example, in one embodiment, data is provided by an ambient temperature monitor or atmospheric pressure monitor. In one embodiment, a plurality of ex-IMD data sources 55 are provided. Data sources other than those enumerated herein are also contemplated.
Data provided by ex-IMD data source 55 is coupled to portable device 35A by link 60. In one embodiment, link 60 includes a wired coupling and in another embodiment, a wireless coupling. In one embodiment, ex-IMD data source 55 is coupled to, and integrated with, portable device 35A.
The data provided by ex-IMD data source 55 is received by portable device 35A. In various embodiments, processing of the data is conducted by portable device 35A or programmer 45A. In one embodiment, the data is provided in real time, (either continuously or according to a predetermined schedule) or upon a change exceeding a predetermined amount, or upon request or inquiry from programmer 45A or portable device 35A.
Portable device 35A is coupled to a block modeled in the figure as user data source 65, by link 70. In one embodiment, user data source 65 provides data volunteered by the user and is integrated with portable device 35A. User data source 65 includes, in one embodiment, a display screen, an audio generator and an input device. In operation, portable device 35A displays a question or prompt directed to the user and the user is instructed to respond by providing a manual input. For example, in one embodiment, portable device 35A sounds a characteristic tone and display a question concerning the well-being of a user. The user, in response to the prompt, may use a stylus, keyboard, voice response, or other means to indicate a suitable answer to the question presented. The data received from the user prompt is then stored by portable device 35A. In one embodiment, processing of the data received from user data source 65 is done by portable device 35A or by programmer 45A. User data source 65 may generate a prompt according to a predetermined schedule, randomly, or based on data received from portable device 35A, IMD 25 or environmental data source 55. In one embodiment, data is entered by the user on the user's initiative.
In one embodiment, programmer 45A receives data from several data sources and communicated via any of several data communication channels. For example, programmer 45A may receive data from IMD 25A via link 30B or via portable device 35A by way of link 30A and link 40A. In addition, programmer 45A may receive data from IMD 25A via network 50 by way of link 30A, link 40B and link 40C. Data may be acquired using an interrupt driven system or on a query-based system.
In addition, one embodiment provides that data from IMD 25A is communicated to programmer 45A via any of several communication paths. For example, data may be communicated to programmer 45A using link 40A, 40B, 40C, 60 or 70.
Consider the operation of the embodiment in
In addition to data entry, in one embodiment, stylus 80C, along with screen 80B, and buttons 80D, allow a user to exercise limited control over the operation of implantable medical device 25. In one embodiment, reasonable constraints on the authority to change the operation of device 25 are established and implemented by a clinician using programmer 45.
Programmer 45 accesses Internet 50A via link 40C. In one embodiment, link 40C includes a dial-up modem connection, a cable modem connection, a DSL connection, an ISDN line, or other channel providing access to the Internet.
Using the system of
Using the system of
Input/output 125, IMD transceiver 135 and communication interface 140, in conjunction with controller 130 enables receipt and transmission of data from IMD 25 as well as data from programmer 45. IMD transceiver 135 and transceiver 115 provide a wireless telemetric link between IMD 25 and portable device 35.
Portable device 35 may be coupled to a portable communicator and one or more of long term data 120, input/output 125, controller 130, IMD transceiver 135, or communication interface 140 may be provided by the portable communicator.
Programmer 45 receives data from portable device 35 via link 40E. In one embodiment, programmer 45 performs data processing. Updated programming for execution by IMD 25 is determined by programmer 45 and transmitted wirelessly to IMD 25 via link 30D. Updated programming may be based on data received from portable device 35, as well as manual inputs received at programmer 45. IMD 25 includes a transmitter to communicate using link 30C and a receiver to communicate using link 30D.
In the embodiment illustrated in
In the embodiment illustrated in
In the embodiment illustrated in
At 155, the input data includes a sleep schedule. The sleep schedule may describe the sleep (or wake) times of the user. The user may enter the data into portable device 35. In an embodiment including portable device 35 coupled to portable communicator 80, the data may be entered, for example, using stylus 80C, keys 80D or a keyboard. At 160, the input data includes a user-selected quality of life index. The user may select and specify a suitable response based on subjective or objective criteria. At 165, the input data includes an entry corresponding to the user's physical strength. At 170, the input data includes an entry corresponding to the mental acuity of the user. In this instance, portable communicator 80 may determine a value based on predetermined criteria which may entail analysis of a series of user entered responses. At 175, the input data includes information concerning the recent dietary intake of the user. Data may include caloric content, nutritional content (sodium levels), quantity and type of foods. At 180, the input data may include user provided data concerning voiding patterns or behavior. At 190, the input data may include drug intake or medicine compliance information. At 195, the input data may include alcohol consumption information such as quantity, type and time of intake. At 200, the input data may include transient illness information concerning such matters as time of onset, symptoms, treatment and recovery. At 205, the input data may include miscellaneous predictive input information. For example, the user may enter data to indicate that he will soon be walking or running or otherwise exercising. Other input data may also be provided depending upon the circumstances of the patient. The user input information may be tailored by the treating physician using programmer 45 and portable device 35. For example, the data collection protocol may be tailored to reduce battery consumption by prompting the user for a response at a reduced frequency.
At 215, the external device includes a blood pressure monitor. Encoded blood pressure information for the patient is provided as a function of time or other measured parameter. At 220, the external device includes an objective measure of the patient's quality of life. In one embodiment, this may entail a sensor adapted to correlate with quality of life. At 225, the external device includes a temperature monitor. Encoded temperature information is provided as a function of time or other measured parameter. The measured temperature may correspond to a body temperature, an ambient temperature, or other temperature. At 230, an external device provides data concerning the sleep time of the patient. The device may include a monitor coupled to a clock or a monitor coupled to another device corresponding to sleep time and sleep phase variation.
At 240, the implantable device includes a heart rhythm monitor. At 245, the implantable device includes a respiration monitor. At 250, the implantable device includes an activity monitor. At 255, the implantable device includes a contractility measurement device.
In one embodiment, a security protocol is implemented. The security protocol may assure authorized access for communications between programmer 45 and the portable device 35. In addition, one embodiment provides secure communications between portable device 35 and IMD 25. Authorization may be limited to reading data or reading and editing data. Security may entail a password and username system, encryption, or other biometric authentication system to prevent unauthorized access.
The present system provides data that may be useful in trend analysis, and thus, improve health care for a patient. For example, the present system may allow monitoring of device performance over an extended duration. Long term device performance data may facilitate improved therapy. In addition, the present system may allow cost-effective compilation of patient medical data. Such historical data may prove beneficial in developing treatment protocols for the patient.
Although the invention has been described in conjunction with the foregoing specific embodiments, many alternatives, variations, and modifications will be apparent to those of ordinary skill in the art. Other such alternatives, variations, and modifications are intended to fall within the scope of the following appended claims.
This application is a Continuation of U.S. application Ser. No. 12/891,338, filed on Sep. 27, 2010, now issued as U.S. Pat. No. 8,160,716, which is a Continuation of U.S. application Ser. No. 11/381,051, filed on May 1, 2006, now issued as U.S. Pat. No. 7,805,199, which is a Continuation of U.S. application Ser. No. 10/093,353 filed on Mar. 6, 2002, now issued as U.S. Pat. No. 7,043,305, which are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4310003 | Schlager | Jan 1982 | A |
4519395 | Hrushesky | May 1985 | A |
4712179 | Heimer | Dec 1987 | A |
4777960 | Berger et al. | Oct 1988 | A |
4796634 | Huntsman et al. | Jan 1989 | A |
4809697 | Causey, III et al. | Mar 1989 | A |
4825869 | Sasmor et al. | May 1989 | A |
4838275 | Lee | Jun 1989 | A |
4928688 | Mower | May 1990 | A |
4967749 | Cohen | Nov 1990 | A |
5031629 | DeMarzo | Jul 1991 | A |
5047930 | Martens et al. | Sep 1991 | A |
5097831 | Lekholm | Mar 1992 | A |
5113869 | Nappholz et al. | May 1992 | A |
5174289 | Cohen | Dec 1992 | A |
5226413 | Bennett et al. | Jul 1993 | A |
5251626 | Nickolls et al. | Oct 1993 | A |
5262944 | Weisner et al. | Nov 1993 | A |
5282838 | Hauser et al. | Feb 1994 | A |
5292341 | Snell | Mar 1994 | A |
5309919 | Snell et al. | May 1994 | A |
5311449 | Adams | May 1994 | A |
5311873 | Savard et al. | May 1994 | A |
5321618 | Gessman | Jun 1994 | A |
5372607 | Stone et al. | Dec 1994 | A |
5421830 | Epstein et al. | Jun 1995 | A |
5540727 | Tockman et al. | Jul 1996 | A |
5549654 | Powell | Aug 1996 | A |
5594638 | Iliff | Jan 1997 | A |
5607460 | Kroll et al. | Mar 1997 | A |
5613495 | Mills et al. | Mar 1997 | A |
5626630 | Markowitz et al. | May 1997 | A |
5630835 | Brownlee | May 1997 | A |
5690690 | Nappholz et al. | Nov 1997 | A |
5693076 | Kaemmerer | Dec 1997 | A |
5697959 | Poore | Dec 1997 | A |
5716382 | Snell | Feb 1998 | A |
5720771 | Snell | Feb 1998 | A |
5722999 | Snell | Mar 1998 | A |
5724985 | Snell et al. | Mar 1998 | A |
5731296 | Sollevi | Mar 1998 | A |
5759199 | Snell et al. | Jun 1998 | A |
5790534 | Kokko et al. | Aug 1998 | A |
5792064 | Panescu et al. | Aug 1998 | A |
5800473 | Faisandier | Sep 1998 | A |
5833623 | Mann et al. | Nov 1998 | A |
5860918 | Schradi et al. | Jan 1999 | A |
5873894 | Vandegriff et al. | Feb 1999 | A |
5891178 | Mann et al. | Apr 1999 | A |
5911132 | Sloane et al. | Jun 1999 | A |
5935078 | Feierbach | Aug 1999 | A |
5935081 | Kadhiresan | Aug 1999 | A |
5942986 | Shabot et al. | Aug 1999 | A |
5970986 | Bolz et al. | Oct 1999 | A |
5995939 | Berman et al. | Nov 1999 | A |
6001060 | Churchill et al. | Dec 1999 | A |
6006132 | Tacker, Jr. et al. | Dec 1999 | A |
6015388 | Sackner et al. | Jan 2000 | A |
6016442 | Hsu et al. | Jan 2000 | A |
6024089 | Wallace et al. | Feb 2000 | A |
6024699 | Surwit et al. | Feb 2000 | A |
6045513 | Stone et al. | Apr 2000 | A |
6070101 | Struble et al. | May 2000 | A |
6073048 | Kieval et al. | Jun 2000 | A |
6076015 | Hartley et al. | Jun 2000 | A |
6091990 | Hsu et al. | Jul 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6102874 | Stone et al. | Aug 2000 | A |
6115630 | Stadler et al. | Sep 2000 | A |
6168563 | Brown | Jan 2001 | B1 |
6190324 | Kieval et al. | Feb 2001 | B1 |
6240317 | Villaseca et al. | May 2001 | B1 |
6249703 | Stanton et al. | Jun 2001 | B1 |
6250309 | Krichen et al. | Jun 2001 | B1 |
6263245 | Snell et al. | Jul 2001 | B1 |
6275727 | Hopper et al. | Aug 2001 | B1 |
6280409 | Stone et al. | Aug 2001 | B1 |
6304773 | Taylor et al. | Oct 2001 | B1 |
6312378 | Bardy | Nov 2001 | B1 |
6331160 | Bardy | Dec 2001 | B1 |
6336900 | Alleckson et al. | Jan 2002 | B1 |
6336903 | Bardy | Jan 2002 | B1 |
6351675 | Tholen et al. | Feb 2002 | B1 |
6363282 | Nichols et al. | Mar 2002 | B1 |
6368284 | Bardy | Apr 2002 | B1 |
6381496 | Meadows et al. | Apr 2002 | B1 |
6383136 | Jordan | May 2002 | B1 |
6398728 | Bardy | Jun 2002 | B1 |
6411840 | Bardy | Jun 2002 | B1 |
6411847 | Mower | Jun 2002 | B1 |
6416471 | Kumar et al. | Jul 2002 | B1 |
6434429 | Kraus et al. | Aug 2002 | B1 |
6438407 | Ousdigian et al. | Aug 2002 | B1 |
6438408 | Mulligan et al. | Aug 2002 | B1 |
6440066 | Bardy | Aug 2002 | B1 |
6441747 | Khair et al. | Aug 2002 | B1 |
6442433 | Linberg | Aug 2002 | B1 |
6443890 | Schulze et al. | Sep 2002 | B1 |
6453201 | Daum et al. | Sep 2002 | B1 |
6470215 | Kraus et al. | Oct 2002 | B1 |
6480745 | Nelson et al. | Nov 2002 | B2 |
6490487 | Kraus et al. | Dec 2002 | B1 |
6497655 | Linberg et al. | Dec 2002 | B1 |
6514195 | Ferek | Feb 2003 | B1 |
6542775 | Ding et al. | Apr 2003 | B2 |
RE38119 | Mower | May 2003 | E |
6564104 | Nelson et al. | May 2003 | B2 |
6564105 | Starkweather et al. | May 2003 | B2 |
6574503 | Ferek-Petric | Jun 2003 | B2 |
6579231 | Phipps | Jun 2003 | B1 |
6584353 | Meyer | Jun 2003 | B2 |
6585644 | Lebel et al. | Jul 2003 | B2 |
6592528 | Amano | Jul 2003 | B2 |
6622045 | Snell et al. | Sep 2003 | B2 |
6622048 | Mann et al. | Sep 2003 | B1 |
6628989 | Penner et al. | Sep 2003 | B1 |
6648823 | Thompson et al. | Nov 2003 | B2 |
6650939 | Taepke, II et al. | Nov 2003 | B2 |
6650944 | Goedeke et al. | Nov 2003 | B2 |
6665558 | Kalgren et al. | Dec 2003 | B2 |
6669631 | Norris et al. | Dec 2003 | B2 |
6684103 | Ding et al. | Jan 2004 | B2 |
6687547 | Goedeke et al. | Feb 2004 | B2 |
6738667 | Deno et al. | May 2004 | B2 |
6738671 | Christophersom et al. | May 2004 | B2 |
6764446 | Wolinsky et al. | Jul 2004 | B2 |
6804558 | Haller et al. | Oct 2004 | B2 |
6827670 | Stark et al. | Dec 2004 | B1 |
6931273 | Groenewegen et al. | Aug 2005 | B2 |
6937899 | Sheldon et al. | Aug 2005 | B2 |
6944495 | MacAdam et al. | Sep 2005 | B2 |
6961617 | Snell | Nov 2005 | B1 |
6975900 | Rudy et al. | Dec 2005 | B2 |
7024248 | Penner et al. | Apr 2006 | B2 |
7043305 | Kenknight et al. | May 2006 | B2 |
7123953 | Starobin et al. | Oct 2006 | B2 |
7203549 | Schommer et al. | Apr 2007 | B2 |
7273457 | Penner | Sep 2007 | B2 |
7275220 | Brummel et al. | Sep 2007 | B2 |
RE39897 | Mower | Oct 2007 | E |
7468032 | Stahmann et al. | Dec 2008 | B2 |
7805199 | KenKnight et al. | Sep 2010 | B2 |
20010007053 | Bardy | Jul 2001 | A1 |
20010012955 | Goedeke et al. | Aug 2001 | A1 |
20010031997 | Lee | Oct 2001 | A1 |
20010031998 | Nelson et al. | Oct 2001 | A1 |
20010039375 | Lee et al. | Nov 2001 | A1 |
20010039503 | Chan et al. | Nov 2001 | A1 |
20010047125 | Quy | Nov 2001 | A1 |
20010049471 | Suzuki et al. | Dec 2001 | A1 |
20010049544 | Lee | Dec 2001 | A1 |
20010051787 | Haller et al. | Dec 2001 | A1 |
20020013613 | Haller et al. | Jan 2002 | A1 |
20020013614 | Thompson | Jan 2002 | A1 |
20020016550 | Sweeney et al. | Feb 2002 | A1 |
20020019586 | Teller et al. | Feb 2002 | A1 |
20020023654 | Webb | Feb 2002 | A1 |
20020026103 | Norris et al. | Feb 2002 | A1 |
20020026223 | Riff et al. | Feb 2002 | A1 |
20020040234 | Linberg | Apr 2002 | A1 |
20020045808 | Ford et al. | Apr 2002 | A1 |
20020049482 | Fabian et al. | Apr 2002 | A1 |
20020052539 | Haller et al. | May 2002 | A1 |
20020077562 | Kalgren et al. | Jun 2002 | A1 |
20020082665 | Haller et al. | Jun 2002 | A1 |
20020082868 | Pories et al. | Jun 2002 | A1 |
20020115939 | Mulligan et al. | Aug 2002 | A1 |
20020120311 | Lindh et al. | Aug 2002 | A1 |
20020123672 | Christophersom et al. | Sep 2002 | A1 |
20020138012 | Hodges et al. | Sep 2002 | A1 |
20020173830 | Starkweather et al. | Nov 2002 | A1 |
20020193667 | McNair | Dec 2002 | A1 |
20030055406 | Lebel et al. | Mar 2003 | A1 |
20030055679 | Soll et al. | Mar 2003 | A1 |
20030074029 | Deno et al. | Apr 2003 | A1 |
20030088290 | Spinelli et al. | May 2003 | A1 |
20030093127 | Dalal | May 2003 | A1 |
20030144711 | Pless et al. | Jul 2003 | A1 |
20030171791 | KenKnight et al. | Sep 2003 | A1 |
20030235816 | Slawin et al. | Dec 2003 | A1 |
20040019287 | White | Jan 2004 | A1 |
20040117204 | Mazar et al. | Jun 2004 | A1 |
20040122294 | Hatlestad et al. | Jun 2004 | A1 |
20040122295 | Hatlestad et al. | Jun 2004 | A1 |
20040122296 | Hatlestad et al. | Jun 2004 | A1 |
20040122297 | Stahmann et al. | Jun 2004 | A1 |
20040122484 | Hatlestad et al. | Jun 2004 | A1 |
20040122485 | Stahmann et al. | Jun 2004 | A1 |
20040122486 | Stahmann et al. | Jun 2004 | A1 |
20040122487 | Hatlestad et al. | Jun 2004 | A1 |
Number | Date | Country |
---|---|---|
0297675 | Jan 1989 | EP |
0362611 | Apr 1990 | EP |
709058 | May 1996 | EP |
0709058 | May 1996 | EP |
2000123098 | Apr 2000 | JP |
200167403 | Mar 2001 | JP |
2001299702 | Oct 2001 | JP |
2002514454 | May 2002 | JP |
2002183312 | Jun 2002 | JP |
2002311158 | Oct 2002 | JP |
WO-9938278 | Jul 1999 | WO |
WO-9958056 | Nov 1999 | WO |
WO-9958086 | Nov 1999 | WO |
WO-0041765 | Jul 2000 | WO |
WO-0041766 | Jul 2000 | WO |
WO-0103575 | Jan 2001 | WO |
WO-0124876 | Apr 2001 | WO |
WO-0167948 | Sep 2001 | WO |
WO-03075744 | Sep 2003 | WO |
Entry |
---|
“U.S. Appl. No. 10/323,604, Final Office Action mailed Aug. 19, 2008”, 16 pgs. |
“U.S. Appl. No. 10/323,604, Non-Final Office Action mailed Apr. 21, 2009”, 20 pgs. |
“U.S. Appl. No. 10/323,604, Response filed Feb. 19, 2009 to Final Office Action mailed Aug. 19, 2008”, 14 pgs. |
“U.S. Appl. No. 10/323,606, Examiner's Answer mailed Feb. 26, 2008”, 29 pgs. |
“U.S. Appl. No. 10/323,606, Reply Brief filed Apr. 28, 2008”, 9 pgs. |
“U.S. Appl. No. 10/323,607, Non-Final Office Action mailed Aug. 24, 2009”, 7 pgs. |
“U.S. Appl. No. 10/323,607, Non-Final Office Action mailed Oct. 22, 2008”, 6 pgs. |
“U.S. Appl. No. 10/323,607, Response filed Feb. 23, 2009 to Non-Final Office Action mailed Oct. 22, 2008”, 9 pgs. |
“U.S. Appl. No. 10/323,607, Response filed Jun. 22, 2005 to Final Office Action mailed Mar. 23, 2005”, 12 pgs. |
“U.S. Appl. No. 10/323,607, Response filed Sep. 13, 2005 to Notice of Non-Compliant Amendment mailed Sep. 8, 2005”, 12 pgs. |
“U.S. Appl. No. 10/323,607, Supplemental Response filed May 22, 2007 to Final Office Action mailed Aug. 1, 2006”, 10 pgs. |
“U.S. Appl. No. 10/323,616, Final Office Action mailed Nov. 13, 2008”, 19 pgs. |
“U.S. Appl. No. 10/323,616, Non-Final Office Action mailed Apr. 2, 2009”, 22 pgs. |
“U.S. Appl. No. 10/323,616, Response filed Mar. 13, 2009 to Final Office Action mailed Nov. 13, 2008”, 17 pgs. |
“U.S. Appl. No. 10/323,616, Response filed Aug. 3, 2009 to Non-Final Office Action mailed Apr. 2, 2009”, 19 pgs. |
“U.S. Appl. No. 10/323,713, Preliminary Amendment mailed Dec. 17, 2003”, 14 pgs. |
“U.S. Appl. No. 10/323,859, Final Office Action mailed Jul. 9, 2009”, 9 pgs. |
“U.S. Appl. No. 10/323,859, Non-Final Office Action mailed Oct. 17, 2008”, 7 pgs. |
“U.S. Appl. No. 10/323,859, Response filed Mar. 17, 2009 to Non-Final Office Action mailed Oct. 17, 2008”, 20 pgs. |
“U.S. Appl. No. 10/323,860, Response filed Aug. 4, 2009 to Final Office Action mailed Mar. 5, 2009”, 14 pgs. |
“U.S. Appl. No. 10/323,860, Response filed Aug. 31, 2009 to Advisory Action mailed Aug. 19, 2009”, 16 pgs. |
“U.S. Appl. No. 10/323,860, Response filed Nov. 24, 2008 to Non-Final Office Action mailed Jul. 22, 2008”, 17 pgs. |
“U.S. Appl. No. 12/891,338, Notice of Allowance mailed Dec. 7, 2011”, 10 pgs. |
“European Application Serial No. 03713931, Office Action mailed Jul. 22, 2008”, 4 pgs. |
“European Application Serial No. 03713931.8, Office Action mailed May 20, 2009”, 2 pgs. |
“European Application Serial No. 03713931.8, Response filed Jan. 15, 2009 to Communication dated Jul. 22, 2008”, 17 pgs. |
“European Application Serial No. 03713931.8, Response filed Sep. 18, 2009 to Communication dated May 20, 2009”, 4 pgs. |
“International Search Report for corresponding PCT Application No. PCT/US 03/06851”, (Nov. 25, 2004), 4 Pages. |
Barbaro, V., et al., “A portable unit for remote monitoring of pacemaker patients”, Journal of Telemedicine and Telecare, 3(2), (1997), 96-102. |
Bourge, Robert, et al., “Noninvasive Rejection Monitoring of Cardiac Transplants Using High Resolution Intramyocardial Electrograms”, PACE, vol. 21, Part II, (Nov. 1998), 2338-2344. |
Girouard, Steven D, et al., “Cardiac Rhythm Management Systems and Methods Predicting Congestive Heart Failure Status”, U.S. Appl. No. 10/213,268, filed Aug. 6, 2002, 33 pgs. |
Hatlestad, John, “Methods and Devices for Detection of Context When Addressing a Medical Condition of a Patient”, U.S. Appl. No. 10/269,611, filed Oct. 11, 2002, 29 pgs. |
Hutten, H., et al., “Cardiac pacemaker as bridge to cardiac telemonitoring”, Biomedizinische Technik, 41(6), Institut for Elektro-und Biomedizinische Technik Technische Universitat Graz., [Article in German With English Abstract], (Jun. 1996), 158-165. |
Hutten, H., et al., “Cardiac Telemonitoring through the Linkage of Close-up Telemetry and Internet Transmission”, Institute for Electro-and Biomedical Technology, Technical University of Graz Inffeldgasse, 42, [Article in German with English Abstract], (1997), 67-69. |
Ji, J., “An Ultraminiature CMOS Pressure Sensor for a Multiplexed Cardiovascular Catheter”, IEEE Transactions on Electron Devices, vol. 39, No. 10, (Oct. 1992), pp. 2260-2267. |
Mower, Morton, U.S. Appl. No. 10/214,474, filed Aug. 8, 2002, entitled “Method and Apparatus for Treating Hemodynamic Disfunction”. |
Smith, R.A., et al., “An intranet database for pacemaker patients”, International Journal of Medical Informatics, 47, (1997), 79-82. |
Zhu, Qingsheng, et al., “Method and Apparatus for Determining Changes in Heart Failure Status”, U.S. Appl. No. 10/001,223, filed Nov. 15, 2001, 22 pgs. |
“U.S. Appl. No. 10/093,353, Final Office Action mailed Jun. 3, 2005”, 11 pgs. |
“U.S. Appl. No. 10/093,353, Non Final Office Action mailed NOv. 3, 2004”, 11 pgs. |
“U.S. Appl. No. 10/093,353, Notice of Allowance mailed Dec. 13, 2005”, 10 pgs. |
“U.S. Appl. No. 10/093,353, Response filed Feb. 25, 2005 to Non Final Office Action mailed Nov. 3, 2004”, 11 pgs. |
“U.S. Appl. No. 10/093,353, Response filed Nov. 3, 2005 to Final Office Action mailed Jun. 3, 2005”, 9 pgs. |
“U.S. Appl. No. 10/323,604, Appeal Brief filed Dec. 10, 2009”, 54 pgs. |
“U.S. Appl. No. 10/323,604, Decision on Appeal mailed Jun. 6, 2012”, 15 pgs. |
“U.S. Appl. No. 10/323,604, Decision on Pre-Appeal Brief Request mailed Nov. 10, 2009”, 2 pgs. |
“U.S. Appl. No. 10/323,604, Examiner's Answer to Appeal Brief mailed Aug. 6, 2010”, 21 pgs. |
“U.S. Appl. No. 10/323,604, Final Office Action mailed Feb. 12, 2007”, 13 pgs. |
“U.S. Appl. No. 10/323,604, Non-Final Office Action mailed Aug. 8, 2007”, 13 pgs. |
“U.S. Appl. No. 10/323,604, Non-Final Office Action mailed Dec. 30, 2005”, 15 pgs. |
“U.S. Appl. No. 10/323,604, Notice of Allowance mailed Aug. 10, 2012”, 7 pgs. |
“U.S. Appl. No. 10/323,604, Notice of Non-Compliant Brief mailed Jan. 11, 2010”, 2 pgs. |
“U.S. Appl. No. 10/323,604, Fre-Appeal Request filed Aug. 20, 2009”, 5 pgs. |
“U.S. Appl. No. 10/323,604, Reply Brief filed Oct. 5, 2010”, 7 pgs. |
“U.S. Appl. No. 10/323,604, Response filed Jan. 8, 2008 to Non-Final Office Action mailed Aug. 8, 2007”, 17 pgs. |
“U.S. Appl. No. 10/323,604, Response filed May 30, 2007 to Final Office Action mailed Feb. 12, 2007”, 17 pgs. |
“U.S. Appl. No. 10/323,604, Response filed Jun. 30, 2006 to Restriction Requirement mailed Dec. 30, 2005”, 20 pgs. |
“U.S. Appl. No. 10/323,604, Response filed Jan. 8, 2008 to Office Action mailed Aug. 8, 2007”, 17 pgs. |
“U.S. Appl. No. 10/323,604, Response filed Nov. 22, 2005 to Restriction Requirement mailed Oct. 26, 2005”, 12 pgs. |
“U.S. Appl. No. 10/323,604, Response to Notice of Non-Compliant Brief filed Feb. 11, 2010”, 56 pgs. |
“U.S. Appl. No. 10/323,604, Restriction Requirement mailed Oct. 26, 2005”, 6 pgs. |
“U.S. Appl. No. 10/323,604, Restriction Requirement mailed Dec. 9, 2005”, 8 pgs. |
“U.S. Appl. No. 10/323,604, Supplemental Notice of Allowability mailed Nov. 5, 2012”, 2 pgs. |
“U.S. Appl. No. 10/323,616, Final Office Action mailed Oct. 31, 2007”, 20 pgs. |
“U.S. Appl. No. 10/323,713, Advisory Action mailed Jan. 31, 2007”, 3 pgs. |
“U.S. Appl. No. 10/323,713, Final Office Action mailed Apr. 4, 2008”, 16 pgs. |
“U.S. Appl. No. 10/323,713, Final Office Action mailed Nov. 8, 2006”, 12 pgs. |
“U.S. Appl. No. 10/323,713, Non Final Office Action mailed Apr. 10, 2007”, 13 pgs. |
“U.S. Appl. No. 10/323,713, Non Final Office Action mailed Dec. 9, 2005”, 10 pgs. |
“U.S. Appl. No. 10/323,713, Non-Final Office Action mailed Jun. 21, 2006”, 11 pgs. |
“U.S. Appl. No. 10/323,713, Non-Final Office Action mailed Sep. 28, 2007”, 15 pgs. |
“U.S. Appl. No. 10/323,713, Notice of Allowance mailed Aug. 20, 2008”, 9 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Jan. 8, 2007 to Final Office Action mailed Nov. 8, 2006”, 17 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Mar. 26, 2007 to Final Office Action mailed Nov. 8, 2006”, 15 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Apr. 18, 2006 to Non Final Office Action mailed Dec. 9, 2005”, 15 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Jul. 10, 2007 to Non-Final Office Action mailed Apr. 10, 2007”, 18 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Jul. 30, 2008 to Final Office Action mailed Apr. 4, 2008”, 11 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Sep. 21, 2006 to Non Final Office Action mailed Jun. 21, 2006”, 14 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Oct. 10, 2005 to Restriction Requirement mailed Sep. 9, 2005”, 11 pgs. |
“U.S. Appl. No. 10/323,713, Response filed Dec. 28, 2007 to Non-Final Office Action mailed Sep. 28, 2007”, 19 pgs. |
“U.S. Appl. No. 10/323,713, Restriction Requirement mailed Sep. 9, 2005”, 6 pgs. |
“U.S. Appl. No. 11/381,051, Non-Final Office Action mailed Mar. 19, 2008”, 14 pgs. |
“U.S. Appl. No. 11/381,051, Non-Final Office Action mailed Oct. 22, 2008”, 13 pgs. |
“U.S. Appl. No. 11/381,051, Notice of Allowance mailed May 18, 2010”, 6 pgs. |
“U.S. Appl. No. 11/381,051, Notice of Allowance mailed Jun. 2, 2009”, 8 pgs. |
“U.S. Appl. No. 11/381,051, Notice of Allowance mailed Dec. 18, 2009”, 8 pgs. |
“U.S. Appl. No. 11/381,051, Preliminary Amendment filed May 1, 2006”, 5 pgs. |
“U.S. Appl. No. 11/381,051, Response filed Feb. 23, 2009 to Non-Final Office Action mailed Oct. 22, 2008”, 11 pgs. |
“U.S. Appl. No. 11/381,051, Response filed Aug. 18, 2008 to Non-Final Office Action mailed Mar. 19, 2008”, 7 pgs. |
“U.S. Appl. No. 11/381,051, Supplemental Preliminary Amendment filed Jul. 31, 2006”, 6 pgs. |
“U.S. Appl. No. 12/341,207, Notice of Allowance mailed Feb. 7, 2011”, 10 pgs. |
“U.S. Appl. No. 12/341,207, Preliminary Amendment mailed Jan. 25, 2011”, 6 pgs. |
“U.S. Appl. No. 13/769,737, Notice of Allowance mailed May 15, 2013”, 12 pgs. |
“U.S. Appl. No. 13/769,737, Supplemental Notice of Allowability mailed Aug. 20, 2013”, 2 pgs. |
“U.S. Appl. No. 13/769,737, Supplemental Notice of Allowability mailed Aug. 26, 2013”, 2 pgs. |
“Correlation”, [online]. [retrieved Mar. 19, 2007]. Retrieved from the Internet: <URL: http://everything2.com/index.pl?node=correlation>, (1999 & 2001), 3 pgs. |
“European Application Serial No. 03713931.8, Communication dated Feb. 3, 2005”, 2 pgs. |
“European Application Serial No. 03713931.8, Response filed Mar. 3, 2005 to Communication dated Feb. 3, 2005”, 6 pgs. |
“European Application Serial No. 03814044.8, Response filed Oct. 20, 2008 to Communication mailed Apr. 21, 2008”, 14 pgs. |
“International Application Serial No. PCT/US03/06851, International Search Report mailed Nov. 25, 2004”, 4 pgs. |
Anderson, T. W., “R. A. Fisher and multivariate analysis”, Statist. Sci., 11(1), (1996), 20-34. |
Garson, G. David, “Correlation”, Statistics Solutions, Inc. http://statisticssolutions.com/correlation.htm, (Copyright 1998, 2006), 12 pgs. |
Kenknight, Bruce H, “Method and Apparatus for Establishing Context Among Events and Optimizing Implanted Medical Device Performance”, U.S. Appl. No. 11/381,051, filed May 1, 2006, 44 pgs. |
Number | Date | Country | |
---|---|---|---|
20120323289 A1 | Dec 2012 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12891338 | Sep 2010 | US |
Child | 13447816 | US | |
Parent | 11381051 | May 2006 | US |
Child | 12891338 | US | |
Parent | 10093353 | Mar 2002 | US |
Child | 11381051 | US |