Open omahane opened 3 months ago
@omahane - May I assist with this?
@omahane @ian-sears - This just became a bit more complicated -- This is not a name change; it is closing a facility and opening a new facility in a different location, serving the same population...
Update 6/17/24 - I have reached out to VHA Digital Media for clarification as to whether this is a facility rename OR a total facility closure and opening of a new facility. Related JIRA ticket VAHELP-7563
@omahane @jilladams @ian-sears
Update 6/17/24 - I have reached out to VHA Digital Media for clarification as to whether this is a facility rename OR a total facility closure and opening of a new facility. Related JIRA ticket VAHELP-7563
Editor replied with clarity today in Jira ticket. This is indeed to be Sarpy County VA Clinic.
@ian-sears @TroyCMSSupport Can you confirm that they are going to change the name upstream in VAST?
Awaiting VAST update (request was made to VAST, (see attched) on Feb 27th. The node still shows the old address and we've not yet seen an update from VAST in the CMS.
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: https://va-gov.atlassian.net/browse/VAHELP-7563
[x] Name of submitter (if applicable) Submitter: Jeffrey.Gates@va.gov
[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/nebraska-western-iowa-health-care/locations/bellevue-va-clinic Facility API ID: vha_636GL
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.
18138
CMS Engineer steps
(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.
Changed name
then save node (with moderation state = published)CMS Help desk (wrap up)