Furscription

Problem

Before software like this, a prescription left the clinic as a fax, a phone call, or a handwritten pad sheet, and every online pharmacy had its own portal with its own login. A vet finishing an appointment had to remember which channel this particular pharmacy wanted, re-key the client's address and the pet's weight by hand, and then field the callback when something was illegible. The task isn't complicated; it's just repeated forty times a day, and every repetition is a chance to transcribe a dose wrong.

Process

1 Start with who the prescription is for2 Pick the pet from the client's record3 Find the product as you type4 Directions for use, on one screen5 Review everything before it goes out6 Authorize with a signature

1 / 6

Start with who the prescription is for

Every prescription begins with a client, so the first screen asks one thing: who is the pet owner? A single search field with a Client Name filter keeps it fast for a clinic that knows its regulars, and the five-step stepper across the top sets expectations before any data is entered.

Pick the pet from the client's record

Once a client is chosen, their pets appear as cards showing species, breed, weight, date of birth and neuter status. That detail is there so the wrong Cooper or Marley cannot be picked by accident. The client moves into a summary rail on the right with a Switch button, and the completed step turns into a checkmark.

Find the product as you type

Product search returns matches after only a few characters, so typing apoq is enough to surface every Apoquel strength and form. Each result carries the strength, the form and the active ingredient, which is what separates one row from the next. The rail now holds both the client and the pet, so the context stays in view while choosing.

Directions for use, on one screen

Quantity, refills, days supply, expiry and substitution sit together in a grid, with sensible defaults such as an expiry computed from today. Directions can be picked from predefined text or written freely, and the pharmacist message has its own field. Character counters on both text areas show the limits before anyone hits them.

Review everything before it goes out

The review page collects the pet, the client, the pharmacy and every medication detail in one place, each block with its own Edit or Switch. A warning marks the directions as still pending, so a gap cannot slip through unnoticed. Saving a draft, submitting for approval and authorizing are three separate actions, matching how clinics with staff preparers actually work.

Authorize with a signature

Authorizing is a deliberate moment. The dialog shows the prescriber's license details, their saved signature and a plain language disclaimer that must be confirmed with a checkbox before the button is available. The signature is the one that will appear on the outgoing prescription, and it can be updated without leaving the flow.

← BackNext →

UX flow

Two paths to one outcome: the five-step wizard from scratch, or a refill request that already knows its client, pet and drug. Both return to the queue.

UI system

The pieces those colors get spent on, lifted straight out of the product. Buttons, fields, the stepper, the status pill, the card shape that repeats for clients, patients and products: the small set everything else is assembled from.

Complete, current and not-yet-reached, so progress is never ambiguous.

One filled button per screen; everything else is an outline.

The queue's three working states, and the pill a row carries.

Label above, hint inside, state carried on the border.

Predefined directions offered before free text, with a counter.

Selection is a tinted row with a coral edge: a state, not a button.

One card shape for client, patient and product, each switchable.

The same object whether it's a search result or pinned in the rail.

Column headers with the sorted column marked.

Color palette

Two brand colors and three neutrals pulled from them. The neutrals do almost all the work: in software a vet stares at for hours, color has to mean something when it finally appears.

Design notes

The product is a queue and a wizard. The queue is one table of every prescription in flight, filtered to the three states that actually need a human, sorted so whatever is closest to lapsing rises to the top, openable between appointments and closable again. Everything else (the scoped filters, the record-card search, the context rail) exists so a vet never has to hold anything in their head from one appointment to the next.

1234

1. 1Status filters open on everything still waiting on a vet.
2. 2Four filters scoped to a field, rather than one fuzzy search box.
3. 3Duration sorts the queue, so what's about to lapse rises to the top.
4. 4Nav is named after the job (New Rx, Faxes), not after database tables.

1234

1. 1Five numbered steps, visible from the first screen to the last.
2. 2Every result is a whole record (phone, email, address) so you can tell two clients apart at the moment you choose.
3. 3Emails stay masked until there's a reason to reveal them.
4. 4Search scoped by field, so a common surname stays findable.

1234

1. 1The rail holds client, pet and drug, each with its own Switch: changing your mind doesn't mean backing out through three screens.
2. 2Expiry computed from the prescribing date rather than typed in.
3. 3Predefined directions offered first; free text stays available underneath.
4. 4Counters on every field a pharmacist has to read back.

Outcome

The redesign held as the product grew. Furscription launched under Wag! and is now distributed through MWI Animal Health, reaching far more clinics than the original flows were drawn for, and the queue and the five-step wizard are still the structure the product is built around.