Integrating a FHIR Server in Your Architecture
summary
Explains concrete integration patterns: facade on the source, generic FHIR server in the middle, and facade on the consumer, showing when each is used and how CRUD, search, history, validation, transactions and custom $operations are implemented. Covers real examples — external reporting, portal/app platform, clinical data repository (including ETL into an existing warehouse), and system integration — and gives tradeoffs: copy versus real‑time, ownership of authoritative source, conflict resolution strategies, use of an integration engine for scheduling/routing, and when messaging beats REST.
AI-written summary · about
chapters (10)
- 0:00Introduction to FHIR servers
- 2:32What is a FHIR server
- 8:41Types of FHIR servers
- 11:10Example use cases
- 13:25Basic integration patterns
- 21:00Multiple sources integration
- 26:21Applying patterns to examples
- 31:53Integration engines and messaging
- 35:09Key considerations for implementation
- 37:43Q&A and summary
related talks
53mEffective Design of RESTful APIs
21mPreparations and plans from the Austrian EHR towards FHIR
27mFHIR for delivery to quality registrations
36mApplication Architecture Patterns
38mFHIR Projects
27mEnterprise Architecture and FACIN - Serpro Case
01h 01mAn Architect's Approach to API Strategies
41mBridging research protocols in healthcare systems