Streamlining Centricity Zepbound Prior Authorization Workflows

Klivira automates Centricity Zepbound prior authorization workflows, integrating directly with your EMR to reduce manual burden and accelerate patient access to critical GIP/GLP-1 therapies.

For revenue cycle directors and prior authorization coordinators, managing the increasing volume and complexity of Zepbound (tirzepatide) prior authorizations within a Centricity EMR environment presents significant operational challenges. Klivira's platform is engineered to address these specific bottlenecks, ensuring efficient, evidence-grounded submissions.

Navigating Zepbound Prior Authorizations within Centricity

Zepbound, a GIP/GLP-1 dual agonist indicated for chronic weight management, frequently requires prior authorization due to its cost and specific coverage criteria. Within Centricity, the PA process for Zepbound typically initiates at the point of order entry, requiring diligent documentation and often complex routing to specialty pharmacies. Klivira integrates directly with Centricity, leveraging Athena APIs, to embed automation seamlessly into this existing workflow.

Centricity's Role in Zepbound Order Entry and ePA Integration

As a legacy EMR now under athenahealth, Centricity's architecture handles prescription orders for Zepbound. Klivira's integration surfaces directly with Athena APIs, allowing for automated identification of Zepbound orders requiring prior authorization. This facilitates the initiation of an electronic prior authorization (ePA) request, often leveraging X12 278 or NCPDP SCRIPT standards, without requiring staff to navigate away from the Centricity interface.

Distinguishing Pharmacy vs. Medical Benefit for Zepbound in Centricity

For GIP/GLP-1 medications like Zepbound, understanding the payer's distinction between pharmacy and medical benefit is critical. While Zepbound itself is a pharmacy benefit drug, associated diagnostic services or administration (if applicable) may fall under medical benefit. Klivira's platform assists in identifying the correct benefit pathway based on payer rules and patient eligibility data pulled from Centricity, ensuring accurate submission and reducing claim denials related to incorrect benefit classification.

Automating Documentation Retrieval from Centricity for Zepbound PAs

Successful Zepbound prior authorizations hinge on comprehensive clinical documentation. Klivira's intelligent automation pulls relevant data points directly from Centricity's structured fields and clinical notes. This includes extracting information from the problem list (e.g., obesity, related comorbidities), medication history (e.g., failed weight loss attempts with other agents), and vitals (e.g., BMI measurements, weight history) to construct a robust PA submission packet.

Key Documentation Points for Zepbound Prior Authorization

  • Patient's Body Mass Index (BMI) and weight history.
  • Presence of weight-related comorbidities (e.g., hypertension, dyslipidemia, obstructive sleep apnea, prediabetes).
  • Documentation of previous dietary and lifestyle interventions.
  • History of other weight loss medications attempted and failed, or contraindications to other therapies.
  • Clinical notes supporting the diagnosis of chronic weight management.
  • Labs, including A1C if applicable for related conditions.

Facilitating Specialty Pharmacy Routing for Zepbound

Zepbound is typically dispensed through specialty pharmacies. Klivira's integration with Centricity streamlines the routing of approved Zepbound prescriptions to the designated specialty pharmacy. This ensures that once prior authorization is secured, the prescription moves efficiently through the fulfillment process, minimizing delays in patient access to therapy. Our system helps manage the handoff, reducing manual interventions and potential errors.

Frequently asked questions

How does Klivira integrate with Centricity for Zepbound PAs?

Klivira integrates with Centricity primarily through Athena APIs, allowing for direct data exchange. This enables automated identification of Zepbound orders, extraction of necessary clinical documentation from patient charts, and submission of ePA requests without requiring manual data entry into separate portals.

Can Klivira help distinguish between pharmacy and medical benefit for Zepbound in Centricity?

Yes, Klivira's platform is designed to assist in navigating the complexities of pharmacy versus medical benefit for specialty medications like Zepbound. By analyzing payer rules and patient eligibility data available through Centricity, our system helps ensure PA requests are routed and submitted under the correct benefit, reducing denials.

What kind of documentation does Klivira pull from Centricity for Zepbound prior authorizations?

Klivira intelligently extracts critical documentation from Centricity, including data from problem lists (e.g., obesity, comorbidities), medication histories (e.g., prior weight loss attempts), and vitals (e.g., BMI, weight trends). This comprehensive data is compiled to meet payer-specific criteria for Zepbound authorization.

Does Klivira support specialty pharmacy routing for Zepbound prescriptions originating in Centricity?

Absolutely. Once a Zepbound prior authorization is approved, Klivira supports the seamless electronic routing of the prescription to the patient's designated specialty pharmacy. This integration minimizes manual steps, reduces potential for errors, and accelerates the time to therapy for patients.

Is Klivira compatible with Centricity's current operational model under athenahealth?

Yes, Klivira's integration strategy is specifically designed to be compatible with Centricity's current operational model, leveraging the Athena APIs. This ensures robust and reliable connectivity for prior authorization automation, even for legacy Centricity installs.

Related coverage

Other centricity prior auth coverage

Ready to automate prior auth for this integration?

See how Klivira automates prior authorizations for your team.

Request a demo