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

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

: AS.2 Manage Patient Demographics, Location and Synchronization (Function) - XML Representation

Page standards status: Informative

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="EHRSFMR2-AS.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>Capture and management of patient administrative information across locations in order to support care, including directories, and/or registries.</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>A patient directory/registry may contain information including, but not limited to: full name, residence or physical location, alternate contact person, primary phone number, and relevant health status information. Various views of Patient Registry or Directory information may constructed to accommodate various user's needs. Examples of specific directory views are presented in the following functions.</p>
<p>The patient administrative information also includes patient location information (within a facility as well as home care location(s)); as well as the patient's registration in healthcare programs.</p>
</div></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>AS.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 provide the ability to harmonize a patient's demographic information with an external system (e.g., a centralized registry or health information exchange) triggered by clinical or administrative events (e.g., arrival of a new patient, reappearance of a past patient at a given facility, or periodic synchronization of health information).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.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 transmit a notification to an external system (e.g., an external Client Registry or a Personal Health Record System) that a patient's demographic information was modified.</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.2#03</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 tag patient information with the current status (e.g., active, admitted, inactive, or discharged).</p>
</div></span>
                
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
                
                <span>AS.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 manage the administrative status and location of the patient during care within a facility. (e.g., waiting to see a provider, admitted, holding, waiting for nurse, waiting for consultant, or on the way to the Operating Room).</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-AS.2"/>
  <version value="2.1.1-ballot"/>
  <name
        value="AS_2_Manage_Patient_Demographics__Location_and_Synchronization"/>
  <title
         value="AS.2 Manage Patient Demographics, Location and Synchronization (Function)"/>
  <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="Capture and management of patient administrative information across locations in order to support care, including directories, and/or registries."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <purpose
           value="A patient directory/registry may contain information including, but not limited to: full name, residence or physical location, alternate contact person, primary phone number, and relevant health status information. Various views of Patient Registry or Directory information may constructed to accommodate various user's needs. Examples of specific directory views are presented in the following functions.

The patient administrative information also includes patient location information (within a facility as well as home care location(s)); as well as the patient's registration in healthcare programs."/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2-AS.2-01"/>
    <label value="AS.2#01"/>
    <conformance value="MAY"/>
    <conditionality value="false"/>
    <requirement
                 value="The system MAY provide the ability to harmonize a patient's demographic information with an external system (e.g., a centralized registry or health information exchange) triggered by clinical or administrative events (e.g., arrival of a new patient, reappearance of a past patient at a given facility, or periodic synchronization of health information)."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2-AS.2-02"/>
    <label value="AS.2#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to transmit a notification to an external system (e.g., an external Client Registry or a Personal Health Record System) that a patient's demographic information was modified."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2-AS.2-03"/>
    <label value="AS.2#03"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to tag patient information with the current status (e.g., active, admitted, inactive, or discharged)."/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <key value="EHRSFMR2-AS.2-04"/>
    <label value="AS.2#04"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to manage the administrative status and location of the patient during care within a facility. (e.g., waiting to see a provider, admitted, holding, waiting for nurse, waiting for consultant, or on the way to the Operating Room)."/>
  </statement>
</Requirements>