Multi-Language Support
summary
Explains concrete FHIR mechanisms: use the resource language element and xml:lang in narratives, set HTTP Content-Language and request with Accept-Language header, and use the predefined translation extension (valueString/valueMarkdown) and a language-coded extension on repeating elements like Address/Name. Terminology servers support $expand with a language parameter; recommendation is to persist language-specific expanded value sets, questionnaires and structure definitions or do runtime translation for volatile data. A translatable flag plus language-specific derived profiles is used in production; Java validator and IG tooling work is underway.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:22Presentation
- 3:04Simple Use Case
- 11:24Accept Language
- 14:27Code Systems
- 17:35Automatic Translation
- 19:08Questionnaires
- 21:37Structure definitions
- 25:30Summary
related talks
45mSupercharge FHIR Search with Large Language Models (LLMs)
43mEnglish introduction to FHIR
38mDrupal 8's Multilingual APIs
47mIntroduction to terminology
37mArabic introduction to FHIR
22mInternationalisation(i18n) & Localisation(l10n)
41mMastering FHIR Terminology: Navigating advanced services
40mIntroduction to FHIR Profiling