Developer Preview End Date & API Token Change

[Developer Group for QPP APIs]

Developer Preview Tokens Expire November 1, New Tokens Coming

The Developer Preview was scheduled to end on November 1, 2017, but we are extending it to December 15, 2017 to allow additional time for testing. Existing API Tokens will expire on November 1 and Developer Preview participants will need to begin using new Production API tokens that we will issue them before that date.

If you are a Developer Preview participant, our team will automatically issue you a Production API Token using a process similar to the one that we used to distribute the Preview API Tokens. All you need to do in order to continue testing is to replace your existing API token with the new one. None of the endpoints are changing and none of the data you have submitted will be disturbed. The new tokens will remain valid throughout the QPP Year 1 reporting and not expire until December 1, 2018.

Roadmap to Production

We will continue to iterate the API in the following ways between now and December 15, 2017:

• fix bugs
  
• add the ability to submit QRDA III files via the API
  
• add the ability to submit QCDR Measures via the API
  

On December 15, we will shut down the endpoints in preparation for the opening of the official QPP Submissions window on January 1. During this time the endpoints will be inaccessible and all data in the system will be deleted. When the official QPP Submissions window opens on January 1, Production API Token holders can begin submitting official data for QPP Program Year 1 (2017) using the same endpoints at the same URLs as they have been using in the Developer Preview program.

[David Michael]

Hi,
Could you please update, When would the QCDR measures are being accepted ?

Thanks
David

[Jonathan Sullivan]

We are working toward adding support for the submission of QCDR measures via the API to the Developer Preview on December 4.

[Jonathan Sullivan]

I have two updates:

• API Developer Preview participants can test submitting QRDA III files via the API now by using the /converter endpoint at https://qpp.cms.gov/api/submissions/converter
  

• We are working toward adding support for the submission of QCDR measures via the API to the Developer Preview on December 4.
  

On Friday, October 20, 2017 at 3:04:15 PM UTC-4, Developer Group for QPP APIs wrote:

[Pawan Jindal(MyMipsScore.com)]

Hi Jonathan, 

Is this not available on the sandbox? It is returning a "not found" error on https://qpp-submissions-sandbox.navapbc.com and Postman.

[Mari Miyachi]

Yes Pawan - it is only available via the developer preview not the sandbox.

[Darrell Burns]

We did not receive a new token.  What process do I follow to get the production API token?

[zarana....@eclinicalworks.com]

We received the New Token but it gives bellow response if we use new Token.Kindly suggest for same.

{

    "error": {

        "type": "NotFoundError",

        "message": "Not Found"

    }

}

On Friday, October 20, 2017 at 3:04:15 PM UTC-4, Developer Group for QPP APIs wrote:

[Zarana Thakkar]

I am Getting Below error via Developer Preview API https://qpp.cms.gov/api/submissions

[Ivana Ng]

Darrell - please email q...@cms.hhs.gov.

Ivana Ng

Product Manager

Nava

On Mon, Nov 6, 2017 at 10:25 AM, Darrell Burns <drb...@gmail.com> wrote:

We did not receive a new token.  What process do I follow to get the production API token?

--
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/b16c2938-525d-4d61-a8b7-a9582e1e2f81%40googlegroups.com.

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

[Ivana Ng]

Hi Zarana - 

That does not look like an authentication error. Please provide the following info so I can triage:

1. Endpoint 

2. Http method (e.g. GET, POST)

3. Request payload

4. Response payload

Thanks,

Ivana

Ivana Ng

Product Manager

Nava

--

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/8c454f1e-a32e-4dfd-a156-47c2b0721766%40googlegroups.com.

[Zarana Thakkar]

Hi Ivana,

Please find below information.Kindly help for same.

1. URL: https://qpp.cms.gov/api/submissions
   
2. HTTP Method: POST
3. Request Payload:

{

  "programName": "mips",

  "entityType": "individual",

  "taxpayerIdentificationNumber": "000123456",

  "nationalProviderIdentifier": "0123456789",

  "performanceYear": 2016

}

             4.Response Payload:

{

    "error": {

        "type": "NotFoundError",

        "message": "Not Found"

    }

}

Please FInd Below Screen Shot For same.

Thank you

Zarana

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.

[Ivana Ng]

Hi Zarana - 

Your url is incomplete. The base url is https://qpp.cms.gov/api/submissions, and you must append the name of the endpoint you want to reach. In this case, the actual url is  https://qpp.cms.gov/api/submissions/submissions

That said, as a registry, you have certain permissions when using the Submissions API. Please refer to this post for more info.

-Ivana

Ivana Ng

Product Manager

Nava

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/c8ebcf20-54be-4aec-9c1c-0f962f3f19eb%40googlegroups.com.

[Zarana Thakkar]

Thank you 

[Darrell Burns]

I did contact them.  Case CS0018999

Still no reply.  We really need this token to continue our testing!

On Monday, November 6, 2017 at 9:23:10 AM UTC-7, Ivana Ng wrote:

Darrell - please email q...@cms.hhs.gov.

Ivana Ng

Product Manager

Nava

On Mon, Nov 6, 2017 at 10:25 AM, Darrell Burns <drb...@gmail.com> wrote:

We did not receive a new token.  What process do I follow to get the production API token?

--
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.

[Jonathan Sullivan]

Hi Darrell, I apologize for the disruption to your testing. I am trying to track down your ticket. In the meanwhile, what is the name of your organization?

[Darrell Burns]

We were able to get our token.  Thank you Jonathan. 

[Jairo R Rodriguez]

HI, we have tried to submit to the developer preview URL below using Postman and using one of the many QRDA file examples in the Qpp-conversion-tool but when submitting we are getting a bad request error. When I add the ContentType then it tells me the multiform needs a boundary, removing it just gives out bad request. Do you have maybe a postman collection that you can share?

[Shane Jarrell]

Please confirm that there WILL be a sandbox API available somewhere, somehow available for continued testing after the 15th? How are we supposed to go live when the API is still changing? Once the API has been hardened, I assume everyone would need to test again.

On Friday, October 20, 2017 at 3:04:15 PM UTC-4, Developer Group for QPP APIs wrote:

[Jonathan Sullivan]

Jairo, could you please create a separate thread for this question and include the contents of your submission so that we can better respond to your question? Thanks.

[Jonathan Sullivan]

The existing sandbox API will continue to be available after December 15th. The API is feature complete with the exception of the ability to submit QCDR measures. This last remaining feature will be added to the Developer Preview and the sandbox at the beginning of December.

[anuj Kumar dwivedi]

Hi,

I have Developer Preview API token and tried to submit JSON data to CMS but it is giving error as like attached screen shot. Could you please assist me what exactly issue there.

Also please let me know, How can i get "entityId".

Thanks,

Anuj

[Shane Jarrell]

Thanks! Whew I thought it was going to be gone.

[Jonathan Sullivan]

I think you are trying to POST a submission object and you can't do that. Read this thread for details: https://groups.google.com/forum/#!topic/qpp-apis/mZTborxePxE