Encounters and Patient Movement
Purpose: To dissect the encounter—the central organizing event in healthcare—and understand how Epic tracks every patient interaction and movement through the system, from outpatient clinics to hospital stays.
The Spine of Clinical Data
Section titled “The Spine of Clinical Data”Every diagnosis, order, and clinical note connects to an encounter. It’s the fundamental organizing principle of the medical record, representing each discrete interaction between a patient and the healthcare system. Epic’s encounter model captures everything from a five-minute telehealth check-in to a month-long hospital stay.
Each row represents a unique patient interaction, identified by the Contact Serial Number (CSN).
Understanding the CSN (Contact Serial Number)
Section titled “Understanding the CSN (Contact Serial Number)”The PAT_ENC_CSN_ID is Epic’s unique identifier for every patient interaction. It serves as the universal foreign key linking all encounter-related data.
The Magic of PAT_ENC_DATE_REAL
Section titled “The Magic of PAT_ENC_DATE_REAL”When multiple encounters occur on the same day, how do you maintain chronological order? Epic’s elegant solution uses decimal sequencing.
The decimal portion (0.00, 0.01, 0.02…) provides unique sequencing for same-day encounters, guaranteeing a correct timeline.
Encounter Types and Settings
Section titled “Encounter Types and Settings”Encounters occur in various settings, which can often be identified by the department name or specific encounter type fields.
Hospital Admissions
Section titled “Hospital Admissions”For inpatient stays, PAT_ENC
and the related PAT_ENC_HSP
table track admission and discharge details.
The ADT Event Trail: Tracking Patient Movement
Section titled “The ADT Event Trail: Tracking Patient Movement”The CLARITY_ADT table provides a detailed audit trail of patient movement (Admission, Discharge, Transfer) within a facility.
Appointment Status Lifecycle
Section titled “Appointment Status Lifecycle”The APPT_STATUS_C_NAME
field tracks the workflow of scheduled appointments.
Note that many encounters (especially non-scheduled or inpatient) may have a NULL status.
Provider Roles in Encounters
Section titled “Provider Roles in Encounters”Epic tracks multiple provider relationships for each encounter.
- Visit Provider: The provider who saw the patient.
- PCP: The patient’s primary care provider at the time of the visit.
- Referring Provider: The provider who sent the patient for the visit.
Building an Encounter Timeline
Section titled “Building an Encounter Timeline”To understand a patient’s care journey, you can construct a chronological timeline of their visits.
Key Takeaways
Section titled “Key Takeaways”- PAT_ENC is the master encounter table, with PAT_ENC_CSN_ID as the unique identifier for every interaction.
- PAT_ENC_DATE_REAL uses decimal sequencing to ensure unique and reliable chronological ordering.
- Encounters span all care settings, from outpatient appointments to inpatient hospital stays and ED visits.
- CLARITY_ADT provides a granular audit trail of patient movement during an admission.
- Multiple provider roles (Visit, PCP, Referring) are tracked for each encounter.
- Encounter types can be inferred from department names and admission type fields since this extract lacks a dedicated encounter type column.