Navigating SCAN Health Plan Aimovig Prior Authorization

Understanding SCAN Health Plan's Formulary and Medical Policy for Aimovig

Aimovig (erenumab) is a calcitonin gene-related peptide (CGRP) inhibitor approved for the preventive treatment of migraine. As a specialty drug, it typically resides on a higher formulary tier and requires prior authorization from most payers, including SCAN Health Plan. RCM teams must consult SCAN Health Plan's current formulary and specific medical policy for CGRP inhibitors to identify the precise requirements. These documents detail which diagnoses are covered, what step therapy protocols are in place, and the clinical criteria that must be met for approval. Accessing the most current policy through the payer's provider portal or direct inquiry is a foundational step.

Core Clinical Criteria for Aimovig Authorization

SCAN Health Plan's medical policy for Aimovig will outline specific clinical criteria that must be met for a prior authorization request to be approved. These often include a confirmed diagnosis of episodic or chronic migraine, documented frequency of migraine attacks, and a history of failed trials with other preventive therapies. Common prior therapy requirements may involve adequate trials of oral prophylactic medications from different classes, such as beta-blockers, antidepressants, or anticonvulsants, or documentation of contraindications to these agents. The prescribing physician must clearly document the patient's medical history, prior treatment failures, and the rationale for initiating Aimovig in the clinical notes submitted with the PA request. Adherence to established criteria, which may reference guidelines like MCG or InterQual, is critical for a successful submission.

Prior Authorization Submission Pathways for SCAN Health Plan

Multiple avenues exist for submitting a prior authorization request to SCAN Health Plan. Electronic prior authorization (ePA) via solutions like CoverMyMeds or through a direct X12 278 transaction is often the most efficient method, reducing manual data entry and accelerating turnaround times. Many EHR systems, including Epic Hyperspace and Cerner PowerChart, now offer integrated ePA capabilities, often leveraging SMART on FHIR standards for data exchange. Alternatively, requests can be submitted via SCAN Health Plan's provider portal, fax, or phone. RCM teams should verify SCAN Health Plan's preferred submission method for specialty medications to optimize processing.

Required Documentation for Aimovig PA Submissions

• Completed SCAN Health Plan Prior Authorization Request Form (if not using ePA).
• Clinical notes supporting the migraine diagnosis (ICD-10 codes: G43.xx).
• Documentation of migraine frequency (e.g., migraine diary, physician attestation).
• Detailed history of prior preventive migraine treatments, including agent names, dosages, duration of trial, and reasons for failure (e.g., lack of efficacy, intolerable side effects).
• Documentation of contraindications to alternative therapies, if applicable.
• Prescribing physician's NPI, DEA, and contact information.

Common Denial Reasons and the Appeals Process

Prior authorization denials for Aimovig often stem from incomplete clinical documentation, failure to meet step therapy requirements, or insufficient evidence of medical necessity as defined by SCAN Health Plan's policy. Upon receiving a denial, RCM teams must immediately review the denial reason code and rationale. The appeals process typically begins with an internal appeal to SCAN Health Plan, requiring additional clinical information or clarification. If the internal appeal is unsuccessful, an external review may be pursued. For certain denials, a peer-to-peer (P2P) consultation with the prescribing physician and a SCAN Health Plan medical director can be an effective pathway to provide additional clinical context and potentially overturn a denial. Timely submission of appeals is critical, adhering to payer-specific deadlines.

Operationalizing Prior Authorization Efficiency

To mitigate PA-related delays and denials, RCM teams should implement structured workflows for specialty drug authorizations. This includes proactive identification of medications requiring PA, dedicated staff training on payer-specific requirements, and consistent communication with prescribing providers for necessary clinical documentation. Centralized PA teams or specialized coordinators can develop expertise in complex drug categories like CGRP inhibitors. Regular audits of PA processes can identify bottlenecks and areas for improvement. Establishing clear communication channels with patients regarding their authorization status and potential out-of-pocket costs is also crucial for patient satisfaction and adherence.

Technology's Role in Optimizing Aimovig PA Workflows

Integrating technology into the prior authorization workflow can significantly enhance efficiency and accuracy. Advanced PA platforms can automate data extraction from EHRs, populate ePA forms, and submit requests electronically via X12 278 or NCPDP SCRIPT. These systems can also track PA status, send automated reminders for renewals, and provide analytics on denial rates and turnaround times. EHR integrations, particularly those leveraging the Da Vinci PAS implementation guide, can embed PA initiation directly into clinical workflows within systems like Epic or Cerner. This reduces manual intervention, minimizes errors, and allows clinical staff to focus on patient care rather than administrative tasks. Platforms like Availity and CoverMyMeds serve as key intermediaries for electronic submissions to various payers, including SCAN Health Plan.

Compliance and Data Security Considerations

All prior authorization activities, whether manual or electronic, must adhere to HIPAA regulations regarding the protection of Protected Health Information (PHI) and Electronic Protected Health Information (ePHI). When transmitting clinical data for PA requests, ensure secure channels are utilized. Discuss with your compliance team how your organization's PA processes, especially those involving third-party vendors or integrated technologies, align with HIPAA Security and Privacy Rules. CMS-0057-F outlines interoperability requirements for payers, which will increasingly impact electronic PA processes, necessitating secure and standardized data exchange.