Deploying Health Cloud Analytics is a wizard-driven process layered on top of a working Health Cloud configuration. The walkthrough below covers the standard go-live sequence from prerequisites through dashboard customization with clinical stakeholders.
- Confirm Health Cloud and CRM Analytics prerequisites
Verify that the org has Health Cloud licensed and configured with at least one Patient (Person Account) record, one Care Plan, and one HealthCondition record. Confirm that CRM Analytics Plus is licensed and that the running admin user has Manage CRM Analytics permission. Without these prerequisites, the wizard runs but the dashboards return zero results, which causes a confusing first demo to clinical stakeholders.
- Run the Health Cloud Analytics wizard
From Setup, search for Health Cloud CRM Analytics Settings and select the page. Click Start to launch the wizard. The wizard prompts for an app name, an initial set of filters (by line of business or geographic region), and a deployment confirmation. Click Deploy. The deployment runs for fifteen to forty-five minutes, depending on data volume. Salesforce sends an email when the deployment completes, after which the dashboards become visible in the Analytics Studio under the new Health Cloud Analytics app.
- Configure row-level security predicates
Open the Analytics Data Manager, find the Patient Population dataset, and inspect the security predicate. Compare it to the org's actual role hierarchy and Health Cloud care team assignments. Adjust the predicate JSON to match the org's clinical access controls. Test by logging in as a sample care manager and confirming they see only their assigned patients in the dashboards. Repeat for every dataset that holds patient-level data. This step is the gating step for HIPAA-compliant rollout and should not be skipped.
- Customize, validate, and roll out
Clone every wizard-deployed dashboard so customizations do not get overwritten by future wizard re-runs. Add cohort filters relevant to the org's quality initiatives. Add organization-specific KPIs the standard dashboards do not include. Walk the clinical leadership team through each dashboard, capture feedback, iterate. Schedule a soft launch for two weeks with a small group of clinical users, capture feedback, fix issues, then announce broadly. Communicate the dashboards' refresh schedule clearly so users do not expect intraday data when the refresh is nightly.
- The wizard does not validate that source data is present. Running against an empty Health Cloud setup produces dashboards that load successfully but show no patients anywhere.
- Re-running the wizard overwrites the deployed dashboards. Always clone before customizing so a future wizard run does not erase the changes.
- Row-level security predicates that look correct can still expose patient data if the care team assignments are stale. Refresh the test scenario after any role hierarchy change.
- Default dataflow schedule is nightly. Clinical stakeholders expecting real-time visibility into newly admitted patients need to be set straight before the first live demo.
- The Health Cloud Analytics app requires CRM Analytics Plus. Orgs on the base CRM Analytics SKU see the settings page but cannot complete the deployment.