A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. If the element is present, it must have either a @value, an @id, or extensions Partitions the audit event into one or more categories that can be used to filter searching, to govern access control and/or to guide system behavior. Describes what happened. The most specific codes for the event. Indicator for type of action performed during the event that generated the audit. Indicates and enables segmentation of various severity including debugging from critical. The time or period during which the activity occurred. The time when the event was recorded. Indicates whether the event succeeded or failed. A free text descripiton can be given in outcome.text. The authorization (e.g., PurposeOfUse) that was used during the event being recorded. Allows tracing of authorization for the events and tracking whether proposals/recommendations were acted upon. The patient element is available to enable deterministic tracking of activities that involve the patient as the subject of the data used in an activity. This will typically be the encounter the event occurred, but some events MAY be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission lab tests). An actor taking an active role in the event or activity that is logged. The actor that is reporting the event. Specific instances of data or objects that have been accessed. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. Indicates whether the event succeeded or failed. Additional details about the error. This MAY be a text description of the error or a system code that identifies the error. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. The Functional Role of the user when performing the event. The structural roles of the agent indicating the agent's competency. The security role enabling the agent with respect to the activity. Reference to who this agent is that was involved in the event. Indicator that the user is or is not the requestor, or initiator, for the event being audited. Where the agent location is known, the agent location when the event occurred. Where the policy(ies) are known that authorized the agent participation in the event. 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. When the event utilizes a network there SHOULD be an agent describing the local system, and an agent describing remote system, with the network interface details. The authorization (e.g., PurposeOfUse) that was used during the event being recorded. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. Logical source location within the healthcare enterprise network. For example, a hospital or other provider location within a multi-entity provider group. Identifier of the source where the event was detected. Code specifying the type of source where event originated. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. Identifies a specific instance of the entity. The reference SHOULD be version specific. This is allowed to be a Parameters resource. Code representing the role the entity played in the event being audited. Security labels for the identified entity. Text that describes the entity in more detail. The query parameters for a query-type entities. Tagged value pairs for conveying additional information about the entity. The entity is attributed to an agent to express the agent's responsibility for that entity in the activity. This is most used to indicate when persistence media (the entity) are used by an agent. For example when importing data from a device, the device would be described in an entity, and the user importing data from that media would be indicated as the entity.agent. A record of an event relevant for purposes such as operations, privacy, security, maintenance, and performance analysis. The name of extra detail provided in the value. This element is the tag for the value. Where a simple string is used for the tag name, use the CodeableConcept.display element. The value of the extra detail. Create Read Update Delete Execute Indicator for type of action performed during the event that generated the event. If the element is present, it must have either a @value, an @id, or extensions Emergency Alert Critical Error Warning Notice Informational Debug The severity of the audit entry. If the element is present, it must have either a @value, an @id, or extensions