Provider Access API Testing

Provider Access APITesting with Operon

Operon performs group-based attribution and bulk export of clinical, claims, and encounter data to provider organizations under attribution agreement.

Da Vinci PDex Provider Access IG latest publishedAvailable for TestingLast Verified 2026-05-10
Capability Matrix

What You Can Test with Us

Operon's Provider Access API capability surface vs Da Vinci PDex Provider Access IG latest published. Verified 2026-05-10.

Operon Provider Access API capability matrix vs Da Vinci PDex Provider Access IG latest published
ResourceProfileReadSearchWriteNotes
GroupDa Vinci Provider Access GroupYesYesNoAttribution group
PatientUS Core PatientYesYesNo
CoverageCARIN BB CoverageYesYesNo
ExplanationOfBenefitCARIN BB EOBYesYesNo
EncounterUS Core EncounterYesYesNo
ConditionUS Core ConditionYesYesNo
MedicationRequestUS Core MedicationRequestYesYesNo
ObservationUS Core ObservationYesYesNo
ProcedureUS Core ProcedureYesYesNo
Conformance Basis

Implementation Guide Conformance

Primary IG

Da Vinci PDex Provider Access IG latest published ↗Last verified 2026-05-10

Companion IGs

Authentication

OAuth 2.0 with attribution-based authorization. Provider system credentials scoped to attributed Group(s).

Supported FHIR Operations

  • GET /Group/{id}
  • POST /Group/{id}/$export
  • GET /$export-poll-status
  • GET /Patient/$everything

Operon publishes a CapabilityStatement aligned to Da Vinci PDex Provider Access 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

Group attribution sync

Trigger
Provider system polls for current attribution membership
Request
GET Group/{provider-group-id}
Expected response
Group resource with member references
Conformance checkpoints
  • Attribution accuracy
  • Profile compliance
Readiness metric emitted
Attribution accuracy

Scenario 2

Bulk export kickoff/poll/download

Trigger
Provider requests Group-scoped $export
Request
POST Group/{id}/$export with type filters
Expected response
Async kickoff + status poll + ndjson manifest
Conformance checkpoints
  • Bulk Data v2.0.0 spec compliance
  • Manifest integrity
  • NDJSON profile validity
Readiness metric emitted
Export latency

Scenario 3

Delta export

Trigger
Provider requests $export with `_since`
Request
POST Group/{id}/$export?_since={timestamp}
Expected response
Delta-only ndjson manifest
Conformance checkpoints
  • _since boundary correctness
  • Stable resource IDs
Readiness metric emitted
Export latency

Scenario 4

Permission-scoped resource filtering

Trigger
Provider has attribution for subset of available types
Request
POST Group/{id}/$export?_type=Encounter,Condition
Expected response
Manifest containing only authorized types
Conformance checkpoints
  • Scope honoring
  • No leakage of unauthorized resource types
Readiness metric emitted
Scope-honoring rate
Sample Data

Sample Bundles

What's Provisioned

Provider attribution Group of 50 members across two specialties, with 12 months of clinical and claims data; designed to exercise full and delta exports.

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 Provider Access 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 PDex Provider Access IG and Bulk Data v2.0.0, export latency distribution, scope-honoring report.

Readiness Metrics Emitted

  • Export latency: Wall-clock time from $export kickoff to manifest available.
  • Attribution accuracy: Match between attributed Group membership and the plan's source-of-truth attribution roster.
  • Scope-honoring rate: Share of exports returning only resource types the provider was authorized for.
Related APIs

The Other CMS-0057-F APIs

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 PAS IG latest published

Prior Authorization API

Plans and providers submit, inquire, and act on PA decisions across UM vendors and internal review queues.

View Prior Authorization 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 Provider Access 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.