Logical model describing the model for the Annex81 proposal and approval

UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.

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

Date of encoding of the information by the Recorder.

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.

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.

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

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

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

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

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.

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

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

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).

Logical model describing the model for the Annex81 proposal and approval

UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.

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

Date of encoding of the information by the Recorder.

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.

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.

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

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

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

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

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.

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

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

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).

Logical model describing the model for the Annex81 proposal and approval

UUID (see Doc Bart: https://docs.google.com/document/d/13qamEPfdQ2HgUiXmjwHQNchpEU3LsQHF5MN9jKufX2g/edit?usp=sharing ) Absent during creation by client software, otherwise always present.

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

Date of encoding of the information by the Recorder.

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.

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.

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

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

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

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

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.

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

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

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).