HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## : AS.3.2.1 Manage Consents and Authorizations from a PHR (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-AS.3.2.1"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Maintain the Consents and Authorization directives/statements from the patient's PHR.</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Provide the ability to manage Consents and Authorizations from a Personal Health Record including manage access control for individual elements of records to which the Consent or Authorization applies.</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

        <table id="statements" class="grid dict">

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage Consents and Authorizations from a Personal Health Record according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to render the identity and relationship (e.g., Dr. Smith, primary care physician or Jane Doe, sister-in-law) of the person(s) for which the Consent or Authorization applies.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage access control to the patient's information as specified by the Consent or Authorization according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage access control for the section(s) of the patient's record to which the Consent or Authorizations applies according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#05</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to manage access control for individual elements of records to which the Consent or Authorization applies according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#06</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to manage access control for the time period within which the Consent or Authorization applies according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>AS.3.2.1#07</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to render Consents and Authorizations.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url
           value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-AS.3.2.1"/>
      <version value="2.1.1-ballot"/>
      <name value="AS_3_2_1_Manage_Consents_and_Authorizations_from_a_PHR"/>
      <title
             value="AS.3.2.1 Manage Consents and Authorizations from a PHR (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:04:36+11: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="Maintain the Consents and Authorization directives/statements from the patient's PHR."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Provide the ability to manage Consents and Authorizations from a Personal Health Record including manage access control for individual elements of records to which the Consent or Authorization applies."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-AS.3.2.1-01"/>
        <label value="AS.3.2.1#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage Consents and Authorizations from a Personal Health Record 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-AS.3.2.1-02"/>
        <label value="AS.3.2.1#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render the identity and relationship (e.g., Dr. Smith, primary care physician or Jane Doe, sister-in-law) of the person(s) for which the Consent or Authorization applies."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-AS.3.2.1-03"/>
        <label value="AS.3.2.1#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage access control to the patient's information as specified by the Consent or Authorization 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="true"/>
        </extension>
        <key value="EHRSFMR2-AS.3.2.1-04"/>
        <label value="AS.3.2.1#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage access control for the section(s) of the patient's record to which the Consent or Authorizations applies 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="true"/>
        </extension>
        <key value="EHRSFMR2-AS.3.2.1-05"/>
        <label value="AS.3.2.1#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage access control for individual elements of records to which the Consent or Authorization applies 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="true"/>
        </extension>
        <key value="EHRSFMR2-AS.3.2.1-06"/>
        <label value="AS.3.2.1#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage access control for the time period within which the Consent or Authorization applies 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-AS.3.2.1-07"/>
        <label value="AS.3.2.1#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render Consents and Authorizations."/>
      </statement>
    </Requirements>