Systems, devices and methods for monitoring diet-related analyte responses - Patents.com

Abstract

Systems, devices, and methods are provided for detecting, measuring, and classifying an individual's diet based on analyte measurements. Such results and related information can be presented to an individual to indicate which meals are causing the most severe analyte reactions. Such results can be organized and classified based on preselected criteria or previous meals and results, and can be organized and presented in a format relative to the monitored analyte, glucose. Various embodiments disclosed herein relate to methods, systems, and software applications designed to engage individuals by providing timely and direct feedback regarding analyte reactions associated with their diet.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Patent Application No. 63 / 452,263, filed March 15, 2023, and U.S. Patent Application No. 63 / 335,030, filed April 26, 2022, the entire disclosures of which are expressly incorporated by reference herein for any purpose. [Technical field]

[0002] The present subject matter relates generally to systems, devices, and methods for collecting information about an individual's analyte levels and information about the diet consumed by the individual, and further to processing, analyzing, presenting, or any combination of this information for the purpose of monitoring diet-related analyte responses and providing insights, actions, and recommendations to the individual. [Background technology]

[0003] The increase in the prevalence of type 2 diabetes and metabolic syndrome over the past few decades is believed to be due to changes in diet and activity levels. For example, the consumption of relatively readily available foods with a high glycemic index (GI) causes a rapid rise in blood glucose and insulin levels after meals, which is positively correlated with weight gain and obesity. Furthermore, follow-up studies have shown that weight gain and obesity may increase the risk of developing diseases such as type 2 diabetes and metabolic syndrome.

[0004] While most people understand the importance of diet in general terms, in practice many struggle to translate this vague awareness into concrete food choices. This problem exists primarily because people are unable to directly see the impact of their choices. This, in turn, can lead to misconceptions about portion sizes, misconceptions about which foods are relatively healthy, and a general lack of awareness about the duration and intensity of activity needed to stay healthy. Advertising, habits, peer pressure, food preferences, and general recommendations can also make this problem more difficult.

[0005] These problems can be addressed by analyte monitoring systems that track and better understand an individual's physiological response. Also, because elevated glucose levels are primarily caused by food ingestion, postprandial glucose levels can be related to the amount of carbohydrates and other dietary components consumed by an individual and the individual's physiological response to the meal. However, the analysis of such large amounts of incoming data has been problematic in that it is difficult to represent the data in a meaningful way that allows for effective action. Nevertheless, understanding data on food choices and subsequent challenges is necessary not only on an individual basis (by individuals, dietary managers, and health care professionals) but also on a clinical basis to understand and mitigate glucose fluctuations such as hyperglycemic episodes.

[0006] There have been previous efforts to implement software that tracks a user's food intake and correlates it with the user's analyte data, but these previous efforts have suffered from a number of deficiencies. For example, some systems require an individual to perform multiple, tedious and uncomfortable blood glucose measurements (e.g., finger-prick blood glucose tests). In addition, such solutions can have problems with insufficient data points to adequately determine the glycemic response to a meal. For example, individual blood glucose measurements may be performed before or after the user's glycemic response peaks, making it difficult to accurately capture the glycemic response and to meaningfully compare meals based on the glycemic response. Insufficient data points also make it difficult to automatically detect the occurrence of meal events from the user's analyte data. In other words, some previous systems are highly dependent on the user's manual logging of meals.

[0007] Additionally, some prior art systems attempt to detect meal events based simply on the presence or absence of an increase in glucose levels (e.g., Patent Document 1). However, such systems do not take into account the user's past meal history and may therefore count the number of meals the user has eaten more than they actually did, which is unsuitable. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] US Patent Application Publication No. 2003 / 0208113 Summary of the Invention [Problem to be solved by the invention]

[0009] Thus, there is a need for improved systems, devices and methods for collecting dietary information, assessing and detecting diet, and correlating with analyte levels. [Means for solving the problem]

[0010] Provided herein are exemplary embodiments of systems, devices, and methods for detecting, measuring, and classifying the diet of a human individual in relation to the individual's analyte measurements, whether such individual has or has been diagnosed with diabetes, is considered pre-diabetic, has metabolic syndrome, or has no diabetes, pre-diabetic, or metabolic syndrome symptoms. In other words, such an individual may be anyone who is motivated to improve their health by changing their diet and activity habits. Information obtained by the systems, devices, and methods according to exemplary embodiments of the present disclosure can be presented to the individual to reveal which meals, or aspects of their diet, are contributing most to the burden on the analyte levels.

[0011] According to a first aspect of the present disclosure, a system is provided for monitoring an analyte response associated with a user's diet. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of an analyte level of the user, and one or more processors coupled to a memory storing a dietary monitoring application. When the dietary monitoring application is executed by the one or more processors, the dietary monitoring application causes the one or more processors to output a first challenge graphical user interface (GUI) representing a list of one or more challenges related to the user's analyte response. The one or more challenges include one or more ongoing challenges, one or more completed challenges, and one or more unattempted challenges. The first challenge GUI includes a first challenge card, a second challenge card, and a third challenge card. The first challenge card represents one or more ongoing challenges, each of the one or more ongoing challenges representing a challenge currently being engaged by the user on the dietary monitoring application. The second challenge card represents one or more completed challenges, each of the one or more completed challenges representing a challenge completed by the user. The third challenge card represents one or more unattempted challenges, each of which represents a challenge that the user has not yet participated in.

[0012] The food monitoring application may store multiple challenges in a database. The challenges may be the same for all users or may be personalized based on data analyzed by the food monitoring application. Users may also be categorized based on common characteristics, demographics, location, behavior, or activity, and challenges may be output to these user categories. For example, a pizza challenge may be output to users that the food monitoring application determines to be pizza eaters (e.g., users who have eaten a threshold amount of pizza within a predefined time period). Challenges may be generated for users based on various criteria or behaviors. For example, challenges may be output to users based on a particular group of users or characteristics of the user identified by the food monitoring application, psychographic attributes, information the user has entered into the food monitoring application (e.g., entries the user has entered into a diary), timing of the user's food intake, demographics, geographic considerations (e.g., a particular location or region where an activity occurs), seasonal activity, etc. Additionally, the challenges may be generated and displayed on the food monitoring application in a predefined order or based on certain criteria or behaviors analyzed by the food monitoring application.

[0013] The data indicative of the user's analyte level may include the user's analyte response, the user's analyte response may include a meal-related analyte response, the user's analyte response may include the user's glucose level.

[0014] In some embodiments, the first challenge card of the system includes one or more selectable first challenge icons, each of which represents a challenge that the user is currently working on.

[0015] In some embodiments, each of the one or more selectable first challenge icons includes a first indicia and an image and a textual representation of the currently active challenge, the first indicia being displayed on the image and configured to indicate that the challenge is currently active, hi some embodiments, the first indicia is a small green circle.

[0016] In some embodiments, the second challenge card includes one or more selectable second challenge icons, each of the one or more selectable second challenge icons representing a challenge that the user has completed.

[0017] In some embodiments, each of the one or more selectable second challenge icons includes a second indicia and an image and a textual representation of the completed challenge, the second indicia being configured to be overlaid on the image to indicate that the challenge has been completed by the user, hi some embodiments, the second indicia is a colored check mark.

[0018] In some embodiments, the third challenge card includes one or more selectable third challenge icons, each of the one or more selectable third challenge icons representing a challenge that the user has not yet attempted. In some embodiments, each of the one or more selectable third challenge icons includes an image and a textual representation of the unattempted challenge.

[0019] In some embodiments, each of the first challenge card, the second challenge card, and the third challenge card includes a plurality of selectable challenge icons, and a first set of the plurality of selectable challenge icons is displayed on the first challenge GUI. The viewing device further includes a touch panel screen. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to receive an input corresponding to a swipe or drag operation from the touch panel screen, and display a second set of the plurality of selectable challenge icons on the first challenge GUI in response to the received input. At least one or more of the second set of the plurality of selectable challenge icons are different from at least one or more of the first set of the plurality of selectable challenge icons.

[0020] In some embodiments, the listing of one or more challenges includes one or more selectable challenge icons, each of the one or more selectable challenge icons corresponding to one of the one or more challenges related to the user's analyte response or glucose level. When executed by the one or more processors, the dietary monitoring application further causes the one or more processors to, in response to a selection of one of the one or more selectable challenge icons, outputting a second challenge GUI representing context information related to a challenge of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons.

[0021] The context information may be a separate screen that describes one of the one or more challenges that corresponds to a selected one of the one or more selectable challenge icons. The context information may provide information about each challenge. For example, if one of the one or more challenges that corresponds to a selected one of the one or more selectable challenge icons is about consuming vegetables and fruits, the context information may provide a description of the challenge as well as background information that supports the importance and relevance of consuming vegetables and fruits.

[0022] In some embodiments, the second challenge GUI includes a challenge summary section including a selected one of the one or more selectable challenge icons, an image, and a challenge name that is a textual representation of a challenge corresponding to the selected one of the one or more selectable challenge icons of the one or more challenges, an effort indicator configured to indicate when the user last attempted a challenge corresponding to the selected one of the one or more selectable challenge icons of the one or more challenges, and an achievement indicator configured to indicate when the user last successfully completed a challenge corresponding to the selected one of the one or more selectable challenge icons of the one or more challenges.

[0023] In some embodiments, when a challenge of the one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an unattempted challenge, the second challenge GUI further includes a start button. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to perform, in response to the start button being selected, starting an unattempted challenge in the meal monitoring application.

[0024] In some embodiments, when the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to the start button being selected, start an unattempted challenge in the meal monitoring application for the following day.

[0025] In some embodiments, when a challenge of the one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an ongoing challenge, the second challenge GUI further includes a stop button. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to perform, in response to the stop button being selected, stopping continuation of the ongoing challenge.

[0026] In some embodiments, if a challenge of the one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an ongoing challenge, the second challenge GUI further includes a progress card configured to show a progress of the ongoing challenge accumulated by the user, the progress card including a unit of measure and a unit of time indicating the progress. In some embodiments, the unit of measure includes a unit of minutes and the unit of time includes a number of days.

[0027] In some embodiments, if a challenge of the one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an ongoing challenge, a modal display is displayed over the second challenge GUI, and the modal display is configured to prompt the user to provide progress information regarding the ongoing challenge in the meal monitoring application.

[0028] In some embodiments, the meal monitoring application is configured to detect whether the user has successfully completed the ongoing challenge based on the tracked progress, and when executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to the meal monitoring application detecting that the user has successfully completed the ongoing challenge, output a third challenge GUI including a challenge summary section, an effort indicator, an achievement indicator, and a message congratulating the user on successfully completing the ongoing challenge, and in response to the meal monitoring application detecting that the user has successfully completed the ongoing challenge, qualifying the ongoing challenge as a completed challenge. The third challenge GUI further includes a first button, the first button configured to restart the completed challenge when the user selects the first button, and the third challenge GUI further includes a second button, the second button configured to, in response to the user selecting the second button, output the first challenge GUI and cause the user to select a different challenge from the list of one or more challenges represented by the first challenge GUI.

[0029] The meal monitoring application can be configured to automatically detect whether a user is on track to complete a challenge based on meal inputs or analyte level variability associated with the meal inputs. For example, the meal monitoring application can automatically detect when a user has consumed four consecutive "green load" (low glycemic response) meals.

[0030] In some embodiments, in response to a user selecting the first button, a modal display is displayed over the third challenge GUI, the modal display being configured to prompt the user to confirm whether the user wishes to start over on the completed challenge.

[0031] The modal display can include information about the challenge that has already been completed. The modal display can be a more powerful, visual, in-application modal display that provides more context that motivates the user to take immediate action. The modal display can present graphics and text that motivate the user to take a particular action. The modal display can also include suggested answers that allow the user to indicate if they would like to start the challenge over again.

[0032] In some embodiments, the meal monitoring application is configured to detect whether the user has been successful in completing the ongoing challenge based on the tracked progress, and when executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to the meal monitoring application detecting that the user has not been successful in completing the ongoing challenge, output a fourth challenge GUI including a challenge summary section, an effort indicator, an achievement indicator, and a message informing the user that the ongoing challenge has not been successful, and, in response to the meal monitoring application detecting that the ongoing challenge has not been successful, identify the ongoing challenge as a completed challenge. The fourth challenge GUI further includes a first button, the first button configured to restart the completed challenge from the beginning when the user selects the first button, and the fourth challenge GUI further includes a second button, the second button configured to, in response to the user selecting the second button, output the first challenge GUI and allow the user to select a different challenge from the list of one or more challenges represented by the first challenge GUI.

[0033] In some embodiments, in response to a user selecting the first button, a modal display is displayed over the fourth challenge GUI, the modal display being configured to prompt the user to confirm whether the user wishes to start over on the completed challenge.

[0034] In some embodiments, the meal monitoring application includes a home GUI that includes a challenge card, the challenge card including a selectable link, and when executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to a user selecting the link, output a first challenge GUI.

[0035] In some embodiments, each of the one or more challenges is configured to represent a challenge regarding a behavior or activity of the user that may affect the user's analyte level.

[0036] According to a second aspect of the present disclosure, a system for monitoring analyte responses associated with a user's diet is provided. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of a user's analyte levels, and one or more processors coupled to a memory storing a dietary monitoring application. When the dietary monitoring application is executed by the one or more processors, the dietary monitoring application causes the one or more processors to receive dietary information input by a user, the dietary information configured to represent the user's food choices, and output a home GUI. The home GUI includes a plurality of selectable sections, including a user profile section, a dietary input section, a trend section, a diary section, and a report section; a meal card configured to display one or more meal listings including the input dietary information for one or more meals consumed by the user; a trend card including a graphical representation representing information regarding the analyte responses associated with the user's food choices; a challenge card representing a list of one or more challenges related to the user's analyte responses or glucose levels; and a recommendation card representing one or more recommendations related to the user's food choices or analyte responses.

[0037] The food monitoring application may store multiple recommendations in a database. In addition, the food monitoring application may output recommendations from reliable sources. The stored recommendations may be the same for all users or may be personalized based on data analyzed by the food monitoring application. Users may also be classified based on common characteristics, demographics, location, behavior, or activity, and recommendations may be output for such user categories. Recommendations may be generated for a user based on various criteria and behaviors. For example, recommendations may be generated for a user based on a particular group or user characteristics of the user identified by the food monitoring application, psychographic attributes, information the user entered into the food monitoring application (e.g., entries the user entered into a diary), timing of the user's food intake, the amount of time the user used the food monitoring application or a particular sensor, demographics, geographic considerations (e.g., a particular location or region where the activity occurred), and seasonal activity. The order in which recommendations are generated and displayed on the food monitoring application may be a predefined order based on certain criteria or behaviors analyzed by the food monitoring application. The food monitoring application can analyze the data it receives and generate appropriate recommendations based on this. The recommendations can also become more personalized as a function of time. For example, after 30 days, a recommendation on how to remove the sensor can be output to the user. Also, the generated recommendations can be refined and updated as the amount of data the food monitoring application receives and analyzes increases.

[0038] The data indicative of the user's analyte level may include the user's analyte response, the user's analyte response may include a meal-related analyte response, the user's analyte response may include the user's glucose level.

[0039] In some embodiments, the recommendation card includes one or more selectable recommendation icons, each of the one or more selectable recommendation icons corresponding to one of the one or more recommendations.

[0040] In some embodiments, each of the one or more selectable recommendation icons includes an image for a corresponding one of the one or more recommendations and a recommendation name that is a text representation of the corresponding one of the one or more recommendations.

[0041] In some embodiments, the recommendation card includes a plurality of selectable recommendation icons, and a first set of the selectable recommendation icons are displayed on the recommendation card. The viewing device further includes a touch panel screen. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to receive an input in response to a swipe or drag operation from the touch panel screen, and display a second set of the selectable recommendation icons on the recommendation card in response to the received input. At least one or more of the second set of the selectable recommendation icons are different from at least one or more of the first set of the selectable recommendation icons.

[0042] In some embodiments, the recommendation card includes one or more selectable recommendation icons, each of the one or more selectable recommendation icons corresponding to one of the one or more recommendations. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to a selection of one of the one or more selectable recommendation icons, output a modal display on the home GUI. The modal display provides contextual information regarding the corresponding one of the one or more recommendations, and the modal display is configured to prompt the user to act on the corresponding one of the one or more recommendations.

[0043] In some embodiments, when the dietary monitoring application is executed by the one or more processors, the dietary monitoring application further causes the one or more processors to detect a user's food choices, analyze the entered dietary information, and display one or more selectable recommendation icons on the recommendation card based on the analysis, each of the one or more selectable recommendation icons representing a recommendation related to the user's food choices or test substance responses.

[0044] In some embodiments, the recommendation card includes one or more selectable recommendation icons, each of the one or more selectable recommendation icons corresponding to one of the one or more recommendations. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to a selection of one of the one or more selectable recommendation icons, delete the selected one of the one or more selectable recommendation icons from the recommendation card, and display a new selectable recommendation icon on the recommendation card in place of the deleted recommendation icon.

[0045] In some embodiments, the recommendation card includes one or more selectable recommendation icons, each of the one or more selectable recommendation icons corresponding to one of the one or more recommendations, and each of the one or more selectable recommendation icons is configured to be displayed on the recommendation card for a predetermined period of time.

[0046] In some embodiments, when the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to detect when a predetermined time period has been reached, and, in response to the predetermined time period being reached, replace one or more selectable recommendation icons on the recommendation card with a new set of one or more selectable recommendation icons, at least one of which is different from at least one of the one or more selectable recommendation icons that were replaced.

[0047] In some embodiments, the home GUI is configured to transition between a plurality of views, the plurality of views including at least a first view and a second view.

[0048] In some embodiments, in the first view, the home GUI is configured to display a user profile section, a meal entry section, a diary section, and a meal card. The viewing device further includes a touch panel screen. When the home GUI is in the first view, the meal monitoring application further causes the one or more processors to receive an input from the touch panel screen in response to a scroll operation, a swipe operation, a pull operation, or a drag operation when the meal monitoring application is executed by the one or more processors. The home GUI is configured to transition from the first view to a second view in response to the received input, and in the second view, a trend card, a challenge card, and a recommendation card are displayed on the home GUI.

[0049] In some embodiments, the home GUI is configured to transition between a plurality of views, each of the plurality of views being a different view, and the viewing device further includes a touch screen. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to receive input in response to a scroll, swipe, pull, or drag operation from the touch screen, and display one of the plurality of views of the home GUI in response to the received input.

[0050] In some embodiments, the meal card is configured to display one or more meal lists that include dietary information for one or more recently consumed meals.

[0051] In some embodiments, each entry in the one or more meal lists contains details of a meal eaten by the user, and the one or more meal lists are displayed on the meal card in chronological order, with the entry corresponding to the most recently eaten meal being displayed at the top of the meal card.

[0052] In some embodiments, each entry in the one or more meal listings includes details of a meal consumed by the user and the analyte responses associated with that meal.

[0053] In some embodiments, each entry in the one or more meal listings includes a textual description of the meal consumed by the user, a portion size indication indicating whether the meal was a small, medium, or large portion size relative to the user's usual meal sizes, a date stamp associated with the date the user consumed the meal, a time stamp associated with the time the meal was consumed, and a graphical representation indicating the test substance response associated with the meal.

[0054] In some embodiments, the graphical representation has multiple segments.

[0055] In some embodiments, the plurality of segments includes a first segment indicating a test substance response that includes a small glycemic response, a second segment indicating a test substance response that includes a medium glycemic response, and a third segment indicating a test substance response that includes a large glycemic response.

[0056] In some embodiments, the first segment, the second segment, and the third segment are each a different color.

[0057] In some embodiments, the trend card graphical representation depicts analyte responses associated with a user's food choices over a given time period.

[0058] In some embodiments, the graphical representation of the trend card includes a plurality of color segments including a first color segment, a second color segment, and a third color segment.

[0059] In some embodiments, the first color segment has a green color indicating a small glycemic response, the second color segment has a yellow color indicating a medium glycemic response, and the third color segment has an orange color indicating a large glycemic response.

[0060] In some embodiments, the trend card comprises a summary panel configured to provide an overall assessment of a user's food choices over a given time period.

[0061] In some embodiments, the trend card includes a summary panel including information indicative of analyte responses associated with the user's food selections, and the trend card is dynamically configured. When the dietary monitoring application is executed by the one or more processors, the dietary monitoring application further causes the one or more processors to detect whether new trend information is obtained from the analyte responses associated with the user's food selections, and if new trend information is detected, populating the trend card with an updated summary panel.

[0062] In some embodiments, if data indicative of test substance levels has not yet been received or if data indicative of test substance levels has not yet been associated with the entered meal information, then no trend card is displayed on the home GUI.

[0063] In some embodiments, the challenge card on the home GUI includes one or more selectable challenge icons, each of which is configured to represent a challenge related to the user's test substance response or glucose level.

[0064] In some embodiments, each of the one or more selectable challenge icons includes an image associated with the challenge represented by the selected challenge icon and a challenge name that is a text representation of the challenge represented by the selected challenge icon.

[0065] In some embodiments, an indicia indicating that a challenge is in progress is displayed on the image to indicate that the challenge depicted by the image is an active challenge on the meal monitoring application.

[0066] In some embodiments, the challenge card includes a selectable link, and when the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to, in response to a user selecting the link, output a first challenge GUI that includes information regarding all challenges provided by the meal monitoring application.

[0067] In some embodiments, the challenge card includes a plurality of selectable challenge icons, and a first set of the plurality of selectable challenge icons is displayed on the challenge card. The viewing device further includes a touch panel screen. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to receive input in response to a swipe or drag operation from the touch panel screen, and display a second set of the plurality of selectable challenge icons on the challenge card in response to the received input. At least one or more of the second set of the plurality of selectable challenge icons are different from at least one or more of the first set of the plurality of selectable challenge icons.

[0068] In some embodiments, the challenge card includes a plurality of selectable challenge icons, and the challenge card is configured to simultaneously display two or three of the plurality of selectable challenge icons on the home GUI.

[0069] In some embodiments, the recommendation card includes a plurality of selectable recommendation icons, and the recommendation card is configured to simultaneously display two or three of the plurality of selectable recommendation icons.

[0070] In some embodiments, the home GUI further includes a navigation bar.

[0071] In some embodiments, the home GUI further includes a banner containing messages regarding sensor scanning and meal loading.

[0072] According to a third aspect of the present disclosure, there is provided a system for monitoring an analyte response associated with a meal of a subject. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of a user's analyte level, and one or more processors coupled to a memory storing a meal monitoring application. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to perform the following steps for the received data indicative of the subject's analyte level: identifying a peak analyte level within a predetermined time period; identifying an estimated meal start time and an initial analyte level based on the peak analyte level; identifying a analyte level variation; prompting the subject to input meal information; and associating the input meal information with the analyte level variation.

[0073] In some embodiments the viewing device comprises a smartphone.

[0074] In some embodiments, the data indicative of the subject's analyte level includes data indicative of a glucose level.

[0075] In some embodiments, the system further comprises a trusted computer system, the trusted computer system being a cloud computing platform including one or more servers, In some embodiments, the trusted computer system is configured to transmit data indicative of the analyte level of the subject to the viewing device.

[0076] In some embodiments, the system further comprises a sensor control device, the sensor control device including an analyte sensor, at least a portion of the analyte sensor configured to be disposed beneath a skin layer of the subject and contact a bodily fluid of the subject, In some embodiments, the sensor control device is further configured to transmit data indicative of the analyte level of the subject to the viewing device.

[0077] In some embodiments, the wireless communication circuitry of the viewing device is configured to receive data indicative of the subject's analyte level according to a Bluetooth® or near-field wireless communication wireless protocol.

[0078] In some embodiments, the peak analyte level value comprises the highest glucose value above a predetermined analyte level threshold. In some embodiments, the predetermined analyte level threshold is 170 mg / dL. In some embodiments, the predetermined analyte level threshold is 180 mg / dL. In some embodiments, the predetermined analyte level threshold is 190 mg / dL.

[0079] In some embodiments, the predetermined time period of received data indicative of an analyte level for a subject comprises the most recent two hours of analyte data. In some embodiments, the predetermined time period of received data indicative of an analyte level for a subject comprises the most recent four hours of analyte data. In some embodiments, the predetermined time period of received data indicative of an analyte level for a subject comprises the most recent eight hours of analyte data.

[0080] In some embodiments, the estimated meal start time is determined by looking back two hours from the time of the peak analyte level. In some embodiments, the estimated meal start time is determined by looking back three hours from the time of the peak analyte level. In some embodiments, the estimated meal start time is determined by looking back four hours from the time of the peak analyte level.

[0081] In some embodiments, the analyte level fluctuation value is determined by subtracting the initial analyte level value from the peak analyte level value.

[0082] In some embodiments, when the dietary monitoring application is executed by the one or more processors, the dietary monitoring application further causes the one or more processors to associate the dietary information with the analyte level variation values ​​and store them in the memory of the viewing device.

[0083] According to a fourth aspect of the present disclosure, there is provided a system for monitoring an analyte response associated with a subject's diet. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of a user's analyte level, and one or more processors coupled to a memory storing a dietary monitoring application. When the dietary monitoring application is executed by the one or more processors, the dietary monitoring application causes the one or more processors to perform the following steps: receive dietary information input by the subject; receive data indicative of the subject's analyte level within a predetermined amount of time after the subject inputs the dietary information; identify a peak analyte level value in the received data indicative of the subject's analyte level; identify an initial analyte level value; identify a variance in the analyte level; and associate the input dietary information with the variance in the analyte level value.

[0084] In some embodiments the viewing device comprises a smartphone.

[0085] In some embodiments, the data indicative of the subject's analyte level includes data indicative of a glucose level.

[0086] In some embodiments, the system further comprises a trusted computer system, the trusted computer system being a cloud computing platform including one or more servers, In some embodiments, the trusted computer system is configured to transmit data indicative of the analyte level of the subject to the viewing device.

[0087] In some embodiments, the system further comprises a sensor control device including an analyte sensor, at least a portion of the analyte sensor configured to be disposed beneath a skin layer of the subject and contact a bodily fluid of the subject, In some embodiments, the sensor control device is further configured to transmit data indicative of the analyte level of the subject to the viewing device.

[0088] In some embodiments, the wireless communication circuitry of the viewing device is configured to receive data indicative of the subject's analyte level according to a "Bluetooth" or near-field wireless communication wireless protocol.

[0089] In some embodiments, the peak analyte level value comprises the highest glucose value above a predetermined analyte level threshold. In some embodiments, the predetermined analyte level threshold is 170 mg / dL. In some embodiments, the predetermined analyte level threshold is 180 mg / dL. In some embodiments, the predetermined analyte level threshold is 190 mg / dL.

[0090] In some embodiments, the analyte level fluctuation value is determined by subtracting the initial analyte level value from the peak analyte level value.

[0091] In some embodiments, when the dietary monitoring application is executed by the one or more processors, the dietary monitoring application further causes the one or more processors to associate the dietary information with the analyte level variation values ​​and store them in the memory of the viewing device.

[0092] In some embodiments, when the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to display a notification that a meal entry has not been made after a predetermined reminder period has elapsed.

[0093] In some embodiments, the predetermined reminder period is one week. In some embodiments, the predetermined reminder period is three days. In some embodiments, the predetermined reminder period is one day.

[0094] In some embodiments, the initial test substance level is determined based on the time of day of meal information entered by the subject.

[0095] According to a fifth aspect of the present disclosure, there is provided a system for monitoring an analyte response associated with a subject's meal. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of a user's analyte level, and one or more processors coupled to a memory storing a meal monitoring application. When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to perform a step of outputting a diary GUI. The diary GUI includes a plurality of meal entries, each meal entry of the plurality of meal entries including a date of the meal entry, a meal name, a graphical representation of an analyte level variation value associated with the meal entry, and a numerical representation of an analyte level variation value associated with the meal entry.

[0096] In some embodiments, the graphical representation of the analyte level variation value has multiple segments.

[0097] In some embodiments, the plurality of segments includes a first segment indicating that the analyte level fluctuation value was within a first analyte level fluctuation range, and a second segment indicating that the analyte level fluctuation value was within a second analyte level fluctuation range that is different from the first analyte level fluctuation range.

[0098] In some embodiments, the first segment is a different color than the second segment.

[0099] In some embodiments, the first segment is a different region than the second segment.

[0100] In some embodiments, the first analyte level range is less than 70 mg / dL.

[0101] In some embodiments, the second analyte level fluctuation range is 70 mg / dL to 120 mg / dL.

[0102] In some embodiments, the plurality of segments further includes a third segment indicating that the analyte level fluctuation value was within a third analyte level fluctuation range different from the first analyte level fluctuation range and the second analyte level fluctuation range.

[0103] In some embodiments, the third segment is a different color than the first and second segments.

[0104] In some embodiments, each meal entry of the plurality of meal entries further comprises a time of the meal entry.In some embodiments, each meal entry of the plurality of meal entries further comprises an activities section.In some embodiments, each meal entry of the plurality of meal entries further comprises a notes section.

[0105] In some embodiments, the diary GUI further comprises a view setting configured to display multiple meal entries by day or week.

[0106] In some embodiments, each meal input of the plurality of meal inputs further comprises a weighted average of the analyte level variation values. In some embodiments, the weighted average of the analyte level variation values ​​is based on a plurality of previous meal inputs having the same or similar meals or foods as each meal input. In some embodiments, the weighted average of the analyte level variation values ​​is determined by a weighted average function that includes a recency factor.

[0107] In some embodiments, the recency factor of the weighted average function is configured to reduce the analyte level variation value of a past dietary input by a predetermined factor per day for the number of days between the date of the past dietary input and the current date.

[0108] According to a sixth aspect of the present disclosure, there is provided a system for monitoring an analyte response associated with a subject's meal. The system includes a viewing device, the viewing device including a wireless communication circuit configured to receive data indicative of a user's analyte level, and one or more processors coupled to a memory storing a meal monitoring application. When the meal monitoring application is executed by the one or more processors, the meal monitoring application further causes the one or more processors to output a trend GUI. The trend GUI includes a glycemic response view and a meal view, the glycemic response view includes a graphical representation representing a plurality of segments including a first segment and a second segment. The first segment indicates a first analyte level variation range, and the second segment indicates a second analyte level variation range different from the first analyte level variation range.

[0109] In some embodiments, the first segment represents a first set of dietary inputs, and each dietary input in the first set has an analyte level variation value within a first analyte level variation range.

[0110] In some embodiments, the second segment represents a second set of dietary inputs, and the analyte level variation value for each dietary input of the second set is within a second analyte level variation range.

[0111] In some embodiments, the meal view includes a plurality of meal entries, each meal entry of the plurality of meal entries including a date and time of the meal entry, a meal name, a graphical representation of an analyte level variation value associated with the meal entry, and a numerical representation of an analyte level variation value associated with the meal entry.

[0112] According to a seventh aspect of the present disclosure, a method for monitoring an analyte response associated with a user's diet is provided. The method includes receiving data indicative of a user's analyte level via a wireless communication circuit, identifying the user's analyte response based on the data indicative of the analyte level, and outputting, by a processor coupled to a memory storing a dietary monitoring application, a first challenge GUI representing a list of one or more challenges related to the user's analyte response. The one or more challenges include one or more ongoing challenges, one or more completed challenges, and one or more unattempted challenges. The first challenge GUI includes a first challenge card, a second challenge card, and a third challenge card. The first challenge card represents one or more ongoing challenges, each of the one or more ongoing challenges representing a challenge currently being engaged in by the user on the dietary monitoring application. The second challenge card represents one or more completed challenges, each of the one or more completed challenges representing a challenge completed by the user. The third challenge card represents one or more unattempted challenges, each of which represents a challenge that the user has not yet participated in.

[0113] According to an eighth aspect of the present disclosure, a method for monitoring analyte responses associated with a user's diet is provided. The method includes receiving, by a processor coupled to a memory storing a dietary monitoring application, dietary information input by a user, the dietary information representing the user's food choices, and outputting, by the processor, a home GUI. The home GUI includes a plurality of selectable sections including a user profile section, a dietary input section, a trend section, a diary section, and a report section, a meal card configured to display one or more meal listings including the input dietary information for one or more meals consumed by the user, a trend card including a graphical representation representing information regarding the analyte responses associated with the user's food choices, a challenge card representing a listing of one or more challenges regarding the user's analyte responses or glucose levels, and a recommendation card representing one or more recommendations regarding the user's food choices or analyte responses.

[0114] According to a ninth aspect of the present disclosure, there is provided a method for monitoring an analyte response associated with a user's meal, the method including the steps of receiving data indicative of the user's analyte level via a wireless communication circuit, identifying, by a processor coupled to a memory storing a meal monitoring application, a peak analyte level within a predetermined time period for the received data indicative of the user's analyte level, identifying, by the processor, an estimated meal start time and an initial analyte level based on the peak analyte level, identifying, by the processor, a variance in the analyte level, prompting, by the processor, the user to input meal information, and associating, by the processor, the input meal information with the variance in the analyte level.

[0115] According to a tenth aspect of the present disclosure, there is provided a method for monitoring an analyte response associated with a user's diet, the method comprising the steps of receiving data indicative of a user's analyte level via a wireless communication circuit, receiving, by a processor coupled to a memory storing a dietary monitoring application, dietary information input by the user, receiving, by the processor, data indicative of the user's analyte level within a predetermined amount of time after the user inputs the dietary information, identifying, by the processor, a peak analyte level value in the received data indicative of the user's analyte level, identifying, by the processor, an initial analyte level value, identifying, by the processor, a variance in the analyte level, and relating, by the processor, the input dietary information to the variance in the analyte level.

[0116] According to an eleventh aspect of the present disclosure, there is provided a method of monitoring an analyte response associated with a user's meal, the method including receiving, via a wireless communication circuit, data indicative of a user's analyte levels, and outputting, by a processor coupled to a memory storing a meal monitoring application, a diary GUI, the diary GUI including a plurality of meal entries, each meal entry of the plurality of meal entries including a date of the meal entry, a meal name, a graphical representation of an analyte level variation value associated with the meal entry, and a numerical representation of an analyte level variation value associated with the meal entry.

[0117] According to a twelfth aspect of the present disclosure, there is provided a method of monitoring an analyte response associated with a meal of a user, the method including receiving, via a wireless communication circuit, data indicative of an analyte level of the user, and outputting, by a processor coupled to a memory storing a meal monitoring application, a trend GUI. The trend GUI includes a glycemic response view and a meal view, the glycemic response view including a graphical representation representing a plurality of segments including a first segment and a second segment. The first segment indicates a first analyte level variation range, and the second segment indicates a second analyte level variation range different from the first analyte level variation range.

[0118] In many embodiments, an individual's meal-related analyte responses collected by an analyte monitoring system, such as an in vivo analyte monitoring system, can be compared or linked to dietary information, and based on the associated historical glucose readings and associated algorithms, variables, weightings, and comparisons, common consistencies (or disruptions) and trends in the individual's meal-related analyte responses can be identified.

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

[0120] This embodiment can provide information quickly to an individual, encouraging them to take action to better understand how their diet is affecting their body's test substance response. By comparing current and past test substance data, individuals can see how their efforts are leading to better dietary and food choices, and how these choices are directly impacting their health.

[0121] Many of the embodiments provided herein provide an improved GUI or GUI functionality for the analyte monitoring system that is highly intuitive and user-friendly, allowing the user to quickly access physiological information. More specifically, these embodiments provide a variety of user interfaces that quickly present the user with various physiological conditions and possible responses, and that can correlate the analyte data with factors such as diet, exercise, and stress, without forcing the user (or HCP) to laboriously search through large amounts of analyte data, and allow the user to easily navigate within and between the various user interfaces. Furthermore, in many of the embodiments, some GUIs and GUI functionality allow the user (and / or their caregiver) to better understand and take action on managing diet, eating habits, and stressors by learning the correlation between such actions and glucose levels. Similarly, in many embodiments, the improved digital interface, functionality, or both of the diet monitoring system allows for a better visualization of the impact of food choices on analyte (glucose) levels. Other improvements and advantages are also provided. Various configurations of these devices are described in more detail in the following, but merely exemplary, embodiments.

[0122] The GUI improvements shown in the various aspects of the detailed description and claims of this specification provide at least the technical effect of assisting the user of the device to operate the device more accurately, efficiently and safely. It will be understood that the information provided to the user on the GUI, the order in which the information is provided, and the clarity of the organization of the information can have a significant impact on the user's interaction with the system and the way the system is operated. Thus, the GUI guides the user, who is performing the technical task of operating the system, to read the required indications and obtain the necessary information accurately and efficiently.

[0123] The aspects of the present disclosure are provided in relation to one another, and features of one aspect can be applied to other aspects. Any feature of one aspect of the present disclosure can be applied to other aspects of the present disclosure in any suitable combination. For example, a system feature of the first aspect can be combined with a method feature of the seventh or eighth aspect. It should also be understood that the specific combinations of the various features described and defined in any aspect of the present disclosure can be independently implemented, provided, used, or any combination thereof.

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

[0125] Details of the subject matter described herein, both in structure and operation, will become apparent from a study of the accompanying drawings, in which like parts are designated by like reference numerals. Additionally, the drawings do not necessarily illustrate components to scale, with emphasis instead being placed upon illustrating the principles of the subject matter. Additionally, while any figures are intended to convey concepts, detailed attributes such as relative size and shape may be shown diagrammatically and not precisely. [Figure 1] FIG. 1 is a schematic diagram illustrating an exemplary embodiment of an analyte monitoring system for performing analyte (e.g., glucose) measurement, data acquisition, and / or data processing; [Figure 2A]FIG. 1 is a block diagram illustrating an exemplary embodiment of a viewing device configured as a smartphone. [Figure 2B] FIG. 1 is a block diagram illustrating an exemplary embodiment of a sensor control device. [Figure 3A] FIG. 1 is a flow diagram illustrating an embodiment of a method for collecting and evaluating dietary information. [Figure 3B] FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for monitoring various analytes for use in a dietary monitoring application; [Figure 3C] FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for monitoring various analytes for use in a dietary monitoring application; [Figure 3D] FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for monitoring various analytes for use in a dietary monitoring application; [Figure 3E] FIG. 1 is a schematic diagram illustrating an exemplary embodiment of a system for monitoring various analytes for use in a dietary monitoring application; [Figure 3F] FIG. 1 is a flow diagram illustrating an exemplary embodiment of a method for correlating test substance data with dietary information. [Figure 3G] FIG. 1 is a flow diagram illustrating another exemplary embodiment of a method for associating test substance data with dietary information. [Figure 4A-1] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-2] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-3a] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-3b] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-4a] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-4b] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-5] FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-6]FIG. 1 illustrates an example embodiment of a home GUI for a meal monitoring application. [Figure 4A-7] FIG. 1 illustrates an example embodiment of a modal display of a home screen of a meal monitoring application. [Figure 4B] FIG. 1 illustrates an example embodiment of an “About Us” GUI for a meal monitoring application. [Figure 4C] FIG. 1 illustrates an example embodiment of a "Contact Us" modal display for a meal monitoring application. [Figure 4D] FIG. 1 illustrates an example embodiment of a "frequently asked questions" GUI for a diet monitoring application. [Figure 4E] FIG. 1 illustrates an example embodiment of a "frequently asked questions" GUI for a diet monitoring application. [Figure 4F] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4G] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4H] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4I] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4J] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4K] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4L] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4M] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4N] FIG. 1 illustrates an exemplary embodiment of a collaborative GUI for a meal monitoring application. [Figure 4O] FIG. 1 illustrates an example embodiment of a notification GUI for a meal monitoring application. [Figure 5A] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5B] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5C-1] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5C-2] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5D-1] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5D-2] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5E] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5F] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5G-1] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5G-2] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5H] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 5I] FIG. 1 illustrates an example embodiment of a profile GUI for a meal monitoring application. [Figure 6A] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6B] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6C] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6D] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6E] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6F] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6G] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6H] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6I] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 6J] FIG. 1 illustrates an example embodiment of an "add food" GUI for a food monitoring application. [Figure 7A] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7B] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7C] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7D] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7E] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7F] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7G] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7H] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7I] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7J] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7K] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7L]FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7M] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7N] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7O] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7P] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7Q] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 7R] FIG. 1 illustrates an example embodiment of a diary GUI for a meal monitoring application. [Figure 8A] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8B] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8C] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8D] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8E] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8F] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8G] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 8H] FIG. 1 illustrates an example embodiment of a trends GUI for a meal monitoring application. [Figure 9A] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9B] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9C]FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9D] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9E] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9F-1] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9F-2] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9F-3] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 9F-4] FIG. 1 illustrates an example embodiment of a report GUI for a meal monitoring application. [Figure 10] FIG. 1 is a flow diagram illustrating an example embodiment of a method for onboarding a user to a meal monitoring application. [Figure 11A-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11A-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11A-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-5] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11B-6]FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11C-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11C-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11C-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11D-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11D-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11D-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11D-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-5] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-6] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-7] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-8] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-9] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11E-10] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11F-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11F-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11F-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11G-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11G-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11H-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11H-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11H-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11I-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11I-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11I-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11I-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11J-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11J-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11J-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11K-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11K-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11K-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11K-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11L-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11L-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11L-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11L-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-1] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-4] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-5] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11M-6] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11N-1]FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11N-2] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 11N-3] FIG. 1 illustrates an example embodiment of an onboarding GUI for a meal monitoring application. [Figure 12A] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12B] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12C] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12D] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12E] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12F] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12G] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12H] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12I] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12J] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 12K] FIG. 1 illustrates an example embodiment of a challenge GUI for a meal monitoring application. [Figure 13A] FIG. 1 illustrates an example embodiment of notifications shown on a GUI of a meal monitoring application. [Figure 13B] FIG. 1 illustrates an example embodiment of notifications shown on a GUI of a meal monitoring application. [Figure 13C]FIG. 1 illustrates an example embodiment of notifications shown on a GUI of a meal monitoring application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0128] A number of systems have been developed to automatically monitor analytes, such as glucose, in bodily fluids, such as blood flow, interstitial fluid ("ISF"), dermal fluid in the dermis layer, and other biological fluids, and some of these systems are configured to obtain information regarding at least one analyte in the body by placing a sensor at least in part below the surface of the user's skin (e.g., within the user's blood vessels or subcutaneous tissue).

[0129] Such a system may be referred to as an "in vivo" monitoring system. An in vivo analyte monitoring system may be a "Continuous Analyte Monitoring" system (or a "Continuous Glucose Monitoring" system). A Continuous Analyte Monitoring system is a system that can transmit data from a sensor control device to a viewing device continuously (e.g., automatically according to a schedule) rather than on a prompting basis. An in vivo analyte monitoring system may also be a "Flash Analyte Monitoring" system (or a "Flash Glucose Monitoring" system, or simply a "Flash" system). A Flash analyte monitoring system is a system that can transmit data from a sensor control device in response to a data scan or data request by a viewing device, such as using a Near Field Communication (NFC) protocol or a Radio Frequency Identification (RFID) protocol. An in vivo analyte monitoring system may also operate without the need for finger-prick calibration.

[0130] In vivo analyte monitoring systems can be distinguished from "in vitro" systems that contact a biological sample outside the body (or, more accurately, "ex vivo"). Typically, an in vitro system includes a metering device having a port for receiving an analyte test strip carrying a user's bodily fluid, which can then be analyzed to determine the user's blood glucose level. Note that while many of the present embodiments perform monitoring in vivo, the embodiments disclosed herein can also be used with in vivo analyte monitoring systems that incorporate in vitro capabilities, or with entirely in vitro or ex vivo analyte monitoring systems.

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

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

[0133] In-Vivo Analyte Monitoring System Embodiments By way of example, and not by way of limitation, the GUI and associated software described herein may be used in connection with an exemplary analyte monitoring system such as that shown in FIG. 1 and the exemplary systems described below in the discussion of FIGS. 3B-3E. FIG. 1 illustrates an exemplary in-vivo analyte monitoring system 100 to which any and / or all of the embodiments described herein may be applied. The system 100 may include a sensor control device 102 and a viewing device 120 that communicate with each other via a local communication path (or link) 140. The local communication path 140 may be wired or wireless, and may be unidirectional or bidirectional. In embodiments in which the local communication path 140 is wireless, a communication protocol may be used, such as any Near Field Communication (NFC) protocol, RFID protocol, "Bluetooth" or "Bluetooth" Low Energy protocol, Wi-Fi protocol, proprietary protocol, and any communication protocol existing as of the filing date of this application or any variant developed thereafter.

[0134] "Bluetooth" is a well-known short-range wireless communication protocol standard, and "Bluetooth" Low Energy is a version of the standard that can operate with less power. Note that "Bluetooth" Low Energy ("Bluetooth" LE, BTLE, BLE) is also sometimes called "Bluetooth" Smart or "Bluetooth" Smart Ready. The BTLE version is described in "Bluetooth Specification, version 4.0" published on June 30, 2010, which is expressly incorporated by reference herein for any purpose. The term "NFC" is a term used for a number of protocols (or standards) that specify the operating parameters, modulation schemes, coding, transmission rates, frame formats, and command definitions of NFC devices. Examples of these protocols, without being exhaustive, include ECMA-340, ECMA-352, ISO / IEC14443, ISO / IEC15693, ISO / IEC16000-3, ISO / IEC18092, and ISO / IEC21481. No. 6,399,433, filed on Dec. 13, 2003, the entire contents of which (together with all subparts thereof) are hereby incorporated by reference for all purposes.

[0135] The viewing device 120 may also be in bidirectional or unidirectional wired, wireless or combined communication with any or all of the following: medication delivery device 160 via communication path (link) 143; local computer system 170 via communication path (link) 141; and network 190 via communication path (link) 142. The same wireless protocols described with respect to link 140 may be used for all or some of links 141, 142, 143 as well.

[0136] The viewing device 120 can communicate with numerous entities via the network 190. The network 190 can be part of an electrical communication network such as a Wi-Fi network, a local area network (LAN), a wide area network (WAN), or a data network for one-way or two-way communication such as the Internet. The trusted computer system 180 can then be accessed via the network 190. In an alternative embodiment, the communication paths 141 and 142 can be the same path, which can include the network 190 and / or additional networks. All communications over the communication paths 140, 141, 142, 143, 144 can be encrypted, and the sensor control device 102, the viewing device 120, the drug delivery device 160, the remote computer system 170, and the trusted computer system 180 can each be configured to encrypt and decrypt communications sent and received.

[0137] Variations of devices 102 and 120, as well as other components of an in vivo analyte monitoring system suitable for use in combination with embodiments of the systems, devices, and methods described herein, are described in U.S. Patent Application Publication No. 2011 / 0213225 (the "'225 Publication"), the entire contents of which are incorporated herein by reference for all purposes.

[0138] The sensor control device 102 may include a housing 103 that houses an in-vivo analyte monitoring circuit and a power source (not shown). The in-vivo analyte monitoring circuit may extend through an adhesive patch 105 and be in electrical communication with an analyte sensor 104 that protrudes outwardly of the housing 103. The adhesive patch 105 includes an adhesive layer (not shown) for attachment to a user's body skin surface. It should be noted that other forms of attachment to the body may be used in addition to or instead of adhesion.

[0139] The sensor 104 is adapted to be at least partially inserted into a user's body to make fluid contact with the user's bodily fluid (e.g., interstitial fluid (ISF), dermal fluid, or blood) at an insertion site and thereby be used in combination with an in vivo analyte monitoring circuit to measure analyte-related data of the user. In general, the sensor control device 102 and its components may be attached to the body in one or more steps using a mechanical applicator 150, as described in the '225 publication, which is incorporated herein by reference, or may be attached in any other desired manner.

[0140] Once activated, the sensor control device 102 may wirelessly communicate collected analyte data (e.g., data corresponding to the analyte level being monitored and / or temperature data being monitored and / or stored historical analyte-related data) to the viewing device 120, which may then, in certain embodiments, algorithmically process the data into data indicative of the user's analyte level that may then be displayed to the user and / or otherwise incorporated into a diabetes monitoring regimen.

[0141] Various embodiments disclosed herein relate to a viewing device 120 that may have a user interface including one or more of a display 122, a keyboard, user interface components 121 (optional), and the like, where display 122 may output information to a user, receive input from a user (e.g., if display 122 is configured as a touch screen), or both. Viewing device 120 may optionally include one or more user interface components 121, such as buttons, actuators, touch-sensitive switches, capacitive switches, pressure-sensitive switches, jog wheels, and the like. Viewing device 120 may also include one or more data communication ports 123 for wired data communication with an external device, such as a local computer system 170. Additionally, viewing device 120 may further include an integrated or attached in-vitro meter that may include an in-vitro test strip port (not shown) for receiving an in-vitro analyte test strip for performing in-vitro measurements of an analyte in blood.

[0142] The drug delivery device 160 can inject or infuse a drug into the body of an individual wearing the sensor control device 102. Drugs include, but are not limited to, insulin. Like the viewing device 120, the drug delivery device can include a processing circuit, a non-transitory memory that stores instructions executable by the processing circuit, wireless or wired communication circuitry, and a user interface that includes one or more of a display, a touch screen, a keyboard, input buttons or input devices, and the like. The drug delivery device 160 can include a drug reservoir, a pump, an infusion tube, and an infusion cannula configured to be at least partially implanted in the user's body. The pump can deliver insulin from the reservoir through the tube and cannula in that order into the user's body. The drug delivery device 160 can include processor-executable instructions for controlling the pump and thus the amount of insulin delivered. The instructions may also cause calculation of insulin delivery amount and duration (e.g., bolus and / or basal infusion profile) based on analyte level measurements obtained directly or indirectly from sensor control device 102. Alternatively, calculation of insulin delivery amount and duration, as well as pump control, may be performed directly by viewing device 120. The drug delivery device may be configured to communicate directly with viewing device 120 in a closed or semi-closed loop system. Alternatively, the drug delivery device may have the functionality of viewing device 120 described herein, or vice versa, providing an integrated viewing and drug delivery device.

[0143] Computer system 170 may be any suitable data processing device, such as a personal computer, laptop, or tablet. Computer 170 may be local to viewing device 120 (e.g., accessible via a direct wired connection, such as USB) or remote from viewing device 120 and may be (or include) software for managing and analyzing data and communicating with components of analyte monitoring system 100. The operation and use of computer 170 is described in more detail in the '225 publication, which is incorporated herein by reference. Analyte monitoring system 100 may also be configured to operate using a data processing module (not shown), as described in the '225 publication, which is incorporated herein by reference.

[0144] The trusted computer system 180 may be used to authenticate users, sensor control devices 102, and / or viewing devices 120, store sensitive data received from devices 102 and / or 120, output sensitive data to devices 102 and / or 120, and the like, which are just a few examples of the functionality of the trusted computer system 180. The trusted computer system 180 may include one or more computers, servers, networks, databases, and the like. In some embodiments, the trusted computer system 180 may include a cloud computing platform with one or more servers. The trusted computer system 180 may be owned by the manufacturer or distributor of the sensor control device 102, either physically or virtually via a secure connection, or may be maintained and operated by a different party (e.g., a third party).

[0145] The term "trusted" for the trusted computer system 180 can be used to mean that the system 100 can assume that the computer system 180 provides authentic data or information. In other words, the "trusted" nature of the trusted computer system 180 is merely guaranteed by being under the ownership or control of the manufacturer, and can be as "trusted" as a normal web server. Alternatively, the trusted computer system 180 can be implemented in a more secure manner, for example, by strengthening the security of Internet access, such as additional password requirements, encryption, or firewalls, to provide enhanced protection against counterfeiting attacks and attacks by computer hackers.

[0146] Data processing and software execution within system 100 may be performed by one or more processors in either viewing device 120, computer system 170, or sensor control device 102. For example, raw data measured by sensor 104 may be subjected to algorithmic processing to convert it into a value representative of an analyte level that is highly suitable for display to a user, which processing may be performed in either sensor control device 102, viewing device 120, or computer system 170. Information derived from the raw data, such as this information, may be displayed on any display provided in either sensor control device 102, viewing device 120, or computer system 170 in any of the formats discussed above (with respect to display 122). A user may then use this information to determine corrective actions required to ensure that the analyte level remains within an acceptable and / or clinically safe range.

[0147] 2A is a diagram illustrating an example embodiment of a viewing device 120, and FIG. 2B is a diagram illustrating an example embodiment of a sensor control device 102. As mentioned above, the viewing device 120 can be a mobile communication device such as, for example, a Wi-Fi or Internet-enabled smartphone, tablet, or personal digital assistant (PDA). Examples of smartphones include, but are not limited to, smartphones based on the WINDOWS® operating system, the ANDROID® operating system, the IPHONE® operating system, the PALM WEBOS® operating system, the BLACKBERRY® operating system, and the SYMBIAN® operating system, and having network connectivity for data communication over the Internet or a local area network (LAN).

[0148] The viewing device 120 can also be configured as a mobile smart wearable electronics assembly, such as an optical assembly (e.g., monocular or binocular smart glasses) worn over or adjacent to the user's eyes. Such an optical assembly can have a transparent display that can display information to the user about the user's analyte levels (as described herein) while at the same time allowing the user to see through the display with minimal interference to the user's overall field of vision. The optical assembly can have wireless communication capabilities similar to a smart phone. Other examples of wearable electronics include devices worn around or near the user's wrist (e.g., watch), neck (e.g., necklace), head (e.g., headband, hat), chest, etc.

[0149] 2A is a block diagram illustrating an exemplary embodiment of a viewing device 120 according to various embodiments disclosed herein. In this example, viewing device 120 takes the form of a smartphone on which various software, applications, and graphical user interfaces disclosed herein may reside. Here, viewing device 120 includes input component 121, display 122, and processing hardware 206. Processing hardware 206 may include one or more processors, microprocessors, controllers, and / or microcontrollers, each of which may be separate chips or may be distributed across multiple different chips (and portions thereof). Here, processing hardware 206 includes communications processor 222 having on-board non-transitory memory 223, and application processor 224 having on-board non-transitory memory 225. Viewing device 120 also includes RF transceiver 228 coupled to RF antenna 229, memory 230, multifunction circuitry 232 having one or more associated antennas 234, power supply 226, and power management circuitry 238. FIG. 2A shows a simplified diagram of the internal components of a smartphone, and of course the smartphone may include other hardware and functionality (eg, codecs, drivers, glue logic, etc.).

[0150] The communications processor 222 interfaces with the RF transceiver 228 and performs functions such as analog-to-digital conversion, coding / decoding, digital signal processing, and the like that aid in converting audio, video, and data signals into a suitable format (e.g., in-phase and quadrature) for presentation to the RF transceiver 228 so that the RF transceiver 228 can transmit those signals wirelessly. The communications processor 222 also interfaces with the RF transceiver 228 and can perform functions in the reverse direction, such as receiving wireless transmissions from the RF transceiver 228 and converting them into digital data, audio, and video.

[0151] Application processor 224 may be configured to perform functions unrelated to processing communications transmitted and received via RF antenna 229, such as running the operating system and any software applications resident on viewing device 120 (e.g., any sensor interface applications or analyte monitoring applications, including SLL 304), and video and graphics processing. Any number of applications may be running simultaneously on viewing device 120 at any time. Such applications would typically include one or more applications related to a diabetes monitoring therapy, as well as general use applications unrelated to such therapy, such as, for example, email, calendar, weather, etc.

[0152] Memory 230 may be shared among one or more of the various functional units present in viewing device 120, or may be distributed among two or more of them (e.g., as separate memories present in different chips). Memory 230 may also be a separate, standalone chip in its own right. Memory 230 is non-transitory memory and may be volatile memory (e.g., RAM, etc.) and / or non-volatile memory (e.g., ROM, flash memory, F-RAM, etc.).

[0153] Multifunction circuitry 232 may be implemented as one or more chips and / or components that include communications circuitry to perform other functions, such as local wireless communications (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy) and determining the geographic location of viewing device 120 (e.g., global positioning system (GPS) hardware). And, optionally, one or more other antennas 234 are associated with multifunction circuitry 232.

[0154] Power source 226 may include one or more batteries, which may be rechargeable or disposable. Power management circuitry 238 may control battery charging, power monitoring, power boosting, DC conversion, and the like. As mentioned above, viewing device 120 may further include one or more data communication ports, such as a USB port (or connector) or an RS-232 port (or any other wired communication port) for data communication with remote computer system 170 (see FIG. 1) or sensor control device 102, to name a few.

[0155] FIG. 2B is a block schematic diagram illustrating an exemplary embodiment of a sensor control device 102 having an analyte sensor 104 and sensor electronics 250 (including analyte monitoring circuitry). While any number of chips can be used, in many embodiments, most of the sensor electronics 250 are integrated onto a single semiconductor chip 251, which can be, for example, a custom application specific integrated circuit (ASIC). Within the ASIC 251 are several higher order functional units, such as an analog front end (AFE) 252, a power management circuit 254, a processor 256, and a communication circuit 258 (which can be implemented as a transmitter, receiver, transceiver, passive circuitry, etc., to communicate according to a communication protocol). In the embodiment shown in FIG. 2B, both the AFE 252 and the processor 256 are utilized as analyte monitoring circuitry, but in other embodiments, either circuitry can perform the analyte monitoring function. The processor 256 may comprise one or more processors, microprocessors, controllers, and / or microcontrollers.

[0156] Also included within ASIC 251 is non-transitory memory 253, which may be shared among the various functional units present within ASIC 251 or may be distributed among two or more of them. Memory 253 may be volatile and / or non-volatile. In this embodiment, ASIC 251 is coupled to power source 260, which may be a coin cell battery or the like. AFE 252 interfaces with in-vivo analyte sensor 104 to receive measurement data therefrom and outputs such data in digital form to processor 256, which then processes the data to determine final results such as discrete analyte values ​​and trend values. The data may then be provided to communication circuitry 258 for transmission via antenna 261 to viewing device 120 (not shown), where further processing may be performed, such as by a sensor interface application. It should be noted that the functional components of ASIC 251 may also be distributed among two or more separate semiconductor chips. For example, in some embodiments, the communications circuitry 258 can be a semiconductor chip separate from the ASIC 251, and the communications circuitry 258 can be configured to process signals received from the in-vivo analyte sensor 104 (e.g., via the ASIC 251) into a final result, a discrete or trend value of the analyte.

[0157] By performing data processing functions within the electronic components of the sensor control device 102, the system 100 can flexibly schedule communications from the sensor control device 102 to the viewing device 120, thereby reducing the number of unnecessary communications and achieving further power savings in the sensor control device 102.

[0158] Transmission of information from the sensor control device 102 to the viewing device 120 may be automatic, continuous, or both automatic and continuous when the test substance information is available, or may not be automatic or continuous and may be stored or recorded in the memory of the sensor control device 102 (e.g., for later output).

[0159] Data transmission from the sensor control device 102 to the viewing device 120 can be initiated by either the sensor control device 102 or the viewing device 120. For example, in many exemplary embodiments, the sensor control device 102 can spontaneously transmit data periodically, unsolicited, so that an eligible viewing device 120 can receive the transmitted data (e.g., analyte sensor data) if it is in range and listening. In this case, the viewing device 120 does not need to first send a request or the like to prompt the sensor control device 102 to transmit the data. Thus, this is at the initiative of the sensor control device 102. Such transmission can be according to a schedule (e.g., about every minute, about every five minutes, about every ten minutes, etc.) programmed within the device 102 (e.g., using an enabled Wi-Fi, "Bluetooth" or BTLE connection). Transmission can also be in a random or pseudo-random manner, such as whenever the sensor control device 102 detects a change in the analyte sensor data. Moreover, repeated transmissions may occur regardless of whether viewing device 120 actually receives each such transmission.

[0160] The system 100 may also be configured to transmit a transmission from the viewing device 120 prompting the sensor control device 102 to transmit data it has from the sensor control device 102 to the viewing device 120. This is commonly referred to as "on-demand" data transmission. On-demand data transmission may be initiated based on a schedule stored in the memory of the viewing device 120 or upon a user request via a user interface of the viewing device 120. For example, if a user wishes to check their analyte levels, the user may scan the sensor control device 102 using an NFC, "Bluetooth", BTLE, or Wi-Fi connection. Data may be exchanged by broadcast, session-based transmission, on-demand transmission, or a combination thereof.

[0161] Thus, once the sensor control device 102 is placed on the body such that at least a portion of the sensor 104 is in contact with bodily fluids and in electrical communication with electronics within the device 102, analyte information from the sensor can be transmitted on-demand or autonomously from the sensor control device 102 to the viewing device 120. On-demand transmission can be performed by first powering on the viewing device 120 (or the viewing device 120 can remain powered on) and executing a software algorithm stored in and accessed from the memory of the viewing device 120 to generate and send one or more requests, commands, control signals, or data packets to the sensor control device 102. The software algorithm executed (e.g., under control of the processing hardware 206 of the viewing device 120) can include routines for detecting the relative position of the sensor control device 102 with respect to the viewing device 120 and initiating transmission of the generated requests, commands, control signals, and / or data packets.

[0162] Exemplary embodiments of a method for relating test substance data to dietary information In many embodiments, the subject matter described herein is implemented by a software application program stored in a memory of and executed by a processor-equipped device, such as a viewing device (e.g., a smartphone), a drug delivery device, or any one of the other computing devices described herein. In certain embodiments, the software is implemented as one or more software applications ("apps") that can be downloaded to a viewing device, such as a mobile communication device or a smartphone.

[0163] The software may provide a mechanism for the user to conveniently define consumables (e.g., specify the type of food or type of drink and their quantities). In this specification, such consumables are referred to broadly as meals, and the term "meal" is used broadly to refer to any type of food or drink.

[0164] This software may perform a number of functions related to collecting meal information and correlating the collected meal information with analyte information, either through in vivo analyte sensors 104, or through in vitro test strips and meters, or through a trusted computer system 180. In the following, this software will generally be referred to as a "meal monitor application," "meal monitoring application," or "meal monitoring app."

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

[0166] The meal monitoring application may also monitor the user's analyte data to identify when changes in the analyte data occur that indicate the occurrence of a potential meal event, and seek to associate the potential meal event with meal information for the relevant time period. The meal monitoring application may prompt the individual to enter meal information for the potential meal event and allow the individual to modify the time of the detected meal event. In some embodiments, if a meal event is detected but the meal monitoring application determines that meal information has already been entered, the user may not be prompted.

[0167] The meal monitoring application may also associate the measured analyte responses with meal events and store the results in a non-transitory memory or database. In particular, the meal monitoring application may display each meal and its associated analyte response (e.g., analyte response, such as glucose response) to the user, for example, sorting the meals in descending order (e.g., for glucose, descending order of magnitude of glycemic response). Additionally, the analyte response to each meal event may be illustrated in an easy-to-understand graphical representation. For example, if a meal has a relatively small analyte response (i.e., good analyte response), the name of the meal may be displayed next to a green symbol to communicate that the analyte response caused by the meal was within a predetermined low analyte response range. Similarly, if a meal has a relatively large analyte response (i.e., undesirable analyte response), the name of the meal may be displayed next to an orange symbol to communicate that the analyte response caused by the meal was within a predetermined high analyte response range. Additionally, in some embodiments, a numerical value indicating elevated analyte levels may be displayed adjacent to the graphical representation.

[0168] Another aspect of the meal monitoring application includes detecting a peak analyte value from the post-prandial analyte response, as described in detail herein, and another exemplary embodiment of the magnitude of the analyte response may be determining the difference between the post-prandial analyte peak value and the detected analyte value at the start of the meal.

[0169] Yet another aspect of the dietary monitoring application includes analyzing analyte responses for the same or similar meals. For example, if a user repeatedly consumes the same or similar meals, a weighted average for the meals can be determined and displayed. Additionally, in some embodiments, more recently collected analyte data can be weighted more heavily in the weighted average.

[0170] Exemplary embodiments of the dietary monitoring application may utilize analyte data analysis software or software-implementable processes, such as those disclosed in, for example, U.S. Patent Application Publication Nos. 2013 / 0085358, 2014 / 0350369, 2014 / 0088393, 2018 / 0128007, 2017 / 0185748, 2020 / 0105397, 2021 / 0030323, 2022 / 0000399, WO 2015 / 153482, and PCT / US2020 / 12134, the entire disclosures of all of which are incorporated herein by reference for any purpose. Additionally, exemplary embodiments of this software are collectively referred to as a "meal event detector." A meal event detector may be an algorithm, routine, or other set of instructions (which may be part of or separate from a meal monitoring application) capable of detecting and quantifying the occurrence of actual or potential meal events in the analyte data of a monitored individual.

[0171] Reference is now made to FIG. 3A, which is a flow diagram illustrating an exemplary embodiment of a method 300 for collecting and correlating meal information with analyte data to determine the glycemic load of the meal. The method 300 includes operations that can be described as operations performed by an electronic device, such as a viewing device 120 (e.g., a smartphone), a drug delivery device 160, or a computer system 170 or 180, or a processor thereof. The user can be an individual or a diabetic patient, a clinical administrator, a medical professional, a dietary profession, or the like. By way of example only, the method 300 will be described below with reference to a diabetic patient using the dietary monitoring software as an app downloaded onto a viewing device 120 configured as a smartphone. For ease of explanation, the analyte monitored in this embodiment and other embodiments described below is glucose, although other analytes may be monitored as noted herein.

[0172] 3A, at step 302, a user may log meal information. The user may, at their discretion, enter meal information directly into viewing device 120 (via a user interface) before, during, or after consuming a meal. In some embodiments, the user enters meal information in response to reminders generated by the meal monitoring application according to a predefined schedule that can be set and modified by the user.

[0173] At step 304, the user's analyte data is monitored. This analyte data monitoring step can be performed in a variety of ways by a variety of systems, such as those illustrated in the system diagrams of FIG. 1 and FIG. 3B-3E. In one exemplary embodiment, system 325 (FIG. 3B) can transmit the user's analyte data from a sensor control device 102 (having an analyte sensor 104) worn on the user's body to the viewing device 120, where it is received by a sensor interface application 327 resident on the viewing device 120. The sensor interface application 327 can then transmit the analyte data over network 190 to trusted computer system 180, where it can be further processed and / or aggregated with other analyte data. The trusted computer system 180 then transmits the appropriate analyte data as appropriate to a dietary monitoring application 329, also resident on the viewing device 120. Depending on system 325 , in one embodiment, sensor interface application 327 and meal monitoring application 329 may be separate software programs resident on a single viewing device 120 .

[0174] 3C illustrates another exemplary embodiment of a system 330 for monitoring a user's analyte data. System 330 is similar to system 325, except that sensor interface functionality 327 constitutes a module within meal monitoring application 329. According to one aspect of system 330, sensor interface functionality 327 is authorized to communicate directly with sensor control device 102 and can receive analyte data from sensor control device 102, which can be analyzed by meal monitoring application 329. Meal monitoring application 329 can then transmit the analyte data over network 190 to trusted computer system 180, where further processing can be performed on the analyte data. In some embodiments, meal monitoring application 329 can also be configured to transmit meal information to trusted computer system 180.

[0175] 3D illustrates another exemplary embodiment of a system 335. In the system 335, a sensor interface application 327 resides on a first viewing device 120A and a meal monitoring application 329 resides on a second viewing device 120B. According to one aspect of the system 335, the sensor control device 102 can send analyte data directly to the sensor interface application 327, which in turn can transmit the analyte data to the trusted computer system 180 over the network 190. The meal monitoring application 329, which resides on a separate viewing device 120B, can then receive the analyte data from the trusted computer system 180. In some embodiments, the meal monitoring application 329 can also be configured to transmit the meal information to the trusted computer system 180.

[0176] In yet another embodiment, FIG. 3E illustrates another exemplary embodiment of a system 340 in which test substance data is manually entered or transmitted to the dietary monitoring application 329 and there is no direct communication between the system 340 and a sensor control device or trusted computer system. The system 340 may be utilized, for example, with the dietary monitoring application 329 in an "unlinked mode," which is described in more detail below in the discussion of FIG. 10.

[0177] Additionally, in any of the above systems, information (e.g., a timestamp) indicating the time each analyte data measurement was collected may be transferred to viewing device 120. As discussed herein above, this data transfer may be on-demand (e.g., upon execution of a user scan), streamed, or otherwise scheduled. Additionally, analyte data collected from a separate blood glucose measurement (e.g., a test strip read by a meter) may be entered into viewing device 120 either manually or automatically.

[0178] Returning to FIG. 3A, at step 306, the viewing device 120 may algorithmically process the collected analyte data to determine whether a meal event has occurred. This may be done using the meal event detection method described in the discussion of FIG. 3F. The meal event detection method illustrated in FIG. 3F examines the analyte data for one or more conditions that indicate the occurrence of a meal event. Again, this algorithmic process may be repeated frequently, for example, whenever new analyte data is received from the sensor control device 102 in response to a user using the viewing device 120 to perform an NFC scan of the sensor control device 102. Manual logging of meal information by the user (step 302) may occur simultaneously with the monitoring (step 304) and processing (step 306) of the analyte data. Those skilled in the art will appreciate that these methods may be implemented in a system that autonomously transmits analyte data wirelessly from the sensor control device to the viewing device at predetermined intervals.

[0179] 3A, each time new data is sent to viewing device 120, algorithmic processing may be applied to the new data. For purposes of detecting meal events, such data may represent a period of several hours (e.g., the past 8 hours, etc.). Steps 308-320 may be performed for each detected meal event, and may be performed repeatedly for all detected meal events, starting with meal events whose detection time is closer to the present.

[0180] Once a meal event is detected at step 306, the meal monitoring application evaluates at step 308 whether meal information corresponding to the detected meal event has already been entered (e.g., by a user at step 302). This evaluation may be done by examining whether meal information was entered during a period of time before the detected event's occurrence time up to the time of occurrence, or optionally a range of time after the occurrence time (e.g., to compensate for inaccuracies in timekeeping or entry times). If so, at step 314 the meal monitoring application may associate the meal information with the detected event. In some embodiments, if multiple meal information entries are found, the meal monitoring application may associate all found meal information entries with the detected event, or may associate only the meal information that occurred closest in time to the detected event with the detected event.

[0181] If meal information that can be associated with the detected event has not been entered, the user is prompted to enter meal information at step 310. If a meal event has not occurred, the user may decline or ignore the prompt. If a meal event has occurred, meal information may be entered at step 312.

[0182] The prompt can be in the form of an alarm notification, such as a vibration or sound, that alerts the user to launch the meal monitoring application to view the prompt, or alternatively, the prompt can be a notification that is displayed the next time the user views the application.

[0183] Whether the user logs meal information at their own discretion (step 302), or in response to a prompt (step 310), or logs meal information (step 312), the meal information can include various levels of detail and can be entered in the same or similar manner.

[0184] 3A, once the meal information for a meal event is entered at step 312, the meal monitoring application associates analyte data with the meal information in memory at step 314. Specifically, analyte data occurring around the time of a meal event may be associated with the meal event information. The analyte data selected to be associated with a meal event may be selected based on the time the meal event occurred, or, optionally, a time after the meal event occurred to reflect changes in analyte levels due to the digestion of a meal.

[0185] In some embodiments, analyte data occurring from the start of a meal to a certain time after the meal is finished may be associated with a meal event. Also, analyte data occurring from the start of a meal to the end of a detected glucose excursion may be associated with a meal event. In some embodiments, analyte data collected during a certain length of time around a meal event may be associated with a meal event, which may be, for example, any combination of 1, 2, or 3 hours before the meal event (e.g., measured from the start of the meal event, the middle of the meal event, or the end of the meal event) to 1, 2, 3, 4, 5, 6, 7, or 8 hours after the meal event. In either case, the time at which the meal event occurred may be determined based on information entered by the user or may be determined by algorithmic analysis of the analyte data.

[0186] The association of the analyte data with the meal event can be used to determine the glycemic load of the meal event in step 316. In some embodiments, the glycemic load of the meal event can be determined algorithmically based on the analyte data contemporaneous with the meal event, which algorithmic processing can include steps 314 and 316. The determination of the glycemic load can be quantitative in terms of maximum (peak) or minimum glucose levels, median or mean glucose levels, change in glucose level from minimum to maximum (delta (Δ) glucose level), percent fluctuation in glucose level, duration of glucose response, rate of change in glucose level, area of ​​glucose response, and any combination thereof.

[0187] The meal event detector outputs information regarding the glycemic response to a meal, which information can be used to characterize the magnitude (severity) of the glycemic response. For example, the meal event detector can output a start time and a peak time for each detected meal event. "Meal start glucose" can be the glucose value at the start time of the meal event, and "peak glucose" can be the glucose value when the elevated episode of the glycemic response to the detected meal event peaks. By determining the difference between these glucose values, a delta glucose measure of the glycemic response to the meal can be determined.

[0188] Returning to FIG. 3A, in step 318, the determined glycemic response (glycemic load) is output to the user. Such output may be, for example, by visual display on a smartphone display, as described below in the description of FIGS. 7A-7I. The determined glycemic response may be output from a quantitative perspective, a qualitative perspective, or both. For example, the determined glycemic response may be output on the same quantitative scale used to determine the glycemic response in step 316. Such output may be in the form of text, a graph, or both. The determined glycemic response may also be output qualitatively, for example, in text representing "low" or "mild," "moderate" or "moderate," or "high" or "severe," or synonyms thereof. The number of scales representing the magnitude of the response may also be increased or decreased. Additionally or alternatively, the determined glycemic response may also be output as an image, such as an icon (e.g., an image of a colored shape indicating various degrees of magnitude of the response).

[0189] 3A, by repeating method 300, the meal monitoring application may continually receive, monitor and store analyte data (e.g., step 304 of method 300) and continually search for and detect meal events (step 306). The most recently entered information about a detected (logged) meal may be included in the choices presented to the user as each new event is detected.

[0190] As will be described below, the information output by the dietary monitoring application provides the user with quick, specific and easy-to-understand information about the burden that their diet is placing on their analyte levels. This information can then be used to help the user avoid or minimize certain foods in their diet that they may not have realized were placing a burden on their glucose levels, e.g., raising their glucose levels too high. This information can also help the user to control portion sizes by helping them understand the relative impact of portion sizes on glucose levels.

[0191] Next, an exemplary embodiment of a method for associating analyte data with dietary information will be described. Turning to FIG. 3F, a flow diagram is shown illustrating an exemplary embodiment of a method 350 for associating analyte data with dietary information when no dietary information has been previously input by the user. It should be noted at the outset that one skilled in the art will recognize that the method 350, either in its entirety or in any one or more individual steps, can be combined with or implemented as part of the method 300 shown in FIG. 3A. The method 350 begins with step 352 receiving data indicative of a user's analyte level. In some embodiments, step 352 can be performed by, for example, a user scanning a sensor control device with a viewing device. In other embodiments, step 352 can be performed autonomously if the sensor control device is configured to wirelessly stream analyte data to the viewing device. Then, in step 354, a peak analyte level value within a predetermined time period is identified for the received analyte data. In some embodiments, step 354 may include, for example, identifying a highest glucose value within the received analyte data that exceeds a predetermined analyte level threshold (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL, etc.). Additionally, in some embodiments, the predetermined time period may include a set number of hours of analyte data within the received analyte data (e.g., the last 2 hours of analyte data, the last 4 hours of analyte data, the last 8 hours of analyte data, the last 12 hours of analyte data, etc.).

[0192] 3F, an estimated meal start time and associated initial analyte level may be identified at step 356. In some embodiments, for example, the estimated meal start time may be identified by counting back from the time of the peak analyte level (e.g., 2 hours prior to the time of the peak analyte level, 3 hours prior to the time of the peak analyte level, 4 hours prior to the time of the peak analyte level, etc.). The initial analyte level may be identified by referencing the analyte level indication at the estimated meal start time.

[0193] A further step 358 determines an analyte level variability by subtracting the initial analyte level from the peak analyte level. In a next step 360, the method 350 may prompt the user to enter meal information. In step 362, the entered meal information is stored in memory in association with the analyte level variability.

[0194] Turning now to FIG. 3G, a flow diagram is shown illustrating an exemplary embodiment of a method 370 for associating test substance data with dietary information. The method 370 is a method in which dietary information has already been input by a user. It should be noted at the outset that one skilled in the art will recognize that the method 370, either in its entirety or in one or more individual steps, can be combined with or implemented as part of the method 300 shown in FIG. 3A. As shown at the top of FIG. 3G, the method 370 begins with a step 372 in which a user inputs dietary information. In some embodiments, the step 372 can be a step in which the user proactively inputs dietary inputs, for example, before being prompted by a prompt from a dietary monitoring application. In other embodiments, the user can input dietary information in response to a prompt displayed by the dietary monitoring application. For example, according to some embodiments, the meal monitoring application may be configured to display a reminder notification to the user (as shown in notification GUI 440 of FIG. 4O) if no meal entry has been made after a predetermined reminder period (e.g., no meal entry for the past week, no meal entry for the past three days, no meal entry for the past day, etc.).

[0195] Next, at step 374, the meal monitoring application receives data indicative of the user's analyte levels within a predetermined amount of time. In some embodiments, step 374 may include the user scanning the sensor control device within a predetermined amount of time from the meal entry (e.g., within 4 hours of the meal entry being made, within 8 hours of the meal entry being made, within 12 hours of the meal entry being made, etc.). In other embodiments, step 374 may be performed autonomously if the sensor control device is configured to wirelessly stream the analyte data to the viewing device.

[0196] 3G, at step 376, a peak analyte value in the analyte data may be identified. In some embodiments, step 376 may include identifying the highest glucose value above a predefined analyte level threshold (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL, etc.). The peak analyte value may be a glucose value above a predefined analyte level threshold during a time window after the meal entry (e.g., a 2 hour time window after the meal entry, a 3 hour time window after the meal entry, a 4 hour time window after the meal entry). Then, at next step 378, an initial analyte level is identified. According to some embodiments, the initial analyte level may be identified by identifying an analyte level value at or near the time of the meal entry.

[0197] A subsequent step 380 involves determining an analyte level variation value, for example by subtracting the initial analyte level value from the peak analyte level value, and in a next step 382 the analyte level variation value may then be stored in memory in association with the dietary input made by the user.

[0198] Exemplary embodiments of the GUIs and associated functionality of a meal monitoring application Next, exemplary embodiments of various GUIs and associated software functionality of a meal monitoring application capable of implementing any of the above-described methods 300, 350, 370 will be described. However, those skilled in the art will appreciate that these various interfaces may be displayed by any of the embodiments of viewing device 120 (e.g., a smartphone), drug delivery device 160, or local computer system 170 described herein.

[0199] Exemplary embodiments of the home and related GUIs 4A-1 through 4A-7 illustrate an example embodiment of a home GUI (sometimes referred to herein as a “home screen GUI”) and functionality associated with the home GUI used in conjunction with a meal monitoring application.

[0200] Referring to FIG. 4A-1, an exemplary embodiment of a home GUI 400 of a meal monitoring application is shown. According to an aspect of the embodiments, the home GUI 400 may include a number of selectable sections. Such selectable sections may include, but are not limited to, a user profile section 402, a meal entry section 404, a trends section 406, a diary section 412, and a reports section 414. A user may select a section to cause the meal monitoring application to display a GUI corresponding to the selected section. Such GUIs are described in more detail below. In some embodiments, the home GUI 400 may also include a navigation bar 416 (bottom), an email button 408 (top) for requesting support from the manufacturer, and a notification button 410 (top) configured to relay in-app notifications to the user. For example, selecting the notification button 410 may cause the meal monitoring application to display a notification log, such as that shown in GUI 440 of FIG. 4O.

[0201] FIG. 4A-2 illustrates a further exemplary embodiment of a home GUI for use in a meal monitoring application. Specifically, FIG. 4A-2 illustrates a home GUI 450 similar to the home GUI 400 illustrated in FIG. 4A-1. According to an aspect of some embodiments, the home GUI 450 includes an information button 455 (at the top) configured to display a number of selectable links. The information button 455 can be selected by a user to cause the meal monitoring application to display a GUI corresponding to the selected link. Additionally, the home GUI 450 further includes a banner 451. The banner 451 includes a message reminding the user to scan the sensor every 8 hours to ensure that a total meal load can be verified. In some embodiments, the banner 451 is positioned adjacent to or away from the greeting and user name display in the user profile section 453.

[0202] 4A-3a-4b illustrate another exemplary embodiment of a home GUI for use in a meal monitoring application. FIG. 4A-3a-4b illustrates a home GUI 460 similar to the home GUIs 400, 450, which may include multiple selectable sections. Such selectable sections may include, but are not limited to, a user profile section 4002, a meal entry section 4004, a trends section 4006, a diary section 4012, and a reports section 4014. Similar to the home GUIs 400, 450, the home GUI 460 may also include a navigation bar 4016 (bottom). According to an aspect of the embodiments, the home GUI 460 may further include (1) a meal card 4100, (2) a trends card 4200, (3) a challenge card 4300, and (4) a recommendation card 4400. Additionally, the home GUI 460 may also include a banner 461. The banner 461 includes a message reminding the user to scan the sensor every 8 hours so that the total meal load can be viewed. In some exemplary embodiments, the user name is displayed in the user profile section 4002 of the home GUI 460 in close proximity to the banner 461.

[0203] Further, according to an aspect of the embodiments, the home GUI 460 may be scrollable and dynamic. Thus, in some embodiments, the content displayed in the home GUI 460 may change in response to a predetermined user input. Such predetermined user input may include, for example, a predetermined action performed by a user on a screen, such as scrolling, dragging, pulling, etc. As such, the home GUI 460 may include a plurality of views configured to display portions of the home GUI 460 to a user. Specifically, in some embodiments, the home GUI 460 may be configured to transition between a plurality of different views. More specifically, the home GUI may be configured to transition between the views in response to a predetermined user input.

[0204] In some exemplary embodiments, the home GUI includes at least a first view and a second view. In some embodiments, as shown in FIG. 4A-5, in a first view of the scrollable home GUI 460, a user profile section 4002, a meal entry section 4004, a diary section 4012, and a meal card 4100 can be displayed on the home GUI 460. Additionally, as shown in FIG. 4A-6, in a second view of the scrollable home GUI 460, a trend card 4200, a challenge card 4300, and a recommendation card 4400 can be displayed on the home GUI 460. According to an aspect of some embodiments, the navigation bar 4016 is configured to remain anchored on the home GUI 460 (as shown in FIG. 4A-5 and FIG. 4A-6) and is displayed on all views of the scrollable home GUI 460.

[0205] Referring again to FIG. 4A-3a-4A-4b, in some embodiments, the meal card 4100 is configured to display one or more meal lists 4101. The one or more meal lists 4101 include meal information for one or more recently consumed meals. Specifically, each meal list section 4101 presents details of a particular meal consumed by the user along with a glycemic response associated with that meal. In some exemplary embodiments, the one or more meal lists 4101 may be ordered such that the meal section 4101 corresponding to the most recently consumed meal is displayed first, i.e., at the top of the meal card 4100, and subsequent meal sections 4101 are displayed in chronological order. As best shown in FIGS. 4A-3a-4A-4b, in some embodiments, each meal list entry 4101 may include (1) a textual representation of the meal (food) 4102 (e.g., “boiled egg” as shown in FIG. 4A-4a), (2) a portion size indicator 4103 indicating the relative portion size of the meal compared to the user's usual meal sizes (e.g., “S” representing a small meal, “M” representing a medium meal, and “Large” representing a large meal), (3) a date stamp 4104 associated with the date the meal was consumed, (4) a time stamp 4105 associated with the time the meal was consumed, and (5) a graphical representation 4106 indicating the user's glycemic response to the meal corresponding to the entry.

[0206] In many embodiments, as shown in FIGS. 4A-3a-4b, the graphical representation 4106 may include a shape (e.g., an arch, circle, or bar shape) divided into multiple segments with different colors (or no color) for each segment. Each color may correspond to a range or rank of test substance response. For example, as shown in each meal listing 4101 in FIGS. 4A-3a-4b, a semicircular (or "rainbow" shape) may include three segments, with (1) a first segment colored green to indicate a low glycemic response to the meal, (2) a second segment colored yellow to indicate a medium glycemic response to the meal, and (3) a third segment colored orange to indicate a high glycemic response to the meal.

[0207] According to another aspect of some embodiments, each of the different colors may indicate a range of analyte level excursion values ​​("impact"), as determined by any of methods 300, 350, 370 (described in the description of FIGS. 3A, 3F, 3G). For example, if the analyte level excursion value (e.g., the difference between the pre-prandial glucose level and the post-prandial glucose level a predetermined time after the meal) is determined to be within a range of low analyte level excursion (e.g., less than 60 mg / dL or less than 3.3 mmol / L), a first segment may be colored green (and the other segments gray) to indicate that the meal caused a low glycemic response (low meal impact). As another example, if the test substance level fluctuation value is determined to be within a range of moderate test substance level fluctuation (e.g., 60 mg / dL to 100 mg / dL, or 3.3 mmol / L to 5.6 mmol / L), the second segment is colored yellow (and the other segments are colored gray) to indicate that the blood glucose response caused by the meal (food) was moderate (the meal (food) load was moderate). As yet another example, if the test substance level fluctuation value is determined to be within a range of high test substance level fluctuation (e.g., over 100 mg / dL or over 5.6 mmol / L), the third segment is colored orange (and the other segments are colored gray) to indicate that the blood glucose response caused by the meal (food) was large (the meal (food) load was large).

[0208] According to another aspect of some embodiments, all segments may be grayed out if one or more conditions are met, such as if the analyte level fluctuation is less than zero, if the analyte level fluctuation is greater than a maximum analyte level fluctuation (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL), or if the initial analyte level is greater than a maximum initial analyte level (e.g., 180 mg / dL, 200 mg / dL, 220 mg / dL, 250 mg / dL, etc.). If one or more of these conditions are met, this may indicate that the identified analyte level fluctuation is not representative of analyte level fluctuation associated with dietary intake, for example, because it is unreliable, cannot be calculated accurately, etc.

[0209] Additionally, while the illustrated graphical representation 4106 is a semicircle divided into three colored segments, one of ordinary skill in the art would understand that other geometric shapes, colors, and numbers of segments may be employed and are fully within the scope of the present disclosure. Similarly, while the above description indicates that each color may represent a particular range of values, one of ordinary skill in the art would understand that other ranges may be utilized and that the numerical values ​​provided above are not intended to be limiting.

[0210] With further reference to FIGS. 4A-3a-4A-4b, according to another aspect of the embodiments, the trend card 4200 of the home GUI 460 can be configured to present recent trend information regarding test substance responses associated with the user's food choices. In some exemplary embodiments, the trend card can include a summary panel 4201 that can show an overall evaluation of the user's food choices for a particular period of time (e.g., the previous day, week, or month). For example, the summary panel 4201 of FIG. 4A-3b describes that the user's "food choices resulted in a 33% decrease in foods classified as green." Additionally, the summary panel 4201 of FIG. 4A-4b describes that the user's "food choices resulted in a 25% decrease in foods classified as green."

[0211] Also, in some embodiments, as shown in FIGS. 4A-3a-4b, the trend card 4200 further includes a graphical representation 4202 indicating a analyte response associated with the user's food choices over a particular time period. In some embodiments, the graphical representation 4202 may include a shape divided into multiple segments with each segment having a different color (or no color), and each color may correspond to a range or rank of analyte response. In some exemplary embodiments, the graphical representation 4202 may include a semicircular shape having three segments, with (1) a first segment being colored green to indicate a low glycemic response associated with the user's food choices over a recent or particular time period, (2) a second segment being colored yellow to indicate a medium glycemic response associated with the user's food choices over a recent or particular time period, and (3) a third segment being colored orange to indicate a high glycemic response associated with the user's food choices over a recent or particular time period.

[0212] In some embodiments, the trend card 4200 is not displayed in the home GUI 4200 if analyte data (e.g., data indicative of analyte levels (e.g., glucose levels)) has not yet been received, if no analyte data is associated with the meal (food) entry, or both. In accordance with an aspect of some embodiments, the trend card 4200 may be dynamic. In particular, the meal monitoring application may detect whether new trend information is included in the analyte responses associated with the user's food selections. The trend card 4200 may be configured to update as new trend information is detected, and the updated trend card 4200 may include an updated summary panel 4201 with information regarding the new trend information.

[0213] Also, in some embodiments, as shown in FIG. 4A-3a-4b, the home GUI 460 includes a challenge card 4300 configured to display one or more selectable challenge icons 4301. Each challenge icon 4301 represents one of a variety of challenges that the user may participate in, each challenge being related to the user's test substance response or glucose level. The challenges may suggest specific actions or activities to the user, and may present seasonal and / or behavior-based challenges that may impact the user's test substance levels, which in turn may help the user manage their diabetes. In some exemplary embodiments, the challenge icons 4301 may represent a challenge for the user to consume a predetermined number of consecutive meals classified as meals with a particular test substance response (e.g., the "4 meals in a row" challenge icon shown in FIG. 4A-3b, where the "4 meals in a row" challenge icon 4301 represents a challenge for the user to consume four consecutive low-load (low-glycemic) meals). Additionally, the challenge icon 4301 may represent a challenge to the user to consume a particular type of meal (e.g., the "breakfast" challenge icon shown in FIGS. 4A-3b and 4A-4b). In yet another example, the challenge icon 4301 may represent a challenge to the user to continue to consume a particular amount of food (e.g., vegetables and fruits) per day for a predetermined period of time. In still another example, the challenge icon 4301 may represent a challenge to the user's lifestyle trends (e.g., drink more water, eliminate soda, increase exercise, or eliminate fast food for a predetermined period of time). Those skilled in the art will readily recognize various other challenges for use in a food monitoring application.

[0214] According to an aspect of the embodiments, each challenge icon 4301 may include an image or photo 4302 associated with a particular challenge. Additionally, the challenge icon 4301 may also include a challenge name 4303, which is a textual representation of the challenge that the challenge icon represents. In some embodiments, different challenge icons 4301 may be displayed on the challenge card 4300 depending on the received user input (e.g., user input by a predetermined action such as a swipe or drag operation). For example, in some embodiments, the challenge card 4300 may display a challenge icon set of two or three challenge icons 4301. In response to the received input, the challenge card 4300 may display a new set of challenge icons 4301 on the home GUI 460. In some embodiments, at least one challenge icon 4301 of the new challenge icon set is different from at least one challenge icon 4301 of the original challenge icon set before receiving the user input.

[0215] In some embodiments, when a user selects a challenge icon 4301, the new challenge icon 4301 is displayed in place of the previously selected challenge icon 4301. In some embodiments, the challenge icon 4301 can be scheduled to remain on the home GUI 460 for a predetermined period of time.

[0216] Additionally, the challenge card 4300 may include a selectable "View All" link 4304. When the user selects the "View All" link 4304, the challenge list GUI 1200 is output, which includes a list of challenges. The challenge list displays all open challenges in which the user is currently participating, challenges that the user has successfully completed, and challenges that the user has not yet participated in.

[0217] Additionally, in some embodiments, the home GUI 460 displays a recommendation card 4400 configured to display one or more selectable recommendation icons 4401. Each recommendation icon 4401 represents one of various recommendations being presented to the user. The recommendations may relate to the user's food choices, test substance responses, or both. The recommendations may suggest specific actions or activities to the user, and may provide seasonal and / or behavior-based content (e.g., recommendations for healthy eating around and around holidays, or how to attach and remove sensors). In some embodiments, the recommendation icons 4401 may be linked to a trusted source of information regarding the recommendation they represent. According to one aspect of some embodiments, the dietary monitoring application algorithmically processes and analyzes the entered dietary input data to detect and / or quantify the user's food choices. The recommendation icons 4401 may then be utilized to strongly promote recommendations that are believed to represent more desirable (more beneficial) suggestions for the user. For example, if the dietary monitoring application detects that the user frequently consumes chicken, a recommendation icon related to chicken 4401 may be displayed to the user. In yet another example, if the dietary monitoring application detects that the user has a tendency to consume pizza, a recommendation icon suggesting alternatives to pizza may be displayed to the user.

[0218] According to another aspect of some embodiments, when a user selects a recommendation icon 4401, a modal display 4405 (FIG. 4A-7) related to the selected recommendation icon 4401 may be displayed on the home GUI 460. The modal display 4405 may provide context information related to the recommendation to guide the user to act on the recommendation. In some embodiments, the context information may prompt the user to perform an activity or action in accordance with the recommendation. For example, when a user selects the "Summer Vacation" recommendation icon 4401 as shown in FIG. 4A-6, a modal display 4405 providing information related to the summer vacation recommendation is displayed on the home GUI 460 (see, for example, "Keep recording your meals even on your days off. Click the button below to add a meal now." in FIG. 4A-7). In some embodiments, the modal display 4405 may include a start button 4406 as shown in FIG. 4A-7. When the user selects the start button 4406, the user may proceed with their efforts to follow the recommendations (e.g., selecting the "Add Food" button in FIG. 4A-7 may allow the user to add a meal (food) entry, thereby allowing the user to track their meals over the holiday according to the summer vacation recommendations).

[0219] According to an aspect of the embodiments, as best shown in FIGS. 4A-4b, each recommendation icon 4401 may include an image or photo 4402 associated with the particular recommendation. Each recommendation icon 4401 may further include a recommendation name 4403, which is a textual representation of the corresponding recommendation. Additionally, in some embodiments, different recommendation icons 4401 may be displayed in the recommendation card 4400 depending on the received user input (e.g., user input by swiping, dragging, or some other second predetermined action). For example, in some embodiments, the recommendation card 4400 may display a recommendation icon set of two or three recommendation icons 4401. The recommendation card 4400 may display a new set of recommendation icons 4401 on the home GUI 460 depending on the received input. In some embodiments, at least one recommended icon 4401 in the new set of recommended icons is different from at least one recommended icon 4401 in the original set of recommended icons before user input was received.

[0220] In some embodiments, when a user selects a recommendation icon 4401, the new recommendation icon 4401 is displayed in place of the previously selected recommendation icon 4401. In some embodiments, a particular recommendation icon 4401 can be scheduled to remain on the home GUI 460 for a predetermined period of time.

[0221] In an aspect of some embodiments, as best shown in FIGS. 4A-4a, the home GUI 460 can further include an information button 4008 (top) configured to display a number of selectable links. The information button 4008, when selected by a user, can cause the meal monitoring application to display a GUI corresponding to the selected link. In some embodiments, as best shown in FIGS. 4A-4a, selecting the information button 4008 can display (1) a "Profile" link 4001, (2) a "Notifications" link 4003, (3) a "Order your next sensor" link 4005, (4) a "Frequently Asked Questions" ("FAQ") link 4007, (5) a "About Us" link 4009, and (6) a "Contact Us" link 4011.

[0222] 4B illustrates a About Us GUI 470 that is displayed on the food monitoring application when a user selects the About Us link 4009 on the Home GUI 460. In some embodiments, the About Us GUI 470 includes multiple selectable sections that the user can select to display a corresponding GUI, including, but not limited to, a License section 471, a Privacy Policy section 472, and a Terms of Use section 473.

[0223] 4C further illustrates a contact us modal display 474 that is displayed on the meal monitoring application when a user selects the contact us link 4011 on the home GUI 460. In particular, the contact us modal display 474 may be displayed on the home GUI 460 and may include contact information that has been provided to the meal monitoring application.

[0224] 4D and 4E illustrate an exemplary embodiment of a FAQ GUI 480 that is displayed on the food monitoring application when a user selects a FAQ link 4007 on the home GUI 460. According to some embodiments, the FAQ GUI 480 includes a first question section 481 that includes information about launching the food monitoring application and a second question section 482 that includes information about adding (logging) food to the food monitoring application. In some embodiments, the first question section 481 and the second question section 482 each include a list of selectable question links 483. When the question link 483 is selected, the question link 483 is configured to expand (as shown in FIG. 4E) to display a list of answers to the question stated in the question link 483. In some embodiments, the first question section 481 and the second question section 482 are configured to expand ( FIG. 4E ) or collapse ( FIG. 4D ) in response to a received user input (e.g., a predetermined action such as a tapping action). 4F-I, an exemplary embodiment of an association GUI for when a user launches the meal monitoring application for the first time is shown. In some embodiments, once a user successfully launches the meal monitoring application (and further completes the onboarding process and tutorial), the meal monitoring application may prompt the user to provide account information to associate the meal monitoring application with the sensor interface application. For example, FIG. 4F shows a modal display requesting the user to associate the meal monitoring application with the sensor interface application. Upon selection of the "Associate" button 418 (FIG. 4F), the meal monitoring application may display an account login GUI 420, including an email field 422, a password field 424, and a sign-in button 426, as shown in FIG. 4G. Once the user successfully signs in, a consent GUI 430 may be displayed to the user to obtain the user's consent to sharing data with the meal monitoring application.If the user agrees to this, the screen returns to the home GUI 400, and a modal display 432 indicating that the link between the meal monitoring application and the sensor interface application has been successfully completed is displayed.

[0225] 4J-4N show further exemplary embodiments of the association GUI for the first time the user launches the meal monitoring application. Specifically, FIG. 4J shows a modal display requesting the user to associate the meal monitoring application with the sensor interface application. When the "associate" button 4180 (FIG. 4J) is selected, the meal monitoring application may display an account login GUI 465 including an email field 4220, a password field 4240, and a sign-in button 4260, as shown in FIG. 4K. Once the user successfully signs in, the consent GUI 475 (FIG. 4L) may be displayed to the user to obtain the user's consent to sharing data with the meal monitoring application. If the user agrees, the user may be returned to the home GUI 450 or 460 with a modal display 4320 indicating that the meal monitoring application has been successfully associated with the sensor interface application (FIG. 4M shows the modal display on the home GUI 460). In some embodiments, if the meal monitoring application is unable to successfully link with the sensor interface application, a modal display 4321 is displayed on the home GUI 450 or 460 indicating this (e.g., that the attempted link was unsuccessful because the account credentials already in use by another meal monitoring application, as shown in FIG. 4N). In some embodiments, the modal display 4321 may include an "OK" button 4322 and a "Link" button 4323, as shown in FIG. 4N.

[0226] Example Embodiment of User Profile GUI 5A and 5B, an exemplary embodiment of a user profile GUI 500 of a diet monitoring application is shown. The user profile GUI 500 is displayed when a user selects the user profile section 402 on the home GUI 400. As shown in FIG. 5A, the user profile GUI 500 can include a number of editable fields configured to receive personal information about a user of the diet monitoring application. In some embodiments, the user profile GUI 500 can include a profile icon 504, a name field 508, an email address field 510, a phone number field 512, a country field 514, and a language field 516. Additionally, as shown in FIG. 5B, the user profile GUI 500 can further include a number of selectable options to prompt the user to enter additional profile information or user preferences. For example, the number of selectable options can include a disease state field 518, a unit of measure field 520, and medications taken field 522. According to another aspect of some embodiments, the user profile GUI 500 may also include a consent checkbox 524 to indicate whether the user wishes to opt-in (or opt-out) to receive additional information and / or promotional solicitations. In many embodiments, the user profile GUI includes an update button 526 to save any changes the user makes to the profile information. In some embodiments, the user profile GUI 500 may also include a "Link Sensor App" button (not shown) if the user has not yet linked the meal monitoring application to the sensor app.

[0227] 5C-1 and 5C-2 show further exemplary embodiments of a user profile GUI 550 of a meal monitoring application. In some embodiments, FIG. 5C-1 and FIG. 5C-2 show a user profile GUI 550 that may be displayed when a user selects a user profile section 4002 on the home GUI 460. The user profile GUI 550 is similar to the user profile GUI 500, except that the user profile GUI 550 further includes a birth date field 501, a gender field 503, and a consent checkbox 507 for the user to indicate whether the user wishes to opt-in (or opt-out) to receive personalized notifications for the user. FIG. 5D-1 and FIG. 5D-2 show the user profile GUI 550 further including a "Link Sensor App" button 531. FIG. 5E shows the user profile GUI 550 with a user selecting an options button 532 (e.g., FIG. 5D-1). Specifically, the user profile GUI is configured to display a number of selectable links when the user selects the options button 532. Such selectable links (as shown in FIG. 5E) include, but are not limited to, a "Reset Password" link 533, a "Delete Account" link 534, and a "Log Out" link 535. If the user selects the "Delete Account" link, the meal monitoring application may display a modal display 536 requesting the user to confirm whether or not they wish to proceed with deleting the account information (as shown in FIG. 5F).

[0228] According to another aspect of the embodiments, as shown in FIG. 5G-1, a user may select a profile icon 5004 to upload a photo / image 5005 to be associated with the user profile. In some embodiments, the user may select a photo 5005 from a photo library. Specifically, as shown in FIGS. 5H and 5I, when the user selects the profile icon 5004, a pop-up modal display 537 configured to request access to the user's photos may be displayed on the user profile GUI 550. FIG. 5H illustrates the pop-up modal display 537 presented via a first mobile operating system (e.g., iOS), and FIG. 5I illustrates the pop-up modal display 538 presented via a second mobile operating system (e.g., Android). In some embodiments, if the user does not associate a photo 5005 with the user profile, a placeholder image (e.g., as shown in FIGS. 5C-1-5F) is displayed instead on the profile icon 5004. In some embodiments, as shown in FIGS. 5C-1 through 5F, the placeholder image is an initial corresponding to the first letter of the entered user's first name (e.g., "J" for a user named "John").

[0229] Exemplary embodiment of meal entry GUI 6A-6E, an exemplary embodiment of a meal entry GUI 600 for a meal monitoring application is shown. Referring first to FIG. 6A, the meal entry GUI 600 is displayed when a user selects the meal entry section 404 on the home GUI 400. Alternatively, the meal entry GUI 600 can be displayed by a user selecting an icon corresponding to the meal entry GUI 600 in the navigation bar (bottom). The meal entry GUI 600 can also include an information button 602 for providing context information 603 (FIG. 6C) and a notification button 604 for relaying in-app notifications (FIG. 4O) to the user.

[0230] A desirable aspect of the embodiments described herein is the ease of inputting meal information. This can facilitate use of the meal monitoring application and allow the user to more intuitively understand the impact of food intake on blood glucose levels, which can in turn improve the user's health. As shown in FIG. 6A, the meal entry GUI 600 can include selectable meal type suggestions 606, which allow the user to easily indicate the type of meal (e.g., breakfast, lunch, dinner, snack, dessert, etc.) for the meal entry. According to another aspect of the embodiments, the meal entry GUI 600 can include a search / add field 608, which allows the user to enter the name of the food to be included in the meal entry. As the user enters the meal name in the search / add field 608, the meal monitoring application can automatically suggest entries based on the user's previous meal entries. For example, in some embodiments, the meal monitoring application can retrieve information about previous meal entries with the same (or similar) food name and display them (e.g., in a list) in the results section 612. The list may be sorted such that the most commonly consumed (selected) meal is first (at the top) of the list, with the remaining meals ordered by frequency of consumption (e.g., the most commonly consumed meal is first, the next most commonly consumed meal is second, ..., the least commonly consumed meal is last). In some embodiments, the list may also be sorted by least burdensome entry (e.g., lowest analyte level fluctuation value) to suggest more preferred foods to the user. Once the desired food name is displayed in the results section 612, the user may select the entry and press the add button 610. This is convenient for the user as it does not require the user to enter all of the food or meal names.

[0231] Additionally, in some embodiments, the meal entry GUI 600 may also include voice recognition capabilities. According to one aspect of some embodiments, instead of manually entering a meal name in the search / add field 608, a user may enter the meal name by pressing a voice recognition button 609 and speaking the meal name out loud. The meal monitoring application may be configured to display the closest results in the results section 612 in response to this voice command.

[0232] Additionally, although Figure 6B illustrates a list-based results section 612, one of ordinary skill in the art will appreciate that other interfaces may be implemented, such as by manually entering text, selecting a meal name from a list (e.g., a selection or drop-down list), selecting a photo of the meal from a collection of photos, selecting a friendly meal indicator (e.g., a tag or code), or any combination thereof.

[0233] According to another aspect of some embodiments, the meal entry GUI 600 may also include an activity checkbox 614. As shown in FIGURE 6B, when the activity checkbox 614 is selected, an activity text box 616 is displayed on the meal entry GUI 600, allowing the user to enter a text description of the exercise (e.g., walking, gardening, cycling, etc.) that was engaged in around the time of the meal event.

[0234] According to another aspect of some embodiments, upon entering the meal information (and optionally further entering the activity information), the user may select a "Next" button 618 to display a modal display configured to request additional information, as shown in FIG. 6D. The modal display may include, for example, a date field 620, a time field 622, and a meal portion field 624, which may capture details of the meal event. Additionally, in some embodiments, the modal display may include an "Add Notes" checkbox 626. When the user selects the "Add Notes" checkbox 626, a notes text box 630 (FIG. 6E) is displayed, which may allow the user to enter additional notes to accompany the meal entry (e.g., specific information about the meal, medications the user took around the time of the meal).

[0235] In some embodiments, the time fields may be auto-populated based on the time the user selects the "Next" button 618. According to an aspect of some embodiments, the auto-populated time fields may also be editable by the user. In other embodiments, the time fields may include the time the meal started and ended when consumed (rather than a single time entry as shown in FIG. 6D). In other embodiments, the times in the time fields may be generalized (heuristic) time periods (e.g., early morning, late afternoon, etc.) or approximate time ranges (e.g., 6-7am, 5-6pm, etc.) rounded to any desired increment (e.g., 10, 15, 30, 60 minutes, etc.).

[0236] 6F-6J illustrate another example embodiment of a meal entry GUI 650 for a meal monitoring application. Referring first to FIG. 6F, similar to the meal entry GUI 600 shown in FIGS. 6A-6E, the meal entry GUI 650 may be displayed when a user selects the meal entry section 4004 on the home GUI 460. Alternatively, the meal entry GUI 650 may be displayed by a user selecting an icon corresponding to the meal entry GUI 650 in the navigation bar (bottom). The meal entry GUI 650 may also include an information button 653 for providing context information (FIG. 6J).

[0237] As shown in FIG. 6F, the meal entry GUI 650 can include selectable meal type suggestions 6506, allowing the user to easily indicate the type of meal (e.g., breakfast, lunch, dinner, snack, drink, etc.) for the meal entry. According to another aspect of some embodiments, the meal entry GUI 650 can include a search / add field 6508, which allows the user to enter the name of the food to be included in the meal entry (as shown in FIG. 6G). As with the search / add field 608, as the user types the meal name in the search / add field 6508, the meal monitoring application can automatically suggest entries based on the user's previous meal entries. In some embodiments, once the user enters a meal name or selects an entry entered by the auto-suggest feature, a meal tag 6511 containing the entered meal name is added to the meal library section 6512 (best shown in FIGS. 6G and 6I). A user may assign one or more meal tags 6511 to meals consumed (e.g., in FIG. 6I, the user has assigned the meal tags 6511 "diet coke," "green salad," and "ham sandwich" to the lunch entry).

[0238] In some embodiments, the meal entry GUI 650 may also include a voice recognition feature 6509. According to one aspect of some embodiments, instead of manually entering the meal name in the search / add field 6508, the user may press a voice recognition button 6509 (best shown in FIGS. 6F and 6I ) and enter the meal name by speaking it out loud.

[0239] According to another aspect of some embodiments, the meal entry GUI 650 may include portion size indicator 6524 options indicating relative amounts of meals consumed, such as selectable buttons indicating different meal sizes, such as "small," "medium," and "large" (e.g., in FIG. 6H , the "medium" portion size indicator 6524 has been selected).

[0240] Additionally, the meal entry GUI 650 may also include a time field 6522 that includes a time and date associated with the meal entry. In some embodiments, the time field 6522 may be automatically associated with the meal entry or may be auto-populated based on the time the user entered the meal entry. According to an aspect of some embodiments, the auto-populated time field 6522 may also be editable by the user.

[0241] According to another aspect of the embodiments, once the meal information is entered, the user may select an add button 6518 (as best shown in FIGS. 6H and 6I). In some embodiments, as best shown in FIGS. 6F and 6H, the meal entry GUI 650 may also include a feedback query 6515 (e.g., "Did you like the meal?") that asks the user to indicate whether they liked the meal. In some embodiments, the feedback query 6515 may include a first sign 6516 (e.g., a thumbs up gesture button). The user may indicate that they enjoyed the meal by selecting the first sign 6516. The feedback query 6515 may also include a second sign 6517 (e.g., a thumbs down gesture button). The user may indicate that they did not enjoy the meal by selecting the second sign 6517. However, one skilled in the art will recognize that the meal entry GUI embodiments described herein may utilize other buttons, icons, or indicia to indicate whether the user enjoyed the meal.

[0242] Feedback obtained from the user via feedback query 6515 may be used to recommend foods that induced a low to moderate glycemic response (load) to the user. For example, if the user selects a first signature in response to feedback query 6515 asking the user to indicate whether they enjoyed a meal, and the meal induced a low to moderate glycemic load, the meal monitoring application may thereafter recommend the meal to the user. Additionally, feedback obtained from the user via feedback query 6515 may be used to avoid recommending foods that the user did not enjoy or that had a medium to high glycemic load. For example, if the user selects a second signature in response to feedback query 6515 asking the user to indicate whether they enjoyed a meal, the meal monitoring application may thereafter avoid recommending meals that the user did not enjoy. In this regard, feedback query 6515 may be used to help the user make better food choices by recommending foods that induced a low to moderate glycemic load and that the user enjoyed.

[0243] Exemplary embodiment of the diary GUI Turning now to Figures 7A-7I, an exemplary embodiment of a diary GUI 700 of a meal monitoring application is shown. In many embodiments, the diary GUI 700 is displayed when a user selects the diary section 412 on the home GUI 400 (Figure 4A-1). Alternatively, the diary GUI 700 can be displayed by a user selecting an icon corresponding to the diary GUI 700 in the navigation bar (bottom). Additionally, the diary GUI 700 can include an information button 702 (Figure 7A) to provide contextual information 714 (Figure 7B) and a notification button 704 (Figure 7A) to provide an in-app notification to the user (Figure 4O). In some embodiments, the diary GUI 700 can also include a search bar 708 configured to allow a user to search for a particular diary entry.

[0244] According to an aspect of some embodiments, the diary GUI 700 can display a user's past test substance responses to meals in a user-friendly and easy-to-understand manner. In some embodiments, for example, the diary GUI 700 can include multiple views in which the test substance responses can be organized and displayed. For example, as shown in FIG. 7A, when the day view option 706 is selected, the diary GUI 700 can display the test substance responses "by day." Similarly, as shown in FIG. 7H, when the week view option 736 is selected, the diary GUI 700 can display the test substance responses "by week."

[0245] Referring again to FIG. 7A, an exemplary embodiment of a daily overview 710 of glycemic responses associated with meals in the diary GUI 700 is shown. As shown in the daily overview 710, a meal entry including "Dosa, Tea" is displayed for the day "12 March 2022", with multiple meals and foods displayed for this date. As shown, to the left of each meal entry is a graphical representation of the user's glycemic response to that meal. In addition to the graphical representation, each meal entry may also include a time of entry and a numerical value indicating the analyte level fluctuation value ("load") associated with that meal.

[0246] In many embodiments, the graphical representation includes a shape (e.g., an arch, circle, or bar shape) divided into multiple segments with a different color (or no color) for each segment, and each color can correspond to a range or rank of analyte response. For example, as shown in the daily overview 710, a semicircular (or "rainbow" shape) can include three segments, with (1) a first segment colored green to indicate a low glycemic response to the meal, (2) a second segment colored yellow to indicate a medium glycemic response to the meal, and (3) a third segment colored orange to indicate a high glycemic response to the meal.

[0247] According to another aspect of some embodiments, each of the different colors may indicate a range of analyte level fluctuation values, as determined by any of methods 300, 350, 370 (described in the description of FIGS. 3A, 3F, 3G). For example, if the analyte level fluctuation value is determined to be within a low analyte level fluctuation range (e.g., less than 60 mg / dL or less than 3.3 mmol / L), a first segment may be colored green (and the other segments gray) to indicate that the meal caused a low glycemic response (low meal load). As another example, if the test substance level fluctuation value is determined to be within a range of moderate test substance level fluctuation (e.g., 60 mg / dL to 100 mg / dL, or 3.3 mmol / L to 5.6 mmol / L), the second segment is colored yellow (and the other segments are colored gray) to indicate that the glycemic response caused by the meal was moderate (the meal load was moderate). As yet another example, if the test substance level fluctuation value is determined to be within a range of high test substance level fluctuation (e.g., over 100 mg / dL or over 5.6 mmol / L), the third segment is colored orange (and the other segments are colored gray) to indicate that the glycemic response caused by the meal was large (the meal load was large). These interface examples are shown in modal displays 722, 724, and 726 (FIGS. 7D, 7E, and 7F).

[0248] According to another aspect of some embodiments, all segments may be grayed out if one or more conditions are met, such as if the analyte level fluctuation is less than zero, if the analyte level fluctuation is greater than a maximum analyte level fluctuation (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL), or if the initial analyte level is greater than a maximum initial analyte level (e.g., 180 mg / dL, 200 mg / dL, 220 mg / dL, 250 mg / dL, etc.). If one or more of these conditions are met, this may indicate that the identified analyte level fluctuation is not representative of analyte level fluctuation associated with dietary intake, for example, because it is unreliable, cannot be calculated accurately, etc.

[0249] Additionally, while the illustrated graphical representation is a semicircle divided into three colored segments, one of ordinary skill in the art would understand that other geometric shapes, colors, and numbers of segments may be employed and are fully within the scope of the present disclosure. Similarly, although the above description indicates that each color may represent a particular range of values, one of ordinary skill in the art would understand that other ranges may be utilized and that the numerical values ​​set forth above are not intended to be limiting.

[0250] Referring again to FIG. 7A, in accordance with another aspect of some embodiments, a user may select a graphical representation to display a pop-up modal display providing more information about a particular meal (food) entry. For example, as shown in FIG. 7D, a pop-up modal display 722 includes a graphical representation and a textual description in close proximity to one another that the meal entry is a "low load" (green). The textual description includes the analyte level variation value for the meal entry (e.g., 27 mg / dL) followed by an explanation of how the analyte level variation value was calculated (e.g., using the glucose value at the time the food was entered and the subsequent glucose peak). Similarly, a pop-up modal display 724 (FIG. 7E) is associated with a meal entry that is a "medium load" (yellow) and is accompanied by a textual description, and a pop-up modal display 726 (FIG. 7F) is associated with a meal entry that is a "high load" (orange) and is accompanied by a textual description.

[0251] In some embodiments, when a meal (food) entry is selected that is not yet associated with received test substance data, the meal monitoring application may also display a notification 728 (as shown in FIG. 7G) that test substance data has not yet been received for that entry.

[0252] In an alternative embodiment, as shown in Figure 7I, a meal entry shown in the day view can be configured to expand to display an additional information panel 738. In these embodiments, if the meal has been consumed multiple times in the past, the information panel 738 can include a weighted average metric of analyte level fluctuations.

[0253] In some embodiments, the weighted average of analyte level variation values ​​for a particular food may be based on the same (or similar) food entries added within a predefined time period (e.g., the last 60 days, the last 90 days, the last 120 days). In some embodiments, the weighted average may be based on the minimum of a predefined number of analyte level variation values ​​and the maximum of a predefined number of analyte level variation values ​​within a predefined time period. Additionally, in some embodiments, meal entries for which no analyte level variation values ​​were identified (or below a minimum threshold) may be omitted from the weighted average calculation. Thereafter, the weighted average is calculated (updated) whenever an associated meal entry is created or updated.

[0254] Also, according to some embodiments, the weighted average may take into account the recency of the analyte level variation values ​​stored for a particular meal. For example, in determining the weighted average, past analyte level variation values ​​for a meal entry that are more recent than other past analyte level variation values ​​may be weighted more heavily. For example, and by way of example only, in calculating the weighted average, the analyte level variation values ​​for a meal entry may be decreased by a predetermined factor for each day going back from the current date.

[0255] In other embodiments, other representative values ​​of analyte level variation, such as the general mean, median, mode, etc., may be used instead of the weighted average.

[0256] In some embodiments, the information panel 738 can also be configured to display activity information associated with a particular meal (e.g., information entered into the activity text box 616 (FIG. 6B)). As shown in FIG. 71, for example, the additional information panel 738 may display "Workout, Running." In some embodiments, the information panel 738 can also display notes (e.g., information entered into the notes text box 630 (FIG. 6E)).

[0257] Returning to FIG. 7H, an exemplary embodiment of a weekly view 734 of glycemic responses associated with meals in the diary GUI 700 is shown. As shown in the weekly view 734, a number of meals are displayed for the week of "November 13, 2021 - November 19, 2021". As shown, the left portion of each meal entry displays a graphical representation of the user's glycemic response to that meal. In addition to the graphical representation, each meal entry may also include a date, a time of entry, and a numerical value indicating the analyte level variation. Those skilled in the art will appreciate that any of the features and processes described above with respect to the daily view 710 (FIG. 7A) may also be applied with respect to the weekly view 734 (FIG. 7H).

[0258] Returning to FIG. 7C, an exemplary embodiment of a filter GUI 720 of the diary GUI 700 is shown. According to some embodiments, the filter GUI 720 can include a date filter 719, which is a filter for limiting the display of meal entries to a particular date range. In some embodiments, the filter GUI 720 can also include an analyte level variability filter 717, which is a filter for limiting the display of meal entries to a particular analyte level variability rank (e.g., low load, medium load, or high load). The filter GUI 720 can also include an "apply" button 716 for applying the selected filter to the current set of meal entries. Similarly, in some embodiments, the filter function can also include a release button 718 for resetting (removing) the current filter.

[0259] 7J-7R, further exemplary embodiments of a diary GUI 750 of a dietary monitoring application are shown. In many embodiments, the diary GUI 750 is displayed when a user selects the diary section 4012 on the home GUI 460. Alternatively, the diary GUI 750 can be displayed by a user selecting an icon corresponding to the diary GUI 750 in the navigation bar (bottom). Specifically, the diary GUI 750 shown in FIG. 7J is similar to the diary GUI 700, except that it does not include a notification button. In accordance with another aspect of this embodiment, the diary GUI 750 differs from the diary GUI 700 in that each meal (food) entry includes a portion indicator 751 indicating a relative meal portion size (e.g., "S" for small meal, "M" for medium meal, "L" for large meal) instead of a numerical value indicating the analyte level variability associated with the meal.

[0260] Additionally, when a user selects an information button 7502 in the diary GUI 750, context information 7514 (FIG. 7K) may be provided. In some embodiments, the context information 7514 may include a references link 752. When a user selects the references link 752, a references GUI 760 (FIG. 7L) is output that includes references (sources) related to the context information 7514.

[0261] 7M, there is shown an exemplary embodiment of a filter GUI 770 of the diary GUI 750. The filter GUI 770 is similar to the filter GUI 720 of the diary GUI 700.

[0262] Additionally, Figures 7N-7R illustrate exemplary embodiments of various pop-up modal displays 761, 762, 763, 764, 765, respectively, that provide detailed information about a particular meal (food) entry. Specifically, the pop-up modal displays 761, 762, 763, 764, 765 shown in Figures 7N-7R can be displayed on the meal monitoring application when a user selects a graphical representation on the diary GUI 750. For example, as shown in Figure 7N, the pop-up modal display 761 includes a graphical representation and a textual notation that the meal entry is "low load" (green) in close proximity to each other. The textual notation includes the analyte level variance value for the meal entry (e.g., 2.2 mmol / L) followed by an explanation of how the analyte level variance value was calculated (e.g., using the glucose value at the time the food was entered and the highest glucose value in the following two hours). Similarly, pop-up modal display 762 (FIG. 7O) is associated with a meal entry that is a “medium load” (yellow) and is accompanied by text to that effect, and pop-up modal display 763 (FIG. 7P) is associated with a meal entry that is a “high load” (orange) and is accompanied by text to that effect.

[0263] According to another aspect of some embodiments, as shown in FIG. 7Q, a pop-up modal display 764 shows a graphical representation of the meal entry being "unloaded" (all gray) and a corresponding textual notation. The textual notation indicates that the meal entry has an analyte level fluctuation value that is less than zero (e.g., -0.8 mmol / L). In some embodiments, when a meal (food) entry that is not yet associated with received analyte data is selected, the meal monitoring application may display a notification 765 (as shown in FIG. 7R) informing the user that glucose data is not available for that entry and reminding the user to scan the sensor once every 8 hours.

[0264] Example embodiment of Trends GUI 8A-8D, further exemplary embodiments of the trends GUI and associated functionality of a meal monitoring application are shown. In many embodiments, the trends GUI 800 can be displayed when a user selects the trends section 406 on the home GUI 400 (FIG. 4A-1). Alternatively, the trends GUI 800 can be displayed by a user selecting an icon corresponding to the trends GUI 800 in the navigation bar (bottom). Additionally, the trends GUI 800 can include an information button 802 (FIG. 8A) to provide context information 816 (FIG. 8B) and a notification button 804 (FIG. 8A) to provide the user with an in-app notification (FIG. 4O).

[0265] According to an aspect of some embodiments, the trends GUI 800 can display dietary trends in a user-friendly and easy-to-understand manner. In some embodiments, for example, the trends GUI 800 can include multiple views in which trends can be displayed. For example, as shown in FIG. 8A, when the "Glucose Load" option 806 is selected, the trends GUI 800 can display trend information related to test substance response. Similarly, as shown in FIG. 8C, when the "Diet" option 818 is selected, the trends GUI 800 can display trend information related to diet (food).

[0266] 8A, which is an illustration of a "Glucose Load" trend view, weekly and monthly trend information may also be presented as indicated by time period option 808. Additionally, in some embodiments, the trends GUI 800 may include a date changer 810 that allows a user to select different time periods. According to one aspect of some embodiments, the presented trend information is automatically changed (updated) as the user changes the selected time period.

[0267] In many embodiments, the trend GUI 800 further includes a graphical representation 812. The graphical representation 812 provides an easy-to-understand depiction of the "glycemic load" that the user's food choices for a selected time period have had on test substance levels. For example, the graphical representation 812 shown in FIG. 8A shows that, for example, 53% of the user's food entries for the month of September 23 to October 22 were classified as "low load" (e.g., shown by green segments). Similarly, the graphical representation 812 shown in FIG. 8A shows that 33% of the user's food entries for the same period were classified as "medium load" (e.g., shown by yellow segments). Also, about 13% of the user's food entries for the same period were classified as "high load" (e.g., shown by orange segments). As shown in Figure 8A, the color of each segment indicates the range of analyte level variation values ​​(e.g., as described above with respect to Figures 4A-3a-4b), and the percentage of the area of ​​each segment relative to the total area of ​​the graphical representation indicates the frequency of the corresponding analyte level variation values. Note that while Figure 8A shows the graphical representation 812 as a "pie chart" as shown, one of ordinary skill in the art will recognize that other types of graphs (e.g., bar graphs, line graphs, etc.), color schemes (e.g., red, yellow, green, etc.), and numbers of segments (e.g., three, four, five, six, etc.) can be employed and are fully within the scope of the present disclosure.

[0268] According to another aspect of some embodiments, the trends GUI 800 may also include a summary panel 814. The summary panel 814 may show an overall evaluation of the user's food choices. For example, the summary panel 814 of FIG. 8A may state that the user's "food choices resulted in a 36% decrease in foods categorized as green."

[0269] Turning now to FIG. 8C, a trend GUI 800 is shown with the meal view option 818 selected. According to an aspect of some embodiments, the meal view can include a meal list 822. The meal list 822 displays the name of each meal, along with a graphical and numerical representation of the analyte level change, and the corresponding date and time. In some embodiments, a search bar 820 can be provided to allow the user to identify specific meals within a selected time period. In some embodiments, a voice recognition function can be provided to allow the user to speak the meal name instead of manually entering it into the search bar 820. Additionally, according to some embodiments, a filter button 824 can be provided to allow the user to filter the trend information for viewing in various useful views. For example, in some embodiments, selecting the filter button 824 can display a filter setting GUI 840. The filter setting GUI 840 can include a meal type filter 826, a sugar level impact filter 828, a date range filter 830, or any combination thereof.

[0270] 8E-8H show further exemplary embodiments of the trends GUI and trend GUI related features used in a diet monitoring application. In many embodiments, the trends GUI 850 can be displayed when a user selects the trends section 4006 on the home GUI 460 (FIG. 4A-3a). Alternatively, the trends GUI 850 can be displayed by a user selecting an icon corresponding to the trends GUI 850 in the navigation bar (bottom). The trends GUI 850 shown in FIGS. 8E-8H is similar to the trends GUI 800 shown in FIGS. 8A-8D, except that it does not include a notification button. FIG. 8E shows the trends GUI 850 with the "Glucose Load" option 8506 selected to display trend information regarding test substance response. FIG. 8F shows the context information 8516 that is displayed when a user selects the information button 8502 on the trends GUI 850. Additionally, FIG. 8G shows the trends GUI 850 with the "Meals" option 8518 selected to display trend information regarding meals (food). Figure 8H illustrates a filter setting GUI 870 that is displayed when a user selects the filter button 8524 (Figure 8G). As shown in Figure 8H, the filter setting GUI 870 can include a meal type filter 8526, a glycemic load filter 8528, a date range filter 8530, or any combination thereof.

[0271] Example embodiment of the report GUI 9A-9F, an exemplary embodiment of a report GUI 900 of a meal monitoring application is shown. With reference to FIGS. 9A and 9B, in many embodiments, the report GUI 900 is displayed when a user selects the report section 414 on the home GUI 400 (FIG. 4A-1). Alternatively, the report GUI 900 can be displayed by a user selecting an icon corresponding to the report GUI 900 in the navigation bar (bottom). Additionally, the report GUI 900 can include an information button 902 (FIG. 9A) to provide context information 912 (FIG. 9B) and a notification button 904 (FIG. 9A) to provide an in-app notification (FIG. 4O) to the user.

[0272] According to an aspect of the embodiments, the report GUI 900 may include a date range field 906 and a glucose load option 908. The date range field 906 allows a user to select a date range for the report. The glucose load option 908 allows a user to view a report for a meal (food) entry with a particular analyte level variability rank (e.g., "low load," "medium load," "high load"). The report GUI 900 may include a "Generate Report" button 910 that the user may select after completing the selection of the desired settings.

[0273] 9C-9E show further exemplary embodiments of a report GUI 930 for use in a meal monitoring application. In many embodiments, the report GUI 930 can be displayed when a user selects the report section 4014 on the home GUI 460. Alternatively, the report GUI 930 can be displayed by a user selecting an icon corresponding to the report GUI 930 in the navigation bar (bottom). Specifically, the report GUI 930 is similar to the report GUI 900, except that the report GUI 930 does not include a notification button. Additionally, as shown in FIG. 9C, the report GUI 930 includes a "Clear All" button 931. By selecting this button, the user can clear all inputs made to the report GUI 930. FIG. 9E shows the context information 9312 that is displayed when a user clicks the information button 9302 of the report GUI 930.

[0274] Turning now to FIG. 9F, an exemplary embodiment of a report 920 generated by the dietary monitoring application is shown. According to some embodiments, the report 920 may be generated in a PDF file, allowing a user to easily print the report or attach the report to an email to send to a healthcare provider. In other embodiments, the report 920 may be generated in a Word document (.doc) file, an Excel spreadsheet, or a CSV file. In some embodiments, the report 920 may be in any other desired format, such as an in-app report or a WebView. As shown in FIG. 9F, the report 920 may include a date and time field 922, a food field 924, an activity field 926, a glucose load field 928, a portion size field 930, and a notes field 932. However, one of ordinary skill in the art will appreciate that these fields are merely exemplary and that other fields, measurements, values, text fields, and options described herein may be displayed in the report 920.

[0275] Exemplary embodiments of an on-boarding method and associated GUI Next, exemplary embodiments of a method for onboarding a user to a meal monitoring application and various associated GUIs and functions are described. Turning first to FIG. 10, a method 1000 for onboarding a user to any of the meal monitoring application embodiments of the present disclosure is shown. It should be noted at the outset that those skilled in the art will appreciate that the onboarding method and associated GUIs can be software installed in the non-transitory memory of any of the viewing device 120 (e.g., smartphone), drug delivery device 160, and local computer system 170 embodiments described herein.

[0276] Referring to FIG. 10, in step 1002, the meal monitoring application is launched. However, it may be prudent to allow the user to proceed only after ensuring that the requirements for fully utilizing the meal monitoring application are met. In step 1004, the user receives a prompt asking whether or not they have a user account. In some embodiments, the user account may be an account for establishing authentication with a trusted computer system, which may then provide the meal monitoring application with the user's analyte data. If the user does not have an account, in step 1006, the meal monitoring application may prompt the user to register an account. In some embodiments, if the user declines to register an account, the meal monitoring application may be terminated. In other embodiments, if the user declines to register an account, the meal monitoring application may enter a "non-federated" mode. In this mode, the meal monitoring application may be used by the user as an unfederated food diary to manually enter meal-related information.

[0277] If the user has registered for an account or already has an account, the user successfully logs into the account at step 1010. The meal monitoring application then queries whether the user is wearing an active sensor control device at step 1012. In some embodiments, if the user does not have a sensor control device, the meal monitoring application may display an interface configured to allow the user to order a sensor at step 1014. At step 1016, the meal monitoring application may exit or switch to a "non-integrated" mode.

[0278] If the user is wearing an active sensor control device, the meal monitoring application queries whether the user has installed the sensor app, step 1018. If the user has not yet installed the sensor app, the meal monitoring application may prompt the user to download the sensor app, step 1020. In some embodiments, for example, the meal monitoring application may automatically open the sensor app's page in the "app store."

[0279] According to many embodiments, once it is determined that the requirements are met, the meal monitoring application may launch at step 1022 and display the home GUI shown in FIGS. 4A-1 through 4A-7.

[0280] 11A-1-11N-3 show example embodiments of onboarding GUIs for a meal monitoring application. Any of the onboarding GUIs shown in FIG. 11A-1-11N-3 can be combined with the embodiments described herein. In some embodiments, when the meal monitoring application is launched for the first time (as described in the description of step 1002 of FIG. 10), the GUIs 1100, 1105, 1110 (FIG. 11A-1-11A-3) can provide the user with a brief introduction to the meal monitoring application.

[0281] 11B-1 through 11B-6 illustrate further exemplary embodiments of onboarding GUIs for use with the meal monitoring application. Specifically, FIG. 11B-1 through FIG. 11B-6 illustrate onboarding GUIs 1101, 1102, 1103, 1111, 1112, and 1113, respectively, that can provide a user with a brief introduction to the meal monitoring application after launching the application for the first time.

[0282] Additionally, FIGS. 11C-1 and 11C-2 show language selection screens 1116 and 1117, respectively, which may be utilized to change the language the user desires for the food monitoring application. The onboarding GUI 1118 shown in FIG. 11C-3 is similar to the onboarding GUI 1101 shown in FIG. 11B-1, except that it is configured to display content in Swedish.

[0283] Next, onboarding GUIs 1115, 1120, 1125, and 1130 (FIGS. 11D-1 to 11D-4) can be used to register the user and create a new account. In another embodiment, onboarding GUIs 1121, 1122, 1123, 1124, 1126, and 1127 (FIGS. 11E-1 to 11E-10) can be used to register the user and create a new account.

[0284] If an account has already been created, the GUIs 1130, 1135, 1140 (FIGS. 11F-1-11F-3) may be utilized to log the user in. In some embodiments, the meal monitoring application requests permission to track the user's activity across other applications and websites by displaying a pop-up modal display 1131 on the onboarding GUI 1126 or a pop-up modal display 1132 on the onboarding GUI 1140, as shown in FIGS. 11G-1 and 11G-2.

[0285] An onboarding GUI 1145 (FIG. 11H-1) may then walk the user through the requirements of the meal monitoring application. For example, an onboarding GUI 1150 (FIG. 11H-2) may ask the user if they have a sensor control device. In some cases, the GUI 1150 may also include a link or button that allows the user to order a sensor if they do not already have one. An onboarding GUI 1155 (FIG. 11H-3) may ask the user if they have the sensor app installed.

[0286] In other embodiments, the onboarding GUI 1133 (FIG. 11I-1) may explain the requirements of the meal monitoring application to the user. For example, the onboarding GUI 1134 (FIG. 11I-2) may ask the user if they have a sensor control device. In some cases, the onboarding GUI 1134 may also include a link or button 1138 that allows the user to order a sensor if the user does not already have a sensor. The onboarding GUI 1136 (FIG. 11I-3) may ask the user if they have installed the sensor app. In some embodiments, a pop-up modal display 1137 may be displayed on the onboarding GUI 1133, as shown in FIG. 11I-4. In particular, the pop-up modal display 1137 may provide information regarding notifications. For example, the pop-up modal display 1137 may inform the user that the meal monitoring application would like to send notifications to the user. Additionally, according to an aspect of the embodiments, the pop-up modal display 1137 may include a "Don't Allow" button 1141 and an "Allow" button 1142. By selecting these buttons, the user can configure the notification. Note that this example is merely illustrative, and one of ordinary skill in the art will appreciate that other combinations and sequences of modal presentations can be used and are fully within the scope of the present disclosure.

[0287] According to another aspect of the embodiments, onboarding GUIs 1160, 1165, 1170 (FIGS. 11J-1-11J-3) may be displayed to inform the user that all requirements have been met (e.g., onboarding GUI 1160) or that one or more requirements have not been met (e.g., onboarding GUI 1165, 1170). In some embodiments, onboarding GUIs 1171, 1172, 1173, 1174 (FIGS. 11K-1-11K-4) may also be displayed to inform the user that all requirements have been met (e.g., onboarding GUI 1171) or that one or more requirements have not been met (e.g., onboarding GUI 1172, 1173, 1174).

[0288] According to another aspect of some embodiments, in addition to the onboarding GUIs described above, tutorial GUIs 1175, 1180, 1185, 1190 (FIGS. 11L-1-11L-4) may also be optionally displayed to the user after the onboarding process is completed. In some embodiments, tutorial GUIs 1191, 1192, 1193, 1194, 1195, 1196 (FIGS. 11M-1-11M-6) may also be optionally displayed to the user on the food monitoring application after the onboarding process is completed. In addition, in some embodiments, food tutorial GUIs 1197, 1198, 1199 (FIGS. 11N-1-11N-3) may also be optionally displayed to the user.

[0289] Example Embodiments of the Challenge GUI and Related Functionality 12A-12K, an exemplary embodiment of a challenge GUI of a dietary monitoring application is shown. Referring to FIG. 12A, a challenge list GUI 1200 (sometimes referred to herein as a "first challenge GUI") is displayed. The challenge list GUI 1200 may be displayed when a user selects a "see all" link 4304 on a challenge card in the home GUI 460 (as shown in FIG. 4A-3a-4A-4b). According to some embodiments, as shown in FIG. 12A, the challenge list GUI 1200 lists one or more challenges related to the user's test substance response, including an ongoing challenge card 1201 (sometimes referred to herein as a "first challenge card"), a completed challenge card 1202 (sometimes referred to herein as a "second challenge card"), and an unattended challenge card 1203 (sometimes referred to herein as a "third challenge card").

[0290] Specifically, the in-progress challenge card 1201 may include one or more challenge icons 1211 that indicate an ongoing challenge (one that the user is currently working on). In this regard, the in-progress challenge card 1201 lists ongoing challenges (one of the food monitoring application in which the user is currently participating). The challenge icon 1211 may include an image 1212 and a challenge name 1213, which is a textual description of the purpose of the challenge represented by the challenge icon 1211. In some embodiments, as shown in FIG. 12A, a mark 1214 indicating that a challenge is in progress (e.g., a small green circle) may be displayed on the image 1212 of the challenge icon 1211 to indicate that the challenge represented by the challenge icon 1211 is in progress (one that the user is currently working on). It will be appreciated by those skilled in the art that various other marks may be used in the challenge GUI described herein as the mark 1214 indicating that a challenge is in progress, and that such marks are also fully within the scope of the present disclosure.

[0291] Further, the ongoing challenge card 1201 may include multiple challenge icons 1211. In some embodiments, the ongoing challenge card 1201 may display two or three challenge icons 1211. In some embodiments, the ongoing challenge card 1201 may include multiple challenge icons 1211, and the ongoing challenge card 1201 may include more challenge icons 1211 than can be displayed on the challenge list GUI 1200 at any given time. In some embodiments, the ongoing challenge card 1201 may be configured to respond to received user input (e.g., by a swipe, scroll, drag, or other predetermined action), and in response to such user input, may display a new set of challenge icons 1211 that were not previously displayed on the challenge list GUI 1200. For example, the ongoing challenge card 1201 may display a new set of challenge icons 1211 in response to received input. In some embodiments, at least one challenge icon 1211 of the new challenge icon set displayed on the challenge card 1201 during the challenge is different from at least one challenge icon 1211 of the original challenge icon set before user input was received.

[0292] According to another aspect of the embodiments, the challenge list GUI 1200 further includes a completed challenge card 1202. The completed challenge card 1202 includes one or more challenge icons 1211 representing challenges that the user has completed or that the user has previously participated in. In this regard, the completed challenge card 1202 lists the completed challenges of the food monitoring application. The challenge icon 1211 can include an image 1212 and a challenge name 1213, which is a textual description of the purpose of the challenge represented by the challenge icon 1211. In some embodiments, a participation indicator 1215 (e.g., a colored check mark, such as the green check mark shown in FIG. 12A) can be displayed over the image of the challenge icon 1211 to indicate that the challenge represented by the challenge icon 1211 is a challenge that the user has previously participated (completed). It will be appreciated by those skilled in the art that various other participation indicators can be used in the challenge GUI described herein and are fully within the scope of the present disclosure.

[0293] In some embodiments, the completed challenge card 1202 may display two or three challenge icons 1211. In some embodiments, the completed challenge card 1202 may include multiple challenge icons 1211, and the completed challenge card 1202 may include more challenge icons 1211 than can be displayed in the challenge overview GUI 1200 at any given time. In some embodiments, the completed challenge card 1202 may be configured to respond to received user input (e.g., via a swipe, scroll, drag, or other predetermined action) and, in response to such user input, may display a new set of challenge icons 1211 that were not previously displayed on the challenge overview GUI 1200. In some exemplary embodiments, the completed challenge card 1202 may display a new set of challenge icons 1211 in response to received input. In some embodiments, at least one challenge icon 1211 of the new challenge icon set displayed on the completed challenge card 1202 is different from at least one challenge icon 1211 of the original challenge icon set before receiving the user input.

[0294] Additionally, in some embodiments, the challenge list GUI 1200 includes an unattempted challenge card 1203. The unattempted challenge card 1203 includes one or more challenge icons 1211 that represent challenges that the user has not yet attempted (participated in). The challenge icon 1211 may include an image 1212 and a challenge name 1213, which is a textual description of the purpose of the challenge that the challenge icon 1211 represents.

[0295] In some embodiments, the unattempted challenge card 1203 may display two or three challenge icons 1211. In some embodiments, the unattempted challenge card 1203 may include multiple challenge icons 1211, and the unattempted challenge card 1203 may include more challenge icons 1211 than can be displayed in the challenge list GUI 1200 at any given time. In some embodiments, the unattempted challenge card 1203 may be configured to respond to received user input (e.g., by swiping, scrolling, dragging, or other predetermined actions) and, in response to such user input, may display (enter) additional or alternative challenge icons 1211 that were not previously displayed on the challenge list GUI 1200. In response to the received input, the unattempted challenge card 1203 may display a new set of challenge icons 1211. In some embodiments, at least one challenge icon 1211 in the new challenge icon set is different from at least one challenge icon 1211 in the original challenge icon set before receiving the user input.

[0296] FIG. 12B illustrates a challenge information GUI 1210 (sometimes referred to herein as a “second challenge GUI”) for an unattempted challenge (e.g., a “5 items a day” challenge). Specifically, when a challenge icon 1211 of an unattempted challenge card 1203 in the challenge list GUI 1200 is selected, a challenge information GUI 1210 for the corresponding unattempted challenge is displayed. In some embodiments, the challenge information GUI 1210 includes a challenge summary section 1225 that includes a challenge icon 1221 with an image 1222 and a challenge name 1223 that shows a textual representation of the unattempted challenge. In some embodiments, the challenge information GUI 1210 also provides context information 1228 about the challenge. For example, the unattempted challenge depicted in the challenge information GUI 1210 of FIG. 12B is a challenge about eating vegetables and fruits, and thus the context information 1228 includes a description of the challenge as well as a contextual description that supports the importance of consuming vegetables and fruits.

[0297] Additionally, the challenge information GUI 1210 may include an effort indicator 1226. The effort indicator 1226 may be adjacent to a date stamp indicating when the challenge was last attempted. In some embodiments, if the challenge has not been attempted before, no date stamp is displayed adjacent to the effort indicator 1226. The challenge information GUI 1210 may also include an achievement indicator 1227. The achievement indicator 1227 may be adjacent to a date stamp indicating when the challenge was last successfully completed. In some embodiments, if the challenge has not been attempted before, no date stamp is displayed adjacent to the achievement indicator 1227 (see, e.g., FIG. 12B).

[0298] In some embodiments, the challenge information GUI 1210 includes a start button 1229. When the user selects the start button 1229, the challenge can be started. Although not shown, when a challenge is started, the corresponding challenge icon 1211 is no longer displayed on the unattempted challenge card 1203 of the challenge list GUI 1200. Instead, the challenge icon 1211 is displayed on the challenge being attempted card 1201 of the challenge list GUI 1200 to indicate that the challenge is being performed (attempted). In some embodiments, when the user selects the start button 1229 (FIG. 12B), the challenge is started immediately. In some embodiments, the challenge is not started until the next day. For example, the meal monitoring application is configured to start the selected challenge the next day if the challenge the user is trying to start is related to breakfast and the user started the challenge in the afternoon. According to an aspect of some embodiments, the user can work on multiple challenges at the same time. In some embodiments, the user can start two challenges at the same time.

[0299] FIG. 12C illustrates a challenge information GUI 1220 for an ongoing challenge (e.g., a “Fizzy Drink” challenge that encourages users to choose less sugary drinks instead of sugary drinks). In some examples, the “Fizzy Drink” challenge can be output (prompted) to users who have consumed one or more sugary drinks, such as sugary drinks, within a predetermined period of time, or a threshold number of such drinks. The challenge information GUI 1220 for an ongoing challenge is similar to the challenge information GUI 1210 for a challenge that has not yet been started, except that it includes a stop button 1339 instead of a start button. In this regard, a user can stop the continuation of each challenge by selecting the stop button 1339. Additionally, the challenge icon 1231 shown on the challenge information GUI 1220 for an ongoing challenge includes a mark 1232 (e.g., a small green circle) on the icon image 1233 to indicate that the challenge is in an ongoing state. In some embodiments, the challenge information GUI 1220 for the ongoing challenge further includes a progress card 1235. The progress card 1235 indicates the progress the user has made with the challenge. According to one aspect of the embodiments, the progress card 1235 includes a unit of measure and a unit of time to indicate the progress. For example, if the challenge requires 7 days to complete, the progress card can indicate the number of days the user has completed so far. Additionally, the progress card can indicate the progress in minutes (e.g., "0 / 7" indicates that the user has completed 0 days out of 7 days so far). However, one skilled in the art will appreciate that other units of measure, time units, or both, including but not limited to hours, weeks, and percentages, can be employed and are fully within the scope of the present disclosure.

[0300] FIG. 12D illustrates another exemplary embodiment of a challenge information GUI for an ongoing challenge. According to an aspect of the embodiments, a modal display 1236 may be displayed above the challenge information GUI 1230 for the ongoing challenge. The modal display 1236 may be configured to prompt the user to provide progress information regarding the ongoing challenge that the user is currently working on. For example, as shown in FIG. 12D, if the ongoing challenge requires the user to consume 5 servings of vegetables or fruits per day, the modal display 1236 may ask the user if the challenge is complete. The modal display 1236 may include a "yes" button 1237 and a "no" button 1238, which may be selected by the user to indicate a response to the prompt displayed by the modal display 1236. In some embodiments, the user is prompted daily to respond to the modal display 1236 for a particular challenge to report and track progress for that challenge.

[0301] FIG. 12E illustrates a challenge GUI 1240 (sometimes referred to herein as a “third challenge GUI”). The challenge GUI 1240 is displayed to the user when the user has successfully completed the challenge or has indicated that the user has. For example, the challenge GUI 1240 illustrated in FIG. 12E may be displayed in response to the user selecting the “Yes” button 1237 on the modal display 1236. According to an aspect of the embodiments, the challenge GUI 1240 may include an effort indicator 1246, an achievement indicator 1247, a challenge icon 1241 including an image 1242 representing the completed challenge and a challenge name 1243, and a congratulatory message 1245 informing the user that the challenge has been successfully completed. Additionally, a participation indicator 1247 (e.g., a green check mark) may be displayed over the image 1242 of the challenge icon 1241 to indicate that the challenge indicated by the challenge icon 1241 is a challenge that the user has completed. Additionally, in some embodiments, the challenge GUI 1240 may also include a "Try Again" button 1248 and a "Try Another Challenge" button 1249. In some embodiments, when a user selects the "Try Again" button 1248, the user may start the challenge over again. In some embodiments, when a user selects the "Try Another Challenge" button 1249, the challenge list GUI 1200 is displayed, allowing the user to select a different challenge.

[0302] In some embodiments, if the user fails to complete the challenge or if the user indicates that they have failed to complete the challenge, a challenge GUI 1250 (sometimes referred to herein as a “fourth challenge GUI”) may be displayed (FIG. 12F). For example, the challenge GUI 1250 shown in FIG. 12F may be displayed in response to a user selecting the “No” button 1238 on the modal display 1236 (FIG. 12D). According to an aspect of some embodiments, the challenge GUI 1250 may include an effort indicator 1251, an achievement indicator 1252, a challenge icon 1251 including an image 1252 representing a completed challenge and a challenge name 1253, and a message 1255 informing the user that they have not been successful in completing the challenge. In some embodiments, as shown in FIG. 12F, the message 1255 may include a word of encouragement to the user (e.g., “Try again!”). Additionally, a participation indicator 1257 (e.g., a green check mark) may be overlaid on the image 1252 of the challenge icon 1251 to indicate that the challenge represented by the challenge icon 1251 is a challenge that the user has completed. Additionally, in some embodiments, the challenge GUI 1250 may include a "Try Again" button 1258 and a "Try Another Challenge" button 1259. In some embodiments, when the user selects the "Try Again" button 1258, a modal display 1256 (FIG. 12G) is displayed on the challenge GUI to ask the user whether they want to start the challenge over again. In some embodiments, when the user selects the "Try Another Challenge" button 1259, a challenge list GUI 1200 (FIG. 12A) is displayed to allow the user to select a different challenge.

[0303] 12H-12K show further exemplary embodiments of a challenge GUI of a food monitoring application. Specifically, FIG. 12H shows a challenge information GUI 1260 for an unattempted challenge (e.g., a "4 meals in a row" challenge). Note that the challenge information GUI 1260 is similar to the challenge information GUI 1210 shown in FIG. 12B, except that the challenge icon 1271 shown in FIG. 12H does not include a mark. FIG. 12I shows the challenge information GUI 1270 that is displayed after the user begins the challenge. In this embodiment, the challenge information GUI 1270 includes (1) a challenge summary card 1275, (2) a previous progress card 1276, (3) a current progress card 1277, (4) a statistics card 1274, and (5) a stop button 1279. The challenge summary card 1275 displays the challenge icon 1271 for the challenge along with a textual representation 1278 of the challenge. The challenge icon 1271 has an image 1272 representing the challenge being displayed, and a challenge name 1273 .

[0304] In some embodiments, the current progress card 1277 may include a first progress indicator 1281 that visually indicates the progress the user is currently making toward completing the challenge. In particular, the first progress indicator 1281 may include a first graphical representation (e.g., a first plurality of circles). Each of the first plurality of circles in the first progress indicator 1281 may have a first color (e.g., green circles indicating an increase in completion). In some embodiments, the first progress indicator 1281 may use a second color (e.g., yellow circles) to indicate that the user has failed in their efforts toward completing the challenge.

[0305] Additionally, in some embodiments, as shown in FIG. 12I-K, the previous progress card 1276 may include a second progress indicator 1282 that visually indicates the progress the user has made in a previous challenge. Specifically, the second progress indicator 1282 may include a second graphical representation (e.g., a second plurality of circles). Each of the second plurality of circles in the second progress indicator 1282 may be colored with a first color (e.g., green circles indicating an increase in completion). In some embodiments, as best shown in FIG. 12J, the second progress indicator 1282 may use a second color (e.g., yellow circles) to indicate that the user failed to complete the previous challenge.

[0306] In some embodiments, if the user fails to complete the challenge, a challenge GUI 1280 is displayed (FIG. 12J). According to one aspect of the embodiments, the meal monitoring application is configured to automatically detect whether the user is on track to complete the challenge based on the meal input or analyte level variability associated with the meal input. For example, the meal monitoring application may automatically detect that the user has consumed four consecutive "green load" (low glycemic response) meals. Thus, when the meal monitoring application detects that the user has failed to consume four consecutive green load meals, the challenge GUI 1280 shown in FIG. 12J may be displayed in response.

[0307] According to an aspect of some embodiments, the challenge GUI 1280 may include a challenge summary card 1275, a previous progress card 1276, a statistics card 1278, and a message 1291 informing the user that they were not successful in completing the challenge. In some embodiments, as shown in FIG. 12J, the message 1291 may include a word of encouragement to the user (e.g., "Try again!"). Additionally, in some embodiments, the challenge GUI 1280 may include a "Try Again" button 1288 and a "Try Another Challenge" button 1289.

[0308] FIG. 12K illustrates a challenge GUI 1290 that is displayed to a user when the user successfully completes a challenge. In some exemplary embodiments, the challenge GUI 1290 illustrated in FIG. 12K may be displayed in response to a meal monitoring application automatically detecting that the user has consumed four consecutive meals of a green load. According to an aspect of the embodiments, the challenge GUI 1290 may include a challenge summary card 1275, a previous progress card 1276, a statistics card 1278, and a congratulatory message 1293 informing the user that the challenge has been successfully completed. Additionally, in some embodiments, the challenge GUI 1290 may include a "Try Again" button 1298 and a "Try Another Challenge" button 1299. In some embodiments, the user may select the "Try Again" button 1298 to allow the user to start the challenge over again.

[0309] According to an aspect of some embodiments, the statistics card 1278 is configured to indicate the number of times the user has successfully completed the challenge in the past. In some embodiments, the statistics card 1278 includes a numeric value and a textual notation indicating the number of times the challenge has been successfully completed (e.g., "0 Times" in FIGS. 12I and 12J, "1 Time" in FIG. 12K).

[0310] Exemplary embodiments of alert notifications for a meal monitoring application To help the user maintain and improve glycemic control, the meal monitoring application may also display various alerts and notifications to remind and encourage the user to log meals. In some embodiments, as shown in FIG. 13A, a meal monitoring application lock screen notification 1310 may be displayed. For example, the lock screen notification 1310 may be displayed to inform the user that a high glucose meal was detected and to prompt the user to log an item based on the detected glucose spike. Alternatively, the notification 1310 may be a congratulatory notification, for example, to inform the user that they stayed within a post-meal target range or that they have logged a certain number of meals.

[0311] In some embodiments, the food monitoring application may provide an in-app modal display 1320 to the user via the food monitoring application, as shown in FIG. 13B. In some embodiments, the in-app modal display 1320 may be configured to obscure (overlay) a portion of the interface (e.g., the home GUI 460) that is displayed underneath (FIGS. 13B and 13C). The food monitoring application may also respond by presenting an in-app modal display 1320 to remind or encourage the user when the user taps on the lock screen notification 1310. The in-app modal display 1320 may be a more powerful, visual in-application modal display that provides more context to motivate immediate action. The in-app modal display 1320 may include a possible answer that allows the user to indicate that they have not eaten anything and a possible link that the user can select to open a food logging screen to add food. An example food logging screen is described elsewhere in this application. Alternatively, the in-app modal display 1320 may be a congratulatory notice, for example with encouraging words and graphics praising the user for staying within their goal. The in-app modal display 1320 may also show graphics and text encouraging the user to log meals by reminding the user that there may be a variety of reasons for the detected glucose spike and that logging meals may help understand the cause of the glucose spike.

[0312] The in-app modal display 1320 may also display graphics and text to gently nudge the user to want to deliver a predefined message 1330. According to an aspect of embodiments, the message 1330 may be a personalized message for the user. In some embodiments, the dietary monitoring application may be configured to analyze past dietary entries, analyte level variability associated with past dietary entries, or both, to push a specific analysis-based message 1330 to the user.

[0313] In some exemplary embodiments, the in-app modal display 1320 includes a message 1330 that suggests food choices to the user based on the user's past experiences and inputs. As shown in Figure 13B, the in-app modal display 1320 includes a message 1330 that suggests salmon and roasted vegetables for dinner based on the user's past sugar levels.

[0314] According to another aspect of the embodiments, the in-app modal display 1320 may include messages 1330 relating to the following topic areas (1)-(4), including, but not limited to, (1) sensor scanning (e.g., a message prompting the user to scan the sensor before going to bed); (2) user profile (e.g., a message requesting the user to complete their user profile); (3) nutrition (e.g., a message providing nutritional tips); and (4) dietary input (e.g., messages recommending food (diet) changes, such as recommendations to substitute certain foods for other foods (e.g., chicken instead of pizza)).

[0315] In some embodiments, the in-app modal display 1320 is a gentle nudge to the user. In some embodiments, the in-app modal display 1320 is displayed when the user selects a banner notification 1310 (e.g., see FIG. 13A ) that is displayed outside of the food monitoring application. In some embodiments, the gentle nudge banner notification 1310 may be displayed outside of the food monitoring application (e.g., on the lock screen). The banner notification 1310 includes a message indicating that the food monitoring application has personalized suggestions for the user (e.g., dinner recommendations as shown in FIG. 13A ).

[0316] According to one aspect of embodiments, the in-app message sending feature of the meal monitoring application requires the user to explicitly opt-in to enable in-app messages 1330. Thus, before the meal monitoring application can enter an in-app message 1330 for the user, the user must have previously given the meal monitoring application permission to send in-app messages 1330 to the user.

[0317] It should be noted that the above examples are merely illustrative, and one of ordinary skill in the art will appreciate that other combinations and sequences of modal presentations may be used and are fully within the scope of the present disclosure.

[0318] As a summary and / or supplement to the above described several embodiments, various aspects of the present subject matter are specified below. Note that what is emphasized here is the mutual relationship and interchangeability of the following embodiments. In other words, emphasis is placed on the fact that each feature of the multiple embodiments can be combined with any other feature unless otherwise expressly described or without logical validity. Note that although no explicit reference is made below to the drawings, the description in each of the following paragraphs is a reprint and development of each of the embodiments described in this specification.

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

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

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

[0322] In this specification, an entity is often described as being coupled to a different entity. In this specification, the terms "coupled," "associated," and "connected" (or any variation thereof) are used interchangeably and should be understood as generic terms that refer to a direct coupling of two entities (without significant (e.g., parasitic) intervening entities) and an indirect coupling of two entities (with one or more intervening entities that are significant). When entities are shown as being directly coupled together, or when entities are described as being coupled together without any intervening entities, it should be understood that the entities may also be indirectly coupled together unless the context clearly indicates otherwise.

[0323] The subject matter of the present disclosure has been described in sufficient detail and distinctly in the specification and accompanying drawings to permit means-plus-function claims, as provided for in 35 U.S.C. §112(f), to be included at any time within the scope of the claims, but only those claims which expressly recite the phrase "means for" should be construed as having such means-plus-function format.

[0324] Aspects of the invention are set out in the independent claims and preferred features are set out in the dependent claims. Preferred features set out in the dependent claims may be used in any combination in one embodiment and preferred features of one aspect may also be used in combination with other aspects.

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

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

[0327] Although the embodiments are susceptible to various modifications and variations, specific examples thereof are shown in the drawings and described in detail herein. These embodiments are not limited to the particular forms disclosed, but on the contrary, these embodiments include all modifications, equivalents, and alternatives that do not depart from the spirit of the invention. These embodiments are not limited to the particular forms disclosed, but on the contrary, these embodiments include all modifications, equivalents, and alternatives that do not depart from the spirit of the invention.

[0328] Itemized Description Exemplary embodiments are described below in numbered sections.

[0329] Section 1 1. A system for monitoring a diet-related test substance response of a user, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level of the user; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: outputting a first challenge graphical user interface (GUI) representative of a list of one or more challenges related to the user's test substance response; Run the command, the one or more challenges include one or more ongoing challenges, one or more completed challenges, and one or more unattempted challenges; the first challenge GUI includes a first challenge card, a second challenge card, and a third challenge card; the first challenge card represents the one or more active challenges, each of the one or more active challenges representing a challenge currently being engaged by the user on the meal monitoring application; the second challenge card represents the one or more completed challenges, each of the one or more completed challenges representing a challenge completed by the user; The system, wherein the third challenge card represents one or more unattempted challenges, each of the one or more unattempted challenges representing a challenge that the user has not yet participated in.

[0330] Section 2 the first challenge card includes one or more selectable first challenge icons; 2. The system of claim 1, wherein each of the one or more selectable first challenge icons represents a challenge that the user is currently working on.

[0331] Section 3 each of the one or more selectable first challenge icons includes a first indicia and an image and a textual representation of the currently active challenge; 3. The system of claim 2, wherein the first indicia is displayed on the image and configured to indicate that the challenge is currently being undertaken.

[0332] Section 4 4. The system of claim 3, wherein the first indicia is a small green circle.

[0333] Section 5 the second challenge card includes one or more selectable second challenge icons; The system of any one of claims 1 to 4, wherein each of the one or more selectable second challenge icons represents a challenge that the user has completed.

[0334] Section 6 each of the one or more selectable second challenge icons includes a second indicia and an image and a text representation of the completed challenge; 6. The system of claim 5, wherein the second indicia is configured to be overlaid on the image to indicate that the challenge has been completed by the user.

[0335] Section 7 7. The system of claim 6, wherein the second indicia is a colored check mark.

[0336] Section 8 the third challenge card includes one or more selectable third challenge icons; The system of any one of claims 1 to 7, wherein each of the one or more selectable third challenge icons represents a challenge that the user has not yet attempted.

[0337] Section 9 9. The system of claim 8, wherein each of the one or more selectable third challenge icons includes an image and a textual representation of the unattempted challenge.

[0338] Section 10 each of the first challenge card, the second challenge card, and the third challenge card includes a plurality of selectable challenge icons; displaying a first set of selectable challenge icons from the plurality of selectable challenge icons on the first challenge GUI; the viewing device further includes a touch screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving an input corresponding to a swipe or drag operation from the touch panel screen; displaying a second set of selectable challenge icons from the plurality of selectable challenge icons on the first challenge GUI in response to the received input; Then, The system described in any one of claims 1 to 9, wherein at least one of the plurality of selectable challenge icons of the second set is different from at least one of the plurality of selectable challenge icons of the first set.

[0339] Section 11 the one or more challenge listings include one or more selectable challenge icons; each of the one or more selectable challenge icons corresponds to one of the one or more challenges related to the user's test substance response or glucose level; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to a selection of a challenge icon of the one or more selectable challenge icons, outputting a second challenge GUI representing context information regarding a challenge of the one or more challenges that corresponds to the selected challenge icon of the one or more selectable challenge icons. The system according to any one of claims 1 to 10, further comprising:

[0340] Section 12 The second challenge GUI, a challenge summary section including the selected one of the one or more selectable challenge icons, an image, and a challenge name, the challenge name being a text representation of the one of the one or more challenges that corresponds to the selected one of the one or more selectable challenge icons; an effort indicator configured to indicate when the user last attempted one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons; an achievement indicator configured to indicate when the user last succeeded in completing one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons; 12. The system of claim 11, comprising:

[0341] Section 13 When the one challenge corresponding to the selected one of the one or more selectable challenge icons among the one or more challenges is an unattempted challenge, the second challenge GUI further includes a start button; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to the start button being selected, starting the unattempted challenge in the meal monitoring application. 13. The system according to claim 11 or 12, further comprising:

[0342] Section 14 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: responsive to the start button being selected, starting the unattempted challenge in the meal monitoring application the following day. 14. The system according to claim 13, further comprising:

[0343] Section 15 When the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an ongoing challenge, the second challenge GUI further includes a stop button; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: responsive to the stop button being selected, stopping the ongoing challenge from continuing. 13. The system according to claim 11 or 12, further comprising:

[0344] Section 16 When the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an ongoing challenge, the second challenge GUI further includes a progress card configured to show a progress of the ongoing challenge accumulated by a user; 13. The system of claim 11 or 12, wherein the progress card includes units of measure and units of time for indicating the progress.

[0345] Section 17 the units of measure include fractional units; 17. The system of claim 16, wherein the time units include days.

[0346] Section 18 a modal display is displayed on the second challenge GUI when the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an active challenge; 13. The system of claim 11 or 12, wherein the modal display is configured to prompt the user to provide progress information regarding the ongoing challenge in the meal monitoring application.

[0347] Section 19 the meal monitoring application is configured to detect whether the user has been successful in completing the ongoing challenge based on tracking progress; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: and when the meal monitoring application detects that the user has successfully completed the ongoing challenge, responsively outputting a third challenge GUI including a challenge summary section, an effort indicator, an achievement indicator, and a message congratulating the user on successfully completing the ongoing challenge. and, in response to the meal monitoring application detecting that the user has successfully completed the ongoing challenge, identifying the ongoing challenge as a completed challenge; Then, the third challenge GUI further includes a first button, the first button configured to restart the completed challenge when the user selects the first button; 20. The system of claim 18, wherein the third challenge GUI further includes a second button that, when the user selects the second button, outputs the first challenge GUI and allows the user to select a different challenge from the list of one or more challenges represented by the first challenge GUI.

[0348] Section 20 in response to the user selecting the first button, a modal display is displayed over the third challenge GUI; 20. The system of claim 19, wherein the modal display is configured to prompt the user to confirm whether the user wants to start the completed challenge over again.

[0349] Section 21 the meal monitoring application is configured to detect whether the user has been successful in completing the ongoing challenge based on tracking progress; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: and if the meal monitoring application detects that the user has not been successful in completing the ongoing challenge, responsively outputting a fourth challenge GUI including a challenge summary section, an effort indicator, a completion indicator, and a message informing the user that they have not been successful in completing the ongoing challenge. if the meal monitoring application detects that the ongoing challenge has not been successfully completed, in response, identifying the ongoing challenge as a completed challenge; Then, the fourth challenge GUI further includes a first button, the first button configured to restart the completed challenge when the user selects the first button; 20. The system of claim 18, wherein the fourth challenge GUI further includes a second button that, when the user selects the second button, outputs the first challenge GUI and allows the user to select a different challenge from the list of one or more challenges represented by the first challenge GUI.

[0350] Section 22 in response to the user selecting the first button, a modal display is displayed over the fourth challenge GUI; 22. The system of claim 21, wherein the modal display is configured to prompt the user to confirm whether the user wants to start the completed challenge over again.

[0351] Section 23 the meal monitoring application includes a home GUI including a challenge card; the challenge card includes a selectable link; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: outputting the first challenge GUI in response to the user selecting the link; The system according to any one of claims 1 to 22, further comprising:

[0352] Section 24 A system described in any one of claims 1 to 23, wherein each of the one or more challenges is configured to represent a challenge regarding the user's behavior or activity that may affect the user's test substance level.

[0353] Section 25 1. A system for monitoring a diet-related test substance response of a user, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level of the user; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving meal information input by the user, the meal information configured to represent food choices of the user; outputting a home graphical user interface (GUI); Run the command, The home GUI: a plurality of selectable sections, including a user profile section, a meal entry section, a trends section, a diary section, and a reports section; a meal card configured to display one or more meal lists including the entered meal information for one or more meals consumed by the user; a trend card including a graphical representation depicting information regarding analyte responses associated with the user's food choices; a challenge card presenting a list of one or more challenges related to the user's test substance response or glucose level; a recommendation card presenting one or more recommendations regarding the user's food choices or test substance responses.

[0354] Section 26 the recommendation card includes one or more selectable recommendation icons; 26. The system of claim 25, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations.

[0355] Section 27 27. The system of claim 26, wherein each of the one or more selectable recommendation icons includes an image for a corresponding one of the one or more recommendations and a recommendation name that is a text representation of the corresponding one of the one or more recommendations.

[0356] Section 28 the recommendation card includes a plurality of selectable recommendation icons; a first set of selectable recommendation icons from the plurality of selectable recommendation icons is displayed on the recommendation card; the viewing device further includes a touch screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving an input corresponding to a swipe operation or a drag operation from the touch panel screen; displaying a second set of selectable recommendation icons from the plurality of selectable recommendation icons on the recommendation card in response to the received input; Then, The system of any one of claims 25 to 27, wherein at least one of the plurality of selectable recommendation icons of the second set is different from at least one of the plurality of selectable recommendation icons of the first set.

[0357] Section 29 the recommendation card includes one or more selectable recommendation icons; each of the one or more selectable recommendation icons corresponds to a recommendation of the one or more recommendations; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to a selection of a recommendation icon among the one or more selectable recommendation icons, outputting a modal display on the home GUI. Then, the modal presentation provides contextual information regarding the corresponding one of the one or more recommendations; 29. The system of any one of claims 25 to 28, wherein the modal display is configured to instruct the user to act on the corresponding one of the one or more recommendations.

[0358] Section 30 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting a food selection of the user; Analyzing the input dietary information; displaying one or more selectable recommendation icons on the recommendation card based on the analysis; Then, 30. The system according to any one of claims 25 to 29, wherein each of the one or more selectable recommendation icons represents a recommendation regarding the user's food choices or test substance reactions.

[0359] Section 31 the recommendation card includes one or more selectable recommendation icons; each of the one or more selectable recommendation icons corresponds to a recommendation of the one or more recommendations; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to a selection of one of the one or more selectable recommendation icons, deleting the selected one of the one or more selectable recommendation icons from the recommendation card; displaying a new selectable recommendation icon on the recommendation card in place of the removed recommendation icon; The system according to any one of claims 25 to 30, further comprising:

[0360] Section 32 the recommendation card includes one or more selectable recommendation icons; each of the one or more selectable recommendation icons corresponds to a recommendation of the one or more recommendations; 32. The system according to any one of claims 25 to 31, wherein each of the one or more selectable recommendation icons is configured to be displayed on the recommendation card for a predetermined period of time.

[0361] Section 33 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting when the predetermined period of time has been reached; responsively replacing the one or more selectable recommendation icons on the recommendation card with a new set of one or more selectable recommendation icons when the predetermined period is reached; Then, 33. The system of claim 32, wherein at least one of the one or more selectable recommendation icons of the new set is different from at least one of the one or more selectable recommendation icons that it replaced.

[0362] Section 34 the home GUI is configured to transition between a plurality of views; 34. The system according to any one of claims 25 to 33, wherein the plurality of views includes at least a first view and a second view.

[0363] Section 35 In the first view, the home GUI is configured to display the user profile section, the meal entry section, the diary section, and the meal card; the viewing device further includes a touch screen; When the home GUI is in the first view, when the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving an input corresponding to a scroll operation, a swipe operation, a pull operation, or a drag operation from the touch panel screen; Then, the home GUI is configured to transition from the first view to the second view in response to the received input; 35. The system of claim 34, wherein in the second view, the trend card, the challenge card, and the recommendation card are displayed on the home GUI.

[0364] Section 36 the home GUI is configured to transition between a plurality of views; each of the plurality of views is a different view; the viewing device further includes a touch screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving an input corresponding to a scroll operation, a swipe operation, a pull operation, or a drag operation from the touch panel screen; displaying a view of the plurality of views of the home GUI in response to the received input; The system according to any one of claims 25 to 35, further comprising:

[0365] Section 37 37. The system of any one of claims 25 to 36, wherein the meal card is configured to display one or more meal lists including meal information for one or more recently consumed meals.

[0366] Section 38 each entry in said one or more meal listings includes details of a meal consumed by said user; the one or more meal listings are displayed on the meal card in chronological order; 38. The system according to any one of paragraphs 25 to 37, wherein a meal item corresponding to a most recently consumed meal is displayed at the top of the meal card.

[0367] Section 39 39. The system according to any one of claims 25 to 38, wherein each item in the one or more meal listings includes details of a meal consumed by the user and a test substance response related to the meal.

[0368] Section 40 Each item in said meal list or lists: a textual representation of meals consumed by the user; a portion size indicator that indicates whether the meal size was small, medium, or large compared to the user's usual meal size; a date stamp associated with the date the user consumed the meal; and A timestamp associated with the time the meal was consumed; and a graphical representation showing the test substance response associated with the meal; The system according to any one of claims 25 to 39, comprising:

[0369] Section 41 41. The system of claim 40, wherein the graphical representation has a plurality of segments.

[0370] Section 42 The plurality of segments are a first segment indicative of said test substance response including a low blood glucose response; a second segment indicative of said test substance response including a moderate glycemic response; a third segment indicative of said test substance response including a high glycemic response; 42. The system of claim 41, comprising:

[0371] Section 43 43. The system of claim 42, wherein the first segment, the second segment, and the third segment are each a different color.

[0372] Section 44 44. The system of any one of claims 25 to 43, wherein the graphical representation of the trend card shows the test substance response associated with the user's food choices over a given period of time.

[0373] Section 45 45. The system of clause 44, wherein the graphical representation of the trend card includes a plurality of color segments including a first color segment, a second color segment, and a third color segment.

[0374] Section 46 the first color segment having a green color indicating a small glycemic response; the second color segment having a yellow color indicating a moderate glycemic response; 46. ​​The system of claim 45, wherein the third color segment has an orange color indicating a high glycemic response.

[0375] Section 47 The system of any one of claims 25 to 40, wherein the trend card comprises a summary panel configured to provide an overall assessment of the user's food choices over a given time period.

[0376] Section 48 the trend card includes a summary panel including information indicative of the analyte responses associated with the user's food choices; The trend card is dynamically configured; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: detecting whether the test substance responses associated with the user's food choices provide new trend information; when new trend information is detected, populating the trend card with an updated summary panel; The system according to any one of claims 25 to 47, further comprising:

[0377] Section 49 A system as described in any one of clauses 25 to 48, wherein the trend card is not displayed on the home GUI if data indicating the test substance level has not yet been received or if data indicating the test substance level has not yet been associated with the input dietary information.

[0378] Section 50 the challenge card on the home GUI includes one or more selectable challenge icons; 50. The system of any one of claims 25 to 49, wherein each of the one or more selectable challenge icons is configured to represent a challenge regarding the user's test substance response or glucose level.

[0379] Section 51 each of the one or more selectable challenge icons: an image associated with the challenge represented by the selected challenge icon; and a challenge name, which is a textual representation of the challenge represented by the selected challenge icon.

[0380] Section 52 52. The system of claim 51, wherein an indicia indicating that a challenge is in progress is displayed on the image to indicate that the challenge represented by the image is a challenge currently being run on the meal monitoring application.

[0381] Section 53 the challenge card includes a selectable link; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: In response to the user selecting the link, outputting a first challenge GUI including information regarding all challenges offered by the diet monitoring application. The system according to any one of claims 25 to 52, further comprising:

[0382] Section 54 the challenge card includes a plurality of selectable challenge icons; a first set of selectable challenge icons from the plurality of selectable challenge icons is displayed on the challenge card; the viewing device further includes a touch screen; When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving an input corresponding to a swipe operation or a drag operation from the touch panel screen; displaying a second set of selectable challenge icons on the challenge card in response to the received input; Then, A system described in any one of clauses 25 to 53, wherein at least one of the plurality of selectable challenge icons of the second set is different from at least one of the plurality of selectable challenge icons of the first set.

[0383] Section 55 the challenge card includes a plurality of selectable challenge icons; The system described in any one of clauses 25 to 54, wherein the challenge card is configured to simultaneously display two or three challenge icons of the plurality of selectable challenge icons on the home GUI.

[0384] Section 56 the recommendation card includes a plurality of selectable recommendation icons; Item 56. The system according to any one of items 25 to 55, wherein the recommendation card is configured to simultaneously display two or three recommendation icons among the plurality of selectable recommendation icons.

[0385] Section 57 57. The system of any one of clauses 25 to 56, wherein the home GUI further comprises a navigation bar.

[0386] Section 58 58. The system of any one of clauses 25 to 57, wherein the home GUI further comprises a banner including a message regarding sensor scanning and meal loading.

[0387] Section 59 1. A system for monitoring a test substance response associated with a meal in a subject, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level in the subject; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: identifying a peak analyte level within a predetermined time period for the received data indicative of the analyte level in the subject; determining an estimated meal start time and an initial test substance level based on the peak test substance level; determining an analyte level variation value; Prompting the subject to input dietary information; Associating the input dietary information with the test substance level fluctuation value; A system that executes the above.

[0388] Section 60 60. The system of clause 59, wherein the viewing device comprises a smartphone.

[0389] Section 61 61. The system of claim 59 or 60, wherein the data indicative of the test substance level of the subject comprises data indicative of a glucose level.

[0390] Section 62 the system further comprising a trusted computer system; 62. The system according to any one of claims 59 to 61, wherein the highly reliable computer system is a cloud computing platform including one or more servers.

[0391] Section 63 63. The system of claim 62, wherein the trusted computer system is configured to transmit the data indicative of the test substance level of the subject to the viewing device.

[0392] Section 64 The system further comprises a sensor control device; the sensor control device includes an analyte sensor; A system described in any one of clauses 59 to 63, wherein at least a portion of the test substance sensor is configured to be positioned under the subject's skin layer and to contact the subject's bodily fluids.

[0393] Section 65 65. The system of claim 64, wherein the sensor control device is further configured to transmit the data indicative of the test substance level of the subject to the viewing device.

[0394] Section 66 A system described in any one of clauses 59 to 65, wherein the wireless communication circuitry of the viewing device is configured to receive the data indicating the test substance level of the subject according to a wireless protocol such as "Bluetooth" or near-field wireless communication.

[0395] Section 67 67. The system of any one of clauses 59 to 66, wherein the test substance level peak value comprises a highest glucose value above a predetermined test substance level threshold.

[0396] Section 68 68. The system of clause 67, wherein the predetermined analyte level threshold is 170 mg / dL.

[0397] Section 69 68. The system of clause 67, wherein the predetermined analyte level threshold is 180 mg / dL.

[0398] Section 70 68. The system of clause 67, wherein the predetermined analyte level threshold is 190 mg / dL.

[0399] Section 71 A system as described in any one of claims 59 to 70, wherein the predetermined period of received data indicating the test substance level of the subject includes the last two hours of test substance data.

[0400] Section 72 A system as described in any one of claims 59 to 71, wherein the predetermined period of received data indicating the test substance level of the subject includes the last 4 hours of test substance data.

[0401] Section 73 A system as described in any one of claims 59 to 72, wherein the predetermined period of received data indicating the test substance level of the subject includes the last 8 hours of test substance data.

[0402] Section 74 Item 74. The system according to any one of items 59 to 73, wherein the estimated meal start time is identified by determining the time two hours prior to the time of the peak value of the test substance level.

[0403] Section 75 Item 74. The system according to any one of items 59 to 73, wherein the estimated meal start time is identified by determining the time three hours prior to the time of the peak value of the test substance level.

[0404] Section 76 Item 74. The system according to any one of items 59 to 73, wherein the estimated meal start time is identified by determining the time four hours prior to the time of the peak value of the test substance level.

[0405] Section 77 77. A system according to any one of clauses 59 to 76, wherein the analyte level fluctuation value is determined by subtracting the analyte level initial value from the analyte level peak value.

[0406] Section 78 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: storing said dietary information in said memory of said viewing device in association with analyte level variation values; The system according to any one of claims 59 to 77, further comprising:

[0407] Section 79 1. A system for monitoring a test substance response associated with a meal in a subject, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level in the subject; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: receiving dietary information entered by the subject; receiving the data indicative of the test substance level of the subject within a predetermined amount of time after the subject inputs the dietary information; identifying a peak analyte level in the received data indicative of the analyte level in the subject; identifying an initial analyte level; determining an analyte level variation value; Associating the input dietary information with the test substance level fluctuation value; A system that executes the above.

[0408] Section 80 80. The system of clause 79, wherein the viewing device comprises a smartphone.

[0409] Section 81 81. The system of claim 79 or 80, wherein the data indicative of the test substance level of the subject comprises data indicative of a glucose level.

[0410] Section 82 the system further comprising a trusted computer system; 82. The system according to any one of claims 79 to 81, wherein the highly reliable computer system is a cloud computing platform including one or more servers.

[0411] Section 83 A system described in any one of clauses 79 to 82, wherein the highly reliable computer system is configured to transmit the data indicating the test substance level of the subject to the viewing device.

[0412] Section 84 The system further comprises a sensor control device; the sensor control device includes an analyte sensor; A system described in any one of clauses 79 to 83, wherein at least a portion of the test substance sensor is configured to be positioned under the subject's skin layer and to contact the subject's bodily fluids.

[0413] Section 85 The system described in clause 84, wherein the sensor control device is further configured to transmit the data indicative of the test substance level of the subject to the viewing device.

[0414] Section 86 A system described in any one of clauses 79 to 85, wherein the wireless communication circuitry of the viewing device is configured to receive the data indicating the test substance level of the subject according to a wireless protocol such as "Bluetooth" or near-field wireless communication.

[0415] Section 87 87. The system of any one of clauses 79 to 86, wherein the test substance level peak value comprises a highest glucose value above a predetermined test substance level threshold.

[0416] Section 88 88. The system of clause 87, wherein the predetermined analyte level threshold is 170 mg / dL.

[0417] Section 89 88. The system of clause 87, wherein the predetermined analyte level threshold is 180 mg / dL.

[0418] Section 90 88. The system of clause 87, wherein the predetermined analyte level threshold is 190 mg / dL.

[0419] Section 91 91. A system according to any one of clauses 79 to 90, wherein the analyte level fluctuation value is determined by subtracting the analyte level initial value from the analyte level peak value.

[0420] Section 92 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: storing said dietary information in said memory of said viewing device in association with analyte level variation values; The system according to any one of claims 79 to 91, further comprising:

[0421] Section 93 When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: A step of displaying a notification that a meal entry has not been made after a predetermined reminder period has elapsed. The system according to any one of claims 79 to 92, further comprising:

[0422] Section 94 94. The system of claim 93, wherein the predetermined reminder period is one week.

[0423] Section 95 94. The system of claim 93, wherein the predetermined reminder period is three days.

[0424] Section 96 94. The system of claim 93, wherein the predetermined reminder period is one day.

[0425] Section 97 Item 97. The system according to any one of items 79 to 96, wherein the initial test substance level is identified based on the time of the meal information input by the subject.

[0426] Section 98 1. A system for monitoring a test substance response associated with a meal in a subject, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level in the subject; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: Steps to output the diary Graphical User Interface (GUI) Run the command, the diary GUI includes a plurality of meal entries; each meal entry of the plurality of meal entries: The date of the meal entry; and The name of the meal, a graphical representation of analyte level variability associated with the dietary input; and a numerical representation of the analyte level variation value associated with the dietary input; and Including, the system.

[0427] Section 99 99. The system of claim 98, wherein the graphical representation of the test substance level variation value has a plurality of segments.

[0428] Section 100 The plurality of segments are a first segment indicating that the analyte level fluctuation value was within a first analyte level fluctuation range; a second segment indicating that the analyte level fluctuation value was within a second analyte level fluctuation range different from the first analyte level fluctuation range; 99. The system of claim 99, comprising:

[0429] Section 101 101. The system of claim 100, wherein the first segment is a different color than the second segment.

[0430] Section 102 101. The system of claim 100, wherein the first segment is a different area than the second segment.

[0431] Section 103 Item 103. The system according to any one of items 100 to 102, wherein the first test substance level fluctuation range is less than 70 mg / dL.

[0432] Section 104 Item 103. The system according to any one of items 100 to 102, wherein the second test substance level fluctuation range is 70 mg / dL to 120 mg / dL.

[0433] Section 105 A system described in any one of clauses 100 to 104, wherein the plurality of segments further includes a third segment indicating that the test substance level fluctuation value was in a third test substance level fluctuation range different from the first test substance level fluctuation range and the second test substance level fluctuation range.

[0434] Section 106 106. The system of claim 105, wherein the third segment is a different color than the first segment and the second segment.

[0435] Section 107 107. The system of any one of clauses 98 to 106, wherein each meal entry of the plurality of meal entries further includes a time of the meal entry.

[0436] Section 108 Item 108. The system of any one of items 98 to 107, wherein each meal entry of the plurality of meal entries further includes an activity field.

[0437] Section 109 Item 98. The system of item 108, wherein each meal entry of the plurality of meal entries further includes a notes section.

[0438] Section 110 109. The system of any one of claims 98 to 109, wherein the diary GUI further comprises a view setting configured to display the plurality of meal entries by day or week.

[0439] Section 111 111. The system according to any one of clauses 98 to 110, wherein each meal input of the plurality of meal inputs further comprises a weighted average of the test substance level variation values.

[0440] Section 112 112. The system of claim 111, wherein the weighted average of the test substance level variation values ​​is based on a plurality of past meal inputs having the same or similar meals or foods as each meal input.

[0441] Section 113 112. The system of claim 111, wherein the weighted average of the test substance level variation values ​​is determined by a weighted average function that includes a recency factor.

[0442] Section 114 Item 113. The system of item 113, wherein the recency coefficient of the weighted average function is configured to reduce the test substance level variation value of a past dietary input by a predetermined coefficient per day for the number of days from the date of the past dietary input to the current date.

[0443] Section 115 1. A system for monitoring a test substance response associated with a meal in a subject, comprising: The system includes a viewing device; The viewing device is a wireless communication circuit configured to receive data indicative of an analyte level in the subject; and one or more processors coupled to a memory storing a meal monitoring application; Equipped with When the meal monitoring application is executed by the one or more processors, the meal monitoring application causes the one or more processors to: Steps to output trend Graphical User Interface (GUI) Then, the trends GUI includes a glycemic response view and a meal view; the glycemic response view includes a graphical representation representing a plurality of segments including a first segment and a second segment; the first segment represents a first analyte level range; The second segment represents a second analyte level range of variation different from the first analyte level range of variation.

[0444] Section 116 116. The system of claim 115, wherein the first segment represents a first set of meal inputs, and a test substance level variation value for each meal input of the first set is within the first test substance level variation range.

[0445] Section 117 The system of claim 115 or 116, wherein the second segment represents a second set of dietary inputs, and the test substance level variation value of each dietary input of the second set is within the second test substance level variation range.

[0446] Section 118 the meal view includes a plurality of meal entries; each meal entry of the plurality of meal entries: The date and time of the meal entry; and The name of the meal, a graphical representation of analyte level variability associated with the dietary input; and a numerical representation of the analyte level variation value associated with the dietary input; and The system according to any one of claims 115 to 117, comprising:

[0447] Section 119 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, via the wireless communication circuitry, data indicative of the analyte level of the user; identifying a analyte response of the user based on the data indicative of the analyte level; outputting, by a processor coupled to a memory storing a dietary monitoring application, a first challenge graphical user interface (GUI) presenting a list of one or more challenges related to the user's analyte response; Including, the one or more challenges include one or more ongoing challenges, one or more completed challenges, and one or more unattempted challenges; the first challenge GUI includes a first challenge card, a second challenge card, and a third challenge card; the first challenge card represents the one or more active challenges, each of the one or more active challenges representing a challenge currently being engaged by the user on the meal monitoring application; the second challenge card represents the one or more completed challenges, each of the one or more completed challenges representing a challenge completed by the user; The method, wherein the third challenge card represents one or more unattempted challenges, each of the one or more unattempted challenges representing a challenge that the user has not yet participated in.

[0448] Section 120 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, by a processor coupled to a memory storing a meal monitoring application, meal information input by the user, the meal information representing food choices of the user; outputting, by said processor, a home graphical user interface (GUI); Including, The home GUI: a plurality of selectable sections, including a user profile section, a meal entry section, a trends section, a diary section, and a reports section; a meal card configured to display one or more meal lists including the entered meal information for one or more meals consumed by the user; a trend card including a graphical representation depicting information regarding analyte responses associated with the user's food choices; a challenge card presenting a list of one or more challenges related to the user's test substance response or glucose level; a recommendation card presenting one or more recommendations regarding the user's food choices or test substance responses.

[0449] Section 121 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, via the wireless communication circuitry, data indicative of the analyte level of the user; identifying, by a processor coupled to a memory storing a dietary monitoring application, a peak analyte level within a predetermined time period from the received data indicative of the analyte level of the user; determining, by the processor, an estimated meal start time and an initial test substance level based on the peak test substance level; determining, by the processor, a variance in the analyte level; prompting, by the processor, the user to input meal information; Correlating the input dietary information with the test substance level variation value by the processor; The method includes:

[0450] Section 122 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, via the wireless communication circuitry, data indicative of the analyte level of the user; receiving, by a processor coupled to a memory storing a meal monitoring application, meal information entered by the user; receiving, by the processor, the data indicative of the analyte level of the user within a predetermined amount of time after the user inputs the meal information; identifying, by the processor, a peak analyte level in the received data indicative of the analyte level of the user; identifying, by the processor, an initial analyte level; determining, by the processor, a variance in the analyte level; Correlating the input dietary information with the test substance level variation value by the processor; The method includes:

[0451] Section 123 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, via the wireless communication circuitry, data indicative of the analyte level of the user; outputting, by a processor coupled to a memory storing the diet monitoring application, a diary graphical user interface (GUI); Including, the diary GUI includes a plurality of meal entries; each meal entry of the plurality of meal entries: The date of the meal entry; and The name of the meal, a graphical representation of analyte level variability associated with the dietary input; and a numerical representation of the analyte level variation value associated with the dietary input; and A method comprising:

[0452] Section 124 1. A method for monitoring a diet-related analyte response of a user, comprising: receiving, via the wireless communication circuitry, data indicative of the analyte level of the user; outputting, by a processor coupled to a memory storing the meal monitoring application, a trend graphical user interface (GUI); Including, the trends GUI includes a glycemic response view and a meal view; the glycemic response view includes a graphical representation representing a plurality of segments including a first segment and a second segment; the first segment represents a first analyte level range; The method, wherein the second segment represents a second analyte level range of variation different from the first analyte level range of variation. [Explanation of symbols]

[0453] 100, 325, 330, 335, 340 Test substance monitoring system 102 Sensor Control Device 103 Case 104 Test substance sensor 105 Adhesive Patch 120 Viewing Devices 120A First Viewing Device 120B Secondary Viewing Device 121 User Interface Components (Input Components) 122 Display 123 Data communication port 140, 141, 142, 143, 144 Communication channels (links) 150 Mechanical Applicator 160 Drug Delivery Devices 170 Local Computer System 180 Highly Reliable Computer Systems 190 Network 206 Processing Hardware 222 Communications Processor 223, 225, 230, 253 Memory 224 Application Processor 226, 260 power supply 228 RF Transmitter / Receiver 229 RF Antenna 232 Multifunctional circuit 234, 261 Antenna 238, 254 Power management circuit 250 Sensor Electronics 251 Semiconductor Chip (ASIC) 252 Analog Front End (AFE) 256 processors 258 Communication Circuit 327 Sensor Interface Application (Sensor Interface Function) 329 Food Monitoring Application 400, 450, 460 Home GUI 402, 453, 4002 User Profile section of the Home GUI 404, 4004 Meal entry section of the home GUI 406, 4006 Trend section of Home GUI 408 Email Button 410, 604, 704, 804, 904 Notification buttons 412, 4012 Diary section of Home GUI 414, 4014 Reports section of the Home GUI 416, 4016 Navigation Bar 418, 4180, 4323 "Link" button 420, 465 Account Login GUI 422, 4220 Email field in account login GUI 424, 4240 Password field in account login GUI 426, 4260 Sign-in button in account login GUI 430, 475 Consent GUI 432, 474, 4320, 4321, 4405, 536, 537, 538, 722, 724, 726, 761, 762, 763, 764, 765, 1131, 1132, 1137, 1236, 1256, 1320 Modal Display 440 Notification GUI 451, 461 Home GUI banner 455, 4008, 602, 653, 702, 7502, 802, 8502, 902, 9302 Information button 470 Company Profile GUI 471 License section of the About Us GUI 472 Privacy Policy section of Company Profile GUI 473 Terms of Use section of About Us GUI 480 FAQ GUI 481 FAQ GUI 1st Question Section 482 FAQ GUI 2nd Question Section 483 Question Link 4001 "Profile" Link 4003 "Notification" Link 4005 "Order your next sensor" link 4007 Frequently Asked Questions Link 4009 "Company Profile" Link 4011 "Contact Us" Link 4100 Meal Card 4101 Meal List 4102 Meal (food) text notation 4103, 6524, 751 Amount display 4104 Date stamp 4105 Timestamp 4106, 4202, 812 Graphic representation 4200 Trend Card 4201, 814 Summary Panel 4300 Challenge Card 4301, 1211, 1221, 1231, 1241, 1271 Challenge Icons 4302, 1212, 1222, 1233, 1242, 1272 Challenge Icon Images / Photos 4303, 1213, 1223, 1243, 1253, 1273 Challenge name 4304 "See All" Links 4322 "OK" button 4400 Recommendation Card 4401 Recommendation Icon 4402 Recommendation Icon Images / Photos 4403 Recommendation Name 4406, 1229 Start button 500, 550 User Profile GUI 501 Date of birth field in user profile GUI 503 Gender field in user profile GUI 504, 5004 Profile Icon 507, 524 consent checkbox 508 Name field in user profile GUI 510 Email address field in user profile GUI 512 Phone number field in user profile GUI 514 Country field in user profile GUI 516 User Profile GUI Language Field 518 Disease status field in user profile GUI 520 Units of measurement field in user profile GUI 522 Administered medications field in user profile GUI 526 Update button in user profile GUI 531 "Link sensor app" button 532 User Profile GUI Option Buttons 533 "Reset Password" Link 534 "Delete your account" link 535 "Log out" link 5005 Photo / image associated with user profile 600, 650 Meal input GUI 603, 714, 7514, 816, 8516, 912, 9312, 1228 Context information 606, 6506 Selectable meal type candidates in the meal entry GUI 608, 6508 Search / add field in meal entry GUI 609, 6509 Voice recognition button and voice recognition function for meal input GUI 610, 6518 Add button for meal entry GUI 612 Meal Entry GUI Results Section 614 Activity checkboxes in meal entry GUI 616 Activity text box in meal entry GUI 618 "Next" button in the meal entry GUI 620 Modal display of date field on meal entry GUI 622, 6522 Time field 624 Meal portion size column 626 "Add a note" checkbox 630 Memo Text Box 6511 Meal Tag 6512 Meal Library section of the Meal Entry GUI 6515 Feedback Queries 6516 First signs of a feedback query 6517 Second Sign of a Feedback Query 700, 750 Diary GUI 706 Diary GUI day view option 708 Search bar in diary GUI 710 Diary GUI daily list 716 "Apply" button in filter GUI 717 Test substance level fluctuation value filter 718 Cancel button in filter GUI 719 Date Filter 720, 770 Filter GUI 728 Notification that test substance data has not yet been received 734 Diary GUI Weekly List 736 Week view option in diary GUI 738 Information Panel 752 Reference Links 760 Reference material GUI 800, 850 Trend GUI 806, 8506 Trend GUI "Glucose Load" option 808 Trend GUI Period Options 810 Trend GUI Date Setting Change Section 818, 8518 Meal view options in Trends GUI ("Meals" options) 820 Trends GUI Search Bar 822 Trending GUI Meals (Food) List 824, 8524 Filter button in Trend GUI 826, 8526 Meal type filter in Trends GUI 828, 8528 Glucose Load Filter in Trend GUI 830, 8530 Date range filter in Trends GUI 840, 870 Filter setting GUI 900 Report GUI 906 Date range field in reports GUI 908 Glucose Loading Option in Report GUI 910 "Generate Report" button 920 Report 922 Report Date and Time Column 924 Food section of report 926 Report Activities 928 Report Glucose Load Column 931 "Clear all" button in report GUI 932 Report Notes 1100, 1101, 1102, 1103, 1105, 1110, 1111, 1112, 1113, 1115, 1118, 1120, 1121, 1122, 1123, 1124, 1125, 1126, 1127, 1130, 1133, 1134, 1135, 1136, 1140, 1145, 1150, 1155, 1160, 1165, 1170, 1171, 1172, 1173, 1174 Onboarding GUI 1116, 1117 Language selection screen A link or button where you can order the 1138 sensor 1141 "Don't Allow" button 1142 "Allow" button 1175, 1180, 1185, 1190, 1191, 1192, 1193, 1194, 1195, 1196 Tutorial GUI 1197, 1198, 1199 Food tutorial GUI 1200 Challenge List GUI (First Challenge GUI) 1201 Challenge Card (First Challenge Card) 1202 Completed Challenge Card (2nd Challenge Card) 1203 Unattempted Challenge Card (Third Challenge Card) 1210, 1220, 1230, 1260, 1270 Challenge Information GUI (Second Challenge GUI) 1214, 1232 Signs indicating that a challenge is in progress 1215, 1257 Signs of participation 1225 Challenge Summary section of Challenge Info GUI 1226, 1246 Initiative Display Section 1227 Achievement display section 1235 Progress Card 1237 "Yes" button 1238 "No" button 1240, 1290 Challenge GUI (Third Challenge GUI) 1245, 1293 Congratulatory Messages 1248, 1258, 1288, 1298 "Try again" button 1249, 1259, 1289, 1299 "Try another challenge" button 1250, 1280 Challenge GUI (4th Challenge GUI) 1255, 1291 A message informing the user that they were not successful in completing a challenge 1275 Challenge Summary Card 1276 Last Progress Card 1277 Current progress card 1279, 1339 Stop button 1281 First Progress Indicator 1282 Second Progress Indicator 1310 Banner notification (lock screen notification) 1330 In-App Messages

Claims

1. A system for monitoring a subject's response to a test substance related to their diet, The system includes a viewing device, The browsing device is A wireless communication circuit configured to receive data indicating the level of the substance tested in the subject, One or more processors coupled to memory storing the meal monitoring application, Equipped with, When the meal monitoring application is executed by one or more processors, the meal monitoring application is executed by one or more processors. With respect to the data received from the subject indicating the level of the test substance, the step of identifying the peak value of the test substance level within a predetermined period, The steps include identifying the estimated meal start time and the initial level of the test substance based on the peak value of the test substance level, A step to identify the fluctuation value of the test substance level, The steps include prompting the aforementioned subjects to enter their meal information, The steps include: associating the input dietary information with the value of the change in the level of the tested substance; A system that executes an action.

2. The system according to claim 1, wherein the viewing device includes a smartphone.

3. The system according to claim 1 or 2, wherein the data indicating the level of the test substance of the subject includes data indicating glucose levels.

4. The aforementioned system further comprises a highly reliable computer system, The system according to claim 1, wherein the highly reliable computer system is a cloud computing platform including one or more servers.

5. The system according to claim 4, wherein the highly reliable computer system is configured to transmit the data indicating the level of the substance being tested for the subject to the viewing device.

6. The system further comprises a sensor control device, The sensor control device includes a sensor for the substance to be tested, The system according to claim 1, wherein at least a portion of the substance sensor is configured to be placed beneath the skin layer of the subject and in contact with the subject's bodily fluids.

7. The system according to claim 6, wherein the sensor control device is further configured to transmit the data indicating the level of the substance being tested for the subject to the viewing device.

8. The system according to claim 1, wherein the wireless communication circuit of the viewing device is configured to receive the data indicating the level of the substance being tested for the subject in accordance with a Bluetooth® or short-range wireless communication protocol.

9. The system according to claim 1, wherein the peak value of the test substance level includes a maximum glucose value that exceeds a predetermined threshold value for the test substance level.

10. The system according to claim 9, wherein the predetermined test substance level threshold is 170 mg / dL, 180 mg / dL, or 190 mg / dL.

11. The system according to claim 1, wherein the predetermined period of the data indicating the level of the test substance of the received subject includes the most recent two hours of test substance data, or the most recent four hours of test substance data, or the most recent eight hours of test substance data.

12. The system according to claim 1, wherein the estimated meal start time is determined by determining a time two hours prior to the time of the peak value of the test substance level, or a time three hours prior to the time of the peak value of the test substance level, or a time four hours prior to the time of the peak value of the test substance level.

13. The system according to claim 1, wherein the fluctuation value of the level of the test substance is determined by subtracting the initial value of the level of the test substance from the peak value of the level of the test substance.

14. When the meal monitoring application is executed by one or more processors, the meal monitoring application is executed by one or more processors. The step of storing the aforementioned meal information in the memory of the viewing device in association with the change in the level of the substance being tested. The system according to claim 1, further enabling the execution of the following:

15. A method for monitoring a user's response to a test substance related to their diet, The process involves receiving data indicating the user's test substance level via a wireless communication circuit, A processor coupled to memory storing the meal monitoring application determines, with respect to the received data indicating the user's level of the test substance, the peak value of the test substance level within a predetermined period. The processor performs the steps of determining the estimated meal start time and the initial value of the test substance level based on the peak value of the test substance level, The processor performs the steps of identifying the fluctuation value of the level of the substance to be tested, The processor provides a step of prompting the user to input meal information, The processor performs the steps of associating the input dietary information with the test substance level fluctuation value, A method that includes this.

Images