SYSTEMS AND METHODS FOR DISTRIBUTING CONTINUOUS GLUCOSE DATA

• US 20160232318A1
• Filed: 02/09/2016
• Published: 08/11/2016
• Est. Priority Date: 02/10/2015
• Status: Active Grant

• Current Assignee: DexCom Incorporated
• Original Assignee: DexCom Incorporated
• Inventors: Mensinger, Michael Robert, Cabrera, Esteban Jr., Cohen, Eric, Heintzman, Nathaniel David, Kamath, Apurv Ullas, Morris, Gary A., Pal, Andrew Attila, Reihman, Eli, Valdes, Jorge
• Granted Patent: US 10,945,600 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61B 5/0004 characterised by the type of physiological signal transmitted
• CPC Class Codes: A61B 5/0022 Monitoring a patient using a global network, e.g. telephone networks, internet
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61B 5/7275 Determining trends in physiological measurement data; Predicting development of a medical condition based on physiological measurements, e.g. determining a risk factor
• CPC Class Codes: A61B 5/742 using visual displays A61B5/339 takes precedence
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 50/30 for calculating health indices; for individual health risk assessment

Abstract

The present disclosure relates to systems, devices and methods for receiving biosensor data acquired by a medical device, e.g., relating to glucose concentration values, and controlling the access and distribution of that data. In some embodiments, systems and methods are disclosed for monitoring glucose levels, displaying data relating to glucose values and metabolic health information, and controlling distribution of glucose data between applications executing on a computer, such as a smart phone. In some embodiments, systems and methods are disclosed for controlling access to medical data such as continuously monitored glucose levels, synchronizing health data relating to glucose levels between multiple applications executing on a computer, and/or encrypting data.

Claims

1. A method for controlling distribution of data relating to glucose levels between applications executing on a computing device, comprising:

receiving, at a mobile computing device, a plurality of data values relating to glucose level monitoring;

separating, at a first application operable on the mobile computing device, the plurality of data values into a first set of data and a second set of data according to a predetermined criteria, the first set of data comprising data values restricted from the second set of data; and

providing the second set of data to a second application operable on the mobile computing device.

2. The method of claim 1, wherein the first application includes a medical device software application that configures the mobile computing device to receive and process glucose data including the data values relating to the glucose level monitoring provided by a continuous glucose monitoring sensor device, and wherein the second application includes a third-party software application.

3. The method of claim 2, wherein the third-party software application is configured to provide at least some capabilities different than that of the first application including processing ancillary data and integrating the ancillary data with the glucose data, wherein the ancillary data includes one or more of insulin data, meal data, or exercise data.

4. The method of claim 2, wherein the third-party software application is not an approved medical device software application approved by a governmental regulatory institution authorized to regulate medical device technologies.

5. The method of claim 1, wherein the plurality of data values are separated into the first set of data and the second set of data based on predetermined data permissions associated with the second application.

6. The method of claim 1, wherein the received plurality of data values include continuously generated glucose measurements, and wherein the separating the plurality of data values further includes:

averaging the continuously generated glucose measurements over a predetermined interval to produce glucose average values to be in the second set of data.

7. The method of claim 1, wherein the received plurality of data values include continuously generated glucose measurements, and wherein the separating the plurality of data values further includes:

generating generalized indications of the continuously generated glucose measurements over a predetermined interval to be in the second set of data, wherein a generalized indication is representative of the continuously generated glucose measurements being in one of a predefined low range, a predefined normal range, and a predefined high range.

8. The method of claim 1, wherein each of the plurality of data values include an associated timestamp;

and the method comprises;

determining, by the first application, that a time duration between a current time and the timestamps meets a predetermined amount of delay; and

delaying the providing the second set of data to a second application for the predetermined amount of delay.

9. The method of claim 8, wherein the delay is between five minutes and three hours.

10. The method of claim 8, further comprising:

encrypting the second set of data prior to the providing the second set of data to the second application.

11. The method of claim 1, wherein the first application is configured to process glucose data associated with a continuous glucose sensor device;

and the method further comprising;

receiving from a third-party application, at the first application, one or more single glucose measurements acquired from a single-measurement glucose sensor device;

analyzing, by the first application, metadata corresponding to the one or more single glucose measurements; and

authenticating, by the first application, the one or more single glucose measurements as calibration data for the continuous analyte sensor device.

12. A method for controlling access to data relating to glucose levels on a mobile computing device, comprising:

receiving data relating to glucose levels using a first application operable on a smart phone;

encrypting at least a subset of the data;

providing the encrypted subset of data to a second application operable on the smart phone;

providing the encrypted subset of data to a third application operable on the smart phone via the second application; and

providing a key to the third application to decrypt the encrypted subset of data.

13. The method of claim 12, wherein the first application includes a medical device software application that configures the mobile computing device to receive and process the data relating to the glucose levels provided by a continuous glucose monitoring sensor device, and wherein one or both of the second application and the third application is a third-party software application.

14. The method of claim 13, wherein the third-party software application is configured to provide at least some capabilities different than that of the first application including processing ancillary data and integrating the ancillary data with the glucose data, wherein the ancillary data includes one or more of insulin data, meal data, or exercise data.

15. The method of claim 13, wherein the third-party software application is not an approved medical device software application approved by a governmental regulatory institution authorized to regulate medical device technologies.

16. The method of claim 12, further comprising:

prior to the providing the encrypted subset of data to the second application, separating the data into a first data set of the data and a second data set of the data consisting of the subset according to a predetermined criteria, wherein the first set of data comprises data values restricted from the second set of data.

17. The method of claim 12, wherein the received data includes glucose values and an associated timestamp for each glucose value;

and the method comprises;

determining, by the first application, that a time duration between a current time and the timestamps meets a predetermined amount of delay; and

delaying the providing the second set of data to a second application for the predetermined amount of delay.

18. The method of claim 17, wherein the delay is between five minutes and three hours.

19. The method of claim 12, wherein the second application is provided the key to decrypt the encrypted subset of data.

20. A medical device software application on a computer-readable medium of a mobile computing device, the medical device software application for managing glucose data received from a glucose sensor, and comprising instructions which, when executed by a processor of the mobile computing device, causes the mobile computing device to:

receive one or more glucose measurements generated by the glucose sensor;

divide the one or more glucose measurements into a first set of data and a second set of data according to a predetermined criteria, the first set of data comprising data values restricted from the second set of data; and

provide the second set of data to a third-party software application operable on the mobile computing device.

21. The medical device software application of claim 20, wherein the third-party software application is not an approved medical device software application approved by a governmental regulatory institution authorized to regulate medical device technologies.

22. The medical device software application of claim 20, wherein the third-party software application is configured to provide at least some capabilities different than that of the medical device software application including processing ancillary data and integrating the ancillary data with the retrospective glucose data, wherein the ancillary data includes one or more of insulin data, meal data, or exercise data.

23. The medical device software application of claim 20, wherein the received one or more glucose measurements include an associated timestamp, and wherein the medical device software application includes instructions, which when executed by the processor causes the mobile computing device to:

assign the received one or more glucose measurements as retrospective glucose data or actionable glucose data based on a predetermined amount of time difference between the timestamp and a current time; and

provide the retrospective glucose data to a third-party software application operable on the mobile computing device.

24. The medical device software application of claim 20, wherein the medical device software application includes instructions, which when executed by the processor, causes the mobile computing device to:

encrypt the received one or more glucose measurements or the second set of data prior to providing the second set of data to the third-party software application;

transmit an instruction for the third-party software application to provide the encrypted second set of data to a second third-party software application operable on the mobile computing device; and

provide a key to the second third-party software application to decrypt the encrypted retrospective glucose data.