search

department-of-veterans-affairs / caseflow

Caseflow is a web application that enables the tracking and processing of appealed claims at the Board of Veterans' Appeals.
Other
54 stars 18 forks source link

AMA Intake | UX Priorities #13840

Closed carodew closed 4 years ago

carodew commented 4 years ago

@carolaponce commented on Fri Oct 19 2018

Taking Abby's issue and continue to use this list as a source of UX deliverables + priorities.

833

Working On****

Initiative: Supporting intake and disposition tracking for non-compensation business lines

Non-compensation functionality, which is basically a modified version of our compensation features. The main pieces are intake, dispositions, and possibly a generic queue/work distribution mechanism. Next steps: refine draft designs. Initial Demo done - will collect feedback from all teams and push screens to production (Date end of October?)

Process documentation #1028

Initiative: Alerting users about invalid AMA issues

Flag ineligible/untimely/duplicate issues to users, so they can either override the check and process the form anyway, or notify the Veteran that they submitted a form with ineligible issues. | Suzanne finished these screens. I need to figure out if any of these screens need modifications for Non-comp.

Next Priorities****

Initiative: User Research Plan for December Pilot

Can we schedule this in Oakland? @shanear? What to plan for (WIP)

Initiative: Allow withdrawing issues for HLRs and SCs

Initiative: Tracking power(s) of attorney at the issue level

Veterans will be able to appoint a per-issue representative, using the 21-22a form, so we want to create an intake path for this form. This functionality is somewhat standalone, and will likely involve close collaboration with Queue designers. Timing: sometime prior to February. For VBA, they'll view the POA in VBMS; for the Board, they'll view it in Queue.

Initiative: searching/viewing status of SCs/HLRs/Appeals

Queue will add information about HLRs/SCs to Queue - still needs definition (Shane has some thoughts on what might go here, I think the plan is for Queue to develop it, but we need to know what they need)

Finished Work

Initiative: Establishing AMA reviews

This is the "core path" for establishing AMA appeals. Most of the backbones of this work is complete, but there are some nitty-gritty details/scenarios that still require design work. Carola will own setting up any future user testing sessions. The bulk of this work should be ready for testing during the pilot (likely ~December 2018).

Initiative: Editing reviews post-intake

Users can add or remove SC/HLR issues after intake, via a link in VBMS to a page in Caseflow. For appeals, we'll need to collaborate with the Queue team, who will own the flow for attorneys to edit issues in Queue after intake. This is mostly finished on the VBA side; keep an eye on opportunities to collaborate with Queue. This is currently in development (almost finished, as of Oct.)

Initiative: supporting opt-ins from the legacy system to AMA

A Veteran can opt their legacy appeal into AMA after receiving an SOC/SSOC decision from VBA. We'll need a way for them to identify opt-ins and close out VACOLS issues.

Parking lot

@carolaponce commented on Wed Oct 24 2018

From @shanear

department-of-veterans-affairs/caseflow#7383 department-of-veterans-affairs/caseflow#5695 department-of-veterans-affairs/caseflow#7515

1023

@jimruggiero commented on Sat Sep 07 2019

@leikkisa Putting this list on your radar for Foxtrot roadmap prep I'm going to start when I return from PTO. Prep work will be to organize all that's currently in the backlog, for Foxtrot and then meet with you to review and get your input on tech debt/prioritization and finesse my prep docs. I'd like your thoughts on the unchecked items above: is the list still accurate? any of this roll into tech debt/improvements? Not an immediate priority, but wanted you to have a few weeks to think on this. I expect to have my stuff ready for us to discuss between 9/25-10/1.

@jimruggiero commented on Sat Sep 07 2019

@carodew mind if I put this in your backlog until we determine next steps for this outstanding work?

@carodew commented on Mon Sep 09 2019

@jimruggiero sure, it can hangout with us designers. This seems like something you and I should talk through to figure out what the intent is, current needs, and break it down into smaller chunks?

@jimruggiero commented on Mon Sep 09 2019

@carodew Agreed. I'm thinking we can chat late next week or the week after. There's no rush on this.

@carodew commented on Tue Mar 31 2020

@jimruggiero should we bounce this back to @msj0nes and @rutvigupta-design to determine relevancy/next steps? This seems like a pre-epic or pre-product brief set of notes, but if it's not something to prioritize in the short term I think labeling and closing is probably the best approach.

@rutvigupta-design commented on Tue Mar 31 2020

@carodew @jimruggiero I would love to work with @msj0nes to break this into smaller incremental improvement tickets.

msj0nes commented 4 years ago

I believe this should be closed. Design work for foxtrot will be via more current stakeholder communications.

msj0nes commented 4 years ago

Closing. This isn't work currently prioritized . Will depend on more recent stakeholder feedback to craft UX priorities.