The Documentation Templates and Rules (DTR) component of Da Vinci ePA lives or dies on the SMART App Launch experience inside the provider EHR. The provider does not pause to log into a payer portal; the DTR SMART app has to launch in context, render the payer-specific Questionnaire, run the CQL rules quietly, and return a completed Bundle ready for PAS submission. Six tools handle this layer well in 2026, and the differences between them matter a lot to provider adoption. For broader context, the CMS interop knowledge base is the entry point on this site for the standards-side picture.
1. Logica Health SMART Sandbox
Logica Health (the rebrand of the SMART Health IT project at Boston Children's) runs the canonical SMART App Launch sandbox. The reference tooling is open-source, well-maintained, and the conformance suite is the bar everyone else measures against. Payer dev teams building DTR SMART apps usually start here for testing, then move to a production-grade host.
2. Cerner Open Developer Experience (CODE)
Cerner CODE remains the largest installed base for SMART App Launch in US EHRs. The platform supports both Standalone and EHR Launch flows, with the certification process around production deployment well-documented. Payer-built DTR apps target CODE early in the rollout. The trade-off is the certification timeline; submitting a new SMART app to Cerner App Gallery is a multi-month process.
3. Epic App Orchard
Epic App Orchard is the equivalent for Epic-installed health systems. The SMART App Launch flow on Epic is conformant and stable, with the same kind of certification gate as Cerner CODE. The Epic-specific quirks (vendor scopes, sandbox tenant management) require attention during DTR rollout but are well-documented.
4. 1upHealth Developer Platform
1upHealth provides a SMART App Launch hosting layer that fits payers building DTR SMART apps without standing up their own SMART server. The platform handles OAuth, scopes, app registration, and the launch URL flow. The strength is developer ergonomics; the trade-off is that the platform is a managed dependency rather than an in-house build.
5. Smile CDR SMART Module
Smile Digital Health bundles a SMART App Launch module inside Smile CDR. Payers running Smile for the FHIR backbone often run DTR SMART apps off the same instance, which simplifies consent, audit, and access control. The unified deployment is the main appeal.
6. Microsoft Cloud for Healthcare (FHIR Service)
Microsoft Cloud for Healthcare ships SMART App Launch as part of the Azure FHIR service. For payers that already run on Azure, the integration is clean and the operational model fits existing Microsoft tooling. The community of DTR SMART apps targeting Microsoft FHIR is smaller than the Smile or 1upHealth ecosystems, which matters more in 2026 as DTR app reuse becomes common.
What Makes a SMART App Launch Implementation Good in 2026
The differences across these six tools come down to three operational dimensions. First, launch reliability: how often the SMART app fails to start inside the provider EHR (a common failure mode in early ePA rollouts). Second, scope and consent flow: how cleanly the payer-specific data access scopes are negotiated without confusing the clinician. Third, fallback behavior: what happens when the SMART app cannot launch (degraded experience versus complete failure).
A useful test during evaluation is to load the DTR SMART app inside three different provider EHRs and one mobile EHR client. The failures cluster around context handoff (Patient and Encounter resources not arriving cleanly), which exposes implementation gaps that demos hide.
How This Ties Into the Rest of the Stack
The DTR SMART app is the provider-facing front door, but the work behind it is the CQL engine evaluating coverage rules. The two pieces have to work together cleanly; a fast SMART app paired with a slow CQL engine produces a frustrating provider experience.
For the rule-engine side of this picture, the Top 5 CQL Engines for Medical Necessity Decisions in Prior Auth covers the runtime layer. For the real-time notification flow back to the EHR after decision, the FHIR Subscription engines for real-time Prior Auth decisions closes the loop.