Programming system for medical devices, a server for such a system and a method for managing the system

• US 20040073276A1
• Filed: 11/10/2003
• Published: 04/15/2004
• Est. Priority Date: 12/22/2000
• Status: Abandoned Application

• Current Assignee: St. Jude Medical AB (Abbott Laboratories Incorporated)
• Original Assignee: St. Jude Medical AB (Abbott Laboratories Incorporated)
• Inventors: Samuelsson, Eric
• Application Number:
  US10/451,044
• Publication Number:
  US 20040073276A1
• Time in Patent Office: Days
• US Class Current: 607/60
• CPC Class Codes: A61N 1/37211 Means for communicating with stimulators
• CPC Class Codes: A61N 1/37264 Changing the program; Upgrading firmware
• CPC Class Codes: A61N 1/37282 characterised by communication with experts in remote locations using a network
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

In a system for managing the programming of an implantable medical device, a programmer communicates with the implantable medical device via a transceiver, and also communicates with a remote server via a network. The programmer includes a machine-readable code module that interrogates the implanted device to obtain identifying information associated with the implanted device, and the programmer transmits this identifying information, as well as programmer identifying information, to the remote server via the network. Based on this identifying information, the remote server selects an operating program for the programmer and/or the implanted device, and transmits the operating program to the programmer for appropriate installation.

Claims

1. A programming system for an implantable medical device, said system including a programmer (20) with a transceiver (25) for communicating with implanted medical devices (10) and a memory (22), characterised in that said programmer further comprises a network connection (26) for establishing communication with a remote server (30) through a network (40) and

a first machine readable code module (221) arranged to interrogate an implanted device (10) via said transceiver to obtain identifying information associated with said implanted device, transmit said device identifying information and programmer identifying information to said remote server,

receive from said server operating software for execution by said programmer for programming said implanted medical device and install said operating software in said programmer.

2. A programming system as claimed in claim 1, characterised in that said first machine readable code module (221) is further arranged to enable receipt of machine readable code for operating said device by said programmer (20) and

transmission of said machine readable code for operating said device to said device for installation.

3. A system as claimed in claim 1 or 2, characterised in that said implantable medical device includes a hardware platform and an installed operating software module, wherein said first machine readable code module is arranged to read and transmit to said server information identifying said medical device, said installed software and possibly said hardware platform.

4. A system as claimed in any previous claim, characterised in that said programmer includes a hardware platform and an installed programming software module, wherein said first machine readable code module (221) is arranged to read and transmit to said server information identifying said programmer, said installed software and possibly said hardware platform.

5. A system as claimed in any previous claim, characterised in that said implantable medical device is a cardiac stimulating device.

6. A server for communicating with programmers (20) of implantable medical devices (10) through a network (40), characterised in that said server (30) includes storage means (31, 32) for storing identifying information associated with implantable medical devices, programmers and software modules for operation of said medical devices and programmers, said server further being arranged to process software requests from a programmer (20), and download to said programmer software modules for installation on said programmer (20)

7. A server as claimed in claim 6, further arranged to download to said programmer software modules for installation on said medical device (10).

8. A method of managing a system for programming an implantable medical device including an implantable medical device (10), a programmer (20) adapted to communicate with said implantable medical device and a remote server (30), wherein said programmer is adapted to communicate with said remote server through a network (40) said method including the steps of:

interrogating said medical device using said programmer to obtain device identifying information,

transmitting said device identifying information and information identifying said programmer to said server,

downloading operating software to said programmer for installation on said programmer on the basis of said identifying information.

9. A method as claimed in claim 8, further including the step of:

downloading operating software for said medical device to said programmer for installation on said device on the basis of said identifying information.

10. A method as claimed in. Claim 8 or 9, characterised in that the interrogation step includes

interrogating said medical device to obtain information identifying said device and information identifying an operating software module installed on said device.

11. A method as claimed in any one of claims 8 to 10, characterised in that said transmitting step includes transmitting information identifying said programmer and information identifying an operating software module installed on said programmer.

12. A method as claimed in claim any one of claims 8 to 11, characterised by the steps of

in said server, determining a required operating software module for said programmer (20) and/or said implanted medical device (10), comparing identifying information of said required software module with said transmitted software identifying information and downloading said required software if the transmitted software identifying information is not the same as said required software identifying information.