A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage.

Based on IHE-ATNA.

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ã căn cứ xử lý không qua đồng ý. Nghĩa vụ chứng minh trực tiếp thuộc điểm a; các điểm còn lại vẫn cần hồ sơ trách nhiệm giải trình, giám sát và biện pháp bảo vệ phù hợp. / Coded basis for processing without consent. The direct burden to demonstrate applicability belongs to point (a); the other grounds remain subject to applicable accountability, oversight, and safeguard records.

Thời hạn lưu hồ sơ sự cố vi phạm dữ liệu cá nhân, ghi trên AuditEvent của chính sự cố đó.

Phạm vi hẹp — đọc kỹ trước khi dùng. Căn cứ NĐ 356/2025/NĐ-CP Điều 29 khoản 1 điểm c: 'Tổ chức phải lưu hồ sơ vi phạm trong thời gian tối thiểu 5 năm kể từ ngày khắc phục xong sự cố' — và điều khoản này áp cho hồ sơ sự cố liên quan dữ liệu vị trí và dữ liệu sinh trắc học, không phải cho nhật ký truy cập nói chung.

Vì vậy extension này CHỈ dùng trên AuditEvent ghi nhận một sự cố vi phạm thuộc phạm vi trên. KHÔNG dùng làm thời hạn lưu trữ chung cho mọi nhật ký truy cập: thời hạn lưu nhật ký là chính sách ở cấp hệ thống và cấp phân loại dữ liệu, gắn một khoảng thời gian tuỳ ý lên mọi AuditEvent vừa sai căn cứ vừa làm tăng lượng dữ liệu phải giữ.

Trước 0.10.0, phần mô tả có câu 'khuyến nghị mặc định 5 năm cho mọi loại DLCN nhạy cảm' — đó là mở rộng quá phạm vi điều khoản, đã gỡ (kiểm toán 31/07/2026 — analysis/77 mục C1).

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 a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Type of event.

This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed.

Identifier for the category of event.

This field enables queries of messages by implementation-defined event categories.

Loại thao tác của sự kiện. RÀ 07/09/2026: đã thử siết lên 1..1 với lập luận đây là thành phần hoạt động trong định nghĩa nhật ký hệ thống của Luật 116/2025/QH15 Điều 2 khoản 11 — Codex và Fable cùng bác, và bác đúng: Điều 2 khoản 11 định nghĩa tập hợp các bản ghi, không đặt nghĩa vụ trường cho từng bản ghi, còn nghĩa vụ nhật ký duy nhất của Luật (Điều 25 khoản 2 điểm b) chỉ áp cho doanh nghiệp cung cấp dịch vụ viễn thông, Internet. Trả lại 0..1 MS.

Indicator for type of action performed during the event that generated the event.

This broadly indicates what kind of action was done on the AuditEvent.entity by the AuditEvent.agent.

Thời điểm ghi nhận sự kiện audit — KHÔNG phải mốc bắt đầu nghĩa vụ thông báo vi phạm. Cần đủ chính xác để phục vụ điều tra, làm nguồn xác định 'thời điểm phát hiện vi phạm' (mốc tính 72 giờ theo Luật 91/2025/QH15 Điều 23 khoản 1 — biểu diễn trong hồ sơ thông báo vi phạm, xem VNCoreCompositionBreachNotification) và lưu vết an ninh mạng theo Luật 116/2025/QH15 (hiệu lực từ 01/07/2026).

In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.

This ties an event to a specific date and time. Security audits typically require a consistent time base (e.g. UTC), to eliminate time-zone issues arising from geographical distribution.

Theo pattern BALP: 0 biểu diễn quyết định permit thành công; mã khác 0 biểu diễn deny/failure và outcomeDesc NÊN giải thích lý do. Đây là quy ước AuditEvent của profile, không phải mã do pháp luật quy định. / Following BALP, 0 records a successful permit decision; a non-zero code records deny/failure and outcomeDesc SHOULD explain why.

In some cases a "success" may be partial, for example, an incomplete or interrupted transfer of a radiological study. For the purpose of establishing accountability, these distinctions are not relevant.

Indicates whether the event succeeded or failed.

PurposeOfUse là trục nghiệp vụ tách biệt với processingLegalBasis. Dùng BTG chỉ khi người dùng thực sự vượt qua policy/quyền thông thường; ETREAT cho mục đích điều trị khẩn cấp; ERTREAT cho quyền thường trực của khoa cấp cứu theo policy. / PurposeOfUse is separate from legal basis. Use BTG only for a real override, ETREAT for emergency treatment, and ERTREAT for normally provisioned emergency-department access.

Use AuditEvent.agent.purposeOfUse when you know that it is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

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.

Chủ thể thực hiện. RÀ 07/09/2026: đã thử siết lên 1..1 dựa trên QĐ 425/QĐ-BYT rồi trả lại 0..1 vì hai lý do độc lập — QĐ 425/QĐ-BYT chỉ điều chỉnh Hệ thống đơn thuốc Quốc gia chứ không phải mọi hệ thống KCB (Codex, Fable), và siết min cũng KHÔNG đạt mục tiêu: fixture âm ExampleAuditEventReadNoTraceability chỉ khai who.display là một chuỗi tên người vẫn thoả 1..1 mà không truy ngược được về tài khoản nào. Khả năng truy vết do invariant vn-audit-data-access-traceable canh, không phải do cardinality.

Where a User ID is available it will go into who.identifier.

This field ties an audit event to a specific resource or identifier.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Logical network location for application activity, if the activity has a network location.

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.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

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.

Specification of the participation type the user plays when performing the event.

The Participation type of the agent to the event.

Requester con người được biểu diễn bằng Practitioner hoặc PractitionerRole; requester hệ thống/tổ chức được biểu diễn bằng Device hoặc VNCoreOrganization. Phạm vi này hỗ trợ cả tác nhân trực tiếp và tác nhân vận hành đối với các trường hợp Điều 19 khoản 1 điểm b, c, d, đ. / A human requester is represented by Practitioner or PractitionerRole; a system or organizational requester is represented by Device or VNCoreOrganization. This supports both direct and operational requesters for Article 19(1)(b), (c), (d), and (đ) cases.

Where a User ID is available it will go into who.identifier.

This field ties an audit event to a specific resource or identifier.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Logical network location for application activity, if the activity has a network location.

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 reason (purpose of use), specific to this agent, that was used during the event being recorded.

Use AuditEvent.agent.purposeOfUse when you know that is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

The reason the activity took place.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

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.

Specification of the participation type the user plays when performing the event.

The Participation type of the agent to the event.

Chủ thể thực hiện. RÀ 07/09/2026: đã thử siết lên 1..1 dựa trên QĐ 425/QĐ-BYT rồi trả lại 0..1 vì hai lý do độc lập — QĐ 425/QĐ-BYT chỉ điều chỉnh Hệ thống đơn thuốc Quốc gia chứ không phải mọi hệ thống KCB (Codex, Fable), và siết min cũng KHÔNG đạt mục tiêu: fixture âm ExampleAuditEventReadNoTraceability chỉ khai who.display là một chuỗi tên người vẫn thoả 1..1 mà không truy ngược được về tài khoản nào. Khả năng truy vết do invariant vn-audit-data-access-traceable canh, không phải do cardinality.

Where a User ID is available it will go into who.identifier.

This field ties an audit event to a specific resource or identifier.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Tối thiểu hai URI: (1) một URI điều luật có fragment đến đúng điều-khoản-điểm, theo convention urn:vn-law:91-2025-qh15#dieu-19-khoan-1-diem-a; và (2) một URI chính sách PDP nội bộ có version bất biến, ví dụ urn:vn-policy:example-hospital:emergency-access:version-3. / At least two URIs: one statute URI with an article-clause-point fragment and one immutable, versioned local PDP-policy URI.

For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.

This value is used retrospectively to determine the authorization policies.

Logical network location for application activity, if the activity has a network location.

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.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

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.

Specification of the participation type the user plays when performing the event.

The Participation type of the agent to the event.

Chủ thể thực hiện. RÀ 07/09/2026: đã thử siết lên 1..1 dựa trên QĐ 425/QĐ-BYT rồi trả lại 0..1 vì hai lý do độc lập — QĐ 425/QĐ-BYT chỉ điều chỉnh Hệ thống đơn thuốc Quốc gia chứ không phải mọi hệ thống KCB (Codex, Fable), và siết min cũng KHÔNG đạt mục tiêu: fixture âm ExampleAuditEventReadNoTraceability chỉ khai who.display là một chuỗi tên người vẫn thoả 1..1 mà không truy ngược được về tài khoản nào. Khả năng truy vết do invariant vn-audit-data-access-traceable canh, không phải do cardinality.

Where a User ID is available it will go into who.identifier.

This field ties an audit event to a specific resource or identifier.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Logical network location for application activity, if the activity has a network location.

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.

Hệ thống hoặc đơn vị phát sinh log. Log phục vụ truy vết xử lý dữ liệu y tế số theo NĐ 102/2025/NĐ-CP; bối cảnh an ninh mạng theo Luật 116/2025/QH15 (Luật không đặt nghĩa vụ log riêng cho cơ sở KCB — xem phần phạm vi ở đầu profile) (hiệu lực từ 01/07/2026).

Since multi-tier, distributed, or composite applications make source identification ambiguous, this collection of fields may repeat for each application or process actively involved in the event. For example, multiple value-sets can identify participating web servers, application processes, and database server threads in an n-tier distributed application. Passive event participants (e.g. low-level network transports) need not be identified.

The event is reported by one source.

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.

Identifier of the source where the event was detected.

This field ties the event to a specific source system. It may be used to group events for analysis according to where the event was detected.

Specific instances of data or objects that have been accessed.

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

The event may have other entities involved.

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.

Identifies a specific instance of the entity. The reference should be version specific.

Specific instances of data or objects that have been accessed.

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

The event may have other entities involved.

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.

Identifies a specific instance of the entity. The reference should be version specific.

The type of the object that was involved in this audit event.

This value is distinct from the user's role or any user relationship to the entity.

Code for the entity type involved in the audit event.

To describe the object being acted upon. In addition to queries on the subject of the action in an auditable event, it is also important to be able to query on the object type for the action.

Code representing the role the entity played in the event being audited.

Code representing the role the entity played in the audit event.

For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves.

Specific instances of data or objects that have been accessed.

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

The event may have other entities involved.

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.

Identifies a specific instance of the entity. The reference should be version specific.

The type of the object that was involved in this audit event.

This value is distinct from the user's role or any user relationship to the entity.

Code for the entity type involved in the audit event.

To describe the object being acted upon. In addition to queries on the subject of the action in an auditable event, it is also important to be able to query on the object type for the action.

Code representing the role the entity played in the event being audited.

Code representing the role the entity played in the audit event.

For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves.

Specific instances of data or objects that have been accessed.

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

The event may have other entities involved.

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.

Identifies a specific instance of the entity. The reference should be version specific.

The type of the object that was involved in this audit event.

This value is distinct from the user's role or any user relationship to the entity.

Code for the entity type involved in the audit event.

To describe the object being acted upon. In addition to queries on the subject of the action in an auditable event, it is also important to be able to query on the object type for the action.

Code representing the role the entity played in the event being audited.

Code representing the role the entity played in the audit event.

For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves.

Mã căn cứ xử lý không qua đồng ý. Nghĩa vụ chứng minh trực tiếp thuộc điểm a; các điểm còn lại vẫn cần hồ sơ trách nhiệm giải trình, giám sát và biện pháp bảo vệ phù hợp. / Coded basis for processing without consent. The direct burden to demonstrate applicability belongs to point (a); the other grounds remain subject to applicable accountability, oversight, and safeguard records.

Theo pattern BALP: 0 biểu diễn quyết định permit thành công; mã khác 0 biểu diễn deny/failure và outcomeDesc NÊN giải thích lý do. Đây là quy ước AuditEvent của profile, không phải mã do pháp luật quy định. / Following BALP, 0 records a successful permit decision; a non-zero code records deny/failure and outcomeDesc SHOULD explain why.

PurposeOfUse là trục nghiệp vụ tách biệt với processingLegalBasis. Dùng BTG chỉ khi người dùng thực sự vượt qua policy/quyền thông thường; ETREAT cho mục đích điều trị khẩn cấp; ERTREAT cho quyền thường trực của khoa cấp cứu theo policy. / PurposeOfUse is separate from legal basis. Use BTG only for a real override, ETREAT for emergency treatment, and ERTREAT for normally provisioned emergency-department access.

Requester con người được biểu diễn bằng Practitioner hoặc PractitionerRole; requester hệ thống/tổ chức được biểu diễn bằng Device hoặc VNCoreOrganization. Phạm vi này hỗ trợ cả tác nhân trực tiếp và tác nhân vận hành đối với các trường hợp Điều 19 khoản 1 điểm b, c, d, đ. / A human requester is represented by Practitioner or PractitionerRole; a system or organizational requester is represented by Device or VNCoreOrganization. This supports both direct and operational requesters for Article 19(1)(b), (c), (d), and (đ) cases.

Tối thiểu hai URI: (1) một URI điều luật có fragment đến đúng điều-khoản-điểm, theo convention urn:vn-law:91-2025-qh15#dieu-19-khoan-1-diem-a; và (2) một URI chính sách PDP nội bộ có version bất biến, ví dụ urn:vn-policy:example-hospital:emergency-access:version-3. / At least two URIs: one statute URI with an article-clause-point fragment and one immutable, versioned local PDP-policy URI.

A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage.

Based on IHE-ATNA.

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ã căn cứ xử lý không qua đồng ý. Nghĩa vụ chứng minh trực tiếp thuộc điểm a; các điểm còn lại vẫn cần hồ sơ trách nhiệm giải trình, giám sát và biện pháp bảo vệ phù hợp. / Coded basis for processing without consent. The direct burden to demonstrate applicability belongs to point (a); the other grounds remain subject to applicable accountability, oversight, and safeguard records.

Thời hạn lưu hồ sơ sự cố vi phạm dữ liệu cá nhân, ghi trên AuditEvent của chính sự cố đó.

Phạm vi hẹp — đọc kỹ trước khi dùng. Căn cứ NĐ 356/2025/NĐ-CP Điều 29 khoản 1 điểm c: 'Tổ chức phải lưu hồ sơ vi phạm trong thời gian tối thiểu 5 năm kể từ ngày khắc phục xong sự cố' — và điều khoản này áp cho hồ sơ sự cố liên quan dữ liệu vị trí và dữ liệu sinh trắc học, không phải cho nhật ký truy cập nói chung.

Vì vậy extension này CHỈ dùng trên AuditEvent ghi nhận một sự cố vi phạm thuộc phạm vi trên. KHÔNG dùng làm thời hạn lưu trữ chung cho mọi nhật ký truy cập: thời hạn lưu nhật ký là chính sách ở cấp hệ thống và cấp phân loại dữ liệu, gắn một khoảng thời gian tuỳ ý lên mọi AuditEvent vừa sai căn cứ vừa làm tăng lượng dữ liệu phải giữ.

Trước 0.10.0, phần mô tả có câu 'khuyến nghị mặc định 5 năm cho mọi loại DLCN nhạy cảm' — đó là mở rộng quá phạm vi điều khoản, đã gỡ (kiểm toán 31/07/2026 — analysis/77 mục C1).

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 a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Type of event.

This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed.

Identifier for the category of event.

This field enables queries of messages by implementation-defined event categories.

Loại thao tác của sự kiện. RÀ 07/09/2026: đã thử siết lên 1..1 với lập luận đây là thành phần hoạt động trong định nghĩa nhật ký hệ thống của Luật 116/2025/QH15 Điều 2 khoản 11 — Codex và Fable cùng bác, và bác đúng: Điều 2 khoản 11 định nghĩa tập hợp các bản ghi, không đặt nghĩa vụ trường cho từng bản ghi, còn nghĩa vụ nhật ký duy nhất của Luật (Điều 25 khoản 2 điểm b) chỉ áp cho doanh nghiệp cung cấp dịch vụ viễn thông, Internet. Trả lại 0..1 MS.

Indicator for type of action performed during the event that generated the event.

This broadly indicates what kind of action was done on the AuditEvent.entity by the AuditEvent.agent.

The period during which the activity occurred.

The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

Thời điểm ghi nhận sự kiện audit — KHÔNG phải mốc bắt đầu nghĩa vụ thông báo vi phạm. Cần đủ chính xác để phục vụ điều tra, làm nguồn xác định 'thời điểm phát hiện vi phạm' (mốc tính 72 giờ theo Luật 91/2025/QH15 Điều 23 khoản 1 — biểu diễn trong hồ sơ thông báo vi phạm, xem VNCoreCompositionBreachNotification) và lưu vết an ninh mạng theo Luật 116/2025/QH15 (hiệu lực từ 01/07/2026).

In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.

This ties an event to a specific date and time. Security audits typically require a consistent time base (e.g. UTC), to eliminate time-zone issues arising from geographical distribution.

Theo pattern BALP: 0 biểu diễn quyết định permit thành công; mã khác 0 biểu diễn deny/failure và outcomeDesc NÊN giải thích lý do. Đây là quy ước AuditEvent của profile, không phải mã do pháp luật quy định. / Following BALP, 0 records a successful permit decision; a non-zero code records deny/failure and outcomeDesc SHOULD explain why.

In some cases a "success" may be partial, for example, an incomplete or interrupted transfer of a radiological study. For the purpose of establishing accountability, these distinctions are not relevant.

Indicates whether the event succeeded or failed.

A free text description of the outcome of the event.

PurposeOfUse là trục nghiệp vụ tách biệt với processingLegalBasis. Dùng BTG chỉ khi người dùng thực sự vượt qua policy/quyền thông thường; ETREAT cho mục đích điều trị khẩn cấp; ERTREAT cho quyền thường trực của khoa cấp cứu theo policy. / PurposeOfUse is separate from legal basis. Use BTG only for a real override, ETREAT for emergency treatment, and ERTREAT for normally provisioned emergency-department access.

Use AuditEvent.agent.purposeOfUse when you know that it is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

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.

Specification of the participation type the user plays when performing the event.

The Participation type of the agent to the event.

The security role that the user was acting under, that come from local codes defined by the access control security system (e.g. RBAC, ABAC) used in the local context.

Should be roles relevant to the event. Should not be an exhaustive list of roles.

What security role enabled the agent to participate in the event.

This value ties an audited event to a user's role(s). It is an optional value that might be used to group events for analysis by user functional role categories.

Chủ thể thực hiện. RÀ 07/09/2026: đã thử siết lên 1..1 dựa trên QĐ 425/QĐ-BYT rồi trả lại 0..1 vì hai lý do độc lập — QĐ 425/QĐ-BYT chỉ điều chỉnh Hệ thống đơn thuốc Quốc gia chứ không phải mọi hệ thống KCB (Codex, Fable), và siết min cũng KHÔNG đạt mục tiêu: fixture âm ExampleAuditEventReadNoTraceability chỉ khai who.display là một chuỗi tên người vẫn thoả 1..1 mà không truy ngược được về tài khoản nào. Khả năng truy vết do invariant vn-audit-data-access-traceable canh, không phải do cardinality.

Where a User ID is available it will go into who.identifier.

This field ties an audit event to a specific resource or identifier.

Alternative agent Identifier. For a human, this should be a user identifier text string from authentication system. This identifier would be one known to a common authentication system (e.g. single sign-on), if available.

In some situations, a human user may authenticate with one identity but, to access a specific application system, may use a synonymous identify. For example, some "single sign on" implementations will do this. The alternative identifier would then be the original identify used for authentication, and the User ID is the one known to and used by the application.

Human-meaningful name for the agent.

The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Where the event occurred.

The policy or plan that authorized the activity being recorded. Typically, a single activity may have multiple applicable policies, such as patient consent, guarantor funding, etc. The policy would also indicate the security token used.

For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.

This value is used retrospectively to determine the authorization policies.

Type of media involved. Used when the event is about exporting/importing onto media.

Used when the event is about exporting/importing onto media.

Usually, this is used instead of specifying a network address. This field is not used for Media Id (i.e. the serial number of a CD).

Logical network location for application activity, if the activity has a network location.

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.

An identifier for the network access point of the user device for the audit event.

This could be a device id, IP address or some other identifier associated with a device.

This datum identifies the user's network access point, which may be distinct from the server that performed the action. It is an optional value that may be used to group events recorded on separate servers for analysis of a specific network access point's data access across all servers.

An identifier for the type of network access point that originated the audit event.

The type of network access point of this agent in the audit event.

This datum identifies the type of network access point identifier of the user device for the audit event. It is an optional value that may be used to group events recorded on separate servers for analysis of access according to a network access point's type.

The reason (purpose of use), specific to this agent, that was used during the event being recorded.

Use AuditEvent.agent.purposeOfUse when you know that is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

The reason the activity took place.

An actor taking an active role in the event or activity that is logged.

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.