-
Notifications
You must be signed in to change notification settings - Fork 70
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
VAMC Facility closed: Elmendorf-Richardson VA Clinic #17658
Comments
I reached out to the Editor, which looks to be [email protected] 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. |
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. |
I'm going to go ahead and close this Github since we think there's no action for Sitewide, and the correction needs to come from VAST. If that turns out to be incorrect, this ticket can be reopened. |
Clarity from the Editor. |
What does that mean about the work that needs to be done here? |
Editor is completing the Joint Base Elmendorf node information in preparation to Publish. Once Published we can execute the Archival process of the currently Published, but Removed from Source Elemendorf page, moving the traffic, redirect, et to the new Joint Base Elmendorf facility page. |
Still awaiting Editor to complet addition of facilityu Health Services to the Joint Base Elmendorf facility prior to the removal of this facility. Will update here once that has been completed. |
@ian-sears @TroyCMSSupport I see that the editor added a page intro a week or so ago (July 23). Can you see if there's something holding up the creation of the services? They already services on the one that is closing: https://prod.cms.va.gov/alaska-health-care/locations/elmendorf-richardson-va-clinic. While we don't want them moved but recreated, it should be a relatively trivial matter, if the same services are being offered, that is. |
I once again reached out to the Editor last night via the ongoing Jira tickets to get this done. The Editor expressed distress at understanding the process of "moving" Health Services from one facility to the other and described difficulty at their facility for him to get the subordinate tasked with doing this into a meeting (with him). That was a month ago. Only two things I see holding this up is for the DRAFT Joint Base Elmendorf facility to have the remaining 4 of total of 5 Health Services moved over, and then the Joint Base Elmendorf Hours of Operation to be updated via VAST request from the Editor (currently just reads "24/7"). However the Editor has become unresponsive to requests for status or estimate of when this will be completed. I'm about to escalate to VHADigitalMedia due to unresponsiveness. Get the Joint Base Elmendorf stood up, and then migrate the Elmendorf traffic over to close it. |
@ian-sears Has this been escalated? I'd like to move this closed facility through but closing it without publishing its replacement doesn't help Veterans that much. |
Just awaiting the Redirect to take place prior to closing this facility. Ref #17663 |
@ian-sears The redirect has been deployed. This ticket can be closed after any editor confirmation. |
Editor has been notified. VAHELP-7224 CMS Help Desk ticket closed as complete. Closing this GH as complete as well. |
Intake
What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media)
Trigger: Removed from source flag
Link to associated JIRA help desk ticket (if applicable)
Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-7224
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
Mental health care at VA Alaska health care
Orthopedics at VA Alaska health care
Primary care at VA Alaska health care
Radiology at VA Alaska health care
#17663
CMS Engineer steps
(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 Helpdesk)
Help desk will complete these steps or escalate to request help from CMS engineering.
Removed from source
, add a revision log that explains the change, with a link to github issue, and change moderation state to archive. (Note: any remaining health services, non-clinical services and events for the given facility will be archived automatically when these changes are saved.)CMS Help desk (wrap up)
The text was updated successfully, but these errors were encountered: