Method and system for updating a medical device

• US 8,595,607 B2
• Filed: 06/04/2010
• Issued: 11/26/2013
• Est. Priority Date: 06/04/2009
• Status: Active Grant

• Current Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Original Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Inventors: Nekoomaram, Saeed, Crouther, Nathan Christopher
• Primary Examiner(s): Chung, Phung M
• Application Number:
  US12/794,721
• Publication Number:
  US 20100313105A1
• Time in Patent Office: 1,271 Days
• Field of Search: 714/708, 714/758, 714/710, 714/701, 714/799, 717/171, 709/221
• US Class Current: 714/807
• 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 establishing a connection between a medical device and a remote computing device, receiving an upgrade command at the medical device, storing a current version of persistent data and a current version of executable code in a first storage area of the medical device, transmitting at least the current version of the persistent data to the remote computing device, receiving a second format of the current version of the persistent data and an upgraded version of executable code at the medical device, storing the second format of the current version of the persistent data and the upgraded version of the executable code in a second storage area of the medical device, and executing the upgraded version of the executable code with the second format of the current version of the persistent data.

Claims

1. A method comprising:

establishing a connection between a medical device and a remote computing device;

receiving an upgrade command at the medical device;

storing a current version of persistent data and a current version of executable code in a first storage area of the medical device;

transmitting at least the current version of the persistent data to the remote computing device, wherein the remote computing device is configured to convert the current version of the persistent data from a first format to a second format;

receiving the second format of the current version of the persistent data and an upgraded version of executable code at the medical device;

storing the second format of the current version of the persistent data and the upgraded version of the executable code in a second storage area of the medical device;

executing the upgraded version of the executable code with the second format of the current version of the persistent data;

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

disabling the functionality of the medical device related to the critical component of the upgraded version of the executable code when the failure is detected.

2. The method of claim 1, further comprising verifying an integrity of the upgraded version of the executable code and the second format of the current version of the persistent data prior to executing the upgraded version of the executable code.

3. The method of claim 2, wherein the integrity of the upgraded version of the executable code and the second format of the current version of the persistent data is verified using a cyclic redundancy check.

4. The method of claim 1, wherein converting the current version of the persistent data from the first format to the second format includes modifying a layout of the data associated with the current version of the persistent data.

5. The method of claim 1, further comprising copying the upgraded executable code and the second format of the current version of the persistent data from the second storage area to the first storage area.

6. The method of claim 1, wherein the current version of the persistent data is one or more of user-configurable data or manufacturing data.

7. The method of claim 1, further comprising executing the current version of executable code with the current version of the persistent data when an error associated with a non-critical component of the upgraded version of the executable code or the second format of the current version of the persistent data is detected.

51. The method of claim 1, wherein the critical component of the upgraded version of the executable code is related to a bolus calculation function of the medical device or a bolus delivery function of a peripheral pump operatively connected to the medical device.

8. An apparatus, comprising:

one or more processors; and

a memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to establish a connection to a remote computing device, receive an upgrade command, store a current version of persistent data and a current version of executable code in a first storage area of the memory, transmit at least the current version of the persistent data to the remote computing device, wherein the remote computing device is configured to convert the current version of the persistent data from a first format to a second format, receive the second format of the current version of the persistent data and an upgraded version of executable code, store the second format of the current version of the persistent data and the upgraded version of the executable code in a second storage area of the memory, execute the upgraded version of the executable code with the second format of the current version of the persistent data, detect a failure of a critical component of the upgraded version of the executable code, and disable a functionality of the apparatus related to the critical component of the upgraded version of the executable code when the failure is detected.

9. The apparatus of claim 8, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to verify an integrity of the upgraded version of the executable code and the second format of the current version of the persistent data prior to executing the upgraded version of the executable code.

10. The apparatus of claim 9, wherein the integrity of the upgraded version of the executable code and the second format of the current version of the persistent data is verified using a cyclic redundancy check.

11. The apparatus of claim 8, wherein converting the current version of the persistent data from the first format to the second format includes modifying a layout of the data associated with the current version of the persistent data.

12. The apparatus of claim 8, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to copy the upgraded version of the executable code and the second format of the current version of the persistent data from the second storage area to the first storage area.

13. The apparatus of claim 8, wherein the current version of the persistent data is one or more of user-configurable data or manufacturing data.

14. The apparatus of claim 8, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to execute the current version of executable code with the current version of the persistent data when an error associated with a non-critical component of the upgraded version of the executable code or the second format of the current version of the persistent data is detected.

52. The apparatus of claim 8, wherein the critical component of the upgraded version of the executable code is related to a bolus calculation function of the apparatus or a bolus delivery function of a peripheral pump operatively connected to the apparatus.

15. A method comprising:

establishing a connection between a first medical device and a remote computing device;

storing user-configurable data associated with the first medical device on the remote computing device;

establishing a connection between a second medical device and the remote computing device;

converting the user-configurable data associated with the first medical device from a first format to a second format, wherein the second format of the user-configurable data corresponds to the second medical device; and

transmitting the second format of the user-configurable data to the second medical device, wherein the second format of the user-configurable data is configured to alter at least one setting of the second medical device;

wherein the first medical device is a blood glucose monitoring device and the second medical device is a continuous glucose monitoring device.

16. The method of claim 15, wherein converting the user-configurable data associated with the first medical device from the first format to the second format includes changing a layout of the user-configurable data.

17. The method of claim 16, wherein changing the layout of the user-configurable data includes altering a number of bits of each data element associated with the user-configurable data.

18. The method of claim 15, further comprising, verifying an integrity of the second format of the user-configurable data prior to altering at least one setting of the second medical device based on the second format of the user-configurable data.

19. The method of claim 18, wherein the integrity of the second format of the user-configurable data is verified using a cyclic redundancy check.

20. A system, comprising:

a remote computing device;

a first medical device in signal communication with the remote computing device; and

a second medical device in signal communication with the remote computing device;

wherein the remote computing device is configured to;

store user-configurable data associated with the first medical device;

convert the user-configurable data associated with the first medical device from a first format to a second format, wherein the second format of the user-configurable data corresponds to the second medical device; and

transmit the second format of the user-configurable data to the second medical device, wherein the second format of the user-configurable data is configured to alter at least one setting of the second medical device;

wherein the first medical device is a blood glucose monitoring device and the second medical device is a continuous glucose monitoring device.

21. The system of claim 20, wherein converting the user-configurable data associated with the first medical device from the first format to the second format includes changing a layout of the user-configurable data.

22. The system of claim 21, wherein changing the layout of the user-configurable data includes altering a number of bits of each data element associated with the user-configurable data.

23. The system of claim 20, wherein the second medical device is configured to verify an integrity of the second format of the user-configurable data prior to altering at least one setting based on the second format of the user-configurable data.

24. The system of claim 21, wherein the integrity of the second format of the user-configurable data is verified using a cyclic redundancy check.

25. A method comprising:

establishing a connection between a medical device and a remote computing device;

identifying the medical device;

comparing a current version of software of the medical device with one or more available versions of software for the identified medical device using a compatibility table, wherein the compatibility table is associated with the identified medical device; and

transmitting an available version of the software for the identified medical device to the identified medical device;

wherein the transmitted available version of the software for the identified medical device includes a bolus calculation function of the identified medical device or a bolus delivery function of a peripheral pump operatively connected to the identified medical device.

26. The method of claim 25, further comprising selectively transmitting a plurality of the available versions of software to the identified medical device based on the compatibility table.

27. The method of claim 25, wherein the available one or more versions of software for the identified medical device includes software for one or more processors of the identified medical device.

28. The method of claim 25, wherein the available one or more versions of software for the identified medical device includes firmware for one or more processors of the identified medical device.

29. The method of claim 25, wherein the available one or more versions of software for the identified medical device are based, at least in part, on a hardware version of at least one component of the identified medical device.

30. The method of claim 29, wherein the hardware version of the at least one component of the identified medical device is stored in the compatibility table.

31. The method of claim 25, wherein the medical device is identified by a serial number of the medical device.

32. An apparatus, comprising:

one or more processors; and

a memory for storing instructions which when executed by the one or more processors, causes the one or more processors to establish a connection to a medical device, identify the medical device, compare a current version of software of the identified medical device with one or more available versions of software for the medical device using a compatibility table, wherein the compatibility table is associated with the identified medical device, and transmit an available version of the software for the identified medical device to the identified medical device, wherein the transmitted available version of the software for the identified medical device includes a bolus calculation function of the identified medical device or a bolus delivery function of a peripheral pump operatively connected to the identified medical device.

33. The apparatus of claim 32, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to selectively transmit a plurality of available versions of software to the identified medical device based on the compatibility table.

34. The apparatus of claim 32, wherein the one or more available versions of software for the identified medical device includes software for the one or more processors of the identified medical device.

35. The apparatus of claim 32, wherein the one or more available versions of software for the identified medical device includes firmware for the one or more processors of the identified medical device.

36. The apparatus of claim 32, wherein the available one or more versions of software for the identified medical device are based, at least in part, on a hardware version of at least one component of the identified medical device.

37. The apparatus of claim 36, wherein the hardware version of the at least one component of the identified medical device is stored in the compatibility table.

38. The apparatus of claim 32, wherein the medical device is identified by a serial number of the medical device.

39. A method comprising:

establishing a connection between a medical device and a remote computing device;

identifying the medical device;

receiving a request for data corresponding to at least one of a version of persistent data for the medical device or a version of executable code for the medical device;

identifying the requested data based at least in part on a compatibility table; and

transmitting the identified data corresponding to the at least one of the version of persistent data for the medical device or the version of executable code for the medical device;

wherein the transmitted identified data corresponding to the at least one of the version of persistent data for the medical device or the version of executable code for the medical device includes a bolus calculation function of the medical device or a bolus delivery function of a peripheral pump operatively connected to the medical device.

40. The method of claim 39, wherein the medical device is identified by a serial number of the medical device.

41. The method of claim 40, wherein the compatibility table is identified based on the serial number of the medical device.

42. The method of claim 39, wherein the version of the persistent data corresponds to at least one of user-selectable data or manufacturing data.

43. The method of claim 39, wherein the version of the persistent data is configured to replace persistent data stored on the medical device.

44. The method of claim 39, wherein the version of the executable code for the medical device is configured to replace executable code stored on the medical device.

45. An apparatus, comprising:

one or more processors; and

a memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to establish a connection between a medical device and a remote computing device, identify the medical device, receive a request for data corresponding to at least one of a version of persistent data for the medical device or a version of executable code for the medical device, identify the requested data based at least in part on a compatibility table, and transmit the identified data corresponding to the at least one of the version of persistent data for the medical device or the version of executable code for the medical device, wherein the transmitted identified data corresponding to the at least one of the version of persistent data for the medical device or the version of executable code for the medical device includes a bolus calculation function of the medical device or a bolus delivery function of a peripheral pump operatively connected to the medical device.

46. The apparatus of claim 45, wherein the medical device is identified by a serial number of the medical device.

47. The apparatus of claim 46, wherein the compatibility table is identified based on the serial number of the medical device.

48. The apparatus of claim 45, wherein the version of the persistent data corresponds to at least one of user-selectable data or manufacturing data.

49. The apparatus of claim 45, wherein the version of the persistent data is configured to replace persistent data stored on the medical device.

50. The apparatus of claim 45, wherein the version of the executable code for the medical device is configured to replace executable code stored on the medical device.