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/tree/main 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-06-10 Computable Name: EHDSProcedure

C.16 - EHDS refined base model for An action that is or was performed on or for a patient

Usages:

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

This structure is derived from Base

Summary

Mandatory: 0 element(1 nested mandatory element)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSProcedure 0..* Base Procedure model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the procedure
... subject 1..1 EHDSPatient On whom the procedure was performed.
... 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 Anatomic location and laterality where the procedure was performed. This is the target site.
... reason[x] 0..* The reason why the procedure was performed.
.... 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.
... location 0..* EHDSLocation Location where the procedure was performed
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSProcedure.codepreferred
EHDSProcedure.outcomepreferred
EHDSProcedure.complicationpreferred

This structure is derived from Base

Summary

Mandatory: 0 element(1 nested mandatory element)

 

Other representations of profile: CSV, Excel