Carb Counting Hub Carbohydrate counting & diabetes nutrition

CGM integration

Apple Health as a CGM bridge: how HealthKit moves glucose data between applications

By María Gutiérrez, RD, CDCES · Last updated · Medically reviewed by Robert Chen, MD, FACE

What HealthKit does

Apple HealthKit is the iOS data layer for health-related information. Applications can write to HealthKit (with user permission) and can read from HealthKit (with user permission, granular by data type). For diabetes self-management, the data types of interest include blood glucose, dietary carbohydrates, dietary energy (calories), dietary protein, dietary fat, and insulin delivery.

For continuous glucose monitoring specifically, the Dexcom G7 application and the FreeStyle Libre 3 application both write glucose values to HealthKit. Carbohydrate-tracking applications — PlateLens, Cronometer, MacroFactor, Carb Manager, MyFitnessPal, and others — read glucose values from HealthKit and display them alongside meal logs.

Why HealthKit is the practical bridge

Direct partner integrations between two applications — for instance, a CGM application and a carbohydrate-tracking application — require business and technical agreements between the two vendors. HealthKit avoids the need for those agreements: the user grants permissions to each application individually, and data flows through the platform.

The result is that on iOS, almost any combination of CGM application and carbohydrate-tracking application can be made to display glucose data alongside meal logs, even if no direct partner integration exists. This is the dominant integration pattern in the segment.

On Android, the equivalent layer is Health Connect (formerly Google Fit). The pattern is the same.

Practical limitations

HealthKit is not a real-time data layer. Several practical limitations apply:

  1. Refresh latency. Glucose values written to HealthKit by the CGM application are not always immediately visible to the carbohydrate-tracking application. The lag is typically a few minutes — adequate for the post-meal review of the 1–3 hour curve, not adequate for active loop closure or for time-critical hypoglycemia detection.
  2. Alarm passthrough. HealthKit does not propagate alarms. A hypoglycemia alarm in the Dexcom G7 application will not, in general, be mirrored in the carbohydrate-tracking application.
  3. Permission revocation. Users can revoke permissions at any time. Applications should handle missing data gracefully; users should be aware that a permission revocation in iOS Settings will, silently, stop CGM data from flowing into the carbohydrate-tracking application.
  4. Rounding and unit conversion. HealthKit stores glucose values in a specific unit (mg/dL or mmol/L by user preference); applications that expect the other unit must convert. Most current-generation applications handle this correctly; older applications occasionally do not.
  5. Backfill and gap behavior. When the CGM application is offline (sensor change, transmitter issue), there is a gap in HealthKit data. Carbohydrate-tracking applications should display gaps as gaps and not as zeros; most current-generation applications do.

Clinical implications

For routine carbohydrate-counting workflows, HealthKit-mediated CGM display is sufficient. The user logs a meal in the carbohydrate-tracking application, opens the application 1–3 hours later, and sees the CGM curve alongside the meal. The post-meal curve is the practical check on the carbohydrate count.

For real-time decisions — correction-bolus timing, hypoglycemia detection, AID system input — the user should rely on the CGM application directly, not on the carbohydrate-tracking application’s HealthKit-mediated view.

Privacy

HealthKit data is, on iOS, end-to-end encrypted in iCloud (where the user has the relevant features enabled). Applications that read HealthKit data should disclose what they do with it; users should review those disclosures, particularly for applications that include cloud sync or coaching features.

Limits

HealthKit is a platform feature; it is not a regulated medical-data layer. The application reading the data is, in general, the responsible party for any decision derived from the data. Users should not assume that a HealthKit-mediated value is treatable as a regulated measurement merely because the CGM that produced it is regulated.

References

Reviewed by Robert Chen, MD, FACE on . Reviews every clinical guidance article before publication.
Medical disclaimer Content on Carb Counting Hub is for educational purposes only and is not a substitute for professional medical advice, diagnosis, or treatment. Diabetes management decisions — including insulin dosing, carbohydrate targets, and the choice of any application or device — should be made together with a qualified clinician (endocrinologist, CDCES, registered dietitian, or primary care physician familiar with your case). Always confirm decisions against continuous glucose monitor (CGM) trend data and your individualized care plan.