Streamlining OpenEMR Aetna Prior Authorization Automation

For organizations leveraging OpenEMR, achieving efficient OpenEMR Aetna prior authorization automation is critical to maintaining revenue integrity and patient access. Klivira connects OpenEMR to Aetna's complex PA ecosystem, simplifying submissions.

Revenue cycle directors and prior authorization coordinators at FQHCs and global health organizations using OpenEMR face unique challenges when processing Aetna prior authorizations. The manual navigation of Aetna's varied submission channels, coupled with the need to extract specific clinical data from an open-source EHR, often leads to delays and administrative burden. Klivira addresses these complexities by integrating directly with OpenEMR to automate Aetna PA workflows.

Navigating Aetna's Diverse Prior Authorization Channels from OpenEMR

Aetna utilizes multiple distinct channels for prior authorization submissions depending on benefit category and service type. Medical benefit precertification requests, encompassing commercial and Medicare Advantage lines, are primarily routed through the Availity provider portal or accepted via X12 278 transactions through clearinghouses. For pharmacy benefit PA, administered by CVS Caremark, submissions route through ePA partners like CoverMyMeds or Surescripts. Klivira's platform is engineered to connect OpenEMR data to these specific Aetna channels, eliminating the need for manual portal entry or faxing.

Klivira's Integration Approach for OpenEMR and Aetna PA

  • Leveraging OpenEMR's FHIR R4 and REST API capabilities for secure, structured clinical data exchange.
  • Automating medical benefit PA submissions to Aetna via the Availity portal and direct X12 278 transactions.
  • Streamlining pharmacy benefit PA through established ePA partners such as CoverMyMeds and Surescripts, connecting directly with CVS Caremark.
  • Facilitating real-time status updates and communications to be pushed back into OpenEMR workflows, enhancing visibility.
  • Supporting the distinct requirements for specialty drug PA, which may involve dedicated management workflows.

Operationalizing Aetna Clinical Policy Bulletins (CPBs) within OpenEMR Workflows

Aetna's medical necessity criteria are published as Clinical Policy Bulletins (CPBs) in their public library. These CPBs are critical for understanding documentation requirements, step-therapy protocols, and site-of-service rules. Klivira integrates this policy intelligence, guiding OpenEMR users to gather the precise clinical documentation required by specific Aetna CPBs for procedures like advanced imaging, specialty biologics, or bariatric surgery, ensuring submissions align with payer expectations upfront.

Turnaround Time Compliance and CMS-0057-F Considerations for Aetna

Aetna's prior authorization turnaround times are influenced by state-mandated minimums, payer-published targets, and NCQA Utilization Management accreditation standards. For Aetna's Medicare Advantage, Medicaid managed-care (Aetna Better Health), and QHP-on-FFM lines of business, CMS-0057-F introduces new requirements for electronic PA API conformance and decision timeframes (e.g., 72 hours for standard, 24 hours for expedited). Klivira's automation helps OpenEMR users meet these varied and often tight deadlines, improving compliance and patient care continuity.

Enhancing Documentation for Aetna's Common Denial Reasons

Common Aetna medical PA denial categories include insufficient documentation for medical necessity, failure to meet step-therapy requirements, site-of-service mismatches, and off-label use without compendium support. By integrating with OpenEMR's clinical data, Klivira helps proactively identify and gather the necessary information before submission. This approach aims to reduce denials, which are communicated via X12 835/277 transactions or Availity portal updates using CARC and RARC codes, thereby improving financial outcomes for OpenEMR-enabled practices.

Frequently asked questions

How does Klivira integrate with OpenEMR for Aetna prior authorizations?

Klivira integrates with OpenEMR by leveraging its FHIR R4 and REST API capabilities to extract relevant patient demographics, clinical history, and proposed treatment plans. This data is then used to populate and submit prior authorization requests to Aetna's various channels, including Availity, X12 278, CoverMyMeds, and Surescripts, automating the manual data entry process.

Which Aetna prior authorization channels does Klivira support for OpenEMR users?

Klivira supports Aetna's primary prior authorization channels for OpenEMR users. This includes medical benefit submissions via the Availity provider portal and X12 278 transactions, as well as pharmacy benefit ePA submissions through partners like CoverMyMeds and Surescripts, which connect to CVS Caremark. This comprehensive coverage ensures all major Aetna PA types are addressed.

Can Klivira help OpenEMR users comply with Aetna's Clinical Policy Bulletins?

Yes, Klivira assists OpenEMR users in complying with Aetna's Clinical Policy Bulletins (CPBs). By referencing Aetna's publicly available CPB library, Klivira's platform guides the collection of specific clinical documentation and adherence to medical necessity criteria, step-therapy protocols, and other requirements outlined in relevant CPBs, directly from within the OpenEMR workflow.

What Aetna lines of business are covered by Klivira's OpenEMR integration?

Klivira's OpenEMR integration covers Aetna's diverse lines of business, including commercial, Medicare Advantage, and Medicaid managed-care plans (Aetna Better Health). We account for the differing prior authorization rules, submission channels, and turnaround time requirements applicable to each line, including those impacted by federal mandates like CMS-0057-F for specific government-sponsored plans.

How does Klivira handle Aetna's pharmacy benefit vs. medical benefit PA for OpenEMR?

Klivira intelligently differentiates between Aetna's pharmacy benefit (CVS Caremark) and medical benefit prior authorizations. Pharmacy benefit requests are routed through ePA partners like CoverMyMeds and Surescripts, while medical benefit requests are submitted via Availity or X12 278. This ensures that OpenEMR users' requests are directed to the correct Aetna channel based on the specific service or medication, including specialty drugs that may fall under either benefit.

Related coverage

Other openemr prior auth coverage

Other EMR integrations for aetna

Ready to automate prior auth for this integration?

See how Klivira automates prior authorizations for your team.

Request a demo