HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

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

## : CPS.9.5 Ad Hoc Query and Rendering (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.9.5"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/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>Providers and administrators need to respond quickly to new requirements for data measurement and analysis. This need may result from new regulatory requirements or internal requirements. This need also requires that users be able to define and retain their own query parameters. The data being queried may be in either structured or unstructured data formats.</p>
    <p>Providers and administrators also need to query for the absence of specific clinical or administrative data. For example, the Quality Control department may desire to determine the level of adherence to the Diabetes Mellitus management protocol. If the protocol calls for the capture of fasting blood sugars information every 3 months at minimum, the investigator might need to perform a multi-patient query that identifies diabetic patients who do not show a Fasting Blood Sugar result within the last 3 months. Key time-related Emergency Department benchmarking reports include: arrival time; entrance-to-treatment-area time, doctor-to-patient contact time; decision-to-admit time, discharge or transfer time; and departure (from the Emergency Department) time. Important time intervals include, but are not limited to, the &quot;door-to-doctor time&quot;, &quot;doctor-to-dictation time&quot;, &quot;admission to bed availability or departure&quot;, and overall length of stay.</p>
    <p>A key feature of an electronic health record is its ability to support the delivery of care by enabling prior information to be found and meaningfully displayed. EHR systems should facilitate search, filtering (e.g., filtering by key word, tagged data, or diagnosis), summarization, and presentation of available data needed for patient care. Systems should enable views to be customized (e.g., specific data may be organized chronologically, by clinical category, or by consultant). The views may be arranged chronologically, by problem, or by other parameters, and may be filtered or sorted. Jurisdictional laws and organizational policies that prohibit certain users from accessing certain patient information must be supported.</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;">
                CPS.9.5#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 ad hoc query and reports of structured clinical and administrative data through either internal or external reporting tools.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#02
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to capture and render information extracted 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;">
                CPS.9.5#03
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to extract and transmit reports generated.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#04
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to capture and maintain report parameters, based on patient demographic, and/or clinical data, which would allow sorting, and/or filtering of the data.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#05
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to save report parameters for generating subsequent reports.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#06
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to edit one or more parameters of a saved report specification when generating a report using that specification.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#07
                </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 reports, using internal or external reporting tools, based on the absence of a clinical data element (e.g., a laboratory test has not been performed in the last year).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#08
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability for the patient to render [query] the financial data and the data about his or her health related accounts.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#09
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to present and transmit customized views of summarized information based on sort and filter controls for date or date range, problem, or other clinical parameters.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#10
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to present and transmit summarized information through customized views based on prioritization of chronology, problem, or other pertinent clinical parameters.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.9.5#11
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability for a provider to capture and maintain filters to search for previous events (e.g., encounters, reports, consults) meeting specified criteria.</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/ehrsfmr2/Requirements/EHRSFMR2-CPS.9.5"/>
      <version value="2.1.1"/>
      <name value="CPS_9_5_Ad_Hoc_Query_and_Rendering"/>
      <title value="CPS.9.5 Ad Hoc Query and Rendering (Function)"/>
      <status value="active"/>
      <date value="2025-12-13T09:06:06+00:00"/>
      <publisher value="HL7 International / Electronic Health Records"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="Provide support for ad hoc query and report generation using tools internal or external to the system. Present customized views and summarized information from a patient's comprehensive EHR subject to jurisdictional laws and organizational policies related to privacy and confidentiality. The view may be arranged chronologically, by problem, or other parameters, and may be filtered or sorted."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Providers and administrators need to respond quickly to new requirements for data measurement and analysis. This need may result from new regulatory requirements or internal requirements. This need also requires that users be able to define and retain their own query parameters. The data being queried may be in either structured or unstructured data formats.

    Providers and administrators also need to query for the absence of specific clinical or administrative data. For example, the Quality Control department may desire to determine the level of adherence to the Diabetes Mellitus management protocol. If the protocol calls for the capture of fasting blood sugars information every 3 months at minimum, the investigator might need to perform a multi-patient query that identifies diabetic patients who do not show a Fasting Blood Sugar result within the last 3 months. Key time-related Emergency Department benchmarking reports include: arrival time; entrance-to-treatment-area time, doctor-to-patient contact time; decision-to-admit time, discharge or transfer time; and departure (from the Emergency Department) time. Important time intervals include, but are not limited to, the &quot;door-to-doctor time&quot;, &quot;doctor-to-dictation time&quot;, &quot;admission to bed availability or departure&quot;, and overall length of stay.

    A key feature of an electronic health record is its ability to support the delivery of care by enabling prior information to be found and meaningfully displayed. EHR systems should facilitate search, filtering (e.g., filtering by key word, tagged data, or diagnosis), summarization, and presentation of available data needed for patient care. Systems should enable views to be customized (e.g., specific data may be organized chronologically, by clinical category, or by consultant). The views may be arranged chronologically, by problem, or by other parameters, and may be filtered or sorted. Jurisdictional laws and organizational policies that prohibit certain users from accessing certain patient information must be supported."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-01"/>
        <label value="CPS.9.5#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render ad hoc query and reports of structured clinical and administrative data through either internal or external reporting tools."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-02"/>
        <label value="CPS.9.5#02"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture and render information extracted from unstructured clinical and administrative data in the report generation process, using internal or external tools."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-03"/>
        <label value="CPS.9.5#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract and transmit reports generated."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-04"/>
        <label value="CPS.9.5#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain report parameters, based on patient demographic, and/or clinical data, which would allow sorting, and/or filtering of the data."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-05"/>
        <label value="CPS.9.5#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to save report parameters for generating subsequent reports."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-06"/>
        <label value="CPS.9.5#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to edit one or more parameters of a saved report specification when generating a report using that specification."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#6"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-07"/>
        <label value="CPS.9.5#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render reports, using internal or external reporting tools, based on the absence of a clinical data element (e.g., a laboratory test has not been performed in the last year)."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.2.3#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-08"/>
        <label value="CPS.9.5#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability for the patient to render [query] the financial data and the data about his or her health related accounts."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.1.5#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-09"/>
        <label value="CPS.9.5#09"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to present and transmit customized views of summarized information based on sort and filter controls for date or date range, problem, or other clinical parameters."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.1.5#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-10"/>
        <label value="CPS.9.5#10"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to present and transmit summarized information through customized views based on prioritization of chronology, problem, or other pertinent clinical parameters."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.9.5-11"/>
        <label value="CPS.9.5#11"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability for a provider to capture and maintain filters to search for previous events (e.g., encounters, reports, consults) meeting specified criteria."/>
      </statement>
    </Requirements>