Document Templates and Rules (DTR) Testing

Document Templates and Rules (DTR)Testing with Operon

Operon exposes payer-defined Questionnaires through a FHIR endpoint that the provider EHR can fetch, pre-populate from the member's clinical record, and submit. Adaptive questionnaires use $next-question to drive iteration. The combined QuestionnaireResponse is then attached to the PAS Claim submission.

Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive)Available for TestingLast Verified 2026-05-10
Capability Matrix

What You Can Test with Us

Operon's Document Templates and Rules (DTR) capability surface vs Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive). Verified 2026-05-10.

Operon Document Templates and Rules (DTR) capability matrix vs Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive)
ResourceProfileReadSearchWriteNotes
QuestionnaireDa Vinci DTR QuestionnaireYesYesNoStandard and Adaptive variants
QuestionnaireResponseDa Vinci DTR QuestionnaireResponseYesYesYesSubmitted by provider EHR
LibraryCQL Library (referenced from Questionnaire)YesNoNo
ValueSetUS Core / Da Vinci ValueSetsYesYesNoReturned via $package
CodeSystemUS Core / Da Vinci CodeSystemsYesYesNoReturned via $package
Conformance Basis

Implementation Guide Conformance

Primary IG

Da Vinci DTR IG v2.0.1 / v2.1.0 / v2.2.0 concurrent (Standard + Adaptive) ↗Last verified 2026-05-10

Companion IGs

Authentication

OAuth 2.0 with SMART-on-FHIR launch context inherited from the CRD card. Provider EHR exchanges the launch token for a DTR access token scoped to the patient.

Supported FHIR Operations

  • GET /Questionnaire
  • GET /Questionnaire/{id}
  • POST /Questionnaire/$package
  • POST /QuestionnaireResponse
  • POST /QuestionnaireResponse/$next-question

Operon publishes a CapabilityStatement aligned to Da Vinci DTR IG. The current version ships in the Operon CMS-0057-F Testing Spec; a hosted metadata endpoint follows in v2.

Testing Scenarios

Anchor Scenarios

The exact paths your testing partners hit. Each scenario maps to a concrete request shape, expected response, conformance checkpoints, and the readiness metric Operon emits.

Scenario 1

Standard questionnaire pre-population

Trigger
CRD card launches DTR for a service requiring PA
Request
GET /Questionnaire/{id} + POST /Questionnaire/$package
Expected response
Questionnaire with pre-population extensions + bundled ValueSets / CodeSystems
Conformance checkpoints
  • DTR profile validity
  • Pre-population expression correctness
  • $package returns all referenced terminology
Readiness metric emitted
DTR pre-population coverage

Scenario 2

Adaptive questionnaire flow

Trigger
Provider EHR launches a DTR Adaptive questionnaire from a CRD card
Request
POST /QuestionnaireResponse/$next-question with partial answers
Expected response
Next question(s) based on prior answers
Conformance checkpoints
  • Adaptive flow semantics
  • Partial-response idempotency
  • Termination conditions respected
Readiness metric emitted
Adaptive flow completion rate

Scenario 3

QuestionnaireResponse submission

Trigger
Provider submits completed questionnaire
Request
POST /QuestionnaireResponse with status=completed
Expected response
201 Created with the canonical QuestionnaireResponse
Conformance checkpoints
  • QuestionnaireResponse profile validity
  • Reference integrity (questionnaire, subject, encounter)
  • Audit trail entry created
Readiness metric emitted
DTR submission success rate
Sample Data

Sample Bundles

What's Provisioned

Eight representative payer Questionnaires across medical, pharmacy, and behavioral health PA workflows. Includes both Standard (single-pass) and Adaptive (iterative) variants, each pre-populated against a synthetic member's clinical record.

Sample bundle excerpts are included in the Operon CMS-0057-F Testing Spec PDF. Full bundles are loaded into your sandbox tenant when your testing window is provisioned.

How It Works

How a Testing Window Works for Document Templates and Rules (DTR)

Step 1

Intake

Submit org type, role, this API selection, target window, and system-of-record context.

Step 2

Sandbox Tenant + Kickoff

Provisioned within 2 business days; 60-minute joint kickoff confirms scenarios, conformance targets, and success criteria.

Step 3

Testing Window + Report

1 to 4 weeks of live testing with daily conformance and latency telemetry, ending in a public-reporting-ready conformance and readiness report.

What You Get

Measurement Output

End-of-Engagement Report

Per-scenario conformance vs the Da Vinci DTR IG (Standard + Adaptive), pre-population coverage report, adaptive flow completion telemetry, and a $package terminology integrity report.

Readiness Metrics Emitted

  • DTR pre-population coverage: Percent of Questionnaire items that pre-populate successfully against the provider EHR clinical data.
  • Adaptive flow completion rate: Percent of Adaptive questionnaires that reach a valid termination state without provider abandonment.
  • DTR submission success rate: Percent of completed QuestionnaireResponses that validate and persist without rejection.
Related APIs

The Other CMS-0057-F APIs

Da Vinci PDex Provider Access IG latest published

Provider Access API

Providers under attribution agreement pull clinical, claims, and encounter data via group-based bulk export.

View Provider Access API Details →

Da Vinci PDex Payer-to-Payer IG latest published

Payer-to-Payer API

Concurrent and prior payers exchange member historical data via $member-match and historical bundle handoff.

View Payer-to-Payer API Details →

Da Vinci PAS IG latest published

Prior Authorization API

Plans and providers submit, inquire, and act on PA decisions across UM vendors and internal review queues.

View Prior Authorization API Details →

Da Vinci CRD IG v2.0.1 / v2.1.0 / v2.2.1 concurrent

Coverage Requirements Discovery (CRD)

Plans expose CDS Hooks services so a provider EHR can surface prior-authorization requirements at order entry or order-sign time, before the claim is submitted.

View Coverage Requirements Discovery (CRD) Details →
Ready to Test

Schedule a Document Templates and Rules (DTR) Testing Window

30 minutes with our team. We'll ask about the systems you already run, where you are on the CMS-0057-F calendar, and what testing you need to ship.