Render and complete a Da Vinci DTR SMART app Questionnaire within an EHR context
domain: hl7.org/fhir/us/davinci-dtr · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Launch the DTR SMART app from the EHR using the SMART App Launch context carrying the order and coverage resource references
Retrieve the payer-supplied Questionnaire resource referenced in the CRD card or DTR context, including any associated Library resources containing CQL logic
Execute the CQL expressions embedded in the Questionnaire to pre-populate QuestionnaireResponse answers from available EHR data, reducing clinician burden
Render remaining unanswered questions to the clinician for manual completion
POST the completed QuestionnaireResponse to the EHR FHIR server and signal completion so the EHR can proceed with prior authorization or ordering
Known gotchas
DTR Questionnaires reference CQL libraries by canonical URL; the app must resolve those libraries from the payer's endpoint, and network restrictions or expired tokens cause silent pre-population failures
QuestionnaireResponse.authored and QuestionnaireResponse.author are expected by downstream PAS operations; omitting them breaks the handoff
CQL evaluation may access patient data via the EHR FHIR endpoint using the launch context token; ensure the SMART scopes granted at launch cover every resource type the CQL queries
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?