ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.16.0 - CI Build
Publish Box goes here
| Active as of 2024-08-12 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-AS.2.2"/>
<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>Provide the patient's location information within a facility's premises.</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>It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or "J. Doe1"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information.</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.2#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 render information regarding the patient's assigned location when the patient has an assigned location (e.g., specific bed).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.2#02</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD provide the ability to render information regarding a patient's location based on existing patient-consent documentation and according to scope of practice, organizational policy, and/or jurisdictional laws.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.2#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 manage information regarding the patient's current location (e.g., temporary location of patient).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.2#05</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 render information regarding the patient's current location by alternate identifiers (e.g., by arrival number, by alias, or by bed-number).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.2#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 render the de-identified list of patients who have not consented to release of information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.2#07</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 render an alert if the patient has exceeded a system-defined time in a location.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2.2"/>
<version value="0.16.0"/>
<name value="AS_2_2_Manage_Patient_s_Location_Within_Facility"/>
<title value="AS.2.2 Manage Patient's Location Within Facility (Function)"/>
<status value="active"/>
<date value="2024-08-12T10:56:01+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Provide the patient's location information within a facility's premises."/>
<purpose
value="It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or "J. Doe1"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-01"/>
<label value="AS.2.2#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render information regarding the patient's assigned location when the patient has an assigned location (e.g., specific bed)."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-02"/>
<label value="AS.2.2#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render information regarding a patient's location based on existing patient-consent documentation and according to scope of practice, organizational policy, and/or jurisdictional laws."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-03"/>
<label value="AS.2.2#03"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage information regarding the patient's current location (e.g., temporary location of patient)."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-05"/>
<label value="AS.2.2#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render information regarding the patient's current location by alternate identifiers (e.g., by arrival number, by alias, or by bed-number)."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.2#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-06"/>
<label value="AS.2.2#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY render the de-identified list of patients who have not consented to release of information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.2-07"/>
<label value="AS.2.2#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render an alert if the patient has exceeded a system-defined time in a location."/>
</statement>
</Requirements>