Implement heading styles for hardened VAMC Register for care pages (1 of 3)

[mmiddaugh]

Issue description

We need to doublecheck the newly hardened Medical records page to ensure consistency of design now that the new content model has been implemented.

Problems to be solved

• Because this top task page exists across the VAMC system, the page don't have facility context so we will need to include hyperlinked name
• Locations should be restyled like service locations, including the presentation of hours by day
• Heading level hierarchy should be maintained
• Padding between areas of content and around optional "release valve" fields (these are limited rich text - could have bullets but will not have (or need) headers)

Register for care resources

• Register for care content model mural
• Example Register for care page from Pittsburgh https://pr7705-6dug5xhx8nbfoodoeepelyhivmuvyree.ci.cms.va.gov/cheyenne-health-care/register-for-care https://web-6dug5xhx8nbfoodoeepelyhivmuvyree.ci.cms.va.gov/cheyenne-health-care/register-for-care

Screenshots

Front end display in hardened version


Content mural showing areas of focus


Related issues

This issue is one of 3 to complete this design implementation

• Heading levels will be done in this issue
• Hours and phone styles in #37630
• Replace alert style in #37631

Template

Newly hardened pages use this template which has not been rolled to Production yet and needs to be viewed in CMS.

 <!--
  layout: vamc_system_register_for_care.drupal.liquid
  path: preview
  entityId: N/A
-->

note, this is different than the template currently on Prod

``` ```

The following systems have data in this new hardened template and can be used for validation:

• VA Western Colorado health care (i.e. http://prod.cms.va.gov/western-colorado-health-care/register-for-care-0)
• VA Cheyenne health care
• VA Eastern Oklahoma health care  
• VA Sheridan health care

Tasks

Implement UXPin design for Register for care pages, including the following

• [ ] Add new Q2 heading for "Patient registration (admissions)"
• [ ] Add new Q2 heading for "Not yet enrolled in VA health care?"
• [ ] Ensure new Q2 headings are available by jumplink
• [ ] The name of each facility is an H3, linked to that VAMC page. (For example, clicking on Rocky Mountain Regional VA Medical Center from [Eastern Colorado health care register for care page]https://www.va.gov/eastern-colorado-health-care/register-for-care/) leads to facility page this will not be possible in Preview mode given the single page preview limitation
• [ ] General margin and padding styling should follow current design system standards (included in UX pin if needed)
• [ ] Campus map and directions link will not be needed, per Dave C.
• [ ] Validate this work using VAMC systems listed above (Because these newly hardened pages have not been rolled out to all VAMC systems, we need to validate using the systems which have piloted the templates and have data in them)
• [ ] Work with Steve Wirt and CMS team for deployment of these changes to production
• [ ] Work with Nick O to validate these changes

Acceptance Criteria

Register for care page is designed consistent with UX Pin spec, including

• [ ] When viewing health care Register for care page, Veteran sees "Patient registration (admissions)" heading
• [ ] When viewing health care Register for care page, Veteran sees "Not yet enrolled in VA health care?" heading
• [ ] Veteran can view "Patient registration (admissions)" content by clicking on jumplink
• [ ] Veteran can view "Not yet enrolled in VA health care?" content by clicking on jumplink
• [ ] The name of each facility is an H3
• [ ] A Veteran can click on the name of the facility from the medical records page and view the facility page
• [ ] General margin and padding styling should follow current design system standards (included in UX pin if needed)
• [ ] Deployment is coordinated with CMS team
• [ ] Steps taken to test these changes and their results are documented in this issue
• [ ] Nick has signed off on these changes with a comment in this issue

[mmiddaugh]

@GcioNapoleon, this issue is not blocked as facility name is not within a WYSIWYG - everything from name through hours is powered by a singular template Ethan can assist with the graphQL to pull facility name, if needed.