R5-TestPlan-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-TestPlan-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-TestPlan-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from TestPlan to Basic Source Code Card. Type Relationship Target Code Card. Type Comment TestPlan.meta 0..1 todo is equivalent to Basic.meta 0..1 todo Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `TestPlan.meta` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). TestPlan.implicitRules 0..1 todo is equivalent to Basic.implicitRules 0..1 todo Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `TestPlan.implicitRules` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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. TestPlan.language 0..1 todo is equivalent to Basic.language 0..1 todo Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `TestPlan.language` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.language` has no mapping targets in FHIR R4. Typically, this is because the element has…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-TestPlan-element-map-to-R4
  l: R5-TestPlan-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5TestPlanElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 TestPlan to FHIR R4 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:49.5704221-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 TestPlan to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/TestPlan
    l: TestPlan
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 4.0.1
  element:
    code:
      v: TestPlan.meta
    display:
      v: meta
    target:
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `TestPlan.meta` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: TestPlan.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `TestPlan.implicitRules` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
  element:
    code:
      v: TestPlan.language
    display:
      v: language
    target:
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `TestPlan.language` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: TestPlan.text
    display:
      v: text
    target:
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `TestPlan.text` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
  element:
    code:
      v: TestPlan.contained
    display:
      v: contained
    target:
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `TestPlan.contained` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: TestPlan.identifier
    display:
      v: identifier
    target:
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `TestPlan.identifier` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this test plan outside of FHIR, where it is not possible to use the logical URI.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/TestPlan
    l: TestPlan
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.url
    l: extension-TestPlan.url
  target version:
    v: 0.1.0
  element:
    code:
      v: TestPlan.url
    display:
      v: url
    target:
      code:
        v: Extension
      equivalence:
        v: wider
      comment:
        v: Element `TestPlan.url` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/TestPlan
    l: TestPlan

v: 5.0.0

v: 0.1.0

code:
  v: TestPlan.version
display:
  v: version
target:
  code:
    v: Extension
  equivalence:
    v: wider
  comment:
    v: Element `TestPlan.version` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There may be different test plan 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 test plan with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.versionAlgorithm
  l: extension-TestPlan.versionAlgorithm
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.versionAlgorithm[x]
  display:
    v: versionAlgorithm[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.versionAlgorithm[x]` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.versionAlgorithm[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.name
  l: extension-TestPlan.name
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.name
  display:
    v: name
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.name` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.title
  l: extension-TestPlan.title
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.title` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.status
  l: extension-TestPlan.status
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.status` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of test plans that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.experimental
  l: extension-TestPlan.experimental
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.experimental
  display:
    v: experimental
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.experimental` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.experimental` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of test plans that are appropriate for use versus not.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.date
  l: extension-TestPlan.date
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.date
  display:
    v: date
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.date` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.date` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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 test plan. 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.publisher
  l: extension-TestPlan.publisher
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.publisher
  display:
    v: publisher
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.publisher` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the test plan is the organization or individual primarily responsible for the maintenance and upkeep of the test plan. 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 test plan. This item SHOULD be populated unless the information is available from context.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.contact
  l: extension-TestPlan.contact
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.contact
  display:
    v: contact
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.contact` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.description
  l: extension-TestPlan.description
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.description
  display:
    v: description
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.description` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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 test plan 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 test plan is presumed to be the predominant language in the place the test plan was created).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.useContext
  l: extension-TestPlan.useContext
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.useContext` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.jurisdiction
  l: extension-TestPlan.jurisdiction
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.jurisdiction
  display:
    v: jurisdiction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.jurisdiction` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Element `TestPlan.jurisdiction` has been flagged as deprecated. It may be possible for the test plan 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.)

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.purpose
  l: extension-TestPlan.purpose
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.purpose
  display:
    v: purpose
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.purpose` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the test plan 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 test plan.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.copyright
  l: extension-TestPlan.copyright
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.copyright
  display:
    v: copyright
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.copyright` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.copyrightLabel
  l: extension-TestPlan.copyrightLabel
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.copyrightLabel
  display:
    v: copyrightLabel
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.copyrightLabel` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.copyrightLabel` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.category
  l: extension-TestPlan.category
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.category
  display:
    v: category
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.category` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.category` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.scope
  l: extension-TestPlan.scope
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.scope
  display:
    v: scope
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.scope` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.testTools
  l: extension-TestPlan.testTools
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.testTools
  display:
    v: testTools
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testTools` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testTools` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.dependency
  l: extension-TestPlan.dependency
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.dependency
  display:
    v: dependency
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.dependency` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.dependency` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.dependency.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.dependency.description` is part of an existing definition because parent element `TestPlan.dependency` requires a cross-version extension. Element `TestPlan.dependency.description` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.dependency.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.dependency.predecessor
  display:
    v: predecessor
  target:
    code:
      v: Extension.extension:predecessor
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.dependency.predecessor` is part of an existing definition because parent element `TestPlan.dependency` requires a cross-version extension. Element `TestPlan.dependency.predecessor` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.dependency.predecessor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.exitCriteria
  l: extension-TestPlan.exitCriteria
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.exitCriteria
  display:
    v: exitCriteria
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.exitCriteria` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.exitCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TestPlan
  l: TestPlan
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TestPlan.testCase
  l: extension-TestPlan.testCase
target version:
  v: 0.1.0
element:
  code:
    v: TestPlan.testCase
  display:
    v: testCase
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.sequence
  display:
    v: sequence
  target:
    code:
      v: Extension.extension:sequence
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.sequence` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.sequence` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.sequence` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.scope
  display:
    v: scope
  target:
    code:
      v: Extension.extension:scope
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.scope` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.scope` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.dependency
  display:
    v: dependency
  target:
    code:
      v: Extension.extension:dependency
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.dependency` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.dependency` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.dependency` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.dependency.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:dependency.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.dependency.description` is part of an existing definition because parent element `TestPlan.testCase.dependency` requires a cross-version extension. Element `TestPlan.testCase.dependency.description` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.dependency.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.dependency.predecessor
  display:
    v: predecessor
  target:
    code:
      v: Extension.extension:dependency.extension:predecessor
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.dependency.predecessor` is part of an existing definition because parent element `TestPlan.testCase.dependency` requires a cross-version extension. Element `TestPlan.testCase.dependency.predecessor` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.dependency.predecessor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testRun
  display:
    v: testRun
  target:
    code:
      v: Extension.extension:testRun
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testRun` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.testRun` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testRun` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testRun.narrative
  display:
    v: narrative
  target:
    code:
      v: Extension.extension:testRun.extension:narrative
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testRun.narrative` is part of an existing definition because parent element `TestPlan.testCase.testRun` requires a cross-version extension. Element `TestPlan.testCase.testRun.narrative` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testRun.narrative` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testRun.script
  display:
    v: script
  target:
    code:
      v: Extension.extension:testRun.extension:script
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testRun.script` is part of an existing definition because parent element `TestPlan.testCase.testRun` requires a cross-version extension. Element `TestPlan.testCase.testRun.script` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testRun.script` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testRun.script.language
  display:
    v: language
  target:
    code:
      v: Extension.extension:testRun.extension:script.extension:language
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testRun.script.language` is part of an existing definition because parent element `TestPlan.testCase.testRun.script` requires a cross-version extension. Element `TestPlan.testCase.testRun.script.language` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testRun.script.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testRun.script.source[x]
  display:
    v: source[x]
  target:
    code:
      v: Extension.extension:testRun.extension:script.extension:source
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testRun.script.source[x]` is part of an existing definition because parent element `TestPlan.testCase.testRun.script` requires a cross-version extension. Element `TestPlan.testCase.testRun.script.source[x]` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testRun.script.source[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testData
  display:
    v: testData
  target:
    code:
      v: Extension.extension:testData
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testData` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.testData` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testData` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testData.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:testData.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testData.type` is part of an existing definition because parent element `TestPlan.testCase.testData` requires a cross-version extension. Element `TestPlan.testCase.testData.type` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testData.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testData.content
  display:
    v: content
  target:
    code:
      v: Extension.extension:testData.extension:content
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testData.content` is part of an existing definition because parent element `TestPlan.testCase.testData` requires a cross-version extension. Element `TestPlan.testCase.testData.content` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testData.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.testData.source[x]
  display:
    v: source[x]
  target:
    code:
      v: Extension.extension:testData.extension:source
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.testData.source[x]` is part of an existing definition because parent element `TestPlan.testCase.testData` requires a cross-version extension. Element `TestPlan.testCase.testData.source[x]` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.testData.source[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: TestPlan.testCase.assertion
  display:
    v: assertion
  target:
    code:
      v: Extension.extension:assertion
    equivalence:
      v: wider
    comment:
      v: Element `TestPlan.testCase.assertion` is part of an existing definition because parent element `TestPlan.testCase` requires a cross-version extension. Element `TestPlan.testCase.assertion` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.assertion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

code:
  v: TestPlan.testCase.assertion.type
display:
  v: type
target:
  code:
    v: Extension.extension:assertion.extension:type
  equivalence:
    v: wider
  comment:
    v: Element `TestPlan.testCase.assertion.type` is part of an existing definition because parent element `TestPlan.testCase.assertion` requires a cross-version extension. Element `TestPlan.testCase.assertion.type` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.assertion.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

code:
  v: TestPlan.testCase.assertion.object
display:
  v: object
target:
  code:
    v: Extension.extension:assertion.extension:object
  equivalence:
    v: wider
  comment:
    v: Element `TestPlan.testCase.assertion.object` is part of an existing definition because parent element `TestPlan.testCase.assertion` requires a cross-version extension. Element `TestPlan.testCase.assertion.object` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.assertion.object` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

code:
  v: TestPlan.testCase.assertion.result
display:
  v: result
target:
  code:
    v: Extension.extension:assertion.extension:result
  equivalence:
    v: wider
  comment:
    v: Element `TestPlan.testCase.assertion.result` is part of an existing definition because parent element `TestPlan.testCase.assertion` requires a cross-version extension. Element `TestPlan.testCase.assertion.result` is not mapped to FHIR R4, since FHIR R5 `TestPlan` is not mapped. Element `TestPlan.testCase.assertion.result` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).