[CYPRESS-168] Cypress v2.3.1 QRDA Cat 1 Smoking Gun Tests Need To Be Relaxed Created: 07/26/13  Updated: 05/14/18  Resolved: 09/12/13

Status: Closed
Project: CYPRESS Issue Tracker
Component/s: None

Type: Question Priority: Major
Reporter: Rob McCready (Inactive) Assignee: Samuel Sayer (Inactive)
Resolution: Delivered Votes: 1
Labels: QRDA-I

Issue Links:
Duplicate
is duplicated by CQM-780 Issue w/ the Excel Spreadsheet for ma... Closed
is duplicated by CYPRESS-328 CAT I files are requiring codes from ... Closed
is duplicated by CYPRESS-166 Expected Value Set OID seems incorrec... Closed
is duplicated by CYPRESS-171 Expected Value Set OID seems incorrec... Closed
Relates
relates to CYPRESS-930 ONE office visit must satisfy TWO val... Closed
relates to CYPRESS-634 Valueset missing in 155v3 CAT I File Closed
Solution: This issue appears in both Cypress 2.3.1 and Cypress 2.4.1. The solution to this problem is that Cypress should consider any one of the clinical sections returned in the QRDA Category 1 as "passing." If/When you run into this issue during certification, please have your proctor contact the Cypress team so we can confirm that the error is due to this bug.

http://projectcypress.org/issue168.html

This is known to occur for the following measures:
CMS165/NQF0018
CMS155/NQF0024
CMS147/NQF0041
CMS133/NQF0565
CMS161v1/NQF0104
CMS75
CMS90
CMS74
Previous Issue Type: Other

 Description   

The issue a vendor discovered is that Cypress is required to provide various alternatives for the specific clinical codes associated with a clinical concept. However, the behavior of those various clinical codes is not always consistent within the measure.

On this case, the SNOMED and CPT codes are both "legal" for the concept on this measure. However, the sections that should be provided with the QRDA Category 1 XML are different based on which code the EHR vendor selects, because of "bleeding" issues within the CQM.

What results is that Cypress can sometimes expect two or more sections to be present in the QRDA Category 1 XML for one code, but only one section to be present in the QRDA Category 1 XML if the EHR vendor opts to select another code. When these problems occur, EHR vendor should pass certification on this particular issue even though Cypress reports a failure.

The solution to this problem is that Cypress should consider any one of the clinical sections returned in the QRDA Category 1 as "passing", effectively relaxing some of the constraints on the Cypress "smoking gun" tests which were introduced in Cypress v2.3.1.

Detailed Example for Jira Issue #168



 Comments   
Comment by David Czulada [ 05/29/15 ]

Kelli-

Which version of Cypress are you using? In Cypress 2.6.0 "missing" smoking gun data is only treated as a warning.

If you are seeing something to the contrary, could you please open up a new JIRA ticket and post the QRDA file along with a screen shot of the error message.

Thanks
-Dave Czualda

Comment by Kelli Klippenstein (Inactive) [ 05/28/15 ]

This is also an issue with CMS 61 for patient B, Heart_Adult. Cypress expects them to have four lab results corresponding to LDL, HDL, Triglycerides, and Total Cholesterol. Per the June 2014 specs they should not need a Total Cholesterol if they have the other three (LDL, HDL, Triglycerides).

Comment by David Ross (Inactive) [ 03/14/14 ]

Transitioning ticket back to OPEN

Comment by Brett Marquard [ 03/10/14 ]

Hi, Sapna,

I agree - this is occurring with CMS 74.

Take care,
Brett

Comment by SAPNA MALANI [ 03/07/14 ]

This issue is also with CMS 74:Primary Caries Prevention Intervention as Offered by Primary Care Providers, including Dentists

Thanks !

Comment by David Ross (Inactive) [ 03/04/14 ]

Renee,

Unfortunately the disposition on this issue has not changed: if it is encountered during certification, the testing lab should contact the Cypress team to confirm that the error is due to this bug. If it is this particular bug, the EHR vendor should still pass certification.

There is not an ETA on a fix yet.

Thanks!

-Dave

Comment by Renee Fromhold (Inactive) [ 03/04/14 ]

I've seen this issue with CQM 138, and 165 also. Anytime a snomed is provided with an alternate CPT, the CPT is not accepted when validating the QRDA 1 files. Is this going to be addressed? Or is the error correct (not an error)? Cypress version is 2.4.1. I first reported the issue in January for CQM 139. It was acknowledged as a bug, but there has not been a resolution. It's now March. Will this be addressed in the near future? We manually enter test data, and having to go back and manually replace the cpt with the snomed can be time consuming.

Comment by Ben (Inactive) [ 02/26/14 ]

Thanks for the confirmation Samuel. FYI we're also seeing the same issue in CMS-155 (exact same patients & problematic codes).

Comment by Samuel Sayer (Inactive) [ 02/25/14 ]

In regards to CMS147, this indeed looks like an issue with the smoking gun validator. If/When you run into this issue during certification, please have your proctor contact the Cypress team so we can confirm that the error is due to this bug. This is the guidance we discussed with ONC.

Comment by Ben (Inactive) [ 02/24/14 ]

Samuel, to give you some additional information to help troubleshoot the issue: we are seeing an error in CMS-147 for templates A, Diabetes_Peds and B, Diabetes_Peds in value sets 2.16.840.1.113883.3.526.3.1012 and 2.16.840.1.113883.3.464.1003.101.12.1022 respectively. The issue seems to be that the single procedure is mapped to both a SNOMED and a CPT, but those codes are in different value sets.

Please let me know if there is any additional information I can give to help with this. Also, I see that the status of this issue was changed back to "In Progress", but could we remove that this was "delivered" too? It makes the issue hard to find for people who are running into this.

Comment by Samuel Sayer (Inactive) [ 02/03/14 ]

This issue is also appearing in Cypress 2.4.1. We will update this issue with guidance when available.

Comment by Jean Colbert (Inactive) [ 09/12/13 ]

Fixed in Cypress v2.4 Release.

Generated at Fri Apr 26 15:11:33 EDT 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.