System and method for tracking and presenting glucose monitoring data

Abstract

Systems and methods for improved continuous glucose monitoring ("CGM") are provided. The disclosed systems and methods provide for tracking of analyte measurements, CGM-related event data, and sensor-related data. Aspects of the present disclosure allow one or more users' data and analyte measurements to be displayed in a graphical user interface for improved functionality. The graphical user interface includes a history graph of analyte measurements and incorporates event data representing a plurality of event indications. The time frame of the history graph is adjustable by the user, and events can be presented as groups within the event indication based on the time frame of the history graph. The graphical user interface may also be configured to display a graph of trend data for each individual event, and a sensor life indication representing the time remaining until expiration of one or more analyte sensors.

Description

Technical Field

[0001] Systems and methods for improved continuous glucose monitoring are provided.

Background Art

[0002] Type 1 diabetes is a chronic metabolic disorder caused by the pancreas's inability to produce sufficient amounts of the hormone insulin, resulting in a decreased ability of the body to metabolize glucose. This dysfunction leads to hyperglycemia, i.e., the presence of excessive amounts of glucose in the plasma. Persistent hyperglycemia and / or hypoinsulinemia are associated with various severe symptoms and life-threatening long-term complications, such as dehydration, ketoacidosis, diabetic coma, cardiovascular disease, chronic renal failure, retinal damage, and nerve damage with a risk of limb amputation.

[0003] Blood or interstitial glucose monitoring is required to achieve acceptable blood glucose control. Continuous glucose monitoring (CGM) has been utilized for such glucose monitoring over the past 20 years. CGM creates much richer and more complex data than conventional intermittent glucose monitoring data. This additional complexity can be overwhelming for the device user, as well as caregivers and healthcare providers ("HCPs"), especially when there are no appropriate tools to assist in the interpretation of such data.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure relates to continuously monitoring the concentration of an analyte in a physiological fluid and provides a system and method for providing a configured graphical user interface for tracking information regarding the analyte concentration.

Means for Solving the Problems

[0005] According to aspects of the present disclosure, a system and method are provided for displaying analyte measurements on one or more devices, each including a display device (display), one or more memories for storing analyte measurement data and event data, and one or more processors. The one or more processors may be configured to perform the following steps: access analyte measurement data and event data from the one or more memories; determine a first time frame for displaying the analyte measurement data as part of a graph; identify a plurality of events in event data that occurred within the first time frame; determine whether a set of events is within a predetermined proximity range in a graph having the first time frame based on the time (duration) associated with the plurality of events; and provide a graph for display including one or more event displays corresponding to the plurality of events, wherein the set of events is combined such that it is represented by a first event display when it is determined that the set of events is within the predetermined proximity range, and each of the one or more event displays is associated with an analyte measurement in the graph.

[0006] According to aspects of the present disclosure, one or more processors may further be configured to perform the steps of: identifying a first user input as corresponding to a command for a diagram to move from a first time frame to a second time frame, wherein the second time frame is a shorter period than the first time frame; determining that a set of events in the diagram in the second time frame is outside a predetermined proximity; and automatically providing the diagram in the second time frame for display in response to the first user input, wherein the set of events is displayed in relation to the diagram as at least two separate event displays. The one or more processors described above may be further configured to perform the steps of: identifying a second user input as corresponding to a command for a diagram to move from a first time frame to a third time frame, wherein the third time frame is a longer period than the first time frame; determining that one or more additional events in the diagram in the third time frame are within a predetermined proximity range of a set of events; and automatically providing the diagram in the third time frame for display in response to the second user input, wherein the set of events and the additional events are displayed in relation to the diagram as a single combined event display.

[0007] In yet another aspect of this disclosure, the single combined event display may be associated with a single analyte measurement, and events within a set of events may be associated with different times. The first event display may be positioned within the diagram at a location corresponding to the midpoint between different periods. The first event display may include a symbol indicating the number of events to which it is associated.

[0008] In yet another aspect of this disclosure, the one or more processors may be configured to: identify user input for selecting a particular event display to be displayed with a diagram; and, in response to the selection of the particular event display, provide for display additional information relating to one or more events associated with the event display, wherein the additional information includes trend diagrams (trend graphs) of analyte measurements for each of the one or more events. Each trend diagram may display a range of analyte measurements corresponding to a predetermined period before and after each of the one or more events.

[0009] In other aspects of the present disclosure, the one or more processors may further be configured to: identify a sensor configured to provide the analyte measurement; determine the period of time the sensor will continue to operate; and provide a sensor life indicator for display on the same display device as the diagram, wherein the sensor life indicator includes a number indicating the period of time the sensor will continue to operate, and the sensor life indicator is color-coded to indicate the unit of time represented by the number. The number may be surrounded by a plurality of ticker marks corresponding to the unit of time represented by the number.

[0010] In yet another aspect of the present disclosure, the one or more processors may be configured to perform the steps of: comparing the most recent analyte measurement with one or more thresholds; and providing a current measurement display having color in a diagram for display, the color being based on a comparison of the analyte measurement with one or more thresholds.

[0011] In yet another aspect of the present disclosure, the one or more processors may be further configured to determine whether the one or more processors are communicating with a motion sensor, and the current measurement display includes an animation (moving image) when the one or more processors are communicating with the motion sensor. The one or more processors may be further configured to perform the steps of: identifying a user selection of a particular point in a diagram provided for display; determining an analyte measurement associated with that particular point; and providing color-coded analyte measurements for display, wherein the colors correspond to a relationship between an analyte measurement and one or more thresholds.

[0012] Other aspects of this disclosure provide methods and systems for tracking and presenting sensor lifetime data. For example, one or more processors include the steps of: associating a first mobile device with a first user and a second mobile device with a second user; receiving analyte measurements of the first user from an analyte sensor; receiving analyte sensor data, the analyte sensor data including analyte measurements and sensor lifetime data indicating the period over which the analyte sensor will continue to operate; and receiving input data from the first user in one or more processors located away from the first and second mobile devices, which identifies the second user as having access to a selective subset of the analyte sensor data. The process may be configured to include the steps of: providing a selective subset of analyte sensor data to a second mobile device using one or more processors; and providing a selective subset of analyte sensor data to a second mobile device for display on the second mobile device, wherein the display on the second mobile device includes a sensor life display based on sensor life data, the sensor life display includes a sensor life digit indicating the period of time the sensor continues to operate, and the sensor life display is color-coded to indicate the unit of time represented by the sensor life digit.

[0013] In other aspects of this disclosure, one or more processors may switch the display of a sensor lifetime indicator on a second mobile device between a first mode and a second mode based on input received on the second mobile device. The sensor lifetime indicator in the first mode may consist of a sensor lifetime digit and a set of ticker marks surrounding the sensor lifetime digit. The set of ticker marks may include a set of solid ticker marks and a set of faded ticker marks, the number of solid ticker marks corresponding to the sensor lifetime digit. When the analyte sensor continues to operate for less than one hour, one or more processors may provide a sensor lifetime indicator for display in which the sensor lifetime digit represents minutes and the set of ticker marks are replaced with circular indicators representing the amount of time elapsed in the last hour the sensor continues to operate. The second mode may include a sensor lifetime digit and text identifying the date and time when the analyte sensor will expire. The sensor lifetime indicator may include colors representing the units of time corresponding to days, hours, and minutes. The one or more processors described above may include one or more servers that communicate with the first mobile device and the second mobile device.

[0014] In other aspects of the present disclosure, one or more processors may perform the steps of: pairing a first mobile device with a new analyte sensor; automatically transmitting updated sensor lifetime data from the first mobile device to one or more processors in response to the pairing; transmitting a notification from one or more processors to a second mobile device that the first mobile device has been paired with a new analyte sensor; and providing an updated sensor lifetime display for display on the second mobile device based on the updated sensor lifetime data. The sensor lifetime display may be presented as an overlay that remains visible when a second user moves between multiple different display devices on the second mobile device. [Brief explanation of the drawing]

[0015] [Figure 1] This is a diagram of a continuous analysis target monitoring system according to the aspect of this disclosure. [Figure 2] This is a diagram of a continuous analysis target monitoring system according to the aspect of this disclosure. [Figure 3A] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 3B] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 4A] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 4B] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 5A] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 5B] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 6] This is a diagram showing the sensor lifespan indicator according to the embodiments of this disclosure. [Figure 7] This is a diagram showing the sensor lifespan indicator according to the embodiments of this disclosure. [Figure 8] This is a diagram showing the sensor lifespan indicator according to the embodiments of this disclosure. [Figure 9] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 10] This is a graphical user interface for visualizing data related to sensor measurements of an analyte, relating to an aspect of this disclosure. [Figure 11]A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 12] A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 13] A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 14] A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 15] A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 16] A graphical user interface for visualizing data related to sensor measurements of an object to be analyzed, according to an aspect of the present disclosure. [Figure 17] A flowchart showing functions according to an aspect of the present disclosure. [Figure 18] A flowchart showing functions according to an aspect of the present disclosure.

Mode for Carrying Out the Invention

[0016] This disclosure relates to a continuous glucose monitoring system ("CGM" system) that provides an enhanced graphical user interface. In a CGM system, the level or concentration of glucose can be determined by the use of a continuous glucose monitoring (CGM) sensor. The CGM sensor utilizes current-measuring electrochemical sensor technology for measuring glucose using electrodes such as a working electrode and a counter electrode, the electrodes being operably connected to a sensor electronic device covered by a sensing membrane and a biointerface membrane, which are attached by clips. Examples of such systems are found, for example, in U.S. Patent No. 10,188,796B2 and U.S. Patent Application Publication 2018 / 0296757A1, each of which is incorporated herein by reference in its entirety.

[0017] Figure 1 shows a system 100 for continuous glucose monitoring of user 102. The system 100 includes an analyte (e.g., glucose) sensor 112, which transmits (transmits) analyte concentration level values ​​to a device 104 via a wireless transmission 110. Device 104 may be a mobile device such as a smartphone or tablet, or any other wireless-enabled mobile or stationary device including a display device and at least one processor for receiving and processing data from the analyte sensor 112. Device 104, including its at least one processor, may receive, store, and analyze data from the analyte sensor 112. According to aspects of this disclosure, the graphical user interface of the system is configured to provide analyte concentration level values ​​and related information in a manner improved from currently available systems. For example, the device may be a smartphone, e.g., an iPhone® available from Apple Inc., California, and may include an ARM microprocessor. In such a case, the smartphone may execute a set of instructions downloaded to device 104 as an application or app to perform the functions of device 104 described herein.

[0018] The analyte sensor 112 may be coupled with an electronic module including a wireless transceiver to facilitate communication with device 104. In another example, the sensor and transceiver may be part of a combined component. In one embodiment, device 104 may include a touchscreen for input and run an operating system for hosting a graphical user interface as described below. The analyte sensor 112 may be any type of continuous glucose monitoring sensor, such as those applied subcutaneously, transdermally, or transepidermally, and may be implantable or other types. The continuous glucose monitoring sensor transmits a data stream containing the glucose concentration level in host 102. Device 104 can receive, store, and process this data stream. For example, various algorithms known in the art may be executed on at least one of the processors in device 104 to process the data stream, etc.

[0019] The specific glucose analyte measurements described herein are intended to illustrate specific implementations and are not intended to limit the scope of this disclosure. The techniques described herein may be used, for example, to visualize continuous analyte measurements for configurations other than those depicted in Figures 1 and 2, using other sensors for glucose or other analytes found in interstitial fluid.

[0020] Figure 2 shows a diagram of system 200, which may include the analyte sensor 112 and device 104 of system 100. In addition, system 200 may include a computer 210. The memory of computer 210 may store information accessible by one or more processors, including instructions and data that may be executed by one or more processors or used in other ways. The memory of computer 210 or devices 104, 106 and 204 may be of any type capable of storing information accessible by processors, such as computer-readable media, or other media that store data that may be read with the help of electronic devices such as hard drives, memory cards, ROMs, RAMs, DVDs or other optical discs, and other writable and read-only memories. The systems and methods may include different combinations of the above, so that different parts of the instructions and data are stored on different types of media.

[0021] Computer 210 and one or more processors of devices 104, 106, and 204 may execute a set of instructions. The instructions may be any set of instructions executed directly (e.g., in machine code) or indirectly (e.g., in a script) by the processor. For example, the instructions may be stored as computer code on a computer-readable medium. In this regard, the terms “instruction” and “program” may be used interchangeably herein. Instructions may be stored in an object code format for direct processing by the processor, or in any other computer language, including scripts or collections of independent source code modules that are interpreted on demand or pre-compiled. The functions, methods, and routines of instructions are described in more detail below.

[0022] The data may be retrieved, stored, or modified by one or more processors according to instructions. For example, the system and method are not limited to any particular data structure, but the data may be stored in computer registers, in relational databases as tables with multiple different fields and records, in XML documents, or in flat files. The data may be formatted in any computer-readable format.

[0023] The processors of computer 210 and devices 104, 106, and 204 may be any conventional processor, such as those manufactured by Intel Corporation or Advanced Micro Devices. Alternatively, the processor may be a dedicated device such as an ASIC. The memory may be a hard drive or other storage medium located within the server farm of the data center. Therefore, references to processors, computers, or memory should be understood to include references to sets of processors, computers, or memories that may or may not operate in parallel.

[0024] Computer 210 may be located on one node of network 250 and may communicate directly and indirectly with other nodes of the network. For example, computer 210 may include a web server configured to communicate with devices 104, 106, and 204 via network 250 to send and display information to users such as user 102 or 202 in Figure 2 on the display devices of devices 104, 106, and 204. Computer 210 may also include multiple computers that exchange information with different nodes of the network for the purpose of receiving, processing, and sending data to client devices. In this case, the client devices would typically still be located on a node of the network different from any of the computers including server 210.

[0025] Network 250 and the intervening nodes between Server 210 and client devices may include various configurations and may use various protocols, including the Internet, World Wide Web, intranet, virtual private network, Local Ethernet® network, private network using proprietary communication protocols for one or more companies, cellular and wireless networks (e.g., WiFi), instant messaging, HTTP and SMTP, and various combinations of the above. Although only a small number of computers are shown in Figures 1 and 2, it should be understood that a typical system can include a large number of connected computers.

[0026] Devices 104, 106, and 204 may be configured similarly to server 210, comprising one or more processors and memory containing stored instructions. Devices 104, 106, and 204 may have all the components commonly used in relation to a computer, such as a central processing unit (CPU), a web browser, an electronic display, and memory (e.g., RAM and an internal hard drive) for storing data and instructions such as user input. Client devices may also include a camera, a GPS receiver, a speaker, a network interface device, and all the components used to connect these elements to each other. In addition, each device 104, 106, and 204 may be a device intended for use by one or more specific users. For example, devices 104 and 106 may be associated with user 102, while device 204 is associated with user 202. The association between a user and a device may be achieved by assigning each user a unique identifier such as a user ID, and by requiring the user to verify their identity (identification information) by providing verification before accessing an application or specific information using one or more applications running on the device. User verification may take the form of, for example, a password or a unique biometric identifier (biometric authentication).

[0027] According to aspects of this disclosure, user 102 may be provided with CGM data, including interactive trend diagrams, event displays, event logs, and sensor operation data, via device 104. As further described below, the interactive trend diagrams, event displays, and sensor operation data provide an enhanced user interface that enables flexibility and simplicity in acquiring comprehensive CGM data.

[0028] Figures 3A and 3B are graphical user interfaces 300 and 300' as presented on the display device of device 104 in Figures 1 and 2, respectively. At the top, the graphical user interface 300 includes a colored bubble 302, a white bubble 304, the current analyte measurement 306, a trending arrow 310, and a sensor lifetime indicator 360. The color of the colored bubble 302 may be configured to change to indicate whether the current analyte concentration level is above, below, or within a target range of analyte concentration levels, as determined by one or more processors of device 104. In some embodiments, the determination that a level is within a target range would be based on the measured level being within an upper and lower threshold. Levels below the target or target range are represented here by a blue bubble, levels above the target analyte concentration level are represented by a red bubble, and levels at the target analyte concentration level are represented by a green bubble. The white bubble 304 is static, as shown in the embodiments described herein, and contains a numerical value of the current analyte concentration level near the center of the bubble 304. In other embodiments, the concentration level may be represented using other visual cues, such as dots or clusters of objects, bars of a bar graph embedded in the bubble, or numbers located in different parts of the bubble. As will be further discussed below, the sensor life indicator 360 is a graphical overlay that provides information about the period of time the analyte sensor will continue to operate. The graphical user interface 300 also includes an arrow indicator 310, which may include a single arrow, a double arrow, a flashing arrow, and any other directional indicators. In some examples, the arrow may move to indicate the directional trend of the most recent analyte measurement.

[0029] The lower part of the interface 300 includes a history graph (history diagram) 318 of analyte measurements. This history graph may include a timeline (time axis) 320, a schematic representation of analyte measurements (schematic representation of analyte measurements) 322, analyte value axis labels 324, a target analyte concentration band 326, and an animation 328 of the current analyte reading. The analyte measurements 322 in the history graph 318 correspond to specific measurements taken by the analyte sensor described above, and these schematic representations of analyte measurements 322 are displayed in the history graph 318 to indicate the corresponding time when each analyte measurement was acquired, as provided by the timeline 320.

[0030] The current analyte reading animation 328, sometimes also called the "now dot," may be configured to pulsate (constantly switch between) the depiction in Figure 3A and the depiction in Figure 3B. In one or more embodiments, the current analyte reading animation 328 (or "now dot") may stop pulsating or disappear to indicate an error or lack of connectivity with the analyte sensor. In one or more embodiments, the now dot may include a halo 330 surrounding the central dot, and only the halo 330 may pulsate. The now dot 328 may also change color, blink at different speeds, etc., to the extent that the color and speed indicate conditions such as the analyte concentration level relative to a predetermined threshold concentration. For example, in Figure 3A, the now dot 328 is green because the current analyte measurement is within the upper and lower thresholds defining the analyte concentration band 326. If the current analyte value is outside the analyte concentration band 326, the current dot 328 may change color. For example, the current dot 328 may be displayed in red if the current analyte value is above the analyte concentration band 326, and in blue if the current analyte value is below the analyte concentration band 326. In addition, an icon indicating loss of connection to the analyte sensor may be further presented in the graphical user interface 300. In other embodiments, the broken link icon may be displayed after a period of absent data, for example, one minute. In such cases, the broken link icon may indicate loss of connection or that the sensor is connected but delivering unstable (e.g., invalid or unusable) readings.

[0031] The timeline 320 of interface 300 also includes event displays 340 and 342. Event displays 340 and 342 represent information related to CGM-related events that have occurred, such as physical activity (e.g., sports, walking, running, swimming, etc.), dietary information (e.g., identification of the meal, type of food consumed, amount of carbohydrates consumed, etc.), insulin information (e.g., amount and timing of insulin intake), and general user notes about other events that may affect the CGM readings. The user can input events into device 104 by selecting an icon 352 from the navigation bar 350 at the bottom of interface 300. When an event is input into device 104, the timeline 320 may be updated to include a display of that event. Each event display on the timeline 320 may be associated with a time and an analyte measurement.

[0032] When multiple events are associated with a particular time, the event displays shown on the timeline may be configured to indicate this fact. For example, in Figure 3A, event display 340 contains the number "3" and event display 342 contains the number "1". The "3" in event display 340 represents the number of events associated with that event display. Each event display 340 and 342 may be configured to be a selectable icon. As will be discussed further below, depending on the user's selection of an event display, device 104 may display an event log that provides detailed information about one or more events associated with the selected event display.

[0033] The time frame of the history graph 318 may be set to a specific default value. The timeline 320 in Figure 3A shows that the history graph 318 has a time frame spanning four hours. However, the default time frame of device 104 can also be set to one of several different time frames, such as one hour, four hours, eight hours, twelve hours, twenty-four hours, or longer. The ability to edit the default time frame may be presented on the home screen, where the user may enter the desired default time frame for the history graph 318.

[0034] Device 104 may also be configured to adjust the time frame of the timeline 320 according to one or more user inputs. For example, device 104 may have a touch-sensitive display device that can recognize a user input in which the user touches the history graph 318 or a portion of the display screen nearby and pinches with two fingers. Upon receiving this user input, device 104 may modify the history graph 318 to correspond to the new time frame according to the pinch command. For example, a user of device 104 may provide a pinch command to the interface 300 shown in Figure 3A. In response to this pinch command, device 104 may change the displayed interface 300 to the graphical user interface 300' shown in Figure 3B. The graphical user interface 300' is modified to include a modified history graph 318' containing a modified set of analyte measurements 322' in a graphical representation corresponding to the modified time frame of the timeline 320'. In particular, the time frame of timeline 320' is approximately 12 hours at this point, rather than the 4-hour time frame of timeline 320 on interface 300. The amount of change in the time frame can be based on the size or number of thumb commands provided by the user. In addition, device 104 may have settings that thumb commands cause a smooth transition from one time frame to another, or that thumb commands cause the history graph 318 to jump from one time frame to another. For example, device 104 may be configured so that thumb commands automatically jump out (switch) a timeline with a 4-hour time frame to an 8-hour, 12-hour, or 24-hour time frame. User input to device 104 that transitions from a shorter time frame to a longer time frame can be called "zooming out" of the timeline, and transitioning from a longer time frame to a shorter time frame can be called "zooming in" on the timeline.

[0035] When displaying a historical graph of analyte measurements, device 104 may be configured to present event data according to the content of the time frame in the historical graph. For example, event displays 340 and 342 in Figure 3A are combined into a single event display 344 within the timeline 320' in Figure 3B. In this case, event display 344 displays the number "4" to indicate that it corresponds to four separate events. When determining whether events should be combined into a single event display, device 104 may identify whether the set of events are within some predetermined proximity range to each other within the time frame of the displayed timeline. If one or more events are determined to be within a predetermined proximity range for a given time frame, those events may be displayed as part of a single event display.

[0036] If a set of events is displayed using two or more separate event displays on a timeline, a predetermined proximity may be based on the distance between the event displays. Each event may be associated with a time or time range that determines the event's position on the timeline. If multiple events are recorded simultaneously or overlapping at the same time, device 104 may present these events on the timeline using a single event display. For example, in Figure 3A, event display 340 represents three events all associated with the same time. As can be seen in timeline 320, the time of the event associated with event display 340 is between 5 p.m. and 6 p.m. With respect to event display 342, it is associated with an event that occurred immediately after 6 p.m. With respect to timeline 320, event displays 340 and 342 are far enough apart from each other that the event associated with event display 342 may be displayed separately from event display 340. However, in Figure 3B, timeline 320' has a time frame that requires event displays 340 and 342 to be within a predetermined proximity range to each other. Based on this determination, device 104 combines the events associated with event displays 340 and 342 to form a single event display 344.

[0037] Identifying events within a predetermined proximity range may be based on the determination that, if separate event displays were placed on the timeline at the times corresponding to those events, those event displays would touch or overlap. For example, the four events associated with event display 344 are associated with times at which, if each event were given its own display, it would produce overlapping event displays. Based on this determination, device 104 displays the four events together with a single event display 344. Thus, in response to user input for device 104 to zoom out from timeline 320 in Figure 3A to timeline 320' in Figure 3B, event displays 340 and 342 may be combined into a single event display 344. The predetermined proximity may take the form of a specific time range relative to the overall time frame of the timeline. This time range may correlate with the length of the time frame. For example, with respect to timeline 320 in Figure 3A, the predetermined proximity between events may be a 20-minute time range, in which case all events within 20 minutes of each other are displayed in relation to a single event display. With respect to the timeline 320' in Figure 3B, the predetermined proximity may be 1 hour, in which case all events within 1 hour of each other are displayed in relation to a single event display.

[0038] In addition, the user of device 104 may provide user input corresponding to the "zoom in" command, such as by providing a reverse pinch touch command. When device 104 zooms in on the timeline, event displays associated with multiple events may be separated into two or more event displays. For example, when device 104 displays interface 300' in Figure 3B, the user may provide device 104 with a reverse pinch touch command so that device 104 transitions to interface 300 in Figure 3A. When performing this transition, device 104 may determine that one or more events in event display 344 are no longer within a predetermined proximity range of each other when displayed in the timeline 320. Based on this determination, event display 344 may be divided into two or more separate event displays 340 and 342. The history graph may also be scrollable in response to user input. For example, a user may slide (swipe) their finger to the right on the touch display device of device 104 to scroll through the history graph 318 in Figure 3A, viewing previous analyte measurements while remaining within a 4-hour time frame. The history graph may be configured to be scrollable within a predetermined period, such as the most recent 24 hours.

[0039] Each event stored or accessed by device 104 may be associated with an analyte measurement and a time. The graphical user interface history graph 318 is configured to allow the user to identify how CGM-related events have affected the user's analyte measurements over time. Thus, the event display is shown in the history graph in a manner that allows the user to identify the relative timing of the events to the user's analyte measurements. When events are grouped into a single event display, the disclosed system may identify a time range for the grouped events and identify a central position based on that time range. This central position may be based on the average time of the grouped events or on the midpoint between two of the events. For example, device 104 may identify the earliest and latest events in a set of events that are grouped together to form a single event display. Device 104 may then identify the midpoint in time between the earliest and latest events as a point on the timeline where the event display is placed. By displaying events in this way, users can view historical graphs over longer timeframes while still being able to identify general trends in analyte measurements related to those events.

[0040] The user may select a portion of the history graph 318 to view analyte measurements and event data in relation to a specific time. User selection may be made by touching or dragging (dragging) the user's finger along the area of ​​the analyte measurement 322 in the graphical representation. For example, Figures 4A and 4B include graphical user interfaces 400 and 400' where the user has selected a point in the history graph 318. In Figure 4A, the user has last touched a portion of the history graph 318 where the analyte measurement 322 in the graphical representation is associated with an event display 340. Point 410 indicates the selected analyte measurement 322 in the graphical representation, and line 412 extends to the timeline 320 to indicate the time of the selected analyte measurement 322. In one or more embodiments, point 410 may be color-coded based on the current analyte measurement in the graphical representation it represents. For example, measurements within the analyte concentration band 326 may be represented by green dots 410, while measurements above and below the analyte concentration band 326 may be represented by red and blue dots 410, respectively. In Figure 4A, dots 410 and line 412 indicate that the selected analyte measurement is associated with event display 340. A schematic overlay 402 may also be displayed in relation to the selected dot 410. The schematic overlay 402 may include the analyte measurement 404, a trend arrow 408, and a time 420 corresponding to the selected dot 410. The analyte measurement 404 may be color-coded to indicate whether the selected dot corresponds to an analyte measurement above, below, or within a specified range of analyte values. For example, the analyte measurement 404 may be presented in green when dot 410 corresponds to an analyte measurement 404 within the target analyte concentration band 326. Values ​​above the target analyte concentration band 326 may be shown in red, for example, and values ​​below the target analyte concentration band 326 may be shown in blue. The trend arrow 408 is shown to indicate how the analyte value is changing at point 410.

[0041] Device 104 may determine that the selected point 410 corresponds to an analyte measurement associated with the event display 340. Based on this determination, the graphical representation overlay 402 may include event descriptions 406a-c that provide information identifying the nature of one or more events to which the event display 340 is associated. For example, event description 406a represents that the user entered a note, event description 406b represents the event that the user consumed 80 grams of carbohydrates, and event description 406c represents the occurrence of 35 minutes of physical activity. The graphical user interface may be configured to allow the user to select the type of information displayed within the graphical representation overlay 402. For example, the user may configure the graphical representation overlay 402 to display only analyte measurement data without displaying event descriptions 406a-c. Event information can be accessed through the event log even if it is not displayed in relation to the graphical representation overlay 402, as described below.

[0042] In Figure 4B, the user has selected point 410' corresponding to event display 344. Therefore, a schematic representation overlay 402' similar to the schematic representation overlay 402 discussed in relation to Figure 4A is presented. As seen in Figure 4B, the schematic representation overlay 402' here includes four event descriptions 406a to d. In addition, given that the midpoint of the four events associated with event display 344 is different from the midpoint of the three events associated with event display 340, the time 410' and analyte measurement value 404' displayed in the schematic representation overlay 402' are slightly different from those displayed in the schematic representation overlay 402 in Figure 3A.

[0043] If a user wishes to view event displays positioned at the precise time of each individual event, they may zoom in on the timeline until all event displays are divided to represent individual events, and the historical graph can be viewed to show more detailed data on the effect of each event on the recorded analyte measurements.

[0044] In addition to, or instead of, zooming in on the history graph, the user may receive more detailed event data by selecting an overlay 402 of a schematic representation that appears in relation to a selected point 410 to bring the event log to a display. For example, Figure 5A is a graphical user interface 500 that displays a patient's event log. The event log may include a calendar 510 with selectable dates, a daily history graph 512 for displaying a graph (schematic) of analyte measurements taken on a particular day, and a scrollable list of event lists 502a-c. The history graph 512 may appear as if using color-coded lines 514, such that analyte measurements appear in different colors in the scheme depending on whether the value is within the target range (e.g., appears in green), above the target range (e.g., appears in red), or below the target range (e.g., appears in blue). Each event list 502a-c may provide information identifying the type of event, the time associated with the event, and other CGM-related data associated with the event. The event lists may be presented in reverse chronological order.

[0045] In addition, each event list 502a to c may include its own trend diagram 504. The trend diagram 504 may include a schematic representation of the analyte measurement value 506 and an icon 508 indicating the time at which the event occurred relative to the schematic representation of the analyte measurement value 506. The icon 508 may take the form of any schematic display or marking that indicates the occurrence of the event within the schematic representation of the analyte measurement value 506. The schematic representation 506 of the analyte measurement value may be color-coded so that a portion of the schematic representation indicates that the analyte measurement value is above, below, or within the target range of the analyte value. For example, in the trend diagram 504, the left side of the schematic representation 506 may appear in blue to indicate that this portion is below the target range of the analyte value, the central portion of the schematic representation 506 may appear in green to indicate that this portion is within the target range of the analyte value, and the right side of the schematic representation may appear in red to indicate that this portion is above the target range of the analyte value.

[0046] Analyte measurements may be presented in relation to trend diagrams 504, but the shape and / or color of the trend diagram 504 may be sufficient to show how a particular event resulted in the analyte measurements. In particular, trend diagrams 504 may be configured to include multiple analyte measurements that occurred before the event and multiple analyte measurements that occurred after the event. The amount of analyte measurements before and after the event may be based on a predetermined period or a predetermined number of measurements. The period before the event can be selected to be a sufficient amount of time to show whether the user's analyte measurements were rising, falling, or stable before the event. The period after the event can be selected to be a sufficient amount of time to show whether the event affected the user's short-term analyte measurements. For example, trend diagram 504 includes a schematic representation of analyte measurements 506 corresponding to the period between one hour before the event and two hours after the event. Thus, each event list 502a-c may have its own trend diagram 504 corresponding to the period before and after that particular event. Thus, the user may use the zoomed-out view of the history graph 318 to determine the overall impact of multiple events on the user's analyte measurements over a longer period, and access event logins to determine the effect of specific events on a subset of the user's analyte measurements.

[0047] Interface 500 may also include icons 530, which can be selected by the user to add additional event data to the event log. For example, Figure 5B is an interface 500' that may be displayed by device 104 when icon 530 is selected. Interface 500' displays several event icons 520a to e, each representing a different type of event. The user may select the appropriate event and then enter data related to that event, including an identification of the time or time range in which the event occurred. Returning to Figures 3A to B, when an event is added to the event log, device 104 may update the history graph 318 to include the added event in one of the event displays shown on the timeline 320.

[0048] In addition to the features described above, the device 104 in Figures 1 and 2 may receive sensor lifetime data from the analyte sensor 112. In particular, analyte sensors such as sensor 112 have a specific date and time when the sensor expires. Sensor expiration without replacement can result in gaps in a patient's analyte measurement data, which can negatively impact the user's and the user's physician's ability to track the patient's condition. Therefore, it is important that user 102 and others can track the sensor lifetime of the analyte sensor 112. According to embodiments disclosed herein, the graphical user interfaces of devices 104 and 204 may provide users 102 and 202 with a rapid, continuous, and non-intrusive display of the sensor lifetime data of the analyte sensor 112.

[0049] For example, the graphical user interface 300 in Figure 3A includes an overlay of a sensor life indicator 360 that shows the remaining time for the user's analyte sensor. Specifically, the numbers displayed within the sensor life indicator 360 may indicate the number of days, hours, or minutes remaining before the analyte sensor expires. The unit of time represented by the numbers (e.g., days, hours, or minutes) may be represented by at least a color-coded portion of the sensor life indicator 360. For example, the numbers within the sensor life indicator 360 may appear in black when they represent the number of days remaining in the sensor life, and in red when they represent the number of hours or minutes remaining in the sensor life.

[0050] The remaining time before the sensor expires may also be indicated by a graphic representation surrounding the displayed number within the sensor life indicator 360. For example, in Figure 6, the sensor life indicator 360 provides sensor life data in days. The sensor life indicator 360 includes a ticker marker 604 whose appearance changes according to the number of days remaining until the sensor expires. On the left side of Figure 6, the sensor life indicator 360 includes a displayed number 602 and several ticker marks 604 surrounding the displayed number 602. Each day, the displayed number 602 counts down the remaining days until the sensor expires. The displayed number 602 is displayed in black, indicating that it represents days rather than hours or minutes. In addition, the appearance of one of the ticker marks 604 changes in relation to the number of days remaining. For example, on the right side of Figure 6 is the sensor life indicator 360', which shows the appearance of the sensor life indicator 360 after 9 days have elapsed. The displayed number 602' is now "7," indicating that there are 7 days of sensor life remaining, and the nine ticker marks 604' appear in light gray, while the seven ticker marks 604 continue to be displayed in bold. Thus, the sensor life indicators 360 and 360' provide the user with both a numerical and graphical representation of the number of days remaining before the sensor fails.

[0051] In Figure 7, the sensor life display 360 provides sensor life data in units of time. On the left side of Figure 7, the sensor life display 360 includes the displayed number 702 and ticker marks 704. The displayed number 702 is a red "24," indicating that there are 24 hours left until the sensor fails. Every hour, the displayed number 702 counts down the remaining time until the sensor fails. In addition, the sensor life display 360 includes 24 ticker marks 704, which appear in red and surround the displayed number 702. The appearance of each ticker mark 704 changes every hour. For example, the right side of Figure 7 shows the sensor life display 360', which represents the appearance of the sensor life display 360 after 20 hours. The displayed number 702' is here a red "4," indicating that there are 4 hours of sensor life remaining. In addition, several ticker marks 704' appear in gray, with only four ticker marks 704 remaining in red. Therefore, the sensor life indicators 360 and 360' in Figure 7 provide the user with both a numerical and graphical representation of the time remaining before the sensor fails.

[0052] In Figure 8, the sensor life display 360 provides sensor life data in minutes. On the left side of Figure 8, the sensor life display 360 includes a displayed number 802 surrounded by a solid circle 804. The displayed number 802 is a red "60," which, in combination with the solid circle 804, indicates that there are 60 minutes left until the sensor fails. Every minute, the displayed number 802 counts down the remaining minutes until the sensor fails. In addition, the sensor life display 360 may include a pie chart showing the percentage of the last hour of sensor life that has elapsed. For example, the right side of Figure 8 is the sensor life display 360', which shows the appearance of the sensor life display 360 after 30 minutes have elapsed. The displayed number 802' is here a red "30," indicating that there are 30 minutes of sensor life remaining. In addition, the sensor life display 360' includes a pie chart 806. The pie chart 806 is half filled, indicating that half of the last hour of sensor life has elapsed. Therefore, the sensor life indicators 360 and 360' in Figure 8 provide the user with both a numerical and graphical representation of the remaining time before the sensor fails.

[0053] According to embodiments of the present disclosure, the sensor life indicators 360, 360' shown in Figures 6-8 may be displayed as an overlay on a specific portion of the display screen of the device 104, as shown in Figures 3A-B. By displaying a numerical and graphical representation of the remaining sensor life period as described above, the sensor life indicator 360 may be presented as a small, unobtrusive overlay that does not obscure other relevant information provided on the graphical user interface. For example, by using color coding, tick markers, and pie charts to specify units of time, the sensor life indicator 360 can provide the user with the remaining time without requiring the display of a single number or other text. However, in one or more embodiments, the sensor life indicator 360 may be configured to switch from a compact mode, as shown in Figure 3A, to an extended mode, as shown in Figure 9.

[0054] Device 104 may receive user input to toggle the sensor life display 360 between compact mode and extended mode. For example, the user may tap the sensor life display 360 in Figure 3A, and in response to this user input, device 104 may present the sensor life display 360 in extended mode, as shown in the graphical user interface 900 in Figure 9. In extended mode, the sensor life display 360 may continue to display the ticker mark 604 and the displayed digit 602, but may also include a unit display 902 and an expiration date 904. The unit display 902 may include text identifying the unit represented by the displayed digit 602. For example, the unit display 902 may include the text "Days Left", "Hours Left", or "Minutes Left", depending on the unit of time represented by the displayed digit 602. The expiration date 904 may include identification of the month, day, year, and time of sensor failure, as shown in Figure 9. The user of device 104 may collapse the extended sensor life display 360 back to compact mode by tapping the extended sensor life display. In one or more embodiments, the extended sensor life display may automatically collapse (terminate) after a predetermined period of time, such as 5 seconds.

[0055] If the device 104 determines that the sensor lifespan is within a predetermined time frame, it may display a low sensor lifespan warning, such as the “Urgent Low” banner 1002 shown in the graphical user interface 1000 of Figure 10. When the analyte sensor has expired, the device 104 may display a home screen message indicating that the sensor has expired, and the sensor lifespan display 360 may no longer be displayed. For example, Figure 11 shows a graphical user interface 1100 that displays a message indicating that the sensor has expired and needs to be replaced. This message may include a banner 1102. In addition, the device 104 may display a selectable icon 1104 that can be used to replace the expired sensor with a new one. For example, the user may attach a new analyte sensor and tap the icon 1104. In response to tapping the icon 1104, the device 104 may search for and pair with the new analyte sensor. Once paired with the new analyte sensor, the device 104 may receive sensor lifespan data for the new analyte sensor. Next, using the received sensor lifetime data, a sensor display 360 may be generated based on the expiration date and time of the new analyte sensor.

[0056] The disclosed system may determine whether the analyte sensor 112 has exceeded the upper or lower sensor limit. If the analyte sensor 112 is above or below the sensor limit, the device 104 may provide an indication that the sensor is above the sensor limit and that an accurate reading cannot be provided. For example, in Figure 12, the graphical representation of the analyte measurement 322 does not appear above the sensor limit 1202. Instead, the graphical user interface 1200 displays a vertical band 1204. The width of the vertical band 1204 corresponds to the period on the timeline 320 when the analyte sensor was above the sensor limit. The vertical band 1204 may be presented as a vertical color gradient, as shown in Figure 12. The vertical band 1204 may be color-coded; for example, the vertical band 1204 may be red when the analyte sensor is above the sensor upper limit, or blue when the analyte sensor is below the sensor lower limit.

[0057] Device 104 may display color-coded push notifications in relation to high and low sensor readings. For example, a push notification may appear with a blue icon when the analyte sensor measurement falls below a lower target threshold, and a push notification may appear with a red icon when the analyte sensor measurement exceeds a higher target threshold. These target thresholds may be set by the user using the graphical user interface of device 104.

[0058] Figure 13, which may be called the “My Progress” screen, provides a graphical user interface 1300 that may be displayed on device 104 to provide the user with an overview of their analyte measurements over a desired period of time. The graphical user interface 1300 may include several icons 1302 representing different timeframes, e.g., 7, 14, 30, 60, and 90 days. The user may select one of the icons 1302 to view an overview of their analyte measurements over a selected period. In Figure 13, the user has selected icon 1302 corresponding to the 90-day overview. Thus, the graphical user interface provides average glucose 1304 corresponding to the user’s average glucose level over the 90-day period. The display also includes percentage values ​​1310 representing the percentage of time over the 90-day period during which the user’s analyte values ​​were within, below, or above the user’s desired target range. The user may select an alternative setting in which the percentage value 1310 is presented as an absolute value of time (e.g., hours and minutes).

[0059] A graphical representation 1308 of these percentages is also provided within the display device. As described above, the same color coding may be used for the graphical representation 1308 and the percentage values ​​1310, where green represents values ​​within the target range, red represents values ​​above the target range, and blue represents values ​​below the target range. In addition, the graphical user interface 1300 may also display the user's Glucose Management Indicator percentage over a desired time range.

[0060] Information presented in the graphical user interface 1300 over a specific period may be presented alongside previous periods so that the user can compare their progress. For example, the graphical user interface 1300 may include a toggle switch that allows the user to activate a comparison mode within the "My Progress" screen. In Figure 14, the graphical user interface 1300 has been modified to include summary information for two periods. Annotation box 1402 provides a summary of analyte measurements taken during the most recent 90-day period, and annotation box 1404 provides a summary of analyte measurements taken during the previous 90-day period. As discussed above, the analyte values ​​may include color coding of measurements that are within, above, or below the target range. In this way, the user can easily track their progress over different periods using the color-coded graphical display.

[0061] Returning to Figure 2, in one or more embodiments of this disclosure, user 102 may grant access to one or more individuals to certain CGM-related data, such as analyte measurement data, event data, and sensor data. Identified individuals may access this CGM-related data on their own devices using an application such as a "Follower App" configured to provide user 102's CGM-related data. For example, user 202 may download a Follower App to device 204. The Follower App may be configured to associate device 204 with user 202. For example, the Follower App may require user 202 to enter identification information (e.g., user ID) and verification information (e.g., password or biometric data) to associate device 204 with user 202. Devices 104 and 106 may similarly be associated with user 102. User 102 may then use device 104 or 106 to grant user 202 access to user 102's CGM-related data.

[0062] Permission for user 102 to access user 202 may be achieved by device 104 or 106 sending access permission data to a remote computer 210. The access permission data may include user identification information for both user 102 and any individual to whom user 102 has granted access, and this data may be stored on computer 210. For example, the remote computer 210 may be a server that can be accessed by device 204 via a follower app. Device 204 may send user identification and verification information for user 202 to computer 210. User identification information for user 202 may be compared with user identification information contained in the stored access permission data. If user identification information for user 202 matches the user identification information provided in the access permission data, computer 210 may send user 102's CGM-related data to device 204. If user identification information for user 202 does not match any of the identification information contained in the stored access permission data, CGM-related data for other users will not be provided to user 202 via computer 210.

[0063] The CGM-related data of user 102 sent to device 204 may be a subset of user 102's CGM-related data selected by user 102 as accessible to user 202. Therefore, the follower application running on device 204 provides user 202 with only the selected subset of user 102's CGM-related data. For example, user 102 may be granted access to sensor lifetime data and analyte measurement data, but not to event data, or may only be granted access to specific types of events. Any CGM-related data that user 202 is granted access to can be displayed on device 204 in the same manner as described above. For example, the follower application may display a sensor lifetime display 360 having the same appearance as the sensor lifetime display 360 discussed above. Similar to the sensor lifetime display 360 displayed on device 102, the sensor lifetime display 360 displayed on device 104 may be controlled to switch between collapsed mode and expanded mode. In addition, device 104 may display the same sensor life notification as discussed above for device 102. The sensor life display 360 may remain visible as an overlay when user 202 navigates to different screens within the follower app displayed on device 204.

[0064] In one or more embodiments, devices 104 and 204 may receive and display push notifications regarding sensor lifetime data. For example, computer 210 may determine that the analyte sensor 112 for user 102 is within a predetermined period and send push notifications to devices 104 and 204 that provide a statement of how much time remains before the analyte sensor 112 expires. For example, computer 210 may send a push notification if it determines that the analyte sensor 112 has 3 days, 24 hours, and / or 2 hours remaining before expiring.

[0065] As discussed above, user 102 may replace their analyte sensor 112 with a new analyte sensor 112. The new analyte sensor 112 may be paired with a user device such as device 104. Once paired with the new sensor 112, device 104 may send sensor lifetime data for the new analyte sensor 112 to computer 210. Computer 210 may then send sensor lifetime data for the new analyte sensor 112 to device 204 according to access permission data previously stored on computer 210. Upon receiving sensor lifetime data for the new analyte sensor 112, device 204 may update the displayed sensor lifetime display to correspond to the expiration date and time of the new analyte sensor 112.

[0066] Returning to Figure 2, user 202 may use device 204 to track CGM-related data of multiple users 102, each having analyte measurements acquired by sensor 112. Each user 102 may grant user 202 access to at least some subset of the CGM-related data, as described above. Computer 210 may receive each user's CGM-related data as provided by each user device 104, and computer 210 may transmit each user's received CGM-related data to device 204 according to the access rights granted to user 202 by each user 102. In one or more embodiments, device 204 may include a follower app configured to display multiple users 102 who are permitted to access the CGM-related data for user 202. For example, Figure 15 shows a scrollable graphical user interface 1500 displayed on device 204 to show all users 102 (not shown) that user 202 (not shown) is following. Each user may be listed in an individual user list 1502. Each user list 1502 may include identification information such as the name of the followed user, and a status display 1504 which may provide the latest analyte measurement value of the followed user, indicating whether the analyte measurement value is increasing, decreasing, or stable. Each user list 1502 may also include a time display 1506 which indicates the time when the last data was received for that user. For example, user list 1502a identifies the followed user as "John Smith". Status display 1504a indicates that John Smith's analyte measurement value is 68 mg / dl and is decreasing, and time display 1506a states that this measurement value is current because it was taken "now". The time display may identify the number of hours or minutes since the last analyte measurement was received, such as time display 1506b. If more than one day has passed since the last measurement, the time display may provide the date and time of the last analyte measurement, as provided using time display 1506c.

[0067] Status display 1504 may also indicate whether the user's sensor is above or below the sensor limit. For example, status display 1504d states that the sensor is "HIGH," meaning that the sensor is above the sensor limit. User list 1502 and status indicator 1504 may be color-coded as described above to indicate whether the latest analyte measurement of a followed user is within, above, or below a predetermined range of analyte values. In this way, a user of the follower app can quickly assess the status of multiple users on a single display screen. User list 1502 may also indicate whether data is unavailable to the user, as can be seen for user list 1502e, in which case the time display indicates that no data is available, and status display 1504e does not contain any numerical values. User list 1502 may also include status display 1504 with a high or low glucose warning diagram. For example, user list entry 1502f includes a "Low Glucose Alert" accompanied by an exclamation mark icon.

[0068] An arbitrary user list 1502 may be selected by a user of the follower app to access detailed information about that user. For example, Figure 16 is a graphical user interface 1600 that may be displayed on device 204 when a particular user list is selected. The graphical user interface 1600 may include features described in relation to the graphical user interface 300 of Figure 3A. For example, the graphical user interface 1600 includes a sensor life display 360, a history graph 318, a current dot 328, a graphical representation of analyte measurements 322, a target analyte band 326, and a timeline 320. The display also includes the user's name, a time display 1506, a status display 1504, and a color-coded history list 1606 of analyte values. This history list 1606 may provide analyte values ​​at a specific time selected by the user of device 204. In addition, if the user of device 204 is permitted to access event data, the history graph 318 may include event displays such as an event display 344. The user may zoom in and out of the history graph 318 as described above.

[0069] Figure 17 is a flowchart 1700 corresponding to the functions that can be performed by one or more processors of the system described above in Figures 1 and 2 to collect analyte data and display it on a mobile device such as device 104. Multiple processors may be used to perform the disclosed functions, including performing some of the processing on a remote computer such as computer 210 discussed in Figure 2.

[0070] As described above, the mobile device may be paired with an analyte sensor worn by the user (block 1702). The mobile device may receive and store analyte measurement data collected and transmitted by the analyte sensor (block 1704). The mobile device may receive event data (block 1706). As described above, event data may be entered by the user of the mobile device, and event data may include CGM-related data such as information on insulin ingested by the user, physical activity, food consumed, and CGM-related notes provided by the user. Event data may include data identifying the time of the event, including the time the event was recorded. The user of the mobile device may provide the mobile device with user input commands to display analyte measurement data in a history graph corresponding to a first time frame (block 1708). As described above, the first time frame may be one of several default time frames selected by the user, or it may correspond to a time frame previously viewed by the user. The mobile device may identify several events associated with a time or time range corresponding to the first time frame (block 1710). In block 1712, a determination is made as to whether two or more events are within a predetermined proximity range of each other within a first time frame. As described above, the predetermined proximity may be the proximity of event representations corresponding to events in the timeline of the first time frame. The predetermined proximity may also be defined by the time range between the two events. The time range constituting the predetermined proximity may be based on the length of the first time frame. In particular, the time range used as the predetermined proximity may be correlated with the length of the first time frame such that the longer the first time frame, the longer the time range with respect to the predetermined proximity.

[0071] The mobile device may provide a diagram for display that includes one or more event displays based on the determination of the proximity of identified events (block 1714). As described above, if it is determined that two or more events are within a predetermined proximity range to each other along the timeline of the first time frame, the event display may correspond to multiple events. In block 1716, the mobile device receives user input that corresponds to a command for the displayed diagram to move from the first time frame to the second time frame. In response to this command, the mobile device determines whether events that occurred in the second time frame are within a predetermined proximity range to each other with respect to the second time frame (block 1718). As described above, if the user input corresponds to zooming in on the diagram, some events that were previously within a predetermined proximity range in the first time frame are no longer within the predetermined proximity range in the second time frame. Alternatively, if the user input corresponds to zooming out on the diagram, some events that were not within a predetermined proximity range in the first time frame are now within a predetermined proximity range in the second time frame. In block 1720, the mobile device provides for display a diagram of a second time frame, which includes an event display based on a determination of the proximity of events to each other. When displaying the event display in the second time frame, one or more events may be displayed in the displayed diagram in relation to the new time and analyte measurement values, compared to the time and analyte measurement values ​​in which the events were displayed in the first time frame.

[0072] Figure 18 is a flowchart 1800 which may be executed by a disclosed system, such as the system described in Figure 2. In blocks 1802 and 1804, one or more processors, such as the processors of one or more servers, store identification data for a first user associated with a first device and identification data for a second user associated with a second device. As described above, the connection between the identification data and the device associates the device with a specific user. In block 1806, one or more servers receive analyte sensor data from an analyte sensor used by the first user. The analyte sensor data may include analyte measurements, event data, and sensor lifetime data. In block 1808, one or more processors receive access permission data from the device associated with the first user. The access permission data identifies the second user as having access rights to a specific subset of the first user's analyte sensor data and event data. One or more servers transmit a specified subset of the first user's analyte sensor data to a second device according to access permission data (block 1810). The transmission of the subset of analyte sensor data may be automatically pushed to the second device or provided in response to a request from the second device.

[0073] In block 1812, the second device receives the analyte sensor data transmitted by the first user, and in block 1814, the second device provides a sensor lifetime indicator overlay for display according to the analyte sensor data. As described above, the sensor lifetime indicator may be color-coded to specify the unit of time represented by the sensor lifetime indicator. One or more servers may receive updated sensor lifetime data from the device associated with the first user (block 1816). For example, the first user may pair the first device with a new analyte sensor. Upon pairing with the new sensor, the first device may transmit the analyte sensor data for the new analyte sensor to one or more servers. In block 1818, one or more servers transmit the updated sensor lifetime data to the second device according to stored access permission data. The second device may then display an updated sensor lifetime indicator based on the updated sensor lifetime data (1820).

[0074] Embodiments are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments. It will be understood that each block in a flowchart and / or block diagram, and combinations of blocks in a flowchart and / or block diagram, may be implemented by computer-readable program instructions.

[0075] These computer-readable program instructions may be provided to the processor of a general-purpose computer, a dedicated computer, or other programmable data processing device, and the machine may generate means for instructions executed via the processor of the computer or other programmable data processing device to perform functions / operations specified in one or more blocks of a flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that can instruct computers, programmable data processing devices, and / or other devices to function in a particular manner, thereby including a product containing instructions that perform modes of functions / operations specified in one or more blocks of a flowchart and / or block diagram.

[0076] The above computer-readable program instructions may be loaded onto a computer, another programmable data processing device, or another device, and a series of operations (arithmetic processes) may be executed on that computer, other programmable device, or other device to generate a computer implementation process, which in turn may execute instructions on the computer, other programmable device, or other device that perform functions / operations specified in the blocks(s) of the flowchart and / or block diagram.

[0077] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in a flowchart or block diagram may represent a module, segment, or instruction portion, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions described in a block may occur in an order different from the order shown in the diagram. For example, two consecutively shown blocks may actually be executed substantially simultaneously, or such blocks may sometimes be executed in reverse order depending on the functionality involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs a specified function or operation, or implements a combination of dedicated hardware and computer instructions.

Claims

1. A method for tracking analyte sensor data generated by at least one analyte sensor, The process of associating a first mobile device with a first user and a second mobile device with a second user using one or more processors, The process of receiving the analyte sensor data in one or more processors, wherein the analyte sensor data includes the analyte measurement value and sensor lifetime data indicating the period during which the at least one analyte sensor continues to operate, The process of receiving input data from a first user in one or more processors that identifies a second user as having access rights to a selective subset of the analyte sensor data, wherein the selective subset of the analyte sensor data includes the sensor lifetime data, The process of providing the second mobile device with the selected subset of the analyte sensor data based on the input data using one or more processors, A step of providing a sensor life display based on the sensor life data for display on a second mobile device, based on the selective subset of the analyte sensor data, wherein the sensor life display includes a sensor life digit indicating the period of time the at least one analyte sensor continues to operate, and the sensor life display is color-coded to indicate the unit of time represented by the sensor life digit. Methods that include...

2. The method according to claim 1, further comprising the step of using one or more processors to switch the display mode of the sensor life indicator between a first mode and a second mode based on input received in the second mobile device.

3. The method according to claim 2, wherein the sensor life display in the first mode comprises the sensor life digit and a plurality of ticker marks surrounding the sensor life digit.

4. The method according to claim 3, wherein the plurality of ticker marks include a set of solid ticker marks and a set of fading ticker marks, and the number of the set of solid ticker marks corresponds to the sensor life digit.

5. The method according to claim 4, wherein when the at least one analyte sensor continues to operate for a period of one hour or less, the sensor life digit represents minutes, and the plurality of ticker marks surrounding the sensor life digit are replaced with a visual representation including a solid line representing the period of one hour or less during which the at least one analyte sensor continues to operate.

6. The method according to claim 5, wherein the visual representation further includes a shaded area within the solid line, and the shaded area corresponds to the amount of time elapsed during the period of one hour or less in which the at least one analyte sensor continues to operate.

7. The method according to claim 2, wherein the sensor life display in the second mode includes a sensor life digit and text identifying the date and time when the at least one analyte sensor expires.

8. The method according to claim 1, wherein the units of time represented by the sensor life digit of the sensor life indicator include days, hours, and minutes, and each unit of time corresponds to a different color.

9. The method according to claim 1, wherein the one or more processors include one or more servers that communicate with the first mobile device and the second mobile device.

10. The process involves pairing the first mobile device with a new analyte sensor, In response to the pairing, the first mobile device automatically transmits updated sensor lifetime data to one or more processors. The process of sending a notification from one or more processors to the second mobile device that the first mobile device has been paired with the new analyte sensor, A step of providing an updated sensor life display for display on the second mobile device based on the updated sensor life data. The method according to claim 1, further comprising:

11. The method according to claim 1, wherein the sensor life indicator is presented as an overlay that remains visible when the second user moves between a plurality of different display devices on the second mobile device.

12. The method according to claim 1, wherein the analyte sensor data is transmitted wirelessly from the at least one analyte sensor to the first mobile device.

13. A process of associating a third mobile device with a third user using one or more processors, A step in which one or more processors receive input data from a third user that identifies the second user as having access rights to the selective subset of the analyte sensor data, wherein the selective subset of the analyte sensor data includes the sensor lifetime data. The method according to claim 1, further comprising:

14. A method for tracking analyte sensor data generated by multiple analyte sensors, The process involves using one or more processors to associate a first mobile device with a first user, a second mobile device with a second user, and a third mobile device with a third user. The process of receiving the analyte sensor data in one or more processors, wherein the analyte sensor data includes analyte measurement values ​​obtained from each of the plurality of analyte sensors, and sensor lifetime data indicating the period during which each of the plurality of analyte sensors continues to operate. The process of receiving first input data from the first user in one or more processors, which identifies the third user as having access rights to the analyte sensor data associated with the first analyte sensor among the plurality of analyte sensors, The process of providing the third mobile device with the analyte sensor data associated with the first analyte sensor among the plurality of analyte sensors, based on the first input data, using one or more processors, The process of receiving a second input data from the second user in one or more processors, which identifies the third user as having access rights to the analyte sensor data associated with the second analyte sensor among the plurality of analyte sensors, The process of providing the third mobile device with the analyte sensor data associated with the second analyte sensor among the plurality of analyte sensors, based on the second input data, using one or more processors, A step of providing, for display on the third mobile device based on the analyte sensor data, a list of users among a plurality of users who have permitted the third user to access the analyte sensor data associated with a specific analyte sensor among the plurality of analyte sensors corresponding to the user, wherein the list includes at least a first individual user list for the first user and a second individual user list for the second user, A step of providing a first sensor life display based on the sensor life data associated with the first analyte sensor among the plurality of analyte sensors for display on the third mobile device based on the analyte sensor data, A step of providing a second sensor life display based on the sensor life data associated with the second analyte sensor among the plurality of analyte sensors for display on the third mobile device based on the analyte sensor data. A method comprising the first sensor life indicator and the second sensor life indicator each include a sensor life digit indicating the period during which the first analyte sensor and the second analyte sensor of the plurality of analyte sensors continue to operate, and the first and second sensor life indicators are color-coded to indicate the unit of time represented by the sensor life digit.

15. The method according to claim 14, further comprising the step of using one or more processors to switch between a first mode and a second mode when displaying at least one of the sensor life indicators, which is selected from the first sensor life indicator and the second sensor life indicator, based on input received in the third mobile device.

16. The method according to claim 15, wherein the first mode comprises a sensor life digit and a plurality of ticker marks surrounding the sensor life digit.

17. The method according to claim 16, wherein the plurality of ticker marks include a set of solid ticker marks and a set of fading ticker marks, and the number of the set of solid ticker marks corresponds to the sensor life digit.

18. The method according to claim 17, wherein when the first analyte sensor and the corresponding analyte sensor among the plurality of analyte sensors operate for a period of one hour or less, the sensor life digit represents minutes, and the plurality of ticker marks surrounding the sensor life digit are replaced with a visual representation including a solid line representing the one hour or less during which the corresponding analyte sensor among the plurality of analyte sensors operates.

19. The method according to claim 18, wherein the visual representation further includes a shaded area within the solid line, and the shaded area corresponds to the amount of time elapsed during the period of one hour or less in which the at least one analyte sensor continues to operate.

20. The method according to claim 15, wherein the second mode includes a sensor lifetime digit and text identifying the date and time on which the first analyte sensor and the corresponding analyte sensor among the plurality of analyte sensors expire.

21. The method according to claim 14, wherein the sensor life digit of the first sensor life indicator and the sensor life digit of the second sensor life indicator include days, hours, and minutes, and each unit of time corresponds to a different color.

22. The method according to claim 14, wherein the one or more processors include one or more servers that communicate with the first mobile device, the second mobile device, and the third mobile device.

23. The process involves pairing at least one of the first mobile device and the second mobile device with a new analyte sensor. In response to the pairing, the process includes automatically transmitting updated sensor lifetime data corresponding to the new analyte sensor from at least one of the first mobile device and the second mobile device to one or more processors, The process includes sending a notification from one or more processors to the third mobile device that at least one of the first mobile device and the second mobile device has been paired with the new analyte sensor, A step of providing an updated sensor life display for display on the third mobile device based on the updated sensor life data. The method according to claim 14, further comprising:

24. The method according to claim 14, wherein at least a subset of the analyte sensor data associated with the first analyte sensor among the plurality of analyte sensors is transmitted wirelessly from the first analyte sensor among the plurality of analyte sensors to the first mobile device, and at least a subset of the analyte sensor data associated with the second analyte sensor among the plurality of analyte sensors is transmitted wirelessly from the second analyte sensor among the plurality of analyte sensors to the second mobile device.

25. The method according to claim 14, wherein each of the first and second individual user lists includes the name of the user, a time display corresponding to the latest analyte measurement, and a status display corresponding to the latest analyte measurement.

26. A computer program product stored on at least one computer-readable medium for tracking analyte sensor data generated by at least one analyte sensor, wherein the product is executed by one or more processors of a computing system including a first mobile device, a second mobile device, and one or more servers, and the computing system The process involves associating the first mobile device with a first user and associating the second mobile device with a second user. The process of receiving the analyte sensor data in one or more processors, wherein the analyte sensor data includes the analyte measurement value and sensor lifetime data indicating the period during which the at least one analyte sensor continues to operate, The process of receiving input data from a first user in one or more processors that identifies a second user as having access rights to a selective subset of the analyte sensor data, wherein the selective subset of the analyte sensor data includes the sensor lifetime data, The process of providing the second mobile device with the selected subset of the analyte sensor data based on the input data using one or more processors, A step of providing a sensor life display based on the sensor life data for display on a second mobile device, based on the selective subset of the analyte sensor data, wherein the sensor life display includes a sensor life digit indicating the period of time the at least one analyte sensor continues to operate, and the sensor life display is color-coded to indicate the unit of time represented by the sensor life digit. A computer program product that includes computer-readable instructions that perform a certain action.

27. The computer program product according to claim 26, wherein when the computer-readable instruction is executed by at least one processor of the computing system, the computing system further causes the computing system to switch the display mode of the sensor life indicator between a first mode and a second mode based on input received in the second mobile device.

28. The computer program product according to claim 27, wherein the sensor life display in the first mode comprises the sensor life digit and a plurality of ticker marks surrounding the sensor life digit.

29. The computer program product according to claim 28, wherein the plurality of ticker marks include a set of solid ticker marks and a set of fading ticker marks, and the number of the set of solid ticker marks corresponds to the sensor life digit.

30. When the aforementioned at least one analyte sensor continues to operate for a period of one hour or less, The aforementioned sensor life digit represents minutes. When the computer-readable instruction is executed by the at least one processor of the computing system, it further causes the computing system to replace the plurality of ticker marks surrounding the sensor life digit with a visual representation including a solid line that indicates the at least one analyte sensor will continue to operate for one hour or less. The computer program product according to claim 29.

31. The computer program product according to claim 30, wherein the visual representation further includes a shaded area within the solid line, and the shaded area corresponds to the amount of time elapsed during the period of one hour or less in which the at least one analyte sensor continues to operate.

32. The computer program product according to claim 27, wherein the sensor life display in the second mode includes a sensor life digit and text identifying the date and time when the at least one analyte sensor expires.

33. The computer program product according to claim 26, wherein the units of time represented by the sensor life digit of the sensor life indicator include days, hours, and minutes, and each unit of time corresponds to a different color.

34. The computer program product according to claim 26, wherein the one or more processors include one or more servers that communicate with the first mobile device and the second mobile device.

35. When the computer-readable instruction is executed by at least one processor of the computing system, the computing system will... The process involves pairing the first mobile device with a new analyte sensor, In response to the pairing, the first mobile device automatically transmits updated sensor lifetime data to one or more processors. The process involves sending a notification to the second mobile device that the first mobile device has been paired with the new analyte sensor, A step of providing an updated sensor life display for display on the second mobile device based on the updated sensor life data. The computer program product according to claim 26, further comprising the following steps.

36. When the computer-readable instruction is executed by at least one processor of the computing system, the computing system will... The process of presenting the sensor life indicator as an overlay that remains visible when the second user moves between multiple different display devices on the second mobile device. The computer program product according to claim 26, further comprising the following steps.

37. The computer program product according to claim 26, wherein the data from the analyte sensor is transmitted wirelessly from at least one of the analyte sensors.

38. When the computer-readable instruction is executed by at least one processor of the computing system, the computing system will... The process of associating a third mobile device with a third user, A step in which one or more processors receive input data from a third user that identifies the second user as having access rights to the selective subset of the analyte sensor data, wherein the selective subset of the analyte sensor data includes the sensor lifetime data. The computer program product according to claim 26, further comprising the following steps.

Images