Building an FHIR API for an EHR – The journey of i.s.h.med
summary
Built a FHIR API for i.s.h.med that keeps the EHR as the single source of truth behind a containerized Kubernetes facade, with separate endpoints per FHIR major release and market (e.g., German 0.4), an identifier service that maps complex encounter and backend keys, tenancy-aware routing, and a terminology service implemented with Ontoserver by CSIRO to translate local catalogs to SNOMED/LOINC. The result provides an MDR-compliant interoperability channel and supports EASY attestation and German funding requirements.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 3:00Why build a FHIR API
- 8:19Technical approach and architecture
- 13:28Terminology and data mapping
- 17:34Implementation process








