Analytics

Therapy Discontinuation Reasons in Specialty Pharma: Why "Other" Is Your Biggest Category, and How to Fix the Reason Codes

Why discontinuation reasons from hubs and specialty pharmacies end up as other or unknown, and how to build a reason model leaders can act on.

Oct 20265 min readAnalytics

Why the reason a patient stopped is the least trusted field in the report

Every specialty brand tracks how many patients stop therapy. Far fewer can say why with any confidence. Ask for the top discontinuation reasons from last quarter and the chart usually leads with a bar labelled other, unknown or patient choice. The categories that would change a decision, such as a prior authorization renewal that lapsed, a copay the patient could not afford or side effects nobody followed up, are spread thinly across the rest.

This is not because nobody asks. Hub case managers, specialty pharmacy staff and nurse educators record reasons every day. The problem is that each source uses its own list, the reason is chosen by whoever closes the record, often weeks after the patient went quiet, and many patients stop without anyone recording a reason at all. When the files are combined, the lists are flattened into a handful of broad buckets and the detail is lost.

The cost is real. Medical affairs cannot see a tolerability signal early. Patient services cannot tell which stops were preventable. Market access cannot show a payer that its renewal criteria are pushing patients off therapy. This article sets out why discontinuation reasons degrade, a reason model that holds up, and how to put it in place. It builds on our guides to mapping SP and hub status codes and defining an active patient.

Four reasons the reason codes fail

  • Every source has its own list

    Each specialty pharmacy, the hub and the nurse program record reasons in their own words and codes. Combined without a mapping table, they collapse into broad buckets.

    • Twenty source codes mapped to five labels
    • Free text never read
    • New codes land in other by default
  • The reason is recorded late

    A patient misses a refill, outreach runs for weeks, and the record is closed long after the moment that mattered. By then the person closing it often does not know why the patient stopped.

    • Closure date is not stop date
    • Reason chosen to close the case
    • Context sits in call notes
  • Silent stops have no reason at all

    Many patients simply stop refilling and never answer outreach. These are the patients most worth understanding, and they are usually counted as unknown or not counted as a stop until the grace period runs out.

    • Lost to follow up is a status, not a reason
    • Unknown share rarely reported
    • Data around the stop is never checked
  • One patient, one reason

    Real stops have more than one cause: a renewal lapsed and the copay rose at the same time. Forcing a single reason hides the access and financial causes behind whichever is easiest to record.

    • Primary and contributing reasons
    • Access causes recorded as patient choice
    • No link to PA or copay events

What a discontinuation reason model that holds up looks like

A small, owned taxonomy
Every source code mapped
Stop date separate from closure date
Evidence beside the label
Unknown reported as a number

How to put it in place

Pull every reason code in use

List every discontinuation and closure reason from each specialty pharmacy, the hub and any nurse or adherence program, with how often each is used.

Agree the taxonomy

Bring patient services, medical, market access and analytics together to agree the top-level groups and sub-reasons, with a definition for each.

Map and date it

Map every source code into the taxonomy in one governed table with an effective date and an owner. Alert on any code that is not mapped.

Attach the evidence

Link each patient's stop to PA, claims, copay and safety events from the 60 days before it, so reviewers can see what changed.

Review the unknowns monthly

A short monthly review of unknown and other stops, using the evidence, keeps the taxonomy honest and shows where outreach scripts need to change.

Questions leaders ask about discontinuation reasons

Why is other or unknown our largest discontinuation reason?
Usually because each source uses its own reason list, the lists are flattened when combined, and many patients stop without anyone recording why. Mapping every source code and reporting the unknown share separately is the first step to shrinking it.
Should we record one reason or several?
Record a primary reason and allow contributing reasons. Stops often have an access or financial cause alongside a clinical or patient one, and a single forced choice tends to hide the access causes.
What is the difference between a stop date and a closure date?
The stop date is when the patient's last supply ran out, based on fill date plus days supply. The closure date is when someone closed the hub or pharmacy record. Persistence and reason trends should use the stop date.
Can AI fill in missing discontinuation reasons?
It can help by reading call notes and suggesting a reason, but only once the taxonomy is agreed and the events around each stop are linked. Suggestions should be reviewed and labelled as inferred, not recorded as fact.
Who should own the discontinuation reason taxonomy?
Patient services usually owns it, with medical affairs and market access agreeing the groups that matter to them. Analytics maintains the mapping table, and every change is dated so trends stay comparable.

Compare your discontinuation reasons with ours

Send us last quarter's discontinuation reason chart and the source code lists behind it. We will show where the detail is being lost and what a reason model would look like for your brand. More on our work at specialty pharma analytics and automation.

Contact us

Part of our Pharma Commercial and Patient Analytics hub. Start with our specialty pharmacy analytics.

Talk to us

Is this a problem you are living with?

If any of the above sounds like your week, tell us which part. We will come back with what it would take to fix it.

  • A reply from a consultant, not a sales sequence
  • Usually within one working day
  • No obligation, and nothing to sit through

We reply from [email protected], usually within one working day. We do not add you to a mailing list.