Request to update VA File Number guidance

[oddball-lindsay]

Duplicate check

• [X] I've searched for any related issues and avoided creating a duplicate issue.

This update is for:

Pattern

What is the name?

Know how their information is updated

What is the nature of this update?

• [ ] How to build this component/pattern
• [ ] When to use this component/pattern
• [ ] When to use something else
• [ ] Usability guidance
• [ ] Accessibility considerations
• [ ] Content considerations
• [X] Implementation
• [ ] Package information
• [ ] Addition to Forms Library documentation
• [X] Update to existing Forms Library documentation

What problem does this solve?

We were presenting designs to stakeholders and they have provided feedback that the pattern for VA File Number formatting is incorrect. It is an 8-digit number that does not have any dashes. The current pattern has an example that is formatted more like a SSN number.

Hoping to pass this information along to the design system, to save other teams from having a similar discussion with their stakeholders.

Additional Context

https://design.va.gov/patterns/ask-users-for/social-security-number also mentions the VA File Number and may be worth updating with this additional context. Some other notes I have gathered regarding this number, if you'd like to include it:

1. "VA File Number" = an eight-digit claims folder number assigned through the Beneficiary Identification and Records Locator Subsystem (BIRLS).
   1. ...but we can rely on SSN in most cases.
2. Also known as “C-file numbers” or CNA, these were assigned prior to VA converting to the use of SSNs, which is why some older Veterans have C-File numbers even if they have an SSN. Can't remember when VA converted to using SSNs (when available).
   1. The team guesses this happened sometime in the 1990s
3. Today, an 8-digit file number can still be assigned in cases where a Veteran doesn’t have an SSN (edge case for a much older Veteran who has not yet engaged with the VA)
4. VA File numbers are known to VSOs and their representatives, not to be confused with participant IDs which are relatively new and only used for internal VA.gov backend systems

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @babsdenney @danbrady @LWWright7