WO2025201696A1

WO2025201696A1 - Reduction of notification for communication disconnects when using connected devices for treatment of a medical condition

Info

Publication number: WO2025201696A1
Application number: PCT/EP2025/051946
Authority: WO
Inventors: Felix BOOTZ
Original assignee: Roche Diabetes Care GmbH
Current assignee: Roche Diabetes Care GmbH
Priority date: 2024-03-26
Filing date: 2025-01-27
Publication date: 2025-10-02
Anticipated expiration: 2026-09-26

Abstract

Embodiments are described herein for delaying notifications related to disconnected analyte monitoring devices used to assist in treatment of a medical condition. The user may implement a mobile device and/or one or more analyte monitoring devices for monitoring information related to their medical condition or other health-related information. The mobile device may receive data from an analyte monitoring device when it is connected to the analyte monitoring device. The mobile device may detect a disconnection with the analyte monitoring device and delay a notification to the user related to the disconnection until a predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device. The predicted period of time may be based on the analyte level of the user and/or a rate of change of the analyte level to help prevent the delay from negatively impacting the health of the user.

Description

Reduction of notification for communication disconnects when using connected devices for treatment of a medical condition

The present disclosure refers to methods, a computer-readable storage medium, an apparatus, and a computer program.

Background

People with medical conditions or other health-related conditions often need to monitor events to maintain their health. For example, a person with diabetes often needs to monitor their current glucose level regularly to make sure their glucose level does not go too high or too low. A person with a potassium condition may often need to monitor their current blood potassium levels in a similar manner. These people may perform continuous monitoring to determine whether applied therapeutic interventions are having the intended effect, or if additional interventions are needed to help treat their condition.

Individuals with medical conditions may use a number of devices to help them monitor their current condition and/or events that may occur over the course of a day. Individuals often use their mobile devices to monitor their current condition. In one example, a person with diabetes may use their mobile device (e.g., in combination with other sensor devices) to monitor their current blood glucose levels, insulin dosing information, information related to carbohydrate intake, and/or other information that may be helpful in treatment of the diabetic condition.

In order to view information related to a current condition on a mobile device, the mobile device may receive information from other monitoring devices. For example, the mobile device may receive current blood glucose levels from a blood glucose monitoring device and/or a continuous glucose monitor. These devices may communicate via a communication medium, such as a wireless RF communication signal. Due to interference, the connection between these devices may not always be maintained. The mobile device may provide alerts to the user when the mobile device is unable to receive health-related information from other monitoring devices, such that the user is aware that their condition may be worsening, and the mobile device is unable to report the current status of their condition. These types of notifications may be provided several times as the mobile device disconnects and reconnects to other monitoring devices. The notifications may cause the user to be concerned about the current state of their medical condition unnecessarily, as the current state of the medical condition may be relatively normal. The frequency of the notifications can also cause user fatigue, which may cause the user to ignore important notifications helpful to the treatment of their medical condition.

US 2022/0248988 describes improved digital interfaces, graphical user interfaces, and alarms for analyte monitoring systems. The document discloses methods, systems and interfaces for signal loss condition determination, Time-in-Ranges interfaces, GMI metrics, urgent low glucose alarms, alarm suppression features, alarm setup interfaces, and alarm unavailability detection features. It also describes interfaces for alarm logging and compatibility checking of an analyte monitoring software application. Additionally, it covers interface enhancements like an enhanced visibility mode, a voice accessibility mode, and interfaces relating to user privacy and caregiver alarms.

US 20180172664 describes systems, devices and methods for enhanced performance, power efficiency, interoperability, data security and user privacy in wireless communications for in vivo analyte monitoring systems. The document discloses the use of a Bluetooth or Bluetooth Low Energy enabled handheld relay device for wirelessly relaying analyte data between a sensor unit device and one or more reader devices. The document also covers advertisement and encryption schemes for wirelessly transmitting data in a manner that allows for improved security, efficiency and privacy.

Summary

Methods, a computer-readable storage medium, an apparatus, and a computer program according to the independent claims are provided. Further embodiments are disclosed in dependent claims.

According to an aspect, a method is provided, comprising:

- receiving, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a plurality of measurements of an analyte level of a user and a rate of change of the analyte level;

- detecting a disconnection with the analyte monitoring device via the communication medium; - detecting that the analyte level of the user is within a threshold range at a time of the disconnection;

- in response to the detection of the disconnection with the analyte monitoring device and after the determination that the analyte level of the user is within the threshold range, determining, based on the measurement of the analyte level and the rate of change of the analyte level, a predicted period of time at which a threshold related to the analyte level will be reached;

- delaying a notification to the user related to the disconnection until the predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device; and

- after the predicted period of time has elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, providing the notification to the user indicating the disconnection with the analyte monitoring device.

According to another aspect, at least one computer-readable storage medium is provided, having instructions stored thereon that are configured, when executed by at least one processor, to cause the at least one processor to:

- receive, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a measurement of a blood- analyte level of the user and a rate of change of the analyte level;

- detect a disconnection with the analyte monitoring device via the communication medium;

- detect that the analyte level of the user is within a threshold range at a time of the disconnection;

- in response to the detection of the disconnection with the analyte monitoring device and after the determination that the analyte level of the user is within the threshold range, determine, based on the measurement of the analyte level and the rate of change of the analyte level, a predicted period of time at which a threshold related to the analyte level will be reached;

- in response to the predicted period of time having elapsed without a detection of the reconnection to the analyte monitoring device via the communication medium, provide a notification to the user indicating the disconnection with the analyte monitoring device; and

- in response to the detection of the reconnection to the analyte monitoring device prior to the predicted period of time having elapsed, cancel the notification to prevent the notification from being provided to the user.

According to another aspect, another method is provided, comprising: - receiving, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a plurality of measurements of an analyte level of a user and a rate of change of the analyte level;

- detecting a disconnection with the analyte monitoring device via the communication medium;

- detecting that the analyte level of the user is within a threshold range at a time of the disconnection;

- delaying a notification to the user related to the disconnection;

- detecting a reconnection to the analyte monitoring device via the communication medium prior to an expiration of the predicted period of time; and

- in response to the reconnection being detected prior to the expiration of the predicted period of time, cancel the notification to prevent the notification from being provided to the user.

Further, an apparatus comprising a processor configured to perform the (another) method is provided.

Moreover, a computer program (product) is provided, comprising instructions which, when the program is executed by a computer, cause the computer to carry out the (another) method.

The measurement of the analyte level may be a first measurement. The rate of change may be a first rate of change of the analyte level. The disconnection may be a first disconnection. The predicted period of time may be a first predicted period of time. The notification may be a first notification.

The method may comprise at least one of:

- detecting a reconnection with the analyte monitoring device;

- receiving, via the communication medium, a second measurement of the analyte level of the user and a second rate of change of the analyte level;

- detecting a second disconnection with the analyte monitoring device via the communication medium; - in response to the detection of the second disconnection with the analyte monitoring device, determining, based on the second measurement of the analyte level and the second rate of change of the analyte level, a second predicted period of time at which the threshold related to the analyte level will be reached;

- determining that the second predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device; and

- delaying a second notification related to the second disconnection from being provided to the user until the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device; and

- after the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, providing the second notification to the user indicating the disconnection with the analyte monitoring device.

The disconnection may be between a mobile device and the analyte monitoring device.

The threshold may comprise a high-end threshold and/or a low-end threshold related to the analyte level of the user.

The threshold may be a user defined threshold and/or a predefined threshold related to an extreme diabetic state. The high-end threshold related to the extreme diabetic state may comprise a state of hyperglycemia. Additionally or alternatively, the low-end threshold related to the extreme diabetic state may comprise a state of hypoglycemia.

The method may comprise at least one of:

- receiving a user indication to set the threshold to one of the user defined threshold or the predefined threshold related to the extreme diabetic state; and

- determining, based on the user indication, the predicted period of time based on one of the user defined threshold or the predefined threshold related to the extreme diabetic state.

The rate of change of the analyte level may be a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold. The notification may comprise at least one of a visual notification, an audible notification, a tactile notification, and a vibratory notification.

The notification may comprises the visual notification and the visual notification may be provided via a display and/or a light emitting diode (LED).

The analyte monitoring device may be a continuous glucose monitor.

The method may be performed by an application executing on a mobile device.

The instructions may be configured to cause the at least one processor to perform at least one of the following:

- determine that the predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device; and

- in response to detection of the predefined maximum period of time having elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, provide the notification to the user indicating the disconnection with the analyte monitoring device.

The threshold may comprises a high-end threshold and/or a low-end threshold related to the analyte level of the user.

The threshold may be a user defined threshold and/or a predefined threshold related to an extreme diabetic state, wherein preferably the high-end threshold related to the extreme diabetic state may comprise a state of hyperglycemia, and wherein more preferably the low-end threshold related to the extreme diabetic state may comprise a state of hypoglycemia.

- receive a user indication to set the threshold to one of the user defined threshold or the predefined threshold related to the extreme diabetic state; and

- determine, based on the user indication, the predicted period of time based on one of the user defined threshold or the predefined threshold related to the extreme diabetic state. The rate of change of the analyte level may be a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold.

The notification may comprise at least one of a visual notification, an audible notification, a tactile notification, and a vibratory notification. The notification may comprise the visual notification and the instructions may be configured to cause the at least one processor to provide the visual notification via a display and/or a light emitting diode (LED). The analyte monitoring device may be a continuous glucose monitor.

Embodiments are described herein for delaying notifications related to disconnected analyte monitoring devices used to assist in treatment of a medical condition. The user may implement one or more computing devices for enabling them to properly treat their medical condition. For example, the user may implement their mobile device and/or one or more analyte monitoring devices for monitoring information related to their medical condition or other health-related information. The analyte monitoring device may be a glucose monitoring device, such as a continuous glucose monitor, for example. The embodiments described herein may be implemented on one or more computing devices, such as a mobile device of a user. The embodiments may be implemented via computer-executable instructions stored on a computer- readable media. In one example, the embodiments described herein may be implemented as methods and/or computer-executable instructions that may be executed by one or more processors via one or more applications executing on one or more computing devices.

The user’s mobile device may receive data from an analyte monitoring device when it is connected to the analyte monitoring device via a communication medium. The data may be related to the medical condition of the user. For example, the data may relate to an analyte level of the user. The analyte level may comprise a blood glucose level, a blood potassium level, or another analyte level monitored by the user. The data from the analyte monitoring device may comprise a rate of change of the analyte level.

The mobile device may detect a disconnection with the analyte monitoring device via the communication medium. The mobile device may detect that the analyte level of the user is within a threshold range at a time of the disconnection. The mobile device may delay a notification to the user related to the disconnection until a predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device. In response to the detection of the disconnection with the analyte monitoring device and after the determination that the analyte level of the user is within the threshold range, the mobile device may determine the predicted period of time at which a threshold related to the analyte level will be reached. The predicted period of time may be determined based on the measurement of the analyte level and/or the rate of change of the analyte level. The mobile device may delay the notification to the user related to the disconnection until the predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device. In response to the predicted period of time having elapsed without a detection of the reconnection to the analyte monitoring device via the communication medium, the mobile device may provide a notification to the user indicating the disconnection with the analyte monitoring device.

In another example, the mobile device may delay the notification of the user related to the disconnection and detect a reconnection to the analyte monitoring device via the communication medium prior to an expiration of the predicted period of time. In response to the reconnection being detected prior to the expiration of the predicted period of time, the mobile device may cancel the notification to prevent the notification from being provided to the user.

The notification may comprise a visual notification, an audible notification, or a vibratory or tactile notification. The visual notification may be provided via a display or a light emitting diode (LED). In response to the mobile device detecting a reconnection to the analyte monitoring device prior to the predicted period of time having elapsed, the mobile device may cancel the notification to prevent the notification from being provided to the user.

As the predicted period of time may be based on the analyte level and/or rate of change of the analyte level of a user at a given instance in time, longer predicted periods of time may allow for additional unforeseen factors to affect the analyte level of the user. As such, the notification may be prevented from being delayed for such a long period of time that it may be harmful to the treatment of the medical condition of the user. The mobile device may determine that the predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device. The mobile device may provide the notification to the user indicating the disconnection with the analyte monitoring device if the predefined maximum period of time has elapsed without detecting a reconnection.

In another example, the measurement of the analyte level may include a first measurement. The rate of change may include a first rate of change of the analyte level. The disconnection may be a first disconnection. The predicted period of time may be a first predicted period of time. The notification may be a first notification. The mobile device may detect a reconnection with the analyte monitoring device and receive, via the communication medium, a second measurement of the analyte level of the user and/or a second rate of change of the analyte level. The mobile device may detect a second disconnection with the analyte monitoring device via the communication medium. In response to the detection of the second disconnection with the analyte monitoring device, the mobile device may determine, based on the second measurement of the analyte level and/or the second rate of change of the analyte level, a second predicted period of time at which the threshold related to the analyte level will be reached. The mobile device may determine that the second predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device. The mobile device may delay a second notification related to the second disconnection from being provided to the user until the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device. After the predefined maximum period of time has elapsed without the mobile device detecting the reconnection to the analyte monitoring device via the communication medium, the mobile device may provide the second notification to the user indicating the disconnection with the analyte monitoring device.

As described herein, the mobile device may determine a predicted period of time at which a threshold related to the analyte level will be reached. The threshold may comprise a high-end threshold or a low-end threshold related to the analyte level of the user. For example, the threshold may be a user defined threshold or a predefined threshold related to an extreme diabetic state. The high-end threshold related to the extreme diabetic state may comprise a state of hyperglycemia. The low-end threshold related to the extreme diabetic state may comprise a state of hypoglycemia. The mobile device may receive a user indication to set the threshold to one of the user defined threshold or the predefined threshold related to the extreme diabetic state and determine, based on the user indication, the predicted period of time based on one of the user defined threshold or the predefined threshold related to the extreme diabetic state. The rate of change of the analyte level may include a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold.

The delay of the notifications when the analyte level of the user is within a normal or healthy range may prevent the user from needlessly receiving notifications related to the disconnection, which may be helpful in assisting the treatment of the medical condition of the user, and the predefined maximum period of time may prevent the delay from becoming potentially harmful to the user.

The embodiments described above in connection with the method may be provided correspondingly for the computer-readable storage medium and/or the apparatus and/or the computer program.

Brief description of the

FIGs. 1 A and 1 B show a perspective view of representative user environments.

FIGs. 2A-2C show graphs that illustrate example timeframes in which notifications may be delayed and/or provided to a user after an analyte monitoring device is disconnected from a computing device.

FIG. 3 shows a flowchart of an example process for delaying notifications of a disconnection between an analyte monitoring device and another computing device.

FIGs. 4A-4C depict example GUIs illustrating overlay notifications provided on a display of a computing device.

FIG. 5 is a block diagram of an example computing device.

FIG. 6 is a block diagram of an example continuous monitoring device.

FIG. 7 is a block diagram of an example blood glucose meter (BGM) device.

Detailed

FIG. 1A is a perspective view of a representative user environment. As shown in FIG. 1 A, a user 100 may be a person with a medical condition. For example, the user 100 may be a person with diabetes, a person with a potassium disorder, or a person with another medical condition. The user 100 may use one or more devices to help monitor and/or treat the medical condition. For example, the user 100 may use one or more devices to help monitor an analyte level and/or treat the medical condition.

In one example, the medical condition may include a diabetic condition. The diabetic condition may include a metabolic syndrome, pre-diabetes, type 1 diabetes, type 2 diabetes, and/or gestational diabetes. The user 100 may be in an extreme diabetic state, such as hypoglycemia or hyperglycemia, when the blood glucose level of the user 100 is above or below a threshold blood glucose level. The user 100 may use a glucose monitoring device to monitor blood glucose levels.

A glucose monitoring device may include any device that detects and reports a level of glucose in the blood of the user, either through direct measurement of the blood or through an indirect detection process. A blood glucose level is also referred to as a blood sugar level. Examples of glucose monitoring devices include, but are not strictly limited to, continuous glucose monitoring devices, flash glucose monitoring devices, and blood glucose meters that provide a single measurement of blood glucose levels from a blood sample in a “spot” monitoring process. A blood glucose treatment device may include any device that treats a diabetic condition of the user, either through direct treatment into the blood or through an indirect treatment process or by providing information to allow for treatment.

In some embodiments, the blood glucose monitoring device and/or blood glucose treatment device is a pen device 103. The pen device 103 may include any injector pen capable of monitoring and/or managing insulin delivery. Example pen devices may communicate with an external device, such as the mobile device 104 and/or a remote computing device 122, to determine insulin levels, calculate doses, track doses, deliver insulin, and/or provide other information such as notifications or alerts. In some examples, pen devices may periodically communicate data indicating the blood glucose levels of the user 100 to an external device, such as a mobile device 104, for computing or storing the blood glucose levels of the user 100.

In some embodiments, the glucose monitoring device is a continuous glucose monitor (CGM) 102. The CGM 102 includes a subcutaneous sensor that is used to sense and monitor the amount of glucose in interstitial fluid of the user 100. The CGM 102 includes a transmitting device that is located directly over the sensor that wirelessly powers the data transfer from the sensor. The CGM 102 periodically communicates data indicating the blood glucose levels of the user 100 to an external device, such as a mobile device 104, for computing or storing the blood glucose levels of the user 100.

Some embodiments of the mobile device 104 operate as a CGM controller device. Though the mobile device 104 is provided as an example of a device with which the CGM 102 communicates, the CGM 102 may communicate with other dedicated CGM controller devices for providing similar functionality that is described herein for the mobile device 104. In some cases, the CGM 102 processes the blood glucose data to provide an amount of glucose in interstitial fluid of the user 100. In some cases, the CGM 102 provides the blood glucose data to the mobile device 104 and/or pen device 103, and the mobile device 104 and/or pen device 103 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.

In some embodiments, the blood glucose monitoring device is a flash glucose monitor (FGM) 111. The FGM 111 includes a subcutaneous sensor that is used to sense and monitor the amount of glucose in interstitial fluid of the user 100. A separate reader device, such as the mobile device 104, pen device 103, or another reader device, receives the blood glucose data from the sensor of the FGM 111 when the device is within range, such as but not limited to the RF range, of the sensor. The FGM 111 transmits an instantaneous blood glucose level or a graphical trend of the blood glucose level to the reader device for display. The mobile device 104 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.

In some embodiments, the user 100 uses a blood glucose meter (BGM) 106 as a blood glucose monitoring device to monitor blood glucose levels. The BGM 106 includes a port 108 that receives a blood glucose measurement strip 110. The user 100 deposits a sample of blood on the blood glucose measurement strip 110. The BGM 106 analyzes the sample and measure the blood glucose level in the sample. The blood glucose level measured from the sample is displayed on a display 112 of the BGM 106 or communicated to an external device, such as the mobile device 104. The mobile device 104 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein. The blood glucose level measured by the pen device 103 or BGM 106 or computed using data received from the CGM 102 or FGM 111 , is used to treat the diabetic condition of the user 100. The mobile device 104 communicates with the CGM 102, FGM 111 , the BGM 106, and/or pen device 103 using wired or wireless communications that are transmitted and received between devices on a wired or wireless communication medium. The mobile device 104 may also, or alternatively, receive data from a monitoring device (e.g., the CGM 102, FGM 111 , the BGM 106, and/or pen device 103) indirectly via one or more other devices (e.g., a remote computing device 122 or another computing device). For example, a monitoring device may be capable of communicating data to one or more intermediate computing device for storing data thereon for being transmitted to and/or requested by the mobile device 104. The mobile device 104, the CGM 102, a CGM controller, the BGM 106, the FGM 111 , or pen device 103 may be collectively referred to as user devices or computing devices. The mobile device 104 communicates with the CGM 102, the FGM 111 , the BGM 106, and/or pen device 103 using the same or different wired or wireless protocols. For example, the mobile device 104 communicates with the CGM 102, FGM 111 , the BGM 106, and/or pen device 103 using BLUETOOTH®, near field communication (NFC), THREAD®, WIFI®, ZIGBEE®, WI-MAX®, a cellular communication protocol, a proprietary wireless communication protocol, or another radio frequency (RF) communication protocol.

Though various blood glucose monitoring devices (e.g., pen device 103, CGM 102, BGM 106, FGM 111 , and/or another blood glucose monitoring device) are provided as examples of analyte monitoring devices, other analyte monitoring devices may be implemented for measuring and/or monitoring other analyte levels of the user 100. For example, the user 100 may have a potassium condition or disorder, such as hypokalemia (e.g., a potassium deficiency in which a person has blood potassium levels below a predefined threshold) or hyperkalemia (e.g., a condition in which a person has blood potassium levels above a predefined threshold.) The user 100 may use a blood potassium monitoring device to monitor blood potassium levels. The user 100 may deposit a sample of blood in the blood potassium monitoring device, which analyzes the sample and measure the blood potassium level in the sample. The blood potassium level measured from the sample may be communicated to an external device, such as the mobile device 104. The mobile device 104 may process the blood potassium data to manage the condition and provide treatment notifications as described herein. For example, the notifications may alert the user 100 to ingest potassium or diuretics, take medication, perform dialysis, and/or conduct another form of treatment. In another example, a user 100 may have a liver condition or disorder and the user 100 may use a blood ketone meter or other monitoring device to monitor blood ketone levels. The blood ketone level measured from the sample may be communicated to an external device, such as the mobile device 104. The mobile device 104 may process the blood ketone data to manage the condition and provide treatment notifications as described herein. Any other devices that are used to monitor any other medical conditions based on analyte levels of the user 100 and/or communications between connected devices may similarly utilize one or more embodiments described herein.

The mobile device 104 may establish a connection to one or more analyte monitoring devices (e.g., pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device) at a time. For example, the mobile device may establish a connection via a wired or wireless communication medium with one or more blood glucose monitoring devices. The connection may be established via a wired or a wireless communication protocol, such as BLUETOOTH®, NFC, THREAD®, WIFI®, ZIGBEE®, WIMAX®, or another RF communication protocol. The mobile device 104 may transmit and/or receive data via the one or more established connections for assisting in monitoring and/or treating the diabetic condition. The connection between devices may be initiated by the transmission and/or receipt of a connection request message from one of the devices via a communication medium. Another device may transmit a connection response message in response to the connection request message via the communication medium. The devices may detect that the connection has been established based on the exchange of the connection request/connection response messages and/or subsequent messages, such as acknowledgement messages, messages for establishing secure communications, or other subsequent messages (e.g., depending on the communication protocol).

The mobile device 104 may receive data from other devices and/or input from the user 100 via a user interface for being provided on a display. The mobile device 104 may receive input via hard buttons or soft buttons provided on the display. In response to the data that is received at the mobile device 104, the mobile device may provide output to the user 100 in the form of visual output on the display, audio output via a speaker, haptic feedback via vibrations, and/or other output to the user. The mobile device 104 may be a connected smart device and/or may be in communication with other connected smart devices. Example connected smart devices may include a wearable device. The connected smart device may be an armband (e.g., a smart watch, such as an APPLE® watch, a FITBIT® armband, or other device capable of being worn on the arm of the user 100), a ring, glasses (e.g., GOOGLE® GLASS™), a headset (e.g., BLUETOOTH® headset), clothing (e.g., shirts, gloves, etc.), or another wearable device capable of being worn by the user 100. The connected smart device may be a wearable device or other device capable of monitoring the heart rate of the user 100, such as a heart rate monitor. The connected smart device may include a device capable of monitoring a wake/sleep state of the user, such as a wearable device, a heart rate monitor, a smart bed, or another device.

The mobile device 104 may be configured to determine information corresponding to the device’s location (/.e., location information). For example, the mobile device 104 may be able to determine the geolocation (e.g., latitude and longitude) of the mobile device 104 using signals from a global positioning system (GPS) or triangulation via cellular communications. The mobile device 104 may communicate with the remote computing device 122 for accessing a third-party service (e.g., via an application programming interface (API)), for example, to determine the location of the mobile device 104 or access other software/applications. In one example, the mobile device 104 may provide data received from one or more devices to the remote computing device 122, via the network 120, for performing one or more processes described herein. The mobile device 104 may receive a response from the remote computing device 122 with information for being displayed to the user and/or for being communicated to other devices.

Some embodiments of the mobile device 104 include one or more sensors for detecting a relative position of the device or information about the user 100. The mobile device 104 may detect a movement or a change in orientation. Based on the movement or change in orientation (or lack thereof) of the mobile device 104 over a period of time, the mobile device 104 may detect that the user 100 is standing, sitting, or lying down. In other words, the mobile device 104 detects/infers that the user 100 is awake. The mobile device 104 may detect that the user 100 is exercising when the movement or a change in orientation is greater than a threshold for a period of time. The mobile device 104 may detect the heartrate of the user 100 using a heartrate sensor. Based on the heartrate and/or the movement of the user 100 over a period of time, the mobile device 104 may detect whether the user 100 is asleep or awake. The information about the mobile device 104 or the user 100 is used to provide information about or treat the diabetic condition.

The mobile device 104 may provide information to the user 100 about the user’s medical condition. For example, the mobile device 104 may provide blood glucose levels, blood potassium levels, meal-related information, exercise-related information, treatment notifications, and/or graphs and other graphical user interfaces, such as alerts or notifications, for display. The mobile device 104 may provide therapeutic protocol data to the pen device 103. For example, the mobile device 104 may provide insulin dose levels for an associated medication titration event (e.g., basal insulin titration event) to the pen device 103. Having received the insulin dose level, the pen device 103 may be configured to administer a corresponding amount of insulin.

The mobile device 104 may communicate with other devices directly via a wired communication and/or a short-range wireless communication (e.g., WI-FI®, BLUETOOTH®, BLE, NFC, or another suitable short-range wireless communication). The mobile device 104 may communicate indirectly with remote computing device(s) 122 via a network 120 (e.g., using a WI-FI® network, a cellular network, a WI-MAX® network, or another wired or wireless network). The network 120 is a wired or wireless network. The network 120 is used to communicate over the Internet to other devices.

The mobile device 104 may communicate with the remote computing device(s) 122 to generate user interfaces for display on the mobile device 104, perform remote computation, or to otherwise control a remote computing device. For example, the mobile device 104 may provide a user interface via an application (e.g. , a web browser or other local application) that is generated locally for providing access to locally stored data or data from a remote computing device 122.

As described herein, the mobile device 104 may display information to the user 100 to assist in treatment of the user’s medical condition. For example, as described herein, the mobile device 104 may provide information to the user 100 related to the user’s health, devices assisting in treatment of the medical condition (e.g., a bolus or insulin level for treating a diabetic condition, an amount of potassium for treating a blood potassium condition, or another form of treatment), a current state of the user’s medical condition (e.g., including measured and/or monitored analyte levels, such as blood glucose levels, blood potassium levels, and/or other analyte levels), and/or other information related to the user, the user’s medical condition, and/or one or more devices to enable proper treatment of the user’s medical condition. The mobile device 104 may provide data related to the user’s medical condition, such as blood glucose levels; blood potassium levels; meal-related information; exercise-related information; dosing information (e.g., dosing levels or reminders for glucose or other forms of treatment); information related to the state of one or more devices in the system (e.g., battery state, on/off state, error state, connected state, and/or other states related to analyte monitoring devices and/or one or more other devices); graphs and other graphical user interfaces for display, and/or notifications (e.g., or alerts) that may be provided to the user 100. The mobile device 104 may provide data received from one or more other devices, such as analyte monitoring devices or treatment devices, and/or data generated locally thereon from one or more software applications.

The mobile device 104 may communicate with one or more analyte monitoring devices, such as the pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device. The mobile device 104 may receive data from an analyte monitoring device in order to allow the user 100 to treat the medical condition. For example, the mobile device may receive analyte levels (e.g. , blood glucose levels, blood potassium levels, and/or other analyte levels) from one or more analyte monitoring devices for being displayed to the user. The data from the analyte monitors may also indicate a rate of change of the analyte levels. The analyte monitoring devices may each provide the analyte levels and/or the rate of change to the mobile device 104 in response to measurements are performed locally thereon and while the analyte monitoring device is connected to the mobile device 104. The analyte monitoring devices may provide data to the mobile device 104 at predefined times of day and/or throughout periods of time (e.g., the day and/or night). The analyte monitoring devices may provide data to the mobile device 104 in response to the analyte levels reaching a predefined threshold or coming within a predefined level of a predefined threshold.

The mobile device 104 may provide notifications to the user 100 in response to the data that is collected from the analyte monitoring devices and/or in response to an indication to notify the user 100 based on the data related to the medical condition. The mobile device 104 may provide notifications via one or more notification types. For example, the notifications may be provided via a visual notification on a graphical user interface displayed on the mobile device 104, a visual notification provided via a light emitting diode (LED), an audible notification provided via a speaker or other audio device on the mobile device 104, a tactile or vibratory notification on the mobile device 104, and/or another notification type provided via the mobile device 104 or another device in the user environment. The notifications may be provided to the user 100 via an application (e.g., a medical application, such as a diabetes-related application, an exercise- related application, a nutrition or mealtime-related application, another health-related application, or another type of application) residing locally thereon and/or via one or more remote computing devices 122. For example, one or more remote computing devices 122 may be implemented to execute the application for providing a graphical user interface with the notifications for providing the information related to the medical condition of the user 100 and/or treatment thereof.

The mobile device 104 may provide a notification (e.g., or alert) the user 100 in response to different triggering events. For example, the mobile device 104 may provide a notification to the user 100 if the user’s analyte level is greater than or less than a threshold. For example, the CGM 102 may provide regular or continuous data indicating the glucose levels of the user 100, while the CGM 102 is connected to the mobile device 104, and the mobile device 104 may notify the user 100 when the analyte levels are outside of a normal or healthy range (e.g., at or above a predefined high-end threshold and/or below a predefined low-end threshold). The mobile device 104 may also receive data related to the medical condition of the user 100 from the remote computing device 122 and notify the user 100 in response to such data.

As the mobile device 104 may become unable to properly receive and/or monitor data from other devices (e.g., analyte monitoring devices, remote computing device 122, and/or another device) if it becomes disconnected from those devices, the mobile device 104 may also provide a notification to the user 100 when the mobile device becomes disconnected from another device, such that the user 100 may understand that their analyte levels or other information related to their medical condition may be changing. As shown in FIG. 1 B, the mobile device 104 may become disconnected from analyte measurement devices, such as the pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device. The disconnections between the mobile device 104 and the analyte measurement device may be the result of the analyte measurement device losing power, a range or distance between the mobile device 104 and the analyte measurement device, a congested RF environment, and/or other RF interference (e.g., walls or other physical structures). A congested RF environment may include multiple devices communicating on a same RF band. For example, if the mobile device 104 and the analyte measuring device are communicating on a BLUETOOTH communication link, the greater the number of other BLUETOOTH devices communicating within the same space may cause a greater amount of interference with the communications between the analyte monitoring device and the mobile device 104. A relatively strong source of interference on an overlapping RF band can also cause interference with the communications between the mobile device 104 and the analyte measurement device. For example, if the mobile device 104 and the analyte measuring device are communicating on a BLUETOOTH communication link, a WIFI hotspot (e.g., a router device) may cause a relatively large amount of interference with the communications between the analyte monitoring device and the mobile device 104. When the interference level of communications between the analyte monitoring device and the mobile device 104 is above a certain threshold, the analyte monitoring device and the mobile device 104 may be unable to successfully communicate, resulting in the disconnection. Similar causes of interference may result in the mobile device 104 becoming disconnected from other devices, such as the remote computing device 122.

In response to devices, such as the analyte monitoring device and the mobile device 104, becoming disconnected, the mobile device 104 may provide a notification (e.g., or alert) to the user 100. For example, the mobile device 104 may execute an application (e.g., a health-related application or another application related to the medical condition of the user, such as a diabetes- related application) thereon that is configured to detect that the mobile device 104 and the analyte monitoring device are disconnected and provide the notification to the user. The disconnection may be detected by the application executing on the mobile device based on a failure to receive one or more messages (e.g., in response to a request or an anticipated message) within a period of time. The mobile device 104 may identify the device from which it has become disconnected to alert the user 100 that data related to the user’s medical condition is not currently being monitored at the mobile device. The mobile device 104 may provide such notifications to the user 100 via the one or more notification types (e.g., a visual notification, an audible notification, a tactile or vibratory notification, and/or another notification type). As the interference level between the devices on the RF communication link and/or the range or distance between the devices changes, the mobile device 104 may continue to disconnect and reconnect to the device causing multiple notifications to be provided to the user 100 within the period of disconnections and reconnections. The notification may be provided to one or more other devices via a message on another wireless communication. For example, the mobile device 104 may provide a notification of the disconnection to another mobile device (e.g., via the remote computing device 122). A first mobile device (e.g., a parent’s mobile device, or another family member’s mobile device) may have access to the status of the analyte monitoring device’s connection status with a second mobile device (e.g., a child’s mobile device, or another family member’s mobile device) via the remote computing device 122, which may indicate the disconnection between the analyte monitoring device and the second mobile device. When the mobile device 104 becomes disconnected from one or more devices, the devices may add to or increase the amount of RF communications on the RF communication link in attempting to re-establish the connection. The attempts to re-establish connection on the RF communication link may cause battery drain on the mobile device 104 and/or the other devices with which the mobile device is attempting to connect (e.g., the analyte monitoring device), which may be power-restricted devices.

The notification of the disconnection may be provided to inform the user 100 that the user’s analyte level may be approaching a threshold, or even be greater than or less than a threshold, but the mobile device 104 is unable to make such a determination due to the mobile device 104 being disconnected from the analyte monitoring device. However, the notifications may be provided to the user 100 even though the user’s analyte level may be at or within a normal or healthy level. Thus, the notifications may be provided regardless of whether the user’s analyte level is within a target range or at or near a threshold. These notifications that are caused by the disconnections between the analyte monitoring device and the mobile device 104 may be distracting to the user 100. The notifications that are caused by the disconnections between the analyte monitoring device and the mobile device 104 may result in user fatigue to the notifications, which may cause the user 100 not to pay attention to the notifications provided to actually help treat the user’s medical condition (e.g., such as notifications for the analyte level reaching a certain unhealthy threshold, notifications to take medication, and/or other notifications for treatment of the medical condition). The notifications that are caused by the disconnections between the analyte monitoring device and the mobile device 104 may result in an increased stress level to the user 100, which may negatively affect the user’s medical condition (e.g., due to increased heart rate or other results of stress). If the notifications are provided at night or at other time periods when the user 100 is attempting to sleep, the notifications may prevent the user 100 from being able to sleep and also, or alternatively, negatively affect the user’s medical condition. The notifications related to disconnected devices may be adjusted to reduce the impact on the user 100, the mobile device 104, the analyte monitoring device, and/or the network/RF communication links on which the on which the mobile device 104 is communicating. For example, the mobile device 104 may delay the notification related to disconnections for a period of time after the disconnection, while also avoiding a negative impact to the health or medical condition of the user 100. The mobile device may delay the notification related to disconnections when the user’s analyte level is at or within a normal or healthy level (/.e., within a target range). The notification may be delayed for a period of time that is at or less than a predicted period of time at which the user’s analyte level may be predicted to reach a predefined threshold (e.g., a high-end threshold or low-end threshold) related to the medical condition of the user 100. The delay may allow some time for reconnection between the devices without providing a notification to the user 100. The predicted period of time may be determined based on the analyte level of the user 100 at, or before, a disconnection between the devices and/or a rate of change of the analyte level of the user 100, such that the notification is tailored to the analyte level of the user and/or the thresholds related to the user’s medical condition.

The mobile device 104 may operate one or more local application that may be implemented to determine the predicted periods of time at which notifications may be provided after a disconnection. In one example, the mobile device 104 may operate multiple applications capable of sharing data or information for enabling notifications to be provided to the user after a disconnection. A health-related application or another application related to a particular analyte monitoring device may receive data from the analyte monitoring device that is related to the medical condition of the user (e.g., analyte levels and/or rate of change of analyte levels) and provide the data to a separate application operating locally on the mobile device 104 for determining predicted periods of time at which notifications may be provided after a disconnection. The user may be able to access data and/or notifications from each of the applications independently, when the mobile device 104 is operating multiple applications. In another example, the mobile device 104 may send data related to the medical condition of the user (e.g., analyte levels and/or rate of change of analyte levels) at the time of the disconnection to another device, such as the remote computing device 122, for determining the predicted periods of time at which notifications may be provided. FIG. 2A includes a graph 200 that illustrates an example timeframe in which periods of time may be determined for providing notifications to a user after an analyte monitoring device is disconnected from a computing device. The computing device may be a mobile device operating a local application for monitoring information related to a medical condition of the user based on data received from the analyte monitoring device. However, similar timeframes may be implemented and/or determined for providing notifications to the user in response to disconnections between other devices, such as a mobile device and a remote computing device providing data related to the medical condition of the user; a mobile device and a remote display device (e.g., wearable headset or glasses); and/or other types of devices that may be communicating to allow the user to treat their medical condition.

As shown in FIG. 2A, the analyte monitoring device may perform measurements of an analyte level 202 and provide the measurements of the analyte level 202 to the computing device over a period of time that the computing device is connected to the analyte monitoring device. The measurements of the analyte level 202 may be included with other data from the analyte monitoring device. For example, the measurements of the analyte level 202 may be provided with an indication of a rate of change of the analyte level. In another example, the rate of change may be determined from the changes in the analyte level 202 that are performed over time.

The analyte monitoring device may become disconnected from the computing device at a time to. In response to the disconnection, the computing device may determine that the analyte level 202 includes a value 202a that is at or within a normal or healthy level. The normal or healthy level may be above and/or below one or more thresholds. For example, the computing device may determine that the analyte level 202a is within a threshold range 210. The threshold range 210 may include analyte values that are above and/or below one or more predefined and/or user defined thresholds. The threshold range 210 may include analyte values above a high-end first threshold 206a and/or below a low-end second threshold 206b. The thresholds 206a, 206b may be set to a defined value relative to a threshold related to an extreme medical condition or state to alert the user when the analyte level is approaching the extreme medical condition or state. The thresholds 206a, 206b may indicate that the analyte level of the user is trending toward the extreme medical condition or state and/or operate as a triggering event for warning the user that the analyte level is approaching or trending toward the extreme medical condition or state. The thresholds 206a, 206b may be user-defined thresholds or predefined thresholds at the time of initial configuration of the application or device on which the thresholds 206a, 206b are stored. For example, the thresholds 206a, 206b may be predefined at the time of programming of the initial application and/or at configuration of the device during manufacture. The thresholds 206a, 206b may be user-defined by the person having the medical condition, a health care provider having access to the data related to the medical condition of the user, or another user with access to data related to the medical condition of the user for defining the thresholds 206a, 206b. The user-defined thresholds may be defined in response to a user indication received at the computing device to set the user-defined threshold.

The threshold range 210 may also, or alternatively, include analyte values above a predefined threshold 208b and/or below predefined threshold 208a. The predefined thresholds 208a, 208b may each represent thresholds related to extreme medical conditions or states. For example, the predefined threshold 208a may represent a high-end threshold of an extreme diabetic state, such as hyperglycemia, when the blood glucose level of the user is at or above the predefined threshold 208a. In another example, the predefined threshold 208a may represent a high-end threshold of an extreme potassium state, such as hyperkalemia, when the blood potassium level of the user is at or above the predefined threshold 208a. The predefined threshold 208b may represent a low-end threshold of an extreme diabetic state, such as hypoglycemia, when the blood glucose level of the user is at or below the predefined threshold 208b. In another example, the predefined threshold 208b may represent a low-end threshold of an extreme potassium state, such as hypokalemia, when the blood potassium level of the user is at or above the predefined threshold 208b. Though examples are provided, the thresholds 206a, 206b, 208a, 208b may represent thresholds related to other medical conditions. One or more of the thresholds 206a, 206b, 208a, 208b may be user-specific thresholds that are tailored to the user based on the medical condition of the user. The thresholds 206a, 206b may be user-defined in an effort to notify the user when the analyte level 202 is approaching an extreme state, which may be represented by the predefined thresholds 208a, 208b.

The computing device may detect that, at the time to of the disconnection, the analyte level 202a of the user is at or within the threshold range 210, which may represent a normal or healthy level. After the computing device detects the disconnection with the analyte monitoring device at time to, the computing device may determine a predicted period of time t_predicted at which one or more of the thresholds 206a, 206b, 208a, 208b related to the analyte level will be reached. For example, the computing device may determine the predicted period of time(s) t_predicted based on the measurement of the analyte level 202a and/or the rate of change of the analyte level 202 at the time to at which the disconnection occurred, or within a defined period of time prior to the occurrence of the disconnection.

The predicted period of time t_predicted may include a time at which the computing device determines that an analyte level 202 may reach or exceed a given threshold. The predicted period of time predicted may be calculated from the analyte value 202a at the time to of disconnection (e.g., or one or more analyte values within a period prior to the disconnection at time to) and/or the rate of change of the analyte value at time to (e.g. , or within a period prior to the disconnection at time to). Equation 1 , below, includes an example algorithm that may be implemented for determining the predicted period of time at which the analyte level 202 may reach or exceed a given threshold. t_predicted ^— (^Th 3d) / r, Equation 1 where At_predicted is a predicted amount of time from the time to of disconnection for the analyte level to reach a threshold; a_Th is a threshold analyte value; a_d is the analyte value at the time to of disconnection; and r is the rate of change of the analyte value at the time to of disconnection. The rate of change r may be positive or negative depending on whether the analyte level 202 is rising or falling at time to. A positive threshold value or negative threshold value may be selected based on the direction of the rate of change.

Equation 1 may be applied to different threshold values to identify a predicted periods of time predicted . For example, Equation 1 may be used to determine the predicted period of time t_predicted_i from the time to of disconnection using the analyte value of threshold 206b (e.g., a_Th), the analyte value 202a (e.g., a_d), and the rate of change r at the time to of disconnection. Equation 1 may be used to determine the predicted period of time t_predicted_2 from the time to of disconnection using the analyte value of threshold 206a (e.g., a_Th), the analyte value 202a (e.g., a_d), and the rate of change r at the time to of disconnection. Equation 1 may be used to determine the predicted period of time t_predicted_3 from the time to of disconnection using the analyte value of threshold 208b (e.g., a_Th), the analyte value 202a (e.g., a_d), and the rate of change r at the time to of disconnection. Equation 1 may be used to determine the predicted period of time t_predicted_4 from the time to of disconnection using the analyte value of threshold 208a (e.g. , a_Th), the analyte value 202a (e.g., a_d), and the rate of change r at the time to of disconnection.

The notification of the disconnection between the analyte monitoring device and the computing device may be delayed until the predicted period of time t_predicted has elapsed. For example, as shown in FIG. 2A, the computing device may delay the notification after the time to of disconnection until one or more of the predicted periods of time t_predicted (e.g. , t_predictedi, t_predicted2, t_Predicted3, or tpredicted^ have elapsed. The computing device may calculate multiple predicted periods of time t_predicted and provide multiple notifications to the user as each predicted period of time elapses. For example, the computing device may calculate predicted periods of time t_predicted for multiple thresholds in the same direction of the rate of change (e.g., thresholds 206a, 208a or thresholds 206b, 208b). As each predicted period of time t_predicted elapses, a notification may be provided indicating that the predicted period of time tpredicted has elapsed or that a user’s analyte level is approaching a corresponding predefined threshold.

FIG. 2B includes a graph 200a that illustrates another example timeframe in which periods of time may be determined for providing notifications to a user relative to a maximum period of time. As shown in FIG. 2B, the computing device may delay the notification of the disconnection between the analyte monitoring device and the computing device until the predicted period of time t_predicted has elapsed or until a predefined maximum period of time t_max has elapsed since the time to of disconnection. For example, the computing device may determine that the predicted period of time t_Predicted4 is a greater period of time than the predefined maximum period of time tmax from the time t₀ of disconnection. As such, the computing device may delay the notification of the disconnection between the analyte monitoring device until the predefined maximum period of time tmax has elapsed since the time to of disconnection. If there are one or more other predicted periods of time t_predicted (e.g. , t_predicted2) that have been calculated for providing notifications to the user based on other thresholds (e.g. , thresholds 206a) that are less than the predefined maximum period of time tmax, the computing device may provide a corresponding notification after the predicted periods of time t_predicted (e.g., t_predicted2) has elapsed from the time to of disconnection. The computing device may indicate that the predefined maximum period of time t_max has been reached in the notification. FIG. 20 includes a graph 200b that illustrates another example timeframe in which periods of time may be determined for providing notifications to a user relative to a disconnection and/or a reconnection between the analyte monitoring device and the computing device. As shown in FIG. 2C, the computing device may delay the notification of the disconnection between the analyte monitoring device and the computing device until the predicted period of time t_predicted has elapsed or until a predefined maximum period of time t_max has elapsed since the time to of disconnection. If the computing device determines that the analyte monitoring device has reconnected with the computing device at a time t_COnnect that is before a predicted period of time t_predicted and/or the predefined maximum period of time t_max, the computing device may prevent the notification of the disconnection from being provided to the user. For example, the computing device may determine that the predicted period of time t_predictedi has elapsed prior to the time t_COnnect at which the analyte monitoring device has reconnected with the computing device and provide a corresponding notification to the user. Additionally, or alternatively, the computing device may determine that the predicted period of time t_predicted3 has failed to elapse prior to the time t_COnnect at which the analyte monitoring device has reconnected with the computing device and prevent a corresponding notification from being provided to the user. The computing device and/or the analyte monitoring device may continue monitoring an analyte value 202b of the user from the time tconnect of reconnection.

In another example, the computing device and/or the analyte monitoring device may delay a reconnection request or ignore a reconnection request from the other device based on the predicted period of time tpredicted. For example, the computing device and/or the analyte monitoring device may prevent additional messages from being communicated on the communication medium and avoid introducing additional interference to communications between other devices by delaying a reconnection request and/or a reconnection response until the predicted period of time tpredicted or a predefined time prior to the predicted period of time t_predicted.

FIG. 3 shows a flowchart of an example process 300 for delaying notifications of a disconnection between an analyte monitoring device and another computing device until one or more conditions are identified. One or more portions of the process 300 may be performed by one or more computing devices. For example, the one or more portions of the process 300 may be performed by one or more mobile devices, such as mobile device 104 shown in FIGs. 1A and 1 B, and/or one or more remote computing devices, such as remote computing device 122 shown in FIGs. 1A- 1C. One or more portions of the process 300 may be performed locally on an analyte monitoring device prior to providing an indication to another computing device for providing a notification of a disconnection between the analyte monitoring device and the computing device to the user. One or more portions of the process 300 may be stored in memory as computer-readable or machine-readable instructions that may be executed by a processor of the one or more computing devices. Though portions of the process 300 may be described herein as being performed by a particular computing device, the process 300 may be performed by another computing device or distributed across multiple computing devices, such as one or more mobile devices, remote computing devices, analyte monitoring devices, and/or one or more other devices.

As illustrated in FIG. 3, at 302 data related to a medical condition of the user may be monitored. For example, the computing device may receive the data related to a medical condition of the user from an analyte monitoring device and/or a remote computing device. The data related to the medical condition of the user may include an analyte level and/or a rate of change of the analyte level. The analyte level may include a blood glucose level or a blood potassium level of the user, for example. The data related to the medical condition may be received via one or more intermediary devices. For example, a remote computing device may monitor data related to the medical condition of the user based on data received from one or more intermediary devices, such as a mobile device in direct communication with the analyte monitoring device.

At 304, a disconnection between the analyte monitoring device and another computing device may be detected. The disconnection may be detected by a computing device, such as a mobile device and/or the analyte monitoring device itself. In response to the detection of the disconnection, the computing device or the analyte monitoring device may predict one or more periods of time at which an analyte level will reach a threshold. Additionally, or alternatively, in response to the detection of the disconnection, the computing device or the analyte monitoring device may send a message to another device for predicting one or more periods of time at which an analyte level will reach a threshold.

At 306, a determination may be made as to whether the analyte level of the user is at or within a threshold range at the time of detection of the disconnection at 304. For example, the analyte monitoring device or another computing device may determine whether the analyte level of the user is within a predefined range that indicates a normal or healthy level. If the analyte level is not at or within the threshold range at 306, a notification may be provided at 307. The notification may indicate that the computing device has disconnected from the analyte monitoring device. The notification may indicate that the analyte level of the user may be approaching or may have reached a predefined threshold. For example, the notification may indicate that the analyte level of the user may be approaching or may have reached a user-defined threshold or a threshold indicating an extreme medical condition or state, such as a state of hyperglycemia, hypoglycemia, hyperkalemia, hypokalemia, or another extreme medical condition or state. At 309, a reconnection between the computing device and the analyte monitoring device may be detected. For example, the computing device may transmit or receive a reconnection request message via a communication medium. The computing device may transmit or receive a reconnection response message in response to the reconnection request message via the communication medium. The computing device may detect that the connection has been reestablished based on the reconnection request/reconnection response message exchange and/or subsequent messages (e.g., depending on the communication protocol). After the analyte monitoring device has reconnected with the computing device, process 300 may return to 302 and date related to the medical condition may continue to be monitored.

If the analyte level is determined to be at or within the threshold range at 306, one or more predicted periods of time may be determined at 308. The one or more predicted periods of time may each include a period of time at which the analyte level of the user may be predicted to reach a corresponding threshold. For example, the corresponding threshold may be a high-end threshold or a low-end threshold of the predefined range indicating the normal or healthy analyte level. The corresponding threshold may be user-defined thresholds or predefined thresholds related to an extreme medical condition or state. The one or more predicted periods of time may each be determined based on the measurement of the analyte level and/or the rate of change of the analyte level at the time the disconnection is determined. For example, the one or more predicted periods of time may be determined using Equation 1 herein. Other similar algorithms or models may be implemented for determining the predicted periods of time.

One or more notifications related to the detected disconnection may be delayed, at 310, until a later triggering event. For example, each of the one or more notifications may be delayed until an expiration of a predicted period of time at which the analyte level is predicted to reach a corresponding threshold or a predefined maximum period of time has elapsed. The one or more notifications may be delayed when the analyte level is at or within the threshold range indicating a normal or healthy analyte level to allow for the analyte monitoring device to reconnect with the computing device and/or without affecting the health of the user. At 312, a determination may be made as to whether one or more of the predicted periods of time has elapsed since the disconnection. If a predicted period of time has not elapsed, a determination may be made, at 314, as to whether a predefined maximum period of time has elapsed since the disconnection. If a maximum period of time since the disconnection has not elapsed, a determination may be made, at 315, as to whether the analyte monitoring device has reconnected with the computing device. If the analyte monitoring device has reconnected with the computing device, the one or more notifications may be canceled to prevent the one or more notifications from being provided to the user and data related to the medical condition may continue to be monitored at 302.

If a triggering event for providing a notification fails to be received and the analyte monitoring device has not yet reconnected with the computing device, the triggering conditions may continue to be monitored for triggering the notification of the disconnection to the user. If one of the predicted periods of time is determined to have lapsed at 312 or the maximum period of time has elapsed at 314, a corresponding notification may be provided to the user at 316. The notification may indicate that the computing device has disconnected from the analyte monitoring device. The notification may indicate that the analyte level of the user may be approaching or may have reached a predefined threshold. The predefined threshold may correspond to the predicted period of time causing the triggering of the corresponding notification. For example, the notification may indicate that the analyte level of the user may be approaching or may have reached a user-defined threshold or a threshold indicating an extreme medical condition or state, such as a state of hyperglycemia, hypoglycemia, hyperkalemia, hypokalemia, or another extreme medical condition or state.

At 318, a determination may be made as to whether there are additional notifications pending to be provided. If the maximum period of time has elapsed, any of the additional notifications that are pending as a result of the disconnection may be canceled and prevented from being provided. If the computing device is capable of providing multiple notifications based on different predicted periods of time (e.g., a notification that relates to a user-defined threshold and/or a notification that relates to a predefined threshold for an extreme medical condition), then the process may continue to monitor other predicted periods of time relating to other thresholds, as well as the disconnected status of the devices.

FIGs. 4A-4C depict illustrations of GUIs displaying example overlay notifications on a display 404 of a computing device 400. The GUIs may be generated by software executing on the computing device 400. As shown in FIG. 4A, an overlay notification 408 may be displayed on the display 404 of the computing device 400. The overlay notification 408 may be overlaid on the graphical user interface 406 (e.g., on an application related to the medical condition of the user, a lock screen, a home screen, a call screen, and/or other graphical user interface), when the graphical user interface 406 is displayed to the user. The overlay notification 408 may be provided as a medical overlay notification providing information related to the medical condition of the user. For example, the overlay notification 408 may be provided as a diabetic overlay notification providing information related to the diabetic condition of the user or another overlay notification related to another medical condition of the user. The information provided on the overlay notification 408 may include an indication 410 that the computing device 400 has detected a disconnection from the analyte monitoring device. The overlay notification 408 may be provided after a predicted period of time related to a threshold of the analyte level has elapsed from the time of the disconnection. The overlay notification 408 may be provided after a predefined maximum period of time has elapsed from the time of the disconnection.

As shown in FIG. 4B, an overlay notification 408a may include one or more different types of information. For example, the overlay notification 408a may include a suggestion or link 411 with instructions or a procedure to re-establish the connection between the computing device 400 and the analyte monitoring device. The overlay notification 408a may also or alternatively include an indication 412 that the analyte level of the user may be approaching or may have reached a predefined threshold. The predefined threshold may correspond to a predicted period of time related to a corresponding threshold analyte level. The indication 412 may inform the user or suggest to use an alternative analyte monitoring device to check the analyte level of the user. The overlay notification 408a may include an indication 414 of the analyte level of the user at the time of the disconnection. For example, the overlay notification 408a may include an indication of the user’s blood glucose level or blood potassium level at the time of the disconnection. The overlay notification 408a may include an indication 416 of the predicted analyte level of the user at the time of the display of the overlay notification 408a. For example, the overlay notification 408a may include an indication of the user’s predicted blood glucose level or blood potassium level at the time of the triggering of the overlay notification 408a, which may be the value of the corresponding threshold (e.g., user-defined threshold or threshold of the extreme medical condition or event).

As shown in FIG. 40, the overlay notification 408c may include an indication 418 that the analyte monitoring device has reconnected to the computing device 400. The indication 418 of the reconnection may be provided in response to a detection of the reconnection with the analyte monitoring device. After being reconnected, the overlay notification 408c may include a current analyte level of the user.

FIG. 5 is a block diagram of an example computing device 500. The computing device 500 may be a mobile computing device, such as a tablet, a cellular phone, a wearable device, an analyte monitoring device (e.g., a CGM controller device), a remote computing device, or another computing device, for example. As shown in FIG. 5, the computing device 500 may include a processor 502 for controlling the functionality of the computing device 500. The processor 502 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 502 may perform signal coding, data processing, power control, image processing, input/output processing, or any other functionality that enables the computing device 500 to perform as described herein.

The processor 502 may store information in or retrieves information from the memory 516. The memory 516 includes a non-removable memory or a removable memory. The non-removable memory includes random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory includes a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), or any other type of removable memory. The processor 502 may access the memory 516 for executable instructions or other information that is used by the computing device 500. For example, the memory 516 may include computer-readable or machine-readable instructions that may be executed by the processor 502 for performing one or more methods, processes, or procedures, or portions thereof, as described herein. The computing device 500 may include a camera 506 that is in communication with the processor 502. The camera 506 may be a digital camera or other optical device capable of generating images or videos (e.g., image sequences) for being captured at the computing device 500. The camera 506 may include a lighting device capable of flashing to in response to signals from the processor 502.

The computing device 500 may include one or more communication circuits 518. The processor 502 may be in electrical communication with the communication circuit 518 for sending or receiving information. The communication circuit 518 may be capable of performing wired and/or wireless communications. For example, the communication circuit 518 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signals (e.g., BLUETOOTH®, near field communication (NFC), WIFI®, WI-MAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. In some embodiments, one or more communication circuits 518 are capable of performing infrared (IR) communications.

The processor 502 may be in electrical communication with a keypad 524 for providing input to the processor 502. The keypad 524 may include one or more keys for receiving input from a user. The keypad 524 may include hard or soft keys for which the function of the keys changes as a user performs selections.

Other input into the processor 502 may be provided by one or more sensors 526. The sensors 526 include a motion sensor, a proximity sensor, a heartrate monitoring sensor, an accelerometer, a gyroscope, and/or another sensor on the computing device 500. The motion sensor may transmit infrared signals or use image processing to sense movement. The proximity sensor may transmit infrared signals to detect when an object is within a predefined proximity. The heartrate monitoring sensor may implement photoplethysmography to detect the amount of blood flow in the user. The heartrate monitoring sensor may include one or more LED or photodiodes to detect the amount of blood flow in the user. The heartrate monitoring sensor may implement infrared technology to detect the amount of blood flow in the user. The heartrate monitoring sensor may take an electrocardiogram (ECG) and detect information about the user’s heartrate from the ECG. The accelerometer may measure the non-gravitational acceleration of the computing device 800 in a given direction. The accelerometer may respond to vibrations associated with movement in a given direction. The measurements from the accelerometer may be used by the processor 502 to determine the magnitude or direction of the relative movement of the computing device 500, or the user’s relative position (e.g., standing, sitting, or lying down). The gyroscope may be used to determine the orientation of the computing device 500.

The processor 502 may be in electrical communication with or generate images on a display 520 for providing information to a user. The communication between the display 520 and the processor 502 may be a two-way communication, as the display 520 may include a touch screen module capable of receiving information from a user and providing such information to the processor 502. For example, the display 520 may provide soft buttons for selection by a user that are recognized by the touch screen module and provided to the processor 502 as input.

The processor 502 may be in electrical communication with or control a speaker 508. The speaker 508 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 502.

The computing device 500 may include an electric motor 510 that is in electrical communication with or controlled by the processor 502. The electric motor 510 may rotate and causes the computing device 500 to vibrate (e.g., to indicate a notification) or provide haptic feedback in response to a triggering event detected by the processor 502.

The processor 502 may be in electrical communication with or receive information from a microphone 514. For example, the processor 502 may receive audio signals via the microphone 514.

The computing device 500 may include a global positioning system (GPS) circuit 504. The GPS circuit 504 may be capable of receiving GPS information. The processor 502 may be capable of determining the GPS coordinates (e.g., latitude and longitude) of the computing device 500 based on the GPS information received via the GPS circuit.

The computing device 500 may include a visual indicator, such as one or more light-emitting diodes (LEDs) 512. In some embodiments, one or more LEDs 512 are illuminated or flashed to provide an alert or communicate other information to the user (e.g., low battery or turning on of the device).

FIG. 6 is a block diagram of an example continuous monitoring device 600. In some embodiments, the continuous monitoring device 600 is a CGM or FGM, for example. The continuous monitoring device 600 may include a subcutaneous sensor 626 that is used to sense and monitor the amount of glucose in interstitial fluid of the user. Data is transmitted from the sensor 626 to a transmitting device 604. When the continuous monitoring device 600 is a CGM, the transmitting device 604 is located directly over the sensor 626 and wirelessly powers the data transfer from the sensor 626 via power supply 620. When the continuous monitoring device 600 is an FGM, the transmitting device 604 is a mobile device or other reader device that instantaneously receives the information from the sensor 626 when the device is within the RF range of the sensor 626.

The transmitting device 604 receives data communications from the sensor 626 via a communication circuit 618. The communication circuit 618 may be in electrical communication with a processor 602. The processor 602 may include one or more circuits, such as general- purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 602 may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the transmitting device 604 to perform as described herein.

The transmitting device 604 may include another communication circuit 616 for communicating with other devices. The processor 602 may be in electrical communication with the communication circuit 616 for sending or receiving information. The communication circuits 616, 618 are capable of performing wired or wireless communications. For example, the communication circuits 616, 618 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signals (e.g., BLUETOOTH®, near field communication (NFC), WIFI®, WI-MAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. The communication circuits 616, 618 may communicate using the same RF protocol or a different RF protocol. The processor 602 may store information in or retrieve information from the memory 612. The memory 612 may include a non-removable memory or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), or any other type of removable memory. For example, the memory 612 may include computer-readable or machine-readable instructions that may be executed by the processor 602 for performing one or more methods, processes, or procedures, or portions thereof, as described herein. The processor 602 may access the memory 612 for executable instructions or other information that is used by the transmitting device 604. The processor 602 is in electrical communication with one or more input keys 624 for providing input to the processor 602.

The processor 602 may be in electrical communication with or control a speaker 614. The speaker 614 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 602.

The continuous monitoring device 600 may include an electric motor 610 that is in electrical communication with or controlled by the processor 602. The electric motor 610 may rotate and causes the continuous monitoring device 600 to vibrate (e.g., to indicate a notification) or provide haptic feedback in response to a triggering event detected by the processor 602. The electric motor 610 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 614.

FIG. 7 is a block diagram of an example blood glucose meter (BGM) device 700. As shown in FIG. 7, the BGM device 700 may include a processor 702 for controlling the functionality of the BGM device 700. The processor 702 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The processor 702 may perform signal coding, data processing, power control, image processing, input/output processing, and/or any other functionality that enables the BGM device 700 to perform as described herein. The processor 702 may store information in or retrieve information from the memory 716. The memory 716 may include a non-removable memory or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, and/or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), and/or any other type of removable memory. The memory 716 may include computer-readable or machine-readable instructions that may be executed by the processor 702 for performing one or more methods, processes, or procedures, or portions thereof, as described herein. The processor 702 may access the memory 716 for executable instructions or other information that is used by the BGM device 700.

The BGM device 700 may include one or more communication circuits 718. The processor 702 may be in electrical communication with the communication circuit 718 for sending or receiving information. The communication circuit 718 may be capable of performing wired and/or wireless communications. For example, the communication circuit 718 may include one or more radio frequency (RF) transceivers for transmitting and receiving RF signals (e.g., BLUETOOTH®, near field communication (NFC), WIFI®, WI-MAX®, cellular, or other RF signals) via an antenna, or other communications module capable of performing wireless communications. In some embodiments, one or more communication circuits 718 may be capable of performing infrared (IR) communications.

The processor 702 may be in electrical communication with a keypad 724 for providing input to the processor 702. The keypad 724 may include one or more keys for receiving input from a user. The keypad 724 may include hard or soft keys for which the function of the keys changes as a user performs selections.

Other input into the processor 702 may be provided by the BGM sensor module 704. The BGM sensor module 704 may include a blood glucose measuring engine that may analyze blood samples provided by a patient on a blood glucose measurement strip and measure the amount of blood glucose in the samples.

The processor 702 may be in electrical communication with or generate images on a display 706 for providing information to a user. The communication between the display 706 and the processor 702 may be a two-way communication, as the display 706 may include a touch screen module capable of receiving information from a user and providing such information to the processor 702. For example, the display 706 may provide soft buttons for selection by a user that are recognized by the touch screen module and provided to the processor 702 as input.

The processor 702 may be in electrical communication with or control a speaker 708. The speaker 708 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 702.

The BGM device 700 may include an electric motor 710 that is in electrical communication with or controlled by the processor 702. The electric motor 710 may rotate and cause the BGM device 700 to vibrate (e.g., to indicate an notification) or provide haptic feedback in response to a triggering event detected by the processor 702. The electric motor 710 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 708.

The processor 702 may be in electrical communication with or receive information from a microphone 722. For example, the processor 702 may receive audio signals via the microphone 722.

The BGM device 700 may include a visual indicator, such as one or more one or more lightemitting diodes (LEDs) 728. In some embodiments, one or more LEDs 728 are illuminated or flashed to provide an alert or communicate other information to the user (e.g., low battery or turning on of the device).

Although features, elements, and functions are described above in particular combinations, a feature, element, or function is used alone or in any combination with the other features, elements, or functions. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements may be subsequently made that are also intended to be encompassed by the following claims.

The methods described herein are implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random-access memory (RAM), removable disks, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

Claims

1. A method comprising:

- receiving, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a plurality of measurements of an analyte level (202, 202a) of a user (100) and a rate of change of the analyte level (202, 202a);

- detecting a disconnection with the analyte monitoring device via the communication medium; and

- detecting that the analyte level (202, 202a) of the user (100) is within a threshold range (210) at a time of the disconnection; characterized by:

- in response to the detection of the disconnection with the analyte monitoring device and after the determination that the analyte level (202, 202a) of the user (100) is within the threshold range (210), determining, based on the measurement of the analyte level (202, 202a) and the rate of change of the analyte level (202, 202a), a predicted period of time at which a threshold (206a, 206b, 208a, 208b) related to the analyte level (202, 202a) will be reached;

- delaying a notification (408, 408a, 408c) to the user (100) related to the disconnection until the predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device; and

- after the predicted period of time has elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, providing the notification (408, 408a, 408c) to the user (100) indicating the disconnection with the analyte monitoring device.

2. The method of claim 1 , wherein the measurement of the analyte level (202, 202a) is a first measurement, wherein the rate of change is a first rate of change of the analyte level (202, 202a), wherein the disconnection is a first disconnection, wherein the predicted period of time is a first predicted period of time, and wherein the notification (408, 408a, 408c) is a first notification, the method further comprising:

- detecting a reconnection with the analyte monitoring device;

- receiving, via the communication medium, a second measurement of the analyte level (202, 202a) of the user (100) and a second rate of change of the analyte level (202, 202a);

- detecting a second disconnection with the analyte monitoring device via the communication medium; - in response to the detection of the second disconnection with the analyte monitoring device, determining, based on the second measurement of the analyte level (202, 202a) and the second rate of change of the analyte level (202, 202a), a second predicted period of time at which the threshold (206a, 206b, 208a, 208b) related to the analyte level (202, 202a) will be reached;

- determining that the second predicted period of time is greater than a predefined maximum period of time for delaying notifications (408, 408a, 408c) related to disconnections with the analyte monitoring device; and

- delaying a second notification related to the second disconnection from being provided to the user (100) until the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device; and

- after the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, providing the second notification to the user (100) indicating the disconnection with the analyte monitoring device.

3. The method of claim 1 or 2, wherein the disconnection is between a mobile device (104) and the analyte monitoring device.

4. The method of any of the preceding claims, wherein the threshold (206a, 206b, 208a, 208b) comprises a high-end threshold or a low-end threshold related to the analyte level (202, 202a) of the user (100).

5. The method of claim 4, wherein the threshold (206a, 206b, 208a, 208b) is a user (100) defined threshold (206a, 206b, 208a, 208b) or a predefined threshold (206a, 206b, 208a, 208b) related to an extreme diabetic state, wherein the high-end threshold related to the extreme diabetic state comprises a state of hyperglycemia, and wherein the low-end threshold related to the extreme diabetic state comprises a state of hypoglycemia.

6. The method of claim 5, further comprising:

- receiving a user indication to set the threshold (206a, 206b, 208a, 208b) to one of the user (100) defined threshold (206a, 206b, 208a, 208b) or the predefined threshold (206a, 206b, 208a, 208b) related to the extreme diabetic state; and

- determining, based on the user indication, the predicted period of time based on one of the user (100) defined threshold (206a, 206b, 208a, 208b) or the predefined threshold (206a, 206b, 208a, 208b) related to the extreme diabetic state.

7. The method of any of claims 4 to 6, wherein the rate of change of the analyte level (202, 202a) is a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold.

8. The method of any of the preceding claims, wherein the notification (408, 408a, 408c) comprises at least one of an audible notification, a tactile notification, a vibratory notification, and a visual notification, wherein the visual notification is preferably provided via a display (112, 404, 520, 706) or a light emitting diode.

9. The method of any of the preceding claims, wherein the analyte monitoring device is a continuous glucose monitor.

10. The method of any of the preceding claims, wherein the method is performed by an application executing on a mobile device (104).

11. At least one computer-readable storage medium having instructions stored thereon that are configured, when executed by at least one processor (502, 602, 702), to cause the at least one processor (502, 602, 702) to:

- receive, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a measurement of a blood- analyte level (202, 202a) of the user (100) and a rate of change of the analyte level (202, 202a); and

- detect that the analyte level (202, 202a) of the user (100) is within a threshold range (210) at a time of the disconnection; characterized by:

- in response to the detection of the disconnection with the analyte monitoring device and after the determination that the analyte level (202, 202a) of the user (100) is within the threshold range (210), determine, based on the measurement of the analyte level (202, 202a) and the rate of change of the analyte level (202, 202a), a predicted period of time at which a threshold (206a, 206b, 208a, 208b) related to the analyte level (202, 202a) will be reached;

- in response to the predicted period of time having elapsed without a detection of the reconnection to the analyte monitoring device via the communication medium, provide a notification (408, 408a, 408c) to the user (100) indicating the disconnection with the analyte monitoring device; and

- in response to the detection of the reconnection to the analyte monitoring device prior to the predicted period of time having elapsed, cancel the notification (408, 408a, 408c) to prevent the notification (408, 408a, 408c) from being provided to the user (100).

12. The at least one computer-readable storage medium of claim 11 , wherein the instructions are further configured to cause the at least one processor (502, 602, 702) to:

- determine that the predicted period of time is greater than a predefined maximum period of time for delaying notifications (408, 408a, 408c) related to disconnections with the analyte monitoring device; and

- in response to detection of the predefined maximum period of time having elapsed without detecting the reconnection to the analyte monitoring device via the communication medium, provide the notification (408, 408a, 408c) to the user (100) indicating the disconnection with the analyte monitoring device.

13. A method comprising:

- receiving, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a plurality of measurements of an analyte level (202, 202a) of a user (100) and a rate of change of the analyte level (202, 202a); and

- delaying a notification (408, 408a, 408c) to the user (100) related to the disconnection;

- detecting a reconnection to the analyte monitoring device via the communication medium prior to an expiration of the predicted period of time; and - in response to the reconnection being detected prior to the expiration of the predicted period of time, cancel the notification (408, 408a, 408c) to prevent the notification (408, 408a, 408c) from being provided to the user (100).

14. An apparatus comprising a processor (502, 602, 702) configured to perform the method as recited in any of claims 1 to 10 or 13.

15. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method of any of claims 1 to 10 or 13.