Unified Health Scoring
Unified Health Scoring in Salesforce is the composite metric that aggregates multiple individual indicators (clinical risk factors in Health Cloud, engagement and retention signals in Customer Success contexts) into a single number or rating that gives care teams or account managers an at-a-glance view of where a patient or customer stands.
Definition
Unified Health Scoring in Salesforce is the composite metric that aggregates multiple individual indicators (clinical risk factors in Health Cloud, engagement and retention signals in Customer Success contexts) into a single number or rating that gives care teams or account managers an at-a-glance view of where a patient or customer stands. The score is computed by a weighted formula over the inputs, displayed on the record page or in dashboards, and used to trigger automated workflows when the score crosses configured thresholds.
The same conceptual pattern appears in two distinct Salesforce contexts. In Health Cloud, Unified Health Scoring rolls up clinical indicators (vitals, lab results, social determinants, condition severity) into a Care Risk Score that helps care managers prioritize patients. In Customer Success and Service Cloud, equivalent Customer Health Scoring rolls up engagement signals (product usage, support volume, renewal proximity, sentiment) into a Customer Health Score that drives renewal and expansion plays. The mechanics are similar; the inputs and downstream workflows differ by domain.
Unified Health Scoring in Health Cloud and Customer Success
What Unified Health Scoring measures and why it matters
A Unified Health Score collapses many disparate signals into one indicator that a busy human reviewer can act on at scale. In Health Cloud, a care manager working a panel of 500 patients cannot inspect every clinical detail on every patient every day; the score lets them sort the panel and focus on the top 20 highest-risk patients in the next 30 minutes. In Customer Success, an account manager covering 200 accounts cannot review every product-usage trend every week; the customer health score lets them focus on the dozen at-risk accounts before renewal pressure arrives. The signal-to-action compression is the value proposition. Done well, scoring saves hours per reviewer per week and surfaces real issues earlier. Done badly, it drowns out the underlying signals and produces false confidence.
Score composition and the input signals
Building a Unified Health Score is a configuration exercise. The org picks the input signals (Health Cloud: blood pressure trends, A1C levels, ED visits, missed appointments, social determinants scores. Customer Success: product login frequency, feature adoption breadth, support ticket volume and severity, NPS, days to renewal). Each input gets a weight reflecting its predictive value for the outcome the score targets (worsening health, churn risk). The composite is a weighted sum, often normalized to a 0-to-100 scale or a Red/Yellow/Green rating. The input set and weights should be revisited regularly; the original weights reflect the team hypothesis, not ground truth. As actual outcomes accumulate, refine the formula based on which inputs actually predicted the outcomes.
Implementation: Calculated Insights, Apex, or third-party tools
Three implementation paths exist. Calculated Insights in Data Cloud is the modern preferred path: define the score as a SQL aggregation against the Unified Data Model, refresh on a schedule, surface the result through Customer 360 widgets. Apex rollup or formula fields on the core platform is the older path that works in any org without Data Cloud; the score lives on the record (Patient Account, Customer Account) and recalculates through scheduled Apex or process automation. Third-party tools (Totango, Gainsight, Catalyst for Customer Success; specialized clinical risk platforms for Health) offer richer scoring algorithms and pre-built integrations. Pick based on the org existing platform investments and the sophistication of the scoring required.
Thresholds, alerts, and the action layer
A score is only useful if it drives action. Configure thresholds on the score (Red below 40, Yellow 40-70, Green above 70) and tie automated workflows to each band. Red patients get a Care Manager Task and a phone outreach scheduled within 24 hours. Yellow customers get a Customer Success check-in and an executive sponsor heads-up. Green accounts go to a quarterly review cadence. The threshold configuration is per-org and per-use-case; document the rules so the team understands why a given account or patient is in a given band. Without explicit thresholds and downstream workflows, the score is just a dashboard widget that nobody acts on; the workflows are what turn the score into business outcomes.
Scoring validation and the feedback loop
Validate the scoring formula by comparing predicted outcomes against actual outcomes over time. For Health Cloud, track whether patients flagged Red actually had worse 90-day clinical outcomes than those flagged Green. For Customer Success, track whether customers flagged at-risk actually churned at higher rates than those flagged healthy. If the score does not predict the outcome it is supposed to predict, the formula needs revision. Mature scoring implementations run this validation quarterly and adjust the input weights based on what the data shows. Without validation, the score drifts from reality over time; the original hypothesis that built it stops matching the actual customer or patient base, and the score becomes misleading rather than useful.
Privacy, compliance, and the score regulatory context
Both Health Cloud and Customer 360 use Unified Health Scoring with significant regulatory considerations. Health Cloud scoring touches Protected Health Information (PHI) and is subject to HIPAA: access to the score is logged, retention is regulated, and patient consent governs what data feeds the score. Customer health scoring touches personally identifiable information and customer engagement data; depending on jurisdiction (GDPR for EU customers, CCPA for California), the customer may have rights to know what data feeds their score and to request changes. Mature implementations document the score data sources and the access policy, and they include the score in privacy impact assessments. Compliance is not optional for either domain; build the audit trail at the same time as the scoring formula.
Building and operating a Unified Health Score
Standing up Unified Health Scoring is a four-phase project. The phases are: design the scoring formula with input signals and weights, implement the formula in Data Cloud Calculated Insights (or Apex rollup), build threshold-driven workflows that turn the score into action, and validate the formula against actual outcomes over time. Each phase has a different stakeholder profile: clinical or success leaders define the signals, admins implement the configuration, operations owns the workflow, analytics owns the validation. Plan the project with shared milestones across all four groups.
- Design the scoring formula with input signals and weights
Work with clinical or customer-success leaders to identify the input signals that predict the outcome the score targets. For Health Cloud, the signals might be A1C trend, ED visits in 90 days, missed appointment count, social determinants of health, and active diagnoses. For Customer Success, login frequency, feature adoption breadth, support volume, NPS, days to renewal. Assign each signal a weight from 0 to 1 reflecting its predictive value; the weights should sum to 1. Document the rationale for each weight. Get sign-off from the business leader who owns the outcome (the chief medical officer for Health, the VP of Customer Success for the customer use case).
- Implement the formula in Data Cloud or Apex
For orgs running Data Cloud, build a Calculated Insight that computes the score as a SQL aggregation over the Unified Data Model. Schedule the insight to refresh daily (or more frequently for operationally-critical use cases). For orgs without Data Cloud, implement the formula as an Apex rollup with scheduled execution, or as a Custom Metadata-driven formula field that recalculates on record save. Test the implementation against a known sample (a patient or account where you know what the score should be) and confirm the formula produces that value. Iterate until the implementation matches the design.
- Build threshold-driven workflows
Configure thresholds on the score (Red, Yellow, Green or whatever rating system fits the use case). For each threshold, define the downstream action: assign a Care Manager Task, send an executive notification, trigger a customer success play, schedule a phone outreach, route a Case. Implement the actions through Flow, Apex, or your customer success automation tool. Test each action by setting a sample record to the relevant score and confirming the action fires. Document the threshold-to-action mapping in the operational runbook so the team understands why a given record gets a given workflow.
- Validate the formula against actual outcomes
After three to six months of scoring, validate the formula by comparing predicted outcomes against actual outcomes. For Health Cloud, run a cohort analysis: patients flagged Red, did they actually have worse 90-day outcomes (more ED visits, more hospitalizations)? For Customer Success, did at-risk accounts actually churn at higher rates? If the formula does not predict the outcome, refine the input weights or add new signals. Schedule a quarterly validation review. Document the validation results and any formula adjustments. Without the validation loop, the score drifts from reality over time and stops being useful.
- Initial scoring weights are hypotheses, not ground truth. Run quarterly validation against actual outcomes and refine weights based on what the data shows; without validation, the score drifts from reality.
- Health Cloud scoring touches PHI and is subject to HIPAA. Access logging, retention policy, and patient consent all apply. Build audit trails at the same time as the formula.
- A score without threshold-driven workflows is just a dashboard widget. The action layer (Care Manager Tasks, Customer Success plays) is what turns scoring into business outcomes.
- Data Cloud Calculated Insights run on a schedule, not real time. For operationally-critical use cases (a deteriorating patient, an escalating customer), the latency may be too long; consider supplementary real-time signals.
- Each scoring use case (Health Cloud vs Customer Success) has its own design and validation cycle. Reusing a Health Cloud score for Customer Success without rethinking the inputs almost never works.
Trust & references
Straight from the source - Salesforce's reference material on Unified Health Scoring.
- Health Cloud OverviewSalesforce Help
- Calculated Insights in Data CloudSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Unified Health Scoring?
Q2. Why use a composite score?
Q3. What should you do when the score indicates concern?
Discussion
Loading discussion…