Curaway Documentation¶
Curaway is an agentic AI-powered cross-border medical travel coordination platform. Patients from high-cost markets (US, UK, UAE) are matched with accredited providers in India, Turkey, Thailand, and Spain via a conversational intake, structured FHIR record construction, explainable provider matching, and an independent MSO (Medical Second Opinion) panel — all inside a single multi-tenant platform built to clinical-data standards.
MVP flow: Conversational intake → AI clinical extraction → FHIR R4 record → Provider + doctor match → Explainable reasoning → MSO second opinion → Confirmed travel plan
Where to start¶
-
:material-presentation:{ .lg .middle } Investor demo
End-to-end patient journey (4 min): intake → matched providers → MSO second opinion → confirmed travel. Product- and outcome-led.
-
:material-code-braces:{ .lg .middle } Technical deep dive
Engineering / due-diligence walkthrough: 5-layer intake model, document pipeline, Patient Fitness Score, multi-tenancy, and agent architecture.
For engineers¶
-
:material-sitemap:{ .lg .middle } Architecture
Platform overview, data model, agent system, matching engine, document pipeline, auth, and infrastructure — 20 sections.
-
:material-scale-balance:{ .lg .middle } Architecture Decision Records
26 ADRs — the "why" behind every major technical choice, from Railway PostgreSQL to the multi-tenancy model.
-
:material-code-json:{ .lg .middle } API Reference
Live Swagger docs, response envelope, error codes, and HTTP status mapping.
-
:material-flask-outline:{ .lg .middle } Specifications
Feature specs, AI steer docs, SDD-MVP, and implementation roadmaps.
For clinicians and operators¶
-
:material-wrench:{ .lg .middle } Runbook
Local dev setup, deployment, database operations, triage tuning, MSO video, GDPR erasure, and troubleshooting.
-
:material-microphone:{ .lg .middle } Voice rules
How Curaway speaks: no medical advice, no clinical directives, no jargon. The four enforcement layers explained.
-
:material-hospital-building:{ .lg .middle } MSO Teleconsultation
How independent specialist second opinions are scheduled, delivered, and attached to the patient record.
Platform at a Glance¶
| Metric | Value |
|---|---|
| PostgreSQL tables | 34+ |
| Providers seeded | 42 (8 countries) |
| Doctors seeded | 172 (mixed completeness) |
| Neo4j nodes | 172+ doctors + 42 providers + 30+ procedures |
| Neo4j relationships | 600+ |
| Qdrant vectors | 124+ (4 collections) |
| API endpoints | 128+ |
| Backend tests | 760+ (0 failures) |
| Frontend tests | 32 (Vitest) |
| Feature flags | 58+ |
| ADRs | 26 |
| LLM agents | 4 (Clinical Context, Intake, Match, Explanation) |
Total infrastructure cost: ~$20/month (21 of 25 services on free tiers)
Technology Stack¶
| Layer | Technologies |
|---|---|
| Backend | FastAPI (Python 3.12+), LangGraph, LangChain |
| Frontend | Next.js, React, TypeScript (Vercel) |
| Databases | PostgreSQL (Railway), Neo4j Aura, Qdrant Cloud |
| Cache & Events | Upstash Redis, Upstash QStash |
| Storage | Cloudflare R2 (S3-compatible) |
| Auth | Clerk (JWT, RBAC, multi-tenant orgs) |
| Feature Flags | Flagsmith |
| LLM Inference | Claude Haiku 4.5, Claude Sonnet 4.6, GPT-4o mini |
| Observability | Langfuse (LLM traces), PostHog (user behavior) |
| Resend | |
| Hosting | Railway Pro ($20/mo), Vercel (free) |
Links¶
| Resource | URL |
|---|---|
| Live API | services.curaway.ai |
| Swagger Docs | services.curaway.ai/docs |
| App | app.curaway.ai |
| Backend Repo | github.com/curaway-ai/curaway-backend |
| Frontend Repo | github.com/curaway-ai/curaway-frontend |