The other day was a frustrating day on the Dexcom. In the afternoon, after a luncheon I had thrown at my apartment, my Dexcom was showing me at a steady 270 mg/dl while I was working my retail job. It wasn’t coming down, which I found really odd, so I went into the back to test. I was 140 mg/dl.
So I callibrated, and all of a sudden the Dexcom alarms asking me for a blood sugar reading! But I just did one!
The second calibration held and the Dexcom worked again.
Later that night, as I was getting ready for bed, the Dexcom showed me at a steady 117 mg/dl. Awesome, I thought. I really showed that luncheon who’s boss! But then when I tested, I rang in at 295 mg/dl! What the crap?!
When I calibrated, the Dexcom once again prompted me for another reading.
At this point I thought there was something fishy going on with my sensor. I’d had this alarm prior but I could never figure out what it was from, and so I though maybe it was a sign of a wonky sensor or a bad connection. Frustrated and not wanting to deal with bad reports from a Dexcom, I ripped out the sensor on just Day Five. Perhaps a bit premature, but it was late and I was frustrated.
The next day, I finally got around to tweeting about what had happened. Surely someone on the Internet will know! And sure enough, three people wrote me back explaining that the Dexcom will prompt you for a second blood sugar reading if the calibration reading is way off from what it currently has you at. They say that they do that because the Dexcom doesn’t want you feeding it a potentially erroneous blood sugar reading, for instance, if you had some food still on your hands.
Smart thinking, Dexcom! I totally would not have thought that it was actually a safety precaution and I had never heard of anyone saying that the Dexcom will prompt you for a second reading if your meter reading and Dexcom reading are very far apart.
Goes to show you learn something new everyday!
Do you have any technology surprises about the Dexcom or Omnipod that I should know about?