Home / Insights / Laboratory

Lab software for fertility clinics with in-house hormone testing

LaboratoryPublished 2026-11-189 min readInternational

Fertility clinics run some of the most time-sensitive testing outside a hospital. Estradiol, progesterone, LH and hCG results decide whether a patient triggers tonight, adjusts medication tomorrow or comes back in two days. When a clinic brings that testing in house, the lab software must keep up with the cycle. This guide covers what it needs to do.

Written and reviewed by the Catenix team. How these guides are written and checked.

In brief

  • Fertility testing is serial: the same patient is tested repeatedly through a cycle, and each result is read against the last.
  • Results must reach the clinician the same day, often within hours, and be visible in the clinic's own EHR or fertility system.
  • Repeat samples on the same day, new visits on new days and corrected results must all file correctly without duplicating or overwriting.
  • QC, operator competency and an audit trail matter as much here as in any lab, especially for clinics working toward accreditation.
  • Catenix supports in-house hormone testing on immunoassay analysers, with same-day reports, a per-visit record and cumulative result views.

Take it with you: POCT connectivity buyer's guide · POCT readiness checklist (PDF, no form).

Why fertility clinics bring testing in house

Sending cycle-monitoring bloods to an outside lab adds courier time and often means results arrive the next morning. In-house immunoassay analysers let a clinic draw blood in the morning and act on the result the same afternoon. The trade-off is that the clinic now runs a lab, with everything that implies: QC, competency, traceability and, in many cases, accreditation.

The tests and the timing

A typical in-house fertility menu includes estradiol, progesterone, LH, FSH, hCG, AMH, prolactin and TSH, sometimes with others such as testosterone or vitamin D. In a monitored cycle, a patient may have bloods taken every day or two, and the clinical team compares each result with the previous ones and with the scan. That shapes what the software must do:

  • show each result against the patient's earlier results in the same cycle, in a cumulative view
  • release results quickly, with critical or unexpected results flagged for a person
  • keep a clear record of which sample was taken on which day and time

Repeat samples and new visits

Fertility work produces patterns that general lab software often handles badly. A patient might give two samples on the same day, for example a repeat after an unexpected value. A patient returns daily for a week. A result is corrected after release. Each of these must file correctly: same-day repeats against that day's visit, the next day's sample as a new visit, and corrections replacing the earlier value with a record of the change. When this goes wrong, a clinician can see yesterday's value against today's date, which is a real clinical risk.

When choosing software, test these exact scenarios before go-live: two samples on one day, consecutive daily samples, and a corrected result.

Reports the clinical team can use

Clinicians need a report that shows the current result and the trend across the cycle at a glance, in the clinic's branding, with the clinic's own reference ranges and comments. Patients may receive results through an app or portal, with release controlled by the clinic. Results often also need to reach the clinic's EHR or fertility management system so the whole team works from one record.

QC, competency and accreditation

Immunoassay QC should be filed automatically, charted on Levey-Jennings charts and checked against Westgard rules, with patient results held when QC fails. Operators should be trained and authorised per analyser. Clinics working toward ISO 15189 accreditation, or regulated by bodies such as the HFEA in the UK alongside CQC, benefit from having QC, competency, equipment and audit records in the same system as the results. See setting up a private laboratory in the UK.

Connecting the analyser

Common in-house immunoassay analysers connect over ASTM E1394 or HL7 v2, and many support host query, so the operator loads barcoded tubes and each one picks its tests from the order. That removes manual test selection and typed results, which matters when the same patient is tested daily. Analyser not on the list? We build the driver, usually within a couple of days. See bidirectional analyser interfaces, and check your model in our analyser connection guides or the open connectivity dataset.

A worked example: one monitored cycle

Here is how the record should look for one patient through part of a monitored cycle. Days and times are illustrative, and the tests follow whatever protocol the clinic uses.

WhenSampleWhat the system must do
Day 2, 08:30Baseline hormone panelOpen a new visit; release the same day; start the cumulative view
Day 6, 08:15Estradiol and LHOpen a new visit for the new day; show it beside day 2
Day 8, 09:00Estradiol, LH and progesteroneOpen a new visit for the new day
Day 8, 13:00Repeat estradiolFile against the same day 8 visit; show both values with collection times; overwrite neither
Day 10, 08:40Estradiol and LHOpen a new visit; if a day 8 value is corrected, replace it and record the change

Run this exact sequence with test patients in every vendor demonstration, and check what the clinician sees on the cumulative report after each step. The two failure patterns to look for are a same-day repeat that opens a separate visit, and a new day's sample that files into the previous day's visit.

Planning same-day turnaround

Same-day release depends on the whole morning, not just the analyser:

  1. Run QC before the first patient sample, so a QC problem is found before results are waiting.
  2. Draw cycle-monitoring bloods in a defined window, so samples arrive in a predictable batch.
  3. Load samples as they arrive rather than holding them for one large run, where the analyser allows.
  4. Let the analyser pick tests from the order by barcode, so nobody selects tests by hand.
  5. Review and release in the system, with any held result shown with its reason.
  6. Track turnaround from collection to release on a dashboard, and look at the slowest days.

Common mistakes

  • A general system that files every sample as a new encounter, or every day's sample into one long encounter.
  • Typing results from the analyser screen during a busy morning.
  • No QC before the first run, so a failure is found after patient results are already waiting.
  • Reports that show only today's value, leaving the clinician to look up earlier results.
  • Patient-facing release before review by the clinical team.

Questions to ask any vendor

  1. Show us two samples on one day, then a sample the next day. How do they appear?
  2. How does a corrected result appear on the cumulative report?
  3. Is our immunoassay analyser supported by model, with host query?
  4. Can patient release wait until the clinical team approves?
  5. How do results reach our EHR or fertility system? See our integrations.
  6. In a group with several sites, are each site's QC and competency records kept separately?

Patient-facing release

Many clinics let patients see their results in an app or portal. For cycle monitoring, decide what the patient sees and when. Common choices are release only after the clinical team has reviewed the result and planned the next step, or release of selected tests only, with others shared during a consultation. Whatever you choose, the system should hold results back until the agreed step is complete, record when each result became visible, and show the clinic's own comments rather than a generic interpretation.

Checklist for fertility clinics

  1. Same-day release, with the analyser connected and no typing.
  2. A cumulative view of each patient's results across the cycle.
  3. Correct handling of same-day repeats, daily visits and corrected results.
  4. Branded clinician and patient reports with clinic-authored ranges.
  5. Delivery into the clinic's EHR or fertility system.
  6. QC with Westgard rules and lockout, and operator competency.
  7. An audit trail suitable for accreditation and regulatory inspection.

Where Catenix fits

For a clinic running hormone tests in house, Catenix connects the immunoassay analyser over ASTM E1394 or HL7 v2 with host query where supported, files QC with Westgard rules, holds results when QC or competency fails, opens a new visit for each clinic day while keeping same-day repeats together, shows a cumulative results table, and produces branded reports in the clinic's own layout. Results can reach the clinic's EHR and patients through a controlled portal. It is priced per site with no per-test fees. Catenix handles workflow, connectivity and records; reference ranges and comments are the clinic's own content, and clinical decisions stay with the clinical team. Catenix is connectivity, workflow and record-keeping software and is not marketed as a medical device.

Questions people ask

Can a fertility clinic run its own hormone testing?

Yes. Many clinics run immunoassay analysers in house for same-day cycle monitoring, with the QC, competency and records a lab needs.

How should repeat samples on the same day be recorded?

Against that day's visit, with each sample's collection time kept, so the clinician sees both values in order and nothing is overwritten.

Can results go to our fertility management system?

Often, through HL7 or an API. Ask your fertility system vendor which routes it supports for an outside lab system.

Does Catenix interpret hormone results?

No. The clinic's ranges and comments appear on reports as the clinic's own content, and decisions stay with the clinical team.

Which analysers do clinics use for in-house hormone testing?

Usually a benchtop immunoassay analyser with estradiol, progesterone, LH, FSH and hCG on its menu. Check that it connects over ASTM or HL7 and supports host query; our analyser connection guides list the interface for each model.

How quickly can in-house hormone results be released?

The assay run times set the floor. With QC run before the first sample, a connected analyser and no typing, results can usually be released the same day, often within hours of the draw, depending on run times and review.

Sources and further reading

Take it with you

The buyer's guide, in your inbox.

Nine pages on what POCT connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier.

Get the POCT connectivity buyer's guide

Nine pages, vendor-neutral: what connectivity is, the standards in plain English, the cost of doing it by hand and eight questions to ask any supplier. The PDF also opens directly from the downloads page; leave an email only if you want it in your inbox.

We use your email only to send the guide and, if you ask, to follow up once. No newsletter unless you tick the box. See our privacy notice.

Thank you. The guide is on its way. You can also open it now.
That did not send. Open the guide directly or email contact@catenix.com.

See it done in software.

A 30-minute walkthrough on a live tenant, with your analysers and your allowable-error limits.