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

Discharge status: Hospital Measures - Expired vs. Patient Characteristic: Expired

XMLWordPrintable

    • Icon: EH/CAH eCQMs EH/CAH eCQMs
    • Resolution: Answered
    • Icon: Minor Minor
    • None
    • Harshad Patil
    • CitiusTech
    • Hide
      There is a difference between the two: "Patient Characteristic Expired" simply indicates that the patient is dead. An encounter with "Discharge Status: Expired" indicates that the patient died during the encounter. For some measures, this distinction may be important.

      That said, "Patient Characteristic Expired" during "Occurrence A of Encounter, Performed: <valueset>" would also indicate that the patient died during the encounter (and is the approach that NQF1354 takes). Perhaps there might be a clinically relevant reason a measure would prefer using the discharge status versus the above – I don't know. If not, however, it might make sense for measures to harmonize on one preferred representation where possible (and I suspect "Patient Characteristic Expired" would be the more reliable way to go). This, however, is likely a conversation for another day!

      Regarding QRDA Cat I, I expect that it's not an "either/or" situation-- if the patient is dead, you should report "Patient Characteristic Expired" with the expiry date/time, and if they were discharged due to death, you should also report the "Discharge Status: Expired" on the relevant encounter (assuming the measure asked for that information).

      The measure use of datatypes and timing will be reviewed at the next annual measure update and amended according to the steward's discretion.
      Show
      There is a difference between the two: "Patient Characteristic Expired" simply indicates that the patient is dead. An encounter with "Discharge Status: Expired" indicates that the patient died during the encounter. For some measures, this distinction may be important. That said, "Patient Characteristic Expired" during "Occurrence A of Encounter, Performed: <valueset>" would also indicate that the patient died during the encounter (and is the approach that NQF1354 takes). Perhaps there might be a clinically relevant reason a measure would prefer using the discharge status versus the above – I don't know. If not, however, it might make sense for measures to harmonize on one preferred representation where possible (and I suspect "Patient Characteristic Expired" would be the more reliable way to go). This, however, is likely a conversation for another day! Regarding QRDA Cat I, I expect that it's not an "either/or" situation-- if the patient is dead, you should report "Patient Characteristic Expired" with the expiry date/time, and if they were discharged due to death, you should also report the "Discharge Status: Expired" on the relevant encounter (assuming the measure asked for that information). The measure use of datatypes and timing will be reviewed at the next annual measure update and amended according to the steward's discretion.
    • CMS31v3/NQF1354
    • Impacting product implementation

      To represent that a patient has expired, which data element is better suited? Or are both supposed to be used for different purposes?

      Patient Characteristic Expired: Patient Expired (used in NQF 1354 and 0453)
      Discharge status: Hospital Measures - Expired (used in NQF 0142)

      I am not talking about value sets here - there are different tickets which have raised that and looks like they will be harmonized in the next CQM release.

      We need to know (irrespective of whether the codes are harmonized or not) which of the above data elements (or both?) to use in the QRDA Cat I file in case a patient expires and why.

            julia.skapik Julia Skapik (Inactive)
            harshad.patil@citiustech.com Harshad Patil (Inactive)
            eldred (Inactive), Jyoti Moryani (Inactive), Pranjali Kamat (Inactive), Rob McClure
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              Comment Posted On: