We agree that clarifications are needed to the Scope and Usage of the resource to highlight areas of workflow in healthcare where Task can be used. Also, links to the Workflow module page will be added where appropriate.    Change the sentence "A task to be performed." to the following: A task to be performed as a part of a workflow and the related informations like inputs, outputs and execution progress. While very simple workflows can be implemented with Request alone, most workflows would require a Task (explicit or contained) as a means to track the execution data (i.e. inputs, outputs, status). Please refer to the workflow page for more details.    Change scope and usage to: A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity. Concretely the Task resource could be used in FHIR to serve different purposes like: operationalizing a Request (but could exists without a Request) communicate between Filler and Placer allows tracking of business status (i.e. collection of specimen, dispense of medication, procedure scheduled) communicate the results of the execution (e.g. via .output) Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real-world actions by one or more humans. Some orders can only be processed when other real-world actions happen, such as a patient presenting themselves so that the action to be performed can actually be performed. Often these real-world dependencies are only implicit in the order details.