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.3 Care-Related Decision Support (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download



<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-PH.5.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.5.3#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 render information regarding health guidelines and best practices.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.3#02</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 PHR Account Holder the ability to analyze health data and context-driven assessments in comparison to practice standards in order to prompt additional testing, possible diagnoses, or adjunctive treatment.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.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 from an authoritative source (e.g., provider EHR-S or a care management PHR-S) rules related to abnormal trends.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.3#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 PHR Account Holder the ability to analyze health data and context-driven assessments in comparison to practice standards in order to prompt additional testing, possible diagnoses, or adjunctive treatment.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.3#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 PHR Account Holder the ability to analyze assessment data in correlation with the data in the PHR Account Holder's problem list.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.3#06</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY render a notification to the PHR Account Holder to request additional assessments, testing, or adjunctive treatment.</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.3#07</span>
                
            </td>
            <td style="padding-left: 4px;">
                
                <span>MAY</span>
                
            </td>
            <td style="padding-left: 4px;" class="requirement">
                
                <span><div><p>The system MAY render a notification to the PHR Account Holder to follow a provider-designated care plan related to assessment results (e.g., peak flow results, blood glucose readings, weight, or blood pressure).</p>
</div></span>
                

                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>PH.5.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 integrate health information contained in the PHR with appropriate health education materials (e.g., consumer self-identified as a smoker vis-à-vis smoking cessation materials sent to the PHR-S).</p>
</div></span>
                

                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.5.3"/>
  <version value="0.1.0"/>
  <name value="PH_5_3_Care_Related_Decision_Support"/>
  <title value="PH.5.3 Care-Related Decision Support (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 system should aid the PHR Account Holder with making his or her self-assessments and treatment plans for self-care. Some decision support algorithms are straightforward and can be provided as part of the PHR-S service. Others may be more complex and are detailed in function PH.5.4 (Integration with Third Party Clinical Decision Support Services). For example, a child's weight and height can be plotted on a growth curve chart which graphically displays growth progress. Another example, is the ability for a pregnant woman to plot weight changes over time against a norm."/>
  <statement>
    <key value="PHRSFMR2-PH.5.3-01"/>
    <label value="PH.5.3#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to render information regarding health guidelines and best practices."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-02"/>
    <label value="PH.5.3#02"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the PHR Account Holder the ability to analyze health data and context-driven assessments in comparison to practice standards in order to prompt additional testing, possible diagnoses, or adjunctive treatment."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-03"/>
    <label value="PH.5.3#03"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture from an authoritative source (e.g., provider EHR-S or a care management PHR-S) rules related to abnormal trends."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-04"/>
    <label value="PH.5.3#04"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the PHR Account Holder the ability to analyze health data and context-driven assessments in comparison to practice standards in order to prompt additional testing, possible diagnoses, or adjunctive treatment."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-05"/>
    <label value="PH.5.3#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the PHR Account Holder the ability to analyze assessment data in correlation with the data in the PHR Account Holder's problem list."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-06"/>
    <label value="PH.5.3#06"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY render a notification to the PHR Account Holder to request additional assessments, testing, or adjunctive treatment."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-07"/>
    <label value="PH.5.3#07"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY render a notification to the PHR Account Holder to follow a provider-designated care plan related to assessment results (e.g., peak flow results, blood glucose readings, weight, or blood pressure)."/>
  </statement>
  <statement>
    <key value="PHRSFMR2-PH.5.3-08"/>
    <label value="PH.5.3#08"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to integrate health information contained in the PHR with appropriate health education materials (e.g., consumer self-identified as a smoker vis-à-vis smoking cessation materials sent to the PHR-S)."/>
  </statement>
</Requirements>