Salesforce Health Cloud to ClickHouse Integration
AI-first ETL from Salesforce Health Cloud into ClickHouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesforce Health Cloud into ClickHouse
Datrise syncs Salesforce Health Cloud's patients, care plans, care teams, clinical encounters, cases, and consents into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.
Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.
Ideal for high-volume event analytics that need sub-second aggregation.
Endpoints
Salesforce Health Cloud: Patient and member relationship management on Salesforce.
ClickHouse: Columnar OLAP engine for fast aggregations.
How Salesforce Health Cloud entities map to ClickHouse
| Salesforce Health Cloud entity | ClickHouse object | Notes |
|---|---|---|
| patients | salesforce_health_cloud_patients | id PK · custom fields → JSON or Map 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 ClickHouse?
Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.
How does the Salesforce Health Cloud to ClickHouse sync stay up to date?
It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.
Related pipelines
More destinations for Salesforce Health Cloud
- 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
- Salesforce Health Cloud → PlanetScale
Early access
Connect Salesforce Health Cloud to ClickHouse 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.