# US 10,945,600 B2 · Systems and methods for distributing continuous glucose data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,945,600 B2 - Document ID: US10945600B2 - Status: Granted - Kind: B2 - Application number: 15/019,881 - Filed: 2016-02-09 - Published: 2016-08-11 - Granted: 2021-03-16 - Earliest claimed: 2015-02-10 - Assignees: DexCom, Inc. - Applicants: DexCom, Inc. - Inventors: Michael Robert Mensinger; Esteban Cabrera, Jr.; Eric Cohen; Nathaniel David Heintzman; Apurv Ullas Kamath; Gary A. Morris; Andrew Attila Pal; Eli Reihman; Jorge Valdes - Web page: https://patentgrep.com/patent/US10945600B2 ## CPC - A61B 5/0002: {Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network (endoradiosondes A61B5/07)} - A61B 5/0004: {characterised by the type of physiological signal transmitted} - A61B 5/0022: {Monitoring a patient using a global network, e.g. telephone networks, internet} - A61B 5/14532: {for measuring glucose, e.g. by tissue impedance measurement} - 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} - A61B 5/742: {using visual displays (displays for heart-related electrical signals, e.g. ECG, A61B5/339)} - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules - G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes} - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H 40/67: for remote operation - G16H 50/30: for calculating health indices; for individual health risk assessment - A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## 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 ### Claim 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 stored and executing at 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 executing at the mobile computing device. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 2) 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. ### Claim 4 (depends on 2) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) 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. ### Claim 8 (depends on 1) 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. ### Claim 9 (depends on 8) The method of claim 8, wherein the delay is between five minutes and three hours. ### Claim 10 (depends on 8) 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. ### Claim 11 (depends on 1) The method of claim 1, wherein the first application is configured to process glucose data associated with a continuous analyte 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. ### Claim 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 stored and executing at a smart phone; separating the data into a first set of data and a second set of data according to a predetermined criteria; encrypting at least the second set of data to generate an encrypted second set of data; providing the encrypted second set of data to a second application executing at the smart phone; providing the encrypted second set of data to a third application executing at the smart phone via the second application; and providing a key to the third application to decrypt the encrypted second set of data. ### Claim 13 (depends on 12) 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. ### Claim 14 (depends on 13) 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. ### Claim 15 (depends on 13) 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. ### Claim 16 (depends on 12) 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. ### Claim 17 (depends on 16) The method of claim 16, wherein the delay is between five minutes and three hours. ### Claim 18 (depends on 12) The method of claim 12, wherein the second application is provided the key to decrypt the encrypted second set of data. ### Claim 19 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, by the medical device software application, one or more glucose measurements generated by the glucose sensor; divide, by the medical device software application stored and executing at the mobile computing device, 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, by the medical device software application, the second set of data to a third-party software application executing at the mobile computing device. ### Claim 20 (depends on 19) The medical device software application of claim 19, 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. ### Claim 21 (depends on 19) The medical device software application of claim 19, 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 retrospective glucose data, wherein the ancillary data includes one or more of insulin data, meal data, or exercise data. ### Claim 22 (depends on 19) The medical device software application of claim 19, 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 executing at the mobile computing device. ### Claim 23 (depends on 19) The medical device software application of claim 19, 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 to generate an encrypted second set of data; transmit an instruction for the third-party software application to provide the encrypted second set of data to a second third-party software application executing at the mobile computing device; and provide a key to the second third-party software application to decrypt the encrypted second set of data. ### Claim 24 (depends on 1) The method of claim 1, wherein the first set of data includes real-time glucose measurements and the second set of data includes retrospective glucose measurements but does not include the real-time glucose measurements. ### Claim 25 (depends on 24) The method of claim 24, wherein the first set of data further includes predicted glucose measurements and the second set of data does not include the predicted glucose measurements. ### Claim 26 (depends on 1) The method of claim 1, wherein the first set of data includes real-time glucose measurements and the second set of data includes averaged glucose values over defined intervals but does not include the real-time glucose measurements. ### Claim 27 (depends on 1) The method of claim 1, wherein the first set of data includes real-time glucose measurements and the second set of data includes generalized indications of glucose levels but does not include the real-time glucose measurements.