Effectiveness of Disease-Specific mHealth Apps in Patients With Diabetes Mellitus: Scoping Review
Bibliographic record
Abstract
Background According to the World Health Organization, the worldwide prevalence of diabetes mellitus (DM) is increasing dramatically and DM comprises a large part of the global burden of disease. At the same time, the ongoing digitalization that is occurring in society today offers novel possibilities to deal with this challenge, such as the creation of mobile health (mHealth) apps. However, while a great variety of DM-specific mHealth apps exist, the evidence in terms of their clinical effectiveness is still limited. Objective The objective of this review was to evaluate the clinical effectiveness of mHealth apps in DM management by analyzing health-related outcomes in patients diagnosed with type 1 DM (T1DM), type 2 DM (T2DM), and gestational DM. Methods A scoping review was performed. A systematic literature search was conducted in MEDLINE (PubMed), Cochrane Library, EMBASE, CINAHL, and Web of Science Core Collection databases for studies published between January 2008 and October 2020. The studies were categorized by outcomes and type of DM. In addition, we carried out a meta-analysis to determine the impact of DM-specific mHealth apps on the management of glycated hemoglobin (HbA1c). Results In total, 27 studies comprising 2887 patients were included. We analyzed 19 randomized controlled trials, 1 randomized crossover trial, 1 exploratory study, 1 observational study, and 5 pre-post design studies. Overall, there was a clear improvement in HbA1c values in patients diagnosed with T1DM and T2DM. In addition, positive tendencies toward improved self-care and self-efficacy as a result of mHealth app use were found. The meta-analysis revealed an effect size, compared with usual care, of a mean difference of –0.54% (95% CI –0.8 to –0.28) for T2DM and –0.63% (95% CI –0.93 to –0.32) for T1DM. Conclusions DM-specific mHealth apps improved the glycemic control by significantly reducing HbA1c values in patients with T1DM and T2DM patients. In general, mHealth apps effectively enhanced DM management. However, further research in terms of clinical effectiveness needs to be done in greater detail.
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.014 | 0.060 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.009 | 0.010 |
| Bibliometrics | 0.011 | 0.010 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.004 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.003 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.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.
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".