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

This page is part of the Documentation Templates and Rules (v2.2.0-ballot: STU 2.2 Ballot) based on FHIR (HL7® FHIR® Standard) R4. This version is a pre-release. The current official version is 2.1.0. For a full list of available versions, see the Directory of published versions

CodeSystem: DTR Intended Audience Codes

Official URL: http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes Version: 2.2.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: DTRIntendedAudience

Codes defining audience of additional documentation to be captured.

This Code system is referenced in the content logical definition of the following value sets:

This case-sensitive code system http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes defines the following codes in a Is-A hierarchy:

CodeDisplayDefinition
clinical Clinical Documentation Details most likely to originate from a clinician are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by clinician. Indicates that the CRD client should expose the need to launch DTR to clinical users.
admin Administrative Documentation Administrative details not likely to require clinical expertise are needed to satisfy additional documentation requirements, determine coverage and/or prior auth applicability - e.g. via DTR by back-end staff. Indicates that while the CRD client might expose the ability to launch DTR as an option for clinical users, it should be clear that clinical input is not necessary and deferring the use of DTR to back-end staff is perfectly appropriate. Some CRD clients might be configured (based on provider preference) to not even show clinicians the option to launch.
patient Patient Documentation Details most likely to originate from the patient or their personal representative (e.g. parent, spouse, etc.) are required to satisfy additional documentation requirements, determine coverage and/or prior auth applicability. For example, information about household composition, accessibility considerations, etc. This should be used when the data needs to come from the patient themselves, rather than a clinician's assessment of the patient