I just heard that Omni pod 5 is officially released in the US.
It’s supposed to have phone control so we can ditch the pda.
Direct dexcom integration with its own brand new algorithm and an adjustable glucose target.
That’s pretty much all the things I’ve been wanting in a pump.
Has anyone tried it? How is the algorithm ?
Is it a game changer?
I don’t think I’d stay with them long term, but I’d be curious to try it until the Mobi comes out… Assuming it doesn’t screw with my ability to get the Mobi later.
Unfortunately, there’s only one phone on the compatibility list right now, and it’s not even even an iPhone. 2 models of the Samsung S-10. I might have to go coerce a family member with one of those to swap phones with me
I know someone around here was in an Omnipod 5 study. @Sally7 maybe? Whoever it was, I recall them saying the algorithm wasn’t for them, though. But then again, it took a while to get Control-IQ tweaked, maybe there will be a similar process with Omnipod 5.
It says you can customize your target. I had heard they were going to let you aim for a lower target goal than the other looping pumps. Does anyone know what they will let you aim for? I don’t really want to aim for a higher number than I’m happy with. Over 105, maybe 110 and I won’t like it.
But I really like the idea of the Tandem T Sport Patch pump, instant bolus from the patch itself plus a choice of cannulas. My “warranty” is coming up on my Omnipod so maybe perfect timing to try something new that has more options!
While I won’t be switching to this device, I am curious about its specifications. After a quick look through its website, I couldn’t find anything about target BG, any description about how the algorithm works (modulated basal rates, microboluses, or some combination?) or even a FAQ file. I was hoping that they’d link to a User Guide, but I couldn’t find one.
I’m happy, however, to see some movement in the commercial hybrid closed loop sector. I’m sure the details I was looking for will be out soon. This is definitely a step in the right direction, just not sure how big a step it is.
Edited to add: Well, I finally found the FAQ page.
I’m reading over on the Facebook Omnipod group that the Omnipod 5 will be introduced as a Limited Market Release (LMR) for a period of time before it will be available to the broader market. Some comments say that the LMR group is already fully subscribed and is comprised of T1D employees of Insulet and Dexcom. That makes sense that Insulet wants to work out any bugs before releasing to the larger market. I’m sure it’s hard to be patient when you’ve been anticipating this release for so long.
Here’s the Juicebox podcast #620 interview with Insulet CEO Shacey Petrovic and Dr. Trang Ly, Senior VP and Medical Director.
Around the 16-minute mark, Dr. Trang Ly talks about the system using 110 mg/dL target for calculating boluses and informing the algorithm.
Edited to add: Shacey Petrovic gave a nice compliment to the DIY Loop movement as “paving the way” for the commercial companies. Dr. Ly also made mention near the end about micro-boluses, so I suspect that it uses micro-boluses instead of modulated basal rates as its primary technique.
Your body does not care what you call it - insulin is insulin, no matter what name you give it. A bolus or an increased basal is basically just an increase in insulin. It all comes down to timing and amount. An aggressive basal increase can be the same as a conservative or extended bolus. And vice versa.
I agree that at low insulin delivery rates, the body doesn’t care that you think of it as basal delivery or micro-bolus delivery. If, for example, you compare an algorithm that delivers a temporary basal rate of 1.2 units/hour for one hour to an algorithm that delivers twelve 0.1 micro-boluses every five minutes for an hour. It is the same thing. And the words we attach to that do not create any difference in meaning.
Before I adopted the DIY Loop automated insulin dosing system with its modulated basal delivery tactic, I was skeptical that changes in basal delivery could affect good BG control. What I discovered was that changing basal deliveries on an every five minute basis could indeed keep non-mealtime periods under good control.
I have not used a system with micro-boluses as its fundamental tactic and wonder if it might have some advantage over temp-basal delivery.
At larger quantities of delivered insulin, I believe that the distinction between basal and bolus insulin is important. The healthy non-diabetic body is capable of releasing a large bolus of insulin in response to the rapidly rising glucose experienced soon after meal is consumed. The larger size size of that bolus release and squeezing it into a short time period give it the “punch” needed to halt excessive glucose rises.
I found this description interesting as to how Ominpod 5 compares with other commercial hybrid systems. It is published in a FAQ on the Insulet website.
How does the Omnipod® 5 Algorithm compare to the other AID Systems? >
The SmartAdjust™ technology is a model predictive control algorithm that communicates with the Dexcom G6 CGM every 5 minutes and predicts where glucose will be in 60 minutes and increases, decreases or pauses insulin using a customized glucose target set by the user. The MiniMed 670G is a proportional-integral-derivative algorithm that takes CGM values from the Medtronic sensor and every 5 minutes adjusts insulin to a set Target glucose of 120mg/dL. The Tandem Control:IQ system is also a model predictive control algorithm that communicates with the Dexcom G6 CGM and every 5 minutes predicts where glucose will be in 30 minutes and increases, decreases or pauses insulin to a target range rather than a customized glucose target.
I have written about this in other places, so please forgive me if I’m repeating myself here. I’ve not seen this idea proposed by anyone else.
I, too, think that the user should be able to select a glucose target below Omnipod 5’s lower limit of 110 mg/dL. Since I have been watching my own CGM data for over 12 years now, I’ve learned that lowering blood glucose variability permits safely lowering the average glucose level. Glucose variability is measured with standard deviation (SD) and coefficient of variation (CV%).
Perhaps the algorithm designers could conditionally allow a lower BG target to be set when glucose variability has dropped below certain levels for a sustained period of time. This could permit users to earn the ability to safely use a lower BG target for the algorithm to use.
I see this proposal as taking nothing away from the larger majority of users the Omnipod 5 is designed to serve but it also enables the small slice of better managed users to access an algorithm better suited to their metabolic reality. It’s a win for everyone involved and builds in an incentive for the typical user to improve their glucose variability.
Using my DIY Loop, I aim for 83 and I’m happy with a 14-day average in the low 90s. With a SD at 20 mg/dL, you can appreciate that my hypo safety is just as good as someone with an average of 110 and a SD of 40 mg/dL.
I think it sounds very interesting! I like that all the code resides on the POD vs PDM. I also like that it LEARNS so even if your factors are off, by POD 2 and beyond, it is auto-adjusting things for you and only gets better with age. It will also have full support of the Omnipod folks. Scott at the Juicebox Podcast can’t wait to try it on Arden because she is about to go off to College. He said she has no desire to have to build / regbuild the app using a mac and support it herself so he is looking forward to it! Yeah, 110 is not to everyone’s liking, but I think it was an FDA thing.