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

## : RI.1.1.6 Report (Output) Record Lifecycle Event (Function)

Page standards status: Normative

Raw json | Download

    {
      "resourceType" : "Requirements",
      "id" : "EHRSFMR2-RI.1.1.6",
      "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>Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner.</p>\n<p>Reference: ISO 21089-2018, Section 15.6.</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            RI.1.1.6#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 render Record Entry content (e.g., as a report) retaining original, unaltered content and signature bindings, Action and Record Entry provenance and metadata.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#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 Record Entry extracts, including content, context, provenance and metadata.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#03\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 capture the identity of the patient or the individual subject who is the target of Record Entry content that is presented/reported.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#04\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\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            <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: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>IF the identity of a specific recipient has been stored, THEN the system SHOULD render protected Record Entry content based on established permissions and according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#05\n            </td>\n            <td style=\"padding-left: 4px;\">\n            SHOULD\n            \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: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;\">conditional</span>\n            \n            </td>\n            <td style=\"padding-left: 4px;\" class=\"requirement\">\n                <div><p>IF known and explicit as to Record Entry content being output/reported, THEN the system SHOULD transmit corresponding authorizations and patient consent permissions.</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#06\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-TI.1.6.html\">TI.1.6</a> (Secure Data Exchange).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#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 provide the ability to extract Record Entry content prior to output/report, conforming to function <a href=\"Requirements-EHRSFMR2-RI.1.1.13.html\">RI.1.1.13</a> (Extract Record Entry Content).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#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 de-identify Record Entry content prior to output/report, conforming to function <a href=\"Requirements-EHRSFMR2-RI.1.1.10.html\">RI.1.1.10</a> (De-Identify Record Entries).</p>\n</div>\n                \n            </td>\n        </tr>\n        \n        <tr>\n            <td style=\"padding-left: 4px;\">\n            RI.1.1.6#09\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 render updates (new versions) of Record Entry Content to known recipients of prior versions of that Record Entry Content according to scope of practice, 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-RI.1.1.6",
      "version" : "2.1.1",
      "name" : "RI_1_1_6_Report__Output__Record_Lifecycle_Event",
      "title" : "RI.1.1.6 Report (Output) Record Lifecycle Event (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" : "Report (Output) Record Entries (1 or more instances)",
      "jurisdiction" : [
        {
          "coding" : [
            {
              "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
              "code" : "001",
              "display" : "World"
            }
          ]
        }
      ],
      "purpose" : "Occurs when an agent causes the system to produce and deliver record entry content in a particular form and manner. \n\nReference: ISO 21089-2018, Section 15.6.",
      "statement" : [
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-01",
          "label" : "RI.1.1.6#01",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : false,
          "requirement" : "The system SHOULD provide the ability to render Record Entry content (e.g., as a report) retaining original, unaltered content and signature bindings, Action and Record Entry provenance and metadata."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-02",
          "label" : "RI.1.1.6#02",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to render Record Entry extracts, including content, context, provenance and metadata."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-03",
          "label" : "RI.1.1.6#03",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to capture the identity of the patient or the individual subject who is the target of Record Entry content that is presented/reported."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : true
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-04",
          "label" : "RI.1.1.6#04",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : true,
          "requirement" : "IF the identity of a specific recipient has been stored, THEN the system SHOULD render protected Record Entry content based on established permissions and according to scope of practice, organizational policy, and/or jurisdictional law."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-05",
          "label" : "RI.1.1.6#05",
          "conformance" : [
            "SHOULD"
          ],
          "conditionality" : true,
          "requirement" : "IF known and explicit as to Record Entry content being output/reported, THEN the system SHOULD transmit corresponding authorizations and patient consent permissions."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-06",
          "label" : "RI.1.1.6#06",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL conform to function [TI.1.6](Requirements-EHRSFMR2-TI.1.6.html) (Secure Data Exchange)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-07",
          "label" : "RI.1.1.6#07",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to extract Record Entry content prior to output/report, conforming to function [RI.1.1.13](Requirements-EHRSFMR2-RI.1.1.13.html) (Extract Record Entry Content)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : false
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-08",
          "label" : "RI.1.1.6#08",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to de-identify Record Entry content prior to output/report, conforming to function [RI.1.1.10](Requirements-EHRSFMR2-RI.1.1.10.html) (De-Identify Record Entries)."
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
              "valueBoolean" : true
            }
          ],
          "key" : "EHRSFMR2-RI.1.1.6-09",
          "label" : "RI.1.1.6#09",
          "conformance" : [
            "SHALL"
          ],
          "conditionality" : false,
          "requirement" : "The system SHALL provide the ability to render updates (new versions) of Record Entry Content to known recipients of prior versions of that Record Entry Content according to scope of practice, organizational policy, and/or jurisdictional law."
        }
      ]
    }