Organization

The Organization FHIR resource maps primarily to the Account object in Salesforce​.

FHIR V4​.0 - Clinical ​Data Model Mapping 

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

Organization ResourceSalesforce FieldTypeSalesforce CardinalityNotes
identifierIdentifierObject0​.MThe identifier information for an organization is represented as Identifier records that reference the organization record using their Identifier​.Parent​RecordId field​.
activeAccount​.IsActiveBoolean0​.1N/A
typeAccount​.TypePicklist0.1While FHIR defines account​.type as a zero-to-many code set bundle reference, its Salesforce implementation is a zero-to-one picklist​.
nameAccount​.NameString0​.1N/A
aliasN/AN/AN/ANot supported
telecomContact​Point​PhoneObject0​.MThe telecom information for an organization is represented as Contact​Point​Phone records that reference the organization record using their Contact​Point​Phone​.ParentId field​.
addressContact​Point​AddressObject0​.MThe address information for an organization is represented as Contact​Point​Address records that reference the organization record using their Contact​Point​Address​.ParentId field​.
contactAccount​Contact​Relation​.ContactIdLookup: Contact0​.MContacts are connected to organizations using the Account​Contact​Relation junction object​. The Account​Contact​Relation​.AccountId field references the organization’s account record, and the Account​Contact​Relation​.ContactId field references the contact record of the contact’s person account​.
contact​.relationshipAccount​Contact​Relation​.RolesMulti-Select picklist0​.MWhile FHIR defines organization​.contact​.purpose as a code set bundle, its Salesforce implementation is a picklist​.
contact​.namePerson​NameObject0​.MThe name information for a contact is represented as Person​Name records that reference the contact’s person account using their Person​Name​.Parent​RecordId field​.
While FHIR defines patient​.contact​.name as a zero-to-one resource, the Salesforce implementation can support zero-to-many references​.
contact​.telecomContact​Point​PhoneObject0​.MThe telecom information for a contact is represented as Contact​Point​Phone records that reference the contact’s person account record using their Contact​Point​Phone​.ParentId field​.
contact​.addressContact​Point​AddressObject0​.MThe address information for a contact is represented as Contact​Point​Address records that reference the contact’s person account record using their Contact​Point​Address​.ParentId field​.
While FHIR defines patient​.contact​.address as a zero-to-one resource, the Salesforce implementation can support zero-to-many references​.
contact​.endPointN/AN/AN/ANot supported