Facility Locator iteration: Provider core training / PPMS data

[jilladams]

Background

Provider Core Training

Design was handled during #11542 . Figma file: https://www.figma.com/file/GvNVeG9GAXZaBpny7vNxZP/Facility-Locator?type=design&node-id=172-16230&mode=design

All of the following user stories in this group are related to using facility locator to search for community providers in VA's network the other facility types are not in the MVP scope for this effort.

1. As a Veteran, I want to see what Providers have completed Provider Core Training
2. As a Veteran, I want to learn about Provider Core Training and what it means
3. As a Veteran, I want to filter my search in the Facility Locator to return only providers who have received the Provider Core Training

Implementation Notes:

• the area for Veterans to learn about Provider core training will not be housed in facility locator, you should design a link/call to action etc. for Veterans to click or otherwise engage that links them out to this information that is housed elsewhere

For background, here is a blurb on Provider Core Training: Department of Veterans Affairs (VA) has created the Provider Core Training so that Veterans can be offered care from the highest quality providers available. Referring Veterans to Providers who have completed the Provider Core Training ensures that Veterans are receiving high-quality care in the community.

User Stories

• [ ] As a Veteran, I want to see what Providers have completed Provider Core Training
• [ ] As a Veteran, I want to learn about Provider Core Training and what it means
• [ ] As a Veteran, I want to filter my search in the Facility Locator to return only providers who have received the Provider Core Training

Affected users and stakeholders

• CMS_editors_of_X_product
• Developers of Y teams

Hypothesis

A hypothesis may depend on a spike ticket to be completed.

We believe that _thissolution will achieve _thisoutcome. We'll know that to be true when this measurable outcome occurs.

Assumptions

• Tk
• Tk

(How will these assumptions be validated?)

Acceptance Criteria

• [ ] Testable_Outcome_X
• [ ] Testable_Outcome_Y
• [ ] Testable_Outcome_Z
• [ ] Requires KB article update

Change management triage

The change represented by this user story will:

• [ ] Be a site-wide change to appearance or key functionality (such as log-in process)
• [ ] Be a specific change that requires more than 30 minutes of work by a user to meet a publishing requirement
• [ ] Remove a piece of functionality (such as restricting editing functions, or “hardening”)
• [ ] Require action by some or all users by a specific deadline
• [ ] Change the front end and be highly visible to the public
• [ ] Noticeable performance improvements (publishing speed, predictability)

If you selected an item above, use the Change Management Runbook to create a CM epic and associated tickets.

If you did not select an item above, update issues/PRs in GitHub but don’t plan for change management.

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.

Runbook

## Labels (You can delete this section once it's complete) - [x] Issue type (red) (defaults to "Epic") - [ ] CMS subsystem (green) - [ ] CMS practice area (blue) - [x] CMS workstream (orange) - [ ] CMS-supported product (black)

[mmiddaugh]

per Keri Kinyon, as of 9/27/2023 barely .02% of total providers in PPMS (estimating current providers at around 1.3M) have completed training – specific to the 8 courses they are tracking for this program.