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-ballot 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

• Narrative Content
• XML
• JSON
• TTL

: AS.7 Support Encounter/Episode of Care Management (Header) - XML Representation

Page standards status: Informative

Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2-AS.7"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMHeader"/>
  </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>Manage and document 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, encounter management promotes patient-centered/oriented care and enables real time, immediate point of service, point of care by facilitating efficient work flow and operations performance to ensure the integrity of (1) the health record, (2) public health, financial and administrative reporting, and (3) the healthcare delivery process.</p>
<p>This support is necessary for care provision functionality that relies on providing user interaction and workflows. These interactions and workflows are configured according to clinical protocols and business rules. These protocols and rules are based on encounter specific values such as care setting, encounter type (inpatient, outpatient, home health, etc.), provider type, patient's EHR, health status, demographics, and the initial purpose of the encounter.</p>
</div></span>
    

    
    
    

    
    <table id="statements" class="grid dict">
        
    </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-AS.7"/>
  <version value="2.1.1-ballot"/>
  <name value="AS_7_Support_Encounter_Episode_of_Care_Management"/>
  <title value="AS.7 Support Encounter/Episode of Care Management (Header)"/>
  <status value="active"/>
  <date value="2025-08-29T14:03:55+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="Manage and document 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, encounter management promotes patient-centered/oriented care and enables real time, immediate point of service, point of care by facilitating efficient work flow and operations performance to ensure the integrity of (1) the health record, (2) public health, financial and administrative reporting, and (3) the healthcare delivery process.

This support is necessary for care provision functionality that relies on providing user interaction and workflows. These interactions and workflows are configured according to clinical protocols and business rules. These protocols and rules are based on encounter specific values such as care setting, encounter type (inpatient, outpatient, home health, etc.), provider type, patient's EHR, health status, demographics, and the initial purpose of the encounter."/>
</Requirements>