ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-AS.2.1"/>
<meta>
<profile value="http://hl7.org/ehrs/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 interactions with other systems, applications, and modules to enable the maintenance of updated demographic information in accordance with realm-specific recordkeeping requirements.</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>The minimum demographic data set must include the data required by realm-specific laws governing health care transactions and reporting. For example, this may include data input of death status information, or may include support to identify multiple names, such as updating from Baby Girl Doe, to neonate's given name.</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.1#01</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to capture and harmonize patient demographic information through interaction with other systems, applications, and modules according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#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 harmonize information regarding a patient's occupation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#03</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 capture and harmonize a patient's special-interest requirements (e.g., divers, firefighters, or airline pilots whose abilities to perform their occupations may be impacted based on a given diagnosis, and/or treatment).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#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 tag a patient who has similar names in other systems (e.g., aliases, similar names to family members for common issues, multiple patients with same name, one patient with multiple names in external systems).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#05</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 a patient's information from multiple internal or external systems and harmonize the information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#06</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 analyze the data quality of a patient's information (e.g., vital records information regarding the higher data quality of the date-and-time-of-death on one record, versus the lower data quality of the month-of-death on another record).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.1#07</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability to capture data-validation rules for patient demographic data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., synchronization of a patient's records where the values for the patient's sex are Male="1" in one record, and Male="m" in another record, can only be accomplished if the data-validation rules for those values in each record are known).</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2.1"/>
<version value="0.14.0"/>
<name value="AS_2_1_Synchronize_Patient_Demographic_Data"/>
<title value="AS.2.1 Synchronize Patient Demographic Data (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Support interactions with other systems, applications, and modules to enable the maintenance of updated demographic information in accordance with realm-specific recordkeeping requirements."/>
<purpose
value="The minimum demographic data set must include the data required by realm-specific laws governing health care transactions and reporting. For example, this may include data input of death status information, or may include support to identify multiple names, such as updating from Baby Girl Doe, to neonate's given name."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-01"/>
<label value="AS.2.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture and harmonize patient demographic information through interaction with other systems, applications, and modules according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.1#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-02"/>
<label value="AS.2.1#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture and harmonize information regarding a patient's occupation."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-03"/>
<label value="AS.2.1#03"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture and harmonize a patient's special-interest requirements (e.g., divers, firefighters, or airline pilots whose abilities to perform their occupations may be impacted based on a given diagnosis, and/or treatment)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-04"/>
<label value="AS.2.1#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD tag a patient who has similar names in other systems (e.g., aliases, similar names to family members for common issues, multiple patients with same name, one patient with multiple names in external systems)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-05"/>
<label value="AS.2.1#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture a patient's information from multiple internal or external systems and harmonize the information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-06"/>
<label value="AS.2.1#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to analyze the data quality of a patient's information (e.g., vital records information regarding the higher data quality of the date-and-time-of-death on one record, versus the lower data quality of the month-of-death on another record)."/>
<derivedFrom value="PHFP S.1.4.1#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-AS.2.1-07"/>
<label value="AS.2.1#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture data-validation rules for patient demographic data according to scope of practice, organizational policy, and/or jurisdictional law (e.g., synchronization of a patient's records where the values for the patient's sex are Male="1" in one record, and Male="m" in another record, can only be accomplished if the data-validation rules for those values in each record are known)."/>
<derivedFrom value="PHFP S.1.4.1#4"/>
</statement>
</Requirements>