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

Seeking clarity in cases such as these where multiple encounters exist within a QRDA-I

XMLWordPrintable

    • BJ Pate
    • 18007118363
    • Quantros, Inc.
    • Hide
      Thank you for your questions.

      Q: If those encounters existed and they are being processed for example through Stroke2 CMS104v3: Should both of these episodes of care be evaluated by the stroke algorithm, and produce distinct pass/fail/exclusion/exception results for each of these episodes? A: Yes, for episode of care measures, each episode in the measurement period should be evaluated. The measure logic in STK2 will determine which data captured during the measurement period are used to calculate the measure rates for each episode.
       
      Q: If so is there someplace within documentation that clearly specifies this. Or is it by design Stroke2 CMS104v3 would limit which of those encounters (ie. through Occurrences) would be evaluated? A: Please refer to the 2016 Measure Logic Guidance document, eCQM Measure Logic Guidance v1.11 Update June 2015
       Page 4, for a detailed description of Episode of Care based measures, and the application of Occurrences to episodes.
       
      Q: We are also looking for clarification on how to interpret the Occurrence clauses in the STK algorithms as they apply to Non-Elective Inpatient Encounters. Do these occurrences apply to the contents of a QRDA files (as a whole), or do they apply to the contents of one or more episodes of care contained within the QRDA file? A: Please refer to the Section 4.3, Specific Occurrences, of the Measure Logic Guidance document mentioned above for a detailed explanation of how Occurrences are applied. In general, Occurrence will not apply to the contents of the QRDA file as a whole, they are applied to data elements within the measure logic.
       
      Q: If the occurrences apply to the contents of an episode of care, then the terminology of “Occurrence A of $EncounterInpatientNonElective” seems to be misleading, as there can only be one Inpatient Encounter per episode of care for Inpatient measures. In episode-of-care measures, the episodes are always designated by a specific occurrence (refer to page 4 of the Logic Guidance document). Also, as previously stated there can be more than one Inpatient Encounter per episode of care. Further, a common misunderstanding of “Occurrence A” is to think of it as “Occurrence 1” (vs Occurrence 2, 3, or 4). In other words, there may be more than one Occurrence A per measurement period, as Occurrence A simply means “any (or all) occurrence that meet the population criteria.” A: In the case of the Stroke 2 initial population:
      •Initial Population =
      ◦AND: Age >= 18 year(s) at: Occurrence A of $EncounterInpatientNonElective
      ◦AND: Union of:
      ◾"Diagnosis, Active: Hemorrhagic Stroke (ordinality: Principal)"
      ◾"Diagnosis, Active: Ischemic Stroke (ordinality: Principal)"
      ◾starts during Occurrence A of $EncounterInpatientNonElective
      This could be restated narratively as:
       
      “Occurrence A of $EncounterInpatientNonElective equals all encounters that meet the $EncounterInpatientNonElective criteria, where the patient is >=18 years of age at the start of the encounter, and which contain a principal diagnosis of ischemic or hemorrhagic stroke”
       
      Q:Lastly, is there an option for hospitals to build QRDA files as patient based OR episode of care based, or are QRDA files always built as patient-based files? A: One QRDA I report per patient should be submitted for a CCN. If a second QRDA file is submitted for a patient at a CCN, then the first file is overwritten.
      Show
      Thank you for your questions. Q: If those encounters existed and they are being processed for example through Stroke2 CMS104v3: Should both of these episodes of care be evaluated by the stroke algorithm, and produce distinct pass/fail/exclusion/exception results for each of these episodes? A: Yes, for episode of care measures, each episode in the measurement period should be evaluated. The measure logic in STK2 will determine which data captured during the measurement period are used to calculate the measure rates for each episode.   Q: If so is there someplace within documentation that clearly specifies this. Or is it by design Stroke2 CMS104v3 would limit which of those encounters (ie. through Occurrences) would be evaluated? A: Please refer to the 2016 Measure Logic Guidance document, eCQM Measure Logic Guidance v1.11 Update June 2015  Page 4, for a detailed description of Episode of Care based measures, and the application of Occurrences to episodes.   Q: We are also looking for clarification on how to interpret the Occurrence clauses in the STK algorithms as they apply to Non-Elective Inpatient Encounters. Do these occurrences apply to the contents of a QRDA files (as a whole), or do they apply to the contents of one or more episodes of care contained within the QRDA file? A: Please refer to the Section 4.3, Specific Occurrences, of the Measure Logic Guidance document mentioned above for a detailed explanation of how Occurrences are applied. In general, Occurrence will not apply to the contents of the QRDA file as a whole, they are applied to data elements within the measure logic.   Q: If the occurrences apply to the contents of an episode of care, then the terminology of “Occurrence A of $EncounterInpatientNonElective” seems to be misleading, as there can only be one Inpatient Encounter per episode of care for Inpatient measures. In episode-of-care measures, the episodes are always designated by a specific occurrence (refer to page 4 of the Logic Guidance document). Also, as previously stated there can be more than one Inpatient Encounter per episode of care. Further, a common misunderstanding of “Occurrence A” is to think of it as “Occurrence 1” (vs Occurrence 2, 3, or 4). In other words, there may be more than one Occurrence A per measurement period, as Occurrence A simply means “any (or all) occurrence that meet the population criteria.” A: In the case of the Stroke 2 initial population: •Initial Population = ◦AND: Age >= 18 year(s) at: Occurrence A of $EncounterInpatientNonElective ◦AND: Union of: ◾"Diagnosis, Active: Hemorrhagic Stroke (ordinality: Principal)" ◾"Diagnosis, Active: Ischemic Stroke (ordinality: Principal)" ◾starts during Occurrence A of $EncounterInpatientNonElective This could be restated narratively as:   “Occurrence A of $EncounterInpatientNonElective equals all encounters that meet the $EncounterInpatientNonElective criteria, where the patient is >=18 years of age at the start of the encounter, and which contain a principal diagnosis of ischemic or hemorrhagic stroke”   Q:Lastly, is there an option for hospitals to build QRDA files as patient based OR episode of care based, or are QRDA files always built as patient-based files? A: One QRDA I report per patient should be submitted for a CCN. If a second QRDA file is submitted for a patient at a CCN, then the first file is overwritten.
    • Multiple Episode of Care within QRDA-I, Evaluation of these EoC, and Occurrences surrounding these

      Posting same question here because unsure where this would really need to go:
      QRDA category I files are generated one per patient, and should cover all of the data elements required to compute the quality measures whose computation is being certified.
      The HL7 QRDA Implementation Guide is essential reading, and describes the data elements that must/may be included.
      A QRDA-I file indeed contains data relating to multiple visits. Unfortunately, at this time, the only way to associate clinical data with an encounter is temporally – the timing of the diagnosis/result/med-order/etc indicates whether it is associated with the visit.

      Here is additional feedback from Lantana:

      A QRDA file may have multiple visits of a single patient. In that case, the clinical data of patient will be linked to an encounter via timestamp.
      For instance, a QRDA may have two inpatient encounters (encounter_1, and encounter_2), a patient has lab tests in both encounter.

      encounter_1: from 2011-01-01 to 2011-01-10
      encounter_2: from 2011-02-05 to 2011-02-11
      lab_1 exam: occurred 2011-01-05 09:30 AM
      lab_2 exam: occurred 2011-02-07 12:30 PM

      As lab_1 exam's timestamp falls into the encounter_1's date range, thus the lab_1 exam is linked to encounter_1. Same as lab_2 exam, it is linked to the encounter_2 by comparing the date range.

      The above was taken from QRDA-76 Jira cases link: https://jira.oncprojectracking.org/browse/QRDA-76?jql=text%20~%20%22multiple%20encounters%20per%20measure%22

      We are seeking clarity in cases such as these where multiple encounters exist within a QRDA-I, particularly within evaluation of EH measures. With the example from above: If those encounters existed and they are being processed for example through Stroke2 CMS104v3: Should both of these episodes of care be evaluated by the stroke algorithm, and produce distinct pass/fail/exclusion/exception results for each of these episodes? If so is there someplace within documentation that clearly specifies this. Or is it by design Stroke2 CMS104v3 would limit which of those encounters (ie. through Occurrences) would be evaluated?

      We are also looking for clarification on how to interpret the Occurrence clauses in the STK algorithms as they apply to Non-Elective Inpatient Encounters. Do these occurrences apply to the contents of a QRDA files (as a whole), or do they apply to the contents of one or more episodes of care contained within the QRDA file?

      If the occurrences apply to the contents of an episode of care, then the terminology of “Occurrence A of $EncounterInpatientNonElective” seems to be misleading, as there can only be one Inpatient Encounter per episode of care for Inpatient measures.

      Lastly, is there an option for hospitals to build QRDA files as patient based OR episode of care based, or are QRDA files always built as patient-based files?

            matthew.tiller Matthew Tiller
            bpate BJ Pate (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: