Diagnosis codes are not returned on Claim Response or Claim Inquiry Response

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • 1.0.0 [deprecated]
    • Financial Mgmt
    • PAS Claim Inquiry Response
      PAS Claim Response
    • (many)
    • Hide

      The following changes need to be made to allow the communication of diagnoses in the communication request:
      a) The communicatedDiagnosis extension needs the valueCodeableConcept to be 1..1 instead of 0..1
      b) the use of the extension in the CommunicationRequest needs to be 0..* instead of 0..1
      c) the extension needs to be added to the ClaimInquiryResponse.item as 0..1
      d) the extension needs to be added to the ClaimResponse.item as 0..*

      Show
      The following changes need to be made to allow the communication of diagnoses in the communication request: a) The communicatedDiagnosis extension needs the valueCodeableConcept to be 1..1 instead of 0..1 b) the use of the extension in the CommunicationRequest needs to be 0..* instead of 0..1 c) the extension needs to be added to the ClaimInquiryResponse.item as 0..1 d) the extension needs to be added to the ClaimResponse.item as 0..*
    • Andy Stechishin / Mark Scrimshire: 13-0-0
    • Correction
    • Non-substantive

      Diagnosis can be sent back on the Claim Response and the Claim Inquiry Response, we have them in the communication to manage the DX/LOINC/Modifier situation, but we don't have the ability to return the Diagnosis.

      Claim Response need to be able to return 12 and on the Claim Inquiry Response 1.

      Example:  

       

            Assignee:
            Jean Duteau
            Reporter:
            Mary Kay McDaniel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: