-
Notifications
You must be signed in to change notification settings - Fork 19
VSOs
Matt Wagner edited this page Jun 10, 2021
·
3 revisions
Veterans Service Organizations have the following overall goals:
- Assist Veterans in moving through the appeals process
- Helping the veteran by giving reminders and advice about forms, hearings
- Representing Veterans who have elected a hearing at their hearing.
There are two groups of VSOs: National and Field (state/county).
- National VSOs write and submit Informal Hearing Presentations (IHPs) for Veterans who have not elected a hearing. Veteran Service Organizations (VSOs) currently access their appeals work in VACOLS. They also have access to the Veteran's claims folder in VBMS.
- Field VSOs currently have a read only view of VACOLS, so that will continue with Caseflow.
Under AMA, they will still be writing IHPs. The Board does not need to wait for an IHP to be submitted, though it currently tends to wait.
If a Veteran has chosen the Direct Review lane under AMA, meaning they are not submitting any new evidence, the Board has a goal timeframe of deciding the case within 365 days from the NOD date. This timeframe will take precedence over waiting for the IHP to be submitted.
- Facilitate VSOs knowledge of actions they could take for their Veterans' cases
- e.g. submit IHP (VSOs are assigned appeals in VACOLS for this today)
- e.g. prepare for hearing (VSOs are not assigned appeals in VACOLS for this today)
- Provide VSOs with as lightweight of functionality as required before AMA effective date
- We could use a lightweight MVP for VSOs
- Build queue for VSO users - see a list of appeals assigned to that VSO
- Search for appeals, only see appeals at that VSO
- As a VSO representative, I need to be able to see all Veterans' appeals that have chosen me as their representative. (Case search?)
- When a VSO searches for an appeal, the results can only show Veterans' appeals that have chosen them as their VSO.
- As a VSO representative, I need to be able to access Veterans' claims folders in VBMS that have chosen me as their representative.
- As a VSO representative, I want to be notified of my Veterans' upcoming hearings, so I can contact them, prepare for the hearing, and help the Veteran through the process. (connect with hearing schedule? a view of hearing prep?)
This is likely where the bulk of the functionality lives.
- As a VSO representative, I need to see which appeals have been routed to me (specifically) for an IHP, so I can quickly write it and don't hold it up in the appeals process.
- As a VSO representative, I need to see which AMA or legacy docket the appeal is in, so I know how quickly I need to complete my work (Direct Reviews have a 365 day goal).
- When a VSO representative has finished writing the IHP, they need transfer the case back to the Board, so that the attorney and judge can consider it for the BVA decision.
URLs:
- PVA:
appeals.cf.ds.va.gov/organizations/pva
- American Legion:
appeals.cf.ds.va.gov/organizations/american-legion
- DAV:
appeals.cf.ds.va.gov/organizations/disabled-american-veterans
- VVA:
appeals.cf.ds.va.gov/organizations/vietnam-veterans-of-america
- AMVETS:
- VFW:
https://appeals.cf.ds.va.gov/organizations/veterans-of-foreign-wars
- What data can/can't VSOs see that Board employees can?
- What access hurdles do we need to get over first? (none; requisite users have CSS access)
- How does Jed currently know which employees are with which VSOs?
- Can we scope out case assignment to employees within VSO organizations to complete specific tasks? (Jed's case assignment program does this for one VSO)
- Does VSO access equate to access for other representatives that use single sign-on? (https://github.com/department-of-veterans-affairs/caseflow/issues/5581#issuecomment-394783431)
- What is our strategy for answering VSO questions about getting access to Reader?
- What can we do / how does the Board want to manage timeliness by VSOs? The Board has mentioned not requiring or waiting for IHPs, especially for Direct Docket cases and the 365 day goal.
- What is our stance on providing VSOs access to the hearing schedule and how might it fit into the Hearing Schedule roadmap
- Jed's answers to a few questions - https://github.com/department-of-veterans-affairs/dsva-vacols/issues/9
- VSO Mural from Queue discovery
- VSO Research 2018
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
-
Caseflow-Team
- Tier 4
- Bat Team
- Technical Documentation
- Backend Code Patterns
- Backend Working Group
- FACOLS, VACOLS DB Schema
- Asyncable Models
- External Data: where and why
- Data Fetching Scripts
- Caseflow Data Model and Dictionary
- User Access Permissions
- Controller Schemas
- Constants
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks