Generated Narrative: StructureDefinition ext-R4-Dosage.doseAndRate Name Flags Card. Type Description & Constraints Extension 0..* Extension R4: Amount of medication administered (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 Extension R4: The kind of dose or rate specified (new) #xD; url 1..1 uri "type" #xD; value[x] 0..1 CodeableConcept The kind of dose or rate specified Binding: R4DoseRateTypeForR3 (0.1.0) (example): The kind of dose or rate specified. #xD; extension:dose 0..1 Extension R4: dose #xD; url 1..1 uri "dose" #xD; value[x] 0..1 Amount of medication per dose #xD; valueRange Range #xD; valueQuantity Quantity(SimpleQuantity) #xD; extension:rate 0..1 Extension R4: rate #xD; url 1..1 uri "rate" #xD; value[x] 0..1 Amount of medication per unit of time #xD; valueRatio Ratio #xD; valueRange Range #xD; valueQuantity Quantity(SimpleQuantity) #xD; url 1..1 uri "http://hl7.org/fhir/4.0/StructureDefinition/extension-Dosage.doseAndRate" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R4: Amount of medication administered (new)
This extension is part of the cross-version definitions generated to enable use of the element `Dosage.doseAndRate` as defined in FHIR R4 in FHIR STU3. The source element is defined as: `Dosage.doseAndRate` 0..* `Element` Following are the generation technical comments: Element `Dosage.doseAndRate` has a context of Dosage based on following the parent source element upwards and mapping to `Dosage`. Element `Dosage.doseAndRate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `Dosage.doseAndRate` has a context of Dosage based on following the parent source element upwards and mapping to `Dosage`. Element `Dosage.doseAndRate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
R4: The kind of dose or rate specified (new)
R4: `Dosage.doseAndRate.type` (new:CodeableConcept)
Element `Dosage.doseAndRate.type` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.type` has a context of Dosage based on following the parent source element upwards and mapping to `Dosage`. Element `Dosage.doseAndRate.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
If the type is not populated, assume to be "ordered". Element `Dosage.doseAndRate.type` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.type` has a context of Dosage based on following the parent source element upwards and mapping to `Dosage`. Element `Dosage.doseAndRate.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
The kind of dose or rate specified, for example, ordered or calculated.
Element `Dosage.doseAndRate.dose[x]` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.dose[x]` is mapped to FHIR STU3 element `Dosage.dose[x]` as `Equivalent`. The target context `Dosage.dose[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Dosage`. 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.
The amount of therapeutic or other substance given at one administration event. Element `Dosage.doseAndRate.dose[x]` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.dose[x]` is mapped to FHIR STU3 element `Dosage.dose[x]` as `Equivalent`. The target context `Dosage.dose[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Dosage`.
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.
Element `Dosage.doseAndRate.rate[x]` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.rate[x]` is mapped to FHIR STU3 element `Dosage.rate[x]` as `Equivalent`. The target context `Dosage.rate[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Dosage`. 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.
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. Element `Dosage.doseAndRate.rate[x]` is part of an existing definition because parent element `Dosage.doseAndRate` requires a cross-version extension. Element `Dosage.doseAndRate.rate[x]` is mapped to FHIR STU3 element `Dosage.rate[x]` as `Equivalent`. The target context `Dosage.rate[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Dosage`.
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.
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).