Context-specific mappings
summary
Doctolib builds a bidirectional mapping engine that serves multiple incompatible national IGs by adding a context path parameter and branching mapping logic at two levels: coarse resource mappers that correspond to whole-profile differences and fine-grained component mappers that map attributes like Address or Identifier. Implementation uses Kotlin, Spring Boot and MapStruct-style code generation, supports tenants per country (France, Germany, Italy) and reuses sub-mappers to stay DRY. The single engine handles distinct IGs in production without duplicating full implementations.
AI-written summary · about
chapters (8)
- 0:00Introduction and setup
- 1:48Facade approach and challenges
- 3:58MapStruct and initial mapping strategy
- 5:22Superset approach limitations
- 7:53Context-specific mapping solution
- 10:17Mapper hierarchy and implementation
- 13:29Future improvements and synergies
- 14:14Q&A session
related talks
44mFHIR Mapping Language
41mMapping V2 to FHIR and back
21mTransitioning of Message Mapping Guide to FHIR Implementation Guide
01h 00mFrom Domain Driven Design DDD to Delivery
08mLocalization for Real-World Use-Cases: Key Learnings from Onboarding Global Brands
43mGlobal Implementations with the International Patient Access
49mUsing DI to build customer specific internet offices with a single code base
50mTerminology mapping and translation – ConceptMap updates in FHIR R5