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

Negation documentation

XMLWordPrintable

    • Hide
      Please see linked ticket, CQM-1835, for the solution
      Show
      Please see linked ticket, CQM-1835 , for the solution
    • CMS30v5/NQF0639, CMS60v4/NQF0164, CMS71v5/NQF0436, CMS72v4/NQF0438, CMS91v5/NQF0437, CMS100v4/NQF0142, CMS104v4/NQF0435, CMS105v4/NQF0439, CMS108v4/NQF0371, CMS109v4/NQFna, CMS188v5/NQF0147, CMS190v4/NQF0372
    • CMS100v3/NQF142, CMS102v3/NQF441, CMS104v3/NQF435, CMS105v3/NQF439, CMS108v3/NQF371, CMS109v3/NQFna, CMS188v4/NQF0147, CMS190v3/NQF0372, CMS30v4/NQF0639, CMS60v3/NQF0164, CMS71v4/NQF0436, CMS72v3/NQF0438
    • This issue requires end-users to input data that is no longer required.

      In reading the solution for JIRA 1835, the content suggests that our vendor should be able to use the documentation of a contraindication such as "bleeding risk" to then map the medication that would have potentially been provided, such as an anticoagulant to a null value in lieu of a specific code provided in the value-set. This would alleviate the need for the provider to document outside of workflow to identify what medication would have been given, if not contraindicated. Since the guidance and measure specifications do not align as intended, is it possible for our vendor to move forward with the utilization of the nullflavor without the actual change to the measure specifications?

            JLeflore Mathematica EH eCQM Team
            bodinekm Kimberly M. Bodine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: