This page is part of the Documentation Templates and Rules (v2.2.0: STU 2.2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
| Official URL: http://hl7.org/fhir/us/davinci-dtr/ValueSet/questionnaireAudience | Version: 2.2.0 | ||||
| Standards status: Trial-use Active as of 2026-03-27 | Maturity Level: 1 | Computable Name: DTRAudience | |||
Codes defining audience of additional documentation to be captured
References
http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes version 📦2.2.0| Code | Display | Definition |
| 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 |
Expansion performed internally based on codesystem DTR Intended Audience Codes v2.2.0 (CodeSystem)
This value set contains 3 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes | 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. | ||
http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes | 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. | ||
http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes | 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 |