To the FHIR and back. Bidirectional conversion of CCDA
summary
A bidirectional C-CDA ↔ FHIR converter is described that actually exists as a hybrid system combining a hybrid rule engine with embedded code (Zen Lisp) and mapping tables, not just slides. It performs reversible nesting via Composition to make FHIR tree-shaped, marks types with StructureDefinition hints, applies array/index/predicate rules, converts almost all types one-to-one (about 99%), and emits valid CDA XML and FHIR Bundles; it adds constant CDA meta fields, supports optional provenance, and uses MDM/IDs to deduplicate for ingest.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:05What is CDA and CCDA
- 5:02Mapping approaches overview
- 7:07First converter version experience
- 8:58Fire to CDA conversion steps
- 19:03Adding constant CDA data
- 20:27CDA to Fire conversion process
- 26:37Q&A session begins
- 27:18Handling large Fire bundles
- 29:24Comparing to published guides
- 31:32Context conduction in CCDA
- 33:39Terminology conversion challenges
- 36:35Provenance resource handling
- 38:40Medication resource mapping
- 40:04OID to system conversion
- 41:30Closing remarks
