-
Notifications
You must be signed in to change notification settings - Fork 19
End product codes
Request issues that are processed in VBMS get added as contentions to end products. End products represent units of work that are then distributed and routed to different offices for processing. There are many different types of end products. This page is to document more about the types of end products and how the correct code to use is chosen by Caseflow.
Factors in determining a claim label:
- Source type
- Higher level review
- Supplemental claim
- Decision document (board grant effectuation)
- And more!
- Claim labels cannot be changed to switch between these.
- Rating / non-rating
- Rating
- Non-rating
- Not specified
- Benefit type
- Compensation
- Pension
- Not specified
- Original or remand
- Original - the claim was initiated by the claimant
- Remand - the claim has been sent from the business back (potentially to a different part of the business) for additional review.
- Board remands
- VBA Duty to assist errors
- Difference of opinion
- Note: An EP in one of these remand categories cannot be changed to a different type, or to a non-remand.
- Primary or correction
- Primary - This is the first claim, not a correction of another claim
- Correction - The claim has been created to correct mistakes and data on another claim
- Control
- Local quality error
- National quality error
Additional factors indirectly influence end product code selection as well. For example, whether an issue gets added to a follow up board grant effectuation or remand claim depend on the disposition of request issues when they are decided on the previous claim.
In the future, we may be accounting for special types of claims such as spina bifida and fiduciary claims.
- 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