Salesforce Health Cloud to Databricks SQL Warehouse Integration
AI-first ETL from Salesforce Health Cloud into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Health Cloud into Databricks SQL Warehouse
Datrise syncs Salesforce Health Cloud's patients, care plans, care teams, clinical encounters, cases, and consents into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.
Ideal for lakehouse analytics and ML feature tables on Databricks.
Endpoints
Salesforce Health Cloud: Patient and member relationship management on Salesforce.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Salesforce Health Cloud entities map to Databricks SQL Warehouse
| Salesforce Health Cloud entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| patients | salesforce_health_cloud_patients | id PK · custom fields → VARIANT or STRUCT columns |
| care plans | salesforce_health_cloud_care_plans | id PK · linked to salesforce_health_cloud_patients |
| care teams | salesforce_health_cloud_care_teams | id PK · linked to salesforce_health_cloud_patients |
| clinical encounters | salesforce_health_cloud_clinical_encounters | id PK · linked to salesforce_health_cloud_patients |
FAQ
How does Datrise handle Salesforce Health Cloud's custom fields in Databricks SQL Warehouse?
Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.
How does the Salesforce Health Cloud to Databricks SQL Warehouse sync stay up to date?
It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.
Related pipelines
More destinations for Salesforce Health Cloud
- Salesforce Health Cloud → ClickHouse
- Salesforce Health Cloud → DuckDB
- Salesforce Health Cloud → Amazon Athena
- Salesforce Health Cloud → Amazon S3 Data Lake
- Salesforce Health Cloud → Azure Data Lake Storage
- Salesforce Health Cloud → Azure Synapse
- Salesforce Health Cloud → Spreadsheets
- Salesforce Health Cloud → Airtable
- Salesforce Health Cloud → CSV Files
- Salesforce Health Cloud → MongoDB
- Salesforce Health Cloud → Supabase
- Salesforce Health Cloud → Neon
More sources for Databricks SQL Warehouse
- DealerSocket → Databricks SQL Warehouse
- VinSolutions → Databricks SQL Warehouse
- JobNimbus → Databricks SQL Warehouse
- Buildertrend → Databricks SQL Warehouse
- ServiceTitan → Databricks SQL Warehouse
- Housecall Pro → Databricks SQL Warehouse
- Jobber → Databricks SQL Warehouse
- Mindbody → Databricks SQL Warehouse
- Clio → Databricks SQL Warehouse
- MyCase → Databricks SQL Warehouse
- Allbound → Databricks SQL Warehouse
- Impartner → Databricks SQL Warehouse
Early access
Connect Salesforce Health Cloud to Databricks SQL Warehouse the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.