Developer Preview
CMS Web Interface Developer Preview
The Developer Preview environment allows developers to build direct integrations with other software to test programmatically submitting Quality Payment Program (QPP) performance data to CMS. The API’s functionality in the Developer Preview closely matches that of the QPP system that is in production.
Anyone may continue to test the current iteration of the Developer Preview environment through our Interactive Documentation.
The CMS Web Interface API base URL for the Developer Preview is: https://preview.qpp.cms.gov/api/submissions/web-interface
What 3rd party developers can do with the Web Interface API
Using the data exposed through the API, developers can:
- Submit Patient Data
- View & Prepare Samples
- Confirm or Skip Patients
- Track Performance
- View Measures Specifications
Getting Started
You will need a Developer Preview user account to connect to the Developer Preview for the CMS Web Interface via a preferred API tool.
-
If you do NOT have a Developer Preview user account you will need to:
a. Navigate to preview.qpp.cms.gov.
b. If you have a Production HARP account, you’ll proceed to Step 1 of the process where you enter your Production Username and Password. Then follow the steps to create a Developer Preview user account and password.
c. If you do not have a Production HARP account, you’ll need to create a Production HARP account by following the link on the page, and then come back to complete the steps to connect your Production HARP account and create a developer preview user account and password.
Authentication
Once you have successfully registered for a Developer Preview user account you will need to obtain an authorization token for the next steps. You can do this by following steps 1 thru 3 here.
Provisioning organizations for testing
Once you have a developer preview account you will need to associate your account with an organization that you can use to test with. To provision organizations follow steps listed here. NOTE: These endpoints require a token from the Authentication step above in an Authentication header on the requests. The request should look like this:
curl -X "PUT" "https://preview.qpp.cms.gov/api/synthetic-data/reserve" \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <your-auth-token-here>' \
-d $'{
"scenarioType": "SINGLE_PRACTICE",
"password": "some-password-for-users"
}'
Once you have linked an organization to your account you can use the fake users that were created to directly obtain a token without MFA using the AuthN endpoint. You can test to make sure the organization link was successful by hitting the GET /organizations endpoint.
You can now test your integrations and submit data for any of the organizations returned on this endpoint.
Please Note
Any data submitted in the Developer Preview will not count toward a MIPS-eligible clinician or group’s final score in the Quality Payment Program.
Since the Developer Preview is an integration environment for the CMS WI API, it may be changed in ways that break backward compatibility and is not subject to any service-level guarantees or deprecation policy.
ACOs participating in the Medicare Shared Savings Program (MSSP) are required to report through the APM Performance Pathway (APP) for purposes of assessing their quality performance for that program. MSSP ACOs using the CMS Web Interface Developer Preview will automatically be assigned program name app1 so that the submission is counted towards the APP.
Where to go for support
Send test Web Interface API requests in the Interactive Documentation.
Contact the QPP Service Center.
