← All work
Healthcare Multi-panel platform Design system

Medio

A four-panel healthcare system — patient, physician, medical centre, backoffice — designed coherently enough for a fully outsourced dev team to build without logical gaps.

In staging · launch expected 2027
mediostaging.com
Medio physician dashboard in dark theme — today's appointments across medical centres, and the next patient's history, reason for consultation and GP referral
Medio physician app on mobile — today's appointments, with Finalize Prescription on the one that just ended
[ medio · physician panel ] desktop & mobile · light & dark themes
// context & role

A platform managing the full care system — booking, appointments, prescriptions, shift and staff management, fee management — up to government-level coordination.

Four panels serve four very different user types: Patient (mobile-leaning), Physician (desktop web), Medical Centre, and Backoffice. Medio has two designers. I owned the physician and medical-centre panels end to end and designed the patient side's key journeys, from booking to major redesigns.

Patient
Mobile-leaning
Physician
Desktop web
Medical Centre
Operations
Backoffice
Admin
Company
Medio by Circle One
Role
Product Designer, one of two
Period
Feb 2025 – present · part-time for the first weeks, during the SternX handover
// problem

Undefined problems, an outsourced team, and no room for logical gaps.

Most flows started as unknown, undefined problems. Development was outsourced, so any logical inconsistency in the design would surface as a broken product. And the system had to feel uniform across four very different user types.

// approach

Turn ambiguity into flows an outsourced team can't misread.

01
Designed flows from scratch

Simplified user setup, appointment management, prescription writing and reading, and meetings / consultations.

02
Made every flow logically airtight

The core contribution: complete, uniform flows across all panels, designed defensively so an outsourced dev team could build them without gaps.

03
Architected the design system

A DS Core foundation with 360+ semantic color tokens in full light/dark modes, per-panel component libraries, dedicated handoff files per panel, and a custom Health Icon set.

04
Added AI features for healthcare pain points

Targeted at real healthcare pain points and informed by customer needs, market research, and R&D.

// key work

Flows that cross panels, and the workspace they land in.

→ consultation reason

Physicians write their own pre-consultation questionnaire: steps of typed questions, from yes/no to file upload, or a template to start from. Patients answer it while they book, one step at a time, and can skip it. The answers are waiting on the appointment before it starts, beside the patient's history and their GP's referral.

Medio physician settings — the reason-for-consultation builder, with steps of typed questions
01 · physicianscroll ↓Builds the questionnaire in steps, each question typed — scale, date, dropdown, file upload — or starts from a template.
Medio patient app — answering the reason-for-consultation questions while booking, step 2 of 6
02 · patientscroll ↓Answers it while booking, a step at a time, with the option to skip.
Medio patient app — consultation booked, with the note, clinic location, record sharing, co-attendant invite and GP referral
03 · patientscroll ↓Once booked, the note stays editable, and records can be shared in full, in part, or later.
Medio physician panel — appointment detail with patient history, saved notes, reason-for-consultation answers and GP referral
04 · physicianThe answers arrive on the appointment, with the patient's past sessions, saved notes, and the GP's referral.
→ shifts & fees

A physician can work at several medical centres, so hours and fees are set per centre: one weekly grid with a column for each, and a fee for every centre and consultation type. The centre manages the same schedule from its side — each doctor's working hours, and an inbox of fee, shift and exception requests, approved or rejected, with who raised and who reviewed each one on record.

Medio physician panel — editing shifts across three medical centres in one weekly grid, with weekly hours per centre
01 · physicianEvery centre in one grid: shifts by day, the consultation types each shift takes, and weekly hours per centre.
Medio physician app on mobile — consultation fees per medical centre for video, audio and in-person visits
02 · physicianscroll ↓A fee per centre and per type — video, audio, in person.
Medio medical centre panel — a doctor's working hours, with a new shift edit request to review
03 · medical centreA doctor's working hours from the centre's side, with a pending edit request flagged on top.
Medio medical centre panel — received requests, filterable by approved, rejected and pending
04 · medical centreFee, shift and exception requests — pending, approved or rejected, with who created and who reviewed each.
→ the physician's day

Calendar, chats and the day's dashboard, on desktop and mobile, in light and dark. Each one filters by medical centre, because one physician's day can span several, and the three consultation types — in person, video, audio — carry the same icons on every panel.

Medio physician calendar — month view across all medical centres
calendarMonth view across every centre, narrowed to one from the filter, with the current shift named under the dates.
Medio chats and follow-ups in dark theme — unread filter, medical centre filter, and a link to each patient's detail
chats & follow-upsUnread-only at a toggle, and every patient's last visit one tap from their record.
Medio physician dashboard in dark theme — recent notifications and patient follow-ups, each with its next action
dashboardFurther down the dashboard: notifications that carry their next action, and follow-ups waiting on a reply.
// status
In staging, launch expected 2027

Market launch is expected in 2027. Outcomes are launch-pending — this case study will be revisited with numbers once Medio is live.

360+
semantic color tokens, light + dark
4
panels, each with its own component library
1
custom Health Icon set
// next project
Agrino
An agriculture super-app, backed by Keshavarzi Bank.
View case →