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

## : S.3.5 Manage PHR Output (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.3.5"/>
      <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>S.3.5#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 render reports consisting of all or part of an individual’s PHR.</p>
    </div></span>

                    Satisfied by:<ol>

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

                    </ol>

                </td>
            </tr>

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

                    <span>S.3.5#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 determine the records or reports that are considered the formal health record for disclosure purposes.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.5#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 conform to function RI.1 (Manage Record Lifecycle and Lifespan) to ensure that updates to unstructured Health Record Information are tracked.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.5#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 conform to function RI.1 (Manage Record Lifecycle and Lifespan) to ensure that updates to Structured Health Record Information are tracked.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.5#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 provide the ability to render hardcopy and electronic report summary information (e.g., procedures, medications, laboratory results, immunizations, allergies, or vital signs).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.5#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 render reports in both chronological and specified records elements order.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.3.5"/>
      <version value="0.1.0"/>
      <name value="S_3_5_Manage_PHR_Output"/>
      <title value="S.3.5 Manage PHR Output (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 request PHR output which may include standard and ad hoc reports in hardcopy or electronic formats. This output may be for the PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing of the PHR information for any purposes the PHR Account Holder deems appropriate."/>
      <statement>
        <key value="PHRSFMR2-S.3.5-01"/>
        <label value="S.3.5#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render reports consisting of all or part of an individual’s PHR."/>
        <satisfiedBy value="https://www.hl7.org/fhir/bundle.html"/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.5-02"/>
        <label value="S.3.5#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to determine the records or reports that are considered the formal health record for disclosure purposes."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.5-03"/>
        <label value="S.3.5#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function RI.1 (Manage Record Lifecycle and Lifespan) to ensure that updates to unstructured Health Record Information are tracked."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.5-04"/>
        <label value="S.3.5#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function RI.1 (Manage Record Lifecycle and Lifespan) to ensure that updates to Structured Health Record Information are tracked."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.5-05"/>
        <label value="S.3.5#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render hardcopy and electronic report summary information (e.g., procedures, medications, laboratory results, immunizations, allergies, or vital signs)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.5-06"/>
        <label value="S.3.5#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render reports in both chronological and specified records elements order."/>
      </statement>
    </Requirements>