VAMC product dashboard - Githubissues

kevwalsh commented 4 years ago

Background

"The Health Services was the biggest time suck, then facilities, it's a toss up for the remaining one but they were much less time consuming"

We believe that dashboards specific to the needs of

For each of the following dashboards

VAMC systems

[ ] At /admin/content/vamc-systems, there's a listing of all VAMC systems, with their most relevant content and administrative fields.

VAMC facility health services

[ ] On a given VAMC /health-services page, there's a listing of health services that shows the
[ ] at /admin/content/vamc-systems/vamc-health-services, there's a listing of all health services that shows all VAMC facility health services, with their most relevant content and administrative fields.

VAMC facilities

[ ] On a given VAMC /locations, there's a listing of vamc-facilities for that VAMC system that shows
[ ] at /admin/content/vamc-systems/facilities, there's a listing of all health services that shows all VAMC facility health services, with their most relevant content and administrative fields.

EWashb commented 2 years ago

Deprioritized as of Q3 2022

mmiddaugh commented 1 year ago

Some artifacts are available related to this work:

Prototype with associated user stories - both found in #2786
VAMC Dashboard tech plan.pdf
The dashboard created for Vet Centers was intended to inform this work and was designed with the following goals (which we can assume will be similar to VAMC editorial needs)
- to provide access to everything a Vet Center editor might need to do in one place, and use the Vet Center page to do so
- to help Vet Center editors orient to their top tasks through cards that use icons and descriptions
- to bridge the gap between the content model and users' mental model through action links in cards that jump link to relevant parts of a form
- to allow editors to review satellite locations and their operating statuses at a glance so they can make see what might need updating