Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-36405

Payers need CPT/HCPCS, not just SNOMED/LOINC for services

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Financial Mgmt
    • STU
    • Supported Hooks
    • Hide

      The payers will need to adjust to receiving clinical codes.  The EHRs will not provide translations.  The encoding process happens at a completely different point in the business cycle and the full translation often involves human decision-making.  To provide the needed decision support, payers will have to map SNOMED, LOINC and other clinical codes to billing codes - or more likely to "ranges of possible billing codes" and will need to deal with clinical data as it is, not as they might wish it to be.  We understand this involves adding extra capabilities to payer systems they have not previously had.  This expectation is called out explicitly here: http://build.fhir.org/ig/HL7/davinci-crd/background.html#impact-on-payer-processes.

      However, we should call out the same impact in the DTR specification.  We will raise a tracker item to do that.

      Show
      The payers will need to adjust to receiving clinical codes.  The EHRs will not provide translations.  The encoding process happens at a completely different point in the business cycle and the full translation often involves human decision-making.  To provide the needed decision support, payers will have to map SNOMED, LOINC and other clinical codes to billing codes - or more likely to "ranges of possible billing codes" and will need to deal with clinical data as it is, not as they might wish it to be.  We understand this involves adding extra capabilities to payer systems they have not previously had.  This expectation is called out explicitly here: http://build.fhir.org/ig/HL7/davinci-crd/background.html#impact-on-payer-processes. However, we should call out the same impact in the DTR specification.  We will raise a tracker item to do that.
    • Bob Dieterle / Jeff Brown : 22-0-1
    • Clarification
    • Non-substantive

    Description

      Payers do not know what to do with SNOMED and LOINC codes and what they authorize are services to be paid for which are represented by either CPT or HCPCS.

       

      So to authorized payment based on non-payment codes does not work.

       

      A work around could be the clinical codes are submitted to the payer, the payer does their best to translate to a payment code and responds with a payment code.

       

      The provider would then need to determine if the translated payment code value is in alignment with the desired service requested.

       

      I believe this same issue also exists in the specifications:

       

      Documentation Templates Rules Implementation Guide

      Prior Authorization Implementation Guide

      Attachments

        Activity

          People

            Unassigned Unassigned
            chris_cioffi Chris Cioffi
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: