Prior Authorization Modernization
Prior authorization will run on two paths for years: the X12 278 and the FHIR Prior Authorization API required by CMS-0057-F (the CMS Interoperability and Prior Authorization Final Rule).
The Burden Is in the Pended Queue
Certified and denied are the easy outcomes. Pended is where the work is: no deterministic resolution date, a documentation round-trip, and follow-up that consumes staff time indefinitely.
Automation that handles request and response and stops there has automated the part that was not expensive.
Documentation and Dual-Path
Documentation Is the Actual Obstacle
The 278 has no natural home for a chart note or an imaging report. The 275 attachment transaction is the standards-based answer and payer adoption is uneven: different payers accept different documentation, expressed different ways, with different linkage conventions. This variance is why fax machines survive in prior authorization thirty years after the 278 was defined. The standard exists; what payers accept does not line up.
Dual-Path Is the Pragmatic Architecture
CMS-0057-F obligates payers to expose a FHIR Prior Authorization API beginning January 1, 2027. It does not retire the 278. Organizations that build a single workflow surface above both paths get the benefit regardless of which payers move when. PNT supports 278, 275, and FHIR-based prior authorization exchange, routing in transit with no PHI retained. Per-payer path support is maintained per payer.
Frequently Asked Questions
How do you automate prior authorization?
By handling the pended queue as well as the request and response. Certified and denied resolve themselves; pended authorizations have no deterministic resolution date and require a documentation round-trip, which is where the administrative burden actually sits. Automation that stops at the first response has automated the cheap half.
Should we build for X12 278 or the CMS-0057-F FHIR API?
Both. CMS-0057-F requires impacted payers to expose a FHIR Prior Authorization API beginning January 1, 2027, but does not retire the X12 278, which remains the HIPAA standard transaction. Payers will move at different times. A single workflow surface above both paths is the architecture that survives.
Why is prior authorization still done by fax?
Because the clinical justification a payer needs has no natural home in the 278, and payer support for the 275 attachment transaction is uneven: different payers accept different documentation with different linkage conventions. The obstacle is variance in what payers accept; the standard itself exists.
Transactions and Industries
278 Prior Authorization
The X12 278 path and the FHIR mandate: system-to-system authorization requests and responses.
275 Claims Attachments
Clinical documentation formatted and linked to the correct 837 claim in real time.
Health Plans
Vendor concentration is now a board question. An intermediary that retains nothing changes the answer.
Ready to talk through your use case?
Talk to a Post-n-Track specialist about your data challenges. A direct conversation, starting with what you need.