One Medical Health Profile


One Medical is always finding ways to improve the proactive care quality for our patients. One way to do this is to provide transparency to our patients so they can take control of their own health decisions. We researched, designed and iterated on ways we can provide our patients with a one stop snapshot of their health.


My Role

I led the end to end design for both iOS and Android platforms though research, user testing, wireframing, visual design, and prototyping. I worked closely with engineers to ensure design quality standards. I collaborated with the Product Manager to identify user needs and defining features.


The Goal

The goal for this project was to transform the current non informative Profile page into a portal that captures the entire health snapshot of the user. We wanted to provide our users with transparency into their health records.



After I was assigned this project, I worked closely with PMs and Engineers to brainstorm ideas. I created user stories with the PM to make sure we cover all the functionality and solve our user's needs. I worked closely with engineers to help them with developing realistic development estimates. Involving cross functional teams early on in the process is crucial for the success of a project. After the initial ideation period, I started my design process. 


Current Profile State


Findings from user testing the current Profile

Prior to joining the team, our user researcher did some testing to understand what were the top things our users wanted to see on their profile. The findings were very crucial in defining the goal of the new Health Profile. Many of our users expressed the desire for transparency into their health.

"The more transparency I have on my health information, the more I feel empowered to control it" 

"Doctors always ask the same questions even when I have already answered them." 

"I want to see what the doctor sees."


User Testing with Wireframes

Health Wires.png

After we tested different versions, we found that the version with a dashboard view of the user's health information resonated with them the most. Users liked how easy it was for them to scan through all the items in a high level and being able to drill down into each section.


The New Health Profile Experience


For the new health profile, I focused mainly on providing transparency to our patients about their health. I broke up the Health Profile into three different sections:

  • The header navigates the user into their personal info page. There they can view and edit details such as their contact info or insurance policies.
  • The Records section which shows the user a dashboard snapshot of their Vitals, Medications, Allergies, and Vaccines.
  • The History timeline section which shows the user their complete history of everything they have done at our offices. 

These components added together gave our patients a quick snapshot of their health. If desired, the patient can also go into detailed individual views to see their full history.


Detailed Health Records


I created detailed views for each dashboard section in the Records view. The left screen is the Measurements and Vitals detailed section. The user can see all the vitals the doctor has recorded during their visits, and they can add to the measurements if they've recorded them at home.

The right screens show how the user can add blood pressure readings. The background color of these screens correlate to the legend color on the graph.



Interactive Prototyping


Communicating the solution

I used Invision to create an interactive prototype. I wanted to communicate how the Health Profile ties together. 

The prototype above demonstrates the following actions:
1) Viewing the Records Dashboard
2) Viewing the Personal Info section
3) Viewing the History Timeline
4) Viewing the Measurements & Vitals dashboard

Prototyping is an important step in my design process because it helps with communicating design solutions across the org. I also found that delivering the prototype, along with static mocks and specs was very useful in communicating the desired behavior to the engineer.


What's next?

My next step is to continually monitor and study how users interact with my feature. Paying attention to stats and metrics will also help me determine what is successful and what needs continual work. There are always ways to improve designs.