HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

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

## : TI.5 Standards-Based Interoperability (Header) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-TI.5"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMHeader"/>
      </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>Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions.</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>Interoperability standards enable certain applications to be shared among PHR systems, resulting in a unified (logical) view of a given PHR system where several disparate systems may actually be participating transparently. Interoperability standards also enable certain information to be shared among PHR systems (including information that resides in regional, national, or international information exchanges). Interoperability standards also promote timely and efficient information capture, use, and re-use, often reducing the cumulative workload of the broad set of stakeholders.</p>
    <p>When health-related information is exchanged -- or when external applications are used to extend a PHR system -- the interoperability methods and underlying standards that were used in the process may need to be disclosed during a legal proceeding (especially when the resulting information becomes part of the patient's medical record).</p>
    </div></span>

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

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

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-TI.5"/>
      <version value="2.0.1-ballot"/>
      <name value="TI_5_Standards_Based_Interoperability"/>
      <title value="TI.5 Standards-Based Interoperability (Header)"/>
      <status value="active"/>
      <date value="2025-04-04T11:42:51+11:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions."/>
      <purpose
               value="Interoperability standards enable certain applications to be shared among PHR systems, resulting in a unified (logical) view of a given PHR system where several disparate systems may actually be participating transparently. Interoperability standards also enable certain information to be shared among PHR systems (including information that resides in regional, national, or international information exchanges). Interoperability standards also promote timely and efficient information capture, use, and re-use, often reducing the cumulative workload of the broad set of stakeholders.

    When health-related information is exchanged -- or when external applications are used to extend a PHR system -- the interoperability methods and underlying standards that were used in the process may need to be disclosed during a legal proceeding (especially when the resulting information becomes part of the patient's medical record)."/>
    </Requirements>