The market for specialty pharmacy PA automation has expanded significantly over the past few years. There are now enough vendors with credible offerings that evaluating them carefully is genuinely useful work — not a formality before selecting the one you'd already decided on, but a process that can meaningfully differentiate solutions whose surface pitches sound similar.
The challenge is that the vendor evaluation conversations tend to stay at the level of features and demo screens. The questions that actually separate adequate implementations from strong ones don't always make it into those conversations. Here are seven questions that should.
Question 1: What Percentage of Our Actual Payer Mix Does Your System Cover for Direct Submission?
The first question isn't about technology — it's about coverage fit. A PA automation platform that covers 85% of major national commercial plans is useful, but if 30% of your script volume runs through Medicaid managed care organizations or regional Blue plans with proprietary portals, the remaining 15% of your payer mix could represent a disproportionate share of your problem cases.
Ask the vendor to map their current payer connectivity against your actual payer mix — not a generic list, but your specific payer ID distribution. For payers not directly connected, ask what the fallback workflow is: manual staff routing, fax, or a hybrid? The answer tells you what residual staff workload looks like after implementation.
Question 2: How Does Your System Handle PA Submissions Where the Payer Doesn't Have Electronic Infrastructure?
Electronic prior authorization infrastructure is uneven. Some payers support structured HL7 FHIR-based PA transactions; others use CoverMyMeds or Surescripts-connected ePA workflows; others still require direct portal submission or fax. A vendor who tells you "we handle all payers electronically" is either overstating their coverage or using "electronically" in a way that includes browser-automation portal-scraping — a technically valid approach but one that breaks whenever the payer updates their portal UI.
Ask specifically how submissions are routed to payers who don't have a structured API or ePA connection. The honest answer from any vendor will involve some combination of portal automation, integrated fax, and manual exception handling — and you want to know the relative proportions before you sign.
Question 3: What Does Your Business Associate Agreement Cover, and What Are the Permitted Uses of Our Patient Data?
This question should come early in the conversation, not at the end after the operational questions are settled. Any PA automation vendor is a business associate under HIPAA. The BAA they offer should specify, at minimum: permitted uses of PHI, safeguard requirements, breach notification obligations, subcontractor accountability, and PHI return or destruction at termination.
Pay particular attention to the permitted uses clause. Some vendors include language permitting them to use de-identified or aggregated patient data for product improvement, benchmarking services, or analytics products. Depending on the de-identification standard applied (Safe Harbor vs. Expert Determination under 45 CFR 164.514), this may or may not raise concerns for your compliance team — but you should know it's there before signing.
We're not saying data usage for product improvement is inherently problematic — aggregated, properly de-identified data can improve the product for everyone. We're saying you should know what you're agreeing to before you agree to it, and your HIPAA compliance officer should review the BAA, not just the sales team.
Question 4: How Does Your System Integrate with Our Pharmacy Management System, and What Is the Integration Architecture?
The operational value of PA automation depends heavily on how cleanly the vendor integrates with your pharmacy management system. For the three most common specialty pharmacy platforms — Rx30, PioneerRx, and QS/1 — integration architectures vary: some vendors use native API connections where available, some use HL7 v2 interface engines, some use database-level integrations, and some use screen-scraping agents that read from the PMS UI.
The integration method matters for data fidelity, update frequency, and what happens when the PMS is updated. A HL7 v2 interface that's been implemented against a specific PMS version may require updates when the PMS releases a new version. A screen-scraping integration is inherently fragile. Ask for specifics on the integration method, the update maintenance process, and the SLA for integration fixes when a PMS update breaks the connection.
Question 5: What Is Your Average First-Pass Submission Accuracy Rate, and How Do You Define It?
Most PA automation vendors will cite a submission accuracy or first-pass approval rate. Before interpreting this number, understand the denominator: is it the percentage of submissions that go through without payer rejection due to missing or incorrect data? Is it the percentage that receive payer approval on the first submission (which conflates submission quality with payer coverage policy decisions)? Is it measured across all payer types or only hub-connected payers?
A submission accuracy rate that looks strong may be calculated only for the subset of payers where the vendor has the strongest connectivity, with the harder cases excluded. Ask for the rate broken down by payer type and submission method, and ask how they handle submission errors — who is notified, what is the correction process, and how quickly are resubmissions processed.
Question 6: What Does Onboarding Look Like, and What Is the Realistic Time-to-Value?
Implementation timelines for PA automation vary widely based on the PMS integration complexity, the pharmacy's payer mix complexity, and the vendor's onboarding process maturity. A vendor who promises two-week onboarding for a pharmacy with a complex Medicaid population and a legacy PMS integration is likely underselling the implementation effort. A vendor who quotes 12 weeks for a straightforward commercial-payer-heavy pharmacy with a standard PMS may be overselling it.
Ask for a detailed onboarding plan with milestones, and ask to speak with a reference customer who has a similar PMS and payer mix to understand their actual implementation timeline. Importantly, ask what happens to your PA workflow during the transition period: is there a parallel-run phase where both manual and automated submissions run, and how long does that typically last?
Question 7: What Is Your Approach to Appeal Support, and How Does It Work in Practice?
PA automation platforms vary significantly in how much support they provide beyond initial submission. Some platforms stop at submission and status tracking; others offer appeal workflow support; a smaller number include tools for generating appeal letters, assembling supporting documentation, or identifying which denial reason codes warrant appeal based on historical approval rates.
Ask specifically: when a PA comes back denied, what does your system do? Does it categorize the denial by reason code? Does it suggest whether the denial is administratively reversible or requires clinical documentation? Does it provide any appeal letter templates or prior documentation assembly? The appeal support capability is often the feature that differentiates a good platform from a great one — because first-pass denials are unavoidable, and what happens next determines whether that denial becomes a reversal or a lost script.
A Note on the Evaluation Process Itself
The seven questions above are starting points, not the complete evaluation. A useful vendor evaluation for PA automation also includes a live demo using scripts representative of your actual complexity (not curated demo cases), a reference check with pharmacies of comparable size and payer mix, and a technical review by whoever manages your PMS integration — typically your IT lead or PMS administrator.
The goal is to understand not just what the platform can do in its best case, but how it performs across the full distribution of your script complexity, including the payer types and drug categories where your current workflow is most painful. The vendors who can answer that version of the evaluation clearly tend to be the ones worth working with.
