Identification of Type 2 Diabetes Management Mobile App Features and Engagement Strategies: Modified Delphi Approach
Bibliographic record
Abstract
BACKGROUND: Diabetes is a significant public health issue. Saudi Arabia has the highest prevalence of type 2 diabetes mellitus (T2DM) in the Arab world. Currently, it affects 31.6% of the general population, and the prevalence of T2DM is predicted to rise to 45.36% by 2030. Mobile health (mHealth) offers improved and cost-effective care to people with T2DM. However, the efficiency of engagement strategies and features of this technology need to be reviewed and standardized according to stakeholder and expert perspectives. OBJECTIVE: The main objective of this study was to identify the most agreed-upon features for T2DM self-management mobile apps; the secondary objective was to identify the most agreed-upon strategies that prompt users to use these apps. METHODS: In this study, a 4-round modified Delphi method was applied by experts in the domain of diabetes care. RESULTS: In total, 11 experts with a mean age of 47.09 years (SD 11.70) consented to participate in the study. Overall, 36 app features were generated. The group of experts displayed weak agreement in their ranking of intervention components (Kendall W=0.275; P<.001). The top 5 features included insulin dose adjustment according to carbohydrate counting and blood glucose readings (5.36), alerting a caregiver of abnormal or critical readings (6.09), nutrition education (12.45), contacts for guidance if required (12.64), and offering patient-specific education tailored to the user's goals, needs, and blood glucose readings (12.90). In total, 21 engagement strategies were generated. Overall, the experts showed a moderate degree of consensus in their strategy rankings (Kendall W=0.454; P<.001). The top 5 engagement strategies included a user-friendly design (educational and age-appropriate design; 2.82), a free app (3.73), allowing the user to communicate or send information/data to a health care provider (HCP; 5.36), HCPs prescribing the mobile app in the clinic and asking about patients' app use compliance during clinical visits (6.91), and flexibility and customization (7.91). CONCLUSIONS: This is the first study in the region consisting of a local panel of experts from the diabetes field gathering together. We used an iterative process to combine the experts' opinions into a group consensus. The results of this study could thus be useful for health app developers and HCPs and inform future decision making on the topic.
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.039 | 0.034 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.005 | 0.003 |
| Science and technology studies | 0.004 | 0.003 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.008 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.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.
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".