Digital Referral Prescription Implementation Guide
1.0.0 - STU

Digital Referral Prescription Implementation Guide, published by eHealth Platform. 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
Active as of 2026-03-01 | Computable Name: BeModelReferralPrescription

Data model for the prescription referral.

Usages:

- Derived from this Logical Model: BeModelNursingPrescription
- Refer to this Logical Model: BeModelOrganisationClaim and BeModelTreatmentStatus

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.

- Key Elements Table
- Differential Table
- Snapshot Table
- Statistics/References
- All

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(12 nested mandatory elements)

Key Elements View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

Differential View

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

Snapshot View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
BeModelReferralPrescription |  | 0..* | Base | BeModelReferralPrescription Instances of this logical model can be the target of a Reference
identifier |  | 1..1 | Identifier | Business identifier of the request
shortCode |  | 1..1 | CodeableConcept | 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.
creationDate |  | 1..1 | dateTime | Date of creation of the referral prescription
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, …)
careRequested |  | 1..1 | CodeableConcept | Type of care requested (e.g. 'Compression therapy', 'Sample collection', CT Scan).
discipline |  | 1..1 | CodeableConcept | Category of the requested care (nursing, radiology, ...)
description |  | 0..1 | CodeableConcept | Additional details on the requested care
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).
validationStartDate |  | 1..1 | dateTime | Start date of the prescription validity (encoded by the prescriber).
validationEndDate |  | 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').
Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(12 nested mandatory elements)

Other representations of profile: CSV, Excel