Centricity Medicaid Prior Authorization Automation: Navigating State-Specific Workflows

Klivira delivers comprehensive **Centricity Medicaid prior authorization automation**, streamlining complex, state-specific workflows directly from your EMR.

For organizations leveraging Centricity, managing Medicaid prior authorizations presents unique challenges due to diverse state regulations and varying payer models. This complexity often leads to significant administrative burden, delayed patient care, and impacts revenue cycle efficiency.

The Challenge of Medicaid PA within Centricity Workflows

Centricity users frequently encounter a fragmented landscape for Medicaid prior authorizations. Submissions often require navigating distinct state Medicaid portals for Fee-for-Service (FFS) plans or individual MCO provider portals for managed care, diverging from a unified EMR workflow. This manual effort impacts staff productivity and can delay access to care.

Deconstructing Medicaid Prior Authorization Complexity

Medicaid's dual structure of Fee-for-Service (FFS) and Managed Care Organizations (MCOs) creates a highly variable prior authorization environment. Each state defines its own medical necessity criteria, and MCOs like Centene subsidiaries, Molina, UHC Community Plan, or Anthem Medicaid plans administer benefits with specific portal requirements, all while adhering to state-defined criteria as a floor.

Key Service Categories Requiring Medicaid Prior Authorization

Inpatient admissions and continued-stay reviews
Advanced imaging and specialty drugs
Durable Medical Equipment (DME) and behavioral health services
Therapy services (PT, OT, speech)
Non-emergency medical transportation (NEMT) in many states

Klivira's Seamless Integration with Centricity via Athena APIs

Klivira integrates directly with Centricity, leveraging the underlying Athena APIs. This robust connection enables the secure, bidirectional exchange of clinical documentation and patient demographic data, eliminating duplicate data entry and ensuring that prior authorization requests are initiated with complete and accurate information directly from the EMR.

Automating Medicaid PA Across Diverse Channels

Klivira intelligently routes Medicaid prior authorization requests based on the specific delivery model and payer. For FFS plans, requests are directed to the state Medicaid agency's fiscal agent or portal. For managed care, Klivira connects to the responsible MCO's provider portal or utilizes X12 278 routing where supported, ensuring comprehensive coverage across all operational channels.

Navigating CMS-0057-F and Medicaid MCO Interoperability

Medicaid managed-care organizations are directly impacted payers under CMS-0057-F, which mandates FHIR-based Prior Authorization APIs and specific decision timeframes. Klivira helps Centricity users align with these evolving interoperability requirements, facilitating compliance and leveraging new digital pathways for faster prior authorization processing with MCOs.

Frequently asked questions

How does Klivira handle the state-by-state variation in Medicaid PA rules?

Klivira's platform identifies the specific state and delivery model (FFS or MCO) for each Medicaid member. It then applies the relevant state Medicaid agency rules and MCO-specific criteria, ensuring requests meet local medical necessity requirements.

Can Klivira integrate with Centricity for both FFS and MCO Medicaid plans?

Yes, Klivira's integration with Centricity via Athena APIs supports routing for both FFS Medicaid plans, typically via state portals or fiscal agents, and managed care plans, through MCO provider portals or X12 278 where available.

What specific data is pulled from Centricity for Medicaid PA requests?

Klivira pulls essential patient demographics, clinical notes, procedure codes, and diagnostic information from Centricity via Athena APIs. This data populates prior authorization requests, reducing manual data entry and improving submission accuracy.

How does Klivira address dual-eligible Medicare and Medicaid patients?

For dual-eligible Medicare and Medicaid members, Klivira coordinates D-SNP (Dual Special Needs Plan) requirements. The platform considers both Medicare and Medicaid coverage rules to ensure accurate and complete prior authorization submissions, minimizing potential denials.

Does Klivira support X12 278 submissions for Medicaid?

Yes, Klivira supports X12 278 routing for Medicaid prior authorizations where the specific state Medicaid agency or managed care organization has implemented and supports this electronic data interchange channel for PA submissions.