<?xml version="1.0" encoding="UTF-8"?>

<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-TI.2.1.3"/>
  <meta>
    <profile value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/><div xmlns="http://www.w3.org/1999/xhtml">
    
    
    <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> System Audit Triggers are designed to capture system related events, both routine and exceptional, including key metadata (who, what, when, where, why).</div>
    
    
    
    <div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
    
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#01
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHOULD provide the ability to log system maintenance events for loading new versions of, or changes to, the clinical system.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#02
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHOULD provide the ability to store system maintenance events for loading new versions of codes and knowledge bases.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#03
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHOULD provide the ability to log system maintenance events for creating and restoring of backup.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#04
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHOULD provide the ability to audit events in the case of detection of corrupt or dirty data.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#05
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL provide the ability to audit the access and usage of systems, data, and organizational resources.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#06
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL provide the ability to log system events at the hardware and software architecture level.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#07
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL provide the ability to log system maintenance events for entry to, and exit from, the PHR system.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1.3#08
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL provide the ability to log system maintenance events for remote access connections including those for system support and maintenance activities for security and access purposes.
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <url value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.2.1.3"/>
  <version value="2.0.1"/>
  <name value="TI_2_1_3_System_Audit_Triggers"/>
  <title value="TI.2.1.3 System Audit Triggers (Function)"/>
  <status value="active"/>
  <date value="2026-06-23T23:02:24+10:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description value="Manage System Audit Triggers"/>
  <purpose value="System Audit Triggers are designed to capture system related events, both routine and exceptional, including key metadata (who, what, when, where, why)."/>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-01"/>
    <label value="TI.2.1.3#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement value="The system SHOULD provide the ability to log system maintenance events for loading new versions of, or changes to, the clinical system."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-02"/>
    <label value="TI.2.1.3#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement value="The system SHOULD provide the ability to store system maintenance events for loading new versions of codes and knowledge bases."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-03"/>
    <label value="TI.2.1.3#03"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement value="The system SHOULD provide the ability to log system maintenance events for creating and restoring of backup."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-04"/>
    <label value="TI.2.1.3#04"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement value="The system SHOULD provide the ability to audit events in the case of detection of corrupt or dirty data."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-05"/>
    <label value="TI.2.1.3#05"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement value="The system SHALL provide the ability to audit the access and usage of systems, data, and organizational resources."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-06"/>
    <label value="TI.2.1.3#06"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement value="The system SHALL provide the ability to log system events at the hardware and software architecture level."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-07"/>
    <label value="TI.2.1.3#07"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement value="The system SHALL provide the ability to log system maintenance events for entry to, and exit from, the PHR system."/>
  </statement>
  <statement>
    <extension url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1.3-08"/>
    <label value="TI.2.1.3#08"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement value="The system SHALL provide the ability to log system maintenance events for remote access connections including those for system support and maintenance activities for security and access purposes."/>
  </statement>
</Requirements>