Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Disallow Veterans to be matched cross-state lines for hearing scheduling #14519

Closed
3 tasks
chandracarney opened this issue Jun 11, 2020 · 2 comments · Fixed by #14635
Closed
3 tasks

Disallow Veterans to be matched cross-state lines for hearing scheduling #14519

chandracarney opened this issue Jun 11, 2020 · 2 comments · Fixed by #14635
Assignees
@ferristseng
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃
Milestone
PI4-S5: Thurgood ...

Comments

@chandracarney
Copy link

chandracarney commented Jun 11, 2020 •
edited
Loading

Description

The Hearing Branch would like to pause Vets from populating cross-border RO scheduling queues in Caseflow.

Acceptance criteria

  • Veterans are matched with their state's closest RO
  • Approved alternate scheduling sites (within the Veteran's state) should still appear in the dropdown
  • Update documentation: geomatching

Background/context/resources

Caseflow currently matches Veterans to the nearest RO, even if that RO is across state lines for Veterans and their PoAs. While the intended effect was to to allow Veterans shorter travel to their hearing if an out-of-state RO is closer, the unintended consequence has been that out-of-state PoAs are unable to attend hearings with their Veteran clients due to state laws.

Previous PR to match cross state lines: #11706

Technical notes

  • rerun the fetch hearing locations job to repopulate the array for active hearings (not for hearings that have been scheduled, or held)
    • only runs for 1000 appeals at a time so it will have to be run multiple times
@chandracarney chandracarney added Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃 labels Jun 11, 2020
@chandracarney chandracarney mentioned this issue Jun 15, 2020
Closed
@chandracarney
Copy link
Author

Written approval on 6/29/20 from DVC this has been okayed by the Chairman. Moved to current sprint.

@chandracarney
Copy link
Author

This issue can close #13432, #12927, #13434, and the epic #13954.

@ferristseng ferristseng self-assigned this Jul 1, 2020
@ferristseng ferristseng mentioned this issue Jul 1, 2020
Merged
3 tasks
va-bot pushed a commit that referenced this issue Jul 8, 2020
@ferristseng
Disable Geomatching Across State Lines (#14635)
360cc61 
Resolves #14519

Selectively reverts: #11706

### Description

  * Restoring tests and methods that are RO-specific
  * Add documentation

### Acceptance Criteria
- [x] Veterans are matched with their state's closest RO
- [x] Approved alternate scheduling sites (within the Veteran's state) should still appear in the dropdown
    - The way I tested this is to run through the code in console manually, since it's hard to verify this with the data in dev
      1. Setup VA.gov service environment variables:
      ```
      export VA_DOT_GOV_API_URL='https://sandbox-api.va.gov/services/'
      export VA_DOT_GOV_API_KEY='<Facilities Locator API key (dev environment) in OnePassword>'
      ```
      2. Start a Rails console
      3. Run:
      ```
      addr = Address.new(address_line_1: "<Your Street>", city: "<Your City>", state: "<Your State>", zip: <Your Zip Code>)
      v = ExternalApi::VADotGovService.validate_address(addr)
      d = ExternalApi::VADotGovService.get_distance(ids: RegionalOffice.facility_ids_for_ro('<Closest RO>'), lat: v.data[:lat], long: v.data[:long])
      d.data
      ```
- [x] Update documentation: geomatching
This was referenced Aug 4, 2020
Closed
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferristseng ferristseng

Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-hearings Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Tango 💃
Projects
None yet
Milestone
PI4-S5: Thurgood Marshall Sprint
Development

Successfully merging a pull request may close this issue.

Disable Geomatching Across State Lines department-of-veterans-affairs/caseflow
2 participants
@ferristseng @chandracarney