HL7 Electronic Health Record System Functional Model, Release 2.1.1
            
            2.1.1 - 
  
            
          
HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/mvdzel/ehrsfm-fhir-r5/ and changes regularly. 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 Active as of 2025-10-31 | Computable Name: TI_2_1_2_Security_Audit_Triggers | |||
Manage 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 
                
             | 
            
                
                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.  |