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

## : RI.1.1.13 Extract Record Lifecycle Event (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-RI.1.1.13"/>
      <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>RI.1.1.13#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 extract Record Entry content to produce subsets, derivations, summaries or aggregations according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#02</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 de-identify Record Entries during extraction in accordance with function [[RI.1.1.10]] (De-Identify Record Entries).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#03</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 extract Record Entry content based on queries with selection criteria, for example, key words, date/time range, full text search.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#04</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 extract metadata associated with Record Entry content.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#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 extract, with parameterized selection criteria, across the complete data set that constitutes all Record Entries for a patient.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#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 extract and present a full chronicle of the healthcare process from assembled Record Entries.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#07</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 extract and present a full chronicle of healthcare delivered to a patient from assembled Record Entries.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#08</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 extract Record Entry content for various purposes, including administrative, financial, research, quality analysis and public health.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#09</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 extract Record Entries for system migration.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#10</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 a set of over-riding parameters to exclude sensitive or privileged Record Entry content from extraction.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.13#11</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 extract unstructured Record Entry content and convert it into structured data.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-RI.1.1.13"/>
      <version value="0.1.0"/>
      <name value="RI_1_1_13_Extract_Record_Lifecycle_Event"/>
      <title value="RI.1.1.13 Extract Record Lifecycle Event (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="Occurs when an agent causes the system to selectively pull out a subset of record entry content, based on explicit criteria.

    Reference: ISO 21089-2018, Section 15.13."/>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-01"/>
        <label value="RI.1.1.13#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to extract Record Entry content to produce subsets, derivations, summaries or aggregations according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-02"/>
        <label value="RI.1.1.13#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to de-identify Record Entries during extraction in accordance with function [[RI.1.1.10]] (De-Identify Record Entries)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-03"/>
        <label value="RI.1.1.13#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to extract Record Entry content based on queries with selection criteria, for example, key words, date/time range, full text search."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-04"/>
        <label value="RI.1.1.13#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to extract metadata associated with Record Entry content."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-05"/>
        <label value="RI.1.1.13#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract, with parameterized selection criteria, across the complete data set that constitutes all Record Entries for a patient."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-06"/>
        <label value="RI.1.1.13#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract and present a full chronicle of the healthcare process from assembled Record Entries."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-07"/>
        <label value="RI.1.1.13#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract and present a full chronicle of healthcare delivered to a patient from assembled Record Entries."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-08"/>
        <label value="RI.1.1.13#08"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to extract Record Entry content for various purposes, including administrative, financial, research, quality analysis and public health."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-09"/>
        <label value="RI.1.1.13#09"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract Record Entries for system migration."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-10"/>
        <label value="RI.1.1.13#10"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage a set of over-riding parameters to exclude sensitive or privileged Record Entry content from extraction."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.13-11"/>
        <label value="RI.1.1.13#11"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to extract unstructured Record Entry content and convert it into structured data."/>
      </statement>
    </Requirements>