Achieving Highmark CMS-0057-F Compliance for Prior Authorization

Navigating **Highmark CMS-0057-F compliance** requires a strategic approach to prior authorization workflows, especially for impacted Medicare Advantage and Medicaid plans. Klivira streamlines this process, ensuring your submissions meet regulatory standards and accelerate decision-making.

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) introduces significant changes for payers like Highmark and the providers who serve their members. For revenue cycle directors and prior authorization coordinators, understanding and adapting to these new requirements, particularly around API integration and decision timeframes, is critical for operational efficiency and claim reimbursement.

Understanding Highmark's Role in CMS-0057-F Compliance

As a major Blue Cross Blue Shield plan serving Pennsylvania, West Virginia, Delaware, and New York, Highmark is an impacted payer under CMS-0057-F for its Medicare Advantage (MA), Medicaid managed-care, and Qualified Health Plan (QHP) lines on the Federally-Facilitated Exchange. This rule mandates new standards for prior authorization processes, including API-based submissions and accelerated decision timeframes, with a phased rollout through 2027.

Navigating Highmark Prior Authorization Channels and CMS-0057-F

Currently, Highmark routes most medical-benefit prior authorization submissions through Availity Essentials. X12 278 transactions are also accepted via clearinghouses for applicable procedures. CMS-0057-F introduces a requirement for a FHIR-based Prior Authorization API, aligned with the HL7 Da Vinci PAS IG, which will eventually supplement or replace legacy channels for impacted lines of business. Klivira's platform is designed to bridge these methods, supporting both current submission channels and future API integrations for Highmark.

Key CMS-0057-F Requirements Impacting Highmark Workflows

**Prior Authorization API:** Highmark must implement a FHIR-based API for automated PA requests, status, and decisions, aligning with Da Vinci PAS IG, for its impacted plans.
**Accelerated Decision Timeframes:** Highmark must adhere to 72 hours for standard PA requests and 24 hours for expedited requests for MA, Medicaid managed-care, and QHP members.
**PA Reason Disclosure:** Payers are required to provide specific reasons for any prior authorization denial, enhancing transparency for providers.
**PA Metric Reporting:** Highmark will be required to publicly report prior authorization metrics annually, starting in 2026, for its impacted lines of business.
**Patient and Provider Access APIs:** Expansion of FHIR-based APIs to allow patients and providers to access relevant coverage and clinical data.

Klivira's Strategy for Highmark CMS-0057-F Compliance

Klivira's platform is engineered to support providers in achieving seamless Highmark CMS-0057-F compliance. We facilitate PAS-conformant submissions for payers with production API conformance, while maintaining robust X12 278 fallback for Highmark processes not yet transitioned. Our system tracks and enforces the new 72/24-hour decision timeframes for impacted Highmark PA requests and parses detailed denial reasons, feeding them into appeal-workflow automation.

Operationalizing New Prior Authorization Timelines with Highmark

The CMS-0057-F rule mandates significantly shorter decision timeframes for Highmark's Medicare Advantage, Medicaid managed-care, and QHP plans. Klivira's platform helps your team operationalize these new rules by automatically flagging requests requiring expedited review and tracking Highmark's response times against the 24-hour (urgent) and 72-hour (standard) limits. This ensures your team can enforce compliance and escalate as necessary.

Accessing Highmark Policy and Streamlining Documentation

Highmark publishes its medical policy and clinical utilization management guidelines through its provider site. Klivira integrates with your EMR to help compile and attach necessary clinical documentation, streamlining the submission process whether through Availity, X12 278, or future FHIR APIs. This ensures that even complex prior authorizations, including those for advanced imaging or specialty services, are submitted with all required information to Highmark, reducing potential delays.

Frequently asked questions

What Highmark plans are affected by CMS-0057-F?

CMS-0057-F applies to Highmark's Medicare Advantage organizations, Medicaid managed-care organizations, and Qualified Health Plan (QHP) issuers on the Federally-Facilitated Exchange. Commercial plans are not directly impacted by this specific federal rule.

How will CMS-0057-F change prior authorization submissions to Highmark?

The rule mandates Highmark to implement a FHIR-based Prior Authorization API for impacted plans, enabling automated requests, status checks, and decisions. While legacy channels like Availity and X12 278 will likely remain, the API will become a key method for compliant electronic prior authorization.

What are the new decision timeframes for Highmark prior authorizations under CMS-0057-F?

For impacted Highmark plans, the rule mandates a decision timeframe of 72 hours for standard prior authorization requests and 24 hours for urgent or expedited requests. These timeframes are significantly shorter than many historical state-mandated minimums.

How does Klivira help integrate with Highmark's PA processes for CMS-0057-F?

Klivira provides a unified platform that connects with Highmark's existing Availity and X12 278 channels, and will integrate with their future FHIR PA API. This enables automated submission, real-time status tracking, enforcement of decision timeframes, and parsing of detailed denial reasons to streamline appeals.

Will Highmark's use of Availity change due to CMS-0057-F?

While Availity remains a primary submission portal for Highmark, CMS-0057-F introduces a requirement for a FHIR-based API. Over time, for impacted plan types, providers may have the option to submit via the new API, potentially supplementing or integrating with existing Availity workflows. Klivira supports both channels.