stefaniefgray commented 10 months ago

Intake

[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Flagged Facilities view
[x] Link to associated help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-6710
[x] Name of submitter (if applicable) Submitter: @stefaniefgray
[x] If the submitter is an editor, send them links to any relevant KB articles for the VAMC Facility product. KB articles:
[x] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/gulf-coast-health-care/locations/naval-hospital-pensacola-va-clinic Facility API ID: vha_520QC

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.

[x] 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).
[x] 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.
[x] 3. Updates the Section (default is "VAMC facilities", but it should be a VAMC system in a VISN) and VAMC system field accordingly.
[x] 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! ```

[x] 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.)

https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16356

[x] 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

[x] 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.

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

CMS Help desk (wrap up)

[x] 11. Notify editor and any other stakeholders.

stefaniefgray commented 10 months ago

URL change ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16356

stefaniefgray commented 10 months ago

@jilladams @xiongjaneg Facility is already open -- can we please prioritize this one next sprint? Thank you! 🙌

Edit: Err, never mind, under the weather today and brain is swimming. Order of operations -- need editors to finish homepage and adding health services. But good to have on radar. Sorry for premature ping!

TroyCMSSupport commented 4 months ago

@omahane @ian-sears - Page has been updated by editor to include Hours and Health services.

ian-sears commented 3 months ago

@omahane @TroyCMSSupport @jilladams Yes. The Awaiting Editor tasks (reason for the Flag) were completed by the Editor. This facility is now prepared for the Canonical redirect to take place in #16356

omahane commented 3 months ago

@jilladams @Agile6MSkinner Based on our Flagged Facilities touchpoint meeting, I'd this this blocked. We don't don't know how to proceed given that this not a clinic of its own but more like services in a Naval hospital.

@ian-sears @TroyCMSSupport Could you update this ticket with your complete knowledge?

ian-sears commented 2 months ago

Yes. I cannot locate the comment (or was it verbal in a meeting?) that I think Michelle Middaugh was going to ask in an upcoming RCS meeting about this facility. So far as we (CMS Help Desk) understand it, this is not really a facility, per se, so much as a location for Scheduled Surgeries Only. When this was brought up it is myu recollection that Michelle reacted with the above. I've reached out to Michelle to ask if I have overlooked any resultant comment from that so we could get this moved forward.