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.

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​.

FHIR V4​.0 - Clinical ​Data Model Mapping

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

Table 1. RelatedPerson - Salesforce
RelatedPerson Resource Salesforce Field Type Salesforce Cardinality Notes
identifier Identifier Object 0​.M The identifier information for a related person is represented as Identifier records that reference the related person’s person account using their Identifier​.Parent​RecordId field​.
active Account​.IsActive Boolean 0​.1 N/A
patient Contact​Contact​Relation__c​.Contact__c Lookup: Contact 1.1 Though Salesforce can tehnically accommodate patient as a zero-to-many association, it is recommended to align with the FHIR defined one-to-one association.
relationship Contact​​Contact​​Relation__c​​.Role__c Lookup: ReciprocalRole__c 0​.M While FHIR defines relatedPerson​.relationship as a code set bundle, its Salesforce implementation is a reference to ReicprocalRole__c​.
name Person​Name Object 0​.M The name information for a related person is represented as Person​Name records that reference the related person’s person account using their Person​Name​.Parent​RecordId field​.
telecom Contact​Point​Phone Object 0​.M The telecom information for a related person is represented as Contact​Point​Phone records that reference the related person’s person account using their Contact​Point​Phone​.ParentId field​.
gender Contact​.Gender Picklist 0​.1 While FHIR defines relatedPerson​.gender as a code set, its Salesforce implementation is a picklist​.
birth​Date Contact​.Birthdate ​Date 0​.1 N/A
address Contact​Point​Address Object 0​.M The address information for a related person is represented as Contact​Point​Address records that reference the related person’s person account using their Contact​Point​Address​.ParentId field​.
photo N/A N/A N/A Not supported
period Contact​​Contact​​Relation__c​​.StartDate__c ​Date 0​.1 Because Salesforce doesn’t support a native period data type, the relatedPerson.period FHIR resource is flattened to a set of strart and end dates​.
Contact​​Contact​​Relation__c​​.EndDate__c ​Date 0​.1
communication Person​Language Object 0​.M The language information for a related person is represented as Person​Language records that reference the related person’s person account using their Person​Language​.IndividualId field​.
communication​.language Person​Language​.​Language Picklist 0​.1 While FHIR defines relatedPerson​.communication​.language as a code set bundle, its Salesforce implementation is a picklist​.
communication​.preferred Person​Language​.Rank Double 0​.1 While FHIR defines relatedPerson​.communication​.preferred as a boolean, its Salesforce implementation is an integer field that ranks the degree of preference​.