[CAIA Intake] 10-10 Health Enrollment: Adding Emergency Contact to 10-10EZR form

[IMHieuVo]

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

• Team name: 10-10 Health Enrollment Team
• OCTO product owner: Patrick Bateman
• Product name: 10-10EZR Health Benefits Information Update form
• Product manager: Alex Seelig
• Slack channel: #1010-health-apps
• Dedicated content writer on your team (if you have one):
• Dedicated a11y specialist on your team (if you have one): N/A

About your initiative

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

Select all that apply.

• [ ] Digitizing a new form
• [ ] Creating a new digital tool
• [X] Updating an existing form or tool
• [ ] Translating a form or tool into Spanish
• [ ] Adding new unauthenticated content to VA.gov
• [ ] Updating existing unauthenticated content on VA.gov
• [ ] Something else: insert description

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

The 10-10EZR Health Benefits Update paper form asks for Next of Kin and Emergency Contact information but we left it off our online form MVP launch. Now the team is circling back and adding the Next of Kin and Emergency Contact to our online form. We will start with the Emergency Contact first.

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.

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

• [ ] Yes
• [x] No
• [ ] I’m not sure

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.

The Figma wireframe is ready and the engineers have started building out the pages and their design patterns. We have most of the content in place and ready for review. We would like a content freeze for Emergency Contact on Tuesday, September 10.

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

• [ ] Yes

• [x] No

  Note: For an incremental launch, we use React widgets to display dynamic content. We'll need at least 2 weeks of extra time to coordinate the content for this and work with your engineer. Learn more about our process for dynamic content. If your launch plans change, notify CAIA of the change as soon as possible so we can talk about how that will impact the timeline.

If you are releasing incrementally:

• What dates do you anticipate starting and ending your incremental launch? N/A
• What is the name of your engineer who will build the React widget? N/A

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• [ ] Design intent
• [ ] Midpoint review
• [ ] Staging
• [X] None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide a link to your Collaboration Cycle Request:

• Hyperlinked Ticket Number: N/A

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.

• Mural NoK-EC
• Figma Link

Next steps

• [ ] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Naomi Eke, and we’ll then acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.
• [ ] Review the remaining next steps in the VFS team tasks section here.
• [ ] If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
• [ ] If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
• [ ] If you're creating an experimental design, also contact the design system team: Read more about experimental designs
  Suggest an addition or update to the design system team
• [ ] If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
• [ ] If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

[strelichl]

(Just noting I removed Aliyah from the "dedicated content writer" field since she is on CAIA/supporting multiple product teams and that field is for product teams that have their own content role. Sorry that question is a bit confusing!)

[aliyahblackmore]

Update here:

• I did one last review of the emergency contact screens in Figma
• I tracked one question follow up question in the destructive screen section. It doesn't seem like there's a need for any other static page adjustments at this time, but let me know if there was something else you were interested in changing.
• And since you just mentioned that there may be a potential shift re: primary/secondary contacts, I'll look out for any design updates in the coming days! The contact freeze date (9/10) will shift because of this, but the current designs have all of the content recs.
• And I'll hold on sharing the static page update with your SMEs just in case the primary/secondary updates impact the page.