Agentforce Life Sciences Developer Guide

Agentforce Life Sciences Developer Guide
Life Sciences Cloud Data Models
Life Sciences Cloud Standard Objects
Life Sciences Cloud Associated Objects
Life Sciences Cloud Fields on Standard Objects
StandardValueSet Names and Standard Picklist Fields
Life Sciences Cloud Platform Events
Working With Electronic Health Records
Mapping FHIR v4.0 to Salesforce Standard Objects
Considerations for Integration
Address
AdverseEvent
Allergy​Intolerance
Annotation
Attachment
Care​Plan
Codeable​Concept
Coding
CommunicationRequest
Condition
ContactPoint
Device
DiagnosticReport
Document​Reference
Dosage
Encounter
EpisodeOfCare
​Flag
Goal
Human​Name
Identifier
​Immunization
InformationOrigin
Location
​Medication
​Medication​​Request
Medication​Statement
​Observation
Organization
Patient
Practitioner
PractitionerRole
​Procedure
RelatedPerson
ResearchStudy
Service​Request
Timing
Store HL7 v2.3 Messages in Salesforce Standard Objects
Life Sciences Cloud Business APIs
Apex Reference
Life Sciences Cloud Standard Invocable Actions
Life Sciences Cloud Tooling API Objects
Life Sciences Cloud Metadata Types
API End-of-Life Policy
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

ContactPoint

The ContactPoint FHIR resource maps to the Contact​Point​Phone​ object in Salesforce.

FHIR V4.0 - Clinical Data Model Mapping

Here’s how the fields defined by FHIR for ContactPoint map to the fields in Salesforce.

Table 1. ContactPoint - Salesforce
Contact Point Resource Salesforce Field ​Type Salesforce Cardinality Notes
system Contact​Point​Phone​.Phone​Type Picklist 0.1 While FHIR defines contact​Point​​.system as a reference to a code set bundle, the Salesforce implementation is a picklist.
value Contact​Point​Phone​.Telephone​Number Phone 0.1 While FHIR defines contact​Point​​.value as a string, Contact​Point​Phone​.Telephone​Number is a phone data type.
Contact​Point​Phone​.Area​Code String 0.1 N/A
Contact​Point​Phone​.Extension​Number String 0.1 N/A
Contact.​Email ​Email 0.1 While FHIR defines contact​Point​​.value as a string, Contact.​Email is an email data type.
use Contact​Point​Phone​.Usage​Type Picklist 0.1 While FHIR defines contact​Point​​.use as a code, the Salesforce implementation is a picklist.
Contact​Point​Email​.Usage​Type Picklist 0.1
rank Contact​Point​Phone​.Preference​Rank Double 0.1 N/A
Contact​Point​Email​.Preference​Rank Double 0.1 N/A
period Contact​Point​Phone​.Active​From​Date​ ​Date​ 0.1 Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates.
Contact​Point​Phone​.Active​To​​Date​ ​Date​ 0.1
Contact​Point​Email​.Active​From​Date​ ​Date​ 0.1 Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates.
Contact​Point​Email​.Active​To​​Date​ ​Date​ 0.1