CGM App Compatibility Checks for Safe Mobile Alert Operation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Incompatibilities between continuous glucose monitoring applications and mobile device operating systems can lead to malfunctioning of critical alert functions, posing risks for diabetic patients due to inadequate glucose level notifications.

Innovation Solution

A method to determine compatibility by comparing data values from the application and operating system with a configuration file, using truncated test entries, ranges, wildcard entries, and regular expressions to ensure safe or normal operation of the CGM application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the CGM application is installed on various user equipment with different operating systems, then the adaptability and versatility of the system is improved, but incompatibilities may arise causing malfunctioning of critical alert functions

Engineering Contradiction:
Improvecompatibility across different operating systemsVSAvoidreliability of critical alert functions
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs compatibility verification before the CGM application is installed or updated on the user equipment. By checking whether the operating system version falls within the supported range and verifying hardware attributes against the configuration file in advance, the system prevents incompatibility issues from occurring, thereby ensuring reliable operation of critical alert functions across different operating systems

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A configuration file serves as an intermediary between the CGM application and diverse user equipment. This configuration file contains test values, supported operating system versions, and hardware attribute requirements that mediate the compatibility check, allowing the system to adapt to different operating systems while maintaining reliability standards

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive compatibility checks are performed before installation, then the reliability of the CGM application is improved, but the complexity of the installation process increases

Engineering Contradiction:
Improvereliability of CGM application operationVSAvoidcomplexity of compatibility verification process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically performs compatibility verification by retrieving the user equipment's operating system version and hardware attributes, comparing them against the configuration file, and determining compatibility without requiring manual user input or complex user-side verification procedures. This self-service approach maintains reliability while minimizing user burden and perceived complexity

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12572444B2Compatibility check for continuous glucose monitoring application
Publication Date: 2026.03.10 DEXCOM INC
  • US12572444B2 patent drawing
  • US12572444B2 patent drawing
  • US12572444B2 patent drawing

AI summary

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.