Provider and location availability is not a single setting but a layered calculation, and the required layers differ by platform. NexHealth states that a provider must be marked Active, assigned appointment types, and have at least one active availability slot to appear in online booking or its Waitlist feature; if no availability is configured for a provider at a location, patients see a message prompting them to call the office [1]. Medplum, by contrast, documents a minimum seed of a Practitioner, a HealthcareService, and a Schedule linked to that service, with no Location required for a single provider [8]. Elation describes availability as weekly recurring time rules that define when a provider can see patients at each practice location for specific appointment types [2]. The practical question for software buyers is therefore not whether a system supports availability, but how it binds provider, location, service, and time into a bookable unit, which of those bindings are required, and which an administrator can change without breaking the patient-facing flow.
Availability as a Resource Model
RXNT frames availability around three resource types: Person, Material, and Location. A Person resource covers an individual provider, a Material resource covers a room or shared equipment, and a Location resource applies scheduling changes to an entire office, including office hours, holiday closures, or emergency shutdowns [5]. Each availability block is marked Available or Not Available for a selected time, and the system requires the resource to have been created in advance; if it does not appear in the selection list, it has not yet been set up [5]. This model treats provider and location as parallel bookable entities rather than as attributes of one appointment.
Medplum takes a FHIR-native approach with a stricter constraint. Each Schedule belongs to exactly one actor, whether a Practitioner, PractitionerRole, Location, or Device, and Medplum enforces a single-actor constraint even though the FHIR specification allows Schedule.actor to hold multiple references [8]. Because the actor can be a Practitioner, PractitionerRole, Location, or Device, a Location is one possible actor but is not required for every Schedule [8]. Every actor referenced by a Schedule must also have a timezone set through the FHIR timezone extension [8]. The minimum seed for a single provider is a Practitioner, a HealthcareService, and a Schedule linked to that service, with no Location included in that minimum set [8]. This separation makes availability resolution unambiguous per resource, but it also means multi-actor availability must be modeled as multiple Schedules rather than one combined record.
Binding Location and Session Format to Time
PracticeRunner binds availability blocks to provider, location, session format, service, and scheduling audience. A block can be limited to a location and service so that an office visit does not need to use the same schedule as telehealth or phone sessions [4]. Session formats include Office, Telehealth, and Phone, and when availability is tied to a location, scheduling can show times that match the requested location and session format [6]. A client looking for telehealth should not need to see office-only times, and an in-person consultation should not need to use a phone-only block [6]. Location defaults reduce repeated choices when staff create appointments, but PracticeRunner states that these defaults do not replace availability blocks; availability still controls when a provider is available at a particular location and which session formats, services, and audiences can use that time [6].
Upheal uses a named, reusable weekly schedule that includes hours for each day, a time zone, and one or more locations, with one location set as the default [7]. If more than one location is listed on an availability, clients can choose between those locations when self-scheduling, regardless of the default [7]. To allow clients to choose between telehealth or in-person sessions, an administrator sets a location for each on the availability; to restrict clients to one location, the availability must contain only that location [7]. Upheal also separates practice schedules, which admins create for the whole practice, from provider schedules, which belong to one provider and can be created by admins or by the provider for themselves [7].
A Suggested Validation Scenario for a Multi-Location Practice
A hypothetical two-location therapy practice could test availability binding by creating one provider who works in-person at Location A on Mondays and Wednesdays, telehealth on Tuesdays, and phone sessions at Location B on Thursdays. In PracticeRunner, the administrator would create separate availability blocks for each location and session format, then verify that a client requesting telehealth on a Monday does not see office-only times [6]. In Upheal, the administrator would create a provider schedule with multiple locations and confirm that clients can choose between telehealth and in-person only when both locations are listed on that availability [7]. In Medplum, the same provider would require separate Schedule resources for each actor because of the single-actor constraint; a Location would be modeled as its own Schedule actor rather than as a required attribute of a provider Schedule [8]. The test should also include a custom date override, such as a holiday week, to confirm whether the system treats the override as additive or replacement. This scenario is a suggested evaluation method, not a documented test result from any vendor.
Recurring Patterns and Override Boundaries
Elation supports weekly recurring patterns by location and appointment type, with multiple availability blocks per day and the ability to remove availability for specific days or locations [2]. The documentation states there is no native every-other-week rule; rotating schedules must be modeled using recurring weekly patterns plus manual overrides [2]. Elation also warns that a time frame without both a Start Time and End Time cannot be saved [2]. Its Clone function copies availability to another provider, and the copy is additive: if the target provider already has a block at that location on the same day and time, it is skipped, so running Clone Availability twice is safe and will not create duplicates [2].
NexHealth separates recurring weekly schedules from custom dates, which are one-off availability slots for specific dates such as a provider working a Saturday or a modified schedule during a holiday week [1]. A provider might have a recurring weekly schedule plus a custom date override for a specific week [1]. NexHealth also supports provider-level appointment duration overrides: when editing appointment types, an administrator can customize durations for a specific provider, and if the custom duration is shorter than the global appointment type duration, only the shorter slots will appear to patients for that provider [1]. This creates a second layer of slot calculation beyond the raw availability window.
Patient-Facing Filtering and Slot Computation
Luma Health describes Patient Scheduling+ as using a Digital Forms framework to guide patients through scheduling, with Luma determining which appointments meet patient needs so patients see appropriate open appointments [3]. Administrators can configure whether open appointments are sorted by distance to the patient's ZIP code, how many hours are skipped before showing same-day availabilities, and how many days of open appointments a patient can see [3]. Filters can show open appointments for particular providers or facilities, and organizations can preconfigure which resources appear from the provider and facility filters [3]. Luma also lists configurable options such as merging short sequential appointments of the same type into single longer available appointments and overriding the number of days shown for appointments with set intervals [3].
NexHealth uses display buttons labeled 10, 25, 50, and 100 on the availability screen as pagination controls that determine how many hours of availability are shown at one time [1]. This is an administrative view control, not a patient-facing slot limit. NexHealth also requires each provider to be toggled to Active; a provider set to Inactive will not appear in online booking or the Waitlist even if availability slots exist [1]. The combination of active status, appointment type mapping, and at least one availability slot forms the minimum condition for a provider to appear as a booking option in NexHealth [1]. This condition is specific to NexHealth and is not stated as a universal requirement across the other platforms reviewed.
What the Documentation Does Not Establish
The sources describe configuration mechanics but do not provide independent measurements of booking accuracy, patient conversion, or administrative error rates. Luma Health's document states that any functionality not outlined may be subject to additional configuration or scope, but it does not quantify performance [3]. Medplum labels its Scheduling feature as beta and notes that a seed bundle can partially succeed on hosted Medplum, advising users to inspect every response entry before accepting bookings [8]. This is a deployment caution, not a claim about production reliability.
None of the retrieved documents establishes a universal requirement for how many availability layers a scheduling system must expose, and the minimum required resources differ across platforms. NexHealth requires active status, appointment type mapping, and at least one availability slot [1], while Medplum's minimum seed omits Location entirely [8]. RXNT's resource model, Medplum's single-actor Schedule constraint, and Upheal's practice-versus-provider schedule split represent different design choices for the same underlying problem [5][8][7]. A buyer evaluating these systems should test whether the product can represent the practice's actual multi-location, multi-format schedule without manual workarounds, because the documentation shows that workarounds differ in cost and visibility.
Sources & references
- How do I set up providers and provider availability for online booking? | NexHealth Help Center · help.nexhealth.com
- Calendar & Booking Site Guide - Specifying Provider availability by Practice Location & Appointment Type · help.elationhealth.com
- Patient Scheduling+ - Luma Health · www.lumahealth.io
- Online Scheduling and Inquiries | PracticeRunner Help · practicerunner.com
- Availability Calendar Overview – RXNT Help Center · help.rxnt.com
- Setting Availability by Location and Session Format | PracticeRunner Help · practicerunner.com
- Setting up Availability for client self-scheduling | Upheal Support Center · upheal.io
- Scheduling | Medplum · www.medplum.com