[ ] An audit generates notifications in Slack when data is missing.
[ ] Testable_Outcome_Y
[ ] Testable_Outcome_Z
[ ] Requires Content Model Documentation
[ ] Requires design review
[ ] Requires KB article update
Implementation steps
Lighthouse (a blocker)
Creates a new endpoint that can be queried by facility id to allow us to compare CMS data received (with as little “Lighthouse-ification transforming the data” [Adam’s words] as possible) to the data in the CMS database.
Facilities
Creates a cron-based scheduled (perhaps weekly, bi-weekly, or every 4 weeks) audit of facilities to determine that facilities data matches the data provided by the new Lighthouse endpoint.
Concerns
This audit could take a while to run and may be resource-intensive.
User Story or Problem Statement
As a Veteran, I want the facilities data on VA.gov to be the same as the data in the CMS.
Background
This is a follow-up of work done in https://github.com/department-of-veterans-affairs/va.gov-cms/issues/19250
Acceptance Criteria
Implementation steps
Lighthouse (a blocker)
Creates a new endpoint that can be queried by facility id to allow us to compare CMS data received (with as little “Lighthouse-ification transforming the data” [Adam’s words] as possible) to the data in the CMS database.
Facilities
Creates a cron-based scheduled (perhaps weekly, bi-weekly, or every 4 weeks) audit of facilities to determine that facilities data matches the data provided by the new Lighthouse endpoint.
Concerns
This audit could take a while to run and may be resource-intensive.
ACs