HL7 Belgium FHIR Implementation Guide: Patient Dossier
1.0.1 - STU1 Belgium

HL7 Belgium FHIR Implementation Guide: Patient Dossier, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 1.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/patient-dossier/ and changes regularly. See the Directory of published versions

Logical Model: BeProcedure Model

Official URL: https://www.ehealth.fgov.be/standards/fhir/patient-dossier/StructureDefinition/be-model-procedure Version: 1.0.1
Draft as of 2026-02-25 Computable Name: BeModelProcedure

Procedure logical model

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
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... @id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... @id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

This structure is derived from Base

Summary

Mandatory: 0 element(7 nested mandatory elements)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... @id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. be-model-procedure 0..* Base BeProcedure Model
... identifier 1..* Identifier Unique identifier for the procedure
... recordedDate 1..1 dateTime Date of the last modification/recording of the procedure
... performedDate[x] 1..1 Date or period when the procedure was actually performed
.... performedDateDateTime dateTime
.... performedDatePeriod Period
... recorder 1..1 Reference() Person, organization or device that recorded the procedure.
... performer 0..1 Reference(Practitioner | PractitionerRole | Organization) Person who performed the procedure.
... request 0..* Reference() CarePlan and/or Referral Prescription that is at the origin of the procedure. For example: a physiotherapy session performed on prescription from the general practitioner
... partOf 0..* Reference() Part of the event being referenced: procedure, observation (symptoms) or problem (disease). For example: Blood draw (procedure) is part of the diagnostic observation (Observation)
... category 0..* CodeableConcept Type or nature of the procedure. For example: surgical, psychiatric or chiropractic procedures
... focalDevice 0..* CodeableReference() Implanted or manipulated device
... usedDevice 0..* Reference() Devices or materials used temporarily during the procedure. For example: surgical robot, intraoperative imaging, neuronavigation. This also includes substances such as gels. Standard small instruments such as scalpels and syringes are not recorded
... status 1..1 code Procedure status (not-done, stopped, completed, entered-in-error). Note: 'not-done' is out of scope as it implies planning. Business Rule: 'completed' by default
... code 1..1 CodeableConcept Identification of the procedure (SNOMED-CT Procedure concept)
... reason 0..* BackboneElement Reason why the procedure is performed. For example: amputation after an accident, broken leg
.... @id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... reasonCode 0..1 CodeableConcept Coded reason why the procedure is performed
.... reasonReference 0..1 Reference() Reference to the condition, observation or procedure that is the reason
... bodySite 0..1 BeModelBodySite The site on the patient's body where the procedure was performed
... surgicalApproach 0..* CodeableConcept Indicates by which anatomical route or according to which technique the procedure was performed. For example: laparoscopic, endoscopic, percutaneous
... location 0..1 Reference() Reference to the location where the procedure was performed. Example: Healthcare provider's office, Patient's home, Hospital, Outpatient, other
... outcome 0..1 CodeableConcept Result of the procedure execution. Example: Partial success, Success, Unsuccessful
... report 0..* Reference() Any report resulting from the procedure. Currently this is expected to be an attached document (pdf, URL, jpg, etc.). In the future possibly reference to a DiagnosticReport or other data object
... note 0..* Annotation Additional information about the procedure

doco Documentation for this format

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()

This structure is derived from Base

Summary

Mandatory: 0 element(7 nested mandatory elements)

 

Other representations of profile: CSV, Excel