HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

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

## : TI.1.3.1 Emergency Access Control (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-TI.1.3.1"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/phrsfmr2/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>Manage emergency access to PHR-S resources.</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>The intent of Emergency Access Control is to mitigate the potential for impeding the provision of care in an emergency situation in accordance with organizational policy.</p>
    <p>For example, emergency access may include:</p>
    <ul>
    <li>Single record entry (e.g., single laboratory results, single document, single view);</li>
    <li>Single patient;</li>
    <li>Single login session, multiple patients;</li>
    <li>Site mode allowing simultaneous emergency access to all users.</li>
    </ul>
    <p>Logging of a user's activities should occur in the audit record/metadata. Reports of emergency access use for follow up are critical for compliance and monitoring.</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>TI.1.3.1#01</span>

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

                    <i>dependent</i>

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to capture emergency access (permission) rules according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#02</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 capture categories of emergency access criteria (e.g., 1) Single record entry such as single laboratory results, single document, single view; 2) Single patient; 3) Single login session, multiple patients; 4) Site mode allowing simultaneous emergency access to all users) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#03</span>

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

                    <i>dependent</i>

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL manage emergency access by individual users based on criteria (e.g., defined rules and categories) according to organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#04</span>

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

                    <i>dependent</i>

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to maintain emergency access time limits according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#05</span>

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

                    <span>MAY</span>

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

                    <span><div><p>The system MAY present periodic reminders to a system administrator to review user's emergency access privileges.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#06</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 a reason for emergency access.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>TI.1.3.1#07</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 render an after action report for follow up of emergency access.</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/phrsfmr2/Requirements/PHRSFMR2-TI.1.3.1"/>
      <version value="2.0.1-ballot"/>
      <name value="TI_1_3_1_Emergency_Access_Control"/>
      <title value="TI.1.3.1 Emergency Access Control (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:42:51+11:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description value="Manage emergency access to PHR-S resources."/>
      <purpose
               value="The intent of Emergency Access Control is to mitigate the potential for impeding the provision of care in an emergency situation in accordance with organizational policy.

    For example, emergency access may include:
    - Single record entry (e.g., single laboratory results, single document, single view);
    - Single patient;
    - Single login session, multiple patients;
    - Site mode allowing simultaneous emergency access to all users.

    Logging of a user's activities should occur in the audit record/metadata. Reports of emergency access use for follow up are critical for compliance and monitoring."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-01"/>
        <label value="TI.1.3.1#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture emergency access (permission) rules according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-02"/>
        <label value="TI.1.3.1#02"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture categories of emergency access criteria (e.g., 1) Single record entry such as single laboratory results, single document, single view; 2) Single patient; 3) Single login session, multiple patients; 4) Site mode allowing simultaneous emergency access to all users) according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-03"/>
        <label value="TI.1.3.1#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL manage emergency access by individual users based on criteria (e.g., defined rules and categories) according to organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-04"/>
        <label value="TI.1.3.1#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to maintain emergency access time limits according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-05"/>
        <label value="TI.1.3.1#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY present periodic reminders to a system administrator to review user's emergency access privileges."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-06"/>
        <label value="TI.1.3.1#06"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture a reason for emergency access."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="PHRSFMR2-TI.1.3.1-07"/>
        <label value="TI.1.3.1#07"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to render an after action report for follow up of emergency access."/>
      </statement>
    </Requirements>