Da Vinci Documentation Templates and Rules FHIR Implementation Guide
DTR lets payers express documentation requirements computably and allows provider systems or SMART applications to retrieve existing clinical data, prompt for missing information, and create structured responses for downstream authorization or claims workflows.
What the authority record establishes
DTR lets payers express documentation requirements computably and allows provider systems or SMART applications to retrieve existing clinical data, prompt for missing information, and create structured responses for downstream authorization or claims workflows.
Technical specification; becomes required where adopted by regulation, contract, program, or trading-partner agreement
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
DTR addresses one of the principal causes of authorization delay: incomplete or incorrectly structured clinical information. Buyers should evaluate computable policy governance and user review, not only form rendering.
Affected operating stages
- Documentation Requirement Retrieval
- Clinical Data Extraction
- Questionnaire Completion
- Provider Review
- Supporting Information Packaging
Capabilities to examine
Clinical Documentation Assembly
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for clinical documentation assembly.
Clinical Criteria Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for clinical criteria management.
FHIR CRD, DTR, And PAS Interoperability
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FHIR CRD, DTR, and PAS interoperability.
Audit Trail And Decision Provenance
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail and decision provenance.
Affected buyer audiences
- payers and medical-policy teams
- EHR and clinical workflow vendors
- provider authorization teams
- CQL and knowledge-engineering teams
- ePA coordinators
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
Prior Auth Monitor does not provide patient-specific medical advice, determine coverage, authorize care, or establish final payment. Its records support organizational research and operating review.