EhrPractitioner__c to PersonAccount and HealthcareProvider and PersonAccount

Fields in EhrPractitioner__c map to Person Accounts and HealthcareProvider in the Clinical data model.

Mapping 
FieldDetailsClinical Data Model FieldsNotes
Address​{1-5}​City​__cThe city in a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​Country​__cThe country in a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​EndDate​__cThe last date when an address is valid as a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​Line1​__cThe first line of a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​Line2​__cThe second line of a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​PostalCode​__cThe postal code in a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​StartDate​__cThe first date when an address is valid as a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​State​__cThe state in a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​Text​__cA complete postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Address​{1-5}​Use​__cDetails such as home or office related to a postal address where the practitioner can be found or visited or to which mail can be delivered.Contact​Point​AddressThe address information for a practitioner is represented as Contact​Point​Address records that reference the account record of the practitioner’s person account using the Contact​Point​Address​.ParentId field​. If your Health Cloud implementation models providers as Contacts instead of Person Accounts, then you can’t map addresses to your providers.
Birth​Date​__cThe practitioner’s birth date, needed for identification.Contact​.BirthdateN/A
Communication​{1-5}​Code​__cThe system-defined code that represents a language that the practitioner can use to communicate with the patient about the patient’s health.Person​LanguageThe language information for a practitioner is represented as Person​Language records that reference the practitioner’s person account record using their Person​Language​.IndividualId field​. The EHR data model could store only five languages spoken by a practitioner, while the Clinical data model supports a much higher number.
Communication​{1-5}​Label​__cThe human-readable label that represents a language that the practitioner can use to communicate with the patient about the patient’s health.Person​LanguageThe language information for a practitioner is represented as Person​Language records that reference the practitioner’s person account record using their Person​Language​.IndividualId field​. The EHR data model could store only five languages spoken by a practitioner, while the Clinical data model supports a much higher number.
Communication​{1-5}​System​__cThe system that defines a language that the practitioner can use to communicate with the patient about the patient’s health.Person​LanguageThe language information for a practitioner is represented as Person​Language records that reference the practitioner’s person account record using their Person​Language​.IndividualId field​. The EHR data model could store only five languages spoken by a practitioner, while the Clinical data model supports a much higher number.
Gender​__cThe gender that the practitioner is considered to have for administration and record-keeping purposes, needed to address the practitioner correctly.Contact​.GenderN/A
Given​Name1​__cThe first name in the practitioner’s given name. (Lisa Marie is the given name of Lisa Marie Smith.)Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
Family​Name​{1-3}​​__cThe first name in the practitioner’s family name (Smith in Carol Smith Rodgers Andrews).Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
Name255​__cThe name of the practitioner. Limit: 255 characters.Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
Name​__cThe long text description of the practitioner’s name.Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
Prefix​Name​{1-3}​​__cThe first prefix in the practitioner’s name.Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
Suffix​Name​{1-3}​​__cThe first suffix in the practitioner’s name.Person​NameThe name information for a practitioner is represented as Person​Name records that reference the practitioner’s person account record using their Person​Name​.Parent​RecordId field​.
IsRestricted​__cIndicates whether or not this field has restricted visibility based on sharing rules.Not supportedN/A
IsVisible​OnPatient​Card​__cIndicates whether or not this field appears on the patient card.Not supportedN/A
Location​{1-5}​City​__cThe city associated with a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Country​__cThe country associated with a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Description​__cThe description of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​EndDate​__cThe last date when a location is valid as a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Id​__cAn external identifier for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Line1​__cThe first line in the address of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Line2​__cThe second line in the address of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Name​__cThe name of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Postal​Code​__cThe postal code in the address of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Start​Date​__cThe first date when a location is valid as a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​State​__cThe state in the address of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Telecom​Period​End​__cThe last date when a contact detail is valid for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Telecom​Period​Start​__cThe first date when a contact detail is valid for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Telecom​System​__cThe system that defines a contact detail, such as phone or fax, for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Telecom​Use​__cDetails such as home, office, or mobile related to contact information for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Telecom​Value​__cThe content details, such as the phone number, for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Text​__cThe complete address of a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Type​__cThe location type for a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
Location​{1-5}​Use​__cDetails such as home or office related to a location where the practitioner provides care.Healthcare​Practitioner​Facility​.AccountIdIn the Clinical data model, location details for a practitioner is defined only when creating records for PractitionerRoles in Healthcare​Practitioner​Facility and CareProvider​Facility​Specialty
The Clinical data model implementation references practice locations indirectly. This is done by referencing the local business account of the required facility using the ​Healthcare​Practitioner​Facility​.AccountId field.
The Clinical data model implementation supports only one location reference for each practitioner role.
NameThe EHR practitioner ID. Limit: 255 characters.IdentifierThe identifier information for a practitioner is represented as Identifier records that reference the practitioner’s Healthcare​Provider record using their Identifier​.Parent​RecordId field​.
Organization255​__cThe organization where the practitioner performs the associated roles. Limit: 255 characters.Not supportedNot supported
Organization​__cThe long text description of the organization where the practitioner performs the associated roles.Not supportedNot supported
Period​__cThe period during which the practitioner is authorized to act as a practitioner in these roles for the organization.Healthcare​Practitioner​Facility​.Effective​FromIn the Clinical data model, period details for a practitioner’s role is defined only when creating records for Practitioner​Roles in Healthcare​Practitioner​Facility and Care​Provider​Facility​Specialty
Period​__cThe period during which the practitioner is authorized to act as a practitioner in these roles for the organization.Healthcare​Practitioner​Facility​.Effective​ToIn the Clinical data model, period details for a practitioner’s role is defined only when creating records for Practitioner​Roles in Healthcare​Practitioner​Facility and Care​Provider​Facility​Specialty
PhotoUrl​__cThe URL for a photo of the practitioner.Not supportedN/A
Source​System​__cThe external system of record.Healthcare​Provider​.Source​System​N/A
Source​SystemId​__cThe ID of the record in the source system.Healthcare​Provider​.Source​System​IdentifierN/A
Source​System​Modified​__cThe date and time when the record was last modified in the source system.Healthcare​Provider​.Source​System​ModifiedN/A
Specialty​Code​__cThe system-defined code that represents a specialty of the practitioner’s.Care​Provider​Facility​Specialty​.Specialty​IdThe Clinical data model implementation is a picklist.
Specialty​System​__cThe system that defines a specialty of the practitioner’s.Care​Provider​Facility​Specialty​.Specialty​IdThe Clinical data model implementation is a picklist.
Telecom​{1-5}​Period​End​Date​__cThe last date when a contact detail is valid for the practitioner.Contact​Point​PhoneThe telecom information for a practitioner is represented as Contact​Point​Phone records that reference the practitioner’s person account record using their Contact​Point​Phone​.ParentId field​.
Telecom​{1-5}​Period​Start​Date​__cThe first date when a contact detail is valid for the practitioner.Contact​Point​PhoneThe telecom information for a practitioner is represented as Contact​Point​Phone records that reference the practitioner’s person account record using their Contact​Point​Phone​.ParentId field​.
Telecom​{1-5}​System​__cThe system that defines a contact detail, such as phone or fax, for the practitioner.Contact​Point​PhoneThe telecom information for a practitioner is represented as Contact​Point​Phone records that reference the practitioner’s person account record using their Contact​Point​Phone​.ParentId field​.
Telecom​{1-5}​Use​__cDetails such as home, office, or mobile related to contact information that can be used to contact the practitioner.Contact​Point​PhoneThe telecom information for a practitioner is represented as Contact​Point​Phone records that reference the practitioner’s person account record using their Contact​Point​Phone​.ParentId field​.
Telecom​{1-5}​Value​__cThe content details, such as the phone number, that can be used to contact the practitioner.Contact​Point​PhoneThe telecom information for a practitioner is represented as Contact​Point​Phone records that reference the practitioner’s person account record using their Contact​Point​Phone​.ParentId field​.

Health Cloud Developer Guide
Health Cloud Data Model
Health Cloud Associated Objects
Health Cloud Fields on Standard Objects
Health Cloud Platform Events
Working With Electronic Health Records
Emergency Response Management
Apex Reference
Health Cloud Business APIs
Health Cloud Tooling API Objects
Health Cloud Standard Invocable Actions
Metadata Types
Health Cloud FHIR APIs
MuleSoft Direct Integrations
API End-of-Life Policy
Health Cloud Managed Package
Health Cloud Managed Package Data Model
Care Management (Managed Package)
Claims (Managed Package Feature)
Electronic Health Records (Managed Package)
Mapping the EHR Data Model to the Clinical Data Model
EhrAllergyIntolerance__c to AllergeyIntolerance
EhrCondition__c to HealthCondition
EhrDevice__c to CareRegisteredDevice and Asset
EhrDosageInstruction__c to PatientMedicationDosage
EhrEncounter__c to ClinicalEncounter
EhrEncounterParticipant​__c to ClinicalEncounterProvider
EhrImmunization​__c to PatientImmunization
EhrVaccinationProtocol__c to Patient Immunization
EhrImmunizationReaction​__c to PatientHealthReaction
EhrMedicationPrescription__c to Medication​​Request
EhrMedicationStatement​__c to Medication​Statement
EhrObservation__c to CareObservation
EhrRelatedObservation​__c to CareOberservationComponent
EhrPatient__c to Person Account
EhrPatientCareProvider__c to Contact​Contact​Relation__c​
EhrPatientContact__c to Contact​Contact​Relation__c
EhrPractitioner__c to PersonAccount and HealthcareProvider and PersonAccount
EhrPractitionerQualification__c to BoardCertification
EhrPractitionerRole__c to HealthcarePractitionerFacility
EhrProcedure__c to PatientMedicalProcedure
EhrProcedurePerformer__c to CarePerformer
EhrProcedureRequest__c to ClinicalServiceRequest
EhrAllergyIntolerance__c
EhrCarePlan__c
EhrCarePlanActivity__c
EhrCarePlanConcern__c
EhrCarePlanGoal__c
EhrCarePlanParticipant__c
EhrCondition__c
EhrConditionRelatedItem__c
EhrDevice__c
EhrDosageInstruction__c
EhrEncounter__c
EhrEncounterAccommodation__c
EhrEncounterParticipant__c
EhrImmunization__c
EhrImmunizationReaction__c
EhrMedicationPrescription__c
EhrMedicationStatement__c
EhrObservation__c
EhrPatient__c
EhrPatientCareProvider
EhrPatientContact__c
EhrPractitioner__c
EhrPractitionerIdentity__c
EhrPractitionerQualification__c
EhrPractitionerRole__c
EhrProcedure__c
EhrProcedurePerformer__c
EhrProcedureRequest__c
EhrProgram__c
EhrRelatedObservation__c
EhrRelatedPerson__c
EhrVaccinationProtocol__c
EhrVirtualDevice__c
EhrVirtualDeviceChannel__c
Health Cloud Managed Package to Platform Data Model Mapping
Health Cloud Custom Metadata Types (Managed Package)
Health Cloud Empower Components for Experience Cloud Sites (Managed Package)
Working With Electronic Health Records (Managed Package)
Health Cloud Managed Package Aura Components
Previous Versions