| Literature DB >> 28438724 |
Sruthy Agnisarman1, Shraddhaa Narasimha2, Kapil Chalil Madathil1,2, Brandon Welch3, Fnu Brinda2, Aparna Ashok4, James McElligott3.
Abstract
BACKGROUND: Telemedicine is the use of technology to provide and support health care when distance separates the clinical service and the patient. Home-based telemedicine systems involve the use of such technology for medical support and care connecting the patient from the comfort of their homes with the clinician. In order for such a system to be used extensively, it is necessary to understand not only the issues faced by the patients in using them but also the clinician.Entities:
Keywords: heuristics, Internet, user-computer interface, cognition; telemedicine
Year: 2017 PMID: 28438724 PMCID: PMC5422657 DOI: 10.2196/humanfactors.7293
Source DB: PubMed Journal: JMIR Hum Factors ISSN: 2292-9495
Figure 1Doxy.me log-in screen, waiting room, and clinician’s view.
Figure 2Vidyo log-in screen, contact list, and clinician’s view.
Figure 3VSee log-in screen, application screen, and clinician’s view.
Figure 4Polycom log-in screen, welcome screen, and clinician’s view.
Usability heuristics used for evaluating the telemedicine interfaces (adapted from Nielsen’s heuristics [27,28]).
| Heuristic | Description |
| Visibility of system status | The system should always keep users informed about what is going on, through appropriate feedback within a reasonable amount of time. |
| Match between system and the real world | The system should speak the users’ language, using familiar words, phrases, and concepts rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. |
| User control and freedom | Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialog. Support undo and redo. |
| Consistency and standards | Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. |
| Error prevention | Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action. |
| Recognition rather than recall | Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialog to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. |
| Flexibility and efficiency of use | Accelerators—unseen by the novice user—may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. |
| Esthetic and minimalist design | Dialogs should not contain information that is irrelevant or rarely needed. Every extra unit of information in a dialog competes with the relevant units of information and diminishes their relative visibility. |
| Help users recognize, diagnose, and recover from errors | Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. |
| Help and documentation | Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. |
Figure 5Experimental procedure followed.
Heuristic violations identified in the telemedicine initiation session.
| Task | Problem description | Solution recommendation | Heuristic violated | Severity rating |
| Entering room name (Doxy.me) | User may not comprehend the meaning of “room name” in a Web-based system setting | Provide explanation or rename as “clinician’s name” | Match between system and the real world | 2.5 |
| Select check boxes | The check boxes are not noticeable | Make the check box more noticeable | Error prevention | 4 |
| Sharing camera and microphone | Instruction says “allow” camera and microphone, but popup says “share” | Keep the instruction consistent with the website features | Consistency and standards | 3 |
| An email verification is sent to the user | Email is very lengthy and has too many links | Email could consist of a body with just the essential links | Esthetic and minimalistic design | 3.5 |
| Click on the link in the welcome email sent by the company | Clicking on the link does not lead to log-in page. Instead, it downloads the application | Reword the link description or the link must lead to the log-in page | Consistency and standards | 0 |
| Click on email icon on top right corner of the application | Not all users may recognize the icon of an envelope as symbolizing email | There could be a label below the icon | Error prevention | 3 |
| Click log-in | Log-in button remains inactive if the portal is entered after entering username and password | Application should show an error message | Help users recognize, diagnose, and recover from errors | 3 |
| Downloading .exe file | Does not prompt to confirm if download should be initiated. | Notify user before downloading. | Visibility of system status | 3.5 |
| Enter email address in “Enter your email” tab | Email id is mandatory and cannot proceed to free video sign up option | Email entry could be on top with the sign-up for free tab below it instead of beside it | Error prevention | 3 |
| Click on the your account URL in the welcome email | Email contains a link for online account and another link for downloading. User might get confused and download application | Provide sufficient information about each link | Error prevention. | 4 |
| Selecting check in devices and software | There is multiple check in options which may confuse users | Provide sufficient information about each device and software | Error prevention. | 3 |
| Set camera, microphone, and speaker | There is no option to go back and redo these actions if they are missed | Provide an option to do these checks when necessary | Help users recognize, diagnose, and recover from errors | 2 |
Heuristic violations identified while concluding the telemedicine session.
| Task | Problem description | Solution recommendation | Heuristic violated | Severity rating |
| Click on red phone icon at the bottom of the page to end session | Remains in full screen even after ending the call | A dialog box saying press escape or automatically escape from full screen | Error prevention | 1 |
| Log-out of the application | No obvious log-out button | Provide conspicuous log-out button | Visibility of system status | 4 |
| Click on log-out | Log-out button is not easily seen | Provide conspicuous log-out button | Visibility of system status | 3 |
| No issues were identified | ||||
Figure 6Heuristics violated during the telemedicine initiation session.
Figure 8Heuristics violated during the telemedicine session conclusion.
Figure 9Microphone and camera sharing option.
Figure 10Absence of log-out option.
Figure 11Multiple log-in options in Polycom.
Figure 12Information processing model.
Heuristic violations identified during the telemedicine session.
| Task | Problem description | Solution recommendation | Heuristic violated | Severity rating |
| Click on email tab on the right side of the link | Not enough information provided about copy and email tabs. Directly going to default mail client | Popup boxes explaining meaning or function. Users need to choose the email client | User control and freedom | 3.3 |
| Enter data in chat box provided at the bottom right corner of the screen | The notification for an incoming message is not salient. Only the chat box symbol turns red | Make the chat box header turn another color | Visibility of system status | 4 |
| Click on email icon on top right corner of the application | Clicking on the icon directly leads to default mail client | Application needs to allow user to choose preferred email client | User control and freedom | 4 |
| Click on your name | Room owner’s name is shown under “my contacts.” Tab or option to the chat room is not obvious | Popup with “connect your room” button needs to pop up when the user hovers the mouse over the name | Visibility of system status | 3.3 |
| Patient comes online | No popup when the patient comes online | Popup and audio notification to indicate that the patient is online | Visibility of system status | 3 |
| Inviting patient | Direct email invitation and copy option are next to each other. This may confuse the user about whether both actions must be completed or only one | A simple “or” in between the two tabs | Esthetic and minimalist design | 3 |
| Disabling video and audio | Video and audio toggling icons are not salient | Icon could be presented in a brighter color | Recognition rather than recall | 3 |
| Enlarging the screen | Application does not have a full screen button. User has to drag to enlarge the screen | Provide a full screen button | Consistency and standards | 4 |
| Compose email in default email client | The invitation to the patient has to be sent from the default email client | Application must provide the option to the user regarding preferred email client | User control and freedom | 4 |
| Compose invitation email to patient | Application always redirects to default mailer | An option to enter patient’s email id could be provided with an example invitation email | User control and freedom | 4 |
| Compose email in default email client | Directly goes to default mail client | Allow user to choose preferred email client | User control and freedom | 4 |
| Enter full screen by clicking on full screen icon at the bottom of the page | System says “my rpcloud.vc” is full screen when the view is changed to full screen mode | Use terms which user can easily understand | Match between system and the real world | 1 |