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 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 Encounter.text 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. Encounter.contained contained is equivalent to Encounter.contained 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. 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 Encounter.identifier Element `Encounter.identifier` is mapped to FHIR R4 element `Encounter.identifier` as `Equivalent`. Encounter.status status maps to wider concept Encounter.status Encounter.status 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). Encounter.class class maps to wider concept Encounter.class Encounter.class 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. Encounter.priority priority is equivalent to Encounter.priority Encounter.priority Element `Encounter.priority` is mapped to FHIR R4 element `Encounter.priority` as `Equivalent`. Encounter.type type is equivalent to Encounter.type 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.serviceType serviceType maps to wider concept Encounter.serviceType Encounter.serviceType 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. Encounter.subject subject is equivalent to Encounter.subject 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 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 Encounter.episodeOfCare Element `Encounter.episodeOfCare` is mapped to FHIR R4 element `Encounter.episodeOfCare` as `Equivalent`. Encounter.basedOn basedOn maps to wider concept Encounter.basedOn Encounter.basedOn 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. Encounter.partOf partOf is equivalent to Encounter.partOf 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.#xD;#xD;Refer to the Notes section in the Patient resource for further details. Encounter.serviceProvider serviceProvider is equivalent to Encounter.serviceProvider Encounter.serviceProvider Element `Encounter.serviceProvider` is mapped to FHIR R4 element `Encounter.serviceProvider` as `Equivalent`. Encounter.participant participant maps to wider concept Encounter.participant Encounter.participant 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. Encounter.participant.type type is equivalent to Encounter.participant.type 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 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. Encounter.participant.period period is equivalent to Encounter.participant.period Encounter.participant.period Element `Encounter.participant.period` is mapped to FHIR R4 element `Encounter.participant.period` as `Equivalent`. Encounter.participant.actor actor maps to wider concept Encounter.participant.individual Encounter.participant.individual 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.#xD;#xD;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.#xD;#xD;The role of the participant can be used to declare what the actor will be doing in the scope of this encounter participation.#xD;#xD;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. Encounter.appointment appointment is equivalent to Encounter.appointment Encounter.appointment Element `Encounter.appointment` is mapped to FHIR R4 element `Encounter.appointment` as `Equivalent`. Encounter.actualPeriod actualPeriod is equivalent to Encounter.period Encounter.period 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. Encounter.length length is equivalent to Encounter.length Encounter.length 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.#xD;#xD;May differ from the time in `Encounter.period` due to leave of absence(s). Encounter.reason reason maps to wider concept Encounter.reasonCode Encounter.reasonCode 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'.#xD;#xD;Examples:#xD; * pregnancy would use HealthcareService or a coding as the reason#xD; * patient home monitoring could use Condition as the reason Encounter.reason.use use is equivalent to Encounter.reasonCode Encounter.reasonCode Element `Encounter.reason.use` is mapped to FHIR R4 element `Encounter.reasonCode` as `Equivalent`. Encounter.reason.value value is related to Encounter.reasonCode Encounter.reasonCode 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. is related to Encounter.reasonReference Encounter.reasonReference 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. Encounter.diagnosis diagnosis maps to wider concept Encounter.diagnosis Encounter.diagnosis 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. Encounter.diagnosis.condition condition maps to wider concept Encounter.diagnosis.condition Encounter.diagnosis.condition 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. Encounter.diagnosis.use use is equivalent to Encounter.diagnosis.use Encounter.diagnosis.use Element `Encounter.diagnosis.use` is mapped to FHIR R4 element `Encounter.diagnosis.use` as `SourceIsBroaderThanTarget`. Encounter.account account is equivalent to Encounter.account 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.dietPreference dietPreference is equivalent to Encounter.hospitalization.dietPreference Encounter.hospitalization.dietPreference 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). Encounter.specialArrangement specialArrangement is equivalent to Encounter.hospitalization.specialArrangement Encounter.hospitalization.specialArrangement Element `Encounter.specialArrangement` is mapped to FHIR R4 element `Encounter.hospitalization.specialArrangement` as `Equivalent`. Encounter.specialCourtesy specialCourtesy is equivalent to Encounter.hospitalization.specialCourtesy Encounter.hospitalization.specialCourtesy 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.#xD;#xD;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.#xD;#xD;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. Encounter.admission admission maps to wider concept Encounter.hospitalization Encounter.hospitalization 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.#xD;#xD;The duration recorded in the period of this encounter covers the entire scope of this admission record. Encounter.admission.preAdmissionIdentifier preAdmissionIdentifier is equivalent to Encounter.hospitalization.preAdmissionIdentifier Encounter.hospitalization.preAdmissionIdentifier Element `Encounter.admission.preAdmissionIdentifier` is mapped to FHIR R4 element `Encounter.hospitalization.preAdmissionIdentifier` as `Equivalent`. Encounter.admission.origin origin is equivalent to Encounter.hospitalization.origin Encounter.hospitalization.origin Element `Encounter.admission.origin` is mapped to FHIR R4 element `Encounter.hospitalization.origin` as `Equivalent`. Encounter.admission.admitSource admitSource is equivalent to Encounter.hospitalization.admitSource Encounter.hospitalization.admitSource Element `Encounter.admission.admitSource` is mapped to FHIR R4 element `Encounter.hospitalization.admitSource` as `Equivalent`. Encounter.admission.reAdmission reAdmission is equivalent to Encounter.hospitalization.reAdmission Encounter.hospitalization.reAdmission Element `Encounter.admission.reAdmission` is mapped to FHIR R4 element `Encounter.hospitalization.reAdmission` as `Equivalent`. Encounter.admission.destination destination is equivalent to Encounter.hospitalization.destination Encounter.hospitalization.destination Element `Encounter.admission.destination` is mapped to FHIR R4 element `Encounter.hospitalization.destination` as `Equivalent`. Encounter.admission.dischargeDisposition dischargeDisposition is equivalent to Encounter.hospitalization.dischargeDisposition Encounter.hospitalization.dischargeDisposition Element `Encounter.admission.dischargeDisposition` is mapped to FHIR R4 element `Encounter.hospitalization.dischargeDisposition` as `Equivalent`. Encounter.location location maps to wider concept Encounter.location 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 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 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.form form is equivalent to Encounter.location.physicalType Encounter.location.physicalType 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. Encounter.location.period period is equivalent to Encounter.location.period Encounter.location.period Element `Encounter.location.period` is mapped to FHIR R4 element `Encounter.location.period` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknownversion: 0.1.0) Source Code Relationship Target Code Comment Encounter.status (status) is equivalent to Extension (R5: planned | in-progress | on-hold | discharged | completed | cancelled | discontinued | entered-in-error | unknown) 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). Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: Classification of patient encounter context - e.g. Inpatient, outpatient additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Encounter.class (class) is equivalent to Extension (R5: Classification of patient encounter context - e.g. Inpatient, outpatient additional types) 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. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: serviceType additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Encounter.serviceType (serviceType) is equivalent to Extension (R5: serviceType additional types) 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. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: The current status of the subject in relation to the Encounter (new)version: 0.1.0) Source Code Relationship Target Code Comment Encounter.subjectStatus (subjectStatus) maps to wider concept Extension (R5: The current status of the subject in relation to the Encounter (new)) 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. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: The group(s) that are allocated to participate in this encounter (new)version: 0.1.0) Source Code Relationship Target Code Comment Encounter.careTeam (careTeam) maps to wider concept Extension (R5: The group(s) that are allocated to participate in this encounter (new)) 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). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: Connection details of a virtual service (e.g. conference call) (new)version: 0.1.0) Source Code Relationship Target Code Comment Encounter.virtualService (virtualService) maps to wider concept Extension (R5: Connection details of a virtual service (e.g. conference call) (new)) 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:#xD;#xD;* a persistent, virtual meeting room that can only be used for a single purpose at a time, #xD;* and a dynamic virtual meeting room that is generated on demand for a specific purpose.#xD;#xD;Implementers may consider using Location.virtualService for persistent meeting rooms.#xD;#xD;If each participant would have a different meeting link, an extension using the VirtualServiceContactDetail can be applied to the Encounter.participant BackboneElement. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: The planned start date/time (or admission date) of the encounter (new)version: 0.1.0) Source Code Relationship Target Code Comment Encounter.plannedStartDate (plannedStartDate) maps to wider concept Extension (R5: The planned start date/time (or admission date) of the encounter (new)) 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). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: The planned end date/time (or discharge date) of the encounter (new)version: 0.1.0) Source Code Relationship Target Code Comment Encounter.plannedEndDate (plannedEndDate) maps to wider concept Extension (R5: The planned end date/time (or discharge date) of the encounter (new)) 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). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: Reason the encounter takes place (core or reference) additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Encounter.reason.value (value) maps to wider concept Extension (R5: Reason the encounter takes place (core or reference) additional types) 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Encounter|5.0.0 to R5: The diagnosis relevant to the encounter additional typesversion: 0.1.0) Source Code Relationship Target Code Comment Encounter.diagnosis.condition (condition) is equivalent to Extension (R5: The diagnosis relevant to the encounter additional types) 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.
Cross-version mapping for FHIR R5 Encounter to FHIR R4 Encounter
This ConceptMap represents cross-version mappings for elements from a FHIR R5 Encounter to FHIR R4.
Element `Encounter.meta` is mapped to FHIR R4 element `Encounter.meta` as `Equivalent`.
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 `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 `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 `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 `Encounter.identifier` is mapped to FHIR R4 element `Encounter.identifier` as `Equivalent`.
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 `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.
Element `Encounter.priority` is mapped to FHIR R4 element `Encounter.priority` as `Equivalent`.
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..*.
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.
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).
Element `Encounter.episodeOfCare` is mapped to FHIR R4 element `Encounter.episodeOfCare` as `Equivalent`.
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.
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.
Element `Encounter.serviceProvider` is mapped to FHIR R4 element `Encounter.serviceProvider` as `Equivalent`.
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.
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.
Element `Encounter.participant.period` is mapped to FHIR R4 element `Encounter.participant.period` as `Equivalent`.
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.
Element `Encounter.appointment` is mapped to FHIR R4 element `Encounter.appointment` as `Equivalent`.
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.
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).
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
Element `Encounter.reason.use` is mapped to FHIR R4 element `Encounter.reasonCode` as `Equivalent`.
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.
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.
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.
Element `Encounter.diagnosis.use` is mapped to FHIR R4 element `Encounter.diagnosis.use` as `SourceIsBroaderThanTarget`.
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.
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).
Element `Encounter.specialArrangement` is mapped to FHIR R4 element `Encounter.hospitalization.specialArrangement` as `Equivalent`.
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.
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.
Element `Encounter.admission.preAdmissionIdentifier` is mapped to FHIR R4 element `Encounter.hospitalization.preAdmissionIdentifier` as `Equivalent`.
Element `Encounter.admission.origin` is mapped to FHIR R4 element `Encounter.hospitalization.origin` as `Equivalent`.
Element `Encounter.admission.admitSource` is mapped to FHIR R4 element `Encounter.hospitalization.admitSource` as `Equivalent`.
Element `Encounter.admission.reAdmission` is mapped to FHIR R4 element `Encounter.hospitalization.reAdmission` as `Equivalent`.
Element `Encounter.admission.destination` is mapped to FHIR R4 element `Encounter.hospitalization.destination` as `Equivalent`.
Element `Encounter.admission.dischargeDisposition` is mapped to FHIR R4 element `Encounter.hospitalization.dischargeDisposition` as `Equivalent`.
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".
Element `Encounter.location.location` is mapped to FHIR R4 element `Encounter.location.location` as `Equivalent`.
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.
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.
Element `Encounter.location.period` is mapped to FHIR R4 element `Encounter.location.period` as `Equivalent`.
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.
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).
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.
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).
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).