Generated Narrative: StructureDefinition EHDSDosageObligations Name Flags Card. Type Description & Constraints EHDSDosage 0..* EHDSDosage Dosage model #xD; renderedDosageInstruction O 0..1 string Full dosage information as human-readable text covering all dosage steps. Generating the text follows local rules and should include all locally implemented dosage data even when such elements are not present in this model. Obligations Actor SHOULD:able-to-populate Producer #xD; dosageDetails #xD; note O 0..1 string Patient oriented instructions as free text for this dosage step Obligations Actor SHOULD:able-to-populate Producer #xD; doseAndRate #xD; dose[x] O 0..1 Quantity, Range Amount of medication per one dose. (1 tablet, 2-3 tablets, 20ml) Obligations Actor SHALL:able-to-populate Producer #xD; repeat O 0..1 Base Repetition of the administration. Obligations Actor SHALL:able-to-populate Producer #xD; bounds[x] O 0..1 Quantity, Period Time bounds for the treatment (current dosage scheme), Quantity contains a number of time units (e.g 10 days), Period contains start and end date (e.g. 05.08.2023 - 10.08.2023). Obligations Actor SHALL:able-to-populate Producer #xD; frequency O 0..1 Base Frequency of intake/administration (e.g 'three times a day') Obligations Actor SHALL:able-to-populate Producer #xD; numberOfTimes O 0..1 integer Number of times per period (e.g '3 times') Obligations Actor SHALL:able-to-populate Producer #xD; period O 0..1 Quantity Duration to which the frequency applies (e.g '... / 1 day') Obligations Actor SHALL:able-to-populate Producer #xD; routeOfAdministration O 0..1 CodeableConcept Route of administration Obligations Actor SHOULD:able-to-populate Producer #xD; Documentation for this format
Obligations for the logical model for dosage.
The model covers usage instructions for administering a medicinal product, focusing on the most frequently used data elements. More complex dosage schemes may require additional elements, which should be communicated as part of the rendered dosage instructions element.
Full dosage information as human-readable text covering all dosage steps. Generating the text follows local rules and should include all locally implemented dosage data even when such elements are not present in this model.
Order of the dosage instruction, in case one treatment consists of several dosage steps. When two schemes share the same sequence number, they are meant to be running in parallel.
Patient oriented instructions as free text for this dosage step
Amount of medication administered per one dose (= one timing)
System SHALL support at least Quantity data type for the element. System SHOULD support Range data type for the element.
Amount of medication per one dose. (1 tablet, 2-3 tablets, 20ml)
UCUM (units of measurement), EDQM Standard Terms (units of presentation)
Amount of medication per time period (e.g. 100mg per 1 hour). When rate is provided per 1 time unit, Quantity data type can be used with a suitable unit (e.g. mg/h, ug/min).
System SHALL support at least Quantity data type for the element.
Time bounds for the treatment (current dosage scheme), Quantity contains a number of time units (e.g 10 days), Period contains start and end date (e.g. 05.08.2023 - 10.08.2023).
Duration of administration (e.g '5 minutes', '1 hour')
Frequency of intake/administration (e.g 'three times a day')
Number of times per period (e.g '3 times')
Duration to which the frequency applies (e.g '... / 1 day')
The day of the week of administration, e.g Mon, Tue, etc
Exact time of day of administration (e.g '10:00')
Time period or event when the administration should happen ('before meal', 'immediately', 'morning')