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.4"/>
<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 ensure that the patient's bed assignments within the facility optimize care and minimize risks e.g., of exposure to contagious patients.</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>Access to a list of available beds is important to safely manage the care of patients whose bed requirements may change based on change in condition or risk factors. For example, a patient may need a room with special equipment or to be close to the nursing station or to be in a private room.</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.4#01</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 patient bed assignment interactions that are internal or external to the system (e.g., including temporary bed assignments).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#02</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY transmit patient information to an external system that will facilitate bed assignment, care optimization and risk mitigation.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#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 render lists of information to help enable effective bed assignment, including at a minimum, list of patients currently within the facility, a list of empty rooms and a list of available patient care spaces.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#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 render lists of information on patient status to help enable effective bed assignment, including at a minimum, a list of patients waiting to be triaged, a list of patients waiting to be registered, and a list of patients that have been admitted to the facility but are queued up for a transition of care.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#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 waiting time for patients not yet brought to a treatment area.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#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 render the number of patients that have been admitted to the facility but are queued up for a transition of care.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#07</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 on incoming transported patients (e.g., rescue in-bounds).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#08</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 re-location of patients.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>AS.2.4#09</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 manage separately multiple patients being simultaneously cared for in a single room or in an identified space 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.4#10</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 manage temporary beds and the patients in the temporary beds 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.4#11</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY tag with a status indication that the patient is ready for a transition of care (e.g., transport to an inpatient bed).</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2.4"/>
<version value="0.14.0"/>
<name value="AS_2_4_Manage_Patient_Bed_Assignment"/>
<title value="AS.2.4 Manage Patient Bed Assignment (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 ensure that the patient's bed assignments within the facility optimize care and minimize risks e.g., of exposure to contagious patients."/>
<purpose
value="Access to a list of available beds is important to safely manage the care of patients whose bed requirements may change based on change in condition or risk factors. For example, a patient may need a room with special equipment or to be close to the nursing station or to be in a private room."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-01"/>
<label value="AS.2.4#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage patient bed assignment interactions that are internal or external to the system (e.g., including temporary bed assignments)."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.4#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-02"/>
<label value="AS.2.4#02"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY transmit patient information to an external system that will facilitate bed assignment, care optimization and risk mitigation."/>
<derivedFrom value="EHR-S_FM_R1.1 S.1.4.4#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-03"/>
<label value="AS.2.4#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render lists of information to help enable effective bed assignment, including at a minimum, list of patients currently within the facility, a list of empty rooms and a list of available patient care spaces."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-04"/>
<label value="AS.2.4#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render lists of information on patient status to help enable effective bed assignment, including at a minimum, a list of patients waiting to be triaged, a list of patients waiting to be registered, and a list of patients that have been admitted to the facility but are queued up for a transition of care."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-05"/>
<label value="AS.2.4#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render waiting time for patients not yet brought to a treatment area."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-06"/>
<label value="AS.2.4#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render the number of patients that have been admitted to the facility but are queued up for a transition of care."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-07"/>
<label value="AS.2.4#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render information on incoming transported patients (e.g., rescue in-bounds)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-08"/>
<label value="AS.2.4#08"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage re-location of patients."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-09"/>
<label value="AS.2.4#09"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage separately multiple patients being simultaneously cared for in a single room or in an identified space according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-10"/>
<label value="AS.2.4#10"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage temporary beds and the patients in the temporary beds according to scope of practice, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-AS.2.4-11"/>
<label value="AS.2.4#11"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY tag with a status indication that the patient is ready for a transition of care (e.g., transport to an inpatient bed)."/>
</statement>
</Requirements>