Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid unnoticed carb entries #2168

Open
MaBeWi opened this issue May 13, 2024 · 2 comments
Open

Avoid unnoticed carb entries #2168

MaBeWi opened this issue May 13, 2024 · 2 comments

Comments

@MaBeWi
Copy link

MaBeWi commented May 13, 2024

I am a the father of a young new looper using dexcom g7, omnipod dash and loop 3.2.3. Thanks to loop, our family finally sleeps well at night, so thank you for an awesome app!

We had a scary situation a couple of days ago. After entering carbs and approving the insulin suggestion, the bolus injection failed because the pump was out of reach. Without us noticing, the carb entry was however saved in the app even though the insulin injection failed.

We then entered the carbs again and because the app now assumed we were eating twice of our intended carb amount, the app suggested twice the insulin amount, which we then approved by mistake. My worry is that this can happen when at school etc.

Potential solution:

in cases where an insulin injection is approved by user; is it possible to save the carb entry only if insulin injection proceeds without error?

@marionbarker
Copy link
Contributor

I don’t mean to minimize that this was frightening. But this is the design and it is documented. The Button you pressed says Save and Bolus. Perhaps we should modify the button to say Save Carbs and Bolus. Would that have made it more likely you would have taken a different action?

I certainly will move the warning box in this section to be higher up. And I will ask for more review from mentors (and you) on better words to get this concept across to new Loopers.

https://loopkit.github.io/loopdocs/operation/features/carbs/#meal-entry_1

@oliverstory
Copy link

Maybe 'Save carbs and attempt bolus' would be a good label for the button? Although it is a bit long.

Or 'Save carbs then bolus' - shorter but clear that the 'save carbs' happens first, so if you then get a 'bolus failed' message it is clearer that it's the bolus part rather than the 'save carbs' part that failed.

Our little looper is at daycare and I have received several calls from staff members who've encountered an issue at this step and wondered what to do next. I've seen this occur both with the 'pod not connected' error and when there's an automatic bolus in progress when you press 'save and bolus'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants