[CYPRESS-1541] File failed import error for 2019 eCQMs Created: 11/19/18 Updated: 04/03/19 Resolved: 04/03/19 |
|
Status: | Closed |
Project: | CYPRESS Issue Tracker |
Component/s: | None |
Type: | Bug/Issue | Priority: | Moderate |
Reporter: | Reggie Zhang (Inactive) | Assignee: | Lauren DiCristofaro (Inactive) |
Resolution: | Resolved | Votes: | 0 |
Labels: | KnownBug4.0.1, QRDA-I |
Attachments: |
![]() ![]() ![]() |
Description |
When validating various 2019 reporting period eCQMs for CAT1 Export with Cypress 4.0.1, I am encountering a "File failed import" error message and this seems to be prevalent with all files regardless of measure or patient. I've attempted to diagnose the root cause using the schematron to no avail and the validation utility provides no additional information. Attached are the Cypress test deck xmls for CMS 104 and the export xmls. UPDATE 1: After additional investigation, we've found that it seems to have been caused by an id missing in the ACT element of Encounter, Performed but we believe that this should not be causing an error since this is no longer mandatory for the Reporting Year 2019 Version of QRDA (R5) despite being required for the previous version (R4). The files provided by Cypress still have an id at that location so submitting our export xml files modified to have the id at that location will not generate the "File failed import" error. It's possible this might affect other templates as well. |
Comments |
Comment by Lauren DiCristofaro (Inactive) [ 04/03/19 ] |
Addressed in Cypress 4.0.2 https://www.healthit.gov/cypress/release.html#4.0.2 |
Comment by Lauren DiCristofaro (Inactive) [ 12/20/18 ] |
Hi Reggie, |
Comment by Reggie Zhang (Inactive) [ 12/17/18 ] |
Has there been any progress towards a resolution for this issue yet? |
Comment by Alex Liu [ 12/03/18 ] |
It appears that Cypress utilizes the act ID as the identifier for a particular encounter located at entry/act/id. We believe the more appropriate "encounter" identifier should be the ID located within the Encounter Performed (V4) template using the encounter/id element. This is also supported in The HL7 QRDA I STU Release 5 standard in Section 3.18.1 Encounter Performed (V4): "Encounter id is represented using the encounter/id element, the encounter/id/@root (or combined with @extension, if @extension is present) uniquely identifies an encounter." |
Comment by Lauren DiCristofaro (Inactive) [ 11/20/18 ] |
Hello Reggie, |
Comment by Cypress Team (Inactive) [ 11/19/18 ] |
Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day |