The Joint Commission

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Short Demo for Logic Explorer in the DDSP (duration: 5:22 minutes) click the link or copy/paste the following text in your web browser:

https://attendee.gotowebinar.com/recording/5577215987372462336

Purpose: 

The Joint Commission’s Direct Data Submission Platform (DDSP) provides HCO staff with a Logic Explorer to assist in researching and understanding how the patient data processed against the eCQM specifications.

How to Use:

On the Quality Improvement page, click on the magnifying glass next to the QRDA I document needing to be researched.  The Source Viewer's "Logic Explorer" will automatically open.

To access the "Source Viewer", click on the 'Mode' drop-down box on the right-hand side of the box and select "Source Viewer".  To toggle back to "Logic Explorer", click on the 'Mode' drop-down box again and select "Logic Explorer".

Screenshot view of the platform quality improvement page indicating the view options within Source Viewer.

You may receive the message “Alert: The Logic Explorer may not function properly because the QRDA has warnings.”  If this is the case, and Logic Explorer is not working as expected for the QRDA I document, go back to the Data Accuracy page and review the warning messages that were generated for the document.  If Logic Explorer is working as expected, then close this message box and continue working within Logic Explorer.

Using the Logic Explorer:

Once in the page, it will population with:

  • On the upper side of the page, QRDA file description appear.

    • Measure

    • Reporting Quarter

    • Patient ID

    • Filename

    • Processing Date

  • On the Lower side of the page, the CQL logic with all the definition expended appear.

    • A Blue check mark means that the encounter met the definition of that portion of the measure.

    • A Red cross mark means that the encounter does not meet the definition of that portion of the measure.

(CQL logic example screen print pending)

Next steps if an encounter definition is not passing the measure: review the conditions of the definition within the source viewer to determine if the file contains those conditions in order to trouble shoot and resolve the issue.

  • No labels