MedGlobal360
A medical tourism app connecting international patients with accredited hospitals and doctors in India, with an assigned care coordinator, end-to-end journey tracking, and a Care Circle that lets family back home follow along.
Role
Product Designer
Timeline
7 weeks
Team
3 Engineers, 1 PM, 1 Data Scientist, 1 Product Designer
Platform
App
Link
App
Overview
MedGlobal360 is a medical tourism app that helps people travel to India for serious treatment, the transplants and major procedures they can't get affordably or quickly at home, and guides them through every step. A patient says what treatment they need and when they want to travel, a care coordinator is assigned to match them with the right hospital and doctor, and the app carries the whole journey from that first plan through travel, surgery, recovery, and the trip home. I designed it end to end as a freelance UI/UX designer, and added a Care Circle so the family a patient leaves behind can follow the journey too.
The Challenge
Traveling to another country for major surgery is one of the most stressful things a person can do. You're placing your health in the hands of a hospital you've never seen, in a country you may never have visited, often for something as serious as a transplant. On top of the fear sits the logistics, choosing a doctor, understanding the cost, arranging a visa, booking flights and a place to stay, keeping documents in order. Normally all of that lives across email threads, phone calls, and agencies, opaque and scattered. The app had to make a frightening, complicated process feel trustworthy and handled, for someone making the biggest health decision of their life from thousands of miles away.
Research & Insight
This was a freelance engagement, so it started with the client, understanding their business and what a patient actually goes through. I ran it as two named exercises: Jobs-to-be-Done, to find the real job, and a Value Proposition Canvas, to map the patient's and the family's pains and gains against what the product could relieve.
The job (JTBD). I ran interviews framed around the struggle, not the features, and the job wasn't what you'd assume. Nobody's real job is "find a hospital abroad." It's closer to make the biggest health decision of my life, far from home, without drowning in fear. Once you hear it that way, the whole product shifts from a catalog to a source of reassurance.
The canvas (jobs, pains, gains). The company's model is matchmaking with a human touch: a patient shares their need, a care coordinator connects them to the right hospital and doctor and stays with them. Mapping the customer side, a few things stood out.
Trust is the entire product. Nobody crosses the world for surgery on a whim. Accreditation, real reviews, verified doctors, and honest pricing aren't features here, they're the reason someone taps "book."
It's a journey, not a booking. The value isn't finding a doctor, it's being carried from first consultation to discharge, so the app had to be built around a timeline, not a catalog.
The coordinator is the hero, and the app is their extension. A real person carries the decisions and the reassurance, so the design had to support that relationship, not replace it.
The patient isn't the only one who's scared. The biggest pain that surfaced wasn't even the patient's, it was the family back home, terrified and out of the loop. This became the seed of Care Circle.
On the value side, each pain earned a reliever: proof-first browsing for "can I even trust this?", a human coordinator for "who do I talk to?", and Care Circle, permission-based access for up to three family members, as the gain creator for that family pain. That value side is what Product Strategy is built from.
Assumptions versus validated findings. Everything on the canvas started as an assumption, tagged with its source, until evidence promoted it. To me a finding is something at least two independent sources or a real behaviour confirmed, a confident stakeholder opinion is still an assumption. So "trust is the whole product" started as the client's belief, and became a finding only when it kept surfacing on its own across patient conversations. Care Circle started as my hypothesis, and moved toward validated when the client confirmed the out-of-the-loop pain was real and recurring, and stakeholders kept singling it out. I was honest about the limits too: it was a lean freelance project, so I couldn't validate everything, so I kept the riskiest assumptions flagged and would test them with usability sessions and a small patient cohort before betting the roadmap. The framework's value isn't a full canvas, it's being honest about which boxes you actually know and which you're still guessing.
Product Strategy
These are the relievers, the value side of the canvas, each one answering a pain the research surfaced.
Lead with proof. Because trust is the product, JCI and NABH accreditation, ratings, review counts, years of experience, and starting prices sit on the surface of every doctor, hospital, and treatment, so trust is built into the browsing, not buried in the fine print.
Make cost and quality comparable. Treatments show transparent starting prices, durations, and hospital counts, and doctors and hospitals sit side by side with the same signals, so a patient can weigh options honestly.
Frame everything as one coordinated journey. Since it's a journey not a booking, onboarding sells the full arc, and a My Journey space ties travel, accommodation, appointments, and documents together, so the patient always knows where they are and what's next.
Keep a human at the center. Because the coordinator is the hero, a care coordinator, supported by an in-app assistant named Med, is the front door to help, so the patient always has someone, not just a screen.
Bring the family in with Care Circle. To answer the family's out-of-the-loop pain, I designed Care Circle, which lets a patient add up to three people who can log in and see the journey, the appointments, the progress, the reassurance, without the patient having to relay it. It was the client's stated requirement, and the solution I proposed was one the stakeholders singled out.
Experience Architecture
The structure turns the canvas into a flow, proof up front, one coordinated journey, the coordinator and the family always reachable.
Getting in: a branded splash, a three-part onboarding that names the three reasons to trust the app, Find Care, Compare, and Plan, then account creation or a guest path, with social and phone sign-in and a language switch for an international audience.
The home base: a personalized home with a treatment-plan call to action, quick answers to "Why MedGlobal360" and "Why India", and curated rows of popular treatments, top doctors, and top hospitals.
Discovery and booking: searchable, filterable lists of doctors and hospitals, each profile carrying accreditation, ratings, experience, and a bio, then a schedule-and-time picker to book an appointment.
The coordinator: a chat space with Med, the in-app care assistant, opening with the questions patients ask most, cost, the right specialist, documents, recovery length, and a search for doctors and specialties.
The journey and the circle: a My Journey timeline that holds travel, hotel, hospital and doctor visits, and documents in one place, a chat line to the coordinator, and Care Circle, where up to three family members can join to follow the whole thing from home. Bottom navigation ties it together: Home, Explore, My Journey, Chat, and Profile.
Interface System
The visual system serves the core finding, this is a scared person making a first-time decision, so it has to feel calm, credible, and clear.
A calm, clinical warmth. Soft blue gradients, white cards, and generous space give the app the steadiness of good healthcare, while warm photography of real doctors and patients keeps it human.
Trust as a visual language. Because trust is the product, accreditation badges, star ratings, review counts, and clear starting prices are treated as first-class interface, repeated consistently so a patient learns to read credibility at a glance.
A friendly, confident blue. A single approachable blue carries the primary actions, with the logo's spectrum of colors reserved for identity, so the interface stays calm while the brand stays alive.
Built for a global patient. A visible language switch, plain wording, and clear iconography acknowledge that the user may be reading in a second language while making a first-time decision.
One clear step at a time. Onboarding, booking, and the journey all break a big, intimidating process into single, legible steps, so nothing ever feels like more than the next thing to do.
Outcome
I designed MedGlobal360 end to end as a freelance UI/UX designer, from the client conversations through onboarding, discovery, booking, the coordinator chat, and the full journey experience, into one app that makes crossing the world for treatment feel guided instead of frightening.
The moment I'm proudest of is Care Circle. It started as a hypothesis on the canvas, the family back home is scared and out of the loop, and rather than bolt on a share button, I gave the patient a way to bring up to three loved ones into the app to follow every step. It earned its place when the client confirmed that pain was real and recurring, and it was the piece stakeholders singled out. It captures what the whole product is trying to be, not just a booking tool, but a way to make people going through something hard feel less alone.
I'm honest about the scope. This was a lean freelance project, so the riskiest assumptions are well-reasoned but not fully validated, a round of usability sessions with real patients is the next step. What the design settles is the harder question: how to make a frightening, scattered process feel trustworthy, coordinated, and handled from thousands of miles away.
