VAMC Facility name change: Tulare VA Clinic to Visalia VA Clinic

[omahane]

Intake

• [x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Flag in CMS

• [x] Link to associated help desk ticket (if applicable) Help desk ticket: Helpdesk link

• [x] Name of submitter (if applicable) Submitter: @TroyCMSSupport

• [x] If the submitter is an editor, send them link to KB article: "How Do I Update My VAMC Facility's Basic Location Data?". Let them know that once VAST/Lighthouse has been updated 1/ the Facility Name will be automatically updated and 2/ we will use a Facility name change flag to update the facility's URL. We can notify them once we have been notified that VAST/Lighthouse has been updated.

• [x] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/central-california-health-care/locations/tulare-va-clinic Facility API ID: vha_570GB

Acceptance criteria

VAMC Facility name change

CMS help desk steps

Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag. What happens: The name change is made in VAST, that syncs to Lighthouse which syncs to Drupal.

• [x] 1. Check that the title change in name field on the VAMC node has shown up in Drupal.
• [x] 2. Create a URL change request, changing the entry from the old facility URL to the new facility URL. (Note: The URL change request ticket blocks the completion of this ticket.)

18141

CMS Engineer steps

• [x] 3. Execute the steps of the URL change request ticket from step 2 above.

(Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the following items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)

Drupal Admin steps (CMS Engineer or Help desk)

Help desk will complete these steps or escalate to request help from CMS engineering.

• [x] 4. Locate the newly renamed VAMC Facility (https://prod.cms.va.gov/admin/content/bulk) Search by new name
• [x] 5. Updates URL alias for this facility
• [x] 6. Resave this facility
• [x] 7. Make bulk alias changes to facility service nodes. (https://prod.cms.va.gov/admin/content/bulk?type=health_care_local_health_service)
• [x] 8. Bulk save fixed titles to facility service nodes. (https://prod.cms.va.gov/admin/content/bulk?type=health_care_local_health_service)
• [x] 9. Update menu title for facility
• [x] 10. May also need to directly edit the VAMC System menu to alpha sort the menu item after the title changes
• [x] 11. Update Alt text for facility image, if relevant
• [x] 12. Update Meta description (TBD: some backwards compatibility for SEM, by including something like ", formerly known as [previous name]".
• [x] 13. Edit facility node and remove flag Changed name then save node (with moderation state = published)

CMS Help desk (wrap up)

• [x] 14. Notify editor and any other stakeholders. Ask editor to validate that the photo of the facility does not contain the old name in any signage, etc. and to replace if necessary.

[TroyCMSSupport]

@omahane @jilladams @ian-sears - I believe this is ready for the next steps --

[ian-sears]

Closing as completed. Node has been updated.