Core concepts

A quick glossary of the terms you'll see throughout these docs, the portal, and the API. For how these pieces fit together in practice, see Referrals workflow and Scheduling & booking.

Tenant

Each clinic using Fertiligent is a tenant, with its own portal at https://<tenant>.fertiligent.ai. Tenants share the identity server and API but their data is kept separate. See Multi-tenancy & environments for how tenant resolution works for API integrations.

Prospect

A prospect is a potential patient moving through the outreach and intake funnel, before they've become an active patient. Prospects move through stages — from not yet started through to booked. Booking an appointment for a prospect is what promotes them to an active patient. See Referrals workflow for how a confirmed referral creates a prospect and drives it through outreach.

Patient

A patient is an active patient record — the clinical side of a person's journey, as distinct from the outreach side tracked on the prospect.

Referral

A referral is an inbound referral (for example a fax or an uploaded document) that Fertiligent's extraction pipeline reads, and that staff review and confirm. It moves through states such as Uploaded, Extracting, Needs review, and Confirmed. See Referrals workflow for the full lifecycle.

Care episode / case

A care episode (also referred to as a case) is a unit of clinical care coordination for a patient — the container that clinical work is organized around once someone is an active patient.

Scheduling primitives

Scheduling is built from a small set of primitives that work together. See Scheduling & booking for how staff use them day to day.

Term	What it represents
Roster rule	Defines when a provider or resource is available.
Availability	A query over roster rules that surfaces open slots.
Appointment type	The kind of appointment being booked.
Resource	A bookable thing — for example a provider or a room.
Booking	A reservation of a slot, for an appointment type, against a resource.