MedicationAdministration
Overview
Profile (MedicationAdministration) Administered Medication (either manually reported or reported by an insulin pump) are represented by the MedicationAdministration resource. Medications are generally insulin, but are not limited to insulin. Describes the event of a patient consuming or otherwise being administered a medication.
Below is the
code
that are currently used under this Observation:System Code Display http://roche.com/fhir/iop/cs 67866001_short_acting 67866001_short_acting http://roche.com/fhir/iop/cs 67866001_long_acting 67866001_long_acting
Canonical url - http://roche.com/fhir/iop/StructureDefinition/MedicationAdministration
The below overview shows the elements of the resource, data type and the cardinality of each. Further details like "Binding"/"Fixed values"/"contraints" etc can be found on clicking on each element.
Structure definition :
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.
| |
id | Σ | 0..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. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
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 might 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
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). IETF language tag for a human language
| |
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 can 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 a 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 information is added later.
|
contained | I | 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
|
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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of 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 | I | 0..0 | Identifier | There are no (further) constraints on this element Element idMedicationAdministration.identifier External identifier DefinitionIdentifiers associated with this Medication Administration that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.
|
basedOn | I | 0..0 | Reference(CarePlan) | There are no (further) constraints on this element Element idMedicationAdministration.basedOn Plan this is fulfilled by this administration DefinitionA plan that is fulfilled in whole or in part by this MedicationAdministration. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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.
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | MedicationDispense | Procedure) | Element idMedicationAdministration.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. MedicationDispense will be used to indicate waste. Reference(MedicationAdministration | MedicationDispense | Procedure) Constraints
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.status in-progress | not-done | 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.
|
statusReason | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.statusReason 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.
| |
category | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.category Type of medication administration DefinitionThe type of medication administration (for example, drug classification like ATC, where meds would be administered, legal category of the medication). 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.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.category.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.category.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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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
|
coding | Σ I | 0..* | CodingBinding | Element idMedicationAdministration.category.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.category.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
medication | Σ | 1..1 | CodeableReference(Medication) | There are no (further) constraints on this element Element idMedicationAdministration.medication 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.medication.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.medication.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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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
|
concept | Σ | 0..1 | CodeableConceptBinding | Element idMedicationAdministration.medication.concept Reference to a concept (by class) DefinitionA reference to a concept - e.g. the information is identified by its general class to the degree of precision found in the terminology. 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.
|
reference | Σ I | 0..1 | Reference(Medication) | Element idMedicationAdministration.medication.reference Reference to a resource (by instance) DefinitionA reference to a resource the provides exact details about the information being referenced. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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.
|
subject | Σ I | 1..1 | Reference(Patient | Group) | 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 resolvable (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.
|
encounter | I | 0..0 | Reference(Encounter) | There are no (further) constraints on this element Element idMedicationAdministration.encounter Encounter administered as part of DefinitionThe visit, admission, or other contact between patient and health care provider during which the medication administration was performed. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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.
|
supportingInformation | I | 0..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. This attribute can be used to provide documentation of specific characteristics of the patient present at the time of administration. For example, if the dose says "give "x" if the heartrate exceeds "y"", then the heart rate can be included using this attribute. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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.
|
occurence[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationAdministration.occurence[x] Specific date/time or interval of time during which the administration took place (or did not take place) DefinitionA specific date/time or interval of time during which the administration took place (or did not take place). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate.
| |
occurenceDateTime | dateTime | Data type | ||
occurencePeriod | Period | Data type | ||
recorded | Σ | 0..0 | dateTime | There are no (further) constraints on this element Element idMedicationAdministration.recorded When the MedicationAdministration was first captured in the subject's record DefinitionThe date the occurrence of the MedicationAdministration was first captured in the record - potentially significantly after the occurrence of the event. UTC offset is allowed for dates and partial dates
|
isSubPotent | 0..0 | boolean | There are no (further) constraints on this element Element idMedicationAdministration.isSubPotent Full dose was not administered DefinitionAn indication that the full dose was not administered.
| |
subPotentReason | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.subPotentReason Reason full dose was not administered DefinitionThe reason or reasons why the full dose was not 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. MedicationAdministrationSubpotentReason (example) Constraints
| |
performer | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idMedicationAdministration.performer Who or what performed the medication administration and what type of performance they did DefinitionThe performer of the medication treatment. For devices this is the device that performed the administration of the medication. An IV Pump would be an example of a device that is performing the administration. Both the IV Pump and the practitioner that set the rate or bolus on the pump can be listed as performers.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.performer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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 even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of 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.
|
function | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.performer.function Type of performance DefinitionDistinguishes the type of involvement of the performer in the medication administration. 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 code describing the role an individual played in administering the medication.
| |
actor | Σ | 1..1 | CodeableReference(Practitioner | PractitionerRole | Patient | RelatedPerson | Device) | There are no (further) constraints on this element Element idMedicationAdministration.performer.actor Who or what performed the medication administration DefinitionIndicates who or what performed the medication administration. CodeableReference(Practitioner | PractitionerRole | Patient | RelatedPerson | Device) Constraints
|
reason | 0..0 | CodeableReference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationAdministration.reason Concept, condition or observation that supports why the medication was administered DefinitionA code, Condition or observation that supports why the medication was administered. CodeableReference(Condition | Observation | DiagnosticReport) BindingA set of codes indicating the reason why the MedicationAdministration was made.
| |
request | I | 0..1 | Reference(MedicationRequest) | There are no (further) constraints on this element Element idMedicationAdministration.request Request administration performed against DefinitionThe original request, instruction or authority to perform the administration. This is a reference to the MedicationRequest where the intent is either order or instance-order. It should not reference MedicationRequests where the intent is any other value.
|
device | 0..0 | CodeableReference(Device) | There are no (further) constraints on this element Element idMedicationAdministration.device Device used to administer DefinitionThe device that is to be used for the administration of the medication (for example, PCA Pump).
| |
note | 0..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 | 0..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 Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
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. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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 even if unrecognized 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of 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 | I | 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 SHALL NOT exceed 1,048,576 (1024*1024) characters 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 http://hl7.org/fhir/StructureDefinition/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.
| |
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.
| |
method | 0..1 | CodeableConceptBinding | 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.
| |
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..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 might 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.
|
Attribute description :
Attribute | Description | Terminology reference |
---|---|---|
status | status of MedicationAdministration resource | status |
partOf | Reference to indicate parent MedicationAdminstration | |
Category | Bolus Delivery type | insulin-codes |
medication.concept | Informs the type of administration conducted (ex. Basal or Bolus).. | insulin-codes |
medication.reference | Reference to specific medication administered (Applicable only for commerical drugs - Future imple) | |
Subject | Patient on whom the administration takes place. | |
occurence | Date or period of time over which the administration is conducted (FHIR-Mandatory). | |
Performer | Who (HcP) or what (device) conducted the administration. | |
Request | Medication Request associated to the administration. | |
Dosage | Information about the quantity and units of the administered medication. |