Clinician-supervised AI

The Complete AI Medical Scribe for Fertility & IVF Clinics

One AI scribe for the whole fertility journey, documenting every encounter, referral, call, and message, and turning it into a structured record your clinicians simply review and sign. Built for fertility, with your team in control and your data your own.

Today it documents the consultation, reads your referrals, and captures every patient call and message. This is where it's going: the scribe that does the entire documentation job, so your team can get back to care.

Fertility teams drown in paperwork

Clinicians spend nearly six hours a day in the EHR, about half of it on clerical work.

The evidence is clear. Across published clinical evaluations, AI scribes have cut charting time by 10–70% and lowered clinician burnout, from 51.9% to 38.8% in a multicenter JAMA study, saving roughly three hours of after-hours admin a week, with clinician oversight of every note. A scribe built for fertility should relieve that burden across the whole journey: referrals, consults, monitoring, calls, and patient messages.

The words a fertility note is written in

A general scribe hears English. A fertility clinic speaks something else.

A reproductive endocrinologist (REI) works in a dialect. Ovarian reserve is an AMH and an antral follicle count. A stimulation is a protocol, agonist or antagonist, a starting dose in units, then an estradiol, an endometrial thickness and a follicle count by side at every scan, and a trigger timed to the hour. An egg retrieval is reported as oocytes retrieved, mature and fertilized, an embryo is a day-5 blastocyst with a grade in the lab's own nomenclature and, more often each year, a PGT-A result, and a transfer is one embryo or two, fresh or frozen, on a medicated or a natural preparation, followed by luteal support and a beta hCG on a date. IUI, ICSI, FET, HSG, hysteroscopy, ERA. A general-purpose scribe transcribes this phonetically and then writes fluent prose around the mishearing, which is the worst failure a note can have, because it reads well.

We treat the dialect as data rather than vocabulary. Each encounter type carries the values its note needs: a cycle monitoring scan wants cycle day, estradiol, endometrial thickness and follicles by side; a retrieval debrief wants oocytes retrieved, mature and fertilized; a transfer note wants embryos transferred, their stage and how the transfer went. While the encounter is running, the scribe shows which of those it has not heard yet, so how many were frozen gets asked in the room and not reconstructed at the desk afterwards. A value lands in the note with its unit or it does not land at all. A grade is written as the embryologist gave it. And every sentence in the draft points back to the line of transcript it came from, so a clinician checking antagonist from tonight is one click from reading it said. None of this replaces the signature. It is what makes the signature quick.

Ambient, dictation, or a person in the room

Three different things get called a scribe, and they fail differently.

Dictation transcribes what a clinician says on purpose, after the visit, accurate, and still an extra task at the end of the day. A human scribe captures the visit as it happens and costs a salary per clinician, which is why the model has never scaled past the practices that can afford it. An ambient AI scribe listens to the encounter itself and drafts from it (the category is also called ambient clinical documentation), so nothing is said twice, and its failure mode is different in kind: it can write a confident sentence the conversation did not support. That is why every sentence we draft is traceable back to the line of transcript it came from, and why a clinician signs before anything enters the record. We have written up the three models in full, including how consent differs between them.

What the first week looks like

No migration, no switchover weekend. The work is templates and consent wording.

Day one is your note templates: we take the formats your clinicians already sign (consultation, monitoring, IUI, IVF and FET) and set the scribe to draft into them rather than into a shape of ours. Day two is the consent script, reviewed with your own counsel, because the clinic is the custodian of the record and the wording has to match the retention setting the clinic chooses. Then one clinician runs it in clinic for a few days with every note reviewed line by line, which is how the template corrections get found. Most clinics are signing scribe-drafted notes in the first week and have the whole team on it within two or three. Nothing is migrated and nothing is switched off, so there is no day on which the old way stops working.

It writes into the EMR you already run

We do not ask a clinic to change its EMR.

The scribe drafts the note, the clinician signs it, and on the platform the signed note is written into your chart by an integration we configure for your clinic during onboarding. Clinics we work with run eIVF, IDEAS, BabySentry, Artisan, MedART and Meditex, and hospital-based programs run Epic or Cerner; we scope the integration to whichever your clinic has. The integration is one-way by design: it writes the signed note into the record and never reads back or alters what is already in the chart. That is the arrangement most clinic privacy officers ask for first, and it keeps the EMR as the system of record. On a scribe seat alone it runs standalone: sign the note, copy it into the chart. There is no data migration, no schema to map, and no switchover weekend, which is why getting started is measured in days rather than quarters. What each plan includes is on the pricing page. What the scribe writes is structured from the start, which is the same foundation our approach to data management for fertility clinics is built on. The scribe is one part of the wider IVF clinic software; what it records is delivered to your record system through EMR integration. On the patient side of the same platform, AI patient support for fertility clinics answers calls and messages, and the AI fertility companion answers patients between visits.

Questions clinics ask us

The ones that come up in the first call, answered as directly as we can.

Does it work for IVF clinics specifically, or is it a general scribe?

Fertility is the only thing it does. There is no general-practice version of this product that a fertility mode was added to: the note templates are cycle templates, the measurements it writes are follicle and endometrial measurements, and the vocabulary is protocols, gonadotropins, grading and PGT. That is a narrower product than a general scribe on purpose. It is also why a monitoring visit comes out as comparable values rather than a paragraph.

Which EMR systems does Fertiligent Scribe work with?

The one your clinic already uses. Integration is configured per clinic during onboarding and comes with the platform rather than a scribe seat. Clinics we work with run eIVF, IDEAS, BabySentry, Artisan, MedART and Meditex, and hospital-based programs run Epic or Cerner; we scope the integration to whichever of these, or another, your clinic has. It is one-way: it writes into the chart and nothing already there is altered. Scribe seats on their own run standalone, and your team copies the signed note across.

Who signs the note?

Your clinician does. The scribe produces a draft in which every sentence is traced back to the line of transcript it came from, and it flags anything the consultation did not support rather than filling the gap. Nothing enters the record until a clinician has reviewed and signed it.

Does it cover more than the consultation?

Yes. Today it documents the consultation, reads incoming referrals into a structured record, and captures patient calls and messages. Monitoring visits are handled with cycle-aware measurements so the note carries what a monitoring visit is supposed to carry.

How is this different from ambient dictation?

Dictation records a clinician describing the visit, usually afterwards. This listens to the visit itself, so nothing is said twice, no one narrates a consultation they have just had. The trade-off is that an ambient system can draft a sentence the conversation did not support, which dictation cannot. We handle that by tracing every drafted sentence back to the line of transcript behind it and flagging what the encounter did not cover, rather than filling the gap.

What happens to the audio after the note is written?

By default it is deleted as soon as the transcription completes, the retention period ships set to zero days, so keeping audio is something a clinic switches on deliberately rather than something it has to switch off. If you do set a retention period, the consent script the clinician reads changes to match it, and the system refuses to record at all if no approved wording describes the setting truthfully.

How long does it take to get running?

Days to a couple of weeks for a first clinic. Most of that is setting up your note templates and getting clinicians comfortable with the review and sign-off step. There is no EMR migration to wait on either way; on the platform the integration is configured during that same onboarding.

How much time does it actually save?

We don't publish our own figures yet. The independent evidence on ambient AI scribes reports documentation-time reductions ranging from about 10% to 70% depending on setting, and a measurable drop in clinician burnout. The sources are footnoted above. We'd rather you measure it on your own referrals and calls than take a number from us.

Can we see it before we commit?

Yes. Book a demo below and bring your own de-identified referrals and call recordings. There is also a live demo you can try yourself at fertiligent.ai/demo, which runs on a fictional clinic with synthetic data.

Which languages and accents does it handle?

Each clinic is configured for one transcription language; the default is Canadian English. Other languages Azure Speech supports can be set up for your clinic. It does not currently switch between languages inside a single consultation, so a genuinely bilingual encounter is not something we would claim to handle well yet.

Hosting region, subprocessors, the BAA, retention and what happens to your data when you leave are set out in full on the security and data handling page.

See it on your own referrals and calls

Book a short demo and watch Fertiligent document a consultation, read a referral, and summarize a call in real time, then see the roadmap to the complete scribe.

Bring your own de-identified referrals and call recordings if you have them. Nothing you send here is used for anything but arranging the demo.

We use these details to arrange your demo and to follow up about Fertiligent. See our Privacy notice