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.

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

Automatically transfer No Show hearing tasks #12539

Closed
14 of 17 tasks
pshahVA opened this issue Oct 31, 2019 · 3 comments
Closed
14 of 17 tasks

Automatically transfer No Show hearing tasks #12539

pshahVA opened this issue Oct 31, 2019 · 3 comments
Assignees
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 💃

Comments

@pshahVA
Copy link

pshahVA commented Oct 31, 2019

Story

When a hearing No Show task has been open for more than 30 days, the task is automatically completed and the appeal is transferred to the appropriate location.

Acceptance criteria

  • no feature flag needed

Once a No Show hearing task has been open for 30 days:
If the appeal is Legacy, assign it to:

  • 55 if the POA / representative type is a Co-located Veteran Service Organization (VSO)
  • 81 (Case Storage) if the POA / representative type is any other, including:
    • private agent / attorney
    • state or regional VA organization (e.g. NC Department of Military & Veterans Affairs)
    • no representative
    • a non-co-located Veteran Service Organization (VSO)
  • If the appeal is AMA, assign it to Mail (create an EvidenceSubmissionWindow task, which is part of the Mail org)
Open questions:

Link to requirements-gathering doc

  • Do the above requirements apply to all or only some Case Types? (Example Case Types: Original, Post Remand, CAVC ...what else?)
    • Applies to all case types. The important distinction is Legacy vs AMA.
  • How can the automatic transfer be reversed? (i.e. what happens when Caseflow automatically transfers a No Show, and it's later discovered that the Veteran did send mail requesting to be rescheduled?) How do we enable a Hearing Coordinator to fetch the Veteran's file so that it's actionable?
    • The Board staff (attorneys and judges) who review the case to make a decision have the ability to send the case back the Hearing Branch if they determine a hearing needs to be scheduled
  • What is the flow for distributing No Show cases in the Hearings Management queue to individual Coordinators before the 30-day mark?
    • What's the value of this manual step (on demo, there appears to be bulk assign capability)?
    • Can Caseflow distribute them to the right Coordinator automatically?
    • How does an individual Coordinator know when a Veteran has sent in mail (are they alerted; or do they have to proactively look for each specific Legacy Veteran in VACOLS)?
  • What is "Mail"? Do we need to create a Mail task, reuse one? What is "Mail" expected to do? What should the language/notification look like for Mail?
    • Evidence Submission Window task for AMA appeals
  • Does "case storage" mean that it skips hearings and goes to a decision, or is there another route it takes?
  • When does it move to 81 or 55? And what are the exact rules?
  • Would it move to location 81 after 15/30 days, or would it move before? Is 30 days appropriate?
  • What happens at the 30 day mark?
  • What does this mean for an AMA case that is not in VACOLS?
  • Who has access to the current "Hearings Management team cases" queue to clear it?
  • How does the transfer of No Show tasks happen currently? What does the queue look like?

Out of scope

  • Automatically route cases to ROs or users

Release notes

  • [] Communicate with the training team that this behavior has changed so they can update their docs

Designs

n/a

Background/context

Currently after a Veteran is scheduled, then no show happens, a task is created and it is sent to the org's “Assigned” queue tab. This is after the Veteran's 15 days to request to have their hearing rescheduled. After the 25 days of hold are up, its hold is removed and it shows up in the organization’s “Unassigned” queue to indicate action is needed.

Please refer to this slack thread for more information:
https://dsva.slack.com/archives/CJL810329/p1579124576132400

We move a legacy case to 81 when the hearing tasks are completed:

def when_child_task_completed(child_task)
super
return unless appeal.tasks.open.where(type: HearingTask.name).empty?
if appeal.is_a?(LegacyAppeal)
update_legacy_appeal_location
else
IhpTasksFactory.new(parent).create_ihp_tasks!
end
end
def update_legacy_appeal_location
location = if hearing&.held?
LegacyAppeal::LOCATION_CODES[:transcription]
elsif appeal.representatives.empty?
LegacyAppeal::LOCATION_CODES[:case_storage]
else
LegacyAppeal::LOCATION_CODES[:service_organization]
end
AppealRepository.update_location!(appeal, location)
end

Success criteria

Appeals with No Show hearing tasks are automatically moved to the appropriate location after 30 days.

Technical notes

Resources/other links

@jimruggiero jimruggiero added Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Product: caseflow-hearings Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. labels Dec 29, 2019
@nicholer nicholer changed the title Hearings to Automatic transfer of “No-Show” to “location 81” Hearings to Automatic transfer of “No Show” to “location 81” Mar 31, 2020
@nicholer nicholer changed the title Hearings to Automatic transfer of “No Show” to “location 81” Automatically transfer No Show hearing tasks Apr 2, 2020
@tomas-nava
Copy link
Contributor

waiting on further requirements from hearings branch

@pshahVA
Copy link
Author

pshahVA commented Apr 30, 2020

Not sure if this helps:
§ 20.302 Rule 302. Appeals with a request for a Board hearing.
(a) Except as described in paragraphs (b) and (c) of this section, for appeals in which the appellant requested, on the Notice of Disagreement, a Board hearing, the Board's decision will be based on a review of the following:
(1) Evidence of record at the time of the agency of original jurisdiction's decision on the issue or issues on appeal;
(2) Evidence submitted by the appellant or his or her representative at the hearing, to include testimony provided at the hearing; and
(3) Evidence submitted by the appellant or his or her representative within 90 days following the hearing.
(b) In the event that the hearing request is withdrawn pursuant to § 20.704(e), the Board's decision will be based on a review of evidence described in paragraph (a)(1) of this section, and evidence submitted by the appellant or his or her representative within 90 days following receipt of the withdrawal.
(c) In the event that the appellant does not appear for a scheduled hearing, and the hearing is not rescheduled subject to § 20.704(d), the Board's decision will be based on a review of evidence described in paragraph (a)(1) of this section, and evidence submitted by the appellant or his or her representative within 90 days following the date of the scheduled hearing.
(Authority: 38 U.S.C. 7105, 7107, 7113(b))
[84 FR 182, Jan. 18, 2019]

@lund5000
Copy link
Contributor

lund5000 commented Jun 2, 2021

Completed in https://vajira.max.gov/browse/CASEFLOW-212

@lund5000 lund5000 closed this as completed Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

6 participants