The purpose of this project was to improve the usability of healthcare apps and make it easier for users
to access their healthcare information, communicate with providers, and keep their healthcare accounts on one platform.
The Olive app user needs a way to organize and manage their personal and family healthcare accounts.
When required to use multiple apps to access and keep track of healthcare information, it becomes
complicated for the user to keep track of schedules, costs of visits, insurance claims, and communications
with providers.
We will know this to be true when Olive app users are able to link 2 or more healthcare accounts on one platform
and can access tools and personal information across one or more profiles.
A possible solution to this problem will be to create an app that will allow the user to integrate their insurance information, medical provider, dental, and vision care. This will give the user access to manage each of their healthcare accounts and information in one platform.
Target Audience:
The target audience for this product is any user who is subscribed to an insurance plan
that has separate providers for vision and dental. The user will require all of their medical information on one
platform.
Competition:
Obvious competitors are other private medical providers such as Kaiser Permanente,
MyHealth, MyChart, and Carbon Health. A competitor would be any healthcare provider than offers medical, dental,
and vision in one platform.
Risk/Opportunity:
A risk to creating this app would be integrating the applications and information from a variety of medical providers.
There are not many apps that allow syncing, but one example would be TrueBill, a banking app, that syncs the information
so the user can access it in one application.
This provides an opportunity to create a more useful medical platform to eliminate using multiple apps for medical,
vision, dental, and insurance.
General Tasks:
Business Objectives:
Interview Questions:
Communication:
Finding A Doctor:
Making Payments:
Dental/Vision Coverage:
Scheduling Appointments:
Test Results:
Sutter Health Care provides coordinated care to more than 3 million Californians. It is a not-for-profit organization that puts resources back into its communities. Sutter hospitals serve more of the Medi-Cal patient population in Northern California than any other health system.* With over 12K physicians and 2k advanced practice clinicians, Sutter had over 1.5 million outpatient care visits in the last year.
Objective:
Abby recently had tests taken at her last visit to her medical provider. They informed her that the results
will be available in their healthcare application and she will get a notification when they are ready.
Entry Point: Launch of application
Success Criteria: Reviewing test results
Objective:
Joe has just enrolled in a new insurance plan through his employer. He needs to link his insurance information within
his healthcare application to be able to view what visits will be covered.
Entry Point: Launch of application
Success Criteria: Adding insurance information to account
For this task, I asked for 5 participants to do a physical and open card sort for the Olive app. The participants sorted 40 cards into relevant categories.
Analysis:
My initial thoughts on doing a closed card sort was that it would be biased based on where I would intuitively find
information searching through a healthcare app. The open card sort gave a lot of insight to what topics can be found in
general categories but other topics could easily placed throughout the application.
100% of participants agreed on the placement for the topics on payments, test results, and messages. 80% of the
participants had varying thoughts on where to put “settings” and “privacy”. Moving forward, I would like to do more
research to see if a closed card sort would generalize the placement of topics that are currently spread out.
User Errors
Issue 1: Linking an Account (high)
Problem:
When asked to navigate to their Account page to move forward with linking an account, the users were not able
to find the feature on the dashboard of where to find their Account settings. All 5 participants were challenged with
this issue.
Solution:
To resolve this issue, I will add text on the dashboard and include where to locate Accounts in the onboarding
process.
Issue 2: Coverage Costs (high)
Problem:
When asked to link a healthcare account, the users would navigate to their Coverage page from their dashboard.
Out of the 5 participants, 4 made this initial error.
Solution:
An option will be added to the Coverage page to “Link an Account” as well as in the Account settings.
Depending on the user, the option to link a healthcare account would fall under the coverage category or as an account
settings feature.
Issue 3: Sending a Message(medium)
Problem:
When asked to send a message to a provider, the users were confused as to where to enter their message. Out of
the five participants, two of the users clicked the send button before tapping the empty text field to enter a message.
Solution:
To resolve this issue I will add a placeholder text to help users identify the field in which to enter message
text.
Issue 4: Pop-up Notification (low)
Problem:
When the users bypassed clicking the popup notification and then returned to the dashboard, the notification
was no longer visible. The users were then not able to know if they had an unread message from a provider.
Solution: I will add a counter badge to the categories to help users remember if they have an unread message outside of
the popup notification.
Issue 5: Using Software (low)
Problem: When navigating through the prototype, the users would click through the screen arrows instead of the actual
prototype.
Solution: This error is low, but emphasizes the necessity for clear instructions on how to use the prototype before
testing.
Positive Quotes:
Negative Quotes:
The feedback was constructive and aligned with the participants behaviors while navigating through the prototype. I was able to update my prototype to how the users will intuitively use it best. I made it possible for the users to access the same features in the same amount of steps based on where they would naturally look for what they need. I would like to perform a usability test with a new set of participants to see if the same errors are made, as well as with the same participants to get their feedback on the improvements.