Apnea Board Forum - CPAP | Sleep Apnea
Possible bug wrt Pulse Rate Reporting? - Printable Version

+- Apnea Board Forum - CPAP | Sleep Apnea (https://www.apneaboard.com/forums)
+-- Forum: Public Area (https://www.apneaboard.com/forums/Forum-Public-Area)
+--- Forum: Software Support Forum (https://www.apneaboard.com/forums/Forum-Software-Support-Forum)
+--- Thread: Possible bug wrt Pulse Rate Reporting? (/Thread-Possible-bug-wrt-Pulse-Rate-Reporting)



Possible bug wrt Pulse Rate Reporting? - hoselife - 02-22-2021

Hi! Thank you so much to everyone involved with OSCAR, it's truly wonderful. I may have stumbled upon a bug in how Viatom (and possibly other?) Pulse Rate data are reported. I noticed it because I looked a bit unusually healthy on my OSCAR stats (ha). 

With the first image here you can see Oscar is reporting the heart rate spike as being at 56.85 bpm. However, if you look to the y-axis to the Left, you'll see it is much closer to 75 bpm. The second image is from the Wellue O2 Ring's internal reporting. You can see from this image that this spike is indeed closer to 75 bpm. All the values seem to be similarly underreported.

Unrelatedly, I note that when I go to Preferences --> Oximetry and try to change the values for flagging, then hit OK, if I return to this menu, those values have always reset. This seems to be an separate bug impacting flagging on the basis of custom HR or SPO2 rates.

Thanks again!


RE: Possible bug wrt Pulse Rate Reporting? - kappa - 02-23-2021

I would zoom in (drag over) that section around the spike and ensure that you are actually measuring the peak. At that resolution there's too much chance you are missing the actual peak of the spike. I have no issues with viewing exact pulse rate values provided you are zoomed in sufficiently. CPAP values have issues if you have clock drift configured (will be fixed in the next release).

Regarding the flagging values, I think that's a known bug. There's a comment from sawinglogz that 'This isn't specific to Viatom. Those fields don't work at all. You need to change the threshold in Preferences > Waveforms > Oximeter Waveforms' but I'm not sure how that helps... might take a look at it myself.


RE: Possible bug wrt Pulse Rate Reporting? - Crimson Nape - 02-23-2021

The Viatom/Wellue devices sample in 4-second intervals.  For some reason, the ViHealth app, for Android and iPhone, records samples at a 2-second interval by repeating each value.   Each value is reported as an integer, meaning that each number is a whole number without any decimal component.  With the spike coming from a 58-ish to a 77-ish at the current zoom resolution and the value displayed is a decimal value, it is very possible for you not to be directly on the exact point but slightly askew.  Your current display is set at a 5-hour span (18000 seconds).  That equates to 4500 (18000/4) sample points being displayed. I would recommend that you zoom in to a 1 to 2 minute time span and look at the value at a higher resolution again.


RE: Possible bug wrt Pulse Rate Reporting? - hoselife - 02-23-2021

Crimson Nape, Kappa. Thanks for the explanation! I checked and it was definitely a resolution/interval issue on my part. Should I delete this thread?


RE: Possible bug wrt Pulse Rate Reporting? - Crimson Nape - 02-23-2021

No, if you had this problem, then others might too.  Reading other member's posts serve to help educate oneself.

- Red