Skip to content

Posts tagged ‘dexcom’

Dexcom Adhesive, Activated!

Nothing to see here, especially if you’re looking for an adhesive-related Dexcom rash. Because ever since switching to the sensors that expire after 8/17/17, the rash is a thing of the past.

Now I can wear my sensors for the recommended seven days (sometimes stretching it a day or two here and there, if I’m feeling bold), and my skin is fine when I remove the thing.

Great joy! YAY!!!!

However, if I add any Opsite Flexifix tape, that’s suddenly causing an irritation. It’s like the reverse of what was happening for years.  So.  Close.

But it’s awesome to be adhesive itch-free after almost five years of scratchy-scratch.  Life without blistering skin reactions, Toughpads, and welts that last for over a week is so much nicer.

The only downside to the new post-08/15/17 expiration sensors is that the adhesive itself seems to be weaker.  For the first time in years, I had a sensor go loose and yawn off my skin after 10 hours of wear.

A quick call to the Dexcom customer care team was quick to replace this sensor, thankfully.  And I learned something random on the phone call.

“Are you pressing down on the sensor adhesive after application?” the customer service guy asked.

“Yes, I am.”

“Oh good.  That helps activate the sensor adhesive,” he said.

“It activates it?”

“Yes, and that’s what helps it stay stuck.”

Huh.  I’d only heard that once before (earlier in the day, from Abby in the instagram comments section), but apparently it’s true.  In order to DEXCOM ADHESIVE, ACTIVATE!, you need to press down on the adhesive part.  Is that common knowledge or just instinctively done by most Dexcom users?  For me, it was just something I did without thinking, kind of like riding a bike.

tl;dr – The rash is gone. Make sure you press on your sensor adhesive.  Write a blog post about it once in a while to confirm that the rash is still MIA.  And long live sensors that expire after 08/15/17!

Your moop or mine?

The first flight out was jumbly, with the plane riding into some kind of air pocket right after takeoff, eliciting audible screams from some of us.  (No, not from me.  Turns out that, if things get scary, I resort to frantically saying the F word under my breath whilst clutching the arm rest.)  Once the plane hit some smooth air, everyone breathed a little easier and tried to mellow out.

In the silence of folks calming down, I heard that low, moop sound that the Dexcom G5 app makes when it is ready to be calibrated, like the sonar ping from a submarine.  It’s subtle but unmistakable.

Moop.

My sensor was fine when I boarded the plane.  I pulled out my phone anyway, just to make sure my CGM wasn’t crying for attention.  Huh.  Not me.  Sliding the phone back into my purse, my peripheral vision caught the movements of the woman next to me, who had her phone in hand and I could see the little pigeon head I knew by heart.

“Type 1?”

She grinned.  “Yeah.”

“Me, too.  Since I was seven.”

“I was 13.”

“I thought it was my CGM that needed to be calibrated,” I said, gesturing towards my phone.  “But it was you this time.”


It’s the thread that runs through all of us, that instant and unfettered understanding of the thing that simmers on the back burner some days and threatens to burn the house down on others.  I know that feeling. So did the woman next to me.

Instantly, she became familiar. I didn’t know her name or where she lived or what kind of history she brought on board with her, but there was an instant connection of, “Yeah, me too. I know that thing you have. I also moop.  And beep. And check. And worry. And celebrate. And dose. And fight. And laugh. And keep perspective. And move on.”

The Follow Up About Dexcom.

Today is Day 7.  I’ll be pulling this sensor off in six hours.

Day 7. No filter. No rash. No worries. #dexcom

A post shared by Kerri Sparling (@sixuntilme) on

No rash.  No filter.  Does this mean no worries?

(For reference, this post is a follow up from a week ago when I put on a Dexcom G5 sensor and transmitter without a barrier underneath the sensor.  For the last four and a half years, I’ve had an allergic/irritation response to the sensor.  Big, scaly rashes would blister up and take weeks to heal … like the one currently on my left thigh.  But rumor had it that sensors with an expiration date past 8/17/2017 were not causing this rash reaction.  

So I tried a 11/2017 expiration-dated sensor and the result?  No rash. NO RASH! The only issue I noticed was some blood around the transmitter after inserting it, but I wonder if that happens more often than I realize and the Toughpad had previously kept the blood from being visible. Whatever the case, I’m not itchy yet and I’m really, really hopeful that this rash issue is tabled forever. Next question is what to do with the box of sensors that has a pre-August 2017 expiration date …)

The One About Expiration Dates.

On the Dexcom and Libre Rash Facebook group, I saw a note posted back in December from someone referencing sensors with an expiration date after August 17, 2017.

“Dex recently changed their mfg process to eliminate a substance that caused rashes in some. Get some expiration date AFTER 8/15/17 …”

Huh.  Interesting.  (Read: HOLY SHIT COULD THIS BE TRUE??!!) I’ve been experiencing a Dexcom adhesive rash since 2012 and despite many conversations with clinicians and diabetes device industry specialists, no one has a solution for this issue.  (No one openly acknowledges this issue, either, which I find weird.)  For several years, I thought I was the only one having a rash reaction to the sensor adhesive, but then the Facebook group popped up and holy shit, there are a lot of us.  (The group currently has over 1900 members.)

Since 2012, I’ve tried several workarounds for this rash issue.  Steroid inhaler spray, barrier tapes, the blessed JnJ Toughpad … nothing eliminates the rash completely but the Toughpad does the best job of giving me seven days of sensor wear.  Fine.  The data and protection I get from using a CGM is worth the itch.  (See also: two solid pregnancies, two healthy kids, an A1C I’m happy with, and a marked decrease in overnight hypoglycemic events.  See also also:  “hypoglycemic events” is a stupid name)

Expiration investigation.

A post shared by Kerri Sparling (@sixuntilme) on

My previous sensor shipment has an expiration date of August 7, 2017.  The shipment I received last week expires in November 2017.  Even though I have a couple August expiration sensors left to use, I’m skipping ahead.  I want to know if the rumors are true.

New one goes in in a few hours.  Here’s hoping.

 

Enjoy the Silence. Or Not So Much.

[Disclosure about my relationship with Dexcom]

During the first trimester of this pregnancy, lows were intense and weirdly symptomatic; a nice contrast from the hypoglycemia unawareness that’s crept in over the last five or six years.  (I ended up stashing a jar of jellybeans in the dining room hutch, only to have to move it into direct line of sight in the kitchen in efforts to keep up with the persistent low blood sugars of those first few weeks.)  As this pregnancy has moved forward, the lows have become slightly more predictable and the hypo-unawareness has returned, making the Dexcom BEEPS! and BLARGHS! more necessary.

Until that week when I noticed, “Hey, the alarms have been quieter.”  And then I realized, “Hey, the alarms aren’t working.”  Because overnight, my G4 receiver had been rendered mute.

When I received the Dexcom recall notice several months ago, it was very early February, and I was still using the G5 transmitter.  At the time, the only people who knew I was pregnant were my family and my medical team, but I knew, and I was stalking blood sugars with vigor (and a side of panic).  My endocrinologist, not a fan of the data output from the G5 application, asked if I would consider using the G4 for the remainder of my pregnancy.  Wanting her to check the “compliant” box on my chart (there’s a first time for everything), I switched back to the G4 the following week and have been on it since.

And for months, my G4 receiver was fine.  Alarmed all the damn time, vibrating and buzzing from my bedside table or my purse and alerting me to the changing needs of my baby-hosting body.  And then, all of a sudden, the speaker went full garbage, not working at all.  Only a vibration came from the receiver, making my phone* the best laid plan for alerting me audibly.

It wasn’t until I woke up one morning and saw the empty raisin box and the discarded juice box that I realized the night before wasn’t very comfortable.  And that I didn’t wake up because of alarms, but instead because of aggressive baby kicks.  I couldn’t ride out the rest of this pregnancy without replacing the receiver, because I was NOT waking up even with the phone alarms.  I needed high octane, receiver-in-a-glass-with-some-coins sort of jolting.  I needed to connect the alarms to Siah, encouraging her to walk across my face when I was low.  Or similar.

I needed the receiver to actually WORK PROPERLY.

So I went to the website – Dexcom has a special page set up for this particular issue.  There’s also a special hotline number to call: (844) 607-8398.  After a quick exchange with the woman on the phone, she asked me to confirm that my alarms weren’t working by doing the following:

  • press the center button on your receiver to access the Main Menu
  • scroll down to Profiles
  • select Profiles
  • scroll down to Try It
  • select Try It
  • scroll down to 55 Fixed Low
  • select 55 Fixed Low
  • verify that you receive vibrations first (vibratory portion of alarm), followed by beeps (audible portion of alarm).

And once we confirmed the alarm absence, a new receiver was scheduled to be shipped out.  Should be arriving in the next few days, in time for me to finish up this pregnancy as a G4 user (to make my doctor happy) and hopefully by staying in my threshold lines (to make my fetus happy).

If your G4 receiver suddenly craps out, sound-wise, call the hotline number and have a new one sent out.  Alarms that won’t alarm are alarming.

(* I follow myself on the Dexcom Follow app, along with one other person.  Yes, redundant.  In response to the dead receiver speaker, I changed the alarm settings on my phone so that I’d be alerted for highs and lows.  This worked, in theory, except when my phone was on silent or in the other room.)

Follow

Get every new post delivered to your Inbox

Join other followers