R5-Encounter-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-Encounter-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-Encounter-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/Encounter|5.0.0 to Encounterversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 Codes from Encounter Encounter.meta meta is equivalent to Encounter.meta Encounter.meta Element `Encounter.meta` is mapped to FHIR R4 element `Encounter.meta` as `Equivalent`. Encounter.implicitRules implicitRules is equivalent to Encounter.implicitRules Encounter.implicitRules Element `Encounter.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. Encounter.language language is equivalent to Encounter.language Encounter.language Element `Encounter.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 spec…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-Encounter-element-map-to-R4
  l: R5-Encounter-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5EncounterElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 Encounter to FHIR R4 Encounter
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:45.172613-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 Encounter to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/Encounter
    l: Encounter
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Encounter
    l: Encounter
  target version:
    v: 4.0.1
  element:
    code:
      v: Encounter.meta
    display:
      v: meta
    target:
      code:
        v: Encounter.meta
      display:
        v: Encounter.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.meta` is mapped to FHIR R4 element `Encounter.meta` as `Equivalent`.
  element:
    code:
      v: Encounter.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Encounter.implicitRules
      display:
        v: Encounter.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.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.
  element:
    code:
      v: Encounter.language
    display:
      v: language
    target:
      code:
        v: Encounter.language
      display:
        v: Encounter.language
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.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).
  element:
    code:
      v: Encounter.text
    display:
      v: text
    target:
      code:
        v: Encounter.text
      display:
        v: Encounter.text
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.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.
  element:
    code:
      v: Encounter.contained
    display:
      v: contained
    target:
      code:
        v: Encounter.contained
      display:
        v: Encounter.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.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.
  element:
    code:
      v: Encounter.identifier
    display:
      v: identifier
    target:
      code:
        v: Encounter.identifier
      display:
        v: Encounter.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `Encounter.identifier` is mapped to FHIR R4 element `Encounter.identifier` as `Equivalent`.
  element:
    code:
      v: Encounter.status
    display:
      v: status
    target:
      code:
        v: Encounter.status
      display:
        v: Encounter.status
      equivalence:
        v: wider
      comment:
        v: Element `Encounter.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).
  element:
    code:
      v: Encounter.class
    display:
      v: class
    target:
      code:
        v: Encounter.class
      display:
        v: Encounter.class
      equivalence:
        v: wider
      comment:
        v: Element `Encounter.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.class` do not cover the following types: CodeableConcept. The mappings for `Encounter.class` do not cover the following types based on type expansion: text.

code:
  v: Encounter.priority
display:
  v: priority
target:
  code:
    v: Encounter.priority
  display:
    v: Encounter.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.priority` is mapped to FHIR R4 element `Encounter.priority` as `Equivalent`.

code:
  v: Encounter.type
display:
  v: type
target:
  code:
    v: Encounter.type
  display:
    v: Encounter.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.type` is mapped to FHIR R4 element `Encounter.type` as `Equivalent`. Since there are many ways to further classify encounters, this element is 0..*.

code:
  v: Encounter.serviceType
display:
  v: serviceType
target:
  code:
    v: Encounter.serviceType
  display:
    v: Encounter.serviceType
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.serviceType` do not cover the following types: CodeableReference. The mappings for `Encounter.serviceType` do not cover the following types based on type expansion: reference.

code:
  v: Encounter.subject
display:
  v: subject
target:
  code:
    v: Encounter.subject
  display:
    v: Encounter.subject
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.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).

code:
  v: Encounter.episodeOfCare
display:
  v: episodeOfCare
target:
  code:
    v: Encounter.episodeOfCare
  display:
    v: Encounter.episodeOfCare
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.episodeOfCare` is mapped to FHIR R4 element `Encounter.episodeOfCare` as `Equivalent`.

code:
  v: Encounter.basedOn
display:
  v: basedOn
target:
  code:
    v: Encounter.basedOn
  display:
    v: Encounter.basedOn
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.basedOn` is mapped to FHIR R4 element `Encounter.basedOn` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Encounter.basedOn` with unmapped reference targets: CarePlan, DeviceRequest, MedicationRequest.

code:
  v: Encounter.partOf
display:
  v: partOf
target:
  code:
    v: Encounter.partOf
  display:
    v: Encounter.partOf
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.partOf` is mapped to FHIR R4 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.

code:
  v: Encounter.serviceProvider
display:
  v: serviceProvider
target:
  code:
    v: Encounter.serviceProvider
  display:
    v: Encounter.serviceProvider
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.serviceProvider` is mapped to FHIR R4 element `Encounter.serviceProvider` as `Equivalent`.

code:
  v: Encounter.participant
display:
  v: participant
target:
  code:
    v: Encounter.participant
  display:
    v: Encounter.participant
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.participant` is mapped to FHIR R4 element `Encounter.participant` as `Equivalent`. Any Patient or Group present in the participation.actor must also be the subject, though the subject may be absent from the participation.actor for cases where the patient (or group) is not present, such as during a case review conference.

code:
  v: Encounter.participant.type
display:
  v: type
target:
  code:
    v: Encounter.participant.type
  display:
    v: Encounter.participant.type
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.participant.type` is mapped to FHIR R4 element `Encounter.participant.type` as `Equivalent`. The participant type indicates how an individual actor 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:
  v: Encounter.participant.period
display:
  v: period
target:
  code:
    v: Encounter.participant.period
  display:
    v: Encounter.participant.period
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.participant.period` is mapped to FHIR R4 element `Encounter.participant.period` as `Equivalent`.

code:
  v: Encounter.participant.actor
display:
  v: actor
target:
  code:
    v: Encounter.participant.individual
  display:
    v: Encounter.participant.individual
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.participant.actor` is mapped to FHIR R4 element `Encounter.participant.individual` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Encounter.participant.actor` with unmapped reference targets: Device, Group, HealthcareService, Patient. For planning purposes, Appointments may include a CareTeam participant to indicate that one specific person from the CareTeam will be assigned, but that assignment might not happen until the Encounter begins. Hence CareTeam is not included in Encounter.participant, as the specific individual should be assigned and represented as a Practitioner or other person resource. Similarly, Location can be included in Appointment.participant to assist with planning. However, the patient location is tracked on the Encounter in the Encounter.location property to allow for additional metadata and history to be recorded. The role of the participant can be used to declare what the actor will be doing in the scope of this encounter participation. If the individual is not specified during planning, then it is expected that the individual will be filled in at a later stage prior to the encounter commencing.

code:
  v: Encounter.appointment
display:
  v: appointment
target:
  code:
    v: Encounter.appointment
  display:
    v: Encounter.appointment
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.appointment` is mapped to FHIR R4 element `Encounter.appointment` as `Equivalent`.

code:
  v: Encounter.actualPeriod
display:
  v: actualPeriod
target:
  code:
    v: Encounter.period
  display:
    v: Encounter.period
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.actualPeriod` is mapped to FHIR R4 element `Encounter.period` as `Equivalent`. If not (yet) known, the end of the Period may be omitted.

code:
  v: Encounter.length
display:
  v: length
target:
  code:
    v: Encounter.length
  display:
    v: Encounter.length
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.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).

code:
  v: Encounter.reason
display:
  v: reason
target:
  code:
    v: Encounter.reasonCode
  display:
    v: Encounter.reasonCode
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.reason` is mapped to FHIR R4 element `Encounter.reasonCode` as `Equivalent`. The reason communicates what medical problem the patient has that should be addressed during the episode of care. This reason could be patient reported complaint, a clinical indication that was determined in a previous encounter or episode of care, or some planned care such as an immunization recommendation. In the case where you have a primary reason, but are expecting to also address other problems, you can list the primary reason with a use code of 'Chief Complaint', while the other problems being addressed would have a use code of 'Reason for Visit'. Examples: * pregnancy would use HealthcareService or a coding as the reason * patient home monitoring could use Condition as the reason

code:
  v: Encounter.reason.use
display:
  v: use
target:
  code:
    v: Encounter.reasonCode
  display:
    v: Encounter.reasonCode
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.reason.use` is mapped to FHIR R4 element `Encounter.reasonCode` as `Equivalent`.

code:
  v: Encounter.reason.value
display:
  v: value
target:
  code:
    v: Encounter.reasonCode
  display:
    v: Encounter.reasonCode
  equivalence:
    v: relatedto
  comment:
    v: Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonCode` as `SourceIsBroaderThanTarget`. Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.reason.value` do not cover the following types: CodeableReference.
target:
  code:
    v: Encounter.reasonReference
  display:
    v: Encounter.reasonReference
  equivalence:
    v: relatedto
  comment:
    v: Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonCode` as `SourceIsBroaderThanTarget`. Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.reason.value` do not cover the following types: CodeableReference.

code:
  v: Encounter.diagnosis
display:
  v: diagnosis
target:
  code:
    v: Encounter.diagnosis
  display:
    v: Encounter.diagnosis
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.diagnosis` is mapped to FHIR R4 element `Encounter.diagnosis` as `Equivalent`. Also note that for the purpose of billing, the diagnoses are recorded in the account where they can be ranked appropriately for how the invoicing/claiming documentation needs to be prepared.

code:
  v: Encounter.diagnosis.condition
display:
  v: condition
target:
  code:
    v: Encounter.diagnosis.condition
  display:
    v: Encounter.diagnosis.condition
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.diagnosis.condition` is mapped to FHIR R4 element `Encounter.diagnosis.condition` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.diagnosis.condition` do not cover the following types: CodeableReference. The mappings for `Encounter.diagnosis.condition` do not cover the following types based on type expansion: concept.

code:
  v: Encounter.diagnosis.use
display:
  v: use
target:
  code:
    v: Encounter.diagnosis.use
  display:
    v: Encounter.diagnosis.use
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.diagnosis.use` is mapped to FHIR R4 element `Encounter.diagnosis.use` as `SourceIsBroaderThanTarget`.

code:
  v: Encounter.account
display:
  v: account
target:
  code:
    v: Encounter.account
  display:
    v: Encounter.account
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.account` is mapped to FHIR R4 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.

code:
  v: Encounter.dietPreference
display:
  v: dietPreference
target:
  code:
    v: Encounter.hospitalization.dietPreference
  display:
    v: Encounter.hospitalization.dietPreference
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.dietPreference` is mapped to FHIR R4 element `Encounter.hospitalization.dietPreference` as `Equivalent`. For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

code:
  v: Encounter.specialArrangement
display:
  v: specialArrangement
target:
  code:
    v: Encounter.hospitalization.specialArrangement
  display:
    v: Encounter.hospitalization.specialArrangement
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.specialArrangement` is mapped to FHIR R4 element `Encounter.hospitalization.specialArrangement` as `Equivalent`.

code:
  v: Encounter.specialCourtesy
display:
  v: specialCourtesy
target:
  code:
    v: Encounter.hospitalization.specialCourtesy
  display:
    v: Encounter.hospitalization.specialCourtesy
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.specialCourtesy` is mapped to FHIR R4 element `Encounter.hospitalization.specialCourtesy` as `Equivalent`. Although the specialCourtesy property can contain values like VIP, the purpose of this field is intended to be used for flagging additional `benefits` that might occur for the patient during the encounter. It could include things like the patient is to have a private room, special room features, receive a friendly visit from hospital adminisitration, or should be briefed on treatment by senior staff during the stay. It is not specifically intended to be used for securing the specific record - that is the purpose of the security meta tag, and where appropriate, both fields could be used.

code:
  v: Encounter.admission
display:
  v: admission
target:
  code:
    v: Encounter.hospitalization
  display:
    v: Encounter.hospitalization
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.admission` is mapped to FHIR R4 element `Encounter.hospitalization` 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 admission record.

code:
  v: Encounter.admission.preAdmissionIdentifier
display:
  v: preAdmissionIdentifier
target:
  code:
    v: Encounter.hospitalization.preAdmissionIdentifier
  display:
    v: Encounter.hospitalization.preAdmissionIdentifier
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.preAdmissionIdentifier` is mapped to FHIR R4 element `Encounter.hospitalization.preAdmissionIdentifier` as `Equivalent`.

code:
  v: Encounter.admission.origin
display:
  v: origin
target:
  code:
    v: Encounter.hospitalization.origin
  display:
    v: Encounter.hospitalization.origin
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.origin` is mapped to FHIR R4 element `Encounter.hospitalization.origin` as `Equivalent`.

code:
  v: Encounter.admission.admitSource
display:
  v: admitSource
target:
  code:
    v: Encounter.hospitalization.admitSource
  display:
    v: Encounter.hospitalization.admitSource
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.admitSource` is mapped to FHIR R4 element `Encounter.hospitalization.admitSource` as `Equivalent`.

code:
  v: Encounter.admission.reAdmission
display:
  v: reAdmission
target:
  code:
    v: Encounter.hospitalization.reAdmission
  display:
    v: Encounter.hospitalization.reAdmission
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.reAdmission` is mapped to FHIR R4 element `Encounter.hospitalization.reAdmission` as `Equivalent`.

code:
  v: Encounter.admission.destination
display:
  v: destination
target:
  code:
    v: Encounter.hospitalization.destination
  display:
    v: Encounter.hospitalization.destination
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.destination` is mapped to FHIR R4 element `Encounter.hospitalization.destination` as `Equivalent`.

code:
  v: Encounter.admission.dischargeDisposition
display:
  v: dischargeDisposition
target:
  code:
    v: Encounter.hospitalization.dischargeDisposition
  display:
    v: Encounter.hospitalization.dischargeDisposition
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.admission.dischargeDisposition` is mapped to FHIR R4 element `Encounter.hospitalization.dischargeDisposition` as `Equivalent`.

code:
  v: Encounter.location
display:
  v: location
target:
  code:
    v: Encounter.location
  display:
    v: Encounter.location
  equivalence:
    v: wider
  comment:
    v: Element `Encounter.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".

code:
  v: Encounter.location.location
display:
  v: location
target:
  code:
    v: Encounter.location.location
  display:
    v: Encounter.location.location
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.location.location` is mapped to FHIR R4 element `Encounter.location.location` as `Equivalent`.

code:
  v: Encounter.location.status
display:
  v: status
target:
  code:
    v: Encounter.location.status
  display:
    v: Encounter.location.status
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.location.status` is mapped to FHIR R4 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.

code:
  v: Encounter.location.form
display:
  v: form
target:
  code:
    v: Encounter.location.physicalType
  display:
    v: Encounter.location.physicalType
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.location.form` is mapped to FHIR R4 element `Encounter.location.physicalType` 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.

code:
  v: Encounter.location.period
display:
  v: period
target:
  code:
    v: Encounter.location.period
  display:
    v: Encounter.location.period
  equivalence:
    v: equivalent
  comment:
    v: Element `Encounter.location.period` is mapped to FHIR R4 element `Encounter.location.period` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.status
  l: extension-Encounter.status
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Encounter.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).

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.class
  l: extension-Encounter.class
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.class
  display:
    v: class
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Encounter.class` is mapped to FHIR R4 element `Encounter.class` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.class` do not cover the following types: CodeableConcept. The mappings for `Encounter.class` do not cover the following types based on type expansion: text.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.serviceType
  l: extension-Encounter.serviceType
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.serviceType
  display:
    v: serviceType
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Encounter.serviceType` is mapped to FHIR R4 element `Encounter.serviceType` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.serviceType` do not cover the following types: CodeableReference. The mappings for `Encounter.serviceType` do not cover the following types based on type expansion: reference.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.subjectStatus
  l: extension-Encounter.subjectStatus
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.subjectStatus
  display:
    v: subjectStatus
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.subjectStatus` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.subjectStatus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Different use-cases are likely to have different permitted transitions between states, such as an Emergency department could use `arrived` when the patient first presents, then `triaged` once has been assessed by a nurse, then `receiving-care` once treatment begins, however other sectors may use a different set of these values, or their own custom set in place of this example valueset provided.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.careTeam
  l: extension-Encounter.careTeam
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.careTeam
  display:
    v: careTeam
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.careTeam` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.careTeam` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.virtualService
  l: extension-Encounter.virtualService
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.virtualService
  display:
    v: virtualService
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.virtualService` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.virtualService` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There are two types of virtual meetings that often exist: * a persistent, virtual meeting room that can only be used for a single purpose at a time, * and a dynamic virtual meeting room that is generated on demand for a specific purpose. Implementers may consider using Location.virtualService for persistent meeting rooms. If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail can be applied to the Encounter.participant BackboneElement.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedStartDate
  l: extension-Encounter.plannedStartDate
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.plannedStartDate
  display:
    v: plannedStartDate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.plannedStartDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.plannedStartDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.plannedEndDate
  l: extension-Encounter.plannedEndDate
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.plannedEndDate
  display:
    v: plannedEndDate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.plannedEndDate` has a context of Encounter based on following the parent source element upwards and mapping to `Encounter`. Element `Encounter.plannedEndDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.reason.value
  l: extension-Encounter.reason.value
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.reason.value
  display:
    v: value
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonCode` as `SourceIsBroaderThanTarget`. Element `Encounter.reason.value` is mapped to FHIR R4 element `Encounter.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.reason.value` do not cover the following types: CodeableReference.

source:
  v: http://hl7.org/fhir/StructureDefinition/Encounter
  l: Encounter
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-Encounter.diagnosis.condition
  l: extension-Encounter.diagnosis.condition
target version:
  v: 0.1.0
element:
  code:
    v: Encounter.diagnosis.condition
  display:
    v: condition
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `Encounter.diagnosis.condition` is mapped to FHIR R4 element `Encounter.diagnosis.condition` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.diagnosis.condition` do not cover the following types: CodeableReference. The mappings for `Encounter.diagnosis.condition` do not cover the following types based on type expansion: concept.