HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - Normative

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

## : CP.4 Manage Orders (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CP.4"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <language value="en"/>
      <text>
        <status value="extensions"/>
        <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">

        <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>The provision of clinical care includes the need to order from a variety of treatments using order sets as appropriate as well as reviewing the results of treatment. Orders for treatments may include medications, non-medication therapies (e.g., physical therapy, special diet, immunizations, non-allopathic regimens); diagnostic care (e.g., laboratory , radiology); blood products and other biologics (e.g., blood transfusions, human growth hormones). Patients are often referred to other health care providers for more specialized diagnostic workup, and/or treatment. An effective EHR-S must include support and management of these processes and associated documentation.</p>
    </div></div>

        <div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>

        <table id="statements" class="grid dict">

            <tr>
                <td style="padding-left: 4px;">
                CP.4#01
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to manage role-based, context-based, and/or user-based order entry.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#02
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to manage the creation, renewal, modification and discontinuation of orders.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#03
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to render relevant, patient-specific laboratory test results when entering an order.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#04
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to manage the status of an order (e.g., open, completed, in process).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#05
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to capture, maintain and render order entry with an appropriate registration process when the identity of the patient is unknown or in an urgent situation.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#06
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                    <span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #e5f5e5;color: #388e3c;border: 1px solid #a2d1a2;">dependent</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to manage standing orders or orders that may be submitted by providers other than licensed providers according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#07
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to capture and render problem/diagnosis as an element of an order.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#08
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to capture, maintain and render, as discrete data, a diagnosis/problem code, and/or description associated with an order of any type (including prescriptions and medications ordered for administration).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#09
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to link an order of any type (including medication order) with a related clinical problem(s), and/or diagnosis code(s) and description.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#10
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to annotate and render comments and instructions with an order.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#11
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to annotate and render free text comments and instructions with an order (e.g., &quot;Short draw, do CBC first&quot;).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#12
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to tag frequently used and institutionally-approved order sets as &quot;favorites&quot; or &quot;preferences&quot; to facilitate retrieval and ordering.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#13
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to manage orders submitted to or received from external organizations, and/or facilities such as Health Information Exchanges (HIEs) or regional Electronic Health Record Systems (EHR-Ss).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#14
                </td>
                <td style="padding-left: 4px;">
                SHALL

                    <span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #e5f5e5;color: #388e3c;border: 1px solid #a2d1a2;">dependent</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL render patient identifying information (e.g., the patient name, identification number, and age or date of birth) on all order screens, according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#15
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to capture, maintain and render an indicator of oral verification (&quot;read-back&quot;) of the complete order by the person receiving the telephone or verbal order.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#16
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to capture and render the urgency status (e.g., As-Soon-As-Possible or STAT) associated with an order.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#17
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to render order history for any order, including the ordering clinician, order details, date, and time.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#18
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to tag and render a field as required for a complete order by order type (e.g., pediatric order for antibiotic that requires the patient's weight).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#19
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to tag orders to be activated at a future date and time including admission orders, discharge orders, and post-operative orders.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#20
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to manage conditional orders that can be activated when certain criteria and conditions are met.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#21
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to capture, store and render the identity of all providers who signed an order including their name and credential identifier.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#22
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to render a list of active orders for a patient.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#23
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to render a list of orders by similar or comparable type (e.g., all radiology or all laboratory orders).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#24
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to render outstanding orders for multiple patients, as opposed to outstanding orders for a single patient (e.g., all outstanding orders for a specific clinician or all outstanding orders for a care setting).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#25
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to capture and transmit the provider's order cancellation request.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#26
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD conform to function <a href="Requirements-EHRSFMR2-CPS.8.4.html">CPS.8.4</a> (Support for Communication between Provider and Patient, and/or the Patient Representative) to manage information regarding orders.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CP.4#27
                </td>
                <td style="padding-left: 4px;">
                SHALL

                    <span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #e5f5e5;color: #388e3c;border: 1px solid #a2d1a2;">dependent</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to determine and capture co-signatures for orders based upon roles (e.g., consulting physician) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
        <valueCode value="normative"/>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.4"/>
      <version value="2.1.1"/>
      <name value="CP_4_Manage_Orders"/>
      <title value="CP.4 Manage Orders (Function)"/>
      <status value="active"/>
      <date value="2025-12-13T09:06:06+00:00"/>
      <publisher value="HL7 International / Electronic Health Records"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="Provide the ability to manage clinical orders and results including medication, non-medication, diagnostic tests, blood products, other biologics and referrals, using order sets as appropriate."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="The provision of clinical care includes the need to order from a variety of treatments using order sets as appropriate as well as reviewing the results of treatment. Orders for treatments may include medications, non-medication therapies (e.g., physical therapy, special diet, immunizations, non-allopathic regimens); diagnostic care (e.g., laboratory , radiology); blood products and other biologics (e.g., blood transfusions, human growth hormones). Patients are often referred to other health care providers for more specialized diagnostic workup, and/or treatment. An effective EHR-S must include support and management of these processes and associated documentation."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-01"/>
        <label value="CP.4#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage role-based, context-based, and/or user-based order entry."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-02"/>
        <label value="CP.4#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage the creation, renewal, modification and discontinuation of orders."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-03"/>
        <label value="CP.4#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render relevant, patient-specific laboratory test results when entering an order."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-04"/>
        <label value="CP.4#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to manage the status of an order (e.g., open, completed, in process)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-05"/>
        <label value="CP.4#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture, maintain and render order entry with an appropriate registration process when the identity of the patient is unknown or in an urgent situation."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CP.4-06"/>
        <label value="CP.4#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage standing orders or orders that may be submitted by providers other than licensed providers according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-07"/>
        <label value="CP.4#07"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and render problem/diagnosis as an element of an order."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-08"/>
        <label value="CP.4#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture, maintain and render, as discrete data, a diagnosis/problem code, and/or description associated with an order of any type (including prescriptions and medications ordered for administration)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-09"/>
        <label value="CP.4#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to link an order of any type (including medication order) with a related clinical problem(s), and/or diagnosis code(s) and description."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-10"/>
        <label value="CP.4#10"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to annotate and render comments and instructions with an order."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-11"/>
        <label value="CP.4#11"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to annotate and render free text comments and instructions with an order (e.g., &quot;Short draw, do CBC first&quot;)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-12"/>
        <label value="CP.4#12"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to tag frequently used and institutionally-approved order sets as &quot;favorites&quot; or &quot;preferences&quot; to facilitate retrieval and ordering."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-13"/>
        <label value="CP.4#13"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage orders submitted to or received from external organizations, and/or facilities such as Health Information Exchanges (HIEs) or regional Electronic Health Record Systems (EHR-Ss)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CP.4-14"/>
        <label value="CP.4#14"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL render patient identifying information (e.g., the patient name, identification number, and age or date of birth) on all order screens, according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-15"/>
        <label value="CP.4#15"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture, maintain and render an indicator of oral verification (&quot;read-back&quot;) of the complete order by the person receiving the telephone or verbal order."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-16"/>
        <label value="CP.4#16"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and render the urgency status (e.g., As-Soon-As-Possible or STAT) associated with an order."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-17"/>
        <label value="CP.4#17"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render order history for any order, including the ordering clinician, order details, date, and time."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-18"/>
        <label value="CP.4#18"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to tag and render a field as required for a complete order by order type (e.g., pediatric order for antibiotic that requires the patient's weight)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-19"/>
        <label value="CP.4#19"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to tag orders to be activated at a future date and time including admission orders, discharge orders, and post-operative orders."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-20"/>
        <label value="CP.4#20"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage conditional orders that can be activated when certain criteria and conditions are met."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-21"/>
        <label value="CP.4#21"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture, store and render the identity of all providers who signed an order including their name and credential identifier."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-22"/>
        <label value="CP.4#22"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render a list of active orders for a patient."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-23"/>
        <label value="CP.4#23"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render a list of orders by similar or comparable type (e.g., all radiology or all laboratory orders)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-24"/>
        <label value="CP.4#24"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render outstanding orders for multiple patients, as opposed to outstanding orders for a single patient (e.g., all outstanding orders for a specific clinician or all outstanding orders for a care setting)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-25"/>
        <label value="CP.4#25"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and transmit the provider's order cancellation request."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CP.4-26"/>
        <label value="CP.4#26"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function [CPS.8.4](Requirements-EHRSFMR2-CPS.8.4.html) (Support for Communication between Provider and Patient, and/or the Patient Representative) to manage information regarding orders."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CP.4-27"/>
        <label value="CP.4#27"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to determine and capture co-signatures for orders based upon roles (e.g., consulting physician) according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
    </Requirements>