Skip to main content

Roadmap

Fertiligent is an AI operating system for fertility clinics, one clinic-governed agent working across every patient channel, with the clinic keeping oversight of what it says and does.

A clinic runs on conversations, documentation, and records. Each is work a person does today that the system can carry, in that order, because each one earns the next. That progression is where the platform is going, and this page is where it is up to. Past it, the same assistant moves from answering and drafting to doing the work itself, inside the rules the clinic sets and with every step on the record (see Agents across the clinic under Later).

Timelines are directional and subject to change; nothing here commits us to a feature on a date, and availability differs by clinic. For what has already shipped, see the Release Notes.

Work runs in four tracks (Intake & Referrals, Patient Communication, Clinical Copilot & EMR, and Trust & Compliance) and every track holds to the same principles: the clinic owns its data and its brand, clinicians keep judgment, and an AI answer shows where it came from.

Live today​

Not roadmap, in production now, and the foundation everything below builds on.

  • AI voice agent for inbound calls: after-hours and overflow phone answering that resolves routine questions, books consults, and escalates anything clinical to your team. No fertility platform we know of answers the clinic line today.
  • Conversations: voice, SMS, email and portal messages in one worklist, oldest first, with read state per person.
  • Email as a conversation channel: a patient's email threads onto the right person, the clinic can start an email conversation, and patient notifications leave from a dedicated sending domain with delivery reports. Enabled per clinic.
  • Referral and fax intake: inbound referral documents are read and structured, with staff review before anything is confirmed; a referral that looks like a re-send is flagged where it cannot be missed.
  • Referral funnel report: received, confirmed, rejected, time to initiate and to first appointment, and staff time saved, by period and physician.
  • Outreach sequences: follow-up your clinic authors, including questions that wait for the patient's answer.
  • Intake work in the right order: in-progress referrals ranked by who needs the clinic first, each with its reason, a same-day reply goal on patient messages, and a weekly page showing how both are doing.
  • Referral status portal: a referred patient can check where their referral stands and supply what is missing.
  • Scheduling and the fertility clinical model, cycles, embryology, cryostorage and genetic testing as first-class records.
  • EMR integration: clinical data delivered to the systems a clinic nominates, in FHIR R4.
  • Approved replies: a clinic can hold the assistant to wording it has approved. At the strictest setting, anything not covered by approved wording goes to your team with no automatic reply by text, portal or email.
  • Assistant analytics: hours saved, resolution rate and satisfaction for the conversations the assistant handled.

Now: actively in development​

Intake & Referrals

  • Funnel analytics beyond the referral: the referral funnel report is live; the work now extends it from first inquiry, through booked consult, to started treatment, so clinic leadership can see exactly what the platform converts end to end.

Clinical Copilot & EMR

  • Fertility-native clinical documentation. Consult notes, cycle summaries and referral letters drafted with fertility-specific context, from the consult itself, in the clinic's own structure: for a clinician to review and sign. A note reaches the record when a clinician signs it and only then; a draft is checked against what was actually said, and what it cannot support is shown rather than smoothed over. General-purpose transcription mishears fertility vocabulary, so getting protocols, medications and cycle language right is a requirement rather than a refinement. In controlled rollout: off by default and switched on per clinic, deliberately, after the privacy assessment that handling consultation audio requires; see AI Scribe for what it does today.

Patient Communication

  • Expanded language coverage: the interface and patient-facing wording already ship in more than twenty languages, and the Scribe transcribes in the language spoken and can write a document in another, and the assistant already answers in European Portuguese on the phone and in the portal; the work now is the assistant's own spoken and written languages across every channel, so a clinic can meet patients in the language they are most comfortable in.

Trust & Compliance

  • HIPAA-aligned security program: formal Security Risk Analysis, Business Associate Agreements supported as standard, and continuous vulnerability scanning.

Next: coming up​

Clinical Copilot & EMR

  • Deeper EMR integration and write-back: structured intake data and drafted documentation flow into the clinic's existing fertility EMR, so staff work where they already work. Named integrations will be announced as they ship.

Intake & Referrals

  • Insights from the calls your team handles: the call transcription behind the voice agent, applied to the calls your staff answer, where the clinic turns it on and call-recording notice is in place. It flags a missed booking or a follow-up nobody picked up, gives coaching cues, and shows why an inquiry did not convert. A clinic that is not ready to let the assistant answer the phone still gets value from its own calls in the first week.
  • Appointment and billing analytics: extending today's assistant reporting into the rest of the funnel.
  • Leadership dashboards: response times, inquiry volume by channel, staff hours deflected, and waitlist movement in one view, building on the weekly reply times intake teams already see.
  • Configurable guardrails and approval workflows: escalation rules and routing logic that match your clinic's protocols, building on the approved replies clinics can already set.

Patient Communication

  • Support between visits: most of a cycle happens away from the clinic. The patient companion is being extended to the stretches in between: stimulation days, medication timing, the two-week wait, and coverage and benefits questions. It works from the clinic's own protocols and instructions, and anything clinical goes to the care team.
  • Patient companion enhancements: deeper personalisation and clinic branding options.

Trust & Compliance

  • SOC 2 Type II attestation (planned): independent audit of our security controls, available to enterprise security teams under NDA once complete.
  • Continuous compliance tooling: automated evidence collection and control monitoring, the prerequisite for that audit.

Later: on the horizon​

Agents across the clinic

  • From answering to acting: the assistant moves from answering and drafting to carrying out multi-step work across the clinic's systems, such as chasing a missing referral document, rebooking around a cancelled monitoring slot, or preparing a cycle brief before a review consult. Each agent works within permissions the clinic sets, and higher-risk actions wait for a staff member to approve them.
  • An action record the clinic can inspect: every step an agent takes is recorded for the clinic (what it looked at, what it did, and who approved it), with sensitive details masked, so a privacy officer can review it.
  • Hard boundaries between clinics: each clinic's agents, data and permissions are kept apart from every other clinic's, including between sites of the same network unless the network chooses to share.

Clinical Copilot & EMR

  • Support after a failed cycle: when a cycle does not succeed, the clinician gets a brief that draws on the patient's cycles to date, the Scribe drafts the review consult for the clinician to check and sign, and the patient companion supports the patient in the days before that consult. It is the first use of longitudinal patient context (below), at a point where many patients step away from treatment.

Platform & Interoperability

  • Deeper interoperability: standards-based connections to EMRs, labs and partner systems, in both directions.
  • Specialist clinical and lab tools, connected rather than rebuilt: embryo assessment, lab quality control, dosing and clinical decision support stay with the specialist tools a clinic chooses. Fertiligent brings their results into the patient's record, so clinicians and the assistant work from them.
  • Longitudinal patient context: a clinical context layer spanning a patient's full history across cycles and protocols, including results from those specialist tools.
  • Care-coordination automation: self-serve booking and follow-up sequencing across the whole patient journey.

Multi-site & networks

  • Network administration: central configuration, single sign-on, role-based access and per-site customisation for groups running several locations.
  • Cross-site benchmarking: intake performance and patient-experience measures compared across a network.

Trust & Compliance

  • Expanded certifications and residency: an ISO 27001 pathway, regional data residency options, and privacy programmes for the jurisdictions our clinics operate in, including PIPEDA, Quebec Law 25 and GDPR.

Last reviewed: 2026-10-15. Maintained by the Fertiligent product team. Have a request, or want to influence what we build next? Talk to your account team or email info@fertiligent.ai, what customers are waiting on is the strongest input we have.