Salesforce Health Cloud Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Health Cloud Developer Guide
Health Cloud Data Model
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
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
API End-of-Life Policy
PDF

Medication​Statement

The medication​Statement FHIR resource maps to the Medication​Statement object in Salesforce​.

FHIR V4​.0 - Clinical Data Model Mapping

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

Table 1. Medication​Statement - Salesforce
Medication ​Statement ​Resource Salesforce Field Type Salesforce Cardinality Notes
identifier Identifier Object 0​.M The identifier information for a medication statement is represented as Identifier records that reference the Medication​Statement record using their Identifier​.Parent​RecordId field​.
basedOn Medication​Statement​.Medication​RequestId Lookup: Medication​Request 0​.1

While FHIR defines medication​Statement​.basedOn as a zero-to-many resource, the Salesforce implementation of Medication​Statement​.Medication​RequestId is zero-to-one​.

The Salesforce implementation doesn’t support references to care plan or service request records​.
partOf Medication​Statement​.Parent​Medication​Statement​Id Lookup: Medication​Statement 0​.1

The Salesforce implementation of medication​Request​.partOf is flattened into three separate references​.

​References to medication administration and medication dispense records are not supported​.

While FHIR defines medication​Statement​.partOf as a zero-to-many resource, the Salesforce implementation is zero-to-one for each of the flattened fields​.
Medication​Statement​.ProcedureId Lookup: Patient​Medical​Procedure 0​.1
Medication​Statement​.Care​Observation​Id Lookup: Care​Observation 0​.1
status Medication​Statement​.​Status Picklist 1​.1 While FHIR defines Medication​Statement​.status as a code set bundle, the Salesforce implementation of Medication​Statement​.​Status is picklist​.
status​Reason Medication​Statement​.​Status​Reason​CodeId Lookup: ​CodeSet​Bundle 0​.1 N/A
category Medication​Statement​.Delivery​Setting Picklist 0​.1 While FHIR defines Medication​Statement​.category as a code set bundle, the Salesforce implementation is a picklist​.
medication​.medication​Codeable​Concept Medication​Statement​.Medication​CodeId Lookup: ​CodeSet​Bundle 0​.1 While the individual fields Medication​Statement​.Medication​CodeId and Medication​Statement​.MedicationId are zero-to-one references, the set {Medication​Statement​.Medication​CodeId, Medication​Statement​.MedicationId} is a one-to-one resource​.
medication​.medication​Reference Medication​Statement​.MedicationId Lookup: Medication 0​.1
subject Medication​Statement​.PatientId Master-Detail ​Reference: Account 1​.1 Only references to patients are supported​.
context Medication​Statement​.Clinical​EncounterId Lookup: Clinical​Encounter 0​.1 Only references to encounters are supported​.
effective​.effective​Date​Time Medication​Statement​.Start​Date​Time DateTime 0​.1 The Medication​Statement​.Start​Date​Time field is used as both the Salesforce counterpart for medication​Statement​.effective​.effective​Date​Time and the start date field for medication​Statement​.effective​.effective​Period​.
effective​.effective​Period Medication​Statement​.Start​Date​Time Date​Time 0​.1 Because Salesforce doesn’t support a native period data type, the implementation of medication​Statement​.effective​.effective​Period is flattened into a set of start and end dates​.
Medication​Statement​.End​Date​Time Date​Time 0​.1
date​Asserted Medication​Statement​.Assertion​Date​Time Date​Time 0​.1 N/A
information​Source Medication​Statement​.​Statement​SourceId Polymorphic Lookup: Account, Healthcare​Provider 0​.1 N/A
derived​From N/A N/A N/A Not supported
reason​Code Medication​Statement​.Medication​Reason​CodeId Lookup: ​CodeSet​Bundle 0​.1 While FHIR defines Medication​Statement​.reason​Code as a zero-to-many resource, the Salesforce implementation is zero-to-one​.
reason​Reference Medication​Statement​.Medication​ReasonId Polymorphic Lookup: Health​Condition, Care​Observation 0​.1

While FHIR defines Medication​Statement​.reason​Reference as a zero-to-many resource, the Salesforce implementation is zero-to-one​.

Only references to condition and observation records are supported​.
note N/A N/A N/A Not supported
dosage Patient​Medication​Dosage Object 0​.M The dosage information for a medication statement is represented as Patient​Medication​Dosage records that reference the Medication​Statement record using their Patient​Medication​Dosage​.Parent​RecordId field​.