jilladams
commented
1 year ago https://github.com/department-of-veterans-affairs/va.gov-cms/issues/12920 has been consolidated into this epic. Notes from that ticket:
3/10/23
Initial list to explore: Make an appointment Pharmacy DAV Vans VAMC Facility Map Contact us Required health services
Input into this list with:
- where are the editors creating the most problems (Laura)
- @kmariepat-cityfriends crosswalk the old board
3/13/23
Have a conversation with VHA digital media to determine which order of priorities, true up with that team
4/17/23
Next steps:
-
VAMC Facility Map (low hanging fruit opportunity) (needs less explaining, learning opportunities)
-
Required health services (make a better structured content type, use as an opportunity to teach this process)
Learnings:
- drupal core concepts
- abstraction of editorial to the front end
- single source of truth
- using interface to encourage best practice behaviors
Decision makers: PO + Jenny HL
Background
The content model for VAMC MVP was 60-80% "complete". There was a heavy reliance on blobby rich text fields and "Detail page" content type for the parts of the content model that were not determined.
This super epic reflects various content model hardening opportunities, including "Top tasks" (see below) and others.
Top tasks
The VAMC product contains 6 "top task" pages identified as priority content.
[health-care-system]/medical-records-office [health-care-system]/register-for-care [health-care-system]/billing-insurance [health-care-system]/policies [health-care-system]/make-an-appointment [health-care-system]/contact-us [health-care-system]/pharmacy
In the MVP (Pittsburgh), this content was all created using the VAMC detail page content type, and has since been cloned 20 times for the VAMC systems that are currently slated for launch in Q4 2020, Q1 2021.
Much of this content will thus be duplicated 150 times, once for each VAMC system.
This presents problems for content reliability, consistency, and maintainability.