Systems and methods for updating a medical device

• US 10,255,055 B2
• Filed: 11/17/2016
• Issued: 04/09/2019
• Est. Priority Date: 05/24/2010
• Status: Active Grant

• Current Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Original Assignee: Abbott Diabetes Care Incorporated (Abbott Laboratories Incorporated)
• Inventors: Kiaie, Namvar, Cole, Jean-Pierre
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US15/354,932
• Publication Number:
  US 20170068533A1
• Time in Patent Office: 873 Days
• Field of Search: 717168-178, 600319, 600316, 600347, 600365
• CPC Class Codes: G01N 33/48792 Data management, e.g. communication with processing unit for in vivo diagnostics A61B5/0002; transmission systems for measured values G08C
• 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 2201/865 Monitoring of software
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

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.

Claims

1. A method, comprising:

detecting, with one or more processors of a medical device, an occurrence of a plurality of events associated with the medical device;

storing the plurality of events associated with the medical device in an event log with a plurality of unique identifiers, wherein each event of the plurality of events associated with the medical device has a corresponding unique identifier in the plurality of unique identifiers;

uploading at least one event of the plurality of events associated with the medical device to a computing device;

analyzing, with the computing device, the uploaded at least one event of the plurality of events to determine trend data associated with the uploaded at least one event of the plurality of events; and

receiving at least one recommendation for the medical device, wherein the at least one recommendation is based, at least in part, on the trend data associated with the uploaded at least one of the plurality of events,

wherein the trend data corresponds to a medication administered to a user of the medical device, an upgrade or an update of software of the medical device, or an activity of the user of the medical device.

2. The method of claim 1, wherein the at least one recommendation corresponds to an offer for a consumable product related to treatment of a condition of the user of the medical device.

3. The method of claim 1, wherein the medical device is an analyte monitoring device.

4. The method of claim 1, further comprising:

determining, by reference to the plurality of unique identifiers, that the at least one of the plurality of events has not been previously uploaded to the computing device prior to uploading the at least one of the plurality of events.

5. The method of claim 1, wherein the trend data corresponds to the medication administered to the user of the medical device.

6. The method of claim 1, wherein the trend data corresponds to the upgrade or update of software of the medical device.

7. The method of claim 1, wherein the trend data corresponds to the activity of the user of the medical device.

8. A method, comprising:

detecting an operable coupling of a medical device with a peripheral device;

receiving identification data of the peripheral device at the medical device;

determining if the medical device is configured to support the peripheral device by comparing the identification data of the peripheral device to a device history log stored in a first non-volatile storage area of a memory of the medical device;

if the identification data of the peripheral device is found in the device history log, proceeding with support of the peripheral device;

if the identification data of the peripheral device is not found in the device history log, upgrading executable code and data of the medical device so that the medical device supports the peripheral device, and storing identification data of the peripheral device in the medical device history log;

determining if the operably coupled peripheral device includes a data management program;

if the operably coupled peripheral device does not include a data management program, uploading a data management program to the operably coupled peripheral device, the data management program having a version; and

running the uploaded data management program on the peripheral device,

wherein upgrading the executable code and data of the medical device comprises;

copying first code and associated first data to a second non-volatile storage area of the memory, wherein the first code and associated first data are current code and associated current data;

downloading new upgraded code; and

upon recovering from a reset, using the new upgraded code, wherein if a failure occurs while using the new upgraded code, reverting to using the first code and associated first data stored in the second non-volatile storage memory area.

9. The method of claim 8, further comprising:

comparing the version of the uploaded data management program from the medical device against a version of a data management program on a network;

if the version of the data management program on the network is more current than the version of the uploaded data management program from the medical device, then uploading the version of the data management program on the network to the peripheral device; and

running the more current version by the peripheral device.

10. The method of claim 8, further comprising:

running a first version of a program on the medical device until the operable coupling of the peripheral device to the medical device is detected; and

then running a second version of the program on the medical device, the second version of the program being different from the first version of the program.