Utilization of Patient-Generated Data Collected Through Mobile Devices: Insights From a Survey on Attitudes Toward Mobile Self-Monitoring and Self-Management Apps for Depression
Bibliographic record
Abstract
BACKGROUND: Depression is a severe psychiatric disease with high prevalence and an elevated risk for recurrence and chronicity. A substantial proportion of individuals with a diagnosis of unipolar depressive disorder do not receive treatment as advised by national guidelines. Consequently, self-monitoring and self-management become increasingly important. New mobile technologies create unique opportunities to obtain and utilize patient-generated data. As common adherence rates to mobile technologies are scarce, a profound knowledge of user behavior and attitudes and preferences is important throughout any developmental process of mobile technologies and apps. OBJECTIVE: The aim of this survey was to provide descriptive data upon usage and anticipated usage of self-monitoring and self-management of depression and preferences of potential users in terms of documented parameters and data-sharing options. METHODS: A Web-based survey comprising 55 questions was conducted to obtain data on the usage of mobile devices, app usage, and participant's attitudes and preferences toward mobile health apps for the self-monitoring and self-management of depression. RESULTS: A total of 825 participants provided information. Moreover, two-thirds of the sample self-reported to be affected by depressive symptoms, but only 12.1% (81/668) of those affected by depression have ever used any mobile self-monitoring or self-management app. Analysis showed that people want personally relevant information and feedback but also focus on handling sensitive data. CONCLUSIONS: New mobile technologies and smartphone apps, especially in combination with mobile sensor systems, offer unique opportunities to overcome challenges in the treatment of depression by utilizing the potential of patient-generated data. Focus on patient-relevant information, security and safe handling of sensitive personal data, as well as options to share data with self-selected third parties should be considered mandatory throughout any development process.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.014 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".