@plandolfi I don't want to rain on your parade, but there's a lot of prior art in the space. Have you seen
Nightscout?
There are already a lot of people using this to remotely monitor their kids at school, and by giving the child a Pebble watch, the kid can see the data on their wrist. While it is not immediately designed for a child, it provides the same level of information. It uses the Dexcom G4 Sensor technology and if you build an
xDrip doesn't require a Dexcom receiver. Or you can use the
DexCom G5, which will shortly be available on an Apple Watch.
All of the data input to manage a child on MDI can be input via the CarePortal in NightScout.
In addition, the majority of children are now encouraged on to pumps, which provides a much more flexible routine. Very few young children are on fixed insulin doses and therefore have specified eating times.
Reviewing your PDF from a critical perspective, it looks as though the real innovation in this could be in packaging up the NightScout product and delivering a more child friendly monitoring product and software package. Personally, if I was to be doing this, that's the approach that I would take.
If the intention is to package it all up into a watch receiver, to which the sensor will talk, consider the battery issue that plagues many smart watches now. Given what you are trying to do, you might want to consider a different way of getting the data to the network.
I don't know who is assessing your project, so I can't say whether they would have knowledge of what is out there, but if they have any knowledge of the #WeAreNotWaiting movement, then I'm afraid that they may see this as copying that, so I would reference it up front and consider how I might address it in my concept.
I'm happy to have a chat with you about this, in a private chat if you want it.