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 HTML5 for information about the relationship between xml:lang and the html lang attribute). PlanDefinition.text (text) is equivalent to PlanDefinition.text 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. PlanDefinition.contained (contained) is equivalent to PlanDefinition.contained 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. PlanDefinition.url (url) is equivalent to PlanDefinition.url 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. PlanDefinition.identifier (identifier) is equivalent to PlanDefinition.identifier 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. PlanDefinition.version (version) is equivalent to PlanDefinition.version 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). PlanDefinition.name (name) is equivalent to PlanDefinition.name 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. PlanDefinition.title (title) is equivalent to PlanDefinition.title 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. PlanDefinition.subtitle (subtitle) is equivalent to PlanDefinition.subtitle Element `PlanDefinition.subtitle` is mapped to FHIR R4 element `PlanDefinition.subtitle` as `Equivalent`. PlanDefinition.type (type) is equivalent to PlanDefinition.type Element `PlanDefinition.type` is mapped to FHIR R4 element `PlanDefinition.type` as `Equivalent`. PlanDefinition.status (status) is equivalent to PlanDefinition.status 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). PlanDefinition.experimental (experimental) is equivalent to PlanDefinition.experimental 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. PlanDefinition.subject[x] (subject[x]) maps to wider concept PlanDefinition.subject[x] 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. PlanDefinition.date (date) is equivalent to PlanDefinition.date 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). PlanDefinition.publisher (publisher) is equivalent to PlanDefinition.publisher 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. PlanDefinition.contact (contact) is equivalent to PlanDefinition.contact 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). PlanDefinition.description (description) is equivalent to PlanDefinition.description 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). PlanDefinition.useContext (useContext) is equivalent to PlanDefinition.useContext 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. PlanDefinition.jurisdiction (jurisdiction) is equivalent to PlanDefinition.jurisdiction 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.) PlanDefinition.purpose (purpose) is equivalent to PlanDefinition.purpose 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. PlanDefinition.usage (usage) is equivalent to PlanDefinition.usage Element `PlanDefinition.usage` is mapped to FHIR R4 element `PlanDefinition.usage` as `Equivalent`. PlanDefinition.copyright (copyright) is equivalent to PlanDefinition.copyright 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. PlanDefinition.approvalDate (approvalDate) is equivalent to PlanDefinition.approvalDate 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). PlanDefinition.lastReviewDate (lastReviewDate) is equivalent to PlanDefinition.lastReviewDate 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). PlanDefinition.effectivePeriod (effectivePeriod) is equivalent to PlanDefinition.effectivePeriod 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). PlanDefinition.topic (topic) is equivalent to PlanDefinition.topic 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) PlanDefinition.author (author) is equivalent to PlanDefinition.author Element `PlanDefinition.author` is mapped to FHIR R4 element `PlanDefinition.author` as `Equivalent`. PlanDefinition.editor (editor) is equivalent to PlanDefinition.editor Element `PlanDefinition.editor` is mapped to FHIR R4 element `PlanDefinition.editor` as `Equivalent`. PlanDefinition.reviewer (reviewer) is equivalent to PlanDefinition.reviewer 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). PlanDefinition.endorser (endorser) is equivalent to PlanDefinition.endorser 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). PlanDefinition.relatedArtifact (relatedArtifact) is equivalent to PlanDefinition.relatedArtifact 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. PlanDefinition.library (library) is equivalent to PlanDefinition.library Element `PlanDefinition.library` is mapped to FHIR R4 element `PlanDefinition.library` as `Equivalent`. PlanDefinition.goal (goal) maps to wider concept PlanDefinition.goal Element `PlanDefinition.goal` is mapped to FHIR R4 element `PlanDefinition.goal` as `Equivalent`. PlanDefinition.goal.category (category) is equivalent to PlanDefinition.goal.category Element `PlanDefinition.goal.category` is mapped to FHIR R4 element `PlanDefinition.goal.category` as `Equivalent`. PlanDefinition.goal.description (description) is equivalent to PlanDefinition.goal.description Element `PlanDefinition.goal.description` is mapped to FHIR R4 element `PlanDefinition.goal.description` as `Equivalent`. If no code is available, use CodeableConcept.text. PlanDefinition.goal.priority (priority) is equivalent to PlanDefinition.goal.priority Element `PlanDefinition.goal.priority` is mapped to FHIR R4 element `PlanDefinition.goal.priority` as `Equivalent`. PlanDefinition.goal.start (start) is equivalent to PlanDefinition.goal.start Element `PlanDefinition.goal.start` is mapped to FHIR R4 element `PlanDefinition.goal.start` as `Equivalent`. PlanDefinition.goal.addresses (addresses) is equivalent to PlanDefinition.goal.addresses Element `PlanDefinition.goal.addresses` is mapped to FHIR R4 element `PlanDefinition.goal.addresses` as `Equivalent`. PlanDefinition.goal.documentation (documentation) is equivalent to PlanDefinition.goal.documentation Element `PlanDefinition.goal.documentation` is mapped to FHIR R4 element `PlanDefinition.goal.documentation` as `Equivalent`. PlanDefinition.goal.target (target) maps to wider concept PlanDefinition.goal.target Element `PlanDefinition.goal.target` is mapped to FHIR R4 element `PlanDefinition.goal.target` as `Equivalent`. PlanDefinition.goal.target.measure (measure) is equivalent to PlanDefinition.goal.target.measure Element `PlanDefinition.goal.target.measure` is mapped to FHIR R4 element `PlanDefinition.goal.target.measure` as `Equivalent`. PlanDefinition.goal.target.detail[x] (detail[x]) maps to wider concept PlanDefinition.goal.target.detail[x] 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. PlanDefinition.goal.target.due (due) is equivalent to PlanDefinition.goal.target.due Element `PlanDefinition.goal.target.due` is mapped to FHIR R4 element `PlanDefinition.goal.target.due` as `Equivalent`. PlanDefinition.action (action) maps to wider concept PlanDefinition.action 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. PlanDefinition.action.prefix (prefix) is equivalent to PlanDefinition.action.prefix Element `PlanDefinition.action.prefix` is mapped to FHIR R4 element `PlanDefinition.action.prefix` as `Equivalent`. PlanDefinition.action.title (title) is equivalent to PlanDefinition.action.title Element `PlanDefinition.action.title` is mapped to FHIR R4 element `PlanDefinition.action.title` as `Equivalent`. PlanDefinition.action.description (description) is equivalent to PlanDefinition.action.description Element `PlanDefinition.action.description` is mapped to FHIR R4 element `PlanDefinition.action.description` as `Equivalent`. PlanDefinition.action.textEquivalent (textEquivalent) is equivalent to PlanDefinition.action.textEquivalent Element `PlanDefinition.action.textEquivalent` is mapped to FHIR R4 element `PlanDefinition.action.textEquivalent` as `Equivalent`. PlanDefinition.action.priority (priority) is equivalent to PlanDefinition.action.priority Element `PlanDefinition.action.priority` is mapped to FHIR R4 element `PlanDefinition.action.priority` as `Equivalent`. PlanDefinition.action.code (code) is equivalent to PlanDefinition.action.code Element `PlanDefinition.action.code` is mapped to FHIR R4 element `PlanDefinition.action.code` as `SourceIsNarrowerThanTarget`. PlanDefinition.action.reason (reason) is equivalent to PlanDefinition.action.reason 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. PlanDefinition.action.documentation (documentation) is equivalent to PlanDefinition.action.documentation Element `PlanDefinition.action.documentation` is mapped to FHIR R4 element `PlanDefinition.action.documentation` as `Equivalent`. PlanDefinition.action.goalId (goalId) is equivalent to PlanDefinition.action.goalId Element `PlanDefinition.action.goalId` is mapped to FHIR R4 element `PlanDefinition.action.goalId` as `Equivalent`. PlanDefinition.action.subject[x] (subject[x]) maps to wider concept PlanDefinition.action.subject[x] 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). PlanDefinition.action.trigger (trigger) is equivalent to PlanDefinition.action.trigger Element `PlanDefinition.action.trigger` is mapped to FHIR R4 element `PlanDefinition.action.trigger` as `Equivalent`. PlanDefinition.action.condition (condition) maps to wider concept PlanDefinition.action.condition 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. PlanDefinition.action.condition.kind (kind) is equivalent to PlanDefinition.action.condition.kind 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. PlanDefinition.action.condition.expression (expression) is equivalent to PlanDefinition.action.condition.expression 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. PlanDefinition.action.input (input) maps to wider concept PlanDefinition.action.input Element `PlanDefinition.action.input` is mapped to FHIR R4 element `PlanDefinition.action.input` as `Equivalent`. PlanDefinition.action.output (output) maps to wider concept PlanDefinition.action.output Element `PlanDefinition.action.output` is mapped to FHIR R4 element `PlanDefinition.action.output` as `Equivalent`. PlanDefinition.action.relatedAction (relatedAction) maps to wider concept PlanDefinition.action.relatedAction 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. PlanDefinition.action.relatedAction.targetId (targetId) is equivalent to PlanDefinition.action.relatedAction.actionId Element `PlanDefinition.action.relatedAction.targetId` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.actionId` as `Equivalent`. PlanDefinition.action.relatedAction.relationship (relationship) is equivalent to PlanDefinition.action.relatedAction.relationship Element `PlanDefinition.action.relatedAction.relationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`. PlanDefinition.action.relatedAction.endRelationship (endRelationship) is equivalent to PlanDefinition.action.relatedAction.relationship Element `PlanDefinition.action.relatedAction.endRelationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`. PlanDefinition.action.relatedAction.offset[x] (offset[x]) is equivalent to PlanDefinition.action.relatedAction.offset[x] 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`. PlanDefinition.action.timing[x] (timing[x]) is equivalent to PlanDefinition.action.timing[x] 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. PlanDefinition.action.participant (participant) maps to wider concept PlanDefinition.action.participant Element `PlanDefinition.action.participant` is mapped to FHIR R4 element `PlanDefinition.action.participant` as `Equivalent`. PlanDefinition.action.participant.type (type) maps to wider concept PlanDefinition.action.participant.type Element `PlanDefinition.action.participant.type` is mapped to FHIR R4 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`. PlanDefinition.action.participant.role (role) is equivalent to PlanDefinition.action.participant.role Element `PlanDefinition.action.participant.role` is mapped to FHIR R4 element `PlanDefinition.action.participant.role` as `Equivalent`. PlanDefinition.action.type (type) is equivalent to PlanDefinition.action.type Element `PlanDefinition.action.type` is mapped to FHIR R4 element `PlanDefinition.action.type` as `Equivalent`. PlanDefinition.action.groupingBehavior (groupingBehavior) is equivalent to PlanDefinition.action.groupingBehavior Element `PlanDefinition.action.groupingBehavior` is mapped to FHIR R4 element `PlanDefinition.action.groupingBehavior` as `Equivalent`. PlanDefinition.action.selectionBehavior (selectionBehavior) is equivalent to PlanDefinition.action.selectionBehavior Element `PlanDefinition.action.selectionBehavior` is mapped to FHIR R4 element `PlanDefinition.action.selectionBehavior` as `Equivalent`. PlanDefinition.action.requiredBehavior (requiredBehavior) is equivalent to PlanDefinition.action.requiredBehavior Element `PlanDefinition.action.requiredBehavior` is mapped to FHIR R4 element `PlanDefinition.action.requiredBehavior` as `Equivalent`. PlanDefinition.action.precheckBehavior (precheckBehavior) is equivalent to PlanDefinition.action.precheckBehavior Element `PlanDefinition.action.precheckBehavior` is mapped to FHIR R4 element `PlanDefinition.action.precheckBehavior` as `Equivalent`. PlanDefinition.action.cardinalityBehavior (cardinalityBehavior) is equivalent to PlanDefinition.action.cardinalityBehavior Element `PlanDefinition.action.cardinalityBehavior` is mapped to FHIR R4 element `PlanDefinition.action.cardinalityBehavior` as `Equivalent`. PlanDefinition.action.definition[x] (definition[x]) is equivalent to PlanDefinition.action.definition[x] 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. PlanDefinition.action.transform (transform) is equivalent to PlanDefinition.action.transform 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. PlanDefinition.action.dynamicValue (dynamicValue) maps to wider concept PlanDefinition.action.dynamicValue 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. PlanDefinition.action.dynamicValue.path (path) is equivalent to PlanDefinition.action.dynamicValue.path 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. PlanDefinition.action.dynamicValue.expression (expression) is equivalent to PlanDefinition.action.dynamicValue.expression 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. PlanDefinition.action.action (action) is equivalent to PlanDefinition.action.action Element `PlanDefinition.action.action` is mapped to FHIR R4 element `PlanDefinition.action.action` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: subject additional typesversion: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.subject[x] (subject[x]) is equivalent to Extension (R5: subject additional types) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to Alternate Referenceversion: 5.2.0) Source Code Relationship Target Code Comment PlanDefinition.subject[x] (subject[x]) is equivalent to Extension (Alternative reference (target type is wrong)) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: detail additional typesversion: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.goal.target.detail[x] (detail[x]) is equivalent to Extension (R5: detail additional types) 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. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Actors within the plan (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.actor (actor) maps to wider concept Extension (R5: Actors within the plan (new)) 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). PlanDefinition.actor.title (title) maps to wider concept Extension.extension:title (R5: User-visible title (new)) 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). PlanDefinition.actor.description (description) maps to wider concept Extension.extension:description (R5: Describes the actor (new)) 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). PlanDefinition.actor.option (option) maps to wider concept Extension.extension:option (R5: Who or what can be this actor (new)) 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). PlanDefinition.actor.option.type (type) maps to wider concept Extension.extension:option.extension:type (R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson (new)) 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). PlanDefinition.actor.option.typeCanonical (typeCanonical) maps to wider concept Extension.extension:option.extension:typeCanonical (R5: Who or what can participate (new)) 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). PlanDefinition.actor.option.typeReference (typeReference) maps to wider concept Extension.extension:option.extension:typeReference (R5: Who or what can participate (new)) 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). PlanDefinition.actor.option.role (role) maps to wider concept Extension.extension:option.extension:role (R5: E.g. Nurse, Surgeon, Parent (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Unique id for the action in the PlanDefinition (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.linkId (linkId) is equivalent to Extension (R5: Unique id for the action in the PlanDefinition (new)) 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). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: subject additional typesversion: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.subject[x] (subject[x]) is equivalent to Extension (R5: subject additional types) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: User-visible title (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.input.title (title) maps to wider concept Extension (R5: User-visible title (new)) 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). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: What data is provided (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.input.requirement (requirement) maps to wider concept Extension (R5: What data is provided (new)) 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). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: What data is provided (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.input.relatedData (relatedData) maps to wider concept Extension (R5: What data is provided (new)) 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 Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: User-visible title (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.output.title (title) maps to wider concept Extension (R5: User-visible title (new)) 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). Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: What data is provided (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.output.requirement (requirement) maps to wider concept Extension (R5: What data is provided (new)) 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). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: What data is provided (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.output.relatedData (relatedData) maps to wider concept Extension (R5: What data is provided (new)) 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 Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Where it should happen (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.location (location) maps to wider concept Extension (R5: Where it should happen (new)) 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. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: What actor (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.participant.actorId (actorId) maps to wider concept Extension (R5: What actor (new)) 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). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedpersonversion: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.participant.type (type) is equivalent to Extension (R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson) Element `PlanDefinition.action.participant.type` is mapped to FHIR R4 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`. Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Who or what can participate (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.participant.typeCanonical (typeCanonical) maps to wider concept Extension (R5: Who or what can participate (new)) 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). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Who or what can participate (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.participant.typeReference (typeReference) maps to wider concept Extension (R5: Who or what can participate (new)) 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). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: E.g. Author, Reviewer, Witness, etc (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.action.participant.function (function) maps to wider concept Extension (R5: E.g. Author, Reviewer, Witness, etc (new)) 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). Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|5.0.0 to R5: Preconditions for service (new)version: 0.1.0) Source Code Relationship Target Code Comment PlanDefinition.asNeeded[x] (asNeeded[x]) maps to wider concept Extension (R5: Preconditions for service (new)) 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).
Cross-version mapping for FHIR R5 PlanDefinition to FHIR R4 PlanDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR R5 PlanDefinition to FHIR R4.
Element `PlanDefinition.meta` is mapped to FHIR R4 element `PlanDefinition.meta` as `Equivalent`.
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 `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 `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 `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 `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 `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 `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).
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.
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.
Element `PlanDefinition.subtitle` is mapped to FHIR R4 element `PlanDefinition.subtitle` as `Equivalent`.
Element `PlanDefinition.type` is mapped to FHIR R4 element `PlanDefinition.type` as `Equivalent`.
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).
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.
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.
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).
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.
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).
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).
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.
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.)
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.
Element `PlanDefinition.usage` is mapped to FHIR R4 element `PlanDefinition.usage` as `Equivalent`.
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.
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).
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).
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).
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)
Element `PlanDefinition.author` is mapped to FHIR R4 element `PlanDefinition.author` as `Equivalent`.
Element `PlanDefinition.editor` is mapped to FHIR R4 element `PlanDefinition.editor` as `Equivalent`.
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).
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).
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.
Element `PlanDefinition.library` is mapped to FHIR R4 element `PlanDefinition.library` as `Equivalent`.
Element `PlanDefinition.goal` is mapped to FHIR R4 element `PlanDefinition.goal` as `Equivalent`.
Element `PlanDefinition.goal.category` is mapped to FHIR R4 element `PlanDefinition.goal.category` as `Equivalent`.
Element `PlanDefinition.goal.description` is mapped to FHIR R4 element `PlanDefinition.goal.description` as `Equivalent`. If no code is available, use CodeableConcept.text.
Element `PlanDefinition.goal.priority` is mapped to FHIR R4 element `PlanDefinition.goal.priority` as `Equivalent`.
Element `PlanDefinition.goal.start` is mapped to FHIR R4 element `PlanDefinition.goal.start` as `Equivalent`.
Element `PlanDefinition.goal.addresses` is mapped to FHIR R4 element `PlanDefinition.goal.addresses` as `Equivalent`.
Element `PlanDefinition.goal.documentation` is mapped to FHIR R4 element `PlanDefinition.goal.documentation` as `Equivalent`.
Element `PlanDefinition.goal.target` is mapped to FHIR R4 element `PlanDefinition.goal.target` as `Equivalent`.
Element `PlanDefinition.goal.target.measure` is mapped to FHIR R4 element `PlanDefinition.goal.target.measure` as `Equivalent`.
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.
Element `PlanDefinition.goal.target.due` is mapped to FHIR R4 element `PlanDefinition.goal.target.due` as `Equivalent`.
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.
Element `PlanDefinition.action.prefix` is mapped to FHIR R4 element `PlanDefinition.action.prefix` as `Equivalent`.
Element `PlanDefinition.action.title` is mapped to FHIR R4 element `PlanDefinition.action.title` as `Equivalent`.
Element `PlanDefinition.action.description` is mapped to FHIR R4 element `PlanDefinition.action.description` as `Equivalent`.
Element `PlanDefinition.action.textEquivalent` is mapped to FHIR R4 element `PlanDefinition.action.textEquivalent` as `Equivalent`.
Element `PlanDefinition.action.priority` is mapped to FHIR R4 element `PlanDefinition.action.priority` as `Equivalent`.
Element `PlanDefinition.action.code` is mapped to FHIR R4 element `PlanDefinition.action.code` as `SourceIsNarrowerThanTarget`.
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.
Element `PlanDefinition.action.documentation` is mapped to FHIR R4 element `PlanDefinition.action.documentation` as `Equivalent`.
Element `PlanDefinition.action.goalId` is mapped to FHIR R4 element `PlanDefinition.action.goalId` as `Equivalent`.
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).
Element `PlanDefinition.action.trigger` is mapped to FHIR R4 element `PlanDefinition.action.trigger` as `Equivalent`.
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.
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.
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.
Element `PlanDefinition.action.input` is mapped to FHIR R4 element `PlanDefinition.action.input` as `Equivalent`.
Element `PlanDefinition.action.output` is mapped to FHIR R4 element `PlanDefinition.action.output` as `Equivalent`.
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.
Element `PlanDefinition.action.relatedAction.targetId` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.actionId` as `Equivalent`.
Element `PlanDefinition.action.relatedAction.relationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`.
Element `PlanDefinition.action.relatedAction.endRelationship` is mapped to FHIR R4 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`.
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`.
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.
Element `PlanDefinition.action.participant` is mapped to FHIR R4 element `PlanDefinition.action.participant` as `Equivalent`.
Element `PlanDefinition.action.participant.type` is mapped to FHIR R4 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`.
Element `PlanDefinition.action.participant.role` is mapped to FHIR R4 element `PlanDefinition.action.participant.role` as `Equivalent`.
Element `PlanDefinition.action.type` is mapped to FHIR R4 element `PlanDefinition.action.type` as `Equivalent`.
Element `PlanDefinition.action.groupingBehavior` is mapped to FHIR R4 element `PlanDefinition.action.groupingBehavior` as `Equivalent`.
Element `PlanDefinition.action.selectionBehavior` is mapped to FHIR R4 element `PlanDefinition.action.selectionBehavior` as `Equivalent`.
Element `PlanDefinition.action.requiredBehavior` is mapped to FHIR R4 element `PlanDefinition.action.requiredBehavior` as `Equivalent`.
Element `PlanDefinition.action.precheckBehavior` is mapped to FHIR R4 element `PlanDefinition.action.precheckBehavior` as `Equivalent`.
Element `PlanDefinition.action.cardinalityBehavior` is mapped to FHIR R4 element `PlanDefinition.action.cardinalityBehavior` as `Equivalent`.
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.
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.
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.
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.
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.
Element `PlanDefinition.action.action` is mapped to FHIR R4 element `PlanDefinition.action.action` as `Equivalent`.
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 `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 `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 `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 `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 `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 `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 `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).
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).
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).
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).
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
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).
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).
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
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.
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).
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).
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).
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).
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).