HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

: TI.2.1 Audit Triggers (Function)

Page standards status: Normative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-TI.2.1"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
  </meta>
  <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> PHR 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.</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#01
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL audit key events, as specified in function [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1#02
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL capture key Audit Metadata at each Audit Trigger, as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1#03
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL capture an Audit Log Entry at each Audit Trigger as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) according to scope of practice, organizational policy, and/or jurisdictional law.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1#04
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                The system SHALL capture the current master clock time to establish valid record date and time metadata.
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            TI.2.1#05
            </td>
            <td style="padding-left: 4px;">
            MAY
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                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).
                
            </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"/>
  <version value="2.0.1"/>
  <name value="TI_2_1_Audit_Triggers"/>
  <title value="TI.2.1 Audit Triggers (Function)"/>
  <status value="active"/>
  <date value="2026-06-23T08:11:09+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description value="Manage Audit Triggers"/>
  <purpose
           value="PHR 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."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1-01"/>
    <label value="TI.2.1#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL audit key events, as specified in function [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1-02"/>
    <label value="TI.2.1#02"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL capture key Audit Metadata at each Audit Trigger, as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) and child functions, according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="true"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1-03"/>
    <label value="TI.2.1#03"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL capture an Audit Log Entry at each Audit Trigger as specified in [TI.2.1](Requirements-PHRSFMR2-TI.2.1.html) (Audit Triggers) according to scope of practice, organizational policy, and/or jurisdictional law."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1-04"/>
    <label value="TI.2.1#04"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL capture the current master clock time to establish valid record date and time metadata."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-TI.2.1-05"/>
    <label value="TI.2.1#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="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)."/>
  </statement>
</Requirements>