Agentforce Health Developer Guide

Agentforce Health Developer Guide
Health Cloud Data Model
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Health 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
CRDMetricData
Device
DiagnosticReport
Document​Reference
Dosage
DTRMetricData
DTRQuestionnaireResponse
DTRStdQuestionnaire
Encounter
EpisodeOfCare
​Flag
Goal
Human​Name
Identifier
​Immunization
InformationOrigin
Location
​Medication
​Medication​​Request
Medication​Statement
​Observation
Organization
PASClaim
PASClaimResponse
PASMetricData
Patient
Practitioner
PractitionerRole
​Procedure
RelatedPerson
ResearchStudy
Service​Request
Subscription
SubscriptionTopic
Timing
Store HL7 v2.3 Messages in Salesforce Standard Objects
Emergency Response Management
Apex Reference
Health Cloud Business APIs
Health Cloud Tooling API Objects
Health Cloud Standard Invocable Actions
Metadata Types
Health Cloud FHIR APIs
MuleSoft Direct Integrations
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.

​Flag

The ​Flag ​FHI​R resource maps to the Clinical​Alert object in Salesforce​.

​FHI​R V4​.0 - Clinical ​Data ​Model ​Mapping

Here’s how the fields defined by ​FHI​R for ​Flag map to the fields in Salesforce​.

Table 1. ​Flag - Salesforce
​Flag ​Resource Salesforce ​Field Type Salesforce Cardinality Notes
identifier Identifier Object 0​.​M The identifier information for a clinical alert is represented as Identifier records that reference the clinical alert record using their Identifier​.​Parent​RecordId field​.
status Clinical​Alert​.Status ​Picklist 0​.1 While ​FHI​R defines ​Flag​.status as a code, the Salesforce implementation of Clinical​Alert​.Status is picklist​.
category Clinical​Alert​.Categories ​Multi-Select ​Picklist 0​.​M While ​FHI​R defines ​Flag​.category as a code set bundle, the Salesforce implementation of Clinical​Alert​.Categories is a multi-select picklist​.
code Clinical​Alert​.CodeId Lookup: CodeSet​Bundle 1​.1 While ​FHI​R defines ​Flag​.code as a code set bundle only, the Salesforce implementation flattens it into Clinical​Alert​.Code and Clinical​Alert​.Code​Description​. The latter is meant to display non-coded information to users as required​.
Clinical​Alert​.Code​Description String 0​.1
subject Clinical​Alert​.Subject ​Polymorphic Lookup: Location, ​Account Healthcare​Provider, ​Medication, and ​Patient​Medical​Procedure 1​.1 The Salesforce implementation of flag​.subject doesn’t support plan definitions​.
period Clinical​Alert​.Start​Date ​Date Time 0​.1 In Salesforce’s implementation, ​Flag​.period is split into two fields, Clinical​Alert​.Start​Date and Clinical​Alert​.​End​Date​.
Clinical​Alert​.​End​Date ​Date Time 0​.1
encounter Clinical​Alert​.​Related​EncounterId Lookup: Clinical​Encounter 0​.1 N/​A
author Clinical​Alert​.​Raised​ById ​Polymorphic Lookup: Healthcare​Provider, Care​Registered​Device, and Healthcare​Practitioner​Facility 0​.1 The Salesforce implementation of flag​.author doesn’t support patients, and organizations​.