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

Publication Build: This will be filled in by the publication tooling

## : CP.9.2 Capture Health Service Report Information (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CP.9.2"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data.</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

        <table id="statements" class="grid dict">

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

                    <span>CP.9.2#01</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 that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CP.9.2#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 render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CP.9.2#03</span>

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

                    <i>conditional</i>

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CP.9.2#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 provide the ability to capture and render the acknowledgement that health service reports have been received.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CP.9.2#05</span>

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

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHALL conform to function <a href="Requirements-EHRSFMR2-CP.9.1.html">CP.9.1</a> (Produce a Summary Record of Care).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CP.9.2#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 render a notification that prompts providers on the information needed for regulatory safety reporting.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.9.2"/>
      <version value="2.1.1-ballot"/>
      <name value="CP_9_2_Capture_Health_Service_Report_Information"/>
      <title value="CP.9.2 Capture Health Service Report Information (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:04:36+11: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="Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry)."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-01"/>
        <label value="CP.9.2#01"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY render a notification that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.3.6#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-02"/>
        <label value="CP.9.2#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.3.6#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-03"/>
        <label value="CP.9.2#03"/>
        <conformance value="MAY"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-04"/>
        <label value="CP.9.2#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and render the acknowledgement that health service reports have been received."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-05"/>
        <label value="CP.9.2#05"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [CP.9.1](Requirements-EHRSFMR2-CP.9.1.html) (Produce a Summary Record of Care)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.9.2-06"/>
        <label value="CP.9.2#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD render a notification that prompts providers on the information needed for regulatory safety reporting."/>
      </statement>
    </Requirements>