OB-GYN coding and reimbursement: an owner’s operating playbook

Why owners need a payment operating system

Coding and reimbursement connect clinical business activity with payer rules and cash management. Owners do not need to code individual encounters themselves. They do need a reliable way to know whether the practice’s billing rules match its contracts, whether claims represent the work performed, and whether payment reaches the bank in a predictable period.

That responsibility becomes more visible when a practice adds a service, changes billing staff, negotiates a contract, or revises its maternity care workflow. A claim can be technically clean but paid at an unfavorable rate. A payer can remit the contracted rate while the practice has missed a separately billable service. A favorable month can also hide an older receivables problem. Owners need a process that connects activity to payment and assigns someone to investigate exceptions.

This guide sets out that process at the business level. It does not give code selection instructions for specific cases. CPT, ICD-10-CM, HCPCS, payer policies, and contract terms change. A qualified coder or billing specialist should validate operational rules against authoritative current references before the practice submits claims.

Build the control framework before the first claim

Start with an inventory of entities, locations, billing identifiers, and services. Record which legal entity furnishes each service, which tax identification number and National Provider Identifier appear on the claim, where the service occurs, and which organization receives payment. In a multisite group, this inventory helps expose stale identifiers, duplicate payer records, or a mismatch between the contracted entity and the billing entity.

Next, create a payer requirements register. For every material contract, store the signed agreement, amendments, fee schedule, provider roster requirements, authorization rules, timely filing limits, appeal deadlines, claim submission instructions, and electronic remittance arrangements. Assign a business owner and a backup. Record the source document and the date the practice last verified the operational rule. A staff member should be able to trace a billing edit back to the contract or payer policy that supports it.

Create a service-to-billing map for each major line, such as office evaluation and management, maternity care, delivery, gynecologic procedures, and imaging. Include other ancillary services that the practice provides. The map should identify who performs the work, where it occurs, the documentation workflow, the responsible billing queue, and the payment destination. Keep clinical decision-making and coding interpretation with appropriately qualified professionals. Owners use the map to confirm that the business workflow has a responsible person at every handoff.

Treat maternity payment as an episode and transition problem

Maternity reimbursement has historically involved global maternity billing, separate antepartum or delivery services, transfers between clinicians, and payer-specific policies. Owners should not assume every patient episode is billed the same way across all plans. The practice must verify the applicable payer contract and current coding guidance for the services actually furnished.

ACOG describes a significant upcoming structural change to obstetric billing. ACOG describes a transition to new CPT maternity care codes and recommends health plans use E/M billing for antepartum visits during the implementation period, with modifier TH to identify maternity care. Its public guidance also explains that current delivery-only codes encompass labor management through delivery and completion of postpartum orders and the birth certificate. These details are presented here as ACOG’s published transition guidance, not as individualized coding instruction. Practices should consult the current ACOG payment for obstetric services page, their payer bulletins, and qualified coding staff as the transition approaches.

Owners can prepare without guessing at code-level implementation. Identify each payer that covers a meaningful share of maternity revenue and note whether it has published a transition policy. Ask the billing vendor or internal team to show how the current system represents prenatal visits, delivery, transfers of care, and postpartum work. Assess whether the practice management system can support distinct charge capture and reporting across prenatal encounters, including cases that may no longer use one episode-level claim. Test the sequence in a controlled environment before changing production configuration. Reconcile claims and remittances for a sample of transitions, then compare the result with the payer’s written policy.

Do not wait for a first denial to expose a configuration gap. Make an implementation register with the payer, affected service, source of rule, system owner, test case, approval status, and effective period. Confirm that scheduling, charge entry, coding edits, claim generation, remittance posting, and patient statements reflect the same approved workflow. Preserve prior rules and effective dates so that a claim can be explained later.

Measure the revenue cycle by failure point

An owner dashboard should separate at least five stages: charge capture, clean claim submission, adjudication, remittance posting, and cash deposit. A single “collections” number cannot show where work is being lost or delayed.

Use operational definitions consistently:

Charge lag: days from service date to charge entry or release, reported by service line and location.
First-pass acceptance: claims accepted by the clearinghouse or payer without a front-end rejection, divided by claims submitted. Keep clearinghouse acceptance distinct from final adjudication.
Denial rate: denied claim lines or claims divided by the corresponding submitted population, using one clearly named unit.
Appeal recovery: dollars recovered on appealed denials divided by dollars appealed, with appeal labor and vendor fees tracked separately.
Days in accounts receivable: total receivables divided by average daily net patient service revenue, with the reporting convention documented.
Aging mix: receivables grouped into stable age bands, separated by payer and patient responsibility.
Net collection rate: cash collected compared with collectible allowed amounts for a defined cohort, excluding or separately identifying contractual write-offs and other adjustments.

The formula is only useful if the numerator and denominator are visible. Have finance reconcile the dashboard to the ledger and billing system. Record whether the measure is based on service date, claim date, adjudication date, or deposit date. A current-month cash report may include older work, while current-month services may not yet have reached adjudication. Use cohort views to understand cash conversion for claims from the same period.

Classify denials by root cause, and also report them by payer. Common business categories include eligibility, authorization, credentialing, missing or inconsistent data, timely filing, code or modifier edits, medical record requests, coordination of benefits, and payer processing. Assign each category to an accountable team. Then review the largest categories by preventable dollars, not just claim count. A small number of high-value recurring errors can matter more than a large queue of low-dollar corrections.

For underpayments, compare the expected allowed amount with the actual remittance using the executed fee schedule and claim facts. Store examples, payer correspondence, appeal outcomes, and any corrected contract load. Do not treat a paid claim as a correctly paid claim. Owners should see both underpayment dollars identified and amounts recovered, along with the time required to secure recovery.

Protect coding quality while improving capture

The commercial goal is complete, accurate representation of the service furnished. A practice should not encourage unsupported coding, upcoding, or documentation changes made solely to reach a payment target. Instead, establish a defensible review path:

A qualified professional identifies a recurring question or denial pattern.
The practice checks current official coding guidance, the payer contract, and relevant payer policy.
The billing rule is documented with its source and effective period.
A sample is reviewed to determine whether the issue is isolated or systematic.
Staff receive role-specific training, and the change is tested before broad release.
Subsequent claims are monitored for both payment and accuracy.

Use periodic audits that examine samples across providers and service categories, then compare locations and payers. The purpose is to find process variation, unsupported assumptions, or training needs. Track findings to closure, including refunds or disclosures when qualified compliance advisers determine they are needed. Maintain versioned policies and training records. Escalate ambiguous issues to a qualified coding specialist or compliance professional. Counsel can advise on legal questions. Do not allow informal interpretations to become permanent rules.

ACOG offers an OB-GYN coding manual and other coding resources. Its member Payment Advocacy and Policy Portal Its public description says the portal supports payer issues and coding questions. It also addresses denials, appeals, telehealth billing, and federal program rules; access is free to ACOG members and their staff after registration. These resources can be useful for eligible practices, but they are not open-access owner tools. The ACOG coding page lists public resources and identifies the portal boundary.

SMFM has published open-access historic coding and billing resources and offers practice management and MFM-specific coding education. Its listed course materials cover financial literacy and practice performance indicators. Coding topics include E/M, incident-to billing, shared or split billing, and ICD-10 indication lists. Course availability and registration terms vary. The SMFM coding guidance page and SMFM learning catalog provide access details. These offerings show the value of specialty-specific training; a practice should confirm current course status before budgeting.

Make payer contracts measurable

Rank payer contracts using more than nominal fee levels. For each material contract, owners should review:

Net revenue and volume by service line.
Allowed amounts compared with actual remittances.
Denial frequency, appeal success, and time to payment.
Authorization and documentation workload.
Timely filing and appeal windows.
Retroactive adjustment and audit provisions.
Credentialing requirements and contract exit terms.
Patient responsibility and bad-debt exposure.

The practice can estimate contract contribution by service line if it can reliably attribute direct labor and other costs. Avoid false precision when shared costs cannot be allocated credibly. At a minimum, report payer yield alongside administrative burden and collection speed. A contract with a higher nominal fee may consume more staff time or produce more unresolved receivables.

Prepare for negotiation with a clean evidence file: executed documents, payer-specific production, remittance examples, denial trends, and the operational cost of payer requirements. Add service mix and market alternatives when they inform the negotiation. Identify the terms that matter most before a renewal discussion begins. If an amendment changes claim rules or rates, route it to billing configuration and finance. Operational leadership should test the revised rule against representative claims.

Manage vendors as part of the control environment

If a billing company, clearinghouse, coding service, or practice management vendor supports the revenue cycle, the contract should define measurable work and access to records. Specify which party owns charge entry and claim edits. Define responsibility for appeals and reporting. Assign responsibility for posting and payer enrollment in the same schedule. Define service levels with denominators and exclusions. Clarify who approves write-offs, refunds, bank changes, and changes to claim rules.

Require timely export of claim-level data, remittances, work queues, appeal records, and configuration history. Confirm that the practice can retrieve these records if the vendor relationship ends. Review security, subcontractors, breach notice, and permitted data uses. Set rules for retention and deletion. Define transition assistance in its own clause. A low administrative fee is not a complete comparison if the vendor retains control of the only usable history.

Establish a monthly operating review with the vendor or internal revenue-cycle leader. Review charge lag and claim acceptance. Track denials in a separate measure. Keep aging and underpayment results visible in their own reports. Include appeals and unresolved payer issues in the action log. For each variance, record the root cause, accountable person, next action, and expected resolution window. Keep a decision log that allows owners to see whether a problem recurred after the first corrective action.

A 90-day owner implementation sequence

Weeks one through four: name an executive owner and operational lead. Inventory billing entities and payer contracts. Inventory services and systems. Record report definitions and vendor responsibilities. Select a small set of measures with known sources. Reconcile those measures to finance before presenting them to partners.

Weeks five through eight: analyze denials and aging by payer. Review charge lag and underpayment examples by service line. Validate the highest-impact rules with qualified coding resources. Document process owners and backup coverage. Identify contract or system changes that need formal testing.

Weeks nine through twelve: launch a monthly revenue-cycle review and close the first action log. Audit whether the chosen measures changed for a real operational reason. Prioritize one or two process fixes with clear owners. Update partner reporting and staff training based on actual findings, then set the next review cycle.

The sequence is a management framework, not a promise that any practice will improve collections by a particular amount. Results depend on contracts, service mix, payer behavior, data quality and staffing. Results also depend on the actual work performed.

Owner review checklist

Can every important billing rule be tied to a current source?
Are all service lines and billing entities represented in the system map?
Can the team distinguish claim rejection from adjudicated denial?
Do owners see underpayment and recovery data by payer?
Are maternity transition preparations based on written payer guidance?
Does the practice test billing changes before production release?
Are coding questions escalated to qualified professionals?
Does the vendor contract preserve access to practice data and work history?
Are metric definitions stable and reconciled with finance?
Does every recurring problem have an accountable owner and a documented closeout?

The objective is operational visibility. Accurate claims, a controlled process, and clear payment evidence make it easier for owners to manage cash, evaluate payer relationships, and support staff doing complex administrative work.

Sources and limits

These sources describe association resources and published payment guidance. Payer contracts and policies may differ. This guide is business education and does not provide clinical, patient, legal, tax, coding, billing, compliance, or professional advice.