Skip to content

Commit

Permalink
Merge pull request #703 from marionbarker/working-docs
Browse files Browse the repository at this point in the history
Clarify Glucose in Apple Health
  • Loading branch information
marionbarker authored Sep 2, 2023
2 parents fe1a83a + 3d924c4 commit 784f325
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/faqs/apple-health-faqs.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,9 +155,9 @@ If you happen to wear a *Dexcom* G6 and G7 sensor at the same time, then startin
*Loop* only uses data from the CGM you selected as your CGM for closed-loop insulin delivery, but don't be surprised at the double trace if you want to wear both during the transition from G6 to G7.

!!! tip "Add Permission to Health for *Dexcom* to Write Glucose"
If either the G6 or the G7 has permission to write to health, then Loop will delete the glucose values that it wrote to health 3 hours earlier. That's when the *Dexcom* app will start writing its glucose values and you only want one to show up in Health history.
If either the G6 or the G7 has permission to write to *Apple Health*, then Loop will delete the *Loop* glucose data in *Apple Health* that is older than 3 hours and newer than 1 week. The *Dexcom* app will write its glucose values to Health when each value is 3 hours old.

If you transition from G6 to G7 (or alternate back and forth), be sure that at least the app you are currently using has permission to write to health. (I inadvertently forgot to turn on health permission for G7. By the time I noticed, I had a gap of several days in my Apple Health storage of glucose values.)
If you transition from G6 to G7 (or alternate back and forth), be sure that at least the app you are currently using has permission to write to health. (I inadvertently forgot to turn on health permission for G7. By the time I noticed, I had a gap of several days in my *Apple Health* storage of glucose values.)

#### *Libre*

Expand Down
4 changes: 3 additions & 1 deletion docs/loop-3/add-cgm.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,9 @@ Minimal documentation is provided.
{align="center"}

!!! tip "Don't forget Health Permissions"
For those switching from *Dexcom G6* to *Dexcom G7*, you might forget to add permission for the *G7* app to write to *Apple Health*. If you want long-term history of those CGM readings to persist in *Apple Health*, turn on the permission for the *Dexcom* app to write glucose to *Health*. The Loop values are removed from *Apple Health* 3 hours after they are written if either the G6 or G7 *Dexcom* apps have write permission.
For those switching from *Dexcom G6* to *Dexcom G7*, you might forget to add permission for the *G7* app to write to *Apple Health*. If you want long-term history of those CGM readings to persist in *Apple Health*, turn on the permission for the *Dexcom* app to write glucose to *Health*.

If either the G6 or the G7 has permission to write to *Apple Health*, then *Loop* will delete the *Loop* glucose data in *Apple Health* that is older than 3 hours and newer than 1 week. The *Dexcom* app will write its glucose values to Health when each value is 3 hours old.

### Medtronic Enlite CGM

Expand Down

0 comments on commit 784f325

Please sign in to comment.