Scuba Diving with dexcom G5


#21

I have a question… I am diving in Iceland in a week with a dry suit of course and wanted to know what people’s thoughts were on keeping the dexcom on during diving since it won’t be getting wet. Diving no more than 35 feet so pretty shallow but wanted to know if anyone knew about pressure and it affecting the dexcom??? Any help appreciated. Thanks


#22

I am T1D and am currently DiveMaster in training with Padi. Recently forgot that I was still wearing my Dexcom G5, went on a 45feet dive for about 35 minutes. Once back at the car, my iPhone registered an ideal glucose value, and gave me a profile for during the dive, too. So 45 feet for 35 minutes no problem! Gabby diving!!!


#23

My son has a G6. Doesn’t seem to be a way to remove the transmitter without breaking the sensor in the process. He is 12 and I’m teaching him to dive in the pool. Any suggestions on removing the transmitter and just keeping the sensor on and using some type of wrap to keep it somewhat protected from water log…??
He loves to snorkel so this was the next step.


#24

So, what are you doing with your CGM while you are diving. Do you normally remove it or have you been keeping it on while diving and just start the dive a little high and bring a gel pack with you if you feel low?


#25

So I have gained a little more experience with the G5 while diving. These are my experiences only and should not be taken as professional medical advice!

  1. I have recently run an experiment (repeated about 10 times) and have taken my G5 sensor with the transmitter down on scuba dives. All dives were between 45 and 75 feet. There were a few dives as deep as 106 feet. Upon return to the boat the receiver has registered the transmitter almost immediately, and displayed my BG levels in 5 minute intervals for the entire dive. --> The sensor and transmitter both can withstand 106ft scuba dives. I was wearing my 7mm wetsuit which helps with prevention of any mechanical issues under water, incl. failing glue.

  2. Do not take the receiver, as it is not waterproof. My procedure allows me to monitor immediately before I enter the water, immediately after, and gives me the history for the time during my dive. If you want data while under water you need to think pressure and waterproof but transparent containers. Not sure that is the way to go. If you control your BG before and after, you should be fine for the up to 60 minutes in the water. If not, as a professional I recommend calling the dive, which I have done several times out of caution.

  3. I have seen a significant impact of body hydration on the reliability of the readouts. If you go through cycles of hydration and dehydration the data will not be very reliable and appear “jumpy”. The same seems to be true on some occasions related to pressure. I mostly had good quality readings for times during my dives, but once in a while get noisy data readouts, likely due to a combination of surrounding pressure, hydration state, and insertion site for the sensor.

As far as BG levels go: I am trying to go in somewhere between 150-200mg/dL and then come out around 90-100mg/dL. During classes that I help teaching, especially when retrieving weights or during heavy surge, I go in a little higher just to be safe.

I recently came back from a deep dive (100+ft actual depth at 6250ft altitude), and I encountered severe problems keeping my buoyancy upon ascending around 25 ft. Turns out my BG had dropped below 55mg/dL, which could have been very dangerous at depth. So bring a gel, monitor closely, and consider energy consumption upon entry, and during the dive (surge, drift, search&recovery operations, …)

Sorry for the long response, but I hope it provides some valuable information for others, too.

I recommend this very well written article from DAN:
http://www.alertdiver.com/Diving_with_Diabetes


#26

I actually started a thread on this question a couple of weeks ago and was surprised to find out that it is actually doable. I think there are some how-to videos on youtube about it as well. Here’s the thread: