Prior Authorization API Testing

Prior Authorization APITesting with Operon

Operon proxies and measures UM decisions across the plan's PA vendors and internal review queues, exposing a conformant 278-equivalent FHIR surface.

Da Vinci PAS IG latest publishedAvailable for TestingLast Verified 2026-05-10
Capability Matrix

What You Can Test with Us

Operon's Prior Authorization API capability surface vs Da Vinci PAS IG latest published. Verified 2026-05-10.

Operon Prior Authorization API capability matrix vs Da Vinci PAS IG latest published
ResourceProfileReadSearchWriteNotes
ClaimPAS ClaimYesYesYesPA submission
ClaimResponsePAS ClaimResponseYesYesNo
ServiceRequestPAS ServiceRequestYesYesYes
CoverageCARIN BB CoverageYesYesNo
PatientUS Core PatientYesYesNo
PractitionerUS Core PractitionerYesYesNo
Conformance Basis

Implementation Guide Conformance

Primary IG

Da Vinci PAS IG latest published ↗Last verified 2026-05-10

Companion IGs

Authentication

OAuth 2.0 with system-to-system client-credentials flow between provider EHR and payer.

Supported FHIR Operations

  • POST /Claim/$submit
  • POST /Claim/$inquire
  • GET /ClaimResponse/{id}

Operon publishes a CapabilityStatement aligned to Da Vinci PAS IG. The current version ships in the Operon CMS-0057-F Testing Spec; a hosted metadata endpoint follows in v2.

Testing Scenarios

Anchor Scenarios

The exact paths your testing partners hit. Each scenario maps to a concrete request shape, expected response, conformance checkpoints, and the readiness metric Operon emits.

Scenario 1

PA submission (medical or pharmacy)

Trigger
Provider submits PA from EHR
Request
POST Claim with $submit operation
Expected response
ClaimResponse with provisional or final decision
Conformance checkpoints
  • PAS Claim profile
  • X12 278 semantic equivalence
Readiness metric emitted
Decision-time vs SLA

Scenario 2

Determination poll

Trigger
Provider polls for pending PA outcome
Request
POST $inquire with claim correlation id
Expected response
Updated ClaimResponse
Conformance checkpoints
  • Polling cadence support
  • Status semantics
Readiness metric emitted
Decision-time vs SLA

Scenario 3

CRD card on order entry

Trigger
EHR fires CDS Hooks order-select / order-sign
Request
CRD service request
Expected response
CDS card recommending PA submission with required data
Conformance checkpoints
  • Da Vinci CRD card profile
  • PA-required signal accuracy
Readiness metric emitted
CRD signal accuracy

Scenario 4

DTR questionnaire return

Trigger
CRD card prompts DTR launch
Request
GET Questionnaire + POST QuestionnaireResponse
Expected response
Pre-populated questionnaire and submission
Conformance checkpoints
  • DTR profile compliance
  • Pre-population correctness
Readiness metric emitted
DTR pre-population coverage

Scenario 5

SLA-clock conformance (72-hr expedited / 7-day standard)

Trigger
PA submission with urgency indicator
Request
POST Claim with priority code
Expected response
ClaimResponse delivered within SLA window
Conformance checkpoints
  • SLA clock start/stop semantics
  • Public-reporting metric emission
Readiness metric emitted
Decision-time vs SLA

Scenario 6

Denial-reason taxonomy emission

Trigger
PA denied with structured reason
Request
POST Claim
Expected response
ClaimResponse with denial reason aligned to public-reporting taxonomy
Conformance checkpoints
  • Denial-code conformance
  • Public-reporting alignment
Readiness metric emitted
Denial-reason taxonomy alignment
Sample Data

Sample Bundles

What's Provisioned

Six PA scenarios spanning medical and pharmacy lines, expedited and standard SLAs, approval and denial paths, with CRD/DTR companion artifacts.

Sample bundle excerpts are included in the Operon CMS-0057-F Testing Spec PDF. Full bundles are loaded into your sandbox tenant when your testing window is provisioned.

How It Works

How a Testing Window Works for Prior Authorization API

Step 1

Intake

Submit org type, role, this API selection, target window, and system-of-record context.

Step 2

Sandbox Tenant + Kickoff

Provisioned within 2 business days; 60-minute joint kickoff confirms scenarios, conformance targets, and success criteria.

Step 3

Testing Window + Report

1 to 4 weeks of live testing with daily conformance and latency telemetry, ending in a public-reporting-ready conformance and readiness report.

What You Get

Measurement Output

End-of-Engagement Report

Per-scenario conformance vs Da Vinci PAS, CRD, and DTR, SLA-clock report, denial-reason alignment report, and a pre-filled CMS public-reporting metric template.

Readiness Metrics Emitted

  • Decision-time vs SLA: Median and p95 decision time vs the 72-hour expedited and 7-day standard targets.
  • Denial-reason taxonomy alignment: Percent of denials whose reason maps to the CMS public-reporting denial taxonomy.
  • Public-reporting metric template: Filled-in template aligned to the CMS public-reporting metrics format for plans.
Related APIs

The Other CMS-0057-F APIs

Da Vinci PDex Provider Access IG latest published

Provider Access API

Providers under attribution agreement pull clinical, claims, and encounter data via group-based bulk export.

View Provider Access API Details →

Da Vinci PDex Payer-to-Payer IG latest published

Payer-to-Payer API

Concurrent and prior payers exchange member historical data via $member-match and historical bundle handoff.

View Payer-to-Payer API Details →

Da Vinci CRD IG v2.0.1 / v2.1.0 / v2.2.1 concurrent

Coverage Requirements Discovery (CRD)

Plans expose CDS Hooks services so a provider EHR can surface prior-authorization requirements at order entry or order-sign time, before the claim is submitted.

View Coverage Requirements Discovery (CRD) Details →

Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive)

Document Templates and Rules (DTR)

Plans expose payer-defined Questionnaires (Standard and Adaptive) that the provider EHR can launch from a CRD card, pre-populate from clinical data, and attach to the subsequent PA Claim.

View Document Templates and Rules (DTR) Details →
Ready to Test

Schedule a Prior Authorization API Testing Window

30 minutes with our team. We'll ask about the systems you already run, where you are on the CMS-0057-F calendar, and what testing you need to ship.