[CYPRESS-2006] CMS108v8 - 2020 reporting year Cypress testing CAT1 file is failing for IPP Created: 04/02/20 Updated: 04/03/20 Resolved: 04/03/20 |
|
| Status: | Closed |
| Project: | CYPRESS Issue Tracker |
| Component/s: | None |
| Type: | Question | Priority: | Moderate |
| Reporter: | Sanu Philip (Inactive) | Assignee: | David Czulada |
| Resolution: | Resolved | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
13_Nora_Simmons_32_CAT-1.xml
16_Nora_Simmons_input.xml
Cypress Screen_Error.png
Patient_Cypress_Info.docx
|
| 2020 Reporting Period Hosp Inpt eCQMs: |
CMS108v8/NQFna
|
| Cypress Version: | cypress 5.2.0 |
| Description |
|
Hi Team, This is Regards to CMS108v8 for 2020 reporting year Cypress testing, And we created CAT1 file which is failing for IPP. As per our understanding the CAT1 file should qualify, since Patient Obstetrics codes which is way back in 2017. Patient having Obstetrics codes ICD10CM: O00.80 Time Elements: Prevalence Period Start: 2017-04-10T08:00:00.000Z Prevalence Period End: 2017-04-10T11:00:00.000Z
Version - cypress 5.2.0 Measure - CMS108v8 Attached Cypress input file and CAT1 files. We are running on AWS instance. Please review. Regards, Sanu |
| Comments |
| Comment by David Czulada [ 04/02/20 ] |
|
Sanu Since the diagnosis is nested within the encounter (in the file 13_Nora_Simmons_32_CAT-1). Is it being interpreted as the following (the text below is from the QRDA Implementation Guide). Since the Obstetrics diagnosis is not relevant to the encounter on 2020/05/18 it should not be nested within the encounter template. Another note, an Encounter Diagnosis should be reporting using the "2.16.840.1.113883.10.20.22.4.80" template. -Dave Czulada QDM Attribute: Diagnosis is a coded diagnosis/problem addressed during the encounter. Diagnosis attribute is intended to capture ALL diagnoses, including principal diagnosis. This is represented through entryRelationship to Encounter Diagnosis template as specified in the Encounter Activity (V3) parent template. |
| Comment by Cypress Team (Inactive) [ 04/02/20 ] |
|
Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day |