Medications with no end date

XMLWordPrintable

    • Type: EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Priority: Minor
    • Component/s: Measure
    • None
    • Hide
      The QDM guidance regarding cumulative medication duration states that it should generally be calculated as the number of doses in the interval of interest, divided by the doses per day. The actual duration (start date to end date) of a "Medication, Active" entry should not be a part of the calculation-- only the metadata of the order should be used (quantity, dosage, refills, etc).

      Regarding #1, there still could be a problem if you are using the "during" timing relationship. If you say something like Sum > 180 day(s) of: "Medication, Active: MyMed (cumulative medication duration)" during "Measurement Period", then if the Medication, Active has no end date it will not be captured in the calculation (since we can't determine that it is during the measurement period). Instead, you could potentially use starts during – but be aware that this will capture (and calculate) entries that overlap past the measure period end. Another possible approach would be to do the calculation on a different datatype (like Medication, Order) if you know it's more likely to have an end date.

      Regarding #2, as noted above, in the case of CMD the duration should be based on order data, not on the start/end times of the "Medication, Active" event. Unless an order has unlimited refills, it shouldn't calculate the CMD based on "forever"-- it will calculate out as far as the refills go.
      Show
      The QDM guidance regarding cumulative medication duration states that it should generally be calculated as the number of doses in the interval of interest, divided by the doses per day. The actual duration (start date to end date) of a "Medication, Active" entry should not be a part of the calculation-- only the metadata of the order should be used (quantity, dosage, refills, etc). Regarding #1, there still could be a problem if you are using the "during" timing relationship. If you say something like Sum > 180 day(s) of: "Medication, Active: MyMed (cumulative medication duration)" during "Measurement Period", then if the Medication, Active has no end date it will not be captured in the calculation (since we can't determine that it is during the measurement period). Instead, you could potentially use starts during – but be aware that this will capture (and calculate) entries that overlap past the measure period end. Another possible approach would be to do the calculation on a different datatype (like Medication, Order) if you know it's more likely to have an end date. Regarding #2, as noted above, in the case of CMD the duration should be based on order data, not on the start/end times of the "Medication, Active" event. Unless an order has unlimited refills, it shouldn't calculate the CMD based on "forever"-- it will calculate out as far as the refills go.
    • CMS156v3/NQF0022, CMS179v3/NQFna
    • Development

      Two questions related to one another for meds with no end date:

      1. If a medication end date is not captured (made mandatory) from submissions, then the the duration of the medication (cumulative medication duration) intake cannot be calculated. If this is the case, then the patient will in essence not qualify for the measure so the patient will not be eligible. For example EP_CMS156v2_NQF0022_HighRisk_Med_Elderly (PQRS measure 9)
      Question- What is advised in this case?

      2. The system cannot tell if the patient has stopped taking the medication (or the medication is not active in reality).
      In this scenario if the end date is not present, but there is a start datew for the med, we are assuming that the the medication is active.
      Question- Is this a safe assumption

            Assignee:
            Chris Moesel (Inactive)
            Reporter:
            Adetola Adetunji (Inactive)
            Adetola Adetunji (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: