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-CPS.4.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>Maintain order set templates based on preferred standards, provider preferences, organizational policy or other criteria.</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>Order set templates, which may include medication orders, allow a care provider to choose common orders for a particular circumstance or disease state according to standards (e.g., best practice guidelines) or other criteria. Order Set Templates may be defined to allow or not allow the provider to modify (add/remove/update) specific orders when applying them to a specific patient.</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.4.1#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 manage order set templates, including creation from provider input and version control.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#02</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 capture an order set template based on a specific patient's orders/data according to scope of practice, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#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 manage order set templates created for conditions or diseases.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#04</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 the practice standards or criteria used to create order set templates (e.g., as a note attached to the template).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#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 render order set templates to providers based on diagnoses, conditions, or symptoms to aid decision support.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#06</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL conform to function [[CP.4.1]] (Use Order Sets).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#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 capture and maintain an order set template containing all order types relevant to a particular problem (e.g., laboratory , radiology, medications, nursing tasks, and materials management).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#08</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD capture, maintain and render order set templates customized by patient age, sex, or other patient factors.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#09</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD capture, maintain and render order set templates customized by provider type.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#10</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY capture, maintain and render order set templates customized by provider.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#11</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD capture, maintain and render standing order set templates for triage or for specific conditions.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#12</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 links or access to applicable clinical standards and reference materials within an order set.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#13</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, maintain and render the date that an order set was last modified.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#14</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, maintain and render order set templates that are pre-configured with order entry information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#15</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, maintain and render multiple choices of orders within an order set template for clinician selection.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#16</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, maintain and render text instructions or recommendations within order sets.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#17</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 a name for an order set.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#18</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 order set(s) by name.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#19</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 orders in the same manner regardless of the manner in which they were ordered (individually or from within an order set).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#20</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 integrate order sets within other order sets.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#21</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL determine and render drug-drug interaction and drug-allergy reaction checking to orders placed through an order set in the same way as orders placed individually.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#22</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 reports on the use of order sets, including such data as orders, ordering provider, date/time ordered, basic patient data (e.g., demographics), and condition(s) being treated.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#23</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, maintain and render order sets that allow or disallow individual orders to be selected or deselected by the user (e.g., standing orders that can't be modified during care provision).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>CPS.4.1#24</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 maintain order set preferences.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.4.1"/>
<version value="0.14.0"/>
<name value="CPS_4_1_Manage_Order_Set_Templates"/>
<title value="CPS.4.1 Manage Order Set Templates (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="Maintain order set templates based on preferred standards, provider preferences, organizational policy or other criteria."/>
<purpose
value="Order set templates, which may include medication orders, allow a care provider to choose common orders for a particular circumstance or disease state according to standards (e.g., best practice guidelines) or other criteria. Order Set Templates may be defined to allow or not allow the provider to modify (add/remove/update) specific orders when applying them to a specific patient."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-01"/>
<label value="CPS.4.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage order set templates, including creation from provider input and version control."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-02"/>
<label value="CPS.4.1#02"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY capture an order set template based on a specific patient's orders/data according to scope of practice, organizational policy, and/or jurisdictional law."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#4"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-03"/>
<label value="CPS.4.1#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage order set templates created for conditions or diseases."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-04"/>
<label value="CPS.4.1#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture the practice standards or criteria used to create order set templates (e.g., as a note attached to the template)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-05"/>
<label value="CPS.4.1#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY render order set templates to providers based on diagnoses, conditions, or symptoms to aid decision support."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#8"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-06"/>
<label value="CPS.4.1#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to function [[CP.4.1]] (Use Order Sets)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.4.1#9"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-07"/>
<label value="CPS.4.1#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture and maintain an order set template containing all order types relevant to a particular problem (e.g., laboratory , radiology, medications, nursing tasks, and materials management)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-08"/>
<label value="CPS.4.1#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture, maintain and render order set templates customized by patient age, sex, or other patient factors."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-09"/>
<label value="CPS.4.1#09"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture, maintain and render order set templates customized by provider type."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-10"/>
<label value="CPS.4.1#10"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY capture, maintain and render order set templates customized by provider."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-11"/>
<label value="CPS.4.1#11"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture, maintain and render standing order set templates for triage or for specific conditions."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-12"/>
<label value="CPS.4.1#12"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage links or access to applicable clinical standards and reference materials within an order set."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-13"/>
<label value="CPS.4.1#13"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render the date that an order set was last modified."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-14"/>
<label value="CPS.4.1#14"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render order set templates that are pre-configured with order entry information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-15"/>
<label value="CPS.4.1#15"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render multiple choices of orders within an order set template for clinician selection."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-16"/>
<label value="CPS.4.1#16"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain and render text instructions or recommendations within order sets."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-17"/>
<label value="CPS.4.1#17"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture a name for an order set."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-18"/>
<label value="CPS.4.1#18"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render order set(s) by name."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-19"/>
<label value="CPS.4.1#19"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to render orders in the same manner regardless of the manner in which they were ordered (individually or from within an order set)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-20"/>
<label value="CPS.4.1#20"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to integrate order sets within other order sets."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-21"/>
<label value="CPS.4.1#21"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL determine and render drug-drug interaction and drug-allergy reaction checking to orders placed through an order set in the same way as orders placed individually."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-22"/>
<label value="CPS.4.1#22"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render reports on the use of order sets, including such data as orders, ordering provider, date/time ordered, basic patient data (e.g., demographics), and condition(s) being treated."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-23"/>
<label value="CPS.4.1#23"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture, maintain and render order sets that allow or disallow individual orders to be selected or deselected by the user (e.g., standing orders that can't be modified during care provision)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-CPS.4.1-24"/>
<label value="CPS.4.1#24"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture and maintain order set preferences."/>
</statement>
</Requirements>