Considerations for Health Cloud Installation

Before you install the Health Cloud packages in your org, review these considerations.
  • The managed package delivers the core of the Health Cloud capabilities. Install the Health Cloud managed package before the unmanaged packages.
  • The managed package is automatically updated. Don’t delete any part of the managed package after installing it. Deleting a part of the managed package can block automatic upgrades to future releases.
  • The custom objects, components, classes, and triggers delivered in the Health Cloud packages are one API version behind the core Salesforce API. Health Cloud standard objects have the same API version as core Salesforce. So if your org’s API version is 56, the Health Cloud custom object’s API version is 55 and the standard Health Cloud object’s API version is 56.
  • When creating custom fields or objects, don’t use the same API names as any packaged objects or fields. If you use the same names, the custom fields or objects can interfere with flows, processes, and triggers in Health Cloud.