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.2.3 Medication Order Efficiencies (Function)

Page standards status: Normative

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "EHRSFMR2-CP.4.2.3",
      "meta" : {
        "profile" : [
          🔗 "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"
        ]
      },
      "language" : "en",
      "text" : {
        "status" : "extensions",
        "div" : "<div xml:lang=\"en\" xmlns=\"http://www.w3.org/1999/xhtml\" lang=\"en\">\n    \n    \n    <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>Make medication ordering workflows more efficient 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>\n</div></div>\n    \n    \n    \n    <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>\n    \n    <table id=\"statements\" class=\"grid dict\">\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#01\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability to present a list of medications based on an attribute of the medication (e.g., partial medication name, therapeutic class, or formulary).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#02\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability to present a list of medications based on an attribute of the patient (e.g., proposed treatment, patient condition, order set, age, gender).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#03\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability for the clinician to edit medication administration instructions and link it to the corresponding instances of that medication order.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#04\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability to extract, update and store a prescription reorder by allowing a prior prescription to be reordered without re-entering previous data (e.g., administration schedule, quantity, SIG).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#05\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHOULD provide the ability to extract, update and store a prescription reorder from a prior prescription using the same dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#06\n            </td>\n            <td style=\"padding-left: 4px;\">\n            MAY\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system MAY provide the ability to extract, update and store a prescription renewal from a prior prescription using a different dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#07\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHALL conform to function <a href=\"Requirements-EHRSFMR2-CP.4.1.html\">CP.4.1</a> (Use Order Sets).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            CP.4.2.3#08\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHALL provide the ability to extract and render medications by generic, and/or brand name.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n    </table>\n</div>"
      },
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
          "valueCode" : "normative"
        },
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
          "valueCode" : "ehr"
        }
      ],
      "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.4.2.3",
      "version" : "2.1.1",
      "name" : "CP_4_2_3_Medication_Order_Efficiencies",
      "title" : "CP.4.2.3 Medication Order Efficiencies (Function)",
      "status" : "active",
      "date" : "2025-12-13T09:06:06+00:00",
      "publisher" : "HL7 International / Electronic Health Records",
      "contact" : [
        {
          "telecom" : [
            {
              "system" : "url",
              "value" : "http://www.hl7.org/Special/committees/ehr"
            }
          ]
        }
      ],
      "description" : "Provide the tooling necessary to increase the efficiency of medication ordering.",
      "jurisdiction" : [
        {
          "coding" : [
            {
              "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
              "code" : "001",
              "display" : "World"
            }
          ]
        }
      ],
      "purpose" : "Make medication ordering workflows more efficient 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" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-01",
          "label" : "CP.4.2.3#01",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to present a list of medications based on an attribute of the medication (e.g., partial medication name, therapeutic class, or formulary).",
          "derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#4"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-02",
          "label" : "CP.4.2.3#02",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to present a list of medications based on an attribute of the patient (e.g., proposed treatment, patient condition, order set, age, gender)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-03",
          "label" : "CP.4.2.3#03",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability for the clinician to edit medication administration instructions and link it to the corresponding instances of that medication order."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-04",
          "label" : "CP.4.2.3#04",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to extract, update and store a prescription reorder by allowing a prior prescription to be reordered without re-entering previous data (e.g., administration schedule, quantity, SIG).",
          "derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#14"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-05",
          "label" : "CP.4.2.3#05",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to extract, update and store a prescription reorder from a prior prescription using the same dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight).",
          "derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#15"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-06",
          "label" : "CP.4.2.3#06",
          "conformance" : [
            "MAY"
          ],
          "conditionality" : false,
          "requirement" : "The system MAY provide the ability to extract, update and store a prescription renewal from a prior prescription using a different dosage but allowing for editing of details adequate for correct filling and administration of medication (e.g., dose, frequency, body weight)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-07",
          "label" : "CP.4.2.3#07",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL conform to function [CP.4.1](Requirements-EHRSFMR2-CP.4.1.html) (Use Order Sets).",
          "derivedFrom" : "EHR-S_FM_R1.1 DC.1.7.1#10"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-CP.4.2.3-08",
          "label" : "CP.4.2.3#08",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to extract and render medications by generic, and/or brand name."
        }
      ]
    }