Systems, devices, and methods for range-based time and meal-related analyte monitoring

Abstract

Systems, apparatus, and methods for detecting and measuring the effects of diet and / or the amount of time an individual spends within a predetermined analyte range, based on analyte measurements. These results and related information are presented to the individual to show them the analyte response associated with the consumed diet, or changes in analyte levels over a predetermined time period following the consumption of the diet. These results may be organized based on ranking or scoring systems to allow individuals to visualize their diet-related analyte response and range effects. Various embodiments disclosed herein relate to methods, systems, and software applications designed to engage individuals by providing direct and timely feedback on their diet-related analyte responses.

Description

Technical Field

[0001] The topics described herein generally relate to computational interfaces for analyte monitoring systems, as well as related systems, methods, and apparatuses. Specifically, this document discloses various implementations of time-in-range (TIR) ​​and diet-related graphical user interfaces and related methods for analyte monitoring systems. Background Technology

[0002] The rising prevalence of type 2 diabetes and metabolic syndrome over the past few decades has been attributed to changes in diet and activity levels. For example, consuming more readily available high-glycemic index foods can lead to a rapid increase in postprandial blood glucose and insulin levels, which is positively correlated with weight gain and obesity. These conditions can be further traced back to an increased risk of developing these and other diseases.

[0003] Most people generally understand the importance of their diet. However, in practice, many struggle to translate this general awareness into concrete food choices. These problems stem primarily from the inability to directly perceive the impact of their choices. This can lead to misunderstandings about portion sizes, which foods are relatively healthy, and a lack of general awareness of the duration and intensity of activities necessary to maintain health. Advertising, habits, peer pressure, food preferences, and generalized recommendations further exacerbate these issues.

[0004] To address these issues, analyte monitoring systems can be used to track and better understand individual physiological responses. Since high glucose levels are primarily driven by food consumption, postprandial glucose levels can be correlated with the amount of carbohydrates and other dietary components consumed by an individual, as well as with their physiological response to the diet. However, a challenge in analyzing this data influx is representing the data in a meaningful way to enable effective action. Data related to dietary choices and their subsequent effects should be understood on both a clinical and individual basis so that individuals, diet managers, and / or healthcare professionals can understand and regulate glucose shifts, such as hyperglycemic episodes.

[0005] Studies have shown that individuals who maintain their analyte levels within the target analyte range are more likely to experience positive health outcomes. Therefore, it would be beneficial to provide individuals with user-friendly and actionable information about the amount of time spent within the target analyte range, the impact of their dietary intake on their corresponding analyte levels, and means to incentivize and encourage them to make beneficial food choices.

[0006] Existing systems for tracking dietary consumption and correlating it with an individual's analyte data have several shortcomings. For example, some systems require individuals to perform numerous inconvenient and uncomfortable discrete blood glucose measurements (e.g., finger-prick glucose tests). These solutions may fail to adequately determine the glycemic response to a diet due to an insufficient number of data points. For instance, an individual may perform discrete blood glucose measurements sometime before or after the time when the user's glycemic response peaks, making it difficult to accurately identify the glycemic response and to meaningfully compare diets based on it. The lack of data points may also make it difficult to detect dietary events in the user's analyte data. Consequently, some existing systems rely heavily on users manually recording their meals. Furthermore, many existing systems that seek to detect dietary events solely based on the presence of elevated glucose levels are insufficient because they fail to account for the user's previous dietary history and may therefore overestimate the amount of food consumed.

[0007] Therefore, there is a need for improved systems, apparatus, and methods for collecting dietary information, assessing and detecting diets, and relating them to analyte levels. Specifically, there is a need for robust, user-friendly graphical user interfaces for analyte monitoring systems, as well as related methods and apparatus, that allow individuals to understand analyte responses and analyte range effects associated with their consumed diets. Summary of the Invention

[0008] Aspects of the invention are set forth in the independent claims, and preferred features are set forth in the dependent claims. Features associated with one aspect may be applied individually or in combination to the other aspects. Example embodiments of systems, apparatuses, and methods for detecting and measuring an individual's time-varying duration within a predetermined analyte range based on analyte measurements are provided herein. Example embodiments of systems, apparatuses, and methods for detecting, measuring, and ranking an individual's diet based on analyte measurements are also provided herein. In many embodiments, these results and related information are presented to the individual to show the individual the analyte response associated with the consumed diet, or the change in analyte levels over a predetermined time period following the consumption of the diet. These individuals may be those who exhibit or have been diagnosed with diabetes, those who are considered to have prediabetes, those who have metabolic syndrome, and even those who do not have symptoms of diabetes, prediabetes, or metabolic syndrome. These individuals may be anyone who improves his or her health by adjusting his or her diet and / or activity practices. The resulting information may be presented to the individual to show which diets or aspects of diet have the greatest impact on analyte levels.

[0009] In many implementations, an individual's diet-related analyte response (e.g., glucose response) is based on analyte data (e.g., glucose data) collected by an analyte monitoring system (e.g., a glucose monitoring system) (such as an in vivo analyte monitoring system (e.g., an in vivo glucose monitoring system)). These responses can be compared or linked to dietary information to identify common consistency (or inconsistency) and trends based on relevant historical glucose readings and correlation algorithms and comparisons.

[0010] Many of the embodiments disclosed herein are designed to engage individuals by providing direct and timely feedback on their diet-related analyte responses. In some embodiments, the analyte response may be provided to the individual in an easily understandable format to characterize the impact of dietary consumption.

[0011] Many implementations can immediately inform individuals, thereby encouraging them to take action to better understand how their own diet affects their body's analyte response. Many implementations can also organize data based on changes in individual analyte levels detected over a predetermined period after a meal, such as ranking meals. Individuals can compare and contrast their current and historical analyte data to understand how their efforts relate to better diets and meal choices, and how these choices directly impact their health. Individuals can also better understand how specific food choices can help them stay within target ranges for analyte values ​​and visualize the impact of analyte responses and ranges associated with specific foods. In this way, individuals are motivated to stay within target analyte ranges.

[0012] Many of the implementations described herein are improved graphical user interfaces (GUIs) or GUI features for analyte monitoring systems that are highly intuitive, user-friendly, and provide rapid access to an individual's physiological information. More specifically, these implementations allow individuals to easily navigate between different user interfaces that can quickly indicate various physiological conditions and / or actionable responses to the user, and correlate analyte data with diet, exercise, stress, or other factors, without requiring the user (or HCP) to perform the arduous task of examining large amounts of analyte data.

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

[0014] The aspects described and claimed herein contribute to improvements in the GUI that result in at least the ability of users of the assistive device to operate it more accurately, efficiently, and safely. It will be understood that the information provided to an individual on the GUI, the order in which that information is provided, and the clarity of its structure can significantly influence how the individual interacts with the system and how the system operates. Therefore, the GUI, in the technical task of the operating system, guides the individual to accurately and efficiently acquire necessary readings and / or obtain information.

[0015] Other systems, apparatuses, methods, features, and advantages of the subject matter described herein will be apparent to those skilled in the art upon examination of the following figures and detailed description. All such additional systems, apparatuses, methods, features, and advantages are included within the scope of the subject matter described herein and are protected by the appended claims. Where these features are not expressly set forth in the claims, the features of the exemplary embodiments should in no way be construed as limiting the appended claims. Attached Figure Description

[0016] By studying the accompanying drawings, the details of the subject matter described herein (both regarding its structure and operation) can be readily apparent, in which similar reference numerals refer to similar components. The components in the drawings are not necessarily drawn to scale, but rather to emphasize the principles of the subject matter. Furthermore, all illustrations are intended to convey concepts, where relative sizes, shapes, and other detailed attributes are depicted schematically rather than literally or precisely.

[0017] Figure 1 This is a system overview of the analyte monitoring system, which includes a sensor applicator, a sensor control device, a reader device, a network, a trusted computer system, and a local computer system.

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

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

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

[0021] Figure 4A-1 This is a flowchart depicting an example implementation of a method for associating analyte data with dietary information and ranking the dietary information.

[0022] Figure 4A-2 and Figure 4A-3 It is a graph depicting the trajectory of glucose after a meal.

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

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

[0025] Figure 4A-6 This is a flowchart depicting an example implementation of a method for calculating a user's blood glucose control over a predetermined time period.

[0026] Figure 4B This is a block diagram depicting an example implementation of the homepage GUI.

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

[0028] Figures 4D to 4N This is a block diagram depicting an example implementation of the homepage GUI, modalities, and their related features.

[0029] Figures 5A to 5N This is a block diagram depicting an example implementation of a diet record GUI and modal.

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

[0031] Figure 6B-1 and Figure 6B-2 This is a block diagram depicting an example implementation of the reporting GUI.

[0032] Figure 7 This is a block diagram depicting an example implementation of a GUI that illustrates the effects of diet.

[0033] Figures 8A to 8E This is a block diagram depicting an example implementation of a dietary review GUI.

[0034] Figures 9A to 9Q-4 This is a block diagram depicting an example implementation of a beginner-friendly GUI and its related features.

[0035] Figures 10A to 10M This is a block diagram depicting an example implementation of the account and settings GUI and its related features.

[0036] Figures 11A to 11G This is a block diagram depicting an example implementation of a data loss GUI and its features.

[0037] Figures 12A-1 to 12D-2 This is a block diagram depicting an example implementation of an interface including activity cards and features.

[0038] Figure 13A This is a flowchart depicting an example implementation of a method for dietary testing.

[0039] Figure 13B This is a flowchart depicting an example implementation of a method for determining a customized time window for a user's expected consumption of one or more meals based on historical data.

[0040] Figure 13C-1 to Figure 13E-5 This is a block diagram depicting an example implementation of a dietary detection interface and its features.

[0041] Figure 14 This is a flowchart depicting an example implementation of a method for identifying time periods of influence of high and low analyte levels based on user dietary shifts.

[0042] Figures 14A-1 to 15B This is a block diagram depicting an example implementation of the insight interface and features. Detailed Implementation

[0043] This document provides example implementations of systems, apparatus, and methods for monitoring and measuring an individual's analyte response to diet. Specifically, based on the collected analyte data, diet-related events and their impact on an individual's analyte levels can be further understood by the user and ultimately used to modify future dietary choices and eating habits.

[0044] Before describing the subject matter in more detail, it is worthwhile to describe exemplary implementations of systems, apparatuses, and methods that can implement the subject matter.

[0045] Several systems have been developed to automatically monitor analytes, such as glucose, in bodily fluids (e.g., blood flow), interstitial fluid (“ISF”), dermal fluid, or other biological fluids. Some of these systems are configured such that at least a portion of the sensor is positioned below the surface of the user’s skin (e.g., in the user’s blood vessels or subcutaneous tissue) to obtain information about at least one analyte in the body.

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

[0047] In vivo analyte monitoring systems can be distinguished from "in vitro" systems, which contact biological samples outside the body (or more precisely, "ex vivo") and typically include a meter device with a port for receiving an analyte test strip carrying the user's bodily fluids. This test strip can be analyzed to determine the user's blood glucose levels. While in many of these embodiments, monitoring is performed in vivo, the embodiments disclosed herein can be used with in vivo analyte monitoring systems that incorporate in vitro capabilities, as well as purely in vitro or ex vivo analyte monitoring systems.

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

[0049] In vivo monitoring systems may also include means for receiving sensed analyte data from sensor control devices and processing and / or displaying the sensed analyte data to a user in any quantity or form. Such means and variations thereof may be referred to as a “reader device” (or simply “reader”), a “handheld electronics” (or “handheld”), a “portable data processing” device or unit, a “data receiver”, a “receiver” device or unit (or simply “receiver”), or a “remote” device or unit, to name just a few. Other means, such as personal computers, have also been used with or included in in vivo and in vitro monitoring systems.

[0050] Implementation of in vivo analyte monitoring system

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

[0052] Example implementation of a reader device

[0053] Figure 2A This is a block diagram depicting an example embodiment of a reader device 120, which in some embodiments may include a smartphone. Here, the reader device 120 may include a display 122, an input unit 121, and a processing core 206, which includes a communication processor 222 coupled to a memory 223 and an application processor 224 coupled to a memory 225. It may also include a separate memory 230, an RF transceiver 228 with an antenna 229, and a power supply 226 with a power management module 238. Furthermore, the reader device 120 may also include a multifunction transceiver 232 that can communicate with the antenna 234 via Wi-Fi, NFC, Bluetooth, BTLE, and GPS. As those skilled in the art will understand, these components are electrically and communicatively coupled in a manner that forms a functional device.

[0054] Example implementation of sensor control device

[0055] Figure 2B and Figure 2C This is a block diagram depicting an example embodiment of a sensor control device 102 having an analyte sensor 104 and sensor electronics 160 (including analyte monitoring circuitry), the sensor electronics having substantial processing capabilities for presenting final result data suitable for display to a user. Figure 2BThe image depicts a single semiconductor chip 161, which may be a custom application-specific integrated circuit (ASIC). Within the ASIC 161 are shown several high-level functional units, including an analog front-end (AFE) 162, power management (or control) circuitry 164, a processor 166, and communication circuitry 168 (which may be implemented as a transmitter, receiver, transceiver, passive circuitry, or otherwise according to a communication protocol). In this embodiment, both the AFE 162 and the processor 166 serve as analyte monitoring circuitry; however, in other embodiments, either circuitry may perform analyte monitoring functions. The processor 166 may include one or more processors, microprocessors, controllers, and / or microcontrollers, each of which may be a discrete chip or distributed across multiple different chips (and portions thereof).

[0056] Memory 163 is also included within ASIC 161 and can be shared by various functional units present within ASIC 161, or distributed among two or more of them. Memory 163 can also be a separate chip. Memory 163 can be volatile and / or non-volatile memory. In this embodiment, ASIC 161 is coupled to power supply 172, which can be a button battery, etc. AFE 162 interfaces with in vivo analyte sensor 104 and receives measurement data from it, outputting the data in digital form to processor 166, which then processes the data to derive final results such as glucose discrete values ​​and trend values. This data can then be provided to communication circuitry 168 for transmission via antenna 171 to reader device 120 (not shown), for example, where a software application residing in the data receiving device requires minimal further processing to display the data.

[0057] Figure 2C Similar to Figure 2BAlternatively, it may include two discrete semiconductor chips, 162 and 174, which may be packaged together or separately. Here, AFE 162 resides on ASIC 161. On chip 174, processor 166 is integrated with power management circuitry 164 and communication circuitry 168. AFE 162 includes memory 163, and chip 174 includes memory 165, which may be isolated or distributed therein. In one example embodiment, AFE 162 is combined with power management circuitry 164 and processor 166 on a single chip, while communication circuitry 168 is on a separate chip. In another example embodiment, both AFE 162 and communication circuitry 168 are on a single chip, while processor 166 and power management circuitry 164 are on another chip. It should be noted that other chip combinations comprising three or more chips are possible, each responsible for the individual functions described, or sharing one or more functions for fail-safe redundancy.

[0058] Example implementation of time-based software applications within the scope

[0059] In many embodiments, the subjects described herein are implemented by a software application stored in memory and executed by a processor-based device, such as a reader device (e.g., a smartphone), a drug delivery device, a trusted computer system, a local computer system, or any other computing device described herein. In some embodiments, the software is implemented as one or more downloadable software applications (“Apps”) on a reader device (such as a mobile communication device or a smartphone). In some embodiments, the software and its associated features and functions may be implemented on a single centralized device, or alternatively, may be distributed across multiple discrete devices in geographically dispersed locations. Likewise, those skilled in the art will recognize that the various computer systems represented in the embodiments disclosed herein (such as…) Figure 1 The diagram shown is intended to cover both physical computing devices and virtual computing devices (e.g., virtual servers or virtual machines).

[0060] Typically, the software provides a mechanism that allows users to specify consumables (e.g., food type, beverage type, or portions thereof) in a user-friendly manner. These consumables will generally be referred to herein as a meal or multiple meals, and these terms are widely used to refer to all types of food and beverages.

[0061] According to one aspect of many embodiments, the software can perform multiple functions related to collecting dietary information and associating that dietary information with analyte information collected by in vivo analyte sensor 104 or in vitro test strips and instruments, or with analyte information from trusted computer system 180. The software will generally be referred to below as a “time-in-range application,” a “TIR application,” or a “dietary monitoring application.”

[0062] According to another aspect of many implementations, the TIR app can be used by people with diabetes, including those with type 2 diabetes who are on basal insulin or those on multi-dose insulin therapy with the potential motivation to change their diet. It can also be used by people with prediabetes or non-diabetic individuals who want to minimize their glucose deviations by controlling their diet. Users of the TIR app may have poorly controlled diabetes and want to control it, but have found that adhering to a prescribed “diabetic diet” for extended periods is unsustainable because they don’t want to give up their favorite foods. Users of the TIR app may also have their diabetes under control, but their daily diet is no longer effective because they are, for example, taking a new medication, starting a new exercise program, becoming pregnant, or experiencing other life changes.

[0063] The TIR application allows individuals to record information about each meal they consume (i.e., each "meal event"). The TIR application can correlate log entries from the user with analyte data indicating the relevant time period in which the meal was consumed.

[0064] In some implementations, the TIR application categorizes food choices based on blood glucose (or other analyte) responses. It can be used in conjunction with an analyte monitoring system 100 to help people better understand the impact of their diet on their glucose levels. The TIR application can correlate measured analyte responses with dietary events and store the results in a non-transitory memory or database. Specifically, the TIR application can display each diet and its associated analyte (e.g., glucose or other analyte) response to the user, for example, in a list where each diet is ranked and organized according to the magnitude of the decrease in blood glucose response (for example, glucose). Users can directly see how food choices and portion sizes affect their glucose levels. Users can understand which foods have the greatest impact. The TIR application also helps dispel myths about healthy eating (e.g., problematic high-carbohydrate foods that may be mistakenly considered healthy, such as orange juice and breakfast cereals).

[0065] In many implementations, TIR applications can enable users to see the good and bad foods (or good and bad eating behaviors) present in their current diet to help them identify what modifications they can make to achieve improved glucose control and improve the time their glucose levels remain within the target range. TIR applications can assist users by providing data visualizations of the glucose response and TIR effects of different food choices. TIR applications can also provide easily understandable scores for recorded meals based on changes in the user's glucose levels detected over a predetermined time period after eating (e.g., three hours). In some implementations, for example, a higher-scoring meal may correspond to a meal associated with a lower glycemic response. Conversely, a lower-scoring meal may correspond to a meal associated with a higher glycemic response. In this way, higher-scoring meals indicate to users that specific food choices can help them stay within the target range of the analyte values. In some implementations, TIR applications can gamify TIR to incentivize users to make beneficial food choices and increase TIR metrics.

[0066] TIR applications can utilize and evaluate the amount of time a user spends within a defined range of values ​​to assess the glucose effects of diet (and other events). For example, a TIR application can evaluate the amount of time a user spends within a defined value or TIR range (e.g., within a target glucose range of approximately 70 mg / dL to approximately 180 mg / dL). In some implementations, the target range can be set by the user. For example, the target range can be set to approximately 80 mg / dL to approximately 170 mg / dL. The lower limit of the target range can be at least approximately 65 mg / dL, such as approximately 70 mg / dL or 80 mg / dL. The upper limit of the target range can not exceed approximately 180 mg / dL, such as approximately 170 mg / dL or 120 mg / dL. The target can also be automatically adjusted incrementally by the TIR application (without user intervention) if the user meets the currently assigned target or purpose after a predetermined period of time. For example, if a user has consistently achieved a target of 30% of their glucose measurements within the target range over the past week, the TIR application can set a new target for the user to maintain 35% of their measured analyte levels within the target range. Similarly, if the target of 30% of glucose measurements being within the target range cannot be consistently achieved, the TIR application can allow the user to set a new target of maintaining 25% of measured analyte levels within the target range. However, those skilled in the art will understand that other target ranges may be utilized in addition to those listed or described herein, and these figures are not intended to be limiting.

[0067] TIR can be determined as a percentage by dividing the time the analyte level remains within a certain range by the total time period. For example, if glucose remains within the TIR threshold for 6 hours within a total 24-hour period, the TIR is 25%. Alternatively, the metric can be displayed as a time increment rather than a percentage; using the example above, the TIR would be 6 hours (within a total 24-hour period).

[0068] In many implementations, users of the TIR application can continuously monitor their glucose levels, for example, using the sensor control device 102 of system 100. (As in...) Figure 3 As seen herein, analyte levels can be transmitted (i) from sensor 104 to analyte monitoring application 310; (ii) from analyte monitoring application 310 to a cloud including server 320; and (iii) from server 320 to TIR application 330. In some embodiments, cloud 320 may include one or more servers having the same or different functionalities. For example, analyte data may be uploaded to a first server or set of servers responsible for collecting analyte data, and then downloaded to the TIR application by a second server or set of servers responsible for downloading the data for use by the time-of-range application. Those skilled in the art will also understand that analyte monitoring application 310 and TIR application 330 may reside on a single device (such as, for example, a single smartphone), or alternatively, may reside on two different devices (such as, for example, two smartphones, or a smartphone and a dedicated receiver). Those skilled in the art will further understand that in some embodiments, many features and functionalities of the TIR application as described herein may be integrated into analyte monitoring application 310. In such cases, the analyte data received by the analyte monitoring application 310 from the sensor 104 can perform the features and functions of the TIR application without being transmitted to the cloud or server.

[0069] Additional details regarding the features and interface of the time-based software application can be found in all of U.S. Patent Publications 2017 / 0128007, 2021 / 0030323 and 2022 / 0000399, which are incorporated herein by reference in their entirety for all purposes. Any of these features and interfaces may be implemented and / or used in combination with the embodiments described herein.

[0070] Example implementation of GUI and related features for Time-in-Range ("TIR") applications

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

[0072] Example implementations of the homepage GUI and related methods

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

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

[0075] Still referencing Figure 4A-1 At 4003, the peak analyte value in the analyte data is identified. In some implementations, this may require identifying the highest glucose value exceeding a predetermined analyte level threshold (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL, etc.). In some implementations, if a newly identified highest glucose value is higher than a previously identified highest glucose value, the peak analyte value is updated to the newly identified highest glucose value. The peak analyte value may also be a glucose value exceeding the predetermined analyte level threshold during a time window following the meal entry (e.g., a one-hour window following the meal entry, a two-hour window following the meal entry, a three-hour window following the meal entry, or a four-hour window following the meal entry). In some implementations, the peak analyte value may also be a glucose value exceeding the predetermined analyte level threshold before the meal entry time (e.g., three hours before the meal entry). When the peak analyte value is determined before the meal entry time, the postprandial period ends early to allow the user to receive scores (as described below) before the full time window following the time when the peak analyte value was determined.

[0076] According to one aspect of the implementation, peak analyte detection will cease if the percentage difference between the most recent analyte value and the peak analyte value is less than a predetermined threshold. In some implementations, peak analyte detection will cease after a predetermined time period (e.g., three hours) following the dietary entry.

[0077] Then, at 4004, the initial analyte level is determined. According to some implementations, the initial analyte level can be determined by confirming the analyte level at or near the time of the dietary entry (e.g., within 15 minutes before or after the dietary entry).

[0078] In some implementations, the historical analyte data range is defined as a postprandial period, which extends from the time of the initial analyte level (e.g., 15 minutes before or after the meal entry, 30 minutes before or after the meal entry, or 1 hour before or after the meal entry) to the end time of the peak analyte value (e.g., 2 hours after the meal entry, 3 hours after the meal entry, or 4 hours after the meal entry). In some implementations, the end of the postprandial period may be the first of two events to occur: (1) a first analyte (e.g., glucose) reading obtained within three hours of the initial analyte level, or (2) a last analyte (e.g., glucose) reading obtained before the entry of a new meal entry.

[0079] Subsequently, in some embodiments, at 4005, the analyte level offset can be determined, for example, by subtracting the initial analyte level from the peak analyte level. Then, at 4006, the analyte level offset can be associated with the dietary entries entered by the user and stored together in memory. Then, at 4007, and based on the analyte level variance, a score or rating is assigned to the specific diet associated with the entered dietary information. In some embodiments, the specific diet is scored only after the end of the postprandial period. In some embodiments, the score for each of one or more dietary events is calculated based on a glucose response based on data indicating the glucose level associated with each dietary event.

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

[0081] According to some implementations, allocating or calculating the meal score at 4007 can further take into account certain physiological conditions present in the user's body prior to consuming the meal. More specifically, some individuals with diabetes may have high initial analyte levels (e.g., glucose levels) before consuming a meal. For example, some individuals with type 2 diabetes who still have the ability to produce insulin to metabolize glucose may frequently exhibit high pre-meal glucose levels. Therefore, the endogenous insulin present in those individuals before consuming a meal will affect the response to the meal and will cause the analyte level offset value (also known as "PeakDelta" or "peak δ") to decay. To illustrate, Figure 4A-2 and Figure 4A-3 Postprandial glucose trajectories 4100 and 4150 for individuals with the same diet at different times are shown. The second graph 4150, on the right, depicts an initial analyte level of approximately 150 mg / dL (also known as pre-meal glucose level) and a PeakDelta value of approximately 100 mg / dL. The first graph 4100, on the left, depicts a pre-meal glucose level of approximately 180 mg / dL and a PeakDelta value of approximately 70 mg / dL for the same diet consumed. Therefore, for individuals with high pre-meal glucose levels, the PeakDelta value, or analyte level offset, decreases.

[0082] To account for higher initial analyte levels in some users, the PeakDelta value can be adjusted according to some implementation methods. For example, the PeakDelta value can be adjusted according to the following example equation: PeakDeltaAdj=PeakDelta+f(G 餐前 (1) As explained above, PeakDelta is the analyte level shift, or the difference between the peak analyte level after a diet and the initial analyte level. PeakDeltaAdj is the adjusted analyte shift, and G... 餐前 This is the initial analyte level. In some implementations, G 餐前 It is the glucose level at the time stamp preceding the timestamp on the diet label. In other implementations, G 餐前 It is the lowest glucose level before the timestamp on the diet label within a predetermined duration (e.g., one hour, ninety minutes, two hours, three hours, etc.).

[0083] Additionally, according to some implementation methods, f(G) 餐前 It can be represented by the following linear function: f(G 餐前 )=a×G 餐前 +b (2) Variables a and b can be constants determined based on a simulation of a virtual type 2 diabetes patient population consuming a variety of diets, including varying amounts of carbohydrates, fat, and protein. In other embodiments, variables a and b can be constants determined from in vivo data. Those skilled in the art will understand that other methods can be used to determine variables a and b using one or more of simulation data, in vivo data, population data, and other test data. The first variable a can be related to G. 餐前 Multiply, while the second variable b can be multiplied by G. 餐前 Add the product of a and b. In some implementations, for example, a = 0.4 and b = -50 mg / dL.

[0084] According to some implementation methods, if data is available for multiple instances of the same diet (or the same type of diet) consumed at different times / days, the weighted average of variables a and b can be used to calculate the adjusted analyte level offset value PeakDeltaAdj. Specifically, for multiple instances of the same diet, G 餐前 and G 峰值 The values ​​can be correlated. Additionally, in some implementations, the values ​​of multiple instances of the same diet can be further grouped by meal time period (e.g., breakfast, lunch, or dinner). For each diet with more than one instance, variables a and b can be estimated as a est and b est For those with associated a est and b est For a given diet, a weighted average of each parameter can be calculated, with greater weighting for diets with more instances. The PeakDeltaAdj value can then be determined based on the latest weighted average parameter for a specific user.

[0085] Those skilled in the art will understand that other variables and / or constants may be used in the equations described herein without departing from the scope of this disclosure.

[0086] According to other implementations, when PeakDelta is low, a logic function can be used to make G... 餐前 Minimize the impact. This can be used to reduce inappropriate ratings of small diets with minimal analyte level offset. An example implementation of the logistic function is represented by the following equation: (3) (4) In the above equation, d is PeakDelta, and a and b are constants.

[0087] Furthermore, according to some implementations, one or more data validity checks may be performed before calculating the PeakDeltaAdj value. For example, in some implementations, a first data validity check may be performed to determine whether a predetermined time window (also known as an offset period) following the dietary label timestamp contains at least two (2) hours of glucose data. As another example, a second data validity check may be performed to determine whether another dietary label exists within the offset period, and if so, whether the offset period contains at least two (2) hours of glucose data preceding the dietary label.

[0088] According to another aspect of some implementation methods, the scoring index itself can be G. 餐前 and / or G 峰值 The function.

[0089] Figure 4A-4 This is a flowchart depicting an example implementation of a method 4200 for correlating analyte data with dietary information that interprets a user's high pre-meal glucose levels. (As shown...) Figure 4A-4 As seen at the top, method 4200 begins at 4201, where the software receives dietary information input by the user. In many embodiments, this can be a timestamped dietary label input by the user, these timestamps potentially associated with glucose data received from a sensor control device worn by the user. At 4202, for each dietary label, the meal time is aligned with the glucose data to reflect postprandial shift. That is, from the analyte data and the dietary label, the initial and peak analyte levels for each meal should be verifiable. Subsequently, at 4203, one or more data validity checks may optionally be performed, as described above. If the one or more data validity checks fail, the software may indicate that the meal is unscored. In some embodiments, the software may prompt the user to correct unscored meals by inputting more analyte data, by correcting the dietary label information, or by other means. In some embodiments, the software may prompt the user to delete unscored dietary labels.

[0090] Still referencing Figure 4A-4 If the data validity checks have passed, at 4205, the initial analyte value (Gpremeal) and the peak analyte level value (Gpeak) are identified. Then, the adjusted analyte level offset (PeakDeltaAdj) can be calculated using any of the methods described above. Subsequently, at 4206, a meal score can be calculated or assigned to a meal based on the adjusted analyte level offset (PeakDeltaAdj). Optionally, at 4207, all of the user's meals can be ranked according to the assigned scores.

[0091] In some embodiments, the adjusted analyte level offsets allocated to each meal over a predetermined time period (e.g., the most recent 24 hours) are averaged together to determine the combined meal score for the predetermined time period (e.g., the previous day or the most recent 24 hours). In some embodiments, the combined meal score may be displayed as a numerical value or its representation on an interactive graphical user interface. Specifically, in some embodiments, the combined meal score may be a maximum analyte level value. For example, in some embodiments, the maximum analyte level value for the combined meal score may be 150 mg / dL. According to one aspect of the embodiments, to determine the numerical range of the combined meal score, a determined analyte level value exceeding the maximum analyte level value is set as the maximum analyte level value (e.g., if a determined analyte level value exceeds 150 mg / dL, then for the purpose of determining the numerical range of the combined meal score, the analyte level value will be considered as 150 mg / dL). According to another aspect of the embodiments, the analyte level value associated with the combined meal score is divided by a predetermined value (e.g., 1.5 mg / dL) to achieve a dimensionless range for the combined meal score. For example, in some embodiments, the combined dietary score can be a value between 1 and 100. Therefore, in some example embodiments, if the combined dietary score is associated with an analyte level of 150 mg / dL, the combined dietary score is calculated as 100. Those skilled in the art will understand that other predetermined values, maximum analyte levels, and ranges can be used as the combined dietary score without departing from the scope of this disclosure.

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

[0093] refer to Figure 4A-5 At 4301, the method for the interface includes receiving data indicating analyte levels (e.g., data indicating glucose levels) from the sensor control device 102 by at least one processor.

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

[0095] At 4303, method 4300 may include: providing an interactive graphical user interface to a display device configured to display data indicating analyte levels based on determination, wherein the display device indicates the amount of time the data indicating analyte levels are within a predetermined analyte range. According to some embodiments, for example, the amount of time the data indicating analyte levels are within the predetermined analyte range may be displayed as an increment or percentage value and may be graphically represented as portions or segments of circles or rings, wherein the area of ​​each portion or segment is proportional to the percentage value. In other embodiments, the graphical representation may be a pie chart, one or more bars or bar segments, a line graph, one or more Harvey spheres, a thermometer, a digital gauge (e.g., a velocimeter), or any other geometry or image configured to reflect user progress.

[0096] Turning to Figures 4A through 6, the flowcharts depict an example implementation of method 4400 for calculating a user's blood glucose control over a predetermined time period. First, those skilled in the art will also recognize that any combination, subset, or all of the steps of method 4400 can be implemented in conjunction with any combination, subset, or all of the steps of methods 4000, 4200, and / or 4300 described above. For ease of illustration, in this embodiment and other embodiments described below, the monitored analyte will be glucose, but other analytes may also be monitored, as noted herein.

[0097] Specifically, method 4400 can calculate a user's blood glucose control over a predetermined time period and provide customized feedback to the user by utilizing a combination of one or more indicators and / or data associated with the user's continuous glucose monitoring device.

[0098] like Figure 4A-6 As shown at the top, method 4400 begins at 4401, wherein one or more indicators are calculated as part of a total score, wherein the score indicates the user's blood glucose control over a predetermined time period. The predetermined time period can be one day, one week, two weeks, 15 days, 30 days, one month, etc. Those skilled in the art will understand that various other predetermined time periods can be utilized at 4401 without departing from the scope of this disclosure.

[0099] Specifically, at least one or more of the following indicators are used as part of the total score: (1) one or more indicators recommended by the American Diabetes Association (“ADA”); (2) user data indicating analyte levels received from the sensor control device (e.g., data indicating glucose levels); and (3) dietary score indicators. Method 4400 may utilize one or more of the following indicators recommended by the ADA: (1) the amount of time the continuous glucose monitoring device is worn; (2) the amount of time the continuous glucose monitoring device is active (including the number of times the sensor is scanned within a time period); (3) glucose variability; (4) the amount of time the user’s glucose level is at or below a predetermined threshold (e.g., at or below 54 mg / dL or 70 mg / dL); and (5) the amount of time the user’s glucose level is at or above a predetermined threshold (e.g., at or above 180 mg / dL or 250 mg / dL). Those skilled in the art will understand that various other indicators recommended by the ADA may be used in conjunction with method 4400 without departing from the scope of this disclosure.

[0100] Additionally, method 4400, and specifically 4401, may utilize any of the dietary scoring indicators described herein. For example, the dietary scoring indicators described in methods 4200 and / or 4300 may be used as part of the total score calculated in 4401. Those skilled in the art will understand that various other dietary scoring indicators may be used in conjunction with method 4400 without departing from the scope of this disclosure.

[0101] At point 4401, continuous glucose monitoring data from the user over a predetermined time period is also used for calculation. For example, point 4401 can use data indicating user analyte levels (e.g., data indicating glucose levels) that are indicative of a day, week, month, etc., to calculate the total score.

[0102] Subsequently, at 4402, a raw score is determined for each of the one or more metrics used to calculate the total score at 4401. The raw score for each of the one or more metrics can be normalized such that each metric conforms to ADA guidelines to be mapped to a predefined numerical score value (e.g., 70 or 80 points) that is less than a predefined maximum score value (e.g., 100 points). In this way, the raw score for each of the one or more calculated metrics can be standardized, making it possible for users to go beyond the ADA guidelines and make improvements.

[0103] At point 4403, weights can be assigned to each normalized metric. Specifically, weights can be assigned to the normalized raw scores of each of one or more metrics. In this respect, specific weights can be applied to emphasize one or more specific metrics. The sum of all applied weights can be 1. Therefore, each weighted metric is provided with a sub-score.

[0104] Next, at 4404, a total score for a predetermined time period (e.g., one day, one week, etc.) is calculated based on one or more metrics or sub-scores. If corresponding weights have been applied to one or more metrics, all weighted sub-scores are summed to determine the user's total score for the predetermined time period. For example, the total score can be a numerical value (e.g., a value between 1 and 100). The total score can be updated at a predetermined frequency, thus providing an updated total score for each predetermined time period. The total score can also be a daily score in numerical form provided to the user each day. In this way, method 4400 provides user-friendly and actionable information, enabling the user to better understand progress in blood glucose control and / or areas that need improvement.

[0105] At point 4405, a total score and / or related information can be displayed to the user at the end of each predetermined time period, wherein the total score and / or related information is output via the GUI of the dietary monitoring application. For example, if daily scores are provided, updated or new daily scores can be output to the user daily via the dietary monitoring application. For indicators where the total score is above a predetermined threshold total score value (e.g., a score equal to or higher than 85, 90, 95, etc.), the dietary monitoring application can be configured to output positive feedback information related to blood glucose control and / or its progress. For indicators where the total score is below a predetermined threshold total score value (e.g., a score equal to or lower than 65, 60, 55, etc.), the dietary monitoring application can be configured to output information providing customized suggestions / recommendations for improving the user's blood glucose control. The total score and related feedback can be output to the user through various interface implementations described herein without departing from the scope of this disclosure.

[0106] According to another aspect of some implementations, the GUI of the dietary monitoring application can also be configured to display historical total scores to show the user's progress over time. Additionally, according to some implementations, the GUI of the dietary monitoring application can also be configured to provide insights based on certain trends in the user's historical total scores (e.g., when the score is trending upward, when the score is trending downward, how the score compares to the average total score over a predetermined period, and whether the score is higher or lower than a previously predetermined period).

[0107] refer to Figure 4BA block diagram illustrating an example implementation of a homepage GUI 400 for a TIR application is shown. According to one aspect of the implementation, the homepage GUI 400 may include: (1) a TIR card 401; (2) a logbook section 4008 including a list 402 of dietary events 419; (3) a selectable homepage icon 403 that outputs the homepage GUI 400 when selected by a user; (4) a selectable meal icon 404 that outputs a meal report GUI when selected by a user, the meal report GUI including information about one or more dietary events that occurred in a previous time period (e.g., the past week); and (5) a "+" icon 405 that, when selected by a user, outputs a meal record GUI 500 configured to receive dietary information input by the user (see example...). Figures 5A to 5G In some implementations, the TIR card 401 may include graphical elements indicating the amount of time a user spends within the target analyte range (“time within range” or “TIR”) during a predetermined time period (e.g., a 24-hour period). In some implementations, although not illustrated, the homepage GUI 400 may include selectable insight icons instead of the meal icon 404. Specifically, although Figure 4B Not shown in the image, but when the user selects the Insight icon, the output will be either Insight GUI 14000 or Insight GUI 150000 (for example, respectively). Figures 14A-1 to 14A-4 ,as well as Figures 15A-1 to 15A-5 This will be described in further detail below.

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

[0109] Those skilled in the art will further recognize that other types of progress indicators (e.g., text, numbers, or graphics) may also be utilized, and such indicators are entirely within the scope of this disclosure. Furthermore, although the graphic elements shown are circles or rings with shaded portions including gradients, those skilled in the art will understand that other geometries, colors, and quantities of portions or gradients may be utilized, and such portions or gradients are entirely within the scope of this disclosure.

[0110] In some implementations, the TIR card 401 may further include a selectable information icon 409, which, when selected by a user, outputs a TIR information screen 410 associated with the TIR card 401. For example, and as... Figure 4C As depicted, the TIR information screen 410 provides details on how the TIR ring 406 visually displays the progress indicator 408 and the daily TIR target 407. In some embodiments, the TIR information screen 410 also informs the user that the TIR target settings are configurable. (Return to Reference) Figure 4BIn some embodiments, the homepage GUI 400 also includes a selectable settings icon 411, which, when selected, outputs a settings GUI where the user can adjust TIR target settings, such as changing the daily TIR target 407 and the metrics displaying TIR data (e.g., displaying the TIR value 408 or the daily TIR target 407 in hours or as a percentage). In some embodiments, and as in... Figure 4B As illustrated in the diagram, the homepage GUI 400 also includes a message 412 adjacent to the TIR card, wherein message 412 indicates the time when the TIR card 401 was last updated.

[0111] refer to Figure 4B The homepage GUI 400 may include a logbook section 4008 containing a list 402 of dietary information, including one or more dietary events 419 that occurred within a predetermined time period (e.g., a day). Each dietary event 419 provides details of a specific meal consumed within the predetermined time period. In some embodiments, each dietary event 419 may include a text description 413 of the meal (e.g., “blueberry oatmeal”), a portion size indicator 414 (e.g., “typical”) describing the relative portion size of the meal (e.g., typical, larger, or smaller compared to a user’s daily meal allowance), and / or a timestamp 415 associated with the time the meal was consumed (e.g., “8:04 AM”). Although not illustrated, in some embodiments, a dietary event 419 may include one or more dietary labels associated with the meal. Users may use dietary labels (not shown) to describe the contents or characteristics of the meal, or to list the type of food, such as vegetables, chicken, beef, pork, fish, salad, pasta, or vegetarian, to name just a few examples of labels. Alternatively or additionally, a dietary event 419 may include a photograph / image 417 associated with the meal. In some implementations, a user can take a photo of the meal, or alternatively, select a photo from a photo library. In some implementations, a placeholder photo / image 417 will be displayed instead when the user does not associate photo 417 with a meal. In some example implementations, list 402 can be sorted such that meal events 419 corresponding to the most recently consumed meal are presented first or at the top of the list, with subsequent meal events 419 displayed in chronological order.

[0112] like Figure 4BAs illustrated in the diagram, each dietary event 419 may additionally or alternatively include a rating or score 420 for a single specific diet based on its associated analyte response. In some embodiments, the analyte response may be based on changes in analyte levels over a predetermined time period following the consumption of the specific diet. In some embodiments, the diet is assigned a score 420 based on the analyte level offset from the time of consumption of the specific diet to the peak glucose level within three hours of eating.

[0113] Furthermore, the score 420 can be displayed as a numerical value. In some embodiments, the score 420 can be a number between one and five, wherein a higher allocation value corresponds to a lower analyte response and a lower allocation value corresponds to a higher analyte response. For example, (1) a change in analyte level from 0 mg / dL to 20 mg / dL within a two-hour postprandial period can correspond to a score of “5” 420; (2) a change in analyte level from 21 mg / dL to 40 mg / dL within a two-hour postprandial period can correspond to a score of “4” 420; (3) a change in analyte level from 41 mg / dL to 60 mg / dL within a two-hour postprandial period can correspond to a score of “3” 420; (4) a change in analyte level from 61 mg / dL to 90 mg / dL within a two-hour postprandial period can correspond to a score of “2” 420; and (5) a change in analyte level of 91 mg / dL or higher within a two-hour postprandial period can correspond to a score of “1” 420. As another example, (1) a change in analyte level from 0 mg / dL to 24 mg / dL within a three-hour postprandial period can correspond to a score of “5” 420; (2) a change in analyte level from 25 mg / dL to 49 mg / dL within a three-hour postprandial period can correspond to a score of “4” 420; (3) a change in analyte level from 50 mg / dL to 74 mg / dL within a three-hour postprandial period can correspond to a score of “3” 420; (4) a change in analyte level from 75 mg / dL to 99 mg / dL within a three-hour postprandial period can correspond to a score of “2” 420; and (5) a change in analyte level of 100 mg / dL or higher within a three-hour postprandial period can correspond to a score of “1” 420. Those skilled in the art will understand that other changes in analyte levels can be used with different scores (including more or fewer scores) and are entirely within the scope of this disclosure.

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

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

[0116] In some implementations, when the user toggles the switch control 424 downwards, the main GUI 400 is configured to display multiple selectable rings 425. Figure 4B Not shown in the text, but see for example Figure 6B-1 Each ring corresponds to a different day of the past week. For example, when the toggle control 424 is toggled down, the homepage GUI 400 can display multiple (seven) rings 425. Figure 4B(Not shown in the image), one ring corresponds to each day of the week. Similar to the TIR ring 406 shown on TIR card 401, each of the plurality of rings 425 represents the user's progress toward the daily TIR goal for that particular day. For example, the number of TIR hours a user spends on a particular day can be visually displayed as a progress indicator 426 (e.g., shaded portion) extending along the circumference of ring 425 to the total circumference of ring 425, indicating that the user has spent X% of TIR (where X% is the amount of hours spent in the range divided by 24 hours).

[0117] In some implementations, when a user selects a specific ring from multiple rings 425, a report GUI 600 is displayed (e.g., Figure 6B-1 In some implementations, when the toggle control 424 is switched to the upward position, the multiple rings 425 are no longer displayed. Implementations of the reporting GUI 600 will be described in further detail below.

[0118] refer to Figure 4D A block diagram illustrating an example implementation of a homepage GUI 450 for a TIR application is shown. According to one aspect of the implementation, the homepage GUI 450 may include: (1) an analyzer graphics card 451; (2) a logbook section 4508 including a list 452 of dietary events 469; (3) a selectable homepage icon 453 that outputs a homepage GUI 400 when selected by the user; and (4) a selectable diet icon 454 that outputs a diet impact GUI 800 or a diet commentary GUI 8000 (respectively) when selected by the user. Figure 8A and Figures 8B to 8E The dietary impact GUI includes information about one or more dietary events 469 that occurred in a previous time period (e.g., the past week); and (5) a "+" icon 455, which, when selected by the user, outputs a dietary record GUI 500 (not shown) configured to receive dietary information input by the user. In some embodiments, although not illustrated, the home GUI 450 may include selectable insight icons instead of dietary icons 454. Specifically, when the user selects an insight icon, insight GUI 14000 or insight GUI 150000 is output (e.g., respectively). Figures 14A-1 to 14A-5 ,as well as Figures 15A-1 to 15A-5 This will be described in further detail below.

[0119] In some implementations, the homepage GUI 450 is displayed in response to a first predetermined input from the user on the homepage GUI 400 (such as when the user drags or swipes with their finger or performs some other predetermined gesture). Similarly, the homepage GUI 400 may be displayed in response to a second predetermined input from the user on the homepage GUI 450 (such as when the user drags or swipes with their finger or performs some other predetermined gesture).

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

[0121] The analyte graph 460 may include solid lines 462-1, 462-2 to indicate the user's target analyte range associated with data indicating analyte levels. For example, the area between solid lines 462-1, 462-2 indicates a target analyte range (e.g., between 70 mg / dL and 180 mg / dL). In some embodiments, and as such... Figure 4DAs illustrated in the diagram, the analyte trend line 461 is configured as a dashed or broken line to represent the time period during which the user's analyte level falls outside the limits of the target analyte range (e.g., exceeds the range or falls below the range). Alternatively, the analyte trend line 461 is configured as a solid line to represent the time period during which the user's analyte level is within the target analyte range. As previously mentioned, the target analyte range can be set by the user. For example, the target analyte can be set to about 80 mg / dL to about 170 mg / dL, alternatively about 70 mg / dL to about 180 mg / dL, or about 65 mg / dL to about 120 mg / dL. In some embodiments, and as... Figure 4D As illustrated in the diagram, the homepage GUI 450 also includes a message 463 adjacent to the analyzer graphics card 451, wherein the message 463 indicates the time when the analyzer graphics card 451 was last updated.

[0122] According to another aspect of some embodiments, one or more meal icons 464 may be displayed on the analyte trend line 461. In some embodiments, one or more meal icons 464 may be displayed near, close to, and / or on the proximal side of the analyte trend line 461, or along the x-axis, at the top or bottom of the graphics window. Additionally, in some embodiments, one or more meal icons 464 may be displayed with or without leaders. Each meal icon 464 may be a photograph or image associated with a specific meal. In some aspects of the embodiments, meal icons 464 are positioned on the analyte trend line 461 to allow the user to visually associate the post-meal analyte trajectory with the associated meal. In some embodiments, meal icons 464 are positioned on the analyte trend line 461 based on the time associated with the meal. For example, if meal event 469 indicates that the blueberry oatmeal was consumed at 8:04 AM, then the meal icon 464 corresponding to meal event 469 will be displayed on the x-axis of the analyte graph 460 at approximately 8:04 AM.

[0123] Still referencing Figure 4DSimilar to the homepage GUI 400, the homepage GUI 450 may include a logbook section 4508 containing a list 452 of one or more meal events 469 that occur within a predetermined time period (e.g., a day). Each meal event 469 provides details of a specific meal consumed within the predetermined time period. In some embodiments, and as previously described with respect to the homepage GUI 400, each meal event 469 may include a text description 473 of the meal (e.g., “blueberry oatmeal”), a portion size indicator 474 (e.g., “typical”) describing the relative portion size of the meal (e.g., typical, larger, or smaller compared to a user’s daily meal allowance), and / or a timestamp 475 associated with the time the meal was consumed (e.g., “8:04 AM”). Although not illustrated, in some embodiments, a meal event 469 may include one or more meal labels associated with the meal. Alternatively or additionally, a meal event 469 may include a photograph / image 477 associated with the meal. In some implementations, a placeholder image 477 will be displayed instead when the user does not associate the photo or image 477 with a meal. In some example implementations, the list 452 may be sorted such that meal events 469 corresponding to the most recently consumed meal are presented first or at the top of the list 452, with subsequent meal events 469 displayed in chronological order.

[0124] like Figure 4D As depicted herein, and similar to the embodiments previously described herein, each dietary event 469 may additionally or alternatively include a rating or score 480 for a single specific diet based on its corresponding analyte response. In some embodiments, the analyte response may be based on changes in analyte levels over a predetermined period following the consumption of the specific diet. In some embodiments, a score 480 is assigned to a diet based on changes in analyte levels from the time of consumption of the specific diet to peak glucose within three hours of eating. Furthermore, the score 480 may be displayed as a numerical value. In some embodiments, the score 480 may be a number between one and five, where a higher assigned value corresponds to a lower analyte response, and a lower assigned value corresponds to a higher analyte response. As depicted in the homepage GUI 450, the score 480 may be displayed in graphical elements such as asterisk icons 481. In some embodiments, each asterisk icon 481 may be filled with a colored portion, such as yellow. In many embodiments, the asterisk icons 481 are unfilled and include a dashed outline to indicate missing diet scores. In some implementations, the score information icon 492 is displayed on the home GUI 450 near and adjacent to list 452. When selected by the user, the score information icon 492 outputs a dietary score information modality, which includes information about the different score options and how the dietary score is determined.

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

[0126] In some implementations, when the user toggles the switch control 494 downwards, the main GUI 450 is configured to display multiple selectable rings 425. Figure 4D Not shown in the text, but see for example Figure 6B-1 Each ring is a TIR indicator corresponding to a different date in the past week. Each of the rings 425 for different dates may include a graphical or visual indicator of the amount of TIR (progress indicator) and an indicator of the target / purpose percentage or the number of TIR hours. In some embodiments, when a user selects a specific ring from the multiple rings 425, a report GUI 600 (not shown) for the relevant day is displayed. Those skilled in the art will recognize that other types of indicators (e.g., text, numbers (as percentages or fractions), graphics) may also be utilized, and these indicators are entirely within the scope of this disclosure.

[0127] In addition, in some implementations, the homepage GUI 450 also includes a selectable settings icon 499, which, when selected, outputs a settings GUI related to the TIR application.

[0128] Go to Figure 4E-1A block diagram of an additional example implementation of a homepage GUI 430 for a TIR application is shown. In some implementations, the homepage GUI 430 may include: (1) a TIR card 431; (2) an analyte graph card 4311, which includes an analyte graph 4310 with an analyte trend line 4315; (3) a logbook section 4308, which includes a list 432 of dietary events 4309; (4) a selectable homepage icon 433, which outputs the homepage GUI 430 when selected by the user; (5) a selectable diet icon 434, which outputs a diet report GUI 600 (Figure 6) when selected by the user, the diet report GUI including information about one or more dietary events that occurred in a previous time period (e.g., the past week); and (6) a "+" icon 435, which outputs a diet record GUI 500 configured to receive dietary information input by the user (see, for example) when selected by the user. Figures 5A to 5G In this regard, the TIR card 431 and the analyte graphics card 4311 are displayed on a single interface. In some embodiments, although not illustrated, the home GUI 430 may include selectable insight icons instead of diet icons 434. Specifically, although not illustrated, when the user selects an insight icon, either Insight GUI 14000 or Insight GUI 150000 is output (e.g., respectively). Figures 14A-1 to 14A-5 ,as well as Figures 15A-1 to 15A-5 This will be described in further detail below.

[0129] According to one aspect of the implementation, the TIR card 431 of the homepage GUI 430 is similar to Figure 4B The TIR card 401 of the homepage GUI 400 described herein differs from the visual display of the TIR card 401, except that the visual display of the TIR card 431 is different from that of the TIR card 401. Specifically, for the TIR card 431 ( Figure 4E-1 The daily TIR target 437 is displayed outside of the TIR ring 436, rather than within its interior region. For example, in some embodiments, the daily TIR target 437 is adjacent to the TIR ring 436. According to one aspect of the embodiment, the TIR ring 436 includes a progress indicator 438 and a TIR value 4305. Similar to... Figure 4B The TIR card 401 depicted includes a selectable information icon 439 in the homepage GUI 430. When selected by the user, this selectable information icon outputs a TIR information screen 440 associated with the TIR card 431. Figure 4F The TIR information screen 440 depicted in the image is similar to Figure 4C The TIR information screen 410 is located within the TIR information screen. Specifically, the TIR information screen 440 provides details on how the daily TIR ring 436 is visually displayed with the progress indicator 438 and the daily TIR target 437. In some implementations, such as Figure 4F As shown, the TIR information screen 440 also informs the user that the TIR target settings are configurable.

[0130] According to another aspect of the implementation, the analysis object graphics card 4311 of the homepage GUI 430 is similar to Figure 4D The analyte graphical card 451 of the homepage GUI 450 depicted in the diagram includes, in addition to the target analyte range 4312 (e.g., "Target glucose range: 70 mg / dL to 180 mg / dL"). Furthermore, as... Figure 4E-1 As shown, the homepage GUI 430 includes one or more selectable icons 4313 (e.g., radio buttons, checkboxes, sliders, toggle controls, etc.) that allow the user to select a predefined time period within which the user's analyte data will be displayed in the analyte graphics card 4311. For example, the selectable icons 4313 may be used to select a predefined time period of at least approximately four hours and / or no more than approximately 24 hours, such as four hours, 12 hours, or 24 hours. Those skilled in the art will understand that other predefined time periods can be utilized, and these time periods are entirely within the scope of this disclosure. In some embodiments, and as... Figure 4E-1 As shown, the selectable icon 4313 can be directly adjacent to and below the analyzer graphic 4310 on the analyzer graphic card 4311.

[0131] In some implementations, although Figure 4E-1 Not illustrated, but one or more meal icons may be displayed directly adjacent to and below the analyte graph 4310, or below the x-axis. For example, meal icons may be displayed at the bottom of the graph window 4314. According to some aspects of the embodiments, meal icons are positioned on the analyte graph card 4311 to allow the user to visually associate the post-meal analyte trajectory with the associated meal. In some embodiments, meal icons are positioned below the analyte graph 4310 and the x-axis based on the time associated with the meal. For example, if meal event 4309 indicates that the meal was consumed at 9:00 AM, the meal icon corresponding to meal event 4309 will be displayed directly adjacent to and below 9:00 AM on the x-axis of the analyte graph 4310.

[0132] In some implementations, and as such Figure 4E-2As depicted, a notification may appear on the analyzer graphics card 4311, wherein notification 4316 instructs the user to input a gesture (e.g., tap or tap and hold) on the trend line 4315 to provide glucose readings associated with a selected area of ​​the trend line 4315. In some embodiments, notification 4316 may also inform the user that a swipe-to-scroll gesture can be used on the trend line 4315 to provide glucose readings for each selected area of ​​the trend line 4315. Furthermore, Figure 4E-3 A homepage GUI 430 is depicted, wherein the analyte graphics card 4311 includes a visual indicator 4317 that includes an analyte reading (e.g., a glucose reading) corresponding to a selected area of ​​a trend line 4315. In some embodiments, the visual indicator may include an analyte level value and a timestamp (e.g., "117 mg / dL" and "10:00 AM") corresponding to the selected area of ​​the trend line 4315.

[0133] In some implementations, and as such Figure 4E-3 As best shown, the analyzer graphics card 4311 may include an analyzer graphics information icon 4318, which outputs an analyzer graphics information modality 445 when selected by the user. Figure 4G The analyte graphical information modality 445 provides the user with information about the predefined amount of time in which the analyte data for the selected user will be displayed in the analyte graphical card 4311. In some embodiments, the analyte graphical information modality 445 also informs the user that tapping or holding an area of ​​the analyte graphical card 4310 will allow the user to visualize glucose readings associated with the selected area. In some embodiments, the analyte graphical information modality 445 also includes a disclaimer informing the user that they should consult a healthcare professional before changing their diet or exercise plan.

[0134] In some example implementations, and as Figure 4E-4 As depicted, the notification card 441 can be output to the home GUI 430. For example, the notification card 441 can be displayed directly adjacent to and above the TIR card 431 on the home GUI 430. In some embodiments, the TIR card 431, the analyte graphics card 4311, and the logbook section 4308 are shifted downwards on the home GUI 430 to allow the notification card 441 to be positioned on the home GUI 430. In some embodiments, the notification card 441 can inform the user that it is time to scan the sensor. In some embodiments, the notification card 441 can also inform the user that the sensor can be scanned using an analyte monitoring application.

[0135] In some example implementations, and as Figure 4E-5As depicted, the announcement card 441 can be output to the homepage GUI 430 in place of the TIR card. For example, the announcement card 441 can be displayed directly adjacent to and above the analyzer graphics card 4311. In some example embodiments, the announcement card 441 can prompt the user to accept a challenge related to a new TIR goal. For example, the announcement card 441 can inform the user that the user has reached a specific number of TIR goals within a predefined time period (e.g., five out of the past seven days) and prompt the user to increase the target TIR goal by a specific number of hours (e.g., one hour). In some embodiments, the announcement card 441 may include an "opt out" button 442 that the user can choose to reject the challenge and an accept button 443 that the user can choose to accept and initiate a challenge. According to one aspect of the embodiment, the TIR application can be configured to output the announcement card 441, including the challenge prompt, to the user after the user has reached a specific number of TIR goals within a predefined time period.

[0136] The notification card 441 can be used in conjunction with any of the implementations described herein. Furthermore, in some implementations, the notification card 441 may include one or more of the following: (1) information about the meal record (e.g., “Welcome, [User Name], tap the “+” button below to add your first meal” or “Well done, [User Name]! You’ve added your first meal! Use the Libre 2 app to scan your sensors in 3 hours and come back here to check your body’s response to the meal”); (2) information related to the scan (e.g., “Ready? Use the Libre 2 app to scan your sensors and start tracking toward your TIR target. The goal is to turn off your ringtone before midnight every day” or “Use Libre 2 app to scan your sensors to add your first meal”). 2. The application scans your sensors. When you're done, come back here and see how your body responds to the meal”); (3) Information related to the updated settings (e.g., “Your time goal within range has been set. You will see it here tomorrow” or “Your new goal is [hours], and you will see it here tomorrow. Keep it up!”); encouraging messages for the user (e.g., “Your new goal is [hours], and you will see it here tomorrow. Keep it up!” or “Well done, [user name]! You have reached your goal for 5 out of the last 7 days. Challenge yourself and raise your goal by one hour! Accept the challenge”); (4) prompting the user to accept a new challenge (e.g., “Well done, [user name]! You have reached your goal for 5 out of the last 7 days. Challenge yourself and raise your goal by one hour! Accept the challenge”); and (5) notifying the user when a score is available (e.g., “Score! Your first meal score is available. Tap the meal card below for details.”).

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

[0138] In some example implementations, and as in, for example Figures 4E-1 to 4E-4 As depicted, TIR card 431 can be arranged on the home GUI 430 directly adjacent to and above the analyzer graphics card 4310. Furthermore, logbook section 4308 can be arranged directly adjacent to and below the analyzer graphics card 4311 on the home GUI 430.

[0139] also, Figure 4E-6 The illustration shows the homepage GUI 430 of a user using the TIR application on the first day or within the first 24 hours. (Example) Figure 4E-6 As depicted, the homepage GUI 430 includes an analyte graphics card 4311 without analyte trend lines. In some embodiments, and before the user enters meals into the TIR application, the homepage GUI 430 includes a logbook section 4308 containing a list of meal events that have not been entered. In some embodiments, and as... Figure 4E-6 As depicted, the logbook section 4308 includes a note 446 informing the user that no meals have been added yet. According to another embodiment, and before setting daily TIR goals in the TIR application, the home GUI 430 may include a TIR card 431 within the TIR ring 436 that does not contain daily TIR goals or TIR values. In some embodiments, and as... Figure 4E-6As shown, and before setting the daily TIR target in the TIR application, the TIR card 431 may include a message 447 informing the user that the TIR application is collecting user data. Furthermore, in some embodiments, and before setting the daily TIR target in the TIR application, the TIR card 431 may also include a selectable information icon 448 that outputs an information modality 465 when selected by the user. Figure 4H ).like Figure 4H As shown, information modality 465 may include message 466 informing the user that the TIR application is in the process of setting personalized TIR goals for the user during the first 24 hours of computation using the TIR application. Additionally, information modality 465 may also include message 466 with a reminder instructing the user to periodically scan the sensors while the user waits. Information modality 465 may be configured to partially obscure or overlay the underlying homepage GUI 430. In some embodiments, information modality 465 may also include a selectable "OK" button 467 that the user can press.

[0140] Figure 4E-7 The homepage GUI 430 is depicted after a personalized daily TIR goal 437 has been set. Specifically, Figure 4E-7 A homepage GUI 430 is depicted, which includes a TIR card 431 containing the user's daily TIR target 437. In some implementations, the daily TIR target 437 can be set before the TIR application displays the analyte trend line or before the user enters any dietary events (e.g., ...). Figure 4E-7 As shown in the diagram). According to one aspect of the embodiment, the daily TIR target 437 and TIR value 4305 within the TIR ring 436 can be measured. Figure 4E-7 (Not shown in the image), and it is displayed on the main GUI 430 as a numerical value indicating the hours and the unit of measurement. In some implementations, if a daily TIR target 437 is set but the TIR hours for a specific time period have not yet been detected, a placeholder image or photograph 449 can be displayed in the TIR ring 436, such as... Figure 4E-7 As shown in the diagram. In some implementations, after setting the daily TIR target 437, mode 470 can be output ( Figure 4I This modality informs the user that a new TIR target has been set. In some implementations, modality 470 may also inform the user that the TIR target can be changed through settings in the TIR application.

[0141] In some implementations, and Figure 4E-7As best depicted, the homepage GUI 430 may also include a text description 4333 indicating the day of the week, wherein the text description 4333 includes the date adjacent to the toggle control 4334 configured to be switched. In some embodiments, the homepage GUI 430 may be associated with a past day, wherein the text description 4333 includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the homepage GUI 430 is associated with a past day, the homepage GUI 430 may also include a selectable "Go to Today" link, which, when selected, outputs the homepage GUI 430 corresponding to that day.

[0142] Go to Figure 4J-1 and Figure 4J-3 This describes an additional implementation of the homepage GUI 485. The homepage GUI 485 is similar to the homepage GUI 430 (see, for example...). Figure 4E-1 In addition to the logbook section 4808 of the homepage GUI 485, which includes one or more Time of Day (“TOD”) cards 4801, such as Figure 4J-1 and Figure 4J-3 As shown in the diagram. Specifically, the homepage GUI 485 includes a TIR card 4819, an analyte graphic card 4811, a logbook section 4808, a selectable homepage icon 4821, and a selectable "+" icon 4823. The TIR card includes information related to the amount of time that indicates glucose levels within a predetermined analyte range (e.g., a predetermined glucose range). In some embodiments, and as shown in the diagram... Figures 4J-1 to 4J-3 As shown, the homepage GUI 485 also includes a selectable insight icon 4804 instead of a meal icon. Specifically, when the user selects the insight icon 4804, the output is either Insight GUI 14000 or Insight GUI 150000 (e.g., respectively). Figures 14A-1 to 14A-5 ,as well as Figures 15A-1 to 15A-5 This will be described in further detail below. Those skilled in the art will understand that the dietary icons can replace the insight icons 4804 and be used in conjunction with the homepage GUI 485.

[0143] refer to Figures 4J-1 to 4J-3 Each TOD card 4801 in the logbook section 4808 of the homepage GUI 485 can represent a different increment or time period for a specific day. In some implementations, and as... Figure 4J-1 As best illustrated, the logbook section 4808 may include four different TOD cards 4801, each TOD card 4801 representing a different six-hour period of a particular day. For example, and as shown... Figure 4J-1As best depicted herein, the logbook portion 4808 may include, but is not limited to: (1) an “overnight” TOD card 4801a (e.g., a TOD card 4801 corresponding to the time period from 12:00 AM to 6:00 AM on a particular day); (2) a “morning” time card 4801b (e.g., a TOD card 4801 corresponding to the time period from 6:00 AM to 12:00 PM on a particular day); (3) an “afternoon” TOD card 4801c (e.g., a TOD card 4801 corresponding to the time period from 12:00 AM to 6:00 AM on a particular day); and (4) an “evening” TOD card 4801d (e.g., a TOD card 4801 corresponding to the time period from 6:00 PM to 12:00 AM on a particular day). Those skilled in the art will understand that various TOD cards 4801 and the time periods associated with each TOD card 4801 may be utilized without departing from the scope of this disclosure.

[0144] In some implementations, and still referencing Figures 4J-1 to 4J-3Each TOD card 4801 may include, but is not limited to: (1) a TOD indicator 4802 (e.g., “overnight,” “morning,” “afternoon,” or “evening”) configured to indicate the time of day represented by the TOD card 4801; (2) a time period indicator 4803 (e.g., “12:00 AM to 6:00 AM” for overnight TOD card 4801, “6:00 AM to 12:00 PM” for morning TOD card 4801, “12:00 PM to 6:00 PM” for afternoon TOD card 4801, and “6:00 PM to 12:00 AM” for evening TOD card 4801) configured to indicate the time period represented by the corresponding TOD card 4801; and (3) a TOD icon 4804 configured to indicate the time period associated with the TOD card 4801 (e.g., for use with the TOD card 4801). The TOD icon 4804 represents the moon with the letter "Z" for the overnight time period of the overnight TOD card 4801, the TOD icon 4804 represents half a sun or sunrise for the morning time period of the morning TOD card 4801, the TOD icon 4804 represents the whole sun for the afternoon time period of the afternoon TOD card 4801, and the TOD icon 4804 represents the moon for the evening time period of the night TOD card 4801; and (4) a graphical representation 4805 indicating the average analyte score (e.g., average glucose score) associated with the time period represented by each corresponding TOD card 4801 (e.g., the average glucose score corresponding to the time period between 12:00 AM and 6:00 AM is represented by the graphical representation of the overnight TOD card 4801). Those skilled in the art will recognize that various different time periods can be used to indicate the time period indicator 4803 using other time ranges or time periods. According to some embodiments, the time period represented by the time period indicator 4803 may be user-defined and / or configurable. Furthermore, according to one aspect of the implementation, the average analyte score associated with the TOD card 4801 and the current time of day is configured to be continuously updated. For example, if the current time of day is 9:00 AM, the morning TOD card 4801 (e.g., representing the TOD card 4801 for the period between 6:00 AM and 12:00 PM) is configured to continuously update the average analyte score of the morning TOD card 4801.

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

[0146] In some example implementations, and as Figures 4J-1 to 4J-3 As best illustrated, the graphical representation 4805 includes segmented portions 4806, where each segment is configured to be filled with color (or not colored at all) to correspond to the average analyte fraction. In the example embodiment, and as... Figure 4J-1As best shown in the diagram, the graphical representation 4805 may include a segmented bar with three segmented portions 4806, wherein: (1) the first segment 4806a may be red or orange and indicates the analyte fraction corresponding to a high glucose effect or response (e.g., an average glucose range exceeding 250 mg / dL); (2) the first segment 4806a and the second segment 4806b may be yellow and indicate the analyte fraction corresponding to a moderate glucose effect or response (e.g., an average glucose range between 181 mg / dL and 250 mg / dL, or not greater than 250 mg / dL and / or at least 181 mg / dL); or (3) the first segment 4806a, the second segment 4806b and the third segment 4806c may be green and indicate the analyte fraction corresponding to a low glucose effect or response (e.g., an average glucose range between 70 mg / dL and 180 mg / dL, or not greater than 180 mg / dL). In some embodiments, although not illustrated, if the average glucose fraction corresponds to a low glucose effect (e.g., an average glucose range below 70 mg / dL), the graphical representation 4805 is replaced with a "low" icon instead of the segmented portion 4806. Those skilled in the art will understand that various other graphical representations and colors, as well as color configurations, may be used in conjunction with the graphical representations without departing from the scope of this disclosure.

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

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

[0149] Turn to Figure 4J-1 and Figure 4J-3 Each TOD card 4801 can switch between a collapsed view and an unfolded view. Specifically, according to some implementations, in the collapsed view (see, for example...), Figure 4J-1 Each TOD card 4801 is configured in a collapsed view. The TOD card 4801 is configured to display a TOD indicator 4802, a time period indicator 4803, a TOD icon 4804 representing the time period associated with the TOD card 4801, and a graphical representation 4805 indicating the average glucose score associated with the time period represented by the corresponding TOD card 4801. Furthermore, according to some embodiments, in the expanded view (see, for example...), Figure 4J-3In this configuration, the TOD card 4801 is configured in an expanded view at night. The expanded view 4801 displays a TOD indicator 4802, a time period indicator 4803, a TOD icon 4804 representing the time period associated with the TOD card 4801, a graphical representation 4805 indicating the average glucose score associated with the time period represented by the corresponding TOD card 4801, and a list 4822 of dietary information including one or more dietary events 4829 that occurred during the relevant time period associated with the TOD card 4801. Furthermore, in some embodiments, in the expanded view of the corresponding TOD card 4801, the TOD card 4801 is configured to display a dietary record link 4809, which outputs a dietary record GUI 500 when selected by the user, such as... Figure 5A As shown and further described below.

[0150] Specifically, in some implementations, if a user enters dietary information via the dietary record GUI 500, details related to the entered dietary information are displayed as dietary events 4829 in a list 4822 of dietary information for the corresponding TOD card 4801, with the dietary record link 4809 selected from that TOD card. In some example implementations, and as... Figure 4J-3 As best shown in the image, the meal record link 4809 is directly adjacent to and below the list 4822 of meal events 4829 displayed on the specific TOD card 4801 in the expanded view.

[0151] In some implementations, and as such Figure 4J-3 As best illustrated, each TOD card 4801 can be configured to include information about one or more meal events 4829 that occurred within the time period represented by the respective TOD card 4801. According to one aspect of the implementation, each meal event 4829 may include a text description 4823 of the meal, a meal type indicator 4824 describing whether the entered meal information describes food or beverage, a timestamp 4825 associated with the time the meal was consumed, and / or a photograph or image 4826 of the meal. In some implementations, a placeholder image is displayed instead when the user does not associate a photograph or image 4826 with a meal. In some example implementations, the list 4822 may be sorted such that, for each TOD card 4801, the meal event 4829 corresponding to the most recently consumed meal is presented first or at the top of the list 4829, with subsequent meal events 4829 displayed chronologically.

[0152] Furthermore, in some example implementations, each dietary event 4829 is configured to respond to a fifth predetermined input from the user (such as when the user taps a specific dietary event 4829 or via some other predetermined gesture) to output a dietary comment GUI 800 or a dietary comment GUI 8000 related to the selected dietary event 4829 (e.g., as shown below). Figure 8A and Figures 8B to 8E As shown in the diagram, and as will be described in further detail below.

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

[0154] According to another aspect of the implementation, each TOD card 4801 is configured to switch between a folded view and an unfolded view in response to a sixth predetermined input from a user on the corresponding TOD card 4801 (such as when the user taps, pulls down on the TOD card 4801, pulls up on the TOD card 4801, or by some other predetermined gesture). For example, in an example implementation, each TOD card 4801 may switch from displaying a folded view to an unfolded view in response to received user input (e.g., by a tap gesture, a pull-down gesture, or by selecting or pressing a corresponding area of ​​the TOD card 4801). Furthermore, in some implementations, the TOD card 4801 may switch from displaying an unfolded view to a folded view in response to received user input (e.g., by a tap gesture, a pull-up gesture, or by selecting or pressing a corresponding area of ​​the TOD card 4801).

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

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

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

[0158] According to another aspect of the implementation, and as Figure 4J-1 As best illustrated, the logbook section 4808 is also configured to display the TOD card 4801 associated with the elapsed or historical time period of a specific day presented on the interface and the current time period. For example, in some embodiments, and as shown in... Figure 4J-1As shown, if the current time of day is 7 PM, the logbook section 4808 is configured to display overnight TOD cards 4801a, morning TOD cards 4801b, afternoon TOD cards 4801c, and evening TOD cards 4801d. In some embodiments, the time period indicator for the TOD card 4801 corresponding to the current time of day (e.g., afternoon TOD card 4801 if the current time of day is 3 PM) is configured to display a progress stamp 4812 (e.g., "Now") to indicate that a specific time period is current or in progress. In some embodiments, the progress stamp 4812 is displayed as part of the TOD indicator 4802. For example, if the current time of day is 3 PM, the afternoon TOD card 4801 may display the time period indicator 4803 "12 PM to Now" to indicate that the current time of day is within the time period associated with the active state of the TOD card 4801 (e.g., 12 PM to 6 PM for the afternoon TOD card 4801).

[0159] In some implementations, and as in Figure 4J-1 As best illustrated, the homepage GUI 485 may also include a text description 4833 indicating the day of the week, wherein the text description 4833 includes the date adjacent to the toggle control 4834 configured to be switched. In some embodiments, the homepage GUI 485 may be associated with a past day, wherein the text description 4833 includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the homepage GUI 485 is associated with a past day, the homepage GUI 485 may also include a selectable "Go to Today" link, which, when selected, outputs the homepage GUI 485 corresponding to that day.

[0160] Go to Figures 4K-1 to 4K-3 A block diagram of an additional example implementation of a homepage GUI 495 for a TIR application is shown. In some implementations, the homepage GUI 495 may include: (1) a daily scorecard 4951; (2) an analysis graphic card 4911; (3) a logbook section 4958; (4) a selectable homepage icon 4953 that outputs the homepage GUI 495 when selected by the user; and (5) a selectable insight icon 4954 that outputs either Insight GUI 14000 or Insight GUI 150000 (e.g., respectively) when selected by the user. Figures 14A-1 to 14A-5 ,as well as Figures 15A-1 to 15A-5 ), as will be described in further detail below; and (6) the “+” icon 4957, which, when selected by the user, outputs a diet record GUI 500 configured to receive dietary information input by the user (see, for example) Figures 5A to 5G ).

[0161] According to one aspect of the implementation, the homepage GUI 495 is similar to the homepage GUI 485 (see, for example...). Figures 4J-1 to 4J-3 This is in addition to including a daily score card 4951 instead of a TIR card. In some implementations, the daily score card 4951 may be controlled to use graphical elements (such as daily score circles or rings 4903) to highlight the user's "daily score" based on the user's recorded diet and / or the user's analytes (e.g., glucose). Figure 4K-1 As seen in the diagram, the daily score card 4951 shows a daily score ring 4903, with a daily score value 4904 (points earned daily) inside or within the inner area of ​​the daily score ring 4903. For example, the daily score value 4904 may include a numerical value and unit of measurement indicating the user's earned daily score (e.g., "80 points"). In some implementations, the user's current daily score relative to a predetermined target daily score may be displayed in two ways: (1) the daily score value 4904 may be a numerical value and unit of measurement (e.g., "80 points") listed inside the daily score ring 4904; and (2) the daily score value 4904 may be visually displayed as a progress indicator 4905 (e.g., a shaded portion) extending along the circumference of the daily score ring 4903 to X% of the total circumference of the daily score ring 4903, to indicate that the user has earned X% of the predetermined target daily score (e.g., where X% is the daily score value 4904 divided by the predetermined target daily score). In this way, the ratio of the circumference of the daily score ring 4903, including the progress indicator 4905 (e.g., the shaded portion), to the total circumference of the daily score ring 4903 is proportional to the ratio of the daily score value 4904 that the user has obtained within a predetermined daily score range during the day. In some embodiments, the progress indicator 4905 may include a color with a gradient configured to transition between various shades. In this way, the degree to which the color gradient transitions between various shades indicates the user's progress toward their predetermined daily score goal.

[0162] Those skilled in the art will further recognize that other types of progress indicators 4905 (e.g., text, numbers, or graphics) may also be utilized, and such indicators are entirely within the scope of this disclosure. Furthermore, although the illustrated graphic elements are circles or rings with shaded portions including gradients, those skilled in the art will understand that other geometries, colors, and quantities of portions or gradients may be utilized, and such portions or gradients are entirely within the scope of this disclosure.

[0163] In some implementations, and as such Figure 4K-1In the best-case scenario, the daily score card 4951 may also include a selectable information icon 4907, which, when selected by the user, outputs a daily score information screen 4950 related to the daily score card 4951. Figure 4L For example, and as Figure 4L As depicted, the Daily Score Information Screen 4950 provides details on how the Daily Score Ring 4903 visually displays the progress indicator 4905 and the daily score value 4904. In some embodiments, the Daily Score Information Screen 4950 also informs the user that the daily score is calculated daily and resets at a predetermined hour (e.g., midnight).

[0164] In some implementations, such as Figure 4K-2 As shown, the daily scorecard 4951 may also include a message 4906 that instructs the user on their daily score at the end of a specific day (e.g., "You achieved 87 points!"). Furthermore, and as... Figure 4K-2 As best illustrated, in some embodiments, the logbook section 4958 may include a list 4952 of meal events 4959 instead of one or more TOD cards.

[0165] also, Figure 4K-3 The homepage GUI495 is shown after the user first uses the TIR application and before entering a meal plan. (See also:) Figure 4K-3 As depicted, the homepage GUI 495 includes an analyte graphics card 4911 without analyte trend lines. In some embodiments, and before the user inputs meals into the TIR application, the homepage GUI 495 includes a logbook section 4958 containing a list of unentered meal events. According to another aspect of the embodiment, and as... Figure 4K-3 Ideally, a notification card 4908 is displayed on the homepage GUI 495 to replace the daily score card. Specifically, the notification card 4908 can inform the user that the user can use a predetermined gesture (e.g., tap) on the "+" icon 4957 to enter meals into the TIR application.

[0166] In some implementations, and Figure 4K-3As best illustrated, the homepage GUI 495 may also include a text description 4933 indicating the day of the week, wherein the text description 4933 includes the date adjacent to the toggle control 4934 configured to be switched. In some embodiments, the homepage GUI 495 may be associated with a past day, wherein the text description 4933 includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the homepage GUI 495 is associated with a past day, the homepage GUI 495 may also include a selectable "Go to Today" link, which, when selected, outputs the homepage GUI 495 corresponding to that day.

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

[0168] In some implementations, and as in Figure 4M-1 As best illustrated, the homepage GUI 499 may also include a text description 4973 indicating the day of the week, wherein the text description 4973 includes the date adjacent to the toggle control 4974 configured to be switched. In some embodiments, the homepage GUI 499 may be associated with a past day, wherein the text description 4973 includes the date associated with the past day (e.g., "Friday, February 11"). In some embodiments, although not illustrated, when the homepage GUI 499 is associated with a past day, the homepage GUI 499 may also include a selectable "Go to Today" link, which, when selected, outputs the homepage GUI 499 corresponding to that day.

[0169] like Figure 4M-1 and Figure 4M-2As illustrated in the diagram, each dietary event 4999 may additionally or alternatively include a rating or score 4922 for a single specific diet based on its associated analyte response (e.g., glucose response). In some embodiments, the analyte response may be based on changes in analyte levels (e.g., glucose levels) over a predetermined time period following the consumption of the specific diet. In some embodiments, the diet is assigned a score 4922 based on the analyte level offset from the time of consumption of the specific diet to the peak glucose level within three hours of eating.

[0170] Furthermore, the fraction 4922 can be displayed as a numerical value. In some implementations, the fraction 4922 can be a number between one and five, where a higher allocation value corresponds to a lower analyte response, and a lower allocation value corresponds to a higher analyte response.

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

[0172] Furthermore, according to another aspect of the implementation, the homepage GUI 499 is similar to, for example... Figure 4E-1 The homepage GUI 430 depicted in the text displays the average dietary rating card 4991 instead of the TIR card. Specifically, according to one aspect of the implementation, and as... Figures 4M-1 to 4M-3 As shown, the average dietary rating card 4991 includes an average dietary rating 4920, which can be displayed as a numerical value, and a graphical indicator 4921 corresponding to the average dietary rating 4920. More specifically, the average dietary rating 4920 is the average of the scores 4922 of all rated dietary events 4999 within a predetermined time period (e.g., a specific time period of day), or it can be based on the average of the scores 4922 of multiple rated dietary events 4999 within a predetermined time period (e.g., the scores of all rated dietary events of a specific type of diet, such as the scores 4922 of all rated breakfasts). In some embodiments, and as... Figures 4M-1 to 4M-3 As best depicted, the average dietary rating 4920 can be a number between one and five, where a higher allocation value corresponds to a lower average analyte response, and a lower allocation value corresponds to a higher average analyte response. In some embodiments, the average dietary rating 4920 is displayed as a numerical value including one or more decimal values ​​(e.g., an average dietary rating of "5.0").

[0173] For example, if a single dietary event 4999 is recorded for a specific day (where one dietary event 4999 is given a score of "5" 4922), then the average dietary rating card 4991 will display an average dietary rating of "5" or "5.0". Furthermore, if two dietary events 4999 are recorded for a specific day (where one dietary event 4999 is given a score of "5" 4922, and the second dietary event 4999 is given a score of "1"), then the average dietary rating 4920 will be "3" or "3.0", which is the average of the scores 4922 for the two dietary events 4999 (e.g., ...). Figure 4M-1 (As shown in the diagram). In some implementations, if a user has recorded two meal events 4999 but only one has been rated, the average meal rating 4920 will only consider the rated meal event 4999, as shown in the diagram. Figure 4M-2 As shown in the figure. In some implementations, the average dietary rating 4920 is configured to be updated continuously and automatically to take into account all dietary events 4999 being rated within a predetermined time period.

[0174] like Figures 4M-1 to 4M-3As best illustrated in the diagram, and according to another aspect of the embodiment, the average dietary rating card 4991 also includes a graphic indicator 4921 for an average dietary rating 4920. Specifically, the graphic indicator 4921 may include an average dietary rating indicator 4923 that visually represents the average dietary rating provided over a predetermined time period (e.g., a specific time period of day). In some embodiments, the graphic indicator 4921 is a plurality of asterisks including colored portions, wherein the ratio of each asterisk including a colored portion to the total number of asterisks is proportional to the ratio of the average dietary rating 4920 to the maximum available dietary rating. Those skilled in the art will understand that other graphic indicators 4921, indicators 4923, and symbols (e.g., emojis, trophy icons, bars, triangles, squares, circles, etc.) may be used instead of asterisk icons without departing from the scope of this disclosure.

[0175] In some implementations, and as such Figure 4M-3 In the best-illustrated representation, when the average dietary rating 4920 is not an integer (e.g., the average dietary rating 4920 is "3.4"), the graphic indicator 4921 may include at least one asterisk with a half-colored portion. For example, if the average dietary rating 4920 is "3.4", the graphic indicator 4921 may display three of the five asterisks with a full-colored portion and one of the five asterisks with a half-colored portion, as shown below. Figure 4M-3 As depicted in the text.

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

[0177] In some implementations, and with reference to Figure 4M-5If the user deletes all rated meals, if the user does not receive an average meal rating for a predetermined time period (e.g., this day), or if the meal event has not been rated within the predetermined time period, the average meal rating card 4991 does not display the average meal rating, and the graphic indicator 4921 corresponding to the average meal rating includes multiple asterisks, wherein none of the asterisks includes a colored portion and is unfilled. In some implementations, if the user deletes all rated meals or if the meal event has not been rated within the predetermined time period, prompt 4925 (see, for example...) Figure 4M-5 This will appear on the average dietary rating card 4991. Specifically, and as... Figure 4M-5 As shown, prompt 4925 informs the user that after recording their meals and obtaining a first meal rating for a predetermined time period (e.g., this day), the user will receive an average meal rating 4920. In some implementations, after the user records their first meal and / or cancels prompt 4925 (e.g., by tapping the exit button), prompt 4925 is removed from the average meal rating card 4991 and will not reappear.

[0178] Furthermore, in some implementations, and with reference to Figure 4M-6 If the user does not receive an average dietary rating for a predetermined time period (e.g., this day), the average dietary rating card 4991 will not display an average dietary rating, and the graphic indicator 4921 will include multiple asterisks, wherein none of the asterisks includes a colored portion and the multiple asterisks are unfilled. Additionally, in some implementations, if the user does not receive an average dietary rating for a predetermined time period (e.g., this day), a message 4926 will appear on the average dietary rating card 4991, informing the user that no dietary rating is available during the predetermined time period (e.g., "No dietary rating is available on this day").

[0179] In some implementations, and as such Figures 4M-1 to 4M-4 and Figure 4M-6 The average dietary rating card 4991 depicted includes an information icon 4927, which outputs the average dietary rating modality 4990 when selected. Figure 4N Specifically, and as Figure 4N As shown, the Average Dietary Rating Modus 4990 can inform users that the average dietary rating is based on the dietary logs of all users with ratings over a predetermined time period (e.g., between midnight and 11:59 PM). Furthermore, the Average Dietary Rating Modus 4990 can also inform users that their average dietary rating can change as new dietary ratings or scores become available throughout the predetermined time period (e.g., the entire day).

[0180] According to another aspect of some implementations, and in particular referring to Figures 4M-1 to 4M-3 One or more meal icons 49014 may be displayed on the analyte trend line 49015. In some embodiments, one or more meal icons 49014 may be displayed near, close to, and / or below the analyte trend line 49015, or along the x-axis, at the top or bottom of the graphics window 49904. Additionally, in some embodiments, one or more meal icons 49014 may be displayed with or without leaders. Each meal icon 49014 may be a photograph or image associated with a specific meal. In some aspects of the embodiments, meal icons 49014 are positioned on the analyte trend line 49015 to allow the user to visually associate the post-meal analyte trajectory with the relevant meal. In some embodiments, meal icons 49014 are positioned on the analyte trend line 49015 based on the time associated with the meal. For example, if dietary event 4992 indicates that the blueberry oatmeal was consumed at 8:04 AM, then the dietary icon 49014 corresponding to the blueberry oatmeal dietary event 4992 will be displayed on the x-axis of the analyte graph 49011 at approximately 8:04 AM.

[0181] Those skilled in the art will understand that any GUI (or portions thereof) described herein is intended for illustrative purposes only, and that any individual elements or combinations thereof depicted and / or described with respect to a particular embodiment or figure may be freely combined with any other elements or combinations thereof depicted and / or described with respect to any other embodiment.

[0182] Example implementation of the diet record GUI

[0183] Go to Figures 5A to 5N This section will describe an example implementation of a diet record interface and its associated features. First, refer to... Figure 5A When a user selects the "+" icon in any GUI implementation described herein that includes a "+" icon, or the meal recording button in any GUI implementation described herein corresponding to a detected missed meal, the meal recording GUI 500 (which will be described in further detail below) is displayed. In some implementations, the TIR application may prompt the user to record meals, for example, if a meal event is detected or a predetermined time period has elapsed. Users of the TIR application may also voluntarily record meals without any prompting. Figure 5B As seen in the document, if a user wishes to voluntarily add meals, they can select the option to add meals, for example, by tapping the "+" icon on any GUI implementation that includes the "+" icon described herein. This will then populate or display the meal record GUI 500. Figure 5A and Figure 5BAs shown, the meal record GUI 500 may include a meal entry field 501, which allows the user to enter the name or description of a food as a meal entry. When the user enters characters of a meal or food name into the meal entry field 501 ( Figure 5B The TIR application can automatically suggest entries based on a user's past meal entries. For example, in some implementations, the TIR application can retrieve information related to past meal entries with the same (or similar) food names and display them, for example, as a list of past meal events 503 in the results section 502. If the desired food name appears in the results section 502, the user can conveniently select a meal entry without having to type the full name of the food or meal.

[0184] Furthermore, despite Figure 5B The results section 502 is shown in list form, but those skilled in the art will understand that other interfaces can be implemented, such as by manually entering text, by selecting a meal name from a list (e.g., a selection list or dropdown list), by selecting a meal image from a set of images, by selecting an identifiable marker of the meal (e.g., a label), or any combination thereof. In some embodiments, score information icons 522 (e.g., Figure 5D The results section displays the score information icon 522, which, when selected, outputs a dietary score information modality that includes information about the different score options and how dietary scores are determined.

[0185] According to another aspect of the implementation, and as Figure 5D As shown, if the input is dietary information that has not been identified as a past meal, the results section 502 will indicate that no past meals were found. After entering new dietary information, the user can select the continue button 504, which enables the display to be configured to request additional information 510, such as, for example... Figure 5E As seen in [the image / image]. Users can edit meal entries as needed. For example, a user can click the pencil icon 505 next to the name of the meal or food that appears in the meal entry description 506.

[0186] Modality 510 may include a portion indicator 511 option indicating the relative portion size of the consumed meal, such as selectable buttons indicating different portion sizes, like "smaller," "typical," and "larger." The user can also add photos / images 512 of the meal to be associated with it. For example, modality 510 may include a camera icon 513 that, when selected or clicked, opens the camera of a device with a time-lapse application installed on it, allowing the user to take a picture of the food or alternatively select an image from a photo library. Modality 510 may also include meal label entries 514, where the user can type one or more meal labels 515 to be associated with the consumed meal. Meal label 515 (e.g., Figure 5F () can be keywords that specify or describe one or more of the components and / or characteristics of a meal, or additional content consumed with the meal. For example, a meal label 515 could refer to specific details of the meal or side dishes consumed with it, as well as a list of food types, such as carrots, lettuce, blueberries, cheese, bananas, and fries. Figure 5F As shown in the image, for example, select the "Carrot" dietary label. After entering the dietary information, the user can click "Save" to record the information.

[0187] In some implementations, modality 510 also includes a time field 517 that includes the time and date associated with the meal entry. In some implementations, the time field 517 may be automatically associated with the meal entry, or based on the user's selection of the continue button 504 (e.g., ...). Figure 5D The time is automatically filled. According to one aspect of some implementation methods, and as... Figure 5G As shown in the diagram, the automatically filled time field 517 can still be edited by the user.

[0188] According to another aspect of the implementation, and as Figure 5C As shown, if a user selects a previously entered meal, the meal entry can be pre-populated with past meal information and assigned the current date and time. Furthermore, as... Figure 5C As shown, a meal entry modal 520 (also known as a meal entry modal window) will appear, which includes a time field 527 with the current date and time, and information associated with a past meal event 503. Users can edit meal entries as needed. Users can edit the meal name by clicking the pencil icon 525 adjacent to the meal name. Users can edit meal entries to add meal names. Users can also select the camera icon 531 and edit the image 532 associated with the meal entry. Users can also edit the meal tag 533 associated with the past meal event 503. Users can click "Add Meal" 535 to record information.

[0189] Now for reference Figure 5H A block diagram depicting an example embodiment of modality 530 is shown. Modality 530 is similar to modality 510 (Figure E), except that it does not display photos / pictures associated with meals. In some embodiments, such as Figure 5H As depicted, when a user does not associate a photo or image with a meal, a placeholder image 534 will be displayed instead. Similar to modal 510, modal 530 may include a camera icon 536, which, when selected or clicked, opens the camera of a device on which the TIR application is installed, and the user can take a picture of the food or alternatively select an image from the photo library.

[0190] Figures 5I to 5N These are various block diagrams illustrating example implementations of a camera interface or its related features, any of which can be used in conjunction with the implementations described herein. References Figure 5I The document describes a camera GUI 540 that allows the user to select the camera icon 513 on a previously described interface implementation. Figure 5E ) or 531 ( Figure 5H The following is displayed. In some implementations, the device's camera cannot be used until the user grants the TIR application permission to access the camera. Camera GUI 540 relates to enabling camera access. In some implementations, camera GUI 540 may include a modal prompting the user to enable camera access.

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

[0192] Figure 5K The diagram illustrates a block diagram of an example implementation of a camera GUI 560, wherein the camera GUI 560 includes an indicator specifying that camera access has been restricted. Figure 5L The diagram illustrates a block diagram of an example embodiment of a camera GUI 570, wherein the camera GUI 570 includes an indicator indicating that the camera of the specified device is unavailable.

[0193] Figure 5M and Figure 5NBlock diagrams illustrating example embodiments of camera GUIs 580 and 590 involving photo capture and / or selection are shown respectively. In some embodiments, and with reference to... Figure 5M The camera GUI 580 may include a retake button that, when selected by the user, removes the previously captured photo and allows the user to take another photo associated with a specific meal. In some implementations, the camera GUI 580 includes a "Use Photo" button that, when selected by the user, allows the user to use the captured photo and associate it with a specific meal. Furthermore, Figure 5N An example implementation of a camera GUI 590 is depicted, in which photos are displayed. In some implementations, the camera GUI 590 includes a library button that, when selected by the user, allows the user to browse photos stored on the device. In some implementations, the camera GUI 590 also includes a "skip" button that, when selected by the user, allows the user to skip using photos displayed on the camera GUI 590.

[0194] According to some implementations, after a user successfully logs in and saves their meal plan, the user will be redirected to a GUI that guides them to the meal plan login GUI 500. For example, if the user is in GUI 12100 ( Figure 12D-1 and Figure 12D-2 If the user selects the "+" icon, they will be redirected to GUI 12100 after successfully recording a meal. In this way, the meal icon 12115 corresponding to the newly recorded meal will also appear on the meal timeline 12114 in GUI 12100. Figure 12D-2 Therefore, if a user associates a photo or image with a meal, then the meal icon 12115 ( Figure 12D-2 This will include photos or images. Additionally, if a user, as described in this article, uses the Insight GUI 15000 (which corresponds to one or more missed meals)... Figures 15A-1 to 15A-5 If the user selects either the "+" icon 15007 or the meal record button 15023 on the notification 15004, the user will be redirected to the Insight GUI 15000 after successfully recording a meal. In some implementations, although not illustrated, when a new meal is recorded, and as will be described in more detail below, the Insight GUI 15000 can be updated (e.g., ...). Figures 15A-1 to 15A-5 As shown in the figure, this displays the dietary events corresponding to the newly recorded meals. Furthermore, according to some implementations, and as will be described in more detail below, when a new meal is recorded, the total average dietary score for a predetermined time period can be updated to include the newly recorded meal.

[0195] Example implementations of the reporting GUI and related methods

[0196] This section describes an example implementation of a method for outputting a report GUI. Specifically, Figure 6AOperations of a method 6000 for performing a process for a reporting GUI that displays data indicating analyte levels for a particular day, along with associated non-medical statistics, are illustrated. First, those skilled in the art will recognize that the method steps described herein may include software instructions stored in the memory of a computing device of system 100 (e.g., reader 120, local computer system 170, trusted computer system 180), such that when executed by one or more processors of the computing device, the instructions cause the one or more processors to perform any or all of the method steps described herein. (Refer again) Figure 6A At 6001, the method for reporting the GUI may include receiving a seventh predetermined input (e.g., a tap or press gesture) from a user on a toggle control adjacent to a text description on the interface, wherein the text description indicates the day of the week. In one aspect of the implementation, when the user toggles down the toggle control, the displayed interface is configured to display a plurality of selectable rings, each ring being a TIR indicator corresponding to a different day of the past week. For example, in some implementations, a plurality (seven) of selectable rings are displayed on the displayed interface.

[0197] At 6002, the method for reporting the GUI also includes user selection of a specific ring from a plurality of rings displayed in response to the user switching a toggle control, wherein each of the plurality of selectable rings is a TIR indicator corresponding to a different day in the past week.

[0198] At 6003, at least one processor determines, based on data stored in a database, a dataset and dietary information indicating the level of analytes associated with the day corresponding to the selected cycle.

[0199] At 6004, an interactive reporting GUI is provided to a display device. This interactive reporting GUI is configured to display a dataset indicating analyte levels and dietary information based on the determination. The reporting GUI displays: a TIR card, an analyte graphic card reflecting data indicating analyte levels within a time period corresponding to the selected ring, and / or a dietary list reflecting dietary information within a time period corresponding to the selected ring. Those skilled in the art will recognize that method 4000 ( Figure 4A-1 Whether it is the whole or any one or more individual steps, it can be related to Figure 6A Method 6000 is implemented in combination with or as part thereof. Similarly, those skilled in the art will recognize that method 4100 ( Figure 4A-2 Whether it is the whole or any one or more individual steps, it can be related to Figure 6A Method 6000 is implemented by combining or as part of it.

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

[0201] Go to Figure 6B-1 A block diagram depicting an example implementation of a reporting GUI 600 for a TIR application is shown. As previously described, the reporting GUI 600 can be displayed in response to a user selecting a specific ring from a plurality of rings 425 displayed on the home GUI 400 or home GUI 450. Specifically, and as... Figure 6B-1 The diagram shows a report GUI 600 corresponding to the relevant day associated with the selected ring 425. The report GUI 600 may include: (1) a TIR card 601; (2) an analyte graphic card 602 reflecting data indicating analyte levels and dietary information corresponding to a specific day associated with the selected ring 425; (3) a dietary information list 603 including one or more dietary events 604; (4) a selectable "date summary" icon 605, which outputs the report GUI 600 for the relevant day when selected by the user; and (5) a selectable dietary icon 606, which outputs a dietary impact GUI 650 when selected by the user. Figure 6B-1 (Not shown in the image), the dietary impact GUI includes information about one or more dietary events 604 that occurred in a previous time period (e.g., the past week); and / or (6) a "+" icon 607, which, when selected by the user, outputs a dietary record GUI 500 configured to receive dietary information input by the user. Figure 5A ).

[0202] According to some aspects of the implementation, a plurality of rings 425 are displayed above and adjacent to the TIR card 601, each ring corresponding to a different day of the week. In some implementations, only a specific ring 425 corresponding to the displayed report GUI 600 will be highlighted, bolded, or colored to indicate that the report GUI 600 is associated with that specific ring 425. According to another aspect of the implementation, a user can switch between report GUIs 600 corresponding to a specific day by selecting the ring associated with that specific day from the plurality of rings 425. Furthermore, in some implementations, the report GUI 600 may include a "Go to Today" link 608, which, when selected, outputs either a home GUI 400 including data corresponding to that day or a report GUI 600 corresponding to that day.

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

[0204] Still referencing Figure 6B-1 And similar to the previously described homepage GUI 450, the analysis graph card 602 in the reporting GUI 600 may include an analysis graph 630, which includes an analysis trend line 631 that reflects the user's analysis level over a predetermined time period based on data indicating the analysis level. For example, and as... Figure 6B-1 As shown, the x-axis of the analyte graph 630 may include time units covering a 24-hour period (e.g., three-hour increments), while the y-axis may include measurement units (e.g., mg / dL) of the measured user analyte concentration. For example, and as... Figure 6B-1 The time shown on the x-axis in the diagram indicates the glucose concentration measured starting at 12:00 AM that day.

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

[0206] According to another aspect of the implementation, one or more meal icons 633 may be displayed on the analyte trend line 631. Each meal icon 633 may be a photograph or image associated with a specific meal. In some aspects of the implementation, meal icons 633 are positioned on the analyte trend line 631 to indicate the postprandial analyte trajectory associated with the relevant meal. In some implementations, meal icons 633 are positioned on the analyte trend line 631 based on the time associated with the meal.

[0207] Still referencing Figure 6B-1 Similar to Homepage GUI 400 and Homepage GUI 450, Reporting GUI 600 may include a list 603 of dietary information, which includes one or more dietary events 604 that occurred on a relevant day as described in Reporting GUI 600. Each dietary event 604 provides details of a specific meal consumed on the relevant day. In some embodiments, and similar to the previously described GUI implementations, each dietary event 604 may include a text description 640 of the meal, a portion indicator 641 describing the relative portion size of the meal, and / or a timestamp 642 associated with the time the meal was consumed, and / or a score 643. In some embodiments, the score 643 corresponding to a specific dietary event 604 may be displayed as a numerical value inside an asterisk icon 644. Although not illustrated, in some embodiments, dietary event 604 may include one or more dietary tags associated with the meal. Alternatively or additionally, dietary event 604 may include a photo / image 646 associated with the meal. In some embodiments, a placeholder image 646 will be displayed instead when the user does not associate a photo or image 646 with a meal. In some example implementations, list 603 may be sorted such that meal events 604 corresponding to the most recently consumed meal are presented first or at the top of list 603, with subsequent meal events 604 displayed chronologically. In some implementations, score information icon 648 is displayed on the reporting GUI 600 near and adjacent to the meal card. When selected by the user, score information icon 648 outputs a meal score information modality, which includes information about different score options and how meal scores are determined.

[0208] Go to Figure 6B-2 A block diagram depicts another example implementation of the reporting GUI 625 for TIR applications. Figure 6B-2 The report GUI 625 depicted in the text is similar to Figure 6B-1 The report GUI 600, except that it includes a selectable homepage icon 626 instead of a selectable "Daily Summary" icon 605. Figure 6B-1 In addition to the above, the reporting GUI 625 includes multiple rings 627, each corresponding to a different day of the week. Similar to the multiple rings 425 depicted in the reporting GUI 600, each of the multiple rings 627 depicted in the reporting GUI 625 represents the user's progress toward their daily TIR goal for a particular day. However, in the reporting GUI 625, the number of TIR hours a user spends on a particular day can be visually displayed through a color gradient of a specific ring among the multiple rings 627. For example, in some implementations, and as... Figure 6B-2 The lightness or darkness of the color gradient depicted in the diagram can indicate the amount of time a user spends within a specific day associated with a specific ring in the multiple rings 627.

[0209] Example implementation of the dietary influence GUI

[0210] An example implementation of a dietary impact GUI for an analyte monitoring system will now be described. Figure 7 This is a block diagram depicting an example implementation of a dietary influence GUI 700 used with an analyte monitoring system. (See diagram for example.) Figure 7 As seen in the diagram, the Dietary Effects GUI 700 can provide users with additional insights into the impact of consuming specific foods. In some implementations, the Dietary Effects GUI 700 can provide diet-related information and data indicating analyte levels over a specific time period (e.g., the past seven days).

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

[0212] In some implementations, the analyte response may be based on changes in analyte levels over a predetermined period following the consumption of a specific meal. In some implementations, a score 704 is assigned to the meal event 703 based on changes in analyte levels from the time of consumption of the specific meal event to the peak glucose level within three hours of eating.

[0213] In some implementations, the fraction 704 can be a number between one and five, where a higher fraction corresponds to a lower analyte response and a lower fraction corresponds to a higher analyte response. For example, and as previously detailed, (1) a change in analyte level from 0 mg / dL to 24 mg / dL over a three-hour postprandial period can correspond to a fraction 704 of “5”; (2) a change in analyte level from 25 mg / dL to 49 mg / dL over a three-hour postprandial period can correspond to a fraction 704 of “4”; (3) a change in analyte level from 50 mg / dL to 74 mg / dL over a three-hour postprandial period can correspond to a fraction 704 of “3”; (4) a change in analyte level from 75 mg / dL to 99 mg / dL over a three-hour postprandial period can correspond to a fraction 704 of “2”; and (5) a change in analyte level of 100 mg / dL or higher over a three-hour postprandial period can correspond to a fraction 704 of “1”. As depicted in the dietary impact GUI 700, score 704 can be displayed in graphical elements such as asterisk icon 711. In some embodiments, asterisk icon 711 is filled with a colored portion, such as yellow. In many embodiments (not shown), asterisk icon 711 is unfilled and includes a dashed outline indicating the missing dietary score 704. In some embodiments, and as... Figure 7 As depicted, the missed meal score 704 is indicated by a "?" character. In some implementations, the "?" character is displayed in the asterisk icon 711 instead of a numerical value to indicate that a particular meal was not scored. The missed meal score 704 occurs when one or both of the following conditions are met: (1) the user records the next meal too early, or (2) the time-lapse application does not have enough analyte data to score the meal (e.g., the user does not scan in time to ensure that glucose data has been transferred to the time-lapse application).

[0214] According to one aspect of the implementation, a dietary highlight card 701 is configured to display information related to a dietary event 703 that occurred within a predetermined time period (e.g., the past week). Specifically, the dietary highlight card 701 displays information related to the dietary event 703, including "Best Diet" and a title "Best Diet of the Past 7 Days" 720. In some implementations, the best diet is defined by the dietary event 703 with the highest score within the predetermined time period. In some implementations, the best diet is defined based on data indicating analyte levels, by the dietary event 703 within the previous seven-day period that provided the most desired analyte response. In some implementations, the dietary highlight card 701 includes a text description 721 of the best diet and an asterisk icon 722 including a score 724 corresponding to the best diet's allocation. The dietary highlight card 701 may also include a photograph or image 725 associated with the best diet, wherein the text description 721 and the asterisk icon 722 cover over it, partially obscuring the photograph or image 725.

[0215] According to another aspect of the implementation, each of the dietary events 703 listed on the Dietary Influence GUI 700 provides details about a specific meal consumed within a predetermined time period (e.g., a week). In some implementations, each dietary event 703 may include a text description 731 of the meal, a photo or image associated with the meal 739, a portion indicator 732 describing the relative portion size of the meal, a timestamp 733 associated with the time the meal was consumed, and / or a score 704 associated with the meal. In some implementations, dietary events 703 may additionally or alternatively include one or more dietary labels 735 associated with the meal (e.g., “lettuce,” “blueberries,” “cheese,” “banana,” “fries”). In some implementations, an information message 736 is displayed near the list 702, wherein the information message 736 informs the user that a higher score 704 means a higher probability of remaining within the target TIR range.

[0216] Still referencing Figure 7 The dietary impact GUI 700 may also include a score information icon 742. In some aspects of the implementation, each of the dietary events 703 is selectable, and when selected by the user, a dietary commentary GUI 800 or a dietary commentary GUI 8000 providing details related to the selected dietary event 803 is output (respectively). Figure 8A and Figures 8B to 8E ), which will be described further below.

[0217] In some embodiments, although not illustrated, the dietary effects GUI 700 may include a graphical representation, such as a segmented bar, instead of a star icon 711, to indicate scores 704 to the user. Specifically, although not illustrated, the dietary effects GUI 700 may include a segmented bar with three segments, wherein: (1) the first segment may be red or orange and indicates the analyte score corresponding to a high glucose effect or response (e.g., an average glucose range greater than 250 mg / dL); (2) the first and second segments may be yellow and indicate the analyte score corresponding to a moderate glucose effect or response (e.g., an average glucose range between 181 mg / dL and 250 mg / dL, or not greater than 250 mg / dL and / or at least 181 mg / dL); or (3) the first, second, and third segments may be green and indicate the analyte score corresponding to a low glucose effect or response (e.g., an average glucose range between 70 mg / dL and 180 mg / dL, or not greater than 180 mg / dL). Those skilled in the art will understand that various other graphic representations and colors, as well as color configurations, can be used in conjunction with the graphic representations without departing from the scope of this disclosure.

[0218] Example implementation of the Dietary Review GUI

[0219] An example implementation of the dietary review GUI and other related features for the analyte monitoring system will now be described. Figure 8A This is a block diagram depicting an example implementation of a dietary review GUI 800 used in conjunction with an analyte monitoring system. Figure 8A As seen in Figure 8, the Dietary Review GUI 800 can provide users with additional insights into the effects of consuming a specific food. As shown in Figure 8, users can select a dietary event from a list on the Reporting GUI 600, Dietary Impact GUI 700, Home GUI 400, Home GUI 450, Home GUI 430, Home GUI 485, Home GUI 495, or Home GUI 499, or from a list on any other interface described herein that can be configured as a home interface. After the user selects a dietary event, the Dietary Review GUI 800 can open to display details associated with the selected dietary event 803, including a photo / image 805, a description 801, a portion size indicator 802, a dietary label 804, a timestamp 806 including the date and time associated with the meal, a score 807, and / or an analyte graph 810, which includes an analyte graph 811 with an analyte trend line 812 containing data indicating analyte levels at least during the relevant time period of the meal consumption. In some implementations, although... Figure 8ANot illustrated, but the analyte graphics card 810 may include selectable information icons, which, when selected, output analyte graphics information mode 445, such as... Figure 4G As shown in the image.

[0220] Specifically, the meal review GUI 800 includes a meal description card 820, which includes a meal description 801, a portion size indicator 802, a meal label 804, and a timestamp 806. Furthermore, a score 807 is displayed in an asterisk icon 830 and positioned above the meal description 801. In some embodiments, and as... Figure 8A As illustrated in the diagram, the dietary description card 820 partially obscures the photograph or image 805 associated with the diet.

[0221] Still referencing Figure 8A And similar to the analyte graph card described in a previous GUI implementation, the analyte graph card 810 in the Dietary Review GUI 800 may include an analyte graph 811 with an analyte trend line 812 that reflects the user's analyte levels over a predetermined time period based on data indicating analyte levels. For example, and as... Figure 8A As shown, the x-axis of the analyte graph 811 may include time units covering a predetermined time period (e.g., hourly increments), while the y-axis may include measurement units (e.g., mg / dL) of the measured user analyte concentration. The analyte graph card 810 may include solid lines 813-1, 813-2 indicating the user's target analyte range associated with data indicating analyte levels. For example, the area between solid lines 813-1, 813-2 indicates the target analyte range (e.g., between 70 mg / dL and 180 mg / dL). In some embodiments, and as... Figure 8A As illustrated in the diagram, the analyte trend line 811 is configured as a dashed or broken line to represent the time period during which the user's analyte level exceeds the analyte TIR target range. Additionally, the analyte trend line 812 is configured as a solid line to represent the time period during which the user's analyte level remains within the analyte target range.

[0222] According to another aspect of the implementation, a meal icon 840 corresponding to meal event 803 can be displayed on the analyte trend line 812. The meal icon 840 can be a photograph or image associated with the meal event. In some aspects of the implementation, the meal icon 840 is positioned on the analyte trend line 812 to indicate the postprandial analyte trajectory associated with the relevant meal. In some implementations, the meal icon 840 is positioned on the analyte trend line 812 based on the time associated with the meal. In other implementations, the meal icon 840 can be positioned above or below the analyte trend line 812. In some implementations, the meal icon 840 can be positioned above or below the analyte graph 811. In some implementations, although... Figure 8A Not illustrated, but the dietary icon 840 can be placed on a dietary timeline that is separate from and different from the analyte graph 811 and / or the analyte trend line 812, as described below with reference to other interface implementations (e.g., see [link to other implementation]). Figure 12D-2 (This will be described in more detail.)

[0223] In some implementations, the dietary review GUI 800 includes analyte level statistics 850 related to the dietary event 803. For example, and as... Figure 8A As illustrated in the diagram, the diet review GUI 800 may include analyte level statistics associated with diet 850-1 (e.g., "173 mg / dL"), pre-diet analyte level 850-2 (e.g., "140 mg / dL"), and post-diet analyte level 850-3 (e.g., "95 mg / dL"). In some embodiments, the analyte level statistics 850 are displayed proximal to and adjacent to the analyte graphic card 810. In this way, a user can refer to the analyte graphic card 810 to obtain a visual representation of the diet-associated analyte level statistics 850. Furthermore, in some embodiments, a message 860 indicating a target glucose range (e.g., "Target glucose range: 70 mg / dL to 80 mg / dL") is displayed below the analyte graphic card 810. In some aspects of the embodiments, an informational message 870 is also displayed on the diet review GUI 800, indicating that medications, activities, stress, and other facts can affect glucose levels. In another aspect of the implementation, the diet review GUI 800 may also include a diet summary message 880, wherein the diet summary message 880 describes the glucose spike associated with the diet event, statistics related to the user's TIR, and may include an incentive message (e.g., "Your glucose spike is +33 mg / dL. You've entered the range 3 hours after this meal. Great!").

[0224] Figures 8B to 8EThis is a block diagram depicting another example implementation of a dietary review GUI 8000 for use with an analyte monitoring system. The dietary review GUI 8000 can be similar to the dietary review GUI 800, except that the score 8007 is not displayed as a star icon but includes a different graphical representation. Specifically, the score 8007 can be represented by a segmented bar 8008 having three segments 8009, wherein: (1) the first segment 8009a can be red or orange and indicates the analyte score corresponding to a high glucose effect or response (e.g., an average glucose range exceeding 250 mg / dL); (2) the first segment 8009a and the second segment 8009b can be yellow and indicate the analyte score corresponding to a moderate glucose effect or response (e.g., an average glucose range between 181 mg / dL and 250 mg / dL, or not greater than 250 mg / dL and / or at least 181 mg / dL); or (3) the first segment 8009a, the second segment 8009b and the third segment 8009c can be green and indicate the analyte score corresponding to a low glucose effect or response (e.g., an average glucose range between 70 mg / dL and 180 mg / dL, or not greater than 180 mg / dL). Those skilled in the art will understand that various other graphic representations and colors, as well as color configurations, can be used in conjunction with the graphic representations without departing from the scope of this disclosure. For example, Figure 8B The segmented bars 8008 are depicted, with the first segment 8009a and the second segment 8009b including yellow, indicating the analyte fraction corresponding to a moderate glucose effect or fraction.

[0225] Similar to the Dietary Review GUI 800, the Dietary Review GUI 8000 provides users with additional insights into the effects of consuming specific foods. For example, users can select dietary events from a list on the Reporting GUI 600, Dietary Effects GUI 700, GUI 12100, any home interface described herein, or any other interface described herein that includes selectable dietary events or dietary icons. After the user selects a dietary event or icon, the Dietary Review GUI 8000 can open to display detailed information related to the selected dietary event or icon.

[0226] In some implementations, and as such Figure 8C As shown, if the diet review GUI 8000 corresponds to a detected missed meal that the user has not yet recorded (as will be described in more detail below), the diet review GUI 8000 may include a description 8010 indicating the detected meal (“Meal Detected”) and a placeholder image 8011 as a substitute photo / picture. Furthermore, and as... Figure 8CAs shown, when a missed meal is detected, the meal review GUI 8000 may also include an in-app notification 8012 related to the detected missed meal. The in-app notification 8012 may be set between the meal description card 8016 and the meal summary message 8017.

[0227] In some implementations, and with reference to Figure 8C The in-app notification 8012 includes a query 8013 asking the user whether they have eaten (e.g., "Did you eat around 1:00 pm?") and a message 8014 instructing the user that their glucose levels have risen at a specific time and that they should record their meal (e.g., "We noticed your glucose levels rose around this time. If you have already eaten, please try to record it now."). According to one aspect of the implementation, the in-app notification 8012 may include a selectable "ignore" button 8015 and a selectable meal recording button 8022. Specifically, when the user selects the ignore button 8015, a modal (not shown) will appear instructing the user that ignoring the missed meal will delete the meal detection and return the user to the home screen. In some implementations, although not shown, the modal will include a confirmation button.

[0228] Furthermore, in some implementations, if the user selects the meal record button 8022, the meal record GUI 500 is output. Figure 5A Furthermore, in some implementations, dietary input modality 520 may occur (e.g., Figure 5C As shown in the diagram), the time field 527 is pre-populated with the date and time associated with a detected missed meal, which is associated with an in-app notification 8012 from which the meal record button 8022 was selected. In other embodiments, a meal input modality 520 may appear (e.g., Figure 5C As shown in the diagram, the user sets the date and time associated with the detected missed meal in the time field 527. In some implementations, when the meal record GUI 500 is output via the user selecting the meal record button 8022 of the meal review GUI 8000, the camera interface is not displayed to the user (e.g., Figures 5I to 5N In some implementations, once the user records meals for a specific period associated with missed meal detection (e.g., by selecting the meal recording button 8022 in in-app notification 8012), the corresponding in-app notification 1301 is removed from GUI 8000 (see, for example...). Figure 8B ).

[0229] According to another aspect of the implementation method, and specifically referring to Figure 8CMissed meal occurrence markers 8018 (such as missed meal icons 8018) may be displayed near, close to, and / or on the analyte trend line 8019 on the analyte graph 8023 displayed on the diet review GUI 8000. In some embodiments, the missed meal icon 8018 includes a placeholder image to indicate that the missed meal icon 8018 corresponds to an unrecorded meal. In some embodiments, the analyte trend line 8019 may include meal icons 8020 corresponding to other dietary events that occurred during a predetermined time period (e.g., the past 24 hours) represented by the analyte graph 8023. Furthermore, in some embodiments, the diet review GUI 8000 may include selectable edit links 8024 that, when selected, allow the user to edit information provided in the diet review GUI 8000.

[0230] In some implementations, and as such Figure 8D In the best-case scenario, if a missed meal is detected but has not yet been scored (e.g., if a predetermined time period after a particular meal has not yet ended, such as a three-hour postprandial period, then a score is not yet available for the detected missed meal), the meal review GUI 8000 does not display a graphical representation (e.g., a segmented bar 8008) corresponding to the meal score.

[0231] In some implementations, and as such Figure 8E As described, if a missed meal is detected but only partial analyte data (e.g., glucose data) is available, the Dietary Review GUI 8000 can display a graphical representation of the missed meal when scores are available. For example, and as... Figure 8E As shown, segment bars 8008 are displayed corresponding to the score 8007 for missed meals. Furthermore, and as... Figure 8E As shown, if only some analyte data is available for the detected missed diet, the diet review GUI 8000 may display an analyte graph 8023 without an analyte trend line. In some embodiments, the analyte graph 8023 will include a message indicating to the user that there is no glucose data. Furthermore, in some embodiments, if only some analyte data is available for the detected missed diet, the diet review GUI 8000 may display only a portion of the analyte level statistics. For example, and as... Figure 8E As shown, the Dietary Review GUI 8000 can display analyte level statistics associated with the peak analyte level (e.g., "195 mg / dL") of the detected diet 8021-1, the analyte level 8021-2 (e.g., "195 mg / dL") before consuming the missed diet, and the analyte level 8021-3 (e.g., "-- mg / dL") after consuming the diet.

[0232] In summary, in some example implementations, if it is determined that an attack has been detected and at least a predetermined time period (e.g., three hours) has elapsed since the corresponding meal associated with the attack was ingested, the meal review GUI 8000 may display a score 8007, an in-app notification 8012, and a missed meal attack marker 8018, as shown below. Figure 8C The best depiction is achieved in this regard. In this respect, the diet is detected and scored. Furthermore, in some implementations, if it is determined that sufficient time has elapsed to identify peak analyte values ​​in the analyte data but not sufficient time has elapsed to accurately score the diet (e.g., between 30 minutes and three hours after the diet is consumed), the diet review GUI 8000 is displayed instead of a graphical representation corresponding to the diet score, such as... Figure 8D The best depiction is as follows. In this respect, a diet is detected but not yet scored. Additionally, according to some embodiments, if it is determined that sufficient time has been passed to identify peak analyte values ​​in the analyte data and accurately score the diet associated with the detected episode, but there is missing analyte data or another diet is recorded close in time to the first diet associated with the detected episode (e.g., within a one-hour window of the first diet associated with the detected episode), the diet review GUI 8000 may display an in-app notification 8012 related to the missed diet, but may not display the score of the missed diet (e.g., similar to the diet review 8000 embodiment shown in Figure 8F, except that Figure 8F depicts the score of the missed diet). In this respect, a diet is detected but cannot be scored.

[0233] Furthermore, in some implementations, after a detected dietary event is successfully recorded, the TIR application will output something like... Figure 8B The dietary review GUI 8000 is described in the text. Furthermore, in some implementations, if a missed meal is detected but not yet recorded, the user has a predetermined amount of time to record the missed meal before it is automatically deleted. For example, in some implementations, the user has seven days to retrospectively record detected missed meals in the TIR application.

[0234] Example implementation of the beginner's guide GUI

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

[0236] also, Figures 9A to 9Q-4 This is a block diagram depicting an example implementation of a beginner-friendly GUI and its related features. For example... Figure 9A As described in the diagram, the GUI 920 allows users to log in to their accounts using a beginner's guide. Next, Figure 9B A beginner's guide GUI 925 is depicted that can provide users with a trial disclaimer. In some implementations, the beginner's guide GUI 925 includes a confirmation button 927 (e.g., an "I accept" button) that the user can press to confirm their agreement to the terms of the TIR application. Next, the beginner's guide GUI 930 is displayed to the user ( Figure 9C ).like Figure 9CAs depicted, the onboarding GUI 930 includes a name entry field 931, in which the user can enter the name that will be associated with the user's account credentials.

[0237] Next, in some implementations, and as... Figure 9D As depicted, the onboarding GUI 935 can provide an introductory greeting to the user, which includes the name entered in the prior onboarding GUI 930. In some embodiments, the onboarding GUI 935 can provide an introductory greeting to the user and indicate the benefits of using the TIR application (e.g., (1) the user can take full advantage of the TIR application by capturing the food the user eats, (2) view the impact on the user's analyte levels (such as glucose levels), and / or (3) track the user's average meal score or total average meal score). Furthermore, the onboarding GUI 935 can provide a brief description of what will appear in subsequent onboarding GUIs and an estimated reading time for what will appear in subsequent onboarding GUIs. After this, the onboarding GUI 940 can be utilized ( Figure 9E ), 945 Figure 9F ) and 950 ( Figure 9G Provide users with further information about the TIR application.

[0238] In some implementations, the beginner-friendly GUI 940 ( Figure 9E This can inform users about studies that have shown TIR can be a simple yet powerful way to track how food affects glucose levels. Additionally, and refer to... Figure 9F The onboarding GUI 945 can inform the user that the American Diabetes Association recommends a 17-hour TIR per day. In some implementations, the onboarding GUI 945 can also inform the user that because glucose activity varies from person to person, the TIR can also vary. In some implementations, the onboarding GUI 945 can also inform the user that because glucose activity depends on the user, the TIR application will suggest goals based on glucose data from the user's first day. (Reference) Figure 9G The diagram illustrates a block diagram depicting a beginner's guide GUI 950, which can inform the user that after setting a goal, the TIR ring will fill as the user spends more time in their TIR, even while the user sleeps. The beginner's guide GUI 950 may also include messages encouraging users to close the TIR ring before midnight each day to achieve their goals.

[0239] In addition, in some embodiments, a beginner-friendly GUI may be displayed, providing the user with a brief introduction on how to record meals in the TIR application. Furthermore, in some embodiments, a beginner-friendly GUI may be displayed, including a link that, when selected by the user, outputs a meal recording information modality, which includes prompts for adding meals through the TIR application. In some embodiments, a beginner-friendly GUI may be displayed, providing the user with information related to meal ratings or scores. For example, in some embodiments, although not illustrated, the beginner-friendly GUI may explain to the user that the TIR application rates meals based on changes in glucose levels after eating. Furthermore, in some embodiments, the beginner-friendly GUI may also explain that a 5-star meal will cause the minimum increase in glucose, while a 1-star meal will cause the maximum. In other example embodiments, the beginner-friendly GUI may also explain that receiving meals filled with green bars will result in the minimum increase in the user's glucose, while not filling orange bars will result in the maximum increase, and that over time, the user will see which foods are most helpful in improving the user's overall average meal score. In some implementations, although not illustrated, a beginner-friendly GUI is shown that provides the user with information related to the functional aspects of meal recording (e.g., including labels and portion sizes when recording meals).

[0240] In some implementations, the onboarding GUI providing information related to dietary ratings may include a link that, when selected, outputs a dietary rating information modality including information on how diets are ranked or rated in the TIR application, as described above. In some implementations, the dietary rating information modality including information on how diets are rated may also include emojis indicating the effect on glucose. In some implementations, the dietary rating information modality including information on how diets are ranked may also include how a rating bar is displayed when there are missing scores, and a selectable link that, when selected, outputs an information modality including information related to the missing scores. Furthermore, according to some aspects of the implementations, the dietary rating information modality may include a link that, when selected by the user, outputs another dietary rating information modality including details on why scores are measured three hours after the diet is consumed. In some implementations, the dietary rating information modality including details on why scores are measured three hours after the diet is consumed may also include a prompt that provides the user with advice on how to avoid exceeding the range over longer periods. In some implementations, the meal scoring information modality also includes details about why users should be allowed time between meals. Furthermore, the meal scoring information modality includes details about recording all foods consumed within a 30-minute window during the same meal to minimize the number of meals receiving missed scores or ratings.

[0241] Additionally, in some implementations, an information GUI may be provided that includes details about why a meal is missing a score or rating. For example, the information GUI may include one or more information cards, where each description in the information card could lead to a different scenario where a meal is not rated (e.g., the user records the next meal too quickly, or the TIR application does not have enough glucose data to rate the meal).

[0242] In some implementations, an information GUI may be provided that includes details about how the average dietary score is calculated based on a predetermined time period (e.g., based on the average dietary score calculated over the most recent 24 hours).

[0243] In another aspect of the implementation, a new user guide GUI 965 may be displayed informing the user that notifications must be allowed in order to receive alerts from the TIR application. Figure 9H In addition, the onboarding GUI 965 can also inform the user that notifications must be allowed in order to receive reminders that the user should scan sensors to keep user data updated or that the user should record meals. Furthermore, in some implementations, the onboarding GUI 965 informs the user that notifications must be allowed in order to receive notifications when new "insights" become available.

[0244] In some implementations, although Figure 9H Not illustrated, but the tutorial GUI 965 may include a "back" button that, when selected by the user, returns the user to a previously displayed tutorial GUI prior to the tutorial GUI 965. Further, in some embodiments, and as shown... Figure 9H As depicted, the onboarding GUI 965 includes a "Continue" button 982 that, when selected by the user, outputs a notification modal window 977. Specifically, the notification modal window 977 may include a "Disallow" button 983 that, when selected by the user, prevents the TIR application from sending notifications to the user. The notification modal window 977 may also include an "Allow" button 984 that, when selected by the user, allows the TIR application to send notifications to the user. In some implementations, and as... Figure 9I As depicted, the notification modal window 977 can be configured to partially obscure or overlay the underlying tutorial GUI 965, making it invisible. Furthermore, in some implementations, when the user selects the "Allow" button 984, the tutorial GUI 970 is output. Figure 9J This confirms that the new user onboarding process is complete.

[0245] Go to Figure 9K The description describes pop-up modality 975. Pop-up modality 975 includes a message informing the user that a specific dataset (e.g., the latest glucose data and the user's target glucose range) has been imported from another analyte monitoring application into the TIR application. Pop-up modality 975 also includes a message header 976 that includes the name entered by the user (e.g., "You are here, [User Name]!"). Pop-up modality 975 may also include a confirmation "OK" button that can be pressed by the user. Pop-up modality 975 may also include a celebratory emoji.

[0246] In some implementations, users can set their TIR goals through a onboarding process. Specifically, and as... Figure 9L As depicted, a user's TIR target can be set using a beginner's guide GUI 980. The beginner's guide GUI 980 may include a time entry field 9802, through which the user can manually enter the desired TIR target in time units (e.g., "17" hours). In another aspect of the implementation, and as described... Figure 9L As best depicted, a percentage entry field 9803 is provided, through which the user can manually enter the desired TIR target in percentage units (e.g., "70%" percentage). In some implementations, and as... Figure 9LAs depicted, the novice-guided GUI 980 may also include a selectable bar 9801, which is configured to update the TIR target in response to an eighth predefined input from the user (such as when the user drags the selectable bar with their finger or through some other predefined gesture).

[0247] In some implementations, if a user updates their TIR goal in one way (e.g., via selectable bar 9801, time entry field 9802, or percentage entry field 9803), the onboarding GUI 980 will be updated to reflect the updated TIR goal (e.g., 17 hours equals 70%) in both the time entry field 9802 and the percentage entry field 9803. In this way, the onboarding GUI 980 allows the user to visualize the new TIR goal based on both hours and percentage. In some implementations, the onboarding GUI 980 may also include an information section 9804 informing the user that selecting a TIR goal is not permanent and that the user can change the TIR goal at any time by accessing the settings. Furthermore, the information section 9804 may also inform the user that the TIR application will recommend new TIR goals based on the user's progress over time.

[0248] like Figure 9L As shown, the user can select the "back" button 9805 to return to the previous tutorial GUI. Furthermore, in some implementations, and as... Figure 9L As shown, after entering new TIR target settings, the user can click "Set Target" 9806 to save the TIR target. In some implementations, once the user clicks "Set Target" 9806, a confirmation in-application modal 981 (such as...) is displayed on the onboarding GUI 980. Figure 9M (best depicted in the text), thus confirming that the user's TIR target has been set. In some implementations, and as... Figure 9L As depicted, the in-application modal 981 includes a "Confirm" button 9807, which the user can select to confirm the message provided in the in-application modal 981.

[0249] Go to Figure 9NThe following describes a new user guide GUI 985. The new user guide GUI 985 includes information related to "insights" provided by the TIR application, which will be described in further detail below. Specifically, the new user guide GUI 985 may include an information section 9851 that informs the user that the TIR application can provide weekly insights about their progress. Furthermore, in some implementations, the information section 9851 also informs the user that they can choose to be notified of new insights in the TIR application's settings or by checking for updates in the "Insights" tab or icon. The new user guide GUI 985 may include a "back" button 9852 that, when selected by the user, returns the user to the previously displayed new user guide GUI. Additionally, the new user guide GUI 985 may also include a "next" button 9853 that, when selected by the user, displays the next new user guide GUI.

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

[0251] In some implementations, the onboarding GUI 990 includes a "Next" button or a "Continue" button 9902, which, if selected for the first time by the user, displays an onboarding GUI 995 that allows the user to connect to a third-party health monitoring application. Specifically, and as... Figure 9PThe diagram depicts a beginner's onboarding GUI 995, which may include a movement setting 9951, configurable by the user, allowing a third-party health monitoring application to share movement-related data (e.g., steps or pushes) with the TIR application when enabled. In this way, the TIR application is configured to read movement-related data from the third-party health monitoring application to better understand its impact on the user's glucose levels. The beginner's onboarding GUI 995 may also include a sleep setting 9952, configurable by the user, allowing a third-party health monitoring application to share sleep-related data (e.g., sleep hours) with the TIR application when enabled. In this respect, the TIR application is configured to receive sleep-related data from the third-party health monitoring application to better understand its impact on the user's glucose levels. Furthermore, the beginner's onboarding GUI 995 may include a selectable "On All" button 9953, which, when selected by the user, allows the TIR application to access health data related to both the user's movement and sleep from the third-party health monitoring application. The onboarding GUI 995 may also include an information message 9954 informing the user that the TIR application will read data from a third-party health monitoring application to help the user understand the impact of movement and sleep factors on the user's glucose levels. According to another embodiment, the onboarding GUI 995 may also include an "Allow" button 9955, which outputs an option when selected by the user. Figure 9H The beginner's guide GUI 965 is depicted in the figure. In some embodiments, the beginner's guide GUI 995 may also include a "disallow" button 9956.

[0252] Furthermore, according to another aspect of the implementation, if the user selects the "Next" button or the "Continue" button 9902 of the onboarding GUI 995 a second time or at a subsequent time after the initial selection, a notification modal will be displayed informing the user that in order for the TIR application to access the third-party health monitoring application, the user must go to the settings of the third-party health monitoring application (e.g., Apple Health or Health Connect settings) under the "Sharing" tab. In some implementations, the notification modal includes an "OK" button that the user can select to confirm the notification. In some implementations, an onboarding modal (not shown) may be displayed that informs the user that the TIR application requires access to a third-party health monitoring application (e.g., Health Connect or Apple Health). Specifically, the onboarding modal may include (1) an selectable installation link and / or (2) a continue link that, when selected, allows the user to continue using the TIR application without connecting to the third-party health monitoring application.

[0253] In some example implementations, users can create a profile setup through a onboarding process. For example, in some implementations, and referring to… Figures 9Q-1 to 9Q-4 It can output a beginner's guide GUI 9100, which can include multiple selectable options or fields to prompt the user with profile information or preferences. For example, and as... Figures 9Q-1 to 9Q-4 The multiple selectable fields depicted may include: an age field 9101, where the user can enter an age range; a medical condition field 9102, where the user can enter whether they have been diagnosed with a medical condition (e.g., type 1 diabetes, type 2 diabetes, or other conditions); a diagnosis field 9103, where the user can enter the date they were diagnosed with the medical condition; a medication field 9104, where the user can confirm how they manage their medical condition (e.g., whether they are taking diabetes-related medications, such as long-acting / basal insulin or oral medications, or whether they are managing it through diet, exercise, or using an insulin pump, or choose not to answer); and a medication history field 9105, where the user can enter the date (if any) when they checked their glucose levels using a continuous glucose monitoring device. In some embodiments, although not illustrated, the medication history field 9105 may be used to enter the number of diabetes-related medications the user is taking.

[0254] According to some implementations, the beginner's guide GUI 9100 includes a collapsed view (best shown in...). Figure 9Q-1 and Figure 9Q-2 (in the middle) and expanded view (best shown in) Figure 9Q-3 (in the middle). For example, in the expanded view, and as... Figure 9Q-3As depicted, the age field 9101 includes multiple selectable age range options (e.g., "18 to 20", "21 to 34", "35 to 44", "45 to 54", "55 to 64", "65 to 70", "71 years or older", and in some embodiments, also includes an "unwilling to answer" option). In the collapsed view, and as... Figure 9Q-1 As shown, the selected age range option is displayed on the age field 9101 (e.g., "35 to 44"). Additionally, in the expanded view, and as... Figure 9Q-3 As shown, the medical condition field 9102 includes several selectable medical condition options (e.g., "Type 1", "Type 2", "Prediabetes", "Pregnancy", "I do not have diabetes", or "Unwilling to answer"). In the collapsed view, and as... Figure 9Q-1 As shown, the selected medical condition option is displayed on the medical condition field 9102 (e.g., "Type 2"). In some implementations, in the expanded view, and as... Figure 9Q-3 As shown, the diagnosis field 9103 includes several selectable time range options, corresponding to the time period when the user was diagnosed with a medical condition (e.g., "less than a year ago", "1 to 5 years ago", "6 to 10 years ago", "11 to 15 years ago", "16 to 20 years ago", "more than 20 years ago", and "I don't know / don't want to answer"). In the collapsed view, and as... Figure 9Q-1 The selected time range option, as depicted in the diagram, is displayed on diagnostic field 9103.

[0255] According to some implementations, in the collapsed view of the beginner's guide GUI 9100, the beginner's guide GUI 9100 is divided into a first page and a second page (…). Figure 9Q-1 and Figure 9Q-2 For example, and as Figure 9Q-1 As depicted, on the first page of the beginner's guide GUI 9100 in collapsed view, only the first part of several selectable fields is displayed (e.g., age field 9101, medical condition field 9102, and diagnosis field 9103). The first page of the beginner's guide GUI 9100 may include a back button 9106 and a next button 9107, which, when selected by the user, outputs the second page of the beginner's guide GUI 9100 in collapsed view. Furthermore, and as... Figure 9Q-2 As depicted, on the second page of the new user guide GUI 9100 in the collapsed view, only the second portion of several selectable fields (e.g., drug field 9104 and drug history field 9105) is displayed. In some embodiments, the second page of the new user guide GUI 9100 in the expanded view includes a next button 9108 and a back button 9109, which, when selected, returns the user to the first page of the new user guide GUI 9100 in the collapsed view.

[0256] According to one aspect of the implementation, in the expanded view of the novice guide GUI 9100, and as... Figure 9Q-3 As depicted, the medication field 9104 includes multiple selectable medication options, whereby a user can select one or more medication options suitable for the user (e.g., "diet and exercise," "oral medication (tablets or pills)," "non-insulin injection," "long-acting or basal insulin," "short-acting or rapid-acting or bolus insulin," "insulin pump," and / or "I don't know / don't want to answer"). In some embodiments, in the expanded view of the onboarding GUI 9100, and as... Figure 9Q-3 As depicted, each drug option selected by the user includes a shaded or colored portion to indicate that the drug option has been selected. In the collapsed view of the beginner's guide GUI 9100, although not illustrated, one or more selected drug options are displayed in the drug field 9104, wherein one or more selected drug options include a shaded or colored portion when displayed in the collapsed view of the beginner's guide GUI 9100.

[0257] In addition, and refer to Figure 9Q-3 In the expanded view of the onboarding GUI 9100, the medication history field 9105 includes several selectable time range options (e.g., "less than a month ago," "1 to 6 months," "6 to 12 months," "1 to 2 years," "2 to 5 years," "more than 5 years," and "I don't know / I don't want to answer"), corresponding to the time period during which the user checked their glucose levels using a medical device (e.g., a continuous glucose monitoring device). In the collapsed view of the onboarding GUI 9100, and as... Figure 9Q-2 The selected time range option, which corresponds to the period of time the user uses the medical device, is shown in the drug history field 9105.

[0258] According to one aspect of the implementation, if the user has not yet created a profile, the new user guide GUI 9100 is displayed in a collapsed view, wherein the new user guide GUI 9100 can be divided between a first page and a second page of the collapsed view. Figures 9Q-1 to 9Q-2 However, in some implementations, when in a collapsed view, the drug field 9104 can display multiple selectable drug options. Figure 9Q-2 Furthermore, in some implementations, if the user is creating a profile or selecting from one or more inputs among multiple selectable fields, the onboarding GUI 9100 can expand to display a view ( Figure 9Q-3Furthermore, in some implementations, the onboarding GUI 9100 can collapse the view display when the user has successfully selected each of the multiple selectable fields, showing the user's selection for each of the multiple selectable fields. Additionally, in some implementations (although not illustrated), when the user has not yet selected a specific field from the multiple selectable fields, each of the specific multiple selectable fields includes a message indicating to the user that an option can be selected.

[0259] In some implementations, when the "I don't know / I don't want to answer" option is selected for one of a plurality of selectable fields, the other options for that specific selectable field are deselected, making "I don't know / I don't want to answer" the only selected option for that selectable field. According to another aspect of the implementation, when a user is editing a user profile and has selected a specific option for one of a plurality of selectable fields, a checkmark appears next to the selected option (e.g., if the user selects "6 to 10 years ago" as the time range corresponding to the period when the user was diagnosed with a medical condition, a checkmark appears next to the "6 to 10 years ago" option). Those skilled in the art will understand that other indicators can be used to indicate the selected option for a selectable field without departing from the scope of this disclosure.

[0260] Additionally, in some implementations (although not illustrated), a disclaimer modal may be provided on the onboarding GUI 9100, wherein the disclaimer modal includes a message conveyed to the user that the user should not make treatment decisions based on data displayed in the TIR application and that the user should always consult a healthcare provider before changing the user's management procedures.

[0261] Figure 9Q-4 A block diagram of an example implementation of a user guide GUI 9100 is shown, in which the user has made selections related to user profile settings. Specifically, the user guide GUI 9100 is displayed in a collapsed view, where the age field 9101, medication status field 9102, diagnosis field 9103, medication field 9104, and medication history field 9105 are all displayed on one page of the user guide GUI 9100. More specifically, when the user completes selections related to user profile settings, the user guide GUI 9100 is displayed, where the age field 9101, medication status field 9102, diagnosis field 9103, medication field 9104, and medication history field 9105 all display the corresponding selections in the corresponding fields. In some implementations, and as... Figure 9Q-4 As depicted, the options in the drug field 9104 are each displayed with a shaded or colored portion to indicate that a drug option has been selected.

[0262] Example implementation of the account and settings GUI

[0263] Figures 10A to 10M Block diagrams depicting example implementations of account and settings interfaces or their related features, any of which can be used in conjunction with the implementations described herein. References Figure 10A The diagram depicts a setup GUI 1000. The setup GUI 1000a includes (but is not limited to): a text greeting 1001, which includes a name entered by the user (e.g., “Hi, Samantha!”); a text description 1002, which indicates a start date associated with the user (e.g., “Starting January 3, 2022”), wherein the text description 1002 is displayed directly adjacent to the text greeting 1001 on its far side (e.g., below); an “Account” section 1003; a “Preferences” or “Settings” section 1004; a “Help” section 1005; and an “About” section 1006, which, when selected, outputs information related to the TIR application.

[0264] In some implementations, and as such Figure 10A As shown in the diagram, the selectable pencil icon 1007 is displayed adjacent to the text greeting 1001, which, when selected by the user, outputs a settings GUI 1010 including a name entry field 1011. Figure 10B Users can edit the name they previously entered and that is associated with their account credentials.

[0265] In some implementations, although Figure 10A Not illustrated, but the settings GUI 1000 may also include an "Activity" section (e.g., an "Apple Health" section or a "Health Connect" section), which, when selected, outputs an interface related to activity settings (see example...). Figure 10L and Figure 10M ).

[0266] Furthermore, in some implementations, although Figure 10A Not shown in the figure, but the GUI 1000 settings may also include a notification section that outputs an interface related to notifications and reminders when selected.

[0267] Setting up GUI 1010 ( Figure 10B It also includes a "Save" button 1012, which users can press to save the name entered in the name entry field 1011.

[0268] Figure 10C-1 This is an example implementation of the account settings interface. Figure 10C-1 The document describes an account settings GUI 1020. According to one aspect of the implementation, when a user accesses, for example, the previous settings GUI 1000 (… Figure 10A When the "Account" section 1003 is selected, the account settings GUI 1020 can be displayed. According to another aspect of the implementation, and as... Figure 10C-1 As depicted, the GUI 1020 settings may include a target glucose range setting 1021 and a measurement unit setting 1023. In some embodiments, although not illustrated, the target glucose range setting 1021 may be used to allow the user to configure the target glucose range. In some embodiments, and as shown... Figure 10C-1 As depicted, the target glucose range setting 1021 may be non-configurable and displayed only for informational purposes (e.g., informing the user that the target glucose range is between 70 mg / dL and 180 mg / dL). For example, when the user selects the target glucose range setting 1021 in the setting GUI 1020, the setting GUI 1030 is output (…). Figure 10D The output settings GUI includes information related to the user's target glucose range. Other combinations of configurable and non-configurable settings are possible, and those skilled in the art will recognize that such combinations are entirely within the scope of this disclosure.

[0269] like Figure 10C-1As shown, in some embodiments, the account settings GUI 1020 also includes configurable TIR target settings 1022. Furthermore, in some embodiments, although not shown, the account settings GUI 1020 may also include a selectable "Send Research Data" option, which, when selected by the user, outputs the "Send Research Data" GUI. The Send Research Data GUI includes an information section informing the user that information from their account will be sent to the research team via email to help improve their TIR application experience. The information section of the Send Research Data GUI also provides details about the information or data that will be sent to the research team and ensures that the user does not share any personally identifiable information (“PII”). Additionally, the Send Research Data GUI may include an export information section indicating the date the user last exported and sent research data to the research team. According to one aspect of the embodiment, the Send Research Data GUI may include a "Send" button 126, which, when selected by the user, outputs a research confirmation modal. Specifically, the research confirmation modal is configured to partially obscure or cover the underlying interface (e.g., the Send Research Data GUI). In some implementations, the research confirmation modality requests confirmation that the user wishes to send their data (e.g., the user's dietary and glucose data) to the research team. In some implementations, the research confirmation modality may include a "Send" button that, when selected by the user, sends the user's data (e.g., the user's dietary and glucose data) to the research team. The research confirmation modality may also include a "Cancel" button that, when selected by the user, cancels the request to send the user's data to the research team.

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

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

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

[0273] Still referencing Figures 10E-1 to 10E-3 In some embodiments, the setup GUI 1040 also includes an information section 1044 that informs the user of TIR goals recommended by the American Diabetes Association. Furthermore, in some embodiments, the setup GUI 1040 allows the user to select specific progress indicators for TIR goals. For example, and as... Figure 10E-1 In the best-illustrated implementation, the user can choose to view TIR target progress in hours or as a percentage. In other implementations (not illustrated), the target progress view is not configurable. For example, in some implementations, the user can only view TIR target progress in hours.

[0274] like Figure 10E-1 As shown, after entering new TIR target settings, the user can click "Save" 1045 to update the information. In some implementations, after the user clicks "Save" 1045, and as... Figure 10E-3 As best depicted, the in-application modal 1046 is displayed on the settings GUI 1040, allowing the user to confirm the TIR target change. In some implementations, and as... Figure 10E-3 As depicted, the in-application modal 1046 includes a message instructing the user that the TIR target change will take effect the following day.

[0275] also, Figure 10F This is a setup GUI 1050 that depicts an interface related to the measurement unit. According to one aspect of the embodiment, the setup GUI 1050 can be displayed when the user selects the measurement unit portion 1023 in the previous setup GUI 1020 (FIG. 10C). In some embodiments, although not illustrated, the measurement unit is configurable (e.g., mg / dL or mmol / L). In some embodiments, and as... Figure 10FThe units of measurement described herein are not configurable and are displayed in units determined by a third party's region or country (e.g., mg / dL for the United States). Figure 10F As shown, the setup GUI 1050 includes an information message 1051 indicating that the glucose measurement units are automatically set based on the user's country. In some embodiments, the setup GUI 1050 also includes a guidance message 1052 instructing the user to change the measurement units via another analyte monitoring application (e.g., "Libre 2").

[0276] Figure 10G This is an in-application modal notification 1055 that provides information about exiting the TIR application. According to one aspect of the implementation, the in-application modal notification 1055 can be displayed when the user selects the "Check Out" option 1024 in the previous settings GUI 1020 (FIG. 10C). According to another aspect of the implementation, the in-application modal notification GUI 1020 can be configured to partially obscure or overlay the underlying interface (e.g., settings GUI 1000) to make it invisible.

[0277] also, Figure 10H-1 This is a settings GUI 1060a that depicts a settings preference interface including multiple notification options for a TIR application, in which a user can turn one or more notifications on and / or off. According to one aspect of the implementation, when, for example, the user selects a previous account settings GUI 1000 (… Figure 10A When the "Preferences" section 1004 in the configuration file is accessed, the settings GUI 1060a can be displayed. According to another aspect of the implementation, and as... Figure 10H-1 As best illustrated, the settings GUI 1060a may include (but is not limited to) one or more of the following: a text label and description of a “TIR Challenge” notification adjacent to a toggle control 1061 configured to switch between on and off positions; a text label and description of a “Record Meal Reminder” notification adjacent to a toggle control 1062 configured to switch between on and off positions; and a text label and description of a “Scan Sensor Reminder” notification adjacent to a toggle control 1063 configured to switch between on and off positions. In some embodiments, a notification reminding the user to scan their sensor may be provided after seven hours without scanning. Those skilled in the art will understand that, instead of toggling, the settings GUI 1060a may include any one or more of the following: an on / off checkbox, an on / off slider toggle control, an on / off radio button, an on / off button, etc.

[0278] According to one aspect of the implementation, if the "Record Meal Reminder" notification is enabled, the TIR application is configured to swipe the user after a predetermined period of time (e.g., every six hours) has elapsed if the user has not recorded meals after the first reminder. In some implementations, if the "Record Meal Reminder" notification is enabled, the TIR application is configured to swipe the user after a predetermined period of time (e.g., every four hours) has elapsed if the user has recorded meals after the first reminder.

[0279] Figure 10H-2 The settings GUI 1060a depicts all notifications being turned off. Additionally, as... Figure 10H-2 As depicted, the settings GUI 1060a includes an in-application modal 1065 that provides information on conditions for disabling notifications and a "Go to Settings" button that opens the corresponding settings interface to allow the user to enable notifications.

[0280] Figure 10H-3 Additional example implementations for setting up the GUI are described. Specifically, Figure 10H-3 A settings GUI 1060b is depicted, which is similar to settings GUI 1060a, but also includes a text label and description of a "New Insight" notification adjacent to a toggle control 1064 configured to switch between on and off positions. In some embodiments, settings GUI 1060b also includes a configurable home screen view setting 1066. According to one aspect of the embodiment, and as... Figure 10H-4 As described, a settings GUI 1069 can be output in response to a user selecting a home screen view setting 1066 in settings GUI 1060B. Specifically, through settings GUI 1069, the home screen view setting 1066 can be user-configurable, allowing the user to select between one or more home screen views 1068, for example, in home GUI 400 ( Figure 4B ), Homepage GUI450 ( Figure 4D ), Homepage GUI 430 ( Figures 4E-1 to 4E-7 ), Homepage GUI 485 ( Figures 4J-1 to 4J-3 ), Homepage GUI 495 ( Figures 4K-1 to 4K-3 ), or homepage GUI 499 ( Figures 4M-1 to 4M-6 The meal view 1068a in the logbook section of the website (e.g., a list of meal events), or the homepage GUI 400 ( Figure 4B ), Homepage GUI 450 ( Figure 4D ), Homepage GUI 430 ( Figures 4E-1 to 4E-7 ), Homepage GUI 485 ( Figures 4J-1 to 4J-3 ), Homepage GUI 495 ( Figures 4K-1 to 4K-3 ), or homepage GUI499 ( Figures 4M-1 to 4M-6 The time view of the day in the logbook section of the document 1068b (e.g., a time card of the day) or any interface described herein that can be configured as a home screen interface (e.g., a GUI 12100, such as...) Figures 12D-1 to 12D-2 As shown, or GUI 13100 (as shown in Figures 13C-1 to 13C-5), select between them. For example, in Figure 10H-4 In the middle, dietary view 1068a has been selected.

[0281] Figure 10H-5 The settings GUI 1060b depicts all notifications being turned off. Additionally, as... Figure 10H-5 As depicted, the settings GUI 1060b includes an in-application modal 1067 that provides information on conditions for disabling notifications and a "Go to Settings" button that opens the corresponding settings interface to allow the user to enable notifications.

[0282] Figure 10I An example implementation of the account interface is depicted. Figure 10I The document describes account GUI 1070, which allows users to select from previous account settings GUI 1000. Figure 10A The "Help" section 1005 is displayed in the system. According to some implementations, the account GUI 1070 includes (but is not limited to): a tutorial section 1071 and a "Contact Us" section 1072.

[0283] Figure 10J Account GUI 1180 is depicted, which includes contact information for help and feedback in the TIR application. When the user selects the previous account GUI 1070 ( Figure 10I When you access the "Contact Us" section (1072) in the system, you can display the account GUI (1180).

[0284] In some implementations, and in response to the user's input in the account GUI 1070 ( Figure 10I Selecting the TIR tutorial section 1071 in the ) outputs a settings interface including the following: (1) TIR tutorial option, which outputs a tutorial interface related to TIR when selected; (2) Small daily goals tutorial option, which outputs a tutorial interface related to small daily goals when selected; (3) Meal record tutorial option, which outputs a tutorial interface related to meal record when selected; (4) Impact score tutorial option, which outputs a tutorial interface related to impact score when selected; and (5) Weekly insight tutorial option, which outputs a tutorial interface related to weekly insight when selected.

[0285] In some implementations, and in response to the user's input in the account GUI 1070 ( Figure 10I Selecting the TIR tutorial section 1071 in the implementation allows the display of a tutorial interface related to the TIR application. For example, in some implementations, a tutorial interface may be displayed informing the user about studies that have shown TIR can be a simple and powerful way to track how food affects an individual's glucose levels. According to another aspect of the implementation, a tutorial interface may be displayed providing (1) user information about the TIR ring, specifically explaining that the TIR ring represents the user's progress toward their goal and will fill as the user spends more time within the target range, and (2) a message encouraging the user to close the TIR ring before midnight each day to reach their goal. In yet another aspect of the implementation, a tutorial interface may be displayed informing the user that TIR can vary from person to person and that the American Diabetes Association recommends approximately 17 hours of TIR per day.

[0286] In another aspect of the implementation, a tutorial interface may be displayed that (1) provides the user with a brief introduction on how to record meals in the TIR application, and (2) includes a link that, when selected by the user, outputs a meal recording information modality including prompts for adding meals through the TIR application. Furthermore, in some implementations, a tutorial interface is displayed that provides the user with information related to meal ratings or scores. For example, in some implementations, a tutorial interface may be displayed that (i) explains to the user that the TIR application rates meals based on changes in glucose after eating, and that a 5-star meal will cause the minimum increase in glucose, while a 1-star meal will cause the highest, and (2) includes a link that, when selected, outputs a meal rating information modality including information on how to rank or rate meals in the TIR application, as described above. In some implementations, the meal rating information modality, which includes information on how to rate meals, may also include emojis to indicate the effect on glucose. According to some aspects of the implementation, the dietary rating information modality may include a link that, when selected by the user, outputs another dietary rating information modality, which includes details about why scores are measured three hours after a meal is consumed. In some implementations, the dietary rating information modality including details about why scores are measured three hours after a meal is consumed may also include prompts that provide the user with advice on how to avoid exceeding the range over longer time periods. In some implementations, the dietary rating information modality also includes details about why users should allow time between meals. Furthermore, the dietary rating information modality includes details about recording all foods consumed within a 30-minute window under the same meal to minimize the number of meals for which scores or ratings are missed. Additionally, in some implementations, the dietary rating information modality includes details about scanning at least every eight hours to ensure the TIR application has the glucose data required to provide a dietary rating or score. Additionally, in some implementations, the dietary rating information modality informs the user that for an accurate dietary rating or score, the TIR application requires glucose readings from the user at the start of each meal and two hours thereafter, and that if the user misses a scan or there is a sensor problem, the TIR application may not be able to rate the user's meal.

[0287] In another aspect of the implementation, a tutorial interface may be displayed, which includes (1) details about why it is recommended to wait approximately three hours between meals to obtain an accurate glucose reading, and (2) details about recording all foods consumed within a 30-minute window under the same meal to minimize the number of meals receiving missed scores or ratings.

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

[0289] Figure 10K This is a block diagram depicting the account tutorial GUI 1080, when the user selects the previous account GUI 1070 ( Figure 10I In section 1071 of the tutorial, the account tutorial GUI can be displayed. For example... Figure 10K As described, the Account Tutorial GUI 1080 may include a TIR tutorial section 1081, a TIR Goals and Progress Loop tutorial section 1082, and a Dietary Influence Score tutorial section 1083.

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

[0291] In another aspect of the implementation, and in response to the user's input in the account tutorial GUI 1080 ( Figure 10K Selecting the TIR Goals and Progression Loop tutorial section 1082 can display a tutorial interface related to TIR goals and progress loops. For example, in some implementations, a tutorial interface may be displayed informing the user that the American Diabetes Association recommends a person's TIR should be approximately 17 hours per day. In another example implementation, a tutorial interface may be displayed informing the user that the TIR application calculates the user's current TIR and suggests an ideal first goal. In yet another example implementation, a tutorial interface may be displayed providing the user with information about the TIR loop, specifically explaining that the TIR loop represents the user's progress toward their goal and will fill with each hour spent within the goal range.

[0292] In another aspect of the implementation, and in response to the user's input in the account tutorial GUI 1080 ( Figure 10KSelecting section 1083 of the Dietary Influence Score tutorial can display a tutorial interface related to the Dietary Influence Score. In some implementations, for example, a tutorial interface can be displayed that explains to the user one of the purposes behind the scoring (e.g., the TIR application scores a user's diet so that the user can understand which foods are best used to keep the user within a range). In some example implementations, a tutorial interface can be displayed that explains to the user that the score is based on changes in the user's glucose levels over three hours after eating. In other example implementations, a tutorial interface can be displayed that provides the user with keys to different score options and what each score option represents regarding glucose changes.

[0293] According to another aspect of the implementation, the TIR application may also include an account interface related to general account and TIR application information. For example, an "About" interface may be provided, which offers general information related to the TIR application. Furthermore, in some implementations, the About interface may include a selectable trial disclaimer section, which, when selected by the user, outputs an account interface including a trial disclaimer and information related to the intended use of the TIR application. Specifically, the account interface with the trial disclaimer may also include an information section indicating the date the user signed the TIR application agreement (as in the previous onboarding GUI 925, such as...). Figure 9B (As seen in the video).

[0294] In addition, in some implementations, the interface may also include a selectable license section that, when selected by the user, outputs an interface containing information related to the licenses and notifications of the open-source software used in the TIR application.

[0295] In another aspect of the implementation, an interface including the terms of use for the TIR application can be output from the "About" interface. In some implementations, the interface including the terms of use is displayed when the user first installs and / or opens the TIR application. Furthermore, in some implementations, an interface including a privacy policy for the TIR application can be output from the "About" interface. In some implementations, the interface including the privacy policy is displayed when the user first installs and / or opens the TIR application.

[0296] Go to Figure 10L This describes an example implementation of the activity settings GUI 1085. According to one aspect of the implementation, when the user selects, as in reference settings GUI 1000 (… Figure 10AWhen the "Activity" section is described, the Activity Settings GUI1085 can be displayed. Specifically, if the user has not previously connected to a third-party health monitoring application (such as Apple Health or Health Connect) during the onboarding process or in their settings, the following will be displayed: Figure 10L The activity settings GUI 1085 is depicted in the diagram. More specifically, in some embodiments, the activity settings GUI 1085 includes an information section that informs the user that the TIR application reads the user's exercise and fitness data from a third-party health monitoring application and correlates it with the user's glucose readings to understand its impact on the user's glucose levels. In some embodiments, the information section also informs the user that preferences within the third-party health monitoring application can be customized by going to the "Share" tab or from within the third-party health monitoring application itself. Furthermore, in some embodiments, the activity settings GUI 1085 includes a "Connect" button 1086 that, when selected, allows the user to connect the TIR application to the third-party health monitoring application. In some embodiments, when the user selects the Connect button 1086, a confirmation modal is displayed on the activity settings GUI 1085, confirming to the user that the TIR application wishes to access the third-party health monitoring application. In some embodiments, the confirmation modal (although not illustrated) includes a selectable "OK" confirmation button.

[0297] Figure 10M Additional example implementations of the activity settings GUI are described. Specifically, Figure 10M The activity settings GUI 1090 is depicted, and when the user selects the reference settings GUI 1000 ( Figure 10A When the user is in the “Activity” section described in the description, the Activity Settings GUI is displayed. More specifically, Activity Settings GUI 1090 is displayed if the user is not previously connected to a third-party health monitoring application (such as Apple Health, Samsung Health, or Google Fit via Health Connect) during the onboarding process or in their settings. Even more specifically, Activity Settings GUI 1090 is similar to Activity Settings GUI 1085 (as described in the description). Figure 10L As shown in the image, except that it does not include a "connect" button.

[0298] Example implementation of data loss GUI and related features

[0299] Figures 11A to 11G These are block diagrams illustrating example implementations of a data loss interface or its related features, any of which can be used in conjunction with any implementation described herein.

[0300] refer to Figure 11AThis document depicts an example implementation of a block diagram of a GUI 11000 for a TIR application. The GUI 11000 is similar to the homepage GUI 400 (…). Figure 4B In addition to including notifications associated with one or more data loss conditions (e.g., "based on 12-hour glucose data"), in some implementations, and as... Figure 11A The notifications described herein, which are associated with one or more data loss conditions, can be presented as in-app notifications 11111 set on the TIR card 11112.

[0301] Figure 11B A block diagram depicts another example implementation of the GUI 11100 for a TIR application. GUI 11100 is similar to the homepage GUI 450 ( Figure 4D In addition to including notifications associated with one or more data loss conditions (e.g., "based on 12-hour glucose data"), in some implementations, and as... Figure 11B The notifications associated with one or more data loss conditions, as described in the diagram, can be presented as in-application notifications 11101 set on the analytics graphics card 11102.

[0302] In addition, Figure 11C In the example implementation depicted, GUI 11200 includes an in-application modal notification 11222 associated with a data loss condition. In some implementations, the in-application modal notification 11222 may include informational prompts addressing one or more data loss conditions. Furthermore, the in-application modal notification 11222 may be configured to partially obscure or overlay the underlying interface, making it invisible.

[0303] Figure 11D A block diagram depicts another example implementation of the GUI 11300 for a TIR application. GUI 11300 is similar to the homepage GUI 485 ( Figures 4J-1 to 4J-3 In addition to including notifications 11301 (e.g., "based on 12-hour glucose data") associated with one or more data loss conditions, in some implementations, and as... Figure 11D As depicted, a notification 11301 associated with one or more data loss conditions can be presented as an in-app notification 11301 set on a TIR card 11302 on a GUI 11300. In some embodiments, the in-app notification 11301 may be positioned directly adjacent to and below the daily TIR target 11302. In some embodiments, and as... Figure 11DAs best depicted, in-app notification 11301 can be set below daily TIR target 11302 and TIR ring 11304 which includes TIR value 11303.

[0304] Figure 11E A block diagram depicts another example implementation of the GUI 11400 for a TIR application. GUI 11400 is similar to the homepage GUI 485 ( Figures 4J-1 to 4J-3 In addition to including notification 11401 (e.g., "based on 12-hour glucose data") associated with one or more data loss conditions, in some implementations, and as... Figure 11E The notification 11401, which is associated with one or more data loss conditions, as depicted in the diagram, can be presented as an in-app banner set between the TIR card 11419 and the analysis graphics card 11411 of the GUI 11400.

[0305] Figure 11F A block diagram depicts another example implementation of the GUI 11500 for TIR applications. GUI 11500 is similar to the homepage GUI 485 (…). Figures 4J-1 to 4J-3 In addition to including notifications 11501 associated with one or more data loss conditions (e.g., "Based on 12-hour glucose data," "Incomplete glucose data," or "You have lost glucose data"), in some implementations, and as such... Figure 11F As depicted, a notification 11501 associated with one or more data loss conditions can be presented as an in-app banner positioned between the analytics graphics card 11511 and the logbook section 11518 of the GUI 11500. Specifically, the notification or in-app banner 11501 may be positioned directly adjacent to one or more selectable icons 11513 below it, and directly adjacent to a message 11514 indicating when the GUI 11500 was last updated above it. In some embodiments, the notification or in-app banner 11501 may include an information icon 11502 that outputs an information modality 11600 (such as...) when selected by the user. Figure 11G (As depicted in the text), this information modality provides further information about the data loss situation.

[0306] Specifically, such as Figure 11GAs shown, information modality 11600 can inform the user that the TIR application may not have an accurate picture of the user's analyte data (e.g., glucose data) for the day, possibly due to a missed sensor scan or a technical problem with the user's sensor. Furthermore, in some embodiments, information modality 11600 can provide the user with a reminder message reminding them that to avoid gaps in the analyte data (e.g., glucose data), the user should scan the sensor at least once every eight hours in the analyte monitoring application. Information modality 11600 may also include an selectable "OK" button.

[0307] Those skilled in the art will understand that the notification and data loss features described herein are intended for illustrative purposes only, and that any individual elements or combinations thereof depicted and / or described with respect to a particular embodiment or figure may be freely combined with any other elements or combinations thereof depicted and / or described with respect to any other embodiment.

[0308] Example implementation of in-app banner notifications

[0309] The TIR application may also include in-app banner notifications, any of which may be used in conjunction with the implementations described herein. In some implementations, the in-app banner notification may include information relating to one or more of the following: (1) meal records (e.g., “added meals” or “deleted meals”); (2) updated settings (e.g., “updated time range”); (3) scans (e.g., “successful scan”, “ready to scan”, “6 hours since last scan”, or “scan unsuccessful”); detected errors (e.g., prompting the user to try again later, or to check out and check in to continue); and (4) lack of internet connection (e.g., requiring the user to connect to the internet to obtain the latest TIR and glucose data).

[0310] Example implementation of activity cards and their related features

[0311] Figures 12A-1 to 12D-2 Block diagrams depict example implementations of an interface including activity cards or related features thereof, any of which can be used in conjunction with the implementations described herein.

[0312] Figures 12A-1 to 12A-4 A block diagram depicts another example implementation of the GUI 12000 for TIR applications. GUI 12000 is similar to the homepage GUI 485 (as shown in the image). Figures 4J-1 to 4J-3 (As depicted in the image), in addition to including a health section 1201 that may include one or more activity cards 1202, 1203 (e.g., mobile card 1202 and sleep card 1203). Specifically, when the user accesses, for example, the novice guide GUI 995 (in... Figure 9P As shown in the diagram, the health section 1201 can be displayed on the GUI 12000 when enabling third-party health monitoring applications (such as Apple Health, Samsung Health, or Google Fit, via Health Connect) to share data related to the user's movement, sleep, or both. For example, if the user allows a third-party health monitoring application to share only data related to the user's movement via, for example, the mobile settings 9951 in the beginner's guide GUI 995, then the GUI 12000 will display the health section 1201, including the mobile card 1202, as shown. Figure 12A-1 and Figure 12A-2 As depicted in the text. Specifically, Figure 12A-1 A mobile card 1202 is depicted, which displays the number of steps a user has taken (e.g., "24437 steps") within a predetermined time period (e.g., within a specific time period of day). In some embodiments, and as such... Figure 12A-2 As depicted, the mobile card 1202 displays the number of wheelchair pushes a user has received within a predetermined time period (e.g., within a specific time period of day) (e.g., "1437 pushes"). Figure 12A-2 As depicted in Figures 12-3, the health portion 1201, including the mobile card 1202, may be directly adjacent to and on the far side (e.g., below) of the logbook portion 1208 of the GUI 12000.

[0313] In some implementations, and as such Figure 12A-3 As best illustrated, if, through sleep settings 9952 of, for example, the novice GUI 995, the user allows a third-party health monitoring application to share only data related to the user's sleep, then the GUI 12000 will display a health section 1201 including a sleep card 1203, which shows the time the user has spent sleeping in a predetermined time period in the past (e.g., the previous night) (e.g., "17 hours and 31 minutes"). Furthermore, in some embodiments, and as shown in... Figure 12A-4As best depicted, if, through, for example, the Mobility Settings 9951 and Sleep Settings 9952 of the Beginner's Guide GUI 995, the user allows a third-party health monitoring application (e.g., Apple Health, Samsung Health, or Google Fit, via Health Connect) to share data related to both the user's mobility and sleep, then the GUI 12000 will display a Health section 1201 including a Mobility Card 1202 and a Sleep Card 1203. In some embodiments, the Mobility Card 1202 may be directly adjacent to the Sleep Card 1203. Furthermore, in some embodiments, the Health Report 1201 may be directly adjacent to and distal to the Logbook Report 1208 of the GUI 12000 (e.g., below it). Additionally, in some embodiments, and as... Figures 12A-1 to 12A-4 As shown, the health section 1201 also includes a message 1204 adjacent to and distal to the SIM card 1202 and / or the sleep card 1203 (e.g., below), wherein the message 1204 indicates when the data displayed in the health section 1201 was last updated. In some embodiments, the sleep card 1203 and the SIM card 1202 are configured to update each time the TIR application is opened.

[0314] According to another aspect of the implementation method, and as Figure 12B As best shown in the diagram, if in the initial setup or through the tutorial process (e.g., Tutorial GUI 995, as...) Figure 9P As shown in the diagram, if a user denies the TIR application access to and connection to a third-party health monitoring application (e.g., Apple Health, Samsung Health, or Google Fit via HealthConnect), the GUI 12000 can display a health section 1201 including a connection card 1205. Specifically, in some embodiments, the connection card 1205 may include a message instructing the user to gain insights into how movement and sleep affect the user's glucose levels by connecting to the third-party health monitoring application. Furthermore, in some embodiments, the connection card 1205 may include a selectable "Connect" button 1206, which, when selected, outputs a connection modal 1206 on the interface (e.g., GUI 12000). Figure 12C The modal includes a message instructing the user that the TIR application needs to install a third-party health monitoring application, and that the user can continue to use health data after the third-party health monitoring application is installed. In some implementations, and as... Figure 12C As shown, connection mode 1206 includes selectable mounting links 1207.

[0315] In some implementations, although not illustrated, users can install / download third-party health monitoring applications through third-party app stores on reader devices such as mobile communication devices or smartphones. Specifically, users can select an installation link corresponding to the third-party health monitoring application in the third-party app store. Subsequently, and after installation, users can choose to open the link, which allows them to open the downloaded third-party health monitoring application. Users can then browse the onboarding and setup interfaces within the third-party health monitoring application, which allow users to authorize the TIR application to access and select the data they wish the TIR application to read and / or write to the third-party health monitoring application. In some implementations, users can customize the data types that the third-party health monitoring application can read, such as data related to basal metabolic rate, blood glucose, blood pressure, body fat, distance, exercise, heart rate, and / or altitude. Users can also choose to allow the third-party health monitoring application to read all collected health data. Furthermore, in some implementations, users can customize the data types that the TIR application can access, such as sleep, step count, and / or push data. Specifically, users can customize whether the TIR application can access and read sleep, step count, and / or push data. Additionally, users can customize whether the TIR application has permission to access and write sleep, step count, and / or push data. In some implementations, the user can select the "Allow All" button, which allows the TIR application to read and write all sleep, step count, and / or push data provided by the underlying third-party health monitoring application. In some implementations, the third-party health monitoring application will output a connection interface to confirm to the user that the third-party health monitoring application has successfully granted the TIR application access permissions.

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

[0317] Specifically, Figure 12D-1 and Figure 12D-2A further example embodiment of the block diagram of GUI 12100 is shown, wherein GUI 12100 includes a health section 12101, which may include one or more activity cards 12102, 12103 (e.g., mobile card 12102 and / or sleep card 12103). More specifically, GUI 12100 may be configured as the home screen of a TIR application and may include: (1) an analyzer graphics card 12110; (2) the health section 12101; (3) a selectable home screen icon 12111, which outputs GUI 12100 when selected by the user; and (4) a selectable insight icon 12112, which outputs insight GUI 14000 or insight GUI 150000 (e.g., respectively) when selected by the user. Figures 14A-1 to 14A-4 as well as Figures 15A-1 to 15A-4 ), which will be described in more detail below; and / or (5) the “+” icon 12113, when selected by the user, the output of the meal record GUI 500 is configured to receive dietary information input by the user. Figure 5A In some implementations, and as in... Figure 12D-2 As depicted, GUI 12100 may also include a meal timeline 12114 containing one or more meal icons 12115, each of which corresponds to a meal event. In some embodiments, the meal timeline 12114 is displayed on GUI 12100 only when one or more meal events are detected. Furthermore, according to some embodiments (although not illustrated), when no analyte data or meal event is detected, GUI 12100 will display an analyte graph 12110 without an analyte trend line and without the meal timeline 12114.

[0318] Specifically, in some implementations, and referring to Figure 12D-2Each of one or more meal icons 12115 is positioned along the meal timeline 12114 to correspond to a time associated with a meal event (e.g., the detection time of the meal event or the input time associated with the occurrence time of the meal event). In some embodiments, the meal timeline 12114 may be displayed near, close to, and / or on the far side (e.g., below) of the analyte graphic 12116 on the analyte graphic card 12110, below the x-axis, and / or at the bottom of the graphics window. In some implementations, the GUI 12100 includes a target analyte range 12117 (e.g., "Target glucose range: 70 mg / dL to 180 mg / dL") and one or more selectable icons 12118 (e.g., radio buttons, checkboxes, sliders, toggle controls, etc.) that allow the user to select a predefined time period within which the user's analyte data will be displayed in the analyte graphics card 12110. Specifically, in some implementations, the meal timeline 12114 may be located distally (e.g., below) relative to the analyte graphics 12116 and between the x-axis and one or more selectable icons 12118. More specifically, the x-axis may include time units covering a 24-hour period (e.g., three-hour increments, etc.). In this way, the meal timeline 12114 can be configured so that the user can visually associate the post-meal analyte trajectory with the relevant meal events associated with each meal icon 12115 displayed on the meal timeline 12114.

[0319] Furthermore, in some embodiments, each meal icon 12115 may be a photograph or image associated with a specific meal. In some embodiments, the meal icon 12115 may include a placeholder image instead of a photograph or image selected by the user. According to one aspect of the embodiments, each meal icon 12115 along the meal timeline 12114 is selectable. Specifically, when a user selects a specific meal icon 12115, a meal review GUI corresponding to the selected meal icon 12115 is output (e.g., such as...). Figure 8A and Figures 8B to 8E The dietary review GUI 800 or dietary review GUI 8000 are shown respectively.

[0320] In some implementations, and as such Figure 12D-1 and Figure 12D-2 As illustrated in the diagram, the GUI 12100 also includes a message 12119 adjacent to the analyzer graphics card 12110, wherein the message 12119 indicates the time when the analyzer graphics card 12110 was last updated. Additionally, in some embodiments, and as shown in the diagram... Figure 12D-1 and Figure 12D-2As shown, the health section 12101 also includes a message 12104 adjacent to and distal to the mobile SIM card 12102 and / or the sleep SIM card 12103 (e.g., below), wherein the message 12104 indicates when the data displayed in the health section 12101 was last updated. In some embodiments, the sleep SIM card 12103 and the mobile SIM card 12102 are configured to update each time the TIR application is opened.

[0321] In some implementations, and as in Figure 12D-1 and Figure 12D-2 As best illustrated, GUI 12100 may also include a text description 12120 indicating the day of the week (e.g., "Today is June 28th"), wherein the text description 12120 may include the date adjacent to the toggle control 12121 configured to be toggled. In some embodiments, although not illustrated, GUI 12100 may be associated with a past day, wherein the text description 12120 includes the date associated with a past day (e.g., "Friday, February 11th"). In some embodiments, although not illustrated, when the user toggles down the toggle control 12121, GUI 12100 is configured to display multiple selectable rings, each ring corresponding to a different date in the past week (similar to...). Figure 6B-1 The GUI 12100 may display multiple (seven) rings (425) as depicted in the diagram. For example, when the toggle control 12121 is toggled downwards, the GUI 12100 may display multiple (seven) rings, one ring corresponding to each day of the week. In some embodiments, although not shown, when the user selects a specific ring from the multiple rings, the GUI 12100 may display data related to the date corresponding to the selected ring. In some embodiments, when the toggle control 12121 is toggled upwards, the multiple rings are no longer displayed. Furthermore, in some embodiments, although not shown, when the GUI 12100 is associated with a past day, the home GUI 12100 may also include a selectable "Go to Today" link, which, when selected, outputs GUI 12100 including data corresponding to that day.

[0322] Example implementation of dietary testing GUI, methods, and related features

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

[0324] According to one aspect of the implementation, method 13500 may utilize one or more parameters associated with an analyte level shift (e.g., a glucose level shift) when determining dietary detection. For example, a first parameter may include the minimum rate of change in the analyte level (e.g., a glucose level change) over time required to initiate a shift (“trigger shift change”). In some implementations, other parameters may be utilized to effectively detect dietary events or shifts, including but not limited to: (1) the duration of a threshold analyte level shift (e.g., the duration of a minimum or maximum analyte level shift); (2) the threshold change in the analyte level throughout the episode (e.g., the maximum or minimum change in the glucose level throughout the episode); (3) the highest and / or lowest threshold analyte level values ​​that meet the threshold (e.g., the maximum minimum glucose value, the minimum minimum glucose value, the minimum maximum glucose value, or the maximum maximum glucose value); and (4) the permissible threshold time window between analyte level readings (e.g., the maximum amount of time permissible between glucose level readings).

[0325] Those skilled in the art will understand that the parameters related to offset and effective detection of seizures can utilize a variety of different thresholds and numbers.

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

[0327] At 13502, after determining the start of the offset, the slope is calculated to determine the end of the offset. In some example implementations, the previous timestamp is determined as the end of the offset when the slope is less than the trigger offset change.

[0328] At 13503, and at the end of the determined offset, the “trigger window” is calculated as the time (e.g., in minutes) between the start and end of the offset. According to one aspect of the implementation, the change in total analyte level (e.g., change in total glucose level) is calculated as the difference in analyte level values ​​(e.g., difference in glucose level values) between the start and end of the offset.

[0329] At 13504, the minimum threshold analyte level required for effective attack detection is determined, wherein the minimum threshold analyte level is calculated as the minimum analyte value (e.g., glucose value) during the offset period.

[0330] At 13505, the highest threshold analyte level required for effective attack detection is determined, wherein the highest threshold analyte level is calculated as the maximum analyte value (e.g., glucose value) during the offset period.

[0331] At 13506, a threshold time window is determined between analyte level readings (e.g., glucose level readings), wherein the threshold time window is calculated as the time difference between intra-episode analyte level readings (e.g., glucose level readings).

[0332] In some example implementations, an event is determined to be valid if certain threshold conditions are met, including but not limited to the following: (1) the permissible threshold time window between analyte level readings is determined to be between the minimum and maximum analyte level offset durations; (2) the total analyte level change (e.g., total glucose level change) is determined to be between the maximum and minimum analyte level changes calculated throughout the episode; (3) the highest analyte level value of the offset threshold is between the minimum and maximum highest analyte level values; and (4) all threshold time windows are less than the maximum permissible time between analyte level readings for a valid episode. In this regard, if the episode is valid, the diet for that episode is detected.

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

[0334] In some implementations, when multiple meals are entered within a predetermined time period of the consumed meal (e.g., within one hour of the meal), these multiple meals are recorded as a single meal. In some implementations, for the purpose of scoring meal events, the multiple meals recorded as a single meal may include the timestamp of the earliest of the multiple entered meals. According to some implementations, the concatenation of meals does not extend to meals that have elapsed a predetermined time within the initial meal (e.g., one hour from the initial meal).

[0335] Go to Figure 13BThe flowchart depicts an example implementation of a method 13600 for determining a customized time window for a user's expected consumption of one or more meals based on historical data. For example, the customized time window can be determined by utilizing at least one or more of the following: historical analyte data and / or data related to historically consumed and / or recorded meals. In this regard, the diet monitoring application is configured to output notifications or reminders associated with the customized time window to the user to prompt them to record their meals.

[0336] like Figure 13B As shown at the top, method 13600 begins at 13601, where historical meal times are identified. Historical meal times, or meal times within a past time period, can be identified by analyzing meals previously recorded by the user on a diet monitoring application and / or by meals detected through algorithms that analyze analyte data (e.g., glucose data). Recorded meals can be dietary information received as input through a reader device. Any diet detection method described herein (e.g., method 13500, such as...) can be used. Figure 13A (As shown) Determine the historical meal times.

[0337] At point 13602, the average meal time is determined by analyzing the identified historical meal times. Point 13602 requires a predefined minimum number and a predefined maximum number of historical meal time instances to determine the average meal time. The predefined maximum number of historical meal time instances can be meal times associated with a predefined number of recent meals. Alternatively, the average meal time can be calculated using data corresponding to meal times associated with recent meals or predetermined elapsed time periods, where data associated with the most recent time period (e.g., the last few days) is given more weight.

[0338] At 13603, a customizable time window corresponding to the expected consumption of one or more meals by the user in a future time period is calculated (e.g., a customizable time window for the expected consumption of one or more meals by the user the following day). The customizable time window can be calculated as: (1) a time window calculated as a multi-hour range centered on the calculated average meal time; (2) a time window determined by using meal times associated with a predefined number of recent meals, which are within a predetermined multiple of the z-score of the average meal time; and (3) a time window determined by a machine learning-based model. For example, according to some embodiments, the machine learning-based model can be trained with certain datasets, including but not limited to: data indicating the user's glucose level obtained by the body unit of a continuous glucose monitoring system, meals recorded by the user on a dietary monitoring application, meals detected algorithmically by analysis of analyte data, population and demographic data related to the user, and other information sources. According to another aspect of some embodiments, the time window can be a predetermined period of time (e.g., 2 to 4 hours), or it can be determined based on statistical analysis (e.g., one hour if the user's meal times are consistent, and four hours if the user's meal times are inconsistent). In another approach, the time window for the same meal can be the same or different on different days of the week. For example, the lunch time window can be the same from Monday to Friday, but different on Saturday and / or Sunday. In other implementations, the time window can be associated with a geographical location.

[0339] At point 13604, and after calculating the expected customized time window for future time periods, the customized time window can be updated to include meal times for the current time period (e.g., the current day) as one of the meal times associated with a predefined number of recent meals. Point 13604 can be repeated with each newly recorded meal time instance associated with consumed meals to continuously update the customized time window. In this way, method 13600 is dynamic, allowing it to change the estimated customized time window based on the user's recent eating trends.

[0340] Furthermore, a customized time window can be used as a dietary reminder for the user. Specifically, after the entire customized time window has expired, the dietary monitoring application can output a reminder or notification on the GUI of the dietary monitoring application, wherein the reminder or notification is configured to instruct the user to eat the meal (e.g., when the current CGM data does not indicate that a meal has been eaten and / or the current CGM level is below a threshold) and / or to record the meal via input on a reader device (e.g., when the CGM data indicates that a meal has been eaten). According to one aspect of many embodiments, the dietary monitoring application can also be configured to output a reminder or notification after a meal has been detected, which can occur before the time window expires. Notifications associated with meals are described herein, for example, with reference to Figures 13C-1 to 13C-1. Figure 13E-1 as well as Figure 13E-4 As described below, however, those skilled in the art will understand that various other notices may be used with any interface implementation described herein without departing from the scope of this disclosure.

[0341] Figure 13C-1 and Figure 13C-2 These are block diagrams illustrating example implementations of dietary detection interfaces or their related features, any of which can be used in conjunction with the implementations described herein.

[0342] Refer to Figure 13C-1 and Figure 13C-2 An example implementation of the block diagram of the homepage GUI 485, wherein the homepage GUI 485 also includes one or more notifications 1301 (also referred to herein as in-app notifications 1301) associated with missed meal detection or episodes. In some implementations, and as shown in Figure 13C-1 and Figure 13C-2 As depicted, one or more notifications 1301 associated with missed dietary detection can be presented as in-application notifications 1301 positioned between the analyte graphics card 4811 and the logbook section 4808. Those skilled in the art will understand that, without departing from the scope of this disclosure, in-application notifications 1301 can be displayed in various other locations on the home GUI 485.

[0343] According to one aspect of the implementation, the in-application notification 1301 may prompt the user to record meals. In some implementations, and referring to Figures 13C-1 and... Figure 13C-2 Each of the in-app notifications 1301 includes a query 1302 asking the user whether they have eaten (e.g., “Have you eaten?”) and a message 1303 informing the user that their blood sugar rose around a specific time associated with a missed meal detection (e.g., “Your blood sugar rose around 10:34 am”). According to one aspect of the implementation, each of the in-app notifications 1301 may include a selectable “ignore” button 1304 and a selectable meal record button 1305. Specifically, when the user selects the ignore button 1304 on a particular in-app notification 1301, the in-app notification 1301 is removed from the display of the home GUI 485.

[0344] More specifically, in some implementations, if the user selects the meal record button 1305, the meal record GUI 500 is output. Figure 5A Furthermore, in some implementations, dietary input modality 520 may occur (e.g., Figure 5CAs shown in the diagram), the time field 527 is pre-populated with the date and time associated with a detected missed meal, which is associated with an in-app notification 1301 from which the meal record button 1305 was selected. In other embodiments, a meal input modality 520 may appear (e.g., Figure 5C As shown in the diagram, the user sets the date and time associated with the detected missed meal in the time field 527. In some implementations, after the user records a meal within a specific time period associated with the missed meal detection (e.g., by selecting the meal record button 1305 in the in-app notification 1301), the corresponding in-app notification 1301 is removed from the home GUI 485. Furthermore, the recorded meal will be displayed in the logbook section 4808 of the home GUI 485, for example, in the appropriate TOD card 4801 under the list 4822 of meal events 4829.

[0345] According to another aspect of the implementation method, and as Figure 13C-2 As best illustrated, one or more missed meal markers 1310 (such as one or more missed meal icons 1310) may be displayed near, close to, and / or on the side of the analyte trend line 4815, or along the x-axis, at the top or bottom of the graphics window 484. In some aspects of the implementation, each missed meal icon 1310 is positioned on the analyte graphics card 4811 to allow the user to visually associate the post-meal analyte trajectory with the associated missed meal and the specific time the missed meal was detected. In some implementations, the corresponding missed meal icon 1310 is removed from the analyte graphics card 4811 when the user selects the ignore button 1304 on a specific in-app notification 1301 associated with a detected missed meal. In some implementations, although not illustrated, when the user records a meal associated with a specific previously detected missed meal, the missed meal icon 1310 is replaced with a meal icon.

[0346] In some implementations, if the user ignores or cannot activate the in-app notification 1301, the in-app notification 1301 and the corresponding missing meal icon 1310 are removed from the home GUI 485 after a predetermined period of time (e.g., after 24 hours).

[0347] According to another aspect of the implementation, and as Figure 13C-2As best depicted, if two in-app notifications 1301 associated with a detected missed meal are displayed on the home GUI 485, the in-app notifications 1301 are oriented such that the first in-app notification 1301a is stacked or partially overlaid on the second in-app notification 1301b. In some implementations, the in-app notifications 1301 are stacked chronologically. For example, the most recent in-app notification 1301a is configured such that it stacks or partially overlays the previous or earlier in-app notification 1301b. In this way, the most recent in-app notification 1301 is more prominently displayed on the home GUI 485 compared to the previous in-app notification 1301 which is positioned below or partially below the most recent in-app notification 1301 in the stack of in-app notifications 1301. Furthermore, in some implementations, if two in-app notifications 1301 are displayed on the home GUI 485, each in-app notification 1301 includes a page number 1311 that indicates that the in-app notification 1301 is a particular in-app notification 1301 out of the total number of in-app notifications 1301 displayed on the home GUI 485 (e.g., “1 / 2” if there are a total of two in-app notifications 1301 and the most recent in-app notification 1301 is primarily displayed on the home GUI 485).

[0348] According to another aspect of the implementation method, and as Figure 13C-2 As best illustrated, if more than two in-app notifications 1301 associated with a detected missed meal are displayed on the home GUI 485, the in-app notifications 1301 are configured to stack or partially overlap each other. In some implementations, the in-app notifications 1301 are stacked chronologically. Furthermore, in some implementations, if more than two in-app notifications are displayed on the home GUI 485, each in-app notification 1301 includes a page number 1311 indicating that the in-app notification 1301 is a specific in-app notification 1301 out of the total number of in-app notifications 1301 displayed on the home GUI 485 (e.g., "1 / 10" if there are a total of ten in-app notifications 1301 and the most recent in-app notification 1301 is primarily displayed on the home GUI 485). Additionally, according to some implementations, once an in-app notification is removed from GUI 485 (e.g., by the user ignoring the in-app notification or recording a meal corresponding to a specific time associated with a missed meal detection), the page number is configured to update to reflect the new total number of in-app notifications (e.g., if the user selects the ignore button on one of ten in-app notifications, the page number on that in-app notification will be updated to reflect "1 / 9" instead of "1 / 10").

[0349] Furthermore, according to another aspect of the implementation, and in response to a tenth predetermined input from the user (such as when the user taps or swipes on a specific in-app notification 1301, selects the ignore button 1304, or performs some other predetermined gesture), the underlying in-app notification 1301 will be displayed on top of the stack of in-app notifications 1301. For example, if the user selects the ignore button 1304 on one of the three in-app notifications 1301, the second in-app notification 1301 will be primarily displayed on the home GUI 485. In some implementations, the second in-app notification 1301 of the three in-app notifications 1301 will further display page number 1311 indicating that it is a "2 / 3" in-app notification 1301. Furthermore, if the user selects the ignore button 1304 on the second in-app notification 1301, the third in-app notification 1301 will be primarily displayed on the home GUI 485. In some implementations, the third in-app notification 1301 of the three in-app notifications 1301 will further display page number 1311 indicating that it is a “3 / 3” in-app notification 1301.

[0350] In some implementations, the analyzer graphics card 4811 of the home GUI 485 is configured to be updated such that the missing meal icon 1310 corresponding to the primarily displayed in-app notification 1301 is displayed on the analyzer graphics card 4811. For example, if the user swipes from the first in-app notification 1301, causing the second in-app notification 1301 to be primarily displayed on the home GUI 485, the analyzer graphics card 4811 is configured to be updated such that the missing meal icon 1310 associated with the first in-app notification 1301 is removed from the analyzer graphics card 4811, and the missing meal icon 1310 associated with the second in-app notification 1301 is displayed on the analyzer graphics card 4811.

[0351] Although notification 1301 related to missed dietary detection has been described herein with reference to Homepage GUI 485, those skilled in the art will understand that notification 1301 and its associated features may be used in conjunction with Homepage GUI 400 without departing from the scope of this disclosure. Figure 4B ), Homepage GUI 450 ( Figure 4D ), Homepage GUI 430 ( Figures 4E-1 to 4E-7 ), Homepage GUI 485 ( Figures 4J-1 to 4J-3 ), Homepage GUI 495 ( Figures 4K-1 to 4K-3 ) and Homepage GUI 499 ( Figures 4M-1 to 4M-2 Use them together.

[0352] For example, Figure 13D-1 and Figure 13D-2This is a block diagram depicting the homepage GUI 499, which includes dietary detection features. Specifically, and referring to... Figure 13D-1 and Figure 13D-2 One or more notifications 1351 associated with missed meals may be presented as in-app notifications 1351 on a homepage GUI 499, wherein the homepage GUI 499 includes: an average meal rating card 4991, which includes an average meal rating 4920, a graphical indicator 4921 corresponding to the average meal rating 4920, and an average meal rating indicator 4923 visually illustrating the average meal rating provided over a predetermined time period; an analyte graphic card 4910, which includes an analyte graphic 49011, the analyte graphic including an analyte trend line 49015; and a logbook section 4998, which includes a list 4992 of meal events 4999. In some example embodiments, the in-app notification may be positioned between the analyte graphic card 4910 and the logbook section 4998 of the homepage GUI 499. Those skilled in the art will understand that the in-app notifications 1351 may be displayed in various other locations on the homepage GUI 499 without departing from the scope of this disclosure.

[0353] In some implementations, and still referencing Figure 13D-1 and Figure 13D-2 Each of the in-app notifications 1351 includes a query 1352 asking the user whether they have eaten (e.g., “Have you eaten?”) and a message 1353 informing the user that their blood sugar rose around a specific time associated with a missed meal detection (e.g., “Your blood sugar rose around 10:34 am”). According to one aspect of the implementation, each of the in-app notifications 1351 may include a selectable “ignore” button 1354 and a selectable meal record button 1355. Specifically, when the user selects the ignore button 1354 on a particular in-app notification 1351, the in-app notification 1351 is removed from the display of the home GUI 499.

[0354] According to one aspect of the implementation, if the user selects the meal record button 1355, the meal record GUI 500 is output. Figure 5A Furthermore, in some implementations, dietary input modality 520 may occur (e.g., Figure 5C As shown in the diagram), the time field 527 is pre-populated with the date and time associated with a detected missed meal, which is associated with an in-app notification 1351 from which the meal record button 1355 was selected. In other embodiments, a meal input modality 520 may appear (e.g., Figure 5CAs shown in the diagram, the user sets the date and time associated with the detected missed meal in the time field 527. In some implementations, once the user records a meal within a specific time period associated with the missed meal detection (e.g., by selecting the meal record button 1355 in the in-app notification 1351), the corresponding in-app notification 1351 is removed from the home GUI 499. Furthermore, the recorded meal will be displayed in the logbook section 4998 of the home GUI 499, for example, under the list 4992 of meal events 4999.

[0355] According to another aspect of the implementation method, and as Figure 13D-2 As best illustrated, one or more missed meal markers 1350 (such as one or more missed meal icons 1350) may be displayed near, close to, and / or on the side of the analyte trend line 49015, or along the x-axis, at the top or bottom of the graphics window 49904. In some aspects of the implementation, each missed meal icon 1350 is positioned on the analyte graphics card 49011 to allow the user to visually correlate the post-meal analyte trajectory with the associated missed meal and the specific time the missed meal was detected. In some implementations, the corresponding missed meal icon 1350 is removed from the analyte graphics card 49011 when the user selects the ignore button 1354 on a specific in-app notification 1351 associated with a detected missed meal. In some implementations, although not illustrated, the missed meal icon 1350 is replaced with a meal icon when the user records a meal associated with a specific previously detected missed meal.

[0356] In some implementations, if the user ignores or cannot activate the in-app notification 1351, the in-app notification 1351 and the corresponding missing meal icon 1350 are removed from the home GUI 499 after a predetermined period of time (e.g., after 24 hours).

[0357] According to another aspect of the implementation, and as Figure 13D-2As best depicted, if two in-app notifications 1351 associated with a detected missed meal are displayed on the homepage GUI 499, the in-app notifications 1351 are oriented such that the first in-app notification 1351a is stacked or partially overlaid on the second in-app notification 1351b. In some implementations, the in-app notifications 1351 are stacked chronologically. For example, the most recent in-app notification 1351a is configured such that it stacks or partially overlays the previous or earlier in-app notification 1351b. In this way, the most recent in-app notification 1351 is more prominently displayed on the homepage GUI 499 compared to the previous in-app notification 1351 which is positioned below or partially below the most recent in-app notification 1351 in the stack of in-app notifications 1351. Furthermore, in some implementations, if two in-app notifications 1351 are displayed on the home GUI 499, each in-app notification 1351 includes a page number 13511 that indicates that the in-app notification 1351 is a specific in-app notification 1351 out of the total number of in-app notifications 1351 displayed on the home GUI 499 (e.g., "1 / 2" if there are a total of two in-app notifications 1351 and the most recent in-app notification 1351 is primarily displayed on the home GUI 499).

[0358] According to another aspect of the implementation method, and as Figure 13D-2 As best illustrated, if more than two in-app notifications 1351 associated with a detected missed meal are displayed on the home GUI 499, the in-app notifications 1351 are configured to stack or partially overlap each other. In some implementations, the in-app notifications 1351 are stacked chronologically. Furthermore, in some implementations, if more than two in-app notifications are displayed on the home GUI 499, each in-app notification 1351 includes a page number 13511 indicating that the in-app notification 1351 is a specific in-app notification 1351 out of the total number of in-app notifications 1351 displayed on the home GUI 499 (e.g., "1 / 10" if there are a total of ten in-app notifications 1351 and the most recent in-app notification 1351 is primarily displayed on the home GUI 499). Additionally, according to some implementations, once an in-app notification is removed from GUI 499 (e.g., by the user ignoring the in-app notification or recording a meal corresponding to a specific time associated with a missed meal detection), the page number is configured to update to reflect the new total number of in-app notifications (e.g., if the user selects the ignore button on one of ten in-app notifications, the page number on the in-app notification will be updated to reflect "1 / 9" instead of "1 / 10").

[0359] Furthermore, according to another aspect of the implementation, and in response to an eleventh predetermined input from the user (such as when the user taps or swipes on a specific in-app notification 1351, selects the ignore button 1354, or performs some other predetermined gesture), the underlying in-app notification 1351 will be displayed on top of the stack of in-app notifications 1351. For example, if the user selects the ignore button 1354 on one of the three in-app notifications 1351, the second in-app notification 1351 will be primarily displayed on the home GUI 499. In some implementations, the second in-app notification 1351 of the three in-app notifications 1351 will further display a page number 13511 indicating that it is a "2 / 3" in-app notification 1351. Furthermore, if the user selects the ignore button 1354 on the second in-app notification 1351, the third in-app notification 1351 will be primarily displayed on the home GUI 499. In some implementations, the third in-app notification 1351 of the three in-app notifications 1351 will further display page number 13511 indicating that it is a “3 / 3” in-app notification 1351.

[0360] In some implementations, the analyzer graphics card 4910 of the home GUI 499 is configured to be updated such that the missing meal icon 1350 corresponding to the primarily displayed in-app notification 1351 is displayed on the analyzer graphics card 4910. For example, if the user swipes from the first in-app notification 1351, causing the second in-app notification 1351 to be primarily displayed on the home GUI 499, the analyzer graphics card 4910 is configured to be updated such that the missing meal icon 1350 associated with the first in-app notification 1351 is removed from the analyzer graphics card 4910, and the missing meal icon 1350 associated with the second in-app notification 1351 is displayed on the analyzer graphics card 4910.

[0361] Figures 13E-1 to 13E-5 This is a block diagram depicting another example implementation of an interface including dietary detection features, wherein any interface can be used in conjunction with the implementations described herein. Specifically, Figure 13E-1 A GUI 13100 for TIR applications is depicted. Specifically, the GUI 13100 can be configured as the main interface of a TIR application. More specifically, the GUI 13100 is similar to... Figure 12D-2 The GUI 12100 depicted in the image differs in that it also includes a dietary section 13101, which may include one or more notifications 13102 associated with missed meal detection or episodes. Figure 13E-1 Only one notification 13102 is depicted in the text. In some implementations, and as... Figure 13E-1As depicted, one or more notifications 13102 associated with missed dietary detection may be presented as in-app notifications 13102 positioned between the analyte graphics card 13103 and the health section 13104. Those skilled in the art will understand that the in-app notifications 13102 may be displayed in various other locations on the GUI 13100 without departing from the scope of this disclosure. In some embodiments where the health section 13104 is not displayed in the GUI 13100 (although not illustrated), one or more notifications 13102 are displayed directly adjacent to the analyte graphics card 13103 and distal to it (e.g., below).

[0362] According to one aspect of the implementation, the in-application notification 13102 can prompt the user to record meals. In some implementations, and referring to... Figure 13E-1 Each of the in-app notifications 13102 includes a message indicating that a meal has been detected. Additionally, in some implementations, each of the in-app notifications 13102 may include a timestamp 13107 indicating the time associated with the detected meal (e.g., “9:00 AM”). Alternatively, in some example implementations, each of the in-app notifications 13102 may include a graphical representation 13113, such as a segmented bar 13113, representing a score associated with the detected meal. Specifically, the score can be represented by a segmented bar 13113 having three segments 13114, wherein: (1) the first segment 13114a may be red or orange and indicates the analyte score corresponding to a high glucose effect or response (e.g., an average glucose range exceeding 250 mg / dL); (2) the first segment 13114a and the second segment 13114b may be yellow and indicate the analyte score corresponding to a moderate glucose effect or response (e.g., an average glucose range between 181 mg / dL and 250 mg / dL, or not greater than 250 mg / dL and / or at least 181 mg / dL); or (3) the first segment 13114a, the second segment 13114b and the third segment 13114c may be green and indicate the analyte score corresponding to a low glucose effect or response (e.g., an average glucose range between 70 mg / dL and 180 mg / dL, or not greater than 180 mg / dL). Those skilled in the art will understand that various other graphic representations and colors, as well as color configurations, can be used with the graphic representations without departing from the scope of this disclosure.

[0363] According to one aspect of the implementation, each of the in-application notifications 13102 may include a selectable "ignore" button 13105 and a selectable meal record button 13106. Specifically, when a user selects the ignore button 13105 on a particular in-application notification 13102, the in-application notification 13102 is removed from the display of the GUI 13100. More specifically, in some implementations, if the user selects the meal record button 13106, the meal record GUI 500 is output. Figure 5A Furthermore, in some implementations, dietary input modality 520 may occur (e.g., Figure 5C As shown in the diagram), the time field 527 is pre-populated with the date and time associated with a detected missed meal, which is associated with an in-app notification 13102 from which the meal record button 13106 was selected. In other embodiments, a meal input modality 520 may appear (e.g., Figure 5C As shown in the diagram, the user sets the date and time associated with the detected missed meal in the time field 527. In some implementations, when the meal record GUI 500 is output via the user selecting the meal record button 13106 of the GUI 13100, the camera interface is not displayed to the user (e.g., Figures 5I to 5N Furthermore, in some implementations, after a user records a meal at a specific time associated with a dietary monitoring event, the corresponding in-app notification 13102 is replaced with a dietary event 13108 corresponding to the recorded meal (see, for example...). Figure 13E-2 ).

[0364] In some implementations, although not illustrated, an in-app banner can be displayed on GUI 13100 after the user successfully records a meal, indicating that a meal has been added. Additionally, the in-app banner may include a selectable "View Meal" link, which, when selected, outputs either a meal review GUI 800 or a meal review GUI 8000 corresponding to the newly recorded meal (respectively...). Figure 8A and Figures 8B to 8E Furthermore, in some embodiments (although not illustrated), and when a user edits a recorded meal entry, an in-app banner may be displayed on GUI 13100, indicating to the user that the meal has been updated. In some embodiments, when a meal is updated, the in-app banner (not illustrated) may also include a "View Meal" link, which, when selected, outputs either a meal review GUI 800 or a meal review GUI 8000 correspo...

Claims

1. A glucose monitoring system, comprising: The reader device includes: A wireless communication circuit is configured to receive data indicating glucose levels from a sensor control device; and One or more processors, coupled to a memory storing a dietary monitoring application, wherein the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to: The detection includes one or more episodes in the data indicating the glucose level, wherein the one or more episodes are associated with one or more meals consumed by the user, and wherein dietary information related to the one or more meals consumed and associated with the detected one or more episodes has not yet been received by the dietary monitoring application; and Output a homepage graphical user interface (GUI), which includes at least one of the following: A glucose graph card, comprising a glucose graph with a glucose trend line, the trend line reflecting the data indicating the glucose level; The dietary section is configured to display one or more notifications, wherein each of the one or more notifications corresponds to one of the one or more episodes; and The health section includes one or more activity cards, each of which is configured to display data related to the user's activities.

2. The glucose monitoring system according to claim 1, wherein, Each of the one or more notifications is positioned between the glucose graphic card and the health section on the homepage graphical user interface.

3. The glucose monitoring system according to claim 1, wherein, Each of the one or more notifications includes a message indicating that the outbreak has been detected.

4. The glucose monitoring system according to claim 1, wherein, Each of the one or more notifications includes a timestamp configured to indicate the time associated with one of the one or more attacks.

5. The glucose monitoring system according to claim 1, wherein, Each of the one or more notifications includes a graphical representation configured to represent a score associated with one of the one or more episodes.

6. The glucose monitoring system according to claim 5, wherein, The graphical representation includes segmented bars, wherein each segmented bar comprises a plurality of segment portions, and each of the plurality of segment portions is configured to correspond to the glucose effect based on the data indicating the glucose level.

7. The glucose monitoring system according to claim 6, wherein, The plurality of segment portions include three segment portions, wherein a first segment of the three segment portions includes a first color and indicates a score corresponding to a high glucose effect based on the data indicating the glucose level, wherein a second segment of the three segment portions includes a second color and indicates a score corresponding to a moderate glucose effect based on the data indicating the glucose level, and wherein a third segment of the three segment portions includes a third color and indicates a score corresponding to a low glucose effect based on the data indicating the glucose level.

8. The glucose monitoring system according to claim 1, wherein, Each of the one or more notifications includes an optional ignore button and an optional meal record button.

9. The glucose monitoring system according to claim 8, wherein, The reader device also includes a touchscreen, and wherein, when the dietary monitoring application is executed by the one or more processors, the one or more processors further enable the one or more processors to: In response to the selection of the ignore button on one of the one or more notifications, one of the one or more notifications is removed from the homepage graphical user interface.

10. The glucose monitoring system according to claim 8, wherein, The reader device also includes a touchscreen, and wherein, when the dietary monitoring application is executed by the one or more processors, the one or more processors further enable the one or more processors to: In response to the selection of the meal record button, a meal record graphical user interface is output, the meal record graphical user interface being configured to receive input meal information, the meal information being associated with one of the one or more meals consumed in one of the one or more episodes associated with one of the one or more notifications.

11. The glucose monitoring system according to claim 10, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to the receipt of input dietary information by the dietary record graphical user interface, one of the one or more notifications is removed from the home graphical user interface, and a dietary event corresponding to the input dietary information is added to the home graphical user interface, wherein the dietary event is displayed in the dietary section.

12. The glucose monitoring system according to claim 10, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to the receipt of input dietary information by the dietary record graphical user interface, an in-app banner is displayed on the home graphical user interface, wherein the in-app banner includes a message indicating that dietary information has been received.

13. The glucose monitoring system according to claim 12, wherein, The in-app banner also includes selectable links that, when selected, output a graphical user interface for dietary reviews that includes information related to the dietary event.

14. The glucose monitoring system according to claim 1, wherein, The one or more activity cards include a first activity card and a second activity card, the first activity card containing data related to the user's movement during a predetermined time period, and the second activity card containing data related to the user's sleep during the predetermined time period.

15. The glucose monitoring system according to claim 14, wherein, Data related to the user's movement includes data related to the user's steps and / or wheelchair movement during the predetermined time period.

16. The glucose monitoring system according to claim 14, wherein, Data related to the user's sleep includes data related to the user's sleep time during the predetermined time period.

17. The glucose monitoring system according to claim 1, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to the detection of one or more seizures, a seizure marker associated with each of the detected seizures is displayed on the dietary timeline.

18. The glucose monitoring system according to claim 17, wherein, The glucose graphic card also includes an x-axis containing time units, wherein the dietary timeline is positioned below the x-axis.

19. The glucose monitoring system according to claim 18, wherein, The attack markers associated with each of the one or more detected attacks are set along the dietary timeline so that the user can visually associate the attack markers associated with each of the one or more detected attacks with corresponding data indicating glucose levels reflected on the glucose trendline.

20. The glucose monitoring system according to claim 17, wherein, The episode marker associated with each of the one or more detected episodes includes a missed meal icon.

21. The glucose monitoring system according to claim 17, wherein, Each of the one or more notifications includes a selectable ignore button and a selectable meal record button, wherein the reader device further includes a touchscreen, and wherein the meal monitoring application, when executed by the one or more processors, also enables the one or more processors to: In response to the selection of the diet record button, a diet record graphical user interface is output, the diet record graphical user interface being configured to receive input diet information, the diet information being associated with one of one or more diets consumed in each of the one or more detected episodes.

22. The glucose monitoring system according to claim 21, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to receiving input dietary information from the dietary record graphical user interface, the attack marker associated with each of the one or more detected attacks is removed from the dietary timeline, and the removed attack marker is replaced with a recorded dietary icon.

23. The glucose monitoring system according to claim 22, wherein, The recorded meal icons include photos or images associated with the entered meal information.

24. The glucose monitoring system according to claim 17, wherein, Each of the one or more notifications includes a selectable ignore button and a selectable meal record button, wherein the reader device further includes a touchscreen, and wherein the meal monitoring application, when executed by the one or more processors, also enables the one or more processors to: In response to the selection of the ignore button, the attack marker is removed from the dietary timeline.

25. The glucose monitoring system according to claim 1, wherein, The homepage graphical user interface also includes a text description indicating the current date of the week, wherein the text description includes the date adjacent to a toggle control configured to switch between a first position and a second position.

26. The glucose monitoring system according to claim 25, wherein, The homepage graphical user interface displays multiple selectable rings in response to the toggle control being switched to the first position, wherein each of the selectable rings corresponds to a different date in the past week.

27. The glucose monitoring system according to claim 26, wherein, The reader device also includes a touchscreen, and wherein, when the dietary monitoring application is executed by the one or more processors, the one or more processors further enable the one or more processors to: In response to the user selecting one of the plurality of selectable rings, data associated with different dates in the past week corresponding to the selected ring is displayed on the home graphical user interface.

28. The glucose monitoring system according to claim 1, wherein, The diet section is also configured to display one or more diet events, each of which corresponds to a diet recorded by the user, and wherein, when the diet monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: A score is determined for each of one or more dietary events and one or more episodes, wherein each determined score corresponds to a glucose response based on data indicating glucose levels associated with each of the one or more dietary events and one or more episodes.

29. The glucose monitoring system according to claim 28, wherein, The homepage graphical user interface also includes an average dietary score card, which is configured to reflect data related to the total average dietary score, wherein the total average dietary score is the sum of all determined scores for each of the one or more dietary events and the one or more episodes within a predetermined time period.

30. The glucose monitoring system according to claim 29, wherein, The scheduled time period is 24 hours.

31. The glucose monitoring system according to claim 29, wherein, The total average dietary score is configured to be updated continuously at a predetermined frequency to reflect the new total average dietary score.

32. The glucose monitoring system according to claim 29, wherein, The average dietary score includes messages, status indicators configured to provide a summary related to the total average dietary score, and / or a graphical representation corresponding to the total average dietary score.

33. The glucose monitoring system according to claim 32, wherein, The graphical representation includes a gradient scale containing gradients, where each part of the gradient corresponds to a different state of the total average dietary score.

34. The glucose monitoring system according to claim 33, wherein, The gradient includes a color gradient, wherein each color of the color gradient corresponds to the different states of the total average dietary score.

35. The glucose monitoring system according to claim 33, wherein, The total average dietary score can be a value between 1 and 100, wherein the gradient scale is configured to represent the range of total average dietary scores between 1 and 100.

36. The glucose monitoring system according to claim 34, wherein, The gradient scale includes a selector configured to align with the color of the gradient scale corresponding to the state of the total average dietary score.

37. The glucose monitoring system according to claim 26, wherein, The homepage graphical user interface also includes a selectable "Go to Today" link, and the reader device also includes a touchscreen, and the diet monitoring application, when executed by the one or more processors, further enables the one or more processors to: In response to the user selecting the Go to Today link, data associated with the different dates of the past week corresponding to the current date in the week is displayed on the homepage graphical user interface.

38. A glucose monitoring system, comprising: The reader device includes: The wireless communication circuit is configured to receive data indicating glucose levels from a sensor control device. An input device is configured to receive dietary information indicating one or more meals consumed by a user; and One or more processors, coupled to a memory storing a dietary monitoring application, wherein the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to: The detection includes one or more episodes of the data indicating the glucose level, wherein each of the one or more episodes is associated with dietary information, which is dietary information of one or more meals consumed by the user but not received by the input device; Determine a score for each of one or more dietary events and one or more detected episodes, wherein each of the one or more dietary events is configured to reflect dietary information received by the input device indicating one or more meals consumed by the user, and wherein the score corresponds to a glucose response based on data indicating glucose levels associated with each of the one or more dietary events and one or more detected episodes; and Output an insight graphical user interface (GUI), which includes at least one of the following: An average dietary score card is configured to reflect data related to a total average dietary score, wherein the total average dietary score is the sum of all determined scores for each of the one or more dietary events and the one or more episodes within a predetermined time period; and The dietary section includes a list configured to display the one or more dietary events and one or more notifications corresponding to the one or more events.

39. The glucose monitoring system according to claim 38, wherein, The scheduled time period is 24 hours.

40. The glucose monitoring system according to claim 38, wherein, The total average dietary score is configured to be updated continuously at a predetermined frequency to reflect the new total average dietary score.

41. The glucose monitoring system according to claim 38, wherein, The average dietary score includes a message, a status indicator configured to provide a summary related to the total average dietary score, and a graphical representation corresponding to the total average dietary score.

42. The glucose monitoring system according to claim 41, wherein, The graphical representation includes a gradient scale containing gradients, where each part of the gradient corresponds to a different state of the total average dietary score.

43. The glucose monitoring system according to claim 42, wherein, The gradient includes a color gradient, wherein each color of the color gradient corresponds to the different states of the total average dietary score.

44. The glucose monitoring system according to claim 42, wherein, The total average dietary score can be a value between 1 and 100, wherein the gradient scale is configured to represent a range of total average dietary scores between 1 and 100.

45. The glucose monitoring system according to claim 43, wherein, The gradient scale includes a selector configured to align with the color of the gradient scale corresponding to the state of the total average dietary score.

46. ​​The glucose monitoring system according to claim 38, wherein, Each of the one or more dietary events includes a textual description of the meal, a photograph associated with the meal, a timestamp associated with the meal, a portion size indicator associated with the meal, and / or a graphical representation configured to represent a determined score associated with one of the one or more dietary events.

47. The glucose monitoring system according to claim 46, wherein, The graphical representation includes a segmented bar, wherein the segmented bar comprises a plurality of segment portions, each of which is configured to correspond to the glucose response based on the data indicating the glucose level.

48. The glucose monitoring system according to claim 47, wherein, The plurality of segment portions include three segment portions, wherein a first segment of the three segment portions includes a first color and indicates a score corresponding to a high glucose response based on the data indicating the glucose level, wherein a second segment of the three segment portions includes a second color and indicates a score corresponding to a medium glucose response based on the data indicating the glucose level, and wherein a third segment of the three segment portions includes a third color and indicates a score corresponding to a low glucose response based on the data indicating the glucose level.

49. The glucose monitoring system according to claim 38, wherein, Each of the one or more notifications includes a message indicating that an outbreak has been detected.

50. The glucose monitoring system according to claim 38, wherein, Each of the one or more notifications includes a timestamp configured to indicate the time associated with a corresponding attack in one of the one or more attacks.

51. The glucose monitoring system according to claim 38, wherein, Each of the one or more notifications includes a graphical representation configured to represent a determined score associated with a corresponding episode in the one or more episodes.

52. The glucose monitoring system according to claim 51, wherein, The graphical representation includes segmented bars, wherein the segmented bars comprise multiple segment portions, each of which is configured to correspond to the glucose effect based on the data indicating the glucose level.

53. The glucose monitoring system according to claim 52, wherein, The plurality of segment portions include three segment portions, wherein a first segment of the three segment portions includes a first color and indicates a score corresponding to a high glucose response based on the data indicating the glucose level, wherein a second segment of the three segment portions includes a second color and indicates a score corresponding to a medium glucose response based on the data indicating the glucose level, and wherein a third segment of the three segment portions includes a third color and indicates a score corresponding to a low glucose response based on the data indicating the glucose level.

54. The glucose monitoring system according to claim 38, wherein, Each of the one or more notifications includes an optional ignore button and an optional meal record button.

55. The glucose monitoring system according to claim 54, wherein, The reader device also includes a touchscreen, and wherein, when the dietary monitoring application is executed by the one or more processors, the one or more processors further enable the one or more processors to: In response to the selection of the ignore button on one of the one or more notifications, remove one of the one or more notifications and the corresponding detected episode from the diet section.

56. The glucose monitoring system according to claim 55, wherein, The total average dietary score is configured to be updated in response to the removal of a detected episode from the one or more episodes.

57. The glucose monitoring system according to claim 54, wherein, The reader device also includes a touchscreen, and wherein, when the dietary monitoring application is executed by the one or more processors, the one or more processors further enable the one or more processors to: In response to the selection of the meal record button, a meal record graphical user interface is output, the meal record graphical user interface being configured to receive input meal information, the meal information being related to a meal associated with a meal corresponding to one of the one or more episodes of one of the one or more notifications.

58. The glucose monitoring system according to claim 57, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to the receipt of input dietary information by the dietary record graphical user interface, one of the one or more notifications is removed from the home graphical user interface, and the removed notification is replaced with a new dietary event, wherein the new dietary event is displayed in the dietary section.

59. The glucose monitoring system according to claim 57, wherein, When the dietary monitoring application is executed by the one or more processors, the one or more processors also cause the one or more processors to: In response to the receipt of input dietary information by the dietary record graphical user interface, an in-app banner is output on the insight graphical user interface, wherein the in-app banner includes a message indicating that dietary information has been received.

60. The glucose monitoring system according to claim 38, wherein, The dietary section is configured to display one or more dietary events and one or more notifications in chronological order.

61. The glucose monitoring system according to claim 38, wherein, The one or more detected episodes are automatically scored.

62. The glucose monitoring system according to claim 38, wherein, After the input device receives the dietary information corresponding to one of the one or more detected episodes, the one or more detected episodes are scored.

63. The glucose monitoring system according to claim 38, wherein, The scheduled time period is 24 hours.

64. The glucose monitoring system according to claim 38, wherein, The dietary section is configured to be continuously updated at a predetermined frequency to reflect one or more new dietary events and one or more new notifications within a subsequent predetermined time period.

65. The glucose monitoring system according to claim 38, wherein, The insight graphical user interface also includes selectable links to all diets, wherein the reader device also includes a touchscreen, and wherein the diet monitoring application, when executed by the one or more processors, further enables the one or more processors to: In response to the selection of all said dietary links, a dietary graphical user interface is output, the dietary graphical user interface including information related to all said one or more dietary events and one or more episodes corresponding to the predetermined time period.

66. A method comprising the following steps: One or more indicators are calculated as part of a total score, wherein the total score indicates the user's blood glucose control over a predetermined time period; Determine the raw score for each of one or more calculated indicators; The original scores of each of the one or more calculated indicators are normalized; The normalized raw scores of each of the one or more calculated metrics are weighted, wherein each weighted normalized raw score is assigned a sub-score; Calculate the total score within the predetermined time period based on the sub-scores; and At the end of the predetermined time, information related to the total score is output to the graphical user interface.

67. The method according to claim 66, wherein, The predetermined time period is one day, one week, or one month.

68. The method according to claim 66, wherein, The one or more indicators include data indicating glucose levels received from the sensor control device.

69. The method according to claim 66, wherein, The one or more indicators include dietary score indicators.

70. The method of claim 66, wherein, The one or more indicators include at least one or more of the amount of time the user wears the continuous glucose monitoring device and the amount of time the continuous glucose monitoring device is active.

71. The method according to claim 66, wherein, One or more of the indicators include blood glucose variability.

72. The method according to claim 66, wherein, The one or more indicators include the amount of time the user's glucose level is below a first predetermined threshold.

73. The method according to claim 72, wherein, The first predetermined threshold is 54 mg / dL or 70 mg / dL.

74. The method according to claim 66, wherein, The one or more indicators include the amount of time the user's glucose level is above a second predetermined threshold.

75. The method according to claim 74, wherein, The second predetermined threshold is 180 mg / dL or 250 mg / dL.

76. The method according to claim 66, wherein, The original score of each of the one or more calculated indicators is a predefined numerical score that is less than a predefined maximum score value.

77. The method of claim 66, wherein, Weighting the normalized raw scores of each of the one or more calculated metrics includes applying different weights to at least one or more calculated metrics.

78. The method according to claim 66, wherein, Calculating the total score within the predetermined time period includes summing the sums of the sub-scores.

79. The method according to claim 66, wherein, The total score is a numerical score for each day.

80. The method of claim 66, further comprising: The total score is updated at a predetermined frequency, wherein the updated total score is calculated within a subsequent predetermined time period.

81. A method comprising the following steps: The meal time in the past time period is identified by analyzing at least one or more of the meal information detected by the glucose data algorithm and the meal information received by the input device on the reader device. The average meal time is determined based on the identified meal times from the past time period. Calculate the expected customized time window corresponding to the time when the user expects to eat one or more meals in the future; and Update the expected customized time window with each new instance of recorded meal times.

82. The method according to claim 81, wherein, Determining the average meal time includes: a predefined minimum number of meal time instances from the past time period and a predefined maximum number of meal time instances from the past time period.

83. The method according to claim 81, wherein, Determining the average meal time includes using data corresponding to meal times associated with meals consumed within a predetermined elapsed time period.

84. The method according to claim 81, wherein, Calculating the expected customized time window includes: calculating the time window as a multi-hour range centered on the determined average meal time.

85. The method according to claim 81, wherein, Calculating the expected customized time window includes: calculating a time window determined by using meal times associated with a predefined amount of food consumed within a predetermined elapsed time period, wherein the meal times fall within a predetermined multiple of the z-score of the determined average meal times.

86. The method according to claim 81, wherein, Calculating the expected customized time window includes: calculating the time window determined by a machine learning-based model.

87. The method of claim 81, further comprising: During the expiration period of the customized time window, a notification related to the customized time window is output to the graphical user interface.

88. The method according to claim 87, wherein, The notification is configured to remind the user to eat or to record meals via input on the reader device.

89. A method comprising the following steps: Calculate the dietary offset for each meal consumed within a first pre-specified time period; Determine the average of the sum of the dietary offsets associated with each meal consumed within the first pre-specified time period; By comparing the average value associated with the first pre-specified time period with the average value associated with the second pre-specified time period, at least one or more high analyte level influence periods and one or more low analyte level influence periods within the first pre-specified time period are determined. Determine whether there is a threshold difference between the average value associated with the first pre-specified time period and the average value associated with the second pre-specified time period; as well as A graphical user interface ("GUI") is provided to a display device, the graphical user interface being configured to display information relating to at least one of the identified time periods of influence of one or more high analyte levels and the identified time periods of influence of one or more low analyte levels.

90. The method according to claim 89, wherein, The first pre-specified time period is configured as a moving time window.

91. The method according to claim 89, wherein, The first pre-specified time period is configured as one or more consecutive time blocks.

92. The method of claim 89, wherein calculating the dietary shift comprises: Calculate the difference between the highest glucose level experienced within a predetermined time period after a meal and the initial glucose level at or near the time of the meal.

93. The method according to claim 92, wherein, The predetermined time period is a two-hour or three-hour period.

94. The method of claim 89, wherein calculating the dietary shift comprises: When the rate of change in glucose exceeds a set threshold, the difference between the initial glucose level and the highest glucose level is calculated.

95. The method according to claim 94, wherein, The glucose change rate is the glucose increase rate.

96. The method of claim 89, wherein calculating the dietary shift comprises: When the rate of change in glucose changes, the increment between the initial glucose level and the highest glucose level is calculated.

97. The method of claim 89, wherein calculating the dietary shift comprises: Calculate the increment between the initial glucose level and the highest glucose level determined by a machine learning-based model.

98. The method according to claim 89, wherein, The average value of the sum of the dietary offsets associated with each diet consumed within the first pre-specified time period is determined at a predetermined frequency.

99. The method according to claim 98, wherein, The predetermined frequency is daily.

100. The method according to claim 89, wherein, The average value is the sum of the dietary shifts associated with each meal consumed within the first pre-specified time period, divided by the number of dietary shifts that occurred within the first pre-specified time period.

101. The method according to claim 89, wherein, The second pre-specified time period is a longer time period than the first pre-specified time period, wherein the first pre-specified time period is a period of one day.

102. The method according to claim 101, wherein, The second pre-specified time period is a one-week period.

103. The method according to claim 89, wherein, The second pre-specified time period is a longer time period than the first pre-specified time period.

104. The method according to claim 89, wherein, Determining whether there is a threshold difference between the average value associated with the first pre-specified time period and the average value associated with the second pre-specified time period includes: using a statistical z-score calculated within the first pre-specified time period.

105. The method according to claim 89, wherein, Determining whether there is a threshold difference between the average value associated with the first pre-specified time period and the average value associated with the second pre-specified time period includes using a statistical T-test.

106. The method according to claim 89, wherein, Determining whether there is a threshold difference between the average value associated with the first pre-specified time period and the average value associated with the second pre-specified time period includes using a machine learning-based model.

107. The method of claim 89, further comprising: When the threshold difference causes the average value within the first pre-specified time period to be greater than the average value within the second pre-specified time period, the first pre-specified time period is identified as the time period affected by the high analyte level.

108. The method of claim 89, further comprising: When the threshold difference causes the average value within the first pre-specified time period to be less than the average value within the second pre-specified time period, the first pre-specified time period is identified as the period of influence of the low analyte level.

109. The method according to claim 89, wherein, Information relating to at least one of the identified periods of influence of one or more high analyte levels and the identified periods of influence of one or more low analyte levels is configured to be displayed on the graphical user interface at the end of each week.

Images