-
Notifications
You must be signed in to change notification settings - Fork 19
Intake Integrations
Intake integrates with three other systems
- Benefits Gateway Services (BGS)
- Veterans Benefits Management System (VBMS)
- Veterans Appeals Control and Location System (VACOLS)
We use these other systems for a combination of fetching data, such as from the Corporate Database, as well as for establishing and working with end products (also referred to as claims).
Claim establishment includes the following steps:
- Establishing an end product in VBMS
- Adding request issues to the end product. When these are on a claim in VBMS, they are called contentions
- If the contentions are for rating issues, associating the contentions to rating issues
- If an informal conference was requested on a Higher Level Review, we also generate a tracked item (BGS)
Once a claim is established, there are additional actions that can be taken:
- Contentions can be added or removed (VBMS)
- Contention text can be updated (VBMS)
- End products can be cancelled, which can happen if all of the contentions on it were removed (BGS)
If contentions are added or removed on a rating end product, the contentions are associated to rating issues again so that it includes mapping for all issues on the end product.
BGS integration GitHub repo - ruby-bgs
Intake primarily uses BGS to fetch data from CorpDB
VBMS integration GitHub repo - connect_vbms
We establish end products for Higher Level Reviews and Supplemental Claims that are compensation or pension. We also establish end products for Board Grant Effectuations that have granted compensation and pension issues on appeals.
- 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