US20130166642A1 - Communication for implantable medical devices - Google Patents
Communication for implantable medical devices Download PDFInfo
- Publication number
- US20130166642A1 US20130166642A1 US13/334,361 US201113334361A US2013166642A1 US 20130166642 A1 US20130166642 A1 US 20130166642A1 US 201113334361 A US201113334361 A US 201113334361A US 2013166642 A1 US2013166642 A1 US 2013166642A1
- Authority
- US
- United States
- Prior art keywords
- data block
- message
- response
- data
- byte
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
- H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61N—ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY
- A61N1/00—Electrotherapy; Circuits therefor
- A61N1/18—Applying electric currents by contact electrodes
- A61N1/32—Applying electric currents by contact electrodes alternating or intermittent currents
- A61N1/36—Applying electric currents by contact electrodes alternating or intermittent currents for stimulation
- A61N1/372—Arrangements in connection with the implantation of stimulators
- A61N1/37211—Means for communicating with stimulators
- A61N1/37252—Details of algorithms or data aspects of communication system, e.g. handshaking, transmitting specific data or segmenting data
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61N—ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY
- A61N1/00—Electrotherapy; Circuits therefor
- A61N1/18—Applying electric currents by contact electrodes
- A61N1/32—Applying electric currents by contact electrodes alternating or intermittent currents
- A61N1/36—Applying electric currents by contact electrodes alternating or intermittent currents for stimulation
- A61N1/372—Arrangements in connection with the implantation of stimulators
- A61N1/37211—Means for communicating with stimulators
- A61N1/37252—Details of algorithms or data aspects of communication system, e.g. handshaking, transmitting specific data or segmenting data
- A61N1/37254—Pacemaker or defibrillator security, e.g. to prevent or inhibit programming alterations by hackers or unauthorised individuals
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
- G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- the invention relates to communication with implantable medical devices.
- Medical devices such as cardiac pacemakers and implantable pulse generators of spinal cord stimulation systems are implanted beneath the skin of a human body. Occasionally, these implanted devices receive messages from or send data to an external system. Such messages can include, for example, receiving updated control parameters or sending operational history data that can then be analyzed by the external system.
- Data messages and commands are sent from an external system to a specific implanted medical device in order to properly monitor or implement a treatment protocol. It is important that these data messages and commands are received and processed properly by the correct implanted medical device.
- an implanted medical device may receive data messages and commands from multiple external devices when the messages were intended to be received by another patient's implanted medical device. If an implanted medical device responds to a message intended for a different patient's device, the results could be inconsistent with the intended treatment protocol for that patient and may be potentially dangerous to the patient.
- Various embodiments of the invention provide methods and systems for two-way communication between an implanted medical device and an external system. Messages are generated by the external system and responses are generated by the implanted device in a data block format. The data blocks are generated according to a defined size and structure. Data blocks generated by the external system and received by the implanted device include device identification information indicating when the received message is to be processed or disregarded by the implanted device. The data block blocks also include mechanisms for communicating larger data messages through multiple data blocks and ensuring that the data block messages were received completely and properly.
- the invention provides a method of communicating between an implanted device implanted in a patient and an external device external to the patient.
- the implanted device receives a data block of a defined size and monitors the data block for a first flag.
- the first flag indicates when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message.
- the implanted device monitors the data block for a device ID and a command token indicating the type of message that is being received, and stores message content from the data block to a memory of the implanted device.
- the implanted device appends message content from the data block to message content stored in the memory for a previously received data block.
- the method further includes monitoring the data block for a checksum value.
- the implanted device compares the checksum value from the data block to a checksum value calculated by the implanted device indicative of the data in the data block.
- a message error is transmitted by the implanted device when the checksum value from the data block is not consistent with the calculated checksum value.
- the implanted device compares the checksum value from the data block to a checksum value calculated by the implanted device indicative of the data in the data block and the data in all of the previously received data blocks of the message.
- the method further includes comparing the device ID from the data block to one or more stored device IDs indicating external devices which are authorized to communicate with the implanted device. If the device ID from the data block does not correspond to one of the stored device IDs, then the implanted device disregards the data block.
- the method further includes the implanted device generating a response data block of the defined size in response to receiving the message from the external device.
- Generating the response data block includes setting a first flag of the response data block indicating when the response data block is a first data block in a response message and when the response data block is a subsequent data block in a multiple data block response message.
- the implanted device includes a response code, the command token, and message data in the response date block.
- the response code indicates when a command in the received message has been accepted by the implanted device or rejected.
- the command token in the response data block is the same as the command token in the received message from the external device.
- the data block is a subsequent data block in a multiple data block response message, additional response message content is included in the response data block.
- the invention provides a method of communicating between an implanted device implanted in a patient and an external device external to the patient.
- the method includes generating, by the external device, a data block of a defined size and transmitting the data block to the implanted device.
- Generating the data block includes setting a first flag in the data block indicating when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message.
- the data block includes a device ID, a command token indicating the type of message, and message content.
- the data block includes additional message content.
- the invention provides an implantable medical device including a housing, a wireless communication module, a processor, and a memory.
- the memory includes instructions that, when executed by the processor, cause the implantable device to receive a data block of a defined size and monitor the data bock of a first flag.
- the first flag indicates when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message.
- the instructions cause the implantable device to monitor the data block for a device ID and a command token and to store message content from the data block to the memory.
- the instructions cause the implantable device to append message content from the data block to message content stored in the memory from a previously received data block.
- FIG. 1A is a block diagram of a system for communication between an implantable medical device and an external system.
- FIG. 1B is a partial perspective view of a patient using a spinal cord stimulation system including the system for communication of FIG. 1A .
- FIG. 2A is a diagram of the content of a first data block in a message received by the implantable medical device of FIG. 1 from the external system.
- FIG. 2B is a diagram of the content of a final data block in a multiple data block message received by the implantable medical device of FIG. 1 from the external system.
- FIG. 2C is a diagram of the content of an intermediate data block in a multiple data block message received by the implantable medical device of FIG. 1 from the external system.
- FIG. 3A is a diagram of the content of a first data block in a response message sent by the implantable medical device of FIG. 1 to the external system.
- FIG. 3B is a diagram of the content of an intermediate data block in a multiple data block response message sent by the implantable medical device of FIG. 1 to the external system.
- FIG. 3C is a diagram of the content of a final data block in a multiple data block response message sent by the implantable medical device of FIG. 1 to the external system.
- FIG. 4 is a flowchart of a method of analyzing a data block received by the implantable device of FIG. 1 from the external system.
- FIG. 1A illustrates a system for communication between an implanted medical device and an external system, which may include an external device.
- the implanted device 101 is designed to be implanted beneath the skin of a patient.
- the implanted device 101 can include, for example, a cardiac pacemaker system or an implantable pulse generator for a spinal cord stimulator system.
- the implanted device 101 includes a processor 103 and a memory 105 positioned within a housing of the device 101 .
- the processor 103 controls the operation of the implanted device 101 by executing instructions stored on the memory 105 .
- the memory 105 can also store control parameters that govern the operation of the implanted device 101 and historical operation data indicative of past operation of the implanted device 101 .
- an external device 107 is used to communicate with the implanted device 101 .
- Such communication may be used, for example, to send operational commands to the implanted device 101 , to update control parameters for the implanted device 101 , or to request performance and operational data from the implanted device 101 .
- the implanted device 101 is designed to be implanted beneath the skin of a patient, wired communication is not feasible. Therefore, both the implanted device 101 and the external device 107 include wireless communication modules ( 109 and 111 , respectively) to facilitate communication between the two devices.
- the wireless communication modules 109 , 111 in the construction illustrated in FIG. 1 include radio frequency (RF) transmitters and receivers using the Medical Implant Communication Service (MICS) band. However, in other constructions, the wireless communication can be accomplished using other communication technologies such as Bluetooth.
- the external device 107 also includes a processor 113 that controls the operation of the external device by executing instructions stored on a memory 115 .
- FIG. 1B further illustrates one example of a spinal cord stimulation system 120 .
- the implanted device 101 includes several implanted medical electric leads 125 connected to an implantable pulse generator (IPG) 130 .
- the leads 125 each include electrode arrays 135 at the distal end of the base lead cable.
- the electrode arrays 135 include multiple electrical stimulation electrodes placed adjacent to the dura of the spine 140 of a patient 145 using an anchor.
- the spinal column includes the C1-C7 (cervical), T1-T12 (thoracic), L1-L5 (lumbar), and S1-S6 (sacral) vertebrae and the electrode arrays 135 may be positioned anywhere along the spine 140 to deliver the intended therapeutic effects of spinal cord electrical stimulation in a desired region of the spine 140 .
- the electrodes of the electrode arrays 135 promote electrical stimulation to the neurons of the spine based on electrical signals generated by the IPG 130 .
- the stimulation is provided from the IPG 130 to the electrodes via the base lead, which is connected to the IPG 130 with the proximal end of the base lead.
- the body of the lead can traverse through the body of the patient via the spinal column and from the spinal column through the body of the patient to the implant site of the IPG 130 .
- the IPG 130 communicates with an external device 107 .
- the external device 107 can include, for example, any one of a clinical programmer (CP) 150 , a patient programmer and charger (PPC) 155 , and a pocket (or fob) programmer (PP) 160 .
- the implanted medical device 101 and the external device 107 communicate according to a data block-based format. All data blocks used in the communication are of the same, defined size.
- the data block format used provides for communication of larger volume data message content by allowing messages to be spread across multiple data blocks. Furthermore, the data block format provides mechanisms to ensure that only complete and properly formatted messages received from approved external devices are processed by the implanted device 101 .
- FIGS. 2A-2C illustrate the format of data blocks generated by the external device 107 and transmitted to the implanted device 101 .
- Each data block in a message sent according to this example is fifteen bytes in size. However, the data blocks can be larger or smaller in other constructions.
- the first byte of every data block includes a flag that indicates whether the data block is the first data block in a message. A value of “1” in the first byte indicates that the data block either contains a single data block message or is the first data block of a multiple data block message. A value of “0” indicates that the data block is either a subsequent data block in a multiple data block message or was sent and received in error.
- the data block of FIG. 2A is the data block format used for a single data block message or for the first data block of a multiple data block message.
- the flag in Byte 1 contains a value of “1” to indicate such.
- the next three bytes in the data block (bytes 2 - 4 ) contain a device identifier (“device ID”).
- the device ID in this example identifies the external device 107 sending the message.
- the implanted device 101 Upon receiving the message and verifying the correctness of the bytes received, the implanted device 101 checks the device ID against a stored list of one or more external devices that are approved to communicate with the implanted device. This mechanism ensures that the implanted device 101 responds only to commands that were intended for the implanted device 101 .
- the device ID defined in bytes 2 - 4 of the data block of FIG. 2A identify the implanted device 101 for which the message is intended.
- the implanted device 101 will only process messages that identify the specific implanted device 101 in the device ID bytes.
- Bytes 5 and 6 in the data block of FIG. 2A define a command token.
- the command token identifies the command being sent.
- Bytes 7 - 14 include message data content.
- the command token instructs the implanted device 101 how to process the message data content.
- the implanted device 101 is also able to determine how many data blocks will be included in the message based on the command token.
- the last byte in the data block of FIG. 2A contains a checksum value.
- the implanted device 101 calculates a checksum value based on the previous fourteen bytes in the data block of FIG. 2A (including the flag byte, the device ID, and the command token) and compares the calculated checksum value to the checksum value in byte 15 of the data block.
- the checksum value is calculated by adding all bytes of the data block together and ignoring any overflow. In other constructions, other checksum calculation techniques may be implemented.
- FIG. 2B illustrates a final data block in a multiple data block message.
- the first byte in the data block of FIG. 2B is a flag byte.
- the value of the flag byte in the data block of FIG. 2B is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message.
- Additional message content is stored in bytes 2 - 14 of the data block. This additional message content is combined with message content from the first data block ( FIG. 2A ).
- the last byte in the data block of FIG. 2B (byte 15 ) is a final checksum value.
- the implanted device 101 When the implanted device 101 receives the final data block, it calculates a final checksum value indicative of all of the previous bytes in all of the data blocks in the multiple data block message—including the first data block and the checksum value in byte 15 of the first data block ( FIG. 2A ). The implanted device 101 verifies the accuracy of the entire message by comparing this calculated checksum value to the final checksum value in byte 15 of the final data block.
- FIG. 2C illustrates an intermediate data block in a message sent through three or more data blocks.
- the first byte in the intermediate data block is a flag byte, the value of which is set to “0” to indicate that the data block is not the first data block in a multiple data block message.
- the remaining bytes in the data block (bytes 2 - 15 ) all contain additional message data content that, when received by the implanted device 101 , is combined with message content from previously received data blocks.
- the first data block would be of the format illustrated in FIG. 2A .
- the value of the flag byte would be set to “1” to indicate that it is the first data block in a message.
- the first data block would also include the device ID of the external device 107 that generated and sent the message. It would also include a command token, the first eight bytes of message data content, and a checksum value indicative of the data in the previous fourteen bytes of the first data block.
- the second data block would be an intermediate data block of the format illustrated in FIG. 2C .
- the value of the flag byte of the second data block would be set to “0” to indicate that the second data block is a subsequent data block of a multiple data block message.
- the second data block would also include the next fourteen bytes of message data content.
- the third and final data block in the three data block message would be of the format illustrated in FIG. 2B .
- the flag byte again would be set to “0” to indicate that the third data block is a subsequent data block of a multiple data block message.
- the third data block would also include the next thirteen bytes of message data content.
- the last byte (byte 15 ) of the third data block would include a checksum value indicative of the data in the previous fourteen bytes of the third data block and all of the bytes of the first and second data blocks.
- the data block message format is used to implement a command-response form of communication between the external device 107 and the implanted device 101 .
- the implanted device 101 After receiving a complete message from the external device 107 , the implanted device 101 generates and transmits a response message.
- the format of the response message is slightly different from the format of the initial command message.
- the response message is also transmitted through a data block of the same size as the command message—in this case fifteen bytes.
- FIGS. 3A-3C illustrate the format of the response message.
- the first byte of each data block of the response message is a flag byte.
- the value of the flag byte is set to “1” to indicate when the data block includes a single data block response message or a first data block in a multiple data block response message.
- the value of the flag byte is set to “0” to indicate when the data block is a subsequent data block in a multiple data block response message.
- the data block of FIG. 3A illustrates the format of a single data block response message and a first data block of a multiple data block response message.
- the first byte is a flag byte, the value of which is set to “1.”
- the second byte is a response code.
- the response code indicates whether the command from the command message received by the implanted device 101 was processed by the implanted device 101 .
- the next two bytes include the same command token that was included in bytes 2 and 3 of the first data block of the command message ( FIG. 2A ).
- Bytes 5 - 14 include response parameter data.
- the response code and the command token are used by the external device 107 to determine which bytes of the data block include response parameter data and how many data blocks will be included in the response message.
- the final byte (byte 15 ) of the first data block of the response message includes a checksum value.
- the checksum value of the first data block of the response message is also indicative of the content in the previous bytes (bytes 1 - 14 ) of the first data block of the response message.
- the external device 107 calculates a checksum value based on the data in bytes 1 - 14 and compares the calculates checksum value to the checksum value in byte 15 to verify the accuracy of the message content.
- FIG. 3B illustrates an intermediate data block of a response message that includes at least three data blocks.
- the first byte in the intermediate data block includes a flag, the value of which is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message.
- the remaining bytes of the intermediate data block include the next fourteen bytes of response parameter data for the response message.
- FIG. 3C illustrates a final data block of a response message that includes at least two data blocks.
- the first byte in the final data block includes a flag, the value of which is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message.
- Bytes 2 - 14 include the last fourteen bytes of response parameter data for the response message.
- the last byte of the final data block (byte 15 ) includes a final checksum value.
- the final checksum value is indicative of the content in the previous bytes (bytes 1 - 14 ) of the final data block and all of the bytes in the previous data blocks of the multiple data block response message.
- the external device 107 calculates a final checksum value based on the data in bytes 1 - 14 of the final data block and all of the bytes of the previous data blocks in the response message. The external device 107 then compares the calculated final checksum value to the checksum value in byte 15 of the final data block to verify the accuracy of the response message content.
- the implanted device 101 can detect an error in the format of a message received from an external device based on the checksum value. Furthermore, the implanted device 101 can determine when the device ID of the external device sending the message is not recognized. In either case, the implanted device 101 can either ignore the defective message or can send a response message indicating that the message was defective and was not processed by the implanted device 101 . When the external device 107 receives such an “error” message from the implanted device 101 , the external device will correct the message and resend. Alternatively, the external device 107 monitors for a response message and resends the command message if a response is not received within a defined period of time.
- FIG. 4 illustrates how the implanted device 101 receives and processes data blocks received from the external device 107 according to the format described above in reference to FIGS. 2A-2C .
- the implanted device 101 begins by receiving a data block through the wireless communication module 109 (step 401 ).
- the implanted device 101 monitors the first byte (i.e., the flag byte) of the received data block to determine whether the data block is a first data block of a message (step 403 ). If the flag byte indicates that the data block is a first data block of a message, the implanted device verifies the accuracy of the received message by comparing the checksum value in byte 15 of the data block to a calculated checksum value (step 405 ). If the calculated checksum value is not consistent with the checksum value in byte 15 , the implanted device 101 either sends a response message indicating the error condition or disregards the data block (step 407 ).
- the first byte i.e., the flag byte
- the implanted device 101 checks the device ID in bytes 2 - 4 to determine whether the external device sending the message is authorized to send commands to the implanted device 101 (step 409 ). If the device ID is not recognized by the implanted device 101 , the command message is not processed. The implanted device 101 then either sends a response message indicating the problem or disregards the message (step 411 ).
- the implanted device 101 accesses the command token in bytes 5 - 6 and identifies the type of message/command (step 413 ).
- the implanted device 101 stores the message content data from bytes 7 - 14 to an internal memory.
- the implanted device 101 is able to identify the length and format of the message content data based on the command token and, in some constructions, is able to determine how many data blocks will be included in the message. If the first data block is the only data block in the message (step 417 ), the implanted device 101 processes the command message (step 419 ).
- the implanted device 101 sets an internal flag indicating that the implanted device 101 has received a first data block in a multiple data block message (step 420 ) and waits for additional data blocks before processing the message (step 421 ).
- the implanted device 101 When the flag in the first byte of the data block indicates that the data block is a subsequent data block in a multiple data block message (step 403 ), the implanted device 101 begins by verifying that the implanted device 101 has received a first data block for the message (step 422 ). If the implanted device 101 receives a “subsequent” data block before receiving the first data block in the message (as indicated by the internal “first block received” flag), the “subsequent” data block is disregarded (step 423 ).
- the implanted device 101 appends the additional message data from the data block (bytes 2 - 15 in an intermediate data block and bytes 2 - 14 in a final data block) to stored message data from previously received data blocks (step 424 ).
- the implanted device 101 is able to determine the number of data blocks to expect in a message based on the command token. As such, the implanted device is able to determine if the received “subsequent” data block is the final data block in the message (step 425 ).
- the implanted device 101 continues to wait for the remaining data blocks before processing the message/command (step 421 ). However, if the data block is the final data block in a multiple data block message, the implanted device 101 calculates a final checksum based on the data from all of the data blocks in the message and compares the calculated final checksum to the final checksum value in byte 15 of the final data block (step 429 ). If the final checksum values are not consistent, the implanted device either sends a response message indicating the error or disregards the message (step 431 ). If the final checksum values are consistent, the implanted device 101 processes the multiple data block message.
- the external device 107 processes received response messages according to a similar method. After receiving a response message, the external device checks the first flag and, if appropriate, the checksum value. However, the response message will not include a device ID. Furthermore, the external device 107 will monitor first data blocks of response messages for a response code and a command token to determine how to process the response message.
- the invention provides, among other things, systems and methods for communication between an implanted device implanted in a patient and an external device external to the patient.
- the communication methods utilize data blocks of a defined size to transmit messages and responses.
- the communication format accommodates messages of varying sizes by extending a single message across multiple data blocks.
- the communication format allows the implanted device to identify the external device that has sent the message and disregard messages received from unapproved external devices.
- only the first and last data blocks in multiple data block messages include checksum values.
- all data blocks may include a checksum value indicative of the previous bytes in the data block and all of the bytes in all previously received/transmitted data blocks.
- the data blocks of a multiple data block message may identify the order of the data blocks.
- the flag byte may identify the placement of the data block in the sequence of multiple data blocks instead of only identifying whether the data block is the first data block of a message.
- information such as the device ID can be included in all of the data blocks in a multiple data block message instead of only the first data block.
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Biomedical Technology (AREA)
- General Health & Medical Sciences (AREA)
- Public Health (AREA)
- Life Sciences & Earth Sciences (AREA)
- Animal Behavior & Ethology (AREA)
- Signal Processing (AREA)
- Radiology & Medical Imaging (AREA)
- Veterinary Medicine (AREA)
- Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
- Computer Networks & Wireless Communication (AREA)
- Medical Informatics (AREA)
- Biophysics (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Epidemiology (AREA)
- Heart & Thoracic Surgery (AREA)
- Primary Health Care (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
Abstract
Description
- The invention relates to communication with implantable medical devices. Medical devices, such as cardiac pacemakers and implantable pulse generators of spinal cord stimulation systems are implanted beneath the skin of a human body. Occasionally, these implanted devices receive messages from or send data to an external system. Such messages can include, for example, receiving updated control parameters or sending operational history data that can then be analyzed by the external system.
- Data messages and commands are sent from an external system to a specific implanted medical device in order to properly monitor or implement a treatment protocol. It is important that these data messages and commands are received and processed properly by the correct implanted medical device. In environments such as medical clinic, multiple patients with implanted medical devices are present in the same location. In such situations, an implanted medical device may receive data messages and commands from multiple external devices when the messages were intended to be received by another patient's implanted medical device. If an implanted medical device responds to a message intended for a different patient's device, the results could be inconsistent with the intended treatment protocol for that patient and may be potentially dangerous to the patient.
- Various embodiments of the invention provide methods and systems for two-way communication between an implanted medical device and an external system. Messages are generated by the external system and responses are generated by the implanted device in a data block format. The data blocks are generated according to a defined size and structure. Data blocks generated by the external system and received by the implanted device include device identification information indicating when the received message is to be processed or disregarded by the implanted device. The data block blocks also include mechanisms for communicating larger data messages through multiple data blocks and ensuring that the data block messages were received completely and properly.
- In one embodiment, the invention provides a method of communicating between an implanted device implanted in a patient and an external device external to the patient. The implanted device receives a data block of a defined size and monitors the data block for a first flag. The first flag indicates when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message. When the first flag indicates that the data block is a first data block in the message, the implanted device monitors the data block for a device ID and a command token indicating the type of message that is being received, and stores message content from the data block to a memory of the implanted device. When the first flag indicates that the data block is a subsequent data block in a multiple data block message, the implanted device appends message content from the data block to message content stored in the memory for a previously received data block.
- In some embodiments, the method further includes monitoring the data block for a checksum value. When the first flag indicates that the data block is the first data block in the message, the implanted device compares the checksum value from the data block to a checksum value calculated by the implanted device indicative of the data in the data block. A message error is transmitted by the implanted device when the checksum value from the data block is not consistent with the calculated checksum value. When the final data block in a multiple data block message is received, the implanted device compares the checksum value from the data block to a checksum value calculated by the implanted device indicative of the data in the data block and the data in all of the previously received data blocks of the message.
- In some embodiments, the method further includes comparing the device ID from the data block to one or more stored device IDs indicating external devices which are authorized to communicate with the implanted device. If the device ID from the data block does not correspond to one of the stored device IDs, then the implanted device disregards the data block.
- In some embodiments, the method further includes the implanted device generating a response data block of the defined size in response to receiving the message from the external device. Generating the response data block includes setting a first flag of the response data block indicating when the response data block is a first data block in a response message and when the response data block is a subsequent data block in a multiple data block response message. When the response data block is the first data block in the response message, the implanted device includes a response code, the command token, and message data in the response date block. The response code indicates when a command in the received message has been accepted by the implanted device or rejected. The command token in the response data block is the same as the command token in the received message from the external device. When the data block is a subsequent data block in a multiple data block response message, additional response message content is included in the response data block. After the response data block is generated by the implanted device, the response data block is transmitted to the external device.
- In another embodiment, the invention provides a method of communicating between an implanted device implanted in a patient and an external device external to the patient. The method includes generating, by the external device, a data block of a defined size and transmitting the data block to the implanted device. Generating the data block includes setting a first flag in the data block indicating when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message. When the data block is a first data block in the message, the data block includes a device ID, a command token indicating the type of message, and message content. When the data block is a subsequent data block in a multiple data block message, the data block includes additional message content.
- In another embodiment, the invention provides an implantable medical device including a housing, a wireless communication module, a processor, and a memory. The memory includes instructions that, when executed by the processor, cause the implantable device to receive a data block of a defined size and monitor the data bock of a first flag. The first flag indicates when the data block is a first data block in a message and when the data block is a subsequent data block in a multiple data block message. When the first flag indicates that the data block is the first data block in the message, the instructions cause the implantable device to monitor the data block for a device ID and a command token and to store message content from the data block to the memory. When the first flag indicates that the data block is a subsequent data block in a multiple data block message, the instructions cause the implantable device to append message content from the data block to message content stored in the memory from a previously received data block.
- Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.
-
FIG. 1A is a block diagram of a system for communication between an implantable medical device and an external system. -
FIG. 1B is a partial perspective view of a patient using a spinal cord stimulation system including the system for communication ofFIG. 1A . -
FIG. 2A is a diagram of the content of a first data block in a message received by the implantable medical device ofFIG. 1 from the external system. -
FIG. 2B is a diagram of the content of a final data block in a multiple data block message received by the implantable medical device ofFIG. 1 from the external system. -
FIG. 2C is a diagram of the content of an intermediate data block in a multiple data block message received by the implantable medical device ofFIG. 1 from the external system. -
FIG. 3A is a diagram of the content of a first data block in a response message sent by the implantable medical device ofFIG. 1 to the external system. -
FIG. 3B is a diagram of the content of an intermediate data block in a multiple data block response message sent by the implantable medical device ofFIG. 1 to the external system. -
FIG. 3C is a diagram of the content of a final data block in a multiple data block response message sent by the implantable medical device ofFIG. 1 to the external system. -
FIG. 4 is a flowchart of a method of analyzing a data block received by the implantable device ofFIG. 1 from the external system. - Before any embodiments of the invention are explained in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The invention is capable of other embodiments and of being practiced or of being carried out in various ways.
-
FIG. 1A illustrates a system for communication between an implanted medical device and an external system, which may include an external device. The implanteddevice 101 is designed to be implanted beneath the skin of a patient. The implanteddevice 101 can include, for example, a cardiac pacemaker system or an implantable pulse generator for a spinal cord stimulator system. The implanteddevice 101 includes aprocessor 103 and amemory 105 positioned within a housing of thedevice 101. Theprocessor 103 controls the operation of the implanteddevice 101 by executing instructions stored on thememory 105. In various constructions, thememory 105 can also store control parameters that govern the operation of the implanteddevice 101 and historical operation data indicative of past operation of the implanteddevice 101. - On occasion, an
external device 107 is used to communicate with the implanteddevice 101. Such communication may be used, for example, to send operational commands to the implanteddevice 101, to update control parameters for the implanteddevice 101, or to request performance and operational data from the implanteddevice 101. Because the implanteddevice 101 is designed to be implanted beneath the skin of a patient, wired communication is not feasible. Therefore, both the implanteddevice 101 and theexternal device 107 include wireless communication modules (109 and 111, respectively) to facilitate communication between the two devices. Thewireless communication modules FIG. 1 include radio frequency (RF) transmitters and receivers using the Medical Implant Communication Service (MICS) band. However, in other constructions, the wireless communication can be accomplished using other communication technologies such as Bluetooth. Theexternal device 107 also includes aprocessor 113 that controls the operation of the external device by executing instructions stored on amemory 115. -
FIG. 1B further illustrates one example of a spinalcord stimulation system 120. In this example, the implanteddevice 101 includes several implanted medical electric leads 125 connected to an implantable pulse generator (IPG) 130. The leads 125 each includeelectrode arrays 135 at the distal end of the base lead cable. Theelectrode arrays 135 include multiple electrical stimulation electrodes placed adjacent to the dura of thespine 140 of apatient 145 using an anchor. The spinal column includes the C1-C7 (cervical), T1-T12 (thoracic), L1-L5 (lumbar), and S1-S6 (sacral) vertebrae and theelectrode arrays 135 may be positioned anywhere along thespine 140 to deliver the intended therapeutic effects of spinal cord electrical stimulation in a desired region of thespine 140. The electrodes of theelectrode arrays 135 promote electrical stimulation to the neurons of the spine based on electrical signals generated by theIPG 130. The stimulation is provided from theIPG 130 to the electrodes via the base lead, which is connected to theIPG 130 with the proximal end of the base lead. The body of the lead can traverse through the body of the patient via the spinal column and from the spinal column through the body of the patient to the implant site of theIPG 130. TheIPG 130 communicates with anexternal device 107. In the example ofFIG. 1B , theexternal device 107 can include, for example, any one of a clinical programmer (CP) 150, a patient programmer and charger (PPC) 155, and a pocket (or fob) programmer (PP) 160. - Examples of implantable pulse generators and spinal cord stimulation systems are described in further detail in U.S. application Ser. No. 13/118,764, titled “SYSTEM AND METHOD OF ESTABLISHING A PROTOCOL FOR PROVIDING ELECTRICAL STIMULATION WITH A STIMULATION SYSTEM TO TREAT A PATIENT,” filed on May 31, 2011 and U.S. application Ser. No. 13/118,775, also titled “SYSTEM AND METHOD OF ESTABLISHING A PROTOCOL FOR PROVIDING ELECTRICAL STIMULATION WITH A STIMULATION SYSTEM TO TREAT A PATIENT,” filed on May 31, 2011, both of which are incorporated herein by references in their entirety.
- The implanted
medical device 101 and theexternal device 107 communicate according to a data block-based format. All data blocks used in the communication are of the same, defined size. The data block format used provides for communication of larger volume data message content by allowing messages to be spread across multiple data blocks. Furthermore, the data block format provides mechanisms to ensure that only complete and properly formatted messages received from approved external devices are processed by the implanteddevice 101. -
FIGS. 2A-2C illustrate the format of data blocks generated by theexternal device 107 and transmitted to the implanteddevice 101. Each data block in a message sent according to this example is fifteen bytes in size. However, the data blocks can be larger or smaller in other constructions. The first byte of every data block includes a flag that indicates whether the data block is the first data block in a message. A value of “1” in the first byte indicates that the data block either contains a single data block message or is the first data block of a multiple data block message. A value of “0” indicates that the data block is either a subsequent data block in a multiple data block message or was sent and received in error. - The data block of
FIG. 2A is the data block format used for a single data block message or for the first data block of a multiple data block message. As described above the flag inByte 1 contains a value of “1” to indicate such. The next three bytes in the data block (bytes 2-4) contain a device identifier (“device ID”). The device ID in this example identifies theexternal device 107 sending the message. Upon receiving the message and verifying the correctness of the bytes received, the implanteddevice 101 checks the device ID against a stored list of one or more external devices that are approved to communicate with the implanted device. This mechanism ensures that the implanteddevice 101 responds only to commands that were intended for the implanteddevice 101. In other constructions, the device ID defined in bytes 2-4 of the data block ofFIG. 2A identify the implanteddevice 101 for which the message is intended. In such embodiments, the implanteddevice 101 will only process messages that identify the specific implanteddevice 101 in the device ID bytes. -
Bytes FIG. 2A define a command token. The command token identifies the command being sent. Bytes 7-14 include message data content. When the implanteddevice 101 receives a message including the data block ofFIG. 2A , the command token instructs the implanteddevice 101 how to process the message data content. In some examples, the implanteddevice 101 is also able to determine how many data blocks will be included in the message based on the command token. - The last byte in the data block of
FIG. 2A (byte 15) contains a checksum value. To ensure accuracy of the message included in the data block, the implanteddevice 101 calculates a checksum value based on the previous fourteen bytes in the data block ofFIG. 2A (including the flag byte, the device ID, and the command token) and compares the calculated checksum value to the checksum value inbyte 15 of the data block. The checksum value is calculated by adding all bytes of the data block together and ignoring any overflow. In other constructions, other checksum calculation techniques may be implemented. - If the number of bytes required for the message data content is greater than eight, the message can be transmitted through multiple data blocks.
FIG. 2B illustrates a final data block in a multiple data block message. As described above, the first byte in the data block ofFIG. 2B is a flag byte. The value of the flag byte in the data block ofFIG. 2B is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message. Additional message content is stored in bytes 2-14 of the data block. This additional message content is combined with message content from the first data block (FIG. 2A ). The last byte in the data block ofFIG. 2B (byte 15) is a final checksum value. When the implanteddevice 101 receives the final data block, it calculates a final checksum value indicative of all of the previous bytes in all of the data blocks in the multiple data block message—including the first data block and the checksum value inbyte 15 of the first data block (FIG. 2A ). The implanteddevice 101 verifies the accuracy of the entire message by comparing this calculated checksum value to the final checksum value inbyte 15 of the final data block. - If the number of bytes required for the message data content is greater than 21, the message can be transmitted through three or more data blocks.
FIG. 2C illustrates an intermediate data block in a message sent through three or more data blocks. Again, the first byte in the intermediate data block is a flag byte, the value of which is set to “0” to indicate that the data block is not the first data block in a multiple data block message. The remaining bytes in the data block (bytes 2-15) all contain additional message data content that, when received by the implanteddevice 101, is combined with message content from previously received data blocks. - For example, a message that requires 35 bytes for the message data content would be sent using three data blocks. The first data block would be of the format illustrated in
FIG. 2A . The value of the flag byte would be set to “1” to indicate that it is the first data block in a message. The first data block would also include the device ID of theexternal device 107 that generated and sent the message. It would also include a command token, the first eight bytes of message data content, and a checksum value indicative of the data in the previous fourteen bytes of the first data block. The second data block would be an intermediate data block of the format illustrated inFIG. 2C . The value of the flag byte of the second data block would be set to “0” to indicate that the second data block is a subsequent data block of a multiple data block message. The second data block would also include the next fourteen bytes of message data content. The third and final data block in the three data block message would be of the format illustrated inFIG. 2B . The flag byte again would be set to “0” to indicate that the third data block is a subsequent data block of a multiple data block message. The third data block would also include the next thirteen bytes of message data content. The last byte (byte 15) of the third data block would include a checksum value indicative of the data in the previous fourteen bytes of the third data block and all of the bytes of the first and second data blocks. - In this example, the data block message format is used to implement a command-response form of communication between the
external device 107 and the implanteddevice 101. After receiving a complete message from theexternal device 107, the implanteddevice 101 generates and transmits a response message. The format of the response message is slightly different from the format of the initial command message. However, the response message is also transmitted through a data block of the same size as the command message—in this case fifteen bytes. -
FIGS. 3A-3C illustrate the format of the response message. Like the command messages, the first byte of each data block of the response message is a flag byte. The value of the flag byte is set to “1” to indicate when the data block includes a single data block response message or a first data block in a multiple data block response message. The value of the flag byte is set to “0” to indicate when the data block is a subsequent data block in a multiple data block response message. - The data block of
FIG. 3A illustrates the format of a single data block response message and a first data block of a multiple data block response message. As described above, the first byte is a flag byte, the value of which is set to “1.” The second byte is a response code. The response code indicates whether the command from the command message received by the implanteddevice 101 was processed by the implanteddevice 101. The next two bytes (bytes 3 and 4) include the same command token that was included inbytes FIG. 2A ). Bytes 5-14 include response parameter data. The response code and the command token are used by theexternal device 107 to determine which bytes of the data block include response parameter data and how many data blocks will be included in the response message. - The final byte (byte 15) of the first data block of the response message includes a checksum value. Like the first data block of the command message described above (
FIG. 2A ), the checksum value of the first data block of the response message is also indicative of the content in the previous bytes (bytes 1-14) of the first data block of the response message. As such, when theexternal device 107 receives a first data block of a response message, theexternal device 107 calculates a checksum value based on the data in bytes 1-14 and compares the calculates checksum value to the checksum value inbyte 15 to verify the accuracy of the message content. -
FIG. 3B illustrates an intermediate data block of a response message that includes at least three data blocks. The first byte in the intermediate data block includes a flag, the value of which is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message. The remaining bytes of the intermediate data block include the next fourteen bytes of response parameter data for the response message. -
FIG. 3C illustrates a final data block of a response message that includes at least two data blocks. The first byte in the final data block includes a flag, the value of which is set to “0” to indicate that the data block is a subsequent data block in a multiple data block message. Bytes 2-14 include the last fourteen bytes of response parameter data for the response message. The last byte of the final data block (byte 15) includes a final checksum value. Like in the final data block of the command message described above (FIG. 3B ), the final checksum value is indicative of the content in the previous bytes (bytes 1-14) of the final data block and all of the bytes in the previous data blocks of the multiple data block response message. As such, when theexternal device 107 receives the final data block of a response message, theexternal device 107 calculates a final checksum value based on the data in bytes 1-14 of the final data block and all of the bytes of the previous data blocks in the response message. Theexternal device 107 then compares the calculated final checksum value to the checksum value inbyte 15 of the final data block to verify the accuracy of the response message content. - As described above, the implanted
device 101 can detect an error in the format of a message received from an external device based on the checksum value. Furthermore, the implanteddevice 101 can determine when the device ID of the external device sending the message is not recognized. In either case, the implanteddevice 101 can either ignore the defective message or can send a response message indicating that the message was defective and was not processed by the implanteddevice 101. When theexternal device 107 receives such an “error” message from the implanteddevice 101, the external device will correct the message and resend. Alternatively, theexternal device 107 monitors for a response message and resends the command message if a response is not received within a defined period of time. -
FIG. 4 illustrates how the implanteddevice 101 receives and processes data blocks received from theexternal device 107 according to the format described above in reference toFIGS. 2A-2C . The implanteddevice 101 begins by receiving a data block through the wireless communication module 109 (step 401). The implanteddevice 101 monitors the first byte (i.e., the flag byte) of the received data block to determine whether the data block is a first data block of a message (step 403). If the flag byte indicates that the data block is a first data block of a message, the implanted device verifies the accuracy of the received message by comparing the checksum value inbyte 15 of the data block to a calculated checksum value (step 405). If the calculated checksum value is not consistent with the checksum value inbyte 15, the implanteddevice 101 either sends a response message indicating the error condition or disregards the data block (step 407). - If the checksum values verify the accuracy of the message content in the first data block, the implanted
device 101 then checks the device ID in bytes 2-4 to determine whether the external device sending the message is authorized to send commands to the implanted device 101 (step 409). If the device ID is not recognized by the implanteddevice 101, the command message is not processed. The implanteddevice 101 then either sends a response message indicating the problem or disregards the message (step 411). - If the device ID is recognized, the implanted
device 101 accesses the command token in bytes 5-6 and identifies the type of message/command (step 413). The implanteddevice 101 stores the message content data from bytes 7-14 to an internal memory. As noted above, the implanteddevice 101 is able to identify the length and format of the message content data based on the command token and, in some constructions, is able to determine how many data blocks will be included in the message. If the first data block is the only data block in the message (step 417), the implanteddevice 101 processes the command message (step 419). However, if other data blocks are to be received, the implanteddevice 101 sets an internal flag indicating that the implanteddevice 101 has received a first data block in a multiple data block message (step 420) and waits for additional data blocks before processing the message (step 421). - When the flag in the first byte of the data block indicates that the data block is a subsequent data block in a multiple data block message (step 403), the implanted
device 101 begins by verifying that the implanteddevice 101 has received a first data block for the message (step 422). If the implanteddevice 101 receives a “subsequent” data block before receiving the first data block in the message (as indicated by the internal “first block received” flag), the “subsequent” data block is disregarded (step 423). - If the internal flag indicates that a first data block was received before the subsequent data block (step 422), the implanted
device 101 appends the additional message data from the data block (bytes 2-15 in an intermediate data block and bytes 2-14 in a final data block) to stored message data from previously received data blocks (step 424). As described above, the implanteddevice 101 is able to determine the number of data blocks to expect in a message based on the command token. As such, the implanted device is able to determine if the received “subsequent” data block is the final data block in the message (step 425). If the data block is not the final data block in the message, the implanteddevice 101 continues to wait for the remaining data blocks before processing the message/command (step 421). However, if the data block is the final data block in a multiple data block message, the implanteddevice 101 calculates a final checksum based on the data from all of the data blocks in the message and compares the calculated final checksum to the final checksum value inbyte 15 of the final data block (step 429). If the final checksum values are not consistent, the implanted device either sends a response message indicating the error or disregards the message (step 431). If the final checksum values are consistent, the implanteddevice 101 processes the multiple data block message. - The
external device 107 processes received response messages according to a similar method. After receiving a response message, the external device checks the first flag and, if appropriate, the checksum value. However, the response message will not include a device ID. Furthermore, theexternal device 107 will monitor first data blocks of response messages for a response code and a command token to determine how to process the response message. - Thus, the invention provides, among other things, systems and methods for communication between an implanted device implanted in a patient and an external device external to the patient. The communication methods utilize data blocks of a defined size to transmit messages and responses. The communication format accommodates messages of varying sizes by extending a single message across multiple data blocks. Furthermore, the communication format allows the implanted device to identify the external device that has sent the message and disregard messages received from unapproved external devices.
- The systems and methods described above are exemplary. Other constructions and embodiments are possible. For example, in the methods described above, only the first and last data blocks in multiple data block messages include checksum values. In other constructions, all data blocks may include a checksum value indicative of the previous bytes in the data block and all of the bytes in all previously received/transmitted data blocks. Furthermore, in other constructions, the data blocks of a multiple data block message may identify the order of the data blocks. For example, the flag byte may identify the placement of the data block in the sequence of multiple data blocks instead of only identifying whether the data block is the first data block of a message. Additionally, in other constructions, information such as the device ID can be included in all of the data blocks in a multiple data block message instead of only the first data block. Various features and advantages of the invention are set forth in the following claims.
Claims (24)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/334,361 US9098610B2 (en) | 2011-12-22 | 2011-12-22 | Communication for implantable medical devices |
US14/715,915 US9154219B2 (en) | 2011-12-22 | 2015-05-19 | Communication for implantable medical devices |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/334,361 US9098610B2 (en) | 2011-12-22 | 2011-12-22 | Communication for implantable medical devices |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/715,915 Continuation US9154219B2 (en) | 2011-12-22 | 2015-05-19 | Communication for implantable medical devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130166642A1 true US20130166642A1 (en) | 2013-06-27 |
US9098610B2 US9098610B2 (en) | 2015-08-04 |
Family
ID=48655621
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/334,361 Active 2032-07-01 US9098610B2 (en) | 2011-12-22 | 2011-12-22 | Communication for implantable medical devices |
US14/715,915 Active US9154219B2 (en) | 2011-12-22 | 2015-05-19 | Communication for implantable medical devices |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/715,915 Active US9154219B2 (en) | 2011-12-22 | 2015-05-19 | Communication for implantable medical devices |
Country Status (1)
Country | Link |
---|---|
US (2) | US9098610B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170048655A1 (en) * | 2014-04-21 | 2017-02-16 | Lg Electronics Inc. | Method and apparatus for transmitting data using bluetooth low energy in wireless communication system |
US11582612B2 (en) * | 2018-06-12 | 2023-02-14 | Impulse Dynamics Nv | Power coupling modulation transmission |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150018728A1 (en) | 2012-01-26 | 2015-01-15 | Bluewind Medical Ltd. | Wireless neurostimulators |
US9861812B2 (en) | 2012-12-06 | 2018-01-09 | Blue Wind Medical Ltd. | Delivery of implantable neurostimulators |
US10105540B2 (en) | 2015-11-09 | 2018-10-23 | Bluewind Medical Ltd. | Optimization of application of current |
US10201712B2 (en) * | 2016-01-28 | 2019-02-12 | Medtronic, Inc. | Telemetry overuse reduction in an implantable device |
US10124178B2 (en) | 2016-11-23 | 2018-11-13 | Bluewind Medical Ltd. | Implant and delivery tool therefor |
US20180353764A1 (en) | 2017-06-13 | 2018-12-13 | Bluewind Medical Ltd. | Antenna configuration |
US11400299B1 (en) | 2021-09-14 | 2022-08-02 | Rainbow Medical Ltd. | Flexible antenna for stimulator |
Citations (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5342408A (en) * | 1993-01-07 | 1994-08-30 | Incontrol, Inc. | Telemetry system for an implantable cardiac device |
US5902949A (en) * | 1993-04-09 | 1999-05-11 | Franklin N. Eventoff | Musical instrument system with note anticipation |
US20020050925A1 (en) * | 1997-07-11 | 2002-05-02 | Steven Willard Arms | System for remote powering and communication with a network of addressable multichannel sensing modules |
US20050192649A1 (en) * | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for providing variable medical information |
US20050192842A1 (en) * | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for authorizing and processing reimbursements for services provided in the collection of implantable medical device data |
US20060173444A1 (en) * | 2000-01-21 | 2006-08-03 | Medtronic, Inc. | Ambulatory medical apparatus with hand held communication device |
US7177690B2 (en) * | 1999-07-27 | 2007-02-13 | Advanced Bionics Corporation | Implantable system having rechargeable battery indicator |
US20070049990A1 (en) * | 2005-08-30 | 2007-03-01 | Klostermann Daniel J | Telemetry protocol for ultra low error rates useable in implantable medical devices |
US7269186B2 (en) * | 2001-08-06 | 2007-09-11 | Qualcomm Incorporated | Protocol for framing a payload |
US7457669B2 (en) * | 2004-06-17 | 2008-11-25 | Cardiac Pacemakers, Inc. | On-demand retransmission of data with an implantable medical device |
US20090018598A1 (en) * | 2007-07-10 | 2009-01-15 | Thomas Doerr | System for the remote programming of a personal medical device |
US7519430B2 (en) * | 2004-06-17 | 2009-04-14 | Cardiac Pacemakers, Inc. | Dynamic telemetry encoding for an implantable medical device |
US20100013668A1 (en) * | 2007-01-31 | 2010-01-21 | St Jude Medical Ab | Method in a medical telemetry system and medical telemetry system |
US20100073127A1 (en) * | 2008-09-24 | 2010-03-25 | Toshiba Tec Kabushiki Kaisha | Device use restricting system |
US20100094654A1 (en) * | 2008-06-03 | 2010-04-15 | Andrew Royal Stewart | Implantable storage device for maintaining medical records |
US7743151B2 (en) * | 2004-08-05 | 2010-06-22 | Cardiac Pacemakers, Inc. | System and method for providing digital data communications over a wireless intra-body network |
US7755527B2 (en) * | 2008-01-16 | 2010-07-13 | Microchip Technology Incorporated | Read and write interface communications protocol for digital-to-analog signal converter with non-volatile memory |
US20110179405A1 (en) * | 2006-10-24 | 2011-07-21 | Dicks Kent E | Systems for remote provisioning of electronic devices |
US20110270025A1 (en) * | 2010-04-30 | 2011-11-03 | Allergan, Inc. | Remotely powered remotely adjustable gastric band system |
US20120163481A1 (en) * | 2006-04-20 | 2012-06-28 | Lifescan Scotland Ltd. | Method for transmitting data in a blood glucose system and corresponding blood glucose system |
US8468372B2 (en) * | 1997-05-13 | 2013-06-18 | Round Rock Research, Llc | Diagnostic and managing distributed processor system |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6738670B1 (en) | 2000-06-19 | 2004-05-18 | Medtronic, Inc. | Implantable medical device telemetry processor |
US7155290B2 (en) * | 2003-06-23 | 2006-12-26 | Cardiac Pacemakers, Inc. | Secure long-range telemetry for implantable medical device |
US7831828B2 (en) * | 2004-03-15 | 2010-11-09 | Cardiac Pacemakers, Inc. | System and method for securely authenticating a data exchange session with an implantable medical device |
GB0409769D0 (en) | 2004-04-30 | 2004-06-09 | Algotec Ltd | Electrical nerve stimulation device |
US7565197B2 (en) * | 2004-06-18 | 2009-07-21 | Medtronic, Inc. | Conditional requirements for remote medical device programming |
US20060020304A1 (en) | 2004-07-20 | 2006-01-26 | Medtronic, Inc. | Medical device telemetry arbitration system using time of response |
US7686768B2 (en) | 2005-11-23 | 2010-03-30 | Vital Sensors Holding Company, Inc. | Implantable pressure monitor |
US7574266B2 (en) | 2006-01-19 | 2009-08-11 | Medtronic, Inc. | System and method for telemetry with an implantable medical device |
US7940933B2 (en) | 2006-08-18 | 2011-05-10 | Medtronic, Inc. | Secure telemetric link |
US8515547B2 (en) * | 2007-08-31 | 2013-08-20 | Cardiac Pacemakers, Inc. | Wireless patient communicator for use in a life critical network |
US8572459B2 (en) | 2008-10-16 | 2013-10-29 | Codman Neuro Sciences Sárl | Insuring proper communication with chosen implant among multiple implants in proximity to one another |
KR20120026077A (en) | 2009-04-30 | 2012-03-16 | 삼성전자주식회사 | Method and system for managing a body area network using a coordinator device |
US8649757B2 (en) | 2010-01-13 | 2014-02-11 | Medtronic, Inc. | Proximity based selection of an implantable medical device for far field communication |
US9072903B2 (en) * | 2011-05-31 | 2015-07-07 | Greatbatch Ltd. | System and method of establishing a protocol for providing electrical stimulation with a stimulation system to treat a patient |
-
2011
- 2011-12-22 US US13/334,361 patent/US9098610B2/en active Active
-
2015
- 2015-05-19 US US14/715,915 patent/US9154219B2/en active Active
Patent Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5342408A (en) * | 1993-01-07 | 1994-08-30 | Incontrol, Inc. | Telemetry system for an implantable cardiac device |
US5902949A (en) * | 1993-04-09 | 1999-05-11 | Franklin N. Eventoff | Musical instrument system with note anticipation |
US8468372B2 (en) * | 1997-05-13 | 2013-06-18 | Round Rock Research, Llc | Diagnostic and managing distributed processor system |
US20020050925A1 (en) * | 1997-07-11 | 2002-05-02 | Steven Willard Arms | System for remote powering and communication with a network of addressable multichannel sensing modules |
US7177690B2 (en) * | 1999-07-27 | 2007-02-13 | Advanced Bionics Corporation | Implantable system having rechargeable battery indicator |
US20060173444A1 (en) * | 2000-01-21 | 2006-08-03 | Medtronic, Inc. | Ambulatory medical apparatus with hand held communication device |
US7347819B2 (en) * | 2000-01-21 | 2008-03-25 | Medtronic Minimed, Inc. | Ambulatory medical apparatus and method using a robust communication protocol |
US7269186B2 (en) * | 2001-08-06 | 2007-09-11 | Qualcomm Incorporated | Protocol for framing a payload |
US20050192649A1 (en) * | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for providing variable medical information |
US20050192842A1 (en) * | 2004-02-27 | 2005-09-01 | Cardiac Pacemakers, Inc. | Systems and methods for authorizing and processing reimbursements for services provided in the collection of implantable medical device data |
US7457669B2 (en) * | 2004-06-17 | 2008-11-25 | Cardiac Pacemakers, Inc. | On-demand retransmission of data with an implantable medical device |
US7519430B2 (en) * | 2004-06-17 | 2009-04-14 | Cardiac Pacemakers, Inc. | Dynamic telemetry encoding for an implantable medical device |
US7743151B2 (en) * | 2004-08-05 | 2010-06-22 | Cardiac Pacemakers, Inc. | System and method for providing digital data communications over a wireless intra-body network |
US8265768B2 (en) * | 2005-08-30 | 2012-09-11 | Boston Scientific Neuromodulation Corporation | Telemetry protocol for ultra low error rates useable in implantable medical devices |
US20070049990A1 (en) * | 2005-08-30 | 2007-03-01 | Klostermann Daniel J | Telemetry protocol for ultra low error rates useable in implantable medical devices |
US20120163481A1 (en) * | 2006-04-20 | 2012-06-28 | Lifescan Scotland Ltd. | Method for transmitting data in a blood glucose system and corresponding blood glucose system |
US20110179405A1 (en) * | 2006-10-24 | 2011-07-21 | Dicks Kent E | Systems for remote provisioning of electronic devices |
US20100013668A1 (en) * | 2007-01-31 | 2010-01-21 | St Jude Medical Ab | Method in a medical telemetry system and medical telemetry system |
US20090018598A1 (en) * | 2007-07-10 | 2009-01-15 | Thomas Doerr | System for the remote programming of a personal medical device |
US7755527B2 (en) * | 2008-01-16 | 2010-07-13 | Microchip Technology Incorporated | Read and write interface communications protocol for digital-to-analog signal converter with non-volatile memory |
US20100094654A1 (en) * | 2008-06-03 | 2010-04-15 | Andrew Royal Stewart | Implantable storage device for maintaining medical records |
US20100073127A1 (en) * | 2008-09-24 | 2010-03-25 | Toshiba Tec Kabushiki Kaisha | Device use restricting system |
US20110270025A1 (en) * | 2010-04-30 | 2011-11-03 | Allergan, Inc. | Remotely powered remotely adjustable gastric band system |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170048655A1 (en) * | 2014-04-21 | 2017-02-16 | Lg Electronics Inc. | Method and apparatus for transmitting data using bluetooth low energy in wireless communication system |
US10142767B2 (en) * | 2014-04-21 | 2018-11-27 | Lg Electronics Inc. | Method and apparatus for transmitting data using Bluetooth low energy in wireless communication system |
US11582612B2 (en) * | 2018-06-12 | 2023-02-14 | Impulse Dynamics Nv | Power coupling modulation transmission |
Also Published As
Publication number | Publication date |
---|---|
US9098610B2 (en) | 2015-08-04 |
US9154219B2 (en) | 2015-10-06 |
US20150249495A1 (en) | 2015-09-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9154219B2 (en) | Communication for implantable medical devices | |
US9974108B2 (en) | Paired communication between an implanted medical device and an external control device | |
US11103706B2 (en) | Systems and methods for enhancing function of spine stabilization muscles associated with a spine surgery intervention | |
US9827424B2 (en) | System and method of establishing a protocol for providing electrical stimulation with a stimulation system to treat a patient | |
US7023359B2 (en) | Telemetry module with configurable physical layer for use with an implantable medical device | |
US6985088B2 (en) | Telemetry module with configurable data layer for use with an implantable medical device | |
US9375574B2 (en) | System and method of providing computer assisted stimulation programming (CASP) | |
US8265768B2 (en) | Telemetry protocol for ultra low error rates useable in implantable medical devices | |
US9686781B2 (en) | Establishing an RF link between a base station and a medical device | |
US20060020302A1 (en) | Medical device telemetry arbitration system based upon user selection | |
EP1796787B1 (en) | Medical device telemetry arbitration system using time of response | |
US20130268023A1 (en) | Tibial nerve stimulation | |
US11331488B2 (en) | Systems and methods for enhancing function of spine stabilization muscles associated with a spine surgery intervention | |
US20040024429A1 (en) | Configuration of implanted devices | |
US20230321438A1 (en) | Systems and methods for enhancing function of spine stabilization muscles associated with a spine surgery intervention | |
US20190060645A1 (en) | Wireless bone stimulator system and method | |
AU2020200328A1 (en) | Systems and methods for enhancing function of spine stabilization muscles associated with a spine surgery intervention |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GREATBATCH LTD., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:POLEFKO, RICHARD J.;HOWARD, DAVID J.;LEYH, SCOTT G.;AND OTHERS;SIGNING DATES FROM 20111216 TO 20111220;REEL/FRAME:027432/0645 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: MANUFACTURERS AND TRADERS TRUST COMPANY, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:GREATBATCH, INC.;GREATBATCH LTD.;ELECTROCHEM SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:036980/0482 Effective date: 20151027 |
|
AS | Assignment |
Owner name: QIG GROUP, LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GREATBATCH LTD.;REEL/FRAME:037810/0051 Effective date: 20160212 |
|
AS | Assignment |
Owner name: NUVECTRA CORPORATION, TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:QIG GROUP, LLC;REEL/FRAME:038455/0153 Effective date: 20160314 |
|
AS | Assignment |
Owner name: GREATBATCH LTD., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 Owner name: ELECTROCHEM SOLUTIONS, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 Owner name: GREATBATCH INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 Owner name: QIG GROUP LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 Owner name: MICRO POWER ELECTRONICS, INC., OREGON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 Owner name: NEURONEXUS TECHNOLOGIES, INC., MICHIGAN Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY;REEL/FRAME:039132/0773 Effective date: 20160418 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: CIRTEC MEDICAL CORP., MINNESOTA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NUVECTRA CORPORATION;REEL/FRAME:052185/0680 Effective date: 20200317 |
|
AS | Assignment |
Owner name: MICRO POWER ELECTRONICS, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: PRECIMED INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: GREATBATCH-GLOBE TOOL, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: NEURONEXUS TECHNOLOGIES, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: ELECTROCHEM SOLUTIONS, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: GREATBATCH LTD., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 Owner name: GREATBATCH, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:060938/0069 Effective date: 20210903 |
|
AS | Assignment |
Owner name: MICRO POWER ELECTRONICS, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: PRECIMED INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: GREATBATCH-GLOBE TOOL, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: NEURONEXUS TECHNOLOGIES, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: ELECTROCHEM SOLUTIONS, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: GREATBATCH LTD., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 Owner name: GREATBATCH, INC., NEW YORK Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MANUFACTURERS AND TRADERS TRUST COMPANY (AS ADMINISTRATIVE AGENT);REEL/FRAME:061659/0858 Effective date: 20210903 |
|
AS | Assignment |
Owner name: BMO HARRIS BANK N.A., AS COLLATERAL AGENT, ILLINOIS Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:CIRTEC MEDICAL CORP.;REEL/FRAME:062559/0098 Effective date: 20230130 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |