Uploaded image for project: 'eCQM Issue Tracker'
  1. eCQM Issue Tracker
  2. CQM-1284

Stroke 4 Thrombolytic Therapy Contraindication

XMLWordPrintable

    • Icon: EH/CAH eCQMs EH/CAH eCQMs
    • Resolution: Answered
    • Icon: Minor Minor
    • None
    • Hide
      Regarding the parallel logic statements:

      The intent of eCQM logic statements “Medication, Order Not Done: Medical Reason” and “Medication, Administered Not Done: Medical Reason” is to allow for documentation of a medical reason or a patient refusal to occur in two different clinical workflows: ordering, and medication administration. Recognizing that some acceptable reasons for not providing pharmacotherapy are difficult to capture as structured data, members of the eMeasures Issues Group (eMIG) reached the decision to use these parallel statements consistently throughout the eCQMs.

      As the intent of the statements are two address two separate processes (ordering and administration) that may occur at different points in time, and only one of the statements needs to be met in order to meet the exclusion criteria, we agree that presenting both to the physician is unnecessary.

      Regarding alignment with the chart abstracted measure:

      For this measure specifically, the logic is intended to align with the manually abstracted data element, Reason for Not Initiating IV Thrombolytic. This data element is a denominator exclusion, which lists valid reasons for which a patient would not receive IV Thrombolytic. As you noted, the manually abstracted data element states that
      other reasons for not initiating IV thrombolytic therapy must be documented by a physician/APN/PA or pharmacist- with the exception of nursing documentation of a telemedicine/teleneurology reason for not initiating IV thrombolytic therapy. In addition, several stand-alone reasons, such as patient refusal and an NIHSS score of zero are acceptable.

      In the eCQM, the “Medication, Administered Not Done: Medical Reason” logic provides a way to capture documentation at the point of administration for those stand-alone reasons as well as telemedicine reason, which are not explicitly modeled. We understand your concern that nursing staff documentation of other reasons for not administering should not be accepted for this data element, and will consider your feedback for the next annual update.

      Finally, your ticket references the December 2012 version of the eCQM (CMS91v1). Please note, the April 2014 version of this measure includes logic to support capture of standalone reasons for not administering IV thrombolytic, such as a documentation of an NIHSS score of zero. We encourage you to refer to the latest eCQM specifications (2014 CQM Eligible Hospitals, April 2014 Update) for this and other measures, as they have been updated to include new codes, logic corrections and clarifications. You can find the technical eCQM specifications for all versions of the eCQMs in CMS's eCQM library: http://cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/eCQM_Library.html
      Show
      Regarding the parallel logic statements: The intent of eCQM logic statements “Medication, Order Not Done: Medical Reason” and “Medication, Administered Not Done: Medical Reason” is to allow for documentation of a medical reason or a patient refusal to occur in two different clinical workflows: ordering, and medication administration. Recognizing that some acceptable reasons for not providing pharmacotherapy are difficult to capture as structured data, members of the eMeasures Issues Group (eMIG) reached the decision to use these parallel statements consistently throughout the eCQMs. As the intent of the statements are two address two separate processes (ordering and administration) that may occur at different points in time, and only one of the statements needs to be met in order to meet the exclusion criteria, we agree that presenting both to the physician is unnecessary. Regarding alignment with the chart abstracted measure: For this measure specifically, the logic is intended to align with the manually abstracted data element, Reason for Not Initiating IV Thrombolytic. This data element is a denominator exclusion, which lists valid reasons for which a patient would not receive IV Thrombolytic. As you noted, the manually abstracted data element states that other reasons for not initiating IV thrombolytic therapy must be documented by a physician/APN/PA or pharmacist- with the exception of nursing documentation of a telemedicine/teleneurology reason for not initiating IV thrombolytic therapy. In addition, several stand-alone reasons, such as patient refusal and an NIHSS score of zero are acceptable. In the eCQM, the “Medication, Administered Not Done: Medical Reason” logic provides a way to capture documentation at the point of administration for those stand-alone reasons as well as telemedicine reason, which are not explicitly modeled. We understand your concern that nursing staff documentation of other reasons for not administering should not be accepted for this data element, and will consider your feedback for the next annual update. Finally, your ticket references the December 2012 version of the eCQM (CMS91v1). Please note, the April 2014 version of this measure includes logic to support capture of standalone reasons for not administering IV thrombolytic, such as a documentation of an NIHSS score of zero. We encourage you to refer to the latest eCQM specifications (2014 CQM Eligible Hospitals, April 2014 Update) for this and other measures, as they have been updated to include new codes, logic corrections and clarifications. You can find the technical eCQM specifications for all versions of the eCQMs in CMS's eCQM library: http://cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/eCQM_Library.html
    • Hide
      Workflow burden by requiring a physician to answer an extra question that should not be needed. Administration of medication done or not done can be captured in the background. Requiring to distinguish ordered vs administered requires a physician to make a choice.
      Show
      Workflow burden by requiring a physician to answer an extra question that should not be needed. Administration of medication done or not done can be captured in the background. Requiring to distinguish ordered vs administered requires a physician to make a choice.

      In the STK-4 algorithm the code is written in a way that requires an EHR with the ability to capture a contraindication at the time of ordering a medication OR the time of administering a medication. From an interface perspective, it forces a physician to document a contraindication by checkbox as it relates to "Order not done" or "Administered not done". If the intent of the eMeasures is to be a reflection of the legacy inpatient quality reporting measures, this makes absolutely no sense. When a quality abstractor is determining if a medication measure was met or not met, they look for evidence of administration given. Whether it was ordered or not has no bearing on the outcome. In essence, at what point in time (order or administered) a contraindication is documented has no bearing on the outcome. Medication administered in this case is what matters. I believe the "Medication, order not done" should be completely removed from the algorithm unless someone can explain why these two actions need to be captured when only one really counts in the end. Thank you

      • Denominator Exclusions =
      o AND:
       OR: "Occurrence A of Encounter, Performed: Inpatient Encounter (reason: 'Carotid Intervention')"
       OR: "Risk Category Assessment: National Institute of Health Stroke Scale (result = 0 )" <= 180 minute(s) starts after start of
       OR: "Occurrence A of Symptom, Active: Neurologic Symptoms of Stroke (start datetime)"
       OR: "Occurrence A of Symptom, Active: Baseline State (stop datetime)"
       OR: "Medication, Administered: Thrombolytic (t-PA) Therapy" <= 2 day(s) starts before start of "Occurrence A of Encounter, Performed: Emergency Department Visit (facility location arrival datetime)"
       OR:
       OR: "Medication, Order not done: Medical Reason" for "Thrombolytic (t-PA) Therapy RxNorm Value Set"
       OR: "Medication, Order not done: Patient Refusal" for "Thrombolytic (t-PA) Therapy RxNorm Value Set"
       OR: "Medication, Administered not done: Medical Reason" for "Thrombolytic (t-PA) Therapy RxNorm Value Set"
       OR: "Medication, Administered not done: Patient Refusal" for "Thrombolytic (t-PA) Therapy RxNorm Value Set"
       <= 180 minute(s) starts after start of "Occurrence A of Symptom, Active: Baseline State (stop datetime)"

            JLeflore Mathematica EH eCQM Team
            jkunisch Joseph Kunisch (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved:
              Comment Posted On: