Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions

ConceptMap: R3EncounterElementMapToR5

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-Encounter-element-map-to-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3EncounterElementMapToR5

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Encounter to FHIR R5.

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


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

Source CodeRelationshipTarget CodeComment
Encounter.meta (meta)is broader thanEncounter.metaElement `Encounter.meta` is mapped to FHIR R5 element `Encounter.meta` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.meta` do not cover the following types: Meta. The mappings for `Encounter.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Encounter.implicitRules (implicitRules)is equivalent toEncounter.implicitRulesElement `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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Encounter.language (language)is equivalent toEncounter.languageElement `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 broader thanEncounter.textElement `Encounter.text` is mapped to FHIR R5 element `Encounter.text` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.text` do not cover the following types: Narrative. The mappings for `Encounter.text` do not cover the following types based on type expansion: div, status. 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 in formation is added later.
Encounter.contained (contained)is equivalent toEncounter.containedElement `Encounter.contained` is mapped to FHIR R5 element `Encounter.contained` as `SourceIsBroaderThanTarget`. 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.
Encounter.identifier (identifier)is broader thanEncounter.identifierElement `Encounter.identifier` is mapped to FHIR R5 element `Encounter.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.identifier` do not cover the following types: Identifier. The mappings for `Encounter.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Encounter.status (status)is broader thanEncounter.statusElement `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 detemine the appropraite transitions that may occur between statuses (and also classes). This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid.
Encounter.class (class)is equivalent toEncounter.classElement `Encounter.class` is mapped to FHIR R5 element `Encounter.class` as `SourceIsNarrowerThanTarget`.
Encounter.type (type)is equivalent toEncounter.typeElement `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.priority (priority)is equivalent toEncounter.priorityElement `Encounter.priority` is mapped to FHIR R5 element `Encounter.priority` as `Equivalent`.
Encounter.subject (subject)is broader thanEncounter.subjectElement `Encounter.subject` is mapped to FHIR R5 element `Encounter.subject` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.subject` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.subject` with unmapped reference targets: Group, Patient. While the encounter is always about the patient, the patient may 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 broader thanEncounter.episodeOfCareElement `Encounter.episodeOfCare` is mapped to FHIR R5 element `Encounter.episodeOfCare` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.episodeOfCare` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.episodeOfCare` with unmapped reference targets: EpisodeOfCare.
Encounter.incomingReferral (incomingReferral)is related toEncounter.basedOnElement `Encounter.incomingReferral` is mapped to FHIR R5 element `Encounter.basedOn` as `RelatedTo`. The mappings for `Encounter.incomingReferral` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.incomingReferral` with unmapped reference targets: ReferralRequest.
Encounter.participant (participant)is broader thanEncounter.participantElement `Encounter.participant` is mapped to FHIR R5 element `Encounter.participant` as `Equivalent`.
Encounter.participant.type (type)is equivalent toEncounter.participant.typeElement `Encounter.participant.type` is mapped to FHIR R5 element `Encounter.participant.type` as `Equivalent`. The participant type indicates how an individual partitipates 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 broader thanEncounter.participant.periodElement `Encounter.participant.period` is mapped to FHIR R5 element `Encounter.participant.period` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.participant.period` do not cover the following types: Period. The mappings for `Encounter.participant.period` do not cover the following types based on type expansion: end, start.
Encounter.participant.individual (individual)is broader thanEncounter.participant.actorElement `Encounter.participant.individual` is mapped to FHIR R5 element `Encounter.participant.actor` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.participant.individual` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.participant.individual` with unmapped reference targets: Practitioner, RelatedPerson.
Encounter.appointment (appointment)is broader thanEncounter.appointmentElement `Encounter.appointment` is mapped to FHIR R5 element `Encounter.appointment` as `RelatedTo`. The mappings for `Encounter.appointment` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.appointment` with unmapped reference targets: Appointment.
Encounter.period (period)is broader thanEncounter.actualPeriodElement `Encounter.period` is mapped to FHIR R5 element `Encounter.actualPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.period` do not cover the following types: Period. The mappings for `Encounter.period` do not cover the following types based on type expansion: end, start. If not (yet) known, the end of the Period may be omitted.
Encounter.length (length)is equivalent toEncounter.lengthElement `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.reason (reason)is narrower thanEncounter.reason.valueElement `Encounter.reason` 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.diagnosis (diagnosis)is broader thanEncounter.diagnosisElement `Encounter.diagnosis` is mapped to FHIR R5 element `Encounter.diagnosis` as `Equivalent`.
Encounter.diagnosis.condition (condition)is broader thanEncounter.diagnosis.conditionElement `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. 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.role (role)is narrower thanEncounter.diagnosis.useElement `Encounter.diagnosis.role` is mapped to FHIR R5 element `Encounter.diagnosis.use` as `SourceIsNarrowerThanTarget`.
Encounter.account (account)is broader thanEncounter.accountElement `Encounter.account` is mapped to FHIR R5 element `Encounter.account` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.account` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.account` with unmapped reference targets: Account. 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 thanEncounter.admissionElement `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 broader thanEncounter.admission.preAdmissionIdentifierElement `Encounter.hospitalization.preAdmissionIdentifier` is mapped to FHIR R5 element `Encounter.admission.preAdmissionIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.hospitalization.preAdmissionIdentifier` do not cover the following types: Identifier. The mappings for `Encounter.hospitalization.preAdmissionIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Encounter.hospitalization.origin (origin)is broader thanEncounter.admission.originElement `Encounter.hospitalization.origin` is mapped to FHIR R5 element `Encounter.admission.origin` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.hospitalization.origin` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.hospitalization.origin` with unmapped reference targets: Location.
Encounter.hospitalization.admitSource (admitSource)is equivalent toEncounter.admission.admitSourceElement `Encounter.hospitalization.admitSource` is mapped to FHIR R5 element `Encounter.admission.admitSource` as `Equivalent`.
Encounter.hospitalization.reAdmission (reAdmission)is equivalent toEncounter.admission.reAdmissionElement `Encounter.hospitalization.reAdmission` is mapped to FHIR R5 element `Encounter.admission.reAdmission` as `Equivalent`.
Encounter.hospitalization.destination (destination)is broader thanEncounter.admission.destinationElement `Encounter.hospitalization.destination` is mapped to FHIR R5 element `Encounter.admission.destination` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.hospitalization.destination` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.hospitalization.destination` with unmapped reference targets: Location.
Encounter.hospitalization.dischargeDisposition (dischargeDisposition)is equivalent toEncounter.admission.dischargeDispositionElement `Encounter.hospitalization.dischargeDisposition` is mapped to FHIR R5 element `Encounter.admission.dischargeDisposition` as `Equivalent`.
Encounter.location (location)is broader thanEncounter.locationElement `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 broader thanEncounter.location.locationElement `Encounter.location.location` is mapped to FHIR R5 element `Encounter.location.location` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.location.location` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.location.location` with unmapped reference targets: Location.
Encounter.location.status (status)is equivalent toEncounter.location.statusElement `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.period (period)is broader thanEncounter.location.periodElement `Encounter.location.period` is mapped to FHIR R5 element `Encounter.location.period` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.location.period` do not cover the following types: Period. The mappings for `Encounter.location.period` do not cover the following types based on type expansion: end, start.
Encounter.serviceProvider (serviceProvider)is broader thanEncounter.serviceProviderElement `Encounter.serviceProvider` is mapped to FHIR R5 element `Encounter.serviceProvider` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.serviceProvider` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.serviceProvider` with unmapped reference targets: Organization.
Encounter.partOf (partOf)is broader thanEncounter.partOfElement `Encounter.partOf` is mapped to FHIR R5 element `Encounter.partOf` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.partOf` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Encounter.partOf` with unmapped reference targets: Encounter. This is also used for associating a child's encounter back to the mother's encounter. Refer to the Notes section in the Patient resource for further details.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `Encounter.meta` is mapped to FHIR R5 element `Encounter.meta` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.meta` do not cover the following types: Meta. The mappings for `Encounter.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.text (text)is equivalent toExtension (STU3: text additional types)Element `Encounter.text` is mapped to FHIR R5 element `Encounter.text` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.text` do not cover the following types: Narrative. The mappings for `Encounter.text` do not cover the following types based on type expansion: div, status. 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 in formation is added later.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.identifier (identifier)is equivalent toExtension (STU3: identifier additional types)Element `Encounter.identifier` is mapped to FHIR R5 element `Encounter.identifier` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.identifier` do not cover the following types: Identifier. The mappings for `Encounter.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: planned | arrived | triaged | in-progress | onleave | finished | cancelled +version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.status (status)is equivalent toExtension (STU3: planned | arrived | triaged | in-progress | onleave | finished | cancelled +)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 detemine the appropraite transitions that may occur between statuses (and also classes). This element is labeled as a modifier because the status contains codes that mark the encounter as not currently valid.

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

Source CodeRelationshipTarget CodeComment
Encounter.statusHistory (statusHistory)is equivalent toExtension (STU3: 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 equivalent toExtension.extension:status (STU3: planned | arrived | triaged | in-progress | onleave | finished | cancelled + (new))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 equivalent toExtension.extension:period (STU3: 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 7 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: List of past encounter classes (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.classHistory (classHistory)is equivalent toExtension (STU3: 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 equivalent toExtension.extension:class (STU3: 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 equivalent toExtension.extension:period (STU3: 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 8 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: period additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.participant.period (period)is equivalent toExtension (STU3: period additional types)Element `Encounter.participant.period` is mapped to FHIR R5 element `Encounter.participant.period` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.participant.period` do not cover the following types: Period. The mappings for `Encounter.participant.period` do not cover the following types based on type expansion: end, start.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: The start and end time of the encounter additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.period (period)is broader thanExtension (STU3: The start and end time of the encounter additional types)Element `Encounter.period` is mapped to FHIR R5 element `Encounter.actualPeriod` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.period` do not cover the following types: Period. The mappings for `Encounter.period` do not cover the following types based on type expansion: end, start. If not (yet) known, the end of the Period may be omitted.

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: Reason the encounter takes place (resource) additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.diagnosis.condition (condition)is equivalent toExtension (STU3: Reason the encounter takes place (resource) additional types)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. 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).

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

Source CodeRelationshipTarget CodeComment
Encounter.diagnosis.rank (rank)is equivalent toExtension (STU3: 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 12 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: preAdmissionIdentifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.hospitalization.preAdmissionIdentifier (preAdmissionIdentifier)is broader thanExtension (STU3: preAdmissionIdentifier additional types)Element `Encounter.hospitalization.preAdmissionIdentifier` is mapped to FHIR R5 element `Encounter.admission.preAdmissionIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.hospitalization.preAdmissionIdentifier` do not cover the following types: Identifier. The mappings for `Encounter.hospitalization.preAdmissionIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

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

Source CodeRelationshipTarget CodeComment
Encounter.hospitalization.dietPreference (dietPreference)is equivalent toExtension (STU3: 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 14 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: Special courtesies (VIP, board member) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.hospitalization.specialCourtesy (specialCourtesy)is equivalent toExtension (STU3: 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 15 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: Wheelchair, translator, stretcher, etc. (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.hospitalization.specialArrangement (specialArrangement)is equivalent toExtension (STU3: 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).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|3.0.2 to STU3: period additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Encounter.location.period (period)is equivalent toExtension (STU3: period additional types)Element `Encounter.location.period` is mapped to FHIR R5 element `Encounter.location.period` as `SourceIsBroaderThanTarget`. The mappings for `Encounter.location.period` do not cover the following types: Period. The mappings for `Encounter.location.period` do not cover the following types based on type expansion: end, start.