Salesforce Health Cloud Developer Guide

Health Cloud Developer Guide
Health Cloud Data Model
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Patient Creation
Creating and Importing Documents
Intelligent Appointment Management
Code Sets and Code Set Bundles
Working With Electronic Health Records
Mapping FHIR v4.0 to Salesforce Standard Objects
Considerations for Integration
Address
Allergy​Intolerance
Annotation
Attachment
Codeable​Concept
Coding
Condition
ContactPoint
Device
DiagnosticReport
Document​Reference
Dosage
Encounter
​Flag
Human​Name
Identifier
​Immunization
Location
​Medication
​Medication​​Request
Medication​Statement
​Observation
Organization
Patient
Practitioner
PractitionerRole
​Procedure
RelatedPerson
Service​Request
Timing
Store HL7 v2.3 Messages in Salesforce Standard Objects
Storing HL7 Admission, Discharge, Transfer (ADT) Data in the Packaged EHR Data Model
Storing HL7 Clinical Document Architecture (CDA) Data in the Packaged EHR Data Model
Storing HL7 Observation Results (ORU) Data in the Packaged EHR Data Model
Storing FHIR Data in the Packaged EHR Data Model
Emergency Response Management
Health Cloud Business APIs
Health Cloud Metadata APIs
Health Cloud Custom Metadata Types
Health Cloud Empower Components for Experience Cloud Sites
PDF

Newer Version Available

This content describes an older version of this product. View Latest

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. Health Cloud’s 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.