Identification of the Needs and Preferences of Patients With Cancer for the Development of a Clinic App: Qualitative Study
Bibliographic record
Abstract
BACKGROUND: Mobile health (mHealth) tools were developed during the past decades and are increasingly used by patients in cancer care too. Scientific research in the development of mHealth services is required in order to meet the various needs of patients and test usability. OBJECTIVE: The aim of this study is to assess patients' needs, preferences, and usability of an app (My University Clinic [MUC] app) developed by the Comprehensive Cancer Center Freiburg (CCCF) Germany. METHODS: Based on a qualitative cross-sectional approach, we conducted semistructured interviews with patients with cancer, addressing their needs, preferences, and usability of the designed MUC app. Patients treated by the CCCF were recruited based on a purposive sampling technique focusing on age, sex, cancer diagnoses, and treatment setting (inpatient, outpatient). Data analysis followed the qualitative content analysis according to Kuckartz and was performed using computer-assisted software (MAXQDA). RESULTS: For the interviews, 17 patients with cancer were selected, covering a broad range of sampling parameters. The results showed that patients expect benefits in terms of improved information about the disease and communication with the clinic staff. Demands for additional features were identified (eg, a list of contact persons and medication management). The most important concerns referred to data security and the potential restriction of personal contacts with health care professionals of the clinical departments of the CCCF. In addition, some features for improving the design of the MUC app with respect to usability or for inclusion of interacting tools were suggested by the patients. CONCLUSIONS: The results of this qualitative study were discussed within the multidisciplinary team and the MUC app providers. Patients' perspectives and needs will be included in further development of the MUC app. There will be a second study phase in which patients will receive a test version of the MUC app and will be asked about their experiences with it. TRIAL REGISTRATION: Deutsches Register Klinischer Studien DRKS00022162; https://drks.de/search/de/trial/DRKS00022162.
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.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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".