Earlier, as I was grappling with the data from my DreamStation bPAP (DSX700), I wondered aloud on the forum about exactly what algorithm was used by SleepyHead or DreamStation software to declare an OA or obstructive apnea event. After an overnight sleep test, I was diagnosed with severe obstructive sleep disorder and had reported AHI values > 40, with OA events counts usually in excess of 200 per night and CA counts that were either really low or, sometimes, around 100.
We have been struggling to get the bPAP settings right and various forum members have been incredibly helpful. I am using supplemental O2 (4 lpm) through the mask at least until we get this thing better understood and treated. Trying to make the DreamStation/SleepyHead AHI/OA/CA/HA numbers better has been a real struggle. And, I could not make subjectivesense of the OA counts when I tried to map what was happening in the 2-20 minutes while I was falling asleep to what the record showed the next morning when I downloaded the data.
I do want to quickly add that despite current AHI and apnea counts, I am sleeping much better and feeling more energetic. Whether that is the cervical collar, the supplemental O2, the bPAP machine....we don't know yet.
Meanwhile....
I've been recording O2 saturation and pulse rate every night on my Masimo MightySat along with my bPAP data...and over the weekend, I wrote some code to dig into this a bit more. The Masimo bluetooth stream the data to my iPhone in real-time...and I can email myself the 25,000+ time points in a csv file when I wake up.
Here's the hypothesis for your consideration:
All the OAs & CAs & HAs in the world really don't matter as long as you are not desaturating. If your O2 saturation wobbles around between 90-99 all night long....you are not in trouble. It's "severe" desaturation that is the concern...and this is usually defined as at or below 88%.
So now, let me share data from last night.
First, here's the entire night's PulseOx and heart rate record from the Masimo MightySat. The little green "+"'s mark desaturation events which were defined as periods with O2_Sat<=88%. The time resolution of the MightySat is 1 second and I defined as a desat event 1s or more of PO2<=88. The straight black line indicates the user-set threshold of 88% saturation. There were 19 desaturation events which tended to occur in bursts. Over 8.6 hours of sleep, I was at or below desaturation threshold for about 10 minutes, total. More time details of those desat events are in the figure.
The Dreamstation numbers seen in the figure (upper left) are from the DreamMapper app, not SleepyHead. PulseOx data are longer than bPAP data....because I start the PulseOx before and stop after starting and stopping the bPAP.
Now, here's a magnification of the time axis to focus in on one of the DeSat bursts, composed of 4 deSat events, that occured around 2AM.
So....what do we learn from SleepyHead and the bPAP data?
49 CAs, 20 HAs, 187 OAs, and AHI = 29.96.
The next figure takes the detailed pulseOx graph and lines it up on top of SleepyHead graphs, zoomed in to have the exact same time period. At the top of the SleepyHead record is, as usuaal, the full timeline with all the events marked...the CAs, the OAs, etc etc. The zoomed graph show 4 of the 19 total desat events I recorded last night.
For the 3 longer deSat events, they were associated with BND events and two of them were associated with CA events. But note that there are other CA and OA events called by the software that are not associated with any significant desaturation. Are they false positives?
For me, I don't think the SleepyHead Event record is particularly helpful....in my case. Your case may be different. But, if you can see some value in my records, please share the insights.
I think it makes most sense for me to focus on O2 Sat/deSat and not worry about making machine or mask or any other adjustments to change any other measurement. Just focus on O2 Sat.
What do you think?
Thanks in advance for your feedback, suggestions, and comments.