Patient self-scheduling appointment template rules are the configuration layer that decides which open slots a portal can expose and which visit reasons a patient may attach to them. The rule set is not uniform across products. PCC Learn describes a portal visit type that marks specific template slots as available to portal scheduling without affecting Appointment Book users [1]. DPC Pro documentation instead describes a per-time-slot booking mode that can override an organization default [2]. Lobbie organizes controls around booking links, schedules, appointment types, locations, and practitioners [3]. Luma Health frames the same problem through form-driven filtering and configurable availability behavior [4]. FollowMyHealth requires appointment type, provider, and service configuration before direct scheduling appears [7]. Keona Health adds visit reason and limiting rule controls [8]. The practical question is therefore not whether a product supports self-scheduling, but which template object owns the rule, what inputs it accepts, and what the patient sees when a rule fails.

Slot-Level Gating Versus Category-Level Availability

PCC EHR separates the scheduling template from the portal category. A practice first assigns visit reasons to a Portal Scheduling Category, then opens Provider Hours and marks specific template slots with a portal version of each visit type [1]. The documentation states that portal visit types function the same as other visit types and only indicate that those slots are available to Portal Scheduling, with no effect on Appointment Book scheduling [1]. A PCC conference slide deck describes two methods: offer only slots designated with a Portal Visit Type, or offer all open slots matching the visit reason color [5]. The first method is more restrictive because it requires explicit slot marking; the second maximizes available slots but still depends on visit types, providers, and locations specified in the Portal Scheduling tab [5].

DPC Pro places the rule directly on the schedule template block. The documentation instructs an administrator to navigate to Settings, Schedule Templates, open the provider's template, select a time slot, and set the booking mode to Self-Schedule [2]. The organization default applies to all time slots unless overridden, and individual time slots can override that default [2]. This creates a gradual rollout path: a practice can allow self-scheduling for afternoon follow-up slots while keeping other blocks on request-and-approval [2]. The distinction matters because PCC's portal visit type is a visibility marker layered onto an existing template, while DPC Pro's booking mode is a slot-level workflow decision that also determines whether the visit is confirmed immediately or held for staff review [2].

What the Patient Selects: Visit Reason, Type, and Location Rules

PCC constrains patient choice through categories and visit reasons. A patient selects a specific visit reason within a category and may add a note such as symptoms or discussion subjects [1]. When scheduling multiple patients, the visit reason type for each patient must match [1]. The Visit Reasons tab displays a Portal Scheduling column showing whether each reason is Sick, Well, Vaccine Only, Other, or not enabled [1]. An alternative Portal Display Name can be set for the patient-facing label [1]. This means the template rule does not simply expose time; it also limits which clinical reason can occupy that time, and the multipatient constraint prevents mixed visit reason types in a single booking action [1].

Lobbie approaches the same problem through a self-scheduling flow rather than a provider template. The flow can be configured so patients choose between all enabled appointment types or are fixed to a single selected appointment type [3]. Location and practitioner selection follow the same selectable or fixed pattern [3]. The connected schedules determine where self-scheduled appointments appear, and the order of multiple schedules determines presentation [3]. Minimum notice and maximum advance scheduling settings prevent bookings within a specified window or beyond a specified horizon [3]. These are flow-level rules that sit above the underlying practitioner availability, so the template itself may remain unchanged while the booking link narrows what the patient can request [3].

Checklist Before Enabling a Self-Scheduling Template Rule

Confirm which object owns the rule: a portal visit type on a provider template in PCC, a per-slot booking mode in DPC Pro, or a flow-level appointment type and location setting in Lobbie [1][2][3]. Verify that the visit reason or appointment type is active and patient-visible, since FollowMyHealth requires both the 'Can patient schedule this appointment?' option and provider configuration [6]. Review patient-level exclusions such as privacy, status flags, and care center assignment, which can block an otherwise available slot [1]. Decide whether the slot should confirm immediately or enter a staff review queue, and document the resulting record status and reporting label [2][1].

Eligibility Filters and Patient-Side Exclusions

Template rules are only part of the exposure chain. PCC documentation states that patients with privacy enabled, a status flag that prevents scheduling, or assignment to a care center that does not use patient portal scheduling cannot be selected and are marked with 'Please Call to Schedule' [1]. The PCC slide deck adds that flags already checked under 'Prevent All Scheduling' will not be available to select [5]. A separate flag, 'Prevent Only Portal Scheduling,' appears in the slide deck as a practice-level control [5]. These exclusions operate outside the template but determine whether a technically available slot is actually offered to a given patient.

FollowMyHealth adds age and visibility rules at the appointment type level. The Appointment Types screen includes a Max Age filter specifying whether the appointment type is available based on patient age, and a Visible to Patient toggle [6]. The 'Can patient schedule this appointment?' option makes the type available in the direct scheduling workflow, but providers must also be properly configured for the patient to view it [6]. Keona Health documentation describes limiting rules as necessary only if a selected resource sees a specific population or patient criteria [8]. These controls show that a template rule may be valid yet still produce no bookable slot for a particular patient because an eligibility filter intervenes.

Booking Mode, Confirmation, and Record Ownership

DPC Pro makes the confirmation outcome part of the template rule. In self-schedule mode, the patient books directly and the visit is confirmed immediately; in request-and-approval mode, the patient submits a request that staff must review before confirmation [2]. The documentation states that a self-booked visit is created immediately with a status of Scheduled, and DPC Pro does not send a confirmation email for a self-booked visit [2]. For request-and-approval, staff select Approve & Schedule, check the date and time, select a provider and location, set duration, optionally add internal notes, and submit the review [2]. If the chosen provider already has a visit at that time, DPC Pro documentation indicates a conflict handling step, though the exact resolution behavior is not fully described in the retrieved passage [2].

PCC records the scheduling actor rather than a separate approval state. The Appointments by Scheduling User report groups appointments made through patient portal self-scheduling as scheduled by 'Portal User' [1]. This gives practices an audit trail for which appointments originated in the portal, but the documentation does not describe a request queue or staff approval workflow equivalent to DPC Pro's request-and-approval mode [1][2]. Luma Health's Patient Scheduling+ documentation describes form-driven appointment matching and configurable availability behaviors, including merging smaller time slots into larger open appointments and allowing appointment durations to override provider availabilities [4]. These are availability computation rules rather than confirmation workflow rules, and the retrieved Luma material does not specify a request queue in the same terms as DPC Pro [4].

A Hypothetical Validation Scenario for Template Rule Changes

A practice could test a template rule change without exposing patients to unintended slots. One suggested workflow is to create a test provider template with a single portal-designated slot, assign one portal scheduling category containing one visit reason, and then attempt booking from a test patient account that lacks any scheduling-prevention flag. The expected result under PCC's Method 1 is that only the striped portal visit type slot appears, while an Appointment Book user can still book the same slot [1][5]. The test should also verify that a patient with a 'Prevent Only Portal Scheduling' flag sees no bookable slot even though the template rule remains active [5].

For a DPC Pro-style configuration, the same scenario would set one template block to Self-Schedule and a second block to request-and-approval, then confirm that the first booking creates a Scheduled visit immediately while the second creates a request requiring staff review [2]. The test should also check whether the organization default reasserts itself on a newly created slot that was not explicitly overridden [2]. This hypothetical validation is a suggestion for isolating which object owns the rule; it is not a claim that any product has been independently tested. The value is that it forces a practice to distinguish template visibility, patient eligibility, and confirmation workflow as separate failure points.