GCL Global Patient Hub
A patient-acquisition platform that connects Korean hospitals, treatment packages, language support, pricing, consultation intake, and partner/provider case operations.
Overview
GCL puts the public patient site and the coordinators' internal CRM into one product. When enquiries arrive in one place and get handled in another, somebody ends up retyping them.
I never wanted to build a hospital directory. Patients, partner operators, and provider staff each needed to pick up the same case under different scopes. The consultation form collects nationality, country of residence, language, budget, travel window, partner-support requests, and consent flags, then hands off through the Supabase lead flow.
What I spent the most time on was the boundary between what is public and what is not. Beta metrics, Supabase state, and medical document handling are gone from the public homepage, and the admin, partner, and provider quote desks sit behind a server-validated gate.
Core skills
Implementation
- 1Separated hospital, treatment, comparison, consultation, and landing routes in React + Vite, then connected EN/JP skin-package wedges to consultation prefill.
- 2Designed lead storage as Supabase v1 first, legacy inquiries fallback second, and local demo fallback last.
- 3Placed admin, partner, and provider quote desks behind a server-validated gate and recorded case activity events.
Strengths
- Separates the public patient site from internal operations while keeping marketing, intake, assignment, and quote flows on one model.
- Implements the operating slice from partner assistance request to provider shortlist, quote request, provider response, and commission check.
- Keeps medical data and beta operations metrics out of the public homepage through explicit content boundaries.
Metrics
Tech stack
Screenshots
