Referral Prescription
1.0.0 - STU Belgium flag

Referral Prescription, 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/referral/StructureDefinition/BeModelReferralPrescription Version: 1.0.0
Draft as of 2024-12-10 Computable Name: BeModelReferralPrescription

Logical model describing the model for the prescription referral. This draft is used in the HL7 Belgian workgroup for referral.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(12 nested mandatory elements)

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. BeModelReferralPrescription 0..* Base BeModelReferralPrescription
Instances of this logical model can be the target of a Reference
... Id 1..1 Identifier UUID (see Doc: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.
... ShortCode 1..1 CodeableConcept “Business” code allowing the healthcare professional to find a prescription associated with a patient
... RecordedDate 1..1 dateTime Date of encoding of the information by the Recorder.
... Patient 1..1 Identifier Is the unique identifier of the patient. The unique identifier must be: NISS, National Registry Number or Bis Patient
... Author 1..1 Identifier 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: 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 Annotation 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").

doco Documentation for this format

This structure is derived from Base

Summary

Mandatory: 0 element(12 nested mandatory elements)

 

Other representations of profile: CSV, Excel