Feedback to improve diabetes management

The continuous glucose monitoring system addresses the challenge of interpreting raw glucose data by providing user-friendly feedback, enhancing diabetes management through actionable insights and improved health outcomes.

JP2024540795APending Publication Date: 2024-11-06DEXCOM INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024506761
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-12-22
Filing Date
2022-10-26
Publication Date
2024-11-06

AI Technical Summary

Technical Problem

Conventional glucose monitoring applications present raw data in a way that is difficult for users to interpret, especially for those new to glucose monitoring, leading to frustration and inability to derive meaningful insights, exacerbated by limitations of mobile devices, hindering effective diabetes management.

Method used

A continuous glucose monitoring system that generates and analyzes glucose measurements over time, identifying periods of good or poor diabetes control, and provides user-friendly feedback to users, highlighting improvements and areas for improvement.

Benefits of technology

Enhances user understanding of glucose levels, promotes better diabetes management by providing actionable insights, motivating users to improve their health outcomes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024540795000001_ABST
    Figure 2024540795000001_ABST
Patent Text Reader

Abstract

Glucose level measurements or other data about a user are obtained over time, such as from a wearable glucose monitoring device worn by the user. These glucose level measurements or other data are analyzed based on various rules, for example, to determine periods of good diabetes management during the day by the user and provide feedback to the user indicative of such. Good diabetes management is identified in various ways, for example, by identifying improvements in glucose measurements for a given period over the past day or days, identifying periods of a day during which glucose measurements were best, identifying sustained positive patterns (e.g., good diabetes management for the same period on each of multiple days), etc.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 292,929, filed December 22, 2021, entitled "Feedback For Improving Diabetes Management," the entire disclosure of which is incorporated herein by reference, and also claims the benefit of U.S. Provisional Patent Application No. 63 / 263,188, filed October 28, 2021, entitled "Ranking Feedback For Improving Diabetes Management," the entire disclosure of which is incorporated herein by reference. [Background technology]

[0002] Diabetes is a metabolic condition that affects hundreds of millions of people and is one of the leading causes of death worldwide. For people living with type I diabetes, access to treatment is essential for their survival, and it can reduce adverse outcomes among people with type II diabetes. With proper treatment, serious damage to the heart, blood vessels, eyes, kidneys, and nerves caused by diabetes can be avoided. Regardless of the type of diabetes (e.g., type I or type II), successfully managing diabetes involves monitoring and repeatedly adjusting food and activity to control a person's blood sugar, e.g., to reduce serious fluctuations in a person's glucose and / or to lower a person's glucose overall.

[0003] However, many conventional glucose monitoring applications use user interfaces that display raw glucose information in a manner that is difficult for users to interpret, especially for users who have only recently begun monitoring their glucose. As a result, users may not be able to derive insight from the data and therefore cannot change their behavior in a meaningful way to improve their glucose. Over time, these users often become overwhelmed and frustrated by the way the information is presented by these conventional glucose monitoring applications, and therefore discontinue use of these applications before improvements in glucose and overall health can be realized. Furthermore, as users increasingly utilize mobile devices (e.g., smart watches and smartphones) to access glucose monitoring information, the limitations imposed by the small screens of these mobile devices further exacerbate the inability of conventional systems to provide meaningful glucose information for users to understand. Summary of the Invention [Means for solving the problem]

[0004] To overcome these problems, a technique for diabetes management feedback to improve diabetes management is discussed. In one or more implementations, in a continuous glucose level monitoring system, a first glucose measurement is obtained from a glucose sensor of the continuous glucose level monitoring system. The first glucose measurement is measured for a user during a first time period of a plurality of time periods on a current day, and the glucose sensor is inserted at an insertion site of the user. One or more features are generated from the first glucose measurement during the first time period on the current day. The one or more features are analyzed to determine at least one feature that satisfies one or more rules for the first time period on the current day. A plurality of diabetes management feedbacks in a library of diabetes management feedbacks corresponding to the one or more satisfied rules are identified. A user interface is generated that includes an indication of the identified diabetes management feedback and the first time period, and the identified diabetes management feedback is displayed.

[0005] This Summary introduces a selection of concepts in a simplified form that are further described below in the Detailed Description. As such, this Summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. [Brief description of the drawings]

[0006] The detailed description is given with reference to the accompanying drawings. [Figure 1] FIG. 1 is a diagram of an environment in an example implementation operable to implement diabetes management feedback to improve diabetes management as described herein. [Diagram 2] 1 illustrates an example implementation of a wearable glucose monitoring device in more detail. [Diagram 3] FIG. 1 is a diagram of an example architecture of a diabetes management feedback generation system. [Figure 4]1 illustrates an example of providing feedback indicating an improvement in at least one characteristic over a period of time. [Diagram 5] An example of providing feedback indicating the best period during the day is given. [Figure 6] 13 illustrates an example of providing feedback indicative of a positive persistence pattern. [Figure 7] 1 shows a procedure in an example for implementing diabetes management feedback to improve diabetes management. [Figure 8] 13 shows a procedure in another example of implementing diabetes management feedback to improve diabetes management. [Figure 9] 1 illustrates an overview of example systems, including example computing devices that represent one or more computing systems and / or devices that may implement various techniques described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] overview Techniques for feedback to improve diabetes management are discussed herein. Generally, blood glucose measurements of a user are obtained over time. These glucose level measurements are typically obtained by a wearable glucose monitoring device worn by the user. These glucose level measurements may be generated substantially continuously, such that the device may be configured to generate glucose level measurements at regular or irregular time intervals (e.g., about every hour, about every 30 minutes, about every 5 minutes, etc.), in response to the establishment of a communication coupling with a different device (e.g., when a computing device establishes a wireless connection with the wearable glucose level monitoring device to retrieve one or more of the measurements), etc. These glucose level measurements are analyzed based on various rules to determine periods of good (or optionally poor) diabetes management by the user, and feedback indicative of such is provided to the user.

[0008] In one or more implementations, a data stream of glucose measurements is received. Various other data streams, such as activity data (e.g., the user's step count), may optionally be received. One or more features are generated and stored for a particular time period. Each feature may be calculated from data in the data stream and is a value indicative of whether the user is engaging in beneficial diabetes management behaviors or lifestyle choices. The features may include metrics that are representations or summaries of data in the data stream for a particular time period and are generated and stored. These periods are, for example, different blocks of time within a day. For example, a day may include a first period from midnight to 6 a.m. (corresponding to sleep), a second period from 6 a.m. to noon (corresponding to after breakfast), a third period from noon to 6 p.m. (corresponding to after lunch), and a fourth period from 6 p.m. to midnight (corresponding to after dinner). These periods may be fixed or may be adaptively identified based on features identified in another data stream (e.g., sleep onset may be detected by an activity monitor and used to determine the start of the "sleep" period for the day).

[0009] Good diabetes management is identified, for example, by identifying improvements in glucose measurements for a given period over the past day or days, identifying periods of a day during which glucose measurements were best (e.g., within an optimal range or closest to optimal), identifying sustained positive patterns (e.g., good diabetes management for the same period on each of multiple days), etc. Once identified, feedback is generated informing the user of these improvements in glucose measurements, best periods of a day, sustained positive patterns, combinations thereof, etc. This feedback can be retrospective, for example, informing the user of the user's assessment of their diabetes management at the end of the previous day or day.

[0010] The techniques discussed herein are similarly applied to identifying poor diabetes management. Inadequate diabetes management may be identified and feedback (e.g., warnings or adverse effects) may be displayed or otherwise presented to the user to encourage better diabetes management by the user. This feedback may be used to identify problem areas that need to be addressed, actions or choices that should be avoided in the future, etc.

[0011] The techniques discussed herein generate feedback for the user that informs the user of good diabetes management choices (or poor diabetes management choices) that the user has made. This feedback is provided for reflection and motivation by the user, and often provides the user with inspirational insights to continue good diabetes management to improve the user's health, extend lifespan, etc. This feedback also educates the user regarding good diabetes management choices, for example, by allowing them to mimic the changes in the user from one period to another that showed improvement (e.g., increased amount of vegetables consumed).

[0012] In some situations, multiple different feedback items may be provided to the user. In such situations, a prioritization technique is optionally used to prioritize the multiple different feedback items and select one or two to be provided to the user. This prioritization technique improves the user interface presented to the user, such as by reducing the amount of feedback provided to the user (number of feedback items at one time or over time), by reducing repetitiveness in the feedback provided to the user, by highlighting the greatest or most significant glycemic improvements or comparisons, by highlighting the glycemic improvements or comparisons that are most relevant to the user at a given time based on contextual information such as diabetes type, comorbidities, medication, patient or clinician preferences, user feedback regarding previously provided insights, or duration of product use.

[0013] In the following description, an exemplary environment in which the techniques described herein can be used is first described. Then, details of example implementations and procedures that can be performed in the exemplary environment and other environments are described. The execution of the exemplary procedures is not limited to the exemplary environment, and the exemplary environment is not limited to the execution of the exemplary procedures.

[0014] Example Environment 1 is a diagram of an environment 100 in an example implementation operable to implement feedback to improve diabetes management as described herein. The illustrated environment 100 includes a person 102, who is depicted wearing a wearable glucose monitoring device 104. The illustrated environment 100 also includes a computing device 106, other users in a user population 108 who wear the glucose monitoring device 104, and a glucose monitoring platform 110. The wearable glucose monitoring device 104, the computing device 106, the user population 108, and the glucose monitoring platform 110 are communicatively coupled, including via a network 112.

[0015] Alternatively or additionally, the wearable glucose monitoring device 104 and the computing device 106 may be communicatively coupled in other manners, such as using one or more wireless communication protocols or techniques. By way of example, the wearable glucose monitoring device 104 and the computing device 106 may communicate with each other using one or more of Bluetooth (e.g., a Bluetooth Low Energy link), near-field communication (NFC), 5G, etc.

[0016] In accordance with the described techniques, the wearable glucose monitoring device 104 is configured to provide measurements of glucose of the person 102. Although a wearable glucose monitoring device is discussed herein, it should be understood that a user interface for glucose monitoring can be generated and presented in association with other devices capable of providing glucose measurements, e.g., non-wearable glucose devices such as blood glucose meters that require a fingerstick, patch, or the like. However, implementations that include a wearable glucose monitoring device 104 can be configured with, for example, a glucose sensor that continuously detects an analyte indicative of the glucose of the person 102 and enables the generation of glucose measurements. In the illustrated environment 100 and throughout the detailed description, these measurements are referred to as glucose measurements 114.

[0017] In one or more implementations, the wearable glucose monitoring device 104 is a continuous glucose monitoring (CGM) system. As used herein, the term "continuous" used in connection with glucose monitoring may refer to the ability of the device to generate measurements substantially continuously, such that the device may be configured to generate glucose measurements 114 in response to establishing a communication coupling with a different device (e.g., when a computing device establishes a wireless connection with the wearable glucose monitoring device 104 to retrieve one or more of the measurements), at regular or irregular time intervals (e.g., every hour, every 30 minutes, every 5 minutes, etc.). This functionality, along with further aspects of the configuration of the wearable glucose monitoring device 104, are described in more detail in connection with FIG. 2.

[0018] Additionally, the wearable glucose monitoring device 104 transmits glucose measurements 114 to the computing device 106, such as via a wireless connection. The wearable glucose monitoring device 104 can communicate these measurements in real time, for example, as they are generated using a glucose sensor. Alternatively or additionally, the wearable glucose monitoring device 104 can communicate the glucose measurements 114 to the computing device 106 at set time intervals. For example, the wearable glucose monitoring device 104 can be configured to communicate the glucose measurements 114 to the computing device 106 (as they are being generated) every five minutes.

[0019] Certainly, the time intervals at which glucose readings 114 are communicated may vary from the above examples without departing from the spirit or scope of the presently described techniques. The readings may be communicated by the wearable glucose monitoring device 104 to the computing device 106 according to other bases in accordance with the presently described techniques, such as upon request from the computing device 106. In any event, the computing device 106 may maintain the glucose readings 114 of the person 102 at least temporarily, for example, within a computer-readable storage medium of the computing device 106.

[0020] Although the computing device 106 is illustrated as a mobile device (e.g., a mobile phone), it may be configured in various ways without departing from the spirit or scope of the described techniques. By way of example and not limitation, the computing device 106 may be configured as different types of devices, such as a mobile device (e.g., a wearable device, tablet device, or laptop computer), a stationary device (e.g., a desktop computer), an automobile computer, etc. In one or more implementations, the computing device 106 may be configured as a dedicated device associated with the glucose monitoring platform 110, which has the functionality to, for example, obtain glucose readings 114 from the wearable glucose monitoring device 104, perform various calculations related to the glucose readings 114, display information related to the glucose readings 114 and the glucose monitoring platform 110, communicate the glucose readings 114 to the glucose monitoring platform 110, etc.

[0021] Further, computing device 106 may represent two or more devices in accordance with the described techniques. In one or more scenarios, for example, computing device 106 may correspond to both a wearable device (e.g., a smart watch) and a mobile phone. In such a scenario, both of these devices may be capable of performing at least some of the same operations, such as to retrieve glucose readings 114 from wearable glucose monitoring device 104, communicate those readings to glucose monitoring platform 110 via network 112, display information related to glucose readings 114, etc. Alternatively or additionally, different devices may have different capabilities that other devices do not have or that are limited to designated devices through computational instructions.

[0022] In a scenario in which the computing device 106 corresponds to a separate smartwatch and a mobile phone, for example, the smartwatch may be configured with various sensors and capabilities for measuring various physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow velocity, etc.) and activities (e.g., walking or other movement) of the person 102. In this scenario, the mobile phone may not be configured with these sensors and capabilities or may include a limited amount of the capabilities - although in other scenarios the mobile phone may be capable of providing the same functionality. Continuing with this particular scenario, the mobile phone may have capabilities that the smartwatch does not have, such as a camera for capturing images associated with glucose monitoring, and an amount of computing resources (e.g., battery and processing speed) that allows the mobile phone to more efficiently perform calculations related to the glucose measurements 114. Even in scenarios in which the smartwatch is capable of performing such calculations, the computing instructions may limit the execution of those calculations to the mobile phone to not burden both devices and efficiently utilize available resources. To this extent, computing device 106 may be configured in different ways and represent a different number of devices than described herein without departing from the spirit and scope of the described technology.

[0023] According to the discussed techniques, the computing device 106 is configured to implement diabetes management feedback to improve diabetes management. In the environment 100, the computing device 106 includes a glucose monitoring application 116 and a storage device 118. Here, the glucose monitoring application 116 includes a diabetes management feedback generation system 120. Although shown as being included in the computing device 106, additionally or alternatively, at least some functionality of the diabetes management feedback generation system 120 is located elsewhere, such as in the glucose monitoring platform 110. Furthermore, the glucose readings 114 and the feedback library 122 are shown stored in the storage device 118. The storage device 118 may also represent one or more databases, as well as other types of storage capable of storing the glucose readings 114 and the feedback library 122. The feedback library 122 stores a number of feedback items (e.g., messages or message templates) that may be provided to the user 102, for example, to highlight the positive impact of recent diabetes management choices for reflection and motivation by the user 102. This feedback may also be referred to as insights or inspirational insights.

[0024] In one or more implementations, the glucose measurements 114 and / or the feedback library 122 may be stored at least in part remotely from the computing device 106, for example, in a storage device of the glucose monitoring platform 110, and retrieved or otherwise accessed in connection with constructing and outputting (e.g., displaying) a user interface for presenting diabetes management feedback. By way of example, the glucose measurements 114 and / or the feedback library 122 may be generally stored in a storage device of the glucose monitoring platform 110 along with the glucose measurements 108 of the user population and / or the feedback library 122 of the user population, and portions of that data may be retrieved or otherwise accessed as needed to display a user interface for presenting diabetes management feedback.

[0025] Generally speaking, the glucose monitoring application 116 is configured to support interactions with a user that enable feedback regarding the user's glucose to be presented, which may include, for example, obtaining glucose measurements 114 for processing (e.g., to determine appropriate feedback), receiving information about the user (e.g., through an onboarding process and / or user feedback), communicating the information to a healthcare provider, communicating the information to the glucose monitoring platform 110, etc.

[0026] In one or more implementations, the glucose monitoring application 116 also leverages the resources of the glucose monitoring platform 110 in connection with diabetes management feedback to improve diabetes management. As mentioned above, by way of example, the glucose monitoring platform 110 may be configured to store data, such as glucose measurements 114 associated with a user (e.g., person 102) and / or users of the user population 108, as well as a feedback library 122. The glucose monitoring platform 110 may also provide updates and / or additions to the glucose monitoring application 116. Furthermore, the glucose monitoring platform 110 may train, maintain, and / or deploy algorithms (e.g., machine learning algorithms) to generate or select feedback or identify time periods during which feedback is to be provided, such as by using a wealth of data collected from the person 102 and users of the user population 108. One or more such algorithms may require an amount of computing resources that exceeds the resources of a typical personal computing device, such as a mobile phone, laptop, tablet device, and wearable, just to name a few. Nonetheless, glucose monitoring platform 110 may include or otherwise have access to resources needed to operate such algorithms, e.g., cloud storage, server devices, virtualization resources, etc. Glucose monitoring platform 110 may provide a variety of resources that glucose monitoring application 116 leverages in connection with enabling the presentation of diabetes management feedback via a user interface.

[0027] According to the described techniques, the diabetes management feedback generation system 120 is configured to use the glucose measurements 114 to identify one or more feedback items in a feedback library 122 and output one or more user interfaces presenting the identified diabetes management feedback. The glucose monitoring application 116 may display the configured user interface 124 via a display device of the computing device 106 or other display device.

[0028] As discussed above and below, in accordance with the described techniques, various management feedback (e.g., messages) may be selected or generated based on the user's glucose measurements 114. Consider the following description of FIG. 2 in the context of measuring glucose, for example, continuously, to obtain data describing such measurements.

[0029] 2 illustrates a more detailed example 200 of an implementation of the wearable glucose monitoring device 104 of FIG. 1. In particular, the illustrated example 200 includes a top view and a corresponding side view of the wearable glucose monitoring device 104. It should be understood from the following description that the wearable glucose monitoring device 104 may be modified in various ways in implementation without departing from the spirit or scope of the described techniques. As mentioned above, by way of example, a user interface including the presentation of diabetes management feedback may be configured and displayed (or otherwise output) in association with other types of devices for glucose monitoring, such as non-wearable devices (e.g., blood glucose meters requiring a finger stick), patches, etc.

[0030] In this example 200, the wearable glucose monitoring device 104 is illustrated to include a sensor 202 and a sensor module 204. Here, the sensor 202 is shown in a side view inserted, for example, subcutaneously into the skin 206 of the person 102. The sensor module 204 is illustrated as a dashed rectangle in a top view. The wearable glucose monitoring device 104 also includes a transmitter 208 in the illustrated example 200. The use of a dashed rectangle for the sensor module 204 indicates that the sensor module may be contained or otherwise implemented within the housing of the transmitter 208. In this example 200, the wearable glucose monitoring device 104 further includes an adhesive pad 210 and an attachment mechanism 212.

[0031] In operation, the sensor 202, adhesive pad 210, and attachment mechanism 212 may be assembled to form an application assembly, which is configured to be applied to the skin 206 such that the sensor 202 is inserted subcutaneously as depicted. In such a scenario, the transmitter 208 may be attached to the assembly after affixing to the skin 206 via the attachment mechanism 212. Alternatively, the transmitter 208 may be incorporated as part of an application assembly, such that the sensor 202, adhesive pad 210, attachment mechanism 212, and transmitter 208 (with sensor module 204) can be affixed to the skin 206 all at once. In one or more implementations, this application assembly is affixed to the skin 206 using a separate sensor applicator (not shown). Unlike the finger prick required by conventional blood glucose meters, user-initiated application of the wearable glucose monitoring device 104 is substantially painless and does not require the withdrawal of blood. Additionally, an automatic sensor applicator generally allows the person 102 to implant the sensor 202 subcutaneously in the skin 206 without the assistance of a clinician or healthcare provider.

[0032] The application assembly can also be removed by peeling the adhesive pad 210 from the skin 206. It should be understood that the wearable glucose monitoring device 104 and its various components as shown are simply one example form factor, and that the wearable glucose monitoring device 104 and its components can have different form factors without departing from the spirit or scope of the presently described techniques.

[0033] In operation, the sensor 202 is communicatively coupled to the sensor module 204 via at least one communication channel, which may be a wireless connection or a wired connection. Communications from the sensor 202 to the sensor module 204 or from the sensor module 204 to the sensor 202 may be performed actively or passively, and these communications may be continuous (e.g., analog) or discrete (e.g., digital).

[0034] The sensor 202 may be a device, molecule, and / or chemical that changes or causes a change in response to an event that is at least partially independent of the sensor 202. The sensor module 204 is implemented to receive an indication of a change to the sensor 202 or caused by the sensor 202. For example, the sensor 202 may include glucose oxidase that reacts with glucose and oxygen to form hydrogen peroxide that is electrochemically detectable by the sensor module 204, which may include electrodes. In this example, the sensor 202 may be configured as or include a glucose sensor configured to detect an analyte in blood or interstitial fluid that is indicative of diabetes management using one or more measurement techniques. In one or more implementations, the sensor 202 may also be configured to detect analytes in blood or interstitial fluid that are indicative of other markers, such as lactate levels, which may improve accuracy in generating various diabetes management feedback. Additionally or alternatively, the wearable glucose monitoring device 104 may include additional sensors in the sensor 202 to detect analytes indicative of other markers.

[0035] In another example, the sensor 202 (or additional, not shown, sensors of the wearable glucose monitoring device 104) can include first and second conductors, and the sensor module 204 can electrically detect a change in electrical potential across the first and second conductors of the sensor 202. In this example, the sensor module 204 and the sensor 202 are configured as a thermocouple, such that the change in electrical potential corresponds to a change in temperature. In some examples, the sensor module 204 and the sensor 202 are configured to detect a single analyte, e.g., glucose. In other examples, the sensor module 204 and the sensor 202 are configured to detect multiple analytes, e.g., sodium, potassium, carbon dioxide, and glucose. Alternatively or additionally, the wearable glucose monitoring device 104 includes multiple sensors for detecting not only one or more analytes (e.g., sodium, potassium, carbon dioxide, glucose, and insulin), but also one or more environmental conditions (e.g., temperature). Thus, the sensor module 204 and the sensor 202 (and any additional sensors) may detect the presence of one or more analytes, the absence of one or more analytes, and / or a change in one or more environmental conditions.

[0036] In one or more implementations, the sensor module 204 can include a processor and memory (not shown). The sensor module 204 can utilize the processor to generate glucose readings 114 based on communications with the sensor 202 exhibiting the changes described above. Based on these communications from the sensor 202, the sensor module 204 is further configured to generate communicable data packages that include the at least one glucose reading 114. In one or more implementations, the sensor module 204 can configure these packages to include additional data including, by way of example and not limitation, a sensor identifier, a state of the sensor, a temperature corresponding to the glucose reading 114, measurements of other analytes corresponding to the glucose reading 114, and the like. It should be understood that such packets can include a variety of data in addition to the at least one glucose reading 114 without departing from the spirit or scope of the described techniques.

[0037] In implementations in which the wearable glucose monitoring device 104 is configured for wireless transmission, the transmitter 208 can wirelessly transmit the glucose readings 114 as a data stream to the computing device. Alternatively or additionally, the sensor module 204 may buffer the glucose readings 114 (e.g., in a memory of the sensor module 204 and / or other physical computer-readable storage medium of the wearable glucose monitoring device 104) and later cause the transmitter 208 to transmit the buffered glucose readings 114 at various intervals, such as time intervals (every second, every 30 seconds, every minute, every 5 minutes, every hour, etc.), storage intervals (when the buffered glucose readings 114 reach a threshold amount of data or number of readings), etc.

[0038] Having considered example environments and examples of wearable glucose monitoring devices, we now turn to a discussion of some example details of techniques for diabetes management feedback to improve diabetes management.

[0039] System Architecture 3 is a diagram of an example architecture of a diabetes management feedback generation system 120. The diabetes management feedback generation system 120 includes a diabetes management characteristic determination module 302, a diabetes management characteristic comparison module 304, a normalization module 306 (optional), a diabetes management feedback identification module 308, a UI module 310, and a user-specific diabetes management characteristic threshold determination module 312. Generally, the diabetes management feedback generation system 120 analyzes the glucose measurements 114 of the user 102 and looks for patterns in the glucose measurements 114 that indicate good diabetes management by the user. Good diabetes management may be quantified in a variety of ways, such as the glucose measurements 114 staying within a certain range, the glucose measurements 114 not fluctuating more than a certain amount, etc. In one or more implementations, the diabetes management feedback generation system 120 identifies good diabetes management by identifying an improvement in the glucose measurement 114 for a given period over the past day or days, by identifying a period of a day during which the glucose measurement 114 was best (e.g., was within the optimal range or closest to the optimal value), by identifying a sustained positive pattern (e.g., good diabetes management for the same period on each of multiple days), or a combination thereof.

[0040] The diabetes management characteristic determination module 302 receives a data stream 320. In one or more implementations, the data stream 320 includes the glucose measurements 114 and a timestamp indicating the time each of the glucose measurements 114 was taken (e.g., by the wearable glucose monitoring device 104) or received (e.g., by the glucose monitoring application 116). The timestamp may be provided, for example, by the wearable glucose monitoring device 104 or the glucose monitoring application 116. Additionally or alternatively, the data stream 320 includes additional data that may be used to identify good diabetes management (e.g., other data that affects the glucose level of the user 102). This additional data may be referred to as an additional data stream (e.g., the diabetes management characteristic determination module 302 receives multiple data streams 320, each of which includes data from a different source or sensor).

[0041] For example, the data stream 320 may include activity data such as the number of steps taken over a particular time range (e.g., every 10 seconds, every minute), heart rate and timestamps over a particular time range (e.g., at regular or irregular intervals such as every 15 seconds), movement speed and timestamps (e.g., at regular or irregular intervals such as every 15 seconds), etc. Activity data may be received from a variety of sources, such as the wearable glucose monitoring device 104, an activity tracking application running on the computing device 106, an activity or fitness tracker worn by the user 102, etc.

[0042] As another example, data stream 320 may include data regarding a user's sleep patterns. For example, data stream 320 may include data indicative of how long the user slept, what state the user was sleeping at a particular time (e.g., stage 1, stage 2, stage 3, or rapid eye movement (REM) sleep), etc.

[0043] As another example, the data stream 320 may include data regarding user engagement with the glucose monitoring application 116. For example, this application engagement data may include timestamps of when the user 102 viewed the application and the portions of the screens or UI that were viewed, timestamps of when the user 102 provided input to (or otherwise interacted with) the application 116 and the content of that input, timestamps of when the user viewed or acknowledged feedback provided by the diabetes management feedback generation system 120, etc.

[0044] As another example, the data stream 320 may include data regarding a user's engagement with others in the user population 108, such as via the glucose monitoring platform 110. For example, this other user engagement data may include timestamps of when the user 102 communicated with other users, as well as who the other users were, a description of the information communicated with the other users, etc.

[0045] As another example, the data stream 320 may include dietary data, which may include timestamps of when the user 102 ate and the foods consumed, timestamps of when particular types or classes of foods (e.g., vegetables, grains, meats, sweets, sodas) were consumed, the amount of food consumed, etc.

[0046] As another example, the data stream 320 may include sleep data, such as data indicating the number of minutes a user sleeps per day. The sleep data may be received from a variety of sources, such as the wearable glucose monitoring device 104, a sleep tracking application running on the computing device 106, an activity or fitness tracker worn by the user 102, etc.

[0047] As another example, the data stream 320 may include medication data, which may include a timestamp of when the user 102 took a medication and the medication taken (which may be used to determine whether the user 102 took their medication at a given time or at a given interval), an indication of a change in medication (e.g., a change in the type or dose of medication taken), etc.

[0048] As another example, the data stream 320 may include data reflective of stress management, such as heart rate variability (HRV), skin conductance and temperature, respiration rate measurements, data from an electroencephalogram (EEG), cortisol in biological fluids, and volatile organic components (VOCs) emitted from the skin.

[0049] As another example, the data stream 320 may include data related to user interactions with the computing device 106, the display of the computing device 106, or other system components that indicate a level of engagement in diabetes management. Examples of such data include the number of times an application (e.g., a glucose monitoring application) was opened, the amount of time spent reviewing glucose data or previous insights or educational materials, the frequency of interactions with a coach or clinician, etc.

[0050] In one or more embodiments, the diabetes management feedback generation system 120 receives a data stream 320 including the glucose measurements 114 and provides feedback to improve diabetes management. Additionally, the diabetes management feedback generation system 120 optionally receives additional data in the data stream 320 that may be used to identify positive diabetes management actions or the impact of these actions in the absence of a glucose measurement 114. For example, if the user 102 uses only a CGM regularly, but continues to use a glucose monitoring application 116 or another diabetes management application (or wears another device that collects additional data), the diabetes management feedback generation system 120 continues to provide feedback derived from this other data during times when the CGM is not being used.

[0051] The diabetes management characteristic determination module 302 generates one or more features 322. A feature 322 may be calculated from data in one or more data streams and refers to any value that indicates whether a user is engaging in beneficial diabetes management behaviors or lifestyle choices. A feature 322 may be a metric that is a representation or summary of data in the data stream 320 for a particular time period. In one or more implementations, each feature 322 is one or two values ​​that represent or summarize data in the data stream 320 for a particular time period, converting raw data obtained from the data stream 320 into a numerical indicator of adherence to beneficial diabetes management and lifestyle choices. The diabetes management characteristic determination module 302 stores the generated features 322 in a data store 324 (e.g., maintained on the storage device 118). The generated features 322 are maintained for a period of time that may vary depending on the embodiment. For example, the generated features 322 may be maintained for two weeks, one month, one year, etc.

[0052] In one or more implementations, each period is a portion of a day (or other 24-hour interval). These periods are selected to capture the impact of certain diabetes management decisions and lifestyle choices. In one or more implementations, each day is divided into periods based on the time the user eats and the time the user goes to bed. For example, a day may include a first period from midnight to 6 a.m. (corresponding to sleep), a second period from 6 a.m. to noon (corresponding to after breakfast), a third period from noon to 6 p.m. (corresponding to after lunch), and a fourth period from 6 p.m. to midnight (corresponding to after dinner). Additionally or alternatively, additional periods may correspond to other user actions that affect glucose levels, such as when the user exercises.

[0053] The glucose monitoring application 116 optionally provides a user interface that allows the user 102 to customize the periods to fit his or her typical schedule. For example, assume that the user 102 typically goes to bed at 10 p.m., eats breakfast at 7 a.m., lunch at noon, and dinner at 5 p.m. These times may be provided (e.g., by the user) to the glucose monitoring application 116, which determines the periods of a day to include a first period from 10 p.m. to 7 a.m. (corresponding to sleep), a second period from 7 a.m. to noon (corresponding to after breakfast), a third period from noon to 5 p.m. (corresponding to after lunch), and a fourth period from 5 p.m. to midnight (corresponding to after dinner). A day may be divided into a number of periods other than four. For example, assume that the user 102 typically goes to bed at 10 p.m., exercises at 5 a.m., eats breakfast at 7 a.m., eats lunch at 11 a.m., eats a snack at 2 p.m., and eats dinner at 6 p.m. These times may be provided to the glucose monitoring application 116, which determines the periods of the day to include a first period from 10:00 p.m. to 5:00 a.m. (corresponding to sleep), a second period from 5:00 a.m. to 7:00 a.m. (corresponding to exercise), a third period from 7:00 a.m. to 11:00 a.m. (corresponding to after breakfast), a fourth period from 11:00 a.m. to 2:00 p.m. (corresponding to after lunch), a fourth period from 2:00 p.m. to 6:00 p.m. (corresponding to a snack), and a sixth period from 6:00 p.m. to 10:00 p.m. (corresponding to after dinner).

[0054] Additionally or alternatively, different periods of the user 102 can be automatically learned or directly detected (e.g., sleep onset detected by an activity tracker) by the glucose monitoring application 116 by monitoring various data available to the glucose monitoring application 116 (e.g., movement or sleep patterns from an activity tracker, dietary patterns from a food or calorie tracking application). Various rules or criteria can be used to determine the periods based on various data available to the glucose monitoring application 116, such as detecting sleep onset and sleep stop from an activity tracker and using the sleep start and sleep stop times to determine the periods corresponding to sleep.

[0055] In one or more implementations, the glucose monitoring application 116 uses a machine learning system to determine the different time periods of the user 102. A machine learning system refers to a computer representation that can be adjusted (e.g., trained) based on inputs to approximate an unknown function. In particular, a machine learning system can include a system that utilizes algorithms that learn from and make predictions on known data by analyzing known data to learn to generate outputs that reflect patterns and attributes of the known data. For example, machine learning systems can include decision trees, support vector machines, linear regression, logistic regression, Bayesian networks, random forest learning, dimensionality reduction algorithms, boosting algorithms, artificial neural networks, deep learning, and the like.

[0056] The machine learning system is trained by using training data, which is, for example, a set of a plurality of data (e.g., the number of times exercise, sleep, or meal occurred during a day) and a timestamp indicating the time when the exercise, sleep, or meal occurred. A known label is associated with the set of a plurality of data indicating the time period to which the data corresponds. The machine learning system is trained by updating weights or values ​​of layers in the machine learning system to minimize the loss between the time periods generated by the machine learning system for the training data and the corresponding known labels of the training data. A variety of different loss functions can be used in training the machine learning system, such as cross-entropy loss, mean squared error loss, etc.

[0057] In one or more implementations, the machine learning system is trained over time as the glucose monitoring application 116 is used over time. For example, a user can provide an indication of whether a particular period is correct or not, which can be used as a known label for the current period and used to further train the machine learning system.

[0058] Thus, different periods can be established for different users. Additionally, different periods can be established for different days. For example, a user 102 may have a different schedule for different types of days (e.g., a different schedule for weekends and holidays than for weekdays). Thus, the periods for different types of days can be provided by the user 102 or can be determined by a machine learning system of the glucose monitoring application 116.

[0059] In one or more embodiments, the blocks of time of different periods may be different for a user across different days. For example, a user may typically go to bed between 11:00 PM and midnight and wake up between 5:30 AM and 6:30 AM. For any given day, the time the user goes to bed and the time the user wakes up may be detected using various data streams, such as data from an activity tracker worn by the user. Thus, the period corresponding to the user's sleep may be 11:13 PM to 6:00 AM one day, 11:27 PM to 5:48 AM the next day, 11:45 PM to 6:12 AM the next day, etc.

[0060] In one or more embodiments, the time periods may be different for the different data streams. The time periods for the different data streams may be selected or identified for the purpose of choosing a time window that best captures data related to the occurrence or characteristics of the behavior itself (e.g., meal selection), the effect of the behavior on physiology that may be delayed relative to the behavior (e.g., glucose, sleep quality, etc.), or a combination of the behavior and its effect.

[0061] The diabetes management characteristic determination module 302 may generate any of a variety of features 322 for the data stream 320 for each time period, and may generate different features 322 for different types of data in the data stream 320 (e.g., features 322 for glucose measurements that are different from features for activity). For example, for a glucose measurement, the diabetes management characteristic determination module 302 may generate a time-in-range feature, such as the time during the period during which the glucose measurement was within an acceptable or desired range of glucose levels, e.g., between 70 milligrams per deciliter (mg / dL) and 180 mg / dL, or within a narrow range between 70 mg / dL and 140 mg / dL. This acceptable or desired range may be a default range, may be a custom range set by a user or a medical professional, or the like. As another example, for a glucose measurement, the diabetes management characteristic determination module 302 may generate a time-below-threshold feature, such as the time during the period during which the glucose measurement was below a particular glucose level (e.g., 250 mg / dL or 70 mg / dL). This particular glucose level may be a default level, may be a custom level set by a user or a medical professional, or the like. As another example, for a glucose measurement, the diabetes management characteristic determination module 302 can generate a time above threshold characteristic, such as the time during the period that the glucose measurement was above a particular glucose level (e.g., 250 mg / dL). This particular glucose level can be a default level, a custom level set by a user, a medical professional, or the like. As another example, for a glucose measurement, the diabetes management characteristic determination module 302 can generate any of a variety of statistics, such as the coefficient of variation of the glucose measurements within the period (the ratio of the standard deviation to the mean of the glucose measurements within the period), the average glucose measurement within the period, the standard deviation of the glucose measurements within the period, etc.As another example, for a glucose measurement, the diabetes management characteristic determination module 302 may generate any of a variety of additional values ​​such as the maximum glucose measurement in the time period, the rate of change of the maximum glucose measurement in the time period, the rise in the maximum glucose measurement in the time period, the low blood glucose index (LBGI) in the time period, the high blood glucose index (HBGI) in the time period, etc. As another example, for a glucose measurement, the diabetes management characteristic determination module 302 may generate a value indicative of the rate of increase or decrease in glucose levels (e.g., a rapid rise around a predicted mealtime may allow the diabetes management feedback generation system 120 to infer that the patient has consumed a food with a high glycemic index, or a rapid fall from a high glucose level associated with detected physical activity may allow the diabetes management feedback generation system 120 to infer that the user has taken an action to reduce glucose by exercising).

[0062] As another example, for activity data, the diabetes management feature determination module 302 can generate a step feature, which is the number of steps during the time period, an average or range of heart rate reserve during the time period, metabolic equivalents (METs) expended during the time period, etc. As another example, for activity data, the diabetes management feature determination module 302 can generate a time in range feature, such as the time during the time period that the user's heart rate was within an acceptable or desired range of heart rates, for example, 120 beats per minute (BPM) to 170 BPM. This acceptable or desired range may be a default range, may be a custom range set by the user or a medical professional, etc. As another example, for activity data, the diabetes management feature determination module 302 can generate a time above threshold feature, such as the time during the time period that the user's heart rate was above a particular level (e.g., 120 BPM). This particular level may be a default level, may be a custom setting set by the user or a medical professional, etc.

[0063] As another example, for sleep data, the diabetes management characteristic determination module 302 may generate values ​​indicative of sleep duration, number of sleep disturbances or interruptions, time spent in particular sleep states, and the like.

[0064] The diabetes management feature comparison module 304 receives the distinct features 322 from the data store 324 (additionally or alternatively, the features 322 may be received directly from the diabetes management feature determination module 302) and generates a period score 326. The period score 326 indicates the difference between the distinct features 322 generated for the different periods. The diabetes management feature determination module 302 generates distinct features 322 for each period of a day, as described above. The period score 326 allows the diabetes management feature determination module 302 to compare features 322 for different periods within the same day, for the same period across different days, or across different types of days, etc.

[0065] In one or more implementations, the diabetes management feature comparison module 304 compares the features 322 to each other for each period of the day. Additionally or alternatively, the diabetes management feature comparison module 304 compares the features 322 for one or more periods of the current day to a corresponding period of one or more days in the past (e.g., the previous week or two weeks). "Current day" refers to the day (or other 24-hour interval) that the diabetes management feedback generation system 120 is analyzing. The current day can be, for example, the day on which the user 102 is currently living, the day immediately preceding the day on which the user 102 is currently living, or another day in the user's past. In a situation where there are multiple types of days (e.g., weekends and holidays as one type and weekdays as another type), the diabetes management feature comparison module 304 compares the features 322 for one or more periods of the current day (e.g., the day on which the user 102 is currently living or the previous day) to a corresponding period of one or more days in the past of the same type (e.g., the previous week or two weeks for weekdays, or the previous three or four weeks for weekends and holidays).

[0066] Additionally or alternatively, the diabetes management feature comparison module 304 compares summary statistics of features 322 calculated from corresponding time periods of a set of past days. For example, the diabetes management feature comparison module 304 can compare the mean, median, interquartile range (IQR), XX th order, standard deviation, etc. of features 322 calculated from corresponding time periods of a set of past days.

[0067] Additionally or alternatively, the diabetes management feature comparison module 304 compares features 322 for one or more time periods during multiple days of a week to corresponding time periods during multiple days of the past week or weeks. For example, for a particular diabetes management feature or features (e.g., time in range), the feature value corresponding to a particular daytime window from the entire week's data (the collection of after-breakfast windows from that week) may be compared to the same feature value for the corresponding daytime window calculated over a past date range (e.g., the previous week or month).

[0068] In one or more implementations, the score for a period is based on the effect size of the period, the significance of the period, the novelty of the feedback generated for the period, or a combination thereof. Additionally or alternatively, if there is a variable time window involved in the feedback (e.g., the number of days over which a consistent pattern of positive glycemic control is detected), and the duration of the time window indicates the relative "attention" of the feedback, then this duration (or a normalized version of this duration) can serve as a score or as one component of a composite score for the period.

[0069] The effect size of a period refers to the difference between the period and the other period to which it is compared. Effect sizes are calculated in various ways, such as subtracting the feature of one period from the feature of the other period, or comparing the feature of one period to a summary statistic calculated over a set of other periods (e.g., comparing the time in range after breakfast on the current day to the 90th of the time in range value calculated for each post-breakfast period on the past 14 days). For example, for the time in range feature of glucose measurements, the effect size can be calculated by subtracting the time in range of one period from the time in range of the other period. For example, if the time in range of a period on the previous day is 120 minutes and the time in range of the corresponding period on the current day is 150 minutes, the effect size is 30 minutes. Additionally or alternatively, the effect size can be calculated as a percentage improvement. For example, if the time in range of a period on the previous day is 120 minutes and the time in range of the corresponding period on the current day is 150 minutes, the effect size is 25% because 150 minutes is 25% greater than 120 minutes. Additionally or alternatively, the time in range may be identified as a percentage of a period rather than a fraction. For example, the time in range for a period yesterday may be 60% and the time in range for a corresponding period today may be 70%, thus resulting in an effect size of 10%.

[0070] The significance of a period refers to the difference between a period and the other period it is being compared to, accounting for the typical day-to-day variability of the user 102. This allows the diabetes management feedback generation system 120 to customize feedback to the typical behavior of the user 102, as well as changes in the typical behavior of the user 102 over time, rather than applying a common threshold or rule across users. For example, one user may be fairly consistent in their behavior, resulting in fairly consistent glucose levels, while another user may be less consistent in their behavior, resulting in greater fluctuations in glucose levels. Thus, smaller changes in a feature will be more noticeable to a user whose user behavior is consistent than to a user whose user behavior is inconsistent. The significance of the comparison accounts for these different behaviors.

[0071] The significance of the comparison may be generated in any of a variety of ways. For example, the significance of the comparison may be or may include a value indicating the number of standard deviations that the generated features are away from the feature mean (e.g., the mean is calculated based on the features over a period of time spanning multiple days, such as two weeks) from which the generated features are generated. Thus, the size of the standard deviation may vary from user to user or may change over time for a given user (e.g., calculated over a moving window). A larger number of standard deviations away from the mean indicates a more significant difference.

[0072] The novelty of feedback generated for a period of time refers to how frequently, i.e., how often, a particular feedback is generated for that period of time. For example, if feedback is frequently provided indicating that the period corresponding to the breakfast period has the best glucose level of the day (e.g., the period having a glucose level within the optimal range or closest to the optimal value), the novelty score for the breakfast period of the day can be lowered to avoid repeatedly providing the same feedback (which is expected to be of little interest to the user). The novelty of feedback generated for a period of time can be measured in any of a variety of different ways, such as a count of the number of times the feedback was generated (e.g., over the past two weeks or month), a value indicating how often the feedback was generated relative to other feedback, etc.

[0073] The period score 326 may be output as any of a variety of different values. In one or more implementations, the period score 326 for a period is the effect size determined by the diabetes management feature comparison module 304. Additionally or alternatively, the period score 326 for a period may be a tuple including one or more of the effect size, significance, novelty (for each possible feedback), other indication of difference between different features, etc. Additionally or alternatively, the period score 326 for a period may be a value determined by combining (e.g., a weighted average) one or more of the effect size, significance, novelty, other indication of difference between different features, etc. In such a situation, a different period score 326 may be generated for each possible feedback (e.g., because different feedbacks may have different novelty).

[0074] In one or more implementations, the duration scores 326 are provided to a normalization module 306, which adjusts the duration scores 326 arising from the different scores (e.g., effect size, significance, and novelty) to a common scale or common units (e.g., values ​​ranging between 0 and 1). The normalization module 306 outputs the normalized data as a normalized duration score 328. This normalization may be performed using any of a variety of known or proprietary techniques. It should be noted that the normalization module 306 is optional, and that in certain situations, normalization need not be performed. For example, in some situations where only a single type of score (e.g., one of effect size, significance, or novelty) is used by the diabetes management feedback generation system 120, it is not necessary to adjust the duration scores 326 to a common scale or units (although if the effect size is calculated with respect to one of several possible diabetes management features, with each feature having potentially different units, the duration scores 326 may still be adjusted to a common scale or units). As another example, if multiple types of scores (e.g., two or more of effect size, significance, or novelty) are used by the diabetes management feedback generation system 120 but already have a common scale or units, there is no need to adjust the duration score 326 to a common scale or units.

[0075] The diabetes management feedback identification module 308 receives the period score, which may be the period score 326 or the normalized period score 328, and selects feedback 330 to provide to the UI module 310. The diabetes management feedback identification module 308 applies any of a variety of different rules 332 from a rules library 334 to determine a number of feedback items to retrieve from the feedback library 122 and provide to the UI module 310. The rules library may be stored in a variety of locations, such as stored in the storage device 118.

[0076] A variety of different feedback items may be included in the feedback library 122 and provided as feedback 330, each providing feedback to the user 102. Examples of such feedback include indicating an improvement in glucose levels for the current period relative to the past few days, feedback identifying the best period of the day (e.g., the period of the day during which the glucose level was within the optimal range or closest to the optimal value (e.g., based on any one or more of the characteristics described above)), positive sustained patterns (e.g., characteristics that are met for the same period over multiple days), etc.

[0077] In one or more implementations, the feedback in the feedback library 122 is general feedback that does not need to be modified based on a user's particular characteristics or glucose values ​​(e.g., a message such as "My glucose levels after breakfast were the best today!"). Additionally or alternatively, the feedback in the feedback library 122 includes templates to which the diabetes management feedback identification module 308 adds characteristics or glucose values. For example, the feedback library 122 may include a message such as "In range for ___ nights in a row!" (underlines entered by the diabetes management feedback identification module 308). For example, if the diabetes management feedback identification module 308 determines that the user was within the desired range for three periods corresponding to sleep, the diabetes management feedback identification module 308 replaces the blank spaces with "3."

[0078] Further examples of feedback include "Overnight glucose was 70-140 mg / dL >40% of the time for 5 consecutive days", "Peak glucose after lunch was <130 mg / dL for 3 consecutive days", "Peak glucose after lunch was 22 mg / dL lower than any day in the last 7 days", "Times after dinner were 70-140 mg / dL were 18% more than any day in the last 7 days", "Times after dinner were 70-180 mg / dL were 5% more than any day today", "Peak glucose after lunch was 14 mg / dL lower than any day today", "Average glucose after dinner today was 21 mg / dL lower than any day in the last 7 days", "Times after dinner were 70-140 mg / dL were 4% more than any day today", and "Times after lunch were 70-140 mg / dL were 3% higher than any day in the last 7 days".

[0079] A variety of different rules 332 may be included in the rules library 334, with each rule 332 corresponding to one of the items of feedback in the feedback library 122. The rules may cover different characteristics and different time periods within a day or within a corresponding period across multiple days. For example, one rule may be the period of the day with the highest score (e.g., whether the glucose measurements in a particular period of the day were within a particular range or below a particular glucose level for a longer period than the glucose measurements in other periods of the day). Another rule may be whether the glucose measurements in a particular period of the day improved a threshold amount over the glucose measurements in a corresponding period of the past day or days (e.g., whether the glucose measurements were within a particular range for at least one threshold or below a particular glucose level for a longer period than the glucose measurements measured for the user during the past day or days). Another rule may be whether the glucose measurements for a particular period of the day were part of a sustained pattern of good glucose measurements (e.g., whether the glucose measurements for the current day and those taken over a period of the past day or days (e.g., 2-4 weeks) were within a particular range or below a particular glucose level for the current day and the past day or days, respectively).

[0080] The rules 332 may include references to various thresholds, such as exceeding or not exceeding the threshold. In one or more implementations, the user-specific diabetes management characteristic threshold determination module 312 generates a threshold 336 based on the characteristics 322. This is a user-specific diabetes management characteristic threshold based on the distribution of diabetes management characteristics observed over the user's 102 historical time window (e.g., the threshold may be set to the 75th highest number of diabetes management characteristics observed in a given daily period over the previous month). This threshold 336 is then used by the diabetes management feedback identification module 308 as a threshold in the various rules 332 (e.g., to identify the number of consecutive days that meet or exceed the threshold (e.g., a sustained positive pattern)). Deriving the threshold 336 from the user's own historical data allows the threshold 336 to represent a level of glycemic control that is "good" relative to the typical levels observed for the user, but still achievable. The choice of summary statistic used to set the threshold (e.g., 60th vs. 80th) is a parameter that allows control of the balance between the "noticeability" of a positive sustained pattern and its achievability for that particular patient. The choice of summary statistic used to set the threshold may be made by the user 102, a medical professional, an administrator or designer of the glucose monitoring application 116 or glucose monitoring platform 110, etc. The threshold 336 can also accommodate intra-user changes in glycemic control over time, since the historical time window used to derive the threshold 336 may be updated as it progresses in time.

[0081] In one or more implementations, the diabetes management feedback identification module 308 uses a rule 332 to indicate that a rule is satisfied if a score corresponding to a characteristic for a period of time exceeds a threshold, and the feedback corresponding to the rule is selected as the feedback 330. This causes the diabetes management feedback identification module 308 to select multiple items of feedback 330 to be displayed or otherwise presented by the UI module 310.

[0082] Additionally or alternatively, in a situation where multiple rules are satisfied, the diabetes management feedback identification module 308 selects one of the satisfied rules and selects feedback corresponding to the selected rule as feedback 330. The diabetes management feedback identification module 308 may select one of the multiple rules in various manners, such as randomly or pseudo-randomly selecting one of the multiple satisfied rules. Additionally or alternatively, the diabetes management feedback identification module 308 may prioritize the multiple rules and select one of the multiple rules having the highest priority. For example, the rule having the highest priority is selected.

[0083] The diabetes management feedback identification module 308 optionally uses various criteria to determine which of the multiple satisfied rules to select. These criteria may be based on various factors, such as how recently the rule was satisfied, the rank or priority of the rule, the category of the rule, the number of consecutive days the rule was satisfied, etc. For example, a less recently satisfied rule is selected over a more recently satisfied rule. For example, this may allow different feedback (corresponding to different rules) to be selected as feedback 330, so that feedback is not repeated too frequently.

[0084] As another example, the rules may correspond to different categories, such as an improvement category (e.g., rules corresponding to improvement in glucose measurements for a period over the past day or more), a best category (e.g., rules identifying periods of a day during which glucose measurements were best (e.g., within an optimal range or closest to an optimal value), a persistence pattern category (e.g., rules identifying positive persistence patterns), etc. Rules corresponding to a particular category may be selected in preference to rules corresponding to other categories. For example, rules corresponding to the persistence pattern category may be selected in preference to rules corresponding to the improvement category, e.g., to avoid displaying feedback that repeats the same improvement too frequently.

[0085] As another example, rules designated (e.g., by a developer or designer of the diabetes management feedback identification module 308) as more urgent or safety relevant are selected in preference to rules that are less urgent or safety relevant. For example, this may allow feedback corresponding to urgent or safety related features (e.g., not staying in range or exceeding a threshold glucose level) to be selected in preference to other non-urgent or non-safety related features to display or otherwise present more important diabetes management feedback to the user.

[0086] As another example, rules designated (e.g., by the user 102) to be a higher priority are selected over rules designated (e.g., by the user 102) to be a lower priority. For example, this may allow feedback corresponding to rules that are of greater interest to the user to be displayed or otherwise presented as opposed to feedback corresponding to rules that are of less interest to the user.

[0087] As another example, rules that have met at least the threshold number of consecutive days are selected in preference to rules that have not met at least the threshold number of consecutive days. For example, this may allow a positive trend or pattern (e.g., peak glucose remaining below 200 mg / dL during the post-lunch period) over a number of days to be displayed or otherwise presented to the user, encouraging the user to continue the trend or pattern.

[0088] In one or more implementations, the feedback 330 is general in nature, informing the user 102 of a particular period during which glucose management was good without specifying a particular value indicating the amount of improvement (e.g., indicating "After dinner glucose is great!" rather than "Today's after dinner glucose was lower than usual"). In such a situation, the diabetes management feedback identification module 308 selects the feedback 330 corresponding to the period during which more than one rule was satisfied. For example, assume that for the current day, both a first period and a second period satisfied the time within range rule, and the first period did not satisfy the coefficient of variation rule for glucose measurements within the period, but the second period did satisfy the coefficient of variation rule for glucose measurements within the period. In this situation, the diabetes management feedback identification module 308 selects the feedback 330 corresponding to the second period rather than the first period, because more rules were satisfied for the second period than for the third period. As another example, assume that for the current day, both a first time period and a second time period satisfy the time within range rule, and the first time period does not satisfy the steps during the time period rule, but the second time period does satisfy the steps during the time period rule. In this situation, the diabetes management feedback identification module 308 selects the feedback 330 corresponding to the second time period rather than the first time period because the second time period satisfies more rules than the third time period.

[0089] The UI module 310 receives the feedback 330 and causes the feedback 330 to be displayed or otherwise presented (e.g., at the computing device 106). This display or other presentation may take various forms, such as a static text display, a graphic or video display, an audio presentation, combinations thereof, etc. In one or more implementations, different types or categories of feedback are displayed or otherwise presented in different ways. For example, feedback categories may include categories of improvement in glucose readings for a given period over the past day or days, categories of periods of the day that had the best glucose readings (e.g., periods that had glucose readings that were within the optimal range or closest to the optimal value), and categories of positive persistence patterns. Feedback corresponding to these different categories may be displayed using different colors, different icons, etc.

[0090] In one or more implementations, the feedback 330 is ordered based on priority. For example, if multiple rules are satisfied, the diabetes management feedback identification module 308 selects the highest priority feedback as the feedback 330 first. A user input can be received requesting additional feedback of lower priority desired by the user 102, and the diabetes management feedback identification module 308 provides the user requested lower priority feedback. For example, this allows for the presentation of the highest priority feedback, then in response to the user request for additional feedback, the presentation of the second highest priority feedback, then in response to the additional user request for additional feedback, the presentation of the third highest priority feedback, and so on.

[0091] In one or more implementations, the diabetes management feedback identification module 308 determines whether there is an improvement in the user's glucose level for a current period relative to the past day or days (wherein the past days are optionally the same type of day), such as the previous week or two weeks ago, based on the at least one feature. If the diabetes management feedback identification module 308 determines that a rule indicates that an improvement for a period meets a threshold (e.g., at least a certain percentage improvement), the diabetes management feedback identification module 308 selects feedback 330 that corresponds to the rule.

[0092] FIG. 4 illustrates an example 400 that provides feedback indicating an improvement in at least one feature for a period of time. The improvement in example 400 is an improvement in the current period of time relative to the corresponding period of each of the immediately preceding days. Example 400 illustrates a number of days (shown as June 23, 2021 - June 29, 2021), each day having a period of night (e.g., while the user is sleeping), breakfast (e.g., during and after breakfast), lunch (e.g., during and after lunch), and dinner (e.g., during and after dinner). A period score is generated for period 402 (dinner) for the current day (June 29) indicating a difference between one or more features of period 402 and the same one or more features of a corresponding period (dinner) from June 23 to June 28 of the previous multiple days. In the illustrated example, a comparison of these periods and the generated scores indicates that the user's glucose level during period 402 is lower than the user's typical amount during the previous multiple days from June 23 to June 28, satisfying rule 332. This determination may be made in a variety of ways, such as by determining how many standard deviations the glucose levels for time period 402 on June 29th were from the average generated for the corresponding time period from June 23rd to June 28th.

[0093] The diabetes management feedback identification module 308 identifies the feedback 404 and the UI module 310 causes the feedback 404 to be displayed. In the illustrated example, the feedback 404 is a thoughtful insight informing the user that their after dinner glucose was lower than normal today. This draws the user's attention to improved glucose levels over a period of time and allows the user to review the changes they made to their dinner on June 29 versus the past few days and continue those changes for better diabetes management.

[0094] FIG. 5 illustrates an example 500 that provides feedback indicating the best period during a day. Example 500 illustrates a single day (shown as June 29, 2021) that has periods of night (e.g., while the user is sleeping), breakfast (e.g., during and after breakfast), lunch (e.g., during and after lunch), and dinner (e.g., during and after dinner). A period score is generated for period 502 (breakfast) on the current day (June 29) that indicates a difference between one or more characteristics of period 502 and one or more characteristics of three other periods on June 29. In the illustrated example, a comparison of these periods and the generated scores indicates that the user's glucose level during period 502 was better than any other period on June 29, satisfying rule 332. This determination can be made in a variety of ways, such as determining that the user's glucose level was within a particular range for longer than any other period on June 29, determining that the user's glucose level remained below a threshold level during period 502 but not during other periods on June 29.

[0095] The diabetes management feedback identification module 308 identifies the feedback 504 and the UI module 310 causes the feedback 504 to be displayed. In the illustrated example, the feedback 504 is a resonant insight informing the user that their glucose after dinner was better than any other period today. This draws the user's attention to the improved glucose levels over a period of time and allows the user to consider the foods consumed during breakfast versus the foods consumed during other periods on June 29th and use that knowledge to modify the foods consumed during other periods for better diabetes management.

[0096] FIG. 6 illustrates an example 600 that provides feedback indicative of a positive persistence pattern. The positive persistence pattern in example 600 is a pattern of corresponding periods over consecutive days of the same type (e.g., weekdays). Example 600 illustrates a number of days (shown as June 21, 2021 - June 25, 2021, June 28, 2021, and June 29, 2021), each having a period of night (e.g., while the user is sleeping), breakfast (e.g., during and after breakfast), lunch (e.g., during and after lunch), and dinner (e.g., during and after dinner). A period score is generated for period 602 (lunch) on the current day (June 29) and indicates the difference between one or more features of period 602 and the same one or more features of the corresponding period (lunch) of each of the past few days, June 21 - June 25, and June 28. In the illustrated example, a comparison of these periods and the generated scores indicates that the user's glucose levels during period 602 and the corresponding periods of June 24, June 25, and June 28 are within a particular range and satisfy the rule.

[0097] The diabetes management feedback identification module 308 identifies the feedback 604 and the UI module 310 causes the feedback 604 to be displayed. In the illustrated example, the feedback 604 is a thoughtful insight informing the user that the user's overnight glucose was within the desired range after lunch for four consecutive weekdays. This draws the user's attention to a sustained pattern of staying within the desired range and allows the user to consider the types of foods consumed for lunch over the past few weekdays and continue to consume similar types of foods for better diabetes management.

[0098] Returning to FIG. 3, the description is now given with reference to multiple periods within a time range that is a day. Additionally or alternatively, different periods or time ranges can be used. For example, each period can be a full day and the time range can be a week, a month, multiple months, a year, etc. As another example, each period can be a full week and the time range can be a month, multiple months, or a full year.

[0099] Discussion is also made herein regarding positive comparisons that indicate good diabetes management and display or otherwise present feedback (e.g., inspirational insights) to motivate the user. Similarly, negative comparisons may be made that indicate poor diabetes management and display or otherwise present feedback (e.g., warnings or adverse effects) to the user to encourage better diabetes management by the user. Negative comparisons are similar to the techniques discussed herein, but the rules applied to the features are different. For example, feedback may be displayed indicating the period with the worst glucose level of the day (e.g., the period with the glucose level outside the optimal range or furthest from the optimal value) rather than the period with the best glucose level of the day (e.g., the period with the glucose level within the optimal range or closest to the optimal value). As another example, feedback may indicate that the time within range for a given period was 25% less than the corresponding period in the past few days. Additional features may also be included for negative comparisons. For example, for glucose measurements, the diabetes management feature determination module 302 may generate a threshold crossing feature, such as whether a particular glucose level (e.g., 400 mg / dL) was exceeded during the period.

[0100] In one or more implementations, the diabetes management feedback generation system 120 applies additional criteria to determine when to display or otherwise present negative feedback, such as a warning or adverse effect. This additional criteria may include identifying a pattern of characteristics that is met on multiple occurrences, such as a particular period being the worst glucose level of a day for multiple consecutive days, or the time in range for a given period being 25% less than the corresponding period of the previous few days for two consecutive days. This additional criteria may prevent warnings or negative effects from being displayed or otherwise presented to the user on a single bad day to avoid unnecessarily warning the user or informing the user of the negative effects for a single anomaly.

[0101] As described above, situations arise where the diabetes management feedback identification module 308 uses various criteria to determine which rule to select from among the multiple satisfied rules. In one or more implementations, a negative comparison is one of these criteria, and operates such that the rule corresponding to the period that did not satisfy the negative comparison is selected over the period that did satisfy the negative comparison. For example, assume that for the current day, both a first period and a second period satisfy the time within range rule, and the first period does not satisfy the negative comparison of the above threshold rule (e.g., did not exceed the threshold glucose level during the period), but the second period does satisfy the negative comparison of the above threshold rule (e.g., exceeded the threshold glucose level during the period). In this situation, the diabetes management feedback identification module 308 selects the rule for the first period rather than the second period. This is because there is no negative comparison satisfied for the first period.

[0102] The diabetes management feedback generation system 120 optionally takes additional actions based on the feedback 330. In one or more implementations, these actions include informing the glucose monitoring application 116 or the wearable glucose monitoring device 104 that the frequency of generating glucose readings 114 may be reduced. For example, if the diabetes management feedback generation system 120 identifies a sustained positive pattern (e.g., glucose within a certain range) for a certain period of at least a threshold number of days, the diabetes management feedback generation system 120 informs the glucose monitoring application 116 or the wearable glucose monitoring device 104 that the frequency of generating glucose readings 114 may be reduced (e.g., from every 5 minutes to every 10 minutes) to reduce the power consumed in generating the glucose readings 114.

[0103] Additionally or alternatively, these actions may include determining whether to recommend ongoing CGM use (e.g., starting a new sensor immediately after the current sensor expires) or whether it may be appropriate to discontinue CGM use and start a new sensor several days later. For example, if the diabetes management feedback generation system 120 does not identify a sustained positive pattern (e.g., glucose within a specified range) for a specified period of at least a threshold number of days, the diabetes management feedback generation system 120 may recommend (e.g., via a display or other presentation to the user) ongoing CGM use.

[0104] The feedback is also described herein with respect to being displayed or otherwise presented to the user 102. Additionally or alternatively, the feedback is communicated or otherwise delivered to others, such as a clinician (e.g., the user's doctor or nurse), a pharmacist, etc. This can help partially automate some of the manual work of reviewing raw glucose or other diabetes management data that a clinician may have to do themselves in the absence of generated feedback. Additionally or alternatively, the duration score 326 or normalized duration score 328 can be provided to the clinician, pharmacist, or others, allowing the clinician, pharmacist, or others to apply their own recommended rule set in determining the feedback to convey to the user.

[0105] Having discussed exemplary details of techniques relating to user interfaces for presenting glucose insights, we now consider some example procedures to illustrate additional aspects of these techniques.

[0106] Exemplary Procedure This section describes example procedures for implementing diabetes management feedback to improve diabetes management. Aspects of the procedures may be implemented in hardware, firmware, software, or combinations thereof. The procedures are illustrated as a set of blocks that specify operations to be performed by one or more devices, and are not necessarily limited to the order shown for performing the operations by each block.

[0107] 7 illustrates an example procedure 700 for implementing diabetes management feedback to improve diabetes management. Procedure 700 is performed by a diabetes management feedback generation system, such as diabetes management feedback generation system 120, for example.

[0108] First glucose measurements of the user for a first time period of the multiple time periods are obtained (block 702). These first glucose measurements are obtained, for example, from a glucose sensor of a continuous glucose level monitoring system, where the glucose sensor is inserted at an insertion site of the user.

[0109] One or more features are generated for the first time period (block 704), where the one or more features are generated from the first glucose measurement.

[0110] The one or more features are analyzed to determine at least one feature that satisfies the one or more rules for the first time period (block 706). The analysis may include different time periods in the same 24 hour interval as the first time period, or corresponding time periods across multiple 24 hour intervals.

[0111] At least one diabetes management feedback of the plurality of diabetes management feedbacks in the library of diabetes management feedback that corresponds to the one or more rules is identified (block 708). Different rules may correspond to different feedback, which is identified in block 708. Additionally or alternatively, different time periods may correspond to different feedback, and in block 708, feedback corresponding to a first time period is identified.

[0112] A user interface is generated that includes the identified at least one diabetes management feedback and an indication of the first time period (block 710). The identified at least one diabetes management feedback is displayed (block 712) or otherwise presented.

[0113] 8 illustrates another example procedure 800 for implementing diabetes management feedback to improve diabetes management. Procedure 800 is performed by a diabetes management feedback generation system, such as diabetes management feedback generation system 120.

[0114] First diabetes management measurements of the user for a first time period of the plurality of time periods are obtained (block 802). These first diabetes management measurements may be obtained from a glucose sensor or any of a variety of other sensors as described above (e.g., any sensor that provides data to data stream 320).

[0115] One or more features are generated for the first time period (block 804), where the one or more features are generated from the first diabetes management measurement.

[0116] The one or more features are analyzed to determine at least one feature that satisfies the one or more rules for the first time period (block 806). The analysis may include different time periods in the same 24 hour interval as the first time period, or corresponding time periods spanning multiple 24 hour intervals.

[0117] At least one diabetes management feedback of a plurality of diabetes management feedbacks in a library of diabetes management feedback that corresponds to the one or more rules is identified (block 808). Different rules may correspond to different feedbacks, which are identified in block 808. Additionally or alternatively, different time periods may correspond to different feedbacks, and in block 808, feedback corresponding to a first time period is identified.

[0118] The identified at least one diabetes management feedback is displayed (block 810) or otherwise presented. Additionally or alternatively, the identified diabetes management feedback may be communicated or otherwise presented to a clinician, pharmacist, or other healthcare provider.

[0119] Exemplary Systems and Devices 9 illustrates, generally at 900, an example system including an example computing device 902 that represents one or more computing systems and / or devices capable of implementing various techniques described herein. This is illustrated through the inclusion of diabetes management feedback generation system 120. Computing device 902 may be, for example, a service provider's server, a device associated with a client (e.g., a client device), an on-chip system, and / or any other suitable computing device or computing system.

[0120] The exemplary computing device 902 as shown includes a processing system 904, one or more computer-readable media 906, and one or more input / output (I / O) interfaces 908 communicatively coupled to each other. Although not shown, the computing device 902 may further include a system bus or other data and command transfer system coupling the various components together. The system bus may include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and / or a processor or local bus utilizing any of a variety of bus architectures. Various other examples, such as control and data lines, are also contemplated.

[0121] The processing system 904 represents functionality for performing one or more operations using hardware. Thus, the processing system 904 is illustrated as including hardware elements 910, which may be configured as a processor, functional blocks, etc. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 910 are not limited by the material from which they are formed, or the processing mechanisms employed therein. For example, a processor may be comprised of semiconductors and / or transistors (e.g., electronic integrated circuits (ICs)). In this context, processor-executable instructions may be electronically executable instructions.

[0122] The computer-readable medium 906 is illustrated as including a memory / storage component 912. The memory / storage component 912 represents memory / storage capacity associated with one or more computer-readable media. The memory / storage component 912 may include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical disks, magnetic disks, etc.). The memory / storage component 912 may include fixed media (e.g., RAM, ROM, fixed hard drives, etc.) as well as removable media (e.g., flash memory, removable hard drives, optical disks, etc.). The computer-readable medium 906 may be configured in a variety of other ways, as further described below.

[0123] Input / output interface 908 represents functionality that allows a user to input commands and information into computing device 902 and that allows information to be presented to a user and / or other components or devices using various input / output devices. Examples of input devices include keyboards, cursor control devices (e.g., a mouse), microphones, scanners, touch capabilities (e.g., capacitive or other sensors configured to detect physical contact), cameras (e.g., employing visible wavelengths or non-visible wavelengths such as infrared frequencies to recognize movements as non-touch gestures), and the like. Examples of output devices include display devices (e.g., a monitor or projector), speakers, printers, network cards, haptic response devices, and the like. Thus, computing device 902 can be configured in a variety of ways to support user interaction, as described further below.

[0124] Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, etc. that perform particular tasks or implement particular abstract data types. As used herein, the terms "module," "function," and "component" generally refer to software, firmware, hardware, or combinations thereof. Aspects of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

[0125] An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. Computer-readable media may include a variety of media that may be accessed by computing device 902. By way of example, computer-readable media may include "computer-readable storage media" and "computer-readable signal media."

[0126] A "computer-readable storage medium" may refer to a medium and / or device that allows for persistent and / or non-transient storage of information, as opposed to merely a signal transmission, carrier wave, or signal itself. Thus, a computer-readable storage medium refers to a non-signal-bearing medium. A computer-readable storage medium includes hardware, such as volatile and non-volatile, removable and non-removable media, and / or storage devices implemented in a manner or technology suitable for storage of information, such as computer-readable instructions, data structures, program modules, logic elements / circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, hard disk, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or other storage device, tangible media, or any article suitable for storing the desired information and that can be accessed by a computer.

[0127] A "computer-readable signal medium" may refer to a signal-bearing medium configured to transmit instructions to the hardware of the computing device 902, such as via a network. Signal media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, data signal, or other transport mechanism. Signal media also includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, communication media includes wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0128] As previously described, the hardware elements 910 and computer-readable medium 906 represent modules, programmable device logic, and / or fixed device logic implemented in hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein, such as to execute one or more instructions. The hardware may include integrated circuits or components of on-chip systems, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), and other implementations in silicon or other hardware. In this context, the hardware may operate as a processing device that executes program tasks defined by instructions and / or logic embodied by the hardware, as well as hardware utilized to store instructions for execution, such as computer-readable storage media previously described.

[0129] Combinations of the foregoing may be used to implement the various techniques described herein. Thus, software, hardware, or executable modules may be implemented as one or more instructions and / or logic embodied on some form of computer-readable storage medium and / or by one or more hardware elements 910. Computing device 902 may be configured to implement specific instructions and / or functions corresponding to the software and / or hardware modules. Thus, implementation of modules executable as software by computing device 902 may be achieved at least partially in hardware, for example, through use of computer-readable storage medium and / or hardware elements 910 of processing system 904. The instructions and / or functions may be executable / operable by one or more articles of manufacture (e.g., one or more computing devices 902 and / or processing system 904) to implement the techniques, modules, and examples described herein.

[0130] The techniques described herein may be supported by various configurations of computing device 902 and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented in whole or in part through the use of a distributed system, such as on a "cloud" 914 via platform 916, as described below.

[0131] The cloud 914 includes and / or represents a platform 916 for resources 918. The platform 916 abstracts the underlying functionality of the hardware (e.g., servers) and software resources of the cloud 914. The resources 918 may include applications and / or data available while computer processing is running on a server remote from the computing device 902. The resources 918 may also include services provided over the Internet and / or over a subscriber network, such as a cellular network or a Wi-Fi network.

[0132] The platform 916 can abstract resources and functionality for connecting the computing device 902 with other computing devices. The platform 916 can also serve to abstract the scaling of resources to provide a level of scale corresponding to the demand faced by the resources 918 implemented via the platform 916. Thus, in an embodiment of interconnected devices, implementations of the functionality described herein can be distributed throughout the system 900. For example, the functionality can be performed in part on the computing device 902 as well as via the platform 916 that abstracts the functionality of the cloud 914.

[0133] In some aspects, the techniques described herein relate to a method implemented in a diabetes management monitoring system, the method including obtaining a first diabetes management measurement from a sensor of the diabetes management monitoring system, the first diabetes management measurement being measured for a user during a first period of a plurality of periods of a current day; generating one or more features for the first period of the current day from the first diabetes management measurement; analyzing the one or more features to determine at least one feature for the first period of the current day that satisfies one or more rules; identifying at least one diabetes management feedback from a plurality of diabetes management feedbacks in a library of diabetes management feedback that corresponds to the one or more rules that have been satisfied; and displaying the identified at least one diabetes management feedback.

[0134] In some aspects, techniques described herein relate to a method, wherein each of a plurality of time periods within a day includes a different time period within the day.

[0135] In some aspects, techniques described herein relate to a method, where the multiple periods of the day include an evening period, a breakfast period, a lunch period, and a dinner period.

[0136] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes comparing the first diabetes control measurement to diabetes control measurements measured for the user during one or more additional periods of the day to determine whether the first diabetes control measurement was within a particular range or below a particular level for a longer period of time than the diabetes control measurements measured for the user during the one or more additional periods of time, and determining that the first diabetes control measurement satisfies one or more rules in response to determining that the first diabetes control measurement was within a particular range or below a particular level for a longer period of time than the diabetes control measurements measured for the user during the one or more additional periods of time, wherein the identified at least one diabetes management feedback includes an indication that the user's diabetes management during the day was best during the first period of time.

[0137] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes comparing the first diabetes control measurement to diabetes control measurements measured for the user during the past one or more days to determine whether the first diabetes control measurement was within a particular range or below a particular level for at least a threshold time period longer than the diabetes control measurements measured for the user during the past one or more days, and determining that the first diabetes control measurement satisfies one or more rules in response to determining that the first diabetes control measurement was within a particular range or below a particular level for at least a threshold time period longer than the diabetes control measurements measured for the user during the past one or more days, wherein the identified at least one diabetes control feedback includes an indication that the user's diabetes management for the current period was better than the user's diabetes management for the past one or more days.

[0138] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes determining whether the first diabetes control measurement and the diabetes control measurements measured for the user during a period of time in the past one or more days were within a particular range or below a particular level for each of the current day and the past one or more days, determining that the first diabetes control measurement satisfies one or more rules in response to determining that the first diabetes control measurement and the diabetes control measurements measured for the user during a period of time in the past one or more days were within a particular range or below a particular level for each of the current day and the past one or more days, and determining a total number of days by counting each of the current day and the past one or more days, wherein the identified at least one diabetes control feedback includes an indication that the user's diabetes control level for the period of time was within a particular range for the total number of days.

[0139] In some aspects, the techniques described herein relate to a method, where obtaining includes obtaining first activity data from an activity tracker worn by a user, and generating includes generating one or more features for a first time period from both the first diabetes management measurement and the first activity data.

[0140] In some aspects, the techniques described herein relate to a method, wherein the identifying includes identifying two or more rules satisfied by the first diabetes management measure, the method further including determining a priority for each of the two or more rules, and identifying as the at least one diabetes management feedback, a diabetes management feedback corresponding to one of the two or more rules having a highest priority.

[0141] In some aspects, techniques described herein relate to a device including a diabetes management monitoring system, the device including: a library of diabetes management feedback; a display device; a diabetes management characteristic determination module implemented at least partially in hardware to obtain from a sensor a first diabetes management measurement measured for a user for a first time period of a plurality of time periods of a current day; a diabetes management characteristic comparison module implemented at least partially in hardware to generate one or more characteristics for the first time period of the current day from the first diabetes management measurement and analyze the one or more characteristics to determine at least one characteristic that satisfies one or more rules for the first time period of the current day; and a reportable diabetes management feedback identification module implemented at least partially in hardware to identify at least one diabetes management feedback of the plurality of diabetes management feedbacks in the library of diabetes management feedback that corresponds to the one or more rules satisfied, generate a user interface including an indication of the identified at least one diabetes management feedback and the first time period, and display the identified at least one diabetes management feedback.

[0142] In some aspects, the techniques described herein relate to a device where each of a number of periods within a current day includes a different number of time periods during a 24-hour interval.

[0143] In some aspects, the techniques described herein relate to a device where the multiple periods of the day include an evening period, a breakfast period, a lunch period, and a dinner period.

[0144] In some aspects, the techniques described herein relate to a device, wherein the diabetes management feature comparison module is for analyzing one or more features by comparing the first diabetes management measurement to diabetes management measurements measured for the user during one or more additional periods of the day to determine whether the first diabetes management measurement was within a particular range or below a particular level for a longer period of time than the diabetes management measurements measured for the user during the one or more additional periods of time, and in response to determining that the first diabetes management measurement was within a particular range or below a particular level for a longer period of time than the diabetes management measurements measured for the user during the one or more additional periods of time, determining that the first diabetes management measurement satisfies one or more rules, and wherein the identified at least one diabetes management feedback includes an indication that the user's diabetes management during the day was best during the first period of time.

[0145] In some aspects, the techniques described herein relate to a device, wherein the diabetes feature comparison module is for analyzing one or more features by comparing the first diabetes control measurement to diabetes control measurements measured for the user during the past one or more days to determine whether the first diabetes control measurement was within a particular range or below a particular glucose level for at least a threshold time period longer than the diabetes control measurements measured for the user during the past one or more days, and in response to determining that the first diabetes control measurement was within a particular range or below a particular level for at least a threshold time period longer than the diabetes control measurements measured for the user during the past one or more days, determining that the first diabetes control measurement satisfies one or more rules, and the identified at least one diabetes management feedback includes an indication that the user's diabetes management for the current period was better than the user's diabetes management for the past one or more days.

[0146] In some aspects, the techniques described herein relate to a device, wherein the diabetes management feature comparison module is for analyzing the one or more features by determining whether the first diabetes management measurement and the diabetes management measurements measured for the user during a period of time in the past one or more days were within a specific range or below a specific level for each of the current day and the past one or more days, determining that the first diabetes management measurement satisfies one or more rules in response to determining that the first diabetes management measurement and the diabetes management measurements measured for the user during a period of time in the past one or more days were within a specific range or below a specific level for each of the current day and the past one or more days, and determining a total number of days by counting each of the current day and the past one or more days, and wherein the identified at least one diabetes management feedback includes an indication that the user's diabetes management measurement level for the period of time was within a specific range for the total number of days.

[0147] In some aspects, the techniques described herein relate to a device, wherein the diabetes management characteristic determination module is further for obtaining first activity data from an activity tracker worn by a user, and the diabetes management characteristic comparison module is for generating one or more characteristics for the first time period from both the first diabetes management measurement and the first activity data.

[0148] In some aspects, techniques described herein relate to a device, wherein the reportable diabetes management feedback identification module is for identifying two or more rules satisfied by a first diabetes management measurement, determining a priority for each of the two or more rules, and identifying as the identified at least one diabetes management feedback a diabetes management feedback corresponding to one of the two or more rules having a highest priority.

[0149] In some aspects, the techniques described herein relate to a device including a processor; a library storing a plurality of diabetes management feedbacks; a display device; and a computer-readable storage medium storing a plurality of instructions of an application that, in response to execution by the processor, causes the processor to obtain from a sensor a first diabetes management measurement measured for the user during a first period of a plurality of periods of the current day; generate one or more features from the first diabetes management measurement for the first period of the current day; analyze the one or more features to determine at least one feature that satisfies one or more rules for the first period of the current day; identify at least one diabetes management feedback from the plurality of diabetes management feedbacks in the library of diabetes management feedback that corresponds to the period of the current day; and display the identified at least one diabetes management feedback.

[0150] In some aspects, the techniques described herein relate to a computing device, where each of a number of periods within a current day includes a different number of time periods during a 24-hour interval.

[0151] In some aspects, the techniques described herein relate to a computing device, where the multiple periods of the day include an evening period, a breakfast period, a lunch period, an exercise period, and a dinner period.

[0152] In some aspects, the techniques described herein relate to a computing device, where obtaining a first diabetes management measurement further includes obtaining first activity data from an activity tracker worn by a user, and generating one or more features includes generating one or more features for a first time period from both the first diabetes management measurement and the first activity data.

[0153] In some aspects, techniques described herein relate to a method implemented in a continuous glucose level monitoring system, the method including obtaining a first glucose measurement value measured for a user during a first period of a plurality of periods of a day from a glucose sensor of the continuous glucose level monitoring system, the glucose sensor being inserted at an insertion site of the user; generating one or more features from the first diabetes management measurement value for the first period of the day; analyzing the one or more features to determine at least one feature that satisfies one or more rules for the first period of the day; identifying at least one diabetes management feedback value from a plurality of diabetes management feedback values ​​in a library of diabetes management feedback values ​​that corresponds to the one or more rules that have been satisfied; generating a user interface including an indication of the identified at least one diabetes management feedback value and the first period of the day; and displaying the identified at least one diabetes management feedback value.

[0154] In some aspects, techniques described herein relate to a method, wherein each of a plurality of time periods within a day includes a different time period within the day.

[0155] In some aspects, techniques described herein relate to a method, where the multiple periods of the day include an evening period, a breakfast period, a lunch period, and a dinner period.

[0156] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes comparing the first glucose measurement to glucose measurements measured for the user during one or more additional periods on the day to determine whether the first glucose measurement was within a particular range or below a particular glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional periods of time, and determining that the first glucose measurement satisfies one or more rules in response to determining that the first glucose measurement was within a particular range or below a particular glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional periods of time, wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level during the day was best during the first period of time.

[0157] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes comparing the first glucose measurement to glucose values ​​measured for the user during the past one or more days to determine whether the first glucose measurement was within a particular range or below a particular glucose level for at least a threshold time period longer than the glucose measurements measured for the user during the past one or more days, and determining that the first diabetes management measurement satisfies one or more rules in response to determining that the first glucose measurement was within a particular range or below a particular glucose level for at least a threshold time period longer than the glucose measurements measured for the user during the past one or more days, wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level for the current day period was better than the user's glucose level for the past one or more days.

[0158] In some aspects, the techniques described herein relate to a method, wherein the analyzing includes determining whether the first glucose measurement and glucose measurements measured for the user during a period of the past one or more days were within a specific range or below a specific glucose level for each of the current day and the past one or more days, determining that the first glucose measurement satisfies one or more rules in response to determining that the first glucose measurement and glucose measurements measured for the user during a period of the past one or more days were within a specific range or below a specific glucose level for each of the current day and the past one or more days, and determining a total number of days by counting each of the current day and the past one or more days, wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level for the period of time was within a specific range for the total number of days.

[0159] In some aspects, the techniques described herein relate to a method, where obtaining includes obtaining first activity data from an activity tracker worn by a user, and generating includes generating one or more features for the first time period from both the first glucose measurement and the first activity data.

[0160] In some aspects, the techniques described herein relate to a method, wherein the identifying includes identifying two or more rules satisfied by the first glucose measurement value, the method further including determining a priority for each of the two or more rules, and identifying as the at least one diabetes management feedback, a diabetes management feedback corresponding to one of the two or more rules having a highest priority.

[0161] In some aspects, techniques described herein relate to a device including a continuous glucose level monitoring system, the device including: a library of diabetes management feedback; a display device; a diabetes management feature determination module implemented at least partially in hardware to obtain a first glucose measurement measured for a user during a first period of a plurality of periods of a current day from a glucose sensor, the glucose sensor being inserted at an insertion site of the user; a diabetes management feature comparison module implemented at least partially in hardware to generate one or more features for the first period of the current day from the first glucose measurement and analyze the one or more features to determine at least one feature that satisfies one or more rules for the first period of the current day; and a reportable diabetes management feature comparison module implemented at least partially in hardware to identify at least one diabetes management feedback of the plurality of diabetes management feedbacks in the library of diabetes management feedback that corresponds to the one or more rules satisfied, generate a user interface including an indication of the identified at least one diabetes management feedback and the first period of time, and display the identified at least one diabetes management feedback.

[0162] In some aspects, the techniques described herein relate to a device where each of a number of periods within a current day includes a different number of time periods during a 24-hour interval.

[0163] In some aspects, the techniques described herein relate to a device where the multiple periods of the day include an evening period, a breakfast period, a lunch period, and a dinner period.

[0164] In some aspects, the techniques described herein relate to a device, wherein the diabetes management feature comparison module is for analyzing one or more features by comparing the first glucose measurement to glucose measurements measured for the user during one or more additional periods of the day to determine whether the first glucose measurement was within a particular range or below a particular glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional periods of time, and in response to determining that the first glucose measurement was within a particular range or below a particular glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional periods of time, determining that the first glucose measurement satisfies one or more rules, and wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level during the day was best during the first period of time.

[0165] In some aspects, the techniques described herein relate to a device, wherein the diabetes management feature comparison module is for analyzing one or more features by comparing the first glucose measurement to glucose values ​​measured for the user during the past one or more days to determine whether the first glucose measurement was within a particular range or below a particular glucose level for at least a threshold time period longer than the glucose measurements measured for the user during the past one or more days, and in response to determining that the first glucose measurement was within a particular range or below a particular glucose level for at least a threshold time period longer than the glucose measurements measured for the user during the past one or more days, determining that the first glucose measurement satisfies one or more rules, and wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level for the current period was better than the user's glucose level for the past one or more days.

[0166] In some aspects, the techniques described herein relate to a device, wherein the diabetes management feature comparison module is for analyzing one or more features by determining whether the first glucose measurement and the glucose measurements measured for the user during a period of the past one or more days were within a specific range or below a specific glucose level for each of the current day and the past one or more days, determining that the first glucose measurement satisfies one or more rules in response to determining that the first glucose measurement and the glucose measurements measured for the user during a period of the past one or more days were within a specific range or below a specific level for each of the current day and the past one or more days, and determining a total number of days by counting each of the current day and the past one or more days, wherein the identified at least one diabetes management feedback includes an indication that the user's glucose level for the period of time was within a specific range for the total number of days.

[0167] In some aspects, the techniques described herein relate to a device, wherein the diabetes management characteristic determination module is further for obtaining first activity data from an activity tracker worn by a user, and the diabetes management characteristic comparison module is for generating one or more characteristics for the first time period from both the first glucose measurement and the first activity data.

[0168] In some aspects, techniques described herein relate to a device, wherein the reportable diabetes management feedback identification module is for identifying two or more rules satisfied by a first diabetes management measurement, determining a priority for each of the two or more rules, and identifying as the at least one diabetes management feedback a diabetes management feedback corresponding to one of the two or more rules having a highest priority.

[0169] In some aspects, the techniques described herein relate to a device including a processor; a library storing a plurality of diabetes management feedbacks; a display device; and a computer-readable storage medium storing a plurality of instructions of an application that, responsive to execution by the processor, causes the processor to: obtain a first glucose measurement from a sensor of a continuous glucose level monitoring system measured for a user during a first period of a plurality of periods of a day, where the glucose sensor is inserted at an insertion site of the user; generate one or more features from the first glucose measurement for the first period of the day, analyze the one or more features to determine whether the at least one feature satisfies one or more rules for the first period of the day; identify at least one diabetes management feedback of the plurality of diabetes management feedbacks in the library of diabetes management feedback that corresponds to the period of the day; generate the identified at least one diabetes management feedback, where the identified diabetes management feedback includes an indication of the first period of the day; and display the identified at least one diabetes management feedback.

[0170] In some aspects, the techniques described herein relate to a computing device, where each of a number of periods within a current day includes a different number of time periods during a 24-hour interval.

[0171] In some aspects, the techniques described herein relate to a computing device, where the multiple periods of the day include an evening period, a breakfast period, a lunch period, an exercise period, and a dinner period.

[0172] In some aspects, the techniques described herein relate to a computing device, where obtaining the first glucose measurement further includes obtaining first activity data from an activity tracker worn by a user, and generating the one or more features includes generating the one or more features for a first time period from both the first diabetes management measurement and the first activity data.

[0173] conclusion Although the systems and techniques have been described in language specific to structural features and / or methodological acts, it should be understood that the systems and techniques defined in the appended claims are not necessarily limited to the particular features or acts described. Rather, the particular features and acts are disclosed as exemplary forms for implementing the claimed subject matter. [Explanation of symbols]

[0174] 100 Environment 102 people 104 Wearable glucose monitoring devices 106 Computing Devices 108 User Population 110 Glucose Monitoring Platform 112 Network 114 Glucose Measurements 116 Glucose Monitoring Applications 118 Storage Devices 120 Diabetes Management Feedback Generation System 122 Feedback Library 124 User Interface 200 Examples of wearable glucose monitoring devices 202 Sensor 204 Sensor Module 206 Skin 208 Transmitter 210 Adhesive Pad 212 Attachment mechanism 302 Diabetes Management Characterization Module 304 Diabetes Management Characteristics Comparison Module 306 Normalization Module 308 Reportable Diabetes Management Feedback Identification Module 310 UI Module 312 User-specific feature threshold determination module 320 Data Stream 322 Features 324 Datastore 326 Period Score 328 Normalized Period Score 330 Feedback 332 rules 334 Rules Library 336 Threshold 900 System 902 Computing Devices 904 Processing System 906 Computer-readable medium 908 I / O Interface 910 Hardware Elements 912 Memory / Storage 914 Cloud 916 Platform 918 resources

Claims

1. 1. A method implemented in a continuous glucose level monitoring system, the method comprising: obtaining (702) a first glucose measurement measured for a user during a first period of a day from a glucose sensor of the continuous glucose level monitoring system, the glucose sensor being inserted at an insertion site for the user; generating (704) one or more features for the first time period of the day from the first glucose measurement; analyzing (706) the one or more characteristics to determine at least one characteristic that satisfies one or more rules for the first period of the current day; identifying 708 at least one diabetes management feedback of a plurality of diabetes management feedbacks in a library of diabetes management feedbacks corresponding to the one or more satisfied rules; generating (710) a user interface including the identified at least one diabetes management feedback and an indication of the first time period; and causing (712) the identified at least one diabetes management feedback to be displayed.

2. The method of claim 1 , wherein each of the multiple time periods within the current day includes a different multiple hour period within the current day.

3. The analyzing step comprises: comparing the first glucose measurement to glucose measurements measured for the user during one or more additional time periods on the day to determine whether the first glucose measurement was within a specified range or below a specified glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional time periods; determining that the first glucose measurement satisfies the one or more rules in response to determining that the first glucose measurement has been within the specified range or below a specified glucose level for a longer period of time than the glucose measurements measured for the user during the one or more additional time periods; The method of claim 1 or 2, wherein the at least one diabetes management feedback identified comprises an indication that the user's glucose level during the current day was best during the first period of time.

4. The analyzing step comprises: comparing the first glucose measurement to glucose measurements measured for the user during the past one or more days to determine whether the first glucose measurement was within a specified range or below a specified glucose level for at least a threshold period of time longer than the glucose measurements measured for the user during the past one or more days; determining that the first glucose measurement satisfies the one or more rules in response to determining that the first glucose measurement has been within the specified range or below a specified glucose level for the threshold period that is at least longer than the glucose measurements measured for the user during the past one or more days; 4. The method of claim 1, wherein the at least one diabetes management feedback identified comprises an indication that the user's glucose level for the period of the current day was better than the user's glucose level during the period of the past one or more days.

5. The analyzing step comprises: determining whether the first glucose measurement and glucose measurements taken for the user during the past one or more days were within a specified range or below a specified glucose level for the current day and the past one or more days, respectively; determining that the first glucose measurement satisfies the one or more rules in response to determining that the first glucose measurement and glucose measurements measured for the user during the time period of the past one or more days were within the specified range or below a specified glucose level for each of the current day and the past one or more days; determining a total number of days by counting each of the current day and the past one or more days; 5. The method of claim 1, wherein the at least one diabetes management feedback identified comprises an indication that the user's glucose level for the period was within the specified range for the total number of days.

6. The obtaining includes obtaining first activity data from an activity tracker worn by the user; 6. The method of claim 1, wherein the generating comprises generating the one or more features for the first time period from both the first glucose measurement and the first activity data.

7. A computing device (106), comprising: A processor (904); a library (122) for storing a plurality of diabetes management feedbacks; A display device; a computer readable storage medium (906) storing a plurality of instructions for an application; The instructions of the application, in response to execution by the processor, cause the processor to: Obtaining 802 a first diabetes management measurement from a sensor, the first measurement being taken for the user during a first period of a plurality of periods during the current day; generating 804 one or more features for the first time period of the day from the first diabetes management measurement; analyzing 806 at least one characteristic to determine whether the characteristic satisfies one or more rules for the first time period of the current day; identifying 808 at least one diabetes management feedback among a plurality of diabetes management feedback in a library of diabetes management feedback corresponding to the period of the current day; and displaying (810) the identified at least one diabetes management feedback.

8. The computing device of claim 7 , wherein each of the multiple time periods within the current day includes a different multiple hour period during a 24 hour interval.

9. The computing device of claim 7 or 8, wherein the multiple periods within the day include an evening period, a breakfast period, a lunch period, an exercise period, and a dinner period.

10. obtaining the first diabetes management measurement further comprises obtaining first activity data from an activity tracker worn by the user; 10. The computing device of claim 7, wherein generating the one or more features comprises generating the one or more features for the first time period from both the first diabetes management measurement and the first activity data.

Citation Information

Patent Citations

  • System and method for data analytics and visualization

    US20160098848A1

  • Presenting insulin therapy insights that include pre-generated content at an electronic device and related systems, and methods

    US20190381243A1