[go: up one dir, main page]

WO2025201696A1 - Réduction de notification pour des déconnexions de communication lors de l'utilisation de dispositifs connectés pour le traitement d'une affection médicale - Google Patents

Réduction de notification pour des déconnexions de communication lors de l'utilisation de dispositifs connectés pour le traitement d'une affection médicale

Info

Publication number
WO2025201696A1
WO2025201696A1 PCT/EP2025/051946 EP2025051946W WO2025201696A1 WO 2025201696 A1 WO2025201696 A1 WO 2025201696A1 EP 2025051946 W EP2025051946 W EP 2025051946W WO 2025201696 A1 WO2025201696 A1 WO 2025201696A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
analyte
monitoring device
time
notification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2025/051946
Other languages
English (en)
Inventor
Felix BOOTZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Roche Diabetes Care GmbH
Original Assignee
Roche Diabetes Care GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Roche Diabetes Care GmbH filed Critical Roche Diabetes Care GmbH
Publication of WO2025201696A1 publication Critical patent/WO2025201696A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/40—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for data related to laboratory analysis, e.g. patient specimen analysis
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/17—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices

Definitions

  • the mobile device may receive information from other monitoring devices.
  • the mobile device may receive current blood glucose levels from a blood glucose monitoring device and/or a continuous glucose monitor. These devices may communicate via a communication medium, such as a wireless RF communication signal. Due to interference, the connection between these devices may not always be maintained.
  • the mobile device may provide alerts to the user when the mobile device is unable to receive health-related information from other monitoring devices, such that the user is aware that their condition may be worsening, and the mobile device is unable to report the current status of their condition. These types of notifications may be provided several times as the mobile device disconnects and reconnects to other monitoring devices.
  • the notifications may cause the user to be concerned about the current state of their medical condition unnecessarily, as the current state of the medical condition may be relatively normal.
  • the frequency of the notifications can also cause user fatigue, which may cause the user to ignore important notifications helpful to the treatment of their medical condition.
  • US 2022/0248988 describes improved digital interfaces, graphical user interfaces, and alarms for analyte monitoring systems.
  • the document discloses methods, systems and interfaces for signal loss condition determination, Time-in-Ranges interfaces, GMI metrics, urgent low glucose alarms, alarm suppression features, alarm setup interfaces, and alarm unavailability detection features. It also describes interfaces for alarm logging and compatibility checking of an analyte monitoring software application. Additionally, it covers interface enhancements like an enhanced visibility mode, a voice accessibility mode, and interfaces relating to user privacy and caregiver alarms.
  • At least one computer-readable storage medium having instructions stored thereon that are configured, when executed by at least one processor, to cause the at least one processor to:
  • analyte monitoring device receives, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a measurement of a blood- analyte level of the user and a rate of change of the analyte level;
  • another method comprising: - receiving, via a communication medium, data from an analyte monitoring device, wherein the data is related to a medical condition of a person, wherein the data comprises a plurality of measurements of an analyte level of a user and a rate of change of the analyte level;
  • an apparatus comprising a processor configured to perform the (another) method is provided.
  • a computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the (another) method.
  • the measurement of the analyte level may be a first measurement.
  • the rate of change may be a first rate of change of the analyte level.
  • the disconnection may be a first disconnection.
  • the predicted period of time may be a first predicted period of time.
  • the notification may be a first notification.
  • the method may comprise at least one of:
  • the disconnection may be between a mobile device and the analyte monitoring device.
  • the threshold may comprise a high-end threshold and/or a low-end threshold related to the analyte level of the user.
  • the method may comprise at least one of:
  • the notification may comprises the visual notification and the visual notification may be provided via a display and/or a light emitting diode (LED).
  • LED light emitting diode
  • the analyte monitoring device may be a continuous glucose monitor.
  • the instructions may be configured to cause the at least one processor to perform at least one of the following:
  • the threshold may comprises a high-end threshold and/or a low-end threshold related to the analyte level of the user.
  • the threshold may be a user defined threshold and/or a predefined threshold related to an extreme diabetic state, wherein preferably the high-end threshold related to the extreme diabetic state may comprise a state of hyperglycemia, and wherein more preferably the low-end threshold related to the extreme diabetic state may comprise a state of hypoglycemia.
  • the instructions may be configured to cause the at least one processor to perform at least one of the following:
  • the rate of change of the analyte level may be a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold.
  • Embodiments are described herein for delaying notifications related to disconnected analyte monitoring devices used to assist in treatment of a medical condition.
  • the user may implement one or more computing devices for enabling them to properly treat their medical condition.
  • the user may implement their mobile device and/or one or more analyte monitoring devices for monitoring information related to their medical condition or other health-related information.
  • the analyte monitoring device may be a glucose monitoring device, such as a continuous glucose monitor, for example.
  • the embodiments described herein may be implemented on one or more computing devices, such as a mobile device of a user.
  • the embodiments may be implemented via computer-executable instructions stored on a computer- readable media.
  • the embodiments described herein may be implemented as methods and/or computer-executable instructions that may be executed by one or more processors via one or more applications executing on one or more computing devices.
  • the user’s mobile device may receive data from an analyte monitoring device when it is connected to the analyte monitoring device via a communication medium.
  • the data may be related to the medical condition of the user.
  • the data may relate to an analyte level of the user.
  • the analyte level may comprise a blood glucose level, a blood potassium level, or another analyte level monitored by the user.
  • the data from the analyte monitoring device may comprise a rate of change of the analyte level.
  • the mobile device may detect a disconnection with the analyte monitoring device via the communication medium.
  • the mobile device may detect that the analyte level of the user is within a threshold range at a time of the disconnection.
  • the mobile device may delay a notification to the user related to the disconnection until a predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device.
  • the mobile device may determine the predicted period of time at which a threshold related to the analyte level will be reached.
  • the predicted period of time may be determined based on the measurement of the analyte level and/or the rate of change of the analyte level.
  • the mobile device may delay the notification to the user related to the disconnection until the predicted period of time has elapsed without detecting a reconnection to the analyte monitoring device.
  • the mobile device may provide a notification to the user indicating the disconnection with the analyte monitoring device.
  • the mobile device may delay the notification of the user related to the disconnection and detect a reconnection to the analyte monitoring device via the communication medium prior to an expiration of the predicted period of time. In response to the reconnection being detected prior to the expiration of the predicted period of time, the mobile device may cancel the notification to prevent the notification from being provided to the user.
  • the notification may comprise a visual notification, an audible notification, or a vibratory or tactile notification.
  • the visual notification may be provided via a display or a light emitting diode (LED).
  • the mobile device may cancel the notification to prevent the notification from being provided to the user.
  • the predicted period of time may be based on the analyte level and/or rate of change of the analyte level of a user at a given instance in time
  • longer predicted periods of time may allow for additional unforeseen factors to affect the analyte level of the user.
  • the notification may be prevented from being delayed for such a long period of time that it may be harmful to the treatment of the medical condition of the user.
  • the mobile device may determine that the predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device.
  • the mobile device may provide the notification to the user indicating the disconnection with the analyte monitoring device if the predefined maximum period of time has elapsed without detecting a reconnection.
  • the measurement of the analyte level may include a first measurement.
  • the rate of change may include a first rate of change of the analyte level.
  • the disconnection may be a first disconnection.
  • the predicted period of time may be a first predicted period of time.
  • the notification may be a first notification.
  • the mobile device may detect a reconnection with the analyte monitoring device and receive, via the communication medium, a second measurement of the analyte level of the user and/or a second rate of change of the analyte level.
  • the mobile device may detect a second disconnection with the analyte monitoring device via the communication medium.
  • the mobile device may determine, based on the second measurement of the analyte level and/or the second rate of change of the analyte level, a second predicted period of time at which the threshold related to the analyte level will be reached.
  • the mobile device may determine that the second predicted period of time is greater than a predefined maximum period of time for delaying notifications related to disconnections with the analyte monitoring device.
  • the mobile device may delay a second notification related to the second disconnection from being provided to the user until the predefined maximum period of time has elapsed without detecting the reconnection to the analyte monitoring device. After the predefined maximum period of time has elapsed without the mobile device detecting the reconnection to the analyte monitoring device via the communication medium, the mobile device may provide the second notification to the user indicating the disconnection with the analyte monitoring device.
  • the mobile device may determine a predicted period of time at which a threshold related to the analyte level will be reached.
  • the threshold may comprise a high-end threshold or a low-end threshold related to the analyte level of the user.
  • the threshold may be a user defined threshold or a predefined threshold related to an extreme diabetic state.
  • the high-end threshold related to the extreme diabetic state may comprise a state of hyperglycemia.
  • the low-end threshold related to the extreme diabetic state may comprise a state of hypoglycemia.
  • the mobile device may receive a user indication to set the threshold to one of the user defined threshold or the predefined threshold related to the extreme diabetic state and determine, based on the user indication, the predicted period of time based on one of the user defined threshold or the predefined threshold related to the extreme diabetic state.
  • the rate of change of the analyte level may include a positive rate of change toward the high-end threshold or a negative rate of change toward the low-end threshold.
  • the delay of the notifications when the analyte level of the user is within a normal or healthy range may prevent the user from needlessly receiving notifications related to the disconnection, which may be helpful in assisting the treatment of the medical condition of the user, and the predefined maximum period of time may prevent the delay from becoming potentially harmful to the user.
  • FIGs. 2A-2C show graphs that illustrate example timeframes in which notifications may be delayed and/or provided to a user after an analyte monitoring device is disconnected from a computing device.
  • FIG. 3 shows a flowchart of an example process for delaying notifications of a disconnection between an analyte monitoring device and another computing device.
  • FIG. 5 is a block diagram of an example computing device.
  • FIG. 6 is a block diagram of an example continuous monitoring device.
  • FIG. 7 is a block diagram of an example blood glucose meter (BGM) device.
  • BGM blood glucose meter
  • FIG. 1A is a perspective view of a representative user environment.
  • a user 100 may be a person with a medical condition.
  • the user 100 may be a person with diabetes, a person with a potassium disorder, or a person with another medical condition.
  • the user 100 may use one or more devices to help monitor and/or treat the medical condition.
  • the user 100 may use one or more devices to help monitor an analyte level and/or treat the medical condition.
  • the medical condition may include a diabetic condition.
  • the diabetic condition may include a metabolic syndrome, pre-diabetes, type 1 diabetes, type 2 diabetes, and/or gestational diabetes.
  • the user 100 may be in an extreme diabetic state, such as hypoglycemia or hyperglycemia, when the blood glucose level of the user 100 is above or below a threshold blood glucose level.
  • the user 100 may use a glucose monitoring device to monitor blood glucose levels.
  • the user 100 uses a blood glucose meter (BGM) 106 as a blood glucose monitoring device to monitor blood glucose levels.
  • BGM blood glucose meter
  • the BGM 106 includes a port 108 that receives a blood glucose measurement strip 110.
  • the user 100 deposits a sample of blood on the blood glucose measurement strip 110.
  • the BGM 106 analyzes the sample and measure the blood glucose level in the sample.
  • the blood glucose level measured from the sample is displayed on a display 112 of the BGM 106 or communicated to an external device, such as the mobile device 104.
  • the mobile device 104 processes the blood glucose data to manage the diabetic condition and provide treatment notifications as described herein.
  • 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.
  • the mobile device 104 communicates with the CGM 102, FGM 111 , the BGM 106, and/or pen device 103 using BLUETOOTH®, near field communication (NFC), THREAD®, WIFI®, ZIGBEE®, WI-MAX®, a cellular communication protocol, a proprietary wireless communication protocol, or another radio frequency (RF) communication protocol.
  • BLUETOOTH® near field communication
  • NFC near field communication
  • THREAD® WIFI®
  • ZIGBEE® ZIGBEE®
  • WI-MAX® wireless local area network
  • a cellular communication protocol a proprietary wireless communication protocol
  • RF radio frequency
  • blood glucose monitoring devices e.g., pen device 103, CGM 102, BGM 106, FGM 111 , and/or another blood glucose monitoring device
  • other analyte monitoring devices may be implemented for measuring and/or monitoring other analyte levels of the user 100.
  • the user 100 may have a potassium condition or disorder, such as hypokalemia (e.g., a potassium deficiency in which a person has blood potassium levels below a predefined threshold) or hyperkalemia (e.g., a condition in which a person has blood potassium levels above a predefined threshold.)
  • the user 100 may use a blood potassium monitoring device to monitor blood potassium levels.
  • the user 100 may deposit a sample of blood in the blood potassium monitoring device, which analyzes the sample and measure the blood potassium level in the sample.
  • the blood potassium level measured from the sample may be communicated to an external device, such as the mobile device 104.
  • the mobile device 104 may process the blood potassium data to manage the condition and provide treatment notifications as described herein. For example, the notifications may alert the user 100 to ingest potassium or diuretics, take medication, perform dialysis, and/or conduct another form of treatment.
  • a user 100 may have a liver condition or disorder and the user 100 may use a blood ketone meter or other monitoring device to monitor blood ketone levels.
  • the blood ketone level measured from the sample may be communicated to an external device, such as the mobile device 104.
  • the mobile device 104 may process the blood ketone data to manage the condition and provide treatment notifications as described herein. Any other devices that are used to monitor any other medical conditions based on analyte levels of the user 100 and/or communications between connected devices may similarly utilize one or more embodiments described herein.
  • connection between devices may be initiated by the transmission and/or receipt of a connection request message from one of the devices via a communication medium.
  • Another device may transmit a connection response message in response to the connection request message via the communication medium.
  • the devices may detect that the connection has been established based on the exchange of the connection request/connection response messages and/or subsequent messages, such as acknowledgement messages, messages for establishing secure communications, or other subsequent messages (e.g., depending on the communication protocol).
  • the mobile device 104 may receive data from other devices and/or input from the user 100 via a user interface for being provided on a display.
  • the mobile device 104 may receive input via hard buttons or soft buttons provided on the display.
  • the mobile device may provide output to the user 100 in the form of visual output on the display, audio output via a speaker, haptic feedback via vibrations, and/or other output to the user.
  • the mobile device 104 may be a connected smart device and/or may be in communication with other connected smart devices.
  • Example connected smart devices may include a wearable device.
  • the connected smart device may be an armband (e.g., a smart watch, such as an APPLE® watch, a FITBIT® armband, or other device capable of being worn on the arm of the user 100), a ring, glasses (e.g., GOOGLE® GLASSTM), a headset (e.g., BLUETOOTH® headset), clothing (e.g., shirts, gloves, etc.), or another wearable device capable of being worn by the user 100.
  • the connected smart device may be a wearable device or other device capable of monitoring the heart rate of the user 100, such as a heart rate monitor.
  • the connected smart device may include a device capable of monitoring a wake/sleep state of the user, such as a wearable device, a heart rate monitor, a smart bed, or another device.
  • the mobile device 104 may be configured to determine information corresponding to the device’s location (/.e., location information). For example, the mobile device 104 may be able to determine the geolocation (e.g., latitude and longitude) of the mobile device 104 using signals from a global positioning system (GPS) or triangulation via cellular communications. The mobile device 104 may communicate with the remote computing device 122 for accessing a third-party service (e.g., via an application programming interface (API)), for example, to determine the location of the mobile device 104 or access other software/applications. In one example, the mobile device 104 may provide data received from one or more devices to the remote computing device 122, via the network 120, for performing one or more processes described herein. The mobile device 104 may receive a response from the remote computing device 122 with information for being displayed to the user and/or for being communicated to other devices.
  • GPS global positioning system
  • API application programming interface
  • Some embodiments of the mobile device 104 include one or more sensors for detecting a relative position of the device or information about the user 100.
  • the mobile device 104 may detect a movement or a change in orientation. Based on the movement or change in orientation (or lack thereof) of the mobile device 104 over a period of time, the mobile device 104 may detect that the user 100 is standing, sitting, or lying down. In other words, the mobile device 104 detects/infers that the user 100 is awake.
  • the mobile device 104 may detect that the user 100 is exercising when the movement or a change in orientation is greater than a threshold for a period of time.
  • the mobile device 104 may detect the heartrate of the user 100 using a heartrate sensor. Based on the heartrate and/or the movement of the user 100 over a period of time, the mobile device 104 may detect whether the user 100 is asleep or awake.
  • the information about the mobile device 104 or the user 100 is used to provide information about or treat the diabetic condition.
  • the mobile device 104 may provide information to the user 100 about the user’s medical condition.
  • the mobile device 104 may provide blood glucose levels, blood potassium levels, meal-related information, exercise-related information, treatment notifications, and/or graphs and other graphical user interfaces, such as alerts or notifications, for display.
  • the mobile device 104 may provide therapeutic protocol data to the pen device 103.
  • 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.
  • an associated medication titration event e.g., basal insulin titration event
  • the mobile device 104 may communicate with other devices directly via a wired communication and/or a short-range wireless communication (e.g., WI-FI®, BLUETOOTH®, BLE, NFC, or another suitable short-range wireless communication).
  • the mobile device 104 may communicate indirectly with remote computing device(s) 122 via a network 120 (e.g., using a WI-FI® network, a cellular network, a WI-MAX® network, or another wired or wireless network).
  • the network 120 is a wired or wireless network.
  • the network 120 is used to communicate over the Internet to other devices.
  • the mobile device 104 may communicate with the remote computing device(s) 122 to generate user interfaces for display on the mobile device 104, perform remote computation, or to otherwise control a remote computing device.
  • 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.
  • an application e.g. , a web browser or other local application
  • the mobile device 104 may provide data related to the user’s medical condition, such as blood glucose levels; blood potassium levels; meal-related information; exercise-related information; dosing information (e.g., dosing levels or reminders for glucose or other forms of treatment); information related to the state of one or more devices in the system (e.g., battery state, on/off state, error state, connected state, and/or other states related to analyte monitoring devices and/or one or more other devices); graphs and other graphical user interfaces for display, and/or notifications (e.g., or alerts) that may be provided to the user 100.
  • the mobile device 104 may provide data received from one or more other devices, such as analyte monitoring devices or treatment devices, and/or data generated locally thereon from one or more software applications.
  • the mobile device 104 may communicate with one or more analyte monitoring devices, such as the pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device.
  • the mobile device 104 may receive data from an analyte monitoring device in order to allow the user 100 to treat the medical condition.
  • the mobile device may receive analyte levels (e.g. , blood glucose levels, blood potassium levels, and/or other analyte levels) from one or more analyte monitoring devices for being displayed to the user.
  • the data from the analyte monitors may also indicate a rate of change of the analyte levels.
  • the analyte monitoring devices may each provide the analyte levels and/or the rate of change to the mobile device 104 in response to measurements are performed locally thereon and while the analyte monitoring device is connected to the mobile device 104.
  • the analyte monitoring devices may provide data to the mobile device 104 at predefined times of day and/or throughout periods of time (e.g., the day and/or night).
  • the analyte monitoring devices may provide data to the mobile device 104 in response to the analyte levels reaching a predefined threshold or coming within a predefined level of a predefined threshold.
  • the 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.
  • 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
  • one or more remote computing devices 122 may be implemented to execute the application for providing a graphical user interface with the notifications for providing the information related to the medical condition of the user 100 and/or treatment thereof.
  • the mobile device 104 may become unable to properly receive and/or monitor data from other devices (e.g., analyte monitoring devices, remote computing device 122, and/or another device) if it becomes disconnected from those devices, the mobile device 104 may also provide a notification to the user 100 when the mobile device becomes disconnected from another device, such that the user 100 may understand that their analyte levels or other information related to their medical condition may be changing. As shown in FIG. 1 B, the mobile device 104 may become disconnected from analyte measurement devices, such as the pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device.
  • analyte measurement devices such as the pen device 103, CGM 102, BGM 106, FGM 111 , a blood potassium monitoring device, and/or another analyte monitoring device.
  • the disconnections between the mobile device 104 and the analyte measurement device may be the result of the analyte measurement device losing power, a range or distance between the mobile device 104 and the analyte measurement device, a congested RF environment, and/or other RF interference (e.g., walls or other physical structures).
  • a congested RF environment may include multiple devices communicating on a same RF band. For example, if the mobile device 104 and the analyte measuring device are communicating on a BLUETOOTH communication link, the greater the number of other BLUETOOTH devices communicating within the same space may cause a greater amount of interference with the communications between the analyte monitoring device and the mobile device 104.
  • the notification of the disconnection between the analyte monitoring device and the computing device may be delayed until the predicted period of time t pre dicted has elapsed.
  • the computing device may delay the notification after the time to of disconnection until one or more of the predicted periods of time t pre dicted (e.g. , t pre dictedi, t pre dicted2, t P redicted3, or tpredicted ⁇ have elapsed.
  • the computing device may calculate multiple predicted periods of time t pre dicted and provide multiple notifications to the user as each predicted period of time elapses.
  • One or more portions of the process 300 may be stored in memory as computer-readable or machine-readable instructions that may be executed by a processor of the one or more computing devices. Though portions of the process 300 may be described herein as being performed by a particular computing device, the process 300 may be performed by another computing device or distributed across multiple computing devices, such as one or more mobile devices, remote computing devices, analyte monitoring devices, and/or one or more other devices.
  • a disconnection between the analyte monitoring device and another computing device may be detected.
  • the disconnection may be detected by a computing device, such as a mobile device and/or the analyte monitoring device itself.
  • the computing device or the analyte monitoring device may predict one or more periods of time at which an analyte level will reach a threshold.
  • the computing device or the analyte monitoring device may send a message to another device for predicting one or more periods of time at which an analyte level will reach a threshold.
  • a determination may be made as to whether the analyte level of the user is at or within a threshold range at the time of detection of the disconnection at 304.
  • the analyte monitoring device or another computing device may determine whether the analyte level of the user is within a predefined range that indicates a normal or healthy level. If the analyte level is not at or within the threshold range at 306, a notification may be provided at 307.
  • the notification may indicate that the computing device has disconnected from the analyte monitoring device.
  • the notification may indicate that the analyte level of the user may be approaching or may have reached a predefined threshold.
  • the one or more predicted periods of time may each include a period of time at which the analyte level of the user may be predicted to reach a corresponding threshold.
  • the corresponding threshold may be a high-end threshold or a low-end threshold of the predefined range indicating the normal or healthy analyte level.
  • the corresponding threshold may be user-defined thresholds or predefined thresholds related to an extreme medical condition or state.
  • the one or more predicted periods of time may each be determined based on the measurement of the analyte level and/or the rate of change of the analyte level at the time the disconnection is determined. For example, the one or more predicted periods of time may be determined using Equation 1 herein. Other similar algorithms or models may be implemented for determining the predicted periods of time.
  • One or more notifications related to the detected disconnection may be delayed, at 310, until a later triggering event.
  • each of the one or more notifications may be delayed until an expiration of a predicted period of time at which the analyte level is predicted to reach a corresponding threshold or a predefined maximum period of time has elapsed.
  • the one or more notifications may be delayed when the analyte level is at or within the threshold range indicating a normal or healthy analyte level to allow for the analyte monitoring device to reconnect with the computing device and/or without affecting the health of the user.
  • a determination may be made as to whether one or more of the predicted periods of time has elapsed since the disconnection.
  • a determination may be made as to whether there are additional notifications pending to be provided. If the maximum period of time has elapsed, any of the additional notifications that are pending as a result of the disconnection may be canceled and prevented from being provided. If the computing device is capable of providing multiple notifications based on different predicted periods of time (e.g., a notification that relates to a user-defined threshold and/or a notification that relates to a predefined threshold for an extreme medical condition), then the process may continue to monitor other predicted periods of time relating to other thresholds, as well as the disconnected status of the devices.
  • the overlay notification 408 may be provided as a diabetic overlay notification providing information related to the diabetic condition of the user or another overlay notification related to another medical condition of the user.
  • the information provided on the overlay notification 408 may include an indication 410 that the computing device 400 has detected a disconnection from the analyte monitoring device.
  • the overlay notification 408 may be provided after a predicted period of time related to a threshold of the analyte level has elapsed from the time of the disconnection.
  • the overlay notification 408 may be provided after a predefined maximum period of time has elapsed from the time of the disconnection.
  • the overlay notification 408a may include an indication 414 of the analyte level of the user at the time of the disconnection.
  • the overlay notification 408a may include an indication of the user’s blood glucose level or blood potassium level at the time of the disconnection.
  • the overlay notification 408a may include an indication 416 of the predicted analyte level of the user at the time of the display of the overlay notification 408a.
  • the overlay notification 408a may include an indication of the user’s predicted blood glucose level or blood potassium level at the time of the triggering of the overlay notification 408a, which may be the value of the corresponding threshold (e.g., user-defined threshold or threshold of the extreme medical condition or event).
  • FIG. 5 is a block diagram of an example computing device 500.
  • the computing device 500 may be a mobile computing device, such as a tablet, a cellular phone, a wearable device, an analyte monitoring device (e.g., a CGM controller device), a remote computing device, or another computing device, for example.
  • the computing device 500 may include a processor 502 for controlling the functionality of the computing device 500.
  • the processor 502 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like.
  • the processor 502 may perform signal coding, data processing, power control, image processing, input/output processing, or any other functionality that enables the computing device 500 to perform as described herein.
  • the processor 502 may store information in or retrieves information from the memory 516.
  • the memory 516 includes a non-removable memory or a removable memory.
  • the non-removable memory includes random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage.
  • the removable memory includes a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), or any other type of removable memory.
  • SIM subscriber identity module
  • the processor 502 may access the memory 516 for executable instructions or other information that is used by the computing device 500.
  • the memory 516 may include computer-readable or machine-readable instructions that may be executed by the processor 502 for performing one or more methods, processes, or procedures, or portions thereof, as described herein.
  • the computing device 500 may include a camera 506 that is in communication with the processor 502.
  • the camera 506 may be a digital camera or other optical device capable of generating images or videos (e.g., image sequences) for being captured at the computing device 500.
  • the camera 506 may include a lighting device capable of flashing to in response to signals from the processor 502.
  • the heartrate monitoring sensor may take an electrocardiogram (ECG) and detect information about the user’s heartrate from the ECG.
  • ECG electrocardiogram
  • the accelerometer may measure the non-gravitational acceleration of the computing device 800 in a given direction.
  • the accelerometer may respond to vibrations associated with movement in a given direction.
  • the measurements from the accelerometer may be used by the processor 502 to determine the magnitude or direction of the relative movement of the computing device 500, or the user’s relative position (e.g., standing, sitting, or lying down).
  • the gyroscope may be used to determine the orientation of the computing device 500.
  • the processor 502 may be in electrical communication with or control a speaker 508.
  • the speaker 508 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 502.
  • the computing device 500 may include a visual indicator, such as one or more light-emitting diodes (LEDs) 512.
  • a visual indicator such as one or more light-emitting diodes (LEDs) 512.
  • LEDs light-emitting diodes
  • 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).
  • the transmitting device 604 may include another communication circuit 616 for communicating with other devices.
  • the processor 602 may be in electrical communication with the communication circuit 616 for sending or receiving information.
  • the communication circuits 616, 618 are capable of performing wired or wireless communications.
  • 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.
  • RF radio frequency
  • the communication circuits 616, 618 may communicate using the same RF protocol or a different RF protocol.
  • the processor 602 may store information in or retrieve information from the memory 612.
  • the processor 602 may be in electrical communication with or control a speaker 614.
  • the speaker 614 may provide an audible sound (e.g., tone, beep, or buzz) in response to a triggering event detected by the processor 602.
  • the continuous monitoring device 600 may include an electric motor 610 that is in electrical communication with or controlled by the processor 602.
  • the electric motor 610 may rotate and causes the continuous monitoring device 600 to vibrate (e.g., to indicate a notification) or provide haptic feedback in response to a triggering event detected by the processor 602.
  • the electric motor 610 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 614.
  • FIG. 7 is a block diagram of an example blood glucose meter (BGM) device 700.
  • the BGM device 700 may include a processor 702 for controlling the functionality of the BGM device 700.
  • the processor 702 may include one or more circuits, such as general-purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like.
  • the processor 702 may perform signal coding, data processing, power control, image processing, input/output processing, and/or any other functionality that enables the BGM device 700 to perform as described herein.
  • the processor 702 may store information in or retrieve information from the memory 716.
  • the memory 716 may include a non-removable memory or a removable memory.
  • the non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, and/or any other type of non-removable memory storage.
  • the removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card (e.g., a digital camera memory card), and/or any other type of removable memory.
  • SIM subscriber identity module
  • the memory 716 may include computer-readable or machine-readable instructions that may be executed by the processor 702 for performing one or more methods, processes, or procedures, or portions thereof, as described herein.
  • the processor 702 may access the memory 716 for executable instructions or other information that is used by the BGM device 700.
  • the 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.
  • the BGM sensor module 704 may include a blood glucose measuring engine that may analyze blood samples provided by a patient on a blood glucose measurement strip and measure the amount of blood glucose in the samples.
  • the BGM device 700 may include an electric motor 710 that is in electrical communication with or controlled by the processor 702.
  • the electric motor 710 may rotate and cause the BGM device 700 to vibrate (e.g., to indicate an notification) or provide haptic feedback in response to a triggering event detected by the processor 702.
  • the electric motor 710 may provide an alert to supplement the audible alarm or replace the audible alarm provided by the speaker 708.
  • the BGM device 700 may include a visual indicator, such as one or more one or more lightemitting diodes (LEDs) 728.
  • a visual indicator such as one or more one or more lightemitting diodes (LEDs) 728.
  • 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).
  • Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random-access memory (RAM), removable disks, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)
  • Measurement Of The Respiration, Hearing Ability, Form, And Blood Characteristics Of Living Organisms (AREA)

Abstract

Des modes de réalisation de la présente invention sont décrits dans la description pour retarder des notifications relatives à des dispositifs de surveillance d'analyte déconnectés utilisés pour contribuer au traitement d'une affection médicale. L'utilisateur peut mettre en œuvre un dispositif mobile et/ou un ou plusieurs dispositifs de surveillance d'analyte pour surveiller des informations relatives à son affection médicale ou à d'autres informations liées à la santé. Le dispositif mobile peut recevoir des données depuis un dispositif de surveillance d'analyte lorsqu'il est connecté au dispositif de surveillance d'analyte. Le dispositif mobile peut détecter une déconnexion du dispositif de surveillance d'analyte et retarder une notification à l'utilisateur concernant la déconnexion jusqu'à ce qu'une durée prédite se soit écoulée sans détecter une reconnexion au dispositif de surveillance d'analyte. La durée prédite peut être basée sur le taux d'analyte de l'utilisateur et/ou un taux de changement du taux d'analyte pour contribuer à éviter que le retard ait un impact négatif sur la santé de l'utilisateur.
PCT/EP2025/051946 2024-03-26 2025-01-27 Réduction de notification pour des déconnexions de communication lors de l'utilisation de dispositifs connectés pour le traitement d'une affection médicale Pending WO2025201696A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP24166252.7 2024-03-26
EP24166252 2024-03-26

Publications (1)

Publication Number Publication Date
WO2025201696A1 true WO2025201696A1 (fr) 2025-10-02

Family

ID=90482412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2025/051946 Pending WO2025201696A1 (fr) 2024-03-26 2025-01-27 Réduction de notification pour des déconnexions de communication lors de l'utilisation de dispositifs connectés pour le traitement d'une affection médicale

Country Status (1)

Country Link
WO (1) WO2025201696A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180172664A1 (en) 2016-12-20 2018-06-21 Abbott Diabetes Care Inc. Systems, devices, and methods for wireless communications in analyte monitoring systems
US20220248988A1 (en) 2020-09-17 2022-08-11 Abbott Diabetes Care Inc. Digital and user interfaces for analyte monitoring systems
CN116052822A (zh) * 2023-02-28 2023-05-02 上海移宇科技有限公司 一种模拟血糖丢失值的方法
US11670418B2 (en) * 2014-10-22 2023-06-06 Dexcom, Inc. User interfaces for continuous glucose monitoring

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11670418B2 (en) * 2014-10-22 2023-06-06 Dexcom, Inc. User interfaces for continuous glucose monitoring
US20180172664A1 (en) 2016-12-20 2018-06-21 Abbott Diabetes Care Inc. Systems, devices, and methods for wireless communications in analyte monitoring systems
US20220248988A1 (en) 2020-09-17 2022-08-11 Abbott Diabetes Care Inc. Digital and user interfaces for analyte monitoring systems
CN116052822A (zh) * 2023-02-28 2023-05-02 上海移宇科技有限公司 一种模拟血糖丢失值的方法

Similar Documents

Publication Publication Date Title
US9582646B2 (en) Connected patient monitoring system and method to provide patient-centric intelligent monitoring services
JP6640857B2 (ja) 医療用ブレスレット規格
EP3389491B1 (fr) Rétro-saisie de données destinées au suivi continu du glucose
US20170124272A1 (en) Data backfilling for continuous glucose monitoring
US10022086B1 (en) Extended band system
AU2017225089A1 (en) Systems and methods for providing sensitive and specific alarms
US20140253323A1 (en) Low analyte level alert system from continuous analyte monitor
US20140340219A1 (en) Physiological monitoring and alerting
KR20100024500A (ko) 개인용 가상 보조기
KR20160110847A (ko) 다중 생체신호를 이용한 건강 이상 징후 알람 시스템
WO2018183345A1 (fr) Appareil d'interface utilisateur de capteur d'analyte et procédés
WO2017133576A1 (fr) Lit électrique
JP4514518B2 (ja) 在宅医療装置
US20230301560A1 (en) Imputation of data using contextual information
WO2025201696A1 (fr) Réduction de notification pour des déconnexions de communication lors de l'utilisation de dispositifs connectés pour le traitement d'une affection médicale
JP2004275272A (ja) 生体情報端末、情報管理装置、生体情報収集システム、及び生体情報異常評価方法
Mitchell et al. Beat: Bio-environmental android tracking
WO2023023109A1 (fr) Facilitation de l'adhésion à des tâches conçues pour préserver ou améliorer la santé
EP3818935B1 (fr) Test de la capacité cognitive de l'utilisateur à s'auto-soigner à la suite d'un événement médical
US20240196336A1 (en) Variable power transmission for battery-powered devices
CN114641833A (zh) 提供来自多个患者监测器的患者监测数据的视觉表示
US20250255561A1 (en) Electronic apparatus and controlling method thereof
EP4609781A1 (fr) Dispositif de surveillance mobile portable, système de surveillance et procédé de transmission de données
WO2024249623A1 (fr) Surveillance d'événement mise à jour en continu personnalisable pour des écrans sur un dispositif informatique

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25700798

Country of ref document: EP

Kind code of ref document: A1