
At about 1:45 am, the reading crossed out of range and triggered an alarm. I can't remember exactly why I didn't deal with it at the time, but the high blood sugar persisted, without any more alerts, until approximately 5:45 am, when I woke up, realized I was (still) high, corrected with insulin, and brought my level back down. I don't know for sure, but I suspect other Dexcom Seven users will experience this same phenomenon. The only way I have found to avoid it is to wake up with the first alert, correct as needed, then move the threshold so I will get another alert if the readings keep trending in the wrong direction. This is a plain old pain in the behind at night.
As of now, I am starting my Dexcom Seven wish list, and here is Wish #1: I would like a snooze option with the Dexcom. I would call it a "persistent out-of-range alert". There is already one such alert built in - if the reading is consistently less than 40 mg/dL the receiver buzzes you at regular intervals until you get over 40 - but I would like to have optional extra out-of-range alerts. In my perfect Dexcom world, these alerts would occur at regular intervals specified by the user (15 minutes, 30 minutes, or 60 minutes?) to indicate that glucose values have stayed out of range. This would be helpful in lots of situations, but especially at night, when I accidentally turned off my alarm and I'm "sleeping in".
No comments:
Post a Comment