HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

: S.2.3 Manage Standard Reporting (Function)

Page standards status: Normative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="PHRSFMR2-S.2.3"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/>
    <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
    
    
    <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>PHR Account Holders may request standard, pre-configured, packaged reports. The purpose is not for PHR interchange but rather for PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing (if desired).</p>
</div></div>
    
    
    
    <div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
    
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
            S.2.3#01
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to render standard reports of structured clinical and administrative and financial data using either internal or external reporting tools.</p>
</div>
                Satisfied by:<ol>
                <li><a href="https://www.hl7.org/fhir/measure.html">https://www.hl7.org/fhir/measure.html</a></li>
                </ol>
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            S.2.3#02
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to maintain report parameters based on data sorted or filtered by the PHR Account Holder or by the PHR-S settings.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            S.2.3#03
            </td>
            <td style="padding-left: 4px;">
            MAY
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system MAY provide the ability to render information from unstructured clinical and administrative data in the report generation process using internal or external tools.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            S.2.3#04
            </td>
            <td style="padding-left: 4px;">
            MAY
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system (or an external application using data from the PHR-S) MAY provide the ability to maintain report parameters for generating subsequent reports.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            S.2.3#05
            </td>
            <td style="padding-left: 4px;">
            MAY
            
            
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system (or an external application using data from the PHR-S) MAY provide the ability to update one or more parameters of a saved report specification when generating a report using that specification.</p>
</div>
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="normative"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <url value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.2.3"/>
  <version value="2.0.1"/>
  <name value="S_2_3_Manage_Standard_Reporting"/>
  <title value="S.2.3 Manage Standard Reporting (Function)"/>
  <status value="active"/>
  <date value="2025-12-07T09:26:53+00:00"/>
  <publisher value="EHR WG"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Enable PHR Account Holders or authorized designees to request and read pre-configured, packaged reports of PHR information."/>
  <purpose
           value="PHR Account Holders may request standard, pre-configured, packaged reports. The purpose is not for PHR interchange but rather for PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing (if desired)."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.2.3-01"/>
    <label value="S.2.3#01"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to render standard reports of structured clinical and administrative and financial data using either internal or external reporting tools."/>
    <satisfiedBy value="https://www.hl7.org/fhir/measure.html"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.2.3-02"/>
    <label value="S.2.3#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to maintain report parameters based on data sorted or filtered by the PHR Account Holder or by the PHR-S settings."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.2.3-03"/>
    <label value="S.2.3#03"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to render information from unstructured clinical and administrative data in the report generation process using internal or external tools."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.2.3-04"/>
    <label value="S.2.3#04"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system (or an external application using data from the PHR-S) MAY provide the ability to maintain report parameters for generating subsequent reports."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="PHRSFMR2-S.2.3-05"/>
    <label value="S.2.3#05"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system (or an external application using data from the PHR-S) MAY provide the ability to update one or more parameters of a saved report specification when generating a report using that specification."/>
  </statement>
</Requirements>