Method and system for updating a medical device

• US 8,726,266 B2
• Filed: 05/23/2011
• Issued: 05/13/2014
• Est. Priority Date: 05/24/2010
• Status: Expired due to Fees

• 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:
  US13/114,020
• Publication Number:
  US 20110289497A1
• Time in Patent Office: 1,086 Days
• Field of Search: 717168-178, 600/319, 600/316, 600/347, 600/365
• US Class Current: 717/171
• 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 of using a device history log of a medical device, comprising:

running a first version of data and/or program on the medical device;

detecting an operable coupling of the medical device with a peripheral device and receiving identification data of the peripheral device at the medical device;

upon detecting the operable coupling, running a second version of data and/or program on the medical device, the second version being different from the first version;

determining if the medical device is configured to support the peripheral device by comparing the identification data of the peripheral device to the device history log stored in 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, uploading support data and/or program to the medical device to support 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 from the medical device to the operably coupled peripheral device, the data management program having a version;

comparing the version of the uploaded data management program from the medical device against a most current version of the data management program on a network and if a more current version exists on the network, uploading the more current version from the network to the peripheral device and running the more current version by the peripheral device.

2. The method of claim 1 further comprising the step of automatically reverting from running the second version of data and/or program to running the first version of data and/or program upon disconnection of the peripheral device from the medical device.

3. A method of updating a peripheral device configuration, comprising:

running a first version of data and/or program on the medical device;

detecting an operable coupling of a peripheral device to the medical device, the medical device being configured to provide medical data;

upon detecting the operable coupling, running a second version of data and/or program on the medical device, the second version being different from the first version;

automatically reverting from running the second version of data and/or program to running the first version of data and/or program upon disconnection of the peripheral device from the medical device;

receiving identification data of the peripheral device in the medical device at the operable coupling;

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 memory of the medical device;

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

if the identification data of the peripheral device operably connected to the medical device is not found in the device history log, uploading support data and/or program to the medical device to support the peripheral device, and storing identification data of the peripheral device in the 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 from the operably-connected medical device to the peripheral device; and

comparing a version of the uploaded data management program from the medical device against a most current version of the data management program on a network and if a more current version exists on the network, uploading the more current version from the network to the peripheral device and running the more current version by the peripheral device.

4. The method of claim 3 further comprising updating the device history log for the medical device at a manufacturing site of the medical device based on modifications to the medical device.

5. The method of claim 4 further comprising communicating modifications made to the medical device to a remote location including the manufacturing site of the medical device, the communicating including one or more of a wired or a wireless communication between the medical device and the remote location.

6. A system including a device history log, comprising:

a medical device configured to provide medical data;

a memory located in the medical device, the memory having a data management program having a version;

a medical device processor located in the medical device, the medical device processor programmed to run a first version of data and/or program on the medical device; and

a peripheral device configured to operably couple to the medical device, the peripheral device having identification data;

wherein the medical device processor is programmed to run a second version of data and/or program on the medical device upon detecting the operable coupling, the second version being different from the first version, and to communicate with the peripheral device when the medical device and peripheral device are operably coupled to determine if the peripheral device has a data management program suitable to manage the medical data provided by the medical device;

wherein the medical device processor is further programmed to automatically revert from running the second version of data and/or program to running the first version of data and/or program upon disconnection of the peripheral device from the medical device;

wherein the medical device processor is further programmed to upload the data management program from the medical device to the peripheral device if the peripheral device does not include a suitable data management program;

wherein the peripheral device is configured to run the data management program uploaded by the medical device;

wherein the medical device processor is further programmed to receive the identification data from the peripheral device and determine if the medical device is configured to support the peripheral device by comparing the identification data received from the peripheral device to a device history log stored in the medical device memory;

if the identification data of the peripheral device is found in the device history log, the medical device processor is programmed to proceed with support of the peripheral device; and

if the identification data of the peripheral device is not found in the device history log, upload support data and/or program to the medical device to support the peripheral device, and store identification data of the peripheral device in the device history log.

7. The system of claim 6 wherein the data management program uploaded by the medical device is configured to program the peripheral device to compare the version of the uploaded data management program from the medical device against a most current version of a data management program on a network and if a more current version exists on the network, to upload the more current version from the network to the peripheral device to run the more current version by the peripheral device to manage the data from the medical device.

8. A medical device system, comprising:

a medical device configured to provide medical data, comprising;

a microprocessor; and

a memory having a data management program having a version and a device history log;

a peripheral device configured to operably couple to the medical device, the peripheral device having identification data;

wherein the medical device microprocessor is programmed to run a first version of data and/or program on the medical device until the peripheral device is operably coupled to the medical device following which the medical microprocessor is programmed to run a second version of data and/or program on the medical device, the second version being different from the first version, and to automatically revert from running the second version of data and/or program to running the first version of data and/or program upon disconnection of the peripheral device from the medical device;

wherein the medical device microprocessor is further programmed to communicate with the peripheral device when the medical device and peripheral device are operably coupled to determine if the peripheral device has a data management program suitable to manage the medical data provided by the medical device;

wherein the medical device microprocessor is further programmed to upload the data management program from the medical device to the peripheral device if the peripheral device does not include a suitable data management program;

wherein the peripheral device is configured to run the data management program uploaded by the medical device;

wherein the medical device microprocessor is further programmed to receive the identification data from the peripheral device and determine if the medical device is configured to support the peripheral device by comparing the identification data received from the peripheral device to the device history log stored in the medical device memory;

if the identification data of the peripheral device is found in the device history log, the medical device processor is programmed to proceed with support of the peripheral device; and

if the identification data of the peripheral device is not found in the device history log, upload support data and/or program to the medical device to support the peripheral device and store identification data of the peripheral device in the device history log.