QPP Submissions Will No Longer Support XML Format starting January 2, 2020
June 27, 2019

As a reminder, QPP Submissions will no longer support QPP XML format starting January 2, 2020. The QPP Submissions API will only accept requests and return responses in QPP JSON format.

This means that files must be uploaded to the QPP website in either QPP JSON or QRDA III XML. This change improves the Submissions API performance and eliminates security vulnerabilities related to XML.

Who is impacted

The deprecation of QPP XML means that if you’ve ever configured your software to send requests to the QPP Submissions API or provided a file for your client to upload to the QPP website in QPP XML format, you will need to update your software to send those requests in QPP JSON format.

Please review the timeline below for key dates on QPP XML deprecation.

Organizations that already submit in QPP JSON are not impacted.

This does not apply to QRDA III XML. The QRDA III XML converter tool will remain available to convert QRDA III XML to QPP JSON.

Key dates for QPP XML deprecation

  • Summer 2019— The QPP Submissions API Developer Preview environment for Year 3 launches and accepts QPP JSON only. 
    • Developer Preview environment: The QPP Submissions API in this environment will only accept requests in QPP JSON format. 
    • Production environment: The QPP Submissions API in this environment will still accept requests in QPP JSON and QPP XML format. 
    • Interactive documentation (https://preview.qpp.cms.gov/api/submissions/public/docs/): this website will only document the API in QPP JSON/
    • Static documentation (https://cmsgov.github.io/qpp-submissions-docs/): this website will only document the API in QPP JSON.
  • January 2020— The production QPP Submissions API begins accepting Year 3 performance year data. All requests to the production QPP Submissions API on and after this date accepts QPP JSON format only.

The Centers for Medicare & Medicaid Services (CMS) will be posting reminders when each of these key dates through the Google Group for QPP APIs. 

CMS recommends migrating as soon as possible to ensure you don’t experience any disruption.

Where to go for support in migrating to QPP JSON 

Post in the Google Group for QPP APIs, and get feedback and help from the QPP Product Team and the QPP APIs Developer Community.