Diabetes Management System

• US 20170203030A1
• Filed: 01/17/2017
• Published: 07/20/2017
• Est. Priority Date: 01/14/2016
• Status: Active Grant

• Current Assignee: Bigfoot Biomedical, Inc.
• Original Assignee: Bigfoot Biomedical, Inc.
• Inventors: Brewer, Jeffrey, Lee, Kevin S.
• Granted Patent: US 10,293,101 B2
• Time in Patent Office: Days
• CPC Class Codes: A61M 2005/14268 with a reusable and a disposable component
• CPC Class Codes: A61M 2205/18 with alarm
• CPC Class Codes: A61M 2205/3303 Using a biosensor
• CPC Class Codes: A61M 2205/3546 Range
• CPC Class Codes: A61M 2205/3553 remote, e.g. between patient's home and doctor's office
• CPC Class Codes: A61M 2205/3561 local, e.g. within room or hospital
• CPC Class Codes: A61M 2205/3569 sublocal, e.g. between console and disposable
• CPC Class Codes: A61M 2205/3584 using modem, internet or bluetooth
• CPC Class Codes: A61M 2205/502 User interfaces, e.g. screens or keyboards
• CPC Class Codes: A61M 2205/52 with memories providing a history of measured variating parameters of apparatus or patient
• CPC Class Codes: A61M 2205/8206 battery-operated
• CPC Class Codes: A61M 5/142 Pressure infusion, e.g. using pumps
• CPC Class Codes: A61M 5/14244 adapted to be carried by the patient, e.g. portable on the body
• CPC Class Codes: A61M 5/1723 using feedback of body parameters, e.g. blood-sugar, pressure measurement of body parameters A61B5/00
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/20 for computer-aided diagnosis, e.g. based on medical expert systems
• CPC Class Codes: G16H 50/50 for simulation or modelling of medical disorders

Abstract

A variety of location-based and/or proximity-based features related to diabetes management systems can be used to improve maintenance compliance and/or to provide important information to PWD designated assistance entities (e.g., family, friends, givers, HCPs, emergency medicine providers) under certain conditions. In some cases, a user'"'"'s location can be tracked or determined to trigger and/or time alerts about upcoming maintenance tasks in a way that will increase the likelihood that the PWD will immediately perform the designated maintenance task. In some cases, methods, devices, and systems provided herein can use proximity to non-paired mobile computing devices to deliver data to PWD designated assistance entities.

Claims

1. A diabetes management system comprising:

one or more of a continuous glucose monitor and an insulin delivery device; and

a mobile controller device in wireless communication with the continuous glucose monitor, the insulin delivery device, or a combination thereof, the mobile controller device being adapted to (a) to receive blood glucose levels for a user from the continuous glucose monitor or (b) receive insulin delivery data from the insulin delivery device, and wherein the insulin delivery device is adapted to output maintenance reminders to the user based, at least in part, on location information, the mobile controller device comprising;

a location subsystem to detect a location of the mobile controller device, the continuous glucose monitor, the insulin delivery device, or a combination thereof,

a maintenance model that models the user'"'"'s behavior with regard to maintenance reminders based, at least, on locations and context for the diabetes management system when the maintenance reminders are presented to the user,

a maintenance subsystem (i) to continually update the maintenance model by (a) detecting or receiving indications that the user has conducted maintenance tasks on the diabetes management system and (b) updating the maintenance model based on the conducted maintenance tasks, and (ii) to continually provide maintenance reminders at optimal times for upcoming maintenance tasks by (a) obtaining a current location from the location subsystem, (b) determining a current context for the diabetes management system, and (c) identifying the optimal times and providing upcoming maintenance reminders for the upcoming maintenance tasks at the optimal times based on evaluation of the current context and the current location using the maintenance model.

2. The diabetes management system of claim 1, wherein the upcoming maintenance task is selected from the group consisting of recharging a continuous glucose monitor or an insulin delivery device, changing the sensor of a continuous glucose monitor, changing the infusion set of an insulin delivery device, changing the infusion location of an insulin delivery device, changing a sensor location for a continuous glucose monitor, refilling insulin into an insulin delivery device, changing an insulin containing cartridge in an insulin delivery device, replacing a battery in an insulin delivery device, or a combination thereof.

3. The diabetes management system of claim 1, wherein:

the mobile controller device is a mobile computing device adapted to connect to a Wi-Fi system, and

the location subsystem detects the location of the mobile computing device based on available Wi-Fi systems at the location.

4. The diabetes management system of claim 1, wherein:

the mobile controller device is a mobile computing device, and

the location subsystem detects the location of the mobile computing device using a global positioning system (GPS).

5. The diabetes management system of claim 1, wherein:

the maintenance subsystem receives maintenance information from one or more of the insulin delivery device and the continuous glucose monitor about the conducted maintenance tasks and, in response to receiving the maintenance information, obtains (i) locations of the mobile controller device where the conducted maintenance tasks were performed and (ii) contexts of the diabetes management system when the conducted maintenance tasks were performed, and

the maintenance model is updated based on combinations of (i) the conducted maintenance tasks, (ii) the locations where the conducted maintenance tasks were performed, and (iii) the contexts when the conducted maintenance tasks were performed.

6. The diabetes management system of claim 5, wherein the contexts when each of the conducted maintenance tasks were performed include, at least, a time of day when each of the conducted maintenance tasks were performed.

7. The diabetes management system of claim 6, wherein the contexts when each of the conducted maintenance tasks were performed further include, at least, a day of the week when each of the conducted maintenance tasks were performed.

8. The diabetes management system of claim 1, wherein:

for a particular upcoming maintenance task, the maintenance subsystem begins monitoring for an optimal time to provide a particular maintenance reminder for the particular upcoming maintenance task upon a determination that the particular upcoming maintenance task is due within a threshold first period of time,

the monitoring includes repeatedly obtaining the current location, determining the current context, and identifying the optimal time to provide the particular maintenance reminder, and

the monitoring for the particular upcoming maintenance task is not performed before the particular upcoming maintenance task is due within the threshold first period of time.

9. The diabetes management system of claim 8, wherein the maintenance subsystem automatically provides the particular maintenance reminder regardless of the current location and the current context when the particular maintenance task is due within a threshold second period of time that is less than the first period of time.

10. The diabetes management system of claim 1, wherein:

the continually updating of the maintenance model includes the maintenance system (i) determining a particular location where the user conducts a majority of maintenance tasks, (ii) tracking the timing of a diurnal pattern of maintenance tasks at the particular location, and (iii) incorporating a diurnal period of time when the user is likely to conduct maintenance tasks representing the diurnal pattern of maintenance tasks into the maintenance model, and

the continually providing maintenance reminders includes providing the maintenance reminders during the diurnal period of time prior to the scheduled time for the maintenance tasks when the user is at the particular location where the user conducts the majority of the maintenance tasks.

11. The diabetes management system of claim 10, wherein the maintenance reminders are held until the user arrives at the particular location where the user conducts the majority of maintenance tasks when the user is not at the particular location during the diurnal period of time when the user conducts most maintenance tasks.

12. The diabetes management system of claim 11, wherein the maintenance reminders are displayed at particular times when the maintenance tasks are scheduled regardless of whether the user is at the particular location where the user conducts a majority of maintenance tasks.

13. A wearable insulin delivery device comprising:

an insulin pump device to administer insulin dosages to a patient wearing the insulin delivery device;

one or more sensor interfaces to obtain, at least, blood glucose levels for the patient;

a wireless interface to wirelessly communicate with one or more other computing;

a data storage device to store a uniform resource locator (URL) for a remote server system and a unique identifier for the patient;

an input subsystem to receive input from the patient;

an output subsystem to output information to the patient; and

a controller (i) to control the insulin pump device delivering insulin to the patient based, at least in part, on the blood glucose levels received through the one or more sensor interfaces, (ii) to securely communicate with a paired mobile computing device that is authorized to communicate with the remote server system regarding the patient, (iii) to automatically output an alarm via the output subsystem in response to an alarm condition, and (iv) to transmit a wireless beacon signal using the wireless interface in response to the patient failing to provide a response via the input subsystem within a threshold period of time of the alert being output,

wherein the beacon signal (i) includes, at least, the URL encoded with the unique identifier for the patient and (ii) is configured to prompt a third party computing device passively monitoring for beacon signals to transmit a request to the remote server system using the encoded URL.

14. The insulin delivery device of claim 13, wherein:

the wireless interface comprises a BLUETOOTH wireless interface, and

the beacon signal is transmitted as a BLUETOOTH low energy (BLE) beacon signal with the encoded URL in a payload of the BLE beacon signal.

15. The insulin delivery device of claim 13, wherein:

the unique identifier for the patient is encoded in either a path of the URL or as a parameter appended to the URL, and

receipt of the encoded URL prompts the remote server system (i) to automatically determine one or more possible locations where the patient is currently located and (ii) to contact one or more of emergency personnel and authorized patient contacts as to the one or more possible locations where the patient is currently located.

16. The insulin delivery device of claim 13, wherein:

the data storage device further stores health status information for the patient related to management of the patient'"'"'s diabetes,

the URL is further encoded with the health status information for the patient.

17. The insulin delivery device of claim 13, wherein:

the data storage device further location information for the patient communicated from the paired mobile computing device,

the URL is further encoded with the location information for the patient.

18. A diabetes management system comprising:

a paired mobile computing device that is registered with a remote server system in association with a patient;

one or more other computing devices that are registered with the remote server system in association with one or more other patients, wherein the one or more other computing devices are (i) preauthorized by the patient to receive and present health-related information for to the patient, and (ii) to passively monitor for the health-related information transmitted over one or more local wireless protocols; and

a insulin delivery device comprising;

an insulin pump device to administer insulin dosages to the patient;

one or more sensor interfaces to obtain, at least, blood glucose levels for the patient;

a wireless interface to wirelessly communicate with the paired mobile computing device and the one or more other computing devices;

a data storage device to store (i) a unique identifier for the patient, (ii) authentication information to pair and securely communicate with the paired mobile computing device, and (iii) encryption information to securely broadcast the health-related information to the one or more other computing devices; and

a controller (i) to control the insulin pump device delivering insulin to the patient based, at least in part, on the blood glucose levels received through the one or more sensor interfaces, (ii) to securely communicate with the paired mobile computing device, and (iii) to broadcast secure wireless signals including the health-related information for detection and presentation by the one or more other computing devices in response to detecting no connectivity with the paired mobile computing device.

19. The diabetes management system of claim 18, wherein the one or more other computing devices are each programmed (i) to request authentication from the patient before presenting the health-related information that has been transmitted by the insulin delivery device and detected by the one or more other computing devices, (ii) to receive input from the patient, (iii) to verify the input with the remote server system, and (iv) to output the health-related information in response to the input being verified with the remote server system.

20. The diabetes management system of claim 18, wherein:

the wireless interface comprises a BLUETOOTH wireless interface, and

the broadcast secure wireless signals are transmitted as a BLUETOOTH low energy (BLE) beacon signal using one or more secure transmission protocols.