Epic Cadence Scheduling: Provider Templates, Appointment Types, and Build Guide
Epic Cadence scheduling build fails most often not because analysts lack technical skill, but because scheduling requirements are collected from clinic operations teams without understanding how those requirements translate into Cadence’s template, slot, and appointment type architecture. This article covers what analysts, build specialists, and project leads need to know to configure Epic Cadence correctly – from provider template structure through appointment type build, scheduling rules, MyChart self-scheduling, and go-live validation.
- What Is Epic Cadence?
- Provider Templates: The Foundation of Cadence Scheduling
- Appointment Types: Build and Configuration
- Scheduling Rules, Restrictions, and Referral Management
- MyChart Self-Scheduling and Patient Access
- Cadence Integrations and SIU Interface
- Waitlists, Referrals, and Referral Pools
- Testing and Validation Strategy for Cadence
- Go-Live Planning and Common Failure Points
- Roles, Certifications, and Career Path
- Downloads
What Is Epic Cadence?
Epic Cadence is Epic Systems’ outpatient scheduling module. It manages provider availability, appointment booking, patient reminders, waitlists, referral tracking, and the patient access workflows that drive clinic operations. Cadence is the system that determines when a patient can see a provider, which appointment type they need, how long the slot will be, and whether they can self-schedule through MyChart.
Cadence does not operate independently. It shares data with Epic’s clinical modules – when a provider orders a follow-up in the encounter, that referral flows into Cadence’s scheduling workflow. When a patient schedules through MyChart, the appointment writes directly to the provider’s Cadence schedule. When the patient arrives, the check-in workflow in Epic links to the Cadence appointment record. Every downstream clinical workflow – preregistration, insurance eligibility verification, visit documentation – depends on Cadence appointment data being correct at the point of scheduling.
The implementation challenge is that Cadence requirements come from clinic operations – schedulers, medical assistants, department managers, and physicians – who understand their workflows in operational terms, not in Epic’s build object model. Translating “we see new patients for 60 minutes on Tuesday and Thursday mornings, and established patients for 20 minutes any day except Friday afternoons” into a functioning Cadence template configuration requires knowing exactly how Cadence’s template blocks, appointment types, and slot restrictions interact. The full Epic module context is covered in the Epic EHR Learning Hub.
Provider Templates: The Foundation of Epic Cadence Scheduling
The provider template is the central build object in Cadence. It defines when a provider is available to see patients, what types of appointments fill each time block, and how many patients can be scheduled in each slot. Everything else in Cadence – scheduling rules, MyChart availability, referral pools – depends on the template being built correctly first.
Template Architecture: How Cadence Templates Work
A Cadence provider template is built on a schedule period – a defined date range during which the template is active. Within that period, the template defines which days the provider sees patients, what the daily start and end time is, and how the time is divided into appointment slots. Slots are defined by appointment type – each slot is associated with one or more appointment types that can fill it.
Templates have two primary scheduling models: time-based slots and wave scheduling. Time-based slots are discrete – a 9:00 AM slot, a 9:20 AM slot, a 9:40 AM slot. Each slot holds one appointment unless double-booking is configured. Wave scheduling groups multiple patients into the same arrival time window, expecting that not all will be ready simultaneously – a common model in high-volume primary care and urgent care clinics.
Templates are associated with a provider and a department. The same provider may have different templates for different departments – a cardiologist who sees patients in the main cardiology clinic on Mondays and Wednesdays, and at a satellite clinic on Fridays, requires separate templates for each department even if the appointment types are identical. This is one of the most common scoping mistakes in Cadence implementations: assuming one template per provider when providers work across multiple locations.
Template Types: Standard, Rotating, and Master
| Template Type | How It Works | Best For | Build Complexity |
|---|---|---|---|
| Standard (Fixed) | Same slot configuration repeats every week within the schedule period | Providers with consistent weekly schedules | Low – one pattern to build and maintain |
| Rotating | Different slot patterns alternate on defined cycle (e.g., week A / week B) | Providers with alternating call schedules, part-time patterns | Medium – multiple patterns, cycle configuration |
| Master Template | Reusable template structure applied to multiple providers or departments | Large groups where multiple providers share identical schedule patterns | High upfront, low maintenance – changes propagate |
| Variable / Ad Hoc | One-time template modifications for specific date ranges – holidays, events | Temporary schedule changes without altering the base template | Low per change – but volume of changes creates maintenance overhead |
Slot Configuration: What Goes Inside a Template
Each slot in a Cadence template has a start time, a duration, and one or more appointment types associated with it. The appointment type association controls which types of appointments can fill that slot. A slot associated only with “New Patient – Cardiology” cannot be filled with a “Follow-Up – Cardiology” appointment unless the template is configured to allow it.
Overbook slots allow double-booking within a specific slot. This is different from wave scheduling. An overbook slot explicitly allows two appointments at the same time – used for no-show buffer management or for accompanying family members who need separate appointments. Overbook configuration requires clinical approval – schedulers should not enable it without physician buy-in on the expected workflow impact.
Hold slots reserve time that cannot be booked by schedulers. Common uses include provider admin time, lunch blocks, and procedure time. Hold slots can be configured to release automatically a defined number of days before the appointment date – a common strategy to hold time for urgent add-ons but release unused holds to avoid schedule gaps.
A 12-provider orthopedic group implementing Cadence across three clinic locations had each surgeon providing their schedule pattern verbally during requirements sessions. Fourteen unique schedule patterns were documented. During build review, the clinical informatics team identified that six of the fourteen patterns were functionally identical – same appointment types, same slot durations, different days of the week. By building three master templates and applying day-of-week variations, the team reduced the build scope from fourteen individual templates to three master templates with day-level modifications. This cut template build time by 40% and simplified ongoing maintenance when slot durations changed for post-operative follow-up visits. The key requirement was getting providers to agree on standardized appointment types before build began – which required a facilitated session with the clinic operations manager, not just the physicians.
Appointment Types: Build and Configuration in Epic Cadence
Appointment types are the second critical build object in Cadence. Every scheduled appointment is associated with an appointment type. The appointment type drives the slot duration, the visit type in the clinical record, the billing visit type, the patient reminder workflow, and whether the appointment is visible for self-scheduling in MyChart. Getting appointment types wrong creates cascading problems across scheduling, billing, and clinical documentation.
Appointment Type Attributes That Drive Build Decisions
Every appointment type in Cadence has a set of attributes that define its behavior. The duration is the default slot length – 20 minutes for a routine follow-up, 60 minutes for a new patient comprehensive evaluation. Duration can be overridden at the template level or at booking time depending on configuration. The visit type maps to the clinical record and determines which documentation template loads when the provider opens the encounter.
The billing visit type is separate from the clinical visit type and links to the expected E/M level for revenue cycle purposes. Mismatches between the scheduled appointment type and the billed visit type are a source of compliance risk under CMS documentation guidelines. Build analysts must work with the revenue cycle team to ensure appointment type-to-billing visit type mapping is reviewed and approved before go-live.
The new vs. established patient flag on an appointment type affects scheduling rules. Many payers distinguish new from established patient visits for billing. Some scheduling rules require that “New Patient” appointment types can only be placed in slots explicitly designated for new patients on the provider template. Getting this wrong means new patients can book follow-up slots, disrupting the slot utilization model the clinic designed.
| Attribute | What It Controls | Who Approves | Common Error |
|---|---|---|---|
| Duration | Slot length in template | Clinical operations + physician | Template slot and appt type duration mismatch |
| Visit Type | Clinical documentation template loaded | Clinical informatics + provider | Wrong template loads – wrong note type |
| Billing Visit Type | Expected E/M level for billing | Revenue cycle + compliance | Billing mismatch = compliance risk |
| New/Established Flag | Scheduling rule enforcement | Clinical operations | New patients book follow-up slots |
| MyChart Enabled | Patient self-scheduling visibility | Clinical operations + patient access | Wrong types exposed to self-scheduling |
| Reminder Configuration | Patient notification timing and channel | Patient access + operations | Reminders not firing or wrong timing |
| Telehealth Flag | Marks appointment as video/phone visit | Clinical ops + IT (video platform config) | Telehealth link not generating for patient |
Appointment Type Standardization: The Build Decision That Matters Most
Most Cadence implementations start with too many appointment types. Every department proposes their own list. Cardiology wants “New Cardiology Patient,” “Cardiology Follow-Up,” “Cardiology Consult,” “Cardiology Device Check,” and six more. Orthopedics has an equally long list. Without governance, you end up with 200+ appointment types across a health system where 40 well-defined types would serve the same clinical need.
Appointment type proliferation creates reporting problems. A health system that wants to analyze new patient volume across all specialties cannot do so if “New Patient” is expressed as thirty different appointment type names. It creates maintenance problems when CMS changes documentation guidelines and every billing visit type must be reviewed. And it creates scheduling errors when schedulers choose the wrong type from an overwhelming dropdown list.
The right approach is a standardized appointment type taxonomy agreed across specialties before build begins. Common categories: New Patient, Established Patient, Consult, Procedure, Telehealth New, Telehealth Established, Post-Op, Annual Wellness. Specialty-specific variants should only be created when clinical or billing requirements genuinely differ – not just because the department prefers its own label.
Scheduling Rules, Restrictions, and Referral Management
Scheduling rules in Cadence enforce business logic at the point of booking. They can restrict which appointment types a scheduler can book for a given provider, require that certain conditions are met before scheduling (referral on file, insurance authorization, specific diagnosis), limit how far in advance appointments can be booked, or restrict booking to specific patient populations.
Rule Types and Their Build Implications
Overbook rules define whether a scheduler can place appointments beyond the template’s defined slot capacity. These are set at the department, provider, or appointment type level. Overbook limits protect against schedule inflation that causes provider burnout and patient wait time degradation. Build analysts configure overbook rules with input from department managers and medical directors.
Scheduling lead time rules define how far in advance an appointment can be booked. A provider may want no appointments scheduled more than 90 days out so that template changes can be made without impacting patient appointments. A specialist practice may want appointments available 6 months out for elective procedures. Build analysts configure this in the provider’s scheduling preferences and must align it with the template’s active period.
Referral requirements enforce that a referral exists before booking a specialist appointment. When correctly configured, Cadence checks for an active referral linked to the scheduling department and appointment type before allowing the booking to proceed. The referral requirement links to the organization’s referral management workflow – in Epic, this is typically configured in Referral (REF) records tied to the scheduling department. Analysts familiar with Epic EHR Orders and CPOE workflows will recognize that provider-to-provider referral orders in the clinical record integrate with Cadence’s scheduling validation.
Patient Matching and Duplicate Prevention
Cadence scheduling creates or updates patient records at the time of booking. Patient matching rules determine when an incoming scheduling request creates a new Epic patient record versus linking to an existing one. Duplicate patient records are a persistent data quality problem in scheduling-heavy implementations. A patient who calls to schedule an appointment and gives a slightly different name, phone number, or date of birth than their existing record can generate a duplicate.
Build analysts configure the Enterprise Master Patient Index (EMPI) matching algorithm thresholds and the duplicate detection workflow. Too strict matching creates false duplicates. Too loose matching fails to catch real duplicates. The matching algorithm uses weighted scoring across demographic fields – name, date of birth, gender, address, phone, SSN. Configuring the algorithm requires review of the organization’s actual patient data quality and tolerance for false positives versus false negatives.
MyChart Self-Scheduling and Patient Access Configuration
MyChart self-scheduling lets patients book their own appointments through Epic’s patient portal without calling the clinic. Cadence drives MyChart self-scheduling – patients see available slots based on the provider template, appointment type configuration, and self-scheduling eligibility rules configured in Cadence. If the template is wrong, patients see incorrect availability. If the appointment type is not enabled for self-scheduling, it does not appear to patients regardless of slot availability.
Self-Scheduling Eligibility and Guardrails
Not all appointment types should be available for self-scheduling. New patient appointments in specialty care often require referral verification before scheduling – allowing self-scheduling for these bypasses the referral check and creates downstream billing and authorization problems. Cadence’s self-scheduling configuration allows build teams to restrict self-scheduling to established patients only, to patients with active referrals, or to specific appointment types that require no clinical gatekeeping.
Questionnaire routing is a Cadence feature that presents patients with screening questions before completing a self-scheduled appointment. A patient scheduling a sick visit can be asked about symptoms – if responses suggest an urgent condition, the questionnaire routes them to a different scheduling path (urgent care, nurse triage). This logic is configured as scheduling questionnaires in Cadence and must be validated with clinical leadership before activating.
A primary care network with 45 providers activated MyChart self-scheduling across all locations simultaneously at go-live. Within the first week, three issues surfaced. First, patients were self-scheduling “Annual Wellness Visit” appointments on days the provider had marked as procedure-only in the template – the procedure hold slots had been accidentally enabled for self-scheduling. Second, established patients from other health systems (who had MyChart accounts via Care Everywhere) were self-scheduling as new patients because the patient relationship check was not configured. Third, a behavioral health provider’s entire schedule was visible to self-scheduling patients – a privacy configuration error, as behavioral health had explicitly requested scheduling go through staff only. All three were configuration errors in Cadence, not clinical errors. They were identified and resolved within 48 hours but created significant scheduler rework and patient communication. The fix: a pre-activation review of self-scheduling eligibility settings per provider, per appointment type, had not been on the test plan.
Telehealth Appointment Configuration
Telehealth appointments in Cadence require appointment type configuration that flags the visit as video or telephone, integration with the video platform (Epic’s native video or a third-party integration like Zoom for Healthcare or Doximity), and patient notification configuration that delivers the video link before the visit. Build analysts configure the telehealth appointment type attributes and the video platform integration in coordination with the telehealth IT team.
The patient-facing MyChart experience for telehealth requires that the appointment type generates a unique video visit link delivered via MyChart notification. If the video platform integration is not tested end-to-end before go-live, patients arrive at their appointment time with no video link – a high-visibility failure that generates immediate complaints and erodes patient trust in the portal.
Cadence Integrations and the HL7 SIU Interface
Cadence does not always operate as a closed system. Many health systems have ancillary scheduling systems, patient engagement platforms, or external referral sources that need to receive scheduling events from Epic. The HL7 SIU (Scheduling Information Unsolicited) message type is the standard mechanism for transmitting scheduling events from Cadence to downstream systems via Epic Bridges.
SIU Message Events and Downstream Systems
| SIU Event | Trigger | Common Receiving System | Key Data in Message |
|---|---|---|---|
| S12 – New Appointment | New appointment booked in Cadence | RIS, patient engagement platform, referral system | Patient ID, provider, dept, appt type, date/time |
| S13 – Rescheduled | Appointment moved to new date/time | RIS, patient engagement, reminder platform | Original appt ID, new date/time, reason |
| S14 – Modified | Appointment details changed (type, provider) | RIS, downstream scheduling systems | Changed fields, appointment ID |
| S15 – Cancelled | Appointment cancelled | RIS, billing, patient engagement, waitlist | Cancellation reason, appointment ID |
| S26 – No-Show | Patient marked no-show at check-in | Care management platform, no-show outreach system | Patient ID, provider, appointment type, timestamp |
SIU interface configuration lives in Epic Bridges. Build teams configure which Cadence events trigger outbound SIU messages and which downstream systems receive them. A common mistake is configuring SIU messages to fire for all scheduling events without filtering – this floods the receiving system with high-volume message traffic that includes appointment type changes, room reassignments, and internal status updates the receiving system does not need. Configure SIU filtering to send only clinically meaningful events to each receiving system.
Radiology information systems (RIS) are the most common recipient of Cadence SIU messages. When a patient is scheduled for an imaging appointment in Epic, the SIU S12 message triggers the order in the RIS, pre-populates patient demographics, and creates the radiology worklist entry. The appointment type code in the SIU message must map to a valid procedure code in the RIS – this code mapping is as important here as LOINC mapping in lab interfaces.
Waitlists, Referral Pools, and Patient Access Workflows
Cadence’s waitlist functionality manages patients who need an appointment sooner than current availability allows. When a patient is placed on a waitlist, Cadence monitors the schedule for cancellations and can automatically notify the patient or scheduler when a matching slot opens. The waitlist configuration defines which appointment types and providers the patient is waiting for, the patient’s urgency level, and the notification method.
Referral Pool Configuration
Referral pools in Cadence allow patients to be placed in a queue for a specialty or service line rather than a specific provider. A patient referred to orthopedics goes into the orthopedics referral pool and can be assigned to any available orthopedic surgeon – not necessarily the one originally requested. Build analysts configure referral pools with the scheduling department, define which providers are in each pool, and set the rules for how patients are assigned from the pool to a specific provider.
Referral management in Epic links to the clinical ordering workflow. When a primary care provider places a referral order in the encounter, that order creates a referral record in Cadence that the specialist’s scheduling team can see. The referral record tracks the referral status, the number of authorized visits, and whether the patient has been scheduled. Build analysts must map the clinical referral order workflow to the Cadence referral management workflow – these are configured separately and must be validated together.
Testing and Validation Strategy for Epic Cadence
Cadence testing requires both technical validation and operational workflow validation. The template may be technically correct – slots configured, appointment types associated, scheduling rules active – but if the schedulers cannot complete their actual daily workflows using it, the build fails. Testing must include schedulers using the system in representative scenarios, not just build analysts checking configuration.
Test Scenarios That Must Be Covered
Template validation requires confirming that each slot displays the correct appointment types, that slot durations match the appointment type durations, that hold slots are not bookable by schedulers, and that the template activates and deactivates on the correct dates. This is unit-level testing of the build object. It should be completed before integrated workflow testing begins.
Scheduling rule testing requires attempting to book appointments that should be blocked and confirming the rule fires correctly. Test that new patient appointment types cannot book into follow-up slots. Test that overbook limits enforce correctly. Test that scheduling a referral-required appointment without an active referral produces the correct warning or block. Teams experienced in BAT vs UAT methodology will recognize that scheduler acceptance testing must validate not just that the rules fire but that the workflow produces the right outcome for the scheduler – a helpful warning versus a cryptic error.
MyChart self-scheduling validation requires logging in as a test patient and attempting to book appointments that should be available and appointments that should not be. Confirm that behavioral health providers are not visible. Confirm that established-patient-only types do not appear for new patients. Confirm that the telehealth video link generates and delivers via notification. These tests should be performed in a test environment that mirrors production MyChart configuration as closely as possible.
SIU interface testing validates that scheduling events in Cadence trigger the correct outbound messages and that receiving systems process them correctly. A schedule booking in Cadence should create the expected record in the RIS. A cancellation should update the RIS record. Test all five SIU event types against each receiving system. The connection to Bridges-based interface testing is direct – the same integration validation approach used for other Epic interfaces applies here.
Patient reminder testing is often missed. Every appointment type with a configured reminder should be tested end-to-end – book an appointment, confirm the reminder fires at the correct timing, verify the content is correct. Reminder failures on go-live day produce no-show spikes that overwhelm clinical operations teams and damage patient satisfaction scores before the system has had a chance to stabilize. Clinical documentation workflows also connect here – the EpicCare Inpatient ClinDoc guide shows how appointment data flows into visit documentation, which means Cadence data accuracy affects documentation quality downstream.
Go-Live Planning and Common Failure Points for Epic Cadence
Cadence go-live has a different risk profile than clinical module go-lives. Patient safety risk is lower than pharmacy or laboratory. Revenue cycle risk is significant – incorrect appointment types affect billing. Operational disruption risk is high – schedulers who cannot book appointments or who create scheduling errors have immediate, visible impact on patients and providers. The Epic EHR Go-Live Support framework applies here, with scheduling operations leads added to the command center structure.
| Failure Point | Impact | Mitigation |
|---|---|---|
| Template not active on go-live date | High – no slots available | Validate template activation dates 48hr before go-live |
| Wrong appointment type on slot | High – billing and documentation errors | Full template slot audit before go-live, revenue cycle sign-off |
| MyChart self-scheduling misconfigured | Medium – wrong patient access, privacy risk | Per-provider self-scheduling review before activation |
| Patient reminders not firing | Medium – no-show spike | End-to-end reminder test per appointment type before go-live |
| SIU interface not firing | Medium – RIS/downstream system out of sync | SIU interface stability test 48hr before go-live |
| Duplicate patient records from scheduling | Medium – data quality, care coordination | EMPI matching thresholds tested with real name/DOB variation scenarios |
| Referral requirements blocking valid bookings | Medium – scheduler frustration, delayed access | Referral rule tested for all specialist appointment types before go-live |
Data Conversion: Pre-Built Appointments
Most Cadence implementations require converting existing scheduled appointments from the legacy scheduling system into Epic before go-live. Patients who have appointments booked 3, 6, or 12 months out need those appointments to appear in Epic on day one. Data conversion scope for scheduling typically covers the forward-booking window – any appointment with a future date as of go-live.
Appointment type mapping is the core data conversion challenge. The legacy system may have 80 appointment types that must map to the 40 Epic appointment types defined in the new build. The mapping table must be approved by both scheduling operations and revenue cycle before conversion runs. Conversion validation requires a sample of converted appointments to be reviewed by schedulers to confirm the appointment type, provider, time slot, and patient demographics converted correctly.
Roles, Certifications, and Career Path for Cadence Specialists
| Role | Certification | Key Skills | Salary Range (2026) |
|---|---|---|---|
| Cadence Build Analyst | Epic Cadence | Template build, appt type config, scheduling rules | $75,000 – $110,000 |
| Senior Cadence Analyst | Epic Cadence + Prelude | Multi-specialty build, MyChart, SIU interfaces, EMPI | $95,000 – $130,000 |
| Patient Access Manager | Epic Cadence + operational background | Patient access strategy, MyChart, referral management | $90,000 – $125,000 |
| Cadence Consultant (Contract) | Epic Cadence | 2+ full implementations, multi-specialty experience | $65 – $100+/hr |
Appointment type standardization governance – getting department stakeholders to agree on a manageable, consistent appointment type taxonomy before build begins – is the single highest-leverage activity in a Cadence implementation. Skip it and you spend the rest of the project managing an ever-growing list of department-specific appointment types that create reporting gaps, billing risks, and scheduler confusion. Invest the time in pre-build governance and the rest of the template configuration becomes significantly easier.
Authoritative References
- CMS – Physician Fee Schedule and Evaluation and Management Documentation Guidelines (E/M Coding)
- HL7 v2 SIU – Scheduling Information Unsolicited Message Specification