| Literature DB >> 35052167 |
Kamaldeep Gupta1, Sharmistha Roy1, Ramesh Chandra Poonia2, Soumya Ranjan Nayak3, Raghvendra Kumar4, Khalid J Alzahrani5, Mrim M Alnfiai6, Fahd N Al-Wesabi7,8.
Abstract
The recent developments in the IT world have brought several changes in the medical industry. This research work focuses on few mHealth applications that work on the management of type 2 diabetes mellitus (T2DM) by the patients on their own. Looking into the present doctor-to-patient ratio in our country (1:1700 as per a Times of India report in 2021), it is very essential to develop self-management mHealth applications. Thus, there is a need to ensure simple and user-friendly mHealth applications to improve customer satisfaction. The goal of this study is to assess and appraise the usability and effectiveness of existing T2DM-focused mHealth applications. TOPSIS, VIKOR, and PROMETHEE II are three multi-criteria decision-making (MCDM) approaches considered in the proposed work for the evaluation of the usability of five existing T2DM mHealth applications, which include Glucose Buddy, mySugr, Diabetes: M, Blood Glucose Tracker, and OneTouch Reveal. The methodology used in the research work is a questionnaire-based evaluation that focuses on certain attributes and sub-attributes, identified based on the features of mHealth applications. CRITIC methodology is used for obtaining the attribute weights, which give the priority of the attributes. The resulting analysis signifies our proposed research by ranking the mHealth applications based on usability and customer satisfaction.Entities:
Keywords: T2DM; critic; mHealth applications; usability score
Year: 2021 PMID: 35052167 PMCID: PMC8775296 DOI: 10.3390/healthcare10010004
Source DB: PubMed Journal: Healthcare (Basel) ISSN: 2227-9032
Figure 1Flowchart model representing the ranking of mHealth application based on usability aspect.
List of attributes (criteria) and sub-attributes (sub-criteria) for identifying the usability score of T2DM mHealth applications.
| Attributes (Criteria) | Definition | Sub-Attributes (Sub-Criteria) |
|---|---|---|
| Learnability (A1) | The user’s ability to perceive and become familiar with the features and functions of T2DM mHealth applications by applying a minimal amount of effort is referred to as learnability. The higher score means that the T2DM mHealth applications are much more self-descriptive, whereas a low score suggests that the T2DM mHealth applications use terminologies that the user may not be familiar with. | Familiarity (A11) |
| Learning time (A21) | ||
| Minimal action (A23) | ||
| Efficiency (A2) | The ease of work is measured by efficiency. It denotes how quickly and cheaply users can finish the task given with limited resources. | Number of taps (A21) |
| Task completion time (A22) | ||
| Response time (A23) | ||
| Ease-of use (A24) | ||
| Connection (A25) | ||
| Memorability (A3) | Memorability refers to how quickly users can re-acquaint themselves with a design after being away from it for a while. | Saving (A31) |
| Retain (A32) | ||
| Reminder (A33) | ||
| Aesthetic (A4) | For evaluating and analyzing the visual effect of T2DM mHealth applications, aesthetic is a key usability attribute. It helps to determine the users’ interest in the corresponding T2DM mHealth applications, both functionally and non-functionally. | Attractive (A41) |
| Appeal (A42) | ||
| Organized (A43) | ||
| Error (A5) | During the evaluation of the T2DM mHealth applications, this relates to the frequency of errors made, the seriousness or severity of the errors, and the measures for recovery. | Presence of Error (A51) |
| Navigation (A6) | Controllability is an important usability attribute that evaluates a T2DM mHealth navigational capability. The score represents how easy it is for the user to navigate through the T2DM mHealth applications and execute the needed task. | Search (A61) |
| Complex (A62) | ||
| Involvement (A63) | ||
| Readability (A7) | The mHealth applications’ content must be readable. Legibility and understandability are two aspects of readability. Color combinations, word style (italic, bold, etc.), font size, and typeface should all be legible in mHealth applications. In terms of word choice and phrase length, mHealth applications should be understandable. | Legible (A71) |
| Understandable (A72) | ||
| Cognitive Load (A8) | Cognitive load refers to the number of working memory resources (such as thinking, reasoning, and remembering) required to operate mHealth applications. The mHealth applications’ cognitive load should be reduced. Removing non-essential content, breaking the content into smaller chunks, displaying the information both visually and verbally, and so on are some techniques to reduce cognitive load. | Essentiality (A81) |
| Presentation (A82) | ||
| Provision for Physically Challenged Users (A9) | A group of users using certain mHealth applications may have physical disabilities such as hearing impairment, movement disabilities, or visual problems, among other things. The application’s user interface should be built or structured in such a way that it can manage various types of user groups as well. | Weak Muscle Control (A91) |
| Low Vision (A92) | ||
| Hearing Impairment (A93) | ||
| Satisfaction (A10) | This attribute measures the amount of satisfaction with mHealth applications. It refers to the user’s comfort, likeability, and pleasure. | Provision (A101) |
| Finding Correct Information (A102) | ||
| Improvement (A103) | ||
| Recommendation (A104) |
Sub-attributes (sub-criteria) identified for evaluating usability of T2DM mHealth applications.
| Sub-Attributes (Sub-Criteria) | Definition |
|---|---|
| Familiarity (A11) | Measures how quickly the user can easily become familiar with the app. |
| Learning time (A21) | Measures the average amount of time users spend in learning various app functions. |
| Minimal action (A23) | It states that minimal action should be required to record/update the blood glucose and other values. |
| Number of taps (A21) | Measures the number of tapping times needed for searching particular information in the app. Less tapping states that the app is efficient. |
| Task completion time (A22) | Measures how long it takes people to accomplish a task and compares it to how long it takes an expert to complete the same task. It also specifies that the tasks such as weight management, measure of step count, and tracking of carb intakes, blood glucose values, and HbA1c are completed at a good pace. |
| Response time (A23) | Measures the response time for recording/charting the glucose values over time. |
| Ease-of use (A24) | Measures how easily the data, such as blood glucose values, HbA1c, and carbs, are entered/recorded and graphically represented. |
| Connection (A25) | Measures the efficiency through which the app can be connected to social media and electronic medical record systems. |
| Saving (A31) | Measures the ease with which the blood sugar values, medication log, and carb intakes are saved for future reference. |
| Retain (A32) | Measures how comfortably the blood glucose values, medication names, carb intakes, and other values are retained for a long time. |
| Reminder (A33) | Measures how efficiently the reminder/alert function is set. |
| Attractive (A41) | Measures the extent at which the layout of the app is found attractive by its users. |
| Appeal (A42) | Measures as to what extent the app’s design visually appeals to the users. |
| Organized (A43) | Measures how meaningfully the app features are organized. |
| Presence of Error (A51) | It states whether the app contains errors and measures the frequency of errors that result from users and compares it with the target value. |
| Search (A61) | Measure the time taken by the app to search for food databases to log in meals. |
| Complex (A62) | Measures the complexity of the navigation of the app features. |
| Involvement (A63) | It measures the user engagement and intervention in the app for finding information. |
| Legible (A71) | It states that the app properties and features should be legible in all aspects. |
| Understandable (A72) | Measures the extent to which the basic characteristics and features of the app are clearly described and can be easily understood by users. |
| Essentiality (A81) | It specifies that only the essential components are present in the app. |
| Presentation (A82) | It states that the information should be presented both visually and verbally. |
| Weak Muscle Control (A91) | Measures the efficiency through which the app can be handled by users with weak muscle control. |
| Low Vision (A92) | This specifies that there should be a provision of increasing the font size for helping users with low vision. |
| Hearing Impairment (A93) | This assures that valuable information such as app education should be available in the text along with the audio to assist the user with hearing impairment. |
| Provision (A101) | Measures as to what extent the app provides resources/tips to the users. |
| Finding Correct Information (A102) | This attribute specifies that the app should be helpful in finding the correct information. |
| Improvement (A103) | Measures the extent to which the app is capable of improving lifestyle. |
| Recommendation (A104) | It measures the action of the users in recommending the app to others. |
Figure 2Identifying attributes and sub-attributes for measuring usability score for T2DM mHealth application.
Figure 3Homepage of Glucose Buddy application.
Figure 4Homepage of mySugr application.
Figure 5Homepage of Diabetes: M application.
Figure 6Homepage of Blood Glucose Tracker application.
Figure 7Homepage of OneTouch Reveal application.
Figure 8Steps involved in CRITIC method.
Figure 9Steps for the technique for order of preference by similarity to ideal solution (TOPSIS) method.
Figure 10Steps involved in VIKOR method.
Figure 11Steps for PROMETHEE II (Preference Ranking Organization Methods for Enrichment Evaluations).
Demographics of the participants (n = 30).
| Variable | n | |
|---|---|---|
| Age | <65 | 20 |
| ≥65 | 10 | |
| Gender | Male | 15 |
| Female | 15 | |
| Use of Smart phone | Frequently (4 to 7 days in a week) | 26 |
| Occasionally (1 to 3 days in a week) | 4 | |
| Rarely (<1 day in a week) | 0 | |
| Education | Elementary School | 1 |
| Middle School | 2 | |
| High School | 7 | |
| Graduate | 14 | |
| Post Graduate | 6 |
Usability score of each attribute.
| Alternatives ID | Alternatives Name | A1 | A2 | A3 | A4 | A5 | A6 | A7 | A8 | A9 | A10 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Alt 1 | Glucose Buddy | 119 | 104 | 98 | 101 | 82 | 70 | 130 | 81 | 117 | 119 |
| Alt 2 | mySugr | 128 | 115 | 113 | 111 | 63 | 72 | 113 | 64 | 111 | 116 |
| Alt 3 | Diabetes: M | 120 | 102 | 98 | 121 | 91 | 74 | 107 | 74 | 111 | 115 |
| Alt 4 | Blood Glucose Tracker | 121 | 101 | 99 | 116 | 94 | 73 | 111 | 75 | 109 | 104 |
| Alt 5 | OneTouch Reveal | 121 | 99 | 92 | 120 | 82 | 69 | 113 | 68 | 111 | 115 |
Weight of each attribute.
| Attributes | Learnability (A1) | Efficiency (A2) | Memorability (A3) | Aesthetic (A4) | Error (A5) | Navigation (A6) | Readability (A7) | Cognitive Load (A8) | Provision for Physically Challenged Users (A9) | Satisfaction (A10) |
|---|---|---|---|---|---|---|---|---|---|---|
| Weights | 0.101316801 | 0.089114537 | 0.084815071 | 0.129194116 | 0.117180195 | 0.104248405 | 0.094418961 | 0.099547741 | 0.089309841 | 0.090854332 |
Figure 12Objective weights of each attribute.
Rank based on .
| Alternatives ID | Item (Alternatives) |
| Rank |
|---|---|---|---|
| Alt 1 | Glucose Buddy | 0.397278402 | 3 |
| Alt 2 | mySugr | 0.748031419 | 1 |
| Alt 3 | Diabetes: M | 0.350935988 | 4 |
| Alt 4 | Blood Glucose Tracker | 0.271650464 | 5 |
| Alt 5 | OneTouch Reveal | 0.47378464 | 2 |
Figure 13Rank obtained by TOPSIS method based on the performance score.
Rank obtained based on the values of (aggregating index).
| Alternatives ID | Item (Alternatives) |
| Rank |
|---|---|---|---|
| Alt 1 | Glucose Buddy | 0.769670172 | 4 |
| Alt 2 | mySugr | 0 | 1 |
| Alt 3 | Diabetes: M | 0.709485465 | 3 |
| Alt 4 | Blood Glucose Tracker | 0.898883249 | 5 |
| Alt 5 | OneTouch Reveal | 0.40239348 | 2 |
Figure 14Rank obtained by VIKOR based on the aggregating index.
Rank obtained based on the values of (net outranking flow).
| Alternatives ID | Item (Alternatives) |
| Rank |
|---|---|---|---|
| Alt 1 | Glucose Buddy | 0.01632707 | 3 |
| Alt 2 | mySugr | 0.344439094 | 1 |
| Alt 3 | Diabetes: M | −0.14960478 | 4 |
| Alt 4 | Blood Glucose Tracker | −0.26391893 | 5 |
| Alt 5 | OneTouch Reveal | 0.052757542 | 2 |
Figure 15Rank obtained by PROMETHEE II based on the net outranking flow.
Comparison of the alternatives based on the usability rank.
| (Alternatives) Item | TOPSIS | VIKOR | PROMETHEE II |
|---|---|---|---|
| Alt 2 (mySugr) | Rank 1 | Rank 1 | Rank 1 |
| Alt 5 (OneTouch Reveal) | Rank 2 | Rank 2 | Rank 2 |
| Alt 1 (Glucose Buddy) | Rank 3 | Rank 4 | Rank 3 |
| Alt 3 (Diabetes: M) | Rank 4 | Rank 3 | Rank 4 |
| Alt 4 (Blood Glucose Tracker) | Rank 5 | Rank 5 | Rank 5 |
Figure 16Comparison of the ranks obtained by TOPSIS, VIKOR, and PROMETHEE II.