top of page

The Global Maternity Code Is Being Deleted. What Self-Funded Plans Must Do Before 2027

Oct 29
7 min read

Updated: Nov 3

For decades, a pregnancy has been one of the most predictable line items a self-funded health plan pays. Routine maternity care has been billed under a single “global” obstetric code that bundles roughly nine months of prenatal visits, the delivery, and postpartum care into one claim at one price. The American Medical Association describes that code as a single service that stands in for an entire pregnancy, which simplifies billing but hides how much care varies.

That bundle also worked as a built-in cost ceiling. No matter how many prenatal visits a patient had, the plan paid one negotiated amount. That ceiling is about to be removed, and most plan sponsors have not connected the change to their own exposure.

Effective January 1, 2027, the AMA is deleting the global maternity codes in CPT® and splitting maternity care into four separately reported phases. For a self-funded plan, one capped claim becomes a stream of separate claims, each one a new leveling and payment decision. This is a payment integrity event with a hard date.

January 1, 2027. The AMA deletes global obstetric codes 59400, 59510, 59610, and 59618. Across the full restructure, 17 codes are deleted, 12 are added, and 6 are revised.

What Is Changing on January 1, 2027

The coding change is final. The AMA’s CPT® Editorial Panel approved it, and the AMA has published the full lists of deleted, new, and revised codes. Maternity care will be reported in four phases:

  • Antepartum. Every prenatal visit is reported as its own evaluation and management (E/M) encounter under standard E/M rules.

  • Labor management. New daily codes, split by initial versus subsequent day and by straightforward versus complex.

  • Delivery. New delivery-only codes that do not depend on the other components. Labor management is reported separately.

  • Postpartum. Each postpartum visit is an E/M encounter. Routine postpartum care on the delivery date belongs to the delivery code, and the physician's hospital visits after the delivery day use subsequent hospital care codes.

The American College of Obstetricians and Gynecologists (ACOG) worked with the AMA on the restructure and has published its own guidance on how payers should handle prenatal visits during the transition. We cover that timing below.

From One Claim to a Dozen or More

Operationally, a pregnancy that used to arrive as one global claim now arrives as a stream. Revenue-cycle vendor Rivia Health puts it at “a dozen or more separate claims” across nine-plus months, and Wildflower Health describes the same shift from one global claim to a dozen or more. Those are vendor estimates, not AMA figures, but the direction is not in dispute.

The extra volume is not just an administrative headache for your third-party administrator (TPA). Every additional claim is another chance for an error to be paid. When the global code governed the episode, the plan paid once. Now each prenatal visit, each labor management day, the delivery, and each postpartum encounter is leveled and adjudicated on its own. RMH Compass, which benchmarks employer maternity benefits, expects higher claim volume and higher TPA processing fees, and says there is “no longer a built-in cost ceiling” for complex, multi-visit pregnancies.

Four Error Patterns to Expect During the Transition

Unbundling and upcoding are long-standing improper payment patterns, and this transition sets up ideal conditions for both. A legal alert on National Law Review advises provider organizations to build controls against “inappropriate unbundling, duplicate billing, unsupported E/M coding” and inconsistent coding across sites. The same patterns show up on the paying side:

  • E/M level creep. With every prenatal and postpartum visit billed as its own E/M encounter, routine visits can be leveled higher than the documentation supports. Small per-visit increases, multiplied across a dozen or more encounters, add up.

  • Duplicate antepartum billing. When several providers or sites touch the same pregnancy, the same prenatal visit can be submitted more than once across the nine-month window. The global code made that much harder.

  • Old and new codes overlapping on the same pregnancy. Pregnancies that straddle January 1 can be billed under both systems. A late-2026 delivery is still billed with a global code such as 59400, which includes postpartum care, while postpartum visits on or after January 1, 2027 are billed as separate E/M visits. Prenatal visits in 2026 can be billed with antepartum codes 59425 or 59426, while visits in 2027 are billed as E/M. When global codes, E/M visits, and the old antepartum codes overlap on one pregnancy, the plan can pay twice for the same care.

  • Postpartum services billed separately that belong in the delivery code. Under the AMA’s guidelines, routine postpartum care on the delivery date is part of the delivery code. Billed on its own, it is a duplicate.

In our view, the transition year is when these patterns are most expensive. Provider billing systems, superbills, and EHR templates are all being rebuilt at once, while payer claim-edit rules for the new maternity code families will be new and unproven. Immature billing on one side and immature edits on the other is exactly when incorrect claims get paid.

The Medicare Piece Is Not Settled, and That Matters

The coding change is final. Medicare’s response is not. In the CY2027 Physician Fee Schedule proposed rule (CMS-1848-P), published in the Federal Register on July 16, 2026, CMS proposed to recognize the new codes. According to AAPC, it also asked for comment on creating 15 HCPCS G-codes to preserve Medicare's global structure. ACOG urged CMS to “make a clean break by not implementing the proposed G-codes,” and warned that patients would be split into two groups depending on whether their insurers choose to unbundle.

Comments closed on September 14, 2026, and the AMA says CMS will release the final rule in early November. Your plan’s claims are adjudicated under your plan document and your TPA’s edit logic, not the Medicare fee schedule. But if Medicare keeps one structure while commercial payers adopt another, edit logic across the market fragments, and the transition-year confusion that drives improper payments gets worse.

The Defense Is Layered Claims Review

This is a known problem with a known answer. Unbundling creates exposure, a payment integrity problem, and payment integrity is solved by reviewing claims on both sides of payment, not just one.

Pre-Pay review catches cross-claim and cross-coding problems before money leaves the plan. Examples include a 2027 postpartum E/M visit billed after a 2026 global delivery claim that already covers postpartum care, a duplicate prenatal visit, a postpartum service that belongs in the delivery code. These are catchable before payment when the plan applies Pre-Pay review tuned to the new maternity code families, instead of relying on a carrier engine built to protect its own book.

Post-Pay review behind it recovers what leaks through while everyone’s systems adjust. No edit set is perfect in a transition year. An independent claims review identifies and recovers errors paid before the edits matured.

Running one without the other guarantees a coverage gap, and a transition year like this one is when that gap is most expensive.

Stephen Carrabba, President and Co-Founder, ClaimInformatics

This is also a fiduciary question, not just an operational one. Plan sponsors have a duty to pay only what the plan owes and to protect plan assets from waste. When a long-standing cost control disappears on a known date, choosing not to strengthen claims review is itself a decision. Understanding why independent claim review is a fiduciary responsibility has never mattered more, because the party that benefits from the old bundled convenience is not the party whose assets are now exposed.

This is the same upcoding and unbundling dynamic that already inflates employer plans, now concentrated into a single, dated coding event. Plans that treat 2027 as a payment-integrity deadline, not a billing-department update, are the ones that keep the cost ceiling they are about to lose.

What to Do Before January

  • Confirm your TPA is ready. Ask how its edit logic will handle the new prenatal E/M, labor management, delivery-only, and postpartum codes, and when those edits go live.

  • Know the transition has started. Payer and coding guidance, including an AAFP coding bulletin and state Medicaid programs such as MassHealth, already set September 1, 2026 as the point where a pregnancy’s first prenatal visit is billed with individual E/M codes rather than the global code, so claims under the new structure may already be arriving ahead of the AMA’s January 1, 2027 effective date.

  • Insist on both layers. Pre-Pay review to stop errors before payment, and independent Post-Pay review to recover what gets through during the immature-edit window.

  • Treat it as a fiduciary action item. Document the decision to strengthen maternity claims review ahead of the change. A defensible process is built before the exposure, not after.

Get Ahead of the 2027 Maternity Unbundling

ClaimInformatics helps self-funded plans and TPAs build the layered Pre-Pay and Post-Pay review that protects plan assets when the global maternity cost ceiling disappears. See our Self-Funded Solutions or let us pressure-test your maternity claims exposure before January.

Schedule a confidential assessment: claiminformatics.com/contact or send an email to hello@claiminformatics.com for immediate follow-up.

Related Reading

FAQs Block

What exactly is changing with maternity coding in 2027?

Effective January 1, 2027, the AMA is deleting the global obstetric CPT® codes, including 59400, 59510, 59610, and 59618, and splitting maternity care into four separately reported phases: antepartum, labor management, delivery, and postpartum. The restructure deletes 17 codes, adds 12, and revises 6. Prenatal and postpartum visits are reported as individual E/M encounters.

Why does deleting the global code matter for a self-funded plan?

The global code bundled an entire pregnancy into one capped payment. Without it, one claim becomes a dozen or more separate claims, each leveled and adjudicated on its own, and the built-in cost ceiling for multi-visit pregnancies is gone. That raises claim volume and the risk of paid errors.

What billing errors should plans watch for?

E/M level creep on prenatal and postpartum visits, duplicate prenatal billing across providers, old and new codes overlapping on pregnancies that straddle January 1, 2027, and routine postpartum care billed separately when it belongs in the delivery code. These are most likely during the transition year, when provider billing systems and payer edits are both immature.

Is the Medicare payment change final?

No. The coding change is final, but the CMS CY2027 Physician Fee Schedule is a proposed rule that also asks for comment on 15 HCPCS G-codes that would preserve the global structure for Medicare. Comments closed September 14, 2026, and the AMA says CMS will release the final rule in early November. Your plan's claims follow your plan document and your TPA's edits, but a split market makes edit logic harder to get right.

How should a plan protect itself before the change?

Use layered claims review. Pre-Pay review tuned to the new maternity code families stops cross-claim and cross-coding errors before payment, and independent Post-Pay review recovers what leaks through while edit logic matures. Running one without the other leaves a coverage gap that is most expensive during a transition year.

Comments


bottom of page