Glucose monitoring across phases and corresponding phased information display

The multi-phase glucose monitoring program addresses user confusion by withholding initial data and gradually revealing insights, ensuring accurate representation of user behavior and promoting informed health actions.

JP2024542911APending Publication Date: 2024-11-19DEXCOM INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023579581
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-10-28
Filing Date
2022-08-31
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

Users of continuous glucose monitoring systems often struggle with overwhelming and complex glucose data, leading to difficulty in understanding their glucose levels and taking appropriate actions, as conventional systems may not accurately represent typical user behavior due to altered behavior in response to data output.

Method used

A multi-phase glucose monitoring program that includes phases with controlled data output, where initial data is withheld during the first phase to establish a baseline, and subsequent phases gradually reveal glucose data and insights to encourage normal behavior and facilitate learning.

Benefits of technology

This approach allows users to understand their glucose levels effectively by gradually introducing information, promoting normal behavior and improving health management through informed actions based on accurate glucose data representation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024542911000001_ABST
    Figure 2024542911000001_ABST
Patent Text Reader

Abstract

Glucose monitoring across phases and corresponding phased information display is described. A multi-phase glucose monitoring program is initiated, including at least a first phase and a second phase. First glucose data of a user is acquired during the first phase of the multi-phase glucose monitoring program. Output of the first glucose data in a glucose monitoring user interface is prevented during the first phase of the multi-phase glucose monitoring program. Second glucose data of the user is then acquired during a second phase of the multi-phase glucose monitoring program. The second glucose data is output in real time in the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 263,186, filed October 28, 2021, and entitled “Glucose Monitoring Over Phases and Corresponding Phased Information Display,” the entire disclosure of which is incorporated herein by reference. [Background technology]

[0002] Diabetes is a metabolic condition that affects hundreds of millions of people. For these people, monitoring blood glucose levels and regulating those levels within an acceptable range is important not only to mitigate long-term problems such as heart disease and vision loss, but also to avoid the effects of high and low glucose. Because blood glucose levels are almost constantly changing over time and in response to daily occurrences such as diet or exercise, maintaining the levels within an acceptable range can be difficult. Advances in medical technology have allowed the development of various systems for monitoring blood glucose, including continuous glucose monitoring (CGM) systems that measure and record glucose concentrations in virtually real time. CGM systems are an important tool for users of these systems to ensure that measured glucose values ​​are within an acceptable range.

[0003] Glucose monitoring systems utilize wearable devices that include sensors that can be inserted into the user's skin to monitor glucose, and that are coupled to a user device (e.g., the user's smartphone) so that glucose data can be output to the user, for example, via a user interface. However, in many cases, users can be overwhelmed by the amount and / or complexity of glucose data provided to the user. As a result, some users (especially new users) may have difficulty understanding their glucose data and therefore may not be able to take meaningful action to improve their health. Other users may change their behavior in an attempt to control the output of glucose data. As an example, some users may eat foods with fewer carbohydrates to keep their glucose values ​​within range. As a result, glucose data captured by conventional CGM systems may not portray the true nature of a user's typical behavior and resulting glucose readings. Summary of the Invention [Means for solving the problem]

[0004] To overcome these problems, glucose monitoring across phases and corresponding phased information display is utilized. A multi-phase glucose monitoring program is initiated, including at least a first phase and a second phase. First glucose data of the user is acquired during the first phase of the multi-phase glucose monitoring program. Output of the first glucose data in the glucose monitoring user interface is prevented during the first phase of the multi-phase glucose monitoring program. Second glucose data of the user is then acquired during the second phase of the multi-phase glucose monitoring program. The second glucose data is output in real time in the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

[0005] This Summary introduces a selection of concepts in a simplified form that are further described below in the Detailed Description. As such, this Summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The detailed description is given with reference to the accompanying drawings. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram of an environment in an example implementation operable to use the techniques described herein. [Diagram 2] 2 shows a more detailed example of the wearable glucose monitoring device of FIG. 1. [Diagram 3] An example system is presented that acquires a person's glucose data during a multi-phase glucose monitoring program and displays different respective information during different phases. [Figure 4] 13 illustrates an example implementation of a user interface in which output of glucose data acquired during phases of a multi-phase glucose monitoring program is prevented. [Diagram 5] 13 illustrates an example implementation of a user interface that displays instructions for transitioning to a subsequent phase of a multi-phase glucose monitoring program. [Figure 6] 13 illustrates an example implementation of a user interface displaying glucose data obtained during subsequent phases of a multi-phase glucose monitoring program. [Figure 7] 1 illustrates an example implementation of a user interface that displays user interface elements that can be selected to view more detailed information about one or more phases of a multi-phase glucose monitoring program. [Figure 8] 13 illustrates an exemplary implementation of a user interface that displays glucose data obtained during subsequent phases of a multi-phase glucose monitoring program and displays additional information related to the glucose data. [Figure 9] 13 illustrates another exemplary implementation of a user interface that displays glucose data obtained during subsequent phases of a multi-phase glucose monitoring program and displays additional information related to the glucose data. [Figure 10] 1 illustrates a procedure in an exemplary implementation of a multi-phase glucose monitoring program. [Figure 11] 1 illustrates a procedure in an exemplary implementation in which a glucose report is generated based on glucose data obtained during first, second, third, and fourth phases of a multi-phase glucose monitoring program. [Figure 12] An example of a system including various components of an exemplary device that may be implemented as any type of computing device described and / or utilized with reference to FIGS. 1-11 for implementing embodiments of the techniques described herein is shown. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] overview Glucose monitoring across phases and corresponding phased information display are described. A multi-phase engine is configured to acquire glucose data (e.g., glucose measurements) across multiple phases of a glucose monitoring program. As an example, the multi-phase engine may acquire first glucose data during a first phase of the glucose monitoring program, acquire second glucose data during a second phase of the glucose monitoring program, acquire third glucose data during a third phase of the glucose monitoring program, and acquire fourth glucose data during a fourth phase of the glucose monitoring program. It should be understood that a multi-phase glucose monitoring program may have fewer phases (e.g., two) or more phases (e.g., five or more) without departing from the spirit or scope of the described techniques.

[0008] In one or more implementations, each phase utilizes a different wearable glucose sensor to acquire glucose data. In this scenario, a transition between phases may correspond to a user replacing a glucose sensor associated with a previous phase with a new glucose sensor. In other words, a user wears a first glucose sensor during a first phase and then replaces the first glucose sensor with a second glucose sensor to begin a second phase. However, it should be understood that a user may proceed to different phases of a multi-phase glucose monitoring program based on the occurrence of different events or the satisfaction of different conditions, as discussed in more detail throughout.

[0009] In addition to acquiring glucose data, the multi-phase engine is configured to control the display of information related to the acquired glucose data during the multi-phase glucose monitoring program. In particular, the multi-phase engine controls the display of information such that different information is displayed during and after each phase of the program. In one or more implementations, for example, the multi-phase engine controls the display of information based on rules that define what information, if any, is displayed during and after each phase. As an example, the multi-phase engine can control what information related to the first, second, third, and fourth glucose data, respectively, is displayed during and between the first, second, third, and fourth phases of the multi-phase glucose monitoring program.

[0010] As part of determining what information is displayed during different phases, the multi-phase engine may be configured to determine the end of a phase. For example, the multi-phase engine may be configured in various ways to detect a completion event indicating the end of a phase. In connection with a first phase, for example, the multi-phase engine may detect a completion event indicating the completion of the first phase. Examples of completion events that may be detected by the multi-phase engine include detecting removal of a glucose sensor for each of a phase end, detecting insertion of a glucose sensor for a phase following a phase end, detecting expiration of a glucose monitoring period associated with a phase end, and detecting a user input to end a completed phase and / or start a next phase, to name a few.

[0011] The multi-phase engine is configured to display information about the acquired glucose data via a user interface displayed on a display device of the user's computing device, e.g., the user's smartwatch or smartphone. In the first phase, for example, the multi-phase engine may prevent the display of the first glucose data acquired during the first phase via the user interface. In other words, the glucose data is not displayed via the user interface in the illustrated first phase. Doing so may encourage the user to "act normally" during the first phase, to behave as if the user were not wearing the wearable glucose monitoring device. In this way, the first glucose data may provide a baseline against which data from subsequent phases may be compared to derive various insights about the user's behavior.

[0012] In contrast, the multi-phase engine may display at least a portion of the second glucose data acquired during the second phase, e.g., the user's current glucose level, via the user interface. In particular, the user's current glucose level may correspond to information that the multi-phase engine prevented from being displayed during the first phase. Alternatively or additionally, the multi-phase engine may display limited insights and / or limited recommendations derived from the second glucose data via the user interface. It should be understood that the information displayed in each phase may vary depending on the design (e.g., rules) of a given multi-phase glucose monitoring program. However, in general, the multi-phase engine gradually reveals different information (e.g., more information and / or more detailed information) in subsequent phases of the glucose monitoring program. Similarly, in the third and / or fourth phases of the glucose monitoring program, the multi-phase engine may control the user interface to display different information to the user, e.g., more information than was displayed in the second phase.

[0013] By gradually revealing information to the monitored user, rather than presenting the information from the beginning of the program as in conventional glucose monitoring systems, the multi-phase engine may learn how the user behaves "normally" because no information is output that will "scare" the user into behaving differently than normal. The multi-phase engine may also more effectively educate the user as to what the information output via the user interface means, because the user is only shown a certain amount of new information in each phase, so that the user has time to learn about the information before additional and / or more detailed information is output in subsequent phases. In other words, by gradually revealing information, the multi-phase engine helps a person build up their knowledge over time.

[0014] In some aspects, techniques described herein relate to a computer-implemented method including initiating a multi-phase glucose monitoring program including at least a first phase and a second phase, acquiring first glucose data for a user during the first phase of the multi-phase glucose monitoring program, preventing output of the first glucose data in a glucose monitoring user interface during the first phase of the multi-phase glucose monitoring program, acquiring second glucose data for the user during a second phase of the multi-phase glucose monitoring program, and outputting the second glucose data in real time in the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

[0015] In some aspects, the techniques described herein relate to a computer-implemented method in which first glucose data is collected by a first glucose sensor worn by a user during a first phase of a multi-phase glucose monitoring program, and second glucose data is collected by a second glucose sensor worn by the user during a second phase of the multi-phase glucose monitoring program.

[0016] In some aspects, the techniques described herein relate to computer-implemented methods in which the first glucose data and the second glucose data are each obtained from a single transmitter communicatively coupled to a computing device that displays a glucose monitoring user interface.

[0017] In some aspects, the techniques described herein relate to a computer-implemented method further including detecting a completion event indicating completion of the first phase.

[0018] In some aspects, the techniques described herein relate to a computer-implemented method that further includes outputting information based on the first glucose data in a glucose monitoring user interface after detecting completion of the first phase.

[0019] In some aspects, the techniques described herein relate to computer-implemented methods in which the completion event includes one of detecting removal of a first glucose sensor worn by a user during a first phase, detecting insertion of a second glucose sensor for a second phase, detecting expiration of a glucose monitoring period associated with a first phase of a multi-phase glucose monitoring program, or detecting user input via a glucose monitoring user interface to end the first phase or initiate a second phase.

[0020] In some aspects, the techniques described herein relate to computer-implemented methods in which the first glucose data and the second glucose data are collected by a single glucose sensor.

[0021] In some aspects, the techniques described herein relate to a computer-implemented method further including generating a glucose report for the user upon completion of the multi-phase glucose monitoring program based at least in part on the first glucose data and the second glucose data.

[0022] In some aspects, techniques described herein relate to a computer-implemented method that includes acquiring first glucose data for a user using a first glucose sensor during a first phase of a multi-phase glucose monitoring program, acquiring second glucose data for the user using a second glucose sensor during a second phase of the multi-phase glucose monitoring program, acquiring third glucose data for the user using a third glucose sensor during a third phase of the multi-phase glucose monitoring program, acquiring fourth glucose data for the user using a fourth glucose sensor during a fourth phase of the multi-phase glucose monitoring program, and generating a glucose report based on the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data.

[0023] In some aspects, the techniques described herein relate to a computer-implemented method further including controlling a glucose monitoring user interface during a multi-phase glucose monitoring program by progressively revealing information based on the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data.

[0024] In some aspects, the techniques described herein relate to a computer-implemented method in which controlling a glucose monitoring user interface during a multi-phase glucose monitoring program further includes preventing output of the first glucose data in a first configuration of the glucose monitoring user interface during a first phase of the multi-phase glucose monitoring program, outputting the second glucose data in real-time in the second configuration of the glucose monitoring user interface during a second phase of the multi-phase glucose monitoring program, outputting the third glucose data in real-time in the third configuration of the glucose monitoring user interface along with one or more glucose insights or recommendations during a third phase of the multi-phase glucose monitoring program, and outputting the fourth glucose data in real-time in the fourth configuration of the glucose monitoring user interface along with one or more additional glucose insights or recommendations during a fourth phase of the multi-phase glucose monitoring program.

[0025] In some aspects, the techniques described herein relate to computer-implemented methods that further include generating a baseline based on first glucose data obtained during a first phase of a multi-phase glucose monitoring program, where one or more glucose insights or one or more additional glucose insights are generated based at least in part on the baseline.

[0026] In some aspects, the techniques described herein relate to a computer-implemented method in which the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data are each obtained from a single transmitter communicatively coupled to a computing device that displays a glucose monitoring user interface.

[0027] In some aspects, the techniques described herein relate to computer-implemented methods in which a single transmitter is coupled to a first glucose sensor, a second glucose sensor, a third glucose sensor, and a fourth glucose sensor during a first phase, a second phase, a third phase, and a fourth phase, respectively.

[0028] In some aspects, the techniques described herein relate to a system including a sensor kit for a multi-phase glucose monitoring program, the sensor kit including at least a first glucose sensor for monitoring glucose during a first phase of the multi-phase glucose monitoring program and a second glucose sensor for monitoring glucose during a second phase of the multi-phase glucose monitoring program, and a multi-phase engine configured to control a glucose monitoring user interface during the multi-phase glucose monitoring program, acquire first glucose data for a user from the first glucose sensor of the sensor kit during the first phase of the multi-phase glucose monitoring program, prevent output of the first glucose data in the glucose monitoring user interface during the first phase of the multi-phase glucose monitoring program, acquire second glucose data for the user during the second phase of the multi-phase glucose monitoring program, and output the second glucose data in real time in the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

[0029] In some aspects, the techniques described herein relate to a system in which the sensor kit further includes a third glucose sensor for monitoring glucose during a third phase of the multiphase glucose monitoring program, and a fourth glucose sensor for monitoring glucose during a fourth phase of the multiphase glucose monitoring program.

[0030] In some aspects, the techniques described herein relate to a system in which the multi-phase engine is further configured to acquire third glucose data for the user from a third glucose sensor of the sensor kit during a third phase of the multi-phase glucose monitoring program, and output the third glucose data in real time along with one or more glucose insights or recommendations in the glucose monitoring user interface during the third phase of the multi-phase glucose monitoring program, and acquire fourth glucose data for the user during a fourth phase of the multi-phase glucose monitoring program, and output the fourth glucose data in real time along with one or more additional glucose insights or recommendations in the glucose monitoring user interface during the fourth phase of the multi-phase glucose monitoring program.

[0031] In some aspects, the techniques described herein relate to a system further including a transmitter configured to form a wireless connection with a computing device displaying a glucose monitoring user interface, the transmitter configured to communicate the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data to the computing device.

[0032] In some aspects, the techniques described herein relate to a computer-readable storage device including stored instructions that, upon execution by one or more processors, perform operations including initiating a multi-phase glucose monitoring program including at least a first phase and a second phase, acquiring first glucose data for a user during the first phase of the multi-phase glucose monitoring program, preventing output of the first glucose data in a glucose monitoring user interface during the first phase of the multi-phase glucose monitoring program, acquiring second glucose data for the user during the second phase of the multi-phase glucose monitoring program, and outputting the second glucose data in real time in the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

[0033] In some aspects, the techniques described herein relate to a computer-readable storage device in which first glucose data is collected by a first glucose sensor worn by a user during a first phase of a multi-phase glucose monitoring program, and second glucose data is collected by a second glucose sensor worn by the user during a second phase of the multi-phase glucose monitoring program.

[0034] In the following description, an exemplary environment in which the techniques described herein can be used is first described. Then, implementation details and example procedures that can be performed in the exemplary environment, as well as in other environments, are described. The execution of the exemplary procedures is not limited to the exemplary environment, and the exemplary environment is not limited to the execution of the exemplary procedures.

[0035] Example Environment 1 is a diagram of an environment 100 in an example implementation operable to employ glucose monitoring across phases and corresponding phased information display as described herein. The illustrated environment 100 includes a person 102 shown wearing a wearable glucose monitoring device 104, examples of which include wearable glucose monitoring device 104(a), wearable glucose monitoring device 104(b), and wearable glucose monitoring device 104(c) having first, second, and third glucose sensors, respectively. The illustrated environment 100 also includes a computing device 106, which is shown to have a multi-phase engine 108. The wearable glucose monitoring device 104 and the computing device 106 are communicatively coupled, including via a network (not shown).

[0036] The wearable glucose monitoring device 104 and the computing device 106 may be communicatively coupled in various ways, such as using one or more wireless communication protocols or techniques. By way of example, the wearable glucose monitoring device 104 and the computing device 106 may communicate with each other using one or more of wireless, cellular, Wi-Fi, Bluetooth (e.g., a Bluetooth Low Energy link), near field communication (NFC), 5G, etc.

[0037] In accordance with the described technology, the wearable glucose monitoring device 104 is configured to provide a measurement of glucose of the person 102. Although a wearable glucose monitoring device is discussed herein, it should be understood that glucose monitoring across phases may be used with other devices capable of providing glucose measurements, such as non-wearable glucose devices (such as blood glucose meters requiring a finger prick), patches, and the like. Additionally or alternatively, the multi-phase monitoring program may be used in conjunction with devices capable of generating measurements or making determinations regarding characteristics of the person 102 in addition to and / or different from glucose, such as temperature, other analytes (e.g., lactate, sodium, insulin, etc.), blood oxygen, heart rate, and heart rate variability, to name a few. However, in implementations that include a wearable glucose monitoring device 104, the wearable glucose monitoring device may be configured with a glucose sensor that detects analytes indicative of glucose of the person 102 to enable the generation of a glucose measurement, as described above and below.

[0038] In one or more embodiments, the wearable glucose monitoring device 104 is a continuous glucose monitoring ("CGM") system. As used herein, the term "continuous" used in connection with glucose monitoring may refer to the ability of a device to generate measurements substantially continuously, and thus the device may be configured to generate glucose measurements at regular or irregular time intervals (e.g., about every hour, about every 30 minutes, about every 5 minutes, etc.), such as upon establishing a communication coupling with a different device (e.g., when the computing device 106 establishes a wireless connection with the wearable glucose monitoring device 104 to retrieve one or more of the measurements). This functionality, along with further aspects of the configuration of the wearable glucose monitoring device 104, are described in more detail in connection with FIG. 2.

[0039] Additionally, the wearable glucose monitoring device 104 transmits glucose measurements to the computing device 106, such as via a wireless connection. The wearable glucose monitoring device 104 can communicate the measurements in real time, for example, as the measurements are generated using a glucose sensor. Alternatively or additionally, the wearable glucose monitoring device 104 can communicate the glucose measurements to the computing device 106 at set time intervals. For example, the wearable glucose monitoring device 104 can be configured to communicate glucose measurements to the computing device 106 (as the measurements are generated) approximately every 5 minutes. Certainly, the time intervals at which the glucose measurements are communicated may vary from the above example without departing from the spirit or scope of the described technology. The measurements may be communicated by the wearable glucose monitoring device 104 to the computing device 106 according to other bases in accordance with the described techniques, such as upon request from the computing device 106. In any event, the computing device 106 can maintain the glucose measurements of the person 102 at least temporarily, for example, in a computer-readable storage medium of the computing device 106.

[0040] The computing device 106 may be configured in a variety of ways without departing from the spirit or scope of the described technology. By way of non-limiting example, the computing device 106 may be configured as a mobile device (e.g., a mobile phone, a wearable device, or a tablet device), a desktop computer, or a laptop computer, to name a few form factors. In one or more implementations, the computing device 106 may be configured as a dedicated device associated with a glucose monitoring platform (not shown). The dedicated device associated with the glucose monitoring platform may be configured with functionality to obtain glucose measurements from the wearable glucose monitoring device 104, perform various calculations related to the glucose measurements, display information related to the glucose measurements and the glucose monitoring platform, communicate the glucose measurements to the glucose monitoring platform, etc.

[0041] Furthermore, computing device 106 can represent two or more devices in accordance with the described techniques. In one or more scenarios, for example, computing device 106 can correspond to both a wearable device (e.g., a smart watch) and a mobile phone. In such a scenario, both of these devices may be capable of performing at least some of the same operations, such as to receive glucose measurements from wearable glucose monitoring device 104, communicate those measurements over a network to a glucose monitoring platform, display information related to the glucose measurements, etc. Alternatively or in addition, different devices may have different capabilities that other devices do not have or that are limited to the devices specified through computing instructions.

[0042] In a scenario in which the computing device 106 corresponds to a separate smartwatch and a mobile phone, for example, the smartwatch may be configured with various sensors and capabilities for measuring various physiological markers (e.g., heart rate, heart rate variability, respiration, blood flow velocity, etc.) and activities (e.g., walking or other movement) of the person 102. In this scenario, the mobile phone may not be configured with these sensors and capabilities or may include a limited amount of the capabilities - although in other scenarios, the mobile phone may be capable of providing the same functionality. Continuing with this particular scenario, the mobile phone may have capabilities that the smartwatch does not have, such as a camera for capturing images associated with glucose monitoring, and an amount of computing resources (e.g., battery and processing speed) that allows the mobile phone to more efficiently perform calculations related to glucose measurements. Even in scenarios in which the smartwatch is capable of performing such calculations, the computing instructions may limit the execution of those calculations to the mobile phone to efficiently utilize available resources without burdening both devices. To this extent, the computing device 106 may be configured in a different manner and represent a different number of devices than described herein without departing from the spirit and scope of the described technology.

[0043] In accordance with the described technique, the multi-phase engine 108 is configured to acquire glucose data (e.g., glucose measurements) across multiple phases of a monitoring program, e.g., multiple phases of a glucose monitoring program. The illustrated environment 100 shows a first phase 110, a second phase 112, and a third phase 114 of a glucose monitoring program. It should be understood that a multi-phase monitoring program may have fewer phases (e.g., two) or more phases (e.g., four or more) without departing from the spirit or scope of the described technique. Indeed, the ellipsis depicted below the third phase 114 in the illustrated environment 100 indicates that such a program may include more phases. The illustrated environment 100 also includes arrows to the left of the depicted phases, indicating the progression of time from top to bottom. Thus, in this example, the first phase 110 precedes in time the second phase 112, which in turn precedes in time the third phase 114. Thus, a second phase 112 follows the first phase 110 and a third phase 114 follows the first and second phases 110,112.

[0044] In environment 100, multi-phase engine 108 acquires first glucose data 116 during a first phase 110, acquires second glucose data 118 during a second phase 112, and acquires third glucose data 120 during a third phase 114, where each different phase corresponds to a different wearable glucose monitoring device 104, e.g., during first phase 110, first glucose data 116 is acquired from wearable glucose monitoring device 104(a), during second phase 112, second glucose data 118 is acquired from wearable glucose monitoring device 104(b), and during third phase 114, third glucose data 120 is acquired from wearable glucose monitoring device 104(c). It should be understood that while different phases of the environment 100 each correspond to the wearing and use of a different wearable glucose monitoring device 104, a user may proceed into different phases of a multi-phase monitoring program based on the occurrence of different events or the satisfaction of different conditions, as described in more detail below.

[0045] In addition to acquiring glucose data, the multi-phase engine 108 is configured to control the display of information related to the acquired glucose data during the multi-phase glucose monitoring program. In particular, the multi-phase engine 108 controls the display of information such that different information is displayed during and after each phase of the program. In one or more implementations, for example, the multi-phase engine 108 controls the display of information based on rules that define what information, if any, is displayed during and after each phase. In the context of the illustrated environment 100, the multi-phase engine 108 controls what information associated with the first, second, and third glucose data 116, 118, 120, respectively, is displayed during and between the first, second, and third phases 110, 112, 114 of the multi-phase monitoring program.

[0046] As part of determining what information is displayed during different phases, the multi-phase engine 108 may be configured to determine the end of a phase. For example, the multi-phase engine 108 may be configured in various ways to detect a completion event indicating the end of a phase. In connection with the first phase 110, for example, the multi-phase engine 108 may detect a completion event indicating the completion of the first phase 110. Examples of completion events that may be detected by the multi-phase engine 108 include detecting the removal of a glucose sensor for each of the phase endings, detecting the insertion of a glucose sensor for the phase following the phase endings, detecting the expiration of a glucose monitoring period associated with the phase endings, and detecting a user input to end the ending phase and / or start the next phase, to name a few.

[0047] In the illustrated environment 100, the multi-phase engine 108 is configured to display information regarding the acquired glucose data via a user interface 122 displayed on a display device of the computing device 106. By way of example, the user interface 122 may correspond to an application downloaded to the computing device, such as an application associated with a multi-phase glucose monitoring program provided by a glucose monitoring platform. Alternatively or additionally, the user interface 122 may correspond to a different application, such as a browser application or a third party application. In any case, the multi-phase engine 108 is configured to display different information via the user interface 122 for each of the different phases.

[0048] In the first phase 110, for example, the multi-phase engine 108 may prevent the display of the first glucose data 116 acquired during the first phase 110 via the user interface 122, and the glucose data is not displayed via the user interface 122 in the illustrated first phase 110. One reason for preventing the display of the first glucose data 116 may be to encourage the person 102 to "act normal" during the first phase 110, such that the person 102 behaves as if he or she were not wearing the wearable glucose monitoring device 104(a). In this manner, the first glucose data 116 may provide a baseline against which data from subsequent phases may be compared to derive various insights into the behavior of the person 102.

[0049] In contrast, the multi-phase engine 108 may display at least a portion of the second glucose data 118 acquired during the second phase 112, e.g., the person's 102's current glucose level 124, via the user interface 122. In this example, the person's 102's current glucose level 124 may correspond to information that the multi-phase engine 108 prevented from being displayed during the first phase 110. Alternatively or additionally, the multi-phase engine 108 may display limited insights and / or limited recommendations derived from the second glucose data 118 via the user interface 122. It should be appreciated that the information displayed in each phase may vary depending on the design (e.g., rules) of a given multi-phase monitoring program. However, in general, the multi-phase engine 108 gradually reveals different information (e.g., more information and / or more detailed information) in subsequent phases of the program.

[0050] In the illustrated third phase 114, the multi-phase engine 108 causes different information to be displayed via the user interface 122, e.g., more information than was displayed in the second phase 112. Here, the user interface 122 is shown in the third phase 114, including a current glucose level 124, a trend indicator 126, and a glucose trace 128. In particular, the multi-phase engine 108 prevented the trend indicator 126 and the glucose trace 128 from being presented in the first and second phases 110, 112, and then revealed that information in the third phase 114. Certainly, the multi-phase engine 108 may gradually reveal different information and varying amounts of information in each subsequent phase in a variety of ways without departing from the spirit or scope of the described techniques. Consider the following description of FIG. 2 in the context of measuring glucose, e.g., continuously, to obtain glucose data describing such measurements.

[0051] 2 illustrates a more detailed example 200 of an implementation of the wearable glucose monitoring device 104 of FIG. 1. In particular, the illustrated example 200 includes a top view and a corresponding side view of the wearable glucose monitoring device 104. It should be understood from the following description that the wearable glucose monitoring device 104 may be modified in various ways in implementations without departing from the spirit or scope of the described techniques. As discussed above, for example, glucose monitoring over phases can be used in conjunction with other types of devices for glucose monitoring, such as non-wearable devices (e.g., blood glucose meters requiring finger pricks), patches, etc.

[0052] In this example 200, the wearable glucose monitoring device 104 is illustrated to include a glucose sensor 202 and a sensor module 204. Here, the glucose sensor 202 is shown in a side view inserted, for example, subcutaneously into the skin 206 of the person 102. The sensor module 204 is illustrated as a dashed rectangle in a top view. The wearable glucose monitoring device 104 also includes a transmitter 208 in the illustrated example 200. The use of a dashed rectangle for the sensor module 204 indicates that the sensor module may be housed or otherwise implemented within the housing of the transmitter 208. In this example 200, the wearable glucose monitoring device 104 further includes an adhesive pad 210 and an attachment mechanism 212. In one or more implementations, a user may utilize a different sensor 202 and sensor module 204 for each of the different phases of a monitoring program. However, in these examples, the same transmitter 208 may be used for each of the different phases. Alternatively, a single sensor 202 may be utilized for multiple phases without the need to remove and insert a new sensor for each phase. In one or more implementations, the wearable glucose monitoring device 104 may be part of a sensor kit that includes a transmitter 208 and multiple different sensors 202 for each of the different phases. For example, the sensor kit may include one transmitter 208 and four different sensors 202 for each of the four phases of a glucose monitoring program.

[0053] In operation, the glucose sensor 202, adhesive pad 210, and attachment mechanism 212 may be assembled to form an application assembly configured to be applied to the skin 206 such that the sensor 202 is inserted subcutaneously as depicted. In such a scenario, the transmitter 208 may be attached to the assembly after application to the skin 206 via the attachment mechanism 212. Alternatively, the transmitter 208 may be incorporated as part of the application assembly such that the glucose sensor 202, adhesive pad 210, attachment mechanism 212, and transmitter 208 (with sensor module 204) can be applied to the skin 206 all at once. In one or more implementations, this application assembly is applied to the skin 206 using a separate sensor applicator (not shown). Unlike the finger prick required by conventional blood glucose meters, user-initiated application of the wearable glucose monitoring device 104 is substantially painless and does not require the drawing of blood. Additionally, the automatic sensor applicator generally allows the person 102 to implant the glucose sensor 202 subcutaneously in the skin 206 without the assistance of a clinician or healthcare provider.

[0054] The application assembly can also be removed by peeling the adhesive pad 210 from the skin 206. It should be understood that the wearable glucose monitoring device 104 and its various components as illustrated are simply one example form factor, and that the wearable glucose monitoring device 104 and its components can have different form factors without departing from the spirit or scope of the presently described techniques.

[0055] In operation, the glucose sensor 202 is communicatively coupled to the sensor module 204 via at least one communication channel, which may be a wireless or wired connection. Communication from the glucose sensor 202 to the sensor module 204 or from the sensor module 204 to the glucose sensor 202 may be performed actively or passively, and these communications may be continuous (e.g., analog) or discrete (e.g., digital).

[0056] The glucose sensor 202 may be a device, molecule, and / or chemical that changes or causes a change in response to an event that is at least partially independent of the glucose sensor 202. The sensor module 204 is implemented to receive an indication of a change to or caused by the glucose sensor 202. For example, the glucose sensor 202 may include glucose oxidase that reacts with glucose and oxygen to form hydrogen peroxide that is electrochemically detectable by the sensor module 204, which may include electrodes. In this example, the glucose sensor 202 may be configured as or include a glucose sensor configured to detect analytes in blood or interstitial fluid indicative of glucose levels using one or more measurement techniques. In one or more embodiments, the glucose sensor 202 may also be configured to detect analytes in blood or interstitial fluid indicative of other markers, such as lactate levels, which may improve accuracy in identifying or predicting glucose-based events. Additionally or alternatively, the wearable glucose monitoring device 104 may include additional sensors to the glucose sensor 202 for detecting those analytes indicative of other markers.

[0057] In another example, the glucose sensor 202 (or additional, not shown, sensors of the wearable glucose monitoring device 104) can include first and second conductors, and the sensor module 204 can electrically detect a change in electrical potential across the first and second conductors of the glucose sensor 202. In this example, the sensor module 204 and the glucose sensor 202 are configured as a thermocouple, such that the change in electrical potential corresponds to a change in temperature. In some examples, the sensor module 204 and the glucose sensor 202 are configured to detect a single analyte, e.g., glucose. In other examples, the sensor module 204 and the glucose sensor 202 are configured to detect multiple analytes, e.g., sodium, potassium, carbon dioxide, and glucose. Alternatively or additionally, the wearable glucose monitoring device 104 includes multiple sensors for detecting not only one or more analytes (e.g., sodium, potassium, carbon dioxide, glucose, and insulin), but also one or more environmental conditions (e.g., temperature). Thus, the sensor module 204 and glucose sensor 202 (and any additional sensors) may detect the presence of one or more analytes, the absence of one or more analytes, and / or a change in one or more environmental conditions.

[0058] In one or more implementations, the sensor module 204 can include a processor and memory (not shown). The sensor module 204 can utilize the processor to generate a glucose reading 214 based on communication with the glucose sensor 202 indicating the above-mentioned changes. Based on the above-mentioned communication from the glucose sensor 202, the sensor module 204 is further configured to generate a communicable data package including at least one glucose reading 214. In this example 200, glucose data 216 represents these data packages. In one or more implementations, the first glucose data 116, the second glucose data 118, and the third glucose data 120 can include one or more such packets of glucose data 216. Additionally or alternatively, the sensor module 204 can configure the glucose data 216 to include additional data, including, by way of example, supplemental sensor information 218. The supplemental sensor information 218 can include a sensor identifier, a sensor status, a temperature corresponding to the glucose reading 214, measurements of other analytes corresponding to the glucose reading 214, etc. It should be appreciated that the supplemental sensor information 218 can include a variety of data that supplements the at least one glucose measurement 214 without departing from the spirit or scope of the described techniques.

[0059] In implementations in which the wearable glucose monitoring device 104 is configured for wireless transmission, the transmitter 208 can transmit the glucose data 216 as a data stream to the computing device. Alternatively or additionally, the sensor module 204 can buffer the glucose measurements 214 and / or the supplemental sensor information 218 (e.g., in a memory of the sensor module 204 and / or in another physical computer-readable storage medium of the wearable glucose monitoring device 104) and later cause the transmitter 208 to transmit the buffered glucose data 216 at various regular or irregular intervals, such as time intervals (about every second, about every 30 seconds, about every minute, about every 5 minutes, about every hour, etc.), storage intervals (when the buffered glucose measurements 214 and / or supplemental sensor information 218 reach a threshold amount of data or number of measurements), etc.

[0060] Having considered example environments and example wearable glucose monitoring devices, we now turn to a description of some example details of techniques for phased glucose monitoring and phased information display, according to one or more embodiments.

[0061] Phased glucose monitoring and phased information display 3 illustrates an example system 300 for acquiring glucose data for a person during a multi-phase glucose monitoring program and displaying different respective information during different phases. The illustrated example 300 includes the multi-phase engine 108 from FIG.

[0062] In example 300, multi-phase engine 108 includes a phase determination module 302 and a user interface configuration module 304. The illustrated system also includes a display module 306. In implementations, the system of example 300 may include more, fewer, or different components that implement a multi-phase monitoring program (e.g., a multi-phase glucose monitoring program) without departing from the spirit or scope of the described techniques. As described above, multi-phase engine 108 is configured to acquire glucose data during a multi-phase glucose monitoring program and to control the display of information about the acquired glucose data during different phases of the program.

[0063] Here, the multi-phase engine 108 is shown obtaining glucose data 308. By way of example, the glucose data 308 may correspond to the first glucose data 116 (e.g., during the first phase 110), the second glucose data 118 (e.g., during the second phase 112), the third glucose data 120 (e.g., during the third phase 114), or other glucose data for the respective phases.

[0064] The multi-phase engine 108 is also shown to obtain a multi-phase monitoring program 310 and phase-related data 312. In general, the multi-phase monitoring program 310 describes aspects of the program that the multi-phase engine 108 uses to determine what, if any, information is related to the glucose data 308 and to output the determined information to a user (e.g., participating in the program), provide it to a glucose monitoring platform (e.g., a service provider), and / or provide it to other entities observing the results of the program (e.g., a doctor or other healthcare provider, a spouse, a parent, or a child). The multi-phase monitoring program 310 may also describe how a user participating in the program may move from one phase to the next, e.g., how a user may move from a first phase 110 to a second phase 112.

[0065] In the example 300, the next phase criteria 314 correspond to data describing how a user in the multi-phase monitoring program 310 transitions from one phase to the next. It should be understood that the user may transition to a subsequent phase based on various criteria, such as the occurrence or non-occurrence of one or more events, without departing from the spirit or scope of the described techniques. In one example, for example, a phase may be defined based on a glucose sensor worn by the person 102, such that when the person 102 changes from wearing a first sensor (e.g., included in the wearable glucose monitoring device 104(a)) to wearing a second sensor (e.g., included in the wearable glucose monitoring device 104(b)), the next phase criteria 314 describes that a next phase (e.g., second phase 112) of the multi-phase monitoring program 310 begins. In other words, there is a one-to-one correspondence between the multi-phase monitoring programs and the glucose sensors worn (e.g., applied to the skin of the person 102) during the phases.

[0066] Certainly, transitions to subsequent phases may be based on criteria different from transitions to wearing a different sensor. Rather than corresponding to a respective sensor, for example, transitions to a new phase may be based on the behavior of the user wearing one or more sensors. In these examples, a single sensor may be usable for multiple phases, for example, for each of multiple phases of a monitoring program. By way of example, a transition may correspond to the user performing one or more actions, for example, performing an action a threshold number of times, or according to a prescribed pattern (particular frequency or sequence). In one scenario, for example, the next phase criteria 314 may define that the user transitions to the next phase of the multi-phase monitoring program 310 after performing an action a number of times. Examples of such actions may include capturing and uploading (with the computing device 106) a photo of a meal consumed by the user, accessing a computing application (or user interface) associated with the multi-phase monitoring program 310, and providing inputs via the user interface describing various aspects of the user's behavior or observations during the day (e.g., describing exercise, sleep, or stress), in other words, logging the user's behavior and observations. Additional examples of such behaviors may include falling asleep by a particular time (days consecutively or over the course of a phase), sleeping for a threshold number of hours, a threshold number of days (consecutively or over the course of a phase), walking a particular number of steps per day, etc. Certainly, the next phase criteria 314 may define different ways to transition to a subsequent phase (e.g., "unlock" a subsequent phase), including combinations of behaviors (e.g., logging a behavior and walking some steps) without departing from the spirit or scope of the described techniques.

[0067] In general, the phase-related data 312 describes these behaviors, so that the described behaviors can be compared to criteria to determine whether the user transitions to a subsequent phase of the multi-phase monitoring program 310. In accordance with the above-mentioned exemplary behaviors that may cause transitions, for example, the phase-related data 312 may correspond to photos (e.g., of the user's meals) captured and uploaded by the user, application data describing the number of times the user accessed a computing application (or user interface) associated with the multi-phase monitoring program 310, and / or stored data describing various aspects of the user's behavior or condition observations during the day (based on user inputs to enter such information). Alternatively or additionally, the phase-related data 312 may correspond to tracking data describing the user's sleep and / or movement, such as data collected from one or more devices (e.g., a smart watch). Indeed, the phase-related data 312 may originate from various sources and may describe various aspects of the user or environmental conditions associated with transitions between phases of the multi-phase monitoring program 310.

[0068] In this example 300, the multi-phase engine 108 includes a phase determination module 302 configured to determine a phase 316 (e.g., a current phase) of the multi-phase monitoring program 310. The phase determination module 302 may determine the phase 316 by comparing the phase-related data 312 to the next phase criteria 314. If the phase determination module 302 determines that the phase-related data 312 satisfies the next phase criteria 314, the phase determination module 302 determines that the phase 316 transitions to the next phase. On the other hand, if the phase determination module 302 determines that the phase-related data 312 does not satisfy the next phase criteria 314, the phase determination module 302 determines that the phase 316 remains in the same phase.

[0069] The multi-phase engine 108 also includes a user interface configuration module 304. According to the described techniques, the user interface configuration module 304 is configured to control the output of information to a user participating in the multi-phase monitoring program 310 and to control the output of information to any other entity observing the multi-phase monitoring program 310 (e.g., communication to a healthcare provider or glucose monitoring platform). In one or more implementations, for example, the user interface configuration module 304 is configured to control the information output to a user participating in the multi-phase monitoring program 310 by configuring the user interface 122 to include the information and / or by preventing the user interface 122 from including the information. According to the described techniques, for example, the user interface configuration module 304 may prevent the user interface 122 from including the first glucose data 116 during the first phase 110.

[0070] In one or more implementations, the user interface configuration module 304 uses phase-based display rules 318 to determine what information to display in each phase of the multi-phase monitoring program 310. Although shown separate from the multi-phase monitoring program 310, the phase-based display rules 318 may be included as part of or otherwise associated with the multi-phase monitoring program 310. Here, the phase-based display rules 318 are shown as having a first phase rule 320, a second phase rule 322, and an Nth phase rule 324.

[0071] The first phase rules 320 specify what information, if any, about the glucose data 308 is displayed during a first phase of the multi-phase monitoring program, e.g., first phase 110. For example, the first phase rules 320 specify information that is permitted to be displayed during the first phase and may also specify information that is not permitted to be displayed during the first phase. The user interface configuration module 304 prevents the display of information that the first phase rules 320 specify as not permitted to be displayed during the first phase. In the context of the first phase 110, for example, the first phase rules 320 may specify that glucose data is not displayed during the first phase 110. Based on such rules, the user interface configuration module 304 prevents the display of the first glucose data 116 during the first phase 110, e.g., via the user interface 122. In this manner, the user interface configuration module 304 may filter the incoming data during the first phase of the program to selectively display various amounts of data coming into the system, such as various amounts (from zero to substantially greater than zero) of glucose data 308, phase-related data 312, and insights and / or recommendations that may be derived from that data.

[0072] Similarly, the second phase rules 322 specify what information, if any, about the glucose data 308 is displayed during a second phase of the multi-phase monitoring program, e.g., the second phase 112. For example, the second phase rules 322 may specify information that is permitted to be displayed during the second phase and may also specify information that is not permitted to be displayed during the second phase. The user interface configuration module 304 prevents the display of information that the second phase rules 322 specify as not permitted to be displayed during the second phase. In the context of the second phase 112, for example, the second phase rules 322 may specify that glucose data is permitted to be displayed during the second phase 112, but recommendations and / or insights are not displayed. Based on such rules, the user interface configuration module 304 causes the second glucose data 118 to be displayed during the second phase 112 and prevents the display of recommendations and / or insights, e.g., via the user interface 122. In this manner, the user interface configuration module 304 may filter the incoming data during the second phase of the program to selectively display various amounts of data incoming to the system, such as various amounts (from zero to substantially greater than zero) of glucose data 308, phase-related data 312, and insights and / or recommendations that may be derived from that data.

[0073] It should be understood that according to the described technique, a "multi-phase monitoring program" may have only two phases and therefore only two sets of phase rules. If a multi-phase monitoring program has, for example, only two phases, the phase-based display rules 318 may include only a first phase rule 320 and a second phase rule 322. In this scenario, the phase-based display rules 318 may not include an Nth phase rule 324, e.g., a third phase rule. However, if a multi-phase monitoring program includes more than two phases, the phase-based display rules 318 may include a respective rule set for each phase. For example, if a multi-phase monitoring program includes three phases, the phase-based display rules 318 may include three rule sets, e.g., a first phase rule 320, a second phase rule 322, and an Nth phase rule 324. If the multi-phase monitoring program includes four phases, the phase-based display rules 318 may include four rule sets, for example, a first phase rule 320, a second phase rule 322, a third phase rule, and an Nth phase rule 324. In the illustrated example, the Nth phase rule 324 is shown with dashed lines to indicate that it is optional. In other words, one or more implementations may not include or otherwise use the Nth phase rule 324, for example, when the multi-phase monitoring program 310 includes only two phases. The phase-based display rules 318 also include an ellipsis between the second phase rule 322 and the Nth phase rule 324 to indicate that there may not be an additional rule set between the second phase rule 322 and the Nth phase rule 324, or that there may be one or more additional rule sets between the second phase rule 322 and the Nth phase rule 324. For example, in addition to the first phase rules 320 and the second phase rules 322, there may be zero or several additional rule sets depending on the number of phases in the multi-phase supervisor 310.

[0074] In general, the phase-based display rules 318 define what data is displayed during and between each phase of the multi-phase monitoring program 310, and the user interface configuration module 304 processes those rules along with incoming information (e.g., phases 316 and glucose data 308) during and between phases to determine which incoming information to incorporate as part of the user interface 122, which incoming information to prevent from being included as part of the user interface 122, and how to configure the graphical elements of the user interface 122 to display information that is allowed to be output.

[0075] In the illustrated example 300, the user interface configuration module 304 is shown outputting the user interface 122 to the display module 306, which is configured to cause the user interface 122 to be displayed via a display device 326, such as a display device of the computing device 106 or some other display device. It should be understood that the user interface 122 may be output from the display in different or additional ways. For example, the user interface configuration module 304 may configure and output the user interface for communication over a network, such as to a glucose monitoring platform, to a portal for a healthcare provider (telehealth), and / or for communication via email, to name a few. Alternatively or additionally, the user interface configuration module 304 may configure the user interface for audible output via a speaker, such as via a voice assistant device.

[0076] In this example, the user interface 122 includes glucose data 308 (which may correspond to glucose data for a respective phase, such as first glucose data 116 being the first glucose data during the first phase 110 being the first phase), insights 328, recommendations 330, and other graphical elements 332. Each of the glucose data 308, insights 328, recommendations 330, and other graphical elements 332 is shown with dashed lines. The dashed lines indicate that the glucose data 308, insights 328, recommendations 330, and other graphical elements 332 are optionally included as part of the user interface 122 during different phases of the multi-phase monitoring program 310. Their inclusion and exclusion from the user interface 122 depends on phase-based display rules 318 specified for the different phases and the user interface configuration module 304's processing of those rules to generate the user interface 122 during and between stages of the multi-phase monitoring program 310.

[0077] In general, the glucose data 308 may include or otherwise correspond to one or more glucose measurements generated by the wearable glucose monitoring device 104. For example, the glucose data 308 may be represented in the user interface 122 as one or more numerical values ​​(e.g., a number representing the person's 102's current glucose) or as a representation of those values ​​(e.g., an indicator plotted on a graph). The insights 328 include one or more statistics calculated using the glucose data 308 (and / or the phase-related data 312) and / or inferences or conclusions drawn based on one or more predictions generated based on the glucose data 308 (and / or the phase-related data 312).

[0078] Certainly, the user interface 122 may be configured by the user interface configuration module 304 to include any number of insights 328 associated with a given phase depending on the respective phase-based display rules 318. Examples of insights may include trends (e.g., a person's glucose is rising, falling, or staying the same over the last few measurements or over a certain amount of time; a person's blood pressure (or heart rate variability) is rising, falling, or staying the same over a certain amount of time), the amount of time in or out of a range of glucose values ​​over a previous time interval (e.g., "Time in Range"), the likelihood of some event occurring in the future (e.g., occurrence of a glycemic event and / or a given glucose level), the relative change of some value or metric over time (e.g., lower average glucose, increased Time in Range during the current phase compared to the previous one, etc.), a prediction of a value or metric (e.g., A1C), and the relative change in a person's characteristic (e.g., perception of increased or decreased stress, improved or worse sleep), to name a few.

[0079] The recommendations 330 include advice output for the person to improve the person's data, maintain observed "healthy" data, and / or otherwise suggest a course of action (e.g., contact a health care provider). Similar to the insights 328, the user interface 122 may be configured by the user interface configuration module 304 to include any number of recommendations 330 associated with a given phase depending on the respective phase-based display rules 318. Examples of recommendations may include suggestions regarding, for example, activity (e.g., engaging in one or more exercises for a few minutes per day or week, or walking a threshold number of steps per day), eating behavior (e.g., specifying types of foods to eat, specifying foods not to eat, specifying amounts of foods to eat, specifying when to eat, etc.), sleep behavior (e.g., lying in bed for at least a certain amount of time, or getting a threshold number of hours of sleep per night on average), device engagement behavior (e.g., operating an app a threshold number of times, recording one or more behaviors each a threshold number of times, reducing the amount of screen time, etc.), and medication behavior (e.g., taking one or more medications or supplements according to a schedule), to name a few.

[0080] In one or more implementations, the user interface configuration module 304 may include or otherwise have access to an analytical engine (not shown) configured to generate insights 328 and / or recommendations 330. In implementations where such an analytical engine is maintained by the glucose monitoring platform and configured as a web-based service provider, the platform may have access to significantly more computing resources than the computing device 106. These resources may include numerous servers and may include databases that store glucose data and health data for a population of users, e.g., thousands or millions of hours of user data. This vast amount of data allows patterns (e.g., correspondences) between glucose data and health data to be identified across a population of users. Additionally, this amount of data allows identifiable patterns in the data to be trusted and distinguished from anomalies that may appear as "normal" correspondences when the platform has access to only a small amount of data. These patterns may allow glucose data or health data to be predicted using observations (inputs) of the other.

[0081] Further, the glucose monitoring platform may include computing resources (e.g., storage and processing power) to deploy one or more machine learning models to "learn" those patterns (e.g., using one or more algorithms and history) and generate predictions that are used to generate insights 328 or recommendations 330. Alternatively or additionally, such glucose monitoring platforms may build (e.g., train) one or more machine learning models using data from the population and have the trained (or otherwise learned) machine learning models loaded onto a remote device, such as the computing device 106. As an example, the trained machine learning models may be downloaded from the platform by the computing device 106. The computing device 106 may then deploy the trained (or otherwise learned) machine learning models at the platform level locally at the computing device to process the data at the computing device 106. The multi-phase engine 108 may include or otherwise have access to various machine learning models that generate information used to configure the user interface 122 without departing from the spirit or scope of the described techniques.

[0082] As discussed above, the user interface 122 also includes other graphical elements 332. In general, the other graphical elements 332 include any of a variety of components that may be displayed as part of the user interface 122. Some examples of the other graphical elements 332 include messages in text, text headings, menus, icons, buttons, images, videos, and the like. However, these other graphical elements 332 are separate from the glucose data 308, insights 328, and recommendations 330, and thus, if the text of a message displayed via the user interface 122 includes glucose data 308, the message may not be considered one of the other graphical elements 332, but may instead be considered glucose data 308. Consider the following examples of user interfaces described in connection with FIGS. 4-9 in the context of information that may be included in user interfaces in different phases, and information that may be prevented from being included in those user interfaces in different phases.

[0083] FIG. 4 illustrates an example implementation 400 of a user interface in which output of glucose data obtained during phases of a multi-phase glucose monitoring program is prevented.

[0084] The illustrated example 400 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is depicted presenting only other graphical elements 332, namely, a label 402 (e.g., “Glucose Monitoring Program”) and a message 404 (e.g., “Preventing Output of Glucose Data Until Phase 2”). Glucose data 308 is not included as part of the user interface 122. Rather, the user interface configuration module 304 prevents output of the glucose data 308 via the user interface 122. The user interface configuration module 304 may configure the user interface 122 in this manner, for example, during a first phase of a multi-phase monitoring program, such as during the first phase 110 of the multi-phase glucose monitoring program of FIG. 1. Thus, in the context of FIG. 1, the user interface configuration module 304 prevents output of the first glucose data 116 during the first phase 110 by configuring the user interface 122 without the first glucose data 116 during the first phase 110.

[0085] In one or more implementations, the user interface configuration module 304 may also prevent output of the first glucose data 116 during or during a transition period between the first phase 110 and the second phase 112, for example, by configuring the user interface 122 without the first glucose data 116 during such period. In the illustrated example 400, the user interface 122 also does not include any of the insights 328 or recommendations 330. Thus, the user interface configuration module 304 may prevent the display of the insights 328 and / or recommendations 330 during the first phase 110 by not including them as part of the user interface 122. Consider the following description of FIG. 5 in the context of an example user interface that may be displayed during the first phase 110 and the second phase 112.

[0086] FIG. 5 shows an example implementation 500 of a user interface that displays instructions for transitioning to a subsequent phase of a multi-phase glucose monitoring program.

[0087] The illustrated example 500 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is again depicted presenting only other graphical elements 332, namely, a label 502 (e.g., "Glucose Monitoring Program"), a first message 504 (e.g., "Phase 1 Complete!"), and a second message 506 (e.g., "Remove the active sensor and insert a new sensor to proceed to Phase 2"). In this example 500, the second message 506 includes, at least in part, instructions instructing the user on how to transition to a subsequent phase of the multi-phase glucose monitoring program. Thus, the user interface configuration module 304 may continue to prevent output of one or more of the glucose data 308, insights 328, and recommendations 330 between the first phase 110 and the second phase 112. However, it should be understood that in different implementations, the user interface 122 may be configured to display different and / or additional information when transitioning between the first phase 110 and the second phase 112.

[0088] As an example, the user interface configuration module 304 may configure the user interface 122 to include a button (e.g., other graphical elements 332) that is selectable to display a report for the first phase 110 of the person's 102 program, which may include one or more of the first glucose data 116, insights 328 derived based on the first glucose data 116, and / or recommendations 330 derived based on the first glucose data 116 and / or based on the insights 328. In such an implementation, the user interface configuration module 304 may therefore not prevent the glucose data 308 (or insights 328 and recommendations 330) from being displayed after the first phase 110 and before the second phase 112, which is the first phase. Whether the user interface configuration module 304 prevents the glucose data 308 from being displayed between (or during) phases may depend on the phase-based display rules 318. Consider the following example in the context of a user interface that may be displayed during phases subsequent to the first phase 110 of a multi-phase glucose monitoring program.

[0089] FIG. 6 illustrates an example implementation 600 of a user interface that displays glucose data obtained during subsequent phases of a multi-phase glucose monitoring program.

[0090] The illustrated example 600 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is shown including glucose data 308 and other graphical elements 332. In particular, the glucose data 308 displayed via the user interface 122 includes a current glucose 602, and the other graphical elements 332 displayed via the user interface 122 include a unit indicator 604 (e.g., "Mg / dL") and a value label 606, which indicates that the displayed value is the person's current glucose, rather than corresponding to some other measurement, e.g., heart rate. In one or more implementations, the current glucose 602 is displayed by the user interface 122 in real time, e.g., as the glucose data 308 is received from the wearable glucose monitoring device 104. In this manner, the current glucose 602 may correspond to a most recently received glucose measurement, i.e., a glucose measurement most recently generated by the wearable glucose monitoring device 104 and communicated from the wearable glucose monitoring device 104 to the computing device 106, e.g., via a wireless connection.

[0091] A user interface with this information, or similar information, may be displayed during the second phase 112 of the multi-phase glucose monitoring program of Figure 1. By configuring the user interface 122 during the first phase 110 substantially as shown in Figure 4 (e.g., by preventing the output of glucose data 308), and then configuring the user interface 122 during the second phase 112 substantially as shown in this example 600 (e.g., by including glucose data 308), the user interface configuration module 304 may gradually reveal information obtained and determined during the multi-phase program.

[0092] By gradually revealing information to the person 102 being monitored, rather than presenting the information from the beginning of the program, the multi-phase engine 108 may learn how the person 102 behaves "normally" because information that "scares" the person and causes the person to behave differently than normal is not output. The multi-phase engine 108 may also more effectively educate the person 102 as to what the information output via the user interface 122 means, because the person 102 is only shown a certain amount of new information in each phase, so that the person has time to learn about the information before additional and / or more detailed information is output in a subsequent phase. In other words, by gradually revealing information, the multi-phase engine 108 helps the person 102 build up their knowledge over time. The multi-phase engine 108 may output or provide access to information between phases that differs from during the phases, such as aggregated information. In this context, consider the following description of FIG. 7.

[0093] FIG. 7 shows an example implementation 700 of a user interface that displays user interface elements that can be selected to view more detailed information about one or more phases of a multi-phase glucose monitoring program.

[0094] The illustrated example 700 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is depicted presenting other graphical elements 332, including a label 702 (e.g., "Glucose Monitoring Program"), a first message 704 (e.g., "Phase X Completed!"), and a second message 706 (e.g., "You Can Review Your Glucose Report"). In this example 700, the other graphical elements 332 also include a review button 708, selectable by a user of the computing device 106 to obtain a glucose report of the person 102 (e.g., over phase X). Thus, the report that may be presented in response to selection of the review button 708 may display the glucose data 308. This is in contrast to the exemplary user interface of FIG. 5, which did not include functionality for accessing the glucose data 308. Similar to the user interfaces output during a phase, the user interfaces output after a phase (or during a transition to a subsequent phase) may also gradually reveal information.

[0095] In this example 700, the "glucose report" may correspond to or otherwise include glucose data 308 from at least the most recently completed phase (e.g., phase X). Additionally or alternatively, the "glucose report" may correspond to or otherwise include glucose data 308 from one or more phases preceding the most recently completed phase. In a scenario in which "phase X" corresponds to the second phase 112, for example, the glucose report presented upon selection of the review button 708 may include at least a portion of the second glucose data 118, or may include at least a portion of the first glucose data 116 and the second glucose data 118. In one or more implementations, a glucose report may be generated based on the first glucose data 116 collected during a first phase 110 of the glucose monitoring program, the second glucose data 118 collected during a second phase 112 of the glucose monitoring program, the third glucose data 120 collected during a third phase 114 of the glucose monitoring program, and the fourth glucose data collected during a fourth phase of the glucose monitoring program. Notably, therefore, even though glucose data collected during various phases may not be output during such phases (e.g., the first glucose data 116 may be prevented from being output during the first phase 110), this data may still be available and output at a later time, e.g., via a glucose report. Information included in such a report may be based in part on information displayed during a completed phase. For example, in a scenario where current glucose was displayed during a most recently completed phase, the multi-phase engine 108 may generate a report to include only the person's measured glucose over the course of the most recently completed phase (and / or any preceding phases). Indeed, the information displayed after completion of a phase of a multi-phase monitoring program may vary within the spirit and scope of the described techniques.

[0096] FIG. 8 illustrates an example implementation 800 of a user interface that displays glucose data obtained during subsequent phases of a multi-phase glucose monitoring program and that displays additional information related to the glucose data.

[0097] The illustrated example 800 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is shown including glucose data 308, recommendations 330, and other graphical elements 332. In particular, the glucose data 308 displayed via the user interface 122 includes a current glucose 802. In one or more implementations, the current glucose 802 is displayed by the user interface 122 in real time, for example, as the glucose data 308 is received from the wearable glucose monitoring device 104. In this manner, the current glucose 802 may correspond to a most recently received glucose measurement, i.e., a glucose measurement most recently generated by the wearable glucose monitoring device 104 and communicated from the wearable glucose monitoring device 104 to the computing device 106, for example, via a wireless connection.

[0098] 6, other graphical elements 332 displayed via user interface 122 may include a units indicator 804 (e.g., "Mg / dL") and a value label 806, which indicates that the displayed number is the person's current glucose rather than corresponding to some other measurement, e.g., heart rate. However, in contrast to FIG. 6, user interface 122 is shown displaying recommendations 330.

[0099] The user interface 122 may be configured to include additional information (e.g., recommendations 330 or insights 328) along with the glucose data 308 at one or more times (e.g., phases) after the time (e.g., phases) the glucose data 308 is initially displayed. Alternatively, one or more recommendations 330 and / or insights 328 may be displayed via the user interface 122 before the glucose data 308 is displayed. Thus, in some scenarios, the user interface 122 may be configured to include the glucose data 308 along with one or more recommendations 330 and / or insights 328 at one or more times (e.g., phases) after the time (e.g., phases) the recommendations 330 and / or insights 328 are initially displayed. The illustrated recommendation 330 is merely one example of a recommendation that may be presented to a person associated with a multi-phase monitoring program. Indeed, recommendations may be presented in a variety of manners during a multi-phase monitoring program in accordance with the techniques described.

[0100] FIG. 9 illustrates an example implementation 900 of a user interface that displays glucose data obtained during subsequent phases of a multi-phase glucose monitoring program and that displays additional information related to the glucose data.

[0101] The illustrated example 900 shows a computing device 106 displaying a user interface 122 via a display device 326. Here, the user interface 122 is shown including glucose data 308, insights 328, and other graphical elements 332. In particular, the glucose data 308 displayed via the user interface 122 includes a current glucose 902. As described above, the current glucose 902 may be displayed in real time by the user interface 122, for example, as the glucose data 308 is received from the wearable glucose monitoring device 104. In this manner, the current glucose 902 may correspond to a most recently received glucose measurement, i.e., a glucose measurement most recently generated by the wearable glucose monitoring device 104 and communicated from the wearable glucose monitoring device 104 to the computing device 106, for example, via a wireless connection.

[0102] In addition to the current glucose 902, the glucose data 308 displayed via the user interface 122 also includes a glucose trace 904 in this example 900. The insights 328 displayed in this example 900 are indications of trends, e.g., graphical elements showing glucose trends of the person 102 over time.

[0103] In the illustrated example 900, the trend indication surrounds the current glucose 902 and is generally circular with a triangular portion pointing in the direction of the trend, e.g., increasing glucose. If glucose is decreasing, the triangular portion of the trend indication may be generally pointing downward. Generally, if glucose is observed to be increasing more rapidly, the triangular portion will be pointing more upward, and if glucose is observed to be decreasing more rapidly, the triangular portion will be pointing more downward. In a scenario where glucose is substantially maintaining a level, the trend indicator may be substantially pointing horizontally. Certainly, the user interface 122 may be configured to present different insights 328 than the glucose trend indicator without departing from the spirit or scope of the described techniques. Additionally, the glucose trend indicator may indicate glucose trends in a different manner than the depicted example.

[0104] In addition to the glucose data 308 (e.g., current glucose 902 and glucose trace 904), the user interface 122 also includes other graphical elements 332. In this example 900, the other graphical elements 332 include a notification button 906 and a menu 908 having various selectable options. The notification button 906 may be selectable by a user of the computing device 106 to present additional information from the illustrated example, such as alerts, further details regarding the displayed information, further insights 328, and recommendations 330 related to the displayed information, to name a few. In accordance with the described techniques, the user interface 122 shown in the illustrated example 900 generally includes more information than the user interfaces shown in FIGS. 4-8. This indicates that the user interface 122 shown in FIG. 9 corresponds to a later phase than that represented by the previous example. This further demonstrates that the user interface displayed in the subsequent phase may include additional information and / or more detailed information than presented in the preceding phase of the multi-phase monitoring program.

[0105] Having described exemplary details of a technique for data stream bridging for sensor migration, we will now consider some example procedures to illustrate additional aspects of the technique.

[0106] Exemplary Procedure This section describes example procedures for glucose monitoring across phases and corresponding phased information display. Aspects of the procedures may be implemented in hardware, firmware, software, or combinations thereof. The procedures are illustrated as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the order shown for performing the operations by each block. In at least some implementations, the procedures are performed by a multi-phase engine, such as multi-phase engine 108.

[0107] FIG. 10 illustrates a procedure 1000 in an exemplary implementation of a multi-phase glucose monitoring program.

[0108] A multi-phase glucose monitoring program including at least a first phase and a second phase is initiated (block 1002). By way of example, the multi-phase engine 108 initiates a multi-phase glucose monitoring program including at least a first phase 110 and a second phase 112.

[0109] First glucose data for the user is acquired during a first phase of the multi-phase glucose monitoring program (block 1004). By way of example, the multi-phase engine 108 acquires first glucose data 116 during a first phase 110 of the glucose monitoring program.

[0110] Output of the first glucose data in the glucose monitoring user interface is prevented during the first phase of the multi-phase glucose monitoring program (block 1006). As an example, in the first phase 110, the multi-phase engine 108 prevents output of the first glucose data 116 acquired during the first phase 110 via the user interface 122. In other words, during the first phase 110, the glucose data is not displayed via the user interface 122. One reason for preventing the display of the first glucose data 116 may be to encourage the user to "act normal" during the first phase 110, to behave as if the user were not wearing the wearable glucose monitoring device 104(a). In this way, the first glucose data 116 may provide a baseline against which data from subsequent phases may be compared to derive various insights about the user's behavior.

[0111] Second glucose data for the user is acquired during a second phase of the multi-phase glucose monitoring program (block 1008). By way of example, the multi-phase engine 108 acquires second glucose data 118 during a second phase 112 of the glucose monitoring program.

[0112] The second glucose data is output in real time at the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program (block 1010). By way of example, the multi-phase engine 108 may display at least a portion of the second glucose data 118 obtained during the second phase 112, e.g., the person's 102's current glucose level 124, via the user interface 122. In particular, the second glucose data (e.g., the user's current glucose level 124) displayed during the second phase may thus correspond to information that the multi-phase engine 108 prevented from being displayed during the first phase 110. Alternatively or additionally, the multi-phase engine 108 may display limited insights and / or limited recommendations derived from the second glucose data 118 via the user interface 122.

[0113] In particular, each different phase may correspond to a different wearable glucose monitoring device 104, e.g., during a first phase 110, first glucose data 116 is obtained from the wearable glucose monitoring device 104(a), and during a second phase 112, second glucose data 118 is obtained from the wearable glucose monitoring device 104(b). Although each different phase of the illustrated environment 100 corresponds to the wearing and use of a different wearable glucose monitoring device 104, it should be understood that a user may proceed into different phases of a multi-phase monitoring program based on the occurrence of different events or the satisfaction of different conditions, as described throughout.

[0114] FIG. 11 illustrates a procedure 1100 in an exemplary implementation in which a glucose report is generated based on glucose data obtained during first, second, third, and fourth phases of a multi-phase glucose monitoring program.

[0115] The user's first glucose data is acquired using the first glucose sensor during a first phase of the multi-phase glucose monitoring program (block 1102), the user's second glucose data is acquired using the second glucose sensor during a second phase of the multi-phase glucose monitoring program (block 1104), the user's third glucose data is acquired using the third glucose sensor during a third phase of the multi-phase glucose monitoring program (block 1106), and the user's fourth glucose data is acquired using the fourth glucose sensor during a fourth phase of the multi-phase glucose monitoring program (block 1108). By way of example, the multi-phase engine 108 acquires first glucose data 116 during a first phase 110 of the glucose monitoring program, acquires second glucose data 118 during a second phase 112 of the glucose monitoring program, acquires third glucose data 120 during a third phase 114 of the glucose monitoring program, and acquires fourth glucose data during a fourth phase of the glucose monitoring program.

[0116] A glucose report is generated based on the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data (block 1110). By way of example, the multi-phase engine 108 generates a glucose report based on the first glucose data 116 collected during the first phase 110 of the glucose monitoring program, the second glucose data 118 collected during the second phase 112 of the glucose monitoring program, the third glucose data 120 collected during the third phase 114 of the glucose monitoring program, and the fourth glucose data collected during the fourth phase of the glucose monitoring program. Notably, therefore, even though glucose data collected during various phases may not be output during said phases (e.g., the first glucose data 116 may be prevented from being output during the first phase 110), this data may still be available and output later, for example, via a glucose report.

[0117] Having described example procedures according to one or more embodiments, we now turn to example systems and devices that can be utilized to implement the various techniques described herein.

[0118] Exemplary Systems and Devices 12 illustrates, generally at 1200, an example system including an example computing device 1202 that represents one or more computing systems and / or devices capable of implementing various techniques described herein, as illustrated through the inclusion of a multi-phase engine 108. The computing device 1202 may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and / or any other suitable computing device or computing system.

[0119] The exemplary computing device 1202 as shown includes a processing system 1204, one or more computer-readable media 1206, and one or more I / O interfaces 1208 communicatively coupled to each other. Although not shown, the computing device 1202 may further include a system bus or other data and command transfer system coupling the various components together. The system bus may include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and / or a processor or local bus utilizing any of a variety of bus architectures. Various other examples, such as control and data lines, are also contemplated.

[0120] The processing system 1204 represents functionality for performing one or more operations using hardware. Thus, the processing system 1204 is illustrated as including hardware elements 1210, which may be configured as a processor, functional blocks, etc. This may include implementations in hardware as application specific integrated circuits or other logic devices formed using one or more semiconductors. The hardware elements 1210 are not limited by the materials from which they are formed, or the processing mechanisms employed therein. For example, a processor may be comprised of semiconductors and / or transistors (e.g., electronic integrated circuits (ICs)). In this context, processor-executable instructions may be electronically executable instructions.

[0121] The computer-readable medium 1206 is illustrated as including memory / storage 1212. The memory / storage 1212 represents memory / storage capacity associated with one or more computer-readable media. The memory / storage 1212 may include volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical disks, magnetic disks, etc.). The memory / storage 1212 may include fixed media (e.g., RAM, ROM, fixed hard drives, etc.) as well as removable media (e.g., flash memory, removable hard drives, optical disks, etc.). The computer-readable medium 1206 may be configured in a variety of other ways, as further described below.

[0122] Input / output interface 1208 represents functionality that allows a user to input commands and information into computing device 1202 and that allows information to be presented to a user and / or other components or devices using various input / output devices. Examples of input devices include keyboards, cursor control devices (e.g., a mouse), microphones, scanners, touch capabilities (e.g., capacitive or other sensors configured to detect physical contact), cameras (e.g., employing visible wavelengths or non-visible wavelengths such as infrared frequencies to recognize movements as non-touch gestures), and the like. Examples of output devices include display devices (e.g., a monitor or projector), speakers, printers, network cards, haptic response devices, and the like. Thus, computing device 1202 can be configured in a variety of ways to support user interaction, as described further below.

[0123] Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, etc. that perform particular tasks or implement particular abstract data types. As used herein, the terms "module," "function," and "component" generally refer to software, firmware, hardware, or combinations thereof. Aspects of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

[0124] An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. Computer-readable media may include a variety of media that may be accessed by computing device 1202. By way of example, and not limitation, computer-readable media may include "computer-readable storage media" and "computer-readable signal media."

[0125] A "computer-readable storage medium" may refer to a medium and / or device that allows for persistent and / or non-transient storage of information, as opposed to merely a signal transmission, carrier wave, or signal itself. Thus, a computer-readable storage medium refers to a non-signal-bearing medium. A computer-readable storage medium includes hardware, such as volatile and non-volatile, removable and non-removable media, and / or storage devices implemented in a manner or technology suitable for storage of information, such as computer-readable instructions, data structures, program modules, logic elements / circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, hard disk, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or other storage device, tangible media, or any article suitable for storing the desired information and that can be accessed by a computer.

[0126] A "computer-readable signal medium" may refer to a signal-bearing medium configured to transmit instructions to the hardware of the computing device 1202, such as via a network. Signal media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, data signal, or other transport mechanism. Signal media also includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media.

[0127] As previously described, the hardware elements 1210 and the computer-readable medium 1206 represent modules, programmable device logic, and / or fixed device logic implemented in hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein, such as to execute one or more instructions. The hardware may include integrated circuits or components of on-chip systems, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), and other implementations in silicon or other hardware. In this context, the hardware may operate as a processing device that executes program tasks defined by instructions and / or logic embodied by the hardware, as well as hardware utilized to store instructions for execution, such as the computer-readable storage medium previously described.

[0128] Combinations of the foregoing may be used to implement various techniques described herein. Thus, software, hardware, or executable modules may be implemented as one or more instructions and / or logic embodied on some form of computer-readable storage medium and / or by one or more hardware elements 1210. Computing device 1202 may be configured to implement specific instructions and / or functions corresponding to software and / or hardware modules. Thus, implementation aspects of modules executable as software by computing device 1202 may be achieved at least partially in hardware, for example, through the use of computer-readable storage medium and / or hardware elements 1210 of processing system 1204. The instructions and / or functions may be executable / operable by one or more articles of manufacture (e.g., one or more computing devices 1202 and / or processing system 1204) to implement the techniques, modules, and examples described herein.

[0129] The techniques described herein may be supported by various configurations of computing device 1202 and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented in whole or in part through the use of a distributed system, such as on a "cloud" 1214 via platform 1216, as described below.

[0130] Cloud 1214 includes and / or represents a platform 1216 for resources 1218. Platform 1216 abstracts the underlying functionality of the hardware (e.g., servers) and software resources of cloud 1214. Resources 1218 may include applications and / or data available while computer processing is running on a server remote from computing device 1202. Resources 1218 may also include services provided over the Internet and / or over a subscriber network, such as a cellular network or a Wi-Fi network.

[0131] The platform 1216 can abstract resources and functionality for connecting the computing device 1202 with other computing devices. The platform 1216 can also serve to abstract the scaling of resources to provide a level of scale corresponding to the demand faced by the resources 1218 implemented via the platform 1216. Thus, in an embodiment of interconnected devices, implementation aspects of the functionality described herein can be distributed throughout the system 1200. For example, functionality can be implemented partially on the computing device 1202 as well as via the platform 1216 that abstracts the functionality of the cloud 1214.

[0132] conclusion Although the systems and techniques have been described in language specific to structural features and / or methodological acts, it should be understood that the systems and techniques defined in the appended claims are not necessarily limited to the particular features or acts described. Rather, the particular features and acts are disclosed as exemplary forms for implementing the claimed subject matter. [Explanation of symbols]

[0133] 100 Environment 102 people 104 Wearable Glucose Monitoring Devices 106 Computing Devices 108 Multiphase Engine 110 First Phase 112 Second Phase 114 Third Phase 122 User Interface 124 Current Glucose Level 126 Trend Indicators 128 Glucose Trace 200 Examples 202 Glucose Sensor 204 Sensor Module 206 Skin 208 Transmitter 210 Adhesive Pad 212 Attachment mechanism 1202 Computing Devices 1204 Processing System 1206 Computer-readable medium 1208 I / O Interface 1210 Hardware Elements 1212 Memory / Storage 1214 Cloud 1216 Platform 1218 resources

Claims

1. 1. A computer-implemented method, comprising: initiating a multi-phase glucose monitoring program including at least a first phase and a second phase; acquiring first glucose data for a user during the first phase of the multi-phase glucose monitoring program; preventing output of the first glucose data in a glucose monitoring user interface during the first phase of the multi-phase glucose monitoring program; obtaining second glucose data for the user during the second phase of the multi-phase glucose monitoring program; outputting the second glucose data in real time at the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

2. 2. The computer-implemented method of claim 1, wherein the first glucose data is collected by a first glucose sensor worn by the user during the first phase of the multi-phase glucose monitoring program, and the second glucose data is collected by a second glucose sensor worn by the user during the second phase of the multi-phase glucose monitoring program.

3. 3. The computer-implemented method of claim 2, wherein each of the first glucose data and the second glucose data is obtained from a single transmitter communicatively coupled to a computing device that displays the glucose monitoring user interface.

4. 3. The computer-implemented method of claim 2, further comprising: detecting a completion event indicating completion of the first phase; and outputting information based on the first glucose data in the glucose monitoring user interface after detecting the completion of the first phase.

5. The completion event is detecting removal of the first glucose sensor worn by the user during the first phase; detecting insertion of the second glucose sensor relative to the second phase; detecting the expiration of a glucose monitoring period associated with the first phase of the multi-phase glucose monitoring program; or 5. The computer-implemented method of claim 4, further comprising one of: detecting a user input via the glucose monitoring user interface to end the first phase or to start the second phase.

6. The computer-implemented method of claim 1 , wherein the first glucose data and the second glucose data are collected by a single glucose sensor.

7. 1. A system comprising: a sensor kit for a multi-phase glucose monitoring program, the sensor kit including at least a first glucose sensor for monitoring glucose during a first phase of the multi-phase glucose monitoring program, and a second glucose sensor for monitoring glucose during a second phase of the multi-phase glucose monitoring program; A multi-phase engine, controlling a glucose monitoring user interface during said multi-phase glucose monitoring program; obtaining first glucose data for a user during the first phase of the multi-phase glucose monitoring program from the first glucose sensor of the sensor kit; preventing output of the first glucose data in the glucose monitoring user interface during the first phase of the multi-phase glucose monitoring program; obtaining second glucose data for the user during the second phase of the multi-phase glucose monitoring program; a multi-phase engine configured to output the second glucose data in real time at the glucose monitoring user interface during the second phase of the multi-phase glucose monitoring program.

8. 8. The system of claim 7, wherein the sensor kit further includes a third glucose sensor for monitoring glucose during a third phase of the multiphase glucose monitoring program, and a fourth glucose sensor for monitoring glucose during a fourth phase of the multiphase glucose monitoring program.

9. The multi-phase engine, obtaining third glucose data for the user during the third phase of the multi-phase glucose monitoring program from the third glucose sensor of the sensor kit; outputting the third glucose data along with one or more glucose insights or recommendations in real time at the glucose monitoring user interface during the third phase of the multi-phase glucose monitoring program; obtaining fourth glucose data for the user during the fourth phase of the multi-phase glucose monitoring program; 10. The system of claim 8, further configured to output the fourth glucose data in real time in the glucose monitoring user interface during the fourth phase of the multi-phase glucose monitoring program along with one or more additional glucose insights or recommendations.

10. 10. The system of claim 9, further comprising a transmitter configured to form a wireless connection with a computing device that displays the glucose monitoring user interface, the transmitter configured to communicate the first glucose data, the second glucose data, the third glucose data, and the fourth glucose data to the computing device.

Citation Information

Patent Citations

  • Noninvasive Blood Glucose Measurement Method and Apparatus

    US20160174853A1