If the prior claim is pending at the AC, and a claimant has
evidence of a new critical or disabling condition with onset after
the date of the hearing decision, the claimant may request to file
a new application.
A “new” critical or disabling condition generally
means that onset occurred after the date of the hearing decision
on the prior claim. Though not exhaustive, SSA considers any condition
that meets the criteria of a listed impairment or meets the criteria under Terminal
Illness (TERI), Compassionate Allowances (CAL), or Presumptive Disability/Presumptive
Blindness (PD/PB) a “critical or disabling condition.”
If the claimant requests an exception to file a new disability
application while a request for review is pending, the AC, through
the Office of Appellate Operations (OAO) Executive Director's Office
(EDO), must approve the request before the claimant can file a new
application. If the EDO does not approve the request, the claimant
may not file a new application until the AC completes its action
on the request for review of the prior claim or the claimant chooses
to withdraw the request for review, as explained in HALLEX HA 01340.003.
See HALLEX HA 01330.006 and HA 01350.020 for AC actions regarding
protective filing dates when the claimant does not request an exception
but submits new and material evidence. For protective filing relating
to withdrawal requests, see HALLEX HA 01340.003 D.
1. How Exception Requests
are Submitted
Exception requests may be submitted in any of the following
ways:
•
A representative or
claimant may submit an exception request to the FO. The
FO follows the procedures in POMS DI 51501.015C to notify
the EDO of the request.
•
A representative or claimant may contact the AC
via telephone to submit an exception request. Telephone requests
are handled by OAO's Claimant and Public Assistance Branch (CPAB)
at 877-670-2722, using the same general procedures noted in POMS DI 51501.015.
•
A representative or claimant may submit a written
request directly to the AC. However, these requests are discouraged
due to delay in processing time. See HALLEX HA 01195.001 C.3. below.
Some members of the public may submit
a written request to an OAO email box. Due to firewall and privacy
issues, the EDO will not reply by email to members of the public.
To avoid significant delay in processing or misrouting exception
requests, the staff handling the email account should notify the
individual by telephone that future requests should be directed
to the FO or CPAB.
2. EDO Response to Exception
Requests
The EDO generally evaluates and responds to exception requests
from the FO or CPAB within two days. After the EDO evaluates the
request, an email response is sent to the FO or CPAB, the file and
eView are documented (when applicable), and the EDO enters one of
the following case characteristics into the Appeals Review and Processing
System (ARPS):
•
SUBN (Subsequent Application
Not Permitted)
•
SUBR (Subsequent Application Permitted)
When the EDO is notified of a written request that was submitted
directly to the AC (see HALLEX HA 01195.001 C.3. below), the
EDO will act on the request as soon as possible to avoid further
delay. After reviewing the request, the EDO will take necessary
action to notify the representative or claimant of the exception
decision.
3. Branch Actions When
Exception Is Submitted to Branch or a New Application Is Pending
Without Approved Exception
If a representative or claimant submits a written exception
request directly to the AC, the person who first identifies the
request must immediately make a notation in the "remarks" section in ARPS
and send an email to ^DCARO OAO. The email must include the claimant's
name, Social Security Number (SSN), and a brief explanation, specifically
noting the location of the written request in the file. The EDO will
provide appropriate guidance to the employee and/or the employee's supervisor
after evaluating the request.
b. Erroneous Subsequent
Applications
OAO produces a monthly report to identify cases where a subsequent
application was erroneously accepted after July 28, 2011 (i.e., the
subsequent application is for the same title and benefit type as the case
pending with the AC, and there is no case characteristic for an exception
noted in ARPS). This report is used to notify the FO regarding erroneous
subsequent applications. OAO staff does not need to separately notify
the FO if an analyst or adjudicator discovers an erroneous subsequent
application.
The FO will continue processing the subsequent application
if an initial determination has been issued. If the subsequent application
has reached the hearing level and the AC action is still pending,
the HO will handle the claim as outlined in HALLEX HA 01195.005.
The analyst will add a remark in ARPS and continue processing the request
for review using the procedures in HALLEX HA 01195.025 or HA 01195.030.
The AC will not add a SUBN or SUBR case characteristic to these
cases. However, if the subsequent claim is pending at the hearing level, the
AC will add a SUBA (R/H of Sub App Pending in HO) case characteristic.