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.1.7.3 Manage Consents and Authorizations (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.1.7.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>Decisions are documented and include the extent of information, verification levels and exposition of treatment options. This documentation helps ensure that decisions made at the discretion of the patient, family, or other responsible party, govern the actual care that is delivered or withheld. There may be several documents active at any one time that may govern a patient's care. Both clinical and administrative consents and authorizations are considered part of this function. A consent or authorization includes patient authorization for re-disclosure of sensitive information to third parties. Consents/Authorizations for printing should include appropriate standardized forms for patients, guardians, or foster parents. The system must appropriately present forms for adolescents according to privacy rules.</p>
    <p>Some jurisdictions may mandate assent. Assent is agreement by the patient to participate in services when they a legally unable to consent (e.g., an adolescent, an adult with early dementia).</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.1.7.3#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 capture and render an indication that a patient has completed a consent and authorization (e.g., the patient completes an eye surgery -related consent before receiving eye surgery).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#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 capture and render an indication that a patient has withdrawn applicable consents and authorizations.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#03
                </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.2.1.html">CPS.2.1</a> (Support externally-sourced Clinical Documents).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#04
                </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.2.2.html">CPS.2.2</a> (Support externally-sourced Clinical Data).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#05
                </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 scanned consent and authorization paper documents.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.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 present consent and authorization forms on-line.</p>
    </div>

                </td>
            </tr>

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

                    <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 MAY provide the ability to enter consent and authorization forms on-line, with appropriate electronic signature, according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#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 render printable consent and authorization forms/form templates.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY render the consents and authorizations as part of the patient's record during a specific clinical activity, (e.g., a treatment or a surgery).</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system MAY provide the ability to render consents and authorizations chronologically, reverse chronologically, and by type of consent or authorization.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#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 capture an assent for patients who are legally unable to consent.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#12
                </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 the source of each consent, such as the patient or the patient's personal representative if the patient is legally unable to provide it.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                CPS.1.7.3#13
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to manage information regarding the patient's personal representative, advocate, healthcare proxy, legal representative, financially responsible entity or other similar person or entity, including their level of authority to make medical or financial decisions on behalf of the patient.</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.1.7.3"/>
      <version value="2.1.1"/>
      <name value="CPS_1_7_3_Manage_Consents_and_Authorizations"/>
      <title value="CPS.1.7.3 Manage Consents and Authorizations (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="Create, maintain, and verify patient decisions (such as informed consent for treatment or disclosure)."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Decisions are documented and include the extent of information, verification levels and exposition of treatment options. This documentation helps ensure that decisions made at the discretion of the patient, family, or other responsible party, govern the actual care that is delivered or withheld. There may be several documents active at any one time that may govern a patient's care. Both clinical and administrative consents and authorizations are considered part of this function. A consent or authorization includes patient authorization for re-disclosure of sensitive information to third parties. Consents/Authorizations for printing should include appropriate standardized forms for patients, guardians, or foster parents. The system must appropriately present forms for adolescents according to privacy rules.

    Some jurisdictions may mandate assent. Assent is agreement by the patient to participate in services when they a legally unable to consent (e.g., an adolescent, an adult with early dementia)."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-01"/>
        <label value="CPS.1.7.3#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and render an indication that a patient has completed a consent and authorization (e.g., the patient completes an eye surgery -related consent before receiving eye surgery)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-02"/>
        <label value="CPS.1.7.3#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture and render an indication that a patient has withdrawn applicable consents and authorizations."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-03"/>
        <label value="CPS.1.7.3#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function [CPS.2.1](Requirements-EHRSFMR2-CPS.2.1.html) (Support externally-sourced Clinical Documents)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-04"/>
        <label value="CPS.1.7.3#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function [CPS.2.2](Requirements-EHRSFMR2-CPS.2.2.html) (Support externally-sourced Clinical Data)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-05"/>
        <label value="CPS.1.7.3#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture scanned consent and authorization paper documents."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-06"/>
        <label value="CPS.1.7.3#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to present consent and authorization forms on-line."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-07"/>
        <label value="CPS.1.7.3#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to enter consent and authorization forms on-line, with appropriate electronic signature, 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-CPS.1.7.3-08"/>
        <label value="CPS.1.7.3#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render printable consent and authorization forms/form templates."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-09"/>
        <label value="CPS.1.7.3#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY render the consents and authorizations as part of the patient's record during a specific clinical activity, (e.g., a treatment or a surgery)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#6"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-10"/>
        <label value="CPS.1.7.3#10"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render consents and authorizations chronologically, reverse chronologically, and by type of consent or authorization."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-11"/>
        <label value="CPS.1.7.3#11"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture an assent for patients who are legally unable to consent."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#8"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-12"/>
        <label value="CPS.1.7.3#12"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture the source of each consent, such as the patient or the patient's personal representative if the patient is legally unable to provide it."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#9"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.1.7.3-13"/>
        <label value="CPS.1.7.3#13"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage information regarding the patient's personal representative, advocate, healthcare proxy, legal representative, financially responsible entity or other similar person or entity, including their level of authority to make medical or financial decisions on behalf of the patient."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.1.3.3#10"/>
      </statement>
    </Requirements>