Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX: Revisit FE design for VA health service accordions #13932

Open
5 tasks
mmiddaugh opened this issue Sep 29, 2020 · 1 comment
Open
5 tasks

UX: Revisit FE design for VA health service accordions #13932

mmiddaugh opened this issue Sep 29, 2020 · 1 comment
Labels
Design CMS team practice area Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide VA.gov frontend CMS team practice area VA services taxonomy CMS-managed product owned by the Facilities team VAMC CMS managed product owned by Facilities team vamc-pages Veteran experience Pertaining to Veteran user experience

Comments

@mmiddaugh
Copy link
Contributor

mmiddaugh commented Sep 29, 2020

Issue description

VA health and non-clinical services may be offered at more than one location for a given health system. A given service might have multiple locations, each of which might use the same address as the main facility, another location on the campus or an offsite location

  • Service is offered at a single location which uses the facility address (displaying only a wing/room/suite)
  • Service is offered at a single location which does not use the facility address (displaying a full address, including - possibly- another city)
  • Service is offered at multiple locations, each of which may or may not use the facility address
  • Service locations may have different hours than the main facility and/or from each other.
  • Service locations may use the main facility phone number or have one or more additional distinct numbers, including one specifically for Appointments.

All service locations and the relevant associated information , such as phone numbers and hours of operation, should be presented in a visually distinct and understandable way.

Problems to solve

  • Veteran confusion can result when an editor misunderstands the intent, misuses the fields, or when the data is mishandled by the template.
  • Within a service accordion, service locations are not visually separated. It can be difficult to understand how many distinct service locations are listed, how headers are grouped, and which information relates to which location, especially for those using assistive tech.
Workflow system vs facility
  • Much of the information displayed for a facility's service is created at the system level. Service locations are entered at the facility level. This can be a confusing interface for editors.
    • Example: Portland VAMC Podiatry: Vancouver VA Medical Center and Salem VA Clinic are listed as podiatry service locations for the Portland VA Medical Center. These are facilities within the same health system and have their own service accordions. They should not be added as service locations for the Portland VA Medical Center.
Service location name
  • Editors can enter the Name of the office or location but the field is not required. If the field is not populated, nothing is displayed to give context to the associated information such as hours of operation or physical address. The absence of a name heading also can impact heading hierarchy. Example: Bath VAMC Mental health
Service location address
  • Editors can specify that the facility's street address should be used and/or choose to add Building name/number and/or Wing/Floor/Room info.
    • If the editor specifies that the location should use the facility address and does not enter additional information, no address is displayed. Example: Portland VAMC Podiatry
    • If the editor specifies wing/floor/room + facility address will display only the wing/floor/room information without the additional street address for context. Example: Bath VAMC Mental health
    • Editors need to understand what is expected for the Name field and how it is different from the Building name
    • Use of the word "facility" in this content block may not be clear
    • Editors need to understand how to enter details with the correct format (i.e., "Building 78, 3rd Floor")
Service location phone numbers
  • Editors can enter a number at the service level for appointments.
    • Editors need support to create meaningful phone labels
    • How should the UX support separate appointment numbers for each service location?
    • How should the front end display appointment phone numbers which are the same for each service location?
Service location hours of operation
  • Editors can specify that the service location uses the facility's hours, enter specific hours for the service location or display no hours at all. Comments can be also be added next to the hours for each day. There is a separate free text field for Additional hours options text field.
    • Editors need to understand what can be entered in the comment field and how the field is different from the Additional hours field. Examples: Bath VAMC Mental health: VCL, Care coordinator and Urgent care details and Portland VAMC Podiatry: the word "Varies" is displayed in italics without context
      • The help text for the Additional hours field is duplicative and does not provide necessary support.

Exported mural with Veteran front-end mapped to CMS editor UX


Related issues

Open questions

  • What logic should be used to determine the order of service locations?
    • Can we use parameters/variables to identify distinct service locations to use in applying sort order logic?
    • Editor specified?
  • If the service location has the same address as the facility on which it appears, should the location name and address already present on the screen be duplicated within the accordion?
  • Should Additional hours options be available when editor selects to not display hours? In combination with specified hours or with facility hours?
  • Which services could leverage service region to display national hotline numbers?

Acceptance criteria

FE design should include plan for the following

  • Separate locations should be visually distinct
  • Heading level hierarchy defined separate from should be maintained (although can be overridden for visual styles, if needed)
  • consideration for single service locations using all possible permutations
  • consideration for multiple service locations using all possible permutations
  • inclusion of service region for national phone number
@mmiddaugh mmiddaugh added the Design CMS team practice area label Sep 29, 2020
@mmiddaugh mmiddaugh changed the title [Consider] Iterations for facility health services [CONSIDER] Iterations for facility health services Jan 20, 2021
@jilladams jilladams added VAMC CMS managed product owned by Facilities team Drupal engineering CMS team practice area VA.gov frontend CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) labels May 30, 2023
@jilladams jilladams transferred this issue from department-of-veterans-affairs/va.gov-team May 30, 2023
@jilladams jilladams added the Epic Issue type label May 30, 2023
@jilladams jilladams changed the title [CONSIDER] Iterations for facility health services Facility Health Services: Iteration candidates May 30, 2023
@jilladams jilladams added VA services taxonomy CMS-managed product owned by the Facilities team Veteran experience Pertaining to Veteran user experience labels Jul 1, 2023
@mmiddaugh mmiddaugh changed the title Facility Health Services: Iteration candidates UX: Revisit FE design for VA health service accordions Jan 9, 2024
@mmiddaugh mmiddaugh removed the Epic Issue type label Jan 10, 2024
@aklausmeier
Copy link

@thejordanwood FYA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design CMS team practice area Drupal engineering CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide VA.gov frontend CMS team practice area VA services taxonomy CMS-managed product owned by the Facilities team VAMC CMS managed product owned by Facilities team vamc-pages Veteran experience Pertaining to Veteran user experience
Projects
None yet
Development

No branches or pull requests

3 participants