How to evaluate INR results with ">" sign

XMLWordPrintable

    • Type: Certification
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • Hide
      We work with some hospitals that result INR with a > sign (ex: >8.0), and not a specific numeric result. We are, at this time, unable to evaluate the data because of the > sign. How do you suggest we handle this? How should this result be evaluated? How should this data be submitted in the QRDA file? Per these hospitals, the result of > is driven by the instrument they are using and can't be altered.
      Logic is:
      union ( ["Laboratory Test, Performed": "INR"] INRLabTest
      where INRLabTest.result > 3.0
      return "Assessment, Performed" { id: INRLabTest.id, authorDatetime: INRLabTest.resultDatetime }
      Show
      We work with some hospitals that result INR with a > sign (ex: >8.0), and not a specific numeric result. We are, at this time, unable to evaluate the data because of the > sign. How do you suggest we handle this? How should this result be evaluated? How should this data be submitted in the QRDA file? Per these hospitals, the result of > is driven by the instrument they are using and can't be altered. Logic is: union ( ["Laboratory Test, Performed": "INR"] INRLabTest where INRLabTest.result > 3.0 return "Assessment, Performed" { id: INRLabTest.id, authorDatetime: INRLabTest.resultDatetime }
    • Medisolv, Inc
    • Kristen Beatson
    • 4105493849
    • Hide
      For 2019, the interval "IVL" data type is supported. You would, for example, report it as as IVL_REAL or and IVL_PQ as shown below:

                  <value xsi:type="IVL_REAL">
                      <low value="8"/>
                    </value>

                    <value xsi:type="IVL_PQ">
                      <low value="140" unit="mmHg" inclusive="true"/>
                    </value>

      The logic for comparing intervals deserves some considerations. For example: if measure requires “>3”,  and if data reported as below, the outcomes will vary:

       > 4 : passes the rule, as the data fully meets the criteria, as any number greater than 4 is also greater than criteria required in the condition >3
      < 8 : does NOT pass the rule, because <8 partially meets the criteria, as data that is <= 3 does not meet criteria
      > 2 : does NOT pass the rule, because >2 partially meets the criteria, as data that is <=3 does not meet criteria
      Show
      For 2019, the interval "IVL" data type is supported. You would, for example, report it as as IVL_REAL or and IVL_PQ as shown below:             <value xsi:type="IVL_REAL">                 <low value="8"/>               </value>               <value xsi:type="IVL_PQ">                 <low value="140" unit="mmHg" inclusive="true"/>               </value> The logic for comparing intervals deserves some considerations. For example: if measure requires “>3”,  and if data reported as below, the outcomes will vary:  > 4 : passes the rule, as the data fully meets the criteria, as any number greater than 4 is also greater than criteria required in the condition >3 < 8 : does NOT pass the rule, because <8 partially meets the criteria, as data that is <= 3 does not meet criteria > 2 : does NOT pass the rule, because >2 partially meets the criteria, as data that is <=3 does not meet criteria

          Assignee:
          Matthew Tiller
          Reporter:
          Kristen Beatson
          Votes:
          0 Vote for this issue
          Watchers:
          9 Start watching this issue

            Created:
            Updated:
            Resolved: