You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I find that an omnipod has been leaking for hours after a bolus, and the loop thinks I have 16u on board but in reality I probably only got half that or less, I don’t want it to use the data from the time I spent struggling to get back into range due to faulty hardware for closed loop basal rates for the next 24 hours.
Ideally, I’d love a way to say that insulin was not going in so I don’t want to be treated as if I have all that insulin on board. This might be a more nuanced fix but I think from my perspective, given my lowered sensitivity while a new site is saturating, and my wildly out of range BS, I would say the algorithm should be able to operate under the assumption that I’ve only gotten 50-75% of the insulin in thinks I’ve gotten over the past say 4/12/24 hours.
I can’t say there’s any alternative to the algo getting the data that I haven’t actually been getting the insulin it thinks I have been, but what I personally do is give myself a small bolus when I change pump sites anyway, but I do a higher one when it’s been leaking…which doesn’t help the “perceived IOB” the loop has.
Happy to bounce some ideas around if helpful!
The text was updated successfully, but these errors were encountered:
You can delete insulin from your history to accomplish this, however in this exact situation I almost always correct with a shot when I fill a new pod for an amount fairly close to my current IOB. It's a bit of a safety net.
I am not sure deleting insulin from the Active Insulin list affects current IOB. Also, I do not think @sarahspins suggestion addresses the OP: to have IOB better reflect reality (i.e. half/third/whatever the current value). Definitely giving a corrective bolus would help the problem of insulin deficiency, but the question is how to modify current IOB? One suggestion would be to add carbs on board without giving a bolus, expiring roughly over the desired corrective period (in the future).
When I find that an omnipod has been leaking for hours after a bolus, and the loop thinks I have 16u on board but in reality I probably only got half that or less, I don’t want it to use the data from the time I spent struggling to get back into range due to faulty hardware for closed loop basal rates for the next 24 hours.
Ideally, I’d love a way to say that insulin was not going in so I don’t want to be treated as if I have all that insulin on board. This might be a more nuanced fix but I think from my perspective, given my lowered sensitivity while a new site is saturating, and my wildly out of range BS, I would say the algorithm should be able to operate under the assumption that I’ve only gotten 50-75% of the insulin in thinks I’ve gotten over the past say 4/12/24 hours.
I can’t say there’s any alternative to the algo getting the data that I haven’t actually been getting the insulin it thinks I have been, but what I personally do is give myself a small bolus when I change pump sites anyway, but I do a higher one when it’s been leaking…which doesn’t help the “perceived IOB” the loop has.
Happy to bounce some ideas around if helpful!
The text was updated successfully, but these errors were encountered: