FHIRsmith: ConceptMap/ConceptMap-R4B-Encounter-element-map-to-R5.json

FHIR IG analytics

Package	hl7.fhir.uv.xver-r4b.r5
Resource Type	ConceptMap
Id	ConceptMap-R4B-Encounter-element-map-to-R5.json
FHIR Version	R5
Source	http://hl7.org/fhir/uv/xver-r4b.r5/0.1.0/ConceptMap-R4B-Encounter-element-map-to-R5.html
URL	http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Encounter-element-map-to-R5
Version	0.1.0
Status	active
Date	2026-03-17T16:03:51.6392042-05:00
Name	R4BEncounterElementMapToR5
Title	Cross-version mapping for FHIR R4B Encounter to FHIR R5 Encounter
Realm	uv
Authority	hl7
Description	This ConceptMap represents cross-version mappings for elements from a FHIR R4B Encounter to FHIR R5.

Resources that use this resource

No resources found

Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.classHistory	R4B: List of past encounter classes (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.diagnosis.condition	R4B: The diagnosis or procedure relevant to the encounter additional types
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.diagnosis.rank	R4B: Ranking of the diagnosis (for each role type) (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.hospitalization.dietPreference	R4B: Diet preferences reported by the patient (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.hospitalization.specialArrangement	R4B: Wheelchair, translator, stretcher, etc. (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.hospitalization.specialCourtesy	R4B: Special courtesies (VIP, board member) (new)
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.reasonReference	R4B: Reason the encounter takes place (reference) additional types
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.status	R4B: planned \| arrived \| triaged \| in-progress \| onleave \| finished \| cancelled +
hl7.fhir.uv.xver-r4b.r5#0.1.0	extension-Encounter.statusHistory	R4B: List of past encounter statuses (new)

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R4B-Encounter-element-map-to-R5

Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0

Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to Encounterversion: 5.0.0)

Source Code

Relationship

Target Code

Comment

Encounter.meta (meta)

is equivalent to

Encounter.meta

Element `Encounter.meta` is mapped to FHIR R5 element `Encounter.meta` as `Equivalent`.

Encounter.implicitRules (implicitRules)

is equivalent to

Encounter.implicitRules

Element `Encounter.implicitRules` is mapped to FHIR R5 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 it's narrative along with other profiles, value sets, etc.

Encounter.language (language)

is equivalent to

Encounter.language

Element `Encounter.language` is mapped to FHIR R5 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).

Encounter.text (text)

is equivalent to

Encounter.text

Element `Encounter.text` is mapped to FHIR R5 element `Encounter.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Encounter.contained (contained)

is equivalent to

Encounter.contained

Element `Encounter.contained` is mapped to FHIR R5 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.

Encounter.identifier (identifier)

is equivalent to

Encounter.identifier

Element `Encounter.identifier` is mapped to FHIR R5 element `Encounter.identifier` as `Equivalent`.

Encounter.status (status)

is broader than

Encounter.status

Element `Encounter.status` is mapped to FHIR R5 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).

Encounter.class (class)

is equivalent to

Encounter.class

Element `Encounter.class` is mapped to FHIR R5 element `Encounter.class` as `SourceIsNarrowerThanTarget`.

Encounter.type (type)

is equivalent to

Encounter.type

Element `Encounter.type` is mapped to FHIR R5 element `Encounter.type` as `Equivalent`. Since there are many ways to further classify encounters, this element is 0..*.

Encounter.serviceType (serviceType)

is equivalent to

Encounter.serviceType

Element `Encounter.serviceType` is mapped to FHIR R5 element `Encounter.serviceType` as `SourceIsNarrowerThanTarget`.

Encounter.priority (priority)

is equivalent to

Encounter.priority

Element `Encounter.priority` is mapped to FHIR R5 element `Encounter.priority` as `Equivalent`.

Encounter.subject (subject)

is equivalent to

Encounter.subject

Element `Encounter.subject` is mapped to FHIR R5 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).

Encounter.episodeOfCare (episodeOfCare)

is equivalent to

Encounter.episodeOfCare

Element `Encounter.episodeOfCare` is mapped to FHIR R5 element `Encounter.episodeOfCare` as `Equivalent`.

Encounter.basedOn (basedOn)

is equivalent to

Encounter.basedOn

Element `Encounter.basedOn` is mapped to FHIR R5 element `Encounter.basedOn` as `Equivalent`.

Encounter.participant (participant)

is broader than

Encounter.participant

Element `Encounter.participant` is mapped to FHIR R5 element `Encounter.participant` as `Equivalent`.

Encounter.participant.type (type)

is equivalent to

Encounter.participant.type

Element `Encounter.participant.type` is mapped to FHIR R5 element `Encounter.participant.type` as `Equivalent`. The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

Encounter.participant.period (period)

is equivalent to

Encounter.participant.period

Element `Encounter.participant.period` is mapped to FHIR R5 element `Encounter.participant.period` as `Equivalent`.

Encounter.participant.individual (individual)

is equivalent to

Encounter.participant.actor

Element `Encounter.participant.individual` is mapped to FHIR R5 element `Encounter.participant.actor` as `Equivalent`.

Encounter.appointment (appointment)

is equivalent to

Encounter.appointment

Element `Encounter.appointment` is mapped to FHIR R5 element `Encounter.appointment` as `Equivalent`.

Encounter.period (period)

is equivalent to

Encounter.actualPeriod

Element `Encounter.period` is mapped to FHIR R5 element `Encounter.actualPeriod` as `Equivalent`. If not (yet) known, the end of the Period may be omitted.

Encounter.length (length)

is equivalent to

Encounter.length

Element `Encounter.length` is mapped to FHIR R5 element `Encounter.length` as `Equivalent`. May differ from the time the Encounter.period lasted because of leave of absence.

Encounter.reasonCode (reasonCode)

is narrower than

Encounter.reason.value

Element `Encounter.reasonCode` is mapped to FHIR R5 element `Encounter.reason.value` as `SourceIsNarrowerThanTarget`. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Encounter.reasonReference (reasonReference)

is related to

Encounter.reason.value

Element `Encounter.reasonReference` is mapped to FHIR R5 element `Encounter.reason.value` as `RelatedTo`. The mappings for `Encounter.reasonReference` do not cover the following types: Reference. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Encounter.diagnosis (diagnosis)

is broader than

Encounter.diagnosis

Element `Encounter.diagnosis` is mapped to FHIR R5 element `Encounter.diagnosis` as `Equivalent`.

Encounter.diagnosis.condition (condition)

is broader than

Encounter.diagnosis.condition

Element `Encounter.diagnosis.condition` is mapped to FHIR R5 element `Encounter.diagnosis.condition` as `RelatedTo`. The mappings for `Encounter.diagnosis.condition` do not cover the following types: Reference. The mappings for `Encounter.diagnosis.condition` do not cover the following types based on type expansion: display, identifier, reference, type. For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Encounter.diagnosis.use (use)

is equivalent to

Encounter.diagnosis.use

Element `Encounter.diagnosis.use` is mapped to FHIR R5 element `Encounter.diagnosis.use` as `SourceIsNarrowerThanTarget`.

Encounter.account (account)

is equivalent to

Encounter.account

Element `Encounter.account` is mapped to FHIR R5 element `Encounter.account` as `Equivalent`. The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Encounter.hospitalization (hospitalization)

is broader than

Encounter.admission

Element `Encounter.hospitalization` is mapped to FHIR R5 element `Encounter.admission` as `Equivalent`. An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included. The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.

Encounter.hospitalization.preAdmissionIdentifier (preAdmissionIdentifier)

is equivalent to

Encounter.admission.preAdmissionIdentifier

Element `Encounter.hospitalization.preAdmissionIdentifier` is mapped to FHIR R5 element `Encounter.admission.preAdmissionIdentifier` as `Equivalent`.

Encounter.hospitalization.origin (origin)

is equivalent to

Encounter.admission.origin

Element `Encounter.hospitalization.origin` is mapped to FHIR R5 element `Encounter.admission.origin` as `Equivalent`.

Encounter.hospitalization.admitSource (admitSource)

is equivalent to

Encounter.admission.admitSource

Element `Encounter.hospitalization.admitSource` is mapped to FHIR R5 element `Encounter.admission.admitSource` as `Equivalent`.

Encounter.hospitalization.reAdmission (reAdmission)

is equivalent to

Encounter.admission.reAdmission

Element `Encounter.hospitalization.reAdmission` is mapped to FHIR R5 element `Encounter.admission.reAdmission` as `Equivalent`.

Encounter.hospitalization.destination (destination)

is equivalent to

Encounter.admission.destination

Element `Encounter.hospitalization.destination` is mapped to FHIR R5 element `Encounter.admission.destination` as `Equivalent`.

Encounter.hospitalization.dischargeDisposition (dischargeDisposition)

is equivalent to

Encounter.admission.dischargeDisposition

Element `Encounter.hospitalization.dischargeDisposition` is mapped to FHIR R5 element `Encounter.admission.dischargeDisposition` as `Equivalent`.

Encounter.location (location)

is broader than

Encounter.location

Element `Encounter.location` is mapped to FHIR R5 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".

Encounter.location.location (location)

is equivalent to

Encounter.location.location

Element `Encounter.location.location` is mapped to FHIR R5 element `Encounter.location.location` as `Equivalent`.

Encounter.location.status (status)

is equivalent to

Encounter.location.status

Element `Encounter.location.status` is mapped to FHIR R5 element `Encounter.location.status` as `Equivalent`. When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.

Encounter.location.physicalType (physicalType)

is equivalent to

Encounter.location.form

Element `Encounter.location.physicalType` is mapped to FHIR R5 element `Encounter.location.form` as `Equivalent`. 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.

Encounter.location.period (period)

is equivalent to

Encounter.location.period

Element `Encounter.location.period` is mapped to FHIR R5 element `Encounter.location.period` as `Equivalent`.

Encounter.serviceProvider (serviceProvider)

is equivalent to

Encounter.serviceProvider

Element `Encounter.serviceProvider` is mapped to FHIR R5 element `Encounter.serviceProvider` as `Equivalent`.

Encounter.partOf (partOf)

is equivalent to

Encounter.partOf

Element `Encounter.partOf` is mapped to FHIR R5 element `Encounter.partOf` as `Equivalent`. 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.

Source Code

Relationship

Target Code

Comment

Encounter.status (status)

is equivalent to

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: List of past encounter statuses (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.statusHistory (statusHistory)

is broader than

Extension (R4B: List of past encounter statuses (new))

Element `Encounter.statusHistory` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.statusHistory` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The current status is always found in the current version of the resource, not the status history.

Encounter.statusHistory.status (status)

is broader than

Element `Encounter.statusHistory.status` is part of an existing definition because parent element `Encounter.statusHistory` requires a cross-version extension. Element `Encounter.statusHistory.status` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.statusHistory.status` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Encounter.statusHistory.period (period)

is broader than

Extension.extension:period (R4B: The time that the episode was in the specified status (new))

Element `Encounter.statusHistory.period` is part of an existing definition because parent element `Encounter.statusHistory` requires a cross-version extension. Element `Encounter.statusHistory.period` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.statusHistory.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: List of past encounter classes (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.classHistory (classHistory)

is broader than

Extension (R4B: List of past encounter classes (new))

Element `Encounter.classHistory` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.classHistory` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Encounter.classHistory.class (class)

is broader than

Extension.extension:class (R4B: inpatient | outpatient | ambulatory | emergency + (new))

Element `Encounter.classHistory.class` is part of an existing definition because parent element `Encounter.classHistory` requires a cross-version extension. Element `Encounter.classHistory.class` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.classHistory.class` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Encounter.classHistory.period (period)

is broader than

Extension.extension:period (R4B: The time that the episode was in the specified class (new))

Element `Encounter.classHistory.period` is part of an existing definition because parent element `Encounter.classHistory` requires a cross-version extension. Element `Encounter.classHistory.period` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.classHistory.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: Reason the encounter takes place (reference) additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.reasonReference (reasonReference)

is broader than

Extension (R4B: Reason the encounter takes place (reference) additional types)

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: The diagnosis or procedure relevant to the encounter additional typesversion: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.diagnosis.condition (condition)

is equivalent to

Extension (R4B: The diagnosis or procedure relevant to the encounter additional types)

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: Ranking of the diagnosis (for each role type) (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.diagnosis.rank (rank)

is broader than

Extension (R4B: Ranking of the diagnosis (for each role type) (new))

Element `Encounter.diagnosis.rank` has a context of Encounter.diagnosis based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.diagnosis.rank` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: Diet preferences reported by the patient (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.hospitalization.dietPreference (dietPreference)

is broader than

Extension (R4B: Diet preferences reported by the patient (new))

Element `Encounter.hospitalization.dietPreference` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.hospitalization.dietPreference` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: Special courtesies (VIP, board member) (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.hospitalization.specialCourtesy (specialCourtesy)

is broader than

Extension (R4B: Special courtesies (VIP, board member) (new))

Element `Encounter.hospitalization.specialCourtesy` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.hospitalization.specialCourtesy` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0 to R4B: Wheelchair, translator, stretcher, etc. (new)version: 0.1.0)

Source Code

Relationship

Target Code

Comment

Encounter.hospitalization.specialArrangement (specialArrangement)

is broader than

Extension (R4B: Wheelchair, translator, stretcher, etc. (new))

Element `Encounter.hospitalization.specialArrangement` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.hospitalization.specialArrangement` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R4B-Encounter-element-map-to-R5",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r5"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4B-Encounter-element-map-to-R5",
  "version": "0.1.0",
  "name": "R4BEncounterElementMapToR5",
  "title": "Cross-version mapping for FHIR R4B Encounter to FHIR R5 Encounter",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:03:51.6392042-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R4B Encounter to FHIR R5.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceScopeCanonical": "http://hl7.org/fhir/4.3",
  "targetScopeUri": "http://hl7.org/fhir/5.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0",
      "element": [
        {
          "code": "Encounter.meta",
          "display": "meta",
          "target": [
            {
              "code": "Encounter.meta",
              "display": "Encounter.meta",
              "relationship": "equivalent",
              "comment": "Element `Encounter.meta` is mapped to FHIR R5 element `Encounter.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Encounter.implicitRules",
              "display": "Encounter.implicitRules",
              "relationship": "equivalent",
              "comment": "Element `Encounter.implicitRules` is mapped to FHIR R5 element `Encounter.implicitRules` as `Equivalent`.\nAsserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "Encounter.language",
          "display": "language",
          "target": [
            {
              "code": "Encounter.language",
              "display": "Encounter.language",
              "relationship": "equivalent",
              "comment": "Element `Encounter.language` is mapped to FHIR R5 element `Encounter.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Encounter.text",
          "display": "text",
          "target": [
            {
              "code": "Encounter.text",
              "display": "Encounter.text",
              "relationship": "equivalent",
              "comment": "Element `Encounter.text` is mapped to FHIR R5 element `Encounter.text` as `Equivalent`.\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
            }
          ]
        },
        {
          "code": "Encounter.contained",
          "display": "contained",
          "target": [
            {
              "code": "Encounter.contained",
              "display": "Encounter.contained",
              "relationship": "equivalent",
              "comment": "Element `Encounter.contained` is mapped to FHIR R5 element `Encounter.contained` as `Equivalent`.\nThis 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."
            }
          ]
        },
        {
          "code": "Encounter.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Encounter.identifier",
              "display": "Encounter.identifier",
              "relationship": "equivalent",
              "comment": "Element `Encounter.identifier` is mapped to FHIR R5 element `Encounter.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.status",
          "display": "status",
          "target": [
            {
              "code": "Encounter.status",
              "display": "Encounter.status",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.status` is mapped to FHIR R5 element `Encounter.status` as `SourceIsBroaderThanTarget`.\nThe target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier.\nNote that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes)."
            }
          ]
        },
        {
          "code": "Encounter.class",
          "display": "class",
          "target": [
            {
              "code": "Encounter.class",
              "display": "Encounter.class",
              "relationship": "equivalent",
              "comment": "Element `Encounter.class` is mapped to FHIR R5 element `Encounter.class` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Encounter.type",
          "display": "type",
          "target": [
            {
              "code": "Encounter.type",
              "display": "Encounter.type",
              "relationship": "equivalent",
              "comment": "Element `Encounter.type` is mapped to FHIR R5 element `Encounter.type` as `Equivalent`.\nSince there are many ways to further classify encounters, this element is 0..*."
            }
          ]
        },
        {
          "code": "Encounter.serviceType",
          "display": "serviceType",
          "target": [
            {
              "code": "Encounter.serviceType",
              "display": "Encounter.serviceType",
              "relationship": "equivalent",
              "comment": "Element `Encounter.serviceType` is mapped to FHIR R5 element `Encounter.serviceType` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Encounter.priority",
          "display": "priority",
          "target": [
            {
              "code": "Encounter.priority",
              "display": "Encounter.priority",
              "relationship": "equivalent",
              "comment": "Element `Encounter.priority` is mapped to FHIR R5 element `Encounter.priority` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.subject",
          "display": "subject",
          "target": [
            {
              "code": "Encounter.subject",
              "display": "Encounter.subject",
              "relationship": "equivalent",
              "comment": "Element `Encounter.subject` is mapped to FHIR R5 element `Encounter.subject` as `Equivalent`.\nWhile 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)."
            }
          ]
        },
        {
          "code": "Encounter.episodeOfCare",
          "display": "episodeOfCare",
          "target": [
            {
              "code": "Encounter.episodeOfCare",
              "display": "Encounter.episodeOfCare",
              "relationship": "equivalent",
              "comment": "Element `Encounter.episodeOfCare` is mapped to FHIR R5 element `Encounter.episodeOfCare` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.basedOn",
          "display": "basedOn",
          "target": [
            {
              "code": "Encounter.basedOn",
              "display": "Encounter.basedOn",
              "relationship": "equivalent",
              "comment": "Element `Encounter.basedOn` is mapped to FHIR R5 element `Encounter.basedOn` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.participant",
          "display": "participant",
          "target": [
            {
              "code": "Encounter.participant",
              "display": "Encounter.participant",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.participant` is mapped to FHIR R5 element `Encounter.participant` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.participant.type",
          "display": "type",
          "target": [
            {
              "code": "Encounter.participant.type",
              "display": "Encounter.participant.type",
              "relationship": "equivalent",
              "comment": "Element `Encounter.participant.type` is mapped to FHIR R5 element `Encounter.participant.type` as `Equivalent`.\nThe participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc."
            }
          ]
        },
        {
          "code": "Encounter.participant.period",
          "display": "period",
          "target": [
            {
              "code": "Encounter.participant.period",
              "display": "Encounter.participant.period",
              "relationship": "equivalent",
              "comment": "Element `Encounter.participant.period` is mapped to FHIR R5 element `Encounter.participant.period` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.participant.individual",
          "display": "individual",
          "target": [
            {
              "code": "Encounter.participant.actor",
              "display": "Encounter.participant.actor",
              "relationship": "equivalent",
              "comment": "Element `Encounter.participant.individual` is mapped to FHIR R5 element `Encounter.participant.actor` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.appointment",
          "display": "appointment",
          "target": [
            {
              "code": "Encounter.appointment",
              "display": "Encounter.appointment",
              "relationship": "equivalent",
              "comment": "Element `Encounter.appointment` is mapped to FHIR R5 element `Encounter.appointment` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.period",
          "display": "period",
          "target": [
            {
              "code": "Encounter.actualPeriod",
              "display": "Encounter.actualPeriod",
              "relationship": "equivalent",
              "comment": "Element `Encounter.period` is mapped to FHIR R5 element `Encounter.actualPeriod` as `Equivalent`.\nIf not (yet) known, the end of the Period may be omitted."
            }
          ]
        },
        {
          "code": "Encounter.length",
          "display": "length",
          "target": [
            {
              "code": "Encounter.length",
              "display": "Encounter.length",
              "relationship": "equivalent",
              "comment": "Element `Encounter.length` is mapped to FHIR R5 element `Encounter.length` as `Equivalent`.\nMay differ from the time the Encounter.period lasted because of leave of absence."
            }
          ]
        },
        {
          "code": "Encounter.reasonCode",
          "display": "reasonCode",
          "target": [
            {
              "code": "Encounter.reason.value",
              "display": "Encounter.reason.value",
              "relationship": "source-is-narrower-than-target",
              "comment": "Element `Encounter.reasonCode` is mapped to FHIR R5 element `Encounter.reason.value` as `SourceIsNarrowerThanTarget`.\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis)."
            }
          ]
        },
        {
          "code": "Encounter.reasonReference",
          "display": "reasonReference",
          "target": [
            {
              "code": "Encounter.reason.value",
              "display": "Encounter.reason.value",
              "relationship": "related-to",
              "comment": "Element `Encounter.reasonReference` is mapped to FHIR R5 element `Encounter.reason.value` as `RelatedTo`.\nThe mappings for `Encounter.reasonReference` do not cover the following types: Reference.\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis)."
            }
          ]
        },
        {
          "code": "Encounter.diagnosis",
          "display": "diagnosis",
          "target": [
            {
              "code": "Encounter.diagnosis",
              "display": "Encounter.diagnosis",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.diagnosis` is mapped to FHIR R5 element `Encounter.diagnosis` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.diagnosis.condition",
          "display": "condition",
          "target": [
            {
              "code": "Encounter.diagnosis.condition",
              "display": "Encounter.diagnosis.condition",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.diagnosis.condition` is mapped to FHIR R5 element `Encounter.diagnosis.condition` as `RelatedTo`.\nThe mappings for `Encounter.diagnosis.condition` do not cover the following types: Reference.\nThe mappings for `Encounter.diagnosis.condition` do not cover the following types based on type expansion: display, identifier, reference, type.\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis)."
            }
          ]
        },
        {
          "code": "Encounter.diagnosis.use",
          "display": "use",
          "target": [
            {
              "code": "Encounter.diagnosis.use",
              "display": "Encounter.diagnosis.use",
              "relationship": "equivalent",
              "comment": "Element `Encounter.diagnosis.use` is mapped to FHIR R5 element `Encounter.diagnosis.use` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "Encounter.account",
          "display": "account",
          "target": [
            {
              "code": "Encounter.account",
              "display": "Encounter.account",
              "relationship": "equivalent",
              "comment": "Element `Encounter.account` is mapped to FHIR R5 element `Encounter.account` as `Equivalent`.\nThe billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization",
          "display": "hospitalization",
          "target": [
            {
              "code": "Encounter.admission",
              "display": "Encounter.admission",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.hospitalization` is mapped to FHIR R5 element `Encounter.admission` as `Equivalent`.\nAn Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.\r\rThe duration recorded in the period of this encounter covers the entire scope of this hospitalization record."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.preAdmissionIdentifier",
          "display": "preAdmissionIdentifier",
          "target": [
            {
              "code": "Encounter.admission.preAdmissionIdentifier",
              "display": "Encounter.admission.preAdmissionIdentifier",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.preAdmissionIdentifier` is mapped to FHIR R5 element `Encounter.admission.preAdmissionIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.origin",
          "display": "origin",
          "target": [
            {
              "code": "Encounter.admission.origin",
              "display": "Encounter.admission.origin",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.origin` is mapped to FHIR R5 element `Encounter.admission.origin` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.admitSource",
          "display": "admitSource",
          "target": [
            {
              "code": "Encounter.admission.admitSource",
              "display": "Encounter.admission.admitSource",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.admitSource` is mapped to FHIR R5 element `Encounter.admission.admitSource` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.reAdmission",
          "display": "reAdmission",
          "target": [
            {
              "code": "Encounter.admission.reAdmission",
              "display": "Encounter.admission.reAdmission",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.reAdmission` is mapped to FHIR R5 element `Encounter.admission.reAdmission` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.destination",
          "display": "destination",
          "target": [
            {
              "code": "Encounter.admission.destination",
              "display": "Encounter.admission.destination",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.destination` is mapped to FHIR R5 element `Encounter.admission.destination` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.hospitalization.dischargeDisposition",
          "display": "dischargeDisposition",
          "target": [
            {
              "code": "Encounter.admission.dischargeDisposition",
              "display": "Encounter.admission.dischargeDisposition",
              "relationship": "equivalent",
              "comment": "Element `Encounter.hospitalization.dischargeDisposition` is mapped to FHIR R5 element `Encounter.admission.dischargeDisposition` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.location",
          "display": "location",
          "target": [
            {
              "code": "Encounter.location",
              "display": "Encounter.location",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.location` is mapped to FHIR R5 element `Encounter.location` as `Equivalent`.\nVirtual 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\"."
            }
          ]
        },
        {
          "code": "Encounter.location.location",
          "display": "location",
          "target": [
            {
              "code": "Encounter.location.location",
              "display": "Encounter.location.location",
              "relationship": "equivalent",
              "comment": "Element `Encounter.location.location` is mapped to FHIR R5 element `Encounter.location.location` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.location.status",
          "display": "status",
          "target": [
            {
              "code": "Encounter.location.status",
              "display": "Encounter.location.status",
              "relationship": "equivalent",
              "comment": "Element `Encounter.location.status` is mapped to FHIR R5 element `Encounter.location.status` as `Equivalent`.\nWhen the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed."
            }
          ]
        },
        {
          "code": "Encounter.location.physicalType",
          "display": "physicalType",
          "target": [
            {
              "code": "Encounter.location.form",
              "display": "Encounter.location.form",
              "relationship": "equivalent",
              "comment": "Element `Encounter.location.physicalType` is mapped to FHIR R5 element `Encounter.location.form` as `Equivalent`.\nThis information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.\n\nThere may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario."
            }
          ]
        },
        {
          "code": "Encounter.location.period",
          "display": "period",
          "target": [
            {
              "code": "Encounter.location.period",
              "display": "Encounter.location.period",
              "relationship": "equivalent",
              "comment": "Element `Encounter.location.period` is mapped to FHIR R5 element `Encounter.location.period` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.serviceProvider",
          "display": "serviceProvider",
          "target": [
            {
              "code": "Encounter.serviceProvider",
              "display": "Encounter.serviceProvider",
              "relationship": "equivalent",
              "comment": "Element `Encounter.serviceProvider` is mapped to FHIR R5 element `Encounter.serviceProvider` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Encounter.partOf",
          "display": "partOf",
          "target": [
            {
              "code": "Encounter.partOf",
              "display": "Encounter.partOf",
              "relationship": "equivalent",
              "comment": "Element `Encounter.partOf` is mapped to FHIR R5 element `Encounter.partOf` as `Equivalent`.\nThis is also used for associating a child's encounter back to the mother's encounter.\r\rRefer to the Notes section in the Patient resource for further details."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.status|0.1.0",
      "element": [
        {
          "code": "Encounter.status",
          "display": "status",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Encounter.status` is mapped to FHIR R5 element `Encounter.status` as `SourceIsBroaderThanTarget`.\nThe target context `Encounter.status` is a modifier element, so this extension does not need to be defined as a modifier.\nNote that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.statusHistory|0.1.0",
      "element": [
        {
          "code": "Encounter.statusHistory",
          "display": "statusHistory",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.statusHistory` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.statusHistory` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nThe current status is always found in the current version of the resource, not the status history."
            }
          ]
        },
        {
          "code": "Encounter.statusHistory.status",
          "display": "status",
          "target": [
            {
              "code": "Extension.extension:status",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.statusHistory.status` is part of an existing definition because parent element `Encounter.statusHistory` requires a cross-version extension.\nElement `Encounter.statusHistory.status` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.statusHistory.status` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Encounter.statusHistory.period",
          "display": "period",
          "target": [
            {
              "code": "Extension.extension:period",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.statusHistory.period` is part of an existing definition because parent element `Encounter.statusHistory` requires a cross-version extension.\nElement `Encounter.statusHistory.period` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.statusHistory.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.classHistory|0.1.0",
      "element": [
        {
          "code": "Encounter.classHistory",
          "display": "classHistory",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.classHistory` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.classHistory` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Encounter.classHistory.class",
          "display": "class",
          "target": [
            {
              "code": "Extension.extension:class",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.classHistory.class` is part of an existing definition because parent element `Encounter.classHistory` requires a cross-version extension.\nElement `Encounter.classHistory.class` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.classHistory.class` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Encounter.classHistory.period",
          "display": "period",
          "target": [
            {
              "code": "Extension.extension:period",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.classHistory.period` is part of an existing definition because parent element `Encounter.classHistory` requires a cross-version extension.\nElement `Encounter.classHistory.period` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.classHistory.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.reasonReference|0.1.0",
      "element": [
        {
          "code": "Encounter.reasonReference",
          "display": "reasonReference",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.reasonReference` is mapped to FHIR R5 element `Encounter.reason.value` as `RelatedTo`.\nThe mappings for `Encounter.reasonReference` do not cover the following types: Reference.\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.diagnosis.condition|0.1.0",
      "element": [
        {
          "code": "Encounter.diagnosis.condition",
          "display": "condition",
          "target": [
            {
              "code": "Extension",
              "relationship": "equivalent",
              "comment": "Element `Encounter.diagnosis.condition` is mapped to FHIR R5 element `Encounter.diagnosis.condition` as `RelatedTo`.\nThe mappings for `Encounter.diagnosis.condition` do not cover the following types: Reference.\nThe mappings for `Encounter.diagnosis.condition` do not cover the following types based on type expansion: display, identifier, reference, type.\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.diagnosis.rank|0.1.0",
      "element": [
        {
          "code": "Encounter.diagnosis.rank",
          "display": "rank",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.diagnosis.rank` has a context of Encounter.diagnosis based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.diagnosis.rank` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.hospitalization.dietPreference|0.1.0",
      "element": [
        {
          "code": "Encounter.hospitalization.dietPreference",
          "display": "dietPreference",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.hospitalization.dietPreference` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.hospitalization.dietPreference` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).\nFor example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.hospitalization.specialCourtesy|0.1.0",
      "element": [
        {
          "code": "Encounter.hospitalization.specialCourtesy",
          "display": "specialCourtesy",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.hospitalization.specialCourtesy` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.hospitalization.specialCourtesy` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Encounter|4.3.0",
      "target": "http://hl7.org/fhir/4.3/StructureDefinition/extension-Encounter.hospitalization.specialArrangement|0.1.0",
      "element": [
        {
          "code": "Encounter.hospitalization.specialArrangement",
          "display": "specialArrangement",
          "target": [
            {
              "code": "Extension",
              "relationship": "source-is-broader-than-target",
              "comment": "Element `Encounter.hospitalization.specialArrangement` has a context of Encounter.admission based on following the parent source element upwards and mapping to `Encounter`.\nElement `Encounter.hospitalization.specialArrangement` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}