Salesforce Health Cloud Developer Guide

Health Cloud Developer Guide
Health Cloud Objects
Health Cloud Custom Fields on Standard Objects
Patient Creation
Patient Creation Job Flow in Health Cloud
Create a Custom Apex Class for the Patient Creation Job Flow
Customize the Patient Conversion Process
Override the Health Cloud Job Flows
Add Your Job to the Patient Creation Job Flow
Data Mapping to Health Cloud Objects
Working With Electronic Health Records
Health Cloud Custom Metadata Types
Health Cloud Business API
Health Cloud Empower Components for Communities
PDF

Newer Version Available

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

Data Mapping to Health Cloud Objects

When a patient is converted, Health Cloud copies patient data from CandidatePatient__c to the corresponding Account, Contact, and Case (CarePlan record type) objects. A mapping defines how patient data maps to the fields in the destination Salesforce objects. This mapping is specified in the JobFlowDataMapping__mdt custom metadata object.

These mappings can’t be changed or deleted. To change the mappings in your org, create another mapping group and specify in the Health Cloud Settings to use that mapping group instead of the default mappings.

Salesforce uses the MedicalRecordNumber__c and SourceSystem__c fields to check for duplicate patient records during the patient creation process. You can create a validation rule to verify that all candidate patient records have values in these fields before converting patient records.

Note

Table 1. JobFlowDataMapping__mdt
MappingGroupName SourceObject SourceField TargetObject TargetField
defaultPatientCreate CandidatePatient__c Name__c Account Name
defaultPatientCreate CandidatePatient__c MedicalRecordNumber__c Account MedicalRecordNumber__c
defaultPatientCreate null Health Cloud Care Plan1 Care Plan2 Subject
defaultPatientCreate CandidatePatient__c MedicalRecordNumber__c Contact MedicalRecordNumber__c
defaultPatientCreate CandidatePatient__c Address1Line1__c Contact MailingStreet
defaultPatientCreate CandidatePatient__c GivenName1__c Contact FirstName
defaultPatientCreate CandidatePatient__c FamilyName1__c Contact LastName
defaultPatientCreate CandidatePatient__c BirthDate__c Contact Birthdate
defaultPatientCreate CandidatePatient__c Address1City__c Contact MailingCity
defaultPatientCreate CandidatePatient__c Address1Country__c Contact MailingCountry
defaultPatientCreate CandidatePatient__c Telecom1Value__c Contact Phone
defaultPatientCreate CandidatePatient__c Address1PostalCode__c Contact MailingPostalCode

1 Because the source object for this record is null, Health Cloud Care Plan is a string literal and not a field name. This string value is applied to the target field, Subject.

2 Care Plan is a string literal that corresponds to the object that represents a care plan, namely a Case whose record type is CarePlan.

The following is a description of the fields in the JobFlowDataMapping__mdt custom metadata type that’s used for mapping.

Mapping Group Name
The name of a mapping group, which represents a set of field mappings. The patient creation job flow uses only one mapping group named defaultPatientCreate.
Source Object
The API name of the sObject from which data is copied to the target object.
Source Field
The API name of the field that is copied to the target object.
Target Object
The API name of the sObject to copy the data to.
Target Field
The API name of the field to copy the data to.
Active
Indicates whether the job is used (true) or not (false).

Mapping Extra Fields

You can add new field mappings by inserting a record in the JobFlowDataMapping__mdt custom metadata object for each new mapping. Custom mappings can be changed and removed.

To add a mapping in the user interface:

  1. From Setup, enter Custom Metadata Types in the Quick Find box, then select Custom Metadata Types.
  2. Click Job Flow Data Mapping, then click Manage Job Flow Data Mappings.
  3. Click New, and fill out the information for the new mapping.
  4. Click Save.

You can also deactivate the delivered JobFlowDataMapping__mdt and use your own custom set of mappings when you create and activate a new record with the same setting name and setting value.

Note