Systems, devices, and methods for dietary related analyte response monitoring

Abstract

Systems, devices, and methods for detecting, measuring, and classifying a diet of an individual based on analyte measurements. These results and related information may be presented to an individual to display to the individual which diets cause the most serious analyte response. These results may be organized and classified based on preselected criteria or prior meals and results to organize and present the results in a format with glucose as a monitoring analyte. Various embodiments disclosed herein relate to methods, systems, and software applications aimed at attracting individuals by providing direct and timely feedback on the individual's diet-related blood glucose response.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Application No. 63 / 452,263, filed on March 15, 2023, and U.S. Application No. 63 / 335,030, filed on April 26, 2022, both of which are expressly incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] The present subject matter broadly relates to systems, devices, and methods for collecting information about analyte levels of individuals and information about meals consumed by these individuals. The present subject matter also relates to processing, analyzing, and / or presenting this information for use in meal-related analyte response monitoring, and providing insights, activities, and recommendations for these individuals. Background Art

[0004] Over the past few decades, the rising prevalence of type 2 diabetes and metabolic syndrome has been attributed to changes in diet and activity levels. For example, consuming more readily available high-glycemic index foods may lead to rapid increases in blood sugar and insulin levels after meals, which is positively associated with weight gain and obesity. These conditions can further be traced to an increased risk of developing these and other diseases.

[0005] Most people generally understand the importance of diet. However, in practice, many people have difficulty translating this general awareness into their specific food choices. These problems exist primarily because people cannot directly see the impact of their choices. This can lead to misconceptions about portion sizes, misunderstandings about which foods are relatively healthy, and a general lack of awareness of the duration and intensity of activity required to stay healthy. Advertising, habits, peer pressure, food preferences, and advice based on generalizations further exacerbate these problems.

[0006] To address these issues, an individual's physiological response can be tracked and better understood by an analyte monitoring system. Since high glucose levels are primarily driven by the consumption of food, postprandial glucose levels may be related to the amount of carbohydrates and other dietary components consumed by the individual, as well as the individual's physiological response to the meal. However, the challenge for analyzing this influx of data is to represent the data in a meaningful way so that efficient action can be taken. Data related to dietary choices and subsequent effects should be understood on a clinical basis as well as an individual basis so that individuals, dietary managers, and / or medical professionals can understand and regulate blood sugar fluctuations, such as hyperglycemic episodes.

[0007] There are many deficiencies in software that attempts to track user's dietary consumption and associate it with the user's analyte data. For example, some systems require individuals to perform many inconvenient and uncomfortable discrete blood glucose measurements (e.g., fingertip blood glucose tests). These solutions may also be unable to fully determine the glycemic response to a meal due to an insufficient number of data points. For example, an individual may perform discrete blood glucose measurements at a certain time before or after the user's blood glucose response reaches a peak, which makes it difficult to accurately determine the blood glucose response and meaningfully compare meals based on the blood glucose response. The lack of data points may also make it difficult to automatically detect the occurrence of dietary events in the user's analyte data. Therefore, some existing systems rely heavily on users to manually record meals.

[0008] Prior art systems that seek to detect meal events based solely on the presence of elevated glucose levels, such as US Patent Publication No. 2003 / 0208113, are insufficient because they do not take into account the user's previous meal history and therefore may overestimate the number of meals the user has consumed.

[0009] Therefore, there is a need for improved systems, devices and methods for dietary information collection, dietary assessment and monitoring, and correlation with analyte levels. Summary of the invention

[0010] Provided herein are exemplary embodiments of systems, devices and methods for detecting, measuring and classifying meals of human individuals relative to individual analyte measurements. These individuals may be those who exhibit or are diagnosed with diabetes, those who are considered to be prediabetes, those who suffer from metabolic syndrome, and even those who do not have symptoms of diabetes, prediabetes or metabolic syndrome. These individuals may be anyone who improves their health by adjusting their diet and / or activity practices. Result information can be presented to the individual to show which meals or various aspects of the meals have the greatest impact on analyte levels.

[0011] According to a first aspect of the present disclosure, a system for monitoring a dietary-related analyte response in a user is provided, the system comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating an analyte level of the user; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a first challenge graphical user interface (GUI), the first challenge GUI reflecting a list of one or more challenges related to the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card, wherein the first challenge card reflects the one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being performed by the user on the dietary monitoring application, wherein the second challenge card reflects the one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and wherein the third challenge card reflects the one or more unattempted challenges, wherein each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

[0012] The dietary monitoring application can store challenges in a database. The stored challenges can be output to each user in the same way, or can be personalized based on the data analyzed by the dietary monitoring application. Challenges can be output to a class of users based on shared characteristics, demographics, locations, behaviors, or activities. For example, a pizza challenge can be output to a user (e.g., to a user who has eaten a threshold amount of pizza within a predetermined time period), where the dietary monitoring application determines to eat pizza. Challenges can be generated to users based on various different criteria or behaviors. For example, challenges can be output to users based on the following: a specific user group or characteristic identified by the dietary monitoring application; psychology; information input to the dietary monitoring application by the user, such as a diary entry; the time when the user consumes the meal; demographics; geographic factors, such as activities occurring in a specific place or region, and; seasonal activities. Challenges can be generated and displayed on the dietary monitoring application in a predetermined order or a sequence based on specific criteria or behaviors analyzed by the dietary 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 implementations, the first challenge card of the system includes one or more selectable first challenge icons, wherein each of the one or more selectable first challenge icons reflects a challenge currently being performed by a user.

[0015] In some embodiments, each of the one or more selectable first challenge icons includes a first indicator, a picture, and a text description related to the challenge currently in progress, wherein the first indicator is displayed on the picture and is configured to indicate that the challenge is currently in progress. In some embodiments, the first indicator is a green dot.

[0016] In some implementations, the second challenge card includes one or more selectable second challenge icons, wherein each of the one or more selectable second challenge icons reflects a challenge to be completed by the user.

[0017] In some embodiments, each of the one or more optional second challenge icons includes a second indicator, a picture, and a text description associated with the completed challenge, wherein the second indicator is superimposed on the picture and is configured to indicate that the challenge has been completed by the user. In some embodiments, the second indicator is a colored check mark.

[0018] In some embodiments, the third challenge card includes one or more optional third challenge icons, wherein each of the one or more optional third challenge icons reflects a challenge that the user has not yet attempted. In some embodiments, each of the one or more optional third challenge icons includes a picture and text description related to the completed challenge.

[0019] In some embodiments, each of the first challenge card, the second challenge card, and the third challenge card includes a plurality of optional challenge icons, wherein a first set of the plurality of optional challenge icons is displayed on the first challenge GUI, wherein the reader device also includes a touch screen, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a swipe gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the plurality of optional challenge icons on the first challenge GUI, wherein at least one or more of the plurality of optional challenge icons of the second set is different from at least one or more of the plurality of optional challenge icons of the first set.

[0020] In some embodiments, the list of one or more challenges includes one or more optional challenge icons, wherein each of the one or more optional challenge icons corresponds to one of one or more challenges related to the user's analyte response or glucose level, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to selecting one of the one or more optional challenge icons, output a second challenge GUI that reflects contextual information related to a challenge in the one or more challenges corresponding to the selected one of the one or more optional challenge icons.

[0021] The contextual information may be a separate screen explaining one of the one or more challenges that corresponds to the selected one of the one or more selectable challenge icons. The contextual information may provide information related to the corresponding challenge. For example, if one of the one or more challenges that corresponds to the selected one of the one or more selectable challenge icons is related to eating vegetables and fruits, the contextual information may provide a contextual description of the importance or relevance of consuming vegetables and fruits along with a description of the challenge.

[0022] In some embodiments, the second challenge GUI includes: a challenge profile portion, including a selected one of one or more optional challenge icons, a picture, and a challenge title, which provides a text description of a challenge of the one or more challenges corresponding to the selected one of the one or more optional challenge icons; an attempt indicator, configured to indicate the time when the user last attempted a challenge of the one or more challenges corresponding to the selected one of the one or more optional challenge icons; and a completion indicator, configured to indicate the time when the user last successfully completed a challenge of the one or more challenges corresponding to the selected one of the one or more optional challenge icons.

[0023] In some embodiments, if a challenge among the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an unattempted challenge, the second challenge GUI also includes a start button, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: start the unattempted challenge on the dietary monitoring application in response to selecting the start button.

[0024] In some implementations, the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: in response to selecting the start button, start an unattempted challenge on the meal monitoring application the next day.

[0025] In some embodiments, if a challenge among the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an active challenge, the second challenge GUI also includes a stop button, wherein the dietary monitoring application, when executed by one or more processors, also causes the one or more processors to: stop continuing the active challenge in response to selecting the stop button.

[0026] In some embodiments, if a challenge of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an active challenge, the second challenge GUI also includes a progress card configured to indicate the user's progress made toward the active challenge, wherein the progress card includes a unit of measure and a unit of time indicating the progress. In some embodiments, the unit of measure includes a unit of fraction, and the unit of time includes a number of days.

[0027] In some embodiments, if a challenge of one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an active challenge, a modal is displayed on the second challenge GUI, wherein the modal is configured to prompt the user to provide progress information related to the active challenge in the dietary monitoring application.

[0028] In some embodiments, the dietary monitoring application is configured to detect whether the user successfully completes the active challenge based on the tracked progress, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to the dietary monitoring application detecting that the user successfully completes the active challenge, output a third challenge GUI, wherein the third challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message congratulating the user for successfully completing the active challenge, and in response to the dietary monitoring application detecting that the user successfully completes the active challenge, identify the active challenge as a completed challenge, wherein the third challenge GUI also includes a first button that, when selected by the user, is configured to restart the completed challenge, and wherein the third challenge GUI also includes a second button that, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from a list of one or more challenges reflected by the first challenge GUI.

[0029] The meal monitor application may be configured to automatically detect whether a challenge is successfully progressing based on meal entries or analyte level variance values ​​associated with meal entries. For example, the meal monitor application may automatically detect that a user has consumed four consecutive "green impact" or low glycemic response meals.

[0030] In some implementations, in response to the user selecting the first button, a modal is displayed on the third challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart the completed challenge.

[0031] The modal can include information related to the completed challenge. The modal can be a more vivid and intuitive modal within the application that provides more context for prompting actions. The modal can present graphics and text that prompt the user to take a specific action. The modal can include possible answers so that the user can indicate whether they want to restart the challenge.

[0032] In some embodiments, the dietary monitoring application is configured to detect whether the user successfully completes the active challenge based on the tracked progress, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to the dietary monitoring application detecting that the user has not successfully completed the active challenge, output a fourth challenge GUI, wherein the fourth challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message notifying the user that the active challenge has not been successfully completed, and in response to the dietary monitoring application detecting that the active challenge has not been successfully completed, identify the active challenge as a completed challenge, wherein the fourth challenge GUI also includes a first button that, when selected by the user, is configured to restart the completed challenge, and wherein the fourth challenge GUI also includes a second button that, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from the list of one or more challenges reflected by the first challenge GUI.

[0033] In some implementations, in response to the user selecting the first button, a modal is displayed on the fourth challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart the completed challenge.

[0034] In some embodiments, the dietary monitoring application includes a home page GUI, which includes a challenge card, wherein the challenge card includes an optional link, wherein the dietary monitoring application, when executed by one or more processors, also causes the one or more processors to: output a first challenge GUI in response to a user selecting the link.

[0035] In some embodiments, each of the one or more challenges is configured to represent a challenge to 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 dietary-related analyte responses in a user is provided, the system comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating an analyte level of a user; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to: receive dietary information input by a user, wherein the dietary information is configured to reflect the user's food selections; output a home page GUI, wherein the home page GUI comprises: a plurality of optional sections comprising a user profile section, a dietary entry section, a trend section, a diary section, and a report section; a meal card configured to display one or more meal lists comprising input dietary information associated with one or more meals consumed by the user; a trend card comprising a graphical representation of information related to an analyte response associated with the user's food selections; a challenge card reflecting a list of one or more challenges associated with the user's analyte response or glucose level; and a recommendation card reflecting one or more recommendations associated with the user's food selections or analyte responses.

[0037] The dietary monitoring application can store recommendations in a database. In addition, the dietary monitoring application can output recommendations from a trusted source. The stored recommendations can be output to each user in the same way, or can be personalized based on the data analyzed by the dietary monitoring application. Recommendations can be output to a class of users based on shared characteristics, demographics, location, behavior, or activity. Recommendations can be generated based on various different standards or behaviors. For example, recommendations can be output to users based on the following: a specific user group or characteristic identified by the dietary monitoring application; psychology; information input to the dietary monitoring application by the user, such as diary entries; the time when the user consumes the meal; the amount of time the user has used the dietary monitoring application or a specific sensor; demographics; geographic factors, such as activities that occur in a specific place or region, and; seasonal activities. Recommendations can be generated and displayed on the dietary monitoring application in a predetermined order based on specific standards or behaviors analyzed by the dietary monitoring application. The dietary monitoring application can analyze the data and generate relevant recommendations based on the received data. Over time, recommendations may become more personalized. For example, after 30 days, recommendations related to instructions on how to remove the sensor can be output to the user. As more data is received and analyzed by the dietary monitoring application, the generated recommendations may be refined or updated.

[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 implementations, the recommendation card includes one or more selectable recommendation icons, where each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations.

[0040] In some implementations, each of the one or more selectable recommendation icons includes an image associated with a corresponding one of the one or more recommendations, and a recommendation title that provides a text description of the corresponding one of the one or more recommendations.

[0041] In some embodiments, the recommendation card includes multiple optional recommendation icons, wherein a first set of the multiple optional recommendation icons is displayed on the recommendation card, wherein the reader device also includes a touch screen, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a slide gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of multiple optional recommendation icons on the recommendation card, wherein at least one or more of the multiple optional recommendation icons in the second set is different from at least one or more of the multiple optional recommendation icons in the first set.

[0042] In some embodiments, the recommendation card includes one or more selectable recommendation icons, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to selecting one of the one or more selectable recommendation icons, output a modal on the home page GUI, wherein the modal provides contextual information related to a corresponding one of the one or more recommendations, and wherein the modal is configured to guide the user to take action based on the corresponding one of the one or more recommendations.

[0043] In some embodiments, the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: detect a user's food selection; analyze the input dietary information; and based on the analysis, display one or more optional recommendation icons on a recommendation card, wherein each of the one or more optional recommendation icons reflects a recommendation related to the user's food selection or analyte response.

[0044] In some embodiments, the recommendation card includes one or more optional recommendation icons, wherein each of the one or more optional recommendation icons corresponds to one of the one or more recommendations, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to selecting one of the one or more optional recommendation icons, remove the selected one of the one or more optional recommendation icons from the recommendation card, and display a new optional recommendation icon on the recommendation card to replace the removed recommendation icon.

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

[0046] In some embodiments, the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: detect when a predetermined time period is reached, and in response to reaching the predetermined time period, replace one or more optional recommendation icons on the recommendation card with a new set of one or more optional recommendation icons, wherein at least one of the one or more optional recommendation icons in the new set is different from at least one of the one or more optional recommendation icons replaced.

[0047] In some implementations, the home page GUI is configured to switch between multiple views, where the multiple views include at least a first view and a second view.

[0048] In some embodiments, the home page GUI is in a first view, wherein the home page GUI is configured to display a user profile portion, a meal entry portion, a diary portion, and a meal card in the first view, wherein the reader device also includes a touch screen, wherein the meal monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a scroll gesture, a swipe gesture, a pull gesture, or a drag gesture from the touch screen, and wherein, in response to the received input, the home page GUI is configured to transition from the first view to a second view, wherein trend cards, challenge cards, and recommendation cards are displayed on the home page GUI in the second view.

[0049] In some embodiments, the home page GUI is configured to transition between multiple views, wherein each of the multiple views is different, wherein the reader device also includes a touch screen, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a scroll gesture, a swipe gesture, a pull gesture, or a drag gesture from the touch screen, and in response to the received input, display one of the multiple views of the home page GUI.

[0050] In some implementations, the meal card is configured to display one or more meal listings including meal information related to one or more of the most recently consumed meals.

[0051] In some embodiments, each of the one or more meal lists includes detailed information of a meal consumed by a user, wherein the one or more meal lists are displayed on a meal card in chronological order, wherein a meal list corresponding to a most recently consumed meal is displayed at a top portion of the meal card.

[0052] In some embodiments, each of the one or more meal listings includes detailed information of a meal consumed by a user and a corresponding meal-related analyte response for the meal.

[0053] In some embodiments, each of one or more meal lists includes: a textual description of the meal consumed by the user; a portion size indicator, including information indicating that the meal is small, medium, or large compared to the user's daily meal supply; a date stamp associated with the date the meal was consumed by the user; a timestamp associated with the time the meal was consumed; and a graphical representation of the analyte response associated with the meal.

[0054] In some implementations, the graphical representation includes a plurality of segments.

[0055] In some embodiments, the plurality of segments include a first segment, and wherein the first segment indicates an analyte response including a low blood glucose response, wherein the plurality of segments include a second segment, wherein the second segment indicates an analyte response including a moderate blood glucose response, and wherein the plurality of segments include a third segment, wherein the third segment indicates an analyte response including a high blood glucose response.

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

[0057] In some embodiments, the graphical representation of the trend card indicates analyte responses associated with the user's food selections over a predetermined time period.

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

[0059] In some embodiments, the first color segment includes green indicating a low glycemic response, wherein the second color segment includes yellow indicating a moderate glycemic response, and wherein the third color segment includes orange indicating a high glycemic response.

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

[0061] In some embodiments, the trend card includes a summary panel that includes information indicating an analyte response associated with a user's food selections, wherein the trend card is configured to be dynamic, and wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: detect whether the analyte response associated with the user's food selections provides new trend information, and in response to detecting the new trend information, populate an updated summary panel on the trend card.

[0062] In some embodiments, the trend card is not displayed on the home page GUI when data indicative of analyte levels is not received or associated with the input dietary information.

[0063] In some embodiments, a challenge card on the home page GUI includes one or more selectable challenge icons, wherein each of the one or more selectable challenge icons is configured to reflect a challenge related to an analyte response or glucose level of a user.

[0064] In some implementations, each of the one or more selectable challenge icons includes a picture associated with the challenge reflected by the selected challenge icon, and a challenge title that provides a textual description of the challenge reflected by the selected challenge icon.

[0065] In some embodiments, a live indicator is displayed on the picture to indicate that the challenge reflected by the picture is an active challenge on the meal monitoring application.

[0066] In some embodiments, the challenge card includes an optional link, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to a user selecting the link, output a first challenge GUI including information about all challenges offered on the dietary monitoring application.

[0067] In some embodiments, the challenge card includes a plurality of selectable recommendation icons, wherein a first set of the plurality of selectable challenge icons is displayed on the challenge card, wherein the reader device further includes a touch screen, and wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: receive input corresponding to a swipe gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the plurality of selectable challenge icons on the challenge, wherein at least one or more of the plurality of selectable challenge icons of the second set is different from at least one or more of the plurality of selectable challenge icons of the first set.

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

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

[0070] In some implementations, the home page GUI also includes a navigation bar.

[0071] In some implementations, the home page GUI also includes a banner including messages related to scanning sensors and meal impact.

[0072] According to a third aspect of the present disclosure, a system for monitoring a meal-related analyte response in a subject is provided, the system comprising: a reader device, comprising: a wireless communication circuit, configured to receive data indicating an analyte level of the subject; one or more processors, coupled to a memory, the memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to: identify a peak analyte level value of the data indicating the analyte level of the subject received within a predetermined time period, determine an estimated meal start time and an initial analyte level value based on the peak analyte level value, determine an analyte level variance value, prompt the subject to input meal information, and associate the input meal information with the analyte level variance value.

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

[0074] In some embodiments, data indicative of an analyte level in the subject includes data indicative of glucose levels.

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

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

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

[0078] In some embodiments, the peak analyte level value comprises the highest glucose value that exceeds 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 for the received data indicating the analyte level of the subject includes the last two hours of analyte data. In some embodiments, the predetermined time period for the received data indicating the analyte level of the subject includes the last four hours of analyte data. In some embodiments, the predetermined time period for the received data indicating the analyte level of the subject includes the last eight hours of analyte data.

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

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

[0082] In some embodiments, the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and the associated analyte level variance values ​​in a memory of the reader device.

[0083] According to a fourth aspect of the present disclosure, a system for monitoring a dietary-related analyte response in a subject is provided, the system comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating an analyte level of the subject; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causes the one or more processors to: receive dietary information input by the subject, receive data indicating the analyte level of the subject within a predetermined amount of time after the dietary information is input by the subject, identify a peak analyte level value of the received data indicating the analyte level of the subject, determine an initial analyte level value, determine an analyte level variance value, and associate the input dietary information with the analyte level variance value.

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

[0085] In some embodiments, data indicative of an analyte level in the subject includes data indicative of glucose levels.

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

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

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

[0089] In some embodiments, the peak analyte level value comprises the highest glucose value that exceeds 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 variance value is determined by subtracting the initial analyte level value from the peak analyte level value.

[0091] In some embodiments, the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and the associated analyte level variance values ​​in a memory of the reader device.

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

[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, initial analyte level values ​​are determined based on meal timing information input by the subject.

[0095] According to a fifth aspect of the present disclosure, a system for monitoring a dietary-related analyte response in a subject is provided, the system comprising: a reader device, comprising: a wireless communication circuit, configured to receive data indicating an analyte level of the subject; one or more processors, coupled to a memory, the memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a diary GUI, the diary GUI comprising a plurality of dietary entries, wherein each of the plurality of dietary entries comprises: a date of each dietary entry, a meal name, a graphical representation of an analyte level variance value associated with each dietary entry, and a numerical representation of the analyte level variance value associated with each dietary entry.

[0096] In some embodiments, the graphical representation of analyte level variance values ​​includes a plurality of segments.

[0097] In some embodiments, the plurality of segments includes a first segment, wherein the first segment indicates analyte level variance values ​​within a first analyte level variance range, and wherein the plurality of segments includes a second segment, wherein the second segment indicates analyte level variance values ​​within a second analyte level variance range different from the first analyte level variance range.

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

[0099] In some embodiments, the first segment comprises a different area than the second segment.

[0100] In some embodiments, the first analyte level has a variance range of less than 70 mg / dL.

[0101] In some embodiments, the second analyte level variance ranges between 70 mg / dL and 120 mg / dL.

[0102] In some embodiments, the plurality of segments further includes a third segment that indicates analyte level variance values ​​within a third analyte level variance range that is different from both the first analyte level variance range and the second analyte level variance range.

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

[0104] In some embodiments, each of the plurality of meal entries further includes a time of each meal entry. In some embodiments, each of the plurality of meal entries further includes an activity field. In some embodiments, each of the plurality of meal entries further includes a notes field.

[0105] In some implementations, the diary GUI further includes a view setting configured to display the plurality of meal entries by day or by week.

[0106] In some embodiments, each of the plurality of meal entries further comprises a weighted average of analyte level variance values. In some embodiments, the weighted average of analyte level variance values ​​is based on a plurality of historical meal entries having meals or foods that are the same or similar to each meal entry. In some embodiments, the weighted average of analyte level variance 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 variance value of the historical dietary entry by a predetermined factor for each day between the date of the historical dietary entry and the current date.

[0108] According to a sixth aspect of the present disclosure, a system for monitoring a dietary-related analyte response in a subject is provided, the system comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating an analyte level of the subject; one or more processors coupled to a memory, the memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a trend GUI, the trend GUI comprising a blood glucose response view and a dietary view, wherein the blood glucose response view comprises a graphical representation reflecting a plurality of segments, the plurality of segments comprising a first segment and a second segment, wherein the first segment indicates a first analyte level variance range, and the second segment indicates a second analyte level variance range different from the first analyte level variance range.

[0109] In some embodiments, a first segment indicates a first set of meal entries, each meal entry having an analyte level variance value within a first analyte level variance range.

[0110] In some embodiments, the second segment indicates a second set of meal entries, each meal entry having an analyte level variance value within a second analyte level variance range.

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

[0112] According to a seventh aspect of the present disclosure, a method for monitoring a dietary-related analyte response in a user is provided, the method comprising: receiving data indicating an analyte level of the user through a wireless communication circuit; identifying the analyte response of the user based on the data indicating the analyte level; and outputting a first challenge GUI by a processor coupled to a memory storing a dietary monitoring application, the first challenge GUI reflecting a list of one or more challenges related to the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card; wherein the first challenge card reflects one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being conducted by the user on the dietary monitoring application, wherein the second challenge card reflects one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and wherein the third challenge card reflects one or more unattempted challenges, wherein each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

[0113] According to an eighth aspect of the present disclosure, a method for monitoring dietary-related analyte responses in a user is provided, the method comprising: receiving dietary information input by a user by a processor coupled to a memory storing a dietary monitoring application, wherein the dietary information reflects the user's food selection; and outputting a homepage GUI by the processor, the homepage GUI comprising: a plurality of optional parts, wherein the plurality of optional parts include a user profile part, a meal entry part, a trend part, a diary part, and a report part; a meal card configured to display one or more meal lists, the one or more meal lists including input dietary information related to one or more meals consumed by the user; a trend card including a graphical representation of information related to an analyte response associated with the user's food selection; a challenge card reflecting a list of one or more challenges related to the user's analyte response or glucose level; and a recommendation card reflecting one or more recommendations related to the user's food selection or analyte response.

[0114] According to a ninth aspect of the present disclosure, a method for monitoring a meal-related analyte response in a user is provided, the method comprising: receiving data indicating an analyte level of a user via a wireless communication circuit; identifying, by a processor coupled to a memory storing a meal monitoring application, a peak analyte level value of data indicating an analyte level of a subject received within a predetermined time period; determining, by the processor, an estimated meal start time and an initial analyte level value based on the peak analyte level value; determining, by the processor, an analyte level variance value; prompting, by the processor, the subject to input meal information; and associating, by the processor, the input meal information with the analyte level variance value.

[0115] According to the tenth aspect of the present disclosure, a method for monitoring a dietary-related analyte response in a user is provided, the method comprising: receiving data indicating an analyte level of a user through a wireless communication circuit; receiving dietary information input by a user by a processor coupled to a memory storing a dietary monitoring application; receiving data indicating the analyte level of the user within a predetermined amount of time after the dietary information is input by the user by the processor; identifying, by the processor, a peak analyte level value of the received data indicating the analyte level of the subject; determining, by the processor, an initial analyte level value; determining, by the processor, an analyte level variance value; and associating, by the processor, the input dietary information with the analyte level variance value.

[0116] According to the eleventh aspect of the present disclosure, a method for monitoring a dietary-related analyte response in a user is provided, the method comprising: receiving data indicating an analyte level of the user through a wireless communication circuit; outputting a diary GUI by a processor coupled to a memory storing a dietary monitoring application, the diary GUI comprising a plurality of dietary entries, wherein each of the plurality of dietary entries comprises: the date of each dietary entry, the name of the meal, a graphical representation of an analyte level variance value associated with each dietary entry, and a numerical representation of the analyte level variance value associated with each dietary entry.

[0117] According to a twelfth aspect of the present disclosure, a method for monitoring a meal-related analyte response in a user is provided, the method comprising: receiving data indicating an analyte level of the user through a wireless communication circuit; and outputting a trend GUI by a processor coupled to a memory storing a meal monitoring application, the trend GUI comprising a blood glucose response view and a meal view, wherein the blood glucose response view comprises a graphical representation reflecting a plurality of segments, the plurality of segments comprising a first segment and a second segment, wherein the first segment indicates a first analyte level variance range, and the second segment indicates a second analyte level variance range different from the first analyte level variance 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 to discover common consistencies (or inconsistencies) and trends therein based on relevant historical glucose readings and associated algorithms, variables, weights, and comparisons.

[0119] Many of the embodiments disclosed herein are intended to engage individuals by providing direct and timely feedback about their meal-related analyte responses. In some embodiments, the analyte responses may be provided to individuals in an easily understandable format to characterize the impact of meal consumption.

[0120] This embodiment can immediately provide individuals with information, thereby encouraging individuals to take action to better understand how their own diet affects their body's analyte response. Individuals can compare and contrast their current and historical analyte data to understand how their own efforts relate to better diet and dietary choices, and how these choices directly affect their health.

[0121] Many embodiments provided herein are improved GUI or GUI features for analyte monitoring systems, which are highly intuitive, user-friendly, and provide quick access to the physiological information of users. More specifically, these embodiments can allow users to easily navigate between different user interfaces, which can quickly indicate various physiological conditions and / or operable responses to users, and make analyte data related to meals, motion, pressure or other factors, without requiring users (or HCP) to complete the arduous task of checking a large amount of analyte data. In addition, in many embodiments, some GUI and GUI features allow users (and / or their caregivers) to better understand and improve their diet, eating habits, and manage other stressors when they see the correlation with these activities and their glucose levels. Similarly, in many embodiments, the improved digital interface and / or features for the dietary monitoring system can improve the visualization of the impact of food selection on analyte (glucose) levels. Other improvements and advantages are also provided. The various configurations of these devices are described in detail by the embodiments that are only used as examples.

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

[0123] Aspects of the present disclosure may be provided in combination with each other, and features of one aspect may be applied to other aspects. Any feature in one aspect of the present disclosure may be applied to other aspects of the present disclosure in any appropriate combination. For example, the features of the system of the first aspect may be used in combination with the features of the method of the seventh or eighth aspect. It should also be understood that the specific combination of various features described and defined in any aspect of the present disclosure may be independently implemented and / or provided and / or used.

[0124] Other systems, devices, methods, features, and advantages of the subject matter described herein will be or will become apparent to one skilled in the art upon examination of the following drawings and detailed description. All such additional systems, devices, methods, features, and advantages are included in this specification, are within the scope of the subject matter described herein, and are protected by the appended claims. Features of the exemplary embodiments should in no way be construed as limiting the appended claims without explicit recitation of such features in the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0125] The details of the subject matter described herein (both with respect to its structure and operation) may be apparent from a careful reading of the accompanying drawings, in which like reference numerals refer to like parts. The components in the figures are not necessarily drawn to scale, emphasis instead being placed on illustrating the principles of the subject matter. In addition, all illustrations are intended to convey concepts, in which relative size, shape, and other detailed attributes may be depicted schematically rather than literally or precisely.

[0126] Figure 1 is a high-level diagram depicting an exemplary embodiment of an analyte monitoring system for analyte (eg, glucose) measurement, data acquisition, and / or processing.

[0127] Figure 2A is a block diagram depicting an example implementation of a reader device configured as a smartphone.

[0128] Figure 2B is a block diagram depicting an exemplary implementation of a sensor control device.

[0129] Figure 3A is a flow chart depicting an exemplary embodiment of a method for dietary information collection and assessment.

[0130] FIG. 3B to FIG. 3E is a high-level diagram depicting an exemplary embodiment of various analyte monitoring systems for use with a meal monitor application.

[0131] Figure 3F is a flow chart depicting an exemplary implementation of a method for associating analyte data with dietary information.

[0132] Figure 3G is a flow chart depicting another exemplary embodiment of a method for associating analyte data with dietary information.

[0133] Figure 4A-1 is an exemplary implementation of a home page GUI for a meal monitor application.

[0134] Figure 4A-2is an exemplary implementation of a home page GUI for a meal monitor application.

[0135] Figure 4A-3 and Figure 4A-4 is an exemplary implementation of a home page GUI for a meal monitor application.

[0136] Figure 4A-5 and Figure 4A-6 is an exemplary implementation of a home page GUI for a meal monitor application.

[0137] Figure 4A-7 is an exemplary implementation of a home screen modal for a meal monitor application.

[0138] Figure 4B is an exemplary implementation of an "About Us" GUI for a meal monitor application.

[0139] Figure 4C is an exemplary implementation of a "Contact Us" modal for a meal monitor application.

[0140] FIG. 4D to FIG. 4E is an exemplary implementation of a "FAQ" GUI for a meal monitor application.

[0141] FIG. 4F to FIG. 4I is an exemplary implementation of a connection GUI for a meal monitor application.

[0142] Figures 4J to 4N is an exemplary implementation of a connection GUI for a meal monitor application.

[0143] Fig.4O is an exemplary implementation of a notification GUI for a meal monitor application.

[0144] Figure 5A and Figure 5B is an exemplary implementation of a profile GUI for a meal monitor application.

[0145] FIG. 5C to FIG. 5I is an exemplary implementation of a profile GUI for a meal monitor application.

[0146] FIG. 6A to FIG. 6E is an exemplary implementation of an “Add Food” GUI for a meal monitor application.

[0147] FIG. 6F to FIG. 6J is an exemplary implementation of an “Add Food” GUI for a meal monitor application.

[0148] 7A to 7Iis an exemplary implementation of a diary GUI for a meal monitor application.

[0149] Figures 7J to 7R is an exemplary implementation of a diary GUI for a meal monitor application.

[0150] FIG. 8A to FIG. 8D is an exemplary implementation of a trending GUI for a meal monitor application.

[0151] FIG. 8E to FIG. 8H is an exemplary implementation of a trending GUI for a meal monitor application.

[0152] FIG. 9A to FIG. 9B is an exemplary implementation of a reporting GUI for a meal monitor application.

[0153] FIG. 9C to FIG. 9E is an exemplary implementation of a reporting GUI for a meal monitor application.

[0154] Fig.9F is an exemplary implementation of a reporting GUI for a meal monitor application.

[0155] Fig.10 is a flow chart depicting an exemplary implementation of a method for onboarding a user to a meal monitor application.

[0156] Figures 11A-1 to 11N-3 is an exemplary implementation of an inclusion GUI for a meal monitor application.

[0157] FIG. 12A to FIG. 12K is an exemplary implementation of a challenge GUI for a meal monitor application.

[0158] FIG. 13A to FIG. 13C is an exemplary implementation of a notification on a GUI for a meal monitor application. DETAILED DESCRIPTION

[0159] Provided herein are exemplary embodiments of systems, devices, and methods for monitoring and measuring analyte responses of human individuals to meals. Specifically, based on the collected analyte data, users can further understand meal-related events and their impact on individual analyte levels, and ultimately be used to modify future meal choices and eating habits.

[0160] Before describing the subject matter in greater detail, it is worth describing exemplary embodiments of systems, devices, and methods that may implement the subject matter.

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

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

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

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

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

[0166] Embodiments of in vivo analyte monitoring systems

[0167] For purposes of illustration and not limitation, the GUI and associated software described herein may be used with Figure 1 The exemplary analyte monitoring system described in FIG. 3B to FIG. 3E The exemplary systems described are used in conjunction with. Figure 1 1 is an illustrative view depicting an exemplary in vivo analyte monitoring system 100, which may be used by any and / or all embodiments described herein. The system 100 may have a sensor control device 102 and a reader device 120 that communicate with each other via a local communication path (or link) 140, which may be wired or wireless and unidirectional or bidirectional. In embodiments where the local communication path 140 is wireless, any near field communication (NFC) protocol, RFID protocol, Bluetooth or low power Bluetooth protocol, WiFi protocol, proprietary protocol, etc. may be used, including those communication protocols existing as of the date of this application or variants thereof developed later.

[0168] Bluetooth is a well-known standardized short-range wireless communication protocol, and low-power Bluetooth is its version that requires less power to operate. Low-power Bluetooth (Bluetooth LE, BTLE, BLE) is also called Bluetooth Smart or Bluetooth Smart Ready. The version of BTLE is described in the Bluetooth Specification Version 4.0 released on June 30, 2010, which is expressly incorporated herein by reference for all purposes. The term "NFC" applies to many protocols (or standards) that set forth the operating parameters, modulation schemes, encodings, transmission speeds, frame formats, and command definitions of NFC devices. The following is a non-exhaustive list of examples of these protocols, the entire contents of each of which (and all sub-parts thereof) are incorporated herein by reference for all purposes: ECMA-340, ECMA-352, ISO / IEC 14443, ISO / IEC 15693, ISO / IEC 16000-3, ISO / IEC 18092, and ISO / IEC 21481.

[0169] The reader device 120 is also capable of communicating with the drug delivery device 160 via a communication path (or link) 143, wirelessly, or a combination of two-way or one-way communication, with the local computer system 170 via a communication path (or link) 141, and with the network 190 via a communication path (or link) 142. The same wireless protocol described for link 140 can also be used for all or part of links 141, 142, and 143.

[0170] The reader device 120 can communicate with any number of entities via a network 190, which can be part of a telecommunications network, such as a Wi-Fi network, a local area network (LAN), a wide area network (WAN), the Internet, or other data network for one-way or two-way communications. The trusted computer system 180 can be accessed via the network 190. In alternative embodiments, the communication paths 141 and 142 can be the same path, which can include the network 190 and / or additional networks. All communications on the paths 140, 141, 142, 143, and 144 can be encrypted, and the sensor control device 102, the reader 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 those communications sent and received.

[0171] Variations of devices 102 and 120 and other components of in vivo based analyte monitoring systems suitable for use with the system, device, and method embodiments described herein are described in US Patent Publication No. 2011 / 0213225 (the '225 publication), the entire contents of which are incorporated herein by reference for all purposes.

[0172] The sensor control device 102 may include a housing 103 that includes an in vivo analyte monitoring circuit and a power source (not shown). The in vivo analyte monitoring circuit may be electrically coupled to an analyte sensor 104 that may extend through an adhesive patch 105 and extend from the housing 103. The adhesive patch 105 includes an adhesive layer (not shown) for attaching to the skin surface of the user's body. In addition to or in place of an adhesive, other forms of body attachment to the body may be used.

[0173] Sensor 104 is adapted to be at least partially inserted into a user's body, where it can be in fluid contact with a bodily fluid (e.g., interstitial fluid (ISF), dermal fluid, or blood) of the user and used in conjunction with in vivo analyte monitoring circuitry to measure analyte-related data of the user. In general, sensor control device 102 and its components can be applied to the body in one or more steps as described in the incorporated '225 publication using a mechanical applicator 150 or in any other desired manner.

[0174] Upon activation, the sensor control device 102 may wirelessly communicate collected analyte data (such as, for example, data corresponding to monitored analyte levels and / or monitored temperature data, and / or stored historical analyte-related data) to the reader device 120, where, in certain embodiments, it may be algorithmically processed into data representative of the user's analyte levels and then displayed to the user and / or otherwise incorporated into a diabetes monitoring regimen.

[0175] Various embodiments disclosed herein relate to a reader device 120 that may have a user interface that includes one or more of a display 122, a keyboard, an optional user interface component 121, and the like. Here, the display 122 may output information to the user and / or accept input from the user (e.g., if configured as a touch screen). The reader device 120 may include one or more optional user interface components 121, such as buttons, actuators, touch-sensitive switches, capacitive switches, pressure-sensitive switches, micro-wheels, and the like. The reader 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. The reader device 120 may also include an integrated or attachable in vitro meter, including an in vitro test strip port (not shown) to receive an in vitro analyte test strip for performing in vitro blood analyte measurements.

[0176] The drug delivery device 160 can inject or infuse drugs (such as but not limited to insulin) into the individual body wearing the sensor control device 102. Like the reader device 120, the drug delivery device can include a processing circuit, a non-transitory memory containing instructions that can be executed by the processing circuit, a wireless or wired communication circuit, and a user interface, which includes one or more of a display, a touch screen, a keyboard, an input button, or an instrument, etc. The drug delivery device 160 can include a drug reservoir, a pump, an infusion tube, and an infusion cannula, which are configured to be at least partially implanted in the user's body. The pump can transport insulin from the reservoir through a tube and then transport it to the user's body through a cannula. The drug delivery device 160 can include instructions that can be executed by a processor to control the amount of insulin pumped and delivered. These instructions can also calculate the insulin delivery amount and duration (e.g., single infusion and / or basal infusion curve) based on the analyte level measurement obtained directly or indirectly from the sensor control device 102. Alternatively, the calculation of the insulin delivery amount and duration and the control of the pump can be performed directly by the reader device 120. The drug delivery device may be configured to communicate directly with the reader device 120 in a closed-loop or semi-closed-loop system. Alternatively, the drug delivery device may include the functionality of the reader device 120 described herein, or vice versa, to achieve an integrated reader and drug delivery device.

[0177] The computer system 170 can be a personal computer or laptop computer, a tablet computer, or other suitable data processing device. The computer 170 can be local (e.g., accessible via a direct wired connection such as a USB) or remote to the reader device 120, and can be (or include) software for data management and analysis and communication with components in the analyte monitoring system 100. The operation and use of the computer 170 are further described in the '225 publication incorporated herein by reference. The analyte monitoring system 100 can also be configured to operate with a data processing module (not shown), also as described in the incorporated '225 publication.

[0178] The trusted computer system 180 may be used to perform authentication of a user, the sensor control device 102, and / or the reader device 120; to store confidential data received from the device 102 and / or 120; to output confidential data to the device 102 and / or 120; to name a few. The trusted computer system 180 may include one or more computers, servers, networks, databases, etc. In some embodiments, the trusted computer system 180 may include a cloud computing platform including one or more servers. The trusted computer system 180 may be owned physically or virtually through a secure connection by a manufacturer or distributor of the sensor control device 102, or may be maintained and operated by a different party (e.g., a third party).

[0179] Trusted computer system 180 can be trusted because system 100 can assume that computer system 180 provides authentic data or information. Trusted computer system 180 can be simply trusted because it is under the ownership or control of the manufacturer, for example, like a typical network server. Alternatively, trusted computer system 180 can be implemented in a more secure manner, such as by requiring additional passwords, encryption, firewalls or other Internet access security enhancements, which further prevent attacks by counterfeiters or computer hackers.

[0180] Data processing and software execution within the system 100 may be performed by one or more processors of the reader device 120, the computer system 170, and / or the sensor control device 102. For example, raw data measured by the sensor 104 may be processed by an algorithm into a value that is representative of the analyte level and readily displayable to a user, and this may occur in the sensor control device 102, the reader device 120, or the computer system 170. This information and any other information derived from the raw data may be displayed in any manner described above (with respect to the display 122) on any display resident on any of the sensor control device 102, the reader device 120, or the computer system 170. The user may use this information to determine any necessary corrective actions to ensure that the analyte level remains within an acceptable and / or clinically safe range.

[0181] Figure 2A and Figure 2B 1 and 102, respectively. As discussed above, the reader device 120 may be a mobile communication device such as, for example, a Wi-Fi or Internet-enabled smartphone, tablet computer, or personal digital assistant (PDA). Examples of smartphones may include, but are not limited to, a computer based on operating system, operating system, Operating system, PALM Operating system or Those mobile phones that use an operating system and have a network connection for data communication through the Internet or a local area network (LAN).

[0182] The reader device 120 can also be configured as a mobile smart wearable electronic device assembly, such as an optical assembly (e.g., smart glass or smart glasses) worn above or near the user's eyes. The optical assembly can have a transparent display that displays information about the user's analyte level (as described herein) to the user while allowing the user to view through the display so that the user's overall vision is minimally obstructed. The optical assembly can be capable of wireless communication similar to a smartphone. Other examples of wearable electronic devices include devices worn around or near a user's wrist (e.g., a watch, etc.), neck (e.g., a necklace, etc.), head (e.g., a headband, a hat, etc.), chest, etc.

[0183] Figure 2A is a block diagram of an exemplary embodiment of a reader device 120 according to various embodiments disclosed herein. In this example, the reader device 120 is in the form of a smartphone on which the various software, applications, and graphical user interfaces disclosed herein may reside. Here, the reader device 120 includes an input component 121, a display 122, and processing hardware 206, which may include one or more processors, microprocessors, controllers, and / or microcontrollers, each of which may be a discrete chip, or distributed among multiple different chips (and portions thereof). Here, the processing hardware 206 includes a communication processor 222 with on-board non-transitory memory 223 and an application processor 224 with on-board non-transitory memory 225. The reader device 120 also includes an RF transceiver 228 coupled to an RF antenna 229, a memory 230, a multifunction circuit 232 with one or more associated antennas 234, a power supply 226, and a power management circuit 238. Figure 2Ais a simplified representation of the internal components of a smartphone, and may of course include other hardware and functionality (e.g., codecs, drivers, glue logic, etc.).

[0184] The communication processor 222 may interface with the RF transceiver 228 and perform analog-to-digital conversion, encoding and decoding, digital signal processing, and other functions that help convert voice, video, and data signals into a format suitable for providing to the RF transceiver 228 (e.g., in-phase and quadrature), which may then transmit the signals wirelessly. The communication processor 222 may also interface with the RF transceiver 228 to perform the inverse functions required to receive wireless transmissions and convert them into digital data, voice, and video.

[0185] The application processor 224 may be adapted to execute an operating system and any software applications resident on the reader device 120 (such as any sensor interface applications or analyte monitoring applications including, for example, the SLL 304), process video and graphics, and perform other functions unrelated to processing communications sent and received via the RF antenna 229. Any number of applications may be running on the reader device 120 at any time, and typically include one or more applications related to a diabetes monitoring regimen in addition to other commonly used applications unrelated to a diabetes monitoring regimen (e.g., email, calendar, weather, etc.).

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

[0187] The multifunction circuit 232 may be implemented as one or more chips and / or components, including communication circuitry, that performs other functions, such as local wireless communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy) and determining the geographic location of the reader device 120 (e.g., Global Positioning System (GPS) hardware). One or more other antennas 234 are associated with the functional circuit 232 as desired.

[0188] The power source 226 may include one or more batteries, which may be rechargeable or disposable batteries for single use. The power management circuit 238 may regulate battery charging and power monitoring, boost voltage, perform DC conversion, etc. As described above, the reader device 120 may also 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 communicating with a remote computer system 170 (see Figure 1 ) or sensor control device 102, etc. for data communication.

[0189] Figure 2B is a schematic block diagram depicting an exemplary embodiment of a sensor control device 102 having an analyte sensor 104 and sensor electronics 250 (including analyte monitoring circuitry). Although any number of chips may be used, in many embodiments, most of the sensor electronics 250 are incorporated on a single semiconductor chip 251, which may be, for example, a customized application specific integrated circuit (ASIC). Shown within the ASIC 251 are several high-level functional units, including an analog front end (AFE) 252, a power management circuit 254, a processor 256, and communication circuitry 258 (which may be implemented as a transmitter, receiver, transceiver, passive circuit, or otherwise implemented according to a communication protocol). Figure 2B In the embodiment shown in , both AFE 252 and processor 256 function as analyte monitoring circuits, but in other embodiments, either circuit can perform analyte monitoring functions. Processor 256 may include one or more processors, microprocessors, controllers, and / or microcontrollers.

[0190] A non-transitory memory 253 is also included in the ASIC 251 and can be shared by various functional units present in the ASIC 251, or can be distributed between two or more functional units therein. The memory 253 can be a volatile and / or non-volatile memory. In this embodiment, the ASIC 251 is coupled to a power supply 260, which can be a button battery or the like. The AFE 252 interfaces with the in vivo analyte sensor 104 and receives measurement data therefrom, and outputs the data in digital form to the processor 256, which in turn processes the data to derive final results, analyte discrete values ​​and trend values, etc. The data can then be provided to the communication circuit 258 for transmission to the reader device 120 (not shown) via the antenna 261, where further processing can be performed by, for example, a sensor interface application. It should be noted that the functional components of the ASIC 251 can also be distributed between two or more discrete semiconductor chips. For example, in some embodiments, communication circuit 258 may be a semiconductor chip separate from ASIC 251 and may be configured to process signals received from in vivo analyte sensor 104, for example, via ASIC 251, into end result analyte discrete and trend values.

[0191] The performance of the data processing functionality within the electronics of the sensor control device 102 provides the system 100 with flexibility to schedule communications from the sensor control device 102 to the reader device 120 , which in turn limits the amount of unnecessary communications and can further save power at the sensor control device 102 .

[0192] When analyte information is available, the information may be automatically and / or continuously communicated from the sensor control device 102 to the reader device 120 or may not be automatically and / or continuously transmitted but rather stored or recorded in a memory of the sensor control device 102, such as for later output.

[0193] Data can be sent from the sensor control device 102 to the reader device 120 under the initiative of the sensor control device 102 or the reader device 120. For example, in many exemplary embodiments, the sensor control device 102 can periodically transmit data in an unprompted manner so that a qualified reader device 120 (if within range and in a listening state) can receive the transmitted data (e.g., sensed analyte data). This is initiated by the sensor control device 102 because the reader device 120 does not have to first send a request or other transmission to prompt the sensor control device 102 to communicate. For example, the transmission can be performed using an active Wi-Fi, Bluetooth, or BTLE connection, and can be transmitted according to a schedule programmed in the device 102 (e.g., approximately every 1 minute, approximately every 5 minutes, approximately every 10 minutes, etc.). The transmission can also occur in a random or pseudo-random manner, such as whenever the sensor control device 102 detects a change in the sensed analyte data. In addition, the transmission can occur in a repeated manner regardless of whether the reader device 120 actually receives each transmission.

[0194] The system 100 may also be configured so that the reader device 120 sends a transmission that prompts the sensor control device 102 to transfer its data to the reader device 120. This is often referred to as "on-demand" data transmission. On-demand data transmission may be initiated via a user interface of the reader device 120 based on a schedule stored in a memory of the reader device 120, or at the command of a user. For example, if a user wants to check his or her analyte level, the user may scan the sensor control device 102 using an NFC, Bluetooth, BTLE, or Wi-Fi connection. Data exchange may be accomplished using broadcast, session-based transmission, on-demand transmission, or any combination thereof.

[0195] 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 the bodily fluid and electrically coupled to the electronics within the device 102, the sensor-derived analyte information may be transmitted on-demand or in an autonomous manner from the sensor control device 102 to the reader device 120. The on-demand transmission may occur by first powering on the reader device 120 (or may be powered continuously) and executing a software algorithm stored in and accessed from a memory of the reader device 120 to generate one or more requests, commands, control signals, or data packets to send to the sensor control device 102. For example, the software algorithm executed under the control of the processing hardware 206 of the reader device 120 may include a routine to detect the position of the sensor control device 102 relative to the reader device 120 to initiate the transmission of the generated request commands, control signals, and / or data packets.

[0196] Exemplary embodiments of methods for associating analyte data with dietary information

[0197] In many embodiments, the subject matter described herein is implemented by a software application that is stored in a memory and executed by a processor-based device, such as any one of a reader device (e.g., a smartphone), a drug delivery device, or any other computing device described herein. In certain embodiments, the software is implemented as one or more downloadable software applications ("Apps") on a reader device, such as a mobile communication device or a smartphone.

[0198] The software can provide a mechanism for the user to define consumables (e.g., food types, beverage types, or portions thereof) in a user-friendly manner. These consumables are generally referred to herein as one or more meals, and these terms are widely used to represent all types of food and beverages.

[0199] The software may perform many functions related to the collection of dietary information and the association of that dietary information with analyte information collected by the in vivo analyte sensor 104 or by in vitro test strips and meters or from a trusted computer system 180. Hereinafter, the software is generally referred to as a "diet monitor application," "diet monitoring application," or "diet monitoring app."

[0200] The meal monitor application may allow an individual to record information about each meal consumed by the individual (ie, each "meal event"). The meal monitor application may correlate analyte data from relevant time periods during which the user's log entries indicate that a meal has been consumed.

[0201] The dietary monitor application may also monitor the user's analyte data and identify when the analyte data changes in a manner that indicates or suggests a potential dietary event has occurred, and seeks to associate dietary information for a relevant time period with the potential dietary event. The dietary monitor application may prompt the individual to enter dietary information associated with a potential dietary event and allow the individual to modify the time of the detected dietary event. In some embodiments, if a dietary event has been detected and the dietary monitor application determines that dietary information has been entered, the user may not be prompted.

[0202] The dietary monitor application can also associate the measured analyte response with the dietary event and store the result in a non-transitory memory or database. Specifically, the dietary monitor application can (for example, in the form of a list, in which each meal is sorted in descending order of the blood glucose response amplitude, taking glucose as an example) display each meal to the user with its associated analyte (for example, glucose or other analytes) response. In addition, the analyte response for each dietary event can be depicted with an easy-to-understand graphical representation. For example, if the analyte response to the meal is relatively low (i.e., favorable), the name of the meal can be displayed near the green indicator to indicate that the analyte response caused by the meal falls within a predetermined low analyte response range. Similarly, if the analyte response to the meal is relatively high (i.e., undesirable), the name of the meal can be displayed near the orange indicator to convey that the analyte response caused by the meal falls within a predetermined high analyte response range. In some embodiments, a numerical value indicating an increase in analyte levels can also be displayed near the graphical representation.

[0203] Another aspect of the meal monitor application includes detecting a peak analyte value from the analyte response after a meal. Methods for determining the peak analyte metric are further described herein. Another exemplary embodiment of the analyte response amplitude is to determine the difference between the peak analyte value after a meal and the analyte value detected at the beginning of the meal.

[0204] Yet another aspect of the meal monitor application includes analyzing analyte responses for the same or similar meals. For example, if a user consumes the same or similar meal on repeated occasions, a weighted average of the meal may be determined and displayed. Additionally, in some embodiments, the weighted average may give more weight to the analyte data that was collected most recently.

[0205] Exemplary embodiments of the meal monitor application may use analyte data analysis software or software-implementable processes, such as, for example, as disclosed in U.S. Patent Publication Nos. 2013 / 0085358, 2014 / 0350369, 2014 / 0088393, 2018 / 0128007, 2017 / 0185748, 2020 / 0105397, 2021 / 0030323, 2022 / 0000399, or International Publication Nos. WO 2015 / 153482 or PCT / US20 / 12134, all of which are incorporated herein in their entirety and for all purposes. Exemplary embodiments of the software are collectively referred to herein as "meal event detectors". A dietary event detector may be an algorithm, routine, or other set of instructions (as part of a dietary monitor application or separate therefrom) that may detect and / or quantify the occurrence of actual or potential dietary events in an individual's monitored analyte data.

[0206] Reference now Figure 3A , which is a flowchart depicting an exemplary embodiment of a method 300 for collecting dietary information, associating with analyte data, and determining the glycemic impact of the meal. The method 300 includes actions that can be described as being performed by an electronic device, such as a reader 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 professional, or other person. By way of example only, the method 300 will be described with reference to a diabetic patient using a dietary monitor software as a downloaded app on a reader device 120 configured as a smartphone. For ease of illustration, in this embodiment and other embodiments described below, the monitored analyte will be glucose, but other analytes may also be monitored, as noted herein.

[0207] refer to Figure 3A , a meal event may be recorded by a user at 302. The user may, at his / her discretion, enter the meal information (via a user interface) directly into the reader device 120 before, during, or after consuming the meal. In some implementations, the user enters the meal information in response to a reminder generated by the meal monitor application according to a predetermined schedule that may be set and / or modified by the user.

[0208] At 304, the user's analyte data is monitored. The analyte data monitoring step can be performed by various systems in various ways, such as Figure 1 and FIG. 3B to FIG. 3E In one exemplary embodiment, system 325 ( Figure 3B ), the user's analyte data can be transmitted from the sensor control device 102 (having the analyte sensor 104) worn on the user's body to the reader device 120, where the analyte data is received by the sensor interface application 327 resident thereon. Next, the sensor interface application 327 can transmit the analyte data to the trusted computer system 180 via the network 190, where the analyte data can be further processed or aggregated with other analyte data. Subsequently, the relevant analyte data is then transmitted from the trusted computer system 180 to the meal monitor application 329, which also resides on the reader device 120. In one aspect, according to the system 325, the sensor interface application 327 and the meal monitor application 329 can be separate software programs resident on a single reader device 120.

[0209] Figure 3CAnother exemplary embodiment of a system 330 for monitoring analyte data of a user is depicted, except that the sensor interface function 327 includes a module within a meal monitor application 329. According to one aspect of the system 330, the sensor interface function 327, which may be authorized to communicate directly with the sensor control device 102, may receive analyte data from the sensor control device 102, which may then be analyzed by the meal monitor application 329. Subsequently, the meal monitor application 329 may transmit the analyte data to the trusted computer system 180 via the network 190, where further processing of the analyte data may occur. In some embodiments, the meal monitor application 329 may also be configured to transmit meal information to the trusted computer system 180.

[0210] In another embodiment, Figure 3D A schematic diagram of another exemplary embodiment of a system 335 is depicted, wherein a sensor interface application 327 resides on a first reader device 120A and a meal monitor application 329 resides on a second reader device 120B. According to one aspect of the system 335, the sensor control device 102 may transmit analyte data directly to the sensor interface application 327, which in turn transmits the analyte data to the trusted computer system 180 via the network 190. Subsequently, the meal monitor application 329 residing on a separate reader device 120B may receive the analyte data from the trusted computer system 180. In some embodiments, the meal monitor application 329 may also be configured to transmit the meal information to the trusted computer system 180.

[0211] In yet another embodiment, Figure 3E A schematic diagram depicting another exemplary embodiment of a system 340 in which analyte data is manually entered or transmitted into a meal monitor application 329 without direct communication with a sensor control device or a trusted computer system. For example, the system 340 can be used with a meal monitor application 329 in an "unlinked mode," as described below with respect to Fig.10 Further described.

[0212] In any of the foregoing systems, information indicating the time at which each analyte data measurement was collected (e.g., a timestamp) may also be transmitted to the reader device 120. As already described herein, such data transmission may be performed on demand (e.g., by a user performing a scan), in a streaming manner, or in other regularly occurring manners. Analyte data collected by discrete blood glucose measurements (e.g., such as using a meter to read a test strip) may also be manually or automatically input into the reader device 120.

[0213] Return to reference Figure 3A, the reader device 120 may algorithmically process the collected analyte data at 306 and determine whether a meal event has occurred. This may be accomplished by using, for example, Figure 3F The method for detecting a dietary event described herein is implemented by checking one or more conditions in the analyte data indicating the occurrence of a dietary event. The algorithmic processing can also be repeated frequently, for example, each time new analyte data is received from the sensor control device 102, such as in response to an NFC scan of the sensor control device 102 by a user using a reader device 120 or other means. Manual recording of dietary information (302) by a user can be performed simultaneously with monitoring (304) and processing (306) of analyte data. Those skilled in the art will appreciate that these methods can be implemented in a system in which analyte data is autonomously and wirelessly transmitted from a sensor control device to a reader at predetermined intervals.

[0214] Still reference Figure 3A Each time new data is transmitted to the reader device 120, algorithmic processing may be applied to the new data, which may represent a time period of multiple hours (e.g., such as the past 8 hours), to detect meal events. Steps 308 to 320 may be performed for each meal detected, starting with the most recently detected meal, and repeated for each additional detected meal event.

[0215] If a meal event is detected at 306, then at 308, the meal monitor application evaluates whether the meal information corresponding to the detected meal event has been entered (such as input by the user at 302). This evaluation can be performed by checking a time period before the time when the detected event occurs, and a limited time after the detected time (e.g., to compensate for inaccuracies in timing or input), to see whether any meal information is entered during the time period. If meal information is entered, then at 314, the meal monitor application can associate the meal information with the detected event. In some embodiments, if multiple meal information entries are found, the meal monitor application can associate all entries with the detected event, or can associate the detected event only with the meal information that occurs closest in time.

[0216] If no dietary information that can be associated with the detected event is entered, the user is prompted to enter dietary information at 310. If no dietary event occurs, the user can reject or ignore the prompt. Otherwise, dietary information can be entered at 312.

[0217] The reminder can take the form of an alarm notification, such as a vibration or sound, which prompts the user to activate the meal monitor application to view the reminder. Alternatively, the reminder can be a notification that appears the next time the user views the application.

[0218] Whether the user records the meal information at his / her own discretion (302) or in response to (312) a prompt (310), the meal information may include various levels of detail and may be entered in the same or similar manner.

[0219] Return to reference Figure 3A Once the information of the meal event has been input at 312, the meal monitor application associates the analyte data with the meal information in memory at 314. Specifically, analyte data occurring around the meal event time can be associated with the information of the meal event. The analyte data selected to be associated with the meal event can be selected based on the time during which the meal event occurs and optionally the time period after the meal event occurs to reflect changes in analyte levels due to meal digestion.

[0220] In some embodiments, the analyte data occurring in a time period after the meal stops from the time when the meal starts can be associated with the meal event. In addition, the analyte data that the glucose offset ends from the meal start to the detection can be associated with the meal event. In some embodiments, the analyte data collected during the fixed time range around the meal event are associated with the meal event, for example, from one hour before the meal event, two hours or three hours (for example, as measured by the beginning of the meal event, the median time of the meal event or the end of the meal event) to any combination of one hour, two hours, three hours, four hours, five hours, six hours, seven hours or eight hours after the meal event. In each case, the time when the meal event occurs can be based on the information identification meal event input by the user or the time when the meal event occurs can be identified by the algorithm by analyzing the analyte data.

[0221] At 316, the association of the analyte data with the meal event can be used to determine the glycemic impact of the meal event. In some embodiments, the glycemic impact of the meal event can be determined algorithmically with reference to the analyte data that occurs concurrently with the meal event, and the algorithmic processing can constitute both steps 314 and 316. The determined glycemic impact can be quantitatively determined based on the maximum (peak) or minimum glucose level, the median or mean glucose level, the minimum to maximum change in glucose level (delta (Δ) glucose value), the percentage change in glucose level, the duration of the glucose response, the rate of change of the glucose level, the area of ​​the glucose response, and any combination thereof.

[0222] The meal event detector outputs information about the glycemic response to the meal, which can be used to characterize the magnitude or severity of the response. For example, the meal event detector can output the start time and peak time for each detected meal event. The meal start glucose can be the glucose value at the meal event start time, and the peak glucose can be the glucose value when the rising phase of the detected meal event reaches a peak. The difference of these glucose values ​​can be determined to provide an incremental glucose measurement of the glycemic response to the meal.

[0223] Return to reference Figure 3A The determined blood glucose response or impact may then be output to the user at 318, such as visually displayed on a display of a smartphone, as will be described below with respect to 7A to 7I Described. The determined blood glucose response can be output in a quantitative and / or qualitative manner. For example, at 316, the determined blood glucose response can be output in the same quantitative measurement in which it is determined. This can be done in text and / or graphical form. In addition, the determined blood glucose response can be output qualitatively, for example, described in text as low or slight, moderate or moderate, or high or severe, or any synonyms thereof. Fewer or more amplitude divisions can also be used. The determined blood glucose response can also or alternatively be output as an icon or other image (e.g., colored shapes of various amplitude levels).

[0224] Return to reference Figure 3A , method 300 can repeat itself such that the meal monitor application continues to receive, monitor, and store analyte data (e.g., step 304 of method 300), and continuously searches for detected events 306. The most recently entered information about detected or recorded meals can be included in the option provided to the user for entering meal information each time a new event is detected.

[0225] As will be described below, the information output by the dietary monitoring application provides users with specific, easy to understand, and immediate information about the effects of their meals on their analyte levels. The output information can help users learn to avoid or minimize certain meals in their diet that they were not aware of affecting their glucose levels, for example, they were not aware of causing their glucose levels to be so high. The output information can also help users learn to control the size of their meals by observing the relative effects of different servings on their glucose levels.

[0226] An exemplary embodiment of a method for associating analyte data with dietary information will now be described. Figure 3F, a flowchart depicts an exemplary embodiment of a method 350 for associating analyte data with dietary information, wherein the dietary information was not previously input by a user. First, one skilled in the art will recognize that the method 350, whether as a whole or any one or more of the individual steps, may be associated with Figure 3A Method 350 is implemented in conjunction with or as a part of method 300. Method 350 begins at 352, where data indicating a user's analyte level is received. For example, in some embodiments, this may occur when a user scans their sensor control device with their reader device. In other embodiments, if the sensor control device is configured to wirelessly stream analyte data to the reader device, this may occur autonomously. At 354, a peak analyte level value within a predetermined time period of the received analyte data is identified. For example, in some embodiments, this may require identifying the 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.). In addition, 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 two hours of analyte data, the last four hours of analyte data, the last eight hours of analyte data, the past twelve hours of analyte data, etc.).

[0227] Still reference Figure 3F At 356, an estimated meal start time and an initial analyte level value associated therewith may be determined. For example, in some embodiments, the estimated meal start time may be identified by counting down from the time of the peak analyte level value (e.g., two hours before the peak analyte level value, three hours before the peak analyte level value, four hours before the peak analyte level value, etc.). The initial analyte level value may be determined by reference to the analyte level reading for the estimated meal start time.

[0228] Subsequently, at 358, an analyte level variance value is determined by subtracting the initial analyte level value from the peak analyte level value. Method 350 may then prompt the user to enter dietary information at 360. At 362, the entered dietary information is associated with the analyte level variance value and stored in memory.

[0229] Go to Figure 3G , a flowchart depicts an exemplary embodiment of a method 370 for associating analyte data with dietary information, wherein the dietary information has been input by a user. First, one skilled in the art will recognize that the method 370, whether as a whole or any one or more of the individual steps, may be associated with Figure 3A Method 300 is implemented in combination with or as a part thereof. Figure 3GAs seen at the top of , method 370 begins at 372, where dietary information is entered by a user. For example, in some embodiments, this can be a dietary entry actively entered by the user without any prompt from the dietary monitor application. In other embodiments, the user can enter dietary information in response to a prompt displayed by the dietary monitor application. For example, according to some embodiments, if no dietary entry is entered after a predetermined reminder time period (e.g., no dietary entry in the past week, no dietary entry in the past three days, no dietary entry in the past day, etc.), the dietary monitor application can be configured to display a reminder notification to the user (e.g., Figure 4F 440).

[0230] Subsequently, at 374, data indicative of the user's analyte level is received by the meal monitor application within a predetermined amount of time. In some embodiments, this may require the user to scan their sensor control device within a predetermined amount of time from the meal entry time (e.g., within four hours of the meal entry, within eight hours of the meal entry, within twelve hours of the meal entry, etc.). In other embodiments, this may occur autonomously if the sensor control device is configured to wirelessly stream analyte data to the reader device.

[0231] Still reference Figure 3G , at 376, a peak analyte value in the analyte data is identified. In some embodiments, this may require identifying the highest glucose value that exceeds a predetermined analyte level threshold (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL, etc.). The peak analyte value may also be a glucose value that exceeds a predetermined analyte level threshold within a time window after the meal entry (e.g., during a two-hour window after the meal entry, during a three-hour window after the meal entry, or during a four-hour window after the meal entry). Then, at 378, an initial analyte level value is determined. According to some embodiments, the initial analyte level value may be determined by determining an analyte level value at or near the meal entry time.

[0232] Subsequently, at 380, an analyte level variance value may be determined, for example, by subtracting the initial analyte level value from the peak analyte level value.The analyte level variance value may then be associated with the meal entry entered by the user and stored in memory at 382.

[0233] Example Implementation of a Meal Monitor Application GUI and Related Features

[0234] An exemplary embodiment of various GUIs and related software features of a meal monitor application that can perform any of the above methods 300, 350, and 370 will now be described. Those skilled in the art will appreciate that these various interfaces can be displayed on any embodiment of the reader device 120 (e.g., a smartphone), medication delivery device 160, or local computer system 170 described herein.

[0235] Exemplary Implementation of Home Page GUI and Related GUIs

[0236] Figures 4A-1 to 4A-7 An exemplary implementation of a home page GUI (also referred to herein as a "home screen GUI") and its associated features for use with a meal monitor application is shown.

[0237] refer to Figure 4A-1 , depicts an exemplary embodiment of a home page GUI 400 for a meal monitor application. According to one aspect of the embodiment, the home page GUI 400 may include a plurality of selectable sections, including, but not limited to, a user profile section 402, a meal entry section 404, a trend section 406, a diary section 412, and a report section 414. User selection of a section may cause the meal monitor application to display one of the corresponding GUIs described in more detail below. In some embodiments, the home page GUI 400 may also include a navigation bar 416 (bottom), an email button 408 (top) for requesting manufacturer support, 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 monitor application to display a notification log, such as Fig.4O GUI 440 is shown.

[0238] Figure 4A-2 An exemplary embodiment of a home page GUI for use with a meal monitor application is depicted. Specifically, Figure 4A-2 A home page GUI 450 is depicted, which is similar to Figure 4A-1 . According to one aspect of some embodiments, the home page GUI 450 includes an information button 455 (top) that is configured to display a plurality of selectable links that, when selected by the user, cause the meal monitor application to display a GUI corresponding to the selected link. In addition, the home page GUI 450 also includes a banner 451 that includes a message reminding the user to scan the sensor every eight hours to see the impact of all meals. In some embodiments, the banner 451 is displayed directly adjacent to and distal to the greeting and user name displayed on the user profile portion 453.

[0239] Figure 4A-3 and Figure 4A-4Another exemplary embodiment of a home page GUI for use with a meal monitor application is shown. Figure 4A-3 and Figure 4A-4 A home page GUI 460 is depicted, which is similar to the home page GUIs 400 and 450 and can include a number of selectable sections, including, but not limited to, a user profile section 4002, a meal entry section 4004, a trend section 4006, a diary section 4012, and a report section 4014. Similar to the home page GUIs 400 and 450, the home page GUI 460 can also include a navigation bar 4016 (bottom). According to one aspect of an embodiment, the home page GUI 460 can also include: (1) a meal card 4100; (2) a trend card 4200; (3) a challenge card 4300; and (4) a recommendation card 4400. In addition, the home page GUI 460 can include a banner 461 that includes a message reminding the user to scan the sensor every eight hours to see the impact of all meals. In an exemplary embodiment, the user profile section 4002 of the home page GUI 460 displays a user name, wherein the user name is directly adjacent to and displayed near the banner 461.

[0240] In addition, according to one aspect of the embodiment, the home page GUI 460 can be configured to be scrollable and dynamic. Therefore, in some embodiments, the content displayed on the home page GUI 460 can change in response to a predetermined input of the user, such as when the user scrolls, drags, pulls the screen, or through some other predetermined gestures. In this way, the home page GUI 460 can include multiple views, wherein each view is configured to display a portion of the home page GUI 460 to the user. Specifically, in some embodiments, the home page GUI 460 can be configured to switch between multiple views, wherein each of the multiple views is different. More specifically, the home page GUI can be configured to switch between views in response to a predetermined input of the user.

[0241] In an exemplary embodiment, the home page GUI includes at least a first view and a second view. Figure 4A-5 As depicted, in a first view of the scrollable home page GUI 460, a user profile section 4002, a meal entry section 4004, a diary section 4012, and a meal card 4100 may be displayed on the home page GUI 460. Additionally, in a second view of the scrollable home page GUI 460, and as shown in FIG. Figure 4A-6 As shown, trend cards 4200, challenge cards 4300, and recommendation cards 4400 are displayed on the home page GUI 460. According to one aspect of the embodiment, the navigation bar 4016 is configured to remain fixed on the home page GUI 460 and is displayed in all views of the scrollable home page GUI 460 (e.g., Figure 4A-5 and Figure 4A-6shown).

[0242] In some embodiments, and still with reference to Figure 4A-3 and Figure 4A-4 , the meal card 4100 is configured to display one or more meal lists 4101 that include meal information associated with one or more of the most recently consumed meals. Specifically, each meal list 4101 provides detailed information about a particular meal consumed by the user and its corresponding meal-related blood glucose response. In some exemplary embodiments, the one or more meal lists 4101 may be sorted so that the meal list 4101 corresponding to the most recently consumed meal is presented first or is located at the top of the meal card 100, and subsequent meal lists 4101 are displayed in chronological order. In some embodiments, and as Figure 4A-3 and Figure 4A-4 As best shown, each meal listing 4101 may include: (1) a textual description 4102 of the meal / food (e.g., Figure 4A-4 4106 indicating the user's glycemic response to the corresponding meal.

[0243] In many embodiments, and as Figure 4A-3 and Figure 4A-4 As depicted, graphical representation 4106 may include segment shapes (e.g., arches, circles, bars), where each segment includes a different color (or no color at all). Each color may correspond to an analyte response range or ranking. For example, Figure 4A-3 and Figure 4A-4 As shown in each of the meal lists 4101 depicted in , the semicircular (or "rainbow") shape can include three segments, where: (1) the first segment can have a green color to indicate a low glycemic response; (2) the second segment can have a yellow color to indicate a moderate glycemic response; or (3) the third segment can have an orange color to indicate a high glycemic response to the meal / food.

[0244] According to another aspect of the embodiment, different colors can each indicate that the method 300, 350, or 370 (as described with respect to Figure 3A , Figure 3F and Figure 3GThe first segment is green (and the other segments are gray) to indicate that the meal / food caused a low glycemic response or a small effect. As another example, if the analyte level variance value is determined to be within a medium analyte level variance range (e.g., between 60 mg / dL and 100 mg / dL, or between 3.3 mmol / L and 5.6 mmol / L), the second segment is yellow (and the other segments are gray) to indicate that the meal / food caused a medium glycemic response or a medium effect. As another example, if the analyte level variance value is determined to be within the high analyte level variance range (e.g., greater than 100 mg / dL or greater than 5.6 mmol / L), the third segment is orange (and the other segments are gray) to indicate that the meal / food caused a high glycemic response or high impact.

[0245] According to another aspect of the embodiment, one or more conditions may cause all segments to be gray, such as if the analyte level variance value is below zero, if the analyte level variance value is above a maximum analyte level variance value (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL), or if the initial analyte level value is above a maximum initial analyte level value (e.g., 180 mg / dL, 200 mg / dL, 220 mg / dL, 250 mg / dL, etc.) One or more of these conditions may indicate that the determined analyte level variance value is either unreliable to be accurately calculated, or otherwise does not represent an analyte level variance value associated with dietary consumption.

[0246] In addition, although the graphical representation 4106 shown is a segmented semicircle with three colored segments, those skilled in the art will appreciate that other geometric shapes, colors, and numbers of segments may be used and are well within the scope of the present disclosure. Likewise, as described above, each color may represent a specific range of values. However, those skilled in the art will appreciate that other ranges may be used in addition to the listed ranges, and that these numbers are not meant to be limiting.

[0247] Still reference Figure 4A-3 and Figure 4A-4, and according to another aspect of the embodiment, the trend card 4200 of the homepage GUI 460 can be configured to present recent trend information related to the analyte response associated with the user's food selections. In some exemplary embodiments, the trend card includes a summary panel 4201, which can provide an overall assessment of the user's food selections over a specific time period (e.g., the last day, last week, or last month). By way of illustration, Figure 4A-3 The summary panel for 4201 states that the user's "food choices resulted in a 33% decrease in green choices." Additionally, Figure 4A-4 The summary panel 4201 states that the user's "food choices resulted in a 25% decrease in green choices."

[0248] In some embodiments, and as Figure 4A-3 and Figure 4A-4 As depicted, trend card 4200 also includes a graphical representation 4202 indicating analyte responses associated with a user's meals / food choices over a particular time period. In some embodiments, graphical representation 4202 includes a segment shape, wherein each segment includes a different color (or no color at all), wherein each color can correspond to an analyte response range or ranking. In an exemplary embodiment, graphical representation 4202 can include a semicircular shape having three segments, wherein: (1) a first segment can have a green color to indicate a low glycemic response; (2) a second segment can have a yellow color to indicate a medium glycemic response; or (3) a third segment can have an orange color to indicate a high glycemic response associated with a user's food choices over a recent or particular time period.

[0249] In some embodiments, if analyte data (e.g., data indicating analyte levels, such as glucose levels) has not yet been received and / or associated with a meal / food entry, the trend card 4200 will not be displayed on the home page GUI 460. According to one aspect of the embodiment, the trend card 4200 is configured to be dynamic. Specifically, the dietary monitoring application can detect whether the analyte response associated with the user's food selection includes new trend information. If new trend information is detected, the trend card 460 is configured to update to populate an update summary panel 4201 including information related to the new trend information.

[0250] In some embodiments, and as Figure 4A-3 and Figure 4A-4As depicted, the homepage GUI 460 includes a challenge card 4300 configured to display one or more selectable challenge icons 4301. Each challenge icon 4301 represents a different challenge in which a user can participate, wherein each challenge is related to an analyte response or glucose level of the user. The challenges can suggest certain behaviors or activities to the user and provide seasonal and / or behavior-based challenges that can affect the user's analyte level and thereby help the user manage his or her diabetes. In some exemplary embodiments, the challenge icon 4301 can represent a challenge for a user to consume a predetermined number of consecutive meals that are classified as having a particular analyte response (e.g., Figure 4A-3 4 in a row” challenge icon depicted in , where 4 in a row challenge icon 4301 indicates a challenge associated with a user consuming four low-impact or low-glycemic meals in a row). Additionally, challenge icon 4301 may indicate a challenge associated with a user consuming a particular type of meal (e.g., Figure 4A-3 and Figure 4A-4 ). In yet another example, challenge icon 4301 may represent a challenge for a user to consume a certain number of portions of a food (e.g., vegetables or fruit) each day within a predetermined time period. In another example, challenge icon 4301 may represent a challenge for a user's lifestyle tendencies (e.g., a user to stay hydrated, avoid carbonated beverages, increase physical activity, or avoid fast food within a predetermined time period). Those skilled in the art may readily recognize various other challenges for use with a meal monitoring application.

[0251] According to one aspect of an embodiment, each challenge icon 4301 may include an image or picture 4302 associated with a particular challenge. In addition, the challenge icon 4301 may include a challenge title 4303 that provides a text description of the challenge represented by the corresponding challenge icon. In some embodiments, the challenge card 4300 may display different challenge icons 4301 in response to received user input (e.g., by a sliding gesture, a dragging gesture, or some other predetermined gesture). For example, in some embodiments, the challenge card 4300 may display a group of two or three challenge icons 4301. In response to the received input, the challenge card 399 may display a new group of challenge icons 4301 on the homepage GUI 460. In some embodiments, before receiving the user input, at least one of the challenge icons 4301 in the new group is different from at least one of the challenge icons 4301 in the original group.

[0252] In some implementations, once the user selects a challenge icon 4301, a new challenge icon 4301 will be displayed to replace the previously selected challenge icon 4301. In some implementations, the challenge icon 4301 may be scheduled to remain on the home GUI 460 for a predetermined period of time.

[0253] In addition, the challenge card 4300 may include an optional "View All" link 4304, which, when selected by the user, outputs a challenge GUI 1200 including a challenge list, wherein the challenge list displays all live challenges in which the user is participating, challenges successfully completed by the user, and challenges in which the user has not yet participated.

[0254] In addition, in some embodiments, the homepage GUI 460 displays a recommendation card 4400, which is configured to display one or more optional recommendation icons 4401, wherein each recommendation icon 4401 represents a different recommendation presented to the user. The recommendation can be related to the user's food selection and / or analyte response. The recommendation can suggest certain activities to the user and provide content based on seasons and / or behaviors (e.g., recommendations related to healthy eating before and after the holidays, or how to wear or remove sensors). In some embodiments, the recommendation icon 4401 can be linked to a trusted source related to the corresponding recommendation. According to one aspect of the embodiment, the dietary monitor application can process and analyze the input dietary entry data through an algorithm, and detect and / or quantify the user's food selection so as to push the recommendation through the recommendation icon 4401, which can be considered as a more desirable or beneficial recommendation for the user. For example, if the dietary monitoring application detects that the user often consumes chicken, a recommendation icon 4401 related to chicken can be displayed to the user. In addition, in another example, if the dietary monitor application detects that the user has a tendency to consume pizza, a recommendation icon providing a pizza substitute can be displayed to the user.

[0255] According to another aspect of the embodiment, after the user selects the recommendation icon 4401, a modal 4405 ( Figure 4A-7 ), wherein modality 4405 may provide contextual information related to the recommendation to guide the user to take action based on the recommendation. In some embodiments, the contextual information may prompt the user to participate in activities or behaviors consistent with the recommendation. For example, if the user selects the "Summer Vacation" recommendation icon 4401, as shown in FIG. Figure 4A-6 As depicted, a modal 4405 providing information related to summer vacation recommendations will be displayed on the home page GUI 460 (see, for example, Figure 4A-7 , "Log your meals, even while on vacation. Click the button below to add your meals now.") In some embodiments, and Figure 4A-7 As shown, modal 4405 may include a start button 4406 that, when selected by a user, allows the user to take steps to comply with the recommendation (e.g., Figure 4A-7 The "Add Food" button in allows the user to add a meal or food item to track meals while on vacation, consistent with summer vacation recommendations).

[0256] According to one aspect of the embodiment, and as Figure 4A-4 As best shown, each recommendation icon 4401 can include an image or picture 4402 related to its particular recommendation. The recommendation icon 4401 can also include a recommendation title 4403 that provides a text description of the corresponding recommendation. In addition, in some embodiments, the recommendation card 4400 can display different recommendation icons 4401 in response to receiving user input (e.g., via a slide gesture, a drag gesture, or some other second predetermined gesture). For example, in some embodiments, the recommendation card 4400 can display a group of two or three recommendation icons 4401. In response to the received input, the recommendation card 4400 can display a new group of recommendation icons 4401 on the home page GUI 460. In some embodiments, prior to receiving the user input, at least one of the recommendation icons 4401 in the new group is different from at least one of the recommendation icons 4401 in the original group.

[0257] In some implementations, once the user selects a recommendation icon 4401, a new recommendation icon 4401 will be displayed to replace the previously selected recommendation icon 4401. In some implementations, a particular recommendation icon 4401 may be scheduled to remain on the homepage GUI 460 for a predetermined period of time.

[0258] In some embodiments, and as Figure 4A-4 As best shown, the home page GUI 460 may also include an information button 4008 (top) that is configured to display a plurality of selectable links that, when selected by the user, may cause the meal monitor application to display a GUI corresponding to the selected link. Figure 4A-4 As best shown, selecting the information button 4008 may display: (1) a “Profile” link 4001; (2) a “Notifications” link 4003; (3) an “Order Your Next Sensor” link 4005; (4) a “Frequently Asked Questions” (“FAQ”) link 4007; (5) an “About Us” link 4009; and (6) a “Contact Us” link 4011.

[0259] For example, Figure 4B Depicted is an About Us GUI 470 displayed on a meal monitor application after a user selects an About Us link 4009 on the Home GUI 460. In some implementations, the About Us GUI 470 includes a plurality of selectable sections, including but not limited to a License section 471, a Privacy Policy section 472, and a Terms and Conditions section 473, which, when selected by a user, may display a corresponding GUI.

[0260] also, Figure 4CA contact us modal 474 is shown displayed on the meal monitor application after the user selects the About Us link 4011 on the home GUI 460. Specifically, the contact us modal 474 can be displayed on the home GUI 460 and can include contact information provided for the meal monitor application.

[0261] Figure 4D and Figure 4E An exemplary embodiment of a FAQ GUI 480 displayed on a meal monitor application after a user selects a FAQ link 4007 on the home GUI 460 is depicted. According to some embodiments, the FAQ GUI 480 includes a first question portion 481 having information related to starting the meal monitor application and a second question portion 482 having information related to adding or logging food on the meal monitor application. In some embodiments, the first question portion 481 and the second question portion 482 each include a list of selectable question links 483 that, when selected, are configured to expand to include a list of corresponding answers to the question described in the selected question link 483 (e.g., Figure 4E In some embodiments, the first question portion 481 and the second question portion 482 are configured to expand in response to a received user input (eg, a tap gesture or other predetermined gesture). Figure 4E ) and minimize ( Figure 4D ). Next, refer to FIG. 4F to FIG. 4I , depicts an exemplary implementation of a connection GUI when a user first starts a meal monitor application. In some implementations, after the user successfully starts the meal monitor application (and completes the onboarding process and tutorial), the meal monitor application may prompt the user to provide account information to connect the meal monitor application to the sensor interface application. For example, Figure 4F A modal is depicted requesting the user to connect the meal monitor application to the sensor interface application. Upon selecting the connect button 418 ( Figure 4F ), the meal monitor application may display an account login GUI 420, which includes an email field 422, a password field 424, and a login button 426, such as Figure 4G Once the user successfully logs in, a consent GUI 430 may be displayed to the user to obtain the user's consent to share data with the meal monitor application. Once the user agrees, they are returned to the home page GUI 400, where a modal 432 indicates that the meal monitor application has successfully connected to the sensor interface application.

[0262] Figure 4J-4NDepicted are additional exemplary embodiments of a connection GUI when a user first starts a meal monitoring application. Specifically, Figure 4J A modal is depicted requesting the user to connect the meal monitor application to the sensor interface application. Upon selecting the connect button 4180 ( Figure 4J ) thereafter, the meal monitor application may display an account login GUI 465, which includes an email field 4220, a password field 4240, and a login button 4260, such as Figure 4K Once the user successfully logs in, the consent GUI 475 ( Figure 4L ) to obtain the user's consent to share data with the meal monitor application. Once the user agrees, they return to the home page GUI 450 or 460, where the modal 4320 ( Figure 4M 4321 is displayed on the home GUI 450 or 460 indicating that the meal monitoring application successfully connected with the sensor interface application. In some embodiments, if the meal monitoring application did not successfully connect with the sensor interface application, a modal 4321 is displayed on the home GUI 450 or 460 indicating this (e.g., the connection failed because the attempted account credentials were already in use in another meal monitoring application, such as Figure 4N In some embodiments, and as Figure 4N As depicted, modal 4321 may include an ok button 4322 and a connect button 4323 .

[0263] Example Implementation of User Profile GUI

[0264] Next reference Figure 5A and Figure 5B , depicts an exemplary embodiment of a user profile GUI 500 for a meal monitor application. When a user selects the user profile section 402 on the home page GUI 400, the user profile GUI 500 is displayed. Figure 5A As shown, the user profile GUI 500 may include a plurality of editable fields configured to receive personal information about a user of the meal monitor application. In some embodiments, the user profile GUI 500 may 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. In addition, as shown in FIG. Figure 5BAs shown, the user profile GUI 500 may also include multiple optional options to prompt the user to provide additional profile information or preferences. For example, multiple optional options may include a medical condition field 518, a measurement unit field 520, and a medication field 522. According to another aspect of some embodiments, the user profile GUI 500 may also include a consent check box 524 to indicate whether the user wishes to opt-in (or opt-out) to receive additional information and / or marketing solicitations. In many embodiments, the user profile GUI includes an update button 526 to save any changes that the user may make to its profile information. In some embodiments, if the user has not yet connected the dietary monitor application to the sensor application, the user profile GUI 500 may also include a "link sensor application" button (not shown).

[0265] Figure 5C An additional exemplary embodiment of a user profile GUI 550 for a meal monitor application is depicted. Figure 5C Depicted is a user profile GUI 550, which in some implementations can be displayed when a user selects the user profile section 4002 on the home page GUI 460. The user profile GUI 550 is similar to the user profile GUI 500, except that it also includes a date of birth field 501, a gender field 503, and a consent checkbox 507 to indicate whether the user wishes to opt-in (or opt-out) of receiving personalized notifications. Figure 5D A user profile GUI 550 is depicted, also including a “Link Sensor Application” button 531 . Figure 5E A user profile GUI 550 is depicted in which a user has selected option button 532 (e.g., Figure 5D Specifically, when the user selects option button 532, user profile GUI 550 is configured to display a plurality of selectable links, including but not limited to reset password link 533, delete account link 534, and logout link 535 (eg, Figure 5E If the user selects the delete account link, the meal monitor application may display a modal 536 requesting the user to confirm that they want to proceed with deleting the account information (e.g. Fig. 5F shown).

[0266] According to another aspect of the embodiment, and as Figure 5G As depicted, the user may select profile icon 5004 to upload a photo / picture 5005 associated with the user profile. In some implementations, the user may select picture 5005 from a photo library. FIG. 5H to FIG. 5IAs shown, when the user selects profile icon 5004, a pop-up modal 537 can be displayed on the user profile GUI 550, wherein the pop-up modal 537 is configured to request access to the user's photos. Figure 5H depicts a pop-up modal 537 presented by a first mobile operating system (e.g., iOS), and Fig.5I A pop-up modal 538 is depicted being presented by a second mobile operating system (e.g., Android). In some implementations, when the user has not associated a photo 5005 with a user profile, a placeholder image will instead be displayed on the profile icon 5004 (e.g., as shown in FIG. FIG. 5C to FIG. 5F In some embodiments, and as FIG. 5C to FIG. 5F As shown, the placeholder image is the initial corresponding to the first letter of the name entered by the user (eg, "J" for a user named "John").

[0267] Example Implementation of a Meal Entry GUI

[0268] Go to FIG. 6A to FIG. 6E , depicts an exemplary embodiment of a meal entry GUI 600 for a meal monitor application. Fig. 6A , when the user selects the meal entry section 404 on the home page GUI 400, the meal entry GUI 600 is displayed. Alternatively, if the user selects the corresponding icon in the navigation bar (bottom), the meal entry GUI 600 may also be displayed. The meal entry GUI 600 may also include an information button 602 ( Figure 6C ) and a notification button 604 ( Fig.4O ).

[0269] One desirable aspect of the embodiments described herein is that dietary information can be easily entered. This can facilitate the use of dietary monitor applications and allow users to more intuitively understand the glycemic impact of dietary consumption, thereby improving the user's health. Fig. 6AAs shown, the meal entry GUI 600 may include an optional meal type option 606, and the user can easily indicate the meal type (e.g., breakfast, lunch, dinner, snacks, desserts, etc.) of the meal entry by the optional meal type option. According to another aspect of the embodiment, the meal entry GUI 600 may include a search / add field 608, which allows the user to enter the name of the food for the meal entry. When the user enters the characters of the meal or food name in the search / add field 608, the meal monitor application can automatically suggest entries based on the meal entry of the user in the past. For example, in some embodiments, the meal monitor application can retrieve information related to the past meal entry with the same (or similar) food name, and display it in the result section 612, for example as a list. The list can be sorted so that the most frequently consumed or selected meal is presented first or is at the top of the list, and the remaining meals are presented in the order of decreasing consumption frequency (e.g., the most frequently consumed meal is presented first, the second most frequently consumed meal is presented second, and so on, the least frequently consumed meal is presented last). In some embodiments, the list can be sorted based on the entry with the lowest impact (e.g., the lowest analyte level variance value) to suggest more favorable foods to the user. If the desired food name appears in the results section 612, the user can conveniently select the entry without having to type the full name of the food or meal and then press the add button 610.

[0270] In some embodiments, the meal entry GUI 600 may also include a voice recognition feature. According to one aspect of some embodiments, the user may press the voice recognition button 609 and speak the name of the meal or food, rather than manually typing the meal or food name into the search / add field 608. In response, the meal monitor application may be configured to display the closest results in the results section 612.

[0271] In addition, despite Fig. 6A The results portion 612 is shown in the form of a list, but those skilled in the art will appreciate that other interfaces can be implemented, such as by manually entering text, by selecting a meal name from a list (e.g., a selection list or drop-down list), by selecting a meal picture from a set of pictures, by selecting an identifiable indicia of the meal (e.g., a label or code), or any combination thereof.

[0272] According to another aspect of the embodiment, the meal entry GUI 600 may also include an active check box 614. Figure 6B As seen, when the activity checkbox 614 is selected, an activity text box 616 is presented on the meal entry GUI 600 that allows the user to enter a text description of any physical activity (e.g., walking, gardening, bicycling, etc.) they engage in around the meal event time.

[0273] According to another aspect of the embodiment, after entering the meal information (and optionally the activity information), the user may select the continue button 618, which may cause a modal configured to request additional information to be displayed, such as Fig.6D The modal may include, for example, a date field 620, a time field 622, and a meal portion field 624 to capture details of the meal event. Additionally, in some embodiments, the modal may include an "add note" checkbox 626 that, when selected by the user, presents a note text box 630 ( Fig. 6E ). This allows the user to enter additional notes while eating (e.g., specific information about the meal / food, medications taken by the user around the meal / food time).

[0274] In some embodiments, the time field may be automatically populated based on the time at which the user selects the continue button 618. According to one aspect of some embodiments, the user may still edit the automatically populated time field. In other embodiments, the time field may include a start time and a stop time during which the meal is consumed (rather than a start time such as Fig.6D In other implementations, the time field can be a generalized or heuristic part of the day (e.g., early morning, late afternoon, etc.), or an approximate time range (e.g., 6 to 7am, 5 to 6pm, etc.) with any desired level of granularity (e.g., 10 minutes, 15 minutes, 30 minutes, 60 minutes, etc.).

[0275] FIG. 6F to FIG. 6J Another exemplary embodiment of a meal entry GUI 650 for a meal monitor application is depicted. Fig. 6F , and with FIG. 6A to FIG. 6E , the meal entry GUI 650 may be displayed when the user selects the meal entry section 4004 on the home page GUI 460. Alternatively, the meal entry GUI 650 may also be displayed if the user selects the corresponding icon in the navigation bar (bottom). The meal entry GUI 650 may also include an information button 653 ( Figure 6J ).

[0276] like Fig. 6F As shown, the meal entry GUI 650 may include an optional meal type option 6506 by which the user can easily indicate the meal type of the meal entry (e.g., breakfast, lunch, dinner, snacks and beverages, etc.). According to another aspect of the embodiment, the meal entry GUI 650 may include a search / add field 6508 that allows the user to enter the name of the food for the meal entry (e.g., Figure 6G). In a similar manner to the search / add field 6508, as the user enters characters of a meal or food name in the search / add field 6508, the meal monitor application can automatically suggest entries based on the user's past meal entries. In some embodiments, once the user enters the name of a meal or food, or selects an entry populated by the auto-suggest function, a meal tag 6511 including the entered meal or food name is added to the meal library portion 6512 (in Figure 6G and Fig.6I ). A user may associate one or more meal tags 6511 with a consumed meal (e.g., in Fig.6I In , users have added "diet cola", "vegetable salad" and "ham sandwich" meal tags to their lunch entries 6511).

[0277] In some embodiments, the meal entry GUI 650 may also include a voice recognition feature 6509. According to one aspect of some embodiments, the user may press the voice recognition button 6509 ( Fig. 6F and Fig.6I ) and speak the name of the meal or food, rather than manually typing the meal or food name into the search / add field 6508.

[0278] According to another aspect of the implementation, the meal entry GUI 650 may include a portion indicator 6524 option indicating the relative size of the meal consumed, e.g., selectable buttons indicating different sized meals, such as "small," "medium," and "large" (e.g., in the Figure 6H Select the “Medium” portion indicator 6524).

[0279] In addition, the meal entry GUI 650 may also include a time field 6522 that includes the time and date associated with the meal entry. In some embodiments, the time field 6522 may be automatically associated with the meal entry, or automatically populated based on the time the user enters the meal entry. According to one aspect of some embodiments, the user may still edit the automatically populated time field 6522.

[0280] According to another aspect of the embodiment, after entering the meal information, the user can select the add button 6518 (eg, FIG. 6H to FIG. 6I In some embodiments, and as Fig. 6F and Figure 6HAs best shown, the meal entry GUI 650 may also include a feedback query 6515, requesting whether the user liked the meal (e.g., "Did you like it?"). In some embodiments, the feedback query 6515 may include a first indicator 6516 (e.g., a thumbs up button) that the user may select to indicate that the user liked the meal. Additionally, the feedback query 6515 may include a second indicator 6517 (e.g., a thumbs down button) that the user may select to indicate that the user did not like the meal. Those skilled in the art will recognize that the meal entry GUI embodiments described herein may use other buttons, icons, or indicators to indicate whether the user liked the meal.

[0281] Feedback provided by the user through feedback query 6515 can be used to recommend food items that cause low or medium glycemic response / impact to the user. For example, if the user selects a first indicator in response to a feedback query 6515 requesting whether the user likes a meal, and if the meal causes a low or medium glycemic impact, the meal monitor application can then recommend the meal to the user. In addition, feedback provided by the user through feedback query 6515 can be used to avoid recommending foods that the user does not like, or foods that have a medium or high glycemic impact. For example, if the user selects a second indicator in response to a feedback query 6515 requesting whether the user likes a meal, the meal monitor application can then avoid recommending meals that the user does not like. In this regard, feedback query 6515 can be used to help users make better food choices by recommending foods they like to the user, which cause a low or medium glycemic impact.

[0282] Example Implementation of a Diary GUI

[0283] Go to 7A to 7I , depicts an exemplary embodiment of a diary GUI 700 for a meal monitor application. In many embodiments, when a user is in the home page GUI 400 ( Figure 4A-1 ) selects the diary section 412, the diary GUI 700 is displayed. Alternatively, the diary GUI 700 may be displayed when the user selects the corresponding icon in the navigation bar (bottom). In addition, the diary GUI 700 may include a function for providing contextual information 714 ( Figure 7B ) information button 702 ( Fig. 7A ) and for providing in-app notifications to users ( Fig.4O ) notification button 704 ( Fig. 7A ). In some implementations, the diary GUI 700 may also include a search bar 708 that is configured to allow a user to search for a particular diary entry.

[0284] According to one aspect of the embodiments, the diary GUI 700 can display the analyte responses of the user to previous meals in a user-friendly and easy to understand manner. In some embodiments, for example, the diary GUI 700 can include multiple views through which the analyte responses can be organized and displayed. For example, Fig. 7A As shown, when the day view option 706 is selected, the diary GUI 700 can present the analyte responses “by day”. Figure 7H As shown, when the week view option 736 is selected, the diary GUI 700 may present the analyte responses “by week.”

[0285] Reference again Fig. 7A , depicts an exemplary embodiment of a daily list 710 of meal-related glycemic responses for a diary GUI 700. As can be seen in the daily list 710, a variety of meals and / or foods are presented on the day of "March 12, 2022", including a meal / food entry containing "dosa biscuits, tea". As seen to the left of each meal / food entry, a graphical representation is displayed indicating the user's glycemic response to the corresponding meal / food. In addition to the graphical representation, each meal / food entry may also include an entry time and a numerical value indicating an analyte level variance value ("impact") associated with the meal / food.

[0286] In many embodiments, the graphical representation includes a segment shape (e.g., an arch, a circle, a bar), where each segment includes a different color (or no color at all). Each color can correspond to an analyte response range or ranking. For example, as shown in daily list 710, a semicircle (or "rainbow") shape can include three segments, where: (1) the first segment can have a green color to indicate a low glycemic response; (2) the second segment can have a yellow color to indicate a moderate glycemic response; or (3) the third segment can have an orange color to indicate a high glycemic response to a meal / food.

[0287] According to another aspect of the embodiment, different colors can each indicate that the method 300, 350, or 370 (as described with respect to Figure 3A , Figure 3F and Figure 3GAs described above, the range of analyte level variance values ​​is determined. For example, if the analyte level variance value is determined to be within the low analyte level variance range (e.g., less than 60 mg / dL or less than 3.3 mmol / L), the first segment is green (and the other segments are gray), to indicate that the meal / food causes a low blood sugar response or has a small effect. As another example, if the analyte level variance value is determined to be within the medium analyte level variance range (e.g., between 60 mg / dL and 100 mg / dL, or between 3.3 mmol / L and 5.6 mmol / L), the second segment is yellow (and the other segments are gray), to indicate that the meal / food causes a medium blood sugar response or a medium effect. As another example, if the analyte level variance value is determined to be within the high analyte level variance range (e.g., greater than 100 mg / dL, or greater than 5.6 mmol / L), the third segment is orange (and the other segments are gray), to indicate that the meal / food causes a high blood sugar response or a high effect. Examples of these interfaces are shown in modes 722, 724, and 726 ( Fig.7D , Fig. 7E and Figure 7F ).

[0288] According to another aspect of the embodiment, one or more conditions may cause all segments to be gray, such as if the analyte level variance value is below zero, if the analyte level variance value is above a maximum analyte level variance value (e.g., 170 mg / dL, 180 mg / dL, 190 mg / dL), or if the initial analyte level value is above a maximum initial analyte level value (e.g., 180 mg / dL, 200 mg / dL, 220 mg / dL, 250 mg / dL, etc.) One or more of these conditions may indicate that the determined analyte level variance value is either unreliable to be accurately calculated, or otherwise does not represent an analyte level variance value associated with dietary consumption.

[0289] In addition, although the graphical representation shown is a segmented semicircle with three colored segments, those skilled in the art will appreciate that other geometric shapes, colors, and numbers of segments may be used and are well within the scope of the present disclosure. Likewise, as described above, each color may represent a specific range of values. However, those skilled in the art will appreciate that other ranges may be used in addition to the listed ranges, and that these numbers are not meant to be limiting.

[0290] Reference again Fig. 7A According to another aspect of the embodiment, when the graphical representation is selected by the user, a pop-up modal may be displayed that provides additional information about the particular meal / food item. Fig.7DAs shown, pop-up modal 722 presents a graphical representation of a "low impact" (green) meal / item adjacent to a text description that provides the analyte level variance value for the meal / item (e.g., 27 mg / dL) followed by the method by which the analyte level variance value was calculated (e.g., using the glucose value at the time you entered the food and the subsequent peak). Similarly, pop-up modals 724, 726 ( Fig. 7E and Figure 7F ) are each associated with a “medium impact” (yellow) and “high impact” (orange) diet / item and their corresponding text descriptions.

[0291] In some embodiments, if a meal / food entry has not yet been associated with received analyte data, selection of the meal / food entry may cause the meal monitor application to display a notification 728 stating that analyte data has not yet been received for the entry (e.g., Figure 7G shown).

[0292] In an alternative embodiment, if Fig.7I As shown, the meal / food items shown in the daily list may be configured to expand to display additional information panels 738. In these embodiments, if the meal has been consumed multiple times in the past, the information panel 738 may include a weighted average measure of the analyte level variance values.

[0293] In some embodiments, a weighted average of analyte level variance values ​​for a particular food or meal can be based on the same (or similar) food entries added within a predetermined time period (e.g., within the last sixty days, within the last ninety days, within the last 120 days). In some embodiments, the weighted average can be based on a predetermined number of minimum analyte variance level values ​​and a predetermined number of maximum analyte variance level values ​​within the predetermined time period. In addition, in some embodiments, as part of the weighted average determination, meal / food entries for which no analyte variance level value was determined (or which was less than a minimum threshold) can be discarded. The weighted average can then be calculated / updated each time the relevant meal / food entry is created and / or updated.

[0294] According to some embodiments, the weighted average may also take into account the recency of the stored analyte level variance values ​​for a particular meal / food. For example, historical analyte level variance values ​​for meal / food entries that are more recent may be weighted more heavily when determining the weighted average than other historical values. By way of illustration only, in calculating the weighted average, the meal / food entries may be decremented by a predetermined factor for each day prior to the current date.

[0295] In other embodiments, a regular mean, median, mode, or another measure of central tendency of the analyte level variance values ​​may be used instead of a weighted mean.

[0296] In some embodiments, the information panel 738 can also be configured to display activity information associated with a particular meal, such as input into the activity text box 616 ( Figure 6B ). Fig.7I As shown, for example, "Workout, Running" is displayed in the additional information panel 738. In some embodiments, the information panel 738 can also display comments, such as those entered into the comment text box 630 ( Fig. 6E ) in the .

[0297] Return to reference Figure 7H , depicts an exemplary embodiment of a weekly list 734 of meal-related glycemic responses for a diary GUI 700. As can be seen in the weekly list 734, multiple meals / foods are presented within the one-week period of "November 13 to November 19, 2021". As seen in the left portion of each meal / food entry, a graphical representation is displayed indicating the user's glycemic response to the corresponding meal / food. In addition to the graphical representation, each meal / food entry can include a date, entry time, and a numerical value indicating an analyte level variance value. Those skilled in the art will appreciate that with respect to the daily list 710 ( Fig. 7A ) may also be used with respect to the weekly list 734 ( Figure 7H )application.

[0298] Return to reference Figure 7C , depicts an exemplary embodiment of a filter GUI 720 for a diary GUI 700. According to some embodiments, the filter GUI 720 may include a date filter 719 to limit the display of meal / food entries to a specific date range. In some embodiments, the filter GUI 720 may also include an analyte level variance value filter 717 to limit the display of meal / food entries to a specific ranking of analyte level variance values ​​(e.g., low impact, medium impact, or high impact). The filter GUI 720 may also include an apply button 716 to apply the selected filter to the current set of meal / food entries. Likewise, in some embodiments, the filter feature may also include a clear button 718 to reset or remove any current filters.

[0299] refer to Figures 7J to 7R , depicts an additional exemplary embodiment of a diary GUI 750 for a meal monitor application. In many embodiments, the diary GUI 750 is displayed when the user selects the diary section 4012 on the home GUI 460. Alternatively, the diary GUI 750 can be displayed when the user selects the corresponding icon in the navigation bar (bottom). Specifically, Figure 7JA diary GUI 750 is depicted, which is similar to the diary GUI 700, except that the diary GUI 750 does not include a notification button. According to another aspect of an embodiment, unlike the diary GUI 700, each meal / food entry in the diary GUI 750 includes a portion indicator 751 that describes the relative portion size of the meal (e.g., "S" for a small meal, "M" for a medium meal, or "L" for a large meal), rather than a numerical value indicating the analyte level variance value associated with the meal / food.

[0300] Additionally, contextual information 7514 ( Figure 7K In some implementations, the reference link 752 may be included with contextual information 7514, which when selected by a user outputs the reference GUI 760 ( Figure 7L ), the reference GUI includes references / sources related to context information 7514.

[0301] refer to Figure 7M , an exemplary implementation of a filter GUI 770 for the diary GUI 750 is provided, which is similar to the filter GUI 720 for the diary GUI 700.

[0302] in addition, Figures 7N to 7R Depicted are exemplary embodiments of various pop-up modalities 761, 762, 763, 764, and 765, respectively, which provide additional information about a particular meal / food entry. Specifically, when a user selects a graphical representation on the diary GUI 750, Figures 7N to 7R The pop-up modals 761, 762, 763, 764, and 765 in FIG. 7 can be displayed on the meal monitor application. For example, Figure 7N As shown, pop-up modal 761 presents a graphical representation of a "low impact" (green) meal / item adjacent to a text description that provides the analyte level variance value for the meal / item (e.g., 2.2 mmol / L) followed by the method by which the analyte level variance value was calculated (e.g., using your blood glucose level at the time of food entry and its highest level over the next two hours). Similarly, pop-up modals 762, 763 ( Fig.7O and Figure 7P ) are each associated with a “medium impact” (yellow) and “high impact” (orange) diet / item and their corresponding text descriptions.

[0303] According to another aspect of the embodiment, and as Figure 7QAs shown, pop-up modal 764 presents a graphical representation of a "no effect" (all gray) meal / item and a corresponding text description, wherein the text description provides that the analyte level variance value for the meal / item is less than zero (e.g., -0.8 mmol / L). In some embodiments, if the meal / food entry has not yet been associated with the received analyte data, selection of the meal / food entry may cause the meal monitor application to display a notification 765 advising that no blood glucose data is available for the entry and reminding the user to scan the sensor every eight hours (e.g., Figure 7R shown).

[0304] Example Implementation of Trends GUI

[0305] Go to FIG. 8A to FIG. 8D , depicts an exemplary embodiment of a trend GUI and related features for a meal monitor application. In many embodiments, when a user is in the home page GUI 400 ( Figure 4A-1 ) when selecting the trend section 406 on the navigation bar. Alternatively, the trend GUI 800 may also be displayed by selecting a corresponding icon in the navigation bar (bottom). In addition, the trend GUI 800 may include a function for providing contextual information 816 ( Figure 8B ) information button 802( Fig. 8A ) and for providing in-app notifications to users ( Fig.4O ) notification button 804( Fig. 8A ).

[0306] According to another aspect of the embodiment, the trend GUI 800 can display the meal-related trends in a user-friendly and easy-to-understand manner. In some embodiments, for example, the trend GUI 800 can include multiple views through which the trends can be displayed. For example, Fig. 8A As shown, when the corresponding "Glycemic Impact" option 806 is selected, the trend GUI 800 can present trend information related to the analyte response. Figure 8C As shown, when the "Meals" option 818 is selected, the trend GUI 800 may present trend information related to meals / foods.

[0307] Reference again Fig. 8A , with respect to the "Glycemic Impact" trend view, trend information may also be presented by week or month, as indicated by the time period option 808. Additionally, in some embodiments, the trend GUI 800 may also include a date change setting 810 that allows the user to select a different time period. According to one aspect of the embodiment, if the user selects a different time period, the presented trend information may automatically change / update.

[0308] In many embodiments, the trend GUI 800 also includes an easily understandable graphical representation 812 of the "glycemic impact" of the user's meal / food choices on their analyte levels during the selected time period. By way of illustration, Fig. 8A The graphical representation 812 shows that, for example, in the one-month period between September 23 and October 22, 53% of the user's meals / food items were classified as having "low impact" (e.g., shown as green segments). Similarly, Fig. 8A The graphical representation 812 shows that, during the same time period, 33% of the user's meals / food items were classified as having "medium impact" (e.g., shown as yellow segments). Similarly, during the same time period, approximately 13% of the user's meals / food items were classified as having "high impact" (e.g., shown as orange segments). Fig. 8A As can be seen, each segment can have a corresponding color, with a range of analyte level variance values ​​(as described above for Figure 4A-3 and Figure 4A-4 ), and a corresponding area reflecting the magnitude of the analyte level variance values ​​as a percentage of the total graphical representation. Although graphical representation 812 is Fig. 8A , but those skilled in the art will appreciate 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., 3, 4, 5, 6, etc.) may be used and are well within the scope of the present disclosure.

[0309] According to another aspect of some embodiments, the trend GUI 800 may also include a summary panel 814 that may provide an overall assessment of the user's food choices. By way of illustration, Fig. 8A The summary panel for 814 states that the user's "food choices resulted in a 36% decrease in green choices."

[0310] Go to Figure 8C, shows a trend GUI 800, wherein the meal view option 818 is selected. According to one aspect of the embodiment, the meal view may include a meal / food list 822 showing the name of each meal / food, a graphical and numerical representation of the analyte level variance value, and the corresponding date and time. In some embodiments, a search bar 820 may also be provided so that the user can identify a specific meal / food within a selected time period. In some embodiments, a voice recognition feature is provided to allow the user to speak the name of a meal or food, rather than manually typing it into the search bar 820. In addition, according to some embodiments, a filter button 824 may be provided to allow the user to filter trend information in a variety of useful views. For example, in some embodiments, selecting the filter button 824 may result in displaying a filter setting GUI 840, which may include a meal type filter 826, a blood glucose level impact filter 828, and / or a date range filter 830.

[0311] FIG. 8E to FIG. 8H Depicted are additional exemplary embodiments of trend GUIs and related features for use with a dietary monitoring application. In many embodiments, the trend GUI 850 can be displayed when the user selects the trend section 4006 on the home GUI 460 (FIG. 4A). Alternatively, the trend GUI 850 can also be displayed by selecting a corresponding icon in the navigation bar (bottom). FIG. 8E to FIG. 8H The trend GUI 850 depicted in FIG. 8 is similar to FIG. 8A to FIG. 8D 800 is depicted in FIG. 8 , except that trend GUI 850 does not include a notification button. Fig. 8E It is depicted that when the corresponding "Glycemic Impact" option 8506 is selected, the trend GUI 800 presents trend information related to the analyte response. Figure 8F Contextual information 8516 is shown displayed when a user selects the information button 8502 on the trend GUI 850. In addition, Figure 8G It is shown that when the "Meal" option 8518 is selected, the trend GUI 850 presents trend information related to meals / foods. Figure 8H Shown is a diagram showing that after the user has selected filter button 8524 ( Figure 8G ) and then the filter setting GUI 870 is displayed. Figure 8H As shown, the filter settings GUI 870 may include a meal type filter 8526 , a glycemic impact filter 8528 , and / or a date range filter 8530 .

[0312] Example Implementation of a Reporting GUI

[0313] Go to 9A to 9F, depicts an exemplary embodiment of a report GUI 900 for a meal monitor application. Fig.9A and Fig. 9B In many embodiments, when a user is on the home page GUI 400 ( Figure 4A-1 ) when selecting the report section 414 on the navigation bar. Alternatively, the report GUI 900 may be displayed by selecting a corresponding icon in the navigation bar (bottom). In addition, the report GUI 900 may include a function for providing contextual information 912 ( Fig. 9B ) information button 902( Fig.9A ) and for providing in-app notifications to users ( Fig.4O ) notification button 904( Fig.9A ).

[0314] According to one aspect of the embodiment, the report GUI 900 may include a date range field 906 to allow the user to select a date range for the report, and a blood glucose level impact option 908 to allow the user to report meals / food items with a specific analyte level variance value ranking (e.g., "low impact," "medium impact," and "high impact"). The report GUI 900 also includes a generate report button 910 that can be selected once the user has selected the desired settings.

[0315] FIG. 9C to FIG. 9E An additional exemplary embodiment of a report GUI 930 for use with a meal monitor application is depicted. In many embodiments, the report GUI 930 can be displayed when the user selects the trend section 4014 on the home GUI 460. Alternatively, the report GUI 930 can be displayed by selecting a corresponding icon 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. In addition, and as shown in FIG. Fig. 9C As depicted, reporting GUI 930 includes a “clear all” button 931 that a user may select to clear all entries entered into reporting GUI 930 . Fig.9E Depicted is context information 9312 that is displayed when a user clicks the information button 9302 on the reporting GUI 930.

[0316] Go to Fig.9F, showing an exemplary embodiment of a report 920 generated by a dietary monitor application. According to some embodiments, the report 920 can be generated as a PDF file so that the user can easily print the report or attach it to an email to send to a healthcare provider. In other embodiments, the report 920 can be generated as a Word .DOC file, an Excel spreadsheet, or a comma-delimited file. In some embodiments, the report 920 can be an in-application report, a web view, or any other desired format. Fig.9F As can be seen, report 920 may include a date and time field 922, a food field 924, an activity field 926, a glycemic impact field 928, a serving size field 930, and a notes field 932. One skilled in the art will appreciate that these fields are for illustration only, and that other fields, measurements, values, text fields, and / or options described herein may be displayed in report 920.

[0317] Exemplary Implementation of Joining Method and Related GUI

[0318] An exemplary embodiment of a method for joining a user to a meal monitor application, and various GUIs and features associated therewith, will now be described. Fig.10 , a method 1000 for adding a user to any meal monitor application embodiment of the present disclosure is provided. First, those skilled in the art will appreciate that the adding method and associated GUI can be software installed in the non-transitory memory of any embodiment of the reader device 120 (e.g., a smartphone), the drug delivery device 160, or the local computer system 170 described herein.

[0319] refer to Fig.10 , at 1002, the meal monitor application is started. However, before the user is allowed to operate further, it will be beneficial to ensure that appropriate requirements are met to fully use the meal monitor application. At 1004, the user receives a prompt asking whether they have a user account. In some embodiments, the user account can be an account number established with a trusted computer system for verification, and the trusted computer system can then provide the user's analyte data to the meal monitor application. If the user does not have an account, at 1006, the meal monitor application can prompt the user to register an account. In some embodiments, if the user refuses to register an account, the meal monitor application can terminate. In other embodiments, if the user refuses to register an account, the meal monitor application can enter an "unlinked" mode, in which the user can use the meal monitor application as a disconnected meal diary to manually input meal related information.

[0320] If the user registers an account, or already has an account, then at 1010, the user successfully logs into the account. Subsequently, at 1012, the meal monitor application asks the user whether he is wearing an active sensor control device. In some embodiments, if the user does not have a sensor control device, then at 1014, the meal monitor application can display an interface through which the user can order sensors. At 1016, the meal monitor application can terminate or enter an "unlinked" mode.

[0321] If the user is wearing an active sensor control device, the meal monitor application asks the user whether the sensor application is installed at 1018. If the user has not installed the sensor application, the meal monitor application may prompt the user to download the sensor application at 1020. For example, in some embodiments, the meal monitor may automatically open the "app store" to the sensor application page.

[0322] According to many embodiments, once it is determined that the requirements are met, at 1022 the meal monitor application starts and the home page GUI of FIG. 4A may be displayed.

[0323] Figures 11A-1 to 11N-3 Depicted are exemplary embodiments of an add-in GUI for a meal monitor application, any of which may be used with the embodiments described herein. In some embodiments, when the meal monitor application is first launched (e.g., with respect to Fig.10 ), GUIs 1100, 1105, and 1110 ( Figures 11A-1 to 11A-3 ) can provide the user with a brief introduction to the meal monitor application.

[0324] Figure 11B-1 to Figure 11B-6 Depicted are additional exemplary embodiments of an add-in GUI for use with a meal monitoring application. Specifically, Figure 11B-1 to Figure 11B-6 Depicted are joining GUIs 1101, 1102, 1103, 1104, 1105, and 1106, respectively, which may provide a user with a brief introduction to the meal monitor application after the user launches the meal monitor application for the first time.

[0325] also, Figure 11C-1 and Figure 11C-2 Depicted are language selection screens 1116 and 1117 , respectively, which a user may use to change the desired language of the meal monitor application. Figure 11C-3 Depicted is a join GUI 1118, which is similar to Figure 11B-1 The Join GUI 1101 is shown in , except that it is configured to display content in Swedish.

[0326] Next, you can use the join GUI 1115, 1120, 1125, 1130 ( Figure 11D-1 to Figure 11D-4 ) to register a user and create a new account. In other embodiments, the Join GUI 1121, 1122, 1123, 1124, 1126, 1127 ( Figure 11E-1 to Figure 11E-10 ) to register a user and create a new account.

[0327] If an account has already been created, the GUI 1130, 1135, 1140 ( Figure 11F-1 to Figure 11F-3 ) to log in the user. In some embodiments, and as Figure 11G-1 and Figure 11G-2 As shown, a pop-up modal 1131 or 1132 may be displayed on the Join GUI 1126 or Join GUI 1140 to request permission for the meal monitor application to track the user's activities on other applications and websites.

[0328] Next, a join GUI 1145 may be provided ( Figure 11H-1 ) to explain to the user the requirements of the meal monitor application. For example, adding GUI 1150 ( Figure 11H-2 ) asks the user whether he has a sensor control device. In some cases, if the user does not yet have a sensor, the GUI 1150 may also include a link or button for ordering a sensor. Join GUI 1155 ( Figure 11H-3 ) asks the user whether the sensor app is already installed.

[0329] In other embodiments, a join GUI 1133 ( Figure 11I-1 ) to explain to the user the requirements of the meal monitor application. For example, adding GUI 1134 ( Figure 11I-2 ) asks the user whether he has a sensor control device. In some cases, if the user does not yet have a sensor, the Join GUI 1134 may also include a link or button 1138 for ordering a sensor. Join GUI 1136 ( Figure 11I-3 ) asks the user whether the sensor application has been installed. In some embodiments, and if Figure 11I-4 As shown, a pop-up modal 1137 can be displayed on the join GUI 1133. Specifically, the pop-up modal 1137 can provide information about the notification. For example, the pop-up modal 1137 can notify the user that the dietary monitoring application wants to send a user notification. In addition, according to one aspect of the embodiment, the pop-up modal 1137 may include a "Do Not Allow" button 1141 and an "Allow" button 1142, which the user can select to configure the notification settings. This example is for illustration only, and those skilled in the art will recognize that other combinations and arrangements of modalities can be implemented and are fully within the scope of the present disclosure.

[0330] According to another aspect of the embodiment, the join GUIs 1160, 1165, and 1170 ( Figures 11J-1 to 11J-3 ) to inform the user whether all requirements are met (e.g., joining GUI 1171), or if one or more requirements are not met (e.g., joining GUIs 1165 and 1170). In some embodiments, joining GUIs 1171, 1172, 1173, 1174 ( Figure 11K-1 to Figure 11K-4 ) to inform the user whether all requirements are met (e.g., joining GUI 1171), or whether one or more requirements are not met (e.g., joining GUIs 1172, 1173, and 1174).

[0331] In addition to the aforementioned joining GUI, according to another aspect of the embodiment, after the joining process is completed, the tutorial GUIs 1175, 1180, 1185 and 1190 ( Figure 11L-1 to Figure 11L-4 ) may optionally be displayed to the user. In some embodiments, after the joining process is completed, the tutorial GUIs 1191, 1192, 1193, 1194, 1195, and 1196 ( Figure 11M-1 to Figure 11M-6 ) can optionally be displayed to the user on the meal monitor application. In addition, in some embodiments, the food tutorial GUIs 1197, 1198, 1199 ( Figure 11N-1 to Figure 11N-3 ) can optionally be displayed to the user.

[0332] Example Implementation of Challenge GUI and Related Features

[0333] Next reference FIG. 12A to FIG. 12K , depicts an exemplary implementation of a challenge GUI for a dietary monitoring application. Fig. 12A , displaying the challenge list GUI 1200 (also referred to herein as the "first challenge GUI"). When the user selects the "view all" link 4304 on the challenge card of the homepage GUI 460, the challenge list GUI 1200 (eg, Figure 4A-3 and Figure 4A-4 According to some embodiments, and as Fig. 12A As depicted, the challenge list GUI 120 reflects a list of one or more challenges associated with the user's analyte response, and includes: a live challenge card 1201 (also referred to herein as a "first challenge card"); a completed challenge card 1202 (also referred to herein as a "second challenge card"); and an unattempted challenge card 1203 (also referred to herein as a "third challenge card").

[0334] Specifically, the live challenge card 1201 may include one or more challenge icons 1211 reflecting challenges that are active or currently being taken by the user. In this regard, the live challenge card 1201 lists live challenges or challenges that the user is currently participating in on the dietary monitoring application. The challenge icon 1211 may include a picture 1212 and a challenge title 1213 providing a textual description related to the subject of the corresponding challenge reflected by the challenge icon 1211. In some embodiments, and as Fig. 12A As shown, a live indicator 1214 (e.g., a green dot) may be displayed on the picture 1212 of the challenge icon 1211 to indicate that the challenge represented by the challenge icon 1211 is active or currently being performed by the user. Those skilled in the art will recognize that various other live indicators 1214 may be used with the challenge GUI described herein and are fully within the scope of the present disclosure.

[0335] In addition, the live challenge card 1201 may include a plurality of challenge icons 1211. In some implementations, two or three challenge icons 1211 may be displayed on the live challenge card 1201. In some implementations, the live challenge card 1201 may include a plurality of challenge icons 1211, wherein the number of challenge icons 1211 in the live challenge card 1201 exceeds the number that can be displayed on the challenge list GUI 1200 at any given time. In some implementations, the live challenge card 1201 responds to receiving user input (e.g., via a swipe gesture, a scroll gesture, a drag gesture, or some other predetermined gesture) to display a new set of challenge icons 1211 that were not previously displayed on the challenge list GUI 1200 in response to the input. For example, in response to receiving the input, the live challenge card 1201 may display a new set of challenge icons 1211. In some implementations, at least one of the challenge icons 1211 in the new set displayed on the live challenge card 1201 is different from at least one of the challenge icons 1211 in the original set before receiving the user input.

[0336] According to another aspect of an embodiment, the challenge list GUI 1200 also includes a completed challenge card 1202, which includes one or more challenge icons 1211 reflecting challenges that have been completed by the user or that the user has previously participated in. In this regard, the completed challenge card 1202 lists completed challenges in the dietary monitoring application. The challenge icon 1211 may include a picture 1212 and a challenge title 1213 that provides a textual description related to the subject of the corresponding challenge reflected by the particular challenge icon 1211. In some embodiments, a participation indicator 1215 (e.g., a colored check mark, such as Fig. 12A) is superimposed on the picture displayed on the challenge icon 1211 to indicate that the challenge represented by the challenge icon 1211 is a challenge that the user has previously participated in or completed. Those skilled in the art will recognize that various other participation indicators can be used with the challenge GUI described herein and are fully within the scope of the present disclosure.

[0337] In some implementations, two or three challenge icons 1211 may be displayed on the completed challenge card 1202. In some implementations, the completed challenge card 1202 may include a plurality of challenge icons 1211, wherein the number of challenge icons 1211 in the completed challenge card 1202 exceeds the number that can be displayed on the challenge list GUI 1200 at any given time. In some implementations, the completed challenge card 1202 is responsive to receiving user input (e.g., via a swipe gesture, a scroll gesture, a drag gesture, or some other predetermined gesture) to display a new set of challenge icons 1211 that were not previously presented on the challenge list GUI 1200 in response to the input. In an exemplary implementation, in response to receiving the input, the completed challenge card 1202 may display a new set of challenge icons 1211. In some implementations, at least one of the challenge icons 1211 in the new set on the completed challenge card 1202 is different from at least one of the challenge icons 1211 in the original set prior to receiving the user input.

[0338] Additionally, in some implementations, the challenge list GUI 1200 includes an unattempted challenge card 1203 that includes one or more challenge icons 1211 reflecting challenges that the user has not yet attempted or that the user has not yet participated in. The challenge icon 1211 may include a picture 1212 and a challenge title 1213 that provides a textual description related to the subject of the corresponding challenge reflected by the particular challenge icon 1211.

[0339] In some implementations, two or three challenge icons 1211 may be displayed on an unattempted challenge card 1203. In some implementations, an unattempted challenge card 1203 may include a plurality of challenge icons 1211, wherein the number of challenge icons 1211 in an unattempted challenge card 1203 exceeds the number that can be displayed on the challenge list GUI 1200 at any given time. In some implementations, an unattempted challenge card 1203 is responsive to receiving user input (e.g., via a swipe gesture, a scroll gesture, a drag gesture, or some other predetermined gesture) to display or populate additional or alternative challenge icons 1211 that were not previously displayed on the challenge list GUI 1200 in response to the input. In response to receiving the input, the unattempted challenge card 1203 may display a new set of challenge icons 1211. In some implementations, at least one of the challenge icons 1211 in the new set is different from at least one of the challenge icons 1211 in the original set prior to receiving the user input.

[0340] Fig. 12B A challenge information GUI 1210 (also referred to herein as a "second challenge GUI") for an unattempted challenge (e.g., a "5 a day" challenge) is depicted. Specifically, when a user selects a corresponding challenge icon 1211 from an unattempted challenge card 1203 on the challenge list GUI 1200, the challenge information GUI 1210 for the unattempted challenge is displayed. In some implementations, the challenge information GUI 1210 includes a challenge profile portion 1225, wherein the challenge profile portion 1225 includes a challenge icon 1221 with a picture 1222 and a challenge title 1223 that provides a text description of the unattempted challenge. In some implementations, the challenge information GUI 1210 also provides contextual information 1228 related to its corresponding challenge. For example, in Fig. 12B , the unattempted challenge represented by the challenge information GUI 1210 is related to eating vegetables and fruits, and therefore, the contextual information 1228 provides a contextual description of the importance of consuming vegetables and fruits as well as a description of the challenge.

[0341] Additionally, the challenge information GUI 1210 may include an attempt indicator 1226, wherein the attempt indicator 1226 may be adjacent to a date stamp indicating when the challenge was last attempted. In some implementations, if the challenge has not been previously attempted, no date stamp may appear adjacent to the attempt indicator 1226. The challenge information GUI 1210 may also include a completion indicator 1227, wherein the completion indicator 1227 may be adjacent to a date stamp indicating when the challenge was last successfully completed. In some implementations, if the challenge has not been previously completed, no date stamp may appear adjacent to the completion indicator 1227 (e.g., see FIG. 10 ). Fig. 12B ).

[0342] In some embodiments, the challenge information GUI 1210 includes a start button 1229 that, when selected by the user, can start the challenge. Although not shown, once a challenge is started, the challenge icon 1211 will no longer be displayed in the unattempted challenge card 1202 on the challenge list GUI 1200. Instead, the challenge icon 1211 will be displayed in the live challenge card 1214 on the challenge list GUI 1200 to indicate that the challenge is active or live. In some embodiments, the challenge will start when the user selects the start button 1229 ( Fig. 12B ). In some embodiments, the challenge will not start until the next day. For example, if the challenge the user wishes to start is related to breakfast, and the challenge starts in the afternoon, the meal monitoring application is configured to start the selected challenge the next day. According to one aspect of the embodiment, the user can attempt multiple challenges at the same time. In some embodiments, the user can start two challenges at the same time.

[0343] Fig. 12C A challenge information GUI 1220 for an active challenge (e.g., a "carbonated drink" challenge that encourages users to choose low-sugar drinks instead of high-sugar soda or similar drinks) is depicted. In some examples, a carbonated drink challenge can be output / recommended to users who have drunk one or more high-sugar soda or similar drinks or a threshold amount of such drinks within a predetermined time period. The challenge information GUI 1220 for an active challenge is similar to the challenge information GUI 1210 for an unattempted challenge, except that it includes a stop button 1339 instead of a start button. In this regard, the user can select the stop button 1339 to stop continuing the corresponding challenge. In addition, the challenge icon 1231 for an active challenge depicted on the challenge information GUI 1220 includes a live indicator 1232 (e.g., a green dot) on the picture 1233 thereon to indicate the live status of the challenge. In some embodiments, the challenge information GUI 1220 for an active challenge also includes a progress card 1235, wherein the progress card 1235 indicates the progress made by the user to the challenge. According to one aspect of the implementation, the progress card 1235 includes a unit of measure and a unit of time for indicating progress. For example, if a challenge requires seven days to complete, the progress card may indicate the number of days the user has completed. In addition, the progress card may use fractional units to indicate progress (e.g., "0 / 7" means the user has completed zero days out of seven). However, those skilled in the art will recognize that other units of measure and / or units of time may be used, including but not limited to hours, weeks, and percentages, and are fully within the scope of the present disclosure.

[0344] Fig.12DAnother exemplary embodiment of a challenge information GUI for an active challenge is depicted. According to one aspect of the embodiment, a modal 1236 can be displayed on the challenge information GUI 1230 for an active challenge, wherein the modal is configured to prompt a user to provide progress information related to an ongoing active challenge. For example, and as Fig.12D As shown, if the active challenge requires the user to consume five servings of vegetables or fruits in a day, the modal 1236 can ask the user whether the challenge has been completed. The modal 1236 can include a "yes" button 1237 and a "no" button 1238, which the user can select to indicate their response to the prompt provided by the modal 1236. In some embodiments, the user is prompted daily to respond to the modal 1236 associated with a particular challenge in order to report and track its progress.

[0345] Fig.12E A challenge GUI 1240 (also referred to herein as a "third challenge GUI") is depicted, which is displayed to the user when the user successfully completes a challenge or indicates a challenge. For example, in response to the user selecting a "yes" button 1237 on the modal 1236, a third challenge GUI may be displayed. Fig.12E . According to one aspect of an embodiment, the challenge GUI 1240 may include: an attempt indicator 1246; a completion indicator 1247; a challenge icon 1241, including a picture 1242 and a challenge title 1243 indicating that the challenge has been completed; and a congratulatory message 1245, notifying the user that the challenge has been successfully completed. In addition, a participation indicator 1247 (e.g., a green check mark) may be superimposed on the picture 1242 of the challenge icon 1241 to indicate that the challenge represented has been completed by the user. In addition, in some embodiments, the challenge GUI 1240 may include a "retry" button 1248 and a "try another" button 1249. In some embodiments, when the user selects the retry button 1248, the user can restart the challenge. In some embodiments, when the user selects the try another button 1249, the challenge list GUI 1200 is displayed to allow the user to select a different challenge.

[0346] In some implementations, if the user does not successfully complete the challenge or is instructed to complete the challenge, a challenge GUI 1250 (also referred to herein as the "fourth challenge GUI") may be displayed. Fig.12F For example, in response to the user in modal 1236 ( Fig.12D) on the challenge GUI 1250 depicted in FIG. 12 may be displayed. According to one aspect of the implementation, the challenge GUI 1250 may include: an attempt indicator 1251; a completion indicator 1252; a challenge icon 1251 including a picture 1252 and a challenge title 1253 indicating that the challenge has been completed; and a message 1255 notifying the user that the challenge was not successfully completed. In some implementations, and as Fig.12F As depicted, the message 1255 may include an encouraging note to the user (e.g., "Try again!"). Additionally, a participation indicator 1257 (e.g., a green check mark) may be superimposed on the image 1252 of the challenge icon 1251 to indicate that the represented challenge has been completed by the user. Additionally, in some implementations, the challenge GUI 1250 may include a "Retry" button 1258 and a "Try Another" button 1259. In some implementations, when the user selects the Retry button 1258, the modal 1256 ( Figure 12G ) will be displayed on the challenge GUI, asking the user to confirm whether to restart the challenge. In some embodiments, when the user selects the Try Another button 1258, the challenge list GUI 1200 ( Fig. 12A ) to allow the user to select a different challenge.

[0347] FIG. 12H to FIG. 12K Depicted are additional exemplary embodiments of a challenge GUI for a dietary monitoring application. Specifically, Fig.12H Depicted is a challenge information GUI 1260 for an unattempted challenge (e.g., a "4 in a row in one day" challenge) similar to Fig. 12B The challenge information GUI 1210 depicted in Fig. 12A The challenge icon 1271 in does not include an indicator. Fig.12I A challenge information GUI 1270 is shown that is displayed after a user starts a challenge. In this embodiment, the challenge information GUI 1270 includes: (1) a challenge profile card 1275, in which a challenge icon 1271 with a picture 1272 and a challenge title 1273 representing the challenge are displayed, as well as a text description 1278 of the challenge; (2) a historical progress card 1276; (3) a current progress card 1277; (4) a statistics card 1274; and (5) a stop button 1279.

[0348] In some embodiments, the current progress card 1277 may include a first progress indicator 1281 that visually shows the user's current progress in completing the challenge. Specifically, the first progress indicator 1281 may include a first graphical indication, such as a first plurality of circles, wherein the first progress indicator 1281 is each circle in the first plurality of circles, which includes a first color (e.g., green circles indicate increasing successful progress). In some embodiments, a second color (e.g., yellow circles) may be used on the first progress indicator 1281 to indicate that the user's attempt at the challenge was unsuccessful.

[0349] Furthermore, in some embodiments, and as FIG. 12I to FIG. 12K As shown, the historical progress card 1276 may include a second progress indicator 1282 that visually illustrates the progress made by the user in previous or past cycles of the challenge. Specifically, the second progress indicator 1282 may include a second graphical indication, such as a second plurality of circles, wherein the second progress indicator 1282 is each circle in the second plurality of circles, which includes a first color (e.g., green circles indicate an increase in successful progress). In some embodiments, and as Fig.12J As best shown, a second color (e.g., a yellow circle) may be used on the second progress indicator 1282 to indicate that the user has made an unsuccessful attempt at the challenge in the last cycle of the challenge.

[0350] In some implementations, if the user does not successfully complete the challenge, the challenge GUI 1280 ( Fig.12J ). According to one aspect of the embodiment, the meal monitor application is configured to automatically detect whether the challenge has been successfully progressed based on the meal entry or the analyte level variance value associated with the meal entry. For example, the meal monitor application may automatically detect that the user has consumed four consecutive "green impact" or low glycemic response meals. Thus, Fig.12J The challenge GUI 1280 depicted in FIG. 12 may be displayed in response to the meal monitor application detecting that the user has not consumed four Green Impact meals consecutively.

[0351] According to one aspect of the implementation, the challenge GUI 1280 may include: a challenge profile card 1275; a history progress card 1276; a statistics card 1278; and a message 1291 notifying the user that the challenge was not successfully completed. Fig.12I As depicted, message 1291 may include an encouraging note to the user (eg, “Try again!”). Additionally, in some implementations, challenge GUI 1280 may include a “Try Again” button 1288 and a “Try Another” button 1289.

[0352] Figure 12KA challenge GUI 1290 is depicted, which is displayed to the user when the user successfully completes the challenge. In some exemplary embodiments, Figure 12K The challenge GUI 1290 shown in FIG. 12 can be displayed in response to the dietary monitoring application automatically detecting that the user has consumed four green impact meals in a row. According to one aspect of the embodiment, the challenge GUI 1290 may include: a challenge profile card 1275; a historical progress card 1276; a statistics card 1278; and an encouraging message 1293 notifying the user that the challenge has been successfully completed. In addition, in some embodiments, the challenge GUI 1290 may include a "retry" button 1298 and a "try another" button 1299. In some embodiments, when the user selects the retry button 1298, the user can restart the challenge.

[0353] According to one aspect of the implementation, the statistics card 1278 is configured to indicate the number of times the user successfully completed the challenge. In some implementations, the statistics card 1278 includes a numerical value and a textual description indicating the number of times the challenge has been successfully completed (e.g., FIG. 12I to FIG. 12J The "0 times" shown and Figure 12K “1 time” shown).

[0354] Example Implementation of Alerts for Meal Monitor Application

[0355] The meal monitor application may also display various alerts and notifications to remind and / or encourage the user to log meals, thereby helping the user to improve or maintain blood sugar control. Fig.13A As shown, a lock screen notification 1310 may appear for a meal monitoring application. For example, a lock screen notification 1310 may appear notifying the user that a high glucose meal was detected and prompting the user to log items based on the detected glucose peak. Alternatively, notification 1310 may be a celebratory notification notifying the user that they remain within range after a meal, or that they have logged a certain number of meals, for example.

[0356] In some embodiments, and as Fig. 13B As shown, a dietary monitoring application in-application mode 1320 may be provided to the user via a dietary monitoring application. In some embodiments, the in-application mode 1320 may be configured to partially obscure or overlay an underlying interface (e.g., homepage GUI 460) from view ( Fig. 13B and Fig. 13C). The app can also remind and / or encourage the user in response to the user clicking on the notification 1310 on the lock screen, presenting an in-app modal 1320. The in-app modal 1320 can be a more vivid and intuitive modal within the app that provides more context for the prompting action. The in-app modal 1320 can include possible answers so that the user can indicate that they did not eat anything, or the user can choose a link to add food, which can open a food logging screen, examples of which are described elsewhere in the app. Alternatively, the in-app modal 1320 can be a celebratory notification that contains encouraging words and graphics to replenish the user, such as staying within a target range. The in-app modal 1320 can present graphics and text that encourages the user to log meals by reminding the user that many reasons may cause a detected glucose peak, and logging meals will help the user identify the cause of the glucose peak.

[0357] In addition, the in-app modal 1320 can present graphics and text that gently nudge the user to deliver a predetermined message 1330. According to one aspect of the embodiment, the message 1330 is personalized for the user. In some embodiments, the dietary monitoring application is configured to analyze past dietary entries and / or analyte level variance values ​​associated with past dietary entries in order to push specific messages 1330 to the user based on the analysis.

[0358] In an exemplary embodiment, the in-application modal 1320 includes a message 1330 that suggests food choices for the user based on the user's past experiences and entries. Fig. 13B As shown, in-application modal 1320 includes message 1330 suggesting salmon and grilled vegetables for dinner based on the user's previous blood sugar levels.

[0359] According to another aspect of an embodiment, the in-app modal 1320 may include messages 1330 related to the following subject areas, including, but not limited to: (1) sensor scanning (e.g., prompting a user to scan their sensors before bed); (2) user profile (e.g., requesting a user to fill out their profile); (3) nutrition (e.g., providing nutrition tips); and (4) meal entries (e.g., recommending foods or meal changes, such as swapping out certain foods for other foods, e.g., replacing pizza with chicken).

[0360] In some embodiments, the in-app modal 1320 gently nudges the user. In some embodiments, after the user selects the banner notification 1310 displayed outside the meal monitoring application, the in-app modal 1320 is displayed (e.g., see Fig.13AIn some embodiments, a banner notification 1320 can be displayed outside of the meal monitoring application (e.g., on the lock screen) to nudge the user, where the banner notification 1310 includes an indication that the meal monitoring application has provided personalized suggestions for the user (e.g., Fig.13A Dinner recommendations shown).

[0361] According to one aspect of the implementation, the in-app messaging feature on the meal monitoring application requires the user to specifically opt-in to activate in-app messages 1330. Thus, before the meal monitoring application populates in-app messages 1330 for the user, the user must first grant permission for the meal monitoring application to send the user in-app messages 1330.

[0362] These examples are for illustration only, and those skilled in the art will recognize that other combinations and permutations of modalities may be implemented and are fully within the scope of the present disclosure.

[0363] Various aspects of the subject matter are set forth below to review and / or supplement the embodiments described so far, with emphasis on the interrelationship and interchangeability of the following embodiments. In other words, it is emphasized that each feature of the embodiments can be combined with each other feature unless otherwise explicitly stated or logically unbelievable. The embodiments described herein are reiterated and expanded in the following paragraphs without explicit reference to the drawings.

[0364] Systems, devices and methods for detecting, measuring and classifying individual meals based on analyte measurements. These results and related information can be presented to the individual to show which meals cause the most severe analyte response to the individual. These results can be organized and classified based on preselected criteria or previous meals and results so that the results are organized and presented in a format with glucose as the monitored analyte. Various embodiments disclosed herein relate to methods, systems and software applications intended to attract individuals by providing direct and timely feedback on individual meal-related glycemic responses.

[0365] It should be noted that all features, elements, components, functions, and steps described with respect to any embodiment provided herein are intended to be freely combined and replaced with those from any other embodiment. If a feature, element, component, function, or step is described with respect to only one embodiment, it should be understood that the feature, element, component, function, or step can be used with each of the other embodiments described herein unless otherwise explicitly stated. Therefore, this paragraph serves as a pre-condition and written support for the introduction of claims at any time, which combine the features, elements, components, functions, and steps of different embodiments, or replace those of one embodiment with the features, elements, components, functions, and steps of another embodiment, even if the following description does not explicitly state, but in a particular case, such a combination or replacement is possible. It is explicitly acknowledged that the description of every possible combination and replacement is too cumbersome, especially considering that the permissibility of each such combination and replacement will be easily recognized by a person of ordinary skill in the art.

[0366] To the extent that embodiments disclosed herein include or operate in association with memory, storage, and / or computer-readable media, then the memory, storage, and / or computer-readable media are non-transitory. Thus, to the extent that memory, storage, and / or computer-readable media are covered by one or more claims, then the memory, storage, and / or computer-readable media are only non-transitory.

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

[0368] The subject matter described herein and in the drawings has sufficient detail and clarity to permit the inclusion of claims in means-plus-function format at all times pursuant to 35 U.S.C. § 112(f). However, a claim should be construed to invoke such means-plus-function format only if the phrase "means for" is expressly recited in the claim.

[0369] Aspects of the invention are set out in the independent claims, and preferred features are set out in the dependent claims. Preferred features of the dependent claims may be provided in combination in a single embodiment, and preferred features of one aspect may also be provided in combination with other aspects.

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

[0371] The publications discussed herein are only used to be disclosed before the filing date of the present application. Nothing herein should be construed as admitting that the present disclosure is not entitled to be published in advance by virtue of a previous disclosure. In addition, the publication date provided may be different from the actual publication date, which may require independent confirmation.

[0372] Although the embodiments are susceptible to various modifications and alternative forms, specific examples thereof have been shown in the drawings and described in detail herein. The embodiments are not limited to the specific forms disclosed, but rather, the embodiments will cover all modifications, equivalents, and alternatives falling within the spirit of the present disclosure. In addition, any features, functions, steps, or elements of the embodiments may be listed in or added to the claims, as well as negative limitations that limit the scope of the claims by not including features, functions, steps, or elements within the scope.

[0373] Terms

[0374] Exemplary embodiments are set forth in the following numbered clauses:

[0375] Item 1. A system for monitoring a dietary-related analyte response in a user, the system comprising: a reader device comprising: a wireless communication circuit configured to receive data indicating an analyte level of the user; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a first challenge graphical user interface (GUI), the first challenge GUI reflecting a list of one or more challenges associated with the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card, wherein the first challenge card reflects the one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being conducted by the user on the dietary monitoring application, wherein the second challenge card reflects the one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and wherein the third challenge card reflects the one or more unattempted challenges, wherein each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

[0376] Clause 2. The system of clause 1, wherein the first challenge card comprises one or more selectable first challenge icons, wherein each of the one or more selectable first challenge icons reflects a challenge currently being performed by the user.

[0377] Clause 3. A system according to clause 2, wherein each of the one or more optional first challenge icons comprises a first indicator, an image, and a text description related to a challenge currently in progress, wherein the first indicator is displayed on the image and is configured to indicate that the challenge is currently in progress.

[0378] Clause 4. The system of clause 3, wherein the first indicator is a green dot.

[0379] Clause 5. The system of any preceding clause, wherein the second challenge card includes one or more selectable second challenge icons, wherein each of the one or more selectable second challenge icons reflects a challenge to be completed by the user.

[0380] Clause 6. A system according to clause 5, wherein each of the one or more optional second challenge icons comprises a second indicator, an image, and a text description associated with a completed challenge, wherein the second indicator is superimposed on the image and is configured to indicate that the challenge has been completed by the user.

[0381] Clause 7. A system according to clause 5, wherein each of the one or more optional second challenge icons comprises a second indicator, an image, and a text description associated with a completed challenge, wherein the second indicator is superimposed on the image and is configured to indicate that the challenge has been completed by the user.

[0382] Clause 8. The system of any preceding clause, wherein the third challenge card includes one or more selectable third challenge icons, wherein each of the one or more selectable third challenge icons reflects a challenge that the user has not yet attempted.

[0383] Clause 9. The system of clause 8, wherein each of the one or more selectable third challenge icons comprises a picture and a text description associated with the completed challenge.

[0384] Clause 10. A system according to any of the preceding clauses, wherein each of the first challenge card, the second challenge card, and the third challenge card includes a plurality of optional challenge icons, wherein a first set of the plurality of optional challenge icons is displayed on the first challenge GUI, wherein the reader device also includes a touch screen, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a swipe gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the plurality of optional challenge icons on the first challenge GUI, wherein at least one or more of the plurality of optional challenge icons of the second set is different from at least one or more of the plurality of optional challenge icons of the first set.

[0385] Clause 11. A system according to any of the preceding clauses, wherein the list of one or more challenges includes one or more optional challenge icons, wherein each of the one or more optional challenge icons corresponds to one of one or more challenges related to an analyte response or glucose level of a user, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to selection of one of the one or more optional challenge icons, output a second challenge GUI that reflects contextual information related to one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons.

[0386] Clause 12. A system according to clause 11, wherein the second challenge GUI comprises: a challenge profile portion, including a selected one of one or more optional challenge icons, a picture, and a challenge title, which provides a text description of one of the one or more challenges corresponding to the selected one of the one or more optional challenge icons; an attempt indicator, configured to indicate the time when the user last attempted one of the one or more challenges corresponding to the selected one of the one or more optional challenge icons; and a completion indicator, configured to indicate the time when the user last successfully completed one of the one or more challenges corresponding to the selected one of the one or more optional challenge icons.

[0387] Clause 13. A system according to clause 11 or clause 12, wherein, if one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an unattempted challenge, the second challenge GUI also includes a start button, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: start the unattempted challenge on the dietary monitoring application in response to selection of the start button.

[0388] Clause 14. The system of clause 13, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: in response to selection of a start button, start an unattempted challenge on the dietary monitoring application on the next day.

[0389] Clause 15. A system according to clause 11 or clause 12, wherein, if one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an active challenge, the second challenge GUI also includes a stop button, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: stop the continuation of the active challenge in response to selection of the stop button.

[0390] Clause 16. A system according to clause 11 or clause 12, wherein, if one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an active challenge, the second challenge GUI also includes a progress card configured to indicate the user's progress made on the active challenge, wherein the progress card includes a unit of measurement and a unit of time indicating the progress.

[0391] Clause 17. The system of clause 16, wherein the units of measure include fractional units, and wherein the units of time include days.

[0392] Clause 18. A system according to clause 11 or clause 12, wherein, if one of the one or more challenges corresponding to a selected one of the one or more selectable challenge icons is an active challenge, a modal is displayed on a second challenge GUI, wherein the modal is configured to prompt a user to provide progress information related to the active challenge in a dietary monitoring application.

[0393] Clause 19. A system according to clause 18, wherein the dietary monitoring application is configured to detect whether a user successfully completes an active challenge based on the tracked progress, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to the dietary monitoring application detecting that the user successfully completes the active challenge, output a third challenge GUI, wherein the third challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message congratulating the user for successfully completing the active challenge, and in response to the dietary monitoring application detecting that the user successfully completes the active challenge, identify the active challenge as a completed challenge, wherein the third challenge GUI also includes a first button that, when selected by the user, is configured to restart the completed challenge, and wherein the third challenge GUI also includes a second button that, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from a list of one or more challenges reflected by the first challenge GUI.

[0394] Clause 20. The system of clause 19, wherein, in response to the user selecting the first button, a modal is displayed on the third challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart the completed challenge.

[0395] Clause 21. A system according to clause 18, wherein the dietary monitoring application is configured to detect whether a user successfully completes an active challenge based on the tracked progress, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to the dietary monitoring application detecting that the user has not successfully completed the active challenge, output a fourth challenge GUI, wherein the fourth challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message notifying the user that the active challenge has not been successfully completed, and in response to the dietary monitoring application detecting that the active challenge has not been successfully completed, identify the active challenge as a completed challenge, wherein the fourth challenge GUI also includes a first button that, when selected by the user, is configured to restart the completed challenge, and wherein the fourth challenge GUI also includes a second button that, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from a list of one or more challenges reflected by the first challenge GUI.

[0396] Clause 22. The system of clause 21, wherein, in response to the user selecting the first button, a modal is displayed on the fourth challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart the completed challenge.

[0397] Clause 23. A system according to any of the preceding clauses, wherein the dietary monitoring application includes a home page GUI, the home page GUI includes a challenge card, wherein the challenge card includes an optional link, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: output a first challenge GUI in response to a user selecting a link.

[0398] Clause 24. The system of any preceding clause, wherein each of the one or more challenges is configured to represent a challenge to a behavior or activity of the user that may affect the user's analyte level.

[0399] Item 25. A system for monitoring dietary-related analyte responses in a user, the system comprising: a reader device comprising: wireless communication circuitry configured to receive data indicating an analyte level of a user; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to: receive dietary information input by a user, wherein the dietary information is configured to reflect the user's food selections; output a main graphical user interface (GUI), wherein the homepage GUI comprises: a plurality of optional sections, the plurality of optional sections comprising a user profile section, a meal entry section, a trends section, a diary section, and a report section; a meal card configured to display one or more meal lists comprising input dietary information associated with one or more meals consumed by the user; a trend card comprising a graphical representation of information associated with an analyte response associated with the user's food selections; a challenge card reflecting a list of one or more challenges associated with the user's analyte response or glucose level; and a recommendation card reflecting one or more recommendations associated with the user's food selections or analyte response.

[0400] Clause 26. The system of clause 25, wherein the recommendation card comprises one or more selectable recommendation icons, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations.

[0401] Clause 27. The system of clause 26, wherein each of the one or more selectable recommendation icons includes an image associated with a corresponding one of the one or more recommendations, and a recommendation title providing a text description of the corresponding one of the one or more recommendations.

[0402] Clause 28. A system according to any one of clauses 25 to 27, wherein the recommendation card includes a plurality of optional recommendation icons, wherein a first set of the plurality of optional recommendation icons is displayed on the recommendation card, wherein the reader device further includes a touch screen, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a swipe gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the plurality of optional recommendation icons on the recommendation card, wherein at least one or more of the plurality of optional recommendation icons of the second set is different from at least one or more of the plurality of optional recommendation icons of the first set.

[0403] Clause 29. A system according to any of clauses 25 to 28, wherein the recommendation card includes one or more optional recommendation icons, wherein each of the one or more optional recommendation icons corresponds to one of the one or more recommendations, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: output a modal on a home page GUI in response to a selection of one of the one or more optional recommendation icons, wherein the modal provides contextual information related to a corresponding one of the one or more recommendations, and wherein the modal is configured to guide the user to take action based on the corresponding one of the one or more recommendations.

[0404] Clause 30. A system according to any of clauses 25 to 29, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: detect food selections of a user; analyze input dietary information; and based on the analysis, display one or more optional recommendation icons on a recommendation card, wherein each of the one or more optional recommendation icons reflects a recommendation related to the user's food selections or analyte responses.

[0405] Clause 31. A system according to any of clauses 25 to 30, wherein the recommendation card includes one or more optional recommendation icons, wherein each of the one or more optional recommendation icons corresponds to one of one or more recommendations, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to selection of one of the one or more optional recommendation icons, remove a selected one of the one or more optional recommendation icons from the recommendation card, and display a new optional recommendation icon on the recommendation card to replace the removed recommendation icon.

[0406] Clause 32. A system according to any of clauses 25 to 31, wherein the recommendation card includes one or more optional recommendation icons, wherein each of the one or more optional recommendation icons corresponds to one of the one or more recommendations, and wherein each of the one or more optional recommendation icons is configured to be displayed on the recommendation card for a predetermined time period.

[0407] Clause 33. A system according to clause 32, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: detect when a predetermined time period is reached, and in response to reaching the predetermined time period, replace one or more optional recommendation icons on the recommendation card with one or more optional recommendation icons from a new set, wherein at least one of the one or more optional recommendation icons in the new set is different from at least one of the one or more optional recommendation icons that are replaced.

[0408] Clause 34. The system of any of clauses 25 to 33, wherein the home page GUI is configured to switch between a plurality of views, wherein the plurality of views comprises at least a first view and a second view.

[0409] Clause 35. A system according to clause 34, wherein the home page GUI is in a first view, wherein the home page GUI is configured to display a user profile portion, a meal entry portion, a diary portion, and a meal card in the first view, wherein the reader device also includes a touch screen, wherein the meal monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a scroll gesture, a swipe gesture, a pull gesture, or a drag gesture from the touch screen, and wherein, in response to the received input, the home page GUI is configured to transition from the first view to a second view, wherein trend cards, challenge cards, and recommendation cards are displayed on the home page GUI in the second view.

[0410] Clause 36. A system according to any of clauses 25 to 35, wherein the home GUI is configured to transition between multiple views, wherein each of the multiple views is different, wherein the reader device also includes a touch screen, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a scroll gesture, a swipe gesture, a pull gesture, or a drag gesture from the touch screen, and in response to the received input, display one of the multiple views of the home GUI.

[0411] Clause 37. A system according to any of clauses 25 to 36, wherein the meal card is configured to display one or more meal listings including meal information related to one or more of the most recently consumed meals.

[0412] Clause 38. A system according to any of clauses 25 to 37, wherein each of one or more meal lists includes detailed information of a meal consumed by a user, wherein the one or more meal lists are displayed on a meal card in chronological order, and wherein a meal list corresponding to a most recently consumed meal is displayed at a top portion of the meal card.

[0413] Clause 39. The system of any of Clauses 25 to 38, wherein each of the one or more meal lists includes detailed information of a meal consumed by the user and a corresponding meal-related analyte response of the meal.

[0414] Clause 40. A system according to any of clauses 25 to 39, wherein each of one or more meal lists comprises: a textual description of a meal consumed by a user; a portion indicator including information indicating that the meal is small, medium, or large compared to the user's usual meal supply; a date stamp associated with the date the meal was consumed by the user; a timestamp associated with the time the meal was consumed; and a graphical representation of an analyte response associated with the meal.

[0415] Clause 41. The system of clause 40, wherein the graphical representation comprises a plurality of segments.

[0416] Clause 42. A system according to clause 41, wherein the plurality of segments include a first segment, and wherein the first segment indicates an analyte response including a low blood glucose response, wherein the plurality of segments include a second segment, wherein the second segment indicates an analyte response including a moderate blood glucose response, and wherein the plurality of segments include a third segment, wherein the third segment indicates an analyte response including a high blood glucose response.

[0417] Clause 43. The system of clause 42, wherein the first segment, the second segment, and the third segment each have a different color.

[0418] Clause 44. The system of any of Clauses 25 to 43, wherein the graphical representation of the trend card indicates analyte responses associated with the user's food selections over a predetermined time period.

[0419] Clause 45. The system of clause 44, wherein the graphical representation of the trend card comprises a plurality of color segments, the color segments comprising a first color segment, a second color segment, and a third color segment.

[0420] Clause 46. The system of clause 45, wherein the first color segment comprises green indicating a low glycemic response, wherein the second color segment comprises yellow indicating a moderate glycemic response, and wherein the third color segment comprises orange indicating a high glycemic response.

[0421] Clause 47. The system of any of Clauses 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 predetermined time period.

[0422] Clause 48. A system according to any of clauses 25 to 47, wherein the trend card includes a summary panel that includes information indicating an analyte response associated with a user's food selections, wherein the trend card is configured to be dynamic, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: detect whether the analyte response associated with the user's food selections provides new trend information, and in response to detecting the new trend information, populate an updated summary panel on the trend card.

[0423] Clause 49. The system of any of Clauses 25 to 48, wherein the trend card is not displayed on the home page GUI when data indicative of analyte levels is not received or associated with the input dietary information.

[0424] Clause 50. A system according to any of clauses 25 to 49, wherein the challenge card on the home page GUI includes one or more selectable challenge icons, wherein each of the one or more selectable challenge icons is configured to reflect a challenge related to an analyte response or glucose level of the user.

[0425] Clause 51. The system of clause 50, wherein each of the one or more selectable challenge icons includes a picture associated with the challenge reflected by the selected challenge icon and a challenge title providing a text description of the challenge reflected by the selected challenge icon.

[0426] Clause 52. The system of clause 51, wherein a live indicator is displayed on the picture to indicate that the challenge reflected by the picture is an active challenge on the dietary monitoring application.

[0427] Clause 53. A system according to any of clauses 25 to 52, wherein the challenge card includes an optional link, wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: in response to a user selecting the link, output a first challenge GUI that includes information about all challenges provided on the dietary monitoring application.

[0428] Clause 54. A system according to any of clauses 25 to 53, wherein the challenge card includes a plurality of optional recommendation icons, wherein a first set of the plurality of optional challenge icons is displayed on the challenge card, wherein the reader device further includes a touch screen, and wherein the dietary monitoring application, when executed by one or more processors, further causes the one or more processors to: receive input corresponding to a swipe gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the plurality of optional challenge icons on the challenge, wherein at least one or more of the plurality of optional challenge icons of the second set is different from at least one or more of the plurality of optional challenge icons of the first set.

[0429] Clause 55. A system according to any of clauses 25 to 54, wherein the challenge card includes a plurality of selectable challenge icons, wherein the challenge card is configured to display two or three of the plurality of selectable challenge icons simultaneously on the home page GUI.

[0430] Clause 56. The system of any of clauses 25 to 55, wherein the recommendation card comprises a plurality of selectable recommendation icons, wherein the recommendation card is configured to display two or three of the plurality of selectable recommendation icons simultaneously.

[0431] Clause 57. A system according to any one of clauses 25 to 56, wherein the home page GUI further comprises a navigation bar.

[0432] Clause 58. The system of any of clauses 25 to 57, wherein the home page GUI further comprises a banner including a message related to the scanning sensor and the impact of the meal.

[0433] Item 59. A system for monitoring a meal-related analyte response in a subject, the system comprising: a reader device, comprising: wireless communication circuitry configured to receive data indicative of an analyte level of the subject; one or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to: identify a peak analyte level value of data indicative of an analyte level of the subject received within a predetermined time period, determine an estimated meal start time and an initial analyte level value based on the peak analyte level value, determine an analyte level variance value, prompt the subject to enter meal information, and associate the entered meal information with the analyte level variance value.

[0434] Clause 60. The system of clause 59, wherein the reader device comprises a smartphone.

[0435] Clause 61. The system of Clause 59 or Clause 60, wherein the data indicative of the subject's analyte level comprises data indicative of glucose level.

[0436] Clause 62. The system of any one of clauses 59 to 61, further comprising a trusted computer system, wherein the trusted computer system is a cloud computing platform comprising one or more servers.

[0437] Clause 63. The system of Clause 62, wherein the trusted computer system is configured to transmit data indicative of the subject's analyte level to the reader device.

[0438] Clause 64. A system according to any one of clauses 59 to 63, further comprising a sensor control device, wherein the sensor control device comprises an analyte sensor, and wherein at least a portion of the analyte sensor is configured to be located beneath a skin layer of a subject and in contact with a bodily fluid of the subject.

[0439] Clause 65. The system of Clause 64, wherein the sensor control device is further configured to transmit data indicative of the subject's analyte level to the reader device.

[0440] Clause 66. The system of any of Clauses 59 to 65, wherein the wireless communication circuitry of the reader device is configured to receive data indicative of the subject's analyte level according to a Bluetooth or near field communication wireless protocol.

[0441] Clause 67. The system of any of Clauses 59 to 66, wherein the peak analyte level value comprises a highest glucose value that exceeds a predetermined analyte level threshold.

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

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

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

[0445] Clause 71. The system of any of Clauses 59 to 70, wherein the predetermined time period of received data indicative of the subject's analyte level includes the last two hours of analyte data.

[0446] Clause 72. The system of any of Clauses 59 to 71, wherein the predetermined time period of received data indicative of the subject's analyte level includes the last four hours of analyte data.

[0447] Clause 73. The system of any of Clauses 59 to 72, wherein the predetermined time period of received data indicative of the subject's analyte level includes the last eight hours of analyte data.

[0448] Clause 74. The system of any one of Clauses 59 to 73, wherein the estimated meal start time is determined by counting back two hours from the time of the peak analyte level value.

[0449] Clause 75. The system of any of Clauses 59 to 73, wherein the estimated meal start time is determined by counting back three hours from the time of the peak analyte level value.

[0450] Clause 76. The system of any of Clauses 59 to 73, wherein the estimated meal start time is determined by counting back four hours from the time of the peak analyte level value.

[0451] Clause 77. The system of any of Clauses 59 to 76, wherein the analyte level variance value is determined by subtracting the initial analyte level value from the peak analyte level value.

[0452] Clause 78. The system of any of clauses 59 to 77, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and associated analyte level variance values ​​in a memory of the reader device.

[0453] Item 79. A system for monitoring a dietary-related analyte response in a subject, the system comprising: a reader device comprising: wireless communication circuitry configured to receive data indicative of an analyte level of the subject; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to: receive dietary information entered by the subject, receive data indicative of the analyte level of the subject within a predetermined amount of time after the dietary information is entered by the subject, identify a peak analyte level value of the received data indicative of the analyte level of the subject, determine an initial analyte level value, determine an analyte level variance value, and associate the entered dietary information with the analyte level variance value.

[0454] Clause 80. The system of clause 79, wherein the reader device comprises a smartphone.

[0455] Clause 81. The system of clause 79 or clause 80, wherein the data indicative of the subject's analyte level comprises data indicative of glucose level.

[0456] Clause 82. The system of any one of clauses 79 to 81, further comprising a trusted computer system, wherein the trusted computer system is a cloud computing platform comprising one or more servers.

[0457] Clause 83. The system of any of Clauses 79 to 82, wherein the trusted computer system is configured to transmit data indicative of the subject's analyte level to the reader device.

[0458] Clause 84. A system according to any one of clauses 79 to 83, further comprising a sensor control device, wherein the sensor control device comprises an analyte sensor, and wherein at least a portion of the analyte sensor is configured to be located beneath a skin layer of a subject and in contact with a bodily fluid of the subject.

[0459] Clause 85. The system of clause 84, wherein the sensor control device is further configured to transmit data indicative of the subject's analyte level to the reader device.

[0460] Clause 86. The system of any of clauses 79 to 85, wherein the wireless communication circuitry of the reader device is configured to receive data indicative of the subject's analyte level according to a Bluetooth or near field communication wireless protocol.

[0461] Clause 87. The system of any of Clauses 79 to 86, wherein the peak analyte level value comprises a highest glucose value that exceeds a predetermined analyte level threshold.

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

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

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

[0465] Clause 91. The system of any one of clauses 79 to 90, wherein the analyte level variance value is determined by subtracting the initial analyte level value from the peak analyte level value.

[0466] Clause 92. A system according to any of clauses 79 to 91, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and associated analyte level variance values ​​in a memory of the reader device.

[0467] Clause 93. The system of any of clauses 79 to 92, wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to display a notification that a meal entry has not been entered after a predetermined reminder time period.

[0468] Clause 94. A system according to clause 93, wherein the scheduled reminder period is one week.

[0469] Clause 95. A system according to clause 93, wherein the scheduled reminder period is three days.

[0470] Clause 96. A system according to clause 93, wherein the predetermined reminder period is one day.

[0471] Clause 97. The system of any one of clauses 79 to 96, wherein the initial analyte level value is determined based on meal time information input by the subject.

[0472] Item 98. A system for monitoring a dietary-related analyte response in a subject, the system comprising: a reader device comprising: wireless communication circuitry configured to receive data indicative of an analyte level in the subject; one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a diary graphical user interface (GUI), the diary GUI comprising a plurality of dietary entries, wherein each of the plurality of dietary entries comprises: a date of each dietary entry, a meal name, a graphical representation of an analyte level variance value associated with each dietary entry, and a numerical representation of the analyte level variance value associated with each dietary entry.

[0473] Clause 99. The system of clause 98, wherein the graphical representation of the analyte level variance values ​​comprises a plurality of segments.

[0474] Clause 100. A system according to clause 99, wherein the plurality of segments include a first segment, and wherein the first segment indicates analyte level variance values ​​within a first analyte level variance range, and wherein the plurality of segments include a second segment, and wherein the second segment indicates analyte level variance values ​​within a second analyte level variance range that is different from the first analyte level variance range.

[0475] Clause 101. The system of clause 100, wherein the first segment has a different color than the second segment.

[0476] Clause 102. The system of clause 100, wherein the first segment comprises a different area than the second segment.

[0477] Clause 103. The system of any of clauses 100 to 102, wherein the first analyte level variance range is less than 70 mg / dL.

[0478] Clause 104. The system of any of clauses 100 to 102, wherein the second analyte level variance range is between 70 mg / dL and 120 mg / dL.

[0479] Clause 105. The system of any of clauses 100 to 104, wherein the plurality of segments further comprises a third segment indicating analyte level variance values ​​within a third analyte level variance range that is different from both the first analyte level variance range and the second analyte level variance range.

[0480] Clause 106. The system of clause 105, wherein the third segment has a different color than the first segment and the second segment.

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

[0482] Clause 108. The system of any of clauses 98 to 107, wherein each meal entry of the plurality of meal entries further comprises an activity field.

[0483] Clause 109. The system of any of clauses 98 to 108, wherein each meal entry of the plurality of meal entries further comprises a notes field.

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

[0485] Clause 111. The system of any of Clauses 98 to 110, wherein each dietary entry of the plurality of dietary entries further comprises a weighted average of analyte level variance values.

[0486] Clause 112. The system of clause 111, wherein the weighted average of the analyte level variance values ​​is based on a plurality of historical meal entries having the same or similar meals or foods as each meal entry.

[0487] Clause 113. The system of clause 111, wherein the weighted average of the analyte level variance values ​​is determined by a weighted average function that includes a recency factor.

[0488] Clause 114. The system of clause 113, wherein the recency factor of the weighted average function is configured to reduce the analyte level variance value of the historical dietary entry by a predetermined factor for each day between the date of the historical dietary entry and the current date.

[0489] Item 115. A system for monitoring a meal-related analyte response in a subject, the system comprising: a reader device comprising: wireless communication circuitry configured to receive data indicating an analyte level of the subject; one or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to output a trend graphical user interface (GUI), the trend GUI comprising a blood glucose response view and a meal view, wherein the blood glucose response view comprises a graphical representation reflecting a plurality of segments, the plurality of segments comprising a first segment and a second segment, wherein the first segment indicates a first analyte level variance range and the second segment indicates a second analyte level variance range different from the first analyte level variance range.

[0490] Clause 116. The system of clause 115, wherein the first segment indicates a first set of meal entries, each meal entry having an analyte level variance value within a first analyte level variance range.

[0491] Clause 117. The system of clause 115 or clause 116, wherein the second segment indicates a second set of meal entries, each meal entry having an analyte level variance value within a second analyte level variance range.

[0492] Clause 118. A system according to any one of clauses 115 to 117, wherein the meal view comprises: a plurality of meal entries, wherein each of the plurality of meal entries comprises: a date and time of each meal entry, a meal name, a graphical representation of analyte level variance values ​​associated with each meal entry, and a numerical representation of the analyte level variance values ​​associated with each meal entry.

[0493] Item 119. A method for monitoring a dietary-related analyte response in a user, the method comprising: receiving data indicating an analyte level of a user via a wireless communication circuit; identifying an analyte response of the user based on the data indicating the analyte level; and outputting a first challenge graphical user interface (GUI) by a processor coupled to a memory storing a dietary monitoring application, the first challenge GUI reflecting a list of one or more challenges related to the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card; wherein the first challenge card reflects one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being performed by the user on the dietary monitoring application, wherein the second challenge card reflects one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and wherein the third challenge card reflects one or more unattempted challenges, wherein each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

[0494] Item 120. A method for monitoring dietary-related analyte responses in a user, the method comprising: receiving dietary information input by a user by a processor coupled to a memory storing a dietary monitoring application, wherein the dietary information reflects the user's food selections; and outputting a main graphical user interface (GUI) by the processor, the main GUI comprising: a plurality of optional sections, wherein the plurality of optional sections include a user profile section, a meal entry section, a trends section, a diary section, and a report section; a meal card configured to display one or more meal lists, the one or more meal lists including input dietary information related to one or more meals consumed by the user; a trend card including a graphical representation of information related to an analyte response associated with the user's food selections; a challenge card reflecting a list of one or more challenges related to the user's analyte response or glucose level; and a recommendation card reflecting one or more recommendations related to the user's food selections or analyte response.

[0495] Item 121. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicating an analyte level of a user via a wireless communication circuit; identifying, by a processor coupled to a memory storing a meal monitoring application, a peak analyte level value of data indicating an analyte level of a subject received within a predetermined time period; determining, by the processor, an estimated meal start time and an initial analyte level value based on the peak analyte level value; determining, by the processor, an analyte level variance value; prompting, by the processor, the subject to enter meal information; and associating, by the processor, the entered meal information with the analyte level variance value.

[0496] Item 122. A method for monitoring a dietary-related analyte response in a user, the method comprising: receiving data indicating an analyte level of a user via a wireless communication circuit; receiving dietary information input by a user by a processor coupled to a memory storing a dietary monitoring application; receiving data indicating the analyte level of the user by the processor within a predetermined amount of time after the dietary information is input by the user; identifying by the processor a peak analyte level value of the received data indicating the analyte level of the subject; determining by the processor an initial analyte level value; determining by the processor an analyte level variance value; and associating by the processor the input dietary information with the analyte level variance value.

[0497] Item 123. A method for monitoring a dietary-related analyte response in a user, the method comprising: receiving data indicating an analyte level of the user via a wireless communication circuit; outputting a diary graphical user interface (GUI) by a processor coupled to a memory storing a dietary monitoring application, the diary GUI comprising a plurality of dietary entries, wherein each of the plurality of dietary entries comprises: a date of each dietary entry, a meal name, a graphical representation of an analyte level variance value associated with each dietary entry, and a numerical representation of the analyte level variance value associated with each dietary entry.

[0498] Item 124. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicating an analyte level of a user via a wireless communication circuit; and outputting a trend graphical user interface (GUI) by a processor coupled to a memory storing a meal monitoring application, the trend GUI comprising a blood glucose response view and a meal view, wherein the blood glucose response view comprises a graphical representation reflecting a plurality of segments, the plurality of segments comprising a first segment and a second segment, wherein the first segment indicates a first analyte level variance range and the second segment indicates a second analyte level variance range that is different from the first analyte level variance range.

Claims

1. A system for monitoring a meal-related analyte response in a user, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the user, one or more processors coupled to a memory storing a dietary monitoring application, the dietary monitoring application, when executed by the one or more processors, causing the one or more processors to output a first challenge graphical user interface (GUI), the first challenge graphical user interface (GUI) reflecting a list of one or more challenges associated with the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card, wherein the first challenge card reflects the one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being performed by the user on the dietary monitoring application, wherein the second challenge card reflects the one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and Wherein the third challenge card reflects one or more unattempted challenges, wherein each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

2. The system according to claim 1, wherein: The first challenge card includes one or more selectable first challenge icons, wherein each of the one or more selectable first challenge icons reflects a challenge currently being performed by the user.

3. The system according to claim 2, wherein: Each of the one or more selectable first challenge icons includes a first indicator, a picture, and a text description related to a challenge currently in progress, wherein the first indicator is displayed on the picture and the first indicator is configured to indicate that the challenge is currently in progress.

4. The system according to claim 3, wherein: The first indicator is a green dot.

5. A system according to any preceding claim, wherein: The second challenge card includes one or more selectable second challenge icons, wherein each of the one or more selectable second challenge icons reflects a challenge to be completed by the user.

6. The system according to claim 5, wherein: Each of the one or more optional second challenge icons includes a second indicator, an image, and a text description associated with a completed challenge, wherein the second indicator is superimposed on the image and the second indicator is configured to indicate that the challenge has been completed by the user.

7. The system according to claim 6, wherein: The second indicator is a colored check mark.

8. A system according to any preceding claim, wherein: The third challenge card includes one or more selectable third challenge icons, wherein each of the one or more selectable third challenge icons reflects a challenge that the user has not yet attempted.

9. The system according to claim 8, wherein: Each of the one or more selectable third challenge icons includes a picture and a text description associated with a completed challenge.

10. A system according to any preceding claim, wherein: Each of the first challenge card, the second challenge card, and the third challenge card includes a plurality of selectable challenge icons, wherein a first set of the plurality of selectable challenge icons is displayed on the first challenge GUI, wherein the reader device further includes a touch screen, and wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: Receiving input corresponding to a sliding gesture or a dragging gesture from the touch screen, and in response to the received input, displaying a second set of the multiple optional challenge icons on the first challenge GUI, wherein at least one or more of the multiple optional challenge icons of the second set is different from at least one or more of the multiple optional challenge icons of the first set.

11. A system according to any preceding claim, wherein: the list of one or more challenges including one or more selectable challenge icons, wherein each of the one or more selectable challenge icons corresponds to one of the one or more challenges related to the analyte response or glucose level of the user, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting one of the one or more selectable challenge icons, a second challenge GUI is outputted that reflects contextual information related to one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons.

12. The system according to claim 11, wherein: The second challenge GUI includes: a challenge profile portion including a selected one of the one or more selectable challenge icons, a picture, and a challenge title providing a text description of one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons; an attempt 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; and A completion indicator is configured to indicate the time when the user last successfully completed one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons.

13. A system according to claim 11 or claim 12, wherein: If one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an unattempted challenge, the second challenge GUI further includes a start button, wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting the start button, an unattempted challenge on the meal monitoring application is started.

14. The system according to claim 13, wherein: The meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting the start button, an unattempted challenge on the meal monitoring application is started the next day.

15. A system according to claim 11 or claim 12, wherein: If one of the one or more challenges corresponding to the selected one of the one or more selectable challenge icons is an active challenge, the second challenge GUI further includes a stop button, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting the stop button, continuing the active challenge is stopped.

16. A system according to claim 11 or claim 12, wherein: If one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an active challenge, the second challenge GUI also includes a progress card, which is configured to indicate the progress made by the user on the active challenge, wherein the progress card includes a unit of measurement and a time unit indicating the progress.

17. The system of claim 16, wherein: The units of measurement include fractional units, and wherein the units of time include days.

18. A system according to claim 11 or claim 12, wherein: If one of the one or more challenges corresponding to a selected one of the one or more optional challenge icons is an active challenge, a modal is displayed on the second challenge GUI, wherein the modal is configured to prompt the user to provide progress information related to the active challenge in the dietary monitoring application.

19. The system of claim 18, wherein: The dietary monitoring application is configured to detect whether the user successfully completes the proactive challenge based on the tracked progress, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: outputting a third challenge GUI in response to the dietary monitoring application detecting that the user successfully completes the proactive challenge, wherein the third challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message congratulating the user for successfully completing the proactive challenge, and In response to the dietary monitoring application detecting that the user successfully completes the proactive challenge, identifying the proactive challenge as a completed challenge, wherein the third challenge GUI further comprises a first button, wherein when the first button is selected by the user, the first button is configured to restart the completed challenge, and Wherein, the third challenge GUI further includes a second button, which, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from a list of one or more challenges reflected by the first challenge GUI.

20. The system of claim 19, wherein: In response to the user selecting the first button, a modal is displayed on the third challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart a completed challenge.

21. The system of claim 18, wherein: The meal monitoring application is configured to detect whether the user successfully completes the active challenge based on the tracked progress, wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to the dietary monitoring application detecting that the user did not successfully complete the active challenge, outputting a fourth challenge GUI, wherein the fourth challenge GUI includes a challenge profile portion, an attempt indicator, a completion indicator, and a message notifying the user that the active challenge was not successfully completed, and In response to the dietary monitoring application detecting that the proactive challenge was not successfully completed, identifying the proactive challenge as a completed challenge, wherein the fourth challenge GUI further comprises a first button, wherein when the first button is selected by the user, the first button is configured to restart the completed challenge, and Wherein, the fourth challenge GUI further includes a second button, which, when selected by the user, outputs the first challenge GUI, wherein the user selects a different challenge from a list of one or more challenges reflected by the first challenge GUI.

22. The system of claim 21, wherein: In response to the user selecting the first button, a modal is displayed on the fourth challenge GUI, and wherein the modal is configured to prompt the user to confirm whether the user wants to restart the completed challenge.

23. A system according to any preceding claim, wherein: The dietary monitoring application comprises a home page GUI, the home page GUI comprising a challenge card, wherein the challenge card comprises a selectable link, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to the user selecting the link, the first challenge GUI is output.

24. A system according to any preceding claim, wherein: Each of the one or more challenges is configured to represent a challenge to a behavior or activity of the user that can affect an analyte level of the user.

25. A system for monitoring a meal-related analyte response in a user, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the user, One or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to: receiving dietary information input by the user, wherein the dietary information is configured to reflect food selections of the user; Output a homepage graphical user interface (GUI), wherein the homepage GUI includes: a plurality of selectable sections, the plurality of selectable sections comprising 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 listings including input meal information associated with one or more meals consumed by the user; a trend card including a graphical representation reflecting information related to analyte responses associated with food selections of the user; a challenge card reflecting a list of one or more challenges related to the user's analyte response or glucose level; and A recommendation card reflecting one or more recommendations related to the user's food selection or analyte response.

26. The system of claim 25, wherein: The recommendation card includes one or more selectable recommendation icons, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations.

27. The system of claim 26, wherein: Each of the one or more selectable recommendation icons includes an image related to a corresponding one of the one or more recommendations, and a recommendation title providing a text description of the corresponding recommendation of the one or more recommendations.

28. A system according to any one of claims 25 to 27, wherein: The recommendation card includes a plurality of selectable recommendation icons, wherein a first set of the plurality of selectable recommendation icons is displayed on the recommendation card, wherein the reader device further includes a touch screen, and wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: Receive input corresponding to a sliding gesture or a dragging gesture from the touch screen, and in response to the received input, display a second set of the multiple optional recommendation icons on the recommendation card, wherein at least one or more of the multiple optional recommendation icons of the second set is different from at least one or more of the multiple optional recommendation icons of the first set.

29. A system according to any one of claims 25 to 28, wherein: The recommendation card includes one or more selectable recommendation icons, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting one of the one or more selectable recommendation icons, a modal is output on the homepage GUI, wherein the modal provides contextual information related to a corresponding recommendation among the one or more recommendations, and wherein the modal is configured to guide the user to take action based on the corresponding recommendation among the one or more recommendations.

30. A system according to any one of claims 25 to 29, wherein: The meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: detecting a food selection of the user; Analyze the dietary information entered; as well as Based on the analysis, one or more selectable recommendation icons are displayed on the recommendation card, wherein each of the one or more selectable recommendation icons reflects a recommendation related to the food selection or analyte response of the user.

31. A system according to any one of claims 25 to 30, wherein: The recommendation card includes one or more selectable recommendation icons, wherein each of the one or more selectable recommendation icons corresponds to one of the one or more recommendations, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to selecting one of the one or more selectable recommendation icons, the selected one of the one or more selectable recommendation icons is removed from the recommendation card, and a new selectable recommendation icon is displayed on the recommendation card to replace the removed recommendation icon.

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

33. The system of claim 32, wherein: The meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: detecting when the predetermined time period is reached, In response to reaching the predetermined time period, replacing one or more selectable recommendation icons on the recommendation card with a new set of one or more selectable recommendation icons, Wherein, at least one of the one or more selectable recommendation icons in the new set is different from at least one of the replaced one or more selectable recommendation icons.

34. A system according to any one of claims 25 to 33, wherein: The home page GUI is configured to switch between a plurality of views, wherein the plurality of views includes at least a first view and a second view.

35. The system of claim 34, wherein: The home page GUI is in the first view, wherein the home page GUI is configured to display the user profile portion, the meal entry portion, the diary portion, and the meal card in the first view, wherein the reader device further comprises a touch screen, wherein the meal monitoring application, when executed by the one or more processors, further causes the one or more processors to: receiving an input corresponding to a scroll gesture, a slide gesture, a pull gesture, or a drag gesture from the touch screen, and Wherein, in response to the received input, the home page GUI is configured to switch from the first view to the second view, wherein the trend card, the challenge card, and the recommendation card are displayed on the home page GUI in the second view.

36. A system according to any one of claims 25 to 35, wherein: The home page GUI is configured to transition between a plurality of views, wherein each of the plurality of views is different, wherein the reader device further comprises a touch screen, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: receiving an input corresponding to a scroll gesture, a slide gesture, a pull gesture, or a drag gesture from the touch screen, and In response to the received input, one of the plurality of views of the home page GUI is displayed.

37. A system according to any one of claims 25 to 36, wherein: The meal card is configured to display one or more meal listings including meal information related to one or more of the most recently consumed meals.

38. A system according to any one of claims 25 to 37, wherein: Each of the one or more meal lists includes detailed information of a meal consumed by the user, wherein the one or more meal lists are displayed on the meal card in chronological order, wherein a meal list corresponding to a most recently consumed meal is displayed at a top portion of the meal card.

39. A system according to any one of claims 25 to 38, wherein: Each of the one or more meal lists includes detailed information of a meal consumed by the user and a corresponding meal-related analyte response for the meal.

40. A system according to any one of claims 25 to 39, wherein: Each of the one or more meal lists includes: a textual description of a meal consumed by said user; a portion size indicator, including information indicating that the meal is small, medium, or large compared to a typical meal serving for said user; a date stamp associated with a date on which the meal was consumed by the user; a timestamp associated with the time when the meal was consumed; and A graphical representation of the analyte response associated with the meal.

41. The system of claim 40, wherein: The graphical representation includes a plurality of segments.

42. The system of claim 41, wherein: The plurality of segments include a first segment, and wherein the first segment indicates an analyte response including a hypoglycemic response, wherein the plurality of segments includes a second segment, wherein the second segment indicates an analyte response including a moderate glycemic response, and Wherein the plurality of segments includes a third segment, wherein the third segment is indicative of an analyte response including a hyperglycemic response.

43. The system of claim 42, wherein: The first segment, the second segment, and the third segment each have a different color.

44. A system according to any one of claims 25 to 43, wherein: The graphical representation of the trend card indicates analyte responses associated with the user's food selections over a predetermined time period.

45. The system of claim 44, wherein: The graphical representation of the trend card includes a plurality of colored segments including a first colored segment, a second colored segment, and a third colored segment.

46. ​​The system of claim 45, wherein: The first color segment includes a green color indicating a low glycemic response, wherein the second color segment includes a yellow color indicating a medium glycemic response, and wherein the third color segment includes an orange color indicating a high glycemic response.

47. A system according to any one of claims 25 to 40, wherein: The trend card includes a summary panel configured to provide an overall assessment of the user's food choices over a predetermined time period.

48. A system according to any one of claims 25 to 47, wherein: The trend card includes a summary panel including information indicative of an analyte response associated with a food selection of the user, wherein the trend card is configured to be dynamic, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: detecting whether an analyte response associated with the user's food selection provides new trend information, and In response to detecting the new trend information, an updated summary panel is populated on the trend card.

49. A system according to any one of claims 25 to 48, wherein: When data indicative of analyte levels is not received or associated with the input dietary information, the trend card is not displayed on the home page GUI.

50. A system according to any one of claims 25 to 49, wherein: The challenge card on the home page GUI includes one or more selectable challenge icons, wherein each of the one or more selectable challenge icons is configured to reflect a challenge related to an analyte response or glucose level of the user.

51. The system of claim 50, wherein: Each of the one or more selectable challenge icons includes a picture associated with a challenge reflected by the selected challenge icon and a challenge title providing a textual description of the challenge reflected by the selected challenge icon.

52. The system of claim 51, wherein: A live indicator is displayed on the picture to indicate that the challenge reflected by the picture is an active challenge on the meal monitoring application.

53. A system according to any one of claims 25 to 52, wherein: The challenge card includes an optional link, wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: In response to the user selecting the link, a first challenge GUI including information about all challenges provided on the dietary monitoring application is output.

54. A system according to any one of claims 25 to 53, wherein: The challenge card includes a plurality of selectable recommendation icons, wherein a first set of the plurality of selectable challenge icons is displayed on the challenge card, wherein the reader device further includes a touch screen, and wherein the dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to: Receive input corresponding to a slide gesture or a drag gesture from the touch screen, and in response to the received input, display a second set of the multiple optional challenge icons on the challenge, wherein at least one or more of the multiple optional challenge icons of the second set is different from at least one or more of the multiple optional challenge icons of the first set.

55. A system according to any one of claims 25 to 54, wherein: The challenge card includes a plurality of selectable challenge icons, wherein the challenge card is configured to display two or three of the plurality of selectable challenge icons simultaneously on the homepage GUI.

56. A system according to any one of claims 25 to 55, wherein: The recommendation card includes a plurality of selectable recommendation icons, wherein the recommendation card is configured to display two or three of the plurality of selectable recommendation icons simultaneously.

57. A system according to any one of claims 25 to 56, wherein: The home page GUI also includes a navigation bar.

58. A system according to any one of claims 25 to 57, wherein: The home page GUI also includes a banner including messages related to scanning sensors and meal impact.

59. A system for monitoring a meal-related analyte response in a subject, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the subject, One or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to: for the received data indicative of the analyte level of the subject, identifying a peak analyte level value within a predetermined time period, determining an estimated meal start time and an initial analyte level value based on the peak analyte level value, Determine the analyte level variance value, prompting the subject to enter dietary information, and The input dietary information is correlated with the analyte level variance value.

60. The system of claim 59, wherein: The reader device comprises a smartphone.

61. A system according to claim 59 or claim 60, wherein: The data indicative of the analyte level of the subject includes data indicative of glucose level.

62. The system of any one of claims 59 to 61 further comprising a trusted computer system, wherein: The trusted computer system is a cloud computing platform including one or more servers.

63. The system of claim 62, wherein: The trusted computer system is configured to transmit data indicative of the subject's analyte level to the reader device.

64. The system of any one of claims 59 to 63, further comprising a sensor control device, wherein: The sensor control device includes an analyte sensor, and wherein at least a portion of the analyte sensor is configured to be located beneath a skin layer of the subject and in contact with a bodily fluid of the subject.

65. The system of claim 64, wherein: The sensor control device is also configured to transmit data indicative of the subject's analyte level to the reader device.

66. A system according to any one of claims 59 to 65, wherein: The wireless communication circuitry of the reader device is configured to receive data indicative of the subject's analyte level according to a Bluetooth or near field communication wireless protocol.

67. A system according to any one of claims 59 to 66, wherein: The peak analyte level values ​​include the highest glucose value that exceeds a predetermined analyte level threshold.

68. The system of claim 67, wherein: The predetermined analyte level threshold is 170 mg / dL.

69. The system of claim 67, wherein: The predetermined analyte level threshold is 180 mg / dL.

70. The system of claim 67, wherein: The predetermined analyte level threshold is 190 mg / dL.

71. A system according to any one of claims 59 to 70, wherein: The predetermined time period of received data indicative of the subject's analyte level includes the last two hours of analyte data.

72. A system according to any one of claims 59 to 71, wherein: The predetermined time period of received data indicative of the subject's analyte level includes the last four hours of analyte data.

73. A system according to any one of claims 59 to 72, wherein: The predetermined time period of received data indicative of the subject's analyte level includes the last eight hours of analyte data.

74. A system according to any one of claims 59 to 73, wherein: The estimated meal start time was determined by counting back two hours from the time of the peak analyte level value.

75. A system according to any one of claims 59 to 73, wherein: The estimated meal start time was determined by counting back three hours from the time of the peak analyte level value.

76. A system according to any one of claims 59 to 73, wherein: The estimated meal start time was determined by counting back four hours from the time of the peak analyte level value.

77. A system according to any one of claims 59 to 76, wherein: The analyte level variance value is determined by subtracting the initial analyte level value from the peak analyte level value.

78. A system according to any one of claims 59 to 77, wherein: The dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and associated analyte level variance values ​​in the memory of the reader device.

79. A system for monitoring a meal-related analyte response in a subject, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the subject, One or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to: receiving dietary information input by the subject, receiving data indicative of the analyte level of the subject within a predetermined amount of time after input of the dietary information by the subject, identifying a peak analyte level value for the received data indicative of the analyte level of the subject, Determine initial analyte level values, Determine the analyte level variance value, and The input dietary information is correlated with the analyte level variance value.

80. The system of claim 79, wherein: The reader device comprises a smartphone.

81. The system of claim 79 or claim 80, wherein: The data indicative of the analyte level of the subject includes data indicative of glucose level.

82. The system of any one of claims 79 to 81, further comprising a trusted computer system, wherein: The trusted computer system is a cloud computing platform including one or more servers.

83. The system of any one of claims 79 to 82, wherein: A trusted computer system is configured to transmit data indicative of the analyte level of the subject to the reader device.

84. The system of any one of claims 79 to 83, further comprising a sensor control device, wherein: The sensor control device includes an analyte sensor, and wherein at least a portion of the analyte sensor is configured to be located beneath a skin layer of the subject and in contact with a bodily fluid of the subject.

85. The system of claim 84, wherein: The sensor control device is also configured to transmit data indicative of the analyte level of the subject to the reader device.

86. A system according to any one of claims 79 to 85, wherein: The wireless communication circuitry of the reader device is configured to receive data indicative of the analyte level of the subject according to a Bluetooth or near field communication wireless protocol.

87. A system according to any one of claims 79 to 86, wherein: The peak analyte level values ​​include the highest glucose value that exceeds a predetermined analyte level threshold.

88. The system of claim 87, wherein: The predetermined analyte level threshold is 170 mg / dL.

89. The system of claim 87, wherein: The predetermined analyte level threshold is 180 mg / dL.

90. The system of claim 87, wherein: The predetermined analyte level threshold is 190 mg / dL.

91. The system of any one of claims 79 to 90, wherein: The analyte level variance value is determined by subtracting the initial analyte level value from the peak analyte level value.

92. The system of any one of claims 79 to 91, wherein: The dietary monitoring application, when executed by the one or more processors, further causes the one or more processors to store the dietary information and associated analyte level variance values ​​in the memory of the reader device.

93. The system of any one of claims 79 to 92, wherein: The meal monitoring application, when executed by the one or more processors, further causes the one or more processors to display a notification that a meal entry has not been entered after a predetermined reminder time period.

94. The system of claim 93, wherein: The predetermined reminder time period is one week.

95. The system of claim 93, wherein: The predetermined reminder period is three days.

96. The system of claim 93, wherein: The predetermined reminder time period is one day.

97. The system of any one of claims 79 to 96, wherein: The initial analyte level value is determined based on meal time information input by the subject.

98. A system for monitoring a meal-related analyte response in a subject, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the subject, One or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to output a diary graphical user interface (GUI), the diary GUI including a plurality of meal entries, wherein each meal entry in the plurality of meal entries includes: The date of each meal entry stated, Meal name, a graphical representation of the variance values ​​of the analyte levels associated with each of the dietary items, and A numerical representation of the variance value of the analyte level associated with each of the dietary items.

99. The system of claim 98, wherein: The graphical representation of the analyte level variance values ​​includes a plurality of segments.

100. The system of claim 99, wherein: The plurality of segments include a first segment, and wherein the first segment indicates an analyte level variance value within a first analyte level variance range, and Wherein the plurality of segments includes a second segment, and wherein the second segment indicates analyte level variance values ​​within a second analyte level variance range different from the first analyte level variance range.

101. The system of claim 100, wherein: The first segment has a different color than the second segment.

102. The system of claim 100, wherein: The first segment includes a different area than the second segment.

103. The system of any one of claims 100 to 102, wherein: The first analyte level has a variance range of less than 70 mg / dL.

104. The system of any one of claims 100 to 102, wherein: The second analyte level variance range is between 70 mg / dL and 120 mg / dL.

105. The system of any one of claims 100 to 104, wherein: The plurality of segments also includes a third segment that indicates analyte level variance values ​​within a third analyte level variance range that is different from both the first analyte level variance range and the second analyte level variance range.

106. The system of claim 105, wherein: The third segment has a different color than the first segment and the second segment.

107. The system of any one of claims 98 to 106, wherein: Each of the plurality of meal entries further includes a time of the each meal entry.

108. The system of any one of claims 98 to 107, wherein: Each meal entry of the plurality of meal entries also includes an activity field.

109. The system of any one of claims 98 to 108, wherein: The each of the plurality of meal entries also includes a notes field.

110. The system of any one of claims 98 to 109, wherein: The diary GUI also includes a view setting configured to display the plurality of meal entries by day or by week.

111. The system of any one of claims 98 to 110, wherein: Each of the plurality of meal entries also includes a weighted average of the analyte level variance values.

112. The system of claim 111, wherein: The weighted average of the analyte level variance values ​​is based on a plurality of historical meal entries having the same or similar meals or foods as each meal entry.

113. The system of claim 111, wherein: The weighted average of the analyte level variance values ​​is determined by a weighted average function that includes a recency factor.

114. The system of claim 113, wherein: The recency factor of the weighted average function is configured to reduce the analyte level variance value of the historical dietary entry by a predetermined factor for each day between a date of the historical dietary entry and a current date.

115. A system for monitoring a meal-related analyte response in a subject, the system comprising: Reader device, including: wireless communication circuitry configured to receive data indicative of an analyte level of the subject, one or more processors coupled to a memory storing a meal monitoring application, the meal monitoring application, when executed by the one or more processors, causing the one or more processors to output a trend graphical user interface (GUI), the trend GUI including a glycemic response view and a meal view, wherein the blood glucose response view includes a graphical representation reflecting a plurality of segments, the plurality of segments including a first segment and a second segment, wherein the first segment indicates a first analyte level variance range and the second segment indicates a second analyte level variance range different from the first analyte level variance range.

116. The system of claim 115, wherein: The first segment indicates a first set of meal entries each having an analyte level variance value within the first analyte level variance range.

117. The system of claim 115 or claim 116, wherein: The second segment indicates a second set of meal entries each having an analyte level variance value within the second analyte level variance range.

118. The system of any one of claims 115 to 117, wherein: The meal view includes: A plurality of meal items, wherein each of the plurality of meal items comprises: the date and time of each meal entry described, Meal name, a graphical representation of the variance values ​​of the analyte levels associated with each of the dietary items, and A numerical representation of the variance value of the analyte level associated with each of the dietary items.

119. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicative of an analyte level of a user via the wireless communications circuitry; identifying an analyte response of the user based on the data indicative of the analyte level; as well as outputting, by a processor coupled to a memory storing a dietary monitoring application, a first challenge graphical user interface (GUI), the first challenge GUI reflecting a list of one or more challenges associated with the user's analyte response, wherein the one or more challenges include one or more active challenges, one or more completed challenges, and one or more unattempted challenges, the first challenge GUI including a first challenge card, a second challenge card, and a third challenge card; wherein the first challenge card reflects the one or more active challenges, wherein each of the one or more active challenges reflects a challenge currently being performed by the user on the dietary monitoring application, wherein the second challenge card reflects the one or more completed challenges, wherein each of the one or more completed challenges reflects a challenge completed by the user, and wherein the third challenge card reflects one or more unattempted challenges, wherein, Each of the one or more unattempted challenges reflects a challenge in which the user has not yet participated.

120. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving, by a processor coupled to a memory storing a dietary monitoring application, dietary information input by the user, wherein the dietary information reflects food selections of the user; and The processor outputs a homepage graphical user interface (GUI), wherein the homepage GUI includes: a plurality of selectable sections, wherein the plurality of selectable sections include 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 listings including input meal information associated with one or more meals consumed by the user; a trend card including a graphical representation reflecting information related to analyte responses associated with food selections of the user; a challenge card reflecting a list of one or more challenges related to the user's analyte response or glucose level; and A recommendation card reflecting one or more recommendations related to the user's food selection or analyte response.

121. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicative of an analyte level of a user via the wireless communications circuitry; identifying, by a processor coupled to a memory storing a dietary monitoring application, for the received data indicative of the analyte level of the subject, a peak analyte level value within a predetermined time period; determining, by the processor, an estimated meal start time and an initial analyte level value based on the peak analyte level value; determining, by the processor, an analyte level variance value; Prompting the subject to input dietary information by the processor; as well as The input dietary information is correlated, by the processor, with the analyte level variance value.

122. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicative of an analyte level of a user via the wireless communications circuitry; receiving, by a processor coupled to a memory storing a meal monitoring application, meal information input by the user; receiving, by a processor, data indicative of the analyte level of the user within a predetermined amount of time after input of the dietary information by the user; identifying, by the processor, a peak analyte level value of the received data indicative of the analyte level of the subject; determining, by the processor, an initial analyte level value; determining, by the processor, an analyte level variance value; as well as The input dietary information is correlated, by the processor, with the analyte level variance value.

123. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicative of an analyte level of a user via the wireless communications circuitry; A diary graphical user interface (GUI) is outputted by a processor coupled to a memory storing a meal monitoring application, the diary graphical user interface (GUI) comprising a plurality of meal entries, wherein each meal entry of the plurality of meal entries comprises: The date of each meal entry stated, Meal name, a graphical representation of the variance values ​​of the analyte levels associated with each of the dietary items, and A numerical representation of the variance value of the analyte level associated with each of the dietary items.

124. A method for monitoring a meal-related analyte response in a user, the method comprising: receiving data indicative of an analyte level of a user via the wireless communications circuitry; as well as outputting, by a processor coupled to a memory storing a meal monitoring application, a trend graphical user interface (GUI), the trend graphical user interface (GUI) comprising a glycemic response view and a meal view, wherein the blood glucose response view includes a graphical representation reflecting a plurality of segments, the plurality of segments including a first segment and a second segment, wherein the first segment indicates a first analyte level variance range and the second segment indicates a second analyte level variance range different from the first analyte level variance range.

Images