[CYPRESS-272] Patient B, Eye_Adult missing attribute required to meet numerator for CMS167 Created: 11/12/13 Updated: 06/20/18 Resolved: 12/12/13 |
|
Status: | Closed |
Project: | CYPRESS Issue Tracker |
Component/s: | None |
Type: | Question | Priority: | Minor |
Reporter: | Matthew Dugal | Assignee: | Renee Rookwood (Inactive) |
Resolution: | Delivered | Votes: | 0 |
Labels: | None |
Solution: | This will be fixed as part of the next point release. It has the same root cause as |
Previous Issue Type: | Logic affecting more than 1 eCQM |
Description |
Patient B, Eye_Adult is expected to populate the numerator. The numerator includes the following statement: The patient has a diagnostic study result but the result code is not in the list for 'level of severity' so it incorrectly does not meet the numerator. The Data Criteria for the above statement: Group Value Set list for 2.16.840.1.113883.3.526.3.1283 includes codes: 193349004, 312903003, 312904009, 312905005, 390834004, 408411003, 408412005 The patient QRDA generated by Cypress includes one Macular Exam entry: <entry> This entry does not seem to meet the criteria of 'Level of Severity of Retinopathy Findings' as described by the numerator. |
Comments |
Comment by Samuel Sayer (Inactive) [ 02/12/14 ] |
Thomas, I've addressed this in a few topics, but I just posted a new one to the Talk List (https://groups.google.com/d/topic/project-cypress-talk/Ys2VAv-akMc/discussion). Please follow the instructions in the post and re-download the Cat I document. If you're still seeing this issue, please post here. |
Comment by Thomas Ryabin (Inactive) [ 02/12/14 ] |
This issue does not appear to be fixed in Cypress 2.4.1. When I downloaded the QRDA Cat 1 file for Eye_Adult B I only found one instance of the code "193349004" (Level of Severity of Retinopathy Findings), and it appeared in an entry for "Communication from provider to provider", and not in an entry for "Diagnostic Study, Result". |
Comment by Samuel Sayer (Inactive) [ 11/22/13 ] |
This will be fixed as part of the next point release. It has the same root cause as |
Comment by Matthew Dugal (Inactive) [ 11/22/13 ] |
Is there any update on this issue? |