Argonaut: Subscriptions
summary
FHIR Subscriptions move from result-set polling to a topic-based model with a new canonical SubscriptionTopic that defines triggers and allowed filters; Subscription objects bind topics to endpoints and choose channel types (rest-hook, websocket, email, FHIR Messaging) and payload modes such as ping, id-only payload or full resource. R4 implementations use a history bundle for notifications whose first entry is a SubscriptionStatus; a reference server (C# backend, TypeScript UI) is public at subscriptions.argo.run and guidance favors HTTPS and SMART Backend Services for authentication.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:11History
- 3:44Firecast
- 4:40Cds Hooks
- 5:48Subscription Rework
- 9:25What Is a Subscription
- 12:53Allowed Filters
- 13:41Examples
- 19:07Channel Types
- 21:02Pings
- 27:14Subscription Status Resource
- 32:05Will There Be any Standards Recommendations Offered for Security for How Fire Server Will Authenticate to the Subscription Endpoints
- 38:25Will Complex Stateful Subscriptions Be Supported
- 38:51Subscriptions Framework
