SYSTEMS, DEVICES AND METHODS FOR ANALYTIC MONITORING
The system addresses the challenge of suboptimal glucose monitoring in diabetes by offering personalized metrics and user-friendly interfaces, enhancing compliance and accuracy in glucose management.
Patent Information
- Application Number
- DE112022005485
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-15
- Filing Date
- 2022-11-14
- Publication Date
- 2024-11-14
AI Technical Summary
Individuals with diabetes often fail to monitor their glucose levels frequently due to convenience, pain, and complexity associated with existing analyte monitoring systems, leading to suboptimal glycemic control and increased risk of complications.
A system comprising a sensor control device and a reading device that provides personalized glucose metrics, including adjusted A1c, calculated A1c, personalized glucose, and personalized time in range, using physiological parameters to enhance user engagement and timely actionable responses through intuitive and user-friendly graphical user interfaces.
The system improves user compliance and accuracy of glucose monitoring by providing personalized and actionable insights, enabling timely interventions and reducing the complexity of existing systems.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
CROSS-REFERENCE TO RELATED REGISTRATIONS
[0001] This application claims priority pursuant to 35 USC § 119(e) over the preliminary US patent application No. 63 / 279,509 filed on November 15, 2021, which is incorporated herein in its entirety by reference. AREA
[0002] The subject described here generally refers to improved analyte monitoring systems as well as to methods and devices related thereto. BACKGROUND
[0003] The detection and / or monitoring of analyte levels such as glucose, ketones, lactate, oxygen, hemoglobin A1C, albumin, alcohol, alkaline phosphatase, alanine transaminase, aspartate aminotransferase, bilirubin, blood urea nitrogen, calcium, carbon dioxide, chloride, creatinine, hematocrit, lactate, magnesium, oxygen, pH, phosphorus, potassium, sodium, total protein, uric acid, etc., can be important for the health of a person with diabetes. Patients suffering from diabetes mellitus may experience complications such as loss of consciousness, cardiovascular disease, retinopathy, neuropathy, and nephropathy.Diabetics usually need to monitor their glucose levels to ensure they are kept within a clinically safe range, and can also use this information to determine if and / or when insulin is needed to lower the glucose level in their body, or when additional glucose is needed to raise the glucose level in their body.
[0004] Increasing clinical data show a strong correlation between the frequency of glucose monitoring and glycemic control. Despite this correlation, many people diagnosed with diabetes do not monitor their glucose levels as frequently as they should due to a combination of factors, including convenience, discretion in performing tests, and the associated pain and cost of glucose testing.
[0005] To improve patient adherence to a frequent glucose monitoring schedule, in vivo analyte monitoring systems can be used, in which a sensor control device can be worn on the body of the person requiring analyte monitoring. To increase comfort and convenience for the individual, the sensor control device can be small and applied by the individual using a sensor applicator. The application process involves inserting at least one portion of a sensor, which detects the user's analyte level in a body fluid located in a layer of the human body, using an applicator or insertion mechanism, so that the sensor comes into contact with the body fluid.The sensor control device can also be configured to transmit analytical data to another device from which the person, their healthcare provider (“HCP”) or a nurse can review the data and make treatment decisions.
[0006] Despite their advantages, some people are hesitant to use analyte monitoring systems for various reasons, including the complexity and amount of data presented, the learning curve associated with the software and user interfaces for analyte monitoring systems, and a general lack of available usable information.
[0007] Therefore, there is a need for improved digital and graphical user interfaces for analyte monitoring systems, as well as for appropriate methods and devices that are robust and user-friendly and enable timely and actionable responses. SUMMARY
[0008] The purpose and advantages of the disclosed subject matter are set out in the following description and are evident from it, and are further learned through practical application of the disclosed subject matter. Additional advantages of the disclosed subject matter are realized and achieved through the methods and systems particularly highlighted in the written description, the claims, and the accompanying drawings.
[0009] To achieve these and other advantages, and in accordance with the objective of the disclosed subject matter as implemented and generally described, the disclosed subject matter is directed towards glucose monitoring systems. According to one embodiment, a glucose monitoring system may include a sensor control device and a reading device. The sensor control device may include an analyte sensor coupled to sensor electronics and may be configured to transmit data indicating an analyte level of a subject. The reading device may include a wireless communication circuitry configured to receive data indicating the analyte level and a level of glycated hemoglobin for the subject, a non-transient memory, and at least one processor.which is coupled to the non-transient memory and the analyte sensor via communication technology and is configured to calculate several personalized glucose metrics for the subject using at least one physiological parameter and at least one of the received data indicating the analyte level or the received level of glycated hemoglobin, and to display a report on a display device of the reading device, which comprises several interfaces that display at least two or more of the received data indicating the analyte level, the received level of glycated hemoglobin, or the calculated multiple personalized glucose metrics, wherein the multiple interfaces comprising the report are based on a user type.
[0010] As described here, the multiple personalized glucose metrics can include one or more from a customized A1c or a personalized A1c, a calculated A1c, a customized calculated A1c, a personalized glucose, a personalized average glucose, or a personalized time in range. Furthermore, the at least one processor can be configured to calculate multiple personalized glucose targets corresponding to the calculated multiple personalized glucose metrics. The multiple interfaces can also contain the multiple personalized glucose targets. Additionally, the multiple personalized glucose targets can include a glucose target range and / or an average glucose target. As described here, the personalized glucose target range can include a personalized glucose lower limit. Alternatively, the personalized glucose target range can also include a personalized glucose upper limit.
[0011] As explained here, at least one physiological parameter can be selected from the group consisting of: red blood cell glucose uptake, red blood cell lifetime, red blood cell glycation rate constant, red blood cell production rate constant, red blood cell elimination constant, and apparent glycation rate constant. Furthermore, the multiple interfaces can contain at least one physiological parameter for the subject.
[0012] As explained here, the user type can include a healthcare professional. Furthermore, the multiple interfaces can include a glucose monitoring data interface, a glycated hemoglobin interface, a personalized a1c interface, a personalized glucose interface, a personalized average glucose interface, and a personalized time-in-range interface.
[0013] As explained here, the user type can include the subject. Furthermore, the multiple interfaces can include a glucose monitoring data interface, a glycated hemoglobin interface, a mean glucose interface, and a time-in-range interface.
[0014] As explained here, the multiple interfaces that comprise the report can be predetermined based on the user type.
[0015] As explained here, the user can select the multiple interfaces that comprise the report.
[0016] As described here, at least one processor can further be configured to issue a message if at least one of the multiple personalized glucose metrics is at or above the corresponding multiple personalized glucose targets. As described here, the message can be a visual message. Alternatively, the message can be an audio message. The message can also be an alarm. As described here, the message can be a prompt.
[0017] As explained here, the reading device can wirelessly receive the value for glycated hemoglobin for the subject from an electronic patient record system.
[0018] As explained here, the reading device can receive the level of glycated hemoglobin for the subject from a cloud-based database.
[0019] As explained here, the reading device can obtain the level of glycated hemoglobin for the subject from a QR code.
[0020] As explained here, the reading device can obtain the glycated hemoglobin value for the subject from a home test kit. BRIEF DESCRIPTION OF THE FIGURES
[0021] The details of the object presented here, both in terms of its structure and its function, can be seen from the accompanying figures, where identical reference symbols refer to identical parts. The components in the figures are not necessarily to scale; instead, the emphasis is on illustrating the principles of the object. Furthermore, all representations are intended to convey concepts, and relative sizes, shapes, and other detailed attributes may be depicted schematically rather than literally or precisely. Fig. Figure 1 is a system overview of an analyte monitoring system comprising a sensor applicator, a sensor control device, a reading device, a network, a trusted computer system, and a local computer system. Fig. 2A is a block diagram that illustrates an example implementation of a reading device. Fig. 2B and Fig. 2C are block diagrams that illustrate example implementations of sensor control devices. Fig. 2D to 21 are example implementation forms of GUIs that include sensor result interfaces. Fig. 2J-L are example implementations of GUIs that include a glucose monitoring data interface and an interface for calculated A1c. Fig. 3A to 3F are example implementations of GUIs that include time-in-domain interfaces. Fig. 4A to 40 are example implementations of GUIs that include analyte level and trend alert interfaces. Fig. 5A and Fig. 5B are example implementation forms of GUIs that include sensor usage interfaces. Fig. 5C to 5F are example implementation forms of report GUIs that contain sensor usage information. Fig. 5G-5L are example implementation forms of GUIs relating to an analyte monitoring software application. Fig. 6A and Fig. 6B are flowcharts that illustrate example implementation forms of procedures for data replenishment in an analyte monitoring system. Fig. 6C is a flowchart that illustrates an example implementation of a procedure for aggregating interruption and reconnection events in an analyte monitoring system. Fig. 7C is a flowchart that illustrates an example implementation of a procedure for failed or expired sensor transmissions in an analyte monitoring system. Fig. 8A and Fig. 8B are flowcharts that illustrate example implementation forms of procedures for data merging in an analyte monitoring system. Fig. Figures 8C to 8E are diagrams that depict data at different stages of processing according to an example implementation of a data merging procedure in an analyte monitoring system. Fig. 9A is a flowchart that illustrates an example implementation of a sensor transition procedure in an analyte monitoring system. Fig. 9B to 9D are example implementation forms of GUIs that are to be displayed according to an example implementation form of a sensor transition procedure in an analyte monitoring system. Fig. 10A is a flowchart that illustrates an example implementation of a procedure for generating a sensor insertion error system alarm. Fig. 10B to 10D are example implementations of GUIs that are to be displayed according to an example implementation of a procedure for generating a sensor insertion error system alarm. Fig. 11A is a flowchart that illustrates an example implementation of a procedure for generating a sensor termination system alarm. Fig. 11B to 11D are example implementations of GUIs that are to be displayed according to an example implementation of a method for generating sensor termination system alarms. Fig. 12 presents an exemplary timeline 100, which explains the collection of at least one HbA1c value and several glucose levels for a period of time. Fig. 13 presents an example of a system for analyzing physiological parameters to provide an analysis of physiological parameters in accordance with some of the embodiments of the present disclosure. Fig. 14 presents an example of a system for analyzing physiological parameters to provide an analysis of physiological parameters in accordance with some of the embodiments of the present disclosure. Fig. 15 presents an example of a report of calculated HbA1c (eHbA1c) that can be generated as output by a system for analyzing physiological parameters, in accordance with some of the embodiments of the present disclosure. Fig. 16A presents an example of a method for determining a personalized glucose target range in accordance with some embodiments of the present disclosure. Fig. 16B presents an example of a personalized glucose target range report that can be generated as output by a system for analyzing physiological parameters, in accordance with some of the embodiments of the present disclosure. Fig. 17 presents an example of a report on a personalized target for average glucose that can be generated as output by a system for analyzing physiological parameters, in accordance with some of the embodiments of the present disclosure. Fig. Figures 18A-C present a comparison between laboratory HbA1c levels on day 200 (±5 days) relative to the estimated HbA1c values (eHbA1c values) for two different models (18A and 18B) and calculated HbA1c values (cHbA1c values) for the kinetic model of the present disclosure (18C). Fig. Figure 19 presents the data of an exemplary subject with the measured glucose levels (solid line), the HbA1c laboratory measurements (open circles), the cHbA1c model values (long dashed line) and the 14-day eHbA1c model values (dotted line). Fig. Figure 20 shows the relationship between constant glucose and equilibrium HbA1c (1) as determined using the standard conversion of HbA1c to estimated mean glucose (dashed line with error bars), and (2) as measured for the 90 participants (solid lines). Fig. 21 presents the relationship between K (dL / mg) and the target average glucose level (mg / dL) for varying HbA1c target values using the kinetic model of the present disclosure. Fig. Figure 22 is a graphical representation of the average glucose level and laboratory A1c. Fig. 23-29 provide case study implementation formats for reports of the present disclosure. Fig. Figure 30 represents an exemplary healthcare provider interface in accordance with embodiments of the present disclosure. DETAILED DESCRIPTION
[0022] Before the subject matter of this disclosure is described in detail, it should be understood that this disclosure is not limited to the specific embodiments described, as these can naturally vary. It should also be understood that the terminology used here serves only to describe specific embodiments and is not intended to be restrictive, since the scope of this disclosure is limited only by the accompanying claims.
[0023] As used here and in the attached claims, the singular forms “ein”, “eine” and “der / die / das” include reference to the plural unless the context clearly indicates otherwise.
[0024] The publications discussed here are made available only for disclosure prior to the filing date of this application. Nothing here should be construed as an admission that this disclosure is not entitled to anticipate such a publication based on an earlier disclosure. Furthermore, the stated publication dates may differ from the actual publication dates, which may require independent confirmation.
[0025] In general, embodiments of this disclosure include GUIs and digital interfaces for analyte monitoring systems and methods and devices relating thereto. Accordingly, many embodiments include in vivo analyte sensors that are structurally configured such that at least one portion of the sensor is, or can be, positioned within a user's body to obtain information about at least one analyte of the body. However, it should be noted that the embodiments disclosed herein can be used with in vivo analyte monitoring systems that include an in vitro capability, as well as with purely in vitro or ex vivo analyte monitoring systems, including systems that are completely non-invasive.
[0026] Furthermore, for each individual embodiment of a method disclosed herein, systems and devices capable of performing each of these embodiments are covered by the scope of protection of this disclosure. For example, embodiments of sensor control devices, reading devices, local computer systems, and trusted computer systems are disclosed, and these devices and systems may include 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 control units (e.g., for executing instructions) that can perform any and all method steps or facilitate the execution of any and all method steps.
[0027] As previously described, several of the embodiments described here provide enhanced GUIs for analyte monitoring systems, with the GUIs being highly intuitive and user-friendly, providing quick access to a user's physiological information. According to some embodiments, a time-in-range GUI of an analyte monitoring system is provided, wherein the time-in-range GUI comprises multiple bars or bar segments, each bar or bar segment indicating a time period during which a user's analyte level remains within a predefined analyte range correlated with the bar or bar segment. According to another embodiment, an analyte level / trend alert GUI of an analyte monitoring system is provided, wherein the analyte level / trend alert GUI displays a visual message (e.g., prompts, warnings, alarms, pop-up windows, banner messages, etc.).) and wherein the visual message includes an alarm condition, an analyte level measurement associated with the alarm condition, and a trend indicator associated with the alarm condition. Overall, these embodiments provide robust, user-friendly interfaces that can increase user engagement with the analyte monitoring system and enable timely and actionable user responses, to name just a few advantages.
[0028] In addition, several of the embodiments described herein provide improved digital interfaces for analyte monitoring systems. According to some embodiments, improved methods, as well as systems and devices relating thereto, are provided for data padding, aggregation of interruption and reconnection events for wireless communication links, expired or failed sensor transmissions, merging data from multiple devices, transitioning from previously activated sensors to new read devices, generating sensor insertion failure system alarms, and generating sensor termination system alarms.Together and individually, these digital interfaces improve the accuracy and integrity of the analyte data collected by the analyte monitoring system, the flexibility of the system by allowing users to switch between different reading devices, and the system's alarm capabilities by providing more robust communication between devices under specific adverse conditions, to name just a few. Other improvements and benefits are also provided. The various configurations of these devices are described in detail using the embodiments, which are only examples.
[0029] Before describing these aspects of the embodiments in detail, it is desirable to first describe examples of devices that may be present, for example, in an in vivo analyte monitoring system, as well as examples of their operation, all of which can be used with the embodiments described here.
[0030] There are several types of in vivo analyte monitoring systems. Continuous analyte monitoring (or continuous glucose monitoring) systems, for example, can continuously and without prompting, such as automatically according to a schedule, transmit data from a sensor controller to a reader. Flash analyte monitoring (or flash glucose monitoring, or simply "flash" systems), as another example, can transmit data from a sensor controller in response to a query or data request from a reader, such as using a near-field communication (NFC) or radio frequency identification (RFID) protocol. In vivo analyte monitoring systems can also operate without the need for finger-prick calibration.
[0031] In vivo analyte monitoring systems can be distinguished from “in vitro” systems, which come into contact with a biological sample outside the body (or “ex vivo”) and typically include a measuring device that has a port for receiving an analyte test strip containing the user’s body fluid, which can be analyzed to determine the user’s blood glucose level.
[0032] In vivo monitoring systems may include a sensor that, while positioned in vivo, comes into contact with the user's body fluid and detects the analyte levels contained therein. The sensor may be part of the sensor control device, which is located on the user's body and contains the electronics and power supply that enable and control the analyte detection. The sensor control device and variations thereof may also be referred to as a "sensor control unit," "body electronics" device or unit, "body" device or unit, or "sensor data communication" device or unit, to name a few.
[0033] In vivo monitoring systems may also include a device that receives acquired analyte data from the sensor control device and processes and / or displays this acquired analyte data to the user in any number of forms. This device and variations thereof may be referred to as a "handheld reader," "reader" (or simply "reading device"), "handheld electronics" (or simply "handheld device"), "portable data processing" device or unit, "data receiver," "receiver" device (or simply "receiver"), or "remote control" device or unit, to name a few. Other devices, such as personal computers, have also been used with or integrated into in vivo and in vitro monitoring systems. Example implementation of an in-vivo analyte monitoring system
[0034] Fig. Figure 1 is a conceptual diagram illustrating an example embodiment of an analyte monitoring system 100, which includes a sensor applicator 150, a sensor control device 102, and a reader 120. Here, the sensor applicator 150 can be used to apply the sensor control device 102 to a monitoring site on a user's skin, with a sensor 104 being held in position by an adhesive patch 105 for a period of time. The sensor control device 102 is located in the Fig. 2B and Fig. 2C is described in more detail and can communicate with the reader 120 via a communication path 140 using wired or wireless technology. Examples of wireless protocols include Bluetooth, Bluetooth Low Energy (BLE, BTLE, Bluetooth SMART, etc.), Near Field Communication (NFC), and others. Users can view and use the applications installed in the memory on the reader 120 using the screen 122 (which in many embodiments may include a touchscreen) and the input 121. A device battery of the reader 120 can be recharged using the power connector 123. Although only one reader 120 is shown, the sensor control device 102 can communicate with multiple readers 120. Each of the readers 120 can communicate with the others and share data.Further details about the reading device 120 are below in relation to . Fig. 2A. The reading device 120 can communicate with the local computer system 170 via a communication path 141 using a wired or wireless communication protocol. The local computer system 170 can include one or more devices, such as a laptop, desktop computer, tablet, phablet, smartphone, set-top box, video game console, or other computing device, and the wireless communication can include any of a number of applicable wireless network protocols, including Bluetooth, Bluetooth Low Energy (BTLE), Wi-Fi, or others. The local computer system 170 can communicate with a network 190 via the communication path 143, similarly to how the reading device 120 can communicate with the network 190 via a communication path 142, using a wired or wireless communication protocol as previously described. The network 190 can be any of a number of networks, such as...B. private networks and public networks, local or wide area networks, and so on. A trusted computer system 180 may include a cloud-based platform or server and may provide authentication services, secure data storage (e.g., storage of the analytical measurement data received from the reading device), report generation, and may communicate with the network 190 via communication path 144 using wired or wireless technology. Additionally, although . Fig. 1. If the trusted computer system 180 and the local computer system 170 are depicted communicating with a single sensor control device 102 and a single reader 120, then it is understood by those skilled in the art that the local computer system 170 and / or the trusted computer system 180 are each capable of communicating with multiple readers and sensor control devices, either wired or wirelessly.
[0035] Additional details regarding suitable analyte monitoring devices, systems, methods, components and their operation, together with related features, are contained in U.S. Patent No. 9,913,600 for Taub et al., International Publication No. WO2018 / 136898 for Rao et al., International Publication No. WO2019 / 236850 for Thomas et al., and U.S. Patent Publication No. 2020 / 01969191 for Rao et al., all of which are incorporated herein by reference in their entirety. Example design for a reading device
[0036] Fig. Figure 2A is a block diagram illustrating an example embodiment of a reading device 120, which in some embodiments may include a smartphone or smartwatch. Here, the reading device 120 may include a display device 122, an input component 121, and a processing core 206, which contains a communication processor 222 coupled to a memory 223 and an application processor 224 coupled to a memory 225. It may also include a separate memory 230, an RF transmitter / receiver 228 with an antenna 229, a power supply 226, and a power management module 238. Furthermore, the reading device 120 may also include a multifunctional transmitter / receiver 232, which may comprise a wireless communication circuit arrangement and may be configured to communicate via Wi-Fi, NFC, Bluetooth, BTLE, and GPS with one or more antennas 234.As an expert understands, these components are electrically and communicatively coupled in such a way that they form a functional device. Example designs of sensor control devices
[0037] Fig. 2B and Fig. Figure 2C are block diagrams depicting example embodiments of sensor control devices 102, which include analyte sensors 104 and sensor electronics 160 (containing an analyte monitoring circuit arrangement) that can possess most of the processing capability for rendering end-result data suitable for display to the user. Fig. Figure 2B shows a single semiconductor chip 161, which can be a user-specific application-specific integrated circuit (ASIC). Within the ASIC 161, special high-level functional units are shown, comprising an analog front end (AFE) 162, a power management (or control) circuit arrangement 164, a processor 166, and a communication circuit arrangement 168 (which can be implemented as a transmitter, receiver, transmitter / receiver, passive circuit, or otherwise according to the communication protocol). In this embodiment, both the AFE 162 and the processor 166 are used as an analyte monitoring circuit arrangement; however, in other embodiments, either circuit can perform the analyte monitoring function.The processor 166 can contain one or more processors, microprocessors, control units and / or microcontrol units, each of which can be a discrete chip or distributed across a number of different chips (and a section thereof).
[0038] A memory 163 is also included in the ASIC 161 and can be shared by the various functional units present in the ASIC 161 or distributed across two or more of them. The memory 163 can also be a separate chip. The memory 163 can be volatile and / or non-volatile memory. In this embodiment, the ASIC 161 is coupled to the power source 170, which can be a coin cell battery or the like. The AFE 162 has an interface with the in-vivo analytical sensor 104 and receives measurement data from it, outputting the data in digital form to the processor 166, which in turn processes the data to obtain the discrete and trend values of glucose, etc., as the final result.This data can then be provided to the communication circuit arrangement 168 for transmission, for example, via the antenna 171 to the reader 120 (not shown), where minimal further processing by the resident software application is required to display the data. According to some embodiments, for example, a current glucose value can be transmitted from the sensor control device 102 to the reader 120 every minute, and glucose trend values can be transmitted from the sensor control device 102 to the reader 120 every five minutes.
[0039] In some embodiments, the digital data received by the AFE 162 can be sent to the reader 120 (not shown) with minimal or no processing to save energy and processing resources on the sensor control device 102. In still other embodiments, the processor 166 can be configured to generate specific predetermined data types (e.g., the current glucose value, glucose trend values) either for storage in the memory 163 or for transmission to the reader 120 (not shown) and to detect specific alarm conditions (e.g., sensor fault conditions), while other processing and alarm functions (e.g., high / low glucose threshold alarms) can be performed on the reader 120.Experts will understand that the procedures, functions and interfaces described here can be implemented - in whole or in part - by a processing circuit arrangement on the sensor control device 102, the reading device 120, the local computer system 170 or the trusted computer system 180.
[0040] Fig. 2C is similar Fig. 2B, however, contains instead two discrete semiconductor chips 162 and 174, which may be packed together or separately. Here, the AFE 162 is located on the ASIC 161. The processor 166 is integrated with the power management circuit assembly 164 and the communication circuit assembly 168 on the chip 174. The AFE 162 may contain a memory 163, and the chip 174 contains a memory 165, which may be isolated or distributed within it. In one example embodiment, the AFE 162 is combined with the power management circuit assembly 164 and the processor 166 on a single chip, while the communication circuit assembly 168 is on a separate chip. In another example embodiment, both the AFE 162 and the communication circuit assembly 168 are on a single chip, and the processor 166 and the power management circuit assembly 164 are on a separate chip.It should be noted that other chip combinations are also possible, containing three or more chips, each of which is responsible for the separate functions described, or which share one or more functions to ensure fail-safe redundancy. Example implementation forms of graphical user interfaces for analyte monitoring systems
[0041] Example implementations of GUIs for analyte monitoring systems are described here. As a starting point, those skilled in the art will understand that the GUIs described here comprise instructions stored in memory of the reader 120, the local computer system 170, the trusted computer system 180, and / or another device or system that is part of or communicates with the analyte monitoring system 100. When executed by one or more processors of the reader 120, the local computer system 170, the trusted computer system 180, or any device or system of the analyte monitoring system 100, these instructions cause the one or more processors to perform the procedure steps and / or output the GUIs described here.Experts will further recognize that the GUIs described here can be stored as instructions in the memory of a single central device, or alternatively, distributed across multiple discrete devices at geographically distributed locations. Example implementation forms of models for personalized glucose-related metrics
[0042] This document describes example implementations of models for personalized glucose-related metrics. It generally describes methods, devices, and systems for determining physiological parameters related to the kinetics of glycation, red blood cell elimination and formation, and reticulocyte maturation in a subject's body. Such physiological parameters can be used, for example, to calculate a more reliable calculated HbA1c (cHbA1c), an adapted or personalized HbA1c (aHbA1c), an adapted calculated HbA1c (acHbA1c), and / or a personalized glucose target range for personalized diagnoses, treatments, and / or monitoring protocols for the subject.
[0043] Here, the terms "HbA1c level," "HbA1c value," and "HbA1c" are used interchangeably. Here, the terms "personalized A1c," "personalized HbA1c," "aHbA1c level," "aHbA1c value," and "aHbA1c" are used interchangeably. Here, the terms "cHbA1c level," "cHbA1c value," "cHbA1c," and "GD-A1c" are used interchangeably, and / or a personalized glucose target range, among others. Here, the terms "acHbA1c level," "acHbA1c value," and "acHbA1c" are used interchangeably. Kinetic model
[0044] High glucose load in specific organs (particularly the eyes, kidneys, and nerves) is a crucial factor in the development of diabetes complications. Laboratory HbA1c (also referred to as measured HbA1c) is routinely used to assess glycemic control, but studies report a decoupling between this glycemic marker and diabetes complications in some individuals. The precise mechanisms that prevent laboratory HbA1c from predicting diabetes complications are often unclear, but in some cases, they are likely related to an inaccurate estimation of the intracellular glucose load in the affected organs.
[0045] Formula 1 represents the kinetics of red blood cell hemoglobin glycation (or simply red blood cell glycation), red blood cell elimination, and red blood cell formation, where "G" represents free glucose, "R" represents an unglycated red blood cell, and "GR" represents glycated red blood cell hemoglobin. The rate at which glycated red blood cell hemoglobin (GR) is formed is referred to here as the red blood cell hemoglobin glycation rate constant (kR). gly typically in units of dl_*mg- 1 *Day ! ).
[0046] Over time, red blood cells, which contain glycated red blood cells, are continuously eliminated from a person's circulatory system, and new red blood cells are formed, typically at a rate of about 2 million cells per second. The rates associated with elimination and formation are referred to here as the red blood cell elimination constant (k0). age typically in units of day -1 ) or as the formation rate constant for red blood cells (k gen typically in units of M 2 / day). Since the number of red blood cells in the body is kept at a stable level most of the time, the ratio of k age and k gen be an individual constant that is the square of the red blood cell concentration.
[0047] Regarding glycation, formula 2 describes the mechanism in more detail, with glucose transporter 1 (GLUT1) facilitating the transport of glucose (G) into red blood cells. The intracellular glucose (Gl) then interacts with hemoglobin (Hb) to produce glycated hemoglobin (HbG), with the reaction rate constant of hemoglobin glycation being given by k. g is represented (typically in units of dl_*mg- 1 *Day ! ). A typical experimentally measured k g The value is 1.2×10 3 dB / mg / day. The hemoglobin glycation reaction is a multi-step, non-enzymatic chemical reaction; therefore, k g be a universal constant. The rate constant for the transport of glucose into red blood cells and the glycation of Hb to HbG is k gly Then k describes agethe elimination of red blood cells (together with hemoglobin), also referred to here as the turnover rate of red blood cells.
[0048] While elevated intracellular glucose is responsible for diabetic complications, extracellular hyperglycemia selectively damages cells that have limited ability to effectively adjust glucose transport across membranes. HbA1c has been used as a biomarker for diabetic intracellular hyperglycemia primarily for two reasons. First, the glycation reaction takes place within red blood cells (RBCs), so the HbA1c level is regulated by the intracellular glucose level. Second, RBCs lack the capacity to adjust the level of the glucose transporter GLUT1 and are therefore unable to alter glucose uptake across the membrane, behaving similarly to cells selectively damaged by extracellular hyperglycemia.Therefore, under conditions of a fixed RBC lifespan and glucose uptake across the membrane, HbA1c reflects the intracellular glucose load in organs affected by diabetic complications. However, given the variability between individuals in both glucose uptake across the membrane and RBC lifespan, laboratory HbA1c may not always reflect the intracellular glucose load. While variations in RBC glucose uptake across the membrane are likely important for estimating the risk of diabetic complications in vulnerable organs, the lifespan of red blood cells (RBCs) is fixed and therefore not relevant for the risk of complications in other tissues.This explains the inability to rely clinically on laboratory HbA1c in individuals with hematological disorders characterized by abnormal RBC turnover and represents a possible explanation for the apparent ‘decoupling’ between laboratory HbA1c and the development of complications in some individuals with diabetes (. Fig. 1).
[0049] To overcome the limitations of laboratory-derived HbA1c, a measure of personalized HbA1c has been developed that accounts for individual variations in both red blood cell (RBC) turnover and cellular glucose uptake. The current work aims to extend this model by incorporating a standardized RBC lifespan of 100 days (corresponding to an RBC turnover rate of 1% per day or an average RBC age of 50 days) to create a novel clinical marker called adjusted HbA1c (aHbA1c). It is proposed that aHbA1c is the most important glycemic marker for assessing organ stress from hyperglycemia and the risk of future diabetes-related complications.
[0050] As previously described, HbA1c is a commonly used analyte that indicates the proportion of glycated hemoglobin found in red blood cells. Therefore, a kinetic model can be used, for example, to derive a calculated HbA1c based on at least the glucose levels measured for a subject. However, the kinetic model can also be applied to HbA1. For simplicity, HbA1c is used consistently here, but HbA1 could be substituted, except in cases where specific HbA1c values are used (see, for example, Equations 15 and 16). In such cases, specific HbA1 values could be used to derive similar equations.
[0051] Typically, in kinetic modeling of physiological processes, assumptions are made to focus on the factors that most strongly influence the physiological process and to simplify some of the mathematical calculations.
[0052] The present disclosure uses only the following set of assumptions for the kinetic modeling of the physiological process depicted in Equation 1. First, the glucose concentration is high enough not to be affected by the glycation reaction of red blood cells. Second, there are no abnormal red blood cells that would affect the HbA1c measurement, so the hematocrit is constant for the time period of interest. This assumption was made to exclude extreme conditions or life events that do not normally occur and could affect the accuracy of the model. Third, the glycation process is primarily dependent on both the red blood cell concentration and the glucose concentration.Fourth, newly formed red blood cells contain a negligible amount of glycated hemoglobin, as previous reports indicate that reticulocyte HbA1c is very low and almost undetectable. Fifth, red blood cell production is inversely correlated with total cell concentration, while elimination is a first-order process.
[0053] With the five assumptions described above for this kinetic model, the rate of change of glycated and non-glycated red blood cells can be modeled by differential equations 1 and 2. d[GRVdt=kgly[G][R]−kage[GR] (d[R]) / dt=kgen / C−kage[R]−kgly[G][R]
[0054] C is the total population of red blood cells, with C = [ff] + [GR] (equation 2a). C typically has the unit M (mol / L), [R] and [GR] typically have the unit M, and [G] typically has the unit mg / dl.
[0055] Assuming a steady state in which the glucose level is constant and the concentrations of glycated and non-glycated red blood cells remain stable (d[GR] / dt = (d[R]) / dt = 0), the following two equations can be derived. Equation 3 defines the apparent glycation constant K (typically in dL / mg) as the ratio of k gly and k age , while equation 4 establishes the relationship between the formation and elimination rates of red blood cells. K=kgly / kage=[GR] / [G][R] kgen / kage=C2
[0056] For the sake of simplicity, the following is k age used to describe the methods, devices, and systems of the present disclosure. Unless otherwise specified, k age by k gen be replaced. To k age by k gen To replace it, equation 4 would become k gen - k age * C rearranged.
[0057] HbA1c is the proportion of glycated hemoglobin, as shown in equation 5. HbA1c=[GR] / C=(C−[R]) / C
[0058] In a hypothetical situation where a person maintains the same glucose level indefinitely, the HbA1c in Equation 5 can be defined as "equilibrium HbA1c" (EA) (typically expressed as a percentage (e.g., 6.5%), but used in decimal form in the calculations (e.g., 0.065)). For a given glucose level, EA (Equation 6) can be derived from Equations 2a, 3, and 5. EA=(kgly[G]) / (kage+kgly[G])=[G] / (K−1+[G])
[0059] EA is an estimate of HbA1c based on a glucose concentration [G] that remains constant over a long period. This relationship provides an effective approximation of the average glucose and HbA1c for an individual with a stable day-to-day glucose profile. EA depends on K, the value of which is characteristic for each individual. Equation 6 indicates that stable glucose does not correlate linearly with EA. Stable glucose and EA can be approximated by a linear function within a specific range of glucose levels, but not across the entire typical clinical range of HbA1c. Furthermore, in reality, with continuous fluctuations in glucose levels, there is no reliable linear relationship between laboratory HbA1c and an individual's average glucose.
[0060] Others have also concluded this and produced kinetic models to correlate a measured HbA1c value with average glucose levels. For example, the American Diabetes Association has an online calculator to convert HbA1c values into estimated average glucose levels. However, this model is based on the assumption that k age and k gly that the results do not vary significantly between subjects, which proves to be false in the following example 1. Therefore, in the model currently used by the American Diabetes Association, k age and k gly considered as constants and not as varying from subject to subject.
[0061] A more recent model by Higgens et al. (Sci. Transl. Med. 8, 359ral30, 2016) was developed in which the assumption that the lifespan of red blood cells is constant was removed. However, the newer model still assumes that k glyThere was no significant variation between the subjects.
[0062] In contrast, both k age as well as k gly Variables for the kinetic models described here. In addition, k gly a subject's data in some embodiments is used to derive personalized parameters relating to the subject's diabetic condition and treatment (e.g., medication dosage, supplement dosage, exercise plan, diet / meal plan, and the like).
[0063] Continuing with the kinetic model of the present disclosure, the HbA1c value (HbA1c) can be determined. t ) at the end of a time interval t (equation 7) can be derived from equation 1 given initial HbA1c (HbA1co) and assuming a constant glucose level [G] during the time interval. HbA1ct=EA+(HbA1c0−EA)∗e−(kgly[G]+kage)t
[0064] To account for changes in glucose levels over time, each person's glucose profile is approximated as a series of time intervals t with the corresponding average glucose levels [G,]. By recursively applying equation 7, HbA1c z at the end of the time interval t z can be expressed by equation 8 for numerical calculations. HbA1cz=EAz(1−Dz)+∑i=1z−1[EAi(1−Di)∏j=i+1zDj]+HbA1c0∏j=1zDj
[0065] When solving k age and k gly Using equations 6, 7 or 8, k age and k gly be limited to reasonable physiological limits, as a non-restrictive example to 5.0*10 6 dl_*mg ^Tag - 1 < k gly <8.0*10 6 dl_*mg ^Tag -1 and 0.006 day 1 < k age <0.024 day -1Additionally or alternatively, an empirical approach can be used with the Broyden-Fletcher-Goldfarb-Shanno algorithm with estimated initial values for k. gly and k age used (e.g. k gly =4.4*10- 6 dl_*mg ^Tag 1 and k age =0.0092 days x The more data points available for glucose levels and measured data points for HbA1c, the more accurate the physiological parameters described here will be.
[0066] The value for the time interval t can be selected (e.g., by a user or developer, or by software instructions executed on one or more processors) based on a number of factors that may vary between implementations, and thus the value of the time interval t can vary. One such factor is the time interval between a glucose data value (e.g., a measured glucose level at a discrete time, a value representative of the glucose level over a specific time period across several discrete time points, or another) and another value in the individual's glucose history. This time interval between glucose data values can be called the time interval t. g The time interval t g The glucose profile can vary from person to person, so that a single glucose profile can contain a number of different values for the time interval t. gcan exhibit numerous example implementations, which lead to different values for the time interval t. g The methods described here are used. In some embodiments of glucose monitoring systems, glucose data points are recorded after a fixed time interval t. g (e.g., every minute, every ten minutes, every fifteen minutes, etc.) is determined, and the resulting glucose profile is a series of glucose data points, where each point represents the glucose at the end of or over the fixed time interval t. g represented (e.g., a series of glucose data points at one-minute intervals, etc.).
[0037] In other embodiments, glucose data points are represented at several different fixed time intervals t grecorded or determined. In some flash analytical monitoring systems (which are described in more detail here), for example, a user can request glucose data from a device (e.g., a sensor control device) that records glucose data within a recent time period (e.g., the last fifteen minutes, the last hour, etc.) at an initial, relatively short time interval t. g (e.g. every minute, every two minutes) is stored, and all other data (in some cases up to a maximum of eight hours, twelve hours, twenty-four hours, etc.) outside this recent time period are stored in a second, relatively longer time interval t. g (e.g., every ten minutes, every fifteen minutes, every twenty minutes, etc.). The data stored in the second, relatively longer time interval can be derived from the data originally stored at the relatively shorter time interval t. gThe recorded data (e.g., an average, median, or other algorithmically determined value) can be used to determine the glucose profile. In such an example, the resulting glucose profile depends on how often a user requests glucose data and can be a combination of several glucose data points from the first time interval t. g and others in the second time interval t g It could be. Of course, more complex variants are also possible, for example with three or more time intervals t. g In some embodiments, glucose data may also be available that were collected with additional ad-hoc measurements (e.g., with a finger prick and a test strip), leading to even greater variations in the time interval t. g can lead to this.
[0067] An example analysis performed on glucose profiles for a sample of subjects (approximately 400), where glucose data points were generally recorded at time intervals t gThe report, which indicated that a value for the time interval t in the range of three hours (or approximately three hours) to twenty-four hours (or approximately twenty-four hours) could be selected without significant loss of accuracy, was available for a range of one to fifteen minutes. In general, shorter time intervals t resulted in higher accuracy than longer ones, and values for time intervals t closer to three hours were the most accurate. For the time interval t, values below three hours may be prone to accuracy loss due to numerical rounding errors. These rounding errors can be reduced by using longer sequences of digits, but this comes at the cost of increased processing load and computation time. It is noted that other values for the time interval t outside the range of 3 to 24 hours may also be suitable, depending on the desired levels of accuracy and other factors, such as the mean time interval t.g between glucose data points.
[0068] Another factor in selecting the time interval t is the presence of gaps or missing data in the person's glucose profile, where the gaps are longer or significantly longer than the longest time interval t. gThe presence of one or more such gaps can potentially distort the results. These gaps can arise, for example, because no glucose data could be collected over a specific period (e.g., because the user was not wearing a sensor, the user forgot to query the sensor for data, an error occurred, etc.). The presence of gaps and their duration should be considered when selecting the time interval t. In general, the number and duration of gaps should be minimized (or eliminated) whenever possible. However, since it is often difficult to eliminate gaps of this kind, if such gaps exist, the selected time interval t should, in many embodiments, be at least twice the duration of the largest (maximum) gap between glucose data points.For example, if the time interval t is selected as 3 hours, the maximum gap should not be longer than 90 minutes; if the time interval t is selected as 24 hours, the largest gap should not be longer than 12 hours, and so on.
[0069] The HbA1c value z This is the estimated HbA1c of the present kinetic model, referred to here as cHbA1c (calculated HbA1c) to distinguish it from the other eHbA1c described here.
[0070] As previously described and shown in Equation 8, both EA and D are influenced by the glucose level [G,], k gly and k age influenced. Additionally, D depends on the length of the time interval t. Equation 8 is the recursive form of Equation 7. Equations 7 and 8 describe the relationship between HbA1c, glucose levels, and the individual kinetic constants of red blood cells k. gly and k age .
[0071] k age can be measured directly using expensive and complex methods. Here, the kinetic model is extended to include reticulocyte maturation as a method for estimating k. age to include.
[0072] Reticulocytes are immature red blood cells and typically make up about 1% of the total red blood cell count. The rate at which reticulocytes mature into mature red blood cells is variable. mat (typically in units of day -1 ). The maturation half-life for a normal reticulocyte is approximately 4.8 hours, from which equation 9 is derived. kmat=In2 / (4.8 hours)=3.47 days−1
[0073] The kinetic model is based on two assumptions: (1) all red blood cells are reticulocytes at time 0 and (2) reticulocytes are not eliminated (that is, reticulocytes mature into mature red blood cells and do not die). The probability density of reticulocyte age (PRET) can be represented by Equation 10. pRET(τ)=(kage / (1−ln2))∗e−kmat∗τ where t is the cell age.
[0074] The reticulocyte production index (RPI), also known as the corrected reticulocyte count (CRC), is the percentage of reticulocytes among all red blood cells. Therefore, the RPI is the integral of PRET over cell age, as shown in Equation 11, where RPI is the decimal form of the reported RPI (e.g., a reported RPI of 2% in Equation 11 is equal to 0.02). RPI=∫0∞pRET(τ)dτ=kage / (kmat∗(1−ln2))
[0075] Assuming that k mat typically 3.47 days-1 is, can k age RPI can be estimated from a measured RPI. RPI can be determined using standard methods. For example, RPI can be determined by measuring a percentage of hematocrit (HM). m ), by measuring a percentage of reticulocytes (RP) in an RNA-stained blood smear, by determining a maturation correction (MC) from the measured percentage of hematocrit, and by calculating the RPI based on Equation 12, where RP and HM m as percentages and not in decimal form (i.e., RP, which is given as 3%, is 3 in the equation and not 0.03).
[0076] Assuming that k mat Typically, 3.47 days can be considered normal. age RPI can be estimated from a measured RPI. RPI can be determined using standard methods. For example, RPI can be determined by measuring a percentage of hematocrit (HM). m), by measuring a percentage of reticulocytes (RP) in an RNA-stained blood smear, by determining a maturation correction (MC) from the measured percentage of hematocrit, and by calculating the RPI based on Equation 12, where RP and HM m as percentages and not in decimal form (i.e., RP, which is given as 3%, is 3 in the equation and not 0.03). RPI=(RP*HMn / HMn) / MC where HM n the normal hematocrit value is (typically 45).
[0077] Unless otherwise specified, the typical units described are assigned their respective values. A person skilled in the art would recognize other units and the correct conversions. For example, [G] is usually measured in mg / dL, but could be converted to M using the molar mass of glucose. If [G] is used in M, or if another variable with different units is used, the equations should be adjusted to account for the differences in units. Calculating physiological parameters from the kinetic model
[0078] Embodiments of the present disclosure provide a kinetic model of the glycation, elimination and formation of red blood cells as well as reticulocyte maturation in the body of a subject.
[0079] The physiological parameter k age can be estimated from one or more RPI measurements. Although k ageWhile the RPI can be estimated from a single measurement using Equation 11 above, two or more RPI measurements can increase the accuracy of the RPI value. Furthermore, the RPI can change over time in response to treatment and in response to improvement or worsening of a disease condition. Therefore, although the RPI can be measured at any time interval (e.g., weekly to annually), it is preferably measured once every three to six months.
[0080] As soon as k age Once calculated, the physiological parameters k gly and / or K can be estimated using the equations described here if at least one measured HbA1c value (also referred to as HbA1c level measurement) and several glucose levels (also referred to as glucose level measurements) are available over a period of time immediately before the HbA1c measurement.
[0081] Fig. 12 represents an exemplary timeline 100, which represents a collection of at least one measured HbA1c value 12102a, 12102b, 12102c, several glucose levels 12104a and 12104b and at least one measured RPI value 110a, 110b, 110c over the time spans 106 and 108.
[0082] The number of measured HbA1c values 12102a, 12102b, 12102c, which are used to calculate k gly The number of RPI values (110a, 110b, 110c) required for calculating k depends on the frequency and duration of the multiple glucose levels. age The required amount depends on the stability of the individual k mat and the deviation from typical k mat (3.47 days) -1 The RPI is preferably measured every three to six months, but can also be measured monthly or weekly if necessary.
[0083] In a first embodiment, a measured RPI value of 110b can be used to calculate k agecan be used, and a measured HbA1c of 12102 bpm can be used together with the calculated k age and several glucose measurements over a time period of 106 to calculate k gly and / or K can be used. Such embodiments are applicable for subjects with daily glucose measurements that are stable over a long period of time (e.g., over approximately 200 days). K can be calculated at time 101 using equation 6 by replacing EA with the measured HbA1c value and [G] with the daily average glucose over the period of time. gly can then be calculated from equation 3. Therefore, in this embodiment, an initial measurement of the HbA1c level 12102a is not strictly necessary.
[0084] Since no initial HbA1c value is measured, the time interval of 10⁶ of initial glucose level measurements with frequent measurements may need to be long to obtain an accurate representation of the average glucose and reduce error. Using more than 100 days with a stable glucose pattern for this procedure can reduce error. An additional duration, such as 200 days or more, or 300 days or more, further reduces error.
[0085] Embodiments in which a measured HbA1c value can be used include a time span of approximately 106 days to approximately 300 days (or longer), wherein the glucose level is measured at least approximately 72 times per day (e.g., approximately every 20 minutes) to approximately 96 times per day (e.g., approximately every 15 minutes) or more frequently. Furthermore, in such embodiments, the time between glucose level measurements can be reasonably consistent, with an interval between two glucose level measurements not exceeding approximately one hour. Some missing glucose measurement data is tolerable when only one measured HbA1c value is used. An increase in missing data may lead to a larger error.
[0086] Alternatively, in some cases where a measured HbA1c value is used, the time interval of 106 can be shortened if a subject has an existing glucose monitoring history with a stable, consistent glucose profile. For example, in a subject who has been tested for a longer period (e.g., 6 months or more), but perhaps less frequently or regularly, the existing glucose measurements can be used to establish and analyze a glucose profile. Then, if more frequent and regular glucose monitoring is performed over the time interval of 106 (e.g., approximately 72 to 96 times or more per day for approximately 14 days or more), followed by measurement of HbA1c and RPI, the four sets of data can be used in combination to determine one or more physiological parameters. g iy , k age , and / or K) to be calculated at time 101.
[0087] Alternatively, in some embodiments, one or more measured RPI values 110a, 110b, two measured HbA1c values (a first measured HbA1c value 12102a at the beginning of a time period 106 and a second measured HbA1c value 12102b at the end of the time period 106) and several glucose levels 12104a measured during the time period 106 can be used to determine one or more physiological parameters (k gly , k age and / or K) at time 101. In these embodiments, equation 11 can be used to calculate k. age to calculate, and equation 8 can be used to find k gly and / or K at time 101. In such embodiments, the multiple glucose levels 12104a can be measured over a period of about 10 days to about 30 days or longer, with the measurements being taken on average about 4 times daily (e.g. about every 6 hours) to about 24 times daily (e.g. about every 1 hour) or more frequently.
[0088] In the foregoing embodiments, the RPI value(s) can be measured at a different time than shown, since the measured RPI values are relatively stable over time. Therefore, the RPI value(s) can be measured at any time during the time span 106 and be applicable to these embodiments.
[0089] The foregoing embodiments are not limited to the time periods and frequency ranges of glucose level measurement provided as examples. Glucose levels can be measured over a period of approximately a few days up to approximately 300 days or more (e.g., approximately one week or more, approximately 10 days or more, approximately 14 days or more, approximately 30 days or more, approximately 60 days or more, approximately 90 days or more, approximately 120 days or more, and so on). In some embodiments, the period is 7 days or more, preferably one to ten months and less than one year. The frequency of such glucose level measurements can average approximately 14,400 times per day (e.g., a time interval t). g from about every 6 seconds) (or more frequently) to about 3 times daily (e.g. a time interval t) g approximately every 8 hours) (e.g. 1,440 times daily (e.g. a time interval t) g approximately every minute), about 288 times daily (e.g., a time interval t gapproximately every 5 minutes), about 144 times daily (e.g., a time interval t g approximately every 10 minutes), approximately 96 times daily (e.g., a time interval t g approximately every 15 minutes), approximately 72 times daily (e.g., a time interval t g approximately every 20 minutes), approximately 48 times daily (e.g., a time interval t g approximately every 30 minutes), approximately 24 times daily (e.g., a time interval t g approximately every 1 hour), about 12 times daily (e.g., a time interval t) g approximately every 2 hours), approximately 8 times daily (e.g., a time interval t g approximately every 3 hours), approximately 6 times daily (e.g., a time interval t) g approximately every 4 hours), approximately 4 times daily (e.g., a time interval t) g(approximately every 6 hours), and so on). In some cases, less frequent monitoring (such as once or twice daily) can be used, with glucose measurements taken at approximately the same time each day (within about 30 minutes) to allow for a more direct comparison of day-to-day glucose levels and to reduce errors in subsequent analyses.
[0090] The foregoing embodiments may further include the calculation of an error or uncertainty associated with one or more physiological parameters. In some embodiments, the error can be used to determine whether another HbA1c value (not shown) should be measured near time 101, whether one or more glucose levels 12104b should be measured (e.g., near time 101), whether the monitoring and analysis should be extended (e.g., to extend over the time interval 108 from time 101 to time 12103, which includes measuring glucose levels 12104b during time interval 108 and measuring the HbA1c value 12102c at time 12103), and / or whether the frequency of glucose level measurements 12104b in an extended time interval 108 should be increased relative to the frequency of glucose level measurements 12104a during time interval 106.In some embodiments, one or more of the aforementioned measures may be taken if the k. gly , k age and / or K-associated error is at or greater than about 15%, preferably at or greater than about 10%, preferably at or greater than about 7%, and preferably at or greater than about 5%. If a subject has a pre-existing medical condition (e.g., cardiovascular disease), a lower error may be preferred to allow for stricter monitoring and a lower error in the analyses described herein.
[0091] Alternatively, or if the error is acceptable, in some embodiments one or more physiological parameters (k gly , k ageand / or K) at time 101 to determine one or more parameters or characteristics for the personalized diabetes management of a subject (e.g., a cHbA1c at the end of time interval 108, a personalized glucose target range, and / or a treatment or change in treatment for the subject in the near future), each of which is described in more detail herein. In some cases, in addition to the above embodiments, an HbA1c value can be measured at time 12103, and the one or more physiological parameters can be recalculated and applied to a future time interval (not shown).
[0092] Alternatively or additionally, two values for k can be used. ageestimate using Equation 8 and Equation 11. A comparison of these two values can be used to determine whether another HbA1c value (not shown) should be measured near time point 101, whether one or more glucose levels 12104b should be measured (e.g., near time point 101), whether monitoring and analysis should be extended (e.g., to cover the time interval 108 from time point 101 to time point 12103, which includes measuring glucose levels 12104b and measuring the HbA1c value 12102c at time point 12103), and / or whether the frequency of glucose level measurements 12104b in an extended time interval 108 should be increased relative to the frequency of glucose level measurements 12104a during time interval 106. For example, if the two values of k ageIf the values differ by more than 10% (e.g., if the lower value is not within 10% of the higher value, based on the higher value), the k mat the person from the typical kmat (3.47 day -1 ) deviate. If a large difference is observed (e.g., a difference of more than 20%), the individual's kmat value can be determined. If the individual's kmat remains stable over a period of time (e.g., three to six months), the determined kmat value should be used instead of the typical kmat value in Equation 11 in the procedures, systems, and devices described herein. Fluctuations in kmat could indicate other health problems.
[0093] One or more physiological parameters and / or one or more parameters or characteristics for the personalized diabetes management of a subject can be measured and / or calculated and compared for two or more time points (e.g., time point 101 and time point 12103). For example, k glyThe cHbA1c can be compared at time 101 and at time 12103. In another example, the cHbA1c can be compared at time 12103 and at a future time. Some embodiments, which are further described herein, can use such comparisons to (1) monitor the progress and / or effectiveness of a subject's personalized diabetes management and optionally modify the subject's personalized diabetes management, (2) identify an abnormal or pathological physiological condition, and / or (3) identify subjects taking supplements and / or medications that affect red blood cell production and / or metabolism.
[0094] Each of the exemplary methods, devices, and systems described here can affect one or more physiological parameters (k gly , k ageand K) and perform one or more associated analyses (e.g., personalized glucose target range, personalized average glucose target, cHbA1c, and the like). The one or more physiological parameters (k gly , k age and K) and the associated analyses can be updated periodically (e.g., approximately every 3 months to annually). The frequency of updates may depend on factors such as the subject's glucose level and diabetes management (e.g., how well the subject remains within prescribed thresholds), other medical conditions, and the like. Other factors
[0095] In the embodiments described here, which include one or more physiological parameters (k gly , k ageand / or K), in addition to one or more physiological parameters, one or more other parameters specific to the subject may be used. Examples of parameters specific to the subject may include, but are not limited to, vital information (e.g., heart rate, body temperature, blood pressure, or other vital signs), body chemistry information (e.g., drug concentration, blood levels, troponin levels, cholesterol levels, or other body chemistry information), meal data / information (e.g., carbohydrate intake, sugar intake, or other information about a meal), activity information (e.g., occurrence and / or duration of sleep and / or exercise), an existing medical condition (e.g., cardiovascular disease, heart valve replacement, cancer, and systemic diseases such as…)autoimmune diseases, hormonal disorders and blood cell disorders), a family history of a medical condition, current treatment, age, race, sex, geographic location (e.g., where a subject grew up or where a subject currently lives), type of diabetes, duration of diabetes diagnosis and the like, as well as any combination thereof. Systems
[0096] In some embodiments, the determination of one or more physiological parameters (k gly , k age and / or K) for a subject using a system for analyzing physiological parameters.
[0097] Fig. Figure 13 presents an example of a system 211 for analyzing physiological parameters, providing an analysis of physiological parameters in accordance with some of the embodiments of the present disclosure. The system 211 for analyzing physiological parameters comprises one or more processors 212 and one or more machine-readable storage media 214. The one or more machine-readable storage media 214 contain a set of instructions for executing a routine for analyzing physiological parameters, which is executed by the one or more processors 212.
[0098] In some embodiments, the instructions include receiving inputs 216 (e.g., one or more RPI values, one or more glucose levels, one or more HbA1c levels, one or more physiological parameters (k gly , k ageand / or K), which were previously determined, or several other parameters specific to the subject, and / or one or more times assigned to one of the aforementioned), the determination of outputs 218 (e.g. one or more physiological parameters (k gly , k ageand / or K), an error associated with one or more physiological parameters, one or more parameters or properties for the personalized diabetes management of a subject (e.g., cHbA1c, a personalized glucose target range, an average glucose target, a supplement or drug dosage, among other parameters or properties), a matching group of participants, and the like), and communicating the outputs 218. In some embodiments, the communication of the inputs 216 may, for example, be via a user interface (which may be part of a display device), a data network, a server / cloud, another device, a computer, or any combination thereof.In some embodiments, the communication of output 218 can be made, for example, to a display device (which may be part of a user interface), a data network, a server / cloud, another device, a computer, or any combination thereof.
[0099] A “machine-readable medium,” as the term is used here, contains any mechanism capable of storing information in a form accessible to a machine (a machine could be, for example, a computer, network device, mobile phone, personal digital assistant (PDA), manufacturing tool, any device with one or more processors, and the like). For example, a machine-readable medium includes writable / non-writable media (e.g., read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and the like).
[0100] In some cases, the one or more processors 212 and the one or more machine-readable storage media 214 may be located in a single device (e.g., a computer, a network device, a mobile phone, a PDA, an analytical monitor, and the like).
[0101] In some embodiments, a system for analyzing physiological parameters may include other components. Fig. 14 presents another example of a system 311 for analyzing physiological parameters to provide an analysis of physiological parameters in accordance with some of the embodiments of the present disclosure.
[0102] System 311 for analyzing physiological parameters includes the health monitoring device 14320 with the subject interface 14320A and the analysis module 14320B. The health monitoring device 14320 is operationally coupled to, or can be coupled to, the data network 14322. System 311 for analyzing physiological parameters also includes a glucose monitoring device 324 (e.g., in vivo and / or in vitro (ex vivo) devices or system) and a data processing terminal / personal computer (PC) 326, each of which is operationally coupled to the health monitoring device 14320 and / or the data network 14322. Furthermore, in Fig. Figure 14 shows a server / cloud 328 which is operationally coupled to the data network 14322 for bidirectional data communication with one or more of the health monitoring device 14320, the data processing terminal / PC 326, and the glucose monitoring device 324. The system 311 for analyzing physiological parameters within the scope of this disclosure may not include one or more of the server / cloud 328, the data processing terminal / PC 326, and / or the data network 14322.
[0103] In specific embodiments, the analyzer module 14320B is programmed or configured to perform an analysis of physiological parameters and, optionally, other analyses (e.g., cHbA1c, personalized glucose target range, and others described herein). As shown, the analyzer module 14320B is a section of the health monitoring device 14320 (e.g., executed by a processor contained therein). However, the analyzer module 14320B can alternatively be associated with one or more of the server / cloud 328, the glucose monitoring device 324, and / or the data processing terminal / PC 326. For example, one or more of the server / cloud 328, the glucose monitoring device 324, and / or the data processing terminal / PC 326 can include a machine-readable storage medium (or media) containing a set of instructions that cause one or more processors to execute the set of instructions corresponding to the analyzer module 14320B.
[0104] Although the health monitoring device 14320, the data processing terminal / PC 326 and the glucose monitoring device 324 are shown to be operationally coupled to the data network 14322 for communication to / from the server / cloud 328, one or more of the health monitoring device 14320, the data processing terminal / PC 326 and the glucose monitoring device 324 may be programmed or configured to communicate directly with the server / cloud 328 and bypass the data network 14322.The mode of communication of the health monitoring device 14320, the data processing terminal / PC 326, the glucose monitoring device 324 and the data network 14322 includes one or more of wireless communication, wired communication, RF communication, BLUETOOTH® communication, WiFi data communication, RFID-enabled communication, ZIGBEE® communication or any other suitable data communication protocol, which optionally supports data encryption / decryption, data compression, data decompression and the like.
[0105] As described in more detail below, the analysis of physiological parameters can be performed by one or more of the health monitoring device 14320, the data processing terminal / PC 326, the glucose monitoring device 324 and the server / cloud 328, with the resulting analysis output being used collectively in the system 311 for the analysis of physiological parameters 311.
[0106] Additionally, although the glucose monitoring device 324, the health monitoring device 14320 and the data processing terminal / PC 326 are shown to be operationally coupled to each other via communication links, they can be modules within an integrated device (e.g. a sensor with a processor and a communication interface for sending / receiving and processing data). Measurement of glucose and HbA1c levels
[0107] The measurement of multiple glucose levels over different time periods, as described here, can be performed using in vivo and / or in vitro (ex vivo) methods, devices, or systems for measuring at least one analyte, such as glucose, in a body fluid, such as blood, interstitial fluid (ISF), subcutaneous fluid, skin fluid, sweat, tears, saliva, or another biological fluid. In some cases, in vivo and in vitro methods, devices, or systems can be used in combination.
[0108] Examples of in vivo methods, devices, or systems measure glucose levels and optionally other analytes in blood or intravascular fecal occult blood (ISF), wherein at least a portion of a sensor and / or sensor control device is or may be positioned within the body of a subject (e.g., under the skin surface of a subject). Examples of devices include, but are not limited to, continuous analyte monitoring devices and flash analyte monitoring devices. Specific devices or systems are further described herein and can be found in U.S. Patent No. 6,175,752 and U.S. Patent Application No. 2011 / 0213225, the entire disclosure of which is incorporated herein by reference for all purposes.
[0079] In vitro methods, devices, or systems (including those that are completely non-invasive) include sensors that come into contact with body fluid outside the body to measure glucose levels. For example, an in vitro system may use a measuring device that has a port for receiving an analytical test strip containing the subject's body fluid, which can be analyzed to determine the subject's glucose level in the body fluid. Additional devices and systems are described below.
[0109] As described above, the frequency and duration of glucose level measurements can vary from an average of about three times daily (e.g., about every 8 hours) to about 14,400 times daily (e.g., about every 10 seconds) (or more frequently) and from about a few days to over 300 days.
[0110] Once glucose levels are measured, they can be used to determine one or more physiological parameters (k gly , k age and / or K) and in some cases other analyses (e.g., cHbA1c, personalized glucose target range, and others described here). In some cases, such analyses can be performed using a system for analyzing physiological parameters. For example, in some embodiments, again based on Fig. 14 With reference to, the glucose monitoring device 324 shall comprise a glucose sensor coupled with electronics to (1) process signals from the glucose sensor and (2) communicate the processed glucose signals to one or more of the health monitoring device 14320, the server / cloud 328 and the data processing terminal / PC 326.
[0111] The measurement of one or more HbA1c levels at the various times described here can be performed using any suitable method. Typically, HbA1c levels are measured in a laboratory using a blood sample from a subject. Examples of laboratory tests include, but are not limited to, a chromatography-based assay, an antibody-based immunoassay, and an enzyme-based immunoassay. HbA1c levels can also be measured using electrochemical biosensors.
[0112] The frequency of HbA1c level measurements can vary from an average of monthly to annually (or less frequently if the subject's average glucose level is stable). Calculated HbA1c (cHbA1c)
[0113] Back on Fig. 14 By reference, in some embodiments, HbA1c levels can be measured using a laboratory test, the results being entered by the testing entity, a healthcare professional, the subject, or another user into the server / cloud 328, the subject interface 14320A, and / or a display device. The HbA1c levels can then be received by one or more of the health monitoring device 14320, the server / cloud 328, and the data processing terminal / PC 326 for analysis by one or more of the methods described herein.
[0114] After one or more physiological parameters (k gly , k age and / or K), multiple glucose measurements can be taken for a subsequent period and used to calculate HbA1c during and / or at the end of the following period. For example, again, Fig. 12. Referring to one or more physiological parameters (k gly , k age / and / or K) at time 101 based on one or more measured RPI values 110a, 110b, measurements of multiple glucose levels 12104a over time 106, a measured HbA1c level 12102b at the end of time 106, and optionally a measured HbA1c level 12102a at the beginning of time 106. Then, for a subsequent time 108, multiple glucose levels 12104b can be measured. Then, during and / or at the end of time 108, equation 8 can be used to determine a cHbA1c value (HbA1c). zfrom equation 8), where HbA1c is the measured HbA1c level 12102b at the end of time interval 106 (which is the beginning of time interval 108), [G,] are the glucose levels or the averaged glucose levels during time interval 108 (or the portion of time interval 108 in which cHbA1c is determined during time interval 108), and the provided one or more physiological parameters (k gly , k age and / or K) are used according to time 101.
[0115] A subject's cHbA1c can be measured for several consecutive time periods based on one or more physiological parameters (k gly , k age and / or K) are determined using the most recently measured HbA1c level, the most recently measured RPI value(s), and the intervening glucose level measurements. The RPI value can be measured periodically (e.g., every 6 months up to one year) to determine k ageto recalculate. The most recent RPI value or an average of two or more RPI values can be used for the calculation. HbA1c can be measured periodically (e.g., every 6 months to one year) to recalculate one or more physiological parameters. The time between remeasuring the RPI value and the measured HbA1c may depend on (1) the consistency of glucose level measurements, (2) the frequency of glucose level measurements, (3) the diabetes history of a subject and their family, (4) the length of time since the subject's diabetes diagnosis, (5) changes in a subject's personalized diabetes management (e.g., changes in medications / dosages, diet, exercise, and the like), (6) the presence of an illness or disorder affecting k matvarious factors (e.g., anemia, bone marrow disease, genetic predisposition, immune system disorder, and combinations thereof) can influence HbA1c levels. For example, a subject with consistent glucose measurements (e.g., a [G] with a fluctuation of less than 5%) and frequent glucose measurements (e.g., continuous glucose monitoring) may measure HbA1c levels less frequently than a subject who has recently (e.g., within the last 6 months) changed the dosage of a glycation drug, even with consistent and frequent glucose measurements.
[0116] Fig. 15 states with reference to Fig. Figure 13 presents an example of a cHbA1c report that can be generated as output 218 by a System 211 for the Analysis of Physiological Parameters of this Disclosure. The example report shown includes a graph of the average glucose level over time. The report also includes the most recently measured RPI value (open circle), the most recently measured HbA1c level (cross), and the cHbA1c levels calculated by the System 211 for the Analysis of Physiological Parameters (asterisk). Although the most recently measured RPI value and the most recently measured HbA1c level are shown as having been measured on different days, both measurements can be taken during the same visit to a healthcare provider.
[0117] Two cHbA1c levels are displayed, but one or more cHbA1c levels can also be shown on the report, including a line that continuously tracks the cHbA1c. Alternatively, output 218 of System 211 for analyzing physiological parameters can display a single number for a current or last calculated cHbA1c, a table that includes the data from Fig. 15, or another report that provides at least a cHbA1c level to a subject, health care provider or the like.
[0118] In some cases, the cHbA1c can be compared to a previous cHbA1c and / or a previously measured HbA1c level to monitor the effectiveness of a subject's personalized diabetes management. For example, if a diet and / or exercise plan is implemented as part of a subject's personalized diabetes management, with all other factors (e.g., medications and other medical conditions) being equal, changes in cHbA1c compared to the previous cHbA1c and / or the previously measured HbA1c level can indicate whether the diet and / or exercise plan is effective, ineffective, or somewhere in between.
[0119] In some cases, the cHbA1c can be compared to a previous cHbA1c and / or a previously measured HbA1c level to determine whether another HbA1c measurement should be performed. For example, if the cHbA1c changes by 0.5 percentage points or more (e.g., from 7.0% to 6.5% or from 7.5% to 6.8%) compared to the previous cHbA1c and / or the previously measured HbA1c level without a significant change in the glucose profile, another HbA1c measurement can be tested.
[0120] In some cases, comparing the current cHbA1c with a previous cHbA1c and / or a previously measured HbA1c level can indicate whether an abnormal or pathological physiological condition is present. For example, if a subject has maintained a cHbA1c and / or a measured HbA1c level over a prolonged period, and if a change in cHbA1c is then identified without other obvious causes, the subject may have a new abnormal or pathological physiological condition. Evidence of this new abnormal or pathological physiological condition may be derived from one or more physiological parameters (k gly , k age and / or K). Details of abnormal or pathological physiological conditions relating to one or more physiological parameters are discussed further here. Personalized glucose target range
[0121] Typically, glucose levels in subjects with diabetes are preferably maintained in the range of 54 mg / dL to 180 mg / dL. However, the kinetic model described here (see Equation 6) shows that intracellular glucose levels depend on the physiological parameters k gly , k age and are dependent on Ki. Therefore, a measured glucose level may not reflect the actual physiological conditions in a subject. For example, a subject with a higher than normal Ki may glycate glucose more rapidly. Thus, a measured glucose level of 180 mg / dL may be too high for the subject and could potentially worsen the effects of the subject's diabetes in the long term. In another example, a subject with a lower Ki may glycate glucose more rapidly. glyGlucose is glycated to a lesser extent than normal. Accordingly, at a glucose level of 54 mg / dL, the subject's intracellular glucose level can be much lower, causing the subject to feel weak and, over a longer period, leading to hypoglycemia.
[0122] Using the accepted normal lower glucose limit (LGL) and the accepted normal upper HbA1c limit (AU), equations for a personalized lower glucose limit (GL) (equation 13) and a personalized upper glucose limit (GU) (equation 14) can be derived from equation 6.
[0123] GL = (LGL * ¾J) / / c ¾? Equation 13, where k re t^ of the k gly for a normal person and kjffi is the k gly of the subject. GU=AU / (K(I−AU))
[0124] Equation 13 is based on k glyEquation 14 is based on K, since the lower limit of a glucose range is based on an equivalent intracellular glucose level. Equation 14 is based on K, since the upper limit of a glucose range is based on an equivalent extracellular glucose level (e.g., the accepted upper limit of normal HbA1c).
[0125] The currently accepted values for the above are LGL=54 mg / dL, k g e^ = 6.2*10- 6 dL*mg - 1 *Day - 1 , and AU=0.08 (i.e., 8%). Using the currently accepted values, equations 15 and 16 can be derived. GL=3.35*104 Day−! / k GU=0.087 / K
[0126] Fig. Figure 16A presents an example of a method for determining a personalized glucose target range 16530. A desired intracellular glucose range 16532 (e.g., the currently accepted glucose range) with a lower limit 16534 and an upper limit 16536 can be determined using one or more specific physiological parameters (k gly , k age / and / or K) 16538 are personalized using Equation 13 and Equation 14, respectively. This results in a personalized lower glucose limit (GL) 16540 (Equation 13 ± 7%) and a personalized upper glucose limit (GU) 16542 (Equation 14 ± 7%), which define the personalized glucose target range 16530. After one or more physiological parameters (k) are determined, the personalized upper glucose limit (GL) is determined. gly , k ageOnce the values calculated using equations 1 and / or K) have been determined, a personalized glucose target range can be established in which the lower glucose limit according to equation 13 (or equation 15) can be modified by ±7% and / or the upper glucose limit according to equation 14 (or equation 16) can be modified by ±7%. The ±7% with respect to each of the aforementioned calculated values allows for the use of a different value that is substantially close to the calculated value, thus preserving the personalized nature of the personalized glucose target range 16530. Alternatively, the ±7% can also be ±10%, ±5%, or ±3%.
[0127] For example, a test subject with a K of 4.5*10 ~4 dL / mg and a k gly of 7.0*10 6 dL*mg - 1 *Day 1They have a personalized glucose target range of approximately 48±3.4 mg / dl to approximately 193±13.5 mg / dl. Therefore, the subject may have a wider range of acceptable glucose levels than the currently practiced glucose range.
[0128] Fig. Section 16B, referring to Fig. Figure 13 presents an example of a personalized glucose target range report that can be generated as output 218 by a system 211 for analyzing physiological parameters of the present disclosure. The example report shown includes a graph of the glucose level over one day in relation to the previous personalized glucose target range (area between the dashed lines). Alternatively, but not limited to, other reports may include an ambulatory glucose profile (AGP), a numerical display of the personalized glucose target range with the most recent glucose measurement, and the like, as well as any combination thereof.
[0129] In another example, a test subject with a K of 6.5*10 -4 dL / mg and a k gly of 6.0*10 6 dL*mg - 1 *Day 1They have a personalized glucose target range of approximately 56 ± 3.5 mg / dL to approximately 134 ± 10 mg / dL. With the significantly reduced upper limit for glucose levels, the subject's personalized diabetes management may include more frequent glucose measurements and / or medication to remain essentially within the personalized glucose target range.
[0130] In yet another example, a test subject with a K of 5.0*10 -4 dL / mg and a k gly of 5.0*10 -6 dL*mg - 1 *This subject has a personalized glucose target range of approximately 67±4.5 mg / dL to approximately 174±12 mg / dL. This subject is more sensitive to lower glucose levels and may experience symptoms such as weakness, hunger, dizziness, etc., more frequently if the currently used glucose range (54 mg / dL and 180 mg / dL) were used.
[0131] Although the preceding examples all include a personalized lower glucose limit and a personalized upper glucose limit, a personalized glucose target range can alternatively include only the personalized lower glucose limit or the personalized upper glucose limit and use the currently practiced lower or upper glucose limit as the other value in the personalized glucose target range.
[0132] The personalized glucose target range can be determined and / or implemented in a system for analyzing physiological parameters. For example, a set of instructions or a program associated with a glucose monitoring device and / or health monitoring device that determines a therapy (e.g., an insulin dose) may use a personalized glucose target range in such an analysis. In some cases, a display device or a subject interface with a display device may show the personalized glucose target range.
[0133] The personalized glucose target range can be updated over time if one or more physiological parameters are recalculated. Personalized target for average glucose
[0134] In some cases, a patient's personalized diabetes management may include an HbA1c target value for a future time. For example, with reference to Fig. 12. A subject has a measured RPI value of 110b and a measured HbA1c value of 12102b at time point 101, and several glucose level measurements prior to that over time period 106. The subject's personalized diabetes management may include an HbA1c target value (AT) for time point 12103, which would correlate with improved health for the subject. Equation 17 can be used to calculate a personalized target for mean glucose (GT) for the next time period 108, based on the subject's HbA1c target value (AT) and calculated K at time point 101. GT=AT / (K(I−AT))
[0135] In some embodiments, a physiological parameter analysis system can determine an average glucose level for the subject over time (108) and, in some cases, display the average glucose level and / or the target average glucose level. The subject can use the current average glucose level and the target average glucose level to monitor their progress over time (108). In some cases, the current average glucose level can be transmitted (periodically or regularly) to a healthcare provider using a physiological parameter analysis system for monitoring and / or analysis.
[0136] Fig. 17 states with reference to Fig. Figure 13 presents an example of a personalized average glucose target report that can be generated as output 218 by a system 211 for analyzing physiological parameters of the present disclosure. The example report shown includes a graph of a subject's average glucose level (solid line) over time and the personalized average glucose target (shown at 150 mg / dL, dashed line). Alternatively, but not limited to, other reports may include a numerical display of the personalized average glucose target with the subject's average glucose level over a given time frame (e.g., the last 12 hours), and the like, and any combination thereof.
[0137] The personalized target for average glucose can be updated over time if one or more physiological parameters are recalculated. Examples
[0138] Data from 148 type 2 and 139 type 1 participants who had taken part in two previous clinical trials, in which glucose was continuously monitored for six months, were analyzed. Only 90 participants had sufficient data to meet the assumptions of the kinetic model described above and had uninterrupted continuous glucose data of 12 hours or more. Three HbA1c measurements were taken from the study participants: on days 1, 100 (±5 days), and 200 (±5 days), as well as frequent monitoring of subcutaneous glucose throughout the analysis period. This allowed for the analysis of two independent data sets (days 1–100 and days 101–200) for each participant.
[0139] The first data segment (days 1-100) was used for the numerical estimation of individual k gly and k age This allows for the prospective calculation of the final cHbA1c of the second data period (days 101–200). This final cHbA1c can be compared with the observed final cHbA1c to validate the kinetic model described here. For comparison, an estimated HbA1c for the second data period was calculated based on (1) the 14-day mean and (2) the weighted 14-day mean glucose, which were converted using the accepted regression model from the Ale-Derived Average Glucose (ADAG) study, both assuming that k gly a constant, which, as already discussed, is the currently accepted method for linking HbA1c and glucose measurements.
[0140] Fig. Figures 18A-C present a comparison between laboratory HbA1c levels on day 200 (±5 days) and estimated HbA1c values. The eHbA1c values in Figure 18A were calculated using the 14-day mean model, the eHbA1c values in Figure 18B were calculated using the weighted 14-day mean model, and the cHbA1c values in Figure 18C were calculated using the kinetic model described herein (Equation 8). The solid line in all figures represents the linear regression of the HbA1c comparison values for the respective models. The dashed line is a one-to-one relationship, with the model being better the closer the linear regression is to the solid line. The kinetic model described here clearly models the data better, which shows that k age and k glyare individualized, which is a new approach to correlating HbA1c with glucose measurements.
[0141] Fig. Figure 19 presents the data of an exemplary study participant, including measured glucose levels (solid line), HbA1c laboratory measurements (open circles), cHbA1c model values (long dashed line), and 14-day eHbA1c model values (dotted line). The cHbA1c model values in Fig. 19 were determined using the physiological parameters (k age and k gly The physiological parameters were calculated based on the first two HbA1c laboratory measurements and the glucose levels measured between these two measurements. The 14-day eHbA1c values are 14-day moving averages of glucose levels during the study.
[0142] The example of Fig. Figure 19 illustrates the dynamic nature of the relationships between glucose and cHbA1c, as well as glucose and eHbA1c. Additional examples were determined for study participants with type 1 and type 2 diabetes over a range of prediction errors: the 25th, 50th, and 75th percentiles for the cHbA1c method. In these examples, the mismatch between cHbA1c and the 14-day mean glucose value indicates the exaggerated amplitude of variation inherent in the simple 14-day method.
[0143] Fig. Figure 20 shows the relationship between constant glucose and equilibrium HbA1c, (1) as determined using the standard conversion of HbA1c to estimated mean glucose (dashed line with error bars), and (2) as measured for the 90 participants (solid lines). These individual curves (solid lines) represent the agreement of mean glucose with the laboratory measurement of HbA1c, provided their mean glucose level remains stable over days to weeks. The model suggests that the glucose-to-HbA1c ratio is not constant, with larger changes in glucose required to achieve the same change in HbA1c when the values of the latter marker increase.In contrast to previous assessments of the glycation index, the kinetic model presented in this disclosure suggests that an individual's glycation index is not constant across all HbA1c levels. Unlike eHbA1c, a key advantage of cHbA1c is its ability to account for individual differences in glycation. Individuals with low K values are "low glycators" and, for a given HbA1c level, exhibit higher average glucose levels, while the opposite is true for individuals with high K values.
[0144] Using the kinetic model of the present disclosure, it is possible to Fig. 21 A relationship between K (dL / mg) and the target average glucose level (mg / dL) is presented for varying HbA1c target values. That is, if a subject is targeting a specific HbA1c value (e.g., for a subsequent HbA1c measurement or cHbA1c estimation) and has a known K value (e.g., based on several measured glucose levels and at least one measured HbA1c), a target average glucose level for the subject can be derived and / or identified over the period in which the subject is targeting the HbA1c value.
[0145] Further details concerning methods, devices, and systems for determining physiological parameters related to the kinetics of glycation, elimination, and formation of red blood cells in the body of a subject are set forth in U.S. Patent Publication No. 2018 / 0235524 for Dunn et al., International Publication No. WO2020 / 086934 for Xu, International Publication No. WO2021 / 108419 for Xu, International Publication No. WO2021 / 108431 for Xu, U.S. Preliminary Patent Application No. 62 / 939,970, U.S. Preliminary Patent Application No. 63 / 015,044, U.S. Preliminary Patent Application No. 63 / 081,599, and U.S. Preliminary Patent Application No. 62 / 939,956, all of which are reproduced here in their original form. The entirety is included by reference.Such physiological parameters can be used, for example, to calculate personalized glucose metrics or personalized analyte measurements: among others, a more reliable calculated HbA1c (cHbA1c) or glucose-derived A1c (GD-A1c), adapted HbA1c (aHbA1c or personalized A1c), adapted cA1c (or cHbA1c adapted by k). age ) and / or a personalized glucose target range for personalized diagnoses, treatments and / or monitoring protocols.
[0146] For illustrative purposes, not as a limitation, the processor in the reader is configured to run the models described herein to calculate the physiological parameters and personalized glucose metrics. As shown here, the laboratory A1c measurement required to calculate the physiological parameters and personalized glucose metrics can be received by the reader, as an example and not as a limitation, using a camera (as an example, not as a limitation, such as one built into the reader) to scan a QR code containing the relevant laboratory A1c data. As shown here, the laboratory A1c measurement can also be received or retrieved by the reader from a cloud-based database.As explained here, a home test kit can be used to measure HbA1c in a blood sample and can be entered into the reader by the user instead of a laboratory HbA1c measurement.
[0147] A1c glucose discordance disrupts and impairs the supply of glucose to subjects. For example, as shown in Table 1, subjects A, B, and C have the same laboratory-measured A1c levels but different mean glucose levels (125 mg / dL, 154 mg / dL, and 188 mg / dL, respectively). Similarly, subjects B, D, and E have the same mean glucose level of 154 mg / dL but different laboratory-measured A1c levels (7.0%, 6.0%, and 8.0%, respectively). This information is presented in Fig. 22 graphically represented. Table 1 Proband Durchschnittliche Glukose (mg / dL) Labor-A1 c (%) A 125 7,0 B 154 7,0 C 188 7,0 D 154 6,0 E 154 8,0
[0148] The models described here allow for the quantitative removal of red blood cell artifacts, thereby improving the assessment of hyperglycemia risk. For example, and for illustrative purposes only, not as a limitation, subjects with AE can be considered with the following characteristics: Table 2 Proband RBC-Lebensdauer (Tage) Labor-A1 c (%) Personalisiertes A1c (%) A 123 7,0 6,0 B 87 7,0 8,4 C 110 7,0 6,7 D 89 6,0 7,1 E 121 8,0 6,9
[0149] As can be seen in Table 2, subjects A, B, and C have different RBC lifetimes (or measured in days (123, 87, and 110, respectively)), but the same laboratory-measured A1c of 7.0%. Based on the different RBC lifetimes, the personalized or adjusted A1c of subjects A, B, and C, as measured by the models described above, is 6, 8.4, and 6.7, respectively. Since the laboratory-measured A1c is the same for all three subjects, their respective healthcare providers can consider all three to be diabetic and prescribe the same treatment regimen based on these values. However, due to their different RBC lifetimes, their glycemic control is actually very different, as reflected in their significantly different personalized A1cs.In fact, based on their respective personalized A1c values, subject A is prediabetic (based on a personalized A1c of 6.0), subject B is clearly diabetic (based on a personalized A1c of 8.4), and subject C is also diabetic (based on a personalized A1c of 6.7). Accordingly, subjects A, B, and C may require different treatment regimens. Similarly, although subject D might be considered prediabetic based on a lab A1c of 6.0, they could be considered diabetic based on a personalized A1c of 7.1. Furthermore, subject E would be considered diabetic based on a lab A1c of 8.0, but prediabetic based on a personalized A1c of 6.9.
[0150] Fig. Figures 23-29 show exemplary case studies that illustrate the application of the models described here. For example, as shown in Fig. As shown in Figure 23, the exemplary subjects J17, J33, and J5 have measured mean glucose levels of 148 mg / dL, 149 mg / dL, and 153 mg / dL, respectively, and laboratory A1c values of 7.7%, 6.8%, and 8.1%, respectively. However, their personalized mean glucose and personalized mean A1c values, as determined using the models described here, differ considerably. Specifically, J17, J33, and J5 have personalized mean glucose levels of 141 mg / dL, 250 mg / dL, and 130 mg / dL, respectively, and laboratory A1c values of 6.7%, 9.5%, and 6.8%, respectively. In particular, the laboratory-measured glucose metrics of J33 differ significantly from her personalized glucose metrics. Fig. Figure 23 shows a graphical representation of these metrics. These and others in Fig. 23 of the metrics shown are also in Fig. See 24-29. Exemplary embodiments of sensor result interfaces
[0151] Fig. Figures 2D to 2l depict exemplary embodiments of sensor result interfaces or GUIs for analyte monitoring systems. In accordance with the disclosed subject matter, the sensor result GUIs described herein are configured to display analyte data and other health information via a user interface application (e.g., software) running on a reading device, such as a smartphone or a receiver as described with reference to Fig. 2B are described, are installed. Experts will also recognize that a user interface application with a sensor result interface or GUI can also be implemented on a local computer system or other computing device (e.g., wearable computing devices, smartwatches, tablet computers, etc.).
[0152] Referring to Fig. In 2D, the sensor result GUI 235 maps an interface that may include a first section 236, which displays a numerical representation of a current analyte concentration value (e.g., a current glucose value), a directional arrow to indicate an analyte trend direction, and a text description to provide contextual information, such as whether the user's analyte level is within range (e.g., "Glucose within range"). According to embodiments, the first section 236 may include a numerical representation of a personalized analyte concentration value (e.g., a personalized glucose value) as determined using a kinetic model as disclosed below. The first section 236 may also include a color or hue indicating an analyte concentration or trend. As described in Fig. As shown in Figure 2D, the first section 236, for example, is a green hue indicating that the user's analyte level (as an example, not a limitation, the current or personalized glucose level) is within a target range. In some embodiments, for example, a red hue may indicate an analyte level below a low analyte level threshold, an orange hue may indicate an analyte level above a high analyte level threshold, and a yellow hue may indicate an analyte level outside a target range. According to embodiments, the target range may be a personalized glucose target range determined using a kinetic model as disclosed below.
[0153] In addition, according to some embodiments, the sensor result GUI 235 also includes a second section 237 with a graphical representation of the analyte data. In particular, the second section 237 includes an analyte trend graph that reflects an analyte concentration, as shown by the y-axis, over a predetermined time period, as shown by the x-axis. According to embodiments, the second section 237 may include a personalized analyte trend graph that reflects a personalized analyte concentration, as determined using a kinetic model as disclosed below, as shown by the y-axis, over a predetermined time period, as shown by the x-axis. In some embodiments, the predetermined time period may be shown in five-minute increments, with the data comprising a total of twelve hours.However, experts will recognize that other time increments and durations of analyte data can also be used and are entirely within the scope of this disclosure. The second section 237 may also include a point 239 on the analyte trend chart to indicate the current analyte concentration value, a green-tinted area 240 to indicate an analyte target range, and two dotted lines 238a and 238b to indicate a high analyte threshold and a low analyte threshold, respectively. According to embodiments, point 239 in a personalized analyte trend chart may indicate the current personalized concentration value, the green-tinted area 240 to indicate a personalized analyte target range, and / or two dotted lines 238a and 238b to indicate a personalized high analyte threshold and a personalized low analyte threshold, respectively.According to some embodiments, the GUI 235 may also include a third section 241, which includes a graphical indicator and text information about the remaining lifespan of the sensor.
[0154] Next up: Fig. With reference to 2E, another example embodiment of a sensor result GUI 245 is shown. In accordance with the disclosed subject matter, the first section 236 is shown in a yellow shade to indicate that the user's current analyte concentration is not within a target range. According to embodiments, the current analyte concentration may include a current personalized analyte concentration and / or the target range may be a personalized target range as determined using a kinetic model as described herein. Additionally, the second section 237 includes: an analyte trend line 241, which may reflect the analyte level over time, and a current analyte data point 239 to indicate the current analyte concentration value (shown in yellow to indicate that the current value is outside the target range).According to embodiments, the analyte trend line 241 can contain personalized analyte level trends over a time, and the current analyte data point 239 can indicate a personalized analyte concentration value.
[0155] According to another aspect of the embodiments, the data on the sensor result GUI 245 are automatically updated or refreshed at an update interval (e.g., every second, every minute, every 5 minutes, etc.). For example, according to many of the embodiments, when analyte data is received by the reading device, the sensor result GUI 245 will update: (1) the current analyte concentration value shown in the first section 236, and (2) the analyte trend line 241 and the current analyte data point 239 shown in the second section 237. Furthermore, in some embodiments, the automatic updating of the analyte data may result in older analyte history data (e.g., in the left portion of the analyte trend line 241) no longer being displayed.According to embodiments, the current analyte concentration value may contain the current personalized current value, the analyte trend line 241 may contain the personalized analyte trend line 241, and the current analyte data point 239 may contain a current personalized analyte data point 239.
[0156] Fig. 2F is another example embodiment of a Sensor Result GUI 250. According to the illustrated embodiment, the Sensor Result GUI 250 includes a first section 236, shown in an orange hue, to indicate that the user's analyte levels are above a high glucose threshold (e.g., higher than 250 mg / dL). According to embodiments, the user's analyte levels shown may include a current personalized analyte concentration, and the high glucose threshold may include a personalized high glucose threshold. The Sensor Result GUI 250 also displays icons for 251 health information, such as an exercise icon or an apple icon, to reflect entries logged by the user indicating the times the user exercised or ate a meal.
[0157] Fig. 2G is another example embodiment of a sensor result GUI 255. According to the illustrated embodiments, the sensor result GUI 255 includes a first section 236, also shown in an orange hue, to indicate that the user's analyte levels are above a high glucose threshold. As discussed above, the user's analyte levels shown according to embodiments may include a current personalized analyte concentration, and the high glucose threshold may include a personalized high glucose threshold. As shown in Fig. 2G is shown, but the first section 236 does not report a numerical value, instead displaying the text "HI" to indicate that the current analyte concentration value is outside the upper limit of the glucose reporting range. Although in Fig. Since Figure 2G is not shown, those skilled in the art understand that, conversely, an analyte concentration below the lower limit of the glucose reporting range causes the first section 236 to display the text "LO" instead of a numerical value. According to embodiments, the first section 236 can display the text "HI" to indicate that the personalized analyte concentration value is outside an upper limit of the personalized glucose reporting range, and conversely, the first section 236 would display "LO" if the personalized analyte concentration is below a lower limit of the glucose reporting range.
[0158] Fig. 2H is another example embodiment of a Sensor Result GUI 260. According to the illustrated embodiments, the Sensor Result GUI 260 includes a first section 236, shown in a green color, to indicate that the user's current analyte level is within the target range. According to embodiments, the user's current analyte levels can include a current personalized analyte level, and the target range can include a personalized target range. Additionally, according to the illustrated embodiments, the first section 236 of the GUI 260 includes the text "Glucose is getting low," which can indicate to the user that their analyte concentration is predicted to fall below a predicted low analyte level threshold within a predetermined time period (e.g., predicted glucose will fall below 75 mg / dL within 15 minutes).Experts will understand that the Sensor Result GUI 260 can display a "Glucose is rising" message if a user's analyte level is set to rise above a predicted high analyte level threshold within a predetermined time period. According to embodiments, the analyte concentration value can include a personalized analyte concentration value, and the predicted low and high analyte levels can include personalized predicted low and high analyte values, respectively.
[0159] Fig. Figure 2l is another example embodiment of a sensor result GUI 265. According to the illustrated embodiments, the sensor result GUI 265 displays the first section 236 when a sensor error is present. In accordance with the disclosed subject matter, the first section 236 contains three dashed lines 266 instead of the current analyte concentration value to indicate that no current analyte value is available. According to embodiments, the current analyte concentration value may include a current personalized analyte concentration value. In some embodiments, three dashed lines 266 may indicate one or more error states, such as (1) a no-signal state; (2) a signal loss state; (3) a sensor too hot / too cold state; or (4) a glucose level not available state. Furthermore, the following are included in Fig. As can be seen in Figure 2l, the first section 236 displays a gray hue (instead of green, yellow, orange, or red) to indicate that no current analyte data (or current personalized analyte data) is available. Additionally, according to another aspect of the embodiments, the second section 237 can be configured to display the analyte history data in the analyte trend graph, even if an error condition exists that prevents the display of a numerical value for a current analyte concentration in the first section 236. According to embodiments, the analyte history data can include personalized analyte history data. As shown in Fig. 2l is shown, however, no current analyte concentration value data point is shown in the analyte trend diagram of the second section 237.
[0160] Fig. 2J is a glucose monitoring data interface containing a graphical representation of glucose monitoring data (right y-axis) for 200 days, overlaid with three laboratory HbA1c values (left y-axis) and the estimated HbA1c values (left y-axis) based on the 14-day eHbA1c model as disclosed in international publications WO2021 / 108419 for Xu and WO2020 / 086934 for Xu, which are incorporated herein in their entirety by reference. As shown, the estimated HbA1c derived from the 14-day HbA1c model exhibits very dramatic changes over time. However, it is unlikely that HbA1c can change that rapidly.
[0161] Fig. 2K is a glucose monitoring data interface that provides a graphical representation of Fig. 2J contains, superimposed with a calculated HbA1c (left y-axis) for the first 100 days, which was determined using k gly and kage in accordance with the procedures described in the international publications No. WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein in their entirety by reference.
[0162] Fig. 2L is a glucose monitoring data interface that provides a graphical representation of Fig. 2K contains, superimposed with the calculated HbA1c (extension from day 100 to day 200, left y-axis) for the following 100 days using k gly and k age , which were determined in relation to Fig. 2K according to the procedures described in international publications No. WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein in their entirety by reference. The third HbA1c value was not included in this procedure, but the described model predicted the measured value of the third HbA1c value, demonstrating that the model described here is in good agreement with reality. Example implementations of time-in-space interfaces
[0163] Fig. Sections 3A to 3F depict example implementations of GUIs for analyte monitoring systems. In particular, the Fig. 3A to 3F Time-in-range (also referred to as time-in-range and / or time-in-target) GUIs, each comprising multiple bars or bar segments, with each bar or bar segment indicating a period during which a user's analyte level is within a predefined analyte range correlated with the bar or bar segment. In some embodiments, the period may, for example, be expressed as a percentage of a predefined period. According to embodiments, as described below, the Fig. 3A to 3F also represent personalized time-in-ranges (also referred to as personalized time-in-target) GUIs, each comprising multiple bars or bar segments, where each bar or bar segment indicates a period of time during which a user's personalized analytical level is within a predefined personalized analytical range that correlates with the bar or bar segment.
[0164] Continue to Fig. 3A and Fig. Figure 3B shows an example embodiment of a time-in-ranges GUI 305, wherein the time-in-ranges GUI 305 comprises a "user-defined" time-in-ranges view 305A and a "standard" time-in-ranges view 305B, with a movable element 310 that allows the user to select between the two views. In accordance with the disclosed subject matter, the time-in-ranges views 305A and 305B can each comprise multiple bars, each bar indicating a duration during which a user's analyte level remains within a predefined analyte range correlated with the bar. According to embodiments, the user's analyte level can include a personalized analyte level.In some embodiments, the time-in-range views 305A, 305B further include a data range indicator 308, which shows relevant data associated with the multiple bars displayed, and a data availability indicator 314, which shows the time period(s) for which the analyte data are available for the analyte data displayed (e.g., "Data available for 7 out of 7 days").
[0165] Referring to Fig. 3A contains the "User-Defined" Time-in-Range View 305A, which includes six bars (from top to bottom): a first bar indicating that the user's glucose range is above 250 mg / dL for 10% of a predefined period; a second bar indicating that the user's glucose range is between 141 and 250 mg / dL for 24% of the predefined period; a third bar 316 indicating that the user's glucose range is between 100 and 140 mg / dL for 54% of the predefined period; a fourth bar indicating that the user's glucose range is between 70 and 99 mg / dL for 9% of the predefined period; and a fifth bar indicating that the user's glucose range is between 54 and 69 mg / dL for 2% of the predefined period. lies, and a sixth bar indicating that the user's glucose range is less than 54 mg / dL for 1% of the predefined period.Experts will recognize that the glucose ranges and percentage of time allocated to each bar can vary depending on the user-defined ranges and the user's available analytical data, and that the user's glucose range may include the user's personalized glucose range. Furthermore, experts will recognize that, although... Fig. 3A and Fig. 3B shows a predefined period of 314 of seven days, but other predefined periods may also be used (e.g. one day, three days, fourteen days, thirty days, ninety days, etc.) which fall entirely within the scope of protection of this revelation.
[0166] According to another aspect of the embodiments, the "User-Defined" Time-in-Range View 305A also includes a user-definable user-defined target range 312, which contains an activatable "Edit" link that allows a user to define and / or modify the user-defined target range. As shown in the "User-Defined" Time-in-Range View 305A, the user-defined target range 312 has been defined as a glucose range between 100 and 140 mg / dL and corresponds to the third bar 316 of the multiple bars. Those skilled in the art will also understand that in other embodiments, more than one range can be customized by the user, and such embodiments fall entirely within the scope of this disclosure. According to this embodiment, the user-defined target range 312 can include user-defined personalized target ranges.
[0167] Referring to Fig. 3B contains the “standard” time-in-ranges view 305A, which includes five bars (from top to bottom): a first bar indicating that the user’s glucose range is above 250 mg / dL for 10% of a predefined period, a second bar indicating that the user’s glucose range is between 181 and 250 mg / dL for 24% of the predefined period, a third bar indicating that the user’s glucose range is between 70 and 180 mg / dL for 54% of the predefined period, a fourth bar indicating that the user’s glucose range is between 54 and 69 mg / dL for 10% of the predefined period, and a fifth bar indicating that the user’s glucose range is less than 54 mg / dL for 2% of the predefined period.As with the "Custom" Time-in-Range View 305A, professionals will recognize that the percentage of time allocated to each bar can vary depending on the user's available analytical data. Additionally, according to embodiments, the user's glucose range can include the user's personalized glucose range, and the numerical glucose ranges assigned to the five bars can be customized for a user's personalized glucose range. As an example, and not as a limitation, personalized glucose ranges for each of the five bars can be calculated using models such as those disclosed below. However, unlike the "Custom" Time-in-Range View 305A, the glucose ranges displayed in the "Standard" View 305B cannot be customized by the user.
[0168] Fig. 3C and Fig. 3D represents another example implementation of the time-in-spaces GUI 320 with multiple views, 320A and 320B, which are analogous to the views in Fig. 3A and 3B, respectively. According to some embodiments, the Time-in-Range GUI 320 may further include one or more selectable symbols 322 (e.g., radio button, check box, slider, switch, etc.) that allow the user to select a predefined time period over which the user's analytical data is displayed in the Time-in-Range GUI 320. For example, as in Fig. 3C and Fig. As shown in 3D, selectable symbols 322 are used to select a predefined period of seven days, fourteen days, thirty days, or ninety days. Those skilled in the art will recognize that other predefined periods may be used and are entirely within the scope of this disclosure.
[0169] Fig. Figure 3E depicts an example embodiment of a Time-in-Target GUI 330, which can be visually output to a display device of a reading device (e.g., a dedicated reading device, a measuring device, etc.). In accordance with the disclosed subject matter, the Time-in-Target GUI 330 includes three bars, comprising (from top to bottom): a first bar indicating that the user's glucose range is above a predefined target range for 34% of a predefined period, a second bar indicating that the user's glucose range is within the predefined target range for 54% of the predefined period, and a third bar indicating that the user's glucose range is below the predefined target range for 12% of the predefined period.Experts will recognize that the percentage of time allocated to each bar can vary depending on the user's available analytical data, and that the user's glucose range may include the user's personalized glucose range. Furthermore, although... Fig. Figure 3E shows a predefined period 332, which is equal to the last seven days, and a predefined target range 334 of 80 to 140 mg / dL. Those skilled in the art will recognize that other predefined periods (e.g., one day, three days, fourteen days, thirty days, ninety days, etc.) and / or predefined target ranges (e.g., 70 to 180 mg / dL) can also be used and fall entirely within the scope of this disclosure. According to embodiments, the predefined target range can be a predefined personalized target range determined using a kinetic model as disclosed herein.
[0170] Fig. 3F illustrates another example implementation of a Time-in-Range GUI 340, comprising a single bar with five segments containing (from top to bottom): a first segment indicating that the user's glucose range is "very high" or above 250 mg / dL for 1% of a predefined period (14 minutes); a second segment indicating that the user's glucose range is "high" or between 180 and 250 mg / dL for 18% of the predefined period (4 hours and 19 minutes); a third segment indicating that the user's glucose range is within a "target range" or between 70 and 180 mg / dL for 78% of the predefined period (18 hours and 43 minutes); and a fourth segment indicating that the user's glucose range is within the target range for 3% of the predefined period. (34 minutes) is “low” or between 54 and 69 mg / dL, and a fifth bar segment,which indicates that the user's glucose range is "very low" or less than 54 mg / dL for 0% of the predefined period (0 minutes). As in , Fig. As shown in Figure 3F, according to some embodiments, the Time-in-Range GUI 340 can display text next to each bar segment indicating the actual time period, e.g., in hours and / or minutes. According to embodiments, the numerical values assigned to the five bars can be customized for a user's personalized glucose target range.
[0171] According to one aspect of the in Fig. In the embodiment shown in Figure 3F, each bar segment of the time-in-ranges GUI 340 can be a different color. In some embodiments, the bar segments can be separated by dashed or dotted lines 342 and / or marked with numerical labels 344 to indicate the ranges reflected by the adjacent bar segments. In some embodiments, the time in ranges reflected by the bar segments can also be shown as a percentage, as an actual period of time (e.g., 4 hours and 19 minutes), or, as shown in Figure 3F, as a range. Fig. Figure 3F shows how both are expressed. Furthermore, experts will recognize that the percentage of time allocated to each bar segment can vary depending on the user's analytical data. In some embodiments of the Time-in-Ranges GUI 340, the target range can be configured by the user. In other embodiments, the target range of the Time-in-Ranges GUI 340 cannot be modified by the user. In addition to the numerical markers, the Time-in-Ranges GUI 340 may also include target presets (e.g., "Target: > 70%" for the "Target" time-in-range), which can be preset or user-defined. The GUI 340 may also include text prompts that provide a user with guidance regarding the benefits or adverse effects of remaining in certain ranges. Example implementations of analyte level and trend warning interfaces
[0172] Fig. Figures 4A to 4O depict exemplary embodiments of analyte level / trend alert GULs for analyte monitoring systems. In accordance with the disclosed subject matter, the analyte level / trend alert GULs include an audio or visual message (e.g., prompt, warning, alarm, pop-up window, banner message, etc.), wherein the visual message includes an alarm condition, an analyte level measurement associated with the alarm condition, and a trend indicator associated with the alarm condition. According to one embodiment, the at least one processor is configured to output a message if at least one of the multiple personalized glucose metrics is at or above the corresponding multiple personalized glucose targets. The message may include an audio or visual message (e.g., prompt, warning, alarm, pop-up window, banner, etc.).
[0173] Continue to Fig. Figures 4A to 4C show exemplary embodiments of a high glucose alarm 410, a low glucose alarm 420, and a dangerously low glucose alarm 430, respectively, each alarm comprising a pop-up window 402 containing an alarm condition text 404 (e.g., "Low Glucose Alarm"), an analyte level measurement 406 (e.g., a current glucose level of 67 mg / dL) associated with the alarm condition, and a trend indicator 408 (e.g., a trend arrow or a direction arrow) associated with the alarm condition. In some embodiments, an alarm symbol 412 may be adjacent to the alarm condition text 404. According to embodiments, the analyte level measurement 406 may contain a personalized analyte level measurement (e.g., a current personalized glucose level of 67 mg / dL).
[0174] Next, referring to Fig. 4D to 4G are additional example implementations for low glucose alarms (440, 445), dangerously low glucose alarms (450), and high glucose alarms (455), respectively. As shown in Fig. Shown in 4D, the Low Glucose Alarm 440 resembles the Low Glucose Alarm in Fig. 4B (it includes, for example, a pop-up window containing alarm condition text, an analyte level measurement associated with the alarm condition, and a trend indicator associated with the alarm condition) also includes a warning symbol 442 to indicate that the alarm has been configured as a warning (e.g., it displays a warning, plays a sound, or vibrates, even if the device is locked or if the device's "Do Not Disturb" setting is enabled). Regarding Fig. 4E is similar to the low glucose alarm 445, which is similar to the low glucose alarm in Fig. 4B, but instead of a trend arrow, the logged glucose alarm 445 contains a text trend indicator 447. According to one aspect of some embodiments, the text trend indicator 447 can be enabled via the accessibility settings of a device, so that the device reads the text trend indicator 447 to the user via the device's text-to-speech feature (e.g., "Voiceover" for iOS or "Select-to-Speak" for Android).
[0175] Next, referring to Fig. 4F is similar to the 450 low glucose alarm in the low glucose alarm in the 450. Fig. 4D (which contains the alarm symbol), but instead of displaying an analyte level measurement associated with an alarm condition and a trend indicator associated with the alarm condition, the low glucose alarm 450 displays an out-of-range indicator 452 to indicate that the current glucose level is either above or below a predetermined reportable analyte level range (e.g., "HI" or "LO"). According to embodiments, the current glucose level may include a current personalized glucose level, and the predetermined reportable analyte level range may include a predetermined reportable personalized analyte level range. With respect to Fig. 4G's high glucose alarm is similar to the high glucose alarm in 455. Fig. 4A (which includes, for example, a pop-up window containing an alarm condition text, an analyte level measurement associated with the alarm condition, and a trend indicator associated with the alarm condition) further includes an instruction for the user 457. In some embodiments, the instruction may, for example, be a prompt for the user to “check blood glucose.” Those skilled in the art will recognize that other instructions or prompts may also be implemented (e.g., administer a correction bolus, eat a meal, etc.).
[0176] Furthermore, experts will also recognize that, although the Fig. 4A to 4G illustrate example implementation forms of analyte level / trend alert GULs that are displayed on smartphones with an iOS operating system, which analyte level / trend alert GULs can be implemented on other devices, including, for example, smartphones with other operating systems, smartwatches, body-worn devices, reading devices, tablet computer devices, blood glucose meters, laptops, desktops and workstations, to name just a few. Fig. For example, 4H to 4J represent sample implementations of a high glucose alarm, a low glucose alarm, and a dangerously low glucose alarm for a smartphone with an Android operating system. Similarly, the Fig. 4K to 4O each represent example implementations of a dangerously low glucose alarm, a low glucose alarm, a high glucose alarm, a dangerously low glucose alarm (with a blood glucose check symbol) and a high glucose alarm (with an out-of-range indicator) for a reading device. Example implementations of sensor usage interfaces
[0177] Fig. Figures 5A to 5F depict example implementations of sensor usage interfaces that are part of GUIs for analyte monitoring systems. In accordance with the disclosed subject matter, sensor usage interfaces provide technological enhancements that enable the quantification and promotion of user engagement with analyte monitoring systems. For example, the user may benefit from a subtle modification of behavior if the sensor usage interface motivates more frequent interaction with the device and the expected improvement in results occurs. The user may also benefit from more frequent interaction leading to an improvement in a number of metabolic parameters, as discussed in more detail below.
[0178] In some implementations, healthcare professionals (HCPs) can receive a report on user interaction frequency and a history of the patient's recorded metabolic parameters (e.g., estimated HbA1c levels, time spent in the 70-180 mg / dL range, etc.). If an HCP observes that specific patients are less engaged than others in their practice, they can focus their efforts on improving engagement among these less engaged users / patients. HCPs can benefit from more cumulative statistics (e.g., average glucose views per day, average pre / post-meal glucose views, average glucose views on days or at times of day when the patient is "in control" vs.Days or times when the user is "out of control" can be identified by recording the frequency of the user's interaction with the analyte monitoring system. This information can be used to understand why a patient may not be realizing the expected benefits of the system. If a healthcare professional (HCP) observes that a patient is not benefiting from the analyte monitoring system as expected, they may recommend a higher interaction level (e.g., increasing an interaction target level). Accordingly, an HCP may modify the predetermined interaction target level.
[0179] In some implementations, caregivers can receive a report on the user's interaction frequency. Conversely, caregivers can encourage the user to improve their interaction with the analyte monitoring system. Caregivers may be able to use the data to better understand and improve their level of engagement with the user's analyte monitoring systems or to adjust their treatment decisions.
[0180] According to some embodiments, a sensor usage interface may, for example, include the visual display of one or more "view" metrics, each of which can indicate a measure of the user's engagement or interaction with the analytical monitoring system. A "view" may, for example, be an instance in which a sensor results interface is rendered or brought to the foreground (e.g., in specific embodiments, to view one of the GUIs described herein). In some embodiments, with the update interval as described above, data on the sensor results GUI 245 is automatically updated or refreshed according to an update interval (e.g., every second, every minute, every 5 minutes, etc.). Thus, a "view" may comprise one instance per update interval in which a sensor results interface is rendered or brought to the foreground.For example, if the update interval is every minute, repeatedly rendering or bringing the Sensor Result GUI 245 to the foreground during that minute would only constitute one "view." Similarly, if the Sensor Result GUI 245 is continuously rendered or brought to the foreground for 20 minutes, the data on the Sensor Result GUI 245 would be updated 20 times (i.e., once per minute). However, this would only constitute 20 "views" (i.e., one "view" per update interval). Likewise, if the update interval is every five minutes, repeatedly rendering or bringing the Sensor Result GUI 245 to the foreground during those five minutes would only constitute one "view." If the Sensor Result GUI is continuously rendered or brought to the foreground for 20 minutes, this would constitute four "views" (i.e., one "view" for each of the four five-minute intervals).According to other embodiments, a "view" may be defined as an instance when a user views a sensor result interface with a valid sensor reading for the first time in a sensor lifecycle. According to disclosed embodiments, the user may receive a message, as described below, indicating when an instance of rendering or bringing the sensor result GUI to the foreground is not counted as a "view." For example, the user may receive a visual message indicating something like "Results have not been updated," "View does not count," or "Please check glucose level again." In some embodiments, the user may receive a check-in for each instance that counts as a "view," as described in more detail below.
[0181] According to disclosed embodiments, one or more processors can be configured to record no more than one instance of user operation of the reading device during a specific time period. As an example, and not to limit the possibilities, a defined time period can be one hour. A person skilled in the art would understand that a defined time period includes a suitable interval, such as one hour, two hours, three hours, 30 minutes, 15 minutes, etc.
[0182] According to some embodiments, a "view" may, for example, include a visual message (e.g., a prompt, a warning, an alarm, a pop-up window, a banner message, etc.). In some embodiments, the visual message may include an alarm condition, an analyte level measurement associated with the alarm condition, and a trend indicator associated with the alarm condition. For example, the analyte level / trend alert indicators, such as those in Fig. The embodiments shown in Figures 4A to 4O form a “view”.
[0183] In some embodiments, a sensor user interface may include a visual display of a "query" metric, which provides a further measure of the user's engagement or interaction with the analytical monitoring system. For example, a "query" may comprise an instance where a user employs a reading device (such as a smartphone, a dedicated reader, etc.) to query a sensor control device, such as a Flash analytical monitoring system. As described above in the context of "views," a "query" may comprise one instance per refresh interval when a user employs a reading device to query a sensor control device.
[0184] Fig. 5A and Fig. Figure 5B illustrates exemplary embodiments of the sensor usage interfaces 500 and 510, respectively. In accordance with the disclosed subject matter, the sensor usage interfaces 500 and 510 can be, for example, accessed by a mobile app or software located in the non-transient memory of the reading device 120, such as the one described in reference to Fig. 1 and Fig. 2A described, located, rendered, and displayed. In some embodiments, the software can record the date and time of the user's interaction with the system for each instance of a "view" or "query." In some embodiments, the software can record the current glucose value for each instance of a "view" or "query." Referring to Fig. 5A can include the sensor user interface 500: a predetermined time interval 508, which specifies a time period (e.g., a date range) during which view metrics are measured; a metric 502 for total views, which specifies a total number of views over the predetermined time interval 508; a metric 504 for views per day, which specifies an average number of views per day over the predetermined time interval 508; and a metric 506 for the percentage of time the sensor is active, which specifies the percentage of the predetermined time interval 508 during which the reading device 120 is in communication with the sensor control device 102, such as those referred to in Fig. 1, Fig. 2B and Fig. 2C are described. Referring to Fig. 5B can include the sensor user interface 510 a metric 504 for views per day and a metric 508 for the percentage of time the sensor is active, each measured for a predetermined time period 508.
[0185] According to another aspect of the embodiments, those skilled in the art will understand that, although the predetermined time interval 508 is shown to be one week, other predetermined time intervals (e.g., 3 days, 14 days, 30 days) can also be used. Additionally, the predetermined time interval 508 can be a discrete time interval—with a start date and an end date—as in the sensor usage interface 500 of Fig. 5A shown, or it can be a time span relative to a current day or time (e.g., "Last 7 days", "Last 14 days", etc.), as shown in the Sensor Usage Interface 510 of Fig. 5B shown.
[0186] Fig. Figure 5C depicts an example implementation of the sensor usage interface 525 as part of the analyte monitoring system report GUI 515. In accordance with the disclosed subject matter, the GUI 515 is a snapshot report covering a predetermined time period 516 (e.g., 14 days) and comprising several report sections on a single report GUI, which include: a sensor usage interface section 525; a glucose trend interface 517, which may contain a glucose trend graph, a graph of low glucose events, and other associated glucose metrics (e.g., glucose management indicator); and a health information interface 518, which displays user-logged information about the user's average daily carbohydrate intake and medication dosages (e.g.,The Health Information Interface 518 may contain insulin dosages; and a Comment Interface 519, which may contain additional information about the user's analyte and medication patterns presented in a narrative format. According to embodiments, the Health Information Interface 518 may contain a graphical representation of the average glucose level over a day relative to the aforementioned glucose target range (shown with horizontal lines at 80 and 180 mg / dL). The Glucose Trend Interface 517 may also include a percentage of the personalized A1C and / or one percent of the glucose variability. In some embodiments, the Health Information Interface 518 may be segmented to indicate the range in which a user falls. In some embodiments, the segmentation may, for example, be based on color.In particular, a low glucose range may be red, a good glucose range may be green, a high glucose range may be yellow, and a very high glucose range may be orange; however, a person skilled in the art will understand that other means of segmentation may also be possible. According to embodiments, the segmentations may be defined by a user or a healthcare provider. According to embodiments, the health information interface 518 may include a personalized glucose target range report, such as those disclosed in International Publication No. WO2020 / 086934 for Xu, which is incorporated herein in its entirety by reference. According to embodiments, the personalized glucose target range report may include a graphical representation of the glucose level over a day in relation to the preceding personalized glucose target range.According to another aspect of the embodiments, the sensor usage interface 525 can include a metric 526 for the percentage of time the sensor is active, a metric 527 for average queries / views (which, for example, indicates an average sum of the number of queries and the number of views), and a graph 528 for the percentage of time the sensor is active. As in . Fig. As can be seen in section 5C, one axis of the graph for the percentage of time the sensor is active can be aligned with a corresponding axis of one or more other graphs (e.g., graph for average glucose trend, graph for low glucose events), allowing the user to visually correlate data between multiple graphs from two or more sections of the report GUI through common units (e.g., time of day) of the aligned axes.
[0187] Fig. Figure 5D depicts an example implementation of another analytical monitoring system report GUI 530, which contains sensor usage information. In accordance with the disclosed subject matter, the GUI 530 is a monthly summary report that includes a first section comprising a legend 531, wherein the legend 531 contains several graphical symbols, each of which is placed next to a descriptive text. As in Fig. As shown in 5D, legend 531 contains a symbol and descriptive text for "average glucose," a symbol and descriptive text for "queries / views," and a symbol and descriptive text for "low glucose events." GUI 530 also includes a second section, which comprises a calendar interface 532. As shown in Fig. As shown in Figure 5D, the GUI 530, for example, includes a monthly calendar interface, where each day of the month can contain one or more symbols from an average glucose metric, symbols for low glucose events, and a sensor usage metric 532. In some embodiments, such as the one shown in Fig. As shown in Figure 5D, the sensor usage metric ("Query / View") provides a total of the number of queries and the number of views for each day. According to embodiments, an average glucose metric can also include a personalized average glucose metric.
[0188] Fig. Figure 5E depicts an exemplary embodiment of another analytical monitoring system report GUI 540, which contains sensor usage information. In accordance with the disclosed subject matter, the GUI 540 is a weekly summary report containing several report sections, each report section being representative of a different day of the week, and each report section comprising a glucose trend graph 541, which may contain the user's measured glucose levels over a 24-hour period, and a health information interface 543, which may contain information about the user's average daily glucose, carbohydrate intake, and / or insulin doses. In some embodiments, the glucose trend graph 541 may include sensor usage markers 542 to indicate that a query, a view, or both occurred at a specific time during the 24-hour period.According to embodiments, the glucose trend chart 541 can contain the user's personalized glucose levels over a 24-hour period. According to embodiments, the glucose trend chart 541 can include a personalized average glucose target report, which may contain a graphical representation of a subject's average glucose (shown by a solid line as an example, not limited to) over time and the personalized average glucose target. According to embodiments, the health information interface 543 can contain information about the user's personal average daily glucose.
[0189] Fig. Figure 5F depicts an exemplary embodiment of another analyte monitoring system report GUI 550, which contains sensor usage information. In accordance with the disclosed subject matter, the GUI 550 is a daily log report that includes a glucose trend graph 551, which may contain the user's glucose levels over a twenty-four-hour period. According to embodiments, the glucose trend graph 551 may contain the user's personalized glucose levels over a twenty-four-hour period. In some embodiments, the glucose trend graph 551 may include sensor usage markers 552 to indicate that a query, a view, or both occurred at a specific time during the twenty-four-hour period. The glucose trend graph 551 may also include logged event markers, such as...It includes logged carbohydrate intake markers 553 and logged insulin dosage markers 554, as well as glucose event markers, such as event markers 555 for low glucose.
[0190] According to certain embodiments, the Fig. 5A-F additionally contain the laboratory-measured HbA1c ("Laboratory A1c").
[0191] Fig. 5l to 5L represent various GUIs to improve usability and data protection in relation to analytical monitoring software. In Fig. 5G maps the GUI 5540 to a research consent interface 5540, which prompts the user to either decline or consent (via button 5542) regarding permission to use the user's analytical data and / or other product-related data for research purposes. According to embodiments of the disclosed subject matter, the analytical data can be anonymized (de-identified) and stored in an international database for research purposes.
[0192] Next, referring to Fig. 5H displays the GUI 5550 a “Vitamin C” warning interface 5550, which warns the user that daily use of more than 500 mg of vitamin C supplements may lead to falsely high sensor readings.
[0193] Fig. 5l is the GUI 5500, which represents an initial startup interface that can be displayed to a user upon first starting the analytical monitoring software. In accordance with the disclosed subject matter, the GUI 5500 may include a "Start Now" button 5502, which, when pressed, takes the user to the GUI 5510 of Fig. 5J forwards. The GUI 5510 maps a country verification interface 5512, which prompts the user to confirm their country. According to another aspect of the embodiments, the selected country can restrict and / or enable specific interfaces within the analytical monitoring software application for regulatory compliance purposes.
[0194] Continue to Fig. 5K's GUI 5520 provides an interface for creating a user account, enabling the user to initiate a process for creating a cloud-based user account. According to the disclosed subject matter, a cloud-based user account can allow the user to share information with medical professionals, family, and friends; utilize a cloud-based reporting platform to view more sophisticated analytical reports; and back up the user's sensor reading history to a cloud-based server. In some embodiments, GUI 5520 may also include a "skip" link 5522, which allows a user to use the analytical monitoring software application in a "no-account mode" (i.e., without creating or linking a cloud-based account).Selecting the "Skip" link 5522 may display an information window 5524 informing the user that certain functions are unavailable in "no account mode". The information window 5524 may also prompt the user to return to the GUI 5520 or to continue without creating an account.
[0195] Fig. 5L is a GUI 5530 that maps to a menu interface displayed in an analytical monitoring software application while the user is in "no-account mode". According to one aspect of the embodiments, the GUI 5530 includes a "Log in" link 5532 that allows the user to exit "no-account mode" and either create a cloud-based user account or log in with an existing cloud-based user account from within the analytical monitoring software application.
[0196] Experts will understand that all GUIs, reporting interfaces or sections thereof as described herein are for illustrative purposes only and that the individual elements or any combination of elements shown and / or described for a particular embodiment or figure are freely combinable with any elements or any combination of elements shown and / or described in relation to any of the other embodiments. Example implementation forms of digital interfaces for analyte monitoring systems
[0197] Here, example implementations of digital interfaces for analyte monitoring systems are described. In accordance with the disclosed subject matter, a digital interface can comprise a set of instructions, routines, subroutines, and / or algorithms, such as software and / or firmware, stored in non-transient memory, which are executed by one or more processors of one or more devices in an analyte monitoring system, wherein the instructions, routines, subroutines, or algorithms are configured to enable special functions and communication between devices.As a starting point, experts will understand that the digital interfaces described here may include instructions stored in a non-transient memory of a sensor control device 102, a reading device 120, a local computer system 170, a trusted computer system 180 and / or another device or system that is part of or communicates with the analyte monitoring system 100, as described in reference to . Fig. 1, Fig. 2A and Fig. 2B described. These instructions, when executed by one or more processors of the sensor control device 102, the reading device 120, the local computer system 170, the trusted computer system 180, or one or more devices or systems of the analyte monitoring system 100, cause the one or more processors to perform the procedure steps described herein. Those skilled in the art will further recognize that the digital interfaces described herein may be stored as instructions in the memory of a single central device or, alternatively, may be distributed among several discrete devices at geographically dispersed locations. Exemplary embodiments of data supplementation methods
[0198] Exemplary implementations of methods for data replenishment in an analyte monitoring system are now described. In accordance with the disclosed subject matter, gaps in the analyte data and other information can result from interruptions in the communication links between different devices in an analyte monitoring system 100. These interruptions can occur, for example, when a device is switched off (e.g., when a user's smartphone battery runs out) or when a first device temporarily moves out of range of wireless communication with a second device (e.g., when a user wearing the sensor control device 102 accidentally leaves their smartphone at home when going to work). As a result of these interruptions, the reading device 120 may be unable to receive analyte data and other information from the sensor control device 102.It would therefore be advantageous to have a robust and flexible data replenishment procedure in an analyte monitoring system to ensure that, once a communication link is restored, each analyte monitoring device can receive a complete data set as intended.
[0199] Fig. Figure 6A is a flowchart illustrating an exemplary embodiment of a method 600 for data replenishment in an analyte monitoring system. In accordance with the disclosed subject matter, the method 600 can be implemented to provide data replenishment between a sensor control device 102 and a reading device 120. In step 602, analyte data and other information are autonomously communicated between a first device and a second device at a predetermined interval. In some embodiments, the first device can be a sensor control device 102, and the second device can be a reading device 120, as described in [reference to Figure 6A]. Fig. 1, Fig. 2A and Fig. 2B described. In accordance with the disclosed subject matter, analyte data and other information may, but are not limited to, include one or more of the following: data indicating an analyte level in a body fluid, a rate of change of an analyte level, a predicted analyte level, a warning condition for a low or high analyte level, a sensor failure condition, or a communication link event. According to another aspect of the embodiments, autonomous communication at a predetermined interval may include the streaming of analyte data and other information according to a standard wireless communication protocol, such as a Bluetooth or Bluetooth Low Energy protocol, at one or more predetermined rates (e.g., every minute, every five minutes, every fifteen minutes, etc.).In some embodiments, different types of analyte data or other information can be autonomously communicated between the first and second devices at different rates (e.g., glucose trend data every 5 minutes, current glucose values every minute, etc.).
[0200] In step 604, a disconnection event or condition occurs, causing an interruption of the communication link between the first device and the second device. As described above, the disconnection event may be due to the second device's battery (e.g., the Reader 120, smartphone, etc.) being depleted or the second device being manually switched off by a user. The disconnection event may also be due to the first device being moved out of the second device's wireless communication range, a physical barrier blocking the first and / or second device, or anything else preventing wireless communication between the first and second devices.
[0201] In step 606, the communication link between the first device and the second device is re-established (e.g., the first device returns to the wireless communication range of the second device). After the link is re-established, the second device requests analyte history data according to the last "lifecount" metric for which data was received. In accordance with the disclosed subject matter, the lifecount metric can be a numerical value that is incremented and tracked on the second device in units of time (e.g., minutes) and indicates a period of time that has elapsed since the activation of the sensor control device. In some embodiments, for example, the second device (e.g., the reader 120, the smartphone, etc.), after establishing a wireless Bluetooth communication link with the first device (e.g., the smartphone), can...The second device, after the sensor control device 120 has restored the sensor control device, determines the last lifecount metric for which data was received. Then, according to some embodiments, the second device can send a request to the first device for analyte history data and other information whose lifecount metric is greater than the determined last lifecount metric for which data was received.
[0202] In some embodiments, the second device can send a request to the first device for analyte history data or other information associated with a specific lifecount range, instead of requesting analyte history data associated with a lifecount metric greater than a particular last lifecount metric for which data was received.
[0203] In step 608, after receiving the request, the first device retrieves the requested analyte history data from memory (e.g., the non-transient memory of the sensor control device 102) and then transmits the requested analyte history data to the second device in step 610. In step 612, after receiving the requested analyte history data, the second device stores the requested analyte history data in memory (e.g., in the non-transient memory of the read device 120). In accordance with the disclosed subject matter, when stored by the second device, the requested analyte history data can be stored together with the associated lifecount metric. In some embodiments, the second device can also output the requested analyte history data to a display device of the second device, such as a glucose trend graph of a sensor result GUI, as may be found, for example, in a glucose monitoring device.in the . Fig. 2D to 2l is described. In some embodiments, the requested analyte history data can be used, for example, to fill gaps in a glucose trend graph by displaying the requested analyte history data together with previously received analyte data.
[0204] Furthermore, experts will recognize that the data replenishment procedure can be implemented between multiple and different devices in an analyte monitoring system, with the devices communicating with each other via wired or wireless means.
[0205] Fig. Figure 6B is a flowchart illustrating another example implementation of Method 620 for data population in an analyte monitoring system. In accordance with the disclosed subject matter, Method 620 can be implemented to provide data population between a reading device 120 (e.g., a smartphone, a dedicated reading device) and a trusted computer system 180, such as a cloud-based reporting platform. In step 622, analyte data and other information are communicated between the reading device 120 and the trusted computer system 180 based on several upload triggers. In accordance with the disclosed subject matter, the analyte data and other information may, but are not limited to, include one or more of the following: data indicating an analyte level in a body fluid (e.g.,current glucose level, glucose history data), a rate of change of an analyte level, a predicted analyte level, an alarm condition for a low or high analyte level, user-logged information, information relating to the sensor control device 102, alarm information (e.g. alarm settings), wireless connection events and reader device settings, to name just a few.
[0206] According to another aspect of the embodiments, the multiple upload triggers may (but are not limited to) include one or more of the following: activating the sensor control device 102; user entry or deletion of a note or log entry; re-establishment of a wireless communication connection (e.g., Bluetooth) between the reader 120 and the sensor control device 102; change of alarm threshold; alarm presentation, update, or dismissal; re-establishment of internet connection; restart of the reader 120; receipt of one or more current glucose readings from the sensor control device 102; termination of the sensor control device 120; presentation, update, or dismissal of a signal loss alarm; turning the signal loss alarm on / off; viewing of the sensor result screen GUI; or user logging into the cloud-based platform.
[0207] According to another aspect of the embodiments, the reading device 120 can "mark" analyte data and other information to be transmitted to the trusted computer system 180 in order to track the transmission and reception of data between devices. In some embodiments, for example, upon receiving the analyte data and other information, the trusted computer system 180 can send a response to the reading device 120 to acknowledge that the analyte data and other information have been successfully received. The reading device 120 can then mark the data as successfully transmitted. In some embodiments, the reading device 120 can mark the analyte data and other information both before transmission and after receiving the response.In other embodiments, the analyte data and other information can be marked by the reading device 120 only after receiving the response from the trusted computer system 180.
[0208] Referring to Fig. 6B In step 624, a disconnection event occurs, causing an interruption of the communication link between the reader 120 and the trusted computer system 180. The disconnection event can occur, for example, if the user puts the reader 120 into "airplane mode" (e.g., disables the wireless communication modules), if the user turns off the reader 120, or if the reader 120 moves out of wireless communication range.
[0209] In step 626, the communication link between the reader 120 and the trusted computer system 180 (as well as the internet) is re-established, which is one of several upload triggers. Subsequently, based on the previously flagged analyte data and other information that was sent, the reader 120 determines the last successful data transmission to the trusted computer system 180. Then, in step 628, the reader 120 can transmit analyte data and other information that has not yet been received by the trusted computer system 180. In step 630, the reader 120 receives an acknowledgment of the successful receipt of analyte data and other information from the trusted computer system 180.
[0210] Although Fig. Since the data replenishment method described in Section 6B above relates to a reading device communicating with a trusted computer system, those skilled in the art will recognize that it can also be applied between other devices and computer systems in an analyte monitoring system (e.g., between a reading device and a local computer system, between a reading device and a medical delivery device, between a reading device and a wearable computer device, etc.). These embodiments, together with their variations and permutations, fall entirely within the scope of this disclosure.
[0211] In addition to data padding, exemplary implementations of methods for aggregating disconnection and reconnection events for wireless communication links in an analyte monitoring system are described. As per the disclosed subject matter, there can be numerous and far-reaching causes for interruptions of wireless communication links between different devices in an analyte monitoring system. Some causes may be technical in nature (e.g., a reader is located outside the wireless communication range of a sensor control device), while other causes may be related to user behavior (e.g., a user leaving their reader at home).To improve connectivity and data integrity in analyte monitoring systems, it would therefore be advantageous to collect information about separation and recovery events between different devices in an analyte monitoring system.
[0212] Fig. Figure 6C is a flowchart illustrating an exemplary embodiment of Method 640 for aggregating disconnect and reconnect events for wireless communication links in an analyte monitoring system. In some embodiments, Method 640 can, for example, be used to detect, log, and upload Bluetooth or Bluetooth Low Energy disconnect and reconnect events between a sensor control device 102 and a reader device 120 to the trusted computer system 180. In accordance with the disclosed subject matter, the trusted computer system 180 can aggregate disconnect and reconnect events transmitted by multiple analyte monitoring systems. The aggregated data can then be analyzed to determine whether conclusions can be drawn from it for improving connectivity and data integrity in analyte monitoring systems.
[0213] In step 642, analyte data and other information are transferred between the reading device 120 and the trusted computer system 180 based on several upload triggers, such as those previously described in relation to procedure 620 in Fig. As described in 6B, communication occurs in step 644, causing an interruption of the wireless communication link between the sensor control device 102 and the reader 120. Examples of disconnection events may include, but are not limited to, a user putting the reader 120 into "airplane mode", a user turning off the reader 120, the reader 120 running out of power, the sensor control device 102 moving out of the wireless communication range of the reader 120, or a physical barrier blocking the sensor control device 102 and / or the reader 120, to name just a few.
[0214] Still referring to Fig. In step 646, the wireless communication link between the sensor control device 102 and the reader 120 is re-established, which is one of several upload triggers. The reader 120 then determines a disconnect time and a reconnect time, where the disconnect time is the time the wireless communication link was interrupted and the reconnect time is the time the wireless communication link between the sensor control device 102 and the reader 120 is re-established. According to some embodiments, the disconnect and reconnect times can also be stored locally in an event log on the reader 120. In step 648, the reader 120 transmits the disconnect and reconnect times to the trusted computer system 180.
[0215] According to some embodiments, the disconnect and reconnect times can be stored in the non-transient memory of the trusted computer system 180, such as in a database, and aggregated with disconnect and reconnect times collected from other analyte monitoring systems. In some embodiments, the disconnect and reconnect times can also be transferred to and stored on a different cloud-based platform or server than the trusted computer system 180 that stores analyte data. In still other embodiments, the disconnect and reconnect times can be anonymized.
[0216] Additionally, experts will recognize that Method 640 can be used to collect the disconnection and reconnection time between other devices in an analyte monitoring system, including, for example: between the reading device 120 and the trusted computer system 180; between the reading device 120 and a body-worn computer device (e.g., a smartwatch or smart glasses); between the reading device 120 and a drug delivery device (e.g., an insulin pump or insulin pen); between the sensor control device 102 and a body-worn computer device; between the sensor control device 102 and a drug delivery device; and any other combination of devices within an analyte monitoring system.Experts will further recognize that the 640 method can be used to analyze disconnect and reconnect times for various wireless communication protocols, such as Bluetooth or Bluetooth Low Energy, NFC, 802.11x, UHF, cellular connectivity, or any other standardized or proprietary wireless communication protocol. Example implementations for improved transmission of expired / faulty sensors
[0217] Exemplary implementations of methods for improved transmission of expired and / or faulty sensors in an analyte monitoring system are now described. In accordance with the disclosed subject matter, conditions involving expired or faulty sensors, detected by a sensor control device 102, can trigger warnings on the reader 120. However, if the reader 120 is in "airplane mode," switched off, outside the wireless communication range of the sensor control device 102, or otherwise unable to communicate wirelessly with the sensor control device 102, then the reader 120 cannot receive these warnings. This can result in the user missing information, such as the need to replace a sensor control device 102 immediately.If no action is taken in the event of a detected sensor error, this can also lead to the user being unaware of unfavorable glucose conditions (e.g., hypoglycemia and / or hyperglycemia) due to a terminated sensor.
[0218] Fig. Figure 7C is a flowchart illustrating an exemplary embodiment of Method 700 for improved transmission of expired or faulty sensors in an analyte monitoring system. In accordance with the disclosed subject matter, Method 700 can be implemented to enable improved sensor transmissions by a sensor control device 102 after an expired or faulty sensor condition has been detected. In step 702, an expired or faulty sensor condition is detected by the sensor control device 102. In some embodiments, the sensor fault condition may include a sensor insertion fault condition and / or a sensor termination condition.According to some embodiments, a sensor insertion error condition or a sensor termination condition may, for example, but not be limited to, include one or more of: a detected FIFO overflow, a sensor signal below a predetermined insertion error threshold, moisture ingress detected, an electrode voltage exceeding a predetermined diagnostic voltage threshold, an early signal attenuation (ESA) condition, or a late signal attenuation (LSA) condition, to name just a few.
[0219] Referring again to Fig. In step 704, the sensor control device 102 stops acquiring measurements of the analyte levels from the analyte sensor in response to the detection of the sensor fault condition. In step 706, the sensor control device 102 begins transmitting a sensor fault condition indication to the read device 120, while simultaneously enabling the read device 120 to connect to the sensor control device 102 for data population. According to the disclosed subject matter, the transmission of the sensor fault condition indication may include the transmission of multiple Bluetooth or Bluetooth Low Energy (BLE) announcement packets, each of which may contain the sensor fault condition indication. In some embodiments, the multiple Bluetooth or BLE announcement packets may be transmitted repeatedly, continuously, or intermittently.Experts will recognize that other types of wireless broadcasting or multicasting of the sensor fault condition indication may also be implemented. According to another aspect of the embodiments, the reading device 120, in response to receiving the sensor fault condition indication, may visually display a warning or prompt the user for confirmation.
[0220] In step 708, the sensor control device 102 can be configured to monitor for a response or acknowledgment of receipt of the sensor fault condition indication from the reader device 120. In some embodiments, for example, a response or acknowledgment of receipt by the reader device 120 can be generated when a user dismisses a warning on the reader device 120 regarding the sensor fault condition indication or otherwise responds to a prompt to acknowledge the sensor fault condition indication. When a response or acknowledgment of receipt of the sensor fault condition indication is received by the sensor control device 102, the sensor control device 102 can enter either a memory state or an exit state in step 714.According to some embodiments, the sensor control device 102 is placed in a power-saving mode in the memory state, and the sensor control device 102 can be reactivated by a read device 120. In contrast, the sensor control device 102 cannot be reactivated in the termination state and must be removed and replaced.
[0221] If an acknowledgment for the error condition information is not received by the sensor control device 102, then in step 710 the sensor control device 102 will stop transmitting the error condition information after a first predetermined time interval. In some embodiments, the first predetermined time interval can be, for example, one hour, two hours, five hours, etc. Subsequently, in step 712, if an acknowledgment for the error condition information is still not received by the sensor control device 102, then in step 712 the sensor control device 102 will also stop allowing data replenishment after a second predetermined time interval. In some embodiments, the second predetermined time interval can be, for example, one of twenty-four hours, forty-eight hours, etc. The sensor control device 102 then enters a storage or termination state in step 714.
[0222] By enabling the sensor control device 102 to continue transmitting sensor fault conditions for a predetermined period of time, the embodiments of this disclosure reduce the risk of missed sensor fault warnings. Additionally, although the embodiments described above relate to a sensor control device 102 communicating with a reading device 120, those skilled in the art will recognize that sensor fault condition information can also be transmitted between a sensor control device 102 and other types of mobile computing devices, such as wearable computing devices (e.g., smartwatches, smart glasses) or tablet computing devices. Example implementation methods for data merging in analytical monitoring systems
[0223] Example implementations for procedures for merging data received from one or more analyte monitoring systems are now described. As already mentioned with reference to Fig. As described in section 1, a trusted computer system 180, such as a cloud-based platform, can be configured to generate various reports based on received analyte data and other information from multiple readers 120 and sensor control devices 102. However, a large and diverse population of readers and sensor control devices can introduce complexities and challenges in generating reports based on received analyte data and other information. For example, a single user may own multiple readers and / or sensor control devices, either concurrently or sequentially over time, each potentially containing different versions. This can lead to further complications, as groups of duplicate and / or overlapping data may exist for each user.It would therefore be advantageous to have procedures for combining data in a trusted computer system for the purpose of generating reports.
[0224] Fig. Figure 8A is a flowchart illustrating an example implementation of Method 800 for merging data associated with a user and generating one or more report metrics, wherein the data originates from multiple reading devices and multiple sensor control devices. In accordance with the disclosed subject matter, Method 800 can be implemented to merge analyte data to generate different types of report metrics for use in various reports. In step 802, the data are received from one or more reading devices 120 and combined for the purpose of merging. In step 804, the combined data are then deduplicated to remove historical data from multiple reading devices originating from the same sensor control device.In accordance with the disclosed subject matter, the data deduplication process may involve (1) identifying or assigning a priority to each reading device from which analyte data is received, and (2) in the event that duplicated data exists, retaining the data assigned to the reading device with a higher priority. For example, in some embodiments, a newer reading device (e.g., a newer model with a newer version of the software installed) is assigned a higher priority than an older reading device (e.g., an older model with an older version of the software installed). In some embodiments, the priority may be assigned according to device type (e.g., a smartphone has a higher priority than a dedicated reading device).
[0225] Still referring to Fig. In step 806, a determination is made as to whether one or more of the report metrics to be generated require the resolution of overlapping data. If this is not the case, a first type of report metric can be generated in step 808 based on deduplicated data without further processing. In some embodiments, the first type of report metric may, for example, include average glucose levels used in reports, such as a snapshot or a monthly summary report (as described in [reference to]). Fig. 5C and Fig. 5D described). If it is determined that one or more of the report metrics to be generated require the resolution of overlapping data, then a procedure for resolving overlapping data ranges is executed in step 810. A sample execution method for resolving overlapping data ranges is described below with reference to Fig. 8B described. Subsequently, in step 812, a second type of reporting metric is generated based on data that has been deduplicated and processed to resolve overlapping data segments. In some embodiments, the second type of reporting metric may, for example, include calculations of low glucose events that appear in reports such as the daily log report (as described in section 8B). Fig. 5F described), can be used.
[0226] Fig. Figure 8B is a flowchart illustrating an example implementation of Procedure 815 for resolving overlapping areas of analyte data, as described, for example, in step 810 of Procedure 800, as referred to in Fig. 8A described, can be implemented. In step 817, the deduplicated data from each reading device (resulting from step 804 of procedure 800, as described in section 804) can be read. Fig. (as described in Figure 8A) are sorted from earliest to newest. In step 819, the deduplicated and sorted data are then isolated according to a predetermined time interval based on the reporting metric to be generated. In some embodiments, if the reporting metric is, for example, a graph reflecting glucose values over a specific day, the deduplicated and sorted data for that specific day can then be isolated. Next, in step 821, contiguous portions of the deduplicated and sorted data are isolated for each reading device. In accordance with the disclosed subject matter, non-contiguous data points can be discarded or not considered (e.g., not used) to generate reporting metrics.In step 823, for each contiguous section of deduplicated and sorted data from a reader, a determination is made as to whether any overlapping regions exist with other contiguous sections of deduplicated and sorted data from other readers. In step 825, for each identified overlapping region, the deduplicated and sorted data from the higher-priority reader is retained. If, in step 827, it is determined that all contiguous sections have been analyzed according to the previous steps, procedure 815 terminates in step 829. Otherwise, procedure 815 returns to step 823 to continue identifying and resolving any overlapping regions between contiguous sections of deduplicated and sorted data for different readers.
[0227] Fig. Figures 8C through 8E are diagrams (840, 850, 860) that depict various stages of deduplicated and sorted data from multiple reading devices when the data is processed according to Method 815 for resolving overlapping data ranges. Initially referring to Fig. Diagram 8C depicts diagram 840 showing deduplicated and sorted data from three different reading devices: a first reading device 841 (as reflected by the round data points), a second reading device 842 (as reflected by the diamond-shaped data points), and a third reading device 843 (as reflected by the square data points). According to one aspect of diagram 840, the data are mapped in step 821 of procedure 815 after they have been deduplicated, sorted, and isolated to a predetermined time interval. As shown in Fig. As can be seen in Figure 8C, a contiguous data segment has been identified for each of the three reading devices (841, 842, and 843), and three tracks are shown. According to another aspect of diagram 840, non-contiguous points 844 are not included in the three tracks.
[0228] Next, referring to Fig. Diagram 850, shown in Figure 8D, depicts the data from the reading devices 841, 842 and 843 in step 823 of the method 815, identifying three overlapping areas between the contiguous data segments: a first overlapping area 851 between all three contiguous data segments; a second overlapping area 852 between two contiguous data segments (from reading device 842 and reading device 843); and a third overlapping area 853 between two contiguous data segments (also from reading device 842 and reading device 843).
[0229] Fig. 8E is a diagram 860 that maps data in step 825 of procedure 815, wherein a single track 861 indicates the merged, deduplicated, and sorted data from three read devices 841, 842, and 843 after overlapping areas 851, 852, and 853 have been resolved using the priority of each read device. According to diagram 860, the priority order from highest to lowest is: read device 843, read device 842, and read device 841.
[0230] Although the Fig. 8C, Fig. 8D and Fig. 8E, where three contiguous data segments are represented, and three discrete overlapping regions are identified, the person skilled in the art will understand that either fewer or more contiguous data segments (and non-contiguous data points) and overlapping regions are possible. For example, those skilled in the art will recognize that if a user has only two reading devices, there may be fewer contiguous data segments and overlapping regions, if any at all. Conversely, those skilled in the art will understand that if a user has five reading devices, there may be five contiguous data segments with three or more overlapping regions. Example designs for sensor transitions
[0231] Exemplary implementations of sensor transfer methods are now described. In accordance with the disclosed subject matter, as mobile computers and wearable technologies rapidly evolve and become increasingly ubiquitous, users are more likely to replace or upgrade their smartphones more frequently. Therefore, in the context of analyte monitoring systems, it would be advantageous to have sensor transfer methods that allow a user to continue using a previously activated sensor control device with a new smartphone. Additionally, it would also be advantageous to ensure that analyte history data could be transferred from the sensor control device to the new smartphone (and subsequently uploaded to the trusted computer system) in a user-friendly and secure manner.
[0232] Fig. Figure 9A is a flowchart illustrating an example implementation of Method 900 for transitioning a sensor control device. In accordance with the disclosed subject matter, Method 900 can be implemented in an analyte monitoring system to allow a user to continue using a previously activated sensor control device with a new reading device (e.g., a smartphone). In step 902, a user interface application (e.g., a mobile software application or app) is installed on the reading device 120 (e.g., a smartphone), which results in a new unique device identifier or "device ID" being generated and stored on the reading device 120. In step 904, after the app is installed and launched, the user is prompted to enter their user credentials to log in to the trusted computer system 180 (e.g., a smartphone).to log in to a cloud-based platform or server. An example implementation of a GUI 930 to prompt the user to enter their user credentials is shown in . Fig. 9B shown. According to one aspect of the embodiments, the GUI 930 may include a username field 932, which may contain a unique username or an email address, and a masked or unmasked password field 934 to allow the user to enter his password.
[0233] Referring again to Fig. In step 906 of 9A, after the user credentials have been entered into the app, a prompt is displayed requesting user confirmation to log in to the trusted computer system 180. An example implementation of GUI 940 for requesting user confirmation to log in to the trusted computer system 180 is shown in Fig. 9D shown. According to one aspect of the embodiments, the GUI 940 may also contain a warning, such as the one shown in Fig. Figure 9D showed that confirming the login results in the user being logged out of other reading devices (e.g., the user's old smartphone).
[0234] If the user confirms the login, the user credentials are then sent to the trusted computer system 180 in step 908 and subsequently verified. Additionally, according to some embodiments, the device ID can also be transferred from the reading device 120 to the trusted computer system 180 and stored in a non-transient memory of the trusted computer system 180. According to some embodiments, the trusted computer system 180 can, for example, update a device ID field associated with the user's record in a database in response to receiving the device ID.
[0235] After the user access data has been verified by the trusted computer system 180, the user is prompted by the app in step 910 to query the already activated sensor control device 102. In accordance with the disclosed subject matter, querying may involve bringing the reader 120 into close proximity with the sensor control device 102 and causing the reader 120 to transmit one or more wireless query signals according to a first wireless communication protocol. In some embodiments, the first wireless communication protocol may, for example, be a near-field communication (NFC) wireless communication protocol. However, those skilled in the art will recognize that other wireless communication protocols may also be implemented (e.g., infrared, UHF, 802.11x, etc.).An example implementation of the GUI 950 to prompt the user to query the already activated sensor control device 102 is shown in . Fig. 9D shown.
[0236] Still referring to Fig. In step 102, the sensor control device 102 is queryed by the reader device, causing the sensor control device 102 to terminate any existing wireless communication connection with the user's previous reader device, if one currently exists. According to one aspect of the embodiments, the existing wireless communication connection may include a connection established according to a second wireless communication protocol that differs from the first wireless communication protocol. In some embodiments, for example, the second wireless communication protocol may be a Bluetooth or Bluetooth Low Energy protocol. Subsequently, the sensor control device 102 enters a "pairing ready" state, in which it is ready to establish a wireless communication connection with the reader device 120 according to the second wireless communication protocol.
[0237] In step 914, the reader 120 initiates a pairing sequence with the sensor control device 102 via the second wireless communication protocol (e.g., Bluetooth or Bluetooth Low Energy). Subsequently, in step 916, the sensor control device 102 completes the pairing sequence with the reader 120. In step 918, the sensor control device 102 can begin transmitting current glucose data to the reader 120 according to the second wireless communication protocol. In some embodiments, for example, the current glucose data can be wirelessly transmitted to the reader 120 at a predetermined interval (e.g., every minute, every two minutes, every five minutes).
[0238] Still referring to Fig. In step 920, the reader 120 receives and stores current glucose data received from the sensor control device 102 in a non-transient memory of the reader 120. Additionally, according to some embodiments, the reader 120 can request glucose trend data from the sensor control device 102 for refilling. For example, according to some embodiments, the reader 120 can request glucose trend data from the sensor control device 102 for the entire wear time, which is stored in a non-transient memory of the sensor control device 102. In other embodiments, the reader 120 can request glucose trend data for a specific predetermined period (e.g., from day 3 to today, from day 5 to today, the last 3 days, the last 5 days, lifecount > 0, etc.). Those skilled in the art will understand that other refilling schemes may also be implemented (such as...).those relating to . Fig. 6A and Fig. 6B), which also fall entirely within the scope of protection of this disclosure.
[0239] Upon receiving the request in step 922, the sensor control device 102 can retrieve glucose trend data from a non-transient memory and transmit it to the reader 120. In step 924, the reader 120 can, in turn, store the received glucose trend data in a non-transient memory. Additionally, according to some embodiments, the reader 120 can also display the current glucose data and / or the glucose trend data in the app (e.g., on a sensor results screen). In this respect, a new reader can display all available analyte data for the entire wear time of a sensor control device. In some embodiments, the reader 120 can also transmit the current glucose data and / or glucose trend data to the trusted computer system 180. In step 926, the received glucose data can be stored in a non-transient memory (e.g.,a database) of the trusted computer system 180.
[0240] In some embodiments, the received glucose data can also be deduplicated before being stored in the non-transient memory. Example implementations for sensor verification and sensor replacement system alarms
[0241] Exemplary embodiments for autonomous sensor verification and sensor insertion system alarms and associated methods are now described. In accordance with the disclosed subject matter, specific adverse conditions that impair the operation of the analyte sensor and the sensor electronics can be detected by the sensor control device. For example, an improperly inserted analyte sensor can be detected if a measurement of the average glucose level over a predetermined period is determined to be below a threshold for insertion errors. However, due to its small form factor and limited energy capacity, the sensor control device may not have sufficient alarm capabilities. Therefore, it would be advantageous if the sensor control device could transmit information about adverse conditions to another device, such as a reading device (e.g., a sensor).a smartphone), could transmit to warn the user about these conditions.
[0242] Fig. Figure 10A is a flowchart illustrating an exemplary embodiment of a method 1000 for generating a sensor insertion error system alarm (also referred to as a sensor verification system alarm). In step 1002, a sensor insertion error condition is detected by the sensor control device 102. In some embodiments, for example, a sensor insertion error condition can be detected when an average glucose value during a predetermined time period (e.g., the average glucose value over five minutes, eight minutes, 15 minutes, etc.) is below an insertion error threshold for the glucose level. In step 1004, in response to the detection of the insertion error condition, the sensor control device 102 stops the glucose measurements. In step 1006, the sensor control device 102 generates a sensor verification indicator and transmits it to the reading device 120 via a wireless communication circuit arrangement.Subsequently, as shown in steps 1012 and 1014, the sensor control device 102 continues to transmit the sensor verification indicator until either: (1) an acknowledgment for the indicator is received from the reading device 120 (step 1012); or (2) a predetermined waiting period has elapsed (step 1014), whichever occurs first.
[0243] According to another aspect of the embodiments, if a wireless communication link is established between the sensor control device 102 and the reader device 120, the reader device 120 receives the sensor verification indicator in step 1008. In response to receiving the sensor verification indicator, the reader device 120 will display a sensor verification system alarm in step 1010. Fig. 10B to 10D are example embodiments of sensor verification system alarm interfaces as displayed on the reader 120. In some embodiments, the sensor verification system alarm may be, for example, a notification panel, a banner, or a pop-up window output to a smartphone display, such as interfaces 1020 and 1025 in Fig. 10B and Fig. 10C. In some embodiments, the sensor verification alarm can be sent to a display device on a reading device 120, such as a glucose meter, or to a receiver device, such as the interface 1030 in Fig. 10D. According to the embodiments, the reading device 120 can also send a sensor verification indicator receipt back to the sensor control device 102. In some embodiments, for example, the sensor verification indicator receipt can be generated automatically and sent upon successful display of the sensor verification system alarm 1020, 1025, or 1030. In other embodiments, the sensor verification indicator receipt is generated and / or transmitted in response to a predetermined user input (e.g., clearing the sensor verification system alarm, pressing an "OK" confirmation button 1032, etc.).
[0244] Subsequently, in step 1011, the reading device 120 deletes the sensor control device 102. In accordance with the disclosed subject matter, step 1011 may, for example, comprise one or more of: terminating an existing wireless communication link with the sensor control device 102; unpairing the sensor control device 102; revoking an authorization or digital certificate associated with the sensor control device 102; generating or modifying a record stored on the reading device 120 to indicate that the sensor control device 102 is in a memory state; or transmitting an update to the trusted computer system 180 to indicate that the sensor control device 102 is in a memory state.
[0245] Referring again to Fig. In step 1016, the sensor control device 102 stops transmitting the sensor verification indicator if either the sensor verification indicator acknowledgment is received by the sensor control device 102 (in step 1012) or the predetermined waiting period has elapsed (step 1014). Subsequently, in step 1018, the sensor control device 102 enters a memory state in which it does not take any glucose measurements and the wireless communication circuitry is either deactivated or put into a sleep mode. According to one aspect, while in a "memory state," the sensor control device 102 can be reactivated by the read device 120.
[0246] Although the procedure 1000 in Fig. As described in 10A with regard to glucose measurements, experts will recognize that the sensor control device 102 can also be configured to measure other analytes (e.g., lactate, ketone, etc.). Additionally, although the procedure 1000 in Fig. 10A describes specific process steps that are performed by the reading device 120 (e.g., receiving a sensor verification indicator, displaying a sensor verification system alarm, and sending a sensor verification indicator acknowledgment). Persons skilled in the art understand that all or some of these process steps can also be performed by other devices in an analyte monitoring system, such as a local computer system, a body-worn computer device, or a drug delivery device. Persons skilled in the art will also understand that process 1000 of Fig. 10A can be combined with any of the other methods described here, which, without being limited, include method 700 of Fig. 7, which relates to expired or failed sensor transmissions.
[0247] Fig. Figure 11A is a flowchart illustrating an example implementation of a method 1100 for generating a sensor termination system alarm (also referred to as a "sensor replacement" system alarm). In step 1102, a sensor insertion fault condition is detected by the sensor control device 102. As previously described, a sensor termination fault condition may, but is not limited to, one or more of the following: a detected FIFO overflow, a sensor signal below a predetermined insertion fault threshold, detected moisture ingress, an electrode voltage exceeding a predetermined diagnostic voltage threshold, an early attenuation (ESA) condition, or a late attenuation (LSA) condition, to name a few.
[0248] In step 1104, the sensor control device 102 stops glucose measurements in response to the detection of a sensor termination condition. In step 1106, the sensor control device 102 generates a sensor replacement indicator and transmits it to the reader 120 via a wireless communication circuit arrangement. Subsequently, in step 1112, the sensor control device 102 continues to send the sensor replacement indicator while determining whether a sensor replacement indicator acknowledgment has been received from the reader 102.In accordance with the disclosed subject matter, the sensor control device 102 can continue to transmit the sensor replacement indicator until either: (1) a predetermined waiting period has elapsed (step 1113), or (2) an acknowledgment for the sensor replacement indicator is received (step 1112) and the sensor control device 102 has successfully transmitted refill data (steps 1116, 1120) to the reading device 120.
[0249] Still referring to Fig. In step 1008, the reader 120 will receive the sensor replacement indicator if a wireless communication link is established between the sensor control device 102 and the reader 120. In response to receiving the sensor replacement indicator, the reader 120 will display a sensor replacement system alarm in step 1110. Fig. Figures 11B to 11D are example embodiments of sensor replacement system alarm interfaces as displayed on the reader 120. In some embodiments, the sensor replacement system alarm may be, for example, a notification field, a banner, or a pop-up window output to the display device of a smartphone, such as interfaces 1130 and 1135 in [reference missing]. Fig. 11B and Fig. 11C. In some embodiments, the sensor verification alarm can be directed to a display device on a reading device 120, such as a glucose meter, or a receiving device, such as the interface 1140 in Fig. 11D. According to the embodiments, the reading device 120 can also send a sensor replacement indicator receipt back to the sensor control device 102 to confirm receipt of the indicator. In some embodiments, for example, the sensor replacement indicator receipt can be generated automatically and sent upon successful display of the sensor replacement system alarm 1130, 1135, or 1140. In other embodiments, the sensor replacement indicator is generated and / or transmitted in response to a predetermined user input (e.g., clearing the sensor verification system alarm, pressing an "OK" confirmation button 1142, etc.).
[0250] In step 1114, after displaying the sensor replacement system alarm and sending the sensor replacement indicator acknowledgment, the reader 120 can request glucose trend data from the sensor control device 102. In step 1116, the sensor control device 102 can collect the requested glucose trend data and send it to the reader 120. In accordance with the disclosed subject matter, the step for requesting, collecting, and communicating glucose trend data can include a data replenishment routine, such as with reference to Fig. 6A and Fig. Procedure described in 6B.
[0251] Referring again to Fig. In step 1118, the reader 120 can send an acknowledgment of receipt for the requested glucose trend data to the sensor control device 102. Subsequently, in step 1119, the reader 120 deletes the sensor control device 102.In accordance with the disclosed subject matter, step 1119 may, for example, comprise one or more of: terminating an existing wireless communication link with the sensor control device 102; unpairing the sensor control device 102; revoking an authorization or digital certificate associated with the sensor control device 102; generating or modifying a record stored on the read device 120 to indicate that the sensor control device 102 has been terminated; or transmitting an update to the trusted computer system 180 to indicate that the sensor control device 102 has been terminated.
[0252] In step 1120, the sensor control device 102 receives the acknowledgment of receipt for the glucose trend data. Subsequently, in step 1122, the sensor control device 102 stops transmitting the sensor replacement indicator, and in step 1124, the sensor control device 102 can enter a termination state in which it does not take any glucose measurements and the wireless communication circuitry is either deactivated or in a sleep state. In accordance with the disclosed subject matter, the sensor control device 102 cannot be reactivated by the reading device 120 in a termination state.
[0253] Although the procedure 1100 in Fig. Although procedure 1100 in 11A is described with regard to glucose measurements, those skilled in the art will recognize that the sensor control device 102 can also be configured to measure other analytes (e.g., lactate, ketone, etc.). Although procedure 1100 in Fig. Where procedure 11A describes specific process steps performed by the reading device 120 (e.g., receiving a sensor replacement indicator, displaying a sensor replacement system alarm, and sending a sensor replacement indicator acknowledgment), those skilled in the art will understand that all or some of these process steps can also be performed by other devices in an analyte monitoring system, such as a local computer system, a body-worn computer device, or a drug delivery device. Those skilled in the art will also understand that procedure 1100 of Fig. 11A can be combined with any of the other methods described herein, which, without being limited, include method 700 of Fig. 7, which relates to expired or failed sensor transmissions. Example implementation formats for reports that include multiple interfaces
[0254] Example implementations for reports comprising multiple interfaces are now described. In accordance with the disclosed subject matter, a user may be presented with a report containing several of the interfaces disclosed herein. In accordance with the disclosed subject matter, the interfaces may include any combination of measured interfaces based on current or measured analyte values, interfaces for physiological parameters based on the physiological parameters disclosed herein, and personalized interfaces based on personalized glucose metrics disclosed herein.
[0255] In light of the foregoing and in accordance with the disclosed subject matter, a glucose monitoring system is provided, comprising a sensor control device including an analyte sensor coupled to and configured with sensor electronics to transmit data indicating an analyte level of a subject, and a reading device. The reading device of the disclosed subject matter comprises a wireless communication circuit arrangement configured to receive data indicating the analyte level and a level of glycated hemoglobin for the subject, a non-transient memory, and at least one processor.The processor is coupled to the non-transient memory and the analyte sensor via communication technology and is configured to calculate several personalized glucose readings for the subject using at least one physiological parameter and at least one of the received data indicating the analyte level or the received level of glycated hemoglobin, and to display a report on a display device of the reading device, which includes several interfaces that display at least two or more of the received data indicating the analyte level, the received level of glycated hemoglobin, or the calculated multiple personalized glucose readings, wherein the multiple interfaces comprising the report are based on a user type.According to embodiments, at least one physiological parameter is selected from the group consisting of: red blood cell glucose uptake, red blood cell lifetime, red blood cell glycation constant, red blood cell formation constant, red blood cell elimination constant, and apparent glycation constant. By way of example, but not as a limitation, in further embodiments the multiple interfaces include at least one physiological parameter for the subject.
[0256] According to embodiments, the content of a report can vary based on different user types (for example, but not limited to, subjects, healthcare providers, nurses, etc.). As explained here, the multiple interfaces comprising the report are either predetermined based on the user type or can be selected by the user. In one embodiment, the user type includes a healthcare professional. For example, but not limited to, in another embodiment, the multiple interfaces include a glucose monitoring data interface, a glycated hemoglobin interface, a personalized A1c interface, a personalized glucose interface, a personalized average glucose interface, and a personalized time-in-range interface. In one embodiment, the user type includes the subject.As an example, but not to limit, in another embodiment the multiple interfaces include a glucose monitoring data interface, a glycated hemoglobin interface, an average glucose interface, and a time-in-range interface.
[0257] According to some embodiments, subjects using the analyte monitoring systems may only view graphical interfaces displaying either measured analyte measurements or personalized analyte measurements, but not both. For example, it may be advantageous to minimize confusion by displaying graphical interfaces with slightly different data (such as between measured and personalized data). As explained here, the choice of which interfaces to include in a report depends on whether the personalized glucose metrics have been approved or designated by the appropriate regulatory authority for research or clinical use.
[0258] According to embodiments, the personalized glucose metrics can include one or more personalized A1c or adapted A1c, glucose-determined A1c or calculated A1c, personalized glucose, personalized average glucose, and personalized time in range. According to embodiments, the at least one processor is configured to compute multiple personalized glucose targets corresponding to the calculated multiple personalized glucose metrics. According to embodiments, the multiple interfaces also contain the multiple personalized glucose targets. According to embodiments, the personalized glucose targets can include personalized glucose target ranges and / or personalized average glucose targets. According to embodiments, the personalized glucose target range can include a personalized lower limit for glucose and / or a personalized upper limit for glucose.
[0259] Fig. Figure 24 shows an example report 1400 containing four different measured interfaces associated with the example subject J17: a glucose monitoring data interface 2401, which contains a graphical representation of measured glucose measurements from an analyte monitoring device over a predetermined time period; an HbA1c interface 2402, which contains a graphical representation of HbA1c measurements (shown as points 1402a) over a predetermined time period and a graphical representation of calculated A1c (“cA1c”) or glucose-derived A1c; an average glucose interface 1403, which contains a graphical representation of measured 14-day average glucose (148 mg / dL) over a predetermined time period; and a time-in-range interface 1404, which contains a graphical representation of measured time-in-range metrics (75% over 180 mg / dL and 2% below 70 mg / dL,as shown) over a predetermined period of time. As explained here, HbA1c measurements may include laboratory A1c measurements. In another embodiment, the reader, by way of example, but not limited to, wirelessly receives the level of glycated hemoglobin for the subject from an electronic health record system, a cloud-based database, from the subject via a QR code, or from the subject using a home test kit, which may optionally be sent to a laboratory for analysis. As explained here, Fig. 24 any of the interfaces disclosed herein.
[0260] As explained here and as in Fig. As shown in Figure 24, the glucose monitoring data interface 2401 can contain a graphical representation (shown as a dashed line) of the glucose target range 2401b,c in the foreground. The glucose target range 2401b,c can contain a personalized glucose target range, as described here. As explained here and as in Fig. As shown in Figure 24, the HbA1c interface 2402 can contain a graphical representation (shown as a solid line) of the HbA1c target 2402b (6.5% as an example, not for restriction). As explained here and as in Fig. Figure 24 shows that the interface for average glucose 1403 can contain a graphical representation (shown as a solid line) of the target for average glucose 1403a.
[0261] As explained here and as in Fig. As shown in Figure 24, the predetermined time period can be 45 days. As explained here, the predetermined time period can be in five-minute increments, with the data comprising a total of twelve hours. However, those skilled in the art will recognize that other time increments (e.g., 30 days) and durations of analyte data can also be used and are fully within the scope of this disclosure. Fig. 26 and Fig. 28 similarly represent interfaces for the exemplary subjects J33 and J5.
[0262] Fig. Figure 25 shows an example report 1500 containing eight different interfaces assigned to the example subject J17. As in Fig. As shown in Figure 25, the report can contain 1500 measured interfaces, interfaces for physiological parameters, and personalized interfaces. As explained here, Fig. 25 any of the interfaces disclosed herein.
[0263] According to the embodiment disclosed herein, measured interfaces may, by way of example, but not limited to, include an interface 2401 for glucose monitoring data and an HbA1c interface 2402, as shown in Fig. 25 shown. As explained here, the HbA1c interface 2402 may contain a calculated HbA1c (cA1c or GD-A1c) curve fitted by the HbA1c measurements, as described here and in WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein by reference in their entirety.
[0264] According to the embodiment disclosed herein, the interfaces for physiological parameters may, by way of example, but not limited to, include interface 2501 for glucose uptake by red blood cells and interface 2502 for red blood cell lifespan, as shown in Fig. 25 shown. As shown here, interface 2501 for red blood cell glucose uptake can contain a graphical representation of the subject's red blood cell glucose uptake (solid line) 2501a and a reference red blood cell glucose uptake (dashed line) 2501b over a predetermined time period. As implemented here, interface 2502 for red blood cell lifetime can contain a graphical representation of the subject's red blood cell lifetime (solid line) 2502a and a reference red blood cell lifetime (dashed line) 2502b over a predetermined time period. As shown in Fig. 23 can be seen and in Fig. Figure 25 shows that the glucose uptake of red blood cells in subject J17 is 96%, and the red blood cell lifespan is 121 days. The glucose uptake and red blood cell lifespan of the subject can be calculated using the models described here and in WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein by reference in their entirety. As stated here, the physiological parameter interfaces may include any other physiological parameters, as described here and in WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein by reference in their entirety.
[0265] According to the embodiment disclosed herein, personalized interfaces may, by way of example, but not limited to, include a personalized interface 2503 for glucose, a personalized A1c interface 2504, a personalized interface for average 14-day glucose 2505, and a personalized time-in-range interface 2506, as shown in Fig. 25 shown. As explained here, Fig. 25 any of the personalized interfaces disclosed herein. The personalized glucose interface 2503 may contain a graphical representation of the subject's glucose monitoring data interface as personalized using the models described here and in WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein by reference in their entirety. As explained here and in Fig. As shown in Figure 25, the personalized glucose interface 2503 can contain the glucose target range 2401b,c in the foreground. The glucose target range 2401b,c can contain a personalized glucose target range, as described here.
[0266] According to the embodiment disclosed herein, the personalized A1c interface 2504 can include a graphical representation of the subject's fitted or personalized A1c (shown as points 2504a) and fitted cHbA1c (shown as curve fitting 2504c), calculated using the models described herein and in WO2021 / 108419 and WO2020 / 086934 for Xu, which are incorporated herein by reference in their entirety. As explained herein, the personalized HbA1c interface 2504 can include a graphical representation (shown as a solid line) of the HbA1c target 2402b (for example, not to be limited, 6.5%).
[0267] According to the embodiment disclosed herein, the personalized interface 2505 for the average 14-day glucose can contain an interface 1403 for the average glucose, which contains a graphical representation of the personalized average 14-day glucose (as shown, 141 mg / dL) over a predetermined time period. As explained herein and as described in Fig. Figure 25 shows that the personalized interface for average glucose 2503 can include a graphical representation (shown as a solid line) of the target for average glucose 1403a.
[0268] According to the embodiment disclosed herein, the personalized interface 2506 for time in ranges can contain a graphical representation of the personalized time-in-range metrics (as shown, 78% above 180 mg / dL and 3% below 70 mg / dL) over a predetermined time period.
[0269] As explained here and as in Fig. As shown in Figure 25, the predetermined time period can be 45 days. As explained here, the predetermined time period can be in five-minute increments, with the data comprising a total of twelve hours. However, those skilled in the art will recognize that other time increments and durations of analyte data can also be used and are entirely within the scope of this disclosure. Fig. 27 and Fig. 29 similarly provide graphical representations of four different glucose metrics for J33 and J5, respectively.
[0270] According to the embodiments disclosed herein, reports 1400 or 1500 can contain a variety of measured interfaces, physiological parameter interfaces, or personalized interfaces based on the user type. For example, healthcare providers and nurses can benefit from seeing a comparison between measured interfaces and personalized interfaces to assess, for instance, how much the two differ and to evaluate diagnostic and treatment options accordingly. Thus, in one embodiment, the content of a report for an HCP can include, by way of example, not by way of limitation, a predetermined set of measured interfaces, physiological parameter interfaces, and personalized interfaces, as shown in report 1500.According to embodiments, HCPs can have the best access to information that includes measured analyte measurements, personalized analyte measurements, and physiological parameters (for example, without limitation, RBC glucose uptake and RBC lifespan, as in ). Fig. 25, Fig. 27, Fig. 19 shown, or as a second report, as discussed above) as determined using the models described herein. As explained here, in one embodiment, the content of a report for the subject may include a predetermined set of measured interfaces, interfaces for physiological parameters, and / or personalized interfaces. As an example, but not a limitation, a report generated for a user may include measured interfaces, as shown in Report 1400. As explained here, a user type may, as an example, but not a limitation, include the subject, a healthcare provider, a caregiver, an insurance provider, etc.
[0271] As explained here, a user (e.g., the study participant, an HCP, a nurse, an insurance provider, etc.) can select which interfaces the report includes. As an example, not a limitation, the user can choose any combination of measured interfaces, personalized interfaces, and interfaces for physiological parameters disclosed here.
[0272] According to one embodiment, a user can select whether to use a sensor result interface, as disclosed herein, which displays measured analyte measurements (as an example, not to limit, to how those in the Fig. 24, Fig. 26 and Fig. 28 shown) over a predetermined period of time or personalized measurements (as an example, not a limitation, such as those in the Fig. 25, Fig. 27 and Fig. 29) displays over the same predetermined time period, or wishes to view both. As explained here, the user can switch or toggle between viewing a sensor results interface with measured analyte measurements over a predetermined time period and viewing the same sensor interface with personalized analyte measurements over the same predetermined time period. As an example, not a limitation, a user can switch between an average glucose interface 1403, which contains a graphical representation of the average glucose level over a day (as an example, not a limitation, such as the one shown in Fig. 24 shown), and a personalized interface for average glucose 2505, which includes a graphical representation of the personalized average glucose level over the same predetermined time period (as an example, not a limitation, as shown in Fig. 25 are shown), toggle. According to embodiments, a user can similarly switch between any of the other in the Fig. 24, Fig. 26, Fig. 28 measured interfaces shown and those in the Fig. 25, Fig. 27, Fig. The personalized interfaces shown in Figure 29 (by way of example, not limitation, the A1c interface, the glucose interface, the 14-day average glucose interface, and the time-in-range interface, etc.) can be switched. However, those skilled in the art will recognize that other time increments and durations of analyte data can also be used and are fully within the scope of this disclosure. According to embodiments, the sensor result interfaces, analyte level and trend alert interfaces, time-in-range interfaces, and / or sensor usage interfaces as described herein can similarly be selected by a user to display measured analyte measurements over a predetermined time period and / or personalized analyte measurements over a predetermined time period.
[0273] According to embodiments, the combined data can be used in conjunction with one of the graphical user interfaces described above. According to embodiments of this disclosure, a user (e.g., a healthcare provider, nurse, etc.) can personalize any of the graphical interfaces described above. Furthermore, an ambulatory glucose profile report (“AGP report”) (the report proposed by the International Diabetes Center (“IDC”), incorporated herein by reference in its entirety and available on the website http: / / www.agpreport.org / agp / agpreports) can be modified to include one of the graphical interfaces or personalized metrics described herein.As an example, not a limitation, the IDC AGP report version 5 can be modified by replacing the glucose management indicator (GMI) with personalized A1c. Furthermore, a graphical interface for reporting personalized A1c can be achieved by combining any of the graphical components described herein. For example, in one embodiment, a graphical user interface 3000 can be at least the time-in-ranges GUI 340 as described in [reference missing]. Fig. 3F is shown, containing the glucose trend interface 517 as described here and the health information interface 518 as described here. Interface 3000 can contain the patient's name, date of birth (“DOB”), the time period covered by the report, and the percentage of time within that period that the continuous glucose monitoring device was active. As shown in Fig. As shown in Figure 3, the time period can be 14 days. According to embodiments, the time period can be any other period (for example, without limitation, 1 day, 2 days, 3 days, 7 days, 30 days, 45 days, etc., or any other period). According to embodiments, the time period can be selected by the patient or the healthcare provider.
[0274] According to Fig. 30. Another GUI can provide an interface for use by healthcare providers. For example, a provider interface 3100 can include an input interface 3102 through which a provider can input A1c data sets, which may include a laboratory-measured A1c value. Similarly, the provider interface 3100 can also include an output interface 3104, which can contain a measured A1c and a personalized A1c determined based on the measured A1c. The output interface 3104 can also include other data such as GMI, percentage of time in target range, percentage of time below target range, and personalized A1c factor (also known as "adjusted glycation ratio" or "AGR" and as disclosed in U.S. Patent Application No. 18 / 052,805, which is incorporated herein by reference in its entirety).According to embodiments of the present disclosure, the provider interface 3100 can also include a patient record interface 3106 for displaying electronic patient records (“EMR”). According to embodiments of the present disclosure, the EMR can contain data such as the time a sensor is worn, the collected data, the time within, above, or below the range, the measured A1c, the personalized A1c, and more. According to embodiments, the interface 3106 can contain data records over a period of time. For example, as in . Fig. As can be seen, the interface contains 3106 data records in a table format for each month in which data is collected and / or analyzed.
[0275] As disclosed in U.S. patent applications Nos. 17 / 832,537 and 18 / 052,805, which are incorporated herein by reference in their entirety, the measurement of the HbA1c or HbA1c target can be adjusted by a user's apparent glycation ratio (“AGR”) (also referred to as a “personalized A1c factor” or “personalized HbA1c factor”). Table 3, for example, shows an “adjusted” HbA1c target measurement based on AGR. Specifically, as can be seen in Table 3, an A1c target of 6.0 adjusted by an AGR of 60 provides an adjusted A1c target of 5.5. Similarly, an A1c target of 6.0 adjusted by an AGR of 65 provides an adjusted A1c target of 6.0. Alternatively, a measured A1c value can be adjusted in a similar way using the AGR to obtain an adjusted A1c value (or a personalized A1c value).Presenting this information to study participants and healthcare providers can help to make more accurate and informed diabetes diagnoses and treatments, based at least on the individual demographic metrics and / or physiology of the study participant.
[0276] Thus, by measuring the A1c, determining a personalized A1c factor, and applying the factor to the measured A1c, a personalized A1c can be determined.
[0277] Although the disclosed subject matter is described here in the form of specific illustrations and examples, those skilled in the art will recognize that various modifications and improvements can be made to the disclosed subject matter without deviating from its scope of protection. Furthermore, although individual features of one embodiment of the disclosed subject matter may be discussed here or shown in the drawings of one embodiment and not discussed in other embodiments, it should be obvious that individual features of one embodiment can be combined with one or more features of another embodiment or features from several embodiments.
[0278] In addition to the specific embodiments claimed below, the disclosed subject matter is also directed to other embodiments that have any other possible combination of the dependent features claimed below and the features disclosed above. Thus, the specific features presented in the dependent claims and disclosed above can be combined with one another in other ways within the scope of the disclosed subject matter, so that the disclosed subject matter should also be recognized as being specifically directed to other embodiments with other possible combinations. Therefore, the preceding description of specific embodiments of the disclosed subject matter has been presented for illustrative and descriptive purposes only. It is not intended to be exhaustive or to limit the disclosed subject matter to these disclosed embodiments.
[0279] The present description merely illustrates the principles of the disclosed subject matter. Various modifications and alterations of the described embodiments will be obvious to those skilled in the art upon review of the teachings presented here. Accordingly, the disclosure here is intended to be explanatory, but not limiting, with regard to the scope of protection of the disclosed subject matter. QUOTES INCLUDED IN THE DESCRIPTION
[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature
[0000] US patent application no. 63 / 279,509
[0001] 9,913,600
[0035] WO2018 / 136898
[0035] WO2019 / 236850
[0035] 2020 / 01969191
[0035] 6,175,752
[0108] 2011 / 0213225
[0108] 2018 / 0235524
[0145] WO2020 / 086934 [0145, 0160, 0161, 0162, 0186, 0264, 0265, 0266] WO2021 / 108419 [0145, 0160, 0161, 0162, 0263, 0264, 0265, 0266] WO2021 / 108431
[0145] US patent application no. 62 / 939,970
[0145] 63 / 015,044
[0145] 63 / 081,599
[0145] US patent application no. 62 / 939,956
[0145] US patent application no. 18 / 052,805
[0274] 17 / 832,537
[0275] 18 / 052,805
[0275] Cited non-patent literature
[0000] Higgens et al. (Sci. Transl. Med. 8, 359ral30, 2016
[0061]
Claims
[1] Glucose monitoring system that includes: a sensor control device including an analyte sensor coupled to sensor electronics, the sensor control device configured to transmit data indicative of an analyte level of a subject; and a reading device comprising: wireless communication circuitry configured to receive the data indicative of the analyte level and a glycated hemoglobin level for the subject; a non-transitory memory; at least one processor communicatively coupled to the non-transitory memory and the analyte sensor and configured to: Calculating a plurality of personalized glucose metrics for the subject using at least one physiological parameter and at least one of the received data indicative of the analyte level or the received level of glycated hemoglobin; and Displaying on a display device of the reading device a report comprising a plurality of interfaces containing at least two or more of the received data indicating the analyte level, the received level of glycated hemoglobin, or the calculated plurality of personalized glucose metrics, where the multiple interfaces containing the report are based on a user type. [2] The system of claim 1, wherein the plurality of personalized glucose metrics includes one or more of an adjusted A1c, a calculated A1c, an adjusted calculated A1c, a personalized glucose, a personalized average glucose, or a personalized time in range. [3] The system of claim 2, wherein the at least one processor is further configured to calculate a plurality of personalized glucose targets corresponding to the calculated plurality of personalized glucose metrics. [4] The system of claim 3, wherein the plurality of interfaces further includes the plurality of personalized glucose targets. [5] The system of claim 3, wherein the plurality of personalized glucose targets include a glucose target range and / or an average glucose target. [6] The system of claim 5, wherein the personalized glucose target range includes a personalized glucose lower limit. [7] The system of claim 5, wherein the personalized glucose target range includes a personalized glucose upper limit. [8] The system of claim 1, wherein the at least one physiological parameter is selected from the group consisting of: a red blood cell glucose uptake, a red blood cell lifetime, a red blood cell glycation rate constant, a red blood cell formation rate constant, a red blood cell elimination constant, and an apparent glycation constant. [9] The system of claim 8, wherein the plurality of interfaces further includes the at least one physiological parameter for the subject. [10] The system of claim 1, wherein the user type comprises a medical professional. [11] The system of claim 10, wherein the plurality of interfaces include a glucose monitoring data interface, a glycated hemoglobin interface, a personalized A1c interface, a personalized glucose interface, a personalized average glucose interface, and a personalized time-in-range interface. [12] The system of claim 1, wherein the user type includes the subject. [13] The system of claim 12, wherein the plurality of interfaces include a glucose monitoring data interface, a glycated hemoglobin interface, an average glucose interface, and a time-in-range interface. [14] The system of claim 1, wherein the plurality of interfaces comprising the report are predetermined based on the user type. [15] The system of claim 1, wherein the plurality of interfaces comprising the report are selectable by the user. [16] The system of claim 4, wherein the at least one processor is further configured to output a notification if at least one of the plurality of personalized glucose metrics is at or above the corresponding plurality of personalized glucose targets. [17] The system of claim 16, wherein the notification comprises a visual notification. [18] The system of claim 16, wherein the message comprises an audio message. [19] The system of claim 16, wherein the message is an alarm. [20] The system of claim 16, wherein the message is a request. [21] The system of claim 1, wherein the reading device wirelessly receives the glycated hemoglobin level for the subject from an electronic medical record system. [22] The system of claim 1, wherein the reading device wirelessly receives the glycated hemoglobin level for the subject from a cloud-based database. [23] The system of claim 1, wherein the reading device wirelessly receives the glycated hemoglobin level for the subject from a QR code. [24] The system of claim 1, wherein the reading device wirelessly receives the glycated hemoglobin level for the subject from a home test kit.
Citation Information
Patent Citations
Medical devices and methods
US20110213225A1
Methods, devices, and systems for physiological parameter analysis
US20180235524A1
Systems, devices, and methods for analyte sensor insertion
US20200196919A1
Systems, devices, and methods for physiological parameter analysis and related graphical user interfaces
US20220400986A1
Methods, devices, and systems for adjusting laboratory hba1c values
US20230215521A1
