Differences in the Wellue O2 Ring App Data Results and Oscar Data Results on the same

[mikep118]

Hi. I noticed something very interesting when importing my O2 Ring session into Oscar. The O2 App results as shown in the screenshot and the same data imported into Oscar are telling me 2 different things. Obviously the criteria must be different so im wondering which one is right. For example as you can see in the screenshot of the App report results that my Drops of more than >4% are 1 and my drops per hour are 0.2. My drops below <90% are 0 and my O2 is a very good 9.9! So im thinking everything is fine but when I import this session into Oscar it is showing my desaturations or events are 88 which is 20 an hour which is not great. So what I thought was a really good report from the app turns out to be not great at all when interpreted by Oscar. So which one should I rely on. Obviously  Oscar considers a desaturation/event to be something very different than what the O2 app data results considers a desaturation/event to be? Kind of confusing.
Has anyone noticed this when importing the O2 Ring results into Oscar?
Thanks
Mike
   
   
   

[purplebear]

Hi! OSCAR uses 3% drop for a min of 10 sec (which, actually, is the new guideline for desaturations but 4% is still useful; just recently changed although lots of sleep docs have been focusing on 3%; many oximeters list both). Wellvue uses 4%. You can change the OSCAR setting to 4% in Profile/Preferences/Oximetry if the discrepancy bothers you. Cheers!

---

Forgot to add that it's unclear to me how OSCAR computes the SpO2 Baseline that it uses...doesn't seem to be 95%tile or 99.5%tile. This makes a big difference on the number of 3% desaturations computed. I can't find the determination anywhere...anyone know?

[Crimson Nape]

Not to rain on your parade, but the oximetry parameters in the preferences were never linked up to anything in the program. It is a holdover from the old SleepyHead code. It is on the "To-Do" list, though.

- Red

[purplebear]

Oh...my mistake...and good to know. Thanks for the correction.