Solution Modules

 

Primary Modules

The Prior Authorization Solution is composed of three main modules with additional dependencies:

Module Overview

The CRD and PAS modules provide the APIs, orchestration and request routing for the CRD, DTR and PAS APIs. These modules do not implement the actual rules. A fully operational solution requires integration with back end systems provided by the Payer or optionally implemented using modules such as CQL backed DTR. The CRD and PAS modules include an embedded Camel component. This component is responsible for routing the incoming API calls to the appropriate back end endpoints. The Camel component can also invoke custom Processors to enable translation such as X12 to FHIR.

  • Coverage Requirements Discovery (CRD): The CRD operation determines whether a prior authorization is required for a service or procedure. This helps providers avoid unnecessary requests, reduces administrative overhead, and ensures compliance with payer requirements.
    • The CRD Module works in conjunction with the CDS Hooks module. The CRD operation is actually a CDS Hooks call. When the CRD Module starts, it registers itself as a handler for certain types of hooks (e.g. order-sign)
  • Prior Authorization Submission (PAS):
    • This module requires a FHIR Endpoint and a FHIR Repository
    • The PAS Module registers the following operations
      • DTR Related (registered by the PAS module so that a single module on the payer's FHIR endpoint serves both the DTR and PAS APIs; the routes can forward them to a backend such as the CQL Backed DTR module):
        • Questionnaire/$questionnaire-package
        • Questionnaire/$next-question
        • Questionnaire/$log-questionnaire-errors
      • PAS Related:
        • Claim/$submit
        • Claim/$inquire
        • ClaimResponse/$sdh.pa.submit
  • DaVinci Data Exchange
    • In the context of Prior Auth this module supplies the $submit-attachment operation used by Providers to upload additional information after a Prior Auth request is submitted.

Camel Routes

Most operations are dispatched to a Camel route in the module's embedded Camel component. The payer configures each route in the module's routes script to call its backend systems or the provided Camel Processors.

OperationModuleCamel Route
CDS Hooks service call (e.g. order-sign)CRDdirect:start-crd
Questionnaire/$questionnaire-packagePASdirect:start-questionnaire-package
Questionnaire/$next-questionPASdirect:start-next-question
Questionnaire/$log-questionnaire-errorsPASdirect:log-questionnaire-errors
Claim/$submitPASdirect:start-pas-submit
Claim/$inquirePASdirect:start-pas-inquire

ClaimResponse/$sdh.pa.submit is not routed through Camel. The PAS module validates the PAS Response Bundle, stores it in the FHIR Repository, and creates a CDex Task when more information is needed from the provider. See the PAS module reference. The $log-questionnaire-errors operation also stores the submitted OperationOutcome in the FHIR Repository before calling its route.

See Setup Prior Auth for Payers for example routes.

Supporting Modules

  • CQL Backed DTR (Documentation Templates and Rules (Formerly known as DTR Module)
    • This module allows for implementation of Prior Auth rules and documentation requirements using our CQIS suite. From the perspective of the overall Prior Auth deployment this module should be treated as a backend system invoked by the Camel coordination layer in one of the main modules
    • It supports the following operations (see Prior Auth DTR Module Overview):
      • Questionnaire/$questionnaire-package
      • Questionnaire/$next-question
      • Questionnaire/$log-questionnaire-errors
      • Questionnaire/$populate

Standards & Technology

 

The Prior Authorization Solution is built on HL7 FHIR R4 and leverages the following Da Vinci Implementation Guides (IGs):

  • Da Vinci Coverage Requirements Discovery (CRD)
  • Da Vinci Documentation Templates and Rules (DTR)
  • Da Vinci Prior Authorization Support (PAS)

This standards-based approach ensures interoperability between payer and provider systems, supporting secure, real-time communication and regulatory compliance.

Supported Implementation Guide Versions

The Prior Auth modules support STU 2.1 and STU 2.2 of the Da Vinci CRD, DTR and PAS Implementation Guides. Smile provides the operations, Camel routing and helper processors; the content of cards, Questionnaires and prior authorization responses comes from the Camel routes and the back end engines you configure, so conformance to a specific IG version depends on that configuration.

Implementation GuideVersionsVersion-specific behavior in Smile
Da Vinci CRD (STU 2.1, STU 2.2)2.1, 2.2Each CDS Hook declares its version with the davinci-crd.version extension (see CDS Hook Definitions). Prefetch templates support FHIRPath expressions, including the STU 2.2 order-dispatch prefetch on context.dispatchedOrders. The order-dispatch context is accepted in both its STU 2.1 and STU 2.2 forms.
Da Vinci DTR (STU 2.1, STU 2.2)2.1, 2.2$questionnaire-package, $next-question and $log-questionnaire-errors accept the request and response parameter names of both versions, for example PackageBundle and packagebundle. See the DTR API tutorial for the parameters that differ between versions.
Da Vinci PAS (STU 2.1, STU 2.2)2.1, 2.2PAS profiles are referenced without a version, and the ClaimResponse content comes from the PAS Camel routes. Limitations: $inquire returns a single inquiry response Bundle, while STU 2.2 allows zero or more. CDex flow only: when a pended response from Claim/$submit or ClaimResponse/$sdh.pa.submit requests more information, PAS creates a CDex Task, and the Task gets the serviceLineNumber extension only from CommunicationRequest.payload (STU 2.1). A serviceLineNumber at the top level of the CommunicationRequest (STU 2.2) is not copied to the Task.