Ok, so I’ve been thinking about this topic and I may have an unconventional and novel solution. There is a way to incentivize good BG control. There a few basic things that would be required.
-
Internet access
-
Dexcom G4 (with share) or G5
-
A Nightscout site (free and easy to create)
-
An account with IFTTT (free)
Anyone not familiar with IFTTT, it is essentially a way to create automatic rules for various accounts that are linked together. For example, you can turn down the thermostat when you leave the house. Or blink a light when your favorite sports team scores or when your BG gets to high…hmmm…
So I was thinking, how could I use this tech to incentivze good BG control for a teen? There are 12 built-in events in nightscout (below). Using your own imagination you could create automatic rules to help nudge your teen to better control–in your own way.
For example, how about:
-
A simple text reminder that his/her BG is getting too high/low.
-
A rule that de-prioritizes his xbox or ps4 internet speed on your home network, if his/her sugar gets too high.
-
A rule that rewards him/her with $$$ if he/she adds a treatment into the care portal.
-
Maybe a rule that deducts $$$ if he/she spends money at Krispy Kream donut store?
-
How about a rule that plays the Barney “I love you” song every time his/her Dexcom has not uploaded new data in x amount of time…okay, that one might be borer-line torture.
The options are only limited by your imagination. The benefit is that these actions are immediate and are directly associated with their behavior at the time of the incident. Below is the current list of built-in events that Nightscout offers.
ns-event – This event is sent to the maker service for all alarms and notifications. This is good catch all event for general logging.
ns-allclear – This event is sent to the maker service when an alarm has been acknowledged or when the server starts up without triggering any alarms. For example, you could use this event to turn a light to green.
ns-info – Plugins that generate notifications at the info level will cause this event to also be triggered. It will be sent in addition to ns-event.
ns-warning – Alarms at the warning level with cause this event to also be triggered. It will be sent in addition to ns-event.
ns-urgent – Alarms at the urgent level with cause this event to also be triggered. It will be sent in addition to ns-event.
ns-warning-high – Alarms at the warning level with cause this event to also be triggered. It will be sent in addition tons-event and ns-warning.
ns-urgent-high – Alarms at the urgent level with cause this event to also be triggered. It will be sent in addition tons-event and ns-urgent.
ns-warning-low – Alarms at the warning level with cause this event to also be triggered. It will be sent in addition tons-event and ns-warning.
ns-urgent-low – Alarms at the urgent level with cause this event to also be triggered. It will be sent in addition to ns-event and ns-urgent.
ns-info-treatmentnotify – When a treatment is entered into the care portal this event is triggered. It will be sent in addition to ns-event and ns-info.
ns-warning-bwp – When the BWP plugin generates a warning alarm. It will be sent in addition to ns-event and ns-warning.
ns-urgent-bwp – When the BWP plugin generates an urgent alarm. It will be sent in addition to ns-event and ns-urgent.
All of this can be done in theory. I personally haven’t done more than blinking some lights, logging events, and setting off an urgent low siren–but all of the ingredients are there.
Let me know what you guys think and if anyone has tried any. I would be curious as to what configurations you guys can come up with.