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

## : TI.2.3 Audit Notification and Review (Function)

Page standards status: Normative

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "EHRSFMR2-TI.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>EHR system functions allow various methods of critical event notification (from audit triggers) as well as routine log review.</p>\n<p>Audit log notification and review functions implement requirements according to scope of practice, organizational policy, and jurisdictional law.</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            TI.2.3#01\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 render a report based on audit log entries.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            TI.2.3#02\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 render reports based on ranges of system date and time that audit log entries were captured.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            TI.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 to render audit log entry time stamps using UTC (based on ISO 8601).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            TI.2.3#04\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHALL\n            \n                \n                <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>\n                \n            \n            \n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>The system SHALL provide the ability to authorize emergency access to certain logs based on criteria such as individual work assignment, specific user role, specific reason(s), or a need to access a specific patient's information/record entries according to organizational policy and/or jurisdictional law.</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-TI.2.3",
      "version" : "2.1.1",
      "name" : "TI_2_3_Audit_Notification_and_Review",
      "title" : "TI.2.3 Audit Notification and Review (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" : "Notify of Audit Events, Review Audit Log",
      "jurisdiction" : [
        {
          "coding" : [
            {
              "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
              "code" : "001",
              "display" : "World"
            }
          ]
        }
      ],
      "purpose" : "EHR system functions allow various methods of critical event notification (from audit triggers) as well as routine log review.\n\nAudit log notification and review functions implement requirements according to scope of practice, organizational policy, and jurisdictional law.",
      "statement" : [
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-TI.2.3-01",
          "label" : "TI.2.3#01",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to render a report based on audit log entries.",
          "derivedFrom" : "EHR-S_FM_R1.1 IN.2.2#14"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-TI.2.3-02",
          "label" : "TI.2.3#02",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to render reports based on ranges of system date and time that audit log entries were captured."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-TI.2.3-03",
          "label" : "TI.2.3#03",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to render audit log entry time stamps using UTC (based on ISO 8601)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : true
            }
          ],
          "key" : "EHRSFMR2-TI.2.3-04",
          "label" : "TI.2.3#04",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to authorize emergency access to certain logs based on criteria such as individual work assignment, specific user role, specific reason(s), or a need to access a specific patient's information/record entries according to organizational policy and/or jurisdictional law."
        }
      ]
    }