Light DTR EHR

Da Vinci - Documentation Templates and Rules
2.2.0-snapshot - STU 2.2 - Peer Review 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-snapshot 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: Light DTR EHR - USCDI 3 & 4

Official URL: http://hl7.org/fhir/us/davinci-dtr/CapabilityStatement/light-dtr-ehr-700				Version: 2.2.0-snapshot	Highlight text changes?
Standards status: Trial-use Active as of 2026-02-04				Maturity Level: 2	Computable Name: LightDTREHR

This statement defines the expected capabilities of EHRs that rely on a SMART on FHIR application for USCDI 3 (US-Core 6.1) and USCDI 4 (US-Core 7.0) to handle the form filling function of DTR. This requires the server to provide access to the specified resources to allow such an app to retrieve and edit QuestionnaireResponses and related resources.

Raw OpenAPI-Swagger Definition file | Download

Language: en

Implementation Guide Version: 2.2.0-snapshot
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 Server CapabilityStatementversion: 7.0.0)

FHIR RESTful Capabilities

Mode: `server`

EHR systems which leverage a SMART app to manage data capture and rules execution, but which must be able to launch the SMART app.

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 Type	Profile	R	S	U	C	Searches
QuestionnaireResponse	Supported Profiles DTR Questionnaire Response	Y	Y	Y	Y	context, patient
Encounter	Supported Profiles CRD Encounterversion: 2.1.0)	Y
DeviceRequest	Supported Profiles CRD Device Requestversion: 2.1.0)	Y
MedicationRequest	Supported Profiles CRD Medication Requestversion: 2.1.0)	Y
NutritionOrder	Supported Profiles CRD Nutrition Orderversion: 2.1.0)	Y
CommunicationRequest	Supported Profiles CRD Communication Requestversion: 2.1.0)	Y
ServiceRequest	Supported Profiles CRD Service Requestversion: 2.1.0)	Y
VisionPrescription	Supported Profiles CRD Vision Prescriptionversion: 2.1.0)	Y
Task	Supported Profiles PAS Task	Y		Y	Y

Resource Conformance: SHALLQuestionnaireResponse

Core FHIR Resource
QuestionnaireResponse

Reference Policy

Interaction summary

SHALL support read, create, update, search-type.

Supported Profiles

DTR Questionnaire Response

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	context	`reference`	Allows retrieving QuestionnaireResponse for a context
SHALL	patient	`reference`	Allows retrieving QuestionnaireResponse for a patient