Patient insight dashboard
B2B patient portal for medical team
Hours
→
<30 min
10×
faster
Track the patient's treatment process, showing the steps that have been completed, the current step, and the arrangement for the next step. This allows users to see the patient's current treatment status at a glance.
Risk factors are deadly for patients, therefore they are one of the most important pieces of information for doctors. Highlight the risk factors in red so that doctors can see them clearly.
In the main card, information is organized by two navigation bars: the first for switching report categories and the second for ordering reports chronologically. This clear structure minimizes clicks, facilitating easier and more intuitive navigation.
The scattered information about RT treatment, simulation order, and prescription is organized into a table, which allows for a clear overview and easy comparison.
Conducted 4 competitive analyses, 6 stakeholder interviews, translated findings and patient info into dashboard features.
Led the layout exploration process, conducted user testings with 10+ users.
Led the information cards design, iterated the color coordination and dark mode design.
Medical team struggled to quickly grasp patient's condition.
At MSK Cancer Center, cancer patients undergo prolonged treatment journeys involving various healthcare roles. Patient medical records span extensive timeframes, encompassing diverse types and originating from various sources. For the healthcare team, comprehending both patients' historical data and current status is an essential prerequisite for making informed decisions.
Patient has long medical records, and will generate more in the incoming treatment process
Vital medical review in a sea of files
Getting to know the 3 user groups
Through stakeholder interviews, we got to know that the roles involved in the medical team collaborate with each other, with the three most important roles being the radiation oncologist, medical physicist, and radiation therapist; the nurse and scheduler help at each step. The relation of the roles can be simplified in the following stakeholder diagram:
3 stakeholder groups map
The patient info exchange between the 3 user groups is like a relay race
After learning about the steps of cancer treatment and the composition of the medical team through secondary research, we conducted expert interviews with the medical team in order to further understand the daily workflow of our target users.
Collaboration and data transaction during the treatment process
only one solution allowed.
Our client did not agree to develop customized dashboards for each role as the development process was very time-consuming. Therefore, we needed to figure out an information hierarchy that would meet the needs of each role without making the dashboard too complex.
We held a prioritization workshop using the MoSCoW methodology to work with healthcare team members to prioritize patient dashboard functionality and reach consensus on role-specific needs.
Patient data ranking from 3 user groups
Based on the results of the ranking of the 3 user groups, I decided to give a higher priority to the information that 'must have', i.e. priority display and fewer clicks; conversely, a lower priority to the more unnecessary information.
Based on the ranking of the patient data, we got the following information hierarchy, which built the foundation for the prototype layout exploration.
Before we started visual prototyping, we set goals for the final design based on what we found in our research.
Identify at risk factors
Open and close windows
5 min with opening different platforms
30 min+ reading
< 3 min
< 3 min
< 5 clicks
Navigate to needed files
Switching between files
Before
Goal
I brainstormed a series of dashboard layouts to adequately display patient data and meet user needs.
We tested the brainstormed dashboard layouts with users, allowing them to choose the layout that best suited their life scenarios and the elements they preferred.
We conducted an initial test of the first round of layout exploration with the medical team 3 user groups conducting 5 think-aloudsessions. From the testings, here are users' preferences.
progress tracking
patient navigation
info cards
highlighted info
I integrated user-picked favorite elements and considered specific patient information data to come up with a preliminary layout for the dashboard.
When I started to dive into the design and put in specific patient information, the amount of information exceeded the original estimate. I was then faced with the challenge of showing the information all at once would result in information overload, but that would reduce clicks; keeping the interface as simple as possible would increase the number of clicks.
information overload but less clicks
clear display avoid distraction but more clicks
“I wish I could easily find the file I need, a few clicks are acceptable. Comparing the reports on the screen is not necessary.”
Concise information display
Clear navigation to minimize clicks
Where we landed
Key info at a glance
Adapt to different work environments
Identify at risk factors
< 5 clicks
< 3 min
< 3 min
at a glance
👍
👍
👍
a few seconds
no more than 2 clicks
Navigate to needed files
Switching between files
Goal
Result
In the designing process, managing and organizing an overwhelming amount of patient data has been a challenge. The complexity of this data often led to confusion in aligning and interpreting information accurately. This issue was not just a technical hurdle but also a user experience bottleneck. Recognizing this challenge, we turned to the most valuable resource available - the users themselves. Engaging directly with medical professionals, we sought their input to understand their workflows, pain points, and the specific types of data most pertinent to their daily tasks. The involvement of users was not just a step in the process; it was the cornerstone of our approach. Their insights and feedback were invaluable in cutting through the complexity of the data and guiding us toward a solution that truly served their needs. This user-centric approach not only resolved our initial challenge but also set a precedent for how we tackle decision-making in all our future projects.