Da Vinci Clinical Data Exchange (CDex)
2.1.0-preview - CI Build United States of America flag

Da Vinci Clinical Data Exchange (CDex), published by HL7 International - Patient Care Work Group. This is not an authorized publication; it is the continuous build for version 2.1.0-preview). This version is based on the current content of https://github.com/HL7/davinci-ecdx/ and changes regularly. See the Directory of published versions

ValueSet: CDex Attachment Task Code Value Set

Official URL: http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-attachment-task-code Version: 2.1.0-preview
Standards status: Draft Maturity Level: 1 Computable Name: CDexAttachmentTaskCode

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

Codes used to identify the type of attachment request and control the payer system’s behavior.

References

Logical Definition (CLD)

 

Expansion

This value set contains 2 concepts

Expansion based on CDex Temporary Code System v2.1.0-preview (CodeSystem)

CodeSystemDisplayDefinition
  attachment-request-codehttp://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-tempCoded Attachment Request

A Task by a Payer requesting attachments for a Provider claim or prior-authorization using LOINC attachment codes.

  attachment-request-questionnairehttp://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-tempAttachment Request Questionnaire

A Task by a Payer requesting attachments or additional data for a Provider claim or prior-authorization using a data request questionnaire (FHIR Questionnaire).


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