New VAMC Facility: Sunbridge VA Clinic (Previously archived, now re-opened -- ready to go)

[stefaniefgray]

Intake

• What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media)
  Trigger: Outreach Hub event was being held at facility, but facility homepage was archived

• Link to associated help desk ticket (if applicable)
  Help desk ticket: See https://va-gov.atlassian.net/browse/VAHELP-6154

• Name of submitter (if applicable)
  Submitter: @stefaniefgray

• If the submitter is an editor, send them links to any relevant KB articles for the VAMC Facility product.
  KB articles: <insert_kb_article_links>

• Link to facility in production:
  Facility CMS link: https://prod.cms.va.gov/fayetteville-arkansas-health-care/locations/sunbridge-va-clinic
  Facility API ID: vha_564QB

Acceptance criteria

New VAMC Facility

Please refer to the Knowledge Base article titled "How do I add a facility to my health care system?" for more information: https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-do-i-add-a-facility-to-my-health-care-system

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.

• 1. Become aware that the new facility is now on the Facility API (typically, via a Flag, but this may come in as a helpdesk ticket).
• 2. If the editor has followed the steps from the above Knowledge Base article and included which section and VAMC the facility belongs to (i.e. VA Pittsburgh), great! Proceed to step 3. If not, please check with the editor or VHA digital media regarding what section and VAMC it belongs to.
• 3. Updates the Section (default is "VAMC facilities", but it should be a VAMC system in a VISN) and VAMC system field accordingly.
• 4. Communicate with editor (cc VHA Digital Media) to give them go-ahead to complete the content, with this KB article. (See sample notification email below)

Email template

Hello! You should now be able to edit the draft page for this facility, located at [LINK TO NEW FACILITY DRAFT PAGE ON PROD]

Important: Please make sure that all relevant steps listed within the “How do I add a facility to my health care system?” Knowledge Base article have been completed: https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-do-i-add-a-facility-to-my-health-care-system

Once finished, please save this page (and all related VAMC Facility Health Service pages) in the moderation state “Draft." Please do not save them as “Published.”

Please let us know when your draft content is complete, so that we can wrap up the technical process from our end before publishing the new facility to VA.gov. Thanks!

• 5. 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.)

#15192

• 6. When editor has prepared content and let help desk know, reassign this issue to appropriate CMS engineer on Product Support team, for bulk publishing.

CMS engineer steps

• 7. CMS engineer executes the steps of the URL change request ticket from step 5 above.

(Redirects deploy weekly on Wed. at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the 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.

• 8. Drupal Admin bulk publishes nodes and facility.
• 9. Drupal Admin edit facility node and remove New facility flag and save node.
• 10. Let Help desk know this has been done, if not done by Help desk.

CMS Help desk (wrap up)

• 11. Notify editor and any other stakeholders.

[stefaniefgray]

@jilladams @xiongjaneg @omahane This one is ready to go! 🚀

See also linked CSV update ticket: #15192

[stefaniefgray]

@jilladams @xiongjaneg Would it be possible to add this to our next sprint? This clinic has been ready since 9/21. Thank you!

[xiongjaneg]

@stefaniefgray @omahane added to Drupal prerefinement agenda

[jilladams]

@stefaniefgray based on state of checked ACs, I think this is ready for helpdesk follow up.

[xiongjaneg]

updated Jira ticket https://va-gov.atlassian.net/browse/VAHELP-6356

[stefaniefgray]

Editors are now updated! Closing (though I'm confirming whether the clinic should only have two health services listed -- this can remain within Jira, though, no need for Github ticket to stay open)

Thanks for your help @omahane @jilladams and @xiongjaneg ! 🚀