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 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). Transport.text (text) is equivalent to Basic.text 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. Transport.contained (contained) is equivalent to Basic.contained 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. Transport.identifier (identifier) is equivalent to Basic.identifier 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 2 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Formal definition of transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.instantiatesCanonical (instantiatesCanonical) maps to wider concept Extension (R5: Formal definition of transport (new)) 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 3 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Formal definition of transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.instantiatesUri (instantiatesUri) maps to wider concept Extension (R5: Formal definition of transport (new)) 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). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Request fulfilled by this transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.basedOn (basedOn) maps to wider concept Extension (R5: Request fulfilled by this transport (new)) 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). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Requisition or grouper id (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.groupIdentifier (groupIdentifier) maps to wider concept Extension (R5: Requisition or grouper id (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Part of referenced event (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.partOf (partOf) maps to wider concept Extension (R5: Part of referenced event (new)) 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.#xD;#xD;[The allowed reference resources may be adjusted as appropriate for the event resource]. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: in-progress | completed | abandoned | cancelled | planned | entered-in-error (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.status (status) maps to wider concept Extension (R5: in-progress | completed | abandoned | cancelled | planned | entered-in-error (new)) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Reason for current status (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.statusReason (statusReason) maps to wider concept Extension (R5: Reason for current status (new)) 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. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.intent (intent) maps to wider concept Extension (R5: unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option (new)) 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". Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: routine | urgent | asap | stat (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.priority (priority) maps to wider concept Extension (R5: routine | urgent | asap | stat (new)) 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). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Transport Type (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.code (code) maps to wider concept Extension (R5: Transport Type (new)) 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. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Human-readable explanation of transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.description (description) maps to wider concept Extension (R5: Human-readable explanation of transport (new)) 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). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: What transport is acting on (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.focus (focus) maps to wider concept Extension (R5: What transport is acting on (new)) 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.). Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Beneficiary of the Transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.for (for) maps to wider concept Extension (R5: Beneficiary of the Transport (new)) 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). Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Healthcare event during which this transport originated (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.encounter (encounter) maps to wider concept Extension (R5: Healthcare event during which this transport originated (new)) 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). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Completion time of the event (the occurrence) (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.completionTime (completionTime) maps to wider concept Extension (R5: Completion time of the event (the occurrence) (new)) 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). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Transport Creation Date (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.authoredOn (authoredOn) maps to wider concept Extension (R5: Transport Creation Date (new)) 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). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Transport Last Modified Date (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.lastModified (lastModified) maps to wider concept Extension (R5: Transport Last Modified Date (new)) 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). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Who is asking for transport to be done (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.requester (requester) maps to wider concept Extension (R5: Who is asking for transport to be done (new)) 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). Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Requested performer (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.performerType (performerType) maps to wider concept Extension (R5: Requested performer (new)) 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). Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Responsible individual (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.owner (owner) maps to wider concept Extension (R5: Responsible individual (new)) 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. Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Where transport occurs (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.location (location) maps to wider concept Extension (R5: Where transport occurs (new)) 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). Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Associated insurance coverage (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.insurance (insurance) maps to wider concept Extension (R5: Associated insurance coverage (new)) 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). Group 24 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Comments made about the transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.note (note) maps to wider concept Extension (R5: Comments made about the transport (new)) 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). Group 25 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Key events in history of the Transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.relevantHistory (relevantHistory) maps to wider concept Extension (R5: Key events in history of the Transport (new)) 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. Group 26 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Constraints on fulfillment transports (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.restriction (restriction) maps to wider concept Extension (R5: Constraints on fulfillment transports (new)) 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). Transport.restriction.repetitions (repetitions) maps to wider concept Extension.extension:repetitions (R5: How many times to repeat (new)) 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). Transport.restriction.period (period) maps to wider concept Extension.extension:period (R5: When fulfillment sought (new)) 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. Transport.restriction.recipient (recipient) maps to wider concept Extension.extension:recipient (R5: For whom is fulfillment sought? (new)) 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). Group 27 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Information used to perform transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.input (input) maps to wider concept Extension (R5: Information used to perform transport (new)) 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). Transport.input.type (type) maps to wider concept Extension.extension:type (R5: Label for the input (new)) 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. Transport.input.value[x] (value[x]) maps to wider concept Extension.extension:value (R5: Content to use in performing the transport (new)) 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). Group 28 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Information produced as part of transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.output (output) maps to wider concept Extension (R5: Information produced as part of transport (new)) 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). Transport.output.type (type) maps to wider concept Extension.extension:type (R5: Label for output (new)) 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). Transport.output.value[x] (value[x]) maps to wider concept Extension.extension:value (R5: Result of output (new)) 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). Group 29 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: The desired location (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.requestedLocation (requestedLocation) maps to wider concept Extension (R5: The desired location (new)) 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). Group 30 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: The entity current location (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.currentLocation (currentLocation) maps to wider concept Extension (R5: The entity current location (new)) 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). Group 31 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Why transport is needed (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.reason (reason) maps to wider concept Extension (R5: Why transport is needed (new)) 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. Group 32 Mapping from http://hl7.org/fhir/StructureDefinition/Transport|5.0.0 to R5: Parent (or preceding) transport (new)version: 0.1.0) Source Code Relationship Target Code Comment Transport.history (history) maps to wider concept Extension (R5: Parent (or preceding) transport (new)) 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).
Cross-version mapping for FHIR R5 Transport to FHIR R4 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Transport to FHIR R4.
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 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 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 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 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 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.
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).
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).
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).
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).
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].
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).
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.
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".
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).
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.
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).
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.).
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).
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).
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).
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).
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).
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).
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).
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.
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).
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).
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).
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.
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 `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 `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 `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).
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 `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 `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).
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 `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 `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).
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).
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).
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.
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).