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
281 stars 197 forks source link

[CAIA Intake] Benefits Decision Review: Supplemental Claims (VA-20-0995) form updates #83316

Open eileen-coforma opened 3 months ago

eileen-coforma commented 3 months ago

Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.

About your team

About your initiative

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

What's the nature of your initiative and desired outcomes?

Tell us briefly about your work and the outcomes you’re aiming to achieve.

The Supplemental paper form is being updated, and we want to get the digital form to match. Paper form should be done by June.

Collaboration timeframe

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

We started in our current sprint (5/8-5/21), and want our content POC to be closely aligned, so we're inviting early for possible collaboration.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

Form updates include a mandated inclusion of VBA to VHA notification consent for Veterans claiming conditions due to personal traumatic events involving MST. Multiple forms require this update, including: 526ez and 0781. Updates also include optional homelessness questions also on the 10207.

Where are you at in your timeline?

Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.

Form is already in production, but there will be new screens added as a result of this update. We are in the initial discovery with SMEs for update requirements.

Will you release this new product incrementally (for example, release to 25% of users to start)?

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide your ticket number and link:

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.

Next steps

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/88995
eileen-coforma commented 3 months ago

Tagging @bethpotts and @jstrothman for visibility, since we've been in discussion about a content POC.

kristinoletmuskat commented 3 months ago

Noting that Eileen mentioned there might be new pages and suburls in this form that IA could review, but the form itself isn't moving locations. @eileen-coforma when you have ideas for those new urls we'd love to take a look! Feel free to tag me here when ready and we can go over them in like a 15 min call. I know that might be many weeks away.

aprocik1 commented 3 months ago

Hi @eileen-coforma, thanks for this request. I know you're working to finalize the PDF form by June--the end of this week. Some of our content team members are at Code for America, so we have limited capacity this week. If there's something you'd like to start collaborating on right now, I'm available to meet tomorrow 5/29 or Friday 5/31 from 10-2 pm ET. Or, if you'd prefer to wait for a kickoff meeting with our whole team, we're available to meet Thursday 6/6 from 3-5 pm ET or Wednesday 6/12 from 12-1 pm ET. What do you think?

jstrothman commented 3 months ago

@aprocik1 Thank you -- Eileen is unexpectedly out this week. I'd love to take you up on the offer to take a look at one aspect of the updates tomorrow: specifically where we ask questions related to a separate form, which we submit on the back-end. We want to ensure the Veteran is aware that an additional form is being submitted on their behalf. (Related issue: #83774 ) I'm available at 10am -- should I send you an invite?

jstrothman commented 3 months ago

As of 5/29/2024, OMB approved the updated Supplemental Claim VA Form 20-0995, and expected release is June 28th. This means we no longer have a concern about late-breaking changes. We wouldn't be able to release until the paper form is released, but we aren't trying to be ready that day either.

aprocik1 commented 2 months ago

Hi @jstrothman, feel free to follow up here when you're ready for us to align on next steps, whether that be scheduling a kickoff or moving forward in the review we started last week. I know you're at an offsite this week, so take your time. There's no rush on our end--I just didn't want to lose sight of this.

katherine-fung commented 2 months ago

Hi @eileen-coforma @jstrothman,

I'm checking in to see if this work is ready for CAIA to review.

If it's ready for us, can you please confirm which are the latest designs for us to review?

I saw the homelessness questions in the Figma file linked above. Did Danielle Thierry work on this copy with you? If not, these questions are related to another conversation she's having with the VA Homeless Programs Office, so we'll want to give her a heads up about them. For context, what's the purpose of adding these questions? I know in the HLR design, there's a single screen that asks Veterans if they're homeless or at risk and Eileen had said this info would be used to expedite the HLR if Veterans answer yes. But I notice that the SC design has additional questions about homelessness.

jstrothman commented 2 months ago

@katherine-fung Re the homelessness questions: Danielle is aware of these new questions being on the 0995. On 4/24, she shared with me a screenshot of these same questions being implemented on the 20-10207 Priority processing in support of a claim (figma). (@eileen-coforma I realize now I didn't share that info with you at the time.)

I believe the amended questions are based on VEO research, and that VBA intends to use the updated versions on all benefits forms that ask about homelessness.

eileen-coforma commented 2 months ago

@katherine-fung The SC work is not ready for review yet. We expect for it to be ready by early next week. Some of our designs also depend on the meeting we have this Friday with SMEs to clarify content surrounding the VHA Notifications question (also related to the 0781 work you've been involved in)

When it is ready, I will leave links to the Figma pages with new proposed designs.

eileen-coforma commented 1 month ago

@katherine-fung SC is ready for review. Updates to the form are within these pages

All of the new designs are on the top of the page, labeled with proposed

katherine-fung commented 1 month ago

Hi @eileen-coforma,

I've provided most of CAIA's recommendations in Figma comments.

There are still a few outstanding issues.

  1. How should forms make people aware that they have to fill out another form? We still need to standardize this pattern on intro pages and potentially on the subform page itself (in the case of Supplemental Claims, this screen: https://www.figma.com/design/2LGebZcUuu5Iqh4QLPII6A/Supplemental-Claims-(VA-0995)?node-id=1058-35856&t=TBi1B5OIfmoPBjuO-0). I discussed this with Danielle and have some ideas to discuss with A when they're back next week.

  2. A and I will discuss this together when they're back next week: "Can we standardize how we talk about 'VA facility or provider' v. 'VA hospital or clinic' v. 'military treatment facility' v. 'military hospital or clinic' etc.? I think we should try to be consistent with this language, especially if these terms have specific meanings. Maybe we match everything to the check boxes in question 22A on the PDF. What do you think?"

  3. @eileen-coforma - The stakeholders for the VHA notifications content haven't responded to my questions about their edits in the Word doc. Do you want to follow up with them, since you've been communicating with them?

eileen-coforma commented 1 month ago

Thanks @katherine-fung Are the recommendations finalized, or should I wait for A's edits/approvals?

  1. We have already implemented the OMB information for both forms in the introduction, referenced the embedded form within the non-VA evidence question, and changing the relevant pages' subheaders to include the embedded form numbers.

    • If there are other suggestions, it may be out-of-scope, for the update itself.

  2. If we want to match the form, we can simplify it by following 22B "Treatment facility"

  3. Yes! I can reach out about it. I keep forgetting by the time I manage to log into CAG. I think she was also on PTO for a bit.

katherine-fung commented 4 weeks ago

@eileen-coforma we should have these finalized by Monday.

  1. After discussing with Danielle and Laura, I put a recommendation here for the 4142 details on the intro page. It's a minor content tweak (delete the current H2, and replace it with another H2 slightly lower on the page). We want to avoid this header "Details for forms within this application" and nesting SC and 4142 under it because:
    • there's inconsistencies across products for how we refer to "forms," "applications," and "claims"
    • it suggests that there's a parent application that SC and 4142 are part of, whereas SC is the actual application and 4142 is an additional thing to fill out.

If this is out of scope for this update, can we come back to it as part of creating/implementing form-within-a-form patterns (based on the SC and 0781)?

  1. Noted! I'll discuss this with A on Monday.

  2. Thank you!

katherine-fung commented 3 weeks ago

@eileen-coforma A and I finalized the recommendations for point #2.

You can implement the recommendations in these comments:

https://www.figma.com/design/2LGebZcUuu5Iqh4QLPII6A?node-id=0-2532#878499914

https://www.figma.com/design/2LGebZcUuu5Iqh4QLPII6A?node-id=0-2532#878467299

https://www.figma.com/design/2LGebZcUuu5Iqh4QLPII6A?node-id=0-2532#893232661

eileen-coforma commented 3 weeks ago

@katherine-fung thank you!

strelichl commented 3 weeks ago

@eileen-coforma Same question as on the HLR work--do you have a launch date in mind? No rush on that, I just want to make sure we have plenty of lead time to coordinate widget work beforehand. Thanks!