Navigating BCBS Tennessee 21st Century Cures Act Compliance
The 21st Century Cures Act, specifically its implementing regulations, significantly reshapes prior authorization processes for payers like BCBS Tennessee. Understanding these mandates is critical for maintaining efficient revenue cycles.
Revenue cycle directors, prior authorization coordinators, and IT integration leads must navigate evolving regulatory landscapes. The federal 21st Century Cures Act, particularly through the CMS Interoperability and Patient Access Final Rule (CMS-0057-F), introduces new requirements for health plans regarding data exchange and prior authorization workflows. For providers operating in Tennessee, understanding how these mandates apply to BCBS Tennessee is essential for operational continuity and compliance.
The 21st Century Cures Act and Payer Obligations
The 21st Century Cures Act aims to accelerate medical product development and bring innovation to patients faster, but also includes critical provisions for health information interoperability. For payers, these provisions are largely codified through the CMS Interoperability and Patient Access Final Rule (CMS-0057-F), which mandates specific data exchange and prior authorization requirements. As an independent BlueCross BlueShield licensee, BCBS Tennessee is subject to these federal regulations affecting their prior authorization and data sharing operations.
BCBS Tennessee's Compliance Posture
As a major health plan serving Tennessee, BCBS Tennessee is actively working to align its operations with the federal mandates of the 21st Century Cures Act. This includes adapting their systems and processes to meet requirements for electronic prior authorization, data transparency, and interoperability. Providers should anticipate changes in how prior authorization requests are submitted, processed, and responded to, reflecting BCBST's adherence to these evolving regulatory standards.
Key Prior Authorization Changes Mandated by CMS-0057-F for Payers like BCBS Tennessee
- **Electronic Prior Authorization (ePA):** Mandates the implementation and maintenance of an API to support electronic prior authorization requests and responses using the X12 278 standard and the Da Vinci PAS Implementation Guide.
- **Shortened Turnaround Times:** Requires payers to make prior authorization decisions within 7 calendar days for standard requests and 72 hours for expedited requests.
- **Transparency and Reporting:** Payers must publicly report specific metrics regarding prior authorization decisions, including approval rates and turnaround times.
- **Reason for Denial:** Requires payers to provide specific, detailed reasons for denied prior authorization requests to providers and patients.
- **Payer-to-Payer Data Exchange:** Mandates payers to exchange certain patient data upon a patient's request, facilitating continuity of care when patients switch plans.
Impact on Providers Submitting to BCBS Tennessee
For clinics, hospitals, and health systems in Tennessee, these regulatory changes necessitate a shift towards more robust electronic prior authorization workflows when interacting with BCBS Tennessee. Leveraging ePA capabilities, understanding the new turnaround time expectations, and preparing for enhanced data exchange are crucial. Your IT integration leads should ensure systems are capable of interacting with BCBS Tennessee's compliant APIs for efficient data transfer and reduced administrative burden.
Streamlining BCBS Tennessee PA Compliance with Klivira
Klivira's platform is designed to help providers seamlessly adapt to these regulatory shifts. By integrating with EMRs and payer portals, including those utilized by BCBS Tennessee (like Availity and BlueAccess), Klivira automates the electronic submission of prior authorization requests via X12 278, tracks decision statuses, and facilitates compliance with transparency requirements. This ensures your organization can meet the demands of the 21st Century Cures Act without disrupting patient care or revenue cycles.
Frequently asked questions
What is the 21st Century Cures Act's primary impact on prior authorization for BCBS Tennessee?
The primary impact stems from the CMS Interoperability and Patient Access Final Rule (CMS-0057-F), which mandates electronic prior authorization (ePA) via X12 278, sets specific turnaround times for decisions, and requires enhanced transparency and data exchange capabilities for payers like BCBS Tennessee.
Does the Cures Act require BCBS Tennessee to shorten prior authorization turnaround times?
Yes, the CMS-0057-F final rule, implementing aspects of the Cures Act, mandates that payers like BCBS Tennessee must make prior authorization decisions within 7 calendar days for standard requests and 72 hours for expedited requests.
How does the Cures Act affect data exchange between providers and BCBS Tennessee for prior authorizations?
The Cures Act, through CMS-0057-F, requires BCBS Tennessee to implement APIs that support electronic prior authorization requests and responses using the X12 278 standard and the Da Vinci PAS Implementation Guide, facilitating more efficient and standardized data exchange.
What should providers do to ensure compliance with Cures Act requirements when submitting to BCBS Tennessee?
Providers should prioritize adopting robust electronic prior authorization solutions that can integrate with BCBS Tennessee's compliant systems, utilize X12 278 for submissions, and monitor for prompt decision responses. Discussing these changes with your compliance team is also advisable.
Is BCBS Tennessee required to provide reasons for prior authorization denials under the Cures Act?
Yes, the CMS-0057-F final rule mandates that payers, including BCBS Tennessee, must provide specific reasons for any denied prior authorization requests to both the provider and the patient.
Related coverage
Ready to stay compliant with this rule?
See how Klivira automates prior authorizations for your team.
Request a demo