Subscriptions
summary
FHIR moves from query-based polling to a topic-based subscription model that lets servers notify clients when defined events occur, avoiding constant GETs. R5 adds a SubscriptionTopic resource, a SubscriptionStatus and a new bundle type; R4/R4B get backports and profiles. Channels include REST-hook, WebSocket, email and FHIR messaging with three payload modes: ping, id-only, full resource. An open-source .NET reference server with UI (subscriptions.argo.run) implements R4/R4B/R5 for testing and demos, and scales via all-in-one, relay or logic-server architectures.
AI-written summary · about
chapters (13)
- 0:00Introduction and welcome
- 1:03About the speaker
- 3:32Fire and REST polling problem
- 7:00History of FHIR subscriptions
- 8:46Subscription topic design
- 13:01Subscription topic examples
- 17:11Subscription resource structure
- 20:43Payload types and security
- 23:30Architectural considerations
- 25:35Care team notifications use case
- 29:25Reference implementation demo
- 33:21Adoption and production systems
- 34:32Q&A session
