The CMS-0057 rule brings forward a series of critical requirements designed to enhance interoperability and streamline prior authorization processes. These mandates are intended to improve data exchange between payers, providers, and patients, but they also pose challenges as payers adapt their systems and workflows to meet compliance. Key requirements include:
Patient Access API:
Payers must implement an API that allows patients to access their health information, including claims, encounter data, and prior authorization details, empowering patients to make informed decisions about their care.
Provider Access API:
This API facilitates the sharing of patient data between payers and providers, ensuring that providers have comprehensive access to health information, improving care coordination, and reducing duplicative care.
Payer-to-Payer Data Exchange:
When patients switch health plans, the current payer must (with patient consent) securely share the patient’s data with the new payer via an API, ensuring continuity of care and preventing data loss during transitions.
Prior Authorization API:
The rule mandates a Prior Authorization API that automates and streamlines the end to end prior authorization process, reducing delays in care by speeding up the approval process.
Public Reporting Requirements:
Payers are required to publicly report on services and items that require prior authorization, including metrics on approvals, denials, and average decision timeframes, to improve transparency and accountability.
These requirements represent a significant shift in payer operations, pushing towards greater transparency, efficiency, and patient-centered care. While challenging, these mandates also offer payers the opportunity to modernize systems and enhance the overall healthcare experience.
In our work, we've noticed a gap between perception and reality regarding payers' readiness for CMS-0057 compliance. Some payers believe they are further along in their path to compliance than they actually are, potentially leading to delays and setbacks. This over-confidence often stems from underestimating the complexity of the changes required or over-relying on vendors without thorough strategic planning. The importance of evaluating and modifying current processes to accommodate new systems and data streams is often overlooked or underprioritized. The people part of compliance whether it’s education or simply fostering change, can be one of the biggest challenges along the way.
Our “Beyond Compliance” blog series emphasizes a strategic approach to compliance, starting with thorough assessment and analysis, moving through iterative improvements, and transforming insights into impactful actions. Below are the key steps with links to each related blog post:
The health IT landscape is rapidly evolving, and recent developments in both the CMS-0057 rule and the HTI-2 proposed rule have significant implications for payers. These regulations not only emphasize compliance but also present opportunities to leverage these mandates for strategic advantages.
Shift to APIs:
The transition to API-based interoperability is central to both CMS-0057 and HTI-2 regulations. APIs like the Patient Access API, Provider Access API, Payer-to-Payer API, and Prior Authorization API are mandated to improve data exchange and reduce administrative burdens.
HTI-2 Certification Requirements:
The HTI-2 proposed rule outlines certification criteria for health IT modules crucial for payers. By January 1, 2027, all health IT modules must be certified to support the key APIs required by CMS, aligning with the latest interoperability standards.
Compliance Timelines:
Compliance with CMS-0057 and HTI-2 requires careful planning. Key deadlines include January 1, 2026, for initial CMS-0057 requirements, and January 1, 2027, for APIs and certification. Payers must proactively align their strategies with these timelines to ensure compliance and avoid disruptions.
Strategic Utilization of APIs:
Beyond compliance, the APIs required under CMS-0057 and the added certification requirements in HTI-2 offer payers the opportunity to achieve strategic imperatives. These APIs can enhance patient engagement, improve care coordination, and streamline operations across the healthcare ecosystem.
By staying ahead of these developments and proactively addressing the requirements outlined in both CMS-0057 and HTI-2, payers can not only ensure compliance but also drive innovation and strategic growth in an increasingly interconnected healthcare environment.
With over 20 years of experience in Health IT, POCP offers unparalleled expertise in navigating the complexities of CMS-0057. Our team includes leaders with deep industry knowledge and active involvement in standards organizations like NCPDP, HL7, and FHIR Accelerators.
POCP is a recognized expert in helping payers navigate the complexities of modern-day interoperability, including CMS-0057 by developing robust strategies tailored to your current capabilities. To learn more about how we can support your path to compliance and position your organization for strategic success, visit our Payer Navigation for CMS-0057 landing page. Here, you’ll find detailed information on our services and how we can help you meet the CMS-0057 requirements while driving innovation and efficiency
For more information and to start your compliance journey, contact Kendra Obrist at kendra.obrist@pocp.com and Brian Dwyer at brian.dwyer@pocp.com.