Platform Overview¶

Vision¶

Curaway -- "Care All The Way" -- is an AI-powered cross-border medical travel coordination platform that connects patients in the US, UK, and UAE with high-quality, accredited healthcare providers in India, Turkey, Thailand, and Spain. The platform combines clinical AI understanding, graph-based provider matching, and explainable reasoning to guide patients through every step of their medical travel journey.

The founding insight is simple: millions of patients face long wait times, unaffordable procedures, or limited access to specialists in their home countries. Meanwhile, world-class providers abroad offer the same (or better) outcomes at a fraction of the cost. Curaway bridges this gap with an AI-first approach that makes cross-border care safe, transparent, and accessible.

POC Flow¶

The proof-of-concept demonstrates the core patient journey in five steps:

graph LR
    A[Upload Medical Report] --> B[AI Clinical Understanding]
    B --> C[FHIR Record Generation]
    C --> D[Provider Matching]
    D --> E[Explainable Reasoning]

    style A fill:#008B8B,color:#fff
    style B fill:#008B8B,color:#fff
    style C fill:#008B8B,color:#fff
    style D fill:#FF7F50,color:#fff
    style E fill:#FF7F50,color:#fff

Technology Stack¶

Backend Services¶

Frontend¶

AI / ML Models¶

Key Constraints¶

The Curaway POC operates under a unique set of constraints that shape every architectural decision:

Eight Non-Negotiable Rules¶

These rules govern every line of code, every design decision, and every architectural choice in Curaway. They were established at the start of the project and are enforced through code review, automated checks, and documentation.

1. Configurability First¶

Every behavioral parameter must be configurable at runtime without code deployment. This includes matching weights, model selection, prompt templates, feature toggles, and UI copy.

# Example: Matching weights are never hardcoded
weights = await get_config("matching.strategy.weights", tenant_id=tenant_id)

2. Feature Flags Everywhere (Flagsmith)¶

Every new capability ships behind a Flagsmith feature flag. Flags control:

• Agent behavior (agent_enhanced_matching, agent_explanations_enabled)
• UI features (show_doctor_cards, enable_chat_v2)
• Infrastructure (use_qstash_callbacks, enable_r2_uploads)
• Matching strategies (matching_strategy_version)

if await flagsmith.get_flag("agent_enhanced_matching", tenant_id):
    result = await agent_matching_strategy.match(case)
else:
    result = await weighted_rules_strategy.match(case)

3. Multi-Tenancy (tenant_id Everywhere)¶

Every database table includes a tenant_id column. Every API request carries an X-Tenant-ID header. Every query filters by tenant. No exceptions.

-- Every query includes tenant_id
SELECT * FROM patients WHERE tenant_id = $1 AND id = $2;

4. Production-Evolvable POC¶

The POC is not a throwaway prototype. Every component is built to evolve into production with scaling, not rewriting. Database schemas include all production columns (even if unused in POC). API contracts follow REST best practices. Error handling is comprehensive.

5. Neo4j from Day 1¶

The provider-condition-procedure relationship graph is stored in Neo4j, not modeled as relational joins. This enables:

• Multi-hop traversals (Patient → Condition → Procedure → Provider → Doctor)
• Relationship-rich queries with metadata on edges
• Visual debugging of the provider network
• Future expansion to treatment pathways and outcome correlations

6. Branded UI (Teal and Coral)¶

Every user-facing element follows the Curaway brand guidelines:

7. Modular Monolith (Microservices-Ready)¶

The codebase is a single FastAPI application, but internally organized as independent modules with clear boundaries:

app/
  modules/
    clinical/      # Clinical context, FHIR, document processing
    matching/      # Provider matching, strategies, scoring
    intake/        # Patient intake, conversations
    providers/     # Provider management, doctor profiles
    agents/        # LangGraph agents, MCP server
    notifications/ # Email, SMS, push
    analytics/     # Events, PostHog integration

Each module can be extracted into a standalone service when scale demands it.

8. Step-by-Step Guidance¶

Claude Code (the AI development assistant) must explain every decision, present trade-offs before implementation, and guide SD through the reasoning. No black-box changes. Every commit message explains the "why."

Brand Identity¶

Curaway = "Care All The Way"

The name captures the platform's promise: continuous care coordination from the moment a patient considers medical travel through post-procedure follow-up. The brand combines clinical authority (teal) with human warmth (coral).

 ██████╗██╗   ██╗██████╗  █████╗ ██╗    ██╗ █████╗ ██╗   ██╗
██╔════╝██║   ██║██╔══██╗██╔══██╗██║    ██║██╔══██╗╚██╗ ██╔╝
██║     ██║   ██║██████╔╝███████║██║ █╗ ██║███████║ ╚████╔╝
██║     ██║   ██║██╔══██╗██╔══██║██║███╗██║██╔══██║  ╚██╔╝
╚██████╗╚██████╔╝██║  ██║██║  ██║╚███╔███╔╝██║  ██║   ██║
 ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚═╝  ╚═╝ ╚══╝╚══╝ ╚═╝  ╚═╝   ╚═╝
                     Care All The Way

Team¶

Architecture Principles Summary¶

graph TD
    A[Configurability First] --> B[Production-Evolvable POC]
    C[Feature Flags Everywhere] --> B
    D[Multi-Tenancy] --> B
    E[Neo4j from Day 1] --> B
    F[Modular Monolith] --> B
    G[Branded UI] --> H[Patient Trust]
    B --> I[Curaway Platform]
    H --> I

    style A fill:#008B8B,color:#fff
    style C fill:#008B8B,color:#fff
    style D fill:#008B8B,color:#fff
    style E fill:#008B8B,color:#fff
    style F fill:#008B8B,color:#fff
    style G fill:#FF7F50,color:#fff
    style H fill:#FF7F50,color:#fff
    style I fill:#1A1A2E,color:#fff

What's Next¶