# FertiliCore > FertiliCore is a clinical information system built specifically for IVF, assisted reproduction and reproductive genetics. It covers the whole treatment journey in one record — patient file and infertility work-up, treatment cycles and stimulation monitoring, oocyte retrieval, the embryology laboratory, andrology, PGT and the wider genetics laboratory, cryostorage, pregnancy follow-up and live-birth outcome — with HL7 v2, FHIR R4, DICOM, laboratory-device and national ART registry integration. It is deployed on-premise or in a private cloud the clinic controls, never as a shared hosted service. FertiliCore is developed by Omnicore Stratejik Teknolojiler Ltd. Şti. (TÜBİTAK Marmara Teknokent, Gebze / Kocaeli, Türkiye) — see https://www.omnicore.com.tr. It is a ground-up rebuild of a clinical system that had run real IVF and genetics laboratories for around two decades. The interface runs in English, Turkish and Arabic, including right-to-left layout. ## What makes it different The reproductive-genetics laboratory. Most IVF systems record a PGT outcome as a single verdict field, or interface to a reference laboratory to receive one. FertiliCore models the laboratory that produces the result: array-CGH matrices holding copy number per chromosome per embryo plus segmental imbalances sized in megabases, blastomere results scored nucleus by nucleus, marker-level allele tables for monogenic and HLA (saviour-sibling) cases, FISH cytogenetics and sperm FISH, QF-PCR, Y-chromosome microdeletion, fragile-X CGG repeat sizing, thrombophilia genotyping, and DNA-fingerprint checks for maternal-contamination exclusion. Second: deployment. The system runs inside the clinic's own infrastructure or a private cloud tenancy in the clinic's name, on standard PostgreSQL, with multi-tenant isolation enforced by row-level security and an append-only audit trail written by database triggers. ## What it does not do Stated plainly, because it matters when evaluating: there is no billing or revenue-cycle module, no patient-facing portal or app, no donor-programme registry or donor-recipient matching, and no first-party barcode or RFID witnessing hardware (a witness-event log and consent records exist; the scanning hardware does not). The national ART registry connector is a general submission mechanism proven against one registry, not many. Some of the clinical record is modelled and served through the API without yet having a dedicated data-entry screen. The product is in active development. ## Product - [Home](https://fertilicore.com/): What FertiliCore is and who it is for. - [Platform overview](https://fertilicore.com/platform/): The four layers — clinical record, integration, governance, deployment. - [Clinical modules](https://fertilicore.com/modules/): All eleven clinical domains, roughly 130 clinical entities. - [Integrations](https://fertilicore.com/integrations/): HL7 v2, FHIR R4, DICOM, laboratory devices, ART registry. - [Security and compliance](https://fertilicore.com/security/): Row-level tenant isolation, append-only audit, RBAC, approvals. - [Deployment](https://fertilicore.com/deployment/): On-premise and private cloud, stack, migration approach. - [Licensing](https://fertilicore.com/pricing/): Licensed per clinic; pricing quoted, not published. ## Clinical modules - [Patient file & clinical work-up](https://fertilicore.com/modules/patient-records/): One dossier per patient and a linked couple record, carrying reproductive and medical history, review of systems, gynaecological examination, HSG, hysteroscopy, laparoscopy and laparotomy records, coded infertility diagnoses and OHSS risk grading. - [Treatment cycles & monitoring](https://fertilicore.com/modules/treatment-cycles/): The cycle master record with stimulation protocol detail, daily follicle-scan and hormone monitoring, adjuvant medication and luteal support, the OPU procedure with a per-follicle aspiration grid, and the β-hCG cycle outcome. - [Embryology laboratory](https://fertilicore.com/modules/embryology/): Per-OPU embryology sessions, individual embryo records with a daily culture and grading log, pronuclear scoring, structured Gardner blastocyst grading, biopsy workflows for PGT, embryo transfer and thaw sessions. - [Andrology & semen analysis](https://fertilicore.com/modules/andrology/): Semen analysis against the WHO 2021 reference ranges, MSOME high-magnification organelle morphology for IMSI selection, the ICSI-bench spermiogram, male reproductive history and a composite male-factor evaluation. - [Reproductive genetics & PGT](https://fertilicore.com/modules/genetics-pgt/): A full reproductive-genetics laboratory: PGT-A, PGT-SR and PGT-M with array-CGH and blastomere result matrices, FISH cytogenetics, sperm FISH aneuploidy, QF-PCR, Y-chromosome microdeletion, HLA typing, fragile-X repeat sizing, thrombophilia panels and DNA-fingerprint contamination checks. - [Cryostorage & cryobank](https://fertilicore.com/modules/cryostorage/): A liquid-nitrogen tank register and a physical storage map down to tank → canister → goblet → straw, with oocyte vitrification, sperm cryopreservation, thaw registers, survival rates and tank occupancy. - [Pregnancy & birth outcomes](https://fertilicore.com/modules/pregnancy-outcomes/): Serial β-hCG and clinical pregnancy follow-up, antenatal checkups, structured pregnancy outcome, live-birth and neonatal records with APGAR, birth weight and anomalies, plus maternal complications and recurrent-loss work-up. - [Reporting & analytics](https://fertilicore.com/modules/reporting-analytics/): Nine statistics dashboards covering clinic, OPU, embryology, transfer, pregnancy, PGT, andrology, monitoring and cryo; 33 letterhead PDF report templates rendered on demand; and 12 raw-data Excel exports for ad-hoc analysis. ## Integration connectors - [HL7 v2 messaging](https://fertilicore.com/integrations/hl7-v2/) — HL7 v2.5.1: A bidirectional HL7 v2.5.1 interface with an MLLP listener and outbound client. Inbound ADT keeps demographics in step with the hospital information system; finalised laboratory results are dispatched outbound as ORU messages. - [FHIR R4 API](https://fertilicore.com/integrations/fhir-r4/) — HL7 FHIR R4: A FHIR Release 4 REST façade that exposes clinical data as standard resources, so modern EHRs, health-information exchanges and partner applications can read from FertiliCore without a bespoke interface. - [DICOM & DICOMweb](https://fertilicore.com/integrations/dicom/) — DICOM / DICOMweb: A DICOM C-STORE service class provider and DICOMweb endpoints that receive ultrasound and imaging studies from scanners and PACS, and bind them to the patient file and treatment cycle they belong to. - [Analyzers & time-lapse incubators](https://fertilicore.com/integrations/laboratory-devices/) — ASTM / HL7 ORU: Laboratory device connectivity over ASTM and HL7 ORU, by TCP feed or watched folder, covering hormone and general chemistry analyzers alongside time-lapse embryo incubators. - [National ART registry](https://fertilicore.com/integrations/art-registry/) — Registry submission: A submission connector for national assisted-reproduction registries, assembling the required cycle and outcome dataset from the clinical record and pushing it to the authority's endpoint on the mandated schedule. ## Comparisons with other IVF systems These pages state where the competitor is the stronger choice as well as where FertiliCore differs, source every claim to the vendor's own published materials, and carry the date they were last reviewed. - [All comparisons](https://fertilicore.com/compare/): Method, and the short version of the positioning. - [FertiliCore vs MedITEX IVF](https://fertilicore.com/compare/meditex-alternative/): MedITEX IVF by NEXUS / MEDITEX GmbH (formerly CRITEX GmbH), Regensburg, Germany. - [FertiliCore vs eIVF](https://fertilicore.com/compare/eivf-alternative/): eIVF by PracticeHwy.com, Inc., Texas, United States. - [FertiliCore vs IDEAS](https://fertilicore.com/compare/ideas-ivf-alternative/): IDEAS by Mellowood Medical Inc., Toronto, Canada. - [FertiliCore vs BabySentry](https://fertilicore.com/compare/babysentry-alternative/): BabySentry by BabySentry Ltd., Limassol, Cyprus. - [FertiliCore vs MedART](https://fertilicore.com/compare/medart-alternative/): MedART by Meddilink, India, with offices in Dubai, the United States and Switzerland. ## Company and contact - [About](https://fertilicore.com/about/): Why the system was rebuilt, and what carried over. - [FAQ](https://fertilicore.com/faq/): Scope, deployment, integration, migration and commercial questions. - [Request a demo](https://fertilicore.com/contact/): Contact form, or email omnia@omnicore.com.tr. - [Omnicore](https://www.omnicore.com.tr): The engineering company that builds and supports FertiliCore. ## Legal - [Privacy policy](https://fertilicore.com/legal/privacy/): Note that FertiliCore deployments are customer-controlled — we do not host or access patient data. - [Terms of use](https://fertilicore.com/legal/terms/) - [Cookie policy](https://fertilicore.com/legal/cookies/): No analytics, advertising or tracking cookies. ## Optional - [Expanded summary](https://fertilicore.com/llms-full.txt): The same material with per-module detail, for deeper retrieval.