Systems and methods for updating a medical device

Patent metadata

Field	Value
Publication number	US-9501272-B2
Application number	US-201414529535-A
Country	US
Kind code	B2
Filing date	Oct 31, 2014
Priority date	May 24, 2010
Publication date	Nov 22, 2016
Grant date	Nov 22, 2016

Abstract

Embodiments described herein include methods and/or systems for updating a medical device. Embodiments include medical devices which are configured for updates in response to various events including connection of a peripheral device to the medical device, a user initiated event, or based on received recommendations.

First claim

What is claimed is:

1. A method of updating a medical device configuration, comprising:
receiving, at a medical device, an upgrade command from a remote computing device, wherein the medical device is operating with a current executable code;
uploading data from the medical device to the remote computing device;
converting the uploaded data to be utilized by an upgraded software code;
downloading the upgraded software code and converted data to the medical device, wherein, as downloaded, the upgraded software code and converted data comprise at least one block of data, and wherein a first cyclic redundancy check (CRC) code is downloaded to the medical device for the at least one block of data;
generating, by the medical device, a second CRC code for the at least one downloaded block of data;
comparing, by the medical device, the first CRC code with the second CRC code;
performing a verification, by the medical device, of the downloaded upgraded software code and converted data, wherein the verification is successful if the first and second CRC codes match and, if the first and second CRC codes do not match, an error is detected and the verification fails;
if the verification fails, then continuing medical device operation with the current executable code;
if the verification is successful, then attempting, by the medical device, to execute the upgraded software code; and
if the upgraded software code fails to execute, then reverting, by the medical device, to operating with the current executable code.

2. The method of claim 1 , wherein uploading the data includes
packing the data stored in a first memory area of the medical device; and
copying the packed data and current executable code to a second memory area of the medical device.

3. The method of claim 2 , wherein the downloaded software code and converted data are stored in a third memory area of the medical device.

4. The method of claim 2 , wherein the first memory area includes non-user configurable data and the converted data includes updated non-user configurable data.

5. The method of claim 1 , further comprising:
if the verification fails, then deleting the downloaded software code and converted data at the medical device.

6. The method of claim 1 , wherein the upgraded software code includes a critical upgrade and, if the verification fails or the upgraded software code fails to execute, then disabling a feature associated with the critical upgrade.

7. The method of claim 1 , further comprising:
if the verification is successful, then performing a reset by the medical device prior to attempting to execute the upgraded software code.

8. A method of updating a medical device configuration, comprising:
uploading data from a medical device to a remote server;
converting the uploaded data, by the remote server, to be utilized by an upgraded software code;
downloading the upgraded software code and converted data from the remote server to the medical device, wherein, as downloaded, the upgraded software code and converted data comprise at least one block of data, and wherein a first cyclic redundancy check (CRC) code is downloaded to the medical device for the at least one block of data;
generating, by the medical device, a second CRC code for the at least one downloaded block of data;
comparing, by the medical device, the first CRC code with the second CRC code;
performing a verification, by the medical device, of the downloaded upgraded software code and converted data, wherein the verification is successful if the first and second CRC codes match and, if the first and second CRC codes do not match, an error is detected and the verification fails;
if the verification fails, then continuing medical device operation with the current executable code;
if the verification is successful, then attempting, by the medical device, to execute the upgraded software code; and
if the upgraded software code fails to execute, then reverting, by the medical device, to operating with the current executable code.

9. The method of claim 8 , wherein uploading the data includes
packing the data stored in a first memory area of the medical device; and
copying the packed data and current executable code to a second memory area of the medical device.

10. The method of claim 9 , wherein the downloaded software code and converted data are stored in a third memory area of the medical device.

11. The method of claim 9 , wherein the first memory area includes non-user configurable data and the converted data includes updated non-user configurable data.

12. The method of claim 8 , further comprising:
if the verification fails, then deleting the downloaded software code and converted data at the medical device.

13. The method of claim 8 , wherein the upgraded software code includes a critical upgrade and, if the verification fails or the upgraded software code fails to execute, then disabling a feature associated with the critical upgrade.

14. The method of claim 8 , further comprising:
if the verification is successful, then performing a reset by the medical device prior to attempting to execute the upgraded software code.

15. The method of claim 8 , further comprising:
determining, by the medical device, that upgraded software code is available prior to uploading data from the medical device to the remote server.

Assignees

• Abbott Diabetes Care Inc

Inventors

• Kiaie Namvar
• Cole Jean-Pierre

Classifications

• G06F11/1433

  during software upgrading · CPC title

• G06F2201/865

  Monitoring of software · CPC title

• G06F11/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 title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title

• G01N33/48792

  Data management, e.g. communication with processing unit (for in vivo diagnostics A61B5/0002; transmission systems for measured values G08C) · CPC title