No, not all. Loop allows customization. I set my BG target to 83 mg/dL. I can set a temporary target a little higher for exercise or a little lower when I want to deliver more insulin. I use it like the gas pedal in a car.
Loop allows me to set various insulin sensitivities and segment the day with them. Loop doesn’t force me to distort the actual meaning of insulin duration in order to allow the user to change prospective performance like the 670.
Since I’m not algorithm literate, I can’t compare the two algorithms but Loop is unimpaired by regulatory niceties. It doesn’t send me into a redundant button-pressing circus every time I just want to add some insulin. Loop designers built in many safety provisions including falling back to the settings programmed into the insulin pump when the system fails. The most durable command Loop gives is a 30-minute temp basal rate.
Loop’s open source nature and citizen programmers, free of regulatory burden, can continuously iterate and as a result evolve more quickly than any commercial offering. I feel like I am enjoying a system that’s ten years in the future for the commercial systems.
I see the 670G system as a baby step toward an automated system, but it’s a crucial baby step. The commercial companies will deliver this technology to a much broader demographic than any of the DIY automated insulin delivery systems can.
I wish that the Medtronics of the world would open up their code and allow the talent of the open source do it yourself movement to help all of us more quickly.
The JDRF supports this as do some of the commercial diabetes tech players.