Terms and definitions for the main work items

[rlindstrm]

1) Medication plan / Treatment plan / Medication overview / Medication list / ? consists of: 2) Medication lines / Treatment lines / Medication items / ?

[rlindstrm]

This is Medication overview (technically list of statements): Needs an agreed name and a definition.

[rlindstrm]

This is medication line (MedicationStatement):

MedicationStatement about how you actually take the drug, should be linked to the original MedicationStatement how you should have taken it.

MedicationStatements do have legal implications - this is a way to document what the doctor knows and what decides based on this information.

MedicationStatement is linked to related administrations and prescriptions/dispensations, i.e everything that happens under this line of treatment. (Risk of circular dependancies should be managed by business layer)

Medication lines can be grouped either to be related to one treatment (careplan?), or to be treated as inseparable two items of one request (one should not be administered without the other). Grouping is optional, not having grouping should not make the views/exchange cumbersome

Planned variations in posology can be technically one medication line, or it could be several medication lines grouped by care plan (or something similar).

[rlindstrm]

Snapshot as the medication overview in a certain point in time. Ideally calculable from raw data, but could also be specified and tied to a specific use case like Patient Summary). Picture below is a graphic illustration.

[costateixeira]

soem ideas in https://github.com/hl7-be/medication-record/blob/master/input/pagecontent/glossary.md

[costateixeira]

for now ,we start with Medication Overview, and Medication Treatment Line (as used in the logical model)