-
Notifications
You must be signed in to change notification settings - Fork 19
Rapid Appeals Modernization Program
Rapid Appeals Modernization Program (RAMP), is a program that allowed veterans to participate in a simplified version of the AMA process more than a year before the AMA launched, by converting eligible legacy appeals into supplemental claims or higher level reviews.
The two types of RAMP forms are:
-
RAMP Election - This is the form used to opt-in all eligible legacy appeals, and create either a supplemental claim or higher level review to process them. Additionally, it creates the appropriate EP in VBMS to process the supplemental claim or higher level review.
-
RAMP Selection - This is the name for the form used to contest decisions made as part of RAMP Election. "RAMP Selection" is the official for the form chosen by AMO, but because it's easily confused with "RAMP Election", we use the term "RAMP Refiling" in the codebase. loads up any issues on past RAMP decisions that are selectable for review. Unlike RAMP Elections, RAMP Selections allow veterans to select the board appeal lane. Appeals requested via RAMP Selection forms are processed and stored identically to AMA appeals, for this reason, users perform two intakes for these forms. First, they must intake the RAMP Selection form, then they intake an AMA board appeal to construct the more complex issue data required to process AMA appeals.
NOTE: RAMP is intended to be a temporary pilot, and will sunset soon. For that reason we have chosen to deprioritize all but the most urgent development tasks associated with RAMP issues.
Per this article, RAMP processing ended in October 2022. The feature toggle :ramp_intake
is only enabled in Prodtest/Production for a small number of users, and is not enabled in UAT for any users.
- 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