Prior authorizations for compounded medications are a special kind of operational pain. The formulation is often non-standard, the payer's system doesn't recognize the NDC, the reviewer has never heard of the base ingredient, and your patient is calling on day nine asking why their cream still hasn't shipped. If you run a practice that prescribes compounds regularly, you already know that a "normal" PA playbook doesn't quite fit. This one is written for you.

What follows is what we've seen work across concierge and compounding-adjacent practices. Adapt it to your specialty, your payer mix, and your pharmacy partners. Nothing here is legal advice; confirm plan-specific rules with your billing counsel and your PBM contacts.

Why compounded-medication PAs fail more often

Standard PAs fail for boring reasons: missing chart notes, wrong diagnosis code, no step-therapy documentation. Compounds fail for those reasons plus a stack of others that are specific to how these prescriptions travel through the system.

  • The compounded product has no billable NDC, so the claim runs against a placeholder or an ingredient-level code the plan doesn't recognize.
  • The plan treats compounds as excluded by default unless a specific medical-necessity pathway is invoked.
  • The PBM's clinical reviewer is comparing the formulation to a commercially available product and asking why the patient can't just take that.
  • Ingredients are billed separately, and one ingredient (often a bulk chemical or a flavoring agent) triggers a rejection that tanks the whole claim.
  • The pharmacy and the prescriber are working from different versions of the formula, so the PA form and the dispensing record don't match.

If you fix only the prescriber-side documentation, you'll still lose half the battle at the pharmacy counter. The playbook has to cover both sides of the fence.

Step 1: Segment your compound prescriptions by PA risk

Not every compound needs the same workflow. In practice, we sort them into three buckets:

  • Cash-pay only. Patient is paying the pharmacy directly, no insurance touch. PA isn't the issue; clear pricing communication is.
  • Insurance-eligible with a clear precedent. HRT creams, LDN, specific dermatology bases. Your pharmacy partners have submitted these hundreds of times and know which plans approve and which don't.
  • High-risk / novel formulations. Peptides, unusual delivery vehicles, ingredients that show up on PBM exclusion lists. These need medical-necessity letters, and often an appeal from day one.

Every compound your practice prescribes should be tagged in your EMR with one of these categories. If your system can't hold that tag, add it to the medication favorite or order set. The tag drives which downstream workflow fires.

Step 2: Build the documentation packet before you need it

The single biggest time sink we see is scrambling for chart material after a PA is denied. By the time you're on day seven, your MA is digging through eight months of notes to find the failed trial of the commercial equivalent, and the clock is running.

Do the work up front. For each high-risk compound, build a standing documentation template that includes:

  • Diagnosis with ICD-10, plus a one-sentence clinical rationale that ties the compound to that diagnosis.
  • List of commercially available alternatives the patient has tried, failed, or cannot tolerate, with dates and outcomes.
  • Specific reason the compounded formulation is required (dose not commercially available, allergy to excipient, delivery route, etc.).
  • Reference to any peer-reviewed literature or clinical guideline supporting the use, if one exists.
  • Prescriber attestation of medical necessity, signed and dated.

Store the template in the EMR so the clinician can populate it during the visit, not three days later when the pharmacy calls. If your system supports AI-assisted note structuring, this is a good place to use it: the clinician talks through their reasoning, and the structured fields populate for the PA packet.

Step 3: Get the pharmacy on the phone before the script goes out

This one is unglamorous and it works. For any prescription in the high-risk bucket, a member of your team (usually the clinical coordinator) calls the pharmacy before transmission to confirm:

  • The exact formulation the pharmacy will compound, ingredient by ingredient.
  • Whether the pharmacy has billed this formula to this patient's plan before, and what happened.
  • Which ingredient, if any, is likely to trigger a rejection.
  • Whether the pharmacy will submit the PA or expects the prescriber's office to.

That last question causes more delays than any other single issue. Both sides assume the other is handling it. Five days later, nobody has submitted anything. Decide, document who owns it, and put the owner in the chart.

Step 4: Standardize the appeal, because you will appeal

Assume denial on first submission for anything in the high-risk bucket. Build your appeal template now, not after the denial letter arrives. A good appeal packet includes the original PA documentation, the denial letter, a point-by-point response to the reviewer's stated reason for denial, and a peer-to-peer request if the plan allows one.

The peer-to-peer is often the fastest path to approval on compounds because you're finally talking to a clinician who can hear the reasoning. Block 30 minutes on the prescriber's calendar every week specifically for peer-to-peers. Practices that treat these as ad-hoc interruptions never get to them, and the PAs age out.

Step 5: Track your data, or you're guessing

You cannot improve what you don't measure. At minimum, track by payer and by compound:

  • Time from prescription to PA submission.
  • Time from submission to decision.
  • First-pass approval rate.
  • Appeal approval rate.
  • Time from decision to pharmacy dispensing.

Within three months of tracking, patterns emerge. You'll find that one payer approves your progesterone cream 90% of the time on first pass and another denies it every time, requiring a peer-to-peer. That knowledge changes how you counsel patients at the visit, how you set expectations, and whether you route certain prescriptions to a cash-pay pharmacy from the start.

Step 6: Communicate with the patient like an adult

Patients don't care about PBM logic. They care that they were promised a medication and it hasn't arrived. Every high-risk compound prescription should trigger a patient message at the point of prescribing that explains, in plain language, that insurance may require additional review, roughly how long that takes, and what the cash-pay option costs if they'd rather skip the wait.

Practices that do this see a sharp drop in inbound "where is my prescription" calls, which frees your front desk to actually work the PAs instead of answering the phone about them.

Where automation actually helps

Most PA "automation" tools were built for commercial drugs and fall over on compounds. The pieces that do translate well are the ones that reduce administrative friction: pulling the right chart elements into a PA packet, tracking submission and response times, routing denials to the right person on your team, and sending patient status updates without a human having to type them. If you're rebuilding your compound workflow and want to see how purpose-built infrastructure handles this, talk to our team at Qintara. We built this because we watched practices lose good patients to a two-week refill delay that nobody owned.

Frequently Asked Questions

How long should a compound PA reasonably take?

For a formulation your pharmacy has billed before to a payer that recognizes it, 24 to 72 hours is realistic. For novel formulations or plans that require appeal, plan on 10 to 21 days. Anything longer usually means something is stuck between the pharmacy and the prescriber's office, not with the payer.

Should the prescriber's office or the pharmacy submit the PA?

Whichever party has better documentation and a faster turnaround for that specific payer. The point is to decide explicitly on a per-prescription basis and document the owner. Most delays we see come from ambiguity here.

Is it worth pursuing PAs on compounds at all, versus going cash-pay?

It depends on your patient population and your pharmacy relationships. For concierge practices with cash-comfortable patients, aggressive PA work often costs more in staff time than it returns. For practices serving patients who genuinely can't afford the cash price, the PA is the difference between treatment and no treatment. Segment your patient base and set policy accordingly.

What documentation do payers most often ask for on compound PAs?

Evidence of failed trials on commercial alternatives, a specific clinical reason the compound is required (dose, allergy, route), and a prescriber attestation of medical necessity. Build these into your note template so they're captured at the visit rather than reconstructed later.

How do we handle a patient whose PA is denied on appeal?

Have a defined off-ramp: a scripted conversation, a cash-pay quote from the pharmacy ready to send, and a documented clinical decision about whether to switch to a commercial alternative. Patients tolerate bad news; they don't tolerate silence.