FHIR Messaging: the Unloved Paradigm
summary
Explains FHIR messaging as a bundle of type message built around a MessageHeader focus and supports notifications, query responses and transactional “messages of consequence” with request/response semantics and async store‑and‑forward. Advises caching response IDs (15 minute guidance seen, some use 24 hours), shows subscriptions using the Subscription resource, warns of snapshot/delete and provenance problems, notes NHS uses Composition as a grouping workaround to avoid graph validation, and that 5 million messages a day beats 50M REST calls because graph definition not supported by validators.
AI-written summary · about
chapters (18)
- 0:00Introduction to FHIR messaging
- 1:22Why messaging matters
- 2:25Messaging characteristics in FHIR
- 5:17Message structure in FHIR
- 8:15Synchronous vs asynchronous messaging
- 9:44Message patterns explained
- 15:08Handling message consequences
- 17:58Trigger events and focal resources
- 18:19Snapshot problem in messaging
- 20:47Querying in FHIR messaging
- 21:52Subscriptions in FHIR
- 23:21Conformance in messaging
- 27:37Graph definitions for validation
- 31:11Validation challenges
- 33:40NHS implementation approach
- 36:11When to choose messaging over REST
- 37:54Choosing the right paradigm
- 39:40Q&A on composition and messaging
