Systems, devices, and methods for in-range time and dietary related analyte monitoring

Abstract

Systems, devices, and methods for detecting and measuring an amount of time that an individual is within a predetermined analyte range based on analyte measurements. These results and related information are presented to the individual to show to the individual an analyte response associated with the consumed diet, or a change in analyte level over a predetermined period of time after the diet has been consumed. These results may be organized based on a rating system to allow an individual to visualize analyte responses and range effects associated with the diet. Various embodiments disclosed herein relate to methods, systems, and software applications aimed at attracting individuals by providing direct and timely feedback on the individual's dietary related analyte response.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority to U.S. Application Serial No. 63 / 535,134, filed on August 29, 2023, and U.S. Application Serial No. 63 / 416,750, filed on October 17, 2022, the entire disclosures of which are hereby incorporated by reference in their entirety for all purposes. Technical Field

[0003] The subject matter described herein generally relates to computational interfaces for analyte monitoring systems and related systems, methods, and devices. Specifically, various embodiments of in - range time (TIR) and diet - related graphical user interfaces for analyte monitoring systems are disclosed herein. Background Art

[0004] Over the past few decades, the rising prevalence of type 2 diabetes and metabolic syndrome has been attributed to changes in diet and activity levels. For example, consuming more readily available high - glycemic - index foods results in rapid increases in post - meal blood glucose and insulin levels, which are positively correlated with weight gain and obesity. These conditions can further translate into an increased risk of developing these and other diseases.

[0005] Most people generally understand the importance of their diet. However, in practice, many people have difficulty translating this general awareness into their specific food choices. These problems exist mainly because people cannot directly see the impact of their choices. This can lead to misunderstandings about portion sizes, misunderstandings about which foods are relatively healthy, and a general lack of awareness about the duration and intensity of activities necessary to maintain health. These problems are further exacerbated by advertising, habits, peer pressure, food preferences, and advice based on generalizations.

[0006] To address these problems, an analyte monitoring system can track and better understand an individual's physiological response. Since high glucose levels are mainly driven by food consumption, post - meal glucose levels can be related to the amount of carbohydrates and other dietary components consumed by an individual, as well as to the individual's physiological response to the meal. However, the challenge in analyzing this influx of data is to represent the data in a meaningful way to enable efficient action. Data related to dietary choices and subsequent effects should be understood on a clinical basis as well as on a personal basis so that individuals, diet managers, and / or healthcare professionals can understand and regulate glucose excursions, such as hyperglycemic episodes.

[0007] It has been shown that individuals who maintain analyte levels within a target analyte range are more likely to experience positive health outcomes. Accordingly, it would be advantageous to provide an individual with user-friendly and actionable information regarding the amount of time spent within the target analyte range; the impact of the meals consumed by the individual on their respective analyte levels; and means for motivating and encouraging the individual to make beneficial food choices.

[0008] Existing systems for tracking meal consumption and correlating the meals consumed with an individual's analyte data have numerous deficiencies. For example, some systems require an individual to perform many inconvenient and uncomfortable discrete blood glucose measurements (e.g., fingerstick blood glucose tests). These solutions may not be sufficient to fully determine the blood glucose response to a meal due to an insufficient number of data points. For example, an individual may perform a discrete blood glucose measurement at a time before or after the time at which the user's blood glucose response has peaked, making it difficult to accurately confirm the blood glucose response and difficult to meaningfully compare meals based on the blood glucose response. The insufficient number of data points also makes it difficult to detect the occurrence of a meal event in the user's analyte data. Accordingly, some existing systems rely heavily on the user to manually record meals. In addition, some prior art systems that seek to detect meal events based solely on the presence of an elevated glucose level are insufficient because they do not take into account the user's prior meal history and, as a result, will overestimate the amount of meals the user has consumed.

[0009] Accordingly, there is a need for improved systems, devices, and methods for meal information collection, meal assessment and detection, and correlation with analyte levels. In particular, there is a need for an improved graphical user interface for an analyte monitoring system that is robust, user-friendly, and allows an individual to understand the analyte response and analyte range impact associated with the meals consumed, as well as related methods and devices. SUMMARY OF THE INVENTION

[0010] Aspects of the invention are set forth in the independent claims, and the preferred features are set forth in the dependent claims. Features associated with one aspect may be applied, alone or in combination, to other aspects. Example embodiments of systems, devices, and methods for detecting and measuring the amount of time an individual is within a predetermined analyte range based on analyte measurements are provided herein. Example embodiments of systems, devices, and methods for detecting, measuring, and rating an individual's diet based on the individual's analyte measurements are also provided herein. In many embodiments, these results and related information are presented to the individual to show the analyte response associated with the consumed diet, or the change in analyte levels over a predetermined period of time after the diet is consumed. These individuals can be those who exhibit or are diagnosed with diabetes, those who are considered pre-diabetic, those who have metabolic syndrome, and even those who do not have symptoms of diabetes, pre-diabetes, or metabolic syndrome. These individuals can be anyone who can improve their health by regulating his or her diet and / or activity practices. The resulting information can be presented to the individual to show which diets or aspects of the diet have the greatest impact on analyte levels.

[0011] In many embodiments, an individual's diet-related analyte response (e.g., glucose response) is based on analyte data (e.g., glucose data) collected by an analyte monitoring system (e.g., glucose monitoring system), such as an in vivo analyte monitoring system (e.g., in vivo glucose monitoring system). These responses can be compared or linked to diet information to find common consistencies (or inconsistencies) and trends therein based on related historical glucose readings, associated algorithms, and comparisons.

[0012] Many embodiments disclosed herein are designed to engage the individual by providing direct and timely feedback regarding the individual's diet-related analyte response. In some embodiments, the analyte response can be provided to the individual in an easily understandable format to characterize the impact of diet consumption.

[0013] Many embodiments can immediately provide information to the individual, thereby encouraging the individual to take action to better understand how their own diet affects the analyte response of their body. Many embodiments can also organize the data based on the change in the individual's analyte levels detected over a predetermined period of time after consuming the diet, such as rating the diet. The individual can compare and contrast their current and historical analyte data to understand how their own efforts relate to better diet and food choices and how these choices directly affect their health. The individual can also better understand how specific food choices can help them stay within the target range of analyte values and visualize the analyte response and range impact associated with specific foods. In this way, the individual is motivated to stay within the target analyte range.

[0014] Many of the embodiments provided herein are for an improved graphical user interface (GUI) or GUI features for an analyte monitoring system that are highly intuitive, user-friendly, and provide quick access to an individual's physiological information. More specifically, these embodiments may allow an individual to easily navigate between different user interfaces that can quickly indicate to the user various physiological conditions and / or actionable responses and correlate analyte data with diet, exercise, stress, or other factors without the user (or HCP) having to perform the arduous task of reviewing large amounts of analyte data.

[0015] In many embodiments, some GUIs and GUI features allow an individual (and / or their caregiver) to better understand and improve their diet, eating habits, and manage other stressors when they see the correlation with these activities and their glucose levels. Similarly, in many embodiments, improved digital interfaces and / or features for TIR and diet-related systems can improve the visualization of the impact of food choices on analyte (glucose) levels and the amount of time spent within a target analyte range, the visualization of good and bad foods present in an individual's current diet and their impact on glucose levels and TIR, the correlation of dietary information with detected dietary events, and the motivation for an individual to maintain and / or increase TIR by informing the individual of food choices to eat while still maintaining TIR goals, to name a few. Other improvements and advantages are also provided. The various configurations of these devices are described in detail by way of embodiments only as examples.

[0016] The various aspects described and claimed herein for improvements to the GUI have at least a technical effect in assisting the user of the device to operate the device more accurately, efficiently, and safely. It will be understood that the information provided to an individual on the GUI, the order in which the information is provided, and the structural clarity of the information can have a significant impact on how the individual interacts with the system and how the system operates. Thus, the GUI guides an individual to accurately and efficiently read the necessary readings and / or obtain information in the technical tasks of operating the system.

[0017] Other systems, devices, methods, features, and advantages of the subject matter described herein will be or will become apparent to those skilled in the art upon examination of the following drawings and detailed description. All such additional systems, devices, methods, features, and advantages are included in this specification, are within the scope of the subject matter described herein, and are protected by the appended claims. In the absence of expressly stating these features in the claims, the features of the example embodiments should in no way be construed as limiting the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] By carefully reading the accompanying drawings, details of the subject matter set forth herein (both as to its structure and operation) may become apparent, in which like reference numerals refer to like parts. The components in the figures are not necessarily drawn to scale, but rather emphasis is placed upon illustrating the principles of the subject matter. In addition, all of the illustrations are intended to convey concepts, where relative sizes, shapes, and other detailed attributes may be depicted schematically rather than literally or precisely.

[0019] Figure 1 is a system overview of an analyte monitoring system that includes a sensor applicator, a sensor control device, a reader device, a network, a receiving computer system, and a local computer system.

[0020] Figure 2A is a block diagram depicting an example implementation of a reader device.

[0021] Figure 2B and Figure 2C is a block diagram depicting an example implementation of a sensor control device.

[0022] Figure 3 is a block diagram depicting an example implementation of an analyte monitoring system for use with an analyte monitoring application and / or a dietary monitoring application.

[0023] Figure 4A-1 is a flowchart depicting an example implementation of a method for correlating analyte data with dietary information and rating the dietary information.

[0024] Figure 4A-2 and Figure 4A-3 is a graph depicting a postprandial glucose profile.

[0025] Figure 4A-4 is a flowchart depicting an example implementation of a method for correlating analyte data with dietary information and rating the dietary information.

[0026] Figure 4A-5 is a flowchart depicting an example implementation of a method for displaying an interface including information related to a time within a range.

[0027] Figure 4B is a block diagram depicting an example implementation of a home page GUI.

[0028] Figure 4C is a block diagram depicting an example implementation of a time within a range information screen.

[0029] Figures 4D through 4N is a block diagram depicting an example implementation of a home page GUI, modalities, and their associated features.

[0030] Figures 5A through 5N is a block diagram depicting an example implementation of a dietary record GUI and modality.

[0031] Figure 6A is a flowchart depicting an example implementation of a method for displaying a report GUI.

[0032] Figure 6B-1 and Figure 6B-2 is a block diagram depicting an example implementation of a report GUI.

[0033] Figure 7 is a block diagram depicting an example implementation of a dietary impact GUI.

[0034] Figure 8 is a block diagram depicting an example implementation of a dietary review GUI.

[0035] Figures 9A through 9P is a block diagram depicting an example implementation of a onboarding GUI and its related features.

[0036] Figures 10A through 10M is a block diagram depicting an example implementation of an account and settings GUI and its related features.

[0037] Figures 11A through 11G is a block diagram depicting an example implementation of a data loss GUI and features.

[0038] Figures 12A-1 through 12B is a block diagram depicting an example implementation of an interface including activity cards and features.

[0039] Figure 13 is a flowchart depicting an example implementation of a method for dietary detection.

[0040] Figures 13A-1 through 13B-2 is a block diagram depicting an example implementation of a dietary detection interface and features.

[0041] Figures 14A-1 through 14E is a block diagram depicting an example implementation of an insights interface and features. Detailed Description

[0042] Example implementations of systems, devices, and methods for monitoring and measuring an individual's analyte response to a diet are provided herein. In particular, based on the collected analyte data, diet-related events and their impact on the individual's analyte levels can be further understood by the user and ultimately used to modify future diet choices and eating habits.

[0043] Before describing the subject matter in more detail, it is worth describing example implementations of systems, devices, and methods by which the subject matter can be implemented.

[0044] Multiple systems have been developed to automatically monitor analytes in body fluids such as blood flow, interstitial fluid ("ISF"), dermal layer fluid in the dermal layer, or other biological fluids, such as glucose. Some of these systems are configured such that at least a portion of the sensor is disposed beneath the surface of the user's skin (e.g., in the user's blood vessels or subcutaneous tissue) to obtain information about at least one analyte of the body.

[0045] As such, these systems can be referred to as "in vivo" monitoring systems. In vivo analyte monitoring systems include "continuous analyte monitoring" systems (or "continuous glucose monitoring" systems), which can continuously transmit data from a sensor control device to a reader device without prompting (e.g., automatically according to a schedule). In vivo analyte monitoring systems also include "transient analyte monitoring" systems (or "transient glucose monitoring" systems or simply "transient" systems), which can transmit data from a sensor control device in response to a scan or request for data by the reader device, such as using near field communication (NFC) or radio frequency identification (RFID) protocols. In vivo analyte monitoring systems can also operate without the need for fingerstick calibration.

[0046] In vivo analyte monitoring systems can be distinguished from "in vitro" systems that contact ex vivo (or more precisely "ex vivo") biological samples, and these systems typically include a meter device having a port for receiving an analyte test strip carrying the user's body fluid, which can be analyzed to determine the user's glucose level. While in many embodiments the monitoring is done in vivo, the embodiments disclosed herein can be used with in vivo analyte monitoring systems that incorporate in vitro capabilities, as well as pure in vitro or ex vivo analyte monitoring systems.

[0047] The sensor can be part of a sensor control device located on the user's body and includes electronics and a power source that enable and control analyte sensing. The sensor control device and its variants can also be referred to as a "sensor control unit", an "on-body electronics" device or unit, an "on-body" device or unit, or a "sensor data communication" device or unit, to name a few.

[0048] The in vivo monitoring system can also include a device that receives the sensed analyte data from the sensor control device and processes and / or displays the sensed analyte data in any number of forms. This device and its variants can be referred to as a "reader device" (or simply "reader"), a "handheld electronics" (or "handheld"), a "portable data processing" device or unit, a "data receiver", a "receiver" device or unit (or simply "receiver"), or a "remote" device or unit, to name a few. Other devices (such as personal computers) have also been used with or incorporated in in vivo and in vitro monitoring systems.

[0049] Embodiments of an In-Vivo Analyte Monitoring System

[0050] Figure 1 is a conceptual diagram depicting an example implementation of an analyte monitoring system 100 (e.g., a glucose monitoring system), which includes a sensor applicator 150, a sensor control device 102, and a reader device 120. Here, the sensor applicator 150 can be used to deliver the sensor control device 102 to a monitoring location on a user's skin, where the sensor 104 remains in place for a period of time via an adhesive patch 105. The sensor control device 102 is further described in Figure 2B and Figure 2C and can communicate with the reader device 120 via a communication path 140 using wired or wireless technology. Example wireless protocols include Bluetooth, Bluetooth Low Energy (BLE, BTLE, Bluetooth SMART, etc.), Near Field Communication (NFC), and others. The user can use a screen 122 (which can include a touch screen in many implementations) and an input device 121 to view and use applications stored in the memory installed on the reader device 120. The device battery of the reader device 120 can be recharged using a power port 123. Although only one reader device 120 is shown, the sensor control device 102 can communicate with multiple reader devices 120. Each reader device 120 can communicate with each other and share data. More details about the reader device 120 are elaborated below with respect to Figure 2A The reader device 120 can communicate with a local computer system 170 via a communication path 141 using a wired or wireless communication protocol. The local computer system 170 can include one or more of a laptop computer, a desktop computer, a tablet, a flat screen TV, a smart phone, a set-top box, a video game console, or other computing devices, and the wireless communication can include any one of a plurality of applicable wireless networking protocols including Bluetooth, Bluetooth Low Energy (BTLE), Wi-Fi, or others. The local computer system 170 can communicate with a network 190 via a communication path 143, similar to the way the reader device 120 can communicate with the network 190 via a communication path 142 using a wired or wireless communication protocol as previously described. The network 190 can be any one of a plurality of networks, such as a private network and a public network, a local area network or a wide area network, etc. The trusted computer system 180 can include a server and can provide authentication services and secure data storage, and can communicate with the network 190 via a communication path 144 using wired or wireless technology.

[0051] Example Embodiment of a Reader Device

[0052] Figure 2Ais a block diagram depicting an example implementation of a reader device 120 which, in some implementations, may include a smart phone. Here, the reader device 120 may include a display 122, an input component 121, and a processing core 206 which includes a communication processor 222 coupled to a memory 223 and an application processor 224 coupled to a memory 225. It may also include a separate memory 230, an RF transceiver 228 having an antenna 229, and a power supply 226 having a power management module 238. Additionally, the reader device 120 may also include a multi-functional transceiver 232 which may communicate with an antenna 234 via Wi-Fi, NFC, Bluetooth, BTLE, and GPS. As would be understood by one of ordinary skill in the art, these components are electrically and communicatively coupled in a manner that forms a functional device.

[0053] Example Embodiment of a Sensor Control Device

[0054] Figure 2B and Figure 2C is a block diagram depicting an example implementation of a sensor control device 102 having an analyte sensor 104 and sensor electronics 160 (including analyte monitoring circuitry) which may have most of the processing power for presenting final result data suitable for display to a user. In Figure 2B is depicted a single semiconductor chip 161 which may be a custom application specific integrated circuit (ASIC). Shown within the ASIC 161 are certain high-level functional units including an analog front end (AFE) 162, a power management (or control) circuit 164, a processor 166, and a communication circuit 168 (which may be implemented as a transmitter, receiver, transceiver, passive circuit, or otherwise according to a communication protocol). In this implementation, both the AFE 162 and the processor 166 serve as analyte monitoring circuitry, but in other implementations, either circuit may perform the analyte monitoring function. The processor 166 may include one or more processors, microprocessors, controllers, and / or microcontrollers, each of which may be a discrete chip or distributed among multiple different chips (and portions thereof).

[0055] The memory 163 is also included within the ASIC 161 and can be shared by the various functional units present within the ASIC 161 or can be distributed among two or more of them. The memory 163 can also be a separate chip. The memory 163 can be volatile and / or non-volatile memory. In this embodiment, the ASIC 161 is coupled to a power source 172, which can be a coin cell battery or the like. The AFE 162 interfaces with the in-vivo analyte sensor 104 and receives measurement data therefrom and outputs the data in digital form to the processor 166, which in turn processes the data to arrive at final results such as glucose discrete values and trend values. Then, this data can be provided to the communication circuit 168 for transmission via the antenna 171 to a reader device 120 (not shown), for example, where a software application residing in the data receiving device requires minimal further processing to display the data.

[0056] Figure 2C Similar to Figure 2B , but alternatively includes two discrete semiconductor chips 162 and 174, which can be packaged together or separately. Here, the AFE 162 resides on the ASIC 161. The processor 166 is integrated with the power management circuit 164 and the communication circuit 168 on the chip 174. The AFE 162 includes the memory 163, and the chip 174 includes the memory 165, which can be isolated or distributed therein. In one exemplary embodiment, the AFE 162 is combined with the power management circuit 164 and the processor 166 on one chip, while the communication circuit 168 is on a separate chip. In another exemplary embodiment, both the AFE 162 and the communication circuit 168 are on one chip, and the processor 166 and the power management circuit 164 are on another chip. It should be noted that other chip combinations including three or more chips are possible, with each chip taking responsibility for the individual functions described or sharing one or more functions for fail-safe redundancy.

[0057] Example Embodiment of a Software Application within a Time Range

[0058] In many embodiments, the subject matter described herein is implemented by a software application that is stored in memory and executed by a processor-based device, such as a reader device (e.g., a smart phone), a drug delivery device, a receiving computer system, a local computer system, or any other computing device described herein. In certain embodiments, the software is implemented as one or more downloadable software applications ("Apps") on a reader device, such as a mobile communication device or a smart phone. In certain embodiments, the software and its associated features and functions may be implemented on a single centralized device, or alternatively, may be distributed across multiple discrete devices at geographically dispersed locations. Also, those skilled in the art will recognize that the representations of the various computer systems in the embodiments disclosed herein, as Figure 1 shown, are intended to encompass both physical computing devices and virtual computing devices (e.g., virtual servers or virtual machines).

[0059] Generally, the software may provide a mechanism for a user to define consumables (e.g., food types, beverage types, or portions thereof) in a user-friendly manner. These consumables will generally be referred to herein as a meal or meals, and these terms are used broadly to represent all types of food and drink.

[0060] According to one aspect of many embodiments, the software may perform a number of functions related to collecting meal information and associating the meal information with analyte information collected by an in vivo analyte sensor 104 or an in vitro test strip and meter, or analyte information from a receiving computer system 180. The software will generally be referred to hereinafter as the "Time in Range Application", the "TIR Application", or the "Meal Monitoring Application".

[0061] According to another aspect of many embodiments, the TIR Application may be used by diabetic patients, including patients with type 2 diabetes who are on basal insulin, or type 1 or type 2 patients on multiple-dose insulin therapy who have a potential motivation to change their diet. It may also be used by pre-diabetic patients or non-diabetic patients who want to minimize their glucose excursions by controlling their diet. Users of the TIR Application may have poorly controlled diabetes and desire to control their diabetes, but have found that following a prescribed "diabetes diet" over a long period of time is unsustainable because they do not want to give up their favorite foods. Users of the TIR Application may also be controlling their diabetes, but their daily diet is no longer working because they are, for example, taking new medications, starting a new exercise program, pregnant, or experiencing other life changes.

[0062] The TIR application can allow an individual to record information about each meal (i.e., each "meal event") consumed by the individual. The TIR application can associate analyte data from the user's log entries indicating the relevant time period during which the meal was consumed.

[0063] In some embodiments, the TIR application classifies food choices based on the blood glucose (or other analyte) response. It can be used in conjunction with the analyte monitoring system 100 to help people better understand the impact of their diet on their glucose levels. The TIR application can associate the measured analyte response with the meal event and store the results in a non-transitory memory or database. In particular, the TIR application can display to the user each meal and its associated analyte (e.g., glucose or other analyte) response, for example, in the form of a list where each meal is rated and sorted by the degree of decrease in the blood glucose response amplitude (taking glucose as an example). The user can directly see how food choices and portion sizes affect their glucose levels. The user can learn which foods have the greatest impact. The TIR application also helps to dispel myths about healthy eating (e.g., problematically high-carbohydrate foods that may be wrongly considered healthy, such as orange juice and breakfast cereals).

[0064] In many embodiments, the TIR application can enable the user to see the good and bad foods (or good and bad dietary behaviors) present in their current diet in order to assist the user in determining what modifications they can make to achieve improved glucose control and increase the time their glucose levels remain within the target range. The TIR application can assist the user by providing data visualizations of the glucose responses and TIR impacts of different food choices. The TIR application can also provide an easy-to-understand score for the recorded meals based on the change in the user's glucose levels detected within a predetermined time period (e.g., three hours) after eating. In some embodiments, for example, meals with higher scores can correspond to meals associated with lower blood glucose responses. Additionally, meals with lower scores can correspond to meals associated with higher blood glucose responses. In this way, meals with higher scores indicate to the user that specific food choices can help them stay within the target range of analyte values. In some embodiments, the TIR application can gamify the TIR in order to motivate the user to make beneficial food choices and increase the TIR metric.

[0065] TIR applications can utilize and evaluate the amount of time that a user is within a certain value range to evaluate the glucose impact of a meal (and other events). For example, a TIR application can evaluate the amount of time that a user is within a certain value or TIR range (e.g., within a target glucose range of about 70 mg / dL to about 180 mg / dL). In some embodiments, the target range can be set by the user. For example, the target range can be set to about 80 mg / dL to about 170 mg / dL. The lower limit of the target range can be at least about 65 mg / dL, such as about 70 mg / dL or about 80 mg / dL. The upper limit of the target range can be no more than about 180 mg / dL, such as about 170 mg / dL or 120 mg / dL. If a user meets the current assigned goal or objective after a certain predetermined period of time, the goal can also be incrementally and automatically adjusted by the TIR application (without user intervention). For example, if a user has achieved their goal of having 30% of their glucose measurements within the target range, e.g., in the past week, the TIR application can set a new goal for the user to maintain 35% of the measured analyte levels within the target range. Similarly, if the goal of having 30% of their glucose measurements within the target range has not been achieved, the TIR application can set a new goal for the user to maintain 25% of the measured analyte levels within the target range. However, those skilled in the art will understand that other target ranges can be utilized in addition to the target ranges listed or described herein, and these numbers are not meant to be limiting.

[0066] TIR can be determined as a percentage value by dividing the time that the analyte level is within a certain range by the total time period. For example, if glucose is within the TIR threshold for 6 hours within a total period of 24 hours, the TIR metric is 25%. Alternatively, the metric can be displayed based on time increments rather than percentages; using the above example, the TIR would be 6 hours (within a total period of 24 hours).

[0067] In many embodiments, users of the TIR application can continuously monitor their glucose, such as by utilizing the sensor control device 102 of system 100 as described in Figure 3As can be seen in, analyte levels can be transmitted (i) from sensor 104 to the analyte monitoring application 310; (ii) from the analyte monitoring application 310 to the cloud including server 320; (iii) from server 320 to the TIR application 330. In some embodiments, the cloud 320 can include one or more servers with the same or different functions. For example, analyte data can be uploaded to a first server or group of servers responsible for collecting analyte data, and then downloaded by a second server or group of servers responsible for downloading the data for use by the within-range time application to the TIR application. Those skilled in the art will also understand that the analyte monitoring application 310 and the TIR application 330 can reside on a single device (such as, for example, a single smart phone), or, alternatively, can reside on two different devices (such as, for example, two smart phones, or a smart phone and a dedicated receiver).

[0068] Additional details regarding the features and interfaces of the within-range time software application can be found in U.S. Patent Publications No. 2017 / 0128007, No. 2021 / 0030323, and No. 2022 / 0000399, which are hereby incorporated by reference in their entireties for all purposes, and any one of these features and interfaces can be implemented and / or used in combination with the embodiments described herein.

[0069] Example Embodiment of a GUI and Related Features for a Time-in-Range ("TIR") Application

[0070] Example embodiments of various GUIs and related software features for the TIR application will now be described. Those skilled in the art will understand that these various interfaces can be displayed on any of the embodiments of the reader device 120 (such as, for example, a smart phone), the drug delivery device 160, the receiving computer system 180, or the local computer system 170 described herein. These interfaces and their associated features and functions can be implemented on a single centralized device, or, alternatively, can be distributed across multiple discrete devices in geographically dispersed locations. Those skilled in the art will understand that any one or more example embodiments of the methods, interfaces, and systems described herein can be implemented independently, or in combination with any other embodiment described in this application. Additionally, although many of the embodiments described herein relate to glucose monitoring, those skilled in the art will understand that these same embodiments can be implemented for the purpose of monitoring other analytes (such as, for example, lactate and ketones). Further, those skilled in the art will understand that the embodiments described herein are not limited to monitoring one analyte at a time, although each of the embodiments described herein is capable of doing so.

[0071] Example Embodiment of a Home Page GUI and Related Methods

[0072] Example embodiments of a method for correlating analyte data with dietary information will now be described. First, those skilled in the art will recognize that the method steps described herein can include software instructions stored in the memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of system 100 such that the instructions, when executed by one or more processors of the computing device, cause the one or more processors to perform any or all of the method steps described herein. Turning to Figure 4A-1 , the flowchart depicts an example embodiment of a method 4000 for correlating analyte data with dietary information, where the dietary information has been input by a user. As Figure 4A-1 seen at the top of, method 4000 begins at 4001, where dietary information is input by the user. In some embodiments, for example, this can be a dietary entry or an entry in a dietary log that is entered proactively by the user without any prompting from the TIR application. In other embodiments, the user can input dietary information in response to a prompt displayed by the TIR application. For example, according to some embodiments, if no dietary entry has been made after a predetermined reminder period (e.g., no dietary entry in the past week, no dietary entry in the past three days, no dietary entry in the past day, etc.), the TIR application can be configured to display a reminder notification to the user.

[0073] Subsequently, at 4002, the TIR application receives data indicative of the user's analyte level within a predetermined amount of time. In some embodiments, this may require the user to scan their sensor control device within a predetermined amount of time from the time of the dietary entry (e.g., within three hours of the dietary entry, within four hours of the dietary entry, within eight hours of the dietary entry, within twelve hours of the dietary entry, etc.). In other embodiments, this can occur when the sensor control device is configured to transmit analyte data autonomously and wirelessly to the reader device.

[0074] Still referring to Figure 4A-1, at 4003, identify the peak analyte value in the analyte data. In some embodiments, this may involve identifying the highest glucose value that exceeds a predetermined analyte level threshold (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL, etc.). In some embodiments, if the newly identified highest glucose value is higher than the previous highest glucose value, the peak analyte value will be updated to the newly identified highest glucose value. The peak analyte value can also be the glucose value that exceeds the predetermined analyte level threshold during a time window after a meal entry (e.g., during a one-hour window after a meal entry, during a two-hour window after a meal entry, during a three-hour window after a meal entry, during a four-hour window after a meal entry). In some embodiments, the peak analyte value can also be the glucose value that exceeds the predetermined analyte level threshold before the meal entry time (e.g., three hours before the meal entry). When determining the peak analyte value before the meal entry time, the post-meal period ends early to allow the user to receive a score (as described below) before the full time window (e.g., a full three-hour window) after the time the peak analyte value is determined.

[0075] According to one aspect of the embodiment, if the percentage difference between the most recent analyte value and the peak analyte value is less than a predetermined threshold, the detection of the peak analyte value will stop. In some embodiments, the detection of the peak analyte value will stop after a predetermined amount of time (e.g., three hours) has elapsed after the meal entry.

[0076] Then, at 4004, determine the initial analyte level value. According to some embodiments, the initial analyte level value can be determined by confirming the analyte level value at or near the meal entry time (e.g., within fifteen minutes before or after the meal entry).

[0077] In some embodiments, the historical analyte data range is defined as the post-meal period, where the post-meal period ranges from the time of the initial analyte level value (e.g., fifteen minutes before or after the meal entry, thirty minutes before or after the meal entry, or one hour before or after the meal entry) to the end time of the peak analyte value (e.g., two hours after the meal entry, three hours after the meal entry, four hours after the meal entry). In some embodiments, the end of the post-meal period can be one of the following two events that occur first: (1) the first analyte (e.g., glucose) reading within three hours from the initial analyte level value, or (2) the last analyte (e.g., glucose) reading before a new meal entry is input.

[0078] Subsequently, in some embodiments, at 4005, an analyte level offset value can be determined, for example, by subtracting an initial analyte level value from a peak analyte level value. Then, at 4006, the analyte level offset value can be associated with a dietary entry input by a user and stored together in a memory. Then, at 4007, and based on the analyte level variance, a score or rating is assigned to a particular meal associated with the input dietary information. In some embodiments, a particular meal is scored only after the end of a post-meal period. In some embodiments, a score for each of one or more meal events is calculated based on a glucose response based on data indicative of glucose levels associated with each meal event.

[0079] In some embodiments, if certain threshold conditions are met, the meal is not scored. For example, a first threshold condition can be less than a minimum number of analyte readings (e.g., eight glucose readings) within a post-meal period, and / or a peak analyte value is not detected before a predetermined time window (e.g., a three-hour time window) has elapsed since the meal entry time. Additionally, in some embodiments, a second threshold condition can be when the post-meal period is less than a predetermined period (e.g., two hours). In some embodiments, if a new meal entry is input within a predetermined period after a previously input meal entry (e.g., within three hours after an existing recorded meal entry), a peak analyte value cannot be detected and the meal cannot be scored. Additionally, in some embodiments, if a new meal entry is input before a peak analyte value is detected, the new meal cannot be scored.

[0080] According to some embodiments, assigning or calculating a meal score at 4007 can further take into account certain physiological conditions present in the user's body before consuming the meal. More specifically, certain individuals with diabetes can have high initial analyte level (e.g., glucose level) values before consuming a meal. For example, some individuals with type 2 diabetes who still have the ability to produce insulin to metabolize glucose may often exhibit high pre-meal glucose levels. Thus, the endogenous insulin present in those individuals' bodies before consuming the meal can affect the response to the meal and can attenuate the analyte level offset value (also referred to as "PeakDelta"). For illustration, Figure 4A-2 and Figure 4A-3Post - prandial glucose trajectories 4100 and 4150 of the same meal for an individual at different times are shown respectively. The second graph line 4150 on the right depicts an initial analyte level value of approximately 150 mg / dL (also known as the pre - meal glucose level) and a PeakDelta value of approximately 100 mg / dL. The first graph line 4100 on the left depicts a pre - meal glucose level of approximately 180 mg / dL and a PeakDelta value of approximately 70 mg / dL for the same meal consumed. Thus, for an individual with a high pre - meal glucose level, the PeakDelta value or the analyte level offset value will decay.

[0081] To account for the higher initial analyte levels of certain users, according to some embodiments, the PeakDelta value can be adjusted. For example, the PeakDelta value can be adjusted according to the following example equation:

[0082] PeakDeltaAdj = PeakDelta + f(G 餐前 ) (1)

[0083] As explained above, PeakDelta is the analyte level offset value, or the difference between the peak analyte level value after a meal and the initial analyte level. PeakDeltaAdj is the adjusted analyte offset value, and G 餐前 is the initial analyte level. In some embodiments, G 餐前 is the glucose level at a timestamp before the meal label timestamp. In other embodiments, G 餐前 is the minimum glucose level before the meal label timestamp within a predetermined duration (e.g., one hour, ninety minutes, two hours, three hours, etc.).

[0084] Additionally, according to some embodiments, f(G 餐前 ) can be represented by the following linear function:

[0085] f(G 餐前 ) = a ×G 餐前 + b (2)

[0086] The variables a and b can be constants determined based on simulations of a virtual type 2 diabetic patient population that consumes various meals, including varying amounts of carbohydrates, fat content, and protein content. In other embodiments, the variables a and b can be constants determined from in - vivo data. Those skilled in the art will understand that other methods of determining the variables a and b can be utilized using one or more of simulation data, in - vivo data, population data, or other test data. The first variable a can be multiplied by G 餐前 , while the second variable b can be added to G 餐前Add the product with a. In some embodiments, for example, a = 0.4 and b = -50 mg / dL.

[0087] According to some embodiments, if data is available for multiple instances of the same meal (or the same type of meal) consumed at different times / days, the weighted average of variables a and b can be used to calculate the adjusted analyte level offset value PeakDeltaAdj. In particular, for multiple instances of the same meal, G 餐前 and G 峰值 values can be correlated. Additionally, in some embodiments, the values of multiple instances of the same meal can be further grouped by meal period (e.g., breakfast, lunch, or dinner). For each meal with more than one instance, variables a and b can be estimated as a est and b est . For meals with associated a est and b est values, a weighted average calculation of each parameter can be performed, where meals with more instances are weighted more. Subsequently, the PeakDeltaAdj value can be determined based on the most recent weighted average parameters of a particular user.

[0088] Those skilled in the art will understand that other variables and / or constants can be utilized in the equations described herein without departing from the scope of the present disclosure.

[0089] According to other embodiments, when PeakDelta is low, a logic function can be utilized to minimize the impact of G 餐前 . This can be used to reduce the improper scoring of small meals with minimal analyte level offset values. An example embodiment of the logic function is represented by the following equation:

[0090]

[0091] PeakDeltaAdj = k(a × Gpremal + d - b) + (1 - k)d (4)

[0092] In the above equation, d is PeakDelta, and a and b are constants.

[0093] In addition, according to some embodiments, one or more data validity checks may be performed before calculating the PeakDeltaAdj value. For example, in some embodiments, a first data validity check may be performed to determine whether a predetermined time window (also referred to as an offset period) after the dietary label timestamp contains at least two (2) hours of glucose data. As another example, a second data validity check may be performed to determine whether there is another dietary label within the offset period, and if so, to determine whether the offset period contains at least two (2) hours of glucose data before the dietary label.

[0094] According to another aspect of some embodiments, the scoring metric itself may be a function of G 餐前 and / or G 峰值 function.

[0095] Figure 4A-4 is a flowchart depicting an exemplary embodiment of a method 4200 for correlating analyte data with dietary information indicating a user's high pre-meal glucose level. As Figure 4A-4 seen at the top of, method 4200 begins at 4201, where software receives dietary information entered by the user. In many embodiments, this may be a timestamped dietary label entered by the user, and these timestamps may be associated with glucose data received from a sensor control device worn by the user. At 4202, for each dietary label, the meal time is registered with the glucose data to reflect the post-meal offset. That is, from the analyte data and the dietary label, it should be possible to confirm the initial analyte level value and the peak analyte level value for each meal. Subsequently, at 4203, one or more data validity checks may be optionally performed as described above. If the one or more data validity checks fail, the software may indicate that the meal is not scorable. In some embodiments, the software may prompt the user to correct the non-scorable meal by entering more analyte data, by correcting the dietary label information, or by other means. In some embodiments, the software may prompt the user to delete the non-scorable dietary label.

[0096] Still referring to Figure 4A-4 , if the one or more data validity checks have passed, then at 4205, the initial analyte value (Gpremeal) and the peak analyte level value (Gpeak) are identified. Then, any of the methods described above may be used to calculate the adjusted analyte level offset value (PeakDeltaAdj). Subsequently, at 4206, a meal score may be calculated or a meal score may be assigned to the meal based on the adjusted analyte level offset value (PeakDeltaAdj). Optionally, at 4207, all of the user's meals may be rated according to their assigned scores.

[0097] Figure 4A-5 Method 4300 for performing a process for displaying TIR information and non-medical data from a sensor control device 102 is shown. First, those skilled in the art will also recognize that any combination, subset, or all of the steps of method 4300 can be implemented in combination with any combination, subset, or all of the steps of methods 4000 and / or 4200 described above. For ease of explanation, in this and other embodiments described below, the analyte being monitored will be glucose, but other analytes can also be monitored, as noted herein.

[0098] Referring Figure 4A-5 , at 4301, the method for the interface includes receiving, by at least one processor, data indicating an analyte level (e.g., data indicating a glucose level) from the sensor control device 102.

[0099] At 4302, the method further includes determining, by at least one processor, the amount of time that the data indicating the analyte level is within a value range or a predetermined analyte range. For example, the predetermined analyte range can be defined by a glucose value range between 70 mg / dL and 180 mg / dL.

[0100] At 4303, method 4300 can include providing an interactive graphical user interface to a display device, the interactive graphical user interface being configured to display the data indicating the analyte level based on the determination, wherein the display device indicates the amount of time that the data indicating the analyte level is within the predetermined analyte range. According to some embodiments, for example, the amount of time that the data indicating the analyte level is within the predetermined analyte range can be displayed in terms of an increment or a percentage value and can be graphically represented as a portion or segment of a circle or a ring, wherein the area of each portion or segment is proportional to the percentage value. In other embodiments, the graphical representation can be a pie chart, one or more bars or bar segments, a line graph, one or more 23arvey balls, a thermometer, a digital gauge (e.g., a speedometer), or any other geometric shape or image configured to reflect the user's progress.

[0101] Referring Figure 4B, which shows a block diagram depicting an example implementation of a home page GUI 400 for a TIR application. According to one aspect of the implementation, the home page GUI 400 may include: (1) a TIR card 401; (2) a logbook section 4008, including a list 402 of meal events 419; (3) a selectable home page icon 403, which outputs the home page GUI 400 when selected by the user; (4) a selectable meal icon 404, which outputs a meal report GUI when selected by the user, the meal report GUI including information about one or more meal events that occurred during a previous time period (e.g., the past week); and (5) a “+” icon 405, which outputs a meal record GUI 500 configured to receive meal information input by the user when selected by the user (see, for example Figures 5A through 5G ). In some implementations, the TIR card 401 may include a graphical element indicating the amount of time the user was within the target analyte range (“time in range” or “TIR”) during a predetermined time period (e.g., a 24-hour period). In some implementations, although not illustrated, the home page GUI 400 may include a selectable insights icon instead of the meal icon 404. Specifically, although Figure 4B is not illustrated, when the user selects the insights icon, an insights GUI 14000 is output (e.g., Figures 14A-1 through 14A-4 ), which will be described in further detail below.

[0102] In some implementations, the TIR card 401 may use graphical elements (such as a TIR circle or ring 406) to highlight the hours within the range. As shown in Figure 4BAs seen in, the TIR card 401 shows a TIR ring 406, where the daily TIR target 407 (hours within the TIR) is located in the inner or interior region of the TIR ring 406. For example, the daily TIR target 407 can include a numerical value and unit of measurement indicating the user's predetermined TIR target (e.g., "16 hours"). In some embodiments, the current number of hours the user has spent within the predetermined target range can be displayed in two ways: (1) the TIR value 408 can be the numerical value and unit of measurement (e.g., "9 hours") listed inside the ring together with the daily TIR target 407; and (2) the number of hours can be visually displayed as a progress indicator 418 (e.g., a shaded portion) that extends along the circumference of the TIR ring 406 to X% of the total circumference of the TIR ring 406, to indicate that the user has spent X% of the TIR (e.g., where X% is the amount of hours spent within the range divided by 24 hours). In this way, the ratio of the circumference of the TIR ring including the progress indicator 418 (e.g., the shaded portion) to the total circumference of the TIR ring 406 is proportional to the ratio of the amount of time the user has spent within the predetermined target analyte range in a day. In some embodiments, the progress indicator 418 can include a color with a gradient configured to transition between various shades. In this way, the degree to which the color gradient transitions between various shades indicates the user's progress towards reaching their daily TIR target 407. In some embodiments, the TIR value 408 can be represented by a numerical value such as a percentage unit or number of hours, without the TIR ring 406 or progress indicator, etc.

[0103] Those skilled in the art will further recognize that other types of progress indicators (e.g., text, numbers, or graphics) can also be utilized, and these indicators are fully within the scope of the present disclosure. Additionally, although the graphical elements shown are circles or rings with shaded portions including gradients, those skilled in the art will understand that other geometric shapes, colors, and numbers of portions or gradients can be utilized, and these portions or gradients are fully within the scope of the present disclosure.

[0104] In some embodiments, the TIR card 401 can also include a selectable information icon 409 that, when selected by the user, outputs a TIR information screen 410 related to the TIR card 401. For example, and as Figure 4CAs depicted, the TIR information screen 410 provides details on how the TIR ring 406 visually displays the progress indicator 408 and the daily TIR goal 407. In some embodiments, the TIR information screen 410 also informs the user that the TIR goal setting is configurable. In some embodiments, the home page GUI 400 also includes a selectable settings icon 411 that, when selected, outputs a settings GUI in which the user can adjust the TIR goal setting, e.g., change the daily TIR goal 407 and the metric for displaying the TIR data (e.g., showing the TIR value 408 or the daily TIR goal 407 in hours or as a percentage). In some embodiments, and as Figure 4B illustrated, the home page GUI 400 also includes a message 412 adjacent to the TIR card, where the message 412 indicates the time when the TIR card 401 was last updated.

[0105] Referring Figure 4B to, the home page GUI 400 may include a logbook section 4008 that has a list 402 of dietary information that includes one or more dietary events 419 that occurred within a predetermined period (e.g., one day). Each dietary event 419 provides details of a specific meal consumed within the predetermined period. In some embodiments, each dietary event 419 may include a text description 413 of the meal (e.g., "blueberry oatmeal"), a portion indicator 414 (e.g., "typical") that describes the relative portion of the meal (e.g., typical, larger, or smaller compared to the user's daily meal allowance), and / or a timestamp 415 associated with the time of consumption of the meal (e.g., "8:04 AM"). Although not illustrated, in some embodiments, the dietary event 419 may include one or more dietary tags 416 associated with the meal. The user can use the dietary tags 416 (not shown) to describe the content or characteristics of the meal or list the types of food, e.g., vegetables, chicken, beef, pork, fish, salad, pasta, or vegetarian, to name just a few examples of tags. Additionally or alternatively, the dietary event 419 may include a photo / picture 417 associated with the meal. In some embodiments, the user can take a photo of the meal or, alternatively, select a photo from a photo library. In some embodiments, when the user does not associate a photo 417 with the meal, a placeholder photo / picture 417 will be displayed instead. In some example embodiments, the list 402 can be sorted such that the dietary events 419 corresponding to the most recently consumed meals are presented first or at the top of the list, and subsequent dietary events 419 are displayed in chronological order.

[0106] As Figure 4BAs illustrated, each dietary event 419 may additionally or alternatively include a rating or score 420 for a single specific meal based on the analyte response associated therewith. In some embodiments, the analyte response may be based on the change in analyte levels over a predetermined period of time after consuming the specific meal. In some embodiments, a score 420 is given to the meal based on the analyte level offset value from the time of consumption of the specific meal to the peak glucose within three hours of eating.

[0107] Additionally, the score 420 may be displayed as a numerical value. In some embodiments, the score 420 may be a number between one and five, where a higher assigned numerical value corresponds to a lower analyte response and a lower assigned numerical value corresponds to a higher analyte response.

[0108] For example, (1) a change in analyte levels from 0 mg / dL to 20 mg / dL within the two-hour period after a meal may correspond to a "5" score 420; (2) a change in analyte levels from 21 mg / dL to 40 mg / dL within the two-hour period after a meal may correspond to a "4" score 420; (3) a change in analyte levels from 41 mg / dL to 60 mg / dL within the two-hour period after a meal may correspond to a "3" score 420; (4) a change in analyte levels from 61 mg / dL to 90 mg / dL within the two-hour period after a meal may correspond to a "2" score 420; and (5) a change in analyte levels of 91 mg / dL or higher within the two-hour period after a meal may correspond to a "1" score 420. As another example, (1) a change in analyte levels from 0 mg / dL to 24 mg / dL within the three-hour period after a meal may correspond to a "5" score 420; (2) a change in analyte levels from 25 mg / dL to 49 mg / dL within the three-hour period after a meal may correspond to a "4" score 420; (3) a change in analyte levels from 50 mg / dL to 74 mg / dL within the three-hour period after a meal may correspond to a "3" score 420; (4) a change in analyte levels from 75 mg / dL to 99 mg / dL within the three-hour period after a meal may correspond to a "2" score 420; and (5) a change in analyte levels of 100 mg / dL or higher within the three-hour period after a meal may correspond to a "1" score 420. Those skilled in the art will understand that other changes in analyte levels may be used with different scores (including more or fewer scores) and are fully within the scope of the present disclosure.

[0109] As depicted in the home page GUI 400, the score 420 can be displayed in a graphical element, such as the asterisk icon 421. In some embodiments, the asterisk icon 421 is filled with a colored portion, such as yellow. In many embodiments, the asterisk icon 421 is unfilled and includes a dashed outline to indicate a missing meal score 420. Those skilled in the art will understand that other graphical representations and symbols (e.g., emojis, trophy icons, bars, triangles, squares, circles, etc.) can be used instead of the asterisk icon. A missing meal score 420 occurs when one or both of the following happen: (1) the user records the next meal too quickly (e.g., when the user records the next meal before sufficient analyte data has been collected to score the current meal), or (2) the TIR application does not have sufficient analyte data to score the meal 420 (e.g., the user has not been scanned in a timely manner to ensure that glucose data has been transmitted to the TIR application). In some embodiments, the score information icon 422 is displayed adjacent and proximal to the meal information list 402 on the home page GUI 400. When selected by the user, the score information icon 422 outputs a meal score information modal that includes information about different score options and how the meal score is determined.

[0110] Still referring to Figure 4B , the home page GUI 400 may further include a text description 423 indicating the current day of the week, wherein the text description 423 includes a date adjacent to a switch 424 configured to be toggled. In some embodiments, the home page GUI 400 may be associated with the past day, wherein the text description includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the home page GUI 400 is associated with the past day, the home page GUI 400 may further include a selectable "Go to Today" link that, when selected, outputs the home page GUI 400 corresponding to the current day.

[0111] In some embodiments, when the user toggles the switch 424 downward, the home page GUI 400 is configured to display a plurality of selectable rings 425 ( Figure 4B not shown in ), each ring corresponding to a different day of the past week. For example, when the switch 424 is toggled downward, the home page GUI 400 may display a plurality (seven) of rings 425 ( Figure 4B(not shown in the figure), one ring corresponds to each day of the week. Similar to the TIR ring 406 shown on the TIR card 401, each of the multiple rings 425 represents the progress the user has made towards the daily TIR goal for that particular day. For example, the number of TIR hours the user spends on a particular day can be visually displayed as a progress indicator 426 (e.g., the shaded portion) that extends along the circumference of the ring 425 to X% of the total circumference of the ring 425, to indicate that the user has spent X% of the TIR (where X% is the amount of hours spent within the range divided by 24 hours).

[0112] In some embodiments, when the user selects a particular ring from the multiple rings 425, the report GUI 600 will be displayed (e.g., Figure 6B-1 ). In some embodiments, when the switch 424 is toggled to the upward position, the multiple rings 425 are no longer displayed. Embodiments of the report GUI 600 will be described in further detail below.

[0113] Referring to Figure 4D , a block diagram depicting an example embodiment of the home page GUI 450 for a TIR application is shown. According to one aspect of the embodiment, the home page GUI 450 may include: (1) an analyte graphics card 451; (2) a logbook section 4508, which includes a list 452 of dietary events 469; (3) a selectable home page icon 453, which outputs the home page GUI 400 when selected by the user; (4) a selectable dietary icon 454, which outputs a dietary impact GUI 800 ( Figure 8 ) when selected by the user, and the dietary impact GUI includes information about one or more dietary events 469 that occurred during a previous time period (e.g., the past week); and (5) a “+” icon 455, which outputs a dietary record GUI 500 (not shown) configured to receive dietary information input by the user when selected by the user. In some embodiments, although not illustrated, the home page GUI 450 may include a selectable insights icon instead of the dietary icon 454. Specifically, when the user selects the insights icon, an insights GUI 14000 is output (e.g., Figures 14A-1 through 14A-4 ), which will be described in further detail below.

[0114] In some embodiments, the home page GUI 450 is displayed in response to a first predetermined input by the user on the home page GUI 400 (such as when the user drags or swipes with a finger or by some other predetermined gesture). In a similar manner, the home page GUI 400 can be displayed in response to a second predetermined input by the user on the home page GUI 450 (such as when the user drags or swipes with a finger or by some other predetermined gesture).

[0115] In some embodiments, the home page GUI 450 is similar toFigure 4B The implementation of the home page GUI 400 depicted, except that the home page GUI 450 displays an analyte graph card 451 instead of a TIR card. In some implementations, the home page GUI 451 may include an analyte graph 460 with an analyte trend line 461 that reflects the user's analyte level over a predetermined period based on data indicating the analyte level. For example, and as Figure 4D shown, the x-axis of the analyte graph 460 may include time units (e.g., three-hour increments, etc.) covering a twelve-hour period, while the y-axis may include measurement units of the measured user analyte concentration (e.g., mg / dL). Such an analyte graph 460 may show data for any desired period, and those skilled in the art will further recognize that other predetermined periods (e.g., two hours, four hours, twenty-four hours, forty-eight hours, etc.) may be reflected on the x-axis and are fully within the scope of the present disclosure. According to some aspects of the implementation, the glucose concentration (in units of mg / dl or mmol / L) of the user within a certain period (e.g., a day or part of a day) is displayed. The time shown on the x-axis may indicate the glucose concentration measured starting from 12:00 am of the current day.

[0116] The analyte graph 460 may include solid lines 462-1, 462-2 to indicate the user's target analyte range associated with the data indicating the analyte level. For example, the area between the solid lines 462-1, 462-2 indicates the target analyte range (e.g., between 70 mg / dL and 180 mg / dL). In some implementations, and as Figure 4D illustrated, the analyte trend line 461 is configured as a dashed or broken (dashed) line to represent the periods during which the user's analyte level falls outside the bounds of the target analyte range (e.g., exceeds the range or drops below the range). Additionally, the analyte trend line 461 is configured as a solid line to represent the periods during which the user's analyte level is within the target analyte range. As previously mentioned, the target analyte range may be set by the user. For example, the target analyte may be set to approximately 80 mg / dL to approximately 170 mg / dL, alternatively approximately 70 mg / dL to approximately 180 mg / dL, or approximately 65 mg / dL to approximately 120 mg / dL. In some implementations, and as Figure 4D illustrated, the home page GUI 450 further includes a message 463 adjacent to the analyte graph card 451, where the message 463 indicates the time when the analyte graph card 451 was last updated.

[0117] According to another aspect of some embodiments, one or more meal icons 464 may be displayed on the analyte trend line 461. In some embodiments, one or more meal icons 464 may be displayed near the analyte trend line 461, adjacent to the analyte trend line and / or proximal to the analyte, or along the x-axis, at the top of the graphical window, or at the bottom of the graphical window. Additionally, in some embodiments, one or more meal icons 464 may be displayed with or without a lead line. Each meal icon 464 may be a photograph or image associated with a particular meal. In some aspects of the embodiments, the meal icon 464 is disposed on the analyte trend line 461 to allow the user to visually associate the post-meal analyte trace with the associated meal. In some embodiments, the meal icon 464 is disposed on the analyte trend line 461 based on the time associated with the meal. For example, if the meal event 469 indicates that blueberry oatmeal was consumed at 8:04 am, the meal icon 464 corresponding to the blueberry oatmeal meal event 469 will be located at approximately 8:04 am on the x-axis displayed on the analyte graph 460.

[0118] Still referring to Figure 4D , and similar to the home page GUI 400, the home page GUI 450 may include a logbook section 4508 that has a list 452 of one or more meal events 469 that occurred during a predetermined time period (e.g., one day). Each meal event 469 provides details of a particular meal consumed during the predetermined time period. In some embodiments, and as previously described with respect to the home page GUI 400, each meal event 469 may include a text description 473 of the meal (e.g., "blueberry oatmeal"), a portion indicator 474 (e.g., "typical") that describes the relative portion of the meal (e.g., typical, larger, or smaller compared to the user's daily meal allowance), and / or a timestamp 475 associated with the time of consumption of the meal (e.g., "8:04 am"). Although not illustrated, in some embodiments, the meal event 469 may include one or more meal tags 476 associated with the meal. Additionally or alternatively, the meal event 469 may include a photo / picture 477 associated with the meal. In some embodiments, when the user does not associate a photo or picture 477 with the meal, a placeholder picture 477 will be displayed instead. In some example embodiments, the list 452 may be sorted such that the meal event 469 corresponding to the most recently consumed meal is presented first or at the top of the list 452, and subsequent meal events 469 are displayed in chronological order.

[0119] As Figure 4DDepicted as such, and similar to the embodiments previously described herein, each dietary event 469 may additionally or alternatively include a rating or score 480 for a single specific meal based on its corresponding analyte response. In some embodiments, the analyte response may be based on the change in analyte levels over a predetermined period of time after consuming a specific meal. In some embodiments, a score 480 is given to a meal based on the change in analyte levels from the time of consumption of the specific meal to the peak glucose within three hours of eating. Additionally, the score 480 may be displayed as a numerical value. In some embodiments, the score 480 may be a number between one and five, where a higher assigned numerical value corresponds to a lower analyte response and a lower assigned numerical value corresponds to a higher analyte response. As depicted in the home page GUI 450, the score 480 may be displayed in a graphical element such as a star icon 481. In some embodiments, each star icon 481 may be filled with a colored portion, such as yellow. In many embodiments, the star icon 481 is unfilled and includes a dashed outline to indicate a missing meal score. In some embodiments, a score information icon 492 is displayed adjacent and proximal to the list 452 on the home page GUI 450. When selected by the user, the score information icon 492 outputs a meal rating information modality that includes information about different score options and how the meal score is determined.

[0120] Similar to the home page GUI 400, the home page GUI 450 may also include a text description 493 indicating the current day of the week, where the text description 493 includes a date adjacent to a switch 494 configured to be toggled. In some embodiments, the home page GUI 450 may be related to the past day, where the text description includes a date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the home page GUI 450 is related to the past day, the home page GUI 450 may also include a selectable "Go to Today" link that, when selected, outputs the home page GUI 450 corresponding to the current day.

[0121] In some embodiments, when the user toggles the switch 494 downward, the home page GUI 450 is configured to display a plurality of selectable rings 425, each ring being a TIR indicator corresponding to a different day of the past week. Each of the rings 425 for different dates may include a graphical or visual indication (progress indicator) of the amount of TIR and an indication of the target / goal percentage or number of TIR hours. In some embodiments, when the user selects a specific ring from the plurality of rings 425, a report GUI 600 (not shown) for the relevant day will be displayed. Those skilled in the art will recognize that other types of indicators (e.g., text, numbers (as percentages or fractions), graphics) may also be utilized, and these indicators are fully within the scope of the present disclosure.

[0122] In addition, in some embodiments, the home page GUI 450 further includes a selectable settings icon 498 that, when selected, outputs a settings GUI related to the TIR application.

[0123] Go to Figure 4E-1 , which shows a block diagram of an additional exemplary embodiment of the home page GUI 430 for the TIR application. In some embodiments, the home page GUI 430 may include: (1) a TIR card 431; (2) an analyte graphics card 4311 that includes an analyte graphic 4310 having an analyte trend line 4315; (3) a logbook section 4308 that includes a list 432 of dietary events 4309; (4) a selectable home page icon 433 that, when selected by a user, outputs the home page GUI 430; (5) a selectable dietary icon 434 that, when selected by the user, outputs a dietary report GUI 600 (FIG. 6), the dietary report GUI including information about one or more dietary events that occurred during a previous time period (e.g., the past week); and (6) a "+" icon 435 that, when selected by the user, outputs a dietary record GUI 500 configured to receive dietary information input by the user (see, e.g., Figures 5A through 5G ). In this regard, the TIR card 431 and the analyte graphics card 4311 are shown on a single interface. In some embodiments, although not illustrated, the home page GUI 430 may include a selectable insights icon instead of the dietary icon 434. Specifically, although not illustrated, when the user selects the insights icon, an insights GUI 14000 (e.g., Figures 14A-1 through 14A-4 ) is output, which will be described in further detail below.

[0124] According to one aspect of an embodiment, the TIR card 431 of the home page GUI 430 is similar to the TIR card 401 of the home page GUI 400 depicted in Figure 4B , except that the visual display of the TIR card 431 is different from the visual display of the TIR card 401. Specifically, for the TIR card 431 ( Figure 4E-1 ), the daily TIR target 437 is shown outside the TIR ring 436, rather than in its inner region. For example, in some embodiments, the daily TIR target 437 is adjacent to the TIR ring 436. According to one aspect of an embodiment, the TIR ring 436 includes a progress indicator 438 and a TIR value 4305. Similar to the TIR card 401 depicted in Figure 4B , the TIR card 431 of the home page GUI 430 includes a selectable information icon 439 that, when selected by the user, outputs a TIR information screen 440 related to the TIR card 431. As depicted in Figure 4F , the TIR information screen 440 is similar toFigure 4C the TIR information screen 410 in Figure 4C . Specifically, the TIR information screen 440 provides details on how the daily TIR loop 436 visually displays the progress indicator 438 and the daily TIR target 437. In some embodiments, as Figure 4F shown in Figure 4F , the TIR information screen 440 also informs the user that the TIR target setting is configurable.

[0125] According to another aspect of the embodiment, the analyte graphic card 4311 of the home page GUI 430 is similar to Figure 4D the analyte graphic card 451 of the home page GUI 450 depicted in Figure 4D , except that it includes a target analyte range 4312 (e.g., "target glucose range: 70 mg / dL to 180 mg / dL"). Additionally, as Figure 4E-1 shown in Figure 4E-1 , the home page GUI 430 includes one or more selectable icons 4313 (e.g., radio buttons, check boxes, sliders, switches, etc.), which allow the user to select a predefined amount of time within which the user's analyte data will be shown in the analyte graphic card 4311. For example, the selectable icon 4313 can be used to select a predefined amount of time of at least about four hours and / or no greater than about 24 hours, such as four hours, 12 hours, or 24 hours. Those skilled in the art will understand that other predefined amounts of time can be utilized and are fully within the scope of the present disclosure. In some embodiments, and as Figure 4E-1 shown in Figure 4E-1 , the selectable icon 4313 can be directly adjacent to and distal to the analyte graphic 4310 on the analyte graphic card 4311.

[0126] In some embodiments, although Figure 4E-1 not illustrated in Figure 4E-1 , one or more meal icons can be directly adjacent to and below the analyte graphic 4310, or below the x-axis. For example, the meal icon can be displayed at the bottom of the graphic window 4314. According to some aspects of the embodiment, the meal icon is provided on the analyte graphic card 4311 to allow the user to visually associate the post-meal analyte trajectory with the associated meal. In some embodiments, the meal icon is provided below the analyte graphic 4310 and the x-axis based on the time associated with the meal. For example, if the meal event 4309 indicates that the meal was consumed at 9:00 am, the meal icon corresponding to the meal event 4309 will be shown directly adjacent to and below 9:00 am on the x-axis on the analyte graphic 4310.

[0127] In some embodiments, and as Figure 4E-2As depicted, a notification can appear on the analyte graph card 4311, where the notification 4316 indicates that a user inputting a gesture (e.g., tapping or tap and hold) on the trend line 4315 can provide a glucose reading associated with the selected region of the trend line 4315. In some embodiments, the notification 4316 can also inform the user that a swipe-to-scroll gesture can be utilized on the trend line 4315 to provide glucose readings for various selected regions of the trend line 4315. Additionally, Figure 4E-3 The home page GUI 430 is depicted, where the analyte graph card 4311 includes a visual indicator 4317 that includes n analyte readings (e.g., glucose readings) corresponding to the selected region of the trend line 4315. In some embodiments, the visual indicator can include an analyte level value and a timestamp (e.g., "117 mg / dL" and "10:00 am") corresponding to the selected region of the trend line 4315.

[0128] In some embodiments, and as Figure 4E-3 best shown in, the analyte graph card 4311 can include an analyte graph information icon 4318 that outputs an analyte graph information modality 445 ( Figure 4G ) when selected by the user, and the analyte graph information modality provides the user with information about a predefined time amount for which the selected user's analyte data will be shown in the analyte graph card 4311. In some embodiments, the analyte graph information modality 445 also informs the user that tapping or holding an area of the analyte graph 4310 will allow the user to visualize the glucose reading associated with the selected region. In some embodiments, the analyte graph information modality 445 also includes a disclaimer that indicates to the user that they should consult a healthcare professional before changing their diet or exercise program.

[0129] In some example embodiments, and as Figure 4E-4 depicted, the bulletin card 441 can be output to the home page GUI430. For example, the bulletin card 441 can be shown directly adjacent to and above the TIR card 431 on the home page GUI 430. In some embodiments, the TIR card 431, the analyte graph card 4311, and the logbook section 4308 are shifted downward on the home page GUI 430 to allow the bulletin card 441 to be set on the home page GUI 430. In some embodiments, the bulletin card 441 can inform the user that it is time to scan the sensor. In some embodiments, the bulletin card 441 can also inform the user that the analyte monitoring application can be utilized to scan the sensor.

[0130] In some example embodiments, and as Figure 4E-5As depicted, the bulletin card 441 can be output to the home page GUI 430 to replace the TIR card. For example, the bulletin card 441 can be displayed directly adjacent to and above the analyte graphic card 4311. In some example embodiments, the bulletin card 441 can prompt the user to accept a challenge related to the new TIR target. For example, the bulletin card 441 can inform the user that the user has achieved the TIR target a specific number of times within a predefined time period (e.g., five days out of the past seven days), and prompt the user to increase the target TIR target by a specific number of hours (e.g., one hour). In some embodiments, the bulletin card 441 can include an "opt-out" button 442 that the user can select to decline the challenge and an accept button 443 that the user can select to accept and initiate the challenge. According to one aspect of the embodiment, the TIR application can be configured to output the bulletin card 441 including the challenge prompt to the user after the user has achieved the TIR target a specific number of times within a predefined time period.

[0131] The bulletin card 441 can be utilized with any of the embodiments described herein. Additionally, in some embodiments, the bulletin card 441 can include one or more of the following: (1) information about the dietary record (e.g., "Welcome, [user name], tap the '+' button below to add your first meal" or "Good job, [user name]! You added your first meal! Use the Libre 2 app to scan your sensor within 3 hours and come back here to check how your body responds to the meal"); (2) information related to scanning (e.g., "Ready? Use the Libre 2 app to scan your sensor and start tracking towards your TIR target. The goal is to turn off your ringtone before midnight every day" or "Use the Libre 2 app to scan your sensor. When you're done, come back here to see how your body responds to the meal"); (3) information related to the updated settings (e.g., "Your in-range time target has been set. You'll see it here tomorrow" or "Your new target is [hours], and you'll see it here tomorrow. Keep it up!"); an encouraging message to the user (e.g., "Your new target is [hours], and you'll see it here tomorrow. Keep it up!" or "Good job, [user name]! You've achieved your target 5 days out of the past 7 days. Challenge yourself and increase your target by one hour! Accept the challenge"); (4) prompting the user to accept a new challenge (e.g., "Good job, [user name]! You've achieved your target 5 days out of the past 7 days. Challenge yourself and increase your target by one hour! Accept the challenge"); and (5) notifying the user when the score is available (e.g., "Score! Your first meal score is available. Tap the meal card below to view the details.").

[0132] Additionally, and as Figure 4E-1Best depicted in, and according to another aspect of the embodiment, the analyte graphics card 4311 may include a selectable arrow 4319 that, when selected by the user, provides a different view of the analyte graphic 4310 on the analyte graphics card 4311. For example, if the analyte graphics card 4311 is configured to display analyte data within a predefined amount of time (e.g., a 24-hour period), the analyte graphic 4310 may be divided into a first view and a second view. In some embodiments, in the first view of the analyte graphic 4310, analyte data within a first portion of the predefined amount of time is shown (e.g., analyte data within the period between 12:00 AM and 6:00 PM or between 12:00 AM and 9:00 PM is shown). Additionally, although not illustrated, in the second view of the analyte graphic 4310, analyte data within a second portion of the predefined amount of time is shown (e.g., analyte data within the period between 6:00 PM and 12:00 AM or between 9:00 PM and 12:00 AM is shown).

[0133] In some example embodiments, and as, for example Figures 4E-1 through 4E-4 depicted in, the TIR card 431 may be arranged to be directly adjacent to and proximal to the analyte graphics card 4310 on the home page GUI 430. Additionally, the logbook section 4308 may be arranged to be directly adjacent to and distal to the analyte graphics card 4311 on the home page GUI 430.

[0134] Additionally, Figure 4E-6 illustrates the home page GUI 430 on the first day or within 24 hours that the user is utilizing the TIR application. As Figure 4E-6 depicted in, the home page GUI 430 includes an analyte graphics card 4311 without an analyte trend line. In some embodiments, and before the user enters a meal into the TIR application, the home page GUI 430 includes a logbook section 4308 without a list of entered meal events. In some embodiments, and as Figure 4E-6 depicted in, the logbook section 4308 includes a note 446 informing the user that no meals have been added. According to another aspect of the embodiment, and before setting a daily TIR goal in the TIR application, the home page GUI 430 may include a TIR card 431 without a daily TIR goal or TIR value inside the TIR ring 436. In some embodiments, and as Figure 4E-6As shown, and before setting the daily TIR goal in the TIR application, the TIR card 431 may include a message 447 indicating to the user that the TIR application is collecting user data. Additionally, in some embodiments, and before setting the daily TIR goal in the TIR application, the TIR card 431 may also include a selectable information icon 448 that outputs an information modal 465 ( Figure 4H ) when selected by the user. As Figure 4H shown, the information modal 465 may include a message 466 that indicates to the user that the TIR application is in the process of the first 24 hours of using the TIR application to set a personalized TIR goal for the user. Additionally, the information modal 465 may also include a message 466 that has a reminder indicating that the user can scan the sensor periodically while the user waits. The information modal 465 may be configured to partially obscure or overlay the underlying home page GUI 430. In some embodiments, the information modal 465 may also include a selectable "ok" button 467 that the user can press.

[0135] Figure 4E-7 Depicts the home page GUI 430 after a personalized daily TIR goal 437 has been set. Specifically, Figure 4E-7 depicts the home page GUI 430 that has a TIR card 431 including the user's daily TIR goal 437. In some embodiments, the daily TIR goal 437 may be set before the TIR application displays the analyte trend line or the user enters any dietary events (as Figure 4E-7 shown). According to one aspect of the embodiment, the daily TIR goal 437 and the TIR value 4305 inside the TIR ring 436 may be measured and displayed on the home page GUI 430 as a numerical value indicating the number of hours and the unit of measurement. In some embodiments, if the daily TIR goal 437 is set but the number of TIR hours within a specific time period has not been detected, a placeholder image or photo 449 may be displayed in the TIR ring 436, as Figure 4E-7 shown. In some embodiments, once the daily TIR goal 437 has been set, a modal 470 ( Figure 4I ) may be output that informs the user that a new TIR goal has been set. In some embodiments, the modal 470 may also inform the user that the TIR goal can be changed using the settings of the TIR application.

[0136] In some embodiments, and in Figure 4E-7Best depicted in, the home page GUI 430 may also include a text description 4333 indicating the current day of the week, wherein the text description 4333 includes a date adjacent to a switch 4334 configured to be toggled. In some embodiments, the home page GUI 430 may be related to the past day, wherein the text description 4333 includes a date associated with the past day (e.g., "Friday, February 11th"). In some embodiments, although not illustrated, when the home page GUI 430 is related to the past day, the home page GUI 430 may also include a selectable "Go to Today" link that outputs the home page GUI 430 corresponding to the current day when selected.

[0137] Go to Figure 4J-1 and Figure 4J-3 , depicts an additional embodiment of the home page GUI 485. The home page GUI 485 is similar to the home page GUI 430 (see, for example Figure 4E-1 ), except that the logbook section 4808 of the home page GUI 485 includes one or more time-of-day ("TOD") cards 4801, as Figure 4J-1 and Figure 4J-3 shown. Specifically, the home page GUI 485 includes a TIR card 4819, an analyte graphic card 4811, a logbook section 4808, a selectable home icon 4821, and a selectable "+" icon 4823. The TIR card includes information related to the amount of time during which data indicating a glucose level is within a predetermined analyte range (e.g., a predetermined glucose range). In some embodiments, and as Figures 4J-1 through 4J-3 shown, the home page GUI 485 also includes a selectable insights icon 4804 instead of a meal icon. Specifically, when the user selects the insights icon 4804, an insights GUI 14000 is output (e.g., Figures 14A-1 through 14A-4 ), which will be described in further detail below. Those skilled in the art will understand that a meal icon may be used in place of the insights icon 4804 with the home page GUI 485.

[0138] Referring to Figures 4J-1 through 4J-3 , each TOD card 4801 in the logbook section 4808 of the home page GUI 485 may represent a different increment or time period of a particular day. In some embodiments, and as Figure 4J-1 best shown, the logbook section 4808 may include four different TOD cards 4801, wherein each TOD card 4801 represents a different six-hour time period of a particular day. For example, and as Figure 4J-1Best depicted in, the logbook section 4808 may include, but is not limited to: (1) an "overnight" TOD card 4801a (e.g., a TOD card 4801 corresponding to the time period from 12:00 a.m. to 6:00 a.m. of a particular day); (2) a "morning" time card 4801b of the day (e.g., a TOD card 4801 corresponding to the time period from 6:00 a.m. to 12:00 p.m. of a particular day); (3) an "afternoon" TOD card 4801c (e.g., a TOD card 4801 corresponding to the time period from 12:00 p.m. to 6:00 a.m. of a particular day); and (4) an "evening" TOD card 4801d (e.g., a TOD card 4801 corresponding to the time period from 6:00 p.m. to 12:00 a.m. of a particular day). Those skilled in the art will understand that various TOD cards 4801 and time periods associated with each TOD card 4801 may be utilized without departing from the scope of the present disclosure.

[0139] In some embodiments, and still referring to Figures 4J-1 through 4J-3, each TOD card 4801 may include, but is not limited to: (1) a TOD indicator 4802 (e.g., "overnight", "AM", "PM", or "evening"), configured to indicate the time period represented by the TOD card 4801; (2) a time period indicator 4803 (e.g., "12 AM to 6 AM" for an overnight TOD card 4801, "6 AM to 12 PM" for an AM TOD card 4801, "12 PM to 6 PM" for a PM TOD card 4801, and "6 PM to 12 AM" for an evening TOD card 4801), configured to indicate the time period represented by the corresponding TOD card 4801; (3) a TOD icon 4804, configured to represent the time period associated with the TOD card 4801 (e.g., a TOD icon 4804 of a moon with the letter "Z" for representing the overnight time period for an overnight TOD card 4801, a half sun or sunrise TOD icon 4804 for representing the AM time period for an AM TOD card 4801, a whole sun TOD icon 4804 for representing the PM time period for a PM TOD card 4801, and a moon TOD icon 4804 for representing the evening time period for an evening TOD card 4801); and (4) a graphical representation 4805, indicating the average analyte score (e.g., average glucose score) associated with the time period represented by each corresponding TOD card 4801 (e.g., the average glucose score corresponding to the time period between 12 AM and 6 AM is represented by the graphical representation of the overnight TOD card 4801). Those skilled in the art will recognize that other time ranges or time periods may be utilized to indicate the various different time periods of the time period indicator 4803. According to some embodiments, the time periods represented by the time period indicator 4803 may be user - predefined and / or configurable. Additionally, according to one aspect of the embodiments, the average analyte score associated with the TOD card 4801 related to the current time of day is configured to be continuously updated. For example, if the current time of day is 9 AM, the AM TOD card 4801 (e.g., the TOD card 4801 identifying the time period between 6 AM and 12 PM) is configured to continuously update the average analyte score of the AM TOD card 4801.

[0140] In some embodiments, as Figure 4J-1As best shown in, the analyte graphic card 4811 of the home page GUI 485 may include analyte graphic TOD icons 4814, which correspond to the TOD icons 4804 displayed on each TOD card 4801 (e.g., an analyte graphic TOD icon 4814a of a moon with the letter "Z" for representing the overnight period for the overnight TOD card 4801, an analyte graphic TOD icon 4814b of a half sun or sunrise for representing the morning period for the morning TOD card 4801, an analyte graphic TOD icon 4814c of a whole sun for representing the afternoon period for the afternoon TOD card 4801, and an analyte graphic TOD icon 4814d of a moon for representing the evening period for the evening TOD card 4801). Specifically, and as Figure 4J-1 As best shown in, each of the analyte graphic TOD icons 4814a, 4814b, 4814c, and 4814d is displayed near the analyte trend line 4815, displayed proximate to and / or near the analyte trend line, or along the x-axis or at the bottom of the graphic window 484 of the analyte graphic card 4811. More specifically, each analyte graphic TOD icon 4814 is arranged along the x-axis to allow the user to visually associate the time period associated with the analyte graphic TOD icon 4814 on the analyte graphic card 4811.

[0141] In some example embodiments, and as Figures 4J-1 through 4J-3 As best shown in, the graphical representation 4805 includes a section portion 4806, where each section is configured to be filled with color (or no color at all) to correspond to the average analyte score. In an example embodiment, and as Figure 4J-1As best shown in , graphical representation 4805 may include a segment bar having three segment portions 4806, where: (1) a first segment 4806a may be red or orange and indicate an analyte fraction corresponding to a high glucose impact (e.g., an average glucose range exceeding 250 mg / dL); (2) the first segment 4806a and a second segment 4806b may be yellow and indicate an analyte fraction corresponding to a medium glucose impact (e.g., an average glucose range between 181 mg / dL and 250 mg / dL); or (3) the first segment 4806a, the second segment 4806b, and a third segment 4806c may be green and indicate an analyte fraction corresponding to a low glucose impact (e.g., an average glucose range between 70 mg / dL and 180 mg / dL). In some embodiments, although not illustrated, if the average glucose fraction corresponds to a low glucose impact (e.g., an average glucose range below 70 mg / dL), graphical representation 4805 is replaced with a "low" icon rather than segment portion 4806. Those skilled in the art will understand that various other graphical representations, colors, and color configurations may be utilized with the graphical representation without departing from the scope of the present disclosure.

[0142] In addition, and with specific reference to Figure 4J-2 , in some embodiments, and in response to a third predetermined input from the user (such as when the user taps on graphical representation 4805 corresponding to a particular TOD card 4801 or by some other predetermined gesture), a visual indicator 4807 may be displayed on the home page GUI 485. Specifically, visual indicator 4807 is configured to display the average analyte level value associated with the selected graphical representation (e.g., average glucose "117 mg / dL"). In addition, in some example embodiments, an information icon 4882 is displayed on the home page GUI 485, where information icon 4882 is configured to output an analyte fraction information modality (which includes information related to the average analyte fraction, including but not limited to how the average analyte fraction is determined) when selected by the user.

[0143] In some embodiments, the analyte score information modality may include a reference chart that provides information about an average glucose score, an average glucose range associated with the average glucose score, and an impact level associated with the average glucose score. In some embodiments, the analyte score information modality may further include details about a user's target glucose range (e.g., a target glucose range of 70 mg / dL to 180 mg / dL) and inform the user that the target glucose range can be set or changed using an analyte monitoring application. Additionally, in some embodiments, the analyte score information modality may further include a disclaimer that indicates to the user that they should consult a healthcare professional before changing their diet or exercise program. In some embodiments, the analyte score information modality may further include one or more information cards, where each information card provides information about the TOD card 4801 (e.g., what time of day or why that time of day). In some embodiments, in response to a fourth predetermined input from the user (such as when the user taps or pulls down on a particular information card or by some other predetermined gesture), the selected information card may be configured to expand to provide additional details related to the TOD card 4801. However, in some embodiments, the default information cards are all in a collapsed configuration.

[0144] Returning again to Figure 4J-1 and Figure 4J-3 , each TOD card 4801 may transition between a collapsed view and an expanded view. Specifically, according to some embodiments, in the collapsed view (see, for example Figure 4J-1 , where each TOD card 4801 is configured in a collapsed view), the TOD card 4801 is configured to display a TOD indicator 4802, a time period indicator 4803, a TOD icon 4804 representing the time period associated with the TOD card 4801, and a graphical representation 4805 indicating the average glucose score associated with the time period represented by the respective TOD card 4801. Additionally, according to some embodiments, in the expanded view (see, for example Figure 4J-3, wherein, in the evening, the TOD card 4801 is configured to be in an expanded view), and the TOD card in the expanded view 4801 is configured to display a TOD indicator 4802, a time period indicator 4803, a TOD icon 4804 representing the time period associated with the TOD card 4801, a graphical representation 4805 indicating the average glucose score associated with the time period represented by the corresponding TOD card 4801, and a list 4822 of dietary information including one or more dietary events 4829 that occurred during the relevant time period associated with the TOD card 4801. Additionally, in some embodiments, in the expanded view of the corresponding TOD card 4801, the TOD card 4801 is configured to display a dietary record link 4809 that outputs a dietary record GUI 500 when selected by the user, as Figure 5A shown and further described below.

[0145] Specifically, in some embodiments, if the user inputs dietary information through the dietary record GUI 500, details related to the input dietary information will be displayed as a dietary event 4829 in the list 4822 of dietary information for the corresponding TOD card 4801 from which the dietary record link 4809 was selected. In some example embodiments, and as Figure 4J-3 best shown in, the dietary record link 4809 is directly adjacent to and distal to the list 4822 of dietary events 4829 displayed on a specific TOD card 4801 in the expanded view.

[0146] In some embodiments, and as Figure 4J-3 best shown in, each TOD card 4801 can be configured to include information about one or more dietary events 4829 that occurred during the time period represented by the corresponding TOD card 4801. According to one aspect of the embodiments, each dietary event 4829 can include a text description 4823 of the meal, a meal type indicator 4824 that describes whether the input dietary information describes food or a beverage, a timestamp 4825 associated with the consumption time of the meal, and / or a photo or picture 4826 of the meal. In some embodiments, when the user does not associate a photo or picture 4826 with the meal, a placeholder picture will be displayed instead. In some example embodiments, the list 4822 can be sorted such that for the corresponding TOD card 4801, the dietary event 4829 corresponding to the most recently consumed meal is presented first or at the top of the list 4822, and subsequent dietary events 4829 are displayed in chronological order.

[0147] In addition, in some example embodiments, each meal event 4829 is configured to output a meal review GUI 800 associated with the selected meal event 4829 in response to a fifth predetermined input of the user (such as when the user taps on a particular meal event 4829 or by some other predetermined gesture), as Figure 8 shown and as will be described in further detail below).

[0148] According to another aspect of the embodiment, and as Figure 4J-3 best shown, each TOD card 4801 may include an entry counter 4810 configured to display the number of meal events 4829 recorded for a particular time period associated with the respective TOD card 4801. For example, if the user has recorded two meal events 4829 under the evening TOD card 4801, the entry counter 4810 associated with the evening TOD card 4801 will indicate "two entries". Additionally, according to some embodiments, each TOD card 4801 may be configured to display the entry counter 4810 in both a collapsed view and an expanded view.

[0149] According to yet another aspect of the embodiment, each TOD card 4801 is configured to transition between a collapsed view and an expanded view in response to a sixth predetermined input of the user on the respective TOD card 4801 (such as when the user taps, pulls the TOD card 4801 down with a finger, pulls the TOD card 4801 up with a finger, or by some other predetermined gesture). For example, in an example embodiment, each TOD card 4801 may transition from displaying a collapsed view to an expanded view in response to a received user input (e.g., by a tap gesture, a pull-down gesture, or by selecting or pressing a corresponding area of the TOD card 4801). Additionally, in some embodiments, the TOD card 4801 may transition from displaying an expanded view to a collapsed view in response to a received user input (e.g., by a tap gesture, a pull-up gesture, or by selecting or pressing a corresponding area of the TOD card 4801).

[0150] In some embodiments, and with reference to Figures 4J-1 through 4J-3, the home page GUI 485 is configured to default to display the TOD card 4801 corresponding to the current time of the day in an expanded view. For example, if the current time of the day is 9:00 am, the morning TOD card 4801 will be configured to be displayed in an expanded view on the home page GUI 485. Additionally, if a new time of the day occurs, for example, if the day transitions from the morning time of the day to the afternoon time of the day, the TOD card 4801 corresponding to the new time of the day (e.g., the afternoon TOD card 4801) will be populated in the logbook section 4808 of the home page GUI 485. Specifically, the TOD card 4801 corresponding to the new time of the day will default to be output to the home page GUI 485 in an expanded view. In some embodiments, the TOD card 4801 corresponding to the current time of the day defaults to be displayed in an expanded view (e.g., the afternoon TOD card), while the TOD card 4801 corresponding to the TOD cards 4801 of the past for that particular day (e.g., the overnight TOD card 4801 and the morning TOD card 4801) defaults to be displayed in a collapsed view.

[0151] In some embodiments, the TOD card 4801 corresponding to the current time of the day defaults to be displayed in a collapsed view. In some embodiments, the logbook section 4808 is configured to default to display each TOD card 4801 in an expanded view.

[0152] Furthermore, in some embodiments, although not illustrated, the TOD card 4801 corresponding to the current time of the day is configured to be highlighted as active by including a colored portion. For example, if the current time of the day is 7:00 pm, the afternoon TOD card 4801 may include a colored portion to indicate that it is active. Specifically, the TOD icon 4804 and / or the TOD indicator 4802 of the TOD card 4801 corresponding to the current time of the day may include a colored portion (e.g., be highlighted or colored, e.g., colored blue, while all other TOD indicators 4802 and TOD icons 4804 corresponding to other TOD cards 4801 are not highlighted or colored).

[0153] According to another aspect of the embodiment, and as Figure 4J-1 best shown in, the logbook section 4808 is further configured to display the TOD card 4801 related to the elapsed time period or historical time period and the current time period of a particular day presented on the interface. For example, in some embodiments, and as Figure 4J-1As shown in [FIGURE], if the current time of day is 7:00 PM, the logbook section 4808 is configured to display the overnight TOD card 4801a, the AM TOD card 4801b, the PM TOD card 4801c, and the PM TOD card 4801d. In some embodiments, the time period indicator for the TOD card 4801 corresponding to the current time of day (e.g., the PM TOD card 4801 if the current time of day is 3:00 PM) is configured to display a progress stamp 4812 (e.g., "Now") to indicate that a particular time period is current or in progress. In some embodiments, the progress stamp 4812 is displayed as part of the TOD indicator 4802. For example, if the current time of day is 3:00 PM, the PM TOD card 4801 can display the time period indicator 4803 "12:00 PM to Now" to indicate that the current time of day is within the time period associated with the TOD card 4801 being active (e.g., 12:00 PM to 6:00 PM for the PM TOD card 4801).

[0154] In some embodiments, and as best shown in Figure 4J-1 [FIGURE], the home page GUI 485 may also include a text description 4833 indicating the current day of the week, wherein the text description 4833 includes the date adjacent to a switch 4834 configured to be toggled. In some embodiments, the home page GUI 485 may be associated with the past day, wherein the text description 4833 includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the home page GUI 485 is associated with the past day, the home page GUI 485 may also include a selectable "Go to Today" link that, when selected, outputs the home page GUI 485 corresponding to the current day.

[0155] Go to Figures 4K-1 through 4K-3 [FIGURE], a block diagram of an additional exemplary embodiment of the home page GUI 495 for a TIR application is shown. In some embodiments, the home page GUI 495 may include: (1) a daily scorecard 4951; (2) an analyte graph card 4911; (3) a logbook section 4958; (4) a selectable home icon 4953 that, when selected by a user, outputs the home page GUI 495; (5) a selectable insights icon 4954 that, when selected by a user, outputs the insights GUI 14000 (e.g., Figures 14A-1 through 14A-4 ), as will be described in further detail below; and (6) a "+" icon 4957 that, when selected by a user, outputs a dietary record GUI 500 configured to receive dietary information input by the user (see, e.g., Figures 5A through 5G ).

[0156] According to one aspect of the embodiment, the home page GUI 495 is similar to the home page GUI 485 (see, for example, Figures 4J-1 through 4J-3 ), except that it includes a daily scorecard 4951 instead of a TIR card. In some embodiments, the daily scorecard 4951 can highlight the user's "daily score" based on the user's recorded meals and / or the user's analyte (e.g., glucose) using graphical elements such as a daily score circle or ring 4903. As seen in, for example, Figure 4K-1 , the daily scorecard 4951 shows a daily score ring 4903 with a daily score value 4904 (points earned daily) inside or within the inner area of the daily score ring 4903. For example, the daily score value 4094 can include a numerical value and a unit of measurement indicating the daily score obtained by the user (e.g., "80 points"). In some embodiments, the current daily score of the user relative to a predetermined target daily score can be displayed in two ways: (1) the daily score value 4904 can be the numerical value and unit of measurement listed inside the daily score ring 4904 (e.g., "80 points"); and (2) the daily score value 4904 can be visually displayed as a progress indicator 4905 (e.g., a shaded portion) extending along the circumference of the daily score ring 4903 to X% of the total circumference of the daily score ring 4903, indicating that the user has obtained X% of the predetermined target daily score (e.g., where X% is the daily score value 4904 divided by the predetermined target daily score). In this way, the ratio of the circumference of the daily score ring 4903 including the progress indicator 4905 (e.g., the shaded portion) to the total circumference of the daily score ring 4903 is proportional to the ratio of the daily score value 4904 obtained by the user within the predetermined daily score range in a day. In some embodiments, the progress indicator 4905 can include a color with a gradient configured to transition between various shades. In this way, the degree to which the color gradient transitions between various shades indicates the user's progress towards their predetermined target daily score goal.

[0157] Those skilled in the art will further recognize that other types of progress indicators 4905 (e.g., text, numbers, or graphics) can also be utilized, and these indicators are fully within the scope of the present disclosure. Additionally, although the graphical elements shown are circles or rings with shaded portions including gradients, those skilled in the art will understand that other geometric shapes, colors, and numbers of portions or gradients can be utilized, and these portions or gradients are fully within the scope of the present disclosure.

[0158] In some embodiments, and as best depicted in Figure 4K-1 , the daily scorecard 4951 can also include a selectable information icon 4907 that, when selected by the user, outputs a daily score information screen 4950 related to the daily scorecard 4951 (Figure 4L )。For example, and as Figure 4L depicted in, the daily score information screen 4950 provides details on how the daily score ring 4903 visually displays the progress indicator 4905 and the daily score value 4904. In some embodiments, the daily score information screen 4950 also informs the user that the daily score is calculated daily and reset at a predetermined hour (e.g., midnight).

[0159] In some embodiments, as Figure 4K-2 shown in, the daily score card 4951 may also include a message 4906 that indicates to the user the user's daily score at the end of a particular day (e.g., "You reached 87 points!"). Additionally, and as Figure 4K-2 best shown in, in some embodiments, the logbook section 4958 may include a list 4952 of dietary events 4959 instead of one or more TOD cards.

[0160] Furthermore, Figure 4K-3 illustrates the home page GUI 495 before a dietary entry after the user first utilizes the TIR application. As Figure 4K-3 depicted in, the home page GUI 495 includes an analyte graphic card 4911 without an analyte trend line. In some embodiments, and before the user enters a dietary entry into the TIR application, the home page GUI 495 includes a logbook section 4958 without a list of entered dietary events. According to another aspect of the embodiments, and as Figure 4K-3 best depicted in, an announcement card 4908 is displayed on the home page GUI 495 to replace the daily score card. Specifically, the announcement card 4908 may inform the user that the user can use a predetermined gesture (e.g., tap) on the "+" icon 4957 to enter a dietary entry into the TIR application.

[0161] In some embodiments, and in Figure 4K-3 best shown in, the home page GUI 495 may also include a text description 4933 indicating the current day of the week, wherein the text description 4933 includes a date adjacent to a switch 4934 configured to be toggled. In some embodiments, the home page GUI 495 may be related to the past day, wherein the text description 4933 includes a date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the home page GUI 495 is related to the past day, the home page GUI 495 may also include a selectable "Go to Today" link that outputs the home page GUI 495 corresponding to the current day when selected.

[0162] Go to Figure 4M-1 and Figure 4M-2, a block diagram showing an additional exemplary implementation of the home page GUI 499 for a TIR application. In some implementations, the home page GUI 499 may include: (1) an average meal rating card 4991; (2) an analyte graph card 4910; (3) a logbook section 4998, which includes a list 4992 of meal events 4999; (4) a selectable home page icon 4995, which outputs the home page GUI 499 when selected by the user; (5) a selectable insights icon 4994; and (6) a “+” icon 4997, which outputs a meal record GUI 500 configured to receive meal information input by the user when selected by the user (see, for example Figures 5A through 5G ).

[0163] In some implementations, and as best shown in Figure 4M-1 , the home page GUI 499 may also include a text description 4973 indicating the current day of the week, wherein the text description 4973 includes a date adjacent to a switch 4974 configured to be toggled. In some implementations, the home page GUI 499 may be related to the past day, wherein the text description 4973 includes a date associated with the past day (e.g., “Friday, February 11”). In some implementations, although not illustrated, when the home page GUI 499 is related to the past day, the home page GUI 499 may also include a selectable “Go to Today” link, which outputs the home page GUI 499 corresponding to the current day when selected.

[0164] As Figure 4M-1 and Figure 4M-2 illustrated, each meal event 4999 may additionally or alternatively include a rating or score 4922 for a single specific meal based on the analyte response associated therewith (e.g., glucose response). In some implementations, the analyte response may be based on the change in analyte level (e.g., glucose level) within a predetermined period of time after consuming a specific meal. In some implementations, a score 4922 is given to a meal based on the analyte level offset value from the time of consumption of the specific meal to the peak glucose within three hours of eating.

[0165] In addition, the score 4922 may be displayed as a numerical value. In some implementations, the score 4922 may be a number between one and five, wherein a higher assigned numerical value corresponds to a lower analyte response, and a lower assigned numerical value corresponds to a higher analyte response.

[0166] For example, (1) a change in analyte level from 0 mg / dL to 20 mg / dL within the two-hour post-meal period can correspond to a "5" score 4922; (2) a change in analyte level from 21 mg / dL to 40 mg / dL within the two-hour post-meal period can correspond to a "4" score 4922; (3) a change in analyte level from 41 mg / dL to 60 mg / dL within the two-hour post-meal period can correspond to a "3" score 4922; (4) a change in analyte level from 61 mg / dL to 90 mg / dL within the two-hour post-meal period can correspond to a "2" score 4922; and (5) a change in analyte level of 91 mg / dL or higher within the two-hour post-meal period can correspond to a "1" score 4922. As another example, (1) a change in analyte level from 0 mg / dL to 24 mg / dL within the three-hour post-meal period can correspond to a "5" score 4922; (2) a change in analyte level from 25 mg / dL to 49 mg / dL within the three-hour post-meal period can correspond to a "4" score 4922; (3) a change in analyte level from 50 mg / dL to 74 mg / dL within the three-hour post-meal period can correspond to a "3" score 4922; (4) a change in analyte level from 75 mg / dL to 99 mg / dL within the three-hour post-meal period can correspond to a "2" score 4922; and (5) a change in analyte level of 100 mg / dL or higher within the three-hour post-meal period can correspond to a "1" score 4922. Those skilled in the art will understand that other changes in analyte levels can be used with different scores and are fully within the scope of the present disclosure.

[0167] In addition, according to another aspect of the embodiment, the home page GUI 499 is similar to, for example Figure 4E-1 the home page GUI 430 depicted in, except that it displays the average meal rating card 4991 instead of the TIR card. Specifically, according to one aspect of the embodiment, and as Figures 4M-1 through 4M-3 shown in, the average meal rating card 4991 includes an average meal rating 4920 that can be displayed as a numerical value and a graphical indication 4921 corresponding to the average meal rating 4920. More specifically, the average meal rating 4920 is the average of the scores 4922 of all scored meal events 4999 within a predetermined period (e.g., within a specific day period), or can be based on the average of the scores 4922 of multiple scored meal events 4999 within a predetermined period (e.g., the scores 4922 of all scored meal events of a specific type of meal, such as the scores 4922 of all scored breakfasts). In some embodiments, and as Figures 4M-1 through 4M-3Best depicted in, the average dietary rating 4920 can be a number between one and five, where a higher assigned value corresponds to a lower average analyte response and a lower assigned value corresponds to a higher average analyte response. In some embodiments, the average dietary rating 4920 is shown as a numerical value including one or more decimal values (e.g., average dietary rating "5.0").

[0168] For example, if a dietary event 4999 is recorded for a particular day (where a dietary event 4999 is given a "5" score 4922), the average dietary rating card 4991 will show an average dietary rating of "5" or "5.0". Additionally, if two dietary events 4999 are recorded for a particular day (where one dietary event 4999 is given a "5" score 4922 and the second dietary event 4999 is given a "1" score), the average dietary rating 4920 will be "3" or "3.0", i.e., the average of the scores 4922 of the two dietary events 4999 (as Figure 4M-1 shown). In some embodiments, if the user has recorded two dietary events 4999 but only one has been scored, the average dietary rating 4920 will only consider the scored dietary event 4999, as Figure 4M-2 shown. In some embodiments, the average dietary rating 4920 is configured to update continuously and automatically to account for all dietary events 4999 being scored within a predetermined time period.

[0169] As Figures 4M-1 through 4M-3 best shown in, and according to another aspect of the embodiments, the average dietary rating card 4991 further includes a graphical indication 4921 of the average dietary rating 4920. Specifically, the graphical indication 4921 can include an average dietary rating indicator 4923 that visually depicts the average dietary rating provided within a predetermined time period (e.g., a particular day period). In some embodiments, the graphical indication 4921 is a plurality of asterisks including a colored portion, where the ratio of each asterisk including the colored portion to the total number of asterisks is proportional to the ratio of the average dietary rating 4920 to the maximum available dietary rating. Those skilled in the art will understand that other graphical indications 4921, indicators 4923, and symbols (e.g., emojis, trophy icons, bars, triangles, squares, circles, etc.) can be used instead of the asterisk icon without departing from the scope of the present disclosure.

[0170] In some embodiments, and as Figure 4M-3Best depicted in, when the average meal rating 4920 is not an integer (e.g., the average meal rating 4920 is "3.4"), the graphical indicator 4921 may include at least one asterisk with a semi-colored portion. For example, if the average meal rating 4920 is "3.4", the graphical indicator 4921 may show that three out of five asterisks have a fully colored portion and one out of five asterisks has a semi-colored portion, as Figure 4M-3 depicted in.

[0171] According to one aspect of an embodiment, the average meal rating 4920 is provided only after the user has received a first score for a meal event 4999 recorded within a predetermined period. In some embodiments, and as Figure 4M-4 depicted in, the announcement card 4924 will be shown directly adjacent and proximal to the analyte graphic card 4910, where an announcement "+" icon is used to add a first meal. In some embodiments, although not illustrated, the announcement card will be shown directly adjacent and proximal to the average meal rating card, where the announcement card includes a message indicating to the user that a first meal rating or score is available and that the user can tap on the specific meal event that was scored to view further details. Further, in some embodiments, and as Figure 4M-4 depicted in, a banner may be shown on the analyte graphic card 4910, where the banner 49001 indicates that the user can tap on the analyte trend line 49015 to view analyte readings (e.g., glucose readings) and horizontally slide to scroll through the analyte graph 49011.

[0172] In some embodiments, and with reference to Figure 4M-5 , if the user deletes all scored meals, if the user has not received an average meal rating within a predetermined period (e.g., this day), or if no meal events have been scored within the predetermined period, the average meal rating card 4991 does not display an average meal rating, and the graphical indicator 4921 corresponding to the average meal rating includes a plurality of asterisks, where none of the asterisks includes a colored portion and are unfilled. In some embodiments, if the user deletes all scored meals or if no meal events have been scored within the predetermined period, a prompt 4925 (see, for example Figure 4M-5 ) will appear on the average meal rating card 4991. Specifically, and as Figure 4M-5As shown, the prompt 4925 can inform the user that once the user records a meal and obtains the first meal rating within a predetermined time period (e.g., this day), the user will obtain the average meal rating 4920. In some embodiments, once the user records their first meal and / or cancels the prompt 4925 (e.g., by tapping the exit button), the prompt 4925 is removed from the average meal rating card 4991 and will no longer appear.

[0173] In addition, in some embodiments, and with reference to Figure 4M-6 , if the user does not receive the average meal rating within a predetermined time period (e.g., this day), the average meal rating card 4991 does not display the average meal rating, and the graphical indicator 4921 includes a plurality of asterisks, where none of the asterisks includes a colored portion and the plurality of asterisks are unfilled. Additionally, in some embodiments, if the user does not receive the average meal rating within a predetermined time period (e.g., this day), the message 4926 will appear on the average meal rating card 4991, indicating to the user that no meal rating is available during the predetermined time period (e.g., "No meal rating available today").

[0174] In some embodiments, and as Figures 4M-1 through 4M-4 and Figure 4M-6 depicted, the average meal rating card 4991 includes an information icon 4927 that outputs an average meal rating modal 4990 ( Figure 4N ) when selected. Specifically, and as Figure 4N shown, the average meal rating modal 4990 can inform the user that the average meal rating is based on the meal logs of all users with ratings within a predetermined time period (e.g., between midnight and 11:59 PM). Additionally, the average meal rating modal 4990 can also inform the user that as new meal ratings or scores become available throughout the predetermined time period (e.g., throughout this day), the user's average meal rating can change.

[0175] According to another aspect of some embodiments, and particularly with reference to Figures 4M-1 to 4M-3, one or more meal icons 49014 may be displayed on the analyte trend line 49015. In some embodiments, one or more meal icons 49014 may be displayed near the analyte trend line, close to the analyte trend line and / or displayed proximal to the analyte, or along the x-axis, at the top of the graph window 49904, or at the bottom of the graph window 49904. Additionally, in some embodiments, one or more meal icons 49014 may be displayed with or without leads. Each meal icon 49014 may be a photograph or image associated with a particular meal. In some aspects of the embodiments, the meal icon 49014 is located on the analyte trend line 49015 to allow the user to visually associate the post-meal analyte trace with the associated meal. In some embodiments, the meal icon 49014 is located on the analyte trend line 49015 based on the time associated with the meal. For example, if the meal event 4992 indicates that blueberry oatmeal was consumed at 8:04 am, the meal icon 49014 corresponding to the blueberry oatmeal meal event 4992 will be around 8:04 am on the x-axis displayed on the analyte graph 49011.

[0176] Those skilled in the art will understand that any GUI (or portion thereof) described herein is for illustrative purposes only, and any combination of independent elements or elements depicted and / or described for a particular embodiment or figure may be freely combined with any other elements or any other combination of elements depicted and / or described for any other embodiment.

[0177] Example embodiments of a dietary record GUI

[0178] Turning to Figures 5A to 5N , example embodiments of the meal record interface and features associated therewith will be described. First, referring to Figure 5A , when the user selects the "+" icon on any GUI embodiment that includes the "+" icon described herein, the meal record GUI 500 is displayed. In some embodiments, the TIR application may prompt the user to record a meal, for example, if a meal event is detected or a predetermined period of time has elapsed. The user of the TIR application may also voluntarily record a meal without any prompt. As Figure 5B seen, if the user wants to voluntarily add a meal, the user can, for example, tap the "+" icon on any GUI embodiment that includes the "+" icon described herein to select the option to add a meal, after which the meal record GUI 500 will be populated or displayed. As Figure 5A and Figure 5BAs shown, the dietary record GUI 500 may include a dietary entry field 501 that allows a user to enter the name or description of a food item as a dietary entry. When the user enters characters of a dietary or food name into the dietary entry field 501 ( Figure 5B ), the TIR application may automatically suggest entries based on the user's past dietary entries. For example, in some embodiments, the TIR application may retrieve information related to past dietary entries with the same (or similar) food name and display it, for example, as a list of past dietary events 503 in the result section 502. If the desired food name appears in the result section 502, the user can conveniently select the dietary entry without having to type the full name of the food or meal.

[0179] In addition, although Figure 5B the result section 502 is shown in list form, those skilled in the art will appreciate that other interfaces may be implemented, such as by manually entering text, by selecting a dietary name from a list (e.g., a selection list or a drop-down list), by selecting a dietary picture from a set of pictures, by selecting a recognizable marker (e.g., a label) of the meal, or any combination thereof. In some embodiments, a score information icon 522 is displayed with the result section, where the score information icon 522 outputs a dietary score information modality when selected, which includes information about different score options and how the dietary score is determined.

[0180] According to another aspect of the embodiment, and as Figure 5D shown, if the dietary information entered is not recognized as a past meal, the result section 502 will indicate that no past meal was found. Once new dietary information has been entered, the user may select the continue button 504, which may cause a modality 510 configured to request additional information to be displayed, as seen, for example, in Figure 5E . The user may edit the dietary entry as needed. For example, the user may click on a pencil icon 505 adjacent to the name of the meal or food that appears in the dietary entry description 506.

[0181] The modal 510 may include a portion indicator 511 option that indicates the relative portion size of the meal consumed, for example, selectable buttons that indicate different portion sizes of the meal, such as "smaller," "typical," and "larger." The user may also add a photo / picture 512 of the meal to be associated with the meal. For example, the modal 510 may include a camera icon 513 that, when selected or clicked, opens the camera of the device on which the time in range application is installed, and the user may take a picture of the food or alternatively select a picture from a photo library. The modal 510 may also include a meal tag entry 514, wherein the user may type one or more meal tags 515 to be associated with the meal consumed. The meal tag 515 may be a keyword that specifies or describes one or more of the ingredients and / or characteristics of the meal, or additional content consumed with the meal. For example, the meal tag 515 may relate to the specific content of the meal or a side dish consumed with the meal, and list the type of food, for example, carrots, lettuce, blueberries, cheese, bananas, French fries. Figure 5F As shown in the figure, for example, the "carrot" meal tag is selected. After entering the meal information, the user can click "save" 516 to record the information.

[0182] In some embodiments, the modal 510 also includes a time field 517 that includes a time and date associated with the meal entry. In some embodiments, the time field 517 can be automatically associated with the meal entry, or based on the user selecting the continue button 504 (e.g., Figure 5D ) is automatically filled in at the time. According to an aspect of some embodiments, and as Figure 5G As illustrated in FIG, the automatically populated time field 517 may still be edited by the user.

[0183] According to another aspect of the embodiment, and as Figure 5C As shown in , if the user selects a meal that has already been entered, the meal entry can be pre-populated with information from the past meal and assigned the current date and time. Figure 5C , a meal entry modal 520 (also referred to as a meal entry modal window) will appear, which includes a time field 527 with the current date and time and information associated with past meal events 503. The user can edit the meal entry as needed. The user can edit the meal name by clicking on the pencil icon 525 adjacent to the meal name. The user can edit the meal entry to add the meal name. The user can also select the camera icon 531 and edit the picture 532 associated with the meal entry. The user can also edit the meal tag 533 associated with the past meal event 503. The user can click "Add Meal" 535 to record the information.

[0184] Now refer to Figure 5H, a block diagram showing an example implementation depicting modality 530. Modality 530 is similar to modality 510 (Figure E), except that it does not display a photo / picture associated with the meal. In some implementations, as Figure 5H depicted in, when the user does not associate a photo or picture with the meal, a placeholder picture 534 will be displayed instead. Similar to modality 510, modality 530 may include a camera icon 536 that, when selected or clicked, opens the camera of the device on which the TIR application is installed, and the user can take a picture of the food or alternatively select a picture from the photo library.

[0185] Figures 5I to 5N are various block diagrams showing example implementations depicting a camera interface or its related features, any of which can be utilized with the implementations described herein. Referring to Figure 5I , a camera GUI 540 is depicted, which can be displayed after the user selects the camera icon 513 ( Figure 5E ) or 531 ( Figure 5H ) on the previous interface implementations described herein. In some implementations, the camera of the device cannot be utilized until the user grants the TIR application permission to access the camera. The camera GUI 540 is related to enabling camera access. In some implementations, the camera GUI 540 may include a modality that prompts the user to enable camera access.

[0186] In some implementations, the TIR application cannot utilize the photos stored on the device until the user has granted access. Figure 5J The figure depicts a block diagram showing an example implementation of a camera GUI 550 related to enabling photo access. In some implementations, the camera GUI 540 may include a modality that prompts the user to enable photo access. In one aspect of the implementation, the user can allow access to select photos. In another aspect of the implementation, the user can allow access to all photos. In yet another aspect of the implementation, the user can restrict access to any photos.

[0187] Figure 5K The figure illustrates a block diagram showing an example implementation of a camera GUI 560, where the camera GUI 560 includes an indicator specifying that camera access has been restricted. Figure 5L The figure illustrates a block diagram showing an example implementation of a camera GUI 570, where the camera GUI 570 includes an indicator specifying that the camera of the device is unavailable.

[0188] Figure 5M and Figure 5N respectively illustrate block diagrams showing example implementations of camera GUIs 580 and 590 related to photo capture and / or selection. In some implementations, and referring toFigure 5M , the camera GUI 580 may include a retake button that, when selected by the user, deletes the previously taken photo and allows the user to take another photo to associate with a specific meal. In some embodiments, the camera GUI 580 includes a "Use Photo" button that, when selected by the user, allows the user to use the captured photo and associate it with a specific meal. Additionally, Figure 5N illustrates an example embodiment of the camera GUI 590 on which a photo is displayed. In some embodiments, the camera GUI 590 includes a library button that, when selected by the user, allows the user to browse through the photos stored on the device. In some embodiments, the camera GUI 590 also includes a "Skip" button that, when selected by the user, allows the user to skip the photo displayed on the camera GUI 590.

[0189] Example embodiments of a report GUI and related methods

[0190] Example embodiments of methods for an output report GUI will be described. Specifically, Figure 6A illustrates the operations of a method 6000 for performing a process for a report GUI that displays data indicative of analyte levels for a particular day and non-medical statistical data associated therewith. First, those skilled in the art will recognize that the method steps described herein may include software instructions stored in the memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of the system 100 such that the instructions, when executed by one or more processors of the computing device, cause the one or more processors to perform any or all of the method steps described herein. Referring again to Figure 6A , at 6001, the method for the report GUI may include receiving, from the user, a seventh predetermined input (e.g., a tap or press gesture) on a toggle switch adjacent to a text description on the interface, where the text description indicates the current day of the week. In one aspect of the embodiment, when the user toggles the switch down, the displayed interface is configured to display a plurality of selectable rings, each ring being a TIR indicator corresponding to a different day of the past week. For example, in some embodiments, a plurality (seven) of selectable rings are displayed on the displayed interface.

[0191] At 6002, the method for the report GUI further includes the user selecting a particular ring from the plurality of rings displayed in response to the user toggling the switch, where each of the plurality of selectable rings is a TIR indicator corresponding to a different day of the past week.

[0192] At 6003, at least one processor determines, based on data stored in the database, a data set indicative of analyte levels and dietary information associated with the day corresponding to the selected ring.

[0193] At 6004, an interactive report GUI is provided to the display device, the interactive report GUI being configured to display a data set indicating an analyte level and dietary information based on the determination, wherein the report GUI displays: a TIR card, an analyte graphic card reflecting data indicative of the analyte level during a time period corresponding to a selected loop, and / or a dietary list reflecting dietary information during a time period corresponding to the selected loop. Those skilled in the art will recognize that method 4000( Figure 4A-1 ) whether in its entirety or any one or more individual steps can be combined with or implemented as part of the method 6000 of Figure 6A . In a similar manner, those skilled in the art will recognize that method 4100( Figure 4A-2 ) whether in its entirety or any one or more individual steps can be combined with or implemented as part of the method 6000 of Figure 6A .

[0194] As previously stated, those skilled in the art will recognize that the method steps described herein may include instructions (e.g., software, firmware, etc.) stored in a non-transitory memory of the sensor control device 102, the reader device 120, or any other computing device or system that is part of or communicates with the analyte monitoring system 100. Additionally, the method steps described herein may be performed by a single centralized device or by multiple devices.

[0195] Moving on to Figure 6B-1 , a block diagram depicting an example implementation of a report GUI 600 for a TIR application is shown. As previously described, the report GUI 600 may be displayed in response to a user selecting a specific loop from among the multiple loops 425 displayed on the home page GUI 400 or the home page GUI 450. Specifically, and as illustrated in FIG. 6B, the report GUI 600 corresponding to the relevant day associated with the selected loop 425 will be displayed. The report GUI 600 includes (1) a TIR card 601; (2) an analyte graphic card 602 that reflects data indicating the analyte level and dietary information corresponding to a specific day associated with the selected loop 425; (3) a dietary information list 603 that includes one or more dietary events 604; (4) a selectable "Daily Summary" icon 605 that outputs the report GUI 600 for the relevant day when selected by the user; (5) a selectable dietary icon 606 that outputs a dietary impact GUI 650 when selected by the user( Figure 6B-1(not shown in the figure), the dietary impact GUI includes information about one or more dietary events 604 that occurred during a previous time period (e.g., the past week); and / or (6) a "+" icon 607 that, when selected by the user, outputs a dietary record GUI 500 configured to receive dietary information input by the user. Figure 5A )

[0196] According to some aspects of the embodiments, a plurality of rings 425 are displayed proximal to and adjacent to the TIR card 601, each ring corresponding to a different day of the week. In some embodiments, only the particular ring 425 corresponding to the displayed report GUI 600 will be highlighted, bolded, or colored to indicate that the report GUI 600 is associated with that particular ring 425. According to another aspect of the embodiments, the user can transition between report GUIs 600 corresponding to a particular day by selecting the ring associated with that particular day from the plurality of rings 425. Additionally, in some embodiments, the report GUI 600 can include a "Go to Today" link 608 that, when selected, outputs a home page GUI 400 including data corresponding to the current day or a report GUI 600 corresponding to the current day.

[0197] The TIR card 601 shown on the report GUI 600 includes a TIR ring 612 with a TIR value 611 inside the TIR ring 612. In some embodiments, and as Figure 6B-1 illustrated, the TIR value 611 can include a numerical value and a unit of measurement indicating the number of hours (e.g., "15 hours") the user spent within a predetermined target / goal TIR range for the relevant day. Additionally, the number of hours spent within the TIR range can be visually displayed as a progress indicator 618 (e.g., a shaded portion) that extends along the circumference of the TIR ring 612 to X% of the total circumference of the TIR ring 612. In this way, the ratio of the circumference of the TIR ring 612 including the progress indicator 618 to the total circumference of the TIR ring 612 is proportional to the ratio of the amount of time the user spent within the target TIR range to the predetermined daily TIR goal 617 for the relevant day. In some embodiments, the TIR card also includes a message 635 related to the user's daily TIR goal 617. In some embodiments, the TIR card 601 also includes a daily TIR goal 617 indicating a predetermined TIR goal (e.g., "10 hours"). The daily TIR goal 617 can be displayed below the message 635 related to the user's daily TIR goal 617.

[0198] Still referring to Figure 6B-1, and similar to the previously described home page GUI 450, the analyte graph 602 in the report GUI 600 may include an analyte graph 630, which includes an analyte trend line 631 that reflects the user's analyte level over a predetermined period based on data indicating the analyte level. For example, and as Figure 6B-1 shown, the x-axis of the analyte graph 630 may include time units (e.g., three-hour increments, etc.) covering a twenty-four-hour period, while the y-axis may include units of measurement of the measured user analyte concentration (e.g., mg / dL). For example, and as Figure 6B-1 illustrated, the time shown on the x-axis may show the glucose concentration measured starting from 12:00 am of the current day.

[0199] The analyte graph 630 may include solid lines 632-1, 632-2 to indicate the user's analyte target range associated with the data indicating the analyte level. For example, the area between the solid lines 632-1, 632-2 indicates the target or desired analyte range (e.g., between 70 mg / dL and 180 mg / dL). In some embodiments, and as Figure 6B-1 illustrated, the analyte trend line 631 is configured as a dashed line or a broken (dashed) line to represent the time period during which the user's analyte level exceeds the analyte TIR target range. Additionally, the analyte trend line 631 is configured as a solid line to represent the time period during which the user's analyte level is within the analyte target range. As previously described, the TIR target range may be configured by the user.

[0200] According to another aspect of the embodiment, one or more meal icons 633 may be displayed on the analyte trend line 631. Each meal icon 633 may be a photo or image associated with a specific meal. In some aspects of the embodiment, the meal icons 633 are located on the analyte trend line 631 to indicate the post-meal analyte trajectory associated with the relevant meal. In some embodiments, the meal icons 633 are located on the analyte trend line 631 based on the time associated with the meal.

[0201] Still referring to Figure 6B-1, and similar to the Home GUI 400 and the Home GUI 450, the Report GUI 600 may include a list 603 of dietary information that includes one or more dietary events 604 that occurred during the relevant day described in the Report GUI 600. Each dietary event 604 provides details of a specific meal consumed during the relevant day. In some embodiments, and similar to the GUI embodiments described previously, each dietary event 604 may include a text description 640 of the meal, a portion indicator 641 that describes the relative portion of the meal, and / or a timestamp 642 associated with the time of consumption of the meal, and / or a score 643. In some embodiments, the score 643 corresponding to a specific dietary event 604 may be displayed as a numerical value inside a star icon 644. Although not illustrated, in some embodiments, the dietary event 604 may include one or more dietary tags 645 associated with the meal. Additionally or alternatively, the dietary event 604 may include a photo / picture 646 associated with the meal. In some embodiments, when the user has not associated a photo or picture 646 with the meal, a placeholder picture 646 will be displayed instead. In some example embodiments, the list 603 may be sorted such that the dietary events 604 corresponding to the most recently consumed meals are presented first or at the top of the list 603, and subsequent dietary events 604 are displayed in chronological order. In some embodiments, a score information icon 648 is displayed adjacent and proximal to the meal card on the Report GUI 600. When selected by the user, the score information icon 648 outputs a meal scoring information modal that includes information about different score options and how the meal score is determined.

[0202] Go to Figure 6B-2 , which depicts a block diagram of another example embodiment of a Report GUI 625 for a TIR application. Figure 6B-2 The Report GUI 625 depicted in Figure 6B-1 is similar to the Report GUI 600 in Figure 6B-1 , except that it includes a selectable home icon 626 instead of a selectable "Daily Summary" icon 605 ( Figure 6B-2 ). Additionally, the Report GUI 625 includes a plurality of rings 627, each corresponding to a different day of the week. Similar to the plurality of rings 425 depicted in the Report GUI 600, each of the plurality of rings 627 depicted in the Report GUI 625 represents the progress the user has made towards their daily TIR goal for a specific day. However, in the Report GUI 625, the number of TIR hours the user spent during a specific day can be visually displayed by the color gradient of a specific ring among the plurality of rings 627. For example, in some embodiments, and as depicted in Figure 6B-2 , the lightness or darkness of the color gradient may indicate the amount of time the user spent within the range of a specific day associated with a specific ring among the plurality of rings 627.

[0203] Example embodiments of a dietary impact GUI

[0204] Example embodiments of a dietary impact GUI for an analyte monitoring system will now be described. Figure 7 is a block diagram depicting an example embodiment of a dietary impact GUI 700 for use with an analyte monitoring system. As Figure 7 seen, the dietary impact GUI 700 can provide additional insights to the user regarding the impact of consuming specific foods. In some embodiments, the dietary impact GUI 700 can provide information related to the diet and data indicating analyte levels over a specific time period (e.g., the past seven days).

[0205] According to one aspect of an embodiment, the dietary impact GUI 700 includes: (1) a dietary highlight card 701; (2) a list 702 of dietary information, which includes dietary events 703 rated according to a score 704 assigned based on a corresponding analyte response recorded; (3) a selectable home icon 705; (4) a selectable diet icon 706; and (5) a selectable "+" icon 707. The dietary impact GUI 700 can be accessed from the diet icon 706 or a diet icon described in connection with other GUI embodiments herein. The dietary impact GUI 700 can list all dietary events 703 recorded over a predetermined time period (e.g., one week). In the diet list 702, the diets can be sorted from the highest score 704 to the lowest score 704, or alternatively, from the lowest score 704 to the highest score 704, where the score 704 is an assigned numerical value corresponding to an analyte response based on data indicating the user's analyte levels. In some embodiments, when one or more diets are given the same score 704, these diets can be sorted by the variance of the analyte levels in the diet list 702. For example, if two diets are given the score 704 "3", the diets can be sorted from the lowest PeakDelta or analyte level variance value to the highest PeakDelta or analyte level variance value. Additionally, in some embodiments, if one or more diets are given the same score 704 and the same analyte level variance, the diets can be sorted chronologically.

[0206] In some embodiments, the analyte response can be based on the change in analyte levels over a predetermined time period after consuming a specific diet. In some embodiments, a score 704 is given to the dietary event 703 based on the change in analyte levels from the time of consumption of a specific dietary event to the peak glucose within three hours of eating.

[0207] In some embodiments, the score 704 can be a number between one and five, where a higher assigned value corresponds to a lower analyte response and a lower assigned value corresponds to a higher analyte response. For example, and as previously detailed, (1) a change in analyte level from 0 mg / dL to 24 mg / dL during the three-hour post-meal period can correspond to a "5" score 704; (2) a change in analyte level from 25 mg / dL to 49 mg / dL during the three-hour post-meal period can correspond to a "4" score 704; (3) a change in analyte level from 50 mg / dL to 74 mg / dL during the three-hour post-meal period can correspond to a "3" score 704; (4) a change in analyte level from 75 mg / dL to 99 mg / dL during the three-hour post-meal period can correspond to a "2" score 704; and (5) a change in analyte level of 100 mg / dL or higher during the three-hour post-meal period can correspond to a "1" score 704. As depicted in the dietary impact GUI 700, the score 704 can be displayed in a graphical element such as the star icon 711. In some embodiments, the star icon 711 is filled with a colored portion, such as yellow. In many embodiments (not shown), the star icon 711 is unfilled and includes a dashed outline to indicate a missing dietary score 704. In some embodiments, and as Figure 7 depicted, the missing dietary score 704 is indicated by the "?" character. In some embodiments, the "?" character is displayed in the star icon 711 instead of a numerical value to indicate that a particular meal has not been scored. A missing dietary score 704 occurs when one or both of the following happen: (1) the user records the next meal too quickly, or (2) the within-range time application does not have sufficient analyte data to score the meal (e.g., the user is not scanned in a timely manner to ensure that glucose data has been transmitted to the within-range time application).

[0208] According to one aspect of an embodiment, the dietary highlight card 701 is configured to display information related to dietary events 703 that occurred during a predetermined time period (e.g., the past week). Specifically, the dietary highlight card 701 displays information related to the dietary event 703, including "Best Meal" and including the title "Best Meals in the Past 7 Days" 720. In some embodiments, the best meal is defined by the dietary event 703 with the highest score within the predetermined time period. In some embodiments, based on data indicating analyte levels, the best meal is defined by the dietary event 703 within the seven-day period that provided the most desirable analyte response last. In some embodiments, the dietary highlight card 701 includes a text description 721 of the best meal and a star icon 722 including a score 724 corresponding to the best meal allocation. The dietary highlight card 701 may also include a photo or picture 725 associated with the best meal, where the text description 721 and the star icon 722 are overlaid thereon, obscuring part of the photo or picture 725.

[0209] According to another aspect of an embodiment, each of the dietary events 703 listed on the dietary impact GUI 700 provides details about a specific meal consumed during a predetermined time period (e.g., a one-week period). In some embodiments, each dietary event 703 may include a text description 731 of the meal, a photo or picture 739 associated with the meal, a portion indicator 732 describing the relative portion of the meal, a timestamp 733 associated with the consumption time of the meal, and / or a score 734 associated with the meal. In some embodiments, the dietary event 703 may additionally or alternatively include one or more dietary labels 735 associated with the meal (e.g., "lettuce", "blueberries", "cheese", "bananas", "fries"). In some embodiments, an information message 736 is displayed proximal to the list 702, where the information message 736 informs the user that the higher the score 704, the higher the likelihood of being within the target TIR.

[0210] Still referring to Figure 7 the dietary impact GUI 700 may also include a score information icon 742. In some aspects of the embodiment, each of the dietary events 703 is selectable, and when selected by the user, a dietary review GUI 800 (not shown) that outputs details related to the selected dietary event 803 is provided, as will be further described below.

[0211] Example embodiments of a dietary review GUI

[0212] Example embodiments of the dietary review GUI and other related features for the analyte monitoring system will now be described. Figure 8is a block diagram depicting an example implementation of a dietary review GUI 800 for use with an analyte monitoring system. As Figure 8 seen, the dietary review GUI 800 can provide the user with additional insights into the effects of consuming a particular food. As Figure 8 seen, the user can select a dietary event from a list on the report GUI 600, the dietary impact GUI 700, the home page GUI 400, the home page GUI 450, the home page GUI 430, the home page GUI 485, the home page GUI 495, or the home page GUI 499. Once the user selects a dietary event, the dietary review GUI 800 can open to show details related to the selected dietary event 803, including a photo / picture 805, a description 801, a portion indicator 802, a dietary label 804, a timestamp 806 including the date and time associated with the meal, a score 807, and / or an analyte graphic card 810 that includes an analyte graphic 811 with an analyte trend line 812 that contains data indicating the analyte level at least during a relevant time period of consuming the meal. In some implementations, although Figure 8 not illustrated, the analyte graphic card 810 can include a selectable information icon that outputs an analyte graphic information modal 445 when selected, as Figure 4G shown.

[0213] Specifically, the dietary review GUI 800 includes a dietary description card 820 that includes a description 801 associated with the meal, a portion indicator 802, a dietary label 804, and a timestamp 806. Additionally, the score 807 is displayed in a star icon 830 and is set proximal to the description 801 of the meal. In some implementations, and as Figure 8 illustrated, the dietary description card 820 partially obscures a photo or picture 805 associated with the meal.

[0214] Still referring to Figure 8 , and similar to the analyte graphic card described in the previous GUI implementations, the analyte graphic card 810 in the dietary review GUI 800 can include an analyte graphic 811 with an analyte trend line 812 that reflects the user's analyte level over a predetermined time period based on data indicating the analyte level. For example, and as Figure 8As shown, the x-axis of the analyte graph 811 may include time units (e.g., one-hour increments, etc.) covering a predetermined time period, while the y-axis may include measurement units of the measured user analyte concentration (e.g., mg / dL). The analyte graph card 810 may include solid lines 813-1, 813-2 to indicate the user's analyte target range associated with the data indicating the analyte level. For example, the area between the solid lines 813-1, 813-2 indicates the target analyte range (e.g., between 70 mg / dL and 180 mg / dL). In some embodiments, and as Figure 8 illustrated, the analyte trend line 811 is configured as a dashed or zigzag (dashed) line for representing the time period during which the user's analyte level exceeds the analyte TIR target range. Additionally, the analyte trend line 811 is configured as a solid line for representing the time period during which the user's analyte level is within the analyte target range.

[0215] According to another aspect of the embodiment, the meal icon 840 corresponding to the meal event 803 may be displayed on the analyte trend line 811. The meal icon 840 may be a photo or image associated with the meal of the meal event. In some aspects of the embodiment, the meal icon 840 is set on the analyte trend line 811 to indicate the post-meal analyte trajectory associated with the relevant meal. In some embodiments, the meal icon 840 is set on the analyte trend line 811 based on the time associated with the meal.

[0216] In some embodiments, the meal review GUI 800 includes analyte level statistics 850 related to the meal event 803. For example, and as Figure 8As shown in the figure, the dietary review GUI 800 may include analyte level statistics related to peak analyte levels associated with a meal 850-1 (e.g., "173 mg / dL"), analyte levels 850-2 before consuming the meal (e.g., "140 mg / dL"), and analyte levels 850-3 after consuming the meal (e.g., "95 mg / dL"). In some embodiments, the analyte level statistics 850 are displayed adjacent and proximal to the analyte graphics card 810. In this way, the user can refer to the analyte graphics card 810 to obtain a visual illustration of the analyte level statistics 850 associated with the meal. Additionally, in some embodiments, a message 860 indicating a target glucose range (e.g., "Target Glucose Range: 70 mg / dL to 80 mg / dL") is displayed below the analyte graphics card 810. In some aspects of the embodiments, an informational message 870 is also displayed on the dietary review GUI 800, where the informational message 870 indicates that medications, activities, stress, and other facts can affect glucose levels. In yet another aspect of the embodiments, the dietary review GUI 800 may further include a meal summary message 880, where the meal summary message 880 describes the glucose spike associated with the meal event, statistics related to the user's TIR, and may include an incentive message (e.g., "Your glucose spike +33 mg / dL. You entered the range 3 hours after this meal. Great!").

[0217] Example embodiments of a onboarding GUI

[0218] The TIR application may also include an onboarding interface, and any onboarding interface can be utilized with the embodiments described herein. According to one aspect of the embodiments, when the user launches the TIR application, the onboarding GUI may be displayed. In some embodiments, the onboarding GUI may provide the user with a brief introduction to the TIR application. For example, in some embodiments, the onboarding GUI may inform the user that the TIR application can help the user understand how the diet affects the user's glucose levels and overall glucose management by providing the user with a daily score, an average analyte rating, or by tracking the user's time in range. In some embodiments, the onboarding GUI explains to the user (1) that the TIR application provides the user with a daily score based on the user's recorded diet and the user's glucose control, and (2) that the daily score is calculated daily and reset at a predetermined time each day (e.g., midnight). Additionally, in some example embodiments, the onboarding GUI may explain to the user that TIR is the amount of time spent within a target glucose range (e.g., between 70 mg / dL and 180 mg / dL or between 3.9 mmol / L and 10 mmol / L), and the longer the TIR, the more likely positive health outcomes are to be experienced. In some example embodiments, the onboarding GUI explains to the user: (1) that the TIR application helps the user track how different foods affect the user's glucose levels and provides the user with an average diet rating; (2) that the rating is the average of the ratings received by the user from the diet on a particular day that is recorded; and (3) that over time, the user will be able to see which foods best improve the user's average diet rating. In one aspect of the embodiments, an onboarding GUI may be provided to explain the requirements of the TIR application to the user. For example, the onboarding GUI may inform the user that the following are required: (1) the TIR application; (2) another analyte monitoring application; and (3) a sensor.

[0219] In addition, Figures 9A to 9O is a block diagram depicting an example embodiment on the onboarding GUI. As Figure 9A depicted therein, the onboarding GUI 920 may be utilized to log the user into an account. Next, Figure 9B depicts an onboarding GUI 925 that may provide the user with a trial disclaimer. In some embodiments, the onboarding GUI 925 includes a confirmation button 927 (e.g., an "I Accept" button) that the user may press to confirm agreement to the terms of the TIR application. Next, the onboarding GUI 930 is displayed to the user ( Figure 9C ). As Figure 9CAs depicted in, the onboarding GUI 930 includes a name entry field 931 in which the user can enter the name that will be associated with the user's account credentials.

[0220] Next, and as Figure 9D depicted in, the onboarding GUI 935 can provide the user with an introductory greeting that includes the name entered in the prior onboarding GUI 930. Additionally, the onboarding GUI 935 can provide a brief description of what will appear in subsequent onboarding GUIs and an estimated reading time for what will appear in the subsequent onboarding GUIs. After that, the onboarding GUIs 940 ( Figure 9E ), 945 ( Figure 9F ), and 950 ( Figure 9G ) can be used to provide the user with a further introduction to the TIR application.

[0221] In some embodiments, the onboarding GUI 940 ( Figure 9E ) can inform the user about studies that have shown that TIR can be a simple and powerful way to track how food affects glucose levels. Additionally, and with reference to Figure 9F , the onboarding GUI 945 can inform the user that the American Diabetes Association recommends 17 hours of TIR per day. In some embodiments, the onboarding GUI 945 can also inform the user that since glucose activity varies from person to person, TIR can also vary. In some embodiments, the onboarding GUI 945 can also inform the user that since glucose activity depends on the user, the TIR application will suggest a goal based on the user's glucose data from the first day. With reference to Figure 9G , a block diagram depicting the onboarding GUI 950 is shown, where the onboarding GUI 950 can inform the user that once the goal is set, the TIR ring will fill as the user spends more time in their TIR, even while the user is sleeping. The onboarding GUI 950 can also include a message encouraging the user to close the TIR ring before midnight each day in order to reach their goal.

[0222] In addition, in some embodiments, a onboarding GUI can be displayed that provides the user with a brief introduction on how to record meals in the TIR application. In addition, in some embodiments, a onboarding GUI can be displayed that includes a link that, when selected by the user, outputs a meal recording information modal that includes tips for adding a meal via the TIR application. In some embodiments, a onboarding GUI is displayed that provides the user with information related to a meal rating or score. For example, in some embodiments, although not illustrated, the onboarding GUI can explain to the user that the TIR application rates meals based on the glucose change after eating, and that a 5-star meal will cause the least amount of glucose elevation while a 1-star meal will cause the most.

[0223] In some embodiments, the onboarding GUI that provides information related to a meal rating can include a link that, when selected, outputs a meal scoring information modal that includes information on how to rate or score a meal in the TIR application, as described above. In some embodiments, the meal scoring information modal that includes information on how to rate a meal can also include emojis to indicate the impact on glucose. According to some aspects of the embodiments, the meal scoring information modal can include a link that, when selected by the user, outputs another meal scoring information modal that includes details on why the score is measured three hours after the meal is consumed. In some embodiments, the meal scoring information modal that includes details on why the score is measured three hours after the meal is consumed can also include a tip that provides the user with advice on how to avoid going out of range over a longer period of time. In some embodiments, the meal scoring information modal also includes details on why the user should allow time between meals. In addition, the meal scoring information modal also includes details on recording all the foods eaten in a 30-minute window under the same meal to minimize the number of meals with missing scores or ratings.

[0224] Additionally, in some embodiments, an information GUI can be provided that includes details on why a meal is missing a score or rating. For example, the information GUI can include one or more information cards, where each of the information cards describes a different scenario that may cause a meal to not be scored (e.g., the user records the next meal too quickly, or the TIR application does not have enough glucose data to score the meal).

[0225] In another aspect of the embodiments, a onboarding GUI 965 can be displayed that informs the user that they must allow notifications in order to receive reminders from the TIR application ( Figure 9H)。In addition, the onboarding GUI 965 can also inform the user that they must allow notifications in order to receive reminders that the user should scan the sensor to keep their user data updated. Additionally, in some embodiments, the onboarding GUI 965 informs the user that they must allow notifications in order to receive notifications when new "insights" are available.

[0226] In some embodiments, although Figure 9H not illustrated herein, the onboarding GUI 965 can include a "Back" button that, when selected by the user, causes the user to return to the previously displayed onboarding GUI that preceded the onboarding GUI 965. Further, in some embodiments, and as Figure 9H depicted in, the onboarding GUI 965 includes a "Continue" button 982 that, when selected by the user, outputs a notification modal window 977. Specifically, the notification modal window 977 can include a "Don't Allow" button 983 that, when selected by the user, does not allow the TIR application to send notifications to the user. The notification modal window 977 can also include an "Allow" button 984 that, when selected by the user, allows the TIR application to send notifications to the user. In some embodiments, and as Figure 9I depicted in, the notification modal window 977 can be configured to partially block or overlay the underlying onboarding GUI 965 such that it is not visible. Additionally, in some embodiments, when the user selects the "Allow" button 984, the onboarding GUI 970 ( Figure 9J ) is output to confirm that the onboarding process is complete.

[0227] Moving on to Figure 9K , a pop-up modal 975 is depicted. The pop-up modal 975 includes a message indicating to the user that a particular data set (e.g., the latest glucose data and the user's target glucose range) has been imported into the TIR application from another analyte monitoring application. The pop-up modal 975 also includes a message header 976 that includes the user-entered name (e.g., "You're in, [user name]!"). The pop-up modal 975 can also include an "Ok" confirmation button that can be pressed by the user. The pop-up modal 975 can also include a celebratory emoji.

[0228] In some embodiments, the user can set their TIR goal through the onboarding process. Specifically, and as Figure 9L depicted in, the onboarding GUI 980 can be utilized to set the user's TIR goal. The onboarding GUI 980 can include a time entry field 9802 through which the user can manually enter the desired TIR goal in time units (e.g., "17" hours). In another aspect of the embodiment, and as Figure 9LBest depicted in, a percentage entry field 9803 is provided through which a user can manually enter a desired TIR target in percentage units (e.g., "70%"). In some embodiments, and as Figure 9L depicted in, the onboarding GUI 980 may also include a selectable bar 9801 configured to update the TIR target in response to an eighth predetermined input from the user (such as when the user drags the selectable bar with a finger or by some other predetermined gesture).

[0229] In some embodiments, if the user updates the TIR target in one way (e.g., via the selectable bar 9801, the time entry field 9802, or the percentage entry field 9803), the onboarding GUI 980 will be updated to reflect the updated TIR target in the time entry field 9802 and the percentage entry field 9803 (e.g., 17 hours equals 70%). In this way, the onboarding GUI 980 allows the user to visualize the new TIR target in terms of both hours and percentage. In some embodiments, the onboarding GUI 980 may also include an information section 9804 that informs the user that selecting a TIR target does not make it permanent and that the user can change the TIR target at any time by going into settings. Additionally, the information section 9804 may also inform the user that the TIR application will also recommend new TIR targets based on the user's progress over time.

[0230] As Figure 9L shown, the user can select the "Back" button 9805 to return to the previous onboarding GUI. Further, in some embodiments, and as Figure 9L shown, after a new TIR target setting has been entered, the user can click "Set Target" 9806 to save the TIR target. In some embodiments, once the user clicks "Set Target" 9806, a confirmation in-app modal 981 (as Figure 9M best depicted in) is displayed on the onboarding GUI 980 to confirm that the user's TIR target has been set. In some embodiments, and as Figure 9L depicted in, the confirmation in-app modal 981 includes a "Confirm" button 9807 that the user can select to confirm the message provided in the in-app modal 981.

[0231] Go to Figure 9N, depicts the onboarding GUI 985. The onboarding GUI 985 includes information related to "Insights" provided by the TIR application, which will be described in further detail below. Specifically, the onboarding GUI 985 may include an information section 9851 that informs the user that the TIR application can provide the user with weekly insights into their progress. Additionally, in some embodiments, the information section 9851 also informs the user that the user can choose to be notified of new insights in the settings of the TIR application or by checking for updates in the "Insights" tab or icon. The onboarding GUI 985 may include a "Back" button 9852 that, when selected by the user, returns the user to the previously displayed onboarding GUI. Additionally, the onboarding GUI 985 may also include a "Next" button 9853 that, when selected by the user, displays the subsequent onboarding GUI.

[0232] In some embodiments, the onboarding GUI 990 (depicted in Figure 9O is provided during the onboarding process of the TIR application. Specifically, the onboarding GUI 990 may inform the user that the TIR application can collect health data (e.g., steps and sleep data) from a third-party health monitoring application (e.g., Apple Health) to help the user understand its impact on the user's glucose levels. The onboarding GUI 990 may also inform the user that the user can connect to a third-party health monitoring application (e.g., Apple Health) during the onboarding process and further customize preferences within the third-party health monitoring application under the "Share" tab. In some embodiments, the onboarding GUI 990 includes a "Back" button 9901 that, when selected by the user, returns the user to the previously displayed onboarding GUI.

[0233] In some embodiments, the onboarding GUI 990 includes a "Next" button or a "Continue" button 9902 that, if selected by the user for the first time, displays the onboarding GUI 995 that allows the user to connect to a third-party health monitoring application. Specifically, and as Figure 9PAs shown, the onboarding GUI 995 is depicted, where the onboarding GUI 995 can include a motion setting 9951 that can be configured by the user such that when enabled, it allows a third-party health monitoring application to share data related to the user's motion (e.g., steps or pushes) with the TIR application. In this way, the TIR application is configured to read data related to the user's motion from the third-party health monitoring application to better understand its impact on the user's glucose level. The onboarding GUI 995 can also include a sleep setting 9952 that can be configured by the user such that when enabled, it allows a third-party health monitoring application to share data related to the user's sleep (e.g., hours of sleep) with the TIR application. In this regard, the TIR application is configured to receive data related to the user's sleep from the third-party health monitoring application to better understand its impact on the user's glucose level. Additionally, the onboarding GUI 995 can include an optional "All On" button 9953 that, when selected by the user, allows the TIR application to access health data related to both the user's motion and sleep from the third-party health monitoring application. The onboarding GUI 995 can also include an information message 9954 that informs the user that the TIR application will read data from the third-party health monitoring application to help the user understand the impact of motion and sleep factors on the user's glucose level. According to another aspect of the embodiment, the onboarding GUI 995 can also include an "Allow" button 9955 that, when selected by the user, outputs Figure 9H the onboarding GUI 965 depicted in. In some embodiments, the onboarding GUI 995 can also include a "Deny" button 9956.

[0234] Furthermore, and according to another aspect of the embodiment, if the user selects the "Next" button or the "Continue" button 9902 of the onboarding GUI 995 a second time or at a subsequent time after the first selection, a notification modal will be displayed that informs the user that in order to allow the TIR application to access the third-party health monitoring application, the user must go to the settings of the third-party health monitoring application (e.g., Apple Health settings) under the "Share" tab. In some embodiments, the notification modal includes an "ok" button that the user can select to confirm the acknowledgement of the notification.

[0235] Although not shown, in some example embodiments, a user may establish profile settings through a onboarding process. For example, in some embodiments, an onboarding GUI may be output that may include multiple selectable options to prompt the user for profile information or preferences. For example, the multiple selectable options may include: an age field where the user may enter an age range; a condition field where the user may enter whether they have been diagnosed with a condition (e.g., type 1 diabetes, type 2 diabetes, or other conditions); a diagnosis field where the user may enter how long ago they were diagnosed with the condition; a medication field where the user may confirm whether they take diabetes-related medications (e.g., long-acting / basal insulin); and a medication history field where the user may enter how much diabetes-related medication the user has taken.

[0236] Example embodiments of an account and settings GUI

[0237] Figures 10A to 10M A block diagram depicting an example embodiment of an account and settings interface or related features thereof, any of which may be utilized in conjunction with the embodiments described herein. Referring to Figure 10A , a settings GUI 1000 is depicted. The settings GUI 1000a includes (but is not limited to): a text greeting 1001 that includes the name entered by the user (e.g., "Hi, Samantha!"); a text description 1002 that indicates a start period associated with the user (e.g., "Started on January 3, 2022"), where the text description 1002 is displayed distally directly adjacent to the text greeting 1001; an "Account" section 1003; a "Preferences" or "Settings" section 1004; a "Help" section 1005; and an "About" section 1006 that outputs information related to the TIR application when selected.

[0238] In some embodiments, and as Figure 10A illustrated, a selectable pencil icon 1007 is displayed adjacent to the text greeting 1001, which when selected by the user outputs a settings GUI 1010 ( Figure 10B ) that includes a name entry field 1011 where the user may edit the previously entered name associated with the user's account credentials.

[0239] In some embodiments, although Figure 10A not shown, the settings GUI may further include an "Activity" section (e.g., an "Apple Health" section) that outputs an interface related to activity settings when selected (see, for example, Figure 10L and Figure 10M )

[0240] The settings GUI 1010 ( Figure 10B)It further includes a "Save" button 1012 that a user can press to save the name entered in the name entry field 1011.

[0241] Figure 10C-1 is an example implementation of an account settings interface. An account settings GUI 1020 is depicted in Figure 10C-1. According to one aspect of the implementation, when a user selects the "Account" section 1003 in, for example, a previous settings GUI 1000( Figure 10A ), the account settings GUI 1020 can be displayed. According to another aspect of the implementation, and as depicted in Figure 10C-1, the settings GUI 1020 can include a target glucose range setting 1021 and a measurement unit setting 1023. In some implementations, although not illustrated, the target glucose range setting 1021 can be utilized such that a user can configure the target glucose range. In certain implementations, and as depicted in Figure 10C-1, the target glucose range setting 1021 can be non-configurable and is only displayed for informational purposes (e.g., to inform the user that the target glucose range is between 70 mg / dL and 180 mg / dL). For example, when a user selects the target glucose range setting 1021 in the settings GUI 1020, an output settings GUI 1030( Figure 10D ) is presented, which includes information related to the user's target glucose range. Other combinations of configurable and non-configurable settings are possible, and those skilled in the art will recognize that these combinations are fully within the scope of the present disclosure.

[0242] As shown in FIG. 10C-1, in some embodiments, the account settings GUI 1020 further includes a configurable TIR target setting 1022. Additionally, in some embodiments, although not shown, the account settings GUI 1020 may further include a selectable "Send Research Data" option that, when selected by the user, can output a "Send Research Data" GUI. The Send Research Data GUI includes an information section that informs the user that information from their account will be sent via email to the research team to help improve their TIR application experience. The information section of the Send Research Data GUI also provides details about the information or data that will be sent to the research team and assures the user that any personally identifiable information ("PII") will not be shared. Additionally, the Send Research Data GUI may further include an export information section that indicates the date the user last exported research data to the research team. According to one aspect of the embodiments, the Send Research Data GUI may include a "Send" button 126 that, when selected by the user, outputs a research confirmation modal. Specifically, the research confirmation modal is configured to partially obscure or overlay the underlying interface (e.g., the Send Research Data GUI). In some embodiments, the research confirmation modal requests confirmation that the user wishes to send their data (e.g., the user's dietary data and glucose data) to the research team. In some embodiments, the research confirmation modal may include a "Send" button that, when selected by the user, sends the user's data (e.g., the user's dietary data and glucose data) to the research team. The research confirmation modal may also include a "Cancel" button that, when selected by the user, cancels the request to send the user's data to the research team.

[0243] Although not shown, in some example embodiments, the account settings GUI 1020 (the FIG. 10C-1 GUI) may further include a selectable "About You" option that, when selected by the user, outputs an About You settings GUI 1035 (see Figure 10C-2 ). The About You settings GUI 1035 ( Figure 10C-2) may include multiple selectable options to prompt the user for profile information or preferences. For example, the multiple selectable options may include: an age field 1031 in which the user can enter an age range; a condition field 1032 in which the user can enter whether they have been diagnosed with a condition (e.g., type 1 diabetes, type 2 diabetes, or other conditions); a diagnosis field 1033 in which the user can enter how long ago they were diagnosed with the condition; a medication field 1034 in which the user can confirm whether they take diabetes-related medications (e.g., long-acting / basal insulin); and a medication history field 1036 in which the user can enter how much diabetes-related medication the user has taken. The "About You" settings GUI 1035 also includes a "Save" button 1037 that is configured to be selectable only when the user makes changes to the profile information and preferences detailed in the "About You" settings GUI 1035.

[0244] In addition, Figures 10E-1 to 10E-3 An example implementation of a settings GUI 1040 is depicted, which is an interface related to the TIR target. The settings GUI 1040 can be displayed when the user selects the TIR target setting 1022 in the previous settings GUI 1000 ( Figure 10A ). According to one aspect of the implementation, and as Figures 10E-1 to 10E-3 depicted, the TIR target can be configured by the user such that the user can select a TIR target where the TIR target will be achieved when the user is within a predetermined target glucose range during the selected time period (e.g., 17 hours). In some implementations, and as Figure 10E-1 depicted, the settings GUI 1040 includes a selectable bar 1041 that is configured to update the TIR target in response to a ninth predetermined input from the user (such as when the user drags the selectable bar with a finger or by some other predetermined gesture).

[0245] According to one aspect of the implementation, and as Figure 10E-2 best depicted, a time entry field 1042 is also provided through which the user can manually enter a desired TIR target in time units (e.g., "17" hours). According to another aspect of the implementation, and as Figure 10E-2Best depicted in, a percentage entry field 1043 is provided, through which a user can manually enter a desired TIR target in percentage units (e.g., "70%"). In some embodiments, if the user updates the TIR target in one way (e.g., through the selectable bar 1041, the time entry field 1042, or the percentage entry field 1043), the settings GUI 1040 will be updated to reflect the updated TIR target in the time entry field 1042 and the percentage entry field 1043 (e.g., 17 hours equals 70%). In this way, the settings GUI 1040 allows the user to visualize the new TIR target in terms of both hours and percentage. In some embodiments, the settings GUI 1040 includes a message indicating to the user that the TIR target change will take effect the next day.

[0246] Still referring to Figures 10E-1 to 10E-3 , in some embodiments, the settings GUI 1040 further includes an information section 1044 that informs the user of the TIR target recommended by the American Diabetes Association. Additionally, in some embodiments, the settings GUI 1040 allows the user to select a specific progress indicator for the TIR target. For example, and as Figure 10E-1 best depicted in, the user can select to view the TIR target progress in terms of hours or percentage. In other embodiments (not shown), the target progress view is not configurable. For example, in some embodiments, the user can only view the TIR target progress in terms of hours.

[0247] As Figure 10E-1 shown in, after a new TIR target setting has been entered, the user can click "Save" 1045 to update the information. In some embodiments, once the user clicks "Save" 1045, and as Figure 10E-3 best depicted in, a confirmation in-app modal 1046 is displayed on the settings GUI 1040, allowing the user to confirm the TIR target change. In some embodiments, and as Figure 10E-3 depicted in, the confirmation in-app modal 1046 includes a message indicating to the user that the TIR target change will take effect the next day.

[0248] Furthermore, Figure 10F is a settings GUI 1050 depicting an interface related to the unit of measurement. According to one aspect of the embodiment, when the user selects the measurement unit section 1023 in the previous settings GUI 1020 (Figure 10C), the settings GUI 1050 can be displayed. In some embodiments, although not shown, the unit of measurement is configurable (e.g., mg / dL or mmol / L). In some embodiments, and as Figure 10FAs depicted, the unit of measurement is not configurable and is displayed in the unit of measurement determined by the region or country of a third party (e.g., mg / dL for the United States). As Figure 10F shown in, the settings GUI 1050 includes an information message 1051 that indicates the glucose measurement unit automatically set based on the user's country. In some embodiments, the settings GUI 1050 further includes an indication message 1052 that indicates that the user can change the measurement unit through another analyte monitoring application (e.g., "Libre 2").

[0249] Figure 10G An in-app modal notification 1055 that provides information about logging out of the TIR application. According to one aspect of the embodiment, the in-app modal notification 1055 can be displayed when the user selects the "Log Out" option 1024 in the previous settings GUI 1020 (Figure 10C). According to another aspect of the embodiment, the in-app modal notification GUI 1020 can be configured to partially obscure or overlay the underlying interface (e.g., the settings GUI 1000) to make it invisible.

[0250] In addition, Figure 10H-1 A settings GUI 1060a that depicts a settings preference interface including multiple notification options for the TIR application, where the user can turn on and / or off one or more notifications. According to one aspect of the embodiment, the settings GUI 1060a can be displayed when, for example, the user selects the "Preferences" section 1004 in the previous account settings GUI 1000 ( Figure 10A ). According to another aspect of the embodiment, and as best illustrated in Figure 10H-1 , the settings GUI 1060a can include (but is not limited to) one or more of the following: a text label and description of the "TIR Challenge" notification adjacent to a switch 1061 configured to switch between an on position and an off position; a text label and description of the "Record Meal Reminder" notification adjacent to a switch 1062 configured to switch between an on position and an off position; and a text label and description of the "Scan Sensor Reminder" notification adjacent to a switch 1063 configured to switch between an on position and an off position. In some embodiments, a notification can be provided to remind the user to scan their sensor after seven hours without a scan. Those skilled in the art will understand that instead of a toggle, the settings GUI 1060a can include any one or more of the following: on-off checkboxes, on-off slider switches, on-off radio buttons, on-off buttons, etc.

[0251] According to one aspect of the embodiment, if the "Record Meal Reminder" notification is turned on, after the first reminder, if the user has not recorded a meal, the TIR application is configured to nudge the user after a predetermined period of time has elapsed (e.g., every six hours). In some embodiments, if the "Record Meal Reminder" notification is turned on, after the first reminder, if the user has recorded a meal, the TIR application is configured to nudge the user after a predetermined period of time has elapsed (e.g., every four hours).

[0252] Figure 10H-2 Depicts a settings GUI 1060a with all notifications turned off. Additionally, as Figure 10H-2 depicted, the settings GUI 1060a includes an in-app modal 1065 that provides information about disabling notification conditions and a "Go to Settings" button that opens the corresponding settings interface to allow the user to enable notifications.

[0253] Figure 10H-3 Depicts an additional example embodiment of the settings GUI. Specifically, Figure 10H-3 depicts a settings GUI 1060b that is similar to the settings GUI 1060a, except that it also includes a text label and description for the "New Insights" notification adjacent to a switch 1064 configured to toggle between on positions. In some embodiments, the settings GUI 1060b also includes configurable home screen view settings 1066. According to one aspect of the embodiment, and as Figure 10H-4 depicted, a settings GUI 1069 can be output in response to the user selecting the home screen view settings 1066 in the settings GUI 1060B. Specifically, through the settings GUI 1069, the home screen view settings 1066 can be user-configurable such that the user can select between one or more home screen views 1068, e.g., the meal view 1068a (e.g., a list of meal events) of the logbook section on the home GUI 400( Figure 4B ), home GUI 450( Figure 4D ), home GUI430( Figures 4E-1 to 4E-7 ), home GUI 485( Figures 4J-1 to 4J-3 ), home GUI 495( Figures 4K-1 to 4K-3 ), or home GUI 499( Figures 4M-1 to 4M-6 ), or the meal view 1068a of the logbook section on the home GUI 400( Figure 4B ), home GUI 450( Figure 4D ), home GUI 430( Figures 4E-1 to 4E-7 ), home GUI485( Figures 4J-1 to 4J-3 ), home GUI 495( Figures 4K-1 to 4K-3 ), or home GUI 499( Figures 4M-1 to 4M-6)Select between the time-of-day view 1068b of the logbook section (e.g., time card of the day). For example, in Figure 10H-4 , the meal view 1068a has been selected.

[0254] Figure 10H-5 Depicts the settings GUI 1060b with all notifications turned off. Additionally, as Figure 10H-5 depicted, the settings GUI 1060b includes an in-app modal 1067 that provides information about disabling notification conditions and a "Go to Settings" button that opens the corresponding settings interface to allow the user to enable notifications.

[0255] Figure 10I Depicts an example implementation of the account interface. Figure 10I Depicts the account GUI 1070, which can be displayed when the user selects the "Help" section 1005 in the previous account settings GUI 1000 ( Figure 10A ). According to some embodiments, the account GUI 1070 includes (but is not limited to): a tutorial section 1071 and a "Contact Us" section 1072.

[0256] Figure 10J Depicts the account GUI 1180, which includes contact information for TIR application help and feedback. The account GUI 1180 can be displayed when the user selects the "Contact Us" section 1072 in the previous account GUI 1070 ( Figure 10I ).

[0257] In some embodiments, in response to the user selecting the TIR tutorial section 1071 in the account GUI 1070 ( Figure 10I ), a settings interface is output, which includes: (1) a TIR tutorial option that can output a TIR-related tutorial interface when selected; (2) a small daily goal tutorial option that can output a small daily goal-related tutorial interface when selected; (3) a meal record tutorial option that can output a meal record-related tutorial interface when selected; (4) an impact score tutorial option that can output an impact score-related tutorial interface when selected; and (5) a weekly insights tutorial option that can output a weekly insights-related tutorial interface when selected.

[0258] In some embodiments, in response to the user in the account GUI 1070 ( Figure 10I) Select the TIR tutorial section 1071, and a tutorial interface related to the TIR application can be displayed. For example, in some embodiments, a tutorial interface can be displayed that informs the user about studies that have shown that TIR can be a simple and powerful way to track how food affects an individual's glucose levels. According to another aspect of the embodiment, a tutorial interface can be displayed that provides (1) user information about the TIR ring, and specifically, explains that the TIR ring represents the user's progress towards their goal and will fill as the user spends more time within the goal range, and (2) a message encouraging the user to close the TIR ring before midnight each day in order to reach their goal. In another aspect of the embodiment, a tutorial interface can be displayed that informs the user that TIR can vary from person to person, and that the American Diabetes Association recommends approximately 17 hours of TIR per day.

[0259] In yet another aspect of the implementation, a tutorial interface can be displayed that (1) provides a brief introduction to the user on how to record meals in the TIR application and (2) includes a link that, when selected by the user, outputs a meal recording information modal that includes tips for adding meals via the TIR application. Additionally, in some implementations, a tutorial interface is displayed that provides information related to meal ratings or scores to the user. For example, in some implementations, a tutorial interface can be displayed that (i) explains to the user that the TIR application rates meals based on glucose changes after eating, and that a 5-star meal will cause the least amount of glucose elevation while a 1-star meal will cause the highest, and (2) includes a link that, when selected, outputs a meal scoring information modal that includes information on how to rate or score meals in the TIR application, as described above. In some implementations, the meal scoring information modal that includes information on how to rate meals can also include emojis to indicate the impact on glucose. According to some aspects of the implementation, the meal scoring information modal can include a link that, when selected by the user, outputs another meal scoring information modal that includes details on why the score is measured three hours after the meal is consumed. In some implementations, the meal scoring information modal that includes details on why the score is measured three hours after the meal is consumed can also include a tip that provides advice to the user on how to avoid going out of range over a longer period of time. In some implementations, the meal scoring information modal also includes details on why the user should allow time between meals. Additionally, the meal scoring information modal also includes details on recording all the foods eaten in a 30-minute window under the same meal to minimize the number of meals with missing scores or ratings. Additionally, in some implementations, the meal scoring information modal also includes details on scanning at least every eight hours to ensure the TIR application has the glucose data required to provide meal ratings or scores. Additionally, in some implementations, the meal scoring information modal informs the user that for accurate meal ratings or scores, the TIR application requires glucose readings from the user at the start of each meal and two hours later, and that if the user misses a scan or has a sensor problem, the TIR application may not be able to rate the user's meals.

[0260] In yet another aspect of the implementation, a tutorial interface can be displayed that includes (1) details on why it is recommended to wait approximately three hours between meals for accurate glucose readings and (2) details on recording all the foods eaten in a 30-minute window under the same meal to minimize the number of meals with missing scores or ratings.

[0261] In addition, in some embodiments, a tutorial interface may be displayed that informs the user that the TIR application can provide weekly insights into the user's progress and that the user can choose to be notified of new insights in the settings of the TIR application or by checking for updates in the "Insights" tab or icon.

[0262] Figure 10K is a block diagram depicting the account tutorial GUI 1080 that can be displayed when the user selects the tutorial section 1071 in the previous account GUI 1070( Figure 10I ). As depicted in Figure 10K , the account tutorial GUI 1080 can include a TIR tutorial section 1081, a TIR goals and progress ring tutorial section 1082, and a dietary impact score tutorial section 1083.

[0263] In response to the user selecting the TIR tutorial section 1081 in the account tutorial GUI 1080( Figure 10K ), a tutorial interface related to TIR can be displayed. For example, in some embodiments, a tutorial interface can be displayed that explains that TIR represents how long the user stays within the target glucose range. According to another aspect of the embodiment, a tutorial interface can be displayed that informs the user that users who maintain their daily TIR are more likely to experience positive health outcomes. In another aspect of the embodiment, a tutorial interface can be displayed that informs the user that the standard target glucose range for most people is between 70 mg / dL and 180 mg / dL, but the user's doctor may have different recommendations.

[0264] In another aspect of the embodiment, and in response to the user selecting the TIR goals and progress ring tutorial section 1082 in the account tutorial GUI 1080( Figure 10K ), a tutorial interface related to TIR goals and progress rings can be displayed. For example, in some embodiments, a tutorial interface can be displayed that informs the user that the American Diabetes Association stipulates that a person's TIR should be approximately 17 hours per day. In another exemplary embodiment, a tutorial interface can be displayed that informs the user that the TIR application calculates the user's current TIR and recommends an ideal first goal. In yet another exemplary embodiment, a tutorial interface can be displayed that provides the user with information about the TIR ring and, in particular, explains that the TIR ring represents the user's progress towards their goal and will fill with each hour spent within the target range.

[0265] In another aspect of the embodiment, in response to the user selecting in the account tutorial GUI 1080( Figure 10K)Select the dietary impact score tutorial section 1083, and a tutorial interface related to the dietary impact score can be displayed. In some embodiments, for example, a tutorial interface can be displayed that explains to the user one of the purposes behind the scoring (e.g., the TIR application scores the user's diet so that the user can understand which foods are best for keeping the user within the range). In some example embodiments, a tutorial interface can be displayed that explains to the user that the score is based on the change in the user's glucose level within three hours of eating. In other example embodiments, a tutorial interface can be displayed that provides the user with a key to different score options and what each score option represents in terms of glucose change.

[0266] According to another aspect of the embodiment, the TIR application can also include an account interface related to general account and TIR application information. For example, an "About" interface can be provided that provides general information related to the TIR application. Additionally, in some embodiments, the About interface can include a selectable trial disclaimer section that, when selected by the user, outputs an account interface including a trial disclaimer and information related to the intended use of the TIR application. Specifically, the account interface with the trial disclaimer can also include an information section indicating the date on which the user signed the TIR application agreement (as seen in the previous onboarding GUI 925, such as Figure 9B seen).

[0267] Furthermore, in some embodiments, the About interface can also include a selectable license section that, when selected by the user, outputs an interface including information related to the license and notice of open source software used in the TIR application.

[0268] In another aspect of the embodiment, an interface including the terms of use of the TIR application can be output from the About interface. In some embodiments, the interface including the terms of use is displayed when the user first installs and / or opens the TIR application. Additionally, in some embodiments, an interface including the privacy policy for the TIR application can be output from the About interface. In some embodiments, the interface including the privacy policy is displayed when the user first installs and / or opens the TIR application.

[0269] Moving on to Figure 10L , an example embodiment of the activity settings GUI 1085 is depicted. According to one aspect of the embodiment, when the user selects as in the reference settings GUI 1000 ( Figure 10A)When describing the "Activity" section, the activity settings GUI 1085 can be displayed. Specifically, if the user has not previously connected to a third-party health monitoring application (e.g., Apple Health) during the onboarding process or in their settings, the activity settings GUI 1085 depicted in Figure 10L is displayed. More specifically, in some embodiments, the activity settings GUI 1085 includes an information section that informs the user that the TIR application reads the user's exercise and fitness data from the third-party health monitoring application and correlates it with the user's glucose readings to understand its impact on the user's glucose level. In some embodiments, the information section also informs the user that they can customize their preferences within the third-party health monitoring application by going to the "Share" tab. Additionally, in some embodiments, the activity settings GUI 1085 includes a "Connect" button 1086 that, when selected, allows the user to connect the TIR application to the third-party health monitoring application.

[0270] Figure 10M Additional example embodiments of the activity settings GUI are depicted. Specifically, Figure 10M depicts the activity settings GUI 1090, which is displayed when the user selects the "Activity" section described in the reference settings GUI 1000 ( Figure 10A ). More specifically, if the user has not previously connected to a third-party health monitoring application (e.g., Apple Health) during the onboarding process or in their settings, the activity settings GUI 1090 is displayed. Even more specifically, the activity settings GUI 1090 is similar to the activity settings GUI 1085 (as shown in Figure 10L ), except that it does not include a "Connect" button.

[0271] Example embodiments of a data loss GUI and related features

[0272] Figures 11A to 11G is a block diagram of an example embodiment depicting a data loss interface or its related features, any of which can be utilized with any of the embodiments described herein.

[0273] Referring to Figure 11A , an example embodiment of a block diagram of the GUI 11000 for the TIR application is depicted. The GUI 11000 is similar to the home page GUI 400 ( Figure 4B ), except that it also includes a notification associated with one or more data loss conditions (e.g., "Based on 12 hours of glucose data"). In some embodiments, and as shown in Figure 11AThe notifications associated with one or more data loss conditions depicted in can be presented as in - app notifications 11111 set on the TIR card 11112.

[0274] Figure 11B A block diagram depicting another example implementation of the GUI 11100 for the TIR application is shown. The GUI 11100 is similar to the home page GUI 450( Figure 4D ) except that it also includes a notification associated with one or more data loss conditions (e.g., "Glucose data based on 12 hours"). In some embodiments, and as Figure 11B depicted in, the notifications associated with one or more data loss conditions can be presented as in - app notifications 11101 set on the analyte graphics card 11102.

[0275] In addition, in Figure 11C the example implementation depicted, the GUI 11200 includes an in - app modal notification 11222 associated with a data loss condition. In some embodiments, the in - app modal notification 11222 can include information prompts for resolving one or more data loss conditions. In addition, the in - app modal notification 11222 can be configured to partially obscure or overlay the underlying interface to make it invisible.

[0276] Figure 11D A block diagram depicting another example implementation of the GUI 11300 for the TIR application is shown. The GUI 11300 is similar to the home page GUI 485( Figures 4J-1 to 4J-3 ) except that it also includes a notification 11301 associated with one or more data loss conditions (e.g., "Glucose data based on 12 hours"). In some embodiments, and as Figure 11D depicted in, the notification 11301 associated with one or more data loss conditions can be presented as an in - app notification 11301 on the TIR card 11302 set on the GUI 11300. In some embodiments, the in - app notification 11301 can be set directly adjacent and below the daily TIR target 11302. In some embodiments, and as Figure 11D best depicted in, the in - app notification 11301 can be set below the daily TIR target 11302 and the TIR ring 11304 that includes the TIR value 11303.

[0277] Figure 11E A block diagram depicting another example implementation of the GUI 11400 for the TIR application is shown. The GUI 11400 is similar to the home page GUI 485( Figures 4J-1 to 4J-3), except that it also includes a notification 11401 associated with one or more data loss conditions (e.g., "glucose data based on 12 hours"). In some embodiments, and as Figure 11E depicted in, the notification 11401 associated with one or more data loss conditions can be presented as an in-app banner located between the TIR card 11419 and the analyte graph card 11411 of the GUI 11400.

[0278] Figure 11E depicts a block diagram of another exemplary embodiment of the GUI 11500 for the TIR application. The GUI 11500 is similar to the home page GUI 485 ( Figures 4J-1 to 4J-3 ), except that it also includes a notification 11501 associated with one or more data loss conditions (e.g., "glucose data based on 12 hours", "incomplete glucose data", or "you have lost glucose data"). In some embodiments, and as Figure 11F depicted in, the notification 11501 associated with one or more data loss conditions can be presented as an in-app banner located between the analyte graph card 11511 and the logbook section 11518 of the GUI 15000. Specifically, the notification or in-app banner 11501 can be set directly adjacent and below one or more selectable icons 11513, and directly adjacent and above a message 11514 indicating when the GUI 11500 was last updated. In some embodiments, the notification or in-app banner 11501 can include an information icon 11502 that outputs an information modal 11600 (as Figure 11G depicted in) when selected by the user, and the information modal provides further information about the data loss condition.

[0279] Specifically, as Figure 11G shown in, the information modal 11600 can inform the user that it is possible that due to missing sensor scans or technical problems with the user's sensor, the TIR application does not have an accurate picture of the user's analyte data (e.g., glucose data) for that day. Additionally, in some embodiments, the information modal 11600 can provide the user with a reminder message that reminds the user to scan the sensor at least once every eight hours in the analyte monitoring application to avoid gaps in the analyte data (e.g., glucose data). The information modal 11600 can also include a selectable "ok" button.

[0280] Those skilled in the art will understand that the notification and data loss situation characteristics described herein are only for illustrative purposes, and any combination of independent elements or elements depicted and / or described for a particular embodiment or figure can be freely combined with any other elements or any combination of other elements depicted and / or described for any other embodiment.

[0281] Example embodiments of in-app banner notifications

[0282] The TIR application can also include in - app banner notifications, and any in - app banner notification can be utilized in conjunction with the embodiments described herein. In some embodiments, the in - app banner notification can include information related to one or more of the following: (1) Meal records (e.g., "Added Meal" or "Deleted Meal"); (2) Updated settings (e.g., "Updated Range Time"); (3) Scans (e.g., "Successfully Scanned", "Ready to Scan", "6 hours since last scan", or "Scan Unsuccessful"); Detected errors (e.g., prompting the user to try again later, or signing out and signing in to continue); and (3) No internet connection (e.g., the user needs to be notified of the internet connection to obtain the latest TIR and glucose data).

[0283] Example embodiments of activity cards and their related features

[0284] Figures 12A-1 to 12B A block diagram depicting an example embodiment of an interface including an activity card or its related features, any of which can be utilized in conjunction with the embodiments described herein.

[0285] Figures 12A-1 to 12A-4 A block diagram depicting another example embodiment of the GUI 12000 for the TIR application. The GUI 12000 is similar to the home page GUI 485 (as Figures 4J-1 to 4J-3 depicted), except that it also includes a health section 1201 that can include one or more activity cards 1202, 1203 (e.g., a motion card 1202 and a sleep card 1203). Specifically, when the user enables a third - party health monitoring application (e.g., Apple Health) to share data related to the user's motion, sleep, or both through, for example, the onboarding GUI 995 (shown in Figure 9P ), the health section 1201 can be displayed on the GUI 12000. For example, if through the motion settings 9951 of the onboarding GUI 995, the user allows the third - party health monitoring application to share only data related to the user's motion, the GUI 12000 will display the health section 1201 including the motion card 1202, as Figure 12A-1 and Figure 12A-2 depicted. Specifically, Figure 12A-1Depicts a motion card 1202 that shows the number of steps (e.g., "24,437 steps") that a user has walked within a predetermined time period (e.g., within a specific time of day). In some embodiments, and as Figure 12A-2 depicted therein, the motion card 1202 shows the number of wheelchair pushes (e.g., "1,437 pushes") that the user has received within a predetermined time period (e.g., within a specific time of day). As Figure 12A-2 and Figure 12A-3 depicted therein, the health section 1201 including the motion card 1202 can be directly adjacent to and distal relative to the logbook section 1208 of the GUI 12000.

[0286] In some embodiments, and as Figure 12A-3 best shown therein, if through, for example, the sleep setting 9952 of the onboarding GUI 995, the user allows a third-party health monitoring application to share only data related to the user's sleep, then the GUI 12000 will display a health section 1201 including a sleep card 1203 that shows the time (e.g., "17 hours 31 minutes") that the user has spent sleeping within a past predetermined time period (e.g., the previous night). Additionally, in some embodiments, and as Figure 12A-4 best depicted therein, if through, for example, the motion setting 9951 and the sleep setting 9952 of the onboarding GUI 995, the user allows a third-party health monitoring application (e.g., Apple Health) to share data related to both the user's motion and sleep, then the GUI 12000 will display a health section 1201 including the motion card 1202 and the sleep card 1203. In some embodiments, the motion card 1202 can be directly adjacent to the sleep card 1203. Additionally, in some embodiments, the health report 1201 can be directly adjacent to and distal relative to the logbook report 1208 of the GUI 12000. Further, in some embodiments, and as Figures 12A-1 to 12A-4 shown therein, the health section 1201 further includes a message 1204 that is adjacent to and distal relative to the motion card 1202 and / or the sleep card 1203, wherein the message 1204 indicates when the data displayed in the health section 1201 was last updated. In some embodiments, the sleep card 1203 and the motion card 1202 are configured to update each time the TIR application is opened.

[0287] According to yet another aspect of an embodiment, and as Figure 12B best shown therein, if in an initial setup or through an onboarding process (e.g., the onboarding GUI 995, as Figure 9PAs shown in [Figure], if the user rejects the TIR application from accessing and connecting to a third-party health monitoring application (e.g., Apple Health), the GUI 12000 may display a health section 1201 that includes a connection card 1205. Specifically, in some embodiments, the connection card 1205 may include a message that indicates that the user can gain insights into how exercise and sleep affect the user's glucose levels by connecting to the third-party health monitoring application. Additionally, in some embodiments, the connection card 1205 may include a selectable "Connect" button 1206.

[0288] Those skilled in the art will understand that the health section 1201, activity cards 1202, 1203, and their related features are for illustrative purposes only, and any independent element or combination of elements depicted and / or described for a particular embodiment or figure can be freely combined with any other element or combination of other elements depicted and / or described for any other embodiment.

[0289] Example embodiments of dietary detection GUI and its related features

[0290] Example embodiments of a method for detecting whether a user has consumed a meal will now be described. First, those skilled in the art will recognize that the method steps described herein may include software instructions stored in the memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of system 100 such that when the instructions are executed by one or more processors of the computing device, the one or more processors perform any one or all of the method steps described herein. Turning to Figure 13 , the flowchart depicts an example embodiment of a method 13500 for detecting whether a user has potentially consumed a meal ("episode" or "offset") based on data received indicating analyte levels (e.g., glucose levels).

[0291] According to one aspect of an embodiment, method 13500 may utilize one or more parameters related to analyte level shifts (e.g., glucose level shifts) when determining a meal detection. For example, a first parameter may include a minimum rate of change of the analyte level (e.g., glucose level) over time required to initiate a shift (“trigger shift change”). In certain embodiments, other parameters may be utilized to effectively detect a meal onset or shift, including but not limited to the following: (1) a threshold analyte level shift duration (e.g., a minimum analyte level shift duration or a maximum analyte level shift duration); (2) a threshold change in the analyte level throughout the onset (e.g., a maximum change or a minimum change in the glucose level throughout the onset); (3) meeting a threshold highest analyte level value and / or a threshold lowest analyte level value (e.g., a maximum lowest glucose value, a minimum lowest glucose value, a minimum highest glucose value, or a maximum highest glucose value); and (4) a threshold time window allowed between analyte level readings (e.g., a maximum amount of time allowed between glucose level readings).

[0292] Those skilled in the art will understand that parameters related to shifts and effectively detecting an onset may utilize a variety of different thresholds and numbers.

[0293] As Figure 13 seen at the top of, method 13500 begins at 13501, where a slope associated with an input analyte level measurement (e.g., a glucose level measurement) is calculated to determine the start of a shift. In some embodiments, if the slope exceeds the trigger shift change parameter, the previous timestamp is determined to be the start of the shift.

[0294] At 13502, once the start of the shift has been determined, the slope continues to be calculated to determine the end of the shift. In some example embodiments, when the slope is less than the trigger shift change, the previous timestamp is determined to be the end of the shift.

[0295] At 13503, and upon determining the end of the shift, a “trigger window” is calculated as the time (e.g., in minutes) between the start of the shift and the end of the shift. According to one aspect of an embodiment, the total analyte level change (e.g., total glucose level change) is calculated as the difference in analyte level values (e.g., difference in glucose level values) between the start of the shift and the end of the shift.

[0296] At 13504, a threshold lowest analyte level value required for effective onset detection is determined, where the threshold lowest analyte level value is calculated as the minimum analyte value (e.g., glucose value) during the shift.

[0297] At 13505, the threshold maximum analyte level value required for valid episode detection is determined, where the threshold maximum analyte level value is calculated as the maximum analyte value (e.g., glucose value) during the offset.

[0298] At 13506, the threshold time window allowed between analyte level readings (e.g., glucose level readings) is determined, where the threshold time window is calculated as the time difference between analyte level readings (e.g., glucose level readings) within an episode.

[0299] In some example embodiments, if certain threshold conditions are met, an episode is determined to be valid. These threshold conditions include, but are not limited to, the following conditions: (1) the threshold time window allowed between analyte level readings is determined to be between a minimum analyte level offset duration and a maximum analyte level offset duration; (2) the total analyte level change (e.g., total glucose level change) is determined to be between the maximum change in analyte level and the minimum change in analyte level calculated throughout the episode; (3) the threshold maximum analyte level value of the offset is between a minimum maximum analyte level value and a maximum maximum analyte level value; and (4) all of the threshold time windows are less than the maximum amount of time allowed between analyte level readings for a valid episode. In this regard, if an episode is valid, a meal for that episode is detected.

[0300] In some example embodiments, when one or more meals are entered within a short time window, the one or more entered meals can be configured such that they are considered part of a single meal entry. In some embodiments, when one or more entered meals occur within a short time window, the one or more entered meals are considered a single meal event and will be given a single score.

[0301] In some embodiments, when multiple meals are entered within a predetermined time period of the consumed meal (e.g., within one hour of the meal), the multiple meals will be recorded as a single meal. In some embodiments, for the purpose of scoring a meal event, the multiple meals recorded as a single meal can include the timestamp of the earliest meal among the multiple entered meals. According to some embodiments, the cascading of meals does not extend to meals that occur within a predetermined time (e.g., one hour from the initial meal) within the initial meal.

[0302] Figures 13A-1 to 13A-2 is a block diagram depicting an example embodiment of a meal detection interface or its related features, any of which can be utilized in conjunction with the embodiments described herein.

[0303] Referring to Figure 13A-1 and Figure 13A-2, depicts an example implementation of a block diagram of the home page GUI 485, where the home page GUI 485 further includes one or more notifications 1301 associated with a missing meal detection. In some implementations, and as Figure 13A-1 and Figure 13A-2 depicted in, one or more notifications 1301 associated with a missing meal detection can be presented as in-app notifications 1301 located between the analyte graph card 4811 and the logbook section 4808. Those skilled in the art will understand that, without departing from the scope of the present disclosure, the in-app notifications 1301 can be displayed in various other locations on the home page GUI 485.

[0304] According to one aspect of an implementation, the in-app notification 1301 can prompt the user to record a meal. In some implementations, and with reference to Figure 13A-1 and Figure 13A-2 , each of the in-app notifications 1301 includes a query 1302 asking the user if they have eaten (e.g., "Have you eaten?"), and a message 1303 indicating to the user that the user's blood glucose has risen near a specific time associated with the missing meal detection (e.g., "Your blood glucose rose around 10:34 am"). According to one aspect of an implementation, each of the in-app notifications 1301 can include a selectable "Ignore" button 1304 and a selectable meal record button 1305. Specifically, when the user selects the ignore button 1304 on a specific in-app notification 1301, the in-app notification 1301 is removed from the display of the home page GUI 485.

[0305] More specifically, in some implementations, if the user selects the meal record button 1305, a meal record GUI 500 ( Figure 5A ) is output. Additionally, in some implementations, a meal input modality 520 (as shown in Figure 5C ) can appear, where the time field 527 is pre-filled with the date and time associated with the detected missing meal, which is associated with the in-app notification 1301 from which the meal record button 1305 was selected. In some implementations, once the user records a meal within the specific time associated with the missing meal detection (e.g., by selecting the meal record button 1305 in the in-app notification 1301), the corresponding in-app notification 1301 will be removed from the home page GUI 485. Additionally, the recorded meal will be displayed in the logbook section 4808 of the home page GUI 485, for example, in the appropriate TOD card 4801 under the list 4822 of meal events 4829.

[0306] According to yet another aspect of an implementation, and as Figure 13A-2As best shown, one or more missing event markers 1310 (such as one or more missing meal icons 1310) may be displayed near the analyte trend line 4815, adjacent to and / or proximal to the analyte, or along the x-axis, at the top of the graphical window 484, or at the bottom of the graphical window 484. In some aspects of the embodiments, each missing meal icon 1310 is disposed on the analyte graphics card 4811 to allow the user to visually correlate the post-meal analyte trace with the associated missing meal and the specific time at which the missing meal was detected. In some embodiments, when the user selects the ignore button 1304 on the specific in-app notification 1301 associated with the detected missing meal, the corresponding missing meal icon 1310 is removed from the analyte graphics card 4811. In some embodiments, although not illustrated, when the user records a meal associated with a specific previously detected missing meal, the missing meal icon 1310 is replaced with a meal icon.

[0307] In some embodiments, if the user ignores or fails to act on the in-app notification 1301, after a predetermined period of time (e.g., after 24 hours), the in-app notification 1301 and the corresponding missing meal icon 1310 are removed from the home page GUI 485.

[0308] According to another aspect of the embodiments, and as Figure 13A-2 best depicted, if two in-app notifications 1301 associated with the detected missing meal are displayed on the home page GUI 485, the in-app notifications 1301 are oriented such that the first in-app notification 1301a is stacked or partially overlaid on the second in-app notification 1301b. In some embodiments, the in-app notifications 1301 are stacked in chronological order. For example, the most recent in-app notification 1301a is positioned such that it is stacked or partially overlies the past or prior in-app notification 1301b. In this way, the most recent in-app notification 1301 is more dominantly displayed on the home page GUI 485 when compared to the past in-app notification 1301 that is below or partially below the most recent in-app notification 1301 in the stack of in-app notifications 1301. Additionally, in some embodiments, if two in-app notifications 1301 are displayed on the home page GUI 485, each in-app notification 1301 includes a page number 1311 that indicates the specific in-app notification 1301 within the total number of in-app notifications 1301 displayed on the home page GUI 485 (e.g., "1 / 2" if there are a total of two in-app notifications 1301 and the most recent in-app notification 1301 is dominantly displayed on the home page GUI 485).

[0309] According to yet another aspect of the embodiments, and asFigure 13A-2 As best shown in Figure 13A-2 , if more than two in-app notifications 1301 associated with the detected missing meal are displayed on the home page GUI 485, the in-app notifications 1301 are configured such that they stack or partially overlap with each other. In some embodiments, the in-app notifications 1301 stack in chronological order. Additionally, in some embodiments, if more than two in-app notifications are displayed on the home page GUI 485, each in-app notification 1301 includes a page number 1311 that indicates the particular in-app notification 1301 within the total number of in-app notifications 1301 displayed on the home page GUI 485 (e.g., "1 / 10" if there are a total of ten in-app notifications 1301 and the most recent in-app notification 1301 is dominantly displayed on the home page GUI 485). Further, according to some embodiments, once an in-app notification is removed from the GUI 485 (e.g., by the user ignoring the in-app notification or logging a meal corresponding to a particular time associated with the missing meal detection), the page number is configured to update to reflect the new total number of in-app notifications (e.g., if the user selects the ignore button on one of the ten in-app notifications, the page number on that in-app notification will update to reflect "1 / 9" instead of "1 / 10").

[0310] Additionally, according to another aspect of the embodiments, and in response to the user's tenth predetermined input (such as when the user taps or swipes on a particular in-app notification 1301, selects the ignore button 1304, or makes some other predetermined gesture), the underlying in-app notification 1301 will be revealed at the top of the stack of in-app notifications 1301. For example, if the user selects the ignore button 1304 on one of the three in-app notifications 1301, the second in-app notification 1301 will be dominantly displayed on the home page GUI 485. In some embodiments, the second in-app notification 1301 among the three in-app notifications 1301 will further display a page number 1311 indicating that it is the "2 / 3" in-app notification 1301. Additionally, if the user selects the ignore button 1304 on the second in-app notification 1301, the third in-app notification 1301 will be dominantly displayed on the home page GUI 485. In some embodiments, the third in-app notification 1301 among the three in-app notifications 1301 will further display a page number 1311 indicating that it is the "3 / 3" in-app notification 1301.

[0311] In some embodiments, the analyte graphic card 4811 of the home page GUI 485 is configured to be updated such that the missing meal icon 1310 corresponding to the in-app notification 1301 that is dominantly displayed is shown on the analyte graphic card 4811. For example, if the user swipes from the first in-app notification 1301 such that the second in-app notification 1301 is dominantly displayed on the home page GUI 485, the analyte graphic card 4811 is configured to be updated such that the missing meal icon 1310 associated with the first in-app notification 1301 is removed from the analyte graphic card 4811 and the missing meal icon 1310 associated with the second in-app notification 1301 is shown on the analyte graphic card 4811.

[0312] Although the notification 1301 associated with the missing meal detection has been described herein with reference to the home page GUI 485, those skilled in the art will understand that, without departing from the scope of the present disclosure, the notification 1301 and its related features may be utilized in conjunction with the home page GUI 400( Figure 4B ), the home page GUI 450( Figure 4D ), the home page GUI 430( Figures 4E-1 to 4E-7 ), the home page GUI 485( Figures 4J-1 to 4J-3 ), the home page GUI 495( Figures 4K-1 to 4K-3 ), and the home page GUI 499( Figures 4M-1 to 4M-2 ).

[0313] For example, Figure 13B-1 and Figure 13B-2 are block diagrams depicting the home page GUI 499 that includes meal detection features. Specifically, and with reference to Figure 13B-1 and Figure 13B-2 , one or more notifications 1351 associated with the missing meal may be presented as in-app notifications 1351 on the home page GUI 499, where the home page GUI 499 includes: an average meal rating card 4991 that includes an average meal rating 4920, a graphical indication 4921 corresponding to the average meal rating 4920, and an average meal rating indicator 4923 that visually maps the average meal rating provided over a predetermined period of time; an analyte graphic card 4910 that includes an analyte graphic 49011, the analyte graphic including an analyte trend line 49015; and a logbook section 4998 that includes a list 4992 of meal events 4999. In some example embodiments, the in-app notification may be located between the analyte graphic card 4910 and the logbook section 4998 of the home page GUI 499. Those skilled in the art will understand that, without departing from the scope of the present disclosure, the in-app notification 1351 may be displayed in various other locations on the home page GUI 499.

[0314] In some embodiments, and still with reference toFigure 13B-1 and Figure 13B-2 , each of the in - app notifications 1351 includes an inquiry 1352 that asks the user whether the user has eaten (e.g., "Have you eaten?"), and a message 1353 that indicates to the user that the user's blood glucose has risen near a specific time associated with the missing meal detection (e.g., "Your blood glucose has risen around 10:34 am"). According to one aspect of an embodiment, each of the in - app notifications 1351 may include an optional "Ignore" button 1354 and an optional meal record button 1355. Specifically, when the user selects the ignore button 1354 on a specific in - app notification 1351, the in - app notification 1351 is removed from the display of the home page GUI 499.

[0315] According to one aspect of an embodiment, if the user selects the meal record button 1355, a meal record GUI 500 is output Figure 5A ). In addition, in some embodiments, a meal input modality 520 (as shown in Figure 5C ) may appear, where the time field 527 is pre - filled with the date and time associated with the detected missing meal, and the detected missing meal is associated with the in - app notification 1351 from which the meal record button 1355 was selected. In some embodiments, once the user records a meal within the specific time associated with the missing meal detection (e.g., by selecting the meal record button 1355 in the in - app notification 1351), the corresponding in - app notification 1351 is removed from the home page GUI 499. In addition, the recorded meal will be displayed in the logbook section 4998 of the home page GUI 499, for example, under the list 4992 of meal events 4999.

[0316] According to yet another aspect of an embodiment, and as shown in Figure 13B-2As best shown, one or more missing event markers 1350 (such as one or more missing meal icons 1350) can be displayed near the analyte trend line 49015, close to the analyte trend line and / or proximally to the analyte, or along the x-axis, at the top of the graph window 49904, or at the bottom of the graph window 49904. In some aspects of the embodiments, each missing meal icon 1350 is located on the analyte graphic card 49011 to allow the user to visually associate the post-meal analyte trace with the associated missing meal and the specific time at which the missing meal was detected. In some embodiments, when the user selects the ignore button 1354 on a specific in-app notification 1351 associated with a detected missing meal, the corresponding missing meal icon 1350 is removed from the analyte graphic card 49011. In some embodiments, although not illustrated, when the user records a meal associated with a specific previously detected missing meal, the missing meal icon 1350 is replaced with a meal icon.

[0317] In some embodiments, if the user ignores or fails to act on the in-app notification 1351, then after a predetermined period of time (e.g., after 24 hours), the in-app notification 1351 and the corresponding missing meal icon 1350 are removed from the home page GUI 499.

[0318] According to another aspect of the embodiments, and as Figure 13B-2 best depicted, if two in-app notifications 1351 associated with a detected missing meal are displayed on the home page GUI 499, then the in-app notifications 1351 are oriented such that the first in-app notification 1351a is stacked or partially overlaid on the second in-app notification 1351b. In some embodiments, the in-app notifications 1351 are stacked in chronological order. For example, the most recent in-app notification 1351a is positioned such that it is stacked or partially overlies the past or prior in-app notification 1351b. In this way, the most recent in-app notification 1351 is more dominantly displayed on the home page GUI 499 when compared to the past in-app notification 1351 that is below or partially below the most recent in-app notification 1351 in the stack of in-app notifications 1351. Additionally, in some embodiments, if two in-app notifications 1351 are displayed on the home page GUI 499, then each in-app notification 1351 includes a page number 13511 that indicates the specific in-app notification 1351 among the total number of in-app notifications 1351 displayed on the home page GUI 499 (e.g., "1 / 2" if there are a total of two in-app notifications 1351 and the most recent in-app notification 1351 is dominantly displayed on the home page GUI 499).

[0319] According to yet another aspect of the embodiment, and as best shown in Figure 13B-2 if more than two in-app notifications 1351 associated with the detected missing meal are displayed on the home page GUI 499, the in-app notifications 1351 are configured such that they stack or partially overlap each other. In some embodiments, the in-app notifications 1351 are stacked in chronological order. Further, in some embodiments, if more than two in-app notifications are displayed on the home page GUI 499, each in-app notification 1351 includes a page number 13511 that indicates the particular in-app notification 1351 among the total number of in-app notifications 1351 displayed on the home page GUI 499 (e.g., "1 / 10" if there are a total of ten in-app notifications 1351 and the most recent in-app notification 1351 is dominantly displayed on the home page GUI 499). Additionally, according to some embodiments, once an in-app notification is removed from the GUI 499 (e.g., by the user ignoring the in-app notification or logging a meal corresponding to a particular time associated with the missing meal detection), the page number is configured to update to reflect the new total number of in-app notifications (e.g., if the user selects the ignore button on one of the ten in-app notifications, the page number on that in-app notification will update to reflect "1 / 9" instead of "1 / 10").

[0320] Further, according to another aspect of the embodiment, in response to an eleventh predetermined input by the user (such as when the user taps or swipes on a particular in-app notification 1351, selects the ignore button 1354, or makes some other predetermined gesture), the underlying in-app notification 1351 will be revealed at the top of the stack of in-app notifications 1351. For example, if the user selects the ignore button 1354 on one of the three in-app notifications 1351, the second in-app notification 1351 will be dominantly displayed on the home page GUI 499. In some embodiments, the second in-app notification 1351 among the three in-app notifications 1351 will further display a page number 13511 indicating that it is the "2 / 3" in-app notification 1351. Additionally, if the user selects the ignore button 1354 on the second in-app notification 1351, the third in-app notification 1351 will be dominantly displayed on the home page GUI 499. In some embodiments, the third in-app notification 1351 among the three in-app notifications 1351 will further display a page number 13511 indicating that it is the "3 / 3" in-app notification 1351.

[0321] In some embodiments, the analyte graphic card 4910 of the home page GUI 499 is configured to be updated such that the missing meal icon 1350 corresponding to the in-app notification 1351 that is predominantly displayed is shown on the analyte graphic card 4910. For example, if the user swipes from the first in-app notification 1351 such that the second in-app notification 1351 is predominantly displayed on the home page GUI 499, the analyte graphic card 4910 is configured to be updated such that the missing meal icon 1350 associated with the first in-app notification 1351 is removed from the analyte graphic card 4910, and the missing meal icon 1350 associated with the second in-app notification 1351 is shown on the analyte graphic card 4910.

[0322] Example embodiments of insight GUI and its related features

[0323] Figures 14A-1 to 14E is a block diagram depicting an example embodiment of an insights interface or its related features, any of which can be utilized with any of the embodiments described herein. Referring to Figures 14A-1 to 14A-5 , depicts an example embodiment of a block diagram of the insights GUI 14000 for a TIR application. The insights GUI 14000 can be displayed when the user selects the insights icon home page GUI 400( Figure 4B ), home page GUI 450( Figure 4D ), home page GUI 430( Figures 4E-1 to 4E-7 ), home page GUI 485( Figures 4J-1 to 4J-3 ), home page GUI 495( Figures 4K-1 to 4K-3 ), or home page GUI 499( Figures 4M-1 to 4M-6 ). According to some embodiments, and as depicted in Figures 14A-1 to 14A-4 , the insights GUI 14000 includes: (1) an insights portion 14100, which can include one or more insights cards 14400, 14500; (2) a top meals portion 14200, which can include a list 14201 of meal information that includes the highest-scoring meal event 14202 rated according to a score 14203 assigned based on a recorded corresponding analyte response; (3) a selectable home icon 14300; (4) a selectable insights icon 14301; (5) a selectable "+" icon 14302; and (6) a selectable settings icon 14303.

[0324] According to one aspect of an embodiment, and as Figure 14A-1Best depicted in, the insights section 14100 can include one or more insight cards 14400, 14500, including but not limited to a "Best Day" insight card 14400 and a "Progress" insight card 14500 that can be based on dietary information and data indicating analyte levels. Specifically, dietary information and data indicating analyte levels (e.g., glucose levels) can be utilized to determine the user's progress over a predefined time period, including but not limited to the user's "best" day (e.g., the day within a predefined time period (e.g., a one-week period) when the user spent the most time in TIR, had the highest daily score, or the highest average dietary rating). Measure the user's progress with respect to specific criteria related to the user's dietary information and data indicating analyte levels (e.g., criteria related to TIR, daily score, average dietary rating, etc.). The insights GUI is configured to have insight cards 14400 and 14500 with statistical data related to the user's progress.

[0325] Specifically, in some example embodiments, the Best Day insight card 14400 can include a summary message 14401 that has statistics detailing the user's "best" day TIR within a predefined time period (e.g., one week), or what the user's highest TIR was on a specific day within a predefined time period (e.g., "From February 6th to 12th, your highest TIR in a day was on Friday, February 11th, with 16 hours within the range"). According to some embodiments, the message 14401 can indicate the user's highest TIR in hours or as a percentage value.

[0326] In some embodiments, if the user has no hours above zero within the range, the Best Day insight card 14400 will display the message 14401, where the message 14401 indicates that the user had zero hours within the range (e.g., "From February 20th to 26th, your highest TIR in a day was on Friday, February 25th, with 0 hours").

[0327] In some embodiments, the Best Day insight card 14400 can include a summary message 14401 that details the user's best day within a predefined time period, where the user received the highest daily score (e.g., "From February 6th to February 12th, the day with the highest score was Wednesday, February 9th, with 87 points").

[0328] In some embodiments, the Best Day insight card 14400 can include a summary message 14401 that details the day with the highest average dietary rating for the user within a predefined time period (e.g., "From January 30th to February 5th, the day with the highest rating was Wednesday, February 2nd, with an average rating of 4.8").

[0329] In some embodiments, after a predefined time period (e.g., a one-week or seven-day time period), the Best Day Insights Card 14400 is displayed on the Insights GUI 14000. For example, after a seven-day time period (e.g., every Sunday of each week), the Best Day Insights Card 14400 is displayed on the Insights GUI 14000, where the Best Day Insights Card 14400 includes a message 14401. In certain embodiments, the Insights GUI 14000 is configured to be updated such that the displayed Best Day Insights Card 14400 is replaced with a new Best Day Insights Card 14400 at a predefined frequency or after each subsequent predefined time period (e.g., every Sunday or every seven days, a new Best Day Insights Card 14400 is displayed on the Insights GUI 14000). In this regard, the Insights GUI 14000 is configured to be updated to display to the user the latest Best Day Insights Card 14400 corresponding to the latest predefined time period.

[0330] In some embodiments, if there is no most recent Best Day Insights Card 14400 (e.g., if the user intermittently monitors analyte data, or if after a predefined time period the user does not monitor analyte data during that corresponding time or there is no TIR application to determine the user's progress), the Insights GUI 14000 is configured to display the most current Best Day Insights Card 14400 (e.g., if the user last monitored analyte data a month ago, the Best Day Insights Card 14400 since a month ago is displayed).

[0331] In some embodiments, although not illustrated, when a new Best Day Insights Card 14400 is available, the "Insights" icon displayed on any interface output by the TIR application is configured to provide an animation to indicate to the user that a new Insights Card 14400 is available. For example, in some embodiments, the Insights icon is configured to change color (e.g., including a colored portion, such as blue) to indicate that a new Insights Card is available.

[0332] In some example embodiments, and as Figure 14A-1 and Figure 14A-4 best shown in, the Best Day Insights Card 14400 may further include an Insights Time Indicator 14402, which is configured to indicate the amount of time elapsed since the Best Day Insights Card 14400 was displayed on the Insights GUI 14000 (e.g., "1 minute ago", "1 week ago", etc.). As Figure 14A-4As shown, in some embodiments, the Best Day Insights Card 14400 may also include a "New" label 14403, which indicates to the user that the Best Day Insights Card 14400 has been newly added to the Insights GUI 14000 or has not been viewed by the user. In some embodiments, in response to a seventh predetermined gesture of the user (such as a tap gesture or some other predetermined gesture), the "New" label 14403 is removed from the Best Day Insights Card 14400. In some embodiments, after a predetermined period of time (e.g., after 24 hours), the "New" label 14403 is automatically removed from the Best Day Insights Card 14400.

[0333] In some embodiments, the Insights GUI 14000 is configured to display an Insights section 14100 that includes only the Best Day Insights Card 14400 (see, for example, Figure 14A-5 ). In other embodiments, and as Figure 14A-1 and Figure 14A-4 depicted, the Insights GUI 14400 may display an Insights section 14100 that includes both the Best Day Insights Card 14400 and the Progress Insights Card 14500 (see, for example, Figure 14A-1 and Figure 14A-4 ).

[0334] According to some embodiments, and with reference to Figure 14A-1 and Figure 14A-4 , the Progress Insights Card 14500 may include a summary message 14501 that details the user's TIR or daily score progress over a predefined period (e.g., "From February 6th to 12th, your average time within range was 2 hours more than from January 30th to February 5th" or "From February 6th to 12th, your average daily score was 4 points higher than from January 30th to February 5th"). In some embodiments, the TIR application is configured to compare the user's average TIR or daily score over a most recent predefined period with the user's average TIR or daily score over a previous predefined period (e.g., comparing the user's average TIR or daily score over the most recent seven days with the user's average TIR or daily score over the previous seven days). According to some embodiments, the message 14501 may include an indication of the user's TIR progress in terms of hours or percentage values.

[0335] In some embodiments, the TIR application is configured to compare the average TIR or daily score of the user over a most recent predefined time period with the average TIR or daily score of the user during the first week of using the TIR application. In some embodiments, the progress insight card 14500 is only displayed after the TIR application has the average TIR or daily score of the user over two predefined time periods for progress comparison. In some embodiments, the insight GUI 14000 is configured to be updated such that after the first progress insight card 14500 is displayed, the displayed progress insight card 14500 is replaced with a new progress insight card 14500 at a predefined frequency (e.g., every Sunday or every seven days, a new progress insight card 14500 is displayed on the insight GUI 14000). In this regard, the insight GUI 14000 is configured to be updated to display the user's most recent progress (e.g., the user's most recent TIR progress).

[0336] In some embodiments, if there is no most recent progress insight card 14500 (e.g., if the user intermittently monitors analyte data, or if after a predefined time period the user does not monitor analyte data during that corresponding time), the insight GUI is configured to display the most current progress insight card 14500 (e.g., the progress insight card 14500 since a month ago).

[0337] In some embodiments, when a new progress insight card 14500 is available, the "Insight" icon displayed on any interface output by the TIR application is configured to provide an animation to indicate to the user that a new insight card 14500 is available. For example, in some embodiments, the insight icon is configured to change color (e.g., including a colored portion, such as blue) to indicate that a new insight card 14500 is available.

[0338] In some aspects of the embodiments, if the average TIR of the user is equal to or lower than the average TIR during the first week of the user using the TIR application, the progress insight card 14500 including the user's TIR progress is not displayed on the insight GUI 14000.

[0339] In some example embodiments, and as Figure 14A-1 and Figure 14A-4 best shown in, the progress insight card 14500 may further include an insight time indicator 14502 configured to indicate the amount of time elapsed since the progress insight card 14500 was displayed on the insight GUI 14000 (e.g., "1 minute ago", "1 week ago", etc.). Additionally, in some embodiments, and as Figure 14A-1As best depicted in, the progress insight card 14500 may also include a "new" label 14503, which indicates to the user that the progress insight card 14500 has been newly added to the insight GUI 14000 or has not been viewed by the user yet. In some embodiments, and as Figure 14A-4 best depicted in, in response to an eighth predetermined gesture of the user (such as a tap gesture or some other predetermined gesture), the "new" label 14503 is removed from the progress insight card 14500. In some embodiments, after a predetermined period of time (e.g., after 24 hours), the "new" label 14503 is automatically removed from the progress insight card 14500.

[0340] Referring to Figures 14A-1 to 14A-4 , in some embodiments, the insight GUI 14000 includes a "Past Insights" link 14600, which outputs a past insight GUI 14650 when selected by the user, as Figures 14B-1 to 14B-3 shown in. As Figure 14B-1 best shown in, the past insight GUI 14650 is configured to display an insight log 14651, wherein the insight log 14651 may include historical best day insight cards 14400 and historical progress insight cards 14500, as well as the most recent best day insight cards 14400 and the most recent progress insight cards 14500. Specifically, in some embodiments, the insight log 14651 is configured to display the best day insight cards 14400 and / or progress insight cards 14500 in chronological order, wherein the most recent best day insight cards 14400 and / or the most recent progress insight cards 14500 are displayed at the top portion of the insight log 14651. As Figure 14B-3 shown in, the past insight GUI 14650 may be configured to display an insight log 14651 that includes only the best day insight cards 14400 (e.g., historical best day insight cards 14400 and the most recent best day insight cards 14400).

[0341] In some embodiments, if the user can select a specific best day insight card 14400 or progress insight card 14500 from the past insight GUI 14650, a report GUI 600 associated with a specific day corresponding to the best day insight card 14400 or progress insight card 14500 is output (e.g., Figure 6B-1 and Figure 6B-2 ), or a home page interface corresponding to the past day is output.

[0342] According to one aspect of the implementation, the past insights GUI 14650 is configured to display the best day insights card 14400 and the progress insights card 14500 during the relevant time period when the TIR application has data. For example, if the data required to output the best day insights card 14400 and / or the progress insights card 14500 is missing during the time period from February 6, 2022 to March 26, 2022, the past insights GUI 14650 may display the historical best day insights card 14400 and the progress insights card 14500 from March 27, 2022 to April 2, 2022 and the historical best day insights card 14400 and the progress insights card 14500 from January 30, 2022 to February 5, 2022.

[0343] In some implementations, and as Figure 14B-2 shown, if no insights are available yet (e.g., the first predefined time period has not elapsed for the best day insights card 14400 to be displayed, or the first most recent predefined time period that can be compared with the previous predefined time period of the prompt of the progress insights card 14500 has not elapsed), the past insights GUI 14650 will display a message 14652 indicating to the user that no insights are available yet. Additionally, in some implementations, the past insights GUI 14650 can also inform the user that insights become available when there is data from the previous week. In some implementations, and as Figure 14B-1 and Figure 14B-2 depicted, the past insights GUI 14650 can include an information icon 14653 that outputs an information modal 14700 ( Figure 14C ) when selected by the user, and this information modal informs the user that when there is analyte (e.g., glucose) data from a previous predefined time period (e.g., the previous week), insights can occur at a predefined frequency (e.g., every Sunday of each week, or every seven days), and the user can choose to receive notifications when new insights cards are released. Additionally, in some implementations, the information modal 14700 can inform the user that the user can choose to receive notifications when new insights are released, and past insights from other predefined time periods (e.g., the past few weeks) are saved and can be viewed at any time. In some implementations, the information modal 14700 notes that the longer the user uses continuous glucose monitoring and the TIR application, the more insights will be available. In some implementations, the information modal 14700 includes a selectable notification preference link 14701.

[0344] As Figure 14B-1Best depicted in, in some embodiments, the insights log 14651 is divided into sub - parts 14654, where each sub - part 14654 represents a different predetermined time period. For example, the insights log 14651 can be divided into sub - parts 14654 of seven - day or one - week periods. In this regard, the best - day insights card 14400 and the progress insights card 14500 for each seven - day or one - week period are shown in the corresponding sub - part 14654 of the insights log 14651. For example, the best - day insights card 14400 and the progress insights card 14500 corresponding to February 6, 2022 to February 12, 2022 are shown in the sub - part 14654 related to the time period from February 6, 2022 to February 12, 2022. The insights log 14651 can be configured to be scrollable and / or dynamic. Thus, in some embodiments, the content shown on the insights log 14651 can change in response to a twelfth predetermined input from the user (such as when the user scrolls, drags, pulls the screen, or by some other predetermined gesture). In this way, the past insights GUI 14650 can include multiple views, where each view is configured to show a portion of the past insights GUI 14650 to the user, and different best - day insights cards 14400 and progress insights cards 14500 can be shown depending on the view.

[0345] According to one aspect of an embodiment, the past insights GUI 14650 can include an insights availability message 14655 ( Figure 14B-1 and Figure 14B-2 ), which indicates to the user that the insights become available when there is data from the previous week.

[0346] Returning to Figures 14A-1 to 14A-3 , and according to another aspect of an embodiment, the top meals section 14200 of the insights GUI 14000 can list the top - rated meal events 14202 recorded over a predetermined time period (e.g., one week or more, two weeks, multiple consecutive weeks, etc.). In the meal list 14201, and with reference to Figure 14A-1 and Figure 14A-3, the diets can be sorted in descending order of the assigned values from the highest score 14203 to the lowest score 14203, where the score 14203 is the assigned value corresponding to the analyte response based on data indicating the user's analyte level. In some embodiments, the analyte response can be based on the change in analyte level over a predetermined period of time after consuming a particular diet. In some embodiments, a score 14203 is given to diet event 14202 based on the change in analyte level from the time of consumption of the particular diet event to the peak glucose within three hours of eating. In some embodiments, the top diet section 14200 is configured to list a predefined number of the highest-scoring diet events 14202 recorded over a predetermined period (e.g., the top diet section 14200 is configured to list three or the top three highest-scoring diet events 14202 among the highest-scoring diet events 14202 recorded over a predetermined period).

[0347] In some embodiments, the score 14203 can be a number between one and five, where a higher assigned value corresponds to a lower analyte response and a lower assigned value corresponds to a higher analyte response. For example, and as previously detailed, (1) a change in analyte level from 0 mg / dL to 24 mg / dL within the three-hour post-meal period can correspond to a "5" score 14203; (2) a change in analyte level from 25 mg / dL to 49 mg / dL within the three-hour post-meal period can correspond to a "4" score 14203; (3) a change in analyte level from 50 mg / dL to 74 mg / dL within the three-hour post-meal period can correspond to a "3" score 14203; (4) a change in analyte level from 75 mg / dL to 99 mg / dL within the three-hour post-meal period can correspond to a "2" score 14203; and (5) a change in analyte level of 100 mg / dL or higher within the three-hour post-meal period can correspond to a "1" score 14203.

[0348] As Figure 14A-1 and Figure 14A-3As depicted in the Insights GUI 14000, the score 14203 can be displayed in a graphical element, such as the asterisk icon 14204. In some embodiments, the asterisk icon 14204 is filled with a colored portion, such as yellow. In many embodiments (not shown), the asterisk icon 14204 is unfilled and includes a dashed outline to indicate a missing meal score 14203. In some embodiments, although not shown, the missing meal score 14203 is indicated by the character "?". In some embodiments, the character "?" is displayed in the asterisk icon 14204 instead of a numerical value to indicate that a particular meal has not been scored. A missing meal score 14203 occurs when one or both of the following happen: (1) the user records the next meal too quickly, or (2) the In-Range Time application does not have sufficient analyte data to score the meal (e.g., the user is not scanned in a timely manner to ensure that glucose data has been transmitted to the In-Range Time application).

[0349] Referring Figure 14A-1 and Figure 14A-3 and according to another aspect of the embodiment, each of the meal events 14202 listed on the Insights GUI 14000 provides details about a particular meal consumed within a predetermined period of time (e.g., one week or more, two weeks, multiple consecutive weeks, etc.). In some embodiments, and as Figure 14A-3 best shown in, each meal event 14202 can include a text description 14205 of the meal, a photo or picture 14206 associated with the meal, a portion indicator 14207 that describes the relative portion of the meal, and / or a score 14203 associated with the meal. In some embodiments, and as Figure 14A-3 best shown in, the meal event 14202 can additionally or alternatively include one or more meal tags 14208 associated with the meal (e.g., "lettuce", "blueberries", "cheese").

[0350] According to one aspect of the embodiment, and referring Figure 14A-3 , when a meal has been entered and scored but no insights are yet available, the Insights GUI 1400 is configured to display an Insights section 14100 that includes a message 14101 indicating that no insights are yet available and a Top Meals section 14200 that includes a list 14201 of meal information.

[0351] According to another aspect of the embodiment, and as Figure 14A-4 shown in, when a meal has not been entered or scored but insights are available, the Insights GUI 14000 is configured to display an Insights section 14100 that includes a Best Day Insights Card 14400 and / or a Progress Insights Card 14500 and a Top Meals section 14200 that includes a message 14210 indicating that the meal has not been scored.

[0352] In some embodiments, and as Figure 14A-4 shown, when a meal has not been entered or recorded by the user, the Insights GUI 14000 may include an Insights section 14100 and a Top Meals section 14200. The Insights section includes a Best Day Insights Card 14400 and / or a Progress Insights Card 14500. The Top Meals section includes a message 14210 indicating that the meal has not been scored yet.

[0353] Furthermore, according to one aspect of the embodiment, each of the meal events 14202 listed in the Top Meals section 14200 of the Insights GUI 14000 is selectable, and when selected by the user, outputs a Meal Review GUI 800 that provides details related to the selected meal event 14202 (as Figure 8 shown). In some embodiments (although not illustrated in Figure 8 ), the Meal Review GUI 800 may include a "Back" button that, when selected by the user, outputs the previous interface from which the specific meal event corresponding to the Meal Review GUI 800 was selected.

[0354] Referring to Figures 14A-1 to 14A-4 , the Insights GUI 14000 may further include an "All Meals" link 14250 that, when selected by the user, outputs a Meals GUI 14800 (as Figures 14D-1 to 14D-3 shown), which provides the user with additional insights into the effects of consuming specific foods. According to one aspect of the embodiment, and referring to Figures 14D-1 to 14D-2 , the Meals GUI 14800 includes a list 14801 of meal information that includes all meal events 14802 recorded in the same predetermined time period (e.g., one week or more, two weeks, multiple consecutive weeks, etc.) as the meal events 14202 recorded in the Insights GUI 14000. For example, if the Top Meals section 14200 of the Insights GUI 14000 displays the highest-scoring meal events 14202 recorded in a two-week time period, the Meals GUI 14800 is configured to display a list 14801 of all meal events 14802 recorded in the two-week time period. Specifically, and similar to the meal events 14202 listed in the Top Meals section 14200 of the Insights GUI 14000 ( Figure 14A-1 and Figure 14A-3),The dietary events 14802 on the dietary GUI 14800 are rated according to the scores 14803 assigned based on the corresponding analyte responses recorded. In some embodiments, in the dietary list 14801, the diets can be sorted from the highest score 14803 to the lowest score 14803, where the score 14803 is an assigned numerical value corresponding to the analyte response based on the data indicating the analyte levels of the user. In some embodiments, when one or more diets are given the same score 14802, these diets can be sorted according to the variance of the analyte levels in the dietary list 14801. For example, if two diets are given the score 13802 "3", the diets can be sorted from the lowest PeakDelta or analyte level variance value to the highest PeakDelta or analyte level variance value. Additionally, in some embodiments, if one or more diets are given the same score 14802 and the same analyte level variance, the diets can be sorted in chronological order.

[0355] In some embodiments, and as Figure 14D-2 best shown in, when a diet is entered without being scored, each unrated dietary event 14802 displayed on the dietary information list 14801 includes (1) an unfilled star icon 14804 that includes a dashed line for indicating the missing dietary score, or in some cases, or (2) no star icon to indicate the missing dietary score.

[0356] In some embodiments, and as Figure 14D-3 best shown in, when the user has not yet entered or recorded a diet, the dietary GUI 14800 displays a message 14805 indicating to the user that the diet has not been scored. Additionally, in some embodiments, the dietary GUI 14800 can further inform the user that a higher rating means a higher likelihood of staying within the target range.

[0357] In some embodiments, and as Figures 14D-1 to 14D-3 shown in, the dietary GUI 14800 further includes an information icon 14806 that outputs a dietary scoring information modal when selected, and the dietary scoring information modal includes information on how to rate or score a diet in the TIR application. In some embodiments, the dietary scoring information modal including information on how to rate a diet can further include emojis to indicate the impact on glucose.

[0358] According to another aspect of the embodiment, and similar to the dietary events 14202 listed on the insights GUI 14000 (as Figure 14A-1 and Figure 14A-3(best shown in), each of the dietary events 14802 listed on the dietary GUI 14800 provides details about a specific diet consumed within a predetermined period (e.g., one week or more, two weeks, multiple consecutive weeks, etc.). In some embodiments, and as Figure 14D-1 best shown in, each dietary event 14802 on the dietary GUI 14800 may include a text description 14815 of the diet, a photo or picture 14816 associated with the diet, a portion indicator 14817 describing the relative portion of the diet, and / or a score 14803 associated with the diet. In some embodiments, the dietary event 14802 may additionally or alternatively include one or more dietary labels 14818 associated with the diet (e.g., "lettuce", "blueberries", "cheese").

[0359] According to one aspect of the embodiment, and in response to the user's ninth predetermined gesture, such as when the user pulls down or scrolls on the dietary GUI 14800, or by some other predetermined gesture, the user can scroll through the dietary GUI 14800 so that they can scroll through the different dietary events 14802 listed thereon.

[0360] In some embodiments, and still referring to Figures 14D-1 to 14D-3 , the dietary GUI 14800 may include an information message 14807 that indicates to the user that the higher the score, the higher the likelihood of staying within the target range. Additionally, the dietary GUI 14800 may further include a back button 14809 that outputs the insight GUI 14000 when selected by the user (see, for example, Figures 14A-1 to 14A-4 ).

[0361] Furthermore, according to one aspect of the embodiment, each of the dietary events 14802 listed in the list of the dietary GUI 14800 is selectable, and when selected by the user, outputs a dietary review GUI 800 that provides details related to the selected dietary event 14802 (as shown in Figure 8 ). In some embodiments (although not illustrated in Figure 8 ), the dietary review GUI 800 may include a "back" button that outputs the previous interface when selected by the user, from which the specific dietary event corresponding to the dietary review GUI 800 was selected.

[0362] According to one aspect of the embodiment, an insight-related notification 14900 may be presented as a pop-up window or banner notification 14900 shown to the user outside of the TIR application (e.g., on the lock screen), as shown in Figure 14EAs seen in. In some example embodiments, when new insight cards are available, a notification 14900 will be displayed, which includes a message notifying the user that the user data has been analyzed within a predefined time period (e.g., last week). Additionally, in some embodiments, the notification 14900 can prompt the user to tap on the notification to view the available new insight cards.

[0363] The various aspects of the subject matter have been set forth above to review and / or supplement the embodiments described so far. Here, the focus is on the interrelationships and interchangeability of the following embodiments. In other words, it is emphasized that unless otherwise explicitly stated or logically implausible, each feature of an embodiment can be combined with each other feature. The embodiments described herein are reiterated and extended in the following paragraphs without explicit reference to the drawings.

[0364] Systems, devices, and methods for detecting, measuring, and classifying an individual's diet based on analyte measurements. These results and related information can be presented to the individual to show the individual which diets cause the most severe analyte responses. These results can be organized and classified based on preselected criteria or previous diets and results to organize and present the results in a format with reference glucose as the monitored analyte. The various embodiments disclosed herein relate to methods, systems, and software applications for managing an individual by providing direct and timely feedback regarding the individual's diet-related glucose response.

[0365] It should be noted that all features, elements, components, functions, and steps described with respect to any embodiment provided herein are intended to be freely combinable and replaceable with those from any other embodiment. If a certain feature, element, component, function, or step is described only with respect to one embodiment, it should be understood that, unless otherwise explicitly stated, that feature, element, component, function, or step can be used with every other embodiment described herein. Thus, this paragraph serves as a preamble basis and written support for introducing claims at any time that combine the features, elements, components, functions, and steps of different embodiments, or replace those of one embodiment with the features, elements, components, functions, and steps of another embodiment, even if the following description does not explicitly state so, but in certain circumstances, such combinations or replacements are possible. It is explicitly recognized that formulating every possible combination and replacement would be overly cumbersome, especially considering that the permissibility of each such combination and replacement would be readily recognized by a person of ordinary skill in the art.

[0366] If the embodiments disclosed herein include a memory, a storage device, and / or a computer-readable medium or operate in association therewith, then the memory, the storage device, and / or the computer-readable medium are non-transitory. Thus, if the memory, the storage device, and / or the computer-readable medium are covered by one or more claims, then the memory, the storage device, and / or the computer-readable medium are only non-transitory.

[0367] In many instances, entities are described herein as being coupled to other entities. It should be understood that the terms "coupled" and "connected" (or any form thereof) are used interchangeably herein, and in both cases, they apply to both direct coupling of two entities (without any non-negligible (e.g., parasitic) intervening entity) and indirect coupling of two entities (with one or more non-negligible intervening entities). When entities are shown as being directly coupled together or are described as being coupled together without describing any intervening entity, it should be understood that these entities may also be indirectly coupled together unless the context clearly dictates otherwise.

[0368] As used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0369] The publications discussed herein are provided solely for disclosure prior to the filing date of the present application. Nothing herein is to be construed as an admission that the present disclosure is not entitled to antedate such disclosure by virtue of prior disclosure. Further, the provided publication dates may be different from the actual publication dates, which may require independent verification.

[0370] Although the embodiments are susceptible to various modifications and alternative forms, specific examples thereof have been shown in the drawings and are described in detail herein. These embodiments are not limited to the specific forms disclosed, but rather, these embodiments will cover all modifications, equivalents, and alternatives falling within the spirit of the present disclosure. Additionally, any feature, function, step, or element of an embodiment can be recited in a claim or added to a claim, as well as in a negative limitation that defines the scope of a claim by a feature, function, step, or element not within that scope.

[0371] The disclosure of the present application also includes systems, devices, and methods for detecting and measuring the amount of time an individual spends within a predetermined analyte range based on analyte measurements. These results and related information are presented to the individual to show the analyte response associated with the consumed meal or the change in analyte levels within a predetermined time period after the meal is consumed. These results can be organized based on a rating system to allow the individual to visualize the analyte response and range impact associated with the meal. Various embodiments disclosed herein relate to methods, systems, and software applications for managing an individual by providing direct and timely feedback on the individual's meal-related analyte response.

[0372] The disclosure of the present application also includes the following numbered clauses:

[0373] 1. A glucose monitoring system, comprising:

[0374] A reader device, comprising:

[0375] A wireless communication circuit configured to receive data indicating glucose levels from a sensor control device;

[0376] An input configured to receive meal information indicating one or more meals consumed by a user; and

[0377] One or more processors coupled to a memory storing a meal monitoring application, which, when executed by the one or

[0378] more processors:

[0379] Determine a score for each of one or more meal events, where the score corresponds to a glucose response based on the data indicating glucose levels associated with each of the one or more meal events,

[0380] Output a home page graphical user interface (GUI) that includes at least one of the following:

[0381] A glucose curve card including a glucose curve having a glucose trend line that reflects the data indicating glucose levels;

[0382] A logbook section having a list including meal information, where the list is configured to display the one or more meal events and the corresponding scores associated with each of the one or more meal events;

[0383] An average meal rating card configured to display an average meal rating, where

[0384] The average meal rating is based on the average of a plurality of, optionally all, scores in the one or more meal events over a predetermined period of time.

[0385] 2. The glucose monitoring system according to clause 1, wherein the sensor control device is configured to collect data indicative of the glucose level in the user's body, the sensor control device includes a glucose sensor, and at least a portion of the glucose sensor is configured to be in fluid contact with the user's body fluid.

[0386] 3. The glucose monitoring system according to clause 1 or 2, wherein the score is a first assigned value, and the first assigned value corresponds to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events.

[0387] 4. The glucose monitoring system according to clause 3, wherein the data indicative of the glucose level is the change in the glucose level within a predefined period of time after the user consumes each of the one or more meals.

[0388] 5. The glucose monitoring system according to clause 3 or 4, wherein a higher first assigned value corresponds to each of the one or more meals associated with a lower glucose response.

[0389] 6. The glucose monitoring system according to any one of clauses 3 to 5, wherein a lower first assigned value corresponds to each of the one or more meals associated with a higher glucose response.

[0390] 7. The glucose monitoring system according to any one of clauses 3 to 6, wherein the first assigned value can be any number between one and five.

[0391] 8. The glucose monitoring system according to any one of clauses 3 to 7, wherein the logbook section displays one or more asterisk icons, and each of the one or more asterisk icons includes a score associated with each of the one or more meal events.

[0392] 9. The glucose monitoring system according to any of the preceding clauses, wherein the average meal rating is a second assigned value, and the second assigned value corresponds to the average of a plurality of, optionally all, scores in the one or more meal events over a predetermined period of time.

[0393] 10. The glucose monitoring system according to clause 9, wherein the second assigned value can be any number between one and five.

[0394] 11. The glucose monitoring system according to clause 9 or 10, wherein the second assigned value can include one or more decimal values.

[0395] 12. The glucose monitoring system according to any one of clauses 9 to 11, wherein a higher second allocation value corresponds to a lower average glucose response.

[0396] 13. The glucose monitoring system according to any one of clauses 9 to 12, wherein a lower second allocation value corresponds to a higher average glucose response.

[0397] 14. The glucose monitoring system according to any of the preceding clauses, wherein the average dietary rating card is further configured to display a graphical indication corresponding to the average dietary rating.

[0398] 15. The glucose monitoring system according to clause 14, wherein the graphical indication includes an average dietary rating indicator, and the average dietary rating indicator is configured to visually map the average dietary rating provided within a predetermined time period.

[0399] 16. The glucose monitoring system according to clause 14 or 15, wherein the graphical indication is a plurality of asterisks including a colored portion, and the ratio of each of the plurality of asterisks including the colored portion to the total plurality of asterisks is proportional to the ratio of the average dietary rating to the maximum available dietary rating.

[0400] 17. The glucose monitoring system according to clause 16, wherein the graphical indication is configured to display at least one of the plurality of asterisks with a semi-colored portion when the average dietary rating is not an integer.

[0401] 18. The glucose monitoring system according to any of the preceding clauses, wherein the average dietary rating is provided only after the user receives a first score associated with one of the one or more dietary events.

[0402] 19. The glucose monitoring system according to any of the preceding clauses, wherein the average dietary rating is configured to be continuously updated to account for each of the one or more dietary events being scored.

[0403] 20. The glucose monitoring system according to any of the preceding clauses, wherein the home page GUI further includes a bulletin card with a message that indicates to the user that the first score is available after the first of the one or more dietary events is scored within a predetermined time period.

[0404] 21. The glucose monitoring system according to any of the preceding clauses, wherein the average dietary rating is not displayed if none of the one or more dietary events are scored within a predetermined time period.

[0405] 22. The glucose monitoring system according to any of the preceding clauses, wherein when none of the one or more dietary events are scored, a graphical indication including a plurality of asterisks is displayed on the average dietary rating card, and none of the plurality of asterisks includes a colored portion.

[0406] 23. The glucose monitoring system according to any of the preceding clauses, wherein the average dietary rating card is directly adjacent to and proximal to the glucose curve card.

[0407] 24. The glucose monitoring system according to any of the preceding clauses, wherein the glucose curve card is configured to reflect the postprandial glucose trajectory associated with each of the one or more dietary events.

[0408] 25. The glucose monitoring system according to any of the preceding clauses, wherein the glucose curve includes an x-axis and a y-axis, the x-axis includes units of time, and the y-axis includes units of measurement associated with data indicating glucose levels.

[0409] 26. The glucose monitoring system according to any of the preceding clauses, wherein the home page GUI further includes one or more selectable icons configured to allow a user to select a predefined amount of time within which data of the user's indicated glucose levels will be shown on the glucose curve card.

[0410] 27. The glucose monitoring system according to clause 26, wherein the one or more selectable icons are configured to allow the user to select a predefined amount of time of four hours, twelve hours, or twenty-four hours.

[0411] 28. The glucose monitoring system according to any of the preceding clauses, wherein the home page GUI further includes an insights icon, wherein the insights icon is selectable, and when the dietary monitoring application is executed by the one or more processors, the one or more processors are further caused to:

[0412] In response to selecting the insights icon, output an insights GUI configured to provide user information related to the user's progress with respect to a certain criterion.

[0413] 29. The glucose monitoring system according to clause 28, wherein the criterion is an average dietary rating criterion.

[0414] 30. A glucose monitoring system, comprising:

[0415] A reader device, comprising:

[0416] A wireless communication circuit configured to receive data indicating glucose levels from a sensor control device;

[0417] An input, configured to receive dietary information indicative of one or more meals consumed by a user; and

[0418] One or more processors, coupled to a memory that stores a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to:

[0419] Determine a user's progress based on dietary information and data indicative of glucose levels, based on criteria related to the dietary information and data indicative of glucose levels over a predefined time period, and

[0420] Output an insights graphical user interface (GUI) that includes at least one of the following:

[0421] An insights section, including one or more insights cards, where each of the one or more insights cards includes statistical data related to the user's progress; and

[0422] A meals section, including a list of dietary information, where the list is configured to display one or more meal events, and each of the one or more meal events displayed on the list is configured to reflect data indicative of a glucose response associated with each of the one or more meals.

[0423] 31. The glucose monitoring system according to clause 30, wherein the sensor control device is configured to collect data indicative of the glucose level in the user's body, the sensor control device includes a glucose sensor, and at least a portion of the glucose sensor is configured to be in fluid contact with the user's body fluid.

[0424] 32. The glucose monitoring system according to clause 30 or 31, wherein the criteria are related to an average meal rating, where the average meal rating corresponds to the average of one or more scores for the one or more meal events, and each of the one or more scores corresponds to a glucose response based on data indicative of the glucose level associated with each of the one or more meal events.

[0425] 33. The glucose monitoring system according to clause 32, wherein the one or more insights cards include a first insights card, and the first insights card is configured to display statistical data related to the day with the highest average meal rating received by the user over a predefined time period.

[0426] 34. The glucose monitoring system according to clause 33, wherein the predefined time period is a one-week period.

[0427] 35. The glucose monitoring system according to clause 33 or 34, wherein the first insight card includes a summary message with statistical data related to the day on which the user received the highest average meal rating within a predefined time period.

[0428] 36. The glucose monitoring system according to any one of clauses 33 to 35, wherein the first day insight card is configured to be displayed on the insight GUI after a predefined time period has elapsed.

[0429] 37. The glucose monitoring system according to any one of clauses 33 to 36, wherein the insight GUI is configured to update and display a second insight card at a predefined frequency, and wherein the second insight card is configured to replace the first insight card on the insight GUI.

[0430] 38. The glucose monitoring system according to clause 37, wherein the predefined frequency is once every seven days.

[0431] 39. The glucose monitoring system according to any one of clauses 30 to 38, wherein the insight GUI further includes an insight icon, and wherein the insight icon is configured to provide an animation when a new insight card is available.

[0432] 40. The glucose monitoring system according to clause 39, wherein the animation includes the insight icon changing color to indicate that a new insight card is available.

[0433] 41. The glucose monitoring system according to any one of clauses 33 to 40, wherein the first insight card includes an insight time indicator configured to indicate the amount of time elapsed since the first insight card was displayed on the insight GUI.

[0434] 42. The glucose monitoring system according to any one of clauses 33 to 41, wherein the first insight card includes a label configured to indicate to the user that the first insight card has been newly added to the insight GUI.

[0435] 43. The glucose monitoring system according to clause 42, wherein the label is configured to be automatically removed from the first insight card after a predetermined time period has elapsed.

[0436] 44. The glucose monitoring system according to clause 43, wherein the predetermined time period is 24 hours.

[0437] 45. The glucose monitoring system according to any one of clauses 30 to 44, wherein the insight GUI further includes a selectable past insights link, and wherein the reader device further includes a touch screen, and wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to:

[0438] In response to selecting the past insights link, output a past insights GUI that includes an insights log having one or more historical insights cards.

[0439] 46. The glucose monitoring system according to clause 45, wherein the insights log is configured to display the one or more historical insights cards in chronological order.

[0440] 47. The glucose monitoring system according to clause 46, wherein the most recent one of the one or more historical insights cards is configured to be displayed at the top portion of the insights log.

[0441] 48. The glucose monitoring system according to any one of clauses 45 to 47, wherein the insights log is divided into one or more sub - sections, wherein each of the one or more sub - sections represents a different time period, and wherein each of the one or more sub - sections includes one or more historical insights cards corresponding to the respective time period represented by each of the one or more sub - sections.

[0442] 49. The glucose monitoring system according to any one of clauses 45 to 48, wherein each of the one or more historical insights cards is configured to display statistical data related to a day within a past predefined time period during which the user received the highest average meal rating.

[0443] 50. The glucose monitoring system according to any one of clauses 45 to 49, wherein the insights log is configured to be scrollable and / or dynamic.

[0444] 51. The glucose monitoring system according to any one of clauses 45 to 50, wherein the one or more historical insights cards are selectable, wherein the reader device further includes a touch screen, and wherein when the meal monitoring application is executed by the one or more processors, it further causes the one or more processors to:

[0445] In response to selecting one of the one or more historical insights cards, output an interface including information related to the statistical data related to the user's progress represented by the selected one of the one or more historical insights cards.

[0446] 52. The glucose monitoring system according to any one of clauses 30 to 51, wherein each of the one or more meal events includes a score, wherein the score is an assigned numerical value corresponding to data indicative of the glucose response associated with each of the one or more meal events.

[0447] 53. The glucose monitoring system according to clause 52, wherein a higher allocation value corresponds to each of the one or more meals associated with a lower glucose response, and wherein a lower allocation value corresponds to each of the one or more meals associated with a higher glucose response.

[0448] 54. The glucose monitoring system according to clause 53, wherein the meal section is configured to display one or more meal events associated with the one or more meals corresponding to the highest allocation value.

[0449] 55. The glucose monitoring system according to clause 54, wherein the meal section is configured to list the one or more meal events in descending order of the allocation values.

[0450] 56. The glucose monitoring system according to clause 54 or 55, wherein the meal section is configured to list a predefined number of one or more meal events associated with the one or more meals corresponding to the highest allocation value.

[0451] 57. The glucose monitoring system according to any one of clauses 52 to 56, wherein the allocation value can be any number between one and five.

[0452] 58. The glucose monitoring system according to any one of clauses 30 to 57, wherein each of the one or more meal events displayed in the meal section includes a textual description of the meal, a photograph associated with the meal, and / or a score, wherein the score is the allocation value that corresponds to data indicating the glucose response associated with each of the one or more meal events.

[0453] 59. The glucose monitoring system according to clause 58, wherein each of the one or more meal events displayed in the meal section further includes a meal label associated with the meal, wherein the meal label can include keywords specifying or describing the ingredients and / or characteristics of the meal.

[0454] 60. The glucose monitoring system according to any one of clauses 30 to 59, wherein each of the one or more meal events displayed in the meal section is selectable, wherein the reader device further includes a touch screen, and wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to:

[0455] In response to selecting one of the one or more meal events, output a meal review GUI that is configured to provide details related to the selected one of the one or more meal events.

[0456] 61. The glucose monitoring system according to any one of clauses 30 to 60, wherein the Insights GUI further includes an optional All Meals link, wherein the reader device further includes a touch screen, and wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to:

[0457] In response to selection of the All Meals link, output a Meal GUI that includes information related to all of the one or more meal events entered during a predefined time period.

[0458] 62. A device, comprising:

[0459] means for receiving data indicative of a glucose level from a sensor control device;

[0460] means for receiving meal information indicative of one or more meals consumed by a user;

[0461] means for determining a score for each of the one or more meal events, wherein the score corresponds to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; and

[0462] means for outputting a home page graphical user interface (GUI) that includes at least one of the following:

[0463] A glucose curve card, including a glucose curve having a glucose trend line that reflects the data indicative of the glucose level;

[0464] A logbook section having a list that includes meal information, wherein the list is configured to display the one or more meal events and the corresponding scores associated with each of the one or more meal events;

[0465] An average meal rating card configured to display an average meal rating, wherein the average meal rating is based on an average of scores of a plurality of optionally all of the one or more meal events during a predefined time period.

[0466] 63. A device, comprising:

[0467] means for receiving data indicative of a glucose level from a sensor control device;

[0468] means for receiving meal information indicative of one or more meals consumed by a user;

[0469] means for determining a user's progress based on meal information and the data indicative of the glucose level based on criteria related to the meal information and the data indicative of the glucose level during a predefined time period; and

[0470] A device for outputting a home page graphical user interface (GUI), the home page GUI including at least one of the following:

[0471] An insights section including one or more insights cards, where each of the one or more insights cards includes statistical data related to the user's progress; and

[0472] A meals section including a list of meal information, where the list is configured to display one or more meal events, and each of the one or more meal events displayed on the list is configured to reflect data indicating a glucose response associated with each of the one or...

Claims

1. A glucose monitoring system, comprising: A reader device, comprising: A wireless communication circuit configured to receive data indicating a glucose level from a sensor control device; An input configured to receive dietary information indicating one or more meals consumed by a user; and One or more processors coupled to a memory that stores a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to: Determine a score for each of one or more dietary events, wherein the score corresponds to a glucose response based on the data indicating the glucose level associated with each of the one or more dietary events, Output a home page graphical user interface (GUI) that includes at least one of the following: A glucose curve card, including a glucose curve having a glucose trend line that reflects the data indicating the glucose level; A logbook section having a list that includes the dietary information, wherein the list is configured to display the one or more dietary events and the corresponding scores associated with each of the one or more dietary events; An average meal rating card configured to display an average meal rating, wherein the average meal rating is based on an average of scores of a plurality of optionally all of the one or more dietary events within a predetermined time period.

2. The glucose monitoring system according to claim 1, wherein, The sensor control device is configured to collect the data indicating the glucose level in the user's body, the sensor control device includes a glucose sensor, wherein at least a portion of the glucose sensor is configured to be in fluid contact with the user's body fluid.

3. The glucose monitoring system according to claim 1, wherein, The score is a first assigned value that corresponds to the glucose response based on the data indicating the glucose level associated with each of the one or more dietary events.

4. The glucose monitoring system according to claim 3, wherein, The data indicating the glucose level is a change in glucose level within a predefined time period after the user consumes each of the one or more meals.

5. The glucose monitoring system according to claim 3, wherein, A higher first assigned value corresponds to each of the one or more meals associated with a lower glucose response.

6. The glucose monitoring system according to claim 3, wherein, A lower first assigned value corresponds to each of the one or more meals associated with a higher glucose response.

7. The glucose monitoring system according to claim 3, wherein, The first assigned value can be any number between one and five.

8. The glucose monitoring system according to claim 3, wherein, The logbook section displays one or more star icons, wherein each of the one or more star icons includes a score associated with each of the one or more dietary events.

9. The glucose monitoring system according to claim 1, wherein, the average meal rating is a second assigned value, and the second assigned value corresponds to the average of a plurality of, optionally all, scores in the one or more meal events within the predetermined time period.

10. The glucose monitoring system according to claim 9, wherein, the second assigned value can include one or more decimal values.

11. The glucose monitoring system according to claim 9, wherein, a higher second assigned value corresponds to a lower average glucose response.

12. The glucose monitoring system according to claim 9, wherein, a lower second assigned value corresponds to a higher average glucose response.

13. The glucose monitoring system according to claim 1, wherein, the average meal rating card is further configured to display a graphical indication corresponding to the average meal rating.

14. The glucose monitoring system according to claim 13, wherein, the graphical indication includes an average meal rating indicator, and the average meal rating indicator is configured to visually represent the average meal rating provided within the predetermined time period.

15. The glucose monitoring system according to claim 1, wherein, the average meal rating is provided only after the user receives a first score associated with one of the one or more meal events.

16. The glucose monitoring system according to claim 1, wherein, the average meal rating is configured to be continuously updated to account for each of the one or more meal events being scored.

17. The glucose monitoring system according to claim 1, wherein, the home page graphical user interface further includes a bulletin card with a message, and the message indicates to the user that the first score is available after the first of the one or more meal events is scored within the predetermined time period.

18. The glucose monitoring system according to claim 1, wherein, if none of the one or more meal events is scored within the predetermined time period, the average meal rating is not displayed.

19. The glucose monitoring system according to claim 1, wherein, the glucose curve card is configured to reflect the post-meal glucose trajectory associated with each of the one or more meal events.

20. The glucose monitoring system according to claim 1, wherein, the glucose curve includes an x-axis and a y-axis, the x-axis includes time units, and the y-axis includes measurement units associated with the data indicating the glucose level.

21. The glucose monitoring system according to claim 1, wherein, the home page graphical user interface further includes one or more selectable icons, and the one or more selectable icons are configured to allow the user to select a predefined amount of time within which the data indicating the glucose level of the user will be shown on the glucose curve card.

22. The glucose monitoring system according to claim 21, wherein, The one or more selectable icons are configured to allow the user to select the predefined amount of time of four hours, twelve hours, or twenty-four hours.

23. The glucose monitoring system according to claim 1, wherein, the home graphical user interface further includes an insights icon, wherein the insights icon is selectable, and wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: in response to selecting the insights icon, output an insights graphical user interface configured to provide the user information related to the user's progress regarding a certain criterion.

24. The glucose monitoring system according to claim 23, wherein, the criterion is an average dietary rating criterion.

25. A glucose monitoring system, comprising: a reader device, comprising: a wireless communication circuit configured to receive data indicating a glucose level from a sensor control device; an input configured to receive dietary information indicating one or more meals consumed by the user; and one or more processors coupled to a memory that stores a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to: determine the user's progress based on the dietary information and the data indicating the glucose level, based on a criterion related to the dietary information and the data indicating the glucose level within a predefined time period, and output an insights graphical user interface (GUI) that includes at least one of the following: an insights section including one or more insights cards, wherein, each of the one or more insights cards includes statistical data related to the user's progress; and a dietary section including a list of the dietary information, wherein, the list is configured to display one or more meal events, and each of the one or more meal events displayed on the list is configured to reflect data indicating a glucose response associated with each of the one or more meals.

26. The glucose monitoring system according to claim 25, wherein, the criterion is related to an average dietary rating, wherein the average dietary rating corresponds to an average of one or more scores of the one or more meal events, and each of the one or more scores corresponds to a glucose response based on the data indicating the glucose level associated with each of the one or more meal events.

27. The glucose monitoring system according to claim 25, wherein, one of the one or more insights cards includes a summary message with statistical data related to the day within the predefined time period when the user received the highest average dietary rating.

28. The glucose monitoring system according to claim 25, wherein, Each of the one or more dietary events includes a score, where the score is an assigned numerical value corresponding to the data indicative of the glucose response associated with each of the one or more dietary events.

29. The glucose monitoring system according to claim 28, wherein a higher assigned numerical value corresponds to each of the one or more meals associated with a lower glucose response, and wherein a lower assigned numerical value corresponds to each of the one or more meals associated with a higher glucose response.

30. A device, comprising: means for receiving data indicative of a glucose level from a sensor control device; means for receiving dietary information indicative of one or more meals consumed by a user; means for determining a score for each of the one or more dietary events, where the score corresponds to a glucose response based on the data indicative of the glucose level associated with each of the one or more dietary events; and means for outputting a home page graphical user interface (GUI) that includes at least one of the following: A glucose curve card, including a glucose curve having a glucose trend line that reflects the data indicative of the glucose level; A logbook section having a list that includes the dietary information, where the list is configured to display the one or more dietary events and the corresponding scores associated with each of the one or more dietary events; An average meal rating card configured to display an average meal rating, where the average meal rating is based on an average of the scores of a plurality or optionally all of the one or more dietary events within a predetermined time period.

31. A device, comprising: means for receiving data indicative of a glucose level from a sensor control device; means for receiving dietary information indicative of one or more meals consumed by a user; means for determining the progress of the user based on the dietary information and the data indicative of the glucose level according to criteria related to the dietary information and the data indicative of the glucose level within a predefined time period; and means for outputting a home page graphical user interface (GUI) that includes at least one of the following: An insights section including one or more insights cards, where each of the one or more insights cards includes statistical data related to the progress of the user; and A meals section including a list of the dietary information, where the list is configured to display one or more dietary events, and each of the one or more dietary events displayed on the list is configured to reflect data indicative of the glucose response associated with each of the one or more meals.

32. A method, comprising the steps of: Receiving dietary information input by a user; Receiving data indicative of glucose levels within a predetermined amount of time; Identifying peak glucose level values; Determining an initial glucose level value; Determining a glucose level offset value; Associating the input dietary information with the glucose level offset value; and is a dietary distribution score associated with the input dietary information.

33. A method, comprising the steps of: receiving, from a user, a predetermined input on a toggle switch adjacent to a text description on an interface, wherein the text description indicates the current day of the week; selecting, by the user, a particular one of a plurality of rings displayed in response to the user toggling the switch, wherein each of the plurality of rings is a TIR indicator corresponding to a different day in the past week; determining, by at least one processor, based on data stored in a database, a data set indicating the glucose level and dietary information associated with the day corresponding to the selected ring; and providing, to a display device, an interactive reporting graphical user interface (GUI) configured to display, based on the determination, the data set indicating the glucose level and the dietary information, wherein the reporting graphical user interface is configured to display one or more of the following: a TIR card, a glucose curve card reflecting data indicating the glucose level during a time period corresponding to the selected ring, and / or a dietary list reflecting dietary information for a time period corresponding to the selected ring.

34. A method, comprising the steps of: determining a start of an offset; determining an end of the offset; calculating a trigger window between the start of the offset and the end of the offset; determining a threshold lowest glucose level value; determining a threshold highest glucose level value; and determining a threshold time window.

35. A computer program, computer program product, or computer-readable medium comprising software code that, when executed by a computer system, is adapted to perform the method according to any one of claims 32 to 34.

36. A glucose monitoring system, comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating a glucose level from a sensor control device; an input configured to receive dietary information indicating one or more meals consumed by a user; and one or more processors coupled to a memory storing a dietary monitoring application that, when executed by the one or more processors, causes the one or more processors to: detect a first episode in the data indicating the glucose level, wherein the first episode is associated with a first meal consumed by the user and wherein the input has not yet received dietary information related to the consumed first meal associated with the first episode; output a home page graphical user interface (GUI) comprising at least one of the following: a glucose curve card comprising a glucose curve having a glucose trend line that reflects the data indicating the glucose level; and a logbook section having a list comprising the dietary information; wherein, in response to detecting the first episode, a first notification associated with the first episode is displayed to the home page graphical user interface, and Further in response to detecting the first episode, a first episode marker associated with the detected first episode is displayed on the glucose profile card.

37. The glucose monitoring system according to claim 36, wherein, when executed by the one or more processors, the dietary monitoring application further causes the one or more processors to: determine a score for each of the one or more dietary events, wherein the score corresponds to a glucose response based on the data indicative of the glucose level associated with each of the one or more dietary events.

38. The glucose monitoring system according to claim 37, wherein, the home page graphical user interface further includes an average dietary rating card configured to display an average dietary rating, wherein the average dietary rating is based on an average of the scores of a plurality, optionally all, of the one or more dietary events within a predetermined time period.

39. The glucose monitoring system according to claim 36, wherein, the first notification is located between the glucose profile card and the logbook section of the home page graphical user interface.

40. The glucose monitoring system according to claim 36, wherein, the first notification includes a query asking the user questions related to the first meal consumed.

41. The glucose monitoring system according to claim 36, wherein, the first notification includes a message providing the user with information related to the first episode and the data indicative of the glucose level.

42. The glucose monitoring system according to claim 36, wherein, the first notification includes a selectable meal record button, wherein the reader device further includes a touch screen, and wherein, when executed by the one or more processors, the dietary monitoring application further causes the one or more processors to: output a meal record graphical user interface in response to the user selecting the selectable meal record button.

43. The glucose monitoring system according to claim 36, wherein, the first notification includes a selectable meal record button, wherein the reader device further includes a touch screen, and wherein, when executed by the one or more processors, the dietary monitoring application further causes the one or more processors to: output a meal entry modal in response to the user selecting the selectable meal record button, wherein the meal entry modal includes a time field pre-filled with the date and time associated with the detected first episode.

44. The glucose monitoring system according to claim 36, wherein, in response to the user recording the first meal consumed associated with the detected first episode, when executed by the one or more processors, the dietary monitoring application further causes the one or more processors to: remove the first notification from the home page graphical user interface.

45. The glucose monitoring system according to claim 36, wherein, In response to the user recording the first meal consumed in association with the detected first episode, when the meal monitoring application is executed by the one or more processors, the one or more processors are further caused to: Remove the first notification from the home page graphical user interface; and Replace the first episode marker with a meal icon.

46. The glucose monitoring system according to claim 36, wherein, In response to the user recording the first meal consumed in association with the detected first episode, when the meal monitoring application is executed by the one or more processors, the one or more processors are further caused to: Remove the first notification from the home page graphical user interface; Replace the first episode marker with a meal icon; and Display an entry in the logbook section for the first meal consumed in association with the detected first episode.

47. The glucose monitoring system according to claim 36, wherein, The first episode marker is displayed on the glucose trend line.

48. The glucose monitoring system according to claim 36, wherein, When the meal monitoring application is executed by the one or more processors, the one or more processors are further caused to: After a predetermined period of time, delete the first notification and the first episode marker from the home page graphical user interface.

49. The glucose monitoring system according to claim 48, wherein, The predetermined period of time is 24 hours.

50. The glucose monitoring system according to claim 36, wherein, When the meal monitoring application is executed by the one or more processors, the one or more processors are further caused to: Detect a second episode in the data indicating the glucose level, where the second episode is associated with a second meal consumed by the user, and where the input has not yet received meal information related to the first meal consumed in association with the first episode; In response to detecting the second episode, display a second notification associated with the second episode on the home page graphical user interface; and Further in response to detecting the second episode, display a second episode marker associated with the detected second episode on the glucose curve card.

51. The glucose monitoring system according to claim 50, wherein, The first notification and the second notification are stacked on the home page graphical user interface.

52. The glucose monitoring system according to claim 51, wherein, The first notification and the second notification are stacked in chronological order.

53. The glucose monitoring system according to claim 50, wherein, The first notification includes a first page number, and wherein the second notification includes a second page number.

54. The glucose monitoring system according to claim 50, wherein, The second notification includes a selectable meal ignore button, where the reader device further includes a touch screen, and where when the meal monitoring application is executed by the one or more processors, the one or more processors are further caused to: In response to the user selecting the ignore button, remove the second notification from the home page graphical user interface and display only the first notification.

55. A glucose monitoring system, comprising: a wireless communication circuit configured to receive data indicative of a glucose level from a sensor control device; and one or more processors coupled to a memory storing a dietary monitoring application, which, when executed by the one or more processors, causes the one or more processors to: determine a score for each of one or more dietary events, wherein the score corresponds to a glucose response based on the data indicative of the glucose level associated with each of the one or more dietary events, output a home page graphical user interface (GUI) that includes at least one of the following: a glucose curve card; a logbook section having a list configured to display the one or more dietary events and corresponding scores associated with each of the one or more dietary events; an average dietary rating card configured to display information associated with at least one of the one or more dietary events within a predetermined time period.

56. A glucose monitoring system, comprising: a wireless communication circuit configured to receive data indicative of a glucose level from a sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by a user; and one or more processors coupled to a memory storing a dietary monitoring application, which, when executed by the one or more processors, causes the one or more processors to: determine the user's progress based on the dietary information and the data indicative of the glucose level according to criteria related to the dietary information and the data indicative of the glucose level within a predefined time period, and output an insights graphical user interface (GUI) that includes at least one of the following: an insights section including statistical data related to the user's progress based on the criteria; and a dietary section including a list of the dietary information, wherein the list is configured to reflect data indicative of a glucose response associated with each of the one or more meals consumed by the user.

57. A glucose monitoring system, comprising: a wireless communication circuit configured to receive data indicative of a glucose level from a sensor control device; one or more processors coupled to a memory storing a dietary monitoring application, which, when executed by the one or more processors, causes the one or more processors to: detect a first episode in the data indicative of the glucose level, wherein the first episode is associated with a first meal consumed by the user, and wherein the dietary monitoring application has not received dietary information related to the first meal consumed associated with the first episode; output a graphical user interface (GUI) that includes at least one of the following: a glucose curve card; and A logbook section having a list including the dietary information; wherein, in response to detecting the first episode, a first notification associated with the first episode is displayed to the graphical user interface, and wherein, further in response to detecting the first episode, a first episode marker associated with the detected first episode is displayed on the glucose curve card.

58. A glucose monitoring system, comprising: A reader device, comprising: A wireless communication circuit configured to receive data indicating a glucose level from a sensor control device; An input configured to receive dietary information; and One or more processors coupled to a memory storing a first dietary monitoring application, which when executed by the one or more processors, causes the one or more processors to: Determine the amount of time that the data indicating the glucose level is within a predetermined glucose range, Output a home page graphical user interface (GUI) that includes at least one of the following: A within-range time card including graphical elements indicating the amount of time that the data indicating the glucose level is within the predetermined glucose range; and A list including the dietary information, wherein the list is configured to display one or more dietary events, each of the one or more dietary events including a score, wherein the score is based on a glucose response associated with the meal and the data indicating the glucose level.

59. A glucose monitoring system, comprising: A reader device, comprising: A wireless communication circuit configured to receive data indicating a glucose level from a sensor control device; An input configured to receive dietary information; and One or more processors coupled to a memory storing a dietary monitoring application, which when executed by the one or more processors, causes the one or more processors to: Identify a peak glucose level value; Determine an initial glucose level value, Determine a glucose level offset value based on the peak glucose level value and the initial glucose level value, Associate the dietary information with the glucose level offset value, assign a score to the meal based on the associated dietary information and the glucose level offset value, and Output to a display a home page graphical user interface (GUI) including a list that includes the dietary information, wherein the list includes the meal and the assigned score.

60. The glucose monitoring system according to claim 60, wherein, when executed by the one or more processors, the dietary monitoring application further causes the one or more processors to: Adjust the glucose level offset value based on a function of the initial glucose level value.

61. The glucose monitoring system according to claim 61, wherein, the function of the initial glucose level value is a linear function.

62. The glucose monitoring system according to claim 62, wherein, The linear function includes a first variable and a second variable, wherein the first variable is multiplied by the initial glucose level value, and wherein the second variable is added to the product of the first variable and the initial glucose level value.

63. The glucose monitoring system according to claim 63, wherein, each of the first variable and the second variable is a weighted average based on multiple instances of the same meal.

64. The glucose monitoring system according to claim 61, wherein, the function of the initial glucose level value is a logical function.

65. The glucose monitoring system according to claim 61, wherein, when the meal monitoring application is executed by the one or more processors, it further causes the one or more processors to: perform one or more data validity checks before adjusting the glucose level offset value.

66. The glucose monitoring system according to claim 66, wherein, the one or more data validity checks include a first data validity check to determine whether data indicating a predetermined minimum amount of the glucose level associated with the glucose offset is available.

67. The glucose monitoring system according to claim 67, wherein, the one or more data validity checks include a second data validity check to determine whether the offset period before the meal label includes pre-meal data indicating a predetermined minimum amount of the glucose level.

68. A device, comprising: means for receiving data indicating the glucose level from a sensor control device; means for receiving meal information indicating one or more meals consumed by the user; means for detecting a first episode in the data indicating the glucose level, wherein the first episode is associated with a first meal consumed by the user, and wherein the input has not yet received meal information related to the first meal consumed associated with the first episode; means for outputting a home page graphical user interface (GUI) that includes at least one of the following: a glucose curve card, including a glucose curve having a glucose trend line that reflects the data indicating the glucose level, and a logbook section having a list including the meal information; means for displaying a first notification associated with the first episode on the home page graphical user interface in response to detecting the first episode; and means for displaying a first episode marker associated with the detected first episode on the glucose curve card in response to detecting the first episode.

69. A device, comprising: means for receiving data indicating the glucose level from a sensor control device; means for determining a score for each of one or more meal events, wherein the score corresponds to a glucose response based on the data indicating the glucose level associated with each of the one or more meal events; and means for outputting a home page graphical user interface (GUI) that includes at least one of the following: a glucose curve card; A logbook section having a list configured to display the one or more meal events and corresponding scores associated with each of the one or more meal events; An average meal rating card configured to display information associated with at least one of the one or more meal events within a predetermined time period.

70. A device, comprising: means for receiving data indicative of a glucose level from a sensor control device; means for receiving meal information indicative of one or more meals consumed by a user; means for determining the progress of the user based on criteria related to the meal information and the data indicative of the glucose level over a predefined time period; and means for outputting an insights graphical user interface (GUI) comprising at least one of the following: An insights section including statistical data related to the progress of the user based on the criteria; and A meal section including a list of the meal information, wherein the list is configured to reflect data indicative of a glucose response associated with each of the one or more meals consumed by the user.

71. A device, comprising: means for receiving data indicative of a glucose level from a sensor control device; means for detecting a first episode in the data indicative of the glucose level, wherein the first episode is associated with a first meal consumed by the user, and wherein the meal monitoring application has not received meal information related to the first meal consumed associated with the first episode; means for outputting a graphical user interface (GUI) comprising at least one of the following: A glucose curve card; and A logbook section having a list including the meal information; means for displaying a first notification associated with the first episode to the graphical user interface in response to detecting the first episode, and means for further displaying a first episode marker associated with the detected first episode on the glucose curve card in response to detecting the first episode.

72. A device, comprising: means for receiving data indicative of a glucose level from a sensor control device; means for receiving meal information; means for determining the amount of time the data indicative of the glucose level is within a predetermined glucose range; and means for outputting a home page graphical user interface (GUI) comprising at least one of the following: A within-range time card including a graphical element indicative of the amount of time the data indicative of the glucose level is within the predetermined glucose range; and A list including the meal information, wherein the list is configured to display one or more meal events, and wherein each of the one or more meal events includes a score based on a glucose response associated with the meal and the data indicative of the glucose level.

73. A device, comprising: A device for receiving data indicative of a glucose level from a sensor control device; A device for receiving dietary information indicative of one or more meals consumed by a user; And A device for determining a post-meal glucose trajectory associated with each of the one or more meals based on the dietary information and the data indicative of the glucose level, and A device for outputting a glucose curve graphical user interface (GUI) that includes at least one of the following: A glucose curve card that includes a glucose curve having a glucose trend line configured to reflect the data indicative of the glucose level, wherein the glucose trend line is further configured to reflect the post-meal glucose trajectory associated with each of the one or more meals, and A list of the dietary information, wherein the list is configured to display one or more meal events, and each of the one or more meal events displayed on the list is configured to reflect data indicative of a glucose response associated with each of the one or more meals.

74. An apparatus, Comprising: A device for receiving data indicative of a glucose level from a sensor control device; A device for receiving dietary information; A device for identifying a peak glucose level value; A device for determining an initial glucose level value; A device for determining a glucose level offset value based on the peak glucose level value and the initial glucose level value; A device for associating the dietary information with the glucose level offset value; A device for assigning a score to a meal based on the associated dietary information and the glucose level offset value; And A device for outputting to a display a home page graphical user interface (GUI) that includes a list, the list including the dietary information, wherein the list includes the meal and the assigned score.

75. A method, Comprising the steps of: Receiving data indicative of a glucose level from a sensor control device; Receiving dietary information; Identifying a peak glucose level value; Determining an initial glucose level value; Determining a glucose level offset value based on the peak glucose level value and the initial glucose level value; Associating the dietary information with the glucose level offset value; Assigning a score to a meal based on the associated dietary information and the glucose level offset value; And Outputting to a display a home page graphical user interface (GUI) that includes a list, the list including the dietary information, wherein the list includes the meal and the assigned score.

Images