Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design: Capture Fields Necessary to Automate Pension Eligibility Determinations in the 686c-674 #8777

Closed
4 tasks done
jason-gcio opened this issue May 5, 2020 · 5 comments
Assignees
Labels
design vsa Work associated with the Veteran-facing Services Applications contract vsa-ebenefits eBenefits migration and transformation

Comments

@jason-gcio
Copy link
Contributor

jason-gcio commented May 5, 2020

Add Mandated Pension Questions to 686c

Implement after launch, but Design can start thinking about it sooner

Description

Pension LOB has mandated updates to BGS/ RBPS to enable simple processing of Pension applications via dependency claims. This presents several challenges, since the 686c does not ask questions about income or pension eligibility.

This will have a few different parts, across domains that are all related. (See mini-epic for this: #7759)

Considerations

  • Helper text for context will be extremely important, especially given the fact these are financial related questions

Outcomes

  • When adding dependent, ask an additional (optional) question: "Did this dependent have income in the last 365 days?"
    Could be slipped in as a Yes / No in that section?
  • Ask a global (optional) question: "Did the household have a total income of less than $XXX in the last tax year?"
    Needs more thought...Whole separate page? Include Veterans Info capture screen?

Tasks

  • Design UX for these questions. Are they inline with existing questions or part of a new "Pension" section? Is a gate needed that only shows these questions to eligible users?
  • Get final content for the questions and helper text
  • Determine which information collection can be leveraged for these questions and add it to the beginning of the application (with the 686c & 674 information collections)

Acceptance Criteria

  • A mockup has been created, or an existing mockup has been updated and noted in the 686 Mockup Changelog
@jason-gcio jason-gcio added design vsa Work associated with the Veteran-facing Services Applications contract vsa-ebenefits eBenefits migration and transformation labels May 5, 2020
@jason-gcio jason-gcio added this to the eBenefits Sprint 21 milestone May 6, 2020
@sporeboy
Copy link
Contributor

Here is what I have at the moment...

For the individual dependent income question:

  • Added yes/no radio button to the child detail screen
  • Added yes/no radio button to the separated spouse screen
  • This is not required
  • Explanatory copy may be added later
  • conditional text box can be added to enter number if "yes"

For the household income question:

  • Added new "chapter" to end of add-child and add-spouse workflows
  • Has some explanatory copy regarding pension vs. disability
  • Text and/or tell-me-more accordion should be revised when we get clarification from stakeholders
  • This is not required
  • Seems the threshold income figure may be dynamic

Looked here for the formula to determine houhold income limits: https://www.va.gov/pension/veterans-pension-rates/

@sporeboy
Copy link
Contributor

The three "add dependent" workflows are:

  • Add child
  • Add spouse
  • Add student

Confirmation needed as to whether the 674 workflow will require this info as well.

@sporeboy
Copy link
Contributor

Did not add additional financial questions to 674... The form does include an accounting of the students income.

So, should we add the net worth question module/chapter to the 674 workflow? Or should we assume the NW question was answered when the child was added originally? If the student is being added now but has never before been claimed, the user must go through the add child workflow. In that case, the net worth question will appear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design vsa Work associated with the Veteran-facing Services Applications contract vsa-ebenefits eBenefits migration and transformation
Projects
None yet
Development

No branches or pull requests

2 participants