Hope someone can help me with this problem!
I’m caregiver for my 86 y.o. Type 1 mom. Ever since Medicare allowed her to have a Dexcom 5 years ago, she has experienced very frequent sensor errors, especially in the last few days of a sensor (both G6 and previously G5).
What happens is: The Dexcom graph is cruising along steadily, but suddenly plunges (often even into Urgent Low territory), then we lose data for anywhere from 30 minutes to 3 hours. If we do a finger stick, however, the number is right in line with the previous graph, as is the Dexcom number when the data finally returns. (I.e., the plunging graph is a false low.)
This happens to such an extent that we almost always have to take the sensor off a couple days early. It wakes us up in the middle of the night with regularity, causes us to treat unnecessarily out of an abundance of caution if we can’t stick her finger right away, etc. And now that Mom has an Omnipod 5, we are concerned that the constant bad data from Dexcom is fouling up her Omnipod algorithm.
Although Dexcom is very good about replacing sensors when we take them off early, they’ve never been able to give us any guidance on how to avoid this problem. It seem plausible that, as they say, the sudden plunge (and it’s always a plunge, never a spike) is the result of the sensor periodically having trouble getting data from Mom’s interstitial fluid, resulting in a lower and lower reading until there is no data at all, but that does not help us avoid the problem.
We’ve tried overpatches and putting the sensor in different locations, and probably other things that I’m forgetting, too.
This all being said, sleep deprived though we all are, of course it is better to have the Dexcom than not, and we don’t want to ditch it. We just want it to work as advertised!
Does this sound familiar to anyone? Has anyone got a fix?
(P.S., This forum was so incredibly helpful to us ~three years ago, when we were having pod problems. My mother has never once had to go to the hospital with a number we couldn’t get down ever since we implemented the fix y’all suggested!)