This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R4B: Task.location (new:Reference(Location))

Element Task.location has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.location has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.location has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.location has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4B: Task.reasonReference (new:Reference(Resource))

Element Task.reasonReference has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.reasonReference has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.reasonReference has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.reasonReference has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in Task.reasonCode if the data is free (uncoded) text.

R4B: Task.insurance (new:Reference(Coverage,ClaimResponse))

Element Task.insurance has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.insurance has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.insurance has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.insurance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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. Usually modifier elements provide negation or qualification. In order 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.

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.

The status of the resource instance.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A code specifying the state of the resource instance.

R4B: Task.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, source, tag, versionId)

Element Task.meta is mapped to FHIR STU3 element ProcessRequest.meta as SourceIsBroaderThanTarget. Element Task.meta is mapped to FHIR STU3 element ProcessResponse.meta as SourceIsBroaderThanTarget. Element Task.meta is mapped to FHIR STU3 element Task.meta as SourceIsBroaderThanTarget. The mappings for Task.meta do not cover the following types: Meta. The mappings for Task.meta do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.

R4B: Task.text additional types (Narrative) additional types from child elements (div, status)

Element Task.text is mapped to FHIR STU3 element ProcessRequest.text as SourceIsBroaderThanTarget. Element Task.text is mapped to FHIR STU3 element ProcessResponse.text as SourceIsBroaderThanTarget. Element Task.text is mapped to FHIR STU3 element Task.text as SourceIsBroaderThanTarget. The mappings for Task.text do not cover the following types: Narrative. The mappings for Task.text do not cover the following types based on type expansion: div, status. 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.

R4B: Task.location (new:Reference(Location))

Element Task.location has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.location has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.location has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.location has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4B: Task.reasonReference (new:Reference(Resource))

Element Task.reasonReference has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.reasonReference has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.reasonReference has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.reasonReference has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in Task.reasonCode if the data is free (uncoded) text.

R4B: Task.insurance (new:Reference(Coverage,ClaimResponse))

Element Task.insurance has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.insurance has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.insurance has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.insurance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4B: Task.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element Task.identifier is mapped to FHIR STU3 element ProcessRequest.identifier as SourceIsBroaderThanTarget. Element Task.identifier is mapped to FHIR STU3 element ProcessResponse.identifier as SourceIsBroaderThanTarget. Element Task.identifier is mapped to FHIR STU3 element Task.identifier as SourceIsBroaderThanTarget. The mappings for Task.identifier do not cover the following types: Identifier. The mappings for Task.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources.

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 may not always be associated with version changes to the resource.

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

An Extension

R4B: Task.meta additional types (Meta) additional types from child elements (lastUpdated, profile, security, source, tag, versionId)

Element Task.meta is mapped to FHIR STU3 element ProcessRequest.meta as SourceIsBroaderThanTarget. Element Task.meta is mapped to FHIR STU3 element ProcessResponse.meta as SourceIsBroaderThanTarget. Element Task.meta is mapped to FHIR STU3 element Task.meta as SourceIsBroaderThanTarget. The mappings for Task.meta do not cover the following types: Meta. The mappings for Task.meta do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId.

The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.

The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.

When the resource last changed - e.g. when the version changed.

This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.

A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.

It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.

Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.

Security Labels from the Healthcare Privacy and Security Classification System.

Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.

The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.

Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

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 may 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 in formation is added later.

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

An Extension

R4B: Task.text additional types (Narrative) additional types from child elements (div, status)

Element Task.text is mapped to FHIR STU3 element ProcessRequest.text as SourceIsBroaderThanTarget. Element Task.text is mapped to FHIR STU3 element ProcessResponse.text as SourceIsBroaderThanTarget. Element Task.text is mapped to FHIR STU3 element Task.text as SourceIsBroaderThanTarget. The mappings for Task.text do not cover the following types: Narrative. The mappings for Task.text do not cover the following types based on type expansion: div, status. 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.

The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.

The status of a resource narrative

The actual narrative content, a stripped down version of XHTML.

The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content may not contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.

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.

An Extension

R4B: Task.location (new:Reference(Location))

Element Task.location has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.location has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.location has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.location has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R4B: Task.reasonReference (new:Reference(Resource))

Element Task.reasonReference has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.reasonReference has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.reasonReference has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.reasonReference has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in Task.reasonCode if the data is free (uncoded) text.

R4B: Task.insurance (new:Reference(Coverage,ClaimResponse))

Element Task.insurance has a context of ProcessRequest based on following the parent source element upwards and mapping to ProcessRequest. Element Task.insurance has a context of ProcessResponse based on following the parent source element upwards and mapping to ProcessResponse. Element Task.insurance has a context of Task based on following the parent source element upwards and mapping to Task. Element Task.insurance has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

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. Usually modifier elements provide negation or qualification. In order 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.

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.

The ProcessRequest business identifier.

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

An Extension

R4B: Task.identifier additional types (Identifier) additional types from child elements (assigner, period, system, type, use, value)

Element Task.identifier is mapped to FHIR STU3 element ProcessRequest.identifier as SourceIsBroaderThanTarget. Element Task.identifier is mapped to FHIR STU3 element ProcessResponse.identifier as SourceIsBroaderThanTarget. Element Task.identifier is mapped to FHIR STU3 element Task.identifier as SourceIsBroaderThanTarget. The mappings for Task.identifier do not cover the following types: Identifier. The mappings for Task.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.

The purpose of this identifier.

This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage.

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

The status of the resource instance.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A code specifying the state of the resource instance.

The type of processing action being requested, for example Reversal, Readjudication, StatusRequest,PendedRequest.

List of allowable action which this resource can request.

The organization which is the target of the request.

The date when this resource was created.

The practitioner who is responsible for the action specified in this request.

The organization which is responsible for the action speccified in this request.

Reference of resource which is the target or subject of this action.

Reference of a prior response to resource which is the target or subject of this action.

If true remove all history excluding audit.

Some resources must not simply be reversed in a processing or accounting sense but rather must have all history removed, such as the accidental submission of sensitive and/or wrong information. If the receiver cannot comply with a Nullify request then they must reject the request.

A reference to supply which authenticates the process.

List of top level items to be re-adjudicated, if none specified then the entire submission is re-adjudicated.

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. In order 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.

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 that contains it. Usually modifier elements provide negation or qualification. In order 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.

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.

A service line number.

Names of resource types to include.

Names of resource types to exclude.

A period of time during which the fulfilling resources would have been created.