Digital Referral Prescription Implementation Guide
1.0.0 - STU Belgium flag

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: BeModelAnnex81 - Detailed Descriptions

Active as of 2025-10-10

Definitions for the BeModelAnnex81 logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. BeModelAnnex81
Definition

Logical model describing the model for the Annex81 proposal and approval

ShortBeModelAnnex81
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. BeModelAnnex81.identifier
Definition

Business identifier of the Annex81 proposal / approval

ShortBusiness identifier of the Annex81 proposal / approval
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..1
TypeIdentifier
4. BeModelAnnex81.shortCode
Definition

'Business' code allowing the healthcare professional to find a prescription associated with a patient

ShortBusiness short identifier allowing the healthcare professional to find a prescription associated with a patient
Control1..1
TypeIdentifier
6. BeModelAnnex81.recordedDate
Definition

Date of encoding of the information by the Recorder.

ShortDate of encoding of the information by the Recorder.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. BeModelAnnex81.creationDate
Definition

Creation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.

ShortCreation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. BeModelAnnex81.author
Definition

Is the unique identifier of 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 the National Register Number (NISS) or bis number.

ShortThe person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be the National Register Number (NISS) or bis number.
Control1..1
TypeIdentifier
12. BeModelAnnex81.status
Definition

Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)

ShortIs the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
Control1..1
TypeCodeableConcept
14. BeModelAnnex81.statusReason
Definition

Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)

ShortGives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Control0..1
TypeCodeableConcept
16. BeModelAnnex81.careRequested
Definition

Type of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))

ShortType of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))
Control1..1
TypeCodeableConcept
18. BeModelAnnex81.patient
Definition

Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis

ShortThe patient's identification. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis
Control1..1
TypeIdentifier
20. BeModelAnnex81.originRequestId
Definition

Reference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.

ShortReference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.
Control0..1
TypeIdentifier
22. BeModelAnnex81.validationStartDate
Definition

Start date of the prescription validity (encoded by the prescriber).

ShortStart date of the prescription validity (encoded by the prescriber).
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
24. BeModelAnnex81.validationEndDate
Definition

End date of the prescription validity (encoded by the prescriber)

ShortEnd date of the prescription validity (encoded by the prescriber)
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
26. BeModelAnnex81.problem
Definition

Reason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).

ShortReason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).
Control0..*
TypeCodeableConcept
28. BeModelAnnex81.feedbackNeeded
Definition

Boolean – true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"

ShortBoolean - true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"
Control1..1
Typeboolean
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. BeModelAnnex81
Definition

Logical model describing the model for the Annex81 proposal and approval

ShortBeModelAnnex81
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. BeModelAnnex81.identifier
Definition

Business identifier of the Annex81 proposal / approval

ShortBusiness identifier of the Annex81 proposal / approval
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..1
TypeIdentifier
4. BeModelAnnex81.shortCode
Definition

'Business' code allowing the healthcare professional to find a prescription associated with a patient

ShortBusiness short identifier allowing the healthcare professional to find a prescription associated with a patient
Control1..1
TypeIdentifier
6. BeModelAnnex81.recordedDate
Definition

Date of encoding of the information by the Recorder.

ShortDate of encoding of the information by the Recorder.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. BeModelAnnex81.creationDate
Definition

Creation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.

ShortCreation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. BeModelAnnex81.author
Definition

Is the unique identifier of 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 the National Register Number (NISS) or bis number.

ShortThe person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be the National Register Number (NISS) or bis number.
Control1..1
TypeIdentifier
12. BeModelAnnex81.status
Definition

Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)

ShortIs the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
Control1..1
TypeCodeableConcept
14. BeModelAnnex81.statusReason
Definition

Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)

ShortGives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Control0..1
TypeCodeableConcept
16. BeModelAnnex81.careRequested
Definition

Type of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))

ShortType of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))
Control1..1
TypeCodeableConcept
18. BeModelAnnex81.patient
Definition

Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis

ShortThe patient's identification. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis
Control1..1
TypeIdentifier
20. BeModelAnnex81.originRequestId
Definition

Reference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.

ShortReference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.
Control0..1
TypeIdentifier
22. BeModelAnnex81.validationStartDate
Definition

Start date of the prescription validity (encoded by the prescriber).

ShortStart date of the prescription validity (encoded by the prescriber).
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
24. BeModelAnnex81.validationEndDate
Definition

End date of the prescription validity (encoded by the prescriber)

ShortEnd date of the prescription validity (encoded by the prescriber)
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
26. BeModelAnnex81.problem
Definition

Reason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).

ShortReason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).
Control0..*
TypeCodeableConcept
28. BeModelAnnex81.feedbackNeeded
Definition

Boolean – true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"

ShortBoolean - true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"
Control1..1
Typeboolean
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. BeModelAnnex81
Definition

Logical model describing the model for the Annex81 proposal and approval

ShortBeModelAnnex81
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. BeModelAnnex81.identifier
Definition

Business identifier of the Annex81 proposal / approval

ShortBusiness identifier of the Annex81 proposal / approval
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..1
TypeIdentifier
4. BeModelAnnex81.shortCode
Definition

'Business' code allowing the healthcare professional to find a prescription associated with a patient

ShortBusiness short identifier allowing the healthcare professional to find a prescription associated with a patient
Control1..1
TypeIdentifier
6. BeModelAnnex81.recordedDate
Definition

Date of encoding of the information by the Recorder.

ShortDate of encoding of the information by the Recorder.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. BeModelAnnex81.creationDate
Definition

Creation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.

ShortCreation date of the referral prescription. This date will not change throughout the process. This date corresponds to the first recordedDate recorded for this referral prescription.
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. BeModelAnnex81.author
Definition

Is the unique identifier of 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 the National Register Number (NISS) or bis number.

ShortThe person who encodes the prescription (e.g. a doctor, nurse, midwife or dentist) and takes responsibility for their content. The unique identifier must be the National Register Number (NISS) or bis number.
Control1..1
TypeIdentifier
12. BeModelAnnex81.status
Definition

Is the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)

ShortIs the status of the referral prescription (e.g. planned, complete, stopped, suspended, in progress, ….)
Control1..1
TypeCodeableConcept
14. BeModelAnnex81.statusReason
Definition

Gives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)

ShortGives the reason for the status of the referral prescription (treatment has been changed, patient is allergic, patient refuses, …)
Control0..1
TypeCodeableConcept
16. BeModelAnnex81.careRequested
Definition

Type of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))

ShortType of care requested (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure))
Control1..1
TypeCodeableConcept
18. BeModelAnnex81.patient
Definition

Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis

ShortThe patient's identification. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis
Control1..1
TypeIdentifier
20. BeModelAnnex81.originRequestId
Definition

Reference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.

ShortReference to the original prescription on which the prescription is based (prescriptionId), care plan, follow-up path, …. referenceId. Reference to the CarePlan that addresses this prescription.
Control0..1
TypeIdentifier
22. BeModelAnnex81.validationStartDate
Definition

Start date of the prescription validity (encoded by the prescriber).

ShortStart date of the prescription validity (encoded by the prescriber).
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
24. BeModelAnnex81.validationEndDate
Definition

End date of the prescription validity (encoded by the prescriber)

ShortEnd date of the prescription validity (encoded by the prescriber)
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
26. BeModelAnnex81.problem
Definition

Reason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).

ShortReason for the request. The problem (code or reference) that is the main reason for this prescription (example: problem justifying the patient's inability to manage his medications).
Control0..*
TypeCodeableConcept
28. BeModelAnnex81.feedbackNeeded
Definition

Boolean – true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"

ShortBoolean - true if the prescriber requests feedback. If he wants to add other care providers, this will be mentioned in free text in the note. Here by default "True"
Control1..1
Typeboolean
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension