DataStandardsWales-Dosage
The Dosage resource is a record of a medication that is administered to a patient.
The DataStandardsWales-Dosage profile is derived from the HL7 Dosage Profile. It defines additional rules for use within health and care organisations in Wales.
Formal Views of Profile Content
- Snapshot View
- Differential View
- Hybrid View
- Examples
| Dosage | Dosage | There are no (further) constraints on this element Element IdDosage How the medication is/was taken or should be taken DefinitionIndicates how the medication is/was taken or should be taken by the patient.
| ||
| sequence | S Σ | 0..1 | integer | Element IdDosage.sequence Multi-sequence dosage instructions. DefinitionTBD If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential. 32 bit number; for values larger than this, use decimal
|
| text | S Σ | 0..1 | string | Element IdDosage.text The complete dosage instruction as a human readable string. DefinitionTBD Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text. Note that FHIR strings SHALL NOT exceed 1MB in size
|
| additionalInstruction | S Σ | 0..* | CodeableConcept | Element IdDosage.additionalInstruction Additional dosage instructions that can be either SNOMED-CT coded terms or free-text instructions. DefinitionTBD Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded. Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text. A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". SNOMEDCTAdditionalDosageInstructions (example)Constraints
|
| patientInstruction | S Σ | 0..1 | string | Element IdDosage.patientInstruction Patient or consumer oriented instructions DefinitionTBD Note that FHIR strings SHALL NOT exceed 1MB in size
|
| timing | S Σ | 0..1 | Timing | Element IdDosage.timing When medication should be administered DefinitionTBD The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.
|
| event | Σ | 0..* | dateTime | There are no (further) constraints on this element Element IdDosage.timing.event When the event occurs DefinitionIdentifies specific times when the event occurs. In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.
|
| repeat | Σ I | 0..1 | Element | There are no (further) constraints on this element Element IdDosage.timing.repeat When the event is to occur DefinitionA set of rules that describe when the event is scheduled. Many timing schedules are determined by regular repetitions.
|
| bounds[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.timing.repeat.bounds[x] Length/Range of lengths, or (Start and/or end) limits DefinitionEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.
| |
| boundsDuration | Duration | Data Type | ||
| boundsRange | Range | Data Type | ||
| boundsPeriod | Period | Data Type | ||
| count | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.count Number of times to repeat DefinitionA total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values. Repetitions may be limited by end time or total occurrences. If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.
|
| countMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.countMax Maximum number of times to repeat DefinitionIf present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. 32 bit number; for values larger than this, use decimal
|
| duration | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.duration How long when it happens DefinitionHow long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationMax How long when it happens (Max) DefinitionIf present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the duration, in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| frequency | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequency Event occurs frequency times per period DefinitionThe number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency. 32 bit number; for values larger than this, use decimal If no frequency is stated, the assumption is that the event occurs once per period, but systems SHOULD always be specific about this
|
| frequencyMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequencyMax Event occurs up to frequencyMax times per period DefinitionIf present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. 32 bit number; for values larger than this, use decimal
|
| period | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.period Event occurs frequency times per period DefinitionIndicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodMax Upper limit of period (3-4 hours) DefinitionIf present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the period in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| dayOfWeek | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.dayOfWeek mon | tue | wed | thu | fri | sat | sun DefinitionIf one or more days of week is provided, then the action happens only on the specified day(s). If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.
|
| timeOfDay | Σ | 0..* | time | There are no (further) constraints on this element Element IdDosage.timing.repeat.timeOfDay Time of day for action DefinitionSpecified time of day for action to take place. When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.
|
| when | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.when Code for time period of occurrence DefinitionAn approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. Timings are frequently determined by occurrences such as waking, eating and sleep. When more than one event is listed, the event is tied to the union of the specified events. Real world event relating to the schedule. EventTiming (required)Constraints
|
| offset | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.offset Minutes from event (before or after) DefinitionThe number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event. 32 bit number; for values larger than this, use decimal
|
| code | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDosage.timing.code BID | TID | QID | AM | PM | QD | QOD | + DefinitionA code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code). BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times). Code for a known / defined timing pattern. TimingAbbreviation (preferred)Constraints
|
| asNeeded[x] | S Σ | 0..1 | Element IdDosage.asNeeded[x] Take "as needed" (for x) DefinitionTBD Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed". A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |
| asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||
| asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
| site | S Σ | 0..1 | CodeableConcept | Element IdDosage.site Body site to administer to DefinitionTBD A coded specification of the anatomic site where the medication first enters the body. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body. SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)Constraints
|
| route | S Σ | 0..1 | CodeableConcept | Element IdDosage.route How drug should enter body DefinitionTBD A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. SNOMEDCTRouteCodes (example)Constraints
|
| method | S Σ | 0..1 | CodeableConcept | Element IdDosage.method Technique for administering medication DefinitionTBD A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV. Terminologies used often pre-coordinate this term with the route and or form of administration. A coded concept describing the technique by which the medicine is administered. SNOMEDCTAdministrationMethodCodes (example)Constraints
|
| doseAndRate | Σ | 0..* | Element | Element IdDosage.doseAndRate Amount of medication administered DefinitionTBD
|
| type | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDosage.doseAndRate.type The kind of dose or rate specified DefinitionThe kind of dose or rate specified, for example, ordered or calculated. If the type is not populated, assume to be "ordered". Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The kind of dose or rate specified. DoseAndRateType (example)Constraints
|
| dose[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.dose[x] Amount of medication per dose DefinitionAmount of medication per dose. The amount of therapeutic or other substance given at one administration event. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.
| |
| doseRange | Range | Data Type | ||
| doseQuantity | SimpleQuantity | Data Type | ||
| rate[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.rate[x] Amount of medication per unit of time DefinitionAmount of medication per unit of time. Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate. It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.
| |
| rateRatio | Ratio | There are no (further) constraints on this element Data Type | ||
| rateRange | Range | There are no (further) constraints on this element Data Type | ||
| rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data Type | ||
| maxDosePerPeriod | S Σ I | 0..1 | Ratio | Element IdDosage.maxDosePerPeriod Upper limit on medication per unit of time DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".
|
| maxDosePerAdministration | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerAdministration Upper limit on medication per administration DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.
|
| maxDosePerLifetime | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerLifetime Upper limit on medication per lifetime of the patient DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
| Dosage | Dosage | There are no (further) constraints on this element Element IdDosage How the medication is/was taken or should be taken DefinitionIndicates how the medication is/was taken or should be taken by the patient.
| ||
| sequence | S Σ | 0..1 | integer | Element IdDosage.sequence Multi-sequence dosage instructions. DefinitionTBD If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential. 32 bit number; for values larger than this, use decimal
|
| text | S Σ | 0..1 | string | Element IdDosage.text The complete dosage instruction as a human readable string. DefinitionTBD Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text. Note that FHIR strings SHALL NOT exceed 1MB in size
|
| additionalInstruction | S Σ | 0..* | CodeableConcept | Element IdDosage.additionalInstruction Additional dosage instructions that can be either SNOMED-CT coded terms or free-text instructions. DefinitionTBD Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded. Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text. A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". SNOMEDCTAdditionalDosageInstructions (example)Constraints
|
| patientInstruction | S Σ | 0..1 | string | Element IdDosage.patientInstruction Patient or consumer oriented instructions DefinitionTBD Note that FHIR strings SHALL NOT exceed 1MB in size
|
| timing | S Σ | 0..1 | Timing | Element IdDosage.timing When medication should be administered DefinitionTBD The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.
|
| event | Σ | 0..* | dateTime | There are no (further) constraints on this element Element IdDosage.timing.event When the event occurs DefinitionIdentifies specific times when the event occurs. In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.
|
| repeat | Σ I | 0..1 | Element | There are no (further) constraints on this element Element IdDosage.timing.repeat When the event is to occur DefinitionA set of rules that describe when the event is scheduled. Many timing schedules are determined by regular repetitions.
|
| bounds[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.timing.repeat.bounds[x] Length/Range of lengths, or (Start and/or end) limits DefinitionEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.
| |
| boundsDuration | Duration | Data Type | ||
| boundsRange | Range | Data Type | ||
| boundsPeriod | Period | Data Type | ||
| count | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.count Number of times to repeat DefinitionA total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values. Repetitions may be limited by end time or total occurrences. If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.
|
| countMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.countMax Maximum number of times to repeat DefinitionIf present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. 32 bit number; for values larger than this, use decimal
|
| duration | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.duration How long when it happens DefinitionHow long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationMax How long when it happens (Max) DefinitionIf present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the duration, in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| frequency | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequency Event occurs frequency times per period DefinitionThe number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency. 32 bit number; for values larger than this, use decimal If no frequency is stated, the assumption is that the event occurs once per period, but systems SHOULD always be specific about this
|
| frequencyMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequencyMax Event occurs up to frequencyMax times per period DefinitionIf present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. 32 bit number; for values larger than this, use decimal
|
| period | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.period Event occurs frequency times per period DefinitionIndicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodMax Upper limit of period (3-4 hours) DefinitionIf present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the period in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| dayOfWeek | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.dayOfWeek mon | tue | wed | thu | fri | sat | sun DefinitionIf one or more days of week is provided, then the action happens only on the specified day(s). If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.
|
| timeOfDay | Σ | 0..* | time | There are no (further) constraints on this element Element IdDosage.timing.repeat.timeOfDay Time of day for action DefinitionSpecified time of day for action to take place. When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.
|
| when | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.when Code for time period of occurrence DefinitionAn approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. Timings are frequently determined by occurrences such as waking, eating and sleep. When more than one event is listed, the event is tied to the union of the specified events. Real world event relating to the schedule. EventTiming (required)Constraints
|
| offset | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.offset Minutes from event (before or after) DefinitionThe number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event. 32 bit number; for values larger than this, use decimal
|
| code | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDosage.timing.code BID | TID | QID | AM | PM | QD | QOD | + DefinitionA code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code). BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times). Code for a known / defined timing pattern. TimingAbbreviation (preferred)Constraints
|
| asNeeded[x] | S Σ | 0..1 | Element IdDosage.asNeeded[x] Take "as needed" (for x) DefinitionTBD Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed". A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |
| asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||
| asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
| site | S Σ | 0..1 | CodeableConcept | Element IdDosage.site Body site to administer to DefinitionTBD A coded specification of the anatomic site where the medication first enters the body. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body. SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)Constraints
|
| route | S Σ | 0..1 | CodeableConcept | Element IdDosage.route How drug should enter body DefinitionTBD A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. SNOMEDCTRouteCodes (example)Constraints
|
| method | S Σ | 0..1 | CodeableConcept | Element IdDosage.method Technique for administering medication DefinitionTBD A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV. Terminologies used often pre-coordinate this term with the route and or form of administration. A coded concept describing the technique by which the medicine is administered. SNOMEDCTAdministrationMethodCodes (example)Constraints
|
| doseAndRate | Σ | 0..* | Element | Element IdDosage.doseAndRate Amount of medication administered DefinitionTBD
|
| type | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDosage.doseAndRate.type The kind of dose or rate specified DefinitionThe kind of dose or rate specified, for example, ordered or calculated. If the type is not populated, assume to be "ordered". Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The kind of dose or rate specified. DoseAndRateType (example)Constraints
|
| dose[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.dose[x] Amount of medication per dose DefinitionAmount of medication per dose. The amount of therapeutic or other substance given at one administration event. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.
| |
| doseRange | Range | Data Type | ||
| doseQuantity | SimpleQuantity | Data Type | ||
| rate[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.rate[x] Amount of medication per unit of time DefinitionAmount of medication per unit of time. Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate. It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.
| |
| rateRatio | Ratio | There are no (further) constraints on this element Data Type | ||
| rateRange | Range | There are no (further) constraints on this element Data Type | ||
| rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data Type | ||
| maxDosePerPeriod | S Σ I | 0..1 | Ratio | Element IdDosage.maxDosePerPeriod Upper limit on medication per unit of time DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".
|
| maxDosePerAdministration | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerAdministration Upper limit on medication per administration DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.
|
| maxDosePerLifetime | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerLifetime Upper limit on medication per lifetime of the patient DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
| Dosage | Dosage | There are no (further) constraints on this element Element IdDosage How the medication is/was taken or should be taken DefinitionIndicates how the medication is/was taken or should be taken by the patient.
| ||
| sequence | S Σ | 0..1 | integer | Element IdDosage.sequence Multi-sequence dosage instructions. DefinitionTBD If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential. 32 bit number; for values larger than this, use decimal
|
| text | S Σ | 0..1 | string | Element IdDosage.text The complete dosage instruction as a human readable string. DefinitionTBD Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text. Note that FHIR strings SHALL NOT exceed 1MB in size
|
| additionalInstruction | S Σ | 0..* | CodeableConcept | Element IdDosage.additionalInstruction Additional dosage instructions that can be either SNOMED-CT coded terms or free-text instructions. DefinitionTBD Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded. Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text. A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery". SNOMEDCTAdditionalDosageInstructions (example)Constraints
|
| patientInstruction | S Σ | 0..1 | string | Element IdDosage.patientInstruction Patient or consumer oriented instructions DefinitionTBD Note that FHIR strings SHALL NOT exceed 1MB in size
|
| timing | S Σ | 0..1 | Timing | Element IdDosage.timing When medication should be administered DefinitionTBD The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.
|
| event | Σ | 0..* | dateTime | There are no (further) constraints on this element Element IdDosage.timing.event When the event occurs DefinitionIdentifies specific times when the event occurs. In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.
|
| repeat | Σ I | 0..1 | Element | There are no (further) constraints on this element Element IdDosage.timing.repeat When the event is to occur DefinitionA set of rules that describe when the event is scheduled. Many timing schedules are determined by regular repetitions.
|
| bounds[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.timing.repeat.bounds[x] Length/Range of lengths, or (Start and/or end) limits DefinitionEither a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.
| |
| boundsDuration | Duration | Data Type | ||
| boundsRange | Range | Data Type | ||
| boundsPeriod | Period | Data Type | ||
| count | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.count Number of times to repeat DefinitionA total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values. Repetitions may be limited by end time or total occurrences. If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.
|
| countMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.countMax Maximum number of times to repeat DefinitionIf present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. 32 bit number; for values larger than this, use decimal
|
| duration | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.duration How long when it happens DefinitionHow long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationMax How long when it happens (Max) DefinitionIf present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. Some activities are not instantaneous and need to be maintained for a period of time. For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).
|
| durationUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.durationUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the duration, in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| frequency | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequency Event occurs frequency times per period DefinitionThe number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency. 32 bit number; for values larger than this, use decimal If no frequency is stated, the assumption is that the event occurs once per period, but systems SHOULD always be specific about this
|
| frequencyMax | Σ | 0..1 | positiveInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.frequencyMax Event occurs up to frequencyMax times per period DefinitionIf present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. 32 bit number; for values larger than this, use decimal
|
| period | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.period Event occurs frequency times per period DefinitionIndicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodMax | Σ | 0..1 | decimal | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodMax Upper limit of period (3-4 hours) DefinitionIf present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger)
|
| periodUnit | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.periodUnit s | min | h | d | wk | mo | a - unit of time (UCUM) DefinitionThe units of time for the period in UCUM units. Note that FHIR strings SHALL NOT exceed 1MB in size A unit of time (units from UCUM). UnitsOfTime (required)Constraints
|
| dayOfWeek | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.dayOfWeek mon | tue | wed | thu | fri | sat | sun DefinitionIf one or more days of week is provided, then the action happens only on the specified day(s). If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.
|
| timeOfDay | Σ | 0..* | time | There are no (further) constraints on this element Element IdDosage.timing.repeat.timeOfDay Time of day for action DefinitionSpecified time of day for action to take place. When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.
|
| when | Σ | 0..* | codeBinding | There are no (further) constraints on this element Element IdDosage.timing.repeat.when Code for time period of occurrence DefinitionAn approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. Timings are frequently determined by occurrences such as waking, eating and sleep. When more than one event is listed, the event is tied to the union of the specified events. Real world event relating to the schedule. EventTiming (required)Constraints
|
| offset | Σ | 0..1 | unsignedInt | There are no (further) constraints on this element Element IdDosage.timing.repeat.offset Minutes from event (before or after) DefinitionThe number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event. 32 bit number; for values larger than this, use decimal
|
| code | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdDosage.timing.code BID | TID | QID | AM | PM | QD | QOD | + DefinitionA code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code). BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times). Code for a known / defined timing pattern. TimingAbbreviation (preferred)Constraints
|
| asNeeded[x] | S Σ | 0..1 | Element IdDosage.asNeeded[x] Take "as needed" (for x) DefinitionTBD Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed". A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc. SNOMEDCTMedicationAsNeededReasonCodes (example)Constraints
| |
| asNeededBoolean | boolean | There are no (further) constraints on this element Data Type | ||
| asNeededCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
| site | S Σ | 0..1 | CodeableConcept | Element IdDosage.site Body site to administer to DefinitionTBD A coded specification of the anatomic site where the medication first enters the body. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body. SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)Constraints
|
| route | S Σ | 0..1 | CodeableConcept | Element IdDosage.route How drug should enter body DefinitionTBD A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject. SNOMEDCTRouteCodes (example)Constraints
|
| method | S Σ | 0..1 | CodeableConcept | Element IdDosage.method Technique for administering medication DefinitionTBD A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV. Terminologies used often pre-coordinate this term with the route and or form of administration. A coded concept describing the technique by which the medicine is administered. SNOMEDCTAdministrationMethodCodes (example)Constraints
|
| doseAndRate | Σ | 0..* | Element | Element IdDosage.doseAndRate Amount of medication administered DefinitionTBD
|
| type | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdDosage.doseAndRate.type The kind of dose or rate specified DefinitionThe kind of dose or rate specified, for example, ordered or calculated. If the type is not populated, assume to be "ordered". Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The kind of dose or rate specified. DoseAndRateType (example)Constraints
|
| dose[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.dose[x] Amount of medication per dose DefinitionAmount of medication per dose. The amount of therapeutic or other substance given at one administration event. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.
| |
| doseRange | Range | Data Type | ||
| doseQuantity | SimpleQuantity | Data Type | ||
| rate[x] | Σ | 0..1 | There are no (further) constraints on this element Element IdDosage.doseAndRate.rate[x] Amount of medication per unit of time DefinitionAmount of medication per unit of time. Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate. It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.
| |
| rateRatio | Ratio | There are no (further) constraints on this element Data Type | ||
| rateRange | Range | There are no (further) constraints on this element Data Type | ||
| rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data Type | ||
| maxDosePerPeriod | S Σ I | 0..1 | Ratio | Element IdDosage.maxDosePerPeriod Upper limit on medication per unit of time DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".
|
| maxDosePerAdministration | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerAdministration Upper limit on medication per administration DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.
|
| maxDosePerLifetime | Σ I | 0..1 | SimpleQuantity | Element IdDosage.maxDosePerLifetime Upper limit on medication per lifetime of the patient DefinitionTBD The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
Mandatory and Must Support Data Elements
When an element is mandatory (min=1), the data is expected to always be present. Elements marked with an S must be supported by both producing and receiving systems and SHOULD be populated if the data exists.
Each MedicationAdministration must support:
- sequence
- text
- additionalInstruction
- patientInstruction
- timing
- asNeeded
- site
- route
- method
- maxDosePerPeriod