Streamlining Medicare CGM Prior Auth Workflows

Navigating Medicare CGM prior auth requirements can be complex, involving distinct processes for Original Medicare and Medicare Advantage plans. Klivira automates these critical workflows to enhance efficiency and compliance.

Revenue cycle directors and prior authorization coordinators face unique challenges with continuous glucose monitor (CGM) authorizations under Medicare. Understanding the nuances of federal programs, Medicare Administrative Contractor (MAC) jurisdictions, and varying policy requirements is crucial for timely approvals and reduced denials. Klivira provides a structured approach to manage these intricacies.

Medicare CGM Prior Auth: Original Medicare vs. Medicare Advantage

For Original Medicare (Fee-for-Service) members, prior authorization for Durable Medical Equipment (DME) like CGMs is handled through specific demonstration programs and expanded lists, routing through the responsible Medicare Administrative Contractor (MAC) for the provider's jurisdiction. Medicare Advantage (MA) plans, operated by private insurers, often have broader prior authorization requirements and their own specific processes, which Klivira also supports.

Submission Channels for Continuous Glucose Monitor Authorization

Traditional Medicare medical (Part A and B) prior authorizations, where applicable, are submitted to the relevant MAC, such as Noridian, NGS, WPS, Palmetto, FCSO, or Novitas. Klivira's MAC-aware routing ensures submissions align with per-jurisdiction specifics. For Medicare Advantage plans, submission channels vary by payer but often include direct payer portals or electronic prior authorization (ePA) via X12 278.

Essential Documentation for CGM Approvals

Successful CGM prior authorization under Medicare typically requires comprehensive clinical documentation. This includes clear evidence of diabetes type (Type 1 or Type 2), documentation of insulin dependence, and detailed physician notes supporting the medical necessity of continuous glucose monitoring. For supply re-authorization, evidence of continued medical necessity and device usage may also be required.

Policy Landscape: National and Local Coverage Determinations (NCDs/LCDs)

Medicare's coverage and prior authorization requirements for CGMs are governed by National Coverage Determinations (NCDs) published by CMS and Local Coverage Determinations (LCDs) issued by individual MACs. Klivira integrates NCD and LCD policy logic into its automation workflows, ensuring that authorization requests are aligned with the specific criteria, MAC jurisdiction, and effective dates.

Klivira's Approach to Streamlining Medicare CGM Prior Auth

Klivira's platform automates the complex process of Medicare CGM prior authorization. For Original Medicare, our system routes requests through the appropriate MAC-jurisdiction submission channels and applies NCD/LCD-aware policy logic. For Medicare Advantage plans, Klivira connects with private payer systems to manage their specific authorization workflows, reducing manual effort and improving submission accuracy.

Turnaround Times and Common Friction Points

Medicare PA programs have specific timeframes, which vary by program. It's important to note that the CMS-0057-F rule, while impacting many lines of business, has limited applicability to Traditional Medicare. Common friction points can include incomplete documentation, misrouting to the incorrect MAC, or non-adherence to specific NCD/LCD criteria. Klivira's pre-submission checks and intelligent routing help mitigate these issues.

Frequently asked questions

Does Original Medicare require prior authorization for all CGM devices?

Original Medicare has a limited scope for prior authorization. However, Continuous Glucose Monitors (CGMs) fall under Durable Medical Equipment (DME), which has specific prior authorization programs. Requirements vary based on the specific device, patient criteria, and the governing National Coverage Determinations (NCDs) and Local Coverage Determinations (LCDs).

How do Medicare Administrative Contractors (MACs) factor into CGM prior auth?

For Original Medicare, MACs are responsible for processing claims and prior authorizations within their assigned jurisdictions. Providers submit CGM prior authorization requests to their respective MAC (e.g., Noridian, NGS, WPS, Palmetto, FCSO, Novitas), which then reviews them against CMS NCDs and their own LCDs. Klivira's system is designed to route requests to the correct MAC based on jurisdiction.

What documentation is typically needed for a Medicare CGM prior authorization?

Key documentation for Medicare CGM prior authorization includes medical records confirming the patient's diabetes type (Type 1 or Type 2), evidence of insulin dependence, and physician notes detailing the medical necessity for continuous glucose monitoring. For ongoing supply re-authorization, documentation of continued use and benefit is often required.

Is the CMS-0057-F rule relevant for Medicare CGM prior auth?

The CMS-0057-F rule primarily affects Medicare Advantage, Medicaid managed care, CHIP, and Qualified Health Plans on the Federal Facilitated Marketplace. Its applicability to Traditional Medicare (Original Medicare) prior authorization programs, including those for CGM devices, is limited. Specific turnaround times for Traditional Medicare PA programs are documented on a per-program basis.

How does Klivira handle the different Medicare plan types for CGM prior auth?

Klivira differentiates between Original Medicare and Medicare Advantage plans. For Original Medicare, we route through the appropriate MAC-jurisdiction submission channels, leveraging NCD/LCD-aware policy logic. For Medicare Advantage plans, Klivira integrates with the specific private payer systems to manage their unique prior authorization workflows for CGM devices.

Related coverage

Other medicare prior auth coverage by specialty

Other medicare prior auth workflows

medicare integrations by EMR

Ready to automate this workflow with this payer?

See how Klivira automates prior authorizations for your team.

Request a demo