Leaders in the field are seeing non-DRAS stations processing requests to change dependency (EP130) information which complicates their in-progress processing of IDES claims (EP689). We need to make sure that submissions via the VA.gov 686c form route requests to the appropriate DRAS station using the following logic:
Change request: set a condition in the VA.gov 686c application when there is an active IDES claim (EP689) so that any dependency change requests (EP130) submitted through electronic claims submission service be Service Branch routed to appropriate DRAS for addressal.
EVSS has proposed adding a call to BGS to see if the user has a pending claim with EP code 689. If there is, then the new claim is routed to either RO 346 or 304 based on user’s branch of service. When the branch of service is "Army" the claim is routed to RO 346. All other branch of service values would get routed to RO 304.
Otherwise, the claim gets the RO based on the previous business rules.
Suggested approach
This is the snipped of code EVSS used to implement the proposed logic for calls made through SEP:
Background
Leaders in the field are seeing non-DRAS stations processing requests to change dependency (EP130) information which complicates their in-progress processing of IDES claims (EP689). We need to make sure that submissions via the VA.gov 686c form route requests to the appropriate DRAS station using the following logic:
Change request: set a condition in the VA.gov 686c application when there is an active IDES claim (EP689) so that any dependency change requests (EP130) submitted through electronic claims submission service be Service Branch routed to appropriate DRAS for addressal.
EVSS has proposed adding a call to BGS to see if the user has a pending claim with EP code 689. If there is, then the new claim is routed to either RO 346 or 304 based on user’s branch of service. When the branch of service is "Army" the claim is routed to RO 346. All other branch of service values would get routed to RO 304.
Otherwise, the claim gets the RO based on the previous business rules.
Suggested approach
This is the snipped of code EVSS used to implement the proposed logic for calls made through SEP:
if ("689".equalsIgnoreCase(selection.getEndProductTypeCode())) if("PEND".equalsIgnoreCase(selection.getStatusTypeCode())) { if("Army".equalsIgnoreCase(branch)) roNumber = "346"; else roNumber = "304"; break; }