Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.

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.

An Extension

Mỗi phân đoạn là một thẻ BHYT trong một khoảng thời gian với một mức hưởng. Người không có thẻ vẫn có ít nhất một phân đoạn (thường là một; profile để segment 1..* nên không chặn trường hợp bảng kê tách nhiều phân đoạn), nhưng phân đoạn không có coverage thì không được mang benefitLevel.

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.

Identifier of this Invoice, often used for reference in correspondence about this invoice or for tracking of payments.

Allows Identification of this Invoice instance.

Mã liên kết hồ sơ khám bệnh, chữa bệnh theo QĐ 3176/QĐ-BYT. Bắt buộc và duy nhất một lát: đây là giá trị mà VNCoreCostStatementComposition.identifier phải trùng, và là khoá nối sang các VNCoreClaim của cùng đợt.

HAI VAI của khoá này, cần phân biệt khi triển khai: với hồ sơ có BHYT, giá trị chính là MA_LK được nộp cho cơ quan bảo hiểm theo QĐ 3176/QĐ-BYT. Với người bệnh KHÔNG có BHYT, bảng kê vẫn bắt buộc lát này nhưng giá trị chỉ đóng vai khoá nối nội bộ của cơ sở giữa bảng kê, bản ký và các hồ sơ cùng đợt — nó sẽ không bao giờ được nộp cho cơ quan bảo hiểm. Cơ sở tự sinh giá trị theo quy tắc của mình; ví dụ ExampleCostStatementUninsured dùng tiền tố LK-UNINSURED-.

Allows Identification of this Invoice instance.

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.

The current state of the Invoice.

Codes identifying the lifecycle stage of an Invoice.

Type of Invoice depending on domain, realm an usage (e.g. internal/external, dental, preliminary).

The individual or set of individuals receiving the goods and services billed in this invoice.

Links the event to the Patient context.

The individual or Organization responsible for balancing of this invoice.

Date/time(s) of when this Invoice was posted.

The list of types may be constrained as appropriate for the type of charge item.

The organizationissuing the Invoice.

Practitioners and Devices can be associated with multiple organizations. It has to be made clear, on behalf of which Organization the services have been rendered.

Bắt buộc. MA_LK trên identifier là khoá trao đổi với BHXH; account là quan hệ thật trong hệ thống, cho phép truy ngược ra mọi Encounter và ChargeItem của đợt mà không phải so chuỗi.

Systems posting the ChargeItems might not always be able to determine, which accounts the Items need to be places into. It is up to the potprocessing Financial System to apply internal rules to decide based on the Encounter/EpisodeOfCare/Patient/Coverage context and the type of ChargeItem, which Account is appropriate.

Each line item represents one charge for goods and services rendered. Details such as date, code and amount are found in the referenced ChargeItem resource.

An Extension

Năm trục độc lập cho biết dòng này được hình thành theo cách nào. Cardinality 0..1 vì phần lớn dòng thông thường không cần khai tường minh; nhưng BẮT BUỘC với các nhánh mà công thức mặc định không áp được: vận chuyển (ba cách tính khác nhau), gói thiết bị y tế và stent bổ sung (trần riêng), và mọi dòng thuộc diện miễn trần. Xem invariant vn-cost-statement-line-quantity-amount-required.

Ba thuộc tính của một dòng bảng kê mà Invoice.lineItem của FHIR R4 không có sẵn: phân đoạn thẻ mà dòng thuộc về, nhóm chi phí, và ngày hoặc khoảng thực hiện.

Invoice.lineItem chỉ có sequence, chargeItem[x] và priceComponent. Ba dữ liệu dưới đây là cột bắt buộc của mẫu QĐ 697/QĐ-BYT nên phải bổ sung; số lượng và tiền thì dùng element gốc (priceComponent.factor và priceComponent.amount).

Để trống khi dòng không thuộc phạm vi BHYT trong các trường hợp thông thường. NGOẠI LỆ: dòng thuộc phân đoạn không có coverage — tức bảng kê của người không có thẻ BHYT — PHẢI khai paymentRatio = 0 tường minh theo QĐ 697/QĐ-BYT Phần Hai mục 2, vì trên profile này việc vắng mặt đã mang nghĩa riêng là dòng ngoài phạm vi BHYT. Xem invariant vn-cost-statement-uninsured-line-defaults.

Để trống khi dòng chưa phân bổ. Khi có, tổng bốn nguồn phải bằng thành tiền bệnh viện của dòng.

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.

Sequence in which the items appear on the invoice.

The ChargeItem contains information such as the billing code, date, amount etc. If no further details are required for the lineItem, inline billing codes can be added using the CodeableConcept data type instead of the Reference.

The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated.

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.

This code identifies the type of the component.

Codes indicating the kind of the price component.

The amount calculated for this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated.

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.

This code identifies the type of the component.

Codes indicating the kind of the price component.

The factor that has been applied on the base price for calculating this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

The amount calculated for this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

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.

Invoice total , taxes excluded.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

ISO 4217 Currency Code.

A code indicating the currency, taken from ISO 4217.

A code indicating the currency, taken from ISO 4217.

Invoice total, tax included.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

Mỗi phân đoạn là một thẻ BHYT trong một khoảng thời gian với một mức hưởng. Người không có thẻ vẫn có ít nhất một phân đoạn (thường là một; profile để segment 1..* nên không chặn trường hợp bảng kê tách nhiều phân đoạn), nhưng phân đoạn không có coverage thì không được mang benefitLevel.

Mã liên kết hồ sơ khám bệnh, chữa bệnh theo QĐ 3176/QĐ-BYT. Bắt buộc và duy nhất một lát: đây là giá trị mà VNCoreCostStatementComposition.identifier phải trùng, và là khoá nối sang các VNCoreClaim của cùng đợt.

HAI VAI của khoá này, cần phân biệt khi triển khai: với hồ sơ có BHYT, giá trị chính là MA_LK được nộp cho cơ quan bảo hiểm theo QĐ 3176/QĐ-BYT. Với người bệnh KHÔNG có BHYT, bảng kê vẫn bắt buộc lát này nhưng giá trị chỉ đóng vai khoá nối nội bộ của cơ sở giữa bảng kê, bản ký và các hồ sơ cùng đợt — nó sẽ không bao giờ được nộp cho cơ quan bảo hiểm. Cơ sở tự sinh giá trị theo quy tắc của mình; ví dụ ExampleCostStatementUninsured dùng tiền tố LK-UNINSURED-.

Bắt buộc. MA_LK trên identifier là khoá trao đổi với BHXH; account là quan hệ thật trong hệ thống, cho phép truy ngược ra mọi Encounter và ChargeItem của đợt mà không phải so chuỗi.

Năm trục độc lập cho biết dòng này được hình thành theo cách nào. Cardinality 0..1 vì phần lớn dòng thông thường không cần khai tường minh; nhưng BẮT BUỘC với các nhánh mà công thức mặc định không áp được: vận chuyển (ba cách tính khác nhau), gói thiết bị y tế và stent bổ sung (trần riêng), và mọi dòng thuộc diện miễn trần. Xem invariant vn-cost-statement-line-quantity-amount-required.

Để trống khi dòng không thuộc phạm vi BHYT trong các trường hợp thông thường. NGOẠI LỆ: dòng thuộc phân đoạn không có coverage — tức bảng kê của người không có thẻ BHYT — PHẢI khai paymentRatio = 0 tường minh theo QĐ 697/QĐ-BYT Phần Hai mục 2, vì trên profile này việc vắng mặt đã mang nghĩa riêng là dòng ngoài phạm vi BHYT. Xem invariant vn-cost-statement-uninsured-line-defaults.

Để trống khi dòng chưa phân bổ. Khi có, tổng bốn nguồn phải bằng thành tiền bệnh viện của dòng.

Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose.

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

Mỗi phân đoạn là một thẻ BHYT trong một khoảng thời gian với một mức hưởng. Người không có thẻ vẫn có ít nhất một phân đoạn (thường là một; profile để segment 1..* nên không chặn trường hợp bảng kê tách nhiều phân đoạn), nhưng phân đoạn không có coverage thì không được mang benefitLevel.

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.

Identifier of this Invoice, often used for reference in correspondence about this invoice or for tracking of payments.

Allows Identification of this Invoice instance.

Mã liên kết hồ sơ khám bệnh, chữa bệnh theo QĐ 3176/QĐ-BYT. Bắt buộc và duy nhất một lát: đây là giá trị mà VNCoreCostStatementComposition.identifier phải trùng, và là khoá nối sang các VNCoreClaim của cùng đợt.

HAI VAI của khoá này, cần phân biệt khi triển khai: với hồ sơ có BHYT, giá trị chính là MA_LK được nộp cho cơ quan bảo hiểm theo QĐ 3176/QĐ-BYT. Với người bệnh KHÔNG có BHYT, bảng kê vẫn bắt buộc lát này nhưng giá trị chỉ đóng vai khoá nối nội bộ của cơ sở giữa bảng kê, bản ký và các hồ sơ cùng đợt — nó sẽ không bao giờ được nộp cho cơ quan bảo hiểm. Cơ sở tự sinh giá trị theo quy tắc của mình; ví dụ ExampleCostStatementUninsured dùng tiền tố LK-UNINSURED-.

Allows Identification of this Invoice instance.

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 current state of the Invoice.

Codes identifying the lifecycle stage of an Invoice.

In case of Invoice cancellation a reason must be given (entered in error, superseded by corrected invoice etc.).

Derived Profiles may choose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.

Type of Invoice depending on domain, realm an usage (e.g. internal/external, dental, preliminary).

The individual or set of individuals receiving the goods and services billed in this invoice.

Links the event to the Patient context.

The individual or Organization responsible for balancing of this invoice.

Date/time(s) of when this Invoice was posted.

The list of types may be constrained as appropriate for the type of charge item.

Indicates who or what performed or participated in the charged service.

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.

Describes the type of involvement (e.g. transcriptionist, creator etc.). If the invoice has been created automatically, the Participant may be a billing engine or another kind of device.

The device, practitioner, etc. who performed or participated in the service.

The organizationissuing the Invoice.

Practitioners and Devices can be associated with multiple organizations. It has to be made clear, on behalf of which Organization the services have been rendered.

Bắt buộc. MA_LK trên identifier là khoá trao đổi với BHXH; account là quan hệ thật trong hệ thống, cho phép truy ngược ra mọi Encounter và ChargeItem của đợt mà không phải so chuỗi.

Systems posting the ChargeItems might not always be able to determine, which accounts the Items need to be places into. It is up to the potprocessing Financial System to apply internal rules to decide based on the Encounter/EpisodeOfCare/Patient/Coverage context and the type of ChargeItem, which Account is appropriate.

Each line item represents one charge for goods and services rendered. Details such as date, code and amount are found in the referenced ChargeItem resource.

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

An Extension

Năm trục độc lập cho biết dòng này được hình thành theo cách nào. Cardinality 0..1 vì phần lớn dòng thông thường không cần khai tường minh; nhưng BẮT BUỘC với các nhánh mà công thức mặc định không áp được: vận chuyển (ba cách tính khác nhau), gói thiết bị y tế và stent bổ sung (trần riêng), và mọi dòng thuộc diện miễn trần. Xem invariant vn-cost-statement-line-quantity-amount-required.

Ba thuộc tính của một dòng bảng kê mà Invoice.lineItem của FHIR R4 không có sẵn: phân đoạn thẻ mà dòng thuộc về, nhóm chi phí, và ngày hoặc khoảng thực hiện.

Invoice.lineItem chỉ có sequence, chargeItem[x] và priceComponent. Ba dữ liệu dưới đây là cột bắt buộc của mẫu QĐ 697/QĐ-BYT nên phải bổ sung; số lượng và tiền thì dùng element gốc (priceComponent.factor và priceComponent.amount).

Để trống khi dòng không thuộc phạm vi BHYT trong các trường hợp thông thường. NGOẠI LỆ: dòng thuộc phân đoạn không có coverage — tức bảng kê của người không có thẻ BHYT — PHẢI khai paymentRatio = 0 tường minh theo QĐ 697/QĐ-BYT Phần Hai mục 2, vì trên profile này việc vắng mặt đã mang nghĩa riêng là dòng ngoài phạm vi BHYT. Xem invariant vn-cost-statement-uninsured-line-defaults.

Để trống khi dòng chưa phân bổ. Khi có, tổng bốn nguồn phải bằng thành tiền bệnh viện của dòng.

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.

Sequence in which the items appear on the invoice.

The ChargeItem contains information such as the billing code, date, amount etc. If no further details are required for the lineItem, inline billing codes can be added using the CodeableConcept data type instead of the Reference.

The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated.

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.

This code identifies the type of the component.

Codes indicating the kind of the price component.

A code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.

The factor that has been applied on the base price for calculating this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

The amount calculated for this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

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.

The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated.

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.

This code identifies the type of the component.

Codes indicating the kind of the price component.

A code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc.

The factor that has been applied on the base price for calculating this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

The amount calculated for this component.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

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.

The total amount for the Invoice may be calculated as the sum of the line items with surcharges/deductions that apply in certain conditions. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the total price was calculated.

Invoice total , taxes excluded.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

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.

Invoice total, tax included.

There is no reason to carry the price in the instance of a ChargeItem unless circumstances require a manual override. The list prices or are usually defined in a back catalogue of the billing codes (see ChargeItem.definition). Derived profiles may require a ChargeItem.overrideReason to be provided if either factor or price are manually overridden.

Payment details such as banking details, period of payment, deductibles, methods of payment.

Derived Profiles may chose to add invariants requiring this field to be populated if either priceOverride or factorOverride have been filled.

Comments made about the invoice by the issuer, subject, or other participants.