Uploaded image for project: 'CYPRESS Issue Tracker'
  1. CYPRESS Issue Tracker
  2. CYPRESS-1139

CMS161v5 - question with unique encounters for patient as reported in QRDA 1

XMLWordPrintable

    • Icon: Question Question
    • Resolution: Answered
    • Icon: Moderate Moderate
    • Logic affecting more than 1 eCQM

      Testing CMS161v5 on Cypress 3.1.0 patient deck (see attached)
      Patient Joel Hunt has 6 Encounter Performed QRDA 1 entries but has only 4 unique encounters

      Encounter, Performed: BH Outpatient encounter
      ICD-9-PCS: 89.03
      CPT: 99214
      SNOMED-CT: 390906007
      February 23, 2015 8:00am - February 23, 2015 9:00am

      Encounter, Performed: BH Outpatient Psychotherapy
      SNOMED-CT: 108313002
      CPT: 90837
      ICD-9-PCS: 94.42
      ICD-10-PCS: GZ72ZZZ
      March 9, 2015 8:00am - March 9, 2015 9:00am

      Encounter, Performed: BH Outpatient Psychotherapy
      SNOMED-CT: 183382003
      CPT: 90837
      ICD-9-PCS: 94.37
      ICD-10-PCS: GZ51ZZZ
      April 21, 2015 8:00am - April 21, 2015 9:00am

      Encounter, Performed: BH Outpatient encounter
      SNOMED-CT: 390906007
      ICD-9-PCS: 89.03
      CPT: 99215
      April 28, 2015 8:00am - April 28, 2015 9:00am

      Each of the 6 EncounterPerformedAct templates have unique id root values
      however the EncounterPerformed entry in the entryRelationship node has 4 unique values across the 6 entries.

      We are importing what we see as 6 unique encounters but are failing the measure test with a higher than expected count error:
      Calculated value (2.0) for DENOM (1EC810C4-E6D2-4ED6-AE02-A0BF4D675F05) does not match expected value (1.0)
      Calculated value (2.0) for IPP (9CDC88D7-31DA-44F1-9348-CFDD29F4B20B) does not match expected value (1.0)

      Questions:
      1) Why are there 2 of the 4 EncounterPerformed entries wrapped with unique EncounterPerformedAct templates when they appear to represent the same event? Is this intentional, expected or an issue in the export?
      2) Our understanding was that each entry with a unique <id> element value is a unique event but this file does not conform to that logic, is this unique for Encounters?

      Thanks in advance for your help.

            dczulada David Czulada
            johnmahoney John Mahoney
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: