This document relates generally to implantable medical devices and particularly, but not by way of limitation, to such a device including power management of a telemetry system allowing communication with an external device.
Medical devices are implanted in human bodies for monitoring physiological conditions, diagnosing diseases, treating diseases, or restoring functions of organs or tissues. Examples of such implantable medical devices include cardiac rhythm management systems, neurological stimulators, neuromuscular stimulators, and drug delivery systems. Because such a device may be implanted in a patient for a long time, the size and power consumption of the device are inherently constrained. Consequently, an implantable device may depend on an external system to perform certain functions. Communication between the implantable device and the external system is referred to as telemetry. Examples of specific telemetry functions include programming the implantable device to perform certain monitoring or therapeutic tasks, extracting an operational status of the implantable device, transmitting real-time physiological data acquired by the implantable device, and extracting physiological data acquired by and stored in the implantable device.
One particular example of implantable medical devices is a cardiac rhythm management device implanted in a patient to treat irregular or other abnormal cardiac rhythms by delivering electrical pulses to the patient's heart. Such rhythms result in diminished blood circulation. Implantable cardiac rhythm management devices include, among other things, pacemakers, also referred to as pacers. Pacers are often used to treat patients with bradyarrhythmias, that is, hearts that beat too slowly or irregularly. Such pacers may coordinate atrial and ventricular contractions to improve the heart's pumping efficiency. Implantable cardiac rhythm management devices also include devices providing cardiac resynchronization therapy (CRT), such as for patients with congestive heart failure (CHF). CHF patients have deteriorated heart muscles that display less contractility and cause poorly synchronized heart contraction patterns. By pacing multiple heart chambers or multiple sites within a single heart chamber, the CRT device restores a more synchronized contraction of the weakened heart muscle, thus increasing the heart's efficiency as a pump. Implantable cardiac management devices also include defibrillators that are capable of delivering higher energy electrical stimuli to the heart. Such defibrillators may also include cardioverters, which synchronize the delivery of such stimuli to portions of sensed intrinsic heart activity signals. Defibrillators are often used to treat patients with tachyarrhythmias, that is, hearts that beat too quickly. In addition to pacers, CRT devices, and defibrillators, implantable cardiac rhythm management systems also include, among other things, pacer/defibrillators that combine the functions of pacers and defibrillators, drug delivery devices, and any other implantable systems or devices for diagnosing or treating cardiac arrhythmias.
Typically, an implantable cardiac rhythm management device communicates, via telemetry, with an external device referred to as a programmer. One type of such telemetry is based on inductive coupling between two closely-placed coils using the mutual inductance between these coils. This type of telemetry is referred to as inductive telemetry or near-field telemetry because the coils must typically be closely situated for obtaining inductively coupled communication. One example of such an inductive telemetry is discussed in Brockway et al., U.S. Pat. No. 4,562,841, entitled “PROGRAMMABLE MULTI-MODE CARDIAC PACEMAKER,” assigned to Cardiac Pacemakers, Inc., the disclosure of which is incorporated herein by reference in its entirety.
In one example, an implantable device includes a first coil and a telemetry circuit, both sealed in a metal housing (referred to as a “can”). The external programmer provides a second coil in a wand that is electrically connected to the programmer. During device implantation, a physician evaluates the patient's condition, such as by using the implanted device to acquire real-time physiological data from the patient and communicating the physiological data in real-time to the external programmer for processing and/or display. The physician may also program the implantable device, including selecting a pacing or defibrillation therapy mode, and parameters required by that mode, based on the patient's condition and needs. The data acquisition and device programming are both performed using the inductive telemetry. If the patient's condition is stable after implantation, he or she needs no attention from the physician or other caregiver until a scheduled routine follow-up. During a typical routine follow-up, the physician reviews the patient's history with the implantable device, re-evaluates the patient's condition, and re-programs the implantable device if necessary.
One problem with inductive telemetry is its requirement that the two coils are closely placed. This typically requires placing the wand on the body surface over the implantable device. Because the wand is electrically connected to the programmer using a cable, the inductive telemetry limits the patient's mobility.
To improve communication range and patient mobility, a far-field radio-frequency (RF) telemetry may be used, in which an RF transceiver in the implantable device is used to communicate with an RF transceiver in the external programmer. With a far-field RF telemetry, the patient is typically free of any body surface attachment that limits mobility. However, RF telemetry may consume several thousand times more energy than inductive telemetry.
For these and other reasons, the present inventors have recognized an unmet need for long-range telemetry at reduced energy consumption from the implantable device.
An implantable medical device includes a radio-frequency (RF) telemetry circuit that includes a power switch through which the RF telemetry circuit is connected to an energy source such as a battery. The power switch is closed to connect power from the energy source to the RF telemetry circuit when a user initiates an RF telemetry session. After the RF telemetry session is completed, the power switch is opened to shut off at least a portion of the RF telemetry circuit.
In one example, the RF telemetry circuit is powered on by sending a telemetry activation signal from the remote device to the implantable device. A physician or other caregiver operating the remote device initiates an RF telemetry session. The power switch is closed when the telemetry activation signal is detected by the implantable device.
In another example, the RF telemetry circuit is powered on by a physical movement sensed by an accelerometer and detected by the implantable device. A patient with the implantable device initiates an RF telemetry session by tapping on the skin over the implantable device. The power switch is closed when the implantable device detects an acceleration resulted from the tapping.
In another example, the RF telemetry circuit is powered on by activating an inductive telemetry circuit included in the implantable device. A physician or other caregiver operating an external programmer initiates an inductive telemetry operation in order to initiate an RF telemetry session. The power switch is closed when an inductive telemetry circuit in the implantable device is activated.
In another example, the RF telemetry circuit is powered on by a magnetic field detected by the implantable device. A physician or other caregiver waves a magnet or a hand held device generating a magnetic field to initiate an RF telemetry session. The power switch is closed when the magnetic filed exceeds a predetermined level and is detected by the implantable device.
In another example, the RF telemetry circuit is powered on by introducing a telemetry activation signal into the patient through a surface electrocardiography (ECG) recording system. A physician or other caregiver operating the remote device including an ECG module initiates an RF telemetry session. The power switch is closed when the telemetry activation signal is detected by a biopotential sensing circuit in the implantable device.
In another example, the RF telemetry circuit is powered on by introducing a telemetry activation signal into a patient through contacts between the patient and an external device adopted for telemetry activation. A patient initiates an RF telemetry session by contacting the external device. The power switch is closed when the telemetry activation signal is detected by a biopotential sensing circuit in the implantable device.
In one example, the RF telemetry circuit is shut off when a termination signal sent from the remote device through the RF telemetry is received by the implantable device. A physician or other caregiver operating the remote device may issue the termination signal. Alternatively, the termination signal may be sent when the remote device determines that the RF telemetry session is to be concluded. The power switch is opened when the implantable device receives the termination signal.
In another example, the RF telemetry circuit is shut off after a predetermined delay following an end of a data transmission session. A timer is started when the data transmission stops. The power switch is opened at the end of the predetermined delay if the data transmission has not resumed.
In another example, the RF telemetry circuit is shut off by activating an inductive telemetry circuit included in the implantable device. A physician or other caregiver operating an external programmer terminates an RF telemetry session. The power switch is closed immediately after the inductive telemetry circuit in the implantable device is activated.
Depending on a patient's needs for care and type of implantable device, one or more of the power-on methods and one or more of the power-off methods discussed in this document may be included in one implantable device. Using more than one method to connect/disconnect power from the energy source to the RF telemetry circuit increases the reliability of initiating and terminating the RF telemetry session in a timely manner to ensure patient safety and conserve energy and hence device longevity. Other aspects of the present systems, devices, and methods will become apparent upon reading the following Detailed Description and viewing the drawings that form a part thereof.
In the drawings, which are not necessarily drawn to scale, like numerals describe substantially similar components throughout the several views. Like numerals having different letter suffixes represent different instances of substantially similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.
In the following detailed description, reference is made to the accompanying drawings that 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 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.
This document discusses, among other things, power management of telemetry circuit in an implantable medical device. The present methods and apparatuses will be described in applications involving implantable cardiac rhythm management systems such as pacemakers, CRT devices, cardioverter/defibrillators, and pacer/defibrillators. However, it is understood that the present methods and apparatuses may be employed in other types of implantable medical devices, including, but not being limited to, neurological stimulators, neuromuscular stimulators, drug delivery systems, and various types of physiological signal monitoring devices.
In one example, RF telemetry link 150 provides for data transmission from implanted device 110 to remote device 140. This may include, for example, transmitting real-time physiological data acquired by implanted device 110, extracting physiological data acquired by and stored in implanted device 110, extracting therapy history data stored in implanted device 110, and extracting data indicating an operational status of implanted device 110 (e.g., battery status and lead impedance). In a further example, RF telemetry link 150 transmits data from remote device 140 to implanted device 110. This may include, for example, programming implanted device 110 to acquire physiological data, programming implanted device 110 to perform at least one self-diagnostic test (such as for a device operational status), and programming implanted device 110 to deliver at least one therapy.
In one example, RF telemetry link 150 is a far-field telemetry link. A far-field, also referred to as the Fraunhofer zone, refers to the zone in which a component of an electromagnetic field produced by the transmitting electromagnetic radiation source decays substantially proportionally to 1/r, where r is the distance between an observation point and the radiation source. Accordingly, far-field refers to the zone outside the boundary of r=λ/2π, where λ is the wavelength of the transmitted electromagnetic energy. In one example, a communication range of RF telemetry link 150 (a distance over which data is capable of being wirelessly communicated) is at least six feet but can be as long as allowed by the particular communication technology. Unlike an inductive telemetry link using a wand placed near implanted device 110, typically attached to the patient, and electrically connected to remote external device 140 with a cable, using RF telemetry link 150 frees the patient from any physical restraints caused by the wand and the cable. On the other hand, the power consumed by implanted device 110 to support a far-field RF telemetry can be as high as ten thousand times that of inductive telemetry. To reduce the energy consumption of implanted device 110, the present inventors have recognized the need for power management to reduce the energy drawn from implanted device 110 to support the RF telemetry link 150.
In this document, “power switch” refers generally to any power connection module, not limited to an on/off switch, that, in one example controls an activation (or power-on) and deactivation (or power-off) of the RF telemetry. In one example, the RF telemetry circuit is powered on, or activated, when it enters an energization state that enables it to perform its intended telemetry function. In another example, the RF telemetry circuit is powered off, or deactivated, when it enters another energizaton state that maintains the circuit off or in a “sleep” or “barely awake” mode to conserve energy. In one example, the power switch connects/disconnects power from the energy source to one or more portions of the RF telemetry circuit.
In one example, power switch 215 connects/disconnects power from energy source 211 to portions of RF telemetry circuit 212. After the telemetry session is terminated, power switch 215 disconnects power from the portions of RF telemetry circuit 212 but maintains power connection to other portions of RF telemetry circuit 212, such that RF telemetry circuit 212 may be activated quickly when a new telemetry session is initiated.
In one example, once RF telemetry link 150 has been established, a physician or other caregiver uses the inductive telemetry link 755 of
In the example of
Each power-on or power-off method discussed above offers advantages, which are discussed herein by way as example, and not by way of limitation. Power-on by RF burst signal allows an RF telemetry session to be initiated at remote device 140. This allows a physician or other caregiver to provide care to a patient from a remote location. An examination of the patient may be performed with or without the patient's knowledge. In one example, the patient's routine check-up is performed through the RF telemetry and telephone, so that the patient saves a trip to a physician's office. In another example, the patient who needs close monitoring is frequently checked by the physician or other caregiver through the RF telemetry, so that the patient need not be hospitalized to receive similar care. Power-on by physical activity allows an RF telemetry session to be initiated by a patient or a person with the patient. No additional external device is required. In one example, implanted device 110 already includes an accelerometer as an activity or metabolic need sensor employed in a therapy algorithm. The same accelerometer may be used for telemetry power management by modifying only software. Power-on of RF telemetry using inductive telemetry is convenient when implanted device 110 includes an inductive telemetry system. Having external programmer 745 available during an RF telemetry session also provides an alternative communications modality if RF telemetry is lost because of RF interference or other reasons. Power-on by magnetic field allows RF telemetry power management using a magnet or a hand-held device. This is likely more convenient to handle than external programmer 745. In one example, implanted device 110 already includes a function activated or suppressed by an external magnet. For example, holding a magnet near implanted device 110 may cause it to pace at a fixed pacing rate, overriding any therapy algorithm that would be otherwise effective. Using a magnetic field for RF telemetry power management in this example may be implemented by modifying only software. Power-on by introducing a signal via surface ECG electrodes is convenient when remote device 140 includes an ECG module. During a patient's follow-up visit to a physician, the physician typically attaches ECG electrodes to the patient to diagnose the patient's condition. By automatically detecting when the cables from such ECG electrodes are connected to the programmer, telemetry is seamlessly automatically activated without requiring physician intervention. In another example, using RF telemetry provides for a higher rate of data transmission as compared with inductive telemetry, reducing the duration of a telemetry session. Power-on by momentarily contacting an external device allows a patient to initiate and/or schedule an RF telemetry session and is convenient for patients who regularly use a medical device such as a monitor.
Power-off by sending a command via RF telemetry deactivates implanted RF telemetry circuit 212 without wasting power by keeping the RF telemetry power on longer than necessary. However, under some circumstances RF telemetry link 150 may be interrupted before the power-off signal is sent to implanted device 110. Examples of such circumstances include a strong RF noise or a patient moving beyond a range of the RF telemetry. Under such circumstances, power-off using a timer ensures that implanted RF telemetry circuit is shut off after the RF telemetry has been idle for a predetermined period of time. Power-off using inductive telemetry permits the physician or other caregiver to immediately terminate the RF telemetry at any time. In one example, the physician or other caregiver terminates an RF telemetry that is accidentally established with an unintended implantable device. An inductive telemetry is less likely to be accidentally established because it often requires the wand to be closely (within a few inches) coupled to the implantable device. In another example, the physician or other caregiver may terminate the RF telemetry by using the inductive telemetry, such as when one or more other power-off methods fail. In a further example, the one or more other power-off methods fail because of the presence of a noise, such as a cellular phone signal.
Depending on the patient's needs for care and type of implantable device, one or more of the power-on methods and one or more of the power-off methods discussed above may be included in one implantable device. Using more than one method to connect/disconnect power from energy source 211 to implanted RF telemetry circuit 212, or at least portions thereof, increases the reliability of initiating and terminating the RF telemetry session in a timely manner. This ensures patient safety, conserves energy, and hence increases device longevity. If one method fails, another available method may be automatically or manually applied. In one example, implanted device 110 employs one power-on method but several power-off methods, such as all three discussed above. This decreases energy waste and patient risks by ensuring that implanted RF telemetry circuit 212 is deactivated as soon as the RF telemetry session ends.
It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the implantable device can be any implantable medical device having an active electronic circuit. Many other embodiments will be apparent to those of skill in the art upon reviewing 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. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.”
This application is a division of U.S. patent application Ser. No. 11/244,273, now U.S. Pat. No. 7,668,596, filed Oct. 5, 2005, which is a division of U.S. patent application Ser. No. 10/071,255, now U.S. Pat. No. 6,985,773, filed on Feb. 7, 2002, the specifications of which are incorporated herein by reference in their entirety. This application is related to commonly assigned Von Arx et al. U.S. patent application Ser. No. 10/025,223, now U.S. Pat. No. 6,993,393, entitled “A TELEMETRY DUTY CYCLE MANAGEMENT SYSTEM FOR AN IMPLANTABLE MEDICAL DEVICE,” filed Dec. 19, 2001 and Von Arx et al. U.S. patent application Ser. No. 10/025,183, now U.S. Pat No. 7,729,776, entitled “AN IMPLANTABLE MEDICAL DEVICE WITH TWO OR MORE TELEMETRY SYSTEMS,” filed Dec. 19, 2001, each of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4341982 | Lahti et al. | Jul 1982 | A |
4404972 | Gordon et al. | Sep 1983 | A |
4441498 | Nordling | Apr 1984 | A |
4486739 | Franaszek et al. | Dec 1984 | A |
4519401 | Ko et al. | May 1985 | A |
4542532 | McQuilkin | Sep 1985 | A |
4542535 | Bates et al. | Sep 1985 | A |
4543954 | Cook et al. | Oct 1985 | A |
4561443 | Hogrefe et al. | Dec 1985 | A |
4562841 | Brockway et al. | Jan 1986 | A |
4634294 | Christol et al. | Jan 1987 | A |
4731814 | Becker et al. | Mar 1988 | A |
4803987 | Calfee et al. | Feb 1989 | A |
4944299 | Silvian | Jul 1990 | A |
4945909 | Fearnot et al. | Aug 1990 | A |
4987897 | Funke | Jan 1991 | A |
5025808 | Hafner | Jun 1991 | A |
5074308 | Sholder et al. | Dec 1991 | A |
5080096 | Hooper et al. | Jan 1992 | A |
5089019 | Grandjean | Feb 1992 | A |
5109853 | Taicher et al. | May 1992 | A |
5113869 | Nappholz et al. | May 1992 | A |
5171977 | Morrison | Dec 1992 | A |
5287384 | Avery et al. | Feb 1994 | A |
5292343 | Blanchette et al. | Mar 1994 | A |
5300093 | Koestner et al. | Apr 1994 | A |
5314453 | Jeutter | May 1994 | A |
5342408 | deCoriolis et al. | Aug 1994 | A |
5350411 | Ryan et al. | Sep 1994 | A |
5350412 | Hoegnelid et al. | Sep 1994 | A |
5370666 | Lindberg et al. | Dec 1994 | A |
5404877 | Nolan et al. | Apr 1995 | A |
5466246 | Silvian | Nov 1995 | A |
5476488 | Morgan et al. | Dec 1995 | A |
5486200 | Lindemans | Jan 1996 | A |
5516285 | Yacker et al. | May 1996 | A |
5532708 | Krenz et al. | Jul 1996 | A |
5535752 | Halperin et al. | Jul 1996 | A |
5562713 | Silvian | Oct 1996 | A |
5568510 | Tam | Oct 1996 | A |
5577087 | Furuya | Nov 1996 | A |
5579876 | Adrian et al. | Dec 1996 | A |
5593430 | Renger | Jan 1997 | A |
5598847 | Renger | Feb 1997 | A |
5603331 | Heemels et al. | Feb 1997 | A |
5630835 | Brownlee | May 1997 | A |
5650759 | Hittman et al. | Jul 1997 | A |
5683432 | Goedeke et al. | Nov 1997 | A |
5694952 | Lidman et al. | Dec 1997 | A |
5697958 | Paul et al. | Dec 1997 | A |
5733313 | Barreras et al. | Mar 1998 | A |
5752976 | Duffin et al. | May 1998 | A |
5752977 | Grevious et al. | May 1998 | A |
5759199 | Snell et al. | Jun 1998 | A |
5764699 | Needham et al. | Jun 1998 | A |
5766232 | Grevious et al. | Jun 1998 | A |
5807397 | Barreras | Sep 1998 | A |
5833603 | Kovacs et al. | Nov 1998 | A |
5843139 | Goedeke et al. | Dec 1998 | A |
5861019 | Sun et al. | Jan 1999 | A |
5881101 | Furman et al. | Mar 1999 | A |
5904708 | Goedeke | May 1999 | A |
5919210 | Lurie et al. | Jul 1999 | A |
5940384 | Carney et al. | Aug 1999 | A |
6009350 | Renken | Dec 1999 | A |
6083248 | Thompson | Jul 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6115583 | Brummer et al. | Sep 2000 | A |
6115634 | Donders et al. | Sep 2000 | A |
6115636 | Ryan | Sep 2000 | A |
6128528 | Erickson et al. | Oct 2000 | A |
6155208 | Schell et al. | Dec 2000 | A |
6167310 | Grevious | Dec 2000 | A |
6167312 | Goedeke | Dec 2000 | A |
6169925 | Villaseca et al. | Jan 2001 | B1 |
6200265 | Walsh et al. | Mar 2001 | B1 |
6223083 | Rosar | Apr 2001 | B1 |
6240317 | Villaseca et al. | May 2001 | B1 |
6263246 | Goedeke et al. | Jul 2001 | B1 |
6275737 | Mann | Aug 2001 | B1 |
6309350 | VanTassel et al. | Oct 2001 | B1 |
6329920 | Morrison et al. | Dec 2001 | B1 |
6336903 | Bardy | Jan 2002 | B1 |
6388628 | Dettloff et al. | May 2002 | B1 |
6424867 | Snell et al. | Jul 2002 | B1 |
6427088 | Bowman, IV et al. | Jul 2002 | B1 |
6434429 | Kraus et al. | Aug 2002 | B1 |
6443891 | Grevious | Sep 2002 | B1 |
6453198 | Torgerson et al. | Sep 2002 | B1 |
6456256 | Amundson et al. | Sep 2002 | B1 |
6456875 | Wilkinson et al. | Sep 2002 | B1 |
6470215 | Kraus et al. | Oct 2002 | B1 |
6482154 | Haubrich et al. | Nov 2002 | B1 |
6490487 | Kraus et al. | Dec 2002 | B1 |
6527729 | Turcott | Mar 2003 | B1 |
6531982 | White et al. | Mar 2003 | B1 |
6535766 | Thompson et al. | Mar 2003 | B1 |
6562000 | Thompson et al. | May 2003 | B2 |
6564104 | Nelson et al. | May 2003 | B2 |
6564105 | Starkweather et al. | May 2003 | B2 |
6574503 | Ferek-Petric | Jun 2003 | B2 |
6574509 | Kraus et al. | Jun 2003 | B1 |
6574510 | Von Arx et al. | Jun 2003 | B2 |
6577900 | Silvian | Jun 2003 | B1 |
6577901 | Thompson et al. | Jun 2003 | B2 |
6582365 | Hines et al. | Jun 2003 | B1 |
6585644 | Lebel et al. | Jul 2003 | B2 |
6600952 | Snell et al. | Jul 2003 | B1 |
6609029 | Mann et al. | Aug 2003 | B1 |
6614406 | Amundson et al. | Sep 2003 | B2 |
6622043 | Kraus et al. | Sep 2003 | B1 |
6622050 | Thompson | Sep 2003 | B2 |
6624786 | Boyle | Sep 2003 | B2 |
6648821 | Lebel et al. | Nov 2003 | B2 |
6659948 | Lebel et al. | Dec 2003 | B2 |
6662048 | Balczewski et al. | Dec 2003 | B2 |
6671328 | Poon et al. | Dec 2003 | B1 |
6675045 | Mass et al. | Jan 2004 | B2 |
6687546 | Lebel et al. | Feb 2004 | B2 |
6708065 | Von Arx et al. | Mar 2004 | B2 |
6716165 | Flanders et al. | Apr 2004 | B1 |
6741886 | Yonce | May 2004 | B2 |
6763269 | Cox | Jul 2004 | B2 |
6801807 | Abrahamson | Oct 2004 | B2 |
6804559 | Kraus et al. | Oct 2004 | B1 |
6809701 | Amundson et al. | Oct 2004 | B2 |
6844854 | Johnson et al. | Jan 2005 | B2 |
6868288 | Thompson | Mar 2005 | B2 |
6889081 | Hsu | May 2005 | B2 |
6907291 | Snell et al. | Jun 2005 | B1 |
6951596 | Green et al. | Oct 2005 | B2 |
6970735 | Uber, III et al. | Nov 2005 | B2 |
6978181 | Snell | Dec 2005 | B1 |
6985088 | Goetz et al. | Jan 2006 | B2 |
6985773 | Von Arx et al. | Jan 2006 | B2 |
6993393 | Von Arx et al. | Jan 2006 | B2 |
7013178 | Reinke et al. | Mar 2006 | B2 |
7027872 | Thompson | Apr 2006 | B2 |
7047076 | Li et al. | May 2006 | B1 |
7069086 | Von Arx | Jun 2006 | B2 |
7107085 | Doi | Sep 2006 | B2 |
7110823 | Whitehurst et al. | Sep 2006 | B2 |
7324012 | Mann et al. | Jan 2008 | B2 |
7668596 | Von Arx et al. | Feb 2010 | B2 |
7729776 | Von Arx et al. | Jun 2010 | B2 |
7738964 | Von Arx et al. | Jun 2010 | B2 |
7860574 | Von Arx et al. | Dec 2010 | B2 |
8041432 | Von Arx et al. | Oct 2011 | B2 |
8046080 | Von Arx et al. | Oct 2011 | B2 |
20010027331 | Thompson | Oct 2001 | A1 |
20010047125 | Quy | Nov 2001 | A1 |
20020013614 | Thompson | Jan 2002 | A1 |
20020019606 | Lebel et al. | Feb 2002 | A1 |
20020049480 | Lebel et al. | Apr 2002 | A1 |
20020062139 | Ding | May 2002 | A1 |
20020065539 | Von Arx et al. | May 2002 | A1 |
20020065540 | Lebel et al. | May 2002 | A1 |
20020147388 | Mass et al. | Oct 2002 | A1 |
20020159545 | Ramesh et al. | Oct 2002 | A1 |
20030018369 | Thompson et al. | Jan 2003 | A1 |
20030028902 | Cubley et al. | Feb 2003 | A1 |
20030041866 | Linberg et al. | Mar 2003 | A1 |
20030050535 | Bowman, IV et al. | Mar 2003 | A1 |
20030083719 | Shankar et al. | May 2003 | A1 |
20030114897 | Von Arx et al. | Jun 2003 | A1 |
20030114898 | Von Arx et al. | Jun 2003 | A1 |
20030135246 | Mass et al. | Jul 2003 | A1 |
20030146835 | Carter | Aug 2003 | A1 |
20030149459 | Von Arx et al. | Aug 2003 | A1 |
20030174069 | Goetz et al. | Sep 2003 | A1 |
20040030260 | Von Arx | Feb 2004 | A1 |
20040047434 | Waltho | Mar 2004 | A1 |
20040102815 | Balczewski et al. | May 2004 | A1 |
20040260363 | Arx et al. | Dec 2004 | A1 |
20050204134 | Von Arx et al. | Sep 2005 | A1 |
20050240245 | Bange et al. | Oct 2005 | A1 |
20050245992 | Persen et al. | Nov 2005 | A1 |
20050288736 | Persen et al. | Dec 2005 | A1 |
20060025834 | Von Arx et al. | Feb 2006 | A1 |
20060116744 | Von Arx et al. | Jun 2006 | A1 |
20080262573 | Seeberger et al. | Oct 2008 | A1 |
20080288024 | Abrahamson | Nov 2008 | A1 |
20100106224 | Von Arx et al. | Apr 2010 | A1 |
20100152816 | Von Arx et al. | Jun 2010 | A1 |
20110066211 | Von Arx et al. | Mar 2011 | A1 |
Number | Date | Country |
---|---|---|
10119393 | Jan 2002 | DE |
0168640 | Jan 1986 | EP |
0607638 | Jul 1994 | EP |
0607638 | Jul 1994 | EP |
1050265 | Nov 2000 | EP |
1062985 | Dec 2000 | EP |
1308184 | May 2003 | EP |
1495783 | Jan 2005 | EP |
2001251451 | Sep 2001 | JP |
2001274901 | Oct 2001 | JP |
2001285337 | Oct 2001 | JP |
2002112347 | Apr 2002 | JP |
2002132962 | May 2002 | JP |
2003299150 | Oct 2003 | JP |
2003348228 | Dec 2003 | JP |
2004094544 | Mar 2004 | JP |
2004104774 | Apr 2004 | JP |
2005281027 | Oct 2005 | JP |
WO-9500202 | Jan 1995 | WO |
WO-9819400 | May 1998 | WO |
WO-9912302 | Mar 1999 | WO |
WO-03053515 | Jul 2003 | WO |
WO-2005000397 | Jan 2005 | WO |
WO-2005099817 | Oct 2005 | WO |
WO-2006020546 | Feb 2006 | WO |
WO-2006020549 | Feb 2006 | WO |
Entry |
---|
“U.S. Appl. No. 10/071,255, Response and Preliminary Amendment filed Oct. 20, 2004 to Restriction Requirement mailed Sep. 28, 2004”, 7 pgs. |
“U.S. Appl. No. 10/025,183, Appeal Brief filed Dec. 29, 2005”, 27 pgs. |
“U.S. Appl. No. 10/025,183, Final Office Action mailed Jan. 13, 2005”, 7 pgs. |
“U.S. Appl. No. 10/025,183, Final Office Action mailed May 25, 2005”, 9 pgs. |
“U.S. Appl. No. 10/025,183, Final Office Action mailed Jul. 31, 2006”, 7 pgs. |
“U.S. Appl. No. 10/025,183, Final Office Action mailed Aug. 3, 2004”, 7 pgs. |
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Feb. 15, 2006”, 5 pgs. |
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Mar. 4, 2004”, 5 pgs. |
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Mar. 26, 2007”, 4 pgs. |
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Dec. 10, 2007”, 4 pgs. |
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 14, 2007”, 4 pgs. |
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 18, 2008”, 7 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Jan. 31, 2007 to Final Office Action mailed Jul. 31, 2006”, 11 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Apr. 13, 2005 to Final Office Action mailed Jan. 13, 2005”, 11 pgs. |
“U.S. Appl. No. 10/025,183, Response filed May 12, 2008 to Non-Final Office Action mailed Dec. 10, 2007”, 10 pgs. |
“U.S. Appl. No. 10/025,183, Response filed May 15, 2006 to Non-Final Office Action mailed Feb. 15, 2006”, 11 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Jun. 2, 2004 to Non-Final Office Action mailed Mar. 4, 2004”, 11 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Jun. 12, 2009 to Non Final Office Action mailed Feb. 19, 2009”, 10 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Jun. 26, 2007 to Non-Final Office Action mailed Mar. 26, 2007”, 14 pgs. |
“U.S. Appl. No. 10/025,183, Response filed Dec. 3, 2004 to Final Office Action mailed Aug. 3, 2004”, 11 pgs. |
“U.S. Appl. No. 10/025,223, Final Office Action mailed Aug. 16, 2004”, 8 pgs. |
“U.S. Appl. No. 10/025,223, Final Office Action mailed Sep. 10, 2004”, 7 pgs. |
“U.S. Appl. No. 10/025,223, Non-Final Office Action mailed Mar. 1, 2005”, 6 pgs. |
“U.S. Appl. No. 10/025,223, Non-Final Office Action mailed Mar. 19, 2004”, 5 pgs. |
“U.S. Appl. No. 10/025,223, Notice of Allowance mailed Aug. 10, 2005”, 4 pgs. |
“U.S. Appl. No. 10/025,223, Final Office Action mailed Aug. 16, 2004”, 9 pgs. |
“U.S. Appl. No. 10/025,223, Non Final Office Action mailed Mar. 1, 2005”, 8 pgs. |
“U.S. Appl. No. 10/025,223, Non Final Office Action mailed Mar. 19, 2004”, 6 pgs. |
“U.S. Appl. No. 10/025,223, Notice of Allowance mailed Aug. 10, 2005”, 6 pgs. |
“U.S. Appl. No. 10/025,223, Response filed Jan. 10, 2005 to Final Office Action mailed Sep. 10, 2004”, 10 pgs. |
“U.S. Appl. No. 10/025,223, Response filed Jun. 21, 2004 to Non Final Office Action mailed Mar. 19, 2004”, 9 pgs. |
“U.S. Appl. No. 10/025,223, Response filed Jun. 30, 2005 to Non Final Office Action mailed Mar. 1, 2005”, 10 pgs. |
“U.S. Appl. No. 10/025,223, Response filed Nov. 11, 2004 to Final Office Action mailed Aug. 16, 2004”, 16 pgs. |
“U.S. Appl. No. 10/071,255, Response and Preliminary Amendment filed Oct. 20, 2004 to Restriction Requirement mailed Sep. 28, 2004”, 10 pgs. |
“U.S. Appl. No. 10/071,255, Restriction Requirement mailed Sep. 28, 2004”, 5 pgs. |
“U.S. Appl. No. 10/071,255, Non Final Office Action mailed Jan. 7, 2005”, 6 pgs. |
“U.S. Appl. No. 10/071,255, Notice of allowance mailed Jun. 15, 2005”, 4 pgs. |
“U.S. Appl. No. 10/071,255, Preliminary Amendment filed Oct. 5, 2005”, 12 pgs. |
“U.S. Appl. No. 10/071,255, Response filed Apr. 7, 2005 non-final office action mailed Jan. 7, 2005”, 12 pgs. |
“U.S. Appl. No. 10/744,943, Response filed Oct. 22, 2007 to Non-Final Office Action Mailed Apr. 20, 2007”, 9 pages. |
“U.S. Appl. No. 10/744,943, Final Office Action mailed Feb. 21, 2008”, 15 pgs. |
“U.S. Appl. No. 10/914,496, Final Office Action mailed May 23, 2007”, 11 pgs. |
“U.S. Appl. No. 10/914,496, Non Final Office Action mailed Dec. 5, 2006”, 9 pgs. |
“U.S. Appl. No. 10/914,496, Non-Final Office Action mailed Mar. 18, 2008”, 9 pgs. |
“U.S. Appl. No. 10/914,496, Response filed Mar. 5, 2007 to Non Final office Action mailed Dec. 5, 2006”, 13 pgs. |
“U.S. Appl. No. 10/914,496, Response filed Aug. 22, 2007 to Final Office Action mailed May 23, 2007”, 12 pgs. |
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed May 29, 2007”, 11 pgs. |
“U.S. Appl. No. 10/914,499, Final Office Action mailed Jan. 24, 2008”, 10 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Apr. 14, 2008 to Final Office Action mailed Jan. 24, 2008”, 11 pgs. |
“U.S. Appl. No. 10/914,638, Final Office Action mailed Apr. 17, 2007”, 10 pgs. |
“U.S. Appl. No. 10/914,638, Notice of Allowance mailed Mar. 21, 2008”, 4 pgs. |
“U.S. Appl. No. 10/914,638, Notice of Allowance mailed Oct. 22, 2007”, 4 pgs. |
“U.S. Appl. No. 10/914,638, Response filed Jan. 18, 2007 to Non-Final Office Action mailed Oct. 18, 2006”, 16 pgs. |
“U.S. Appl. No. 10/914,638, Response filed Aug. 17, 2007 to Final Office Action mailed Apr. 17, 2007”, 8 pgs. |
“U.S. Appl. No. 10/914,638,Non-Final Office Action mailed Oct. 18, 2006”, 9 pgs. |
“U.S. Appl. No. 11/068,478, Non-Final Office Action mailed Dec. 17, 2007”, 15 pgs. |
“U.S. Appl. No. 11/068,478, Response filed Mar. 17, 2008 to Non-Final Office Action mailed Dec. 17, 2007”, 19 pgs. |
“U.S. Appl. No. 11/101,142, Non-Final Office Action mailed Jun. 20, 2007”, 8 pgs. |
“U.S. Appl. No. 11/101,142, Notice of Allowance mailed Nov. 27, 2007”, 5 pgs. |
“U.S. Appl. No. 11/101,142, Response filed Jun. 4, 2007 to Restriction Requirement Response mailed May 3, 2007”, 7 pgs. |
“U.S. Appl. No. 11/101,142, Response filed Sep. 20, 2007 to Non-Final Office Action mailed Jun. 20, 2007”, 7 pgs. |
“U.S. Appl. No. 11/101,142, Restriction Requirement mailed May 3, 2007”, 5 pgs. |
“U.S. Appl. No. 11/101,196, Non Final Office Action mailed Mar. 29, 2007”, 8 pgs. |
“U.S. Appl. No. 11/101,196, Notice of Allowance mailed Aug. 27, 2007”, 5 pgs. |
“U.S. Appl. No. 11/101,196, Response filed Jun. 29, 2007 to Non Final Office Action mailed Mar. 29, 2007”, 8 pgs. |
“U.S. Appl. No. 11/244,273, Restriction Requirement mailed Jul. 22, 2008”, 10 pgs. |
“U.S. Appl. No. 11/244,273, Response filed Mar. 2, 2009 to Non-Final Office Action mailed Nov. 28, 2008”, 13 pages. |
“U.S. Appl. No. 11/244,273, Non-Final Office Action mailed on Nov. 28, 2008”, 7 pgs. |
“U.S. Appl. No. 11/244,273, Notice of Allowance mailed Oct. 5, 2009”, 7 pgs. |
“U.S. Appl. No. 11/244,273, Response filed Aug. 12, 2009 to Ex Parte Quayle mailed Jun. 12, 2009”, 4 pgs. |
“U.S. Appl. No. 11/244,273, Response filed Oct. 22, 2008 to Restriction Requirement mailed Jul. 22, 2008”, 13 pgs. |
“U.S. Appl. No. 11/325,584, Final Office Action mailed Oct. 24, 2008”, 5 pgs. |
“U.S. Appl. No. 11/325,584, Non-Final Office Action mailed Apr. 10, 2008”, 6 pgs. |
“U.S. Appl. No. 11/325,584, Response filed Jan. 22, 2009 to Final Office Action mailed Oct. 24, 2008”, 6 pgs. |
“U.S. Appl. No. 11/325,584, Response filed Jul. 10, 2008 to Non Final Office Action mailed Apr. 10, 2008”, 9 pgs. |
“International Application No. PCT/US02/40488, International Search Report mailed May 9, 2003”, 7 pgs. |
“International Application No. PCT/US03/03748, International Search Report mailed Oct. 20, 2003”, 5 pgs. |
“International Application No. PCT/US2005/028052, International Preliminary Report on Patentability mailed Feb. 22, 2007”, 8 pgs. |
“International Application No. PCT/US2005/028059, International Preliminary Report on Patentability mailed Feb. 13, 2007”, 9 pgs. |
“International Application No. PCT/US2005/028059, International Search Report and Written Opinion mailed Jan. 12, 2005”, 13 pgs. |
“Part III—Department of Health and Human Services, Office of the Secretary—45 CFR Part 142—Security and Electronic Signature Standards; Proposed Rule”, Federal Register, 63(155), (Aug. 12, 1998), 43241-43280. |
“Public Law 104-191 [H.R. 3103]—Health Insurance Portability and Accountability Act of 1996”, United States Public Laws—104th Congress—2nd Session, (Aug. 21, 1996), 78 pgs. |
Bange, Joseph E, et al., “System and Method for RF Transceiver Duty Cycling in an Implantable Medical Device”, U.S. Appl. No. 11/101,196, filed Apr. 7, 2005, 19 pgs. |
Diffie, W., “The First Ten Years of Public-Key Cryptography”, Proceedings of the IEEE, 76(5), (May 1988), 560-577. |
Hammond, E., “Perspectives on Implementation of Administrative Simplification Provisions of P.L. 104-191”, National Committee on Vital and Health Statistics, Subcommittee on Health Data Needs, Standards and Security, (Feb. 11, 1997), 4 pgs. |
Healy, S. J., et al., “System and Method for Providing Secure Exchange of Sensitive Information With an Implantable Medical Device”, U.S. Appl. No. 10/801,150, filed Mar. 15, 2004, 30 pgs. |
Quiles, S., “Secure Remote Access for an Implantable Medical Device”, U.S. Appl. No. 10/914,641, filed Aug. 9, 2004, 41 pgs. |
Quiles, Sylvia, “Automatic Power Control for a Radio Frequency Transceiver of an Implantable Device”, U.S. Appl. No. 10/914,496, filed Aug. 9, 2004, 23 pgs. |
Seeberger, M., “Dynamic Telemetry Link Selection for an Implantable Device”, U.S. Appl. No. 10/914,638, filed Aug. 9, 2004, 35 pgs. |
Von Arx, J., et al., “System and Method for Securely Authenticating a Data Exchange Session With an Implantable Medical Device”, U.S. Appl. No. 10/800,806, filed Mar. 15, 2004, 47 pgs. |
Von Arx, Jeffrey, “Dynamic Telemetry Encoding for an Implantable Medical Device”, U.S. Appl. No. 10/870,324, filed Jun. 17, 2004, 38 pgs. |
“U.S. Appl. No. 10/025,183, Non-Final Office Action mailed Feb. 19, 2009”, 5 pgs. |
“U.S. Appl. No. 10/025,183, Notice of Allowance mailed Sep. 28, 2009”, 5 pgs. |
“U.S. Appl. No. 10/914,496, Final Office Action mailed Sep. 22, 2008”, 12 pgs. |
“U.S. Appl. No. 10/914,496, Notice of Allowance mailed Jan. 16, 2009”, 4 pgs. |
“U.S. Appl. No. 10/914,496, Response filed Jun. 18, 2008 to Non-Final Office Action mailed Mar. 18, 2008”, 10 pgs. |
“U.S. Appl. No. 10/914,496, Response filed Nov. 24, 2008 to Final Office Action mailed Sep. 22, 2008”, 9 pgs. |
“U.S. Appl. No. 10/914,496, Response filed Dec. 12, 2007 to Restriction Requirement mailed Nov. 13, 2007”, 7 pgs. |
“U.S. Appl. No. 10/914,496, Restriction Requirement mailed Nov. 13, 2007”, 5 pgs. |
“U.S. Appl. No. 10/914,499, Advisory Action mailed Aug. 4, 2009”, 5 pgs. |
“U.S. Appl. No. 10/914,499, Final Office Action mailed May 12, 2009”, 10 pgs. |
“U.S. Appl. No. 10/914,499, Final Office Action mailed Jul. 20, 2010”, 5 pgs. |
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Feb. 3, 2010”, 11 pgs. |
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Apr. 24, 2008”, 5 pgs. |
“U.S. Appl. No. 10/914,499, Non-Final Office Action mailed Nov. 5, 2008”, 12 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Feb. 5, 2009 to Non-Final Office Action mailed Nov. 5, 2008”, 12 pgs. |
“U.S. Appl. No. 10/914,499, Response filed May 3, 2010 to Non-Final Office Action mailed Feb. 3, 2010”, 12 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Jun. 30, 2008 to Non-Final Office Action mailed Apr. 24, 2008”, 10 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Jul. 13, 2009 to Final Office Action mailed May 12, 2009”, 10 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Aug. 31, 2010 to Final Office Action mailed Jul. 20, 2010”, 10 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Oct. 23, 2007 to Non-Final Office Action mailed May 29, 2007”, 11 pgs. |
“U.S. Appl. No. 10/914,499, Response filed Nov. 10, 2009 to Advisory Action mailed Aug. 4, 2009”, 12 pgs. |
“U.S. Appl. No. 11/039,200, Non-Final Office Action mailed Aug. 3, 2006”, 10 pgs. |
“U.S. Appl. No. 11/039,200, Notice of Allowance mailed Dec. 15, 2006”, 4 pgs. |
“U.S. Appl. No. 11/039,200, Response filed Nov. 2, 2006 to Non-Final office action mailed Aug. 3, 2006”, 9 pgs. |
“U.S. Appl. No. 11/068,478, Advisory Action mailed Sep. 16, 2008”, 3 pgs. |
“U.S. Appl. No. 11/068,478, Final Office Action mailed Jun. 2, 2008”, 17 pgs. |
“U.S. Appl. No. 11/068,478, Non-Final Office Action mailed Jan. 2, 2009”, 11 pgs. |
“U.S. Appl. No. 11/068,478, Notice of Allowance mailed Jun. 9, 2009”, 7 pgs. |
“U.S. Appl. No. 11/068,478, Response filed Mar. 30, 2009 to Non-Final Office Action mailed Jan. 2, 2009”, 20 pgs. |
“U.S. Appl. No. 11/068,478, Response filed Aug. 4, 2008 to Final Office Action mailed Jun. 2, 2008”, 19 pgs. |
“U.S. Appl. No. 11/068,478, Response filed Nov. 3, 2008 to Advisory Action mailed Sep. 16, 2008”, 17 pgs. |
“U.S. Appl. No. 11/325,564, Examiner Interview Summary mailed Jun. 24, 2009”, 2 pgs. |
“U.S. Appl. No. 11/325,584, Non-Final Office Action mailed Mar. 24, 2009”, 5 pgs. |
“U.S. Appl. No. 11/325,584, Notice of Allowance mailed Mar. 23, 2010”, 4 pgs. |
“U.S. Appl. No. 11/325,584, Notice of Allowance mailed Oct. 21, 2009”, 5 pgs. |
“U.S. Appl. No. 11/325,584, Response filed Jun. 24, 2009 to Non-Final Office Action mailed Mar. 24, 2009”, 9 pgs. |
“U.S. Appl. No. 11/456,942, Advisory Action mailed May 7, 2009”, 6 pgs. |
“U.S. Appl. No. 11/456,942, Final Office Action mailed Mar. 10, 2009”, 15 pgs. |
“U.S. Appl. No. 11/456,942, Non-Final Office Action mailed Aug. 18, 2008”, 15 pgs. |
“U.S. Appl. No. 11/456,942, Notice of Allowance mailed Jul. 17, 2009”, 13 pgs. |
“U.S. Appl. No. 11/456,942, Response filed May 4, 2009 to Final Office Action mailed Mar. 10, 2009”, 9 pgs. |
“U.S. Appl. No. 11/456,942, Response filed Jun. 4, 2009 to Advisory Action mailed May 7, 2009”, 10 pgs. |
“U.S. Appl. No. 11/456,942, Response filed Nov. 18, 2008 to Non-Final Office Action mailed Aug. 18, 2008”, 10 pgs. |
“U.S. Appl. No. 11/733,339, Interview Summary mailed Aug. 13, 2009”, 2 pgs. |
“U.S. Appl. No. 11/733,339, Non-Final Office Action mailed Apr. 30, 2009”, 10 pgs. |
“U.S. Appl. No. 11/733,339, Non-Final Office Action mailed Sep. 9, 2009”, 9 pgs. |
“U.S. Appl. No. 11/733,339, Notice of Allowance mailed Feb. 25, 2010”, 6 pgs. |
“U.S. Appl. No. 11/733,339, Notice of Allowance mailed Apr. 21, 2010”, 6 pgs. |
“U.S. Appl. No. 11/733,339, Response filed Dec. 4, 2009 to Non-Final Office Action mailed Sep. 9, 2009”, 11 pgs. |
“U.S. Appl. No. 12/145,343, Final Office Action mailed Mar. 8, 2011”, 9 pgs. |
“U.S. Appl. No. 12/145,343, Non-Final Office Action mailed Oct. 26, 2010”, 10 pgs. |
“U.S. Appl. No. 12/145,343, Response filed Jan. 25, 2011 to Non-Final Office Action mailed Oct. 26, 2010”, 9 pgs. |
“U.S. Appl. No. 12/145,343, Response filed May 9, 2011 to Final Office Action mailed Mar. 8, 2011”, 9 pgs. |
“U.S. Appl. No. 12/145,343, Response filed Sep. 14, 2010 to Restriction Requirement mailed Aug. 26, 2010”, 8 pgs. |
“U.S. Appl. No. 12/145,343, Restriction Requirement mailed Aug. 26, 2010”, 7 pgs. |
“U.S. Appl. No. 12/648,687, Notice of Allowance mailed Aug. 17, 2010”, 7 pgs. |
“U.S. Appl. No. 12/713,669, Non-Final Office Action mailed Mar. 2, 2011”, 5 pgs. |
“U.S. Appl. No. 12/713,669, Response filed May 16, 2011 to Non-Final Office Action mailed Mar. 2, 2011”, 8 pgs. |
“European Application No. 02799254.4 Office Action Mailed Sep. 23, 2009”, 4 pgs. |
“European Application No. 02799254.4, Communication mailed Oct. 2, 2006”, 4 pgs. |
“European Application No. 02799254.4, Response filed Feb. 15, 2010 to Office Action Mailed Sep. 23, 2009”, 12 pgs. |
“European Application No. 02799254.4, Response filed Apr. 2, 2007 to Communication mailed Oct. 2, 2006”, 18 pgs. |
“European Application No. 03709003.2, Office Action mailed Jul. 27, 2010”, 6 pgs. |
“European Application No. 05783799.9, Communication pursuant to Article 94(3) EPC mailed on Jun. 16, 2009”, 3 pgs. |
“European Application No. 05783882.3, Communication pursuant to Article 94(3) EPC mailed Jun. 16, 2009”, 3 pgs. |
“European Application No. 05783882.3, Response filed Oct. 22, 2009 to Communication mailed Jun. 16, 2009”, 7 pgs. |
“European Application Serial No. 03709003.2, Response filed Jan. 27, 2011 to Office Action mailed Jul. 27, 2010”, 10. |
“European Application Serial No. 05783799.9, Response filed Oct. 23, 2009 to Communication mailed Jun. 16, 2009”, 9 pgs. |
“International Application No. PCT/US2005/011606, International Search Report and Written Opinion mailed Jul. 26, 2005”, 12 pgs. |
“International Application No. PCT/US2005/028052, International Search Report and Written Opinion mailed Nov. 29, 2005”, 12 pgs. |
“International Application No. PCT/US2007/069424, International Search Report mailed Dec. 27, 2007”, 4 pgs. |
“International Application No. PCT/US2007/069424, Written Opinion mailed Dec. 27, 2007”, 9 pgs. |
“International Application No. PCT/US2007/069426, International Search Report mailed Dec. 27, 2007”, 4 pgs. |
“International Application No. PCT/US2007/069426, Written Opinion mailed Dec. 27, 2007”, 8 pgs. |
“Japanese Application Serial No. 2007-525695, Office Action mailed Feb. 3, 2011”, (w/ English Translation), 5 pgs. |
“Japanese Application Serial No. 2007-525695, Response filed Apr. 20, 2011 to Non Final Office Action mailed Feb. 3, 2011”, 5 pgs. |
Bange, Joseph E, et al., “Implantable Medical Device Telemetry With Adaptive Frequency Hopping”, U.S. Appl. No. 11/456,937, filed Jul. 12, 2006, 35 pgs. |
Bange, Joseph E, et al., “Implantable Medical Device Telemetry With Periodic Frequency Hopping”, U.S. Appl. No. 11/456,942, filed Jul. 12, 2006, 43 pgs. |
Golmie, N., et al., “The Evolution of Wireless LANs and PANs—Bluetooth and WLAN coexistence: challenges and solutions”, IEEE Personal Communications, 10(6), (Dec. 2003), 22-29. |
Katoozi, M., et al., “On-Demand Retransmission of Data With an Implantable Medical Device”, U.S. Appl. No. 10/870,328, filed Jun. 17, 2004, 30 pgs. |
Quiles, S., “U.S. Appl. No. 10/914,499, filed Aug. 9, 2004”, 30 pgs. |
Rawat, Prashant, et al., “U.S. Appl. No. 10/744,943, filed Dec. 22, 2003”, 34 pgs. |
Von Arx, J. A., et al., “A Telemetry Duty Cycle Management System for an Implantable Medical Device”, U.S. Appl. No. 11/325,584, filed Jan. 4, 2006, 37 pgs. |
“U.S. Appl. No. 12/713,669, Notice of Allowance mailed Jun. 24, 2011”, 5 pgs. |
“U.S. Appl. No. 12/950,359, Notice of Allowance mailed Jun. 23, 2011”, 7 pgs. |
“U.S. Appl. No. 12/145,343, Examiner Interview Summary mailed Apr. 12, 2012”, 3 pgs. |
“U.S. Appl. No. 12/145,343, Final Office Action mailed Feb. 2, 2012”, 12 pgs. |
“U.S. Appl. No. 12/145,343, Non Final Office Action mailed Jun. 7, 2012”, 13 pgs. |
“U.S. Appl. No. 12/145,343, Non Final Office Action mailed Sep. 30, 2011”, 10 pgs. |
“U.S. Appl. No. 12/145,343, Response filed Apr. 27, 2012 to Final Office Action mailed Feb. 2, 2012”, 11 pgs. |
“U.S. Appl. No. 12/145,343, Response filed Dec. 28, 2011 to Non Final Office Action mailed Sep. 30, 2011”, 12 pgs. |
“Japanese Application Serial No. 2007-525695, Non Final Office Action mailed Oct. 7, 2011”, (w/ English translation), 8 pgs. |
“Japanese Application Serial No. 2007-525695, Office Action mailed Jun. 20, 2012”, (w/ English Translation), 4 pgs. |
“Japanese Application Serial No. 2007-525695, Office Action Response filed Jan. 6, 2012”, (w/ English translation), 10 pgs. |
“Japanese Application Serial No. 2007-525695, Response filed Aug. 27, 2012 to Office Action mailed Jun. 20, 2012”, (w/ English translation of claims), 8 pgs. |
Number | Date | Country | |
---|---|---|---|
20100114233 A1 | May 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11244273 | Oct 2005 | US |
Child | 12684303 | US | |
Parent | 10071255 | Feb 2002 | US |
Child | 11244273 | US |