Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR STU3 - Downloaded Version null See the Directory of published versions

ConceptMap: R4PlanDefinitionElementMapToR3

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-PlanDefinition-element-map-to-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4PlanDefinitionElementMapToR3

This ConceptMap represents cross-version mappings for elements from a FHIR R4 PlanDefinition to FHIR STU3.

Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/3.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to http://hl7.org/fhir/StructureDefinition/PlanDefinition|3.0.2

Source CodeRelationshipTarget CodeComment
PlanDefinition.meta (meta)is equivalent toPlanDefinition.metaElement `PlanDefinition.meta` is mapped to FHIR STU3 element `PlanDefinition.meta` as `Equivalent`.
PlanDefinition.implicitRules (implicitRules)is equivalent toPlanDefinition.implicitRulesElement `PlanDefinition.implicitRules` is mapped to FHIR STU3 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 it's narrative along with other profiles, value sets, etc.
PlanDefinition.language (language)is equivalent toPlanDefinition.languageElement `PlanDefinition.language` is mapped to FHIR STU3 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 toPlanDefinition.textElement `PlanDefinition.text` is mapped to FHIR STU3 element `PlanDefinition.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
PlanDefinition.contained (contained)is equivalent toPlanDefinition.containedElement `PlanDefinition.contained` is mapped to FHIR STU3 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 toPlanDefinition.urlElement `PlanDefinition.url` is mapped to FHIR STU3 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 toPlanDefinition.identifierElement `PlanDefinition.identifier` is mapped to FHIR STU3 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 toPlanDefinition.versionElement `PlanDefinition.version` is mapped to FHIR STU3 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].
PlanDefinition.name (name)is equivalent toPlanDefinition.nameElement `PlanDefinition.name` is mapped to FHIR STU3 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 toPlanDefinition.titleElement `PlanDefinition.title` is mapped to FHIR STU3 element `PlanDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
PlanDefinition.type (type)is equivalent toPlanDefinition.typeElement `PlanDefinition.type` is mapped to FHIR STU3 element `PlanDefinition.type` as `Equivalent`.
PlanDefinition.status (status)is equivalent toPlanDefinition.statusElement `PlanDefinition.status` is mapped to FHIR STU3 element `PlanDefinition.status` as `Equivalent`. Allows filtering of plan definitions that are appropriate for use versus not.
PlanDefinition.experimental (experimental)is equivalent toPlanDefinition.experimentalElement `PlanDefinition.experimental` is mapped to FHIR STU3 element `PlanDefinition.experimental` as `Equivalent`. Allows filtering of plan definitions that are appropriate for use versus not.
PlanDefinition.date (date)is equivalent toPlanDefinition.dateElement `PlanDefinition.date` is mapped to FHIR STU3 element `PlanDefinition.date` as `Equivalent`. 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.
PlanDefinition.publisher (publisher)is equivalent toPlanDefinition.publisherElement `PlanDefinition.publisher` is mapped to FHIR STU3 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 toPlanDefinition.contactElement `PlanDefinition.contact` is mapped to FHIR STU3 element `PlanDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
PlanDefinition.description (description)is equivalent toPlanDefinition.descriptionElement `PlanDefinition.description` is mapped to FHIR STU3 element `PlanDefinition.description` as `Equivalent`. This description can be used to capture details such as why the plan definition was built, 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 toPlanDefinition.useContextElement `PlanDefinition.useContext` is mapped to FHIR STU3 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 toPlanDefinition.jurisdictionElement `PlanDefinition.jurisdiction` is mapped to FHIR STU3 element `PlanDefinition.jurisdiction` as `Equivalent`. It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended.
PlanDefinition.purpose (purpose)is equivalent toPlanDefinition.purposeElement `PlanDefinition.purpose` is mapped to FHIR STU3 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 toPlanDefinition.usageElement `PlanDefinition.usage` is mapped to FHIR STU3 element `PlanDefinition.usage` as `Equivalent`.
PlanDefinition.copyright (copyright)is equivalent toPlanDefinition.copyrightElement `PlanDefinition.copyright` is mapped to FHIR STU3 element `PlanDefinition.copyright` as `Equivalent`.
PlanDefinition.approvalDate (approvalDate)is equivalent toPlanDefinition.approvalDateElement `PlanDefinition.approvalDate` is mapped to FHIR STU3 element `PlanDefinition.approvalDate` as `Equivalent`. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.
PlanDefinition.lastReviewDate (lastReviewDate)is equivalent toPlanDefinition.lastReviewDateElement `PlanDefinition.lastReviewDate` is mapped to FHIR STU3 element `PlanDefinition.lastReviewDate` as `Equivalent`. If specified, this date follows the original approval date.
PlanDefinition.effectivePeriod (effectivePeriod)is equivalent toPlanDefinition.effectivePeriodElement `PlanDefinition.effectivePeriod` is mapped to FHIR STU3 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 measure intended to be used for the year 2016 might be published in 2015.
PlanDefinition.topic (topic)is equivalent toPlanDefinition.topicElement `PlanDefinition.topic` is mapped to FHIR STU3 element `PlanDefinition.topic` as `Equivalent`.
PlanDefinition.author (author)maps to wider conceptPlanDefinition.contributorElement `PlanDefinition.author` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.author` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.author` do not cover the following types based on type expansion: name, telecom.
PlanDefinition.editor (editor)maps to wider conceptPlanDefinition.contributorElement `PlanDefinition.editor` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.editor` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.editor` do not cover the following types based on type expansion: name, telecom.
PlanDefinition.reviewer (reviewer)maps to wider conceptPlanDefinition.contributorElement `PlanDefinition.reviewer` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.reviewer` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.reviewer` do not cover the following types based on type expansion: name, telecom.
PlanDefinition.endorser (endorser)maps to wider conceptPlanDefinition.contributorElement `PlanDefinition.endorser` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.endorser` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.endorser` do not cover the following types based on type expansion: name, telecom.
PlanDefinition.relatedArtifact (relatedArtifact)is equivalent toPlanDefinition.relatedArtifactElement `PlanDefinition.relatedArtifact` is mapped to FHIR STU3 element `PlanDefinition.relatedArtifact` as `Equivalent`. Each related artifact is either an attachment, or a reference to another resource, but not both.
PlanDefinition.library (library)maps to wider conceptPlanDefinition.libraryElement `PlanDefinition.library` is mapped to FHIR STU3 element `PlanDefinition.library` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.library` do not cover the following types: canonical. The mappings for `PlanDefinition.library` do not cover the following types based on type expansion: value.
PlanDefinition.goal (goal)maps to wider conceptPlanDefinition.goalElement `PlanDefinition.goal` is mapped to FHIR STU3 element `PlanDefinition.goal` as `Equivalent`.
PlanDefinition.goal.category (category)is equivalent toPlanDefinition.goal.categoryElement `PlanDefinition.goal.category` is mapped to FHIR STU3 element `PlanDefinition.goal.category` as `Equivalent`.
PlanDefinition.goal.description (description)is equivalent toPlanDefinition.goal.descriptionElement `PlanDefinition.goal.description` is mapped to FHIR STU3 element `PlanDefinition.goal.description` as `Equivalent`. If no code is available, use CodeableConcept.text.
PlanDefinition.goal.priority (priority)is equivalent toPlanDefinition.goal.priorityElement `PlanDefinition.goal.priority` is mapped to FHIR STU3 element `PlanDefinition.goal.priority` as `Equivalent`.
PlanDefinition.goal.start (start)is equivalent toPlanDefinition.goal.startElement `PlanDefinition.goal.start` is mapped to FHIR STU3 element `PlanDefinition.goal.start` as `Equivalent`.
PlanDefinition.goal.addresses (addresses)is equivalent toPlanDefinition.goal.addressesElement `PlanDefinition.goal.addresses` is mapped to FHIR STU3 element `PlanDefinition.goal.addresses` as `Equivalent`.
PlanDefinition.goal.documentation (documentation)is equivalent toPlanDefinition.goal.documentationElement `PlanDefinition.goal.documentation` is mapped to FHIR STU3 element `PlanDefinition.goal.documentation` as `Equivalent`.
PlanDefinition.goal.target (target)maps to wider conceptPlanDefinition.goal.targetElement `PlanDefinition.goal.target` is mapped to FHIR STU3 element `PlanDefinition.goal.target` as `Equivalent`.
PlanDefinition.goal.target.measure (measure)is equivalent toPlanDefinition.goal.target.measureElement `PlanDefinition.goal.target.measure` is mapped to FHIR STU3 element `PlanDefinition.goal.target.measure` as `Equivalent`.
PlanDefinition.goal.target.detail[x] (detail[x])is equivalent toPlanDefinition.goal.target.detail[x]Element `PlanDefinition.goal.target.detail[x]` is mapped to FHIR STU3 element `PlanDefinition.goal.target.detail[x]` as `Equivalent`. 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`.
PlanDefinition.goal.target.due (due)is equivalent toPlanDefinition.goal.target.dueElement `PlanDefinition.goal.target.due` is mapped to FHIR STU3 element `PlanDefinition.goal.target.due` as `Equivalent`.
PlanDefinition.action (action)maps to wider conceptPlanDefinition.actionElement `PlanDefinition.action` is mapped to FHIR STU3 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 toPlanDefinition.action.labelElement `PlanDefinition.action.prefix` is mapped to FHIR STU3 element `PlanDefinition.action.label` as `Equivalent`.
PlanDefinition.action.title (title)is equivalent toPlanDefinition.action.titleElement `PlanDefinition.action.title` is mapped to FHIR STU3 element `PlanDefinition.action.title` as `Equivalent`.
PlanDefinition.action.description (description)is equivalent toPlanDefinition.action.descriptionElement `PlanDefinition.action.description` is mapped to FHIR STU3 element `PlanDefinition.action.description` as `Equivalent`.
PlanDefinition.action.textEquivalent (textEquivalent)is equivalent toPlanDefinition.action.textEquivalentElement `PlanDefinition.action.textEquivalent` is mapped to FHIR STU3 element `PlanDefinition.action.textEquivalent` as `Equivalent`.
PlanDefinition.action.code (code)is equivalent toPlanDefinition.action.codeElement `PlanDefinition.action.code` is mapped to FHIR STU3 element `PlanDefinition.action.code` as `Equivalent`.
PlanDefinition.action.reason (reason)is equivalent toPlanDefinition.action.reasonElement `PlanDefinition.action.reason` is mapped to FHIR STU3 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 toPlanDefinition.action.documentationElement `PlanDefinition.action.documentation` is mapped to FHIR STU3 element `PlanDefinition.action.documentation` as `Equivalent`.
PlanDefinition.action.goalId (goalId)is equivalent toPlanDefinition.action.goalIdElement `PlanDefinition.action.goalId` is mapped to FHIR STU3 element `PlanDefinition.action.goalId` as `Equivalent`.
PlanDefinition.action.trigger (trigger)is equivalent toPlanDefinition.action.triggerDefinitionElement `PlanDefinition.action.trigger` is mapped to FHIR STU3 element `PlanDefinition.action.triggerDefinition` as `Equivalent`.
PlanDefinition.action.condition (condition)maps to wider conceptPlanDefinition.action.conditionElement `PlanDefinition.action.condition` is mapped to FHIR STU3 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 toPlanDefinition.action.condition.kindElement `PlanDefinition.action.condition.kind` is mapped to FHIR STU3 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 toPlanDefinition.action.condition.expressionElement `PlanDefinition.action.condition.expression` is mapped to FHIR STU3 element `PlanDefinition.action.condition.expression` as `SourceIsBroaderThanTarget`. 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)is equivalent toPlanDefinition.action.inputElement `PlanDefinition.action.input` is mapped to FHIR STU3 element `PlanDefinition.action.input` as `Equivalent`.
PlanDefinition.action.output (output)is equivalent toPlanDefinition.action.outputElement `PlanDefinition.action.output` is mapped to FHIR STU3 element `PlanDefinition.action.output` as `Equivalent`.
PlanDefinition.action.relatedAction (relatedAction)maps to wider conceptPlanDefinition.action.relatedActionElement `PlanDefinition.action.relatedAction` is mapped to FHIR STU3 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.actionId (actionId)is equivalent toPlanDefinition.action.relatedAction.actionIdElement `PlanDefinition.action.relatedAction.actionId` is mapped to FHIR STU3 element `PlanDefinition.action.relatedAction.actionId` as `Equivalent`.
PlanDefinition.action.relatedAction.relationship (relationship)is equivalent toPlanDefinition.action.relatedAction.relationshipElement `PlanDefinition.action.relatedAction.relationship` is mapped to FHIR STU3 element `PlanDefinition.action.relatedAction.relationship` as `Equivalent`.
PlanDefinition.action.relatedAction.offset[x] (offset[x])is equivalent toPlanDefinition.action.relatedAction.offset[x]Element `PlanDefinition.action.relatedAction.offset[x]` is mapped to FHIR STU3 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])maps to wider conceptPlanDefinition.action.timing[x]Element `PlanDefinition.action.timing[x]` is mapped to FHIR STU3 element `PlanDefinition.action.timing[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.timing[x]` do not cover the following types: Age. 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`.
PlanDefinition.action.participant (participant)maps to wider conceptPlanDefinition.action.participantElement `PlanDefinition.action.participant` is mapped to FHIR STU3 element `PlanDefinition.action.participant` as `Equivalent`.
PlanDefinition.action.participant.type (type)maps to wider conceptPlanDefinition.action.participant.typeElement `PlanDefinition.action.participant.type` is mapped to FHIR STU3 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`.
PlanDefinition.action.participant.role (role)is equivalent toPlanDefinition.action.participant.roleElement `PlanDefinition.action.participant.role` is mapped to FHIR STU3 element `PlanDefinition.action.participant.role` as `Equivalent`.
PlanDefinition.action.type (type)maps to wider conceptPlanDefinition.action.typeElement `PlanDefinition.action.type` is mapped to FHIR STU3 element `PlanDefinition.action.type` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.type` do not cover the following types: CodeableConcept. The mappings for `PlanDefinition.action.type` do not cover the following types based on type expansion: text.
PlanDefinition.action.groupingBehavior (groupingBehavior)is equivalent toPlanDefinition.action.groupingBehaviorElement `PlanDefinition.action.groupingBehavior` is mapped to FHIR STU3 element `PlanDefinition.action.groupingBehavior` as `Equivalent`.
PlanDefinition.action.selectionBehavior (selectionBehavior)is equivalent toPlanDefinition.action.selectionBehaviorElement `PlanDefinition.action.selectionBehavior` is mapped to FHIR STU3 element `PlanDefinition.action.selectionBehavior` as `Equivalent`.
PlanDefinition.action.requiredBehavior (requiredBehavior)is equivalent toPlanDefinition.action.requiredBehaviorElement `PlanDefinition.action.requiredBehavior` is mapped to FHIR STU3 element `PlanDefinition.action.requiredBehavior` as `Equivalent`.
PlanDefinition.action.precheckBehavior (precheckBehavior)is equivalent toPlanDefinition.action.precheckBehaviorElement `PlanDefinition.action.precheckBehavior` is mapped to FHIR STU3 element `PlanDefinition.action.precheckBehavior` as `Equivalent`.
PlanDefinition.action.cardinalityBehavior (cardinalityBehavior)is equivalent toPlanDefinition.action.cardinalityBehaviorElement `PlanDefinition.action.cardinalityBehavior` is mapped to FHIR STU3 element `PlanDefinition.action.cardinalityBehavior` as `Equivalent`.
PlanDefinition.action.definition[x] (definition[x])maps to wider conceptPlanDefinition.action.definitionElement `PlanDefinition.action.definition[x]` is mapped to FHIR STU3 element `PlanDefinition.action.definition` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.definition[x]` do not cover the following types: canonical, uri. 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)maps to wider conceptPlanDefinition.action.transformElement `PlanDefinition.action.transform` is mapped to FHIR STU3 element `PlanDefinition.action.transform` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.transform` do not cover the following types: canonical. The mappings for `PlanDefinition.action.transform` do not cover the following types based on type expansion: value. 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 conceptPlanDefinition.action.dynamicValueElement `PlanDefinition.action.dynamicValue` is mapped to FHIR STU3 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 toPlanDefinition.action.dynamicValue.pathElement `PlanDefinition.action.dynamicValue.path` is mapped to FHIR STU3 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 toPlanDefinition.action.dynamicValue.expressionElement `PlanDefinition.action.dynamicValue.expression` is mapped to FHIR STU3 element `PlanDefinition.action.dynamicValue.expression` as `SourceIsBroaderThanTarget`. 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 toPlanDefinition.action.actionElement `PlanDefinition.action.action` is mapped to FHIR STU3 element `PlanDefinition.action.action` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Subordinate title of the plan definition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.subtitle (subtitle)maps to wider conceptExtension (R4: Subordinate title of the plan definition (new))Element `PlanDefinition.subtitle` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.subtitle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Type of individual the plan definition is focused on (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.subject[x] (subject[x])maps to wider conceptExtension (R4: Type of individual the plan definition is focused on (new))Element `PlanDefinition.subject[x]` has a context of PlanDefinition based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.subject[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Who authored the content additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.author (author)maps to wider conceptExtension (R4: Who authored the content additional types)Element `PlanDefinition.author` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.author` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.author` do not cover the following types based on type expansion: name, telecom.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Who edited the content additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.editor (editor)maps to wider conceptExtension (R4: Who edited the content additional types)Element `PlanDefinition.editor` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.editor` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.editor` do not cover the following types based on type expansion: name, telecom.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Who reviewed the content additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.reviewer (reviewer)maps to wider conceptExtension (R4: Who reviewed the content additional types)Element `PlanDefinition.reviewer` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.reviewer` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.reviewer` do not cover the following types based on type expansion: name, telecom.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Who endorsed the content additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.endorser (endorser)maps to wider conceptExtension (R4: Who endorsed the content additional types)Element `PlanDefinition.endorser` is mapped to FHIR STU3 element `PlanDefinition.contributor` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.endorser` do not cover the following types: ContactDetail. The mappings for `PlanDefinition.endorser` do not cover the following types based on type expansion: name, telecom.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: library additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.library (library)is equivalent toExtension (R4: library additional types)Element `PlanDefinition.library` is mapped to FHIR STU3 element `PlanDefinition.library` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.library` do not cover the following types: canonical. The mappings for `PlanDefinition.library` do not cover the following types based on type expansion: value.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: routine | urgent | asap | stat (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.priority (priority)maps to wider conceptExtension (R4: routine | urgent | asap | stat (new))Element `PlanDefinition.action.priority` has a context of PlanDefinition.action based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.priority` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: Type of individual the action is focused on (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.subject[x] (subject[x])maps to wider conceptExtension (R4: Type of individual the action is focused on (new))Element `PlanDefinition.action.subject[x]` has a context of PlanDefinition.action based on following the parent source element upwards and mapping to `PlanDefinition`. Element `PlanDefinition.action.subject[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 11 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: timing additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.timing[x] (timing[x])is equivalent toExtension (R4: timing additional types)Element `PlanDefinition.action.timing[x]` is mapped to FHIR STU3 element `PlanDefinition.action.timing[x]` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.timing[x]` do not cover the following types: Age. 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`.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: patient | practitioner | related-person | deviceversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.participant.type (type)is equivalent toExtension (R4: patient | practitioner | related-person | device)Element `PlanDefinition.action.participant.type` is mapped to FHIR STU3 element `PlanDefinition.action.participant.type` as `SourceIsBroaderThanTarget`.

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: type additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.type (type)is equivalent toExtension (R4: type additional types)Element `PlanDefinition.action.type` is mapped to FHIR STU3 element `PlanDefinition.action.type` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.type` do not cover the following types: CodeableConcept. The mappings for `PlanDefinition.action.type` do not cover the following types based on type expansion: text.

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: definition additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.definition[x] (definition[x])maps to wider conceptExtension (R4: definition additional types)Element `PlanDefinition.action.definition[x]` is mapped to FHIR STU3 element `PlanDefinition.action.definition` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.definition[x]` do not cover the following types: canonical, uri. 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.

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/PlanDefinition|4.0.1 to R4: transform additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
PlanDefinition.action.transform (transform)is equivalent toExtension (R4: transform additional types)Element `PlanDefinition.action.transform` is mapped to FHIR STU3 element `PlanDefinition.action.transform` as `SourceIsBroaderThanTarget`. The mappings for `PlanDefinition.action.transform` do not cover the following types: canonical. The mappings for `PlanDefinition.action.transform` do not cover the following types based on type expansion: value. 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.