US-20260127091-A1 - COMPATIBILITY CHECK FOR CONTINUOUS GLUCOSE MONITORING APPLICATION

Abstract

Disclosed are systems, methods, and articles for determining compatibility of a mobile application and operating system on a mobile device. In some aspects, a method includes receiving one or more data values from a mobile device having a mobile medical software application installed thereon, the data value(s) characterizing a version of the software application, a version of an operating system installed on the mobile device, and one or more attributes of the mobile device; determining whether the mobile medical software application is compatible with the operating system by at least comparing the received data value(s) to one or more test values in a configuration file; and sending a message to the mobile device based on the determining, the message causing the software application to operate in one or more of a normal mode, a safe mode, and a non-operational mode.

Inventors

• Issa Sami Salameh
• Douglas William Burnette
• Tifo Vu Hoang
• Steven David King
• Stephen M. Madigan
• Michael Robert Mensinger
• Andrew Attila Pal
• Michael Ranen Tyler

Assignees

• DEXCOM, INC.

Dates

Publication Date

20260507

Application Date

20251231

Claims (20)

1. 1 . A method comprising: receiving, by at least one processor, one or more data values from a user equipment having a glucose monitoring application installed on the user equipment, the one or more data values comprising at least one of: a version of the glucose monitoring application, a version of an operating system installed on the user equipment, or one or more attributes of the user equipment; determining, by the at least one processor, whether the glucose monitoring application is compatible with the operating system by at least comparing the received one or more data values to one or more test values in a configuration file, the one or more test values comprising at least one of: one or more compatible operating system versions or one or more compatible user equipment attributes; and sending, by the at least one processor, a message to the user equipment based on the determining, the message causing the glucose monitoring application to operate in one or more of a normal mode, a safe mode, and a non-operational mode; wherein while the glucose monitoring application is in the safe mode one or more ancillary functions of the glucose monitoring application are disabled; wherein while the glucose monitoring application is in the non-operational mode, one or more core functions are disabled; and wherein the one or more core functions include one or more modules that are essential to the operation of the glucose monitoring application and wherein the one or more ancillary functions include one or more modules that are not essential to the operation of the glucose monitoring application.
2. 2 . The method of claim 1 , wherein the one or more test values further comprise at least one of: a range of one or more compatible operating system versions, a wildcard entry of compatible operating system versions, or a regular expression of one or more compatible user equipment attributes.
3. 3 . The method of claim 1 , wherein the one or more data values are received from the user equipment when the glucose monitoring application is launched, when the glucose monitoring application is updated, when the glucose monitoring application is being used, or when the glucose monitoring application is idling.
4. 4 . The method of claim 1 , wherein the one or more data values are received from the user equipment when the operating system is updated.
5. 5 . The method of claim 1 , wherein the one or more data values are received from the user equipment when the user equipment is turned on or when the user equipment receives a request from a server communicatively coupled with the user equipment.
6. 6 . The method of claim 1 , wherein the one or more attributes of the user equipment comprise a manufacturer of the user equipment and a model of the user equipment.
7. 7 . The method of claim 1 , wherein the message causes the user equipment to display a user interface view on the user equipment while the glucose monitoring application is in the safe mode, the user interface view indicating that the one or more ancillary functions are disabled.
8. 8 . The method of claim 7 , wherein the one or more ancillary functions comprise entering events associated with food consumption.
9. 9 . The method of claim 7 , wherein the user interface view further indicates that an update for the glucose monitoring application is available.
10. 10 . The method of claim 1 , wherein the message causes the user equipment to display a user interface view on the user equipment while the glucose monitoring application is in the non-operational mode, the user interface view indicating that the one or more core functions are disabled.
11. 11 . The method of claim 10 , wherein the one or more core functions comprise one or more of generating an alert, displaying a glucose level, and prompting calibration of a glucose sensor assembly.
12. 12 . The method of claim 11 , wherein the alert is generated if a glucose level of a user is outside of a target range.
13. 13 . The method of claim 1 , further comprising sending, by at least one processor, the message a predetermined quantity of times while the glucose monitoring application is operating in the safe mode or the non-operational mode.
14. 14 . The method of claim 1 , wherein the one or more data values further includes identification information of a transmitter unit of a glucose sensor assembly wearable by a patient user, wherein the identification information of the transmitter unit includes one or both of a transmitter device version number and a software version number, and wherein the identification information of the transmitter unit is provided to the user equipment in an advertisement packet transmitted from the transmitter to the user equipment; and the method further including determining, by the at least one processor, whether the transmitter unit is compatible with the user equipment by at least comparing the received one or more data values to the one or more test values in the configuration file.
15. 15 . A system comprising: at least one processor; and at least one memory including code which when executed by the at least one processor causes operations of the system comprising: receiving, by at least one processor, one or more data values from a user equipment having a glucose monitoring application installed on the user equipment, the one or more data values comprising at least one of: a version of the glucose monitoring application, a version of an operating system installed on the user equipment, or one or more attributes of the user equipment; determining, by the at least one processor, whether the glucose monitoring application is compatible with the operating system by at least comparing the received one or more data values to one or more test values in a configuration file, the one or more test values comprising at least one of: one or more compatible operating system versions or one or more compatible user equipment attributes; and sending, by the at least one processor, a message to the user equipment based on the determining, the message causing the glucose monitoring application to operate in one or more of a normal mode, a safe mode, and a non-operational mode; wherein while the glucose monitoring application is in the safe mode one or more ancillary functions of the glucose monitoring application are disabled; wherein while the glucose monitoring application is in the non-operational mode, one or more core functions are disabled; and wherein the one or more core functions include one or more modules that are essential to the operation of the glucose monitoring application and wherein the one or more ancillary functions include one or more modules that are not essential to the operation of the glucose monitoring application.
16. 16 . The system of claim 15 , wherein the one or more test values further comprise at least one of: a range of one or more compatible operating system versions, a wildcard entry of compatible operating system versions, or a regular expression of one or more compatible user equipment attributes.
17. 17 . The system of claim 15 , wherein the message causes the user equipment to display a user interface view on the user equipment while the glucose monitoring application is in the non-operational mode, the user interface view indicating that one or more core functions are disabled.
18. 18 . The system of claim 15 , wherein the core functions include one or more of generating an alert if a glucose level of a user is outside of a target range, displaying a glucose level, or prompting calibration of a glucose sensor assembly.
19. 19 . A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising: receiving, by the at least one processor, one or more data values from a user equipment having a glucose monitoring application installed on the user equipment, the one or more data values comprising at least one of: a version of the glucose monitoring application, a version of an operating system installed on the user equipment, or one or more attributes of the user equipment; determining, by the at least one processor, whether the glucose monitoring application is compatible with the operating system by at least comparing the received one or more data values to one or more test values in a configuration file, the one or more test values comprising at least one of: one or more compatible operating system versions or one or more compatible user equipment attributes; and sending, by the at least one processor, a message to the user equipment based on the determining, the message causing the glucose monitoring application to operate in one or more of a normal mode, a safe mode, and a non-operational mode; wherein while the glucose monitoring application is in the safe mode one or more ancillary functions of the glucose monitoring application are disabled; wherein while the glucose monitoring application is in the non-operational mode, one or more core functions are disabled; and wherein the one or more core functions include one or more modules that are essential to the operation of the glucose monitoring application and wherein the one or more ancillary functions include one or more modules that are not essential to the operation of the glucose monitoring application.
20. 20 . The non-transitory computer-readable storage medium of claim 19 , wherein the one or more test values further comprise at least one of: a range of one or more compatible operating system versions, a wildcard entry of compatible operating system versions, or a regular expression of one or more compatible user equipment attributes.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. Non-Provisional application Ser. No. 18/485,713, filed Oct. 12, 2023, which is a continuation of U.S. Non-Provisional application Ser. No. 17/338,212, filed Jun. 3, 2021, which is a continuation of U.S. Non-Provisional application Ser. No. 16/728,536, filed Dec. 27, 2019, which is a continuation of U.S. Non-Provisional application Ser. No. 15/333,552, filed Oct. 25, 2016, which claims the benefit of U.S. Provisional Application No. 62/251,524, filed on Nov. 5, 2015. Each of the aforementioned applications is incorporated by reference herein in its entirety, and each is hereby expressly made a part of this specification. TECHNICAL FIELD The present disclosure generally relates to systems for managing continuous glucose monitoring medical devices and software compatibility between such devices and computer servers, and, more particularly, to determining whether a continuous glucose monitoring application installed on a user equipment is compatible with the user equipment's operating system. BACKGROUND Diabetes mellitus is a disorder in which the pancreas cannot create sufficient insulin. In a diabetic state, a person suffering from high blood sugar may experience an array of physiological side effects associated with the deterioration of small blood vessels. These side effects may include, for example, kidney failure, skin ulcers, bleeding into the vitreous of the eye, and the like. A hypoglycemic reaction, such as a low blood sugar event, may be induced by an inadvertent overdose of insulin, or after a normal dose of insulin or glucose-lowering agent. In a severe hypoglycemic reaction, there may be a high risk for headache, seizure, loss of consciousness, and coma. A diabetic person may carry a self-monitoring blood glucose (SMBG) monitor which typically requires the user to prick his or her finger to measure his or her glucose levels. Given the inconvenience associated with traditional finger pricking methods, it is unlikely that a diabetic will take a timely SMBG measurement and, consequently, may be unaware whether his or her blood glucose value is indicative of a dangerous situation. SUMMARY Methods and apparatus, including computer program products, are provided for determining whether a user equipment's continuous glucose monitoring application and operating system are compatible. In some example embodiments, there may be provided a method, which includes receiving, by at least one processor, one or more data values from a user equipment having a glucose monitoring application installed on the user equipment, the one or more data values characterizing a version of the glucose monitoring application, a version of an operating system installed on the user equipment, and one or more attributes of the user equipment; determining, by at least one processor, whether the glucose monitoring application is compatible with the operating system by at least comparing the received one or more data values to one or more test values in a configuration file, the one or more test values comprising one or more of a range of compatible operating system versions, a wildcard entry of compatible operating system versions, and a regular expression of compatible user equipment attributes; and sending, by at least one processor, a message to the user equipment based on the determining, the message causing the glucose monitoring application to operate in one or more of a normal mode, a safe mode, and a non-operational mode. Related systems, methods, and articles of manufacture are also disclosed. In some example embodiments, one of more variations may be made as well as described in the detailed description below and/or as described in the following features. The one or more data values may be received from the user equipment when the glucose monitoring application is launched, when the glucose monitoring application is updated, when the glucose monitoring application is being used, or when the glucose monitoring application is idling. The one or more data values may be received from the user equipment, when the operating system is updated. The one or more data values may be received from the user equipment, when the user equipment is turned on or when the user equipment receives a request from a server communicatively coupled with the user equipment. The one or more attributes of the user equipment may include a manufacturer of the user equipment and a model of the user equipment. The message may cause the user equipment to display a user interface view on the user equipment while the glucose monitoring application is in the safe mode, the user interface view indicating that one or more ancillary functions are disabled. The one or more ancillary functions may include entering events associated with food consumption. The user interface view may indicate that an update for the glucose monitoring application is available. The message may cause the