Bridge by Healthie
Bridge by Healthie is a data tool that enables enterprise customers to seamlessly access bulk data from Healthie for use in their own data infrastructure. As an API-first EHR, Healthie’s infrastructure supports flexible, high-volume data retrieval — making it easy for teams to power analytics, reporting, machine learning, and more.
Bridge is an add-on product for Enterprise customers, delivering structured Healthie data to an S3 bucket or via direct integration with Snowflake (beta).
To get started, complete our Bridge by Healthie Interest Form.
In this article:
Benefits
- Faster access to data: Avoid custom API calls by accessing structured, bulk data regularly refreshed.
- BI & analytics-ready: Compatible with modern data warehouses and BI tools (e.g. BigQuery, Snowflake, Redshift).
- Efficient development: Save engineering time on ETL by working from a common schema across analytics, reporting, and product pipelines.
- Developer-friendly formats: Delivered in Parquet format, with schemas mapped to key Healthie tables.
- Secure and compliant: Access is controlled via secure S3 policies or Snowflake Direct Share, with HIPAA-compliant data handling.
Delivery Methods
Option 1: S3 Bucket (Live)
- Healthie delivers Parquet files containing change data capture (CDC) records that are saved in batches every 15 minutes. End users are responsible for merging CDC records.
- Each CDC record includes a
tx_commit_time
column that represents the transaction commit timestamp from the source database. This is the authoritative indicator for determining record precedence during CDC ingestion. When processing multiple versions of the same record, the record with the latesttx_commit_time
should be considered the current version for merge operations.
- Each CDC record includes a
- Files are stored in a Healthie-owned S3 bucket.
- Customers are granted read-only access to only their organization’s data via AWS S3 external access points.
- Text and JSONB fields are truncated at 8KB per field.
Option 2: Snowflake Direct Share (Beta - launching soon)
- Enables direct access to Bridge data from your own Snowflake account. Snowflake account requirements:
- Business Critical
- HIPAA enabled
- AWS
us-east-1
region
- No data replication required; query directly in your environment.
- Data refreshes hourly for key models, otherwise every 24 hours.
- No additional data transfer costs — customers only pay Snowflake compute costs.
💡 Snowflake Direct Share will offer the same tables and schema as the current S3 delivery, but data will already be merged and query-ready.
Frequency & Table Coverage
Update Frequency
- S3 Bucket: every 15 minutes
- Snowflake Direct Share: either every hour for key models, otherwise every 24 hours
Table Coverage
- Bridge supports a wide range of Healthie data tables, which are documented in our Data Dictionary.
⚠️ Note: Any fields with large text or JSON content are truncated at 8KB.
Access & Setup
Request Access
Complete the Bridge by Healthie Request Form.
A team member will follow up with a contract addendum and next steps.
Set Up Access
- S3: You must have an active AWS account; we’ll provision access to a Healthie-managed S3 bucket.
- Snowflake (once available)
- Must be in the same Snowflake region (AWS
us-east-1
) as Healthie. - You will have to provide your data sharing account identifier.
- Must be in the same Snowflake region (AWS
Stay Updated
Subscribe to the Bridge Portal Card to receive the latest release timelines and updates.
For questions, email us at hello@gethealthie.com.
FAQ: Bridge by Healthie
What is the difference between S3 and Snowflake delivery?
S3 provides incremental data files that customers manually merge and ingest into their own data warehouse. Snowflake (coming soon) will allow you to query a pre-merged, query-ready dataset directly from your own Snowflake account via Snowflake secure data share.
How frequently is data updated?
- S3 files are updated every 15 minutes.
- Snowflake data is refreshed either hourly or daily, depending on the table.
What format is the data delivered in for S3 delivery?
Parquet file format.
Does Bridge deliver full tables or only changes?
For both delivery methods, Bridge offers full tables.
- S3: In addition to the full table, you also get the changes via Parquet. Each file will contain change data capture (CDC) records (inserts/updates/deletes). You must merge the CDC records into your data warehouse.
- Snowflake: Tables are already merged; you query the current state directly.
Are all Healthie data tables included?
Not all tables are currently supported. However, the list is growing and includes core data types (e.g. appointments, payments, charting, diagnoses). Our team actively updates the Data Dictionary.
Why do some tables in the data dictionary not match the Bridge product?
We are working on improving the data dictionary to better reflect what is currently delivered via Bridge. Some tables may be missing, and some present tables may not be part of Bridge. An updated version is coming soon.
Can I control which tables I receive?
Not at this time — Bridge delivers the full set of eligible tables.
Are there any limitations?
- Fields with text or JSONB content are truncated at 8KB.
- S3 access requires an AWS account.
- Snowflake sharing requires matching region your Snowflake instance to be on the same region.
Is Bridge HIPAA-compliant?
Yes. All data delivery mechanisms are HIPAA-compliant, and access is securely controlled.