Clarify alert when systems can't display types of appointments

[outerpress]

Task Description

• This ticket calls out when specific service that's down in alert message. This is a follow-up to #55116
• Sometimes backend services can't display types of appointments. Users need to be notified when VAOS can't display some appointments
• We don't know if the user has appointments of the type we can't display. So some users will be notified, even though the issue doesn't affect them.
• Given that, the notification should be less disruptive than a standard alert, but still provide information when needed
• The situations in which appointments can't be displayed are:
  • Upcoming and past - any combination of:
    • VistA doesn't send back VA in-person appointments
    • VistA doesn't send back phone appointments
    • HSRM doesn't send back CC appointments
    • VVS doesn't send back video appointments
  • Requests - any combination of:
    • VistA doesn't send back VA requests
    • HSRM doesn't send back CC requests

References

• 53370 - Alert when HSRM is unavailable

• 53372 - Alert when VVS is unavailable

Acceptance Criteria

• [ ] content review complete
• [ ] m/t/d dev specs complete

[outerpress]

• @Cieramaddox to work with @ldelacosta on getting content review started

[outerpress]

@ldelacosta adding this to the small improvements Epic - this clarifies in the alert that we can't show community care or VVC appointments. Was there a technical barrier to this one?

[outerpress]

Marcy found an issue with this messaging conflicting today. I'd add fixing this issue to the work. Slack thread