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

As a provider, you can make requests to 1up's Provider Access API and export payer data for members you have an upcoming or active treatment relationship with.

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 followed by a review period for 1up to verify the applicant's identity and data access scope.

Quick-start with a sandbox client

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.

Replace the {curly brackets} and any text inside them with the appropriate value. The sandbox tenant (payer) for this process is bison .

1. Click the following link to access the 1up Dev Portal login page.

2. Register for the 1up Dev Portal, then 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. This should take you back to the Sandbox Clients page, where you can see your first Provider Access client. You will see a client ID next to your client's name as well as an option to copy the client secret.

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.

   curl --location 'https://gateway.1up.health/auth/realms/dev-portal/protocol/openid-connect/token' \
     --header 'Content-Type: application/x-www-form-urlencoded' \
     --data-urlencode 'client_id={add-your-client-id-here}' \
     --data-urlencode 'client_secret={add-your-client-secret-here}' \
     --data-urlencode 'grant_type=client_credentials' \
     --data-urlencode 'scope=bulk-data|user/*.rs'

8. Copy the access_token from the response to a text file. You will use this token for subsequent requests.

9. Make your FHIR bulk export request by replacing {access_token} for your copied access token. This request returns all data the payer has saved for any patients attributed to your organization.

   curl --location 'https://gateway.1up.health/v1/bison/bulk-data/r4/$export' \
       --header 'Authorization: Bearer {access_token}'

10. Copy the job URL from the response.

11. Send a request to check the progress of the FHIR bulk export. The response will include a list of files using URLs.

    1
    2
    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.

    1
    2
    curl --location '{file_URL}' \
        --header 'Authentication: Bearer {access_token}'

14. Review the patient information returned from the sandbox client.