[CDP] Current and possible statuses for VHA copay debt

[charlottecesana]

Description

We need to better understand the current VHA copay debt statuses that exist currently and possibly create additional ones if the ones available do not reflect the full range of statuses of a copay debt.

This undertaking has similar goals in mind as the Diary codes - Suggestions and Questions #80146 for VBA.

Understanding the diary codes will allow us to create a status delineation to surface a different type of alert (informational or alert, color-coded depending on severity) depending on the time-based progression of the debt and level of severity (from first notice of money owed, to becoming a debt, to being sent to collections, and treasury). [First layer]

Secondly, understanding the statuses and mapping these to the correct alert will allow us to recommend the best action or actions to the Veteran based on the level of their debt situation. The experience will be more dynamic and tailored. [Second layer]

Given: When: Cards, Alerts Then:

Tasks

• [x] Identify which are shown in the portal (indicate those that we don't show - for transparency)
• [ ] Identify what proposed changes we have, based on what we know - then they can react and course correct but we can likely make some assumptions to unify the messages across the card and component
• [x] Identify what question we have for the diary code that we don't understand or have enough context on.
• [ ] Denise will reach out to Bob for additional information

Acceptance criteria

• [x] All current status possibilities identified
• [x] Statuses that are not currently available but needed to be identified
• [x] Questions defined
• [ ] Proposed changes defined

Testing

• [ ] N/A if non development work
• [ ] Testing passed and documented in this ticket based off the "Then" statement in the description
• [ ] Testing procedure:
• [ ] If additional testing steps or credentials to perform testing are needed list them here

Questions for SMEs

[mgleo]

https://github.com/department-of-veterans-affairs/vets-website/blob/c9c16def72a2f7fb080a1ba6fba976965a5bd369/src/applications/combined-debt-portal/combined/components/MCPAlerts.jsx < Statuses as shown on production

[mgleo]

Since alerts are attached to location: Do they need to be attached to a specific copay?

[HeatherRienks]

re: Megan's question above- team agreed in Design sync that alerts will be attached to a VA location, not a specific copay. FYI- VHA has fewer statuses.

[HeatherRienks]

VHA MVP work is secondary to VBA MVP work. We will be closing this ticket and creating a new ticket with any outstanding work.

[mgleo]

VHA statuses documented on VHA Statuses tab

[josephrlee]

Here's what we see currently:

• Error
• Past Due
• No VA Healthcare in the past 6 months
• Zero balance

  <p className="vads-u-margin--0">
    Your balance was updated on {formatDate(date)}. Pay your full balance or
    request financial help before
    <strong className="vads-u-margin-left--0p5" data-testid={`due-date-${id}`}>
      {calcDueDate(date, 30)}
    </strong>
    , to avoid late charges, interest, or collection actions.
  </p>
);

CurrentContent.propTypes = {
  date: PropTypes.string,
  id: PropTypes.string,
};

const PastDueContent = ({ id, date, amount }) => (
  <p className="vads-u-margin--0">
    Your balance on
    <strong data-testid={`due-date-${id}`} className="vads-u-margin-x--0p5">
      {formatDate(date)}
    </strong>
    was {currency(amount)}. If you haven't either paid your full balance or
    requested financial help, contact the VA Health Resource Center at{' '}
    <va-telephone contact="8664001238" /> (
    <va-telephone tty contact={CONTACTS[711]} />
    ). We're here Monday through Friday, 8:00 a.m. to 8:00 p.m. ET.
  </p>
);

PastDueContent.propTypes = {
  amount: PropTypes.number,
  date: PropTypes.string,
  id: PropTypes.string,
};

const Alerts = ({ type, copay, error }) => {
  switch (type) {
    case 'status':
      return <Alert.Status copay={copay} />;
    case 'no-health-care':
      recordEvent({
        event: 'visible-alert-box',
        'alert-box-type': 'warning',
        'alert-box-heading': 'You're not enrolled in VA health care',
      });
      return <Alert.NoHealthcare />;
    case 'no-history':
      recordEvent({
        event: 'visible-alert-box',
        'alert-box-type': 'info',
        'alert-box-heading':
          'You haven't received a copay bill in the past 6 months',
      });
      return <Alert.NoHistory />;
    case 'zero-balance':
      recordEvent({
        event: 'visible-alert-box',
        'alert-box-type': 'info',
        'alert-box-heading': 'You don't need to make a payment at this time',
      });
      return <Alert.ZeroBalance copay={copay} />;
    case 'past-due-balance':
      recordEvent({
        event: 'visible-alert-box',
        'alert-box-type': 'info',
        'alert-box-heading': 'Your balance may be overdue',
      });
      return <Alert.PastDue copay={copay} />;
    default:
      recordEvent({
        event: 'visible-alert-box',
        'alert-box-type': 'error',
        'alert-box-heading':
          'We can't access your current copay balances right now',
        'error-key': error?.status || '',
      });
      return <Alert.Error />;
  }
};

[mgleo]

@Tom-Davis @HeatherRienks Moved to validate

[josephrlee]

The next ticket we'll need to create a task list of what proposed changes we want for these statuses.

[Tom-Davis]

Complete for now as priorities shifted and we will make a new ticket when this picks pack up. Closing.