The Complete
IVF EMR
for Fertility Clinics

Yes — MedART models every step of the IVF cycle as a structured longitudinal record, not free-text notes. The seven cycle stages — stimulation start, monitoring scans, OPU, fertilisation, embryo culture, transfer, and FET (or freeze-all + future warming) — each have first-class structured fields for protocol, dose, follicle count and size, hormone values, oocyte counts, fertilisation method, embryo grading, transfer day, and outcome. Pregnancy and live-birth outcomes feed back into the same cycle record so analytics, registry exports, and outcome benchmarking work without manual data collation. This structured granularity is what enables MedART to auto-export to SART/CDC/HFEA/ESHRE without re-keying — see the cycle workflow live in a personalised demo.

Yes — MedART models donor cycles (sperm, egg, or embryo), recipient linking, shared cycles, and surrogacy as first-class workflows, not workarounds layered onto a single-patient EMR. The data model supports: anonymous and known donor records with separately managed consent, recipient–donor linkage that preserves donor anonymity where required, surrogate-and-intended-parent linkage with the legal parent-of-record correctly recorded, shared cycles between linked patients (e.g. reciprocal IVF), and embryo lineage tracking across the donor → recipient → child chain. This is critical in jurisdictions where third-party reproduction is common (parts of the US, Georgia, Ukraine, Greece, parts of Asia) — and where the EMR's data model determines whether donor anonymity, legal parentage, and embryo provenance can be proved end-to-end. Book a walkthrough to see the donor and surrogacy data model in action.

Yes — MedART lets clinics build, version, and reuse their own stimulation protocols (long agonist, antagonist, mild, PPOS, dual-stim, microflare, mini-IVF, modified natural) with dose schedules, monitoring cadence, trigger criteria, and exit/cancel rules. Each protocol is named, versioned, and attributed to the clinician who created it; a cycle references a specific protocol version, so when a protocol is revised, in-flight cycles continue on their original version. This is essential for stimulation governance audits, outcome analysis by protocol version, and accreditation reviews — and prevents the "which version of the protocol was this patient actually on?" problem. See the protocol builder in a tailored demo.

Yes — MedART integrates with leading electronic witnessing systems including RI Witness and Matcher, so every gamete and embryo transfer is verified by two-person electronic witnessing with timestamp, operator identity, and ID-tag scan flowing into the cycle record automatically. Witnessing events appear in the MedART cycle audit trail alongside clinical and embryology events, so a single audit query returns the full custody chain for a specimen — from OPU through transfer or final disposition. For clinics not yet running electronic witnessing, MedART also captures manual two-person sign-off as a fallback, but electronic witnessing is the standard for outcome and liability protection. See the full integrations list.

Yes — MedART integrates with leading time-lapse incubators (EmbryoScope+, MIRI Time-Lapse, Geri+), standard incubators (Vitrolife G-185, K-Systems G210), and cryostorage management systems. Embryo morphology and time-lapse scoring data flows from the incubator into the cycle record without re-entry; cryostorage positions are tracked at the specimen level (tank → canister → cane → goblet → position), so a frozen embryo's location and warming history is one click away. This matters operationally because embryologists who duplicate-enter incubator and cryo data into a separate system spend hours a week on data hygiene — and any error in cryostorage position is a potential adverse event. See the integrations page for supported devices.

Migration from paper or a legacy IVF EMR to MedART follows a structured four-phase process: assessment (what data needs to come over and in what form), extraction (from paper via templated digitisation; from a legacy DB via HL7/FHIR export or direct database export), mapping (legacy fields → MedART schema, validated by a clinical reviewer), and parallel-run validation (every patient rendered side-by-side legacy vs MedART, signed off by the clinic before cut-over). The clinic owns its data throughout — Meddilink is the data processor, not the data controller — and final data-ownership and exit terms are written into the contract. Data migration is included in every MedART implementation package; clinics never pay a separate per-record migration fee. Book a migration scoping call to walk through your specific legacy system or paper-based workflow.