The Joint Commission

Known Issues: eCQM

Also see General Known Issues

Also see Chart-Abstracted Known Issues

As of 3/13/2024:

The table below provides the latest issues associated with the most recent release.

DDSP eCQM Issues

Issue #

DDSP Issue

Date Opened

Work Around

Status

Issue #

DDSP Issue

Date Opened

Work Around

Status

4

“Purge selected” is not available

10/3/22

For CY2021, users are not able to “Purge selected” files, but must instead “Purge All”.

Open

8

"QRDA I Errors and Warning" option in Source Viewer to debug issues does not go to the correct line with the issue in the document.

10/3/2022

None

Open

22

User Profile information cannot be updated. The message "Email address is invalid." will appear even though the email address is valid.

11/28/2022

None

Open

23

If an eCQM file upload using 7zip contains a folder, DDSP generates an error and rejects the file.

11/11/2022

Use Windows default zipper when a folder is included in the zip.

Open

30

The eCQM status on the Home page may show incorrect results

2/20/2023

None

Resolved

2/8/2024

31

The DDSP outcome for the Opioid measure has a mismatch with CMS when there are multiple episodes of care for the specific case. This is due to a known Denominator Exclusion logic issue that CQL does not align with the measure intent. Implementation based on CQL is generating a different measure outcome than the implementation based on the measure intent.

This issue has been brought to CMS and measure developers’ attention for potential correction in a future version of the Opioid measure.

This will impact both the 2022 and 2023 versions of the opioid measure definition and may impact ~3% of the Opioid cases. 

2/20/2023

None

Open

34

Misalignment with CMS: For eSTK-6 Denominator Exception logic below, TJC only accepts "LDL-c" lab result as data type of Quantity (xsitype = "PQ") as described by measure definition, while CMS is accepting both Quantity (xsitype = "PQ") and Interval Quantity (xsitype = "IVL_PQ").  If reporting lab "LDL-c" result with data type "IVL_PQ", it will fail Exception for TJC, but will pass for CMS. TJC will work with CMS to align for a future release

5/29/2023

None

Resolved

9/1/2023

35

Misalignment with CMS: File may receive different outcome than CMS if duplicate ED Encounters is reported.  

5/29/2023

 

Resolved

Confirmed with CMS, there is no misalignment between TJC and CMS 

36

eOP-40 STEMI measure Issue:

For CY2023, some ED Encounters may be wrongfully excluded from the initial population if the ED encounter start and end datetime are falling in different quarters after the UTC normalization. This issue is due to the way measure IP logic is written where it requires both encounter start and end datetime to be in the measurement period (see below).  This logic issue will be corrected for CY2024.   

For the IP logics “ED Encounter with Diagnosis of STEMI” and “ED Encounter with Encounter Diagnosis of STEMI”,  

CY2023

…EDEncounter.relevantPeriod during "Measurement Period"

CY2024 (corrected):

…EDEncounter.relevantPeriod ends during day of "Measurement Period"

8/16/2023

None

Open

37

The Joint Commission (TJC) has not been enforcing the Schematron edits to check for the inclusion of Payer information in QRDA files as CMS does. QRDA files without payer information are not receiving Schematron errors

11/13/2023

 

Resolved

11/27/23

38

When performing the 'Purge’ and ‘Upload' actions in quick succession can lead to the generation of duplicate rows in the 'Result by Measure' table on the Quality Improvement page, as well as in the Submission Dashboard on the Submit Data page. These duplicates may display the same or varying results. 

Impact: If data submission is carried out while these duplicate rows exist, only the first row displayed in the table will be stored in the data warehouse. This may lead to inaccuracies, as the first row may not reflect the correct data. 

1/19/2024 

We advise hospitals that encounter duplicate rows to refrain from submitting data until this issue is fully resolved. 

Re-opened

2/26/2024

39

Incorrect Display of eCQM Status on Home Page -  For hospitals that have performed both a 'Withdraw' and a subsequent 'Submit' action, there is a known display issue on the DDSP application's home page. The eCQM status may incorrectly show as “Withdrawn” on the home page, despite the correct “Submitted” status being displayed on the eCQM submit page. 

1/5/2024

Hospitals that have completed the 'Submit' action, can verify the eCQM status directly on the eCQM submit page. This page accurately reflects the current eCQM submission status. 

Resolved

2/2/24

40

Slow Processing of QRDA Files Containing eHH-1 Measures. The DDSP system is currently experiencing significant delays in processing QRDA files specifically when they include the eHH-1 measure in the reported data.

2/7/2024

Technical staff are aware of the issue and is actively working on implementing a solution to expedite the processing of affected QRDA files.  Hospitals are advised to temporarily hold off uploading QRDA files that contain the eHH-01 measure until our fix is fully implemented. This will prevent extended waiting times for file processing.

Resolved

2/27/2024

41

Timestamp error on Submit Data Page: On the Submit Data page, the timestamp displayed in the “Results generated on” field is incorrect. Users are observing that this field displays the date and time of an older file that was processed, rather than reflecting the timestamp of the latest file processed.

2/27/2024

Currently. there is no workaround to correct the displayed timestamp from the user's end. Our IT has been actively working on the fix.  Before the correction is in place, we recommend users verify the actual processing results by reviewing all pages to ensure all files have completed processing and records are captured for all uploads before Submit. 

Opened

2/27/2024

42

Outcome mismatch with CMS’s for HH-02 when there are multiple episodes of care cases. Measure does not include logic that appropriately constrains the denominator exclusion to the specific qualifying encounter. Implementation based on CQL is generating a different outcome than the implementation based on the measure intent.  

This will impact 2023 versions of the HH-02 definition. 

2/27/2024

None

Opened

2/27/2024

43

Max Logic in eSTK-6 does not work as expected if 2 range values are provided in 2 different Laboratory Test Performed data elements that satisfy “Encounter with MAX LDL less than 70 mg per dL” logic

2/29/2024

None

Opened

2/29/2024

44

Incorrect Display of eCQM Status on Home Page: A few HCO’s show the incorrect status ‘eCQM Status: No Files Uploaded” on their Home Page when;  

-they already submitted data -or- 

-under the heading ‘eCQM Submission Status’ and they have counts listed for both “No Files Uploaded” and “Unsubmitted” 

3/1/2024

Currently, there is no direct workaround to the home page eCQM Status displaying issue. Our IT is actively working on the fix.  Before the correction is in place, we recommend users verify the status by reviewing the Upload Data and Submit Data pages.

Opened

3/1/2024

45

Incorrect eHH-02 Measure Outcome calculation due to UTC Offset handling. TJC DDSP processes files that contain data with varying time zones incorrectly. This issue specifically affects cases where timestamps for the start and end of an encounter have different UTC offsets due to daylight savings time changes, which leads to miscalculating the outcome as Numerator instead of Denominator.

3/12/2024

There is no workaround for CY2023. The issue is scheduled for correction in CY2024

Opened

3/12/2024

 

©The Joint Commission, All Rights Reserved
The Joint Commission is a registered trademark of The Joint Commission.