QRDA III Conversion tool Sandbox Error 500

76 views
Skip to first unread message

Scott Alphonso

unread,
Jan 22, 2018, 3:11:21 PM1/22/18
to Developer Group for QPP APIs
Good Afternoon,  We are getting an internal 500 error on the conversion tool sandbox at https://qpp.cms.gov/developers/conversion-tool-sandbox . I have attached the error file.  What would cause an error like this?  We also get an error on the QPP production submission but it simply says "unknown error".

Any help is greatly appreciated.  


error.json

Scott Fradkin

unread,
Jan 23, 2018, 2:40:22 PM1/23/18
to Developer Group for QPP APIs
Offhand, I'm not sure what would cause this error.  I did double check with a known valid file and it converted successfully.

If you can post the file you are trying to convert, that would be helpful.  Please remove or mask ALL PII from the file before posting: TIN, NPI, etc.

Thanks,
Scott

Scott Alphonso

unread,
Jan 23, 2018, 4:27:03 PM1/23/18
to Developer Group for QPP APIs
Thanks for the reply Scott.  We will work on stripping out the pertinent information.  Would you be able to send or point me to a sample valid file that we can compare too?  

thanks,
Scott A

Scott Fradkin

unread,
Jan 23, 2018, 5:10:52 PM1/23/18
to Developer Group for QPP APIs
We maintain a set of sample files in our public repository: https://github.com/CMSgov/qpp-conversion-tool/tree/master/sample-files

Thanks,
Scott

Scott Alphonso

unread,
Jan 23, 2018, 6:14:47 PM1/23/18
to Developer Group for QPP APIs
Attached is the file we were testing with all the important info ripped out.  
Qrda_CatIII_Provider_2_20180117031906.xml

Scott Fradkin

unread,
Jan 24, 2018, 12:18:01 AM1/24/18
to Developer Group for QPP APIs
Thanks for the file.  Our development team will take a look and dig into this.  If we determine that a code fix is required I'll post back here with an estimate on when we think any fixes will be promoted to production.

Thanks,
Scott

Scott Fradkin

unread,
Jan 24, 2018, 5:53:28 PM1/24/18
to Developer Group for QPP APIs
Hi Scott,

Here's an update for you.

The file you submitted has some numerator and denominator elements that have an older template extension date.  In the XML snippet below my name you'll see that the commented out line has an older, incorrect date on it while the uncommented out corresponding line has the correct date extension.  The template id 2.16.840.1.113883.10.20.27.3.28 should be using an extension date of 2017-06-01.

However, we were able to determine that there is an existing bug relating to correctly parsing some child elements of a measure.  The fix for that bug will be in production either tomorrow or Friday.

We will also be making some validation changes to be more helpful when we detect that a submitted file might not have been created using the most recent version of the QRDA-III IG.  For your reference, here's a link: https://ecqi.healthit.gov/system/files/eCQM_QRDA_EC-508_0.pdf

Thank you for bringing this to our attention and thank you for your sample file!

Thanks,
Scott

-----------

<organizer classCode="CLUSTER" moodCode="EVN">

              <templateId root="2.16.840.1.113883.10.20.24.3.98" />

              <!--<templateId root="2.16.840.1.113883.10.20.27.3.28" extension="2016-09-01" />-->

  <templateId root="2.16.840.1.113883.10.20.27.3.28" extension="2017-06-01" />

              <id root="93261f9e-9835-4d53-a3c2-85f02903707d" />

              <statusCode code="completed" />

              <reference typeCode="REFR">

                <externalDocument classCode="DOC" moodCode="EVN">

                  <id root="2.16.840.1.113883.3.7031" extension="ACI_MR_1" />

                  <text>Medication Reconciliation</text>

                </externalDocument>

              </reference>

Scott Alphonso

unread,
Jan 24, 2018, 8:55:30 PM1/24/18
to Developer Group for QPP APIs
Thanks Scott.  We did use the most recent version of the QRDA III IG but that does not mean a few other changes were not missed.  I'll review it again comparing to the file we generated and then submit a new file when you have the fix in production.

Scott Alphonso

unread,
Jan 26, 2018, 12:51:58 PM1/26/18
to Developer Group for QPP APIs
Hi Scott,

Any word on fix being published?  I made changes, even reviewed the spec and compared.  All looks good on our side now as far as I can tell.  I have attached the latest test submission.  We still receive the same error at this time.

thanks,
Scott A
Test.xml
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
0 new messages