An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.

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.

Extension tái sử dụng cho thông tin chi phí BHYT trên từng item (thuốc/DVKT/VTYT). Bao gồm: phạm vi BHYT (PHAM_VI), tỷ lệ thanh toán BHYT (TYLE_TT/TYLE_TT_BH), mức hưởng (MUC_HUONG), mức trần thanh toán BHYT (T_TRANTT), tỷ lệ thanh toán dịch vụ (TYLE_TT_DV), đơn giá BHYT (DON_GIA_BH) và thành tiền BHYT (THANH_TIEN_BH). Dùng trên: MedicationRequest, MedicationAdministration, Procedure, Claim.item, Claim.item.detail, ExplanationOfBenefit.item, ExplanationOfBenefit.item.detail, ServiceRequest và MedicationDispense khi các resource đó đang đóng vai trò nguồn dữ liệu cho dòng chi phí. Với thiết bị/vật tư, ưu tiên đặt trên Claim.item hoặc item.detail; không dùng trên DeviceUseStatement vì DeviceUseStatement là ghi nhận sử dụng lâm sàng. Theo QĐ 697/QĐ-BYT (các dòng hướng dẫn khoảng 389 và 407), component trong gói TBYT mang lossless các cột 5/6/8/9; chỉ các cột 10–13 được tính ở item tổng gói. Mapping XML 3176: PHAM_VI, TYLE_TT, MUC_HUONG; DON_GIA_BH (Bảng 3 STT 15), TYLE_TT_DV (Bảng 3 STT 17), THANH_TIEN_BH (Bảng 2 STT 21, Bảng 3 STT 20), T_TRANTT (Bảng 3 STT 21). Nguồn thiết kế: OHP Data Processor (medication-pham-vi, medication-payment-ratio, medication-benefit-level). Căn cứ: [QĐ 3176/QĐ-BYT] (ban hành 29/10/2024, hiệu lực 29/10/2024) — Chuẩn dữ liệu đầu ra KCB phục vụ BHXH; [NĐ 188/2025/NĐ-CP] (ban hành 01/07/2025, hiệu lực 15/08/2025) — Hướng dẫn thi hành Luật BHYT. English summary: Reusable line-level BHYT cost information for medication, procedure, service, Claim, EOB, and medication-administration data. On a medical-device package, each Claim/EOB item detail carries columns 5/6/8/9 losslessly, while columns 10–13 remain on the package item. insuranceLineAmount represents the insurance-eligible line amount (THANH_TIEN_BH/column 9), not the final BHYT fund allocation; on an EOB it aligns with adjudication eligible, while the fund allocation uses adjudication benefit.

Số đăng ký lưu hành thuốc (Visa) do Cục Quản lý Dược — Bộ Y tế cấp. Trường SO_DANG_KY theo QĐ 3176/QĐ-BYT (29/10/2024). Bắt buộc khi gửi dữ liệu chi phí thuốc cho BHXH. Căn cứ bổ sung:

• Luật 44/2024/QH15 — 21/11/2024 — sửa đổi Luật Dược, hiệu lực 01/7/2025
• Luật Dược 2016 — đăng ký lưu hành thuốc
• NĐ 102/2025/NĐ-CP — 13/5/2025 — dữ liệu thuốc trong CSDL quốc gia về y tế.

Ngày y lệnh chỉ định dịch vụ/thuốc (NGAY_YL). Mapping XML 3176: NGAY_YL. Nguồn thiết kế: OHP Data Processor (procedure-order-date).

Nguồn chi trả cho dòng chi phí KCB, đặc biệt dùng cho XML2 thuốc (NGUON_CTRA) theo QĐ 3176/QĐ-BYT. Biểu diễn nguồn chi trả ở mức item thay vì gán vào Coverage.type hoặc payment method tổng thể. Nguồn thiết kế: QĐ 3176/QĐ-BYT và terminology VNPaymentSourceCS/VS.

Thông tin thầu của dòng thuốc/vật tư/thiết bị trong dữ liệu KCB/BHYT, đặc biệt dùng cho XML2/XML3 trường TT_THAU theo QĐ 130/QĐ-BYT và QĐ 3176/QĐ-BYT. Đây là chuỗi nghiệp vụ phục vụ thanh toán/gateway, không phải procurement package đầy đủ và không thay thế hồ sơ đấu thầu riêng.

Phương pháp chế biến vị thuốc, dược liệu hoặc thuốc y học cổ truyền — mang trường MA_PP_CHEBIEN của dữ liệu BHYT/KCB. Từ bản 0.9.0 đã có danh mục mã chính thức: vn-tcm-processing-method-vs (Phụ lục 3 QĐ 824/QĐ-BYT, 40 mã). Ưu tiên ghi valueCodeableConcept theo danh mục này. Vẫn cho phép valueString vì hai lý do thực tế: TT 14/2024/TT-BYT bổ sung ba phương pháp phức chế (chưng, tôi, rán dầu) mà bộ mã dùng chung chưa cấp mã riêng, và Điều 4 khoản 2 TT 14/2024/TT-BYT cho phép cơ sở tự xây dựng phương pháp chế biến khi phương pháp đó chưa được quy định.

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.

Định danh của riêng dòng thuốc này, thường là mã nội bộ do phần mềm cơ sở KCB sinh. Mã đơn thuốc quốc gia đặt ở groupIdentifier.

This is a business identifier, not a resource identifier.

Chỉ trạng thái của đơn ĐÃ PHÁT HÀNH; bản nháp chưa sinh mã đơn quốc gia không thuộc phạm vi profile này.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription.

Whether the request is a proposal, plan, or an original order.

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

The kind of medication order.

Phân loại bối cảnh kê đơn. Đơn thuốc ngoại trú và đơn thuốc điện tử tham chiếu TT 26/2025/TT-BYT; đơn nội trú/cấp cứu gắn với bệnh án điện tử theo TT 13/2025/TT-BYT.

The category can be used to include where the medication is expected to be consumed or other types of requests.

A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.

If true indicates that the provider is asking for the medication request not to occur.

If do not perform is not specified, the request is a positive request e.g. "do perform".

Thuốc được kê đơn. Ưu tiên mã hóa bằng ATC (WHO) hoặc SNOMED CT. Nếu chưa có mã, sử dụng text (tên thương mại hoặc tên hoạt chất). Với bài thuốc YHCT: dùng mã từ VNYHCTPrescriptionCS (522 bài thuốc theo QĐ 3080/QĐ-BYT, PL VI). Lưu ý: VN chưa có bộ mã thuốc quốc gia dạng FHIR — sẽ bổ sung khi BYT/Dược điển VN publish.

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 or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.

A coded concept identifying substance or product that can be ordered.

A link to a resource representing the person or set of individuals to whom the medication will be given.

The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified.

The date (and perhaps time) when the prescription was initially written or authored on.

The individual, organization, or device that initiated the request and has responsibility for its activation.

Mã đơn thuốc điện tử do Hệ thống đơn thuốc quốc gia (donthuocquocgia.vn) sinh, theo Phụ lục I TT 26/2025/TT-BYT. Mọi MedicationRequest thuộc cùng một đơn mang cùng giá trị này, kể cả đơn chỉ có một thuốc — nhờ đó nhà thuốc và Hệ thống đơn thuốc quốc gia gom đúng đơn khi bán và báo cáo. Ràng buộc định dạng đặt ở các profile dẫn xuất (đơn ngoại trú, đơn y học cổ truyền) vì cấu trúc hậu tố khác nhau theo loại đơn.

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Indicates how the medication is to be used by the patient.

There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.

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.

Free text dosage instructions e.g. SIG.

Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text.

When medication should be administered.

This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.

The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.

How drug should enter body.

A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.

The amount of medication administered.

Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.

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.

The amount that is to be dispensed for one fill.

Chỉ trạng thái của đơn ĐÃ PHÁT HÀNH; bản nháp chưa sinh mã đơn quốc gia không thuộc phạm vi profile này.

An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns.

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.

An Extension

Extension tái sử dụng cho thông tin chi phí BHYT trên từng item (thuốc/DVKT/VTYT). Bao gồm: phạm vi BHYT (PHAM_VI), tỷ lệ thanh toán BHYT (TYLE_TT/TYLE_TT_BH), mức hưởng (MUC_HUONG), mức trần thanh toán BHYT (T_TRANTT), tỷ lệ thanh toán dịch vụ (TYLE_TT_DV), đơn giá BHYT (DON_GIA_BH) và thành tiền BHYT (THANH_TIEN_BH). Dùng trên: MedicationRequest, MedicationAdministration, Procedure, Claim.item, Claim.item.detail, ExplanationOfBenefit.item, ExplanationOfBenefit.item.detail, ServiceRequest và MedicationDispense khi các resource đó đang đóng vai trò nguồn dữ liệu cho dòng chi phí. Với thiết bị/vật tư, ưu tiên đặt trên Claim.item hoặc item.detail; không dùng trên DeviceUseStatement vì DeviceUseStatement là ghi nhận sử dụng lâm sàng. Theo QĐ 697/QĐ-BYT (các dòng hướng dẫn khoảng 389 và 407), component trong gói TBYT mang lossless các cột 5/6/8/9; chỉ các cột 10–13 được tính ở item tổng gói. Mapping XML 3176: PHAM_VI, TYLE_TT, MUC_HUONG; DON_GIA_BH (Bảng 3 STT 15), TYLE_TT_DV (Bảng 3 STT 17), THANH_TIEN_BH (Bảng 2 STT 21, Bảng 3 STT 20), T_TRANTT (Bảng 3 STT 21). Nguồn thiết kế: OHP Data Processor (medication-pham-vi, medication-payment-ratio, medication-benefit-level). Căn cứ: [QĐ 3176/QĐ-BYT] (ban hành 29/10/2024, hiệu lực 29/10/2024) — Chuẩn dữ liệu đầu ra KCB phục vụ BHXH; [NĐ 188/2025/NĐ-CP] (ban hành 01/07/2025, hiệu lực 15/08/2025) — Hướng dẫn thi hành Luật BHYT. English summary: Reusable line-level BHYT cost information for medication, procedure, service, Claim, EOB, and medication-administration data. On a medical-device package, each Claim/EOB item detail carries columns 5/6/8/9 losslessly, while columns 10–13 remain on the package item. insuranceLineAmount represents the insurance-eligible line amount (THANH_TIEN_BH/column 9), not the final BHYT fund allocation; on an EOB it aligns with adjudication eligible, while the fund allocation uses adjudication benefit.

Số đăng ký lưu hành thuốc (Visa) do Cục Quản lý Dược — Bộ Y tế cấp. Trường SO_DANG_KY theo QĐ 3176/QĐ-BYT (29/10/2024). Bắt buộc khi gửi dữ liệu chi phí thuốc cho BHXH. Căn cứ bổ sung:

• Luật 44/2024/QH15 — 21/11/2024 — sửa đổi Luật Dược, hiệu lực 01/7/2025
• Luật Dược 2016 — đăng ký lưu hành thuốc
• NĐ 102/2025/NĐ-CP — 13/5/2025 — dữ liệu thuốc trong CSDL quốc gia về y tế.

Ngày y lệnh chỉ định dịch vụ/thuốc (NGAY_YL). Mapping XML 3176: NGAY_YL. Nguồn thiết kế: OHP Data Processor (procedure-order-date).

Nguồn chi trả cho dòng chi phí KCB, đặc biệt dùng cho XML2 thuốc (NGUON_CTRA) theo QĐ 3176/QĐ-BYT. Biểu diễn nguồn chi trả ở mức item thay vì gán vào Coverage.type hoặc payment method tổng thể. Nguồn thiết kế: QĐ 3176/QĐ-BYT và terminology VNPaymentSourceCS/VS.

Thông tin thầu của dòng thuốc/vật tư/thiết bị trong dữ liệu KCB/BHYT, đặc biệt dùng cho XML2/XML3 trường TT_THAU theo QĐ 130/QĐ-BYT và QĐ 3176/QĐ-BYT. Đây là chuỗi nghiệp vụ phục vụ thanh toán/gateway, không phải procurement package đầy đủ và không thay thế hồ sơ đấu thầu riêng.

Phương pháp chế biến vị thuốc, dược liệu hoặc thuốc y học cổ truyền — mang trường MA_PP_CHEBIEN của dữ liệu BHYT/KCB. Từ bản 0.9.0 đã có danh mục mã chính thức: vn-tcm-processing-method-vs (Phụ lục 3 QĐ 824/QĐ-BYT, 40 mã). Ưu tiên ghi valueCodeableConcept theo danh mục này. Vẫn cho phép valueString vì hai lý do thực tế: TT 14/2024/TT-BYT bổ sung ba phương pháp phức chế (chưng, tôi, rán dầu) mà bộ mã dùng chung chưa cấp mã riêng, và Điều 4 khoản 2 TT 14/2024/TT-BYT cho phép cơ sở tự xây dựng phương pháp chế biến khi phương pháp đó chưa được quy định.

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.

Định danh của riêng dòng thuốc này, thường là mã nội bộ do phần mềm cơ sở KCB sinh. Mã đơn thuốc quốc gia đặt ở groupIdentifier.

This is a business identifier, not a resource identifier.

Chỉ trạng thái của đơn ĐÃ PHÁT HÀNH; bản nháp chưa sinh mã đơn quốc gia không thuộc phạm vi profile này.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription.

Captures the reason for the current state of the MedicationRequest.

This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.

Identifies the reasons for a given status.

Whether the request is a proposal, plan, or an original order.

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

The kind of medication order.

Phân loại bối cảnh kê đơn. Đơn thuốc ngoại trú và đơn thuốc điện tử tham chiếu TT 26/2025/TT-BYT; đơn nội trú/cấp cứu gắn với bệnh án điện tử theo TT 13/2025/TT-BYT.

The category can be used to include where the medication is expected to be consumed or other types of requests.

A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.

Indicates how quickly the Medication Request should be addressed with respect to other requests.

Identifies the level of importance to be assigned to actioning the request.

If true indicates that the provider is asking for the medication request not to occur.

If do not perform is not specified, the request is a positive request e.g. "do perform".

Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.

Thuốc được kê đơn. Ưu tiên mã hóa bằng ATC (WHO) hoặc SNOMED CT. Nếu chưa có mã, sử dụng text (tên thương mại hoặc tên hoạt chất). Với bài thuốc YHCT: dùng mã từ VNYHCTPrescriptionCS (522 bài thuốc theo QĐ 3080/QĐ-BYT, PL VI). Lưu ý: VN chưa có bộ mã thuốc quốc gia dạng FHIR — sẽ bổ sung khi BYT/Dược điển VN publish.

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 or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.

A coded concept identifying substance or product that can be ordered.

A link to a resource representing the person or set of individuals to whom the medication will be given.

The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified.

The Encounter during which this [x] was created or to which the creation of this record is tightly associated.

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension.

Include additional information (for example, patient height and weight) that supports the ordering of the medication.

The date (and perhaps time) when the prescription was initially written or authored on.

The individual, organization, or device that initiated the request and has responsibility for its activation.

The specified desired performer of the medication treatment (e.g. the performer of the medication administration).

Indicates the type of performer of the administration of the medication.

If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available.

Identifies the type of individual that is desired to administer the medication.

The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.

The reason or the indication for ordering or not ordering the medication.

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.

Condition or observation that supports why the medication was ordered.

This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode.

The URL pointing to a protocol, guideline, orderset, or other definition that is adhered to in whole or in part by this MedicationRequest.

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this MedicationRequest.

A plan or request that is fulfilled in whole or in part by this medication request.

Mã đơn thuốc điện tử do Hệ thống đơn thuốc quốc gia (donthuocquocgia.vn) sinh, theo Phụ lục I TT 26/2025/TT-BYT. Mọi MedicationRequest thuộc cùng một đơn mang cùng giá trị này, kể cả đơn chỉ có một thuốc — nhờ đó nhà thuốc và Hệ thống đơn thuốc quốc gia gom đúng đơn khi bán và báo cáo. Ràng buộc định dạng đặt ở các profile dẫn xuất (đơn ngoại trú, đơn y học cổ truyền) vì cấu trúc hậu tố khác nhau theo loại đơn.

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

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 purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

The description of the overall patte3rn of the administration of the medication to the patient.

This attribute should not be confused with the protocol of the medication.

Identifies the overall pattern of medication administratio.

Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.

Extra information about the prescription that could not be conveyed by the other attributes.

Indicates how the medication is to be used by the patient.

There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.

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.

Indicates the order in which the dosage instructions should be applied or interpreted.

If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential.

Free text dosage instructions e.g. SIG.

Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text.

Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps").

Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text.

A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".

Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded.

Instructions in terms that are understood by the patient or consumer.

When medication should be administered.

This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.

The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.

Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept).

Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed".

A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.

Body site to administer to.

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 coded specification of the anatomic site where the medication first enters the body.

How drug should enter body.

A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.

Technique for administering medication.

Terminologies used often pre-coordinate this term with the route and or form of administration.

A coded concept describing the technique by which the medicine is administered.

A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV.

The amount of medication 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.

The kind of dose or rate specified, for example, ordered or calculated.

The kind of dose or rate specified.

If the type is not populated, assume to be "ordered".

Amount of medication per dose.

Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.

The amount of therapeutic or other substance given at one administration event.

Amount of medication per unit of time.

It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate.

It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.

Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.

Upper limit on medication per unit of time.

This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".

The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours.

Upper limit on medication per administration.

This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.

The maximum total quantity of a therapeutic substance that may be administered to a subject per administration.

Upper limit on medication per lifetime of the patient.

The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject.

Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.

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.

Indicates the quantity or duration for the first dispense of the medication.

If populating this element, either the quantity or the duration must be included.

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.

The amount or quantity to provide as part of the first dispense.

The length of time that the first dispense is expected to last.

The minimum period of time that must occur between dispenses of the medication.

This indicates the validity period of a prescription (stale dating the Prescription).

It reflects the prescribers' perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.

Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription.

An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense.

If displaying "number of authorized fills", add 1 to this number.

The amount that is to be dispensed for one fill.

Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.

In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued, e.g. 90 days supply of medication (based on an ordered dosage). When possible, it is always better to specify quantity, as this tends to be more precise. expectedSupplyDuration will always be an estimate that can be influenced by external factors.

Indicates the intended dispensing Organization specified by the prescriber.

Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done.

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.

True if the prescriber allows a different drug to be dispensed from what was prescribed.

This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.

Identifies the type of substitution allowed.

Indicates the reason for the substitution, or why substitution must or must not be performed.

A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.

A link to a resource representing an earlier order related order or prescription.

Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, duplicate therapy, dosage alert etc.

This element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.

Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.

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