system | ContactPointPhone.PhoneType | Picklist | 0.1 | While FHIR defines contactPoint.system as a reference to a code set bundle, the Salesforce implementation is a picklist. |
value | ContactPointPhone.TelephoneNumber | Phone | 0.1 | While FHIR defines contactPoint.value as a string, ContactPointPhone.TelephoneNumber is a phone data type. |
value | ContactPointPhone.AreaCode | String | 0.1 | N/A |
value | ContactPointPhone.ExtensionNumber | String | 0.1 | N/A |
value | Contact.Email | Email | 0.1 | While FHIR defines contactPoint.value as a string, Contact.Email is an email data type. |
use | ContactPointPhone.UsageType | Picklist | 0.1 | While FHIR defines contactPoint.use as a code, the Salesforce implementation is a picklist. |
use | ContactPointEmail.UsageType | Picklist | 0.1 | While FHIR defines contactPoint.use as a code, the Salesforce implementation is a picklist. |
rank | ContactPointPhone.PreferenceRank | Double | 0.1 | N/A |
rank | ContactPointEmail.PreferenceRank | Double | 0.1 | N/A |
period | ContactPointPhone.ActiveFromDate | Date | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contactPoint.period is flattened to a set of from and to dates. |
period | ContactPointPhone.ActiveToDate | Date | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contactPoint.period is flattened to a set of from and to dates. |
period | ContactPointEmail.ActiveFromDate | Date | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contactPoint.period is flattened to a set of from and to dates. |
period | ContactPointEmail.ActiveToDate | Date | 0.1 | Because Salesforce doesn’t support a native period data type, the Salesforce implementation of contactPoint.period is flattened to a set of from and to dates. |
j