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

EHDSProcedure → Procedure

The content of this page is automatically generated and doesn't document the actual mapping.

Please don't use this material for implementation purposes !

EHDSProcedure → Procedure

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

EHDSProcedure → Procedure
EHDSProcedure (Logical Model) Relationship Procedure
Element Description Relation Element Description Notes
identifier Identifier for the procedure record or act. equal identifier Business identifier for the procedure.
status Status of the procedure (completed, in-progress). equal status Procedure status. Important for workflows and billing.
code Coded description of the procedure performed. equal code Procedure code. May use national coding schemes or SNOMED CT.
subject Who the procedure was performed on. equal subject Patient / Animal Patient.
performed[x] Date/time or period when performed. equal performed[x] When the procedure was performed. FHIR supports multiple data types.
performer Who was involved in performing the procedure. equal performer Performer(s) of the procedure, and their function/role. References PractitionerRole / Practitioner / Organization.
location Where the procedure was carried out. equal location Location where the procedure occurred. Reference to LocationEuCore.
bodySite Body site targeted/affected. equal bodySite Target body site. Can align with BodyStructure details.
reason Clinical reason / indication for performing the procedure. equal reason Reason the procedure was performed. In R4 often reasonCode / reasonReference; in R5 unified as reason.

Return to overview: EHDS Logical Models → FHIR Profiles