React to Events of Data Changes on FHIR Service
summary
Azure Health Data Service captures FHIR change data, persists it, then a long‑running agent converts those changes into events and publishes to Event Grid (claimed to support millions of records per hour). Events contain only system metadata only (id, version, type), so downstream workflows in Logic Apps call the FHIR API to fetch full resources, apply filters, and trigger actions (demo: Apple Watch via Google Fit → MedTech connector → batched Observations → email on heart‑rate spike). System works; privacy limits full payloads in the MVP.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:26About Teng Li
- 1:48Agenda
- 2:08Observing the problem
- 3:16Data management system
- 4:51Reusable solution
- 5:56Customer question
- 6:34Asynchronous workflow
- 10:04Eventdriven architecture
- 10:55Enabling Eventdriven architecture
- 14:34Pop sub system
- 15:46Triggers
- 18:09New Opportunities
- 20:25Demo
- 22:19Observation Resource
- 25:14Demo Architecture
- 27:02Integration Ideas
- 27:50FHIR Subscription
- 28:38QA Session
