Clinical module
One cycle, from stimulation day one to the beta
A FertiliCore treatment cycle is the parent record for one ART attempt: attempt number, modality, protocol, responsible clinician and embryologist, and the landmark dates. Daily monitoring, the oocyte pick-up and the cycle outcome all hang off it, with coded cancellation reasons at both cycle and retrieval level.
- Cycle, monitoring and OPU are built, usable screens
- Ten seeded cycle cancellation reasons, five for OPU
- Nine stimulation protocols in the clinic-wide catalogue
- Oocyte yield split by MII, immature and degenerate
The cycle record as the spine of the attempt
Everything a clinic does in an ART attempt needs a single anchor, and in FertiliCore that anchor is the treatment cycle. It fixes the patient, the attempt number, the modality and the stimulation protocol family, names the responsible physician and embryologist, and holds the landmark dates: cycle start, retrieval, transfer and the beta-hCG draw. The cycle cannot be reassigned to another patient once created. Its status moves through planned, active, in progress, completed or cancelled, and a lock flag freezes the record when the episode closes.
- Modalities offered on the form: IVF, ICSI, FET, IUI, donor egg, donor sperm, natural, cryo donation
- Protocol picker: long agonist, short antagonist, mini IVF, natural, modified natural
- Optional cycle group for batching related cycles
- Detail drawer with General Info, audit History and Files tabs
Stimulation and trigger timing
The cycle's protocol label says which family of regimen was chosen; the detail of the drug exposure is modelled separately. The record captures the gonadotropin agent and dose, the total ampoules consumed across the cycle, the number of stimulation days, and the trigger agent and dose. It also holds the trigger date and the exact trigger time, which matters because retrieval is scheduled roughly 34 to 36 hours afterwards and an hour of drift changes what comes back from the follicle. A clinic-wide catalogue of nine induction protocols is seeded for administrative use.
Daily monitoring during stimulation
Serial monitoring is where dose decisions are actually made, so each monitoring visit is one row on a sheet rather than a note. The row carries the cycle day, the hormone panel and the transvaginal ultrasound findings side by side: oestradiol as the marker of follicular response, LH watched for a premature surge, progesterone for endometrial timing, FSH and beta-hCG. Alongside them sit endometrial thickness and pattern, follicle counts for each ovary, and the individual follicle diameters per side. Medication notes and the next visit date close the row, so the sheet reads as a decision trail rather than a data dump.
- Hormone panel: E2, LH, FSH, P4, hCG with units
- Endometrial thickness in millimetres, plus coded pattern
- Right and left follicle counts with individual diameters
- Dose-adjustment instructions and scheduled next visit
- Rows can be locked once reviewed
Oocyte retrieval
The OPU record documents the theatre event and the harvest. It holds the procedure date and time, the anaesthesia description and anaesthetist, the operating physician and the embryologist receiving the oocytes. The yield is recorded as more than a single number: follicles aspirated and oocytes recovered per ovary, then the maturity breakdown into mature MII, immature MI and germinal vesicle, and degenerate, along with the count of empty follicles. That breakdown is what makes the difference between a poor retrieval and a poor stimulation visible after the fact. The sperm source for the cycle and any complications are recorded on the same header. Beneath it, the system models a per-follicle aspiration grid — one row per follicle with side, sequence number, measured diameter, whether an oocyte was obtained and its maturity grade — and a dated theatre worklist of patients booked for retrieval.
Cancellation recorded as a reason, not a status
A cancelled cycle is a clinical event with a cause, and treating it as a coded value rather than free text is what makes cancellation rates analysable. FertiliCore seeds ten cycle-level cancellation reasons — poor response, OHSS risk, no follicle development, patient request, medical, financial, premature LH surge, endometrial problem, freeze-all and other — and a separate five-value list at retrieval level for premature ovulation, patient refusal, no follicle on follow-up, anaesthesia risk and other. Freeze-all sits in the cycle list deliberately: it is a planned deviation, not a failure, and should not be counted as one.
Closing the loop, and what came before
The cycle outcome is held as exactly one record per cycle, which makes it the single source of the result. It carries the quantitative beta-hCG value and date, the positive, negative or borderline interpretation, whether a clinical pregnancy was confirmed on ultrasound, fetal cardiac activity, the gestational sac count and the eventual outcome. Adjuvant medication and luteal-phase support are modelled with drug, dose, route, frequency and treatment window, and post-transfer monitoring tracks progesterone, beta-hCG and oestradiol through the early luteal window. Prior attempts made at other clinics are held against the patient with year, modality, clinic, treating doctor and result, so protocol choice is informed by what has already been tried.
Field level
What the record actually holds.
Structured fields, not a free-text note — which is what makes the reporting and the registry returns downstream possible.
Cycle master record
- Attempt number for this patient
- Treatment modality and protocol family
- Cycle start and end dates
- Planned or actual retrieval and transfer dates
- Beta-hCG test date
- Responsible physician and embryologist
- Optional cycle group or batch
- Coded cancellation reason and notes
Stimulation and trigger
- Gonadotropin agent and dose
- Total ampoules consumed
- Number of stimulation days
- Trigger agent and dose
- Trigger date and exact trigger time
Daily monitoring
- Monitoring date and stimulation day number
- Oestradiol in pg/mL
- LH and FSH in mIU/mL
- Progesterone in ng/mL
- Beta-hCG in mIU/mL
- Endometrial thickness in mm and coded pattern
- Right and left follicle counts
- Individual follicle diameters per side
- Dose-adjustment and medication instructions
- Scheduled next monitoring date
Oocyte retrieval
- Procedure date and theatre time
- Anaesthesia type and anaesthetist
- Operating physician and receiving embryologist
- Follicles aspirated, right and left
- Oocytes recovered, right, left and total
- Mature MII oocyte count
- Immature MI and germinal-vesicle count
- Degenerate oocyte count
- Empty follicle count
- Sperm source for the cycle
- Intra- and post-procedure complications
Per-follicle aspiration detail
- Ovary side, right or left
- Follicle sequence number
- Measured follicle diameter in mm
- Oocyte obtained, yes or no
- Maturity grade: MII, MI, GV, degenerate or empty
- Intra- and extracytoplasmic morphology codes
Medication and outcome
- Adjuvant drug, dose, route, frequency and window
- Luteal-phase support drug and dosing detail
- Quantitative beta-hCG value and date
- Positive, negative or borderline interpretation
- Clinical pregnancy confirmed on ultrasound
- Fetal cardiac activity and gestational sac count
- Final outcome type and date
- Prior attempts elsewhere: year, modality, clinic, result
Common questions
Which parts of the cycle pathway are click-through screens today?
The treatment cycle record, the daily cycle monitoring sheet and the OPU procedure each have a full list, create and detail-with-inline-edit screen set, and OPU access is governed by its own permission group. The remaining tables in this domain — stimulation protocol detail, per-follicle grid, adjuvant and luteal medication, cycle outcome, prior attempts and the theatre day list — are modelled, stored and exposed over the API, with dedicated front-end screens planned rather than built.
How is the trigger-to-retrieval window handled?
The stimulation record holds the trigger agent, its dose, the trigger date and the exact trigger time. Retrieval is conventionally booked 34 to 36 hours after trigger, so capturing the time rather than just the date is what makes the retrieval slot defensible. The OPU record separately holds its own procedure date and time, so planned and actual timing can be compared.
Can we report on why cycles were cancelled?
Yes. Cancellation is a coded lookup rather than free text, with ten seeded reasons at cycle level and five at retrieval level, and both lists remain administrator-editable. Because freeze-all is one of the seeded cycle reasons, an elective segmentation can be separated from a genuine failure when cancellation rates are analysed. A free-text note sits alongside the code for case-specific detail.
Is oocyte yield recorded in enough detail for laboratory KPIs?
The retrieval header separates follicles aspirated from oocytes recovered on each side, then breaks the total into mature MII, immature MI and germinal-vesicle, and degenerate, plus a count of empty follicles. Maturity rate therefore falls out of the record rather than being estimated. The system additionally models a per-follicle grid recording side, sequence, measured diameter, whether an oocyte was obtained and its maturity.
What happens to treatment history from another clinic?
Prior ART attempts are held against the patient with the year, the modality, the clinic where it was performed, the treating physician and the outcome. This is the context that shapes protocol choice for a poor responder or a repeated-failure case. It is stored and exposed through the API, and it also feeds the Previous IVF Attempts export.
Continues into
See FertiliCore against your own workflow
A working walkthrough with one of our clinical engineers — patient file to live-birth outcome, plus the integration and deployment questions your IT team will ask. No obligation, and no sales script.