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.
Eva
Eva is Fertiligent's patient-facing AI companion, embedded on a clinic's website or portal. She answers questions, captures prospects, and hands off to staff when a person is needed. See Eva, the patient companion.
Knowledge base
The knowledge base is the curated set of clinic materials (services, pricing, hours, FAQs, policies) the phone, chat, and messaging assistants answer from. Answers are grounded in these materials, and the assistant hands off to a person when it can't answer confidently. See Knowledge base.
Fact card
A fact card is a curated, frequently-asked clinic fact the assistant can answer instantly "from memory" — for example a clinic's address or a common price. Changeable facts require periodic staff confirmation so a stale value is never asserted.
Message thread
A message thread is a two-way conversation with a patient, held in the portal and optionally over text (SMS) or email. Threads can be handled by staff directly or with AI-drafted replies that a person approves. See Patient messaging & SMS.
Fertility cycle
A fertility cycle is one treatment cycle recorded against a care episode — stimulation, retrieval, fertilization, and transfer — with related embryo, storage, and genetic-testing records. See Fertility clinical tracking.
Channel consent
Channel consent is a patient's agreement to receive personal health information on a specific channel — by text or by phone. It is separate from verifying a patient's identity: the assistant shares private details only when a patient is both verified and consented. See Consent & patient privacy.
Patient portal
The patient portal is a secure, patient-facing view of a person's own care — their profile, cases, care timeline, outcomes, documents, and messages — plus the controls to manage their own consent. See The patient portal.
Plan
A clinic's plan determines which features are enabled for it. Availability notes throughout these guides refer to whether a feature is included in your plan.
Staff copilot
The staff copilot is an internal AI assistant that answers staff questions from your clinic's own operational documents (SOPs, protocols, policies), with citations — distinct from the patient-facing knowledge base. See Staff copilot.
EMR integration
EMR integration pushes clinical data from Fertiligent to an external Electronic Medical Record system automatically, as standard FHIR resources over secure HTTPS. See EMR integration.
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. |