Development of a Mobile Health App (TOGETHERCare) to Reduce Cancer Care Partner Burden: Product Design Study
Bibliographic record
Abstract
BACKGROUND: Approximately 6.1 million adults in the United States serve as care partners for cancer survivors. Studies have demonstrated that engaging cancer survivors and their care partners through technology-enabled structured symptom collection has several benefits. Given the high utilization of mobile technologies, even among underserved populations and in low resource areas, mobile apps may provide a meaningful access point for all stakeholders for symptom management. OBJECTIVE: We aimed to develop a mobile app incorporating user preferences to enable cancer survivors' care partners to monitor the survivors' health and to provide care partner resources. METHODS: An iterative information gathering process was conducted that included (1) discussions with 138 stakeholders to identify challenges and gaps in survivor home care; (2) semistructured interviews with clinicians (n=3), cancer survivors (n=3), and care partners (n=3) to identify specific needs; and (3) a 28-day feasibility field test with seven care partners. RESULTS: Health professionals noted the importance of identifying early symptoms of adverse events. Survivors requested modules on medication, diet, self-care, reminders, and a version in Spanish. Care partners preferred to focus primarily on the patient's health and not their own. The app was developed incorporating quality-of-life surveys and symptom reporting, as well as resources on home survivor care. Early user testing demonstrated ease of use and app feasibility. CONCLUSIONS: TOGETHERCare, a novel mobile app, was developed with user input to track the care partner's health and report on survivor symptoms during home care. The following two clinical benefits emerged: (1) reduced anxiety among care partners who use the app and (2) the potential for identifying survivor symptoms noted by the care partner, which might prevent adverse events. TRIAL REGISTRATION: ClinicalTrials.gov NCT04018677; https://clinicaltrials.gov/ct2/show/NCT04018677.
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.009 | 0.012 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".