CVS Accountable Care

The brief

CVS Accountable Care needed a public web presence and a custom workflow through which Medicare participants could submit applications. The visible experience had to remain approachable while the system behind it enforced specific data requirements.

I contributed to both the website and the application integration, with particular attention to the boundary between user-friendly input and dependable downstream data.

What made the workflow sensitive

Application forms often appear straightforward from the outside. In practice, they sit between people, eligibility or program requirements, internal operations, and other systems that expect data in exact shapes.

This workflow required more than checking whether fields were filled in. It needed deliberate constraints, clear validation behavior, and predictable handling when information was incomplete or could not move forward.

The public case study intentionally stays at that architectural level. It does not expose applicant data, private field definitions, or the rules used to evaluate submissions.

The approach

The implementation treated validation as part of the product rather than an error message added at the end.

My contribution emphasized:

• structuring the application flow around the information required at each step;
• applying validation close to the point where users could correct an issue;
• preserving consistent data shapes for downstream handling;
• accounting for failure and incomplete-submission paths; and
• keeping the public experience clear despite the underlying constraints.

The website and application flow were considered together so that the handoff did not feel like a separate or less trustworthy system.

Historical context

This case study describes work completed for CVS Accountable Care during 2024–2025. CVS later sold its Medicare Shared Savings Program business to Wellvana and exited the ACO REACH pilot. The official March 2025 notice provides the current business context.

The takeaway

This project demonstrates how I approach forms whose consequences extend beyond the browser. The interface, validation contract, recovery path, and downstream handoff all have to be designed as one workflow.