Evaluation Results of Low-fidelity Prototype

In this post we are uploading our resutls from the evaluation process of our first paper prototype.
You can find all the information attached in this document:
Usability Evaluation Report

Low-Fidelity Prototype

Based on our analysis we have build our first low-fidelity prototype. At first we choosed paper prototype because we though it was going to be fast and we wouldnt spend much time on this stage.

 But after two long sessions on building our prototype we noticed that this method has also its bad side: 

1. We had to make the screen again if we write something wrong.

We are presenting below our results for tre scenarious

1. Make an appointment with a general doctor

Description of the situation: 

Ina is a student from Tirana who is studying in UPM this year. It’s her second month in Madrid and she doesn’t speak Spanish at all. This weekend she was feeling sick , she had cough but she thought she was going to be ok with some tea. But she is still feeling sick and she has a pain on her chest. She thinks it is not emergency but it will be good if she goes to a hospital around her house on Thursday morning between 8:30 AM to 10 AM. She has never been to hospital here, she doesn’t know where the hospitals are, her friends are foreigner too … But her friends told her that she can see a general doctor in the hospital and they will direct her to the necessary doctor. So she is going to use the software to find a hospital close to her home and make an appointment. 


Scenario:

Ina will search for the best hospital close to her house by choosing search by current location.

The results of the hospital will be shown in a map form.

Since she wants the best hospital close to her house it will be hard for her to find in the map so she will switch to the list view to filter for the hospitals based on rating.

She will pick the first hospital in list and she will choose on which date she wants the appoinment . She thinks that  on 7th its a good date for her so she put on the date field 7/04/2011. Then the table with the time available by the hostpital is shown to her. She wants to go early in the morning so she picks the time 8:30 Am , and then she pres on th submit button. The list of her waitting appoinment is shown to her. The first one in the list is the appoinment she just made. There she can see the adress of the hospital and how to get to that hospital. In a very short period of time she could make an appoinemnt.

She is happy for this

We uploaded a video that shows how Ina will interact with our system to perform her task:

PrintScreans of our prototype:

2. Find the best hospital for demartology

Description of the situation : 

Martin has started to work in Madrid 2 weeks ago. Since the last 2 days he has a rash on his face. He first thought it will pass by time but it didnt. Now he wants to see a doctor for this. Since he is new in town he doesnt have a family doctor but his company provides him a private insurance from AIG. Since the insurance will cover his expenses he wants to go to the best private hospital in madrid and make an appointment with directly a dermatologist. He wants to see the doctor in the morning of 07.04.2011 


Scenario

Martin open the applications from his mobile phone. He clicks on find  Healthcare Institution since he is looking for one. He knows that he doesnt need a doctor but he needs to find a best demartologist where he can use his insurance . So he goes to Advance Search. He fills the data of the Advance Search:

Selecting the Public and Private Hospitals by Type of Institucion

From Departaments he chooses Demartology

From insurance he chooses  Aig

As location he type Madrid since he is looking in all the city and

Then he click on the search to view the results.

He order hospitals by rate and chooses the first one.

He likes the rates and reviews for that hospital so he wants to make an appoinment with it. So he choose a date , he thinks that 7th of April is good and he type the date then the time table with free slots is shown to him. He picks the morning ones and submit his request for appoinemnt. After it he can find information how to go to that hospital and other inforamtion related to it. He feel happy that in a very short period of time he could make an appoinment with the best hospital in Madrid.

Video that shows how Martin would perform the steps with our application:

PrintScreans of our prototype:

3. Check Test Results

Description of the situation : 

Martin had seen a dermatologist last week on 7th of april in Hospital Moncloa. The doctor told him that the laborotory results will be available for him this week and based on these results he would let him know if he needs another session for his treatment. Hence he wants to see if his results are in the system and check them to see everything is ok with him or to see if he needs to make another appointment.. 

Scenario:

Marcin will navigate to his profile page to see the results of his previous appointments..

First he has to login to the system with his username and password

In his profile page he can update his personal information, see awaiting and past appointments and check the results from past appointments

He will go to the results page and see that his last appointment at Hospital Moncloa has a new result available

On this result he will see the doctor's note that says he is fine but he needs to make another appointment next month.

And he will also see the doctor's attachment which contains the result of his blood test.

He will download the document for detailed information.

Video that shows how Martin would perform the steps with our application:

PrintScreans of our prototype:

To view our presentation on prototype click on the link below:

Presentation

User Roles Analysis

Based on the interviews we tried to characterized and understand our user and user roles as much as we could.

The main goals for each user group are the following:

Travelling Users

- Searching health institutions and locating them on the map to get directions.

- Make appointments with the hospitals

- Checking lab results

- Finding the best option when they look for a specific doctor.

Residential Users

- Searching health institutions and locating them on the map to get directions.

- Making appointments with family doctors or special doctors.

- Checking lab results

- Finding the best option when they look for a specific doctor.

Non-registered Users

- Reaching the emergency center as soon as possible.

- Searching health institutions and locating them on the map to get directions.

If you want to view the table in PDF format please click on the link below:
User Analysis

Hierarchical Task Analysis (HTA)

After we have performed the brainstorming within our team we had in our minds some possible functionalities that we can include to our system.  With the interviews, we could understand how our users would behave and what would be their expectations and priorities.

Hence we did another session with our team to hierarchically decompose the possible tasks. We started with the main tasks and performed a breadth-first decomposition according to users perspective.

For the complete document please click on the link below:

Hierarchical Task Analysis Document

Contextual Analysis

For contextual analysis, we have interviewed students from UPM and students who don't study at our university. We have interviewed 12 students in an age range 20-27, male and female, residential and foreigner. We couldn't interview people that are not students and older so this part is missing in our contextual analysis. The fact that our users are young might imply that they are somehow familiar with mobile applications since most of them own mobiles and know how to use applications quite well. Because we couldn't´t interview people who might not be familiar with mobile applications we have a limitation in our contextual analysis.

We performed the Task Scenario Analysis to undersand the users Goals.

In the link below you will find a complete description of our anylsis for this :

Contextual Analysis Document

BrainStorming Technique

Our brainstorming took place after we finished competative analysis. We had some ideas from our competitors and we started generated the new ideas for our software. This brainstormins was organized in two session.

In the first session we generated the main ideas in about 2-3 hours. The results are shown in the below pics:

The second session was after we interviewd our users. We had some new ideas after that and so we had another session of brainstorming which was shorter than the first one. The results of it are displayed below:

Competitor Analysis Technique

Summary - The three mobile applications we have analyzed as competitors are very different from each other. One of them offers users to locate health institutions and information on symptoms and diseases, another offers physicians the possibility of having all their patient information on their phone as well as their appointments and round lists, and the last one offers users reminders of medical screening for primary prevention of diseases. None of the above applications offers all the functionalities in our application.

Most of the applications are for doctors and a few of them are to be used by the patient.

We had difficulties in finding the right applications to use in our analysis because there are plenty of them in Internet but not all of them work. In their website there were only few reviews from other people who used it so it was hard to understand how useful these software are. We also found some other that might be of interest to us but they weren't available for free.

Please follow this link to view the full document of our analysis:

Competitor Analysis Document