Compatibility check for continuous glucose monitoring application

• US 10,545,849 B2
• Filed: 10/25/2016
• Issued: 01/28/2020
• Est. Priority Date: 11/05/2015
• Status: Active Grant

• Current Assignee: DexCom Incorporated
• Original Assignee: DexCom Incorporated
• Inventors: Salameh, Issa Sami, Burnette, Douglas William, Hoang, Tifo Vu, King, Steven David, Madigan, Stephen M., Mensinger, Michael Robert, Pal, Andrew Attila, Tyler, Michael Ranen
• Primary Examiner(s): Aponte, Francisco J
• Assistant Examiner(s): Gooray, Mark A
• Application Number:
  US15/333,552
• Publication Number:
  US 20170131993A1
• Time in Patent Office: 1,190 Days
• Field of Search: None
• CPC Class Codes: A61B 5/14532 for measuring glucose, e.g. by tissue impedance measurement
• CPC Class Codes: A61B 5/6801 specially adapted to be attached to or worn on the body surface
• CPC Class Codes: A61B 5/743 Displaying an image simultaneously with additional graphical information, e.g. symbols, charts, function plots
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/143 with loss of software functionality
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 11/3604 Software analysis for verifying properties of programs byte-code verification G06F9/44589
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04M 1/724 User interfaces specially adapted for cordless or mobile telephones
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 88/02 : Terminal devices

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.

Claims

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 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 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 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, wherein the determining further comprises determining if a core functionality of the glucose monitoring application is compatible with the operating system and/or if an ancillary functionality of the glucose monitoring application is compatible with the operating system; 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 if a core functionality of the glucose monitoring application is incompatible with the operating system, then causing the glucose monitoring application to operate in the non-operational mode, 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, wherein the core functions includes 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.

2. 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.

3. The method of claim 1, wherein the one or more data values are received from the user equipment when the operating system is updated.

4. 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.

5. 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.

6. 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 one or more ancillary functions are disabled.

7. The method of claim 6, wherein the one or more ancillary functions comprise entering events associated with food consumption.

8. The method of claim 6, wherein the user interface view further indicates that an update for the glucose monitoring application is available.

9. 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.

10. 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.

11. 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 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 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 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 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, wherein the determining further comprises determining if a core functionality of the glucose monitoring application is compatible with the operating system and/or if an ancillary functionality of the glucose monitoring application is compatible with the operating system, 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 if a core functionality of the glucose monitoring application is incompatible with the operating system, then causing the glucose monitoring application to operate in the non-operational mode, 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, wherein the core functions includes 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.

12. The system of claim 11, 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.

13. The system of claim 11, wherein the one or more data values are received from the user equipment when the operating system is updated.

14. The system of claim 11, 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.

15. The system of claim 11, wherein the one or more attributes of the user equipment comprise a manufacturer of the user equipment and a model of the user equipment.

16. The system of claim 11, 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 one or more ancillary functions are disabled.

17. The system of claim 16, wherein the one or more ancillary functions comprise entering events associated with food consumption.

18. The system of claim 16, wherein the user interface view further indicates that an update for the glucose monitoring application is available.

19. The system of claim 11, 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.

20. The system of claim 19, 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.

21. The system of claim 11, wherein the operations further comprise 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.

22. The system of claim 11, 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 wherein the operations further include 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.