HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: TI.2.1.2 Security Audit Triggers (Function)

Page standards status: Informative

Statement N:

Manage Security Audit Triggers

Description I:

Security Audit Triggers are designed to capture security related events, both routine and exceptional, including key metadata (who, what, when, where, why).

Actors:
ehr Criteria N:

TI.2.1.2#01 | SHALL | The system SHALL provide the ability to enter the reason that access control functions are being overridden.
TI.2.1.2#02 | dependent SHALL | The system SHALL audit key events according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1.2#03 | dependent SHALL | The system SHALL capture key Audit Metadata at each Audit Trigger according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1.2#04 | dependent SHALL | The system SHALL capture an Audit Log Entry at each Audit Trigger according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1.2#05 | SHALL | The system SHALL provide the ability to log system maintenance events for entry to, and exit from, the EHR system.
TI.2.1.2#06 | MAY | The system MAY capture an Audit Log Entry at each Audit Trigger using a common audit engine, e.g., standards-based software.