Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## : S.3.3.1 Manage Consents and Authorizations (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.3.3.1"/>
      <meta>
        <profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <table id="statements" class="grid dict">

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

                    <span>S.3.3.1#01</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to capture Consents and Authorizations according to organizational policy and/or jurisdictional law.</p>
    </div></span>

                    Satisfied by:<ol>

                        <li>https://www.hl7.org/fhir/pacio - advanced directives.html</li>

                    </ol>

                </td>
            </tr>

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

                    <span>S.3.3.1#02</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to determine the entity to which the Consent or Authorization applies.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#03</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to determine a section or sections of the PHR Account Holder's information to which the Consent or Authorizations applies (e.g., the demographic data section, the medication list, or history of illness section).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#04</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 determine individual elements of records to which the Consent or Authorization applies.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#05</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 determine the time period within which the Consent or Authorization is enforced.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#06</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 Consents and Authorizations to another PHR-S, an EHR-S, or elsewhere (e.g., to a printer).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#07</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 import Consents and Authorizations through electronic interfaces (e.g., scanning or faxing).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.3.1#08</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 link to external Consents and Authorizations (e.g., in an external EHR-S).</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.3.3.1"/>
      <version value="0.1.0"/>
      <name value="S_3_3_1_Manage_Consents_and_Authorizations"/>
      <title value="S.3.3.1 Manage Consents and Authorizations (Function)"/>
      <status value="active"/>
      <date value="2024-01-31T14:45:34+00:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="The PHR Account Holder may have Consents and/or Authorization directives that allow or prohibit certain entities from access to part or all of the PHR. Directives may take different forms including documents or system flags on Consent Authorization. The Consent or Authorization requirements would be maintained in accordance with user role, organizational policy and/or jurisdictional law. Based on that, the Consent or Authorization might contain the details of the entity that may be authorized to use, or may be prohibited from using the PHR-S. The Consent or Authorization may detail to the record, field or class, the data available to be used or disclosed. The entities that the Consent or Authorization applies to may or may not be current PHR Account Holders of the PHR-S."/>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-01"/>
        <label value="S.3.3.1#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture Consents and Authorizations according to organizational policy and/or jurisdictional law."/>
        <satisfiedBy
                     value="https://www.hl7.org/fhir/pacio - advanced directives.html"/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-02"/>
        <label value="S.3.3.1#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to determine the entity to which the Consent or Authorization applies."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-03"/>
        <label value="S.3.3.1#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to determine a section or sections of the PHR Account Holder's information to which the Consent or Authorizations applies (e.g., the demographic data section, the medication list, or history of illness section)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-04"/>
        <label value="S.3.3.1#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to determine individual elements of records to which the Consent or Authorization applies."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-05"/>
        <label value="S.3.3.1#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to determine the time period within which the Consent or Authorization is enforced."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-06"/>
        <label value="S.3.3.1#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render Consents and Authorizations to another PHR-S, an EHR-S, or elsewhere (e.g., to a printer)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-07"/>
        <label value="S.3.3.1#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to import Consents and Authorizations through electronic interfaces (e.g., scanning or faxing)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.3.1-08"/>
        <label value="S.3.3.1#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to link to external Consents and Authorizations (e.g., in an external EHR-S)."/>
      </statement>
    </Requirements>