Description I:

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.

Criteria N:
TI.1.3.1#01 SHALL dependent

The system SHALL provide the ability to capture emergency access (permission) rules according to scope of practice, organizational policy, and/or jurisdictional law.
TI.1.3.1#02 MAY dependent

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.
TI.1.3.1#03 SHALL dependent

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.
TI.1.3.1#04 SHALL dependent

The system SHALL provide the ability to maintain emergency access time limits according to scope of practice, organizational policy, and/or jurisdictional law.
TI.1.3.1#05 MAY

The system MAY present periodic reminders to a system administrator to review user's emergency access privileges.
TI.1.3.1#06 SHALL

The system SHALL provide the ability to capture a reason for emergency access.
TI.1.3.1#07 SHALL

The system SHALL provide the ability to render an after action report for follow up of emergency access.
<status value="active"/> <date value="2025-12-19T08:44:27+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="Manage emergency access to EHR-S resources."/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="US"/> </coding> </jurisdiction> <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."/> <derivedFrom value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-TI.1.3.1"/> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#1"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#2"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#3"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="true"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#4"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#5"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#6"/> </statement> <statement> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent"> <valueBoolean value="false"/> </extension> <extension url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info"> <valueCode value="NC"/> </extension> <key value="DHFPR2-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."/> <derivedFrom value="TI.1.3.1#7"/> </statement> </Requirements>