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.5.6 Manage Updated Orders, Recommendations, or Alternative Care Plans (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.5.6"/>
      <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.5.6#01</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 updated orders, updated recommendations, and/or alternative care plans.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.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 manage updated orders (e.g., by presenting updated recommendations for medication regimens based on new findings related to a physician's diagnosis, or by presenting updated recommended laboratory monitoring protocols with respect to the use of a particular medication (e.g., by presenting a recommendation to send a blood sample to the laboratory every two days when using insulin)).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.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 manage updated recommendations (e.g., by presenting recommendations for medication regimens based on findings related to a physician's diagnosis).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.5.6#04</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 alternative treatments (or proposed alternative treatments) (e.g., by presenting alternative treatments in medications on the basis of updated practice standards, updated costs, updated formularies, and/or updated protocols).</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.5.6"/>
      <version value="0.1.0"/>
      <name
            value="PH_5_6_Manage_Updated_Orders__Recommendations__or_Alternative_Care_Plans"/>
      <title
             value="PH.5.6 Manage Updated Orders, Recommendations, or Alternative Care Plans (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 might need to receive updated orders or recommendations from care team members; or receive alternative care plan recommendations as the PHR Account Holder's conditions (or goals) change or when different modalities-of-care are recommended or chosen; or as elements of the PHR Account Holder's care plan change. For example, a physician might recommend an alternate drug if the physician notices that the price of the currently-prescribed drug increases dramatically or that the current drug is proving to be less effective than previously experienced. By accepting this new drug, the PHR Account Holder might then need to reconfigure the PHR system to present reminders for the PHR Account Holder to take the medication every third day instead of once-a-week."/>
      <statement>
        <key value="PHRSFMR2-PH.5.6-01"/>
        <label value="PH.5.6#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage updated orders, updated recommendations, and/or alternative care plans."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.5.6-02"/>
        <label value="PH.5.6#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage updated orders (e.g., by presenting updated recommendations for medication regimens based on new findings related to a physician's diagnosis, or by presenting updated recommended laboratory monitoring protocols with respect to the use of a particular medication (e.g., by presenting a recommendation to send a blood sample to the laboratory every two days when using insulin))."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.5.6-03"/>
        <label value="PH.5.6#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage updated recommendations (e.g., by presenting recommendations for medication regimens based on findings related to a physician's diagnosis)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.5.6-04"/>
        <label value="PH.5.6#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage alternative treatments (or proposed alternative treatments) (e.g., by presenting alternative treatments in medications on the basis of updated practice standards, updated costs, updated formularies, and/or updated protocols)."/>
      </statement>
    </Requirements>