HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

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/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

## : Trust Infrastructure

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-TI"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMSection"/>
      </meta>
      <language value="en"/>
      <text>
        <status value="extensions"/>
        <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">

        <div id="actors"><b>Actors:</b> <div><p>Many TI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many TI functions occur in the background without end user intervention. Other actors may interact more directly with TI functions: System Administrators (to manage and monitor system operations, configurations, backups, etc.), Security Administrators (to implement security policies for authentication, authorization, access control, audit, identity and signatures, etc.).</p></div></div>

        <table id="statements" class="grid dict">

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
        <valueCode value="normative"/>
      </extension>
      <extension
                 url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-actors">
        <valueString
                     value="Many TI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many TI functions occur in the background without end user intervention. Other actors may interact more directly with TI functions: System Administrators (to manage and monitor system operations, configurations, backups, etc.), Security Administrators (to implement security policies for authentication, authorization, access control, audit, identity and signatures, etc.)."/>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI"/>
      <version value="2.1.1"/>
      <name value="Trust_Infrastructure"/>
      <title value="Trust Infrastructure"/>
      <status value="active"/>
      <date value="2025-12-13T09:06:06+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="The Trust Infrastructure (TI) Section consists of functions common to an EHR System infrastructure, particularly those functions foundational to system operations, security, efficiency and data integrity assurance, safeguards for privacy and confidentiality, and interoperability with other systems. TI functions are core and foundational to all other functions of the Model (Care Provision, Care Provision Support, Population Health, Administrative Support and Record Infrastructure). Note extensive reference to TI functions in Overarching Criteria. TI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Trust Infrastructure Section have an identifier starting with &quot;TI&quot;.

    Example(s):
    Care Provision (CP) and Care Provision Support (CPS) functions must operate in a secure electronic environment. For example, Trust Infrastructure functions provide a secure environment for the CP immunization registration query function. Subsequently a CP function reports (transmits) the child's immunization event in a secure manner via another TI exchange function. TI functions also transparently provide other essential services, such as periodic backups of a child's health record and an audit trail of all accesses to that record."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
    </Requirements>