Spectral Features Dominate BCG Respiratory-Event Detection: A Large-Scale Patient-Independent Comparison of Feature Groups in Sleep Apnea Patients

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.28242v1 Announce Type: new Abstract: Unobtrusive ballistocardiographic (BCG) sensing is a promising modality for long-term sleep-apnea monitoring, yet it remains unclear which signal features are most discriminative for respiratory-event detection. We present a literature-guided, patient-independent comparison of ten BCG feature groups using a 512-sensor capacitive pressure mat recorded simultaneously with respiratory polygraphy in 155 patients (52 female, 103 male) undergoing in-hospital evaluation for obstructive sleep apnea. Features were extracted from six spatially distinct signal channels, yielding a 191-dimensional feature vector spanning general statistical, time-domain, frequency-domain, wavelet, frame-energy, and nonlinear complexity descriptors. Under strict leave-one-patient-out cross-validation for binary classification of respiratory-event windows versus event-free reference windows, Random Forest and Histogram Gradient Boosting achieved AUC-ROC of 0.967 and 0.969 and AUC-PR of 0.977 and 0.979, respectively. Feature-importance analysis revealed that frequency-domain features dominate discrimination: breathing-band power in the 0.1-0.4 Hz range accounted for 30.3% of total discriminative information across all spatial channels, and Fast Fourier Transform spectral-shape descriptors of the adaptively preprocessed channel contributed a further 15.1%. AUC and curve-length features provided the main complementary time-domain evidence (21.5%), whereas wavelet-derived and nonlinear features contributed smaller secondary effects (10.4% combined across 59 …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.28242
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.