Does eligibility api work on preview

Matthew Yaeger

unread,

Jan 16, 2020, 4:54:02 PM1/16/20

to Developer Group for QPP APIs

Does the eligibility api work in the preview? I used the request on the doc site (https://cmsgov.github.io/qpp-eligibility-docs/opt-in) but I only get error responses

curl --location --request GET 'https://preview.qpp.cms.gov/api/eligibility/secure/opt-in?year=2019' \

--header 'Authorization: Bearer <my token>' \

--header 'Accept: application/json' \

--header 'Qpp-Opt-In-Entities: 000456789|1234567890'

Craig Powell

unread,

Jan 17, 2020, 12:45:18 PM1/17/20

to qpp-...@googlegroups.com

Matthew,

Yes. The Eligibility API works in preview. Where did you get the Opt In Entities? Are they valid test values?

For testing in DevPre Environment, you must first reserve a test data set. Instructions on how to do that can be found at:

https://cmsgov.github.io/qpp-eligibility-docs/tutorials/make-an-opt-in-decision

Look for the section titled "Obtain a test dataset"

Craig

QPP Team

Shane Jarrell

unread,

Jan 17, 2020, 5:21:20 PM1/17/20

to Developer Group for QPP APIs

I don't believe it does work, I'm still getting not found for the LVT scenario where IsOptInEligible = false. It should be true.

Shane Jarrell

unread,

Jan 17, 2020, 5:35:33 PM1/17/20

to Developer Group for QPP APIs

After creating the LVT Scenario I get

{
    "provisioningDetails": "Your passwords were set correctly.",
    "reservedDataSet": {
      "generatedOn": "2019-12-20T20:19:42.636Z",
      "clinicians": [
        {
          "firstName": "Millie",
          "lastName": "Strosin",
          "tins": [
            "000010598"
          ],
          "npi": "0000000296",
          "npiSSN": "000010618"
        }
      ],
      "virtualGroups": [],
      "scenarioType": "LVT",
      "status": "RESERVED",
      "organizations": [
        {
          "name": "LVT Opt-in - Stanton Inc",
          "tin": "000010598",
          "ptan": "TESTPTAN_8S"
        }
      ],
      "generatedBy": "central_generator",
      "users": [
        {
          "firstName": "Millie",
          "lastName": "Strosin",
          "role": "staff",
          "login": "devpre.Mil...@example.com",
          "tins": [
            "000010598"
          ]
        },
        {
          "firstName": "Rocio",
          "lastName": "Russel",
          "virtualGroups": [],
          "role": "security-official",
          "login": "devpre.Ro...@example.com",
          "tins": [
            "000010598"
          ]
        }
      ],
      "id": "a9e07b8b-98ff-4c6c-90f2-98573e1f1be3",
      "name": "LVT Opt-in",
      "reservedBy": "registry.9107439",
      "reservedOn": "2020-01-16T16:10:08.055Z",
      "customName": "GMedLVTTest",
      "customDescription": "GEHRIMED Test"
    }
  }

Then upon lookup I get

{
    "data": [
        {
            "tin": "000010598",
            "error": {
                "code": 404,
                "name": "NotFoundError",
                "message": "TIN not found."
            }
        },
        {
            "tin": "000010598",
            "npi": "0000000296",
            "error": {
                "code": 404,
                "name": "NotFoundError",
                "message": "TIN-NPI combo not found."
            }
        },
        {
            "tin": "000010598",
            "npi": "000010618",
            "error": {
                "code": 404,
                "name": "NotFoundError",
                "message": "TIN-NPI combo not found."
            }
        }


Tell me how this is working again?

Reply all

Reply to author

Forward