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

ValueSet: Audience Value Set

Official URL: http://hl7.org/fhir/us/davinci-dtr/ValueSet/questionnaireAudience Version: 2.2.0-ballot
Standards status: Trial-use Maturity Level: 1 Computable Name: DTRAudience

Codes defining audience of additional documentation to be captured

References

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codes
    CodeDisplayDefinition
    clinicalClinical DocumentationDetails 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.
    adminAdministrative DocumentationAdministrative 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.
    patientPatient DocumentationDetails 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

Expansion performed internally based on codesystem DTR Intended Audience Codes v2.2.0-ballot (CodeSystem)

This value set contains 3 concepts

CodeSystemDisplay (en-US)Definition
  clinicalhttp://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codesClinical DocumentationDetails 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.
  adminhttp://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codesAdministrative DocumentationAdministrative 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.
  patienthttp://hl7.org/fhir/us/davinci-dtr/CodeSystem/dtr-intendedaudience-codesPatient DocumentationDetails 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

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code