BASIC (01-01)

DI 40525.030 Overview of the CDR Selection and Release Process

A. Process - Automated Direct Release (ADR)

The ADR process works as follows:

  1. Near the beginning of each Fiscal Year (FY), the Office of Continuing Disability Reviews Support (OCDRS) prepares a file for the Office of Systems (OS) to create a file of all “available” direct release continuing disability reviews (CDRs) for the ADR process.

  2. The ADR process allows for regular monthly direct release CDR selections throughout the year based on the file of potential candidates for that FY furnished by OD.

  3. The ADR process is currently set to run one “primary direct release” selection monthly for either Title XVI or Title II and Concurrent Title II/XVI CDRs.

  4. ADR produces a file that will update the Disability Control File (DCF).

B. Process – CDR mailer pull and ship (PAS)

The CDR scannable mailer (form SSA-455-OCR SM) is designed to solicit key information from beneficiaries about their medical condition(s), recent training or education, and any attempts to work. The CDR mailer is intended to act as a screening tool to determine whether the low profile score, indicating that a full CDR is not needed, is valid. Cases that fall into the low range are selected to receive a CDR mailer first before any other CDR actions are taken. That is, while most returned and completed CDR mailers will not require any further CDR actions, some may require additional manual actions or result in a need for a full CDR. These latter cases are commonly referred to as “pull and ship” CDR or DO CDR actions.

C. Process - Automated Continuing Investigation of Disability (ACID) and the Master Beneficiary Record (MBR)

  1. Within the PCs, the DCF controls the title II continuing disability reviews (CDRs) for direct release and CDR Mailer(s).

  2. DCF produces a PKGRAPE file (based on most current folder location within the Processing Center Action Control System (PCACS)) which creates the paper alerts for the Megasite and Caves to pull and ship folder(s).

  3. DCF also determines if a PC has the folder(s) and sends an alert to them.

  4. Updates of CDR or CDR mailer processing are recorded on the DCF and can be queried on the CDR Query (QCDR) screen (see MSOM CDR 001.004) of the DCF.

  5. The update to the CDR PC Input (IPCA) screen creates a transaction which establishes a Title II or Concurrent Title II/XVI direct release on the DCF.

  6. This update to the DCF can take from 24 - 48 hours after the IPCA screen input.

D. Process – Disability Control File (DCF)

The following considerations apply to the DCF:

  1. The DCF controls medical direct release reviews initiated by Central Office (CO) and CDR Mailer(s). (See (Modernized Systems Operations Manual) MSOM CDR 001.001 for more detailed procedures on the DCF.)

  2. Effective August 30, 1999, Title II direct release CDRs and CDR Mailers were included in the Continuing Disability Review Control File (CDRCF), and in the Office of Information Management's (OIM) workload and management information (WMI) screens within SSA's mainframe. Subsequently, the CDRCF was incorporated into the Disability Control File (DCF).

  3. Title II CDRs are controlled under the client's own social security number (COSSN) which equates to the claimant account number (CAN) for PRIMARY or beneficiaries' own account number (BOAN) for Auxiliaries from the MBR.

  4. In title II cases involving primary beneficiaries, the Primary Beneficiary/Number Holder's COSSN and claim Social Security Number (CLMSSN) will be the same.

  5. To access a Title II CDR, a component enters the CAN and appropriate beneficiary identification code (BIC).

  6. The COSSN, as well as the active CAN and BIC, will be propagated onto the DCF Entitlement (ECDR) screen.

  7. Title II Medical CDRs will be reflected as TII or TII/TXVI Concurrent on the ECDR screen of the DCF.

  8. The DCF on-screen legend will read either "TII” or "TII/TXVI," depending on the case situation.

To Link to this section - Use this URL:
DI 40525.030 - Overview of the CDR Selection and Release Process - 03/29/2013
Batch run: 03/29/2013