Use of and Beliefs About Mobile Phone Apps for Diabetes Self-Management: Surveys of People in a Hospital Diabetes Clinic and Diabetes Health Professionals in New Zealand
Bibliographic record
Abstract
BACKGROUND: People with diabetes mellitus (DM) are using mobile phone apps to support self-management. The numerous apps available to assist with diabetes management have a variety of functions. Some functions, like insulin dose calculators, have significant potential for harm. OBJECTIVES: The study aimed to establish (1) whether people with DM in Wellington, New Zealand, use apps for DM self-management and evaluate desirable features of apps and (2) whether health professionals (HPs) in New Zealand treating people with DM recommend apps to patients, the features HPs regard as important, and their confidence with recommending apps. METHODS: A survey of patients seen at a hospital diabetes clinic over 12 months (N=539) assessed current app use and desirable features. A second survey of HPs attending a diabetes conference (n=286) assessed their confidence with app recommendations and perceived usefulness. RESULTS: Of the 189 responders (35.0% response rate) to the patient survey, 19.6% (37/189) had used a diabetes app. App users were younger and in comparison to other forms of diabetes mellitus, users prominently had type 1 DM. The most favored feature of the app users was a glucose diary (87%, 32/37), and an insulin calculator was the most desirable function for a future app (46%, 17/37). In non-app users, the most desirable feature for a future app was a glucose diary (64.4%, 98/152). Of the 115 responders (40.2% response rate) to the HPs survey, 60.1% (68/113) had recommended a diabetes app. Diaries for blood glucose levels and carbohydrate counting were considered the most useful app features and the features HPs felt most confident to recommend. HPs were least confident in recommending insulin calculation apps. CONCLUSIONS: The use of apps to record blood glucose was the most favored function in apps used by people with diabetes, with interest in insulin dose calculating function. HPs do not feel confident in recommending insulin dose calculators. There is an urgent need for an app assessment process to give confidence in the quality and safety of diabetes management apps to people with diabetes (potential app users) and HPs (potential app prescribers).
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 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.006 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".