eMeasure spec standards do not provide a method of representing a comparison between Time 1 and Time 2 observed/reported values and whehter the difference meets a certain threshold.

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Deferred
    • Priority: Minor
    • None
    • Component/s: Data Model
    • This issue impacts the ability to correctly calculate MUCD-22 and MUCD-23.

      eMeasure specification standards do not provide a method of representing a comparison between Time 1 and Time 2 observed/reported values, and whether the difference meets a certain threshold.

      This impacts two MU-3 measures:
      MUCD-22: Functional Status Assessment and Improvement for Patients who Received a Total Hip Replacement
      MUCD-23: Functional Status Assessment and Improvement for Patients who Received a Total Knee Replacement

      We have a workaround for MU-2 versions of these measures which is to use a LOINC code to represent the "difference between follow-up FSA score and FSA care goal", but would be preferable to enhance spec standards.

            Assignee:
            Floyd Eisenberg (Inactive)
            Reporter:
            Jeff McCartney (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: