Prepping OB Global Package Docs for 2027 CPT Revisions

Preparing Obstetric Global Package Documentation for the 2027 CPT Maternity Care Revisions

Merry AI · Thoughtfully curated clinical briefs.

The 2027 CPT maternity revisions dismantle the bundled global package. Antepartum care now maps to standard E/M codes; delivery, labor management, and postpartum care unbundle into discrete reportable units.
The documentation risk is structural. Notes that say "routine prenatal care" without preserved gestational age, risk status, and MDM detail will not map to the new reporting model.
Merry AI captures each antepartum encounter as a structured clinical logic note, attested by the clinician, injected into the EHR. No end-of-pregnancy reconstruction.

• The Loaded Labor and denominator model
• Clinical Logic and audit defense
• Clinical Taxonomy ICD-10 documentation standards
• What the AMA guidance leaves undone
• Chrome Extension DOM overlay and field injection
• Pricing and the Practice Partner pilot

The global obstetric package has functioned as a single bundled payment for decades. The 2027 CPT revision replaces that logic with discrete, separately documented units. This brief, prepared by Merry AI, outlines the documentation changes required before January 1, 2027.

Practices that treat this as a billing update will miss the clinical documentation shift underneath it. The work is in the note, not the modifier. We reference the AMA-ASSN Clinical Research source throughout, and Merry AI maps each gap to a point-of-care capture step.

The Loaded Labor & Denominator Model

CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.

Documentation reconstruction is expensive labor. When a global OB note lacks per-visit detail, someone must rebuild it at pregnancy's end. That someone is usually a medical assistant or the clinician.

The fully loaded cost matters more than the hourly wage. A $35,000 base-wage medical assistant carries a loaded annual cost near $48,000 once benefits, overhead, and turnover are counted.

Reconstruction labor is the hidden cost of the old global model.

The denominator question is simple. If structured capture costs 1.3% of one MA's loaded salary and returns 2.1+ hours daily, the reconstruction model is no longer defensible under the 2027 structure.

G2211 is the unlock here. The visit-complexity add-on applies to the longitudinal OB relationship once each encounter stands alone. Unbundled antepartum E/M makes G2211 reportable where the old global code suppressed it.

Clinical Logic & Audit Defense

Consider a multi-location OB group preparing for the 2027 revisions. They audit 60 recent prenatal visits against the new reporting model to test readiness.

The audit finds a pattern. The global OB package note reads "routine prenatal care" but does not consistently preserve gestational age, risk status, ultrasound and lab review, complication management, or separately reportable counseling.

Under the old bundle this was tolerable. Under the 2027 model, where antepartum care maps to individual E/M codes, those missing elements become unmapped visits and lost complexity.

Merry AI captures each antepartum visit as a structured clinical logic note. It prompts the clinician to attest the maternity-package-relevant elements and injects finalized documentation into the EHR workflow.

The result is clean mapping. Each visit maps to the revised 2027 reporting model without cloned-note risk or end-of-pregnancy reconstruction. Human-attested metrics carry the audit weight, preserving documentation integrity.

Attested clinical metrics are the defense. LVEF percentages for cardiac comorbidity, documented preeclampsia severity, and DSM-5-TR perinatal mood findings protect against California SB 1120 and NCCI Modifier 25 clawbacks. Review the NIH National Library of Medicine Research on documentation fidelity.

Clinical Taxonomy: ICD-10 Documentation Standards

The 2027 E/M mapping depends on accurate diagnosis coding at each encounter. Two codes anchor the antepartum documentation standard.

The trimester specificity requirement is where most notes fail. "Unspecified trimester" should be the exception, not the default. Gestational age capture resolves this at the point of care.

The Z34 to O09 decision must be attested, not assumed. A risk status that shifts mid-pregnancy requires the note to reflect that transition when it occurs.

Trimester-specific fifth and sixth characters replace the .90 default once gestational age is captured. Z34.01 through Z34.93 and the O09 severity ladder become reportable only when the note carries weeks-of-gestation at each visit.

What the AMA Guidance Leaves to the Practice: The Workflow Wedge

The 2027 guidance defines the codes but not the capture discipline. It tells you antepartum care now maps to E/M codes. It does not tell you how to preserve per-visit detail across a 40-week relationship.

Our Anchor Truth is this: the deleted global codes (59400, 59409, 59410, 59425) did not just change billing. They removed the structural excuse for summary notes.

Competitors focused entirely on the code crosswalk. They missed the documentation gap between a bundled summary and 13-plus individually reportable E/M encounters that must each stand alone.

The labor management split is the second missed insight. Straightforward versus complex labor management (59080-59083) now requires the note to carry the complexity drivers: abnormal fetal heart tracing, preeclampsia, prior cesarean, multiple gestation. Narrative alone will not map.

• Capture gestational age weekly so trimester specificity holds at every encounter.
• Attest risk transitions explicitly at the visit where Z34 becomes O09.
• Separate counseling from the pregnancy supervision service to protect Modifier 25.
• Record complexity drivers discretely for the labor management split at delivery.

The workflow wedge lives here. Detail must be captured during each visit, not reconstructed at delivery. Explore specialty-specific capture in the Specialty Clinical Playbook Library.

Chrome Extension DOM Overlay & EHR Field Injection

Capture discipline fails when it requires new software, new logins, or IT procurement. The 2027 deadline does not wait for integration tickets.

Merry AI runs as a browser-native overlay. The Chrome extension renders a DOM layer over the existing EHR and injects finalized text into native fields. Zero IT setup is required.

The closed-EHR point matters most. Many OB practices run systems with no open integration path. A DOM overlay works regardless of API access, and FHIR mapping applies where the system exposes it.

PHP and IOP note-splitting logic, validated in the Path Recovery TN case study, carries over to shared prenatal group visits. Each participant receives an individually attested, separately reportable note.

Pricing & the Practice Partner Pilot

The plan tier maps to the documentation problem you are solving before 2027. Basic covers single-provider overlay capture; Pro adds the complexity and group logic OB requires.

The Practice Partner tier runs a closed pilot: five outpatient practices selected weekly for direct solutions engineering. It orchestrates pre-visit, during-visit, and post-visit documentation with audit-shield logic. Review the Practice Partner pricing anchor.

For a Practice Administrator or CMO, the math is the argument. A $648 annual scribe sits at 1.3% of one MA's loaded cost and closes the per-visit gap the 2027 revision opens.

The deadline is fixed. January 1, 2027 arrives with or without capture discipline in place. The notes written through 2026 are the ones that will or will not map.