Digital prescription care for women, with health diagnostics

I led product design across the platform’s evolution, shaping core product features and user flows, product strategy and information architecture, and translating a complex healthcare infrastructure (telemedicine + pharmacy) into a cohesive, patient-facing experience for prescription care.

goodcleanclinicalcare.com

Platform

Responsive web platform

Duration

1 year (part-time)

My Role

Lead Product Designer

Team

Founder, Product Manager, Scientific Advisor, Project Manager, Mid-level Designer, Engineers, QA

key outcome

Clear separation between clinical consultations and commercial orders, enabling scalable medical workflows

key outcome

Clear separation between clinical consultations and commercial orders, enabling scalable medical workflows

key outcome

HIPAA-compliant consultation architecture with dedicated medical records and chat threads

key outcome

HIPAA-compliant consultation architecture with dedicated medical records and chat threads

key outcome

Split-payment checkout system aligned with regulatory and operational constraints

key outcome

Split-payment checkout system aligned with regulatory and operational constraints

about

Millions of women experience recurring vaginal health issues, yet accessing care remains slow, fragmented, and uncomfortable. Most treatments focus on short-term symptom relief, while the underlying causes often go unexplored — leading to repeated infections and frustration.

This platform reimagines vaginal healthcare through a telehealth-first, data-driven approach. By combining microbiome testing, medical consultations, and prescription care, we enable women to understand their condition, access licensed doctors remotely, and receive personalized treatment — all within a single digital experience.

Case Study 01

Designing a Scalable Prescription Experience

Case Study 02

Designing Split Payments Without Breaking Trust

Case Study 01

Designing a Scalable Prescription Experience

The original prescription experience assumed one treatment would become one prescription. As care evolved, provider visits began producing multiple outcomes, making the existing structure difficult to scale. I redesigned the experience around the clinical workflow, creating a more flexible foundation for complex treatment journeys.

The Problem

The product no longer matched how healthcare actually worked.

The original experience was built around one assumption: one request leads to one prescription.

In reality provider visit is rarely linear. One consultation can result in different outcomes depending on the patient’s medical needs

The original experience was built around one assumption: one request leads to one prescription.

In reality provider visit is rarely linear. One consultation can result in different outcomes depending on the patient’s medical needs

Couldn’t support multiple outcomes

Medication changes were hard to manage

Mixed active and completed states

Limited scalability for refills and follow-ups

Growing complexity created confusion

Initial Model

One request

One review

One prescription

Actual Workflow

One visit

Multiple clinical outcomes

One or more prescriptions

Independent medication
management

before

THE SOLUTION

Organize around provider visits, not requested medications

By separating active care from completed prescriptions, we created a structure that scales with real patient journeys.

Visits for active care and communication

Prescriptions as independent, manageable items

Clear states and next steps for patients

Built for flexibility and future scenarios

after

1

2

3

4

1

2

3

4

1. Ongoing Visits

Provider messages, treatment changes, approvals

2. Prescription Historyv

One card per medication, its own refill schedule and order history

3. Independent cards for each approved prescription

4. Dedicated refill management per medication

Sum Up

Product Impact

Clear Separation Between Care and Orders

By separating active consultations from prescription management, the experience better reflects the real clinical journey. Users can easily distinguish what requires their attention from treatments that have already been completed.

Clear Separation Between Care and Orders

Scalable Information Architecture

Organizing the experience around provider visits instead of individual prescriptions creates a flexible foundation that supports medication changes, multiple prescriptions, follow-up consultations, and future healthcare services without redesigning the interface.

Scalable Information Architecture

Simplified Prescription Management

Each approved medication becomes an independent object with its own refill status, order history, and available actions. This reduces cognitive load while making long-term treatment management more intuitive.

Simplified Prescription Management

Reduced User Uncertainty

Keeping provider communication, treatment progress, and prescription management within clearly defined stages helps users understand where they are in the care journey and what happens next, increasing confidence throughout the experience.

Reduced User Uncertainty

Case Study 02

Designing Split Payments Without Breaking Trust

To access prescription care, every user must go through a medical review by a licensed provider. This review is a real medical service and, due to regulatory and operational constraints, it must be:

Charged separately from any product
Paid upfront, before a prescription can exist
Processed by our telemedicine partner

At the same time, many users arrive with a clear intent: “I know what medication I want, I just need approval.” This creates a core UX and business challenge — charging for medical care upfront while keeping users moving smoothly toward treatment.

Key Design Risks

Users pay for medical care before knowing if they’ll receive treatment.

Paying before approval

Key Design Risks

Any lack of clarity feels riskier when health and money are involved.

Trust in a medical context

Key Design Risks

Two different charges in one journey breaks standard e-commerce expectations.

Split payments

Key Design Risks

Two different charges in one journey breaks standard e-commerce expectations.

Split payments

Considered Options

Two Ways to Handle Payments in a Medical Flow

Charge Everything Upfront

(Consultation + Medication)

Pros

Single checkout

Simple payment logic

No saved payment method

Cons

Users may pay for treatment they never receive

Requires refunds if not approved

High trust risk in a medical context

Complex support and dispute handling

Two Separate Checkouts

(Pay doctor → come back and pay for medication)

Pros

Fully transparent

No premature product charge

Clean compliance model

Cons

Users must return after approval

High drop-off in second step

Breaks momentum for ~90% approved users

Final Decision

Charge Medical Care Now. Charge Medication Only If Approved.

I designed a hybrid flow where the user first selects a prescription product and pays only for the medical consultation, with their payment method securely saved. The doctor then reviews the case asynchronously, and if approved (around 90% of cases), the medication is automatically charged and shipped with no further action required. If not approved, no product charge is made and the user receives a clear explanation or alternative options. This approach allows users to complete their purchase intent in one step, while ensuring all charges remain medically appropriate and ethically sound.

For users

No repeated checkout

Clear expectations

Minimal friction after approval

For the business

Higher post-approval conversion

Lower drop-off during review window

Fewer refunds and support cases

1

2

3

4

5

1

2

3

4

5

1. How it works

Shows each step to set expectations and reduce uncertainty.

2. Authorization checkbox

Captures user authorization for charges and data storage.

3. Pre-purchase FAQs

Addresses concerns that may block checkout.

4. Split charges

Clearly distinguishes consultation and medication charges.

5. Payment summary

Shows what is charged now versus after approval.

Sum Up

Next Steps

Payment Mental Model Validation

I would test whether users interpret the medical consultation fee as a legitimate doctor visit, rather than as a platform fee or hidden cost. This includes observing whether users expect to pay before medical approval, and how they perceive the value of the consultation itself. This would validate whether the pricing structure matches real healthcare expectations.

Payment Mental Model Validation

Charge Transparency & Comprehension

I would evaluate how clearly users understand the difference between “charged today” and “charged if approved.” This includes testing whether users can correctly explain the payment flow after going through checkout, and whether any part of the process feels confusing or misleading. This would surface gaps in labeling, copy, or hierarchy.

Charge Transparency & Comprehension

Friction vs Fairness Tradeoff

I would explore whether saving payment details and charging automatically after approval feels convenient or uncomfortable to users. This includes testing alternative patterns such as manual confirmation versus automatic charging, and measuring where users draw the line between friction and perceived control. The goal would be to ensure that reduced friction does not come at the cost of user confidence.