21-0779 Form: Pre-Staging Bugs And Issues

by SLV Team 42 views
21-0779 Form: Pre-Staging Bugs and Issues

Hey everyone! Before we dive into the staging review for the 21-0779 form, it's super important to address the known bugs lurking in the staging environment. This helps ensure a smoother review process and ultimately a better experience for our users. Let's break down the issues we've spotted so far.

Global Bugs

When addressing global bugs, let's think about the overall user experience. These are the kinds of issues that can impact the entire form, so nailing these is crucial for a seamless interaction. We're talking about the foundational elements that keep users engaged and moving forward.

  • Button Padding: The padding between the “Back” and “Continue” buttons is currently too large. We need to reduce this to 8px. This isn’t just a minor detail, guys; consistent spacing helps users navigate the form effortlessly. Imagine accidentally hitting the wrong button because they're too far apart – we definitely want to avoid that! This applies across all four forms, so it's a high-priority fix.

  • H3 Styles: The H3 heading styles appear to be off, almost resembling H4 styles instead of the intended VADS H3. This can create visual inconsistencies, making the form feel less polished. It’s possible the Figma H3 styles are outdated, so we need to double-check the correct class implementation. Proper heading styles are vital for content hierarchy, ensuring users can quickly scan and understand the information. So, let's get those H3s looking sharp!

Introduction Section

The introduction is like the handshake of the form – it’s the first impression. It needs to be clear, concise, and welcoming. We want users to feel confident they're in the right place and know exactly what to do. Let's fix these issues to make that first impression count!

  • Intro Text Update: The current intro text, “Use this form to verify a Veteran or someone connected to a Veteran is a patient in a qualifying extended care facility,” needs a slight tweak. We’re updating it to “Use this form if you’re a nursing home official to verify a Veteran or someone connected to a Veteran is a patient in a qualifying extended care facility.” This small change adds clarity by specifying the intended user, which is super important. You can see the proposed change in this PR.

  • Typeface Adjustment: The intro text should be updated to the Body/Intro typeface, specifically Bitter 20. This helps maintain consistency with our design system and creates a more visually appealing experience. Font consistency is key to a professional look and feel, and it's one of those subtle details that can make a big difference.

  • Unauthenticated Form: The form needs to be fully unauthenticated. Currently, users have the option to sign in, but this form should be accessible without requiring authentication. This ensures ease of access for nursing home officials who may not have VA accounts. You can track the progress on this PR.

You can reference the staging environment and the Figma design for context.

Step 1: Your Personal Information – Nursing Home Official Details

Step 1 focuses on collecting the nursing home official's personal information. This step is crucial for establishing a point of contact and ensuring we have accurate details for verification. Let's make sure this section is clear and user-friendly.

  • Phone Number Field: The phone number input field should be marked as required. While it currently functions as required, it doesn't visually indicate this to the user. This can lead to confusion and potentially missed information. Adding the visual cue (*required) is a simple fix that greatly improves usability.

Figma reference: Nursing home official personal information

Step 3: Patient Information (Veteran Selected)

Step 3 is where we gather patient information, specifically when a Veteran is selected. Accurate patient details are essential for proper processing, so let’s ensure this section is crystal clear.

Veteran’s Name and Date of Birth

  • H3 Update: The H3 heading should be updated to read “Veteran’s name and date of birth.” Consistency in headings helps users navigate the form more easily. You can follow the PR change here.

  • Date of Birth Fields: This is a nice-to-have! Ideally, we’d update the birth date fields to the dropdown version seen in the Figma file. This offers a more user-friendly input method compared to free-text fields. However, we need to consider potential feedback from Platform during staging review, as the staging environment currently uses a different date picker. If time allows, this would be a great enhancement. The relevant PR change is here.

Figma reference: Veteran’s name and date of birth

Veteran’s Identification Information

  • H3 Update: Similar to the previous section, update the H3 heading to “Veteran’s identification information.” Headings are our friends!

  • Text Replacement: The text “You must enter either a Social Security number or VA File number” needs to be replaced with “You must enter the Veteran’s Social Security number. You can also enter a VA File number if available.” This clarifies that the Social Security number is mandatory, while the VA File number is optional. Clear instructions are crucial to minimize user errors. This change is tracked in this PR.

Figma reference: Veteran’s identification information

Step 3: Patient Information (Spouse or Parent Selected)

This section mirrors the previous one, but it's tailored for when a Spouse or Parent is the patient. Let’s ensure the same level of clarity and accuracy here.

Name and Date of Birth

  • H3 Update: Update the H3 heading to “Patient’s name and date of birth.” You know the drill!

  • Date Component Feedback: Just like in the Veteran section, we have the same feedback regarding the date component. Ideally, we’d use the dropdown version from Figma, but this is another nice-to-have that depends on Platform feedback and time constraints. The relevant PR is here.

Figma reference: Name and date of birth

Patient's Identification Information

  • Text Addition: Add the text “You must enter the patient’s Social Security number. You can also enter a VA File number if available.” below the H3. This mirrors the clarification provided in the Veteran section and ensures users understand the required information. See the Figma design for reference and track the PR change here.

Figma reference: Patient's identification information

Step 4: Level of Care

This step focuses on gathering details about the patient's level of care, specifically the date of admission. Getting this right is key for accurate record-keeping.

Date of Admission

  • Container Size: The container size for the question label “When was the patient admitted to the nursing home? (*Required)” appears narrower than usual. While this isn't a launch blocker, it would be great to investigate if we have time before November 11th. This was addressed with the switch to select date inputs in this PR.

  • Date Component Feedback: We have the same feedback about the date component using the dropdown, as mentioned in Step 3. Let’s keep this in mind for future improvements. The PR is here.

Figma reference: Date of admission

Step 5: Medicaid

Step 5 delves into Medicaid-related information, which is essential for understanding the patient's financial situation and coverage.

Medicaid Start Date

  • Date Component Feedback: Once again, we have the same feedback regarding the date component. Consistency is key! The relevant PR is here.

Figma reference: Medicaid start date

Monthly Costs

  • Hint Text Addition: Add the hint text “Include the patient’s Share of Cost Medicaid” to the monthly costs field. This provides crucial context and helps users enter the correct information. You can track the progress on this PR.

Figma reference: Monthly costs

Confirmation Page

The confirmation page is the final step, providing users with confirmation that their submission was successful. It’s our last chance to leave a positive impression and provide helpful next steps.

  • Submission Date: Add the submission date to the success alert. This gives users a clear record of when they submitted the form, which is always a good practice. The PR for this is here.

  • **