Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
US Da Vinci CDex (FHIR)
-
2.0.0
-
Payer/Provider Information Exchange
-
CDex Task Attachment Request Profile
-
Requesting Attachments Using Attachments Codes
-
-
Enhancement
-
Compatible, substantive
-
Yes
Description
Background and Rationale:
1) The existing LOINC-defined valueset for LOINC attachment codes does not expand with the ig-publisher, making it difficult for the reader to find the codes.
2) 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.
Proposal
1) Update CDEX Task Attachment Request Profile to use a new CDEX-defined value set* of enumerated LOINC Attachment Codes and an additional extensible binding to a new CDex defined PWK01 Attachment Report Type Code for prior auth work-flows
(*Revert to the LOINC-defined attachments codes value set when the publishing issues are fixed.
Note that PWK01 code will not publish due to X12 IP restrictions.
2) Update the page Requesting Attachments Using Attachments Codes"
Requesting attachments using LOINC attachment codes defined by the LOINC Document Ontology is a HIPAA-based request model. The Payer communicates the missing information for a claim or prior authorization with these codes, which typically represent data in document form (e.g., a PDF or CCDA). The sequence diagram in Figure 15 below summarizes the interaction between the Payer and Provider to request and receive attachments using the combination of the CDex Task Attachment Request Profile using attachment codes and the $submit-attachment operation.
to
Requesting attachments using LOINC attachment codes defined by the LOINC Document Ontology or X12's PWK01 attachment codes is a HIPAA-based request model. The Payer communicates the missing information for a claim or prior authorization with these codes, which typically represent data in document form (e.g., a PDF or CCDA). The sequence diagram in Figure 15 below summarizes the interaction between the Payer and Provider to request and receive attachments using the combination of the CDex Task Attachment Request Profile using attachment codes and the $submit-attachment operation.
3) update other reference to the attachment codes in the guide from
"LOINC attachment codes". to "LOINC and PWK01 attachment codes"
Attachments
Issue Links
- is duplicated by
-
FHIR-44876 Update Task.code Value Set to include X12 PWO1 codes for PA
- Duplicate
- relates to
-
FHIR-44884 Change Task.input code slice to align with PAS Task
- Triaged