Salesforce Health Cloud is Salesforce's product for managing patients and care, and community health organizations need it only when they must store and use clinical data, not just track programs and services. If your team coordinates care, records diagnoses and medications, or receives data from an EHR or health information exchange, Health Cloud's clinical data model can save you from building it yourself. If you mainly track enrollments, services and outcomes, Agentforce Nonprofit (formerly Nonprofit Cloud) or the Nonprofit Success Pack (NPSP) with some custom objects may be enough.
Here is how to tell which one you are, and what to ask before you buy. This is general information, not legal or compliance advice.
What Health Cloud is
Health Cloud is a Salesforce industry product built for organizations that manage patients, members or populations. Salesforce documents a clinical data model that is built to align with FHIR R4, the current common version of the FHIR standard, with Patient mapped to Person Accounts and other resources mapped to objects such as health conditions, clinical encounters and medication requests (Health Cloud developer guide, checked November 2026). Salesforce says the model supports most but not all R4 attributes, so don't assume a one-to-one match with your EHR.
In plain terms, Health Cloud gives you ready-made places to put clinical information and tools for coordinating care around a person, so you aren't inventing the structure from scratch.
Questions that decide whether you need it
Do you store clinical data? Diagnoses, medications, allergies, visit history and lab results are what the clinical model is for. If you only record that a person was enrolled in a program and received a service, you probably don't need it.
Do you receive data from an EHR or an exchange? Incoming HL7 or FHIR data needs somewhere to land. Health Cloud provides that structure. See EHR integration with Salesforce and HL7 vs FHIR.
Is care coordination your core work? Multi-person care teams, shared plans and a full view of one person's care are Health Cloud's focus.
Are you a covered entity or business associate? Then PHI rules apply no matter which Salesforce product you choose. Salesforce offers a Business Associate Addendum for a list of "HIPAA Covered Services" that has changed over time, so confirm every product you plan to use is on the current list (Salesforce BAA restrictions page, checked November 2026). Salesforce says compliance remains the customer's responsibility.
When you may not need Health Cloud
Many community health programs are about relationships and services, not charts. A community organization that runs a housing navigation program, tracks CHW visits or reports on funding sources often does well with:
- Agentforce Nonprofit or NPSP for people, households, programs and funders. NPSP is still supported.
- A few custom objects for the extra data you need, such as referrals, assessments or enrollment periods.
- Careful permissions, because even program data about a person's health or housing is sensitive. See Salesforce permissions and PHI.
For the choice between the nonprofit products, see Agentforce Nonprofit vs NPSP. If you are also weighing a purpose-built tool, read case management in Salesforce vs a dedicated system.
A middle path
Some organizations start with a nonprofit product and custom objects, then move to Health Cloud if clinical data needs grow. That works best when you keep the data model tidy from the start, with clear objects for visits, assessments and referrals rather than long text fields. Moving later is easier when the information is already structured. The reverse also happens: an organization buys Health Cloud, then uses a small part of it. Both outcomes are avoidable if you decide based on the data you must hold, not the product name.
A side-by-side view
| Question | Health Cloud | Nonprofit product plus custom objects |
|---|---|---|
| Clinical data model included | Yes, aligned with FHIR R4 | You build what you need |
| Fits an EHR feed | Designed for it | Possible, with more design work |
| Program and funder tracking | Needs configuration | Natural fit |
| License cost | Ask Salesforce | Ask Salesforce |
| Build and upkeep | Depends on scope | Depends on scope |
What about cost?
We won't quote prices, because they depend on your edition, user count and negotiated terms. The cost drivers are licenses, any integration tooling, the build effort and ongoing support.
On licensing, Salesforce's Power of Us program gives eligible US nonprofits (501(c)(3) and 501(c)(4) organizations under its published guidelines) free licenses for certain products, and Salesforce decides eligibility. We could not confirm that Health Cloud is included in that discount, so ask your Salesforce account executive in writing before you budget. Our guide to whether Salesforce is free for nonprofits covers the program in more detail.
What implementation involves
Whichever route you take, the work follows a similar path. We start with your programs and the questions your leaders, funders and payers ask, because those define the data you need. Then comes the data model, the security design, the screens staff will use, and any incoming data feeds. Testing with realistic but fake data comes before anyone touches real records.
The security design deserves its own time. Roles, permission sets and sharing rules decide who sees which client. For the details, read permission sets vs profiles and sharing model best practices.
Training matters as much as configuration. A clinical data model that staff find confusing gets bypassed with notes fields and spreadsheets, and then you have paid for structure you do not use.
Common mistakes
- Buying Health Cloud because the organization is in health. Buy it because of the data you must hold and the workflows you need.
- Skipping the data decision. List the clinical fields you really need. Each one adds mapping and security work.
- Leaving access wide open. Clinical data raises the stakes on every broad permission.
- Treating go-live as the finish line. Integrations and data models need an owner afterward.
Frequently asked questions
Is Health Cloud HIPAA compliant?
Health Cloud is generally described as HIPAA-eligible, but whether a Salesforce product is covered is decided by the Covered Services list in Salesforce's Business Associate Addendum and by your signed agreement, and some features can be excluded. HIPAA compliance also depends on your signed agreement, configuration, access controls and policies. Check the current list and talk to your compliance lead.
Can a nonprofit get Health Cloud at a discount?
It may be possible, but we couldn't verify it from public sources. Ask your Salesforce account executive.
Does Health Cloud replace my EHR?
No. Your EHR remains the clinical system of record. Health Cloud sits alongside it for coordination, outreach and a combined view.
Can we use Salesforce for CalAIM programs without Health Cloud?
Often yes, if the focus is enrollment, services and reporting. See CalAIM billing and CalAIM reporting in Salesforce.
Not sure which fits?
We can look at your data, your sources and your programs and tell you plainly whether you need Health Cloud or something lighter. Book a free Salesforce health check.