Patient appointment waitlist matching workflows differ in a fundamental way: some systems match patients to newly opened slots, while others match slots to a waiting patient population. The distinction shapes who owns the waitlist record, what inputs drive an offer, and when an offer expires. Athelas and athenahealth document patient-anchored waitlist entries that capture preferences and replace a booked appointment [1][5]. NexHealth documents a staff-initiated request that broadcasts one or more open slots to a selected patient group [2]. MedInformatix describes two modes, including a slot-to-patient scoring algorithm that ranks eligible patients when a cancellation appears [3]. A Mayo Clinic study of Epic-based automated waitlists reports offer generation and acceptance outcomes at scale [7]. These are not interchangeable implementations, and a practice evaluating them should compare matching direction, expiration behavior, and the manual work left after an offer is sent.

Two Matching Directions: Patient-to-Slot and Slot-to-Patient

The most consequential architectural difference is the direction of the match. Athelas processes cancellations by identifying waitlist entries that match the timeslot, provider, and location, then sends offers to one or multiple matching patients [1]. The waitlist entry is the persistent record, and the open slot is the trigger. athenahealth's API similarly models a waitlist entry as a request tied to a booked appointment that the entry would replace, with fields for appointment type, provider, department, day-of-week preferences, and hour ranges [5]. In both cases, the patient's stated constraints are stored before a slot exists, and the system searches for slots that satisfy those constraints.

MedInformatix documents the opposite approach in its Waitlist Mode. Instead of searching for slots per patient, it searches for patients per slot, monitoring recently opened slots from cancellations or rescheduled appointments and matching them against the waitlist population [3]. The documentation describes a scoring algorithm that ranks eligible patients using factors such as STAT priority, lost race priority for patients who previously accepted but lost a slot, and how much the offer improves the patient's current appointment [3]. This slot-to-patient orientation treats the open slot as the scarce resource and the patient ranking as the decision layer. A buyer should not assume that a waitlist feature automatically does both; the documented trigger and ranking model determine whether the workflow fills slots quickly or honors patient preference order.

Record Ownership and Inputs: Who Creates the Waitlist Entry

Record ownership varies by product. Athelas allows patients to join the waitlist through the patient portal when no available time appears, specifying facility, one or multiple providers, appointment type, and preferred times, with an Anytime option [1]. Practices can also add patients manually in Insights, entering provider, facility, appointment type, effective and expiration dates, notes, and preferred availability [1]. The same entry can therefore originate from either side, but the documentation places the preference form in the patient's hands for portal-initiated entries.

NexHealth inverts this ownership. The documented workflow begins with a staff member creating a waitlist request by selecting a manually created slot or open slots, then adding patients from four groups: the practice management system ASAP list, patients overdue for Continuing Care, patients who missed or canceled appointments, or a manual search [2]. The patient does not initiate the entry; the practice selects both the slot and the recipient population. NexHealth also documents automatic filtering that excludes patients who already have a future appointment for the ASAP, Missed, and Cancelled flows, with a six-month exclusion window for non-cancelled appointments [6]. This is a broadcast model, not a preference queue, and the record is a request object rather than a persistent patient preference.

A Suggested Validation Scenario for Comparing Matching Behavior

A practice evaluating two waitlist products could construct a controlled scenario without production patient data. Create three test patients with distinct constraints: Patient A specifies one provider and Tuesday mornings, Patient B specifies any provider and any time, and Patient C specifies a different facility. Cancel a Tuesday 9:00 AM appointment for the specified provider, then observe which patients receive offers and in what order. For a slot-to-patient system such as MedInformatix Waitlist Mode, record whether the scoring algorithm ranks Patient B above Patient A and whether Patient C is excluded by the facility group check [3]. For a patient-to-slot system such as Athelas, record whether the cancellation popup reports matching entries and whether offers remain active after the configured time-to-accept window [1].

Repeat the scenario with a manually filled slot. NexHealth documentation states that if an open slot is filled manually after a waitlist request is sent, the request remains active and must be canceled by staff [6]. A validation run should confirm whether the evaluated product surfaces that stale request or silently expires it. Finally, test the claim window by sending an offer and waiting past the documented expiration point. The goal is not to determine which product is better, but to document the exact manual cleanup and race conditions each workflow creates in the practice's own configuration.

Offer Expiration and Claim Mechanics

Expiration rules determine whether an offer remains claimable after the initial message. Athelas documents a bucket and expiration configuration: if time-to-accept is five minutes, bucket size is ten, and expiration is off, offers accumulate across buckets, producing ten active offers in minutes 0–10, twenty in minutes 11–20, and thirty in minutes 21–30 [1]. The documentation states that offers do not expire until a patient accepts when expiration is off, which means multiple patients can hold active offers for the same slot simultaneously. This creates a race condition that the practice must understand before enabling the setting.

NexHealth documents a different default: waitlist requests automatically expire at the scheduled appointment time, and a patient attempting to claim after that time receives a message stating the slot has already been claimed [2]. A separate NexHealth help page states expiration occurs 15 minutes before the scheduled appointment time, with a message that the slot is no longer available [6]. The two NexHealth sources describe slightly different expiration points, which is worth verifying against the current product version. MedInformatix documents a reservation length of 10 minutes for a waitlist offer and a separate 10-minute hold for follow-up offers, with a MAIA conversation session active for 1440 minutes [3]. These are materially different claim windows, and a practice that expects first-come, first-served behavior may be surprised by a system that holds offers open until acceptance.

Matching Logic and Scoring: What Determines Who Gets the Offer

Matching logic ranges from simple constraint filtering to explicit scoring. Athelas matches on timeslot, provider, and location when a cancellation occurs, and the documentation describes a popup that reports how many waitlist entries match that timeslot [1]. The documented inputs are the patient's facility, provider, appointment type, and preferred times, but the documentation does not describe a ranking among multiple matching patients beyond the offer list count. athenahealth's API exposes a priority field with LOW, NORMAL, or HIGH values on waitlist entries [5], suggesting that priority is an input the practice can set, but the API documentation does not describe how priority affects offer ordering.

MedInformatix provides the most explicit scoring description. When Waitlist Mode finds an open slot, it scores eligible patients based on factors that predict likelihood of acceptance, including STAT priority, lost race priority, appointment improvement, and additional factors that the documentation lists but does not fully enumerate in the retrieved anchors [3]. The documentation also describes a facility group check: if a slot is at a different facility, the system checks whether both facilities share the same facility group in WAITLISTFACGROUP, and a reason code with SAME_BOOK_ON_MOVE set causes the offer to be skipped [3]. This is a documented constraint that prevents cross-facility moves under specific conditions. The scoring model is vendor-specific and should not be assumed to generalize to other products.

What the Research Documents About Automated Waitlist Outcomes

A 2025 study of Mayo Clinic Epic Systems software examined an automated waitlist self-rescheduling process for patients with existing appointments who elected to be placed on a waitlist for an earlier offer [7]. The study reviewed 1,019,698 appointment offers generated for 229,998 appointments and sent to 164,248 patients during calendar year 2023 [7]. The authors report that 74,736 waitlisted appointments, or 32.5%, received a first offer within two days of waitlist entry, and patients sent at least one response for 104,554 appointments, or 45.4% [8]. Of the 229,998 waitlisted appointments, 56,636 accepted an offer, an accept rate of 24.6%, and accepted appointments were moved earlier by a mean of 22.6 days [8].

These figures describe one organization's Epic-based implementation and cannot be generalized to other vendors or practice types. The study also notes that offers are first come, first served with an expiration time, and that offers cease once the date exceeds the original booked appointment date [8]. The authors report large numbers of expired offers and offers that are never viewed [7]. A separate multisite mixed methods evaluation published in 2026 reports that 90 of 127 health systems in the Patient Access Collaborative reported data regarding their automated waitlist tool [4]. That finding indicates adoption among surveyed systems but does not establish performance or satisfaction across the market.