Continuous sensor connection loss notification management

Abstract

Data loss related to data from a peripheral medical monitoring device may be managed at a central medical monitoring device. The central medical monitoring device may detect an established communication session between with the peripheral medical monitoring device. During the establishment of the communication session, the central medical monitoring device may receive data messages and may initiate or restart an application termination timer and, based on an expiration of the application termination timer, the central medical monitoring device may provide an application termination notification. The central medical monitoring device may detect connection losses between the central medical monitoring device and the peripheral medical monitoring device and initiate a connection loss timer to provide connection loss notifications prior to re-establishment of the communication session with the peripheral medical monitoring device.

Description

Matter No. P39494-WOCONTINUOUS SENSOR CONNECTION LOSS NOTIFICATION MANAGEMENTBACKGROUND

[0001] 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. 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.

[0002] 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.

[0003] 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, such as a continuous glucose monitor. These devices may communicate via a communication medium, such as wireless RF communication signals.

[0004] In the field of device communication, including communications between the mobile device of a user and other medical monitoring devices, the communications between devices may depend on basic wireless protocols to establish and maintain connections between monitoring devices and sensors. For example, these communications may rely on standard BLUETOOTH or WI-FI connections to facilitate data exchange, which may be prone to interruptions due to environmental interference or device movement. Such communications may lack the capability to dynamically adapt to these disruptions, resulting in data loss. This loss of data between a mobile device of the user and other medical monitoring devices may result in unreliable monitoring and / or improper treatment of the user’s medical condition. In certain cases, such as when the mobile device may be in frequent communication with a medicalMatter No. P39494-WO monitoring device (e.g.. a continuous glucose monitor or other analyte monitoring device) to assist in treatment of a more significant medical condition, the loss of data may affect the monitoring and / or treatment of the user’s medical condition more significantly.

[0005] In addition to potential communication issues, a user’s mobile device may utilize a fixed notification framework that does not account for variations in user-specific health conditions or environmental contexts. As a result, users may receive notifications that are either too frequent or untimely, leading to potential safety risks in assisting in treatment of the user’s medical condition and / or over utilization of resources on power-conservative devices being leveraged to assist in the treatment of the user’s medical condition. For example, the power consumption associated with continuous data transmission and frequent notifications may pose a significant challenge to effectively monitoring and / or assisting in the treatment of the user’s medical condition, particularly for devices that may be in frequent communication (e.g., the user’s mobile device and a continuous glucose monitor or other analyte monitoring device) to assist in treatment of a more significant medical condition.SUMMARY

[0006] Systems, methods, and apparatus are described herein for managing data loss between a central medical monitoring device and a peripheral medical monitoring device and notifying the user to enable remedial action. As described herein, the central medical monitoring device may include a mobile user device. The peripheral medical monitoring device may include a sensor capable of sensing one or more analyte values. For example, the peripheral medical monitoring device may include a glucose monitoring device, such as a continuous glucose monitor.

[0007] The central medical monitoring device may detect an established communication session between with the peripheral medical monitoring device. During the establishment of the communication session, the central medical monitoring device may receive a first data message. The central medical monitoring device may initiate or restart an application termination timer in response to receipt of the data message. The application termination timer may be configured to trigger a notification upon expiration without receiving another data message prior to the expiration of the application termination timer. Based on an expiration of the application termination timer, the central medical monitoring device may provide an application termination notification. The application termination notification may include a notification to execute theMatter No. P39494-WO application (e.g, in a foreground layer of the central medical monitoring device) for enabling logging of data in the first data message.

[0008] The central medical monitoring device may detect a connection loss between the central medical monitoring device and the peripheral medical monitoring device. The central medical monitoring device may initiate, in response to the connection loss, a connection loss timer. Based on an expiration of the connection loss timer, the central medical monitoring device may may provide a connection loss notification. The connection loss notification may be provided via an application or an operating system of the central medical monitoring device. The connection loss notification may comprise a first connection loss notification associated with at least one of a first priority or first visibility level. Based on at least one second expiration of the connection loss timer, the central medical monitoring device may provide at least one second connection loss notification associated with at least one of a higher priority or higher visibility level than the first priority or the first visibility level. The central medical monitoring device may detect a re-establishment of the communication session with the peripheral medical monitoring device and receive a second data message.

[0009] The first connection loss notification may be provided as a visual overlay notification in the application associated with the peripheral medical monitoring device via a graphical user interface (GUI) to indicate the connection loss. The at least one second connection loss notification may include a visual operating system (OS)-level notification via a graphical user interface (GUI) of the central medical monitoring device. The at least one second notification may include at least one of an audible notification or haptic feedback to escalate the priority or visibility level of the at least one second notification to increase a likelihood that the at least one second notification is received by a user.

[0010] The peripheral medical monitoring device may include a glucose monitoring device or other analyte monitoring device. The central medical monitoring device may dynamically adjust the connection loss timer based on a medical state (e.g., diabetic state) indicated by one or more messages received from the glucose monitoring device or other analyte monitoring device. The application termination timer may be initiated to a predefined period of time that is less than a period of time in which a plurality of messages are configured to be received from the glucose monitoring device or other analyte monitoring device.Matter No. P39494-WOBRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIGs. 1 A and IB show a perspective view of representative user environments.

[0012] FIG. 2 shows a flowchart of an example process for managing data loss between a central medical monitoring device and a peripheral medical monitoring device and notifying the user to enable remedial action.

[0013] FIG. 3 shows a flowchart of an example process for receiving EMWR events in data messages at a central medical monitoring device from a peripheral medical monitoring device and providing notifications and / or logging the events.

[0014] FIGs. 4A-4C depict example GUIs illustrating overlay notifications provided on a display of a central medical monitoring device.

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

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

[0017] FIG. 7 is a block diagram of an example blood glucose meter (BGM) device.DETAILED DESCRIPTION

[0018] FIG. 1 A is a perspective view of a representative user environment. As shown in FIG. 1A, a user 100 may be a person with a medical condition. For example, the user 100 may be a person with a 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.

[0019] The one or more devices that may be used to help monitor and / or treat the medical condition of the user 100 may include a central medical monitoring device and / or one or more peripheral medical monitoring devices. For example, a mobile device 104 of the user 100 may operate as a central medical monitoring device, as the mobile device 104 may be configured with applications and / or other software for managing the medical condition of the user, communicating with multiple devices for sending / receiving data for managing the medical condition, and / or performing other functionality central to the management of the medicalMatter No. P39494-WO condition of the user 100. In another example, a remote computing device 122 may operate as a central medical monitoring device. Though a single central medical monitoring device may be provided as an example, one or more central medical monitoring devices may be implemented for performing, as described herein. One or more other medical monitoring devices may operate as peripheral devices or peripheral medical monitoring devices capable of connecting to the central medical monitoring device (e.g., mobile device 104) for transmitting data and / or receiving instructions that may allow the user 100 to monitor and / or treat their medical condition. In one example, the one or more peripheral medical monitoring devices may include sensors for measuring one or more analyte levels of the user 100. The central medical monitoring device (e.g., mobile device 104) may receive data from the one or more peripheral medical monitoring devices for being displayed to the user 100 and / or for being communicated to other computing devices (e. , remote computing device 122). Peripheral devices may also, or alternatively, be referred to as slave devices.

[0020] The peripheral medical monitoring devices may include one or more glucose monitoring devices that may be used to monitor blood glucose levels and / or one or more blood glucose treatment devices that may be used to treat a diabetic condition of the user 100. 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.

[0021] 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 periodicallyMatter No. P39494-WO 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.

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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 theMatter No. P39494-WO 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.

[0026] 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®, WIMAX®, 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 peripheral medical monitoring devices that may operate as analyte monitoring devices, other analyte monitoring devices may be implemented for measuring and / or monitoring other analyte levels of the user 100.

[0027] The mobile device 104 may establish a connection to one or more peripheral medical 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 wiredMatter No. P39494-WO or a wireless communication protocol, such as BLUETOOTH®, NFC, THREAD®, WIFI®, ZIGBEE®, WI-MAX®, 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).

[0028] 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.

[0029] 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.

[0030] The mobile device 104 may be configured to determine information corresponding to the device’s location (i.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. TheMatter No. P39494-WO 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.

[0031] 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.

[0032] 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 analyte levels (e.g. blood glucose 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.

[0033] 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®,Matter No. P39494-WOBLE, 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.

[0034] 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.

[0035] 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 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 notifications to the user 100. 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 theMatter No. P39494-WO 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.

[0036] The mobile device 104 may provide a notification (e.g., or alert) to 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.

[0037] 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 104 becomes disconnected from another device (e.g., one or more peripheral medical monitoring devices), 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. IB, the mobile device 104 may become disconnected from one or more peripheral medical monitoring devices, which may include 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 peripheral medical monitoring devices may be the result of the peripheral medical monitoring device losing power, a range or distance between the mobile device 104 and the peripheral medical monitoring 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 peripheral medical monitoring device are communicating on a BLUETOOTH communication link, the greater the number of other devices communicating within the same space on the same communication link may cause a greater amount of interference with the communications between the peripheral medical monitoring device and the mobile device 104. A relatively strong source of interference on an overlapping RF band can also cause interferenceMatter No. P39494-WO with the communications between the mobile device 104 and the peripheral medical monitoring. For example, if the mobile device 104 and the peripheral medical monitoring 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 peripheral medical monitoring and the mobile device 104 due to the overlapping portions of the communication band e.g., overlapping portions of the 2.4 GHz ISM band) on which the protocols may communicate. When the interference level of communications between the peripheral medical monitoring device and the mobile device 104 is above a certain threshold, the peripheral medical 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, other peripheral medical monitoring devices in the system, and / or other third-party devices communicating with the mobile device 104 on the same protocol or communication link.

[0038] In response to devices, such as one or more of the peripheral medical monitoring devices 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 peripheral medical monitoring device are disconnected and provide the notification to the user 100. The disconnection may be detected by the application executing on the mobile device 104 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 peripheral medical monitoring 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 104. 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).

[0039] As the interference level between the mobile device 104 and the peripheral medical monitoring 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 peripheralMatter No. P39494-WO medical monitoring device causing multiple notifications to be provided to the user 100 within the period of disconnections and reconnections.

[0040] 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.

[0041] Notifications 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).

[0042] The notifications related to disconnected devices may be adjusted to reduce the impact on the user 100, the mobile device 104, the peripheral medical 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 or higher- resource notifications 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 priorityMatter No. P39494-WO or visibility level of the notifications may be increased as the period of time of the disconnection extends to prevent the user from receiving higher priority or visibility notifications when the RF communication link may cause multiple disconnections and reconnections within short period of time, but allow for higher-priority or visibility notifications to be provided when the disconnections persist. The delay in providing notifications or increasing the priority or visibility level of the notifications may allow some time for reconnection between the devices without providing a notification or higher priority / visibility notification to the user 100. This may prevent the mobile device 104 from utilizing resources (e.g., battery resources, processing resources, and / or RF communication resources), or utilize less resources, prior to an expiration of time.

[0043] Even when the mobile device 104 is able to maintain a connection, the 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) to which data received over the connection is directed at the application layer may be closed or terminated and unable to log the data for monitoring the medical condition of the user. For example, the application may be closed or terminated (e.g., by a user input) for power management by user input or in response to power management settings that indicate that power utilization by the application is above a defined threshold at the central medical monitoring device. When the application is closed or terminated, it may be unable to track or log the data (e.g., analyte measurements or other sensor measurement) received from the peripheral medical monitoring application. The central medical monitoring device may utilize background resources for receiving and storing the data while the application is terminated. The operating system implemented on the central medical monitoring device may manage the background resources for storing the received data from the peripheral medical monitoring. As the background resources may be limited and the data may be received periodically from the peripheral medical monitoring device, the data may be discarded prior to being logged by the application and / or the data may over leverage background resources on the central medical monitoring device.

[0044] In accordance with various embodiments, systems and methods may be provided for managing communication and data integrity between a central medical monitoring device, such as the mobile device 103, and a peripheral medical monitoring device. The central medicalMatter No. P39494-WO monitoring device may efficiently maintain a stable communication link using, facilitating secure data exchange and real-time monitoring. The central medical monitoring device may monitor the connection for interruptions, and may employ adaptive reconnection strategies, such as channel switching and transmission power adjustments, to swiftly restore connectivity and minimize data loss.

[0045] In some embodiments, integrated timer mechanisms may be utilized within the central medical monitoring device. These timers may coordinate monitoring and reconnection processes by tracking connection loss durations and data reception intervals, optimizing alert issuance and reconnection protocols. The device may utilize these timers to manage the interplay between notifications and connection management, ensuring efficient and effective user alerts without redundancy.

[0046] By adapting its operations based on environmental, contextual, and / or user-specific factors, the central medical monitoring device may optimize battery consumption while maintaining timely and accurate alerts. This comprehensive approach may enhance the reliability of diabetes management, offering a robust and responsive solution for continuous glucose monitoring and patient safety. The coordinated operations of the central medical monitoring device may ensure a seamless and user-centered experience, adapting dynamically to the user's needs and the device's operational conditions.

[0047] FIG. 2 shows a flowchart of an example process 200 for managing data loss between a central medical monitoring device and a peripheral medical monitoring device and notifying the user to enable remedial action. One or more portions of the process 200 may be performed by one or more computing devices. For example, the one or more portions of the process 200 may be performed by central medical monitoring devices, such as mobile device 104 shown in FIGs.1 A and IB, and / or one or more remote computing devices, such as remote computing device 122 shown in FIGs. 1A-1B. One or more portions of the process 200 may be performed by a peripheral medical monitoring device, such as an analyte monitoring device (e.g., continuous glucose monitor) or another medical monitoring device. One or more portions of the process 200 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 200 may be described herein as being performed by a particular computing device, the process 200 may be performed by another computing device or distributed across multiple computingMatter No. P39494-WO devices, such as one or more central medical monitoring devices (e.g., mobile devices, remote computing devices, or other central medical monitoring devices), peripheral medical monitoring devices (c.g., analyte monitoring devices), and / or one or more other devices.

[0048] As shown in FIG. 2, at 202, a wireless communication session may be initiated on a wireless communication link between a central medical monitoring device (e.g., a mobile device) and a peripheral medical monitoring device (e.g, an analyte monitoring device, such as a continuous glucose monitoring device ). For example, the central medical monitoring device may initiate device communication by establishing a BLUETOOTH or BLUETOOTH Low Energy (BLE) connection between the central medical monitoring device and the peripheral medical monitoring device on a communication layer between the central medical monitoring device and the peripheral medical monitoring device. The central medical monitoring device may establish this connection via a communication layer by scanning for peripheral medical monitoring devices, identifying the peripheral medical monitoring devices through unique identifiers, and initiating secure pairing protocols with at least one peripheral medical monitoring device. Once identified, the central medical monitoring device may initiate secure pairing protocols with the peripheral medical monitoring device, which may include exchanging public keys for encrypted data transmission to ensure security and data integrity. The central medical monitoring device may negotiate connection parameters (e.g., data rates, intervals, and / or transmission power) to optimize power consumption and data reliability. After successful pairing, the central medical monitoring device may maintain the status of the connection, keeping the communication channel open and ready for data exchange, which can include, for example, periodically sending keep-alive signals to maintain the connection and confirm connection stability and / or quality above a threshold.

[0049] At 204, the central medical monitoring device may monitor the status of the connection of the communication session between itself and the peripheral medical monitoring device to detect any interruptions. This monitoring may involve regular checks for data packet exchanges and / or assessing connection integrity, such as verifying the presence of expected acknowledgment signals for transmitted packets. The central medical monitoring device may identify patterns in disconnection events, allowing it to take predictive measures to enhance connection stability, thereby ensuring continuous monitoring.Matter No. P39494-WO

[0050] At 206, the central medical monitoring device may determine whether a connection loss has been detected. A connection loss may be detected when the quality of the communication signals on the wireless communication link are below a threshold. If no connection loss has been detected at 206, the central medical monitoring device may continue monitoring the connection status without any disruption to detect receipt of data (e.g., analyte values, other sensor measurements, and / or other data) from the peripheral medical monitoring device at 224. The connection on the wireless communication link may remain stable, and the central medical monitoring device may ensure regular data exchanges with the peripheral medical monitoring device, applying any adjustments appropriate to maintain the connection, such as, for example, optimizing signal strength or reducing interference.

[0051] If a connection loss has been detected at 206, the process may proceed to 211, where the central medical monitoring device may initiate a series of actions to notify the user and / or attempt to restore the connection. The connection loss may be indicated by the operating system that is monitoring the connection. At 211, upon detecting a connection loss, the central medical monitoring device may initiate a connection loss timer. The connection loss timer may be initiated to a predefined period of time (e.g., 10 minutes) to determine whether the disconnection persists for the predefined period of time without re-establishing connection. The connection loss timer may correspond to and / or overlap with a period of time in which messages may be anticipated to be received from the peripheral medical monitoring device. For example, the connection loss timer may be set to a period of time (e.g., ten minutes) that is a multiple of a period of time anticipated for receiving messages from the peripheral medical monitoring device (e.g., five minutes) reporting data (e.g., analyte measurement values and / or other data). The connection loss timer may be set to a predefined period of time in an effort to attempt to avoid missing a predefined (e.g., multiple) number of messages from the peripheral medical monitoring device without increasing the priority or urgency associated with the notification for alerting the user as to the status of the connection loss.

[0052] The central medical monitoring device may determine whether the connection loss timer expires at 212 without re-establishing a connection at 215. If the central medical monitoring device re-establishes connection at 215 with the peripheral medical monitoring device before the expiration of the connection loss timer at 212, the central medical monitoring device may continue monitoring the re-established connection. During the period in which the centralMatter No. P39494-WO medical monitoring device is atempting to re-establish connection at 215, the central medical monitoring device may periodically notify the user that reconnection efforts are ongoing.

[0053] If the connection loss timer expires at 212 without the re-establishment of the connection with the peripheral medical monitoring device at 215, the central medical monitoring device may increase a level of the connection loss notification at 216 and provide a notification corresponding to the level of the connection loss notification at 217. For example, the level of the connection loss notification may be initiated at a first level connection loss notification. The level of the connection loss notification may be increased to increase the level of priority or visibility associated with the status of the connection loss. Before increasing a level of the connection loss notification at 216, the central medical monitoring device may determine whether it is at a highest level connection loss notification at 213, as the levels of connection loss notifications may be limited to a predefined number and / or have a predefined order.

[0054] A first-level connection loss notification or initial level connection loss notification may be provided to alert the user. This notification may be prompted by a failure to receive data packets within a period of time, a drop in signal strength below a threshold, or a lack of acknowledgment signals within a specified duration (e.g., 30 seconds). The central medical monitoring device may update its user interface to display the first level connection loss notification.

[0055] The first level connection loss notification may indicate an initial level of priority or visibility associated with the status of the connection loss. As the connection loss is associated with a communication link with which the central medical monitoring device is performing communication with a peripheral medical monitoring device configured to report data (e.g., analyte values and / or other sensor values or data) for enabling the user to monitor and properly treat their medical condition, the level of priority or visibility associated with the status of the connection loss may be updated to increase the likelihood of obtaining the user’s attention for addressing the connection loss. However, as the connection may be lost and regained a number of times within a relatively short time period, the first level connection loss notification may be provided in a less invasive manner and / or lower level of visibility to avoid utilizing additional resources on the central medical monitoring device (e.g., battery resources, processing resources, etc.) and / or desensitizing the user to higher priority notifications or notification fatigue.Matter No. P39494-WO

[0056] In one example, the first level connection loss notification may be provided as an overlay notification indicating the connection loss within the application when the application is being displayed in a foreground layer of the central medical monitoring device for user visibility. In another example, the first level connection loss notification may be stored in a notifications tab in the application for being displayed in response to a user selection. The notification tab may be identified with a notification icon alerting the user that the notification is stored for review. The first level connection loss notification may include an operating system (OS)-level notification. The application may send a message to the operating system at the application layer using an OS application programming interface (API) to trigger one or more types of OS-level notifications. For example, the OS-level notifications may be provided as overlay notifications on user interfaces provided by other applications in the foreground layer or the operating system itself (e.g., lock screen, call screen, home screen, or other graphical user interface provided by the operating system). The first level notification may inform the user of the disconnection, prompting the user to take corrective actions, such as repositioning devices or checking wireless communication settings. Simultaneously or subsequently, the central medical monitoring device may attempt to restore the connection by, for example, increasing transmission power or switching communication channels.

[0057] As the connection loss is associated with a communication link with a peripheral medical monitoring device, the level of priority or visibility associated with the status of the connection loss may be updated as the connection lost persists to increase the likelihood of obtaining the user’s attention for addressing the connection loss for monitoring and / or treating the medical condition of the user. The level of the connection loss notification may be increased by the central medical monitoring device providing an operating system (OS)-level notification from an application level notification or an increased OS-level notification. The application may send a message to the operating system at the application layer using an OS application programming interface (API) to trigger one or more types of OS-level notifications. The OS-level notifications may be provided via the operating system on the central medical monitoring device and even be provided while the application that is used to monitor the medical condition is operating in the background layer of the central medical monitoring device. For example, the OS-level notifications may be provided as overlay notifications on user interfaces provided by other applications in the foreground layer or the operating system itself (e.g., lock screen, call screen,Matter No. P39494-WO home screen, or other graphical user interface provided by the operating system). The OS-level notifications may be displayed when the 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) is operating in the background and / or terminated. Different levels of priority may be associated with different OS- level notifications. For example, a lower priority OS-level notification may fail to override a do not disturb mode of the central medical monitoring device, while a higher priority OS-level notification may override the do not disturb mode (e.g., triggering audible notifications).

[0058] The increased level of the connection loss notification may come with other sensory notifications, such as audible and / or haptic notifications. In this case, the connection loss may be considered prolonged, triggering higher-priority and / or higher-visibility notifications to increase the likelihood that the user is aware of the persistent loss of connection. The increased level of connection loss notification may cause the central medical monitoring device to send a message to another external computing device, such as another mobile computing device, a desktop computing device, a wearable computing device, or a remote display device, which may indicate the disconnection between the analyte monitoring device and the central medical monitoring device.

[0059] The central medical monitoring device may reset the connection loss timer to manage the notification escalation process. During this period, the central medical monitoring device may attempt automatic reconnection strategies (e.g., increasing transmission power, switching communication channels, etc.). If the connection is re-established at 215, the central medical monitoring device may continue monitoring the connection status at 204 for a connection loss, ensuring that users are alerted for connection loss that persist beyond transient disconnections. The central medical monitoring device may also log the connection loss in memory for future reference or analysis, helping to identify recurring issues or patterns.

[0060] If the central medical monitoring device remains disconnected from the peripheral medical monitoring device beyond one or more additional periods of the expiration timer , the central medical monitoring device may continue to escalate the level of the connection loss notifications to increase the likelihood that the user is aware of the persistent connection loss. For example, the central medical monitoring device may issue additional OS-level notifications to for display on the central medical monitoring device. These OS-level notifications mayMatter No. P39494-WO remain statically displayed on the central medical monitoring device (e.g., on a lock screen or home screen). These additional notifications could include repeated OS-level notifications and / or persistent in-application messages, to increase the likelihood that the user remains repeatedly informed of the connection loss. The central medical monitoring device may also provide detailed troubleshooting instructions and / or offer a direct link to support resources.

[0061] The central medical monitoring device may manage the lifecycle of these notifications, ensuring they are visible even when the app is not actively in use, enhancing user awareness and prompting corrective action. The OS-level notification may include actionable items, such as, for example, buttons to retry the connection or links to troubleshooting guides. The number and / or level of other sensory level notifications (e.g., audible and / or haptic notifications) may be increased with each level of connection loss notification. The central medical monitoring device may increase the level of the connection loss notifications by prompting the user to manually intervene or by suggesting alternative troubleshooting steps. The central medical monitoring device may escalate the level of the communication notifications by taking further actions to ensure the user is aware of the continued disconnection by requesting user input and prompting the user to perform corrective measures. The central medical monitoring device may escalate the level of the communication notifications by communicating a message to another device, such as another mobile device having a number and / or identifier predefined in memory, the peripheral medical monitoring device itself, and / or a remote computing device. The messages communicated to other devices may cause visual, audible, and / or haptic notifications at another device for alerting the user or other individuals as to the prolonged connection loss.

[0062] If the connection is determined to be re-established at 215, the connection status may be updated, and the notification(s) may be cleared. The user interface of the central medical monitoring device may also be updated to reflect the restored connection, and the central medical monitoring device may resume monitoring the connection status at 204. In an example, the connection status may be updated, and any pending notifications may be cleared from a display of the central medical monitoring device. The central medical monitoring device may update its user interface to reflect the restored connection, resume normal data monitoring activities, and reset relevant timers (e.g., connection loss timer) to ensure ongoing monitoring and data integrity.Matter No. P39494-WO

[0063] After the level of connection loss notifications reaches a predefined level, the central medical monitoring device may initiate further diagnostic protocols to understand the cause of the persistent disconnection. This may involve, for example, an analysis of signal strength, environmental factors, battery levels, and / or potential interference. The central medical monitoring device may log these diagnostic details to provide information to aid in resolving the connection issue. Depending on the severity (e.g., signal below a threshold signal strength) and / or duration (e.g., after a predefined period of time) of the disconnection, the central medical monitoring device may suggest alternative actions to the user, such as manually resetting the peripheral medical monitoring device, switching to a different communication channel, and / or replacing the peripheral medical monitoring device if the peripheral medical monitoring device is suspected to be faulty.

[0064] In some examples, the central medical monitoring device may continue to log information related to the connection loss and / or diagnostics performed, such as the time period for which disconnection persists, a number of events or attempts to reconnect, diagnostic procedures performed to resolve the connection loss, and / or other information to maintain a record of information that can be accessed by the user and / or shared. The central medical monitoring device may also prepare for potential manual intervention by the user, such as pairing with a another peripheral medical monitoring device, performing a reset of the central medical monitoring device and / or the peripheral medical monitoring device, and / or initiating a reset of the communication parameters used to establish the communication session between the central medical monitoring device and the peripheral medical monitoring device. If none of these actions result in a re-established connection, the central medical monitoring device may prompting the user to manually intervene by following specific troubleshooting steps provided by the central medical monitoring device and / or establishing a connection with another peripheral medical monitoring device.

[0065] Referring again to step 224 of FIG. 2, the central medical monitoring device may also, or alternatively, monitor for the regular reception (e.g., every 5-8 minutes) of data packets (e.g, including analyte values or other sensor measurement values) from the peripheral medical monitoring device while the peripheral medical monitoring device maintains a connection to the central medical monitoring device. The central medical monitoring device may identify the integrity and timing of these packets by verifying checksum values and timestamp alignments.Matter No. P39494-WOIn an example, the peripheral medical monitoring device may be configured to transmit data packets at regular intervals (e.g., five minute intervals) and the central medical monitoring device may configure a timer (e.g., an application termination timer) configured to trigger a notification if data fails to be received at the regular intervals or at least a predefined period of time after the interval has ended (e.g., an eight minute period of time). The received data may be processed by the central medical monitoring device to extract relevant health-related measurements (e.g., analyte levels, including glucose levels), and the user interface may be updated to reflect the latest health-related measurements for assisting the user in monitoring and treating their medical condition. Each received data packet may reset a timer to ensure continuous monitoring and avoid unnecessary alerts. The central medical monitoring device may also analyze trends in the data to provide insights or warnings about the status of the user’s medical condition.

[0066] At 227, upon receiving the data from the peripheral medical monitoring device at 224, the central medical monitoring device may log the data 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). If the central medical monitoring device received the data at 224 and / or the application logged the data at 227, the central medical monitoring device may initiate an application termination timer at 226 to track the interval of time since the last successful data reception. The application termination timer may be configured for a period of time (e.g., eight minutes) to trigger a notification if data fails to be received within the period of time to reset the application termination timer. For example, the application may send a message to the operating system that is configured to trigger the notification in the absence of another message from the application configured to restart the application termination timer prior to the expiration (e.g., as the application may be closed and unable to send the message).

[0067] If a connection loss is detected at 206a, while the application termination timer is initiated, the central medical monitoring device may provide connection loss notifications, as described herein, and end the application termination timer at 229. The application termination timer may prevent the central medical monitoring device from overutilizing resources, but provide notification within a period of time to assist with data retention and / or logging of the data.Matter No. P39494-WO

[0068] The central medical monitoring device (e.g, and / or an application thereon) may initiate or restart an application termination timer in response to receipt of another data message at 228 prior to the expiration of the application termination timer. For example, the application may send a message to the operating system to restart the application termination timer. The application termination timer may be configured to trigger a notification upon expiration without receiving another data message prior to the expiration of the application termination timer at 230. Based on an expiration of the application termination timer at 228, the central medical monitoring device may provide an application termination notification at 230. The application termination notification may include a notification to execute the application (e.g, in a foreground layer of the central medical monitoring device) for enabling logging of data in the first data message. The application termination timer may be set to a predefined period of time (e.g., 8 minutes) to manage the notification process for notifying the user to open the application and / or bring the application to the foreground layer while the connection is maintained and to enable data that is being received from the peripheral medical monitoring device to be logged in the application. The predefined period of time to which the application termination timer is set may be the same as or less than the period of time defined for the connection loss timer. For example, the application termination timer may be set to a predefined period of time after an expected data transmission (e.g., comprising analyte values) from the peripheral medical monitoring device (e.g., 5 minute intervals may be expected for reporting analyte values or other sensor measurement values). The application termination timer may be set to a period to allow for the application to be opened / executed in the foreground (or background) for receiving and logging the data after receipt of the data messages, but to notify the user prior to a predefined number (e.g., two or more) of data messages have been received at the central medical monitoring device without being logged in the application.

[0069] The application termination notification provided at 230 may alert the user to open / execute the application in the foreground (or background) to allow for data collection / logging at the application. Without the application being able to log the received data, the user may be unable to view or send that data for appropriately monitoring and / or treating their medical condition. The application termination notification may also provide information to the user to prevent future closures / terminations of the application, such as adjusting power settings and / or reminding the user to keep the application opened / executed in the foregroundMatter No. P39494-WO layer. In response to the information, the central medical monitoring device may update power settings to allow for the application to remain executing in the foreground layer.

[0070] At 230, the central medical monitoring device may provide the application termination notification as an OS-level notification provided through the operating system operating on the central medical monitoring device. The OS-level notification may be provided, as the application may be determined to be closed / terminated. The OS-level notifications may be provided as overlay notifications on user interfaces provided by other applications in the foreground layer or the operating system itself (e.g., lock screen, call screen, home screen, or other graphical user interface provided by the operating system). The OS-level notifications may be visual notifications, audible notifications, and / or haptic notifications.

[0071] The central medical monitoring device may manage the interplay between the connection loss timer tracking connection loss and the application termination timer to optimize the notification strategy. If a connection loss occurs at 206a before the expiration of the application termination timer is detected at 228 (e.g, within 5 minutes), the central medical monitoring device may pause the application termination timer, prioritizing the restoration of the communication with the peripheral medical monitoring device. Upon re-establishing the connection with the peripheral medical monitoring device, both timers may reset, ensuring the timers do not conflict or trigger redundant notifications. This coordination may assist with efficient and effective alert management, minimizing user disruption while maintaining data continuity. In another example, upon re-establishing the connection with the peripheral medical monitoring device, the application termination timer may be started from its time at which the connection loss was detected. The central medical monitoring device may log these events to refine future timer settings and / or improve system reliability.

[0072] The central medical monitoring device may determine whether timer adjustments are appropriate based on contextual factors, such as, for example, the user’s medical state (e.g., diabetic state) based on one or more analyte values or the device’s power management characteristics. The central medical monitoring device may adjust particular periods of time of the application termination timer and / or the connection loss timer in response to certain events. For example, if the central medical monitoring device receives one or more analyte levels from the peripheral medical monitoring device and determines that the user is in an extreme diabetic state (e.g, hypoglycemic or hyperglycemic states), the central medical monitoring device mayMatter No. P39494-WO reduce the period of time of the application termination timer and / or the connection loss timer by a predefined period of time to ensure quicker alerts, thereby enhancing user safety. The longer periods of time of the application termination timer and / or the connection loss timer may be implemented when the user is determined to be in a normal or safe condition and to preserve the batter life and / or processing resources at the central medical monitoring device.

[0073] The central medical monitoring device may adjust notification behaviors to optimize battery and / or processing resources without compromising timely alerts, ensuring a responsive and user-centered experience while preserving on-device resources. For example, the use of different levels of notifications may alert the user while preserving battery and / or processing resources at the central medical monitoring device. Adjustments to the application termination timer and / or the connection loss timer may be performed in response to user input and / or automatically adjusted based on a determination that such adjustments are appropriate based on the contextual factors (e.g., the analyte values and / or medical condition of the user, time of day, device or application settings, etc ). In one example, the central medical monitoring device may detect a user input to turn off a communication circuit or enter a mode (e.g., airplane mode) on the central medical monitoring device, and the application termination timer and / or the connection loss timer may be prevented from being initiated or an option provided to the user to turn off alerts to prevent use of battery and / or processing resources. In another example, the user may provide input indicating the periods of time for the application termination timer and / or the connection loss timer in settings of the application.

[0074] As described herein, the 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) may operate on the central medical monitoring device to log data received in data messages from the peripheral medical monitoring device when the central medical monitoring device and the peripheral medical monitoring device are connected during a wireless communication session and the application is open / executing in the foreground for being able to detect the data messages. Certain data may be used to trigger additional notifications related to the peripheral medical monitoring device and / or the medical condition of the user. For example, the central medical monitoring device may receive data messages that include data indicating a error, maintenance, warning, or reminder (EMWR) events from the peripheral medical monitoring device. The data indicating an EMWRMatter No. P39494-WO event may include an indication of a faulty sensor reading at the peripheral medical monitoring device, a low battery or other power indication, an analyte value or values sensed above or below a defined threshold, an analyte value measurement, a sensor malfunction, a notification of calibration (e.g., analyte level calibration for calibrating the sensor device), temperature indications, calibration failure indications, indications of extreme medical conditions (e.g., hypoglycemic or hyperglycemic conditions), a reminder of a previously reported event, etc. EMWR events may be included in data messages with other information related to the EMWR event, which may be logged in the application by being stored in a log for access by the user and / or being communicated from the central communication monitoring device. EMWR events may be received and / or analyzed to determine whether to trigger a notification to the user at the central medical monitoring device. EMWR events may be transmitted and / or received with a timestamp that may be logged by the application. EMWR events identified by the application within a period of time (e.g., five minutes, ten minutes, or another period of time) may be analyzed to trigger a notification by the application. EMWR events identified by the application within the predefined period of time may be considered active and may trigger a notification at the central medical monitoring device. EMWR events identified by the application outside of the period of time may be logged, but may not trigger notifications because they no longer be active or may be considered stale events.

[0075] The EMWR events received in data messages from the peripheral medical monitoring device may include Record Application Control Point (RACP) commands or requests. An RACP may include a specific command or request sent by the peripheral medical monitoring device that may require immediate processing, such as retrieving stored data or synchronizing time stamps between devices. For example, RACP commands may be sent from a peripheral medical monitoring device after one or more (e.g, a series) of analyte values have been measured at the peripheral medical monitoring device above or below a threshold (e.g., indicating an extreme medical condition, such as an extreme diabetic condition, or that the analyte levels of the user are trending in a direction of the extreme medical condition). Upon a determination that an RACP command or request is detected after the period of time (e.g., five minutes, ten minutes, or another period of time) by the application (e.g., due to a loss of connection and / or the application being closed / terminated), the application may be unable orMatter No. P39494-WO configured to prevent the notification in response to the RACP command or request. However, the EMWR event may be logged in one or more locations by the application.

[0076] EMWR events received from a peripheral medical monitoring device may be logged by the application executing at the central medical monitoring device in one or more locations and / or in one or more formats. For example, the EMWR events may be logged in a Fast Healthcare Interoperability Resources (FHIR) log that is formatted according to FHIR standards. The FHIR logging process may include data such as patient health metrics, device-generated alerts, and / or sensor readings, which may be structured to facilitate seamless integration with electronic health records (EHRs) and other healthcare information systems. By adhering to FHIR standards, the improved patient care may be implemented by enabling healthcare providers to access comprehensive data that aids in diagnosis, treatment planning, and / or monitoring. Furthermore, FHIR logging may play an important role in ensuring that the overall system complies with healthcare regulations, such as HIPAA, by maintaining a secure and standardized approach to data handling and exchange. The EMWR events may also, or alternatively, be logged in an event log of the application that stores EMWR events received from the peripheral medical monitoring device and / or events that occur on the central medical monitoring device itself. Certain EMWR events may be prevented from being logged each time they are received to prevent the logs from filling up and / or occupying storage with repeat events. Each occurrence may still be logged to at least one of the logs (e.g., FHIR) even if it is not stored in the other. For example, the EMWR events may need to be logged in the FHIR log to comply with the standards, but may be prevented from being stored in another event log. One example of an EMWR event that may need to be logged int the FHIR log each time it is received and that may be logged once in another event log when received multiple times within a period of time may include a calibration recommended EMWR event. The calibration recommended EMWR event may refer to a grace period of time for calibrating the peripheral medical monitoring device with an analyte value that may be used to calibrate one or more sensors for measuring the analyte value. For example, if the analyte value is a blood glucose value for calibrating a blood glucose monitoring device, and no value is input within a predefined grace period for calibrating the blood glucose monitoring device, the blood glucose monitoring device may transition to a state that may send the calibration recommended EMWR event to receive a calibration value for calibrating the peripheral medical monitoring device. The calibration value may be input intoMatter No. P39494-WO the central medical monitoring device (e.g., in response to a user pricking their finger and using another blood glucose monitoring device to read a test strip).

[0077] FIG. 3 shows a flowchart of an example process 300 for receiving EMWR events and providing notifications and / or logging the events. One or more portions of the process 300 may be performed by one or more computing devices. For example, one or more portions of the process 300 may be performed by one or more central medical monitoring devices, such as mobile device 104 shown in FIGs. 1A and IB, and / or one or more remote computing devices, such as remote computing device 122 shown in FIGs. 1A and IB. 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, peripheral medical monitoring devices, and / or one or more other devices.

[0078] As shown in FIG. 3, at 302 and 308, the central medical monitoring device may receive EMWR events in data messages from the peripheral medical monitoring device when the devices are connected during a wireless communication session. As described herein, the calibration recommended EMWR events received at 302 may be processed and / or logged differently than other EMWR events 308. At 304, the calibration recommended EMWR events may be analyzed to determine whether the calibration recommended value is the same as the previously received calibration recommended value. The analysis at 304 may be performed to prevent continuously logging the same calibration recommendation value in the event log 320 (e. , preserving space in the event log 320). Upon a determination that the calibration recommended EMWR event does not comprise the same value as the recent value that was previously received from the peripheral medical monitoring device, the central medical monitoring device may activate a notification at 314 and the EMWR event may be logged at 316. The log at 316 may cause an entry to be logged to the event log 320 and the FHIR log 318. Upon a determination that the calibration recommended EMWR event does comprise the same value as the most recent value received from the peripheral medical monitoring device, a determination may be made as to whether the session has ended at 306. If the session has ended at 306, the central medical monitoring device may activate a notification at 314 and log the EMWR event at 316. If theMatter No. P39494-WO session has not ended at 306, the central medical monitoring device may log the EMWR event at 316. The calibration recommended EMWR events may be logged in the event log at 320 a single time within a period of time or when there is no change of the calibration recommended EMWR event. The calibration recommended EMWR events may be logged in the FHIR log at 318 each time. Though the calibration recommended EMWR event is a type of EMWR event that is described as being prevented from being stored in the event log 320 when the value is the same as a previously received value, other EMWRs may be treated similarly.

[0079] The other EMWR events received at 308 may be processed and / or logged differently than the calibration recommended EMWR evens 302. At 310, the central medical monitoring device may determine whether the EMWR event is stale (e.g., received and / or transmitted longer than a predefined period of time) and / or comprises an RACP request or command. Upon a determination that the EMWR event is not stale and / or does not comprise an RACP request or command, the central medical monitoring device may activate a notification at 314 and the EMWR event may be logged at 316. Upon a determination that the EMWR event is stale and / or does comprise an RACP request or command, a determination may be made as to whether the session has ended at 312. If the session has ended at 312, the central medical monitoring device may activate a notification at 314 and log the EMWR event at 316. If the session has not ended at 312, the central medical monitoring device may log the EMWR event at 316. The EMWR events may be logged in the event log at 320 and / or the FHIR log.

[0080] FIGs. 4A-4C depict illustrations of GUIs displaying example overlay notifications on a display 404 of a computing device 400 (e.g., central medical monitoring device, such as a mobile device). The GUIs may be generated by software executing on the computing device 400.

[0081] FIG. 4A illustrates a graphical user interface (GUI) 406 displayed on the display 404 of a central medical monitoring 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 or a user interface of an operating system, such as 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 connection loss notification, as described herein. For example, the information provided on the overlay notification 408 may include an indication 410 that the central medical monitoring device 400Matter No. P39494-WO has detected a connection loss from a peripheral medical monitoring device and / or for at least a period of time. The overlay notification 408 may be provided after a predefined maximum period of time has elapsed from the time of the connection loss or immediately upon detecting the connection loss. The indication 410 may provide information such as a message (e.g., "Sensor Connection Lost," "Device Not Found," "Signal Lost") or informing the user of the detected communication issue. This message may be accompanied by an icon or symbol indicating the severity of the issue, such as a warning triangle or red exclamation mark. The device may also provide the user with additional context, such as the duration of the disconnection or suggestions for corrective actions (e.g., "Move closer to the device," "Check BLUETOOTH settings").

[0082] In response to the central medical monitoring device 400 successfully re-establishing the connection with the peripheral monitoring device within a predefined time frame (e.g., 10 minutes), the overlay notification 408 may be automatically cleared, and normal operations may resume without further user intervention. In some examples, the device may display a brief message confirming the restored connection (e.g., "Connection Restored"), reassuring the user that the system is functioning correctly. However, if the connection loss persists beyond the specified time frame, the central medical monitoring device 400 may escalate the notification by issuing a higher-priority and / or visibility notification, as described herein. For example, the central medical monitoring device 400 may initially display the overlay notification 408 in an application and then display a similar overlay notification and / or information as an OS-level notification, which may appear prominently on the lock screen, home screen, call screen, or another graphical user interface of the operating system or another application. The central medical monitoring device 400 may generate an audible or haptic notification with increased levels of priority or visibility. This escalation may be governed by a communication loss timer, which tracks the duration of the disconnection and determines when to elevate the notification. The communication loss timer may reset upon re-establishing the connection, thus preventing unnecessary alerts and minimizing user disruption.

[0083] 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 central medical monitoring device 400 and the peripheral medical monitoring device.Matter No. P39494-WO

[0084] FIG. 4B provides a detailed view of the graphical user interface (GUI) 406 displayed on the display 404 of the central medical monitoring device 400 when the user interacts with the application after receiving a notification. The overlay notification 408a may be displayed over a medical application displaying information related to the glucose level of the user. A glucose level chart 412 may be prominently displayed on the GUI 406, which may graphically represent the user's glucose levels over time. The chart 412 may include time markers 414 to indicate specific intervals (e.g., every 5 minutes), glucose level indicators 416 to show thresholds for extreme conditions (e.g., 70 mg / dL for hypoglycemia, 180 mg / dL for hyperglycemia), and / or a graph line 418 depicting the glucose measurements received from the peripheral medical monitoring device. This chart 412 may enable the user to visualize trends in their glucose levels, assisting them in understanding how their glucose levels have changed over time and identifying any periods where data was not received due to a communication issue.

[0085] The expanded overlay notification 408a on the display 404 may provide additional details and actionable instructions for the user. For example, the notification may display a message (e.g., "Sensor Connection Lost. Attempting Reconnection," "Connection Failed. Retry in Progress"), informing the user of the ongoing efforts to restore the connection between the peripheral medical monitoring device and the central medical monitoring device 400. In response to this notification, the user may be prompted to take corrective actions, such as "Enable BLUETOOTH," "Ensure Devices are Within Range," or "Restart the App," by interacting with a link or button within the overlay notification 408a, such as "Re-establish Connection" link 410, the selection of such may perform a corresponding action at the central medical monitoring device. In some cases, the central medical monitoring device may automatically retry the connection process at regular intervals (e.g., every 2 minutes) until the connection is successfully restored, and the notification 408a may inform the user of such remedial action.

[0086] Additionally, or alternatively, upon the central medical monitoring device 400 detecting that the peripheral medical monitoring device has stopped transmitting data (e.g., due to a critical issue, such as sensor failure or battery depletion), the GUI 406 may present contextual alerts to inform the user of potential health risks associated with the disconnection. For instance, the overly notification 408a may include messages 420 informing the user that the data from the peripheral medical monitoring device is unavailable and the user may want to use another method for monitoring their medical condition (e.g., "Sensor Data Unavailable: Check DeviceMatter No. P39494-WOStatus"). The overlay notification 408a may provide a warning that the analyte levels may be approaching levels of a critical medical condition (e.g., "Your glucose level may be approaching a critical threshold"). These messages may help the user assess the urgency of the situation and take appropriate action to maintain their health and safety. The central medical monitoring device 400 may also log these events in an event history, allowing the user to review past notifications and trends to better understand the device's performance and any recurring issues. The central medical monitoring device 400 may manage these notifications by coordinating data collection and processing between the application and communication functionalities to ensure the user is kept informed of critical events and can respond promptly to any issues that arise.

[0087] Figure 4C includes an example of a GUI 406, which may display current notifications, past notifications, and / or a comprehensive view of active and past notifications within the display screen 404 on the central medical monitoring device 400. This display screen 404 may act as a centralized notification center, providing the user with an overview of each of the events detected and deemed by the system to be sufficiently important for a notification to be issued. The display screen 406 may presented identified notifications, and / or may categorize these notifications based on their a determined relative importance, origin (e.g., communication issues, application issues) or criticality, ensuring that the user can easily identify and respond to the notification in an order of importance relative to other alerts (e.g., higher priority notifications may be listed at a top of a notification list, send a visual or audio alert of the higher priority notification, etc.)

[0088] Figure 4C illustrates a detailed view of the graphical user interface (GUI) 406 displayed on the screen 404 of the central medical monitoring device 400, which may include an overlay notification 408b on the display 404. The overlay notification 408b may include one or more messages 424, 426, which may include additional details, actionable instructions for the user, and / or a notification that the connection has been restored between the peripheral medical monitoring device and the central medical monitoring device 400. For example, the notification may display a reconnection indication message 424 indicating a re-establishment of connection with the peripheral medical monitoring device (e.g., “Peripheral Medical Monitoring Device Reconnected”).

[0089] In some examples, the overlay notification 408b may act as a centralized notification center, providing the user with one or more messages 426 which can include a prioritized list ofMatter No. P39494-WO critical events detected by the system. These notification messages 410 may be categorized based on their origin (e.g., communication issues, application issues) and / or criticality (e.g., “Sensor Connection Lost”, “App Termination Timer Expired”, “Connection Loss Exceeds Threshold Time”), and can be organized in a prioritized list presented to the user, ensuring that the user can easily identify and respond to the most important alerts in a timely manner.

[0090] As shown in FIG. 4C, the central medical monitoring device 400 may provide in the overlay notifications the application termination notification 426a upon an expiration of the application termination timer. As described herein, the application termination notification 426a may be provided as an OS -level notification.

[0091] In some examples, the prioritized messages 426 displayed on the overlay notification 408b of the GUI 406 may include alerts related to communication issues, such as "Sensor Connection Lost," and / or alerts related to application termination, such as "App Termination Timer Expired."

[0092] In an example, the overlay notification 408b may display a message 426b indicating a period of time for which connection has been lost e.g., "Prolonged Connection Loss: No data received for 10 minutes") and / or an application has been terminated. The device may provide suggestions for corrective or remedial actions, such as "Move closer to the device," "Check Sensor Battery Level," "Restart Peripheral Device," or “Activate Application.” In another instance, the app may display a notification such as "Sensor Stopped Working" or "Device Offline," informing the user that the peripheral medical monitoring device is no longer transmitting data and may provide instructions for resolving the issue, such as "Replace Sensor" or "Check Device Settings."

[0093] FIG. 5 is a block diagram of an example computing device 500. The computing device 500 may be a central medical monitoring device, such as a mobile computing device, including 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 performMatter No. P39494-WO 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.

[0094] 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 nonremovable 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.

[0095] 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.

[0096] 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.

[0097] 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.Matter No. P39494-WO

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.Matter No. P39494-WO

[0102] 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.

[0103] 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.

[0104] The computing device 500 may include a visual indicator, such as one or more lightemitting 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).

[0105] FIG. 6 is a block diagram of an example continuous monitoring device 600, which may operate as a peripheral medical monitoring device. 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.

[0106] 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.

[0107] The transmitting device 604 may include another communication circuit 616 for communicating with other devices. The processor 602 may be in electrical communication withMatter No. P39494-WO 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.

[0108] 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 nonremovable 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.

[0109] 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.

[0110] 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.[0U1] FIG. 7 is a block diagram of an example blood glucose meter (BGM) device 700, which may operate as a peripheral medical monitoring device. As shown in FIG. 7, the BGM device 700 may include a processor 702 for controlling the functionality of the BGM device 700. TheMatter No. P39494-WO 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.

[0112] 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 nonremovable 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.

[0113] 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®, WLMAX®, 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.

[0114] 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.

[0115] 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 bloodMatter No. P39494-WO samples provided by a patient on a blood glucose measurement strip and measure the amount of blood glucose in the samples.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] The BGM device 700 may include a visual indicator, such as one or more one or more light-emitting 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).

[0121] 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.

[0122] 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.Matter No. P39494-WOExamples 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

Matter No. P39494-WOCLAIMSWhat is claimed is:

1. A method comprising: detecting an established communication session between a central medical monitoring device and a peripheral medical monitoring device; during the establishment of the communication session, receiving a first data message at the central medical monitoring device; in response to the receipt of the first data message, initiating an application termination timer; based on an expiration of the application termination timer, providing an application termination notification via the central medical monitoring device, wherein the application termination notification comprises a notification to execute the application on the central medical monitoring device for enabling logging of data in the first data message; detecting a connection loss between the central medical monitoring device and the peripheral medical monitoring device; initiating, in response to the connection loss, a connection loss timer at the central medical monitoring device; based on an expiration of the connection loss timer, providing a connection loss notification; detecting a re-establishment of the communication session with the peripheral medical monitoring device; and receiving a second data message.

2. The method of claim 1, wherein the connection loss notification is provided as a visual overlay notification in the application associated with the peripheral medical monitoring device via a graphical user interface (GUI) at the central medical monitoring device to indicate the connection loss.

3. The method of claim 1, wherein the expiration of the connection loss timer comprises a first expiration of the connection loss timer, wherein the connection loss notification comprises aMatter No. P39494-WO first connection loss notification associated with at least one of a first priority or first visibility level, the method further comprising: based on at least one second expiration of the connection loss timer, providing at least one second connection loss notification associated with at least one of a higher priority or higher visibility level than the first priority or the first visibility level.

4. The method of claim 3, wherein the at least one second connection loss notification comprises a visual operating system (OS)-level notification via a graphical user interface (GUI) of the central medical monitoring device.

5. The method of claim 4, wherein the at least one second notification comprises at least one of an audible notification or haptic feedback to escalate the priority or visibility level of the at least one second notification to increase a likelihood that the at least one second notification is received by a user.

6. The method of claim 1, wherein the peripheral medical monitoring device comprises a glucose monitoring device, and dynamically adjusting the connection loss timer based on a diabetic state indicated by one or more messages received from the glucose monitoring device.

7. The method of claim 1, wherein the peripheral medical monitoring device comprises a continuous glucose monitor.

8. The method of claim 7, wherein the application termination timer is initiated to a predefined period of time that is less than a period of time in which a plurality of messages is configured to be received from the continuous glucose monitor.

9. An apparatus comprising: a transceiver; and a processor configured to: detect an established communication session via the transceiver with a peripheral medical monitoring device;Matter No. P39494-WO during the establishment of the communication session, receive a first data message via the transceiver; in response to the receipt of the first data message, initiate an application termination timer; based on an expiration of the application termination timer, provide an application termination notification, wherein the application termination notification comprises a notification to execute the application for enabling logging of data in the first data message; detect a connection loss with the peripheral medical monitoring device; initiate, in response to the connection loss, a connection loss timer; based on an expiration of the connection loss timer, provide a connection loss notification; detect a re-establishment of the communication session with the peripheral medical monitoring device; and receive a second data message.

10. The apparatus of claim 9, wherein the processor is configured to provide the connection loss notification as a visual overlay notification in the application associated with the peripheral medical monitoring device via a graphical user interface (GUI) to indicate the connection loss.

11. The apparatus of claim 9, wherein the expiration of the connection loss timer comprises a first expiration of the connection loss timer, wherein the connection loss notification comprises a first connection loss notification associated with at least one of a first priority or first visibility level, the processor being further configured to: based on at least one second expiration of the connection loss timer, provide at least one second connection loss notification associated with at least one of a higher priority or higher visibility level than the first priority or the first visibility level.Matter No. P39494-WO12. The apparatus of claim 11 , wherein the processor is configured to provide the at least one second connection loss notification as a visual operating system (OS)-level notification via a graphical user interface (GUI).

13. The apparatus of claim 11, wherein the at least one second notification comprises at least one of an audible notification or haptic feedback to escalate the priority or visibility level of the at least one second notification to increase a likelihood that the at least one second notification is received by a user.

14. The apparatus of claim 9, wherein the peripheral medical monitoring device comprises a glucose monitoring device, and wherein the processor is configured to dynamically adjust the connection loss timer based on a diabetic state indicated by one or more messages received from the glucose monitoring device.

15. The apparatus of claim 9, wherein the peripheral medical monitoring device comprises a continuous glucose monitor.

16. The apparatus of claim 15, wherein the processor is configured to initiate the application termination timer to a predefined period of time that is less than a period of time in which a plurality of messages are configured to be received from the continuous glucose monitor.

17. At least one computer-readable storage medium having computer-executable instructions stored thereon that are configured to, when executed by at least one processor, cause the at least one processor to: detect an established communication session between a central medical monitoring device and a peripheral medical monitoring device; during the establishment of the communication session, receive a first data message; in response to the receipt of the first data message, initiate an application termination timer; based on an expiration of the application termination timer, provide an application termination notification, wherein the application termination notification comprises a notificationMatter No. P39494-WO to execute the application in a foreground layer for enabling logging of data in the first data message; detect a connection loss between the central medical monitoring device and the peripheral medical monitoring device; initiate, in response to the connection loss, a connection loss timer; based on a first expiration of the connection loss timer, provide a first connection loss notification associated with at least one of a first priority or first visibility level; based on at least one second expiration of the connection loss timer, provide at least one second connection loss notification associated with at least one of a higher priority or higher visibility level than the first priority or the first visibility level; detect a re-establishment of the communication session with the peripheral medical monitoring device; and receive, via the transceiver, a second data message.

18. The at least one computer-readable storage medium of claim 17, wherein the instructions are configured to cause the processor to provide the connection loss notification as a visual overlay notification in the application associated with the peripheral medical monitoring device via a graphical user interface (GUI) to indicate the connection loss.

19. The at least one computer-readable storage medium of claim 17, wherein the expiration of the connection loss timer comprises a first expiration of the connection loss timer, wherein the connection loss notification comprises a first connection loss notification associated with at least one of a first priority or first visibility level, the instructions being further configured to cause the processor to: based on at least one second expiration of the connection loss timer, provide at least one second connection loss notification associated with at least one of a higher priority or higher visibility level than the first priority or the first visibility level.

20. The at least one computer-readable storage medium of claim 19, wherein the instructions are configured to cause the processor to provide the at least one second connection lossMatter No. P39494-WO notification as a visual operating system (OS)-level notification via a graphical user interface (GUI).

21. The at least one computer-readable storage medium of claim 19, wherein the at least one second notification comprises at least one of an audible notification or haptic feedback to escalate the priority or visibility level of the at least one second notification to increase a likelihood that the at least one second notification is received by a user.

22. The at least one computer-readable storage medium of claim 17, wherein the peripheral medical monitoring device comprises a glucose monitoring device, and wherein the instructions are configured to cause the processor to dynamically adjust the connection loss timer based on a diabetic state indicated by one or more messages received from the glucose monitoring device.

23. The at least one computer-readable storage medium of claim 17, wherein the peripheral medical monitoring device comprises a continuous glucose monitor.

24. The at least one computer-readable storage medium of claim 23, wherein the instructions are configured to cause the processor to initiate the application termination timer to a predefined period of time that is less than a period of time in which a plurality of messages are configured to be received from the continuous glucose monitor.

Images