FHIR Projects
summary
A FHIR-backed document registry is built to index scanned patient records, convert daily metadata files into FHIR resources, and run rule-based validation against bundle profiles; implementation uses a Vonk-based backend plus a Cloverleaf integration engine, terminology services, and FHIRPath checks. A proof of concept ingests about half a million documents quickly and already reports document type counts, department-level paper volumes, and missing mandatory forms; next steps add binary retrieval from the archive and structured data extraction.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:28Problem and new product Akiva
- 5:18Why choose FHIR for the project
- 8:11System architecture overview
- 9:56Proof of concept results
- 11:02Rule-based validation engine
- 12:54Future integrations and expansions
- 14:02Terminology handling in FHIR
- 17:15Q&A session
related talks
16mThe story of FHIR data exchange and storage combined
45mFHIR Resources for Clinical Research
34mFHIR Projects
47mStoring data using FHIR - a good idea?
45mSafely Capture Institutional Knowledge Using
20mFHIR SQL Builder
46mFHIR Bulk Data API + What's New in v2.0
24mUnleashing the power of FHIR data with knowledge graphs