Revolutionize Health Apps: Leverage Legacy for Massive Scale
summary
Breaks down concrete integration patterns: query (FHIR REST queries, cacheable snapshots), event plus query (notifications reduce polling), and event-carried state transfer used by HL7 v2 ADT feeds that can hit millions of messages per day; notes event sourcing is rarely used and update/command flows require heavy testing. Recommends Kafka-style event buses for scale, cites FHIR ~10-year adoption and ~10 KB payloads, and describes a product approach that absorbs inbound query volume from networks so source systems avoid being overwhelmed.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:03Intro
- 1:15Data Flow Diagrams Explained
- 2:26Understanding Queries
- 3:54Event Carried State Transfer Overview
- 4:41Event Sourcing Introduction
- 5:29Update Mechanisms
- 6:06Implementing Single Sign-On
- 14:22Industry Standards Discussion
- 19:15Further Reading and Resources
related talks
21mEvents with FHIR: a Simplified Way to Unify Health Data
27mOptimize Your API with Event-Driven Microservice Architecture.
36mTransforming HL7 version 2 to FHIR
53mEmerging innovations in healthcare
32mUnifying API and event driven architectures
38mScaling FHIR with microservices
16mThe story of FHIR data exchange and storage combined
23mRevolutionizing Healthcare with Enterprise Architecture