Salesforce Health Cloud Developer Guide
jSummer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
API End-of-Life Policy
Newer Version Available
Health Cloud Developer Guide
This guide provides information on the custom objects used by Health Cloud and their
fields. Some fields may not be listed for some objects.
|
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions with Health Cloud |
-
Health Cloud Data Model
Salesforce Health Cloud provides a rich set of objects to store and access specialized health information. -
Health Cloud Fields on Standard Objects
Health Cloud adds standard and custom fields to some standard Salesforce objects to represent information about individuals. These fields are available only in orgs where Health Cloud is enabled. -
Health Cloud Platform Events
Use the ApplnFormAppealStsChgEvnt platform event to notify subscribers when the status of the Financial Assistance Program’s appeal changes. Use the CareBnftVrfyRqstStsChgEvent platform event to notify subscribers when the status of care benefit verify request changes. -
Working With Electronic Health Records
HL7 (Health Level Seven) is a standard for exchanging electronic health records (EHR). You can parse EHR data transmitted via HL7 data messages and store it in Salesforce. -
Emergency Response Management
Use the objects, fields, and metadata that extend Salesforce for Emergency Response Management. -
Apex Reference
This Apex reference goes into detail about the built-in Apex classes, interfaces, methods, or enums for Health Cloud. -
Health Cloud Business APIs
Use the Health Cloud Business APIs for building integrations with Health Cloud or for creating custom UI components. The APIs wrap complex business logic by executing multiple tasks within a single API call. They aim to fulfill business use cases specific to the healthcare industry, such as enrolling patients into a care program or creating requests for prior authorizations. To use these APIs, you are not required to understand the underlying healthcare data model. Most of the APIs are RESTful APIs, but a few are also available through Apex classes and methods. -
Health Cloud Tooling API Objects
Tooling API exposes metadata used in developer tooling that you can access through REST or SOAP. Tooling API’s SOQL capabilities for many metadata types allow you to retrieve smaller pieces of metadata. For more information about Tooling API objects and to find a complete reference of all the supported objects, see Introducing Tooling API. -
Health Cloud Standard Invocable Actions
Manage healthcare facilities using invocable actions. For more information on standard invocable actions, see REST API Developer Guide and Actions Developer Guide. -
Metadata Types
-
API End-of-Life Policy
-
Health Cloud Managed Package
Health Cloud originally started out as a managed package that was installed on the core Salesforce platform. Over the years, Health Cloud has gradually moved away from distributing new features through the managed packaged, and instead has built its features directly on the core Salesforce platform.