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

## : S.4.2 Registry Notification and Management (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.4.2"/>
      <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>S.4.2#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 conform to function TI.1.1 (Entity Authentication).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.4.2#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 conform to function TI.1.3 (Entity Access Control).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.4.2#03</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 information exchange and communication with registries.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.4.2#04</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 exchange demographic and clinical information with disease-specific registries (and other notifiable registries) according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.4.2#05</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 manage a pointer to PHR Account Holder registry information that might exist in a registry according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.4.2"/>
      <version value="0.1.0"/>
      <name value="S_4_2_Registry_Notification_and_Management"/>
      <title value="S.4.2 Registry Notification and Management (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="Support the automated transfer of formatted demographic and clinical information to disease-specific registries (and other notifiable registries) to enable PHR Account Holder to participate, if and as desired, in provider and public health monitoring and subsequent epidemiological analysis.

    The PHR Account Holder can export personal health information to disease-specific registries, other notifiable registries such as immunization registries, through standard data transfer protocols or messages. The PHR Account Holder can update and configure communication for new registries, or delete communication with an existing registry."/>
      <statement>
        <key value="PHRSFMR2-S.4.2-01"/>
        <label value="S.4.2#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function TI.1.1 (Entity Authentication)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.2-02"/>
        <label value="S.4.2#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function TI.1.3 (Entity Access Control)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.2-03"/>
        <label value="S.4.2#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage information exchange and communication with registries."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.2-04"/>
        <label value="S.4.2#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to exchange demographic and clinical information with disease-specific registries (and other notifiable registries) according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.2-05"/>
        <label value="S.4.2#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage a pointer to PHR Account Holder registry information that might exist in a registry according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law."/>
      </statement>
    </Requirements>