Da Vinci Clinical Data Exchange (CDex)
1.0.0 - STU R1 US

This page is part of the Da Vinci Clinical Documentation Exchange (v1.0.0: STU1) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions

ValueSet: CDex Attachment Reason Value Set

Official URL: http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-attachment-reason Version: 1.0.0
Draft as of 2021-12-03 Computable Name: CDexAttachmentReasonValueSet

Copyright/Legal: Used by permission of HL7 International all rights reserved Creative Commons License

The set of codes is used in the $submit-attachment operation for identifying the reason for attachments

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
    CodeDisplayDefinition
    claimClaimA provider issued list of professional services and products which have been provided to a patient which is sent to an insurer for reimbursement.
    prior-authorizationPrior AuthorizationRequest for data from payers as part of a prior authorization requests from EHR systems. If authorization is required and documentation is necessary to substantiate the need for the service, the specific documentation is requested. The documentation may take the form of attestations by the provider, diagnoses, results of specific diagnostic tests, prior treatment that has been tried and failed, specific studies that need to be performed and other specific documentation such as progress notes or discharge summaries.

 

Expansion

This value set contains 2 concepts

Expansion based on CDex Temporary Code System v1.0.0 (CodeSystem)

All codes in this table are from the system http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp

CodeDisplayDefinition
  claimClaimA provider issued list of professional services and products which have been provided to a patient which is sent to an insurer for reimbursement.
  prior-authorizationPrior AuthorizationRequest for data from payers as part of a prior authorization requests from EHR systems. If authorization is required and documentation is necessary to substantiate the need for the service, the specific documentation is requested. The documentation may take the form of attestations by the provider, diagnoses, results of specific diagnostic tests, prior treatment that has been tried and failed, specific studies that need to be performed and other specific documentation such as progress notes or discharge summaries.

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