An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

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

Giữ 0..1 không Must Support chỉ để đọc dữ liệu lịch sử MA_LYDO_VVIEN. QĐ 4210/QĐ-BYT hết hiệu lực từ 01/07/2024 theo QĐ 4750/QĐ-BYT. Dữ liệu mới dùng Claim.subType (MA_DOITUONG_KCB/QĐ 3276/QĐ-BYT) và Encounter.type (MA_LOAI_KCB/QĐ 1804/QĐ-BYT).

Hình thức đến khám chữa bệnh. Bổ sung cho danh mục loại KCB legacy của VNCoreExtInsuranceVisitType: loại KCB xác định mức hưởng BHYT, extension này ghi nhận nguồn gốc chuyển bệnh (tự đến, chuyển lên, chuyển xuống, chuyển ngang, cấp cứu). Căn cứ nghiệp vụ: NĐ 188/2025/NĐ-CP, TT 01/2025/TT-BYT — chế định chuyển cơ sở khám bệnh, chữa bệnh. Tập mã do VN Core thiết kế; xem đính chính 19/08/2026 tại VNReferralModeCS.

Mở rộng ghi nhận kết quả điều trị (trường KET_QUA_DTRI) cho lượt khám/điều trị. Căn cứ: QĐ 130/QĐ-BYT (2023), sửa đổi bởi QĐ 4750/QĐ-BYT (2023) và QĐ 3176/QĐ-BYT (29/10/2024). 8 giá trị theo VNTreatmentOutcomeVS: 1 Khỏi, 2 Đỡ, 3 Không thay đổi, 4 Nặng hơn, 5 Tử vong tại cơ sở KCB, 6 Tiên lượng nặng xin về, 7 Chưa xác định, 8 Tử vong ngoại viện. Đính chính 16/08/2026: mô tả cũ ghi 5 giá trị và dừng ở 'Tử vong' — thiếu mã 6, 7 và mã 8 (tử vong ngoại viện, do QĐ 4750/QĐ-BYT bổ sung), khiến người triển khai tưởng danh mục hẹp hơn thực tế. Lưu ý: Khác với dischargeDisposition (loại ra viện — MA_LOAI_RV). KET_QUA_DTRI đánh giá kết quả y khoa; MA_LOAI_RV ghi nhận loại ra viện.

Phương thức thanh toán KCB BHYT: phí dịch vụ (FFS), định suất (Capitation), hoặc theo trường hợp bệnh (DRG). Mapping XML 3176: MA_PTTT (Bảng 2 STT 36, Bảng 3 STT 40). Nguồn thiết kế: OHP Data Processor (encounter-payment-method).

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(s) by which this encounter is known.

Identifier(s) by which this encounter is known.

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.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Current state of the encounter.

Loại hình encounter theo v3-ActCode. Khi dùng VR/virtual cho khám từ xa, tham chiếu TT 30/2023/TT-BYT; thanh toán BHYT cần theo hướng dẫn riêng hiện hành.

Classification of the encounter.

Loại hình khám bệnh, chữa bệnh theo trường MA_LOAI_KCB. Đây là nơi biểu diễn mã 01-16 (QĐ 1804/QĐ-BYT Phụ lục 01) trong dữ liệu đầu ra KCB/BHYT; không dùng Claim.type để chứa MA_LOAI_KCB.

Since there are many ways to further classify encounters, this element is 0..*.

The patient or group present at the encounter.

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

The list of people responsible for providing the service.

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.

Persons involved in the encounter other than the patient.

The appointment that scheduled this encounter.

The start and end time of the encounter.

If not (yet) known, the end of the Period may be omitted.

Lý do người bệnh đến khám, nhập viện hoặc yêu cầu dịch vụ. Nên mã hoá khi có thể; cho phép ghi text mô tả chief complaint tại thời điểm tiếp nhận.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

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

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The list of diagnosis relevant to this encounter.

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.

Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).

The type of diagnosis this condition represents.

Trỏ tới VNCoreAccount mang MA_LK của đợt. Không bắt buộc vì có lượt khám không phát sinh chi phí (tư vấn, huỷ lịch), nhưng mọi lượt đã sinh chi phí đều phải có.

The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Details about the admission to a healthcare service.

An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.

The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.

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.

Category or kind of location after discharge.

Cơ sở chịu trách nhiệm về lượt khám. Với hoạt động KHÁM BỆNH, CHỮA BỆNH có quản lý (Luật KCB 15/2023/QH15 Điều 48–50: chỉ cơ sở đã được cấp giấy phép hoạt động mới được cung cấp dịch vụ KCB), bên gửi dữ liệu SHALL trỏ tới cơ sở conform VNCoreKCBOrganization — mang mã cơ sở KCB (identifier[CSKCB]) và trạng thái giấy phép hoạt động. Việc CHẶN tạo lượt mới tại cơ sở đang bị đình chỉ toàn phần thuộc tầng nghiệp vụ/registry của hệ tiếp nhận, không thuộc structural validation — bản ghi lịch sử của cơ sở từng bị đình chỉ vẫn phải biểu diễn được.

Giữ 0..1 không Must Support chỉ để đọc dữ liệu lịch sử MA_LYDO_VVIEN. QĐ 4210/QĐ-BYT hết hiệu lực từ 01/07/2024 theo QĐ 4750/QĐ-BYT. Dữ liệu mới dùng Claim.subType (MA_DOITUONG_KCB/QĐ 3276/QĐ-BYT) và Encounter.type (MA_LOAI_KCB/QĐ 1804/QĐ-BYT).

Loại hình encounter theo v3-ActCode. Khi dùng VR/virtual cho khám từ xa, tham chiếu TT 30/2023/TT-BYT; thanh toán BHYT cần theo hướng dẫn riêng hiện hành.

Loại hình khám bệnh, chữa bệnh theo trường MA_LOAI_KCB. Đây là nơi biểu diễn mã 01-16 (QĐ 1804/QĐ-BYT Phụ lục 01) trong dữ liệu đầu ra KCB/BHYT; không dùng Claim.type để chứa MA_LOAI_KCB.

Lý do người bệnh đến khám, nhập viện hoặc yêu cầu dịch vụ. Nên mã hoá khi có thể; cho phép ghi text mô tả chief complaint tại thời điểm tiếp nhận.

Trỏ tới VNCoreAccount mang MA_LK của đợt. Không bắt buộc vì có lượt khám không phát sinh chi phí (tư vấn, huỷ lịch), nhưng mọi lượt đã sinh chi phí đều phải có.

Cơ sở chịu trách nhiệm về lượt khám. Với hoạt động KHÁM BỆNH, CHỮA BỆNH có quản lý (Luật KCB 15/2023/QH15 Điều 48–50: chỉ cơ sở đã được cấp giấy phép hoạt động mới được cung cấp dịch vụ KCB), bên gửi dữ liệu SHALL trỏ tới cơ sở conform VNCoreKCBOrganization — mang mã cơ sở KCB (identifier[CSKCB]) và trạng thái giấy phép hoạt động. Việc CHẶN tạo lượt mới tại cơ sở đang bị đình chỉ toàn phần thuộc tầng nghiệp vụ/registry của hệ tiếp nhận, không thuộc structural validation — bản ghi lịch sử của cơ sở từng bị đình chỉ vẫn phải biểu diễn được.

An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

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

Giữ 0..1 không Must Support chỉ để đọc dữ liệu lịch sử MA_LYDO_VVIEN. QĐ 4210/QĐ-BYT hết hiệu lực từ 01/07/2024 theo QĐ 4750/QĐ-BYT. Dữ liệu mới dùng Claim.subType (MA_DOITUONG_KCB/QĐ 3276/QĐ-BYT) và Encounter.type (MA_LOAI_KCB/QĐ 1804/QĐ-BYT).

Hình thức đến khám chữa bệnh. Bổ sung cho danh mục loại KCB legacy của VNCoreExtInsuranceVisitType: loại KCB xác định mức hưởng BHYT, extension này ghi nhận nguồn gốc chuyển bệnh (tự đến, chuyển lên, chuyển xuống, chuyển ngang, cấp cứu). Căn cứ nghiệp vụ: NĐ 188/2025/NĐ-CP, TT 01/2025/TT-BYT — chế định chuyển cơ sở khám bệnh, chữa bệnh. Tập mã do VN Core thiết kế; xem đính chính 19/08/2026 tại VNReferralModeCS.

Mở rộng ghi nhận kết quả điều trị (trường KET_QUA_DTRI) cho lượt khám/điều trị. Căn cứ: QĐ 130/QĐ-BYT (2023), sửa đổi bởi QĐ 4750/QĐ-BYT (2023) và QĐ 3176/QĐ-BYT (29/10/2024). 8 giá trị theo VNTreatmentOutcomeVS: 1 Khỏi, 2 Đỡ, 3 Không thay đổi, 4 Nặng hơn, 5 Tử vong tại cơ sở KCB, 6 Tiên lượng nặng xin về, 7 Chưa xác định, 8 Tử vong ngoại viện. Đính chính 16/08/2026: mô tả cũ ghi 5 giá trị và dừng ở 'Tử vong' — thiếu mã 6, 7 và mã 8 (tử vong ngoại viện, do QĐ 4750/QĐ-BYT bổ sung), khiến người triển khai tưởng danh mục hẹp hơn thực tế. Lưu ý: Khác với dischargeDisposition (loại ra viện — MA_LOAI_RV). KET_QUA_DTRI đánh giá kết quả y khoa; MA_LOAI_RV ghi nhận loại ra viện.

Phương thức thanh toán KCB BHYT: phí dịch vụ (FFS), định suất (Capitation), hoặc theo trường hợp bệnh (DRG). Mapping XML 3176: MA_PTTT (Bảng 2 STT 36, Bảng 3 STT 40). Nguồn thiết kế: OHP Data Processor (encounter-payment-method).

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(s) by which this encounter is known.

Identifier(s) by which this encounter is known.

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.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Current state of the encounter.

The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.

The current status is always found in the current version of the resource, not the status history.

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.

planned | arrived | triaged | in-progress | onleave | finished | cancelled +.

Current state of the encounter.

The time that the episode was in the specified status.

Loại hình encounter theo v3-ActCode. Khi dùng VR/virtual cho khám từ xa, tham chiếu TT 30/2023/TT-BYT; thanh toán BHYT cần theo hướng dẫn riêng hiện hành.

Classification of the encounter.

The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient.

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.

inpatient | outpatient | ambulatory | emergency +.

Classification of the encounter.

The time that the episode was in the specified class.

Loại hình khám bệnh, chữa bệnh theo trường MA_LOAI_KCB. Đây là nơi biểu diễn mã 01-16 (QĐ 1804/QĐ-BYT Phụ lục 01) trong dữ liệu đầu ra KCB/BHYT; không dùng Claim.type để chứa MA_LOAI_KCB.

Since there are many ways to further classify encounters, this element is 0..*.

Broad categorization of the service that is to be provided (e.g. cardiology).

Broad categorization of the service that is to be provided.

Indicates the urgency of the encounter.

Indicates the urgency of the encounter.

The patient or group present at the encounter.

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).

The request this encounter satisfies (e.g. incoming referral or procedure request).

The list of people responsible for providing the 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.

Role of participant in encounter.

The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

Role of participant in encounter.

The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period.

Persons involved in the encounter other than the patient.

The appointment that scheduled this encounter.

The start and end time of the encounter.

If not (yet) known, the end of the Period may be omitted.

Quantity of time the encounter lasted. This excludes the time during leaves of absence.

May differ from the time the Encounter.period lasted because of leave of absence.

Lý do người bệnh đến khám, nhập viện hoặc yêu cầu dịch vụ. Nên mã hoá khi có thể; cho phép ghi text mô tả chief complaint tại thời điểm tiếp nhận.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

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

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

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

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

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

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

The list of diagnosis relevant to this encounter.

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.

Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).

The type of diagnosis this condition represents.

Ranking of the diagnosis (for each role type).

Trỏ tới VNCoreAccount mang MA_LK của đợt. Không bắt buộc vì có lượt khám không phát sinh chi phí (tư vấn, huỷ lịch), nhưng mọi lượt đã sinh chi phí đều phải có.

The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Details about the admission to a healthcare service.

An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.

The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.

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.

Pre-admission identifier.

The location/organization from which the patient came before admission.

From where patient was admitted (physician referral, transfer).

From where the patient was admitted.

Whether this hospitalization is a readmission and why if known.

The reason for re-admission of this hospitalization encounter.

Diet preferences reported by the patient.

For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

Medical, cultural or ethical food preferences to help with catering requirements.

Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.

Special courtesies (VIP, board member).

Special courtesies.

Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.

Special arrangements.

Location/organization to which the patient is discharged.

Category or kind of location after discharge.