Skip to site content
New to Availity? Get Started

End-to-End Prior Authorizations Using FHIR APIs

Challenge

Prior authorizations are a critical utilization management (UM) tool. These transactions are used to help ensure high-quality and cost-effective care delivery. Unfortunately, many providers and health plans consider the prior authorization process a burden due to manual interventions, analog technologies, and inconsistent standardization. Conventional prior authorization processes are complex and time-consuming, mainly due to substantial variations in payer requirements, limited adoption of an X12 278 prior authorization request, and challenges related to data management. As a result, provider staff are often tasked with reaching out to a patient’s health plan to supply the necessary demographic and clinical data needed to initiate the authorization process.

Solution

To address pain points within the prior authorization process, a collaborative initiative was launched by Humana, athenahealth, and Availity. The objective was to develop an automated end-to-end prior
authorization process leveraging the Da Vinci Burden Reduction Implementation Guides. This required analysis of the implementation guides and each party’s internal systems to define requirements for implementation. The participating organizations were diligent in their collaboration to clarify the exact details of the implementation. The joint approach to decision making was a powerful demonstration of what collaboration in the healthcare space can look like.

Da Vinci Burden Reduction Implementation Guides

The implementation guides include Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS), which support an integrated workflow to enable automated submission of prior authorizations from EHR systems.

Da Vinci, an initiative sponsored by Health Level Seven® (HL7®) International, collaborates with U.S. payers, providers, and technology suppliers. Aligned with the Centers for Medicare & Medicaid Services’ (CMS) commitment to promote Fast Healthcare Interoperability Resources (FHIR®) as the standard for data sharing through government mandates, the project aims to help improve the delivery of care by streamlining data exchange. Humana, athenahealth, and Availity are all active
members of the Da Vinci project.

The workflow of the implementation and the distinct roles of each healthcare entity within the guides are detailed below:

Project Goals

To address prior authorization pain points, Humana, athenahealth, and Availity embarked on a collaborative initiative to develop an end-to-end prior authorization process leveraging the Da Vinci
Burden Reduction Implementation Guides. The goals of this collaboration were to:

  • Improve transparency into the prior authorization process;
  • Reduce the administrative burdens for both the health plan and its provider network;
  • Leverage available clinical content; and
  • Increase opportunities for automation

Step 1: Coverage Requirements Discovery

The initial phase involves the EHR system utilizing the payer’s FHIR – based CRD API to determine if
authorization is necessary for the specified member and requested service. The payer then responds with a ‘yes’ or ‘no.’ If the response is ‘yes,’ additional details will be provided regarding the necessary information for submitting the authorization request. Understanding authorization requirements before an authorization request is submitted improves overall coordination, speed and effectiveness of the end to end Utilization Management process. Creating a direct, real-time connection is key in this automation.

Step 2: Documentation Templates and Rules

When a prior authorization is needed, the communication from the payer’s system to the provider’s EHR may include a request to complete a questionnaire or a request to include supporting clinical information with the authorization request. In current manual processes, practices may often be able to provide required details when initiating an authorization via portal or phone – causing them to abandon the task. Additionally, providers may become aware of additional requirements only after the authorization has been submitted. DTR simplifies the administrative work for providers and can reduce the turnaround time for an authorization decision.

Step 3: Prior Authorization Support

In the last step, the EHR sends the authorization request and medical documents as a FHIR bundle to the health information network. Prior to the most recent ruling, the CMS Regulation requires the utilization of X12 278 to meet HIPPA standards, unless the payer has received an exception. The health information network translates this transaction and sends the request to the health plan using their existing X12 278 process. The health plan processes the request and quickly responds to the
network with an authorization reference number and status. The network routes the information to the EHR for display in the provider’s workflow. Subsequent status updates triggered by the health
plan are also communicated to the EHR in real time

Overall Results

Outcomes were measured in the following ways:

Burden Reduction:

Evaluate time savings for staff by integrating real-time authorization determination capabilities. This initiative lead to an average of 17,585 orders with no authorization required, which saved provider staff about 4,396 hours per month that would have been spent verifying requirements for these authorizations.1 Additionally, no authorizations were denied due to lack of documentation during the October to December 2023 evaluation period.2

Touchless Resolution:

Measuring the value of authorization determination capabilities and authorization auto-approvals. The stakeholders determined that during the evaluation period, nearly 54% of all requests per month required no authorization, and a monthly average of 70% of authorizations submitted through the
integration were auto approved.

Fast resolution:

Gathering required data elements up front allow for quick resolution of authorization requests, enabling providers to proceed with patient care. Between October to December 2023, the average time for an authorization to reach approval or denial status was 26 hours3 vs. industry averages that range from days to weeks.4 The 26-hour turnaround time on authorizations far exceeds the seven-day target established by the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F).

The Da Vinci Implementation Guide specifications facilitate prior authorization decisions for payers by ensuring they possess the necessary information upon receiving the authorization request. This proactive approach represents a significant stride toward streamlining the authorization process, alleviating administrative burdens for both providers and payers. Most importantly, it reduces turnaround time, directly benefiting the care of members/patients.

In addition, the integration is embedded directly into the existing into the existing provider workflow, causing minimal disruption to daily operations. This seamless transition allows providers to swiftly proceed with downstream activities such as scheduling and care delivery. Beyond the benefits of speed and automation, this process provides comprehensive transparency into each authorization from start to finish.

Lessons Learned

  • Understand: Must understand EHR system/provider workflow to identify where to implement functionality to create the biggest impact
  • Identify and agree: Identify and agree on SLAs and key metrics early to enable reporting and analysis
  • Align: Align on reporting and definition of success vs failure
  • Review: Make time to review the Da Vinci Implementation Guides, and contribute feedback through the HL7 Da Vinci process to drive enhancements
  • Unique identifier: Consider utilization of a unique identifier across all steps to associate CRD call/response, questionnaire, attachment and authorization along with responses throughout
  • Data considerations: Some data elements required by the payer, including X12 278 data elements, may not be available in EHR systems

Corporate Overview