0781 post-concept test designs

[jinaryu]

Design considerations based on research findings

Link to findings

What's locked in

• [x] Keep blue support alerts
• [x] Break out the evidence portions of 0781 into 526ez evidence section, while keeping rest of 0781 questions in additional forms
• [x] Ask SC questions for 0781 conditions
• [x] Introduce the 0781 in additional forms step (rather than conditions)

What's still in flux

• [x] How to streamline 0781 and 526 evidence (learned on 8/21 from Kayce White that there will be an update to the 526 that matches the 0781 section!)
• [x] How to ask SC questions for 0781 conditions

Other notes

• How to handle review & submit for additional forms (look at example of additional disability benefits page)

Tasks

• [x] Design wireframes
• [x] CAIA review
• [x] OCTO review
• [x] VBA review

Acceptance Criteria

• [x] Completed design
• [ ] Reviewed by CAIA, OCTO, and VBA
• [x] Schedule midpoint review

[jinaryu]

Support page to-do Opportunities for improvement include:

• [x] Clarifying if/when links will take users out of the form flow
• [x] Looking into the most familiar phone lines (one Veteran expressed concern that older Veterans would be looking for a toll-free 800 number and might not be familiar with the 988 number)
• [ ] Bucketing resources to clarify which are standard emergency response such as 911

Opportunities for additional forms of support include:

• [x] ~Direction on technical support for file upload~
• [x] Highlighting VSOs as a potential resource
• [x] ~Linking to VA-supported wellness resources such as meditation apps~
• [x] Pointing to more information about how to get care for mental health conditions generally - done by connecting to MST page?

[jinaryu]

More to-do

• [x] embed 0781 supporting docs
• [x] embed 0781 treatment details
• [x] moving additional disability benefits questions to additional forms step - check if this is in scope
• [x] make text boxes bigger on add event page

[jinaryu]

8/20 sync with @shannonkford and @nnicholas7

Shannon's sketch:

• integrating 0781 screener question into SC question (for mental health conditions)
• if it's free text, then we ask them
• 0781 not relevant to secondary SC
• we could test if screener idea messes people up, and if it does then we could punt back to asking in step 2
• if they say - yes it's a traumatic event show add experiences screen, and once they get to 0781, prefill?

Are there other forms with a screening process?

• deprecated wizard pattern

Looking at figma

• you could have one event linked to multiple conditions
• select condition that maps to experience
• we can't get away with them not filling out initial SC questions in step 2: conditions
• can we see what people are writing in SC questions for PTSD?
• ask VBA: what are examples of SC for these types of conditions that aren't traumatic experiences?

Summary

• avoid writing same thing twice
• but its not that big of a lift to write it twice

Treatment facility

• JP: it's nice to consolidate treatment cards; feels weird to split out supporting docs; feels it should be split out
• can we step them through every type of evidence and decide if you want to add more? (do you have other evidence? do you have VA medical records? do you have private records?) - this isn't a huge change
• don't have to worry about not seeing 0781
• facility type becomes required, combine treatment into one?
• even combining 0781 supporting docs with 526 supporting docs?
• maybe we don't have to write that content of how to educate on evidence. it's more integrating types of evidence
• also thinking about in progress forms with these step 3 changes

[jinaryu]

Action items from 8/21 0781 update meeting Notes

• [x] change experiences back to event
• [x] change corpsman example to "corpsman on medical ship in combat area"
• [x] add combat event example and have that be in hint text
• [x] change harassment back to assault
• [x] revise USS example to "U.S.S. Repose"
• [x] change time frame dates back to what's on the paper form
• [x] change "buddy statement" to just "statement"

[jinaryu]

Roadmap:

• [x] by EOW 9/6, finalize prototype C and send out for review
• [x] by 9/13, get feedback from team and Shannon
• [x] schedule check in with kayce week of 9/23
• [x] schedule midpoint review for week of 9/30

[jinaryu]

Finished proto C, sent out for review

[rubensun]

Reviewed proposed flow changes with @kristinoletmuskat We're continuing to make adjustments to the Supporting Evidence sections and exploring alternate treatments to the multi-prompt list and loop patterns to eliminate preceived "foreshadowing" and "confirmation fatigue".

[jinaryu]

Finished prototpying the most recent version

Notable changes:

• consistent multiple responses pattern, using button CTA instead of static question as an anchor
• splitting up VA and private medical records for sake of simplicity in data collection, since date fields are different for both
• updated all footers to the "VSO" version (more updated than currrent "Benefits" version)
• updated "forms to complete" cards

More detailed changelog here

cc: @rubensun

[rubensun]

We also need to collect and incorporate any final content feedback from CAIA. We currently have a touch-base scheduled with @katherine-fung on 9/24.

[rubensun]

Kayce White and Abigail Werner (VBA) provided input into a few pieces of copy adjustments marked as comments in the figma prototype. Overall, Kayce and Abigail have expressed alignment with how we’re approaching the form overall and how we’re referencing physical forms throughout the flow.

[jinaryu]

Rough timeline for wrapping up 0781 design work

~~9/23-27 By EOD 9/25: send out Figma for CAIA content review (ask how long they need.. I’m thinking setting a due date of 10/11?) By EOD 9/25: send out prototype C to Shannon for review 9/27: During biweekly design sync, talk through prototype C with Shannon (hopefully get sign off)~~

9/30-10/4

• [x] 10/3: midpoint review
• [x] Solution for overflow (slack thread) - meet with EE team to see what they're doing

10/7-10/11 (SF out)

• [x] Make midpoint review changes
• [x] Address CAIA content review comments

10/14-10/18 (SF out)

• [x] Add accessibility annotations
• [x] Sketch out backup plan (following 0995 team's pattern, determine "by X date, we will resort to backup")
• [x] Data mapping (confirm which fields are optional vs. required)

10/21-10/25

• [ ] Handoff to engineers, meet as needed
• [ ] Update 526 form flow active

10/28-11/1 Buffer week in case things take longer than expected

[jinaryu]

10/1 from Emily:

• generally speaking, overflow creates more work, but we'll have to do it anyways down the line
• not doing overflow is an MVP approach
• SF - we typically don't try to figure out how much fields based on paper form, take out character counts

Action items:

• [x] Jina - take out character counts.
• [x] Jina - sync with Lisa to determine overflow approach

[jinaryu]

Note: current 0781 doesn't show up in BDD flow and that is intentional because active service members are asked about this during their exit interview/exam, so they don't need to see it in our form. this should also be the case for new 0781 (slack thread)

[jinaryu]

I have finished the 0781 designs with annotations. We still have some pending items that @rubensun will take the lead on finalizing.

[rubensun]

Current gaps to fill

• [ ] Indirect actions impacting 0781 opt-in (removal or deselection of mental health conditions)
• [ ] Handling of documents uploaded post opt-out
• [ ] Placement of MST resources content block