[QRDA-931] Test submissions fail in CMS due to this error. Created: 11/02/20  Updated: 12/22/20  Resolved: 11/13/20

Status: Resolved
Project: QRDA Issue Tracker
Component/s: None

Type: QRDA-I Standard Priority: Moderate
Reporter: Jeff Gremban (Inactive) Assignee: Yan Heras
Resolution: Answered Votes: 0
Labels: CMS_0071, Error, QRDA-I

Attachments: XML File QRDA_10522840.xml    
Impact: QRDA I files being rejected with error CMS_0071 when submitting to CMS. TJC accepts the files.
Institution/Name: Rural Wisconsin Health Cooperative
Contact Name: Jeff Gremban
Contact Email: jgremban@rwhc.com
Contact Phone: 9205622775

 Description   

Attached QRDA sample file of what we have test submitted to CMS.



 Comments   
Comment by Yan Heras [ 11/09/20 ]

Hi Jeff,

The HQR team has confirmed this is a defect on their end. Fix to this will be applied in the coming weeks. 

Thank you. 

 

Comment by Yan Heras [ 11/05/20 ]

Hi Jeff,

Below is an update from the HQR team from their investigation so far, we will keep you posted with the findings.

For QRDA_10522840.xml (CMS_0071 error), we are seeing that it is failing our well formed check with the following error.

[Fatal Error] :1:1: Content is not allowed in prolog.

The latest update is that there were hidden characters at the beginning for the XML file. Most likely due to UTF-8 with BOM. The team will continue to look into this. 

 

Comment by Yan Heras [ 11/02/20 ]

Thanks for confirming. The file looks fine, we will reach out to the HQR team and have them look into this from their end.

Comment by Jeff Gremban (Inactive) [ 11/02/20 ]

Yes I did another 2 test submissions today and still get the error on every file in the zip.

Comment by Yan Heras [ 11/02/20 ]

Hi Jeff,

Do you still see the CMS_0071 error when you try re-submit today?

Thanks

Comment by QRDA-ICF [ 11/02/20 ]

Thank you for submitting a ticket to the QRDA JIRA Issue Tracker. Our experts are reviewing your ticket and will provide feedback as soon as possible. Thank you for your patience.

Generated at Sun Aug 31 08:14:47 UTC 2025 using Jira 10.3.8#10030008-sha1:cdaed80cecc964184c5b19b002388d56f96e274e.