Multi-language intake is the place where most SDC form builders show their seams. A practice with a meaningful share of Spanish, Mandarin, or Vietnamese-speaking patients does not want to maintain three parallel Questionnaire resources, each with its own version history, just so the front desk can hand a tablet to the right person. The cleaner answer in FHIR is a single Questionnaire with the translation extensions populated, rendered correctly by a tool that knows how to use them. The honest answer in 2026 is that only a handful of SDC tools do this without surprise.
This is the five SDC form tools that handle multi-language intake cleanly, with the rough sense of where each one fits. For more on FHIR for healthcare teams covering the wider context, the broader catalog is the place to start.
For the upstream picture of what a FHIR form tool needs to do at all, the complete guide to FHIR form tools for US clinics in 2026 is the reference.
The 5 Tools That Actually Handle Multi-Language
The shortlist:
- LHC-Forms. The US NLM open-source SDC renderer, with built-in support for the translation extensions on Questionnaire items and answer options, used widely in NIH research projects that span language groups.
- Formbox. Health Samurai's standalone SDC form builder, picked by multi-clinic practices that need the same Questionnaire to render in multiple languages without duplicating the resource.
- Smile Digital Health Forms. A commercial Questionnaire layer with translation extension support, common in larger US health systems serving multi-language patient populations.
- Aidbox FHIR Forms. A managed SDC form layer with translation handling, useful when a practice wants one vendor across forms and a backing FHIR store.
- Beda EMR Forms. A practical SDC layer that handles translation extensions well enough for fast template iteration across two or three languages.
What Separates Them in Practice
Three things tend to drive the choice for multi-language intake:
- Translation extension support. The form has to honor the FHIR translation extensions for both item text and answer option text, without forcing a separate Questionnaire per language.
- Language switching at runtime. The form has to let a patient or front-desk staff pick a language at session start, without a page reload that loses partial input.
- Right-to-left script handling. If the patient population includes Arabic or Hebrew speakers, the rendering layer has to switch direction cleanly, not stretch the layout sideways.
Most tools support the first item adequately. Fewer get the runtime switch behavior right. Right-to-left handling done well is still rare in 2026.
Which One Fits Which Practice
A research-heavy practice with a strong open-source bias usually lands on LHC-Forms. A mid-size multi-clinic group with developer capacity tends toward Formbox for the flexibility. A larger health system that wants a managed multi-language story often picks Smile or Aidbox Forms. A scrappy group that iterates fast on a small set of languages goes with Beda.
How to Run a Real Multi-Language Evaluation
Vendor demos rarely include a real switch from English to a right-to-left script mid-session. Ask each tool to render a real intake Questionnaire in three languages, switch language at runtime without losing partial input, validate a value-set-driven dropdown in each language, and extract the response into a clean FHIR Observation. The output of that exercise tells you more than any spec sheet.
For closely related discussions, the top 5 SDC form builders for urgent care settings in 2026 and SDC form builders vs traditional EMR forms for US practices are the natural next reads.
Sources
- Languages page (translation extension, language element semantics) - HL7 FHIR R6 spec
- Multi-Language Support in FHIR (foundational) - PDF slides, Rene Spronk, DevDays 2021
- NLM FHIR Questionnaire Tools - PDF slides, Ye Wang (NLM), DevDays 2024