Automating Medicare Specialty Drug Prior Auth

Navigating the complexities of Medicare specialty drug prior auth requires precision, especially with the distinct requirements of Original Medicare and Part D plans. Klivira provides the automation needed to manage these high-value, often complex, authorizations efficiently.

For revenue cycle directors and prior authorization coordinators, specialty drugs represent a significant operational challenge due to their cost, clinical complexity, and varied benefit structures. When combined with Medicare's specific rules, from MAC-driven medical benefit PAs to commercial Part D pharmacy PAs, efficient processing is critical to patient access and revenue integrity.

Understanding Medicare's Prior Authorization Landscape for Specialty Drugs

Original Medicare (Fee-for-Service) has a limited scope for prior authorization, with certain services like Durable Medical Equipment (DME) and specific outpatient services requiring it. For specialty drugs, the key distinction lies between medical benefit (Part B, often provider-administered) and pharmacy benefit (Part D, patient-administered), each governed by different rules and submission channels.

The Dual Path: Medical vs. Pharmacy Benefit for Medicare Specialty Drugs

Specialty drugs under Medicare often split between medical (Part B) and pharmacy (Part D) benefits, impacting the prior authorization process. Medical benefit drugs, such as infused biologics, route through the responsible Medicare Administrative Contractor (MAC) like Noridian or Novitas. Pharmacy benefit drugs, typically self-administered, follow the specific Part D plan's formulary and PBM protocols, often utilizing ePA standards like NCPDP SCRIPT.

Key Challenges in Medicare Specialty Drug Prior Auth

  • Accurate benefit-side determination (Part B vs. Part D) per drug and patient context.
  • Navigating specific MAC jurisdiction requirements for medical benefit submissions.
  • Adhering to National Coverage Determinations (NCDs) and Local Coverage Determinations (LCDs) published by CMS and MACs.
  • Managing step-therapy protocols and site-of-care policies prevalent in Part D and some Part B scenarios.
  • Addressing the complexities of manufacturer copay assistance for Medicare patients due to anti-kickback statute concerns.

Klivira's Automated Approach to Medicare Specialty Drug PA

Klivira's platform automates the critical steps in Medicare specialty drug prior authorization. Our system intelligently determines the correct benefit side (medical or pharmacy) and routes submissions through the appropriate channel, whether it's a MAC-specific portal, X12 278 for medical benefit, or NCPDP SCRIPT ePA for Part D pharmacy benefit.

Streamlining Documentation and Policy Adherence

For medical benefit specialty drugs, Klivira ensures submissions align with NCDs and MAC-specific LCDs by integrating policy logic directly into the workflow. Our system reads FHIR MedicationRequest and Observation resources to automatically populate critical step-therapy and prior-line therapy documentation, reducing manual effort and common denial reasons.

Coordinated Fulfillment and Compliance Considerations

Beyond approval, Klivira coordinates the handoff to specialty pharmacies for Part D drugs, streamlining the time-to-medication. Our platform also flags potential issues with manufacturer copay assistance for Medicare patients, providing a critical alert for your team to discuss with your compliance department regarding anti-kickback statute considerations.

Frequently asked questions

How does Klivira handle the distinction between Original Medicare and Medicare Advantage plans for specialty drugs?

Klivira's platform identifies the specific payer context. For Original Medicare, we route medical benefit specialty drug PAs through the relevant MAC (e.g., Noridian, WPS) and pharmacy benefit PAs via Part D plan PBMs. For Medicare Advantage, which typically has broader PA requirements, we connect directly to the MA plan's specific medical and pharmacy PA channels.

What documentation is typically required for a Medicare specialty drug prior authorization?

Requirements vary by benefit type and drug. For medical benefit specialty drugs, submissions often require diagnosis codes, J-codes/HCPCS codes, prior-line therapy history, site-of-care information, and supporting clinical notes. Pharmacy benefit PAs (Part D) typically follow formulary and step-therapy protocols, often requiring similar clinical justification.

Does Klivira integrate with Medicare Administrative Contractors (MACs) for medical benefit specialty drug PAs?

Yes, Klivira's MAC-aware routing capability handles per-jurisdiction submission specifics for Original Medicare medical benefit prior authorizations. This includes routing to responsible MACs such as Palmetto, FCSO, and NGS, ensuring submissions reach the correct channel.

How does Klivira address site-of-care policies for Medicare medical benefit specialty drugs?

Klivira's policy engine incorporates site-of-care logic. For medical-benefit specialty drugs, our system includes site-of-care information aligned with the payer's policy in the PA submission. If a payer's policy requires an alternative site (e.g., infusion center instead of hospital outpatient), this is surfaced to the user before submission to prevent denials.

Can Klivira help with pharmacy benefit (Part D) specialty drug prior authorizations?

Yes, Klivira routes pharmacy-benefit specialty drug PAs through established ePA partners such as CoverMyMeds and Surescripts, utilizing the NCPDP SCRIPT ePA standard. This ensures efficient electronic submission to the relevant Part D plan's PBM for faster processing.

Related coverage

Other medicare prior auth coverage by specialty

Other medicare prior auth workflows

medicare integrations by EMR

Ready to automate this workflow with this payer?

See how Klivira automates prior authorizations for your team.

Request a demo