TN 4 (10-16)

DI 30007.155 The Request for Program Consultation (RPC) Resolution and Post-Resolution Actions

A. Timeframe for issuing the RPC resolution

RPC’s goal is to issue a resolution within 14 calendar days of receipt of the DDS’s RPC submission. However, a variety of factors may affect this goal, including current caseloads, available staff, the size of the RPC case file, and whether there is a need for additional medical, vocational, or policy input.

B. The RPC resolution is SSA’s official response

The RPC resolution is the result of the three-member RPC panel discussion vote. The resolution is binding on both the DDS and the DQB involved. The components are required to take the actions identified in the RPC resolution.

The panel members base the decision to affirm or rescind a deficiency on whether the DDS’s development, documentation, and determination are reasonable in relation to program instructions. These are the same criteria discussed in OQR’s Quality Review Standard in GN 04440.007.
The ODP RPC discussion panel member drafts the final RPC resolution document, sends it to RPC’s technical expert for editing and approval, and completes all remaining RPC tool screens. Once approved, the ODP RPC panel discussion member uploads the document into the RPC tool and submits the completed case for closure. Upon closure, the RPC tool automatically emails notification to the involved DDS, DQB, and Center for Disability (CD) that the resolution is available online. The tool also automatically sends a copy of the resolution to the certified electronic folder, to become a part of the official claim file.

C. DDS actions after RPC resolution

If there are actions for the DDS, the DDS will immediately take the action(s) specified in the RPC resolution and finish processing the case. Once RPC has issued an RPC resolution, it is the DDS’s responsibility to code the Rebuttal field in their legacy system before routing the case back to the DQB. For all RPC cases, the DDS must enter “1” in the Rebuttal field.

This entry propagates to the pending receipt list in the Disability Case Adjudication and Review System (DICARS) for easy identification of rebuttals. This action ensures the DQB will give the case priority handling. The DDS must transfer the case to the DQB and input the rebuttal code even if the RPC resolution did not direct corrective action, in order to demonstrate compliance with RPC guidance.

The DDS will follow current procedures for processing and returning the case to the DQB to update their DICARS database with the RPC resolution.

D. DQB actions after RPC resolution

Upon receiving the case back from the DDS, the DQB will:

  1. Immediately take the actions specified in the resolution regarding the deficiency;

  2. Review the corrected case for accuracy, ensuring the DDS and the DQB completed the actions identified in the resolution;

  3. E-mail notification to RPC (include the RPC case number in the subject line) at “^ODP OPCA Controls” to the attention of the Director when:

    • The DDS has not completed actions identified in the resolution and informal attempts to resolve the issue with that component are unsuccessful, or

    • The corrected determination is inaccurate.

  4. Send email confirmation of post-RPC deficiency affirmations, modifications, or rescissions to the DDS, the CD, and OQR.

  5. When a resolution does not support either the DDS or the DQB, handle and report on this universe of claims (“Wrong Deficiency Cited”) as follows:

    • Capture case outcomes on a report under the category, “Agency Deficiencies Cited”; and

    • Ensure the OQR database and all reports reflect the resolution findings.

E. Follow-up questions

Although the RPC resolution is final, components may submit questions to RPC for further clarification of an RPC resolution. Components should send follow-up questions to RPC (include the RPC case number in the subject line) using the “^ODP OPCA Controls” mailbox. RPC will respond to the inquirer via email, cc’ing ODD, OQR and CD. RPC will also attach the question and response as an additional document to the case in the RPC Tool.

NOTE: RPC must receive follow-up question within ten business days of the date of the RPC resolution.

F. A follow-up question indicates program instructions may not support the original resolution

In rare situations, a follow-up question may cite policy, procedures, or published instructions that indicate program instructions may not support the original resolution. When needed, RPC will refer the case to the appropriate ODP policy component for guidance. If the policy component determines that program instructions do not support the original reso