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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). If the element is present, it must have either a @value, an @id, or extensions The business identifier for this task. BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by focus. For example, based on a CarePlan (= basedOn), a task is created to fulfill a ServiceRequest ( = focus ) to collect a specimen from a patient. A shared identifier common to multiple independent Task and Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time. Task that this particular task is part of. The current status of the task. An explanation as to why this task is held, failed, was refused, etc. Contains business-specific nuances of the business state. Indicates the "level" of actionability associated with the Task, i.e. this a proposed task, a planned task, an actionable task, etc. Indicates how quickly the Task should be addressed with respect to other requests. If true indicates that the Task is asking for the specified action to *not* occur. A name or code (or both) briefly describing what the task involves. A free-text description of what is to be performed. The request being fulfilled or the resource being manipulated (changed, suspended, etc.) by this task. The entity who benefits from the performance of the service specified in the task (e.g., the patient). The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. Indicates the start and/or end of the period of time when completion of the task is desired to take place. Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). The date and time this task was created. The date and time of last modification to this task. The creator of the task. The kind of participant or specific participant that should perform the task. Party responsible for managing task execution. The entity who performed the requested task. Principal physical location where this task is performed. A description, code, or reference indicating why this task needs to be performed. Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. Free-text information about the task during its lifecycle. Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. If the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Additional information that may be needed in the execution of the task. Outputs produced by the Task. 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). What task is acting on. 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). A code or description of the performer of the task. The actor or entity who performed the task. 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). Indicates the number of times the requested action should occur. The time-period for which fulfillment is sought. This must fall within the overall time period authorized in the referenced request. E.g. ServiceRequest.occurance[x]. For requests directed at multiple potential recipients or targets, this is used to specify the individual or entity from whom fulfillment is being sought. 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). A code or description to distinguish between inputs. The value of the input parameter as a basic type. 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 progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](request.html#fulfillment). A code or description to distinguish between outputs. The value of the Output parameter as a basic type. Draft Requested Received Accepted Rejected Ready Cancelled In Progress On Hold Failed Completed Entered in Error If the element is present, it must have either a @value, an @id, or extensions Unknown Proposal Plan Order Original Order Reflex Order Filler Order Instance Order Option If the element is present, it must have either a @value, an @id, or extensions