Uploaded image for project: 'QRDA Issue Tracker'
  1. QRDA Issue Tracker
  2. QRDA-655

Issue with Assessment Performed template - Documentation not qualifying

XMLWordPrintable

    • Icon: QRDA-I Standard QRDA-I Standard
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None

      Related to CYPRESS-1342 and CYPRESS-1055

      We are testing our 2018 QRDA 1 files and In the file attached, 'Time of Delivery' is not being evaluated (valueset 2.16.840.1.113762.1.4.1045.28) in the Cypress Validation tool.
      Testing: 2017 Bundle for the 2018 Reporting Period, Hospital Quality Reporting for the EHR Incentive Program, QRDA I

      Cypress responded:
      ("If a QRDA document contains multiple QDM Element instances for the same Quality Datatype, each associated with a different value set (which means that the value of sdtc:valueset attribute is a different value set OID), and these QDM Element instances originate from the same source EHR data instance (e.g., the same code, same time stamp, etc.), then the id element of these QDM Element instances should have the same value. Identical id elements indicate they originate from the same data instance."

      Our interpretation of this guidance is that Identical Ids are only to be used when representing a QDM element with a code that is in multiple valuesets. In all other cases, unique ids should be used. We will be investigating this further.)

      We were under the impression that all data elements related to an encounter would share the same ID so we would just like confirmation that the information provided by Cypress saying that each element associated to an encounter needs a unique id is correct, whether that be through a unique id root or a shared root with unique extensions.

      Thanks

        1. QRDA_1_1.xml
          20 kB
          Matt Hardman
        2. QRDA Example.xml
          4 kB
          Matt Hardman

            matthew.tiller Matthew Tiller
            matt.hardman Matt Hardman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: