UCUM units fo Risk Adjustments Variables

XMLWordPrintable

    • Type: Question/Guidance
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • CMS0832v3, CMS1218v2

      Hello,

      We are seeking clarification regarding how units of measure (UOM) should be handled for Risk Variable results when the documented unit does not exactly match the format specified in the measure guidance.

      Currently, we are trying to determine whether results should still be qualified and included in the QRDA submission when the unit of measure differs from what is specified in the guidance, or whether those results should be excluded.

      The guidance section of the specifications defines expected units for certain Risk Variables. However, in practice, clients may document results using equivalent but differently formatted units.

      For example:

      The specifications indicate that Heart Rate should be reported as {Beats}/min.

      A client may document Heart Rate using the unit bpm.

      In this scenario, we are unsure how the result should be handled.

      Specifically, we would like clarification on the following:

      If a Risk Variable result is documented with a unit of measure that does not exactly match the format specified in the guidance, should the result still be qualified and included in the QRDA file as documented?

      Or

      Should the result not be qualified and therefore not included in the QRDA submission if the unit does not align exactly with the specified format?

      If the result is included with a different unit (e.g., bpm instead of {Beats}/min), does CMS convert or handle equivalent units during processing?

      Any clarification on the expected handling of Risk Variable result units would be greatly appreciated so we can ensure our logic aligns with CMS expectations.

            Assignee:
            David DeRoode
            Reporter:
            Talisa Williams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: