Extending SMART on FHIR with FHIRcast
summary
Realtime synchronization of disparate EHR-connected apps uses SMART on FHIR launch to deliver two launch parameters: hub URL and session id, then the app creates a subscription via an HTTP POST subscribe to that hub. Workflow events are pushed as JSON whose body is FHIR resources — e.g., patient/encounter open/close — and clients unsubscribe similarly. An open-source .NET Core sandbox and tutorial live on GitHub and prototypes run at connectathons; WebSocket vs server-sent events remains unresolved for production.
AI-written summary · about
chapters (7)
- 0:00Introduction to SMART on FHIR
- 2:56Limitations of embedded SMART apps
- 5:20Need for FHIRcast synchronization
- 9:39How FHIRcast extends SMART
- 15:03Current status and next steps
- 26:30Vendor interest and future plans
- 29:29Q&A and closing








