My girlfriend is currently using one of these insulin pumps and there currently is a supplematary device which contunuiously monitors blood glucose level which significantly reduces the need to prick your finger. However, it's still required to test 1-3 times a day to calibrate the glucose monitor in order to relay the correct readings back to the pump. Once the blood sugar levels are sent to the pump, the pump in turn will ask the user to verify the amount of insulin to apply for correction. I think this is interesting on its own. All of this communication is done wirelessly by the way.
that one is not the closed loop, I intended. In the link you gave the user still needs to prick the finger/skin to get some blood on the strip to measure the glucose level. which is not automated. coming to think of it I realize that a non invasive blood sugar monitoring mechanism is needed for this to work, which mostly doesnt exist.
1. Yes, it is commercially available (https://www.accu-chekinsulinpumps.com/ipus/). This is for people with severe diabetes risks and who might have to take large dosages. The commercially available products do not have a closed loop system and the rate is adjusted through manual settings.
2. Yes, it is possible to implement a closed-loop system where we can involve the same chip to monitor current blood glucose level and accordingly adjust the flow rate. Here is a link about it:http://www.cypress.com/?rID=43661&source=header. Systems like this haven't yet come out in the medical industry.
oh ok.. theres no feedback mechanism to know the current blood sugar level of the patient.. it works as a linear open loop.. which is not impressive. if there was a sensor to detect the current blood sugar level and then push insulin accordingly, that wud have been interesting. For open loop drug delivery other mechanisms like micro needle patches are more convenient.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.