Role: UI/Visual Design
Client: CVS Health
Role: UX Design
Client: CVS Health
"Optimize results and improve outcomes for clinical studies and trails in healthcare intelligent data analytics"
The Payments Platform is for remote payments on the pharmacy side of CVS health to be bidirectional into the billing and payments side of commerce/retail pharmacy. This project was to design a payments platform for Individuals, Caregivers and Health admins to facilitate online payments and tracking of retail, pharmacy, FSA, etc. purchases.
My role in this project began with assembling wireframes and continued into creating UI components across web & mobile screens. I assisted in the assembly & annotations of the wireframe deck. I then moved into the visual design part of the project to collaborate with other designers on overall UI design and implementation. Remote Payments was to be rolled out as responsive web and on the CVS mobile app.
Iterated on stlye and brand guidlines
Our problem to solve for was for multiple intended use cases. We had individuals, caregivers, family of patients and health admins. Each with their own unique “happy path” requirements and privacy adherence. Once in the system each user would need to have payment and patient details added. The user may also want to edit these or add to their payment app. For a standard pharmacy user this was fairly straightforward but was problematic in the case of families and healthcare providers who may have multiple “patients” and payment methods. As well as hosting relevant information there were privacy notifications and verification steps when requesting new prescriptions. We were also incorporating a new overall design direction that was being rolled out across multiple projects.
Team worked on wireframes to be tested & validated through to the next phase.
Final design look & feel
We designed a simple but clear signup page based on the most common use cases. The user would choose the best path where they would be led the their respective sign-up questions. We reused the same interaction methodology from customer sign up in the return login steps & new selection of people/cards and would customize your experience appropriately.
We decided on a notched/tabbed approach for the UI to allow for easy navigation but also to keep the interface clean to help the user focus on each task specifically at hand. Regardless of the use case you either had “People” or “Cards” and notifications. When adding new people or cards we had a clean wizard-like form guiding the user through the process, such as how your card could be used and for what pharmacy payment methods and various user/privacy preferences.
We understood that with multiple cards/people it might get confusing so we allowed for organizing and nesting/labeling as well as nicknaming cards, allowing for default setting or linking of multiple people to the same payment method. The final result is a clean and modern approach to a complex set of user inputs and steps that through user testing was validated and iterated to a flexible and mobile first payment platform.
Iterations on form feilds and UI interactions
Example of a few mobile screens