Patent Application
20240090852
The subject matter described herein relates generally to improvements to analyte monitoring systems, as well as computer-related methods and devices relating thereto.
The detection and/or monitoring of analyte levels, such as glucose, ketones, lactate, oxygen, hemoglobin A1C, or the like, can be vitally important to the health of an individual having diabetes. Patients suffering from diabetes mellitus can experience complications including loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy. Diabetics are generally required to monitor their glucose levels to ensure that they are being maintained within a clinically safe range, and may also use this information to determine if and/or when insulin is needed to reduce glucose levels in their bodies, or when additional glucose is needed to raise the level of glucose in their bodies.
Growing clinical data demonstrates a strong correlation between the frequency of glucose monitoring and glycemic control. Despite such correlation, however, many individuals diagnosed with a diabetic condition do not monitor their glucose levels as frequently as they should due to a combination of factors including convenience, testing discretion, pain associated with glucose testing, and cost.
To increase patient adherence to a plan of frequent glucose monitoring, in vivo analyte monitoring systems can be utilized, in which a sensor control device may be worn on the body of an individual who requires analyte monitoring. To increase comfort and convenience for the individual, the sensor control device may have a small form-factor and can be applied by the individual with a sensor applicator. The application process includes inserting at least a portion of a sensor that senses a user's analyte level in a bodily fluid located in a layer of the human body, using an applicator or insertion mechanism, such that the sensor comes into contact with a bodily fluid. The sensor control device may also be configured to transmit analyte data to another device, from which the individual, her health care provider (“HCP”), or a caregiver can review the data and make therapy decisions.
Despite their advantages, however, some people are reluctant to use analyte monitoring systems for various reasons, including the complexity and volume of data presented, a learning curve associated with the software and user interfaces for analyte monitoring systems, and an overall paucity of actionable information presented.
Thus, needs exist for improved reporting interfaces and software for analyte monitoring systems, as well as methods and devices relating thereto, that are robust, user-friendly, and provide for timely and actionable responses.
Provided herein are example embodiments of improvements to in vivo analyte monitoring systems, and computer-related methods and devices relating thereto. According to some embodiments, a graphical user interface (“GUI”) of an analyte monitoring system is provided, wherein the GUI comprises a graph portion comprising a trend line indicative of a user's analyte levels over a predetermined time period, wherein the trend line is based on data indicative of the user's analyte levels received from a sensor control device. In some embodiments, the graph portion comprises a graphical display of the user's analyte levels over the predetermined time period. The graph portion may have an x-axis representing the predetermined time period. For example, the graph portion may comprise a plurality of data points representing the user's analyte levels over the predetermined time period (for example, in the form of a scatter graph). In some examples, the plurality of data points may be joined together by a line (for example, in the form a line graph). In other examples, the plurality of data points may be discrete and not joined together by a line. According to an aspect of some embodiments, the GUI further comprises a plurality of summary metrics associated with the predetermined time period. In some examples, the summary metrics are associated with the user's analyte levels. According to an aspect of some embodiments, the plurality of summary metrics includes a plurality of minimum analyte levels and maximum analyte levels associated with a plurality of time increments within the predetermined time period. In other words, the plurality of summary metrics may include a minimum analyte level and a maximum analyte level for each time increment of a plurality of time increments within the predetermined time period. In some embodiments, the predetermined time period is one day. For example, the plurality of time increments may comprise twenty-four (24) one-hour increments. In other words, each time increment may have a duration of one hour, for example. In some embodiments, the plurality of minimum analyte levels and maximum analyte levels are aligned with an x-axis of the graph portion. For example, each minimum and maximum analyte level may be aligned with a corresponding time interval on the x-axis, and the plurality of minimum and maximum analyte levels are displayed along the x-axis for the different time intervals.
Many of the embodiments provided herein are improved report GUIs or GUI features for analyte monitoring systems that are highly intuitive, user-friendly, and provide for rapid access to physiological information of a user. More specifically, these embodiments allow a user to easily navigate through and between different user interfaces that can quickly indicate to the user various physiological conditions and/or actionable responses, without requiring the user (or an HCP) to go through the arduous task of examining large volumes of analyte data.
The improvements to the GUIs in the various aspects described and claimed herein produce a technical effect at least in that they assist the user of the device to operate the device more accurately, more efficiently, and more safely. It will be appreciated that the information that is provided to the user via the report GUI, the order in which that information is provided, and the clarity with which that information is structured can have a significant effect on the way the user interacts with the system and the way the system operates. The report GUI therefore guides the user in the technical task of operating the system to take the necessary readings and/or obtain information accurately and efficiently. Other improvements and advantages are provided as well. The various configurations of these devices are described in detail by way of the embodiments which are only examples.
Other systems, devices, methods, features and advantages of the subject matter described herein will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, devices, methods, features, and advantages be included within this description, be within the scope of the subject matter described herein, and be protected by the accompanying claims. Aspects of the embodiments are set out in the independent claims and preferred features are set out in the dependent claims. The preferred features of the dependent claims may be provided in combination in a single embodiment and preferred features of one aspect may be provided in conjunction with other aspects. In no way should the features of the example embodiments be construed as limiting the appended claims, absent express recitation of those features in the claims.
The details of the subject matter set forth herein, both as to its structure and operation, may be apparent by study of the accompanying figures, in which like reference numerals refer to like parts. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the subject matter. Moreover, all illustrations are intended to convey concepts, where relative sizes, shapes and other detailed attributes may be illustrated schematically rather than literally or precisely.
Before the present subject matter is described in detail, it is to be understood that this disclosure is not limited to the particular embodiments described, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present disclosure will be limited only by the appended claims.
As used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise.
The publications discussed herein are provided solely for their disclosure prior to the filing date of the present application. Nothing herein is to be construed as an admission that the present disclosure is not entitled to antedate such publication by virtue of prior disclosure. Further, the dates of publication provided may be different from the actual publication dates which may need to be independently confirmed.
Generally, embodiments of the present disclosure include GUIs, software, and digital interfaces for analyte monitoring systems, and methods and devices relating thereto. Accordingly, many embodiments include in vivo analyte sensors structurally configured so that at least a portion of the sensor is, or can be, positioned in the body of a user to obtain information about at least one analyte of the body. It should be noted, however, that the embodiments disclosed herein can be used with in vivo analyte monitoring systems that incorporate in vitro capability, as well as purely in vitro or ex vivo analyte monitoring systems, including systems that are entirely non-invasive.
Furthermore, for each and every embodiment of a method disclosed herein, systems and devices capable of performing each of those embodiments are covered within the scope of the present disclosure. For example, embodiments of sensor control devices, reader devices, local computer systems, and trusted computer systems are disclosed, and these devices and systems can have one or more sensors, analyte monitoring circuits (e.g., an analog circuit), memories (e.g., for storing instructions), power sources, communication circuits, transmitters, receivers, processors and/or controllers (e.g., for executing instructions) that can perform any and all method steps or facilitate the execution of any and all method steps.
Improved reporting graphical user interfaces for analyte monitoring systems are provided. For example, disclosed herein are various embodiments of graphical user interfaces (“GUIs”). The GUIs are highly intuitive, user-friendly, and provide for rapid access to physiological information of a user. In sum, these embodiments provide for a robust, user-friendly interfaces that can increase user engagement with the analyte monitoring system and provide for timely and actionable responses by the user, to name a few advantages. Other improvements and advantages are provided as well. The various configurations of these devices are described in detail by way of the embodiments which are only examples.
Before describing these aspects of the embodiments in detail, however, it is first desirable to describe examples of devices that can be present within, for example, an in vivo analyte monitoring system, as well as examples of their operation, all of which can be used with the embodiments described herein.
There are various types of in vivo analyte monitoring systems. “Continuous Analyte Monitoring” systems (or “Continuous Glucose Monitoring” systems), for example, can transmit data from a sensor control device to a reader device continuously without prompting, e.g., automatically according to a schedule. “Flash Analyte Monitoring” systems (or “Flash Glucose Monitoring” systems or simply “Flash” systems), as another example, can transfer data from a sensor control device in response to a scan or request for data by a reader device, such as with a Near Field Communication (NFC) or Radio Frequency Identification (RFID) protocol. In vivo analyte monitoring systems can also operate without the need for finger stick calibration.
In vivo analyte monitoring systems can be differentiated from “in vitro” systems that contact a biological sample outside of the body (or “ex vivo”) and that typically include a meter device that has a port for receiving an analyte test strip carrying bodily fluid of the user, which can be analyzed to determine the user's blood sugar level.
In vivo monitoring systems can include a sensor that, while positioned in vivo, makes contact with the bodily fluid of the user and senses the analyte levels contained therein. The sensor can be part of the sensor control device that resides on the body of the user and contains the electronics and power supply that enable and control the analyte sensing. The sensor control device, and variations thereof, can also be referred to as a “sensor control unit,” an “on-body electronics” device or unit, an “on-body” device or unit, or a “sensor data communication” device or unit, to name a few.
In vivo monitoring systems can also include a device that receives sensed analyte data from the sensor control device and processes and/or displays that sensed analyte data, in any number of forms, to the user. This device, and variations thereof, can be referred to as a “handheld reader device,” “reader device” (or simply a “reader”), “handheld electronics” (or simply a “handheld”), a “portable data processing” device or unit, a “data receiver,” a “receiver” device or unit (or simply a “receiver”), or a “remote” device or unit, to name a few. Other devices such as personal computers have also been utilized with or incorporated into in vivo and in vitro monitoring systems.
A memory 163 is also included within ASIC 161 and can be shared by the various functional units present within ASIC 161, or can be distributed amongst two or more of them. Memory 163 can also be a separate chip. Memory 163 can be volatile and/or non-volatile memory. In this embodiment, ASIC 161 is coupled with power source 172, which can be a coin cell battery, or the like. AFE 162 interfaces with in vivo analyte sensor 104 and receives measurement data therefrom and outputs the data to processor 166 in digital form, which in turn processes the data to arrive at the end-result glucose discrete data and trend values, etc. This data can then be provided to communication circuitry 168 for sending, by way of antenna 171, to reader device 120 (not shown), for example, where minimal further processing is needed by the resident software application to display the data. According to some embodiments, for example, a current glucose value can be transmitted from sensor control device 102 to reader device 120 periodically (for example, every minute). In some examples, historical glucose values can be transmitted from sensor control device 102 to reader device 120 periodically (for example, every five minutes).
In some embodiments, to conserve power and processing resources on sensor control device 102, digital data received from AFE 162 can be sent to reader device 120 (not shown) with minimal or no processing. In still other embodiments, processor 166 can be configured to generate certain predetermined data types (e.g., current glucose value, historical glucose values) either for storage in memory 163 or transmission to reader device 120 (not shown), and to ascertain certain alarm conditions (e.g., sensor fault conditions), while other processing and alarm functions (e.g., high/low glucose threshold alarms) can be performed on reader device 120. Those of skill in the art will understand that the methods, functions, and interfaces described herein can be performed—in whole or in part—by processing circuitry on sensor control device 102, reader device 120, local computer system 170, or trusted computer system 180.
Described herein are example embodiments of GUIs for analyte monitoring systems. As an initial matter, it will be understood by those of skill in the art that the GUIs described herein comprise instructions stored in a memory of trusted computer system 180, reader device 120, local computer system 170, and/or any other device or system that is part of, or in communication with, analyte monitoring system 100. These instructions, when executed by one or more processors of the trusted computer system 180, reader device 120, local computer system 170, or other device or system of analyte monitoring system 100, cause the one or more processors to perform the method steps and/or output the GUIs described herein. Those of skill in the art will further recognize that the GUIs described herein can be stored as instructions in the memory of a single centralized device or, in the alternative, can be distributed across multiple discrete devices in geographically dispersed locations.
According to one aspect of the embodiments, GUI 300 can include a graph portion comprising an x-axis 309 based on units of time, and a y-axis 307 indicative of an analyte concentration. For example, GUI 300 includes an x-axis 309, labeled in two-hour increments across a twenty-four hour period, and a y-axis 307, labeled in units of milligrams of glucose per deciliter (mg/dL). Those of skill in the art will appreciate that the x-axis and/or the y-axis can be labeled with other increments or units. For example, the x-axis can be labeled in thirty-minute increments, one-hour increments, or four-hour increments, etc. As another example, the y-axis can be displayed in units of millimoles of glucose per liter (mmol/L).
According to another aspect of the embodiments, the graph portion of GUI 300 can further display a high analyte threshold value (“180 mg/dL”) and a low analyte threshold value (“70 mg/dL”) for a target analyte range 308, as indicated by the numeric labels on the left side. In some embodiments, the numeric values for target analyte range 308 can be a different color from the labels on the x-axis and/or y-axis, so as to make them more distinctive. Furthermore, in some embodiments, a plurality of lines, each of which reflects a corresponding threshold value of the target analyte range 308, can extend across the graph portion to provide a visual reference with respect to the relationship at any point-in-time between the user's analyte levels and target analyte range 308. For example, the lines may include a high analyte threshold line and a low analyte threshold line. In some examples, the lines may be colored, for example with the lines for each threshold being in a different color. This allows the user to more easily compare their analyte levels at particular points-in-time to the target analyte range 308, thereby improving patient safety. In addition, according to some embodiments, the target analyte range 308 can be configured by the user, for example, by adjusting either or both of the high analyte threshold value or the low analyte threshold value. In some embodiments, the lines for the threshold values may be provided without the numeric labels.
Referring still to
According to some embodiments, the respective areas under (or above) the trend line can remain uncolored. In still other embodiments, the trend line can be a single color regardless of whether the analyte levels are above, below, or within target analyte range 308.
According to some embodiments, certain information can also be superimposed on the graph proximate to the trend line. For example, in certain analyte monitoring systems, user-initiated analyte checks 315 can be graphically represented as one or more discrete points on the graph to indicate the time(s) at which said checks occurred. A user-initiated analyte check can be, for example, a finger stick blood glucose test, a scan of the sensor control device, a download of analyte data from a trusted computer system, a view of the analyte monitoring program on the reader device, and/or a rendering of a specific GUI (e.g., home screen, sensor results screen) of the analyte monitoring program on the reader device. Those of skill in the art will appreciate that other types of user-initiated analyte checks are possible and within the scope of the present disclosure. According to another aspect of some embodiments, exercise events can be graphically represented as an exercise icon 316 on the graph to indicate the time(s) at which said exercise events occurred. The information (e.g., corresponding to events such as user-initiated analyte checks 315 and exercise icon 316) may be displayed on the graph or adjacent to the graph, such as aligned with the x-axis.
According to another aspect of some embodiments, GUI 300 can comprise one or more summary metrics. For example, in some embodiments, GUI 300 can include a “Time in Range” metric 304 to indicate the percentage of time (e.g., “79%”) that a user's analyte data was within a target analyte range for the predetermined time period. In other embodiments, the “Time in Range” metric 304 can be displayed as a graphical representation (e.g., a pie chart, a plurality of bar portions, a partially-filled ring), or, in the alternative, a numeric amount of time. Other types of graphical representations for “Time in Range” metrics are described in U.S. Publ. Nos. 2021/0282673, 2022/0248988, 2021/037860, 2022/0000399, 2021/0030323, 2022/0092019, and 2022/0110551, all of which are incorporated by reference in their entireties for all purposes.
Referring still to
Referring next to
According to another aspect of the embodiments, report GUI 320 can have a specific arrangement that enhances a user's ability to recognize patterns across multiple time periods. For example, the x-axis of each of interfaces 320-A, 320-B, 320-C, 320-D, and 320-E can be aligned with each other such that the specific time increments for each interface are also aligned. In this regard, a user is able to quickly recognize if her analyte levels are exceeding an analyte threshold at a particular time of the day (e.g., after lunch).
According to another aspect of the embodiments, report GUI 320 can include the name of the user 322, a label indicating a selected reporting period 324, and a “Time CGM Active” statistic 325 to indicate the amount of analyte data available during the selected reporting period 324. According to some embodiments, the selected reporting period 324 can be configurable by the user. For example, in some embodiments, the selected reporting period 324 can be configured by a selected start date and a selected end date. In other embodiments, the selected reporting period 324 can be configured to a specific period of time (e.g., one week, two weeks, one month, etc.) Furthermore, in some embodiments, the “Time CGM Active” statistic can comprise a percentage of time during the selected reporting period 324 for which analyte data was obtained. In other embodiments, the “Time CGM Active” statistic can comprise an actual amount of time (e.g., “12 Days, 11 Hours, 32 Minutes”). Report GUI 320 can also include a legend 326 providing textual descriptions of one or more icons that are displayed in any one or more of the interfaces 320-A, 320-B, 320-C, 320-D, and/or 320-E.
According to another aspect of the embodiments, report GUI 320 can also include a device label 328 to indicate the types of devices and/or software used to obtain the analyte data for the report. For example, device label 328 can indicate that a user was using a particular analyte monitoring program on their smart phone in conjunction with a particular brand and/or model of an on-body analyte sensor. In some embodiments, device label 328 can also indicate whether data from a medication delivery device (e.g., a connected insulin pen, insulin pump, etc.) was obtained for report GUI 320.
Referring next to
According to one aspect of the embodiments, the plurality of summary metrics of GUI 330 can include a maximum analyte level 332 and a minimum analyte level 334 for the predetermined time period. In addition, maximum analyte levels 336 and minimum analyte levels 338 for each time increment in a plurality of time increments can be displayed along the x-axis and adjacent to the graph portion of GUI 330. For example, as shown in
Referring next to
According to one aspect of the embodiments, GUI 340 can include an icon area for the display of certain events along the x-axis. For example, in some embodiments, an alarm icon 342 can be displayed in the icon area to indicate the detection of an alarm condition. Further, the position of alarm icon 342 along the x-axis can indicate to the user the specific time at which the alarm condition was detected. In addition, according to some embodiments, an alarm label 341 can be displayed next to the alarm icon 342 to indicate the type of alarm condition. As seen in
According to some embodiments, other alarm conditions for which an alarm label can be displayed can include a “high” analyte alarm condition, an “urgent low” or “serious low” analyte alarm condition, a “projected high” analyte alarm condition, a “projected low” analyte alarm condition, a “falling fast” analyte alarm condition, a “rising fast” analyte alarm condition, a “signal loss” condition, among others.
According to another aspect of the embodiments, a carbohydrate icon 343 and/or a medication icon 344 can be displayed in the icon area to indicate, respectively, a meal event or an insulin event. In addition, according to some embodiments, the specific amount of carbohydrates (in units of grams) and/or the type (e.g., rapid-acting or long-acting) and the number of units of insulin injected by the user can also be displayed next to the carbohydrate icon 343 or medication icon 344. Accordingly, a user will be able to visually ascertain, at a glance, whether certain events (e.g., meal or insulin), and specific details regarding those events (e.g., grams of carbohydrates or units of rapid-acting insulin), has had an effect on the trend line.
In addition, although the icons are shown in an icon area that is separate from the graph portion of GUI 340, those of skill in the art will appreciate that, in alternative embodiments, the icons can be displayed directly on the graph adjacent to the trend line. Likewise, details of the alarm condition, grams of carbohydrates, and/or units of insulin can also be displayed directly on the graph adjacent to the trend line. In some examples, information corresponding to events, such as, for example, user-initiated analyte checks 315 and/or exercise icons 316 may be displayed in the icon area along the x-axis (for example, instead of on the graph portion adjacent to the trend line).
Referring next to
Referring next to
Referring next to
According to one aspect of the embodiments, GUI 355 can include a maximum analyte level 356 and a minimum analyte level 357 for the predetermined time period. Likewise, maximum analyte levels 359 and minimum analyte levels 358 for each time increment (e.g., every hour) can be displayed along the x-axis and adjacent to the graph portion. In addition, as can be seen in
Referring next to
Referring next to
Referring next to
According to some embodiments, however, GUI 370 can have numerous differences from GUI 355 of
Referring next to
According to one aspect of the embodiments, however, GUI 380 differs from previous embodiments in that each of the interfaces 380-A, 380-B, 380-C, and 380-D will only display minimum analyte levels 382 or maximum analyte levels 384 for each time increment (e.g., every hour) if they are outside the target analyte range. For example, if a minimum analyte level 382 is below the target analyte range, then the numeric value can be displayed in a first color (e.g., red). Similarly, if a maximum analyte level 384 is above the target analyte range, then the numeric value can be displayed in a second color (e.g., yellow). By contrast, however, if a minimum analyte level or maximum analyte level for a particular time increment is within the target analyte range, then no numeric value is displayed to the user. In this manner, GUI 380 can highlight numeric values that fall outside the target analyte range, allowing the user to better focus on ascertaining the underlying causes of such analyte excursions. In other words, the minimum and maximum analyte levels may be displayed if they are above or below the target analyte range, but not if they are within the target analyte range.
Referring next to
According to one aspect of the embodiments, however, GUI 385 differs from previous embodiments in that interfaces 385-A, 385-B, and 385-C can each also include a graphical representation of an amount of the medication taken. For example, interface 385-C depicts a first bar portion 387 sized proportionally to the amount of rapid-acting insulin taken around 7:00 am, which in this case is “1u.” In addition, interface 385-C depicts a second bar portion 388 sized proportionally to the amount of rapid-acting insulin taken around 11:00 am, which in this case is “3u.” Accordingly, the second bar portion 388 is larger than the first bar portion 387. Furthermore, interface 385-C depicts a medication icon 389 that is labeled with “20 u” to indicate a dose of long-acting insulin taken around 9:00 pm. According to some embodiments, icon 389 is used to reflect a different type of insulin (e.g., rapid-acting versus long-acting) and/or to account for scale (i.e., the bar portion for 20u would not fit on the chart if scaled according to the first and the second bar portions).
Referring next to
Referring next to
Referring next to
According to another aspect of some embodiments, information relating to multiple analytes can be displayed on a GUI or GUI report in a similar manner to the previously disclosed embodiments.
According to another aspect of some embodiments, report GUI 510 can further include information relating to a second analyte, such as, for example, ketone. In particular, a plurality of interfaces is provided, each of which depicts a user's glucose levels and ketone levels over a predetermined time period. In addition, in some embodiments, summary metrics 515 can be displayed for a second analyte (e.g., ketones), including, for example, a number of high ketone threshold alarms 517, a number of elevated ketone threshold alarms 518, and/or a maximum ketone level 519 for the predetermined time period. Furthermore, in some embodiments, a graph portion 520, adjacent to the glucose graph portion, can depict ketone levels over the predetermined time period, such that graph portion 520 is aligned along the same x-axis (e.g., time) as the glucose graph portion. As shown in
According to another aspect of some embodiments, report GUI 510 can be configured such that if the levels of the second analyte (e.g., ketone) are within a predetermined target range during a predetermined time period, then a trend line will not be displayed. Referring again to
It will be understood by those of skill in the art that any of the GUIs, reports interfaces, or portions thereof, as described herein, are meant to be illustrative only, and that the individual elements, or any combination of elements, depicted and/or described for a particular embodiment or figure are freely combinable with any elements, or any combination of elements, depicted and/or described with respect to any of the other embodiments. For example, the display of meal information (e.g., amount of carbohydrate) and medication information (e.g., rapid-lasting and long-lasting insulin) for each time increment may be provided or omitted in each of the embodiments described. In addition, the display of alarm icons and alarm labels for the predetermined time period may be provided or omitted in each of the embodiments described. The display of a graphical representation of the amount of medication also may be provided or omitted in each of the embodiments described. The display of summary metrics for the total amounts of meal information and/or medication information over the predetermined time period may be provided or omitted in each of the embodiments described. The “Time in Range” metric may be provided or omitted in each of the embodiments described. The coloring of the graph (e.g., the trend line, the threshold lines, and/or the shaded portions) may be provided or omitted in each of the embodiments described.
In some embodiments, data indicative of the user's analyte levels can be wirelessly transmitted from the sensor control device 102 to the reader device 120, for example, automatically (i.e., without user intervention). For example, the sensor control device 102 may periodically transmit analyte data to the reader device (e.g., by Bluetooth or BLE) without requiring the user to manually perform a scan (e.g., by NFC).
In analyte monitoring systems where data indicative of a user's analyte levels is wirelessly and automatically transmitted from a sensor control device 102 to a reader device 120, the embodiments described herein can be advantageous in that numeric values associated with a subject's analyte levels for each time increment with a predetermined time period (or a subset thereof) can be regularly displayed, such that the user (or her HCP) can make more informed treatment decisions. The numeric values associated with each time increment can be further correlated with events—such as medication, exercise, and/or meals—thereby providing the user (or her HCP) with a robust overview of the user's overall glycemic control over a predetermined time period.
It will also be understood by those of skill in the art that any of the GUIs, reports interfaces, or portions thereof, as described herein, can be implemented in an analyte monitoring system for monitoring one or more types of analytes. These analytes can include one or more of glucose, ketones, lactate, alcohol, or any other analytes that are detectable in a bodily fluid of the user. Preferably, the analyte comprises glucose. It will also be understood by those of skill in the art that the GUIs, reports interfaces, or portions thereof, as described herein, can incorporate data received from multiple analyte monitoring systems and devices relating thereto, including the incorporation of data from devices for taking ex vivo analyte measurements and/or physiological measurements.
It should be noted that all features, elements, components, functions, and steps described with respect to any embodiment provided herein are intended to be freely combinable and substitutable with those from any other embodiment. If a certain feature, element, component, function, or step is described with respect to only one embodiment, then it should be understood that that feature, element, component, function, or step can be used with every other embodiment described herein unless explicitly stated otherwise. This paragraph therefore serves as antecedent basis and written support for the introduction of claims, at any time, that combine features, elements, components, functions, and steps from different embodiments, or that substitute features, elements, components, functions, and steps from one embodiment with those of another, even if the following description does not explicitly state, in a particular instance, that such combinations or substitutions are possible. It is explicitly acknowledged that express recitation of every possible combination and substitution is overly burdensome, especially given that the permissibility of each and every such combination and substitution will be readily recognized by those of ordinary skill in the art.
While the embodiments are susceptible to various modifications and alternative forms, specific examples thereof have been shown in the drawings and are herein described in detail. It should be understood, however, that these embodiments are not to be limited to the particular form disclosed, but to the contrary, these embodiments are to cover all modifications, equivalents, and alternatives falling within the spirit of the disclosure. Furthermore, any features, functions, steps, or elements of the embodiments may be recited in or added to the claims, as well as negative limitations that define the inventive scope of the claims by features, functions, steps, or elements that are not within that scope.
In summary, improved graphical user interfaces for analyte monitoring systems are provided. For example, disclosed herein are various embodiments of GUIs, each of which include a graph portion comprising a trend line indicative of a user's analyte levels over a predetermined time period, and a plurality of summary metrics comprising a plurality of minimum analyte levels and maximum analyte levels associated with a plurality of time increments within the predetermined time period. In many embodiments, the plurality of minimum analyte levels and maximum analyte levels are aligned with an x-axis of the graph portion.
The disclosure of this application also contains the following numbered clauses:
This application claims priority to U.S. Provisional Application No. 63/538,592, filed Sep. 15, 2023, and U.S. Provisional Application No. 63/407,430, filed Sep. 16, 2022, both of which are hereby expressly incorporated by reference in their entireties for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 63538592 | Sep 2023 | US | |
| 63407430 | Sep 2022 | US |
