Accessibility configuration
An SNR record defining search criteria (visit type, occurrence, days) used by batch jobs to trend patient wait times.
Global
High-speed M database structures (^SAP, ^SCHED) existing outside the Chronicles hierarchy to optimize schedule searches.
Appointment request
An ORD record representing a demand for care (like a referral) that has not yet been scheduled into a slot.
Joint appointment
A single encounter contact (CSN) involving multiple providers or resources with overlapping or touching times.
Appointment serial number (ASN)
An identifier that links a chain of related contacts, such as an original appointment and all its subsequent reschedules.
Slot
A time range on a provider’s template (increments of 5 minutes) identified by provider, department, and start time.
Opening
The capacity within a slot. One opening represents the ability to schedule one appointment.
Block
A reservation on a slot for specific visit types or patient populations (e.g., “New Patients”).
Overbook
Extra capacity in a slot beyond regular openings that requires specific security to fill.
Schedule
The actual calendar created from a template blueprint, containing specific appointments and blocks.
Schedule utilization
Measures how full a schedule is by comparing booked time and unmitigated late cancels to regular available time.
Provider utilization
Measures actual care delivery by comparing completed appointment time to regular available time.
Determine wait times
Query ACCESS_PROV (provider level), ACCESS_DEP (department level), or ACCESS_ALL_DEPS (facility level) using the DAYS_WAIT column.
Differentiate request statuses
In AppointmentRequestFact, BaseStatus is the Epic-released internal logic, while Status is the customer-defined value seen by users.
Identify visits from requests
Use EarliestVisitKey in AppointmentRequestFact to link a request to its first resulting encounter in VisitFact.
Audit request actions
Use APPT_REQ_AUDIT to see a row-by-row history of every action taken on a request.
Distinguish appointments vs. visits
V_SCHED_APPT contains strictly scheduled appointments. VisitFact contains those plus non-appointment encounters like telephone or home visits.
Identify joint appointments
Check PAT_ENC_APPT for a single CSN that has multiple rows for different providers or resources.
Link reschedules via ASN
The first appointment’s CSN becomes the ASN for every subsequent reschedule in that series.
Extract scheduling data
Understand that schedule data is extracted from M globals into Clarity tables (like AVAILABILITY) typically within a rolling window of T-4 to T+120.
Calculate utilization
Provider: Completed Time / Regular Available Time. Schedule: (Noncanceled Time + Unmitigated Late Cancel Time) / Regular Available Time.
Find original blocks
In AVAIL_BLOCK, if REL_BLOCK_C is populated, it represents the original block before a time release occurred.
Non-Chronicles Data Dependency
Schedule templates and actual calendars are stored in specialized M globals for performance. If a schedule has not been “viewed” or generated in the system, it will not exist in Clarity tables.
ASN vs. CSN
A CSN (Contact Serial Number) is unique to one specific visit instance. An ASN (Appointment Serial Number) is the “parent” ID that stays constant throughout a chain of cancellations and reschedules.
