Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## : TI.5.3 Standards-Based Application Integration (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-TI.5.3"/>
      <meta>
        <profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <table id="statements" class="grid dict">

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

                    <span>TI.5.3#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 provide the ability to integrate applications in a standards-based fashion when the system is composed of, and/or is extended by disparate applications.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.5.3#02</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 integrate user (or system) authentication for the purposes application context management (e.g., Graphical User Interface application integration via HL7's Context Management Standard from the Clinical Context Object Work Group (CCOW)).</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-TI.5.3"/>
      <version value="0.1.0"/>
      <name value="TI_5_3_Standards_Based_Application_Integration"/>
      <title value="TI.5.3 Standards-Based Application Integration (Function)"/>
      <status value="active"/>
      <date value="2024-01-31T14:45:34+00:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="A PHR-S often consists of multiple applications. Some of those applications may be within the PHR-S; others may be external to the PHR-S. The user of the PHR-S often benefits when those applications are integrated. Application integration can be accomplished in an ad-hoc fashion or in a standards-based fashion.

    The method(s) by which applications may be integrated within an organization depends on that organization's approach to application integration. A given organization could conceivably employ multiple application integration approaches to meet various application integration requirements."/>
      <statement>
        <key value="PHRSFMR2-TI.5.3-01"/>
        <label value="TI.5.3#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to integrate applications in a standards-based fashion when the system is composed of, and/or is extended by disparate applications."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.5.3-02"/>
        <label value="TI.5.3#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to integrate user (or system) authentication for the purposes application context management (e.g., Graphical User Interface application integration via HL7's Context Management Standard from the Clinical Context Object Work Group (CCOW))."/>
      </statement>
    </Requirements>