MétaCan
Menu
Back to cohort
Record W4322392188 · doi:10.2196/42092

Evaluating Barriers and Facilitators to the Uptake of mHealth Apps in Cancer Care Using the Consolidated Framework for Implementation Research: Scoping Literature Review

2023· article· en· W4322392188 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
FundersRoche Italia
KeywordsmHealthImplementation researchObservational studyRandomized controlled trialMedicineMEDLINEResearch designHealth carePsychological interventionMedical physicsNursingSurgery

Abstract

fetched live from OpenAlex

BACKGROUND: Mobile health (mHealth) solutions have proven to be effective in a wide range of patient outcomes and have proliferated over time. However, a persistent challenge of digital health technologies, including mHealth, is that they are characterized by early dropouts in clinical practice and struggle to be used outside experimental settings or on larger scales. OBJECTIVE: This study aimed to explore barriers and enablers to the uptake of mHealth solutions used by patients with cancer undergoing treatment, using a theory-guided implementation science model, that is, the Consolidated Framework for Implementation Research (CFIR). METHODS: A scoping literature review was conducted using PubMed (MEDLINE), Web of Science, and ScienceDirect databases in March 2022. We selected studies that analyzed the development, evaluation, and implementation of mHealth solutions for patients with cancer that were used in addition to the standard of care. Only empirical designs (eg, randomized controlled trials, observational studies, and qualitative studies) were considered. First, information on the study characteristics, patient population, app functionalities, and study outcomes was extracted. Then, the CFIR model was used as a practical tool to guide data collection and interpretation of evidence on mHealth uptake. RESULTS: Overall, 91 papers were included in the data synthesis. The selected records were mostly randomized controlled trials (26/91, 29%) and single-arm, noncomparative studies (52/91, 57%). Most of the apps (42/73, 58%) were designed for both patients and clinicians and could be used to support any type of cancer (29/73, 40%) and a range of oncological treatments. Following the CFIR scheme (intervention, outer setting, inner setting, individuals, process), multistakeholder co-design, codevelopment, and testing of mHealth interventions were identified as key enablers for later uptake. A variety of external drivers emerged, although the most relevant outer incentive fostering mHealth use was addressing patient needs. Among organizational factors likely to influence technology uptake, interoperability was the most prominent, whereas other providers' dimensions such as managerial attitudes or organizational culture were not systematically discussed. Technology-related impediments that could hamper the use of mHealth at the individual level were considered least often. CONCLUSIONS: The hype surrounding mHealth in cancer care is hindered by several factors that can affect its use in real world and nonexperimental settings. Compared with the growing evidence on mHealth efficacy, knowledge to inform the uptake of mHealth solutions in clinical cancer care is still scarce. Although some of our findings are supported by previous implementation research, our analysis elaborates on the distinguishing features of mHealth apps and provides an integrated perspective on the factors that should be accounted for implementation efforts. Future syntheses should liaise these dimensions with strategies observed in successful implementation initiatives.

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.004
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.562
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.411
GPT teacher head0.687
Teacher spread0.276 · 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