One Drop | Mobile: An Evaluation of Hemoglobin A1c Improvement Linked to App Engagement
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.
Bibliographic record
Abstract
BACKGROUND: Three recent reviews evaluated 19 studies testing the hemoglobin A1c (HbA1c) benefit of 16 diabetes apps, including 5 publicly available apps. Most studies relied on small samples and did not link app engagement with outcomes. OBJECTIVE: This study assessed both HbA1c change in a large sample of people using the One Drop | Mobile app and associations between app engagement and changes in HbA1c. METHODS: The One Drop | Mobile app for iOS and Android is designed to manually and passively (via Apple HealthKit, Google Fit, and the One Drop | Chrome blood glucose meter) store, track, and share data. Users can schedule medication reminders, view statistics, set goals, track health outcomes, and get data-driven insights. In June 2017, we queried data on people with diabetes using the app who had entered at least 2 HbA1c values in the app >60 and ≤365 days apart. Multiple imputation corrected for missing data. Unadjusted and adjusted mixed effects repeated measures models tested mean HbA1c change by time, diabetes type, and their interaction. Multiple regression models assessed relationships between using the app to track food, activity, blood glucose, and medications and HbA1c change. RESULTS: The sample (N=1288) included people with type 1 diabetes (T1D) (n=367) or type 2 diabetes (T2D) (n=921) who were 35% female, diagnosed with diabetes for a mean 9.4 (SD 9.9) years, and tracked an average 1646.1 (SD 3621.9) self-care activities in One Drop | Mobile between their first (mean 8.14% [SD 2.06%]) and second HbA1c entry (mean 6.98% [SD 1.1%]). HbA1c values were significantly associated with user-entered average blood glucose 90 days before the second HbA1c entry (rho=.73 to .75, P<.001). HbA1c decreased by an absolute 1.07% (unadjusted and adjusted F=292.03, P<.001) from first to second HbA1c entry. There was a significant interaction between diabetes type and HbA1c. Both groups significantly improved, but users with T2D had a greater HbA1c decrease over time than users with T1D (F=10.54, P<.001). For users with T2D (n=921), HbA1c decreased by an absolute 1.27% (F=364.50, P<.001) from first to second HbA1c entry. Finally, using One Drop | Mobile to record food was associated with greater HbA1c reductions even after adjusting for covariates and after also adjusting for insulin use for users with T2D (all P<.05). CONCLUSIONS: People with T1D and T2D reported a 1.07% to 1.27% absolute reduction in HbA1c during a median 4 months of using the One Drop | Mobile app. Using the app to track self-care was associated with improved HbA1c. More research is needed on the health benefits of publicly available diabetes apps, particularly studies associating app engagement with short- and long-term effects.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.002 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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 it