Estimated date of delivery¶

Estimate a pregnancy's delivery date by anchoring gestational age to the best available menstrual, conception, or ultrasound evidence and retaining the estimate unless a documented redating threshold is crossed.

Version: v1 · 2026-09-08 · History
Domain-specific #: 4422
Origin domain: obstetrics
Subdomain: pregnancy dating
Aliases: Estimated due date, Expected date of confinement, EDD

Core Idea¶

The estimated date of delivery (EDD) is the calendar date corresponding to the clinical estimate of 40 weeks' gestation, derived from the best supported gestational-age origin rather than a prediction of the exact birth day.^[1] A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of obstetrics. It is a standardized gestational timeline anchor integrating menstrual, conception, and ultrasound evidence while distinguishing estimated due date from actual delivery prediction. That residual remains recognizable when examples, notation, scale, or implementation change, but it disappears if the carrier is mistyped, the condition that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test. This gives the entry an operational identity rather than merely a historical label.

A useful analysis keeps three layers separate. The constitutive layer says what must be true: the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit. The evidential layer asks what observation or proof warrants the claim: type the carrier, state every parameter and convention in the definition, test that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. The use layer asks what reasoning becomes available once the identity is established: recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Conflating the layers is the most common source of scope inflation.

Structural Signature¶

Carrier: a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty
Inputs or antecedent state: the exact obstetrics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Estimated date of delivery
Constitutive operation: A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating.
Invariant: the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit
Recognition test: type the carrier, state every parameter and convention in the definition, test that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases
Output or consequence: recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions
Failure boundary: the carrier is mistyped, the condition that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test

What It Is Not¶

It is not the whole field of obstetrics. The field contains many questions and methods that do not instantiate Estimated date of delivery.
It is not its most familiar example. Naegele's rule adds one year, subtracts three months, and adds seven days to the first day of a regular 28-day last menstrual period, subject to cycle and evidence qualifications. exhibits the structure, but the example is evidence for the abstraction rather than its definition.
It is not the neighboring catalog concept Gestational age. Gestational age is elapsed pregnancy time under a dating convention; EDD is the calendar endpoint calculated from that age estimate.
It is not a claim that every boundary case has one uncontested classification. a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Estimated date of delivery must control the decision
It is not an unrestricted metaphor for any process that seems similar. Outside obstetrics, the vocabulary and validity conditions do not transfer literally.

Scope of Application¶

Estimated date of delivery belongs to obstetrics and is useful where the analyst can specify a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty, then evaluate the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit. The scope is broad within that domain but bounded by the need for the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit. This entry describes a clinical dating abstraction, not individual medical advice. Actual delivery commonly differs from the EDD; clinical interpretation and redating follow professional guidance and patient-specific evidence.^[2]

Definition and recognition. Determine whether a proposed instance satisfies the constitutive conditions rather than merely sharing terminology.
Construction or evolution. Track how the exact obstetrics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Estimated date of delivery are converted, constrained, or organized by A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating..
Comparison. Compare instances using carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior, without treating convenience measures as the definition.
Boundary analysis. Diagnose cases where a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Estimated date of delivery must control the decision and state which convention or theorem controls the decision.
Downstream reasoning. Use the established identity to support recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions while preserving the assumptions under which the inference is valid.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Estimated date of delivery can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated. The disciplined statement is: given the exact obstetrics carrier, defining parameters and conventions, boundary conditions, source evidence, comparison cases, and any measurement or proof assumptions needed to evaluate Estimated date of delivery, the structure counts as Estimated date of delivery exactly when the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit.

This format also separates identity from measurement. Empirical, computational, or documentary proxies support recognition only under declared validity and uncertainty assumptions; formal cases require proof rather than measurement. Measurements can be noisy, implementations can approximate, and proofs can use equivalent characterizations; none of those facts licenses changing the object being measured. When reports disagree, first check scope and convention, then data or proof, and only then interpret the disagreement as substantive.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Estimated date of delivery. Estimated date of delivery compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

The compression has a price. A single label can hide canonical, generalized, restricted, approximate, computational, empirical, and historically variant formulations of Estimated date of delivery. Good use therefore carries a small declaration of assumptions alongside the name. The abstraction manages complexity when it reduces the state space of the question while keeping the failure boundary visible; it mismanages complexity when the label substitutes for that boundary analysis.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit independently of one notation or implementation. This step prevents the canonical example from becoming the definition.
Derive consequences. From the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit, infer recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions. Record each assumption used so that a later change of setting does not silently preserve an invalid conclusion.
Test adversarial cases. Examine a generalized or degenerate case may change existence, uniqueness, measurement, or naming conventions, so the exact definition of Estimated date of delivery must control the decision and an object that resembles Estimated date of delivery in purpose or vocabulary but does not satisfy its invariant is outside the class. A robust identity explains why the first is convention-sensitive and why the second is outside the class.
Compare and refine. Use carrier, parameters, convention, domain, scale, boundary conditions, evidence, exact versus approximate form, and limiting behavior to compare legitimate instances, and refine the model when discrepancies reflect hidden variation rather than failure of the abstraction itself.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of obstetrics because they reuse a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty, A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating., and type the carrier, state every parameter and convention in the definition, test that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases. A theorem, diagnostic, or modeling warning can travel when those roles remain literal. For example, the distinction between constitutive identity and a convenient observable transfers from Naegele's rule adds one year, subtracts three months, and adds seven days to the first day of a regular 28-day last menstrual period, subject to cycle and evidence qualifications. to A first-trimester crown-rump-length estimate differs sufficiently from an uncertain menstrual date that a clinician adopts the ultrasound-based EDD under the applicable guideline and records the change..^[3]

Transfer outside the home domain is weaker. The skeletal pattern—type the carrier, apply the defining mechanism of Estimated date of delivery, preserve its invariant, and derive only consequences licensed by the stated boundary—may suggest an analogy, but the domain-specific mechanisms, admissible evidence, and consequences do not come along automatically. The safe transfer procedure maps each role explicitly, checks the invariant again, and refuses the name when only a superficial resemblance remains.

Examples¶

Canonical¶

Naegele's rule adds one year, subtracts three months, and adds seven days to the first day of a regular 28-day last menstrual period, subject to cycle and evidence qualifications. The example exposes the carrier and directly tests that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit; changing incidental notation preserves the identity, while removing that condition destroys it. This example is canonical because every role can be inspected: the carrier is a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty; the operative rule is A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating.; the invariant is the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit; and the result supports recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions.^[1] Changing incidental notation or scale leaves the structure intact, while removing the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit destroys the classification.

Mapped back: a pregnancy, a gestational-age origin, menstrual or assisted-conception dates, ultrasound biometric observations, dating rules, and uncertainty → A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating. → the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit → recognizing and comparing instances of Estimated date of delivery, deriving its domain-specific consequences, selecting valid models or methods, and preventing transfer beyond its assumptions

Applied / In Practice¶

A first-trimester crown-rump-length estimate differs sufficiently from an uncertain menstrual date that a clinician adopts the ultrasound-based EDD under the applicable guideline and records the change. The applied case qualifies only because the same invariant and boundary test remain literal under changed parameters or implementation. The applied case is not licensed merely by vocabulary. It qualifies because the same recognition test—type the carrier, state every parameter and convention in the definition, test that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases—can be run and because the same failure boundary—the carrier is mistyped, the condition that the EDD is derived from one documented dating origin and guideline, with cycle assumptions, scan timing, uncertainty, and any redating decision explicit fails, a neighboring object is substituted, or notation and topical resemblance replace the constitutive test—remains meaningful.^[2] The case also shows why practical outputs should report assumptions, resolution, and uncertainty instead of a naked label.

Mapped back: declared instance → recognition test → boundary check → qualified use

Structural Tensions¶

T1: Axiomatic identity vs. operational recognition. The defining conditions may be exact while empirical or computational recognition is approximate. Neither pole can be removed without changing the analytical task. Diagnostic: Can the reviewer state both the exact condition and the evidence used to infer it?
T2: Local roles vs. global consequence. The mechanism is enacted through local relations, but the abstraction is usually valued for a global classification or prediction. Neither pole can be removed without changing the analytical task. Diagnostic: Does the claimed global result actually follow from the declared local conditions?
T3: Ideal form vs. finite representation. Theory states a clean invariant while data structures, measurements, or proofs expose only finite representations. Neither pole can be removed without changing the analytical task. Diagnostic: Would increasing resolution converge toward the same classification?
T4: Canonical convention vs. legitimate variants. A standard formulation supports communication, while variants may preserve the same core under changed assumptions. Neither pole can be removed without changing the analytical task. Diagnostic: Which role is invariant across variants, and which convention-specific conclusion changes?
T5: Compression vs. hidden assumptions. The name compresses a complex argument but can conceal prerequisites. Neither pole can be removed without changing the analytical task. Diagnostic: Can each downstream inference be traced to an explicit assumption?
T6: Autonomous residual vs. reduction to catalog neighbors. The candidate uses broader structures but adds an identity-bearing residual. Neither pole can be removed without changing the analytical task. Diagnostic: After subtracting the proposed parent and named neighbors, does the constitutive residual still support independent diagnostics?

Structural–Framed Character¶

The entry is structurally mixed but domain-framed. Its portable skeleton is type the carrier, apply the defining mechanism of Estimated date of delivery, preserve its invariant, and derive only consequences licensed by the stated boundary. Its identity-bearing terms—Estimated date of delivery, carrier, parameter, invariant, boundary, evidence, model, transformation, and application—derive their meaning from obstetrics and cannot be replaced by generic systems language without losing the tests that distinguish valid from invalid instances.

This mixed character explains why the abstraction is reusable inside the domain yet does not meet the Prime bar. The structure organizes reasoning, but its claims still depend on domain-specific objects, evidence, and intervention semantics.

Structural Core vs. Domain Accent¶

The structural core consists of a carrier, A last-menstrual-period date supplies an initial convention; known fertilization or embryo-transfer dates can anchor conception more directly; early ultrasound biometry estimates gestational age. Clinical rules reconcile discrepancies and document any redating., a recognition invariant, and a consequence. That skeleton may resemble patterns elsewhere, especially type the carrier, apply the defining mechanism of Estimated date of delivery, preserve its invariant, and derive only consequences licensed by the stated boundary. The domain accent is not decorative: Estimated date of delivery, carrier, parameter, invariant, boundary, evidence, model, transformation, and application determine what counts as an admissible carrier, a valid transition, and successful evidence.

The abstraction therefore remains domain-specific. A cross-domain reuse that preserves only words such as 'balance,' 'cut,' 'sequence,' 'loss,' or 'simulation' is metaphor. Literal transfer requires the original role structure and diagnostics, which in this case remain anchored in obstetrics.

The proposed strict upward parent is prime:measurement. The EDD is a standardized temporal measure inferred from clinical anchors; obstetric dating rules and uncertainty supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Estimated date of delivery adds domain-specific constraints.

The entry does not collapse into that parent because a standardized gestational timeline anchor integrating menstrual, conception, and ultrasound evidence while distinguishing estimated due date from actual delivery prediction It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Estimated date of delivery. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge.

The prospective workspace queue contains one strict upward edge to prime:measurement. No live DAG mutation is authorized.

Relationships to Other Abstractions¶

Current abstraction Estimated date of delivery Domain-specific

Parents (1) — more general patterns this builds on

Estimated date of delivery is a kind of Measurement Prime

The proposed strict upward parent is prime:measurement.

Hierarchy path (1) — routes to 1 parentless root

Estimated date of delivery → Measurement

Neighborhood in Abstraction Space¶

Estimated date of delivery sits in a sparse region of the domain-specific corpus (71^st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Population Aging & Intergenerational Welfare (10 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08

Not to Be Confused With¶

Gestational age. Gestational age is elapsed pregnancy time under a dating convention; EDD is the calendar endpoint calculated from that age estimate.
One canonical example. An instance demonstrates the structure but does not define the whole abstraction.
Measurement or implementation of Estimated date of delivery. A proxy or realization is evidence for the abstraction, not the abstraction itself.
Generalized Estimated date of delivery. An extension qualifies only when its changed axioms and retained invariant are stated.

References¶

[1] American College of Obstetricians and Gynecologists, Committee Opinion No. 700: 'Methods for Estimating the Due Date,' Obstetrics & Gynecology 129(5) (2017), e150-e154, reaffirmed 2022, DOI 10.1097/AOG.0000000000002046. registry ↩a ↩b

[2] World Health Organization, WHO Recommendations on Antenatal Care for a Positive Pregnancy Experience, 2016, gestational-age and ultrasound recommendations. registry ↩a ↩b

[3] L. J. Salomon et al., 'ISUOG Practice Guidelines: Ultrasound Assessment of Fetal Biometry and Growth,' Ultrasound in Obstetrics & Gynecology 53 (2019), 715-723. registry ↩