MyHealth@EU Core
1.0.0 - trial-use 150

MyHealth@EU Core - Downloaded Version 1.0.0 See the Directory of published versions

Logical Model: Procedure model

Official URL: http://fhir.ehdsi.eu/core/StructureDefinition/MyHealthEuProcedure Version: 1.0.0
Active as of 2026-05-04 Computable Name: MyHealthEuProcedure

MyHealth@EU refined model for procedure

Usages:

  • This Logical Model is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... header 1..1 Base Basic metadata for this information
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 0..* Identifier Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries).
.... author[x] 0..* Author responsible for the provided information.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 0..1 dateTime Date and optionally time of authoring/issuing
.... status 1..1 CodeableConcept Status of the procedure (e.g. completed, on hold, stopped)
Binding Description: (preferred): HL7 Event Status
.... source 0..1 CodeableConcept Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
Binding Description: (preferred): SNOMED CT
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
.... procedureDateDateTime dateTime
.... procedureDatePeriod Period
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... reason[x] 0..* The reason 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
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The immediate result of the procedure (e.g. successful, unsuccessful). This does not include assessment over a longer period of time.
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-procedure 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
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice O 0..* MyHealthEuDevice 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.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
MyHealthEuProcedure.​header.status Base preferred Not State Unknown
MyHealthEuProcedure.​header.language Base preferred Not State Unknown
MyHealthEuProcedure.​code Base preferred Not State Unknown
MyHealthEuProcedure.​reason[x] Base preferred Not State Unknown
MyHealthEuProcedure.​outcome Base preferred Not State Unknown
MyHealthEuProcedure.​complication Base preferred Not State Unknown

This structure is derived from EHDSProcedure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 dateTime, Period Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... header 1..1 Base Basic metadata for this information
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 0..* Identifier Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries).
.... author[x] 0..* Author responsible for the provided information.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 0..1 dateTime Date and optionally time of authoring/issuing
.... status 1..1 CodeableConcept Status of the procedure (e.g. completed, on hold, stopped)
Binding Description: (preferred): HL7 Event Status
.... source 0..1 CodeableConcept Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
Binding Description: (preferred): SNOMED CT
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
.... procedureDateDateTime dateTime
.... procedureDatePeriod Period
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... reason[x] 0..* The reason 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
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The immediate result of the procedure (e.g. successful, unsuccessful). This does not include assessment over a longer period of time.
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-procedure 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
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice O 0..* MyHealthEuDevice 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.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
MyHealthEuProcedure.​header.status Base preferred Not State Unknown
MyHealthEuProcedure.​header.language Base preferred Not State Unknown
MyHealthEuProcedure.​code Base preferred Not State Unknown
MyHealthEuProcedure.​reason[x] Base preferred Not State Unknown
MyHealthEuProcedure.​outcome Base preferred Not State Unknown
MyHealthEuProcedure.​complication Base preferred Not State Unknown

This structure is derived from EHDSProcedure

Summary

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... header 1..1 Base Basic metadata for this information
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 0..* Identifier Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries).
.... author[x] 0..* Author responsible for the provided information.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 0..1 dateTime Date and optionally time of authoring/issuing
.... status 1..1 CodeableConcept Status of the procedure (e.g. completed, on hold, stopped)
Binding Description: (preferred): HL7 Event Status
.... source 0..1 CodeableConcept Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
Binding Description: (preferred): SNOMED CT
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
.... procedureDateDateTime dateTime
.... procedureDatePeriod Period
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... reason[x] 0..* The reason 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
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The immediate result of the procedure (e.g. successful, unsuccessful). This does not include assessment over a longer period of time.
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-procedure 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
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice O 0..* MyHealthEuDevice 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.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
MyHealthEuProcedure.​header.status Base preferred Not State Unknown
MyHealthEuProcedure.​header.language Base preferred Not State Unknown
MyHealthEuProcedure.​code Base preferred Not State Unknown
MyHealthEuProcedure.​reason[x] Base preferred Not State Unknown
MyHealthEuProcedure.​outcome Base preferred Not State Unknown
MyHealthEuProcedure.​complication Base preferred Not State Unknown

Differential View

This structure is derived from EHDSProcedure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 dateTime, Period Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MyHealthEuProcedure 0..* EHDSProcedure Procedure model

Elements defined in Ancestors:header, code, procedureDate[x], performer, bodySite, reason[x], outcome, complication, deviceUsed, focalDevice, note
... header 1..1 Base Basic metadata for this information
.... subject 1..1 EHDSPatient Patient/subject information
.... identifier 0..* Identifier Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries).
.... author[x] 0..* Author responsible for the provided information.
..... authorEHDSHealthProfessional EHDSHealthProfessional
..... authorEHDSOrganisation EHDSOrganisation
..... authorEHDSDevice EHDSDevice
.... date 0..1 dateTime Date and optionally time of authoring/issuing
.... status 1..1 CodeableConcept Status of the procedure (e.g. completed, on hold, stopped)
Binding Description: (preferred): HL7 Event Status
.... source 0..1 CodeableConcept Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
.... language 0..1 CodeableConcept Language in which the resource is written. Language is expressed by the IETF language tag.
Binding Description: (preferred): BCP 47
... code O 1..1 CodeableConcept Concept code and display name identifying the type of procedure
Binding Description: (preferred): SNOMED CT
ObligationsActor
SHOULD:handle MyHealth@EU Handler
... procedureDate[x] O 0..1 Date and time of the procedure or interval of its performance
ObligationsActor
SHOULD:handle MyHealth@EU Handler
.... procedureDateDateTime dateTime
.... procedureDatePeriod Period
... bodySite O 0..* MyHealthEuBodyStructure Target body site of the procedure. Laterality may be included as a qualifier of the body site.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... reason[x] 0..* The reason 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
.... reasonCodeableConcept CodeableConcept
.... reasonEHDSCondition EHDSCondition
.... reasonEHDSObservation EHDSObservation
.... reasonEHDSProcedure EHDSProcedure
... outcome 0..1 CodeableConcept The immediate result of the procedure (e.g. successful, unsuccessful). This does not include assessment over a longer period of time.
Binding Description: (preferred): SNOMED CT
... complication 0..* CodeableConcept Any complications that occurred during the procedure, or in the immediate post-procedure 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
... deviceUsed 0..* EHDSDevice Device used to perform the procedure
... focalDevice O 0..* MyHealthEuDevice 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.
ObligationsActor
MAY:able-to-populate MyHealth@EU Handler
... note 0..1 string Additional information about the procedure

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
MyHealthEuProcedure.​header.status Base preferred Not State Unknown
MyHealthEuProcedure.​header.language Base preferred Not State Unknown
MyHealthEuProcedure.​code Base preferred Not State Unknown
MyHealthEuProcedure.​reason[x] Base preferred Not State Unknown
MyHealthEuProcedure.​outcome Base preferred Not State Unknown
MyHealthEuProcedure.​complication Base preferred Not State Unknown

This structure is derived from EHDSProcedure

Summary

 

Other representations of profile: CSV, Excel