The prenatal record lists one gestational age, but the delivery note documents a different gestational age for the same obstetric encounter. What should the coder do before finalizing OB codes that depend on gestation?

When the prenatal record lists one gestational age but the delivery note documents a different gestational age for the same obstetric encounter, the coder should seek clarification to resolve the gestational-age conflict with the delivering provider before finalizing OB codes that depend on gestation. Accurate gestation supports obstetric diagnosis coding and quality data for public maternity services. Always using the prenatal record because it was documented earlier fails when delivery documentation updates gestation. Selecting whichever gestational age produces the higher-weighted DRG fails as payment-driven choice. Omitting all gestation-related codes so the conflict never appears fails reporting completeness and quality metrics. Exam caveat: gestation conflicts require provider resolution, not earlier-note defaults, DRG shopping, or omission. Operational check: query the delivering clinician at the civic obstetric service, update the authoritative gestational age, then assign gestation-dependent codes. Review recurring prenatal-versus-delivery mismatches for documentation workflow improvement in the municipal perinatal program. In municipal and county facility practice, record the rationale for the chosen coding path and the rejected alternatives in the abstract notes so auditors and future coders understand the clinical and compliance basis. Re-check the decision if new authenticated documentation arrives before final bill drop, and escalate persistent documentation gaps to CDI or compliance rather than normalizing unsupported shortcuts that would distort civic claims, quality metrics, or case-mix reporting.