-
Notifications
You must be signed in to change notification settings - Fork 19
Deciding issues for lines of business
Not all business lines use VBMS. For those that don't, they also need a way of processing decision reviews. All decision review tasks for non-VBMS business lines appear in priority order on the business line's queue. Each business line's queue has a separate url, for example https://appeals.cf.ds.va.gov/decision_reviews/insurance. The volume of decision review related work for these business lines was determined to be low enough to where this unified view of all work is expected to be manageable. There has been a "Caseflow Administer" appointed for each non-VBMS business line to manage incoming tasks, and if necessary enter them into the task management system specific to that business line.
NOTE: This is the list of business lines that do and don't use VBMS:
Use VBMS: Compensation, Pension
Don't use VBMS: NCA (National Cemetery Administration), Fiduciary, VHA (Veterans Health Administration), Loan Guaranty, Education, Insurance
A user can click on any item in the queue and be taken to a screen where that item can be completed:
For supplemental claims and higher level reviews, the decision for each issue must be recorded in Caseflow, along with the decision date. When the decision is saved, the higher level review or supplemental claim is considered to be complete.
When the Board receives an appeal related to the business line, it automatically generates a request for that business line to provide any relevant documents to the case, since those documents are likely to not be in the VBMS eFolder. Once the business line has provided those documents, they can confirm the completion in Caseflow.
- 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