Digital Referral Prescription Implementation Guide
1.0.0 - STU Belgium flag

Digital Referral Prescription Implementation Guide, published by . This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/referral/ and changes regularly. See the Directory of published versions

Logical Model: BeModelReferralPrescription

Official URL: https://www.ehealth.fgov.be/standards/fhir/drp/StructureDefinition/BeModelReferralPrescription Version: 1.0.0
Draft as of 2026-03-27 Computable Name: BeModelReferralPrescription

Data model for the prescription referral.

Usages:

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
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG

This structure is derived from Base

Summary

Mandatory: 0 element(10 nested mandatory elements)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... identifier 0..1 Identifier Business identifier of the request
... shortCode 0..1 Identifier Business code allowing the healthcare professional to find a prescription associated with a patient
... recordedDate 1..1 dateTime Date of recording of the information by the Recorder.
... patient 1..1 Identifier Identification of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... author 1..1 Identifier The person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be: NISS, National Registry Number or Bis Requester
... status 1..1 CodeableConcept Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
... statusReason 0..1 CodeableConcept Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Binding: BeVSPrescriptionStatusReason (required)
... careRequested 1..1 CodeableConcept Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
... description 0..1 CodeableConcept Additional details on the requested care
... discipline 1..1 CodeableConcept Category of the requested care (nursing, radiology, ...)
... type 1..1 CodeableConcept Type of the request or prescription ('Prescription' or 'Proposal').
... originRequestId 0..1 Identifier Reference to the ID of the original request (useful when the request is an extension of another one).
... validityStartDate 1..1 dateTime Start date of the prescription validity (encoded by the prescriber).
... validityEndDate 1..1 dateTime End date of the prescription validity (encoded by the prescriber)
... problem 0..* CodeableConcept Medical problem or clinical context related to this request (for example: 'Open wound', 'Broken leg').
... bodyLocation 0..* CodeableConcept Anatomical location where the treatment should be applied (for example: 'Left arm').
Binding: Body Site (required)

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
BeModelReferralPrescription.​statusReason Base required BeVSPrescriptionStatusReason 📦1.0.0 This IG
BeModelReferralPrescription.​bodyLocation Base required Body Site 📦1.0.0 This IG

This structure is derived from Base

Summary

Mandatory: 0 element(10 nested mandatory elements)

 

Other representations of profile: CSV, Excel