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

## : AS.7.2 Support Encounter Documentation (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-AS.7.2"/>
      <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>Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.</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;">
                AS.7.2#01
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD determine and render workflow support for data collection in a care setting.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                AS.7.2#02
                </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 encounter and care setting specific data entry workflows.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                AS.7.2#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 information from the patient record as necessary to support documentation of the patient encounter.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows.</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-AS.7.2"/>
      <version value="2.1.1"/>
      <name value="AS_7_2_Support_Encounter_Documentation"/>
      <title value="AS.7.2 Support Encounter Documentation (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 assistance in assembling data, supporting data collection and processing output from a specific encounter."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.7.2-01"/>
        <label value="AS.7.2#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD determine and render workflow support for data collection in a care setting."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.2#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.7.2-02"/>
        <label value="AS.7.2#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.2#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.7.2-03"/>
        <label value="AS.7.2#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.2#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.7.2-04"/>
        <label value="AS.7.2#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.2#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-AS.7.2-05"/>
        <label value="AS.7.2#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.3.1.2#5"/>
      </statement>
    </Requirements>