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

## : PH.3.5.6 Manage Recommendations (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.3.5.6"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
      </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>Capture and track provider recommendations for future care.</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>In many care activities, recommendations are made for specific future activities. They are easy to let slip by and lose track of them. A thoughtful and documented reason for not following a particular recommendation should be captured to help manage liability risk. Some recommendations may be controversial and there are reasons not to follow them. It is useful to keep a list of recommendations as a separate check on future care to be managed with the help of the PHR Account Holder's provider.</p>
    <p>Example(s):</p>
    <ul>
    <li>The radiologist recommends a repeat mammogram in six months rather than the usual twelve months.</li>
    <li>The Primary Care Provider recommends seeing a surgeon for occasional gallbladder attacks.</li>
    <li>A screening colonoscopy is recommended after age fifty.</li>
    <li>Annual screening or tests based on the PHR Account Holder's occupational risk factors.</li>
    </ul>
    </div></span>

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

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

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

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

                    <span>PH.3.5.6#01</span>

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

                    <i>dependent</i>

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to capture recommendations from encounter and diagnostic studies in structured documents according to organizational policy and/or jurisdictional law (e.g., HIV results may need to be delayed from being sent directly to the PHR System, so that the provider has time to communicate with the patient directly).</p>
    </div></span>

                    Satisfied by:<ol>

                        <li><a href="https://www.hl7.org/fhir/communication.html">https://www.hl7.org/fhir/communication.html</a></li>

                    </ol>

                </td>
            </tr>

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

                    <span>PH.3.5.6#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 capture a recommendation, the identity of the recommending provider, the date of the recommendation, and the date suggested to perform the recommended action.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.3.5.6#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 link a recommendation entry with the corresponding original document (e.g., a recommendation to lose ten pounds should be linked to a document that contains the PHR Account Holder's most recent BMI readings).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.3.5.6#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 render a pending (or future) recommendation (e.g., so that a provider might be able to create a future-order or reminder, or to document the reason that the recommendation was dismissed).</p>
    </div></span>

                </td>
            </tr>

        </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-PH.3.5.6"/>
      <version value="2.0.1-ballot"/>
      <name value="PH_3_5_6_Manage_Recommendations"/>
      <title value="PH.3.5.6 Manage Recommendations (Function)"/>
      <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="Capture and track provider recommendations for future care."/>
      <purpose
               value="In many care activities, recommendations are made for specific future activities. They are easy to let slip by and lose track of them. A thoughtful and documented reason for not following a particular recommendation should be captured to help manage liability risk. Some recommendations may be controversial and there are reasons not to follow them. It is useful to keep a list of recommendations as a separate check on future care to be managed with the help of the PHR Account Holder's provider.

    Example(s):
    - The radiologist recommends a repeat mammogram in six months rather than the usual twelve months.
    - The Primary Care Provider recommends seeing a surgeon for occasional gallbladder attacks.
    - A screening colonoscopy is recommended after age fifty.
    - Annual screening or tests based on the PHR Account Holder's occupational risk factors."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-PH.3.5.6-01"/>
        <label value="PH.3.5.6#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture recommendations from encounter and diagnostic studies in structured documents according to organizational policy and/or jurisdictional law (e.g., HIV results may need to be delayed from being sent directly to the PHR System, so that the provider has time to communicate with the patient directly)."/>
        <satisfiedBy value="https://www.hl7.org/fhir/communication.html"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-PH.3.5.6-02"/>
        <label value="PH.3.5.6#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture a recommendation, the identity of the recommending provider, the date of the recommendation, and the date suggested to perform the recommended action."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-PH.3.5.6-03"/>
        <label value="PH.3.5.6#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to link a recommendation entry with the corresponding original document (e.g., a recommendation to lose ten pounds should be linked to a document that contains the PHR Account Holder's most recent BMI readings)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-PH.3.5.6-04"/>
        <label value="PH.3.5.6#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render a pending (or future) recommendation (e.g., so that a provider might be able to create a future-order or reminder, or to document the reason that the recommendation was dismissed)."/>
      </statement>
    </Requirements>