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

## : PH.6.3 Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.6.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>PH.6.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 capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.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 manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination)).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#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 capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.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 provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.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 render to the PHR Account Holder a notification of the arrival of a provider-originated communication.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#06</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 exchange communications between providers and PHR Account Holders using a secure connection.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#07</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 PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#08</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 TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#09</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 tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#10</span>

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

                    <span>SHOULD</span>

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

                    <span><div><p>IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.3#11</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 transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.6.3"/>
      <version value="0.1.0"/>
      <name
            value="PH_6_3_Communications_Between_Provider_and_PHR_Account_Holder_and_or_PHR_Account_Holder_Proxy"/>
      <title
             value="PH.6.3 Communications Between Provider and PHR Account Holder and/or PHR Account Holder Proxy (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="The PHR Account Holder may fulfill specific requests for data or obtain requested diagnostic studies prior to the formal encounter. This may include providing PHR-S access to the new provider. The provider could also communicate with various members of the PHR Account Holder's care team.

    Example(s): The PHR Account Holder MAY fill out a current Review Of Systems (ROS) template questionnaire and specific chief complaint related questions as part of the History of Present Illness (HPI) prior to the encounter."/>
      <statement>
        <key value="PHRSFMR2-PH.6.3-01"/>
        <label value="PH.6.3#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and maintain communications between providers and the PHR Account Holder and/or the PHR Account Holder's Proxy according to organizational policy and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-02"/>
        <label value="PH.6.3#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage scanned documents based on the document type (e.g., based on the quality, format, origin, completion status, or intended diagnostic use (e.g., a screening versus a diagnostic breast examination))."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-03"/>
        <label value="PH.6.3#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain communications (e.g., date, entity, or details of communication) that were originated by the PHR Account Holder or Authorized PHR User."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-04"/>
        <label value="PH.6.3#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture, maintain and render PHR authorization information (e.g., to support a designee's claim that the designee is authorized to receive PHR Account Holder-related health information)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-05"/>
        <label value="PH.6.3#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD render to the PHR Account Holder a notification of the arrival of a provider-originated communication."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-06"/>
        <label value="PH.6.3#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to exchange communications between providers and PHR Account Holders using a secure connection."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-07"/>
        <label value="PH.6.3#07"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to PH.6.3 (Communication Between Provider and PHR Account Holder and/or the PHR Account Holder's Representative) in order to exchange information."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-08"/>
        <label value="PH.6.3#08"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to TI.1.8 (Patient Privacy and Confidentiality) to support adherence to various levels of confidentiality when exchanging information."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-09"/>
        <label value="PH.6.3#09"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to tag a set of elements within the PHR Account Holder's self-generated care plan that the PHR Account Holder intends to send to selected care team members."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-10"/>
        <label value="PH.6.3#10"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the PHR Account Holder is creating a self-generated care plan, THEN the system SHOULD provide the ability for the PHR Account Holder to tag a set of selected care team members (to whom the PHR Account Holder intends to send certain information)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.3-11"/>
        <label value="PH.6.3#11"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to transmit a tagged set of elements within the PHR Account Holder's self-generated care plan to a tagged set of selected care team members."/>
      </statement>
    </Requirements>