I've Built Myself An Artificial Pancreas!

@catapillar, the issue with the glucagon version of an AP is that the available glucagon now is only stable for a day. Bigfoot has been working with manufacturers who are trying to extend this, and the way openAPS works, if a dual chamber pump was available, it could apply glucagon to counter impending lows.

So after rather a lot more hacking than I expected to have to do to get the 640G data into the oref0 algoriithm effectively and offline, I have a fully looping system that's not dependent on a network connection to make a decision. If you aren't using the straightforward, well followed path, this can be a right PIA, but it's very satisfying to see it doing what it's supposed to be when you get there! This is this morning after a sensor change and a very proteiny breakfast.

So taking this a step further, I finally got around to the Loop app. This is an evolution of the openAPS work , built by someone else, but along very similar guidelines, and in my opinion is what all Hybrid Closed Loop manufacturers should be considering.

Loop is an iPhone app that interfaces with a pump via the RileyLink (a Bluetooth to 900MHz converter) and uses Dexcom G5 on board the phone for CG data). It has similar features to OpenAPS, but as it all runs on your iPhone, requires a lot less carrying.



As you can see in the picture below, Loop has a console showing the current sensor glucose level, the predicted level and also carb and insulin profiles. It also gives you a nice image of basal rate changes. The other feature that's rather cool is the "bolus" feature that works from the Apple Watch or the Phone, and if using the phone, requires the use of the Touch security. Without your fingerprint, no bolus.



What I'd like to see from all the guys trying to commercially produce products like this is that they looked at what we as a community have built and then worked out how they could build a commercial product that fits into that model. Our stuff looks like this because we want it to work for us, in our workflows.

So an app on the phone and the pump and CGM all combining either through that or through a single pump device with a connected phone app has to be the right way to go!

When it gives you a negative number, it basically sets a basal rate of 0. The purpose of the negative value is part of the prediction of future glucose levels.

Both Loop and openAPS are fantastic by the way!

Here's the latest - a guide to getting started with looping. You can do both open and closed loop systems. Some are easier than others. This is the what's available and where to go guide!

http://www.diabettech.com/looping-a-guide/

I thought it might be interesting to show the outcome of one whole month of running on a combination of Loop and OpenAPS. This is the Ambulatory Glucose Profile and the Monthly Stats for a month with a Hybrid Closed Loop. Throughout this period, I've not been low carbing particularly and there have been cakes, toast and just maybe the rather too frequent chocolate. It makes for interesting reading.

What's interesting for me when compared to the 80 days from April through to mid-June that I wore CGM whilst Sugar Surfing on the pump is the similarity of the stats. The major difference between the two is the amount of effort required to get to the same results.



For comparison, I present 80 days of data from the beginning of April through to Mid-June which was all on a pump, but using sugar surfing techniques, rather than having a hybrid closed loop do it for me.

I can now talk to my Pancreas!!!

GrantGam1337 said:

@tim2000s, 73mmol/l - you may want to reconfigure your algorithms slightly

Click to expand...

I can't find the "Evil Stare" emoji.....

So.... I have finally gotten my OpenAPS rig down to a one box solution that works with the glucose monitoring on the pump. It's now highly portable, completely offline capable, charges wirelessly and I monitor it from a Pebble watch on my wrist. It looks a little something like this: