Mix, Match, Merge
summary
Alphabet standardizes FHIR across eight organizations, publishes protos and validators on GitHub, and ships a managed FHIR server with import/export, notifications and analytics. They build a non‑technical data‑mapping UI, an Android FHIR SDK, InfoGateway and FHIR Data Pipes for warehouse analytics. To solve HL7-to-FHIR duplication they implement a configurable reconciliation engine (HDE) that sorts by timestamp, merges 20–25 derived resources per message, avoids race conditions and supports configurable merge rules, which produces a usable longitudinal record and enables downstream enrichment and inference.
AI-written summary · about
chapters (16)
- 0:00Introduction and setup
- 1:06Google’s interoperability problem
- 3:12Fire Foundations team
- 5:43UI for non-technical users
- 7:29Managed server by Cloud
- 8:54Consumer applications by Verily
- 10:19Open Health Stack overview
- 13:11Building blocks for developers
- 16:43WHO collaboration and community
- 17:54Knowledge sharing across Alphabet
- 18:40Covid data reconciliation challenge
- 22:32HealthCARE Data Engine solution
- 26:45HDE architecture and benefits
- 29:16Maturity model of EHR
- 31:41Future of FHIR interoperability
- 32:43Learning from mistakes and community
related talks
19mTurning data into better healthcare: data for hemophilia
19mFrom Zero to Production FHIR Server in 6 Months at a Large Northeast Healthsystem
47mMapping FHIR to OMOP Using Open Source Tools
45mHow to solve scaling pains with FHIR and data streaming?
45mGoogle Cloud FHIR APIs: Data Ingestion, Management, and Analytics
32mMake EHR Data Available for Research and Public Health (MedMorph)
19mAnalyzing FHIR Data Using ML and Analytical Tools
21mClinical and Claims Data Transformation utilizing FHIR Bulk Data