-
Notifications
You must be signed in to change notification settings - Fork 18
Case details
Lauren Peterson edited this page Mar 18, 2019
·
21 revisions
- Caseflow users have enough information about the Veteran and appeal to complete their task
- case title
- currently active tasks
- issues
- hearings
- power of attorney
- about the veteran
- about the appellant
-
Constants (or data that is dependent on the Veteran's life/circumstance) includes:
- Remand reasons
- Co-located admin actions
- Diagnostic code descriptions (for issues)
- Dispositions (for issues)
- Judge case evaluation options
Field | Data source for legacy cases | Data source for AMA cases |
---|---|---|
Veteran name | BGS - no edit | BGS - no edit |
Veteran ID | VACOLS - no edit | Caseflow - no edit |
Veteran address | BGS - edit in SHARE | BGS - edit in SHARE |
Veteran DOB | BGS - no edit | BGS - no edit |
Docket number | VACOLS - Jed edits sometimes | Caseflowreceipt_date + database ID - Caseflow team to edit |
Appellant | VACOLS - edit in VACOLS | BGS - edit in SHARE |
Appellant address | If appellant is not a Veteran, we pull address from VACOLS. If appellant is veteran, we first check BGS, if not found, we pull from VACOLS | BGS - edit in SHARE |
Power of Attorney | BGS - edit in SHARE | BGS - edit in SHARE |
Power of Attorney address | BGS (no addresses for VSOs, yet) - no users should edit | BGS - no users should edit |
Issues | VACOLS - edit in VACOLS | Caseflow - edit in Caseflow |
Issue dispositions | VACOLS - edit in VACOLS | Caseflow - edit in Caseflow |
Appeal type (e.g. AOD) | VACOLS - edit in VACOLS | Caseflow - edit in Caseflow |
Hearing type | VACOLS - edit in VACOLS | Caseflow - TBD, hearing schedule |
Hearing date | VACOLS - edit in VACOLS | Caseflow - TBD, hearing schedule |
Hearing disposition | VACOLS - edit in VACOLS | Caseflow - TBD, hearing schedule |
Hearing judge | VACOLS - edit in VACOLS | Caseflow - TBD, hearing schedule |
Regional office | Geo-match based on Veteran address in BGS | Geo-match based on Veteran address in BGS |
- Type
- Docket
- Document ID (as a copy-able component)
- Total days waiting (if you currently have a task associated with this case)
Why are we doing it this way? see slack conversation and #6015
Colocated, attorneys, judges (for legacy and AMA cases):
- "Task"
- "From"
- "Task instructions"
Unassigned:
- "Assigned to"
Task information (pre-October, pre-AMA)
Colocated:
- "Task"
- "From"
- "Task instructions"
Attorneys:
- "Task information"
- "Assigned to"
- "Assigned by"
- "Assigned on"
Judges (when they are reviewing an attorney's work):
- "Prepared by"
- "Document ID"
- we will be moving this to "About the case" section within Case Snapshot, as a copy-able component
- To be added
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- 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
- 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