Product Documentation
This is the primary product reference for Global Clinic, a cross-border medical-tourism platform that gives international patients a single, trustworthy, end-to-end path to treatment in India, and gives accredited hospitals a reliable engine for the source markets they need.
It is written for business stakeholders, product managers, operations and care teams, partner clinics, and support staff. Engineers should read it too, then move on to the Developer Documentation for the technical implementation guide.
Status note. The patient-facing and clinic-facing surfaces are built as a Next.js / React / TypeScript reference implementation backed by mock data. Several operational surfaces (coordinator console, admin Country-Pack console, agent portal) and the compliance backbone are specified here but not yet built. Where that is the case, this documentation marks the feature as Planned so readers can tell shipped behaviour from target behaviour.
How this documentation is organised
| Section | What it covers | Primary audience |
|---|---|---|
| 1. Product Overview | Vision, objectives, scope, personas, value propositions, capabilities and limitations | Executives, PMs, partners |
| 2. Features and Requirements | Feature catalogue, functional and non-functional requirements, business rules, role-based access | PMs, QA, engineering, clinics |
| 3. Business Processes and Workflows | The operational processes and rules behind the journeys: clinic onboarding, payments and refunds, escalation | Operations, coordinators, clinics |
| 4. User Experience | Design language, navigation maps, screen-by-screen descriptions, decision trees, recovery paths | Product, design, support |
| 5. Legal, Compliance and Policy | Terms, privacy and consent, medical disclaimer, retention, HIPAA / GDPR / DPDP | Legal, compliance, leadership |
| 6. Edge Cases and Exception Handling | Every major exception scenario and the defined response | Operations, support, QA |
| 7. Contextual Help System | How in-product help, tooltips and FAQs are sourced and kept current | Product, support, content |
User journeys. The end-to-end per-persona journeys, organised by lifecycle phase (Discover, Plan, Treat, Return) and tagged Live or Planned, now live in their own User Journeys section.
Roadmap. The Implementation Plan turns the 31 requirement gaps (from the gap analysis and the official India MVT portal benchmark) into 8 delivery workstreams across 3 releases — adding the Wellness/AYUSH vertical, insurance/payer, internationalisation, government-portal-parity discovery and cost depth, immigration/FRRO, travel/guidance, and the operational consoles.
The product in one paragraph
A patient enquires, shares medical records, and receives a specialist opinion and a transparent itemised quote. They fund a milestone-based escrow that protects them until they arrive. The visa engine walks them through a corridor-specific document checklist, generates the hospital invitation, and tracks the application to grant. The Travel Desk arranges flights, an attendant-friendly stay, and airport pickup. A named care coordinator stays with them across the whole journey, which is modelled as 14 stages from Enquiry to Close-out, each with an accountable owner and a service-level target. After treatment, structured tele-follow-ups at 7, 30 and 90 days turn a one-time transaction into continuity of care, and the final escrow milestone releases on a clean, auditable trail.
Key product facts
- Positioning: a facilitator, not a medical provider. Global Clinic coordinates care; it does not practise medicine. This framing is enforced in product copy and contracts.
- Destination: India, across a vetted network of JCI / NABH-accredited hospitals.
- Corridors: Oman / Gulf, Kenya / Nigeria (Africa), Uzbekistan / CIS, and a high-value US / UK diaspora segment. Each corridor is configured by a Country Pack.
- Trust pillars: the visa engine, escrow-protected payments, a named human coordinator, and corridor-specific Country Packs.
- Surfaces: a public marketing site, a patient portal (
/portal/*), and a clinic console (/clinic/*).
See the glossary at the end of the overview for the domain terms used throughout.