QuickStart

This QuickStart explains how to:

Obtain an authorization token so you can access the Adequacy API endpoints.
Generate the Specialty Summary by County report to determine which counties do and do not have adequate coverage for each specialty.
Generate the Servicing Provider Report, with an option to output in HSD format for upload to HPMS.

Obtain an authorization token:

Request a client id and client secret from Quest Analytics Client Services.
Submit a POST request to the following endpoint, passing the client id and client secret in the request body.

For example:

POST /token HTTP/1.1
Host: https://uat-api.questanalytics.com/enterprise/auth
Content-Type: application/json
Subscription-Key: {{subscriptionKey}}
Content-Length: 145 
{ 
    "client_id": "{{clientId}}", 
    "client_secret": "{{clientSecret}}", 
    "scope": "default", 
    "grant_type": "client_credentials" 
}

The request returns a large authorization token (approximately 1800 characters).

Retrieve the Adequacy Summary Results to find out which counties will pass and which will fail when you upload your adequacy data to the government. To retrieve the report, submit a GET request to the following endpoint. The request takes the ProjectId in the URL and the authorization token in the request body.
For example:
```
GET /enterprise/proj-mgmt/v3/Projects/{{projectId}}/adequacy/results/summaries HTTP/1.1
Host: https://uat-api.questanalytics.com
Authorization: Bearer {{accessToken}} 
```
This request returns a data array which contains one element for each specialty in each county. So if there are 100 specialties and 40 counties, the array contains 4000 data elements. Each data element consists of standard fields defined by Quest and custom fields (cargo columns) defined by the client. For example, here is the data element for the cardiology specialty in Anderson county in Tennessee:
```
{
   "State": "Tennessee",
   "County": "44000 - Anderson",
   "CountyStatus": "Active",
   "CountyClass": "M",
   "MembershipName": "Primary Membership",
   "FullMemberCount": 570,
   "SpecialtyGroupCode": "008",
   "SpecialtyGroup": "Cardiology",
   "FullMemberCountWithAccess": 450,
   "MemberAccessPercentage": "79",
   "FullMemberCountWithoutAccess": 120,
   "MemberWithoutAccessPercentage": "21",
   "AccessMetCriteria": "N",
   "AccessCustomization": "N",
   "AccessTelehealthCredit": "",
   "ConAccessCredit": "",
   "AverageCoveringDistance": "---",
   "MinimumServicingProviders": 2,
   "InRegionProviderCount": 1.0,
   "DistinctServicingProviderCount": 1.0,
   "ServicingMetCriteria": "N",
   "OverallMetCriteria": "N",
   "GapAgeDays": "---",
   "MarketMemberAccessPercentage": "---",
   "MarketInRegionProviderCount": "---",
   "MarketDistinctServicingProviderCount": "---",
   "MarketPercentage": "---",
   "ImpactIndicator": ""
}
```
A county has adequate coverage for a specialty if OverallMetCritera = Y. This is true only when both ServicingMetCriteria and AccessMetCriteria are equal to Y:
- ServicingMetCritera indicates whether the number of servicing providers with the specialty is equal to or greater than the required number for the county.
  For example, if the guidelines mandate that a county has 2 cardiologists (MinimumServicingProviders=2) and there is only 1 (InRegionProviderCount=1), then ServicingMetCriteria = N.
- AccessMetCriteria indicates whether enough members have access to the specialty (i.e. the providers are in the right geographic area to cover the mandated percentage of members).
  For example, if the guidelines mandate that 85% of members have access to a cardiologist in a county, but MemberAccessPercentage=79, then AccessMetCriteria=N.