Enhancing Patient Screening with Aetna

Case Study

Overview

I joined Aetna Digital's design team as a UX design intern as the team worked to add new features to the Aetna Health application. It was an incredible opportunity — taking the complexities of health insurance and creating a user-friendly application is no easy task. The design team referred to itself as team MISL: Make Insurance Suck Less.

This case study focuses on the intern capstone project. I worked with five interns from various other fields; we had interns from development, business, and marketing represented. We were tasked with designing a solution to some sort of health equity problem.

Understanding the Problem

A team member had a family member die from colorectal cancer, so we decided to look into the problems affecting this cancer. To learn more, we began researching some statistics. (source)

50+

Average Age when Diagnosed

2nd

Leading Cause of Cancer Death

65%

Five-Year Survival Rate

90%

Five-Year Survival Rate, with early screenings

Diving deeper into our research, we also found that colorectal cancer disproponately affects men and women of color when compared with the non-hispanic white population. Incidence rates are 20% higher for black populations, and mortality rates are 40% higher for black communities.

Diagnosis & Mortality by Race

Research suggests these differences largely reflect differences in socioeconomic status and education levels. This largely stems from the prevalence of risk factors in these communities (smoking, obesity, etc.) and the lack of screenings.

Colorectal Cancer Rates for Combined Sexes

We're not going to fix socioeconomic disparities with an app.

Solving the root causes of socioeconomic disparities via a summer internship and iOS application is unlikely. This presented a problem — if our goal is to find an equitable solution to a health disparity facing our nation, do we move forward with our research, or go back to the drawing board to find another problem. To be entirely honest, we were short for time at this point, so we chose to move forward and research why people from these communities are less likely to get colorectal cancer screenings. We learned the following.

Screening Obstacles

Lack of transportation to screening centers

Cost of colonoscopy

Overall, stigmas surrounding a screening

Screening Stigmas

The test is difficult, painful, or embarrassing

Screenings are only necessary if you see signs or symptoms

Screenings are expensive & time consuming

A lack of family history makes screenings unnecessary.

Wrapping our heads around the data

This is a lot of data, and a very complex problem. To brainstorm solutions, we decided to use a good, 'ol-fashioned whiteboard so we could get ideas and thoughts out of our minds. Here's a picture of our brain map, cleaned up a little bit for readability:

Plan

We devised a plan that we think helps meet our goal while using Aetna's existing resources, therefore helping Aetna as a whole. It consists of 2 parts.

(1) Increasing Testing Availability

Our goal is to be equitable for those who would not normally have access to testing. By utilizing resources such as take-home tests or Aetna'a Cora mobile clinic, we can increase testing while tackling the major problems of transportation and cost.

(2) Spreading Awareness

Many of the stigmas surrounding colorectal cancer screenings stem from misinformation being passed by word of mouth. By utilizing the Aetna Health application and a targeted ad campaign, we can increase awareness for the types of screenings available while displaying the importance of being screened.

Personas

we created a persona that can accurately represent our user’s pain points.

Utilizing Aetna's design system to create a user flow

I was tasked with creating a user flow to increase awareness through the Aetna Health application. Luckily, the design team had already solidified a user flow they called 'Next Best Action', or NBA.

NBA flows are designed to inform users of actions they can take to improve their health. It generally starts with a notification that opens a pop-up in the app. This pop-up shares general information with the option of viewing more, or completing a designated action.

Creating Multiple Flows

To align with our two goals, we wanted two flows. Each requires a user to be 50+ years old with no record of colorectal cancer screenings in the previous 7 years, or a relative who fits that criteria.

If the Cora truck has a planned stop within 10 miles of this individual, they'll be notified with information related to the mobile clinic.

Otherwise, the user will receive information and statistics regarding the importance of screenings.

Cora Truck is Near Notification

Goals

  • Display time, date, and location of Cora stop

  • Emphasize importance of screening

  • Intrigue user to learn more

Notification design:

Next Step:

Display an article that tackles stigmas and persuades the user to schedule an appointment with their medical center

General Information Notification

Goals:

  • Display numerous options for screenings

  • Emphasize importance of screening

  • Intrigue user to learn more

Notification design:

Next Step:

Display a pop-up with a map and further information and ability to add the event to a calendar

Completing the User Flow

The pop-up has much more flexibility than the notification for actually designing a user interface. Based on the Aetna Health design standards, these pop-ups have a large image covering the top portion of the screen, followed by a few bullet points and a large call-to-action. I followed this design because it helps the team meet our goals - the large visual is appealing and makes it easy to display information in a quick, easily-readable way.

For either user flow, the article was out of my hands. The copy team is in charge of producing this information, so I simply designed the user interface for each of them. The information is expected to be short and succinct with more resources available. I still wanted users to have a quick call-to-action, so the information and resources are split between two different containers.