R5-Transport-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-Transport-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-Transport-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/Transport|5.0.0 to Basicversion: 4.0.1) Source Code Relationship Target Code Comment Transport.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `Transport.meta` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Transport.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `Transport.implicitRules` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.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. Transport.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `Transport.language` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.language` has no mapping targets in FHIR R4. Typically, this…
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-Transport-element-map-to-R4
  l: R5-Transport-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5TransportElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 Transport to FHIR R4 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:49.7856077-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 Transport 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/Transport
    l: Transport
  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: Transport.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 `Transport.meta` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: Transport.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 `Transport.implicitRules` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.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: Transport.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 `Transport.language` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.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: Transport.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 `Transport.text` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.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: Transport.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 `Transport.contained` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.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: Transport.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 `Transport.identifier` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This identifier is typically assigned by the dispenser, and may be used to reference the delivery when exchanging information about it with other systems.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Transport
    l: Transport
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.instantiatesCanonical
    l: extension-Transport.instantiatesCanonical
  target version:
    v: 0.1.0
  element:
    code:
      v: Transport.instantiatesCanonical
    display:
      v: instantiatesCanonical
    target:
      code:
        v: Extension
      equivalence:
        v: wider
      comment:
        v: Element `Transport.instantiatesCanonical` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.instantiatesCanonical` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Transport
    l: Transport

v: 5.0.0

v: 0.1.0

code:
  v: Transport.instantiatesUri
display:
  v: instantiatesUri
target:
  code:
    v: Extension
  equivalence:
    v: wider
  comment:
    v: Element `Transport.instantiatesUri` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.instantiatesUri` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.basedOn
  l: extension-Transport.basedOn
target version:
  v: 0.1.0
element:
  code:
    v: Transport.basedOn
  display:
    v: basedOn
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.basedOn` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.basedOn` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.groupIdentifier
  l: extension-Transport.groupIdentifier
target version:
  v: 0.1.0
element:
  code:
    v: Transport.groupIdentifier
  display:
    v: groupIdentifier
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.groupIdentifier` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.groupIdentifier` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.partOf
  l: extension-Transport.partOf
target version:
  v: 0.1.0
element:
  code:
    v: Transport.partOf
  display:
    v: partOf
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.partOf` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.partOf` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Not to be used to link an event to an Encounter - use Event.context for that. [The allowed reference resources may be adjusted as appropriate for the event resource].

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.status
  l: extension-Transport.status
target version:
  v: 0.1.0
element:
  code:
    v: Transport.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.status` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.status` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.statusReason
  l: extension-Transport.statusReason
target version:
  v: 0.1.0
element:
  code:
    v: Transport.statusReason
  display:
    v: statusReason
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.statusReason` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.statusReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This applies to the current status. Look at the history of the transport to see reasons for past statuses.

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.intent
  l: extension-Transport.intent
target version:
  v: 0.1.0
element:
  code:
    v: Transport.intent
  display:
    v: intent
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.intent` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.intent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is immutable. Proposed transports, planned transports, etc. must be distinct instances. In most cases, Transports will have an intent of "order".

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.priority
  l: extension-Transport.priority
target version:
  v: 0.1.0
element:
  code:
    v: Transport.priority
  display:
    v: priority
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.priority` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.priority` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.code
  l: extension-Transport.code
target version:
  v: 0.1.0
element:
  code:
    v: Transport.code
  display:
    v: code
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.code` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The title (eg "My Transports", "Outstanding Transports for Patient X") should go into the code.

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.description
  l: extension-Transport.description
target version:
  v: 0.1.0
element:
  code:
    v: Transport.description
  display:
    v: description
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.description` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.description` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.focus
  l: extension-Transport.focus
target version:
  v: 0.1.0
element:
  code:
    v: Transport.focus
  display:
    v: focus
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.focus` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If multiple resources need to be manipulated, use sub-transports. (This ensures that status can be tracked independently for each referenced resource.).

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.for
  l: extension-Transport.for
target version:
  v: 0.1.0
element:
  code:
    v: Transport.for
  display:
    v: for
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.for` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.for` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.encounter
  l: extension-Transport.encounter
target version:
  v: 0.1.0
element:
  code:
    v: Transport.encounter
  display:
    v: encounter
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.encounter` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.encounter` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.completionTime
  l: extension-Transport.completionTime
target version:
  v: 0.1.0
element:
  code:
    v: Transport.completionTime
  display:
    v: completionTime
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.completionTime` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.completionTime` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.authoredOn
  l: extension-Transport.authoredOn
target version:
  v: 0.1.0
element:
  code:
    v: Transport.authoredOn
  display:
    v: authoredOn
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.authoredOn` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.authoredOn` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.lastModified
  l: extension-Transport.lastModified
target version:
  v: 0.1.0
element:
  code:
    v: Transport.lastModified
  display:
    v: lastModified
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.lastModified` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.lastModified` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.requester
  l: extension-Transport.requester
target version:
  v: 0.1.0
element:
  code:
    v: Transport.requester
  display:
    v: requester
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.requester` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.requester` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.performerType
  l: extension-Transport.performerType
target version:
  v: 0.1.0
element:
  code:
    v: Transport.performerType
  display:
    v: performerType
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.performerType` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.performerType` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.owner
  l: extension-Transport.owner
target version:
  v: 0.1.0
element:
  code:
    v: Transport.owner
  display:
    v: owner
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.owner` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.owner` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Transports may be created with an owner not yet identified.

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.location
  l: extension-Transport.location
target version:
  v: 0.1.0
element:
  code:
    v: Transport.location
  display:
    v: location
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.location` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.location` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.insurance
  l: extension-Transport.insurance
target version:
  v: 0.1.0
element:
  code:
    v: Transport.insurance
  display:
    v: insurance
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.insurance` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.insurance` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.note
  l: extension-Transport.note
target version:
  v: 0.1.0
element:
  code:
    v: Transport.note
  display:
    v: note
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.note` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.note` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.relevantHistory
  l: extension-Transport.relevantHistory
target version:
  v: 0.1.0
element:
  code:
    v: Transport.relevantHistory
  display:
    v: relevantHistory
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.relevantHistory` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.relevantHistory` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.

source:
  v: http://hl7.org/fhir/StructureDefinition/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.restriction
  l: extension-Transport.restriction
target version:
  v: 0.1.0
element:
  code:
    v: Transport.restriction
  display:
    v: restriction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.restriction` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.restriction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Transport.restriction.repetitions
  display:
    v: repetitions
  target:
    code:
      v: Extension.extension:repetitions
    equivalence:
      v: wider
    comment:
      v: Element `Transport.restriction.repetitions` is part of an existing definition because parent element `Transport.restriction` requires a cross-version extension. Element `Transport.restriction.repetitions` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.restriction.repetitions` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Transport.restriction.period
  display:
    v: period
  target:
    code:
      v: Extension.extension:period
    equivalence:
      v: wider
    comment:
      v: Element `Transport.restriction.period` is part of an existing definition because parent element `Transport.restriction` requires a cross-version extension. Element `Transport.restriction.period` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.restriction.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that period.high is the due date representing the time by which the transport should be completed.
element:
  code:
    v: Transport.restriction.recipient
  display:
    v: recipient
  target:
    code:
      v: Extension.extension:recipient
    equivalence:
      v: wider
    comment:
      v: Element `Transport.restriction.recipient` is part of an existing definition because parent element `Transport.restriction` requires a cross-version extension. Element `Transport.restriction.recipient` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.restriction.recipient` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.input
  l: extension-Transport.input
target version:
  v: 0.1.0
element:
  code:
    v: Transport.input
  display:
    v: input
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.input` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.input` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Transport.input.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `Transport.input.type` is part of an existing definition because parent element `Transport.input` requires a cross-version extension. Element `Transport.input.type` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.input.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.
element:
  code:
    v: Transport.input.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension.extension:value
    equivalence:
      v: wider
    comment:
      v: Element `Transport.input.value[x]` is part of an existing definition because parent element `Transport.input` requires a cross-version extension. Element `Transport.input.value[x]` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.input.value[x]` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.output
  l: extension-Transport.output
target version:
  v: 0.1.0
element:
  code:
    v: Transport.output
  display:
    v: output
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.output` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.output` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Transport.output.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `Transport.output.type` is part of an existing definition because parent element `Transport.output` requires a cross-version extension. Element `Transport.output.type` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.output.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: Transport.output.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension.extension:value
    equivalence:
      v: wider
    comment:
      v: Element `Transport.output.value[x]` is part of an existing definition because parent element `Transport.output` requires a cross-version extension. Element `Transport.output.value[x]` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.output.value[x]` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.requestedLocation
  l: extension-Transport.requestedLocation
target version:
  v: 0.1.0
element:
  code:
    v: Transport.requestedLocation
  display:
    v: requestedLocation
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.requestedLocation` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.requestedLocation` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.currentLocation
  l: extension-Transport.currentLocation
target version:
  v: 0.1.0
element:
  code:
    v: Transport.currentLocation
  display:
    v: currentLocation
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.currentLocation` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.currentLocation` 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/Transport
  l: Transport
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Transport.reason
  l: extension-Transport.reason
target version:
  v: 0.1.0
element:
  code:
    v: Transport.reason
  display:
    v: reason
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Transport.reason` is not mapped to FHIR R4, since FHIR R5 `Transport` is not mapped. Element `Transport.reason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Transports might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in `Transport.reasonCode` if the data is free (uncoded) text.

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