Submitting to QPP - A Quick Start Guide

[Developer Group for QPP APIs]

The QPP Submissions window closes in the next two weeks. For those developers who have not yet sent requests to the Submissions API, we've put together a few resources that may be useful:

API Documentation
We maintain developer documentation that explains both how to use the API and provides definitions to the various objects in the API. You can access those here: https://cmsgov.github.io/qpp-submissions-docs/

You can also see relevant examples of payload submissions to API endpoints and test your own input in our public sandbox here: https://qpp-submissions-sandbox.navapbc.com/#/

Accessible Endpoints
Registries and QCDRs can create measurementSets and add them to any submission object. In practice, this means that with your organization API key, you are authorized to send POST requests to these two endpoints: https://qpp.cms.gov/api/submissions/measurement-sets and https://qpp.cms.gov/api/submissions/measurements. You can learn more about these permissions in the Google Developer Group post here: https://groups.google.com/d/msg/qpp-apis/mZTborxePxE/HaqvQvVLAwAJ

Note that the base URL for the API is https://qpp.cms.gov/api/submissions/. Please remember to make your request with the following key value in the header: "Authorization: Bearer [YOUR API TOKEN]."

Other Helpful Links
You may find these other Developer Google Group posts helpful as you use the API.

• Submissions Window Opening Announcement - https://groups.google.com/forum/#!topic/qpp-apis/S7tCtLFS21w
  
• Scoring Explainer for 2017 Qualified Registries and QCDRs - https://groups.google.com/forum/#!topic/qpp-apis/um3Vslh3iPo
  
• QRDA III Conversion Options Available - https://groups.google.com/forum/#!topic/qpp-apis/FBC_WBpWnbw
  
• Announcement: Update to QPP Submissions API Rate Limit Policy + Recommendations for API Integrators - https://groups.google.com/forum/#!topic/qpp-apis/61vuyigtgFg
  
• Known Bugs and Issues - https://groups.google.com/forum/#!topic/qpp-apis/BiO5nstREDw

How to Get Technical Support for the API
For urgent technical questions about the production API (https://qpp.cms.gov/api/submissions), or to report issues with the API that are impacting your operations, contact the Quality Payment Program Service Center at Q...@cms.hhs.gov or 1-866-288-8292.

Non-urgent technical questions about the production API or the public developer sandbox (https://qpp-submissions-sandbox.navapbc.com) can be posted in this QPP APIs Google Group, where they will be answered within four business days. We recommend searching for an existing post about your question before making a new post, as there are over 300 threads covering a wide range of topics.

For questions about QPP measures, scores, policy or how the program works, please contact the Quality Payment Program Service Center at Q...@cms.hhs.gov or 1-866-288-8292.

[abhijeet mahajan]

Thanks.

Could we also get details on what will be the restrictions on using the QPP Sandbox and PROD APIs after the submission window for 2017 data is closed ?

I am specifically interested in knowing the availability of Preview score API.

Thanks,

Abhijeet

[Shane Jarrell]

Bump!

--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/qpp-apis.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/e52a6ec1-e201-49d1-8d11-0e5305c837ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sarah White]

Hi Abhijeet and Shane,

From our developer documentation here: https://cmsgov.github.io/qpp-submissions-docs/

After March 31, 2018, 2017 Qualified Registries and Qualified Clinical Data Registries who have an API token will not be able to access write and update endpoints in the production environment. In other words, the following endpoints, which were available during the submission window, will no longer be accessible:

MeasurementSets

• POST https://qpp.cms.gov/api/submissions/measurement-sets
  
• PUT, PATCH, POST, DELETE https://qpp.cms.gov/api/submissions/measurement-sets/{id}
  

Measurements

• POST https://qpp.cms.gov/api/submissions/measurements
  
• PUT, PATCH, POST, DELETE https://qpp.cms.gov/api/submissions/measurements/{id}
  

Attempting to access any of these endpoints after March 31, 2018 will return a 401 error.

POST https://qpp.cms.gov/api/submissions/submissions/score-preview will still be accessible, as this data is not persisted. Please remember that this endpoint will not return a score for special scoring scenarios.

GET https://qpp.cms.gov/api/submissions/submissions/{id}/score will also remain accessible. Please note that this endpoint returns the score for a submission object, and does not represent the final score for a TIN/NPI.

The public sandbox will still be accessible after the close of the submissions window. Please keep in mind that /score-preview in this environment acts the same as in production - it does not return scores for special scoring scenarios and applies to 2017 submission scoring.

Sarah White

Business Analyst

Nava

Bump!

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/qpp-apis.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/e52a6ec1-e201-49d1-8d11-0e5305c837ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/qpp-apis.

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/CAB0U4zFMvhVWGg_Q71vNBVRLCTe8DsYBhYx%2BiMCw8HQtnXpyug%40mail.gmail.com.

[Sarah White]

Hi Abhijeet,

Please keep in mind that this endpoint uses 2017 QPP program information. We'll have more information about the public sandbox and future use of these resources when we know more about the Year 2 developer program. Unfortunately, I don't have a specified timeline for that right now.

Sarah White

Business Analyst

Nava

On Thu, Mar 22, 2018 at 3:17 PM, abhijeet mahajan <abhije...@gmail.com> wrote:

Thanks Sarah. One final question. From the other posts and QPP Web site readings, the preview score API was supposed to be available only for year one. Is that still valid or the availability of preview score API has been extended ?

And if it's extended then till what time ?

Abhijeet

Bump!

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.

Visit this group at https://groups.google.com/group/qpp-apis.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/e52a6ec1-e201-49d1-8d11-0e5305c837ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.

Visit this group at https://groups.google.com/group/qpp-apis.

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/CAB0U4zFMvhVWGg_Q71vNBVRLCTe8DsYBhYx%2BiMCw8HQtnXpyug%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/qpp-apis.

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/d22e0a22-272b-4f1a-8c17-ed2c3276bacf%40googlegroups.com.

[abhijeet mahajan]

Hi Sarah,

Could you or anyone from the QPP Dev program please confirm if the preview score API will be available for the 2018 submissions.

Will help us to setup the expectations for us from the business side.

 

Thanks,

Abhijeet

[Sarah White]

Hi Abhijeet,

Yes, the /preview-score endpoint will be available. It's not currently available for 2018 until the Developer Preview is ready in the upcoming weeks.

Sarah White

Business Analyst

Nava

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/2831f830-dc37-416c-bb4f-787fc5944050%40googlegroups.com.

[abhijeet mahajan]

Thanks Sarah. 

[Sarah White]

Please email the QPP Help Desk at Q...@cms.hhs.gov

Sarah White

Business Analyst

Nava

On Tue, Oct 16, 2018 at 2:05 PM Pavan S <pavan...@gmail.com> wrote:

Hi

Were Authentication Token for QCDR Sent out yet? we did not receive anything for QCDR. We, however, received the token for Registry.

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/d25a3ec3-edd9-4dc2-b1be-0fd00f8bdca4%40googlegroups.com.

[Pavan S]

I am reaching out for clarification on how to identify the EHR measures that will be submitted via a QCDR. 

For example, if a clinician was going to submit the EHR measure 001 via QCDR how should the EHR measure be identified in the json request that is be submitted CMS. 

Is there a specific format for that ? or we can simply say EHR001.

[Sarah White]

Hi Pavan,

The measure id does not change. You'll just need to mark isEndToEndReported = true. 

You can see an example of this in this thread: https://groups.google.com/d/msg/qpp-apis/jOcn06aG9cU/H4Rb0J9nAQAJ

A scoring explainer about these kinds of measures can be found in this thread: https://groups.google.com/d/msg/qpp-apis/jOcn06aG9cU/H4Rb0J9nAQAJ

In the future, for topics unrelated to a thread, please start a new topic post in the Google Group. Thanks!

[Pavan S]

Is the Score Preview Available yet?  We were getting an error “The request was aborted: Could not create SSL/TLS secure channel.” So wanted to check