New Vet Center Facility: Leesburg Outstation

[TroyCMSSupport]

Description

Use this runbook if: a Vet Centers, Mobile Vet Centers, Vet Center Outstations is flagged as New, OR if an existing facility is flagged as New with a new Facility API ID. (This may happen if a Vet Center moves districts, or a Mobile Vet Center is reallocated to a different Vet Center.)

Intake

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

• [x] Link to associated help desk ticket (if applicable) Help desk ticket: Helpdesk Ticket 7461

• [x] Name of submitter (if applicable) Submitter: @TroyCMSSupport

• [ ] If the submitter is an editor, send them links to any relevant KB articles for the Vet Center product. KB articles:

• [ ] Link to facility in production: Facility CMS link: Facility link Facility API ID: vc_2241 -- This ID is incorrect for outstations, needs to be an OS ID.

Acceptance criteria

New Vet Center

[@TODO: KB ARTICLE FOR ADDING VET CENTERS - SEE runbook-vamc-facility-new]

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.

If a Outstation:

• [x] Confirm what Vet Center it belongs to, and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
• [ ] Contact the Vet Center editor to remind them to (1) add a photo of the Outstation and then they can publish when ready
• [ ] Consider: Following up with Barb/RCS Central office to be sure that she's aware that the Outstation is in-flight

Drupal Admin steps

• [ ] 8. Bulk publish the nodes and facility.
• [ ] 9. Edit the facility node: remove the New facility and Awaiting editor flags, save the node.
• [ ] 10. Let Help desk know this has been done.

CMS Help desk (wrap up)

• [ ] 11. Upgrade the Vet Center Director and Outreach Specialist accounts to the publisher role for that Vet Center.
• [ ] 12. Notify editor and any other stakeholders.

[mmiddaugh]

@agile6MSkinner this one should be pulled into the next sprint if possible Expecting a new name to come through VAST (Leesburg Vet Center Outstation) This location is currently free-range and needs to have a section assigned

[jilladams]

The CSV step to add the Facility url to the LH CSV is not represented in this runbook and needs to be added.

[jilladams]

The API ID is incorrect here - we're expecting an ID which is something like vc_0511OS @mmiddaugh to follow up with RCS.

[mmiddaugh]

RCS will follow up to ensure name and facility ID are updated. Until then, marking this as blocked.

[jilladams]

Same on this one, noting: all of the steps in this runbook can be carried out by Helpdesk who are also Drupal Admins. We shouldn't need Facilities team work here, but Helpdesk is welcome to ask for support from us as needed, @TroyCMSSupport @ian-sears , once Michelle has the updated API ID from RCS.