Da Vinci - Documentation Templates and Rules
2.2.0 - STU 2.2

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: DTR Payer Service

Official URL: http://hl7.org/fhir/us/davinci-dtr/CapabilityStatement/dtr-payer-service | Version: 2.2.0 | Highlight text changes?
Standards status: Trial-use Active as of 2026-02-04 | Maturity Level: 2 | Computable Name: DTRPayerService

This capability statement defines the expected capabilities of payer systems that provide questionnaires to DTR clients. Such systems need only support server capabilities for the Questionnaire Package, ValueSet Expand, and Next Question operations.

Raw OpenAPI-Swagger Definition file | Download

Language: en

## DTR Payer Service

- 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.

## FHIR RESTful Capabilities

### Mode: `server`

A DTR Payer service provides a service endpoint for DTR apps and full EHRs to connect to

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 | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Questionnaire |  |  |  |  |  |  |  |  | `$questionnaire-package`, `$next-question`, `$log-questionnaire-errors`
ValueSet |  |  |  |  |  |  |  |  | `$expand`

#### Resource Conformance: unspecifiedQuestionnaire

Core FHIR Resource
Questionnaire
Reference Policy
Interaction summary

Extended Operations

Conformance | Operation | Documentation
--- | --- | ---
SHALL | $questionnaire-package |
SHALL | $next-question |
SHALL | $log-questionnaire-errors |

#### Resource Conformance: unspecifiedValueSet

Core FHIR Resource
ValueSet
Reference Policy
Interaction summary

Extended Operations

Conformance | Operation | Documentation
--- | --- | ---
SHALL | $expand |