Automating MEDITECH Ajovy Prior Authorization: A Klivira Integration Guide

Navigating MEDITECH Ajovy prior authorization can be a significant operational challenge for health systems. Klivira streamlines this complex process, integrating directly with your MEDITECH environment to accelerate approvals and reduce manual effort.

For revenue cycle directors and prior authorization coordinators, managing high-volume drug PAs like Ajovy within MEDITECH presents unique complexities. The variability across MEDITECH product lines, from Expanse to legacy systems, necessitates a precise approach to data extraction and workflow automation. Klivira addresses these challenges by providing a tailored integration solution.

MEDITECH Integration for Ajovy PA Workflows

Klivira integrates with MEDITECH's diverse product lines to support Ajovy prior authorizations. For MEDITECH Expanse, we leverage modern APIs, including FHIR R4 and SMART App Launch capabilities, to securely access patient data. For legacy MEDITECH environments (Magic, C/S, 6.x), our solutions incorporate HL7 v2 interfaces to ensure comprehensive data exchange and workflow continuity, adapting to the specific integration surface available.

Ajovy Order Entry and ePA Triggering in MEDITECH

When a clinician places an order for Ajovy within MEDITECH's 'Orders activity' module, Klivira's integration can detect this event and initiate the prior authorization workflow. This includes identifying the prescribed medication, patient context, and relevant ordering provider. Our system is designed to facilitate the transition from order entry to an electronic prior authorization (ePA) submission, routing to appropriate specialty pharmacies as needed.

Documenting Ajovy Medical Necessity in MEDITECH

**Clinical Notes:** Klivira extracts relevant clinical documentation from MEDITECH's 'Documentation' modules, including progress notes, physician orders, and specialty consultations, to support medical necessity criteria for Ajovy.
**Patient Summary/Storyboard:** Key patient demographics, problem lists, and historical treatment data are pulled from the 'Patient Summary' or 'Storyboard' for a comprehensive view.
**Diagnostic Results:** Relevant lab results or imaging studies from MEDITECH are included to substantiate the diagnosis and treatment plan.
**Medication History:** Prior medication trials and failures, crucial for Ajovy PA, are extracted from the patient's medication history within MEDITECH.

Navigating Ajovy's Benefit Structure within MEDITECH

While Ajovy is primarily covered under the pharmacy benefit for self-administration, its prescription and related services interact with both pharmacy and medical benefit structures. Klivira's integration with MEDITECH accounts for this distinction, ensuring that all necessary clinical data is extracted and aligned with the correct benefit channel for accurate prior authorization submission, whether it's an NCPDP SCRIPT ePA or an X12 278 medical benefit request.

Write-Back and Status Updates for Ajovy PAs

Klivira's platform is engineered to write prior authorization status updates back into the MEDITECH chart, enhancing visibility for clinicians and administrative staff. For MEDITECH Expanse, this typically involves utilizing FHIR-based write capabilities for resources such as DocumentReference (for PA packets), Communication (for status updates), or Task (for workflow items), subject to customer-specific verification. This ensures that the 'Surveillance / Worklists' and 'Communication / Messaging' modules reflect the latest PA status.

Frequently asked questions

Does Klivira integrate with all MEDITECH product lines for Ajovy PA?

Klivira supports integration across MEDITECH product lines, including MEDITECH Expanse and legacy systems like Magic, C/S, and 6.x. Our approach adapts to the specific integration surfaces available at each customer site, leveraging modern FHIR APIs for Expanse and traditional HL7 v2 interfaces for older deployments to ensure comprehensive coverage for Ajovy prior authorizations.

How does Klivira handle documentation for Ajovy prior authorizations in MEDITECH?

Klivira extracts critical documentation directly from MEDITECH, including clinical notes, problem lists, medication histories, and diagnostic results. This data is pulled from relevant chart sections like the 'Patient Summary,' 'Documentation' modules, and 'Orders activity' to build a robust prior authorization packet that substantiates medical necessity for Ajovy.

Can Klivira help with Ajovy PAs that involve both pharmacy and medical benefits?

Yes, Klivira's integration is designed to manage the complexities of Ajovy prior authorizations that may span both pharmacy and medical benefits. We ensure that all necessary clinical context from MEDITECH is gathered and correctly formatted for submission via appropriate channels, whether it's an ePA for pharmacy benefit or a medical benefit authorization request.

What data does Klivira pull from MEDITECH for Ajovy prior authorizations?

Klivira pulls a comprehensive set of data from MEDITECH for Ajovy PAs, including patient demographics, diagnosis codes, problem lists, medication history (including prior therapies and failures), relevant clinical notes, and supporting diagnostic results. This data is critical for meeting payer-specific medical necessity criteria.

How does Klivira update MEDITECH with Ajovy PA status?

Klivira can write prior authorization status updates directly back into the MEDITECH system. For Expanse, this typically involves using FHIR write capabilities to update relevant patient records, allowing PA coordinators and clinicians to see the real-time status of Ajovy authorizations within their existing MEDITECH workflows and 'Surveillance / Worklists'.