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

[Discovery] How will Claim Contextualization UI updates impact other claims? #84173

Closed
3 tasks done
skylerschain opened this issue Apr 4, 2024 · 4 comments
Closed
3 tasks done
Assignees
Labels
benefits-management-tools aka. squad 1 (previously known as Claim Status Tools) Claim Status Tool design discovery

Comments

@skylerschain
Copy link
Contributor

skylerschain commented Apr 4, 2024

Background

There are many different claim types that exist in CST: Full list.

The current understanding is that the same UI is used for all claim types. So updating it for disability compensation claims (what we are working on now as part of Claim Contextualization) will update it for all.

We need to determine:

  • Will updating the UI for disability compensation claims update it for all claims? (Assuming yes)
  • What will other claim types look like when we update the Overview tab?

Open questions

  • What are the most common claim types in CST? (Jerek started a dashboard)
  • Is there a way to create more bespoke experiences for other claim types? Can there be unique content for the accordion based on the claim? Or we could take the Top 5 claim types and make more bespoke experiences for those. This would be its own epic.

Acceptance criteria

  • Answer the open questions above
  • We have captured current UI states of claim types not served by the compensation claim phases
  • Identify strong candidates for a different claim process description in CST
@skylerschain skylerschain added the benefits-management-tools aka. squad 1 (previously known as Claim Status Tools) label Apr 4, 2024
@uxgary uxgary self-assigned this Apr 29, 2024
@uxgary
Copy link
Contributor

uxgary commented May 22, 2024

Finished reviewing docs shared by the pension team. At this moment, it looks like the new UI could work with pension claims because pension shares a similar claims process as disability (initial review, gathering evidence, review of evidence).

I’m creating some follow up questions for the pension team to see if there’s any info on what happens once the claim leaves the VSR. (rating, preparation for notification, final review)

@jerekshoe jerekshoe transferred this issue from department-of-veterans-affairs/vets-website May 29, 2024
@uxgary
Copy link
Contributor

uxgary commented May 30, 2024

Answers to some of the open questions.

Is there a way to create more bespoke experiences for other claim types?
Yes, we will be able to show the Accordion UI on a claim bases. In other words, as part of the initial launch, we will only launch the new UI (Accordion UI) for disability claims.

Can there be unique content for the accordion based on the claim?
Yes, members of the engineering team has confirmed we can create bespoke content for different claim types.

Identify strong candidates for a different claim process description in CST
After conduct our meeting with the Pension team, we have concluded that the pension claims process follows virtually the same process steps as disability claims. The one key difference as it pertains to claim step names is Rating. Pension claims does not have Rating in the same sense as disability claims because disability claims give a percentage rating (disability rating) that is factored into award amount. Contrastingly, pension claim has a "Pension rate", based on income and number of dependents. Consequently, this instead of "rating" we would use "pension rate" as a step title.

We are in the process of identifying additional candidates as we meet with other teams.

@uxgary
Copy link
Contributor

uxgary commented May 30, 2024

Created an epic in places of this issue, because we have to conduct discovery work on multiple claim types individually

@uxgary uxgary closed this as completed May 30, 2024
@uxgary
Copy link
Contributor

uxgary commented May 30, 2024

Screenshots from the current pension UI.

Overview-Of-October-1-2009-Pension-Claim-Veterans-Affairs
Files-For-October-1-2009-Pension-Claim-Veterans-Affairs
Status-Of-October-1-2009-Pension-Claim-Veterans-Affairs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benefits-management-tools aka. squad 1 (previously known as Claim Status Tools) Claim Status Tool design discovery
Projects
None yet
Development

No branches or pull requests

4 participants