Mapping V2 to FHIR and back
summary
Uses the integration engine as the brain to convert V2 ADT A01 into a FHIR transaction bundle that carries per-resource request instructions, uses conditional update (search-by-identifier) to avoid duplicates, and assigns runtime UUID fullUrl references so Encounter and Observation link to the Patient before the server assigns IDs. Demonstrates conditional delete by tag or Provenance to remove only this system’s allergies, a ConceptMap + $translate for value sets, and a tested script that emulates transactions for basic FHIR servers when advanced REST features are missing.
AI-written summary · about
chapters (4)
- 0:00Start
- 26:43Limitations!
- 30:06What if the server doesn't support Transactions?
- 39:48speaking of translations
related talks
21mTransitioning of Message Mapping Guide to FHIR Implementation Guide
41mBridging research protocols in healthcare systems
38mFHIR Projects
49mBetter managing sets of resources
21mX12 gets lit: X12 to FHIR (and back again)
22mConsent management in medical research with FHIR
21mPreparations and plans from the Austrian EHR towards FHIR
44mLet's build! Clinical Practice Guidelines