MétaCan
Menu
Back to cohort
Record W3127700251 · doi:10.2196/18834

User Engagement With Smartphone Apps and Cardiovascular Disease Risk Factor Outcomes: Systematic Review

2021· review· en· W3127700251 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 Cardio · 2021
Typereview
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersNational Institute of Nursing ResearchNational Heart, Lung, and Blood InstituteNational Institutes of Health
KeywordsmHealthCINAHLMedicinePsychological interventionOperationalizationeHealthDiseaseGerontologyHealth careNursingInternal medicine

Abstract

fetched live from OpenAlex

Background The use of mobile health (mHealth) interventions, including smartphone apps, for the prevention of cardiovascular disease (CVD) has demonstrated mixed results for obesity, hypercholesterolemia, diabetes, and hypertension management. A major factor attributing to the variation in mHealth study results may be mHealth user engagement. Objective This systematic review aims to determine if user engagement with smartphone apps for the prevention and management of CVD is associated with improved CVD health behavior change and risk factor outcomes. Methods We conducted a comprehensive search of PubMed, CINAHL, and Embase databases from 2007 to 2020. Studies were eligible if they assessed whether user engagement with a smartphone app used by an individual to manage his or her CVD risk factors was associated with the CVD health behavior change or risk factor outcomes. For eligible studies, data were extracted on study and sample characteristics, intervention description, app user engagement measures, and the relationship between app user engagement and the CVD risk factor outcomes. App user engagement was operationalized as general usage (eg, number of log-ins or usage days per week) or self-monitoring within the app (eg, total number of entries made in the app). The quality of the studies was assessed. Results Of the 24 included studies, 17 used a randomized controlled trial design, 4 used a retrospective analysis, and 3 used a single-arm pre- and posttest design. Sample sizes ranged from 55 to 324,649 adults, with 19 studies recruiting participants from a community setting. Most of the studies assessed weight loss interventions, with 6 addressing additional CVD risk factors, including diabetes, sleep, stress, and alcohol consumption. Most of the studies that assessed the relationship between user engagement and reduction in weight (9/13, 69%), BMI (3/4, 75%), body fat percentage (1/2, 50%), waist circumference (2/3, 67%), and hemoglobin A1c (3/5, 60%) found statistically significant results, indicating that greater app user engagement was associated with better outcomes. Of 5 studies, 3 (60%) found a statistically significant relationship between higher user engagement and an increase in objectively measured physical activity. The studies assessing the relationship between user engagement and dietary and diabetes self-care behaviors, blood pressure, and lipid panel components did not find statistically significant results. Conclusions Increased app user engagement for prevention and management of CVD may be associated with improved weight and BMI; however, only a few studies assessed other outcomes, limiting the evidence beyond this. Additional studies are needed to assess user engagement with smartphone apps targeting other important CVD risk factors, including dietary behaviors, hypercholesterolemia, diabetes, and hypertension. Further research is needed to assess mHealth user engagement in both inpatient and outpatient settings to determine the effect of integrating mHealth interventions into the existing clinical workflow and on CVD outcomes.

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.003
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Research integrity
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.583
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

Opus teacher head0.086
GPT teacher head0.437
Teacher spread0.351 · 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