HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative
This page is part of the HL7 Electronic Health Record System Functional Model, Release 2.1.1 (v2.1.1: Normative 1 - Normative) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.2.1.2 | Version: 2.1.1 | ||||
| Standards status: Normative | Computable Name: TI_2_1_2_Security_Audit_Triggers | ||||
Manage Security Audit Triggers
Security Audit Triggers are designed to capture security related events, both routine and exceptional, including key metadata (who, what, when, where, why).
| 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 | SHALL dependent |
The system SHALL audit key events according to scope of practice, organizational policy, and/or jurisdictional law. |
| TI.2.1.2#03 | SHALL dependent |
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 | SHALL dependent |
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. |