From 6ef4f6508fc4a3d27b662622c1e94afdf4cdb293 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Wed, 30 Aug 2023 08:12:38 -0700 Subject: [PATCH 1/6] Update the guardrails for basal rates section --- docs/loop-3/therapy-settings.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/loop-3/therapy-settings.md b/docs/loop-3/therapy-settings.md index 7dd0c3f2851..2d82e186cf3 100644 --- a/docs/loop-3/therapy-settings.md +++ b/docs/loop-3/therapy-settings.md @@ -260,8 +260,10 @@ The font color in the value picker has the following meaning: #### Guardrails for Maximum Basal Rate -* Top value available on the picker is 6.4 times the highest basal rate in your scheduled basal rates - +* Recommended maximum value available on the picker is 6.4 times the highest basal rate in your scheduled basal rates + * Values higher than this, if available, are shown in yellow +* Absolute maximum value is 70 divided by the smallest carb ratio (CR) in your schedule + * Depending on your basal rate and CR schedules, the maximum value available on the picker might be more that 6.4 times the highest basal rate #### Guardrails for Maximum Bolus From f096347cb28814007a504aa7a2b815659db304f9 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Wed, 30 Aug 2023 11:52:15 -0700 Subject: [PATCH 2/6] Add CGM section to health permsission for apple-health-faqs --- docs/faqs/apple-health-faqs.md | 119 ++++++++++++++++++++------------- 1 file changed, 74 insertions(+), 45 deletions(-) diff --git a/docs/faqs/apple-health-faqs.md b/docs/faqs/apple-health-faqs.md index 058c52d7360..16107ec461a 100644 --- a/docs/faqs/apple-health-faqs.md +++ b/docs/faqs/apple-health-faqs.md @@ -1,11 +1,12 @@ -## How does Loop use Apple HealthKit? +## How does *Loop* use *Apple* HealthKit? -Loop uses Apple HealthKit as long term storage for glucose, insulin and carbohydrates. But there is more going on than simple storage. +*Loop* uses *Apple* HealthKit as long term storage for glucose, insulin and carbohydrates. But there is more going on than simple storage. -It is important that permissions for Loop be properly configured for the Health app. +It is important that permissions for *Loop* be properly configured for the Health app. -* Loop 2.2.x: See [Health Permissions](../build/health.md) -* Loop 3: See [Apple Health Permissions](../loop-3/onboarding.md#apple-health-permissions) +* `Loop 3.x.x`: See [Apple Health Permissions](../loop-3/onboarding.md#apple-health-permissions) +* `Loop 2.2.x`: See [Health Permissions](../build/health.md) + * If you are still on Loop 2 (or FreeAPS), consider updating to [*Loop 3*](../build/updating.md) To view the list of data stored in Health @@ -27,76 +28,76 @@ To view the list of data stored in Health ## HealthKit Plots -The health app on the Loop phone provides useful plots of data since you started to Loop with that Apple ID. Examples for insulin delivery and carbohydrates are shown in the graphic below. New versions of iOS modified details of the display with the same or improved capabilities. +The health app on the *Loop* phone provides useful plots of data since you started to *Loop* with that *Apple* ID. Examples for insulin delivery and carbohydrates are shown in the graphic below. New versions of iOS modified details of the display with the same or improved capabilities. ![example insulin and carb plots visible with HealthKit](img/health1.jpg){width="600"} ## HealthKit Details -### Glucose and Apple HealthKit +### Glucose and *Apple* HealthKit -For Dexcom users with the Dexcom app on the Loop phone, the Dexcom app writes the value to Health with a 3-hour delay. +For Dexcom users with the Dexcom app on the *Loop* phone, the Dexcom app writes the value to Health with a 3-hour delay. -Loop reads the Dexcom information at the same time the Dexcom app gets the reading from the transmitter. It uses the glucose value to update predictions and stores it in Health. +*Loop* reads the Dexcom information at the same time the Dexcom app gets the reading from the transmitter. It uses the glucose value to update predictions and stores it in Health. -If you look at your Health glucose readings, you'll notice the Loop icon for the last 3 hours and the Dexcom icon for times earlier than that. +If you look at your Health glucose readings, you'll notice the *Loop* icon for the last 3 hours and the Dexcom icon for times earlier than that. -All other CGM readings are reported with the Loop icon and there is no transition after 3 hours. +All other CGM readings are reported with the *Loop* icon and there is no transition after 3 hours. -You may also notice that the Dexcom numbers get smoothed out. For example, the Dexcom readings, when they first are read from the transmitter may bounce up and down a bit. The Dexcom app will retrospectively smooth the numbers, changing what is displayed in their app compared to the original reading. The last 3 hours of data from Loop does not show that smoothing - it reports the value sent by the transmitter. If you suspect a sensor is not behaving well, check the Loop glucose plots compared to the Dexcom plots to assist in your evaluation. It might be time to confirm glucose with a fingerstick meter as well. +You may also notice that the Dexcom numbers get smoothed out. For example, the Dexcom readings, when they first are read from the transmitter may bounce up and down a bit. The Dexcom app will retrospectively smooth the numbers, changing what is displayed in their app compared to the original reading. The last 3 hours of data from *Loop* does not show that smoothing - it reports the value sent by the transmitter. If you suspect a sensor is not behaving well, check the *Loop* glucose plots compared to the Dexcom plots to assist in your evaluation. It might be time to confirm glucose with a fingerstick meter as well. -### Carbohydrates and Apple HealthKit +### Carbohydrates and *Apple* HealthKit -In Loop 2.2.x, if you set Apple Health app permissions to allow it, Loop will read carbohydrates from the Health app. If you give a third-party app permission to store carbohydrate data in Health, and do not realize that Loop reads that information, you might get unexpected insulin delivery based off those carbs. To avoid that unanticipated behavior, the directions tell you to set permissions to allow Loop to write to carbohydrate storage but not read. +In `Loop* 2.2.x`, if you set *Apple* Health app permissions to allow it, *Loop* will read carbohydrates from the Health app. If you give a third-party app permission to store carbohydrate data in Health, and do not realize that *Loop* reads that information, you might get unexpected insulin delivery based off those carbs. To avoid that unanticipated behavior, the directions tell you to set permissions to allow *Loop* to write to carbohydrate storage but not read. -In Loop 3, the option to read from Health carbohydrates is explicitly disabled and can only be enabled by setting up special parameters when you build the app. The insructions for the code customization are not in LoopDocs yet. If it is important to you to use a third-party app to record carbohydrates and have Loop read the information and automatically dose with insulin, [ask for help in zulipchat](../intro/loopdocs-how-to.md#how-to-find-help). +In `Loop 3`, the option to read from Health carbohydrates is explicitly disabled and can only be enabled by setting up special parameters when you build the app. The insructions for the code customization are not in LoopDocs yet. If it is important to you to use a third-party app to record carbohydrates and have *Loop* read the information and automatically dose with insulin, [ask for help in zulipchat](../intro/loopdocs-how-to.md#how-to-find-help). -### Insulin and Apple HealthKit +### Insulin and *Apple* HealthKit -The relationship between Loop and Apple HealthKit is very important to understand if you ever need to do one of these actions: +The relationship between *Loop* and *Apple* HealthKit is very important to understand if you ever need to do one of these actions: * Dose insulin from another source (injection, smart pen) * Remove insulin that wasn't really given (failed site or forgot to reattach a tubed pump) !!! danger "Be Cautious" - Allowing users to delete events is fairly risky. If a user deletes a dose accidentally, or does not understand the IOB impact while in Closed Loop, then Loop may start giving insulin that is not needed. + Allowing users to delete events is fairly risky. If a user deletes a dose accidentally, or does not understand the IOB impact while in closed loop is enabled, then *Loop* may start giving insulin that is not needed. - One method to deal with insulin that wasn't given is to go Open Loop for 3 to 6 hours. However, if you take care, you can remove insulin from Loop. + One method to deal with insulin that wasn't given is to go disable closed loop for 3 to 6 hours. However, if you take care, you can remove insulin from *Loop*. !!! abstract "Developer Notes: Pump Events and Insulin Delivery" - Loop stores Pump Events separately from Insulin Delivery. With permissions set to allow Loop to read insulin from Health (recommended), the Insulin Delivery store contains doses entered from Health as well as the subset of pump events that represent doses. + *Loop* stores Pump Events separately from Insulin Delivery. With permissions set to allow *Loop* to read insulin from Health (recommended), the Insulin Delivery store contains doses entered from Health as well as the subset of pump events that represent doses. Pump Events are displayed by tapping an insulin chart on the main screen and viewing the Event History tab. - When you delete a pump event using the Event History interface in Loop, the associated entry in Insulin Delivery is not deleted. + When you delete a pump event using the Event History interface in *Loop*, the associated entry in Insulin Delivery is not deleted. #### Bolus -* When Loop commands the pump to provide a bolus, either manual or automatic, it is shown in the Loop Event History and in the Health app insulin data list - * It may take a Loop Cycle or two to show up in Health, but it will appear -* When you add insulin, such as from an injection, to the Health app, Loop reads it and adds it to IOB +* When *Loop* commands the pump to provide a bolus, either manual or automatic, it is shown in the `Event History` and in the Health app insulin data list + * It may take a loop cycle or two to show up in Health, but it will appear +* When you add insulin, such as from an injection, to the Health app, *Loop* reads it and adds it to IOB * It will not be added to the Event History because this is not a pump event - * Loop 3 adds a new feature that allows you to add non-pump insulin from within the app instead of requiring you to add it inside the Health app -* If you delete an entry from the Loop Event History list, but leave that same entry in Health, Loop reads it back from Health + * *Loop* 3 adds a new feature that allows you to add non-pump insulin from within the app instead of requiring you to add it inside the Health app +* If you delete an entry from the `Event History` list, but leave that same entry in Health, *Loop* reads it back from Health * It will not show up in the Event History, but it will still contribute to IOB - * You must delete a pump event from both Loop Event History and Health data; it is best if you do this within one Loop Cycle - * If that dose showed up in Event History but you could not find it in Health, look again after the next Loop cycle -* If you delete an entry from Health, but leave that same entry in Loop Event History, Loop reports it to Health again - * You must delete a pump event from both the Loop Event History list and Health data; it is best if you do this within one Loop Cycle + * You must delete a pump event from both `Event History` and Health data; it is best if you do this within one loop cycle + * If that dose showed up in `Event History`` but you could not find it in Health, look again after the next loop cycle +* If you delete an entry from Health, but leave that same entry in `Event History`, *Loop* reports it to Health again + * You must delete a pump event from both the `Event History` list and Health data; it is best if you do this within one loop cycle !!! tip "Pro Tip" Write on a piece of paper the times and values you think you should delete. - Look at those values in both Loop Event History and Health Insulin data list. + Look at those values in both `Event History` and Health Insulin data list. - Record what Loop is reporting as IOB. + Record what *Loop* is reporting as IOB. Review the values one more time, and then delete those entries in both places. Review IOB again. If you made a mistake, you can refer to that written list and adjust appropriately. #### Basal -Loop keeps track of how much basal is delivered so the IOB is properly reported. In older versions of Loop, there may be occasional display glitches, but the **internal** accounting is correct and updates every Loop Cycle. +*Loop* keeps track of how much basal is delivered so the IOB is properly reported. In older versions of *Loop*, there may be occasional display glitches, but the **internal** accounting is correct and updates every Loop Cycle. !!! abstract "Developer Notes: Scheduled Basal is Not a Pump Event" Scheduled basal is not a pump event so you will not see it listed in the Event History tab. @@ -105,7 +106,7 @@ Loop keeps track of how much basal is delivered so the IOB is properly reported. The Insulin Delivery store keeps track of the insulin delivered via scheduled basal. -Loop updates the amount of insulin delivered through basal (both scheduled and temporary) to Health at regular intervals - this does not happen every Loop Cycle when basal rates are not changing. The updates to Health happen: +*Loop* updates the amount of insulin delivered through basal (both scheduled and temporary) to Health at regular intervals - this does not happen every Loop Cycle when basal rates are not changing. The updates to Health happen: * At midnight * When the scheduled basal rate changes @@ -116,32 +117,60 @@ A simple example to illustrate this - for a pump with smallest insulin delivery |
Schedule |
Temp Basal (TB) |
Health | Explanation | |---|---|---|---| |12:00 AM
0.4 U/hr | --- | --- | Start of Day / Start of Example | -|06:00 AM
0.5 U/hr | --- | 06:00 AM
Basal
2.4 U | Loop reports insulin delivered by basal for the last 6 hours when the scheduled basal rate has a new entry | -|--- | 07:15 AM
0.0 U/hr | 07:15 AM
Basal
0.6 U | Loop reports insulin delivered by basal since last report up to time TB starts | +|06:00 AM
0.5 U/hr | --- | 06:00 AM
Basal
2.4 U | *Loop* reports insulin delivered by basal for the last 6 hours when the scheduled basal rate has a new entry | +|--- | 07:15 AM
0.0 U/hr | 07:15 AM
Basal
0.6 U | *Loop* reports insulin delivered by basal since last report up to time TB starts | |--- | 07:45 AM
TB expires | 07:45 AM
Basal
0 U | No insulin was delivered during TB | -|08:00 AM
0.4 U/hr | --- | 08:00 AM
Basal
0.1 U | Loop reports insulin delivered by basal since last report; the scheduled basal rate has a new entry| +|08:00 AM
0.4 U/hr | --- | 08:00 AM
Basal
0.1 U | *Loop* reports insulin delivered by basal since last report; the scheduled basal rate has a new entry| -### Tidepool and Apple HealthKit +### *Tidepool* and *Apple* HealthKit -If you have a [Tidepool](https://tidepool.org) account and use the Tidepool uploader on your Loop phone, the data in Health is uploaded to your Tidepool database where you can view displays with the [Tidepool web browser tool](https://loopkit.github.io/looptips/data/tidepool/). +If you have a [*Tidepool*](https://tidepool.org) account and use the *Tidepool* uploader on your *Loop* phone, the data in Health is uploaded to your *Tidepool* database where you can view displays with the [*Tidepool* web browser tool](https://loopkit.github.io/looptips/data/tidepool/). -## How Do I Modify Apple HealthKit Permissions +## How Do I Modify *Apple* HealthKit Permissions -You can review the Apple HealthKit permissions screen at any time. +### *Loop* Health Permissions -Simply open the Apple Health app (:heart: icon) +You can review and modify the *Apple* HealthKit permissions for the *Loop* app. + +Open the *Apple* Health app (:heart: icon) * Find the toolbar at the bottom that says Sharing * Scroll to the bottom of Sharing -* Select Apps -* Select Loop +* Select *Apps* +* Select *Loop* At this point, you can review and modify the settings. +### CGM Health Permissions + +If you choose to, you may add permission for your CGM app to write to *Apple* Health. *Loop* will read glucose from *Apple* Health, but only while the phone is unlocked and the app is open. + +Note that if a glucose value is added to *Apple* Health "now", *Loop* will pick up that value and use it for the glucose prediction. This can happen with a finger-stick entry or some Libre third-party apps, but not with Dexcom, which has a 3-hour delay before writing to Health. + +#### Dexcom + +The Dexcom app for both G6 and G7 has a 3-hour delay before writing to the Health app. If you tap Glucose data in Health, scroll to the bottom to select `Show All Data` and then scroll back in time, notice the `Loop` icon is replaced by either the `G6` or `G7` icon starting 3 hours ago. + +If you happen to wear a Dexcom G6 and G7 sensor at the same time, then starting 3 hours in the past, both sensor traces will show up in the `Loop Glucose chart`. + +*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. + +#### Libre + +There are several choices for reading Libre sensors. + +With `Loop dev` (will be `Loop 3.4.x` after release), [LibreTransmitter](https://github.com/dabear/LibreTransmitter#libretransmitter-for-loop) is integrated with the `Loop` app. + +The frequent updates (1-minute glucose data) provided by Libre did cause some issues with released versions (`Loop 3.x.x` with customizations that use various third-party apps to read the *Libre*). These were fixed initially by modifying the third-party apps to limit how frequently they supplied glucose data. + +With `Loop dev` (will be `Loop 3.4.x` after release), the Loop app only initiates a closed-loop cycle automatically following a new glucose value if it has been more than 4.2 minutes since the last one. + +`Loop 3.x.x` versions do not have that limitation on how frequently Loop responds to a new glucose reading. There is a [Customization](https://www.loopandlearn.org/custom-code/#loop-cycle-time) that incorporates the 4.2 minute interval check which can be applied to Loop 3.2.2. + ## How Do I Change Glucose Units? -The glucose units (mg/dL or mmol/L) Loop uses match what is in Apple Health. Once you connect a device that reports glucose to the phone, make sure the units match the device. Note - you can change units for Dexcom Share and it translates units for you - not sure about other devices. +The glucose units (mg/dL or mmol/L) *Loop* uses match what is in *Apple* Health. Once you connect a device that reports glucose to the phone, make sure the units match the device. Note - you can change units for Dexcom Share and it translates units for you - not sure about other devices. * These instructions to change Blood Glucose units are for iOS 15 * Select the Health app (Heart icon) From 265fa77bac6cc3d00ab18ca5267f26c0c34c7a4c Mon Sep 17 00:00:00 2001 From: marionbarker Date: Fri, 1 Sep 2023 17:19:18 -0700 Subject: [PATCH 3/6] Update info about when Loop removes Dexcom data from Health --- docs/faqs/apple-health-faqs.md | 5 +++++ docs/loop-3/add-cgm.md | 2 ++ 2 files changed, 7 insertions(+) diff --git a/docs/faqs/apple-health-faqs.md b/docs/faqs/apple-health-faqs.md index 16107ec461a..38fe393a94d 100644 --- a/docs/faqs/apple-health-faqs.md +++ b/docs/faqs/apple-health-faqs.md @@ -156,6 +156,11 @@ If you happen to wear a Dexcom G6 and G7 sensor at the same time, then starting *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 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 There are several choices for reading Libre sensors. diff --git a/docs/loop-3/add-cgm.md b/docs/loop-3/add-cgm.md index cfb0f62d318..27419876c47 100644 --- a/docs/loop-3/add-cgm.md +++ b/docs/loop-3/add-cgm.md @@ -92,6 +92,8 @@ Minimal documentation is provided. ![graphic showing Loop searching for G7](img/g7.svg){width="500"} {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. 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. ### Medtronic Enlite CGM From b906248da72f47779c651dd3025f369501acb583 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Fri, 1 Sep 2023 17:31:55 -0700 Subject: [PATCH 4/6] fix typos, add more do-not-translate indicators --- docs/faqs/apple-health-faqs.md | 30 ++++++++++++++---------------- docs/loop-3/add-cgm.md | 14 +++++++------- 2 files changed, 21 insertions(+), 23 deletions(-) diff --git a/docs/faqs/apple-health-faqs.md b/docs/faqs/apple-health-faqs.md index 38fe393a94d..eff38dacaff 100644 --- a/docs/faqs/apple-health-faqs.md +++ b/docs/faqs/apple-health-faqs.md @@ -36,16 +36,14 @@ The health app on the *Loop* phone provides useful plots of data since you start ### Glucose and *Apple* HealthKit -For Dexcom users with the Dexcom app on the *Loop* phone, the Dexcom app writes the value to Health with a 3-hour delay. +For *Dexcom* users with the *Dexcom* app on the *Loop* phone, the *Dexcom* app writes the value to Health with a 3-hour delay. -*Loop* reads the Dexcom information at the same time the Dexcom app gets the reading from the transmitter. It uses the glucose value to update predictions and stores it in Health. +*Loop* reads the *Dexcom* information at the same time the *Dexcom* app gets the reading from the transmitter. It uses the glucose value to update predictions and stores it in Health. -If you look at your Health glucose readings, you'll notice the *Loop* icon for the last 3 hours and the Dexcom icon for times earlier than that. +If you look at your Health glucose readings, you'll notice the *Loop* icon for the last 3 hours and the *Dexcom* icon for times earlier than that. All other CGM readings are reported with the *Loop* icon and there is no transition after 3 hours. -You may also notice that the Dexcom numbers get smoothed out. For example, the Dexcom readings, when they first are read from the transmitter may bounce up and down a bit. The Dexcom app will retrospectively smooth the numbers, changing what is displayed in their app compared to the original reading. The last 3 hours of data from *Loop* does not show that smoothing - it reports the value sent by the transmitter. If you suspect a sensor is not behaving well, check the *Loop* glucose plots compared to the Dexcom plots to assist in your evaluation. It might be time to confirm glucose with a fingerstick meter as well. - ### Carbohydrates and *Apple* HealthKit In `Loop* 2.2.x`, if you set *Apple* Health app permissions to allow it, *Loop* will read carbohydrates from the Health app. If you give a third-party app permission to store carbohydrate data in Health, and do not realize that *Loop* reads that information, you might get unexpected insulin delivery based off those carbs. To avoid that unanticipated behavior, the directions tell you to set permissions to allow *Loop* to write to carbohydrate storage but not read. @@ -146,36 +144,36 @@ At this point, you can review and modify the settings. If you choose to, you may add permission for your CGM app to write to *Apple* Health. *Loop* will read glucose from *Apple* Health, but only while the phone is unlocked and the app is open. -Note that if a glucose value is added to *Apple* Health "now", *Loop* will pick up that value and use it for the glucose prediction. This can happen with a finger-stick entry or some Libre third-party apps, but not with Dexcom, which has a 3-hour delay before writing to Health. +Note that if a glucose value is added to *Apple* Health "now", *Loop* will pick up that value and use it for the glucose prediction. This can happen with a finger-stick entry or some Libre third-party apps, but not with *Dexcom*, which has a 3-hour delay before writing to Health. -#### Dexcom +#### *Dexcom* -The Dexcom app for both G6 and G7 has a 3-hour delay before writing to the Health app. If you tap Glucose data in Health, scroll to the bottom to select `Show All Data` and then scroll back in time, notice the `Loop` icon is replaced by either the `G6` or `G7` icon starting 3 hours ago. +The *Dexcom* app for both G6 and G7 has a 3-hour delay before writing to the Health app. If you tap Glucose data in Health, scroll to the bottom to select `Show All Data` and then scroll back in time, notice the `Loop` icon is replaced by either the `G6` or `G7` icon starting 3 hours ago. -If you happen to wear a Dexcom G6 and G7 sensor at the same time, then starting 3 hours in the past, both sensor traces will show up in the `Loop Glucose chart`. +If you happen to wear a *Dexcom* G6 and G7 sensor at the same time, then starting 3 hours in the past, both sensor traces will show up in the `Loop Glucose chart`. *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. +!!! 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 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 +#### *Libre* -There are several choices for reading Libre sensors. +There are several choices for reading *Libre* sensors. With `Loop dev` (will be `Loop 3.4.x` after release), [LibreTransmitter](https://github.com/dabear/LibreTransmitter#libretransmitter-for-loop) is integrated with the `Loop` app. -The frequent updates (1-minute glucose data) provided by Libre did cause some issues with released versions (`Loop 3.x.x` with customizations that use various third-party apps to read the *Libre*). These were fixed initially by modifying the third-party apps to limit how frequently they supplied glucose data. +The frequent updates (1-minute glucose data) provided by *Libre* did cause some issues with released versions (`Loop 3.0` and `Loop 3.2.x` with customizations that use various third-party apps to read the *Libre*). These were fixed initially by modifying the third-party apps to limit how frequently they supplied glucose data. With `Loop dev` (will be `Loop 3.4.x` after release), the Loop app only initiates a closed-loop cycle automatically following a new glucose value if it has been more than 4.2 minutes since the last one. -`Loop 3.x.x` versions do not have that limitation on how frequently Loop responds to a new glucose reading. There is a [Customization](https://www.loopandlearn.org/custom-code/#loop-cycle-time) that incorporates the 4.2 minute interval check which can be applied to Loop 3.2.2. +`Loop 3.0` and `Loop 3.2.x` versions do not have that limitation on how frequently Loop responds to a new glucose reading. There is a [Customization](https://www.loopandlearn.org/custom-code/#loop-cycle-time) that incorporates the 4.2 minute interval check which can be applied to Loop 3.2.2. ## How Do I Change Glucose Units? -The glucose units (mg/dL or mmol/L) *Loop* uses match what is in *Apple* Health. Once you connect a device that reports glucose to the phone, make sure the units match the device. Note - you can change units for Dexcom Share and it translates units for you - not sure about other devices. +The glucose units (mg/dL or mmol/L) *Loop* uses match what is in *Apple* Health. Once you connect a device that reports glucose to the phone, make sure the units match the device. Note - you can change units for *Dexcom* Share and it translates units for you - not sure about other devices. * These instructions to change Blood Glucose units are for iOS 15 * Select the Health app (Heart icon) diff --git a/docs/loop-3/add-cgm.md b/docs/loop-3/add-cgm.md index 27419876c47..85aa0d114e8 100644 --- a/docs/loop-3/add-cgm.md +++ b/docs/loop-3/add-cgm.md @@ -21,7 +21,7 @@ Loop can be connected to the following CGMs: * Only some Libre sensors are supported; some have encryption that limits DIY use * No details for using Libre will show up on this page until the next release - please read [Build Loop-dev](../version/build-dev.md) and follow the links to understand what you are doing if you choose a development branch * CGMs that require active internet (WiFi or Cell) - * [Dexcom Share](#dexcom-share-as-a-cgm) + * [*Dexcom Share*](#dexcom-share-as-a-cgm) * [Nightscout Remote CGM](#nightscout-remote-cgm) * CGM Simulator - useful to learn the app interface @@ -77,7 +77,7 @@ You can find the **transmitter ID** in your Dexcom G6 app or on the back of the The Dexcom G7 is handled differently - Loop automatically detects when a new sensor/transmitter pair is added to the Dexcom G7 app. -#### About Dexcom Share credentials +#### About *Dexcom Share* credentials You do **NOT** need your Share account info listed in Loop settings if you are using a G5 or G6 system. The transmitter ID is sufficient. In fact, you should leave your Share credentials blank so that you don't accidentally become internet-dependent for CGM data if you forget to update your transmitter ID when you start a new transmitter. @@ -93,7 +93,7 @@ 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. 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*. 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. ### Medtronic Enlite CGM @@ -103,15 +103,15 @@ The Medtronic Enlite CGM is only available if you have connected it to your comp * Go through the [Add Pump](add-pump.md) to Loop steps with that Medtronic pump * Then do the [Add CGM](add-cgm.md) steps and the sensor should be presented as an option -### Dexcom Share as a CGM +### *Dexcom Share* as a CGM -!!! warning "If you need to use Dexcom Share" +!!! warning "If you need to use *Dexcom Share*" If the dexcom is on another phone, you can use Share if internet / cell coverage is good. - Dexcom Share is not available for Dexcom ONE CGM. + *Dexcom Share* is not available for Dexcom ONE CGM. - The Dexcom Share credentials (in other words, account login) is the same as what you used to log in to the active Dexcom app on your iPhone. **Dexcom Share account is not always the same login info as your Dexcom Clarity account.** The information is entered when you first log in to the app and then is never displayed again, nor visible under any information screens. If you have forgotten your G5/G6 account info, you can delete the Dexcom app and redownload it to try logging in again. This will not cause a restart of any sensor sessions in progress. + The *Dexcom Share* credentials (in other words, account login) is the same as what you used to log in to the active Dexcom app on your iPhone. ***Dexcom Share* account is not always the same login info as your Dexcom Clarity account.** The information is entered when you first log in to the app and then is never displayed again, nor visible under any information screens. If you have forgotten your G5/G6 account info, you can delete the Dexcom app and redownload it to try logging in again. This will not cause a restart of any sensor sessions in progress. If you do not enter your Share credentials correctly into Loop, you will get an error when Loop tries to access your Share account to backfill CGM data. An example of the error message is shown in the graphic below. If you see that message, delete your Share account from Loop settings and try again. From 797a1dd8e5d02b77e31507d1b3f390be3aed3353 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Fri, 1 Sep 2023 17:33:52 -0700 Subject: [PATCH 5/6] include pump in max basal rate --- docs/loop-3/therapy-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/loop-3/therapy-settings.md b/docs/loop-3/therapy-settings.md index 2d82e186cf3..e4abaec5803 100644 --- a/docs/loop-3/therapy-settings.md +++ b/docs/loop-3/therapy-settings.md @@ -262,7 +262,7 @@ The font color in the value picker has the following meaning: * Recommended maximum value available on the picker is 6.4 times the highest basal rate in your scheduled basal rates * Values higher than this, if available, are shown in yellow -* Absolute maximum value is 70 divided by the smallest carb ratio (CR) in your schedule +* Absolute maximum value is 70 divided by the smallest carb ratio (CR) in your schedule or the maximum allowed rate by your pump, whichever is higher * Depending on your basal rate and CR schedules, the maximum value available on the picker might be more that 6.4 times the highest basal rate #### Guardrails for Maximum Bolus From 870421448a7e107112149247be036404b8971d79 Mon Sep 17 00:00:00 2001 From: marionbarker Date: Fri, 1 Sep 2023 17:35:05 -0700 Subject: [PATCH 6/6] typo fix --- docs/loop-3/therapy-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/loop-3/therapy-settings.md b/docs/loop-3/therapy-settings.md index e4abaec5803..c5a03a93d2d 100644 --- a/docs/loop-3/therapy-settings.md +++ b/docs/loop-3/therapy-settings.md @@ -262,7 +262,7 @@ The font color in the value picker has the following meaning: * Recommended maximum value available on the picker is 6.4 times the highest basal rate in your scheduled basal rates * Values higher than this, if available, are shown in yellow -* Absolute maximum value is 70 divided by the smallest carb ratio (CR) in your schedule or the maximum allowed rate by your pump, whichever is higher +* Absolute maximum value is 70 divided by the smallest carb ratio (CR) in your schedule or the maximum rate allowed by your pump, whichever is higher * Depending on your basal rate and CR schedules, the maximum value available on the picker might be more that 6.4 times the highest basal rate #### Guardrails for Maximum Bolus