The Prior Authorization Solution is composed of three main modules with additional dependencies:
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.
order-sign)Questionnaire/$questionnaire-packageQuestionnaire/$next-questionQuestionnaire/$log-questionnaire-errorsClaim/$submitClaim/$inquireClaimResponse/$sdh.pa.submitMost 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.
| Operation | Module | Camel Route |
|---|---|---|
CDS Hooks service call (e.g. order-sign) | CRD | direct:start-crd |
Questionnaire/$questionnaire-package | PAS | direct:start-questionnaire-package |
Questionnaire/$next-question | PAS | direct:start-next-question |
Questionnaire/$log-questionnaire-errors | PAS | direct:log-questionnaire-errors |
Claim/$submit | PAS | direct:start-pas-submit |
Claim/$inquire | PAS | direct: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.
Questionnaire/$questionnaire-packageQuestionnaire/$next-questionQuestionnaire/$log-questionnaire-errorsQuestionnaire/$populateThe Prior Authorization Solution is built on HL7 FHIR R4 and leverages the following Da Vinci Implementation Guides (IGs):
This standards-based approach ensures interoperability between payer and provider systems, supporting secure, real-time communication and regulatory compliance.
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 Guide | Versions | Version-specific behavior in Smile |
|---|---|---|
| Da Vinci CRD (STU 2.1, STU 2.2) | 2.1, 2.2 | Each 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.2 | PAS 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. |
You are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.