CLP Vanity URL Request - VHA Digital Media for /va-health-connect - Target date 9/26/24

[TroyCMSSupport]

Instructions

• Requests must be submitted AT LEAST 2 weeks in advance. Some requests take a significant amount of time and coordination to implement, so start the process as soon as you know you will need one.
• This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.
• It is your responsibility to notify VA stakeholders as appropriate.

POC	Github alias(es)
Product team point(s) of contact:	@jilladams @TroyCMSSupport
Content point of contact:	CAIA will enter
IA point of contact:	IA will enter

Type of request

• [x] We need a custom vanity URL (complete vanity URL section)

Do you have a product technical team able to implement this redirect?

• [x] No - CAIA will need to make Public Websites aware of the ticket.

Implementation date

When does this request need to be live? NOTE: Redirects in vsp-platform-revproxy auto-deploy M-Th. Friday launches should be avoided. Choose one:

• [x] On a specific date, connected to a program or publishing requirement. DATE: 9/26/2024
• [ ] Any day prior to a deadline/latest possible date. DEADLINE:

Vanity URLs

Vanity URL	Landing page
www.va.gov/healthconnect	https://prod.cms.va.gov/initiatives/va-health-connect

Link to campaign landing page request issue, if relevant:

Process, Roles and Responsibilities

• [ ] Requesting team: Above information is provided
• [ ] Requesting team: All appropriate VA stakeholders are notified as appropriate
• [ ] IA: Request is vetted and documented and implementation plan is clear
• [ ] IA: Request is assigned to appropriate team for implementation
• [ ] Implementation team: Work is complete
• [ ] Implementation team: Validated in production
• [ ] Requesting team: Validates everything is correct in production and closes ticket

---

related links

• Helpdesk slack thread: https://dsva.slack.com/archives/C0FQSS30V/p1726847517611049
• CLP request: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9169
• Prior redirect request: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9597
• JIRA service desk ticket with Justin: https://va-gov.atlassian.net/browse/VAHELP-8021

[jilladams]

FYI @FranECross that I let Justin know IA will need to reivew, and that we typically request 2 weeks' lead time on redirects, and have asked if 9/26 is a hard and fast date. https://va-gov.atlassian.net/jira/servicedesk/projects/VAHELP/queues/custom/12/VAHELP-8021

[jilladams]

@kristinoletmuskat FYI that there was prior discussion about the IA on this vanity URL here in comments with @mnorthuis : https://github.com/department-of-veterans-affairs/va.gov-cms/issues/9169#issuecomment-1136368754. tl;dr:

• Original request = /healthconnect
• Mikki's proposal = /va-health-connect/

At the time, Abigail Harlow was running this CLP and agreed to that vanity URL. If y'all still feel strongly about /va-health-connect , we can let VHA DM know that's still the preference from IA, and run with that.

[jilladams]

From Justin:

It is hard and fast. This is in conjunction with a SECVA initiative and announcement. Thank you for your partnership on this.

I've pushed back for /va-health-connect. If he has no problems with that, we can update src in ticket body and go ahead to implement, since that was previously signed off by IA.

[jilladams]

Shared in Slack for CAIA awareness, given the timing: https://dsva.slack.com/archives/C01K37HRUAH/p1726861721042729

[jilladams]

Thanks for the update. We would prefer /healthconnect.

We are going to need @mnorthuis 's sign off, I believe.

Mikki, for your awareness when you review: Justin let me know that this request is coming from much higher than him in VHA, that this is a secretary-level initiative, if that matters.