MIPS eligible clinicians and groups can submit data to QPP using the QRDA III format by following the steps below.
1. Create a QRDA III XML file containing the performance category (Quality, Advancing Care Information, Improvement Activities) data you wish to submit. You must follow the 2017 QRDA III Implementation Guide when creating your file:
CMS has three resources which you can use to test your ability to create a QRDA III file that:
• Complies with the 2017 Implementation Guide, and
• Can be successfully converted by CMS to the QPP JSON format used by the Quality Payment Program
QRDA III Conversion Tool Web App
The first tool is a web application where you can either drag and drop, or select from your computer, a QRDA III XML file and have it converted to QPP JSON. If your file cannot be converted, you will receive detailed feedback.
QRDA III Conversion Tool Open Source Package
The second is an open source package which developers can download and use to create their own conversion application or function for their software.
QRDA III Conversion API Endpoint
API Developer Preview participants can test submitting QRDA III files via the API by using the /converter endpoint. Read our documentation to learn more about how to formulate requests to this endpoint. (Note that this link only serves as documentation, and you cannot actually test the /converter endpoint using that link.)
Note that none of these tools have the same functionality as the SEVT or Cypress tools and cannot be used to test QRDA III files against the full range of possible industry uses.
2. Someone with an EIDM account that is associated with the eligible clinician or group, and which has a Security Official or Submitter role, logs in to
qpp.cms.gov with their EIDM credentials.
3. The user is taken to a landing page where they can choose a performance category (Quality, Advancing Care Information, Improvement Activities) to report. On any of the performance category pages, the user can elect to upload a file.
4. The user can select up to 50 QRDA III XML files at a time, each one containing data for a single eligible clinician (one TIN, one NPI) or for a group of eligible clinicians (one TIN, multiple NPIs). (You cannot include multiple TINs in one API call or file upload.)
5. The system consumes the files and returns a score for each eligible clinician and group via the UI. If any validation error are encountered, the system will report the errors via the UI.