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

## : TI.5.1 Application, Structured-Message, and Structured-Document Interchange Standards (Header)

Page standards status: Normative

Raw xml | Download

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

        <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Since a health care organization typically has various external and internal interoperability requirements, it must use a set of corresponding interoperability or interchange standards that will meet its connectivity and information structure, format, and semantic requirements. Information should be exchanged -- and applications should provide functionality -- in a manner that appears to be seamless to the user. To be specific, if data is received from an external source that requires a user to manually copy-and-paste that data into multiple parts of the system, the exchange is not considered to be &quot;seamless&quot;.</p>
    <p>Examples of standards-based EHR information content and exchange methods include: standards-based data extracts, standards-based messages, standards-based documents (e.g., HL7 Clinical Document Architecture (CDA) documents), standards-based healthcare transactions, and standards-based images (e.g., Digital Imaging and Communication in Medicine (DICOM) documents).</p>
    <p>Support for multiple interaction modes is needed to respond to differing levels of immediacy and types of exchange. For example, messaging is effective for many near-real time, asynchronous data exchange scenarios but may not be appropriate if the end-user is requesting an immediate response from a remote application.
    A variety of interaction modes are typically supported such as:</p>
    <ul>
    <li>Unsolicited Notifications (e.g., Adam Everyman has arrived at the clinic for his scheduled appointment);</li>
    <li>Query/Response (e.g., Query: Is Adam Everyman known to the system? Response: Yes, Adam's medical record number is 12345678);</li>
    <li>Service Request and Response (e.g., Request: Laboratory Order for “Fasting Blood Sugar”. Response: the results of the test);</li>
    <li>Information Interchange between organizations (e.g., in a regional health exchange or in a national health system);</li>
    <li>Structured/discrete clinical documents (e.g., a structured clinical note);</li>
    <li>Unstructured clinical document (e.g., dictated surgical note).</li>
    </ul>
    <p>Standard terminology is a fundamental part of interoperability and is described in function <a href="Requirements-EHRSFMR2-TI.4.html">TI.4</a>. Using a formal explicit information model further optimizes interoperability. An example of an information model is the HL7 Reference Information Model (RIM). Organizations typically need to deal with more than one information model and may need to develop a mapping between information models, a meta-model (that helps to explain and organize the various information models), or both.</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/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.5.1"/>
      <version value="2.1.1"/>
      <name
            value="TI_5_1_Application__Structured_Message__and_Structured_Document_Interchange_Standards"/>
      <title
             value="TI.5.1 Application, Structured-Message, and Structured-Document Interchange Standards (Header)"/>
      <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="Support an EHR system's ability to operate seamlessly with systems that adhere to recognized application interchange standards. These systems include other EHR systems, subcomponents of an EHR system, or other (authorized, non-EHR) systems."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Since a health care organization typically has various external and internal interoperability requirements, it must use a set of corresponding interoperability or interchange standards that will meet its connectivity and information structure, format, and semantic requirements. Information should be exchanged -- and applications should provide functionality -- in a manner that appears to be seamless to the user. To be specific, if data is received from an external source that requires a user to manually copy-and-paste that data into multiple parts of the system, the exchange is not considered to be &quot;seamless&quot;.

    Examples of standards-based EHR information content and exchange methods include: standards-based data extracts, standards-based messages, standards-based documents (e.g., HL7 Clinical Document Architecture (CDA) documents), standards-based healthcare transactions, and standards-based images (e.g., Digital Imaging and Communication in Medicine (DICOM) documents).

    Support for multiple interaction modes is needed to respond to differing levels of immediacy and types of exchange. For example, messaging is effective for many near-real time, asynchronous data exchange scenarios but may not be appropriate if the end-user is requesting an immediate response from a remote application.
    A variety of interaction modes are typically supported such as:
    - Unsolicited Notifications (e.g., Adam Everyman has arrived at the clinic for his scheduled appointment);
    - Query/Response (e.g., Query: Is Adam Everyman known to the system? Response: Yes, Adam's medical record number is 12345678);
    - Service Request and Response (e.g., Request: Laboratory Order for “Fasting Blood Sugar”. Response: the results of the test);
    - Information Interchange between organizations (e.g., in a regional health exchange or in a national health system);
    - Structured/discrete clinical documents (e.g., a structured clinical note);
    - Unstructured clinical document (e.g., dictated surgical note).

    Standard terminology is a fundamental part of interoperability and is described in function [TI.4](Requirements-EHRSFMR2-TI.4.html). Using a formal explicit information model further optimizes interoperability. An example of an information model is the HL7 Reference Information Model (RIM). Organizations typically need to deal with more than one information model and may need to develop a mapping between information models, a meta-model (that helps to explain and organize the various information models), or both."/>
    </Requirements>