In the list of workflow scenarios, we will: add sub-headings in the list of workflow patterns for "managed" and "unmanaged" workflows add an explanation that for "unmanaged" workflows, there may be a need for exception handling outside of the FHIR communication space will add additional workflow patterns as proposed by Vassil for each pattern, will provide example use-cases for how these might be used (including discussion of how exceptions would be handled, if not implicit in the pattern) Will make clear in the definition of Request that it doesn't imply that the resource is actionable - that the tag or use of a Task is required to make it actionable. I.e. that the resource describes the activity intended to occur, it doesn't (by itself) demand action.