Written and maintained by CASRAI Editorial Board
Last updated
Da Vinci FHIR (officially the HL7 Da Vinci Project) is the flagship payer-provider collaborative within the HL7 FHIR Accelerator Program, dedicated to authoring normative and STU HL7 FHIR R4 Implementation Guides (IGs) for value-based care, administrative burden reduction, and clinical data exchange. Together with sibling HL7 FHIR Accelerators—most notably the CARIN Alliance (CARIN Blue Button) and the FHIR at Scale Taskforce (FAST)—the Da Vinci IGs form the federally referenced technical architecture for the CMS-0057-F Interoperability and Prior Authorization Final Rule.
What Is the HL7 Da Vinci Project and the HL7 FHIR Accelerator Program?
The HL7 FHIR Accelerator Program is an initiative within Health Level Seven International (HL7) that enables domain-specific industry coalitions to fund, author, ballot, and pilot FHIR Implementation Guides on an accelerated cycle; the HL7 Da Vinci Project is the accelerator governing payer-to-provider and payer-to-payer workflows.
Whereas the base HL7 FHIR R4 specification provides general-purpose global building blocks (`Patient`, `Observation`, `Claim`, `Task`), real-world production interoperability requires constrained profiles, terminology bindings, and custom operations (`$submit`, `$member-match`, `$export`). The HL7 FHIR Accelerator Program addresses this across specialized domain communities:
- HL7 Da Vinci Project (Payer-Provider & Value-Based Care): Publishes more than 15 FHIR R4 Implementation Guides covering prior authorization automation (CRD, DTR, PAS), clinical/payer data exchange (PDex, CDex), quality reporting (DEQM, Gaps in Care), member attribution (ATR), and price transparency (PCT).
- CARIN Alliance (Consumer-Directed Claims & Blue Button): Standardizes consumer access to adjudicated health plan claims via the CARIN IG for Blue Button® and real-time pharmacy benefit checks.
- HL7 FAST — FHIR at Scale Taskforce (National Infrastructure): Originally convened by the Office of the National Coordinator for Health IT (ONC / ASTP), FAST standardizes cross-accelerator infrastructure: scalable OAuth 2.0 / UDAP security, a National Healthcare Directory, cross-network patient identity matching (`$match`), and intermediary routing.
- Research & Specialty Accelerators: Complemented by CodeX (oncology mCODE and radiation/cardiovascular registries), Vulcan (translational and clinical research EHR-to-EDC), Argonaut (core EHR US Core / SMART on FHIR), and Helios (public health surveillance).
How Do Da Vinci CRD, DTR, and PAS Automate Prior Authorization Using FHIR?
The Da Vinci “Burden Reduction” triad—Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS)—links EHR order entry to payer utilization management engines in a continuous three-step FHIR pipeline.
In prior authorization software and CMS-0057-F compliant payer gateways, CRD, DTR, and PAS execute sequentially within the clinician’s ordering workflow:
| Da Vinci IG | Trigger & Protocol | Core FHIR Resources & Operations | Clinical & Administrative Output |
|---|---|---|---|
| 1. CRD (Coverage Requirements Discovery) | Triggered synchronously via CDS Hooks (order-select, order-sign, appointment-book) |
CDS Hooks request payload containing Patient, Coverage, and draft ServiceRequest or MedicationRequest prefetch resources. |
Returns JSON CDS Cards indicating whether PA is required, not required, or conditional, plus a link to launch DTR. |
| 2. DTR (Documentation Templates and Rules) | Launched from the CRD card as a SMART on FHIR app or native EHR questionnaire engine | Questionnaire, QuestionnaireResponse, and Clinical Quality Language (CQL) Library resources via $questionnaire-package. |
Executes CQL rules against the EHR’s FHIR server to auto-populate labs, diagnoses, and prior therapies; prompts clinician only for missing items. |
| 3. PAS (Prior Authorization Support) | Submitted directly from the EHR to the payer’s FHIR PAS endpoint | POST [base]/Claim/$submit (or Claim/$inquire) carrying a FHIR Bundle with Claim (use = "preauthorization") and DTR attachments. |
Translates to/from ASC X12N 278 where required under HIPAA and returns a FHIR ClaimResponse (approved, pended, or denied with specific reasons). |
Beyond Prior Auth: Da Vinci PDex, CDex, DEQM, and PCT
In addition to the CRD/DTR/PAS triad, the Da Vinci portfolio standardizes four major operational data flows between payers and providers:
- PDex (Payer Data Exchange): Powers the CMS-0057-F Provider Access API and Payer-to-Payer API. PDex uses the
$member-matchoperation (matching demographics and coverage) and Bulk FHIR ($export) or$everythingto transfer a member’s longitudinal USCDI clinical history and active prior authorizations when they switch health plans or see an in-network clinician. - CDex (Clinical Data Exchange): Eliminates manual chart-pull faxes by defining three mechanisms for payers and providers to exchange clinical documentation: direct FHIR RESTful queries,
Task-driven requests (including CQL questionnaire queries), and unsolicited attachment submissions via$submit-attachment. - DEQM (Data Exchange for Quality Measures) & ATR (Member Attribution): Standardizes value-based care roster synchronization (`Group` resource in ATR) and automated HEDIS/eCQM quality reporting (`MeasureReport` and `$submit-data` in DEQM).
- PCT (Patient Cost Transparency): Enables multi-provider Good Faith Estimates (GFEs) and Advanced Explanations of Benefits (AEOBs) using FHIR `Bundle`, `Claim` (`use = “predetermination”`), and `ClaimResponse` resources under the No Surprises Act.
What Is the CARIN Blue Button Implementation Guide?
The CARIN Implementation Guide for Blue Button® (`http://hl7.org/fhir/us/carin-bb/`) is the HL7 FHIR R4 standard that maps the Common Payer Consumer Data Set (CPCDS) onto five specialized `ExplanationOfBenefit` (EOB) profiles so members can retrieve their adjudicated insurance claims via consumer apps.
While US Core covers clinical EHR records, clinical EHRs lack complete adjudicated financial and cross-facility pharmacy claims. To satisfy the CMS Patient Access API (`42 CFR § 422.119`), health plans implement the CARIN Blue Button IG, which structures claims around five distinct **`ExplanationOfBenefit`** profiles:
- CARIN BB Inpatient Institutional EOB Profile: Captures acute inpatient facility claims (historically billed on UB-04 / ASC X12 837I), including MS-DRG/APR-DRG codes, admission/discharge dates, revenue center codes, ICD-10-PCS procedure codes, and present-on-admission (POA) indicators.
- CARIN BB Outpatient Institutional EOB Profile: Captures hospital outpatient department, emergency room, and ambulatory facility claims with revenue codes and HCPCS/CPT line items.
- CARIN BB Professional and Non-Clinician EOB Profile: Captures physician, specialist, and durable medical equipment (DME) claims (historically billed on CMS-1500 / ASC X12 837P), including place-of-service (POS) codes, rendering/billing NPIs, CPT/HCPCS modifiers, and allowed/copay/coinsurance amounts.
- CARIN BB Pharmacy EOB Profile: Captures retail and mail-order prescription fills (NCPDP Telecommunications Standard), including 11-digit National Drug Codes (NDCs), days supply, quantity dispensed, refill numbers, and generic/brand indicators.
- CARIN BB Oral EOB Profile: Captures dental claims coded with ADA Current Dental Terminology (CDT) codes, tooth numbers, and oral cavity surface designations.
How the HL7 FAST (FHIR at Scale Taskforce) Solves Enterprise Scalability
The HL7 FAST Accelerator provides the four infrastructure Implementation Guides required to scale Da Vinci and CARIN APIs across thousands of payers and health systems without manual point-to-point onboarding:
- FAST Security (UDAP Tiered OAuth & Dynamic Client Registration): Uses Unified Data Access Profiles (UDAP, RFC 7591 extensions, and X.509 certificate trust communities) so client applications can register and authenticate dynamically across thousands of FHIR endpoints without manual developer portal approval at every hospital or payer.
- FAST National Directory of Healthcare Providers & Services (NDH): Defines a national validated FHIR R4 directory of `Organization`, `Practitioner`, `PractitionerRole`, `HealthcareService`, and `Endpoint` resources so EHRs can programmatically discover which CRD/DTR/PAS endpoint belongs to a patient’s health plan.
- FAST Interoperable Digital Identity & Patient Matching: Standardizes input data quality weights and the FHIR `$match` operation to achieve deterministic and probabilistic patient matching across payer-to-payer and provider-to-payer transactions.
- FAST Hybrid / Intermediary Exchange: Defines HTTP routing headers and provenance rules when FHIR API calls traverse clearinghouses, HIEs, or TEFCA Qualified Health Information Networks (QHINs) between an origin EHR and a destination payer server.
