3 ms·
Why exactly is a phone app involved? If I were designing this thing, DIY or otherwise, the CGM would talk to a dedicated micro controller, which would in turn
by amluto 8y ago
Why exactly is a phone app involved? If I were designing this thing, DIY or otherwise, the CGM would talk to a dedicated micro controller, which would in turn talk to the pump. A phone, if used at all, would get an extremely limited API to read the glucose level, see the pump history, and perhaps change the control parameters within a narrow range. The point would be that no input from the phone should be able to kill or incapacitate the user.
And the controller would beep if communication were lost.
There would not be an Internet API to change any parameters at all.
- sowbug 8y agoThe current solution requires no manufacture or distribution of custom hardware. It's all software that exploits hardware the users already have. Your solution is surely better, but the current one exists.
- jimrandomh 8y agoYou need something with a screen somewhere in the system to be able to monitor it and input data, which means a phone app or a web app. In the case of OpenAPS, it works mostly as you described: an Intel Atom SoC talks to the CGM and to the pump, and syncs with a webapp (called Nightscout) for monitoring and user input if internet access is available, but continues to operate autonomously if it isn't. The webapp sends an alert if the microcontroller hasn't connected for awhile (30 minutes), which is how you find out if it's lost communications or powered off. Users have to be able to input when they're eating carbs. It's possible to do that through the pump (that's how I do it), but there are some ways in which that's not ideal. Most people enter carbs through the webapp. This is capable of creating a dangerous situation for the user (not of killing them). It's a security risk, but also a practical necessity. Some peoples' setups are more internet dependent than that, though. For certain models of CGM, the way you get data from them is by giving them an internet connection and using a web API provided by the CGM maker. (This is built on abusing APIs that were intended for eg family members monitoring glucose values of children who might not be close by.) And, in the case of Loop, the decision algorithm executes on a phone. These setups aren't ideal, but they're all made by hackers with limited time and resources desperate to get something that works, because the market isn't providing anything acceptable.
- amluto 8y ago> Users have to be able to input when they're eating carbs I’m not diabetic, so I’m probably missing something, but why? I would have expected the CGM to detect the extra glucose quickly enough without any extra input from the user. Kind of like how people with pacemakers don’t have to tell the pacemaker before they start jogging.
- cjlars 8y agoThe latest medtronic offering (mentioned in the article) does this. The microcontroller and pump are integrated and there's no communication to an app. The lack of communication is a bit of a downside for people who are used to monitoring their levels on smartwatch, but overall the auto-mode features more than make up for that.