[CYPRESS-228] Cypress 2.4 is using outdated root IDs NQF0338 CMS26 in the QRDA III file. Created: 09/20/13 Updated: 06/20/18 Resolved: 12/12/13 |
|
| Status: | Closed |
| Project: | CYPRESS Issue Tracker |
| Component/s: | None |
| Type: | Bug/Issue | Priority: | Critical |
| Reporter: | Siemens (Inactive) | Assignee: | Samuel Sayer (Inactive) |
| Resolution: | Delivered | Votes: | 0 |
| Labels: | cypress | ||
| Solution: | Fixed in Cypress 2.4.1 |
| Previous Issue Type: | Implementation Problem |
| Description |
|
The QRDA III file that we upload to Cypress 2.4 is creating errors for missing IDs for measure NQF0338 CMS26 The error states: ” It appears that the error is occurring due to a mismatch in the IDs for numerator, denominator, and IPP. We are using the April 2013 specifications, while Cypress 2.4 appears to be using the IDs for numerator, denominator, and IPP from the December 2012 specifications. We noticed that although there has been no change in the eMeasure version number for this measure, the IDs for numerator, denominator, and IPP have been updated in the April version. Can you confirm that the error generated by Cypress is due to the outdated IDs for numerator, denominator, and IPP. |
| Comments |
| Comment by Siemens (Inactive) [ 09/30/13 ] |
|
We are running Cypress in the environment stated above, i.e. with bundles 2.1.2 and 2.4.0. However, Cypress is failing the QRDA III file uploaded by our quality module, as Cypress is looking for population identifiers from December 2012 version of measure definition for CMS measure 26. Cypress is not acknowledging the population identifiers from the April release of this measure. We would like to know if Cypress will be updated in near future to account for the patient identifiers from the April 2013 version for this measure. In the meantime, we will appreciate any guidance on how we can proceed so that we can pass this measure. |
| Comment by Robert Dingwell (Inactive) [ 09/30/13 ] |
|
If you are running a fresh install with only the 2.1.2 and 2.4.0 bundles and said bundles were loaded without the update measures flag then the 2.1.2 bundle contains the original identifiers and the 2.4.0 bundle contains the updated identifiers. |
| Comment by Siemens (Inactive) [ 09/20/13 ] |
|
Hi Rob, |
| Comment by Robert Dingwell (Inactive) [ 09/20/13 ] |
|
I should add that the same would hold true for a fresh install of Cypress 2.3 with the 2.3.0 bundle and the 2.1.1 bundle. Or if the installation was not created from an upgrade path. |
| Comment by Robert Dingwell (Inactive) [ 09/20/13 ] |
|
CMS26 has a somewhat well known problem in that the measure itself was not updated in April and the version specific identifier remained the same yet all of the population identifiers for the measure were changed. The ONC/CMS stance on this if I recall correctly is that either population group is acceptable. Cypress can support testing either group but it requires some very specific configuration and depending on what you currently have for a system may mean standing up a new instance. This is especially true if you have been upgrading from previous versions. The upgrade path usually includes installing the updated measure bundles with the update_measures=true parameter. This will search for measures in the system by the version specific identifier and then update that measure with the one that is in the bundle that is being loaded. As the December and April releases of the measures each have the same version specific identifier for CMS 26 this will effectively overwrite that measure to whatever the last bundle contained. The easiest way to deal with this is to simply have a fresh install of Cypress and load the 2.1.2 and 2.4.0 bundles. The 2.4.0 bundle will contain the population identifiers from the April release and the 2.1.2 bundle will contain the identifiers from the Dec release. |