Top 5 SDC Form Engines for Prior Authorization Workflows

A prior authorization workflow on FHIR runs SDC Questionnaires at the boundary between provider and payer, with the Da Vinci Documentation Templates and Rules IG providing the spec-aligned shape. The form engine underneath has to honor SDC behaviors, route the QuestionnaireResponse into the prior-auth Claim or Communication that the payer expects, and stay current with the Da Vinci roster updates. The five engines below cover the realistic options for prior authorization in 2026. For broader context, see the FHIR integration playbook.

The 5 SDC Form Engines to Know

LHC-Forms with Da Vinci Adapter. The NLM renderer paired with a community-maintained adapter that maps the Documentation Templates and Rules profile into LHC-Forms behavior. Where it shines is the conformance and zero-license cost; where it falls short is the adapter's maintenance velocity, which trails the Da Vinci IG by a release or two.

Smile Digital Health Da Vinci Forms. A managed Documentation Templates and Rules surface backed by Smile CDR with explicit prior-auth workflow integration. The right answer for payers and providers that want the IG-aligned path under a vendor support contract.

Medplum Forms with Bot-Driven Auth Routing. A typed Questionnaire implementation paired with TypeScript bots that handle the QuestionnaireResponse to Claim mapping and the payer-side routing. Useful when the engineering team wants a short loop between form change and routing change.

Cohere Unify with SDC Profile. A managed prior-authorization platform with a Questionnaire surface aligned to Da Vinci. Strong fit for payers running prior-auth volumes that justify a dedicated platform rather than a generic form engine.

Aidbox Forms with Payer Tenancy. A multi-tenant FHIR-native form layer that suits the third-party administrator pattern, where one platform serves multiple payer clients and each client's Da Vinci roster stays isolated.

Prior-auth workflows on SDC overlap with remote patient monitoring Questionnaires when the authorization decision depends on monitored data. The FHIR form builders for remote patient monitoring roundup covers that adjacent surface in detail.

How to Pick the Right Engine

Three questions narrow the field. The first is whether the deployment is on the payer side, the provider side, or a third-party administrator. Payer-side deployments value the workflow integration and the IG-aligned routing. Provider-side deployments value the renderer and the clinician-facing fidelity. Third-party administrators need both, plus tenant isolation.

The second is the Da Vinci IG version commitment. Programs aligned to the current published version can lean on the managed options because the vendors keep their adapters current. Programs aligned to the ballot pre-release version need source-visible engines that can be patched against the ballot text.

The third is the migration shape. Programs replacing fax-and-PDF prior auth with SDC need different engines than programs replacing one SDC implementation with another. The SDC questionnaires vs static PDF forms comparison covers the fax-and-PDF migration trade-off where the renderer's PDF-rendering fidelity matters most.

A working prior-authorization SDC engine fades into the background of the workflow. The wrong one produces forms that the payer cannot accept and provider workflows that revert to fax under deadline pressure. Selection ends up matching the engine's strengths to the deployment role, the IG version, and the migration shape, not to the longest feature checklist on a vendor matrix.