HL7 Europe Base and Core FHIR IG
0.2.0-ci-build - ci-build 150

HL7 Europe Base and Core FHIR IG, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.2.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/base/ and changes regularly. See the Directory of published versions

EHDSProcedure to FHIR Procedure Mapping

Note: The content of this page is work in progress and may change based on ongoing discussions within the working group.

The technical solutions listed are possible candidates under consideration and are not yet approved or ready for implementation.

EHDSProcedure → Procedure

This page describes the element-by-element mapping from the EHDSProcedure logical model to the FHIR ProcedureEuCore profile in this Implementation Guide.

EHDSProcedure → Procedure
EHDSProcedure (Logical Model) Relationship Procedure
Element Description Relation Resource Element Description Notes
header Common header for all patient-related data. relatedto Procedure. General metadata. Dataset-level; not usually carried in Procedure as-is.
header.subject Patient/subject the procedure is about. equivalent Proceduresubject Who the procedure was performed on. Reference to Patient (or other subject) as in FHIR Procedure.subject.
header.identifier Business identifier for the object. equivalent Procedureidentifier Business identifier for this procedure. Copy all identifiers if multiple exist.
header.authorship Resource authoring / provenance details. relatedto Procedurerecorder Who recorded the procedure. Procedure has recorder and asserter, not a generic "author".1.. in the model 0.. in the profile
header.authorship.author[x] Who created/issued the record. equivalent Procedurerecorder Who recorded the procedure. 1.. in the model 0.. in the profile
header.authorship.datetime Date/time the resource was issued. equivalent Procedureextension:recorded 〔R4〕 Date when the procedure was recorded FHIR R5 Procedure supports recorded; pre-adopted this element in R4.1.. in the model 0.. in the profile.
header.authorship.datetime Date/time the resource was issued. equivalent Procedure recorded 〔R5〕 Date when the procedure was recorded FHIR R5 Procedure supports recorded; pre-adopted this element in R4.1.. in the model 0.. in the profileTO BE CHECKED
header.lastUpdate Last technical correction/update. source-is-broader-than-target Proceduremeta.lastUpdated Last system update timestamp. Waiting for Xt-EHR feedback
header.status Technical/administrative dataset status. no-direct-equivalent Procedure- - Waiting for Xt-EHR feedback
header.statusReason[x] Reason for current dataset status. no-direct-equivalent Procedure- - Waiting for Xt-EHR feedback
header.language Language of the resource (IETF tag). equivalent Procedurelanguage Language used in text/narrative.
code Code identifying the procedure. equivalent Procedurecode Procedure code.
date[x] Date and time of the procedure or interval of its performance. equivalent Procedureperformed[x]〔R4〕 When the procedure was performed. Use performedDateTime or performedPeriod according to actual data type. performed[x] used in R4, occurrence[x] used in R5
date[x] Date and time of the procedure or interval of its performance. equivalent Procedureoccurrence[x]〔R5〕 When the procedure was performed. Use occurrenceDateTime or occurrencePeriod according to actual data type. performed[x] used in R4, occurrence[x] used in R5
performer An actor who performed the procedure. equivalent Procedureperformer Who performed the procedure and in what role. FHIR Procedure.performer.actor → Practitioner / PractitionerRole / Organization; add role if available.
bodySite Procedure target body site; may include laterality. equivalent ProcedurebodySite Target body site. Map EHDSBodyStructure → one or more Procedure.bodySite; laterality as qualifier.
reason[x] The reason why the procedure was performed (code or reference). equivalent ProcedurereasonCode / reasonReference〔R4〕 Indication/justification for the procedure. In R4, codes go to reasonCode; references (Condition / Observation / Procedure) go to reasonReference.
reason[x] The reason why the procedure was performed (code or reference). equivalent Procedurereason 〔R5〕 Indication/justification for the procedure. In R5 use the CodeableReference reason.
outcome The outcome of the procedure – did it resolve the reasons? equivalent Procedureoutcome The result of the procedure. CodeableConcept; EHDS prefers SNOMED CT.
complication Any complications during or immediately after the procedure. equivalent Procedurecomplication / complicationDetail 〔R4〕 Complication(s) following the procedure. In R4 codes go to complication; reference (Condition) in complicationDetail.
complication Any complications during or immediately after the procedure. equivalent Procedurecomplication〔R5〕 Complication(s) following the procedure. In R5 use the CodeableReference complication.
deviceUsed Device used to perform the procedure. equivalent ProcedureusedCode / usedReference〔R4〕 Device that was used during the procedure. In R4 usedCode only if you have no Device instance, usedReference if you refer a Device.
deviceUsed Device used to perform the procedure. equivalent Procedureused〔R5〕 Device that was used during the procedure. In R5 use the CodeableReference used.
focalDevice Device that is the focus of the procedure (implanted, removed, calibrated, etc.). equivalent ProcedurefocalDevice.manipulated Manipulated/targeted device during the procedure. Matches FHIR Procedure.focalDevice exactly.
note Additional information about the procedure. equivalent Procedurenote Comments about the procedure. EHDS has 0..1 string; FHIR allows 0..* Annotation → map to one Annotation entry.

Return to overview: EHDS Logical Models → FHIR Profiles