Versions Compared

Key

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

Goal: “Discover users feedback about the current UI and identify problems and potentials to treat in the new design guideline“

Content

Table of Contents
minLevel1
maxLevel2
outlinetrue
styledefault
typelist
printabletrue

Personas Overview:

The following list provides an overview of all user personas in openIMIS. All information in the personas are 100% made up and generated. The following details from the User manual were used to generate the personas: https://openimis.atlassian.net/wiki/x/4wAA2

Role

Name

Location

Age

Background

Goals

Challenges

Enrolment Officer

Fatima Mwanga

Tanzania

32

Social sciences, 5 years in health

Maximize enrolment, improve community awareness

Tech access in remote areas, language barriers

Clerk

Ramesh Gurung

Nepal

28

Office management diploma, 4 years

Maintain accurate records, streamline processing

Application backlog, changing regulations

Accountant

Jean-Paul Ngome

Cameroon

40

Accounting degree, 10 years experience

Accurate financial records, timely reporting

Data reconciliation, resource limitations

Receptionist

Aisha Thapa

Nepal

35

Healthcare management degree, 6 years

Ensure patient access to claim forms, facilitate claims process

High patient volume, ensuring accurate info

Claim Administrator

Ramesh Gurung

Nepal

28

Office management diploma, 4 years

Timely claims submission, improve provider communication

High volume claims, tracking claims status

Medical Officer

Dr. Lila Acharya

Nepal

45

Medical degree, 15 years experience

Ensure claim accuracy, enhance collaboration

Inconsistent info, tight deadlines

Scheme Administrator

Pascal Nguene

Cameroon

38

Public administration degree, 8 years

Smooth scheme operation, provide accurate data

Cumbersome management, data accuracy

openIMIS Administrator

Sara Mbuyu

Tanzania

30

IT background, 5 years in admin

Ensure data security, maintain system reliability

Disruptive updates, user access control

Personas Details:

Expand
titleUser Persona 1: Enrolment Officer

Persona: Fatima Mwanga

  • Location: Tanzania

  • Age: 32

  • Gender: Female

  • Background:

    • Fatima has a degree in social sciences and has been working in health services for 5 years.

    • She has experience in community outreach and public health initiatives.

  • Role & Responsibilities:

    • Enrolls insurees and submits enrollment forms to health insurance administration.

    • Handles policy modifications.

    • Collects feedback from scheme patients and submits it to the health insurance administration.

  • Available Functionality:

    • Capture a photo of an insuree.

    • Send a photo.

    • Inquiry on an insuree.

    • Collect feedback from an insuree.

  • Goals:

    • To ensure maximum enrollment of eligible beneficiaries.

    • To improve community understanding of health insurance benefits.

  • Challenges:

    • Limited access to technology in remote areas.

    • Language barriers with some community members.

  • Technology Proficiency: Basic to intermediate; comfortable with mobile devices but needs training for advanced software.

...

Expand
titleAdd/Update/Delete Family/Group

Heuristic Evaluation

openIMIS

  1. Add/Update/Delete Family/Group:

    Evaluator: Marvin M
    Date : 20.10.2024
    Task : Add/Update/Delete Family/Group

  • Visibility:

    • Issues:

      • Date-Picker info missing for birthday input field / photo date

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

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

      • Reload button has no warning if you really want to reload

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

    • Recommendations:

      • Add DatePicker icon

      • Add feedback notification for search

      • Add feedback information "nothing found" etc.

      • Add forwarding or other response after adding family

      • Refresh the Family-List at a certain point (either if notification arrived or after X seconds)

  • Matching real-world

    • Issues:

      • Only seven inputs needed but 28 input-fields are shown to get answered.

      • After changing from one page to another there is no information shown what type of interaction is happening. If you change from Family to “Add Policy” then you get to the “Policy” Page. But there is no information that you now can add information to the Policy.
        -> Add Policy looks exactly the same as “Read” Policy

      • User hast to scroll through all lists even though he just wants to add/change one information (ex. Policies)

    • Recommendations:

      • Add any information that the user is aware of which action he is doing.

      • Displaying the “menus” only as header or card without records to easily choose the wanted menu

  • User Control and Freedom

    • Issues:

      • Undo and Redo are not fully supported

      • Reload button does not clear all values

      • Poverty State is shown in Family List as checkbox. There is no visual effect which shows that the checkbox cannot be changed.

    • Recommendations:

      • Add a visual indication which shows, that those checkboxes are read only

  • Consistency and Standards

    • Issues:

      • Add Family/Group is possible to do directly from Navigation. All other entries can only be generated from the regarding list. Double entry of Family/Group in Navigation is also bit confusing.

    • Recommendations:

  • Error Prevention

    • Issues:

      • Missing information if you really want to reload the page if data was already entered.

      • No Validation of input fields given

    • Recommendations:

      • Add warning if user wants to reload

      • Add validation to input fields

  • Recognition Rather
    Than Recall

    • Issues:

    • Recommendations:

  • Flexibility and
    Efficiency of Use

    • Issues:

      • Search for Village or Health Facility instead of going through the different fields of information
        Recommendations:

  • Aesthetic and
    Minimalist Design

    • Issues:

      • Field "Status" is shown but cannot be changed or does not give any appended information

      • A lot of information is shown double times. Family head is shown in header, Family Details and Insurees

    • Recommendations:

  • Help Users Recognize,
    Diagnose, and Recover
    from Errors

    • Issues:

      • Missing tooltips for some buttons.

      • Documentation of some processes is really Comprehensive but no direct information panels are used inside the system

    • Recommendations:

  • Help and Documentation

    • Issues:

    • Recommendations:

Expand
titleAdd/Update/Delete Insuree

Heuristic Evaluation

openIMIS

  1. Add/Update/Delete Insuree

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

  • Visibility:

    • Issues:

      • After adding an insuree to a existing family and changing his/her Address, the next time if you open the insuree, the Checkbox “Same Address” is ticked and the entry “Address” hidden. Same for “Village”

    • Recommendations:

      • Show the differentAddress, Village details.

  • Matching real-world

    • Issues:

      • If you want to add a insuree from the list of all insurees then it randomly picks a existing family/group for you. The insuree will therefore be added to the wrong family.

    • Recommendations:

      • Asking the User to which family he wants to add the insuree to. Give the possibility to create a new one if its not existing.

  • User Control and Freedom

    • Issues:

      • Once a Photo Officer was inserted and afterwards removed, then the list of Officers is not going to be provided anymore. The Search needs then a manual input.

    • Recommendations:

      • Make the Photo Officer Search the same component as “Health Facility Search”. This component is much more user friendly

  • Consistency and Standards

    • Issues:

    • Recommendations:

  • Error Prevention

    • Issues:

      • After adding a insuree you can go and update the user status. For the status “inactive” as well as “dead”. The User can therefore the no longer change the user status.

    • Recommendations:

      • Add Reasons for inactivity or dead.

  • Recognition Rather
    Than Recall

    • Issues:

    • Recommendations:

  • Flexibility and
    Efficiency of Use

    • Issues:

    • Recommendations:

  • Aesthetic and
    Minimalist Design

    • Issues:

      • After choosing a Relationship in the add insuree, the field adds a magnifying glass to the result. This indicates it would act as a search. Same for Profession, Education.

    • Recommendations:

      • Remove the magnifying glass from the result

  • Help Users Recognize,
    Diagnose, and Recover
    from Errors

    • Issues:

    • Recommendations:

  • Help and Documentation

    • Issues:

    • Recommendations:

Expand
titleAdd/Update/Delete Policies

Heuristic Evaluation

openIMIS

  1. Add/Update/Delete Policies

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

  • Visibility:

    • Issues:

      • During entering the policy only 3 fields are needed to complete. There are a lot more information that cannot be changed or used for the creation of the policy

    • Recommendations:

      • Hide the overload of information which are not needed.

  • Matching real-world

    • Issues:

    • Recommendations:

  • User Control and Freedom

    • Issues:

      • Needed double click for choosing an element in the list.

    • Recommendations:

      • Add One-Click Elements to List

  • Consistency and Standards

    • Issues:

      • Policy can only be added from Family-Page and not as usual from the list of Policies

      • In Policy details the “Open Family” Button is displayed on the other side than all other buttons as usually.

    • Recommendations:

      • Add create Policy Button to the list of Policies

  • Error Prevention

    • Issues:

      • Update and Read Policy look exactly the same. Not clear what a user can do with the entry.

    • Recommendations:

      • Clarify the possible interactions.

  • Recognition Rather
    Than Recall

    • Issues:

    • Recommendations:

  • Flexibility and
    Efficiency of Use

    • Issues:

    • Recommendations:

  • Aesthetic and
    Minimalist Design

    • Issues:

    • Recommendations:

  • Help Users Recognize,
    Diagnose, and Recover
    from Errors

    • Issues:

      • Notifications after the asynchronous job are hard to find/recognize. The Notifications do not have links to the elements or a detailed error description.

    • Recommendations:

      • Add Links and error description to the Notifications. If its an error, add all inserted data back again, so that the user only needs to change the failure.

  • Help and Documentation

    • Issues:

    • Recommendations:

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:

    • Recommendations:

  • Matching real-world

    • Issues:

    • Recommendations:

  • User Control and Freedom

    • Issues:

    • Recommendations:

  • 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:

    • Recommendations:

  • Help and Documentation

    • Issues:

    • Recommendations:

...

Findings