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.3 Registry and Directory Services (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-TI.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.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 manage internal registry services and directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#02</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 exchange information with external registry services and directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#03</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 exchange information securely with external registry services and directories.</p>
    </div></span>

                </td>
            </tr>

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

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

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL conform to function [[TI.5.1]] (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#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 capture and render local registry services and directory information through standards-based interfaces.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#06</span>

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

                    <span>SHOULD</span>

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

                    <span><div><p>IF the system communicates with external registry services and directories (i.e., external to a PHR-S), THEN the system SHOULD capture and render information using standards-based interfaces.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#07</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 determine the unique identity of a patient through the use of internal, and/or external registry services or directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#08</span>

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

                    <span>MAY</span>

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

                    <span><div><p>The system MAY provide the ability to determine links to healthcare information regarding a patient through the use of internal, and/or external registry services or directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#09</span>

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

                    <span>MAY</span>

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

                    <span><div><p>The system MAY provide the ability to determine the unique identity of a provider through the use of internal, and/or external registry services or directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#10</span>

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

                    <span>MAY</span>

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

                    <span><div><p>The system MAY provide the ability to determine the identity of payers, health plans and sponsors for administrative or financial purposes through the use of internal, and/or external registry services or directories.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.3#11</span>

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

                    <span>MAY</span>

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

                    <span><div><p>The system MAY provide the ability to determine the identity of employers for administrative or financial purposes through the use of internal, and/or external registry services or directories.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-TI.3"/>
      <version value="0.1.0"/>
      <name value="TI_3_Registry_and_Directory_Services"/>
      <title value="TI.3 Registry and Directory Services (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="Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across a PHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, a PHR-S for use within an application. This applies to directories/registries internal to the PHR-S as well as directories/registries external to the PHR-S. Transmission may occur automatically or manually and may include small or large amounts of data. Directories and registries support communication between PHR Systems and may be organized hierarchically or in a federated fashion. For example, a patient being treated by a primary care physician for a chronic condition may become ill while out of town. The new provider's PHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote PHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules.

    An example of local registry usage is a PHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data."/>
      <statement>
        <key value="PHRSFMR2-TI.3-01"/>
        <label value="TI.3#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage internal registry services and directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-02"/>
        <label value="TI.3#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to exchange information with external registry services and directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-03"/>
        <label value="TI.3#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to exchange information securely with external registry services and directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-04"/>
        <label value="TI.3#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [[TI.5.1]] (Application and Structured-Document Interchange Standards) to exchange information with external registry services and directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-05"/>
        <label value="TI.3#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD capture and render local registry services and directory information through standards-based interfaces."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-06"/>
        <label value="TI.3#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the system communicates with external registry services and directories (i.e., external to a PHR-S), THEN the system SHOULD capture and render information using standards-based interfaces."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-07"/>
        <label value="TI.3#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to determine the unique identity of a patient through the use of internal, and/or external registry services or directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-08"/>
        <label value="TI.3#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to determine links to healthcare information regarding a patient through the use of internal, and/or external registry services or directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-09"/>
        <label value="TI.3#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to determine the unique identity of a provider through the use of internal, and/or external registry services or directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-10"/>
        <label value="TI.3#10"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to determine the identity of payers, health plans and sponsors for administrative or financial purposes through the use of internal, and/or external registry services or directories."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-TI.3-11"/>
        <label value="TI.3#11"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to determine the identity of employers for administrative or financial purposes through the use of internal, and/or external registry services or directories."/>
      </statement>
    </Requirements>