Generate Research Study Blocks Action: Generate research study randomization block records to link each block with a specific research study comparison group by using the randomization process.
Process Criteria Matching Response: Parses a GPT-generated JSON response to evaluate each inclusion and exclusion criterion for a given Research Study Candidate, determining whether each criterion is matched or not. This action stores the GPT response in the Care Program Enrollment Evaluation Result entity and computes the number of matched inclusion criteria and exclusion criteria, returning these counts as output.
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.
ConnectApi Namespace: The ConnectApi namespace (also called Connect in Apex) provides classes for accessing the same data available in Connect REST API. Use Connect in Apex to create custom experiences in Salesforce.
embeddedai Namespace: The embeddedai namespace provides classes and methods to manage and represent records and data in Apex to support embedded AI features.
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.
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.
User Credentials Input: Input representation of the user credentials to perform digital verification.
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.
Waterfall Download Input: The request payload containing line items for which to fetch pricing waterfall data.
Work Type Lead Time Input: Input representation of the request to get a list of work types and their associated lead times.
Advanced Provider Search: Facilitate three distinct types of account searches: Healthcare Provider (HCP), Healthcare Organization (HCO), and license-based searches. For HCP and HCO searches, the API processes fields from the account, healthcare provider, and contact point address entities.The license-based searches use fields from the business license entity.
Book Slot Chain (POST): Create service appointments for a care program enrollee in advanced therapy management based on the provided appointment slots.
Email Template (POST): Create an email template. The Health Cloud Starter and Life Sciences Commercial Admin Permission Sets are required for accessing this API. To know more, see Email Template and Intelligent Content.
Email Template (PATCH): Update an email template.The Health Cloud Starter and Life Sciences Commercial Admin Permission Sets are required for accessing this API. To know more, see Email Template and Intelligent Content.
Bulk Presentation (POST): Create a presentation and its associated content in bulk. You can upload presentation files as PDF or ZIP and associated metadata. The JSON payload includes metadata for both the presentation and each page within the presentation. This metadata can include details such as the presentation name, activation date, and page-level information. The Health Cloud Starter and Life Sciences Commercial Admin Permission Sets are required for accessing this API. To know more, see Email Template and Intelligent Content.
Bulk Presentation (PATCH): Update a presentation and its associated content in bulk. You can upload presentation files as PDF or ZIP and associating metadata. The Health Cloud Starter and Life Sciences Commercial Admin Permission Sets are required for accessing this API. To know more, see Email Template and Intelligent Content.
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.
Account Manual Alignment: Manually align an account to a territory in the Life Sciences package to create a Provider Account Territory Info record.
Digital Verification (POST): Perform verification for the digital verification records within advanced therapy management.
Download Provider (POST): Download Health Care provider data from an external system to a Salesforce org after a search is performed.
Provider Search: Search for Healthcare providers and accounts based on a free-text input, either from internal Salesforce data or an external system. This API returns account information, including healthcare providers and matching contact point addresses.
Merge Customer Account (POST): Merges a list of customer accounts. If any one account merge in the request fails, the entire operation is cancelled.
Merge Customer Account with Status (POST): Merges a list of customer accounts and provides a status for each request. This API processes all valid requests and does not fail the entire operation if one request is invalid.
Presentation Page Product (POST, PATCH): Create or update (delete) product and guidance associations for a presentation page. The Health Cloud Starter and Life Sciences Commercial Admin Permission Sets are required for accessing this API. To know more, see Email Template and Intelligent Content.
Sample Limits Validation (POST): Validate the samples requested during a visit against the sample limits for that account, product, and sample limit template.
Split Documents: Split a document and attach one or more pages from the transformed document to Salesforce records.
Benefits Verification (POST): The Verify Benefits API call is the main resource for checking which health benefits are available to a patient.
Waterfall Download (POST): Retrieves pricing waterfall data for multiple line items in a single request.
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.
Waterfall Download Output: The response containing the pricing waterfall data for the requested line items.
Work Type Lead Time Output: Output representation of a list of work types and their associated lead times.
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.
Timeline: Use Timeline to configure a chronological view of records from multiple objects.
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.
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.
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.
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.
Intelligent Sales: Help your sales team plan and execute sales visits and manage field inventory with Intelligent Sales.
Provider Relationship Management: Use the Provider Relationship Management data model along with standard Salesforce objects to manage your provider relationships.
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.
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.
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.
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.
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.
SerializedProduct: Records serial numbers for each individual product in an inventory. This object is available in API version 50.0 and later.
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.
Member: A member is a person who is the primary subscriber, a dependent, or anyone else who is covered under the insurance plan.
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.
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.
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.
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.
Fields on Account: Life Sciences Cloud fields extend the standard Account object to represent information about patients and providers.
Account Management: Account Management in the Life Sciences industry is crucial for organizations to effectively manage their relationships with healthcare providers (HCPs) and healthcare organizations (HCOs). The profile information serves as a foundation for various operational activities within the organization, providing a comprehensive view of HCPs and HCOs including their contact and social network details, specialties, affiliations, business licenses, ratings to segment and categorize HCPs and HCOs, as well as territory and product, and team-specific details. Life Sciences Cloud extends the Salesforce Core Account data model allowing organizations to create a holistic view of their customers providing up-to-date information in support of their business priorities.
Fields on ActionPlanTemplate: Life Sciences Cloud fields extend the standard ActionPlanTemplate object for integration with external systems.
Fields on ActionPlanTemplateItem: Life Sciences Cloud fields extend the standard ActionPlanTemplateItem object to support integration with external systems, commonly used for Key Account Management.
Activity Plans: Activity plans allow administrators to define goals for specific employees, including targeted accounts, plan cycle duration, types of activities, links to products, and weight of activity type. Employees and managers can review and edit these goals before final approval by the administrator. After plans are approved, employees execute activities against their goals, with the option to request changes during an active plan. Charts provide a visual representation of the employee's progress toward goals.
App Alerts: App Alerts keep users informed of critical updates, events, and insights that require timely action, helping to prevent missed opportunities. These alerts can deliver messages from admins and managers, as well as system-triggered updates and external recommendations, enabling users to act directly or dismiss suggestions with feedback. Serving as a direct, immediate communication channel, App Alerts integrate across components to streamline teamwork and enhance commercial engagement.
Fields on AssessmentIndicatorDefinition: Life Sciences Cloud fields extend the AssessmentIndicatorDefinition object to represent the default comparison rule for store checks.
Fields on Assortment: Life Sciences Cloud fields extend the Assortment object to represent the usage type for store checks.
Fields on AssortmentProduct: Life Sciences Cloud fields extend the AssortmentProduct object to represent whether a product is required in an assortment.
Life Sciences Cloud Business APIs: You can access Life Sciences Cloud Business APIs using REST endpoints. These REST APIs follow similar conventions as Connect REST APIs.
Clinical Engagement: These objects are available for Life Sciences Cloud for Clinical Engagement.
Agentforce Life Sciences Developer Guide: Agentforce Life Sciences is an end-to-end, purpose-built platform for the life sciences industry spanning clinical to medical to commercial domains. This guide includes the available developer resources for Agentforce Life Sciences.
Commercial Configuration: The Life Sciences Commercial Configuration objects store settings and configurations for many Customer Engagement features. In some cases, you can control a feature’s behavior by assigning configurations to specific profiles or users. Other configurations apply to all the users in an org.
Consent Management: Consent Management captures and honors healthcare provider consent and communication preferences across subscriptions and channels. Increase engagement and improve relationships by personalizing healthcare provider communications while ensuring privacy and compliance.
Fields on Contact: Life Sciences Cloud fields extend the standard Contact object to represent information about an individual.
Life Sciences Cloud Fields on Standard Objects: Life Sciences Cloud adds fields to some standard Salesforce objects to represent information about individuals. These fields are available only in orgs where Life Sciences Cloud is enabled.
Customer Engagement: These objects are available for Life Sciences Customer Engagement.
Customer Engagement Metadata Type: Metadata API enables you to access some types and feature settings for Customer Engagement for Life Sciences Cloud that you can customize in the user interface.
Data Change Requests: With Data Change Requests, organizations can implement configurable data validation processes that are tailored to their specific business needs. Validate data changes by objects and fields and configure data changes by profile and record type. Data Change Requests support controlled data synchronization of externally managed data domains.
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.
Enablement Coaching: Enablement Coaching helps plan coaching activities, evaluate field employees consistently, and document feedback and development plans. Managers, designated peers, and other authorized evaluators can coach employees without associating an event with a visit.
Event Management: Event Management enables life sciences organizations to plan and execute regulated field events, including speaker programs, representative-led meetings, and healthcare professional (HCP) sponsorship events, within a structured, compliant workflow. Sales representatives create and manage events from initial planning through close-out, by coordinating with participants, assigning subjects, tracking expenses, and selecting the event resources. Built on configurable workflow paths, Event Management enforces compliance through expert eligibility checks, subject assignment rules, monetary cap validations, and compliance statement acknowledgments. Administrators can tailor the workflow to match their organization's unique operational requirements.
Field Email: Field Email streamlines the email creation process, enhances efficiency, and ensures professional and compliant communication that aligns with brand guidelines. Predefined email templates ensure compliance with regulations like GDPR and CAN-SPAM while maintaining brand consistency. Customization options such as dynamic variables and content fragments, allow for personalized messages that resonate with recipients. Tracking key performance metrics like opens and clicks enables users to optimize their email campaigns effectively.
Field Insights: Field Insights data model helps you to automate the synthesis of complex provider information into clear, actionable presentations, ensuring users are informed before each visit. Users can listen to these audio briefings on the go as podcasts in the Life Sciences Cloud Mobile app's built-in audio player. With Field Inisghts, audio briefings are generated daily, users get insights customized to their role with on-the-go access. Field Insights also supports offline playback, playback continuity, and background playback to support
Flow for Life Sciences Cloud: The Flow for Life Sciences Cloud represents the metadata associated with a flow. Use Flow to create an application that takes users through a series of pages to query and update the records in the database. You can also run logic and provide branching capability based on user input to build dynamic applications.
General Events: General Events enable users to log and manage various non-customer related activities. With the Planner tool, users can easily create, view, and manage General Events in their schedules. Users can also add employees to a General Event for team collaborations.
Intelligent Content: Intelligent Content facilitates marketing strategies by enabling direct and interactive communications with healthcare professionals (HCPs). Sales and medical teams can deliver personalized presentations based on real-time feedback and analytics, enhancing the impact of their interactions. By continuously refining and optimizing marketing messages and strategies through data collection and analysis, Intelligent Content ensures that they are relevant and responsive to HCP needs and preferences. Intelligent Content capabilities include analytics and optimized user interfaces, offering a comprehensive solution for targeted content delivery in both planned and unplanned presentations.
Key Account Management: Key Account Management enables Key Account Managers (KAM) to strategically manage and engage with their most important customers. By using comprehensive account and territory plans, KAMs can set clear business objectives, track progress, and ensure alignment across global, affiliate, and territory levels. This structured approach enhances customer targeting accuracy and drives effective execution of strategic initiatives. With capabilities for creating multiple plans, defining specific objectives, and assigning tasks, the Key Account Management ensures alignment, collaboration, and effective execution of strategies to achieve desired business outcomes.
Lists and Filters: Quickly identify a target group of accounts by using Lists and Filters. Static lists are manually-curated lists of accounts that remain fixed. Users can add or remove accounts individually. Dynamic filters apply to a list of accounts that updates based on user pre-defined criteria, and show sortable relevant fields that users add. By using dynamic filters, users can quickly associate the group of accounts with tailored actions, saving time and efforts by removing the need for repetitive manual updates. Lists and Filters streamline workflows by enabling users to identify, interact with, and act on relevant accounts.
Medical Inquiries: Capture critical questions from healthcare professionals such as medical inquiries, adverse events, and product quality complaints with Medical Inquiries. Inquiries can come from multiple channels such as face-to-face visits, remote engagements, or contact centers. Inquiries require a quick and compliant response by the right individuals, typically medical experts like Medical Science Liaisons and Medical Communication Specialists. Medical Science Liaisons (MSLs) are skilled professionals who can answer scientific questions about drug details, interactions, off-label usage, and clinical product information. Medical Communication Specialists work in contact center environments and partner with MSLs to resolve inquiries, including incoming patient and consumer calls about product information, side effects, and adverse reactions.
Medical Insights: Use Medical Insights to gather information that can help uncover patient needs, validate concepts, evaluate scientific data, identify challenges faced by healthcare providers, understand geographical differences in patient care, and identify opportunities and threats. These insights play a crucial role in informing strategies across medical, clinical, and commercial aspects to enhance patient care. Users can capture Medical Insights from various sources such as meetings, calls, and research. They can also tag, vote, and link similar insights to identify and review trending insights.
MedTech Commercial Engagement: These objects are available for Life Sciences Cloud for MedTech Commercial Engagement.
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.
Merge Management: Maintain the integrity of your healthcare provider and healthcare organization profile information with a configurable process that removes duplicated account data. Users can either manually merge or receive merge requests from external sources to consolidate into a single winning account and remove the losing account. This capability provides organizations with a single, accurate view of the HCPs and HCOs that they work with.
Life Sciences Cloud Metadata Types: Metadata API enables you to access some types and feature settings that you can customize in the user interface.
Mobile Metadata: Mobile Metadata represents a metadata cache for the Life Sciences Cloud for Customer Engagement mobile application.
Mobile Sync: The Mobile Sync objects store information about data transactions synchronized from the Life Sciences Cloud for Customer Engagement mobile application. This information includes individual data transactions and supporting summary and logging information.
Next Best: The Next Best intelligent component is an AI-predictive tool that helps sales representatives to prioritize and personalize their customer interactions. Next Best Customer, Next Best Action, and Next Best Message together comprise the Next Best intelligent family. Next Best Customer surfaces the top accounts within a territory. Next Best Action suggests timely actions on a weekly basis, such as visits and emails. Next Best Message provides tailored and relevant messages for each product associated with the account. These recommendations are dynamically generated based on the real-time data, allowing field sales teams to act quickly or dismiss as needed. Next Best recommendations guide users to concentrate on the right accounts at the right time in the right channel to deliver the right message, fostering strong customer relationships.
Order Management: Order Management combines store check with quotes and pricing so field reps can assess a retail location and capture a priced quoted order from the same visit. Store check surfaces products, and quotes and pricing apply price books, pricing recipes, and sales transaction types to build, discount, and lock a quoted order. Both capabilities share visit and account, so a field rep can complete a store check and create a quoted order without switching context.
Patient Engagement: These objects are available for Life Sciences Cloud for Patient Engagement.
Life Sciences 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.
Product Management: Product Management centers on products, which are essential for business activities within the system. Products are modeled in a hierarchy that can mirror a company's SKU structure and are used in scenarios such as selling to pharmacies and delivering messages and samples to healthcare professionals. Product alignment is key to ensuring that users have access to products and related data to perform their jobs effectively. To maintain compliance and adherence to regulatory standards, user access to products can be controlled. Users can access and discuss only products available to them and not restricted for the target customer.
Fields on ProductTransfer: Life Sciences Cloud fields extend the standard ProductTransfer object to capture specific inventory and batch information.
Fields on ProductRequest: Life Sciences Cloud fields extend the standard ProductRequest object for sample order information, including destination user and urgency level.
Fields on ProductRequestLineItem: Life Sciences Cloud fields extend the Product Request Line Item object to represent information about sample order details.
Visit Management: Visit Management supports the call planning and execution process in the Life Sciences Industry. Field users can engage compliantly with accounts through various channels such as face-to-face, phone, and remote. With integrated intelligent content and remote engagement capabilities, field sales representatives and medical teams can plan, execute, and report on visits to healthcare providers and healthcare organizations. Information entered in a provider visit typically includes product details, product messages, presentations, marketing items and samples. Provider Visit Management also supports various compliance requirements regarding sample eligibility, sample limits and allocations, and e-signature capture.
Fields on Quote: Life Sciences Cloud fields extend the Quote object to represent visit, delivery, payment, and pricing information for quoted orders.
Fields on QuoteLineItem: Life Sciences Cloud fields extend the QuoteLineItem object to represent free goods and total quantity on a quoted order line.
Remote Engagement: Enable sales and medical teams to connect with healthcare professionals virtually across multiple channels, with interactive and compliant content, data collection capabilities, and technology flexibility. The benefits of Remote Engagement include accessibility, compliance with regulations like GDPR, increased productivity, convenience in scheduling, and the ability to create interactions through video, voice, and digital assets. Users can plan, launch, conduct, and finish remote calls or meetings, by using tracking, screen sharing, remote signatures, and feedback capture.
Request Bodies: This section lists the request bodies for Life Sciences Cloud Business APIs. The query parameters for an endpoint are listed along with each resource.
Resources: Use these resources of Life Sciences 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.
Fields on RetailStoreKpi: Life Sciences Cloud fields extend the standard RetailStoreKpi object to represent the target price for a store KPI.
Fields on RetailVisitKpi: Life Sciences Cloud fields extend the standard RetailVisitKpi object to represent actual and target prices captured during a store visit.
Samples Management: Enable pharmaceutical companies to efficiently handle and distribute drug samples to healthcare providers. Enhance drug sales and keep healthcare providers informed about the safe and effective use of products, leading to quicker treatments. Track and manage sales representative inventories of samples, ensuring compliance with regulations, and maintaining accurate records of distribution. Effective sample management is crucial for supporting healthcare providers and low-income patients, and ensuring ethical practices and regulatory compliance.
Segmentation: Group accounts based on specific conditions. Segmentations are reusable across different areas (such as sample limits) to distribute or assign elements to segments of accounts with the same set of criteria. There are two types of segmentations: static and dynamic. Static segmentation maintains the assignment even after the initial assignment. Dynamic segmentation changes based on account status or logic changes. Use Segmentation to assign and restrict of various elements without the need for individual account management.
Life Sciences Cloud Associated Objects: This section provides a list of objects associated to Life Sciences Cloud standard objects with their standard fields.
Life Sciences Cloud Standard Objects: Life Sciences Cloud provides a rich set of objects to store and access specialized Life Sciences information.
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.
Fields on StoreAssortment: Life Sciences Cloud fields extend the standard StoreAssortment object to represent the store check type for an assortment associated with a store.
Subject Management: Use Subjects to organize and manage information across various functions. Users can add topics to medical inquiries as subjects, facilitating automatic queue assignments and building a knowledge repository. Subjects can also be applied to medical insights and email templates for easy searching by subject filtering.
Surveys: Surveys provide Life Science companies with an easy-to-use solution for creating, distributing, and completing surveys. Surveys help ensure regulatory compliance, support accurate data management, and deliver actionable insights that enhance research outcomes and enable informed decision-making. Additionally, Surveys include an offline survey capability in the Life Sciences Cloud mobile app, allowing users to collect responses without an internet connection. When back online, data is automatically synced, ensuring seamless integration with the feedback and analytics processes.
System Objects: System objects are related to core system functionality used by Life Sciences Cloud for Commercial Engagement.
Territory Management: Territory Management supports strategically organizing territories and aligning healthcare providers (HCPs) and healthcare organizations (HCOs) to territories. Use Territory Management to optimize resource allocation and improve engagement with HCPs/HCOs. Life Sciences Cloud enables industry-specific territory management features that are integrated with Salesforce Enterprise Territory Management.
Life Sciences 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.
Workflow Management: Configure workflows for Commercial Engagement objects. As users advance records through the steps in a workflow path, unique permissions apply based on each step and the conditions met for that step. Control data permissions for create, update, and delete operations, and control user actions based on a user's role in the workflow. Validate custom business rules and enforce a status transition action checklist. Configure additional actions such as calling Platform Events for both mobile and web platforms.
Life Sciences Cloud Standard Invocable Actions: Use the standard invocable actions available with Life Sciences Cloud to streamline the process of enrolling participants in clinical trials.
Evaluate Access Action: Evaluates a specified access check (user permission) against the current security context and returns whether the running user has the requested permission.
Get Context Data Action: Retrieves the context data that is passed as an input to a prompt template that generates a summary of the data.
Get Qualified Products Action: Retrieves the PricebookEntry IDs for products that a user is authorized to use for a given account and territories. When productPurpose isn’t specified, the action defaults to Quote. Allowed purpose values are Quote, Visit, and Order.
Serialize Hierarchical Context Data: Serializes the hierarchical context data from the Apex embeddedai__RecordApexRepresentation records that are passed as input to a prompt template that generates a summary of the data.
Share Quote Based on Account Action: Synchronizes Quote sharing with Account sharing by querying AccountShare records for the specified Quote account ID and upserting the corresponding QuoteShare records.
Input Classes: These are the Apex input classes for Life Sciences Cloud.
Output Classes: These are the Apex output classes for Life Sciences Cloud.
Apex Reference: This Apex reference goes into detail about the built-in Apex classes, interfaces, methods, or enums for Life Sciences Cloud.
Adverse Events: Adverse Events data model helps you in managing and documenting any unfavorable or unintended signs, symptoms, or diseases that occur in participants during the research study. These adverse events can include a wide range of physical or psychological effects that varies from mild discomfort to serious health complications.
Life Sciences Cloud Data Models: Life Sciences Cloud uses a suite of standard Salesforce objects to structure and store data related to Clinical Engagement, Customer Engagement, Patient Engagement, MedTech Commercial Engagement and other features. To better understand how features work, it helps to look at the data models, which are graphical representations of collections of objects and their relationships.
Financial Assistance Program: The financial assistance program data model helps life sciences organizations implement several financial assistance programs for eligible patients to receive assistance with their out of pocket medical expenses.
ActionableListDefinition: Represents the data source definition details associated with an actionable list.
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.
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 life sciences organizations in determining pharmacy benefits coverage for the medications prescribed to the patients under a care program.
AccountPlan: Life Sciences Cloud fields extend the standard Account Plan object to represent information about customers with measurable objectives and executable steps to proactively manage and grow customer relationships.
AccountPlanObjective: Life Sciences Cloud fields extend the standard Account Plan Objective object to represent information about strategic objectives or initiatives pursued by a relationship team with a customer to enhance customer engagement and satisfaction.
ActionableList: Represents an actionable list. This object is available in API version 65.0 and later.
ActionableListFilterCriteria: Represents a logical expression containing filter conditions to include or exclude data from the dataset that's associated with the actionable list. This object is available in API version 65.0 and later.
ActionPlan: Life Sciences Cloud fields extend the standard ActionPlan object to represent the instance of an action plan.
ActionPlan: Standard and custom fields extend the standard ActionPlan object to represent an instance of the compliance program assigned to an account.
ActionPlanItem: Standard and custom fields extend the standard ActionPlanItem object to represent the junction between Action Plan and Provider Engagement Compliance Cycle.
ActionPlanItem: Life Sciences Cloud fields extend the standard ActionPlanItem object to represent the instance of an action plan item.
ActionPlanTemplateItem: Represents the instance of an item on an action plan template version. This object is available in API version 64.0 and later in Key Account Management feature in the Life Sciences Cloud.
ActionPlanTemplateItemValue: Standard and custom fields extend the standard ActionPlanTemplateItemValue object to represent the value associated with an action plan template item.
ActionPlanTemplateItemValue: Life Sciences Cloud fields extend the standard ActionPlanTemplateItemValue object to represent the value associated with an action plan template item.
ActionPlanTemplateVersion: Life Sciences Cloud fields extend the standard ActionPlanTemplateVersion object to represent a version of an action plan template.
Applicant: Specify the care program enrollee represented as an applicant. This object is available in API version 59.0 and later.
BatchJob: Represents an instance of a batch job that is either running and has been run. This object is available in Life Sciences Cloud API version 65.0 and later.
BatchJobPart: Represents one part of a batch job. This object is available in Life Sciences Cloud in API version 65.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.
CommSubscription: Standard and custom fields extend the standard Communication Subscription object to represent a customer’s subscription preferences for a specific communication. This object is available in API version 65.0 and later.
CommSubscriptionConsent: Standard and custom fields extend the standard Communication Subscription Consent object to represent a customer’s consent to a communication subscription. This object is available in API version 65.0 and later.
Fields on ContactPointAddress: Life Sciences Cloud fields extend the standard Contact Point Address object to represent a contact’s billing or shipping address associated with an individual or account. This object is available in API version 65.0 and later.
ContactPointConsent: Standard and custom fields extend the standard Contact Point Consent object to represent information about a customer's consent to be contacted via a specific contact point. This object is available in API version 65.0 and later.
CustomObjectParticipant: Standard and custom fields extend the standard CustomObjectParticipant object to represent information about the individual collaborating on or who needs to be informed of the Medical Insight.
DataUsePurpose: Standard and custom fields extend the standard Data Use Purpose object to represent information about the reason for contacting a prospect or customer. This object is available in API version 65.0 and later.
DigitalSignature: Life Sciences Cloud fields extend the standard DigitalSignature object to represent a signature. This object is available in API version 65.0 and later.
DocumentTemplate: Represents information about dynamic document generation. This object is available in API version 56.0 and later.
Fields on Event: Life Sciences Cloud fields extend the standard Event object to represent an event in the calendar. In the user interface, event and task records are collectively referred to as activities.
Fields on Event Relation: Life Sciences Cloud fields extend the standard Event Relation object to represent a person (a user, lead, or contact) or a resource (such as a conference room) invited to an event.
Expense: Life Sciences Cloud fields extend the standard Expense object to represent expenses related to a visit. This object is available in API version 65.0 and later.
Location: Standard and custom fields extend the standard Location object to represent information about a user responsible for the location. This object is available in API version 65.0 and later.
PartyPublication: Represents the details of a party's publication.
ProductItemTransaction: Standard and custom fields extend the standard Product Item Transaction object to represent information about an action taken on a product item. This object is available in API version 65.0 and later.
ProductTransfer: Standard and custom fields extend the standard Product Transfer object to represent information about the transfer of inventory between locations. This object is available in API version 65.0 and later.
ProgramEnrollment: Represents details of enrollment for benefits in a program. This object is available in API version 57.0 and later.
RecordAlert: Represents an alert message about a specific record and tracks the status and active period of the alert. This object is available in API version 65.0 and later.
SurveyResponse: Standard and custom fields extend the standard Survey Response object to represent information about a participant’s response to a survey. This object is available in API version 65.0 and later.
VideoCall: Standard and custom fields extend the standard VideoCall object to represent a video call. The VideoCall object stores important information about the video session, including the meeting ID for connection, video call duration, associated participants, linked recordings, and vendor-specific attributes, ensuring a seamless and organized approach to managing video call data. This object is available in API version 65.0 and later.
VideoCallParticipant: Standard and custom fields extend the standard VideoCallParticipant object to represent a participant of a video call. Participant information can come from the video call provider (for example, Zoom), or Salesforce. This object is available in API version 65.0 and later.
VideoCallRecording: Standard and custom fields extend the standard VideoCallRecording object to represent a recording from a video call, such as a video recording, a voice recording, or a transcript. This object is availavle in API version 65.0 and later.
Site Management: The Site Management data model helps life sciences organizations identify suitable sites for conducting research studies. Study managers can search for the sites and investigators using the Criteria-Based Search and Filter, and send them assessments. From the assessment responses, study managers can assign scores to the sites, investigators, and their responses. They can also tag the sites and investigators for future site selection efforts.
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.
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.
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.
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.
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.
SearchResultActionConfig: Represents a collection of fields to set up the actions that a user can perform on results returned by criteria-based search.
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.
UIObjectRelationConfig: Represents the admin-created configuration of the object relation UI component.
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.
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.
AccountPlanParticipant: Represents the team members participating in the account plan. This object is available in API version 65.0 and later.
AccountPlanProduct: Represents all the products associated with an account plan or its objectives. This object is available in API version 65.0 and later.
AccountPlanRelaObjAnalysis: Represents the strategic analysis done on objects related to the account plan. This object helps to identify internal and external factors that could potentially affect the plan, its objectives, or any related objects. This object is available in API version 65.0 and later.
AccountPlanRelationship: Represents the relationship between multiple account plans for key account management. This object is available in API version 65.0 and later.
AccountPlanStakeholder: Represents the key individuals who can influence an account's actions or have a vested interest in its outcomes. This object is available in API version 65.0 and later.
AccountPlanStkhldrAction: Represents a junction between an account plan stakeholder and an action. Stores information about an action for an account plan that's associated with a stakeholder. This object is available in API version 65.0 and later.
AccountPlanStkhldrProduct: Represents a junction between an account plan stakeholder and a product. Stores information about the products associated with a stakeholder for an account plan. This object is available in API version 65.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.
AcctPlanPtcpStakeholder: Represents a junction between an account plan participant and an account plan stakeholder. Stores information about the account plan participant who collaborates with the account plan stakeholder for performing account plan tasks. This object is available in API version 65.0 and later.
ActionPlanStatusPeriod: Represents the historical changes to the status of an action plan.
ActionPlanTemplate: Represents the instance of an action plan template. In Life Sciences cloud, this object is available in API version 65.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.
ActivityPlan: Represents the user's activity goals for the cycle. This object is available in API version 65.0 and later.
ActivityPlanTerritory: Represents the territory details associated with an activity plan. This object is available in API version 65.0 and later.
Address: Represents a mailing, billing, or home address.
AdverseEventAction: Preventive actions that contributed to avoiding the adverse event or Ameliorating actions taken after the adverse event occured in order to reduce the extent of harm. This object is available in API version 61.0 and later.
AdverseEventCause: Describes the entity that is suspected to have caused the adverse event. This object is available in API version 61.0 and later.
AdverseEventContribFactor: The contributing factors suspected to have increased the probability or severity of the adverse event. This object is available in API version 61.0 and later.
AdverseEventEntry: Represents the event related to unintended/anticipated effects on research participants. This object is available in API version 61.0 and later.
AdverseEventOutcome: Type of outcome from the adverse event. This object is available in API version 61.0 and later.
AdverseEventParty: Indicates who or what participated in the adverse event and how they were involved. This object is available in API version 61.0 and later.
AdverseEventSupportInfo: Supporting information relevant to the event. This object is available in API version 61.0 and later.
AdverseEvntResultingEffect: Effect on the subject due to this event. This object is available in API version 61.0 and later.
AdvTherapyFieldOptOverride: Represents a list of fields with changed optionality, based on certain parameters. This object is available in API version 59.0 and later.
AppAlert: Represents an alert message at the object, tab, or global level. This object is available in API version 65.0 and later.
AppAlertTerritory: Represents a junction between an Alert and a Territory where the alert is sent. This object is available in API version 65.0 and later.
AppAlertUserResponse: Represents the user action for an alert. This object is available in API version 65.0 and later.
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.
AsmtIndDefExt: Represents the translations of assessment indicator definitions. The API name for the Assessment Indicator Definition object is 29 characters, exceeding the 25-character limit for data translation. So, translating assessment indicator definitions requires a new object. This object is available in API version 68.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.
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.
BudgetMngEventType: Each row represents a junction that links a budget to permitted event types, ensuring funds are only allocated to events that align with the budget's purpose. This object is available in API version 67.0 and later.
BudgetProduct: Represents a junction between a budget and the product that the budget is assigned to. This object is available in API version 67.0 and later.
BudgetTerritory: Represents a junction between a budget and the territory that the budget is assigned to. This object is available in API version 67.0 and later.
BusinessLicense: Represents the licenses of a party role like healthcare provider or producer.
BusinessLicenseProduct: Represents the licenses required to be linked to a product for the healthcare provider. This object is available in API version 65.0 and later.
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.
CareInterventionType: Represents the standard, defined list of interventions maintained by an organization. Available in API version 45.0 and later.
CarePgmEnrleeStatusPeriod: Represents the historical changes to the status or stage of a care program enrollee. This object is available in API version 61.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.
CarePgmEnrollmentEvalRslt: Represents the result of an evaluation done to assess the eligibility of a participant enrolling for a research study or care program. This object is available in API version 62.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.
CarePgmTeamMbrRolePeriod: Represents the historical changes in the role of a care program team member. This object is available in API version 61.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.
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.
CareProgramDetail: Represents the detail records related to the care program. This object is available in API version 61.0 and later.
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.
CareProgramSite: Represents the details about the care program site. This object is available in API version 61.0 and later.
CareProgramSiteContract: Represents the association of a care program site and a contract. This object is available in API version 62.0 and later.
CareProgramStatusPeriod: Represents the historical changes to the status of a care program. This object is available in API version 61.0 and later.
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.
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.
CareSiteIstgrSearchableFld: Represents information about the clinical trial investigator associated with a site. This object is available in API version 63.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.
CareTaxonomy: Represents a static list of taxonomy codes.
CommSubConsentCmplSnpsht: Represents the snapshot of compliance information that’s captured at the time of consent of the communication subscription. This object is available in API version 65.0 and later.
ComplianceStatementDef: Used to ensure adherence to regulatory requirements during health care provider engagements. Stores essential compliance information that's displayed across multiple use cases, including visits and consent capture. Compliance statements can be configured to require acknowledgement, have an optional acknowledgement, or be purely informational. Their intended audience can vary from the accounts that are being engaged with to the end user themselves.
ContactPointBestContactTime: Represents the optimal time to visit associated contact point addresses. This object is available in API version 65.0 and later.
ContactPointSocial: Represents social media identifiers or contact points for an individual or account. This object is available in API version 65.0 and later.
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.
DeviceSyncSummary: Represents a summary of the synchronized data from a mobile device. This object is available in API version 65.0 and later.
DeviceSyncTransaction: Represents a set of related data items to synchronize from a mobile device. This object is available in API version 65.0 and later.
DeviceSyncTransactionLog: Represents a log with information about the synchronized data from a mobile device. This object is available in API version 65.0 and later.
DeviceSyncTransactionRecord: Represents a single data item to synchronize from a mobile device. This object is available in API version 65.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.
DistributionChannel: Represents a list of distribution channels, for example direct sales, wholesale, retail, and online, used to specify the fulfillment method for an order or sale. This object is available in API version 68.0 and later.
EnablementCoaching: Represents an enablement coaching that facilitates the formal evaluation of attendees. This object is available in API version 67.0 and later.
EnablementCoachingAttendee: Represents the attendees of an enablement coaching. This object is available in API version 67.0 and later.
EnablementCoachingSession: Represents the association between an enablement coaching and its operational context, such as a visit or appointment. This object is available in API version 67.0 and later.
EnrollmentEligibilityCriteria: Represents criteria that define patient enrollment eligibility for one or more care programs.
EstimatedExpense: Represents the estimated expense of a managed event. This object is available in API version 67.0 and later.
EstimatedExpensePtcpAlloc: Each row represents an allocation of managed event participant to an estimated expense of a managed event. This object is available in API version 67.0 and later.
EventMgmtParticipantRole: Each row represents the responsibility or function a participant performs within an event. For example, organizing, coordinating, presenting, or attending. This object is available in API version 67.0 and later.
EventMgmtParticipantType: Each row represents the category or classification of participants associated with a managed event. This object is available in API version 67.0 and later.
EventMgmtPtcpTypeRoleMap: Each row represents the mapping of allowed participant roles to specific participant types for a given event type. This object is available in API version 67.0 and later.
EventPlan: Represents the plan for an event type. This object is available in API version 67.0 and later.
EventPlanBudget: Represents a junction between an event plan and a budget that's allocated for the event plan. This object is available in API version 67.0 and later.
EventPlanParticipant: Represents a junction between an event plan and the person who is set to participate in events that roll up to the event plan. This object is available in API version 67.0 and later.
EventPlanProduct: Represents a junction between an event plan and a product or category that's part of the event plan. This object is available in API version 67.0 and later.
EventPlanSubject: Represents a junction between an event plan and a subject that's part of the event plan. This object is available in API version 67.0 and later.
EventPlanSvcSpclzn: Each row represents a junction between an event plan and a specific event service specialization, ensuring the plan's resources are appropriately constrained by the specialization's compliance and budgetary rules to maintain strategic alignment. This object is available in API version 67.0 and later.
EventPlanTerritory: Represents a junction between an event plan and the territory that the event plan is for. This object is available in API version 67.0 and later.
ExpenseParticipant: Represents a junction between an expense and the person who incurred the expense. This object is available in API version 67.0 and later.
ExpenseType: The ExpenseType object is a category that's used to classify an expense that occurs. This object is available in API version 65.0 and later.
Expert: Represents the details of an expert who can speak or present at managed events. This object is available in API version 67.0 and later.
ExpertSubject: Represents a junction between an expert and the subject that the expert is certified to speak or present about in managed events. This object is available in API version 67.0 and later.
Formulary: Represents the details of the formulary covered by the payer's health insurance plan. This object is available in API version 65.0 and later.
FormularyItem: Represents details of products within the formulary, including the drug tier, coverage, and copay. This object is available in API version 65.0 and later.
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.
GoalDefinitionProduct: Represents a junction between a goal definition and a product. Stores information about the goal definition that defines the business objective for a product. This object is available in API version 65.0 and later.
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.
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.
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.
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.
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.
Inquiry: Represents the details of an inquiry logged by a sales representative or other user. This object is available in API version 65.0 and later.
InquiryQuestion: Represents a question asked by a healthcare professional (HCP) during an inquiry. This object is available in API version 65.0 and later.
InquiryQuestionAnswer: Represents the answer provided by the Medical Science Liaison (MSL) to the inquiry question. This object is available in API version 65.0 and later.
IntegrationJobRun: Represents the statistical details of asynchronous integration jobs that are run on the system. This object is available in API version 65.0 and later.
InventoryCntProdtBatchItem: Represents the inventory count of a product batch at a location. The inventory count product batch item is a child object of inventory count assessment. This object is available in API version 65.0 and later.
InventoryCountAssessment: Represents an inventory count performed at a location. This object is available in API version 65.0 and later.
InventoryOperation: Represents operations performed on the inventory, such as transfers, disbursements, or adjustments. This object is available in API version 65.0 and later.
LifeSciAccountListColumn: Represents the information of the columns selected from accounts or its supported direct relationship objects in account filters. This object is available in API version 65.0 and later.
LifeSciAccountListMember: Represents information about account static lists and routine. This object is available in API version 65.0 and later.
LifeSciAcctGrpAssignment: Represents a junction between an account and actionable list. This object is available in API version 65.0 and later.
LifeSciAcctListFilterCrit: Stores the rules and conditions derived from the Account object or its supported direct relationship objects to filter Life Sciences accounts. This object is available in API version 65.0 and later.
LifeSciDataChangeDef: Represents the object for which the data change request is configured. This object is available in API version 65.0 and later.
LifeSciDataChangeRequest: Represents the data change requests for the all objects. This object is available in API version 65.0 and later.
LifeSciDataChgDefMngFld: Represents the fields for which the data change request is configured for all objects. This object is available in API version 65.0 and later.
LifeSciDataChgDefRecType: Represents the management of data validation for the object by record type.
LifeSciDataChgPersonaDef: Represents the configuration of data updates for the object by persona.
LifeSciEmailTemplate: Represents a collection of pre-designed and approved email templates that end users send to healthcare professionals (HCPs). These templates help users create and send consistent, professional emails quickly and efficiently. This object is available in API version 65.0 and later.
LifeSciEmailTmplFragment: Represents a collection of reusable components that can be inserted into email templates, allowing end users to create custom and modular emails tailored to their needs. This object is available in API version 65.0 and later.
LifeSciEmailTmplRelaFrgmt: Represents the connectors that link email templates and fragments together. This object is available in API version 65.0 and later.
LifeSciEmailTmplSnapshot: Stores the different versions of an email template for tracking purposes. This object is available in API version 65.0 and later.
LifeScienceAccountList: Represents the type of account lists, such as filter, static list, and routine. This object is available in API version 65.0 and later.
LifeScienceAccountListObject: Represents the object that is referenced in the provider account list. This object is available in API version 65.0 and later.
LifeScienceCustomScript: Represents a custom script associated with a Life Science stage object within a workflow. Use a custom script to implement the validation logic for the stage object. This object is available in API version 65.0 and later.
LifeScienceDocument: Represents a signed document and stores document fields.
LifeScienceEmail: Represents a collection of sendable messages that manages the creation, sending, and tracking of email communications. This object stores the details of each email, including the content, the status of sending attempts, and any responses received. This object is available in API version 65.0 and later.
LifeScienceEmailFragment: Represents a record of an email template fragment that a user selected and included in a sent life science email, capturing the content version at send time. This object is available in API version 68.0 and later.
LifeScienceMobileApp: Represents information about a mobile device associated with a user. This object is available in API version 65.0 and later.
LifeScienceTriggerHandler: Represents a collection of fields to set up the trigger handlers to run for each Life Sciences object. This object is available in API version 65.0 and later.
LifeSciMarketableProduct: Represents information about all products a Life Science company manufactures, markets, sells, or competes with, including brands, indications, and therapeutic areas. It also represents additional information on physical products that are sampled, ordered, or distributed as promotional items. This object is available in API version 65.0 and later.
LifeSciMetadataAssignment: Represents the assignments for a Life Sciences configuration record. This object is a child of LifeSciMetadataRecord. This object is available in API version 65.0 and later.
LifeSciMetadataCategory: Represents the category that Life Sciences configuration records are organized into. This object is available in API version 65.0 and later.
LifeSciMetadataFieldValue: Represents a field value for a Life Sciences configuration record. This object is a child of LifeSciMetadataRecord. This object is available in API version 65.0 and later.
LifeSciMetadataRecord: Represents a configuration record for Life Sciences. This object is a child of LifeSciMetadataCategory. This object is available in API version 65.0 and later.
LifeSciMktProdtCodeSet: Represents the relationship between a life science marketable product and a code set for a specific jurisdiction. This object is available in API version 65.0 and later.
LifeSciMobileMetadataRecord: Represents the metadata created for the mobile application. This object is available in API version 65.0 and later.
LifeSciProductAcctRstrc: Represents information about product use limitations for an account. Product restrictions help facilitate compliance with product detailing and sampling regulations and company policies. This object is available in API version 65.0 and later.
LifeSciStageAction: Represents the configuration of an action performed as part of a workflow. This object is available in API version 65.0 and later.
LifeSciStageObject: Represents an object associated with a workflow. This object is available in API version 65.0 and later.
LifeSciStageOperation: Represents the criteria to evaluate in determining the applicable permissions and available actions for a specific step in a workflow. This object is available in API version 65.0 and later.
LifeSciStageOperationAction: Represents a junction between a stage operation and a stage action. This object defines a set of available stage actions in the context of a specific stage operation. This object is available in API version 65.0 and later.
LifeSciStageOperationCondn: Represents a logical expression for applying an operation in a workflow. This object is available in API version 65.0 and later.
LifeSciStagePath: Represents information about the steps associated with a workflow and the path from one step in the workflow to the next. This object is available in API version 65.0 and later.
LifeSciStageValue: Represents an individual step within a workflow. This object is available in API version 65.0 and later.
MedicalInsight: Represents the important information observed or heard through various outlets like meetings, calls, or research, which is used to inform strategies for better patient care.
MemberPlan: Represents details about the insurance coverage for a member or subscriber.
MergeRequest: Represents the details related to tracking the merge history of records. It maps the losing record (deleted as result of merge) to the winning records (remains after merge). This object is available in API version 65.0 and later.
MngEvent: Represents the details of a managed event. This object is available in API version 67.0 and later.
MngEventBudget: Represents a junction between a managed event and the budget that's allocated for the managed event. This object is available in API version 67.0 and later.
MngEventParticipant: Represents a managed event participant and their participation details. This object is available in API version 67.0 and later.
MngEventParticipantDiscrepancy: Captures the list of discrepancies that have been identified for participants when they don't meet the limits or restrictions on the event. This object is available in API version 67.0 and later.
MngEventProduct: Represents a junction between a managed event and the product that's a focus area of the managed event. This object is available in API version 67.0 and later.
MngEventResource: Represents the details of a resource that's required for a managed event. This object is available in API version 67.0 and later.
MngEventResourcePreference: Represents the preference rank of a resource that's requested for a managed event. This object is available in API version 67.0 and later.
MngEventTerritory: Represents a junction between a managed event and the territory that the managed event belongs to. This object is available in API version 67.0 and later.
MngEventType: Represents a type of managed event. This object is available in API version 67.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.
PersonEducation: Represents information about professional education for a person in a provider role.
PersonEmployment: Represents information about a person’s employment.
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.
Presentation: Represents a collection of presentations, each with various attributes such as activation dates, the ability to be sent by email, associated tags, and gestures. This object is available in API version 65.0 and later.
PresentationClickStrmEntry: Represents the collection of clickstream data captured while the presentation is being used or shown across different forums. This object is available in API version 65.0 and later.
PresentationContent: Represents the AI-generated static asset at run-time, based on a Presentation Content Definition record. This object is available in API version 66.0 and later.
PresentationForum: Represents the details of the forums (call, meetings, order) where the presentation was presented. This object is available in API version 65.0 and later.
PresentationLinkedPage: Represents the connection between a presentation and its associated presentation pages. This object is available in API version 65.0 and later.
PresentationPage: Represents a collection of pages that can be used within a presentation. Each page can contain multiple slides. Pages can be reused across different presentations. This object is available in API version 65.0 and later.
PresentationPageProduct: Represents the link between a presentation page and a product, and may also include a connection to related product message (product guidance). This object is available in API version 65.0 and later.
PresentationPartyAccess: Represents the access-sharing details of a presentation with a healthcare professional, including an expiration date for that access. This object is available in API version 65.0 and later.
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.
ProductBatchItem: Represents the details about the product items in each batch. This object is available in API version 65.0 and later.
ProductDisbursement: Represents details about the product being disbursed. This object is available in API version 65.0 and later.
ProductGuidance: Represents information about key product messages, product objectives, or other information that can assist or guide users when working with the product. This object is available in API version 65.0 and later.
ProductionBatch: Represents the batch of homogeneous products manufactured in the same production line. This object is available in API version 65.0 and later.
ProductRequest: Represents a device request made as part of a care program. Standard and custom fields extend the standard Product Request object to represent information about sample orders. This object is available in API version 65.0 and later in Samples Management feature.
ProductRequestLineItem: A junction object between ProductRequest and ProductTransfer This object is available in API version 50.0 and later. This object is available in API version 65.0 and later in Samples Management feature.
ProductTerrDtlAvailability: Represents the details of the products aligned to territories. This object is an extension of the information stored in the Product Territory Availability object and is used for internal purposes. This object is available in API version 65.0 and later.
ProductTerritoryAvailability: Represents information about the products aligned to territories. This object is available in API version 65.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.
ProviderAcctProductInfo: Represents specific information for healthcare professionals or healthcare organizations at the territory and product levels. This information is used for segmentation and product-level rankings. This object is available in API version 65.0 and later.
ProviderAcctTerritoryInfo: Represents the engagement data between an account and a user within an assigned territory, which includes next provider visit date, preferred address, and planned activities. This object is available in API version 65.0 and later.
ProviderActivityGoal: Represents the goals for the provider accounts. This object is available in API version 65.0 and later.
ProviderActivityGoalLimit: Represents the limits defined for provider activity goals. This object is available in API version 67.0 and later.
ProviderActivityGoalMeasure: Represents the goal measurement for an activity type. This object is available in API version 65.0 and later.
ProviderActivityMeasureType: Represents the details of the activity goal measure type. This object is available in API version 65.0 and later.
ProviderActvtyPlanAdjusment: Represents the details of the adjustment requests for an activity plan. This object is available in API version 65.0 and later.
ProviderAffiliation: Represents the relationship between two healthcare professionals or healthcare organizations. This object is available in API version 65.0 and later.
ProviderAffiliationProduct: Represents the relationship between two healthcare professionals, where one influences the other regarding a product. This object is available in API version 65.0 and later.
ProviderSampleLimit: Represents sample limits and remaining quantity applied to a given account and product. This object is available in API version 65.0 and later.
ProviderSampleLimitTemplate: Setup object that represents the definition and rules of sample limits templates. This object is available in API version 65.0 and later.
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.
ProviderSmplLmtTmplAssignment: Junction that relates sample limit templates to products. This object is available in API version 65.0 and later.
ProviderVisit: Represents the details of a field user's visit to a health care provider. For example, a sales representative visiting a health care provider to discuss product usage and efficacy to enhance adoption. This object is available in API version 65.0 and later.
ProviderVisitChangedEvent: Represents an event for a data manipulation operation performed on a provider visit record. This object is available in API version 65.0 and later.
ProviderVisitDtlProductMsg: Represents delivered messages and reactions from the health care provider for products discussed during a visit. This object is available in API version 65.0 and later.
ProviderVisitMarketingItem: Represents marketing items provided to the health care provider as part of a visit. This object is available in API version 65.0 and later.
ProviderVisitProdDetailing: Represents products discussed during a visit with a health care provider, including key details such as the product brand, therapeutic area, and other relevant information. This object is available in API version 65.0 and later.
ProviderVisitProdDiscussion: Represents any additional notes or information regarding the products discussed during a visit to a health care provider. This object is available in API version 65.0 and later.
ProviderVisitRqstSample: Represents sample products requested to be shipped to the health care provider during a visit. This object is available in API version 65.0 and later.
PrstCntntDefAssignment: Represents assignment of presentation content definition, such as a Podcast or Text Summary to the users, profiles, or groups authorized to access or view, enforcing content visibility and entitlement rules. This object is available in API version 66.0 and later.
PrstCntntUsageSummary: Represents information about the usage of the content asset, including number of times it has been consumed and the point till which it has been consumed. This object is available in API version 66.0 and later.
PrstContentDefinition: Represents the reusable configuration required to generate an end-user content asset, such as an audio summary. This object is available in API version 66.0 and later.
PrvdAccountTerritorySummary: Represents the summaries generated for a provider account for the terrories it is aligned to. This object is available in API version 65.0 and later.
PrvdAccountUserGroupInfo: Represents the classification values for the provider account user group. This object is available in API version 65.0 and later.
PrvdActvtyGoalMeasureProdt: Represents the details of the products associated with the activity goal measure. This object is available in API version 65.0 and later.
PrvdActvtyPlanAdjProdt: Represents the details of the products associated with the provider activity plan adjustment. This object is available in API version 65.0 and later.
PrvdEngmtComplianceCycle: Represents the duration and progress of compliance cycles for a provider, which captures essential metadata to ensure effective monitoring and management of compliance-related activities.
PrvdManagedEventVldEvent: Represents an event that's generated when a provider-related managed event fails or breaches its validation limits. This triggers notifications to users to take prompt action to rectify the breach. This object is available in API version 67.0 and later.
PrvdVstSmplLmtDiscrepancy: Represents discrepancies that occur when samples or sample shipment requests exceed a sample limit. This object is available in API version 65.0 and later.
PrvdVstSmplLmtTransaction: Represents samples or sample shipment requests captured in a visit. This object is available in API version 65.0 and later.
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.
QuoteDocumentCreationEvent: Represents the event that's generated when a quote document is created. This object is available in API version 68.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.
ResearchStdyCmprGroupCndt: Represents the junction between a research study control group and a research study candidate. This object is available in API version 61.0 and later.
ResearchStdyCndtStatusPrd: Represents the time duration during which a research study candidate is assigned a specific status. This object is available in API version 61.0 and later.
ResearchStdyRandomization: Represents the randomization algorithm configuration defined for a research study. This object is available in API version 61.0 and later.
ResearchStdySearchableField: Represents a common dataset that includes multiple fields and values from multiple objects and serves as the basis for searches related to research studies. This object is available in API version 61.0 and later.
ResearchStudy: Represents the details of a research study that include its design, execution, and oversight. This object is available in API version 61.0 and later.
ResearchStudyCandidate: Represents the details of the research participant which includes the associated account and the status of the subject. This object is available in API version 61.0 and later.
ResearchStudyCmprGroup: Represents the details of a research study comparison group. This object is available in API version 61.0 and later.
ResearchStudyProtocolInfo: Represents details of the research study protocol document. This object is available in API version 62.0 and later.
ResearchStudyRelation: Represents different related research studies. This object is available in API version 61.0 and later.
ResearchStudyRndmBlockSlot: Represents the individual randomization block items corresponding to a Research Study Randomization Block This object is available in API version 61.0 and later.
RestrictedParty: Represents a party such as a participant, a speaker, or a vendor that's restricted from taking part in a managed event. This object is available in API version 67.0 and later.
RsrchStdyRandomizationBlock: Represents the details of a block that’s generated through the parameters specified in the research study randomization. This object is available in API version 61.0 and later.
RsrchStdyRandomizationCrit: Represents the criteria definition for grouping the candidates participating in the research study. This object is available in API version 61.0 and later.
ServiceAppointmentGroup: Stores information about a group of related service appointments. This object is available in API version 56.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.
Sprint: Represents a specific timeframe within which account action plans are executed within key account management. This object is available in API version 65.0 and later.
Subject: Represents a subject that's discussed or presented at managed events. This object is available in API version 67.0 and later.
SubjectAssignment: Represents a junction between a subject and the managed event that the subject is a part of. This object is available in API version 67.0 and later.
SubjectMaterialTemplate: Represents the details of a subject material template that's approved for use in managed events. This object is available in API version 67.0 and later.
SubjectProduct: Represents a junction between a managed event subject and the product that the subject belongs to. This object is available in API version 67.0 and later.
SurveyQstnResponseOffline: Represents a participant’s answer to a specific survey question, for both offline and staging environments. This object is available in API version 65.0 and later.
SurveyResponseOffline: Represents information about a participant’s offline survey response, including the response status, participant location, and completion time, for both offline and staging environments. This object is available in API version 65.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.
TerrGeoAssignmentRule: Represents alignment rules that assign accounts to specific territories based on geocodes. This object is available in API version 65.0 and later.
TerritoryAccountScore: Stores the intelligent provider scores to help users better recognize the top accounts in their territories. This object is available in API version 65.0 and later.
TerritoryAcctProdMsgScore: Stores the intelligent product message score on the territory accounts to identify the most relevant message to deliver in their visits. This object is available in API version 65.0 and later.
TerritoryAcctRcmdAction: Represents the recommended engagement actions for the account at territory level. This object is available in API version 65.0 and later.
TerritoryBusinessPlan: Represents the detailed, strategic outline of vital customer information. This object is used to effectively manage and expand customer relationships within a specific territory. This object is available in API version 65.0 and later.
TerritoryContentTmplAsgnt: Stores a link between a territory and a template allowing for the assignment of relevant content to specific territories. This object is available in API version 65.0 and later.
TerritoryProdtQtyAllocation: Represents the quantity allocation of a product to a given territory so that the system validates against the remaining quantity or maximum disbursement limit. This object is available in API version 65.0 and later.
TerritoryUserDowntime: Defines the blocks of time during normal business hours for various types of reasons when sales representatives are out of their territories. This object is available in API version 65.0 and later.
TerrProvAffilAssignRule: Represents a rule for aligning the affiliated accounts to the existing set of aligned accounts, based on their role, specialty, and account type. This object is available in API version 65.0 and later.
TimePeriod: Represents the time period that's used to calculate the indicator performance and result.
UnitOfMeasure: Represents the unit of measures for care metrics and care observations. This object is available in API version 49.0 and later.
UserAdditionalInfo: Represents information about a user such as additional identifiers, user preferences, and a return address. This object is available in API version 65.0 and later.
UserReaction: Represents the reaction from users to the medical insight, like upvote and downvote, which is used to identify trending insights.
VideoCallPtcpRequest: Represents information about remote signature request for video call participants, including key details such as status, type, and other relevant information for tracking and managing the signature process. This object is available in API version 65.0 and later.
VideoCallPtcpSession: Represents information about participants during remote sessions, including duration, device type, operating system, and browser. It logs reconnections separately, offering a comprehensive view of each participant's experience. This object is available in API version 65.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.
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.
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
LifeSciConfigAssignment: Represents the assignments for a Life Sciences configuration record. This object is a child of LifeSciConfigRecord.
LifeSciConfigCategory: Represents the category that Life Sciences configuration records are organized into. This object is available in API version 65.0 and later.
LifeSciConfigFieldValue: Represents a field value for a Life Sciences configuration record. This object is a child of LifeSciConfigRecord.
LifeSciConfigRecord: Represents a configuration record for Life Sciences. This object is a child of LifeScienceConfigCategory.
SearchableObjDataSyncInfo: Represents information about the data synchronization for a search object, such as frequency of synchronization, status, and the date and time of the last synchronization. This object is available in API version 58.0 and later.
SearchCriteriaConfiguration: Represents the configuration details of searchable field sets such as the group of fields used as the basis for search, aggregation, sort, and result display. This object is available in API version 58.0 and later.
SearchResultActionConfig: Represents a collection of fields to set up the actions that a user can perform on results returned by criteria-based search. This object is available in API version 59.0 and later.
TimelineObjectDefinition: Stores timeline configurations. This object is available in API version 55.0 and later.
