Transaction: Diary note
General information
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR
VERSION:
1.0
DATE:
2017-09-01
DEFINITION:
This type of transaction corresponds to a very short note contained in the "multidisciplinary diary" of a patient typically stored in a "healthcare safe" (namely RSW/Inter-med, RSB/Brusafe and Vitalink).
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR
VERSION:
1.0
DATE:
2017-09-01
DEFINITION:
This type of transaction corresponds to a very short note contained in the "multidisciplinary diary" of a patient typically stored in a "healthcare safe" (namely RSW/Inter-med, RSB/Brusafe and Vitalink).
Guidelines
Generalities
This transaction only requires a level 1 of kmehr normalization but some additional very basic guidelines must be fulfilled in order to be integrated as a constitutive element of a practical diary (see guidelines hereafter).
Transaction elements
| Element | Purpose |
|---|---|
|
id |
id of the transaction according to the ID-KMEHR conventions. |
|
cd |
You must use the value "diarynote" from CD-TRANSACTION. It should also provide values from the table CD-DIARY to specify a specific context (such as "medication") to allow the setting up of filters within the diary of the patient. It is allowed to add own local codes. |
|
date |
This is the date of reporting. |
|
time |
This is the time of reporting. |
|
author |
This is the person assuming the responsibility of the medical content of the transaction. It can be specified by a combination of hcparty elements. There must be at least one hcparty identifying a person. |
|
iscomplete |
Expresses if the note is completed. Must be “true”. |
|
isvalidated |
Expresses if the note is validated. Must be “true”. |
Structure overview
A diarynote is mainly composed of the next elements.
- A short textual content within either one text element or one simple text-with-layout element typically composed of a single paragraph. This element is mandatory and unique.
Please note some implementations have more limiting requirements:- Messages send to Vitalink are strongly limited to 320 characters.
- Messages send to RSW are recommended to use the text-with-layout element.
- Optionally, appendixes, such as pictures for instance, may be provided. Those are encapsulated within a lnk element.
- lnk elements can also be used to refer to other elements of "safes". A medication diarynote may for instance be related to a medicationscheme or medicationschemeelement. This feature is however currently not supported and will be consequently more deeply documented in a later version.
Generalities
This transaction only requires a level 1 of kmehr normalization but some additional very basic guidelines must be fulfilled in order to be integrated as a constitutive element of a practical diary (see guidelines hereafter).
Transaction elements
| Element | Purpose |
|---|---|
|
id |
id of the transaction according to the ID-KMEHR conventions. |
|
cd |
You must use the value "diarynote" from CD-TRANSACTION. It should also provide values from the table CD-DIARY to specify a specific context (such as "medication") to allow the setting up of filters within the diary of the patient. It is allowed to add own local codes. |
|
date |
This is the date of reporting. |
|
time |
This is the time of reporting. |
|
author |
This is the person assuming the responsibility of the medical content of the transaction. It can be specified by a combination of hcparty elements. There must be at least one hcparty identifying a person. |
|
iscomplete |
Expresses if the note is completed. Must be “true”. |
|
isvalidated |
Expresses if the note is validated. Must be “true”. |
Structure overview
A diarynote is mainly composed of the next elements.
- A short textual content within either one text element or one simple text-with-layout element typically composed of a single paragraph. This element is mandatory and unique.
Please note some implementations have more limiting requirements:- Messages send to Vitalink are strongly limited to 320 characters.
- Messages send to RSW are recommended to use the text-with-layout element.
- Optionally, appendixes, such as pictures for instance, may be provided. Those are encapsulated within a lnk element.
- lnk elements can also be used to refer to other elements of "safes". A medication diarynote may for instance be related to a medicationscheme or medicationschemeelement. This feature is however currently not supported and will be consequently more deeply documented in a later version.