VIPP5 module 3: Hospital-to-hospital data exchange
summary
Two Dutch hospitals implement VIPP5 Module 3 to share patient ZIPS using an ETL pipeline that transforms source JSON and HL7v2 into FHIR, orchestrated by a message bus with a MassTransit wrapper so deployments switch between RabbitMQ, Azure or AWS. Transformation runs in C# with the Firely .NET SDK, validation is a separate scalable consumer, and an inward/outward FHIR pair with plugins handles merges and full erases. An active patient registry limits loads and correlation ID tracking provides end-to-end observability; one rollout is live, another is mid‑deployment.
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 3:57Use case and real-world problem
- 8:33Source systems and active patients
- 12:01ETL pipeline and messaging solution
- 23:18Data exchange between hospitals
- 30:00Lessons learned and key insights
- 32:25Q&A session
related talks
19mTurning data into better healthcare: data for hemophilia
46mPost-Acute Care Interoperability work group - outcomes
54mPlenary Session
11mPlatform Engineering for Healthcare Interoperability
46mInternational Patient Summary (IPS) - Moving from Specification to Implementation
23mThe Smart4Health project
02h 01mLet's Build a FHIR App: Introduction HAPI Library for FHIR
23mImplementing Provider Directory APIs