We will: In "Direct connection?" section, will call out the fact that there is work-in-progress to allow routing over REST and that once this in place, if it fits within the constraints of the environment, messaging would no longer be necessary. Rename "Human Intervention?" to "Allow Human Intervention?" Revamp "Formal Authorization Required" to: make clear we're talking about authorization for information exchange make clear that Task can be in play even if there's a CommunicationRequest will consider renaming and adjusting diagram so interplay between CommunicationRequest and Task is clearer will reflect that authorization for information exchange sometimes stems from a 'higher level' request (e.g. ServiceRequest, MedicationRequest, etc.) We will add a 'recursive' step beneath Collection and Bundle that speaks to choosing the mechanism for access/exchange of documents and will add documentation that explains the purpose of that recursion.