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

## : CPS.3.11 Support Other Encounter and Episode of Care Documentation (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.3.11"/>
      <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>Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care.</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>Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of</p>
    <ul>
    <li>the health record,</li>
    <li>public health, financial and administrative reporting, and</li>
    <li>the healthcare delivery process.</li>
    </ul>
    </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>CPS.3.11#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 patient data by encounter, including previous admissions and episodes of care.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CPS.3.11#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 capture and annotate patient encounter data from external systems, such as diagnostic tests and reports.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>CPS.3.11#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 capture encounter documentation by one or more of the following input methods:</p>
    <ul>
    <li>direct keyboard entry of text;</li>
    <li>structured data entry utilizing templates, forms, pick lists or macro substitution; and</li>
    <li>dictation with subsequent transcription of voice to text, either manually or via voice recognition system.</li>
    </ul>
    </div></span>

                </td>
            </tr>

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

                    <span>CPS.3.11#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 maintain presentation filters that are specific to the types of encounter (e.g., care provider specialty, location of encounter, date of encounter, associated diagnosis).</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-CPS.3.11"/>
      <version value="2.1.1-ballot"/>
      <name
            value="CPS_3_11_Support_Other_Encounter_and_Episode_of_Care_Documentation"/>
      <title
             value="CPS.3.11 Support Other Encounter and Episode of Care Documentation (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="Where not covered above, provide the means to manage and organize the documentation of the health care needed and delivered during an encounter/episode of care."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Using data standards and technologies that support interoperability, effective documentation of an encounter can promote patient- centered/oriented care and enables real-time, immediate point-of-service care delivery. Effective encounter and episode-of-care documentation can facilitate efficient work flow and improve operations performance. This can help to ensure the integrity of
    - the health record,
    - public health, financial and administrative reporting, and
    - the healthcare delivery process."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.11-01"/>
        <label value="CPS.3.11#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render patient data by encounter, including previous admissions and episodes of care."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.5#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.11-02"/>
        <label value="CPS.3.11#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and annotate patient encounter data from external systems, such as diagnostic tests and reports."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.5#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.11-03"/>
        <label value="CPS.3.11#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture encounter documentation by one or more of the following input methods:
    - direct keyboard entry of text;
    - structured data entry utilizing templates, forms, pick lists or macro substitution; and
    - dictation with subsequent transcription of voice to text, either manually or via voice recognition system."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.5#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.11-04"/>
        <label value="CPS.3.11#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain presentation filters that are specific to the types of encounter (e.g., care provider specialty, location of encounter, date of encounter, associated diagnosis)."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.5#4"/>
      </statement>
    </Requirements>