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: BeModelNursingPrescription

Official URL: https://www.ehealth.fgov.be/standards/fhir/drp/StructureDefinition/BeModelNursingPrescription Version: 1.0.0
Active as of 2025-10-10 Computable Name: BeModelNursingPrescription

Data model for the nursing prescription referral.

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
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
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.
... 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').
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"
... medicalReason 0..1 Annotation Medical reasons for the prescription (e.g. 'Infected wound requiring follow-up'). 410666004 : "Reason For (x)"

doco Documentation for this format

This structure is derived from BeModelReferralPrescription

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
Instances of this logical model can be the target of a Reference
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
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.
... 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').
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"
... medicalReason 0..1 Annotation Medical reasons for the prescription (e.g. 'Infected wound requiring follow-up'). 410666004 : "Reason For (x)"

doco Documentation for this format

This structure is derived from BeModelReferralPrescription

Summary

Mandatory: 0 element(1 nested mandatory element)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
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.
... 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').
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"
... medicalReason 0..1 Annotation Medical reasons for the prescription (e.g. 'Infected wound requiring follow-up'). 410666004 : "Reason For (x)"

doco Documentation for this format

Differential View

This structure is derived from BeModelReferralPrescription

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
Instances of this logical model can be the target of a Reference
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. BeModelNursingPrescription 0..* BeModelReferralPrescription BeModelNursingPrescription

Elements defined in Ancestors:identifier, shortCode, recordedDate, creationDate, patient, author, status, statusReason, careRequested, discipline, description, type, originRequestId, validationStartDate, validationEndDate, problem, bodyLocation
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.
... 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').
... feedbackNeeded 1..1 boolean Follow-up indicator (boolean) specifying whether a feedback is expected from the doctor on this treatment.
... generalRemarks 0..* Annotation General remarks concerning the treatment or request.
... contraIndications 0..1 Annotation Medical contraindications (e.g. 'Latex allergy'). 103306004 : 'Contraindication to (x)"
... medicalReason 0..1 Annotation Medical reasons for the prescription (e.g. 'Infected wound requiring follow-up'). 410666004 : "Reason For (x)"

doco Documentation for this format

This structure is derived from BeModelReferralPrescription

Summary

Mandatory: 0 element(1 nested mandatory element)

 

Other representations of profile: CSV, Excel