FHIR workflow
summary
FHIR workflow lays out concrete patterns and tools: a two-year Workflow Project produces mappings from resources into three patterns — definition, request (intent), and event — and introduces the Task resource introduced in R3 as the generic workhorse to separate authorizations from executable work with explicit state machines and businessStatus. An example scenario resource packages the hundreds of resource instances a complex lab or referral flow spawns. Work is ongoing toward computable mappings and R4 refinements; reference implementations and IG guidance are underway.
AI-written summary · about
chapters (10)
- 0:00Introduction to workflow
- 1:33Historical context
- 3:26FHIR and workflow
- 5:54Workflow project goals
- 7:17Patterns for consistency
- 13:21Refining resource alignment
- 18:12Requests and task execution
- 23:30State machines and status
- 27:04Pattern implementations
- 32:54Q&A and concluding remarks
