Start date: This is the time at which the agreement was to take effect (or took effect or will take effect). This is the time at which the instructions for use in this agreement start. In the case of an agreement to discontinue use, this is the start date of the original medication agreement. The end date indicates from when the medication is to be discontinued.

End date: The time at which the period of use ends (or ended or will end). In the case of an agreement to discontinue use, this is the time at which the medication is to be discontinued. To avoid confusion between 'to' and 'up to', the submission of time is always mandatory for the end date.

With medication for an indefinite period only a start date is indicated.

According to the HCIM TimeInterval, a time interval is defined by either a start and end time, a start time and duration, or a duration and end time. As this HCIM is expressed by the periodOfUse and usageDuration extensions in this profile, this means that precisely two elements out of .valuePeriod.start, .valuePeriod.end (both in the periodOfUse extension) and .valueDuration (in the usageDuration extension) should be present in order to correctly represent the time interval in which the agreement is used (and in particular not all three elements).

Duration: The intended duration of use. E.g. 5 days or 8 weeks. It is not allowed to indicate the duration in months, because different months have a variable duration in days.

According to the HCIM TimeInterval, a time interval is defined by either a start and end time, a start time and duration, or a duration and end time. As this HCIM is expressed by the periodOfUse and usageDuration extensions in this profile, this means that precisely two elements out of .valuePeriod.start, .valuePeriod.end (both in the periodOfUse extension) and .valueDuration (in the usageDuration extension) should be present in order to correctly represent the time interval in which the agreement is used (and in particular not all three elements).

This extension is to describe which overarching medication treatment this information is part of. This is done by the use of an identifier of that medication treatment.

No HCIM concept is available for this element. Therefore a mapping to the relevant Medication Process data element is provided.

It is recommended to use the nl-core-episodeofcare extension to reference nl-core-episodeofcare (EpisodeOfCare) instances rather than the context element, as this approach will be enforced in FHIR R4.

The repeated period in a cyclical schedule (of one or more dosing instructions). A cyclic schedule is noted in days, the corresponding dosing duration is also in days.

Examples of a cyclical schedule: contraceptive pill (21 days, 1 pill 1x a day, then skip for 7 days, repeat), repeat period here is 28 days. RepeatPeriodCyclicalSchedule

The medicine agreed upon to be used.

It is recommended to use the nl-core-episodeofcare extension to reference nl-core-episodeofcare (EpisodeOfCare) instances rather than the context element, as this approach will be enforced in FHIR R4.

The time at which the agreement was made.

Appointment date + time are required (order of the appointments must be clear in cases with multiple appointments on one day)

Reason for this agreement. This can be the reason to start, change or stop the medication treatment.

The medical reason for the prescription or for use of the medication. This can be used to enter a medical indication which was the direct cause for prescription or for use of the medication in question.

It can concern every type of problem (or condition) of the patient, almost all diagnoses, complaints or symptoms.

Please note: The BST401T file of the G standard contains a “special reference” to indicate that “exchange of the reason for prescription is essential”.

Explanation for the medication agreement.

This explanation can contain e.g. information on why a prescriber makes a medication agreement that deviates from the norm.

Instructions for the use of the medication, e.g. dose and route of administration