Cardiac pacing electrically stimulates the heart when the heart's natural pacemaker and/or conduction system fails to provide synchronized atrial and ventricular contractions at appropriate rates and intervals for a patient's needs. Such bradycardia pacing provides relief from symptoms and even life support for hundreds of thousands of patients. Cardiac pacing may also give electrical overdrive stimulation intended to suppress or convert tachyarrhythmias, again supplying relief from symptoms and preventing or terminating arrhythmias that could lead to sudden cardiac death.
Cardiac pacing is usually performed by a pulse generator implanted subcutaneously or sub-muscularly in or near a patient's pectoral region. Implantable cardioverter-defibrillator (ICD) pulse generators usually include cardiac pacing functions, both for bradycardia support and for overdrive stimulation. The generator usually connects to the proximal end of one or more implanted leads, the distal end of which contains one or more electrodes for positioning adjacent to the inside or outside wall of a cardiac chamber. The leads have an insulated electrical conductor or conductors for connecting the pulse generator to electrodes in the heart. Such electrode leads typically have lengths of 50 to 70 centimeters.
A conventional pulse generator may be connected to more than one electrode-lead. For example, atrio-ventricular pacing, also commonly called dual-chamber pacing, involves a single pulse generator connected to one electrode-lead usually placed in the right atrium and a second electrode-lead usually placed in the right ventricle. Such a system can electrically sense heartbeat signals and deliver pacing pulses separately in each chamber. In typical use, the dual-chamber pacing system paces the atrium if no atrial heartbeat is sensed since a predetermined time, and then paces the ventricle if no ventricular heartbeat is sensed within a predetermined time after the natural or paced atrial beat. Such pulse generators can also alter the timing of atrial and ventricular pacing pulses when sensing a ventricular beat that is not preceded by an atrial beat within a predetermined time; that is, a ventricular ectopic beat or premature ventricular contraction. Consequently, dual-chamber pacing involves pacing and sensing in an atrium and a ventricle, and internal communication element so that an event in either chamber can affect timing of pacing pulses in the other chamber.
Recently, left-ventricular cardiac pacing has been practiced to ameliorate heart failure; a practice termed cardiac resynchronization therapy (CRT). CRT has been practiced with electrode-leads and a pulse generator, either an implantable cardioverter-defibrillator (CRT-D) or an otherwise conventional pacemaker (CRT-P). The left-ventricular pacing conventionally uses an electrode in contact with cardiac muscle in that chamber. The corresponding electrode-lead is usually placed endocardially in a transvenous manner through the coronary sinus vein, or epicardially. Left-ventricular pacing is usually practiced together with right-atrial and right-ventricular pacing with a single implanted pulse generator connected to three electrode-leads. CRT pulse generators can independently vary the time between an atrial event and right-ventricular pacing, and the time between an atrial event and left-ventricular pacing, so that the left ventricular pacing pulse can precede, follow, or occur at the same time as the right-ventricular pacing pulse. Similarly to dual-chamber pacing, systems with left-ventricular pacing also change atrial and ventricular pacing timing in response to premature ventricular contractions. Consequently, CRT-D involves pacing in an atrium and in two ventricles, sensing in the atrium and at least one ventricle, and an internal communication element so that an event in the atrium can affect timing of pacing pulses in each ventricle, and an internal communication element so that an event in at least one ventricle can affect timing of pacing pulses in the atrium and the other ventricle.
Pulse generator parameters are usually interrogated and modified by a programming device outside the body, via a loosely-coupled transformer with one inductance within the body and another outside, or via electromagnetic radiation with one antenna within the body and another outside.
Although more than one hundred thousand ICD and CRT-D systems are implanted annually, several problems are known.
A conventional pulse generator has an interface for connection to and disconnection from the electrode leads that carry signals to and from the heart. Usually at least one male connector molding has at least one additional terminal pin not required for defibrillation functions at the proximal end of the electrode lead. The at least one male connector mates with at least one corresponding female connector molding and terminal block within the connector molding at the pulse generator. Usually a setscrew is threaded in at least one terminal block per electrode lead to secure the connection electrically and mechanically. One or more O-rings usually are also supplied to help maintain electrical isolation between the connector moldings. A setscrew cap or slotted cover is typically included to provide electrical insulation of the setscrew. The complex connection between connectors and leads provides multiple opportunities for malfunction.
For example, failure to introduce the lead pin completely into the terminal block can prevent proper connection between the generator and electrode.
Failure to insert a screwdriver correctly through the setscrew slot, causing damage to the slot and subsequent insulation failure.
Failure to engage the screwdriver correctly in the setscrew can cause damage to the setscrew and preventing proper connection.
Failure to tighten the setscrew adequately also can prevent proper connection between the generator and electrode, however over-tightening of the setscrew can cause damage to the setscrew, terminal block, or lead pin, and prevent disconnection if necessary for maintenance.
Fluid leakage between the lead and generator connector moldings, or at the setscrew cover, can prevent proper electrical isolation.
Insulation or conductor breakage at a mechanical stress concentration point where the lead leaves the generator can also cause failure.
Inadvertent mechanical damage to the attachment of the connector molding to the generator can result in leakage or even detachment of the molding.
Inadvertent mechanical damage to the attachment of the connector molding to the lead body, or of the terminal pin to the lead conductor, can result in leakage, an open-circuit condition, or even detachment of the terminal pin and/or molding.
The lead body can be cut inadvertently during surgery by a tool, or cut after surgery by repeated stress on a ligature used to hold the lead body in position. Repeated movement for hundreds of millions of cardiac cycles can cause lead conductor breakage or insulation damage anywhere along the lead body.
Although leads are available commercially in various lengths, in some conditions excess lead length in a patient exists and is to be managed. Usually the excess lead is coiled near the pulse generator. Repeated abrasion between the lead body and the generator due to lead coiling can result in insulation damage to the lead.
Friction of the lead against the clavicle and the first rib, known as subclavian crush, can result in damage to the lead.
In dual-chamber pacing in an ICD, and in CRT-D, multiple leads are implanted in the same patient and sometimes in the same vessel. Abrasion between these leads for hundreds of millions of cardiac cycles can cause insulation breakdown or even conductor failure.
Subcutaneous ICDs that do not use endocardial, transvenous or epicardial lead wires, can deliver defibrillation using subcutaneous electrodes. However, pacing the heart from subcutaneous electrodes results in diaphragmatic stimulation which is uncomfortable to the patient if used in long-term therapy. Therefore pacing therapies such as bradycardia pacing therapy, anti-tachycardia therapy, atrial overdrive pacing for the prevention of arrhythmias, dual chamber pacing for atrio-ventricular synchronization and CRT therapies are inappropriate.
According to an embodiment of a cardiac pacing system, one or more leadless cardiac pacemakers are configured for implantation in electrical contact with a cardiac chamber and configured for performing cardiac pacing functions in combination with a co-implanted implantable cardioverter-defibrillator (ICD). The leadless cardiac pacemaker comprises at least two leadless electrodes configured for delivering cardiac pacing pulses, sensing evoked and/or natural cardiac electrical signals, and bidirectionally communicating with the co-implanted ICD.
Embodiments of the invention relating to both structure and method of operation may best be understood by referring to the following description and accompanying drawings, in which similar reference characters denote similar elements throughout the several views:
In some embodiments of an illustrative cardiac pacing system, one or more leadless cardiac pacemakers with low-power conducted communication can perform single-chamber pacing, dual-chamber pacing, CRT-D, or other pacing, co-implanted with an ICD, enabling functionality extending beyond what is possible or appropriate for conventional subcutaneous ICDs.
A system of leadless cardiac pacemakers enables pacing in conjunction with an implantable cardioverter-defibrillator (ICD) for usage in single-chamber, dual-chamber, CRT-D, and other multi-chamber cardiac pacing schemes.
Various embodiments of a system of an implantable cardioverter-defibrillator (ICD) and one or more leadless cardiac pacemakers are described. The individual leadless cardiac pacemakers can be substantially enclosed in a hermetic housing suitable for placement on or attachment to the inside or outside of a cardiac chamber. The pacemaker can have at least two electrodes located within, on, or near the housing, for delivering pacing pulses to and sensing electrical activity from the muscle of the cardiac chamber, and for bidirectional communication with at least one other co-implanted leadless cardiac pacemaker and optionally with another device outside the body. The housing can contain a primary battery to provide power for pacing, sensing, and communication. The housing can also contain circuits for sensing cardiac activity from the electrodes, receiving information from at least one other device via the electrodes, generating pacing pulses for delivery via the electrodes, transmitting information to at least one other device via the electrodes, monitoring device health, and controlling these operations in a predetermined manner.
A cardiac pacing system includes cardiac pacing in conjunction with an ICD and can supplement the functionality of ICDs with cardiac pacing functions, extending beyond functionality of conventional ICD-pacing arrangements.
The cardiac pacing system comprises a leadless cardiac pacemaker or pacemakers adapted to perform cardiac pacing functions with a co-implanted ICD, without a pacing electrode-lead separate from the leadless cardiac pacemaker, without a communication coil or antenna in the leadless cardiac pacemaker, and without an additional requirement on battery power in the leadless cardiac pacemaker for transmitted communication.
In some embodiments, a cardiac pacing system comprises an ICD with one or more leadless pacemakers for implantation adjacent to the inside or outside wall of a cardiac chamber, without the need for a connection between the leadless pulse generator and an electrode lead that can be connected or disconnected during implantation and repair procedures, and without the need for a lead body.
In some embodiments of a cardiac pacing system, communication between the implanted leadless cardiac pacemaker or pacemakers and other devices, including any co-implanted leadless cardiac pacemakers, the co-implanted ICD, and optionally a device external to the body, uses conducted communication via the same electrodes used for pacing, without the need for an antenna or telemetry coil.
Some embodiments and/or arrangements can implement communication between an implanted leadless cardiac pacemaker and other devices with power requirements similar to those for cardiac pacing, to enable optimization of battery performance. For example, transmission from the leadless cardiac pacemaker adds no power while reception adds a limited amount of power, such as about 25 microwatt.
A cardiac pacemaker or pacemakers are adapted for implantation in the human body. In a specific embodiment, one or more leadless cardiac pacemakers can be co-implanted with an implantable cardioverter-defibrillator (ICD). Each leadless cardiac pacemaker uses two or more electrodes located within, on, or within two centimeters of the housing of the pacemaker, for pacing and sensing at the cardiac chamber, for bidirectional communication with the ICD, optionally with at least one other leadless cardiac pacemaker, and optionally with at least one other device outside the body.
Referring to
The leadless cardiac pacemakers 102 can communicate with one another and/or communicate with a non-implanted programmer and/or the implanted ICD 106 via the same electrodes 108 that are also used to deliver pacing pulses. Usage of the electrodes 108 for communication enables the one or more leadless cardiac pacemakers 102 for antenna-less and telemetry coil-less communication.
The leadless cardiac pacemakers 102 can be configured to communicate with one another and to communicate with a non-implanted programmer 106 via communication that has outgoing communication power requirements essentially met by power consumed in cardiac pacing.
In some embodiments, the individual leadless cardiac pacemaker 102 can comprise a hermetic housing 110 configured for placement on or attachment to the inside or outside of a cardiac chamber 104 and at least two leadless electrodes 108 proximal to the housing 110 and configured for bidirectional communication with at least one other device 106 within or outside the body. For example,
The one or more leadless electrodes 108 can be configured to communicate bidirectionally among the multiple leadless cardiac pacemakers and/or the implanted ICD to coordinate pacing pulse delivery using messages that identify an event at an individual pacemaker originating the message and a pacemaker receiving the message react as directed by the message depending on the origin of the message. A pacemaker or pacemakers that receive the message react as directed by the message depending on the message origin or location. In some embodiments or conditions, the two or more leadless electrodes 108 can be configured to communicate bidirectionally among the one or more leadless cardiac pacemakers 102 and/or the ICD 106 and transmit data including designated codes for events detected or created by an individual pacemaker. Individual pacemakers can be configured to issue a unique code corresponding to an event type and a location of the sending pacemaker.
Information communicated on the incoming communication channel can include but is not limited to pacing rate, pulse duration, sensing threshold, and other parameters commonly programmed externally in conventional pacemakers. Information communicated on the outgoing communication channel can include but is not limited to programmable parameter settings, pacing and sensing event counts, battery voltage, battery current, device health, and other information commonly displayed by external programmers used with conventional pacemakers. The outgoing communication channel can also echo information from the incoming channel, to confirm correct programming.
In some embodiments, information encoded on the leadless cardiac pacemakers can be used to enhance the sensitivity and specificity of the ICD such as, for example, a subcutaneous-only implantable defibrillator. Illustratively, a subcutaneously-only defibrillator senses only far-field signals, making difficult extraction of atrial information as well as uniquely identifying atrial depolarization from ventricular depolarization. When a subcutaneous-only defibrillator is used in combination with one or more leadless cardiac pacemakers, the information derived from the pacing pulse for each leadless pacemaker can be gathered and used to identify atrial and ventricular depolarization without ambiguity.
The leadless cardiac pacemaker 102 can communicate the information listed hereinabove with the implanted ICD 106, or with a programmer outside the body, or both.
For example, in some embodiments an individual pacemaker 102 of the one or more leadless cardiac pacemakers can be configured to deliver a coded pacing pulse with a code assigned according to pacemaker location and configured to transmit a message to one or more other leadless cardiac pacemakers via the coded pacing pulse wherein the code identifies the individual pacemaker originating an event. The pacemaker or pacemakers receiving the message are adapted to respond to the message in a predetermined manner depending on type and location of the event.
In some embodiments or conditions, individual pacemakers 102 can deliver a coded pacing pulse with a code assigned according to pacemaker location and configured to transmit a message to at least one of the leadless cardiac pacemakers via the coded pacing pulse wherein the code identifies the individual pacemaker originating an event. The individual pacemakers can be further configured to deliver a pacing pulse in absence of encoding whereby, for dual-chamber cardiac pacing, a pacing pulse that is not generated in a first cardiac pacemaker that senses the pacing pulse is necessarily generated in a second cardiac pacemaker. Accordingly, neither the use of a code to identify the chamber corresponding to a pacing pulse, nor the use of a code to identify the type of pulse (whether paced or sensed) is a necessary step in a simple system such as a dual chamber pacing system disclosed in the specification.
Moreover, information communicated on the incoming channel can also include a message from another leadless cardiac pacemaker signifying that the other leadless cardiac pacemaker has sensed a heartbeat or has delivered a pacing pulse, and identifies the location of the other pacemaker. Similarly, information communicated on the outgoing channel can also include a message to another leadless cardiac pacemaker or pacemakers, or to the ICD, that the sending leadless cardiac pacemaker has sensed a heartbeat or has delivered a pacing pulse at the location of the sending pacemaker.
In some embodiments and in predetermined conditions, an individual pacemaker 102 of the one or more leadless cardiac pacemakers can be configured to communicate to one or more other implanted pacemakers indication of the occurrence of a sensed heartbeat at the individual pacemaker location via generation of a coded pacing pulse triggered by the sensed heartbeat in a natural refractory period following the sensed heartbeat.
Referring again to
An embodiment of a cardiac pacing system 100 comprises an implantable cardioverter-defibrillator (ICD) 106 and at least one leadless cardiac pacemaker 102 configured for implantation in electrical contact with a cardiac chamber and for performing cardiac rhythm management functions in combination with the implantable ICD 106. The implantable ICD 106 and the one or more leadless cardiac pacemakers 102 configured for leadless intercommunication by information conduction through body tissue.
In another embodiment, a cardiac pacing system 100 comprises one or more leadless cardiac pacemaker 102 or pacemakers configured for implantation in electrical contact with a cardiac chamber 104 and configured to perform cardiac pacing functions in combination with a co-implanted implantable cardioverter-defibrillator (ICD) 106. The leadless cardiac pacemaker or pacemakers 102 are configured to intercommunicate and/or to communicate with a non-implanted programmer and/or the implanted ICD 106 via two or more electrodes 108 that are used for delivering pacing pulses. The pacemakers 102 are configured for antenna-less and telemetry coil-less communication.
In a further embodiment, a cardiac pacing system 100 comprises at least one leadless cardiac pacemaker 102 configured for implantation in electrical contact with a cardiac chamber 104 and configured to perform cardiac pacing functions in combination with a co-implanted implantable cardioverter-defibrillator (ICD) 106. The leadless cardiac pacemaker or pacemakers 102 comprise at least two leadless electrodes 108 configured for delivering cardiac pacing pulses, sensing evoked and/or natural cardiac electrical signals, and transmitting information to the co-implanted ICD 106.
In another example embodiment, a cardiac pacing system 100 comprises at least one leadless cardiac pacemaker 102 configured for implantation in electrical contact with a cardiac chamber 104 and configured to perform cardiac pacing functions in combination with a co-implanted implantable cardioverter-defibrillator (ICD) 106. The leadless cardiac pacemaker or pacemakers 102 comprising at least two leadless electrodes 108 configured for delivering cardiac pacing pulses, sensing evoked and/or natural cardiac electrical signals, and receiving information from the co-implanted ICD 106.
As shown in the Illustrative embodiments, a leadless cardiac pacemaker 102 can comprise two or more leadless electrodes 108 configured for delivering cardiac pacing pulses, sensing evoked and/or natural cardiac electrical signals, and bidirectionally communicating with the co-implanted ICD 106. A leadless cardiac pacemaker 102 can be configured to communicate with other pacemakers and/or communicate with a non-implanted programmer via communication that has communication power requirements essentially met by power consumed in cardiac pacing. For example, the leadless cardiac pacemaker 102 can be configured to communicate with other pacemakers and with a non-implanted programmer via communication that has negligible transmission power requirements in addition to power consumed in cardiac pacing.
Individual pacemakers of the one or more leadless cardiac pacemakers 102 can be configured for operation in a particular location and a particular functionality at manufacture and/or at programming by an external programmer. Bidirectional communication among the multiple leadless cardiac pacemakers can be arranged to communicate notification of a sensed heartbeat or delivered pacing pulse event and encoding type and location of the event to another implanted pacemaker or pacemakers. The pacemaker or pacemakers receiving the communication decode the information and respond depending on location of the receiving pacemaker and predetermined system functionality.
In some embodiments, individual pacemakers 102 of the one or more leadless cardiac pacemakers can be configured to receive conducted communication from a co-implanted cardioverter-defibrillator (ICD) 106 that configures the pacemakers 102 to deliver overdrive anti-tachycardia pacing in response to a detected tachyarrhythmia.
Also shown in
One suitable primary battery uses beta-voltaic technology, licensed to BetaBatt Inc. of Houston, Tex., USA, and developed under a trade name DEC™ Cell, in which a silicon wafer captures electrons emitted by a radioactive gas such as tritium. The wafer is etched in a three-dimensional surface to capture more electrons. The battery is sealed in a hermetic package which entirely contains the low-energy particles emitted by tritium, rendering the battery safe for long-term human implant from a radiological-health standpoint. Tritium has a half-life of 12.3 years so that the technology is more than adequate to meet a design goal of a lifetime exceeding 5 years.
Current from the positive terminal 140 of primary battery 114 flows through a shunt 144 to a regulator circuit 146 to create a positive voltage supply 148 suitable for powering the remaining circuitry of the pacemaker 102. The shunt 144 enables the battery current monitor 136 to provide the processor 112 with an indication of battery current drain and indirectly of device health.
The illustrative power supply can be a primary battery 114 such as a beta-voltaic converter that obtains electrical energy from radioactivity. In some embodiments, the power supply can be selected as a primary battery 114 that has a volume less than approximately 1 cubic centimeter.
The leadless cardiac pacemaker or pacemakers 102 can be configured to detect a natural cardiac depolarization, time a selected delay interval, and deliver an information-encoded pulse during a refractory period following the natural cardiac depolarization. By encoding information in a pacing pulse, power consumed for transmitting information is not significantly greater than the power used for pacing. Information can be transmitted through the communication channel with no separate antenna or telemetry coil. Communication bandwidth is low with only a small number of bits encoded on each pulse.
In some embodiments, information can be encoded using a technique of gating the pacing pulse for very short periods of time at specific points in the pacing pulse. During the gated sections of the pulse, no current flows through the electrodes of a leadless cardiac pacemaker. Timing of the gated sections can be used to encode information. The specific length of a gated segment depends on the programmer's ability to detect the gated section. A certain amount of smoothing or low-pass filtering of the signal can be expected from capacitance inherent in the electrode/skin interface of the programmer as well as the electrode/tissue interface of the leadless cardiac pacemaker. A gated segment is set sufficiently long in duration to enable accurate detection by the programmer, limiting the amount of information that can be transmitted during a single pacing pulse. Accordingly, a technique for communication can comprise generating stimulation pulses on stimulating electrodes of an implanted biostimulator and encoding information onto generated stimulation pulses. Encoding information onto the pulses can comprise gating the stimulation pulses for selected durations at selected timed sections in the stimulation pulses whereby gating removes current flow through the stimulating electrodes and timing of the gated sections encodes the information.
Another method of encoding information on pacing pulses involves varying the timing between consecutive pacing pulses in a pulse sequence. Pacing pulses, unless inhibited or triggered, occur at predetermined intervals. The interval between any two pulses can be varied slightly to impart information on the pulse series. The amount of information, in bits, is determined by the time resolution of the pulse shift. The steps of pulse shifting are generally on the order of microseconds. Shifting pulses by up to several milliseconds does not have an effect on the pacing therapy and cannot be sensed by the patient, yet significant information can be transmitted by varying pulse intervals within the microsecond range. The method of encoding information in variation of pulses is less effective if many of the pulses are inhibited or triggered. Accordingly, a technique for communication can comprise generating stimulation pulses on stimulating electrodes of an implanted biostimulator and encoding information onto generated stimulation pulses comprising selectively varying timing between consecutive stimulation pulses.
Alternatively or in addition to encoding information in gated sections and/or pulse interval, overall pacing pulse width can be used to encode information.
The three described methods of encoding information on pacing pulses can use the programmer to distinguish pacing pulses from the patient's normal electrocardiogram, for example by recognition of the specific morphology of the pacing pulse compared to the R-wave generated during the cardiac cycle. For example, the external programmer can be adapted to distinguish a generated cardiac pacing pulse from a natural cardiac depolarization in an electrocardiogram by performing comparative pattern recognition of a pacing pulse and an R-wave produced during a cardiac cycle.
In an illustrative embodiment, the primary battery 114 can be selected to source no more than 70 microwatts instantaneously since a higher consumption may cause the voltage across the battery terminals to collapse. Accordingly in one illustrative embodiment the circuits depicted in
In various embodiments, the system can manage power consumption to draw limited power from the battery, thereby reducing device volume. Each circuit in the system can be designed to avoid large peak currents. For example, cardiac pacing can be achieved by discharging a tank capacitor (not shown) across the pacing electrodes. Recharging of the tank capacitor is typically controlled by a charge pump circuit. In a particular embodiment, the charge pump circuit is throttled to recharge the tank capacitor at constant power from the battery.
Implantable systems that communicate via long distance radio-frequency (RF) schemes, for example Medical Implant Communication Service (MICS) transceivers, which exhibit a peak power requirement on the order of 10 milliwatts, and other RF or inductive telemetry schemes are unable to operate without use of an additional accumulator. Moreover, even with the added accumulator, sustained operation would ultimately cause the voltage across the battery to collapse.
In some embodiments, the controller 112 in one leadless cardiac pacemaker 102 can access signals on the electrodes 108 and can examine output pulse duration from another pacemaker for usage as a signature for determining triggering information validity and, for a signature arriving within predetermined limits, activating delivery of a pacing pulse following a predetermined delay of zero or more milliseconds. The predetermined delay can be preset at manufacture, programmed via an external programmer, or determined by adaptive monitoring to facilitate recognition of the triggering signal and discriminating the triggering signal from noise. In some embodiments or in some conditions, the controller 112 can examine output pulse waveform from another leadless cardiac pacemaker for usage as a signature for determining triggering information validity and, for a signature arriving within predetermined limits, activating delivery of a pacing pulse following a predetermined delay of zero or more milliseconds.
Also shown in
Several techniques and structures can be used for attaching the housing 110 to the interior or exterior wall of cardiac chamber muscle 104.
A helix 226 and slot 228 enable insertion of the device endocardially or epicardially through a guiding catheter. A screwdriver stylet can be used to rotate the housing 110 and force the helix 226 into muscle 104, thus affixing the electrode 108A in contact with stimulable tissue. Electrode 108B serves as an indifferent electrode for sensing and pacing. The helix 226 may be coated for electrical insulation, and a steroid-eluting matrix may be included near the helix to minimize fibrotic reaction, as is known in conventional pacing electrode-leads.
In other configurations, suture holes 224 and 225 can be used to affix the device directly to cardiac muscle with ligatures, during procedures where the exterior surface of the heart is exposed.
Other attachment structures used with conventional cardiac electrode-leads including tines or barbs for grasping trabeculae in the interior of the ventricle, atrium, or coronary sinus may also be used in conjunction with or instead of the illustrative attachment structures.
Referring to
Referring to
When the depicted leadless pacemaker 102 is used in combination with at least one other pacemaker or other pulse generator in the cardiac pacing system 100 and is generating a pacing pulse but is not optionally sending data for communication, the pacing waveform of the leadless pacemaker 102 can also resemble the conventional pacing pulse shown in
Referring to
As controlled by processor 112, pulse generator 116 selectively generates or does not generate a notch in each timing window 508, 509, 510, and 511 so that the device 102 encodes four bits of information in the pacing pulse. A similar scheme with more timing windows can send more or fewer bits per pacing pulse. The width of the notches is small, for example approximately 15 microseconds, so that the delivered charge and overall pulse width, specifically the sum of the widths of the shorter pulses, in the pacing pulse is substantially unchanged from that shown in
In a leadless cardiac pacemaker, a technique can be used to conserve power when detecting information carried on pacing pulses from other implanted devices. The leadless cardiac pacemaker can have a receiving amplifier that implements multiple gain settings and uses a low-gain setting for normal operation. The low-gain setting could be insufficiently sensitive to decode gated information on a pacing pulse accurately but could detect whether the pacing pulse is present. If an edge of a pacing pulse is detected during low-gain operation, the amplifier can be switched quickly to the high-gain setting, enabling the detailed encoded data to be detected and decoded accurately. Once the pacing pulse has ended, the receiving amplifier can be set back to the low-gain setting. For usage in the decoding operation, the receiving amplifier is configured to shift to the more accurate high-gain setting quickly when activated. Encoded data can be placed at the end of the pacing pulse to allow a maximum amount of time to invoke the high-gain setting.
As an alternative or in addition to using notches in the stimulation pulse, the pulses can be generated with varying off-times, specifically times between pulses during which no stimulation occurs. The variation of off-times can be small, for example less than 10 milliseconds total, and can impart information based on the difference between a specific pulse's off-time and a preprogrammed off-time based on desired heart rate. For example, the device can impart four bits of information with each pulse by defining 16 off-times centered around the preprogrammed off-time.
In some embodiments, a pacemaker 102 can use the leadless electrodes 108 to communicate bidirectionally among multiple leadless cardiac pacemakers and transmit data including designated codes for events detected or created by an individual pacemaker wherein the codes encode information using pacing pulse width.
To ensure the leadless cardiac pacemaker functions correctly, a specific minimum internal supply voltage is maintained. When pacing tank capacitor charging occurs, the supply voltage can drop from a pre-charging level which can become more significant when the battery nears an end-of-life condition and has reduced current sourcing capability. Therefore, a leadless cardiac pacemaker can be constructed with a capability to stop charging the pacing tank capacitor when the supply voltage drops below a specified level. When charging ceases, the supply voltage returns to the value prior to the beginning of tank capacitor charging.
In another technique, the charge current can be lowered to prevent the supply voltage from dropping below the specified level. However, lowering the charge current can create difficulty in ensuring pacing rate or pacing pulse amplitude are maintained, since the lower charge current can extend the time for the pacing tank capacitor to reach a target voltage level.
The illustrative scheme for transmitting data does not significantly increase the current consumption of the pacemaker. For example, the pacemaker could transmit data continuously in a loop, with no consumption penalty.
The illustrative schemes for transmitting data enable assignment of designated codes to events detected or caused by a leadless cardiac pacemaker, such as sensing a heartbeat or delivering a pacing pulse at the location of the pacemaker that senses the event. Individual leadless cardiac pacemakers 102 in a system 100 can be configured, either at manufacture or with instructions from an external programmer or from the co-implanted ICD 106 as described hereinabove, to issue a unique code corresponding to the type of event and location of the leadless cardiac pacemaker. By delivery of a coded pacing pulse with a code assigned according to the pacemaker location, a leadless cardiac pacemaker can transmit a message to any and all other leadless cardiac pacemakers 102 and the ICD 106 implanted in the same patient, where the code signifies the origin of the event. Each other leadless cardiac pacemaker can react appropriately to the conveyed information in a predetermined manner encoded in the internal processor 112, as a function of the type and location of the event coded in the received pulse. The ICD 106 can also use the information for arrhythmia detection. A leadless cardiac pacemaker 102 can thus communicate to any and all other co-implanted leadless cardiac pacemakers and to the co-implanted ICD 106 the occurrence of a sensed heartbeat at the originating pacemaker's location by generating a coded pacing pulse triggered by the sensed event. Triggered pacing occurs in the natural refractory period following the heartbeat and therefore has no effect on the chamber where the leadless cardiac pacemaker is located.
Referring again to
The illustrative leadless pacemaker 102 could otherwise receive triggering information from the other pulse generator 106 implanted within the body via a pulse-modulated or frequency-modulated carrier signal, instead of via the pacing pulses of the other pulse generator 106.
With regard to operating power requirements in the leadless cardiac pacemaker 102, for purposes of analysis, a pacing pulse of 5 volts and 5 milliamps amplitude with duration of 500 microseconds and a period of 500 milliseconds has a power requirement of 25 microwatts.
In an example embodiment of the leadless pacemaker 102, the processor 112 typically includes a timer with a slow clock that times a period of approximately 10 milliseconds and an instruction-execution clock that times a period of approximately 1 microsecond. The processor 112 typically operates the instruction-execution clock only briefly in response to events originating with the timer, communication amplifier 134, or cardiac sensing amplifier 132. At other times, only the slow clock and timer operate so that the power requirement of the processor 112 is no more than 5 microwatts.
For a pacemaker that operates with the aforementioned slow clock, the instantaneous power consumption specification, even for a commercially-available micropower microprocessor, would exceed the battery's power capabilities and would require an additional filter capacitor across the battery to prevent a drop of battery voltage below the voltage necessary to operate the circuit. The filter capacitor would add avoidable cost, volume, and potentially lower reliability.
For example, a microprocessor consuming only 100 microamps would require a filter capacitor of 5 microfarads to maintain a voltage drop of less than 0.1 volt, even if the processor operates for only 5 milliseconds. To avoid the necessity for such a filter capacitor, an illustrative embodiment of a processor can operate from a lower frequency clock to avoid the high instantaneous power consumption, or the processor can be implemented using dedicated hardware state machines to supply a lower instantaneous peak power specification.
In a pacemaker, the cardiac sensing amplifier typically operates with no more than 5 microwatts. A communication amplifier at 100 kHz operates with no more than 25 microwatts. The battery ammeter and battery voltmeter operate with no more than 1 microwatt each.
A pulse generator typically includes an independent rate limiter with a power consumption of no more than 2 microwatts.
The total power consumption of the pacemaker is thus 64 microwatts, less than the disclosed 70-microwatt battery output.
Improvement attained by the illustrative cardiac pacing system 100 and leadless cardiac pacemaker 102 is apparent.
In a specific embodiment, the outgoing communication power requirement plus the pacing power requirement does not exceed approximately 25 microwatts. In other words, outgoing communication adds essentially no power to the power used for pacing.
The illustrative leadless cardiac pacemaker 102 can have sensing and processing circuitry that consumes no more than 10 microwatts as in conventional pacemakers.
The described leadless cardiac pacemaker 102 can have an incoming communication amplifier for receiving triggering signals and optionally other communication which consumes no more than 25 microwatts.
Furthermore, the leadless cardiac pacemaker 102 can have a primary battery that exhibits an energy density of at least 3 watt-hours per cubic centimeter (W·h/cc).
In an illustrative application of the cardiac pacing system 100, one or more leadless cardiac pacemakers 102 can be co-implanted with an ICD 106 in a single patient to provide a system for single-chamber pacing, dual-chamber pacing, CRT-D, or any other multi-chamber pacing application. Each leadless cardiac pacemaker in the system can use the illustrative communication structures to communicate the occurrence of a sensed heartbeat or a delivered pacing pulse at the location of sensing or delivery, and a communication code can be assigned to each combination of event type and location. Each leadless cardiac pacemaker can receive the transmitted information, and the code of the information can signify that a paced or sensed event has occurred at another location and indicate the location of occurrence. The receiving leadless cardiac pacemaker's processor 112 can decode the information and respond appropriately, depending on the location of the receiving pacemaker and the desired function of the system.
The implanted cardioverter-defibrillator (ICD) 106 can comprise a case and be fitted with a pair of electrodes mounted on or near the case. The ICD 106 can be configured to receive and transmit conducted communication using a pulse modulated or frequency modulated carrier signal whereby the ICD 106 can detect communication pulses from co-implanted leadless cardiac pacemakers 102 and transmit programming information to the co-implanted leadless cardiac pacemakers 102. In some embodiments, an implanted cardioverter-defibrillator (ICD) 106 configured to receive conducted communication using two implantable electrodes.
For clarity of illustration, descriptions of the atrial, right ventricular, and left-ventricular leadless cardiac pacemakers in respective
Referring to
In a cardiac pacing system, the multiple leadless cardiac pacemakers can comprise an atrial leadless cardiac pacemaker implanted in electrical contact to an atrial cardiac chamber. The atrial leadless cardiac pacemaker can be configured or programmed to perform several control operations 700 in combination with one or more other pacemakers. In a wait state 702 the atrial leadless cardiac pacemaker waits for an earliest occurring event of multiple events including a sensed atrial heartbeat 704, a communication of an event sensed on the at least two leadless electrodes encoding a pacing pulse marking a heartbeat 706 at a ventricular leadless cardiac pacemaker, or timeout of an interval timed locally in the atrial leadless cardiac pacemaker shown as escape interval timeout 708. The atrial pacemaker responds to a sensed atrial heartbeat 704 by generating 710 an atrial pacing pulse that signals to one or more other pacemakers and optionally to the co-implanted ICD that an atrial heartbeat has occurred, encoding the atrial pacing pulse with a code signifying an atrial location and a sensed event type. The atrial pacing pulse can be encoded using the technique shown in
The atrial leadless cardiac pacemaker can further operate in response to another pacemaker. The atrial pacemaker can detect 706 a signal originating from a co-implanted ventricular leadless cardiac pacemaker. The atrial pacemaker can examine the elapsed amount of the atrial-to-atrial (AA) escape time interval since a most recent atrial heartbeat and determine 714 whether the signal originating from the co-implanted ventricular leadless cardiac pacemaker is premature. Thus, if the atrial leadless cardiac pacemaker detects a signal originating from a co-implanted ventricular leadless cardiac pacemaker, shown as sensed ventricular pacing 706, then the atrial device examines the amount of the escape interval elapsed since the last atrial heartbeat at decision point 714 to determine whether the ventricular event is “premature”, meaning too late to be physiologically associated with the last atrial heartbeat and in effect premature with respect to the next atrial heartbeat. In the absence 716 of a premature signal, the atrial pacemaker waits 702 for an event with no effect on atrial pacing. In contrast if the signal is premature 718, the pacemaker restarts 720 a ventricle-to-atrium (VA) escape interval that is shorter than the atrial-to-atrial (AA) escape interval and is representative of a typical time from a ventricular beat to a next atrial beat in sinus rhythm, specifically the atrial interval minus the atrio-ventricular conduction time. After starting 720 the VA interval, the atrial leadless cardiac pacemaker returns to wait state 702, whereby a ventricular premature beat can be said to “recycle” the atrial pacemaker. The pacemaker responds to timeout of the atrial-to-atrial (AA) escape interval 708 by delivering an atrial pacing pulse 710, causing an atrial heartbeat. The atrial pacing pulse encodes the paced type and atrial location of an atrial heartbeat event.
The atrial leadless cardiac pacemaker can be further configured to time a prolonged post-ventricular atrial refractory period (PVARP) after recycling in presence of the premature signal, thereby preventing pacemaker-mediated tachycardia (PMT). Otherwise, if a received ventricular pacing signal evaluated at decision point 714 is not found to be premature, then the atrial leadless cardiac pacemaker follows transition 716 and re-enters the wait state 702 without recycling, thus without any effect on the timing of the next atrial pacing pulse.
Referring to
The right-ventricular leadless cardiac pacemaker responds to the sensed right-ventricular heartbeat 804 by generating 810 a right-ventricular pacing pulse that signals to at least one other pacemaker of the multiple cardiac pacemakers and optionally to the co-implanted ICD that a right-ventricular heartbeat has occurred. Thus, when a sensed right-ventricular heartbeat occurs 804, the right-ventricular leadless cardiac pacemaker generates 810 a right-ventricular pacing pulse, not to pace the heart but rather to signal to another leadless cardiac pacemaker or pacemakers that a right-ventricular heartbeat has occurred. The right-ventricular pacing pulse can be encoded with a code signifying the right-ventricular location and a sensed event type. The right-ventricular pacing pulse is coded in the manner shown in
The right-ventricular leadless cardiac pacemaker can further be configured to set the ventricular-to-ventricular (VV) escape interval longer than a predetermined atrial-to-atrial (AA) escape interval to enable backup ventricular pacing at a low rate corresponding to the VV escape interval in case of failure of a triggered signal from a co-implanted atrial leadless cardiac pacemaker. Typically, the VV (right) escape interval is longer than the AA interval depicted in
The right-ventricular leadless cardiac pacemaker can respond to timeout of a first occurring escape interval 808 by delivering 810 a right ventricular pacing pulse, causing a right ventricular heartbeat. The right ventricular pacing pulse can encode information including paced type and right-ventricular location of a right ventricular heartbeat event.
When the right-ventricular escape interval times out 808, the right-ventricular leadless cardiac pacemaker delivers 810 a right-ventricular pacing pulse. Because no other right-ventricular heartbeat has occurred during the duration of the VV escape interval, the pacing pulse 810 does not fall in the ventricles' natural refractory period and therefore should effectively pace the ventricles, causing a ventricular heartbeat. The right-ventricular pacing pulse, coded in the manner shown in
The right-ventricular leadless cardiac pacemaker can further be configured to detect 806 a signal originating from a co-implanted atrial leadless cardiac pacemaker. The right-ventricular leadless cardiac pacemaker examines the elapsed amount of the ventricular-to-ventricular (VV) escape interval since a most recent right-ventricular heartbeat and determines 814 whether the signal originating from the co-implanted atrial leadless cardiac pacemaker is premature. An atrial event is defined as premature if too early to trigger an atrio-ventricular delay to produce a right-ventricular heartbeat. In the presence of a premature signal 816, the right-ventricular leadless cardiac pacemaker returns to the wait state 802 with no further action. Thus, a premature atrial beat does not affect ventricular pacing. In the absence of a premature signal 818, the right-ventricular leadless cardiac pacemaker starts 820 a right atrium to right ventricular (AV) escape interval that is representative of a typical time from an atrial beat to a right-ventricular beat in sinus rhythm. Thus a non-premature atrial event leads to starting 820 an AV (right) atrium to right-ventricular escape interval that represents a typical time from an atrial beat to a right-ventricular beat in normally-conducted sinus rhythm. After starting 820 the AV interval, the right-ventricular leadless cardiac pacemaker returns to the wait state 802 so that a non-premature atrial beat can “trigger” the right-ventricular pacemaker after a physiological delay. The right-ventricular leadless cardiac pacemaker also responds to timeout of either the VV escape interval and the AV escape interval 808 by delivering 810 a right ventricular pacing pulse, causing a right ventricular heartbeat. The right ventricular pacing pulse encodes paced type and right-ventricular location of a right ventricular heartbeat event.
Accordingly, co-implanted atrial and right-ventricular leadless cardiac pacemakers depicted in
Referring to
A cardiac pacing system, such as a CRT-D system, can include multiple leadless cardiac pacemakers including a left-ventricular leadless cardiac pacemaker implanted in electrical contact to a left-ventricular cardiac chamber. The left-ventricular leadless cardiac pacemaker can execute operations of an illustrative pacing method 900. In a wait state 902, the left-ventricular cardiac pacemaker waits 902 at the left-ventricular leadless cardiac pacemaker for an earliest occurring event of multiple events including a sensed communication 904 of a pacing pulse marking a heartbeat at an atrial leadless cardiac pacemaker and timeout 906 of a left ventricular escape interval. Generally, the sensed communication 904 can be the sensed communication of an event originating at another co-implanted leadless cardiac pacemaker, in the illustrative embodiment a pacing pulse marking a heartbeat at an atrial leadless cardiac pacemaker shown as sensed atrial pacing. The escape interval timeout 906 can be timeout of an interval timed locally in the left-ventricular leadless cardiac pacemaker. In the wait state 902 for the left-ventricular leadless cardiac pacemaker, operation is simplified and the left-ventricular pacemaker does not respond to left-ventricular heartbeats. Also, the left-ventricular cardiac pacemaker does not pace the left ventricle in the absence of a triggering signal from the atrial leadless cardiac pacemaker. The left-ventricular cardiac pacemaker responds to timeout 906 of the left ventricular escape interval by delivering 908 a left ventricular pacing pulse, causing a left ventricular heartbeat. The left ventricular pacing pulse encodes the type and location of a left ventricular heartbeat event. The left-ventricular pacing pulse can be coded in the manner shown in
The left-ventricular leadless cardiac pacemaker can be further configured detect a signal originating from a co-implanted atrial leadless cardiac pacemaker and examine the elapsed amount of the left ventricular escape interval since a most recent left-ventricular heartbeat. The left-ventricular cardiac pacemaker can determine 910 whether the signal originating from the co-implanted atrial leadless cardiac pacemaker is premature. If the left-ventricular leadless cardiac pacemaker detects sensed atrial pacing, then the left-ventricular device determines whether the atrial event is premature, meaning too early to trigger an atrio-ventricular delay to produce a left-ventricular heartbeat. In the presence of a premature signal 912, the left-ventricular cardiac pacemaker reverts to the wait state 902 and waits for an event with no effect on ventricular pacing so that a premature atrial beat does not affect ventricular pacing. In absence of a premature signal 914, the left-ventricular cardiac pacemaker starts 916 a left atrium to left ventricular (AV) escape interval that is representative of a typical time from an atrial beat to a left ventricular beat in normally-conducted sinus rhythm. As shown in the depicted embodiment, the AV (left) escape interval can have a different value from the AV (right) escape interval. After starting 916 the AV interval, the left-ventricular leadless cardiac pacemaker returns to wait state 902. Accordingly, a non-premature atrial beat can “trigger” the left-ventricular pacemaker after a physiological delay.
The left-ventricular cardiac pacemaker also responds to timeout 906 of the AV escape interval by delivering 908 a left ventricular pacing pulse, causing a left ventricular heartbeat. The left ventricular pacing pulse encodes paced type and left ventricular location of a left ventricular heartbeat event.
In various embodiments, the multiple leadless cardiac pacemakers can comprise a right ventricular leadless cardiac pacemaker and a left ventricular leadless cardiac pacemaker that are configured to operate with atrio-ventricular (AV) delays whereby a left ventricular pacing pulse can be delivered before, after, or substantially simultaneously with a right ventricular pacing pulse. For example, multiple co-implanted leadless cardiac pacemakers that function according to the state diagrams shown in
The co-implanted ICD can configure the leadless cardiac pacemakers via conducted communication in a similar manner to an external programmer. In particular, the ICD can configure them to deliver overdrive anti-tachycardia pacing in response to detected tachyarrhythmias.
In various embodiments, multiple co-implanted leadless cardiac pacemakers can be configured for multi-site pacing that synchronizes depolarization for tachyarrhythmia prevention.
The illustrative system can be useful in conjunction with an ICD, and more particularly with a subcutaneous ICD, for such an ICD has no other means to provide bradycardia support, anti-tachycardia pacing, and CRT.
Referring to
Two or more electrodes are coupled to the ICD and configured to transmit and/or receive conducted communication using a pulse-modulated or frequency-modulated carrier signal. The ICD can be configured to detect communication pulses from at least one co-implanted leadless cardiac pacemaker and transmit programming information to the at least one co-implanted leadless cardiac pacemaker.
The leadless cardiac pacemakers can be configured to broadcast information to the co-implanted ICD and/or at least one other pacemaker. The leadless cardiac pacemakers can further be configured to receive the code and react based on the code, location of the receiving leadless cardiac pacemaker, and predetermined system functionality.
In various embodiments, configurations, and conditions, the leadless cardiac pacemakers can be adapted to perform one or more cardiac pacing functions such as single-chamber pacing, dual-chamber pacing, cardiac resynchronization therapy with cardioversion/defibrillation (CRT-D), single-chamber overdrive pacing for prevention of tachyarrhythmias, single-chamber overdrive pacing for conversion of tachyarrhythmias, multiple-chamber pacing for prevention of tachyarrhythmias, multiple-chamber pacing for conversion of tachyarrhythmias, and the like.
Multiple leadless cardiac pacemakers can be configured for co-implantation in a single patient and multiple-chamber pacing including CRT-D. Bidirectional communication among the multiple leadless cardiac pacemakers can be adapted to communicate notification of a sensed heartbeat or delivered pacing pulse event and encoding type and location of the event to at least one pacemaker of the leadless cardiac pacemaker plurality. The one or more pacemakers that receive the communication can decode the information and react depending on location of the receiving pacemaker and predetermined system functionality.
In some embodiments, the atrial leadless cardiac pacemaker can encode an atrial pacing pulse that identifies synchronous pacing triggered by an atrial sensed event with a first code and encode an atrial pacing pulse that identifies atrial pacing following the AA escape interval with a second code distinct from the first code.
The atrial leadless cardiac pacemaker can, upon delivery of an atrial pacing pulse, time an atrial-to-atrial (AA) escape interval.
Referring to
In some embodiments, the right-ventricular leadless cardiac pacemaker can encode a right-ventricular pacing pulse that identifies synchronous pacing triggered by a right-ventricular sensed event with a first code and encode a right-ventricular pacing pulse that identifies right-ventricular pacing following a ventricular-to-ventricular (VV) escape interval with a second code distinct from the first code.
In some embodiments, the right-ventricular leadless cardiac pacemaker, upon delivery of a right-ventricular pacing pulse, can time a ventricular-to-ventricular (VV) escape interval.
Referring to
In some embodiments, the left-ventricular cardiac pacemaker can configure the left-ventricular leadless cardiac pacemaker for operation in cardiac resynchronization therapy (CRT-D).
Terms “substantially”, “essentially”, or “approximately”, that may be used herein, relate to an industry-accepted tolerance to the corresponding term. Such an industry-accepted tolerance ranges from less than one percent to twenty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. The term “coupled”, as may be used herein, includes direct coupling and indirect coupling via another component, element, circuit, or module where, for indirect coupling, the intervening component, element, circuit, or module does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. Inferred coupling, for example where one element is coupled to another element by inference, includes direct and indirect coupling between two elements in the same manner as “coupled”.
While the present disclosure describes various embodiments, these embodiments are to be understood as illustrative and do not limit the claim scope. Many variations, modifications, additions and improvements of the described embodiments are possible. For example, those having ordinary skill in the art will readily implement the steps necessary to provide the structures and methods disclosed herein, and will understand that the process parameters, materials, and dimensions are given by way of example only. The parameters, materials, and dimensions can be varied to achieve the desired structure as well as modifications, which are within the scope of the claims. Variations and modifications of the embodiments disclosed herein may also be made while remaining within the scope of the following claims. For example, although the description has some focus on the pacemaker, system, structures, and techniques can otherwise be applicable to other uses, for example multi-site pacing for prevention of tachycardias in the atria or ventricles. Phraseology and terminology employed herein are for the purpose of the description and should not be regarded as limiting. With respect to the description, optimum dimensional relationships for the component parts are to include variations in size, materials, shape, form, function and manner of operation, assembly and use that are deemed readily apparent and obvious to one of ordinary skill in the art and all equivalent relationships to those illustrated in the drawings and described in the specification are intended to be encompassed by the present description. Therefore, the foregoing is considered as illustrative only of the principles of structure and operation. Numerous modifications and changes will readily occur to those of ordinary skill in the art whereby the scope is not limited to the exact construction and operation shown and described, and accordingly, all suitable modifications and equivalents may be included.
This application is a continuation of U.S. patent application Ser. No. 14/885,853, filed Oct. 16, 2015, now U.S. Pat. No. 9,409,033, which is a divisional of U.S. patent application Ser. No. 14/318,201, filed Jun. 27, 2014, now U.S. Pat. No. 9,192,774, which is a divisional of U.S. patent application Ser. No. 13/866,803, filed Apr. 19, 2013, now U.S. Pat. No. 8,798,745, which is a divisional of U.S. patent application Ser. No. 11/549,599, filed Oct. 13, 2006, now U.S. Pat. No. 8,457,742, which application claims the benefit of priority to and incorporates herein by reference in its entirety for all purposes, U.S. Provisional Patent Application No. 60/726,706 entitled “LEADLESS CARDIAC PACEMAKER WITH CONDUCTED COMMUNICATION,” filed Oct. 14, 2005; 60/761,531 entitled “LEADLESS CARDIAC PACEMAKER DELIVERY SYSTEM,” filed Jan. 24, 2006; 60/729,671 entitled “LEADLESS CARDIAC PACEMAKER TRIGGERED BY CONDUCTED COMMUNICATION,” filed Oct. 24, 2005; 60/737,296 entitled “SYSTEM OF LEADLESS CARDIAC PACEMAKERS WITH CONDUCTED COMMUNICATION,” filed Nov. 16, 2005; 60/739,901 entitled “LEADLESS CARDIAC PACEMAKERS WITH CONDUCTED COMMUNICATION FOR USE WITH AN IMPLANTABLE CARDIOVERTER-DEFIBRILLATOR,” filed Nov. 26, 2005; 60/749,017 entitled “LEADLESS CARDIAC PACEMAKER WITH CONDUCTED COMMUNICATION AND RATE RESPONSIVE PACING,” filed Dec. 10, 2005; and 60/761,740 entitled “PROGRAMMER FOR A SYSTEM OF LEADLESS CARDIAC PACEMAKERS WITH CONDUCTED COMMUNICATION,” filed Jan. 24, 2006; all by Peter M. Jacobson.
Number | Name | Date | Kind |
---|---|---|---|
3199508 | Roth | Aug 1965 | A |
3212496 | Preston | Oct 1965 | A |
3218638 | Honig | Nov 1965 | A |
3241556 | Zacouto | Mar 1966 | A |
3478746 | Wilson | Nov 1969 | A |
3603881 | Thornton | Sep 1971 | A |
3727616 | Lenzkes | Apr 1973 | A |
3757778 | Graham | Sep 1973 | A |
3823708 | Lawhorn | Jul 1974 | A |
3830228 | Foner | Aug 1974 | A |
3835864 | Rasor et al. | Sep 1974 | A |
3836798 | Greatbatch | Sep 1974 | A |
3870051 | Brindley | Mar 1975 | A |
3872251 | Auerbach et al. | Mar 1975 | A |
3905364 | Cudahy et al. | Sep 1975 | A |
3940692 | Neilson | Feb 1976 | A |
3943926 | Arvizu Barragan | Mar 1976 | A |
3943936 | Rasor et al. | Mar 1976 | A |
3946744 | Auerbach | Mar 1976 | A |
3952750 | Mirowski et al. | Apr 1976 | A |
4027663 | Fischler et al. | Jun 1977 | A |
4072154 | Anderson et al. | Feb 1978 | A |
4083366 | Gombrich et al. | Apr 1978 | A |
4087389 | Coppola | May 1978 | A |
4102344 | Conway et al. | Jul 1978 | A |
4146029 | Ellinwood, Jr. | Mar 1979 | A |
4151513 | Barthel et al. | Apr 1979 | A |
4151540 | Sander et al. | Apr 1979 | A |
4152540 | Citron et al. | May 1979 | A |
4173221 | McLaughlin et al. | Nov 1979 | A |
4187854 | Davis et al. | Feb 1980 | A |
4210149 | Heilman et al. | Jul 1980 | A |
RE30366 | Rasor et al. | Aug 1980 | E |
4223678 | Langer et al. | Sep 1980 | A |
4250888 | Grosskopf | Feb 1981 | A |
4256115 | Bilitch | Mar 1981 | A |
4296756 | Dunning et al. | Oct 1981 | A |
4310000 | Lindemans | Jan 1982 | A |
4312354 | Walters | Jan 1982 | A |
4318412 | Stanly et al. | Mar 1982 | A |
4336810 | Anderson et al. | Jun 1982 | A |
4350169 | Dutcher et al. | Sep 1982 | A |
4374382 | Markowitz | Feb 1983 | A |
4406288 | Horwinski et al. | Sep 1983 | A |
4411271 | Markowitz | Oct 1983 | A |
4418695 | Buffet | Dec 1983 | A |
4424551 | Stevenson et al. | Jan 1984 | A |
4428378 | Anderson et al. | Jan 1984 | A |
4440173 | Hudziak et al. | Apr 1984 | A |
4442840 | Wojciechowicz, Jr. | Apr 1984 | A |
4453162 | Money et al. | Jun 1984 | A |
4458692 | Simson | Jul 1984 | A |
4481950 | Duggan | Nov 1984 | A |
4513743 | Van Arragon et al. | Apr 1985 | A |
4516579 | Irnich | May 1985 | A |
4522208 | Buffet | Jun 1985 | A |
4524774 | Hildebrandt | Jun 1985 | A |
4531527 | Reinhold, Jr. et al. | Jul 1985 | A |
4543955 | Schroeppel | Oct 1985 | A |
4550370 | Baker | Oct 1985 | A |
4552127 | Schiff | Nov 1985 | A |
4552154 | Hartlaub | Nov 1985 | A |
4562846 | Cox et al. | Jan 1986 | A |
4586508 | Batina et al. | May 1986 | A |
4606352 | Geddes et al. | Aug 1986 | A |
4607639 | Tanagho et al. | Aug 1986 | A |
4612934 | Borkan | Sep 1986 | A |
4625730 | Fountain et al. | Dec 1986 | A |
4679144 | Cox et al. | Jul 1987 | A |
4681111 | Silvian | Jul 1987 | A |
4681117 | Brodman et al. | Jul 1987 | A |
4702253 | Nappholz et al. | Oct 1987 | A |
4719920 | Alt et al. | Jan 1988 | A |
4722342 | Amundson | Feb 1988 | A |
4750495 | Moore et al. | Jun 1988 | A |
4763340 | Yoneda et al. | Aug 1988 | A |
4763655 | Wirtzfeld et al. | Aug 1988 | A |
4787389 | Tarjan | Nov 1988 | A |
4791931 | Slate | Dec 1988 | A |
4793353 | Borkan | Dec 1988 | A |
4794532 | Leckband et al. | Dec 1988 | A |
4802481 | Schroeppel | Feb 1989 | A |
4809697 | Causey, III et al. | Mar 1989 | A |
4827940 | Mayer et al. | May 1989 | A |
4830006 | Haluska et al. | May 1989 | A |
4844076 | Lesho et al. | Jul 1989 | A |
4846195 | Alt | Jul 1989 | A |
4858610 | Callaghan et al. | Aug 1989 | A |
4860750 | Frey et al. | Aug 1989 | A |
4875483 | Vollmann et al. | Oct 1989 | A |
4880004 | Baker, Jr. et al. | Nov 1989 | A |
4883064 | Olson et al. | Nov 1989 | A |
4886064 | Strandberg | Dec 1989 | A |
4896068 | Nilsson | Jan 1990 | A |
4903701 | Moore et al. | Feb 1990 | A |
4905708 | Davies | Mar 1990 | A |
4926863 | Alt | May 1990 | A |
4974589 | Sholder | Dec 1990 | A |
4987897 | Funke | Jan 1991 | A |
4995390 | Cook et al. | Feb 1991 | A |
5010887 | Thornander | Apr 1991 | A |
5012806 | De Bellis | May 1991 | A |
5014700 | Alt | May 1991 | A |
5014701 | Pless et al. | May 1991 | A |
5031615 | Alt | Jul 1991 | A |
5040533 | Fearnot | Aug 1991 | A |
5040534 | Mann et al. | Aug 1991 | A |
5040536 | Riff | Aug 1991 | A |
5042497 | Shapland | Aug 1991 | A |
5052399 | Olive et al. | Oct 1991 | A |
5058581 | Silvian | Oct 1991 | A |
5065759 | Begemann et al. | Nov 1991 | A |
5076270 | Stutz, Jr. | Dec 1991 | A |
5076272 | Ferek-Petric | Dec 1991 | A |
5085224 | Galen et al. | Feb 1992 | A |
5086772 | Larnard et al. | Feb 1992 | A |
5088488 | Markowitz et al. | Feb 1992 | A |
5095903 | DeBellis | Mar 1992 | A |
5109845 | Yuuchi et al. | May 1992 | A |
5111816 | Pless et al. | May 1992 | A |
5113859 | Funke | May 1992 | A |
5113869 | Nappholz et al. | May 1992 | A |
5133350 | Duffin | Jul 1992 | A |
5135004 | Adams et al. | Aug 1992 | A |
5170784 | Ramon et al. | Dec 1992 | A |
5170802 | Mehra | Dec 1992 | A |
5179947 | Meyerson et al. | Jan 1993 | A |
5184616 | Weiss | Feb 1993 | A |
5193539 | Schulman et al. | Mar 1993 | A |
5193540 | Schulman et al. | Mar 1993 | A |
5193550 | Duffin | Mar 1993 | A |
5217010 | Tsitlik et al. | Jun 1993 | A |
5247945 | Heinze et al. | Sep 1993 | A |
5259394 | Bens | Nov 1993 | A |
5260621 | Little et al. | Nov 1993 | A |
5267150 | Wilkinson | Nov 1993 | A |
5282841 | Szyszkowski | Feb 1994 | A |
5284136 | Hauck et al. | Feb 1994 | A |
5291902 | Carman | Mar 1994 | A |
5300093 | Koestner et al. | Apr 1994 | A |
5304206 | Baker, Jr. et al. | Apr 1994 | A |
5304209 | Adams et al. | Apr 1994 | A |
5313953 | Yomtov et al. | May 1994 | A |
5318596 | Barreras et al. | Jun 1994 | A |
5324316 | Schulman et al. | Jun 1994 | A |
5331966 | Bennett et al. | Jul 1994 | A |
5333095 | Stevenson et al. | Jul 1994 | A |
5336244 | Weijand | Aug 1994 | A |
5342401 | Spano et al. | Aug 1994 | A |
5354317 | Alt | Oct 1994 | A |
5358514 | Schulman et al. | Oct 1994 | A |
5373852 | Harrison et al. | Dec 1994 | A |
5383912 | Cox et al. | Jan 1995 | A |
5383915 | Adams | Jan 1995 | A |
5404877 | Nolan et al. | Apr 1995 | A |
5405367 | Schulman et al. | Apr 1995 | A |
5406444 | Selfried et al. | Apr 1995 | A |
5411532 | Mortazavi | May 1995 | A |
5411535 | Fujii et al. | May 1995 | A |
5411537 | Munshi et al. | May 1995 | A |
5417222 | Dempsey et al. | May 1995 | A |
5419337 | Dempsey et al. | May 1995 | A |
5431171 | Harrison et al. | Jul 1995 | A |
5446447 | Carney et al. | Aug 1995 | A |
5456261 | Luczyk | Oct 1995 | A |
5466246 | Silvian | Nov 1995 | A |
5469857 | Laurent et al. | Nov 1995 | A |
5480415 | Cox et al. | Jan 1996 | A |
5481262 | Urbas et al. | Jan 1996 | A |
5522876 | Rusink | Jun 1996 | A |
5531779 | Dahl et al. | Jul 1996 | A |
5531781 | Alferness et al. | Jul 1996 | A |
5531783 | Giele et al. | Jul 1996 | A |
5539775 | Tuttle et al. | Jul 1996 | A |
5549654 | Powell | Aug 1996 | A |
5549659 | Johansen et al. | Aug 1996 | A |
5551427 | Altman | Sep 1996 | A |
5556421 | Prutchi et al. | Sep 1996 | A |
5562717 | Tippey et al. | Oct 1996 | A |
5571143 | Hoegnelid et al. | Nov 1996 | A |
5571148 | Loeb et al. | Nov 1996 | A |
5579775 | Dempsey et al. | Dec 1996 | A |
5586556 | Spivey et al. | Dec 1996 | A |
5591217 | Barreras | Jan 1997 | A |
5598848 | Swanson et al. | Feb 1997 | A |
5649952 | Lam | Jul 1997 | A |
5650759 | Hittman et al. | Jul 1997 | A |
5654984 | Hershbarger et al. | Aug 1997 | A |
5662689 | Elsberry et al. | Sep 1997 | A |
5669391 | Williams | Sep 1997 | A |
5674259 | Gray | Oct 1997 | A |
5676153 | Smith et al. | Oct 1997 | A |
5693076 | Kaemmerer | Dec 1997 | A |
5694940 | Unger et al. | Dec 1997 | A |
5694952 | Lidman et al. | Dec 1997 | A |
5697958 | Paul et al. | Dec 1997 | A |
5702427 | Ecker et al. | Dec 1997 | A |
5725559 | Alt et al. | Mar 1998 | A |
5728154 | Crossett et al. | Mar 1998 | A |
5730143 | Schwarzberg | Mar 1998 | A |
5735880 | Prutchi et al. | Apr 1998 | A |
5738102 | Lemelson | Apr 1998 | A |
5740811 | Hedberg et al. | Apr 1998 | A |
5741314 | Daly et al. | Apr 1998 | A |
5766231 | Erickson et al. | Jun 1998 | A |
5792202 | Rueter | Aug 1998 | A |
5792205 | Alt et al. | Aug 1998 | A |
5792208 | Gray | Aug 1998 | A |
5810735 | Halperin et al. | Sep 1998 | A |
5814076 | Brownlee | Sep 1998 | A |
5814087 | Renirie | Sep 1998 | A |
5814089 | Stokes et al. | Sep 1998 | A |
5824016 | Ekwall | Oct 1998 | A |
5871451 | Unger et al. | Feb 1999 | A |
5876353 | Riff | Mar 1999 | A |
5876425 | Gord et al. | Mar 1999 | A |
5891178 | Mann et al. | Apr 1999 | A |
5899928 | Sholder et al. | May 1999 | A |
5935079 | Swanson et al. | Aug 1999 | A |
5954761 | Machek et al. | Sep 1999 | A |
5957861 | Combs et al. | Sep 1999 | A |
5984861 | Crowley | Nov 1999 | A |
5987352 | Klein et al. | Nov 1999 | A |
5995876 | Kruse et al. | Nov 1999 | A |
5999857 | Weijand et al. | Dec 1999 | A |
6002969 | Machek et al. | Dec 1999 | A |
6004269 | Crowley et al. | Dec 1999 | A |
6061596 | Richmond et al. | May 2000 | A |
6076016 | Feierbach | Jun 2000 | A |
6080187 | Alt et al. | Jun 2000 | A |
6093146 | Filangeri | Jul 2000 | A |
6096065 | Crowley | Aug 2000 | A |
6102874 | Stone et al. | Aug 2000 | A |
6112116 | Fischell et al. | Aug 2000 | A |
6115628 | Stadler et al. | Sep 2000 | A |
6115630 | Stadler et al. | Sep 2000 | A |
6115636 | Ryan | Sep 2000 | A |
6119031 | Crowley | Sep 2000 | A |
6125290 | Miesel | Sep 2000 | A |
6125291 | Miesel et al. | Sep 2000 | A |
6128526 | Stadler et al. | Oct 2000 | A |
6129751 | Lucchesi et al. | Oct 2000 | A |
6132390 | Cookston et al. | Oct 2000 | A |
6132456 | Sommer et al. | Oct 2000 | A |
6134459 | Roberts et al. | Oct 2000 | A |
6134470 | Hartlaub | Oct 2000 | A |
6139510 | Palermo | Oct 2000 | A |
6141584 | Rockwell et al. | Oct 2000 | A |
6141588 | Cox et al. | Oct 2000 | A |
6141592 | Pauly | Oct 2000 | A |
6144866 | Miesel et al. | Nov 2000 | A |
6148230 | KenKnight | Nov 2000 | A |
6152882 | Prutchi | Nov 2000 | A |
6163723 | Roberts et al. | Dec 2000 | A |
6164284 | Schulman et al. | Dec 2000 | A |
6167310 | Grevious | Dec 2000 | A |
6178349 | Kieval | Jan 2001 | B1 |
6178356 | Chastain et al. | Jan 2001 | B1 |
6185443 | Crowley | Feb 2001 | B1 |
6185452 | Schulman et al. | Feb 2001 | B1 |
6185464 | Bonner et al. | Feb 2001 | B1 |
6188932 | Lindegren | Feb 2001 | B1 |
6190324 | Kieval et al. | Feb 2001 | B1 |
6198952 | Miesel | Mar 2001 | B1 |
6201993 | Kruse et al. | Mar 2001 | B1 |
6208894 | Schulman et al. | Mar 2001 | B1 |
6208900 | Ecker et al. | Mar 2001 | B1 |
6223081 | Kerver | Apr 2001 | B1 |
6230059 | Duffin | May 2001 | B1 |
6236882 | Lee et al. | May 2001 | B1 |
6240321 | Janke et al. | May 2001 | B1 |
6243608 | Pauly et al. | Jun 2001 | B1 |
6248080 | Miesel et al. | Jun 2001 | B1 |
6263245 | Snell | Jul 2001 | B1 |
6265100 | Saaski et al. | Jul 2001 | B1 |
6266554 | Hsu et al. | Jul 2001 | B1 |
6266564 | Hill et al. | Jul 2001 | B1 |
6272379 | Fischell et al. | Aug 2001 | B1 |
6280409 | Stone et al. | Aug 2001 | B1 |
6289229 | Crowley | Sep 2001 | B1 |
6306088 | Krausman et al. | Oct 2001 | B1 |
6310960 | Saaski et al. | Oct 2001 | B1 |
6315721 | Schulman et al. | Nov 2001 | B2 |
6324418 | Crowley et al. | Nov 2001 | B1 |
6324421 | Stadler et al. | Nov 2001 | B1 |
RE37463 | Altman | Dec 2001 | E |
6343227 | Crowley | Jan 2002 | B1 |
6343233 | Werner et al. | Jan 2002 | B1 |
6347245 | Lee et al. | Feb 2002 | B1 |
6358202 | Arent | Mar 2002 | B1 |
6361522 | Scheiner et al. | Mar 2002 | B1 |
6363282 | Nichols et al. | Mar 2002 | B1 |
6364831 | Crowley | Apr 2002 | B1 |
6370434 | Zhang et al. | Apr 2002 | B1 |
6381492 | Rockwell et al. | Apr 2002 | B1 |
6381493 | Stadler et al. | Apr 2002 | B1 |
6381494 | Gilkerson et al. | Apr 2002 | B1 |
6383209 | Crowley | May 2002 | B1 |
6385593 | Linberg | May 2002 | B2 |
6386882 | Linberg | May 2002 | B1 |
6397100 | Stadler et al. | May 2002 | B2 |
6402689 | Scarantino et al. | Jun 2002 | B1 |
6405073 | Crowley et al. | Jun 2002 | B1 |
6405083 | Rockwell et al. | Jun 2002 | B1 |
6409674 | Brockway et al. | Jun 2002 | B1 |
6409675 | Turcott | Jun 2002 | B1 |
6412490 | Lee | Jul 2002 | B1 |
6418346 | Nelson et al. | Jul 2002 | B1 |
6423056 | Ishikawa et al. | Jul 2002 | B1 |
6424866 | Mika et al. | Jul 2002 | B2 |
6428484 | Battmer et al. | Aug 2002 | B1 |
6434429 | Kraus et al. | Aug 2002 | B1 |
6438410 | Hsu et al. | Aug 2002 | B2 |
6438417 | Rockwell et al. | Aug 2002 | B1 |
6442433 | Linberg | Aug 2002 | B1 |
6444970 | Barbato | Sep 2002 | B1 |
6445953 | Bulkes et al. | Sep 2002 | B1 |
6458145 | Ravenscroft et al. | Oct 2002 | B1 |
6459928 | Mika et al. | Oct 2002 | B2 |
6459937 | Morgan et al. | Oct 2002 | B1 |
6466820 | Juran et al. | Oct 2002 | B1 |
6468263 | Fischell et al. | Oct 2002 | B1 |
6470215 | Kraus et al. | Oct 2002 | B1 |
6471645 | Warkentin et al. | Oct 2002 | B1 |
6472991 | Schulman et al. | Oct 2002 | B1 |
6477424 | Thompson et al. | Nov 2002 | B1 |
6480733 | Turcott | Nov 2002 | B1 |
6482154 | Haubrich et al. | Nov 2002 | B1 |
6484055 | Marcovecchio | Nov 2002 | B1 |
6484057 | Ideker et al. | Nov 2002 | B2 |
6490487 | Kraus et al. | Dec 2002 | B1 |
6496715 | Lee et al. | Dec 2002 | B1 |
6498951 | Larson et al. | Dec 2002 | B1 |
6500168 | Jellie | Dec 2002 | B1 |
6501983 | Natarajan et al. | Dec 2002 | B1 |
6512949 | Combs et al. | Jan 2003 | B1 |
6512959 | Gomperz et al. | Jan 2003 | B1 |
6522926 | Kieval et al. | Feb 2003 | B1 |
6522928 | Whitehurst et al. | Feb 2003 | B2 |
6539257 | KenKnight | Mar 2003 | B1 |
6542781 | Koblish et al. | Apr 2003 | B1 |
6556860 | Groenewegen | Apr 2003 | B1 |
6558321 | Burd et al. | May 2003 | B1 |
6564807 | Schulman et al. | May 2003 | B1 |
6567680 | Swetlik et al. | May 2003 | B2 |
6571120 | Hutten | May 2003 | B2 |
6574509 | Kraus et al. | Jun 2003 | B1 |
6574511 | Lee | Jun 2003 | B2 |
6580946 | Struble | Jun 2003 | B2 |
6580948 | Haupert et al. | Jun 2003 | B2 |
6584351 | Ekwall | Jun 2003 | B1 |
6584352 | Combs et al. | Jun 2003 | B2 |
6589187 | Dirnberger et al. | Jul 2003 | B1 |
6592518 | Denker et al. | Jul 2003 | B2 |
6594523 | Levine | Jul 2003 | B1 |
6597948 | Rockwell et al. | Jul 2003 | B1 |
6597952 | Mika et al. | Jul 2003 | B1 |
6609023 | Fischell et al. | Aug 2003 | B1 |
6611710 | Gomperz et al. | Aug 2003 | B2 |
6615075 | Mlynash et al. | Sep 2003 | B2 |
6622043 | Kraus et al. | Sep 2003 | B1 |
6647292 | Bardy et al. | Nov 2003 | B1 |
6648823 | Thompson | Nov 2003 | B2 |
6649078 | Yu | Nov 2003 | B2 |
6654638 | Sweeney | Nov 2003 | B1 |
6658285 | Potse et al. | Dec 2003 | B2 |
6658297 | Loeb | Dec 2003 | B2 |
6658301 | Loeb et al. | Dec 2003 | B2 |
6659959 | Brockway et al. | Dec 2003 | B2 |
6669631 | Norris et al. | Dec 2003 | B2 |
6681135 | Davis et al. | Jan 2004 | B1 |
6684100 | Sweeney et al. | Jan 2004 | B1 |
6687540 | Marcovecchio | Feb 2004 | B2 |
6687546 | Lebel et al. | Feb 2004 | B2 |
6689117 | Sweeney et al. | Feb 2004 | B2 |
6690959 | Thompson | Feb 2004 | B2 |
6694191 | Starkweather et al. | Feb 2004 | B2 |
6695885 | Schulman et al. | Feb 2004 | B2 |
6697672 | Andersson | Feb 2004 | B2 |
6697677 | Dahl et al. | Feb 2004 | B2 |
6699200 | Cao et al. | Mar 2004 | B2 |
6702857 | Brauker et al. | Mar 2004 | B2 |
6704602 | Berg et al. | Mar 2004 | B2 |
6711440 | Deal et al. | Mar 2004 | B2 |
6716238 | Elliott | Apr 2004 | B2 |
6721597 | Bardy et al. | Apr 2004 | B1 |
6728572 | Hsu et al. | Apr 2004 | B2 |
6728574 | Ujhelyi et al. | Apr 2004 | B2 |
6728576 | Thompson et al. | Apr 2004 | B2 |
6731976 | Penn et al. | May 2004 | B2 |
6731979 | MacDonald | May 2004 | B2 |
6733485 | Whitehurst et al. | May 2004 | B1 |
6735474 | Loeb et al. | May 2004 | B1 |
6735475 | Whitehurst et al. | May 2004 | B1 |
6738670 | Almendinger et al. | May 2004 | B1 |
6741877 | Shults et al. | May 2004 | B1 |
6741886 | Yonce | May 2004 | B2 |
6746404 | Schwartz | Jun 2004 | B2 |
6754538 | Linberg | Jun 2004 | B2 |
6760620 | Sippensgroenewegen | Jul 2004 | B2 |
6764446 | Wolinsky et al. | Jul 2004 | B2 |
6768923 | Ding et al. | Jul 2004 | B2 |
6783499 | Schwartz | Aug 2004 | B2 |
6785576 | Verness | Aug 2004 | B2 |
6786860 | Maltan et al. | Sep 2004 | B2 |
6792314 | Byers et al. | Sep 2004 | B2 |
6799069 | Weiner et al. | Sep 2004 | B2 |
6804559 | Kraus et al. | Oct 2004 | B1 |
6804561 | Stover | Oct 2004 | B2 |
6809507 | Morgan et al. | Oct 2004 | B2 |
6811533 | Lebel et al. | Nov 2004 | B2 |
6813519 | Lebel et al. | Nov 2004 | B2 |
6821154 | Canfield et al. | Nov 2004 | B1 |
6823217 | Rutten et al. | Nov 2004 | B2 |
6824512 | Warkentin et al. | Nov 2004 | B2 |
6829508 | Schulman et al. | Dec 2004 | B2 |
6839596 | Nelson et al. | Jan 2005 | B2 |
6848052 | Hamid et al. | Jan 2005 | B2 |
6850801 | Kieval et al. | Feb 2005 | B2 |
6856835 | Bardy et al. | Feb 2005 | B2 |
6862465 | Shults et al. | Mar 2005 | B2 |
6862480 | Cohen et al. | Mar 2005 | B2 |
6865420 | Kroll | Mar 2005 | B1 |
6869404 | Schulhauser et al. | Mar 2005 | B2 |
6871099 | Whitehurst et al. | Mar 2005 | B1 |
6878112 | Linberg et al. | Apr 2005 | B2 |
6879695 | Maltan et al. | Apr 2005 | B2 |
6879855 | Schulman et al. | Apr 2005 | B2 |
6882875 | Crowley | Apr 2005 | B1 |
6889081 | Hsu | May 2005 | B2 |
6893395 | Kraus et al. | May 2005 | B1 |
6895279 | Loeb et al. | May 2005 | B2 |
6895281 | Amundson et al. | May 2005 | B1 |
6896651 | Gross et al. | May 2005 | B2 |
6897788 | Khair et al. | May 2005 | B2 |
6901294 | Whitehurst et al. | May 2005 | B1 |
6901296 | Whitehurst et al. | May 2005 | B1 |
6907285 | Denker et al. | Jun 2005 | B2 |
6907293 | Grill et al. | Jun 2005 | B2 |
6912420 | Scheiner et al. | Jun 2005 | B2 |
6917833 | Denker et al. | Jul 2005 | B2 |
6925328 | Foster et al. | Aug 2005 | B2 |
6931327 | Goode et al. | Aug 2005 | B2 |
6999821 | Jenney et al. | Feb 2006 | B2 |
7001372 | Richter | Feb 2006 | B2 |
7023359 | Goetz et al. | Apr 2006 | B2 |
7027876 | Casavant et al. | Apr 2006 | B2 |
7146222 | Boling | Dec 2006 | B2 |
7146225 | Guenst et al. | Dec 2006 | B2 |
7164950 | Kroll et al. | Jan 2007 | B2 |
7181505 | Haller et al. | Feb 2007 | B2 |
7187971 | Sommer et al. | Mar 2007 | B2 |
7200437 | Nabutovsky et al. | Apr 2007 | B1 |
7212870 | Helland | May 2007 | B1 |
7277754 | McCabe et al. | Oct 2007 | B2 |
7289853 | Campbell et al. | Oct 2007 | B1 |
7307544 | Kim et al. | Dec 2007 | B2 |
7363090 | Halperin et al. | Apr 2008 | B2 |
7532933 | Hastings et al. | May 2009 | B2 |
7558631 | Cowan et al. | Jul 2009 | B2 |
7565195 | Kroll | Jul 2009 | B1 |
7616991 | Mann et al. | Nov 2009 | B2 |
7630767 | Poore et al. | Dec 2009 | B1 |
7634313 | Kroll et al. | Dec 2009 | B1 |
7650186 | Hastings et al. | Jan 2010 | B2 |
7848823 | Drasler et al. | Dec 2010 | B2 |
7937148 | Jacobson | May 2011 | B2 |
7945333 | Jacobson | May 2011 | B2 |
7991467 | Markowitz | Aug 2011 | B2 |
8010209 | Jacobson | Aug 2011 | B2 |
8295939 | Jacobson | Oct 2012 | B2 |
8352025 | Jacobson | Jan 2013 | B2 |
8457742 | Jacobson | Jun 2013 | B2 |
8788053 | Jacobson | Jul 2014 | B2 |
9168383 | Jacobson et al. | Oct 2015 | B2 |
9192774 | Jacobson | Nov 2015 | B2 |
9216298 | Jacobson | Dec 2015 | B2 |
9227077 | Jacobson | Jan 2016 | B2 |
9358400 | Jacobson | Jun 2016 | B2 |
20010031999 | Carter et al. | Oct 2001 | A1 |
20020032467 | Shemer et al. | Mar 2002 | A1 |
20020077686 | Westlund et al. | Jun 2002 | A1 |
20020099423 | Berg et al. | Jul 2002 | A1 |
20020099430 | Verness | Jul 2002 | A1 |
20020111662 | Iaizzo et al. | Aug 2002 | A1 |
20020116028 | Greatbatch et al. | Aug 2002 | A1 |
20020147488 | Doan et al. | Oct 2002 | A1 |
20030040666 | Rutten et al. | Feb 2003 | A1 |
20030141995 | Lin | Jul 2003 | A1 |
20030158584 | Cates et al. | Aug 2003 | A1 |
20030163184 | Scheiner et al. | Aug 2003 | A1 |
20030199941 | Nielsen et al. | Oct 2003 | A1 |
20040011366 | Schulman et al. | Jan 2004 | A1 |
20040059392 | Parramon et al. | Mar 2004 | A1 |
20040116939 | Goode | Jun 2004 | A1 |
20040133242 | Chapman et al. | Jul 2004 | A1 |
20040143262 | Visram et al. | Jul 2004 | A1 |
20040147973 | Hauser | Jul 2004 | A1 |
20040167587 | Thompson et al. | Aug 2004 | A1 |
20040172116 | Seifert et al. | Sep 2004 | A1 |
20040193223 | Kramer et al. | Sep 2004 | A1 |
20040249417 | Ransbury et al. | Dec 2004 | A1 |
20040260349 | Stroebel | Dec 2004 | A1 |
20050038474 | Wool | Feb 2005 | A1 |
20050038491 | Haack | Feb 2005 | A1 |
20050043765 | Williams et al. | Feb 2005 | A1 |
20050075682 | Schulman et al. | Apr 2005 | A1 |
20050096702 | Denker et al. | May 2005 | A1 |
20050131478 | Kim et al. | Jun 2005 | A1 |
20050149138 | Min et al. | Jul 2005 | A1 |
20050165465 | Pianca et al. | Jul 2005 | A1 |
20050267555 | Marnfeldt et al. | Dec 2005 | A1 |
20050288722 | Eigler et al. | Dec 2005 | A1 |
20060064149 | Belacazar et al. | Mar 2006 | A1 |
20060085039 | Hastings et al. | Apr 2006 | A1 |
20060085041 | Hastings et al. | Apr 2006 | A1 |
20060085042 | Hastings et al. | Apr 2006 | A1 |
20060105613 | Carroll et al. | May 2006 | A1 |
20060108335 | Zhao et al. | May 2006 | A1 |
20060121475 | Davids et al. | Jun 2006 | A1 |
20060135999 | Bodner et al. | Jun 2006 | A1 |
20060136004 | Cowan et al. | Jun 2006 | A1 |
20060161222 | Haubrich et al. | Jul 2006 | A1 |
20060241705 | Neumann et al. | Oct 2006 | A1 |
20060247750 | Seifert et al. | Nov 2006 | A1 |
20060282150 | Olson et al. | Dec 2006 | A1 |
20070016263 | Armstrong et al. | Jan 2007 | A1 |
20070043414 | Fifer et al. | Feb 2007 | A1 |
20070055184 | Echt et al. | Mar 2007 | A1 |
20070088394 | Jacobson | Apr 2007 | A1 |
20070088396 | Jacobson | Apr 2007 | A1 |
20070088397 | Jacobson | Apr 2007 | A1 |
20070088398 | Jacobson | Apr 2007 | A1 |
20070088400 | Jacobson | Apr 2007 | A1 |
20070088405 | Jacobson | Apr 2007 | A1 |
20070088418 | Jacobson | Apr 2007 | A1 |
20070123923 | Lindstrom et al. | May 2007 | A1 |
20070142709 | Martone et al. | Jun 2007 | A1 |
20070167994 | Shelton et al. | Jul 2007 | A1 |
20070179552 | Dennis et al. | Aug 2007 | A1 |
20070270675 | Kane et al. | Nov 2007 | A1 |
20070276004 | Hirsch et al. | Nov 2007 | A1 |
20070276444 | Gelbart et al. | Nov 2007 | A1 |
20070293904 | Gelbart et al. | Dec 2007 | A1 |
20080004535 | Smits | Jan 2008 | A1 |
20080021532 | Kveen et al. | Jan 2008 | A1 |
20080039738 | Dinsmoor et al. | Feb 2008 | A1 |
20080086168 | Cahill | Apr 2008 | A1 |
20080091255 | Caparso et al. | Apr 2008 | A1 |
20080119911 | Rosero | May 2008 | A1 |
20080243218 | Bottomley et al. | Oct 2008 | A1 |
20080269591 | Halperin et al. | Oct 2008 | A1 |
20080306359 | Zdeblick et al. | Dec 2008 | A1 |
20090018599 | Hastings et al. | Jan 2009 | A1 |
20090082827 | Kveen et al. | Mar 2009 | A1 |
20090082828 | Ostroff | Mar 2009 | A1 |
20090149902 | Kumar et al. | Jun 2009 | A1 |
20090171408 | Solem | Jul 2009 | A1 |
20100069983 | Peacock, III et al. | Mar 2010 | A1 |
20100198288 | Ostroff | Aug 2010 | A1 |
20100249828 | Mavani et al. | Sep 2010 | A1 |
20100292541 | Hashiba et al. | Nov 2010 | A1 |
20100305653 | Lund et al. | Dec 2010 | A1 |
20100305656 | Imran et al. | Dec 2010 | A1 |
20100312332 | Forster et al. | Dec 2010 | A1 |
20110004117 | Neville et al. | Jan 2011 | A1 |
20110071586 | Jacobson | Mar 2011 | A1 |
20110077708 | Ostroff | Mar 2011 | A1 |
20110184492 | Martens et al. | Jul 2011 | A1 |
20110208260 | Jacobson | Aug 2011 | A1 |
20110218587 | Jacobson | Sep 2011 | A1 |
20110282423 | Jacobson | Nov 2011 | A1 |
20120089198 | Ostroff | Apr 2012 | A1 |
20120095539 | Khairkhahan et al. | Apr 2012 | A1 |
20120109236 | Jacobson et al. | May 2012 | A1 |
20120116489 | Khairkhahan et al. | May 2012 | A1 |
20120158111 | Khairkhahan et al. | Jun 2012 | A1 |
20120165827 | Khairkhahan et al. | Jun 2012 | A1 |
20120197373 | Khairkhahan et al. | Aug 2012 | A1 |
20130041422 | Jacobson | Feb 2013 | A1 |
20130103109 | Jacobson | Apr 2013 | A1 |
20130123875 | Varady et al. | May 2013 | A1 |
20140051965 | Zdeblick et al. | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
0362611 | Apr 1990 | EP |
1115329 | Jul 2001 | EP |
1741465 | Jan 2007 | EP |
H04506167 | Oct 1992 | JP |
H05245215 | Sep 1993 | JP |
2006507096 | Mar 2006 | JP |
2006516449 | Jul 2006 | JP |
2006526483 | Nov 2006 | JP |
WO-9312714 | Jul 1993 | WO |
WO-9837926 | Sep 1998 | WO |
WO-0234333 | May 2002 | WO |
WO-2004012811 | Feb 2004 | WO |
WO-2006065394 | Jun 2006 | WO |
WO-2007047681 | Apr 2007 | WO |
WO-2007059386 | May 2007 | WO |
WO-2008058265 | May 2008 | WO |
Entry |
---|
Advisory Action mailed Aug. 19, 2014 for U.S. Appl. No. 13/277,151, filed Apr. 19, 2013, 5 pages. |
Appeal Brief filed Jul. 13, 2012 for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 17 pages. |
Appeal Brief filed Mar. 7, 2013 for U.S. Appl No. 11/549,581, filed Oct. 13, 2006, 25 pages. |
Appeal Brief filed Oct. 10, 2011 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 20 pages. |
Beeby S.P., et al., “Micomachined Silicon Generator for Harvesting Power from Vibrations,” (Proceedings) PowerMEMS 2004, Nov. 28-30, 2004, Kyoto, Japan, pp. 104-107. |
Bordacher P., et al., “Impact and Prevention of Far-field Sensing in Fallback Mode Switches,” Pacing and Clinical Electrophysiology, 2003, vol. 26 (1 pt. II), pp. 206-209. |
Brandt J., et al., “Far-field QRS Complex Sensing: Prevalence and Timing with Bipolar Atrial Leads,” Pacing and Clinical Electrophysiology, 2000, vol. 23 (3), pp. 315-320. |
Brown E.S., The Atomic Battery, Technology Review, Published by MIT, 4 pages, Jun. 16, 2005. |
Communication of a Notice of Opposition mailed Oct. 24, 2014 for European Application No. 06836350.6, 35 pages. |
Design of Cardiac Pacemakers, edited by J.G. Webster, 1995, Chapter 11. |
Examiner's Answer to Appeal Brief mailed Aug. 30, 2012 for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 6 pages. |
Examiner's Answer to Appeal Brief mailed Mar. 13, 2012 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 12 pages. |
Extended European Search Report for Application No. European Application No. 06836350.6 dated Nov. 20, 2009. |
Extended European Search Report for Application No. European Application No. 12159212.5 dated Jun. 4, 2012. |
Extended European Search Report for Application No. European Application No. 12159213.3 dated Jun. 4, 2012. |
Extended European Search Report for Application No. European Application No. 12159214.1 dated Jun 4, 2012. |
Extended European Search Report for Application No. European Application No. 12159218.2 dated Jun. 4, 2012. |
Extended European Search Report for Application No. European Application No. 12159219.0 dated Jun. 6, 2012. |
Extended European Search Report for Application No. European Application No. 12159220.8 dated Jun. 4, 2012. |
Extended European Search Report for Application No. European Application No. 12159222.4 dated Jun. 4, 2012. |
Extended European Search Report for Application No. European Application No. 12841426.5 dated Jun. 2, 2015. |
Final Office Action mailed Apr. 27, 2011 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 11 pages. |
Final Office Action mailed Aug. 30, 2010 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 10 pages. |
Final Office Action mailed Aug. 31, 2010 for U.S. Appl. No. 11/549,595, filed Oct. 13, 2006, 10 pages. |
Final Office Action mailed Feb. 23, 2012 for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 12 pages. |
Final Office Action mailed Jun. 24, 2014 for U.S. Appl. No. 13/277,151, filed Apr. 19, 2013, 22 pages. |
Final Office Action mailed Nov. 25, 2009 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 14 pages. |
Final Office Action mailed Nov. 27, 2009 for U.S. Appl. No. 11/549,596, filed Oct. 13, 2006, 10 pages. |
Final Office Action mailed Oct. 16, 2012 for U.S. Appl. No. 11/549,581, filed Oct. 13, 2006, 28 pages. |
International Preliminary Report on Patentability for Application No. PCT/US06/40564, dated Sep. 30, 2008, 26 pages. |
International Preliminary Report on Patentability for Application No. PCT/US12/57776, dated Apr. 22, 2014, 8 pages. |
International Search Report for Application No. PCT/US06/40564, mailed Apr. 8, 2008, 4 pages. |
International Search Report for Application No. PCT/US12/57776, mailed Jan. 10, 2013, 2 pages. |
International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” International Application No. PCT/US06/40564, Apr. 8, 2008, 29 pages. |
International Searching Authority, “Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration,” International Application No. PCT/US12/57776, Jan. 10, 2013, 12 pages. |
Irnich W., “Electronic Security Systems and Active Implantable Medical Devices,” Journal of Pacing and Clinical Electrophysiology, 2002, vol. 25 (8), pp. 1235-1258. |
Irnich W., et al., “Do We need Pacemakers Resistant to Magnetic Resonance Imaging?,” Europace, 2005, vol. 7 (4), pp. 353-365. |
Jacobson P.M., et al., U.S. Appl. No. 12/953,282 entitled “Leadless Cardiac Pacemaker Triggered by Conductive Communication,” filed Nov. 23, 2010. |
Jacobson P.M., et al., U.S. Appl. No. 13/109,728 entitled “Programmer for Biostimulator System,” filed May 17, 2011. |
Jacobson P.M., et al., U.S. Appl. No. 13/191,229 entitled “Implantable Biostimulator Delivery System,” filed Jul. 26, 2011. |
Jacobson P.M., et al., U.S. Appl. No. 13/277,151 entitled “Leadless Cardiac Pacemaker with Conducted Communication,” filed Oct. 19, 2011. |
Jacobson P.M., et al., U.S. Appl. No. 13/708,732 entitled “Leadless Cardiac Pacemaker Triggered by Conductive Communication,” filed Dec. 7, 2012. |
Jacobson P.M., et al., U.S. Appl. No. 13/866,803 entitled “Leadless Cardiac Pacemaker System for Usage in Combination with an Implantable Cardioverter-Defribrillator,” filed Apr. 19, 2013. |
Jacobson P.M., U.S. Appl. No. 13/098,266 entitled “Rate Responsive Leadless Cardiac Pacemaker,” filed Apr. 29, 2011. |
Khairkhahan A., et al., U.S. Appl. No. 13/331,922 entitled “Leadless Pacemaker with Radial Fixation Mechanism ,” filed Dec. 20, 2011. |
Khairkhahan A., et al., U.S. Appl. No. 13/272,074 entitled “Delivery Catheter Systems and Methods,” filed Oct. 12, 2011. |
Khairkhahan A., et al., U.S. Appl. No. 13/272,082 entitled “Leadless Cardiac Pacemaker with Anti-Unscrewing Feature,” filed Oct. 12, 2011. |
Khairkhahan A., et al., U.S. Appl. No. 13/324,781 entitled “Delivery Catheter Systems and Methods,” filed Dec. 13, 2011. |
Khairkhahan A., et al., U.S. Appl. No. 13/324,802 entitled “Pacemaker Retrieval Systems and Methods,” filed Dec. 13, 2011. |
Luchinger R. Safety Aspects of Cardiac Pacemakers in Magnetic Resonance Imaging, A Dissertation Submitted to the Swiss Federal Institute of Technology Zurich, 2002, 137 pages. |
Luechinger R., et al., “Force and Torque Effects of a 1.5-Tesla MRI Scanner on Cardiac Pacemakers and ICDs,” Journal of Pacing and Clinical Rlectrophysiology, 2001, vol. 24 (2), pp. 199-205. |
Luechinger R., et al., “In vivo Heating of Pacemaker Leads During Magnetic Resonance Imaging,” European Heart Journal, 2005, vol. 26 (4), pp. 376-383. |
Non-Final Office Action mailed Aug. 28, 2012 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 12 pages. |
Non-Final Office Action mailed Dec. 1, 2011 for U.S. Appl. No. 13/109,728, filed May 17, 2011, 16 pages. |
Non-Final Office Action mailed Dec. 9, 2008 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 35 pages. |
Non-Final Office Action mailed Dec. 9, 2008 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 35 pages. |
Non-Final Office Action mailed Feb. 4, 2009 for U.S. Appl. No. 11/549,605, filed Oct. 13, 2006, 11 pages. |
Non-Final Office Action mailed Jun. 13, 2013 for U.S. Appl. No. 13/866,803, filed Apr. 19, 2013, 11 pages. |
Non-Final Office Action mailed Jun. 22, 2012 for U.S. Appl. No. 11/549,581, filed Oct. 13, 2006, 27 pages. |
Non-Final Office Action mailed Jun. 7, 2011 for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 12 pages. |
Non-Final Office Action mailed Mar. 17, 2010 for U.S. Appl. No. 11/549,596, filed Oct. 13, 2006, 8 pages. |
Non-Final Office Action mailed Mar. 17, 2010 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 9 pages. |
Non-Final Office Action mailed May 11, 2010 for U.S. Appl. No. 11/549,605, filed Oct. 13, 2006, 16 pages. |
Non-Final Office Action mailed May 12, 2010 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 11 pages. |
Non-Final Office Action mailed May 21, 2012 for U.S. Appl. No. 11/549,596, filed Oct. 13, 2006, 8 pages. |
Non-Final Office Action mailed May 4, 2012 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 42 pages. |
Non-Final Office Action mailed Nov. 24, 2010 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 10 pages. |
Non-Final Office Action mailed Nov. 25, 2008 for U.S. Appl. No. 11/549,596, filed Oct. 13, 2006, 29 pages. |
Non-Final Office Action mailed Oct. 1, 2013 for U.S. Appl. No. 13/866,803, filed Apr. 19, 2013, 11 pages. |
Non-Final Office Action mailed Sep. 11, 2013 for U.S. Appl. No. 13/277,151, filed Apr. 19, 2013, 18 pages. |
Notice of Allowance mailed Feb. 22, 2011 for U.S. Appl. No. 11/549,605, filed Oct. 13, 2006, 4 pages. |
Notice of Allowance mailed Jan. 23, 2013 for U.S. Appl. No. 11/549,599, filed Oct. 13, 2006, 7 pages. |
Notice of Allowance mailed Jan. 5, 2011 for U.S. Appl. No. 11/549,605, filed Oct. 13, 2006, 4 pages. |
Notice of Allowance mailed Jun. 25, 2012 for U.S. Appl. No. 13/109,728, filed May 17, 2011, 7 pages. |
Notice of Allowance mailed Mar. 26, 2014 for U.S. Appl. No. 13/866,803, filed Apr. 19, 2013, 11 pages. |
Notice of Allowance mailed Sep. 10, 2012 for U.S. Appl. No. 11/549,596, filed Oct. 13, 2006, 5 pages. |
Notice of Allowance mailed Sep. 25, 2014 for U.S. Appl. No. 13/277,151, filed Apr. 19, 2013, 10 pages. |
Nyenhuis J.A., et al., MRI and Implanted Medical Devices: Basic Interactions with an Emphasis on Heating, IEEE Transactions on Device and Materials Reliability, 2005, vol. 5 (3), pp. 467-480. |
Ostroff A., et al., U.S. Appl. No. 12/568,513 entitled “MRI Compatible Leadless Cardiac Pacemaker,” filed Sep. 28, 2009. |
Ostroff A., et al., U.S. Appl. No. 12/698,969 entitled “Leadless Cardiac Pacemaker with Secondary Fixation Capability,” filed Feb. 2, 2010. |
Ostroff A., et al., U.S. Appl. No. 13/272,092 entitled “Temperature Sensor for a Leadless Cardiac Pacemaker,” filed Oct. 12, 2011. |
Ostroff A., et al., U.S. Appl. No. 13/910,896 entitlted “Leadless Pacemaker with Multiple Electrodes,” filed Jun. 5, 2013. |
Ostroff A., et al., U.S. Appl. No. 13/915,560 entitled “MRI Compatabile Leadless Cardiac Pacemaker,” filed Jun. 11, 2013. |
Patent Board Decision on Appeal mailed Jun. 1, 2015 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 10 pages. |
Pertijs M., et al., U.S. Appl. No. 13/901,414 entitled “Temperature Sensor for a Leadless Cardiac Pacemaker,” filed May 23, 2013. |
Poore J.W., et al., U.S. Appl. No. 10/891,747 entitled “System and Method for Synchronizing Supplemental Pacing Pulses Generated by a Satellite Pacing Device with Primary Pulses Delivered by a Separate Pacing Device,” filed Jul. 14, 2004 (now Abandoned CIP of this application is U.S. Pat. No. 7,630,767). |
Reply Brief filed May 8, 2012 for U.S. Appl. No. 11/549,591, filed Oct. 13, 2006, 4 pages. |
Reply Brief filed Oct. 29, 2012 for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 4 pages. |
Response mailed Dec. 22, 2011 to Non-Final Office Action for U.S. Appl. No. 12/953,282, filed Nov. 23, 2010, 9 pages. |
Shellock F.G., et al., “Cardiac Pacemaker: in vitro Assessment at 1.5 T,” American Heart Journal, 2006, vol. 151 (2), pp. 436-443. |
Terminal Disclaimer filed Sep. 12, 2014 for U.S. Appl. No. 13/277,151, filed Apr. 19, 2013, 2 pages. |
Varady E., et al., U.S. Appl. No. 13/669,242 entitled “Leadless Cardiac Pacemaker with Integral Battery and Redundant Welds,” filed Nov. 5, 2012. |
Written Opinion for Application No. PCT/US06/40564, mailed Apr. 8, 2008, 25 pages. |
Written Opinion for Application No. PCT/US12/57776, mailed Jan. 10, 2013, 7 pages. |
Pacesetter Request for Adverse Judgment filed Sep. 10, 2015, Interference No. 106,031, 3 pages. |
Order—Miscellaneous, Entered Sep. 9, 2015, Interference No. 106,031, 4 pages. |
Judgement, Entered Sep. 15, 2015, Interference No. 106,031, 3 pages. |
Notice of Allowance mailed Apr. 25, 2016; Related U.S. Appl. No. 11/549,581. |
Patent Board Decision mailed Jan. 21, 2016; Related U.S. Appl. No. 11/549,581. |
Notice of Allowance mailed Apr. 15, 2016; Related U.S. Appl. No. 14/885,853. |
Non-Final Office Action mailed Nov. 18, 2015; Related U.S. Appl. No. 14/885,853. |
Notice of Allowance mailed Sep. 23, 2015; Related U.S. Appl. No. 14/318,201. |
Terminal Disclaimer filed Sep. 16, 2015; Related U.S. Appl. No. 14/318,201. |
Non-Final Office Action mailed Apr. 30, 2015; Related U.S. Appl. No. 14/318,201. |
Non-Final Office Action mailed Dec. 2, 2014: Related U.S. Appl. No. 14/318,201. |
Notice of Allowance mailed Nov. 23, 2015; Related U.S. Appl. No. 12/953,282. |
Patent Board Decision mailed May 27, 2015; Related U.S. Appl. No. 12/953,282. |
Non-Final Office Action mailed Sep. 27, 2011; Related U.S. Appl. No. 12/953,282. |
Notice of Allowance mailed May 22, 2015; Related U.S. Appl. No. 13/098,266. |
Final Office Acton mailed Jan. 29, 2015; Related U.S. Appl. No. 13/098,266. |
Non-Final of Action mailed Aug. 22, 2014; Related U.S. Appl. No. 13/098,266. |
Final Office Action mailed Feb. 27, 2014; Related U.S. Appl. No. 13/098,266. |
Non-Final Office Action mailed Oct. 10, 2013; Related U.S. Appl. No. 13/098,266. |
Non-Final Office Action mailed May 31, 2013; Related U.S. Appl. No. 13/098,266. |
Final Office Action mailed Jun. 22, 2012; Related U.S. Appl. No. 13/098,266. |
Non-Final Office Action mailed Nov. 25, 2011; Related U.S. Appl. No. 13/098,266. |
Number | Date | Country | |
---|---|---|---|
20160317825 A1 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
60761740 | Jan 2006 | US | |
60761531 | Jan 2006 | US | |
60749017 | Dec 2005 | US | |
60739901 | Nov 2005 | US | |
60737296 | Nov 2005 | US | |
60729671 | Oct 2005 | US | |
60726706 | Oct 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14318201 | Jun 2014 | US |
Child | 14885853 | US | |
Parent | 13866803 | Apr 2013 | US |
Child | 14318201 | US | |
Parent | 11549599 | Oct 2006 | US |
Child | 13866803 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14885853 | Oct 2015 | US |
Child | 15208194 | US |