METHODS AND SYSTEMS FOR AUTHORIZING A PORTABLE DEVICE TO COMMUNICATE WITH A MEDICAL DEVICE

• US 20140365654A1
• Filed: 06/06/2014
• Published: 12/11/2014
• Est. Priority Date: 06/06/2013
• Status: Abandoned Application

• Current Assignee: Boston Scientific Neuromodulation Corporation (Boston Scientific Corporation)
• Original Assignee: Boston Scientific Neuromodulation Corporation (Boston Scientific Corporation)
• Inventors: Carbunaru, Rafael, Kothandaraman, Sridhar, Zottola, Dennis, Huerto, Archie Eslabon
• Application Number:
  US14/298,787
• Publication Number:
  US 20140365654A1
• Time in Patent Office: Days
• US Class Current: 709/225
• CPC Class Codes: A61N 1/37235 Aspects of the external programmer
• CPC Class Codes: A61N 1/37247 User interfaces, e.g. input or presentation means
• CPC Class Codes: A61N 1/37252 Details of algorithms or data aspects of communication system, e.g. handshaking, transmitting specific data or segmenting data
• CPC Class Codes: A61N 1/37254 Pacemaker or defibrillator security, e.g. to prevent or inhibit programming alterations by hackers or unauthorised individuals
• 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: G16H 40/63 for local operation
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: H04L 2209/88 Medical equipments
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: 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
• CPC Class Codes: H04L 9/3226 using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 4/38 for collecting sensor information

Abstract

A method, server, and portable device for communicating with an implantable medical device is disclosed. A test that determines whether at least one device configuration parameter respectively corresponding to at least one feature to be tested on the portable device is fulfilled by the portable device is performed. The portable device is authorized to communicate with the implantable medical device only if the feature(s) is fulfilled by the portable device. Authorization of the portable device to communicate with the implantable medical device is denied if the at least one feature is not fulfilled by the portable device.

Claims

1. A method for authorizing a portable device to communicate with an implantable medical device, the method comprising:

performing a test that determines whether at least one device configuration parameter respectively corresponding to at least one feature to be tested on the portable device is fulfilled by the portable device;

authorizing the portable device to communicate with the implantable medical device only if the at least one feature is fulfilled by the portable device; and

denying authorization of the portable device to communicate with the implantable medical device if the at least one feature is not fulfilled by the portable device.

2. The method of claim 1, further comprising providing a graphical user interface that allows the portable device to communicate with the implantable medical device only if the portable device is authorized to communicate with the implantable medical device.

3. The method of claim 1, wherein the portable device comprises a personal smart device.

4. The method of claim 1, wherein the feature to be tested on the portable device is one of a storage memory of the portable device, a random access memory of the portable device, a capability of the portable device to connect to a type of a network, a screen height of the portable device, a screen width of the portable device, an operating system of the portable device, a model of the portable device, a type of central processing unit of the portable device, a speed of central processing unit of the portable device, a type of graphic library of the portable device, a USB capability of the portable device, an API level of the portable device, a near field communication capability of the portable device, a Bluetooth®

capability of the portable device, a wireless capability of the portable device, a hardware connectivity performance of the portable device, a type of security capability of the portable device, a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to a remote system.

5. The method of claim 1, wherein performing the test comprises requesting an input from a user, and receiving the input from the user, wherein the at least one feature is determined to be fulfilled by the portable device based on the input received from the user.

6. The method of claim 5, wherein the feature to be tested is one of a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to a remote system.

7. The method of claim 1, further comprising:

detecting a modification in the portable device, wherein the modification is at least one of an installation of software or firmware, an upgrade of software or firmware, an enablement of a capability, and a disablement of a capability; and

automatically de-authorizing the modified portable device from communicating with the implantable medical device when the modification is detected.

8. The method of claim 7, further comprising:

performing the test that determines whether the at least one device configuration parameter respectively corresponding to the at least one feature to be tested is fulfilled by the modified portable device; and

authorizing the modified portable device to communicate with the implantable medical device if the at least one feature is fulfilled by the modified portable device.

9. The method of claim 1, further comprising:

transmitting, to a server, a request to download a configuration file; and

receiving the configuration file from the server into the portable device, wherein the configuration file includes the at least one device configuration parameter corresponding to the at least one feature to be tested on the portable device.

10. The method of claim 9, further comprising:

receiving an updated configuration file from the server, wherein the updated configuration file includes at least one updated device configuration parameter corresponding to at least one updated feature to be tested on the portable device; and

de-authorizing the portable device when the updated configuration file is received.

11. The method of claim 10, further comprising:

performing a test that determines whether the at least one device configuration parameter respectively corresponding to the at least one updated feature to be tested is fulfilled by the portable device; and

authorizing the portable device to communicate with the implantable medical device if the at least one updated feature is fulfilled by the portable device.

12. The method of claim 1, wherein the at least one device configuration parameter comprises a plurality of device configuration parameters, the at least one feature comprises a plurality of features, and the portable device is authorized to communicate with the implantable medical device only if all of the features are fulfilled by the portable device.

13. A server for facilitating authorization of a portable device to communicate with an implantable medical device, wherein the server comprises:

a memory storing a configuration checking program and a configuration file having at least one device configuration parameter respectively corresponding to at least one feature to be tested on the portable device, wherein the configuration checking program, when executed by the portable device, performs a test that determines whether the at least one device configuration parameter is fulfilled by the portable device, authorizes the portable device to communicate with the implantable medical device only if the at least one feature is fulfilled by the portable device, and denies authorization of the portable device to communicate with the implantable medical device if the at least one feature is not fulfilled by the portable device;

a modem configured for remotely communicating with the portable device; and

a controller configured for receiving a request from the portable device to download the configuration file and the configuration checking program, and for transmitting the configuration file and the configuration checking program to the portable device in response to the request.

14. The server of claim 13, wherein the portable device comprises a personal smart device.

15. The server of claim 13, wherein the feature to be tested on the portable device is one of a storage memory of the portable device, a random access memory of the portable device, a capability of the portable device to connect to a type of a network, a screen height of the portable device, a screen width of the portable device, an operating system of the portable device, a model of the portable device, a type of central processing unit of the portable device, a speed of central processing unit of the portable device, a type of graphic library of the portable device, a USB capability of the portable device, an API level of the portable device, a near field communication capability of the portable device, a Bluetooth®

capability of the portable device, a wireless capability of the portable device, a hardware connectivity performance of the portable device, a type of security capability of the portable device, a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to a remote system.

16. The server of claim 13, wherein the configuration checking program, when executed by the portable device, requests an input from a user, and receives the input from the user, wherein the at least one feature is determined to be fulfilled by the portable device based on the input received from the user.

17. The server of claim 16, wherein the feature to be tested is one of a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to a remote system.

18. The server of claim 13, wherein the configuration checking program, when executed by the portable device, detects a modification in the portable device, and automatically de-authorizes the modified portable device from communicating with the implantable medical device.

19. The server of claim 18, wherein the modification is at least one of an installation of software or firmware, an upgrade of software or firmware, an enablement of a capability, and a disablement of a capability.

20. The server of claim 18, wherein the configuration checking program, when executed by the portable device, performs the test that determines whether the at least one device configuration parameter respectively corresponding to the at least one feature to be tested is fulfilled by the modified portable device, and authorizes the modified portable device to communicate with the implantable medical device if the at least one feature is fulfilled by the modified portable device.

21. The server of claim 13, wherein the memory further stores an updated configuration file having at least one updated device configuration parameter respectively corresponding to at least one updated feature to be tested on the portable device, wherein the configuration checking program, when executed by the portable device, performs a test that determines whether at least one updated device configuration parameter is fulfilled by the portable device, authorizes the portable device to communicate with the implantable medical device only if the at least one updated feature is fulfilled by the portable device, and denies authorization of the portable device to communicate with the implantable medical device if the at least one updated feature is not fulfilled by the portable device, and

wherein the controller is further configured for receiving a request from the portable device to download the updated configuration file, and for transmitting the updated configuration file to the portable device in response to the request.

22. The server of claim 21, wherein the configuration checking program, when executed by the portable device, de-authorizes the portable device from communicating with the implantable medical device prior to performing the test that determines whether at least one updated feature to be tested is fulfilled on the portable device.

23. The server of claim 13,

wherein the configuration checking program is an application program that, when executed by the portable device, provides a graphical user interface that allows the portable device to communicate with the implantable medical device only if the portable device is authorized to communicate with the implantable medical device.

24. The server of claim 13, wherein the at least one device configuration parameter comprises a plurality of device configuration parameters, the at least one feature comprises a plurality of features, and the configuration checking program, when executed by the portable device, authorizes the portable device to communicate with the implantable medical device only if all of the features are fulfilled by the portable device.

25. A portable device in communication with a server, the portable device comprising:

memory configured for storing a configuration checking program and a configuration file having at least one device configuration parameter respectively corresponding to at least one feature to be tested on the portable device, wherein the configuration checking program, when executed, performs a test that determines whether the at least one device configuration parameter is fulfilled by the portable device, authorizes the portable device to communicate with an implantable medical device only if the at least one feature is fulfilled by the portable device, and denies authorization of the portable device to communicate with the implantable medical device if the at least one feature is not fulfilled by the portable device;

a modem configured for remotely communicating with the server; and

a controller configured for sending a request to the server to download the configuration file, receiving the configuration file in response to the request, and for executing the configuration checking program.

26. The portable device of claim 25, wherein the portable device comprises a personal smart device containing the memory, the modem, and the controller.

27. The portable device of claim 25, wherein the feature to be tested on the portable device is one of a storage memory of the portable device, a random access memory of the portable device, a capability of the portable device to connect to a type of a network, a screen height of the portable device, a screen width of the portable device, an operating system of the portable device, a model of the portable device, a type of central processing unit of the portable device, a speed of central processing unit of the portable device, a type of graphic library of the portable device, a USB capability of the portable device, an API level of the portable device, a near field communication capability of the portable device, a Bluetooth®

capability of the portable device, a wireless capability of the portable device, a hardware connectivity performance of the portable device, a type of security capability of the portable device, a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to a remote system.

28. The portable device of claim 25, wherein the configuration checking program, upon execution, requests an input from a user, and receives the input from the user, wherein the at least one feature is determined to be fulfilled by the portable device based on the input received from the user.

29. The portable device of claim 28, wherein the feature to be tested is one of a sensitivity of a touchscreen of the portable device, an accuracy of the touchscreen of the portable device, a connectivity of the portable device to a bridge device, and a connectivity of the portable device to the remote system.

30. The portable device of claim 25, wherein the configuration checking program, upon execution, detects a modification in the portable device, and automatically de-authorizes the modified portable device from communicating with the implantable medical device.

31. The portable device of claim 30, wherein the modification is at least one of an installation of software or firmware, an upgrade of software or firmware, an enablement of a capability, and a disablement of a capability.

32. The portable device of claim 30, wherein the configuration checking program, upon execution, performs the test that determines whether the at least one device configuration parameter respectively corresponding to the at least one feature to be tested is fulfilled by the modified portable device, and authorizes the modified portable device to communicate with the implantable medical device if the at least one feature is fulfilled by the modified portable device.

33. The portable device of claim 25, wherein the memory is further configured for storing an updated configuration file having at least one updated device configuration parameter respectively corresponding to at least one updated feature to be tested on the portable device, and the configuration checking program, when executed, performs a test that determines whether the at least one updated device configuration parameter is fulfilled by the portable device, authorizes the portable device to communicate with the implantable medical device only if the at least one updated feature is fulfilled by the portable device, and denies authorization of the portable device to communicate with the implantable medical device if the at least one updated feature is not fulfilled by the portable device, and

wherein the controller is further configured for sending a request from the portable device to download the updated configuration file, and for receiving the updated configuration file in response to the request.

34. The portable device of claim 33, wherein the configuration checking program, when executed, de-authorizes the portable device from communicating with the implantable medical device prior to performing the test that determines whether at least one updated feature to be tested is fulfilled on the portable device.

35. The portable device of claim 25,

wherein the configuration checking program is an application program that, when executed, provides a graphical user interface that allows the portable device to communicate with the implantable medical device.

36. The portable device of claim 25, wherein the at least one device configuration parameter comprises a plurality of device configuration parameters, the at least one feature comprises a plurality of features, and the configuration checking program, when executed, authorizes the portable device to communicate with the implantable medical device only if all of the features are fulfilled by the portable device.