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

Intent guidance does not match espec for foot exam

XMLWordPrintable

    • Icon: Annual Update Annual Update
    • Resolution: Fixed/Complete
    • Icon: Major Major
    • Inbox
    • None
    • Howard Bregman
    • 608.271.9000
    • Vendor/Epic
    • No
    • Hide
      The intent does not match the logic that specifies "OR" for sensory and pulse testing when it should say "AND" according to the measure.

      The new version of this measure was changed to reflect the fact that the three findings of the foot exam-- visual, pulse and sensory -- are all part of a comprehensive exam and therefore should all be required to satisfy the measure according to the measure steward. The new version of the measure was published at the June 2013 EP update.
      Show
      The intent does not match the logic that specifies "OR" for sensory and pulse testing when it should say "AND" according to the measure. The new version of this measure was changed to reflect the fact that the three findings of the foot exam-- visual, pulse and sensory -- are all part of a comprehensive exam and therefore should all be required to satisfy the measure according to the measure steward. The new version of the measure was published at the June 2013 EP update.

      The clinical recommendation statement for this measure states:

      The foot examination should include inspection, assessment of foot pulses, and testing for loss of protective sensation (10-g monofilament plus testing any one of: vibration using 128-Hz tuning fork, pinprick sensation, ankle reflexes, or vibration perception threshold).

      Given that, why do the specs require a visual inspection and a pulse exam OR a sensory exam? This does not seem to be consistent with the above statement.

            rtallapragada Ramya Tallapragada (Inactive)
            hbregman Howard Bregman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: