MediConnect: Healthcare App UI Design
MediConnect connects patients and clinicians for remote consults. I designed the patient mobile experience and the clinic-facing web portal so booking, the visit, and follow-up feel like one product — not three tools taped together.
- Client
- MediConnect
- Role
- Product designer (web + mobile)
- Duration
- 8 weeks
- Platforms
- iOS · Android · Web
Time to book a visit
−48%
Booking task success
91%
MediConnect
Book. Join. Follow up.
−48%
Time to book a visit
91%
Booking task success
−56%
Missed join-link tickets
01 — The problem
What was broken
Patients landed on a directory that looked like a spreadsheet: names, credentials, and a “book” button that opened a calendar from 2014. They could not tell specialty, language, or whether the doctor was available today. Many booked the wrong person or gave up.
Clinics ran a separate web tool for schedules and another for messages. After the call, instructions went to email. No-shows were high because reminders were generic and the join link was hard to find ten minutes before the slot.
02 — Research
What I learned
Trust is the first conversion
Patients book people. Photo, specialty, languages, next available slot, and a short bio have to be on one profile — not split across tabs.
Booking should be two decisions
Pick a time, confirm reason and payment or insurance. Extra medical-history fields belong after the slot is held, or in a pre-visit form.
The join path is part of UX
A beautiful booking flow still fails if “Join visit” is buried. The home screen on visit day should be the visit.
03 — Process
How the work happened
- 01
Clinic and patient interviews
Spoke with a medical director, two nurses, and seven patients who had missed a video visit. Mapped where they got lost: profile, slot pick, reminder, join.
- 02
One flow, two surfaces
Designed the patient app and the clinic portal against the same objects: doctor, slot, visit, message. Shared components so status language never drifted.
- 03
Design system
Accessible type, high-contrast states for appointment status, and forms that work with autofill. Healthcare UI cannot hide errors in red-only cues.
- 04
Visit-day prototype
Tested reminders, the join button, and the waiting room. Moved the join CTA to the home card two hours before the slot.
04 — Solution
What shipped
Doctor profiles that can carry a booking
One-tap profiles: photo, specialty, languages, next slot, and a clear book action. No “view more” before the patient knows who they are meeting.
Booking in two steps
Choose a time, then confirm. Intake questions that are not required to hold the slot move to a pre-visit checklist.
Visit and messages in one thread
Secure messaging sits on the same visit object as the video room and the after-visit summary. Patients do not hunt email for the join link or the prescription note.
Scope delivered
- Trust-first doctor profiles with next-available slot
- Two-step booking with delayed intake
- Visit-day home card with a persistent Join action
- Secure messaging attached to the visit, not a separate inbox
- Shared design system for patient app and clinic web portal
05 — Outcome
The result
Booking task success rose in usability tests, time from open to confirmed slot fell sharply, and visit-day “can’t find join” support tickets dropped once the home card carried the CTA.
−48%
Time to book a visit
91%
Booking task success
−56%
Missed join-link tickets