DR | Create a remediation plan for each category of failed submissions

[saderagsdale]

Value Statement

As a Veteran who submitted a claim on VA.gov that experienced a silent failure I want to know that all data I shared was received and taken into account during claim development So that my claim decision reflects the data I intended to share.

---

Background Context

Remediation plans, known as Code Yellows, will be created for all affected decision review types. This process typically involves:

• Standing up a team of business line stakeholders to create a remediation plan and working group
• Resubmitting original data in batches using scripts
• Sending communications to Veterans so they're aware of the impact and next steps
• Getting stakeholder approval to close the effort

Tech Tasks

• [ ] Discuss with Thomas Blackwell to check for existing CY processes/best practices
• [ ] Setup meeting with core stakeholder group to kickoff the process
• [ ] Join weekly code yellow scrum to share updates and identify support resources
• [ ] Determine what data needs to be re-submitted w/ business line
• [ ] Decide how to re-submit the data w/ the business line
• [ ] Confirm resubmission and data storage are complete w/ the business line

Definition of Ready

• [ ] We've documented the exact nature of all of our silent failures

Definition of Done

• [ ] All failures have been remediated
• [ ] Reviewed and approved by product owner

[shaunburdick]

This will be ready once we meet with the VBA/BVA teams and generate a playbook

[eileen-coforma]

Met up with VBA and BVA last week, pulled the latest failures other than the silent ones that we can't control. Set up a process for remediation in the future.

[eileen-coforma]

Sent over some more silent downstream failures for SC and HLR and added to spreadsheet to let the teams know.