EHDS Logical Information Models
0.1.0 - ci-build

EHDS Logical Information Models, published by Xt-EHR. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Xt-EHR/xt-ehr-common/ and changes regularly. See the Directory of published versions

Logical Model: Procedure model

Official URL: https://www.xt-ehr.eu/specifications/fhir/StructureDefinition/EHDSProcedure Version: 0.1.0
Draft as of 2025-07-08 Computable Name: EHDSProcedure

EHDS refined base model for an action that is or was performed on or for a patient

Procedures is suggested as a mandatory section of Patient Summary. Implementers should as a minimum be able to produce a list of procedures and give an empty list reason if there are no procedures. The only required element for each listed procedure, is specifying the procedure. The information elements for each procedure are listed in the EHDS-PS-Procedure model.
If the producing system have no record of procedures to list (e.g. the patient has no history of procedures, or the system have no procedure information), it must provide a reason for the empty list. This is accordance with the specification in ISO IPS and updates to the HL7 FHIR IPS.

Receiving systems must be able to handle the data and are encouraged to display the received information to the user but are not obliged to do so.

The information elements and value sets suggested is taken from eHN GL, MyHealth@EU and HL7 FHIR IPS.

Usages:

Views of Logical Model

Description of Differentials, Snapshots and how the different presentations work.

This structure is derived from EHDSDataSet

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Procedure model
Instances of this logical model can be the target of a Reference
... code 0..1 CodeableConcept Code identifying the procedure
Binding Description: (preferred): SNOMED CT
... date[x] 0..1 Date and time of the procedure or interval of its performance
.... dateDateTime dateTime
.... datePeriod Period
... performer 0..* EHDSHealthProfessional An actor who performed the procedure
... reason[x] 0..* The reason why the procedure was performed. This may be a concept from a terminology or a reference to a specific instance that describes the reason.
Binding Description: (preferred): SNOMED CT, ICD-10, Orphacode if rare disease is diagnosed
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The outcome of the procedure - did it resolve the reasons for the procedure being performed?
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the procedure description, which will typically describe the procedure itself rather than any 'post procedure' issues.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode if rare disease is diagnosed
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice 0..* EHDSDevice Device(s) that is/are implanted, removed, or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.reason[x]preferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Procedure model
Instances of this logical model can be the target of a Reference
... header 1..1 Base Common header for all patient-related data
.... subject 1..1 EHDSPatient Subject
.... identifier 0..* Identifier Business identifier for the object
.... authorship 1..* Base Authorship
..... author[x] 1..1 Author
...... authorEHDSHealthProfessional EHDSHealthProfessional
...... authorEHDSOrganisation EHDSOrganisation
...... authorEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of authoring/issuing
.... lastUpdate 0..1 dateTime Date and time of the last update to the resource
.... status 1..1 CodeableConcept Status of the resource
.... statusReason[x] 0..1 Reason for the current status of the resource.
..... statusReasonCodeableConcept CodeableConcept
..... statusReasonString string
.... language 0..1 CodeableConcept Language
Binding Description: (preferred): BCP 47
.... version 0..1 string Version
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... code 0..1 CodeableConcept Code identifying the procedure
Binding Description: (preferred): SNOMED CT
.... dateDateTime dateTime
.... datePeriod Period
... performer 0..* EHDSHealthProfessional An actor who performed the procedure
... bodySite 0..* EHDSBodyStructure Procedure target body site. Details of where the procedure was performed. Laterality may be included as qualifier of the body site.
... reason[x] 0..* The reason why the procedure was performed. This may be a concept from a terminology or a reference to a specific instance that describes the reason.
Binding Description: (preferred): SNOMED CT, ICD-10, Orphacode if rare disease is diagnosed
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The outcome of the procedure - did it resolve the reasons for the procedure being performed?
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the procedure description, which will typically describe the procedure itself rather than any 'post procedure' issues.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode if rare disease is diagnosed
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice 0..* EHDSDevice Device(s) that is/are implanted, removed, or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure.
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSProcedure.header.languagepreferred
EHDSProcedure.codepreferred
EHDSProcedure.reason[x]preferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

 

Other representations of model: CSV, Excel