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 ATNA (RFC 3881).

Identifies the name, action type, time, and disposition of the audited event.

The event must be identified.

Identifier for a family of the event.

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

e.g., a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Identifier for the category of event.

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

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

This broadly indicates what kind of action was done on the Participant Object.

The time when the event occurred on the source.

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.

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

Indicates whether the event succeeded or failed.

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.

A free text description of the outcome of the event.

A person, a hardware device or software process.

The event has one or more active participants.

There may be more than one user per event, for example, in cases of actions initiated by one user for other users, or in events that involve more than one user, hardware device, or system process. However, only one user may be the initiator/requestor for the event.

Specification of the role(s) the user plays when performing the event. Usually the codes used in this element are local codes defined by the role-based access control security system used in the local context.

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.

Direct reference to a resource that identifies the participant.

This field ties an audit event to a specific resource.

Unique identifier for the user actively participating in the event.

This field ties an audit event to a specific user.

a unique value within the Audit Source ID. For node-based authentication -- where only the system hardware or process, but not a human user, is identified -- User ID would be the node name.

Alternative Participant 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 user.

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.

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.

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

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.

This value is used retrospectively to determine the authorization policies.

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.

Type of media involved. 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.

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

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.

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

An identifier for the type of network access point that originated 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.

Application systems and processes.

The event is reported by one source.

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.

Logical source location within the healthcare enterprise network.

This value differentiates among the sites in a multi-site enterprise health information system.

a hospital or other provider location within a multi-entity provider group.

Identifier of the source where the event originated.

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

Code specifying the type of source where event originated.

This field indicates which type of source is identified by the Audit Source ID. It is an optional value that may be used to group events for analysis according to the type of source where the event occurred.

Specific instances of data or objects that have been accessed.

The event may have other objects involved.

required unless the values for Event Identification, Active Participant Identification, and Audit Source Identification are sufficient to document the entire auditable event. Because events may have more than one participant object, this group can be a repeating set of values.

Identifies a specific instance of the participant object. The reference should always be version specific.

Identifier details depends on object type.

Identifies a specific instance of the participant object. The reference should always be version specific.

Object type being audited.

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.

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

Code representing the functional application role of Participant Object being audited.

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

See RFC 3881 for rules concerning matches between role and type.

Identifier for the data life-cycle stage for the participant object.

Institutional policies for privacy and security may optionally fall under different accountability rules based on data life cycle. This provides a differentiating value for those cases.

This can be used to provide an audit trail for data, over time, as it passes through the system.

Denotes policy-defined sensitivity for the Participant Object ID such as VIP, HIV status, mental health status or similar topics.

This field identifies a specific instance of an object, such as a patient, to detect/track privacy and security issues.

Values from ATNA are institution- and implementation-defined text strings (in sensitivity.text). HL7 defines confidentiality codes for records, documents etc. that can also be used here.

An instance-specific descriptor of the Participant Object ID audited, such as a person's name.

This field may be used in a query/report to identify audit events for a specific person, e.g., where multiple synonymous Participant Object IDs (patient number, medical record number, encounter number, etc.) have been used.

Text that describes the object in more detail.

The actual query for a query-type participant object.

For query events it may be necessary to capture the actual query input to the query process in order to identify the specific event. Because of differences among query implementations and data encoding for them, this is a base 64 encoded data blob. It may be subsequently decoded or interpreted by downstream audit analysis processing.

Additional Information about the Object.

Name of the property.

Property value.