You are here:
Experience Cloud for Health Cloud FAQ
Get answers to common questions about Experience Cloud for Health Cloud, a set of Experience Cloud products designed to work with Health Cloud.
What is Experience Cloud for Health Cloud?
Experience Cloud for Health Cloud combines Health Cloud objects, components, and flows in industry-specific community portals. Customers can create engaging, personalized, and secure self-service experiences across the patient, member, and partner journeys. Experience Cloud for Health Cloud includes these three products.
- Experience Cloud for Health Cloud — Recommended for B2C use cases such as member-patient collaborations. Released in Summer ’21.
- Experience Cloud Plus for Health Cloud — Recommended for B2C use cases and for B2B use cases such as provider-payer collaboration with more role-based sharing, reports, and dashboards.
- External Apps for Health Cloud — Recommended for B2B use cases that involve working with partners, such as payers working with brokers or suppliers collaborating on manufacturing plans and forecasts. Includes Leads and Opportunities.
The differences between Experience Cloud for Health Cloud and Experience Cloud Plus for Health Cloud are the same as the differences between Experience Cloud and Experience Cloud Plus. The latter provides advanced sharing, more CRUD access to specific objects, customizable dashboards, and more.
For purchasing details, see Health Cloud Pricing.
Is there a Partner Community for Health Cloud?
For scenarios where external brokers need access, External Apps for Health Cloud provisions partner licenses and Health Cloud permission set licenses to the customer org.
Partner Community licenses represent users as Account-Contact records, while Health Cloud represents users as Person Accounts. However, if necessary, an Apex service can programmatically synchronize data between traditional B2B Account-Contact records and parallel or existing Person Account records.
Can guest users self-register as Person Accounts?
Guest user self-registration is a common use case. For example, a user scheduling a COVID vaccination can self-register before making the appointment.
Experience Cloud builder has a component for self-registration. Also, there are multiple ways to create users as Person Accounts in Experience Cloud.
Can Experience Cloud for Health Cloud users access Quote objects?
The Quote object isn’t supported by default in Experience Cloud for Health Cloud and Experience Cloud Plus for Health Cloud licenses. However, with the Sell & Administer Benefits and Distribution Management add-ons, an Apex service gives end users the ability to create and access information from Quotes. For details about add-on products, see Benefit Sales and Administration Pricing and Distribution Management Pricing.
What features are unique to Experience Cloud for Health Cloud products?
Experience Cloud Plus for Health Cloud and External Apps for Health Cloud were launched as part of Emergency Response Management with Contact Tracing. This feature adds a health assessment portal and contact tracing functionality to Health Cloud and provides access to the Contact Encounter and Contact Encounter Participant objects. For example, members can log into Kaiser and submit a health questionnaire or submit contacts for contact tracing purposes.
As Salesforce builds new Health Cloud data model entities and new Lightning Web Component User Interfaces, these become part of the new Experience Cloud for Health Cloud. Support for existing Health Cloud entities and Lightning Web Components continues for legacy Experience Cloud customers. However, over time, more Health Cloud-specific functionality will be accessible via Experience Cloud for Health Cloud only.
For example, if regular Experience Cloud supports the Case object, that support continues. In addition, Experience Cloud for Health Cloud supports the Case object. However, in future Health Cloud releases, new entities are supported only in Experience Cloud for Health Cloud and not in any other Experience Cloud product.
The new digital process automation (DPA) runtime is only available for Experience Cloud for Health Cloud products.
What if I’ve used Health Cloud and Customer Communities before?
Salesforce previously released components that Health Cloud customers could use with Experience Cloud, and those components remain available and upgradable. However, starting in Summer ’21, customers need the Experience Cloud for Health Cloud products to take advantage of new Experience Cloud components released as part of Health Cloud.
How do I upgrade from Experience Cloud to Experience Cloud for Health Cloud?
Upgrading from a regular Experience Cloud license to an Experience Cloud for Health Cloud license follows the same process as any license swap—ask your account executive for details. Users must have the Health Cloud permission set license enabled to access Health Cloud objects in Experience Cloud for Health Cloud.
How do I migrate community users from Service Cloud to Experience Cloud for Health Cloud?
When you upgrade from Service Cloud to Health Cloud, you must convert Contacts to Person Accounts. Also, you must recreate Contact-based community users by sending registration emails.
You can’t convert the portal-enabled Business Accounts or Contacts in Service Cloud to the Person Accounts in Health Cloud. However, if necessary, an Apex service can programmatically synchronize data between traditional B2B Account-Contact records and parallel or existing Person Account records.
How can I enable site user access for Health Cloud customers?
Site users can use Health Cloud features and objects if they have the Health Cloud for Experience Cloud Sites permission set license and its feature-specific permission sets. For details, see Experience Cloud Setup Checklist for Health Cloud.
