Opt In/Opt Out

[Brett Thom]

Hey team,

Got what I hope is quick questions to answer! I tried asking them during the call today but think I may of worded it confusingly.

1. So say a provider is low threshold eligible and hasn't made their op in/out decision. I know the measurement set endpoint will error, but could we still get a preview score from the score-preview endpoint?
2. When will the opt-in/opt-out endpoint be in the dev preview? I thought you said by the end of the month.... but I tried a GET on the  https://preview.qpp.cms.gov/api/eligibility/secure/opt-in endpoint and it looks like it is returning things. Is it just a work in progress till end of the month?

Thanks for your time!

Brett

[Craig Powell]

Brett,

For Question #2

Opt In status is fully functional and available today in the Dev Preview endpoint.  It was added recently.  For additional reference, check this informational page

https://cmsgov.github.io/qpp-eligibility-docs/opt-in 

Craig

[Sarah White]

Hi Brett,

Yes the /score-preview endpoint is still available. As a reminder, the Submissions API features a provider profile stub in the Developer Preview and production environments for the /score-preview endpoint. You can view how that stub interacts in our Dev Docs here - https://cmsgov.github.io/qpp-submissions-docs/developer-preview. It will not use the real eligibility of a provider on that endpoint. Only /score will in production.

And just to add to Craig's answer - yes the endpoints are live, but to test them fully with a test user you can set as being opt-in eligible, there are a few other things we're wrapping up still. So while you can call those endpoints, the info about that test provider won't be aligned with the Submissions API just yet. We can put out a post to clarify!

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/fa1a24af-e0e9-4128-bbc9-b0199afcffa4%40googlegroups.com.

[Brett Thom]

Awesome thanks for info!

So is that why every tin/npi or tin combo I try on  https://preview.qpp.cms.gov/api/eligibility/secure/opt-in?year=2019 returns as not a valid tin/npi? We will need that test user first?

Thanks

Brett

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

[Abeeb Ayodeji]

Hello Brett,

Do you mind giving me more insight to the data that you are trying to submit? Thank you!

Warmest Regards,

Abeeb Ayodeji

[Brett Thom]

Hey Abeeb, 

So I just hitting that endpoint with  TINs/NPIs with different combinations and every single one I tried returns an error.

            "error": {

                "code": 404,

                "name": "NotFoundError",

                "message": "TIN-NPI combo not found."

            }

Is there a set of test TINs/NPIs or do I have to wait for the new "test" endpoint to exist?

Thanks!

Brett

[Abeeb Ayodeji]

Thank you Brett,

Do you mind sending a sample of a request that you're sending? 

Warmest Regards,

Abeeb Ayodeji

[Brett Thom]

Hey Abeeb,

So I am sending a GET to https://preview.qpp.cms.gov/api/eligibility/secure/opt-in?year=2019
With the following 000456789|1234567890,000987654 in the header Qpp-Opt-In-Entities

Along with the Bearer token in the header

Thanks

Brett

[Abeeb Ayodeji]

Good Morning Brett,

Thank you for getting this to me. It seems you have sent TIN's and NPI's that don't exist, which would explain why you received a not found error.

Warmest Regards,

Abeeb Ayodeji

[Brett Thom]

Hey Abeeb,

So is there any way to see what "live" NPIs/TINs are in the preview site for testing purposes?

Thanks

Brett

[Abeeb Ayodeji]

Hello Brett, 

There is no way to currently see the live NPIs/TINs that are in the preview site for testing, but that functionality is being added in the near future. However, we're currently working to find a way to help you get what you need in the mean time. I will be in touch with you again before this week is over. Thank you!

Warmest Regards,

Abeeb Ayodeji

[Brett Thom]

Thank you for all your help!

[Brett Thom]

Hey Abeeb,

Do you have any update on this?

Thanks!

Brett

[Abeeb Ayodeji]

Good Morning Brett,

Yes! Do you mind telling me what exactly you are trying to test? What is your goal of testing the data as well? 

Warmest Regards,

Abeeb Ayodeji

[Brett Thom]

Hey Abeeb,

I am trying to test scenarios where we actually have a live NPI and TIN so we can test the check eligibility and opt-in or opt out the clinician. Right now every combination just says not-found, so we can't test much. We mocked out what we could but we can't finalize our development or testing without it. 

Thanks

Brett 

[Abeeb Ayodeji]

Thank you Brett!

You will need to reserve a synthetic dataset. The link below outlines the steps involved:

https://preview.qpp.cms.gov/api/data-faker/synthetic-data/docs/index.html?_ga=2.197315247.1241032394.1574801834-226808749.1574451817

Please let me know if you have any other questions or issues. I'm be happy to set some time up for a brief sync up if need be. 

Warmest Regards,

Abeeb Ayodeji

[abhijeet mahajan]

Hi Abbeb,

I am also trying to test the integration with this API. I followed the steps you've mentioned in the above email chain.

I was able to 'reserve' the test scenarios using the QPP Portal (Dev Preview) itself. But after that I am unable to change password for the security official role for that scenario.

My understanding of how we need to test is :

1. Figure out who is the security official for that scenario - either from the portal or from API
2. Use the QPP Auth APIs to get the token (will prefer disabling the MFA for this testing since this is dummy security official anyway) for this security official using the QPP Auth API
3. Use the token obtained in Step 2 to test the opt-in eligibility for the dummy TIN or TIN-NPI 

Is this how we are supposed to test. Currently I am not able to change the password for the dummy security official in the given scenario so can't move ahead.

Could you or someone from your team help me with this case.

Thanks,

Abhijeet

[Brett Thom]

Hey Abeeb,

This helps. So I can /scenarios endpoint and get a return fine... but as soon as I try using the /reserve endpoint I get a key-value error. Is the token passed differently across these endpoints?

{

    "message": "'x' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer x'."

}

Thanks

Brett 

[Brett Thom]

Never mind, I know what I did, disregard!

[Brett Thom]

So noticing two things now... When trying to reserve a scenario on the reserve endpoint, it seems to work but I get the following included in the return JSON

    "provisioningDetails": "Your passwords were not set correctly, please manually set user passwords.",

And then when I try hitting the list endpoint I get the following error, might be because the logins weren't created right?

{

    "statusCode": 400,

    "message": "ExpressionAttributeValues contains invalid value: Supplied AttributeValue is empty, must contain exactly one of the supported datatypes for key :login"

}

[Brett Thom]

Another problem is every scenario I try doesn't seem to be optineligible when I then check those TINS/NPIs on the eligibility endpoint. 

If it makes your job easier, I can join a call

Thanks
Brett 

[abhijeet mahajan]

For  my question on Dec 2 : I am able to test this API now with our Dev preview registry token. 

But the scenarios I have tested seems to be returning isOptinEligible : false.

Do we have like a list of dummy TIN\TIN-NPI combos which will return different results ? We don't want to test with our actual prod data yet.

Any help either from QPP dev group is appreciated.

Thanks,

Abhijeet

[Brett Thom]

Is there any way I can get some help with my questions above? Even though the opt in endpoint is functional we cannot really do much with it without functional test data.

Thanks

Brett

[Satyajeet Aparadh]

Hello Abeeb,

We are facing the same issue, can you let us know if there are a combination of TIN/NPIs that we can test? 

Also is there a way to create test data?  

--

[Sarah White]

Hi all,

There are combinations of TIN/NPIs you can test with, but there's one more fix we need to get that corrected and running in Developer Preview. We're working on it right now to get it resolved as soon as possible. Once that's confirmed I'll post a separate post on the forum with directions on how to use them.

[Nathanael Vissia]

Hi Sarah, 

Has there been any progress with the TIN/NPI combinations that we can use for Opt-in testing in developer preview? If so, can you point me in the right direction? 

--N

[Brett Thom]

Any update on this?

Thanks

Brett

[Hari Krishna Jubburu]

Sarah,

Can you give us the ETA for this fix? Because, as the submission is going to open up in a short time, we need to develop and test this opt-in functionality for our registry application.

Best Regards

Hari Krishna 

To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/a4bfdfa0-edb6-4cd2-8898-19e8a57d3deb%40googlegroups.com.

[Sarah White]

Hi all,

You can already develop and test this functionality and have been able to do so - my understanding is these endpoints on the Eligibility API are available in the Developer Preview environment. You can learn about that in their documentation here - https://cmsgov.github.io/qpp-eligibility-docs/opt-in

The only part remaining that is not yet available is a set of predefined users to test changing a flag to true or false for opting in. Right now, without that, all TINs or TIN/NPIS are not going to appear eligible for this. You should still go ahead and test checking eligibility and setting a decision - setting a decision can be made even if that tin or tin/npi is not eligible to opt in as the decision will not matter for participation or scoring. 

The test TINs and TIN/NPIS we hope to have up this week or next. Once those are available you can then fully test the reaction of the submissions API.

Below is a breakdown of how the Submissions API will react for TINs or TIN/NPIS who are eligible to Opt In and HAVE NOT made a decision to opt in or stay voluntary:

Endpoint	Behavior if opt-in decision needed
POST /submissions	Throws UnprocessableEntityError (422)
POST /measurement-sets	Throws UnprocessableEntityError (422)
POST /measurements	Throws UnprocessableEntityError (422)
GET /measurement-sets/:measurementSetId	Throws NotFoundError (404)
GET /measurements	Throws NotFoundError (404)
GET /measurements/:measurementId	Throws NotFoundError (404)
GET /submissions	Returns submissions, msets empty, warning added to submission object
GET /submissions/:id	Returns submission, mset empty, warning added to submission object
GET /submissions/:submissionId/score	Mset emptied before calling scoring engine, adds warning to scoring response
GET /measurement-sets	Returns an empty measurement-set

[Craig Powell]

Hari, 

We understand the urgency of being able to test Opt In.  We're completing QA on it now and will have it out ASAP.  I'll continue to provide updates.  

Craig 

[Craig Powell]

Update:  We're estimating the ability to reset the Is Opted In value in DevPre (to support repeated testing) will be available mid next week.  

Craig 

[abhijeet mahajan]

Hi Craig,

Any updates on this one ?

Thanks,

Abhijeet

[Kishor Rasure]

Hello Team,

Do we have any update on this? Do we have test data available for opt-in?

[Brett Thom]

Hey team,

Any update on this? We just need some of the scenarios to be isOptInEligible. We tested every other scenario but cannot test ones revolving around opt in eligible clinicians or groups.

Thanks

Brett 

[Michelle Ingle]

Brett and all, 

Please see the update on this posted here: https://groups.google.com/d/msg/qpp-apis/lvx2iikRivo/DkCcMyDLBwAJ

Thanks!

Michelle