Generated Narrative: ConceptMap R5-EncounterHistory-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/EncounterHistory|5.0.0 to Encounterversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
EncounterHistory.meta (meta)is equivalent toEncounter.metaElement `EncounterHistory.meta` is mapped to FHIR R4 element `Encounter.meta` as `Equivalent`.
EncounterHistory.implicitRules (implicitRules)is equivalent toEncounter.implicitRulesElement `EncounterHistory.implicitRules` is mapped to FHIR R4 element `Encounter.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
EncounterHistory.language (language)is equivalent toEncounter.languageElement `EncounterHistory.language` is mapped to FHIR R4 element `Encounter.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
EncounterHistory.text (text)is equivalent toEncounter.textElement `EncounterHistory.text` is mapped to FHIR R4 element `Encounter.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
EncounterHistory.contained (contained)is equivalent toEncounter.containedElement `EncounterHistory.contained` is mapped to FHIR R4 element `Encounter.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
EncounterHistory.identifier (identifier)is equivalent toEncounter.identifierElement `EncounterHistory.identifier` is mapped to FHIR R4 element `Encounter.identifier` as `Equivalent`.
EncounterHistory.status (status)maps to wider conceptEncounter.statusElement `EncounterHistory.status` is mapped to FHIR R4 element `Encounter.status` as `SourceIsBroaderThanTarget`. The target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).
EncounterHistory.class (class)maps to wider conceptEncounter.classElement `EncounterHistory.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.class` do not cover the following types: CodeableConcept. The mappings for `EncounterHistory.class` do not cover the following types based on type expansion: text.
EncounterHistory.type (type)is equivalent toEncounter.typeElement `EncounterHistory.type` is mapped to FHIR R4 element `Encounter.type` as `Equivalent`. Since there are many ways to further classify encounters, this element is 0..*.
EncounterHistory.serviceType (serviceType)maps to wider conceptEncounter.serviceTypeElement `EncounterHistory.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.serviceType` do not cover the following types: CodeableReference. The mappings for `EncounterHistory.serviceType` do not cover the following types based on type expansion: reference.
EncounterHistory.subject (subject)is equivalent toEncounter.subjectElement `EncounterHistory.subject` is mapped to FHIR R4 element `Encounter.subject` as `Equivalent`. While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).
EncounterHistory.length (length)is equivalent toEncounter.lengthElement `EncounterHistory.length` is mapped to FHIR R4 element `Encounter.length` as `Equivalent`. If the precision on these values is low (e.g. to the day only) then this may be considered was an all day (or multi-day) encounter, unless the duration is included, where that amount of time occurred sometime during the interval. May differ from the time in `Encounter.period` due to leave of absence(s).
EncounterHistory.location (location)maps to wider conceptEncounter.locationElement `EncounterHistory.location` is mapped to FHIR R4 element `Encounter.location` as `Equivalent`. Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".
EncounterHistory.location.location (location)is equivalent toEncounter.location.locationElement `EncounterHistory.location.location` is mapped to FHIR R4 element `Encounter.location.location` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: The Encounter associated with this set of historic values (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.encounter (encounter)maps to wider conceptExtension (R5: The Encounter associated with this set of historic values (new))Element `EncounterHistory.encounter` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.encounter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknownversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.status (status)maps to wider conceptExtension (R5: planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown)Element `EncounterHistory.status` is mapped to FHIR R4 element `Encounter.status` as `SourceIsBroaderThanTarget`. The target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: class additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.class (class)maps to wider conceptExtension (R5: class additional types)Element `EncounterHistory.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.class` do not cover the following types: CodeableConcept. The mappings for `EncounterHistory.class` do not cover the following types based on type expansion: text.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: serviceType additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.serviceType (serviceType)maps to wider conceptExtension (R5: serviceType additional types)Element `EncounterHistory.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.serviceType` do not cover the following types: CodeableReference. The mappings for `EncounterHistory.serviceType` do not cover the following types based on type expansion: reference.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: The current status of the subject in relation to the Encounter (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.subjectStatus (subjectStatus)maps to wider conceptExtension (R5: The current status of the subject in relation to the Encounter (new))Element `EncounterHistory.subjectStatus` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.subjectStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: The actual start and end time associated with this set of values associated with the encounter (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.actualPeriod (actualPeriod)maps to wider conceptExtension (R5: The actual start and end time associated with this set of values associated with the encounter (new))Element `EncounterHistory.actualPeriod` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.actualPeriod` 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/EncounterHistory|5.0.0 to R5: The planned start date/time (or admission date) of the encounter (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.plannedStartDate (plannedStartDate)maps to wider conceptExtension (R5: The planned start date/time (or admission date) of the encounter (new))Element `EncounterHistory.plannedStartDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.plannedStartDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: The planned end date/time (or discharge date) of the encounter (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.plannedEndDate (plannedEndDate)maps to wider conceptExtension (R5: The planned end date/time (or discharge date) of the encounter (new))Element `EncounterHistory.plannedEndDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.plannedEndDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/EncounterHistory|5.0.0 to R5: The physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EncounterHistory.location.form (form)maps to wider conceptExtension (R5: The physical type of the location (usually the level in the location hierarchy - bed, room, ward, virtual etc.) (new))Element `EncounterHistory.location.form` has a context of Encounter.location based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.location.form` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.
 <status value="active"/> <experimental value="false"/> <date value="2026-03-17T16:04:45.177765-05:00"/> <contact> <name value="FHIR Infrastructure"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/fiwg"/> </telecom> </contact> <description value="This ConceptMap represents cross-version mappings for elements from a FHIR R5 EncounterHistory to FHIR R4."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <sourceCanonical value="http://hl7.org/fhir/5.0"/> <targetUri value="http://hl7.org/fhir/4.0"/> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/StructureDefinition/Encounter"/> <targetVersion value="4.0.1"/> <element> <code value="EncounterHistory.meta"/> <display value="meta"/> <target> <code value="Encounter.meta"/> <display value="Encounter.meta"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.meta` is mapped to FHIR R4 element `Encounter.meta` as `Equivalent`."/> </target> </element> <element> <code value="EncounterHistory.implicitRules"/> <display value="implicitRules"/> <target> <code value="Encounter.implicitRules"/> <display value="Encounter.implicitRules"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.implicitRules` is mapped to FHIR R4 element `Encounter.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/> </target> </element> <element> <code value="EncounterHistory.language"/> <display value="language"/> <target> <code value="Encounter.language"/> <display value="Encounter.language"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.language` is mapped to FHIR R4 element `Encounter.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/> </target> </element> <element> <code value="EncounterHistory.text"/> <display value="text"/> <target> <code value="Encounter.text"/> <display value="Encounter.text"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.text` is mapped to FHIR R4 element `Encounter.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later."/> </target> </element> <element> <code value="EncounterHistory.contained"/> <display value="contained"/> <target> <code value="Encounter.contained"/> <display value="Encounter.contained"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.contained` is mapped to FHIR R4 element `Encounter.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/> </target> </element> <element> <code value="EncounterHistory.identifier"/> <display value="identifier"/> <target> <code value="Encounter.identifier"/> <display value="Encounter.identifier"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.identifier` is mapped to FHIR R4 element `Encounter.identifier` as `Equivalent`."/> </target> </element> <element> <code value="EncounterHistory.status"/> <display value="status"/> <target> <code value="Encounter.status"/> <display value="Encounter.status"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.status` is mapped to FHIR R4 element `Encounter.status` as `SourceIsBroaderThanTarget`. The target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes)."/> </target> </element> <element> <code value="EncounterHistory.class"/> <display value="class"/> <target> <code value="Encounter.class"/> <display value="Encounter.class"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.class` do not cover the following types: CodeableConcept. The mappings for `EncounterHistory.class` do not cover the following types based on type expansion: text."/> </target> </element> <element> <code value="EncounterHistory.type"/> <display value="type"/> <target> <code value="Encounter.type"/> <display value="Encounter.type"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.type` is mapped to FHIR R4 element `Encounter.type` as `Equivalent`. Since there are many ways to further classify encounters, this element is 0..*."/> </target> </element> <element> <code value="EncounterHistory.serviceType"/> <display value="serviceType"/> <target> <code value="Encounter.serviceType"/> <display value="Encounter.serviceType"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.serviceType` do not cover the following types: CodeableReference. The mappings for `EncounterHistory.serviceType` do not cover the following types based on type expansion: reference."/> </target> </element> <element> <code value="EncounterHistory.subject"/> <display value="subject"/> <target> <code value="Encounter.subject"/> <display value="Encounter.subject"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.subject` is mapped to FHIR R4 element `Encounter.subject` as `Equivalent`. While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked)."/> </target> </element> <element> <code value="EncounterHistory.length"/> <display value="length"/> <target> <code value="Encounter.length"/> <display value="Encounter.length"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.length` is mapped to FHIR R4 element `Encounter.length` as `Equivalent`. If the precision on these values is low (e.g. to the day only) then this may be considered was an all day (or multi-day) encounter, unless the duration is included, where that amount of time occurred sometime during the interval. May differ from the time in `Encounter.period` due to leave of absence(s)."/> </target> </element> <element> <code value="EncounterHistory.location"/> <display value="location"/> <target> <code value="Encounter.location"/> <display value="Encounter.location"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.location` is mapped to FHIR R4 element `Encounter.location` as `Equivalent`. Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual"."/> </target> </element> <element> <code value="EncounterHistory.location.location"/> <display value="location"/> <target> <code value="Encounter.location.location"/> <display value="Encounter.location.location"/> <equivalence value="equivalent"/> <comment value="Element `EncounterHistory.location.location` is mapped to FHIR R4 element `Encounter.location.location` as `Equivalent`."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.encounter"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.encounter"/> <display value="encounter"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.encounter` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.encounter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.status"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.status"/> <display value="status"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.status` is mapped to FHIR R4 element `Encounter.status` as `SourceIsBroaderThanTarget`. The target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier. Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes)."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.class"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.class"/> <display value="class"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.class` do not cover the following types: CodeableConcept. The mappings for `EncounterHistory.class` do not cover the following types based on type expansion: text."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.serviceType"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.serviceType"/> <display value="serviceType"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `EncounterHistory.serviceType` do not cover the following types: CodeableReference. The mappings for `EncounterHistory.serviceType` do not cover the following types based on type expansion: reference."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.subjectStatus"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.subjectStatus"/> <display value="subjectStatus"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.subjectStatus` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.subjectStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.actualPeriod"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.actualPeriod"/> <display value="actualPeriod"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.actualPeriod` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.actualPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.plannedStartDate"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.plannedStartDate"/> <display value="plannedStartDate"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.plannedStartDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.plannedStartDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.plannedEndDate"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.plannedEndDate"/> <display value="plannedEndDate"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.plannedEndDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.plannedEndDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/> </target> </element> </group> <group> <source value="http://hl7.org/fhir/StructureDefinition/EncounterHistory"/> <sourceVersion value="5.0.0"/> <target value="http://hl7.org/fhir/5.0/StructureDefinition/extension-EncounterHistory.location.form"/> <targetVersion value="0.1.0"/> <element> <code value="EncounterHistory.location.form"/> <display value="form"/> <target> <code value="Extension"/> <equivalence value="wider"/> <comment value="Element `EncounterHistory.location.form` has a context of Encounter.location based on following the parent source element upwards and mapping to `Encounter`. Element `EncounterHistory.location.form` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query. There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario."/> </target> </element> </group> </ConceptMap>