A task to be performed.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

System-assigned unique identifier for task tracking and audit. Must include at least one identifier with a canonical Polaris system URI.

Each task must have at least one identifier for tracking. Additional identifiers may be used for integration with external systems.

References to formal protocols, guidelines, or ActivityDefinitions that this task follows.

MERT requirement for protocol-based task execution.

Enables a formal definition of how he task is to be performed, enabling automation.

URI references to external protocols, guidelines, or specifications.

MERT requirement for external protocol references.

Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation.

The request, order, or authorization that initiated this task.

MERT requirement for linking tasks to originating clinical orders.

Identifier for grouping related tasks together for batch processing or workflow management.

MERT requirement for task batch management.

Billing and/or reporting can be linked to whether multiple requests were created as a single unit.

Reference to parent task when this task is part of a larger workflow or represents a sub-task.

Supports Polaris workflow branching and task hierarchy.

Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task).

Task lifecycle states aligned with clinical workflow:

• draft: Task being composed or prepared
• requested/ready: Task requires attention (shown as 'active' in UI)
• in-progress: Task being actively worked on
• completed: Task finished successfully with outcomes recorded
• cancelled: Task deliberately abandoned but audit trail preserved
• failed: Technical or process failure requiring intervention (shown as 'error' in UI)

The status drives workflow and UI presentation. Ready/requested tasks appear in active inboxes.

These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.

Captures why the task is in its current state, particularly for cancelled or failed states.

MERT requirement for status change rationale.

Codes to identify the reason for current status. These will typically be specific to a particular workflow.

Business-specific status information that supplements the standard lifecycle status.

MERT requirement for additional status context beyond standard FHIR states.

The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

There's often a need to track substates of a task - this is often variable by specific workflow implementation.

Clinical tasks in EMR workflows are always orders requiring action, not proposals or plans.

Fixed to 'order' to ensure clinical tasks have clear actionable intent.

Distinguishes whether the task is a proposal, plan or full order.

Clinical priority level for workflow triage and routing.

Used for inbox sorting and urgent task highlighting in UI.

Used to identify the service level expected while performing a task.

Coding that identifies the type of task being performed for workflow routing and automation.

Added for MERT compatibility - enables automated task routing and classification.

Codes to identify what the task involves. These will typically be specific to a particular workflow.

Canonical task description that provides the core content and remains stable throughout the task lifecycle. May include structured forms (lab requisition, referral, etc.) and supports Markdown formatting for rich content.

Polaris requires description (1..1) vs MERT optional (0..1) to prevent ambiguous work items.

The request being actioned or the resource being manipulated by this task.

MERT requirement for specifying the primary focus of task activity.

Used to identify the thing to be done.

All clinical tasks must have clear patient context for safety and clinical decision-making.

Polaris requires patient context (1..1) vs MERT optional (0..1) to prevent clinical errors from missing patient links.

Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.

Links the task to the specific clinical encounter that generated it.

Provides clinical context for task creation and helps with documentation workflow.

For some tasks it may be important to know the link between the encounter the task originated within.

Expected or actual time period during which the task is to be or was executed.

MERT requirement for task timing management.

Timestamp when the task was initially created for complete audit trail.

Polaris requires creation timestamp (1..1) vs MERT optional (0..1) for audit compliance.

Most often used along with lastUpdated to track duration of task to supporting monitoring and management.

Most recent timestamp when the task was modified.

MERT requirement for modification tracking.

Used along with history to track task activity and time in a particular task state. This enables monitoring and management.

The person, system, or organization that initiated this task.

Polaris requires requester (1..1) vs MERT optional (0..1) for clear accountability chain.

Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).

The type of performer (person, device, organization) required to complete the task.

MERT requirement for specifying required performer characteristics.

The type(s) of task performers allowed.

Use to distinguish tasks on different activity queues.

Implements hot potato principle - always exactly one owner for clear accountability:

• Individual practitioners (standard pattern)
• Group identifiers for work-stream assignment (e.g., NURSING_POOL)
• External system pseudo-users (e.g., LAB:LifeLabs)
• AI agent pseudo-users for automated processing
• RelatedPerson for patient/family-initiated tasks NOTE: Polaris requires owner (1..1) vs MERT optional (0..1) for clinical safety

The owner is responsible for the next action on this task. Ownership transfers with each significant action (forward, reply, etc.).

Identifies who is expected to perform this task.

Principal physical location where the task is to be performed.

MERT requirement for task location specification.

Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

Coded indication of why the task was created.

MERT requirement for coded task rationale.

Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

Reference to clinical condition, observation, or other resource that justifies the task.

Links task to specific clinical findings or conditions.

Insurance coverage that is relevant to the performance of this task.

MERT requirement for insurance context.

Free-text notes providing additional context, instructions, or information not captured elsewhere.

Supports rich clinical context and special instructions.

Links to Provenance resources that document key events in the task lifecycle.

MERT requirement for historical context.

Constraints that apply to the fulfillment of the task.

MERT requirement for task execution constraints.

Sometimes when fulfillment is sought, you don't want full fulfillment.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Structured input data, parameters, or resources required for task execution.

Supports structured clinical workflows and forms.

Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A code or description indicating how the input is intended to be used as part of the task execution.

If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

Inputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the input parameter as a basic type.

Results, outcomes, or deliverables produced by completing this task.

Captures structured task outcomes and deliverables.

Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The name of the Output parameter.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

Outputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the Output parameter as a basic type.

Task outputs can take any form.

System-assigned unique identifier for task tracking and audit. Must include at least one identifier with a canonical Polaris system URI.

Each task must have at least one identifier for tracking. Additional identifiers may be used for integration with external systems.

References to formal protocols, guidelines, or ActivityDefinitions that this task follows.

MERT requirement for protocol-based task execution.

URI references to external protocols, guidelines, or specifications.

MERT requirement for external protocol references.

The request, order, or authorization that initiated this task.

MERT requirement for linking tasks to originating clinical orders.

Identifier for grouping related tasks together for batch processing or workflow management.

MERT requirement for task batch management.

Reference to parent task when this task is part of a larger workflow or represents a sub-task.

Supports Polaris workflow branching and task hierarchy.

Task lifecycle states aligned with clinical workflow:

• draft: Task being composed or prepared
• requested/ready: Task requires attention (shown as 'active' in UI)
• in-progress: Task being actively worked on
• completed: Task finished successfully with outcomes recorded
• cancelled: Task deliberately abandoned but audit trail preserved
• failed: Technical or process failure requiring intervention (shown as 'error' in UI)

The status drives workflow and UI presentation. Ready/requested tasks appear in active inboxes.

Captures why the task is in its current state, particularly for cancelled or failed states.

MERT requirement for status change rationale.

Business-specific status information that supplements the standard lifecycle status.

MERT requirement for additional status context beyond standard FHIR states.

Clinical tasks in EMR workflows are always orders requiring action, not proposals or plans.

Fixed to 'order' to ensure clinical tasks have clear actionable intent.

Clinical priority level for workflow triage and routing.

Used for inbox sorting and urgent task highlighting in UI.

Coding that identifies the type of task being performed for workflow routing and automation.

Added for MERT compatibility - enables automated task routing and classification.

Canonical task description that provides the core content and remains stable throughout the task lifecycle. May include structured forms (lab requisition, referral, etc.) and supports Markdown formatting for rich content.

Polaris requires description (1..1) vs MERT optional (0..1) to prevent ambiguous work items.

MERT requirement for specifying the primary focus of task activity.

All clinical tasks must have clear patient context for safety and clinical decision-making.

Polaris requires patient context (1..1) vs MERT optional (0..1) to prevent clinical errors from missing patient links.

Links the task to the specific clinical encounter that generated it.

Provides clinical context for task creation and helps with documentation workflow.

Expected or actual time period during which the task is to be or was executed.

MERT requirement for task timing management.

Timestamp when the task was initially created for complete audit trail.

Polaris requires creation timestamp (1..1) vs MERT optional (0..1) for audit compliance.

Most recent timestamp when the task was modified.

MERT requirement for modification tracking.

The person, system, or organization that initiated this task.

Polaris requires requester (1..1) vs MERT optional (0..1) for clear accountability chain.

The type of performer (person, device, organization) required to complete the task.

MERT requirement for specifying required performer characteristics.

Implements hot potato principle - always exactly one owner for clear accountability:

• Individual practitioners (standard pattern)
• Group identifiers for work-stream assignment (e.g., NURSING_POOL)
• External system pseudo-users (e.g., LAB:LifeLabs)
• AI agent pseudo-users for automated processing
• RelatedPerson for patient/family-initiated tasks NOTE: Polaris requires owner (1..1) vs MERT optional (0..1) for clinical safety

The owner is responsible for the next action on this task. Ownership transfers with each significant action (forward, reply, etc.).

Principal physical location where the task is to be performed.

MERT requirement for task location specification.

Coded indication of why the task was created.

MERT requirement for coded task rationale.

Reference to clinical condition, observation, or other resource that justifies the task.

Links task to specific clinical findings or conditions.

Insurance coverage that is relevant to the performance of this task.

MERT requirement for insurance context.

Free-text notes providing additional context, instructions, or information not captured elsewhere.

Supports rich clinical context and special instructions.

Links to Provenance resources that document key events in the task lifecycle.

MERT requirement for historical context.

Constraints that apply to the fulfillment of the task.

MERT requirement for task execution constraints.

Structured input data, parameters, or resources required for task execution.

Supports structured clinical workflows and forms.

Results, outcomes, or deliverables produced by completing this task.

Captures structured task outcomes and deliverables.

A task to be performed.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human language.

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

System-assigned unique identifier for task tracking and audit. Must include at least one identifier with a canonical Polaris system URI.

Each task must have at least one identifier for tracking. Additional identifiers may be used for integration with external systems.

References to formal protocols, guidelines, or ActivityDefinitions that this task follows.

MERT requirement for protocol-based task execution.

Enables a formal definition of how he task is to be performed, enabling automation.

URI references to external protocols, guidelines, or specifications.

MERT requirement for external protocol references.

Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation.

The request, order, or authorization that initiated this task.

MERT requirement for linking tasks to originating clinical orders.

Identifier for grouping related tasks together for batch processing or workflow management.

MERT requirement for task batch management.

Billing and/or reporting can be linked to whether multiple requests were created as a single unit.

Reference to parent task when this task is part of a larger workflow or represents a sub-task.

Supports Polaris workflow branching and task hierarchy.

Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task).

Task lifecycle states aligned with clinical workflow:

• draft: Task being composed or prepared
• requested/ready: Task requires attention (shown as 'active' in UI)
• in-progress: Task being actively worked on
• completed: Task finished successfully with outcomes recorded
• cancelled: Task deliberately abandoned but audit trail preserved
• failed: Technical or process failure requiring intervention (shown as 'error' in UI)

The status drives workflow and UI presentation. Ready/requested tasks appear in active inboxes.

These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.

Captures why the task is in its current state, particularly for cancelled or failed states.

MERT requirement for status change rationale.

Codes to identify the reason for current status. These will typically be specific to a particular workflow.

Business-specific status information that supplements the standard lifecycle status.

MERT requirement for additional status context beyond standard FHIR states.

The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

There's often a need to track substates of a task - this is often variable by specific workflow implementation.

Clinical tasks in EMR workflows are always orders requiring action, not proposals or plans.

Fixed to 'order' to ensure clinical tasks have clear actionable intent.

Distinguishes whether the task is a proposal, plan or full order.

Clinical priority level for workflow triage and routing.

Used for inbox sorting and urgent task highlighting in UI.

Used to identify the service level expected while performing a task.

Coding that identifies the type of task being performed for workflow routing and automation.

Added for MERT compatibility - enables automated task routing and classification.

Codes to identify what the task involves. These will typically be specific to a particular workflow.

Canonical task description that provides the core content and remains stable throughout the task lifecycle. May include structured forms (lab requisition, referral, etc.) and supports Markdown formatting for rich content.

Polaris requires description (1..1) vs MERT optional (0..1) to prevent ambiguous work items.

The request being actioned or the resource being manipulated by this task.

MERT requirement for specifying the primary focus of task activity.

Used to identify the thing to be done.

All clinical tasks must have clear patient context for safety and clinical decision-making.

Polaris requires patient context (1..1) vs MERT optional (0..1) to prevent clinical errors from missing patient links.

Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.

Links the task to the specific clinical encounter that generated it.

Provides clinical context for task creation and helps with documentation workflow.

For some tasks it may be important to know the link between the encounter the task originated within.

Expected or actual time period during which the task is to be or was executed.

MERT requirement for task timing management.

Timestamp when the task was initially created for complete audit trail.

Polaris requires creation timestamp (1..1) vs MERT optional (0..1) for audit compliance.

Most often used along with lastUpdated to track duration of task to supporting monitoring and management.

Most recent timestamp when the task was modified.

MERT requirement for modification tracking.

Used along with history to track task activity and time in a particular task state. This enables monitoring and management.

The person, system, or organization that initiated this task.

Polaris requires requester (1..1) vs MERT optional (0..1) for clear accountability chain.

Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).

The type of performer (person, device, organization) required to complete the task.

MERT requirement for specifying required performer characteristics.

The type(s) of task performers allowed.

Use to distinguish tasks on different activity queues.

Implements hot potato principle - always exactly one owner for clear accountability:

• Individual practitioners (standard pattern)
• Group identifiers for work-stream assignment (e.g., NURSING_POOL)
• External system pseudo-users (e.g., LAB:LifeLabs)
• AI agent pseudo-users for automated processing
• RelatedPerson for patient/family-initiated tasks NOTE: Polaris requires owner (1..1) vs MERT optional (0..1) for clinical safety

The owner is responsible for the next action on this task. Ownership transfers with each significant action (forward, reply, etc.).

Identifies who is expected to perform this task.

Principal physical location where the task is to be performed.

MERT requirement for task location specification.

Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

Coded indication of why the task was created.

MERT requirement for coded task rationale.

Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

Reference to clinical condition, observation, or other resource that justifies the task.

Links task to specific clinical findings or conditions.

Insurance coverage that is relevant to the performance of this task.

MERT requirement for insurance context.

Free-text notes providing additional context, instructions, or information not captured elsewhere.

Supports rich clinical context and special instructions.

Links to Provenance resources that document key events in the task lifecycle.

MERT requirement for historical context.

Constraints that apply to the fulfillment of the task.

MERT requirement for task execution constraints.

Sometimes when fulfillment is sought, you don't want full fulfillment.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Indicates the number of times the requested action should occur.

E.g. order that requests monthly lab tests, fulfillment is sought for 1.

Over what time-period is fulfillment sought.

Note that period.high is the due date representing the time by which the task should be completed.

E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months.

For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought?

Structured input data, parameters, or resources required for task execution.

Supports structured clinical workflows and forms.

Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A code or description indicating how the input is intended to be used as part of the task execution.

If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.

Inputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the input parameter as a basic type.

Results, outcomes, or deliverables produced by completing this task.

Captures structured task outcomes and deliverables.

Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The name of the Output parameter.

Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.

Outputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the Output parameter as a basic type.

Task outputs can take any form.