Describes 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.

A 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 it's narrative along with other profiles, value sets, etc.

May 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 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

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.

EVT 中給予的鎮靜藥，參照該次 EVT 主處置（code 為 evt）。動脈內藥物參照動脈內藥物治療處置（code 為 intra-arterial-drug-therapy）或 EVT 主處置。能確認屬於同一次 EVT 時才填。IV-tPA 不屬於 EVT 處置，不填。

來源明確記錄已給藥，填 completed。明確記錄未給藥，填 not-done；未給藥也要有預定給藥時間才建立，沒有時改存登錄表單。有給藥紀錄但無法確認是否完成，填 unknown。來源空白時不建立本資源。

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.

只用 CodeableConcept 記錄。IV-tPA 品項未明時，coding 填 StrokeMedicationCS 的 iv-tpa-unspecified。鎮靜藥與動脈內藥物只有藥名時只填 text，原樣保留藥名。coding 與 text 至少填一個。

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.

A reference to a code defined by a terminology system.

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.

Allows for alternative encodings within a code system, and translations to other code systems.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

填 StrokeMedicationCS 的代碼。IV-tPA 品項未明時填 iv-tpa-unspecified。院方核定藥品主檔後，可另加院內或健保藥品代碼。

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.

Allows for alternative encodings within a code system, and translations to other code systems.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

鎮靜藥與動脈內藥物只有名稱時，原樣填入藥名。

Very often the text is the same as a displayName of one of the codings.

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.

The person or animal or group receiving the medication.

The visit, admission, or other contact between patient and health care provider during which the medication administration was performed.

填實際給藥時間；未給藥填預定給藥時間。確認時區前只填日期（YYYY-MM-DD），時間原值用 StrokeEventTimeOnly 擴充附在此元素，並存入 StrokeRegistryResponse 的原始值題目；確認後把同一次給藥的日期與時間合併為 dateTime 並帶時區（例如 +08:00）。只有年月時填 YYYY-MM。只有時間沒有日期時，effectiveDateTime 不填值，改在其 extension 放 StrokeEventTimeOnly。日期與時間都沒有時不建立本資源。

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them Other type slices that contain no new information are not shown in this view

A 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.

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

只用於 dateTime 型別元素；choice 元素只用 dateTime 分支，Period 用於 start 與 end。兩種用法：一、來源只有時間、沒有日期：原元素不填值，只在該元素的 extension 放入本 Extension，例如 Procedure._performedDateTime；此用法不適用 Observation.effective[x]，評估時間缺日期時改存登錄表單。二、來源有日期與時間但時區尚未確認：原元素只填日期（YYYY-MM-DD），並在該元素的 extension 放入本 Extension 保留來源時鐘時間。

劑量無法可靠解析成數值與單位，或該藥劑量單位未經院方核定時，把來源劑量原文填在 note.text，不建立 dosage。

能可靠解析出劑量（dose）或速率（rate），且單位經院方核定時才填。依 mad-1，有 dosage 時 dose 或 rate 至少填一個。無法解析時不建立 dosage，原文改填 note。

May 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 manageable, 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).

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.

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.

已填 dose 或 rate 時，可在此保留來源劑量原文。

value 填劑量數值，unit 填單位文字，system 固定為 http://unitsofmeasure.org，code 填 UCUM 單位代碼。IV-tPA 以毫克記錄，code 必須填 mg（stroke-medadmin-2）。鎮靜藥與動脈內藥物要在院方已核定該藥的劑量單位，且來源劑量能可靠解析成數值與單位時才填 dose，例如 mg、ug（微克）或 [iU]（國際單位）；否則原文改填 note。

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.

The value of the measured amount. The value includes an implicit precision in the presentation of the value.

The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).

Precision is handled implicitly in almost all cases of measurement.

Not allowed to be used in this context

How the Quantity should be understood and represented.

Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

A human-readable form of the unit.

There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

The identification of the system that provides the coded form of the unit.

Need to know the system that defines the coded form of the unit.

A computer processable form of the unit in some unit representation system.

The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.

Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

EVT 中給予的鎮靜藥，參照該次 EVT 主處置（code 為 evt）。動脈內藥物參照動脈內藥物治療處置（code 為 intra-arterial-drug-therapy）或 EVT 主處置。能確認屬於同一次 EVT 時才填。IV-tPA 不屬於 EVT 處置，不填。

來源明確記錄已給藥，填 completed。明確記錄未給藥，填 not-done；未給藥也要有預定給藥時間才建立，沒有時改存登錄表單。有給藥紀錄但無法確認是否完成，填 unknown。來源空白時不建立本資源。

只用 CodeableConcept 記錄。IV-tPA 品項未明時，coding 填 StrokeMedicationCS 的 iv-tpa-unspecified。鎮靜藥與動脈內藥物只有藥名時只填 text，原樣保留藥名。coding 與 text 至少填一個。

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

填 StrokeMedicationCS 的代碼。IV-tPA 品項未明時填 iv-tpa-unspecified。院方核定藥品主檔後，可另加院內或健保藥品代碼。

鎮靜藥與動脈內藥物只有名稱時，原樣填入藥名。

填實際給藥時間；未給藥填預定給藥時間。確認時區前只填日期（YYYY-MM-DD），時間原值用 StrokeEventTimeOnly 擴充附在此元素，並存入 StrokeRegistryResponse 的原始值題目；確認後把同一次給藥的日期與時間合併為 dateTime 並帶時區（例如 +08:00）。只有年月時填 YYYY-MM。只有時間沒有日期時，effectiveDateTime 不填值，改在其 extension 放 StrokeEventTimeOnly。日期與時間都沒有時不建立本資源。

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them Other type slices that contain no new information are not shown in this view

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

劑量無法可靠解析成數值與單位，或該藥劑量單位未經院方核定時，把來源劑量原文填在 note.text，不建立 dosage。

能可靠解析出劑量（dose）或速率（rate），且單位經院方核定時才填。依 mad-1，有 dosage 時 dose 或 rate 至少填一個。無法解析時不建立 dosage，原文改填 note。

已填 dose 或 rate 時，可在此保留來源劑量原文。

value 填劑量數值，unit 填單位文字，system 固定為 http://unitsofmeasure.org，code 填 UCUM 單位代碼。IV-tPA 以毫克記錄，code 必須填 mg（stroke-medadmin-2）。鎮靜藥與動脈內藥物要在院方已核定該藥的劑量單位，且來源劑量能可靠解析成數值與單位時才填 dose，例如 mg、ug（微克）或 [iU]（國際單位）；否則原文改填 note。

Describes 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 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.

The 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.

A 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 it's narrative along with other profiles, value sets, etc.

The 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.

A 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 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.

These 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

May 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 manageable, 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.

May 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 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

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.

Identifiers 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.

A protocol, guideline, orderset, or other definition that was adhered to in whole or in part by this event.

EVT 中給予的鎮靜藥，參照該次 EVT 主處置（code 為 evt）。動脈內藥物參照動脈內藥物治療處置（code 為 intra-arterial-drug-therapy）或 EVT 主處置。能確認屬於同一次 EVT 時才填。IV-tPA 不屬於 EVT 處置，不填。

來源明確記錄已給藥，填 completed。明確記錄未給藥，填 not-done；未給藥也要有預定給藥時間才建立，沒有時改存登錄表單。有給藥紀錄但無法確認是否完成，填 unknown。來源空白時不建立本資源。

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.

A code indicating why the administration was not performed.

A set of codes indicating the reason why the MedicationAdministration is negated.

Indicates where the medication is expected to be consumed or administered.

A coded concept describing where the medication administered is expected to occur.

只用 CodeableConcept 記錄。IV-tPA 品項未明時，coding 填 StrokeMedicationCS 的 iv-tpa-unspecified。鎮靜藥與動脈內藥物只有藥名時只填 text，原樣保留藥名。coding 與 text 至少填一個。

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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May 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 manageable, 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.

A reference to a code defined by a terminology system.

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.

Allows for alternative encodings within a code system, and translations to other code systems.

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

填 StrokeMedicationCS 的代碼。IV-tPA 品項未明時填 iv-tpa-unspecified。院方核定藥品主檔後，可另加院內或健保藥品代碼。

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.

Allows for alternative encodings within a code system, and translations to other code systems.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May 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 manageable, 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.

The identification of the code system that defines the meaning of the symbol in the code.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

鎮靜藥與動脈內藥物只有名稱時，原樣填入藥名。

Very often the text is the same as a displayName of one of the codings.

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.

The person or animal or group receiving the medication.

The visit, admission, or other contact between patient and health care provider during which the medication administration was performed.

Additional information (for example, patient height and weight) that supports the administration of the medication.

填實際給藥時間；未給藥填預定給藥時間。確認時區前只填日期（YYYY-MM-DD），時間原值用 StrokeEventTimeOnly 擴充附在此元素，並存入 StrokeRegistryResponse 的原始值題目；確認後把同一次給藥的日期與時間合併為 dateTime 並帶時區（例如 +08:00）。只有年月時填 YYYY-MM。只有時間沒有日期時，effectiveDateTime 不填值，改在其 extension 放 StrokeEventTimeOnly。日期與時間都沒有時不建立本資源。

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them Other type slices that contain no new information are not shown in this view

A 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.

unique id for the element within a resource (for internal references)

An Extension

Slicing Note: The rules on this element (including its children) apply to all the slices, but are not repeated in them

只用於 dateTime 型別元素；choice 元素只用 dateTime 分支，Period 用於 start 與 end。兩種用法：一、來源只有時間、沒有日期：原元素不填值，只在該元素的 extension 放入本 Extension，例如 Procedure._performedDateTime；此用法不適用 Observation.effective[x]，評估時間缺日期時改存登錄表單。二、來源有日期與時間但時區尚未確認：原元素只填日期（YYYY-MM-DD），並在該元素的 extension 放入本 Extension 保留來源時鐘時間。

The actual value

Indicates who or what performed the medication administration and how they were involved.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May 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 manageable, 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.

May 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 manageable, 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).

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.

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.

Distinguishes the type of involvement of the performer in the medication administration.

A code describing the role an individual played in administering the medication.

Indicates who or what performed the medication administration.

A code indicating why the medication was given.

A set of codes indicating the reason why the MedicationAdministration was made.

Condition 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.

The 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.

The device used in administering the medication to the patient. For example, a particular infusion pump.

劑量無法可靠解析成數值與單位，或該藥劑量單位未經院方核定時，把來源劑量原文填在 note.text，不建立 dosage。

能可靠解析出劑量（dose）或速率（rate），且單位經院方核定時才填。依 mad-1，有 dosage 時 dose 或 rate 至少填一個。無法解析時不建立 dosage，原文改填 note。

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May 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 manageable, 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.

May 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 manageable, 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).

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.

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.

已填 dose 或 rate 時，可在此保留來源劑量原文。

A 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 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.

A code specifying the route or physiological path of administration of a therapeutic agent into or onto the patient. For example, topical, intravenous, etc.

A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.

A 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.

value 填劑量數值，unit 填單位文字，system 固定為 http://unitsofmeasure.org，code 填 UCUM 單位代碼。IV-tPA 以毫克記錄，code 必須填 mg（stroke-medadmin-2）。鎮靜藥與動脈內藥物要在院方已核定該藥的劑量單位，且來源劑量能可靠解析成數值與單位時才填 dose，例如 mg、ug（微克）或 [iU]（國際單位）；否則原文改填 note。

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.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May 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 manageable, 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.

The value of the measured amount. The value includes an implicit precision in the presentation of the value.

The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).

Precision is handled implicitly in almost all cases of measurement.

Not allowed to be used in this context

How the Quantity should be understood and represented.

Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

A human-readable form of the unit.

There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

The identification of the system that provides the coded form of the unit.

Need to know the system that defines the coded form of the unit.

A computer processable form of the unit in some unit representation system.

The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.

Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

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.

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.

A 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.