Open ian-sears opened 3 months ago
I reached out to the Editor, which looks to be Timothy.Chavis@va.gov via Jira Ticket https://va-gov.atlassian.net/browse/VAHELP-7224 to ask if this facility is Closed. Awaiting Editor
We've escalated attempts to reach an Editor to VHADigitalMedia, asking for assistance in reaching their CBOC. Awaiting Customer in VAHELP-7224 @TroyCMSSupport FYSA Spreadsheet updated. Collapsed JIRA-6958 into the above parent JIRA ticket #7224.
Spoke in depth and at length with the Editor (via screenshare on Teams). Samuel Hudson is reaching out to his VAST coordinator to inquire why this was (VAST request??) requested to be closed. This facility page is correct, the Editor is going to go over it in detail just to be certain of that, and no change should be made. This was possibly removed from source in error. @TroyCMSSupport @omahane
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Removed from source flag
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-7224
[x] Name of submitter (if applicable) Submitter: Flagged Facilities
[ ] If the submitter is an editor, send them a link to the KB article: How to archive a closed facility
[ ] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/alaska-health-care/locations/elmendorf-richardson-va-clinic) Facility API ID: vha_463QA
Acceptance criteria
VAMC facility closure
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.
[@TODO: Update email template]
Email template
``` SUBJECT: