Case study

VisitER

VisitER is designed to enhance ER visiting experience by increasing patients' awareness of their wait status and streamlining the communication with the hospital staff.

🏥
Healthcare Industry
🎓
Group Coursework
⏱️
Oct, 2023 - Dec, 2023
👩🏻‍🤝‍👩🏼
Team
  • Hao Wu
  • Candice Zhou
  • Jasmine Zhang
  • Francesca Cheng

Background

Under the circumstances of master-level UX fundamental course project whose theme is:

Improving the citizenship experiences of people of Toronto.

My main responsibilities in the project:

Lead research activities

Secondary research, survey & interview design, and report delivery

Lead testing & evaluations

Usability testing and issues evaluations

Co-work on

Presentation structure, lo-fi wireframes, and medium-fidelity prototypes

Our Process

What exactly is the problem for ER visitors?

Topic & Problem Space

When discussing the concept of citizenship in Toronto, a prominent thought often centers on the experience of visiting Emergency Rooms (ERs). These visits are commonly associated with lengthy waits, tension, anxiety, and a sense of helplessness. To gain a deeper insight into this critical area, we have undertaken comprehensive secondary and primary research. This research focuses on the current state and prevailing challenges of ER visits, with an overarching aim to significantly improve the patient experience.

Collecting Insights

To emphasize with patients about their thoughts and feeling of visiting ERs and figure out their true pain points are, primary research is conducted through interview and survey.

25 Survey Responses

Survey is sent out to the general public on social media and the respondents will be screened by the first question that asks if they have been to a ER in GTA in the past 2 years.

Survey question & responses
9 Interviewees

Interviewees are recruited through our personal network of classmates and friends who do not have close relationship with us. Only those who have been to an ER in GTA in the past 2 years have been invited.

Interview notes
Categorize & Summarize

The raw data from interviews are categorized in the affinity map for critical insights.

Affinity map with insights from interviews
Findings

The raw data from interviews are categorized in the affinity map for critical insights.

Blindly long wait
The lack of information and timely updates about wait time leaves patients in blind status about next steps and the possible end.
👂
Understandable wait time
Actual waiting duration has little impact on patients’ satisfaction about the final treatment. They will show high level of empathy when knowing what’s happening.
📝️️
Preparation
Most people need some checklist or suggestions to make preparations.
Problem Statement

The current state of the Emergency Room (ER) has primarily focused on managing patient emergencies, providing timely medical care, and ensuring patient safety. What the existing product/service fails to address is to effectively communicate with patients, leaving them feeling like they haven't received timely care during their ER visit and lacking the necessary information to make informed decisions and engage fully in their healthcare experience.

Representative User - “Sally Waiphoever”

Knowing the general problems in ER visits, we have our persona, Sally Waiphoever, as the representative user, for whom we are going to dig deep into the mindset and possible solutions to relieve Sally’s pain points.

Persona
Sally’s Mindset

Sally’s Situation of Visiting ER

Based on our well-rounded understandings of Sally, we walk through the scenarios of her visiting the ER and vote on the painful moments, through which we can identify the issues most needed to be addressed through our design.

Most Painful Moments

Through the voting results, we can find that the most of painful moments are in the stage of waiting in ER.

How can we help improve this situation?

Design Objective

Knowing the general problem space and the specific pain points Sally has during visiting the ER, we craft the objective first as guideline for later solution design.

Our project will address this gap by implementing a comprehensive communication and information system that empowers patients to:

  • Enhance their awareness of the status in ER queue
  • Receive effective care during their ER visit
  • Actively participate in their healthcare decisions

Needs Statement

With the big objectives in mind, we create the needs statement for directional inspirations of enablement we would like to provide to users through our solution design.

Sally
Needs a way to
So that
make informed decisions of selecting among ERs
she will feel secured by familiarity and confidence
prepare what information to provide for the assessment
she would have a confident and smooth experience in ER
get informed about her waiting status
she will adjust her expectation accordingly and doesn’t feel lost
receive emotional support
she can get comfort and feels secured during the wait in ER
learn and understand her conditions or symptoms
she could be less stressed about her medical situation

Big Ideas

Aiming to meet the needs, we brainstorm various ideas and vote on its impact and feasibility for prioritization.

Assumptions

Considering the limits of healthcare industry, we have hypothesized the following two assumptions for a promising improved future of ER visit.

Hospitals are willing to share the information (treatment progress) for patients to view.
The wait time is available from the healthcare industry and can be updated in real time.
Prioritization Grid

The ideas that have high feasibility in term of scope and technical requirements while performing well in bring values to the industry and society (high impact) tend to be selected.

Selected Focus

Considering the timeline and guided by our prioritization grid, we have selected the following ideas to continue developing.

Design Goals

With amazing ideas selected, we set up goals for us to narrow down the focus and move forward towards the envisioned future of ER visitors.

Sally can
What
Wow
compare current waiting situations in nearby ERs
to make visit decisions with only one glance
know the status in ER queue
to make a better use of time while waiting
be informed of the possible situations impacting the ER
as soon as wait time changes

How would the solution be roughly like?

Lo-fi Wireframes

Setting up the core tasks we would like the initial solutions to realize, we combine our sketches in the order of task flows to validate its feasibility with representative users.

Lean Evaluation

We have walk 3 representative users through our lo-fi wireframes on paper and ask for their feedbacks, and we get the key findings as below:

  • News are too panicking to be shared
  • Need a detailed list view of ERs
  • Progress bar is better to be in vertical format for compatibility on mobile screen

What is the solution in details?

Does this solution work?

Usability Testing

To validate our revised solution’s feasibility, a formal round of evaluation and usability testing is conducted through observing and interviewing. Three representative users who is between 18 and 50 years old are invited to this session.

Observation
  • If users can finish the three core tasks successfully
  • Their understanding of the screen intention
Interview
  • Ask follow-up questions based on the observation
  • Collect new ideas for development inspiration
  • Gather feedback for improvement
Findings

Based on the evaluation analysis, critical issues are highlighted in sections of the “things to change” and “questions”, which will cause confusion and affect users going through the three basic functions to be aware fo their wait status. This would mainly include icon size, labeling, and component design, based on which we will revise our design as the first step accordingly.

Inspired by the “new ideas”, such as having notebook synced with doctor’s system, we will involve new futures while maintaining the solid base of “things that work”.

What we will do for next?

Next Steps

🛠️
Revise Design
Design is going to be revised based on the feedbacks collected from usability testing, especially around the details of ample touch area, labelling and component design.
🔁
Iterate Testing & Design
After revising and in the process of developing, other loops of designing, testing and revising will be adopted.
🌟
Develop Other Features
Other potential functions can be involved to enhance the ER visit experience further.

Key Learnings

  • Avoid idea of solutions ahead of research.
  • Compared with what we actually produce, such as the wireframes, the rationales of why we need each step in the design process and how we develop the design from one to another deserve more attention.
  • Notice that we are designing for Sally, not ourselves. Try to avoid thinking what we would do if we were Sally. We are not. Instead, we should analyze based on the data collected.