Multilingual clinic platform

The problem

A multi-location private medical center serving the Eastern European diaspora needed a web platform in Polish, Ukrainian, and Russian. Patients did not speak the local language easily; appointment booking required wiring through an external booking API; doctor profiles and specialty directories spread across many locations. The previous site lost patients during the booking flow because language switched mid-step or content was machine-translated and clinically wrong.

The approach

We built a React + Vite frontend with Express backend, i18next for translation routing, multi-step appointment wizard wired to the external booking API, doctor profile and specialty directory across locations, lab partner deep links, and per-specialty service pages. Language persists across the full booking flow; localized content uses native medical terminology curated by clinical staff, not auto-translation.

Stack and engineering choices

• React + Vite frontend
• Express backend
• i18next translation routing
• Multi-step appointment wizard
• External booking API integration
• Per-specialty service pages
• Native medical terminology

Outcome

Patients complete appointments in their own language without dropping mid-flow. Doctor and specialty discovery works across the whole network instead of per-location silos. The clinic adds new languages with config and a translation pass, not a parallel build.