medication-administration-discharge-summary (MedicationAdministration) | I | MedicationAdministration | There are no (further) constraints on this element Element idMedicationAdministration Administration of medication to a patient DefinitionDescribes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. The WG will be updating the MedicationAdministration resource to adjust each affected resource to align with the workflow pattern (see workflow.html).
| |
id | Σ | 1..1 | id | There are no (further) constraints on this element Element idMedicationAdministration.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
|
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationAdministration.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationAdministration.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language. Common Languages (extensible)Constraints
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationAdministration.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
|
contained | 0..* | Resource | There are no (further) constraints on this element Element idMedicationAdministration.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | 0..* | Identifier | There are no (further) constraints on this element Element idMedicationAdministration.identifier External identifier DefinitionExternal identifier - FHIR will generate its own internal identifiers (probably URLs) which do not need to be explicitly managed by the resource. The identifier here is one that would be used by another non-FHIR system - for example an automated medication pump would provide a record each time it operated; an administration while the patient was off the ward might be made with a different system and entered after the event. Particularly important if these records have to be updated.
| |
definition | Σ I | 0..* | Reference(PlanDefinition | ActivityDefinition) | There are no (further) constraints on this element Element idMedicationAdministration.definition Instantiates protocol or definition DefinitionA protocol, guideline, orderset or other definition that was adhered to in whole or in part by this event. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(PlanDefinition | ActivityDefinition) Constraints
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | Procedure) | There are no (further) constraints on this element Element idMedicationAdministration.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(MedicationAdministration | Procedure) Constraints
|
status | Σ ?! | 1..1 | codeBindingFixed Value | There are no (further) constraints on this element Element idMedicationAdministration.status in-progress | on-hold | completed | entered-in-error | stopped | unknown DefinitionWill generally be set to show that the administration has been completed. For some long running administrations such as infusions it is possible for an administration to be started but not completed or it may be paused while some other process is under way. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A set of codes indicating the current status of a MedicationAdministration. MedicationAdministrationStatus (required)Constraints
completed
|
category | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idMedicationAdministration.category Type of medication usage DefinitionIndicates the type of medication administration and where the medication is expected to be consumed or administered. 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 where the medication administered is expected to occur MedicationAdministrationCategory (preferred)Constraints
| |
medication[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationAdministration.medication[x] What was administered DefinitionIdentifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example if you require form or lot number, then you must reference the Medication resource. . Codes identifying substance or product that can be administered. SNOMED CT Medication Codes (example)Constraints
| |
medicationCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
medicationReference | Reference(medication-discharge-summary) | There are no (further) constraints on this element Data type Reference(medication-discharge-summary) Allowed aggregation: referenced, bundled | ||
subject | Σ I | 1..1 | Reference(patient-discharge-summary) | There are no (further) constraints on this element Element idMedicationAdministration.subject Who received medication DefinitionThe person or animal or group receiving the medication. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(patient-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
context | I | 0..1 | Reference(encounter-discharge-summary) | There are no (further) constraints on this element Element idMedicationAdministration.context Encounter or Episode of Care administered as part of DefinitionThe visit, admission or other contact between patient and health care provider the medication administration was performed as part of. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(encounter-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
supportingInformation | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationAdministration.supportingInformation Additional information to support administration DefinitionAdditional information (for example, patient height and weight) that supports the administration of the medication. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
effective[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationAdministration.effective[x] Start and end time of administration DefinitionA specific date/time or interval of time during which the administration took place (or did not take place, when the 'notGiven' attribute is true). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate.
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||
performer | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idMedicationAdministration.performer Who administered substance DefinitionThe individual who was responsible for giving the medication to the patient.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.performer.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.performer.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.performer.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. 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.
|
actor | Σ I | 1..1 | Reference(practitioner-discharge-summary) | There are no (further) constraints on this element Element idMedicationAdministration.performer.actor Individual who was performing DefinitionThe device, practitioner, etc. who performed the action. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(practitioner-discharge-summary) Allowed aggregation: referenced, bundled Constraints
|
onBehalfOf | I | 0..1 | Reference(Organization) | There are no (further) constraints on this element Element idMedicationAdministration.performer.onBehalfOf Organization organization was acting for DefinitionThe organization the device or practitioner was acting on behalf of. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
notGiven | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idMedicationAdministration.notGiven True if medication not administered DefinitionSet this to true if the record is saying that the medication was NOT administered. This element is labeled as a modifier because it indicates that a administration didn't happen. If this is missing, then the medication was administered
|
reasonNotGiven | I | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.reasonNotGiven Reason administration not performed DefinitionA code indicating why the administration was not performed. 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 set of codes indicating the reason why the MedicationAdministration is negated. SNOMED CT Reason Medication Not Given Codes (example)Constraints
|
reasonCode | I | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.reasonCode Reason administration performed DefinitionA code indicating why the medication was given. 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 set of codes indicating the reason why the MedicationAdministration was made. Reason Medication Given Codes (example)Constraints
|
reasonReference | I | 0..* | Reference(Condition | Observation) | There are no (further) constraints on this element Element idMedicationAdministration.reasonReference Condition or Observation that supports why the medication was administered DefinitionCondition or observation that supports why the medication was administered. This is a reference to a condition that is the reason for the medication request. If only a code exists, use reasonCode. Reference(Condition | Observation) Constraints
|
prescription | I | 0..1 | Reference(MedicationRequest) | There are no (further) constraints on this element Element idMedicationAdministration.prescription Request administration performed against DefinitionThe original request, instruction or authority to perform the administration. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
device | I | 0..* | Reference(Device) | There are no (further) constraints on this element Element idMedicationAdministration.device Device used to administer DefinitionThe device used in administering the medication to the patient. For example, a particular infusion pump. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element idMedicationAdministration.note Information about the administration DefinitionExtra information about the medication administration that is not conveyed by the other attributes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
dosage | I | 1..1 | BackboneElement | There are no (further) constraints on this element Element idMedicationAdministration.dosage Details of how medication was taken DefinitionDescribes the medication dosage information details e.g. dose, rate, site, route, etc.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Note that FHIR strings may not exceed 1MB in size
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.dosage.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.dosage.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. 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.
|
text | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.text Free text dosage instructions e.g. SIG DefinitionFree text dosage can be used for cases where the dosage administered is too complex to code. When coded dosage is present, the free text dosage may still be present for display to humans. The dosage instructions should reflect the dosage of the medication that was administered. Note that FHIR strings may not exceed 1MB in size
| |
site | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.site Body site administered to DefinitionA coded specification of the anatomic site where the medication first entered the body. For example, "left arm". If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension body-site-instance. 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. SNOMED CT Anatomical Structure for Administration Site Codes (example)Constraints
| |
route | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.route Path of substance into body DefinitionA code specifying the route or physiological path of administration of a therapeutic agent into or onto the patient. For example, topical, intravenous, etc. 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. SNOMED CT Route Codes (example)Constraints
| |
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.method How drug was administered DefinitionA coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. For example, Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequently. A coded concept describing the technique by which the medicine is administered. SNOMED CT Administration Method Codes (example)Constraints
| |
dose | I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose Amount of medication per dose DefinitionThe amount of the medication given at one administration event. Use this value when the administration is essentially an instantaneous event such as a swallowing a tablet or giving an injection. If the administration is not instantaneous (rate is present), this can be specified to convey the total amount administered over period of time of a single administration.
|
rate[x] | I | 0..1 | There are no (further) constraints on this element Element idMedicationAdministration.dosage.rate[x] Dose quantity per unit of time DefinitionIdentifies 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. If the rate changes over time, and you want to capture this in MedicationAdministration, then each change should be captured as a distinct MedicationAdministration, with a specific MedicationAdministration.dosage.rate, and the date time when the rate change occurred. Typically, the MedicationAdministration.dosage.rate element is not used to convey an average rate.
| |
rateRatio | Ratio | There are no (further) constraints on this element Data type | ||
rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data type | ||
eventHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idMedicationAdministration.eventHistory A list of events of interest in the lifecycle DefinitionA summary of the events of interest that have occurred, such as when the administration was verified. This may not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
MedicationAdministration | 0..* | |
MedicationAdministration.id | id | 1..1 |
MedicationAdministration.meta | Meta | 0..1 |
MedicationAdministration.implicitRules | uri | 0..1 |
MedicationAdministration.language | code | 0..1 |
MedicationAdministration.text | Narrative | 0..1 |
MedicationAdministration.contained | Resource | 0..* |
MedicationAdministration.extension | Extension | 0..* |
MedicationAdministration.modifierExtension | Extension | 0..* |
MedicationAdministration.identifier | Identifier | 0..* |
MedicationAdministration.definition | Reference(PlanDefinition | ActivityDefinition) | 0..* |
MedicationAdministration.partOf | Reference(MedicationAdministration | Procedure) | 0..* |
MedicationAdministration.status | code | 1..1 |
MedicationAdministration.category | CodeableConcept | 0..1 |
MedicationAdministration.medication[x] | Reference(medication-discharge-summary), CodeableConcept | 1..1 |
MedicationAdministration.subject | Reference(patient-discharge-summary) | 1..1 |
MedicationAdministration.context | Reference(encounter-discharge-summary) | 0..1 |
MedicationAdministration.supportingInformation | Reference(Resource) | 0..* |
MedicationAdministration.effective[x] | dateTime, Period | 1..1 |
MedicationAdministration.performer | BackboneElement | 0..* |
MedicationAdministration.performer.id | string | 0..1 |
MedicationAdministration.performer.extension | Extension | 0..* |
MedicationAdministration.performer.modifierExtension | Extension | 0..* |
MedicationAdministration.performer.actor | Reference(practitioner-discharge-summary) | 1..1 |
MedicationAdministration.performer.onBehalfOf | Reference(Organization) | 0..1 |
MedicationAdministration.notGiven | boolean | 0..1 |
MedicationAdministration.reasonNotGiven | CodeableConcept | 0..* |
MedicationAdministration.reasonCode | CodeableConcept | 0..* |
MedicationAdministration.reasonReference | Reference(Condition | Observation) | 0..* |
MedicationAdministration.prescription | Reference(MedicationRequest) | 0..1 |
MedicationAdministration.device | Reference(Device) | 0..* |
MedicationAdministration.note | Annotation | 0..* |
MedicationAdministration.dosage | BackboneElement | 1..1 |
MedicationAdministration.dosage.id | string | 0..1 |
MedicationAdministration.dosage.extension | Extension | 0..* |
MedicationAdministration.dosage.modifierExtension | Extension | 0..* |
MedicationAdministration.dosage.text | string | 0..1 |
MedicationAdministration.dosage.site | CodeableConcept | 0..1 |
MedicationAdministration.dosage.route | CodeableConcept | 0..1 |
MedicationAdministration.dosage.method | CodeableConcept | 0..1 |
MedicationAdministration.dosage.dose | SimpleQuantity | 0..1 |
MedicationAdministration.dosage.rate[x] | Ratio, SimpleQuantity | 0..1 |
MedicationAdministration.eventHistory | Reference(Provenance) | 0..* |