Product & Design System
Medoc
A telehealth platform across web, mobile, and vital-sign hardware that reached eight hospitals in Turkey and Iraq.
Overview
Distance should not decide whether someone can see a doctor
Medoc was a B2B telehealth product created for MedReach Global, also referred to as GAT. It served hospitals in Turkey and Iraq, combining remote appointments with vital-sign data from connected medical hardware.
I worked on Medoc as a Product Designer at The D Agency. Our Design Lead led the design work, and I worked beside him across product UX, UI, the shared design system, and more than 100 web and mobile screens. Our agency owned the design while partner agencies handled development.
Clinical input came from a medical school in Istanbul. Doctor verification was reviewed with MedReach Global. Medoc later reached eight hospitals across Turkey and Iraq.
8
Hospitals reached
Turkey and Iraq
100+
Web and mobile screens
Designed across the product
2
Countries
Turkey and Iraq
Problem
A video call could only solve part of the access problem
Medoc aimed to make medical care easier to reach and afford in developing markets. Patients and doctors could be in different time zones, some conditions still required a physical examination, and the product needed trusted doctor verification.
The service had to connect appointments, consultations, reports, messages, follow-up, and vital-sign data without forcing patients to piece the process together themselves.
Research
About 30 target users defined what remote care had to cover
The team ran an online survey with about 30 target users. The main needs were direct access to affordable care, less COVID exposure from hospital visits, and regular follow-up after a consultation.
The research pushed the product beyond appointment booking. People needed a clear service before, during, and after a consultation, with enough trust to share health information and speak with a verified doctor.
Ideation
The product had to connect the full care flow
We kept time zones visible from booking through the upcoming appointment view, so patients and doctors could see the schedule in their local time.
For consultations that needed physical readings, connected hardware measured vital signs and passed them into Medoc beside the patient record. A medical school in Istanbul contributed to this part of the product.
Partner agencies built the product, so I helped turn the web and mobile work into reusable components, clear states, and shared rules. This gave the development teams one consistent source across more than 100 screens.
Designs
More than 100 screens turned the service into one working system
My lead and I designed the web and mobile products as one connected service. I worked across the interface and built the design system that kept the growing screen set consistent.
The clinician workspace brought appointments, patients, reports, messages, account controls, and vital-sign data into one place. The mobile product gave patients access to appointments, follow-up, and their health information outside the hospital.
Doctor verification requirements were reviewed by my lead and MedReach Global, then carried into the product states and flows. Clinical contributors in Istanbul helped shape how vital-sign data entered the system and appeared beside the rest of the patient record.
Lessons
The system mattered as much as any single screen
Medoc covered more than 100 web and mobile screens, which forced the design system to carry real production work. Components, states, type rules, and spacing stayed consistent across the whole product.
The external delivery model raised the bar for handoff. Our files gave partner agencies enough detail to build the product with limited design support.
The vital-sign integration showed how much medical products depend on close work between design, the client, and clinical contributors. Medoc later reached eight hospitals in Turkey and Iraq.
