Standing up the Clinical Data Model is a multi-team project covering data model, EHR integration, privacy, and care workflows. The configuration below assumes the broader Health Cloud program is in place.
- Activate Health Cloud and the Clinical Data Model
Setup, Health Cloud Settings. Confirm the relevant feature licences and permission sets are assigned to clinical users.
- Map source EHR data to the Clinical Data Model
Build the mapping from source system fields to Health Cloud object fields. FHIR-emitting EHRs map cleanly; legacy custom schemas need more effort.
- Configure ingestion through Health Cloud APIs
Use Salesforce Health Cloud APIs, MuleSoft, or Data Cloud to ingest clinical data on a recurring schedule. Validate referential integrity (every Observation links to a valid Patient).
- Apply consent and privacy controls
Configure Patient Consent records and sharing rules so access matches the minimum-necessary principle. Audit access patterns periodically.
- Build Care Plans and Programs on top
Reference clinical data in Care Plan Goals, Care Program eligibility criteria, and reporting cohorts. The clinical data is what makes the care workflows operational.
- Non-FHIR EHR mapping loses fidelity. Budget for mapping effort and accept some data loss if the source is custom.
- Privacy controls need explicit configuration. Default settings are conservative; misconfiguration produces compliance findings.
- Clinical data volumes grow fast. Plan storage and archival explicitly; large patient populations produce millions of Observation records per year.
- Integration with multiple EHRs (multi-hospital systems) requires careful identity resolution to avoid duplicate patient records.