User Interface for Presenting Glucose Insights

Abstract

A user interface for presenting glucose insights is utilized. The glucose monitoring application is configured to process the glucose measurements to determine one or more glucose insights, for example, about the user's glucose. The glucose measurements can be obtained, for example, from a glucose monitoring device that collects the user's glucose measurements at predetermined intervals, for example, every five minutes. The glucose monitoring application configures the user interface to present one or more visual elements representing the one or more glucose insights based on the configuration data. For example, the glucose monitoring application may configure the user interface to include a visual element in the form of a color area representing whether the user's current glucose measurement (e.g., the most recent glucose measurement obtained from the glucose monitoring device) is below a glucose range, within a glucose range, or above a glucose range.

Description

[Technical field]

[0001] (Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 131,721, filed December 29, 2020, and entitled “User Interfaces for Glucose Insight Presentation,” 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 symptoms 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 it involves monitoring and sometimes adjusting food and activity to control a person's blood sugar, e.g., to reduce the wild fluctuations in a person's glucose and / or to lower a person's glucose overall.

[0003] However, many conventional glucose monitoring applications utilize complex and confusing user interfaces that provide glucose information in a manner that is difficult for users to understand, 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 are unable to affect 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 user interface for presenting glucose insights is utilized. A glucose monitoring application is configured to process glucose measurements to determine one or more glucose insights, for example, about a user's glucose. The glucose measurements may be obtained, for example, from a glucose monitoring device that collects the user's glucose measurements at predetermined intervals, for example, every five minutes. The glucose monitoring application configures the user interface to present one or more visual elements representing the one or more glucose insights based on configuration data. For example, the glucose monitoring application may configure the user interface to include a visual element in the form of a color area representing whether the user's current glucose measurement (e.g., the most recent glucose measurement obtained from the glucose monitoring device) is below a glucose range, within a glucose range, or above a glucose range.

[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.

[0007] [Figure 1] 1 illustrates an environment in an example implementation operable to employ the techniques described herein. [Diagram 2] 2 illustrates an example of the wearable glucose monitoring device of FIG. 1 in more detail. [Diagram 3] FIG. 1 illustrates one embodiment of a system in which the glucose monitoring application utilizes a user interface configuration module and a glucose insight engine to configure a user interface for display. [Figure 4] 1 illustrates an example implementation of a user interface that displays a glucose graph that plots the values ​​of a user's glucose measurements over time. [Diagram 5] 1 illustrates an example implementation of a user interface that displays visual elements representing glucose insights determined for a user. [Figure 6] 1 illustrates an example implementation of a user interface that displays visual elements representative of glucose insight determined for a user and displays information supplementing the glucose insight. [Figure 7] 1 illustrates an example of an implementation of a user interface that displays a first visual element representing a first glucose insight and also displays a second visual element representing a second glucose insight. [Figure 8] 10 illustrates another example of an implementation of a user interface that displays a first visual element representing a first glucose insight and a second visual element representing a different glucose insight than the second visual element of FIG. [Figure 9] 10 illustrates another example of an implementation of a user interface that displays a first visual element representing a first glucose insight and a second visual element representing another, different glucose insight than the second visual element of FIGS. 7 and 8. [Figure 10] 1 illustrates an example implementation of a user interface that displays first and second visual elements representing first and second glucose insights, respectively, and also displays a glucose count. [Figure 11] FIG. 1 illustrates an example implementation of a user interface that displays first and second visual elements representing first and second glucose insights, respectively, and also displays a glucose count and a glucose graph that plots the values ​​of the user's glucose measurements over time. [Figure 12] 13 illustrates another example implementation of a user interface that displays visual elements representative of glucose insights determined for a user. [Figure 13]13 illustrates a procedure in one example implementation in which a user interface is configured to present visual elements representing glucose insights based on configuration data. [Figure 14] 13 illustrates a procedure in another example implementation in which the user interface is configured to present visual elements representing different glucose insights over time based on configuration data. [Figure 15] To implement embodiments of the techniques described herein, an example of a system is shown that includes various components of an exemplary device that may be implemented as any type of computing device as described and / or utilized with reference to FIGS. 1-14. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] overview Conventional glucose monitoring applications may display complex and confusing user interfaces that may include, for example, glucose graphs that plot a user's glucose measurements over time. In some cases, users, particularly those who have only recently begun monitoring their glucose, may be confused as to what the glucose measurements plotted over time mean. As a result, such users may not be able to derive insights from the data and thus be unable to influence the user's behavior to achieve health goals, e.g., glucose-based goals.

[0009] To overcome these problems, a user interface for presenting glucose insights is described. A glucose monitoring application implemented in a computing device, such as a smartphone or smartwatch, is configured to obtain glucose measurements from a glucose monitoring device that collects glucose measurements of a user. In some cases, for example, the glucose monitoring device is a wearable glucose monitoring device that collects glucose measurements from a user in real time and at predetermined intervals, for example, every 5 minutes. The glucose monitoring application processes the glucose measurements to determine, for example, one or more glucose insights regarding the user's glucose. The glucose insights may include, by way of example and not limitation, whether a current glucose measurement is below a glucose range, within a glucose range, or above a glucose range, a trend of the glucose measurement over a period of time (e.g., whether the value of the glucose measurement is increasing, decreasing, or constant over the period of time), or a rate of change of the glucose measurement over a period of time (e.g., how quickly the value of the glucose measurement is increasing or decreasing). In particular, the glucose insights may be based on various other data in addition to the glucose measurement without departing from the spirit or scope of the described techniques. By way of example and not limitation, glucose insights can be determined based on data describing other physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow velocity, etc.), fitness or activity (e.g., steps, activity type, performance, etc.), health status, medication regimens and / or medications taken, diet, stress, sleep, restorative activities (e.g., meditation, massage), and the like.

[0010] According to the described techniques, the glucose monitoring application configures a user interface to present one or more visual elements representing one or more determined glucose insights. This can include, for example, determining which glucose insights to present in the user interface as well as how to present the selected glucose insights to the user. In some cases, for example, the user interface is configured to present a limited number of visual elements representing a limited number of glucose insights (e.g., one insight or two insights) while preventing the display of other information, for example, without displaying a glucose graph or without displaying a number corresponding to the user's current glucose level.

[0011] As described throughout, the visual elements are configured to visually represent glucose insights, such as through color regions, symbols, shapes, or other visual elements. For example, instead of presenting a glucose graph with numbers indicating glucose measurements, a glucose monitoring application may present a visual element indicating that a user's glucose is within a glucose range, such as by presenting a green color region within the user interface indicating that the user is within the glucose range. As another example, a glucose monitoring application may present a shape representing glucose insights, such as a trend of glucose measurements over time or a rate of change of glucose measurements over a period of time. Compared to conventional approaches, this improved user interface presents glucose insights that are important to the user and that the user can easily understand (e.g., a green color region means that one's glucose is good), while limiting the display of information (e.g., a glucose graph) that the user may not yet understand.

[0012] To configure the user interface, the glucose monitoring application can utilize configuration data that maps glucose insights to different visual elements and controls which glucose insights are presented at a given time for a particular user and how those insights are presented, e.g., which one or more visual elements to incorporate into the configured user interface based on one or more determined glucose insights. Broadly speaking, the configuration data can specify which visual elements should be used for a particular glucose insight. The configuration data can also include various user-specified preferences. For example, the glucose monitoring application can receive user input specifying that the user interface is to present only one insight at a time. Additionally, the user preferences maintained in the configuration data may be based on “implicit” and / or “explicit” user feedback.

[0013] In addition to user preferences, the configuration data may include rules that define a progression of insights to present to the user over time such that initially the user interface is configured to present one insight at a time via each visual element. However, after one or more criteria are met, the rules may allow the user interface to be configured to simultaneously present two insights of different types via each visual element. Such a progression may have several "reveals" that allow more and / or different types of insights to be included in the user interface with each reveal. Presenting a different number of insights via the user interface over time may educate the user about their glucose and the impact of their actions on their glucose. Thus, it should be understood that the insights presented in the configured user interface, as well as the manner in which the insights are presented using the visual elements, may change over time based on the configuration data.

[0014] By presenting visual elements to represent glucose insights, the improved user interface described herein provides information that a user can easily understand at a glance. If the visual elements have a color that indicates, for example, that the user's most recent glucose reading is within a desired range, the user can understand this insight at a glance from the user interface. This is in contrast to having to focus on a glucose graph, find a representation of the most recent glucose reading, and determine whether the location of the representation is within an area of ​​the graph that corresponds to the desired range. Configuring a user interface to represent glucose insights with visual elements may be particularly advantageous on mobile devices such as smart watches, where screen space for displaying information may be limited and input for obtaining detailed information may be limited.

[0015] Furthermore, by configuring the user interface to display meaningful insights in a manner that is easy for the user to grasp, while reducing the presentation of information that may be difficult for the user to understand (e.g., glucose graphs), the user is able to better understand and focus on the limited number of glucose insights (e.g., time in range) generated by the glucose monitoring application. This allows the user to better understand their glucose insights, leading to meaningful changes for the user to improve their glucose and long-term health. Furthermore, the configuration data may tailor the insights presented to the user over time to improve the user's understanding of glucose. Thus, the improved user interface improves the user's consistency in using the glucose monitoring application, resulting in improved glucose control and longer-lasting health benefits for the user.

[0016] The following description first describes an example environment in which the techniques described herein can be used. Then, implementation details and example procedures that can be performed in the example environment, as well as in other environments, are described. The execution of the example procedures is not limited to the example environment, and the example environment is not limited to the execution of the example procedures.

[0017] Example environment 1 illustrates an environment 100 in an example implementation operable to employ a user interface for presenting glucose insights as described herein. The illustrated environment 100 includes a person 102 who is shown 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 connected, including via a network 112.

[0018] 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., Bluetooth low energy link), near field communication (NFC), 5G, etc.

[0019] In accordance with the described techniques, a wearable glucose monitoring device 104 is configured to provide measurements of glucose for a 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 glucose for the person 102 and enables the generation of glucose measurements. Throughout the illustrated environment 100 and detailed description, these measurements are referred to as glucose measurements 114.

[0020] 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 can refer to the ability of a device to produce measurements substantially continuously, such that the device can be configured to produce glucose measurements 114 at timed intervals (e.g., every hour, every 30 minutes, every 5 minutes, etc.), in response to establishing a communication connection 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), 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.

[0021] In addition, 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 these measurements are produced 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 produced) every five minutes.

[0022] Of course, the intervals at which the glucose readings 114 are communicated may vary from the above examples without departing from the spirit or scope of the described techniques. Readings may be communicated by the wearable glucose monitoring device 104 to the computing device 106 according to other criteria in accordance with the described techniques, such as based on a request from the computing device 106. In any event, the computing device 106 may at least temporarily maintain the glucose readings 114 of the person 102, for example, in a computer-readable storage medium of the computing device 106.

[0023] Although illustrated as a mobile device (e.g., a mobile phone), the computing device 106 can be configured in various manners without departing from the spirit or scope of the described techniques. By way of example and not limitation, the computing device 106 can be configured as a different type of mobile device (e.g., a wearable device or a tablet device). In one or more implementations, the computing device 106 can be configured as a dedicated device associated with the glucose monitoring platform 110, e.g., having the functionality to 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.

[0024] In addition, the computing device 106 may represent more than one device in accordance with the described techniques. In one or more situations, by way of example, the computing device 106 may correspond to both a wearable device (e.g., a smart watch) and a mobile phone. In such situations, both of these devices may be capable of performing at least some of the same operations, such as, for example, receiving glucose readings 114 from the wearable glucose monitoring device 104, communicating them over the network 112 to the glucose monitoring platform 110, and displaying information related to the glucose readings 114. Alternatively or additionally, different devices may have different capabilities that other devices do not have or that are limited to the devices specified through the computing instructions.

[0025] In a situation where the computing device 106 corresponds to a separate smart watch and a mobile phone, by way of example, the smart watch may be configured with various sensors and functionalities that measure various physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow, etc.) and the activity (e.g., steps or other movements) of the person 102. In this situation, the mobile phone may not be configured with these sensors and functionalities or may include a limited amount of that functionality, while in other situations the mobile phone may be able to provide the same functionality. Continuing with this particular situation, the mobile phone may have capabilities that the smart watch does not have, such as a camera for capturing images associated with glucose monitoring, 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 situations where the smart watch is capable of performing such calculations, the computing instructions may limit the performance of those calculations for the mobile phone in order not to burden both devices and to efficiently utilize available resources. In this regard, the computing device 106 may be configured in a different manner than discussed herein and may represent a different number of devices without departing from the spirit and scope of the described techniques.

[0026] According to the discussed techniques, the computing device 106 is configured to implement a user interface for presenting glucose insights. 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 user interface configuration module 120. Further, the glucose measurements 114 and the configuration data 122 are shown stored in the storage device 118. The storage device 118 may represent one or more databases, as well as other types of storage capable of storing the glucose measurements 114 and the configuration data 122.

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

[0028] Broadly speaking, the glucose monitoring application 116 is configured to support interactions with a user that enable customized presentation of glucose insights for the user, including, for example, obtaining glucose measurements 114 for processing (e.g., to determine glucose insights), receiving information about the user (e.g., through an onboarding process and / or user feedback), outputting alerts, communicating information to a healthcare provider, communicating information to the glucose monitoring platform 110, etc.

[0029] In one or more implementations, the glucose monitoring application 116 also leverages the resources of the glucose monitoring platform 110 in connection with a user interface for presenting glucose insights. As mentioned above, by way of example, the glucose monitoring platform 110 can be configured to store data, such as glucose measurements 114 and configuration data 122, associated with a user (e.g., person 102) and / or users of the user population 108. The glucose monitoring platform 110 can also provide updates and / or additions to the glucose monitoring application 116. Furthermore, the glucose monitoring platform 110 can train, maintain, and / or deploy algorithms (e.g., machine learning algorithms) to generate predictions in connection with determining glucose insights, such as by using the 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, the glucose monitoring platform 110 may include or otherwise have access to resources required to operate such algorithms, such as cloud storage, server devices, virtualization resources, etc. The glucose monitoring platform 110 may provide a variety of resources that the glucose monitoring application 116 leverages in connection with enabling the presentation of glucose insights via a user interface.

[0030] According to the described techniques, the glucose monitoring application 116 is configured to configure and cause output of one or more user interfaces presenting glucose insights utilizing a user interface configuration module 120. The user interface configuration module 120 can, by way of example, configure a user interface 124, and the glucose monitoring application 116 can cause the configured user interface 124 to be displayed via a display device of the computing device 106. By way of example, the user interface configuration module 120 can configure the user interface 124 based on the configuration data 122 to include one or more visual elements representing the respective glucose insights.

[0031] Broadly speaking, configuration data 122 controls which glucose insights are presented to a particular user at a given time and how those insights are presented. In one or more implementations, by way of example, configuration data 122 may include user-specified preferences. For example, glucose monitoring application 116 may receive user input specifying that user interface 124 is to present only one insight at a time. In this situation, glucose monitoring application 116 may retain this preference in configuration data 122, so that when user interface configuration module 120 configures user interface 124, the module configures the interface to present only one determined insight at a time via each visual element.

[0032] Alternatively or additionally, the configuration data 122 may include rules that define a progression of insights to present to the user over time, initially restricting the user interface configuration module 120 to configure the user interface 124 to present one insight at a time via each visual element. However, after one or more criteria are met, the rules may allow the user interface configuration module 120 to configure the user interface 124 to simultaneously present two insights of different types via each visual element. Such a progression may have several "display items" that each reveal allows more and / or different types of insights to be included within the user interface. In this manner, by presenting different numbers of insights via the user interface 124 over time, the user interface configuration module 120 may educate the user about the user's glucose and the impact of the user's actions on the user's glucose. Such progression rules may also be defined such that after one or more criteria are met, the user interface configuration module 120 may configure the user interface 124 to simultaneously present a glucose graph plotting glucose measurements 114 over time with one or more glucose insights.

[0033] As discussed above and below, various insights may be determined based on a user's glucose measurements 114 without following the techniques described. Consider the following description of FIG. 2 in the context of measuring glucose, for example, continuously, and obtaining data describing such measurements.

[0034] 2 illustrates in more detail an example implementation 200 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 that the wearable glucose monitoring device 104 may vary in implementation in various ways from the following description without departing from the spirit or scope of the described techniques. As mentioned above, by way of example, a user interface for presenting glucose insights 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.

[0035] In this example 200, the wearable glucose monitoring device 104 is shown including a sensor 202 and a sensor module 204. Here, the sensor 202 is depicted in a side view, e.g., subcutaneously inserted into the skin 206 of the person 102. The sensor module 204 is depicted 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 dashed rectangle is used for the sensor module 204 to indicate that it may be contained within the housing of the transmitter 208 or may be otherwise implemented. In this example 200, the wearable glucose monitoring device 104 further includes an adhesive pad 210 and an attachment mechanism 212.

[0036] In operation, the sensor 202, adhesive pad 210, and attachment mechanism 212 may be assembled to form an application assembly configured to be applied to the skin 206 such that the sensor 202 is inserted subcutaneously as depicted. In such a situation, the transmitter 208 may be attached to the assembly after being applied to the skin 206, such as via the attachment mechanism 212. Alternatively, the transmitter 208 may be incorporated as part of the application assembly, such that the sensor 202, adhesive pad 210, attachment mechanism 212, and transmitter 208 (with sensor module 204) may be applied to the skin 206 all at once. In one or more implementations, this application assembly is applied 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 generally painless and does not require the drawing of blood. Moreover, an automated sensor applicator generally allows the person 102 to implant the sensor 202 subcutaneously under the skin 206 without the assistance of a clinician or health care provider.

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

[0038] 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 implemented actively or passively, and these communications may be continuous (e.g., analog) or discrete (e.g., digital).

[0039] 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 or due to 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 may include a glucose sensor configured to detect an analyte in blood or interstitial fluid indicative of glucose levels using one or more measurement techniques. In one or more implementations, the sensor 202 may also be configured to detect an analyte in blood or interstitial fluid indicative of other markers, such as lactate levels, which may improve accuracy in generating various predictions related to determining glucose insights. Additionally or alternatively, the wearable glucose monitoring device 104 may include additional sensors in the sensor 202 to detect analytes indicative of other markers.

[0040] In another example, the sensor 202 (or additional sensors of the wearable glucose monitoring device 104, not shown) can include first and second electrical conductors, and the sensor module 204 can electrically detect a change in electrical potential between the first and second electrical 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 to detect 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.

[0041] 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 discussed above. Based on these communications from the sensor 202, the sensor module 204 is further configured to generate communicable data packages including 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.

[0042] In implementations in which the wearable glucose monitoring device 104 is configured for wireless transmission, the transmitter 208 can wirelessly transmit the glucose measurements 114 as a data stream to the computing device. Alternatively or additionally, the sensor module 204 may buffer the glucose measurements 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 measurements 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 measurements 114 reach a threshold amount of data or number of measurements), etc.

[0043] Having considered example environments and examples of wearable glucose monitoring devices, we now consider a detailed description of some examples of techniques for user interfaces for presenting glucose insights in digital media environments, according to one or more implementation aspects.

[0044] User Interface for Presenting Glucose Insights Figure 3 illustrates an example embodiment 300 of a system in which the glucose monitoring application of Figure 1 utilizes a user interface configuration module and a glucose insight engine to configure a user interface for display. The illustrated example 300 includes the glucose monitoring application 116 having the user interface configuration module 120 from Figure 1, which also includes the glucose measurements 114 and the configuration data 122.

[0045] In the illustrated embodiment 300, the glucose monitoring application 116 further includes a glucose insight engine 302. Broadly speaking, the glucose insight engine 302 is configured to process the glucose measurements 114 to determine one or more glucose insights 304, for example, related to the glucose of the person 102. The user interface configuration module 120 is configured to configure the user interface based on the configuration data 122 to present one or more visual elements representative of the glucose insight 304. This includes selecting or otherwise determining visual elements representative of the determined glucose insight 304. As an output of these steps, the user interface configuration module 120 produces a configured user interface 124 having a selected visual element 306 indicative of the determined glucose insight 304.

[0046] As discussed above, the glucose insight engine 302 is configured to determine a glucose insight 304. Here, the glucose insight engine 302 is shown obtaining a glucose measurement 114. By way of example and not limitation, the glucose insight engine 302 can obtain the glucose measurement 114 from any one or more of the wearable glucose monitoring device 104, the storage device 118, or the storage of the glucose monitoring platform 110. In particular, the glucose insight engine 302 can obtain a glucose measurement of the person 102. In addition, the person 102 may correspond to a user of the computing device 106, such that the person 102 can view a configured user interface 124 including a selected visual element 306 that indicates a glucose insight 304 determined for the person 102's glucose. Additionally or alternatively, the glucose insight engine 302 can obtain glucose measurements 114 of other users of the user population 108 and determine a glucose insight 304 for the person 102's glucose in relation to the glucose of the users of the user population 108.

[0047] Indeed, the glucose insight engine 302, in one or more implementations, may not be limited to determining glucose insights based solely on the glucose measurements 114 of the person 102 and / or the glucose measurements 114 of other users of the user population 108. Instead, the glucose insight engine 302 can determine glucose insights 304 further based on a variety of other data without departing from the spirit or scope of the described techniques. By way of example and not limitation, the glucose insight engine 302 can determine glucose insights 304 based on data describing other physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow rate, etc.), fitness or activity (e.g., steps, activity type, performance, etc.), health events, medication regimens and / or medications taken, diet, stress, sleep, recovery events (e.g., meditation, massage), and the like.

[0048] Further, the glucose insight engine 302 may be configured to determine various glucose insights 304 based on the glucose measurements 114. At a given time, by way of example, the glucose insight engine 302 may determine a single glucose insight 304 or may determine multiple glucose insights 304. The glucose insights 304 may include, by way of example and not limitation, the current glucose reading 114, how the current glucose reading 114 compares to one or more other glucose readings 114 for the same or similar time on different days, how the one or more glucose readings 114 compare to one or more other glucose readings 114 for the same meal (e.g., breakfast, snack, lunch, or dinner) on different days, whether the current glucose reading 114 is below the glucose range, within the glucose range, or above the glucose range, the trend of the glucose reading 114 over a period of time (e.g., whether the value of the glucose reading is increasing, decreasing, or constant over the period of time), the rate of change of the glucose reading 114 over a period of time (e.g., how quickly the value of the glucose reading is increasing or decreasing over the period of time), the variability of the glucose reading 114 over the period of time, and how the variability of the glucose reading 114 in a first period of time (e.g., the “current” period) compares to the variability of the glucose reading 114 in one or more other periods of time (e.g., one or more historical periods), just to name a few.

[0049] In one or more implementations, the ranges to which the glucose measurements 114 are compared may vary throughout the day. For example, the ranges may be wider around determined meal times or determined exercise times and narrower around determined inter-meal times and at night. Alternatively or additionally, the ranges may narrow over time, such as in response to a determination that the person 102's glucose measurements 114 are less variable than they were previously as a result of the person 102 developing or changing a behavior that better controls the person's 102 glucose. In one or more implementations, the ranges may be set (or initially set) by the person's 102 health care provider. The health care provider may have access (e.g., through a provider portal) to subsequently update the ranges, and / or the glucose monitoring application 116 or glucose monitoring platform 110 may update the ranges, for example, in the manner described above or otherwise. Furthermore, the range may be set (or initially set) by a user (e.g., a person) of the glucose monitoring application 116, such as during onboarding with the glucose monitoring application 116 to generate glucose measurements 114 and / or while starting the wearable glucose monitoring system 104. The user, as well as a healthcare provider, may have access (e.g., via the glucose monitoring application 116) to subsequently update the range, and / or the glucose monitoring application 116 or glucose monitoring platform 110 may update the range, for example, in the manner described above or otherwise. However, in at least one implementation, the glucose monitoring application 116 may prevent the user from setting and / or updating the range. Furthermore, a healthcare provider (e.g., via a portal) and / or a user (e.g., via the glucose monitoring application) may be able to set different glucose ranges for different time periods (e.g., different times of day), such as different glucose ranges before and after mealtimes or overnight.It should be understood that the range or ranges to which glucose measurements are compared to determine glucose insight can be varied in many ways without departing from the spirit or scope of the described techniques.

[0050] Here, the user interface configuration module 120 is shown obtaining the glucose insight 304. Although the user interface configuration module 120 is shown in this example 300 obtaining the glucose insight 304 from a glucose insight engine 302 that is shown as local to the glucose monitoring application 116 and thus the computing device 106, in one or more implementations, the user interface configuration module 120 can obtain the glucose insight 304 from a different source. For example, the user interface configuration module 130 can obtain the glucose insight 304 over the network 112 from a different source remote from the glucose monitoring platform 110 or the computing device 106. Thus, to this end, the glucose insight engine 302 can be at least partially implemented in the glucose monitoring platform 110 and / or a different remote source in one or more implementations. However, in at least one implementation, the glucose insight engine 302 can be fully implemented in the glucose monitoring platform 110.

[0051] With this in mind, the user interface configuration module 120 may obtain one or more glucose insights 304 from a local source (e.g., when the glucose insight engine 302 is implemented locally on the computing device 106), from a remote source (e.g., when the glucose insight engine 302 is implemented on a glucose monitoring platform 110 remote from the computing device 106), or from some combination of local and remote sources (e.g., when the glucose insight engine 302 is implemented partially on the computing device 106 and partially on the glucose monitoring platform 110). In a situation where the glucose insight engine 302 is implemented partially on the computing device 106 and partially on the glucose monitoring platform 110, that portion of the computing device 106 and portions of the glucose monitoring platform 110 may determine different glucose insights 304, for example, to reduce the latency of providing a particular insight and / or because determining a particular insight may require an amount of computational resources that are burdensome to the operation of the computing device 106 (or simply not possible with the resources of the computing device 106). It should be appreciated that the user interface configuration module 120 can obtain one or more glucose insights 304 from different sources without departing from the spirit or scope of the described techniques.

[0052] Based on the glucose insights 304, the user interface configuration module 120 configures the user interface, thus generating a configured user interface 124, e.g., with selected visual elements 306 that depict the obtained glucose insights 304. In particular, the user interface configuration module 120 generates the configured user interface 124 according to the configuration data 122. As described above, the configuration data 122 generally controls which glucose insights are presented to a particular user at a given time and how those insights are presented, e.g., which one or more visual elements are incorporated into the configured user interface 124, based on the one or more determined glucose insights 304.

[0053] In one or more implementations, by way of example, configuration data 122 may include user-specified preferences. For example, glucose monitoring application 116 may receive user input specifying that user interface 124 present only one insight at a time. In this situation, glucose monitoring application 116 may retain this preference in configuration data 122, so that when user interface configuration module 120 configures user interface 124, the module configures the interface to present only one determined insight at a time via each visual element. User preferences retained in configuration data 122 may be based on user feedback.

[0054] In implementations in which the configuration data 122 holds preferences based on user feedback, this feedback can be "explicit" or "implicit." As used herein, the term "explicit feedback" refers to feedback that a user intentionally provides in relation to a visual element displayed as part of a user interface. As an example, a user who is prompted to provide feedback regarding a visual element (e.g., by displaying a selectable thumbs up or thumbs down for the visual element) and then provides such feedback (e.g., by selecting a thumbs up or thumbs down) intentionally provides feedback regarding the visual element, thus providing explicit feedback. Another example of explicit feedback is providing a rating, e.g., of 5 stars or 1-10, for a visual element. Rather than prompting a user to provide feedback, explicit feedback can also include a user selection not to display a particular visual element as part of the configured user interface 124. One example of this is a selection not to display visual elements that have different colors based on a determined glucose insight, which may apply, for example, in a situation in which a user is color blind and therefore cannot distinguish between different colors. Another example is when a user selects not to display a glucose trend graph as part of the configured user interface 124. In addition to not displaying a visual element (e.g., feedback to omit a visual element), explicit user feedback can also include a selection to affirmatively display various visual elements, such as an affirmative selection to display an insight, a current glucose count, a color area that can show a shape indicating a glucose trend (e.g., increasing, decreasing, or remaining constant). It should be appreciated that a user can provide a variety of explicit feedback regarding which visual elements to display, which visual elements not to display, which visual elements the user prefers, which visual elements the user does not prefer, etc., in accordance with the described techniques.This explicit feedback may be captured and maintained in configuration data 122 to control which visual elements are determined to be included in the configured user interface 124 .

[0055] As mentioned above, feedback may be implicit. As used herein, the term "implicit feedback" refers to feedback that is not explicit with respect to a visual element, but corresponds to a user action detected in relation to the visual element that indicates a preference or non-preference for the visual element. By way of example, implicit feedback may include navigating to a different view or a different visual element to obtain information. Implicit feedback may also include, for example, using the glucose monitoring application 116 less than before (e.g., looking at the visual element less), acting in a manner that may be detrimental to achieving a glucose goal (e.g., lowering or remaining stable) as measured by glucose values ​​and / or other health indicators, switching to a different application, and dismissing or snoozing notifications, just to name a few. Similar to explicit feedback, the user interface configuration module 120 may capture various implicit feedback regarding which visual elements should be displayed, which visual elements should not be displayed, which visual elements the user prefers, which visual elements the user does not prefer, etc., in accordance with the techniques described. This implicit feedback may be captured and maintained in configuration data 122 to control which visual elements are determined to be included in the configured user interface 124 .

[0056] In addition to user preferences, the configuration data 122 may include rules that define a progression of insights to present to the user over time, such that initially the user interface configuration module 120 is limited to configuring the user interface 124 to present one insight at a time via each visual element. However, after one or more criteria are met, the rules may allow the user interface configuration module 120 to configure the user interface 124 to simultaneously present two insights of different types via each visual element. Such a progression may have several "display items" that allow more and / or different types of insights to be included within the user interface, each time revealing them. In this manner, by presenting different numbers of insights via the user interface 124 over time, the user interface configuration module 120 may educate the user about the user's glucose and the impact of the user's actions on the user's glucose. Also, such progression rules may be defined such that after one or more criteria are met, the user interface configuration module 120 may configure the user interface 124 to simultaneously present a glucose graph plotting glucose measurements 114 over time with one or more glucose insights. It should be appreciated that the configuration data 122 can control which glucose insights can be presented via respective visual elements within the configured user interface in a variety of ways, according to the techniques described.

[0057] Additionally, the configuration data 122 controls how the glucose insight is presented depending on the determined glucose insight. Broadly speaking, the configuration data 122 can specify which visual element to use for a particular determined glucose insight 304. By way of example, the configuration data 122 may define to configure the user interface to include a first colored visual element (e.g., an orange area) for a first glucose insight (e.g., the person's 102 most recent glucose reading 114 is above range), to configure the user interface to include a second colored visual element (e.g., a green area) for a second glucose insight (e.g., the person's 102 most recent glucose reading 114 is within range), and to configure the user interface to include a third colored visual element (e.g., a yellow area) for a third glucose insight (e.g., the person's 102 most recent glucose reading 114 is below range).

[0058] In one or more implementations, the configuration data 122 includes a mapping of glucose insights to visual elements, such that the user interface configuration module 120 selects or otherwise determines which visual elements to include in the user interface 304 in response to the determined glucose insight 304. For example, this mapping may be a list of visual elements and respective glucose insights, and when a glucose insight is obtained, the user interface configuration module 120 can refer to the list to identify the respective visual element. Alternatively or additionally, such a list may be configured as logic including if / then statements that the user interface configuration module 120 processes to determine one or more visual elements to configure the user interface, such that "if" a given glucose insight is received, the user interface configuration module 120 can process the statements to identify the visual element to be "next" used in the user interface. The configuration data 122 may control "how" the insights are presented as part of the configured user interface 124 in different ways without departing from the spirit or scope of the described techniques. Consider the following description of FIGS. 4-12 in the context of user interfaces that may be presented with different visual elements.

[0059] 4 shows an example implementation 400 of a user interface that displays a glucose graph that plots the value of a user's glucose measurements over time. The illustrated example 400 includes the example computing device 106 from FIG. 1 displaying the example user interface 124 via a display device, e.g., a touch screen.

[0060] Here, the user interface 124 includes a glucose graph 402 that plots one or more of the glucose readings 114 (e.g., of the person 102) over time. In the illustrated example 400, the time period over which the plotted glucose readings 114 are displayed on the glucose graph 402 is 12 hours. The user interface 124 also includes a selectable element that can be selected to display the plotted glucose readings 114 over different time periods, including a 3 hour period, a 5 hour period, and a 24 hour period. It should be understood that the glucose monitoring application 116 can plot the glucose readings 114 on the glucose graph 402 over different time periods without departing from the spirit or scope of the technology described herein. However, in one or more implementations, these time periods correspond to periods preceding the current time, for example, allowing a user to review a pattern of glucose leading up to a current glucose value.

[0061] However, in some cases, users may be confused as to what the glucose measurements 114 plotted over time mean. As a result, those users may not be able to derive insight from the data and therefore may not be able to influence their behavior according to the glucose insight to achieve health goals, e.g., glucose-based goals. In other words, a glucose graph plotting glucose measurements 114 over time may be difficult for some users to understand and comprehend. Even for users who are able to determine some insight from the glucose graph 402, determining such insight from the glucose graph 402 may be cumbersome because it may require switching to a different user interface to see individual values ​​for each of the multiple glucose measurements 114 or providing user input regarding the individual measurement representations on the graph. Determining such insight from the glucose graph 402 alone may also require the user to already know or make inferences regarding various parameters necessary to make accurate insights, such as, for example, the user may need to know or infer the upper and lower values ​​of the glucose range. However, making such inferences may be impractical, such as when the glucose range changes throughout the course of a day.

[0062] In any event, the glucose graph 402 may present too much information to some users (e.g., new users) before they understand what the patterns in the glucose graph mean about their health. As a result, presenting the glucose graph 402 may overwhelm and annoy users, causing them to stop using the glucose monitoring application. Doing so may prevent the user from realizing the health benefits derived from utilizing the glucose monitoring application, thus resulting in further deterioration of the user's health. In contrast to presenting a glucose graph, consider the following description of a user interface that presents visual elements representing determined glucose insights.

[0063] FIG. 5 illustrates an example implementation 500 of a user interface that displays visual elements representative of glucose insights determined for a user.

[0064] Similar to the illustrated embodiment 400, the illustrated embodiment 500 includes an example of a computing device 106 displaying an example of a user interface 124 from FIG. 1 via a display device, e.g., a touch screen. However, in contrast to the embodiment 400, the user interface 124 shown in the illustrated embodiment 500 does not include a glucose graph. Instead, the user interface 124 includes a visual element 502 in this embodiment 500, e.g., without the display of a glucose graph and without the display of a number corresponding to the user's current glucose.

[0065] In this example 500, visual element 502 represents a glucose insight determined for a user, e.g., person 102. In the context of FIG. 3 , glucose insight engine 302 determines the glucose insight, and user interface configuration module 120 configures user interface 124 to include visual element 502. User interface configuration module 120 can configure user interface 124, at least in part, by referencing or otherwise processing configuration data 122 to determine visual element 502, e.g., configuration data 122 can specify which visual elements to display based on the determined glucose insight.

[0066] In one or more implementations, the visual element 502 corresponds to a color region that may be configured with different colors depending on the determined glucose insight. For example, the user interface configuration module 120 can configure the user interface 124 to include a color region having a first color responsive to a first glucose insight determination, a second color responsive to a second glucose insight determination, a third color responsive to a third glucose insight determination, etc. In particular, the user interface configuration module 120 can configure the user interface 124 to include a color region having a first color (e.g., orange) in response to a determination that the person's 102 most recent glucose measurement 114 is above a desired glucose range (e.g., above a range of 70-180 mg / dL), a color region having a second color (e.g., green) in response to a determination that the person's 102 most recent glucose measurement is within a desired range (e.g., a range between 70-180 mg / dL), and a color region having a third color (e.g., red or yellow) in response to a determination that the person's 102 most recent glucose measurement 114 is below the desired glucose range (e.g., above a range of 70-180 mg / dL).

[0067] It should be understood that the above example is just one example of how the color regions can be used, and that the visual elements corresponding to the colors of the color regions can have any of a variety of colors to represent different glucose insights in accordance with the described techniques. For example, the colors that make up the color regions may correspond to the variability of the glucose measurements of the person 102, so that if the glucose insight engine 302 determines that the variability is low, the user interface configuration module 120 configures the user interface 124 to include a color region having a color corresponding to a positive insight (e.g., green), and so that if the glucose insight engine 302 determines that the variability is high, the user interface configuration module 120 configures the user interface 124 to include a color region having a color corresponding to a negative insight or an insight that the user should take note of (e.g., red or orange). Indeed, different user interfaces can be configured with color regions having different colors to represent different insights without departing from the spirit or scope of the described techniques.

[0068] Alternatively or additionally, one or more color regions may be capable of having a gradient fill such that the color region can be filled with a gradient of colors from an empty (or low-filled) state to a full (or nearly full) state. In one or more implementations, the color gradient may be more saturated from an empty state to a full state (e.g., light green to dark green), or the color gradient may be less saturated from an empty state to a full state (e.g., dark red to light red). Alternatively or additionally, the gradient may have a spectrum of different colors, e.g., green, yellow, red, and mixtures therebetween, such that the color region can be filled from a color at one end of the spectrum (e.g., green) through any intermediate color in the spectrum (e.g., yellow) to a color at the other end of the spectrum (e.g., red). Colors at one end of the spectrum may represent glucose insight determinations that are generally positive with respect to a person's health (e.g., within desired range, low variability, trending toward desired range, etc.), and colors at the other end of the spectrum may represent glucose insight determinations that are generally negative with respect to a person's health (e.g., outside desired range, high variability, trending away from desired range, etc.).

[0069] In any event, by displaying the visual elements 502, the user interface 124 provides information that the user can easily understand at a glance. For example, if the visual elements 502 have a color that indicates that the user's most recent glucose reading is within a desired range, the user can grasp this insight at a glance from the user interface 124. This is in contrast to having to focus on the glucose graph, find a display of the most recent glucose reading, and determine whether the location of the display is within an area of ​​the graph that corresponds to the desired range. Configuring a user interface that uses visual elements to represent glucose insights can be particularly advantageous on mobile devices such as smart watches, where screen space for displaying information may be limited and input for obtaining detailed information may be restricted. Instead, according to the described techniques, the user interface configuration module 120 can configure a user interface for display via a smart watch that includes the visual elements 502 (e.g., color regions) such that the user can simply rotate her or his wrist to look at the display of the smart watch to grasp the glucose insight represented by the displayed visual elements 502. Although configuring the user interface 124 with a single visual element 502 representing a single glucose insight is discussed above and below, it should be understood that the user interface 124 may, in one or more implementations, be configured with more information and / or more visual elements than just a single visual element. In this context, consider the following description of FIG.

[0070] FIG. 6 illustrates an example implementation 600 of a user interface that displays visual elements representative of glucose insight determined for a user and that displays information supplementing the glucose insight.

[0071] Similar to the illustrated embodiment 500, the illustrated embodiment 500 includes an example computing device 106 displaying an example user interface 124 via a display device, e.g., a touch screen, from FIG. 1. In the illustrated embodiment 600, the user interface 124 also includes a visual element 502. Although the user interface 124 does not include a glucose graph or numbers corresponding to the user's current glucose, the user interface does include supplemental information 602.

[0072] In one or more implementations, the user interface configuration module 120 can configure the user interface to include supplemental information. The supplemental information for which the user interface is configured may depend on the determined glucose insight. Furthermore, which supplemental information is displayed and whether the supplemental information is displayed may be controlled by the configuration data 122. Broadly speaking, the supplemental information 602 supplements or describes the visual element 502. With respect to describing the visual element 502, the supplemental information 602 can provide information (e.g., text) that informs the user why the visual element 502 is included in the user interface 124. By way of example, the supplemental information 602 can provide a textual description of the determined glucose insight. It should be appreciated that such a textual description may range in detail from a general description of the insight to a more detailed description including the numerical value, how the numerical value compares to other numerical values ​​(e.g., thresholds), statistical measures derived to determine the glucose insight (e.g., average, standard deviation, etc.), and the like. Alternatively or additionally, the supplemental information 602 may not be specific to the visual element 502 but may simply relate to the user's glucose, for example, the supplemental information 602 may include encouragement or warnings, reminders, indications that a goal has been achieved, etc. The user interface configuration module 120 may configure the user interface 124 with a variety of supplemental information without departing from the spirit or scope of the described techniques. As noted above, the user interface configuration module 120 may alternatively or additionally configure the user interface with two or more visual elements representing two or more glucose insights. In this context, consider the following description of FIG. 7.

[0073] 7 illustrates an example implementation 700 of a user interface that displays a first visual element representing a first glucose insight and also displays a second visual element representing a second glucose insight. The illustrated example 700 includes an example computing device 106 from FIG. 1 that displays the example user interface 124 via a display device, e.g., a touch screen.

[0074] Here, the user interface 124 includes a first visual element 702 and a second visual element 704. In accordance with the described techniques, the user interface configuration module 120 configures the user interface 124 in this example 700 with the first visual element 702, for example, based on a determination of a first glucose insight by the glucose insight engine 302. The user interface configuration module 120 also configures the user interface 124 in this example 700 with the second visual element 704, for example, based on a determination of a second glucose insight by the glucose insight engine 302. Thus, the first and second visual elements 702, 704 represent different glucose insights and are displayed simultaneously. The multiple visual elements that the user interface may be configured for simultaneous display may represent various combinations of different glucose insights without departing from the spirit or scope of the described techniques.

[0075] In the illustrated embodiment 700, for example, the first visual element 702 may correspond to a color region that represents a glucose insight, such as how the user's current glucose compares to a glucose range. For example, in response to the glucose insight engine 302 determining that the user's current glucose is above a glucose range (e.g., a first insight), the user interface configuration module 120 configures the first visual element 702 as a color region having a respective color (e.g., orange for above glucose range). In contrast, the second visual element 704 may correspond to a shape that represents a glucose insight, such as a trend of glucose readings over time or a rate of change of glucose readings over time. For example, in response to the glucose insight engine 302 determining that the user's glucose is increasing over time, or increasing over time but slowly (e.g., a second insight), then the user interface configuration module 120 configures the second visual element 704 to have a particular shape corresponding to the insight (e.g., an upward pointing triangle or arrow representing an increase in glucose readings, or a single upward pointing triangle representing an increase, but a relatively slow increase). It should be understood that the first and second visual elements may be configured to be different color regions and shapes and / or represent different first and second glucose insights in the spirit of the described techniques. Consider the following description of FIG. 8 in the context of using a second visual element that is different from the second visual element 704 and thus represents a different glucose insight than the second visual element 704.

[0076] FIG. 8 illustrates another example implementation 800 of a user interface displaying a first visual element representing a first glucose insight and a second visual element representing a different glucose insight than the second visual element of FIG. 7 .

[0077] Similar to the illustrated example 700, the illustrated example 800 includes an example computing device 106 from FIG. 1 displaying an example user interface 124 via a display device, e.g., a touch screen. In the illustrated example 800, the user interface 124 also includes a first visual element 702, e.g., a color region having a color corresponding to a first glucose insight. However, in contrast to the illustrated example 700, the user interface 124 does not include the second visual element 704, but instead includes a different second visual element 802.

[0078] According to the described technique, the user interface configuration module 120 configures the user interface 124 in this example 800 with a different second visual element 802 based on a determination of a second glucose insight different from the second glucose insight determined with respect to FIG. 7. In response to obtaining the different second glucose insight, the user interface configuration module 120 configures the user interface 124 with a different second visual element 802 that is different from the second visual element 704. In the illustrated example, the different second visual element 802 corresponds to a different shape than the second visual element 704, where the second visual element 704 is a single triangle, whereas the different second visual element 802 is a plurality of stacked triangles. With this in mind, the shape of the different second visual element 802 will represent a different glucose insight than the shape of the second visual element 704. It should be understood that the visual elements may have various shapes to represent different glucose insights without departing from the spirit or scope of the described technique.

[0079] In one embodiment, for example, the second visual element 704 may represent a glucose insight regarding the rate of change of the glucose reading, as described above. In the illustrated embodiment 700, the second visual element 704 (a single upward pointing triangle or arrow) may represent a glucose insight that is determined to be increasing for the person 102, but relatively slowly, e.g., a low rate of change. In contrast, a different second visual element 802 (a double upward pointing triangle or arrow) may represent a glucose insight that is determined to be increasing for the person 102, but relatively faster than the rate determined for embodiment 700, e.g., a moderate rate of change. The user interface configuration module 120 may configure the user interface 124 with one or more downward pointing triangles or arrows to represent a decrease in a value, e.g., a downward trend in the glucose reading, with more downward pointing arrows or triangles corresponding to a greater rate of decrease than fewer arrows or triangles. Additionally, different shapes may be used to represent that glucose measurements of person 102 are substantially the same or similar over a period of time, e.g., the glucose insight engine 302 does not determine an upward or downward glucose trend for person 102. Indeed, glucose insights may be represented in a variety of shapes in accordance with the techniques described.

[0080] FIG. 9 illustrates another example implementation 900 of a user interface displaying a first visual element representing a first glucose insight and a second visual element representing another, different glucose insight than the second visual element of FIGS. 7 and 8 .

[0081] Similar to the illustrated embodiments 700, 800, the illustrated embodiment 900 includes an example of a computing device 106 from FIG. 1 displaying an example user interface 124 via a display device, e.g., a touch screen. In the illustrated embodiment 900, the user interface 124 also includes a first visual element 702, e.g., a color region having a color corresponding to a first glucose insight. In the illustrated embodiment 900, the user interface 124 does not include the second visual element 704 or the different second visual element 802. Instead, the user interface 124 shown in the embodiment 900 includes a second visual element 902 that is different from the second visual element 704 and the different second visual element 802.

[0082] According to the described techniques, the user interface configuration module 120 configures the user interface 124 in this example 900 with a second visual element 902 based on a determination of a second glucose insight that is different from the second glucose insight determined in connection with Figures 7 and 8. In response to obtaining this second glucose insight that is different from the second insight determined in connection with Figures 7 and 8, the user interface configuration module 120 configures the user interface 124 with the second visual element 902 that is different from the second visual element 704 and the different second visual element 802. In the illustrated example, the second visual element 902 corresponds to a different shape than the second visual element 704 and the different second visual element 802, and the second visual element 902 is a larger number of stacked triangles (i.e., three triangles) than the different second visual element 802 (i.e., two triangles) and the second visual element 704 (i.e., a single triangle). With this in mind, the shape of second visual element 902 will represent a different glucose insight than the insight represented by the shape of second visual element 704 and different second visual element 802.

[0083] As described above, by way of example, the second visual element 704 may represent a glucose insight regarding the rate of change of the glucose reading. The second visual element 704 (a single upward triangle or arrow) may represent a glucose insight in which the glucose of the person 102 is increasing, but is determined to be relatively slow, e.g., at a low rate of change. A different second visual element 802 (a double upward triangle or arrow) may represent a glucose insight in which the glucose of the person 102 is increasing, but is determined to be relatively faster than the rate determined in connection with example 700, e.g., a moderate rate of change. In contrast, the second visual element 902 (three upward triangles or arrows) may represent a glucose insight in which the glucose of the person 102 is increasing, but is determined to be relatively faster, e.g., at a relatively high rate of change, than the rate determined in connection with examples 700 and 800. In addition to different shapes, the user interface configuration module 120 may alternatively or additionally configure the user interface 124 to include different numbers of the same or different shapes to represent various glucose insights in accordance with the described techniques.

[0084] 10 shows an example implementation 1000 of a user interface that displays first and second visual elements representing first and second glucose insights, respectively, and also displays a glucose count. The illustrated example 1000 includes an example computing device 106 from FIG. 1 that displays the example user interface 124 via a display device, e.g., a touch screen.

[0085] Here, the user interface 124 includes a first visual element 702 (e.g., a color region having a color corresponding to a first glucose insight) and a different second visual element 802 (e.g., one or more shapes corresponding to a second glucose insight). However, in contrast to FIGS. 5-9, the user interface 124 of this example 1000 also includes a glucose number 1002. The glucose number 1002 can correspond to the user's "current" glucose reading, e.g., the most recent glucose reading 114 produced by and obtained from a glucose monitoring system. It should be appreciated that in one or more circumstances, the user interface configuration module 120 can configure the user interface 124 to include the glucose number 1002, and in other circumstances, the user interface configuration module 120 can prevent the display of the glucose number 1002. The display or non-display of the glucose number 1002 may be controlled, at least in part, by the configuration data 122.

[0086] As discussed above, by way of example, the configuration data 122 may define a progression of insights over time for presentation to the user. In one or more implementations, this may include initially configuring the user interface 124 with one or more glucose insights for display during a stage of the progression (e.g., a first stage). During this stage, the configuration data 122 may also prevent the user interface 124 from being configured with the glucose number such that the glucose number 1002 is not displayed during this stage. In a subsequent stage (e.g., a second, third, or fourth stage, to name a few), the configuration data 122 may allow for incremental configuration that does not prevent the user interface 124 from being configured to display the glucose number 1002. Instead, in this subsequent stage, the user interface 124 may be configured with the glucose number such that one or more glucose insights displayed during a stage (e.g., a first stage) may be displayed simultaneously with the glucose number 1002 via the user interface 124 during the subsequent stage.

[0087] By progressively revealing additional or different information, including additional or different visual elements as well as other graphical elements (e.g., glucose count 1002 or glucose graphs), the glucose monitoring application 116 can educate the user about the user's glucose in a progressively easier to understand manner. As a result of educating the user through the progressive reveal of information, the glucose monitoring application 116 can further prevent the user from becoming overwhelmed or confused by the presented information. Furthermore, a user who is not overwhelmed or confused by the presentation of information can continue to use the glucose monitoring application 116 and, through continued use, can realize the health benefits derived from utilizing the glucose monitoring application as well as achieve improved glucose control.

[0088] Alternatively or additionally, the user interface 124 may be configured with the glucose number 1002 according to, for example, user preferences captured in the configuration data 122. For example, the glucose monitoring application 116 may include a user interface means through which a user can provide input to toggle the display of the glucose number 1002 on or off. To represent the ability of the glucose monitoring application 116 to receive input from a user to select whether to display various visual elements (e.g., representing glucose insights) or various graphical elements, the illustrated embodiment 1000 also includes a user's hand 1004. Here, the hand 1004 is depicted as selecting the interface means 1006 (e.g., using a touch or gesture). In general, receiving a selection via the interface means 1006 represents a function that allows a user to provide input to toggle between displaying one or more visual elements (or other graphical elements) and not displaying them. By way of example and not limitation, a user may select the interface means 1006 to add to (or remove from) the user interface 124 to display one or more of a glucose count, a glucose graph, supplemental information, or any of a plurality of visual elements corresponding to glucose insights. Whether based on user selection (e.g., via the interface means) or based on progressively revealing information, in one or more implementations, the user interface 124 may be configured to display a glucose graph along with one or more visual elements representing respective glucose insights. In this context, consider the following description of FIG. 11.

[0089] FIG. 11 illustrates an example implementation 1100 of a user interface that displays first and second visual elements representing first and second glucose insights, respectively, as well as a glucose count and a glucose graph that plots the values ​​of the user's glucose measurements over time.

[0090] Similar to the illustrated embodiment 1000, the illustrated embodiment 1100 includes an example computing device 106 displaying an example user interface 124 via a display device, e.g., a touch screen, from FIG. 1. In the illustrated embodiment 1100, the user interface 124 includes a first visual element 702, a different second visual element 802, and a glucose number 1002. However, in contrast to the illustrated embodiment 1000, the user interface 124 further includes a glucose graph 1102.

[0091] According to the described technique, the user interface configuration module 120 configures the user interface 124 in this example 1100 with the glucose graph 1102 based on the configuration data 122. The configuration data 122 may include, for example, a user's preference to affirmatively display the glucose graph 1102 or rules of progression that allow the glucose graph 1102 to be displayed at the current stage. Similar to the glucose count 1002, the configuration data 122 may define a progression of insights to present to the user over time. In one or more implementations, this may include initially configuring the user interface 124 with one or more glucose insights for display during a stage of progression (e.g., a first stage). During this stage, the configuration data 122 may also prevent the user interface 124 from being configured with the glucose graph so that the glucose graph 1102 is not displayed during this stage. In a subsequent stage (e.g., a second, third, or fourth stage, to name a few), the configuration data 122 may allow for incremental configuration that does not prevent the user interface 124 from being configured with the glucose graph 1102 for display. Instead, in this subsequent stage, the user interface 124 may configure the glucose graph such that one or more glucose insights displayed during a stage (e.g., a first stage) can be displayed simultaneously with the glucose graph 1102 via the user interface 124 during the subsequent stage. Incrementally revealing the glucose graph in this manner can have advantages similar to the incrementally revealing glucose counts discussed in more detail above.

[0092] In one or more implementations, the user interface configuration module 120 can configure the glucose graph 1102 to visually highlight a desired range, e.g., a “healthy” glucose range. As discussed above, this range may change for a variety of reasons, may be dynamically changed (e.g., by a glucose monitoring application), or may be set based on user or healthcare provider input. This range may also change depending on time, such as the time of day. In any case, to visually highlight the range, the user interface configuration module 120 can configure the glucose graph 1102 to include a visually highlighted in-range region 1104. The in-range region 1104 may be visually highlighted by having a different color than other regions of the glucose graph 1102. For example, the user interface configuration module 120 can configure the in-range region 1104 to have a visually pleasing color (e.g., green), which may be user selected or pre-determined to indicate that having an in-range glucose reading 114 is a positive health indication. By coloring the in-range region 1104 differently than other regions of the glucose graph 1102, the user interface configuration module 120 allows a user to quickly glance at the user interface 124 to determine whether the representation of their glucose measurement 114 is within the desired range.

[0093] FIG. 12 illustrates another example implementation 1200 of a user interface that displays visual elements representative of glucose insights determined for a user.

[0094] The illustrated example 1200 includes an example of a computing device 106 from FIG. 1 displaying an example user interface 124 via a display device, e.g., a touch screen. Here, the user interface includes one or more visual elements 1202. According to the described techniques, the user interface configuration module 120 configures the user interface 124 in this example 1200 with one or more visual elements 1202 based on the determination of one or more glucose insights. As an example, the glucose insight engine 302 can determine a decreasing trend of a user's glucose readings 114 over time, and subsequently determine an increasing trend of the glucose readings 114. In response to determining these glucose insights as trends, the user interface configuration module 120 can configure the user interface 124 to include one or more visual elements 1202 having trend lines. The presentation of trend lines over time contrasts with plotting glucose readings, as trend lines do not show a representation of each reading at the associated time (or a line that substantially passes through the value of each reading at the associated time). Instead, the trend line indicates a general trend of the glucose measurements over time, such as substantially increasing or substantially decreasing. In particular, the one or more visual elements 1202 with the trend line limit the number of glucose value labels, where the labels are limited to values ​​corresponding to an upper threshold of the desired range (e.g., 180 mg / dL) and a lower threshold of the desired range (e.g., 70 mg / dL). Although these labels are shown in the illustrated example 1200, in at least one implementation, the trend graph may be presented via the user interface 124 without glucose value labels. Here, the one or more visual elements 1202 also include an in-range region. By including the in-range region, the user interface 124 can visually indicate whether the user's glucose measurements are trending to remain within, enter, or exit the corresponding desired range.It should be understood that various combinations of the above-described visual elements and other graphical elements may be included as part of the user interface 124 without departing from the spirit or scope of the described techniques.

[0095] 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.

[0096] Exemplary Procedure This section describes example procedures for a user interface for glucose monitoring. Aspects of the procedures may be implemented in hardware, firmware, software, or a combination 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 the respective blocks. In at least some implementations, the procedures are performed by a glucose monitoring application, such as glucose monitoring application 116, utilizing user interface configuration module 120.

[0097] FIG. 13 illustrates a procedure 1300 in an example implementation in which a user interface is configured to present visual elements representing glucose insights based on configuration data.

[0098] A glucose measurement of a user is obtained (block 1302). According to principles described herein, the glucose measurement is collected by a glucose monitoring device. By way of example, the glucose insight engine 302 obtains a glucose measurement 114 of the person 102 from a wearable glucose monitoring device 104.

[0099] The glucose measurements are processed to determine a glucose insight (block 1304). By way of example, the glucose insight engine 302 processes the glucose measurements 114 to determine one or more glucose insights 304, e.g., regarding the glucose of the person 102. The glucose insight engine 302 can be configured to determine various glucose insights 304 based on the glucose measurements 114. At a given time, by way of example, the glucose insight engine 302 may determine a single glucose insight 304 or may determine multiple glucose insights 304. The glucose insights 304 may include, by way of example and not limitation, the current glucose reading 114, how the current glucose reading 114 compares to one or more other glucose readings 114 for the same or similar time on different days, how the one or more glucose readings 114 compare to one or more other glucose readings 114 for the same meal (e.g., breakfast, snack, lunch, or dinner) on different days, whether the current glucose reading 114 is below the glucose range, within the glucose range, or above the glucose range, the trend of the glucose reading 114 over a period of time (e.g., whether the value of the glucose reading is increasing, decreasing, or constant over the period of time), the rate of change of the glucose reading 114 over a period of time (e.g., how quickly the glucose reading is increasing or decreasing in value over the period of time), the variability of the glucose reading 114 over a period of time, and how the variability of the glucose reading 114 in a first period of time (e.g., the “current” period) compares to the variability of the glucose reading 114 in one or more other periods of time (e.g., one or more historical periods), just to name a few.

[0100] As described throughout, the glucose insight engine 302 may not be limited to determining glucose insights based solely on the glucose measurements 114 of the person 102 and / or the glucose measurements 114 of other users of the user population 108. Instead, the glucose insight engine 302 can determine glucose insights 304 based additionally on a variety of other data without departing from the spirit or scope of the described techniques. By way of example and not limitation, the glucose insight engine 302 can determine glucose insights 304 based on data describing other physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow rate, etc.), fitness or activity (e.g., steps, activity type, performance, etc.), health events, medication regimens and / or medications taken, diet, stress, sleep, recovery events (e.g., meditation, massage), and the like.

[0101] The user interface is configured to present visual elements representing the glucose insight based on the configuration data (block 1306). As an example, the user interface configuration module 120 retrieves glucose insights 304 from the glucose insight engine 302. Then, based on the glucose insights 304, the user interface configuration module 120 configures the user interface, thus generating the configured user interface 124, e.g., with selected visual elements 306 illustrating the retrieved glucose insights 304. In particular, the user interface configuration module 120 generates the configured user interface 124 according to the configuration data 122. As discussed throughout, the configuration data 122 generally controls which glucose insights are presented to a particular user at a given time and how those insights are presented, e.g., which one or more visual elements are incorporated into the configured user interface 124, based on the one or more determined glucose insights 304.

[0102] The configured user interface having a visual element representative of the determined glucose insight is displayed (block 1308). By way of example, the glucose monitoring application 116 causes the configured user interface 124 to be displayed by the computing device 106 along with the visual element 306 representative of the glucose insight 304.

[0103] FIG. 14 illustrates an additional procedure 1400 in another example implementation where the user interface is configured to present visual elements representing different glucose insights over time based on configuration data.

[0104] Configuration data is obtained (block 1402). In accordance with principles described herein, the configuration data maps glucose insights to different visual elements and controls which glucose insights are presented in the user interface at a given time and how the glucose insights are presented in the user interface using the different visual elements. By way of example, the user interface configuration module 120 obtains configuration data 122. As discussed throughout, the configuration data 122 generally controls which glucose insights are presented to a particular user at a given time and how those insights are presented, e.g., which one or more visual elements are incorporated into the configured user interface 124, based on the one or more determined glucose insights 304.

[0105] Glucose insights are obtained for the user during a first time period (block 1404), and the user interface is configured to present visual elements representing certain of the glucose insights obtained during the first time period based on the configuration data (block 1406). As an example, the glucose insight engine 302 processes the glucose measurements 114 to determine, for example, one or more glucose insights 304 related to the glucose of the person 102. The user interface configuration module 120 then obtains the glucose insights 304 generated by the glucose insight engine 302 during the first time period. The first time period can correspond, for example, to glucose insights obtained over a period of the previous hour, the previous day, etc. The user interface configuration module 120 then produces the configured user interface 124 by selecting one or more of the glucose insights and presenting visual elements 306 within the user interface 124 configured to represent the selected glucose insights 304.

[0106] Glucose insights are obtained for the user during a second time period (block 1408), and the user interface is configured to present different visual elements representing different glucose insights of at least the glucose insights obtained during the second time period based on the configuration data (block 1410). As an example, the user interface configuration module 120 obtains glucose insights 304 generated by the glucose insight engine 302 during the second time period. The second time period may correspond to a later time period that occurs after the first time period, for example, the second time period may occur one hour, one day, one week, or one month after the first time period. The user interface configuration module 120 then generates the configured user interface 124 by selecting one or more of the glucose insights and presenting visual elements 306 within the user interface 124 configured to represent the selected glucose insights 304.

[0107] In accordance with the principles described herein, a glucose insight is a different type of glucose insight than a different glucose insight. Thus, in particular, the configuration data 122 changes the visual elements and respective glucose insights over time, such as by presenting a color area indicating whether the user's current glucose value is within a glucose range in a first time period and presenting an arrow indicating a trend in the user's glucose readings in a second time period. This change in the glucose insights presented at different times based on the configuration data can be based on a gradual reveal of the glucose insight, changes in user preferences, user feedback data, etc.

[0108] Having described exemplary procedures according to one or more implementations, exemplary systems and devices that can be utilized to implement the various techniques described herein are now discussed.

[0109] Exemplary Systems and Devices 15 illustrates an example system generally at 1500, including an example computing device 1502, which represents one or more computing systems and / or devices that may implement various techniques described herein, as illustrated through the inclusion of a user interface configuration module 120 and a glucose monitoring platform 110. The computing device 1502 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 system.

[0110] The illustrated exemplary computing device 1502 includes a processing system 1504, one or more computer-readable media 1506, and one or more I / O interfaces 1508 communicatively coupled to each other. Although not shown, the computing device 1502 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.

[0111] The processing system 1504 represents the functionality for performing one or more operations using hardware. Thus, the processing system 1504 is illustrated as including hardware elements 1510, which may be configured as a processor, a functional block, or the like. This may include hardware implementations as application specific integrated circuits or other logic devices formed using one or more semiconductors. The hardware elements 1510 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.

[0112] The computer readable medium 1506 is shown as including memory / storage 1512. The memory / storage 1512 represents memory / storage capacity associated with one or more computer readable media. The memory / storage component 1512 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 1512 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 1506 may be configured in a variety of other ways as further described below.

[0113] The input / output interface 1508 embodies functionality that allows a user to input commands and information into the computing device 1502 and to present information to the 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 touch), cameras (which may use visible or invisible wavelengths such as infrared frequencies to recognize movements as gestures that do not involve touch), 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, the computing device 1502 may be configured in a manner further described below to support user interaction.

[0114] Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, program 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," "functionality," and "component" generally represent software, firmware, hardware, or combinations thereof, meaning that aspects of the techniques described herein are platform independent, i.e., the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

[0115] 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 1502. By way of example, and not limitation, computer-readable media may include "computer-readable storage media" and "computer-readable signal media."

[0116] 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.

[0117] A "computer-readable signal medium" may refer to a signal-bearing medium configured to transmit instructions to the hardware of the computing device 1502, 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, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0118] As previously mentioned, the hardware elements 1510 and the computer-readable medium 1506 represent modules, programmable device logic, and / or fixed device logic implemented in hardware form that may be used 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 the computer-readable storage medium described above.

[0119] Combinations of the foregoing may be used to implement 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 1510. The computing device 1502 may be configured to implement specific instructions and / or functions corresponding to the software and / or hardware modules. Thus, implementation aspects of modules executable by the computing device 1502 as software may be achieved at least in part in hardware, for example, through the use of a computer-readable storage medium and / or hardware elements 1510 of the processing system 1504. The instructions and / or functions may be executable / operable by one or more articles of manufacture (e.g., one or more computing devices 1502 and / or processing system 1504) to implement the techniques, modules, and examples described herein.

[0120] The techniques described herein may be supported by various configurations of computing device 1502 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 via a "cloud" 1514 via a platform 1516, as described below.

[0121] Cloud 1514 includes and / or represents a platform 1516 for resources 1518. Platform 1516 abstracts the underlying functionality of the hardware (e.g., servers) and software resources of cloud 1514. Resources 1518 may include applications and / or data available while computer processing is running on a server remote from computing device 1502. Resources 1518 may also include services provided over the Internet and / or through a subscriber network, such as a cellular or Wi-Fi network.

[0122] The platform 1516 may abstract resources and functionality for connecting the computing device 1502 with other computing devices. The platform 1516 may also function to abstract the scaling of resources to provide a level of scale corresponding to the encountered demand of the resources 1518 implemented via the platform 1516. Thus, in an embodiment of interconnected devices, implementation aspects of the functionality described herein may be distributed throughout the system 1500. For example, functionality may be implemented partially on the computing device 1502 as well as via the platform 1516 that abstracts the functionality of the cloud 1514.

[0123] 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]

[0124] 110 Glucose Monitoring Platform 120 User Interface Configuration Module 1502 Computing Devices 1504 Processing System 1506 Computer-readable medium 1508 I / O Interface 1510 Hardware Elements 1512 Memory / Storage 1514 Cloud 1516 Platform 1518 resources

Claims

1. A method implemented in a computing device, such as a smartphone and / or a smartwatch, comprising: obtaining a glucose measurement of a user, the glucose measurement being collected by a glucose monitoring device; processing the glucose measurements to determine a glucose insight, said processing comprising processing the glucose measurements to determine a plurality of glucose insights for the user; configuring a user interface to present visual elements representing the glucose insights based on configuration data, the configuration data mapping the plurality of glucose insights to different visual elements, controlling which glucose insight of the plurality of glucose insights is presented to the user at a given time and how the glucose insight is presented using the different visual elements, the configuration data including user specified preferences of which glucose insight of the plurality of glucose insights is presented to the user at the given time or how the glucose insight is presented, and including rules defining a progression of glucose insights for presentation to the user over time; displaying the configured user interface together with the visual element representing the glucose insight, wherein the configured user interface presents the visual element representing the glucose insight without a value representing the user's current glucose measurement.

2. 2. The method of claim 1, wherein the configured user interface presents the visual element representing the glucose insight without a glucose graph and / or simultaneously with a glucose graph plotting the glucose measurements of the user over a period of time.

3. The method of claim 1 or 2, wherein the configured user interface presents the visual element representing the glucose insight simultaneously with a value representing the user's current glucose measurement.

4. 4. The method of claim 1, wherein the processing further comprises processing the glucose measurements with additional data to determine the plurality of glucose insights, the additional data describing at least one of a physiological marker, a fitness or activity, a health event, a medication, a diet, a stress, a sleep, or a recovery event.

5. 2. The method of claim 1, wherein the configuring the user interface further comprises selecting the glucose insight from the plurality of glucose insights determined for the user based on the configuration data while preventing presentation of other glucose insights of the plurality of glucose insights.

6. A method described in any one of claims 1 to 5, further comprising selecting a visual element representing the determined glucose insight from a plurality of visual elements based on the configuration data.

7. The method of any one of claims 1 to 6, wherein the determined glucose insight is based on current glucose measurements of the user collected by the glucose monitoring device.

8. The method of any one of claims 1 to 7, wherein the determined glucose insight comprises a trend of the glucose measurements of the user over a period of time or comprises a rate of change of the glucose measurements of the user over a period of time.

9. The glucose insights include: an indication of whether the current glucose measurement is below, within, or above the glucose range; a trend of said glucose measurements over a period of time; the rate of change of said glucose measurement over said period of time; the variability of said glucose measurements over said period of time; comparing the variability of the glucose measurements over a current time period with the variability of the glucose measurements over one or more previous time periods; A comparison of the current glucose measurement with one or more other glucose measurements for the same or similar time on one or more different days; or 8. The method of any one of claims 1 to 7, comprising one of comparing one or more of the glucose measurements with one or more other glucose measurements for the same meal on one or more different days.

10. The method of any one of claims 1 to 7, wherein the configuring comprises configuring the user interface based on configuration data to present additional visual elements representing additional glucose insights determined for the user.

11. 11. The method of claim 10, wherein the glucose insight is based on the user's current glucose measurements and the additional glucose insight determined for the user includes trends in the collected glucose measurements of the user over a period of time.

12. 12. The method of claim 11, wherein the visual element comprises a color area representing whether the user's current glucose reading is below, within, or above a glucose range, and the additional visual element includes a shape representing whether the trend of the user's collected glucose readings is increasing, decreasing, or constant over the period of time.

13. A computer readable storage device having instructions stored thereon which, in response to execution by one or more processors, performs operations including the method of any one of claims 1 to 12.

14. A system including a computing device, such as a smartphone and / or a smartwatch, configured to implement the method according to any one of claims 1 to 12, the system comprising: processing means for processing the user's glucose measurements to determine glucose insight; configuration means for configuring a user interface to present visual elements representative of said glucose insight based on configuration data; and a display means for displaying the configured user interface together with the visual element representing the glucose insight.

Images