CV Hanna McFadyen Get in touch
Three phones showing the AlbaHealth app concept: a home screen with services, a doctor's profile with a Make Appointment button, and a list of medical records.

AlbaHealth: Designing a Healthcare App for Clarity and Reassurance

Overview

Healthcare app concept · UX/UI designer in a team of five · 12 weeks, 2025

We set out to fix waiting times. We ended up designing for clarity.

A concept app for a new private healthcare provider: one place to book care, see a doctor remotely and understand your own health.

Research was shared across the team. My focus was user journeys, UI design, the design system and prototyping.

Concept project. AlbaHealth is not a real healthcare provider.

The Problem

We thought the problem was waiting times. It wasn't.

  • What we assumed

    The biggest frustration was speed: long waits and slow booking. A faster booking app looked like the answer.

  • What we heard

    People didn't just feel frustrated. They felt overlooked and uncertain. Delays weren't the only issue: a lack of clarity and reassurance was.

"It's the struggle to try to get an appointment… once you have one and you go, I really never have any issue."

So we stopped designing for speed alone, and designed for clarity and trust.

The app in use

Booking, start to finish.

Pick a date, choose a doctor, confirm. No phone queue at 8am.

Research

We started with interviews, because healthcare is emotional, not just usable.

A survey could tell us how often booking went wrong, but not how it felt. So after each of us researched one area of healthcare (mine was women's health and femtech), we spoke to people directly.

  • Discover 6 interviews

    12 questions on booking, care and managing health.

  • Define Thematic analysis

    Turned into personas and ranked requirements.

  • Structure Card sort

    6 people showed us what belonged where.

  • Review Expert evaluation

    A review of the final prototype.

What We Heard

People wanted clarity and reassurance, not just faster healthcare.

Four themes came up again and again in the interviews, in people's own words.

  • Memoji of an older woman with grey hair, shrugging

    "…basically giving you a few leaflets and then kind of sending you away with that."

    01

    Medical information was hard to understand

    Medical information and results weren't always explained in a way people could follow, so they were left unsure what it meant for them.

  • Memoji of a woman in a hijab, raising her hand

    "It kind of just makes you feel like… you don't matter a little bit."

    02

    People wanted to feel heard and prioritised

    Chasing call-backs and results, and repeating themselves to different people, left patients feeling like an afterthought in their own care.

  • Memoji of an older man, thinking with his hand on his chin

    "They sort of didn't reply to me for a long time, so I didn't know what was happening."

    03

    Next steps weren't clear

    After booking or an appointment, people often didn't know what would happen next, or when they'd hear back.

  • Memoji of a young man, facepalming

    "I've seen myself phone up to 80 times to be able to get through."

    04

    Getting an appointment was hard work

    Phoning at 8am, again and again, often to hear there were no appointments left, and taking time out of work to do it.

Priorities

We cut the doctor's side to do the patient side properly.

A real healthcare system needs separate portals for patients, GPs and clinic staff, each seeing different information. We'd planned to design both sides, but the doctor's side needed its own interviews, requirements and wireframes. In 12 weeks, that would have stretched everything thin.

So we designed for patients. Within the brief (unified services, remote access, patient education, wider reach and trust), we focused on the moments where uncertainty was highest:

  • 01 Booking an appointment
  • 02 Understanding results
  • 03 Seeing a doctor remotely
  • 04 Tracking the care journey

Iterations

Paper, lo-fi, mid-weight, then final.

We sketched over 100 paper screens to flesh out the flows, then built lo-fi wireframes. Each of us designed our own take on the key tasks. Side by side, it was clear which ideas worked: we kept those, dropped the rest, and refined them through two more rounds before the final design.

Eight hand-drawn paper wireframes of the prescription flow: my prescriptions, a repeat order question, and a four-step new prescription request ending in a submitted message.
Paper. Over 100 screens sketched to flesh out the flows, like this prescription request.
Lo-fi blue wireframes: the eight-step booking flow, and four versions of the home screen.
Lo-fi, version 1. The booking flow, and four takes on the home screen, from a list of buttons to a grid.
Version 1.5 wireframes of the Health section: test results, medical history, symptom tracking, prescriptions and a contact screen.
Version 1.5. The Health section reworked: results, history, prescriptions and contact.
Mid-weight prototype screens: a calendar showing prescriptions and appointments, an upcoming list, day overviews and an Aspirin detail screen.
Version 2, mid-weight. The calendar, upcoming appointments and prescriptions, closer to the final look.

The card sort sharpened each section. It showed us what people expected to find in each part of the app, and we built the structure around it: four sections, each holding the tasks people expected to find there.

Card sort results: how many of 6 participants placed each task in each section.
TaskCommunicationsCalendarHealth OverviewProfile
Check Upcoming Appointments0 of 6 in Communications6 of 6 in Calendar0 of 6 in Health Overview0 of 6 in Profile
Book Appointment0 of 6 in Communications5 of 6 in Calendar0 of 6 in Health Overview1 of 6 in Profile
View Calendar0 of 6 in Communications4 of 6 in Calendar0 of 6 in Health Overview2 of 6 in Profile
Contact Customer Services5 of 6 in Communications1 of 6 in Calendar0 of 6 in Health Overview0 of 6 in Profile
View Previous Chats5 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview1 of 6 in Profile
Report Error4 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview1 of 6 in Profile
Misc Help4 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview1 of 6 in Profile
Go to Video Call Portal4 of 6 in Communications2 of 6 in Calendar0 of 6 in Health Overview0 of 6 in Profile
NHS 24 Hour Portal4 of 6 in Communications0 of 6 in Calendar2 of 6 in Health Overview0 of 6 in Profile
Contact GP3 of 6 in Communications2 of 6 in Calendar1 of 6 in Health Overview0 of 6 in Profile
Test Results0 of 6 in Communications0 of 6 in Calendar5 of 6 in Health Overview1 of 6 in Profile
Request Prescription1 of 6 in Communications0 of 6 in Calendar5 of 6 in Health Overview0 of 6 in Profile
Prescription0 of 6 in Communications0 of 6 in Calendar5 of 6 in Health Overview1 of 6 in Profile
Record Symptom0 of 6 in Communications1 of 6 in Calendar4 of 6 in Health Overview0 of 6 in Profile
View Medical History0 of 6 in Communications0 of 6 in Calendar4 of 6 in Health Overview2 of 6 in Profile
View Account Details0 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview6 of 6 in Profile
Change Payment Details0 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview6 of 6 in Profile
Privacy and Security1 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview5 of 6 in Profile
Change Contact Details1 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview5 of 6 in Profile
Notification Settings1 of 6 in Communications0 of 6 in Calendar0 of 6 in Health Overview5 of 6 in Profile
Search for Information2 of 6 in Communications0 of 6 in Calendar1 of 6 in Health Overview3 of 6 in Profile

Darker means more of the 6 participants · outlined: most common choice

Suggested by participants: Prescription reminders A map of where the appointment is Feedback on a clinic

Card sort, 6 participants. Most tasks had a clear home. Contact GP and Search split people the most, so they needed the most thought.
Information architecture: from the dashboard, four sections. Profile: account details, notifications, privacy and security, help, FAQ. Health Overview: medical history, test results, prescriptions, symptom tracker. Calendar: book appointment, upcoming appointments, prescription review, search. Communications: NHS 24 and health portals, 24h emergency service, contact GP, previous chats, video call portal, contact clinic.
The final information architecture, shaped by the interviews and the card sort.

Colour had to mean something. Blue for the calm feel of a clinic. Green only for medication, so prescriptions never look like buttons or appointments.

Accessibility wasn't optional. We studied Apple's guidelines for familiar iPhone patterns, and the Scottish Government's design system, which treats accessibility as a requirement.

Weekly critique shaped the final screens. We commented directly on each other's designs every week, and worked through the comments before signing anything off.

Final Design

Simple, clear and in your control.

We simplified navigation and wording, and made the next step clear at the end of each journey.

01

A clear, all-in-one view of your care

Home and Health bring the main services together, each explained in one line of plain English.

Four services up front, each explained in one line of plain English.
Prescriptions in green, with the next order date and a clear prompt to reorder in time.

02

Book appointments around your schedule

Booking is split into short steps with a progress bar, so people always know how far along they are.

Choose how and when: phone, video or in person, then a date and time.

Doctor card: Dr. Kavya, General Physician at Westmires Clinic, verified, 6 years experience, rated 4.9, with the price per consultation and a Book Now button.

Doctor cards show clinic, experience, rating and price at a glance, so people can compare before they book.

Know who you're seeing, with a short bio and the doctor's availability.
Clear next steps: everything confirmed in one place, with options to add it to your calendar or set a reminder.

03

Prescriptions, without the phone call

Repeat prescriptions take a few taps, and the app says what happens next.

Every medication in green, so it never gets confused with buttons or appointments.

Prescription card for Aspirin: ordered every 28 days, taken between 9 and 9:30am, a note to place the next order within 10 days, and an auto re-order switch.

Reorder reminders show when each prescription is due, with the option to reorder automatically.

Quick add reorders past medication in one tap.

Review card: request date, name, date of birth, and 4 medications requested, with a note that one needs GP review and you will be contacted with next steps.

No surprises: a final check before ordering, and a plain note when a medication needs GP review.

04

Your medical history, all in one place

Results and records are easy to find, and say what they are in plain words.

Results are ready: a clear message, with a summary of the appointment.
The full picture: where, when and who, with a report to download.
Everything in order: past records by date, searchable, as a list or grid.

05

Connect with your GP, without the wait

Patients can reach their practice on their own time, instead of phoning first thing in the morning.

Your practice in one tab: book, find GP details or request a prescription, with the clinic on a map.

Mailbox tab: Letters, Upcoming Appointments and Chat, each with a short description.

One mailbox for letters, appointment updates and chat with your practice.

06

UI kit

The building blocks behind every screen, from the app's own design system.

Typography

League Spartan

Headings · Bold and Semi Bold

Roboto

Body text · Light, Regular and Medium

Colour

  • BlueBrand, buttons, calendar#2B7FFF
  • Dark blueText and borders#193CB8
  • GreenMedication only#00D492
  • Dark greenBorders and text#007A55

Buttons

Primary button: Continue, in AlbaHealth blue.Appointment type buttons: Phone, Video (selected) and In-person.

Navigation

Bottom navigation bar: Home, Calendar (selected), Health and Contact.Search bar with a blue search button.

Calendar

Calendar for December, weekdays in dark blue and weekends in light blue, with past days faded.

Time

Morning and afternoon time slots, with 7:30am selected and unavailable times faded.

Payment

Saved cards: Mastercard, Visa, Google Pay and Apple Pay, each with a radio button, and Add New Card.

Medication

Daily medication tracker: Monday to Wednesday ticked in green, the rest of the week empty.Pharmacy card: Boots, Gyle, Edinburgh, with a View Map button.

Elements

Home banner: Consult a doctor, book today, with 25,000+ happy patients.Service tiles: Medications, Test Results, Symptoms and Medical History, each with an icon and one line of description.Medical record row: Check up (GP), Oct 2025, with a Details button.

Words mattered as much as screens. We avoided medical jargon and wrote in plain, approachable language. In a company this might be a dedicated team's job; here, it was our call.

It works on tablet too. We adapted the phone designs for tablet. There are fewer tablet screens than phone ones, but we took them as far as time allowed.

Tablet

The same app, scaled up for iPad.

Built on the same 4 × 6 grid and components, so every screen could adapt.

Tablet medical records screen: past records listed on the left, and the selected dental surgery on the right with its date, time, location, hospital, surgeon, and expandable doctor's notes, treatments and recovery time.

Next Steps

Next, we'd test it with patients.

We ran out of time for usability testing. It's the first thing I'd do, to find out:

  • 01 · Information Could they find what they needed?

    Did each screen have what people were looking for?

  • 02 · Ease Was it simple to use?

    Were booking and the other journeys easy to follow?

  • 03 · Gaps What's missing?

    Where did people get stuck, and what would they add?

We'd also test with a wider range of ages, and develop messaging and symptom tracking further.

Reflection

What I took from it.

Talk to people before you define the problem. Our first assumption was wrong. The interviews turned a speed problem into a clarity problem.

Cutting scope is a design decision. Dropping the doctor's side gave the patient journeys the time they needed.

In healthcare, clarity builds trust. Not everyone is confident with technology. Plain language and obvious next steps help people manage their care on their own.

Test earlier. Without usability testing, we couldn't prove the designs worked. Next time, I'd put a rough prototype in front of users much sooner.

Thanks for reading

Hanna