Kamita Williams
Back to Selected WorkPediatric Patient Portal‹ 2 / 2
Pediatric patient portal · Launched

Choosing what to design first.

Preparing for a visit and finding a child’s test result are two reasons a family might open a portal. I worked with a children’s hospital to decide which needs the portal should support and where design should begin.

01 / The Problem

Which features did families need, and in what order should we design them?

I reviewed enhancement requests and worked with a children’s hospital client to identify the tasks patients and families needed to reach from home. Together we used those requests to define the scope of the portal. I worked with several teams to turn the hospital’s priorities into a portal families could use, shaping how they find upcoming visits and navigate their child’s health records.

02 / The Insight

Some tasks depend on others.

A caregiver who manages care for two children needs to know whose information is on screen. That question matters whether they are checking a visit time or opening a result. It gives us a reason to consider record selection alongside each feature that uses it.

03 / The Design

Turn family needs into features.

Preparing for a visit called for an appointment summary with the time, clinic, and instructions together. Retrieving an immunization record called for a clearly labeled route into health records. Defining each task in those terms gave us something concrete to review in the designs.

From priorities to screens

I defined the feature sequence and guided navigation, content, and notifications. My UX design partner created the original screens. I reviewed the designs with them and gave feedback on how well each iteration reflected the hospital’s priorities.

04 / The Result

What we heard after launch

The portal launched, and both patients and client stakeholders gave positive feedback on how easy it was to navigate. That feedback tells us about the experience families used. It leaves open which feature was most valuable to them.

The design tradeoff

An appointment summary serves a specific need before a visit. A record selector supports several tasks across the portal. Setting design priorities meant weighing an immediate family need against work that other features depend on.

How we made the decision

The hospital helped identify the tasks families needed most. I set the feature priorities and reviewed the screens with my UX partner, who created the original designs.

What I’d carry forward

For another portal, I’d ask caregivers which tasks they most need to do from home and what they do today when those tasks are hard. I’d use their answers alongside feature dependencies to decide what to design first.

05 / Design examples

Inside the patient portal

Explore four caregiver tasks in the Children’s Mercy app previews. Select a screenshot for a closer look.