Live data from Hacker News

My insulin pump controller has a bug

twitter.com

121–130 of 172 posts

Re: My insulin pump controller has a bug

#121
post #33

A clearer description of the bug is here: https://twitter.com/Tims_Pants/status/1730515134731182490 It's wild that this sort of bug got through testing. As a diabetic it feels like our insulin pump software is very conservative and lacking in features especially compared to what some of the "closed loop" things would like to do. That seems reasonable if the manufacturers are having to do lots of safety testing. But i…

The user-blaming stands out in their official communication. Bad sign for company culture. > Once the bolus dose is confirmed and you tap START, the value that is shown on the screen will be delivered by the system... > As stated in our User Guide, it is important to review the bolus amount before you confirm and start the bolus. Omnipod 5 will always deliver the amount you confirm and that is shown on the Confirm Bo…

In case of buggy interface behavior violently rip device from torso.

Re: My insulin pump controller has a bug

#122

Cue the "you wouldn't steal a car" music. ♫ "You wouldn't demand open-source software for life-critical contexts instead of the industry-perfected closed software" ♫

IIRC, both the ipod and the Zune media players independently ended up with nasty date/time bugs due to errors in open source libraries they used. More eyeballs can be a good thing but given the number of willing eyeballs and the amount of open source code, it seems like the effectiveness of eyeballs on code is going down. Probably still better than just company eyeballs but far from something that should be relied on to filter out defects.

Re: My insulin pump controller has a bug

#124

Earlier quoted context omitted.

Absolutely. The App should be considered hostile by the pump firmware until proven otherwise.

This is quite the overreaction. There is both a confirmation screen and a maximum bolus setting to ameliorate the issue until an OTA update can be provided. Stranding users who use the app without access to our lifesaving medical device is... Bold, to say the least.

If you are a diabetic you should always have a plan B for your 'lifesaving medical device' because they can break. For instance:

https://www.northwoodsendocrinology.com/wp-content/uploads/2...

Presumably whoever provided you your pump has a similar instruction.

Risking using an app/pump combo that has a known flaw, especially a non-deterministic one is bold, to say the least. Safer to switch to the regular controller (assuming you have it) until this is fixed.

Re: My insulin pump controller has a bug

#126
post #97
post #72

Earlier quoted context omitted.

If you wanted 0.66 units and got 66 units, I am pretty sure you would die. I would count on the tissue around the infusion site not having enough throughput to release it all into your system at once and swelling up. This would mean the problem would spread over a few hours, but it would be an extreme emergency anyway. To put it into perspective (at least with my insulin to carb ratio, it varies from person to person…

Heh, yea, this is why when I went to DEFCON I disconnected the feed to my body. I mean it's not likely someone's going to try to murder me via bluetooth, but why take the risk when I didn't have to. In the days before I had a pump I did something similar to myself. I had a short acting insulin and long acting insulin both in pen form. Managed to give myself the large overnight dose which should have been the long act…

At least you noticed!

Re: My insulin pump controller has a bug

#127

"We understand this may impact your experience and are here to support you." I love this - I've never heard the euphemism impact your experience used to mean that your life may end . What a wild PR assignment (language off the company's safety notice https://www.omnipod.com/en-gb/fsn-11-2023 )

The language there is more than a little bit disingenuous, they all but blame the user for their fuck-up.

Re: My insulin pump controller has a bug

#128
post #33

A clearer description of the bug is here: https://twitter.com/Tims_Pants/status/1730515134731182490 It's wild that this sort of bug got through testing. As a diabetic it feels like our insulin pump software is very conservative and lacking in features especially compared to what some of the "closed loop" things would like to do. That seems reasonable if the manufacturers are having to do lots of safety testing. But i…

The user-blaming stands out in their official communication. Bad sign for company culture. > Once the bolus dose is confirmed and you tap START, the value that is shown on the screen will be delivered by the system... > As stated in our User Guide, it is important to review the bolus amount before you confirm and start the bolus. Omnipod 5 will always deliver the amount you confirm and that is shown on the Confirm Bo…

You can pop the pump off on a moment's notice (there is a needle sticking out of the pod at the back, some other manufacturers use an umbillical that can be disconnected).

Totally agreed on the communications failure here, they all but blame the user for not noticing their error. That's not how a responsible medical device manufacturer should deal with this.

Re: My insulin pump controller has a bug

#130
post #33

A clearer description of the bug is here: https://twitter.com/Tims_Pants/status/1730515134731182490 It's wild that this sort of bug got through testing. As a diabetic it feels like our insulin pump software is very conservative and lacking in features especially compared to what some of the "closed loop" things would like to do. That seems reasonable if the manufacturers are having to do lots of safety testing. But i…

That linked description is very interesting. They list 3 steps that need to happen to get an incorrect dose. The 3rd step is that YOU confirm the dose. The next section emphasizes the importance of confirming it. That's all great, and yeah, the user basically hit OK but that does not change the fact that they have a software bug. Also, since it happens intermittently with that kind of input I have to seriously questi…

> that would make me concerned about other issues we just don't know about yet

That's exactly my concern. This is not the kind of bug that you fix and move on, this is the kind of bug that makes you go back, fix your process, ensure your QA would catch this next time and then you audit all of your code to make sure that your broken process hasn't missed anything else.

Post reply on HN