# US 2020/0139141 A1 · Methods of operating a system for management of implantable medical devices (imds) using reconciliation operations and revocation data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0139141 A1
- Document ID: US20200139141A1
- Status: Published application
- Kind: A1
- Application number: 16/179,744
- Filed: 2018-11-02
- Published: 2020-05-07
- Earliest claimed: 2018-11-02
- Assignees: Advanced Neuromodulation Systems, Inc.
- Applicants: Advanced Neuromodulation Systems, Inc
- Inventors: Christopher S. L. Crawford
- Web page: https://patentgrep.com/patent/US20200139141A1

## CPC

- A61N 1/37276: {characterised by means for reducing power consumption during telemetry}
- A61N 1/37217: {characterised by the communication link, e.g. acoustic or tactile}
- A61N 1/37258: {Alerting the patient}
- A61N 1/37282: {characterised by communication with experts in remote locations using a network}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G16H 20/00: ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H 40/40: for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
- G16H 40/63: for local operation
- G16H 40/67: for remote operation
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3247: {involving digital signatures}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/104: {Grouping of entities}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- A61N 1/025: {Digital circuitry features of electrotherapy devices, e.g. memory, clocks, processors}
- A61N 1/0551: {Spinal or peripheral nerve electrodes}
- A61N 1/0553: {Paddle shaped electrodes, e.g. for laminotomy}
- A61N 1/36062: {Spinal stimulation}
- A61N 1/36067: {Movement disorders, e.g. tremor or Parkinson disease (stimulating motor muscle A61N1/36003)}
- A61N 1/37247: {User interfaces, e.g. input or presentation means}
- A61N 1/37254: {Pacemaker or defibrillator security, e.g. to prevent or inhibit programming alterations by hackers or unauthorised individuals}
- A61N 1/37264: {Changing the program; Upgrading firmware}
- H04L 2209/80: Wireless
- H04L 2209/88: Medical equipments
- A61N: ELECTROTHERAPY; MAGNETOTHERAPY; RADIATION THERAPY; ULTRASOUND THERAPY (measurement of bioelectric currents A61B; surgical instruments, devices or methods for transferring non-mechanical forms of energy to or from the body A61B18/00; anaesthetic apparatus in general A61M; incandescent lamps H01K; infrared radiators for heating H05B)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a method for operating a system for management of implantable medical devices (IMDs), comprises: conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur while the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs; conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs; reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming; and distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.

## Claims

### Claim 1

A method for operating a system for management of implantable medical devices (IMDs), comprising:
conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur while the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs and wherein the communication sessions with the plurality of clinician programmer devices include communication of data pertaining to offline programming of IMDs;
conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs;
reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming; and
distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
identifying a legitimate clinician programmer device that uses a cryptographic key to be revoked;
replacing the cryptographic key on the legitimate clinician programmer device during a communication session with the respective clinician programmer device.

### Claim 3 (depends on 2)

The method of claim 2 wherein the identifying and replacing are performed before the revocation data for the cryptographic key of the legitimate clinician programmer device is revoked.

### Claim 4 (depends on 2)

The method of claim 2 wherein the cryptographic key is identified as being used on another unauthorized clinician programmer device.

### Claim 5 (depends on 1)

The method of claim 1 wherein the reconciling identifies use of a common cryptographical key on two separate clinician programmer devices.

### Claim 6 (depends on 1)

The method of claim 1 wherein the reconciling identifies a cloned clinician programming device conducting programming concurrently with programming by a corresponding legitimate clinician programming device.

### Claim 7 (depends on 1)

The method of claim 1 wherein the IMDs communicate programming session metadata for analysis during the reconciling to identify unauthorized programming.

### Claim 8 (depends on 7)

The method of claim 7 wherein the programming session metadata includes clinician programmer device details.

### Claim 9 (depends on 7)

The method of claim 7 wherein the programming session metadata includes clinician identity credentials.

### Claim 10 (depends on 7)

The method of claim 7 wherein the programming session metadata includes programming timing data.

### Claim 11

A method for operating a system for management of implantable medical devices (IMDs), comprising:
conducting communications sessions with a plurality of clinician programmer devices, wherein some of the communication sessions occur while the plurality of clinician programmer devices are engaged in respective programming sessions with IMDs and wherein the communication sessions with the plurality of clinician programmer devices include communication of data pertaining to offline programming of IMDs;
conducting communications sessions with a plurality of patient controller devices, wherein the communication sessions with the patient controller devices include communication of data pertaining to offline programming of IMDs;
reconciling programming session data received from the plurality of clinician programmer devices with programming session data received from patient controller devices to identify instances of unauthorized IMD programming, wherein the reconciling identifies use of one or more compromised cryptographic keys to perform offline programming of one or more IMDs; and
distributing revocation data to patient controller devices to be downloaded to corresponding IMDs, wherein the revocation data identifies cryptographic keys that are no longer trusted.

### Claim 12 (depends on 11)

The method of claim 11 further comprising:
identifying a legitimate clinician programmer device that uses a cryptographic key to be revoked;
replacing the cryptographic key on the legitimate clinician programmer device during a communication session with the respective clinician programmer device.

### Claim 13 (depends on 12)

The method of claim 12 wherein the identifying and replacing are performed before the revocation data for the cryptographic key of the legitimate clinician programmer device is revoked.

### Claim 14 (depends on 12)

The method of claim 12 wherein the cryptographic key is identified as being used on another unauthorized clinician programmer device.

### Claim 15 (depends on 11)

The method of claim 11 wherein the reconciling identifies use of a common cryptographical key on two separate clinician programmer devices.

### Claim 16 (depends on 11)

The method of claim 11 wherein the reconciling identifies a cloned clinician programming device conducting programming concurrently with programming by a corresponding legitimate clinician programming device.

### Claim 17 (depends on 11)

The method of claim 11 wherein the MDs communicate programming session metadata for analysis during the reconciling to identify unauthorized programming.

### Claim 18 (depends on 17)

The method of claim 17 wherein the programming session metadata includes clinician programmer device details.

### Claim 19 (depends on 17)

The method of claim 17 wherein the programming session metadata includes clinician identity credentials.

### Claim 20 (depends on 17)

The method of claim 17 wherein the programming session metadata includes programming timing data.
