Versions Compared

Version Old Version 11 New Version 12
Changes made by

Marvin Marqua

Marvin Marqua

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleAdd/Update/Delete Claims

Heuristic Evaluation

openIMIS

  1. Add/Update/Delete Claims

    Evaluator: Marvin M
    Date : 20.10.2024
    Task : Add/Update/Delete Claims

  • Visibility:

    • Issues:

      • Search Form for Claims is too intense. There are too many possible fields without a distribution into several “search topics” or similar. Preset search filters are getting lost by the mass of fields (example “Claim Status”).

    • Recommendations:

      • Divide Search Form into “search” and “advanced search”

  • Matching real-world

    • Issues:

    • Recommendations:

  • User Control and Freedom

    • Issues:

      • User can not select a Claim from the list by double click everywhere in the row. If you click on a control nothing happens.

    • Recommendations:

      • Change control fields to clickable labels

  • Consistency and Standards

    • Issues:

    • Recommendations:

  • Error Prevention

    • Issues:

    • Recommendations:

  • Recognition Rather
    Than Recall

    • Issues:

    • Recommendations:

  • Flexibility and
    Efficiency of Use

    • Issues:

      • Why does the Health Facility and Admin need to be entered before its even possible to enter a claim?

    • Recommendations:

  • Aesthetic and
    Minimalist Design

    • Issues:

    • Recommendations:

  • Help Users Recognize,
    Diagnose, and Recover
    from Errors

    • Issues:

      • Policy information in Claims are Red if inactive. This Text is the only “negative indicated” text in openIMIS with a red font color. The red color differ from the one in the status notification bar.

    • Recommendations:

      • Highlight the information differently. The red is nowhere else used and with the blue background not good readable.

  • Help and Documentation

    • Issues:

    • Recommendations:

Findings

Finding ID

Module

Finding Description

Severity Level

Evidence/Observations

Impact on User Experience

Recommendation

001

Multiple

Date-Picker info missing for birthday input field / photo date in add insuree.

minor

https://m3.material.io/components/date-pickers/accessibility#83faa6ed-e2a2-4959-bec6-bb4bb5f52747

- “The calendar icon is the exclusive entry point for the date picker.

This improves efficiency for a screen reader and other keyboard users, as it makes interaction with the date picker optional and reduces the amount of key presses required to input a date.”

The user does not know intuitively where to enter a date or where to click to enter the date.

For dates which are more then one or two years before the current date, it is complex to navigate in the picker modal.

  1. Add Date-Picker Icons to date inputs

  2. For Birthdate change to modal date input

https://m3.material.io/components/date-pickers/guidelines#76fda9a2-9563-4054-92fd-513db508cd33

002

Insurees/Policy

Search existing insuree as head of Family does not respond in a reasonable time. No Spinner or Search button + No information if nothing was found.

Moderate

Does not comply with the “Visibility Heuristic” from Nielsen. Its mentioned “Communicate clearly to users what the system’s state is” as well as “Present feedback to the user as quickly as possible (ideally, immediately).”

The user does not know if the search is working or not. Furthermore, its not possible to recognize what the search triggers. Additionally, the user needs to double-click the suggested insuree.

  1. Show that the fields are autocomplete or add tooltip/info

  2. Add spinner if search is loading longer

  3. Add information if nothing was found

    1. Use one-click for selecting a head insuree from the list

003

Multiple

After selecting save button the screen does not change. It just turns gray.

Major

Does not comply with the “Visibility Heuristic” from Nielsen. Its mentioned “Communicate clearly to users what the system’s state is” as well as “Present feedback to the user as quickly as possible (ideally, immediately).”

Users are confused if the operation they did was successful or not. Usability testing as well as the survey suggested, that the notification bar is not observed by the user. Hence, the user needs to check by themselves if their operation was successful or not.

  1. Change from Sidebar notification to a more visible one

  2. Redirect the user after hitting the save button to the list of elements

  3. Reload and sort the lists after the newest objects. (as most user answered they check again the entry in the list after creating it)

004

All

Reload button as well as reload page has no warning if you really want to reload. By hitting the button accidentally, all inserted data gets lost.

Moderate

Does not comply with the “User Control Heuristc” from Nielsen. As its known that users do perform actions by mistake it should be possible to give them a “emergency exit” to leave the unwanted action.

User needs to retype all inserted data.

  1. Adding a modal with the question whether a user really wants to reload the page.

005

Multiple

If a entry is deleted in the list, it will be displayed as gray stripped row. The list itself will not get refreshed afterwards.

Major

Does not comply with the “Visibility Heuristic” from Nielsen. Its mentioned “Communicate clearly to users what the system’s state is” as well as “Present feedback to the user as quickly as possible (ideally, immediately).”

User does not know whether the operation was successful or not. He needs to do an additional click to refresh the list and search for the record.

  1. Change from Sidebar notification to a more visible one

  2. Reload and sort the lists after the newest objects. (as most user answered they check again the entry in the list after creating it)

006

Multiple

Only some small amount of input-fields are needed but a lot more input-fields are shown on several forms (e.g. Add Family

Moderate

Does not comply with the “Aesthetic and Minimalist Design Heuristic” from Nielsen. “User interfaces should be simplified as much as possible, since
every additional feature or item of information on a screen is one
more thing to learn, one more thing to possibly misunderstand,
and one more thing to search through when looking for the thing
you want.”

Possibility to misunderstand an input-field is much higher. Also the frustration of a user increases. The required fields are not that easy to recognize anymore thats why the user will need more time to fill out the form.

  1. Put required fields together

  2. Check which information is really important and leave them on the screen

  3. Categorize the input-fields and organize them into containers

  4. Maybe change to a Wizard rather then a large form

007

008

009