A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.

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.

Nhóm thiết bị y tế theo TT 04/2017/TT-BYT Phụ lục 01, sửa đổi bởi TT 24/2025/TT-BYT và văn bản hợp nhất hiện hành. Đây là phân loại phục vụ thanh toán/đối soát BHYT; khi đang biểu diễn một dòng chi phí, ưu tiên đặt tại Claim.item.extension[deviceGroup] thay vì coi là thuộc tính nội tại bắt buộc của Device.

Phân loại rủi ro thiết bị y tế A/B/C/D theo NĐ 98/2021/NĐ-CP Điều 4 (đã được sửa đổi, bổ sung bởi NĐ 07/2023/NĐ-CP và NĐ 04/2025/NĐ-CP) và TT 05/2022/TT-BYT (đã được sửa đổi, bổ sung bởi TT 59/2025/TT-BYT). Extension này là tùy chọn trên Device vì risk class là thuộc tính pháp lý ở mức sản phẩm/model/regulatory context; không bắt buộc cho mọi Device instance trong trao đổi lâm sàng hoặc BHYT. Phân biệt rõ với các dimension độc lập KHÔNG dùng extension này:

• Nhóm TBYT BHYT N01-N09 (TT 04/2017/TT-BYT Phụ lục 01) → dùng VNCoreExtDeviceGroup;
• Danh pháp thiết bị y tế (QĐ 3107/2024, QĐ 847/2025) → dùng Device.type với hệ danh pháp;
• 6 nhóm phân loại tiêu chuẩn kỹ thuật/chất lượng phục vụ đấu thầu theo TT 57/2025/TT-BYT (31/12/2025, hiệu lực 15/02/2026, triển khai 01/01/2027, căn cứ NĐ 214/2025/NĐ-CP về Luật Đấu thầu) → nếu cần biểu diễn, dùng extension riêng trong package procurement, KHÔNG dùng extension này.

Số lưu hành (registration number) của thiết bị y tế tại Việt Nam.

Căn cứ pháp lý: NĐ 98/2021/NĐ-CP Điều 21 (Phân nhóm số lưu hành), Chương III (Điều 17-33) về đăng ký lưu hành TBYT, đã được sửa đổi, bổ sung bởi NĐ 07/2023/NĐ-CP (03/03/2023) và NĐ 04/2025/NĐ-CP (hiệu lực 01/01/2025).

Phân nhóm theo NĐ 98/2021 Điều 21:

1. Loại A & B — Số công bố tiêu chuẩn áp dụng (Sở Y tế tỉnh/TP tiếp nhận):

   • Format: [STT tiếp nhận]/[Năm tiếp nhận 2 số]/[Mã ký hiệu Sở Y tế]-PCBA (loại A)
   • Format: [STT tiếp nhận]/[Năm tiếp nhận 2 số]/[Mã ký hiệu Sở Y tế]-PCBB (loại B)
   • PCBA/PCBB = Phiếu công bố loại A / loại B
   • Ví dụ: 2300001/23/HN-PCBA (Hồ sơ số 1 năm 2023, Sở Y tế Hà Nội tiếp nhận)

2. Loại C & D — Số Giấy chứng nhận đăng ký lưu hành (Bộ Y tế cấp):

   • Format chuẩn: [STT cấp]/[Năm cấp 2 số]/BYT-ĐKLH
   • Format rút gọn: [STT cấp]/BYT-ĐKLH
   • ĐKLH = Đăng ký lưu hành
   • Ví dụ: 2300055/BYT-ĐKLH hoặc 2300055/23/BYT-ĐKLH

Phạm vi:

• Bắt buộc cho loại B/C/D trước khi đưa ra thị trường
• Loại A chỉ công bố tiêu chuẩn áp dụng (vẫn dùng PCBA format)
• Đây là định danh ở mức sản phẩm/model/regulatory context, KHÔNG phải định danh per-instance

Lưu ý phân biệt: Extension này độc lập với:

• UDI (định danh per-instance theo HL7 best practice)
• MA_VAT_TU (mã nghiệp vụ BHYT theo QĐ 3176)
• Serial number (per-instance physical)
• Mã tài sản BV (internal facility code)

Cờ boolean phân biệt TBYT IVD (chẩn đoán in vitro: sinh phẩm, thuốc thử, máy xét nghiệm) với TBYT thông thường theo VBHN 08/2026/VBHN-BYT. Tùy chọn — chỉ đặt khi cần phân biệt rõ trong ngữ cảnh đăng ký lưu hành/đấu thầu/BHYT.

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.

Unique instance identifiers assigned to a device by manufacturers other organizations or owners.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

Mã vật tư/thiết bị y tế dùng trong XML dữ liệu đầu ra KCB và thanh toán BHYT. Mapping QĐ 3176/QĐ-BYT: MA_VAT_TU. Đây là mã nghiệp vụ/legacy; không phải UDI, serial number, số lưu hành hoặc mã tài sản. Khi mã này được dùng như product/service code của dòng chi phí, ưu tiên biểu diễn ở Claim.item.productOrService.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

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.

Số serial khi hệ thống trao đổi dưới dạng Identifier. Device.serialNumber vẫn là vị trí FHIR chính để ghi serial number.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

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.

Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.

UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.

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

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

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

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

The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.

The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats SHALL be base64 encoded.

The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.

If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

Status of the Device availability.

This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.

The availability status of the device.

The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product.

For example, this applies to devices in the United States regulated under Code of Federal Regulation 21CFR§1271.290(c).

Tên hãng sản xuất. Các QĐ 5086/QĐ-BYT, 637/2022, 1844/2022, 3181/2022 liên quan mã hãng sản xuất VTYT/TBYT; không model thành mã hàng TBYT đầy đủ trong v0.3.

The date and time when the device was manufactured.

The date and time beyond which this device is no longer valid or should not be used (if applicable).

Lot number assigned by the manufacturer.

The serial number assigned by the organization when the device was manufactured.

Alphanumeric Maximum 20.

The model number for the device.

Loại thiết bị cấy ghép, nên mã hóa bằng SNOMED CT hoặc hệ danh pháp thiết bị đã được governance. Chưa required binding vào QĐ 847/QĐ 3107 trong v0.4.

Codes to identify medical devices.

Bệnh nhân gắn với thiết bị cấy ghép. Đây là điểm khác với VNCoreDevice nền, vốn vẫn hỗ trợ thiết bị chưa gắn người bệnh hoặc vật tư/thiết bị trong dữ liệu thanh toán.

If the device is implanted in a patient, then need to associate the device to the patient.

Provides additional safety characteristics about a medical device. For example devices containing latex.

Loại thiết bị cấy ghép, nên mã hóa bằng SNOMED CT hoặc hệ danh pháp thiết bị đã được governance. Chưa required binding vào QĐ 847/QĐ 3107 trong v0.4.

Bệnh nhân gắn với thiết bị cấy ghép. Đây là điểm khác với VNCoreDevice nền, vốn vẫn hỗ trợ thiết bị chưa gắn người bệnh hoặc vật tư/thiết bị trong dữ liệu thanh toán.

A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.

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

Nhóm thiết bị y tế theo TT 04/2017/TT-BYT Phụ lục 01, sửa đổi bởi TT 24/2025/TT-BYT và văn bản hợp nhất hiện hành. Đây là phân loại phục vụ thanh toán/đối soát BHYT; khi đang biểu diễn một dòng chi phí, ưu tiên đặt tại Claim.item.extension[deviceGroup] thay vì coi là thuộc tính nội tại bắt buộc của Device.

Phân loại rủi ro thiết bị y tế A/B/C/D theo NĐ 98/2021/NĐ-CP Điều 4 (đã được sửa đổi, bổ sung bởi NĐ 07/2023/NĐ-CP và NĐ 04/2025/NĐ-CP) và TT 05/2022/TT-BYT (đã được sửa đổi, bổ sung bởi TT 59/2025/TT-BYT). Extension này là tùy chọn trên Device vì risk class là thuộc tính pháp lý ở mức sản phẩm/model/regulatory context; không bắt buộc cho mọi Device instance trong trao đổi lâm sàng hoặc BHYT. Phân biệt rõ với các dimension độc lập KHÔNG dùng extension này:

• Nhóm TBYT BHYT N01-N09 (TT 04/2017/TT-BYT Phụ lục 01) → dùng VNCoreExtDeviceGroup;
• Danh pháp thiết bị y tế (QĐ 3107/2024, QĐ 847/2025) → dùng Device.type với hệ danh pháp;
• 6 nhóm phân loại tiêu chuẩn kỹ thuật/chất lượng phục vụ đấu thầu theo TT 57/2025/TT-BYT (31/12/2025, hiệu lực 15/02/2026, triển khai 01/01/2027, căn cứ NĐ 214/2025/NĐ-CP về Luật Đấu thầu) → nếu cần biểu diễn, dùng extension riêng trong package procurement, KHÔNG dùng extension này.

Số lưu hành (registration number) của thiết bị y tế tại Việt Nam.

Căn cứ pháp lý: NĐ 98/2021/NĐ-CP Điều 21 (Phân nhóm số lưu hành), Chương III (Điều 17-33) về đăng ký lưu hành TBYT, đã được sửa đổi, bổ sung bởi NĐ 07/2023/NĐ-CP (03/03/2023) và NĐ 04/2025/NĐ-CP (hiệu lực 01/01/2025).

Phân nhóm theo NĐ 98/2021 Điều 21:

1. Loại A & B — Số công bố tiêu chuẩn áp dụng (Sở Y tế tỉnh/TP tiếp nhận):

   • Format: [STT tiếp nhận]/[Năm tiếp nhận 2 số]/[Mã ký hiệu Sở Y tế]-PCBA (loại A)
   • Format: [STT tiếp nhận]/[Năm tiếp nhận 2 số]/[Mã ký hiệu Sở Y tế]-PCBB (loại B)
   • PCBA/PCBB = Phiếu công bố loại A / loại B
   • Ví dụ: 2300001/23/HN-PCBA (Hồ sơ số 1 năm 2023, Sở Y tế Hà Nội tiếp nhận)

2. Loại C & D — Số Giấy chứng nhận đăng ký lưu hành (Bộ Y tế cấp):

   • Format chuẩn: [STT cấp]/[Năm cấp 2 số]/BYT-ĐKLH
   • Format rút gọn: [STT cấp]/BYT-ĐKLH
   • ĐKLH = Đăng ký lưu hành
   • Ví dụ: 2300055/BYT-ĐKLH hoặc 2300055/23/BYT-ĐKLH

Phạm vi:

• Bắt buộc cho loại B/C/D trước khi đưa ra thị trường
• Loại A chỉ công bố tiêu chuẩn áp dụng (vẫn dùng PCBA format)
• Đây là định danh ở mức sản phẩm/model/regulatory context, KHÔNG phải định danh per-instance

Lưu ý phân biệt: Extension này độc lập với:

• UDI (định danh per-instance theo HL7 best practice)
• MA_VAT_TU (mã nghiệp vụ BHYT theo QĐ 3176)
• Serial number (per-instance physical)
• Mã tài sản BV (internal facility code)

Cờ boolean phân biệt TBYT IVD (chẩn đoán in vitro: sinh phẩm, thuốc thử, máy xét nghiệm) với TBYT thông thường theo VBHN 08/2026/VBHN-BYT. Tùy chọn — chỉ đặt khi cần phân biệt rõ trong ngữ cảnh đăng ký lưu hành/đấu thầu/BHYT.

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.

Unique instance identifiers assigned to a device by manufacturers other organizations or owners.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

Mã vật tư/thiết bị y tế dùng trong XML dữ liệu đầu ra KCB và thanh toán BHYT. Mapping QĐ 3176/QĐ-BYT: MA_VAT_TU. Đây là mã nghiệp vụ/legacy; không phải UDI, serial number, số lưu hành hoặc mã tài sản. Khi mã này được dùng như product/service code của dòng chi phí, ưu tiên biểu diễn ở Claim.item.productOrService.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

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.

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.

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.

Số serial khi hệ thống trao đổi dưới dạng Identifier. Device.serialNumber vẫn là vị trí FHIR chính để ghi serial number.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

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

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

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

The purpose of this identifier.

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

Identifies the purpose for this identifier, if known .

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

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

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

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

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

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

Identifier.system is always case sensitive.

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

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

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

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

Organization that issued/manages the identifier.

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

The reference to the definition for the device.

Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.

UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.

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

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

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

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

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

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

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

The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.

Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include :

1. GS1: http://hl7.org/fhir/NamingSystem/gs1-di,
2. HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI,
3. ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di,
4. ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di.

The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi.

Allows a recipient of a UDI to know which database will contain the UDI-associated metadata.

The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats SHALL be base64 encoded.

The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.

If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

A coded entry to indicate how the data was entered.

Codes to identify how UDI data was entered.

Supports a way to distinguish hand entered from machine read data.

Status of the Device availability.

This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.

The availability status of the device.

Reason for the dtatus of the Device availability.

The availability status reason of the device.

The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product.

For example, this applies to devices in the United States regulated under Code of Federal Regulation 21CFR§1271.290(c).

Tên hãng sản xuất. Các QĐ 5086/QĐ-BYT, 637/2022, 1844/2022, 3181/2022 liên quan mã hãng sản xuất VTYT/TBYT; không model thành mã hàng TBYT đầy đủ trong v0.3.

The date and time when the device was manufactured.

The date and time beyond which this device is no longer valid or should not be used (if applicable).

Lot number assigned by the manufacturer.

The serial number assigned by the organization when the device was manufactured.

Alphanumeric Maximum 20.

This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.

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

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

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

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

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

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

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

The name of the device.

The type of deviceName. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName.

The type of name the device is referred by.

The model number for the device.

The part number of the device.

Alphanumeric Maximum 20.

Loại thiết bị cấy ghép, nên mã hóa bằng SNOMED CT hoặc hệ danh pháp thiết bị đã được governance. Chưa required binding vào QĐ 847/QĐ 3107 trong v0.4.

Codes to identify medical devices.

The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication.

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

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

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

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

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

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

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

The standard that is used to operate and communicate.

The version of the standard that is used to operate and communicate.

The actual design of the device or software version running on the device.

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

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

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

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

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

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

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

The type of the device version.

A single component of the device version.

The version text.

The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.

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.

Code that specifies the property DeviceDefinitionPropetyCode (Extensible).

Property value as a quantity.

Property value as a code, e.g., NTP4 (synced to NTP).

Bệnh nhân gắn với thiết bị cấy ghép. Đây là điểm khác với VNCoreDevice nền, vốn vẫn hỗ trợ thiết bị chưa gắn người bệnh hoặc vật tư/thiết bị trong dữ liệu thanh toán.

If the device is implanted in a patient, then need to associate the device to the patient.

An organization that is responsible for the provision and ongoing maintenance of the device.

Contact details for an organization or a particular human that is responsible for the device.

used for troubleshooting etc.

The place where the device can be found.

Device.location can be used to track device location.

A network address on which the device may be contacted directly.

If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.

Descriptive information, usage information or implantation information that is not captured in an existing element.

Provides additional safety characteristics about a medical device. For example devices containing latex.

The parent device.