Home / Insights / The FHIR Prior Authorization API, Explained: Da Vinci CRD, DTR, and PAS
November 16, 2026

The FHIR Prior Authorization API, Explained: Da Vinci CRD, DTR, and PAS

Of the four APIs CMS-0057-F requires, the Prior Authorization API is the hardest to build and the one providers feel most. Here is how it actually works.

What the Prior Authorization API is

The Prior Authorization API required by CMS-0057-F is a FHIR-based interface that lets a provider, from inside their EHR, check whether a service needs prior authorization, see exactly what documentation is required, and submit the request electronically — replacing the fax-and-phone process that slows care today. It must be in production by January 1, 2027. What sets it apart from a generic API is that CMS requires it to follow three HL7 Da Vinci implementation guides, which together define the whole workflow.

The three Da Vinci building blocks

  1. CRD — Coverage Requirements Discovery. As the provider orders a service in the EHR, CRD checks the payer in real time and tells them whether prior authorization is required.
  2. DTR — Documentation Templates and Rules. If authorization is needed, DTR pulls the payer’s questionnaire and auto-fills what it can from the patient’s record, so the provider only completes what is missing.
  3. PAS — Prior Authorization Support. PAS packages the request and sends it to the payer, translating between FHIR and the X12 278 transaction, then returns the decision.

How the workflow runs

In practice the three guides chain into one experience: the provider orders a service, CRD flags that it needs prior auth, DTR gathers and pre-fills the documentation, and PAS submits it and brings back the answer — often in the same visit. To the provider it feels like one step inside the EHR; behind it sits a FHIR server, a rules engine, and an X12 bridge to the payer’s existing utilization-management system.

Why it is the hardest of the four APIs

What payers need to build it

A working Prior Authorization API needs a conformant FHIR R4 server, the CRD, DTR, and PAS services, a FHIR-to-X12 278 bridge into your existing utilization-management system, your prior-authorization rules expressed as DTR questionnaires, and conformance and security testing against the CMS guides. Most payers do not have these pieces today — which is why the January 2027 deadline is really a 2025 and 2026 project.

How EIXSYS helps

EIXSYS builds the full Prior Authorization workflow for health plans and TPAs — the FHIR server, the CRD, DTR, and PAS services, and the FHIR-to-X12 bridge into your current UM system — and connects it to the other three CMS-0057-F APIs. Delivery is SOC 2 Type II, HIPAA, and ISO 27001 aligned.

Book a CMS-0057-F readiness assessment →

← All insights

Get started

Have a similar challenge?