MétaCan
Menu
Back to cohort
Record W2510814766 · doi:10.2196/mhealth.5720

Beyond the Randomized Controlled Trial: A Review of Alternatives in mHealth Clinical Trial Methods

2016· review· en· W2510814766 on OpenAlex
Quỳnh Phạm, David Wiljer, Joseph A Cafazzo

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueJMIR mhealth and uhealth · 2016
Typereview
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsCentre for Addiction and Mental HealthPublic Health OntarioUniversity of TorontoUniversity Health Network
Fundersnot available
KeywordsmHealthRandomized controlled trialClinical trialMedicineResearch designPsychological interventionN of 1 trialProtocol (science)Physical therapyAlternative medicineNursingSurgeryStatisticsInternal medicine

Abstract

fetched live from OpenAlex

BACKGROUND: Randomized controlled trials (RCTs) have long been considered the primary research study design capable of eliciting causal relationships between health interventions and consequent outcomes. However, with a prolonged duration from recruitment to publication, high-cost trial implementation, and a rigid trial protocol, RCTs are perceived as an impractical evaluation methodology for most mHealth apps. OBJECTIVE: Given the recent development of alternative evaluation methodologies and tools to automate mHealth research, we sought to determine the breadth of these methods and the extent that they were being used in clinical trials. METHODS: We conducted a review of the ClinicalTrials.gov registry to identify and examine current clinical trials involving mHealth apps and retrieved relevant trials registered between November 2014 and November 2015. RESULTS: Of the 137 trials identified, 71 were found to meet inclusion criteria. The majority used a randomized controlled trial design (80%, 57/71). Study designs included 36 two-group pretest-posttest control group comparisons (51%, 36/71), 16 posttest-only control group comparisons (23%, 16/71), 7 one-group pretest-posttest designs (10%, 7/71), 2 one-shot case study designs (3%, 2/71), and 2 static-group comparisons (3%, 2/71). A total of 17 trials included a qualitative component to their methodology (24%, 17/71). Complete trial data collection required 20 months on average to complete (mean 21, SD 12). For trials with a total duration of 2 years or more (31%, 22/71), the average time from recruitment to complete data collection (mean 35 months, SD 10) was 2 years longer than the average time required to collect primary data (mean 11, SD 8). Trials had a moderate sample size of 112 participants. Two trials were conducted online (3%, 2/71) and 7 trials collected data continuously (10%, 7/68). Onsite study implementation was heavily favored (97%, 69/71). Trials with four data collection points had a longer study duration than trials with two data collection points: F4,56=3.2, P=.021, η(2)=0.18. Single-blinded trials had a longer data collection period compared to open trials: F2,58=3.8, P=.028, η(2)=0.12. Academic sponsorship was the most common form of trial funding (73%, 52/71). Trials with academic sponsorship had a longer study duration compared to industry sponsorship: F2,61=3.7, P=.030, η(2)=0.11. Combined, data collection frequency, study masking, sample size, and study sponsorship accounted for 32.6% of the variance in study duration: F4,55=6.6, P<.01, adjusted r(2)=.33. Only 7 trials had been completed at the time this retrospective review was conducted (10%, 7/71). CONCLUSIONS: mHealth evaluation methodology has not deviated from common methods, despite the need for more relevant and timely evaluations. There is a need for clinical evaluation to keep pace with the level of innovation of mHealth if it is to have meaningful impact in informing payers, providers, policy makers, and patients.

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.113
metaresearch head score (Gemma)0.013
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Meta-epidemiology (broad), Science and technology studies, Research integrity
Consensus categoriesMetaresearch, Meta-epidemiology (narrow), Research integrity
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Randomized trial · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.462
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.1130.013
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0270.003
Bibliometrics0.0010.002
Science and technology studies0.0010.001
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0020.006
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.292
GPT teacher head0.652
Teacher spread0.360 · 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