diff --git a/docs/data/health.md b/docs/data/health.md index 62f5906..3b8eacb 100644 --- a/docs/data/health.md +++ b/docs/data/health.md @@ -12,26 +12,40 @@ There's often confusion over the terminology surrounding Apple's health data sto * **Health App** -- Apple allows iOS users to manage HealthKit permissions and view stored HealthKit data through the use of Apple's Health app (standard on iPhones and iPods, but not available on iPads). ## Loop's use of HealthKit -When you first install Loop onto your iPhone, you will be asked to setup Loop's access to the HealthKit database. Loop uses the iPhone's HealthKit to read and write blood glucose, insulin, and carbohydrate data depending on how you initially setup this section. -At a minimum, you will need these HealthKit settings: +!!! info "Loop and HealthKit" + Older versions of Loop, before version 3.0 was released, required the use of *Apple* Health for data storage older than 3 hours. This is no longer true. -*Loop* + Loop version 3.x uses internal core storage of 7 days of data independent of *Apple* Health. -* insulin data: read and write -* carbohydrate data: read and write -* blood glucose data: read and write +When you first install Loop onto your iPhone, you will be asked to setup Loop's access to the HealthKit database. It is recommended that you enable iPhone's HealthKit for these interfaces -*Dexcom* App +*Loop* App -* blood glucose data: write (if you have this disabled, *Loop* will still function but will not display blood glucose values older than 3 hours old) +* write to: + * Blood Glucose, Carbohydrate and Insulin Delivery +* read from: + * Blood Glucose, Insulin Delivery and Sleep -You can always check your HealthKit settings by opening the Health App, clicking on *Sources* at the bottom bar, and then clicking on the app's name you are interested in, for example, Loop. +*CGM* App -![Health App](img/healthapp.jpg){width="350"} -{align="center"} +There are a number of *CGM* apps. If the option is available, configure them with these permissions: + +* write to: + * Blood Glucose + +Depending on the app, there may be other items you want to have the app read from *Apple* Health. That depends on the CGM. + +!!! warning "*Dexcom* CGM" + If you use one of the *Dexcom* Apps, enable it to write Blood Glucose to Apple Health. + + If that is not enabled, *Loop* will still function but it will not display blood glucose values older than 3 hours old. + +You can always check your HealthKit settings by opening the Health App, clicking on *Sharing* at the bottom bar, scroll down and tap on the row labeled **Apps** and then clicking on the app's name you are interested in, for example, Loop. + +Potential conflicts can arise when third-party apps are granted access to HealthKit permissions that may interfere with Loop's specified data permissions. -Potential conflicts can arise when third-party apps are granted access to HealthKit permissions that may interfere with Loop's specified data permissions. For example, carbohydrate data is stored in *Nightscout* and Spike for some users...you wouldn't want to enable *Spike* app to write duplicate carbohydrate entries that Loop would be reading. Therefore, you should disable other apps from writing carbohydrate data to HealthKit so that Loop does not read those other entries unintentionally. Also, good practice, because carbohydrate entries in HealthKit that were created by non-Loop apps will not be able to customize carbohydrate absorption times nor be edited later if needed. +With Loop 3, it is no longer the default that the *Loop* app reads carbohydrate from Apple Health. This prevents a problem that used to happen where third-party food apps were used to record meals. You can customize your *Loop* app to change this setting, but be aware that carbohydrate entries in HealthKit that were created by non-Loop apps will not be able to customize carbohydrate absorption times nor be edited later if needed. Refer to [LoopDocs: Carbohydrates and Apple HealthKit](https://loopkit.github.io/loopdocs/faqs/apple-health-faqs/#carbohydrates-and-apple-healthkit){: target="_blank"}. ## Your use of Health App diff --git a/docs/data/img/healthapp.jpg b/docs/data/img/healthapp.jpg deleted file mode 100644 index 998ecc2..0000000 Binary files a/docs/data/img/healthapp.jpg and /dev/null differ diff --git a/docs/data/img/tidepool-basal-3-views.png b/docs/data/img/tidepool-basal-3-views.png new file mode 100644 index 0000000..4e3115d Binary files /dev/null and b/docs/data/img/tidepool-basal-3-views.png differ diff --git a/docs/data/img/tidepool-hover-automatic-bolus.png b/docs/data/img/tidepool-hover-automatic-bolus.png new file mode 100644 index 0000000..dcded33 Binary files /dev/null and b/docs/data/img/tidepool-hover-automatic-bolus.png differ diff --git a/docs/data/img/tidepool-hover-meal-postmeal.png b/docs/data/img/tidepool-hover-meal-postmeal.png new file mode 100644 index 0000000..051568e Binary files /dev/null and b/docs/data/img/tidepool-hover-meal-postmeal.png differ diff --git a/docs/data/img/tidepool-therapy-settings.svg b/docs/data/img/tidepool-therapy-settings.svg new file mode 100644 index 0000000..1392627 --- /dev/null +++ b/docs/data/img/tidepool-therapy-settings.svg @@ -0,0 +1,1904 @@ + +image/svg+xmlTidepool does not yet handle Insulin Type.Insulin Type is what Loop uses for forecast.Ignore the Insulin Model reported here(unless you customized Loop) diff --git a/docs/data/nightscout.md b/docs/data/nightscout.md index 7a7fa1b..9dff6fe 100644 --- a/docs/data/nightscout.md +++ b/docs/data/nightscout.md @@ -1,6 +1,6 @@ # Nightscout {: translate="no" } -[Nightscout](https://nightscout.github.io/){: target="_blank" } (NS) is a cornerstone of the DIY type 1 community. It is an excellent tool to remotely view Loop's actions and access insulin and blood glucose data. It allows for easy remote monitoring of *Loop* activities, troubleshooting of *Loop* errors, history of CGM, carbs, boluses, & temporary basal rates, and reports to analyze data trends and patterns. There is a *Nightscout* app in your iPhone App Store, or you can use a web browser to view the data. [Setting up Nightscout for Loop](https://loopkit.github.io/loopdocs/nightscout/new_user/){: target="_blank" } is free and fairly quick. Once set up, the site can be accessed by anyone that you share your unique *Nightscout* URL with. +[Nightscout](https://nightscout.github.io/){: target="_blank" } (NS) is a cornerstone of the DIY type 1 community. It is an excellent tool to remotely view Loop's actions and access insulin and blood glucose data. It allows for easy remote monitoring of *Loop* activities, troubleshooting of *Loop* errors, history of CGM, carbs, boluses, & temporary basal rates, and reports to analyze data trends and patterns. There is a *Nightscout* app in your iPhone App Store, or you can use a web browser to view the data. [Setting up Nightscout for Loop](https://loopkit.github.io/loopdocs/nightscout/new_user/){: target="_blank" } is low cost and fairly quick. Once set up, the site can be accessed by anyone that you share your unique *Nightscout* URL with. ## Nightscout Display *Nightscout* is highly recommended for *Loop* users, especially those using *Loop* as caregivers. *Nightscout* displays are often the easiest way to troubleshoot *Loop* settings if you are having problems and seeking input from others. Below is some discussion about the general *Nightscout* display, as well as some Loop-specific display information. @@ -22,11 +22,13 @@ Insulin boluses are also automatically uploaded to NS by the *Loop* app. The bol ### Temporary Basal Rates -Within your NS profile, you will enter in the scheduled basal rates from your *Loop* settings. This is not automatically updated when you update the *Loop* app; you will have to manually update your basal profile in your NS site if you change your basal profile in *Loop*. If you don't update the NS basal profile, it doesn't cause any problems in *Loop* function...you simply won't have an accurate VISUAL representation of high/low temporary basal rates within NS. The dashed blue line represents the scheduled basal profile (as entered in your NS profile). The solid blue lines indicate the actual basal amounts set for a given time...so as *Loop* sets temporary basal rates higher or lower than your scheduled basal rate, the solid blue line will jump above or below your dashed blue line. There is a slight delay (up to 2-5 minutes) in the rendering of basal changes on the blue lines, so if you want the accurate current basal rate, you should check the *Loop* pill. +Within your [NS profile](https://nightscout.github.io/nightscout/profile_editor/){: target="_blank" } , you can see in the scheduled basal rates from your *Loop* settings. Your *Loop* Therapy Settings profile is stored in your Nightscout site as the Default profile. Nightscout allows the user to have named profiles, but when used with Loop, the current profile is always called "Default" and it is uploaded from the *Loop* app. Fun Fact: your saved Override Presets are uploaded and saved in your Nighscout database and can be downloaded if you later need to start over with a brand-new *Loop* app. Refer to [LoopDocs: Onboarding](https://loopkit.github.io/loopdocs/loop-3/onboarding/#connect-loop-to-nightscout){: target="_blank" }. + +The dashed blue line represents the scheduled basal profile (as entered in your NS profile). The solid blue lines indicate the actual basal amounts set for a given time...so as *Loop* sets temporary basal rates higher or lower than your scheduled basal rate, the solid blue line will jump above or below your dashed blue line. There can be a slight delay (up to 2-5 minutes) in the rendering of basal changes on the blue lines, so if you want the accurate current basal rate, you should check the *Loop* pill. ### Predicted Blood Glucose -The purple line to the right of the blood glucose readings is Loop's predicted blood glucose curve. Watching the behavior of that purple line can help you understand why *Loop* is making decisions regarding high or low temporary basal rates. You can read more on that topic in the [Algorithm](https://loopkit.github.io/loopdocs/operation/algorithm/temp-basal){: target="_blank" } section of *LoopDocs*. +The purple line to the right of the blood glucose readings is Loop's forecasted blood glucose curve. Watching the behavior of that purple line can help you understand why *Loop* is making decisions regarding high or low temporary basal rates. You can read more on that topic in the [Algorithm](https://loopkit.github.io/loopdocs/operation/algorithm/temp-basal){: target="_blank" } section of *LoopDocs*. ### L​oop pill diff --git a/docs/data/overview.md b/docs/data/overview.md index fc30786..0dd5152 100644 --- a/docs/data/overview.md +++ b/docs/data/overview.md @@ -3,22 +3,17 @@ In order to assess your Loop's performance and more specifically your settings, having access to your historical data trends is invaluable. Seeing what your Loop was predicting, what actions were being taken, how blood glucose was reacting, and how insulin needs have been changing is critical when trying to assess any settings changes. ## Problem with traditional methods -As a person with diabetes, you’re probably carrying around a lot of different devices that are holding a lot of different data; a blood glucose meter for your finger sticks, a pump for insulin delivery, a continuous glucose monitor for real-time glucose measurements, phone app for tracking meals, etc. When you go to your endocrinology office, you probably start the process by dropping many of those devices at the front desk to be individually downloaded and then having to pack all of them away 20 minutes later. -Then your clinic staff has the less-than-efficient process of trying to overlay all those different devices into some sort of cohesive strategy for how your diabetes may need some tweaks. Because of Loop use, a clinic currently has to look at separate reports from Medtronic pump, Contour Next Link BG meter, Dexcom CGM/Clarity, and our iPhone Health app, as a typical example. There are also a couple of issues with Loop when using this separate download method: +When you go to your endocrinology office, they need to have a method to view all your Automated Insulin Delivery system data in one place. -* Medtronic’s pump gets so clogged up by the numerous temporary basal rate records being recorded that the clinic can only pull about 7 days of data from the pump at most. +* If you use an Omnipod Eros or DASH pump - there is no PDM for your clinic to read insulin dosing records +* If you use a Medtronic pump, the memory is full of the many commands sent from Loop -* Clinic basically lacks an overlay of basal rate/bolus actions with blood glucose from Dexcom, which really limits their ability to recommend any settings changes. +## Available solutions for DIY apps -* DIY solutions could fill some of the gaps as far as overall management, but the problem was with the actual gathering of the reports. It’s a little hard for the clinic to bring up reports live time, and sometimes remembering to print them out ahead of time just doesn't happen. - -* Manual notes the various tools are not the most streamlined experience (especially for young kids and teens to manage). This inefficiency can lead to people neglecting to note times of site failure or compression lows, for example. If the health care provider wants additional information about a particular blood glucose event(s), chances are good that there would be no notations to help explain the event without effort. If there was a note, it may be in *Nightscout*, *Dexcom*, or in text messages between caregivers...not really centralized and integrated. - -## Available solutions The good news is that the community has some very useful tools to help address the shortcomings in the traditional data aggregation for Loop users. There are several tools available to help you and/or your endocrinologist evaluate your Loop data. Specifically, this section covers: -* Health app +* *Apple* Health app * *Nightscout* * *Tidepool* * *Perceptus* diff --git a/docs/data/tidepool.md b/docs/data/tidepool.md index 4a3fae0..fd5a5e8 100644 --- a/docs/data/tidepool.md +++ b/docs/data/tidepool.md @@ -12,10 +12,8 @@ In Tidepool's own words, their commitment to diabetes data and accessibility We believe that connected data leads to better decision-making. Tidepool's free software liberates data from diabetes devices, and places it in context of the real world. Tidepool is designed to help you discover insights and bring context to your diabetes management. And, to help make your data more actionable, we allow you to share your data with anyone you choose: caregivers, clinicians, endocrinologists, friends, researchers – anyone. -*Tidepool* has [announced](https://tidepool.org/loop/){: target="_blank" } that they are embarking on a project to build and support an FDA-regulated version of *Loop*, to be available in the iOS App Store, intended to work with commercially available insulin pumps and CGMs. - ## Tidepool  Data -Once you start uploading data into your *Tidepool* account, you'll see some of the benefits pretty quickly. Tidepool's data presentation is easy on the eyes. Lots of calm colors, logical data layout, quick to access important information...basically a breeze to get your needed data and get on with your analysis. +Once you start uploading data into your [*Tidepool* account](https://www.tidepool.org/){: target="_blank" }, you'll see some of the benefits pretty quickly. Tidepool's data presentation is easy on the eyes. Lots of calm colors, logical data layout, quick to access important information...basically a breeze to get your needed data and get on with your analysis. ![Tidepool Sample](img/tidepool_sample.png){width="750"} @@ -23,50 +21,58 @@ Once you start uploading data into your *Tidepool* account, you'll see some of t To use Tidepool's services, the process is pretty standard: -* Create a free *Tidepool* account to become the warehouse for your diabetes data. -* Upload device data to your account. - -Children with type 1 diabetes can have their own data account, and parents can have a caregiver account. Users can also choose to share data with their endocrinology clinic. You can also choose to share your diabetes data anonymously for the support of type 1 diabetes researchers if desired. +* Create a free [*Tidepool* account](https://www.tidepool.org/){: target="_blank" } if you don't already have one +* In the *Loop* app, go to Settings, Services and tap on the + sign to add a service + * Choose *Tidepool* and log into your *Tidepool* account + * As soon as you do this, *Loop* will upload the last 7 days of data to Tidepool -### How do you upload data into Tidepool account? +If both you and someone that you provide care for has diabetes, you should set up an account for each person. Refer to the [Tidepool Docs](https://support.tidepool.org/hc/en-us/articles/360038567672-What-To-Do-If-You-and-Your-Child-Have-Diabetes){: target="_blank" }. -There are two methods for uploading different data to your *Tidepool* account: +Users can also choose to share data with their endocrinology clinic. You can also choose to share your diabetes data anonymously for the support of type 1 diabetes researchers if desired. -* **Tidepool Uploader** (program on your computer) - *Tidepool* Uploader supports a large variety of current diabetes devices in the market; Animas, T-slim, Medtronic, Omnipod, Dexcom, and more. The full list of devices is [here](https://tidepool.org/products/tidepool-uploader/#devices){: target="_blank" }. To upload the data from these devices, you download the free *Tidepool* Uploader program, connect your device to the computer according to the instructions provided in the Uploader, and your data is then securely uploaded and stored in your *Tidepool* account. Most users will perform uploads on a semi-regular basis; weekly, monthly, or prior to each clinic visit. +### How do you upload data into Tidepool account? -* **Tidepool Mobile** (app on your phone) - *Tidepool* Mobile is available for both Android and iOS/iPhone users. *Tidepool* Mobile is a companion app to *Tidepool* that lets you add notes about meals, exercise, or anything else. See your CGM, pump, and meter data alongside any notes you add. Track your favorite meals and your regular exercise, and learn from what happens. +Follow these directions to upload Automated Insulin Delivery data from *Loop* to your *Tidepool* account: -!!! abstract " " +* **Tidepool Uploader** + * There are a lot of uploaders, but we assume you are using the *Loop* app + * In Loop, Settings, Add Service and log into your *Tidepool* account - In summary, the **Uploader** is for uploading the numeric data from your various diabetes devices, and the **Mobile app** is for adding contextual information and notes-on-the-go to make your numeric data more useful. +* **Tidepool Mobile** (app on your phone) + * This companion app is optional but many people use it to take notes + * *Tidepool* Mobile is available for both Android and iOS/iPhone users. *Tidepool* Mobile is a companion app to *Tidepool* that lets you add notes about meals, exercise, or anything else. You can see your CGM, pump, and meter data alongside any notes you add. Track your favorite meals and your regular exercise, and learn from what happens. These notes are uploaded to the *Tidepool* web display so you can view those same notes in either location. -### Does Tidepool Uploader work for Loop users? -There has been a lack of ability to get Loop data into *Tidepool* using the *Tidepool* Uploader. The only pumps compatible with *Loop* and supported in *Tidepool* Uploader are the x23/x54 pumps, so users of the x15 and x22 pumps cannot upload their pump data. Furthermore, the Medtronic pump still suffers from the lack of internal storage sufficient to store more than 3-7 days' worth of Looping data. +!!! abstract "**Tidepool Mobile** and *Loop*" -However, there has been a very exciting development! Tidepool's Mobile iOS app has been updated to upload Apple's HealthKit data into *Tidepool*. Since *Loop* uses *HealthKit* to store all of your insulin, carbohydrate, and CGM data, this means *Tidepool* can now upload the full suite of available *Loop* information. So, there's no need to use *Tidepool* Uploader for *Loop* users...their *Tidepool* Mobile app can take care of the needed connections. Read below for lots of details about this important development. + * Adding *Tidepool* service to Loop uploads data from your Automated Insulin Delivery system to the *Tidepool* web display + * This initial upload includes the full 7-day history stored in the *Loop* app + * The companion app, *Tidepool Mobile* is for adding contextual information and notes-on-the-go to make your stored data more useful + * Be sure to [disable Apple Health access for the *Tidepool Mobile* app](https://loopkit.github.io/loopdocs/loop-3/services/#tidepool) when using the *Loop* *Tidepool* service to avoid duplicate uploads + * If you have duplicate uploads from *Loop* and *Tidepool Mobile*, you can apply a filter to show only one on the web display ### How can I share my Tidepool data? -Sharing the data is simple. You can click on your account’s Share option and enter in the email addresses for those that you want to share with. Those people will need a *Tidepool* account. If they don’t have one currently, they will follow easy prompts for an account setup after they’ve received your share invitation. Clinics using *Tidepool* will have a *Tidepool* account email that you can add to your account, enabling the clinic to easily view your data. You can also remove access for anyone with a simple click. +Sharing the data is simple. You can click on your account’s Share option and enter in the email addresses for those that you want to share with. Those people will need a *Tidepool* account. If they don’t have one currently, they will follow easy prompts for an account setup after they’ve received your share invitation. Clinics using *Tidepool* will have a *Tidepool* account email that you can add to your account, enabling the clinic to easily view your data. You can also remove access for anyone with a simple click. ![Share Tidepool](img/share_tidepool.png){width="550"} {align="center"} -## Viewing your Tidepool data +## View your Tidepool data -There are two distinct viewing options for your *Tidepool* data, and they are not identical. You can either view your data: +There are two distinct viewing options for your *Tidepool* data, and they are not identical. You can use both view your data: -1. Using a desktop computer using the Chrome browser and logging into your *Tidepool* account, or -2. Using your *Tidepool* Mobile app **AND** associated notes. +1. Using a [desktop computer](#view-your-loop-data-using-tidepool-browser) using the Chrome or Edge browser and logging into your *Tidepool* account, or +2. Using your [*Tidepool* Mobile app **AND** associated notes](#view-your-loop-data-using-tidepool-mobile-app). !!! info "Supported Desktop Browser" - Currently, only the Chrome desktop browser is compatible with *Tidepool*. You will not be able to use Safari or other browsers to view the data, nor will you be able to use the Chrome application on a phone. If you want to see your data on a computer, you need to use the Chrome browser. + Currently, only the Chrome or Edge desktop browser is compatible with *Tidepool*. You will not be able to use Safari or other browsers to view the data, nor will you be able to use the Chrome application on a phone. If you want to see your data on a computer, you need to use the Chrome or Edge browser. - !!! info "Viewing Data on your Phone" + !!! info "View Data on your Phone" If you want to see your data on your phone, you must use the *Tidepool* Mobile app **and** use an associated note to view the data surrounding the note's time frame. Mobile data viewing is not a live stream, but rather available as "bookmarked" time periods anchored by notes. -### What Loop data will you see in desktop Chrome? -You will see your Loop's temporary basals, CGM readings, boluses, notes, carbohydrates, and various metrics about your data distribution. If you separately load your blood glucose meter or any other supported device to *Tidepool*, those will also overlay. +## View your *Loop* data using *Tidepool* Browser? + +You will see your Loop's temporary basals, CGM readings, boluses, notes, carbohydrates, and various metrics about your data distribution. If you separately load your blood glucose meter or any other supported device to *Tidepool*, those will also overlay. You can choose to upload some CGM data from the *Loop* app. There is a feature in *Loop* for a given CGM to enable *Upload Readings*. This feature is disabled by default. ![Loop in Tidepool](img/loop_in_tidepool.png){width="750"} {align="center"} @@ -77,7 +83,45 @@ You will see your Loop's temporary basals, CGM readings, boluses, notes, car ![Loop in Tidepool 3](img/loop_in_tidepool3.png){width="750"} {align="center"} -### What Loop data will you see in the Tidepool Mobile app? +### Updates to *Tidepool* Browser + +!!! tips "*Tidepool* Updates" + The *Tidepool* browser has some recent (2024) enhancements. + + These require you to use the *Loop* *Tidepool* service uploader to have access to this information + +### View Manual and Automated Details + +If you hover over an item on the *Tidepool* web display, information is revealed indicating + +* automatic (the word Automated is included) or manual (no notation) + + ![automatic bolus](img/tidepool-hover-automatic-bolus.png) + +* details about a manual bolus: + * the recommended value with notation if this recommendation was modified (override or underride) + * if this was a meal entry: Carbs and IC (insulin to carb ratio, called CR in Loop) are shown + * in all manual bolus, the Glucose, IOB, ISF and correction target range are shown + * in the graphic below, the left image is from meal entry and the right from a bolus added after the meal + + ![meal entry details](img/tidepool-hover-meal-postmeal.png) + +* information about manual or automatic temp basal (TB) rates + * the graphic below shows 3 views of a full day of basal rates + * top is without hovering + * middle: cursor hovers over an automatic TB + * bottom hovers over a manual TB + + ![automatic and manual temp basal](img/tidepool-basal-3-views.png) + +## View your Therapy History + +Tap on the Device Settings icon to see your historical therapy settings. You can select your history (after March 2023) by date when you use the *Tidepool Service* uploader associated wtih *Loop* version 3 or later. If you tap on *Copy as Text*, you can paste a nice version into a document. + +![therapy setting history](img/tidepool-therapy-settings.svg) + + +## View your *Loop* data using *Tidepool Mobile* app? !!! info " " The *Tidepool* Mobile app is not a live-viewing app for looping data. For people coming from *Nightscout*, this may be a bit confusing but realize the intended purpose of the *Tidepool* Mobile app isn’t live-viewing. It is the place where you can (1) upload/sync *HealthKit* data, (2) easily add/edit/delete notes to the data set, and (3) search for notes and view *Loop* data surrounding that note. @@ -89,18 +133,6 @@ For example, here’s a sample note+data set below from my *Tidepool* Mobile app ![iOS Tidepool Example](img/ios_tidepool_example.png){width="250"} {align="center"} -## Tidepool's Mobile app for iOS/iPhone -As part of *Tidepool* *Loop* development, *Tidepool* updated its *Tidepool* Mobile iOS app to integrate with *Loop* user's data stored in Apple's HealthKit database. This update also supports the [Jaeb Center observational study](https://www.jaeb.org/projects/){: target="_blank" } of Loop. - -### How does the Loop data upload work? -The *Tidepool* Mobile iOS app will sync Loop's diabetes-related HealthKit data into your *Tidepool* account. The app will continuously upload that data so long as the *Tidepool* Mobile app is open, even if it is only open in the background. That data will then be viewable in two places: on the *Tidepool* Mobile app itself when using notes, or in your *Tidepool* account using the desktop Chrome browser (note: the two options are not identical viewing platforms, see discussion above). This means you will not have to plug any of your devices into a USB cable in order to upload your information to *Tidepool*. - -### Is the Tidepool Mobile app a replacement for Nightscout? -Nope. This was not designed nor intended to be a replacement for your *Nightscout* site. They complement each other, rather than compete. This new upload of Loop data will allow you and your clinics to have a powerful tool to analyze Loop data through an easy-to-use, shared hub. - -### Are there any known issues with Loop and Tidepool Mobile app? -The settings for *Loop* do not show up in `Device Settings` in *Tidepool Web*. This is because this info can't be uploaded from Apple Health. If you used *Tidepool* Web for your Medtronic or Omnipod before, you will still see the pump settings from before you started looping. - ### What cool thing can you use this Tidepool Mobile app for? You mean, what OTHER cool thing can the *Tidepool* Mobile application do besides automatically uploading the data from *Loop*? Tidepool Mobile also provides an easily searchable log of meal boluses. If you are still learning new meals in Loop…how much to bolus, how long of a carb absorption…these notes are searchable and super easy to add. Learning how to bolus for that Tofu Breakfast Burrito? Simply record a note of how you bolused for it. If you want to, come back afterwards and leave yourself some suggestions for the next time to try. This searchable information can also help teens learn and exercise independent skills. If they aren’t sure of how to bolus for a meal, this could give them easy tips from past success without necessarily having to stop and ask a parent. As much as a parent might scoff at the idea of a kid looking up a meal, if the alternative is asking a parent…that might be all the motivation it takes. How about co-parenting? Want to leave a note that another parent or caregiver can look up? *"How were the last Chicken McNuggets bolused?"* or *"When was the last site change?"* can easily be tracked and retrieved with notes. @@ -111,8 +143,6 @@ For an easy example, search for the word burrito (doesn’t have to be a hashtag Hormones can also be easily tracked with notes. *What day-of-the-month and how did I change the basals?* Looking to find patterns in those female hormones? This could be a really slick tracking tool to easily log periods of insulin resistance and what part of the cycle they are occurring at. -### Is the Tidepool Mobile app only for Loop users? -The *Tidepool Mobile* application uploads diabetes-related HealthKit data regardless of the source. Loop users store their data in HealthKit, so this is a nice fit. Other diabetes devices (e.g., OneDrop BG meter) and apps (e.g., Spike and Dexcom) also store their data in HealthKit. Some people even manually enter their diabetes data into HealthKit. For all those uses, the *Tidepool Mobile* application will upload the HealthKit data. OpenAPS does not store its data in HealthKit, so this will not upload OpenAPS-related data. However, if OpenAPS users are using Spike app, some integration of information through Nightscout is possible. Currently, OpenAPS SMBs, boluses, and carbohydrates can be uploaded to HealthKit for OpenAPS+Spike+Nightscout+iPhone users. Spike does plan to add temporary basal integration to HealthKit at some time in the future. - ### How can you get the Tidepool Mobile app? + *Tidepool Mobile* is available in the [iOS App Store](https://apps.apple.com/us/app/tidepool-mobile/id1026395200){: target="_blank" } on your Loop device. diff --git a/docs/how-to/exercise.md b/docs/how-to/exercise.md index b0395a8..578b781 100644 --- a/docs/how-to/exercise.md +++ b/docs/how-to/exercise.md @@ -39,7 +39,7 @@ Glucose levels during sports affect performance in many ways: strength, stamina, **Balancing Act: Finding your blood glucose zone and peak fitness zone** -Caution: Delayed Onset Hypoglycemia can occur typically 6 to 12 hours (sometimes 24 hours) after exhaustive exercise, due to replenishment of muscle glycogen stores and enhances insulin sensitivity. It is possible to prevent this by: +Caution: Delayed Onset Hypoglycemia can occur 6 to 12 hours (sometimes 24 hours) after exhaustive exercise, due to replenishment of muscle glycogen stores and enhanced insulin sensitivity. It is possible to prevent this by: * keeping records of your fitness regimen and the effects it has on your body * using a CGM or frequent blood testing to monitor your body’s response to activity diff --git a/docs/how-to/iob.md b/docs/how-to/iob.md index 685f173..bbd7ae5 100644 --- a/docs/how-to/iob.md +++ b/docs/how-to/iob.md @@ -8,7 +8,7 @@ This Looped group post started the conversation: *I've been having more lows recently than I would like. Any help here would be really really appreciated.* - *I took a screenshot of an example situation...LOOP is predicting that I'll eventually rise up to 124 and is therefore giving me my full regular basal rate EVEN THOUGH im currently way below my desired goal range. I have a better knowledge of my diabetes than LOOP does (sorry if that is heresy around here) and I would not like LOOP to be giving me basal right now OR ELSE I'LL GO LOW.* + *I took a screenshot of an example situation...LOOP is forecasting that I'll eventually rise up to 124 and is therefore giving me my full regular basal rate EVEN THOUGH im currently way below my desired goal range. I have a better knowledge of my diabetes than LOOP does (sorry if that is heresy around here) and I would not like LOOP to be giving me basal right now OR ELSE I'LL GO LOW.* *QUESTION: Which parameter must I change on my loop settings in order to essentially tell LOOP to relax on the basal rates??* @@ -33,16 +33,16 @@ Secondly, if the user were to go above their correction range, they would begin * Blood glucose is still below or just below target, and * Overnight basals were turning off/on. -So, what will you see after you adjust your basal lower? You will see some of the negative IOB disappear and, as a result, the predicted blood glucose curve will not so such an aggressive prediction for a blood glucose rebound. +So, what will you see after you adjust your basal lower? You will see some of the negative IOB disappear and, as a result, the forecasted blood glucose curve will not show such an aggressive forecast for a blood glucose rebound. In this example, the user's basal rates were lowered across the board. All of the basal rates went down about 0.2 U/hr. It works out to about a 15% decrease, and is pretty standard adjustment for this user due to her monthly hormone changes. -The adjustment to basal rates caused Loop to reevaluate its math. After adjustment, Loop now has a negative IOB of -0.55 units vs the previous value of -1.33 units. This is a more reasonable given the situation. The prediction line with a -0.55 units IOB was not predicting nearly as aggressive of a "rebound" blood glucose rise. +The adjustment to basal rates caused Loop to reevaluate its math. After adjustment, Loop now has a negative IOB of -0.55 units vs the previous value of -1.33 units. This is a more reasonable given the situation. The forecast line with a -0.55 units IOB was not forecasting nearly as aggressive of a "rebound" blood glucose rise. ![Looped3](img/looped3.jpg){width="750"} {align="center"} -Why did IOB and prediction change? +Why did IOB and forecast change? The visualization below might be easier. The red line is how loop knew things to be before basal rates were adjusted lower. The purple line is how Loop viewed basal schedule after the adjustment lower. @@ -67,4 +67,4 @@ The confirmation that adjustments were on-track would also be provided by lookin {align="center"} -Note: This entire scenario can also be applied in situations where (1) blood glucose has been steady but above target and (2) Loop is holding significant positive IOB, and (3) Loop has been high temping fairly consistently. By increasing the scheduled basals, Loop will recalculate that the positive IOB was actually necessary (not extra) insulin delivery, and the positive IOB will decrease. This will help the prediction curve to more accurately realize that not all the insulin deliveries were being utilized as "corrections" but rather as needed background basal. +Note: This entire scenario can also be applied in situations where (1) blood glucose has been steady but above target and (2) Loop is holding significant positive IOB, and (3) Loop has been high temping fairly consistently. By increasing the scheduled basals, Loop will recalculate that the positive IOB was actually necessary (not extra) insulin delivery, and the positive IOB will decrease. This will help the forecast curve to more accurately realize that not all the insulin deliveries were being utilized as "corrections" but rather as needed background basal. diff --git a/docs/index.md b/docs/index.md index b5cdbe9..12dc0af 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,7 +1,6 @@ # Introduction -Welcome to LoopTips! The purpose of these pages is to help you make the most of your DIY closed-looping experience. In particular, these pages support users of the [Loop app](https://loopkit.github.io/loopdocs/){: target="_blank" }. These documents have been a long time in the making and as always, your feedback is welcome. If you have comments, please feel free to provide input at the [Looped Facebook Group](https://www.facebook.com/groups/TheLoopedGroup/?fref=nf){: target="_blank" } or in [Loop's Zulipchat](https://loop.zulipchat.com){: target="_blank" } -. +Welcome to LoopTips! The purpose of these pages is to help you make the most of your DIY closed-looping experience. In particular, these pages support users of the [Loop app](https://loopkit.github.io/loopdocs/){: target="_blank" }. These documents have been a long time in the making and as always, your feedback is welcome. If you have comments, please feel free to provide input at the [Looped Facebook Group](https://www.facebook.com/groups/TheLoopedGroup){: target="_blank" }, [Loop and Learn Facebook Group](https://www.facebook.com/groups/LoopandLearn){: target="_blank" } or in [Loop's Zulipchat](https://loop.zulipchat.com/#narrow/channel/270362-documentation/topic/LoopTips){: target="_blank" }. LoopTips is a companion to LoopDocs. LoopTips does not cover the build or installation of Loop app. If you have problems with building your Loop app or troubleshooting the technical aspects of Loop operations, please head over to [LoopDocs](https://loopkit.github.io/loopdocs/){: target="_blank" } for help. The LoopTips pages are specifically related to understanding how your loop is recommending the actions being taken, and how you can improve your blood glucose outcomes on Loop. Some of the pages that originated in LoopTips are now included in LoopDocs. Don't be surprised when you find links between the sites. (The color bar is deliberately a different shade to help you know where you are.)