Systems, devices, and methods for monitoring TIR and diet-related analytes

Abstract

Systems, devices, and methods for detecting and measuring the length of time an individual's analyte levels have been within a predetermined range based on analyte measurements. Presenting these results and related information to the individual reveals to the individual the analyte response associated with the intake of a meal, i.e., the change in analyte level within a predetermined time period after the intake of the meal. These results can also be organized in a ranking format to allow the individual to visualize the analyte response and impact on TIR associated with the meal. Various embodiments disclosed herein relate to methods, systems, and software applications designed to engage individuals by providing timely, direct feedback regarding their diet-related analyte response.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Patent Application No. 63 / 535,134, filed August 29, 2023, and U.S. Patent Application No. 63 / 416,750, filed October 17, 2022, the entire disclosures of which are expressly incorporated herein by reference for all purposes. [Technical Field]

[0002] The subject matter described herein relates generally to computing interfaces for analyte monitoring systems and related systems, methods, and devices. Specifically, this specification discloses various embodiments of time-in-range (TIR) ​​and meal-related graphical user interfaces for analyte monitoring systems. [Background technology]

[0003] The increasing prevalence of type 2 diabetes and metabolic syndrome over the past few decades is thought to be due to changes in dietary habits and physical activity levels. For example, the consumption of relatively readily available foods with a high glycemic index (GI) can cause a rapid rise in blood glucose and insulin levels after meals, which has been shown to be positively correlated with weight gain and obesity. Furthermore, it has been shown that weight gain and obesity can increase the risk of developing diseases such as type 2 diabetes and metabolic syndrome.

[0004] Most people understand the importance of healthy eating in general terms. However, many struggle to translate this general understanding into specific food choices. This difficulty stems primarily from an inability to directly see the impact of their choices. This lack of visibility can lead to misconceptions about portion sizes, misperceptions about which foods are relatively healthy, and a general lack of awareness about the duration and intensity of activity needed to stay healthy. Furthermore, advertising, habit, peer pressure, food preferences, and general advice further exacerbate these problems.

[0005] These challenges can be addressed by using analyte monitoring systems to track and better understand an individual's physiological responses. Furthermore, because elevated glucose levels are primarily caused by food ingestion, postprandial glucose levels can be correlated with the amount of carbohydrates and other dietary components consumed by an individual and their physiological response to the meal. However, analyzing this large volume of incoming data has been challenging due to the difficulty of representing the data in a meaningful format that allows for effective action. Nevertheless, understanding and mitigating glucose excursions, including hyperglycemic excursions, requires data on dietary choices and their effects from a clinical perspective as well as from the individual, dietary planner, and healthcare professional perspectives.

[0006] It has been established that individuals who maintain analyte levels within target ranges are more likely to experience good health outcomes. Therefore, it would be beneficial to provide individuals with easy-to-use, actionable information regarding the length of time their analyte levels have remained within target ranges, information regarding the impact of their diet on their analyte levels, and tools to motivate and empower individuals to make healthier food choices.

[0007] While systems that track food intake and associate meals with individual test substance data have existed for some time, these systems have faced many challenges. For example, some systems require individuals to repeatedly and individually perform laborious and uncomfortable blood glucose measurements, such as finger-prick blood glucose tests. However, these methods can sometimes result in insufficient data points to accurately assess glycemic responses to meals. For example, if individual blood glucose measurements are performed before or after the user's peak glycemic response, it becomes difficult to accurately assess the glycemic response and meaningfully compare meals based on the glycemic response. Furthermore, insufficient data points also make it difficult to detect meal events from the user's test substance data. As a result, some conventional systems rely heavily on the user's manual food logging. Furthermore, while some conventional systems attempt to detect meal events solely based on the presence or absence of elevated glucose levels, many of these systems do not take into account the user's past eating history, potentially overcounting the number of meals the user actually consumed, making them inappropriate. Summary of the Invention [Problem to be solved by the invention]

[0008] Therefore, there is a need for improved systems, devices, and methods for collecting dietary information, assessing and detecting diets, and correlating the same with analyte levels. In particular, there is a need for robust, user-friendly graphical user interfaces for analyte monitoring systems, and related systems, methods, and devices, that enable individuals to correlate and understand the effects of their dietary intake on analyte response and analyte range. [Means for solving the problem]

[0009] Aspects of the invention are recited in independent claims, with preferred features recited in dependent claims. Features associated with one aspect may be applied to other aspects alone or in combination with other features. Provided herein are exemplary embodiments of systems, devices, and methods for detecting and measuring the length of time an individual's analyte levels have been within a predetermined range based on analyte measurements. Also provided herein are exemplary embodiments of systems, devices, and methods for detecting, measuring, and ranking an individual's diet in relation to the individual's analyte measurements. In many embodiments, these results and related information are presented to the individual to enable the individual to understand the analyte response associated with the meal, i.e., the change in analyte levels within a predetermined time period after ingestion of the meal. Target individuals include those who exhibit symptoms of diabetes, those diagnosed with symptoms of diabetes, those considered pre-diabetic, those with metabolic syndrome, and even those without symptoms of diabetes, pre-diabetes, or metabolic syndrome. Target individuals can be anyone who is motivated to improve their health by modifying their diet and activity habits. Information obtained by systems, devices, and methods according to exemplary embodiments of the present disclosure can indicate to an individual which meals, or aspects of their diet, are putting the greatest strain on their analyte levels.

[0010] In many embodiments, an individual's meal-related analyte response (e.g., meal-related glucose response) is derived based on analyte data (e.g., glucose data) collected by an analyte monitoring system (e.g., a glucose monitoring system), such as an in vivo analyte monitoring system (e.g., an in vivo glucose monitoring system). By comparing or linking such meal-related analyte responses with dietary information, common patterns (or anomalies) in the meal-related analyte responses can be identified and, further, trends in the meal-related analyte responses can be identified based on associated historical glucose readings, associated algorithms, and the comparison results.

[0011] Many embodiments disclosed herein are intended to engage individuals by providing direct, timely feedback regarding their diet-related analyte response, which in some embodiments can be presented to the individual in an easy-to-understand format to reveal the burden of dietary intake.

[0012] Many embodiments can quickly provide individuals with useful information, thereby encouraging them to take action to better understand how their diet affects their body's analyte responses. Many embodiments can also organize data, such as ranking meals according to the change in an individual's analyte levels detected within a given time period after ingestion. By comparing and contrasting current and past analyte data, individuals can understand how their efforts are connected to making better dietary habits and dietary choices and how those choices directly impact their health. Furthermore, individuals can gain a better understanding of how specific food choices help maintain analyte levels within target ranges and can visually confirm analyte responses and their impact on analyte ranges in relation to specific foods. This can motivate individuals to maintain analyte levels within target ranges.

[0013] Many of the embodiments provided herein provide improved graphical user interfaces (GUIs) or GUI features for analyte monitoring systems that are highly intuitive and user-friendly, allowing individuals to quickly access physiological information. More specifically, these embodiments provide a variety of user interfaces that quickly present a user with various physiological conditions and possible responses, and that can correlate analyte data with factors such as diet, exercise, and stress, without requiring the user (or HCP) to laboriously navigate through large amounts of analyte data, allowing individuals to easily navigate within and between these various user interfaces.

[0014] In many embodiments, several GUIs and GUI features enable individuals (and their caregivers) to better understand their diet, eating habits, and stressor management, and to take action to improve these by learning how these actions correlate with glucose levels. Similarly, many embodiments provide improvements to the digital interfaces and / or features for TIR and diet-related systems. These improvements include, for example, visualization of the impact of food choices on analyte (glucose) levels and the length of time analyte levels remain in target ranges, visualization of "good" and "bad" foods in an individual's current diet and their impact on glucose levels and TIR, association of detected meal events with dietary information, and motivating individuals to maintain or improve their TIR by presenting food options that can be consumed while maintaining TIR goals. These are just a few examples, and other improvements and advantages are also provided. Various configurations of these devices are described in more detail below with reference to exemplary embodiments, which are provided for illustrative purposes only.

[0015] The GUI improvements described in various aspects of the detailed description and claims herein provide at least the technical effect of assisting users of the device in operating the device more accurately, efficiently, and safely. It will be appreciated that the information provided to an individual on the GUI, the order in which that information is presented, and the clarity of the information's organization can significantly impact how the individual interacts with and operates the system. Thus, the GUI guides an individual performing the technical task of operating the system to accurately and efficiently read the required readings and obtain the required information.

[0016] Other systems, devices, methods, features, and advantages of the subject matter described herein will be apparent to one of ordinary skill in the art or will become apparent upon examination of the following figures and detailed description. It is intended that all such additional systems, devices, methods, features, and advantages be included herein, be within the scope of the subject matter described herein, and be protected by the accompanying claims. Features of the example embodiments should not be construed as limiting the scope of the appended claims, unless expressly recited in the claims. [Brief explanation of the drawings]

[0017] Details of the subject matter described herein, both in terms of its structure and operation, will become apparent from a review of the accompanying drawings, in which like parts are designated by like reference numerals. The drawings are not necessarily drawn to scale, with emphasis instead being placed upon illustrating the principles of the subject matter. Furthermore, the drawings are intended to convey concepts, and detailed attributes such as relative size and shape may be shown diagrammatically and not accurately. [Figure 1] 1 is a system diagram of an analyte monitoring system including a sensor applicator, a sensor control device, a reading device, a network, a trusted computer system, and a local computer system. [Figure 2A] 1 is a block diagram illustrating an exemplary embodiment of a reading device; [Figure 2B] 1 is a block diagram illustrating an exemplary embodiment of a sensor control device; [Figure 2C] 1 is a block diagram illustrating an exemplary embodiment of a sensor control device; [Figure 3] A block diagram illustrating an exemplary embodiment of an analyte monitoring system for use in an analyte monitoring application, a dietary monitoring application, or both. [Figure 4A-1] FIG. 1 is a flow diagram illustrating an exemplary embodiment of a method for associating test substance data with dietary information and ranking the dietary information. [Figure 4A-2] Graph showing postprandial glucose trajectory [Figure 4A-3] Graph showing postprandial glucose trajectory [Figure 4A-4] FIG. 1 is a flow diagram illustrating an exemplary embodiment of a method for associating test substance data with dietary information and ranking the dietary information. [Figure 4A-5] FIG. 1 is a flow diagram illustrating an example embodiment of a method for displaying an interface containing information about time-in-range (TIR). [Figure 4B] Block diagram illustrating an exemplary embodiment of a Home GUI [Figure 4C] FIG. 1 is a block diagram illustrating an exemplary embodiment of a time-in-range (TIR) ​​information screen. [Figure 4D] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-1] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-2] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-3] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-4]1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-5] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-6] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4E-7] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4F] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4G] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4H] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4I] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4J-1] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4J-2] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4J-3] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4K-1] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4K-2] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4K-3] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4L] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-1] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-2] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-3] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-4] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-5] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4M-6] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 4N] 1 is a block diagram illustrating an exemplary embodiment of a home GUI, modal displays, and their associated functionality. [Figure 5A] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5B] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5C] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5D] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5E] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5F] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5G] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5H] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5I] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5J] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5K] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5L] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5M] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 5N] FIG. 1 is a block diagram illustrating an example embodiment of a meal logging GUI and modal display. [Figure 6A] 1 is a flow diagram illustrating an exemplary embodiment of a method for displaying a report GUI. [Figure 6B-1] 1 is a block diagram illustrating an example embodiment of a report GUI. [Figure 6B-2] 1 is a block diagram illustrating an example embodiment of a report GUI. [Figure 7] FIG. 1 is a block diagram illustrating an exemplary embodiment of a meal load GUI. [Figure 8] 1 is a block diagram illustrating an exemplary embodiment of a meal review GUI. [Figure 9A] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9B] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9C] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9D] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9E] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9F] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9G] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9H] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9I] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9J] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9K] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9L] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9M] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9N] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9O] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 9P] 1 is a block diagram illustrating an exemplary embodiment of an onboarding GUI and its associated functionality; [Figure 10A] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10B] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10C-1] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10C-2] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10D] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10E-1] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10E-2]FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10E-3] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10F] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10G] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10H-1] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10H-2] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10H-3] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10H-4] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10H-5] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10I] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10J] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10K] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10L] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 10M] FIG. 1 is a block diagram illustrating an example embodiment of an Account GUI and a Settings GUI and their associated functions. [Figure 11A] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11B]A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11C] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11D] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11E] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11F] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 11G] A block diagram illustrating an exemplary embodiment of a data loss GUI and its functionality. [Figure 12A-1] FIG. 1 is a block diagram illustrating an exemplary embodiment of an interface including activity cards and associated functionality. [Figure 12A-2] FIG. 1 is a block diagram illustrating an exemplary embodiment of an interface including activity cards and associated functionality. [Figure 12A-3] FIG. 1 is a block diagram illustrating an exemplary embodiment of an interface including activity cards and associated functionality. [Figure 12A-4] FIG. 1 is a block diagram illustrating an exemplary embodiment of an interface including activity cards and associated functionality. [Figure 12B] FIG. 1 is a block diagram illustrating an exemplary embodiment of an interface including activity cards and associated functionality. [Figure 13] 1 is a flow diagram illustrating an exemplary embodiment of a meal detection method; [Figure 13A-1] 1 is a block diagram illustrating an exemplary embodiment of a meal detection interface and its functionality. [Figure 13A-2] 1 is a block diagram illustrating an exemplary embodiment of a meal detection interface and its functionality. [Figure 13B-1] 1 is a block diagram illustrating an exemplary embodiment of a meal detection interface and its functionality. [Figure 13B-2] 1 is a block diagram illustrating an exemplary embodiment of a meal detection interface and its functionality. [Figure 14A-1]1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14A-2] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14A-3] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14A-4] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14A-5] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14B-1] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14B-2] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14B-3] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14C] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14D-1] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14D-2] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14D-3] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; [Figure 14E] 1 is a block diagram illustrating an exemplary embodiment of an analysis results interface and its functionality; DETAILED DESCRIPTION OF THE INVENTION

[0018] Provided herein are exemplary embodiments of systems, devices, and methods for monitoring and measuring an individual's analyte response to a diet. Specifically, based on the collected analyte data, a user can gain a better understanding of diet-related events and their impact on an individual's analyte levels, which can then be used to modify future dietary choices and habits.

[0019] Before describing the present subject matter in more detail, it would be helpful to describe exemplary embodiments of systems, devices, and methods in which the present subject matter may be implemented.

[0020] Numerous systems have been developed to automatically monitor analytes, such as glucose, in bodily fluids, such as blood flow, interstitial fluid ("ISF"), dermal fluid in the dermis, etc. Some of these systems are configured to obtain information about at least one analyte in the body by placing a sensor at least partially below the surface of the user's skin (e.g., within the user's blood vessels or subcutaneous tissue).

[0021] Such systems are sometimes referred to as "in vivo" monitoring systems. In vivo analyte monitoring systems include "Continuous Analyte Monitoring" systems (or "Continuous Glucose Monitoring" systems). Continuous analyte monitoring systems are systems that can transmit data from a sensor-controlling device to a reading device continuously (e.g., automatically according to a schedule) rather than prompting. In vivo analyte monitoring systems also include "Flash Analyte Monitoring" systems (or "Flash Glucose Monitoring" systems, or simply "Flash" systems). Flash analyte monitoring systems are systems that can transmit data from a sensor-controlling device in response to a data scan or data request by a reading device, for example, using a Near Field Communication (NFC) protocol or a Radio Frequency Identification (RFID) protocol. In vivo analyte monitoring systems can operate without the need for finger-prick calibration.

[0022] In vivo analyte monitoring systems are distinguishable from "in vitro" systems, which contact a biological sample outside the body (or, more precisely, "ex vivo"). In vitro systems typically include a metering device with a port that receives an analyte test strip containing a user's bodily fluid, and can analyze the test strip to determine the user's blood glucose level. While many of the present embodiments perform monitoring in vivo, the embodiments disclosed herein may be used with in vivo analyte monitoring systems that incorporate in vitro capabilities, or with entirely in vitro or ex vivo analyte monitoring systems.

[0023] The sensor may be part of a sensor control device, which is a device placed on the user's body and contains the electronics and power source responsible for implementing and controlling analyte sensing. Note that sensor control devices and variations thereof may also be referred to as "sensor control units," "on-body electronics" devices or units, "on-body" devices or units, and "sensor data communication" devices or units, as just a few examples of alternative names for sensor control devices.

[0024] In-vivo monitoring systems may also include devices that receive analyte sensor data from the sensor control device and process and / or display the analyte sensor data to a user in any number of forms. Such devices and variations thereof may be referred to as "reader devices" (or simply "readers"), "handheld electronics" (or handhelds), "portable data processing" devices or units, "data receivers," "receiver" devices or units (or simply receivers), or "remote" devices or units, to name just a few. In-vivo and in-vitro monitoring systems have also been used with or incorporated into other devices, such as personal computers.

[0025] In Vivo Analyte Monitoring System Embodiments FIG. 1 is a conceptual diagram illustrating an exemplary embodiment of an analyte monitoring system 100 (e.g., a glucose monitoring system) including a sensor applicator 150, a sensor control device 102, and a reading device 120. In this example, the sensor applicator 150 can be used to deliver the sensor control device 102 to a monitoring location on a user's skin. Once the sensor control device 102 is delivered to the monitoring location, an adhesive patch 105 maintains the sensor 104 in place for a period of time. As further illustrated in FIGS. 2B and 2C , the sensor control device 102 can communicate with the reading device 120 via a communication path 140 using wired or wireless technology. Examples of wireless protocols include Bluetooth, Bluetooth Low Energy (BLE, BTLE, Bluetooth SMART, etc.), and near-field communication (NFC). A user can use a screen 122 (which in many embodiments can be a touchscreen) and an input 121 to view and use applications installed in the memory of the reading device 120. Additionally, the device battery of the reading device 120 can be charged using a power port 123. Although only one reading device 120 is shown in the figure, the sensor control device 102 can communicate with multiple reading devices 120. The reading devices 120 can communicate with each other to share data. The reading devices 120 are described in more detail below in the description of FIG. 2A . The reading device 120 can communicate with a local computer system 170 over a communication path 141 using a wired or wireless communication protocol. The local computer system 170 can include one or more computing devices such as a laptop, a desktop computer, a tablet, a phablet (a combination device of a phone and a tablet), a smartphone, a set-top box, a video game console, etc.For wireless communication, many wireless network protocols are available, such as Bluetooth, Bluetooth Low Energy (BTLE), and Wi-Fi, and any of these wireless network protocols can be used. Using wired or wireless communication protocols, the local computer system 170 can communicate with the network 190 via communication path 143. Similarly, the reading device 120 can communicate with the network 190 via communication path 142. The network 190 can be any of a number of networks, including private networks, public networks, local area networks, and wide area networks. The trusted computer system 180 can include a server and provide authentication services and secure data storage. The trusted computer system 180 can also communicate with the network 190 via communication path 144 using wired or wireless technology.

[0026] Exemplary embodiments of a reading device 2A is a block diagram illustrating an exemplary embodiment of a reading device 120. In some embodiments, the reading device 120 may comprise a smartphone. In this example, the reading device 120 may include a display 122, an input component 121, and a processing core 206, which may include a communications processor 222 coupled to memory 223 and an application processor 224 coupled to memory 225. The reading device 120 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. The reading device 120 may also include a multi-function transceiver 232 capable of communicating with the antenna 234 via WiFi, NFC, Bluetooth, BTLE, and GPS. As will be appreciated by those skilled in the art, these components are electrically and communicatively coupled to form a functional device.

[0027] Exemplary Embodiments of a Sensor Control Device 2B and 2C are block diagrams illustrating an exemplary embodiment of a sensor control device 102 having an analyte sensor 104 and sensor electronics 160 (including analyte monitoring circuitry). The sensor electronics 160 provides the majority of the processing power for rendering the final result data in a form suitable for display to a user. While FIG. 2B shows a single semiconductor chip 161, the semiconductor chip 161 can be a custom application-specific integrated circuit (ASIC). Within the ASIC 161 are several higher-level functional units, including an analog front-end (AFE) 162, a power management (control) circuit 164, a processor 166, and a communications circuit 168 (which can be implemented as a transmitter, receiver, transceiver, passive circuitry, etc., depending on the communications protocol). While this embodiment utilizes both the AFE 162 and processor 166 as analyte monitoring circuitry, in other embodiments, either circuitry can perform the analyte monitoring function. Processor 166 may comprise one or more processors, microprocessors, controllers, and / or microcontrollers, each of which may be a separate chip or may be distributed across several different chips (and portions thereof).

[0028] Also included within the ASIC 161 is a memory 163. The memory 163 may be shared among the various functional units present within the ASIC 161 or may be distributed among two or more of these functional units. The memory 163 may be a separate chip. The memory 163 may be volatile and / or non-volatile memory. In this embodiment, the ASIC 161 is coupled to a power source 172, which may be a coin cell battery or the like. The AFE 162 interfaces with the in-vivo analyte sensor 104 to receive measurement data from the sensor 104 and outputs such data in digital form to a processor 166. The processor 166 then processes the data to determine final results, such as discrete glucose values ​​and trend values. The data may then be provided to a communications circuit 168 and transmitted via an antenna 171 to a reading device 120 (not shown). There, the data may be displayed on the reading device 120 with minimal further processing by, for example, a resident software application.

[0029] FIG. 2C is similar to FIG. 2B, except that it includes two different semiconductor chips 162, 174. The semiconductor chips 162, 174 can be packaged together or individually. In this example, the AFE 162 is located in the ASIC 161. The processor 166 is integrated with the power management circuit 164 and the communication circuit 168 on chip 174. The AFE 162 includes memory 163, and the chip 174 includes memory 165. The memory may be separate or may be integrated as distributed memory. In one exemplary embodiment, the AFE 162 is combined with the power management circuit 164 and the processor 166 on one chip, and the communication circuit 168 is on a separate chip. In another exemplary embodiment, the AFE 162 and the communication circuit 168 are on one chip, and the processor 166 and the power management circuit 164 are on a separate chip. Other chip organizations are also possible, such as three or more chips, each capable of independently performing the functions described herein, or with one or more functions shared between chips for fail-safe redundancy.

[0030] Exemplary Embodiment of a Time In Range (TIR) ​​Software Application In many embodiments, the subject matter described herein is implemented by a software application program stored in memory of and executed by a processor-based device. Such processor-based devices may include, for example, a reading device (e.g., a smartphone), a medication delivery device, a trusted computer system, a local computer system, or any one of the other computing devices described herein. In certain embodiments, the software is implemented as one or more software applications (“apps”) downloadable to a reading device such as a mobile communication device or a smartphone. In certain embodiments, the software and its associated features and functionality may be implemented in a single centralized device or, alternatively, may be distributed across multiple separate devices at geographically dispersed locations. Similarly, those skilled in the art will recognize that the representations of various computer systems in the embodiments disclosed herein, such as those shown in FIG. 1, are intended to encompass both physical and virtual computing devices (e.g., virtual servers or virtual machines).

[0031] Generally, the software may provide a mechanism for a user to conveniently specify a consumable item (e.g., a type of food or a type of drink, or a quantity thereof). In this specification, such consumable items are broadly referred to as "meals," and the term "meal" is used broadly to refer to all types of food and drink.

[0032] According to one aspect of many embodiments, the software can perform many functions related to collecting dietary information and correlating the collected dietary information with analyte information, which may be collected using in-vivo analyte sensors 104, in-vitro test strips and meters, or trusted computer system 180. Hereinafter, the software will generally be referred to as the "Time-in-Range application," "TIR application," or "meal monitoring application."

[0033] According to another aspect of many embodiments, the TIR application can be used by diabetic patients, such as those with type 2 diabetes who are taking basal insulin, or those with type 1 or type 2 diabetes who are on frequent insulin therapy and who are deeply motivated to change their diet. The TIR application can also be used by pre-diabetic and non-diabetic individuals who wish to minimize glucose fluctuations by controlling their diet. Users of the TIR application also include individuals who desire to control their currently uncontrolled diabetes but who believe they cannot adhere to a prescribed "diabetes diet" long-term because they are reluctant to give up their favorite foods. Users of the TIR application can also include individuals who are in control of their diabetes but whose usual diet is no longer working due to new medications, a revised exercise plan, pregnancy, or other life changes.

[0034] In the TIR application, information about each meal an individual consumes (i.e., each "meal event") can be logged by the individual, and the TIR application can associate test substance data for the meal period represented by the user's log entry.

[0035] In some embodiments, the TIR application categorizes food choices according to glycemic response (or other analyte response). The TIR application can also be used in conjunction with the analyte monitoring system 100 to provide a deeper understanding of how diet affects glucose levels. The TIR application can associate measured analyte responses with meal events and store the results in non-transitory memory or a database. Specifically, the TIR application can display each meal and its associated analyte response (e.g., glucose response) to the user, for example, sorting each meal in descending order (e.g., for glucose, descending order of magnitude of glycemic response). The user can directly visualize how food choices and portion sizes affect glucose levels. The user can see which foods contribute the highest levels of stress. The TIR application can also help dispel myths about healthy eating (e.g., that high-carbohydrate foods, such as orange juice and breakfast cereals, are foods to avoid but are sometimes mistakenly perceived as healthy).

[0036] In many embodiments, the TIR application can help a user determine how to modify their diet to achieve better glucose control and increase the time their glucose levels remain within a target range by allowing the user to visually identify the "good" and "bad" foods (or "good eating behaviors" and "bad eating behaviors") in their current diet. The TIR application can assist the user by visualizing glucose response data and the TIR load associated with various food choices. The TIR application can also provide an easy-to-understand score for each logged meal according to the change in the user's glucose level detected within a predetermined time period (e.g., three hours) after the meal. In some embodiments, for example, meals that produce a smaller glycemic response may be assigned a higher score. Conversely, meals that produce a larger glycemic response may be assigned a lower score. In this manner, a high score assigned to a certain meal indicates to the user that the food choices were likely effective in maintaining the user's analyte levels within the target range. In some embodiments, the TIR application can also incorporate a gamification element into TIR management, motivating the user to improve their TIR index by selecting beneficial foods.

[0037] The TIR application can assess the glucose load of meals (and other events) by using and evaluating the length of time a user's values ​​remain within a target range. For example, the TIR application can assess the length of time a user's values ​​remain within a target range (e.g., the time their glucose values ​​remain within a target glucose range of about 70 mg / dL to about 180 mg / dL), i.e., TIR. In some embodiments, the target range can be set by the user. For example, the target range can be set to a range of about 80 mg / dL to about 170 mg / dL. The lower limit of the target range can be at least about 65 mg / dL, e.g., about 70 mg / dL or about 80 mg / dL. The upper limit of the target range can be no greater than about 180 mg / dL, e.g., about 170 mg / dL or about 120 mg / dL. The TIR application can also automatically adjust the target (without user intervention) in stages if the user achieves their current target (goal) after a predetermined period of time. For example, if a user consistently meets (e.g., over the past week) a goal of 30% for the time their glucose readings are in the target range, the TIR application may set a new goal of 35% for the time their analyte level readings are in the target range. Similarly, if a user consistently fails to meet a goal of 30% for the time their glucose readings are in the target range, the TIR application may set a new goal of 25% for the time their analyte level readings are in the target range. However, one skilled in the art will recognize that goal ranges other than those above and described herein may be utilized and that the above values ​​are not intended to be limiting.

[0038] The TIR can be calculated as a percentage of the time that the analyte level was within the target range divided by the total time. For example, if glucose was within the TIR threshold for 6 hours out of a 24-hour period, the TIR index would be 25%. The TIR index can also be expressed in hours (h) rather than as a percentage, in which case the TIR in the above example would be 6 hours (out of a total time = 24 hours).

[0039] In many embodiments, a user of a TIR application is a user who is able to continuously monitor their glucose levels, such as using a sensor control device 102 of system 100. As shown in FIG. 3, transmission of analyte levels can occur (i) from sensor 104 to analyte monitoring application 310; (ii) from analyte monitoring application 310 to a cloud comprised of server 320; or (iii) from server 320 to TIR application 330. In some embodiments, cloud 320 can comprise one or more servers with the same or different functionality. For example, analyte data can be uploaded to a first server or servers responsible for collecting analyte data, and then downloaded to the Time In Range (TIR) ​​application by a second server or servers responsible for downloading data for use by the TIR application. Additionally, those skilled in the art will appreciate that the test substance monitoring application 310 and the TIR application 330 can reside on a single device (e.g., a single smartphone), or alternatively, can reside on two different devices (e.g., two smartphones, or a smartphone and a dedicated receiver).

[0040] Further details regarding the functionality and interfaces of Time In Range (TIR) ​​software applications that may be implemented and utilized in conjunction with the embodiments described herein are described in U.S. Patent Application Publication Nos. 2017 / 0128007, 2021 / 0030323, and 2022 / 0000399, the disclosures of all of which are incorporated herein by reference for any purpose.

[0041] Illustrative embodiments of the GUIs of the Time In Range (TIR) ​​application and their associated functions. Exemplary embodiments of various GUIs and associated software functionality for the TIR application are described below. Those skilled in the art will appreciate that these various interfaces can be displayed on any of the embodiments of the reading device 120 (e.g., a smartphone), medication delivery device, trusted computer system 180, and 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 individual devices at geographically dispersed locations. Those skilled in the art will appreciate that any one or more of the exemplary embodiments of the methods, interfaces, and systems described herein can be implemented independently or in combination with any of the other embodiments described herein. Furthermore, while many of the embodiments described herein relate to glucose monitoring, those skilled in the art will appreciate that these same embodiments can also be implemented to monitor other analytes (e.g., lactate or ketones). Those skilled in the art will also appreciate that, although the embodiments described herein can monitor one analyte at a time, the embodiments described herein are not limited thereto.

[0042] Exemplary Embodiments of Home GUI and Related Methods Next, an exemplary embodiment of a method for associating test substance data with dietary information will be described. It should be noted at the outset that those skilled in the art will recognize that the method steps described herein may be implemented as software instructions stored in memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of system 100, and thus, when executed by one or more processors of the computing device, the instructions may cause the one or more processors to perform any or all of the method steps described herein. Referring now to FIG. 4A-1 , a flow diagram illustrating an exemplary embodiment of a method 4000 for associating test substance data with dietary information is shown. This method 4000 is a method in which dietary information has already been entered by a user. As shown at the top of FIG. 4A-1 , method 4000 begins with step 4001, in which a user inputs dietary information. In some embodiments, step 4001 may be a step in which a user proactively inputs a dietary entry or dietary log entry before being prompted by a TIR application, for example. In other embodiments, the user may input dietary information in response to a prompt displayed by the TIR application. For example, according to some embodiments, the TIR application can be configured to display a reminder notification to the user if no meal entries have been entered after a predetermined reminder notification period (e.g., if no meal entries have been entered in the past week, if no meal entries have been entered in the past three days, if no meal entries have been entered in the past day, etc.).

[0043] Next, in step 4002, the TIR application receives data indicative of the user's analyte level within a predetermined amount of time. In some embodiments, step 4002 may include the user scanning the sensor control device within a predetermined amount of time from entering the meal entry (e.g., within 3 hours of entering the meal entry, within 4 hours of entering the meal entry, within 8 hours of entering the meal entry, within 12 hours of entering the meal entry, etc.). In other embodiments, step 4002 may be performed autonomously if the sensor control device is configured to autonomously wirelessly transmit the analyte data to a reading device.

[0044] Continuing with reference to FIG. 4A-1 , in step 4003, analyte peak values ​​in the analyte data may be identified. In some embodiments, step 4003 may include identifying a highest glucose value above 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 analyte peak value is updated to be the newly identified highest glucose value. The analyte peak value may also be a glucose value that exceeds the predetermined analyte level threshold during a time frame after the meal entry is entered (e.g., a 1-hour time frame after the meal entry is entered, a 2-hour time frame after the meal entry is entered, a 3-hour time frame after the meal entry is entered, or a 4-hour time frame after the meal entry is entered). In some embodiments, the analyte peak value may also be a glucose value that exceeds the predetermined analyte level threshold prior to the time of the meal entry (e.g., 3 hours before the meal entry is entered). If the peak value of the test substance is identified at a time prior to the time of the meal entry, the post-meal period may be ended early to allow the user to receive a score (described below) without waiting for the entire time frame (e.g., the entire 3-hour time frame) after the peak value of the test substance is identified.

[0045] According to one aspect of the embodiment, if the percent difference (%) between the analyte peak value and the most recent analyte value is below a predetermined threshold, analyte peak detection is discontinued. In some embodiments, analyte peak detection is discontinued after a predetermined amount of time (e.g., 3 hours) has elapsed since the meal entry was entered.

[0046] Then, in the next step 4004, the initial analyte level is identified. According to some embodiments, the initial analyte level may be identified by checking the analyte level at or near the time of the meal entry (e.g., within 15 minutes either before or after the meal entry).

[0047] In some embodiments, the range of past analyte data is defined as a postprandial period, which is the period from the time of the initial analyte level (e.g., 15 minutes before or after the input of a meal entry, 30 minutes before or after the input of a meal entry, or 1 hour before or after the input of a meal entry) to the end of the peak analyte level (e.g., 2 hours after the input of a meal entry, 3 hours after the input of a meal entry, or 4 hours after the input of a meal entry). In some embodiments, the end of the postprandial period can be the earlier of (1) the time of the first analyte reading (e.g., glucose reading) within 3 hours of the time of the initial analyte level or (2) the time of the last analyte reading (e.g., glucose reading) before the input of a new meal entry.

[0048] In some embodiments, a subsequent step 4005 determines an analyte level fluctuation value, for example, by subtracting the initial analyte level value from the peak analyte level value. Then, in a next step 4006, the analyte level fluctuation value may be associated with the user-entered meal entry and stored in memory with the meal entry. Then, in a next step 4007, a score is assigned to the particular meal associated with the entered meal information based on the analyte level fluctuation value. In some embodiments, a score for a particular meal may only be assigned after the post-meal period has ended. In some embodiments, a score for one or more meal events is calculated for each meal event based on a glucose response based on data indicating glucose levels associated with each meal event.

[0049] In some embodiments, meals are not scored if certain threshold conditions are met. The first threshold condition can be, for example, a minimum number of analyte readings in the post-meal period (e.g., fewer than eight glucose readings), no analyte peak detected within a predetermined time frame (e.g., a three-hour time frame) from the time of the meal entry, or both. Furthermore, in some embodiments, a second threshold condition can be a post-meal period that is less than a predetermined time (e.g., two hours). In some embodiments, if a new meal entry is made within a predetermined time period of the previous meal entry (e.g., within three hours of the current meal entry in the log), no analyte peak is detected and the meal is not scored. Furthermore, in some embodiments, if a new meal entry is made before an analyte peak is detected, the new meal may not be scored.

[0050] According to some embodiments, step 4007 of assigning or calculating a meal score can further take into account certain physiological conditions the user had prior to consuming the meal. More specifically, some diabetic patients may have high initial analyte levels (e.g., initial glucose levels) before consuming a meal. For example, some type 2 diabetic patients still have the ability to produce insulin to metabolize glucose, but these individuals often exhibit high pre-meal glucose levels. In such cases, endogenous insulin is released before consuming a meal, which may affect the response to the meal and reduce the analyte level fluctuation (sometimes referred to as "PeakDelta"). To illustrate this, Figures 4A-2 and 4A-3 show post-meal glucose trajectories 4100 and 4150, respectively, for an individual consuming the same meal at different times. The second graph 4150 in Figure 4A-3 shows that when the initial analyte level (sometimes referred to as the pre-meal glucose level) is about 150 mg / dL, the PeakDelta value is about 100 mg / dL. On the other hand, the first graph 4100 in Figure 4A-2 shows that when the pre-meal glucose level is about 180 mg / dL, the PeakDelta value is about 70 mg / dL after the same meal. Therefore, if the pre-meal glucose level is high, the person's PeakDelta value (i.e., the analyte level fluctuation value) is likely to be lower.

[0051] According to some embodiments, adjustments can be made to the PeakDelta value to account for higher initial analyte levels in a particular user. For example, adjustments to the PeakDelta value can be made according to the following formula: PeakDeltaAdj = PeakDelta + f(G premeal ) (1)

[0052] As described above, PeakDelta is the variation in the analyte level, i.e., the difference between the peak analyte level after a meal and the initial analyte level. PeakDeltaAdj is the adjusted variation in the analyte level (hereinafter referred to as the "adjusted variation in the analyte level"). G premeal is the initial test substance level. In some embodiments, G premeal is the glucose level at a timestamp prior to the meal tag timestamp. premeal is the minimum glucose level within a given duration (e.g., 1 hour, 90 minutes, 2 hours, 3 hours, etc.) prior to the meal tag's timestamp.

[0053] Furthermore, according to some embodiments, f(G premeal ) can be expressed by the following linear function: f(G premeal ) = a * G premeal + b (2)

[0054] The variables a and b can be constants determined based on simulations of a hypothetical group of type 2 diabetes patients consuming various diets with varying carbohydrate, fat, and protein contents. In other embodiments, the variables a and b can be constants determined from in vivo data. However, one skilled in the art will appreciate that the variables a and b can be determined in other ways using one or more of simulation data, in vivo data, population data, and other test data. The first variable a is G premeal and the second variable b is G premeal and b. In some embodiments, for example, a=0.4 and b=−50 mg / dL.

[0055] According to some embodiments, when data on multiple meal instances with different intake dates for the same meal (or the same type of meal) are available, the adjusted analyte level fluctuation value PeakDeltaAdj can be calculated using a weighted average of variables a and b. Specifically, first, the G premeal Value and G peak Additionally, in some embodiments, the G values ​​of multiple feeding instances of the same meal can be correlated. premeal Value and G peak The values ​​can be categorized by meal time (e.g., breakfast, lunch, dinner). For meals with more than one eating instance, the estimated value a of variable a for each meal is est , the estimated value b of variable b est Then, the parameter a est , b est A weighted average calculation of each parameter can be performed for the meals associated with a meal, where the more instances a meal has, the more weights are used in the weighted average for that meal. A PeakDeltaAdj value can then be determined based on the most recent weighted average parameters for a particular user.

[0056] However, one of ordinary skill in the art will recognize that other variables and constants may be used in the formulas described herein without departing from the scope of the present disclosure.

[0057] According to another embodiment, when PeakDelta is small, G premeal A logistic function may also be utilized to minimize the effect of ( ), thereby reducing the likelihood of assigning an inappropriate score to a small meal with very small analyte level fluctuations. An exemplary embodiment of the logistic function is shown below: k = 1 / (1 + e -.5*(d-5) ) (3) PeakDeltaAdj = k(a * G premal + d - b) +(1 - k)d (4) In the above equation, d is PeakDelta, and a and b are constants.

[0058] Additionally, 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 verify that a predetermined time period after the timestamp of the meal tag (sometimes referred to as the excursion period) contains at least two hours of glucose data. As another example, a second data validity check may be performed to verify that there is another meal tag within the excursion period, and if so, whether the time period prior to the other meal tag within the excursion period contains at least two hours of glucose data.

[0059] According to another aspect of some embodiments, the score indicator itself is premeal , G peak , or it can be a function of both.

[0060] FIG. 4A-4 is a flow diagram illustrating an exemplary embodiment of a method 4200 for associating analyte data with meal information to account for a user's elevated pre-meal glucose levels. As shown at the top of FIG. 4A-4, method 4200 begins in step 4201, in which the software receives user-entered meal information. In many embodiments, this meal information can be a meal tag entered by the user. The meal tag includes a timestamp that can be correlated with glucose data received from a sensor control device worn by the user. Then, in step 4202, the meal time for each meal tag is matched with the glucose data to reflect post-meal glucose fluctuations. Thus, the analyte data and meal tag can be used to ascertain the initial analyte level and peak analyte level for each meal. In the next step 4203, one or more of the data validity checks described above can be optionally performed. If one or more data validity checks are not passed, the software can indicate that the meal cannot be scored (is unscorable). In some embodiments, the software may also prompt the user to correct the unscorable meals by entering more analyte data, correcting meal tag information, etc. In some embodiments, the software may also prompt the user to delete the unscorable meal tags.

[0061] Continuing to refer to FIG. 4A-4, if one or more data validity checks pass, then in step 4205, the initial analyte level (G premeal ) and peak test substance levels (G peak ) is calculated. An adjusted analyte level variation (PeakDeltaAdj) can then be calculated using any of the methods described above. Then, in a next step 4206, a meal score can be calculated (meals can be assigned meal scores) based on the adjusted analyte level variation (PeakDeltaAdj). Optionally, in step 4207, all of the user's meals can also be ranked by the scores assigned to the meals.

[0062] 4A-5 illustrate steps in a process-implemented method 4300 for an interface displaying TIR information and non-medical data obtained from the sensor control device 102. It should be noted at the outset that one skilled in the art will 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 method 4000, method 4200, or both. For ease of explanation, this embodiment and other embodiments described below refer to the monitored analyte as glucose, although other analytes may be monitored, as noted herein.

[0063] Referring to Figures 4A-5, a method of performing processing for an interface includes step 4301, by at least one processor, receiving data indicative of a test substance level (e.g., data indicative of a glucose level) from a sensor control device 102.

[0064] The method further includes determining, by the at least one processor, the length of time that the data indicative of the analyte level fell within a target value range (predetermined analyte level range) 4302. For example, the predetermined analyte level range may be defined as a glucose range of 70 mg / dL to 180 mg / dL.

[0065] Method 4300 may also include step 4303 of providing an interactive graphical user interface on a display device configured to display data indicative of the analyte level based on the identifying step, such that the display device displays the length of time that the data indicative of the analyte level was within a predetermined analyte level range. According to some embodiments, the length of time that the data indicative of the analyte level was within the predetermined analyte level range may be displayed, for example, in units of time or percentage values, as a circular or ring-shaped graph with segments having areas proportional to the percentage values. In other embodiments, the graphical display may be a geometric shape or image configured to reflect the user's progress, such as a pie chart, one or more bar graphs, a stacked bar graph, a line graph, one or more Harvey Ball diagrams, a thermometer, or a numeric gauge (e.g., a speedometer).

[0066] Referring to FIG. 4B, a block diagram illustrating an exemplary embodiment of a home GUI 400 of a TIR application is shown. According to one aspect of the embodiment, the home GUI 400 may include (1) a TIR card 401, (2) a logbook section 4008, (3) a selectable home icon 403, (4) a selectable meal icon 404, and (5) a "+" icon 405. The logbook section 4008 may include a list 402 of meal events 419. A user may select the home icon 403 to output the home GUI 400. A user may select the meal icon 404 to output a meal report GUI including information about one or more meal events that occurred in a past period (e.g., the past week). A user may select the "+" icon 405 to output a meal log GUI 500 (see, e.g., FIGS. 5A-5G) configured to accept user input of meal information. In some embodiments, the TIR card 401 may include a graphical element that indicates the length of time ("Time In Range," "TIR") that the user's test substance was within the target range over a predetermined period of time (e.g., 24 hours). Although not shown, in some embodiments, the home GUI 400 may include a selectable analysis result icon in place of the meal icon 404. Specifically, although not shown in FIG. 4B, when the user selects the analysis result icon, an analysis result GUI 14000 (e.g., FIGS. 14A-1 to 14A-4) is output. Details of the analysis result GUI 14000 will be described below.

[0067] In some embodiments, the TIR card 401 may highlight the number of hours spent within the target range using a graphical element such as a circle or ring (hereinafter, "TIR ring") 406 indicating the TIR. As shown in FIG. 4B , the TIR card 401 displays a daily TIR goal 407 (TIR in hours (h)) within the TIR ring 406. For example, the daily TIR goal 407 may include a numerical value and units (e.g., "16 hours") indicating the user's predetermined TIR goal. In some embodiments, the current number of hours spent within the predetermined goal range by the user may be displayed in two ways: (1) a TIR value 408 and (2) a progress indicator 418. The TIR value 408 may be displayed numerically and units (e.g., "9 hours") within the ring along with the daily TIR goal 407. The number of hours may also be visually indicated by the progress indicator 418 (e.g., by a darker color). The progress indicator 418 may extend along the periphery of the TIR ring 406 to X% of the circumference of the TIR ring 406 to indicate that the user has currently achieved X% TIR (e.g., X% is the percentage of the number of hours the user has been within the target range to date divided by 24 hours). In this case, the percentage of the circumference of the TIR ring 406 that is occupied by the outer periphery of the TIR ring including the progress indicator 418 (e.g., the darker portion) is proportional to the percentage of the day that the user's test substance has been within the target range to date. In some embodiments, the progress indicator 418 may have a gradational color configured to vary in color intensity. In this case, the degree of change in color intensity gradation may indicate the user's progress toward the daily TIR goal 407 to date. In some embodiments, the TIR value 408 may be expressed as a numerical value (e.g., a percentage (%) or a number in hours (h)) without using the TIR ring 406 or a progress indicator.

[0068] Furthermore, one skilled in the art will recognize that other types of achievement indicators (e.g., textual, numerical, or graphical) can be utilized and are fully within the scope of the present disclosure. Also, while the illustrated graphical elements are in the form of round circles or rings with gradient coloring, one skilled in the art will recognize that other geometric shapes, colors, and numbers of segments or gradients can be employed and are fully within the scope of the present disclosure.

[0069] In some embodiments, the TIR card 401 may further include a selectable information icon 409 that, when selected by the user, may launch a TIR information screen 410 for the TIR card 401. For example, as shown in FIG. 4C , the TIR information screen 410 may provide detailed information about how the progress indicator 418 and daily TIR goal 407 are visually represented in the TIR ring 406. In some embodiments, the TIR information screen 410 may also notify the user that the TIR goal settings can be changed. In some embodiments, the home GUI 400 may further include a selectable settings icon 411. When selected by the user, the settings GUI may launch a settings GUI that allows the user to adjust the TIR goal settings, such as changing the daily TIR goal 407 or changing the units in which the TIR data is displayed (e.g., to display the TIR values ​​408 or daily TIR goal 407 in hours (h) or as a percentage (%)). In some embodiments, as shown in Figure 4B, the home GUI 400 may further include a message 412. The message 412 may be located adjacent to the TIR card and indicate when the TIR card 401 was last updated.

[0070] Referring to FIG. 4B , the home GUI 400 may include a logbook section 4008. The logbook section 4008 has a meal information list 402 that includes one or more meal events 419 that occurred during a predetermined time period (e.g., a day). Each meal event 419 provides detailed information about a specific meal consumed within the predetermined time period. In some embodiments, each meal event 419 may include a text description 413 of the meal (e.g., “blueberry oatmeal”), a portion size indicator 414 (e.g., “normal”) indicating a relative portion size (e.g., whether the meal was “typical,” “larger,” or “smaller” compared to the user’s usual portion size), a timestamp 415 associated with the time the meal was consumed (e.g., “8:04 AM”), or any combination thereof. Note that, although not shown, in some embodiments, the meal event 419 may also include one or more meal tags 416 associated with the meal. A user may use meal tags 416 (not shown) to describe the contents and characteristics of a meal or to list the type of food. Food type tags may include, for example, "vegetables," "chicken," "beef," "pork," "fish," "salad," "pasta," and "vegetarian," to name just a few. Additionally or alternatively, a meal event 419 may include a photo (image) 417 associated with the meal. In some embodiments, a user may take a photo of the meal or select a photo from a photo library. In some embodiments, if a user does not associate a photo 417 with a meal, a placeholder photo (image) 417 is displayed instead. In some exemplary embodiments, the list 402 may be ordered such that the meal event 419 corresponding to the most recently eaten meal is displayed first, i.e., at the top of the list 402, and subsequent meal events 419 are displayed in chronological order.

[0071] Additionally or alternatively, as shown in FIG. 4B , each meal event 419 can include a rating (score) 420 for a particular meal. The rating (score) 420 can be a rating (score) based on an analyte response associated with the particular meal. In some embodiments, the analyte response can be based on the change in analyte level within a predetermined time period after consuming the particular meal. In some embodiments, the score 420 assigned to a meal is based on the change in analyte level from the glucose level at the time of consuming the particular meal to the peak glucose level within three hours after eating.

[0072] Additionally, the score 420 may be displayed numerically. In some embodiments, the score 420 may be a number between 1 and 5, with a higher number representing a lower analyte response and a lower number representing a higher analyte response.

[0073] For example, (1) if the change in test substance level two hours after a meal is between 0 and 20 mg / dL, score 420 can be a "5," (2) if the change in test substance level two hours after a meal is between 21 and 40 mg / dL, score 420 can be a "4," (3) if the change in test substance level two hours after a meal is between 41 and 60 mg / dL, score 420 can be a "3," (4) if the change in test substance level two hours after a meal is between 61 and 90 mg / dL, score 420 can be a "2," and (5) if the change in test substance level two hours after a meal is 91 mg / dL or greater, score 420 can be a "1." As other examples, (1) if the change in analyte level three hours after a meal is between 0 and 24 mg / dL, score 420 can be assigned a score of 5, (2) if the change in analyte level three hours after a meal is between 25 and 49 mg / dL, score 420 can be assigned a score of 4, (3) if the change in analyte level three hours after a meal is between 50 and 74 mg / dL, score 420 can be assigned a score of 3, (4) if the change in analyte level three hours after a meal is between 75 and 99 mg / dL, score 420 can be assigned a score of 2, and (5) if the change in analyte level three hours after a meal is greater than or equal to 100 mg / dL, score 420 can be assigned a score of 1. Those skilled in the art will recognize that other types of changes in analyte level can be used and assigned different scores (which may be more or less than the above) and are fully within the scope of the present disclosure.

[0074] As shown in home GUI 400, score 420 may be represented by a graphical element such as a star icon 421. In some embodiments, star icon 421 may be filled with a color, such as yellow. Additionally, in many embodiments, star icon 421 may be a hollow star with a dashed outline to indicate meal score 420 of "no score." However, one skilled in the art will appreciate that other graphical representations or symbols (e.g., emojis, trophy icons, bars, triangles, squares, circles, etc.) may be used in place of the star icon. A meal score 420 may be "no score" if (1) the user logs the next meal too early (e.g., the user logs the next meal before enough analyte data has been collected to score the current meal), or (2) the TIR application does not have enough analyte data to score the meal 420 (e.g., the user does not scan in a timely manner to ensure that glucose data is transmitted to the TIR application), or both (1) and (2) occur. In some embodiments, a score information icon 422 is displayed on the home GUI 400 adjacent to and proximal to the meal information list 402. When the user selects the score information icon 422, a meal score information modal display is displayed that includes information about various score options and how meal scores are determined.

[0075] 4B , home GUI 400 may further include a text representation 423 indicating the current day of the week. Text representation 423 includes a date and is adjacent to a switch 424 configured to be toggled. In some embodiments, home GUI 400 may be a home GUI related to a past day, in which case the text representation includes the date associated with the past day (e.g., "Friday, February 11th"). Note that, although not shown, in some embodiments, when home GUI 400 is a home GUI related to a past day, home GUI 400 may further include a selectable "Go To Today" link that, when selected, may output home GUI 400 corresponding to the current day.

[0076] In some embodiments, the home GUI 400 is configured to display a plurality of selectable circular rings (hereinafter "rings") 425 (not shown in FIG. 4B ) corresponding to different days of the past week when the user toggles the switch 424 downward. For example, toggling the switch 424 downward may cause the home GUI 400 to display seven rings 425 (not shown in FIG. 4B ), one for each day of the week. Similar to the TIR ring 406 displayed on the TIR card 401, each ring of the plurality of rings 425 represents the user's progress toward their daily TIR goal for that particular day. For example, the user's number of TIR hours for a particular day may be visually indicated by a progress indicator 426 (e.g., a darker shade). The progress indicator 426 may extend along the outer periphery of the ring 425 to X% of its circumference to indicate that the user has achieved X% TIR (X% being the number of hours in the goal range divided by 24 hours).

[0077] In some embodiments, a report GUI 600 is displayed (e.g., FIG. 6B-1) when a user selects a particular one of the multiple rings 425. Also, in some embodiments, toggling switch 424 to the up position causes the display of the multiple rings 425 to disappear. Embodiments of the report GUI 600 are described in more detail below.

[0078] Referring to FIG. 4D , a block diagram illustrating an exemplary embodiment of a home GUI 450 of the TIR application is shown. According to one aspect of the embodiment, the home GUI 450 may include (1) an analyte graph card 451, (2) a logbook section 4508, (3) a selectable home icon 453, (4) a selectable meal icon 454, and (5) a “+” icon 455. The logbook section 4508 may include a list 452 of meal events 469. When a user selects the home icon 453, the home GUI 400 may be output. When a user selects the meal icon 454, a meal review GUI 800 ( FIG. 8 ) may be output, the meal review GUI 800 including information about one or more meal events 469 that occurred in a past period (e.g., the past week). When a user selects the “+” icon 455, a meal logging GUI 500 (not shown) configured to accept meal information input by the user may be output. Although not shown, in some embodiments, the home GUI 450 may include a selectable analysis result icon instead of the meal icon 454. Specifically, when the user selects the analysis result icon, an analysis result GUI 14000 (e.g., FIGS. 14A-1 to 14A-4) is output. Details of the analysis result GUI 14000 will be described later.

[0079] In some embodiments, home GUI 450 is displayed in response to a first predetermined input made by a user on home GUI 400. Examples of the first predetermined input include a predetermined operation such as a user dragging or swiping with a finger. Similarly, home GUI 400 can be displayed in response to a second predetermined input made by a user on home GUI 450. Examples of the second predetermined input include a predetermined operation such as a user dragging or swiping with a finger.

[0080] In some embodiments, the home GUI 450 is similar to the embodiment of the home GUI 400 shown in FIG. 4B , except that the home GUI 450 displays an analyte graph card 451 instead of a TIR card. In some embodiments, the home GUI 450 can include an analyte graph 460 having an analyte trend line 461 reflecting the user's analyte levels over a predetermined time period based on the data indicative of the analyte levels. For example, as shown in FIG. 4D , the analyte graph 460 can have time (e.g., in 3-hour increments) on the x-axis and the user's analyte concentration measurements (e.g., in mg / dL) on the y-axis, with the length of the time period displayed on the x-axis being 12 hours. However, such an analyte graph 460 can display data over any desired time period. Accordingly, one skilled in the art will recognize that the length of the time period displayed on the x-axis can be other predetermined time periods (e.g., 2 hours, 4 hours, 24 hours, 48 ​​hours, etc.) and are fully within the scope of the present disclosure. According to some aspects of the embodiments, the user's glucose concentration (units: mg / dL or mmol / L) can be displayed for a fixed period, such as a day or a portion of a day. The period displayed on the x-axis can start at midnight of the current day, and glucose concentration measurements from that point onward can be displayed.

[0081] Analyte graph 460 may include lines 462-1 and 462-2 that indicate a user's target analyte range associated with the data indicating the analyte level. For example, the area between lines 462-1 and 462-2 indicates the target analyte value range (e.g., a range of 70 mg / dL to 180 mg / dL). In some embodiments, as shown in FIG. 4D , analyte trend line 461 corresponding to time periods when the user's analyte level was outside (e.g., above or below) the target analyte range is represented by a dotted or dashed line. Furthermore, analyte trend line 461 corresponding to time periods when the user's analyte level was within the target analyte range is represented by a solid line. As noted above, the target analyte range may be user-configurable. For example, the target analyte range can be set to a range of about 80 mg / dL to about 170 mg / dL, or a range of about 70 mg / dL to about 180 mg / dL, or a range of about 65 mg / dL to about 120 mg / dL. In some embodiments, as shown in FIG. 4D, the home GUI 450 can further include a message 463. The message 463 can be located adjacent to the analyte graph card 451 and can indicate when the analyte graph card 451 was last updated.

[0082] 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, the one or more meal icons 464 may be displayed near, adjacent, or proximal to the analyte trend line 461, or along the x-axis, the top of the graph window, or the bottom of the graph window. Additionally, in some embodiments, the one or more meal icons 464 may be displayed with or without a leader line. Each meal icon 464 may be a photo or image associated with a particular meal. In some aspects of the embodiments, the meal icons 464 are positioned on the analyte trend line 461 to allow a user to visually associate the meal with the analyte trajectory after that meal. Additionally, in some embodiments, the meal icons 464 are positioned on the analyte trend line 461 based on the time of day associated with the meal. For example, if meal event 469 indicates that blueberry oatmeal was eaten at 8:04 AM, meal icon 464 corresponding to blueberry oatmeal meal event 469 will be displayed at a position on the x-axis of test substance graph 460 corresponding to approximately 8:04 AM.

[0083] 4D , like the home GUI 400, the home GUI 450 can also include a logbook section 4508. The logbook section 4508 has a list 452 of one or more meal events 469 that occurred during a given time period (e.g., a day). Each meal event 469 provides detailed information about a particular meal consumed during the given time period. As discussed above with respect to the home GUI 400, in some embodiments, each meal event 469 can include a text description 473 of the meal (e.g., “blueberry oatmeal”), a portion size indicator 474 (e.g., “medium”) indicating the relative portion size (e.g., whether the portion size is “medium,” “large,” or “small” compared to the user’s usual portion size), a timestamp 475 associated with the time the meal was consumed (e.g., “8:04 AM”), or any combination thereof. Note that, although not shown, in some embodiments, a meal event 469 can also include one or more meal tags 476 associated with the meal. Additionally or alternatively, meal event 469 may also include a photo (image) 477 associated with the meal. In some embodiments, if a user has not associated a photo (image) 477 with a meal, a placeholder image 477 is displayed instead. In some exemplary embodiments, list 452 may be ordered such that meal event 469 corresponding to the most recently eaten meal is displayed first, i.e., at the top of list 452, with subsequent meal events 469 displayed in chronological order.

[0084] Additionally or alternatively, as shown in FIG. 4D , each meal event 469 can also include a rating (score) 480 for a particular meal, similar to the embodiments described above. The rating (score) 480 can be a rating (score) for each meal based on the analyte response. In some embodiments, the analyte response can be based on the change in analyte level within a predetermined time after consuming the particular meal. In some embodiments, the score 480 assigned to a meal is based on the change in analyte level from the glucose level at the time of consuming the particular meal to the peak glucose level within three hours after eating. Furthermore, the score 480 can be displayed numerically. In some embodiments, the score 480 can be a number from 1 to 5, with a higher number representing a lower analyte response and a lower number representing a higher analyte response. Additionally, as shown in the home GUI 450, each score 480 can be displayed with a graphic element, such as a star icon 481. In some embodiments, each star icon 481 may be filled with a color, such as yellow. Also, in many embodiments, the star icon 481 may be a hollow star with a dashed outline to indicate that the meal score 480 is "no score." In some embodiments, a score information icon 492 is displayed on the home GUI 450 adjacent to and proximal to the list 452. When the user selects the score information icon 492, a meal score information modal display is displayed that includes information about various score options and how the meal score is determined.

[0085] Like home GUI 400, home GUI 450 may further include a text representation 493 indicating the current day of the week. Text representation 493 includes a date and is adjacent to a switch 494 configured to be toggled. In some embodiments, home GUI 450 may be a home GUI related to a past day, in which case the text representation includes the date associated with the past day (e.g., "Friday, February 11th"). Although not shown, in some embodiments, when home GUI 450 is a home GUI related to a past day, home GUI 450 may further include a selectable "Go to today" link that, when selected, may output home GUI 450 corresponding to the current day.

[0086] In some embodiments, the home GUI 450 is configured to display multiple selectable rings 425 when the user toggles the switch 494 down. Each of the rings 425 represents a TIR indicator corresponding to a different day in the past week. Each of the rings 425 corresponding to a different day may include a graphical (visual) indicator of the TIR amount (progression indicator) and an indicator of the goal as a percentage (%) or number of hours of TIR (h). In some embodiments, when the user selects a particular one of the rings 425, a report GUI 600 (not shown) for that day is displayed. However, one skilled in the art will recognize that other types of indicators (e.g., text indicators, numerical indicators (percentages or scores), or graphical indicators) can be utilized and are fully within the scope of the present disclosure.

[0087] Additionally, in some embodiments, the home GUI 450 may further include a selectable settings icon 498. When the user selects the settings icon 498, a settings GUI for the TIR application may be output.

[0088] 4E-1 , a block diagram illustrating a further exemplary embodiment of a home GUI 430 of the TIR application is shown. In some embodiments, the home GUI 430 can include: (1) a TIR card 431; (2) an analyte graph card 4311; (3) a logbook section 4308; (4) a selectable home icon 433; (5) a selectable meal icon 434; and (6) a “+” icon 435. The analyte graph card 4311 can include an analyte graph 4310 with an analyte trend line 4315. The logbook section 4308 can include a list 432 of meal events 4309. A user can select the home icon 433 to output the home GUI 430. A user can select the meal icon 434 to output a meal report 600 ( FIGS. 6B-1 and 6B-2 ) containing information about one or more meal events that occurred over a past period (e.g., the past week). When the user selects the "+" icon 435, a meal log recording GUI 500 (see, for example, FIGS. 5A to 5G) configured to accept the user's input of meal information can be output. Note that the TIR card 431 and the test substance graph card 4311 are displayed on a single interface. Note that, although not shown, in some embodiments, the home GUI 430 can also include a selectable analysis result icon instead of the meal icon 434. Specifically, although not shown, when the user selects the analysis result icon, an analysis result GUI 14000 (e.g., FIGS. 14A-1 to 14A-4) is output. Details of the analysis result GUI 14000 will be described later.

[0089] According to one aspect of the embodiment, the TIR card 431 of the home GUI 430 is similar to the TIR card 401 of the home GUI 400 shown in FIG. 4B , except that the visual representation of the TIR card 431 differs from the visual representation of the TIR card 401. Specifically, for the TIR card 431 ( FIG. 4E-1 ), the daily TIR goal 437 is displayed outside the TIR ring 436 rather than within the area inside the TIR ring 436. For example, in some embodiments, the daily TIR goal 437 is positioned adjacent to the TIR ring 436. According to one aspect of the embodiment, the TIR ring 436 includes an achievement indicator 438 and a TIR value 4305. Like the TIR card 401 shown in FIG. 4B , the TIR card 431 of the home GUI 430 also includes a selectable information icon 439, and when a user selects the information icon 439, a TIR information screen 440 for the TIR card 431 is displayed. Note that, as shown in Figure 4F, TIR information screen 440 is similar to TIR information screen 410 shown in Figure 4C. Specifically, TIR information screen 440 provides detailed information about how progress indicator 438 and daily TIR goal 437 are visually represented in daily TIR ring 436. In some embodiments, TIR information screen 440, such as that shown in Figure 4F, may also notify the user that the TIR goal settings can be changed.

[0090] According to another aspect of the embodiment, the analyte graph card 4311 of the home GUI 430 is similar to the analyte graph card 451 of the home GUI 450 shown in FIG. 4D , except that it includes a target analyte range 4312 (e.g., “Target Glucose Range: 70-180 mg / dL”). Additionally, as shown in FIG. 4E-1 , the home GUI 430 also includes one or more selectable icons 4313 (e.g., radio buttons, checkboxes, sliders, switches, etc.) that allow a user to select a predetermined time length for displaying user analyte data on the analyte graph card 4311. For example, the selectable icon 4313 may be used to select a predetermined time length (e.g., 4 hours, 12 hours, or 24 hours) that is at least approximately 4 hours and up to approximately 24 hours. Those skilled in the art will recognize that other predetermined time lengths are possible and fully within the scope of the present disclosure. In some embodiments, as shown in FIG. 4E-1, the selectable icon 4313 can be positioned on the test substance graph card 4311 immediately adjacent to the test substance graph 4310, distal to the test substance graph 4310.

[0091] Although not shown in FIG. 4E-1 , in some embodiments, one or more meal icons may be displayed below and immediately adjacent to the location of the test substance graph 4310 or below the x-axis location. For example, the meal icons may be displayed at the bottom of the graph window 4314. According to some aspects of the embodiments, the meal icons are positioned on the test substance graph card 4311 to allow the user to visually associate the meal with the test substance trajectory after the meal. Additionally, in some embodiments, the meal icons are positioned below the test substance graph 4310 or x-axis location based on the time associated with the meal. For example, if meal event 4309 indicates a meal was eaten at 9:00 AM, the meal icon corresponding to meal event 4309 is displayed below and immediately adjacent to the 9:00 AM location on the x-axis of the test substance graph 4310.

[0092] In some embodiments, as shown in FIG. 4E-2, a notification 4316 may be displayed on the analyte graph card 4311. The notification 4316 may inform the user that they can perform an input action (e.g., a tap or a long tap) on the trend line 4315 to display glucose readings associated with a selected region of the trend line 4315. Additionally, in some embodiments, the notification 4316 may inform the user that they can also use a swipe scroll action on the trend line 4315 to display glucose readings for different selected regions of the trend line 4315. Additionally, FIG. 4E-3 illustrates the home GUI 430 with a visual indication 4317 displayed on the analyte graph card 4311. The visual indication 4317 includes an analyte reading (e.g., a glucose reading) corresponding to the selected region of the trend line 4315. In some embodiments, the visual display may include the analyte level value and timestamp (e.g., "117 mg / dL" and "10:00 AM") corresponding to the selected area of ​​the trend line 4315.

[0093] In some embodiments, as shown most clearly in FIG. 4E-3, the analyte graph card 4311 may include an analyte graph information icon 4318, which, when selected by the user, may output the analyte graph information modal display 445 ( FIG. 4G ). The analyte graph information modal display 445 may provide the user with information regarding selecting from predefined time lengths for which the user's analyte data is displayed in the analyte graph card 4311. Additionally, in some embodiments, the analyte graph information modal display 445 may inform the user that tapping or long-tapping an area in the analyte graph 4310 will visualize a glucose reading associated with the selected area. In some embodiments, the analyte graph information modal display 445 also includes a disclaimer informing the user that they should consult with a medical professional before making any changes to their diet or exercise program.

[0094] In some exemplary embodiments, a notification card 441 may be output on the home GUI 430, as shown in FIG. 4E-4. For example, the notification card 441 may be displayed in a position on the home GUI 430 immediately adjacent to and above the position of the TIR card 431. In some embodiments, the positions of the TIR card 431, the analyte graph card 4311, and the logbook section 4308 on the home GUI 430 are moved down to accommodate the notification card 441 on the home GUI 430. In some embodiments, the notification card 441 may notify the user that it is time to scan the sensor. Additionally, in some embodiments, the notification card 441 may notify the user that a sensor scan can be performed using the analyte monitoring application.

[0095] In some exemplary embodiments, a notification card 441 may be output in the home GUI 430 instead of the TIR card, as shown in FIG. 4E-5. For example, the notification card 441 may be displayed immediately adjacent to and above the location of the analyte graph card 4311. In some exemplary embodiments, the notification card 441 may prompt the user to take a challenge associated with a new TIR goal. For example, the notification card 441 may notify the user that the user has achieved their TIR goal a certain number of times in a predetermined time period (e.g., five days out of the last seven days) and prompt the user to increase their TIR goal by a certain number of hours (e.g., one hour). In some embodiments, the notification card 441 may include a “Don't Try” button 442 that the user can select to decline the challenge and a “Try” button 443 that the user can select to accept and initiate the challenge. According to one aspect of an embodiment, the TIR application may be configured to output a notification card 441 to the user containing a prompt to take the challenge after the user has achieved their TIR goal a certain number of times in a predetermined time period.

[0096] Notification card 441 can be used with any of the embodiments described herein. Additionally, in some embodiments, notification card 441 may include (1) information about recording a food log (e.g., "Welcome, [username], tap the '+' button below to add your first meal" or "Great job, [username]! You've added your first meal! Scan your sensor in the Libre2 app in 3 hours and then come back to the app to see how your body responded to this meal"), (2) information about scanning (e.g., Ready? Scan your sensor in the Libre2 app to start tracking your progress toward your TIR goal. Aim to complete one TIR ring by midnight each day" or "Scan your sensor in the Libre2 app. Once scanned, come back to the app to see how your body responded to this meal"), and (3) information about updating settings (e.g., "Time In "Your range goal is set. You can check your goal tomorrow in the app." or "Your new goal is [number of hours] hours. You can check your goal tomorrow in the app. Keep it up!"), (4) a message encouraging the user (e.g., "Your new goal is [number of hours] hours. You can check your goal tomorrow in the app. Keep it up!" or "Great job, [username]! You've met your goal for 5 of the last 7 days. Challenge yourself to beat your goal by 1 hour! Take the challenge!"), (5) a message encouraging the user to take on a new challenge (e.g., "Great job, [username]! You've met your goal for 5 of the last 7 days. Challenge yourself to beat your goal by 1 hour! Take the challenge!"), or (6) a message informing the user that their score is in (e.g., "Your score is in! Your first meal score is in. Tap the meal card below for details.").

[0097] Additionally, as shown most clearly in FIG. 4E-1 , according to another aspect of the embodiment, the analyte graph card 4311 can include a selectable arrow 4319. When a user selects the arrow 4319, the view of the analyte graph 4310 displayed on the analyte graph card 4311 can be changed to a different view. For example, if the analyte graph card 4311 is configured to display analyte data for a predetermined time period (e.g., 24 hours), the analyte graph 4310 can be divided into a first view and a second view. In some embodiments, the first view of the analyte graph 4310 displays analyte data for a first portion of the predetermined time period (e.g., displays analyte data from midnight to 6:00 PM or from midnight to 9:00 PM). Additionally, although not shown, a second view of the test substance graph 4310 displays test substance data for a second portion of a predetermined time period (e.g., displaying test substance data from 6:00 PM to 12:00 PM or from 9:00 PM to 12:00 PM).

[0098] In some exemplary embodiments, for example, as shown in FIGS. 4E-1 through 4E-4, the TIR card 431 can be located on the home GUI 430 immediately adjacent to, and proximal to, the analyte graph card 4311. Additionally, the logbook section 4308 can be located on the home GUI 430 immediately adjacent to, and distal to, the analyte graph card 4311.

[0099] FIG. 4E-6 further illustrates the home GUI 430 for the user's first day (first 24 hours) of use of the TIR application. The home GUI 430 illustrated in FIG. 4E-6 includes an analyte graph card 4311 without an analyte trend line. Also, in some embodiments, the home GUI 430, before the user enters meals into the TIR application, includes a logbook section 4308 without a list of entered meal events. Also, in some embodiments, the logbook section 4308 illustrated in FIG. 4E-6 includes a note 446 informing the user that no meals have yet been added. According to another aspect of the embodiment, the home GUI 430, before a daily TIR goal is set in the TIR application, can include a TIR card 431 without a daily TIR goal or TIR value in the TIR ring 436. In some embodiments, as illustrated in FIG. 4E-6, before a daily TIR goal is set in the TIR application, the TIR card 431 can include a message 447 informing the user that the TIR application is collecting data for the user. Furthermore, in some embodiments, before a daily TIR goal is set in the TIR application, the TIR card 431 may further include a selectable information icon 448, which, when selected by the user, may output an information modal display 465 ( FIG. 4H ). As shown in FIG. 4H , the information modal display 465 may include a message 466 informing the user that the TIR application is calculating usage data for the first 24 hours of use of the TIR application in order to set an optimized TIR goal for the individual user. Furthermore, the information modal display 465 may also include a reminder that periodic sensor scans can be performed while the user waits for the goal to be set. The information modal display 465 may be configured to obscure (overlay) a portion of the home GUI 430 displayed below it. In some embodiments, the information modal display 465 may further include a selectable “OK” button 467 that the user can press.

[0100] FIG. 4E-7 illustrates the home GUI 430 after an individualized user-optimized daily TIR goal 437 has been set. Specifically, FIG. 4E-7 illustrates the home GUI 430 with the user's daily TIR goal 437 displayed on the TIR card 431. In some embodiments (as shown in FIG. 4E-7), the daily TIR goal 437 can be set before the TIR application displays analyte trend lines or before the user enters meal events. According to one aspect of the embodiment, the daily TIR goal 437 and TIR value 4305 can be displayed in the TIR ring 436 of the home GUI 430 as a number indicating the determined number of hours and their units. In some embodiments, if the daily TIR goal 437 has been set but the number of TIR hours for a particular period has not yet been detected, a placeholder image (photo) 449 can be displayed in the TIR ring 436, as shown in FIG. 4E-7. In some embodiments, once the daily TIR target 437 is set, a modal display 470 (FIG. 41) may be output informing the user that a new TIR target has been set. Additionally, in some embodiments, the modal display 470 may also inform the user that the TIR target can be changed from the settings in the TIR application.

[0101] In some embodiments, as shown most clearly in FIG. 4E-7 , home GUI 430 may further include a text representation 4333 indicating the current day of the week. Text representation 4333 includes a date and is adjacent to a switch 4334 configured to be toggled. In some embodiments, home GUI 430 may be a home GUI related to a past day, in which case text representation 4333 includes the date associated with the past day (e.g., "Friday, February 11th"). Note that, although not shown, in some embodiments, when home GUI 430 is a home GUI related to a past day, home GUI 430 may further include a selectable "Go to today" link that, when selected, may output home GUI 430 corresponding to the current day.

[0102] 4J-1-4J-3, further exemplary embodiments of the home GUI 485 are shown. As shown in FIGS. 4J-1-4J-3, the home GUI 485 is similar to the home GUI 430 (see, e.g., FIG. 4E-1 ), except that the logbook section 4808 of the home GUI 485 includes one or more time of day (TOD) cards 4801. Specifically, the home GUI 485 includes a time-to-interval (TIR) ​​card 4819, an analyte value graph card 4811, a logbook section 4808, a selectable home icon 4821, and a selectable “+” icon 4823, where the TIR card 4819 includes information regarding the amount of time that data indicative of a glucose level was within a predetermined analyte level range (e.g., a predetermined glucose level range). Furthermore, in some embodiments, as shown in FIGS. 4J-1 through 4J-3, the home GUI 485 includes a selectable analysis result icon 4804 in place of the meal icon. Specifically, when the user selects the analysis result icon 4804, the analysis result GUI 14000 (e.g., FIGS. 14A-1 through 14A-4) is output. Details of the analysis result GUI 14000 are described below. It should be understood that a person skilled in the art would recognize that the meal icon could be employed in the home GUI 485 in place of the analysis result icon 4804.

[0103] 4J-1-4J-3, each TOD card 4801 in the logbook section 4808 of the home GUI 485 can represent a different increment of time (i.e., a different time period) on a particular day. As shown most clearly in FIG. 4J-1, in some embodiments, the logbook section 4808 can include four different TOD cards 4801, with each TOD card 4801 representing a different six-hour period on a particular day. For example, as most clearly shown in FIG. 4J-1, 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 a time period from midnight to 6:00 AM on a particular day), (2) a "Morning" TOD card 4801b (e.g., a TOD card 4801 corresponding to a time period from 6:00 AM to noon on a particular day), (3) an "Afternoon" TOD card 4801c (e.g., a TOD card 4801 corresponding to a time period from noon to 6:00 PM on a particular day), and (4) an "Evening" TOD card 4801d (e.g., a TOD card 4801 corresponding to a time period from 6:00 PM to midnight on a particular day). However, those skilled in the art will appreciate that various TOD cards and time periods may be used as the TOD card 4801 and the time periods associated with each TOD card 4801 without departing from the scope of this disclosure.

[0104] Continuing with reference to FIGS. 4J-1 through 4J-3, in some embodiments, each TOD card 4801 may include, but is not limited to, (1) a TOD display 4802 configured to indicate the daypart represented by the TOD card 4801 (e.g., "Midnight," "AM," "PM," or "Night"), (2) a time of day display 4803 configured to indicate the time of day represented by the TOD card 4801 (e.g., "12 midnight to 6 AM" for the "Midnight" TOD card 4801," "6 AM to 12 PM" for the "AM" TOD card 4801," "12 PM to 6 PM" for the "PM" TOD card 4801," and "6 PM to 12 midnight" for the "Night" TOD card 4801), and (3) a TOD icon 4804 configured to represent the daypart associated with the TOD card 4801 (e.g., For the "Late Night" TOD card 4801, the TOD icon may include a moon with multiple "Z"s to represent the late night time slot; for the "Morning" TOD card 4801, a half-closed sun or sunrise TOD icon 4804 to represent the morning time slot; for the "Afternoon" TOD card 4801, a full sun TOD icon 4804 to represent the afternoon time slot; and for the "Night" TOD card 4801, a moon TOD icon 4804 to represent the night time slot), and (4) a graphical representation 4805 showing an average analyte score (e.g., average glucose score) associated with the time slot represented by the TOD card 4801 (e.g., the graphical representation 4805 for the "Late Night" TOD card 4801 shows an average glucose score corresponding to the time slot from midnight to 6:00 AM). However, one skilled in the art will recognize that other time ranges (time slots) may be used to represent various time slots in the time slot display 4803. According to some embodiments, the time periods represented in time period display 4803 may be preset or may additionally or alternatively be user configurable. Furthermore, according to one aspect of an embodiment, the average analyte score associated with the TOD card 4801 associated with the current time of day is configured to be continually updated.For example, if the current time is 9:00 AM, the "AM" TOD card 4801 (e.g., the TOD card 4801 representing the time period from 6:00 AM to noon) is configured so that the average test substance score for the "AM" TOD card 4801 is constantly updated.

[0105] As shown most clearly in FIG. 4J-1, in some embodiments, the test substance graph card 4811 of the home GUI 485 may include test substance graph TOD icons 4814 corresponding to the TOD icons 4804 displayed on each TOD card 4801 (e.g., a moon test substance graph TOD icon 4814a with multiple "Z"s representing the late night hours represented by the "late night" TOD card 4801, a half-blooming sun or sunrise test substance graph TOD icon 4814b representing the morning hours represented by the "morning" TOD card 4801, a full sun test substance graph TOD icon 4814c representing the afternoon hours represented by the "afternoon" TOD card 4801, and a moon test substance graph TOD icon 4814d representing the night hours represented by the "night" TOD card 4801). Specifically, as shown most clearly in FIG. 4J-1 , each analyte graph TOD icon 4814a, 4814b, 4814c, 4814d is displayed near, adjacent, proximal to, or along the x-axis or bottom of the graph window 484 of the analyte graph card 4811. More specifically, each analyte graph TOD icon 4814 is displayed along the x-axis to allow a user to visually associate each time period with the analyte graph TOD icon 4814 on the analyte graph card 4811.

[0106] As shown most clearly in Figures 4J-1-4J-3, in some exemplary embodiments, the graphical representation 4805 is divided into a number of segments 4806. Each segment is configured to be filled (or not filled) with a color corresponding to the average analyte score. In an exemplary embodiment, as shown most clearly in FIG. 4J-1 , the graphical representation 4805 may include a bar shape divided into three segments 4806, where (1) the first segment 4806 a may be colored red or orange to indicate an analyte score corresponding to a high glucose load (e.g., an average glucose value in the range of greater than 250 mg / dL), (2) the first segment 4806 a and the second segment 4806 b may be colored yellow to indicate an analyte score corresponding to a moderate glucose load (e.g., an average glucose value in the range of 181 mg / dL to 250 mg / dL), and (3) the first segment 4806 a, the second segment 4806 b, and the third segment 4806 c may be colored green to indicate an analyte score corresponding to a low glucose load (e.g., an average glucose value in the range of 70 mg / dL to 180 mg / dL). Although not shown, in some embodiments, if the average glucose score corresponds to a lower glucose load (e.g., if the average glucose value is in the range of less than 70 mg / dL), segments 4806 of graphical representation 4805 are replaced with a "LOW" icon. However, one skilled in the art will appreciate that various other graphical representations, colors, and color settings can be used for graphical representation 4805 without departing from the scope of the present disclosure.

[0107] Further, with particular reference to FIG. 4J-2 , in some embodiments, visual display 4807 may be displayed on home GUI 485 in response to a user providing a third predetermined input. The third predetermined input may include a predetermined action, such as a user tapping on graphical representation 4805 corresponding to a particular TOD card 4801. Specifically, visual display 4807 is configured to display an average analyte level value associated with the selected graphical representation (e.g., an average glucose value of “117 mg / dL”). Further, in some exemplary embodiments, information icon 4882 is displayed on home GUI 485. Information icon 4882 is configured to output an analyte score information modal display (including information related to the average analyte score, such as, but not limited to, how the average analyte score is determined) when a user selects information icon 4882.

[0108] In some embodiments, the analyte score information modal display can include a lookup table that provides information regarding the average glucose score, the range of average glucose values ​​associated with the average glucose score, and the stress level associated with the average glucose score. In some embodiments, the analyte score information modal display can further include detailed information about the user's target glucose range (e.g., a target glucose range of 70-180 mg / dL) and notify the user that the target glucose range can be set or changed in the analyte monitoring application. In some embodiments, the analyte score information modal display can also include a disclaimer informing the user that they should consult with a medical professional before making any changes to their diet or exercise program. In some embodiments, the analyte score information modal display can further include one or more information cards, each of which can provide information about the TOD card 4801 (e.g., information about the time periods and the reasons for the time periods). In some embodiments, the information cards can be configured such that, in response to a fourth predetermined input by the user, a selected information card expands to provide further details about the TOD card 4801. The fourth predetermined input may be, for example, a predetermined operation such as tapping or pulling down on a specific information card, although in some embodiments, each information card is folded by default.

[0109] 4J-1 and 4J-3, each TOD card 4801 can be toggled between a collapsed view and an expanded view. Specifically, according to some embodiments, a TOD card 4801 in a collapsed view (see, e.g., FIG. 4J-1 showing each TOD card 4801 in a collapsed view) is configured to display a TOD display 4802, a day of the day display 4803, a TOD icon 4804 representing a daypart associated with the TOD card 4801, and a graphical representation 4805 showing an average glucose score associated with the day of the day represented by the TOD card 4801. Additionally, according to some embodiments, a TOD card 4801 in expanded view (e.g., see FIG. 4J-3 showing the "Evening" TOD card 4801 in expanded view) is configured to display a TOD display 4802, a day of the day display 4803, a TOD icon 4804 representing the daypart associated with the TOD card 4801, a graphical representation 4805 showing an average glucose score associated with the daypart represented by the TOD card 4801, and a meal information summary 4822 including one or more meal events 4829 that occurred during the daypart associated with the TOD card 4801. Additionally, in some embodiments, each TOD card 4801, when in expanded view, is configured to display a meal log link 4809, which, when selected by a user, launches a meal log GUI 500, as shown in FIG. 5A . The meal log GUI 500 is described below.

[0110] Specifically, in some embodiments, when a user selects the meal log link 4809 and enters meal information through the meal log GUI 500, detailed information about the entered meal information is displayed as a meal event 4829 in the meal information list 4822 of the TOD card 4801 that includes the selected meal log link 4809. In some exemplary embodiments, as shown most clearly in FIG. 4J-3 , the meal log link 4809 is positioned immediately adjacent to, but distal to, the list 4822 of meal events 4829 displayed on the TOD card 4801 in expanded view.

[0111] In some embodiments, as shown most clearly in FIG. 4J-3 , each TOD card 4801 can be configured to include information about one or more meal events 4829 that occurred during the time period represented by the TOD card 4801. According to one aspect of the embodiment, each meal event 4829 can include a textual description of the meal 4823, a meal type indicator 4824 indicating whether the entered meal information is food or drink information, a timestamp 4825 associated with the time the meal was consumed, a photo (image) 4826 associated with the meal, or any combination thereof. In some embodiments, if a photo (image) 4826 has not been associated with a meal by the user, a placeholder image is displayed instead. In some exemplary embodiments, the order of the list 4822 can be such that the meal event 4829 corresponding to the most recently consumed meal is displayed first, i.e., at the top of the list 4822 for the TOD card 4801, and subsequent meal events 4829 are displayed in chronological order.

[0112] Furthermore, in some exemplary embodiments, each meal event 4829 is configured to output a meal review GUI 800 (shown in FIG. 8 , described in more detail below) associated with the selected meal event 4829 in response to a fifth predetermined input by the user. The fifth predetermined input may include, for example, a predetermined operation such as tapping on a particular meal event 4829.

[0113] According to another aspect of the embodiment, as shown most clearly in FIG. 4J-3, each TOD card 4801 may include a count counter 4810. The count counter 4810 may be configured to display the number of meal events 4829 logged for a particular time period associated with the corresponding TOD card 4801. For example, if a user logs two meal events 4829 for an "Evening" TOD card 4801, the count counter 4810 associated with the "Evening" TOD card 4801 may display "2." Additionally, according to some embodiments, each TOD card 4801 may be configured to display the count counter 4810 in both the collapsed view and the expanded view.

[0114] According to yet another aspect of the embodiment, each TOD card 4801 is configured to switch between a collapsed view and an expanded view in response to a sixth predetermined input by a user on the TOD card 4801. The sixth predetermined input may include, for example, a predetermined action such as tapping the TOD card 4801, pulling the TOD card 4801 down with a finger, or pulling the TOD card 4801 up with a finger. For example, in exemplary embodiments, each TOD card 4801 may switch from a collapsed view to an expanded view in response to a received user input (e.g., a tap, a pull down, or selecting or pressing a corresponding area on the TOD card 4801). Furthermore, in some embodiments, each TOD card 4801 may switch from an expanded view to a collapsed view in response to a received user input (e.g., a tap, a pull up, or selecting or pressing a corresponding area on the TOD card 4801).

[0115] 4J-1-4J-3, in some embodiments, the home GUI 485 is configured to display the TOD card 4801 corresponding to the current time in an expanded view by default. For example, if the current time is 9:00 AM, the home GUI 485 is configured to display the "AM" TOD card 4801 in an expanded view. Furthermore, when a new time slot is entered, for example, when the day switches from the AM time slot to the PM time slot, a TOD card 4801 corresponding to the new time slot (e.g., the "PM" TOD card 4801) is added to the logbook section 4808 of the home GUI 485. Specifically, the TOD card 4801 corresponding to the new time slot is output to the home GUI 485 in an expanded view by default. In some embodiments, the TOD card 4801 corresponding to the current time (e.g., the "Afternoon" TOD card) is displayed in an expanded view by default, while the TOD cards 4801 corresponding to past times of the day (e.g., the "Late Night" TOD card 4801 and the "Morning" TOD card 4801) are displayed in a collapsed view by default.

[0116] In some embodiments, the TOD card 4801 corresponding to the current time may also be displayed in a collapsed view by default. In some embodiments, the logbook section 4808 is configured to display each TOD card 4801 in a collapsed view by default.

[0117] Additionally, although not shown, in some embodiments, the TOD card 4801 corresponding to the current time may be colored to highlight the TOD card 4801 as being active. For example, if the current time is 7:00 PM, the "PM" TOD card 4801 may be colored to indicate that the "PM" TOD card 4801 is active. Specifically, the TOD icon 4804, TOD display 4802, or both of the TOD card 4801 corresponding to the current time may be colored (e.g., highlighted in blue) (while all other TOD displays 4802 and TOD icons 4804 corresponding to other TOD cards 4801 are not highlighted).

[0118] According to another aspect of the embodiment, as shown most clearly in FIG. 4J-1 , the logbook section 4808 is further configured to display TOD cards 4801 in association with past time slots for the particular day being displayed on the interface and the current time slot. For example, in some embodiments, as shown in FIG. 4J-1 , if the current time is 7:00 PM, the logbook section 4808 is configured to display a “Midnight” TOD card 4801 a, a “Morning” TOD card 4801 b, an “Afternoon” TOD card 4801 c, and an “Evening” TOD card 4801 d. In some embodiments, the time slot display of the TOD card 4801 corresponding to the current time (e.g., the “Afternoon” TOD card 4801 if the current time is 3:00 PM) is configured to display an in-progress stamp 4812 (e.g., “Now”) indicating that the time slot is the current time slot (the in-progress time slot). In some embodiments, the in-progress stamp 4812 is displayed as part of the TOD display 4802. For example, if the current time is 3:00 PM, the time period display 4803 of the "Afternoon" TOD card 4801 may display "Noon to Now" to indicate that the time period that includes the current time is the time period associated with the active TOD card 4801 (e.g., for the "Afternoon" TOD card 4801, the time period from noon to 6:00 PM).

[0119] In some embodiments, as shown most clearly in FIG. 4J-1 , home GUI 485 may further include a text representation 4833 indicating the current day of the week. Text representation 4833 includes a date and is adjacent to a switch 4834 configured to be toggled. In some embodiments, home GUI 485 may be a home GUI related to a past day, in which case text representation 4833 includes the date associated with the past day (e.g., "Friday, February 11th"). Note that, although not shown, in some embodiments, when home GUI 485 is a home GUI related to a past day, home GUI 485 may further include a selectable "Go to today" link that, when selected, may output home GUI 485 corresponding to the current day.

[0120] 4K-1-4K-3, block diagrams illustrating further exemplary embodiments of a home GUI 495 of the TIR application are shown. In some embodiments, the home GUI 495 may include: (1) a daily scorecard 4951; (2) a test substance graph card 4911; (3) a logbook section 4958; (4) a selectable home icon 4953; (5) a selectable analysis results icon 4954; and (6) a "+" icon 4957. A user may select the home icon 4953 to output the home GUI 495. A user may select the analysis results icon 4954 to output the analysis results GUI 14000 (e.g., FIGS. 14A-1-14A-4). The analysis results GUI 14000 is described in more detail below. A user may select the "+" icon 4957 to output a meal logging GUI 500 (e.g., see FIGS. 5A-5G) configured to accept meal information input by the user.

[0121] According to one aspect of the embodiment, the home GUI 495 is similar to the home GUI 485 (see, e.g., FIGS. 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” using a graphical element, such as a circle or ring (hereinafter, “daily scoring”) 4903 indicating the daily score. The daily score is based on the user's logged meals, the user's test substance control (e.g., glucose control), or both. For example, as shown in FIG. 4K-1 , the daily scoring 4903 shown on the daily card 4951 displays a daily score value 4904 (points earned each day) within the inner area. For example, the daily score value 4904 can include a numerical value and units (e.g., “80 points”) indicating the user's daily score. In some embodiments, the user's current daily score against a predetermined daily score goal may be displayed in two ways: (1) a daily score value 4904 and (2) an achievement indicator 4905. The daily score value 4904 may be displayed numerically and in units (e.g., "80 points") within the daily scoring 4903. The daily score value 4904 may also be visually displayed as an achievement indicator 4905 (e.g., a darker color). The achievement indicator 4905 may be a display that extends around the perimeter of the daily scoring 4903 to X% of the circumference of the daily scoring 4903 to indicate that the user has currently achieved X% of the predetermined daily score goal (e.g., X% is the daily score value 4904 divided by the predetermined daily score goal). In this case, the proportion of the outer periphery (e.g., the darker portion) of daily scoring 4903 including achievement indicator 4905 to the entire circumference of daily scoring 4903 is proportional to the proportion of the daily score value 4904 achieved by the user up to this point in time toward the predetermined daily score goal. In some embodiments, achievement indicator 4905 can be colored with a gradation configured to change the color density. In this case, the degree of change in color density gradation can indicate the user's progress toward the predetermined daily score goal up to this point in time.

[0122] Furthermore, one skilled in the art will recognize that other types of displays (e.g., textual, numerical, or graphical) can be utilized and are fully within the scope of the present disclosure as the achievement display 4905. Also, while the illustrated graphical element is in the form of a round circle or ring with gradient coloring, one skilled in the art will recognize that other geometric shapes, colors, and numbers of segments and gradients can be employed and are fully within the scope of the present disclosure.

[0123] In some embodiments, as shown most clearly in FIG. 4K-1, daily scorecard 4951 can further include a selectable information icon 4907 that, when selected by the user, can output a daily score information screen 4950 (FIG. 4L) for daily scorecard 4951. For example, as shown in FIG. 4L, daily score information screen 4950 provides detailed information about how achievement indicators 4905 and daily score values ​​4904 are visually represented in daily scoring 4903. In some embodiments, daily score information screen 4950 also notifies the user that the daily score is calculated each day and resets at a predetermined time (e.g., midnight).

[0124] In some embodiments, as shown in FIG. 4K-2, the daily scorecard 4951 may further include a message 4906 indicating to the user their daily score at the end of a particular day (e.g., "You reached 87 points!"). Additionally, as shown most clearly in FIG. 4K-2, in some embodiments, the logbook section 4958 may also include a list 4952 of meal events 4959 in place of one or more TOD cards.

[0125] FIG. 4K-3 further illustrates the home GUI 495 after the user first uses the TIR application and before meal entry. The home GUI 495 illustrated in FIG. 4K-3 includes a test substance graph card 4911 without a test substance trend line. In some embodiments, the home GUI 495 before the user enters a meal into the TIR application also includes a logbook section 4958 without a list of entered meal events. According to another aspect of the embodiment, as best shown in FIG. 4K-3, a notification card 4908 is displayed on the home GUI 495 in place of the daily scorecard. Specifically, the notification card 4908 may notify the user that they can enter a meal into the TIR application by performing a predetermined action (e.g., tapping) on ​​a “+” icon 4957.

[0126] In some embodiments, as shown most clearly in FIG. 4K-3, home GUI 495 may further include a text representation 4933 indicating the current day of the week. Text representation 4933 includes a date and is adjacent to a switch 4934 configured to be toggled. In some embodiments, home GUI 495 may be a home GUI related to a past day, in which case text representation 4933 includes the date associated with the past day (e.g., "Friday, February 11th"). Note that, although not shown, in some embodiments, when home GUI 495 is a home GUI related to a past day, home GUI 495 may further include a selectable "Go to today" link that, when selected, may output home GUI 495 corresponding to the current day.

[0127] 4M-1 and 4M-2, block diagrams illustrating further exemplary embodiments of a home GUI 499 of the TIR application are shown. In some embodiments, the home GUI 499 can include (1) a meal assessment average card 4991, (2) a analyte graph card 4910, (3) a logbook section 4998, (4) a selectable home icon 4995, (5) a selectable analysis results icon 4994, and (6) a "+" icon 4997. The logbook section 4998 can include a list 4992 of meal events 4999. A user can select the home icon 4995 to output the home GUI 499. A user can select the "+" icon 4997 to output a meal logging GUI 500 (see, e.g., FIGS. 5A-5G ) configured to accept user input of meal information.

[0128] In some embodiments, as shown most clearly in FIG. 4M-1 , home GUI 499 may further include a text representation 4973 indicating the current day of the week. Text representation 4973 includes a date and is adjacent to a switch 4974 configured to be toggled. In some embodiments, home GUI 499 may be a home GUI related to a past day, in which case text representation 4973 includes the date associated with the past day (e.g., "Friday, February 11th"). Note that, although not shown, in some embodiments, when home GUI 499 is a home GUI related to a past day, home GUI 499 may further include a selectable "Go to today" link that, when selected, may output home GUI 499 corresponding to the current day.

[0129] Additionally or alternatively, as shown in FIGS. 4M-1 and 4M-2, each meal event 4999 can include a rating (score) 4922 for a particular meal. The rating (score) 4922 can be a rating (score) based on an analyte response (e.g., glucose response) associated with the particular meal. In some embodiments, the analyte response can be based on the change in analyte level (e.g., glucose level) within a predetermined time period after consuming the particular meal. In some embodiments, the score 4922 assigned to the meal is based on the change in analyte level from the glucose level at the time of consuming the particular meal to the peak glucose level within three hours after eating.

[0130] Additionally, score 4922 may be displayed numerically. In some embodiments, score 4922 may be a number between 1 and 5, with a higher assigned number representing a smaller analyte response and a lower assigned number representing a larger analyte response.

[0131] For example, (1) if the change in test substance level two hours after a meal is between 0 and 20 mg / dL, score 4922 can be set to "5," (2) if the change in test substance level two hours after a meal is between 21 and 40 mg / dL, score 4922 can be set to "4," (3) if the change in test substance level two hours after a meal is between 41 and 60 mg / dL, score 4922 can be set to "3," (4) if the change in test substance level two hours after a meal is between 61 and 90 mg / dL, score 4922 can be set to "2," and (5) if the change in test substance level two hours after a meal is 91 mg / dL or more, score 4922 can be set to "1." As another example, (1) if the change in analyte level three hours after a meal is between 0 and 24 mg / dL, score 4922 can be assigned a score of 5, (2) if the change in analyte level three hours after a meal is between 25 and 49 mg / dL, score 4922 can be assigned a score of 4, (3) if the change in analyte level three hours after a meal is between 50 and 74 mg / dL, score 4922 can be assigned a score of 3, (4) if the change in analyte level three hours after a meal is between 75 and 99 mg / dL, score 4922 can be assigned a score of 2, and (5) if the change in analyte level three hours after a meal is greater than or equal to 100 mg / dL, score 4922 can be assigned a score of 1. Those skilled in the art will recognize that other types of changes in analyte level can be used and assigned different scores and are fully within the scope of the present disclosure.

[0132] Furthermore, according to another aspect of the embodiment, the home GUI 499 is similar to the home GUI 430 (e.g., as shown in FIG. 4E-1 ), except that a meal rating average card 4991 is displayed instead of the TIR card. Specifically, according to one aspect of the embodiment, as shown in FIGS. 4M-1 to 4M-3 , the meal rating average card 4991 includes a meal rating average 4920 and a graphical representation 4921 corresponding to the meal rating average 4920. The meal rating average 4920 may be displayed numerically. More specifically, the meal rating average 4920 is an average of the scores 4922 of all scored meal events 4999 during a given period (e.g., a particular day). Alternatively, the meal rating average 4920 may be a score based on the average of the scores 4922 of multiple scored meal events 4999 over a given time period (e.g., the average of all scored meal event scores for a particular type of meal, such as the average of the scores 4922 for all scored breakfasts). In some embodiments, as shown most clearly in FIGS. 4M-1 through 4M-3, the meal rating average 4920 may be a number between 1 and 5, with higher numbers representing lower average test substance responses and lower numbers representing higher average test substance responses. In some embodiments, the meal rating average 4920 is displayed as a number with one or more decimal places (e.g., a meal rating average of "5.0").

[0133] For example, if one meal event 4999 is logged on a particular day and that meal event 4999 is assigned a score 4922 of "5," the meal rating average displayed by the meal rating average card 4991 will be "5" or "5.0." Furthermore, if two meal events 4999 are logged on a particular day, with the first meal event 4999 assigned a score 4922 of "5" and the second meal event 4999 assigned a score 4922 of "1," the meal rating average 4920 will be "3" or "3.0," which is the average of the scores 4922 of the two meal events 4999 (this case is shown in FIG. 4M-1). In some embodiments, if a user logs two meal events 4999 but only one of them is assigned a score, only the meal event 4999 with a score is included in the calculation of the meal rating average 4920, as shown in FIG. 4M-2. In some embodiments, the meal rating average 4920 is configured to be constantly updated automatically so that all meal events 4999 that have been scored over a given period of time are taken into account in the meal rating average 4920 calculation.

[0134] As shown most clearly in FIGS. 4M-1 through 4M-3, according to another aspect of the embodiment, the meal rating average card 4991 can further include a graphical representation 4921 of the meal rating average 4920. Specifically, the graphical representation 4921 can include a meal rating average display 4923 that visually represents the meal rating average obtained over a predetermined period of time (e.g., a particular day). In some embodiments, the graphical representation 4921 is a plurality of colored stars, where the number of colored stars is proportional to the ratio of the meal rating average 4920 to the maximum obtainable meal rating. However, one skilled in the art will appreciate that other graphical representations or symbols (e.g., emojis, trophy icons, bars, triangles, squares, circles, etc.) can be used in place of star icons for the graphic representation 4921 and the meal rating average display 4923 without departing from the scope of the present disclosure.

[0135] In some embodiments, as shown most clearly in FIG. 4M-3, if meal rating average 4920 is not an integer (e.g., meal rating average 4920 is "3.4"), graphical display 4921 may include at least one star with a half-filled color portion. For example, if meal rating average 4920 is "3.4," three of the five stars in graphical display 4921 may be displayed with a fully filled color portion and one of the five stars may be displayed with a half-filled color portion, as shown in FIG. 4M-3.

[0136] According to one aspect of the embodiment, the meal rating average 4920 is provided only after the user has earned their first score for a logged meal event 4999 in a given time period. In some embodiments, as shown in FIG. 4M-4, a notification card 4924 is displayed immediately adjacent to and proximal to the test substance graph card 4910, informing the user that their first meal can be added via the "+" icon. Also, although not shown, in some embodiments, a notification card is displayed immediately adjacent to and proximal to the meal rating average card, informing the user that their first meal rating (meal score) has been achieved and that they can tap on the particular meal event to which a score has been assigned for further details. Additionally, in some embodiments, a banner 49001 may be displayed on the test substance graph card 4910, as shown in FIG. 4M-4. Banner 49001 indicates that the user can tap on test substance trend line 49015 to display test substance readings (e.g., glucose readings) or swipe horizontally to scroll test substance graph 49011.

[0137] 4M-5, in some embodiments, if the user deletes all scored meals, or if the user has not received a meal rating average for a predetermined period (e.g., the day), or if there have been no scored meal events in the predetermined period, the meal rating average card 4991 does not display the meal rating average, and the multiple stars in the graphical display 4921 corresponding to the meal rating average are all white stars with no color. Also, in some embodiments, if the user deletes all scored meals, or if there have been no scored meal events in the predetermined period, a hint 4925 (see, e.g., FIG. 4M-5) is displayed in the meal rating average card 4991. Specifically, as shown in FIG. 4M-5, the hint 4925 may notify the user that the meal rating average 4920 will be available once the user logs a meal and obtains the first meal rating for the predetermined period (e.g., the day). In some embodiments, when the user logs their first meal or hides the tip 4925 (e.g., by tapping the "Done" button), the tip 4925 is removed from the meal rating average card 4991 and will no longer be displayed.

[0138] 4M-6, in some embodiments, if the user has not received a meal rating average for a predetermined period (e.g., that day), no meal rating average is displayed on meal rating average card 4991, and all of the stars in graphical display 4921 are white stars with no color. Furthermore, in some embodiments, if the user has not received a meal rating average for a predetermined period (e.g., that day), a message 4926 (e.g., "Meal ratings for this day have not been released.") is displayed on meal rating average card 4991 to inform the user that meal ratings for this predetermined period have not been released.

[0139] In some embodiments, as shown in FIGS. 4M-1 through 4M-4 and 4M-6, meal rating average card 4991 includes an information icon 4927. When information icon 4927 is selected, meal rating average modal display 4990 (FIG. 4N) is output. Specifically, as shown in FIG. 4N, meal rating average modal display 4990 may inform the user that the meal rating average is based on all of the user's food logs with ratings during a predetermined time period (e.g., from midnight to 11:59 PM the following day). Furthermore, meal rating average modal display 4990 may inform the user that new meal ratings (meal scores) within the predetermined time period (e.g., within the day) may change the user's meal rating average.

[0140] With particular reference to FIGS. 4M-1 through 4M-3, according to another aspect of some embodiments, one or more meal icons 49014 can be displayed on the analyte trend line 49015. In some embodiments, the one or more meal icons 49014 can be displayed near, adjacent to, or proximal to the analyte trend line 49015, or along the x-axis, the top of the graph window 49904, or the bottom of the graph window 49904. Furthermore, in some embodiments, the one or more meal icons 49014 can be displayed with or without a leader line. Each meal icon 49014 can be a photo or image associated with a particular meal. In some aspects of the embodiments, the meal icons 49014 are positioned on the analyte trend line 49015 to allow a user to visually associate the meal with the analyte trajectory after that meal. Additionally, in some embodiments, the meal icons 49014 are positioned on the analyte trend line 49015 based on the time of day associated with the meal. For example, if meal event 4999 indicates that blueberry oatmeal was eaten at 8:04 AM, meal icon 49014 corresponding to blueberry oatmeal meal event 4999 will be displayed at a position on the x-axis of test substance graph 49011 corresponding to approximately 8:04 AM.

[0141] It will be appreciated by those skilled in the art that the GUIs (or portions thereof) described herein are intended to be illustrative only, and that individual elements or any combination of elements shown or described in a particular embodiment or figure may be freely combined with other elements or any other combination of elements shown or described in any other embodiment.

[0142] Exemplary Meal Logging GUI Embodiment 5A-5N, exemplary embodiments of meal logging interfaces and their associated features will now be described. Referring first to FIG. 5A, a meal logging GUI 500 is displayed when a user selects a "+" icon on any GUI embodiment described herein that includes a "+" icon. In some embodiments, the TIR application may prompt the user to log a meal, for example, when a meal event is detected or when a predetermined time period has passed. A user of the TIR application may also log a meal voluntarily rather than being prompted by the TIR application. As shown in FIG. 5B, if a user wishes to add a meal voluntarily, the user may select an add meal option, for example, by tapping the "+" icon on any GUI embodiment described herein that includes a "+" icon, thereby causing the meal logging GUI 500 to appear. As shown in FIGS. 5A and 5B, the meal logging GUI 500 may include a meal entry input field 501. The meal entry input field 501 allows the user to enter the name and description of the food to be included in the meal entry. As a user types a meal name (food name) into the meal entry input field 501 (FIG. 5B), the TIR application can automatically suggest entries based on the user's previously entered meal entries. For example, in some embodiments, the TIR application can obtain information about historical meal entries with the same (or similar) food name and display this in the results section 502 (e.g., as a list of meal event history 503). When the desired food name appears in the results section 502, the user can select that meal entry. This is convenient for the user because they do not need to type the entire food or meal name.

[0143] Note that while FIG. 5B illustrates the results section 502 in a list format, one skilled in the art will appreciate that other interfaces may be implemented. For example, by manually entering text, selecting a meal name from a list (e.g., a selection list or drop-down list), selecting a photo of the meal from a collection of photos, selecting an easily recognizable meal indicator (e.g., a tag), or any combination thereof. In some embodiments, the results section may also display a score information icon 522. Selecting the score information icon 522 outputs a meal score information modal display that includes information about various score options and how the meal score is determined.

[0144] According to another aspect of the embodiment, if no meal history is recognized from the meal information being entered, a message indicating that no meal history was found may be displayed in the results section 502, as shown in FIG. 5D. If new meal information is entered, the user may select a "Continue" button 504 to display a modal display 510. The modal display 510 may be configured to request additional information, as shown in FIG. 5E, for example. The user may edit the meal entry as needed. For example, a pencil icon 505 may be displayed next to the meal name (food name) in the meal entry description 506, which the user may click.

[0145] The modal display 510 may include a portion size indicator 511 option indicating the relative amount of food consumed, and may include selectable buttons indicating different meal sizes, such as "small," "medium," and "large." The user may also add a food photo (image) 512 to associate with the meal. For example, the modal display 510 may include a camera icon 513. Selecting or tapping the camera icon 513 activates the camera of a device on which the Time In Range (TIR) ​​application is installed, allowing the user to take a photo of the food or select a photo from their photo library. Additionally, the modal display 510 may include a meal tag entry 514. The meal tag entry 514 allows the user to type one or more meal tags 515 to associate with the consumed meal. The meal tags 515 may be keywords that designate or describe one or more ingredients of the meal and / or characteristics of the meal or additional ingredients consumed with the meal. For example, meal tags 515 may relate to specific contents of a meal or side dishes consumed with a meal, and the type of food (e.g., carrots, lettuce, blueberries, cheese, bananas, french fries) may be listed on meal tags 515. For example, as shown in Figure 5F, the meal tag for "carrots" is selected. Once the user has finished entering the meal information, they may click "Save" 516 to log the meal information.

[0146] Additionally, in some embodiments, modal display 510 includes a time field 517 that includes the time and date associated with the meal entry. In some embodiments, time field 517 may be automatically associated with the meal entry or may be auto-populated based on the time the user selects the "Continue" button 504 (e.g., FIG. 5D). According to an aspect of some embodiments, the auto-populated time field 517 may also be editable by the user, as shown in FIG. 5G.

[0147] According to another aspect of the embodiment, as shown in FIG. 5C , when a user selects a meal that has been previously entered, a meal entry can be automatically entered with the current date and time assigned to the meal history information. Furthermore, as shown in FIG. 5C , a meal entry entry modal display 520 (sometimes referred to as a meal entry input modal window) is displayed, including a time field 527 with the current date and time and information associated with the meal event history 503. The user can edit the meal entry as needed. The user can edit the meal name by clicking the pencil icon 525 displayed next to the meal name. The user can also edit the meal entry to add a meal name. The user can also select the camera icon 531 to edit the image 532 associated with the meal entry. The user can also edit the meal tag 533 associated with the meal event history 503. The user can click “Add Meal” 535 to record the information in the log.

[0148] Referring now to FIG. 5H, a block diagram illustrating an example embodiment of modal display 530 is shown. Note that modal display 530 is similar to modal display 510 (FIG. 5E), except that no photo (image) associated with the meal is displayed. In some embodiments, as shown in FIG. 5H, if no photo (image) has been associated with the meal by the user, a placeholder image 534 is displayed instead. Like modal display 510, modal display 530 may also include a camera icon 536. Selecting or tapping camera icon 536 launches the camera of the device on which the TIR application is installed, allowing the user to take a photo of the food or select a photo from their photo library.

[0149] 5I-5N are various block diagrams illustrating example embodiments of a camera interface or related functionality. Any of these embodiments may be used with the embodiments described herein. Referring to FIG. 5I, a camera GUI 540 is shown that may be displayed after a user selects camera icon 513 (FIG. 5E) or camera icon 531 (FIG. 5H) on the interface embodiments described above. In some embodiments, the device's camera is unavailable until the user grants the TIR application permission to access the camera. The camera GUI 540 may relate to enabling camera access. In some embodiments, the camera GUI 540 may include a modal display prompting the user to enable camera access.

[0150] In some embodiments, photos stored on the device are not available to the TIR application until permission is granted by the user. FIG. 5J is a block diagram illustrating an example embodiment of a camera GUI 550 for enabling photo access. In some embodiments, the camera GUI 550 may include a modal display prompting the user to enable photo access. In one aspect of the embodiment, the user may allow access to selected photos. In another aspect of the embodiment, the user may allow access to all photos. In yet another aspect of the embodiment, the user may prohibit access to photos.

[0151] Figure 5K is a block diagram illustrating an example embodiment of a camera GUI 560 that includes a clear indication that camera access is prohibited. Figure 5L is a block diagram illustrating an example embodiment of a camera GUI 570 that includes a clear indication that the device's camera is unavailable.

[0152] FIG. 5M is a block diagram illustrating an example embodiment of a camera GUI 580 for taking or selecting a photo, and FIG. 5N is a block diagram illustrating an example embodiment of a camera GUI 590 for taking or selecting a photo. Referring to FIG. 5M, in some embodiments, the camera GUI 580 may include a "Retake" button. When a user selects the "Retake" button, the previously taken photo is deleted and the user may retake a photo to associate with a particular meal. In some embodiments, the camera GUI 580 includes a "Use This Photo" button. When a user selects the "Use This Photo" button, the user may use the taken photo and associate it with a particular meal. Additionally, FIG. 5N illustrates an example embodiment of the camera GUI 590 with a photo displayed. In some embodiments, the camera GUI 590 includes a "Library" button. When a user selects the "Library" button, the user may browse photos stored on the device. In some embodiments, the camera GUI 590 further includes a "Skip" button. When a user selects the "Skip" button, the user may skip using the photo displayed in the camera GUI 590.

[0153] Exemplary embodiments of report GUIs and related methods An exemplary embodiment of a method for outputting a report GUI will now be described. Specifically, FIG. 6A illustrates steps of a process-implemented method 6000 for a report GUI that displays data indicative of analyte levels and related non-medical statistics for a particular day. It should be noted at the outset that those skilled in the art will recognize that the method steps described herein may be implemented by software instructions stored in memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of system 100, and thus, when executed by one or more processors of the computing device, the instructions may cause the one or more processors to perform any or all of the method steps described herein. Returning to FIG. 6A , the method for the report GUI may include step 6001 receiving a seventh predetermined input (e.g., a tap or press) from a user on a toggle switch adjacent to a textual representation of the current day of the week on the interface. In one aspect of the embodiment, the displayed interface is configured to display a plurality of selectable rings when the user toggles the toggle switch down, each of which is a TIR representation corresponding to a different day of the past week. For example, in some embodiments, seven selectable rings are displayed on the displayed interface.

[0154] Additionally, the method for the report GUI further includes a step 6002 in which the user selects a particular ring from a plurality of rings (each of the plurality of selectable rings being a TIR display corresponding to a different day in the past week) that are displayed in response to the user switching a toggle switch.

[0155] Then, in step 6003, at least one processor identifies a set of data indicating test substance levels and dietary information associated with the day corresponding to the selected ring based on data stored in the database.

[0156] Then, in step 6004, an interactive report GUI configured to display a set of data indicative of analyte levels and dietary information based on the identifying step is provided on a display device. The report GUI may display a TIR card, an analyte graph card reflecting data indicative of analyte levels for a time period corresponding to the selected ring, a diet summary reflecting dietary information for a time period corresponding to the selected ring, or any combination thereof. Those skilled in the art will recognize that any one or more of the method 4000 (FIG. 4A-1) in its entirety or individual steps can be combined with or implemented as part of the method 6000 shown in FIG. 6A. Similarly, those skilled in the art will recognize that any one or more of the method 4100 (FIG. 4A-2) in its entirety or individual steps can be combined with or implemented as part of the method 6000 shown in FIG. 6A.

[0157] As noted above, those skilled in the art will recognize that the method steps described herein may be comprised of instructions (e.g., software, firmware, etc.) stored in non-transitory memory, and that such instructions may be stored in non-transitory memory of sensor control device 102, or reading device 120, or any other computing device or system that is part of or in communication with analyte monitoring system 100. Furthermore, the method steps described herein may be performed on a single centralized device or on multiple devices.

[0158] Referring now to FIG. 6B-1 , a block diagram illustrating an exemplary embodiment of a report GUI 600 for the TIR application is shown. As described above, the report GUI 600 may be displayed in response to a user selecting a particular ring from among multiple rings 425 displayed in the home GUI 400 or home GUI 450. Specifically, as shown in FIG. 6B-1 , the report GUI 600 corresponding to the day associated with the selected ring 425 is displayed. The report GUI 600 may include: (1) a TIR card 601; (2) an analyte graph card 602; (3) a meal information list 603; (4) a selectable “Daily Summary” icon 605; (5) selectable meal icons 606; (6) a “+” icon 607; or any combination thereof. The analyte graph card 602 may reflect data indicating analyte levels and meal information corresponding to the particular day associated with the selected ring 425. The meal information list 603 may include one or more meal events 604. A user may select the "Daily Summary" icon 605 to output a report GUI 600 for that day. A user may select the Meals icon 606 to output a Meal Load GUI 650 (not shown in FIG. 6B-1 ) containing information about one or more meal events 604 that occurred in a past period (e.g., the past week). A user may select the "+" icon 607 to output a Meal Log GUI 500 ( FIG. 5A ) configured to accept meal information input by the user.

[0159] According to some aspects of the embodiment, multiple rings 425, each corresponding to a different day of the week, are displayed adjacent to and proximal to the TIR card 601. In some embodiments, only the particular ring 425 corresponding to the currently displayed report GUI 600 is highlighted, bolded, or colored to indicate that the currently displayed report GUI 600 is associated with that particular ring 425. According to another aspect of the embodiment, a user can toggle the display of a report GUI 600 corresponding to a particular day by selecting a ring from the multiple rings 425 associated with that day. Additionally, in some embodiments, the report GUI 600 can include a "Go to today" link 608 that, when selected, can output the home GUI 400 containing data corresponding to the current day or the report GUI 600 corresponding to the current day.

[0160] The TIR card 601 displayed on the report GUI 600 includes a TIR ring 612 within which a TIR value 611 is displayed. In some embodiments, as shown in FIG. 6B-1 , the TIR value 611 may include a numeric value and units (e.g., “15 hours”) indicating the number of hours the user spent in the predetermined target range for TIR measurement on that day. The number of hours spent in the target range for TIR measurement may also be visually displayed as a reach indicator 618 (e.g., a darker area) along the periphery of the TIR ring 612, extending to X% of the circumference of the TIR ring 612. In this case, the percentage of the circumference of the TIR ring 612 that includes the reach indicator 618 is proportional to the percentage of the user's time in the target range for TIR measurement that accounts for the predetermined daily TIR target 617 for that day. In some embodiments, the TIR card further includes a message 635 regarding the user's daily TIR target 617. In some embodiments, the TIR card 601 further includes a daily TIR goal 617 indicating a predetermined TIR goal (e.g., "10 hours"), which may be displayed below a message 635 regarding the user's daily TIR goal 617.

[0161] Continuing with reference to FIG. 6B-1, similar to the home GUI 450 described above, the analyte graph card 602 of the report GUI 600 can include an analyte graph 630 having an analyte trend line 631 reflecting the user's analyte levels over a period of time based on data indicating analyte levels. For example, as shown in FIG. 6B-1, the x-axis of the analyte graph 630 can represent time (e.g., in 3-hour increments) and the y-axis can represent the user's analyte concentration measurements (e.g., in mg / dL), with the x-axis representing a 24-hour period. For example, as shown in FIG. 6B-1, the x-axis can begin at midnight of the current day and display glucose concentration measurements from that time onward.

[0162] Analyte graph 630 may include lines 632-1 and 632-2 that indicate a user's target analyte range associated with the data indicating the analyte level. For example, the area between lines 632-1 and 632-2 indicates the target analyte value range (e.g., a range of 70 mg / dL to 180 mg / dL). In some embodiments, as shown in FIG. 6B-1 , analyte trend line 631 corresponding to the time period during which the user's analyte level exceeded the target analyte range for the TIR is represented by a dotted or dashed line. Furthermore, analyte trend line 631 corresponding to the time period during which the user's analyte level was within the target analyte range is represented by a solid line. As noted above, the target analyte range for the TIR can be user-configurable.

[0163] 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 particular meal. In some aspects of the embodiment, the meal icons 633 are positioned on the analyte trend line 631 to indicate the post-meal analyte trajectory associated with that meal. Additionally, in some embodiments, the meal icons 633 are positioned on the analyte trend line 631 based on the time of day associated with the meal.

[0164] Continuing with reference to FIG. 6B-1 , like the home GUI 400 and the home GUI 450, the report GUI 600 can also include a meal information list 603. The meal information list 603 can include one or more meal events 604 that occurred on the relevant day listed in the report GUI 600. Each meal event 604 provides detailed information about a specific meal consumed on that day. In some embodiments, similar to the GUI embodiments described above, each meal event 604 can include a textual description 640 of the meal, a portion size indicator 641 indicating the relative portion size, a timestamp 642 associated with the time the meal was consumed, a score 643, or any combination thereof. In some embodiments, the score 643 corresponding to a particular meal event 604 can be displayed numerically within a star icon 644. Note that, although not shown, in some embodiments, a meal event 604 can also include one or more meal tags 645 associated with the meal. Additionally or alternatively, a meal event 604 can also include a photo (image) 646 associated with the meal. In some embodiments, if a meal has not had a photo (image) 646 associated with it by the user, a placeholder image 646 is displayed instead. In some exemplary embodiments, the list 603 may be ordered such that the meal event 604 corresponding to the most recently eaten meal is displayed first, i.e., at the top of the list 603, with subsequent meal events 604 displayed in chronological order. In some embodiments, a score information icon 648 is displayed on the report GUI 600 adjacent to and proximal to the meal card. When the user selects the score information icon 648, a meal score information modal display is output that includes information about various score options and how the meal score is determined.

[0165] Referring now to FIG. 6B-2, a block diagram illustrating a report GUI 625 of another exemplary embodiment of a TIR application is shown. Note that the report GUI 625 illustrated in FIG. 6B-2 is similar to the report GUI 600 illustrated in FIG. 6B-1, except that it includes a selectable home icon 626 instead of the selectable "Daily Summary" icon 605 (FIG. 6B-1). Additionally, the report GUI 625 includes multiple rings 627, each corresponding to a different day of the week. Similar to the multiple rings 425 illustrated in the report GUI 600, each ring in the report GUI 625 represents the user's progress toward their daily TIR goal for that particular day. However, the report GUI 625 may visually indicate the user's TIR hours for a particular day by using a color gradient for a corresponding particular one of the multiple rings 627. For example, in some embodiments, as illustrated in FIG. 6B-2, the color gradient for a particular one of the multiple rings 627 may indicate the amount of time the user spent within their goal range for the particular day associated with that ring.

[0166] Exemplary Embodiment of Food Load GUI An exemplary embodiment of a food load GUI for an analyte monitoring system will now be described. FIG. 7 is a block diagram illustrating an exemplary embodiment of a food load GUI 700 for use in an analyte monitoring system. As shown in FIG. 7, the food load GUI 700 can provide a user with further insight into the load caused by the intake of specific foods. In some embodiments, the food load GUI 700 can provide information about meals over a specific period of time (e.g., the past seven days) and data indicative of analyte levels.

[0167] According to one aspect of the embodiment, the meal load GUI 700 includes (1) a meal highlight card 701, (2) a meal information list 702, (3) a selectable home icon 705, (4) a selectable meal icon 706, and (5) a selectable "+" icon 707. The meal information list 702 includes meal events 703 ranked according to scores 704 assigned based on the recorded test substance responses corresponding to the meal events. The meal load GUI 700 can be accessed from the meal icon 706 or from the meal icons mentioned in the description of other GUI embodiments described herein. The meal load GUI 700 can list all logged meal events 703 for a given period (e.g., one week). The meals in the meal list 702 can be ordered from highest score 704 to lowest score 704 or from lowest score 704 to highest score 704. The scores 704 are assigned according to the test substance responses based on data indicating the user's test substance levels. In some embodiments, if two or more meals have the same score 704, they may be ordered in the meal list 702 according to their analyte level fluctuation value. For example, if two meals have a score 704 of "3," they may be ordered from smallest PeakDelta value (analyte level fluctuation value) to largest PeakDelta value (analyte level fluctuation value). Additionally, in some embodiments, if two or more meals have the same score 704 and the same analyte level fluctuation value, they may be ordered chronologically.

[0168] In some embodiments, the analyte response for each meal can be based on the change in analyte level within a predetermined time period after consuming that particular meal, and in some embodiments, the score 704 assigned to a meal event 703 is based on the change in analyte level from the glucose level at the time of consuming that particular meal to the peak glucose level within three hours after eating.

[0169] In some embodiments, score 704 may be a number ranging from 1 to 5, with higher numbers representing smaller analyte responses and lower numbers representing larger analyte responses. For example, as detailed above, (1) if the change in analyte level at 3 hours postprandial is between 0 and 24 mg / dL, score 704 may be a "5," (2) if the change in analyte level at 3 hours postprandial is between 25 and 49 mg / dL, score 704 may be a "4," (3) if the change in analyte level at 3 hours postprandial is between 50 and 74 mg / dL, score 704 may be a "3," (4) if the change in analyte level at 3 hours postprandial is between 75 and 99 mg / dL, score 704 may be a "2," and (5) if the change in analyte level at 3 hours postprandial is 100 mg / dL or greater, score 704 may be a "1." As shown in the meal load GUI 700, the score 704 may be represented by a graphical element such as a star icon 711. In some embodiments, the star icon 711 may be filled with a color, such as yellow. Additionally, in many embodiments (not shown), the star icon 711 may be a hollow star with a dashed outline to indicate a meal score 704 of "no score." In some embodiments, a meal score 704 of "no score" is indicated by the character "?", as shown in FIG. 7. In some embodiments, the star icon 711 may be filled with the character "?" instead of a numeric value to indicate that a particular meal was not assigned a score. Meal score 704 will be "No Score" if (1) the user logs the next meal too early, or (2) the TIR (Time In Range) application does not have enough test substance data to score the meal (e.g., the user did not scan at the appropriate time and therefore did not receive confirmation that the glucose data was sent to the TIR (Time In Range) application), or if both (1) and (2) occur.

[0170] According to one aspect of the embodiment, the meal highlight card 701 is configured to display information about meal events 703 that occurred within a predetermined time period (e.g., the past week). Specifically, the meal highlight card 701 includes a title 720 titled "Best Meal Last 7 Days" and displays information about meal events 703, including "best meal." In some embodiments, the best meal is defined by the meal event 703 with the highest score within the predetermined time period. In some embodiments, the best meal is defined by the meal event 703 with the most desirable test substance response within the past 7 days based on data indicating test substance levels. In some embodiments, the meal highlight card 701 includes a textual representation 721 of the best meal and a star icon 722 containing a score 724 assigned to the best meal. Additionally, the meal highlight card 701 may also include a photo (image) 725 associated with the optimal meal, with a text notation 721 and a star icon 722 overlaid on top of the photo (image) 725 so as to obscure a portion of the photo (image) 725.

[0171] According to another aspect of the embodiment, each meal event 703 listed in the food load GUI 700 provides detailed information about a specific meal consumed within a predetermined time period (e.g., a one-week period). In some embodiments, each meal event 703 may include a textual description 731 of the meal, a photo (image) 739 associated with the meal, a portion size indicator 732 indicating the relative portion size, a timestamp 733 associated with the time the meal was consumed, a score 734 associated with the meal, or any combination thereof. Additionally or alternatively, in some embodiments, the meal event 703 may also include one or more meal tags 735 associated with the meal (e.g., “lettuce,” “blueberries,” “cheese,” “banana,” “fries,” etc.). In some embodiments, an informational message 736 is displayed proximal to the list 702 informing the user that a higher score 704 indicates a higher likelihood of staying within the target analyte range for the TIR.

[0172] 7, the meal load GUI 700 may further include a score information icon 742. In some aspects of the embodiment, each meal event 703 is selectable and, when selected by the user, outputs a meal review GUI 800 (not shown) that provides detailed information about the selected meal event 803, as will be described in more detail below.

[0173] Exemplary Embodiment of a Meal Review GUI Next, an exemplary embodiment of a meal review GUI for an analyte monitoring system and other related features will be described. FIG. 8 is a block diagram illustrating an exemplary embodiment of a meal review GUI 800 for use in an analyte monitoring system. As shown in FIG. 8, the meal review GUI 800 can provide a user with further analysis of the burden of ingesting specific foods. As shown in FIG. 8, a user can select a meal event from a list on the report GUI 600, the meal burden GUI 700, the home GUI 400, the home GUI 450, the home GUI 430, the home GUI 485, the home GUI 495, or the home GUI 499. When a user selects a meal event, the meal review GUI 800 can open and display detailed information about the meal event 803. Such detailed information can include a photo (image) 805, a text description 801, a portion size indication 802, a meal tag 804, a timestamp 806 including a date and time associated with the meal, a score 807, an analyte graph card 810, or any combination thereof. The analyte graph card 810 includes an analyte graph 811 having an analyte trend line 812 containing data showing analyte levels over a period of time that includes at least the time of meal intake. Although not shown in Figure 8, in some embodiments, the analyte graph card 810 can include a selectable information icon that, when selected, outputs the analyte graph information modal display 445, as shown in Figure 4G.

[0174] Specifically, the meal review GUI 800 includes a meal description card 820 that includes a text description 801, a portion size indication 802, a meal tag 804, and a timestamp 806 associated with the meal. Additionally, a score 807 is displayed as a star icon 830 located proximal to the meal's text description 801. In some embodiments, as shown in FIG. 8 , the meal description card 820 is displayed so as to obscure a portion of a photo (image) 805 associated with the meal.

[0175] Continuing with reference to FIG. 8 , similar to the analyte graph cards of the GUI embodiments described above, the analyte graph card 810 of the meal review GUI 800 can also include an analyte graph 811 having an analyte trend line 812 reflecting the user's analyte levels over a predetermined time period based on the data indicative of the analyte levels. For example, as shown in FIG. 8 , the x-axis of the analyte graph 811 can represent time (e.g., in hourly increments) and the y-axis can represent the user's analyte concentration measurements (e.g., in mg / dL), with the length of the period displayed on the x-axis representing the predetermined time period. The analyte graph card 810 can include lines 813-1 and 813-2 indicating the user's target analyte range associated with the data indicative of the analyte levels. For example, the area between lines 813-1 and 813-2 indicates the target analyte value range (e.g., a range of 70 mg / dL to 180 mg / dL). In some embodiments, analyte trend line 812 corresponding to the time periods during which the user's analyte levels were above the target analyte range for the TIR is represented by a dotted or dashed line, as shown in Figure 8. Additionally, analyte trend line 812 corresponding to the time periods during which the user's analyte levels were within the target analyte range is represented by a solid line.

[0176] According to another aspect of the embodiment, meal icons 840 corresponding to meal events 803 may be displayed on the analyte value trend line 812. Each 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 icons 840 are placed on the analyte trend line 812 to show the post-meal analyte trajectory associated with that meal. Additionally, in some embodiments, the meal icons 840 are placed on the analyte trend line 812 at a location based on the time associated with the meal.

[0177] In some embodiments, the meal review GUI 800 includes analyte level statistics 850 for the meal event 803. For example, as shown in FIG. 8 , the meal review GUI 800 may include analyte level statistics for a peak analyte level 850-1 (e.g., 173 mg / dL) associated with the meal, an analyte level 850-2 (e.g., 140 mg / dL) before the meal, and an analyte level 850-3 (e.g., 95 mg / dL) after the meal. In some embodiments, the analyte level statistics 850 are displayed adjacent to and proximal to the analyte graph card 810. Thus, a user can view a visual illustration of the analyte level statistics 850 associated with the meal by referring to the analyte graph card 810. Additionally, in some embodiments, a message 860 indicating a target glucose range (e.g., "Target glucose range: 70-80 mg / dL") is displayed below the analyte graph card 810. In some aspects of the embodiments, an informational message 870 indicating that medications, activity, stress, etc. may affect glucose levels is also displayed on the meal review GUI 800. In yet another aspect of the embodiment, the meal review GUI 800 may further include a meal summary message 880. The meal summary message 880 may describe any glucose spikes associated with the meal event, statistics regarding the user's TIR, and may include a motivational message (e.g., "Glucose spike was +33 mg / dL. 3 hours after this meal, you're back in target range! Feeling great!").

[0178] Exemplary Embodiment of Onboarding GUI Additionally, the TIR application may include multiple onboarding interfaces, any of which may be utilized with the embodiments described herein. According to one aspect of an embodiment, when a user launches the TIR application, an 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 their diet contributes to their glucose levels and overall glucose management by providing them with a daily score and average dietary assessment, and tracking the time the user has spent within their target range. In some embodiments, the onboarding GUI may explain to the user that (1) the daily score provided by the TIR application is based on the meals logged by the user and the user's glucose control, and (2) the calculation of the daily score is performed daily and resets at a predetermined time each day (e.g., midnight). Additionally, in some exemplary embodiments, the onboarding GUI may explain to the user that the TIR is the length of time that a glucose level remains within a target range (e.g., between 70 mg / dL and 180 mg / dL, or between 3.9 mmol / L and 10 mmol / L), and that the longer the TIR, the greater the likelihood of achieving better health. In some exemplary embodiments, the onboarding GUI may explain to the user that (1) the TIR application helps the user track the burden that various foods place on their glucose levels and provides the user with a dietary rating average, (2) the dietary rating average is the average rating the user receives for the meals logged on a particular day, and (3) as the user continues to use the TIR application, the user will begin to understand which foods are most effective at improving the user's dietary rating average.In one aspect of the embodiment, the onboarding GUI can explain the requirements of the TIR application to the user, for example, the onboarding GUI can inform the user that they need (1) a TIR application, (2) other analyte monitoring applications, and (3) sensors.

[0179] 9A-9O are block diagrams illustrating example embodiments of onboarding GUIs. As shown in FIG. 9A, a user may utilize onboarding GUI 920 to log into their account. Next, the user may be presented with a pilot disclaimer in onboarding GUI 925, shown in FIG. 9B. In some embodiments, onboarding GUI 925 includes a confirmation button 927 (e.g., an "I Accept" button) that the user may press to confirm agreement with the TIR application terms. Next, onboarding GUI 930 (FIG. 9C) is displayed to the user. As shown in FIG. 9C, onboarding GUI 930 includes a name entry field 931 in which the user may enter a name to associate with the user's account credentials.

[0180] Next, as shown in Figure 9D, onboarding GUI 935 may present the user with an initial greeting that includes the name entered in the previous onboarding GUI 930. Additionally, onboarding GUI 935 may provide a brief description of what will be displayed in subsequent onboarding GUIs, along with an estimated time to read the content displayed in subsequent onboarding GUIs. Onboarding GUIs 940 (Figure 9E), 945 (Figure 9F), and 950 (Figure 9G) may then provide the user with further instructions introducing them to the TIR application.

[0181] In some embodiments, the onboarding GUI 940 (FIG. 9E) may provide the user with information about research showing that TIR is a simple yet powerful tool for tracking the burden that food places on glucose levels. Furthermore, with reference to FIG. 9F, the onboarding GUI 945 may inform the user that the American Diabetes Association recommends a daily TIR of 17 hours. In some embodiments, the onboarding GUI 945 may also inform the user that TIR may vary from person to person because different people experience different glucose behavior. In some embodiments, the onboarding GUI 945 may also inform the user that because glucose behavior is unique to each user, the TIR application will suggest a goal based on the user's glucose data on the first day. With reference to FIG. 9G, a block diagram illustrating the onboarding GUI 950 is shown. The onboarding GUI 950 may also inform the user that once a goal is set, the TIR ring will fill as the user's TIR accumulates, even while the user sleeps. The onboarding GUI 950 can also include a message encouraging the user to reach their goal by completing one revolution of the TIR ring by midnight each day.

[0182] Additionally, in some embodiments, an onboarding GUI may be displayed that provides a user with a brief explanation of how to log a meal in the TIR application. Additionally, in some embodiments, an onboarding GUI may be displayed that includes a link that, when selected by the user, may output a food logging information modal display that includes tips for adding meals to the TIR application. Additionally, in some embodiments, an onboarding GUI may be displayed that provides the user with information regarding the meal's rating (score). For example, although not shown, in some embodiments, the onboarding GUI may explain to the user that the TIR application rates meals based on post-meal glucose change, and that meals rated as 5 stars are those that result in the smallest increase in glucose levels, and that meals rated as 1 star are those that result in the largest increase in glucose levels.

[0183] In some embodiments, the onboarding GUI providing information about meal evaluations may include a link that, when selected, may output a meal score information modal display, as described above, containing information about how the TIR application ranks and scores meals. Additionally, in some embodiments, the meal score information modal display containing information about how meals are ranked may also include a pictogram indicating glucose load. According to some aspects of the embodiments, the meal score information modal display may include a link that, when selected by the user, may output another meal score information modal display containing more information explaining why the score is recorded three hours after the meal is consumed. Additionally, in some embodiments, the meal score information modal display containing more information explaining why the score is recorded three hours after the meal may also include tips to help the user avoid prolonged deviations from the target range. Additionally, in some embodiments, the meal score information modal display may also include more information explaining why the user should wait between meals. Additionally, this meal score information modal display includes further information about the need to log all food consumed within a 30-minute period as one meal to minimize the number of meals with a "no score" (no rating).

[0184] Additionally, in some embodiments, an informational GUI may be presented that contains detailed information explaining why a meal is "unscored." For example, this informational GUI may include one or more information cards, each describing different instances that may cause a meal to not receive a score (e.g., if the user logs the next meal too soon, or if the TIR application does not have enough glucose data to assign a score to the meal).

[0185] In another aspect of an embodiment, an onboarding GUI 965 (FIG. 9H) may be displayed. The onboarding GUI 965 may inform the user that notifications must be allowed to receive reminder notifications from the TIR application. Additionally, the onboarding GUI 965 may inform the user that notifications must be allowed to receive reminder notifications to remind the user to scan sensors to keep user data up to date. Additionally, in some embodiments, the onboarding GUI 965 may also inform the user that notifications must be allowed to receive notifications informing them that new "analysis results" are available.

[0186] Although not shown in FIG. 9H , in some embodiments, the onboarding GUI 965 may include a “Back” button that, when selected by the user, allows the user to return to the onboarding GUI that was displayed prior to the onboarding GUI 965. Further, in some embodiments, as shown in FIG. 9H , the onboarding GUI 965 may include a “Continue” button 982 that, when selected by the user, outputs a “Notifications” modal window 977. Specifically, the “Notifications” modal window 977 may include a “Don’t Allow” button 983 that, when selected by the user, allows the TIR application to deny notifications from being sent to the user. The “Notifications” modal window 977 may also include an “Allow” button 984 that, when selected by the user, allows the TIR application to allow notifications to be sent to the user. In some embodiments, as shown in FIG. 9I , the “Notifications” modal window 977 may be configured to obscure (overlay) a portion of the onboarding GUI 965 that is displayed below it, obscuring that portion from view. Additionally, in some embodiments, once the user selects the "Allow" button 984, an onboarding GUI 970 is output confirming that the onboarding process is complete (FIG. 9J).

[0187] 9K, a pop-up modal display 975 is shown. The pop-up modal display 975 includes a message indicating to the user that a particular data set (e.g., the most recent 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 display 975 also includes a message header 976 (e.g., "Welcome, [username]!") that includes the name entered by the user. The pop-up modal display 975 may also include a confirmation button ("OK" button) that the user may press. Additionally, the pop-up modal display 975 may include a congratulatory emoji.

[0188] In some embodiments, a user may set a TIR goal through an onboarding process. Specifically, as shown in FIG. 9L, an onboarding GUI 980 may be utilized to set the user's TIR goal. The onboarding GUI 980 may include a time input field 9802 through which a user may manually input a desired TIR goal in hours (h) (e.g., entering "17" hours). In another aspect of the embodiment, as shown most clearly in FIG. 9L, a percentage (%) input field 9803 may be provided through which a user may manually input a desired TIR goal in percentage (e.g., entering "70"%). Also, in some embodiments, as shown in FIG. 9L, the onboarding GUI 980 may include a selectable bar (hereinafter, "selection bar") 9801. The selection bar 9801 may be configured to update the TIR goal in response to an eighth predetermined input by the user. The eighth predetermined input may include, for example, a predetermined operation such as dragging a finger across the selection bar 9801.

[0189] In some embodiments, when the user updates the TIR goal by any means (e.g., selection bar 9801, time input field 9802, or percentage input field 9803), the onboarding GUI 980 updates to reflect the updated TIR goal in the time input field 9802 and percentage input field 9803 (e.g., 17 hours corresponds to 70%). In this manner, the onboarding GUI 980 allows the user to visually confirm the new TIR goal in both hours (h) and percentage (%). Additionally, in some embodiments, the onboarding GUI 980 may include an information section 9804. The information section 9804 informs the user that selecting a TIR goal does not lock them in, but rather that they can change it at any time in settings. Additionally, the information section 9804 may inform the user that the TIR application may suggest new TIR goals based on the user's future progress.

[0190] As shown in FIG. 9L , the user can select a “back” button 9805 to return to the previous onboarding GUI. Additionally, in some embodiments, as shown in FIG. 9L , the user can click “set goal” 9806 after entering a new TIR goal setting to save the TIR goal. In some embodiments, after the user clicks “set goal” 9806, a confirmation in-app modal display 981 (most clearly shown in FIG. 9M ) appears over the onboarding GUI 980, confirming that the user's TIR goal has been set. In some embodiments, as shown in FIG. 9L , the confirmation in-app modal display 981 includes a “confirm” button 9807 that the user can select to acknowledge the message presented in the in-app modal display 981.

[0191] 9N, an onboarding GUI 985 is shown. The onboarding GUI 985 includes information regarding the “Analysis Results” provided by the TIR application. The “Analysis Results” are described in more detail below. Specifically, the onboarding GUI 985 may include an information section 9851 that notifies the user that the TIR application can provide the user with a weekly analysis of the user's progress. Additionally, in some embodiments, the information section 9851 also notifies the user that they can view updated “Analysis Results” information by selecting a setting in the TIR application to receive notifications when new analysis results are available or by checking the “Analysis Results” tab or icon. The onboarding GUI 985 may also include a “Back” button 9852 that the user can select to return to the previously viewed onboarding GUI. The onboarding GUI 985 may also include a “Next” button 9853 that the user can select to display the next onboarding GUI.

[0192] In some embodiments, an onboarding GUI 990 (shown in FIG. 9O) is presented during the onboarding process of the TIR application. Specifically, the onboarding GUI 990 may inform the user that the TIR application collects health data (e.g., step count and sleep data) from a third-party health monitoring application, such as Apple Health, to help the user understand how it impacts the user's glucose levels. The onboarding GUI 990 may also inform the user that during the onboarding process, the user can connect to the third-party health monitoring application (e.g., Apple Health) and change settings in the "Sharing" tab of preferences within the third-party health monitoring application. In some embodiments, the onboarding GUI 990 includes a "Back" button 9901 that the user can select to display the next onboarding GUI.

[0193] In some embodiments, the onboarding GUI 990 includes a "Next" or "Continue" button 9902. When this button is selected for the first time, an onboarding GUI 995 is displayed, allowing the user to connect with a third-party health monitoring application. Specifically, the onboarding GUI 995 is displayed as shown in FIG. 9P. The onboarding GUI 995 may include "Movement Settings" 9951. The "Movement Settings" 9951 may be user-configurable and, when enabled, allow the third-party health monitoring application to share data about the user's movement (e.g., steps taken or wheelchair pushes) with the TIR application. In this manner, the TIR application may be configured to read data about the user's movement from the third-party health monitoring application to better understand the impact of the user's movement on glucose levels. Additionally, the onboarding GUI 995 may include "Sleep Settings" 9952. The "Sleep Settings" 9952 may be user-configurable and, when enabled, allow the third-party health monitoring application to share data about the user's sleep (e.g., hours slept) with the TIR application. In this case, the TIR application may be configured to read data about the user's sleep from the third-party health monitoring application to provide a better understanding of how the user's sleep impacts their glucose levels. Additionally, the onboarding GUI 995 may include a selectable "Turn All On" button 9953. When selected by the user, this button allows the TIR application to access health data about both the user's movement and sleep from the third-party health monitoring application. The onboarding GUI 995 may also include an informational message 9954. The informational message 9954 may inform the user that the TIR application will be able to read data from the third-party health monitoring application to help the user understand how factors such as the user's movement and sleep impact their glucose levels.According to another aspect of the embodiment, the onboarding GUI 995 may also include an "Allow" button 9955, which, when selected by the user, may output the onboarding GUI 965 shown in Figure 9H. In some embodiments, the onboarding GUI 995 may also include a "Don't Allow" button 9956.

[0194] Additionally, according to another aspect of an embodiment, when the user selects the "Next" or "Continue" button 9902 on the onboarding GUI 995 a second or subsequent time, a notification modal is displayed. This notification modal notifies the user that in order for the TIR application to access the third-party health monitoring application, the user must navigate to the "Sharing" tab in the third-party health monitoring application's settings (e.g., Apple Health settings) and grant access. In some embodiments, the notification modal includes an "OK" button that the user can select to indicate that they acknowledge the notification.

[0195] Although not shown, in some exemplary embodiments, the onboarding process also allows the user to configure a profile. For example, in some embodiments, an onboarding GUI may be output that includes multiple selectable options that prompt the user to enter profile information and preferred preferences. These multiple selectable options may include, for example, an age field that allows the user to enter an age range, a medical condition field that allows the user to enter whether the user has been diagnosed with a disease (e.g., type 1 diabetes, type 2 diabetes, other diseases, etc.), a diagnosis field that allows the user to enter how long ago the disease was diagnosed, a medication field that allows the user to identify whether the user is taking diabetes-related medications (e.g., long-acting / basal insulin), and a medication history field that allows the user to enter the number of diabetes-related medications the user is currently taking.

[0196] Exemplary Account and Settings GUI Embodiments 10A-10M are various block diagrams illustrating example embodiments of an "Account" interface and a "Settings" interface or their associated functionality. Any of these embodiments may be utilized in conjunction with the embodiments described herein. Referring to FIG. 10A, a settings GUI 1000 is shown. The settings GUI 1000 includes, but is not limited to, a text greeting 1001 containing a user-entered name (e.g., "Hello, Samantha!"), a text notation 1002 indicating the beginning of a time period associated with the user (e.g., "Starting Date: January 3, 2022"), an "Account" section 1003, a "Preferences" or "Settings" section 1004, and a "Help" section 1005. The text notation 1002 is displayed immediately adjacent to, but distal from, the text greeting 1001. Selecting an "About This App" section 1006 outputs information about the TIR application.

[0197] In some embodiments, as shown in Figure 10A, a selectable pencil icon 1007 is displayed next to the text greeting 1001. When the user selects the pencil icon 1007, a settings GUI 1010 (Figure 10B) is displayed that includes a name entry field 1011 that allows the user to edit the previously entered name associated with the account credentials.

[0198] Also, although not shown in Figure 10A, in some embodiments, the settings GUI may include an "Activities" section (e.g., an "Apple Health" section), which, when selected, outputs an interface related to activity settings (see, e.g., Figures 10L and 10M).

[0199] The setting GUI 1010 (FIG. 10B) also includes a "Save" button 1012, which the user can press to save the name entered in the name entry field 1011.

[0200] FIG. 10C-1 illustrates an exemplary embodiment of an account settings interface. FIG. 10C-1 illustrates an account settings GUI 1020. According to one aspect of an embodiment, the account settings GUI 1020 may be displayed when a user selects the "Account" section 1003 (e.g., in the previous settings GUI 1000 ( FIG. 10A )). According to another aspect of an embodiment, as shown in FIG. 10C-1, the settings GUI 1020 may include a "Set Target Glucose Range" 1021 and a "Set Units of Measurement" 1023. While not shown, in some embodiments, the "Set Target Glucose Range" 1021 may allow a user to set a target glucose range. In certain embodiments, as shown in FIG. 10C-1, the "Set Target Glucose Range" 1021 may be non-changeable and may be displayed for informational purposes only (e.g., to inform the user that the target glucose range is 70 mg / dL to 180 mg / dL). For example, when a user selects "Set Target Glucose Range" 1021 in settings GUI 1020, settings GUI 1030 (FIG. 10D) is output that includes information about the user's target glucose range. Other combinations of non-changeable and changeable settings are possible, and one of ordinary skill in the art will recognize that such other combinations are fully within the scope of the present disclosure.

[0201] As shown in FIG. 10C-1 , in some embodiments, the account settings GUI 1020 also includes a configurable setting, “Set TIR Goals” 1022. Additionally, although not shown, in some embodiments, the account settings GUI 1020 may also include a selectable “Send Study Data” option, which, when selected by a user, may output the “Send Study Data” GUI. The “Send Study Data” GUI may include an information section that notifies the user that information from the user’s account will be emailed to the research team to enhance the user’s experience using the TIR application. Additionally, the information section of the “Send Study Data” GUI may provide more information about the information and content of the data being sent to the research team and assure the user that no personally identifiable information (“PII”) will be shared. Additionally, the “Send Study Data” GUI may include an export information section that indicates the date the user last sent exported study data to the research team. According to one aspect of the embodiment, the “Send Study Data” GUI may include a “Submit” button 126 that, when selected by a user, outputs a study participation confirmation modal. Specifically, the study participation confirmation modal display is configured to obscure (overlap) a portion of an interface (e.g., a "Submit Study Data" GUI) that is displayed below it. In some embodiments, the study participation confirmation modal display prompts the user to confirm whether they wish to submit their data (e.g., the user's dietary data and glucose data) to the study team. In some embodiments, the study participation confirmation modal display may include a "Submit" button that, when selected by the user, will submit the user's data (e.g., the user's dietary data and glucose data) to the study team. The study participation confirmation modal display may also include a "Cancel" button that, when selected by the user, will cancel the request to submit the user's data to the study team.

[0202] Although not shown, in some exemplary embodiments, the account settings GUI 1020 (FIG. 10C-1) may also include a selectable “About You” option that, when selected by the user, will output the user information settings GUI 1035 (see FIG. 10C-2). The user information settings GUI 1035 (FIG. 10C-2) may include multiple selectable options that prompt the user to enter profile information and preferred preferences. These multiple selectable options may include, for example, an age field 1031 that allows the user to enter an age range; a medical condition field 1032 that allows the user to enter whether the user has been diagnosed with a disease (e.g., type 1 diabetes, type 2 diabetes, other diseases, etc.); a diagnosis field 1033 that allows the user to enter how long ago the disease was diagnosed; a medication field 1034 that allows the user to identify whether the user is taking diabetes-related medications (e.g., long-acting / basal insulin); and a medication history field 1036 that allows the user to enter the number of diabetes-related medications the user is currently taking. Additionally, the user information setting GUI 1035 may include a "Save" button 1037. The "Save" button 1037 is configured to be selectable only when the user makes changes to the profile information or environmental settings in the user information setting GUI 1035.

[0203] 10E-1 through 10E-3 further illustrate an exemplary embodiment of a settings GUI 1040, which is an interface related to the TIR goal. The settings GUI 1040 may be displayed if the user selects "Set TIR Goal" 1022 in the previous settings GUI 1000 (FIG. 10A). According to one aspect of the embodiment, as shown in FIGS. 10E-1 through 10E-3, the TIR goal may be user-settable and configured to allow the user to select the TIR goal. In this configuration, achievement of the TIR goal is recognized when the user's glucose values ​​remain within a predetermined target glucose range for a selected period of time (e.g., 17 hours). In some embodiments, as shown in FIG. 10E-1, the settings GUI 1040 may include a selection bar 1041. The selection bar 1041 is configured to update the TIR goal in response to a ninth predetermined input by the user. The ninth predetermined input may include, for example, a predetermined operation such as dragging a finger across the selection bar 1041.

[0204] In one aspect of the embodiment, as shown most clearly in FIG. 10E-2, a time input field 1042 is also provided, allowing the user to manually input the desired TIR target in hours (e.g., entering “17” hours). In another aspect of the embodiment, as shown most clearly in FIG. 10E-2, a percentage (%) input field 1043 is provided, allowing the user to manually input the desired TIR target in percentage terms (e.g., entering “70”). In some embodiments, when the user updates the TIR target by any means (e.g., selection bar 1041, time input field 1042, or percentage (%) input field 1043), the settings GUI 1040 is updated to reflect the updated TIR target in the time input field 1042 and percentage (%) input field 1043 (e.g., 17 hours corresponds to 70%). In this manner, the settings GUI 1040 allows the user to visually confirm the new TIR target in both hours (h) and percentage (%). In some embodiments, the settings GUI 1040 includes a message informing the user that changes to the TIR target will take effect the next day.

[0205] Continuing with reference to FIGS. 10E-1 through 10E-3, in some embodiments, the settings GUI 1040 also includes an information section 1044 that informs the user of the TIR goal recommended by the American Diabetes Association. Additionally, in some embodiments, the settings GUI 1040 allows the user to select a particular progress display for the TIR goal. For example, as shown most clearly in FIG. 10E-1, the user may select whether the TIR goal progress is displayed in hours (h) or as a percentage (%). In other embodiments (not shown), the goal progress display setting is fixed. For example, in some embodiments, the TIR goal progress is only displayed to the user in hours (h).

[0206] As shown in FIG. 10E-1, after the user enters new TIR goal settings, the user can click "Save" 1045 to update the information. In some embodiments, after the user clicks "Save" 1045, a confirmation in-app modal 1046 appears on the settings GUI 1040, as shown most clearly in FIG. 10E-3, allowing the user to confirm the changes to the TIR goal. In some embodiments, as shown in FIG. 10E-3, the confirmation in-app modal 1046 includes a message informing the user that the TIR goal changes will take effect the following day.

[0207] Additionally, FIG. 10F illustrates a settings GUI 1050 showing an interface related to units of measurement. According to one aspect of an embodiment, the settings GUI 1050 may be displayed if the user selects the "Set Units of Measurement" section 1023 in the previous settings GUI 1020 (FIG. 10C). Although not shown, in some embodiments, the units of measurement may be configurable (e.g., mg / dL or mmol / L). In some embodiments, as shown in FIG. 10F, the units of measurement may be non-configurable and displayed in the units of measurement defined by the third-party vendor's region or country (e.g., mg / dL for the United States). Also shown in FIG. 10F, the settings GUI 1050 includes an informational message 1051 indicating that the units of measurement for glucose values ​​will be automatically set based on the user's country. In some embodiments, the settings GUI 1050 also includes a prompt message 1052 indicating that the user can change the units of measurement in another analyte monitoring application (e.g., Libre2).

[0208] 10G is an in-app modal notification 1055 providing information regarding logging out of the TIR application. According to one aspect of an embodiment, the in-app modal notification 1055 may be displayed if the user selected the "Sign Out" option 1024 in the previous Settings GUI 1020 (FIG. 10C). According to another aspect of an embodiment, the in-app modal notification 1055 may be configured to obscure (overlay) a portion of the interface (e.g., Settings GUI 1000) displayed below it, obscuring that portion from view.

[0209] 10H-1 is a settings GUI 1060a illustrating a preferences interface. The settings GUI 1060a includes multiple notification options for the TIR application, allowing a user to turn one or more notifications on or off. According to one aspect of the embodiment, the settings GUI 1060a can be displayed, for example, when a user selects the "Preferences" option 1004 in the previous account settings GUI 1000 (FIG. 10A). 10H-1 , the settings GUI 1060a may include, but is not limited to, one or more of: a text label and description for a “TIR challenge” notification adjacent to a switch 1061 configured to toggle between an on position and an off position; a text label and description for a “Reminder to Log Meals” notification adjacent to a switch 1062 configured to toggle between an on position and an off position; and a text label and description for a “Reminder to Scan Sensor” notification adjacent to a switch 1063 configured to toggle between an on position and an off position. In some embodiments, if a sensor scan has not occurred for seven hours, a notification may be provided to remind the user to scan the sensor. It will be appreciated by those skilled in the art that instead of a toggle switch, the settings GUI 1060a can include one or more of an on / off check box, an on / off slider switch, an on / off radio button, an on / off button, etc.

[0210] According to one aspect of an embodiment, when the "meal log reminder" notification is turned on, the TIR application is configured to nudge the user again after a predetermined time (e.g., every six hours) if the user does not log a meal after the first reminder. In some embodiments, when the "meal log reminder" notification is turned on, the TIR application is configured to nudge the user again after a predetermined time (e.g., every four hours) if the user logs a meal after the first reminder.

[0211] FIG. 10H-2 illustrates the Settings GUI 1060a with all notifications turned off. Further, as shown in FIG. 10H-2, the Settings GUI 1060a includes an in-app modal display 1065. The in-app modal display 1065 provides information about the notification conditions that are disabled and includes a "Go to Settings" button that opens the corresponding settings interface so the user can enable notifications.

[0212] FIG. 10H-3 illustrates a further exemplary embodiment of a settings GUI. Specifically, FIG. 10H-3 illustrates a settings GUI 1060b, which is similar to settings GUI 1060a, except that settings GUI 1060b further includes a text label and description for the “New Analysis Results” notification, and an adjacent switch 1064 configured to toggle between an on position and an off position. In some embodiments, settings GUI 1060b also includes a configurable home screen display setting 1066. According to one aspect of the embodiment, a settings GUI 1069, as illustrated in FIG. 10H-4, can be output in response to a user selecting the home screen display setting 1066 in settings GUI 1060b. Specifically, from settings GUI 1069, a user can change the home screen display setting 1066 and select a home screen display 1068 from one or more views (e.g., meal view 1068a or time slot view 1068b). For example, meal views 1068a include meal views 1068a (e.g., meal event listings) in the logbook section on home GUI 400 (FIG. 4B), home GUI 450 (FIG. 4D), home GUI 430 (FIGS. 4E-1 to 4E-7), home GUI 485 (FIGS. 4J-1 to 4J-3), home GUI 495 (FIGS. 4K-1 to 4K-3), and home GUI 499 (FIGS. 4M-1 to 4M-6). Examples of time slot views 1068b include time slot views 1068b (e.g., time slot cards) in the logbook section on Home GUI 400 (FIG. 4B), Home GUI 450 (FIG. 4D), Home GUI 430 (FIGS. 4E-1 to 4E-7), Home GUI 485 (FIGS. 4J-1 to 4J-3), Home GUI 495 (FIGS. 4K-1 to 4K-3), and Home GUI 499 (FIGS. 4M-1 to 4M-6). For example, FIG. 10H-4 shows the meal view 1068a selected.

[0213] FIG. 10H-5 illustrates the settings GUI 1060b with all notifications turned off. Further, as shown in FIG. 10H-5, the settings GUI 1060b includes an in-app modal display 1067. The in-app modal display 1067 provides information about the notification conditions that are disabled and includes a "Go to Settings" button that opens the corresponding settings interface so the user can enable notifications.

[0214] 10I illustrates an exemplary embodiment of an account interface. In FIG. 10I, an account GUI 1070 is shown, which may be displayed if a user selects the "Help" section 1005 in the previous account setup GUI 1000 (FIG. 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.

[0215] 10J shows the Account GUI 1180, which includes contact information provided for help and feedback on the TIR application. The Account GUI 1180 can be displayed if the user selects the "Contact Us" section 1072 in the previous Account GUI 1070 (FIG. 10I).

[0216] In some embodiments, a user may also select TIR tutorial section 1071 in account GUI 1070 (FIG. 10I), which in response outputs a settings interface including: (1) a "TIR" tutorial option; (2) a "Daily Mini-Goals" tutorial option; (3) a "Food Log" tutorial option; (4) a "Load Score" tutorial option; and (5) a "Weekly Analysis Results" tutorial option. Selecting the "TIR" tutorial option may output a tutorial interface for TIR. Selecting the "Daily Mini-Goals" tutorial option may output a tutorial interface for daily mini-goals. Selecting the "Food Log" tutorial option may output a tutorial interface for food log recording. Selecting the "Load Score" tutorial option may output a tutorial interface for load scores. Selecting the "Weekly Analysis Results" tutorial option may output a tutorial interface for weekly analysis results.

[0217] In some embodiments, in response to a user selecting the “TIR” tutorial section 1071 in the account GUI 1070 ( FIG. 10I ), a tutorial interface regarding the TIR application may be displayed. For example, in some embodiments, a tutorial interface may be displayed that provides the user with information regarding research demonstrating that TIR is a simple yet powerful tool for tracking the burden that food places on an individual's glucose levels. According to another aspect of the embodiment, a tutorial interface may be displayed that provides the user with (1) information regarding the TIR ring, specifically, an explanation that the TIR ring represents the user's progress toward their goal and that the TIR ring fills up as the user accumulates time within the goal range, and (2) a message encouraging the user to complete one revolution of the TIR ring by midnight each day to achieve their goal. In another aspect of the embodiment, a tutorial interface may be displayed that informs the user that TIR may vary from person to person and that the American Diabetes Association recommends a daily TIR of approximately 17 hours.

[0218] In yet another aspect of the embodiment, a tutorial interface may be displayed that includes (1) a brief explanation of how to log a meal in the TIR application and (2) a link that, when selected by the user, will display a meal logging information modal display with tips for adding meals to the TIR application. Additionally, in some embodiments, a tutorial interface may be displayed that provides the user with information regarding meal ratings (scores). For example, in some embodiments, a tutorial interface may be displayed that includes (1) an explanation that indicates to the user that the TIR application rates meals based on post-meal glucose change, and that meals rated with a five-star rating are those that result in the smallest increase in glucose levels and meals rated with a one-star rating are those that result in the largest increase in glucose levels, and (2) a link that, when selected, will display a meal score information modal display, as described above, that includes information about how the TIR application ranks and scores meals. Additionally, in some embodiments, the meal score information modal display with information about how meals are ranked may include an emoji indicating glucose load. According to some aspects of the embodiments, the meal score information modal display may include a link that, when selected by the user, outputs another meal score information modal display containing more detailed information explaining why the score should be determined three hours after the meal is consumed. Additionally, in some embodiments, the meal score information modal display containing more detailed information explaining why the score should be determined three hours after the meal may also include tips to provide the user with clues to help them avoid prolonged deviations from the target range. In some embodiments, the meal score information modal display may also include more detailed information explaining why the user should allow time between meals. Furthermore, the meal score information modal display may also include more detailed information about the need to log all food consumed within a 30-minute period as a "meal" to minimize the number of meals with a "no score (no rating)."Additionally, in some embodiments, the meal score information modal display also includes detailed information explaining that a scan must occur at least every 8 hours in order for the TIR application to have the glucose data necessary to rate (score) a meal. Additionally, in some embodiments, the meal score information modal display informs the user that to accurately rate (score) a meal, the TIR application needs the user's glucose readings at the start of each meal and two hours after eating, and that if the user forgets to scan or there is a problem with the sensor, the TIR application may not be able to rate the user's meal.

[0219] In yet another aspect of the embodiment, a tutorial interface may be displayed that includes detailed information explaining (1) why it is recommended to wait approximately three hours between meals to obtain accurate glucose readings, and (2) that to minimize the number of meals that receive a "no score," all food consumed within a 30-minute period should be logged as a "meal."

[0220] Additionally, in some embodiments, a tutorial interface may be displayed informing the user that the TIR application can provide the user with a weekly analysis of their reach, and that they can view updates to the "Analysis Results" by selecting a setting in the TIR application to receive notifications when new analysis results are available, or by checking the "Analysis Results" tab.

[0221] 10K is a block diagram illustrating an "Account" tutorial GUI 1080, which may be displayed if a user selects tutorial section 1071 in the previous Account GUI 1070 (FIG. 10I). As shown in FIG. 10K, the "Account" tutorial GUI 1080 may include a "TIR" tutorial section 1081, a "TIR Goals and Achievement Rings" tutorial section 1082, and a "Meal Load Score" tutorial section 1083.

[0222] In some embodiments, in response to a user selecting the "TIR" tutorial section 1081 in the "Account" tutorial GUI 1080 (FIG. 10K), a tutorial interface regarding TIR may be displayed. For example, in some embodiments, a tutorial interface may be displayed explaining that TIR represents the length of time a user's glucose levels have been in the target range. According to another aspect of the embodiment, a tutorial interface may be displayed informing the user that a user who regularly maintains a TIR is likely to achieve good health. In another aspect of the embodiment, a tutorial interface may be displayed informing the user that a typical target glucose range for most people is between 70 mg / dL and 180 mg / dL, but that the user's physician may recommend a different range.

[0223] In another aspect of the embodiment, in response to a user selecting the "TIR Goals and Progression Rings" tutorial section 1082 of the "Account" tutorial GUI 1080 (FIG. 10K), a tutorial interface regarding the TIR goals and progress rings may be displayed. For example, in some embodiments, a tutorial interface may be displayed informing the user that, according to the American Diabetes Association, a person should have a daily TIR of approximately 17 hours. In another exemplary embodiment, a tutorial interface may be displayed informing the user that a TIR application calculates the user's current TIR and provides suggestions for an ideal initial goal. In yet another exemplary embodiment, a tutorial interface may be displayed providing the user with information regarding the TIR rings (particularly explaining that the TIR rings represent the user's progress toward their goals and that the TIR rings fill up with each additional hour the user spends within their goal range).

[0224] In yet another aspect of the embodiment, in response to a user selecting the "Meal Load Score" tutorial section 1083 of the "Account" tutorial GUI 1080 (FIG. 10K), a tutorial interface regarding meal load scores may be displayed. In some embodiments, a tutorial interface may be displayed that explains to the user, for example, one of the purposes of scoring (e.g., in a TIR application, scoring the user's meals to help the user understand which foods are most effective in keeping the user within a target range). In some exemplary embodiments, a tutorial interface may be displayed that explains to the user that the score is based on the change in the user's glucose level within three hours after eating. In other exemplary embodiments, a tutorial interface may be displayed that provides the user with various example scores and a key to what each represents in terms of changes in glucose values.

[0225] According to another aspect of the embodiment, the TIR application may also include an account interface related to general account information and information related to the TIR application. For example, an "About This App" interface may be provided that provides general information about the TIR application. Additionally, in some embodiments, the "About This App" interface may include a selectable "Experimental Disclaimer" section that, when selected by the user, outputs an account interface that includes an experimental disclaimer and information related to the intended use of the TIR application. Specifically, the account interface that includes the experimental disclaimer may include an information section indicating the date on which the user agreed to the TIR application's terms of use (e.g., in a previous onboarding GUI 925, as shown in FIG. 9B ).

[0226] Additionally, in some embodiments, the "About This App" interface may include a selectable "Licenses" section that, when selected by the user, will output an interface containing information regarding the licenses and notices for the open source software used in the TIR application.

[0227] In another aspect of the embodiments, the "About This App" interface can output an interface that includes the TIR application's terms of use. In some embodiments, the interface that includes the terms of use is displayed when a user first installs the TIR application or when the user first launches the TIR application. Additionally, in some embodiments, the "About This App" interface can also output an interface that includes the TIR application's privacy policy. In some embodiments, the interface that includes the privacy policy is displayed when a user first installs the TIR application or when the user first opens the TIR application.

[0228] Turning to FIG. 10L, an exemplary embodiment of an activities settings GUI 1085 is shown. According to one aspect of an embodiment, the activities settings GUI 1085 may be displayed when a user selects the “Activities” section described above in the description of the settings GUI 1000 (FIG. 10A). Specifically, if a user has not previously connected with a third-party health monitoring application (e.g., Apple Health), the activities settings GUI 1085, as shown in FIG. 10L, may be displayed during the onboarding process or within settings. More specifically, in some embodiments, the activities settings GUI 1085 may include an information section that informs the user that the TIR application will read the user's movement and fitness data from the third-party health monitoring application and associate it with the user's glucose readings to enable the user to understand the impact on the user's blood glucose levels. Additionally, in some embodiments, the information section may inform the user that they can navigate to a “Share” tab within the third-party health monitoring application to change the application's preferences. Additionally, in some embodiments, the activities settings GUI 1085 may include a “Connect” button 1086. A user can integrate the TIR application with a third-party health monitoring application by selecting the "Integrate" button 1086.

[0229] FIG. 10M illustrates a further exemplary embodiment of an Activities settings GUI. Specifically, the Activities settings GUI 1090 illustrated in FIG. 10M is displayed when a user selects the "Activities" section described above in the description of Settings GUI 1000 (FIG. 10A). More specifically, the Activities settings GUI 1090 is displayed during the onboarding process or within Settings if the user has previously connected with a third-party health monitoring application (e.g., Apple Health). Even more specifically, the Activities settings GUI 1090 is similar to the Activities settings GUI 1085 (shown in FIG. 10L), except that it does not include a "Connect" button.

[0230] Exemplary embodiments of the Data Loss GUI and their associated features 11A-11G are various block diagrams illustrating example embodiments of data loss interfaces or their associated functionality, any of which may be utilized in conjunction with any of the embodiments described herein.

[0231] 11A, a block diagram illustrating an example embodiment of a GUI 11000 for the TIR application is shown. Note that the GUI 11000 is similar to the home GUI 400 (FIG. 4B), except that the GUI 11000 further includes a notification associated with one or more missing data conditions (e.g., "Based on 12 hours of glucose data.") In some embodiments, as shown in FIG. 11A, the notification associated with one or more missing data conditions can be presented as an in-app notification 11111 located on the TIR card 11112.

[0232] 11B is a block diagram illustrating a GUI 11100 of another example embodiment of the TIR application. Note that GUI 11100 is similar to home GUI 450 (FIG. 4D), except that GUI 11100 further includes a notification associated with one or more missing data conditions (e.g., "Based on 12 hours of glucose data.") In some embodiments, as shown in FIG. 11B, the notification associated with one or more missing data conditions can be presented as an in-app notification 11101 located on the analyte graph card 11102.

[0233] 11C is a GUI 11200 that includes an in-app modal notification 11222 associated with a missing data condition. In some embodiments, the in-app modal notification 11222 may include information that provides hints for resolving one or more missing data conditions. Additionally, the in-app modal notification 11222 may be configured to obscure (overlay) a portion of the interface displayed below it, obscuring that portion from view.

[0234] FIG. 11D is a block diagram illustrating a GUI 11300 of another example embodiment of the TIR application. Note that the GUI 11300 is similar to the home GUI 485 (FIGS. 4J-1-4J-3), except that the GUI 11300 further includes a notification 11301 associated with one or more missing data conditions (e.g., "Based on 12 hours of glucose data"). In some embodiments, as shown in FIG. 11D, the notification 11301 associated with one or more missing data conditions can be presented as an in-app notification 11301 located on the TIR card 11302 of the GUI 11300. In some embodiments, the in-app notification 11301 can be located immediately adjacent to and below the daily TIR goal 11302. In some embodiments, as most clearly shown in FIG. 11D, the in-app notification 11301 can be located below the daily TIR goal 11302 and the TIR ring 11304 (including the TIR value 11303).

[0235] 11E is a block diagram illustrating a GUI 11400 of another example embodiment of the TIR application. The GUI 11400 is similar to the home GUI 485 (FIGS. 4J-1-4J-3), except that the GUI 11400 further includes a notification 11401 (e.g., "Based on 12 hours of glucose data") associated with one or more missing data conditions. In some embodiments, as shown in FIG. 11E, the notification 11401 associated with one or more missing data conditions can be presented as an in-app banner positioned between the TIR card 11419 and the analyte graph card 11411 of the GUI 11400.

[0236] FIG. 11F is a block diagram illustrating a GUI 11500 of another exemplary embodiment of the TIR application. The GUI 11500 is similar to the home GUI 485 (FIGS. 4J-1-4J-3), except that the GUI 11500 further includes a notification 11501 associated with one or more missing data conditions (e.g., "Based on 12 hours of glucose data," "Glucose data incomplete," or "Some glucose data missing"). In some embodiments, as shown in FIG. 11F, the notification 11501 associated with one or more missing data conditions may be presented as an in-app banner positioned between the analyte graph card 11511 and the logbook section 11518 of the GUI 11500. Specifically, the notification (in-app banner) 11501 may be positioned immediately below and adjacent to one or more selectable icons 11513 and immediately above and adjacent to a message 11514 indicating when the GUI 11500 was last updated. In some embodiments, the notification (in-app banner) 11501 may include an information icon 11502 that, when selected by the user, outputs an information modal display 11600 (shown in FIG. 11G) that provides further information about the missing data condition.

[0237] Specifically, the informational modal display 11600, as shown in FIG. 11G, may notify the user that they likely forgot to scan their sensor or are experiencing technical issues with their sensor, which is preventing the TIR application from accurately capturing their analyte data (e.g., glucose data) for that day. Additionally, in some embodiments, the informational modal display 11600 may also provide a message reminding the user that they should scan their sensor with the analyte monitoring application at least once every eight hours to prevent gaps in analyte data (e.g., glucose data). The informational modal display 11600 may also include a selectable "OK" button.

[0238] Those skilled in the art will appreciate that the notification and data loss status features described herein are intended to be illustrative only, and that any individual element or combination of elements shown or described in a particular embodiment or figure may be freely combined with any other element or combination of elements shown or described in any other embodiment.

[0239] Exemplary Embodiments of In-App Banner Notifications The TIR application may also include multiple in-app banner notifications, any of which may be used with the embodiments described herein. In some embodiments, the in-app banner notifications may include one or more of the following information: (1) information about recording a food log (e.g., "Meal Added," "Meal Deleted"), (2) information about updating settings (e.g., "Time in Range Updated"), (3) information about scanning (e.g., "Scan Successful," "Ready to Scan," "It's been 6 hours since your last scan," "Scan Failed"), (4) information about error detection (e.g., a notification prompting the user to try again later, or a notification prompting the user to sign out and sign back in to continue), or (5) information about lack of internet connectivity (e.g., a notification informing the user that an internet connection is required to obtain the latest TIR and glucose data).

[0240] Exemplary Embodiments of Activity Cards and Their Associated Features 12A-1-12B are various block diagrams illustrating example embodiments of interfaces including activity cards or related functionality, any of which may be used in conjunction with the embodiments described herein.

[0241] 12A-1 through 12A-4 are block diagrams illustrating a GUI 12000 of another exemplary embodiment of the TIR application. The GUI 12000 is similar to the home GUI 485 (shown in FIGS. 4J-1 through 4J-3), except that the GUI 12000 further includes a health section 1201. The health section 1201 may include one or more activity cards 1202, 1203 (e.g., a movement card 1202 and a sleep card 1203). Specifically, the health section 1201 may be displayed on the GUI 12000 if the user enables, for example, via the onboarding GUI 995 (shown in FIG. 9P), sharing of their movement data, sleep data, or both, from a third-party health monitoring application (e.g., Apple Health). For example, if a user enables sharing only their movement data from a third-party health monitoring application, such as via the "Movement Settings" 9951 in the onboarding GUI 995, a health section 1201 including a movement card 1202 is displayed in the GUI 12000, as shown in FIGS. 12A-1 and 12A-2. Specifically, FIG. 12A-1 shows the movement card 1202 displaying the number of steps (e.g., "24,437 steps") taken by the user during a predetermined period (e.g., a particular day). In some embodiments, as shown in FIG. 12A-2, the movement card 1202 displays the number of wheelchair pushes (e.g., "1,437 times") made by the user during a predetermined period (e.g., a particular day). As shown in FIGS. 12A-2 and 12-3, the health section 1201 including the movement card 1202 can be positioned immediately adjacent to, but distal to, the logbook section 1208 of the GUI 12000.

[0242] In some embodiments, as shown most clearly in FIG. 12A-3 , if a user authorizes sharing of only their sleep-related data from a third-party health monitoring application, such as via “Sleep Settings” 9952 of the onboarding GUI 995, a health section 1201 including a sleep card 1203 is displayed in GUI 12000. The sleep card 1203 displays the amount of time the user spent sleeping during a predetermined past period (e.g., the previous night) (e.g., “17 hours 31 minutes”). Furthermore, in some embodiments, as shown most clearly in FIG. 12A-4 , if a user authorizes sharing of both their movement data and sleep data from a third-party health monitoring application (e.g., Apple Health) via “Movement Settings” 9951 or “Sleep Settings” 9952 of the onboarding GUI 995, a health section 1201 including a movement card 1202 and a sleep card 1203 is displayed in GUI 12000. In some embodiments, the movement card 1202 can be positioned immediately adjacent to the sleep card 1203. Additionally, in some embodiments, health section 1201 may be positioned immediately adjacent to, but distal from, logbook section 1208 of GUI 12000. Additionally, in some embodiments, health section 1201 may further include message 1204, as shown in FIGS. 12A-1 through 12A-4. Message 1204 may be positioned adjacent to, but distal from, movement card 1202 or sleep card 1203, and may indicate when the data displayed in health section 1201 was last updated. In some embodiments, sleep card 1203 and movement card 1202 are configured to update each time the TIR application is launched.

[0243] According to yet another aspect of the embodiment, as shown most clearly in FIG. 12B , if the user does not allow the TIR application to access and integrate with a third-party health monitoring application (e.g., Apple Health) during the initial setup or onboarding process (e.g., onboarding GUI 995 as shown in FIG. 9P ), a health section 1201 including an integration card 1205 is displayed in GUI 12000. Specifically, in some embodiments, integration card 1205 may include a message indicating that by integrating with a third-party health monitoring application, the user will be able to obtain analysis of how their movement and sleep are affecting their glucose levels. Additionally, in some embodiments, integration card 1205 may include a selectable “integrate” button 1206.

[0244] It will be appreciated by those skilled in the art that the health section 1201, activity cards 1202, 1203, and their associated features are intended to be illustrative only, and that any individual element or combination of elements shown or described in a particular embodiment or figure may be freely combined with any other element or combination of elements shown or described in any other embodiment.

[0245] Exemplary Embodiments of Meal Detection GUI and Their Associated Features An exemplary embodiment of a method for detecting whether a user has consumed a meal will now be described. It should be noted at the outset that those skilled in the art will recognize that the method steps described herein may be comprised of software instructions stored in memory of a computing device (e.g., reader 120, local computer system 170, trusted computer system 180) of system 100, and thus, when executed by one or more processors of the computing device, the instructions may cause the one or more processors to perform any or all of the method steps described herein. Referring now to FIG. 13, a flow diagram illustrating an exemplary embodiment of a method 13500 for detecting whether a user has likely consumed a meal (an "episode" or "excursion") has occurred based on received data indicative of analyte levels (e.g., glucose levels).

[0246] According to one aspect of the embodiment, method 13500 may utilize one or more parameters related to fluctuations in analyte levels (e.g., fluctuations in glucose levels) when detecting meals. For example, a first parameter may include a minimum rate of change in analyte levels over time (e.g., rate of change in glucose levels over time) that is a prerequisite for the onset of an excursion ("Trigger Excursion Change" parameter). In some embodiments, other parameters may also be utilized to detect valid mealtime deviations or excursions. Such other parameters include, but are not limited to: (1) a threshold for the duration of a test substance level fluctuation (e.g., an upper or lower limit for the duration of a test substance level fluctuation); (2) a threshold for the amount of change in test substance level from the start to the end of the excursion (e.g., an upper or lower limit for the amount of change in glucose level from the start to the end of the excursion); (3) a threshold for the minimum test substance level or the maximum test substance level, or both (e.g., an upper / lower limit for the minimum glucose value, or a lower / upper limit for the maximum glucose value); and (4) a threshold for the time interval allowed between test substance level readings (e.g., an upper limit for the time interval allowed between glucose level readings).

[0247] Those skilled in the art will appreciate that a variety of different thresholds or values ​​can be used for the parameters related to analyte level fluctuations to detect significant deviations.

[0248] 13, method 13500 begins at step 13501, where the starting point of an analyte level excursion is identified by calculating a slope associated with a received analyte level measurement (e.g., a glucose level measurement). In some embodiments, if the slope exceeds a change-at-excursion-onset parameter, an earlier timestamp is identified as the starting point of the analyte level excursion.

[0249] Once the start of the fluctuation has been identified, the end of the fluctuation is identified by continuing to calculate the slope in step 13502. In some exemplary embodiments, if the slope falls below the change-at-onset parameter, an earlier timestamp is identified as the end of the analyte level fluctuation.

[0250] Once the end point of the excursion has been identified, a "trigger window" is calculated (e.g., in minutes), which is the time from the start point of the excursion to the end point of the excursion, in step 13503. Also, according to one aspect of the embodiment, the difference between the analyte level value at the start point of the excursion and the analyte level value at the end point of the excursion (e.g., the difference in glucose level values) is calculated and used as the total change in analyte level (e.g., the total change in glucose level).

[0251] Then, in step 13504, a minimum analyte level for threshold comparison required to detect a valid deviation is identified, where the minimum analyte level (e.g., glucose value) during the analyte level fluctuations is calculated as the minimum analyte level for threshold comparison.

[0252] Then, in step 13505, a maximum analyte level for threshold comparison necessary to detect a valid deviation is identified, where the maximum analyte level for threshold comparison is calculated as the maximum analyte value (e.g., glucose value) during the analyte level fluctuations.

[0253] Then, in step 13506, a time interval between analyte level readings for threshold comparison is determined, where the time interval is calculated as the difference in measurement times between analyte level readings (e.g., glucose level readings) during the deviation.

[0254] In some exemplary embodiments, a deviation is determined to be valid if it meets certain threshold conditions. These threshold conditions include, but are not limited to, the following: (1) the time interval between analyte level readings for threshold comparison is determined to be between upper and lower limits for the duration of the analyte level fluctuation, (2) the total change in analyte level (e.g., total change in glucose level) is determined to be between upper and lower limits for the change in glucose level from the start to the end of the deviation, (3) the highest analyte level value for threshold comparison in the deviation is between upper and lower limits for the highest analyte level value, and (4) all measurement time intervals for threshold comparison are below the upper limits for the time interval allowed for a valid deviation. From this perspective, if a deviation is determined to be valid, the deviation is detected as a meal.

[0255] In some exemplary embodiments, if one or more meals are entered within a short time frame, the one or more meals may be configured to be treated as part of a single meal entry. In some embodiments, if one or more meals are entered within a short time frame, the one or more meals are treated as a single meal entry and assigned a single score.

[0256] In some embodiments, if multiple meals are entered within a predetermined time of consuming a meal (e.g., within one hour of a meal), the multiple meals are logged as a single meal. In some embodiments, when multiple meals are logged as a single meal, a timestamp for scoring the meal event may be included. This timestamp is the timestamp of the earliest meal entered. In some embodiments, meals entered after a predetermined time has elapsed since the first meal was consumed (e.g., one hour after the first meal was consumed) are not considered for concatenation.

[0257] 13A-1 and 13A-2 are various block diagrams illustrating example embodiments of meal detection interfaces or related functionality, any of which may be utilized in conjunction with the embodiments described herein.

[0258] 13A-1 and 13A-2, block diagrams are shown illustrating example embodiments of the home GUI 485 further including one or more notifications 1301 associated with the detection of a missed meal. In some embodiments, as shown in FIGS. 13A-1 and 13A-2, the one or more notifications 1301 associated with the detection of a missed meal may be presented as an in-app notification 1301 located in a position between the analyte graph card 4811 and the logbook section 4808. However, one skilled in the art will appreciate that the in-app notification 1301 may be displayed in various other positions on the home GUI 485 without departing from the scope of the present disclosure.

[0259] According to one aspect of an embodiment, in-app notifications 1301 may prompt a user to log a meal. Referring to FIGS. 13A-1 and 13A-2 , in some embodiments, each in-app notification 1301 includes a query 1302 asking whether the user ate a meal (e.g., “Did you eat?”) and a message 1303 informing the user that the user experienced a blood glucose elevation around a particular time associated with the detection of a missed meal (e.g., “You experienced a blood glucose elevation around 10:34 AM”). Also, according to one aspect of an embodiment, each in-app notification 1301 may include a selectable “ignore” button 1304 and a selectable meal logging button 1305. Specifically, when a user selects the “ignore” button 1304 for a particular in-app notification 1301, that in-app notification 1301 is removed from view in the home GUI 485.

[0260] More specifically, in some embodiments, when a user selects the log meal button 1305, the log meal GUI 500 (FIG. 5A) is output. Additionally, in some embodiments, the enter meal entry modal display 520 (shown in FIG. 5C) may be displayed with the date and time pre-populated in the time field 527. This date and time is the date and time associated with the “detected missed meal” associated with the in-app notification 1301 at which the selection of the log meal button 1305 occurred. In some embodiments, when a user logs a meal for a particular time associated with the detected missed meal (e.g., by selecting the log meal button 1305 in the in-app notification 1301), the corresponding in-app notification 1301 is removed from the home GUI 485. Additionally, the logged meal also appears in the logbook section 4808 of the home GUI 485, e.g., in the appropriate TOD card 4801 under the list 4822 of meal events 4829.

[0261] According to yet another aspect of the embodiment, as shown most clearly in FIG. 13A-2 , one or more missed episode markers 1310 (e.g., one or more missed meal icons 1310) may be displayed near, adjacent, or proximal to the analyte trend line 4815, or along the x-axis, the top of the graph window 484, or the bottom of the graph window 484. In some aspects of the embodiment, each missed meal icon 1310 is positioned on the analyte graph card 4811 to allow the user to visually associate the meal omission with the particular time at which the meal omission was detected and the subsequent post-meal analyte trajectory. In some embodiments, when the user selects the “Ignore” button 1304 for a particular in-app notification 1301 associated with a detected meal omission, the corresponding missed meal icon 1310 is removed from the analyte graph card 4811. Although not shown, in some embodiments, when a user logs a meal in association with a particular previously detected missed meal, the missed meal icon 1310 is replaced with a meal icon.

[0262] In some embodiments, if the user "ignores" or does not address the in-app notification 1301, the in-app notification 1301 and its corresponding missed meal log icon 1310 are removed from the home GUI 485 after a predetermined time (e.g., 24 hours).

[0263] According to another aspect of the embodiment, as shown most clearly in FIG. 13A-2 , when two in-app notifications 1301 associated with a detected missed meal log entry are displayed in the home GUI 485, the in-app notifications 1301 are stacked or partially overlapped, with the first in-app notification 1301a on top of the second in-app notification 1301b. In some embodiments, the stacking order of the in-app notifications 1301 is chronological. For example, the most recent in-app notification 1301a is stacked or partially overlapped on top of the older (earlier occurring) in-app notification 1301b. In this manner, the most recent of the stacked in-app notifications 1301 is displayed more prominently in the home GUI 485 than the older in-app notification 1301 that is positioned below the most recent in-app notification 1301 (or that is partially positioned below the most recent in-app notification 1301). Additionally, in some embodiments, when two in-app notifications 1301 are displayed on the Home GUI 485, each in-app notification 1301 is provided with a pagination 1311. The pagination 1311 of each in-app notification 1301 indicates that the in-app notification 1301 is a particular in-app notification 1301 among the total number of in-app notifications 1301 currently displayed on the Home GUI 485 (e.g., if there are a total of two in-app notifications 1301 on the Home GUI 485 and the most recent in-app notification 1301 is more prominently displayed, the pagination would be "1 of 2").

[0264] According to yet another aspect of the embodiment, as shown most clearly in FIG. 13A-2, when three or more in-app notifications 1301 associated with detected missed meal entries are displayed on the Home GUI 485, the in-app notifications 1301 are stacked or partially overlapping one another. In some embodiments, the stacking order of the in-app notifications 1301 is chronological. Furthermore, in some embodiments, when three or more in-app notifications 1301 are displayed on the Home GUI 485, each in-app notification 1301 is provided with a page number 1311. The page number 1311 of each in-app notification 1301 indicates that the in-app notification 1301 is a particular in-app notification 1301 among the total number of in-app notifications 1301 currently displayed on the Home GUI 485 (e.g., if there are a total of 10 in-app notifications 1301 on the Home GUI 485 and the most recent in-app notification 1301 is displayed most prominently, the page number would be “1 of 10”). Additionally, according to some embodiments, 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 ten in-app notifications, the in-app notification page number is updated from "1 of 10" to "1 of 9") when an in-app notification is removed from GUI 485 (e.g., if the user "ignores" the in-app notification or logs a meal corresponding to a particular time associated with the corresponding missed meal detection).

[0265] Furthermore, according to another aspect of the embodiment, when the user performs a tenth predetermined input, in response to this, the in-app notification 1301 displayed below moves to the top of the stack of in-app notifications 1301. Examples of the tenth predetermined input include a predetermined operation such as tapping or swiping on a particular in-app notification 1301 or selecting the “Ignore” button 1304. For example, when the user selects the “Ignore” button 1304 on the first of three in-app notifications 1301, the second in-app notification 1301 is displayed most prominently on the home GUI 485. In some embodiments, the second in-app notification 1301 of the three in-app notifications 1301 displays a page number 1311 indicating that it is the “2 of 3” in-app notification 1301. Furthermore, when the user selects the “Ignore” button 1304 on the second of three in-app notifications 1301, the third in-app notification 1301 is displayed most prominently on the home GUI 485. In some embodiments, the third in-app notification 1301 of three in-app notifications 1301 displays a page number 1311 indicating that it is the "3 of 3" in-app notification 1301.

[0266] In some embodiments, the analyte value graph card 4811 of the home GUI 485 is configured to update so that the missed meal log icon 1310 corresponding to the most prominently displayed in-app notification 1301 is displayed on the analyte value graph card 4811. For example, if the user swipes away a first in-app notification 1301 so that a second in-app notification 1301 is displayed most prominently on the home GUI 485, the analyte graph card 4811 is updated so that the missed meal log icon 1310 associated with the first in-app notification 1301 is removed from the analyte graph card 4811, and the missed meal log icon 1310 associated with the second in-app notification 1301 is displayed on the analyte graph card 4811.

[0267] While notification 1301 associated with the detection of missing meal records has been described above with reference to home GUI 485, those skilled in the art will understand that notification 1301 and its associated functionality may also be utilized in home GUI 400 (FIG. 4B), home GUI 450 (FIG. 4D), home GUI 430 (FIGS. 4E-1 to 4E-7), home GUI 485 (FIGS. 4J-1 to 4J-3), home GUI 495 (FIGS. 4K-1 to 4K-3), and home GUI 499 (FIGS. 4M-1 to 4M-2) without departing from the scope of the present disclosure.

[0268] For example, FIGS. 13B-1 and 13B-2 are block diagrams illustrating a home GUI 499 configured to include meal detection functionality. Specifically, with reference to FIGS. 13B-1 and 13B-2, one or more notifications 1351 associated with missed meal recordings can be presented as in-app notifications 1351 on the home GUI 499. The home GUI 499 includes a meal rating average card 4991, an analyte graph card 4910, and a logbook section 4998. The meal rating average card 4991 includes a meal rating average 4920, a graphical display 4921 corresponding to the meal rating average 4920, and a meal rating average display 4923 visually representing the meal rating average obtained over a predetermined time period. The analyte graph card 4910 includes an analyte graph 49011 having an analyte trend line 49015. The logbook section 4998 includes a list 4992 of meal events 4999. In some exemplary embodiments, the in-app notification may be located in a location on the home GUI 499 between the analyte graph card 4910 and the logbook section 4998. However, one skilled in the art will appreciate that the in-app notification 1351 may be displayed in various other locations on the home GUI 499 without departing from the scope of the present disclosure.

[0269] 13B-1 and 13B-2, in some embodiments, each in-app notification 1351 includes a query 1352 asking whether the user ate a meal (e.g., "Did you eat?") and a message 1353 informing the user that the user experienced a blood glucose elevation around a particular time associated with the detection of the missed meal (e.g., "You experienced a blood glucose elevation around 10:34 AM."). Also, according to one aspect of an embodiment, each in-app notification 1351 may include a selectable "Ignore" button 1354 and a selectable meal log button 1355. Specifically, when a user selects the "Ignore" button 1354 for a particular in-app notification 1351, that in-app notification 1351 is removed from display in the home GUI 499.

[0270] More specifically, in some embodiments, when a user selects the log meal button 1355, the log meal GUI 500 (FIG. 5A) is output. Additionally, in some embodiments, the enter meal entry modal display 520 (shown in FIG. 5C) may be displayed with the date and time pre-populated in the time field 527. This date and time is the date and time associated with the “detected missed meal” associated with the in-app notification 1351 at which the selection of the log meal button 1355 occurred. In some embodiments, when a user logs a meal (e.g., by selecting the log meal button 1355 of the in-app notification 1351) for the particular time associated with the detected missed meal, the corresponding in-app notification 1351 is removed from the home GUI 499. Additionally, the logged meal also appears in the logbook section 4998 of the home GUI 499, e.g., below the list 4992 of meal events 4999.

[0271] According to yet another aspect of the embodiment, as shown most clearly in FIG. 13B-2 , one or more unrecorded deviation marks 1350 (e.g., one or more missed meal record icons 1350) may be displayed near, adjacent to, or proximal to the test substance trend line 49015, or along the x-axis, the top of the graph window 49904, or the bottom of the graph window 49904. In some aspects of the embodiment, each missed meal record icon 1350 is positioned on the test substance graph card 4910 to allow the user to visually associate the missed meal record with the particular time at which the missed meal record was detected and the subsequent post-meal test substance trajectory. In some embodiments, when the user selects the “Ignore” button 1354 for a particular in-app notification 1351 associated with a detected missed meal record, the corresponding missed meal record icon 1350 is removed from the test substance graph card 4910. Although not shown, in some embodiments, the missed meal icon 1350 is replaced with a meal icon when the user logs a meal associated with a particular previously detected missed meal.

[0272] In some embodiments, if the user "ignores" or does not address the in-app notification 1351, the in-app notification 1351 and the corresponding missed meal log icon 1350 are removed from the home GUI 499 after a predetermined time (e.g., 24 hours).

[0273] According to another aspect of the embodiment, as shown most clearly in FIG. 13B-2 , when two in-app notifications 1351 associated with a detected missed meal log entry are displayed in the home GUI 499, the in-app notifications 1351 are stacked or partially overlapped, with the first in-app notification 1351a on top of the second in-app notification 1351b. In some embodiments, the stacking order of the in-app notifications 1351 is chronological. For example, the most recent in-app notification 1351a is stacked or partially overlapped on top of the older (earlier occurring) in-app notification 1351b. In this manner, the most recent of the stacked in-app notifications 1351 is displayed more prominently in the home GUI 499 than the older in-app notification 1351 that is positioned below the most recent in-app notification 1351 (or that is partially positioned below the most recent in-app notification 1351). Additionally, in some embodiments, when two in-app notifications 1351 are displayed on the home GUI 499, each in-app notification 1351 is provided with a page number 13511. The page number 13511 of each in-app notification 1351 indicates that the in-app notification 1351 is a particular in-app notification 1351 out of the total number of in-app notifications 1351 currently displayed on the home GUI 499 (e.g., if there are a total of two in-app notifications 1351 on the home GUI 499 and the most recent in-app notification 1351 is more prominently displayed, the page number would be "1 of 2").

[0274] According to yet another aspect of the embodiment, as shown most clearly in FIG. 13B-2 , when three or more in-app notifications 1351 associated with detected missed meal entries are displayed on the home GUI 499, the in-app notifications 1351 are stacked or partially overlapping one another. In some embodiments, the stacking order of the in-app notifications 1351 is chronological. Furthermore, in some embodiments, when three or more in-app notifications 1351 are displayed on the home GUI 499, each in-app notification 1351 is provided with a page number 13511. The page number 13511 of each in-app notification 1351 indicates that the in-app notification 1351 is a particular in-app notification 1351 of the total number of in-app notifications 1351 currently displayed on the home GUI 499 (e.g., if there are a total of 10 in-app notifications 1351 on the home GUI 499 and the most recent in-app notification 1351 is displayed most prominently, the page number would be “1 of 10”). Additionally, according to some embodiments, 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 ten in-app notifications, the in-app notification page number is updated from "1 of 10" to "1 of 9") when an in-app notification is removed from GUI 499 (e.g., if the user "ignores" the in-app notification or logs a meal corresponding to a particular time associated with the corresponding missed meal detection).

[0275] Furthermore, according to another aspect of the embodiment, when the user performs an eleventh predetermined input, in response to this, the in-app notification 1351 displayed below moves to the top of the stack of in-app notifications 1351. Examples of the eleventh predetermined input include a predetermined operation such as tapping or swiping on a particular in-app notification 1351 or selecting the “Ignore” button 1354. For example, when the user selects the “Ignore” button 1354 on the first of three in-app notifications 1351, the second in-app notification 1351 is displayed most prominently on the home GUI 499. In some embodiments, the second in-app notification 1351 of the three in-app notifications 1351 displays a page number 13511 indicating that it is the “2 of 3” in-app notification 1351. Furthermore, when the user selects the “Ignore” button 1354 on the second of three in-app notifications 1351, the third in-app notification 1351 is displayed most prominently on the home GUI 499. In some embodiments, the third in-app notification 1351 of three in-app notifications 1351 displays a page number 13511 indicating that it is the "3 of 3" in-app notification 1351.

[0276] In some embodiments, the analyte value graph card 4910 of the home GUI 499 is configured to update so that the missed meal log icon 1350 corresponding to the most prominently displayed in-app notification 1351 is displayed on the analyte value graph card 4910. For example, if the user swipes away a first in-app notification 1351 so that a second in-app notification 1351 is displayed most prominently on the home GUI 499, the analyte graph card 4910 is updated so that the missed meal log icon 1350 associated with the first in-app notification 1351 is removed from the analyte graph card 4910 and the missed meal log icon 1350 associated with the second in-app notification 1351 is displayed on the analyte graph card 4910.

[0277] Exemplary Embodiments of the "Analysis Results" GUI and Their Associated Features 14A-1-14E are various block diagrams illustrating example embodiments of an analysis results interface or related functionality. Any of these embodiments may be utilized in conjunction with the embodiments described herein. Referring to FIGS. 14A-1-14A-5, block diagrams illustrating an example embodiment of an analysis results GUI 14000 for a TIR application are shown. The "Analysis Results" GUI 14000 may be displayed when a user selects an analysis results icon on home GUI 400 (FIG. 4B), home GUI 450 (FIG. 4D), home GUI 430 (FIGS. 4E-1-4E-7), home GUI 485 (FIGS. 4J-1-4J-3), home GUI 495 (FIGS. 4K-1-4K-3), or home GUI 499 (FIGS. 4M-1-4M-6). According to some embodiments, and as shown in FIGS. 14A-1 through 14A-4, the analysis results GUI 14000 includes (1) an analysis results section 14100, (2) a top meals section 14200, (3) a selectable home icon 14300, (4) a selectable analysis results icon 14301, (5) a selectable "+" icon 14302, and (6) a selectable settings icon 14303. The analysis results section 14100 can include one or more analysis results cards 14400, 14500. The top meals section 14200 can include a meal information list 14201 including the highest scoring meal events 14202 ranked according to scores 14203 assigned based on the recorded analyte responses corresponding to the meal events.

[0278] According to one aspect of the embodiment, as shown most clearly in FIG. 14A-1 , the analysis results section 14100 can include one or more analysis result cards 14400, 14500, such as, but not limited to, a “Best Day” analysis result card 14400 and a “Progress” analysis result card 14500, which can be based on data indicative of analyte levels and dietary information. Specifically, the data indicative of analyte levels (e.g., glucose levels) and dietary information can be used to identify the user's progress over a predetermined period of time. Such a predetermined period of time can include, but is not limited to, the user's “best” day (e.g., the day with the user's longest TIR, highest daily score, or highest average dietary rating over a specified period of time (e.g., one week)). The user's progress can be measured based on the data indicative of the user's analyte levels and specific criteria related to the dietary information (e.g., criteria related to TIR, daily score, average dietary rating, etc.). The analysis result GUI is also configured to display statistics about the user's growth on analysis result cards 14400 and 14500.

[0279] Specifically, in some exemplary embodiments, the "Best Day" analysis results card 14400 may include a summary message 14401. The summary message 14401 may provide statistics detailing which day the user's TIR was "best" during a predetermined time period (e.g., a week) and what the daily TIR (highest daily TIR) was for that particular day during the predetermined time period (e.g., "The highest daily TIR for the period February 6-February 12 was Friday, February 11, when the TIR was 16 hours."). According to some embodiments, the message 14401 may provide the user's highest TIR in hours (h) or as a percentage (%).

[0280] In some embodiments, if the user's TIR (hours in range) is less than one hour, the "Best Day" analysis results card 14400 displays a message 14401 indicating that the user's TIR (hours in range) was 0 hours (e.g., "The highest daily TIR between February 20th and February 26th was Friday, February 25th, when the TIR was 0 hours.").

[0281] In some embodiments, the "Best Day" analysis results card 14400 also includes a summary message 14401 that provides detailed information about the day that achieved the highest daily score as the user's "Best Day" for a given time period (e.g., "The day with the highest score achieved between February 6th and February 12th was Friday, February 9th, with a score of 87 points.").

[0282] In some embodiments, the "Best Day" analysis results card 14400 may also include a summary message 14401 that provides detailed information about the day on which the user had the highest average meal rating during a given time period (e.g., "The highest rated day between January 30th and February 5th was Wednesday, February 2nd, with an average rating of 4.8.").

[0283] In some embodiments, after a predetermined period of time (e.g., a one-week (7-day) period), a "Best Day" analysis result card 14400 is displayed on the analysis results GUI 14000. For example, after a seven-day period (e.g., every Sunday), a "Best Day" analysis result card 14400 including a message 14401 is displayed on the analysis results GUI 14000. In some embodiments, the analysis results GUI 14000 is configured to update at a predetermined frequency (i.e., after each next predetermined period of time), replacing the currently displayed "Best Day" analysis result card 14400 with a new "Best Day" analysis result card 14400 (e.g., displaying a new "Best Day" analysis result card 14400 on the analysis results GUI 14000 every Sunday or every seven days). Thus, the analysis results GUI 14000 is configured to update to display to the user the most recent "Best Day" analysis result card 14400 corresponding to the most recent predetermined period of time.

[0284] In some embodiments, if there is no recent "Best Day" analysis result card 14400 (e.g., if the user only monitors test substance data intermittently, or if a predetermined period of time has passed but the user did not monitor test substance data during that period and the user's achievement during that period has not been identified by the TIR application), the analysis result GUI 14000 is configured to display the "Best Day" analysis result card 14400 for the period closest to the current time (e.g., if the user last monitored test substance data one month ago, the "Best Day" analysis result card 14400 for one month ago is displayed).

[0285] Also, although not shown, in some embodiments, the "Analysis Results" icon displayed on any interface output by the TIR application is configured to display an animation when a new "Best Day" analysis results card 14400 is presented to indicate to the user that a new analysis results card 14400 has been presented. For example, in some embodiments, the analysis results icon is configured to indicate that a new analysis results card has been presented by changing color (e.g., having a color portion such as blue).

[0286] Additionally, in some exemplary embodiments, as shown most clearly in FIGS. 14A-1 and 14A-4, the “Best Day” analysis results card 14400 may also include an analysis results time-of-insight indicator 14402. The analysis results time indicator 14402 is configured to indicate how much time has passed since the “Best Day” analysis results card 14400 was displayed on the analysis results GUI 14000 (e.g., “1 minute ago,” “1 week ago,” etc.). Also, as shown in FIG. 14A-4, in some embodiments, the “Best Day” analysis results card 14400 may further include a “New” tag 14403. The “New” tag 14403 indicates to the user that the “Best Day” analysis results card 14400 is newly added to the analysis results GUI 14000 and that the user has not yet viewed the card. Additionally, in some embodiments, in response to the user performing a seventh predetermined operation (e.g., a predetermined operation such as a tap operation), the "New" tag 14403 is removed from the "Best Day" analysis results card 14400. In some embodiments, the "New" tag 14403 from the "Best Day" analysis results card 14400 is automatically removed after a predetermined period of time (e.g., 24 hours).

[0287] In some embodiments, the analysis results GUI 14000 is configured to display an analysis results section 14100 that includes only a "Best Day" analysis results card 14400 (see, e.g., FIG. 14A-5). In other embodiments, as shown in FIGS. 14A-1 and 14A-4, the analysis results GUI 14000 may display an analysis results section 14100 that includes both a "Best Day" analysis results card 14400 and a "Growth" analysis results card 14500 (see, e.g., FIG. 14A-1 and 14A-4).

[0288] 14A-1 and 14A-4, according to some embodiments, a "Growth" analysis result card 14500 can include a summary message 14501. The summary message 14501 provides detailed information about the user's TIR or daily score growth over a predetermined time period (e.g., "The average TIR (hours in range) for the period February 6-February 12 was 2 hours higher than the average TIR for the period January 30-February 5." or "The average daily score for the period February 6-February 12 was 4 points higher than the average daily score for the period January 30-February 5."). In some embodiments, the TIR application is configured to compare the user's average TIR or daily score for the most recent predetermined time period with the user's average TIR or daily score for an earlier predetermined time period (e.g., compare the user's average TIR or daily score for the most recent 7-day period with the user's average TIR or daily score for the previous 7-day period). According to some embodiments, message 14501 may indicate the user's TIR growth in hours (h) or as a percentage (%).

[0289] In some embodiments, the TIR application is configured to compare the user's average TIR or daily score for the most recent predetermined period with the user's average TIR or daily score for the first week since starting to use the TIR application. In some embodiments, the "Growth" analysis result card 14500 is displayed only after the TIR application has obtained the user's average TIR or daily score for two predetermined periods and is able to compare them to determine growth in the average TIR or daily score. In some embodiments, after the first "Growth" analysis result card 14500 is displayed, the analysis results GUI 14000 is updated at a predetermined frequency thereafter, replacing the currently displayed "Growth" analysis result card 14500 with a new "Growth" analysis result card 14500 (e.g., displaying a new "Growth" analysis result card 14500 on the analysis results GUI 14000 every Sunday or every seven days). Thus, the analysis results GUI 14000 is configured to update to display the user's most recent growth (e.g., the user's most recent TIR growth).

[0290] In some embodiments, if there is no recent "Growth" analysis result card 14500 (e.g., if the user only monitors test substance data intermittently, or if a predetermined period of time has passed but the user has not monitored test substance data during that period), the analysis result GUI is configured to display the "Growth" analysis result card 14500 for the period closest to the current time (e.g., the "Growth" analysis result card 14500 from one month ago is displayed).

[0291] Additionally, in some embodiments, the "Analysis Results" icon on the interface output by the TIR application is configured to display an animation when a new "Growth" analysis results card 14500 is presented to indicate to the user that a new analysis results card 14500 has been presented. For example, in some embodiments, the analysis results icon is configured to indicate that a new analysis results card 14500 has been presented by changing color (e.g., having a color portion such as blue).

[0292] In some aspects of the embodiment, if the user's average TIR is equal to or less than the user's average TIR for the first week of using the TIR application, the "Growth" analysis result card 14500 showing the growth of the user's TIR is not displayed on the analysis result GUI 14000.

[0293] Additionally, in some exemplary embodiments, as shown in FIGS. 14A-1 and 14A-4, the “Growth” analysis result card 14500 may also include an analysis result time indicator 14502. The analysis result time indicator 14502 is configured to indicate how much time has passed since the “Growth” analysis result card 14500 was displayed on the analysis results GUI 14000 (e.g., “1 minute ago,” “1 week ago,” etc.). Additionally, in some embodiments, as shown most clearly in FIG. 14A-4, the “Growth” analysis result card 14500 may also include a “New” tag 14503. The “New” tag 14503 is a tag that indicates to the user that the “Growth” analysis result card 14500 is newly added to the analysis results GUI 14000 and that the user has not yet viewed the card. 14A-4, in response to a user performing an eighth predetermined operation (e.g., a predetermined operation such as a tap operation), the "New" tag 14503 is removed from the "Growth" analysis result card 14500. In some embodiments, the "New" tag 14503 on the "Growth" analysis result card 14500 is automatically removed after a predetermined period of time (e.g., 24 hours).

[0294] 14A-1-14A-4, in some embodiments, analysis results GUI 14000 includes an analysis results history link 14600 that, when selected by a user, outputs analysis results history GUI 14650, as shown in FIGS. 14B-1-14B-3. As shown most clearly in FIG. 14B-1, analysis results history GUI 14650 is configured to display analysis results log 14651. Analysis results log 14651 may include the most recent "best day" analysis results card 14400 and the most recent "growth" analysis results card 14500, as well as past "best day" analysis results cards 14400 and past "growth" analysis results cards 14500. Specifically, in some embodiments, the analysis results log 14651 is configured to display the "Best Day" analysis result cards 14400 and the "Growth" analysis result cards 14500 in chronological order, with the most recent "Best Day" analysis result card 14400 and the most recent "Growth" analysis result card 14500 being displayed at the top of the analysis results log 14651. As shown in FIG. 14B-3, the analysis results history GUI 14650 can also be configured to display the analysis results log 14651 with only the "Best Day" analysis result cards 14400 (e.g., the previous "Best Day" analysis result cards 14400 and the most recent "Best Day" analysis result card 14400).

[0295] In some embodiments, a user may be able to select a particular "Best Day" analysis card 14400 or "Growth" analysis card 14500 from the analysis history GUI 14650. User selection of the "Best Day" analysis card 14400 or "Growth" analysis card 14500 outputs a report GUI 600 (e.g., FIGS. 6B-1 and 6B-2) associated with the particular day corresponding to the selected analysis card, or a home interface corresponding to that past day.

[0296] According to one aspect of the embodiment, the analysis results history GUI 14650 is configured to display the "Best Day" analysis result card 14400 and the "Growth" analysis result card 14500 for a period for which the TIR application has data. For example, if data necessary to output the "Best Day" analysis result card 14400 or the "Growth" analysis result card 14500 for the period from February 6, 2022 to March 26, 2022 is missing, the analysis results history GUI 14650 may display the historical "Best Day" analysis result card 14400 and the "Growth" analysis result card 14500 for March 27, 2022 to April 2, 2022, as well as the historical "Best Day" analysis result card 14400 and the "Growth" analysis result card 14500 for January 30, 2022 to February 5, 2022.

[0297] In some embodiments, as shown in FIG. 14B-2, if the analysis results are not yet available (e.g., if the first predetermined time period required to display the “Best Day” analysis results card 14400 has not yet elapsed, or the first “Latest” predetermined time period required to perform a comparison with the “Previous” predetermined time period required for the “Growth” analysis results card 14500 has not yet elapsed), the analysis results history GUI 14650 displays a message 14652 informing the user that the analysis results are not yet available. Additionally, in some embodiments, the analysis results history GUI 14650 may also notify the user that the analysis results will be available when the previous week's data is available. In some embodiments, as shown in FIGS. 14B-1 and 14B-2, the analysis results history GUI 14650 may include an information icon 14653 that, when selected by the user, may output an information modal display 14700 ( FIG. 14C ). The information modal display 14700 may inform the user that if analyte data (e.g., glucose data) is available for the previous predetermined period (e.g., the previous week), analysis results may be displayed at a predetermined frequency (e.g., every Sunday or every seven days), and that the user may select to receive notifications when new analysis result cards are posted. Additionally, in some embodiments, the information modal display 14700 may inform the user that the user may select to receive notifications when new analysis results are posted, and that analysis results history based on other predetermined periods (e.g., the past few weeks) is stored and may be reviewed at any time. In some embodiments, the information modal display 14700 may also note that the longer the user uses the continuous glucose monitoring application or TIR application, the more robust the analysis results will be. In some embodiments, the information modal display 14700 may include a selectable "Notification Preferences" link 14701.

[0298] As shown most clearly in FIG. 14B-1 , in some embodiments, the analysis results log 14651 is divided into multiple subsections 14654, with each subsection 14654 representing a different predetermined time period. For example, the analysis results log 14651 may be divided into subsections 14654 representing seven-day (one-week) periods. Thus, for each seven-day (one-week) period, a “Best Day” analysis result card 14400 and a “Growth” analysis result card 14500 are displayed in the subsection 14654 of the analysis results log 14651 that corresponds to that period. For example, the subsection 14654 relating to the period February 6, 2022 to February 12, 2022 displays the “Best Day” analysis result card 14400 and the “Growth” analysis result card 14500 that correspond to the period February 6, 2022 to February 12, 2022. The analysis results log 14651 may be scrollable, dynamic, or a combination of both. Thus, in some embodiments, the content displayed in the analysis results log 14651 may change in response to a twelfth predetermined user input. Examples of the twelfth predetermined user input include a predetermined user action such as scrolling, dragging, or pulling. In this manner, the analysis results history GUI 14650 may have multiple views, each configured to display a portion of the analysis results history GUI 14650 to the user, such that a different “Best Day” analysis results card 14400 and “Growth” analysis results card 14500 may be displayed for each view.

[0299] According to one aspect of the embodiment, the analysis results history GUI 14650 may include a timing message 14655 (FIGS. 14B-1 and 14B-2) informing the user that the analysis results will be released when the previous week's data is available.

[0300] 14A-1 to 14A-3, according to another aspect of the embodiment, the top meals section 14200 of the analysis results GUI 14000 may list the highest-scoring meal events 14202 logged over a predetermined period of time (e.g., one week or more, two weeks, several consecutive weeks, etc.). Referring to FIGS. 14A-1 and 14A-3, the meals in the meal list 14201 may be ordered in descending order of the numerical scores assigned to the meals, from highest score 14203 to lowest score 14203. The scores 14203 are assigned according to the analyte response based on data indicating the user's analyte levels. In some embodiments, the analyte response for each meal may be based on the change in analyte level within a predetermined time period after consuming that particular meal. In some embodiments, the score 14203 assigned to the meal event 14202 is based on the change in analyte levels from the glucose value at the time of ingestion of that particular meal to the peak glucose value within three hours after the meal. In some embodiments, the top meals section 14200 is configured to list a predetermined number of the highest-scoring meal events 14202 logged in a predetermined time period (e.g., the top meals section 14200 is configured to list up to three of the highest-scoring meal events 14202, i.e., the top three highest-scoring meal events 14202 logged in a predetermined time period).

[0301] In some embodiments, score 14203 can be a number from 1 to 5, with larger numbers representing smaller analyte responses and smaller numbers representing larger analyte responses. For example, as detailed above, (1) if the change in analyte level three hours after a meal is between 0 and 24 mg / dL, score 14203 can be "5," (2) if the change in analyte level three hours after a meal is between 25 and 49 mg / dL, score 14203 can be "4," (3) if the change in analyte level three hours after a meal is between 50 and 74 mg / dL, score 14203 can be "3," (4) if the change in analyte level three hours after a meal is between 75 and 99 mg / dL, score 14203 can be "2," and (5) if the change in analyte level three hours after a meal is 100 mg / dL or greater, score 14203 can be "1."

[0302] As shown in the analysis results GUI 14000 of FIGS. 14A-1 and 14A-3, the score 14203 may be represented by a graphical element such as a star icon 14204. In some embodiments, the star icon 14204 may be filled with a color, such as yellow. Additionally, in many embodiments (not shown), the star icon 14204 may be a hollow star with a dashed outline to indicate that the meal score 14203 is "no score." In some embodiments, although not shown, a meal score 14203 that is "no score" is indicated by the character "?". In some embodiments, the star icon 14204 may be filled with the character "?" instead of a numeric value to indicate that a particular meal was not assigned a score. Meal score 14203 will be "No Score" if (1) the user logs the next meal too early, or (2) the TIR (Time In Range) application does not have enough test substance data to score the meal (e.g., the user did not scan at the appropriate time and therefore did not receive confirmation that the glucose data was sent to the TIR (Time In Range) application), or if both (1) and (2) occur.

[0303] 14A-1 and 14A-3, according to another aspect of an embodiment, each meal event 14202 listed in the analysis results GUI 14000 provides detailed information about a particular meal consumed within a predetermined time period (e.g., one or more weeks, two weeks, several consecutive weeks, etc.). In some embodiments, as shown most clearly in FIG. 14A-3, each meal event 14202 may include a textual description 14205 of the meal, a photo (image) 14206 associated with the meal, a portion size indicator 14207 indicating the relative portion size, a score 14203 associated with the meal, or any combination thereof. Additionally or alternatively, as shown most clearly in FIG. 14A-3, in some embodiments, the meal event 14202 may also include one or more meal tags 14208 associated with the meal (e.g., “lettuce,” “blueberry,” “cheese,” etc.).

[0304] Referring to FIG. 14A-3, in one aspect of the embodiment, when a meal has been entered and scored, but analysis results are not yet available, the analysis results GUI 14000 is configured to display an analysis results section 14100 containing a message 14101 indicating that analysis results are not yet available, and a top meals section 14200 containing a list of meal information 14201.

[0305] According to another aspect of the embodiment, as shown in FIG. 14A-4, when no meals have yet been entered or scored, but analysis results are available, the analysis results GUI 14000 is configured to display an analysis results section 14100 that includes a "Best Day" analysis results card 14400, a "Growth" analysis results card 14500, or both, and a top meals section 14200 that includes a message 14210 indicating that no meals have yet been scored.

[0306] In some embodiments, as shown in FIG. 14A-4, if the user has not yet entered (logged) any meals, the analysis results GUI 14000 may include an analysis results section 14100 that includes a “Best Day” analysis results card 14400, a “Growth” analysis results card 14500, or both, and a top meals section 14200 that includes a message 14210 indicating that no meals have yet been scored.

[0307] Furthermore, according to one aspect of an embodiment, any of the meal events 14202 listed in the top meals section 14200 of the analysis results GUI 14000 may be configured to be selectable, and when a user selects a meal event 14202, a meal review GUI 800 (shown in FIG. 8 ) is output that provides detailed information related to the selected meal event 14202. In some embodiments (although not shown in FIG. 8 ), the meal review GUI 800 may include a “back” button that, when selected by the user, returns to the interface prior to selecting the particular meal event corresponding to the meal review GUI 800.

[0308] 14A-1 to 14A-4, the analysis result GUI 14000 may further include an "All Meals" link 14250. When a user selects this link, a meal GUI 14800 (shown in FIGS. 14D-1 to 14D-3) may be displayed to provide the user with further analysis results regarding the load of intake of specific foods. Referring to FIGS. 14D-1 and 14D-2, according to one aspect of the embodiment, the meal GUI 14800 includes a meal information list 14801 that includes all meal events 14802 logged during a predetermined period (e.g., one week or more, two weeks, several consecutive weeks, etc.) that is the same period during which the meal events 14202 shown in the analysis result GUI 14000 were logged. For example, if the top meals section 14200 of the analysis results GUI 14000 displays the highest-scoring meal event 14202 logged during a two-week period, the meals GUI 14800 is configured to display a list 14801 of all meal events 14802 logged during that two-week period. Specifically, like the meal events 14202 listed in the top meals section 14200 of the analysis results GUI 14000 (FIGS. 14A-1 and 14A-3), the meal events 14802 displayed on the meals GUI 14800 are ranked according to scores 14803 assigned based on the corresponding recorded test substance responses. In some embodiments, the meals in the meal list 14801 can be ordered from highest score 14803 to lowest score 14803. The scores 14803 are numerical values ​​assigned according to the test substance responses based on data indicating the user's test substance levels. In some embodiments, if two or more meals are assigned the same score 14803, the meals may be ordered in meal list 14801 according to their analyte level fluctuation values. For example, if two meals are assigned a score 14803 of "3," the meals may be ordered from smallest PeakDelta value (analyte level fluctuation value) to largest PeakDelta value (analyte level fluctuation value).Furthermore, in some embodiments, if there are two or more meals with the same score 14803 and the same test substance level fluctuation value, these meals can be arranged in chronological order.

[0309] In some embodiments, as shown most clearly in FIG. 14D-2, if a meal has been entered but not yet scored, the unscored meal event 14802 displayed in meal information list 14801 may either (1) include a hollow star icon 14804 with a dashed outline to indicate "no meal score," or in some cases (2) not include a star icon to indicate "no meal score."

[0310] In some embodiments, as shown most clearly in Figure 14D-3, if the user has not yet entered (logged) any meals, the Meals GUI 14800 displays a message 14805 informing the user that no meals have been scored yet. Additionally, in some embodiments, the Meals GUI 14800 also informs the user that a higher rating means they are more likely to stay within their goal range.

[0311] In some embodiments, as shown in Figures 14D-1 through 14D-3, the meal GUI 14800 further includes an information icon 14806 that, when selected, outputs a meal score information modal display containing information about how the TIR application has ranked and scored the meal. Additionally, in some embodiments, the meal score information modal display containing information about how the meal has been ranked may also include a pictogram indicating the glucose load.

[0312] According to another aspect of an embodiment, similar to the meal events 14202 listed in the analysis results GUI 14000 (most clearly illustrated in FIGS. 14A-1 and 14A-3), the meal events 14802 listed in the meal GUI 14800 also provide detailed information about specific meals consumed within a predetermined time period (e.g., one or more weeks, two weeks, several consecutive weeks, etc.). In some embodiments, as most clearly shown in FIG. 14D-1, each meal event 14802 displayed on the meal GUI 14800 may include a textual description 14815 of the meal, a photo (image) 14816 associated with the meal, a portion size indicator 14817 indicating the relative portion size, a score 14803 associated with the meal, or any combination thereof. Additionally or alternatively, in some embodiments, the meal event 14802 may also include one or more meal tags 14818 associated with the meal (e.g., “lettuce,” “blueberry,” “cheese,” etc.).

[0313] According to one aspect of the embodiment, when the user performs a ninth predetermined operation (e.g., a predetermined operation such as a pull down operation or a scroll operation on the meal GUI 14800), in response, the user can scroll the meal GUI 14800 to change the range of the list of meal events 14802 displayed on the meal GUI 14800.

[0314] 14D-1-14D-3, in some embodiments, the meal GUI 14800 may include an informational message 14807 informing the user that a higher score means a higher likelihood of staying within the goal range. The meal GUI 14800 may also include a "back" button 14809 that, when selected by the user, may output the analysis results GUI 14000 (see, e.g., FIGS. 14A-1-14A-4).

[0315] Furthermore, according to one aspect of an embodiment, any of the meal events 14802 listed in the meal GUI 14800 may be configured to be selectable, and when a user selects a meal event 14802, a meal review GUI 800 (shown in FIG. 8 ) is output that provides detailed information related to the selected meal event 14802. Although not shown in FIG. 8 , in some embodiments, the meal review GUI 800 may include a “back” button that, when selected by the user, outputs the interface prior to selecting the particular meal event corresponding to the meal review GUI 800.

[0316] According to one aspect of an embodiment, a notification 14900 regarding the analysis results may also be presented. As shown in FIG. 14E , this notification 14900 may be displayed to the user as a pop-up window or banner notification 14900 outside of the TIR application (e.g., on the lock screen). In some exemplary embodiments, when a new analysis results card is released, notification 14900 is displayed with a message informing the user that analysis of the user's data for a predetermined period of time (e.g., the last week) is complete. Furthermore, in some embodiments, notification 14900 may prompt the user to view the newly released analysis results card by tapping the notification.

[0317] Several embodiments have been described above, and various aspects of the present subject matter are presented below as a summary and / or supplement to the above. It should be noted that emphasis is placed on the interrelationship and interchangeability of the following embodiments. In other words, emphasis is placed on the fact that each feature of the multiple embodiments can be combined with any other feature unless otherwise explicitly stated or without logical justification. Although no explicit reference is made to the drawings below, the following paragraphs are a reprint and development of the embodiments described in this specification.

[0318] Provided herein are systems, devices, and methods for detecting, measuring, and classifying an individual's diet based on analyte measurements. Such results and related information can be presented to an individual to indicate which meals are causing the most severe analyte responses. Such results can be organized and categorized based on preselected criteria or previous meals and results, thereby allowing such results to be organized and presented in a format relative to the monitored analyte, glucose. Various embodiments disclosed herein relate to methods, systems, and software applications designed to engage individuals by providing timely, direct feedback regarding their diet-related analyte responses.

[0319] It should be noted that all features, elements, components, functions, and steps described in the description of any embodiment described herein are intended to be freely combinable and interchangeable with features, elements, components, functions, and steps of any other embodiment. Furthermore, if a particular feature, element, component, function, or step is described only in the description of one embodiment, it should be understood that the feature, element, component, function, or step can also be used in all other embodiments described herein, unless expressly stated otherwise. Therefore, even if the following description does not explicitly state that features, elements, components, functions, and steps can be combined between different embodiments or interchanged between embodiments as specific examples, this paragraph serves as a preface and supporting description that allows claims incorporating such combinations or interchanges to be added at any time. It is clearly recognized that explicitly describing every possible combination or interchangeability would be an undue burden, especially considering that one skilled in the art would readily recognize the permissibility of all such combinations and interchangeability.

[0320] Memory, storage, and / or computer-readable medium are non-transitory to the extent that embodiments disclosed herein include (or operate in conjunction with) memory, storage, and / or computer-readable medium. Accordingly, memory, storage, and / or computer-readable medium are only non-transitory to the extent that one or more claims about the memory, storage, and / or computer-readable medium are encompassed by the memory, storage, and / or computer-readable medium.

[0321] In many cases, entities are described herein as being coupled to different entities. As used herein, the terms "coupled," "associated," and "connected" (or any variations thereof) are used interchangeably and should be understood as generic terms that refer to a direct coupling of two entities (without significant (e.g., parasitic) intervening entities) and an indirect coupling of two entities (through one or more negligible intervening entities). When entities are shown as being directly coupled, or when entities are described as being coupled without any intervening entities, it should be understood that the entities may also be indirectly coupled, unless the context clearly dictates otherwise.

[0322] As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include reference to the corresponding plural forms unless the context clearly dictates otherwise.

[0323] The publications referenced herein are provided solely for their disclosure prior to the filing date of the present application. Nothing herein should be construed as an admission that the present disclosure is not entitled to antedate such publication by virtue of prior disclosure of such publication. Further, the dates of publication provided herein may be different from the actual publication dates, which may need to be independently confirmed.

[0324] While the embodiments are susceptible to various modifications and variations, specific examples thereof have been shown in the drawings and are described in detail herein. These embodiments are not limited to the particular forms disclosed; on the contrary, these embodiments encompass all modifications, equivalents, and alternatives that do not depart from the spirit of the invention. Furthermore, any feature, function, step, or element of the embodiments may be recited or included in the claims, and the claims may also be defined by negative limitations of any feature, function, step, or element not included in the claims.

[0325] The present disclosure also includes systems, devices, and methods for detecting and measuring the length of time an individual's analyte levels have been within a predetermined range based on analyte measurements. Presenting these results and related information to the individual reveals to the individual the analyte response associated with the intake of a meal, i.e., the change in analyte level within a predetermined time period after ingestion of the meal. These results can also be organized in a ranking format to allow the individual to visualize the analyte response and impact on TIR associated with the meal. Various embodiments disclosed herein relate to methods, systems, and software applications designed to engage individuals by providing timely, direct feedback regarding their diet-related analyte response.

[0326] The disclosure of this application also includes the subject matter set forth in the following numbered sections:

[0327] Section 1 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by the user; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; outputting a home graphical user interface (GUI); Execute the home GUI: a glucose graph card including a glucose graph having a glucose trend line reflecting the data showing the glucose level; a logbook section having a list including the meal information, the list configured to display the one or more meal events and the corresponding score associated with each of the one or more meal events; and a meal rating average card configured to display a meal rating average, said meal rating average being based on an average of meal event scores for a plurality, optionally all, of said one or more meal events over a predetermined time period; 1. A glucose monitoring system comprising:

[0328] Section 2 the sensor control device is configured to collect the data indicative of the glucose level of the user; 2. The glucose monitoring system of claim 1, wherein the sensor control device comprises a glucose sensor, at least a portion of the glucose sensor configured to be in fluid contact with the user's bodily fluids.

[0329] Section 3 3. The glucose monitoring system of claim 1 or 2, wherein the score is a first assigned numerical value assigned according to the glucose response based on the data indicating the glucose levels associated with each of the one or more meal events.

[0330] Section 4 4. The glucose monitoring system of claim 3, wherein the data indicative of the glucose level is the change in glucose level within a predetermined time period after the user ingests each of the one or more meals.

[0331] Section 5 5. The glucose monitoring system of claim 3 or 4, wherein for each of the one or more meals, a larger first assigned number represents a smaller glucose response associated with the corresponding meal.

[0332] Section 6 A glucose monitoring system as described in any of paragraphs 3 to 5, wherein for each of the one or more meals, the smaller the first assigned numerical value, the greater the glucose response associated with the corresponding meal.

[0333] Section 7 7. The glucose monitoring system o...

Claims

1. 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by the user; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; outputting a home graphical user interface (GUI); Execute The home GUI: a glucose graph card including a glucose graph having a glucose trend line reflecting the data showing the glucose level; a logbook section having a list including the meal information, the list configured to display the one or more meal events and the corresponding score associated with each of the one or more meal events; and a meal rating average card configured to display a meal rating average, said meal rating average being based on an average of meal event scores for a plurality, optionally all, of said one or more meal events over a predetermined time period; A glucose monitoring system comprising at least one of:

2. the sensor control device is configured to collect the data indicative of the glucose level of the user; The glucose monitoring system of claim 1 , wherein the sensor control device comprises a glucose sensor, at least a portion of the glucose sensor configured to be in fluid contact with the user's bodily fluids.

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

4. The glucose monitoring system of claim 3 , wherein the data indicative of the glucose level is a change in glucose level within a predetermined time period after the user ingests each of the one or more meals.

5. 4. The glucose monitoring system of claim 3, wherein for each of the one or more meals, a larger first assigned numerical value represents a smaller glucose response associated with the corresponding meal.

6. 4. The glucose monitoring system of claim 3, wherein for each of the one or more meals, a smaller first assigned numerical value represents a greater glucose response associated with the corresponding meal.

7. The glucose monitoring system of claim 3 , wherein the first assigned value can be any number from 1 to 5.

8. the logbook section displays one or more star icons; The glucose monitoring system of claim 3 , wherein each of the one or more star icons includes the score associated with the corresponding one or more meal events.

9. 2. The glucose monitoring system of claim 1, wherein the meal rating average is a second assigned numerical value corresponding to an average of the meal event scores of a plurality, optionally all, of the one or more meal events in the predetermined time period.

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

11. 10. The glucose monitoring system of claim 9, wherein a larger second assigned number represents a smaller corresponding average glucose response.

12. 10. The glucose monitoring system of claim 9, wherein a smaller second assigned number represents a larger corresponding average glucose response.

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

14. the graphical display includes a dietary rating average display; The glucose monitoring system of claim 13 , wherein the meal rating average display is configured to visually represent the meal rating average obtained over the predetermined time period.

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

16. 10. The glucose monitoring system of claim 1, wherein the meal rating average is configured to be continually updated to account for each of the one or more meal events as they are assigned scores.

17. 2. The glucose monitoring system of claim 1, wherein the home GUI further comprises a notification card having a message indicating to the user that an initial score has been achieved the first time a meal event is scored among the one or more meal events in the predetermined time period.

18. The glucose monitoring system of claim 1 , wherein the meal rating average is not displayed if none of the one or more meal events in the predetermined time period have yet been assigned a score.

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

20. 10. The glucose monitoring system of claim 1, wherein the glucose graph comprises an x-axis in units of time and a y-axis in units of measurement associated with the data indicating the glucose level.

21. 2. The glucose monitoring system of claim 1, wherein the home GUI further includes one or more selectable icons configured to allow the user to select from predefined lengths of time for which the user's data showing the glucose level is displayed on the glucose graph card.

22. 22. The glucose monitoring system of claim 21, wherein the one or more selectable icons are configured to allow the user to select from the predefined time lengths of 4 hours, 12 hours, or 24 hours.

23. the home GUI further includes a selectable analysis result icon; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: and responsive to selection of the analysis result icon, outputting an analysis result GUI configured to provide the user with information regarding the user's performance relative to a baseline. The glucose monitoring system of claim 1 further comprising:

24. 24. The glucose monitoring system of claim 23, wherein the criterion is a meal assessment average criterion.

25. 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by the user; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, based on the dietary information and the data indicative of the glucose level, a growth of the user based on a standard relating to the dietary information and the data indicative of the glucose level for a predetermined period of time; outputting an analysis result graphical user interface (GUI); Execute The analysis result GUI comprises: an analysis results section including one or more analysis results cards, each of the one or more analysis results cards including statistics regarding the user's growth; and a meals section including a list of the meal information, the list configured to display one or more meal events, each of the one or more meal events displayed in the list configured to reflect data indicative of a glucose response associated with each of the one or more meals. A glucose monitoring system comprising at least one of:

26. The criteria are related to the dietary rating average, the meal rating average corresponds to an average of one or more scores of the one or more meal events; 26. The glucose monitoring system of claim 25, wherein each of the one or more scores is a score assigned according to a glucose response based on the data indicative of the glucose level associated with the corresponding one or more meal events.

27. 26. The glucose monitoring system of claim 25, wherein one of the one or more analysis result cards includes a summary message including statistics related to the day on which the user achieved the highest average meal rating during the predetermined period.

28. each of the one or more meal events includes a score; 26. The glucose monitoring system of claim 25, wherein the score is a numerical value assigned according to the data indicative of the glucose response associated with each of the one or more meal events.

29. for each of the one or more meals, a larger assigned numerical value represents a smaller glucose response associated with the corresponding meal; 30. The glucose monitoring system of claim 28, wherein for each of the one or more meals, a smaller assigned numerical value represents a greater glucose response associated with the corresponding meal.

30. means for receiving data indicative of the glucose level from the sensor control device; means for receiving dietary information indicative of one or more meals consumed by the user; means for determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; means for outputting a home graphical user interface (GUI); An apparatus comprising: The home GUI: a glucose graph card including a glucose graph having a glucose trend line reflecting the data showing the glucose level; a logbook section having a list including the meal information, the list configured to display the one or more meal events and the corresponding score associated with each of the one or more meal events; and a meal rating average card configured to display a meal rating average, said meal rating average being based on an average of meal event scores for a plurality, optionally all, of said one or more meal events over a predetermined time period; 10. An apparatus comprising:

31. means for receiving data indicative of the glucose level from the sensor control device; means for receiving dietary information indicative of one or more meals consumed by the user; means for determining, based on the dietary information and the data indicative of the glucose level, the user's progress based on a standard relating to the dietary information and the data indicative of the glucose level for a predetermined period of time; means for outputting an analysis result graphical user interface (GUI); An apparatus comprising: The analysis result GUI comprises: an analysis results section including one or more analysis results cards, each of the one or more analysis results cards including statistics regarding the user's growth; and a meals section including a list of the meal information, the list configured to display one or more meal events, each of the one or more meal events displayed in the list configured to reflect data indicative of a glucose response associated with each of the one or more meals; 10. An apparatus comprising:

32. receiving meal information input by a user; receiving data indicative of a glucose level within a predetermined length of time; identifying a peak glucose level; identifying an initial glucose level; determining a glucose level fluctuation value; associating the input meal information with the glucose level fluctuation value; assigning a score to a meal associated with the input meal information; A method comprising:

33. receiving a predetermined input from a user on a toggle switch adjacent to a textual representation of the current day of the week on the interface; a step in which the user selects a particular ring from a plurality of rings displayed in response to the user switching the toggle switch, each of the plurality of rings being a TIR display corresponding to a different day in the past week; identifying, by at least one processor, a set of data indicative of glucose levels and meal information associated with a day corresponding to the particular selected ring based on data stored in a database; providing, on a display device, an interactive report graphical user interface (GUI) configured to display data indicative of the glucose level and the set of meal information based on the identifying step, The report GUI: TIR card, a glucose graph card reflecting data showing glucose levels for the time period corresponding to the particular ring selected; and a meal list reflecting meal information for the period corresponding to the selected specific ring; The method is configured to display one or more of:

34. Identifying the starting point of the fluctuation; identifying an end point of the variation; calculating an activation window, which is the time from the start point of the variation to the end point of the variation; identifying a minimum glucose level for threshold comparison; identifying a highest glucose level for threshold comparison; identifying a time interval for threshold comparison; A method comprising:

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

36. 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by the user; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting a first deviation in the data indicative of the glucose level, the first deviation being associated with a first meal consumed by a user, and meal information relating to the first meal consumed that is associated with the first deviation not yet received by the input unit; outputting a home graphical user interface (GUI), the home GUI comprising: a glucose graph card including a glucose graph having a glucose trend line reflecting the data showing the glucose level; and a logbook section having a list containing said meal information; and responsive to detecting the first deviation, displaying a first notification associated with the first deviation on the home GUI; If the first deviation is detected, in response thereto, further displaying a first deviation mark associated with the detected first deviation on the glucose graph card; A glucose monitoring system.

37. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; 37. The glucose monitoring system of claim 36, further comprising:

38. The home GUI: a meal rating average card configured to display a meal rating average, said meal rating average being based on an average of meal event scores for a plurality, optionally all, of said one or more meal events over a predetermined time period; 38. The glucose monitoring system of claim 37, further comprising:

39. 37. The glucose monitoring system of claim 36, wherein the first notification is located in a location between the glucose graph card and the logbook section of the home GUI.

40. 37. The glucose monitoring system of claim 36, wherein the first notification includes a query that asks the user a question regarding the consumption of the first meal.

41. 37. The glucose monitoring system of claim 36, wherein the first notification includes a message providing the user with information regarding the first deviation and the data indicative of the glucose level.

42. the first notification further comprises a selectable meal logging button; the reading device further comprises a touch panel screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: outputting a meal logging GUI in response to the user selecting the selectable meal logging button.

37. The glucose monitoring system of claim 36, further comprising:

43. the first notification further comprises a selectable meal logging button; the reading device further comprises a touch panel screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: and responsive to the user selecting the selectable meal log button, outputting a meal entry input modal display including a time field pre-populated with a date and time associated with the detected first deviation.

37. The glucose monitoring system of claim 36, further comprising:

44. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: removing the first notification from the home GUI in response to the user logging the first ingested meal associated with the detected first deviation.

37. The glucose monitoring system of claim 36, further comprising:

45. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to the user logging the first ingested meal associated with the detected first deviation, removing the first notification from the home GUI; replacing the first deviation mark with a meal icon; 37. The glucose monitoring system of claim 36, further comprising:

46. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to the user logging the first ingested meal associated with the detected first deviation, removing the first notification from the home GUI; replacing the first deviation mark with a meal icon; displaying an entry for the first ingested meal associated with the detected first deviation in the logbook section; 37. The glucose monitoring system of claim 36, further comprising:

47. 37. The glucose monitoring system of claim 36, wherein the first deviation mark is displayed on the glucose trend line.

48. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: removing the first notification and the first deviation mark from the home GUI after a predetermined period of time has elapsed.

37. The glucose monitoring system of claim 36, further comprising:

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

50. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting a second deviation in the data indicative of the glucose level, the second deviation being associated with a second meal consumed by the user, and meal information relating to the second meal consumed that is associated with the second deviation not yet received by the input unit; responsive to the second deviation being detected, displaying a second notification associated with the second deviation on the home GUI; If the second deviation is detected, in response thereto, further displaying a second deviation mark associated with the detected second deviation on the glucose graph card; 37. The glucose monitoring system of claim 36, further comprising:

51. 51. The glucose monitoring system of claim 50, wherein the first notification is stacked with the second notification on the home GUI.

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

53. the first notice includes a first page number; 51. The glucose monitoring system of claim 50, wherein the second notification includes a second page number.

54. the second notification includes a selectable "ignore" button; the reading device further comprises a touch panel screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: and in response to the user selecting the "ignore" button, removing the second notification from the home GUI and displaying only the first notification.

51. The glucose monitoring system of claim 50, further comprising:

55. 1. A glucose monitoring system comprising: The glucose monitoring system comprises: a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; outputting a home graphical user interface (GUI); Execute The home GUI: glucose graph card, a logbook section having a list configured to display the one or more meal events and the corresponding score associated with each of the one or more meal events; and a dining rating average card configured to display information associated with at least one of the one or more dining events for a predetermined time period; A glucose monitoring system comprising at least one of:

56. 1. A glucose monitoring system comprising: The glucose monitoring system comprises: a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input configured to receive dietary information indicative of one or more meals consumed by the user; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: determining, based on the dietary information and the data indicative of the glucose level, a growth of the user based on a standard relating to the dietary information and the data indicative of the glucose level for a predetermined period of time; outputting an analysis result graphical user interface (GUI); Execute The analysis result GUI comprises: an analytics section containing statistics regarding the user's growth based on the criteria; and a meals section including a list of the meal information, the list configured to reflect data indicative of a glucose response associated with each of the one or more meals consumed by the user; A glucose monitoring system comprising at least one of:

57. 1. A glucose monitoring system comprising: The glucose monitoring system comprises: a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting a first deviation in the data indicative of the glucose level, the first deviation being associated with a first meal consumed by a user, and meal information relating to the first meal consumed that is associated with the first deviation not yet received by the meal monitoring application; outputting a graphical user interface (GUI), said GUI comprising: glucose graph card, and a logbook section having a list containing said meal information; and responsive to the first deviation being detected, displaying a first notification associated with the first deviation on the GUI; If the first deviation is detected, in response thereto, further displaying a first deviation mark associated with the detected first deviation on the glucose graph card; A glucose monitoring system.

58. 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input unit configured to receive meal information; one or more processors coupled to a memory storing a first meal monitoring application; Equipped with When the first meal monitoring application is executed by the one or more processors, the first meal monitoring application causes the one or more processors to: determining a length of time the data indicative of the glucose level was within a predetermined glucose range; outputting a home graphical user interface (GUI); Execute The home GUI: a time-in-range (TIR) ​​card including a graphical element indicating the length of time the data indicating the glucose level was within the predetermined glucose range; and a list including the meal information, the list configured to display one or more meal events, each of the one or more meal events including a score based on a glucose response associated with the meal and the data indicating the glucose level. A glucose monitoring system comprising at least one of:

59. 1. A glucose monitoring system comprising: The glucose monitoring system includes a reading device; The reading device a wireless communication circuit configured to receive data indicative of the glucose level from the sensor control device; an input unit configured to receive meal information; one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: identifying a peak glucose level; identifying an initial glucose level; determining a glucose level fluctuation value based on the peak glucose level value and the initial glucose level value; associating said meal information with said glucose level variability; assigning a score to a meal based on the associated meal information and the glucose level variability value; outputting a home graphical user interface (GUI) having a list including the meal information on a display; Execute A glucose monitoring system, wherein the list includes the meals and the assigned scores.

60. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: making an adjustment to the glucose level fluctuation value based on a function of the initial glucose level value; 60. The glucose monitoring system of claim 59, further comprising:

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

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

63. 63. The glucose monitoring system of claim 62, wherein the first variable and the second variable are respective weighted averages based on multiple eating instances of the same meal.

64. 61. The glucose monitoring system of claim 60, wherein the function of the initial glucose level is a logistic function.

65. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: performing one or more data validity checks before making any adjustments to the glucose level variation values.

61. The glucose monitoring system of claim 60, further comprising:

66. 66. The glucose monitoring system of claim 65, wherein the one or more data validity checks include a first data validity check that determines whether data indicative of the glucose level is available that is a predetermined minimum amount of data associated with fluctuations in glucose level.

67. 67. The glucose monitoring system of claim 66, wherein the one or more data validity checks include a second data validity check that determines whether a period prior to a meal tag within a fluctuation period includes pre-meal data indicating a predetermined minimum amount of the glucose level.

68. means for receiving data indicative of the glucose level from the sensor control device; means for receiving dietary information indicative of one or more meals consumed by the user; means for detecting a first deviation from the data indicative of the glucose level, the first deviation being associated with a first meal ingested by a user, and meal information relating to the first ingested meal associated with the first deviation not yet received by the means for receiving meal information; means for outputting a home graphical user interface (GUI), the home GUI comprising: a glucose graph card including a glucose graph having a glucose trend line reflecting the data showing the glucose level; and a logbook section having a list containing said meal information; and means for displaying a first notification associated with the first deviation on the home GUI in response to the first deviation being detected; means for displaying, in response to the first deviation being detected, a first deviation mark associated with the detected first deviation on the glucose graph card; An apparatus comprising:

69. means for receiving data indicative of the glucose level from the sensor control device; means for determining, for each of one or more meal events, a score assigned according to a glucose response based on the data indicative of the glucose level associated with each of the one or more meal events; means for outputting a home graphical user interface (GUI); An apparatus comprising: The home GUI: glucose graph card, a logbook section having a list configured to display the one or more meal events and the corresponding score associated with each of the one or more meal events; and a dining rating average card configured to display information associated with at least one of the one or more dining events for a predetermined time period; 10. An apparatus comprising:

70. means for receiving data indicative of the glucose level from the sensor control device; means for receiving dietary information indicative of one or more meals consumed by the user; means for determining, based on the dietary information and the data indicative of the glucose level, the user's progress based on a standard relating to the dietary information and the data indicative of the glucose level for a predetermined period of time; means for outputting an analysis result graphical user interface (GUI); An apparatus comprising: The analysis result GUI comprises: an analytics section containing statistics regarding the user's growth based on the criteria; and a meals section including a list of the meal information, the list configured to reflect data indicative of a glucose response associated with each of the one or more meals consumed by the user; 10. An apparatus comprising:

71. means for receiving data indicative of the glucose level from the sensor control device; means for detecting a first deviation in the data indicative of the glucose level, the first deviation being associated with a first meal consumed by a user, and meal information relating to the first meal consumed that is associated with the first deviation not yet received by a meal monitoring application; A means for outputting a graphical user interface (GUI), the GUI comprising: glucose graph card, and a logbook section having a list containing said meal information; and means for displaying a first notification associated with the first deviation on the GUI in response to the first deviation being detected; means for displaying, in response to the first deviation being detected, a first deviation mark associated with the detected first deviation on the glucose graph card; An apparatus comprising:

72. means for receiving data indicative of the glucose level from the sensor control device; a means for receiving dietary information; means for determining the length of time the data indicative of the glucose level was within a predetermined glucose range; means for outputting a home graphical user interface (GUI); An apparatus comprising: The home GUI: a time-in-range (TIR) ​​card including a graphical element indicating the length of time the data indicating the glucose level was within the predetermined glucose range; and a list including the meal information, the list configured to display one or more meal events, each of the one or more meal events including a score based on a glucose response associated with the meal and the data indicating the glucose level.

10. An apparatus comprising:

73. means for receiving data indicative of the glucose level from the sensor control device; means for receiving dietary information indicative of one or more meals consumed by the user; means for identifying a postprandial glucose trajectory associated with each of the one or more meals based on the meal information and the data indicative of the glucose levels; means for outputting a glucose graph graphical user interface (GUI); An apparatus comprising: The glucose graph GUI comprises: a glucose graph card including a glucose graph having a glucose trend line configured to reflect the data indicative of the glucose level, the glucose trend line further configured to reflect the post-prandial glucose trajectory associated with each of the one or more meals; and a list of meal information, the list configured to display one or more meal events, each of the one or more meal events displayed in the list configured to reflect data indicative of a glucose response associated with each of the one or more meals; 10. An apparatus comprising:

74. means for receiving data indicative of the glucose level from the sensor control device; a means for receiving dietary information; means for identifying peak glucose levels; means for identifying an initial glucose level; means for determining a glucose level fluctuation value based on the peak glucose level value and the initial glucose level value; means for relating said meal information to said glucose level variability; means for assigning a score to a meal based on the associated meal information and the glucose level variability value; means for outputting a home graphical user interface (GUI) having a list including the meal information on a display; An apparatus comprising: The list includes the meal and the assigned score.

75. receiving data indicative of a glucose level from a sensor control device; receiving meal information; identifying a peak glucose level; identifying an initial glucose level; determining a glucose level fluctuation value based on the peak glucose level value and the initial glucose level value; associating said meal information with said glucose level variability; assigning a score to a meal based on the associated meal information and the glucose level variability value; outputting a home graphical user interface (GUI) having a list including the meal information on a display; A method comprising: The method, wherein the list includes the meals and the assigned scores.

Images