Comparison
FertiliCore vs MedITEX IVF
MedITEX is the most widely deployed fertility system in Europe and the reference implementation in several national registries. This page sets out where FertiliCore is genuinely different, and where MedITEX remains the safer choice.
Their product
Who MedITEX IVF is.
Described from the vendor's own published materials. Figures a vendor states about itself are presented as their claims, not as verified fact.
MedITEX IVF is developed in Regensburg, Germany by a company founded in 2000, now trading as NEXUS / MEDITEX GmbH after NEXUS AG acquired a majority stake in the former CRITEX GmbH in 2025. It is the established incumbent in German-speaking Europe and the data carrier for several national registry returns.
The vendor states that MedITEX is used by 500 clinics in 54 countries, in 14 languages, covering seven million cycles. Their published product family covers the clinical record, a scheduler, an accounting module, statistics, a patient portal branded MedITEX Connect, a patient app, a digital history-intake survey and registry export.
On registries their published materials are unusually specific, naming DIR in Germany, FIVNAT in France, HFEA in the United Kingdom, ANZARD in Australia and New Zealand and RetePMA in Italy. Interfacing is offered through a REST API alongside named device interfaces for semen analysers, incubators and ultrasound.
Side by side
Twelve capabilities, the same twelve on every page.
Where a row reads not published, it means we could not find the capability described in the vendor's public materials — which is not the same as it being absent from their product. Ask them directly.
| Capability | FertiliCore | MedITEX IVF |
|---|---|---|
| Reproductive genetics assays modelled Running the laboratory, not only filing its result | Yes aCGH matrices, FISH, QF-PCR, Y-microdeletion, HLA, fragile-X, thrombophilia, DNA fingerprint | Not published Not described in their published materials |
| Per-chromosome PGT result matrix | Yes Copy number per chromosome per embryo, plus segmental imbalances sized in megabases | Not published Not described in their published materials |
| Cryostorage mapped to straw position | Yes Tank, canister, goblet and straw as a physical position register | Not published Not described in their published materials |
| On-premise deployment | Yes Containerised, your hardware, standard PostgreSQL | Not published Not described in their published materials |
| Arabic interface, right-to-left | Yes English, Turkish and Arabic — server messages and clinical lookups included | Not published Not described in their published materials |
| HL7 v2, FHIR R4 and DICOM published | Yes Five connectors, each shipping disabled until configured | Partial A REST API plus named analyser, incubator and ultrasound interfaces |
| National registry submission | Partial A general submission connector, proven against one registry | Yes DIR, FIVNAT, HFEA, ANZARD and RetePMA named on their own materials |
| Consent records and witness-event log | Yes Templates, signatures, per-cycle consent checklist, witness events | Not published Not described in their published materials |
| Barcode or RFID witnessing hardware Scanning at the bench, at each handling step | No No first-party hardware — integrate the witnessing vendor you choose | Not published Not described in their published materials |
| Billing and revenue cycle | No Deliberately out of scope — integrates to your finance system | Yes Accounting module in the published product family |
| Patient-facing portal or app | No Not offered today | Yes MedITEX Connect portal and a patient app |
| Donor programme management | No Sperm source is recorded; there is no donor registry or matching | Not published Not described in their published materials |
Be fair first
Where MedITEX IVF is the better choice.
A comparison page that finds no merit in the competitor is an advertisement. These are the cases where we would tell you to buy theirs.
Registry coverage across Europe
Five national registries named on their own materials, including the German DIR. If you must file a statutory return in one of those countries, MedITEX has been doing it for years and FertiliCore has not. This is the single most concrete reason to choose them.
Installed base and continuity
Twenty-five years and, by their own account, several hundred clinics. Reference sites are easy to find, staff move between clinics already knowing the software, and the roadmap is backed by a listed parent company.
Commercial completeness
An accounting module, a patient portal and a patient app are all part of the published product family. FertiliCore has none of the three. If you want the clinical record and the invoice in one system, that is a real advantage.
The difference
Where FertiliCore is a different kind of system.
The genetics laboratory itself
MedITEX's published materials describe fertility clinic management; they do not describe running a reproductive-genetics laboratory. FertiliCore models array-CGH result matrices chromosome by chromosome, marker-level allele tables for monogenic and HLA cases, FISH signal counts, QF-PCR panels and DNA-fingerprint contamination exclusion. If your unit runs PGT in house rather than sending it out, this is the difference.
Deployment you control
FertiliCore is installed into your own infrastructure or a private cloud tenancy in your name, on standard PostgreSQL, with tenant isolation and audit enforced by the database. Your data-residency answer is your own hosting decision rather than your vendor's.
Independence after consolidation
MedITEX now sits inside NEXUS AG's women's-health portfolio. That may be entirely good for its roadmap — but it is a change of owner, and clinics reasonably ask what it means for pricing and direction. FertiliCore is built by an independent engineering company that sells software and nothing else.
Arabic, properly
We found no Arabic interface described in MedITEX's published materials. FertiliCore runs in English, Turkish and Arabic, right-to-left, with server-side validation messages and clinical lookup values translated rather than only the front-end strings.
Pick MedITEX IVF if
Choose MedITEX if you file to DIR, FIVNAT, HFEA, ANZARD or RetePMA, if you want billing and a patient portal from the same vendor, or if a large European reference base is the deciding factor.
Pick FertiliCore if
Choose FertiliCore if you operate your own genetics laboratory, if your data must stay on your infrastructure or in a specific jurisdiction, or if you need a genuine Arabic interface.
FertiliCore and MedITEX IVF
Can FertiliCore file our German DIR return?
Not today. FertiliCore has a national ART registry submission connector, but it is built and proven against one registry rather than five. If a DIR, FIVNAT, HFEA, ANZARD or RetePMA return is a hard requirement for you now, MedITEX is the lower-risk answer and we would tell you so directly.
We already run MedITEX. Can our data be migrated?
In principle yes — migration from an existing clinical system is the normal case for us rather than the exception, and the product itself began as a migration carrying two decades of records. In practice it depends entirely on what export you can obtain from your current installation, which is a question for your vendor before it is a question for us.
Is FertiliCore cheaper than MedITEX?
Neither vendor publishes prices, so anyone claiming to answer this is guessing. What we can say is how we charge: per clinic rather than per user, with implementation and migration quoted separately and explicitly.
Sources and method
This comparison was last reviewed in July 2026. Every statement about MedITEX IVF is drawn from the vendor's own published materials, linked below, and clinic counts or country counts a vendor publishes about itself are presented as that vendor's claim rather than as verified fact. Software changes; if you believe anything here is out of date or unfair, write to omnia@omnicore.com.tr and we will correct it. MedITEX IVF and other product names are the trademarks of their respective owners, and no affiliation or endorsement is implied.
Other comparisons
Compare it against your own case
The most useful comparison is not a table. Bring a real case — a PGT cycle, a difficult cryo audit, a migration you are dreading — and we will show you how it goes through.