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

Import of data from Cypress for calculation

XMLWordPrintable

    • Icon: Other Other
    • Resolution: Answered
    • Icon: Major Major
    • None
    • None
    • Priscilla Mark-Wilson
    • 678-391-2722
    • Hide
      In regards to question: For the capture and export testing, if we go for modular certification, aren't we supposed to import the QRDA 1 data?

      The answer is “no.” There is no expectation that “capture” (170.314(c)(1)incorporates the import of a QRDA 1 document in a complete EHR.

      In regards to question: Also, if a Vendor chooses to do manual entry, what can be done about “extra” test data that the Vendor’s system cannot capture?

      It is not true that if manual import is done that fewer patients would be offered. The patients for the test are created in advance of choosing to either download them as QRDA Cat I documents or HTML, the number would be the same the format would be different. There may actually be more data included in the HTML output of the records as opposed to the QRDA Cat I as the Cat I export adheres to the QRDA Cat I scoop and filter convention.

      In regards to question: Is it expected that the EHR system import the test data directly into the medical record, or is importing it into a calculator piece acceptable for all stages of testing?

      For the capture and export testing, the data should be entered manually through the clinical application user interface. For the import and calculate testing, either manual entry through the clinical application user interface or automated input via the QRDA Category I XML is allowed.
      Show
      In regards to question: For the capture and export testing, if we go for modular certification, aren't we supposed to import the QRDA 1 data? The answer is “no.” There is no expectation that “capture” (170.314(c)(1)incorporates the import of a QRDA 1 document in a complete EHR. In regards to question: Also, if a Vendor chooses to do manual entry, what can be done about “extra” test data that the Vendor’s system cannot capture? It is not true that if manual import is done that fewer patients would be offered. The patients for the test are created in advance of choosing to either download them as QRDA Cat I documents or HTML, the number would be the same the format would be different. There may actually be more data included in the HTML output of the records as opposed to the QRDA Cat I as the Cat I export adheres to the QRDA Cat I scoop and filter convention. In regards to question: Is it expected that the EHR system import the test data directly into the medical record, or is importing it into a calculator piece acceptable for all stages of testing? For the capture and export testing, the data should be entered manually through the clinical application user interface. For the import and calculate testing, either manual entry through the clinical application user interface or automated input via the QRDA Category I XML is allowed.

      While the import of data from Cypress is not explicitly required in the test script, it is highly recommended. In addition, in reviewing the information about Cypress from MITRE (on websites, and in the Demo and Q&A session recording from January), they indicate that if manual entry is done, there will be fewer patients offered, reducing the rigor of the test, and also that each patient may include data from more than the CQMs that the vendor is interested in certifying, while the import data will be stripped of any data that is not explicitly required for the CQMs to which the . Thus, a vendor who will not be certifying for all CQMs and who chooses to do manual entry may be presented with patient data that includes elements the vendor system is not capable of capturing. However, choosing to import the data into the record (as opposed to the calculator) is not trivial. Potentially, this would require the system to create a patient file in addition to “importing” the data, in light of MITRE’s assertion that in order for the calculations to be properly tested the system must not have any data in it at the start of this portion of the test. Also, have this capability in a vendor’s system is somewhat concerning in terms of data security and integrity: if the system can “import” information from a QRDA format under testing conditions, what would stop and end user from importing such data in a real situation.

      Assuming a complete EHR system, is it expected that the system import the data directly into the medical record, or is importing into a calculator piece acceptable for all stages of testing?

            julia.skapik Julia Skapik (Inactive)
            priscilla Priscilla Mark-Wilson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved:
              Comment Posted On: