Operon exposes CDS Hooks services for provider EHR systems so that prior-authorization requirements surface at order-entry or order-sign time. We orchestrate the underlying coverage and policy decision across the plan's UM and benefits systems and return a conformant CDS card.
Operon's Coverage Requirements Discovery (CRD) capability surface vs Da Vinci CRD IG v2.0.1 / v2.1.0 / v2.2.1 concurrent. Verified 2026-05-10.
| Resource | Profile | Read | Search | Write | Notes |
|---|---|---|---|---|---|
| order-select | Da Vinci CRD CDS Hook | Yes | No | No | Fires as a clinician selects an order |
| order-sign | Da Vinci CRD CDS Hook | Yes | No | No | Fires at order-sign time |
| appointment-book | Da Vinci CRD CDS Hook | Yes | No | No | Fires at appointment booking |
| CDS Card | Da Vinci CRD Card | Yes | No | No | Response from a hook invocation |
Primary IG
Companion IGs
Authentication
OAuth 2.0 client-credentials flow between provider EHR and the plan CDS service. CDS Hooks 1.0 + SMART discovery model.
Supported FHIR Operations
GET /cds-servicesPOST /cds-services/{service-id} Operon publishes a CapabilityStatement aligned to Da Vinci CRD IG. The current version ships in the Operon CMS-0057-F Testing Spec; a hosted metadata endpoint follows in v2.
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
POST /cds-services/{service-id} with hook payload (patient, practitioner, draft order)Scenario 2
POST /cds-services/{service-id} for order-sign hookScenario 3
POST /cds-services/{service-id} for order-select hookWhat's Provisioned
Six representative order scenarios spanning medical, pharmacy, and behavioral health categories. Each scenario covers a member in good standing and exercises both the 'PA required' and 'PA not required' decision paths.
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.
Step 1
Submit org type, role, this API selection, target window, and system-of-record context.
Step 2
Provisioned within 2 business days; 60-minute joint kickoff confirms scenarios, conformance targets, and success criteria.
Step 3
1 to 4 weeks of live testing with daily conformance and latency telemetry, ending in a public-reporting-ready conformance and readiness report.
End-of-Engagement Report
Per-scenario conformance vs the Da Vinci CRD IG, hook response latency distribution, CRD-to-DTR handoff verification, and a CDS Card profile validation report.
Readiness Metrics Emitted
CARIN BB IG v2.0.0
Members access their claims, EOBs, encounters, and clinical data through authorized apps.
View Patient Access API Details →Da Vinci PDex Provider Access IG latest published
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
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
Plans and providers submit, inquire, and act on PA decisions across UM vendors and internal review queues.
View Prior Authorization API Details →Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive)
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 →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.