Previous: #6571. We added a hidden field to VAMC system and set Spokane to Cerner.
User Story or Problem Statement
VistA is the legacy electronic health record (EHR) system, Cerner is the new one. Each health system will cut over for the next 5 years.
This is high priority because Spokane is already using Cerner and they are blocked from going live until this is supported. Other VAMCs (Cleveland?) are switching to Cerner soon.
User Story or Problem Statement
As an admin, I can toggle VAMCs between VISTA (default, legacy system) and Cerner so that this status is available through the content API for various Veteran products and tools.
As a content editor, i can see whether my system is set to VISTA or Cerner, and how this is setting governed, and what it affects for Veterans (possibly a link to a KB article), so that i can verify it and request changes if necessary to the right organization.
Previous: #6571. We added a hidden field to VAMC system and set Spokane to Cerner.
User Story or Problem Statement
VistA is the legacy electronic health record (EHR) system, Cerner is the new one. Each health system will cut over for the next 5 years.
This is high priority because Spokane is already using Cerner and they are blocked from going live until this is supported. Other VAMCs (Cleveland?) are switching to Cerner soon.
User Story or Problem Statement
As an admin, I can toggle VAMCs between VISTA (default, legacy system) and Cerner so that this status is available through the content API for various Veteran products and tools.
As a content editor, i can see whether my system is set to VISTA or Cerner, and how this is setting governed, and what it affects for Veterans (possibly a link to a KB article), so that i can verify it and request changes if necessary to the right organization.
Collateral
ACs
These still need refining.
Change management triage
The change represented by this user story will:
TBD
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.Editor-centered
Purpose-driven
: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.Efficient
: Remove distractions and create clear, straightforward paths to get the job done.Approachable
: Offer friendly guidance over authoritative instruction.Consistent
: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.Empowering
: Provide clear information to help editors make decisions about their work.CMS Team
Please check the team(s) that will do this work.
Program
Platform CMS Team
Sitewide Crew
⭐️ Sitewide CMS
⭐️ Public Websites
⭐️ Facilities
⭐️ User support