OPT in - can someone please explain how will i be notified if a physician who opted in but is not eligible is doing it voluntarily?

[Theresa Rangel]

OPT in - can someone please explain how will i be notified if a physician who opted in but is not eligible is doing it voluntarily?

Also API doesnt seem to be working - i keep getting response as unauthorized. Any guidance will be appreciated 

[Christopher Szeluga]

Hi Theresa,

I assume you are attempting to use the Eligibility API. Could you please provide some additional detail about the request you're trying to make? In particular:

• Are you testing an opt-in request in the Developer Preview environment? The endpoints will not be enabled in Production until the beginning of the submission window.
• What API endpoint are you attempting to utilize?
  
• Are you using a registry token, OAuth token, or user token with your request?

A response of "unauthorized" means the token you are using is not authorized for the resource you are attempting to view Eligibility information for.

You can check the opt-in eligibility status for a clinician using the public /api/eligibility/npi/:npi endpoint, and checking the individualScenario.isOptInEligible flag. Likewise, the individualScenario.isOptedIn flag indicates the clinician's opt in decision. The opt-in eligibility status is also available via the Eligibility Lookup tool.

Thanks,

Chris

[Theresa Rangel]

Yes i am using developer preview

I am using this end point https://prview.qpp.cms.gov/api/eligibility/secure/opt-in?year=2019

I am using the same token which i am using for MIPS - OAuth token is different?
In the body i am putting this

{

  "tin": "000000006",

   "optIn": "true"

}

[Theresa Rangel]

Sorry my mistake  .. https://www.screencast.com/t/oTsnpygENEsi i just need a sample as to how to send the data does it take in header! i could not find proper guide on implementing the API

[Christopher Szeluga]

Theresa,

From the screenshot, it looks like the name of your attributes in the body does not match what we are expecting. You should be passing in tin, not taxpayerIdentificationNumber. We have examples of queries on our documentation here which you can use. 

Furthermore, it appears that the TIN you are attempting to use is only 8 digits. A TIN is 9 digits in length. If you are using the OAuth token you use for the Submissions API, that is supported, but keep in mind you will need to be explicitly granted authorization for the resource you are trying to opt-in for.

Thanks,

Chris

[Theresa Rangel]

https://www.screencast.com/t/BgOG4CfKq9hl .. when using taxpayerIdentificationNumber gettign this error

https://www.screencast.com/t/8anlkeR7xke9 when using tin i get not found .. is it possible to provide us a sample that we can test