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
Official URL: https://www.ehealth.fgov.be/standards/fhir/referral/StructureDefinition/BeModelAnnex81 | Version: 1.0.0 | |||
Draft as of 2024-12-06 | Computable Name: BeModelAnnex81 |
Logical model describing the model for the Annex81 proposal and approval
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from Base
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
This structure is derived from Base
Differential View
This structure is derived from Base
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
Key Elements View
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
Snapshot View
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
BeModelAnnex81 | 0..* | Base | BeModelAnnex81 Instances of this logical model can be the target of a Reference | |
Id | 1..1 | Identifier | UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) | |
ShortCode | 1..1 | Identifier | “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. | |
CreationDate | 1..1 | dateTime | 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. | |
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 the National Register Number (NISS) or bis number. | |
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 (list of acts that each profession can do (not nomenclature code)) (snomed-ct code (procedure)) | |
Patient | 1..1 | Identifier | Is the patient's unique identifier. The unique identifier must be the National Patient Registry Number (NISS) or the patient bis | |
OriginRequestId | 0..1 | Identifier | 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. | |
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 | 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). | |
Documentation for this format |
This structure is derived from Base