Ask users for Social Security or VA file number is incomplete

[humancompanion-usds]

Bug Report

• I’ve searched for any related issues and avoided creating a duplicate issue.

What happened

When I recently asked how we handle placing the VA File number onto PDF forms that only have the SSN when a user provides their VA file number, I got a lot more intel then I bargained for. I found the answer to that question but also a whole lot of confusion on what is expected.

What I expected to happen

I expected to get a straight answer. I did not.

Reproducing

Steps to reproduce:

1. Ask anyone how we handle SSN and VA file number in a form.
2. Get many variations, not captured by this pattern in response.
3. 🤯

Urgency

This came up because the new 1010d form wanted to require SSN but not require VA file number. VA file number is not on the paper form. Instead of allowing the user to enter either, and putting the VA file number in the SSN field (same number of digits), they removed the VA file number from the online form.

• This bug is blocking work currently in progress
• This bug is affecting work currently in progress but we have a workaround
• This bug is blocking work planned within the next few sprints
• This bug is not blocking any work
• Other

Details

There is a small mountain of guidance that we need to add to this SSN pattern. There are 3 fields at play:

1. SSN
2. VA file number
3. Military Service number

The Forms Library pattern handles all 3. However, we only show 1 variation of that in the Design System. We need to show all 3 variations, independently, in addition to the most common variation (which is SSN & VA file number and the only variation we show today).

In addition, we don't tell designers and developers that the preferred way to collect this is...not to collect it. Instead we should be pushing teams to use the prefill pattern for uneditable data when the users is IAL2 (LOA3) authenticated and verified.

Full thread.

[humancompanion-usds]

A couple of variations to capture and detail:

SSN is uneditable for IAL2 authenticated users

When a user is authenticated and identity proofed, we should use the SSN we have on file for them and not allow the user to change the SSN in this form. Follow the Help users to know how their information is prefilled pattern for uneditable data.

Decision review forms all use this variation of the pattern, including the 526, the 20-0995, and the 20-0996.

Unauthenticated/IAL1 users or non-Veteran users

Unauthenticated or un-identity proofed (IAL1) users

The most common variation of this pattern is to offer both the SSN and VA file number. Most paper forms feature both and thus, for online forms that must map fields to a paper form, the fields match. For paper forms that only feature one or the other either SSN or VA file number can be supplied. The VA has the ability to identify the Veteran using either. While this is a manual process, it is less burdensome for the user. Both fields are the same number of digits.

Non-Veteran users

When a form is directed towards a non-Veteran, for example a caregiver or spouse may be filling out the form on the Veteran's behalf, we may ask that person for their SSN only. For example, in the 21P-0847 form, we ask for the submitters SSN only on one step. In a later step, when asking for their Veteran's information, we ask for SSN (required) and VA file number (optional). In this case, that matches the fields in the paper form.