IP Library › Granted Patent US 12,572,444
Granted Patent B2
US 12,572,444 · App. 18/485,713 · Granted Mar 10, 2026

Compatibility check for continuous glucose monitoring application

Inventors: Issa Sami Salameh (San Diego, CA); Douglas William Burnette (San Diego, CA); Tifo Vu Hoang (San Marcos, CA); Steven David King (San Diego, CA); Stephen M. Madigan (San Diego, CA); Michael Robert Mensinger (San Diego, CA); Andrew Attila Pal (San Diego, CA); Michael Ranen Tyler (Carlsbad, CA)
Assignee: Dexcom, Inc.
G06F11/3604A61B5/6801G06F8/65G06F8/70G06F8/71G06F9/44505G06F11/00G06F11/143G06F11/1433G06F11/36G06F11/3616G06F11/3688G16H40/40H04L67/34H04M1/724H04W4/12H04W4/20H04W4/70A61B5/14532A61B5/743H04M1/72403H04W88/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,572,444
App. No.
18/485,713
Granted
Mar 10, 2026
Kind
B2
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 (32)

1 . A method comprising:

detecting, by a first processor of a user equipment having an analyte monitoring application installed on the user equipment, that a compatibility trigger event has occurred on the user equipment;

determining, by the first processor, a plurality of data values from the user equipment in response to the detecting, the plurality of data values representing results from one or more self-tests performed on the user equipment;

validating one or more features of the user equipment based on the one or more self-tests, wherein the one or more self-tests include a validation of a compatibility of the user equipment with a transmitter unit of a continuous analyte monitoring device that is separate from the user equipment, wherein:

the plurality of data values correspond to features of the user equipment and features of the transmitter unit of the continuous analyte monitoring device, and

the continuous analyte monitoring device comprises a second processor configured to process analyte data;

sending, by the first processor of the user equipment, the plurality of data values to a server, wherein the server selects a mode comprising one of a normal mode, a safe mode or a non-operational mode based on a determined compatibility of the analyte monitoring application with the user equipment and the transmitter unit of the continuous analyte monitoring device;

receiving, by the first processor, a message from the server indicating the selected mode corresponding to the determined compatibility, wherein the compatibility of the analyte monitoring application with the user equipment and the transmitter unit of the continuous analyte monitoring device is determined by the server based at least on a comparison of the plurality of data values with a predetermined list of self-tests results; and

operating, based on the message indicating the selected mode received at the user equipment, the analyte monitoring application in the selected mode.

2 . The method of claim 1 , wherein the compatibility trigger event comprises at least one of launching of the analyte monitoring application on the user equipment, updating of the analyte monitoring application on the user equipment, active use of the analyte monitoring application on the user equipment, or idling of the analyte monitoring application in a background on the user equipment.

3 . The method of claim 1 , wherein the compatibility trigger event comprises at least one of updating of an operating system on the user equipment or turning on the user equipment.

4 . The method of claim 1 , wherein the compatibility trigger event comprises receipt, by the first processor, of a request from the server to initiate a user equipment compatibility determining process.

5 . The method of claim 4 , wherein the request is received from the server on a periodic basis.

6 . The method of claim 1 , wherein the plurality of data values from the user equipment comprise data values associated with the compatibility trigger event.

7 . The method of claim 6 , wherein the data values associated with the compatibility trigger event comprise at least one of a description of the compatibility trigger event or a time of the compatibility trigger event.

8 . The method of claim 1 , wherein the plurality of data values correspond to a firmware version of the transmitter unit of the continuous analyte monitoring device and a hardware version of the transmitter unit of the continuous analyte monitoring device.

9 . The method of claim 1 , wherein the continuous analyte monitoring device comprises a subcutaneous analyte sensor and the user equipment comprises a smartphone.

10 . A system comprising a user equipment having an analyte monitoring application installed on the user equipment, the user equipment comprising:

a memory comprising executable instructions; and

a first processor in data communication with the memory and configured to execute the executable instructions to:

detect that a compatibility trigger event has occurred on the user equipment;

determine a plurality of data values from the user equipment in response to the detecting, the plurality of data values representing results from one or more self-tests performed on the user equipment;

validate one or more features of the user equipment based on the one or more self-tests, wherein the one or more self-tests include a validation of a compatibility of the user equipment with a transmitter unit of a continuous analyte monitoring device that is separate from the user equipment, wherein the continuous analyte monitoring device comprises a second processor configured to process analyte data and the plurality of data values correspond to features of the user equipment and features of the transmitter unit of the continuous analyte monitoring device;

send the plurality of data values to a server, wherein the server selects a mode comprising one of a normal mode, a safe mode or a non-operational mode based on a determined compatibility of the analyte monitoring application with the user equipment and the transmitter unit of the continuous analyte monitoring device;

receive a message from the server indicating the selected mode corresponding to the determined compatibility, wherein the compatibility of the analyte monitoring application with the user equipment and the transmitter unit of the continuous analyte monitoring device is determined by the server based at least on a comparison of the plurality of data values with a predetermined list of self-tests results; and

operate, based on the message received at the user equipment, the analyte monitoring application in the selected mode.

11 . The system of claim 10 , wherein the compatibility trigger event comprises at least one of launching of the analyte monitoring application on the user equipment, updating of the analyte monitoring application on the user equipment, active use of the analyte monitoring application on the user equipment, or idling of the analyte monitoring application in a background on the user equipment.

12 . The system of claim 10 , wherein the compatibility trigger event comprises at least one of updating of an operating system on the user equipment or turning on the user equipment.

13 . The system of claim 10 , wherein the compatibility trigger event comprises receipt, by the first processor, of a request from the server to initiate a user equipment compatibility determining process.

14 . The system of claim 13 , wherein the request is received from the server on a periodic basis.

15 . The system of claim 10 , wherein the plurality of data values from the user equipment comprise data values associated with the compatibility trigger event.

16 . The system of claim 15 , wherein the data values associated with the compatibility trigger event comprise at least one of a description of the compatibility trigger event or a time of the compatibility trigger event.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 2, 2023
From: SALAMEH, ISSA SAMI; BURNETTE, DOUGLAS WILLIAM; HOANG, TIFO VU; KING, STEVEN DAVID; MADIGAN, STEPHEN M.; MENSINGER, MICHAEL ROBERT; PAL, ANDREW ATTILA; TYLER, MICHAEL RANEN
To: DEXCOM, INC.
Reel/Frame 065438/0428 →
Continuity (5)
Continuation 17338212 · Jun 3, 2021
Continuation 16728536 · Dec 27, 2019
Continuation 15333552 · Oct 25, 2016
Provisional Application 62251524 · Nov 5, 2015
Related Publication 20240126676A1 · Apr 18, 2024
References Cited (32)
US 7792922B2 · Purcell et al. · 2010 [cited by applicant]
US 8452610B2 · Lipner et al. · 2013 [cited by applicant]
US 8595607B2 · Nekoomaram et al. · 2013 [cited by applicant]
US 8983378B2 · Karuppiah · 2015 [cited by examiner]
US 9336353B2 · Valdes · 2016 [cited by examiner]
US 9626183B1 · Smith · 2017 [cited by examiner]
US 9734042B1 · Elgarat · 2017 [cited by applicant]
US 10467073B2 · Michel · 2019 [cited by examiner]
US 10545849B2 · Salameh et al. · 2020 [cited by applicant]
US 10691574B2 · Salameh et al. · 2020 [cited by applicant]
US 20050177051A1 · Almen · 2005 [cited by applicant]
US 20060227367A1 · Kitada · 2006 [cited by examiner]
US 20090228519A1 · Purcell et al. · 2009 [cited by applicant]
US 20100313105A1 · Nekoomaram et al. · 2010 [cited by applicant]
US 20100317401A1 · Lee et al. · 2010 [cited by applicant]
US 20110119072A1 · Lipner et al. · 2011 [cited by applicant]
US 20110320130A1 · Valdes et al. · 2011 [cited by applicant]
US 20120303476A1 · Krzyzanowski et al. · 2012 [cited by applicant]
US 20130086573A1 · Moritzen · 2013 [cited by examiner]
US 20130132416A1 · Hayter · 2013 [cited by examiner]
US 20130317401A1 · Joslin · 2013 [cited by applicant]
US 20140012117A1 · Mensinger et al. · 2014 [cited by applicant]
US 20150154364A1 · Biasi et al. · 2015 [cited by applicant]
US 20150289819A1 · Kamath et al. · 2015 [cited by applicant]
US 20170131993A1 · Salameh et al. · 2017 [cited by applicant]
US 20170132120A1 · Salameh et al. · 2017 [cited by applicant]
US 20190004935A1 · Gross et al. · 2019 [cited by applicant]
US 20200142804A1 · Salameh et al. · 2020 [cited by applicant]
AU 2020203890B2 · 2021 [cited by applicant]
EP 2913806A1 · 2015 [cited by applicant]
International Preliminary Report on Patentability for Application No. PCT/US2016/058705 mailed on May 17, 2018, 07 pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2016/058705 mailed on Jan. 19, 2017, 07 pages. [cited by applicant]