Alternative optional insulin remaining display

[bigolal007]

Is your feature request related to a problem? Please describe.

Not related.

Describe the solution you'd like

Having an optional display for the amount of insulin remaining for users on Omnipod Dash.

My suggestion would be to have an option at some point for the user to input the amount of insulin they have entered into the pod - perhaps once the pod attachment is confirmed (final screen). In the settings, you have the option to have either 50+U (default) displayed or the total amount of insulin e.g. 125U remaining. The proposed display can calculated by the user entering the amount of insulin e.g. 200U and subtracting the Total Delivery figure (in pod details). Obviously this suggestion wouldn't be 100% accurate (maybe +/- 5U) until it reaches the 50U left report by Omnipod. Warning messages would need to be included describing the feature being optional and it's potential inaccuracy based upon the user's initial input.

For me it'd be a great feature to help manage the amount of insulin I use so I can push the duration of my pod from two days out to the full three. In Australia, I'm limited to 13 boxes of pods for the year since I was approved, so at the moment I need to use pens for a month or two so as to not reach my limit approved by my private health insurance to paying the $200+ for each box.

Describe alternatives you've considered

I haven't been able to come up with an alternative.

Additional context

I have proposed this in the discord channel, and another use expressed that they would like this feature as well. I can't remember if a decision was made by any of the developers.

Technical Details

I don't believe this would have any effect on the functionality of the app other than display.

User Impact

There's no issue at the moment. It would be a nice optional feature to have but certainly won't change my mind in using Trio.

[dnzxy]

For me it'd be a great feature to help manage the amount of insulin I use so I can push the duration of my pod from two days out to the full three.

I‘m lost at this statement. You know how much you fill into the pod, you know your TDD / your insulin usage (of currently paired pod) respectively (can be checked via pod diagnostics) and you can then do X - Y. Unless you have wildly varying insulin needs between two pods, you should be able to note down that value a few pods on in a row and then use that number to fill subsequent pods. Even easier than that would be to just do TDD x 3 + Y% (for wiggle room).

It’s a bad idea to give users a false sense of information transparency based on guesstimated values, especially when it comes to insulin. FWIW, even the pod when displaying e.g. 45 U does not actually contain 45 U, but roughly +4 U of that.

[bigolal007]

That makes sense.

You're right - making a change that does impact a large group of users that can have a significant impact isn't a good idea. I'll take what you have said and use that method. It was a feature I've always wanted but haven't considered the adverse effects for others.

Thanks for clarifying it for me.

On Fri, 1 Nov 2024 at 19:42, Deniz Cengiz @.***> wrote:

For me it'd be a great feature to help manage the amount of insulin I use so I can push the duration of my pod from two days out to the full three.

I‘m lost at this statement. You know how much you fill into the pod, you know your TDD / your insulin usage (of currently paired pod) respectively (can be checked via pod diagnostics) and you can then do X - Y. Unless you have wildly varying insulin needs between two pods, you should be able to note down that value a few pods on in a row and then use that number to fill subsequent pods. Even easier than that would be to just do TDD x 3 + Y% (for wiggle room).

It’s a bad idea to give users a false sense of information transparency based on guesstimated values, especially when it comes to insulin. FWIW, even the pod when displaying e.g. 45 U does not actually contain 45 U, but roughly +4 U of that.

— Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/436#issuecomment-2451520927, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4DNWPJTGGCWZTLX42FKNXTZ6M5FXAVCNFSM6AAAAABQ7O4AS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRGUZDAOJSG4 . You are receiving this because you authored the thread.Message ID: @.***>

[dnzxy]

The information you are seeking is already available at your fingertips. That’s why I am lost at your idea. All the data you need to save pods and know how much insulin to fill them with is available. Please be so kind as to explain it further instead of being defensive and throwing sarcasm at me.

I’ll add some more background to my previous reply: Adding the factor of guesstimation and user input, when there can be a varying group of people filling and applying a pod for the actual T1 / Trio user, and a bunch of conditional logic on top of it, for a single pump option is a bad idea for safety concern and software design reasons, yes, in my opinion, as a developer.

[dnzxy]

On second thought, cause while your probably won’t believe me, I am throwing a bunch of things around in my head trying to look at your idea from various angles, this idea / request is probably pointed at the wrong party here.

Let me explain why: We make use of the OmniBLE and OmniKit modules of the LoopKit framework. Those are our pump drivers. The entire pairing workflow / UI you go through is rooted in these modules. The information surrounding pod age, pod fill, the alerts you get for low reservoir or nearing expiry, all these things are rooted in these modules. They are propagated through various layers of the modules into actual Trio code and then processed for display on your phone through the UI.

If this were ever a feature-set to be added, the place to do it would be during the pod priming and application workflow as an added layer/step (I hope it’s clear what I mean by that), so it’s an option that OmniBLE / OmniKit would need to provide us with.

For that reason, I think this request is best pointed toward the maintainers of the submodules. If this were to be added there, we would (naturally, in keeping up with a homogenous iOS infrastructure for pump drivers) probably adopt it when we update our submodule dependencies.

For the other reasons (see my previous 2 comments), I still don’t think this is a good idea, sorry. Trio does a great job (and the information readily available with the current pod UI) in giving you all the information you require.

You can go into your pump settings in Trio, check the delivery of last pod, grab the precise (!) delivery info (precise to 0.05 U!) from there, compare it to your TDD of Trio, then calculate how much you should fill your new pod with.

Pod Settings	Last Pod Info

Editing post to add: I am sorry for the hardships you face surrounding your supply situation. If there’s anything the DIY community can do to maybe let you accumulate some sort of stash for pods, please share them or reach out in the appropriate places. We all are in this together, so I am fully empathic to your situation. The Australasian Looping community is a tight-knit, wonderful, very active group of people and I‘m sure there are folks that may be able to help you out, or that know some loopholes to maybe get yourself a few more pods. The Facebook groups CGM in the Cloud and Aussie, Aussie, Aussie, Loop, Loop, LOOP! may be good places to connect.

[Sjoerd-Bo3]

I wholeheartedly agree with @dnzxy last post on this point. It doesn’t belong in Trio itself but the submodules. Although I think this is a guesstimating feature that shouldn't be done.

[bigolal007]

I must apologise. I wasn't being sarcastic and didnt mean for it to come across that way at all.

I do appreciate your suggestion about the information at my fingertips - perhaps my suggestion comes from a place of laziness and not wanting to do the calculations. I didn't realise the amount of work it would take behind the scenes, hence why I was thinking of it being a ‘small change’ if it reads that way in my suggestion.

Given the amount of work involved as you've laid out and the risks the feature creates, there would certainly be more risks than benefits. I think time would be better spent on other improvements/features.

I appreciate the work that you and everyone else involved have and are continue to do on Trio. It's amazing and a big improvement on iAPS.

Once again, I do apologise for how my reply came across.

On Fri, 1 Nov 2024 at 20:29, Deniz Cengiz @.***> wrote:

The information you are seeking is already available at your fingertips. That’s why I am lost at your idea. All the data you need to save pods and know how much insulin to fill them with is available. Please be so kind as to explain it further instead of being defensive and throwing sarcasm at me.

I’ll add some more background to my previous reply: Adding the factor of guesstimation and user input, when there can be a varying group of people filling and applying a pod for the actual T1 / Trio user, and a bunch of conditional logic on top of it, for a single pump option is a bad idea for safety concern and software design reasons, yes, in my opinion, as a developer.

— Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/436#issuecomment-2451584014, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4DNWPK2DGTGCKDBRUFKEGTZ6NCXTAVCNFSM6AAAAABQ7O4AS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRGU4DIMBRGQ . You are receiving this because you authored the thread.Message ID: @.***>

[Sjoerd-Bo3]

You are alright! It's not the amount of work that is the issue here. It's that the code that needs to change form this is in the modules, not Trio itself. But besides that, the guessing how much you much you injected into the pod is an issue. It's an inexact amount that the user needs to enter. But also can screw up, We cannot check that, or catch such a thing. So it's a false sense of security. Leading to more uncertainty than its doing good. I also wonder sometimes if I make it with the pod. But then I look at the amount delivered. and I know how much is in there from the begin. The amount remaining that the pod gives, is already the indication you seek, its also not that accurate, but to a certain amount (its always more imo).

I believe this will lead to way more confusion then that it will solve.

[dsut4392]

@bigolal007 NDSS will have ways around the 13 box limit for pods, particularly if your insulin needs exceed 200U in 3 days. Contact them and explain your situation and there will be a batter solution than using pens for a month.

[bigolal007]

Really? I had no idea they'd be able to help - I thought it was only through private health insurance. I'll have to give them a call tomorrow.

Thanks for the info!

On Tue, 5 Nov 2024 at 17:39, dsut4392 @.***> wrote:

@bigolal007 https://github.com/bigolal007 NDSS will have ways around the 13 box limit for pods, particularly if your insulin needs exceed 200U in 3 days. Contact them and explain your situation and there will be a batter solution than using pens for a month.

— Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/436#issuecomment-2456357744, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4DNWPK4IPRQQWZZXITYAKTZ7BRY3AVCNFSM6AAAAABQ7O4AS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJWGM2TONZUGQ . You are receiving this because you were mentioned.Message ID: @.***>

[bigolal007]

Unfortunately got immediately dismissed after explaining my situation and told to contact Omnipod. I have one box left, and the limit resets in March.

On Tue, 5 Nov 2024 at 17:39, dsut4392 @.***> wrote:

@bigolal007 https://github.com/bigolal007 NDSS will have ways around the 13 box limit for pods, particularly if your insulin needs exceed 200U in 3 days. Contact them and explain your situation and there will be a batter solution than using pens for a month.

— Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/436#issuecomment-2456357744, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4DNWPK4IPRQQWZZXITYAKTZ7BRY3AVCNFSM6AAAAABQ7O4AS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJWGM2TONZUGQ . You are receiving this because you were mentioned.Message ID: @.***>

[Sjoerd-Bo3]

Could you guys maybe have the convo on discord or fb? Instead of the issue? Its not really meant for this, although I love that you guys are sharing info and such

[bigolal007]

Sure thing. Sorry.

On Wed, 6 Nov 2024 at 11:59, Sjoerd Bozon @.***> wrote:

Could you guys maybe have the convo on discord or fb? Instead of the issue? Its not really meant for this, although I love that you guys are sharing info and such

— Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/436#issuecomment-2458494170, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4DNWPNBIRBZMAC4HCOXHCLZ7FSXTAVCNFSM6AAAAABQ7O4AS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGQ4TIMJXGA . You are receiving this because you were mentioned.Message ID: @.***>