Questions on the Opt-in Eligibility API

[abhijeet mahajan]

Question on the sample result on this page : https://cmsgov.github.io/qpp-eligibility-docs/opt-in

GEThttps://qpp.cms.gov/api/eligibility/secure/opt-in?year=2019

Authorization	Bearer [Auth Token]
Qpp-Opt-In-Entities	000456789|1234567890,000987654

"data": [
    {
        "tin": "000456789",
        "npi": "1234567890",
        "isOptInEligible": true,
        "optInDecisionDate": "2020-01-27T16:57:38.646Z",
        "isOptedIn": false,
        "year": 2019,
        "runNum": 1
    },
    {
        "tin": "000987654",
        "isOptInEligible": false,
        "optInDecisionDate": null,
        "isOptedIn": null,
        "year": 2019,
        "runNum": 1
    }
]

Can we get all possible result examples for this API ? 

I am specifically interested in the possible combinations of 'isOptInEligible' and 'isOptedIn' flags. 

Thanks,

Abhijeet

[abhijeet mahajan]

Hello team,

It would be great if we could get some answers on this one. Possibly in the following format ?

isOptInEligible	isOptedIn	Interpretation of the state	Comments from QPP Dev group
TRUE	FALSE	Voluntary reporting
TRUE	TRUE	Opted in
TRUE	NULL	What does this mean and is it a possible valid response ?
FALSE	NULL	What does this mean and is it a possible valid response ?
FALSE	TRUE	Can never happen\Invalid response but need confirmation
FALSE	FALSE	What does this mean and is it a possible valid response ?

Thanks,
Abhijeet

[Abeeb Ayodeji]

Good Morning Abhijeet, 

We're in the process of working up a resposne and should have something for you shortly. 

Warmest Regards,

Abeeb Ayodeji

[abhijeet mahajan]

Thanks Abeeb. Will wait for it.

I forgot to mention this in my earlier posts. 

Hopefully your team will be publishing the error message structures for the eligibility status API as well.

Abhijeet

[Craig Powell]

Abhijeet

It helps to know isOptedIn is not impacted or connected to isOptInEligible.  Users can elect to opt in / out regardless of their Opt In Eligibility status.  That might seem odd but we have a use case that drove that functionality.  So, effectively, these two fields are independent and don't interact with each other.  With that in mind....

isOptedIn      TRUE = the user has selected to Opt In

                      FALSE = the user has selected to Opt Out 

                      NULL = the user has made no selection

isOptInEligible   TRUE = the user qualifies as one that can choose whether they want to opt in/out

                          FALSE = the user does not qualify as one that can choose to opt in/out

  

Let me know if you have additional questions

Craig 

QPP Team 

Eligibility

[abhijeet mahajan]

Thanks Craig. This helps.

Could you please share the scenario you are referring to which has driven your team to make this design decision. Will help us to understand it better.

Abhijeet

[Craig Powell]

Field research indicated organizations representing many people (registries for example), want the ability to indicate all are electing to opt in regardless of the eligibility status of any given individual.  

Craig