<status value="active"/> <date value="2025-12-19T08:44:27+00:00"/> <publisher value="HL7 International / Electronic Health Records"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/ehr"/> </telecom> </contact> <description value="Manage Record Entry Audit Triggers"/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="US"/> </coding> </jurisdiction> <purpose value="Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function [RI.1](Requirements-DHFPR2-RI.1.html), Record Lifecycle."/> <derivedFrom value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.2.1.1"/> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-TI.2.1.1-01"/> <label value="TI.2.1.1#01"/> <conformance value="SHALL"/> <conditionality value="false"/> <requirement value="The system SHALL conform to function [RI.1](Requirements-DHFPR2-RI.1.html) (Record Lifecycle) and its RI.1.x.1 Subsections to capture and maintain Record Entry Audit Metadata."/> <derivedFrom value="TI.2.1.1#1"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-TI.2.1.1-02"/> <label value="TI.2.1.1#02"/> <conformance value="SHALL"/> <conditionality value="false"/> <requirement value="The system SHALL link an Audit Log Entry to each Record Entry according to scope of practice, organizational policy, and/or jurisdictional law."/> <derivedFrom value="TI.2.1.1#2"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-TI.2.1.1-03"/> <label value="TI.2.1.1#03"/> <conformance value="SHALL"/> <conditionality value="false"/> <requirement value="The system SHALL harmonize Audit Log Entry Metadata and corresponding Record Entry Metadata to ensure they remain identical."/> <derivedFrom value="TI.2.1.1#3"/> </statement> </Requirements>

Description I:

Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function RI.1, Record Lifecycle.

Criteria N:

TI.2.1.1#01

SHALL

The system SHALL conform to function RI.1 (Record Lifecycle) and its RI.1.x.1 Subsections to capture and maintain Record Entry Audit Metadata.

TI.2.1.1#02

SHALL dependent

The system SHALL link an Audit Log Entry to each Record Entry according to scope of practice, organizational policy, and/or jurisdictional law.

TI.2.1.1#03

SHALL

The system SHALL harmonize Audit Log Entry Metadata and corresponding Record Entry Metadata to ensure they remain identical.