Table 3 Some examples of usability problems based on Nielsen principles
From: A heuristic evaluation of a pharmacy surveillance information system
Nielson Principles | Usability Problems | Solutions |
|---|---|---|
Visibility of system status | - Time-consuming search processes - Elongation time in uploading a picture - Displaying ambiguous message after pressing the “save” button when registering non-Iranian patients | - Resolving the technical mistakes in the back-end of the PSIS by the developer team - Modifying the settings related to “non-Iranian patients” page |
Match between system and the real world | - Using the “disabling” label for the “trash” icon in the “users’ management” section - Using the “pencil” icon for “delete” in the “patient management” section - Using the “pencil” icon for “reset password” in the “users’ management” section - Using an inappropriate “change medication type” icon in the “medication management” section. | - Reviewing all labels and correcting the mismatches - Reviewing all icons and modifying the mismatches |
User control and freedom | - Users can’t use multiple search filters - Users can’t change the CAPTCHA code when it is illegible and must refresh the page - Users can’t exit the calendar using the Esc button | - Improving the search filter setting by the developer team - Adding the ability to change the CAPTCHA code |
Consistency and standards | - There are two different names (banned patients/misuser patients) for one field (misuser patients) - Using a unique option (Yes/No) in all system alerts - Using 10 and 11 characters for the patient’s national code and mobile phone. - Using different names for similar menus | - Reviewing all fields and menu to unify their name - Unification of the options in all system alert messages - Adapting each numerical field to the number of allowed characters |
Error prevention | - Accepting duplicate unique codes such as national code - Decrease and increase arrows in numeric fields - Users failed to change the system logo - Lack of using red star for some mandatory data elements | - Modifying the system programming to prevent registering unique codes such as national code, physician code, and pharmacologist code - Changing the format of some fields - Modifying the system to support all image format - Clarifying the mandatory fields with the red star |
Recognition rather than recall | - Users expect reports in .pdf format to open in a new tab but they open on the main page. | - Modifying the settings to open the report page in a new window |
Flexibility and efficiency of use | - Difficulty in use of calendar - Lack of file uploading in the internal messaging system | - Changing the calendar type in the system - Increasing the volume capacity for uploading images |
Aesthetic and minimalist design | - Using “home” and “exit” icons instead of “home page” and “exit” labels - Inappropriate color and size of some icons and notifications - Visual clutter on the page | - Using appropriate icons instead of some labels - Reviewing all icons to modify their size and color - Redesigning the pages with visual clutter and adjusting the length of field boxes |
Help users recognize, diagnose and recover from error | - Lack of an appropriate message when image uploading - Inappropriate message when date entry is incorrect | - Presenting “upload completed” message when images are uploaded successfully. - Displaying a notification when data entry is incorrect and specifying incorrect or incomplete fields. |
Help and documentation | - Repeating the help description for all mandatory data elements | - Displaying a minimal guide on the data entry page that “Starred fields are mandatory” |