While busy at work one afternoon, I was listening to a Spotify playlist (as I often do), when I could’ve sworn I heard my Omnipod beeping to alert me to a failure.
Oh noooo…I thought. I remember sitting in my chair, with my head cocked and music blaring, as I tried to confirm that the beep was indeed emitting from my pod.
And then I realized…it wasn’t my pod after all. It was the song that I’d been listening to. Roughly 2:45 into the song “Honestly” by Cartel, the music rose to such a crescendo that I could’ve sworn that it was my pod failing, but nope, it was just the pitch of the sound emitting from my speakers.
What a relief! But also a stark reminder that this phenomenon occurs on the regular. I mistake beeps from standard household appliances, alarm clocks, television commercials, and the outside world in general for Omnipod beeps. And I’m struck by it every single time.
The sounds of diabetes, just like diabetes itself, are just something I’ve come to accept – in the many unique forms they appear in.
I mused to myself as my Dexcom vibrated incessantly, alerting me to the state of my blood sugar.
I’ve actually been wondering that very thought (and cursing out loud about it) more often than I’d like in recent weeks.
It’s been about 3 weeks since I started the Omnipod 5, and I guess my high hopes for the system to revolutionize my blood sugars came to be a little too literally. The 5 has been a godsend in terms of 1) helping me sleep through the night as I’ve only woken up once this month to correct a low OR high blood sugar and 2) catching lows before they happen or before I have to eat something in order to bring my BG back up.
But what the 5 and I are struggling with is the exact opposite of the latter, and that is catching highs before they happen – and then reacting accordingly. I’ve found that I’m dealing with more rapid and prolonged spikes than I thought I’d be. I’m doing what I can to proactively treat them myself by bolusing when they occur, but for some reason, it seems to take a solid 2-3 hours for my blood sugar to come back down nearly every time.
After consulting with some of my diabetes pals about this, and giving it some further contemplation, I’ve got a 3-step action plan to combat these highs:
Give my Omnipod 5 more time to learn my body’s patterns – I’ve heard across the community that it can take several weeks for this to happen most effectively, so I need to try to be patient and wait for the results to occur.
Continue to correct for highs when they occur, and do so swiftly. One of my colleagues said this helped a lot in the beginning, so I will continue to monitor for highs diligently and not be shy about bolusing for them (as long as I’m not stacking insulin too much).
Pre-bolus, pre-bolus, and pre-bolus some more. I’ve always been a believer in the power of the pre-bolus, especially since I know that Humalog typically takes 60-75 minutes to start working in my body. I’m going to build pre-bolusing into my schedule and try to do it at least 30 minutes before I actually eat each of my meals, and we’ll see where that takes me.
Hopefully, this plan of mine coupled with my automated insulin delivery system will nip these high episodes in the bud before long. I can’t wait for “why, high” to become “smooth sailing” and translate into beautiful, level Dexcom graphs!
As of this writing, I’ve been wearing my new Omnipod 5 pump for about 2 ½ days. I will be changing my first Omnipod 5 pod later this evening, but before then, I wanted to jot down my initial impressions of the system as a whole so far.
The PDM: A bit larger and more brick-like compared to my Dash PDM. Actually, the size is pretty on par with my iPhone. I like that the screen is larger and it seems more sensitive to touch than my Dash – all good things. Except I can’t figure out why it makes chiming sounds only sometimes after I enter my PIN! I’m sure I’ll learn the cause of that eventually…
The pod: Basically indistinguishable from my Dash pods – the only difference I’ve spotted (or rather heard) has to do with the mechanical ticking sound my pod makes when it’s delivering my basal insulin. The old pods had a set frequency, whereas the 5 pods seem to go “tick, tick, tick” in bursts of three or so. Not sure why, but I know I’m still getting my basal rate delivered, which is what counts.
The set-up: Inputting all of my settings into the 5 only took me about 15-20 minutes. It was so easy that it likely would’ve taken me less time if I wasn’t so thorough and careful about triple-checking my settings. I also think it was relatively seamless for me because I was already familiar with 90% of the PDM’s functionality – the only thing I had (and still have to) explore further is automated mode…see below.
Automated vs. manual modes: I can go back and forth between automated (insulin delivery is automatic and the system responds to highs and lows based on data it receives from my Dexcom) and manual (I have to make my own adjustments, just like I did with the older versions of Omnipod). This was a helpful feature for me because I inexplicably got scared of automated mode the first night I wore the pod. I didn’t know what to expect from it – should I trust it right away? Would I notice it working? What if it didn’t? Ultimately, I decided I wasn’t comfortable going to sleep in automated mode, so I kept manual mode on because I wanted to have more control. I waited until the following morning before I turned it on, and since then, I’ve been on automated mode and I’ve spent a solid chunk of my time in range. A few highs here and there, but all my lows seem to be detected before I drop too much, which is just awesome.
Dexcom integration: Similar to the overall set-up of the system, it was extremely easy to get my Dexcom synced up with my Omnipod. All I had to do was enter the 6-character transmitter ID into my PDM and give it a few moments to pick up my Dexcom’s signal. And that was it! I’m sure things will get a little more dicey on days that I have to do both a pod and CGM change (coincidentally, I’m going to do just that in a few hours for the first time…eek), but I do have confidence in my ability to time the changes well so I don’t go without automated mode or Dexcom data for too long.
Let’s talk about sleep: The indisputable best part of this system so far is that I’ve slept soundly the past 3 nights. No CGM alarms going off and waking me up, no frantic shoving of food in my mouth from my bed or late night bolus delivery. And best of all, no waking up in the morning out of range. Now it’s not like that before the 5, I was waking up every night to do something diabetes-related, nor was I starting off each day with a high or low. But I was getting to a point where these things did happen at least on a weekly basis, and naturally, I was getting tired of it. So while I’m acutely aware that I need more time to get to know the system (and it also needs to figure me out), I have hope that it will help me make a major improvement in my diabetes care and management.
All in all, it’s been a relatively smooth start for me and my Omnipod 5. I totally expect some bumps down the road, because that’s normal when starting up any new piece of diabetes technology. But for now, I remain grateful for a comfortable transition to the system.
It arrived on a seemingly ordinary Wednesday, during a week in which I really needed a pleasant surprise.
I opened my front door to take my pup out to do her business when I noticed a large package on my front steps.
I wasn’t expecting anything to come in the mail, so I eagerly tore into it once my dog and I returned indoors.
And this sight was before me:
Yup, I’m the proud owner of an Omnipod 5 – finally!
I won’t be starting it until early next month, though. And I’ve got good reasons to delay it: 1) I’m traveling a decent part of August and I know from experience (or shall I say, my dear mom’s experience) to never try new diabetes technology when you’re out of routine, 2) I have about a month’s worth of old pods to use up before I officially switch over – I can’t imagine not using up my full supply just so I can get started on the new system faster. As I’m sure you must know by now, diabetes supplies are extremely expensive and I am diligent about using up every last pod, CGM sensor, and of course, insulin vial, before it goes into the trash.
While it’s a bit of a tease to know that automated insulin delivery is literally just feet away from me right now, it’s mostly very exciting to know that I have this to look forward to in the coming weeks. It’s nerve-wracking to go on new d-tech, yes, but the rave reviews of the Omnipod 5 have far outweighed any anxieties I have about starting the system.
And once I do, you can bet that I’ll be blogging about it!
This blog post was originally published on Hugging the Cactus in 2019, and again in 2020. I’m sharing it for a third time because 1) it’s one of the most popular posts I’ve ever written and 2) it’s STILL an issue debate among the diabetes community! My opinion on bleeders being readers hasn’t changed. Read on for more (and be warned that the topic might make you a little squeamish, if you wince when talking about blood).
I placed the new Dexcom G6 sensor on my abdomen, hovering my index finger above the large orange insertion button. I pressed it, exhaling as I felt the minute needle pierce my skin’s surface. I looked down, and started to rub the adhesive in circles to make sure it was stuck, when I saw blood. Not just a drop, but a decent-sized pool forming beneath the sensor. Before long, just about the entire surface of the white adhesive was soaked in red.
Yeah, this was going to be a no-go.
It’s pretty rare for me to experience blood at the site of a Dexcom sensor. If I had to put a number on it, I would say less than 10% of my insertions draw blood. An even smaller amount – like, 2% – have caused me to bleed as much I did in the scenario described above. But I know I’m not alone in my bloody sensor experiences – it’s something that many other T1Ds who use a Dexcom have gone through.
There’s a bit of debate, though, that I’ve noticed in the past on Twitter threads and Instagram posts. What to do with a bleeder? Keep it and assume that it’ll read blood sugars normally? Or change it immediately and call Dexcom for a replacement?
Are bleeders readers? Or does it depend?
I’m going to go with…it depends.
Obviously, in that situation I described in the opening of this post, I decided that it wasn’t a good idea to keep the sensor on my body. There was too much blood and I didn’t trust that it would adhere well to my body. I didn’t know how long it would take for the blood to stop (only a few minutes, but still), and I couldn’t be sure that it wouldn’t mess up my readings. On top of that, I wasn’t trying to stain my clothing, if I could help it.
So in that circumstance, I did change my sensor right away, and was glad that the second try resulted in a much cleaner, blood-free insertion. I called Dexcom, explained what happened to the customer support representative, and got a replacement sensor mailed to me.
However, just about any other time I bleed upon a sensor insertion, it tends to be a minuscule amount of blood. I usually don’t even notice until it’s time to replace the sensor, and there’s a bit of dried blood left on the site. Other times, I’ll see small beads of blood forming underneath the spot where the transmitter snaps in. And there’s been a couple of occasions that I’ve bled a fair amount and been totally unaware of it until I caught my reflection in the mirror and noticed the blood staining the white adhesive. And in all of those cases, I’ve kept the sensor on for the full ten days, without noticing any discrepancies in my readings.
All that considered, in my inexpert opinion, I think that bleeders usually are readers and that they’re safe to continue wearing. Of course, there will be exceptions, like when there’s just too much blood to salvage the sensor. But every time I’ve kept using a bloody sensor, I’ve had the same amount of success with its functionality…so yes, I think that for me, bleeders are indeed readers.
The latter half of July in New England has been hot, hot, hot this year. It’s almost pleasant compared to last year’s rainy summer months, but let’s emphasize “almost” in that sentiment.
Fortunately, something that makes the heat a bit more bearable is the fact that the condo complex that I live at has a pool! And what’s even better is that it’s pretty easy to find slots of time on the weekends to hang out by it and enjoy it undisturbed by other community members. Case in point? My boyfriend and I found an hour on a scorching Sunday evening to take a dip before grilling some chicken and veggies for dinner.
We had only just entered the pool up to our waists when a familiar screeching sound blared in our ears. Yup…my pod had just failed.
Rather than get cranky about it, though, I just shrugged and figured it was no big deal, I had to change it in the next few hours, anyways. I was about to rip it off my abdomen when my boyfriend pointed out that the moment I submerged myself more fully in the water, then I wouldn’t hear the screaming pod anymore. Sure enough, he was right – I could only hear the shrill sound when I was underwater, making for an interesting soundtrack whenever I swam under the water’s surface.
We swam and chatted for about an hour before deciding that I probably shouldn’t procrastinate any longer when it came to putting on a new pod. So we dried off and headed inside, and discovered that my blood sugar had lingered in the low 100s the entire time. That was a welcome sight to see – my assumption is that I’d had enough insulin on board from earlier in the day that coupled with the exercise I got from swimming to prevent any sort of blood sugar bump.
So even though I literally swam right into a pod failure, it worked out in a funny way. It’s nice to know that pod failures don’t always have to be a total nuisance.
This was originally published on Hugging the Cactus on September 7, 2020. I’m sharing it again today because my mom and I were recently talking about pod placements and the places where we would (and would not), hypothetically, feel comfortable wearing a pod. It got me thinking about how I’ve had to work up the courage to try new sites over the years, which inspired me to write this post to hopefully help others who feel the same way about navigating new pump sites and nerves. Read on for more…
Am I the only T1D out there who feels incredibly nervous about trying new insulin infusion sites?
I’ve been this way as long as I can remember, now that I’m thinking about it. Throughout my childhood, I stubbornly stuck to injecting in my arms, legs, and upper buttocks (tee-hee) because those were the areas I felt comfortable with. I don’t think I even considered jabbing myself in my stomach until I was in my teens, and it was only after I realized the importance of site rotation and reducing scar tissue.
So it’s kind of funny that when I went on the OmniPod just over five years ago, I only used my stomach and my lower back (just above the upper buttocks region, tee-hee) for pod placements. It was partly because my guinea pig – I mean, my mom – used those areas for her pods with success, and also because I was hesitant in the beginning to wear my pods on my arms or legs because of their increased visibility.
It went that way for a couple of year – four basic sites ’round my abdomen – when it occurred to me yet again that site rotation was also important for insulin pumpers, not just MDI-ers (multiple daily injection…ers). So I added my upper arms into the mix, and soon after, my upper thighs followed.
But lately, I’ve shied away from wearing pods on my thighs because the area isn’t overly comfortable. When I roll over in my sleep at night, my pod presses up against my leg and the resulting pressure is just enough to disrupt my sleep and make it difficult for me to find a more restful position to sleep in.
As a result, I’ve started contemplating potential new pod sites, and one of the first places I went to for advice was…Instagram! Because…duh.
The DOC (diabetes online community) on Insta is a natural resource for this sort of thing because many people tend to share photos of their sites. It’s kind of a thing. One simple scroll through my feed taught me that people can get very inventive when it comes to finding new locations to place their CGMs and insulin pump infusion sites.
I saw people wearing Dexcoms on their forearms and calves. I saw pods on backs, calves, and even the upper chest area, the latter of which I found most intriguing. For men, it seems like a very accessible spot that causes little irritation, but for women? How the heck did the T1D ladies I saw with pods on their chest deal with it?
The general consensus, it seemed, was that women wearing pods on the upper chest agreed it was a site with great absorption and minimal discomfort.
I was still skeptical, though. I was worried about how it would look if I was wearing a v-neck tank with my pod poking out of, well, my bra! Then it hit me that my pod garners questions from strangers regardless of where it’s located. Furthermore, people will (probably?) be less likely to ask about it if it’s located on my chest because, um, that’s really awkward. My eyes are up here, people!!!
Then I remembered: I could give the site a try without wasting a pod because I have a demo pack that I got from a diabetes conference awhile back! The demo pack comes with a dummy pod that looks and feels just like a regular pod, but there’s no reservoir built into it, so insulin can’t be injected into it.
So right now, as I’m writing this, I’m wearing two pods: one on my upper arm that’s actually giving me insulin, and a fake one on my chest just to see how I like it. I must admit, so far, so good! I slept comfortably with it on last night and I haven’t had any issues wearing clothing or undergarments with it. I even went for a jog with it on and got pretty sweaty, but it stayed secure/I didn’t feel it bouncing around at all (thought the adhesive got a bit too damp for my liking…it stayed on but if I wasn’t careful I totally could’ve knocked it off).
While I’m still having a hard time wrapping my head around an actual cannula piercing my skin at this location (eeeek), now that I know I can handle the pod itself living there, I’m one step closer to trying (and liking) a site that’s more intimidating to me – a win in my book.
You’d think that 24 years of living with diabetes would turn anyone into a seasoned veteran of the condition, but even the most experienced people with diabetes slip up and make mistakes every now and then…
Case in point? Me, because I neglected to make sure I had a way of monitoring or checking my blood sugar when exercising…and then experiencing a scary low that I probably could have caught sooner, or maybe even avoided, if I hadn’t been so careless.
This all happened because I inserted a new Dexcom sensor just before taking off for my 3-hour self-defense class. I knew that the sensor’s warm-up period would end and that my continuous blood sugar readings would begin partway through class, so I felt fairly comfortable going without a blood sugar meter as a back-up. After all, my Dexcom sensors almost always start up without any issue, so I was trusting that this one would follow suit.
And that was my biggest mistake: trusting my technology.
When the warm-up period was complete and the class was taking a quick water break, I decided to check my Dex to see what my first blood sugar readings were. I was surprised (and instantly annoyed) to see that instead of a number, my Dexcom was displaying a request for a blood sugar calibration – just like the old G5s used to ask for upon insertion of a new sensor. I couldn’t understand why this happened, but I knew that pondering the matter wouldn’t make any difference…the only thing that would get my Dexcom running normally again was the finger stick checks, which wouldn’t be possible for me to do until I got home from the class because I was without my meter.
So I had no choice but to rely on nothing but my instincts and sensations in order to get a sense of where my blood sugar was headed for the remainder of the class.
And let me tell you, I can’t remember the last time I felt so vulnerable in terms of my diabetes. I was running on zero information, other than the fact that I typically can feel oncoming low blood sugars and that I tend to feel thirstier when my numbers are on the upswing. It was disconcerting – even more so when a little while later I started to feel shaky and dizzy, like I was starting to go low.
I knew I could either 1) treat what I thought was a low blood sugar and deal with the potential consequences (high blood sugar) when I got home, or 2) take a chance and ignore the low symptoms because I couldn’t confirm whether or not I was actually low. I hate to admit it, but I let a good 15-20 minutes pass before I decided it was better to correct what felt like a low rather than run the risk of passing out in front of the entire class. Turns out that I made the right call to treat my low: I felt much better after I ate some fruit snacks, and my blood sugar when I got home that evening was in the low 80s, indicating that I probably avoided a pretty nasty low in class.
While the whole incident could’ve been easily avoided, it did remind me that I ought to take some of the trust that I have in my technology and distribute it a little more evenly between it and my instincts. I proved to myself that in emergency situations, I don’t need a meter or a CGM to pick up on low blood sugars (though I obviously would prefer to have that equipment at my disposal at all times). Instead, I need to trust my instincts more and procrastinate less when it comes to taking an action – because if I had waited longer than those 15-20 minutes, the situation could’ve escalated and then I would’ve really been kicking myself for leaving my meter at home.
Rookie mistakes suck when they happen, but at least the silver lining is that there’s always a lesson to be learned (or reinforced) when they do.
This blog post was originally published on Hugging the Cactus on February 26, 2021. I’m sharing it again today because I see folks trying new Dexcom sites all the time, usually with a lot of success! I thought it was worth it to share my experience with the forearm site because it was the polar opposite of a win for me – read on to learn why.
I don’t usually regret trying new sites for my Dexcom and OmniPod.
But recently, I discovered the one area that I wish I hadn’t tried…and that is my forearm.
For a couple years now, I’ve seen forearm Dexcom sites all across social media. People lauded the location for how comfortable it is and the accurate readings it produces, so I figured, why not give it a shot? (LOL diabetes humor.)
Plus, I wanted to give my stomach and the backs of my arms a break. I put both pods and sensors in those locations and while I like them a lot, I’m wary of scar tissue building up.
So with little fanfare, I tried putting my Dexcom on my left forearm (my non-dominant arm). And I knew immediately after hitting the orange button to insert the sensor that it was a bad choice because it STUNG. It stung something fierce! I remember wincing the moment it pierced my skin, and fortunately, the pain did go away…but resurged with a vengeance about half the time I made any arm motions. It didn’t matter if I was flexing it up or down or twisting it to reach for something – any movement could trigger varying degrees of pain. Nothing incredibly intolerable, but enough to make this site uncomfortable.
And this pain didn’t altogether disappear one day: I still felt stings 24 hours after I put the sensor on. Maybe I hit precisely the wrong spot (I noticed a very small amount of blood discoloring the white adhesive of the sensor), but I asked the diabetes online community and it seems that the general consensus is that this location sucks. The half-dozen or so people who messaged me said that either the pain was too much and they took the sensor off early, or they toughed it out for a full 10 days and never used the site again.
What’s more is that this site wasn’t as out-of-the-way as I wanted it to be. I roll up my sleeves dozens of times each day for different tasks, and each time I went to roll up my left sleeve, I had to go about it gingerly so I didn’t risk bumping into the site and prompting ripples of pain. This was straight-up annoying because my diabetes devices don’t usually inhibit my movements so much.
The one plus-side of trying the new site, and the only thing that motivated me to keep it on for the full 10 days, is that it was just as accurate as any other Dexcom site I’ve tried. My readings matched up pretty closely with how I felt and with what my blood sugar meter reported, so that was a saving grace. And I have to admit that even though I was worried that sleep would be impossible with the sensor in such a tender spot, it really didn’t interfere with my slumbers, which was a relief.
All in all, though, the accuracy wasn’t enough to convince me to want to keep forearm sites in my regular rotation. I’ll stick with abdomen and upper arm sites for now, with the occasional thigh site to further prevent scar tissue.
Between this post and the one from a couple of weeks ago, this blog is rapidly turning into one in which I bemoan the battery life of my diabetes devices…
The fact of the matter is, though, that I’ve definitely had my share of battery issues lately. The Omnipod DASH problem was resolved (rather swiftly), thanks to the folks at Insulet. But now it’s my Dexcom transmitter battery that’s acting up…and resulting in a whole lot of lost data (and even more frustration) for me.
It all started about a week and a half ago, when my Dexcom app notified me that my transmitter battery would be expiring in 3 weeks. That was to be expected – Dexcom transmitter batteries last 90 days, and according to my records, the one I’d been using was for sure approaching the expiry date.
What I didn’t expect was that the waning battery life in my transmitter would trigger multiple false blood sugar readings and periods of no readings whatsoever. At least I think my transmitter is to blame – I hadn’t experienced any issues with sensors from my last shipment and the app usually never experiences errors like this unless there’s a problem with the sensor and/or transmitter, so logic led me to conclude that my transmitter was simply losing reliability as it came closer and closer to its expiration.
My workaround was to do finger stick checks any time I was untrusting of my Dexcom, or whenever it was giving me a “no readings” alert. Plus, I’ve got a fresh transmitter ready to be activated once this one stops working, so it’s not like I’ll be without a Dexcom for an unbearable length of time.
In spite of that, I still thought this was worth talking about here on the blog because 1) I can’t remember if I’ve ever had a transmitter fade so dramatically in the last 3 weeks of its lifespan, 2) it was an exasperating situation and I needed to vent, and 3) I’m wondering if this has ever happened to anyone else before, and if there’s a workaround.
At this moment in time, I’m not quite sure what a feasible solution would be besides ripping a sensor off prematurely and sticking to finger stick checks for a few days until my annoyance ebbs…which is exactly the strategy that I decided to go with. I’m definitely looking forward to new transmitter time…