R3EncounterElementMapToR4 - Extensions for Using Data Elements from FHIR STU3 in FHIR R4 v0.1.0

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

ConceptMap: R3EncounterElementMapToR4

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

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

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

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

Source Code

Relationship

Target Code

Comment

Encounter.meta (meta)

is equivalent to

Encounter.meta

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

Encounter.implicitRules (implicitRules)

is equivalent to

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. 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 to

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 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 R4 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 in formation is added later.

Encounter.contained (contained)

is equivalent to

Encounter.contained

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.

Encounter.identifier (identifier)

is equivalent to

Encounter.identifier

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

Encounter.status (status)

is equivalent to

Encounter.status

Element `Encounter.status` is mapped to FHIR R4 element `Encounter.status` as `Equivalent`. 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.statusHistory (statusHistory)

maps to wider concept

Encounter.statusHistory

Element `Encounter.statusHistory` is mapped to FHIR R4 element `Encounter.statusHistory` as `Equivalent`. The current status is always found in the current version of the resource, not the status history.

Encounter.statusHistory.status (status)

is equivalent to

Encounter.statusHistory.status

Element `Encounter.statusHistory.status` is mapped to FHIR R4 element `Encounter.statusHistory.status` as `Equivalent`.

Encounter.statusHistory.period (period)

is equivalent to

Encounter.statusHistory.period

Element `Encounter.statusHistory.period` is mapped to FHIR R4 element `Encounter.statusHistory.period` as `Equivalent`.

Encounter.class (class)

is equivalent to

Encounter.class

Element `Encounter.class` is mapped to FHIR R4 element `Encounter.class` as `Equivalent`.

Encounter.classHistory (classHistory)

maps to wider concept

Encounter.classHistory

Element `Encounter.classHistory` is mapped to FHIR R4 element `Encounter.classHistory` as `Equivalent`.

Encounter.classHistory.class (class)

is equivalent to

Encounter.classHistory.class

Element `Encounter.classHistory.class` is mapped to FHIR R4 element `Encounter.classHistory.class` as `Equivalent`.

Encounter.classHistory.period (period)

is equivalent to

Encounter.classHistory.period

Element `Encounter.classHistory.period` is mapped to FHIR R4 element `Encounter.classHistory.period` as `Equivalent`.

Encounter.type (type)

is equivalent to

Encounter.type

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..*.

Encounter.priority (priority)

is equivalent to

Encounter.priority

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

Encounter.subject (subject)

is equivalent to

Encounter.subject

Element `Encounter.subject` is mapped to FHIR R4 element `Encounter.subject` as `Equivalent`. 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 equivalent to

Encounter.episodeOfCare

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

Encounter.incomingReferral (incomingReferral)

narrower

Encounter.basedOn

Element `Encounter.incomingReferral` is mapped to FHIR R4 element `Encounter.basedOn` as `SourceIsNarrowerThanTarget`.

Encounter.participant (participant)

maps to wider concept

Encounter.participant

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

Encounter.participant.type (type)

is equivalent to

Encounter.participant.type

Element `Encounter.participant.type` is mapped to FHIR R4 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 equivalent to

Encounter.participant.period

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

Encounter.participant.individual (individual)

is equivalent to

Encounter.participant.individual

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

Encounter.appointment (appointment)

is equivalent to

Encounter.appointment

Element `Encounter.appointment` is mapped to FHIR R4 element `Encounter.appointment` as `SourceIsNarrowerThanTarget`.

Encounter.period (period)

is equivalent to

Encounter.period

Element `Encounter.period` is mapped to FHIR R4 element `Encounter.period` 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 R4 element `Encounter.length` as `Equivalent`. May differ from the time the Encounter.period lasted because of leave of absence.

Encounter.reason (reason)

is equivalent to

Encounter.reasonCode

Element `Encounter.reason` is mapped to FHIR R4 element `Encounter.reasonCode` as `Equivalent`. 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)

maps to wider concept

Encounter.diagnosis

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

Encounter.diagnosis.condition (condition)

is equivalent to

Encounter.diagnosis.condition

Element `Encounter.diagnosis.condition` is mapped to FHIR R4 element `Encounter.diagnosis.condition` as `Equivalent`. 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 equivalent to

Encounter.diagnosis.use

Element `Encounter.diagnosis.role` is mapped to FHIR R4 element `Encounter.diagnosis.use` as `Equivalent`.

Encounter.diagnosis.rank (rank)

is equivalent to

Encounter.diagnosis.rank

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

Encounter.account (account)

is equivalent to

Encounter.account

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.

Encounter.hospitalization (hospitalization)

maps to wider concept

Encounter.hospitalization

Element `Encounter.hospitalization` 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 hospitalization record.

Encounter.hospitalization.preAdmissionIdentifier (preAdmissionIdentifier)

is equivalent to

Encounter.hospitalization.preAdmissionIdentifier

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

Encounter.hospitalization.origin (origin)

is equivalent to

Encounter.hospitalization.origin

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

Encounter.hospitalization.admitSource (admitSource)

is equivalent to

Encounter.hospitalization.admitSource

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

Encounter.hospitalization.reAdmission (reAdmission)

is equivalent to

Encounter.hospitalization.reAdmission

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

Encounter.hospitalization.dietPreference (dietPreference)

is equivalent to

Encounter.hospitalization.dietPreference

Element `Encounter.hospitalization.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).

Encounter.hospitalization.specialCourtesy (specialCourtesy)

is equivalent to

Encounter.hospitalization.specialCourtesy

Element `Encounter.hospitalization.specialCourtesy` is mapped to FHIR R4 element `Encounter.hospitalization.specialCourtesy` as `Equivalent`.

Encounter.hospitalization.specialArrangement (specialArrangement)

is equivalent to

Encounter.hospitalization.specialArrangement

Element `Encounter.hospitalization.specialArrangement` is mapped to FHIR R4 element `Encounter.hospitalization.specialArrangement` as `Equivalent`.

Encounter.hospitalization.destination (destination)

is equivalent to

Encounter.hospitalization.destination

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

Encounter.hospitalization.dischargeDisposition (dischargeDisposition)

is equivalent to

Encounter.hospitalization.dischargeDisposition

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

Encounter.location (location)

maps to wider concept

Encounter.location

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".

Encounter.location.location (location)

is equivalent to

Encounter.location.location

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

Encounter.location.status (status)

is equivalent to

Encounter.location.status

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.

Encounter.location.period (period)

is equivalent to

Encounter.location.period

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

Encounter.serviceProvider (serviceProvider)

is equivalent to

Encounter.serviceProvider

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

Encounter.partOf (partOf)

is equivalent to

Encounter.partOf

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.