Account__c | The person account that represents the patient in Lightning Platform. | ClinicalEncounter.PatientId | N/A |
Class__c | The classification of the encounter. Examples include inpatient, outpatient, ambulatory, and emergency. | ClinicalEncounter.Category | N/A |
Encounter__c | The name of the interaction during which services are provided to the patient. Lookup to EhrEncounter__c. | ClinicalEncounter.RelatedClinicalEncounterId | N/A |
HospitalizeAdmitSourceCode__c | The system-defined code that represents the source from which the patient was admitted. Examples of sources include physician referral and transfer. | ClinicalEncounter.AdmissionSource | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalAdmitSourceLabel__c | The human-readable label that represents the source from which the patient was admitted. Examples of sources include physician referral and transfer. | ClinicalEncounter.AdmissionSource | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeAdmitSourceSystem__c | The system that defines the source from which the patient was admitted. Examples of sources include physician referral and transfer. | ClinicalEncounter.AdmissionSource | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeDestination__c | The location to which the patient is discharged. | ClinicalEncounter.DestinationFacilityId, | The Clinical data model implementations supports references to both HealthcareFacility and Account for this value. |
HospitalizeDestination__c | The location to which the patient is discharged. | ClinicalEncounter.DestinationOrganizationId | The Clinical data model implementations supports references to both HealthcareFacility and Account for this value. |
HospitalizeDietCode__c | The system-defined code that represents diet preferences that the patient reports. | ClinicalEncounter.DietPreference | While the EHR data modal defines this information as a code, the Clinical data model implementation is a multi-select picklist. |
HospitalizeDietLabel__c | The human-readable label that represents diet preferences that the patient reports. Diet preferences include medical, cultural, and ethical food preferences to help with catering requirements. | ClinicalEncounter.DietPreference | While the EHR data modal defines this information as a code, the Clinical data model implementation is a multi-select picklist. |
HospitalizeDietSystem__c | The system that defines diet preferences that the patient reports. Diet preferences include medical, cultural, and ethical food preferences to help with catering requirements. | ClinicalEncounter.DietPreference | While the EHR data modal defines this information as a code, the Clinical data model implementation is a multi-select picklist. |
HospitalizeDischargeDiagnosis__c | A long text description of the final diagnosis that a patient receives before release from the hospital after all testing, surgery, and workup are completed. | Not supported | N/A |
HospitalizeDischargeDispositionCode__c | The system-defined code that represents the category or kind of patient location after discharge. | ClinicalEncounter.DischargeDispositionId | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeDischargeDispositionLabel__c | The human-readable label that represents the category or kind of patient location after discharge. | ClinicalEncounter.DischargeDispositionId | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeDischargeDispositionSystem__c | The system that defines the category or kind of patient location after discharge. | ClinicalEncounter.DischargeDispositionId | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeOrigin__c | The location from which the patient came before admission. | ClinicalEncounter.PreviousFacilityId | The Clinical data model implementations supports references to both HealthcareFacility and Account for this value. |
HospitalizeOrigin__c | The location from which the patient came before admission. | ClinicalEncounter.PreviousOrganizationId | The Clinical data model implementations supports references to both HealthcareFacility and Account for this value. |
HospitalizePeriodEnd__c | The last day when the specified participant was present during the encounter. Periods can overlap or be subsets of the overall encounters period. | ClinicalEncounter.EndDate | N/A |
HospitalizePeriodStart__c | The first day when the specified participant was present during the encounter. Periods can overlap or be subsets of the overall encounters period. | ClinicalEncounter.StartDate | N/A |
HospitalizePreAdmissionId__c | An identifier for hospitalization pre-admission. | ClinicalEncounterIdentifier | Identifier values are represented as child records in ClinicalEncounterIdentifier that reference the ClinicalEncounter record as the parent record. |
HospitalizeReadmission__c | Whether this hospitalization is a readmission (true) or not (false). The default checkbox value is deselected. | ClinicalEncounter.ReadmissionCodeId | N/A |
HospitalizeSpecialArrangementCode__c | The system-defined code that represents special arrangements such as a wheelchair, translator, or stretcher. | Not supported | N/A |
HospitalizeSpecialArrangementLabel__c | The human-readable label that represents special arrangements such as a wheelchair, translator, or stretcher. | Not supported | N/A |
HospitalizeSpecialArrangementSystem__c | The system that defines special arrangements such as a wheelchair, translator, or stretcher. | Not supported | N/A |
HospitalizeSpecialCourtesyCode__c | The system-defined code that represents a special courtesy such as a courtesy that’s extended to a board member or VIP. | ClinicalEncounter.SpecialCourtesy | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeSpecialCourtesyLabel__c | The human-readable label that represents a special courtesy such as a courtesy that’s extended to a board member or VIP. | ClinicalEncounter.SpecialCourtesy | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
HospitalizeSpecialCourtesySystem__c | The system that defines a special courtesy such as a courtesy that’s extended to a board member or VIP. | ClinicalEncounter.SpecialCourtesy | While the EHR data modal defines this information as a code, the Clinical data model implementation is a picklist. |
Indication__c | The reason that the encounter occurs, as specified by using information from another resource. For admissions, this is the admission diagnosis. Typically the indication is a condition or a procedure. | Not supported | N/A |
IsRestricted__c | Indicates whether or not this field has restricted visibility based on sharing rules. | Not supported | N/A |
IsVisibleOnPatientCard__c | Indicates whether or not this field appears on the patient card. | Not supported | N/A |
LengthUnit__c | A unit of measurement of time that the encounter lasted, excluding the time during leaves of absence. | ClinicalEncounter.DurationUnitId | N/A |
LengthValue__c | The length of time that the encounter lasted, excluding the time during leaves of absence. | ClinicalEncounter.Duration | N/A |
Location{1-5}City__c | The city where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Country__c | The country where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Description__c | The description of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}EndDate__c | The last date when this location is valid as a patient encounter location. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Id__c | An external identifier for the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Line1__c | The first line in the address of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Line2__c | The second line in the address of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Name__c | The name of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}PostalCode__c | The postal code in the address of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}StartDate__c | The first date when the location is valid as the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}State__c | The state in the address of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TelecomPeriodEnd__c | The last date when a contact detail is valid for this location. Communication devices available at the location can include phone numbers, fax numbers, mobile numbers, email addresses, and websites. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TelecomPeriodStart__c | The first date when a contact detail is valid for this location. Communication devices available at the location can include phone numbers, fax numbers, mobile numbers, email addresses, and websites. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TelecomSystem__c | The system that defines a contact detail for this location. Communication devices available at the location can include phone numbers, fax numbers, mobile numbers, email addresses, and websites. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TelecomUse__c | Details such as home, office, or mobile related to contact information for this location. Communication devices available at the location can include phone numbers, fax numbers, mobile numbers, email addresses, and websites. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TelecomValue__c | The contact detail such as a phone number for this location. Communication devices available at the location can include phone numbers, fax numbers, mobile numbers, email addresses, and websites. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Text__c | The complete address of the location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TypeCode__c | The system-defined code that represents the type of location where the patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TypeLabel__c | The human-readable label that represents the type of location where the patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}TypeSystem__c | The system that defines the type of location where the patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Type__c | The type of location where the patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Location{1-5}Use__c | Details such as home or office related to a location where a patient encounter occurs. | HealthcareFacility | Location values are supported with child records in the ClinicalEncounterFacility object that connect an encounter with its locations. While the EHR data model could only support five locations for each encounter, the Clinical data model can support a much higher number locations. |
Name | The EHR encounter ID. Limit: 255 characters. | ClinicalEncounterIdentifier | Identifier values are represented as child records in ClinicalEncounterIdentifier that reference the ClinicalEncounter record as the parent record. |
Patient__c | The patient’s name. Lookup to EhrPatient__c. | ClinicalEncounter.PatientId | N/A |
PeriodEnd__c | The last date and time when the period is valid for this patient encounter. | ClinicalEncounter.EndDate | N/A |
PeriodStart__c | The first date and time when the period is valid for this patient encounter. | ClinicalEncounter.StartDate | N/A |
PriorityCode__c | The system-defined code that represents the urgency of the patient encounter. | ClinicalEncounter.PriorityId | This code value is specified as a reference to a code set bundle record. |
PriorityLabel__c | The human-readable label that represents the urgency of the patient encounter. | ClinicalEncounter.PriorityId | This code value is specified as a reference to a code set bundle record. |
PrioritySystem__c | The system that defines the urgency of the patient encounter. | ClinicalEncounter.PriorityId | This code value is specified as a reference to a code set bundle record. |
Priority__c | An indication of the urgency of the patient encounter. Examples include immediate, emergency, urgent, semi-urgent, and non-urgent. | ClinicalEncounter.PriorityId | This code value is specified as a reference to a code set bundle record. |
ReasonCode__c | The system-defined code that represents the reason why the patient encounter occurs. For admissions, the reason can be used for a coded admission diagnosis. | ClinicalEncounterReason.ReasonCodeId | This code value is specified as a reference to a code set bundle record. |
ReasonLabel__c | The human-readable label that represents the reason why the patient encounter occurs. For admissions, the reason can be used for a coded admission diagnosis. | ClinicalEncounterReason.ReasonCodeId | This code value is specified as a reference to a code set bundle record. |
ReasonSystem__c | The system that defines the reason why the patient encounter occurs. For admissions, the reason can be used for a coded admission diagnosis. | ClinicalEncounterReason.ReasonCodeId | This code value is specified as a reference to a code set bundle record. |
Status__c | An indication of the status of the patient encounter. Examples include planned, arrived, in-progress, onleave, finished, and cancelled. | ClinicalEncounter.Status | N/A |
TypeCode__c | The system-defined code that represents the specific type of patient encounter. Examples of types include e-mail consultation, surgical day-care, skilled nursing, and rehabilitation. | ClinicalEncounter.TypeId | This code value is specified as a reference to a code set bundle record. |
TypeLabel__c | The human-readable label that represents the specific type of patient encounter. Examples of types include e-mail consultation, surgical day-care, skilled nursing, and rehabilitation. | ClinicalEncounter.TypeId | This code value is specified as a reference to a code set bundle record. |
TypeSystem__c | The system that defines the specific type of patient encounter. Examples of types include e-mail consultation, surgical day-care, skilled nursing, and rehabilitation. | ClinicalEncounter.TypeId | This code value is specified as a reference to a code set bundle record. |
j