MétaCan
Menu
← Back to cohort
Record W2977370287 · doi:10.2196/16200

Incorporation of Potential User Feedback to Inform the Design of a Prototype Integrated Diabetes Management System

2019· article· en· W2977370287 on OpenAlexvenueno aff
Sunetra Bane

Bibliographic record

VenueIproceedings · 2019
Typearticle
Languageen
FieldMedicine
TopicDiabetes Management and Education
Canadian institutionsnot available
Fundersnot available
KeywordsReferralWorkflowMedicineCoding (social sciences)Diabetes managementDiseaseDiabetes mellitusComputer scienceMedical emergencyType 2 diabetesNursing

Abstract

fetched live from OpenAlex

Background Type 2 diabetes (T2D) is a complex and burdensome chronic disease. Most patients, including uncontrolled (HbA1c >7%) patients, only see their Health Care Provider (HCP) once every three months. Thus, a tremendous amount of patient self-management is required outside the clinic to maintain blood glucose (BG) levels within a healthy range and prevent worsening of the disease. Additionally, HCP’s overseeing diabetes care often rely on patient self-report and lack key data about how well the patient is managing the condition. We hypothesized that the development of an Integrated Diabetes Management (IDM) system which helps patients better track their BG, insulin and diet would support patient self-management. By sharing a data summary with HCPs through an EMR-integrated, web-based portal, the patient’s HCP could would have access to data to help inform treatment decisions and patient education strategies to improve outcomes. Objective The goal of this design research was to better understand how an IDM platform might support patient self-management and care, and, based on this data, create a prioritized list of requirements for a prototype of the system. Methods We used one-hour, semi-structured, in-person interviews and observations with HCPs (n=18) and T2D patients (n=14, recruited via HCP referral). Interview and observation data (via summary notes and transcripts) were analyzed, coding for pain points and workflows. Personas and journey-maps of patients and clinicians were created to inform product design. Pain points and unmet needs were categorized by task and informed the design of features in the IDM system. High fidelity paper prototypes of the solution were tested with HCPs and patients to gather feedback on design options. Results HCPs interviewed ranged from MDs (n=4), NPs (n=7), RNs (n=3), CDEs/RDs (n=2) and health coaches (n=2). For HCPs, tasks along the patient journey consist of diagnosis, training, titration, follow-up, and long-term maintenance. Titration and follow-up are the most resource intensive, with the largest number of tasks falling to RNs and NPs. Key HCPs needs included a way to better track patients’ behaviors and a way to illustrate the relationship between diet, physical activity and BG/insulin readings to educate patients, improving communication between the patient and their HCP. Patient demographics were predominantly male (57%), between 50-59 years old (36%), high-school educated (57%), and split 50/50 between Android and iOS users. Fifty percent of patients had been diagnosed 1-5 years prior to interview, and 58% only used long-acting insulin. Patients had the greatest need for help with self-management of their T2D, including reminders and automatic logging of BG and insulin dose, simplified meal and exercise logging, and the ability to share this information with their HCPs. Conclusions Design research with T2D patients and HCPs was critical to inform the design of a prototype IDM system. User feedback was incorporated to generate an IDM system which included a patient mobile application, BT-connected insulin event capture device, BT-glucose meter, daily meal log, physical activity tracker, and an HCP clinical portal.

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 imitation

Not 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.

metaresearch head score (Codex)0.015
metaresearch head score (Gemma)0.045
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.015
Threshold uncertainty score0.079

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0150.045
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0020.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0050.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.013
GPT teacher head0.231
Teacher spread0.218 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

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".

Quick stats

Citations2
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueIproceedings→Same topicDiabetes Management and Education→French-language works237,207→