This has been fixed in Cypress 2.6.1 and Cypress 2.7.0 released yesterday. They can be downloaded by following the links below.

https://github.com/projectcypress/cypress/wiki/Cypress-2.6.1-Install-Instructions
https://github.com/projectcypress/cypress/wiki/Cypress-2.7.0-Install-Instructions

-Dave Czulada

Ritesh-

Thanks for issuing this concern. Cypress will be releasing a 2.6.1 version. This version will allow the submission of any data for any measures the vendor is certifying. Any data outside these measures will be treated as an error. This should alleviate your concern.

-Dave Czulada

Hello ,
It means ,we will be need to generate "QRDA Category I" files as per measures specific ,addtional/extra data from other measures need to be ignored.
But i have one more confusion about Input data that are provided for certification ,
Is it per measures specific "QRDA category I files" Or combination of measures data per patient .

Hi David,

Sorry for the late reply. I too have sent an email with the image attached. We went ahead and implemented a value set filter during report generation, so this is a non-issue for us going forward.

Thanks,
Smith

David,
We have send a message with attachments..

ritest-

Could you provide the image? If you can't attach the image to this JIRA ticket, please send a message to talk@projectcypress.org. It would be great if you could have the Subject reference this JIRA ticket and the body of the email include your comment above.

It would also be great if you could attach one of the files you used to certify with Cypress 2.4.1.

Thanks in advance.
-Dave Czulada

Adding myself as a watcher since we're receiving these errors as well. We always get them in 2.6.0 for all measures. We have certified for version 2.4.1 last year as well but for 37 measures only. Last year we got them as warnings(Attached image of 2.4.1). We are certifying for all measures this year for version 2.6 and when we download test data and upload data with respect to measure we get these errors. Attached image of 2.6.0.

Providing information that is outside the scope of a measure is an error and not a warning. These errors should be treated as errors and not as warnings.

-Dave Czulada

Smith

I just ran these through a Cypress 2.4.1 i have running locally and the "warnings" show up as errors similar to what you would see in Cypress 2.6.0. Could you try including the image in the attached zip file.

-Dave Czulada

Dave - is there any update on the guidance from ONC?

Apologies. Could not attach image.

Hi,

Adding myself as a watcher since we're receiving these errors as well. We'd often get them in 2.4.1 (last version we certified against) as warnings with the same verbiage. Attached image of 2.4.1 (warnings) vs 2.6 (errors) with same measure, different patients.

Smith

Ryan-

We are still working with ONC to get the official guidance language. I will keep you posted.

-Dave

Hey Dave,

Is there any update on the official guidance? We don’t see this as an error. From your comment above, we have code 99201 and value set 2.16.840.1.113883.3.526.3.1252 which is for CMS-147/NQF-0041. But the QRDA file has this measure defined in the measure section. This is still a valid QRDA file according to the HL7 specifications and only contains entries for value sets of the measures defined in the measure section.

Ryan-

The msg_type parameter is a remnant in the Cypress code and is no longer used. This error is in fact an error, and not a warning. I'm working to find the official guidance on only providing information relevant to a measure in a QRDA Cat I file and will post it here.

-Dave

Yes, I guess our question is if this should really be an error. The text of the error mentions msg_type=>:warning and it is still valid QRDA-I xml. It's just extra data.

Ryan

This error is thrown when a file includes information outside the scope of a particular measure.

For example one of your attached patients Elmer Vasquez (QRDA-cde-408919) has an entry for an office encounter on October 27th with code 99201 and value set 1.16.840.1.113883.3.526.3.1252. This value set is not included in CMS144 and therefore this encounter should not be included in your QRDA file. You should only be providing an entry for value set 2.16.840.1.113883.3.464.1003.101.12.1001.

-Dave Czulada

I've attached the zip file. We were testing CMS 144 Heart Failure (HF): Beta-Blocker Therapy for Left Ventricular Systolic Dysfunction (LVSD).

Ryan-

We have not seen this behavior before. What measures are you testing? Also, could you attach the QRDA I zip file you are submitting?

-Dave