[CYPRESS-201] Risk Category Assessment Depression Screening result codes in QRDA CAT 1 Created: 08/27/13 Updated: 06/20/18 Resolved: 12/12/13 |
|
Status: | Closed |
Project: | CYPRESS Issue Tracker |
Component/s: | None |
Type: | Question | Priority: | Minor |
Reporter: | Robert Allsbrooks (Inactive) | Assignee: | Robert Dingwell (Inactive) |
Resolution: | Delivered | Votes: | 3 |
Labels: | QRDA-I, QRDA-III, TestData, ValueSet, cypress |
Attachments: | 0_GP_Peds_B.html 0_GP_Peds_B.xml 0_Heart_Adult_C.html 0_Heart_Adult_C.xml | ||||||||
Issue Links: |
|
||||||||
Solution: | For Cypress 2.3 and earlier what I would suggest as guidance for the ATLs is that they understand it is a necessity for anyone consuming the Cat I documents for the Depression Screening measures or any other measure that contains a Risk Category Assessment data criteria to be allowed to alter the documents to include the correct coded values. Or that they will need to be modified in the system after the import for the calculation results to match. This is fixed as of Cypress 2.4.1 |
||||||||
Previous Issue Type: | Value Sets |
Description |
In the measure there are numerous references to positive and negative Depression Screening results. We are using the value set codes from the data criteria to search for the result in the patient data. What we have found is that the codes within the value set are not present in the patient data (QRDA Cat I). But we did find a Diagnosis, Active: Depression diagnosis occurred after a Risk Category Assessment: Adolescent Depression Screening. I have attached the files for patients GP_Peds B and Heart_Adult C (from the master list). I've also included the QRDA CAT 1 entries for both adolescent and adult depression screening. Risk Category Assessment: Adolescent Depression Screening entry: <entry> Risk Category Assessment: Adult Depression Screening entry: <entry> |
Comments |
Comment by Robert Dingwell (Inactive) [ 09/17/13 ] |
Rob/Jon, I see what you are saying. After a bit of additional digging this appears to be an issue related to 2.3 and before. Prior to 2.4 the Risk assessment template did not properly deal with coded values and as a result the nullFlavors where produced. Upon looking at the template however the resolution in 2.4 is not correct either as it is rendering the overall depression screening code and not the value code. I believe that we can fix this is a point release within the next few weeks. What I would suggest as guidance for the ATLs is that they understand it is a necessity for anyone consuming the Cat I documents for the Depression Screening measures or any other measure that contains a Risk Category Assessment data criteria to be allowed to alter the documents to include the correct coded values. Or that they will need to be modified in the system after the import for the calculation results to match. |
Comment by Jon Salmon (Inactive) [ 09/17/13 ] |
Per the Master Patient List, the GP Peds B patient from the 2.3 bundle should meet the IPP, Denominator, and Numerator for CMS2v3. To accomplish that, based on the patient data in the HTML and the measure criteria, it needs to meet the following criteria from the Numerator:
As you can see, the Risk Category Assessment result is definitely needed, yet the necessary information, while present in the HTML, is missing from the QRDA. Likewise, Heart Adult C should meet the IPP, Denominator, and Denominator Exclusions for the measure. It should meet the following criteria from the Denominator Exclusions:
As with the other patient, the necessary information is in the HTML but not in the QRDA thus these patients cannot meet their expected populations when processed from QRDA. |
Comment by Robert Dingwell (Inactive) [ 09/16/13 ] |
Rob, I believe when entries like this are encountered it is because the entries where added to meet the criteria that something was done but the value itself for the data criteria that was being targeted did not matter. For example a situation where a measure simply needs to know that a Depression Screening was performed but there was no constraint on the results value. Do you feel that these are being used in a situation where they are matching a result such as positive or negative? |