search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Tech Review | Remove Pension Form #62075

Closed steele-lm closed 1 year ago

steele-lm commented 1 year ago

Issue Description

The online 527 pension form is so outdated that it cannot be processed. VA stakeholders would like access to the form to be removed from va.gov and users informed of the proper pathway.

Possible Use Cases

  1. Veteran filling out a pension form to secure benefits for themselves.
  2. Proxy filling out a pension form on the Vet's behalf (POA, VSO, family member, etc.).
  3. Others?

Possible Scenarios

  1. Pension claim form has been started online but not finished. Intent is to come back later and finish.
  2. Pension claim form has been started online, but abandoned.
    • Can/should we cross-check in-progress online forms against the record of paper submitted forms?
  3. Individual looking for information on pension benefits.
  4. Others?

Resources

  1. Pension Mural Board with form flow
  2. Pension Mural Board with ideas for removal
  3. About form 21P-527EZ Pension landing page
    • Includes link to online tool/form
  4. Online form/tool
  5. Online form 21P-530 Burial
  6. Pension temporary removal mural: https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1689262813123/cb880912d3f71ef79be0d63d0e61e306d1e6ae31?wid=0-1689360929417&sender=u674f33e99d68adb0c1952030

Tasks

steele-lm commented 1 year ago

@DLarson-Oddball @Midge-dev @fred-khoury-oddball I stubbed out the tech review ticket and added general tasks, but feel free to refine since Thomas is out.

steele-lm commented 1 year ago

Hey @DLarson-Oddball I’m using Zenhub in GitHub, click this link to join my workspace and see other features available in GitHub or download the Zenhub extension and sign up with your GitHub account. Posted using Zenhub

steele-lm commented 1 year ago

In-progress form query from Kyle Soskin:

form_ids = ["21P-527EZ", "21P-530"]
all = InProgressForm.where(form_id: form_ids);nil
puts "Total in-progress: #{all.count}"
form_ids.each do |id|
  puts "=== #{id} ==="
  puts "Number of total open in-progress forms: #{all.where(form_id: id).count}"
  pp all.where(form_id: id).group("date_trunc('year', created_at), date_trunc('month', created_at)")
.count(:id).sort_by {|k,v| k}.to_h
end
steele-lm commented 1 year ago

Which yields:

Total in-progress: 4196
=== 21P-527EZ ===
Number of total open in-progress forms: 2677
{2022-10-01 00:00:00 UTC=>1,
 2022-11-01 00:00:00 UTC=>2,
 2023-02-01 00:00:00 UTC=>1,
 2023-03-01 00:00:00 UTC=>10,
 2023-04-01 00:00:00 UTC=>37,
 2023-05-01 00:00:00 UTC=>571,
 2023-06-01 00:00:00 UTC=>1342,
 2023-07-01 00:00:00 UTC=>713}
=== 21P-530 ===
Number of total open in-progress forms: 1520
{2023-02-01 00:00:00 UTC=>1,
 2023-03-01 00:00:00 UTC=>1,
 2023-04-01 00:00:00 UTC=>7,
 2023-05-01 00:00:00 UTC=>365,
 2023-06-01 00:00:00 UTC=>729,
 2023-07-01 00:00:00 UTC=>417}
juliepedtke commented 1 year ago

@steele-lm Is is possible to pull/uncover data on when forms were last edited (not just when they were created, and when they will expire)? Then we could align on a definition of abandonment to deprioritize some in-progress forms that haven't been touched in a long time.

steele-lm commented 1 year ago

@juliepedtke Kyle confirmed that he can narrow the query by last-edit-date once we align on a definition of abandonment.

juliepedtke commented 1 year ago

Last-edit-date would be great to have. I think a definition of abandonment will take some discussion, and doesn't need to be done first. We might decide that we want to slice it some other way, like based on how much info they've filled in, etc.

juliepedtke commented 1 year ago

I guess that leads me to another question: can we query by how many pages of the form / what % of form fields were completed?

steele-lm commented 1 year ago

Kyle indicated that we can "sort of" determine how many pages were filled out... Here is an example of a stored IPF (in staging)

#<InProgressForm id: 22641, user_uuid: "c32deef0c41744f8a3b20a6e7f63da97", form_id: "21P-527EZ", created_at: "2023-07-13 20:03:48.232230000 +0000", updated_at: "2023-07-13 23:56:52.040156000 +0000", metadata: {"version"=>3, "return_url"=>"/additional-information/direct-deposit", "saved_at"=>1689292611843, "submission"=>{"status"=>false, "error_message"=>false, "id"=>false, "timestamp"=>false, "has_attempted_submit"=>false}}, expires_at: "2023-09-11 23:56:52.037188000 +0000", form_data: [FILTERED], encrypted_kms_key: "v1:AQICAHjVjGLd4IjSSZNlaxuvYz6L//LLhgOqQTfIbDnXZJS...", verified_decryptable_at: nil, user_account_id: "95224dec-0e77-4bad-a908-ec4effe7b611">
juliepedtke commented 1 year ago

Interesting! cc @fiorella-io @ohgreatkate

ohgreatkate commented 1 year ago

luckily I believe we captured the URLs in our form flow Murals so that might not end up as challenging as it sounds!

fred-khoury-oddball commented 1 year ago

Here is an in progress list of files we've identified are relating to 527 and 530: burials and memorials form 530:

home loan COE form 527:

fred-khoury-oddball commented 1 year ago

links found so far

fiorella-io commented 1 year ago

Thank you @fred-khoury-oddball! Adding the page # where the links exist was very helpful!