ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
2.1.0 - local
Publish Box goes here
| Active as of 2024-11-26 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-CPS.1.3"/>
<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>Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete.</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 registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event.</p>
<p>After care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of "John Doe1; approximate age is 30" may need to be matched with existing records for "Henry Smith; age 28".</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>CPS.1.3#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 capture patient registration information to accommodate an expedited registration situation (e.g., during a disaster or during a census overload at a facility).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.1.3#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 registration through integration with an external system (e.g., Hospital ADT) before all identifying data is known.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.1.3#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 harmonize information generated during an expedited registration process with the EHR.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.1.3"/>
<version value="2.1.0"/>
<name value="CPS_1_3_Capture_Quick_Registration"/>
<title value="CPS.1.3 Capture Quick Registration (Function)"/>
<status value="active"/>
<date value="2024-11-26T16:30:50+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Capture a registration, either directly entered or received from an external system, without complete supporting demographics, in order to facilitate patient care before the full registration is complete."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<purpose
value="The registration process, including the verification of full demographics data, insurance, contact information, etc. is frequently time consuming. To facilitate patient care in emergency situations, the system must be able to register a patient with minimal information in a time critical manner. Examples of situations when this might be necessary include when a patient presents with acute myocardial infarction, a disaster response, or a mass casualty event.
After care is given during an emergent situation, records are often incomplete or invalid. Such records may need to be completed and validated. Afterwards, those records may need to be harmonized. For example, the records of "John Doe1; approximate age is 30" may need to be matched with existing records for "Henry Smith; age 28"."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.1.3-01"/>
<label value="CPS.1.3#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture patient registration information to accommodate an expedited registration situation (e.g., during a disaster or during a census overload at a facility)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.1.3-02"/>
<label value="CPS.1.3#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture registration through integration with an external system (e.g., Hospital ADT) before all identifying data is known."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.1.3-03"/>
<label value="CPS.1.3#03"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to harmonize information generated during an expedited registration process with the EHR."/>
</statement>
</Requirements>