Follow-up: Inactive VTE

XMLWordPrintable

    • Type: Hosp Inpt eCQMs - Hospital Inpatient eCQMs
    • Resolution: Done
    • Priority: Minor
    • Component/s: Guidance
    • Hide
      Thank you for your question. The patients should be falling into the numerator and not falling out of the measure with an inactive or active diagnosis. In order to answer your specific question regarding the limitation of the value set, I would need further clarification. It is the same value set for inactive and active diagnosis as there are not different codes, it is just flagged differently in the EHR system. You may also want to reach out to your vendor regarding the mapping of inactive and active diagnosis.
      Show
      Thank you for your question. The patients should be falling into the numerator and not falling out of the measure with an inactive or active diagnosis. In order to answer your specific question regarding the limitation of the value set, I would need further clarification. It is the same value set for inactive and active diagnosis as there are not different codes, it is just flagged differently in the EHR system. You may also want to reach out to your vendor regarding the mapping of inactive and active diagnosis.
    • CMS108v5/NQF0371
    • Hide
      The algorithm currently evaluates inactive dx VTE start before start of the IP encounter. Is it expected that an inactive VTE would be acute?

      Based on the statement:
      "Diagnosis, Inactive: Venous Thromboembolism"
      starts before start of Occurrence A of $EncounterInpatient

      For example:If a patient had been diagnosed with an acute VTE during a previous admission and as a result was discharge with Oral Factor Xa. Then readmitted while still taking Oral Factor Xa and has a diagnosis of History of VTE. This would result in a fallout due to the limitation of the diagnosis codes on the value set associate with the path that evaluates Oral Factor Xa with inactive diagnosis of VTE (See below).

      "Diagnosis, Inactive: Atrial Fibrillation/Flutter
      starts before start of Occurrance A of $EncounterInpatient
      Show
      The algorithm currently evaluates inactive dx VTE start before start of the IP encounter. Is it expected that an inactive VTE would be acute? Based on the statement: "Diagnosis, Inactive: Venous Thromboembolism" starts before start of Occurrence A of $EncounterInpatient For example:If a patient had been diagnosed with an acute VTE during a previous admission and as a result was discharge with Oral Factor Xa. Then readmitted while still taking Oral Factor Xa and has a diagnosis of History of VTE. This would result in a fallout due to the limitation of the diagnosis codes on the value set associate with the path that evaluates Oral Factor Xa with inactive diagnosis of VTE (See below). "Diagnosis, Inactive: Atrial Fibrillation/Flutter starts before start of Occurrance A of $EncounterInpatient

          Assignee:
          Joelencia Leflore
          Reporter:
          Brooke Villarreal (Inactive)
          Nichole Cunningham (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

            Created:
            Updated:
            Resolved: