Source connector
Salesforce Health Cloud connector
Salesforce Health Cloud integration for databases, warehouses and BI tools
Patient and member relationship management on Salesforce. Datrise captures Salesforce Health Cloud entities such as patients, care plans, care teams, clinical encounters, cases and consents, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `salesforce_health_cloud_patients`) with a schema derived from the Salesforce Health Cloud API rather than a flattened CSV, in any of the 43 supported destinations.
Datrise is in early access: pick a destination below to open the Salesforce Health Cloud pipeline page, and join the waitlist to get the Salesforce Health Cloud connector (CRM) with guided onboarding.
What Salesforce Health Cloud data Datrise extracts
Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.
| Object | Landing table | Sync mode |
|---|---|---|
| patients | salesforce_health_cloud_patients | Upsert by primary key, incremental on updated-at |
| care plans | salesforce_health_cloud_care_plans | Upsert by primary key, incremental on updated-at |
| care teams | salesforce_health_cloud_care_teams | Upsert by primary key, incremental on updated-at |
| clinical encounters | salesforce_health_cloud_clinical_encounters | Upsert by primary key, incremental on updated-at |
| cases | salesforce_health_cloud_cases | Upsert by primary key, incremental on updated-at |
| consents | salesforce_health_cloud_consents | Upsert by primary key, incremental on updated-at |
Popular destinations for Salesforce Health Cloud
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
Salesforce Health Cloud connector FAQ
- What Salesforce Health Cloud data does the connector extract?
- 6 objects: patients, care plans, care teams, clinical encounters, cases and consents. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
- Is the Salesforce Health Cloud integration incremental?
- Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
- Where can I load Salesforce Health Cloud data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Salesforce Health Cloud → destination pair has its own page with the object-to-table mapping.
Related CRM sources
Other sources in the same category, each with its own connector page.
Early access
Launch your Salesforce Health Cloud pipeline with guided onboarding
Join the waitlist to get priority access for Salesforce Health Cloud integrations with guided setup, schema-aware mapping, and production-grade incremental sync.