IVF Assistant LAB
In active development · early access for pilot clinics

The IVF lab platform, built by an embryologist.

Traceability, witnessing, cryostorage mapping, device monitoring and KPIs — in one system that a working laboratory actually wants to use. Designed on the bench at a functioning IVF centre, not in a product meeting.

Not yet cleared for real patient data — see current status.

The problem

Lab software is usually written by people who have never worked a lab day.

So the witnessing step is an afterthought, the cryo map lives in a spreadsheet, the QC binder is paper, and the KPIs arrive three months late — if at all. Meanwhile the embryologist is the one holding it all together, by memory.

What lab teams end up doing
  • Chasing lot numbers and expiry dates across three different places
  • Keeping the cryo tank map in a spreadsheet nobody dares to edit
  • Re-typing the same patient data into the EMR, the sheet and the log
  • Signing witnessing on paper, then filing it and hoping it's found at audit
  • Calculating KPIs by hand, once a quarter, from exported CSVs
  • Coordinating a time-critical lab day over WhatsApp
The platform

Six domains, one dataset, entered once.

Each area of the lab gets its own workspace, but they share one record. Data captured at the bench propagates to inventory, custody, cryo and KPIs without anyone re-typing it.

01

Daily Workflow

The lab day, sequenced and prepared.

  • Time-critical procedure timeline & countdowns
  • SOP-driven prep calculator (volumes, dishes)
  • Inventory, QC & lot traceability
  • Role-aware mobile delivery
02

Clinical & Embryology

The complete follow-up file and the paper-free lab sheet.

  • Patient file: history, male factor, stimulation, outcome
  • Embryology sheet with Gardner grading
  • PGT & biopsy chain tracking
  • Andrology laboratory
03

Cryo & Custody

Where every sample is, and who touched it.

  • Cryostorage tank, cane and position mapping
  • Unified chain of custody
  • Double-witnessing with named operator and witness
  • One custody log — every module writes into it
04

Analytics & Intelligence

KPIs continuously, not quarterly.

  • Lab & clinical KPIs benchmarked to ESHRE / Vienna
  • Lot-number intelligence and drift signals
  • Real cost per cycle, oocyte and blastocyst
  • Correlation panels with sample-size gating
05

Quality, Safety & Devices

Audit-ready without the binder.

  • Continuous incubator and device monitoring
  • Quality management: CAPA, non-conformance, readiness
  • Troubleshooting knowledge base — the lab's memory
  • Lab design & compliance layout
06

Platform & Admin

Who sees what, and where the data lives.

  • Role-based access and visibility matrix
  • Immutable audit log explorer
  • Bilingual English / Arabic interface
  • Data residency and self-hosting options
How it's built

The agent flags. The embryologist decides.

There is an intelligence layer, and it is deliberately disciplined. It records, correlates and raises things worth looking at. It does not make clinical decisions, and it is not allowed to confirm a witnessed step on your behalf.

Enter once

Any piece of data is captured in one place with one schema, then propagated wherever it's needed. No double entry, no second copy drifting out of sync.

Human in the loop

The system proposes; a qualified operator confirms. Clinical judgements and witnessed steps are always confirm-first — that's architectural, not a setting.

One custody log

Every module writes witnessing events into a single unified chain of custody. There is never a second, competing record for an inspector to reconcile.

Correlation is not proof

Outcome correlations are observed, not controlled — confounded by case mix, operator, incubator and era. The system labels them that way, in the interface, every time.

Sample-size gating

No ranking or "optimum" is shown below a real threshold. Sub-threshold data is still displayed, but marked ineligible rather than quietly excluded.

Data stays where it belongs

Built with a self-hosted, on-premises option in mind so clinics with data-residency obligations can keep patient data inside their own jurisdiction.

What we won't claim

Append-only is not the same as tamper-proof. A browser cannot record a true IP address. Risk-adjusted outcome comparison needs a defined case-mix methodology before it means anything — so those features stay gated until it exists, rather than shipping a number that looks authoritative and isn't.

Demonstration data is badged as demonstration data. If a feature is a recording layer without the downstream connection built yet, the interface says so.

Who's building it

"I built the thing I wanted to use at 6am on an OPU day."

Why that matters

Every workflow in the platform was specified by someone who performs it. The witness points are where they actually are. The prep calculator follows the SOP rather than estimating. The grading uses the Istanbul/Gardner convention the lab already writes on the sheet.

Clinical methodology and product direction are shaped together with a co-founding OB-GYN, so the lab-side and clinical-side views of a cycle stay consistent.

Where it stands today

Honest status, so you can judge for yourself.

This is a real, working system in active daily development — not a finished commercial product. Here is exactly where the line sits.

Interested in a pilot?

If you run or work in an IVF laboratory and any of this sounds like your Tuesday, get in touch. We're talking to a small number of clinics about early access — and we're just as interested in what we've got wrong.

We reply to every message. No mailing list, no drip campaign.
Please don't include patient-identifiable information in this form.

Prefer LinkedIn? Connect there instead.