Eligibility API - find out the Opt-in status for a group or physician

[ksloii]

Hi,

Does the Eligibility API provide a method to find out the opt-in status for a group or physician?

Thanks,

King

[Christopher Szeluga]

Hi King,

Documentation on a specific endpoint for checking the opt-in status will be added to the Eligibility Mini-Site shortly. However, an opt-in eligible flag is already added to places like the Eligibility lookup tool and the authenticated eligibility screens for authorized users of specific clinicians or practices.

Chris

[ksloii]

Thanks Chris!

[SRIDHAR G]

Hi Sarah,

Please confirm if below statements are true regarding Opt-in API

Eligible: either using QPP eligibility tool available on qpp.com or a public eligibility  API call, a provider/practice is MIPS eligible.

1. If provider/practice are eligible to submit MIPS data, a qualified registry can submit their data through Measumentsets API endpoint with out making Opt-in API call.

2. If provider/practice wants to opt-in, they can log in to their EIDM (qpp) account and opt-in through UI, then a qualified registry can submit their data  through Measumentsets API endpoint with out making Opt-in API call.

3. It’s not mandatory for a qualified registry to develop Opt-in API functionality for 2019 reporting year. 

Thanks 

Sridhar

Population Health Analytics 

eClinicalworks 

On Nov 5, 2019, at 1:05 PM, ksloii <king...@gmail.com> wrote:



--
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/5eb90cf8-3f83-450b-90d9-ecd9cc84bc9a%40googlegroups.com.

[Satyajeet Aparadh]

Hello Sarah,

I have a few scenarios on which I need your inputs. 

Consider there are 2 providers, Provider A and Provider B. 

Provider A MEETS all 3 conditions of low volume threshold and is hence eligible

Provider B DOES NOT MEET ANY of the 3 conditions of the low volume threshold and is hence not eligible. 

What will be the API response if we check the Opt-in eligibility status of these 2 providers

1. Will the API provide any error for each of these cases?

2. Will the API return isoptineligible as false? 

-----------------------------------------------------

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

[Andrew Limburg]

Christopher Szeluga,

Currently the it appears that the Eligibility API / Lookup Tool only works for NPIs.  Per the documentation that was released on 11/5, it indicates that we could check status and Opt-In at the Group Level via the Eligibility API.  Is this Group Level Opt-In / Check Status part of an upcoming release?

Thank you,

Andrew Limburg

Part of a Qualified Registry

On Wednesday, October 23, 2019 at 1:36:50 PM UTC-4, ksloii wrote:

[Christopher Szeluga]

Hi Andrew,

We recently released documentation outlining the GET /opt-in status endpoint, which allows you to check the opt-in status for a particular TIN/NPI or TIN. You can use your Registry JWT with this endpoint.

https://cmsgov.github.io/qpp-eligibility-docs/opt-in > "Checking opt-in status".

This endpoint is available in the developer preview environment but is not enabled in production yet.

Thanks!
Chris

[SRIDHAR G]

H Sarah,

Can you please confirm below questions

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

[Sarah White]

Hi Sridhar,

1. Yes.

2. Yes.

3. Only if you are not submitting for an LVT Opt In eligible provider and they do not make a decision. Registries could also log in to the QPP website using their registry credentials and submit a file for such a provider that way. At that point in time the UI would prompt you to make an Opt In decision. So technically, no you don't have to develop the API call, you could go through the UI.

To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/228F53B8-5549-4089-A9E7-7E1D9F076B91%40gmail.com.

[Andrew Limburg]

Chris,

Thank you for that info.

Just had one of our developers try to use that endpoint and it is requiring a token.

Please provide guidance on how we can use the endpoint or how we can get a token.

As we are getting to the end of the year, this is pretty urgent.

Thank you,

Andrew Limburg

[Kevin Perdue]

Hi Andrew,

For me this GET endpoint is working fine.  I am using our registry api token (production), not our developer preview token.  If needed, one way to retrieve is the same place in the UI where your devpre token is on qpp.cms.gov.  In the drop down there should be an option for “Download API Token” (above “Download Developer Preview Token”).  Disregard that this is on the "2018" performance feedback registry dashboard page, that's just where it is.

Using the following, for example, works fine for getting eligibility status through the API. Just replace with your desired TIN(s), TIN/NPI(s), and your registry API token where needed:

curl GET "https://qpp.cms.gov/api/eligibility/secure/opt-in?year=2019" -H "Qpp-Opt-In-Entities: tin1, tin2, tin2|npi1, tin2|npi2, etc." -H "accept: application/json" -H "Authorization: Bearer your-registry-api-token"

Hope this helps,

-Kevin

[Andrew Limburg]

Chris,

For context, we are MIPS Registry.  

We were able to get into the new endpoint. We ran all of our customer's who are reporting at the TIN level through the new endpoint.

Now I have a couple very important questions:

1. Is the data we are getting in response accurate data?
2. If not, when can we can get live production data so that we can validate the Opt In Eligibility status of our clients that we have contracted with.

Andrew

On Thursday, November 14, 2019 at 11:41:50 AM UTC-5, Christopher Szeluga wrote:

[Andrew Limburg]

Thanks Kevin.  That worked for us too.

Andrew

[Kishor Rasure]

Hi Christopher,

Is this endpoint available in the developer preview environment? If not when it will be available as we need to integrate it into our application? Currently, we are getting an error as follows for preview env:

{

    "error": {

        "message": "Authentication is required",

        "type": "JsonWebTokenError"

    }

}

Another question is that only the production URL is working with the production registry token for now?

[Kishor Rasure]

Just to add we are using https://preview.qpp.cms.gov/api/eligibility/secure/opt-in?year=2019 URL. Please let us know the correct way.

[Hari Krishna Jubburu]

Hi Christopher/Sarah,

any update on this?

Best Regards

Hari Krishna 

Please do not include any Protected Health Information (PHI) when responding to this email!  

FIGmd does not transmit via email any healthcare information protected by federal and/or state laws unless authorized by the subject patient or under circumstances where patient authorization is not required. If FIGmd receives PHI directly from a subject patient, we consider this to be an authorized distribution of PHI by the subject patient. 

 

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (or any attachment) is prohibited. If you have received this email in error, please notify the original sender and delete this message (along with any attachments) from your computer and if possible your server.

--
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/3962e049-74a2-4723-b7d3-33152748118e%40googlegroups.com.

[Craig Powell]

Hari

I noticed this question is being tracked and discussed in a separate thread.

https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/qpp-apis/lngfWfY8ZA8

Can we close out this thread and track resolution there?

Craig

QPP Team 

Eligibility