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) shared services team. Feel free to delete instructions and unselected options from the ticket to make it easier to scan.
Your team
Product name:Appointments on VA.gov
Team name: Appointments Team (formerly VAOS)
OCTO product owner: Kay Lawyer (Kristen McConnell while Kay is on leave)
Dedicated content writer on your team (if you have one): N/A
Dedicated a11y specialist on your team (if you have one): N/A
Your CAIA team:
Filled out by CAIA
IA:
Content:
Accessibility:
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:
What's the nature of your initiative and desired outcomes?
Facilitate the OH scheduling process by leveraging past Patient-Provider relationships display available providers for specific types of care at chosen facility locations.
User Story: As a Veteran scheduling an appointment at an Oracle Health facility, I want to stay on VA.gov and not be sent to the OH portal.
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.
We ran usability testing and iterated based on user feedback. We are working with Oracle Health and backend to build the integration.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[x] Yes
[ ] 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? March 1-31
What is the name of your engineer who will build the React widget?Simi Adebowale
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
[x] Design intent
[ ] Midpoint review
[ ] Staging
[ ] 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:
[ ] 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
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) shared services team. Feel free to delete instructions and unselected options from the ticket to make it easier to scan.
Your team
Your CAIA team:
Filled out by CAIA
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?
Facilitate the OH scheduling process by leveraging past Patient-Provider relationships display available providers for specific types of care at chosen facility locations.
User Story: As a Veteran scheduling an appointment at an Oracle Health facility, I want to stay on VA.gov and not be sent to the OH portal.
Supporting artifacts
Figma file of provider selection screen A11Y annotations User flow
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?
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.
We ran usability testing and iterated based on user feedback. We are working with Oracle Health and backend to build the integration.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[ ] 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:
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 a link to your Collaboration Cycle Request:
Next steps
Suggest an addition or update to the design system team