Da Vinci - Documentation Templates and Rules
2.2.0 - STU 2.2 United States of America flag

Da Vinci - Documentation Templates and Rules, published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 2.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-dtr/ and changes regularly. See the Directory of published versions

CapabilityStatement: Full DTR EHR - USCDI 3 & 4

Official URL: http://hl7.org/fhir/us/davinci-dtr/CapabilityStatement/full-dtr-ehr-700 Version: 2.2.0
Standards status: Trial-use Active as of 2026-02-04 Maturity Level: 2 Computable Name: FullDTREHR

This statement defines the expected capabilities of EHRs that manage the form filling functions of DTR internally for USCDI 3 (US-Core 6.1) and USCDI 4 (US-Core 7.0). Such EHRs need only support client capabilities for the Questionnaire Package, ValueSet Expand, and Next Question operations.

Raw OpenAPI-Swagger Definition file | Download

Language: en

Full DTR EHR

  • Implementation Guide Version: 2.2.0
  • FHIR Version: 4.0.1
  • Supported Formats: json
  • Published on: 2026-02-04
  • Published by: HL7 International / Clinical Decision Support

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement imports the CapabilityStatement US Core Client CapabilityStatementversion: 7.0.0)

FHIR RESTful Capabilities

Mode: client

A DTR Native Client provides an EHR-based application

Security

Implementations SHALL meet the general security requirements documented in the HRex implementation guide.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
Questionnaire $questionnaire-package, $next-question, $log-questionnaire-errors
ValueSet $expand
Core FHIR Resource
Questionnaire
Reference Policy
Interaction summary

    Extended Operations
    ConformanceOperationDocumentation
    SHALL$questionnaire-package
    SHALL$next-question
    SHALL$log-questionnaire-errors
    Core FHIR Resource
    ValueSet
    Reference Policy
    Interaction summary

      Extended Operations
      ConformanceOperationDocumentation
      SHALL$expand