Formulary Access Data: What It Actually Tells You About a Prescriber | NPLUS Global

Formulary access data gets treated as a shortcut to understanding prescriber behavior — pull the tier status, infer the willingness to prescribe, move on. That shortcut breaks down fast once you look at what the data is actually measuring versus what teams assume it measures. Here's a more honest accounting of what formulary access signals tell you, and where they stop telling you anything at all.

1. It measures payer restriction, not physician preference. Formulary tier placement, prior authorization requirements, and step therapy edits are decisions made by PBMs and health plans, not by the prescriber. A physician showing up next to a "non-preferred, PA required" drug isn't expressing an opinion about that therapy — they're operating inside a constraint that exists regardless of what they'd choose in a vacuum. Conflating the two leads teams to misread compliance with a plan's rules as clinical hesitation.
2. "Access" isn't a single number — it varies by every plan in the prescriber's panel. The same drug can sit on three different tiers across the commercial, Medicare Advantage, and Medicaid managed care plans that make up one prescriber's patient population. A formulary lookup tied to a single payer tells you almost nothing about the prescriber's actual day-to-day friction unless you know the payer mix sitting behind their patient panel. This is the single most common analytical shortcut that produces misleading segmentation — treating national or median formulary status as if it applies uniformly.
3. Prior authorization friction is a proxy for staff capacity, not clinical conviction. A high PA burden reveals something real, but it's about the practice's administrative bandwidth — does it have staff who chase appeals, submit peer-to-peer reviews, and follow through on denials — more than it reveals about the physician's therapeutic intent. Solo practices and under-resourced clinics abandon PA-heavy prescriptions at a different rate than well-staffed specialty groups, independent of what either would prescribe if the drug were unrestricted.
4. Formulary status is a snapshot, and it goes stale faster than most data operations account for. Plan formularies shift at year-end renewals, and mid-year formulary changes for existing enrollees aren't rare, especially in Medicare Part D and Medicaid MCO contracts. Any formulary file more than a quarter old should be treated as a directional reference, not a current-state fact, and teams that refresh this data annually are often making decisions on conditions that no longer exist in the market.
5. Claims-adjudicated coverage and PBM-published formularies don't always agree. The formulary a plan publishes is the stated policy; what actually gets approved or rejected at the pharmacy counter is the adjudicated reality, and the two diverge more often than people expect — particularly around edits like quantity limits or diagnosis-based restrictions that don't show up cleanly in a published formulary grid. If you're only working from published formulary files, you're missing the exceptions, overrides, and plan-specific carve-outs that actually determine what happens in practice.
6. The real signal is in the gap between formulary status and observed prescribing. A prescriber who keeps writing a non-preferred, PA-required drug at a steady rate despite the friction is telling you something meaningful — about conviction, about patient population needs, or about a practice with enough staff to absorb the appeals process. That signal only exists when you pair formulary access data with actual prescribing or claims volume; the formulary file alone, without the behavioral overlay, is just a policy document.
7. Specialty and primary care prescribers experience the same restriction differently. A rheumatologist managing biologics deals with PA and step therapy as a routine part of the job, with staff and processes built around it; a primary care physician hitting the same restriction on a less common prescription may simply switch to whatever's preferred rather than fight it. Reading formulary friction the same way across specialties will systematically overstate resistance in some populations and understate it in others.
8. Regional and Medicaid MCO coverage in formulary data sets is frequently thinner than commercial and Part D data. State Medicaid managed care formularies change on different cycles, aren't always centrally published in a standardized format, and get deprioritized by data vendors because they're harder to source consistently. If a meaningful share of a prescriber's panel sits in Medicaid MCO plans, the formulary picture you're working from is likely more incomplete than it looks — a gap worth checking before treating an access score as authoritative. At NPLUS Global, this is one of the more common blind spots we flag when clients ask why formulary-based segments don't line up with what field teams are actually seeing.
9. Used alone, formulary access data is a poor targeting trigger — it's context, not a decision. The temptation is to score prescribers as "high opportunity" purely because a drug sits unrestricted on the plans covering their patients, but access without demand doesn't predict prescribing, and restriction without patient need doesn't predict resistance. Formulary data earns its keep when it's layered against actual prescribing patterns, specialty norms, and payer mix — on its own, it answers a policy question, not a behavioral one.

The underlying discipline here isn't complicated, but it's easy to skip under deadline pressure: formulary access data describes the rules a prescriber is operating under, not the choices they're making within them. Teams that keep that distinction explicit — rather than letting "formulary status" quietly become shorthand for "physician attitude" — end up with segmentation that survives contact with the field, instead of models that look clean in a dashboard and fall apart the first time a rep compares them to what they're actually hearing in the office.