HumanName
The HumanName FHIR resource maps to the PersonName object in Salesforce.
FHIR V4.0 - Clinical Data Model Mapping
Here’s how the fields defined by FHIR for HumanName map to the fields in Salesforce.
| HumanName Resource | Salesforce Field | Type | Salesforce Cardinality | Notes |
|---|
family | PersonName.LastName | String | 0.1 | In cases where a person has a middle name, PersonName.LastName is supposed to store a combination of the middle name and the last name. |
Given | PersonName.FirstName | String | 0.1 | While the cardinality defined by FHIR for HumanName.Given is zero-to-many, the Salesforce implementation in PersonName.FirstName is zero-to-one. |
text | PersonName.FullName | String | 0.1 | N/A |
use | PersonName.NameUsageType | Dynamic picklist | 0.1 | While FHIR defines HumanName.use as a code, Salesforce implements PersonName.NameUsageType as a dynamic picklist. |
prefix | PersonName.Prefix | String | 0.1 | While the cardinality defined by FHIR for HumanName.prefix is zero-to-many, the Salesforce implementation in PersonName.Prefix is zero-to-one. |
suffix | PersonName.Suffix | String | 0.1 | While the cardinality defined by FHIR for HumanName.suffix is zero-to-many, the Salesforce implementation in PersonName.Suffix is zero-to-one. |
period | PersonName.EffectiveDate | Date Time | 0.1 | In Salesforce’s implementation, HumanName.period is split into two fields, PersonName.EffectiveDate and PersonName.EndDate. |
period | PersonName.EndDate | Date Time | 0.1 | In Salesforce’s implementation, HumanName.period is split into two fields, PersonName.EffectiveDate and PersonName.EndDate. |
See Also
j