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

## : Record Infrastructure

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-RI"/>
      <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 RI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many RI functions occur in the background without end user intervention. Other actors may interact more directly with RI functions: System Administrators (to create archives of historical patient encounters or to purge records after their legal retention period has expired).</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 RI functions are performed transparently by EHR systems – at least from the perspective of users whose role is primarily clinical. Many RI functions occur in the background without end user intervention. Other actors may interact more directly with RI functions: System Administrators (to create archives of historical patient encounters or to purge records after their legal retention period has expired)."/>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI"/>
      <version value="2.1.1"/>
      <name value="Record_Infrastructure"/>
      <title value="Record 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 Record Infrastructure Section consists of functions common to EHR System record management, particularly those functions foundational to managing record lifecycle (origination, attestation, amendment, access/use, translation, transmittal/disclosure, receipt, de-identification, archive…) and record lifespan (persistence, indelibility, continuity, audit, encryption). RI functions are core and foundational to all other functions of the Model (CP, CPS, POP, AS). Note extensive reference to RI functions in Overarching Criteria. RI functions may be implemented within the architecture of a single system or across a tightly coupled suite of systems (applications).All functions within the Record Infrastructure Section have an identifier starting with “RI”.

    Example(s):
    Care Provision (CP) and Care Provision Support (CPS) functions are invoked by Actors taking Actions (i.e., caregivers documenting care provision). Most all Actions taken to support individual health or to provide healthcare are captured by the EHRS and persistently evidenced in the EHR record. For example, CP immunization administration functions create EHR record entries which must be persisted over time. These same entries form the basis for transmittal to central immunization registries."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
    </Requirements>