Why Do Stable Patients Get Forced Back Through Step Therapy When the Formulary Changes?

How to Keep a Stable Patient on Therapy Through a Formulary Change

The goal is simple: a controlled patient stays on the drug that controls them, without a fresh failure the disease does not need. Here is what does that, move by move.

1. Catch the Formulary Bulletin Before the Change Date

The switch is only a crisis if it surprises you. Payers publish formulary changes ahead of the plan year, but nobody at a busy practice is reading every bulletin against a panel of active patients. The first move is to flag every formulary change that touches a patient you have on that drug within a couple of days of publication, while there is still runway to act. A change caught in advance is a continuity exception you file calmly; a change caught at the pharmacy counter is a flare you fight later.

2. File the Continuity-of-Therapy Exception With Stability Evidence Built In

Most stable-patient switches are avoidable if you ask the plan to honor continuity of therapy before the change bites. That means an exception request that leads with the evidence: how long the patient has been on the drug, the disease control it produced, the labs and visit notes that show stability, and the clinical risk of destabilizing a controlled patient for a rebate. When the request is framed as continuity of care rather than a new start, many payers will grandfather the patient rather than force a refail.

3. Cite the State Step-Therapy Override Statute and Its Deadline

Most states now have step-therapy override laws that require an exception when a patient is stable on their current drug, and many set a hard clock on the payer’s response. The move is to know which statute applies to the patient’s plan, cite the specific continuity-of-therapy override in the request, and hold the payer to the response deadline the law sets. A payer working against a binding statutory clock behaves very differently from one you are simply asking nicely.

4. Work the Appeal the Moment a Denial Lands

If the exception is denied anyway, the clock that matters is the patient’s supply, not the payer’s queue. The moment the denial lands, the appeal goes out with the stability record and the statute attached, a bridge or sample supply is arranged so no dose is skipped, and the case is escalated to a real reviewer instead of a form letter. A stable patient who misses weeks of a biologic does not just wait; they flare, and that flare is far more expensive than the exception that would have prevented it.

5. Hand Formulary Churn to a Dedicated Team

Practices that stop losing stable patients to plan-year churn do it by handing formulary monitoring and continuity exceptions to a dedicated team: remote specialists who read the bulletins, file the exceptions, cite the statutes, and work the appeals, live in 1 to 2 weeks. The prescribers go back to managing disease instead of chasing rebate contracts, a trained backup covers every gap, and the formulary change stops being the thing that quietly undoes a year of control. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Why This Keeps Happening

If the patient is stable and documented, why does the plan still force a refail? Because the review is not asking whether the drug is working; it is enforcing a formulary change driven by a rebate contract, and unless continuity of therapy is specifically negotiated, that change applies to existing patients the same as new starts. The Coalition of State Rheumatology Organizations has spent years documenting how these fail-first requirements land hardest on patients who are already controlled, and biologics for autoimmune conditions are among the categories most exposed to plan-year churn. The denial is a contract decision wearing a clinical letter.

The stakes are not abstract, because interrupting a working biologic is not a neutral event. Research on biologic access has found that when authorization for a working therapy is lost, a meaningful share of patients abandon that treatment entirely within months rather than restart it, and for an autoimmune patient a lapse is a flare waiting to happen. When a formulary switch drops into a busy practice’s auth queue, it competes with every other request, and the stable-patient exception rarely gets worked first even though it is the one where a delay does clinical damage. Closing that gap is exactly what an AI prior authorization workflow with human oversight is built to do.

And the cost is not just the flare. State step-therapy override laws exist precisely because stable patients were being forced off working therapy, and most states now require a continuity exception when a patient is controlled on their current drug. But a statute only helps if someone cites it and holds the payer to the clock; a right nobody invokes is a right that does not protect the patient. The practices that lose the fewest stable patients are the ones treating each formulary bulletin as a deadline to beat, not a letter to react to after the damage is done.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like at plan year? The specialist starts where the practice usually cannot: reading the formulary bulletins against your active panel so a tier move on a drug one of your patients depends on is caught within days, not at the pharmacy counter. Then they file the continuity-of-therapy exception with the stability evidence built in, the years on the drug, the disease control, the labs, and route it to the reviewer who can actually grandfather the patient. Most stable-patient switches are a documentation-and-timing problem, and that is exactly what dedicated prior authorization support is built to solve, before it ever becomes a flare.

When the payer pushes back, the specialist takes the statute off the shelf. They know which state step-therapy override law applies to the patient’s plan, cite the specific continuity provision, and hold the payer to the response deadline the law sets, so the request is working against a binding clock instead of an open-ended queue. If a denial lands anyway, the appeal goes out the same day with the stability record and statute attached, and a bridge supply is arranged so the patient never skips a dose while the fight plays out.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads the bulletin, assembles the stability packet, and flags the statutory deadline; a person confirms the clinical case is right and owns the appeal. Every security control that protects the chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical documentation through an auth workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team hold the formulary line better than your own staff? Because reading payer bulletins, mapping state override statutes, and building continuity packets is their entire day, not the thing they squeeze between refill requests. The people working your exceptions are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US prior authorization and specialty-pharmacy workflows. They know what a continuity-of-therapy exception has to say, which state law sets which deadline, and how to keep a stable patient stable through a plan-year change. That is not a generalist task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a formulary change never catches you short because the one person who handles exceptions is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented continuity-of-therapy workflow: which payers publish which bulletins when, which of your active patients each change touches, the exact continuity criteria each plan honors, the state override statute and its deadline, and the appeal path, all written down and worked the same way every plan year. Before we take a single exception for a new practice, we chart which of your patients are on drugs most exposed to formulary churn so we can watch the right bulletins, not a generic list.

From there the workflow becomes a living playbook rather than tribal knowledge in one nurse’s head. It records how each payer wants continuity of therapy documented, which state statute governs which plan, how to arrange a bridge supply when a switch is looming, and the escalation path when a stable patient hits a gap. It is written down, kept current as payers and formularies change, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a formulary change never lands on an unwatched panel.

That is the difference between fighting this plan year’s switches and fixing the process for good, and it is what a dedicated prior authorization partner actually buys you. A coordinator leaving used to mean the next formulary change caught a stable patient by surprise. Under this model the bulletins keep getting read, the playbook stays, the backup steps in, and a plan-year tier move stops being the thing that quietly costs you a controlled patient.

The Whole Thing in Four Sentences

Stable patients get forced back through step therapy because a formulary tier move driven by a rebate contract applies to existing patients unless continuity of therapy is negotiated, and many payers treat years of stability as insufficient without a fresh failure. Switching the patient, filing a bare exception, or reacting only after the pharmacy rejects the refill all fail the same way. The fix is to catch the bulletin before the change date, file a continuity-of-therapy exception with stability evidence built in, cite the state step-therapy override statute and its deadline, and work the appeal before any dose is missed. A rheumatology and specialty group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop losing stable patients to formulary churn? Try us risk free: two weeks, your real plan-year exception queue, dedicated specialists reading the bulletins and working the continuity exceptions, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From