Open swirtSJW opened 1 year ago
Next Steps: Is VAST the canonical information for the TRICARE half of Lovell, ask in Lovell office hours on 5/18
Per Steve: there is an implementation difference between matching the data on migration, vs. on node save. Answers from office hours will determine best path forward, in order to finalize plan and estimate.
Decisions regarding this and #13707 should result in documentation changes in Github and the Knowledge Base.
the information in VAST to their knowledge is the canonical information for the TRICARE half of Lovell
User Story or Problem Statement
As a Lovell site maintainer I expect that any data that is changed by the nightly VAMC facility migration is propagated from the VA James A Lovell facility (vha_556 in Facility API) to the TRICARE James A Lovell facility (tricare_556) that is not in Facility API
As it is now, Changes to James A Lovell VA will track the facility API data, but James A Lovell TRICARE is not updated, and can become out of sync.
Acceptance Criteria
Implementation steps
This could be done as a post save hook, or it could be done with a post migration task that just syncs VA to TRICAE no matter if data changed or not.
Design principles
Veteran-centered
Single source of truth
: Increase reliability and consistency of content on VA.gov by providing a single source of truth.Accessible, plain language
: Provide guardrails and guidelines to ensure content quality.Purposely structured content
: Ensure Content API can deliver content whose meaning matches its structure.Content lifecycle governance
: Produce tools, processes and policies to maintain content quality throughout its lifecycle.