---
schema_version: "1"
id: 0257d9a4d6b53143740c24ed5dda2a991ffd2b9c0361c1183392a72b4eff9263
title: ContactPoint
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/health_cloud_object_reference/map_fhir_ContactPoint.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.health_cloud_object_reference.meta/health_cloud_object_reference/map_fhir_ContactPoint.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 4f257814d2c592ecaa0a55e77ba452e0dac544fb8d564d644da2357770039803
description: The ContactPoint FHIR resource maps to the Contact​Point​Phone​ object in Salesforce.
---
# ContactPoint

The ContactPoint FHIR resource maps to the Contact​Point​Phone​ object in Salesforce.

## FHIR V4.0 - Clinical Data Model Mapping

Here’s how the fields defined by FHIR for [ContactPoint](https://www.hl7.org/fhir/datatypes.html#ContactPoint) map to the fields in Salesforce.

Table 1. ContactPoint - Salesforce
| Contact Point Resource | Salesforce Field | ​Type | Salesforce Cardinality | Notes |
| --- | --- | --- | --- | --- |
| system | Contact​Point​Phone​.Phone​Type | Picklist | 0.1 | While FHIR defines contact​Point​​.system as a reference to a code set bundle, the Salesforce implementation is a picklist. |
| value | Contact​Point​Phone​.Telephone​Number | Phone | 0.1 | While FHIR defines contact​Point​​.value as a string, Contact​Point​Phone​.Telephone​Number is a phone data type. |
| value | Contact​Point​Phone​.Area​Code | String | 0.1 | N/A |
| value | Contact​Point​Phone​.Extension​Number | String | 0.1 | N/A |
| value | Contact.​Email | ​Email | 0.1 | While FHIR defines contact​Point​​.value as a string, Contact.​Email is an email data type. |
| use | Contact​Point​Phone​.Usage​Type | Picklist | 0.1 | While FHIR defines contact​Point​​.use as a code, the Salesforce implementation is a picklist. |
| use | Contact​Point​Email​.Usage​Type | Picklist | 0.1 | While FHIR defines contact​Point​​.use as a code, the Salesforce implementation is a picklist. |
| rank | Contact​Point​Phone​.Preference​Rank | Double | 0.1 | N/A |
| rank | Contact​Point​Email​.Preference​Rank | Double | 0.1 | N/A |
| period | Contact​Point​Phone​.Active​From​Date​ | ​Date​ | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates. |
| period | Contact​Point​Phone​.Active​To​​Date​ | ​Date​ | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates. |
| period | Contact​Point​Email​.Active​From​Date​ | ​Date​ | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates. |
| period | Contact​Point​Email​.Active​To​​Date​ | ​Date​ | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contact​Point​​.period is flattened to a set of from and to dates. |