Represents an interaction between a patient and one or more healthcare providers for the purpose of providing the patient with healthcare services or assessing a patient’s health status.
This packaged object has a standard object counterpart in the Clinical Data Model. We recommend using the standard object because it’s more closely aligned with FHIR v4.0.
Fields
Account__c
Type: reference
Properties: Create, Filter, Group, Sort, Update
Description: The person account that represents the patient in Lightning Platform.
Description: The system-defined code that represents the source from which the patient was admitted. Examples of sources include physician referral and transfer.
Description: The human-readable label that represents the source from which the patient was admitted. Examples of sources include physician referral and transfer.
Description: 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.
Description: The system that defines diet preferences that the patient reports. Diet preferences include medical, cultural, and ethical food preferences to help with catering requirements.
HospitalizeDischargeDiagnosis__c
Type: textarea
Properties: Create, Nillable, Update
Description: 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.
Description: The last day when the specified participant was present during the encounter. Periods can overlap or be subsets of the overall encounters period.
Description: The first day when the specified participant was present during the encounter. Periods can overlap or be subsets of the overall encounters period.
Description: 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.
IsRestricted__c
Type: boolean
Properties: Create, Defaulted on create, Filter, Group, Sort, Update
Description: Indicates whether or not this field has restricted visibility based on sharing rules.
IsVisibleOnPatientCard__c
Type: boolean
Properties: Defaulted on create, Filter, Group
Description: Indicates whether or not this field appears on the patient card.
LastActivityDate
Type: date
Properties: Filter, Group, Nillable, Sort
Description: Whichever of the following is the most recent:
Due date of the most recent event logged against the record.
Due date of the most recently closed task associated with the record.
LastReferencedDate
Type: dateTime
Properties: Filter, Nillable, Sort
Description: The time stamp that indicates when the current user last viewed a related record.
LastViewedDate
Type: dateTime
Properties: Filter, Nillable, Sort
Description: The timestamp for when the current user last viewed this record. If this value is null, it’s possible that this record was referenced (LastReferencedDate) and not viewed.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Location1Text__c
Type: textarea
Properties: Create, Nillable, Update
Description: The complete address of the location where a patient encounter occurs.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Location2Text__c
Type: textarea
Properties: Create, Nillable, Update
Description: The complete address of the location where a patient encounter occurs.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Location3Text__c
Type: textarea
Properties: Create, Nillable, Update
Description: The complete address of the location where a patient encounter occurs.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Location4Text__c
Type: textarea
Properties: Create, Nillable, Update
Description: The complete address of the location where a patient encounter occurs.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Description: 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.
Location5Text__c
Type: textarea
Properties: Create, Nillable, Update
Description: The complete address of the location where a patient encounter occurs.
Description: 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.
Description: 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.
Description: The system that defines the reason why the patient encounter occurs. For admissions, the reason can be used for a coded admission diagnosis.
Description: 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.
Description: 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.
Description: The system that defines the specific type of patient encounter. Examples of types include e-mail consultation, surgical day-care, skilled nursing, and rehabilitation.
Usage
A patient encounter is characterized by the setting in which it occurs. For example, the encounter can be ambulatory, emergency, home health, inpatient, or virtual. An encounter encompasses the lifecycle from pre-admission to discharge (for inpatient encounters). During the encounter the patient can move from practitioner to practitioner and location to location.
j