The outcome that the whole record was for

Closing the loop back to the cycle

An outcome that cannot be traced to the treatment that produced it is an anecdote. The pregnancy record is therefore anchored to a patient file and to the treatment cycle that produced the conception, and it stays anchored: the patient link is locked once the record exists, so a pregnancy cannot quietly be reassigned. Everything downstream hangs off that anchor, which is what allows a live birth to be attributed to a specific cycle and, through the cycle, to a specific transfer.

• Pregnancy Follow-up list, create form and detail drawer are built screens
• Each pregnancy record carries Files and change-history tabs
• Optional link to the clinic visit at which the pregnancy was recorded
• Records move between active, inactive and deleted rather than being erased

Biochemical, clinical, ongoing: three different things

Reported success rates are only comparable when the denominator and the milestone are defined the same way, so the record keeps the milestones apart rather than collapsing them into one status. Three beta-hCG draws are captured with date and value to three decimals: the first test, the repeat used to judge the rise, and the final reading before sonographic confirmation. Fetal cardiac activity is a separate confirmed flag with its own date, and clinical pregnancy and ongoing pregnancy are separate yes or no fields again. A biochemical pregnancy that never produced a sac is therefore visible as exactly that.

The antenatal course, scan by scan

A pregnancy is a trajectory, not a single verdict, and the checkup record models it as one. Each antenatal visit is captured as its own row under the parent pregnancy, with gestational age in completed weeks plus days, the ultrasound report, fetal heartbeat presence and rate, crown-rump length for dating, nuchal translucency for first-trimester risk screening, fetus count at that scan, and explicit bleeding and pain flags. The serial checkup table is data-model only today, exposed through the API without a dedicated data-entry screen, but the pregnancy record it belongs to is a fully built workspace.

How the pregnancy ended, in structured form

The pregnancy record carries a quick outcome label; the outcome table is the formal dataset, and there is exactly one per pregnancy, enforced by a uniqueness constraint. It models the outcome type and date, gestational age at outcome, mode of delivery, the delivering hospital, separate live-birth and stillbirth counts for multiples, and the type of loss where the pregnancy did not continue. Separating counts of liveborn and stillborn babies matters for multiples, where a single pregnancy can produce both. The system models this record and serves it over the API; it has no dedicated screen yet.

• Outcome type: live birth, miscarriage, ectopic, biochemical, stillbirth, termination, unknown
• Delivery mode: vaginal, caesarean section, instrumental
• Loss type: clinical, biochemical, missed
• Gestational age at outcome distinguishes early loss from term delivery

One record per baby

Birth Records is a built screen and it holds one row per neonate, with birth order distinguishing the first-born from the second in a twin pregnancy. It captures sex, birth weight in grams, birth length, APGAR at one and five minutes, an overall neonatal health status drawn from a seeded list, a congenital-anomaly flag with free-text description, and NICU admission with length of stay in days. APGAR is constrained to the integers zero through ten at both time points, so an out-of-range transcription cannot enter the dataset. Each record links up to the parent outcome and therefore back to the cycle.

Maternal complications, before and after delivery

Maternal morbidity is recorded against the pregnancy rather than left in narrative. Antenatal conditions such as gestational diabetes, pregnancy-induced hypertension, pre-eclampsia, HELLP, preterm premature rupture of membranes, placenta praevia and cervical cerclage are logged with onset date, severity, management and whether and when they resolved. Postpartum complications attach to the outcome record instead, reflecting that they follow the delivery. Both are modelled and API-exposed rather than screen-backed today, and the condition vocabularies are deliberately open-ended, so a clinic that intends to aggregate them should agree its terms in advance.

Recurrent loss, assessed across pregnancies

Recurrent pregnancy loss is not a property of any one conception, so the work-up record attaches to the patient rather than to a single pregnancy. Each row captures one loss with its date, type and gestational age, alongside the four investigative axes: genetic findings on the products of conception, anatomical assessment, immunological work-up and thrombophilia or coagulation findings. It then records whether a cause was identified, what it was, and the management plan for the next attempt. The record is modelled and served over the API; there is no dedicated screen for it yet.