Mobile-Based Self-management Application Requirements for Patients With Gastric Cancer: Quantitative Descriptive Study of Specialist and Patient Perspectives
Bibliographic record
Abstract
BACKGROUND: Gastric cancer is one of the most common gastrointestinal cancers. Patients with gastric cancer experience disabilities and complications that lead to reduced quality of life. Empowering these patients by providing them with information and self-management skills can help reduce side effects and improve their quality of life. OBJECTIVE: The aim of this study was to identify the user requirements for developing a mobile-based self-management app to support patients with gastric cancer. METHODS: Data were analyzed using descriptive statistics and frequency distribution reports using IBM SPSS Statistics software. RESULTS: All of the data elements and functional requirements except "data recording times" and "weight changes in graphs" were identified as essential by clinical experts and patients. Among the functional requirements required in a gastric cancer self-management app, the capabilities related to informing, announcing warnings, and reminders are included. In the demographic data section, most patients (14/26, 53%) did not comment on the importance of recording data such as name, surname, and place of residence, and the demographic data section was met with less agreement from patients than clinicians. CONCLUSIONS: Applying the requirements mentioned in this study can improve the self-management of patients with gastric cancer. Such apps can play an important role in empowering patients and improving their quality of life. However, the apps need to be designed and implemented to see how they can meet users' requirements.
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.004 | 0.018 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| 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 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".