| Literature DB >> 29669705 |
Samina Abidi1, Michael Vallis2, Helena Piccinini-Vallis2, Syed Ali Imran3, Syed Sibte Raza Abidi4.
Abstract
BACKGROUND: Behavioral science is now being integrated into diabetes self-management interventions. However, the challenge that presents itself is how to translate these knowledge resources during care so that primary care practitioners can use them to offer evidence-informed behavior change support and diabetes management recommendations to patients with diabetes.Entities:
Keywords: clinical decision support system; health behavior; knowledge management; self-management; type 2 diabetes mellitus
Year: 2018 PMID: 29669705 PMCID: PMC5932333 DOI: 10.2196/medinform.9629
Source DB: PubMed Journal: JMIR Med Inform
Figure 1Diabetes Web-Centric Information and Support Environment (DWISE) framework overview. HbA1c: glycated hemoglobin.
Figure 2High-level PCP and patient behavior change algorithm. CPG: clinical practice guidelines; ; HbA1c: glycated hemoglobin; DWISE: Diabetes Web-Centric Information and Support Environment; PCP: primary care practitioner.
Figure 3Information personalization and domain knowledge elements of Behavior Change Ontology.
Figure 4A subset of readiness assessment module in Behavior Change Ontology, depicting procedural relationships between classes “Readiness Assessment” and “Readiness Assessment Result.”.
Figure 5Diabetes Web-Centric Information and Support Environment (DWISE) technical architecture. BCI: Behavior Change Institute; CDA: Canadian Diabetes Association; CPG: clinical practice guidelines; PCP: primary care practitioner.
Figure 6Tool for primary care practitioners assessing self-efficacy of the family physicians/certified diabetes educators.
Figure 7Screenshots from Diabetes Web-Centric Information and Support Environment (DWISE) mobile apps depicting functionalities such as scheduling, notifications, barrier identification, and feedback.
Figure 8Axial codes in a primary care practitioner;'s Think Aloud Protocol.
Figure 9Axial category “Screen layout and design features” contain 6 open codes.
Axial codes in each category. DWISE: Diabetes Web-Centric Information and Support Environment; PCP: primary care practitioner.
| A priori category | Axial codes (number of open codes contained in each axial category) |
| Facilitators to DWISE usage | Technical support to facilitate DWISE usage (10) |
| Teaching tool for patients (5) | |
| Need for personalized diabetes self-management apps (4) | |
| Need for information about psychological issues (2) | |
| Compliance with DWISE easier for engaged patients (1) | |
| Barriers to DWISE usage | Practicality of DWISE due to PCP time constraints (4) |
| Impact on patients who fail to achieve DWISE set goals (4) | |
| Age-related suitability (4) | |
| Practicality of DWISE because of technically challenged users (3) | |
| Preference for direct patient-PCP contact (3) | |
| Additional work (1) | |
| Liability-related issues (1) | |
| Patient self-management | Potential to improve self-management and monitoring (3) |
| Potential to modify behavior (1) | |
| Patient education | Teaching tool for patients (5) |
| Potential to improve patient awareness of disease (3) | |
| Patient autonomy and preference | Patient autonomy in choosing self-management support delivery method (4) |
| Power dynamic between patient and provider (2) | |
| Potential to improve patient empowerment (3) | |
| Patient-provider communication | Insight into patient’s self-management practices (2) |
| Potential to improve patient-provider communication (3) | |
| Preference for direct patient-provider contact (3) | |
| Encounter-related issues | Impact on patient provider encounter (3) |
| Practicality of DWISE due to PCP time constraints (4) | |
| Professional roles and responsibilities | Professional roles and responsibilities around DWISE usage (2) |
| Additional work (1) | |
| Usability- or acceptability-related issues | Reminders to improve usability (1) |
| System feedback (2) | |
| Information presentation in DWISE (2) | |
| Integration with other devices (2) | |
| Need for personal features in DWISE (3) |