An improved, long range, telemetry system for uplink and downlink telemetry transmission between an implantable medical device (IMD) and an external medical device (EMD), e.g. a programmer or monitor, specifically operable in accordance with a method for ensuring that the telemetry link is between an intended, rather than an un-intended, implantable medical device and the external medical device. Verification is effective if the operator of the EMD observes an implant event signal that is transmitted by uplink telemetry to the EMD from the IMD contemporaneously with a response-provoking action performed in the vicinity of the implant site of the intended patient. The operator directly observes the response-provoking event, when the patient is in sight, or assists the patient in timing the response-provoking event when the patient is not in sight but is at least in voice communication.
|
24. A method of verifying that a telemetry session has been initiated by an external medical device with a desired implantable medical device of a plurality of implantable medical devices, comprising the steps of:
transmitting a first signal from the external medical device; transmitting a second signal from the plurality of implantable medical devices to the external medical device in response to the first signal; selecting an implantable medical device from the plurality of implantable medical devices in response to the second signal; initiating a telemetry session with the selected implantable medical device; and generating a third signal transmitted to the external medical device from the selected implantable device enabling the external medical device to verify that the telemetry session has been initiated with the selected implantable medical device, wherein the third signal is generated in response to a signal generated external to the selected implantable medical device.
1. A medical device system, comprising:
an external medical device generating downlink telemetry transmissions to and receiving uplink telemetry transmissions from a plurality of implantable medical devices, the external medical device simultaneously transmitting a first signal to a plurality of implantable medical devices; and a transceiver, located in the plurality of implantable medical devices, generating uplink telemetry transmissions to and receiving downlink telemetry transmissions from the external medical device, the transceiver transmitting a second signal in response to the first signal, wherein the external medical device selects a desired implantable medical device from the plurality of implantable medical devices based on the second signal, and initiates a telemetry session with the selected implantable medical device subsequent to selecting the desired implantable medical device, and wherein the selected implantable medical device generates a third signal enabling the external medical device to verify that the telemetry session has been initiated by the external medical device with the selected implantable medical device.
10. A medical device system, comprising:
an external medical device generating downlink telemetry transmissions to and receiving uplink telemetry transmissions from a plurality of implantable medical devices, the external medical device simultaneously transmitting a first signal to a plurality of implantable medical devices; and a transceiver, located in the plurality of implantable medical devices, generating uplink telemetry transmissions to and receiving downlink telemetry transmissions from the external medical device, the transceiver transmitting a second signal in response to the first signal, wherein the external medical device selects a desired implantable medical device from the plurality of implantable medical devices based on the second signal, and initiates a telemetry session with the selected implantable medical device subsequent to selecting the desired implantable medical device, and wherein an operator of the external medical device requests generation of a third signal by the selected implantable medical device enabling the external medical device to verify that the telemetry session has been initiated by the external medical device with the selected implantable medical device and the initiated telemetry session is terminated in response to the third signal not being generated within a predetermined time period.
18. A medical device system, comprising:
an external medical device generating downlink telemetry transmissions to and receiving uplink telemetry transmissions from a plurality of implantable medical devices, the external medical device simultaneously transmitting a first signal to a plurality of implantable medical devices; and a transceiver, located in the plurality of implantable medical devices, generating uplink telemetry transmissions to and receiving downlink telemetry transmissions from the external medical device, the transceiver transmitting a second signal in response to the first signal, the external medical device selecting the desired implantable medical device from the plurality of implantable medical devices based on the second signal, and initiating a telemetry session with the selected implantable medical device subsequent to selecting the desired implantable medical device; a display screen located at the external medical device displaying the uplink telemetry transmissions; and an activity circuit generating a third signal transmitted to the external medical device through the transceiver corresponding to the selected implantable medical device in response to a fourth signal generated external to the selected implantable medical device, and wherein an operator of the external medical device observes the generation of the fourth signal and a display of the third signal on the display screen to verify that the telemetry session has been initiated by the external medical device with the selected implantable medical device.
2. The medical device system of
3. The medical device system of
4. The medical device system of
5. The medical device system of
6. The medical device system of
a display screen located at the external medical device displaying the uplink telemetry transmissions; and an activity circuit located within the selected implantable medical device, wherein the third signal is generated by the activity circuit in response to a fourth signal generated external to the selected implantable medical device, and wherein an operator of the external medical device observes the generation of the fourth signal and a display of the third signal on the display screen to verify that the telemetry session has been initiated by the external medical device with the selected implantable medical device.
7. The medical device system of
8. The medical device system of
9. The medical device system of
11. The medical device system of
12. The medical device system of
13. The medical device system of
14. The medical device system of
15. The medical device system of
a display screen located at the external medical device displaying the uplink telemetry transmissions; and an activity circuit located within the selected implantable medical device, wherein the third signal is generated by the activity circuit in response to a fourth signal generated external to the selected implantable medical device, and wherein an operator of the external medical device observes the generation of the fourth signal and a display of the third signal on the display screen to verify that the telemetry session has been initiated by the external medical device with the selected implantable medical device.
16. The medical device system of
17. The medical device system of
19. The medical device system of
20. The medical device system of
21. The medical device system of
22. The medical device system of
23. The medical device system of
25. The method of
26. The method of
27. The method of
28. The method of
29. The medical device system of
|
The present invention relates generally to telemetry systems for uplink and downlink telemetry transmission between an implantable medical device (IMD) and an external medical device (EMD) such as a programmer or monitor and more specifically to a method for ensuring that the telemetry link is between an intended, rather than an unintended, implantable medical device and the external medical device.
In the context of programming the operating modes or parameters of an IMD or in receiving information from an IMD, it is vital to ensure that programming commands not be received by an IMD other than the device intended to be programmed and that the source of any up-linked information from an IMD is properly identified. In most currently available systems, the programmer must be placed in close proximity to the implanted device, typically by means of a programming head in contact with the patient's body. In such cases, there is little likelihood of confusion as to the identity of the implanted device with which the programmer is communicating.
More recently it has been proposed to provide communication systems for implantable devices in which the programming head is done away with, and communication occurs directly between the implanted medical device and a programmer or monitor which, may be located some distance from the patient. Such systems are disclosed in U.S. Pat. No. 5,404,877 issued to Nolan et al, and U.S. Pat. No. 5,113,869 issued to Nappholz. In the Nappholz patent, in particular, broadcasting RF signals from an implanted device to a programmer or monitor that may be located some feet away from the patient is suggested. Such a communication system is also disclosed in U.S. patent application No. 09/303,178 for a "Telemetry System For Implantable Medical Devices", filed Apr. 30, 1999 by Villaseca et al., which application is incorporated herein by reference in its entirety. In use of such systems, it is possible that multiple patients, each with an implanted device, may simultaneously be within communication range of the associated external device. In such cases, even if a telemetry link is established between the external device and an implanted device, there may still be uncertainty as to which patient's device is communicating with the external device.
In the context of a telemetry system for communications between an implanted medical device and an associated external medical device located at a distance from the implanted device, the present invention is intended to assure that there is no ambiguity as to which implanted device is communicating with the external device or as to which patient has the device implanted. The invention accomplishes this result by providing a mechanism for indicating which of a number of devices within the communication range of the external device is implanted in a specific patient.
The external device preferably issues a request for communication, which may be received by any of a population of implantable devices that employ the inventive telemetry system. Those devices within range of the external device may in response send a telemetry transmission indicating that the request for communication has been received. This transmission preferably includes an identifier unique to the implanted device. A separate mechanism is provided for activating only the implantable device within a specific patient to send a telemetry transmission including an event signal indicative that the implanted device has been so activated. For example, per the direction of the physician or other individual operating the external device, a magnet may be placed adjacent the device implanted in a specified patient, triggering the uplink transmission of an event signal responsive to the magnet placement. The event signal may also include an identifier unique to the implanted device. The identifier may be used to subsequently communicate only with the device implanted in the specified patient.
If no event signal is received, the device implanted in the specified patient is understood to be either incompatible with the inventive telemetry system or out of range. If the external device receives an up-linked event signal, it is displayed to the operator or triggers a signal indicating its receipt. The operator may then determine whether the received event signal correlates in time to the response-provoking event. If so, the operator can conclude that the device that transmitted the event signal is the device with which communication is desired, and may initiate a telemetry session with that implanted, device. Alternatively, the external device may initiate a telemetry session with an implanted device prior to receipt of an uplink signal from the device, and may use the later uplinked event signal to confirm that communication is underway with the desired implanted device. In such embodiments, receipt of the uplinked event signal may serve as a prerequisite for continuation of the telemetry session and reprogramming of the implanted device.
Other mechanisms for triggering the transmission of the event signal may include, for example, application of pressure to a patient's body, for example by physical impact such as by tapping adjacent the implanted device; audio activation by means of a tone generator, electrical activation by means of an electrical signal applied to the patient's body or activation using an RF signal applied by means other than the remotely located external device.
The present invention will be appreciated as the same becomes better understood by reference to the following detailed description of the preferred embodiment of the invention when considered in connection with the accompanying drawings, in which like numbered reference numbers designate like parts throughout the figures thereof, and wherein:
The present invention relates to a long-range telemetry system of the general type described in the above-referenced Villaseca et al. application wherein an implanted device may be programmed or monitored at a distance from the patient in whom the device is implanted. In an exemplary embodiment, the system may employ RF transmission in an occupied band of about 402-405 MHz as in the Villaseca et al. application. Within this bandwidth, one or a number of communication channels may be available. Other frequency ranges may be substituted. Each telemetry transmission may be formatted in a frame based format using frequency shift keying or other modulation format. Preferably, the effective operating physical distance between the IMD antenna and the external device antenna is at least 2 meters and may be on the order of at 5-10 meters or more.
The IMD may employ for example, an elongated antenna which projects outward from the housing of the IMD, as described in the cited Villaseca et al. application or may employ a coil antenna located external to the device housing as described in U.S. Pat. No. 6,009,350 issued to Renken, incorporated herein by reference in its entirety. The EMD may be equipped with a compatible antenna or set of antennas that are arranged to avoid nulls or dead spots in reception, for example corresponding generally to that disclosed in the above-cited Villaseca et al. application or in U.S patent application No. 09/302,637 for a "Telemetry System For Implantable Medical Devices", filed Apr. 30, 1999 by Geodeke et al., which application is also incorporated herein by reference in its entirety.
Programming commands or data are transmitted between an IPG RF telemetry antenna 28 and an external RF telemetry antenna 24 associated with the external programmer 20. In this case, it is not necessary that the external RF telemetry antenna 24 be contained in a programmer RF head of the type described above so that it can be located close to the patient's skin overlying the IPG 10. Instead, the external RF telemetry antenna 24 can be located on the case of the external programmer 20, and the programmer 20 can be located some distance away from the patient 12. For example, the external programmer 20 and external RF telemetry antenna 24 may be on a stand a few meters or so away from the patient 12. Moreover, the patient 12 may be active and could be exercising on a treadmill or the like during an uplink telemetry interrogation of real time ECG or physiologic parameters. The programmer 20 may also be designed to universally program existing IPGs that employ conventional ferrite core, wire coil, RF telemetry antennas of the prior art and therefore also have a conventional programmer RF head and associated software for selective use with such IPGs.
In an uplink telemetry transmission 22, the external RF telemetry antenna 24 operates as a telemetry receiver antenna, and the IPG RF telemetry antenna 28 operates as a telemetry transmitter antenna. Conversely, in a downlink telemetry transmission 26, the external RF telemetry antenna 24 operates as a telemetry transmitter antenna, and the IPG RF telemetry antenna 28 operates as a telemetry receiver antenna. Both RF telemetry antennas are coupled to a transceiver comprising a transmitter and a receiver.
As shown in
In order for the physician or other caregiver or operator to communicate with the programmer 20, a keyboard 65 coupled to CPU 50 is optionally provided. However the primary communication mode may be through graphics display screen 55 of the well known "touch sensitive" type controlled by graphics circuit 53. A user of programmer 20 may interact therewith through the use of a stylus 56, also coupled to graphics circuit 53, which is used to point to various locations on screen 55 which display menu choices for selection by the user or an alphanumeric keyboard for entering text or numbers and other symbols as shown in the above-incorporated '362 patent. Various touch-screen assemblies are known and commercially available. The display 55 and or the keyboard 65 comprise means for entering command signals from the operator to initiate transmissions of downlink telemetry and to initiate and control telemetry sessions once a telemetry link with an implanted device has been accomplished. Graphics display screen 55 is also used to display patient related data and menu choices and data entry fields used in entering the data in accordance with the present invention as described below. Graphics display screen 55 also displays a variety of screens of telemetered out data or real time data.
Graphics display screen 55 may also display up-linked event signals as that are received and thereby serve as a means for enabling the operator of the programmer to correlate the receipt of uplink telemetry from an implanted device with the response-provoking event to the patient's body as discussed above. Further handshaking functionality may be provided by a device such as microphone 61, which may be used to automatically detect tones generated by the IMD in a manner to be discussed below. Programmer 20 is also provided with a strip chart printer 63 or the like coupled to interface controller module 54 so that a hard copy of a patient's ECG, EGM, marker channel or of graphics displayed on the display screen 55 can be generated.
As will be appreciated by those of ordinary skill in the art, it is often desirable to provide a means for programmer 20 to adapt its mode of operation depending upon the type or generation of implanted medical device to be programmed. Accordingly, it may be desirable to have an expansion cartridge containing EPROMs or the like for storing software programs to control programmer 20 to operate in a particular manner corresponding to a given type or generation of implantable medical device. In addition, in accordance with the present invention, it is desirable to provide the capability through the expansion cartridge or through the floppy disk drive 66 or the CD ROM drive 68 (shown in
The non-isolated analog circuit 59 and the digital circuitry 58 of interface module 57 is coupled to the transceiver and antenna driver circuit board 30 which is used to establish the uplink and downlink telemetry links between the IPG 10 and programmer 20 as described above. The atrial and ventricular sense amp circuits of IPG 10 may also be provided with (electrogram) EGM amplifiers that produce atrial and ventricular EGM signals. These A EGM and V EGM signals may be digitized and uplink telemetered to programmer 20 on receipt of a suitable interrogation command. The uplink telemetered EGM signals are received in programming head 22 and provided to non-isolated analog circuit 59. Non-isolated analog circuit 59, in turn, converts the digitized EGM signals to analog EGM signals (as with a digital-to-analog converter, for example) and presents these signals on output lines designated in
IPG 10 may also be capable of generating so-called marker codes indicative of different cardiac events that it detects. A pacemaker with markerchannel capability is described, for example, in U.S. Pat. No. 4,374,382 to Markowitz, which patent is hereby incorporated by reference herein in its entirety. The markers provided by IPG 10 may be received by programming head 22 and presented on the MARKER CHANNEL output line from non-isolated analog circuit 59.
Isolated analog circuit 60 in interface module 57 is provided to receive external ECG and electrophysiological (EP) stimulation pulse signals. In particular, analog circuit 60 receives ECG signals from patient skin electrodes and processes these signals before providing them to the remainder of the programmer system in a manner well known in the art. Circuit 60 further operates to receive the EP stimulation pulses from an external EP stimulator for the purposes of non-invasive EP studies, as is also known in the art.
In accordance with the present invention, the programmer 20 is operated following the steps set forth in
The IPG block diagram 300 is divided generally into a microcomputer circuit 302, an input/output circuit 320, and peripheral components including connectors for atrial and ventricular leads 18, the IPG RF telemetry antenna 28, a battery 318, an activity sensor 316 responsive to application of pressure and a magnetic field responsive solid state or reed switch 380. The block diagram 300 is fairly typical of prior art dual chamber pacemaker IPG circuits except for the specific configuration of the RF telemetry antenna, the transceiver 332 and the operating software for practicing the steps of the present invention.
The input/output circuit 320 includes a digital controller/timer circuit 330 coupled with a pulse generator output amplifier circuit 340, sense amplifiers 360, the IPG RF transceiver 332, other circuits and inputs described below and with a data and control bus 306 for communicating with the microcomputer circuit 302. The pulse generator circuit 340 includes a ventricular pulse generator circuit and an atrial pulse generator circuit, and The sense amplifier circuit 360 includes atrial and ventricular sense amplifiers adapted to coupled to the atrium and ventricle of the patient's heart by means of leads 14. The output circuit 340 and sense amplifier circuit 360 may contain pulse generators and sense amplifiers corresponding to any of those presently employed in commercially marketed cardiac pacemakers.
Crystal oscillator circuit 338 provides the basic timing clock for the circuit, while battery 318 provides power. Power on reset circuit 336 responds to initial connection of the circuit to the battery for defining an initial operating condition and similarly, resets the operative state of the device in response to detection of a low battery condition. Reference and bias circuit 326 generates stable voltage reference and currents for the analog circuits within the input/output circuit 320. Analog to digital converter ADC and multiplexor circuit 328 digitizes analog signals and voltage to provide real time telemetry if a cardiac signals from sense amplifiers 360, for uplink transmission via RF transceiver circuit 332. Voltage reference and bias circuit 326, ADC and multiplexor 328, power on reset circuit 336 and crystal oscillator circuit 338 may correspond to any of those presently used in current marketed implantable cardiac pacemakers. Audio Signal Generator 339 may be provided to generate audible tones in response to telemetry downlink sessions initiated by the EMD, as discussed below.
Control of timing and other functions within the pacemaker circuit is provided by digital controller/timer circuit 330, which includes a set of timers and associated logic. Digital controller/timer circuit 330 defines the basic pacing interval of the IPG 10, which may take the form of an A--A escape interval initiated on atrial sensing or pacing and triggering atrial pacing at the expiration thereof or may take the form of a V--V escape interval, initiated on ventricular sensing or pacing and triggering ventricular pulse pacing at the expiration thereof. Digital controller/timer circuit 330 similarly defines the A-V escape intervals SAV and PAV. The microcomputer circuit 302 via data and control bus 306 controls the specific values of the intervals defined. Sensed atrial depolarizations are communicated to the digital controller/timer circuit 330 on A event line 352, with ventricular depolarizations communicated to the digital controller/timer circuit 330 on V event line 354. In order to trigger generation of a ventricular pacing pulse, digital controller/timer circuit 330 generates a trigger signal on V trigger line 342. Similarly, in order to trigger an atrial pacing pulse, digital controller/timer circuit 330 generates a trigger pulse on a trigger line 344.
Digital controller/timer circuit 330 also defines time intervals for controlling operation of the sense amplifiers in sense amplifier circuit 360. Typically, digital controller/timer circuit 330 will define an atrial blanking interval following delivery of an atrial pacing pulse, during which atrial sensing is disabled, as well as ventricular blanking intervals following atrial and ventricular pacing pulse delivery, during which ventricular sensing is disabled. Digital controller/timer circuit 330 will also define an atrial refractory period during which atrial sensing is disabled, this refractory period extending from the beginning of the A-V escape interval following either a sensed or paced atrial depolarization, and extending until a predetermined time following sensing of a ventricular depolarization or delivery of a ventricular pacing pulse. Digital controller/timer circuit 330 similarly defines a ventricular refractory period following ventricular sensing or delivery of a ventricular pacing pulse, which is typically shorter than the portion of the atrial refractory period following ventricular sensing or pacing. Digital controller/timer circuit 330 also controls sensitivity settings of the sense amplifiers 360 by means of sensitivity control 350.
Microcomputer circuit 302 controls the operational functions of digital controller/timer 324, specifying which timing intervals are employed, and controlling the duration of the various timing intervals, via data and control bus 306. Microcomputer circuitry contains a microprocessor 304 and associated system clock 308 and on processor RAM circuits 310 and 312, respectively. In addition, microcomputer circuit 302 includes a separate RAM/ROM chip 314. Microprocessor 304 is interrupt driven, operating in a reduced power consumption mode normally, and awakened in response to defined interrupt events, which may include delivery of atrial and ventricular pacing pulses as well as sensed atrial and ventricular depolarizations. In addition, if the device operates as a rate responsive pacemaker, a timed interrupt, e.g., every two seconds, may be provided in order to allow the microprocessor to analyze the output of the activity circuit 322 and update the basic rate interval (A--A or V--V) of the device. In addition, the microprocessor 304 may also serve to define fixed or variable A-V escape intervals and atrial and ventricular refractory periods which may also decrease in duration along with decreases in duration of the basic rate interval. Similarly microprocessor 304 may define atrial and/or ventricular refractory periods which decrease in duration as a function of sensed or paced heart rate.
In
In one embodiment of the present invention illustrated in
In
In the embodiment of the present invention illustrated in
The illustrated circuitry of
In a still further embodiment of the present invention, the patient 130 in the illustration of
The steps of
When the selection is completed to the extent possible, the EMD 20 may, if so configured, enter a channel scan mode at S101 wherein an available, un-occupied, communication channel in the operating frequency range is selected, in a fashion analogous to the operation of multi-channel cordless phones. Alternatively, the operator may select a communication channel or the EMD may be hardware-limited to a single communication channel.
If the IMD has a telemetry system that is not continuously activated, the telemetry system of the IMD with which communication is desired may be activated at S116, for example by application of a magnet to the device. Alternatively, the IMD may be configured to automatically activate its receiver intermittently. Once activated, the IMD may then sequentially scan available communication channels at S117 until expiration of a defined time period at S119 or receipt of a beacon or EMD discovery downlink signal at S118. In single channel embodiments the IMD may simply await receipt of a beacon signal without scanning.
In step S102, the operator 102 enters a command on the EMD display or keyboard, and the EMD (programmer 20) transmits a beacon or EMD discovery signal via downlink telemetry and waits for a predetermined time for receipt of an uplinked IMD discovery or ID signal at S103. If no uplinked signal is received, multiple re-transmissions of the EMD discovery signal may optionally be triggered, continuing until terminated by the operator or until expiration of a defined time period at S104.
If the EMD discovery or beacon signal is received by an IMD or IMDs within communication range of the EMD in step S118, the IMDs transmit their ID codes or other IMD discovery signals via uplink telemetry at S120 using the same channel as employed by the EMD for downlink telemetry. In order that IMD discovery signals from more than one IMD can be accurately detected, it is preferable that the IMD discovery signals from the IMDs are generated by their transceiver circuitry (e.g. transmitter/receiver 332,
If no IMD discovery signals are received by the EMD at S103 within a defined time period following transmission of the EMD discovery signal at S102, the operator of the EMD may terminate the attempt to establish a telemetry link at S104. Alternatively, the EMD may repeat the transmission of the beacon or EMD discovery signals at S102 until expiration of a longer time-out period at S104. The EMD displays at S105 all IMD discovery signals that may be elicited by the EMD discovery signal, including any. identifying data relative to the IMDs which transmitted the IMD discovery signals. The operator may then select a desired one of the IMDs having signals displayed at S106. If none of the IMDs having displayed signals are the IMD of interest to the operator, the operator may terminate the attempt to establish communication at S107 or trigger a repeat of the beacon or EMD discovery signal at S102.
Following selection of an IMD at S106, the EMD initiates a telemetry session with the selected IMD at S108, by means of a downlink telemetry transmission to the selected IMD at S122. In one embodiment, the initiation of a telemetry session could include the generation by the IMD of some type of patient stimuli to provide notification of the initiated session. This could include an audible signal, a vibration, a pacing rate shift, a pacing burst, or any other type of stimuli that is detectible by the patient so that the patient and/or an assisting operator is notified of the session.
In some embodiments of the invention, bi-directional communication between the IMD and EMD may now begin, including transmissions, for example, of preliminary information regarding device status from the IMD to the EMD. At S109, the operator of the EMD requests that an assistant or the patient perform a response-provoking event in the region of the implant site that is detectable by the IMD. For example a magnet may be applied to the patient's skin over the IMD that closes a reed switch. Alternatively, the patient's skin over the IMD may be tapped to create a signal detectable by a pressure or activity sensor as described above. Normally, such an event would not trigger an uplink telemetry transmission, but the ready state enables the IMD to respond by transmitting an event signal to the EMD at S124, as discussed above. If an event signal is generated at S110, the event signal may be displayed and stored by the EMD. For example, this event signal could cause the EMD to highlight the identification signals of the device providing the event signal on an EMD screen. This allows the operator to verify that the telemetry session has been initiated with the correct device. The event signal may also include identifying information that may be used by the EMD in subsequent telemetry transmissions to the IMD to assure that only the desired IMD receives and responds to transmissions from the EMD.
If the IMD does not detect a response-provoking event at S123, it continues the telemetry session until terminated by the EMD at S125.
In one embodiment, the operator may have the option to initiate a verification transmission to the selected device. Alternatively, this initiation of a verification transmission could be performed automatically by the EMD. This could be done after generation of the response-provoking event discussed above, or instead of using the response-provoking event. According to this option, a device is selected to be the target of a telemetry transmission. When the IMD receives this transmission, the IMD responds by generating some type of patient stimulus. This stimulus could include an audible signal, a vibration, a pacing rate shift or a pacing burst that is detectable by EKG electrodes, or any other type of stimulus that is detectible by the patient and/or the assisting operator so that the assisting operator is further able to verify that the telemetry session has been initiated with the correct device.
In one embodiment wherein patient stimulus is generated in response to the response-provoking event, the EMD could automatically detect this response-provoking event. This detection could be used by the EMD as a prerequisite for continuing the telemetry session. For example, an audible tone generated by the IMD could be detected by microphone 61 within EMD, and used to verify that the telemetry session has been initiated with the correct device. In another embodiment, a unique waveform pulse could be generated by the IMD that is detectable by an EKG electrode coupled to EMD.
Following transmission of the event signal and/or generation of the patient stimulus at S124, the IMD awaits further communications as part of the ongoing telemetry session or a communication terminating the telemetry session at S125.
If no up-linked event signal and/or patient stimulus is generated at S110, the operator may elect at S114 to terminate the telemetry session at S114 resulting in a downlink transmission to the IMD ending the telemetry session. If the operator does not wish to terminate the session at S114, the request for and performance of the response-provoking event at S109 may be repeated.
If an up-linked event signal and/or patient stimulus is generated by the IMD and detected by the EMD, the signals received by the EMD are decoded and displayed and/or signaled by the EMD at S110. The operator 102 of the EMD observes at S112 the correlation or lack of correlation between the response-provoking event, any patient stimulus, and the display of the corresponding received event signal. Preferably, the operator enters a confirmation of the observed correlation if an event signal is displayed contemporaneously with or immediately following the observed response-provoking event at S112, enabling continuation of the telemetry session at S113. S113. As discussed above, the operator may further confirm this correlation by noting any patient stimuli generated by the IMD following a specific telemetry transmission by the EMD. Reprogramming of the IMD parameters may then be accomplished with certainty that the IMD of interest is the IMD in communication with the EMD. The telemetry session is continued at S13 until terminated by the operator.
If no correlation is observed, the operator may terminate the telemetry session at S111 or alternatively the EMD may automatically do so, resulting in a downlink transmission to the IMD ending the telemetry session. The EMD may then send new beacon signals at S102 as illustrated, to again attempt to contact the IMD of interest. If the operator or the EMD does not terminate the session at S111, the request for and performance of the response-provoking event at S109 may optionally be repeated. In alternative embodiments, the operator or the EMD may instead select a different IMD at S106 or terminate the attempt to establish communication at S107.
By means of a received up-linked event signal correlated to the response-provoking event, the operator 102 is assured that communication is occurring with the IMD in the desired patient 100 and not with some other IMD in another patient within the telemetry range. In the event of a failure to establish a telemetry link with the IMD of interest, the process illustrated in
In the course of a telemetry session, the EMD transmits interrogation or programming commands by downlink telemetry that are received and acted upon by the IMD in real time. Typically, the IMD then transmits requested data and/or confirmation of programming after a prescribed delay by uplink telemetry to the external device. The human operator, of the external programmer or monitor can then decide to transmit further commands via downlink telemetry as desired.
The method illustrated in
As discussed above, the embodiment of
The EMD is initialized, selects a frequency if necessary and sends beacon signals until receipt of an uplinked IMD discovery or ID signal or termination at steps S101-S104, precisely as in FIG. 6. Similarly, the IMD is awakened, if necessary scans for a beacon signal at steps S116-S119 and enters a ready state during which it awaits the occurrence of a response-provoking event at S123A. The IMD transmits an IMD discovery signal at S120, which is received and displayed at S105 also as described above in conjunction with FIG. 6. Unlike the embodiment of
After receipt of the IMD discovery or ID signals at S105, the EMD does not allow for selection of an IMD and immediate initiation of a telemetry session as in FIG. 6. Instead, the EMD operator proceeds directly to request or perform the response provoking event at S109, as discussed above in conjunction with FIG. 6. In response to detection of the response-provoking event within the ready period at S123A, the IMD uplinks an event signal at S124, also as described in conjunction with FIG. 6. Rather than awaiting initiation of a telemetry session following the received beacon signal as in
Following response provoking event at S109, the EMD waits for a defined time period for receipt of an uplinked event signal at S110, as in FIG. 6. Following failure to receive the event signal, during this time period at S100, the EMD operator may elect at S114 to terminate the attempt to establish communication with the IMD or may repeat the response-provoking event at S109, also as described in FIG. 6.
If an event signal is received at S110, the EMD operator observes whether the event signal correlates with the response-provoking event at S112, as in FIG. 6. If the event signal correlates with the response-provoking event, the EMD operator may initiate or the EMD may automatically initiate a telemetry session at S108, as in FIG. 6. In response to receipt of a signal from the EMD at S121A, The IMD enters the telemetry session at S122, where it remains until the session is terminated by the EMD. In the event that correlation is not observed at S112, the operator or the EMD may determine at S150 whether to initiate retransmission of the beacon signals at S102 or to simply terminate the attempt to establish a communications link with the IMD of interest. In alternative embodiments, the EMD operator or the EMD may instead elect to repeat the response-provoking event at S109.
The preceding specific embodiments are illustrative of the practice of the invention. It is to be understood, therefore, that other expedients known to those of skill in the art or disclosed herein may be employed without departing from the invention or the scope of the appended claims. It is therefore to be understood, that within the scope of the appended claims, the invention may be practiced otherwise than as specifically described without actually departing from the spirit and scope of the present invention.
Kuehn, Kevin P., Haubrich, Gregory John
Patent | Priority | Assignee | Title |
10105539, | Dec 17 2014 | Cochlear Limited | Configuring a stimulation unit of a hearing device |
10188425, | Dec 13 2010 | Pacesetter, Inc. | Pacemaker retrieval systems and methods |
10238883, | Oct 14 2005 | Pacesetter Inc. | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
10293168, | Jun 10 2005 | Medtronic Urinary Solutions, Inc. | Systems and methods for clinician control of stimulation systems |
10322287, | Sep 07 2006 | Medtronic Urinary Solutions, Inc. | Systems and methods for patient control of stimulation systems |
10434320, | Jun 10 2005 | Medtronic Urinary Solutions, Inc. | Implantable pulse generator systems and methods for providing functional and/or therapeutic stimulation of muscles and/or nerves and/or central nervous system tissue |
10576275, | Jul 06 2001 | Cochlear Limited | System and method for configuring an external device using operating parameters from an implanted device |
10602284, | Jul 18 2016 | Cochlear Limited | Transducer management |
10744332, | Aug 01 2012 | Pacesetter, Inc. | Biostimulator circuit with flying cell |
10981012, | Jul 06 2001 | Cochlear Limited | Configuration of implanted devices |
11759234, | Dec 13 2010 | Pacesetter, Inc. | Pacemaker retrieval systems and methods |
11786272, | Dec 13 2010 | Pacesetter, Inc. | Pacemaker retrieval systems and methods |
11890032, | Dec 13 2010 | Pacesetter, Inc. | Pacemaker retrieval systems and methods |
6804561, | Oct 11 2000 | Alfred E. Mann Foundation for Scientific Research; ALFRED E MANN FOUNDATION FOR SCIENTIFIC RESEARCH | Antenna for miniature implanted medical device |
6985773, | Feb 07 2002 | Cardiac Pacemakers, Inc | Methods and apparatuses for implantable medical device telemetry power management |
6993393, | Dec 19 2001 | Cardiac Pacemakers, Inc | Telemetry duty cycle management system for an implantable medical device |
7209790, | Sep 30 2002 | Medtronic, Inc | Multi-mode programmer for medical device communication |
7218969, | Jan 19 2005 | Cardiac Pacemakers, Inc. | Dynamic channel selection for RF telemetry with implantable device |
7257447, | Apr 20 2005 | Cardiac Pacemakers, Inc. | Method and apparatus for indication-based programming of cardiac rhythm management devices |
7289855, | Jun 09 2004 | Medtronic, Inc | Implantable medical device package antenna |
7319903, | Apr 07 2004 | Cardiac Pacemakers, Inc | System and method for RF transceiver duty cycling in an implantable medical device |
7406349, | Aug 09 2004 | CARDIAC PACEMAKER, INC | Dynamic telemetry link selection for an implantable device |
7450902, | Nov 16 2005 | MEDOS INTERNATIONAL SARL | Continuous phase frequency shift keying modulation during wireless transmissions in a closed system while minimizing power consumption |
7496409, | Mar 29 2006 | Medtronic, Inc | Implantable medical device system and method with signal quality monitoring and response |
7528094, | Oct 25 2004 | Medtronic, Inc | Method and apparatus for providing safe long-range telemetry with implantable medical devices |
7539541, | Aug 09 2004 | Cardiac Pacemakers, Inc | Automatic power control for a radio frequency transceiver of an implantable device |
7565197, | Jun 18 2004 | Medtronic INC | Conditional requirements for remote medical device programming |
7664553, | Apr 27 2005 | Cardiac Pacemakers, Inc | System and method for enabling communications with implantable medical devices |
7668596, | Feb 07 2002 | Cardiac Pacemakers, Inc. | Methods and apparatuses for implantable medical device telemetry power management |
7697993, | May 13 2004 | Cardiac Pacemakers, Inc | Method and apparatus for question-based programming of cardiac rhythm management devices |
7697994, | Jun 18 2004 | Medtronic, Inc | Remote scheduling for management of an implantable medical device |
7729776, | Dec 19 2001 | 3M Innovative Properties Company | Implantable medical device with two or more telemetry systems |
7738964, | Dec 19 2001 | Cardiac Pacemakers, Inc. | Telemetry duty cycle management system for an implantable medical device |
7761167, | Jun 10 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Systems and methods for clinician control of stimulation systems |
7769451, | Apr 28 2005 | Medtronic, Inc | Method and apparatus for optimizing cardiac resynchronization therapy |
7787953, | Jan 19 2005 | Cardiac Pacemakers, Inc. | Dynamic channel selection for RF telemetry with implantable device |
7813809, | Jun 10 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Implantable pulse generator for providing functional and/or therapeutic stimulation of muscles and/or nerves and/or central nervous system tissue |
7860574, | Dec 19 2001 | Cardiac Pacemakers, Inc. | Implantable medical device with two or more telemetry systems |
7881802, | Aug 09 2004 | Cardiac Pacemakers, Inc | Telemetry switchover state machine with firmware priority control |
7903043, | Dec 22 2003 | Cardiac Pacemakers, Inc | Radio frequency antenna in a header of an implantable medical device |
7937148, | Oct 14 2005 | Pacesetter, Inc | Rate responsive leadless cardiac pacemaker |
7945333, | Oct 14 2005 | Pacesetter, Inc | Programmer for biostimulator system |
7949404, | Jun 26 2006 | Medtronic, Inc. | Communications network for distributed sensing and therapy in biomedical applications |
8000532, | Feb 28 2007 | Medtronic, Inc. | Digital pen to capture data in ambulatory monitored patients |
8010209, | Oct 14 2005 | Pacesetter, Inc | Delivery system for implantable biostimulator |
8019434, | Aug 09 2004 | Cardiac Pacemakers, Inc. | Automatic power control for a radio frequency transceiver of an implantable device |
8024043, | Apr 07 2004 | Cardiac Pacemakers, Inc. | System and method for RF wake-up of implantable medical device |
8033998, | Dec 28 2006 | Medtronic, Inc. | Device and method for automatic threshold setting |
8041432, | Dec 19 2001 | Cardiac Pacemakers, Inc. | Implantable medical device with two or more telemetry systems |
8046080, | Dec 19 2001 | Cardiac Pacemakers, Inc. | Telemetry duty cycle management system for an implantable medical device |
8052610, | Dec 28 2006 | Medtronic, Inc. | Event registration for automatic threshold setting |
8055350, | Apr 27 2005 | Cardiac Pacemakers, Inc. | System and method for enabling communications with implantable medical devices |
8088075, | Nov 30 2006 | ST JUDE MEDICAL AB | Identification of an implantable medical device by correlating cardiac related data |
8126418, | Oct 30 2008 | Medtronic, Inc. | Preselector interference rejection and dynamic range extension |
8126736, | Jan 23 2009 | Warsaw Orthopedic, Inc. | Methods and systems for diagnosing, treating, or tracking spinal disorders |
8145320, | Mar 26 2008 | Medtronic, Inc. | Telemetry control for implantable medical devices |
8160704, | Nov 02 2005 | Cardiac Pacemakers, Inc. | System and method for enabling relayed communications by implantable medical devices |
8160707, | Jan 30 2006 | Medtronic, Inc | Method and apparatus for minimizing EMI coupling in a feedthrough array having at least one unfiltered feedthrough |
8165692, | Jun 10 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Implantable pulse generator power management |
8195304, | Jun 10 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Implantable systems and methods for acquisition and processing of electrical signals |
8219200, | Nov 30 2005 | Medtronic, Inc. | Medical device packaging system |
8224447, | Nov 30 2005 | Medtronic, Inc | Medical device packaging system |
8229568, | Oct 25 2004 | Medtronic, Inc. | Method and apparatus for providing safe long-range telemetry with implantable medical devices |
8238975, | Feb 28 2005 | Cardiac Pacemakers, Inc. | Method and apparatus for antenna selection in a diversity antenna system for communicating with implantable medical device |
8255053, | May 13 2004 | Cardiac Pacemakers, Inc. | Method and apparatus for question-based programming of cardiac rhythm management devices |
8290589, | Apr 07 2004 | Cardiac Pacemakers, Inc. | System and method for RF transceiver duty cycling in an implantable medical device |
8295938, | Dec 06 2006 | Medtronic, Inc | Programming a medical device with a general purpose instrument |
8295939, | Oct 14 2005 | Pacesetter, Inc | Programmer for biostimulator system |
8301110, | Jan 13 2010 | Medtronic, Inc | Proximity based selection of an implantable medical device for far field communication |
8326424, | Apr 07 2004 | Cardiac Pacemakers, Inc. | System and method for RF wake-up of implantable medical device |
8352025, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker triggered by conductive communication |
8352038, | Oct 01 2007 | Medtronic, Inc | Medical device function configuration post-manufacturing |
8386043, | Jul 12 2006 | Cardiac Pacemakers, Inc. | Implantable medical device telemetry with adaptive frequency hopping |
8388553, | Nov 04 2004 | Smith & Nephew, Inc | Cycle and load measurement device |
8391975, | Sep 28 2005 | Medtronic, Inc.; Medtronic, Inc | Telemetry of combined endocavitary atrial and ventricular signals |
8438039, | Apr 27 2005 | Medtronic, Inc.; Medtronic, Inc | User customizable workflow preferences for remote patient management |
8457742, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
8467875, | Feb 12 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Stimulation of dorsal genital nerves to treat urologic dysfunctions |
8478399, | Jan 31 2006 | Medtronic, Inc | Method and apparatus for controlling arrhythmia detection and treatment based on patient posture |
8486070, | Aug 23 2005 | Smith & Nephew, Inc | Telemetric orthopaedic implant |
8525643, | Mar 02 2010 | Medtronic, Inc. | Medical system with identification patch |
8527068, | Feb 02 2009 | Pacesetter, Inc | Leadless cardiac pacemaker with secondary fixation capability |
8538528, | Feb 07 2002 | Cardiac Pacemakers, Inc. | Methods and apparatuses for implantable medical device telemetry power management |
8543205, | Oct 12 2010 | Pacesetter, Inc | Temperature sensor for a leadless cardiac pacemaker |
8570187, | Sep 06 2007 | Smith & Nephew, Inc | System and method for communicating with a telemetric implant |
8615310, | Dec 13 2010 | Pacesetter, Inc | Delivery catheter systems and methods |
8619002, | Dec 22 2003 | Cardiac Pacemakers, Inc. | Radio frequency antenna in a header of an implantable medical device |
8634926, | Sep 08 2004 | Medtronic, Inc | Clinic based instrument system for remote processing and access to implanted systems information |
8639339, | Apr 07 2004 | Cardiac Pacemakers, Inc. | System and method for RF wake-up of implantable medical device |
8682437, | Sep 25 2007 | Medtronic, Inc. | Proximity signature for secure communication with implantable medical device |
8685093, | Jan 23 2009 | Warsaw Orthopedic, Inc. | Methods and systems for diagnosing, treating, or tracking spinal disorders |
8706252, | Jun 10 2004 | Medtronic, Inc. | Systems and methods for clinician control of stimulation system |
8721643, | Aug 23 2005 | Smith & Nephew, Inc. | Telemetric orthopaedic implant |
8725268, | Apr 20 2005 | Cardiac Pacemakers, Inc. | Method and apparatus for indication-based programming of cardiac rhythm management devices |
8788035, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker triggered by conductive communication |
8788053, | Oct 14 2005 | Pacesetter, Inc | Programmer for biostimulator system |
8792983, | Feb 07 2002 | Cardiac Pacemakers, Inc. | Methods and apparatuses for implantable medical device telemetry power management |
8798745, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
8805526, | May 03 2006 | Cardiac Pacemakers, Inc | Configurable medical telemetry radio system |
8855591, | Oct 30 2008 | Medtronic, Inc. | Preselector interference rejection and dynamic range extension |
8855789, | Oct 14 2005 | Pacesetter, Inc | Implantable biostimulator delivery system |
8886318, | Oct 14 2005 | Pacesetter, Inc. | Leadless cardiac pacemaker with conducted communication |
9020611, | Oct 13 2010 | Pacesetter, Inc | Leadless cardiac pacemaker with anti-unscrewing feature |
9060692, | Oct 12 2010 | Pacesetter, Inc | Temperature sensor for a leadless cardiac pacemaker |
9072913, | Oct 14 2005 | Pacesetter, Inc | Rate responsive leadless cardiac pacemaker |
9126032, | Dec 13 2010 | Pacesetter, Inc | Pacemaker retrieval systems and methods |
9168383, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker with conducted communication |
9192774, | Oct 14 2005 | Pacesetter, Inc | Cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
9205255, | Jun 10 2004 | MEDTRONIC URINARY SOLUTIONS, INC | Implantable pulse generator systems and methods for providing functional and/or therapeutic stimulation of muscles and/or nerves and/or central nervous system tissue |
9216294, | Jun 10 2004 | Medtronic Urinary Solutions, Inc. | Systems and methods for clinician control of stimulation systems |
9216298, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker system with conductive communication |
9227077, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker triggered by conductive communication |
9242102, | Dec 20 2010 | Pacesetter, Inc | Leadless pacemaker with radial fixation mechanism |
9272155, | Feb 02 2009 | Pacesetter, Inc | Leadless cardiac pacemaker with secondary fixation capability |
9358400, | Oct 14 2005 | Pacesetter, Inc | Leadless cardiac pacemaker |
9409033, | Oct 14 2005 | Pacesetter, Inc. | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
9445720, | Feb 23 2007 | Smith & Nephew, Inc | Processing sensed accelerometer data for determination of bone healing |
9468769, | Apr 20 2005 | Cardiac Pacemakers, Inc. | Method and apparatus for indication-based programming of cardiac rhythm management devices |
9480846, | May 17 2006 | MEDTRONIC URINARY SOLUTIONS, INC | Systems and methods for patient control of stimulation systems |
9511236, | Nov 04 2011 | Pacesetter, Inc | Leadless cardiac pacemaker with integral battery and redundant welds |
9549688, | Apr 24 2006 | Medtronic, Inc. | Implantable medical device detection |
9649165, | Jul 16 2012 | Board of Regents, The University of Texas System | Medical device identifier |
9687655, | May 23 2012 | Pacesetter, Inc. | Temperature sensor for a leadless cardiac pacemaker |
9687666, | Oct 14 2005 | Pacesetter, Inc. | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
9724526, | Jun 10 2004 | Medtronic Urinary Solutions, Inc. | Implantable pulse generator systems and methods for operating the same |
9802054, | Aug 01 2012 | Pacesetter, Inc | Biostimulator circuit with flying cell |
9872999, | Oct 14 2005 | Pacesetter, Inc. | Leadless cardiac pacemaker system for usage in combination with an implantable cardioverter-defibrillator |
9936878, | Jun 26 2006 | Medtronic, Inc. | Communications network for distributed sensing and therapy in biomedical applications |
9996669, | Dec 06 2006 | Medtronic, Inc | Intelligent discovery of medical devices by a programming system |
Patent | Priority | Assignee | Title |
3945387, | Sep 09 1974 | General Electric Company | Implantable cardiac pacer with characteristic controllable circuit and control device therefor |
4428378, | Nov 19 1981 | Medtronic, Inc. | Rate adaptive pacer |
4987897, | Sep 18 1989 | Medtronic, Inc. | Body bus medical device communication system |
5052388, | Dec 22 1989 | Medtronic, Inc.; Medtronic, Inc | Method and apparatus for implementing activity sensing in a pulse generator |
5113859, | Sep 19 1988 | Medtronic, Inc. | Acoustic body bus medical device communication system |
5113869, | Aug 21 1990 | Pacesetter, Inc | Implantable ambulatory electrocardiogram monitor |
5404877, | Jun 04 1993 | Pacesetter, Inc | Leadless implantable sensor assembly and a cardiac emergency warning alarm |
5499626, | May 01 1992 | TRACHIP, LLC | Individual descriptive record system |
5855609, | Aug 24 1992 | Allergan, Inc | Medical information transponder implant and tracking system |
5891180, | Apr 29 1998 | Medtronic Inc. | Interrogation of an implantable medical device using audible sound communication |
6009350, | Feb 06 1998 | Medtronic, Inc. | Implant device telemetry antenna |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jul 27 2000 | KUEHN, KEVIN P | Medtronic, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 011017 | /0809 | |
Jul 28 2000 | HAUBRICH, GREGORY JOHN | Medtronic, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 011017 | /0809 | |
Aug 02 2000 | Medtronic, Inc | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Apr 26 2006 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Apr 22 2010 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
May 19 2014 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Nov 19 2005 | 4 years fee payment window open |
May 19 2006 | 6 months grace period start (w surcharge) |
Nov 19 2006 | patent expiry (for year 4) |
Nov 19 2008 | 2 years to revive unintentionally abandoned end. (for year 4) |
Nov 19 2009 | 8 years fee payment window open |
May 19 2010 | 6 months grace period start (w surcharge) |
Nov 19 2010 | patent expiry (for year 8) |
Nov 19 2012 | 2 years to revive unintentionally abandoned end. (for year 8) |
Nov 19 2013 | 12 years fee payment window open |
May 19 2014 | 6 months grace period start (w surcharge) |
Nov 19 2014 | patent expiry (for year 12) |
Nov 19 2016 | 2 years to revive unintentionally abandoned end. (for year 12) |