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

## : CPS.4.2.3 Support for Medication Ordering Efficiencies (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.4.2.3"/>
      <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>Support efficient medication ordering workflows by allowing medications to be sorted and reviewed by key attributes, e.g., generic or trade names. Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets.</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;">
                CPS.4.2.3#01
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD present a medication compendia or formulary content (e.g., drug, dose, route and SIG) to facilitate the selection of the medication to be ordered.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#02
                </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 instructions to all medications within a given class of medications.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#03
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY render a list of frequently-ordered medications by diagnosis by provider which could include the full details of the medication, including SIG, quantity, refills, dispense as written, etc. and capture the provider's selection.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#04
                </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 medications by therapeutic class, and/or indication.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#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 medication samples dispensed, including lot number and expiration date.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#06
                </td>
                <td style="padding-left: 4px;">
                MAY

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to tag that the medication sample was dispensed in the office.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#07
                </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 and render reminders to patients regarding necessary follow up tests based on the prescribed medication (e.g., reminders may be sent manually or automatically via a pre-determined rule).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.4.2.3#08
                </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 render reminders to the clinicians regarding necessary patient follow up tests, based on the prescribed medication.</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-CPS.4.2.3"/>
      <version value="2.1.1"/>
      <name value="CPS_4_2_3_Support_for_Medication_Ordering_Efficiencies"/>
      <title
             value="CPS.4.2.3 Support for Medication Ordering Efficiencies (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 tooling necessary to support efficient medication ordering."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Support efficient medication ordering workflows by allowing medications to be sorted and reviewed by key attributes, e.g., generic or trade names. Also support editing medication orders across multiple instances of an order and capturing medication orders in order sets."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-01"/>
        <label value="CPS.4.2.3#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD present a medication compendia or formulary content (e.g., drug, dose, route and SIG) to facilitate the selection of the medication to be ordered."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.7.1#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-02"/>
        <label value="CPS.4.2.3#02"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to link instructions to all medications within a given class of medications."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-03"/>
        <label value="CPS.4.2.3#03"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY render a list of frequently-ordered medications by diagnosis by provider which could include the full details of the medication, including SIG, quantity, refills, dispense as written, etc. and capture the provider's selection."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.7.1#11"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-04"/>
        <label value="CPS.4.2.3#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture medications by therapeutic class, and/or indication."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.7.1#12"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-05"/>
        <label value="CPS.4.2.3#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture, maintain and render medication samples dispensed, including lot number and expiration date."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-06"/>
        <label value="CPS.4.2.3#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to tag that the medication sample was dispensed in the office."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-07"/>
        <label value="CPS.4.2.3#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture and render reminders to patients regarding necessary follow up tests based on the prescribed medication (e.g., reminders may be sent manually or automatically via a pre-determined rule)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.4.2.3-08"/>
        <label value="CPS.4.2.3#08"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and render reminders to the clinicians regarding necessary patient follow up tests, based on the prescribed medication."/>
      </statement>
    </Requirements>