Eng: Update SM widget link behind toggle (Ph2)

[wesrowe]

REFINEMENT: Prefer to do all 4 or 5 widget updates in one ticket, or split up?

Description

User story

As a Veteran, I want the widget experience on the unauthenticated Secure Messaging page to offer a single link to the VA.gov version of SM, even if I have Oracle Health facilities, so that I stay on VA.gov and only one experience is complicated by OH.

As a Cartography team member, I want to feature-toggle the widget's MHV link between Classic and VA.gov, and the removal of the OH link, so that we're prepared for full VA.gov integration.

Notes

• Unauthed page: www.va.gov/health-care/secure-messaging/
• Danielle agreed to the idea of removing Oracle Health links from the widget – instead, all authenticated-and-verified users should be given a single link to the Appointments tool on VA.gov
• Once this one goes smoothly, we can update content in the other three tool widgets (Appts, Records, Meds)

Possible tasks:

• Create/identify a single feature toggle that can release the changes for all tool widgets simultaneously.

Acceptance criteria

• All changes are behind a feature toggle
• With the toggle enabled, a single CTA link component links to VA.gov tool: /my-health/secure-messages
• QA review
• A11y review

[wesrowe]

@sterkenburgsara, to clarify: Can we remove the Oracle links from the widget when we first touch it? Or do we have to put all the changes behind a feature toggle – i.e., we can only remove the OH buttons at the same time we link to the VA.gov portal?

I don't know if it's risky UX-wise to send OH users to Classic.

(Ticket currently has all changes behind a toggle, which seems like the conservative approach.)

[sterkenburgsara]

@wesrowe good question. I would like to discuss with Laura + Danielle. Came up in this Slack thread I started here. I agree it's not a good idea for UX to send OH/Cerner users to the national portal unnecessarily & like the approach of putting it behind a feature flag.

[sterkenburgsara]

Can we start with appointments instead? I think we can definitely go forward with this plan for that tool since it already points to the VA.gov version.

[wesrowe]

I switched the ticket to SM because it's more challenging :-D

What I'll do: write a new ticket for Appts.