ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local International flag

Publish Box goes here

Requirements: TI.2.1 Audit Triggers (Function)

Active as of 2024-11-26
Statement N:

Manage Audit Triggers

 Description I:

EHR Systems have built in audit triggers to capture key events in real-time. Audit triggers signal key:

  • Record management and lifecycle events;
  • Security events related to system and data safeguards, both routine and exceptional;
  • System events related to performance and operations, both routine and exceptional.
  • Clinical events with special log requirements.
 Criteria N:
TI.2.1#01 dependent SHALL

The system SHALL audit key events, as specified in function [[TI.2.1]] (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1#02 dependent SHALL

The system SHALL capture key Audit Metadata at each Audit Trigger, as specified in [[TI.2.1]] (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1#03 dependent SHALL

The system SHALL capture an Audit Log Entry at each Audit Trigger as specified in [[TI.2.1]] (Audit Triggers) according to scope of practice, organizational policy, and/or jurisdictional law.
TI.2.1#04 SHALL

The system SHALL capture the current master clock time to establish valid record date and time metadata.
TI.2.1#05 MAY

The system MAY manage Audit Trigger logging using a common audit engine (e.g., using schema and transports such as specified in the Audit Log specification of IHE Audit Trails and Node Authentication (ATNA) Profile).