Surescripts ePA vs CoverMyMeds: Operational Realities
Understanding the distinctions between Surescripts ePA and CoverMyMeds is critical for optimizing prior authorization workflows. This analysis focuses on their operational realities for health systems and specialty pharmacies.
Health systems navigate a complex prior authorization landscape, often relying on electronic prior authorization (ePA) networks to manage submission volume and reduce administrative burden. The choice between major ePA providers like Surescripts ePA and CoverMyMeds carries significant operational implications. Evaluating these platforms requires a detailed understanding of their differences in payer reach, EHR integration capabilities, and the resulting provider experience. This analysis focuses on the practical distinctions that impact daily operations for specialty pharmacy leads and EHR administrators.
Payer Network Coverage: Differentiating Access
Both Surescripts ePA and CoverMyMeds maintain extensive connections to health plans and pharmacy benefit managers (PBMs) across the United States. However, the specific payer penetration can vary, impacting a health system’s ability to submit all prior authorizations electronically through a single channel. Differences in network aggregation may mean one platform covers a specific regional payer or a particular PBM’s plan more comprehensively than the other. This fragmentation necessitates careful assessment of a health system’s dominant payer mix.
EHR Integration Footprint: Workflow Impact
The depth and method of EHR integration directly influence clinical and administrative workflows. Surescripts ePA typically integrates into major EHRs like Epic Hyperspace and Cerner PowerChart via direct API connections, facilitating a more embedded experience. This often allows for prior authorization initiation directly from the patient chart, pre-population of patient and clinical data, and status updates within the EHR interface. Such integration reduces context switching for clinicians and minimizes manual data entry errors.
Operational Workflow: Provider Experience
The day-to-day operational experience differs between the two platforms, impacting efficiency and staff satisfaction. CoverMyMeds often provides a web-based portal experience alongside EHR integrations, which can be beneficial for specific use cases or for health systems with less robust EHR integration capabilities. Surescripts ePA, by contrast, emphasizes a workflow that keeps the user within the EHR environment for most tasks. The choice affects how staff manage documentation attachments, respond to payer requests for additional information, and track authorization statuses.
Key Operational Workflow Differences
- **Initiation Point**: Directly from the EHR (Surescripts ePA emphasis) versus a combination of EHR and web portal (CoverMyMeds flexibility).
- **Data Population**: Extent of automated data transfer from the EHR, reducing manual input.
- **Documentation Handling**: Mechanisms for attaching clinical notes, lab results, and other supporting documents.
- **Status Updates**: How authorization statuses are communicated back to the provider and integrated into the EHR.
- **Payer Communication**: Facilitation of requests for additional information (RFIs) and peer-to-peer (P2P) review scheduling.
Data Exchange Standards and Compliance
Both ePA networks operate within the framework of HIPAA-mandated electronic transactions. The NCPDP SCRIPT standard is central to pharmacy prior authorizations, while the X12 278 transaction set governs medical prior authorizations. Health systems must ensure their chosen ePA partner adheres to these standards and supports emerging interoperability initiatives. The industry is moving towards greater standardization, exemplified by the Da Vinci Prior Authorization Support (PAS) Implementation Guide, which leverages FHIR to streamline data exchange. Discussing these technical compliance aspects with your internal IT and compliance teams is essential.
The Da Vinci Prior Authorization Support (PAS) Implementation Guide, built on FHIR, aims to standardize the exchange of prior authorization information, moving toward greater interoperability in the ePA landscape, impacting future integration strategies.
Specialty Pharmacy Considerations
Specialty medications often involve complex prior authorization criteria, including specific lab values, step therapy requirements, and detailed clinical documentation. For specialty pharmacies, the ability of an ePA platform to manage these nuances efficiently is paramount. This includes support for drug-specific forms, integration with benefit verification tools, and the capacity to handle expedited or urgent requests. The platform's ability to integrate with pharmacy management systems and provide clear visibility into the authorization lifecycle for these high-cost, high-touch medications is a critical differentiator.
Implementation and Maintenance Realities
Deploying and maintaining an ePA integration involves technical and administrative overhead. This includes initial setup, API configuration, user training, and ongoing support. Health systems should evaluate the vendor's support model, documentation quality, and the frequency of updates. Considerations also extend to how the ePA system handles payer rule changes, formulary updates, and changes in clinical criteria, such as those from MCG or InterQual. A robust integration requires minimal ongoing IT intervention and clear pathways for issue resolution.
Frequently asked questions
Which ePA platform offers better payer coverage for my specific health system's patient population?
Payer network coverage can vary regionally and by specific health plan. It is necessary to conduct a detailed analysis of your health system's top payers and their participation with each ePA network. Both Surescripts ePA and CoverMyMeds provide tools or documentation to help assess their respective payer reach.
How do Surescripts ePA and CoverMyMeds handle complex prior authorizations for specialty medications?
Both platforms are designed to process complex prior authorizations, including those for specialty medications. They support the submission of extensive clinical documentation, often facilitate drug-specific forms, and manage communication with payers regarding criteria like step therapy. The operational difference often lies in the user interface and workflow for attaching and tracking these specific requirements.
What are the technical requirements for integrating Surescripts ePA or CoverMyMeds with an Epic or Cerner EHR system?
Integration with Epic Hyperspace or Cerner PowerChart typically involves utilizing the EHR's native integration capabilities, often through APIs or specific modules. This requires coordination with your EHR vendor and the ePA provider. Technical teams will need to address data mapping, user authentication, and ensuring secure, compliant data exchange, often leveraging standards like SMART on FHIR.
Can both Surescripts ePA and CoverMyMeds be used simultaneously within a health system?
While technically possible, operating both ePA platforms simultaneously can introduce workflow complexities and increase administrative overhead. Most health systems aim for a consolidated solution to standardize processes and reduce staff training requirements. Strategic deployment often involves selecting the platform that best aligns with the majority of your payer mix and EHR integration strategy.
How do peer-to-peer (P2P) reviews function within these ePA networks?
Both Surescripts ePA and CoverMyMeds facilitate the P2P review process. This typically involves the ePA platform notifying the provider of a P2P opportunity, providing contact information for the payer's medical reviewer, and allowing the provider to schedule or conduct the review. The platforms aim to streamline the communication channel, though the P2P discussion itself occurs directly between the provider and payer.
What compliance considerations are relevant when choosing an ePA vendor?
Key compliance considerations include adherence to HIPAA regulations for PHI, secure data transmission protocols, and support for industry standards like NCPDP SCRIPT and X12 278. Health systems must also ensure the vendor's practices align with internal data governance policies. It is essential to engage your compliance and legal teams early in the selection process to review vendor agreements and data handling procedures.
Related coverage
Klivira automates prior authorization end-to-end.
See how it works for your EMR, payer mix, and specialty.