# 1up Provider Access

## Overview for payers

Payers are required to make member data available to in-network providers and attribute member data to their providers. Payers can use the Provider Access API to fulfill that requirement. The Provider Access API includes claims, clinical, encounter, and prior authorization data. Provider Access does not include remittances and cost-sharing information.

## Overview for providers

Providers can request payer data for members they have an upcoming or active treatment relationship with.

The technical staff (IT) for provider organizations connect 1up Provider Access to their organization's Electronic Health Record (EHR) or Data Management System. The API requests and responses are handled in the back-end so providers can use their normal workflow.

In order to use Provider Access, provider organizations create an account through the 1up Dev Portal. Accessing production data requires verification by 1upHealth. The verification process requires a form submitted through the [1up Dev Portal](https://developer.console.1up.health/1up-dev-portal) followed by a review period for 1up to verify the applicant's identity and data access scope.

### Quick-start `$export` with a sandbox client

Audience
This content is intended for technical staff at provider organizations.

You can test the process for creating a client, setting up access with client credentials and an authorization token, and requesting patient data with a sandbox client. The sandbox `tenant` for this process is `bison`.

1. Access the [1up Dev Portal](https://developer.console.1up.health/1up-dev-portal) login page.
2. Register for the 1up Dev Portal, complete email verification, and login.
3. Click Create a Client.
4. Select Provider Access as your Organization Type.
5. Enter a name for your client and click Create.
6. Copy your new client ID and client secret from the clients table.
7. Request an authorization token by pasting the following code into a terminal. Use the copied `client_id` and `client_secret` for this request.

8. Copy the `access_token` from the successful response. You will use this token for subsequent requests.
9. Submit a FHIR bulk export request using the below code with your `access_token`. This request returns all data the payer has saved for any patients attributed to your organization.

10. Copy the job URL from the successful response.
11. Send a request to check on the progress of the FHIR bulk export. The response will include a list of files using URLs.

```curl
curl --location '{job_URL}' \
--header 'Authentication: Bearer {access_token}'
```
12. Copy the URL for any of the files.
13. Send a request to return the data from one of the files.

```curl
curl --location '{file_URL}' \
--header 'Authentication: Bearer {access_token}'
```
14. Review the patient information returned from the sandbox client.