Mô hình logic chuẩn cho Biên bản quyết toán, thanh toán chi phí khám bệnh, chữa bệnh BHYT theo quý (Mẫu số 06/BH), gồm định danh biên bản, đúng một quý, bên chi trả, cơ sở KCB, hợp đồng, bộ 55 chỉ tiêu hiện hành với hai cột trong quý/lũy kế, ý kiến hai bên và người ký xác nhận. LogicalModel là carrier dữ liệu của biểu mẫu; PaymentReconciliation tiếp tục mang semantics remittance/phân bổ khoản thanh toán bulk, còn tài liệu ký có thể render từ instance này và đóng gói bằng Composition/DocumentReference. Căn cứ: [TT 12/2026/TT-BTC] (ban hành 10/02/2026, hiệu lực 10/02/2026) — Giám định, thanh toán, quyết toán chi phí KCB BHYT; [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.

This logical model is the canonical data carrier for the quarterly BHYT healthcare-cost settlement and payment record (Form 06/BH). It contains the settlement identifiers, exactly one calendar quarter, payer, provider, contract, the current 55-indicator set with quarter and year-to-date columns, both parties' opinions, and attestations. PaymentReconciliation retains its FHIR remittance and bulk-payment allocation semantics; a signed document may be rendered from this model and packaged using Composition or DocumentReference.

Một hoặc nhiều định danh nghiệp vụ của biên bản quyết toán. One or more business identifiers for the quarterly settlement record.

Khoảng ngày của đúng một quý dương lịch. The date range of exactly one calendar quarter.

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 start of the period. The boundary is inclusive.

If the low element is missing, the meaning is that the low boundary is not known.

The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

Cơ quan bảo hiểm xã hội lập và xác nhận biên bản. Payer là Organization nền, không phải VNCoreOrganization dành cho cơ sở KCB. Organization.identifier nên dùng namespace mã đơn vị do BHXH quản lý hoặc namespace được hai bên thỏa thuận; không dùng mã CSKCB và không dùng sid/bhxh dành cho mã số BHXH cá nhân. The social-insurance authority that prepares and attests the settlement. The payer uses base Organization, not the healthcare-provider-focused VNCoreOrganization. Organization.identifier SHOULD use a BHXH-managed organization-unit namespace or a namespace agreed by the parties; it SHALL NOT use a healthcare-facility code or the personal social-insurance-number sid/bhxh.

Cơ sở khám bệnh, chữa bệnh ký hợp đồng BHYT. The contracted healthcare provider.

Định danh hợp đồng KCB BHYT giữa payer và provider. Identifier of the BHYT healthcare contract between payer and provider.

Ngày ký hoặc ngày xác lập hợp đồng KCB BHYT được viện dẫn trên biên bản. Date on which the referenced BHYT healthcare contract was signed or established.

Tài liệu điện tử hỗ trợ việc đối chiếu hoặc render biên bản, ví dụ bản hợp đồng, phụ lục hoặc bảng tổng hợp có liên quan. Electronic documents supporting reconciliation or rendering of the report, such as the referenced contract, an addendum, or a related summary.

Số tài khoản chi trả của cơ quan BHXH ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Disbursing bank-account number of the BHXH payer shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ quan BHXH mở tài khoản chi trả. Name of the bank or branch holding the BHXH payer's disbursing account.

Số tài khoản nhận thanh toán của tổ chức cung cấp dịch vụ ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Receiving bank-account number of the provider organization shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ sở KCB mở tài khoản nhận thanh toán; đây là dữ liệu của tổ chức. Name of the bank or branch holding the provider's receiving account; this is organizational data.

Một dòng chỉ tiêu Mẫu 06/BH. Bộ mã hiện hành gồm 55 mã, mỗi mã đúng một lần. One Form 06/BH indicator row; the current set contains 55 unique codes.

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.

Mã số 1..55 theo Mẫu 06/BH. Indicator number 1..55 from Form 06/BH.

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.

Giá trị của chỉ tiêu phát sinh trong quý, làm tròn đến đồng. The indicator value for the quarter, rounded to whole VND.

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.

Numerical value (with implicit precision).

Monetary values have their own rules for handling precision (refer to standard accounting text books).

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

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Giá trị lũy kế của chỉ tiêu từ đầu năm đến hết quý, làm tròn đến đồng. Mã 1, 2, 3, 10 không ghi lũy kế; mã 30 và 43 không ghi ở cả hai cột. Các ô không áp dụng vẫn giữ Money nhưng bỏ value và gắn data-absent-reason not-applicable. The cumulative indicator value from the beginning of the year through the quarter, rounded to whole VND. Indicators 1, 2, 3, and 10 do not populate year-to-date values; indicators 30 and 43 populate neither column. Retain Money for each non-applicable cell, omit value, and add data-absent-reason not-applicable.

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.

Numerical value (with implicit precision).

Monetary values have their own rules for handling precision (refer to standard accounting text books).

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

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Ý kiến hoặc bảo lưu của cơ quan BHXH trên biên bản. The payer's comments or reservations on the settlement.

Ý kiến hoặc bảo lưu của cơ sở KCB trên biên bản. The provider's comments or reservations on the settlement.

Người đại diện hai bên ký xác nhận; phải có ít nhất một người ký phía cơ sở KCB và một người xác minh phía cơ quan BHXH. Representatives who attest the record; at least one healthcare-provider signer and one BHXH payer verifier are required.

Hai nhóm logic providerSigner 1..* và payerSigner 1..* được phân biệt bằng đúng một role AUT hoặc VRF trên mỗi attester và thực thi bằng invariant vn-quarterly-settlement-provider-payer-signers. SUSHI không hỗ trợ quy tắc contains trực tiếp trên LogicalModel; workaround này thực thi cardinality và phân biệt role nhưng không tạo sliceName trong StructureDefinition sinh ra. The logical signer groups use exactly one AUT or VRF discriminator per attester and are enforced by an invariant because SUSHI does not permit contains rules on a LogicalModel; this enforces cardinality and role separation without emitting slice names.

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.

PractitionerRole nền xác định người hoặc vai trò ký, tổ chức và vai trò nghiệp vụ; dùng nền để phía cơ quan BHXH không bị ép vào profile vai trò hành nghề tại cơ sở KCB. Base PractitionerRole identifying the signer or signing role, organization, and business role; the base type avoids forcing a BHXH payer representative into a healthcare-provider practice-role profile.

Mã phân biệt phía ký: HL7 v3 ParticipationType AUT cho cơ sở KCB và VRF cho cơ quan BHXH. Chức vụ cụ thể trên biểu mẫu có thể ghi thêm trong text. Side discriminator: HL7 v3 ParticipationType AUT for the provider and VRF for the BHXH payer. A form-specific office or title may additionally be conveyed in text.

Thời điểm người đại diện ký hoặc xác nhận điện tử. Time at which the representative signed or electronically attested.

Mô hình logic chuẩn cho Biên bản quyết toán, thanh toán chi phí khám bệnh, chữa bệnh BHYT theo quý (Mẫu số 06/BH), gồm định danh biên bản, đúng một quý, bên chi trả, cơ sở KCB, hợp đồng, bộ 55 chỉ tiêu hiện hành với hai cột trong quý/lũy kế, ý kiến hai bên và người ký xác nhận. LogicalModel là carrier dữ liệu của biểu mẫu; PaymentReconciliation tiếp tục mang semantics remittance/phân bổ khoản thanh toán bulk, còn tài liệu ký có thể render từ instance này và đóng gói bằng Composition/DocumentReference. Căn cứ: [TT 12/2026/TT-BTC] (ban hành 10/02/2026, hiệu lực 10/02/2026) — Giám định, thanh toán, quyết toán chi phí KCB BHYT; [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.

This logical model is the canonical data carrier for the quarterly BHYT healthcare-cost settlement and payment record (Form 06/BH). It contains the settlement identifiers, exactly one calendar quarter, payer, provider, contract, the current 55-indicator set with quarter and year-to-date columns, both parties' opinions, and attestations. PaymentReconciliation retains its FHIR remittance and bulk-payment allocation semantics; a signed document may be rendered from this model and packaged using Composition or DocumentReference.

Một hoặc nhiều định danh nghiệp vụ của biên bản quyết toán. One or more business identifiers for the quarterly settlement record.

Khoảng ngày của đúng một quý dương lịch. The date range of exactly one calendar quarter.

Cơ quan bảo hiểm xã hội lập và xác nhận biên bản. Payer là Organization nền, không phải VNCoreOrganization dành cho cơ sở KCB. Organization.identifier nên dùng namespace mã đơn vị do BHXH quản lý hoặc namespace được hai bên thỏa thuận; không dùng mã CSKCB và không dùng sid/bhxh dành cho mã số BHXH cá nhân. The social-insurance authority that prepares and attests the settlement. The payer uses base Organization, not the healthcare-provider-focused VNCoreOrganization. Organization.identifier SHOULD use a BHXH-managed organization-unit namespace or a namespace agreed by the parties; it SHALL NOT use a healthcare-facility code or the personal social-insurance-number sid/bhxh.

Cơ sở khám bệnh, chữa bệnh ký hợp đồng BHYT. The contracted healthcare provider.

Định danh hợp đồng KCB BHYT giữa payer và provider. Identifier of the BHYT healthcare contract between payer and provider.

Ngày ký hoặc ngày xác lập hợp đồng KCB BHYT được viện dẫn trên biên bản. Date on which the referenced BHYT healthcare contract was signed or established.

Tài liệu điện tử hỗ trợ việc đối chiếu hoặc render biên bản, ví dụ bản hợp đồng, phụ lục hoặc bảng tổng hợp có liên quan. Electronic documents supporting reconciliation or rendering of the report, such as the referenced contract, an addendum, or a related summary.

Số tài khoản chi trả của cơ quan BHXH ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Disbursing bank-account number of the BHXH payer shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ quan BHXH mở tài khoản chi trả. Name of the bank or branch holding the BHXH payer's disbursing account.

Số tài khoản nhận thanh toán của tổ chức cung cấp dịch vụ ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Receiving bank-account number of the provider organization shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ sở KCB mở tài khoản nhận thanh toán; đây là dữ liệu của tổ chức. Name of the bank or branch holding the provider's receiving account; this is organizational data.

Một dòng chỉ tiêu Mẫu 06/BH. Bộ mã hiện hành gồm 55 mã, mỗi mã đúng một lần. One Form 06/BH indicator row; the current set contains 55 unique codes.

Mã số 1..55 theo Mẫu 06/BH. Indicator number 1..55 from Form 06/BH.

Giá trị của chỉ tiêu phát sinh trong quý, làm tròn đến đồng. The indicator value for the quarter, rounded to whole VND.

Giá trị lũy kế của chỉ tiêu từ đầu năm đến hết quý, làm tròn đến đồng. Mã 1, 2, 3, 10 không ghi lũy kế; mã 30 và 43 không ghi ở cả hai cột. Các ô không áp dụng vẫn giữ Money nhưng bỏ value và gắn data-absent-reason not-applicable. The cumulative indicator value from the beginning of the year through the quarter, rounded to whole VND. Indicators 1, 2, 3, and 10 do not populate year-to-date values; indicators 30 and 43 populate neither column. Retain Money for each non-applicable cell, omit value, and add data-absent-reason not-applicable.

Ý kiến hoặc bảo lưu của cơ quan BHXH trên biên bản. The payer's comments or reservations on the settlement.

Ý kiến hoặc bảo lưu của cơ sở KCB trên biên bản. The provider's comments or reservations on the settlement.

Người đại diện hai bên ký xác nhận; phải có ít nhất một người ký phía cơ sở KCB và một người xác minh phía cơ quan BHXH. Representatives who attest the record; at least one healthcare-provider signer and one BHXH payer verifier are required.

Hai nhóm logic providerSigner 1..* và payerSigner 1..* được phân biệt bằng đúng một role AUT hoặc VRF trên mỗi attester và thực thi bằng invariant vn-quarterly-settlement-provider-payer-signers. SUSHI không hỗ trợ quy tắc contains trực tiếp trên LogicalModel; workaround này thực thi cardinality và phân biệt role nhưng không tạo sliceName trong StructureDefinition sinh ra. The logical signer groups use exactly one AUT or VRF discriminator per attester and are enforced by an invariant because SUSHI does not permit contains rules on a LogicalModel; this enforces cardinality and role separation without emitting slice names.

PractitionerRole nền xác định người hoặc vai trò ký, tổ chức và vai trò nghiệp vụ; dùng nền để phía cơ quan BHXH không bị ép vào profile vai trò hành nghề tại cơ sở KCB. Base PractitionerRole identifying the signer or signing role, organization, and business role; the base type avoids forcing a BHXH payer representative into a healthcare-provider practice-role profile.

Mã phân biệt phía ký: HL7 v3 ParticipationType AUT cho cơ sở KCB và VRF cho cơ quan BHXH. Chức vụ cụ thể trên biểu mẫu có thể ghi thêm trong text. Side discriminator: HL7 v3 ParticipationType AUT for the provider and VRF for the BHXH payer. A form-specific office or title may additionally be conveyed in text.

Thời điểm người đại diện ký hoặc xác nhận điện tử. Time at which the representative signed or electronically attested.

Mô hình logic chuẩn cho Biên bản quyết toán, thanh toán chi phí khám bệnh, chữa bệnh BHYT theo quý (Mẫu số 06/BH), gồm định danh biên bản, đúng một quý, bên chi trả, cơ sở KCB, hợp đồng, bộ 55 chỉ tiêu hiện hành với hai cột trong quý/lũy kế, ý kiến hai bên và người ký xác nhận. LogicalModel là carrier dữ liệu của biểu mẫu; PaymentReconciliation tiếp tục mang semantics remittance/phân bổ khoản thanh toán bulk, còn tài liệu ký có thể render từ instance này và đóng gói bằng Composition/DocumentReference. Căn cứ: [TT 12/2026/TT-BTC] (ban hành 10/02/2026, hiệu lực 10/02/2026) — Giám định, thanh toán, quyết toán chi phí KCB BHYT; [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.

This logical model is the canonical data carrier for the quarterly BHYT healthcare-cost settlement and payment record (Form 06/BH). It contains the settlement identifiers, exactly one calendar quarter, payer, provider, contract, the current 55-indicator set with quarter and year-to-date columns, both parties' opinions, and attestations. PaymentReconciliation retains its FHIR remittance and bulk-payment allocation semantics; a signed document may be rendered from this model and packaged using Composition or DocumentReference.

Một hoặc nhiều định danh nghiệp vụ của biên bản quyết toán. One or more business identifiers for the quarterly settlement record.

Khoảng ngày của đúng một quý dương lịch. The date range of exactly one calendar quarter.

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 start of the period. The boundary is inclusive.

If the low element is missing, the meaning is that the low boundary is not known.

The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

Cơ quan bảo hiểm xã hội lập và xác nhận biên bản. Payer là Organization nền, không phải VNCoreOrganization dành cho cơ sở KCB. Organization.identifier nên dùng namespace mã đơn vị do BHXH quản lý hoặc namespace được hai bên thỏa thuận; không dùng mã CSKCB và không dùng sid/bhxh dành cho mã số BHXH cá nhân. The social-insurance authority that prepares and attests the settlement. The payer uses base Organization, not the healthcare-provider-focused VNCoreOrganization. Organization.identifier SHOULD use a BHXH-managed organization-unit namespace or a namespace agreed by the parties; it SHALL NOT use a healthcare-facility code or the personal social-insurance-number sid/bhxh.

Cơ sở khám bệnh, chữa bệnh ký hợp đồng BHYT. The contracted healthcare provider.

Định danh hợp đồng KCB BHYT giữa payer và provider. Identifier of the BHYT healthcare contract between payer and provider.

Ngày ký hoặc ngày xác lập hợp đồng KCB BHYT được viện dẫn trên biên bản. Date on which the referenced BHYT healthcare contract was signed or established.

Tài liệu điện tử hỗ trợ việc đối chiếu hoặc render biên bản, ví dụ bản hợp đồng, phụ lục hoặc bảng tổng hợp có liên quan. Electronic documents supporting reconciliation or rendering of the report, such as the referenced contract, an addendum, or a related summary.

Số tài khoản chi trả của cơ quan BHXH ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Disbursing bank-account number of the BHXH payer shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ quan BHXH mở tài khoản chi trả. Name of the bank or branch holding the BHXH payer's disbursing account.

Số tài khoản nhận thanh toán của tổ chức cung cấp dịch vụ ghi trên biểu mẫu; đây là dữ liệu tài chính của tổ chức, không phải tài khoản cá nhân. Receiving bank-account number of the provider organization shown on the form; this is organizational financial data, not a personal account.

Tên ngân hàng hoặc chi nhánh nơi cơ sở KCB mở tài khoản nhận thanh toán; đây là dữ liệu của tổ chức. Name of the bank or branch holding the provider's receiving account; this is organizational data.

Một dòng chỉ tiêu Mẫu 06/BH. Bộ mã hiện hành gồm 55 mã, mỗi mã đúng một lần. One Form 06/BH indicator row; the current set contains 55 unique codes.

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.

Mã số 1..55 theo Mẫu 06/BH. Indicator number 1..55 from Form 06/BH.

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.

Giá trị của chỉ tiêu phát sinh trong quý, làm tròn đến đồng. The indicator value for the quarter, rounded to whole VND.

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.

Numerical value (with implicit precision).

Monetary values have their own rules for handling precision (refer to standard accounting text books).

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

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Giá trị lũy kế của chỉ tiêu từ đầu năm đến hết quý, làm tròn đến đồng. Mã 1, 2, 3, 10 không ghi lũy kế; mã 30 và 43 không ghi ở cả hai cột. Các ô không áp dụng vẫn giữ Money nhưng bỏ value và gắn data-absent-reason not-applicable. The cumulative indicator value from the beginning of the year through the quarter, rounded to whole VND. Indicators 1, 2, 3, and 10 do not populate year-to-date values; indicators 30 and 43 populate neither column. Retain Money for each non-applicable cell, omit value, and add data-absent-reason not-applicable.

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.

Numerical value (with implicit precision).

Monetary values have their own rules for handling precision (refer to standard accounting text books).

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

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Ý kiến hoặc bảo lưu của cơ quan BHXH trên biên bản. The payer's comments or reservations on the settlement.

Ý kiến hoặc bảo lưu của cơ sở KCB trên biên bản. The provider's comments or reservations on the settlement.

Người đại diện hai bên ký xác nhận; phải có ít nhất một người ký phía cơ sở KCB và một người xác minh phía cơ quan BHXH. Representatives who attest the record; at least one healthcare-provider signer and one BHXH payer verifier are required.

Hai nhóm logic providerSigner 1..* và payerSigner 1..* được phân biệt bằng đúng một role AUT hoặc VRF trên mỗi attester và thực thi bằng invariant vn-quarterly-settlement-provider-payer-signers. SUSHI không hỗ trợ quy tắc contains trực tiếp trên LogicalModel; workaround này thực thi cardinality và phân biệt role nhưng không tạo sliceName trong StructureDefinition sinh ra. The logical signer groups use exactly one AUT or VRF discriminator per attester and are enforced by an invariant because SUSHI does not permit contains rules on a LogicalModel; this enforces cardinality and role separation without emitting slice names.

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.

PractitionerRole nền xác định người hoặc vai trò ký, tổ chức và vai trò nghiệp vụ; dùng nền để phía cơ quan BHXH không bị ép vào profile vai trò hành nghề tại cơ sở KCB. Base PractitionerRole identifying the signer or signing role, organization, and business role; the base type avoids forcing a BHXH payer representative into a healthcare-provider practice-role profile.

Mã phân biệt phía ký: HL7 v3 ParticipationType AUT cho cơ sở KCB và VRF cho cơ quan BHXH. Chức vụ cụ thể trên biểu mẫu có thể ghi thêm trong text. Side discriminator: HL7 v3 ParticipationType AUT for the provider and VRF for the BHXH payer. A form-specific office or title may additionally be conveyed in text.

Thời điểm người đại diện ký hoặc xác nhận điện tử. Time at which the representative signed or electronically attested.