You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/ISSUE_TEMPLATE/runbook-vet-center-new.md
+15-7
Original file line number
Diff line number
Diff line change
@@ -35,19 +35,27 @@ Facility API ID: <insert_facility_API_ID>
35
35
#### CMS help desk steps
36
36
**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.**
37
37
38
-
**If a Mobile Vet Center:**
38
+
**If a Mobile Vet Center is entirely new (not a reallocated asset)**
39
39
-[ ] 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.
40
-
-[ ] Contact the Vet Center editor to remind them to (1) add a photo of the Mobile Vet Center and then they can publish when ready and (2) remind them that if this Mobile Vet Center is used by any other facilities to communicate with those Vet Center editors
41
-
-[ ]Consider: Following up with Barb/RCS Central office to be sure that she's aware that the mobile Vet Center is in-flight
40
+
-[ ] Contact the Vet Center editor to remind them to (1) add a photo of the Mobile Vet Center and then they can publish when ready and (2) suggest that they communicate with the editors of any other Vet Centers with access to the unit to have them manually add the MVC to their Locations page as a "Nearby" MVC.
41
+
-[ ]Follow up with Barb/RCS Central office to be sure that she's aware that the mobile Vet Center is in-flight.
42
42
43
-
**If a Outstation:**
43
+
**If an existing Mobile Vet Center is relocated/reassigned to another Vet Center**
44
44
-[ ] 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.
45
-
-[ ] Contact the Vet Center editor to remind them to (1) add a photo of the Outstation and then they can publish when ready
46
-
-[ ] Consider: Following up with Barb/RCS Central office to be sure that she's aware that the Outstation is in-flight
45
+
-[ ] Archive the previous version of the MVC
46
+
-[ ] Contact the Vet Center editor to remind them to (1) add a photo of the Mobile Vet Center and then they can publish when ready and (2) suggest that they communicate with the editors of any other Vet Centers with access to the unit to have them manually add the MVC to their Locations page as a "Nearby" MVC.
47
+
-[ ] Follow up with Barb/RCS Central office to be sure that she's aware that the mobile Vet Center is in-flight. Ask Barb to check with any editors who may have manually added the previous version to their pages as "Nearby" - they should confirm it is still valid.
48
+
49
+
**If a Outstation:**
50
+
-[ ]1. Confirm the Vet Center to which it belongs and set the "Main Vet Center location" field. The parent location may be derived by the Facility ID.
51
+
-[ ]2. Check with Readjustment Counseling Services to (1) confirm the Vet Center and district to which the Outstation belongs, (2) identify the responsible Vet Center Director and Outreach Specialist (names/email addresses), (3) confirm satellite locations (if any), and (4) because the location will be available in the Facility Locator along with a basic detail page via Lighthouse, ask RCS to set an appropriate operating status (i.e., Coming soon) for the new location and for any location which it may replace.
52
+
-[ ] 2a. If this facility replaces another, follow the appropriate runbook for updates to the other facility, as indicated, including updates to user access/permissions.
53
+
-[ ]3. Contact the Vet Center editor to remind them to (1) add a photo of the Outstation and then they can publish when ready
47
54
48
55
**If a Vet Center:**
49
56
-[ ]1. Become aware that the new facility is now on the Facility API (typically, via a Flag).
50
-
-[ ]2. Check with Readjustment Counseling Services to (1) confirm what district the Vet Center belongs and (2) Identify the Vet Center Director and Outreach Specialist (names/email addresses)
57
+
-[ ]2. Check with Readjustment Counseling Services to (1) confirm what district to which the Vet Center belongs, (2) identify the Vet Center Director and Outreach Specialist (names/email addresses), (3) confirm satellite locations (if any), and (4) because the location will be available in the Facility Locator along with a basic detail page via Lighthouse, ask RCS to set an appropriate operating status (i.e., Coming soon) for the new location and for any location which it may replace.
58
+
-[ ] 2a. If this facility replaces another, follow the appropriate runbook for updates to the other facility, as indicated, including updates to user access/permissions.
51
59
-[ ]3. In [Sections taxonomy](https://prod.cms.va.gov/admin/structure/taxonomy/manage/administration/overview), move the Vet Center Section to the appropriate district.
52
60
-[ ]4. Create accounts (or restrict existing accounts) with editor rights only for Vet Center Director and Outreach Specialist so that they cannot publish on their own.
53
61
-[ ]5. Contact Vet Center Director and Outreach specialist to onboard for training [@TODO write sample email - SEE runbook-vamc-facility-new]**Note: this should include instructions for adding content and preparing for publishing and RCS Central Office should be included as CC**
0 commit comments