What is Burden Reduction Rule?
As a healthcare provider, imagine the frustration of trying to order an MRI for a patient experiencing severe, unexplained headaches. You encounter multiple obstacles, such as delays in patient care due to the administrative burden of obtaining insurance authorization, lengthy response times from insurance companies, and the risk of not being reimbursed for the MRI if authorization is denied. These challenges not only impact your ability to provide timely care but also put your patient's well-being at risk.
That’s exactly the problem statement what CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) released in January 2024 intend to solve, by reducing administrative burdens for providers and payers (Medicare Advantage and Part D plan sponsors) and is popularly known as "Burden Reduction Rule". The rule enhances certain policies from the CMS Interoperability and Patient Access Final Rule (CMS-9115-F) and adds several new provisions to increase data sharing and reduce overall payer, healthcare provider, and patient burden through improvements to prior authorization practices and data exchange practices.
In this article, we will simplify and explain what the rule means for payer organizations by classifying the changes in 4 dimensions as shown below.
Rule Provisions
Prior Authorization API
The Prior Authorization (PA) API aims to reduce administrative burdens, improve transparency, and expedite the prior authorization process. It allows providers to quickly determine whether a service requires prior authorization, submit requests electronically, and receive timely decisions, ultimately leading to faster and more efficient patient care.
- The PA API must adhere to specific standards and protocols to ensure interoperability and seamless communication between providers and payers. This standardization simplifies the prior authorization process and reduces administrative burdens.
- Enable providers to submit prior authorization requests electronically and receive timely responses, including approvals, denials, or requests for additional information.
- Clearly define and communicate the documentation needed for prior authorization approval for specific services.
- Maintain an up-to-date list of covered items and services that require prior authorization, accessible through the API.
- Communicate prior authorization approvals and denials electronically, including specific reasons for denials to facilitate appeals or alternative treatment plans.
- Collect and report standardized prior authorization metrics to CMS, starting March 31, 2026. These metrics help assess the effectiveness of the PA process and identify areas for improvement.
Payer-to-Payer data exchange APIs
The P2P API aims to streamline data sharing between payers, especially when patients switch insurance plans or receive care from multiple providers. This can help reduce administrative burden, improve care coordination, and prevent duplication of services.
- Payers must make claims, encounter, and specific prior authorization data available through the P2P API. This data should only encompass information within the past five years from the date of the request
- Payers are required to offer patients an opt-in mechanism to control the sharing of their data via the P2P API. This is typically accomplished through a consent management system.
- The rule emphasizes the importance of protecting patient data privacy and security. Payers must adhere to strict regulations like HIPAA when implementing and using the P2P API
Provider Access API
The Provider Access API aims to improve care coordination, streamline administrative processes, and enhance communication between payers and providers. By providing providers with timely access to relevant patient data, it can facilitate more informed decision-making, reduce duplicate testing, and improve overall patient care.
- Payers are required to make claims, encounter data, and specific prior authorization data (excluding drugs) available to in-network providers through the Provider Access API. This data sharing is limited to providers with whom the patient has an established treatment relationship.
- Payers must maintain a process to verify and track the association between patients and their in-network providers. This ensures that data is only shared with relevant providers involved in the patient's care.
- Patients must be given the option to opt out of having their data shared through the Provider Access API. This ensures patient control over their health information.
- The Provider Access API should allow third-party applications, with patient consent, to register and access the data on behalf of providers. This enables the development of innovative tools and services that can leverage patient data to improve care coordination and outcomes.
Patient Access APIs
The enhanced Patient Access API aims to improve patient engagement and control over their healthcare data. It enables patients to easily access their medical records, claims, and prior authorization information through third-party applications of their choice. This fosters transparency, facilitates informed decision-making, and promotes care coordination.
- Payers are now mandated to incorporate specific prior authorization data (excluding drug prior authorizations) into the existing Patient Access API. This empowers patients to access information about their prior authorizations, understand the approval process, and track the status of their requests.
- Payers must submit annual reports to CMS, starting from January 1, 2026, detailing metrics related to the usage of the Patient Access API. This helps assess the effectiveness of the API in empowering patients and promoting data exchange.
- Rule mandates that payers provide patients with an option to opt out of having their information shared through the API. This ensures patient privacy and control over their data.
Challenges and Considerations
- Existing Implementation Complexities: Several Payers have contracted with third party systems for Prior Authorization processing. CMS 0057F rule brings complexities for Payers on how to route different member request still acting as a hub for all Prior Authorization requirements
- Data Standardization and Interoperability: Lack of standardized data formats and inconsistent terminology across different healthcare systems and providers make it difficult to seamlessly exchange PA information. Integrating the API with legacy systems and ensuring compatibility with various electronic health record (EHR) platforms can be complex and time-consuming.
- Regulatory Compliance: Payers must adhere to strict regulatory requirements, such as HIPAA, to protect patient data privacy and security. Ensuring compliance with evolving regulations while implementing the API adds another layer of complexity.
- Consent: Facilitating patient consent before sharing patient clinical information with other payers or providers may be cumbersome.
- Workflow Integration: Integrating the PA API into existing workflows and processes can be disruptive. Training staff on the new system, updating internal procedures, and managing change effectively are crucial for a smooth transition. Several complex workflows wiz. Order Create and Order approve hook, Coverage Requirement Determination (CRD), Documentation Templates and Requirements (DTR) and Prior Authorization submission and status enquiry may disrupt the existing established processes and add more complexities.
- Provider Adoption and Engagement: Encouraging providers to adopt and utilize the PA API can be a challenge. Some providers may be hesitant to change their existing workflows or may lack the necessary resources to integrate the API into their systems. Payers need to provide adequate support, training, and incentives to drive provider adoption.
How Can Xyram Help?
The CMS-0057-F rule is a game-changer, revolutionizing healthcare data exchange and prior authorization. But implementing these changes can be a daunting task. You need to navigate complex technical requirements, ensure compliance, and seamlessly integrate new processes into your existing workflows.
Xyramsoft is here to simplify your journey to CMS-0057-F compliance. Our comprehensive solutions and expert guidance help provider organizations and payers alike overcome implementation challenges and unlock the full potential of interoperability.
Complimentary Gap Analysis
We'll start with a free in-depth assessment of your current workflows, business requirements, and technology infrastructure. This will identify gaps and pinpoint areas for improvement.
Customizable Integration
We'll develop a tailored adapter interface that seamlessly integrates with your existing systems, ensuring minimal disruption to your operations.
Streamlined Prior Authorization
We'll implement solutions to automate and standardize your prior authorization processes, reducing administrative burden and improving patient care.
Enhanced Data Exchange
We'll leverage cutting-edge technology to facilitate secure and efficient data exchange between providers, payers, and patients, empowering you with valuable insights for better decision-making.
Frequently Asked Questions
Adhering to the CMS 0057-F final rule is critical for plan sponsors to avoid penalties and maintain their ability to participate in the Medicare Advantage and Part D programs. Non-compliance can lead to significant financial, operational, and reputational consequences. Therefore, plan sponsors must implement robust compliance programs and continually monitor their adherence to CMS regulations to avoid these penalties. Additionally, payers will benefits from better cost management, enhanced compliance, improved data insights, and strengthened provider relationships.
Yes, CMS is requiring all payers (excluding QHP issuers on FFE) to send prior authorization decisions within 72 hrs for expedited or urgent requests. Timeframe for standard requests is seven calendar days.
Unlike for payers, the CMS-0057-F final rule does not explicitly list financial penalties for provider organizations that do not comply with its provisions. However there are several potential repercussions for non-compliance like Negative impact on MIPS score, Difficulty in participating in Value based care models, and indirect finacial impact due to denied claims, delay in patient care, delayed claim payments and overall patient dissatisfaction .
Yes, a new measure “Electronic Prior Authorization" has been added for the MIPS Promoting Interoperability performance category and the Medicare Promoting Interoperability Program.
No, the prior authorization requirements in Prior Authorization Final Rule (CMS-0057-F) do not apply to drugs.
Take the next step towards transformation
Connect with us to find services that fit your organization's specific needs
