Heath Data Management Application Design

User Experience Design
Project Overview
Design for medical record keeping application. Taken through design process from problem definition to mid fidelity prototype and presented as the final project for General Assembly's User Experience Design Course. Project was completed within the 6 week time constraint of the class.
Full Presentation

Problem Definition

Do people keep track of their health?

The problem I suspect is that there is not a easy way to record and access all the information pertaining to one's health.

People need a way to easily record and keep track of their health and medical history because staying healthy is a lifelong challenge and having records from the past can help you and your doctor know what is best for you.

User Research

User Interviews

I want to learn how different people currently keep track of their medical data, and how much they know about their own health. I want to see what people would want to know.

Interviewed 12 People

Age Range 21-56

4 Parents

2 College Students

People don’t have a consistent nor organized method of recording their medical data.

“These are things I should know and honestly I just don’t have it recorded anywhere and I don’t think anyone else does”

Most people don’t track their current & past medications, which can lead to difficult & dangerous situations.

“So much variability…. been on 4 different medications depending on which doctor I’m going to. Why should my medicine change if I haven't changed. Now that I know more I tell them exactly what I want“
“I had an allergic reaction to an antibiotic, and I don’t know what it was. Probably something I should know and tell a doctor...”

Most people don’t track their current & past medications, which can lead to difficult & dangerous situations.

“I want to be more of a knowledgeable partner with my doctor when making decisions on my health”

Target Audience

User Personas

As the target audience for this product includes just about any human being, 5 personas were identified as being audience who would potentially be looking for different features and content in the application. These are who we want to keep in mind when developing the product.


AGE: 48
  • goes to the doctor, but only when something is wrong
  • some health issues in the past that should be monitored
  • experiences pain from time to time but usually passes it off as normal 
  • actively taking medication but is sometimes inconsistent

My health records are not complete, not easily accessible, lost, or forgotten.


I want to be more of a knowledgeable partner with my doctor when making decisions on my health.


AGE: 42
  • shares responsibilities of the dependents with a partner
  • often only one partner is present to receive information at a given time
  • sometimes forgets to take care of himself

I have to both track my health and the health of my kids, share the management of my child's health with my partner, and transfer my child's health information to them as they grow older and become more independent.


I want to have better knowledge on my health and the health of my children.


AGE: 22
  • newly independent
  • going to a new set of doctors
  • doesn’t prioritize their health

Finding a new doctor is difficult, and entirely on me to do.
My new doctor doesn't have any of my medical records.
I am now fully independent from my parents.
Doesn't fully know the insurance system yet.


Be happy and healthy.


AGE: 16
  • health is still managed by parents
  • recently able to go to appointments alone
  • does not know a lot about her own health

Doesn't know the answers to the questions the doctor is asking.
Doesn't feel comfortable offering personal details.


Be happy and healthy.


AGE: 32
  • doctor in a big city
  • has both regular patients and new patients
  • limited time with each patient

Don't have full set of information.
Can't fully rely on information given.


I want to have more information and evidence from which to base my medical decisions and advice from. I want to give the best care to my patients to keep them happy and healthy.

Story Boards

Story Boards

Taking inspiration from the interviews conducted these story boards were created to depict situations in which the application can be effective in solving user's wants and needs.

Information Architecture

Card Sorting

User research and a card sorting interviews were conducted in order to determine the health data people are interested in managing and how they organize it.

The results of the card sorting user testing showed that everyone has a different way of organizing medical information. Often terms belong in more than one category and there are many things that are hard to label or define.

Information Architecture

Site Map

Using the results of the the research the site map was produced to investigate the hierarchy of the main components of the application.

User Flows

User Flows

The user flows identify the screens and actions of a user stepping through specific features. The main user interactions for many of the features consist of data viewing, adding, and editing. We want the input of data and information to be simple and easy for users as the app is user content driven.

Mid Fidelity

Wireframe & Prototype

Following the time constraints of the class this mid fidelity prototype was developed in Sketch within a weeks time to be used for user testing and final presentation to the class.

I focused on three main aspects of the app I wanted to tackle - profile and historical health data display and input, medication tracking features, and doctor information features.

The screens created were selected and designed for the purpose of creating a prototype that could navigate through three usability testing scenarios.