MétaCan
Menu
Back to cohort
Record W4367312597 · doi:10.2196/37330

Features of Cancer mHealth Apps and Evidence for Patient Preferences: Scoping Literature Review

2023· article· en· W4367312597 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJMIR Cancer · 2023
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsmHealthCINAHLPsycINFOMEDLINEApp storeMedicineCitationCochrane LibraryAlternative medicineWorld Wide WebFamily medicineComputer sciencePsychological interventionNursingPathology

Abstract

fetched live from OpenAlex

BACKGROUND: Cancer is increasingly being treated as a chronic disease rather than an acute one-time illness. Additionally, oral anticancer therapies, as opposed to intravenous chemotherapy, are now available for an increasing number of cancer indications. Mobile health (mHealth) apps for use on mobile devices (eg, smartphones or tablets) are designed to help patients with medication adherence, symptom tracking, and disease management. Several previous literature reviews have been conducted regarding mHealth apps for cancer. However, these studies did not address patient preferences for the features of cancer mHealth apps. OBJECTIVE: The primary aim was to review the scientific literature that describes the features and functions of mHealth apps designed for cancer self-management. METHODS: As the purpose of this review was to explore the depth and breadth of research on mHealth app features for cancer self-management, a scoping review methodology was adopted. Four databases were used for this review: PubMed/MEDLINE, Embase, CINAHL, and PsycINFO. Citation and reference searches were conducted for manuscripts meeting the inclusion criteria. A gray literature search was also conducted. Data extracted from manuscripts included author, title, publication date, study type, sampling type, cancer type, treatment, age of participants, features, availability (free or subscription), design input, and patient preferences. Finally, the features listed for each app were compared, highlighting similarities across platforms as well as features unique to each app. RESULTS: After the removal of duplicates, 522 manuscripts remained for the title and abstract review, with 51 undergoing full-text review. A total of 7 manuscripts (referred to as studies hereafter) were included in the final scoping review. App features described in each study varied from 2 to 11, with a median of 4 features per app. The most reported feature was a symptom or side effect tracker, which was reported in 6 studies. Two apps specified the inclusion of patients and health care providers during the design, while 1 app noted that IT and communications experts provided design input. The utility of the apps for end users was measured in several ways, including acceptability (measuring the end users' experience), usability (assessing the functionality and performance by observing real users completing tasks), or qualitative data (reports from end users collected from interviews or focus groups). CONCLUSIONS: This review explored the literature on cancer mHealth apps. Popular features within these mHealth apps include symptom trackers, cancer education, and medication trackers. However, these apps and features are often developed with little input from patients. Additionally, there is little information regarding patient preferences for the features of existing apps. While the number of cancer-related apps available for download continues to increase, further exploration of patient preferences for app features could result in apps that better meet patient disease self-management needs.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.475
Threshold uncertainty score0.552

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.162
GPT teacher head0.553
Teacher spread0.391 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it