| Literature DB >> 25100649 |
Naoe Tatara1, Eirik Arsand, Stein Olav Skrøvseth, Gunnar Hartvigsen.
Abstract
BACKGROUND: In a growing number of intervention studies, mobile phones are used to support self-management of people with Type 2 diabetes mellitus (T2DM). However, it is difficult to establish knowledge about factors associated with intervention effects, due to considerable differences in research designs and outcome measures as well as a lack of detailed information about participants' engagement with the intervention tool.Entities:
Keywords: Type 2 diabetes; mHealth; mobile phone; self-management; usability; usage; user-involved design process
Year: 2013 PMID: 25100649 PMCID: PMC4114413 DOI: 10.2196/mhealth.2432
Source DB: PubMed Journal: JMIR Mhealth Uhealth ISSN: 2291-5222 Impact factor: 4.773
Figure 1Screen design and structure of Diabetes Diary (“Diabetesdagbok”).
Schedule for the long-term trial and the timing of data collection.
| Meetings | Time (month, year) | Events |
| 1 | September 2008 a | Introduction of the Few Touch application (except physical activity sensor system and tips function) |
|
|
| Questionnaire 5 |
| 2 | October 2008 (7 weeks after Meeting 1) | Introduction of tips function |
|
|
| Focus group sessions (the participants were divided into two groups) |
| 3 | December 2008b, January 2009c | Introduction of physical activity sensor system |
|
|
| Individual semistructured interview |
|
|
| Questionnaires 4 and 7 |
| 4 | March 2009 | Focus group sessions (the participants were divided into two groups) |
|
|
| Questionnaires 1, 2, 4-8 |
|
|
| System Usability Scale (SUS) [ |
| 5 | June 2009 | Focus group sessiond |
| 6 | October 2009 | Focus group sessions (the participants were divided into two groups) |
|
|
| Questionnaires 3-7, 9 |
aFor P07 and P11, the application was introduced on October 1 and 7, 2008, respectively
bTwo participants attended an individual meeting.
cTen participants attended an individual meeting.
dTen participants attended the focus group session.
Results from Mann-Kendall trend test on usage rate.
|
| Blood glucose sensor system | Nutrition habit recording system | Physical activity sensor system | |||
| Participant | Tau-value |
| Tau-value |
| Tau-value |
|
| P01 | -0.19 | .06 | -0.58 | <.001 | -0.57 | <.001 |
| P02 | 0.22 | .03 | -0.01 | 0.91 | -0.10 | 0.46 |
| P03 | -0.01 | .96 | 0.16 | 0.14 | 0.21 | 0.16 |
| P04 | -0.35 | .002 | -0.37 | <.001 | -0.62 | <.001 |
| P05 | -0.41 | <.001 | -0.18 | 0.07 | -0.16 | 0.18 |
| P06 | -0.31 | .003 | -0.39 | <.001 | -0.43 | 0.001 |
| P07 | -0.11 | .33 | -0.58 | <.001 | -0.58 | <.001 |
| P08 | -0.06 | .56 | -0.34 | .002 | 0.12 | 0.47 |
| P09a | -0.05 | .70 | -0.37 | .002 | -0.35 | 0.08 |
| P10 | -0.54 | <.001 | -0.42 | <.001 | -0.35 | 0.01 |
| P11 | -0.45 | <.001 | -0.71 | <.001 | -0.27 | 0.05 |
| P12 | -0.63 | <.001 | -0.61 | <.001 | -0.07 | 0.69 |
aAll the recorded data on P09’s smartphone were accidentally deleted at Meeting 2, and only data recorded after Meeting 2 were used for analyses.
The numbers of days on which each function was used against a period in which each function was available.
|
| Blood glucose sensor system | Nutrition habit recording system | Physical activity sensor system | ||||||
| Participant | Dra | Dab |
| Dr | Da |
| Dr | Da |
|
| P01d | 102 | 395 | (26%) | 101 | 395 | (26%) | 71 | 152 | (47%) |
| P02d | 158 | 393 | (40%) | 51 | 393 | (13%) | 56 | 239 | (23%) |
| P03d | 390 | 395 | (99%) | 365 | 395 | (92%) | 210 | 219 | (96%) |
| P04 | 16 | 393 | (4%) | 11 | 393 | (3%) | 33 | 138 | (24%) |
| P05d | 294 | 393 | (75%) | 277 | 393 | (70%) | 143 | 265 | (54%) |
| P06 | 334 | 393 | (85%) | 323 | 393 | (82%) | 159 | 244 | (65%) |
| P07d | 327 | 374 | (87%) | 98 | 374 | (26%) | 61 | 202 | (30%) |
| P08d | 58 | 395 | (15%) | 357 | 395 | (90%) | 161 | 197 | (82%) |
| P09c, d | 348 | 352 | (99%) | 8 | 352 | (2%) | 129 | 132 | (98%) |
| P10d, e | 278 | 389 | (71%) | 88 | 393 | (22%) | 116 | 191 | (61%) |
| P11d | 60 | 380 | (16%) | 152 | 380 | (40%) | 86 | 210 | (41%) |
| P12 | 209 | 393 | (53%) | 240 | 393 | (61%) | 86 | 147 | (59%) |
aDr is the number of days on which records were made.
bDa is the number of days when a function was available.
cAll the recorded data on P09’s smartphone were accidentally deleted at Meeting 2, and only data recorded after Meeting 2 were used for analyses.
dThe step counters had problems, so that there were periods when participants could not use their step counter.
eP10’s blood glucose sensor system did not function for 4 days.
Figure 2Distribution of blood glucose measurement frequency among days on which any blood glucose measurement was performed.
Questionnaire 4—Distribution of the answers to questionnaire about perceived usefulness of the Few Touch application (1: Not useful at all, 7: Very useful).
| Elapsed time / Usefulness of the application | 1-3 | 4 | 5 | 6 | 7 | Mean |
| 3-4 months (Meeting 3) | 0 | 1 | 0 | 6 | 5 | 6.3 |
| 6 months (Meeting 4) | 0 | 1 | 1 | 2 | 8 | 6.4 |
| 1 year (Meeting 6) | 0 | 0 | 1 | 4 | 7 | 6.5 |
Figure 3Mechanism of participants’ long-term engagement with the Few Touch application.
Functions and features that caused deteriorated usability of the Few Touch application.
| Function and feature | Design concept | Reality | Affected components in usability |
| User interaction design enabling nutrition habit recording completed by just one press on the appropriate category. | Users would record each meal, snack and drink immediately. | Participants made several records at a time or recorded nutrition habits at the end of the day to summarize their food intake so that they needed more operations at a time. (P01, P03, P05, P06, P08, P10 and P12, Meeting 2) | Efficiency, flexibility |
| Categorization of nutrition habit recording | Categories would correspond to types of eating habits that should be improved in context of T2DM, so that it encourages users to have a healthier diet. | The categorization was not precise enough for their reflective thinking, or it did not match the participants’ individual preferences based on their accumulated personal experiences. (P01, P02, P08, P11 and P012, Meeting 4) | Effectiveness, flexibility |
| Step counter attached on belt | A physical activity sensor should be integrated with their daily tools and outfits. | One participant (P06) did not use a belt normally. P06 had used it in a bag, but it was easy for P06 to forget about using the step counter on the next day. (Meeting 6) | Satisfaction |
| Step counter as a physical activity sensor | Physical activity sensor system should provide easily interpretable values to motivate a user to monitor. | The fact that other types of sports (skiing) or physical activities were not measured was disappointing. (P11, Meeting 4; [ | Effectiveness, satisfaction |
| User interface of tips function and its contents | Tips function would provide a user with concise information that can be shown on a screen without necessity of scrolling or more manual operation than one button press to access to a “tip of the day”. | Participants wanted better access to information that they want to read (P05, P08, and P09, Meeting 5) | Efficiency, satisfaction |
|
|
| Participants wanted more and richer information (P01, P03, P09, and P12, Meeting 4), preferably delivered by SMS with tailored contents based on user’s profile (P12 [ | Satisfaction |
| Diabetes Diary as a software on a smartphone | Users would easily access to their records and information relevant to self-management of diabetes by integrating necessary functionalities into a software application running on their personal mobile phone. | A participant (P04) stopped using the smartphone as his/her personal mobile phone, because it had problems as a mobile phone (Meeting 6) | Effectiveness, efficiency, satisfaction |
Figure 4Modified user interface for nutrition habit recording (left), and the tips function (right).