Accessing Patient Prism Data: Scheduled Exports vs. API

If you’d like to use Patient Prism data in your own tools (data warehouse, BI dashboards, internal reporting), there are two primary ways to pull data from Prism:

Option 1: Scheduled Exports (Simplest)

Scheduled Exports are the easiest way to move Prism data into your environment without building an API integration.

How it works

You link a cloud storage bucket (AWS S3, Azure Blob Storage, or Google Cloud Storage).
You configure what data you want exported (date range, cadence, columns, filters).
Prism automatically generates export files and drops them into your bucket.
Your team ingests those files into your warehouse or reporting tool.

Best for

Customers who want ongoing “data dumps” on a schedule
Teams that prefer minimal engineering work
File-based ingestion workflows (bucket → warehouse)

Option 2: Direct API Access (Most Flexible)

API access is best when you want a direct connection and more control over how and when you pull data.

Patient Prism utilizes GraphQL for our internal reporting, and it can also be used for pulling data out.

GraphQL API for call data and reporting metrics

Best for

Customers who want programmatic access (ETL/ELT jobs)
Use cases requiring flexible queries or computed metrics

Authentication (Recommended Setup)

API tokens are tied to a user. The standard best practice is to create a dedicated service account (often called a “BI” or “API” user), make it a Company Admin, and generate an API token for integration use.

What you’ll need to get started

To start quickly, we typically confirm:

Your preferred approach (Scheduled Exports or API)
Bucket destination details (if using Scheduled Exports)
Your service account + token setup (if using API)
Who should receive technical notifications for integration issues

If you’re unsure which option is best, most teams start with Scheduled Exports for core call data and use the API if they also need transcripts or more customized queries.