Payer APIs and prior authorization: the healthcare interoperability outlook for 2027
Prior authorization clocks started in 2026 and payer APIs are due January 1, 2027, while providers got until 2028 and the drug rule is still a proposal.
Two clocks, one already running
CMS published the Interoperability and Prior Authorization final rule, CMS-0057-F, on February 8, 2024, and it took effect April 8, 2024 [1]. It binds what it calls impacted payers: Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and issuers of Qualified Health Plans on the Federally-facilitated Exchanges [1]. It runs on two timetables. The prior authorization process changes started in 2026: by January 1, 2026 for Medicare Advantage organizations and state fee-for-service programs, by the rating period beginning on or after January 1, 2026 for Medicaid and CHIP managed care, and for plan years beginning on or after January 1, 2026 for Exchange issuers [1]. The application programming interface (API) requirements follow, primarily from January 1, 2027 [1] [2].
The process rules are now in force. Payers must send a decision notice with a specific reason for any denial, and every impacted payer except Exchange QHP issuers must decide within 72 hours for expedited requests and 7 calendar days for standard requests [1]. The prior authorization rules cover items and services; they do not apply to drugs of any type [1]. CMS still describes January 1, 2027 as the date the electronic prior authorization interfaces go live, and its May 2026 announcements restated that deadline [4] [6].
The deadline table
| Date (as written in the source) | What applies | Who |
|---|---|---|
| January 1, 2026 (and the payer-type variants) | Decision notices with specific denial reasons; 72-hour and 7-day decision timeframes [1] | Impacted payers; timeframes exclude Exchange QHP issuers [1] |
| March 31 each year, beginning in 2026 | Prior authorization metrics for the previous calendar year posted on the payer's website (Medicare Advantage text, contract level) [3] | Medicare Advantage organizations; all impacted payers report metrics [1] |
| January 1, 2027 | Patient Access API with prior authorization data; new Provider Access, Payer-to-Payer and Prior Authorization APIs [1] | Impacted payers |
| CY 2027 | Electronic Prior Authorization measure optional, 10 bonus points [7] [8] | Hospitals, critical access hospitals, MIPS clinicians |
| October 1, 2027 (proposed only) | Electronic prior authorization for drugs through the Prior Authorization API and NCPDP standards [9] | Impacted payers, if finalized |
| CY 2028 | Hospitals attest "Yes" or claim an exclusion; the measure becomes required for MIPS clinicians [7] [8] | Hospitals, critical access hospitals, MIPS clinicians |
Public metrics turn turnaround times into a comparison
Under 42 CFR 422.122(c), a Medicare Advantage organization reports prior authorization data at contract level by March 31, beginning in 2026, covering the previous calendar year [3]. The posted data include the list of items and services that need prior authorization, approval and denial percentages for standard and expedited requests, the share approved after appeal, and the average and median time from request to decision [3]. The report due by March 31, 2027 is the first to cover a full calendar year in which the 2026 decision timeframes applied, so it is the first public test of whether plans met them.
Moraph's view
Moraph's view: the March 2027 postings will matter more to health systems than the APIs that go live three months earlier. Revenue cycle teams can set their own denial and turnaround data beside each plan's published figures, contract by contract, and bring the gaps to contract negotiations. Payers whose posted medians sit close to the 7-day ceiling should expect that question.
The four APIs, and what is still only proposed
The 2027 requirements extend the Patient Access API from the 2020 rule to include prior authorization information and add three new FHIR APIs: Provider Access, Payer-to-Payer and Prior Authorization [1]. The Prior Authorization API must show whether an item or service needs prior authorization and what documentation is required, support a HIPAA-compliant request and response, and return the decision with a specific reason for any denial [3]. On February 28, 2024, CMS's National Standards Group announced it would not take HIPAA enforcement action against covered entities that skip the X12 278 standard when they use a FHIR-based Prior Authorization API as the rule describes [2].
On April 14, 2026, CMS and ONC proposed a second rule, CMS-0062 [9] [10]. It would require impacted payers to support electronic prior authorization for all drugs through the Prior Authorization API and NCPDP standards beginning October 1, 2027, add small group QHP issuers on the federally-facilitated SHOP Exchanges as impacted payers, require payers to report API endpoints and usage metrics to CMS, turn currently recommended HL7 FHIR implementation guides into requirements, and adopt FHIR as a HIPAA standard for certain authorization and eligibility transactions [9]. Comments closed June 15, 2026 [9]. As checked on 16 November 2026, the Federal Register lists only the proposal and a correction to the hospital payment rule under the proposal's regulation identifier, so nothing in CMS-0062 binds payers yet [10].
Moraph's view
Moraph's view: payers should build the 2027 Prior Authorization API on the Da Vinci guides now, as though the proposal were final. The proposal points that way, certified provider technology will be required to use the updated guides, and rebuilding an interface a year after go-live costs more than building it once.
The provider side moved a year later
CMS-0057-F created an Electronic Prior Authorization measure, a yes-or-no attestation, for hospitals and MIPS clinicians in CMS's Promoting Interoperability programs [1]. The FY 2027 hospital inpatient rule, published August 4, 2026, made the measure optional and worth 10 bonus points for eligible hospitals and critical access hospitals in CY 2027, and requires a "Yes" attestation or an exclusion from the CY 2028 reporting period, with the measure unscored [7]. In that rule CMS said it is very strongly considering further changes in the FY 2028 proposed rule to align hospital requirements with those for clinicians [7]. The CY 2027 physician fee schedule rule, published November 9, 2026, made the measure optional and worth 10 bonus points for CY 2027, required from CY 2028, and added a required Electronic Prior Authorization for Prescription Drugs measure from CY 2028 [8]. The hospital rule ties the measure to technology certified to 45 CFR 170.315(g)(31) through (g)(33), which will require version 2.2 of the Da Vinci implementation guides [7].
The effect: payers must expose Prior Authorization APIs on January 1, 2027, while hospitals and clinicians face no penalty for not calling them until 2028 [1] [7] [8].
Certification: HTI-4 added, HTI-5 removed
ONC's HTI rules page lists five final rules: HTI-1 (certification program updates, algorithm transparency and information sharing), HTI-2 (TEFCA), HTI-3 (protecting care access), HTI-4 (electronic prescribing, real-time prescription benefit and electronic prior authorization) and HTI-5 (deregulatory actions) [11]. ONC withdrew the remaining, unfinalized HTI-2 proposals effective December 29, 2025 [14]. HTI-4 was published inside the FY 2026 hospital payment rule, took effect October 1, 2025, and added certification criteria for electronic prior authorization [12]. HHS projects HTI-4 will save over $19.2 billion in administrative costs over the next decade [17].
HTI-5 goes the other way. Of the 60 certification criteria in effect, ONC had proposed removing 34 and revising seven; the final rule removes 14 and revises seven [13]. It takes effect December 28, 2026, with some amendments effective January 1, 2027 [13].
TEFCA and the pledge networks
ONC says the first Qualified Health Information Networks (QHINs) under TEFCA were designated in December 2023 [15]. ONC's TEFCA fact sheet, dated February 11, 2026 and last updated June 5, 2026, lists 11 participating QHINs: CommonWell, eClinicalWorks, eHealth Exchange, Epic Nexus, Health Gorilla, Kno2, KONZA, MedAllies, Netsmart, Oracle Health and Surescripts [23]. As checked on 16 November 2026, the Recognized Coordinating Entity's designated QHIN page shows the same 11 networks [16]. HHS reported on February 11, 2026 that nearly 500 million health records had been exchanged through TEFCA, up from roughly 10 million in January 2025 [17].
CMS has also built a voluntary layer alongside the rules. On July 30, 2025 it announced the CMS Interoperability Framework and CMS Aligned Networks, with more than 60 companies pledging to work together and 21 networks pledging to meet the framework's criteria, with results targeted for the first quarter of 2026 [22]. On June 23, 2025, health plans covering nearly eight in ten Americans pledged to reduce the services subject to prior authorization by January 1, 2026, standardize electronic submissions on FHIR APIs, and answer most requests in real time by 2027 [5]. CMS's May 5, 2026 blog relayed that leading health plans announced in April that they had eliminated 11% of prior authorizations across a range of medical services, which it put at 6.5 million fewer prior authorizations; that figure is the plans' own announcement, not a CMS measurement [4]. On May 13, 2026 CMS said 29 organizations had joined an Electronic Prior Authorization Acceleration initiative ahead of the 2027 requirements [6].
Information blocking now has enforcement behind it
OIG's penalty sections, 42 CFR 1003.1400 to 1003.1420, took effect September 1, 2023 [20]. OIG may impose up to $1 million per violation on developers of certified health IT, health information networks and exchanges [19]. Providers instead face disincentives under a rule effective July 31, 2024: an eligible hospital, critical access hospital or MIPS eligible clinician referred by OIG is not a meaningful EHR user, and a Shared Savings Program ACO or participant may be barred for at least 1 year [21]. On September 3, 2025, HHS announced it would increase resources for information blocking enforcement [18]. On February 11, 2026 it said ONC had begun its first oversight actions under 45 CFR 170.580, issuing notices of potential non-conformity to certain certified developers about the information blocking condition and API maintenance requirements [17]. OIG's information blocking page, last updated May 27, 2026, lists no resolved penalty [19].
Moraph's view
Moraph's view: from 2027 a payer's Provider Access API and a health system's patient-facing API both become exchange paths that regulators can test against a complaint. The first public information blocking penalty, whenever it comes, will reset how cautious every actor is about saying no to a data request, and we expect it within the outlook period.
This page describes public rules and announcements; it is not legal advice on what any organization must do.
What this means for you
- Payers: Treat January 1, 2027 as fixed for all four APIs and build the Prior Authorization API on the HL7 Da Vinci guides that the April 2026 proposal would require [1] [9]. Check the March 31 metrics posting against your own decision logs before it goes public [3].
- Health systems: Use 2027, when the Electronic Prior Authorization measure is optional, to connect EHR workflows to the largest payers' Prior Authorization APIs before the CY 2028 requirement [7] [8]. Compare each plan's posted prior authorization metrics with your own denial and turnaround data [3].
- Medicaid agencies: Plan for both CMS-0057-F's 2027 APIs and the proposed drug requirements, which would apply from October 1, 2027 if finalized; the proposal notes that Medicaid's existing decision timeframe for covered outpatient drugs is 24 hours [1] [9].
- EHR and API vendors: Prioritize certification to 45 CFR 170.315(g)(31) through (g)(33) on version 2.2 of the Da Vinci guides, and review API and information blocking practices now that ONC issues notices of potential non-conformity [7] [17].
Moraph predictions
Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.
P1 By Confidence 80% Open
CMS does not postpone the January 1, 2027 compliance date for Medicare Advantage organizations' Provider Access, Payer-to-Payer and Prior Authorization APIs.
How we will check: No final rule, interim final rule or CMS enforcement discretion notice published between 16 November 2026 and 31 March 2027 delays or suspends enforcement of those API requirements for Medicare Advantage organizations.
Basis: The April 2026 drug proposal states it would not change the 2027 API dates, and CMS restated January 1, 2027 in May 2026 [4] [6] [9].
P2 By Confidence 65% Open
CMS publishes a final rule from RIN 0938-AV44 (CMS-0062) that requires impacted payers to support electronic prior authorization for drugs.
How we will check: The Federal Register lists a final rule under RIN 0938-AV44 that adopts electronic prior authorization requirements for drugs for impacted payers, published on or before 31 December 2027.
Basis: The proposal was published April 14, 2026, comments closed June 15, 2026, and it proposes an October 1, 2027 compliance date; as checked on 16 November 2026 no final rule was listed [9] [10].
P3 By Confidence 70% Open
The FY 2028 hospital inpatient final rule keeps the Electronic Prior Authorization measure required (a "Yes" attestation or an exclusion) for eligible hospitals and critical access hospitals for the CY 2028 EHR reporting period.
How we will check: The FY 2028 IPPS/LTCH PPS final rule, published by 31 August 2027, does not make the Electronic Prior Authorization measure optional or delay it for the CY 2028 EHR reporting period.
Basis: The FY 2027 rule requires the measure from CY 2028 and says CMS may align hospital rules with the clinician rules, which require it from CY 2028 [7] [8].
P4 By Confidence 55% Open
HHS OIG publicly announces at least one resolved information blocking civil money penalty or settlement with a developer, health information network or exchange.
How we will check: OIG's information blocking page, an OIG press release or ONC's public list of actors shows at least one resolved information blocking penalty or settlement, dated on or before 31 December 2027.
Basis: Penalties have been available since September 1, 2023, HHS announced more enforcement resources in September 2025, and OIG's page listed no resolved penalty when last updated May 27, 2026 [18] [19] [20].
P5 By Confidence 55% Open
The Recognized Coordinating Entity's designated QHIN page lists at least 13 designated QHINs.
How we will check: On or before 31 December 2027, rce.sequoiaproject.org/designated-qhins/ (or its successor page) shows 13 or more designated QHINs.
Basis: ONC's TEFCA fact sheet, last updated June 5, 2026, lists 11 participating QHINs, the RCE page showed the same 11 as checked on 16 November 2026, and the first designations came in December 2023 [15] [16] [23].
Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.
Spotted an error? Tell us and we will check it and correct the piece where needed.