Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New VAMC Facility: Garner VA Clinic #20106

Open
2 of 21 tasks
ian-sears opened this issue Dec 16, 2024 · 1 comment
Open
2 of 21 tasks

New VAMC Facility: Garner VA Clinic #20106

ian-sears opened this issue Dec 16, 2024 · 1 comment
Labels
Change request User request that does not include any enhancements, but requires an action from the VFS-CMS team. Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. VAMC CMS managed product owned by Facilities team

Comments

@ian-sears
Copy link

ian-sears commented Dec 16, 2024

Intake

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

  • Link to associated help desk ticket (if applicable)
    Help desk ticket: VAHELP-8296

  • Name of submitter (if applicable)
    Submitter: Trying to find out - will update when known

  • If the submitter is an editor, send them links to any relevate KB articles for the VAMC Facility product.
    KB articles: How do I add a facility to my health care system?

  • Link to facility in production:
    Facility CMS link: Garner VA Clinic
    Facility API ID: vha_558BY

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.

  • 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).
  • If the facility is a VA Mobile clinic, the "New facility" flag can be removed and the page archived with no further work needed. (Note, there are required fields that will need to be filled in before doing so.)
  • 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!
    • If not, please check with the editor or VHA digital media regarding what section and VAMC it belongs to.
      • Update the Section (default is "VAMC facilities", but it should be a VAMC system in a VISN) and VAMC system field accordingly.
  • 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!

  • When editor has prepared content and let help desk know, proceed to the remaining steps.

Drupal Admin steps (CMS Engineer or Help desk) Help desk will complete these steps or escalate to request help from CMS engineering.

  • Update the facility Meta description field, using the following format: "Get address and hours, parking and transportation information, and health services offered at [facility name]."
  • Move the facility link in the health care system menu to its place in the alphabetized list (medical centers first, then clinics).
  • Drupal Admin bulk publishes nodes and facility.
  • Contact Lighthouse via Slack at #cms-lighthouse channel that this facility requires a canonical link in the following format (replacing the placeholder data with the actual API Id and VA.gov URL):
  • Add the "Awaiting CSV" flag to the facility node with a revision log message that includes a link to this ticket.
  • Let Help desk know this has been done, if not done by Help desk.

Wait (days or weeks, potentially)

  • After the canonical link has been added to the websites.csv and you have confirmation from Lighthouse that the CSV has been deployed, validate that the change has deployed by checking that the Facility Locator has been updated with the new url.
  • Update this ticket with a comment that the CSV change has been deployed.
  • Edit facility node and remove New facility and "Awaiting CSV" flags with a revision log message that includes a link to this ticket.

CMS Help desk (wrap up)

  • Notify editor and any other stakeholders.
@ian-sears ian-sears added Change request User request that does not include any enhancements, but requires an action from the VFS-CMS team. Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. VAMC CMS managed product owned by Facilities team labels Dec 16, 2024
@ian-sears
Copy link
Author

CMS Help Desk has (Jira VAHELP-8296) emailed the Editor from a nearby Durham, NC facility, asking who the Editor for this New VAMC Facility might be. Awaiting Editor reply.
@TroyCMSSupport fysa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Change request User request that does not include any enhancements, but requires an action from the VFS-CMS team. Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Flagged Facilities Facilities with flags requiring follow-up sitewide User support Workstream: The customer journey of CMS users, from onboarding to support services, etc. VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

1 participant