Create Template of Service Appointment Action: Create a service appointment record of Cancelled status that's used as a template for creating the actual service appointment record while scheduling home visits manually.
Handle Resource Absence Action: Remove a service resource’s visit assignments for a specified period and optionally update the status of the affected visits to a specified value.
Schedule Group Visits Action: Create visiting records for patient home visits by bundling them into a group and scheduling either a single start-of-care visit or a series of recurring visits associated with the bundled records.
Schedule Home Visit Action: Schedule a home visit for the patient to assess the condition before scheduling the recurring visits for the patient care.
Schedule Home Visits Manually Action: Create start of care or recurring home visits and assign care resources that are manually selected by the scheduler to the visits.
Schedule Recurring Home Visit Action: Create a set of recurring home healthcare visits and assign service resources to them based on the specified scheduling policy.
Attribute: Represents an extracted field-level attribute within a Document AI node, including its value, metadata, confidence score, and potential matching information.
attributeName: The standardized or canonical name used to identify this attribute within the extraction context.
confidenceScore: The confidence score assigned by the extraction model for this field value.
fieldApiName: The API name of the field to which the extracted value corresponds.
fieldType: The data type of the field (for example, String, Date, Number).
isExistingParentReferenced: Indicates whether the attribute refers to an already existing parent record in the system.
matchingRecords: The list of potential matching records for this identified attribute during duplicate detection or matching.
parentReferenceId: The reference identifier of the parent node associated with this attribute.
ExtractionMetadata: Represents additional metadata returned during Document AI processing, including matching resolution details and manual review requirements.
id: The unique identifier of the matched record in the system.
matchingRuleIdOrName: The unique identifier or developer name of the matching rule to be used for duplicate detection.
MatchingRecord: Represents a potential existing record identified during Document AI matching or duplicate detection.
Node: Represents a structured entity node in Document AI processing, containing object details, extracted attributes, and potential matching record information.
attributes: The list of extracted field attributes associated with this node.
isExistingRecord: Indicates whether the node corresponds to an existing record in the system.
matchingRecords: The list of potential matching records identified during duplicate detection or matching.
nodeName: The title of the context node to identify this node within the extraction context.
objectApiName: The API name of the Salesforce object represented by this node.
referenceId: The reference identifier used to correlate the record with the original extraction request.
ApexMap Class: Create, clone, and convert string based key-value pairs to a JSON string format.Learn more about the constructors available with the ApexMap class.Initializes a new instance of the ApexMap class by assigning the specified key and value. This constructor creates a single key–value entry that can be included in an embedded AI Apex map for passing contextual data to embedded AI logic.Initializes the ApexMap class.Represents key of the key-value pair. This property is used to store the unique ID or name of the data.Represents value of the key-value pair. This property is used to store the data associated with the key.Create a copy of the ApexMap object and convert key-value pairs to string format.Returns a string representation of the ApexMap object.
RecordApexRepresentation Class: Contains properties and a method to create a serializable representation of a record and its associated data for AI service integration and data processing.Learn more about the constructors available with the RecordApexRepresentation class.Initializes a new instance of the RecordApexRepresentation class with the specified object type, primary record data, and related record data. This constructor represents a structured record and its relationships for consumption by embedded AI logic.Initializes the RecordApexRepresentation class.Stores the type of the object.Stores a list of objects, where each object holds a key-value pair.Stores a list that contains a child or related records associated with the record data.Create detailed, hierarchical record objects and convert them to a custom JSON string for structured AI input.Converts a JSON-formatted string into a RecordApexRepresentation instance. This method parses the provided JSON and constructs a structured record representation that can be used by embedded AI logic.Returns a structured JSON string representation of the RecordApexRepresentation object and its nested related records.
AppointmentBase Class: An abstract base class that represents the care provider or the practitioner information.Represents details about the care provider or the practitioner.
AppointmentBookingInteropFhirAdapter Class: Represents the global class that implements the AppointmentBookingInterop interface.Contains set of options to book a healthcare appointment with the external scheduling system. Contains set of options to cancel the booked appointment from the external scheduling system.Contains set of options to find available time slots for healthcare providers who match the patient’s needs.Contains set of options to retrieve the slot status.
AppointmentProvider Class: Represents additional information about the care provider and an appointment.Represents the code for the appointment type.Represents the ID of the care provider.Represents the unique National Provider Identifier that is assigned to each facility and licensed practitioner.Represents the facility ID of the practitioner.Represents the code of the service type to be performed at the appointment.Represents the ID in the source system of the facility where the encounter will occur.Represents the ID in the source system of the practitioner with whom the encounter will occur.Represents the name of the source system the provider record came from.
BenefitsItem Class: Specific service covered by the insurance plan.Name of the category this benefit is in. Indicates whether the benefit is available only in-network (true) or both in-network and out-of-network (false). The default value is 'false'. Description of the coverage for non-preferred providers.The type of service this plan benefit item provides.The code for the type of service this plan benefit item provides.
BenefitsItemLimit Class: Services not covered, or expenditures required for coverage. Defines the persons eligible for the benefit item. Possible values are EmployeeSpouse, Family, Individual. General information about the limit. Specifies whether the benefit refers to in-network providers or out-of-network providers. Specifies the type of time period during which the benefit item is available. Possible values are Calendar Year, Day, Month, Year to Date. To save the benefitValue in the AllowedLimitfield, set the termType to a value other than Remaining.
BenefitsVerificationRequest Class: Request for verification of benefits.Identifies the associated case. Default National Provider Identifier to be used in the benefits verification request.Specifies the organization name to use for the benefits verification request service. Represents the code of the service type to be performed.
BenefitsVerificationResponse Class: Response for verification of benefits. Last day of the coverage benefit period.First day of the coverage benefit period.Specific service covered by the insurance plan.Identifies the benefit verification request that this message responds to.Use to respond with an error indication following errors such as request-forbidden responses, custom validation errors, or expired API tokens.Indicates whether the coverage benefit is currently in force.Full JSON response from external system.
BookAppointmentRequest Class: Contains set of options to book a healthcare appointment.Represents the type of appointment, such as annual physical or intake examination.Represents optional extra information about the appointment.Specifies the type of service to be performed at the appointment, such as dental cleaning or surgery.Represents the time period slot that’s assigned to the appointment.Represents the ID in the source system of the facility where the encounter will occur.Represents the ID in the source system of the patient.Represents the ID in the source system of the practitioner with whom the encounter will occur.Represents the name of the source system the patient record came from.
BookAppointmentResponse Class: Represents the appointment booking details from the external scheduling system.Represents the unique identifier of the appointment in Health Cloud.Represents the response from the external scheduling system encoded as JSON.Represents optional extra information added to the appointment.Represents the unique identifier of the patient in Health Cloud.Represents the date and time that the available time slot ends.Represents the date and time that the available time slot starts.Represents the unique identifier of the appointment in the source system.Represents the ID of the patient in the source system.Represents the name of the external scheduling system from which the record was sourced.Represents the status of the appointment.
CancelAppointmentRequest Class: Contains set of options to cancel the booked appointment.Unique ID of the appointment in Health Cloud. The appointment ID comes from the ServiceAppointment object.Represents the type of appointment, such as annual physical or intake examination.Represents the reason for canceling the appointment.Specifies the type of service to be performed at the appointment, such as dental cleaning or surgery.Represents the time period slot that’s assigned to the appointment.Represents the healthcare facility where the encounter will occur in the external scheduling system.Represents the ID of the patient in the external scheduling system.ID of the practitioner who is performing care in the encounter.Name of the external scheduling system from which the record was sourced.
CancelAppointmentResponse Class: Represents the appointment cancellation details from the external scheduling system.Represents the appointment identifier from the external scheduling system.Represents the response from the external scheduling system encoded as JSON.Represents the ID of the service appointment that you want to update.Represents the status of the healthcare appointment.
FindSlotsRequest Class: Contains set of options to find available time slots for providers who match the patient’s needs. This class extends the AppointmentBase class and inherits its properties.Represents the start of date range for slots in ISO 8601 format, for example, 2021-02-26T21:24:31.000Z.Represents the end of date range for slots in ISO 8601 format, for example , 2021-02-25T18:24:31.000Z. In the default Apex class, if the property is set to True, gets a provider's next 160 available slots for appointment scheduling. If set to False, gets the next 500 available slots of providers in general. Represents a patient's AccountId.
GetSlotStatusRequest Class: Contains set of options to retrieve the slot status.Unique identifier for the time period slot in the external scheduling system that’s assigned to the appointment.Name of the external scheduling system from which the time period slot record came from. This information comes from Healthcare Practitioner Facility.Represents the ID of the source system from which the request was sourced.
HomeHealth: Contains Apex implementation for Manual Scheduling for healthcare appointments.
PricingAttribute Class: Represents the attribute key, attribute value, and a boolean indicating if the attribute is a picklist type for a product.Represents the unique identifier of the Attribute Definition for the Product.Represents the value of the attribute definition that needs to be considered for pricing, if the attribute is of type Picklist then the attribute value should be a unique identifier of the Attribute Picklist Value.Represents if the attribute definition is of type Picklist.
ProductPricingAttributeDetails Class: Represents details about a product's pricing attributes and their associated quantities.Represents the list of Pricing Attribute Apex Objects that are applicable for the Product.Represents the unique identifier of the Product.Represents the count of the products for which the pricing attributes are applicable.
RecurringVisitSchedulingInput Class: Contains the input for scheduling recurring home visits, including the default address, work type configurations, recurrence series, resource assignment setting, and time zone.Indicates whether Field Service assigns a resource to the service appointments. When false, the service appointments are created and left unassigned. A null value behaves as true.ID of the scheduling policy for the request. This value is required. An individual series can override it.ID of the service territory for the request. This value is required. An individual series can override it.IANA time zone ID used to interpret series start dates and time slots. If this value is omitted, the running user's time zone is used.Request-level visit address. A series uses this address when the series does not specify its own address.Recurring series that make up this scheduling request. Each series defines its own recurrence rule, time slots, and optional overrides.Request-level work type configurations. The request can include up to five configurations. A series can override fields for a work type.
Slot Class: Represents the time period slot details for the appointment.Represents the date and time that the appointment time slot ends in ISO 8601 format, for example, 2021-02-26T21:24:31.000Z..Represents the date and time that the appointment time slot starts in ISO 8601 format, for example, 2021-02-26T21:24:31.000Z..Represents the status of the time slot.Represents the ID of the time slot in the external scheduling system.Represents the name of the external scheduling system from which the record was sourced.
VisitAddress Class: Represents an address for recurring home visits.City portion of the visit address.Country portion of the visit address.Postal code portion of the visit address.State or province portion of the visit address.Street portion of the visit address.
VisitRecurrenceDetails Class: Represents one recurring series for home visits. Each series defines a recurrence pattern and can override request-level defaults.Indicates whether time slots are derived from operating hours instead of the visitTimeSlots list. When true, operating hours take precedence over explicit slots.Next recurrence occurrence after this series' last scheduled visit. The value is written at the end of each scheduling run and used to start the next scheduling cycle.ID of the operating hours record used to derive time slots when isTimeSlotFromOperatingHours is true.Position of this series relative to the other series in the request.RFC 5545 recurrence rule that defines the visit pattern for this series.ID of the scheduling policy for this series. This value overrides the request-level scheduling policy.ID of the service territory for this series. This value overrides the request-level service territory.Anchor date that the recurrence rule is expanded from, interpreted in the effective time zone.Visit address for this series. This value overrides the request-level visit address.ID of the source record for this series. Series in the same request can reference different source records.Explicit time-of-day slots for this series. These slots are ignored when isTimeSlotFromOperatingHours is true.Work type configurations for this series. A non-null value replaces the request-level configuration for that field. A null value inherits the request-level configuration.
VisitTimeSlot Class: Represents a time slot within a day for recurring home visits.End time of the slot, in HH:mm or HH:mm:ss local time.Zero-based position of this time slot among the day's slots.Start time of the slot, in HH:mm or HH:mm:ss local time.
VisitWorkType Class: Represents a work type configuration for recurring home visits.Additional instructions attached to the visit for this work type.Total minutes of existing, non-canceled service appointments already scheduled for this work type under the clinical service request. The value is 0 when no clinical service request ID is provided. This property is output only.Duration of each appointment, in minutes. This value overrides the work type's default service appointment duration.IDs of the service resources preferred when scheduling this work type.IDs of the service resources required to schedule this work type.IDs of the skills required for visits of this work type. Skills associated with the work type are removed before these IDs are used.Total duration, in minutes, of scheduled and already scheduled time for this work type. This property is output only.IDs of the work plan templates used to create work plans on the work order for this work type.ID of the work type that this configuration applies to.
FieldValue Class: Contains a key-value pair represented by the developer name and value of the field. The key-value pair is used for both search results and verification.Creates an instance of the FieldValue class with the specified parameter values.Creates an instance of the FieldValue class.The developer name of the field that is used for search results and verification.The value of the field that is used for search results and verification.
ProcessDefinition Class: Contains the verification process definition, including the list of process details.Creates an instance of the ProcessDefinition class with the specified parameter values.Creates an instance of the ProcessDefinition class.Specifies the display layout of the search component is tab or stacked.Represents the details of verification processes.
ProcessDetail Class: Contains the verification process details.Creates an instance of the ProcessDetail class with the specified parameter values.Creates an instance of the ProcessDetail class.Specifies the apex class that’s used to search and verify data in an external system.Specifies the source type of the data.Specifies the developer name for the process detail.Specifies the name of the field that contains details about the record that's shown to the user after identity verification is successful.Indicates whether retry is allowed after the retry limit (true) or not (false). The default value is false.Specifies the label for the process detail.Specifies the name of the process detail for secondary search.Specifies the minimum number of optional verifiers that must be checked.Specifies the retry limit to verify process details.Specifies the API name of the object on which search is performed.Specifies the conditions used to filter search results.Specifies the values used to sort search results.Specifies the unique idenfitying field of the selected search result.Specifies the sequence in which the search is performed and the search result is displayed.Specifies whether the search is text-based or object-based.Specifies the list of verification process fields.
SearchFilter Class: Contains data filters that is applied in object-based search.Creates an instance of the SearchFilter class with the specified parameter values.Creates an instance of the SearchFilter class.Specifies the developer name of the field that must be searched in object-based search.Indicates whether the developer name of the field is used as a search filter.Indicates whether the value of a field is used as a search filter.Specifies the value filter to be applied on the field to be searched in object-based search.
SearchFilters Class: Contains a list of data filters to be applied for object-based search.Creates an instance of the SearchFilters class with the specified parameter value.Creates an instance of the SearchFilters class.Indicates whether a list of data filters is set in object-based search.Specifies the list of data filters that can be applied in object-based search.
SearchRequest Class: Contains information about the search request data. The search request represents search filters for object-based search, search terms for text-based search, and the verification context that includes the process definition, process details, and process fields.Creates an instance of the SearchRequest class with the specified parameter values.Creates an instance of the SearchRequest class.Specifies the search criteria used for the object-based search.Specifies the search term for the account to use when performing a search.Specifies the object that contains the setup data and context required to perform the search.
SearchResult Class: Contains the contract of search results in tabular format for either the object-based or text-based search.Creates an instance of the SearchResult class with the specified parameter values.Creates an instance of the SearchResult class.Represents the search result header field list that contains the metadata information of the columns that are part of the search result.Represents the search result row field list that contains the column values for a specific row.
SearchResultHeader Class: Contains information about the search result header field list. This list represents the metadata information of the columns that are part of the search result.Creates an instance of the SearchResultHeader class with the specified parameter values.Creates an instance of the SearchResultHeader class.Represents the data type of the header field.Represents the developer name of the field.Represents the label of the field.
SearchResultRow Class: Contains information about the search result row field list. This list represents the column values for a specific row that are part of the search result.Creates an instance of the SearchResultRow class with the specified parameter values.Creates an instance of the SearchResultRow class.A list of object record fields on which the data has been verified.
SelectedSearchResult Class: Contains the details of the record that has been selected for verification.Creates an instance of the SelectedSearchResult class with the specified parameter values.Creates an instance of the SelectedSearchResult class.Specifies the name of the object to be verified.Specifies the object record ID on which the data is to be verified.Specifies the object record fields on which the data is to be verified.
SelectedVerifiedResult Class: Contains information about the verified object that is used for the secondary search.A list of details about the verified object that is used for secondary search.
VerificationContext Class: Contains information about the verification context, including the process definition, selected search result, selected verified result, and verified result.Creates an instance of the VerificationContext class with the specified parameter values.Creates an instance of the VerificationContext class with the specified parameter values.Creates an instance of the VerificationContext class.Indicates whether the verification result is successful or not.Indicates the request response message.Represents the identity verification process definition.Represents the details of the object and fields to appear in the search result.Represents the data from primary search, which is used for secondary search.Represents the verified result.
VerificationProcessField Class: Contains details of the fields used for both search and the verification process.Creates an instance of the VerificationProcessField class with the specified parameter values.Creates an instance of the VerificationProcessField class.Specifies the source type of the data.Specifies the data type of the field.Specifies the developer name of the field.Specifies the name of the field that contains the verification data based on the selected field type.Specifies the type of the field.Stores the formula to specify search filter that’s applied to the field value.Indicates whether the user can manually enter the identity verification details (true) or not (false). The default value is false.Specifies the label of the field.
VerificationProcessFieldList Class: Contains information about the list of fields used for both search and the verification process.Creates an instance of the VerificationProcessFieldList class with the specified parameter values.Creates an instance of the VerificationProcessFieldList class.Represents the list of fields used for verification.
VerifiedDetails Class: Contains details about the verified object that is used for secondary search, including the process that’s used to verify the search object.ID of the record that's shown to the user after identity verification is successful.Name of the record that's shown to the user after identity verification is successful.Specifies the label of the verified search object.Specifies the name of the process that’s used to verify the search object.Specifies the name of the object that is searched.Specifies the ID of the verified search object.
VerifiedResult Class: Contains information about the verification result that includes the required verifiers and optional verifiers and the verification status.Creates an instance of the VerifiedResult class with the specified parameter values.Creates an instance of the VerifiedResult class.Represents the list of optional input representations for verifier fields.Represents the list of required input representations for verifier fields.
Verifier Class: Contains a list of input representations for verifier fields, including the optional and required fields.Creates an instance of the Verifier class with the specified parameter values.Creates an instance of the Verifier class.Specifies the developer name of the field.Indicates the verification state on the field.
BookingStatus Enum: Represents a possible status of a healthcare appointment.
ResourceDetails Class: Represents the home visit details for manual scheduling of appointments. Once the scheduler has selected the recommended resources along with the time slot, it will schedule the appointment using this Apex class.The ID of the selected service resource.End date time of the selected slot for appointment.Start date time of the selected slot for appointment.Sequence number on which appointment needs to schedule.
HomeVisitDetails Class: Represents the details of the home visit requests. Once the scheduler approves the visit requests submitted by the patient or the quote requests submitted by the care coordinator, use this Apex class to retrieve the home visit details.The ID of the selected service resource.The source of the home visit service resource.
SuggestedResponseAssessmentService Methods: Calls the PreviousAssessmentResponses Connect API to retrieve suggestions based on prior responses.Calls the prompt service to get the suggested responses.Merges suggestion from both sources.
GroupVisitAddress Class: Represents the details of the group visit address.The type of address used for the group visit.The city of the address where the group visit is scheduled.The full, formatted address where the group visit is scheduled.The country of the address where the group visit is scheduled.The unique identifier for the group visit address.The postal code of the address where the group visit is scheduled.The state of the address where the group visit is scheduled.The street address where the group visit is scheduled.
HomeVisitPatientBenefitDetails Class: Represents the home visit details for storing benefit related data. This class is used in the Additional Benefits flow in Budget screen and Agent benefit review flow in Agentforce.The ID of patient benefit.The date on which the benefit ends.The name of the benefit.The date on which the benefit starts.The ID of the product catalog.The name of the product catalog.The ID of the product category.The name of the product category.The ID of the coverage benefit.The ID of the coverage Benefit Item.The ID of the coverage benefit item limit.Indicates if the benefit ID is present in the system.The ID of the member plan.The name of the member plan.The ID of the product.The name of the product.The count of the benefit item.The price of the benefit.
HomeVisitPatientQuoteDetails Class: Represents the home visit details for storing quote related data. This class is used in the Additional Quotes flow in Budget screen and Agent Quote review flow in Agentforce.The quote created date.The ID of the service territory.Indicates if the product is travel inventory record type.The ID of the location.The ID of the operating hour.The ID of the opportunity.The ID of the price book.The list of product names in the quote.The list of product IDs in the quote.The quote end date.The quote end time.The ID of the patient's quote details.The name of the quote.The price of the quote.The quote start date.The quote start time. The selected time slot of the operating hour.The source reference type, for example, Opportunity.The count of the visit.The price of the benefit.The scheduling pattern for the recurring visit.The Start Of Care or Recurring visit type.
AppointmentBookingInterop Interface: Contains default Apex implementation for healthcare appointment availability and booking.Creates the healthcare appointment in the external scheduling system.Cancels the booking appointment in the external scheduling system.Finds the available time slots for providers who match the patient’s needs.Retrieves the status of the time period slot that’s assigned to the appointment.This is an example implementation of the default class AppointmentBookingInteropFhirAdapter that implements the healthcloudext.AppointmentBookingInterop interface.
IUnifiedHealthScore
Interface: Stores additional information in the action logs.Stores health score information in the Health Score Action Log object. The action history logged in Health Score Action Log doesn’t include score information by default.
IdentityVerificationExt Interface: The IdentityVerificationExt interface enables you to verify a caller’s identity.Returns the verification data that contains the columns to be verified.Returns the search result that includes the verification data.
DocumentAI Namespace: The DocumentAI namespace provides classes for Document AI to process and extract data from documents, including configurations for duplicate detection, post-transformation, and post-save processing.
embeddedai Namespace: The embeddedai namespace provides classes and methods to manage and represent records and data in Apex to support embedded AI features.
HealthCloudExt Namespace: The HealthCloudExt namespace provides an interface and classes for Health Cloud to integrate with a source electronic health records (EHR) system.
HealthCloudExt Namespace for Benefit Verification: The HealthCloudExt namespace provides an interface and classes for Health Cloud to integrate with a source electronic health records (EHR) system.
hlthcrbilling Namespace: The hlthcrbilling namespace provides classes used to capture billing information for products in Salesforce Health Cloud. Contains the billing details for one or more products being ordered, including the account, price book, work type, order date, and shipping address. The following are properties for ProductBillingDetails. The ID of the Account for which the products are being billed.The date the order is placed.The ID of the Pricebook2 record used to price the products in the order.The list of products to be billed. Each item describes a single line in the order.The shipping address to which the ordered products are delivered.The ID of the Work Type record associated with the order. Represents a single product line item, including the product ID, price book entry, quantity, unit price, and applicable pricing attributes. The following are properties for ProductDetails.The ID of the PricebookEntry record that defines the price for this product in the active price book.The list of pricing attributes that apply to this product line item.The ID of the Product2 record being billed.The quantity of the product being ordered.The unit price of the product.
id_verification Namespace: The id_verification namespace provides an interface and classes for Health Cloud to verify the caller’s identity.
Benefit Verification: Use these resources to verify the health benefits covered by the patient's insurer. The call center agent can view the coverages in the patient's record page.
Get Slots (POST): Get slots associated with the provider or asset.
Template Match Input: Input configuration for template matching against an uploaded or hosted document.
Care Diagnosis Input: Associated diagnosis including code type, name, and description. One or more care diagnoses can be associated with a care request.
Care Request Drug Input: Requested drug including name, strength, frequency, and instructions for administration. One or more drug requests can be associated with a care request.
Care Request Input: The general details of a care-related request including member information, admission date, decision reason, and so on. A single request can contain multiple diagnoses or drugs. Care requests include prior authorizations for drugs and services, admission notifications, concurrent review of admissions, appeals, complaints, and grievances.
Care Request Item Input: The details of a care service request, including name, modifiers, and the effective date. One or more care service requests can be associated with a care request.
Care Request Reviewer Input: The general details of the care request, care request item, care request drug, or care diagnosis associated with the care request reviewer.
Patient Input: Input containing data for a single patient.
Post Transform Data Processing Input: The validation request properties matching the initial structural outputs derived during mapping transformations.
Post Save Operations Input: The properties context containing identities for newly initialized record objects.
Previous Assessment Responses Input: The request representation to fetch past assessment responses for both Discovery Framework and MCG assessments.
Verifier Input: Input representation for verifier fields.
Visited Party Attributes Input: Input representation of the visiting party. For example, for a medical device visit, the visiting party can be the surgeon and the anesthesiologist.
Visitor Attributes Input: Input representation of the visitor attributes. For example, for a medical device visit, visitor can be the sales representative and the clinical specialist.
Work Type Lead Time Input: Input representation of the request to get a list of work types and their associated lead times.
Document Template Match: Automatically identifies the Document AI Automation template for a specified document.
Assessment Previous Responses: Retrieves historical assessment response data for healthcare applications, supporting both internal Discovery Framework and external Milliman Care Guidelines (MCG) assessments.
Book Slot Chain (POST): Create service appointments for a care program enrollee in advanced therapy management based on the provided appointment slots.
Patients (GET, POST, PUT): Retrieve the FHIR patient resource record details. Create or update a patient record rather than making multiple separate calls to the objects in Salesforce.
Visits (POST): Create visits for sales representatives. For example, for a medical device visit, a sales representative visits the surgeon or a hospital location.
Digital Verification (POST): Perform verification for the digital verification records within advanced therapy management.
Extract Document Data (POST): Synchronously extracts unstructured file data using an intelligent ingestion template.
Quotas and Allocations: Find available slots and manage quotas for therapies (Work Procedures) at various stages (Work Types) across multiple treatment centers.
Referral Management: Create a patient referral in a Salesforce org from an external data source.
Split Documents: Split a document and attach one or more pages from the transformed document to Salesforce records.
Omniscript: Get the discovery framework structure stored as OmniProcess.
Transform Extracted Data (POST): Transforms stringified JSON extraction outputs into organized object mapping parameters synchronously.
Synchronization: Synchronize the calculated score from the Data Cloud for a given score category. The fetched scores are stored in the HealthScore object.
Benefits Verification (POST): The Verify Benefits API call is the main resource for checking which health benefits are available to a patient.
Work Type Lead Time (POST): Get a list of work types and their associated lead times that are optimized across regions for a specific advanced therapy.
Care Request Drug: Requested drug including name, strength, frequency, and instructions for administration. One or more drug requests can be associated with a care request.
Care Request Item: The details of a care service request, including name, modifiers, and the effective date. One or more care service requests can be associated with a care request.
Care Request: The general details of a care-related request including member information, admission date, decision reason, and so on. A single request can contain multiple diagnoses, services, or drugs. Care requests include prior authorizations for drugs and services, admission notifications, concurrent review of admissions, appeals, complaints, and grievances.
Program Enrollment Result: Result containing details of all patient enrollment status. If there is success, it contains id of new records created for each patient.
Provider Search Result: Detailed information about a single healthcare provider matching the search criteria.
Question Response Output: Contains the response values and assessment metadata for a single question.
Quota Availability: Output representation of a list of available quotas, and their start and end dates for a work type.
Work Type Lead Time Output: Output representation of a list of work types and their associated lead times.
Intelligent Document Automation: Use the Intelligent Document Automation data objects to simplify the document management process, reduce manual data entry, and get patients the right care and services faster by managing patient and member forms all in one place, from intake through processing.
Create Referral Action: Create a patient referral record. A patient referral consists of multiple objects, such as an account, clinical service request, and clinical service request detail.
Get Appointment Slots Action: Get available appointment slots for healthcare providers or assets based on specified criteria. Calls the Get Appointment Slots Connect 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.
Parse Conversation Response Action: Parses the JSON response from the Parse Conversation Inquiries prompt template from a contact center conversation transcript into a conversation summary, a resolution status, extracted inquiries, and an inquiry count.
Advanced Therapy Management: Advanced Therapy Management helps streamline complex procedures that involve multiple appointments across different locations. Use Advanced Therapy Management’s Multi-Step Scheduling solution for easy scheduling of appointments for program participants. Configure procedure steps based on lead times and set up affiliated service territories to establish where work types are sequentially performed.
Adverse Events: Adverse Events data model helps you in managing and documenting any unfavorable or unintended signs, symptoms, or diseases that occur as a result of an intervention, such as medical care or research, that impacts a patient or group of patients or participants. These adverse events can include a wide range of physical or psychological effects that varies from mild discomfort to serious health complications.
Apex Reference: This Apex reference goes into detail about the built-in Apex classes, interfaces, methods, or enums for Health Cloud.
Assessment Generation: Assessment Generation leverages Einstein generative AI capabilities to create assessment questions by efficiently extracting question details from complex source documents. This innovation, combined with the power of Discovery Framework, helps you to build comprehensive healthcare questionnaires that meet your business needs.
Home Health: The Home Health data model helps you store data for your organization’s home healthcare services. You can store the preferences patients have for their services, the skills your resources possess, the details of each home visit, and so on. The Home Health data model is primarily built over the Salesforce Field Service data model and uses many of its objects.
ClinicalServiceRequest: Represents requests for a procedure or diagnostic service that needs to be planned, proposed, or performed as part of the patient’s healthcare. This object is available in API version 51.0 and later.
ClinicalServiceRequestDetail: Associates records from different objects to a clinical service request record to add more information to it. This is a multi-object junction object. This object is available in API version 51.0 and later.
CoverageBenefit: Represents the benefits provided to a covered member by a purchaser’s plan.
MedicationStatement: Represents a record of medication that the patient is currently taking or has taken in the past. This object is available in API version 51.0 and later.
Timeline: Use Timeline to configure a chronological view of records from multiple objects.
TimelineObjectDefinitionLocalization: Represents the translated value of a timeline configuration’s master label when the Translation Workbench is enabled for your organization. This object is available in API version 60.0 and later.
Intelligent Appointment Management: Health Cloud integrates with a customer’s appointment management system to provide a patient appointment booking experience in Salesforce for call center agents and care coordinators. The Health Cloud data model for appointments enables you to work with multiple source systems operating on different electronic health record platforms.
Health Assessments: Health Cloud Assessments use the power of Discovery Framework and OmniStudio to build more complex questionnaire paths.
Benefits Verification: The benefits verification data model supports providers, payers, and life sciences organizations in determining benefits coverage for services and products provided.
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.
REST Reference: You can access Health Cloud Business APIs using REST endpoints. These REST APIs follow similar conventions as Connect REST APIs.
Care Program Management: Drive increased adherence and improve patient outcomes using the care program management data model. Now you can enroll and manage patients to achieve the maximum impact of your programs.
Care Services Review and Response: These RESTful APIs support data elements required for ANSI X12 278 format Health Care Services Review and Response. Also referred to as ANSI 278 Authorization APIs, they enable payer organizations to electronically receive prior authorization requests and referral requests from providers. Other users of these APIs can be healthcare providers, payers, plan sponsors, or other entities involved in health care services review, such as clearinghouses.
Clinical Data Model: Patient data and healthcare records are important in the healthcare industry. Without accurate information, performing and managing care becomes difficult. These records are readily available if a patient seeks care from the same provider every time. However, in reality, a patient’s healthcare journey takes them to multiple providers and hospitals at different times. Because the patient’s health hinges on the accuracy of their medical records, it’s crucial for the systems used by different providers and hospitals to be interoperable. And to make this interoperability possible, it’s vital to have some industry-recognized standards for how these records are structured, stored, and transferred. That’s where the standards defined by Health Level 7 (HL7) come in.
Predecessors to Code Sets and Code Set Bundles in Health Cloud: Before the Spring ’21 release, the Healthcare Procedure and Healthcare Diagnosis objects stored codes specifically related to procedures and diagnoses. These codes were used for prior-authorization requests and approval processes. Since the Spring’21 release, Health Cloud uses the Code Set and Code Set Bundle objects for this purpose instead.
Coverage Requirement Discovery: Payer organizations in the healthcare industry can use the FHIR-aligned Coverage Requirement Discovery (CRD) data model to help providers access member and coverage-related information in real time, directly from their Electronic Health Records (EHR) system. The automation of coverage requirement discovery reduces time spent on administrative tasks, improves the chances of coverage approval, and helps in reducing human errors.
Create Provider: This API creates healthcare provider records along with the corresponding Account records (for facilities) or Contact records (for practitioners). You can also use it to manage information about practitioner credentials. The Create Provider API is mainly intended to support the operations of payer employees who handle provider records, such as credentialing specialists. Notes about lookupsThe Create provider API supports all standard and custom fields. Details and JSON samplesHere are some JSON samples that you can use as a starting point to build request bodies and interpret responses.This API supports bulk transactions, but Healthcare Provider records are committed one at a time. An input request can succeed in full or in part. Each provider included in the request succeeds or fails on its own.
Crisis Support Center Management: The Crisis Support Center Management data model lets users provide a range of crisis services from a single app. Use a simplified intake flow, search for providers and beds across facilities, and more.
Integrated Care Management: Integrated Care Management provides a data model to store clinical data related to a patient or member’s care plans. This data model is both USCDI and FHIR R4-aligned, which helps with your system’s interoperability.
Disease Surveillance: Disease Surveillance tracks and manages disease data and public health activities. Use the Disease Surveillance data model to centralize patient information, including demographics, disability status, medications, and specimens. Streamline health monitoring and enable timely, informed decision making by gaining a comprehensive view of disease-related data, such as definitions, investigations, and outbreaks.
Document AI Automation: Leverage the generative AI capabilities of Document AI Automation to automatically extract data from PDFs, such as lab reports and disease definitions, and convert it into structured Health Cloud records. Focus on critical tasks by reducing manual data entry efforts, and ensure consistent case intake and disease data management, facilitating faster follow-up and investigation. Use these resources to leverage Document AI Automation:
Documentation Templates and Rules: Da Vinci Documentation Templates and Rules (DTR) is a framework under the HL7 FHIR standards that facilitates the exchange of documentation requirements in the healthcare industry. DTR enables the use of standardized templates and rules in the exchange of critical healthcare documentation, ensuring compliance and reducing administrative burden.
Electronic Signatures: Manage electronic signatures by using Digital Verifications. Set up signature trails for records or workflows that require users to verify key updates. Define signature details such as the order of designated verifiers and whether designated verifiers belong to a user group or have a specific participant role.
Engagement Interaction: The engagement data model stores details, such as start date and end date, time, topic, and attendees, about an interaction between a customer or a customer-authorized representative and a customer service representative (CSR) or contact center agent (CCA). You can add up to 50 custom fields each in the EngagementAttendee, EngagementInteraction, and EngagementTopic objects. The engagement objects also support quick actions that help CCAs to perform routine actions quickly without navigating to multiple pages. CCAs can also create personalized list views for engagement objects by using the My engagement attendees, My engagement interactions, and My engagement topics filters.
Account Custom Fields: Custom fields extend the standard Account object for use in Emergency Response Management.
Emergency Response Management Business APIs: Use Business APIs for building integrations 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 loading details of contact encounters into the system.
Contact Custom Fields: Custom fields extend the standard Contact object for use in Emergency Response Management.
Health Cloud FHIR APIs: Use Salesforce Healthcare API to securely connect and interact with a system that uses Fast Health Interoperability Resources (FHIR) APIs.
FHIR Subscription: Publishers can use the Fast Healthcare Interoperability Resources (FHIR) Subscription data model to store subscription topics, subscriber details, the filters and parameters applied to a subscription, and other subscription details. When an event change occurs in the subscribed resource, it triggers a notification and a platform event is created as an Interoperability Topic Subscription Event record. Then, Mulesoft sends the notification to the subscriber’s endpoint in real time.
Financial Assistance Program: The financial assistance program data model helps health and life sciences organizations implement several financial assistance programs for eligible patients to receive assistance with their out of pocket medical expenses.
Intelligent Sales: Help your sales team plan and execute sales visits and manage field inventory with Intelligent Sales.
Medication Management: The Medication Management data model provides objects to enable providers, care coordinators, and clinicians to perform a medication reconciliation and medication therapy review of their patients’ medication regimen. The data model provides objects for managing information on medication reconciliations, medication recommendations, and comprehensive and targeted medication reviews conducted for patients.
Health Insurance: The health insurance data model provides objects for managing the ways care is paid for. It represents information about participants such as employment, insurance coverage, and dependents. You can manage details of the benefits provided by plans to members and treatment preauthorization requests made by members or providers.
MuleSoft Direct Integrations: Use the Salesforce integration apps that are out-of-the-box integration templates with pre-built transformations that can be used to integrate Health Cloud with external systems. These integration apps are available in MuleSoft Exchange.
Participant Management: Participant Management data model helps you to streamline the recruitment and enrollment processes in clinical trials with advanced digital solutions. With this data model, you can store clinical trial data representing care programs and research studies. It’s USCDI and FHIR R4-aligned, which helps with your system's interoperability and compliance while managing participant data efficiently.
Patient Program Outcome Management: Patient Program Outcome Management data model helps you to improve patient and program outcomes by defining and measuring program outcomes, linking patient progress to program outcomes. Program Leads can define outcomes for a care program, and can generate a program and patient outcome summary. Additionally, case agents can generate a patient outcome summary.
Patient Segmentation: The Patient Segmentation data model helps the Patient Segmentation dashboard generate insights into patient demographics and risk scores based on risk adjustment factors.
Pharmacy Benefits Verification: Pharmacy Benefits Verification uses a data model that’s FHIR-CARIN and NCPDP aligned to store its data and make it interoperable. The pharmacy benefits verification data model supports drug manufacturers, providers, pharmacists, and healthcare organizations in determining pharmacy benefits coverage for the medications prescribed to the patients under a care program.
Provider Network Management: Provider Network Management allows health insurance companies to bring providers into their network and helps members or patients find care that fits their needs. It provides objects for managing provider networks and contract payment agreement terms.
Provider Relationship Management: Use the Provider Relationship Management data model along with standard Salesforce objects to manage your provider relationships.
Access to Provider Network Management: The provider network management standard objects are available to users with the Health Cloud Platform and Provider Network Management permission set licenses and the Health Foundation permission set.
Providers: Use these resources to create practitioner or facility records, or update existing fields in provider records and insert new fields.
AllergyIntolerance: Represents a clinical assessment of a patient’s allergy or intolerance. This object is available in API version 51.0 and later.
CareObservation: Represents the observed values for care metrics originating from external systems that contain biometric data. This object is available in API version 49.0 and later.
CareObservationComponent: Represents information about a component of a care observation. This object is available in API version 51.0 and later.
CarePerformer: Represents the person performing care in observations, procedure, and immunizations. This person may be a physician, the patient’s contact, or anyone who administered any sort of care to the patient in the context of the concerned care event. This object is available in API version 51.0 and later.
ClinicalAlert: Represents a warning or notification of significance related to different healthcare entities. The subject of the alert may be a patient, a location, a provider, a procedure, or even a medication. This object is available in API version 51.0 and later.
ClinicalDetectedIssue: Represents information about a detected issue resulting from a clinical activity. This object is available in API version 55.0 and later.
ClinicalDetectedIssueDetail: Represents additional information about a clinical detected issue. This object is available in API version 55.0 and later.
ClinicalEncounter: Represents a healthcare related encounter of a patient with a care provider. This is a broad object that covers multiple phases of a patient’s healthcare service experience, all the way from pre-admission to stay to discharge, and everything in between. This object is available in API version 51.0 and later.
ClinicalEncounterDiagnosis: Represents a diagnosis related to a clinical encounter. This object is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalEncounterFacility: Represents information about the different facilities involved in an encounter, the time spent at those facilies, and other relevant details. This is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalEncounterIdentifier: Represents the identifier information for a clinical encounter. This object is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalEncounterProvider: Represents the providers involved in an encounter. This object is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalEncounterReason: Represents the reasons for why the encounter was required. This object is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalEncounterSvcRequest: Represents the service requests related to a clinical encounter. This object is a child object of ClinicalEncounter. This object is available in API version 51.0 and later.
ClinicalServiceRequestDetail: Associates records from different objects to a clinical service request record to add more information to it. This is a multi-object junction object. This object is available in API version 51.0 and later.
ClinicalServiceRequest: Represents requests for a procedure or diagnostic service that needs to be planned, proposed, or performed as part of the patient’s healthcare. This object is available in API version 51.0 and later.
CodeSet: Represents various industry defined codes in the context of their systems and versions of those systems. These codes are used in all sorts of digital records. This object is available in API version 50.0 and later.
CodeSetBundle: Represents a group of code sets across multiple systems and versions. All of these code sets refer to the same conceptual entity. This object is available in API version 50.0 and later.
DiagnosticSummary: Represents the findings, interpretations, and summaries of tests performed on patients. This object is available in API version 51.0 and later.
HealthcareFacility: Represents a healthcare facility and all its related details. These details may be physical, functional, geographic, or business details. This object is available in API version 51.0 and later.
HealthCondition: Represents a clinical condition, problem, or any clinically relevant occurrence that is a matter of concern. This object is available in API version 51.0 and later.
Identifier: Represents identifier information for multiple objects. This object is available in API version 51.0 and later.
Medication: Represents detailed information about different medications. This object is available in API version 51.0 and later.
MedicationRequest: Represents a request or order for the supply of medication, along with information about how it should be administered. This object is available in API version 51.0 and later.
MedicationStatement: Represents a record of medication that the patient is currently taking or has taken in the past. This object is available in API version 51.0 and later.
PatientHealthReaction: Represents a patient’s adverse reaction to an allergy, intolerance, or immunization. This object is available in API version 51.0 and later.
PatientImmunization: Represents information about a patient’s immunizations. This object is available in API version 51.0 and later.
PatientMedicalProcedureDetail: Associates records from different objects to a patient medical procedure record to add more information to the procedure record. This is a multi-object junction object. This object is available in API version 51.0 and later.
PatientMedicationDosage: Represents dosage information for medication. This object is primarily used to add dosage information in MedicationStatement, MedicationRequest, or MedicationDispense records. This object is available in API version 51.0 and later.
PersonLanguage: Represents the use and preference information about a person’s language. This object is available in API version 51.0 and later.
PersonName: Represents detailed information about a person’s name. This object is available in API version 51.0 and later.
ActivityTiming: Represents detailed information about an activity that’s repeated in regular intervals over a period of time. This object is available in API version 52.0 and later.
AuthorNote: Stores notes associated with different types of records along with information about the author of the note and the time the note was authored. The author isn’t necessarily the person who created a record. The author is the person who provided the information in the note. This object is available in API version 52.0 and later.
CareRegisteredDevice: Represents a device or device registration information for a patient or a care program enrollee. This object is available in API version 49.0 and later.
ContactProfile: Represents information about an individual, such as their ethnicity, citizenship, birth place, race, and so on. This object is available in API version 57.0 and later.
DiagnosticSummaryDetail: Represents additional information associated with document reference-type DiagnosticSummary records. This additional information may be related documents, authors, or related encounters. This object is available in API version 52.0 and later.
HealthConditionDetail: This child object is used to associate body site and laterality codes to HealthCondition records. This object is available in API version 52.0 and later.
HealthRiskEvalDetail: Represents additional details of a health risk evaluation, including the basis and reason for the evaluation. This object is available in API version 64.0 and later.
HealthRiskEvalOutcome: Represents the outcome of a risk evaluation, such as the probability of disease occurrence. This object is available in API version 64.0 and later.
HealthRiskEvaluation: Represents the evaluation of health risks. This object is available in API version 64.0 and later.
MedicationDispense: Represents the dispense of a medication to a patient in response to a medication request or order. This object also includes the instructions for how the medication is to be administered This object is available in API version 54.0 and later.
MedicationStatementDetail: Represents additional information associated with MedicationStatement records. This object is available in API version 54.0 and later.
MedicinalIngredient: MedicinalIngredient is a child object of Medication that represents substances or drugs that are used as ingredients in the medication. This object is available in API version 52.0 and later.
PatientImmunizationProtocol: Represents the protocol followed by a provider for a patient’s immunization and its related details. The protocol defines the set of recommendations that are followed while a vaccine is administered. This object is a child of the PatientImmunization object. This object is available in API version 56.0 and later.
PatientMedicalProcedure: Represents detailed information about a healthcare procedure the patient has undergone, is undergoing or will undergo. This object is available in API version 51.0 and later.
MedicationAdministration: Represents an instance of medication administered to a patient. This object is available in API version 64.0 and later.
MedicationAdministrationDtl: Represents the details of an instance of medication administered to a patient. This object is available in API version 64.0 and later.
ProblemDefRelationship: Represents a junction between a problem definition and a related problem definition. This object is available in API version 64.0 and later.
Specimen: Represents a sample used for analysis. This object is available in API version 64.0 and later.
Remote Monitoring and Device Registration: The remote monitoring and device registration data model provides objects for managing data collected from devices issued to patients or program members, such as smart watches and heart monitors.
Request Bodies: This section lists the request bodies for Health Cloud Business APIs. The query parameters for an endpoint are listed along with each resource.
Care Services Review Resources: Use these resources to create or update care services review requests, or get information about the status of existing requests.Get details of existing care services review requests.Create care services review requests or update existing requests.Update care services review requests or update existing requests.
Resources: Use these resources of Health Cloud Business APIs to enhance your Salesforce implementation or integrate with other applications.
Response Bodies: A resource can return a response body in either JSON or XML format.
AppointmentReason: Represents a patient’s reason for making an appointment. Used for self-scheduling in Intelligent Appointment Management. This object is available in API version 53.0 and later.
ApptReasonEngmtChannelType: Represents an available engagement channel for a given AppointmentReason. Possible engagement channels could be video, phone, or in person. Possible appointment reasons could be annual physical, fever, or physical therapy. This object is available in API version 56.0 and later.
AssessmentQuestionSourceDoc: Represents assessment questions and their source document. This object is available in API version 61.0 and later.
CarePractnFacilityAppt: Represents a junction object between a HealthcarePractitionerFacility (practitioner at a facility) and a ServiceAppointment (appointment). This object is available in API version 52.0 and later.
DiseaseDefinition: Represents a disease definition that public health organizations regularly monitor to identify and prevent outbreaks. This object is available in API version 64.0 and later.
DiseaseDefinitionCondition: Represents a condition for disease definition criteria. This object is available in API version 64.0 and later.
DiseaseDefinitionCriteria: Represents disease definition criteria, such as clinical, laboratory, and epidemiologic linkage used to diagnose diseases. This object is available in API version 64.0 and later.
DiseaseInvestigation: Represents an investigation of a disease. This object is available in API version 64.0 and later.
DiseaseInvestigationCase: Represents a junction between a disease investigation and a case. This object is available in API version 64.0 and later.
DiseaseOutbreak: Represents a disease outbreak monitored by the public health organization. This object is available in API version 64.0 and later.
DocumentExtractionRequest: Represents a request to extract documents. This object is available in API version 63.0 and later.
DocumentExtractionRqstStep: Represents each step involved in the document extraction request process. This object is available in API version 64.0 and later.
HousingAssessment__c: Represents the settings for assessing the living situation of individuals. This object is available in API version 49.0 and later.
OrderSource: Represents the source details of an order. This object captures the point of origin for an order and the subsequent action, ensuring full traceability for audit purposes and operational visibility across any organizational process. This object is available in API version 67.0 and later.
PartyAppointmentRequest: Represents an appointment request raised by a patient for their home healthcare services. This object is available in API version 61.0 and later.
PartySchedulePreference: Represents the schedule preference that a patient has for their home healthcare visit. This object is available in API version 61.0 and later.
ProductRequest: Represents a device request made as part of a care program.
SerializedProduct: Records serial numbers for each individual product in an inventory. This object is available in API version 50.0 and later.
Visit: Represents a visit to inspect or assess an applicant’s ability to perform an emergency service.
Social Determinants: The social determinants data model represents the barriers, health determinants, and interventions for a patient or member. Available in API version 45.0 and later.
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.
Unified Health Scoring: Unified Health Scoring (UHS) assists payers and providers by giving them a holistic view into their patients’ health profiles.
Upsert Provider: This business-level API enables you to upsert data in Salesforce to represent a practitioner and all the objects and fields in the Provider data model relevant to a Practitioner, such as NPI, provider specialty, and provider taxonomy. The upsert provider API supports all standard and custom fields. Details and JSON samplesHere are some JSON samples you can use as a starting point for building request bodies and interpreting responses.This API supports bulk transactions, but Healthcare Provider records are committed one at a time. An input request can succeed in full or in part. Each provider included in the request succeeds or fails on its own.
Utilization Management: Utilization Management (UM) is a health insurance plan's process of interfacing with plan members and contracted medical providers to interpret, administer, and explain the medical policies of the health plan. Health Cloud provides objects you can use to review and evaluate medical care services, communicate about clinical policies, and help health plan members ensure they receive the right care in the right setting at the right time.
Fields on Account: Health Cloud fields extend the standard Account object to represent information about patients and providers.
Flow for Health Cloud: Represents the metadata associated with a flow. With Flow, you can create an application that navigates users through a series of screens to query and update records in the database. You can also execute logic and provide branching capability based on user input to build dynamic applications.
Fields on Contact: Health Cloud fields extend the standard Contact object to represent information about an individual.
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.
Fields on Lead: Standard and custom fields extend the Lead object to represent information about an incoming patient.
Member: A member is a person who is the primary subscriber, a dependent, or anyone else who is covered under the insurance plan.
Fields on Opportunity: Standard and custom fields extend the Opportunity object to represent information about an incoming patient.
Payer: A payer is a health insurance company that helps cover the cost of member care. payer is represented by records on the Account object.
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.
Fields on ProductRequest: Health Cloud fields extend the standard ProductRequest object to associate it with care programs and to track modification history.
Purchaser: A purchaser is the organization (an employer) that is providing medical insurance plans for their members (employees).
Purchaser Group: A purchaser group is a subset of the purchaser. For example, your company may have individual employee groups in different regions of the country. Each purchaser group can have separate options for insurance plans.
Purchaser Group Member Association: An association that records the members who belong to a purchaser group. This association is represented by records on the AccountContactRelation object.
Purchaser Payer Association: An association that records the purchasers who purchase plans from payers. This association is represented by records on the AccountAccountRelation object.
Fields on Service Appointment: Standard and custom fields extend the standard Service Appointment object to represent information about a healthcare appointment.
Fields on Event and Task (Activity): Custom fields extend the standard Event and Task objects to represent information about an individual’s activities.
Practitioner Availability at Facilities: To book an appointment, we need to know the availability of a given practitioner at a given facility. To get this information, Health Cloud queries the specific source EHR system, using the IDs of the practitioner and the facility as stored in that source system.
Create Appointment: When the patient selects an available slot, the call center agent books the appointment, which triggers a Get Slot Status REST call to the EHR system.
Find Available Time Slots for an Appointment: When a call center agent wants to schedule an appointment, the first step is to find the available time slots for providers who match the patient’s needs. The call center agent gathers selection criteria and then initiates a search to obtain the available slots for providers who match the criteria.
Intelligent Appointment Management Operations: The available operations for Intelligent Appointment Management include finding available appointment time slots, determining the status of an appointment slot, creating an appointment, getting a scheduled appointment, and canceling an appointment.
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.
Identity Verification: Use these resources to verify the caller's identity. For example, the call center agent can ask the person to confirm their social security number, birth date, insurance details, or driver’s license number.
Intelligent Document Management: Use the Intelligent Document Management resources to create or update records in Salesforce objects based on the content document records or received document records.
Applicant: Specify the care program enrollee represented as an applicant. This object is available in API version 59.0 and later.
Benefit: Represents information about benefits associated with the financial assistance program. Benefits are mapped to the members based on the program rules. This object is available in API version 51.0 and later.
BenefitType: Represents information about the type of benefits, such as Financial Assistance Program, available to the care program enrollee. This object is available in API version 51.0 and later.
ProgramEnrollment: Represents details of enrollment for benefits in a program. This object is available in API version 57.0 and later.
Address: The Address FHIR resource maps to the ContactPointAddress object in Salesforce.
AllergyIntolerance: The allergyIntolerance FHIR resource maps to the AllergyIntolerance and PatientHealthReaction objects in Salesforce.
Attachment: The Attachment FHIR resource maps to the Attachment object in Salesforce.
CodeableConcept: The CodeableConcept FHIR resource maps to the CodeSetBundleBundle object in Salesforce.
Coding: The Coding FHIR resource maps to the CodeSet object in Salesforce.
Condition: The Condition FHIR resource maps to the HealthCondition object in Salesforce.
ContactPoint: The ContactPoint FHIR resource maps to the ContactPointPhone object in Salesforce.
Encounter: The Encounter FHIR resource maps to the ClinicalEncounter, ClinicalEncounterDiagnosis, ClinicalEncounterFacility, ClinicalEncounterIdentifier, ClinicalEncounterProvider, ClinicalEncounterReason, and ClinicalEncounterSvcRequest objects in Salesforce.
Flag: The Flag FHIR resource maps to the ClinicalAlert object in Salesforce.
HumanName: The HumanName FHIR resource maps to the PersonName object in Salesforce.
Identifier: The Identifier FHIR resource maps to the Identifier object in Salesforce.
Immunization: The Immunization FHIR resource maps to the PatientImmunization and PatientHealthReaction objects in Salesforce.
Location: The Location FHIR resource maps to the HealthcareFacility and Location objects in Salesforce.
Medication: The medication FHIR resource maps to the Medication object in Salesforce.
MedicationRequest: The MedicationRequest FHIR resource maps to the MedicationRequest object in Salesforce.
MedicationStatement: The medicationStatement FHIR resource maps to the MedicationStatement object in Salesforce.
Patient: The Patient FHIR resource maps to the Account and Contact objects in Salesforce. Patients are modeled using Person Accounts.
Procedure: The procedure FHIR resource maps to the PatientMedicalProcedure and PatientMedicalProcedureDetail objects in Salesforce.
ServiceRequest: The serviceRequest FHIR resource maps to the ClinicalServiceRequest and ClinicalServiceRequestDetail objects in Salesforce.
AdverseEvent: The AdverseEvent FHIR resource maps to the AdverseEvent objects in Salesforce.
Annotation: The Annotation FHIR resource maps to the AuthorNote object in Salesforce.
CarePlan: The CarePlan FHIR resource maps to the CarePlan, CarePlanDetail, CarePlanActivity, and CarePlanActivityDetail objects in Salesforce.
CommunicationRequest: The CommunicationRequest FHIR resource maps to the TrackedCommunication and TrackedCommunicationDetail objects in Salesforce.
Considerations for Integration: The Salesforce implementation of FHIR resources differs from the FHIR specification. Built on the core Salesforce platform, the FHIR-aligned clinical data model comes with field mappings that help you integrate with the FHIR R4 specification.
CRDMetricData: The CRDMetricData FHIR resource maps to the ServiceInformationRequest, ServiceInfoRequestDetail, ServiceInfoResponseCoverage, SvcInfoRespCoverageDetail,ServiceInfoResponseAction ServiceInfoRespSuggestion, ServiceInfoRespOvrideOptobjects.
Device: The Device FHIR resource maps to the Asset and CareRegisteredDevice objects in Salesforce.
DiagnosticReport: The diagnosticReport FHIR resource maps to the DiagnosticSummary object in Salesforce.
DocumentReference: The DocumentReference FHIR resource maps to the DiagnosticSummary and DiagnosticSummaryDetail objects in Salesforce.
Dosage: The Dosage FHIR resource maps to the PatientMedicationDosage object in Salesforce.
DTRMetricData: The DTRMetricData FHIR resource maps to the ServiceInformationRequest, ServiceInfoRequestDetail, ServiceInfoRequestOperation, andServiceInfoResponseCoverageobjects.
DTRQuestionnaireResponse: The DTRQuestionnaireResponse FHIR resource maps to the Assessment and AssessmentReason object.
DTRStdQuestionnaire: The DTRStdQuestionnaire FHIR resource maps to the AssessmentDefinition, AssessmentQuestion, AssessmentQuestionResponse, and AssessmentQuestionVersion objects.
EpisodeOfCare: The episodeOfCare FHIR resource maps to the CareEpisode and CareEpisodeDetail objects in Salesforce.
Goal: The Goal FHIR resource maps to the GoalAssignment and GoalAssignmentDetail objects in Salesforce.
InformationOrigin: The CRDMetricData FHIR resource maps to the AssessmentQuestionResponse object.
Observation: The observation FHIR resource maps to the CareObservation and CareObservationComponent objects in Salesforce.
Organization: The Organization FHIR resource maps primarily to the Account object in Salesforce.
Mapping FHIR v4.0 to Salesforce Standard Objects: The Fast Health Interoperability Resources (FHIR) standard defined by Health Level Seven (HL7) enables healthcare systems to work seamlessly together enhancing their interoperability. The Clinical Data Model is built to align with HL7’s FHIR R4. However, because of the way the Salesforce platform works, the Salesforce implementation of FHIR R4 isn’t identical to how it’s defined by HL7. Here’s how various FHIR resources map to fields in different standard objects in Salesforce.
PASClaim: The PASClaim FHIR resource maps to the CareDiagnosis, CareRequest, CareRequestDrug, CareRequestItem, CareRequestReviewer, and Identifier obejcts.
PASClaimResponse: The PASClaimResponse FHIR resource maps to the CareProcessingError, AuthorNote, TrackedCommunication, andTrackedCommunicationDetailobjects.
PASMetricData: The PASMetricData FHIR resource maps to the CareRequestExchangeInfo object.
Practitioner: The Practitioner FHIR resource maps to the HealthcareProvider object and person accounts in Salesforce.
PractitionerRole: The practitionerRole FHIR resource maps to the HealthcarePractitionerFacility and CareProviderFacilitySpecialty objects in Salesforce.
RelatedPerson: The relatedPerson FHIR resource maps to the Account and Contact objects in Salesforce, and is connected to the person that person’s related to using the ContactContactRelation__c object.
ResearchStudy: The ResearchStudy FHIR resource maps to the ResearchStudy objects in Salesforce.
Subscription: The Subscription FHIR resource maps to the InteropTopicSubscription, InteropTopicSubscriptionDtl, InteropTopicSubcrParameter, and InteropTopicSubcrFilterobjects in Salesforce.
SubscriptionTopic: The SubscriptionTopic FHIR resource maps to the InteropTopic, InteropTopicDetail, InteropTopicTriggerCriteria, InteropTopicFilterand InteropTopicNtfcnResourceobjects in Salesforce.
Timing: The Timing FHIR resource maps to the ActivityTiming object in Salesforce.
AL1 - Patient Allergy Information: The Patient Allergy Information (AL1) HL7 segment maps to the AllergyIntolerance object in Salesforce.
CE - Coded Element: The Coded Element (CE) HL7 segment maps to the CodeSet object in Salesforce.
OBR - Observation Request Segment: The Observation Request Segment (OBR) HL7 segment maps primarily to the ClinicalServiceRequest, DiagnosticSummary, and PatientMEdicalProcedure objects in Salesforce.
OBX - Observation Segment: The Observation Segment (OBX) HL7 segment maps to the CareObservation object in Salesforce.
ORC - Common Order Segment: The Common Order Segment (ORC) HL7 segment maps primarily to the ClinicalServiceRequest and MedicationRequest objects in Salesforce.
PID - Patient Identification: The Patient Identification (PID) HL7 segment maps to the ContactPointPhone object in Salesforce.
PV1 - Patient Visit: The Patient Visit (PV1) HL7 segment maps to the Encounter object, among other objects in Salesforce.
RXA - Pharmacy Administration Segment: The Pharmacy Administration Segment (RXA) HL7 segment maps primarily to the PatientImmunization and Medication objects in Salesforce.
RXC - Pharmacy Component Order Segment: The Pharmacy Component Order Segment (RXC) HL7 segment maps to the Medication and MedicationRequestobjects in Salesforce.
RXE - Pharmacy Encoded Order Segment: The Pharmacy Encoded Order Segment (RXE) HL7 segment maps primarily to the Medication object in Salesforce.
RXR - Pharmacy Route Segment: The Pharmacy Route Segment (RXR) HL7 segment maps primarily to the PatientImmunization and PatientMedicationDosage objects in Salesforce.
XPN - Extended Person Name: The Extended Person Name (XPN) HL7 segment maps to the PersonName object in Salesforce.
Store HL7 v2.3 Messages in Salesforce Standard Objects: Like the Fast Health Interoperability Resources (FHIR) standard defined by Health Level Seven (HL7), HL7 v2.3 is also a database framework defined by HL7 to facilitate interoperability between electronic healthcare systems. Because the Clinical Data Model was built to align with FHIR v4.0, it is also compatible with its predecessor HL7 v2.3. However, because of the way the Salesforce platform works, the Salesforce implementation varies from the HL7 recommendations in certain cases such as the data types that are used.
CareLimitType: Defines the characteristics of limits on benefit provision.
CareProviderSearchConfig: Represents the information about the fields that appear in care provider search results. This type extends the Metadata metadata type and inherits its fullName field.
CareRequestConfiguration: Represents the details for a record type such as service request, drug request, or admission request. One or more record types can be associated with a care request.
CareSystemFieldMapping: Represents a mapping from source system fields to Salesforce objects and fields. This type extends the Metadata metadata type and inherits its fullName field.
DocumentExtractionDef: Represents the metadata definition used to manage and execute document data extraction processes.
IdentityVerificationProcDtl: Represents the search functionality configuration and the minimum number of optional verifiers for identity verification. This type extends the Metadata metadata type and inherits its fullName field.
IdentityVerificationProcFld: Represents the search and verification fields used in identity verification. This type extends the Metadata metadata type and inherits its fullName field.
IndustriesSettings: Represents settings for Health Cloud.This type extends the Metadata metadata type and inherits its fullName field.
ScoreCategory: Represents the category and subcategories that form a unified health profile in the Unified Health Scoring feature.
TimelineObjectDefinition: Represents the container that stores the details of a timeline configuration. You can use this resource with Salesforce objects to see their records' related events in a linear time-sorted view.
Translations: Metadata type that enables work with translations for various supported languages. The ability to translate component labels is part of the Translation Workbench.
UIObjectRelationConfig: Represents the admin-created configuration of the object relation UI component.
VirtualVisitConfig: Represents an external video provider configuration, which relays events from Salesforce to the provider.
Agentforce Health Developer Guide: This guide provides information on the custom objects used by Agentforce Health and their fields. Some fields may not be listed for some objects.
StandardObjectNameChangeEvent: A ChangeEvent object is available for each object that supports Change Data Capture. You can subscribe to a stream of change events using Change Data Capture to receive data tied to record changes in Salesforce. Changes include record creation, updates to an existing record, deletion of a record, and undeletion of a record. A change event isn’t a Salesforce object—it doesn’t support CRUD operations or queries. It’s included in the object reference so you can discover which Salesforce objects support change events.
StandardObjectNameFeed: StandardObjectNameFeed is the model for all feed objects associated with standard objects. These objects represent the posts and feed-tracked changes of a standard object.
StandardObjectNameHistory: StandardObjectNameHistory is the model for all history objects associated with standard objects. These objects represent the history of changes to the values in the fields of a standard object.
Health Cloud Associated Objects: This section provides a list of objects associated to Health Cloud standard objects with their standard fields.
StandardObjectNameOwnerSharingRule: StandardObjectNameOwnerSharingRule is the model for all owner sharing rule objects associated with standard objects. These objects represent a rule for sharing a standard object with users other than the owner.
StandardObjectNameShare: StandardObjectNameShare is the model for all share objects associated with standard objects. These objects represent a sharing entry on the standard object.
Health Cloud Data Model: Salesforce Health Cloud provides a rich set of objects to store and access specialized health information.
AccountServicePreference: Represents the preferences an account has for the services they receive. In Home Health, this object represents the preferences that a patient has for the health workers assigned to their visits. This object is available in API version 58.0 and later.
Accreditation: Represents the professional accreditations of a facility. For example, a joint commission accredits a facility as a general acute care hospital.
ActionPlanTemplate: Represents the instance of an action plan template. In Life Sciences cloud, this object is available in API version 65.0 and later.This object is available in API version 44.0 and later.
ActionPlanTemplateAssignment: Represents the association of an action plan template with its related care plan template, goal, or problem definition. When instantiated, the action plan generates the corresponding intervention tasks and links them to the appropriate record, such as a condition, goal, or care plan.
ActionPlanTemplateItem: Represents the instance of an item on an action plan template version. This object is available in API version 44.0 and later.
ActionVisibility: This object serves as a junction to connect Account or Contact to other objects so that information in those other object can be used to define visibility rules for actions in the Dynamic Actions for Unified Health Scoring component. This object is available in API version 55.0 and later.
Address: Represents a mailing, billing, or home address.
AdvTherapyFieldOptOverride: Represents a list of fields with changed optionality, based on certain parameters. This object is available in API version 59.0 and later.
AgeBandHlthRskAdjFctr: Stores the risk adjustment factor for patients and members based on the age band that they’re a part of and the status of their benefits eligibility. This object is available in API version 61.0 and later.
ApplicationCase: This junction object stores a relationship between Case and IndividualApplication. This object is available in API version 52.0 and later with the Provider Network Management permission set license.
ApplnFormAppealStsChgEvnt: Notifies subscribers of changes to the status of an appeal filed against a Financial Assistance Program. This object is available in API version 63.0 and later.
AssessmentEnvelope: Represents information about an envelope that contains the assessments related to a user. For example, you can create an envelope that contains assessments for a patient or a caregiver related to depression or anxiety. This object is available in API version 58.0 and later.
AssessmentEnvelopeItem: Represents information about an item in an envelope that contains the assessments related to a user. For example, you can create an item that contains an assessment for depression or anxiety. This object is available in API version 58.0 and later.
AssessmentTask: Perform activities such as patient registration or order authorization to capture information.
AssetType: Represents a type of asset, such as a type of item, physical space, or service offering. This object is available in API version 62.0 and later.
Award: Represents a person's or organization's professional awards.
BoardCertification: Represents the practitioner's board certifications such as being board-certified in cardiology and cardiovascular disease.
BundledCareFeeAgreement: Specifies the payment terms for contracts of Bundled Care Fee Agreement. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
BusinessLicense: Represents the licenses of a party role like healthcare provider or producer.
CapitationCareFeeAgreement: Specifies the payment terms for contracts of Capitation Care Fee Agreement type. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
CareBarrier: Represents the circumstances or obstacles affecting a patient or member. Available in API version 45.0 and later.
CareBarrierDeterminant: Represents the relationship of a barrier to a determinant for a patient or member. Available in API version 45.0 and later.
CareBarrierType: Represents the standard, defined list of barriers maintained by an organization. Available in API version 45.0 and later.
CareBenefitVerifyRequest: Request for verification of benefits. This object is available in API version 53.0 and later.
CareBnftVrfyRqstStsChgEvent: Notifies subscribers of changes to the status of a care benefit verify request. This object is available in API version 65.0 and later.
CareDeterminant: Represents the determinants of health for a patient such as availability of safe housing, adequate employment, or local food markets. Available in API version 45.0 and later.
CareDeterminantType: Represents the standard, defined list of determinants of health maintained by an organization, including the domain and type. Available in API version 45.0 and later.
CareDiagnosis: Represents the details of a diagnosis including code type, name, and description. One or more care diagnoses can be associated with a care request.
CareFacilityBed: Represents information related to different bed types at a facility with associated care programs and products. This object is available in API version 58.0 and later.
CareFeeScheduleItem: Stores procedure level fees for a fee schedule definition. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
CareGap: Represents gaps in patient care through a specified period. This object is available in API version 59.0 and later.
CareGapCriteriaResult: Represents the result of an evaluated clinical measure criteria. This object is available in API version 59.0 and later.
CareInterventionType: Represents the standard, defined list of interventions maintained by an organization. Available in API version 45.0 and later.
CareMetricTarget: Represents the expected care metrics at an org level and patient level. This object is available in API version 49.0 and later.
CareObservation: Represents the observed values for care metrics originating from external systems that contain biometric data. This object is available in API version 49.0 and later.
CareObservationDetail: Represents the details of a care observation. It provides detailed findings or contextual information for a patient's health assessment, such as a particular lab result or a clinician's specific insight. The detailed observations enable providers to capture comprehensive and precise health data. This object is available in API version 68.0 and later.
CarePgmEnrolleeWkOrdStep: Represents information about the step in a work order that's executed for the care program enrollee. This object is available in API version 58.0 and later.
CarePgmEnrolleeWorkOrder: Represents information about the work order that's executed for the care program enrollee. This object is available in API version 58.0 and later.
CarePgmProvHealthcareProvider: Represents a junction object identifying the primary healthcare professional associated with a care program provider and to look up all healthcare professionals for care program providers. This object is available in API version 49.0 and later.
CarePlan: Stores information about a care plan associated with a medication therapy review. Care plans are used to assign tasks to patients as part of medication therapy reviews. This object is available in API version 56.0 and later.
CarePlanActivity: Represents a planned action that’s part of a care plan. For example, knowledge campaigns, physiotherapy appointments, medication regimens, etc. This object is a child object of CarePlan. This object is available in API version 56.0 and later.
CarePlanTemplate: Stores information about care plan template that’s used to define to-do lists for patients during medication therapy reviews. This object is available in API version 56.0 and later.
CarePreauth: Represents the details of preauthorizations for care under a member’s plan.
CarePreauthItem: Represents the details of items included in a preauthorization for care under a member’s plan.
CareProcessingError: Stores information on processing errors sent from payer to provider on a member’s authorization request. This object is available in API version 58.0 and later.
CareProgram: Represents a set of activities, such as a patient therapy, financial assistance, education, wellness, or fitness plan, offered to participants by an employer or insurer.
CareProgramAssistance: Represents a junction between Care Program and Program objects. This object is available in API version 61.0 and later.
CareProgramCampaign: Represents a relationship between the Care Program object and the Campaign object. This junction object enables admins to associate one or more campaigns to a program.
CareProgramEligibilityRule: Represents a rule defining the criteria for patient care program enrollment eligibility. This entity creates an association between Care Program and an Enrollment Eligibility Criteria.
CareProgramEnrolleeProduct: Represents the affiliation between a care program enrollee and a care program product, a care program provider, or both.
CareProgramEnrollmentCard: Represents a care program membership card that includes a membership number or enrollment code.
CareProgramGoal: Represents a business or clinical goal related to a care program.
CareProgramProduct: Represents the affiliation between a care program and a care program product, care program provider, or both.
CareProgramProvider: Represents a business account that is the service provider for a care program product.
CareProgramTeamMember: Represents a person who delivers services under a program, such as a program manager or care coordinator.
CareProviderAdverseAction: Captures adverse actions against the provider, such as malpractice lawsuits or revoked licences. This object is available in API version 47.0 and later.
CareProviderFacilitySpecialty: Represents all the specialties that the practitioner provides at a given location. For example, a physician who is board-certified in both spine and neuro may provide spine services at one location and neuro services at another.
CareProviderSearchableField: This object holds denormalized data from certain fields in the Provider Relationship Management data model. Provider search APIs query this object instead of multiple objects, which improves search performance. This object is available in API version 47.0 and later.
CareProviderSearchConfig: Represents fields that can appear in provider search results. Use this object to specify fields in arbitrary objects (source) that are made available in the search object (target). This object is available in API version 48.0 and later.
CareRegisteredDevice: Represents a device or device registration information for a patient or a care program enrollee. This object is available in API version 49.0 and later.
CareRequest: Represents the general details of a care-related request including member information, admission date, decision reason, and so on. A single request can contain multiple diagnoses, services, or drugs. Care requests include preauthorizations for drugs and services, admission notifications, concurrent review of admissions, appeals, complaints, and grievances.
CareRequestDrug: Represents the details of a requested drug including name, strength, frequency, and instructions for administration. One or more drug requests can be associated with a care request.
CareRequestExchangeInfo: Represents information about a care request exchange. This object is available in API version 63.0 and later.
CareRequestExtension: Represents extra details for a care request such as the subscriber details for the member's health plan, home healthcare status, and ambulance transportation details.
CareRequestItem: Represents the details of a care service request, including name, modifiers, and the effective date. One or more care service requests can be associated with a care request.
CareRequestReviewer: Represents the details of a care request reviewer including name, reviewer type, status of the care request at the end of the review, the reviewer’s notes, and date of review. A care request, care request item, care request drug, or care diagnosis can be associated with a care request reviewer. This object is available in API version 52.0 and later.
CareRequestSupportingCntnt: Represents details about supporting content of a care request such as assessments or content documents. This object is available in API version 63.0 and later.
CareService: Represents a healthcare treatment, service, or procedure offered by a provider, practitioner, or facility. This object is available in API version 59.0 and later.
CareServiceVisit: Associates a service request or a referral request (ClinicalServiceRequest) with a visit (ServiceAppointment) that’s part of that service or referral. This object is available in API version 58.0 and later.
CareServiceVisitPlan: Associates a service request with the series of visits that are planned as part of that visit. The series of visits is represented using MaintenancePlan. This object is available in API version 58.0 and later.
CareSpecialty: Represents a listing of provider specialty codes and descriptions. For example, 02 - Physician/General Surgery.
CareSpecialtyTaxonomy: The junction object between CareSpecialty and CareTaxonomy. This object is available in API version 52.0 and later.
CareSystemFieldMapping: Represents a mapping from source system fields to Salesforce target entities and attributes.
CareTask: Represents additional information about a healthcare-related task such as process status, beneficiary, and related tasks. This object is available in API version 61.0 and later.
CareTaskDetail: Represents extra details about a healthcare-related task such as the detail type, detail record, detail code, and detail value. This object is available in API version 61.0 and later.
CareTaxonomy: Represents a static list of taxonomy codes.
CaseRelatedFile: Represents the details of a file attached to a case, such as file properties, file processing details, and other additional relevant information. This object is available in API version 62.0 and later.
CategorizedCareFeeAgreement: Specifies the payment terms for contracts of Categorized Care Fee Agreement. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
ClinicalEncounter: Represents a healthcare related encounter of a patient with a care provider. This is a broad object that covers multiple phases of a patient’s healthcare service experience, all the way from pre-admission to stay to discharge, and everything in between. This object is available in API version 51.0 and later.
ClinicalMeasure: Represents a structured and computable definition of a health-related measure for identifying care gaps. This object is available in API version 59.0 and later.
ClinicalMeasureCriteria: Represents a computable criteria of a health-related measure. This object is available in API version 59.0 and later.
ClinicalMeasureCriteriaGrp: Represents a group of computable criteria for a health-related measure. This object is available in API version 59.0 and later.
CondIntrctnHlthRskAdjFctr: Stores the risk adjustment factor for patients and members based on the set of interacting conditions they are diagnosed with and the status of their benefits eligibility. This object is available in API version 61.0 and later.
ContractPaymentAgreement: Stores information about the contract payment agreement associated with a contract. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
CoverageBenefit: Represents the benefits provided to a covered member by a purchaser’s plan.
CoverageBenefitItem: Specific service covered by the insurance plan. This object is available in API version 53.0 and later.
CoverageBenefitItemLimit: Allows you to track details associated with a specific benefit as it relates to expenditures, limits, coverage levels, eligibility, and exclusion. This object is available in API version 53.0 and later.
CustodyChainEntry: Represents information about an entry or event in the chain of custody. This object is available in API version 59.0 and later.
CustodyItem: Represents information about an item in the custody chain. This object is available in API version 59.0 and later.
CustodyVerfcTypeOverride: Represents information about the verification of an entry in the chain of custody. This object is available in API version 59.0 and later.
DigitalVerfSetupDetail: Stores contextual details of a digital verification setup, such as the user who does the verification, and the messages that display at the time of verification. This object is available in API version 60.0 and later.
DigitalVerification: Stores information about the verification of a related record. This object is available in API version 60.0 and later.
DigitalVerificationSetup: Stores information about a digital verification setup, such as the number of signatures needed and the record action that's related to the verification. This object is available in API version 60.0 and later.
DocumentChecklistItem: Represents a checklist item for a documentation file upload. This object is available in API version 47.0 and later.
EngagementAttendee: Represents information about an attendee of an engagement. For example, when a customer initiates an engagement interaction by calling a service representative to inquire about an insurance claim, this object stores information about the customer and the service representative. This object is available in API version 55.0 and later
EngagementInteraction: Represents information about an interaction between a service representative or any other specialist in an organization and the organization’s customer. Engagement interactions can be initiated through communication channels and can cover one or more topics. For example, a customer can initiate an engagement interaction by calling a service representative to inquire about an insurance claim. This object is available in API version 55.0 and later.
EngagementTopic: Represents information about the topics discussed by a customer and other attendees during an engagement. For example, when a customer initiates an engagement interaction by calling a service representative to inquire about an insurance claim, the topic of the engagement is Claim. This object is available in API version 55.0 and later.
EnrollmentEligibilityCriteria: Represents criteria that define patient enrollment eligibility for one or more care programs.
FeeScheduleDefinition: Stores fee schedule information for contracts of Standard Care Fee Agreement types. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
GoalAssignment: Represents the goals that are part of a care plan.
GoalDefinition: Represents a goal or a business objective that’s used as a reference. When instantiated, GoalDefinition records create GoalAssignment records that serve as goals in care plans.
Pricebook2: Represents a price book that contains the list of products that your org sells.
Pricebookentry: Represents a product entry (an association between a price book and product) in a price book.
Product2: Represents a product that your org sells.
ProductFulfillmentLocation: Associates a business account and a product inventory with the responsible field rep. This object is available in API version 49.0 and later.
ProductItem: Represents the stock of a particular product at a particular location in field service, such as all bolts stored in your main warehouse.
ProductRequired: Represents a product that is needed to complete a visit.
ProductTransfer: Represents the transfer of inventory between locations in field service.
HealthCareDiagnosis: Represents information related to industry-standard healthcare diagnosis codes. Before the Spring ’21 release, the Healthcare Procedure and Healthcare Diagnosis objects stored codes specifically related to procedures and diagnoses. These codes were used for prior-authorization requests and approval processes. Since the Spring’21 release, Health Cloud uses the Code Set and Code Set Bundle objects for this purpose instead.
HealthcareFacilityNetwork: Represents a junction object identifying the insurance network that a location or business entity is a part of. Network participation records are also stored in this object.
HealthcarePayerNetwork: Represents an insurance network group. For example, an insurance company’s exclusive provider organization (EPO) plans.
HealthCareProcedure: Represents information related to industry-standard healthcare procedure codes. Before the Spring ’21 release, the Healthcare Procedure and Healthcare Diagnosis objects stored codes specifically related to procedures and diagnoses. These codes were used for prior-authorization requests and approval processes. Since the Spring’21 release, Health Cloud uses the Code Set and Code Set Bundle objects for this purpose instead.
HealthcareProvider: Represents business-level details about the healthcare organization or the practitioner.
HealthcareProviderNpi: Represents identifiers from the National Provider Identifier that are assigned to every facility and licensed practitioner in the United States. Also includes NPI assigned date, primary mailing address on file, and so on.
HealthcareProviderService: Represents a junction object between a HealthcareService and a HealthcareProvider or HealthcareFacility or HealthcarePractitionerFacility. This object is available in API version 59.0 and later.
HealthcareProviderSpecialty: Represents specialties for a practitioner or a service provider organization. A provider can have multiple specialties such as anesthesiology and cardiovascular.
HealthcareProviderTaxonomy: Represents taxonomy or subspecialty codes for a practitioner or facility. A provider or facility can have multiple taxonomies.
HealthcareServiceDetail: Represents a junction object between a CareService and a CodeSetBundle. For example, this object links a healthcare service such as physical therapy to a set of related codes. This object is available in API version 59.0 and later.
HealthPlanFacilityNetwork: Represents the association between an insurance product or plan and a designated healthcare facility network. This entity is fundamental in healthcare management, allowing insurers and providers to accurately determine which facilities are in-network for a given patient's plan, facilitating eligibility checks and service coordination. This object is available in API version 68.0 and later.
HealthPlanFormularyItem: Represents which drugs, medical devices, or services are covered under specific insurance products within defined time periods. Each record establishes a relationship between Product2 insurance plans and FormularyItem records. This object is available in API version 68.0 and later.
HealthScore: Represents a subject’s score for a specific score category. This object is available in API version 55.0 and later.
HealthScoreActionLog: Represents the log of actions triggered from the Dynamic Actions for Unified Health Scoring component in the Unified Health Scoring feature. This object is available in API version 55.0 and later.
HierCondHlthCodeMapping: Represents how Hierarchical Condition Category (HCC) codes map to condition codes for a specific year. This object is available in API version 61.0 and later.
HierCondHlthRskAdjFctr: Stores the risk adjustment factor for patients and members based on the set of Hierarchical Condition Category (HCC) codes that apply to them and the status of their benefits eligibility. This object is available in API version 61.0 and later.
HlthCareProvTreatedCondition: Represents a junction object between a healthcare provider, facility, or practitioner and a problem definition that's related to a health condition, such as disease or illness. For example, this object links a doctor to the treatment of diabetes, or a facility to the treatment of spinal injuries. This object is available in API version 59.0 and later.
AsmtQstnRespRecommendation: Maps an assessment question’s response to the recommendation it has to provide for a care plan. Recommendations can be problems, goals, interventions, or other assessments. This object is available in API version 57.0 and later.
CareEpisode: Records details of the interaction between a patient and a healthcare provider for the period during which the patient receives healthcare services from the provide. This object is based on the EpisodeOfCare FHIR resource. This object is available in API version 57.0 and later.
CareEpisodeDetail: Represents additional information associated with a CareEpisode record. This information may be the referral requests that an episode of care started from or the diagnoses that the episode of care is meant to address. This object is available in API version 57.0 and later.
CarePlan: Represents a care plan that is created to help improve a patient or member’s health. This object is based on the CarePlan FHIR resource. This object is available in API version 56.0 and later.
CarePlanActivity: Represents an activity that’s part of a care plan. This object is a child of CarePlan. This object is available in API version 56.0 and later.
CarePlanActivityDetail: Represents additional information associated with a CarePlanActivity record. This information may be outcomes of the activity, the performers who contributed to it, or the reasons why the activity was necessary.. This object is a child of CarePlanActivity. This object is available in API version 57.0 and later.
CarePlanDetail: Represents additional information associated with a care plan record. These details may be things addressed by the care plan, contributors in the care plan, supporting information, and so on. This object is available in API version 57.0 and later.
CarePlanTemplate: Represents a template use to instantiate a care plan. This object is available in API version 56.0 and later.
CarePlanTemplateGoal: Represents goals in Care Plan Templates that don’t have problems as their parents. These goals are added directly under the care plan in the template . This object determines the position of goals in the hierarchy of care plan templates. The specific details of goals are referenced from GoalDefinitions records in the PGI library. This object is available in API version 57.0 and later.
CarePlanTemplateProblem: Represents problems in Care Plan Templates. These problems may or may not have goals as their direct children. This object determines the position of problems in the hierarchy of care plan templates. The specific details of problems are referenced from ProblemDefinition records in the PGI library. This object is available in API version 57.0 and later.
GoalAssignmentDetail: Represents additional information associated with a GoalAssignment record. This information may be the outcome of a goal or something addressed by it. This object is available in API version 57.0 and later.
ProblemDefinition: The definition of a care plan problem in the reusable PGI library that’s a part of Integrated Care Management. When instantiated, ProblemDefinition records create HealthCondition records that serve as problems in care plans. This object is available in API version 57.0 and later.
ProblemGoalDefinition: A junction object that associated a goal definition to its parent problem definition. These junction records assist in establishing the problem-goal hierarchy in care plans instantiated from the PGI library. A problem definition can have multiple goal definitions as its children, and a goal definition can have multiple problem definitions as its parents. This object is available in API version 57.0 and later.
IndicatorAssignment: Represents the assignment of an indicator definition that's used to measure the performance of an outcome or a related activity. This object is available in API version 59.0 and later.
IndicatorDefinition: Represents information about the indicator assignment and the process of measuring and calculating the indicator results. This object is available in API version 59.0 and later.
IndicatorPerformancePeriod: Represents information about a specified time period including the frequency at which indicator results should be calculated and the baseline value of the indicator. This object is available in API version 59.0 and later.
IndicatorResult: Represents the result of an indicator assignment for the specified time period that can be used to track the performance of the indicator. This object is available in API version 59.0 and later.
IndividualApplication: Represents an application form submitted by an individual. Available with the Provider Network Management permission set license.
InsurancePolicy: Represents a type of insurance policy. Available with the Provider Network Management permission set license.
InteropTopic: Represents the interoperability topic for which notifications are sent to subscribers. This object is available in API version 64.0 and later.
InteropTopicDetail: Represents the details of an interoperability topic. This object is available in API version 64.0 and later.
InteropTopicFilter: Represents the properties by which an interoperability topic's notification can be filtered. This object is available in API version 64.0 and later.
InteropTopicNtfcnResource: Represents the notification resource for an interoperability topic. This object is available in API version 64.0 and later.
InteropTopicSubcrFilter: Represents the subscriber's criteria for filtering the interoperability topic subscription event. This object is available in API version 64.0 and later.
InteropTopicSubcrParameter: Represents the parameters added to an interoperability topic subscription. This object is available in API version 64.0 and later.
InteropTopicSubscription: Represents a subscription to an interoperability topic. This object is available in API version 64.0 and later.
InteropTopicSubscriptionDtl: Represents the details of an interoperability topic subscription. This object is available in API version 64.0 and later.
InteropTopicTriggerCriteria: Represents the criteria that trigger a notification for an interoperability topic. This object is available in API version 64.0 and later.
MedicationReconciliation: Stores information about a medication reconciliation conducted for a patient This object is available in API version 54.0 and later.
MedicationTherapyReview: Stores information about a medication therapy review conducted for a patient. This object is available in API version 56.0 and later.
MedicationTherapyStmtReview: Represents a junction object between the Medication Therapy Review and Medication Statement objects. This object is available in API version 56.0 and later.
MedReconRecommendation: Stores information about a medication recommendation and associates a recommendation to a medication reconciliation. This object is available in API version 54.0 and later.
MedReconStmtRecommendation: Associates a medication recommendation to a medication statement and medication reconciliation. This object is available in API version 54.0 and later.
MedTherapyStmtReviewIssue: Represents a junction object between the Medication Therapy Statement Review and Clinical Detected Issue objects. This object is available in API version 56.0 and later.
MemberPlan: Represents details about the insurance coverage for a member or subscriber.
MemberPlan: Represents details about the insurance coverage for a member or subscriber.
MemberPlanCarePlan: Represents a junction between member plans and care plans. It defines the problems, goals, and interventions in a care plan based on the patient's health plan coverage. This object is available in API version 66.0 and later.
MemberPlanMedicationStmt: Represents a junction between member plans and medication statements. It associates the medications that a patient is currently taking or has taken in the past with their health plan coverage. This object is available in API version 66.0 and later.
OcrDocumentScanResult: Represents the contents of a document after optical character recognition (OCR) processing. This object is available in API version 50.0 and later.
OpportunityProductCategory: Represents the junction between an Opportunity and the specific Medicare product categories the beneficiary has authorized for discussion. Each record represents one Medicare Part (e.g., Part A, Part C, Part D) included in the scope. This object is available in API version 68.0 and later.
Outcome: Represents information about the expected change in participants that is driven by the organization's activity. This object is available in API version 59.0 and later.
OutcomeActivity: Represents a junction between Outcome and the object that's related to the activity undertaken by an organization to achieve that outcome. This object is available in API version 59.0 and later.
PartyIndicatorResult: Represents information about a party for which the indicator result is calculated. This object is available in API version 62.0 and later.
PartyProfile: Represents additional details related to a patient. This object is available in Health Cloud in API version 61.0 and later.
PercentileBsdCareFeeAgreement: Specifies the payment terms for contracts of Percentile Based Care Fee Agreement. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
PersonEducation: Represents information about professional education for a person in a provider role.
PersonEmployment: Represents information about a person’s employment.
PgmBasedHlthRskAdjFctr: Stores the risk adjustment factor for patients and members based on their eligibility for certain benefits programs. For instance, Medicaid in the US. This object is available in API version 61.0 and later.
PlanBenefit: Represents the standard benefits available under a plan that the purchaser offers to their members.
PlanBenefitItem: Represents the details of a benefit available under a purchaser’s plan that is offered to their members.
PreventiveCareAgreement: Specifies the payment terms for contracts of Preventive Care Fee Agreement. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
ProductAvailabilityProjection: Represents the projected product quantity available at an inventory location at various points in time. Records for this object are automatically created by Intelligent Sales. This object is available in API version 55.0 and later.
ProductRequest: Represents a device request made as part of a care program.
ProductRequestLineItem: A junction object between ProductRequest and ProductTransfer This object is available in API version 50.0 and later.
ProgramEnrlEligibilityCrit: Represents a junction between Program and Enrollment Eligibility Criteria objects. This object is available in API version 61.0 and later.
ProgramRecommendationRule: Represents the eligibility criteria and recommendation for a program. This object is available in API version 61.0 and later.
ProviderNetworkContract: Represents a provider and a network bound together by a contract. This object is available in API version 53.0 and later with the Provider Network Management permission set license.
ProviderNetworkTier: Represents unique tiers for each provider network. This object is available in API version 53.0 and later with the Provider Network Management permission set license.
ProviderSearchSyncLog: Represents a log with information about the provider search data sync status of a healthcare provider record. This object is available in API version 49.0 and later.
PurchaserPlan: Represents the payer plan that a purchaser makes available to its members and members’ dependents.
PurchaserPlan: Represents the payer plan that a purchaser makes available to its members and members’ dependents.
PurchaserPlanAssn: Represents a junction object that associates the purchaser to the plans they offer to members.
PurchaserPlanCareProgram: Represents a junction between puchaser plans and care programs. It defines the care programs that are available under a purchaser plan such as employer-sponsored programs for managing chronic conditions. This object is available in API version 66.0 and later.
ReceivedDocument: Contains a request for an operation to be performed on a document, such as rotating, splitting, or text extraction. This object is available in API version 50.0 and later.
ReceivedDocumentType: Represents a junction object between Received Document and Document Type. This object is available in API version 58.0 and later.
RecordAction: Represents a relationship between a record and an action, such as a flow. Create a RecordAction for every action that you want to associate with a particular record. Available in API version 42.0 and later.
ScheduleBrdcstApptResource: Represents a junction between a Schedule Broadcast Appointment and a Service Resource. This object represents the resources to whom a schedule broadcast is sent. This object is available in API version 60.0 and later.
ScheduleBroadcast: Represents a broadcast of appointments that's sent to resources of specific service territories. This object is available in API version 60.0 and later.
ScheduleBroadcastAppointment: Represents appointments that schedulers broadcast to resources using a schedule broadcast. This object is available in API version 60.0 and later.
ScheduleBroadcastTerritory: Represent service territories to which a schedule broadcast is sent. This object is available in API version 60.0 and later.
ServiceAppointmentAsset: Represents a junction between Service Appointment and Asset. This junction object enables admins to associate a patient appointment to an asset such as a piece of medical equipment. This object is available in API version 62.0 and later.
ServiceAppointmentGroup: Stores information about a group of related service appointments. This object is available in API version 56.0 and later.
ServiceInfoRequestDetail: Represents additional details about a service information request, such as the detail type and detail code. This object is available in API version 63.0 and later.
ServiceInfoRequestOperation: Represents the system operation performed for a service information request such as a session launch or a questionnaire package operation. This object is available in API version 63.0 and later.
ServiceInfoResponseAction: Represents actions to be performed as suggested by a service information response. This object is available in API version 63.0 and later.
ServiceInfoResponseCoverage: Represents coverage details about a service information response. For example, if additional information or documentation is required for the coverage to be provided. This object is available in API version 63.0 and later.
ServiceInfoRespOvrideOpt: Represents the possible reasons for overriding a service information response. This object is available in API version 63.0 and later.
ServiceInfoRespResourceUrl: Represents the URLs of resources relevant to a service information response. This object is available in API version 63.0 and later.
ServiceInfoRespSuggestion: Represents suggestions in a service information response. For example, suggesting a change in medication dosage. This object is available in API version 63.0 and later.
ServiceInformationRequest: Represents information about a service information request, such as the date and time when the request was submitted and the type of service requested. This object is available in API version 63.0 and later.
ServiceInformationResponse: Represents a response to a service information request. This object is available in API version 63.0 and later.
ServiceInfoRqstOpOutcome: Represents the outcome of a service information request operation. This object is available in API version 63.0 and later.
ServiceTerritoryRelationship: Represents the relationship between service territories based on work types performed. This object is available in API version 56.0 and later.
SharedSavingPaymentAgreement: Specifies the payment terms for contracts of Shared Saving Payment Agreement type. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
SkillType: Represents the broader type or category that a skill belongs to. This object is available in API version 58.0 and later.
StandardCareFeeAgreement: Specifies the payment terms for contracts of Standard Care Fee Agreement type. This object is available in API version 54.0 and later with the Provider Network Management permission set license.
SvcInfoRelatedQuestionnaire: Represents the questionnaire associated with a service information request or service information response coverage. This object is available in API version 63.0 and later.
SvcInfoRespCoverageDetail: Represents additional coverage details about a service information response. This object is available in API version 63.0 and later.
Team: Represents the team of members associated with an organization. This object is available in API version 58.0 and later.
TeamMember: Represents the member associated with a team. This object is available in API version 58.0 and later.
TimePeriod: Represents the time period that's used to calculate the indicator performance and result. This object is available in API version 59.0 and later.
TrackedCommunication: Stores information request or communication details sent from payer to provider on a member’s authorization request. This object is available in API version 57.0 and later.
TrackedCommunicationDetail: Stores additional information associated with TrackedCommunication records. This object is available in API version 57.0 and later.
UnitOfMeasure: Represents the unit of measures for care metrics and care observations. This object is available in API version 49.0 and later.
Visit: Track information related to a field rep’s visit to a health care provider.
VisitedParty: Represents the contact person at the account that’s being visited. This object is available in API version 49.0 and later.
VisitedPartyFeed: This object represents the posts and feed-tracked changes of the VisitedParty object. This object is available in API version 49.0 and later.
Visitor: Represents the sales reps performing visits.
VisitorFeed: This object represents the posts and feed-tracked changes of the Visitor object. This object is available in API version 49.0 and later.
WorkProcedure: Represents information about a procedure or process that's part of a program, such as a care program in Health Cloud or Life Sciences Cloud.
WorkProcedureStep: Represents information about the work type that's a part of a work procedure.
WorkTypeAssetType: Represents a junction between Work Type and Asset Type. This junction object enables admins to associate a visit type such as PRP Hair Restoration to an asset type such as Room. This object is available in API version 62.0 and later.
WorkTypeCareSpecialty: Represents a relationship between a care specialty and a visit type (Work Type). This object is available in API version 52.0 and later.
WorkTypeCodeSetBundle: Represents a relationship between visit type (Work Type) and code set bundles that represent the service and appointment details for the visit type. This object is available in API version 52.0 and later.
WorkTypeExtension: Represents additional information about a work type.
WorkTypeStep: Represents each step within a work type.
WorkTypeStepLdTimeOvride: Represents the lead time that's used to override the default lead time required for the work procedure, work type, or work type step that's performed at a service territory in a country. This object is available in API version 59.0 and later.
WorkTypeSvcTerrSchdPrio: Represents the priority of the combination of the service territory, work type, and work procedure while fetching appointment slots. This object is available in API version 59.0 and later.
ApptBookingConfig: Represents a collection of fields to set up appointment scheduling. This object is available in API version 52.0 and later.
ApptBookingUrlConfig: Represents a collection of fields used to set up the URL paths for appointment scheduling endpoints. This object is available in API version 52.0 and later.
AssessmentConfiguration: Represents a configuration for Assessment component. An AssessmentConfiguration entry indicates configuration for user flows such as sending out emails or reminder actions on assessments initiated by the patient. This object is available in API version 58.0 and later.
CareBenefitVerifySettings: Configuration settings for benefit verification requests. This object is available in API version 53.0 and later.
CareLimitType: Defines the characteristics of limits on benefit provision. This object is available in API version 53.0 and later.
CareProviderAfflRoleConfig: Represents information about the affiliations of the healthcare provider. For example, this object represents an affiliation between a healthcare provider and a hospital. This object is available in API version 59.0 and later.
CareProviderSearchConfig: Represents fields that can appear in provider search results. Use this object to specify fields in arbitrary objects (source) that are made available in the search object (target). This object is available in API version 48.0 and later.
CareRequestConfiguration: Represents the details for a record type such as service request, drug request, or admission request. One or more record types can be associated with a care request.
CareSystemFieldMapping: Represents a mapping from fields in external source systems to Salesforce target entities and attributes
DocumentExtrctDefProcFldr: Represents a Document Extraction Definition Processing Folder record in your Salesforce org. This object is available in API version 67.0 and later.
IdentityVerificationProcDef: Represents the definition of the identity verification process. This object is available in API version 54.0 and later.
IdentityVerificationProcDtl: Used to configure the search function as well as the minimum number of verifiers for the identity verification process. Available in API version 54.0 and later.
IdentityVerificationProcFld: Used to configure the questions or criteria for verifying the identity of a caller. This object is available in API version 54.0 and later.
ScoreCategory: Represents the categories that are scored in a unified health profile. This object is available in API version 55.0 and later.
ScoreCategoryCalcInsight: Represents how a score category in Unified Health Scoring is mapped to a calculated insight in Salesforce CDP. Use this object only if you use CDP to calculate scores for Unified Health Scoring. This object is available in API version 55.0 and later.
ScoreRangeClassification: Represents the different score ranges of a score category and how scores in those ranges are classified or interpreted. This object is available in API version 55.0 and later.
TimelineObjectDefinition: Stores timeline configurations. This object is available in API version 55.0 and later.
Unified Health Scoring: The Unified Health Scoring data model provides three objects, three tooling APIs, and a metadata type with two subtypes. Use these objects to implement the feature in your Health Cloud org.
