dsut4392
commented
1 month ago It sounds like a wonderful idea, albeit a lot of work to implement, particularly in a way that would be usable and safe for the people who need it most. On the practical side, without adding significant workflow, logic, and math, ensuring the app has enough information to make sound recommendations is also difficult. First of all, we need a proper 'open loop' mode in which we can run basal/ISF/CR testing while retaining the ability for the app to deliver oref calculations and have low-glucose-suspend protection. Existing reporting solutions such as Nightscout can give you nice plots of BG vs IOB and carbs, but there are often additional contextual factors like unrecorded carbs or exercise that are important. Apps like Lukas Schuster's Diabetes Cockpit are also useful for understanding settings. Leaving aside the many practical difficulties, automating individualised settings guidance within the app is stepping across the line from implementing user-chosen settings to 'providing medical advice', which has significant ethical and legal considerations.
Natolida
Sjoerd-Bo3
Is your feature request related to a problem? Please describe.
Provide a clear and concise description of the problem. Explain how this issue affects your experience with the Trio app and any specific scenarios where it occurs.
The emergence of DIY systems has unquestionably revolutionized the management of diabetes for individuals. Even those with inadequately adjusted basic settings can derive benefits from these systems. However, the most frequent request for assistance I often encounter relates to users not taking the time to test and titrate their basals, carb ratios, and insulin sensitivity factors.
For the past seven years, I've been using DIY systems, and my settings are finely tuned. A decade ago, I was unaware that I had the option to self-titrate my settings, and I heavily relied on my health care team for this. It was a revelation when I discovered that I could adjust my own settings. This newfound control not only improved my management but also increased my time in range, bringing a positive change to my life with diabetes.
While I have the technical ability to assist with documentation, logging, and testing. I do not have the technical ability to pull something like this off. However, I do feel like people would benefit from it.
Describe the solution you'd like
Detail the desired change or feature you'd like to see implemented in the Trio app. Be specific about how this solution would improve your experience and address the problem described above.
What If we included functionality within Trio to support and empower users to self-titrate these basic settings? Could we improve the user experience of those using Trio? Could we help our users further increase their time in range? Could we help our users spend a little less time managing their diabetes?
I don’t think we need to reinvent the wheel here. There are so many resources out there that assist users in self-adjusting settings. I love the book ‘Pumping Insulin’. It has some great resources that provide graphical representations of when and how to adjust your settings. Could we create a report within Trio that presents data similarly?
Describe alternatives you've considered
List and describe any alternative solutions or features you've considered that could also address the problem. Explain why you believe the proposed solution is the best option.
Users could utilise paper format to assist with knowing when and how to titrate settings. However, I feel this is outdated, and it doesn’t hurt to save some trees.
Users could use current reporting to assist with titrating settings. However, current reports can be information-heavy, causing users to be confused about what needs changing.
Additional context
Include any other context, screenshots, or relevant information that might help in understanding the issue or the proposed solution. If applicable, describe any previous discussions or decisions that relate to this feature request.
Basal Testing:
Carb Ratio Testing:
ISF Testing:
Technical Details
If applicable, provide any technical details or considerations that might impact the implementation of this feature. This could include dependencies, potential risks, or required changes to existing functionalities.
User Impact
(Optional) Describe the impact of this issue on your use of the Trio app. Include any specific examples or data that demonstrate how widespread or severe the problem is.