Work

Prescription management without the paperwork feeling

Specialty pharmacies coordinate patients, providers and prescriptions that need approvals and careful timing. WellDyneRX needed one platform that made sense at the pharmacy desk and in a patient’s pocket.

Role
End-to-end product design
Platforms
Web and mobile
Scope
Prescription management, patient workflows, provider coordination
Method
Research, journey mapping, prototyping, usability testing
In thirty seconds

The problem

Specialty prescriptions pass through prescriber, pharmacy, approvals and sometimes a nurse. Each handoff was a phone call or a fax, and nobody held the whole picture.

What I did

Designed the platform end to end: prescription management, patient workflows and provider coordination, across web and mobile.

What changed

One place to see where a prescription stands and act on it, for the patient and the provider.

6→ 2 steps
to request a refill when nothing has changed
−55%
phone calls per prescription between pharmacy and prescriber
92%
task success in usability testing on the patient app
2platforms
web for the pharmacy, mobile for patients and providers
Screens
PrescriptionStatus
Prescribed
Prior authorisation
Filled
Shipped
Need help?
Message pharmacy
Prescription statusEvery handoff visible to the patient, in order, with what happens next.
Patients
Needs auth
Provider coordinationPharmacy and prescriber in one thread, with the patient’s record beside it.
Refill request
Medication
Deliver to
Text me updates
Same prescriber
Request refill
Refill requestTwo taps when nothing has changed. The form only grows when it has to.

Schematic screens, not screenshots. The real ones are in the full case study.

Context

A specialty prescription passes through more hands than a normal one.

The prescriber, the pharmacy, an approval step, sometimes a nurse, and always the patient waiting to know what happens next. Each handoff was a phone call or a fax, and nobody had the whole picture.

How I found out

Research before commitment.

Mapped the journey across patient, prescriber and pharmacy first, to find the steps that only existed because the old process had them. Design decisions were framed as hypotheses and checked in prototype tests with users before anything was committed.

What I did

Map the journey first, then cut the steps the old process invented.

Designed the platform end to end: prescription management, patient workflows and provider coordination, across web and mobile. Mapped the journeys first, then removed the steps that only existed because the old process had them.

With the team

Hypotheses we could check with users before committing.

Partnered with product and engineering through research, journey mapping, prototyping and usability testing, with design decisions framed as hypotheses rather than opinions.

What changed

One place to see where a prescription stands, and to act on it.

A patient can see where each prescription stands, and a provider can act on it from the same place, with far less back and forth in between.

After launch

What happened next.

add yoursWhat the months after launch looked like: adoption, what the team kept, what was cut, and the follow-up work it led to. Two or three sentences are enough.

What I’d do differently

One thing I got wrong, and what I learned from it.

add yoursReviewers trust a case study more when it admits a misstep. Name one call that did not land, what it cost, and what you do differently now because of it.

Let’s talk

Which workflow is costing you the most right now?

Onboarding that leaks customers. An operations queue that still runs on phone calls. A design team that needs a lead. Tell me which one, and I’ll bring design, AI and twelve years of taking flows like that end to end.

Thirty minutes to start. You describe the product and what is slowing it down. I tell you honestly whether I’m the right person for it, and if not, who might be.