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

Provide more guidance on the expectations on Task termination

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci Risk Adjustment (FHIR)
    • 1.0.0
    • Clinical Quality Information
    • STU
    • General Guidance
    • Hide

      The Risk Adjustment use case project participants and implementers had extensive discussions around the workflow around annotation and remediation post ballot. The updated design uses a new Risk Adjustment Data Exchange MeasureReport profile and uses the base FHIR $submit-data operation for Provider to submit clinical evaluation evidence data to Payer. For example, Provider may submit a patient's medical record such as a C-CDA document (using DocumentReference resource) to Payer as clinical evaluation evidence to close and/or invalidate coding gaps using this method. The Task profile included in the ballot will be removed and no longer used. The updates will also include updating the term from remediation to submitting data to payer across the IG where applicable, including narratives, examples, etc.

      After the Payer receives and processes the clinical evaluation evidence data submitted by the Provider, the data will then be used for the next coding gap evaluation and coding gap reports generation. If Provider identifies issues with the gaps shown on the new coding gap reports, they will use the data submission process again to submit proper data and documentation to address the issues.  Will ensure there is guidance added in the IG to state this. 

      Show
      The Risk Adjustment use case project participants and implementers had extensive discussions around the workflow around annotation and remediation post ballot. The updated design uses a new Risk Adjustment Data Exchange MeasureReport profile and uses the base FHIR $submit-data operation for Provider to submit clinical evaluation evidence data to Payer. For example, Provider may submit a patient's medical record such as a C-CDA document (using DocumentReference resource) to Payer as clinical evaluation evidence to close and/or invalidate coding gaps using this method. The Task profile included in the ballot will be removed and no longer used. The updates will also include updating the term from remediation to submitting data to payer across the IG where applicable, including narratives, examples, etc. After the Payer receives and processes the clinical evaluation evidence data submitted by the Provider, the data will then be used for the next coding gap evaluation and coding gap reports generation. If Provider identifies issues with the gaps shown on the new coding gap reports, they will use the data submission process again to submit proper data and documentation to address the issues.  Will ensure there is guidance added in the IG to state this. 
    • Yan Heras/ Corey Spears: 22-0-1
    • Clarification
    • Non-compatible

    Description

      In the remediation process, the provider submits the evidence through the use of a Task. This task is picked up by a Risk Adjustment Coder (CRC). If this CRC determines the evidence is insufficient, it seems like no other action is taken. The process is concluded, and neither the payer nor the provider are notified of this.

      The potential ramifications of this termination should be laid out in the specification. Should this specification provide a means to provide that feedback to the payer and/or provider? Should there be an appeals process or a means to further address any issues or appeal? What are the expectations if this gap is identified again (either immediately or some other time in the future)?

      Attachments

        Activity

          People

            Unassigned Unassigned
            corey_spears Corey Spears
            Corey Spears
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: