R5-PlanDefinition-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-PlanDefinition-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-PlanDefinition-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to PlanDefinitionversion: 4.0.1) Source Code Relationship Target Code Comment PlanDefinition.meta (meta) is equivalent to PlanDefinition.meta Element `PlanDefinition.meta` is mapped to FHIR R4 element `PlanDefinition.meta` as `Equivalent`. PlanDefinition.implicitRules (implicitRules) is equivalent to PlanDefinition.implicitRules Element `PlanDefinition.implicitRules` is mapped to FHIR R4 element `PlanDefinition.implicitRules` as `Equivalent`. 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 its narrative along with other profiles, value sets, etc. PlanDefinition.language (language) is equivalent to PlanDefinition.language Element `PlanDefinition.language` is mapped to FHIR R4 element `PlanDefinition.language` as `Equivalent`. 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 HTML…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-PlanDefinition-element-map-to-R4
  l: R5-PlanDefinition-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5PlanDefinitionElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 PlanDefinition to FHIR R4 PlanDefinition
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:47.6980417-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 PlanDefinition to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
    l: PlanDefinition
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
    l: PlanDefinition
  target version:
    v: 4.0.1
  element:
    code:
      v: PlanDefinition.meta
    display:
      v: meta
    target:
      code:
        v: PlanDefinition.meta
      display:
        v: PlanDefinition.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.meta` is mapped to FHIR R4 element `PlanDefinition.meta` as `Equivalent`.
  element:
    code:
      v: PlanDefinition.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: PlanDefinition.implicitRules
      display:
        v: PlanDefinition.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.implicitRules` is mapped to FHIR R4 element `PlanDefinition.implicitRules` as `Equivalent`. 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 its narrative along with other profiles, value sets, etc.
  element:
    code:
      v: PlanDefinition.language
    display:
      v: language
    target:
      code:
        v: PlanDefinition.language
      display:
        v: PlanDefinition.language
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.language` is mapped to FHIR R4 element `PlanDefinition.language` as `Equivalent`. 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).
  element:
    code:
      v: PlanDefinition.text
    display:
      v: text
    target:
      code:
        v: PlanDefinition.text
      display:
        v: PlanDefinition.text
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.text` is mapped to FHIR R4 element `PlanDefinition.text` as `Equivalent`. Contained resources do not have a 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.
  element:
    code:
      v: PlanDefinition.contained
    display:
      v: contained
    target:
      code:
        v: PlanDefinition.contained
      display:
        v: PlanDefinition.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.contained` is mapped to FHIR R4 element `PlanDefinition.contained` as `Equivalent`. 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.
  element:
    code:
      v: PlanDefinition.url
    display:
      v: url
    target:
      code:
        v: PlanDefinition.url
      display:
        v: PlanDefinition.url
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.url` is mapped to FHIR R4 element `PlanDefinition.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
  element:
    code:
      v: PlanDefinition.identifier
    display:
      v: identifier
    target:
      code:
        v: PlanDefinition.identifier
      display:
        v: PlanDefinition.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.identifier` is mapped to FHIR R4 element `PlanDefinition.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this plan definition outside of FHIR, where it is not possible to use the logical URI.
  element:
    code:
      v: PlanDefinition.version
    display:
      v: version
    target:
      code:
        v: PlanDefinition.version
      display:
        v: PlanDefinition.version
      equivalence:
        v: equivalent
      comment:
        v: Element `PlanDefinition.version` is mapped to FHIR R4 element `PlanDefinition.version` as `Equivalent`. There may be different plan definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

code:
  v: PlanDefinition.name
display:
  v: name
target:
  code:
    v: PlanDefinition.name
  display:
    v: PlanDefinition.name
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.name` is mapped to FHIR R4 element `PlanDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

code:
  v: PlanDefinition.title
display:
  v: title
target:
  code:
    v: PlanDefinition.title
  display:
    v: PlanDefinition.title
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.title` is mapped to FHIR R4 element `PlanDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: PlanDefinition.subtitle
display:
  v: subtitle
target:
  code:
    v: PlanDefinition.subtitle
  display:
    v: PlanDefinition.subtitle
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.subtitle` is mapped to FHIR R4 element `PlanDefinition.subtitle` as `Equivalent`.

code:
  v: PlanDefinition.type
display:
  v: type
target:
  code:
    v: PlanDefinition.type
  display:
    v: PlanDefinition.type
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.type` is mapped to FHIR R4 element `PlanDefinition.type` as `Equivalent`.

code:
  v: PlanDefinition.status
display:
  v: status
target:
  code:
    v: PlanDefinition.status
  display:
    v: PlanDefinition.status
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.status` is mapped to FHIR R4 element `PlanDefinition.status` as `Equivalent`. Allows filtering of plan definitions that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.experimental
display:
  v: experimental
target:
  code:
    v: PlanDefinition.experimental
  display:
    v: PlanDefinition.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.experimental` is mapped to FHIR R4 element `PlanDefinition.experimental` as `Equivalent`. Allows filtering of plan definitions that are appropriate for use versus not.

code:
  v: PlanDefinition.subject[x]
display:
  v: subject[x]
target:
  code:
    v: PlanDefinition.subject[x]
  display:
    v: PlanDefinition.subject[x]
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.subject[x]` is mapped to FHIR R4 element `PlanDefinition.subject[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.subject[x]` do not cover the following types: canonical. The target context `PlanDefinition.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R5 element `PlanDefinition.subject[x]` with unmapped reference targets: AdministrableProductDefinition, ManufacturedItemDefinition, MedicinalProductDefinition, PackagedProductDefinition, SubstanceDefinition. Source element `PlanDefinition.subject[x]` has unmapped reference types. While the target element `PlanDefinition.subject[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases.

code:
  v: PlanDefinition.date
display:
  v: date
target:
  code:
    v: PlanDefinition.date
  display:
    v: PlanDefinition.date
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.date` is mapped to FHIR R4 element `PlanDefinition.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the plan definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.publisher
display:
  v: publisher
target:
  code:
    v: PlanDefinition.publisher
  display:
    v: PlanDefinition.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.publisher` is mapped to FHIR R4 element `PlanDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the plan definition is the organization or individual primarily responsible for the maintenance and upkeep of the plan definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the plan definition. This item SHOULD be populated unless the information is available from context.

code:
  v: PlanDefinition.contact
display:
  v: contact
target:
  code:
    v: PlanDefinition.contact
  display:
    v: PlanDefinition.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.contact` is mapped to FHIR R4 element `PlanDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.description
display:
  v: description
target:
  code:
    v: PlanDefinition.description
  display:
    v: PlanDefinition.description
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.description` is mapped to FHIR R4 element `PlanDefinition.description` as `Equivalent`. This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the plan definition is presumed to be the predominant language in the place the plan definition was created).

code:
  v: PlanDefinition.useContext
display:
  v: useContext
target:
  code:
    v: PlanDefinition.useContext
  display:
    v: PlanDefinition.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.useContext` is mapped to FHIR R4 element `PlanDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: PlanDefinition.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: PlanDefinition.jurisdiction
  display:
    v: PlanDefinition.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.jurisdiction` is mapped to FHIR R4 element `PlanDefinition.jurisdiction` as `Equivalent`. Element `PlanDefinition.jurisdiction` has been flagged as deprecated. It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

code:
  v: PlanDefinition.purpose
display:
  v: purpose
target:
  code:
    v: PlanDefinition.purpose
  display:
    v: PlanDefinition.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.purpose` is mapped to FHIR R4 element `PlanDefinition.purpose` as `Equivalent`. This element does not describe the usage of the plan definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this plan definition.

code:
  v: PlanDefinition.usage
display:
  v: usage
target:
  code:
    v: PlanDefinition.usage
  display:
    v: PlanDefinition.usage
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.usage` is mapped to FHIR R4 element `PlanDefinition.usage` as `Equivalent`.

code:
  v: PlanDefinition.copyright
display:
  v: copyright
target:
  code:
    v: PlanDefinition.copyright
  display:
    v: PlanDefinition.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.copyright` is mapped to FHIR R4 element `PlanDefinition.copyright` as `Equivalent`. The short copyright declaration (e.g. (c) '2015+ xyz organization' should be sent in the copyrightLabel element.

code:
  v: PlanDefinition.approvalDate
display:
  v: approvalDate
target:
  code:
    v: PlanDefinition.approvalDate
  display:
    v: PlanDefinition.approvalDate
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.approvalDate` is mapped to FHIR R4 element `PlanDefinition.approvalDate` as `Equivalent`. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.lastReviewDate
display:
  v: lastReviewDate
target:
  code:
    v: PlanDefinition.lastReviewDate
  display:
    v: PlanDefinition.lastReviewDate
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.lastReviewDate` is mapped to FHIR R4 element `PlanDefinition.lastReviewDate` as `Equivalent`. If specified, this date follows the original approval date. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.effectivePeriod
display:
  v: effectivePeriod
target:
  code:
    v: PlanDefinition.effectivePeriod
  display:
    v: PlanDefinition.effectivePeriod
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.effectivePeriod` is mapped to FHIR R4 element `PlanDefinition.effectivePeriod` as `Equivalent`. The effective period for a plan definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a plan definition intended to be used for the year 2016 might be published in 2015. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.topic
display:
  v: topic
target:
  code:
    v: PlanDefinition.topic
  display:
    v: PlanDefinition.topic
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.topic` is mapped to FHIR R4 element `PlanDefinition.topic` as `Equivalent`. Element `PlanDefinition.topic` has been flagged as deprecated. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'topic' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#topic and useContext.valueCodeableConcept indicating the topic)

code:
  v: PlanDefinition.author
display:
  v: author
target:
  code:
    v: PlanDefinition.author
  display:
    v: PlanDefinition.author
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.author` is mapped to FHIR R4 element `PlanDefinition.author` as `Equivalent`.

code:
  v: PlanDefinition.editor
display:
  v: editor
target:
  code:
    v: PlanDefinition.editor
  display:
    v: PlanDefinition.editor
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.editor` is mapped to FHIR R4 element `PlanDefinition.editor` as `Equivalent`.

code:
  v: PlanDefinition.reviewer
display:
  v: reviewer
target:
  code:
    v: PlanDefinition.reviewer
  display:
    v: PlanDefinition.reviewer
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.reviewer` is mapped to FHIR R4 element `PlanDefinition.reviewer` as `Equivalent`. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.endorser
display:
  v: endorser
target:
  code:
    v: PlanDefinition.endorser
  display:
    v: PlanDefinition.endorser
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.endorser` is mapped to FHIR R4 element `PlanDefinition.endorser` as `Equivalent`. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: PlanDefinition.relatedArtifact
display:
  v: relatedArtifact
target:
  code:
    v: PlanDefinition.relatedArtifact
  display:
    v: PlanDefinition.relatedArtifact
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.relatedArtifact` is mapped to FHIR R4 element `PlanDefinition.relatedArtifact` as `Equivalent`. Each related artifact is either an attachment, or a reference to another resource, but not both.

code:
  v: PlanDefinition.library
display:
  v: library
target:
  code:
    v: PlanDefinition.library
  display:
    v: PlanDefinition.library
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.library` is mapped to FHIR R4 element `PlanDefinition.library` as `Equivalent`.

code:
  v: PlanDefinition.goal
display:
  v: goal
target:
  code:
    v: PlanDefinition.goal
  display:
    v: PlanDefinition.goal
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.goal` is mapped to FHIR R4 element `PlanDefinition.goal` as `Equivalent`.

code:
  v: PlanDefinition.goal.category
display:
  v: category
target:
  code:
    v: PlanDefinition.goal.category
  display:
    v: PlanDefinition.goal.category
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.category` is mapped to FHIR R4 element `PlanDefinition.goal.category` as `Equivalent`.

code:
  v: PlanDefinition.goal.description
display:
  v: description
target:
  code:
    v: PlanDefinition.goal.description
  display:
    v: PlanDefinition.goal.description
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.description` is mapped to FHIR R4 element `PlanDefinition.goal.description` as `Equivalent`. If no code is available, use CodeableConcept.text.

code:
  v: PlanDefinition.goal.priority
display:
  v: priority
target:
  code:
    v: PlanDefinition.goal.priority
  display:
    v: PlanDefinition.goal.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.priority` is mapped to FHIR R4 element `PlanDefinition.goal.priority` as `Equivalent`.

code:
  v: PlanDefinition.goal.start
display:
  v: start
target:
  code:
    v: PlanDefinition.goal.start
  display:
    v: PlanDefinition.goal.start
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.start` is mapped to FHIR R4 element `PlanDefinition.goal.start` as `Equivalent`.

code:
  v: PlanDefinition.goal.addresses
display:
  v: addresses
target:
  code:
    v: PlanDefinition.goal.addresses
  display:
    v: PlanDefinition.goal.addresses
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.addresses` is mapped to FHIR R4 element `PlanDefinition.goal.addresses` as `Equivalent`.

code:
  v: PlanDefinition.goal.documentation
display:
  v: documentation
target:
  code:
    v: PlanDefinition.goal.documentation
  display:
    v: PlanDefinition.goal.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.documentation` is mapped to FHIR R4 element `PlanDefinition.goal.documentation` as `Equivalent`.

code:
  v: PlanDefinition.goal.target
display:
  v: target
target:
  code:
    v: PlanDefinition.goal.target
  display:
    v: PlanDefinition.goal.target
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.goal.target` is mapped to FHIR R4 element `PlanDefinition.goal.target` as `Equivalent`.

code:
  v: PlanDefinition.goal.target.measure
display:
  v: measure
target:
  code:
    v: PlanDefinition.goal.target.measure
  display:
    v: PlanDefinition.goal.target.measure
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.target.measure` is mapped to FHIR R4 element `PlanDefinition.goal.target.measure` as `Equivalent`.

code:
  v: PlanDefinition.goal.target.detail[x]
display:
  v: detail[x]
target:
  code:
    v: PlanDefinition.goal.target.detail[x]
  display:
    v: PlanDefinition.goal.target.detail[x]
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.goal.target.detail[x]` is mapped to FHIR R4 element `PlanDefinition.goal.target.detail[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.goal.target.detail[x]` do not cover the following types: boolean, integer, Ratio, string. The target context `PlanDefinition.goal.target.detail[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.goal.target`. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the goal.target.measure defines a coded value.

code:
  v: PlanDefinition.goal.target.due
display:
  v: due
target:
  code:
    v: PlanDefinition.goal.target.due
  display:
    v: PlanDefinition.goal.target.due
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.goal.target.due` is mapped to FHIR R4 element `PlanDefinition.goal.target.due` as `Equivalent`.

code:
  v: PlanDefinition.action
display:
  v: action
target:
  code:
    v: PlanDefinition.action
  display:
    v: PlanDefinition.action
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action` is mapped to FHIR R4 element `PlanDefinition.action` as `Equivalent`. Note that there is overlap between many of the elements defined here and the ActivityDefinition resource. When an ActivityDefinition is referenced (using the definition element), the overlapping elements in the plan override the content of the referenced ActivityDefinition unless otherwise documented in the specific elements. See the PlanDefinition resource for more detailed information.

code:
  v: PlanDefinition.action.prefix
display:
  v: prefix
target:
  code:
    v: PlanDefinition.action.prefix
  display:
    v: PlanDefinition.action.prefix
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.prefix` is mapped to FHIR R4 element `PlanDefinition.action.prefix` as `Equivalent`.

code:
  v: PlanDefinition.action.title
display:
  v: title
target:
  code:
    v: PlanDefinition.action.title
  display:
    v: PlanDefinition.action.title
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.title` is mapped to FHIR R4 element `PlanDefinition.action.title` as `Equivalent`.

code:
  v: PlanDefinition.action.description
display:
  v: description
target:
  code:
    v: PlanDefinition.action.description
  display:
    v: PlanDefinition.action.description
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.description` is mapped to FHIR R4 element `PlanDefinition.action.description` as `Equivalent`.

code:
  v: PlanDefinition.action.textEquivalent
display:
  v: textEquivalent
target:
  code:
    v: PlanDefinition.action.textEquivalent
  display:
    v: PlanDefinition.action.textEquivalent
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.textEquivalent` is mapped to FHIR R4 element `PlanDefinition.action.textEquivalent` as `Equivalent`.

code:
  v: PlanDefinition.action.priority
display:
  v: priority
target:
  code:
    v: PlanDefinition.action.priority
  display:
    v: PlanDefinition.action.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.priority` is mapped to FHIR R4 element `PlanDefinition.action.priority` as `Equivalent`.

code:
  v: PlanDefinition.action.code
display:
  v: code
target:
  code:
    v: PlanDefinition.action.code
  display:
    v: PlanDefinition.action.code
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.code` is mapped to FHIR R4 element `PlanDefinition.action.code` as `SourceIsNarrowerThanTarget`.

code:
  v: PlanDefinition.action.reason
display:
  v: reason
target:
  code:
    v: PlanDefinition.action.reason
  display:
    v: PlanDefinition.action.reason
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.reason` is mapped to FHIR R4 element `PlanDefinition.action.reason` as `Equivalent`. This is different than the clinical evidence documentation, it's an actual business description of the reason for performing the action.

code:
  v: PlanDefinition.action.documentation
display:
  v: documentation
target:
  code:
    v: PlanDefinition.action.documentation
  display:
    v: PlanDefinition.action.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.documentation` is mapped to FHIR R4 element `PlanDefinition.action.documentation` as `Equivalent`.

code:
  v: PlanDefinition.action.goalId
display:
  v: goalId
target:
  code:
    v: PlanDefinition.action.goalId
  display:
    v: PlanDefinition.action.goalId
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.goalId` is mapped to FHIR R4 element `PlanDefinition.action.goalId` as `Equivalent`.

code:
  v: PlanDefinition.action.subject[x]
display:
  v: subject[x]
target:
  code:
    v: PlanDefinition.action.subject[x]
  display:
    v: PlanDefinition.action.subject[x]
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.subject[x]` is mapped to FHIR R4 element `PlanDefinition.action.subject[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.subject[x]` do not cover the following types: canonical. The target context `PlanDefinition.action.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.action`. The subject of an action overrides the subject at a parent action or on the root of the PlanDefinition if specified. In addition, because the subject needs to be resolved during realization, use of subjects in actions (or in the ActivityDefinition referenced by the action) resolves based on the set of subjects supplied in context and by type (i.e. the patient subject would resolve to a resource of type Patient).

code:
  v: PlanDefinition.action.trigger
display:
  v: trigger
target:
  code:
    v: PlanDefinition.action.trigger
  display:
    v: PlanDefinition.action.trigger
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.trigger` is mapped to FHIR R4 element `PlanDefinition.action.trigger` as `Equivalent`.

code:
  v: PlanDefinition.action.condition
display:
  v: condition
target:
  code:
    v: PlanDefinition.action.condition
  display:
    v: PlanDefinition.action.condition
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.condition` is mapped to FHIR R4 element `PlanDefinition.action.condition` as `Equivalent`. When multiple conditions of the same kind are present, the effects are combined using AND semantics, so the overall condition is true only if all the conditions are true.

code:
  v: PlanDefinition.action.condition.kind
display:
  v: kind
target:
  code:
    v: PlanDefinition.action.condition.kind
  display:
    v: PlanDefinition.action.condition.kind
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.condition.kind` is mapped to FHIR R4 element `PlanDefinition.action.condition.kind` as `Equivalent`. Applicability criteria are used to determine immediate applicability when a plan definition is applied to a given context. Start and stop criteria are carried through application and used to describe enter/exit criteria for an action.

code:
  v: PlanDefinition.action.condition.expression
display:
  v: expression
target:
  code:
    v: PlanDefinition.action.condition.expression
  display:
    v: PlanDefinition.action.condition.expression
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.condition.expression` is mapped to FHIR R4 element `PlanDefinition.action.condition.expression` as `Equivalent`. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.

code:
  v: PlanDefinition.action.input
display:
  v: input
target:
  code:
    v: PlanDefinition.action.input
  display:
    v: PlanDefinition.action.input
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.input` is mapped to FHIR R4 element `PlanDefinition.action.input` as `Equivalent`.

code:
  v: PlanDefinition.action.output
display:
  v: output
target:
  code:
    v: PlanDefinition.action.output
  display:
    v: PlanDefinition.action.output
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.output` is mapped to FHIR R4 element `PlanDefinition.action.output` as `Equivalent`.

code:
  v: PlanDefinition.action.relatedAction
display:
  v: relatedAction
target:
  code:
    v: PlanDefinition.action.relatedAction
  display:
    v: PlanDefinition.action.relatedAction
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.relatedAction` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction` as `Equivalent`. When an action depends on multiple actions, the meaning is that all actions are dependencies, rather than that any of the actions are a dependency.

code:
  v: PlanDefinition.action.relatedAction.targetId
display:
  v: targetId
target:
  code:
    v: PlanDefinition.action.relatedAction.actionId
  display:
    v: PlanDefinition.action.relatedAction.actionId
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.relatedAction.targetId` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.actionId` as `Equivalent`.

code:
  v: PlanDefinition.action.relatedAction.relationship
display:
  v: relationship
target:
  code:
    v: PlanDefinition.action.relatedAction.relationship
  display:
    v: PlanDefinition.action.relatedAction.relationship
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.relatedAction.relationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`.

code:
  v: PlanDefinition.action.relatedAction.endRelationship
display:
  v: endRelationship
target:
  code:
    v: PlanDefinition.action.relatedAction.relationship
  display:
    v: PlanDefinition.action.relatedAction.relationship
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.relatedAction.endRelationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`.

code:
  v: PlanDefinition.action.relatedAction.offset[x]
display:
  v: offset[x]
target:
  code:
    v: PlanDefinition.action.relatedAction.offset[x]
  display:
    v: PlanDefinition.action.relatedAction.offset[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.relatedAction.offset[x]` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.offset[x]` as `Equivalent`. The target context `PlanDefinition.action.relatedAction.offset[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.action.relatedAction`.

code:
  v: PlanDefinition.action.timing[x]
display:
  v: timing[x]
target:
  code:
    v: PlanDefinition.action.timing[x]
  display:
    v: PlanDefinition.action.timing[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.timing[x]` is mapped to FHIR R4 element `PlanDefinition.action.timing[x]` as `Equivalent`. The target context `PlanDefinition.action.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.action`. The intent of the timing element is to provide timing when the action should be performed. As a definitional resource, this timing is interpreted as part of an apply operation so that the timing of the result actions in a CarePlan or RequestOrchestration, for example, would be specified by evaluating the timing definition in the context of the apply and setting the resulting timing on the appropriate elements of the target resource. If the timing is an Age, the activity is expected to be performed when the subject is the given Age. When the timing is a Duration, the activity is expected to be performed within the specified duration from the apply. When the timing is a Range, it may be a range of Ages or Durations, providing a range for the expected timing of the resulting activity. When the timing is a Timing, it is establishing a schedule for the timing of the resulting activity.

code:
  v: PlanDefinition.action.participant
display:
  v: participant
target:
  code:
    v: PlanDefinition.action.participant
  display:
    v: PlanDefinition.action.participant
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.participant` is mapped to FHIR R4 element `PlanDefinition.action.participant` as `Equivalent`.

code:
  v: PlanDefinition.action.participant.type
display:
  v: type
target:
  code:
    v: PlanDefinition.action.participant.type
  display:
    v: PlanDefinition.action.participant.type
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.participant.type` is mapped to FHIR R4 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`.

code:
  v: PlanDefinition.action.participant.role
display:
  v: role
target:
  code:
    v: PlanDefinition.action.participant.role
  display:
    v: PlanDefinition.action.participant.role
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.participant.role` is mapped to FHIR R4 element `PlanDefinition.action.participant.role` as `Equivalent`.

code:
  v: PlanDefinition.action.type
display:
  v: type
target:
  code:
    v: PlanDefinition.action.type
  display:
    v: PlanDefinition.action.type
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.type` is mapped to FHIR R4 element `PlanDefinition.action.type` as `Equivalent`.

code:
  v: PlanDefinition.action.groupingBehavior
display:
  v: groupingBehavior
target:
  code:
    v: PlanDefinition.action.groupingBehavior
  display:
    v: PlanDefinition.action.groupingBehavior
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.groupingBehavior` is mapped to FHIR R4 element `PlanDefinition.action.groupingBehavior` as `Equivalent`.

code:
  v: PlanDefinition.action.selectionBehavior
display:
  v: selectionBehavior
target:
  code:
    v: PlanDefinition.action.selectionBehavior
  display:
    v: PlanDefinition.action.selectionBehavior
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.selectionBehavior` is mapped to FHIR R4 element `PlanDefinition.action.selectionBehavior` as `Equivalent`.

code:
  v: PlanDefinition.action.requiredBehavior
display:
  v: requiredBehavior
target:
  code:
    v: PlanDefinition.action.requiredBehavior
  display:
    v: PlanDefinition.action.requiredBehavior
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.requiredBehavior` is mapped to FHIR R4 element `PlanDefinition.action.requiredBehavior` as `Equivalent`.

code:
  v: PlanDefinition.action.precheckBehavior
display:
  v: precheckBehavior
target:
  code:
    v: PlanDefinition.action.precheckBehavior
  display:
    v: PlanDefinition.action.precheckBehavior
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.precheckBehavior` is mapped to FHIR R4 element `PlanDefinition.action.precheckBehavior` as `Equivalent`.

code:
  v: PlanDefinition.action.cardinalityBehavior
display:
  v: cardinalityBehavior
target:
  code:
    v: PlanDefinition.action.cardinalityBehavior
  display:
    v: PlanDefinition.action.cardinalityBehavior
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.cardinalityBehavior` is mapped to FHIR R4 element `PlanDefinition.action.cardinalityBehavior` as `Equivalent`.

code:
  v: PlanDefinition.action.definition[x]
display:
  v: definition[x]
target:
  code:
    v: PlanDefinition.action.definition[x]
  display:
    v: PlanDefinition.action.definition[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.definition[x]` is mapped to FHIR R4 element `PlanDefinition.action.definition[x]` as `Equivalent`. The target context `PlanDefinition.action.definition[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.action`. Note that the definition is optional, and if no definition is specified, a dynamicValue with a root ($this) path can be used to define the entire resource dynamically.

code:
  v: PlanDefinition.action.transform
display:
  v: transform
target:
  code:
    v: PlanDefinition.action.transform
  display:
    v: PlanDefinition.action.transform
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.transform` is mapped to FHIR R4 element `PlanDefinition.action.transform` as `Equivalent`. Note that when a referenced ActivityDefinition also defines a transform, the transform specified here generally takes precedence. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

code:
  v: PlanDefinition.action.dynamicValue
display:
  v: dynamicValue
target:
  code:
    v: PlanDefinition.action.dynamicValue
  display:
    v: PlanDefinition.action.dynamicValue
  equivalence:
    v: wider
  comment:
    v: Element `PlanDefinition.action.dynamicValue` is mapped to FHIR R4 element `PlanDefinition.action.dynamicValue` as `Equivalent`. Dynamic values are applied in the order in which they are defined in the PlanDefinition resource. Note that when dynamic values are also specified by a referenced ActivityDefinition, the dynamicValues from the ActivityDefinition are applied first, followed by the dynamicValues specified here. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

code:
  v: PlanDefinition.action.dynamicValue.path
display:
  v: path
target:
  code:
    v: PlanDefinition.action.dynamicValue.path
  display:
    v: PlanDefinition.action.dynamicValue.path
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.dynamicValue.path` is mapped to FHIR R4 element `PlanDefinition.action.dynamicValue.path` as `Equivalent`. To specify the path to the current action being realized, the %action environment variable is available in this path. For example, to specify the description element of the target action, the path would be %action.description. The path attribute contains a [Simple FHIRPath Subset](https://hl7.org/fhir/fhirpat.html#simple) that allows path traversal, but not calculation.

code:
  v: PlanDefinition.action.dynamicValue.expression
display:
  v: expression
target:
  code:
    v: PlanDefinition.action.dynamicValue.expression
  display:
    v: PlanDefinition.action.dynamicValue.expression
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.dynamicValue.expression` is mapped to FHIR R4 element `PlanDefinition.action.dynamicValue.expression` as `Equivalent`. The expression may be inlined or may be a reference to a named expression within a logic library referenced by the library element.

code:
  v: PlanDefinition.action.action
display:
  v: action
target:
  code:
    v: PlanDefinition.action.action
  display:
    v: PlanDefinition.action.action
  equivalence:
    v: equivalent
  comment:
    v: Element `PlanDefinition.action.action` is mapped to FHIR R4 element `PlanDefinition.action.action` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.subject
  l: extension-PlanDefinition.subject
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.subject[x]
  display:
    v: subject[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.subject[x]` is mapped to FHIR R4 element `PlanDefinition.subject[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.subject[x]` do not cover the following types: canonical. The target context `PlanDefinition.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R5 element `PlanDefinition.subject[x]` with unmapped reference targets: AdministrableProductDefinition, ManufacturedItemDefinition, MedicinalProductDefinition, PackagedProductDefinition, SubstanceDefinition. Source element `PlanDefinition.subject[x]` has unmapped reference types. While the target element `PlanDefinition.subject[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/StructureDefinition/alternate-reference
  l: alternate-reference
target version:
  v: 5.2.0
element:
  code:
    v: PlanDefinition.subject[x]
  display:
    v: subject[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.subject[x]` is mapped to FHIR R4 element `PlanDefinition.subject[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.subject[x]` do not cover the following types: canonical. The target context `PlanDefinition.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R5 element `PlanDefinition.subject[x]` with unmapped reference targets: AdministrableProductDefinition, ManufacturedItemDefinition, MedicinalProductDefinition, PackagedProductDefinition, SubstanceDefinition. Source element `PlanDefinition.subject[x]` has unmapped reference types. While the target element `PlanDefinition.subject[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. Note that the choice of canonical for the subject element was introduced in R4B to support pharmaceutical quality use cases. To ensure as much backwards-compatibility as possible, it is recommended to only use the new canonical type with these use cases.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.goal.target.detail
  l: extension-PlanDefinition.goal.target.detail
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.goal.target.detail[x]
  display:
    v: detail[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.goal.target.detail[x]` is mapped to FHIR R4 element `PlanDefinition.goal.target.detail[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.goal.target.detail[x]` do not cover the following types: boolean, integer, Ratio, string. The target context `PlanDefinition.goal.target.detail[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.goal.target`. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the goal.target.measure defines a coded value.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.actor
  l: extension-PlanDefinition.actor
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.actor
  display:
    v: actor
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.title
  display:
    v: title
  target:
    code:
      v: Extension.extension:title
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.title` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.title` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.description` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.description` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.option
  display:
    v: option
  target:
    code:
      v: Extension.extension:option
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.option` is part of an existing definition because parent element `PlanDefinition.actor` requires a cross-version extension. Element `PlanDefinition.actor.option` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.option.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:option.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.option.type` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.type` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.option.typeCanonical
  display:
    v: typeCanonical
  target:
    code:
      v: Extension.extension:option.extension:typeCanonical
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.option.typeCanonical` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.typeCanonical` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.typeCanonical` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: PlanDefinition.actor.option.typeReference
  display:
    v: typeReference
  target:
    code:
      v: Extension.extension:option.extension:typeReference
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.option.typeReference` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.typeReference` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.typeReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).
element:
  code:
    v: PlanDefinition.actor.option.role
  display:
    v: role
  target:
    code:
      v: Extension.extension:option.extension:role
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.actor.option.role` is part of an existing definition because parent element `PlanDefinition.actor.option` requires a cross-version extension. Element `PlanDefinition.actor.option.role` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.actor.option.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.linkId
  l: extension-PlanDefinition.action.linkId
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.linkId
  display:
    v: linkId
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.action.linkId` has a context of PlanDefinition.action based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.linkId` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.subject
  l: extension-PlanDefinition.action.subject
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.subject[x]
  display:
    v: subject[x]
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.action.subject[x]` is mapped to FHIR R4 element `PlanDefinition.action.subject[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.subject[x]` do not cover the following types: canonical. The target context `PlanDefinition.action.subject[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `PlanDefinition.action`. The subject of an action overrides the subject at a parent action or on the root of the PlanDefinition if specified. In addition, because the subject needs to be resolved during realization, use of subjects in actions (or in the ActivityDefinition referenced by the action) resolves based on the set of subjects supplied in context and by type (i.e. the patient subject would resolve to a resource of type Patient).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.input.title
  l: extension-PlanDefinition.action.input.title
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.input.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.input.title` has a context of PlanDefinition.action.input based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.input.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.input.requirement
  l: extension-PlanDefinition.action.input.requirement
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.input.requirement
  display:
    v: requirement
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.input.requirement` has a context of PlanDefinition.action.input based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.input.requirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.input.relatedData
  l: extension-PlanDefinition.action.input.relatedData
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.input.relatedData
  display:
    v: relatedData
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.input.relatedData` has a context of PlanDefinition.action.input based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.input.relatedData` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The relatedData element allows indicating that an input to a parent action is an input to specific child actions. It also allows the output of one action to be identified as the input to a different action

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.output.title
  l: extension-PlanDefinition.action.output.title
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.output.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.output.title` has a context of PlanDefinition.action.output based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.output.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.output.requirement
  l: extension-PlanDefinition.action.output.requirement
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.output.requirement
  display:
    v: requirement
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.output.requirement` has a context of PlanDefinition.action.output based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.output.requirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.output.relatedData
  l: extension-PlanDefinition.action.output.relatedData
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.output.relatedData
  display:
    v: relatedData
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.output.relatedData` has a context of PlanDefinition.action.output based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.output.relatedData` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The relatedData element allows indicating that the output of child action is also the output of a parent action. It also allows the input of one action to be identified as the output of a different action

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.location
  l: extension-PlanDefinition.action.location
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.location
  display:
    v: location
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.location` has a context of PlanDefinition.action based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.location` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May reference a specific clinical location or may just identify a type of location.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.participant.actorId
  l: extension-PlanDefinition.action.participant.actorId
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.participant.actorId
  display:
    v: actorId
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.participant.actorId` has a context of PlanDefinition.action.participant based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.participant.actorId` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.participant.type
  l: extension-PlanDefinition.action.participant.type
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.participant.type
  display:
    v: type
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `PlanDefinition.action.participant.type` is mapped to FHIR R4 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`.

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.participant.typeCanonical
  l: extension-PlanDefinition.action.participant.typeCanonical
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.participant.typeCanonical
  display:
    v: typeCanonical
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.participant.typeCanonical` has a context of PlanDefinition.action.participant based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.participant.typeCanonical` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.participant.typeReference
  l: extension-PlanDefinition.action.participant.typeReference
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.participant.typeReference
  display:
    v: typeReference
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.participant.typeReference` has a context of PlanDefinition.action.participant based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.participant.typeReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.action.participant.function
  l: extension-PlanDefinition.action.participant.function
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.action.participant.function
  display:
    v: function
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.action.participant.function` has a context of PlanDefinition.action.participant based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.participant.function` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/PlanDefinition
  l: PlanDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-PlanDefinition.asNeeded
  l: extension-PlanDefinition.asNeeded
target version:
  v: 0.1.0
element:
  code:
    v: PlanDefinition.asNeeded[x]
  display:
    v: asNeeded[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `PlanDefinition.asNeeded[x]` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.asNeeded[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).