For customers with production access, you can request access to your data on the 1upHealth platform in FHIR Bulk Data format by following the instructions below. This type of access allows you to run SQL queries directly on your FHIR data (which your try on our website here), or connect your data to a Business Intelligence / Data Visualization tool of your choice (e.g., Tableau, Sisense, Amazon QuickSight, PowerBI) via a JDBC driver (steps listed below).
This enables a number of population health use cases including:
- Quality Measure Reporting (e.g., HEDIS, Stars)
- Risk Stratification
- Gaps in Care identification
How to Obtain Access to FHIR Analytics:
- Navigate to the 1upHealth Dev Console and log in
- You must already have Production Access (follow steps here)
- Click on 'Applications' in the sidebar menu.
- Select an application (or create a new one)
- Click on 'Generate FHIR Analytics Account' and we will automatically give you access to this service. Once completed, you will be provided with
- Associated 1up Application Client Id
- Associated 1up Application Name
- Access Key Id - this will no longer available after navigating away, so store in a safe location
- Secret Access Key - this will no longer available after navigating away, so store in a safe location
- If you need to see the Schema again you can view those in the ‘Application Details’ in the Dev Console
Connecting via JDBC driver
Once you have obtained the bulk data access, you can now connect your data on the 1upHealth platform to connect to the BI/Visualization tool of your choice by following these steps:
- Follow the steps above to obtain FHIR Bulk Data access for your data on the 1up platform.
- Download the Amazon Athena JDBC42 .jar file
- Download (or use an existing) SQL tool of your choice (e.g., DataGrip, open source tools like DBeaver, SQuirreL, etc.)
- Configure the tool with the following values
- Driver - Amazon Athena JDBC42 (e.g., jdbc:awsathena) - this is the .jar file you downloaded in step 2.
- User Name (i.e., AWS Access Key) - Access Key Id provided in step 1
- Password (i.e., AWS Secret Key) - Secret Access Key provided in step 1
- Schema - Provided in step 1. In our example, 1up.dev.us-east-1.analytics-0582e409a5f15f0e7cd5d794d99bb0a)
- Bucket / Output Location - s3:// + Schema. In our example below, s3://1up.dev.us-east-1.analytics-0582e409a5f15f0e7cd5d794d99bb0a
- AWS Region - pulled from Schema. In our example below, us-east-1
- Example URI - jdbc:awsathena://AwsRegion=us-east-1;S3OutputLocation=s3://1up.dev.us-east-1.analytics-0582e409a5f15f0e7cd5d794d99bb0a;Schema=1up.dev.us-east-1.analytics-0582e409a5f15f0e7cd5d794d99bb0a
- Test the connection with simple query (e.g., select * from dstu2_patient limit 10)
The available tables will include DSTU2 and STU3 resources, such as: