DeMMO: Longitudinal and Cross-Disease Modelling of Digital Mobility Outcomes via Multi-Task Learning

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.25073v2 Announce Type: replace-cross Abstract: Digital mobility outcomes (DMOs) derived from wearable sensors characterise mobility in daily life and offer a promising means of monitoring disease progression. However, existing DMO studies have typically focused on either a single disease or a single visit. To the best of our knowledge, this is the first study to systematically model and analyse longitudinal multivariate DMOs across diverse mobility-limiting diseases. Specifically, we propose DeMMO, an interpretable framework for longitudinal, multi-disease, and multi-outcome learning. DeMMO represents each disease--outcome objective using a longitudinal DMO coefficient matrix and combines temporal regularisation with stable and visit-specific feature selection. Its central technical contribution is an automatic cross-disease and cross-outcome relation-learning mechanism that infers signed relations directly from these longitudinal mappings, thereby enabling selective information sharing across cohorts without requiring paired participants. We evaluate DeMMO on the recently released, large-scale, multicentre Mobilise-D dataset, which comprises four participant-disjoint cohorts representing distinct mobility-limiting diseases, with each cohort contributing one or more clinical measurement outcomes. Compared with eight strong structural longitudinal and deep-regression baselines, DeMMO achieves the best overall predictive performance and outperforms the baselines for most individual outcomes. Stability selection further identifies reliable longitudinal DMO …

Vollständiger Originalartikel ↗

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