A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.

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ở rộng ghi nhận loại hình cơ sở y tế (bệnh viện, phòng khám, trạm y tế...). FHIR Organization.type dùng mã quốc tế — extension này bổ sung phân loại theo y tế Việt Nam. Căn cứ: Luật KCB 2023 (15/2023/QH15), Điều 47-48.

Mở rộng ghi nhận cấp quản lý hành chính của cơ sở y tế trong mô hình hiện hành sau NQ 202/2025/QH15. Không dùng extension này để biểu diễn tuyến chuyên môn kỹ thuật lịch sử.

Mở rộng ghi nhận hạng pháp lý của cơ sở khám bệnh, chữa bệnh theo TT 06/2024/TT-BYT. Chỉ áp dụng cho cơ sở KCB; không dùng để biểu diễn trường hợp chưa xếp hạng hoặc hạng của đơn vị y tế không phải cơ sở KCB.

Mở rộng ghi nhận hạng pháp lý của đơn vị sự nghiệp y tế không phải cơ sở khám bệnh, chữa bệnh theo TT 06/2024/TT-BYT. Áp dụng cho cơ sở y tế dự phòng, trung tâm y tế, cơ sở kiểm nghiệm và kiểm định.

Mở rộng ghi nhận trạng thái xếp hạng của cơ sở y tế nhằm biểu diễn các trường hợp đã xếp hạng, chưa xếp hạng hoặc không áp dụng mà không làm sai bộ mã hạng pháp lý.

Mở rộng ghi nhận cấp khám bệnh, chữa bệnh hiện hành của cơ sở hoặc địa điểm cung cấp dịch vụ theo Luật KCB 2023 và NĐ 96/2023/NĐ-CP. Có thể được dùng trong nghiệp vụ BHYT theo NĐ 188/2025/NĐ-CP.

Mở rộng ghi nhận tuyến chuyên môn kỹ thuật lịch sử theo TT 43/2013/TT-BYT cho dữ liệu cũ hoặc bài toán chuyển đổi. Không dùng để biểu diễn mô hình hiện hành.

Mở rộng ghi nhận dải điểm chất lượng cơ sở khám chữa bệnh phục vụ nghiệp vụ BHYT theo NĐ 188/2025/NĐ-CP.

Mở rộng tham chiếu Cơ quan hướng dẫn chuyên môn kỹ thuật của một cơ sở y tế khi cơ quan này khác với đơn vị quản lý hành chính (Organization.partOf). Trường hợp điển hình: Trạm Y tế (TYT) cấp xã — về quản lý hành chính trực thuộc UBND cấp xã (đặt tại Organization.partOf), nhưng về chuyên môn kỹ thuật chịu sự hướng dẫn, kiểm tra của Sở Y tế cấp tỉnh (đặt tại extension này). Tách biệt 2 chiều quản lý này phản ánh đúng mô hình chính quyền 2 cấp sau Luật 72/2025/QH15 và VBHN 06/VBHN-BYT (hợp nhất TT 43/2025/TT-BYT + TT 53/2025/TT-BYT về Trạm Y tế xã/phường). PHẠM VI CĂN CỨ: ba văn bản trên quy định MÔ HÌNH quản lý hai chiều — đó là chế định nghiệp vụ. Bản thân extension và cách đặt cơ quan hướng dẫn chuyên môn tách khỏi Organization.partOf là thiết kế của VN Core; FHIR base không có element nào cho quan hệ này. Căn cứ:

• Luật 72/2025/QH15 — 16/6/2025 — Luật Tổ chức chính quyền địa phương (hiệu lực 01/7/2025)
• VBHN 06/VBHN-BYT — 01/2026 — hợp nhất TT 43/2025/TT-BYT + TT 53/2025/TT-BYT về tổ chức và hoạt động của Trạm Y tế xã/phường/đặc khu.

Extension ghi nhận quan hệ vòng đời giữa cơ sở y tế hiện tại và một cơ sở khác khi mã/định danh cơ sở thay đổi do sáp nhập, chia tách, đổi tên hoặc thay mã (vd hệ quả của sắp xếp đơn vị hành chính theo NQ 202/2025/QH15). Generic cho mọi cơ sở y tế VN. Mỗi lần lặp mô tả MỘT quan hệ: loại quan hệ (relationType), cơ sở liên quan (target), thời điểm hiệu lực (period), căn cứ pháp lý (legalBasis) và các hạng mục được kế thừa (carryOver). Khi cơ sở tiền nhiệm đã giải thể và không còn Organization resource phân giải được, target có thể dùng Reference.identifier để tham chiếu logic theo mã CSKCB cũ. Căn cứ: NQ 202/2025/QH15 (sắp xếp ĐVHC) + NĐ 102/2025/NĐ-CP (CSDL quốc gia về y tế).

Dùng khi mã/định danh cơ sở thay đổi do sáp nhập, chia tách, đổi tên hoặc thay mã (vd hệ quả sắp xếp ĐVHC theo NQ 202/2025/QH15). Lặp 0..* để ghi nhiều quan hệ. Theo NĐ 102/2025/NĐ-CP — CSDL quốc gia về y tế.

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 for the organization that is used to identify the organization across multiple disparate systems.

Luật 15/2023/QH15 Điều 49 khoản 1 và Điều 50 khoản 1-2 yêu cầu cơ sở khám bệnh, chữa bệnh có giấy phép hoạt động và quy định một giấy phép cho mỗi cơ sở/địa điểm. Nghĩa vụ đó nằm ở profile con VNCoreKCBOrganization (slice identifier[OperatingLicense] 1..1) chứ không ở profile này, vì VNCoreOrganization còn phục vụ nhà thuốc, cơ sở y tế dự phòng, đơn vị kiểm nghiệm, cơ quan quản lý và cơ quan BHXH — những tổ chức không thuộc diện cấp giấy phép hoạt động KCB. Trong mọi trường hợp, CSKCB, MA_GTIN_CSKCB và mã cục bộ KHÔNG được dùng thay thế hoặc làm bằng chứng giấy phép.

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.

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

Mã cơ sở khám chữa bệnh do BHXH Việt Nam cấp — 5 chữ số. Slice này chỉ áp dụng khi cơ sở có mã CSKCB.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

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.

Mã định danh cơ sở khám bệnh, chữa bệnh — 13 ký tự, cấp qua Hệ thống Quản lý Quốc gia về hành nghề KCB. QĐ 2062/QĐ-BYT thay Phụ lục 01-03 QĐ 1551/QĐ-BYT và tiếp tục quy định trường MA_GTIN_CSKCB tại Phụ lục 01 STT 23, Phụ lục 02 STT 19 và Phụ lục 03 STT 18. Văn bản mô tả 'theo chuẩn GLN' nhưng chưa xác minh là GS1 GLN đăng ký toàn cầu. Slice này chỉ áp dụng khi cơ sở đã được cấp mã 13 ký tự.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

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.

Mã quản lý cục bộ do đơn vị tự cấp, dùng cho cơ sở hoặc đơn vị y tế chưa có hoặc không dùng mã CSKCB trong ngữ cảnh đang trao đổi.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

Identifier.system is always case sensitive.

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

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

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

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

Whether the organization's record is still in active use.

This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

Need a flag to indicate a record is no longer to be used and should generally be hidden for the user in the UI.

The kind(s) of organization that this is.

Organizations can be corporations, wards, sections, clinical teams, government departments, etc. Note that code is generally a classifier of the type of organization; in many applications, codes are used to identity a particular organization (say, ward) as opposed to another of the same type - these are identifiers, not codes

When considering if multiple types are appropriate, you should evaluate if child organizations would be a more appropriate use of the concept, as different types likely are in different sub-areas of the organization. This is most likely to be used where type values have orthogonal values, such as a religious, academic and medical center.

We expect that some jurisdictions will profile this optionality to be a single cardinality.

Used to categorize the organization.

Need to be able to track the kind of organization that this is - different organization types have different uses.

A name associated with the organization.

If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches.

Need to use the name as the label of the organization.

A contact detail for the organization.

The use code 'home' is not to be used. Note that these contacts are not the contact details of people who are employed by or represent the organization, but official contacts for the organization itself.

Human contact for the organization.

An address for the organization.

Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used.

May need to keep track of the organization's addresses for contacting, billing or reporting requirements.

Technical endpoints providing access to services operated for the organization.

Tham chiếu đến Endpoint resource biểu diễn cổng điện tử của tổ chức. Đối với CSKCB ký hợp đồng BHXH, có thể tham chiếu đến VNCoreEndpointBHYT (cổng https://gdbhyt.baohiemxahoi.gov.vn). Theo TT 12/2026/TT-BTC Điều 2 + NĐ 164/2025/NĐ-CP.

Organizations have multiple systems that provide various services and need to be able to define the technical connection details for how to connect to them, and for what purpose.

Dùng khi mã/định danh cơ sở thay đổi do sáp nhập, chia tách, đổi tên hoặc thay mã (vd hệ quả sắp xếp ĐVHC theo NQ 202/2025/QH15). Lặp 0..* để ghi nhiều quan hệ. Theo NĐ 102/2025/NĐ-CP — CSDL quốc gia về y tế.

Luật 15/2023/QH15 Điều 49 khoản 1 và Điều 50 khoản 1-2 yêu cầu cơ sở khám bệnh, chữa bệnh có giấy phép hoạt động và quy định một giấy phép cho mỗi cơ sở/địa điểm. Nghĩa vụ đó nằm ở profile con VNCoreKCBOrganization (slice identifier[OperatingLicense] 1..1) chứ không ở profile này, vì VNCoreOrganization còn phục vụ nhà thuốc, cơ sở y tế dự phòng, đơn vị kiểm nghiệm, cơ quan quản lý và cơ quan BHXH — những tổ chức không thuộc diện cấp giấy phép hoạt động KCB. Trong mọi trường hợp, CSKCB, MA_GTIN_CSKCB và mã cục bộ KHÔNG được dùng thay thế hoặc làm bằng chứng giấy phép.

Mã cơ sở khám chữa bệnh do BHXH Việt Nam cấp — 5 chữ số. Slice này chỉ áp dụng khi cơ sở có mã CSKCB.

Mã định danh cơ sở khám bệnh, chữa bệnh — 13 ký tự, cấp qua Hệ thống Quản lý Quốc gia về hành nghề KCB. QĐ 2062/QĐ-BYT thay Phụ lục 01-03 QĐ 1551/QĐ-BYT và tiếp tục quy định trường MA_GTIN_CSKCB tại Phụ lục 01 STT 23, Phụ lục 02 STT 19 và Phụ lục 03 STT 18. Văn bản mô tả 'theo chuẩn GLN' nhưng chưa xác minh là GS1 GLN đăng ký toàn cầu. Slice này chỉ áp dụng khi cơ sở đã được cấp mã 13 ký tự.

Mã quản lý cục bộ do đơn vị tự cấp, dùng cho cơ sở hoặc đơn vị y tế chưa có hoặc không dùng mã CSKCB trong ngữ cảnh đang trao đổi.

Tham chiếu đến Endpoint resource biểu diễn cổng điện tử của tổ chức. Đối với CSKCB ký hợp đồng BHXH, có thể tham chiếu đến VNCoreEndpointBHYT (cổng https://gdbhyt.baohiemxahoi.gov.vn). Theo TT 12/2026/TT-BTC Điều 2 + NĐ 164/2025/NĐ-CP.

A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc.

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ở rộng ghi nhận loại hình cơ sở y tế (bệnh viện, phòng khám, trạm y tế...). FHIR Organization.type dùng mã quốc tế — extension này bổ sung phân loại theo y tế Việt Nam. Căn cứ: Luật KCB 2023 (15/2023/QH15), Điều 47-48.

Mở rộng ghi nhận cấp quản lý hành chính của cơ sở y tế trong mô hình hiện hành sau NQ 202/2025/QH15. Không dùng extension này để biểu diễn tuyến chuyên môn kỹ thuật lịch sử.

Mở rộng ghi nhận hạng pháp lý của cơ sở khám bệnh, chữa bệnh theo TT 06/2024/TT-BYT. Chỉ áp dụng cho cơ sở KCB; không dùng để biểu diễn trường hợp chưa xếp hạng hoặc hạng của đơn vị y tế không phải cơ sở KCB.

Mở rộng ghi nhận hạng pháp lý của đơn vị sự nghiệp y tế không phải cơ sở khám bệnh, chữa bệnh theo TT 06/2024/TT-BYT. Áp dụng cho cơ sở y tế dự phòng, trung tâm y tế, cơ sở kiểm nghiệm và kiểm định.

Mở rộng ghi nhận trạng thái xếp hạng của cơ sở y tế nhằm biểu diễn các trường hợp đã xếp hạng, chưa xếp hạng hoặc không áp dụng mà không làm sai bộ mã hạng pháp lý.

Mở rộng ghi nhận cấp khám bệnh, chữa bệnh hiện hành của cơ sở hoặc địa điểm cung cấp dịch vụ theo Luật KCB 2023 và NĐ 96/2023/NĐ-CP. Có thể được dùng trong nghiệp vụ BHYT theo NĐ 188/2025/NĐ-CP.

Mở rộng ghi nhận tuyến chuyên môn kỹ thuật lịch sử theo TT 43/2013/TT-BYT cho dữ liệu cũ hoặc bài toán chuyển đổi. Không dùng để biểu diễn mô hình hiện hành.

Mở rộng ghi nhận dải điểm chất lượng cơ sở khám chữa bệnh phục vụ nghiệp vụ BHYT theo NĐ 188/2025/NĐ-CP.

Mở rộng tham chiếu Cơ quan hướng dẫn chuyên môn kỹ thuật của một cơ sở y tế khi cơ quan này khác với đơn vị quản lý hành chính (Organization.partOf). Trường hợp điển hình: Trạm Y tế (TYT) cấp xã — về quản lý hành chính trực thuộc UBND cấp xã (đặt tại Organization.partOf), nhưng về chuyên môn kỹ thuật chịu sự hướng dẫn, kiểm tra của Sở Y tế cấp tỉnh (đặt tại extension này). Tách biệt 2 chiều quản lý này phản ánh đúng mô hình chính quyền 2 cấp sau Luật 72/2025/QH15 và VBHN 06/VBHN-BYT (hợp nhất TT 43/2025/TT-BYT + TT 53/2025/TT-BYT về Trạm Y tế xã/phường). PHẠM VI CĂN CỨ: ba văn bản trên quy định MÔ HÌNH quản lý hai chiều — đó là chế định nghiệp vụ. Bản thân extension và cách đặt cơ quan hướng dẫn chuyên môn tách khỏi Organization.partOf là thiết kế của VN Core; FHIR base không có element nào cho quan hệ này. Căn cứ:

• Luật 72/2025/QH15 — 16/6/2025 — Luật Tổ chức chính quyền địa phương (hiệu lực 01/7/2025)
• VBHN 06/VBHN-BYT — 01/2026 — hợp nhất TT 43/2025/TT-BYT + TT 53/2025/TT-BYT về tổ chức và hoạt động của Trạm Y tế xã/phường/đặc khu.

Extension ghi nhận quan hệ vòng đời giữa cơ sở y tế hiện tại và một cơ sở khác khi mã/định danh cơ sở thay đổi do sáp nhập, chia tách, đổi tên hoặc thay mã (vd hệ quả của sắp xếp đơn vị hành chính theo NQ 202/2025/QH15). Generic cho mọi cơ sở y tế VN. Mỗi lần lặp mô tả MỘT quan hệ: loại quan hệ (relationType), cơ sở liên quan (target), thời điểm hiệu lực (period), căn cứ pháp lý (legalBasis) và các hạng mục được kế thừa (carryOver). Khi cơ sở tiền nhiệm đã giải thể và không còn Organization resource phân giải được, target có thể dùng Reference.identifier để tham chiếu logic theo mã CSKCB cũ. Căn cứ: NQ 202/2025/QH15 (sắp xếp ĐVHC) + NĐ 102/2025/NĐ-CP (CSDL quốc gia về y tế).

Dùng khi mã/định danh cơ sở thay đổi do sáp nhập, chia tách, đổi tên hoặc thay mã (vd hệ quả sắp xếp ĐVHC theo NQ 202/2025/QH15). Lặp 0..* để ghi nhiều quan hệ. Theo NĐ 102/2025/NĐ-CP — CSDL quốc gia về y tế.

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 for the organization that is used to identify the organization across multiple disparate systems.

Luật 15/2023/QH15 Điều 49 khoản 1 và Điều 50 khoản 1-2 yêu cầu cơ sở khám bệnh, chữa bệnh có giấy phép hoạt động và quy định một giấy phép cho mỗi cơ sở/địa điểm. Nghĩa vụ đó nằm ở profile con VNCoreKCBOrganization (slice identifier[OperatingLicense] 1..1) chứ không ở profile này, vì VNCoreOrganization còn phục vụ nhà thuốc, cơ sở y tế dự phòng, đơn vị kiểm nghiệm, cơ quan quản lý và cơ quan BHXH — những tổ chức không thuộc diện cấp giấy phép hoạt động KCB. Trong mọi trường hợp, CSKCB, MA_GTIN_CSKCB và mã cục bộ KHÔNG được dùng thay thế hoặc làm bằng chứng giấy phép.

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.

Mã cơ sở khám chữa bệnh do BHXH Việt Nam cấp — 5 chữ số. Slice này chỉ áp dụng khi cơ sở có mã CSKCB.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

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.

Mã định danh cơ sở khám bệnh, chữa bệnh — 13 ký tự, cấp qua Hệ thống Quản lý Quốc gia về hành nghề KCB. QĐ 2062/QĐ-BYT thay Phụ lục 01-03 QĐ 1551/QĐ-BYT và tiếp tục quy định trường MA_GTIN_CSKCB tại Phụ lục 01 STT 23, Phụ lục 02 STT 19 và Phụ lục 03 STT 18. Văn bản mô tả 'theo chuẩn GLN' nhưng chưa xác minh là GS1 GLN đăng ký toàn cầu. Slice này chỉ áp dụng khi cơ sở đã được cấp mã 13 ký tự.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

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.

Mã quản lý cục bộ do đơn vị tự cấp, dùng cho cơ sở hoặc đơn vị y tế chưa có hoặc không dùng mã CSKCB trong ngữ cảnh đang trao đổi.

Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.

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.

Whether the organization's record is still in active use.

This active flag is not intended to be used to mark an organization as temporarily closed or under construction. Instead the Location(s) within the Organization should have the suspended status. If further details of the reason for the suspension are required, then an extension on this element should be used.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

Need a flag to indicate a record is no longer to be used and should generally be hidden for the user in the UI.

The kind(s) of organization that this is.

Organizations can be corporations, wards, sections, clinical teams, government departments, etc. Note that code is generally a classifier of the type of organization; in many applications, codes are used to identity a particular organization (say, ward) as opposed to another of the same type - these are identifiers, not codes

When considering if multiple types are appropriate, you should evaluate if child organizations would be a more appropriate use of the concept, as different types likely are in different sub-areas of the organization. This is most likely to be used where type values have orthogonal values, such as a religious, academic and medical center.

We expect that some jurisdictions will profile this optionality to be a single cardinality.

Used to categorize the organization.

Need to be able to track the kind of organization that this is - different organization types have different uses.

A name associated with the organization.

If the name of an organization changes, consider putting the old name in the alias column so that it can still be located through searches.

Need to use the name as the label of the organization.

A list of alternate names that the organization is known as, or was known as in the past.

There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the organization.

Over time locations and organizations go through many changes and can be known by different names.

For searching knowing previous names that the organization was known by can be very useful.

A contact detail for the organization.

The use code 'home' is not to be used. Note that these contacts are not the contact details of people who are employed by or represent the organization, but official contacts for the organization itself.

Human contact for the organization.

An address for the organization.

Organization may have multiple addresses with different uses or applicable periods. The use code 'home' is not to be used.

May need to keep track of the organization's addresses for contacting, billing or reporting requirements.

The organization of which this organization forms a part.

Need to be able to track the hierarchy of organizations within an organization.

Contact for the organization for a certain purpose.

Where multiple contacts for the same purpose are provided there is a standard extension that can be used to determine which one is the preferred contact to use.

Need to keep track of assigned contact points within bigger organization.

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

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

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

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

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

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

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Indicates a purpose for which the contact can be reached.

The purpose for which you would contact a contact party.

Need to distinguish between multiple contact persons.

A name associated with the contact.

Need to be able to track the person by name.

A contact detail (e.g. a telephone number or an email address) by which the party may be contacted.

People have (primary) ways to contact them in some way such as phone, email.

Visiting or postal addresses for the contact.