A Clinical Journey Mobile Health App for Perioperative Patients: Cross-sectional Study
Bibliographic record
Abstract
BACKGROUND: Mobile eHealth apps are important tools in personal health care management. The Patient Journey app was developed to inform patients with musculoskeletal disorders during their perioperative period. The app contains timely information, video exercises, and functional tasks. Although the Patient Journey app and other health apps are widely used, little research is available on how patients appreciate these apps. OBJECTIVE: The primary aim of this study was to evaluate the user-friendliness of the Patient Journey app in terms of its usability and the attitudes of users toward the app. The secondary aim was to evaluate positive and negative user experiences. METHODS: A web-based questionnaire was sent to 2114 patients scheduled for surgery for a musculoskeletal disorder. Primary outcomes were usability (measured with the System Usability Scale) and user attitudes regarding the Patient Journey app (assessed with the second part of the eHealth Impact Questionnaire). The secondary outcomes were evaluated with multiple choice questions and open-ended questions, which were analyzed via inductive thematic content analyses. RESULTS: Of the 940 patients who responded, 526 used the Patient Journey app. The usability of the app was high (System Usability Scale: median 85.0, IQR 72.5-92.5), and users had a positive attitude toward the Information and Presentation provided via the app (eHealth Impact Questionnaire: median 78.0, IQR 68.8-84.4). The app did not adequately improve the users' confidence in discussing health with others (eHealth Impact Questionnaire: median 63.9, IQR 50.0-75.0) or motivation to manage health (eHealth Impact Questionnaire: median 61.1, IQR 55.6-72.2). Three core themes emerged regarding positive and negative user experiences: (1) content and information, (2) expectations and experiences, and (3) technical performance. Users experienced timely information and instructions positively and found that the app prepared and guided them optimally through the perioperative period. Negative user experiences were overly optimistic information, scarcely presented information about pain (medication), lack of reference data, insufficient information regarding clinical course deviations and complications, and lack of interaction with clinicians. CONCLUSIONS: The Patient Journey app is a usable, informative, and presentable tool to inform patients with musculoskeletal disorders during their perioperative period. The qualitative analyses identified aspects that can further improve the user experiences of the app.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.005 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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 teacher head, 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".