Rebuilt from two decades of clinical practice
The clinical information system for IVF and reproductive genetics.
One record from first consultation to live birth — work-up, stimulation, egg retrieval, embryology, andrology, PGT, cryostorage and outcome. Purpose-built for assisted reproduction, not adapted from a general hospital system.
- 11
- clinical domains
- ~130
- clinical data entities
- 33
- PDF report templates
- 5
- integration standards
Follicles ≥14 mm
11
Endometrium
9.8 mm
OHSS risk
Moderate
Illustrative interface. No patient data is shown.
Why purpose-built matters
An IVF cycle does not fit in a general hospital record.
A general EMR models an encounter and a diagnosis. An ART programme models a couple, a cycle, a cohort of oocytes, each embryo and its daily grade, the biopsy taken from it, the genetic verdict returned, the straw it was vitrified into and the goblet that straw sits in — and, eighteen months later, the child.
Clinics bridge that gap with spreadsheets, lab notebooks and a second system for the genetics laboratory. Every bridge is a place where a chain of custody breaks and where the numbers you report to a registry stop reconciling with the numbers in the lab.
FertiliCore closes it. Every stage of the journey is a first-class record in one database, related to the ones before and after it, under one audit trail.
The full journey
Eleven clinical domains, one continuous record.
Roughly 130 clinical entities spanning registration to live-birth outcome. Follow any stage into its detail.
Clinical modules
Depth where the work actually happens.
Patient file & clinical work-up
Registration, anamnesis, examination, diagnosis
ExploreTreatment cycles & monitoring
Stimulation, follicular tracking, egg retrieval
ExploreEmbryology laboratory
Culture, grading, biopsy, transfer, thaw
ExploreAndrology & semen analysis
Spermiogram, MSOME, male factor
ExploreReproductive genetics & PGT
PGT-A/SR/M, FISH, QF-PCR, carrier panels
ExploreCryostorage & cryobank
Tank register, storage map, freeze & thaw
ExplorePregnancy & birth outcomes
Follow-up, delivery, neonatal outcome
ExploreReporting & analytics
Dashboards, PDF reports, data exports
ExploreThe differentiator
A genetics laboratory, not a genetics checkbox.
Most IVF systems record a PGT verdict as a single field: normal, abnormal, no result. FertiliCore models the laboratory that produced it — the array-CGH matrix chromosome by chromosome, the marker genotypes behind a monogenic call, the FISH signal counts, the contamination check that proves the sample was the embryo's.
PGT-A · array CGH result matrix
Illustrative. No patient data is shown.
Integration platform
Speaks the standards your estate already speaks.
Five connectors, each its own service. Every one ships switched off and stays that way until your team configures and enables it — nothing talks to the outside world by accident.
Trust & governance
Built for the inspection you have not been told about yet.
Isolation, accountability and access control are properties of the database, not promises made by the application layer.
Multi-tenant isolation at the database
Every clinic-scoped table carries a tenant marker protected by PostgreSQL Row-Level Security. One clinic physically cannot read another's rows — the boundary is enforced beneath the application, not by it.
Append-only audit trail
Database triggers log every insert, update and delete with before-and-after values, the acting user, tenant, IP address and session. The trigger auto-attaches to new tables, so coverage never drifts, and the log rejects updates and deletes.
Role-based access control
Permissions are granted per module, screen and operation, with seeded clinical roles — IVF doctor and nurse, embryology lab, andrology, genetics doctor and lab, patient consultant, viewer — and two-factor authentication required for system administrators.
Approval and sign-off workflows
A templated approval engine routes records such as genetic reports through sequential, unanimous or any-one approver chains with SLA deadlines, reminders, escalation and delegation. Every decision is permanently recorded.
Consent and witnessing records
Consent templates produce consent records that carry signatures, with a per-cycle consent checklist so a missing form is visible before the procedure rather than after it, and a witness-event log against the handling steps that require a second pair of eyes.
Scheduling and daily worklists
A shared resource calendar plus the lists a unit actually runs its morning on — retrievals, transfers, β-hCG due, scans, day-three checks and deferred cases — alongside a call and recall log.
Document retention
Consents, scanned forms and external reports attach to any clinical record and are held in S3-compatible object storage with server-side content sniffing and SHA-256 checksums. Documents are soft-deleted only — deleting a record never destroys its paperwork.
Notifications
A data-driven engine maps clinical events — OPU scheduled, fertilisation result, transfer done, β-hCG reminder, PGT result ready, cryostorage expiry — to recipient roles, templates and channels, with per-user preferences, quiet hours and retry.
Your data stays where you decide.
FertiliCore deploys into your own environment — inside the clinic, or in a private cloud tenancy you control — as a set of containers. There is no shared multi-tenant estate you are obliged to join, and no jurisdiction imposed on your patient records by our hosting choices.
Deployment optionsEnglish, Turkish and Arabic.
The interface, the validation messages and the clinical reference lists are translated, not machine-substituted — including full right-to-left layout for Arabic. Patient-facing documents such as discharge summaries and spermiogram reports exist as matched English and Turkish templates.
English Türkçe العربية
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.