HL7 Europe Discharge Report
1.0.0-ci-build - ci-build 150

HL7 Europe Discharge Report, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/discharge-report/ and changes regularly. See the Directory of published versions

EHDSEncounter Mapping

EHDSEncounter -> Encounter (DR)
Ongoing alignment: Future versions of the Xt-EHR models and of the EHDS Implementing Acts may require updates to these mappings.

EHDSEncounter -> Encounter (DR)

This page explains how conceptual elements from the EHDSEncounter logical model are expressed in the corresponding FHIR EncounterEuDr profile used by this Implementation Guide.

Mapping Context

EHDSEncounter -> Encounter (DR)
EHDSEncounter (Logical Model) Relationship Encounter (DR)
Element Relation Resource Element Notes
header related-to Encounter . Dataset-level inherited header; not carried as a single element in Encounter.
header.subject equivalent Encounter subject Reference to PatientEuCore.
header.identifier equivalent Encounter identifier
header.author[x] related-to Encounter participant.individual Encounter does not include a dedicated author element. Authorship is typically inferred from the healthcare professional’s participation in the encounter, for example as admitter or discharger. If an explicit author is required, this could be represented using an appropriate participation (participant.type='AUT').
header.date related-to Encounter participant.period Encounter does not include a dedicated authorship date element. If an explicit date is required, it could be represented as the period of an appropriate participation (participant.type='AUT'); otherwise it may be inferred from Encounter.period.
header.status equivalent Encounter status
header.source related-to Encounter participant.individual Encounter does not include a dedicated informant element. If informant details are required, this could be represented using an appropriate participation (participant.type='INF')
header.language equivalent Encounter language IETF language tag.
priority equivalent Encounter priority
type related-to Encounter type The model describes encounter kind, such as inpatient, ambulatory, or teleconsultation. Use Encounter.class for the broad class and Encounter.type for a more specific type.
type related-to Encounter class The model describes encounter kind, such as inpatient, ambulatory, or teleconsultation. Use Encounter.class for the broad class and Encounter.type for a more specific type.
period equivalent Encounter period
serviceProvider equivalent Encounter serviceProvider
referringProfessional related-to Encounter participant:referrer.individual Use participant.type = REF.
basedOn[x] equivalent Encounter basedOn
reason[x] related-to Encounter reasonCode / reasonReference Use reasonCode for CodeableConcept reasons and reasonReference for Condition, Procedure, or Observation reasons. String reasons require narrative text or an extension.
admission related-to Encounter hospitalization
admission.admitter equivalent Encounter participant:admitter.individual Use participant.type = ADM.
admission.admitSource equivalent Encounter hospitalization.admitSource
dischargeDiagnosis[x] related-to Encounter diagnosis.condition Use diagnosis.condition for a Condition reference and diagnosis.use for role if needed. A coded diagnosis should be represented as a Condition resource when a structured diagnosis is required.
dischargeDestination related-to Encounter hospitalization See dischargeDestination.type and .location mappings.
dischargeDestination.type related-to Encounter hospitalization.dischargeDisposition
dischargeDestination.location[x] related-to Encounter hospitalization.destination
serviceLocation related-to Encounter location
serviceLocation.period equivalent Encounter location.period
serviceLocation.organisationPart[x] related-to Encounter location.location
subEncounter related-to Encounter partOf FHIR Encounter.partOf points from the sub-encounter to the parent encounter.
note equivalent Encounter extension:note

Return to overview: EHDS Logical Models -> FHIR Profiles