FE: Establish criteria to remove flipper caregiver_use_facilities_API

[dsinla]

Description

As we investigate each Facilities related Flipper, document the criteria and timeline for when it should be removed.

Refer to https://github.com/department-of-veterans-affairs/va.gov-cms/issues/10656

Acceptance Criteria

• [ ] Criteria for Flipper removal is created in this ticket

CMS Team

Please check the team(s) that will do this work.

• [ ] Program
• [ ] Platform CMS Team
• [ ] Sitewide Crew
• [ ] ⭐️ Sitewide CMS
• [ ] ⭐️ Public Websites
• [X] ⭐️ Facilities
• [ ] ⭐️ User support

[dsinla]

Relevant detail from this slack chat below

David Shannon @Matt Long I work with @Dawn Pruitt on the Facilities team. As a follow up, can you speak to the eventual criteria/plan to remove this flipper, and the one for HCA? We're trying to improve our process, and we want every flipper (ideally when created) to have a corresponding removal issue created and linked as well. Seems like the plan would be - once verified and tested as part of MVP - to remove the flipper for both apps and integrate the LH API as part of production . Is that correct?

Matt Long @David Shannon, I can. So we’ve tested, as part of the MVP, that we can get the data we would need to suffice an implementation. We are now in the process of determining the best user experience and design that would fit the implementation. Our plan is to get an approved UX design with our stakeholders, implement that within the form, go through a QA process and then roll out to production in a controlled fashion. The controlled implementation would be a 25, 50, 75, 100% rollout over a 4-week period to ensure we have zero issues. At the end of that 4 week roll out period we would remove the toggle.
Additionally, per our stakeholder requirements.. we are awaiting the release of the LH v1 API for facilities that adds additional info in the API response that our stakeholders are looking for. Hence the delay between the creation of the MVP and the advancement of this project.