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

Publication Build: This will be filled in by the publication tooling

## : TI.5.4 Interchange Agreements (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-TI.5.4"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Support the use of Interchange Agreements to specify the rules, responsibilities, expectations, and methods by which Interchange Agreement partners may exchange information.</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Systems that wish to communicate with each other must agree on certain parameters/criteria that will govern an information exchange process. Interchange agreements enable partnering systems to discover, negotiate, and utilize those parameters/criteria. An EHR-S can use this information to define how data will be exchanged between the sending and the receiving partners. Interchange services and capabilities can be discovered in an automated fashion.</p>
    <p>Entity directories can be used to determine the address, profile, and data exchange requirements of known, and/or potential Interchange Agreement partners. Entity registries can be used to determine the security, addressing, and reliability requirements between potential Interchange Agreement partnering systems.
    Example:
    Examples of services that may be provided by the use of Interchange Agreements:</p>
    <ul>
    <li>A new application can automatically determine the source of a patient's demographic information by using a Universal Description and Discovery Integration (UDDI) service. The new application can then retrieve the Web Services Description Language (WSDL) specification to discover the binding details.</li>
    <li>Good Health Hospital, a member of AnyCounty LabNet, shares laboratory results with other partners. Good Health Hospital periodically queries LabNet's directory (UDDI) to determine whether new information providers have joined LabNet. When new information providers are discovered, the Good Health Hospital IT system establishes the appropriate service connections based upon the Service Description (WSDL).</li>
    <li>A clinical research sponsor submits an interchange agreement to a registry. Various EHR systems access that registry to discover the clinical research sponsor's contact information.</li>
    </ul>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

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

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.5.4#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHALL exchange information with Interchange Agreement partners based on interoperability agreement descriptions.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.5.4#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <i>conditional</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF an interchange agreement description specifies the use of a certain standard, THEN the system SHOULD exchange information using the standard specified by the interchange agreement description according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.5.4#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY conform to function <a href="Requirements-EHRSFMR2-TI.3.html">TI.3</a> (Registry and Directory Services) to interact with registries, and/or directories to determine the address, profile, and data exchange requirements of known, and/or potential partners.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.5.4#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY analyze and present interchange service descriptions and capabilities according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>TI.5.4#05</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage Interchange Agreements that have been established with Interchange Agreement partners.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <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.4"/>
      <version value="2.1.1-ballot"/>
      <name value="TI_5_4_Interchange_Agreements"/>
      <title value="TI.5.4 Interchange Agreements (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:04:36+11: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 the use of Interchange Agreements to specify the rules, responsibilities, expectations, and methods by which Interchange Agreement partners may exchange information."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Systems that wish to communicate with each other must agree on certain parameters/criteria that will govern an information exchange process. Interchange agreements enable partnering systems to discover, negotiate, and utilize those parameters/criteria. An EHR-S can use this information to define how data will be exchanged between the sending and the receiving partners. Interchange services and capabilities can be discovered in an automated fashion.

    Entity directories can be used to determine the address, profile, and data exchange requirements of known, and/or potential Interchange Agreement partners. Entity registries can be used to determine the security, addressing, and reliability requirements between potential Interchange Agreement partnering systems.
    Example:
    Examples of services that may be provided by the use of Interchange Agreements:
    - A new application can automatically determine the source of a patient's demographic information by using a Universal Description and Discovery Integration (UDDI) service. The new application can then retrieve the Web Services Description Language (WSDL) specification to discover the binding details.
    - Good Health Hospital, a member of AnyCounty LabNet, shares laboratory results with other partners. Good Health Hospital periodically queries LabNet's directory (UDDI) to determine whether new information providers have joined LabNet. When new information providers are discovered, the Good Health Hospital IT system establishes the appropriate service connections based upon the Service Description (WSDL).
    - A clinical research sponsor submits an interchange agreement to a registry. Various EHR systems access that registry to discover the clinical research sponsor's contact information."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-TI.5.4-01"/>
        <label value="TI.5.4#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL exchange information with Interchange Agreement partners based on interoperability agreement descriptions."/>
        <derivedFrom value="EHR-S_FM_R1.1 IN.5.4#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-TI.5.4-02"/>
        <label value="TI.5.4#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF an interchange agreement description specifies the use of a certain standard, THEN the system SHOULD exchange information using the standard specified by the interchange agreement description according to scope of practice, organizational policy, and/or jurisdictional law."/>
        <derivedFrom value="EHR-S_FM_R1.1 IN.5.4#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-TI.5.4-03"/>
        <label value="TI.5.4#03"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY conform to function [TI.3](Requirements-EHRSFMR2-TI.3.html) (Registry and Directory Services) to interact with registries, and/or directories to determine the address, profile, and data exchange requirements of known, and/or potential partners."/>
        <derivedFrom value="EHR-S_FM_R1.1 IN.5.4#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-TI.5.4-04"/>
        <label value="TI.5.4#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY analyze and present interchange service descriptions and capabilities according to scope of practice, organizational policy, and/or jurisdictional law."/>
        <derivedFrom value="EHR-S_FM_R1.1 IN.5.4#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-TI.5.4-05"/>
        <label value="TI.5.4#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage Interchange Agreements that have been established with Interchange Agreement partners."/>
      </statement>
    </Requirements>