Da Vinci Clinical Data Exchange (CDex), published by HL7 International / Payer/Provider Information Exchange Work Group. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-ecdx/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-pwk01-attachment-report-type-code | Version: 2.1.0 | |||
Standards status: Trial-use | Maturity Level: 2 | Computable Name: CDexPWK01AttachmentReportTypeCodeValueSet | ||
Other Identifiers: http://loinc.org#Logical Observation Identifier Names and Codes (LOINC)#valid-hl7-attachment-requests, OID:1.3.6.1.4.1.12009.10.2.6 | ||||
Copyright/Legal: All X12 work products are copyrighted. Any use of any X12 work product must be compliant with US Copyright laws and X12 Intellectual Property policies. Please see https://x12.org/products/licensing-program |
In addition to using LOINC attachment codes, a payer may request for additional information from the provider to support a prior authorization request using X12's PWK01 Attachment Report Type Code.
Note that the PWK01 codes will not be published in due to X12 IP restrictions.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet cdex-pwk01-attachment-report-type-code
https://codesystem.x12.org/005010/755
No Expansion for this valueset (Unknown Code System)
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 |