Method and system for updating a medical device

• US 9,940,436 B2
• Filed: 07/20/2015
• Issued: 04/10/2018
• Est. Priority Date: 06/04/2009
• Status: Active Grant

• Current Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories)
• Original Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories)
• Inventors: Nekoomaram, Saeed, Crouther, Nathan C.
• Primary Examiner(s): Chung, Phung M
• Application Number:
  US14/804,244
• Publication Number:
  US 20150339116A1
• Time in Patent Office: 995 Days
• CPC Class Codes: G06F 11/1004 to protect a block of data words, e.g. CRC or checksum G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G08B 21/182 Level alarms, e.g. alarms responsive to variables exceeding a threshold
• CPC Class Codes: G08B 29/24 Self-calibration, e.g. compensating for environmental drift or ageing of components
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: H03M 13/09 Error detection only, e.g. using cyclic redundancy check [CRC] codes or single parity bit
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 12/106 Packet or message integrity
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning

Abstract

The present disclosure includes methods, devices and systems for determining the availability of an upgraded version of executable code for a medical device and installing the executable code on the medical device. In some embodiments, methods, devices and systems are also provided for detecting a failure of a critical component of the executable code and disabling a functionality of the medical device relating thereto.

Claims

1. A method, comprising:

determining, by the server, availability of an upgraded version of executable code for a medical device;

detecting a communication connection between the server and a computing device;

transmitting the upgraded version of the executable code from the server to the computing device;

detecting a data communication connection to the medical device at the computing device;

transmitting a current version of persistent data from the medical device to the server over the data communication connection with the computing device, wherein the current version of persistent data comprises manufacturing data and user-configurable data associated with a current version of the executable code on the medical device;

converting the current version of persistent data to an upgraded version of persistent data;

receiving the upgraded version of the executable code and the upgraded version of persistent data at the medical device from the computing device;

automatically initiating installation of the upgraded version of the executable code at the medical device; and

in response to successfully installing the upgraded version of the executable code, executing the upgraded version of the executable code at the medical device with reference to the upgraded version of persistent data.

2. The method of claim 1, further comprising:

detecting a failure of a critical component of the upgraded version of the executable code, and

in response to detecting the failure of the critical component of the upgraded version of the executable code, disabling a functionality of the medical device related to the critical component of the upgraded version of the executable code.

3. The method of claim 1, further comprising verifying an integrity of the upgraded version of the executable code prior to executing the upgraded version of the executable code.

4. The method of claim 3, wherein the integrity of the upgraded version of the executable code is verified using a cyclic redundancy check (CRC).

5. The method of claim 3, wherein the integrity of the upgraded version of the executable code is verified at the medical device.

6. The method of claim 5, wherein verifying the integrity of the upgraded version of the executable code includes generating a CRC code and comparing the generated CRC code to a received CRC code associated with the upgraded version of the executable code.

7. The method of claim 6, wherein generating the CRC code and comparing the generated CRC code to the received CRC code associated with the upgraded version of the executable code is performed by the medical device.

8. The method of claim 6, wherein the integrity of the upgraded version of the executable code is verified when the generated CRC code matches the received CRC code.

9. The method of claim 3, wherein the integrity of the upgraded version of the executable code is verified using one of parity bits, a checksum, or a cryptographic hash function.

10. The method of claim 1, wherein the medical device includes an analyte monitoring device.

11. A system, comprising:

a computing device for data communication over a data connection with a medical device; and

a server configured to determine availability of an upgraded version of executable code for the medical device;

wherein the medical device comprises;

one or more processors of the medical device; and

a memory of the medical device that stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to cause transmission of a current version of persistent data to the server over the data connection with the computing device, to store the upgraded version of the executable code and an upgraded version of the persistent data received from the computing device, to automatically initiate installation of the upgraded version of the executable code, and in response to successful installation of the upgraded version of the executable code, to execute the upgraded version of the executable code with reference to the upgraded version of persistent data, wherein the current version of persistent data comprises manufacturing data and user-configurable data associated with a current version of the executable code on the medical device, and

wherein the server comprises;

one or more processors of the server; and

a memory of the server that stores instructions which, when executed by the one or more processors of the server, causes the one or more processors of the server to convert the current version of persistent data to the upgraded version of persistent data, and to cause transmission of the upgraded version of the executable code and the upgraded version of the persistent data to the medical device via the computing device when the server is in data communication with the computing device.

12. The system of claim 11, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to detect a failure of a critical component of the upgraded version of the executable code, and in response to detection of the failure of the critical component of the upgraded version of the executable code, to disable a functionality related to the critical component of the upgraded version of the executable code.

13. The system of claim 11, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to verify an integrity of the upgraded version of the executable code and the upgraded version of the persistent data prior to executing the upgraded version of the executable code.

14. The system of claim 13, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to, prior to executing the upgraded version of the executable code, verify (a) an integrity of the upgraded version of the executable code using one of parity bits, a checksum, or a cryptographic hash function and (b) the upgraded version of the persistent data.

15. The system of claim 11, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to, prior to executing the upgraded version of the executable code, verify an integrity of the upgraded version of the executable code, using a cyclic redundancy check (CRC), and to verify the upgraded version of the persistent data.

16. The system of claim 11, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to verify an integrity of the upgraded version of the executable code.

17. The system of claim 16, wherein the memory of the medical device stores instructions which, when executed by the one or more processors of the medical device, causes the one or more processors of the medical device to generate a cyclic redundancy check (CRC) code, to compare the generated CRC code to a received CRC code associated with the upgraded version of the executable code, and to verify the integrity of the upgraded version of the executable code if the generated CRC code matches the received CRC code.